Engineering Change Management (ECN/ECO) —— From "Just Make the Change" to "Controlled Changes"
Product development and production processes inevitably involve changes. Customer requirements change, supplier materials are replaced, drawings are incorrect, and processes are modified... Every day, companies face various change requests.
However, the gap in change management often determines the maturity of a quality system. Some companies make changes and then realize that upstream and downstream processes haven't been synchronized, documents haven't been updated, and inventory has been scrapped; mature companies, on the other hand, ensure that changes are controlled—each change is closed-loop, traceable, and verified.
1. What is Engineering Change Management?
Engineering Change Management (ECM) refers to the comprehensive control of changes in design, process, materials, and equipment throughout the product lifecycle, following the process of proposing → reviewing → approving → implementing → verifying.
Common change carriers include:
- ECN (Engineering Change Notice): Engineering Change Notice
- ECO (Engineering Change Order): Engineering Change Order
- ECR (Engineering Change Request): Engineering Change Request
The relationship among these is: ECR → review → ECO → execution → ECN (notify stakeholders).
2. Types of Changes: Design Changes and Process Changes
1. Design Changes
These refer to changes at the product design level, including:
- Modifications to dimensions, tolerances, and material specifications
- Adjustments to functional or performance parameters
- Updates to drawings and BOM (Bill of Materials)
- Replacement or addition/removal of components
Design changes typically require cross-departmental reviews (R&D, Quality, Procurement, Manufacturing) to assess the impact on cost, delivery, quality, and reliability.
2. Process Changes
These refer to changes at the manufacturing process level, including:
- Adjustments to process flow or work sequence
- Replacement of equipment, tooling, or molds
- Modifications to process parameters (temperature, pressure, speed, etc.)
- Changes to inspection methods or frequency
Process changes are often overlooked—R&D may change the design without informing production, or production may modify the process without notifying quality, leading to batch issues.
3. Five Key Steps in Change Management
Step 1: Change Proposal and Documentation
The source of the proposal can be any department. The key is to document the change using a standardized change request form, recording the change reason, change content, scope of impact, and urgency.
Step 2: Change Review (CCB)
Establish a Change Control Board (CCB) or designate a review leader to evaluate the change impact from the following dimensions:
- Technical feasibility
- Quality and reliability risks
- Cost impact (rework, scrap, mold changes)
- Delivery impact (inventory consumption, transition points)
- Regulatory compliance
Step 3: Change Approval and Planning
After the review is passed, develop a change implementation plan, including:
- Transition timing (cutover point)
- Handling of old materials/products (consumption, rework, scrap)
- Document update arrangements (drawings, BOM, control plan, PFMEA)
- Training for relevant personnel
Step 4: Change Implementation and Verification
Execute the change according to the plan and perform first article verification—confirm that the changed product meets the requirements. Only after verification can the change be implemented in batch production.
Step 5: Change Closure and Traceability
After the change is completed, update documents, notify all stakeholders, and archive the change record. A good traceability system can ensure that: on a specific date, due to a specific reason, who approved what change, and which batch numbers were affected—everything is traceable.
4. Common Issues in Change Management
- Verbal Changes—Changes made based on a leader's verbal instruction without written documentation, making it difficult to assign responsibility later
- Changes Made Without Review—Assuming small changes don't require review, leading to a chain of issues
- Lack of Cutover Control—Old and new materials coexist on the production line, causing mixing problems
- Delayed Document Updates—Changes have been implemented for half a year, but drawings and BOMs are still outdated
- Failure to Notify Suppliers—Design changes are made, but suppliers continue to supply according to the old drawings
5. Summary
Engineering Change Management is not about being strict but about being correct. An effective change management system ensures that each change is documented, traceable, and verifiable. For quality managers, change management is a crucial tool for preventive quality—rather than troubleshooting after a change, it's better to identify risks before the change.
Change management must be a closed-loop and traceable process
Knowledge Number: 8.4.1
Version: v20260608
Author: Quality Excellence Think Tank