I am working with our libraries right now and have an oppertunity to change them drastically if I need to. Currently, our libraries contain aproximatly 20,000 different physical parts (lines of .ptf files), about 1,000 different pad stacks, 6,500 symbols. We are creating databases for our sourcing and quality groups to have vision to what parts we use, where we use them and how often. We would also like to pull from those databases to make design decisons based off part cost and quality when placing parts in Design Entry HDL. Does anybody have any "best practices" for how to structure the library, key things to include, key things to exclude, etc?
Also, are there any suggestions on how to integrate the different databases and libraries? We use Windchill on the mechanical side of things, would it be beneficial to change our license from SPB to ADW so that we can use the integration between Windchill and ADW, or are there other systems that can do the same thing without changing our platform?
Good to see that you’re bringing valuable part data early into the design decision phase!
The short answer is that ADW will indeed provide you the best option to elegantly populate your library parts with the needed properties so that the designers can make intelligent design decisions. Where parts are used (in which designs), sourcing/cost/part lifecycle management/etc. are just some of the features that ADW will provide.
You can add properties to PTF files and designers will see those properties when doing a search through the Component Browser, but this will be a much more manual approach for the librarians. Also, you’d need to write programs to determine the where-used data.