An internal part number can represent several approved manufacturer parts. That is convenient until the shared approved set changes while an assembly order is being prepared. The released build needs a clear record of which candidates were permitted at its decision point.
MacroFab’s customer part number documentation describes shared approved vendor lists and purchasing precedence. This is one concrete implementation of an alias that points to a changing set of candidates. Review both membership and selection behavior when using such a model.
Separate the alias from the candidates
Record the customer part number and each approved manufacturer identity behind it. Keep complete orderable numbers where packing, grade, or other suffixes affect procurement. A generic value and footprint name are not sufficient to reconstruct the approved set later.
Identify whether approval applies across all designs or only to specified uses. A component that is acceptable in a low-speed indicator circuit may not be interchangeable in another product with different electrical or environmental demands. Shared data should not silently broaden a qualified use.
Capture the release state
| Field | Why it matters |
|---|---|
| Approved set revision | Identifies the candidate list used at release |
| Candidate restrictions | Preserves product-specific conditions |
| Selection precedence | Explains which candidate purchasing may choose |
| Actual supplied identity | Connects authorization with installed material |
Retain a snapshot or another immutable reference to the applicable set. Linking only to the current library entry is insufficient when that entry can be edited. The historical record should survive a later candidate addition, removal, or manufacturer naming change. Include effective dates where the same alias has several approved revisions.
Handle changes while orders are open
- Identify active orders using the affected customer part number.
- Determine which approved-set revision each order uses.
- Assess whether the change should apply to those orders.
- Record any explicit update to their purchasing authorization.
- Capture the actual manufacturer parts consumed.
Removing a candidate from a shared library does not establish what already purchased stock should become. Give affected inventory and open orders an explicit disposition based on the reason for removal. Likewise, adding a candidate should not retroactively imply that an earlier unapproved substitution was authorized.
This review does not replace the engineering work that qualifies an alternate. It preserves the result of that work in a form that survives database changes. The release record should answer both “what could purchasing select?” and “what was actually assembled?” without relying on today’s contents of a mutable library.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist