Engineering Change Request (ECR)

Engineering Change Request (ECR) is the data object that captures the intent to change released engineering data — the problem, the proposed change, and a preliminary impact assessment — before it is formally authorized. It is the upstream sibling of the ECO: ECRs propose, ECOs authorize, ECNs announce.

What it covers

• Problem statement and rationale — the customer issue, defect, regulatory finding, or improvement that triggers the request.
• Proposed change — affected items, scope, and expected outcome.
• Preliminary impact — schedule, cost, certification, and supply-chain implications.
• Routing for evaluation — typically reviewed by a Change Control Board before promotion to ECO.
• Linkage downstream — an approved ECR becomes (or generates) one or more ECOs.

Relationships (see sidebar)

• Conforms to ISO 10007 for configuration management.
• Supports the Change Management (ECO/ECN) and Quality Management processes.
• Implemented by PLM platforms including Siemens Teamcenter, PTC Windchill, Aras Innovator, and PTC Arena.
• Pairs with ECO (downstream) and ECN (broadcast).