Scope Your PCB Design Data Management System for Success
One of my favorite quotes from Zig Ziglar is “Success means doing the best we can with what we have. Success is the doing, not the getting; in the trying, not the triumph. Success is a personal standard, reaching for the highest that is in us, becoming all that we can be.”
I like that - doing the best we can with what we have. I’d also add that to be successful with anything, we need realistic expectations and an understanding of precisely what success means, which may be different for each of us.
In this blog, we look at what is meant by success in PCB Data Management. Because of constant, dynamic changes in information, your library becomes an actual living, breathing thing. We will then look at what the baseline is for Data Systems so that you can operate with the lowest risk possible.
In the second part, we will look in more detail at what the S.M.A.R.T. rule for every PCB Data Management system involves, and how putting that in place ensures our success.
What is meant by success in PCB Data Management?
I believe that the term “success” regarding PCB Design Management is multi-faceted. When I first started our PCB Data Management system, I was quick to realize that it was a massive undertaking. There was no finish line to cross. Library and PCB data Management project aren’t typical. A typical project is one that starts with a clear scope and objective and ends upon reaching that objective. If what we designed works, it is considered auspicious. That is not the case with PCB Data Management, which involves what I would consider conditional levels of success. We’ll go over this in more detail coming up.
Static vs. Dynamic Information
The primary reason for the consideration of “conditional success” in our Data System is the nature of data itself. The data in our Data System falls into two major categories. The first is static, meaning that the data does not change at all. A few examples of static data might include Manufacturer, part number, schematic symbol, and 3D Model.
The second category of data is dynamic data - information that changes or continually evolves. Examples of dynamic data are supply vendors, price, quantity available, and sometimes even parametric information.
Because dynamic information changes, components need to be updated regularly. This is what makes the PCB Data Management system a living, breathing thing. If dynamic information is not kept up to date in your PCB Data management system, the data becomes irrelevant and of no use to the PCB Designer. A term used to describe a Library in this state is stale.
What would the initial scope and objective of a PCB Data Management System be?
If it is true that the components continually change, what is the starting baseline that we should have for our Data Management system? We accept the fact that some of the data will change at some point. However, by assuring that you meet the minimum standards, you can develop a PCB design with the lowest risk possible. Two standards that you must have in place are minimal component requirements and a review process.
Minimal Component Requirements
Newly created components should meet a checklist of requirements. For example, if a typical schematic symbol requires specific items then that should include pin connections, pin number, pin name, schematic body, default reference designator, part name, and description. On the Footprint (Decal) side, it should include the Pads, Assembly information, Silkscreen, Placement Courtyard, and 3D Model. You then construct the full component with the specific part name/description, Parametric Part Information, Sourcing, the models of the schematic symbol, Footprint and sometimes a simulation model.
The other standard is the Review process, which we cover in more detail in part two of this blog.
You have a baseline of what goes into the component and a reference document to verify that information is on the datasheet.
A common practice is to quarantine new components until they go through the review process. In this way, problems do not pass through to your PCB design and especially to your PCB fabricator.
The scope and initial objective of PCB Data Management is to have components created with minimal required items. Secondly, a review of those components for accuracy compared to the datasheet — which involves updating of specific information (dynamic) over time. However, at this point, we have a sound and successful Data Management system.
We now have a realistic expectation of success for our PCB Data Management system. We can, in the words of Zig Ziglar; do “the best we can with what we have.” We’re starting from a strong foundation we can build on from here. Most importantly–it will stand no matter what.
In part two, we’ll see the specifics of how we construct our Data Management using the S.M.A.R.T. rule. Although each system is different in its specific details, the general rules used are the same.
Would you like to find out more about how Altium Designer can help you with your PCB data management? Talk to an expert at Altium and learn more about making sourcing decisions with ease and confidence.