Issue link: https://resources.pcb.cadence.com/i/1545418
Role-Based Access Role Permissions Designer Search and select approved parts, submit part requests, use temporary parts during NPI review Librarian Add and edit parts, initiate NPI, review part requests, approve standard additions Senior Librarian / Administrator Approve NPI for high-risk or new-supplier parts, modify schema, bulk import/delete, manage permissions Procurement / Supply Chain View supply chain and purchasing data, export BOMs, read-only access to component records External Partners (CM, ODM) Read-only access to approved component data via controlled web portal The key principle is that approval authority is separate from request authority. Designers request, librarians add, adminis- trators approve and govern. No single person should be the sole path for every action. Distributing Workload Without Distributing Risk In larger organizations, a single librarian managing all NPI for a high-volume design team is not sustainable. Options for distributing workload without compromising governance: f Designate a librarian per product line or business unit, each with authority to approve parts within their domain f Create a tiered approval process where low-risk additions such as a standard resistor from an approved manufacturer in a standard package require only librarian sign-off, while new suppliers, new component families, or high counterfeit-risk categories require senior review f Use the NPI workflow to distribute review tasks with defined turnaround expectations so that request owners know when to expect a decision Required Fields as a Governance Mechanism When new components are added to the database, required fields guarantee that a part record is complete before it is visible to designers. Define the minimum set of fields that must be populated before a part can be approved. This is a governance control, not a recommendation. An incomplete part record that reaches designers is indistinguishable from a complete one unless the library enforces completeness at the point of entry. History and Revision Tracking Detailed history and revision tracking allows review of component modifications including the fields changed, the modification date, and the user who made the change. If an incorrect change is made to the database, revision tracking makes it possible to determine where the error was introduced, who made it, and what the previous value was. This is as important for compliance audit trails as it is for day-to-day quality control. 12. Connect the Library to the BOM The library is the upstream source of BOM data. If the connection between the library and the BOM is a manual export and re-entry process, errors accumulate at every transfer point. Part numbers get transposed. Distributor information goes stale between the time the BOM is compiled and the time procurement acts on it. Compliance data verified in the library does not reliably make it into the BOM that goes to the factory. After the BOM is submitted, it must be reviewed and either accepted or rejected by procurement based on: part quantity, availability, lead time, cost, distributor information, manufacturer information, part status, and compliance. If the library data is complete and current, BOM generation should be a direct export, not a manual compilation process that reintroduces the errors the library was built to prevent. 16 www.cadence.com Managing Your Component Library for Supply Chain Resilience