Back to all posts
PFMEA process analysis preview

What Is PFMEA? Process Failure Mode and Effects Analysis Explained

Published
PFMEAProcess FMEAFMEAManufacturing QualityAIAG-VDAProcess Engineering

What Is PFMEA?

Process Failure Mode and Effects Analysis (PFMEA) is a structured, team-based risk analysis method applied to manufacturing and assembly processes. It identifies what could go wrong at each process step, evaluates the potential impact on the customer, and defines controls to prevent or detect failures before products leave the plant.

PFMEA is a core requirement of IATF 16949 for automotive suppliers and is governed by the AIAG-VDA FMEA Handbook (2019). It is also referenced in ISO 9001, APQP, and PPAP documentation packages.

PFMEA is part of FMEA Excellence

The FMEA Excellence application includes a full AI-assisted PFMEA module following the AIAG-VDA 7-Step approach, linked directly to the DFMEA and Control Plan workflow.

What Does PFMEA Analyze?

PFMEA analyzes the production process — the steps, equipment, tooling, and people involved in making a product. It assumes the product design is correct and focuses on failures introduced by the process itself.

PFMEA scope includes

Process-level failure modes

  • Incorrect dimension due to tool wear or fixture drift
  • Missing or wrong component during assembly
  • Insufficient torque, weld strength, or adhesive application
  • Surface contamination or incorrect surface finish
  • Out-of-sequence processing steps

Process-level effects

  • Defective product delivered to the customer
  • Safety hazard from a failed assembly
  • Increased scrap, rework, or warranty costs
  • Line stoppage or production delay
  • Non-conformance to customer or regulatory specifications

The AIAG-VDA 7-Step PFMEA Process

The same 7-Step structure from the AIAG-VDA Handbook applies to PFMEA, with process-specific content at each step.

Step 1: Planning and Preparation

Define the scope, team, and timeline for the PFMEA. Identify process boundaries, reference documents (drawings, process flow diagrams), applicable customer requirements, and lessons learned from similar processes.

Step 2: Structure Analysis

Build the process structure using a Process Flow Diagram (PFD). Decompose the process into process steps, work elements, and 4M categories: Man, Machine, Material, Method (plus Environment and Measurement).

Step 3: Function Analysis

Define the intended function of each process step. Functions describe what the process step must achieve (e.g., "Tighten bolt to 25 Nm ± 2 Nm") and the product characteristics it produces.

Step 4: Failure Analysis

For each process function, identify:

  • Failure Mode — In what way could this process step fail? (e.g., "Torque too low")
  • Failure Effect — What is the impact upstream, downstream, or on the end customer?
  • Failure Cause — What process variable or 4M factor could trigger this failure? (e.g., "Worn socket causing torque loss")

This three-tier failure chain connects process execution to customer impact.

Step 5: Risk Analysis

Rate each failure mode on three criteria:

  • Severity (S) — Impact on the customer or end user (1–10). Note: Severity is typically inherited from the linked DFMEA or product specification.
  • Occurrence (O) — Likelihood the cause occurs during production (1–10).
  • Detection (D) — Effectiveness of current process controls at detecting the failure before it leaves the station (1–10).

The AIAG-VDA handbook uses S, O, and D to assign an Action Priority (AP) — High, Medium, or Low — to guide which failure modes require immediate action.

Step 6: Optimization

For all High and Medium AP items, define and implement actions to reduce risk. Actions may target:

  • Occurrence reduction: Improved process controls, error-proofing (poka-yoke), SPC, revised work instructions
  • Detection improvement: Added inspection steps, gauge capability studies, vision systems

Assign owners, set due dates, and verify effectiveness after implementation.

Step 7: Results Documentation

Complete the PFMEA with all action results, updated risk scores, and authorized sign-off. The PFMEA feeds directly into the Control Plan and is submitted as part of the PPAP documentation package for customer approval.

PFMEA and the Control Plan

The PFMEA and Control Plan are tightly linked documents. Every significant detection or prevention control identified in the PFMEA should appear in the Control Plan, with defined measurement frequency, sample size, and reaction plan.

PFMEA → Control Plan traceability

AIAG-VDA requires that high-severity or high-occurrence failure modes in the PFMEA are directly traceable to specific control plan entries. Teams that update the PFMEA without updating the Control Plan introduce audit risk.

PFMEA vs. DFMEA

PFMEADFMEA
FocusManufacturing / assembly processProduct design
Performed byProcess / manufacturing engineersDesign engineers
TimingBefore production launchBefore design freeze
Failure causesProcess variation, human error, equipmentDesign weaknesses, material selection
ControlsProcess controls, inspection, poka-yokeDesign controls, validation tests
OutputControl Plan input, work instructionsDesign changes, validation plans

Learn more about DFMEA →

Common PFMEA Mistakes to Avoid

Pitfalls and how to prevent them

Copying PFMEA without review

Copying a PFMEA from a previous project without reviewing for process differences is a common audit finding. Each PFMEA must reflect the actual process being analyzed.

Listing effects at only one level

Effects should be described at the process level, the plant level, and the end-customer level. AIAG-VDA requires all three levels for complete risk assessment.

Not updating PFMEA after engineering changes

Process changes — tooling updates, machine replacements, revised work instructions — must trigger a PFMEA review. A PFMEA that doesn't reflect the current process provides false assurance.

Ignoring historical data

Field warranty data, internal scrap data, and supplier quality data are valuable inputs. Use them to calibrate Occurrence ratings and focus analysis on historically problematic process steps.

PFMEA in FMEA Excellence

The FMEA Excellence application includes a complete PFMEA module with:

  • Guided AIAG-VDA 7-Step structure
  • AI-assisted failure mode, cause, and control generation
  • Process Flow Diagram–linked structure analysis
  • Built-in S/O/D rating scales with Action Priority calculation
  • Direct link between PFMEA findings and Control Plan entries
  • Export-ready reports for PPAP and customer audits
Also includes DFMEA

FMEA Excellence supports both DFMEA and PFMEA in a single platform, enabling full traceability from design intent through manufacturing controls and into delivered product quality.

Frequently Asked Questions

What is PFMEA?

PFMEA (Process Failure Mode and Effects Analysis) is a structured risk analysis method that identifies potential failure modes in a manufacturing or assembly process, assesses their impact on product quality and customer safety, and defines preventive or detective controls to reduce risk.

What is the purpose of PFMEA?

The purpose of PFMEA is to proactively prevent manufacturing defects before production begins. It helps teams reduce scrap and rework, improve process control plans, meet IATF 16949 and AIAG-VDA requirements, and protect product quality delivered to customers.

When should PFMEA be done?

PFMEA should be done during the process design and development phase, before production launch. It is typically completed after DFMEA and feeds directly into the Control Plan and process instructions.

What is the relationship between PFMEA and the Control Plan?

PFMEA and the Control Plan are directly linked. High-risk process failure modes identified in the PFMEA drive the detection and prevention controls documented in the Control Plan. Updating the PFMEA should always trigger a review of the Control Plan.

What scoring method does PFMEA use?

PFMEA uses Severity (S), Occurrence (O), and Detection (D) scores on a 1–10 scale. The AIAG-VDA handbook uses these scores to assign an Action Priority (AP) of High, Medium, or Low, guiding which failure modes need immediate corrective action.