Engineering Change Management (ECM) is the discipline of managing product-design changes through their lifecycle — from initial change request through impact analysis, approval, implementation and verification. For manufacturing-centric DACH organisations producing variant-rich products (machinery, automotive supply, medical devices, industrial equipment), engineering changes occur frequently and ripple through BOMs, routings, supplier specifications and customer commitments. Disciplined ECM is the difference between manageable evolution and operational chaos.
ECR and ECO workflow
The two-stage ECR/ECO pattern is standard. ECR (Engineering Change Request): initial proposal for a change, with rationale, scope estimate, preliminary impact analysis. Reviewed by engineering management for technical feasibility and by commercial functions for cost-benefit. ECR approval authorises the next-stage detailed work. ECO (Engineering Change Order): detailed change definition with affected items, replacement parts, effectivity rules, validation requirements, cost-impact calculation. Reviewed by cross-functional CCB (Change Control Board) representing engineering, manufacturing, purchasing, sales, quality, regulatory and finance. ECO approval authorises implementation. Closure happens after the change is implemented in BOMs, supplier specifications and customer documentation, with audit-trail evidence retained.
Impact analysis
Engineering changes cascade through multiple data structures and stakeholders. Comprehensive impact analysis covers: (1) BOM impact — which products include the affected part, in which quantity, at which level. (2) Inventory impact — existing stock of the old version, work-in-process orders, in-transit material. (3) Supplier impact — open POs, contracted supply, tooling investment. (4) Customer impact — products in customer hands, warranty obligations, regulatory submissions. (5) Documentation impact — operating manuals, technical data sheets, regulatory filings, training materials. (6) Cost impact — standard cost change, transition cost, obsolescence write-off. Modern PLM tools (Teamcenter, Windchill, 3DEXPERIENCE) and ERP-side change-management modules support automated impact analysis across these dimensions.
PLM-ERP integration
Engineering changes originate in PLM (Product Lifecycle Management) and propagate to ERP. The integration is one of the most consequential touchpoints in any manufacturing IT landscape. Standard flow: (1) Engineer initiates ECR in PLM (Teamcenter, Windchill, 3DEXPERIENCE, Aras). (2) Impact analysis runs in PLM with PLM-side BOM data, integrated with ERP for transactional impact (inventory, open orders). (3) Approved ECO triggers BOM update in PLM (eBOM — engineering BOM). (4) PLM pushes the BOM change to ERP with defined effectivity date and serial-number range. (5) ERP updates its mBOM (manufacturing BOM), planning logic accommodates the change, purchasing adjusts orders. (6) Implementation evidence flows back to PLM for change-closure documentation. Pre-built connectors exist for major PLM-ERP combinations; custom integration is common in heterogeneous landscapes.
Regulated-industry rigour
In regulated industries (medical devices under MDR, pharma under GMP, automotive Tier-1 under IATF 16949), ECM is not just operational discipline but regulatory obligation. Required documentation: design history file, change-control records, validation evidence, regulatory-impact assessment, notified-body or competent-authority notifications where applicable. Implementation typically requires re-validation of affected processes and quality systems. The change-implementation timeline extends substantially — what might be a 4-week ECO in a consumer-product manufacturer can be a 6-12 month regulatory exercise in pharma manufacturing. ERP and PLM tools serving regulated industries (SAP S/4HANA Pharma, Siemens Teamcenter Medical, MasterControl eQMS) include the rigorous change-control workflows natively.
For simple products with stable BOMs, ERP-only ECM can suffice. For variant-rich products, multi-CAD environments, or regulated industries, PLM-driven ECM with integrated ERP propagation is the standard. The threshold: above 50 BOMs or 100 monthly changes, PLM-based ECM typically pays back.
How long should an ECO take?
Highly variable. Simple changes in consumer-product environments: 1-2 weeks. Complex changes in machinery: 4-12 weeks. Regulated-industry changes (medical devices, pharma): 3-12 months including validation. The right timeline depends on impact scope and regulatory regime.
What is the relationship between ECM and configuration management?
ECM manages design changes to products; configuration management manages changes to IT systems and infrastructure. Both follow similar workflow patterns (request, approval, implementation, verification) but operate on different domains. Mature engineering organisations distinguish them clearly to avoid scope confusion.
