5.1 Engineering change management (ECM)

Uncontrolled variation is the primary driver of manufacturing failure. In an electronics manufacturing environment, a modification to a Bill of Materials (BOM), a Gerber file, or a firmware version without a synchronized propagation path results in revision mismatches, stranded inventory, and functional failure at the test bench. Engineering Change Management (ECM) functions not as a bureaucratic hurdle, but as the synchronization gear between design intent and physical assembly. It ensures that every unit produced matches a validated configuration, preventing the silent drift of product specs.

Change classification and intake

Incoming change requests must be categorized immediately to determine the propagation scope. Misclassification leads to either unnecessary administrative overhead or, more critically, unapproved modifications reaching the customer.

Change classification framework:

• Changes affecting Form, Fit, Function, or Reliability (3FR) must be classified as a Major Change / PCN. Mandatory Customer Approval is required before purchasing new materials or updating tooling.
• Changes that are purely internal process improvements, corrections of typos, or equivalent component sourcing updates (AVL expansion) with no 3FR impact are classified as a Minor Change / ECN. Notification to the customer may be required, but approval is automatic upon internal validation.
• Changes addressing a safety fix or a critical failure in the field are classified as an Emergency ECN, requiring immediate cut-in and bypassing of standard lead times.

Pro-Tip: When in doubt, default to PCN. It is safer to over-communicate a process tweak than to explain a “silent” component swap that caused a field failure.

Impact analysis: the physics of change

Before approval, the “blast radius” of the change must be calculated. A simple capacitor value change impacts procurement, stock handling, and pick-and-place programming.

Assess the following vectors:

1. Inventory (WIP & Stock): Determine disposition of existing parts.
   • Use-As-Is: Low risk. Consume old stock before switching.
   • Rework: Feasible for high-value sub-assemblies? Calculate labor vs. scrap cost.
   • Scrap: Mandatory for reliability risks. Quarantine immediately.
2. Tooling & Test: Does the change require a new stencil, wave solder pallet, or ICT fixture modification?
3. Documentation: Update BOM, Assembly Drawings, and Work Instructions simultaneously. Divergent documentation causes operator error.

Disposition strategy:

• Scrap the old revision if the Cost of Scrap is less than the Cost of Rework.
• Implement a Running Change (consuming the old stock first) for backward-compatible changes.
• Implement a Hard Cut (forcing the new revision effective immediately) for changes that are NOT backward compatible.

Approval and execution workflow

The ECN/PCN workflow authorizes the factory to alter the build standard.

1. Draft: Engineer defines the change, reason code, and proposed effective date.
2. Review: Cross-functional gate (Quality, Purchasing, Production).
   • Quality: Verifies validation plan (First Article Inspection required?).
   • Purchasing: Confirms component availability and lead time.
   • Production: Checks line capacity and tooling readiness.
3. Approval: Customer signs off (for PCN) or Engineering Manager signs off (for ECN).
4. Release: ERP system updates. BOM revision increments.

Pro-Tip: Do not approve an ECN without a confirmed “Effective From” date or serial number. An open-ended approval results in hybrid builds where the factory floor decides when to switch.

Effective date control and revision segregation

The physical implementation of a change must be tied to a specific boundary to ensure traceability.

Segregation protocols:

• Lot Segregation: Do not mix revisions within a single shipping lot. If a partial run is old revision and the remainder is new, pack and label them separately.
• Labeling: Update the revision letter on the PCB label or device housing immediately upon cut-in.
• System Lock: Block the old BOM in the ERP system to prevent accidental re-ordering of obsolete components.

Transition execution:

• Running Change Method: Implement FIFO (First In, First Out) controls, switching the line to the new component only when the bin of the old component is completely empty. This carries a high risk of mixing if bins are not cleared rigorously.
• Date/Serial Cut-in Method: Halt production, purge the line of old parts, load new parts, and flag the first unit for FAI. This incurs line downtime but offers high control.

Final Checkout: Engineering change management (ECM)

Control Point	Metric / State	Non-Negotiable Rule
BOM Revision	Matches ERP	Production must never build to a “Redline” or draft document.
Disposition	Defined (Scrap/Use)	Explicit instruction for old parts is mandatory. No ambiguity.
Cut-In Point	Date or Serial #	Must be traceable. “Next Build” is not a valid date without a schedule.
Validation	Pass/Fail	Major changes require First Article Inspection (FAI) report approval.
Customer Notice	Ack / Signed	PCN requires written customer acknowledgement before implementation.