Issue link: https://iconnect007.uberflip.com/i/1337116
20 DESIGN007 MAGAZINE I FEBRUARY 2021 rotation, etc. Really, to use X = X C – 1, you have to incorporate your five whys. Watson: Exactly. You have to get back to the root cause. What is not working? I mean, you've got to look at the backend. But there's another process here also, once you've taken a component through creating it, first defin- ing who's going to do it, creating the process, taking it into quarantine, QCing that process, and getting it into prototype. Yes, it looks good from there. e one thing I've actually written about is that there's never a finish line in the library. It's not like you look at your library and say, "We're all done." ere's always going to be that tailoring process at the very end where you now get more information from people. Everything filters back. It's one big circle. Matties: In your experience, John, do you find the 80/20 rule to be true? at 80% of the issues come from the library? Watson: Yes, exactly. A lot of the issues that occur on the library are filtered back to the library. A lot of times when you have a library that you've been working with for a while you stop the tailoring process. You never look at your footprints and ask how you can improve this footprint. It's always going to be improved on. You're always going to say, "Yes, this can be improved on here by doing this or that." Maybe there are now recommendations coming in from IPC. ere's always that polishing of that component. It's a complete process here; it's not straight or linear, it's circular. Matties: How many points of data or informa- tion would one component have in the library? Is that user defined, or is there a standard that you would follow? Watson: It could vary. When you're talking about parametric information on a compo- nent, that could be endless, actually. What will happen is you begin to categorize components into what would be categories and families. If you go into Digi-Key and pull up a component, it will show you this is your category, and this is your family of components. ose families of components will start having a general- ized parameter of information. e families will have general parameters of information attached to each family. And that's kind of the way you would organize your library also. ere are two things about a library. Number one is you want to be able to find things quickly and find them accurately, and then number two is you want to structure your library in a way where it rolls with the company. A library is not a static item. It's a very, very dynamic item. It has to grow with your company. Matties: Do you think that if a process is fol- lowed as you're describing, you'll never miss a footprint?