1.2 The Bill of Materials & Revision Control

The Bill of Materials (BOM) is often misunderstood by hardware startups. It is not merely a purchasing list or a rough estimate of parts. It is the primary driver for SMT machine programming, supply chain MRP logic, ERP consumption rules, and product cost accounting.

In the Golden Data Pack (GDP), the BOM functions as Master Data. When the BOM is ambiguous, the production line pauses. The BOM must be treated exclusively as a deterministic database export, never as a casual Excel spreadsheet. Perfect machine-readability and 100% synchronization with the physical CAD design are mandatory.

The Component Identity: MPN is King

The Manufacturer Part Number (MPN) is the single, undisputed valid identifier for a physical component. Internal part numbers (IPNs) or generic text descriptions are insufficient for manufacturing. They require a human to perform translation, which introduces a high chance of human error at scale.

The Data Hierarchy:

1. Primary Key: Manufacturer Part Number (MPN).
2. Validator: Manufacturer Name (Must perfectly match the exact spellings registered to the MPN).
3. Reference: Component Description (e.g., “RES 10k 1% 0402”).
4. Locator: Reference Designators (RefDes) (e.g., R1, R2, R3).

Intake Standards:

If a BOM lists a generic “10k Resistor” without an exact MPN, the required wattage, tolerance, voltage rating, or thermal coefficient for the RF circuit cannot be determined, resulting in rejection. If the Description conflicts with the MPN (e.g., the Description says “10k” but the MPN resolves to a “100k” part), this creates a critical data failure requiring engineering intervention. The MPN legally takes precedence.

AVL Strategy: Approved Vendors & Alternates

Supply chain resilience relies on pre-validated alternates. However, writing “Or Equivalent” in a BOM cell is not an engineering specification—it introduces ambiguity and significant risk.

Defining Alternates

Leaving alternate component selection to the discretion of a purchasing agent during a parts shortage is prohibited. Alternate MPNs must be explicitly defined in the GDP.

• The Explicit Method: Dedicated columns must be added to the database for “Alt_1_Mfr”, “Alt_1_MPN”, “Alt_2_Mfr”, etc.
• The Standard Method: When the part is purely a commodity (e.g., a standard 10k pull-up resistor), reference a controlled “Internal Standard Specification” that maps to EMS house stock (e.g., “Must meet Spec 100-001: 0402 Resistor, 1%”).

Tip

Pro-Tip: The phrase “Or Equivalent” is prohibited for components such as MLCC capacitors, MOSFETs, or inductors.

DC bias characteristics, ESR, and saturation currents vary wildly between manufacturers despite matching top-line voltage and capacitance.

Managing DNP (Do Not Populate)

“Do Not Populate” (DNP) or “Do Not Install” (DNI) components must be explicitly managed within the database to prevent manual placement errors, ghost placements, and false-failure reports blocking the line at Automated Optical Inspection (AOI).

Rules for Managing DNP Components:

1. Explicit Status: The BOM must contain a dedicated column labeled “FITTING_STATUS” (or similar).
2. Binary Values: Exactly “FITTED” must be used for populated parts and “DNP” (or “NO_FIT”) for unpopulated parts.
3. No Silent Deletions: Silently deleting DNP rows from the BOM export is prohibited. If component R5 is physically present in the schematic but missing from the BOM file, a data export failure is assumed. If a RefDes exists in CAD, it must also exist in the BOM (explicitly marked DNP).

Revision Control: The Three Essential Artifacts

A valid, operational manufacturing build requires the perfect alignment of three artifacts. When these revisions are not locked in sync, the data pack is invalid (referred to as a “mixed-revision pack”).

The Synchronization Mandate

The Project Revision code (e.g., “REV_05”) must be clearly labeled on:

1. The BOM Header: Dictating exactly what parts to buy.
2. The PCB Fabrication Data: Dictating exactly the physical copper geometry.
3. The Assembly Drawing: Dictating the visual placement and polarity instructions.

Scenario ⭢ Action:

If the BOM is “Rev B” but the Gerber dataset is “Rev A”, the build is stopped immediately. There is an unacceptable risk that footprint locations (X,Y) in the old bare-board do not match the physical dimensions of the new component packages specified in the new BOM (e.g., the footprint is purely 0603 but the BOM demands an 0402 part).

ECO Cut-Ins & Running Changes

An Engineering Change Order (ECO) issued rapidly after the Gerber Data Package (GDP) release must follow a strict operational “Cut-In” logic to preserve factory traceability.

Cut-In Strategies:

• The Clean Break (Highly Preferred): The ECO triggers a fast, full roll to a new GDP Revision (Rev A ⭢ Rev B). All old stock is purged, quarantined, or physically scrapped.
• The Running Change: The ECO is injected into the current Work In Progress (WIP) build based on a clear logic gate.
  • By Serial Number: “Apply ECO-101 starting at Unit SN #5000.”
  • By Date Code: “Apply ECO-101 for all bare boards assembled after [Date].”

Tip

Pro-Tip: “Use Up Stock” dispositions for critical signal integrity or power-path components are prohibited.

This practice creates a fleet of mixed-performance devices in the field, severely complicating future debugging.

---

Recap: Bill of Materials & Revision Control

Parameter	Requirement	Value / Condition	Action / Document
Component Identifier	MPN is the sole valid identifier.	MPN must be specified. Description must not conflict with MPN.	Reject BOM if generic description only. BOM is master data.
Alternate Components	Explicitly defined alternates required.	Prohibit “Or Equivalent”. Define Alt_Mfr/MPN columns or reference internal spec.	BOM must list pre-validated alternates.
DNP Management	Explicit FITTING_STATUS for all RefDes.	Column values: “FITTED” or “DNP”. Do not delete DNP rows.	BOM must include all CAD RefDes.
Revision Synchronization	BOM, PCB Fab Data, Assembly Drawing revisions must match.	Single Project Revision code (e.g., REV_05) across all three artifacts.	Stop build immediately if mismatch.
ECO Implementation	Changes managed via formal ECO.	Preferred: Clean break to new GDP revision. If running change, define by Serial Number or Date Code.	Prohibit “Use Up Stock” for critical components. ECO document required.