What “aligned” actually means
In an aerospace manufacturing package, a PFMEA and a Control Plan are aligned when a person can take a high-risk failure mode and find the matching prevention or detection control, method, frequency and reaction on the Control Plan — against the same process step, the same characteristic, and the same revision of the process.
If the PFMEA still describes the old fixture, the old inspection frequency, or a characteristic that the new drawing deleted, the package is not aligned. The documents can each look complete and still fail a customer review.
Where drift starts
Engineering change is the usual trigger. A revision adds a diameter, tightens a profile, moves a hole, or changes a material callout. Production may already be running the new revision under a red-line or a shop-floor note while Quality is still working from the previous Control Plan.
Typical break points:
- The routing gained or lost an operation and the Process Flow was updated, but the PFMEA operation numbers were not.
- A special characteristic was added on the drawing and flowed into inspection, but never into the PFMEA severity or classification columns.
- Detection moved from first-article layout to in-process gauging and the Control Plan frequency changed while the PFMEA detection ranking did not.
- Outside processing was added (heat treat, NDT, special process) and only the purchase order was revised.
- A reaction plan was rewritten for containment, but the Control Plan still says “notify supervisor.”
What a reviewer will do with the package
A customer quality engineer or an AS9100 auditor does not read these documents as literature. They pick a key characteristic and walk it: drawing note → process step → PFMEA row → Control Plan row → inspection record → reaction. One broken link is enough.
They will also check dates and revision letters. A Control Plan dated after the engineering change, sitting next to a PFMEA that still carries the previous change notice, is a finding waiting to be written.
A practical alignment pass after a change
Work the change as a set, not as separate assignments:
- List every characteristic and process step the change touches, including outside processing.
- Update the Process Flow first so operation numbers stay stable.
- Revise the PFMEA rows for those operations — failure modes, causes, current controls, rankings if the control actually changed.
- Revise the Control Plan so each revised risk has a method, sample size or frequency, and a reaction that a person on the floor can execute.
- Check work instructions and the inspection plan against the same list.
- Record the engineering change number on every document you touched.
If the existing team does not have hours this week, that is a capacity problem, not a template problem. An alignment review exists specifically to produce the gap list and the corrected documents together.
When to stop and request a full rewrite
If more than a handful of operations moved, if special processes were added, or if the Control Plan and PFMEA were built years apart by different people, a row-by-row patch will take longer than a controlled rewrite against the current routing. Starting rates for both paths are on the pricing page.