4.2 Change control and revisions

In hardware manufacturing, the only operational threat more dangerous than a bad design is an ambiguous one. “Continuous Improvement” is a noble engineering goal, but uncontrolled, undocumented change is a significant operational risk. Once the Data Freeze is locked at the end of the Virtual Build, you can never simply email the factory line manager to say, “Hey, let’s swap R5 for a 20k resistor.” That email creates an immediate, major synchronization gap between your engineering documentation, the procurement team’s purchase orders, and the SMT machine programmer’s raw files.

Engineering Change Orders (ECOs) are the formally governed mechanisms required to break the freeze safely. Without a formal ECO process, you are not mass-producing a product; you are managing an unstructured collection of random science experiments.

The vocabulary of change: ECN vs. ECO

Operational precision is required. Never confuse a technical request with a financial order.

1. ECR / ECN (engineering change request / notice)

• The Definition: The Proposal. “We found a thermal bug in the field. We recommend changing C4 to 10uF.”
• The Status: Pending. No physical action is taken on the production line. An ECN is merely a signal for management to pause and thoroughly evaluate the business impact (raw component cost, scrapped WIP, schedule delays).

2. ECO (engineering change order)

• The Definition: The Executive Directive. “Proceed immediately with the change. Update the BOM to Revision B. Quarantine and scrap all old material.”
• The Status: Active. The factory floor is now officially authorized to spend money, dispose of old inventory, and alter the manufacturing process.
• The Rule: A valid ECO must carry two explicit signatures: Engineering (Technical Approval that the fix works) and Operations (Financial Approval of the schedule delay and scrap cost).

The revision label: the hardware DNA marker

Every physical change must trigger a permanent revision advancement. A board built today must be instantly distinguishable from a board built yesterday when a single piece of silicon or copper was altered.

The revision rules

• The Trigger: When the Form, Fit, or Function of the assembly changes in any way, the Revision letter must increment (e.g. Rev A explicitly becomes Rev B).
• Copper Changes: When altering the PCB copper routing, the bare board part number and the top-level assembly part number must both update.
• Firmware Changes: When only a firmware payload changes, the top-level assembly part number updates, but the underlying bare board part number remains identical.

The implementation strategy: “cut-in” timing

An ECO does not just specify what you are changing; it heavily influences when you change it. Timing directly impacts your financial scrap cost.

1. Running change (use up stock)

• The Logic: The old component works perfectly fine, but the newly qualified component is 10% cheaper or slightly more efficient.
• The Action: “Use up the remaining 5,000 units of the old resistor currently sitting in the warehouse, then smoothly switch to the new one.”
• The Risk: Very low. This systematically minimizes scrapped inventory.

2. Hard cut / mandatory purge

• The Logic: The old component creates field failures or presents a safety hazard. It is highly detrimental to the business.
• The Action: “Stop the SMT line right now. Unload all old parts from the feeders. Dispose of the unused reels. Install the new parts immediately.”
• The Risk: Significant financial cost (scrapped material) and severe line downtime.

3. Next build

• The Logic: The change is a minor optimization for the future, but not worth disrupting the current run.
• The Action: “Update the BOM exclusively for the next Purchase Order next quarter. Do not touch or modify the current Work In Progress (WIP).”

The “mixed build” nightmare

The ultimate failure of any factory change control system is the Mixed Build: accidentally shipping pallets of units that are a confusing mix of half-Rev A and half-Rev B hardware.

The problematic scenario

You issue an urgent ECO to change a microcontroller. The factory dutifully updates the Pick & Place machine file but completely forgets to remove the older reels sitting in the warehouse.

• The Result: The SMT machine loads the old silicon reel. At the end of the line, the test station flashes the newly compiled firmware requiring the new chip architecture. The device instantly fails.
• The Rule: Failing to quarantine and permanently scrap the old material from the building ensures it will eventually find its way back onto the SMT line.

Pro-Tip: Never rely on manual, visual ECOs for mass production. When an ECO requires a human technician to manually solder a green jumper wire across 1,000 finished boards to fix a broken trace, it intentionally introduces 1,000 new opportunities for human error and vibration failure. Accept the financial hit, scrap the bare boards, and respin the PCB design.

Final Checkout: Change control and revisions

Action Step	Primary Responsibility	The Critical Rule
Draft the ECN	Engineering Team	Explicitly define the “From” (Old) state and the “To” (New) state with zero ambiguity.
Approve the ECO	Operations Manager	Thoroughly verify the exact “Cut-In” date and authorize the financial scrap cost.
Update Documents	Document Control	Increment the Revision letter (e.g. A → B) natively on both the BOM and the Schematic.
Purge the Line	Quality Assurance	Walk the floor and remove all old parts from the building.
Verify Implementation	Quality Assurance	Carefully inspect and test the first 5 physical units of the new Revision (First Article Inspection).