Engineering Change Order (ECO)

Engineering Change Order (ECO) is the data object that authorizes a specific change to released engineering data — typically following an ECR (request) and preceding the ECN (notice). It carries the technical detail, impact analysis, approvals, and effectivity that make a change real in the configuration baseline.

What it covers

• Change description and rationale with linked problem reports and ECR.
• Impact analysis across parts, BOMs, drawings, tools, and certifications.
• Approval routing through the Change Review Board with role-based signoffs.
• Effectivity rules — date, unit, lot, or serial-number based.
• Implementation actions — revision bumps, BOM edits, document re-releases.

Relationships (see sidebar)

• Supports the Change Management (ECO/ECN), Configuration Management, and Release Management processes.
• Implemented by PLM platforms including Siemens Teamcenter, PTC Windchill, Aras Innovator, Oracle Agile, and SAP PLM.
• Paired with the Engineering Change Notice (ECN) data object.