Engineering Change Order
An Engineering Change Order is the formal, audited record of an approved change to a product design. In PDM, changes are informal — just new file revisions. In PLM, ECOs follow a three-stage governed flow: Engineering Change Request (the problem), Engineering Change Notice (the proposed solution with impact analysis), and finally the ECO (authorization to implement with effectivity dates and affected serial numbers). ECOs create an auditable trail required by regulated industries and supply-chain accountability.
Why it matters
Change is the most-litigated process in any manufacturing company, and the ECO is the artifact regulators, auditors, and customers reach for first when something goes wrong. Without governed change, every downstream system — manufacturing, service, regulatory — is operating on assumptions. The ECR/ECN/ECO terminology is universal across PLM vendors and across industries; the difference between a mature PLM deployment and an immature one is not the existence of ECOs but whether they are routed automatically, signed electronically, and tied to specific effectivity rather than filed in a SharePoint folder after the fact.
Related concepts
External References
This term appears in
- Managing Product Variants in PLM: A Platform BOM Implementation Guide
- What is Impact Analysis in PLM?
- Enterprise PLM Rollout: How Large Manufacturers Deploy at Scale
- What is PLM Governance?
- PLM and Supply Chain Integration: A Phased Implementation Guide
- What is Configuration Management in PLM?
- PLM vs PDM: What's the Difference, and Which One Do You Actually Need?
- Engineering Change Management in PLM: Process, Tools, and Best Practices
- What is Revision Control in PLM?
- What is PLM? A Plain-English Definition for 2026
Cite this definition
Finocchiaro, Michael. “Engineering Change Order.” DemystifyingPLM PLM Glossary, 2026, https://www.demystifyingplm.com/glossary/engineering-change-order-eco