Change Control in Simple Terms
Small changes cause big problems when nobody checks the knock-on effects. A new material, a moved machine or a revised drawing can affect fit, function, the FMEA, the control plan, stock and customer approval. Change control makes sure the right people look at a change before it is released.
How It Works
- Request: someone raises an engineering change request with the reason and proposed change.
- Impact review: engineering, quality, production and purchasing assess effects on parts, BOMs, tooling, stock, documents and customer approvals.
- Approval: a change board or named approvers accept or reject it.
- Release: an engineering change notice communicates what changes and from when.
- Implementation and verification: documents are updated, old stock is handled and the result is checked.
In automotive, many product and process changes need customer notification and sometimes a new PPAP before shipping.
Example
Engineering wants to switch a plastic housing to a cheaper resin. The impact review finds the material appears in three part numbers, one of them a safety part, and that the change needs customer approval. The team runs validation tests, submits a PPAP, sets a cut-in date and uses up old stock before release.
Common Mistakes
- Making informal changes on the shop floor that never reach the drawings.
- Skipping the where-used check.
- Releasing a change without telling the customer when required.
OperaHive engineering change management handles change requests and notices, BOM revisions, approvals and impact reviews.