Engineering Change Order Management for PCB Assembly

An Ordú um Athrú Innealtóireachta (ECO) is the formal instrument that keeps a product in production consistent with its documentation. Once a PCB program is in pilot or volume, changes cannot travel through email threads and version-less file attachments. Every change to the PCB, BOM, firmware, process, or packaging has to be evaluated for manufacturing impact, approved by the right owners, applied at a defined effective point, and tied to serial or lot records so the resulting units can be traced back to a specific configuration. This article covers how Highleap Electronics processes an ECO from the manufacturing side and what the customer needs to release for the change to be applied without introducing new defects.

1. When an Engineering Change Order Is Required

Not every adjustment is an ECO. Different companies draw the line differently, and Highleap works to the customer’s own change definitions. As a practical baseline, the following changes should go through a formal Engineering Change Order rather than an informal update:

• PCB layout changes that affect copper, drill, silkscreen paste, or board outline — including apparently minor silkscreen edits, because they still generate a new revision
• Layer stackup changes — layer count, dielectric thickness, controlled-impedance targets
• PCB material changes — laminate grade, Tg, halogen content
• Athruithe ar chríochnú dromchla — for example, HASL to ENIG, or ENIG to ENEPIG
• Component MPN changes — even when the electrical function is unchanged, because the physical part and its supply path have changed
• Approved alternate additions or removals
• DNI or DNP changes — components added to or removed from the populated set
• Firmware changes — new release, calibration constants, feature flags
• Test limit changes — tightening or relaxing FCT thresholds
• Assembly process changes — reflow profile, stencil revision, hand-solder sequence
• Athruithe sciath — introduction, removal, or change of coating material
• Label changes — barcode format, regulatory marks, serial-number scheme
• Athruithe pacáistithe — tray to tube, carton dimensions, palletization
• Mechanical interface changes — connector position, mounting holes, keep-outs affecting the enclosure

Distinct from formal engineering change, several other categories exist:

• Temporary deviation. A one-time authorization to build to a variant of the released documents — typically to cover an interim material shortage. Time-boxed and does not become the standard.
• Supplier substitution. A component-level swap within the approved alternates list. If the alternate is not on the list, it is not a substitution — it is an ECO.
• Process adjustment within window. Small tuning of reflow soak or paste volume within the released process window, recorded but not requiring a new revision.
• Documentation correction. Fixing a typo or clarifying a note where the intent is unchanged. Still requires document revision control, but not a design impact review.

The important practice is not the naming convention itself — it is that the customer and Highleap agree on which category each change falls into roimh it is applied.

2. ECO Impact Analysis Across PCB, BOM and PCBA

Every ECO must be evaluated for its manufacturing impact before it is approved. A change that looks small in the schematic can trigger a stencil revision, an ICT program update, and a customer-authorization requirement.

The impact review is what prevents a “small” change from producing an unexpected shipment miss. A component MPN swap can look like a one-line BOM edit and still force a new placement program, a new AOI reference, a new IQC procedure, and a first-article on new material.

3. Managing Old Material, Work in Progress and Finished Goods

The item most often mishandled in an ECO is not the design content — it is the physical inventory around the change. Every ECO has to state what happens to material that already exists at each stage of the flow:

• Old-revision PCBs. Panels or fabricated boards at the previous revision. Options: consume before cutover, scrap, rework where possible, or reserve for spares.
• Old-revision components. Parts that the ECO obsoletes or replaces. Options: consume, return where terms allow, scrap, or transfer to another program that still uses them.
• Obair idir lámha. Boards partially built on the old revision. Options: complete on the old revision if the change is not safety-critical, halt and route to rework, or scrap.
• Finished assemblies. Units already built to the old revision, either in Highleap’s finished-goods stock or at the customer. Options: ship as-is under the old revision, hold pending customer disposition, or rework.
• Field stock. Units already at distributors, integrators, or end users. Options: leave in the field under the old revision, recall for rework, or apply a service ECO the next time the unit is opened.
• Rework path. If reworking old-revision units to the new revision is authorized, the rework procedure is documented and its yield and cost are separately tracked.
• Draimh. Where material must be scrapped, the disposition is written down, quantities are recorded, and the customer explicitly authorizes the write-off.
• Use-as-is. A customer decision to continue using old-revision material because the change is not safety-critical for the affected units. Authorization is written and traceable.
• Re-identification. If old and new revisions look identical, remarking or labeling is required so the shop floor cannot mix them.
• Effective lot and serial number cutoff. The ECO states the last serial or lot at the old revision and the first at the new revision so every unit can be traced to its configuration.

Who authorizes use of old material is a customer decision, not a manufacturing one. Highleap surfaces the options and applies the customer’s disposition; the customer owns the risk of shipping any old-revision units.

4. Updating Manufacturing Files and Production Programs

Once an ECO is approved, the design content is only half the update. Every downstream artifact that references the changed configuration has to be revised in sync — otherwise a “released” ECO produces the wrong output on the line.

• Comhaid déantúsaíochta PCB — Gerber, drill, stackup drawing at the new revision, with prior revision archived
• BB — updated MPNs, DNP list, alternates, and revision number
• Pick-and-place / centroid — regenerated from the new PCB revision so coordinates match
• Líníocht tionóil — polarity, pin-1, DNP, and notes updated to reflect the change
• Scéimreach — released version updated where the change affects net function
• Stionsal — if apertures change, a new stencil is manufactured and the old stencil is retired or clearly marked
• Placement program — machine file updated, referencing the new revision
• AOI program — component library and inspection windows updated for any moved, added, or removed components
• X-ray criteria — updated coverage map if the ECO changes BGA or QFN placement
• Programming file — new firmware image with checksum, previous image archived
• Clár tástála — ICT, FCT, and boundary-scan scripts updated and version-controlled
• Treoracha oibre — visual guides and step-by-step procedures updated at the new revision
• Pacáistiú agus lipéid — regenerated for any change in unit form, weight, or regulatory markings

The specific risk this list closes: an ECO that updates the BOM but not the pick-and-place file will place the new component at the coordinates for the old one. An ECO that updates the Gerber but not the AOI program will flag good boards as defective at inspection. An ECO announced by email but not landed in the file system will produce mixed builds on parallel shifts. The rule is that no ECO is “released” until every dependent file has been updated to the same revision level.

5. First Article and Validation Requirements After an ECO

Not every ECO requires a full re-qualification, and not every ECO can skip one. The right validation depth is decided by the type and risk of the change.

• New PCB first article. Triggered when the ECO changes copper, drill, stackup, controlled impedance, or surface finish. A fabrication first article verifies that the new bare board meets the revised specification.
• Assembly first article. Triggered when the ECO changes stencil, reflow profile, placement program, or introduces a new component package. Produces measurable evidence that the assembly process is producing the intended result on the new revision.
• Reflow profile revalidation. Triggered when the ECO changes board thermal mass, adds a heat-sensitive component, or modifies large ground copper. Measured on a thermocoupled sample.
• X-ray verification. Triggered when the ECO adds or moves BGA, QFN, or LGA components. Confirms voiding and joint quality on the new configuration.
• Functional retest. Triggered when the ECO could plausibly affect functional behavior — firmware update, MPN change on a functional block, calibration change.
• Tástáil aischéimnithí. For firmware ECOs, running the full test suite rather than only the changed feature to confirm nothing else regressed.
• Mechanical fit check. Triggered when the ECO changes connector position, board outline, or component height.
• Compliance retest. Where the ECO could affect certification — a new power stage, changed antenna layout, revised safety-critical component. The customer’s compliance owner decides whether the change requires a new formal test or falls within delta-review provisions.
• Reliability retest. Triggered when material, coating, or high-stress components change. Sample size and test duration are set by the risk, not by a fixed rule.
• Customer approval build. Any ECO where the customer’s own acceptance criteria require them to sign off on physical units before volume resumes at the new revision.

A common mistake is either extreme: revalidating everything on every ECO (which makes the change process too expensive to use) or revalidating nothing (which lets defective ECOs into volume). Highleap proposes the validation scope in the ECO impact review; the customer confirms it before the change is applied.

6. ECO Approval, Effective Date and Traceability

The ECO record is what allows the resulting units to be traced back to a specific configuration months or years later. A complete record includes:

• ECO number — unique identifier
• Cúis — brief statement of why the change is being made
• Affected part numbers — every product SKU affected
• Old revision — the specific document revision being replaced
• Léirmheas nua — the specific document revision taking effect
• Ceaduithe — signatures or system approvals from the responsible owners identified in the impact analysis
• Dáta éifeachtach — the calendar date the ECO becomes the released configuration on the line
• Lot or serial number cutoff — the exact break point between old and new revision units
• Inventory disposition — decisions on old material, WIP, and finished goods
• Torthaí bailíochtaithe — first-article report, functional retest data, compliance sign-off where applicable
• Doiciméid ghaolmhara — updated Gerber, BOM, centroid, firmware, test scripts, work instructions
• Údarú custaiméara — the specific customer approval that released the ECO for production

A release checklist confirms the ECO can go live:

• All impacted files updated and archived at the new revision
• All impacted production programs (SMT, AOI, ICT, FCT, programming) updated
• Fixtures and stencils updated or replaced as required
• Old-revision material dispositioned with customer authorization
• Validation scope executed and evidence attached to the ECO
• Effective date and cutoff serial or lot recorded
• Customer sign-off on file
• Traceability system reflects the new configuration

This record is what a field return, warranty investigation, or regulatory audit will be read against.

7. Submit an Engineering Change for Production Review

Highleap Electronics evaluates ECOs from the manufacturing side — PCB fabrication feasibility, procurement lead time, SMT and THT process impact, inspection and test program updates, and inventory disposition. The customer retains ownership of product design intent, regulatory compliance, and final approval. Where the change originates from a component lifecycle event or supply constraint, procurement can propose alternates through the same ECO channel, subject to customer approval.

To open an ECO review, provide:

• Current revision of PCB, BOM, and firmware
• Proposed revision and description of the change
• Reason for the change (design, supply, quality, compliance, cost)
• Affected files — Gerber, BOM, centroid, assembly drawing, firmware, test scripts
• Affected inventory — old PCBs, components, WIP, finished goods, field stock
• Required implementation date and any hard shipment commitments
• Proposed validation requirement — first article, functional retest, compliance retest
• Customer approval status — pending, conditional, approved
• Whether existing units need to be reworked or can remain at the old revision
• Any related open ECOs on the same program