1. What Is AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA)?
AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA) is a structured operational-risk framework for identifying how manufacturing processes could fail, understanding the consequences, and prioritizing preventive improvements. It connects process requirements, potential failures, their causes, existing controls, and improvement actions.
For manufacturers of industrial machinery, the practical question is: where could machining, assembly, configuration, testing, or handling introduce a defect that escapes into customer operations? Consultants can use PFMEA to structure decisions about tooling, error-proofing, inspection, and production readiness—not simply to produce another quality document.
2. Origin and Background
The harmonized AIAG & VDA FMEA Handbook was released in June 2019 through collaboration between the Automotive Industry Action Group and the German Association of the Automotive Industry. It combined their previously separate regional approaches to help automotive suppliers analyze technical risks consistently. This was a harmonization of existing FMEA practices, not the invention of FMEA itself.
The handbook introduced a seven-step approach and Action Priority methodology. Its original context was automotive product development and production. Other equipment manufacturers can adopt its process-analysis logic, but should not assume that automotive submission requirements automatically apply to their customers or products.
3. How AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA) Works
Understanding the name
- AIAG: Automotive Industry Action Group.
- VDA: Verband der Automobilindustrie, the German Association of the Automotive Industry.
- PFMEA: Process Failure Mode and Effects Analysis—the manufacturing-process application of FMEA.
The seven steps are Planning and Preparation, Structure Analysis, Function Analysis, Failure Analysis, Risk Analysis, Optimization, and Results Documentation. Their sequence matters: teams first understand the process and its intended functions, then analyze failures, evaluate controls, and decide what to improve.
Structure analysis connects three levels: the overall process item, the process step being examined, and the supporting work elements. For example, a hydraulic-unit assembly process contains a coupling-tightening operation supported by an operator, tightening equipment, and input components. Function analysis then establishes what each level must accomplish, including relevant product and process requirements.
Failure analysis builds a cause–failure mode–effect chain. Selecting the wrong tightening program is a cause; insufficient joint preload is a failure mode; leakage during customer operation is an effect. These are different concepts and should remain separate. Effects should consider the manufacturer’s plant, the receiving plant, and the end user where known.
Ratings and Action Priority
- Severity: How serious the failure’s consequences would be.
- Occurrence: The likelihood of the failure cause, considering prevention controls.
- Detection: The effectiveness of controls in detecting the cause or failure mode before escape. Higher detection ratings represent weaker detection capability.
Teams use the handbook’s applicable rating criteria and Action Priority (AP) tables to assign High, Medium, or Low priority. AP replaces the traditional Risk Priority Number as the handbook’s action-prioritization method; it is not simply a renamed numerical score. Nor is Low AP a declaration that a process is safe or acceptable. Use the prescribed tables rather than inventing score thresholds.
4. When to Use AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA)
Use PFMEA when launching production, introducing new equipment or tooling, transferring operations, changing materials or suppliers, or revising a process after quality problems. It is particularly useful before changes become expensive to reverse and when several functions must agree on preventive controls.
For engineer-to-order equipment, distinguish reusable process knowledge from order-specific requirements. Producers of industrial automation equipment should include controller configuration, firmware loading, and wiring verification where these operations affect conformity—not only mechanical assembly.
Useful inputs include process flows, drawings, specifications, defect and rework records, customer complaints, control descriptions, and direct shop-floor knowledge. Bring together manufacturing engineering, quality, operators, maintenance, and relevant product specialists. Effort depends on process complexity and the evidence needed to validate controls, not merely workshop duration.
PFMEA becomes misleading when requirements are unclear, controls are assumed rather than demonstrated, or sparse production history is treated as proof of low occurrence. It is not the right standalone tool for assessing product-design adequacy or determining machinery-safety compliance.
5. How to Apply AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA): Step-by-Step
Use the handbook’s seven steps as the backbone of the engagement. The following guidance translates them into an equipment-manufacturing workplan.
- Planning and Preparation: define the decision.
Specify the product family, factory, process boundaries, variants, and production-readiness milestone. Identify customer requirements and applicable methodology expectations. Gather specifications, process records, field feedback, and previous analyses. Assign a process owner and cross-functional team.
- Structure Analysis: map actual operations.
Walk the production route, including outsourced processing, storage, rework, and alternate paths. Define process items, steps, and work elements. Keep operation identifiers consistent across the process flow, PFMEA, and subsequent control documentation.
- Function Analysis: establish requirements.
Describe what each operation must deliver in measurable terms: required geometry, cleanliness, joint condition, wiring connectivity, or configuration. Separate product characteristics from process parameters. Resolve missing specifications before debating ratings.
- Failure Analysis: construct failure chains.
Identify how each function could fail, the resulting effects, and specific causes. Record separate causes where controls differ. Include setup errors, tool deterioration, material mix-ups, maintenance interventions, and recovery after interrupted cycles where relevant.
- Risk Analysis: assess current controls.
Document prevention and detection separately, assign ratings using the applicable criteria, and determine AP. Challenge optimistic assumptions through equipment trials, measurement evidence, and operator interviews. Test whether different variants, shifts, or operating conditions change the conclusion.
- Optimization: implement and verify actions.
Assign owners, deadlines, resources, and effectiveness tests. Prefer preventing causes where feasible, rather than adding inspection alone. Validate new controls before claiming improved ratings; prevention and detection affect different parts of the assessment.
- Results Documentation: align and maintain.
Summarize unresolved concerns, completed actions, evidence, and required management decisions. Update control plans and operating instructions. Review disagreements with process experts, and revisit the analysis after relevant changes or new failures.
When actions span tooling suppliers, plant engineering, and production teams, program management support can coordinate installation windows, validation dependencies, and document release. Technical ownership should remain with the responsible engineering and quality functions.
6. Example: AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA) in Action
Fictional example: Northline Hydraulic Systems manufactures configurable power units for industrial presses. Following assembly-related leaks, its operations director commissions a PFMEA before adding another product variant.
The team maps component preparation, fitting assembly, tightening, pressure testing, and release. It examines individual operations rather than assigning one risk score to the entire production line. Inputs include drawings, tightening specifications, rework records, test procedures, and technician interviews.
At the tightening step, the team identifies a cause: an operator can select a program intended for a different fitting. The failure mode is inadequate joint preload. Potential effects include internal rework and leakage in customer service. The existing test does not demonstrate reliable detection across all relevant conditions.
Using the prescribed criteria and AP table, the fictional team assigns High priority. It introduces work-order-linked program selection, adds monitored tightening results, and validates the revised process across relevant fitting variants. Engineering confirms that the selected parameters are appropriate; challenge tests establish whether the controls reject defined nonconformities.
A focused defect and error reduction engagement could implement these changes. Northline closes actions only after verification and updates its control plan. It does not lower severity merely because the defect is now less likely to escape.
7. Strengths and Limitations
Strengths
- Connects consequences to causes: Links customer failures to specific manufacturing operations and controls.
- Makes prevention actionable: Converts concerns into assigned improvements rather than leaving them as general warnings.
- Builds shared understanding: Brings engineering, production, quality, and supplier knowledge into one analysis.
Limitations
- Depends on completeness: An omitted failure mechanism receives no meaningful assessment.
- Requires judgment: Ratings do not eliminate uncertainty, especially when process evidence is limited.
- Does not prove effectiveness: A completed worksheet cannot substitute for trials, reliable measurements, or implemented controls.
For equipment manufacturers, supplement PFMEA where interactions, asset degradation, or design-related hazards require additional analysis. Manufacturing reliability work may need to examine both the machine and the process it performs.
8. Common Pitfalls and How to Avoid Them
- Starting with scores: Teams debate numbers before understanding functions. Establish requirements and failure chains first.
- Writing “operator error” as the cause: This hides actionable mechanisms. Identify the wrong selection, missing constraint, ambiguous instruction, or other specific condition.
- Crediting planned controls prematurely: Distinguish proposals from functioning controls. Require installation and effectiveness evidence before recording the improvement.
- Confusing detection with prevention: Finding an incorrect assembly does not necessarily stop the cause recurring. Classify each control by what it actually does.
- Copying a baseline without checking differences: Review tooling, materials, variants, suppliers, and local operating conditions before reusing prior conclusions.
- Stopping at action closure: Ensure verified controls appear in production documentation and remain owned by the process organization.
9. How AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA) Relates to Other Frameworks
Before: Design FMEA and process mapping
Design FMEA examines potential design-related failures; PFMEA examines manufacturing-process failures. Use design analysis to clarify requirements and consequences, then map the production process before assessing how operations could fail. Neither analysis replaces the other.
Alongside: measurement and process control
Measurement System Analysis supports confidence in inspection data. Statistical Process Control helps monitor process variation. PFMEA identifies where these tools are relevant; they provide evidence and operational control rather than another list of hypothetical failures.
After: control plans and qualification
Control plans translate selected controls into production practice. Where customer requirements call for Production Part Approval Process submissions, PFMEA contributes to the qualification package; it does not independently establish production approval.
10. Key Takeaways
- Analyze manufacturing failure chains, not product families as undifferentiated risks.
- Define functions and requirements before assigning ratings.
- Use the prescribed Action Priority tables—not improvised numerical thresholds.
- Prioritize verified prevention and effective detection.
- Keep PFMEA connected to control plans, operating instructions, and change management.
11. FAQs About AIAG & VDA Process Failure Mode and Effects Analysis (PFMEA)
Can non-automotive equipment manufacturers use this approach?
Yes. Its process-risk logic is applicable beyond automotive production. Treat that as a methodological choice, however, and confirm customer expectations rather than assuming automotive qualification requirements apply.
What is the difference between PFMEA and Design FMEA?
PFMEA addresses failures introduced by manufacturing operations. Design FMEA addresses failures arising from the product design. Equipment manufacturers need a clear interface between the two.
Can a small, low-volume manufacturer use PFMEA?
Start with a bounded process and a small cross-functional team. Use drawings, direct observation, prior problems, and control evidence. Record uncertainty explicitly instead of interpreting limited production history as reassurance.
Does a completed PFMEA qualify the production process?
No. It documents risk analysis and improvement decisions. Qualification also requires appropriate evidence that the process and its controls meet relevant specifications and customer requirements.
