Issue link: https://resources.pcb.cadence.com/i/1545418
Required Supply Chain Fields The following fields should be treated as required, not optional, at part creation: Lifecycle and Compliance Availability and Sourcing Part status (Active / NRND / LTB / Obsolete / Discontinued) Minimum lead time (weeks) Lifecycle risk rating (Low / Medium / High) Maximum lead time (weeks) Predicted years to end of life Quantity on hand Date of last lifecycle review Minimum order quantity Compliance: RoHS Multi-source available (Y/N) Compliance: REACH Approved alternate MPNs Compliance: Conflict Minerals Distributor part numbers Compliance: Halogen-Free (if required) Date of last availability review Counterfeit risk rating Sourcing restriction (franchised only / open market) The field table above defines the schema. How to interpret and act on each of these fields at the point of part selection is covered in Section 9. Schema Design Principles f Make supply chain fields required at part creation, not optional. An empty counterfeit risk field is not neutral. It is unknown, which is itself a risk state. f Use controlled vocabulary for status fields. Active, NRND, Last Time Buy, Obsolete, and Discontinued should be standardized terms, not free text that varies by whoever added the part. Standardized lifecycle states make the data reportable, searchable, and queryable across the entire component library, enabling automated supply chain analysis, BOM health reporting, and lifecycle risk identification. f Separate the date a field was last updated from the field value itself. A compliance status entered three years ago is a different risk than one verified last quarter. f Define the authoritative source for lifecycle and risk data. A lifecycle status pulled from SiliconExpert or a comparable aggregator that tracks market signals carries different weight than one entered manually from a datasheet. f Design the schema for growth. Establish additional fields that can be utilized in the future, since required fields for components may change as design complexity, regulatory requirements, and simulation needs evolve. f Create a standard part numbering convention with a prefix per component type and a standardized allocation of digits for the numerical portion, for example RES-00000001. Use a system that automatically increments part numbers to eliminate duplicates and keep the database in sync. Note: A system that will automatically increment your part numbers is the best way to eliminate duplicates and ensure everything stays in sync. Customizable Tables and Views The information designers need to review for part selection may change over time and varies by project type. Ensure the tables and views in your component database are customizable so that users can surface what is relevant without recon- structing filters every session. Saved search configurations for commonly used part sets, for example RoHS-compliant active 0402 resistors, should be defined for reuse and made available across the team. 6 www.cadence.com Managing Your Component Library for Supply Chain Resilience