ECN

An ECN, or Engineering Change Notice, is a controlled document used to propose, review, approve, and communicate engineering or design changes to a product, component, or manufacturing process. It is a core element of formal change control in regulated and industrial manufacturing environments.

What an ECN includes

While formats vary by organization, an ECN commonly includes:

• Identification of the affected items (part numbers, drawings, specifications, BOMs, routings, software, tools)
• Current revision and proposed new revision or configuration
• Description of the change and rationale (e.g., quality, cost, performance, obsolescence)
• Impact assessment on form/fit/function, compliance, tooling, documentation, and inventory
• Required updates in related systems (PLM, ERP, MES, QMS, work instructions, FAI/AS9102 records)
• Disposition instructions for in-process and finished product (use-as-is, rework, scrap, effective date)
• Approvals from engineering, quality, operations, supply chain, and other stakeholders

How ECNs are used operationally

In practice, ECNs connect design changes to operational execution:

• Origination and authoring typically occur in PLM or an engineering document control system.
• Once approved, the ECN drives updates to drawings, CAD models, specifications, and BOMs.
• Revisions and effectivity from the ECN are propagated to ERP, MES, and shop-floor systems so that work orders, routings, and digital travelers use the correct version.
• Quality systems reference ECNs when updating control plans, inspection plans, FAI baselines, and AS9102 packages.
• Suppliers may receive ECN notifications so they can transition to the new revision under controlled conditions.

Scope and boundaries

An ECN:

• Covers defined changes to the design definition or engineering-controlled documents.
• Is part of a broader change-control framework that can include related records such as ECOs, deviations, concessions, or waivers.
• Does not by itself guarantee that downstream systems are synchronized; integration and governance are required to align PLM, ERP, MES, and FAI tools.

Common confusion

• ECN vs ECO (Engineering Change Order): Some organizations use ECN and ECO interchangeably. Others distinguish them, for example treating the ECN as the notification/summary of a change and the ECO as the formal order that implements it. Usage is company-specific.
• ECN vs ECR (Engineering Change Request): An ECR typically initiates or requests a change and may be more exploratory. An ECN is usually created once a specific change is defined and ready for formal review and implementation.
• ECN vs NCR/CAPA: Nonconformance and corrective action records address quality issues and their resolution. ECNs may be one of the actions taken to permanently change the design or process in response to issues surfaced by NCRs or CAPAs, but they are different record types.

Ties to drawing and FAI revision control

In environments using PLM and First Article Inspection (FAI) tools, ECNs are often the authoritative mechanism for changing drawing revisions that FAI and AS9102 records reference. Reliable synchronization of part numbers, revisions, and effectivity dates across PLM, ERP, MES, and FAI systems depends on clear ECN governance, consistent keys (part and revision), and well-defined data flows.