A PFMEA template — Process Failure Mode and Effects Analysis — is the systematic pre-production analysis that identifies every way a manufacturing process can fail, quantifies the risk of each failure mode using Severity, Occurrence, and Detection ratings, and prioritizes actions to reduce risk before production begins. Aligned to the AIAG-VDA FMEA Handbook (2019), the PFMEA is both a PPAP deliverable and a living engineering document that must be updated whenever the process changes, a new failure mode is discovered, or detection controls are modified. This page covers every column of a manufacturing PFMEA template, explains the AIAG-VDA rating scales, and shows how iFactory connects PFMEA detection controls to live inspection results so your ratings reflect what is actually happening on the floor.
Connect Your PFMEA Detection Controls to Live Inspection Data
iFactory links each PFMEA detection control to the live IPQC inspection results being collected on the production floor — so your Detection rating reflects what is actually happening, not what was assumed when the PFMEA was first written.
PFMEA Header & Scope Definition
The PFMEA header establishes the scope of the analysis — which process steps, which part numbers, which manufacturing locations, and which team members are responsible. A PFMEA scope that is too broad produces a superficial analysis; one that is too narrow misses cross-operation failure modes. The standard approach is one PFMEA per manufacturing process flow, with a separate row for each operation and each failure mode at that operation.
PFMEA Number
Unique document control identifier. Traceable to the revision history and linked to the APQP project record and PPAP submission package.
Item / Function
Name of the process step or operation being analyzed. One PFMEA row per function per operation — matched to the process flow diagram step number.
Model Year / Vehicle
Applicable model years and vehicle/platform designations for automotive applications. Links PFMEA to customer-specific program requirements.
Core Team
Cross-functional team: process engineering, quality, manufacturing, tooling, and customer representatives. All must be identified by name and functional responsibility.
PFMEA Date (Original / Revised)
Original issue date and most recent revision date. Revised date must be updated on every change — undated revisions are non-conforming in customer audits.
Process Flow Reference
Process flow diagram step number that this PFMEA row corresponds to. Ensures full traceability between process flow, PFMEA, and control plan.
AIAG-VDA PFMEA Column Structure
The AIAG-VDA 2019 FMEA Handbook introduced a revised column structure that differs from the earlier AIAG 4th Edition format. The most significant change is the replacement of Risk Priority Number (RPN) with Action Priority (AP) — a three-level classification (High, Medium, Low) based on a structured Severity × Occurrence × Detection matrix. Most automotive OEMs now require the AIAG-VDA format for new PFMEA submissions.
| Column | Field | What to Enter | AIAG-VDA Reference |
|---|---|---|---|
| 1 | Process Step / Function | Operation name and what it is supposed to do (intended function) | Step 4 — Structure Analysis |
| 2 | Failure Mode | How the process fails to perform its intended function — the specific non-conformance | Step 5 — Function Analysis |
| 3 | Effect of Failure | Consequence of the failure mode — on the customer, on downstream operations, on safety | Step 5 — Function Analysis |
| 4 | Severity (S) | Rating 1–10: impact of the failure effect on the customer. 9–10 = safety/regulatory. 1 = no discernible effect. | Step 6 — Risk Analysis |
| 5 | Cause of Failure | Specific, assignable cause of the failure mode — not "machine failure" but "drill insert wear exceeds replacement interval" | Step 5 — Function Analysis |
| 6 | Occurrence (O) | Rating 1–10: likelihood the cause produces the failure mode. 1 = unlikely; 10 = almost certain. Based on process capability data. | Step 6 — Risk Analysis |
| 7 | Prevention Controls | Process controls that prevent the cause or failure mode from occurring — standard work, mistake-proofing, setup verification | Step 6 — Risk Analysis |
| 8 | Detection Controls | Process controls that detect the cause or failure mode before it reaches the customer — in-process inspection, SPC, gauge | Step 6 — Risk Analysis |
| 9 | Detection (D) | Rating 1–10: ability of detection controls to identify the failure before delivery. 1 = almost certain to detect; 10 = no detection control. | Step 6 — Risk Analysis |
| 10 | Action Priority (AP) | H (High), M (Medium), or L (Low) — from AIAG-VDA AP table using S × O × D combination. H requires immediate action. | Step 6 — Risk Analysis |
| 11 | Recommended Actions | Specific actions to reduce AP — improve prevention, add detection, reduce occurrence. Must address the specific cause rated. | Step 7 — Optimization |
| 12 | Responsibility & Target Date | Owner of the recommended action and target completion date. Open actions must be tracked to closure. | Step 7 — Optimization |
Severity, Occurrence, and Detection Rating Guidance
Consistent S/O/D ratings across a PFMEA team require defined anchoring for each rating level. The most common PFMEA failure is internally inconsistent ratings — where a Severity 8 on one row covers the same effect as a Severity 6 on another. AIAG-VDA provides detailed rating tables; the summary below provides working anchors for each level in a manufacturing context.
Severity (S) — Effect on Customer
- 9–10: Safety hazard without warning / with warning; regulatory non-compliance
- 7–8: Product inoperable; major customer disruption; 100% of product may need to be scrapped
- 5–6: Product operable but reduced performance; customer dissatisfied
- 3–4: Minor performance reduction; fit/finish issue noticed by most customers
- 1–2: No discernible effect to slight annoyance only
Detection (D) — Control Effectiveness
- 1–2: Mistake-proofing device prevents occurrence or delivery; or 100% automatic gauging rejects before shipping
- 3–4: Error detection — automatic in-process check; SPC with reaction plan
- 5–6: Variable gauging on sample basis; attribute gauging on sample basis
- 7–8: Visual inspection only; manual check after operation
- 9–10: No detection control; defect detected by customer only
Action Priority (AP) — AIAG-VDA vs. RPN
The AIAG-VDA 2019 handbook replaced RPN (Risk Priority Number — the product of S × O × D) with Action Priority (AP) because RPN allowed high-severity failure modes to be rated acceptable by assigning very low occurrence and detection scores. AP applies a structured table that assigns High, Medium, or Low priority based on the combination of all three ratings — and makes Severity 9–10 failure modes automatically High priority regardless of O and D scores.
Any failure mode with Severity 9–10 is AP High regardless of O and D ratings. The team must either reduce S (requires design change), reduce O through prevention controls, or reduce D through additional detection controls. AP High items that have no recommended action are not acceptable in a PPAP submission.
A Detection rating of 3 (automatic in-process check) assigned when the actual control is manual sampling creates a false sense of risk reduction. Detection ratings must match the actual detection control documented in column 8 — and if that control changes (sampling frequency reduced, gauge removed from station), the D rating and AP must be updated immediately. iFactory's link between PFMEA detection controls and live IPQC data makes this verification automatic.
A PFMEA must be updated when: a new failure mode is discovered in production or from a customer return; a process change affects any prevention or detection control; a corrective action is implemented that changes O or D ratings; or the process capability (Cpk) data changes the basis for an Occurrence rating. A PFMEA that has not been updated in over a year should be audited against actual production conditions.
PFMEA in the PPAP Submission Package
The PFMEA is a required element of every PPAP Level 3 and above submission. The submitted PFMEA must be the current revision, signed by the PFMEA team lead and the quality representative, and must contain no open AP High items without documented recommended actions and completion dates. The control plan submitted with the PPAP must be traceable to the PFMEA — every detection control in column 8 of the PFMEA should appear in the control plan measurement method column for the corresponding operation.
Process FMEA is initiated during APQP Phase 3 — Process Design and Development — using the process flow diagram as the input structure. All operations in the process flow get PFMEA coverage.
PFMEA reviewed in a structured team session. Severity ratings confirmed with engineering and customer. Occurrence ratings confirmed with historical data or process capability estimates. Detection ratings confirmed with current control plan.
All AP High items must have documented recommended actions and responsible owners before PPAP submission. Open AP High items without action plans are a major non-conformance in IATF 16949 audits.
Each detection control in PFMEA column 8 is verified against the control plan — same characteristic, same gauge, same frequency. Any gap between PFMEA and control plan must be resolved before PPAP.
After PPAP, PFMEA is maintained as a living document. Production failures, customer returns, and process changes all trigger a review and update. Revision history is maintained in document control.
Link Your PFMEA Detection Controls to Live Inspection Results
iFactory connects each PFMEA detection control to the IPQC inspection workflow — so when your inspector records a measurement, it is compared against the PFMEA characteristic specification and the detection control effectiveness is tracked in real data.
PFMEA Checklist — 25 Items
Use this checklist to review a Process FMEA for AIAG-VDA alignment, rating consistency, special characteristic traceability, and PPAP readiness. Covers the most common PFMEA deficiencies found in customer audits.
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 1 | PFMEA number, revision level, and document control reference assigned | Pass/Fail | High | — | ✓ | ✓ |
| 2 | Part number and current drawing revision in header match document control | Pass/Fail | High | — | ✓ | ✓ |
| 3 | Process flow diagram reference number in header — confirms traceability | Pass/Fail | High | — | ✓ | ✓ |
| 4 | Original issue date and most recent revision date both documented | Pass/Fail | Med | — | ✓ | — |
| 5 | Cross-functional team listed — process engineering, quality, and manufacturing all represented | Pass/Fail | Med | — | ✓ | — |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 6 | Every process step in the routing has at least one PFMEA row | Pass/Fail | High | — | ✓ | ✓ |
| 7 | Failure mode states how the operation fails — specific and measurable, not generic | Pass/Fail | High | — | ✓ | ✓ |
| 8 | Cause of failure is specific and assignable — not "machine failure" or "human error" | Pass/Fail | High | — | ✓ | ✓ |
| 9 | Prevention and detection controls listed separately in correct columns | Pass/Fail | High | — | ✓ | ✓ |
| 10 | Action Priority (AP) used — not RPN, unless customer still requires RPN format | Pass/Fail | High | — | ✓ | ✓ |
| 11 | Recommended actions populated for all AP High rows — no AP High without action | Pass/Fail | High | — | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 12 | Severity ratings 9–10 only assigned for safety or regulatory failure effects | Pass/Fail | High | — | ✓ | ✓ |
| 13 | Occurrence ratings based on process capability data or historical defect rates | Pass/Fail | High | — | ✓ | ✓ |
| 14 | Detection rating of 1–2 only assigned where validated mistake-proofing or 100% auto-gauging is in place | Pass/Fail | High | — | ✓ | ✓ |
| 15 | Rating scale applied consistently across all rows — no internal inconsistencies | Pass/Fail | High | — | ✓ | ✓ |
| 16 | Detection ratings reflect actual current controls — not theoretical or planned controls | Pass/Fail | High | — | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 17 | All special characteristics from engineering drawing identified in PFMEA | Pass/Fail | High | — | ✓ | ✓ |
| 18 | Special characteristics carry correct customer classification symbol — CC, SC, KPC | Pass/Fail | High | — | ✓ | ✓ |
| 19 | All PFMEA special characteristics carried through to control plan with same classification | Pass/Fail | High | — | ✓ | ✓ |
| 20 | High-severity failure modes have documented prevention AND detection controls | Pass/Fail | High | — | ✓ | ✓ |
| # | Checklist Item | Type | Priority | Photo | Required | Critical |
|---|---|---|---|---|---|---|
| 21 | PFMEA updated when any process change affects prevention or detection controls | Pass/Fail | High | — | ✓ | ✓ |
| 22 | PFMEA updated when new failure mode discovered from production or customer return | Pass/Fail | High | — | ✓ | ✓ |
| 23 | No AP High items without documented recommended actions and completion dates | Pass/Fail | High | — | ✓ | ✓ |
| 24 | All detection controls in PFMEA col.8 traced to matching control plan entries | Pass/Fail | High | — | ✓ | ✓ |
| 25 | PFMEA included in PPAP submission — current revision, signed by team lead | Pass/Fail | High | — | ✓ | ✓ |
Frequently Asked Questions
What is a PFMEA and why is it required?
A Process FMEA (Process Failure Mode and Effects Analysis) is a systematic analysis of every way a manufacturing process can fail to produce a conforming part. It is required by IATF 16949 as a PPAP deliverable, by AS9100 for production process risk analysis, and by most automotive OEM customer-specific requirements. The PFMEA identifies failure modes, their causes, their effects, and the controls in place to prevent and detect them. It is the input to the control plan — every detection control in the PFMEA should appear as a monitored characteristic in the control plan.
What is the difference between AIAG-VDA FMEA and the old AIAG 4th Edition format?
The AIAG-VDA 2019 FMEA Handbook introduced several significant changes to the previous AIAG 4th Edition format: Action Priority (AP) replaces RPN as the risk prioritization method; a seven-step FMEA process is defined (scoping, structure analysis, function analysis, failure analysis, risk analysis, optimization, and results documentation); the column structure is updated with additional columns for prevention vs. detection controls; and Severity 9–10 failure modes are automatically AP High regardless of occurrence and detection ratings. Most automotive OEMs now require AIAG-VDA format for new PFMEA submissions beginning with model year 2024 and later programs.
How do you determine the Occurrence rating in a PFMEA?
The Occurrence rating should be based on objective data wherever possible — process capability (Cpk) data, historical defect rates for the same cause, or supplier performance data. For new processes with no history, the Occurrence rating is estimated based on similar processes. AIAG-VDA provides a Cpk-to-Occurrence rating table: Cpk ≥ 1.67 supports an O rating of 2; Cpk 1.33–1.67 supports O rating 3–4; Cpk 1.00–1.33 supports O rating 5–6; Cpk < 1.00 supports O rating 7–10. Occurrence ratings should be updated whenever new process capability data is available.
What triggers a PFMEA update?
A PFMEA must be updated whenever: a new failure mode is discovered in production or from a customer return; a process change affects any prevention or detection control; corrective actions change the basis for an S, O, or D rating; process capability data changes significantly; a customer return or warranty claim identifies a failure mode not in the PFMEA; or an internal audit finds that the current PFMEA does not reflect actual production conditions. The revision date, revision level, and description of changes must be documented in the PFMEA revision history.
How does iFactory support PFMEA maintenance?
iFactory connects each PFMEA detection control to the live IPQC inspection data being collected on the floor. When a detection control's effectiveness changes — because inspection frequency was reduced, a gauge was removed from the station, or defects are escaping a control that was rated highly — the system flags the discrepancy for PFMEA review. Teams can initiate PFMEA updates directly from within iFactory and the updated PFMEA revision is linked to the PPAP record. Book a Demo to see the PFMEA module. Book a Demo
Replace Your Process FMEA Excel Template with a Live Digital Document
iFactory gives automotive and manufacturing quality teams a complete digital PFMEA workflow — AIAG-VDA aligned, linked to the control plan and IPQC, with AP tracking and automatic update triggers when process conditions change.
