Automotive FMEA Guide

Automotive is where FMEA became a formal working method, not just a worksheet. OEMs, Tier 1 suppliers, and sub-tier manufacturers use it to connect design intent, process risk, launch readiness, and ongoing risk control.

A strong automotive FMEA page should not only define the terms. It should explain how PFMEA and DFMEA fit into APQP, PPAP, Control Plan development, customer-specific requirements, and change control after launch.

If you want the method behind the page, continue to AIAG-VDA FMEA Guide, Action Priority Guide, and Control Plan vs FMEA.

Automotive teams often talk about FMEA as one thing, but the real work splits into two distinct domains. PFMEA focuses on process risk. DFMEA focuses on design risk. Both matter, but they answer different questions and are owned by different functions.

For a broader theoretical overview, use Process FMEA vs Design FMEA.

Good automotive teams do not create PFMEA in isolation. They connect it to the launch system. The flow is usually:

1. Define customer requirements, product intent, and process scope.
2. Break the product or process into a clear structure.
3. Write functions and failure chains that can be reviewed by cross-functional teams.
4. Assess Severity, Occurrence, Detection, and derive Action Priority.
5. Translate high-priority risks into prevention or detection actions.
6. Align PFMEA with Control Plan, work instructions, validation, and PPAP evidence.
7. Reopen the PFMEA when tooling, materials, supplier inputs, or customer requirements change.

This is why automotive FMEA should never be treated as a static document. It is part of launch governance, not just a compliance file.

Related implementation pages: 7-step method, audit checklist, common mistakes.

These are the kinds of rows automotive teams should be able to write and defend in a review. The point is not the exact number. The point is whether the failure mode, cause, controls, and action priority logic are specific enough to support real decisions.

• They write process steps at the right level of detail, not too broad and not too micro.
• They separate prevention from detection instead of merging both into vague controls.
• They use realistic Detection ratings, especially for visual checks and manual inspections.
• They treat Action Priority as a decision tool, not as a spreadsheet label.
• They link PFMEA rows to a Control Plan reaction, an owner, and a due date.
• They reopen the analysis when tooling, suppliers, materials, or requirements change.

If you want the logic behind the ratings, see Severity, Occurrence, Detection, and Action Priority.

Automotive auditors and customer reviewers often look for the same weak spots. This is where a page like this should be useful, because the reader wants to know what actually fails in practice.

• PFMEA and Control Plan do not match on special characteristics or reaction plans.
• Failure modes are too generic to trace to a real process risk.
• Detection controls are written as if inspection prevented failure.
• Action Priority is ignored or treated like legacy RPN thinking.
• The document is not updated after process, tooling, or supplier changes.
• PFMEA ownership is unclear between quality, manufacturing, and process engineering.

For audit preparation, use FMEA Audit Checklist.

Reopen the PFMEA when any of the following happens:

• Tooling changes.
• Process parameters change.
• New supplier or material is introduced.
• Customer complaints or field issues appear.
• Control Plan changes.
• PPAP or validation feedback shows the original assumption was wrong.

IATF 16949 and the AIAG-VDA handbook define the floor. Every OEM layers customer-specific requirements (CSRs) on top — and PFMEA / DFMEA submissions are routinely rejected for ignoring them. The table below summarizes the patterns most automotive suppliers actually deal with.

CSRs change frequently. Treat them as a living input to the FMEA template, not a one-time configuration. See FMEA template for the field set CSRs typically modify, and AIAG-VDA FMEA software for tooling that handles per-customer profiles.

Automotive auditors expect PFMEA evidence at each APQP phase, not only at PPAP. The maturity expected at each gate is different — confusing the two is one of the most common findings in launch readiness reviews.

For the underlying method see the 7-step process; for ongoing corrective action linkage see common mistakes and the audit checklist.

DFMEA in automotive is where most teams under-invest. PFMEA gets attention because it directly affects production. DFMEA gets attention only when a customer requires it for PPAP or when a field issue is traced to a design assumption that was never challenged.

• Function-driven, not part-driven. Each design element must have explicit functions and requirements; failure modes are inversions of those functions, not part nicknames.
• Validation as detection. Detection controls are design-verification tests, DV/PV plans, CAE simulations and tolerance analysis — not in-line inspections.
• Interfaces matter. Most automotive DFMEA misses live at the interface between subsystems (connectors, software-to-hardware boundaries, harness routing). The structure tree must include interfaces, not only components.
• Linkage to PFMEA. A DFMEA cause that becomes a manufacturing risk must appear in the PFMEA as a failure mode. The handoff is bidirectional.

For methodology, see Process FMEA vs Design FMEA and Design FMEA software.

1. Build the structure tree before the first rating workshop. Functions and interfaces drive everything downstream.
2. Lock the rating tables and the CSR profile per program. Drift in tables between projects is the most audit-visible inconsistency.
3. Treat the PFMEA and the Control Plan as one dataset, two deliverables. Update them together, never separately.
4. Run cross-functional reviews with a written attendance list (per team roles). Single-author PFMEAs always fail audits.
5. Use a deterministic Action Priority engine — never rely on a spreadsheet formula for AP. See Action Priority.
6. Build the lessons-learned register from 8D records and warranty data, and feed it back into the next program kick-off.

• AIAG-VDA FMEA Guide
• AIAG-VDA 7-step process
• Control Plan vs FMEA
• FMEA Audit Checklist
• PFMEA CNC machining example
• FMEA example
• FMEA for Manufacturing
• Process FMEA software