ECR in Simple Terms
Anyone can spot a reason to change a design: a customer, a production supervisor, a supplier or a quality engineer. The ECR is how that idea enters a controlled change control process instead of being made informally. It is the first step; once approved, the change is released with an engineering change notice.
How It Works
- Raise: describe the problem or opportunity and the proposed change.
- Assess impact: affected parts, assemblies, tooling, stock, cost, timing and customer approval.
- Review: a change board of engineering, quality, production and purchasing discusses it.
- Decide: approve, reject or send back for more information.
- Release: approved changes move to an ECN.
A where-used analysis is a key part of impact assessment, because one part may appear in many assemblies.
Example
Assembly operators report that a cover screw is hard to reach. A manufacturing engineer raises an ECR to move the screw boss 5 mm. Impact review shows a tooling change, a DFMEA update and a customer notification. The board approves it, and an ECN releases the new drawing revision.
Common Mistakes
- Skipping the impact check on stock, tooling and other assemblies.
- Approving changes without updating FMEAs and control plans.
- Forgetting customer notification where it is required.
OperaHive engineering change management manages change requests, approvals and impact reviews across parts, documents and production orders.