Closed-Loop Quality

How to Link 8Ds and Customer Complaints Back to the PFMEA

Tacit AI · · 8 min read
LinkedIn

The 8D for last month’s customer complaint is closed. Containment held and the corrective action is on the line. Then you open the PFMEA for that operation: the same causes and ratings as at launch, and no trace of the 8D.

This guide is for the Director of Quality or customer quality manager who wants to close the loop between the PFMEA and real customer failures. It covers what the standards expect, why the loop breaks, the 3 steps that close it, and the 3 numbers that prove it.

The short version

  • Make D7 the FMEA step: no 8D closes without the PFMEA row and control plan line it changed.
  • Map each complaint to the effect, failure mode and cause the PFMEA uses. Add a row when none exists.
  • Re-rate occurrence and detection for what the process did, not what the row assumed.
  • Read across to every similar part, line and plant, with an owner and date per item.
  • Track 3 numbers: closed 8Ds with a linked FMEA change, days to update, and repeats.

What D7 and IATF 16949 Expect After an 8D

Both expect the 8D to change the system, and the PFMEA and control plan to show it.

  • IATF 16949 clause 10.2.3. Problem solving must include “implementation of systemic corrective actions, including consideration of the impact on similar processes and products”. It must verify their effectiveness. It must also cover “reviewing and, where necessary, updating the appropriate documented information (e.g., PFMEA, control plan)”. The SMMT Industry Forum guidance on IATF corrective actions quotes the clause in full.
  • IATF 16949 clause 8.5.1.1. Review the control plan when you find you shipped nonconforming product, and after a customer complaint and its corrective action, when applicable.
  • Global 8D, D7. Ford’s Global 8D definitions were filed with NHTSA in 2024. D7, Prevent Recurrence, reads: “Modify the necessary systems, including policies, practices, and procedures, to prevent recurrence of this problem and similar ones.”
  • The D7 checklist. The SMMT guidance spells it out: review similar products and processes, assure FMEA updates have been completed, assure control plans have been updated.

Your customer may set its own 8D format and D7 evidence. Ask for both in writing.

Why 8Ds Close Without Touching the PFMEA

The 8D has a deadline and an owner. The FMEA update has neither.

  • Different owners. The 8D team forms around the complaint. The PFMEA owner is often not on it.
  • Different systems. The 8D lives in a customer portal or a CAPA tool. The PFMEA lives in Excel, APIS IQ or PLATO.
  • Different words. The 8D describes a symptom. The PFMEA describes failure modes and causes per process step. Nobody owns the translation.
  • A checkbox, not a link. “FMEA updated: yes”, with no row number and no revision.
  • A frozen document. Teams treat the PPAP version of the PFMEA as released and avoid reopening it.

Step 1: Map the Complaint to the Failure Mode and Cause

Translate the 8D into the PFMEA’s words, then find the row. The 8D gives you a symptom, a root cause and an escape point.

  1. Effect: what the customer saw, at the level they saw it: end user, vehicle or assembly line.
  2. Failure mode: what your part did wrong, at which operation. “Latch height below specification at operation 30”, not “connector does not lock”.
  3. Cause: the verified root cause from D4, at the process step where it happened.
  4. Detection: the escape point from D4, the control that should have caught the part.

Then find the row. There are 4 outcomes:

  • The row and the cause exist. Update the controls and ratings in Step 2.
  • The cause is missing. Add it under the failure mode.
  • No row covers the failure. Add the failure mode, the cause and the controls. This is the gap the 8D found.
  • The cause sits outside the PFMEA. In the design, the equipment or a supplier’s process. Send it to that owner and link both records.

Write the 8D number on the row and the row number on the 8D. That 2-way link is your D7 evidence.

Step 2: Re-Rate Occurrence and Detection From the Evidence

Rate what the process did, not what the row assumed.

  • Occurrence. In AIAG-VDA, PFMEA occurrence weighs process experience and the prevention controls. If the prevention control did not prevent the cause, its rating no longer holds.
  • Detection. The escape point is the detection control that failed. Rate it for what it caught.
  • Severity. If the effect the customer saw is worse than the row says, raise the severity and tell the DFMEA owner.
  • After the fix. Re-rate once the new controls are verified on production parts. Then recheck the Action Priority with the RPN and Action Priority calculator.
  • The control plan in the same change. Every new control gets its control plan line and reaction plan. The work instruction follows.

Step 3: Read Across to Similar Parts, Lines and Plants

Read-across is a list with an owner and a date per item. Close it before the 8D closes.

Check 5 places:

  • The same part on other lines and shifts.
  • Other parts on the same process, machine type or tool family.
  • Other plants that run the process or copied the PFMEA.
  • The DFMEA, if other programs share the design.
  • The master or foundation FMEA that new programs start from.

Each item ends as changed, not applicable with a reason, or open with a date.

3 Numbers That Show the Loop Is Closed

Measure the link, not the activity. Pull 3 numbers each month from the 8D log and the FMEA revision history.

  • Linked share. Closed 8Ds with a PFMEA row number and revision, divided by all closed 8Ds. The target is all of them.
  • Days to update. Median days from 8D closure to the PFMEA and control plan revision. 0 or less means the update landed by closure.
  • Repeats. New 8Ds on a failure mode and cause an earlier 8D already closed. See why the same failure comes back.

Report them by plant and by customer.

8Ds closing without touching the PFMEA?

Get the 8D to FMEA mapping sheet: from the complaint to the failure mode, cause, control and new ratings, on 1 page.

We email you the PDF. No newsletter. Privacy policy

What to Tell the Customer

Your customer’s SQE wants evidence that the system changed, in 5 lines:

  • The root cause, and why the part escaped.
  • What changed on the line, and the date.
  • The PFMEA rows and control plan lines that changed, with their revision.
  • Where else you applied it: parts, lines and plants.
  • The production data that shows the fix holds.

Attach the changed rows to the 8D. “FMEA updated” without the row is not evidence.

How Tacit AI Approaches This

Tacit AI imports your 8Ds, complaints, NCRs and warranty claims and links each record to the FMEA row it belongs to. FMEA freshness flags rows whose evidence is out of date. The control plan is built from the PFMEA rows. Your engineers review and approve every change. It works on top of the FMEA tool you already run.

A Top 20 Global OEM builds FMEAs 8× faster with it, with 26% fewer actions after customer review.

If your last 8D closed without a PFMEA change, book a working session and bring that 8D and the PFMEA it should have changed. See also keeping the PFMEA and control plan aligned and rebuilding the FMEA after a quality escape.

8Ds closing without touching the PFMEA?

Get the 8D to FMEA mapping sheet: from the complaint to the failure mode, cause, control and new ratings, on 1 page.

We email you the PDF. No newsletter. Privacy policy

Frequently Asked Questions

How do automotive suppliers link field complaints back to FMEAs and control plans?

Translate each complaint into the effect, failure mode and cause the FMEA uses, then find the row or add it. Update the control plan line in the same change and record the 8D number on the row.

Does IATF 16949 require a PFMEA update after an 8D?

Clause 10.2.3 requires problem solving to include reviewing and, where necessary, updating documented information such as the PFMEA and control plan. Clause 8.5.1.1 requires a control plan review after a customer complaint and its corrective action, when applicable.

Which 8D discipline updates the FMEA?

D7, Prevent Recurrence, is where the FMEA and control plan updates are confirmed. Some teams make the change in D6, with the corrective action.

What is an escape point in an 8D?

Ford’s Global 8D calls it the place closest to where the problem is generated where its effect should have been detected and contained, but was not. In the PFMEA, it is the detection control in the row.



Bring one FMEA.
See what it’s missing.

Your engineers judge the output. 30 minutes.

Cookie settings
Necessary cookies keep the site working and are always on. Analytics and advertising cookies are only set if you allow them. You can change this at any time. Privacy policy
Necessary
Allow Necessary cookies.
Analytics
Allow Analytics cookies.
Advertising
Allow Advertising cookies.