FMEA in Automotive Manufacturing: PFMEA, Process FMEA, Examples and Complete Guide

Failure Mode and Effects Analysis, commonly known as FMEA, is one of the most important preventive quality tools used in automotive manufacturing. It helps manufacturing and engineering teams think about potential problems before those problems become actual defects.

In a typical automotive manufacturing environment, a product passes through many stages before reaching the customer. These may include product design, material procurement, tooling, machining, stamping, welding, assembly, inspection, testing, packaging and final dispatch. Every stage can introduce a different type of risk.

A problem such as an incorrect dimension, missing component, excessive burr, wrong torque, fixture misalignment or damaged surface may appear to be a small manufacturing issue. However, depending on where the defect occurs and how it affects the final product, it can lead to assembly problems, customer rejection, line stoppage, warranty claims or even safety-related concerns.

This is where FMEA becomes useful.

For manufacturing organizations, Process FMEA (PFMEA) provides a structured way to study manufacturing and assembly processes, identify potential failure modes, understand their causes and effects, evaluate risk and establish suitable prevention and detection controls.

A good PFMEA is not simply a document prepared for an audit. It should be a practical engineering document that helps the team understand what can go wrong, why it can go wrong, how it can be prevented and how the organization will detect the problem if prevention is not sufficient.

This complete guide explains FMEA and PFMEA in practical terms, including:

What is FMEA?
What is PFMEA?
Types of FMEA
Difference between FMEA and PFMEA
Purpose of PFMEA
PFMEA team and responsibilities
Inputs required for PFMEA
Process Flow, PFMEA and Control Plan relationship
PFMEA preparation steps
Severity, Occurrence and Detection
Traditional RPN
AIAG & VDA Action Priority
Practical PFMEA example
Prevention and detection controls
PFMEA review and update
Horizontal deployment
Common PFMEA mistakes
PFMEA and IATF 16949
PFMEA and Automotive Core Tools
PFMEA checklist
Frequently asked questions

What is FMEA?

FMEA stands for Failure Mode and Effects Analysis.

It is a structured method used to identify potential failures, understand their effects and causes, evaluate associated risks and determine actions that can reduce or eliminate those risks.

The basic logic of FMEA can be understood as:

Process or Product → Failure Mode → Effect → Cause → Controls → Risk → Action

The purpose is to look at a product or process from a failure-risk perspective before the failure creates a real problem.

Simple FMEA example

Consider a CNC drilling operation in an automotive component manufacturing process.

The process function is to produce a hole according to the specified diameter and location.

A possible failure mode could be:

Hole diameter oversize

The potential effect could be:

Improper assembly or functional problem

A possible cause could be:

Tool wear

Existing controls may include:

Prevention Control: Tool-life monitoring

Detection Control: Hole diameter inspection

The FMEA team then evaluates whether the existing controls are sufficient and whether additional actions are required.

This simple example demonstrates the basic thinking behind FMEA.

FMEA is therefore not just about filling columns in an Excel sheet. The real objective is to understand the process and identify risks before they reach the next operation or the customer.

Why is FMEA Important in Automotive Manufacturing?

Automotive manufacturing requires a high level of consistency because the final vehicle contains thousands of components and numerous manufacturing and assembly operations.

A variation in one manufacturing operation can sometimes create a problem several operations later.

For example:

Incorrect hole position → Assembly difficulty → Line stoppage → Customer concern

Similarly:

Insufficient welding → Weak joint → Functional failure → Customer complaint

The purpose of FMEA is to identify such possible chains of failure before they occur.

Major benefits of FMEA include:

Identification of potential failures before production problems occur
Reduction of product and process risks
Improved prevention controls
Improved detection controls
Reduction in rejection and rework
Better understanding of manufacturing processes
Improved Control Plan development
Better cross-functional communication
Capture of lessons learned
Support for continuous improvement
Better preparation for new product launches
Better preparation for process changes
Improved customer satisfaction
Better understanding of special characteristics and process controls

FMEA becomes particularly important during:

New product development
New process development
Tool development
Process trials
Process changes
Engineering changes
Supplier changes
Customer complaints
Repeated internal rejection
Corrective actions
Lessons-learned activities

A PFMEA should therefore evolve along with the manufacturing process.

Types of FMEA

FMEA can be applied to different areas of product and process development.

The major FMEA types relevant to automotive organizations include:

Design FMEA – DFMEA
Process FMEA – PFMEA
FMEA-MSR

Each has a different purpose.

Design FMEA – DFMEA

DFMEA stands for Design Failure Mode and Effects Analysis.

DFMEA focuses primarily on potential failures associated with product design, design requirements and product functions.

For example, consider an automotive bracket.

One potential failure mode could be:

Bracket cracks during vehicle operation

The team would evaluate:

What could cause the bracket to crack?
What would happen if it cracked?
What design controls exist?
What design changes could reduce the risk?
How can the design be verified?

DFMEA is therefore mainly concerned with product and design-related risks.

The focus is on the product rather than the manufacturing process.

Process FMEA – PFMEA

PFMEA stands for Process Failure Mode and Effects Analysis.

PFMEA focuses on potential failures associated with manufacturing and assembly processes.

A PFMEA normally considers:

Process steps
Process functions
Potential failure modes
Potential effects
Potential causes
Prevention controls
Detection controls
Risk evaluation
Improvement actions
Responsibility
Completion and effectiveness verification

For an automotive component manufacturer, PFMEA is one of the key tools for understanding manufacturing-process risks.

For example, a stamping operation may have risks such as:

Wrong material
Incorrect blank size
Part deformation
Burr
Crack
Wrinkle
Incorrect hole position
Surface damage
Tool mismatch
Incorrect loading
Missing operation

These risks can be systematically evaluated through PFMEA.

FMEA-MSR

FMEA-MSR refers to FMEA for Monitoring and System Response.

It addresses risks associated with monitoring and system response during vehicle operation.

The AIAG & VDA FMEA methodology provides guidance for Design FMEA, Process FMEA and FMEA-MSR.

The three applications should not be treated as identical documents because their objectives and analysis perspectives are different.

Difference Between FMEA and PFMEA

FMEA is the broader failure-analysis methodology, while PFMEA is specifically focused on manufacturing and assembly process risks.

FMEA	PFMEA
Failure Mode and Effects Analysis	Process Failure Mode and Effects Analysis
General failure-risk analysis methodology	Manufacturing/process-focused application
Can be applied to different areas	Primarily manufacturing and assembly
Covers different FMEA applications	One specific application of FMEA
Identifies potential failures and associated risks	Identifies process-related failures and risks

In simple terms:

PFMEA is a specific application of FMEA for manufacturing processes.

What is the Purpose of PFMEA?

The main purpose of PFMEA is to identify potential process risks before they become actual defects or customer problems.

A good PFMEA should help the team answer several basic questions:

What is the process supposed to do?
What could go wrong?
What would happen if it went wrong?
Why could the failure occur?
What controls already exist?
How can the failure be prevented?
How can the failure be detected?
What is the associated risk?
What action is required?
Who is responsible?
When should the action be completed?
How will the effectiveness of the action be verified?

These questions sound simple, but they force the team to examine the process in detail.

A PFMEA becomes much more useful when the answers are based on:

Actual production experience
Historical rejection data
Customer complaints
Process capability
Machine information
Tooling knowledge
Inspection data
Previous lessons learned
Operator experience
Process trials

Who Should Prepare PFMEA?

PFMEA should ideally be prepared by a cross-functional team rather than by one person working alone.

Depending on the organization and process, the team may include:

Quality Engineer
Process Engineer
Production Engineer
Production Supervisor
Operator
Maintenance Engineer
Tooling Engineer
Manufacturing Engineer
Design Engineer
Supplier Quality Engineer
Project Engineer
Other technical specialists

Each person sees the process from a different perspective.

For example, a Quality Engineer may understand:

Customer complaints
Inspection requirements
Rejection trends
Special characteristics

A Process Engineer may understand:

Machine parameters
Process sequence
Capability
Process limitations

A Tooling Engineer may understand:

Tool wear
Fixture-related risks
Die or mould conditions
Tool maintenance requirements

An experienced operator may identify practical risks that are not obvious from engineering documents.

This is one of the reasons cross-functional participation is important.

Inputs Required for PFMEA

Before starting a PFMEA, the team should collect relevant technical and historical information.

Typical inputs include:

Process Flow Diagram
Product drawing
Product specifications
Customer requirements
Customer-specific requirements
Special characteristics
Previous PFMEA
Similar-product PFMEA
Control Plan
Customer complaints
Internal rejection data
Scrap data
Rework data
Warranty information
Process capability information
Lessons learned
Historical process problems
Process parameters
Inspection methods
Work instructions
Machine information
Tooling information
Previous trial results

Historical information can be particularly valuable.

For example, suppose a machining operation has repeatedly produced oversized holes because of tool wear.

If this problem has occurred repeatedly in production, the PFMEA team should not ignore that information simply because the current process document does not mention it.

Actual manufacturing history can provide important evidence about process risk.

Process Flow, PFMEA and Control Plan Relationship

One of the most important concepts in automotive quality management is the relationship between the Process Flow, PFMEA and Control Plan.

A simplified relationship is:

Process Flow → PFMEA → Control Plan → Work Instructions

Each document has a different purpose.

Process Flow

The Process Flow defines the sequence of manufacturing operations.

For example:

Incoming Material → Blanking → Forming → Piercing → Welding → Inspection → Packing

PFMEA

PFMEA studies each relevant operation and asks:

What can go wrong at this operation?

It identifies:

Failure modes
Effects
Causes
Prevention controls
Detection controls
Risk
Improvement actions

Control Plan

The Control Plan defines how important product and process characteristics will be controlled during production.

Work Instruction

The Work Instruction explains how the operator should perform the operation.

Therefore, these documents should work together rather than being prepared independently.

Example of Process Flow → PFMEA → Control Plan

Consider a CNC drilling process.

Process: CNC Drilling

Function: Produce a hole according to drawing requirement.

Failure Mode: Hole diameter oversize

Potential Effect: Assembly problem

Potential Cause: Tool wear

Prevention Control: Tool-life monitoring

Detection Control: Hole diameter inspection

The relevant control should then be appropriately reflected in the Control Plan.

This linkage is important because PFMEA should not become an isolated document that exists only for documentation purposes.

How to Conduct FMEA: Step-by-Step

A practical FMEA study can be carried out through a structured sequence.

1. Define the Scope

Before starting the analysis, clearly define:

Product
Process
Manufacturing location
Process boundaries
Customer requirements
Team members
Applicable methodology

The team should know exactly which process is being analyzed.

2. Understand the Actual Process

Review the Process Flow Diagram and understand every operation.

Where possible, the team should also visit and observe the actual production process.

This is important because the documented process and actual production process are not always identical.

For example, an instruction may specify one method, while operators may have developed another practical method over time.

Such differences may represent potential process risks and should be evaluated.

3. Identify Process Functions

For each process step, determine what the process is expected to accomplish.

For example:

Process: Drilling

Function: Produce a hole of specified diameter and position.

Another example:

Process: Torque tightening

Function: Tighten the fastener to the specified torque.

Clearly defining the function helps the team identify meaningful failure modes.

4. Identify Potential Failure Modes

The key question is:

What could go wrong?

Possible failure modes include:

Hole oversize
Hole undersize
Wrong component
Missing component
Incorrect torque
Burr present
Incorrect dimension
Surface damage
Incorrect welding
Wrong orientation
Part deformation
Crack
Dent
Scratch
Missing operation
Incorrect assembly

The failure mode should describe what could actually go wrong with the process output.

5. Identify Potential Effects

Next ask:

What happens if this failure occurs?

Possible effects include:

Assembly problem
Functional failure
Customer rejection
Process stoppage
Noise or vibration
Leakage
Reduced product life
Subsequent-process problem
Customer complaint
Safety-related effect

The effect should describe the consequence of the failure.

6. Identify Potential Causes

Now ask:

Why could this failure occur?

Possible causes include:

Tool wear
Incorrect machine parameter
Fixture misalignment
Incorrect material
Operator error
Sensor failure
Equipment malfunction
Improper maintenance
Incorrect work instruction
Incorrect tool setting
Incorrect component loading
Poor process parameter control

The cause should explain why the failure mode could happen.

Difference Between Failure Mode, Effect and Cause

This is one of the most important concepts for people preparing PFMEA.

Consider:

Hole oversize

This is the:

Failure Mode

The possible consequence:

Assembly problem

This is the:

Effect

The reason:

Tool wear

This is the:

Cause

So the relationship is:

Cause → Failure Mode → Effect

For example:

Tool wear → Hole oversize → Assembly problem

A PFMEA becomes much clearer when these three elements are not mixed together.

7. Identify Existing Controls

Existing controls can generally be considered as prevention and detection controls.

Prevention Controls

Prevention controls are intended to prevent a cause or failure from occurring.

Examples include:

Poka-yoke
Tool-life monitoring
Parameter control
Fixture design
Sensor interlock
Automated setting
Error-proofing
Standardized work
Preventive maintenance

Detection Controls

Detection controls are intended to identify a cause or failure before it progresses further.

Examples include:

Visual inspection
Vernier inspection
Go/No-Go gauge
Automated inspection
Sensor
Functional testing
SPC monitoring
Camera inspection
Measurement system

A strong PFMEA should consider both.

8. Evaluate Risk

The team then evaluates risk according to the applicable FMEA methodology.

Traditional FMEA commonly considers:

Severity
Occurrence
Detection

The AIAG & VDA methodology uses these ratings within its Action Priority approach.

The organization should use the applicable methodology rather than mixing rating systems from different approaches.

9. Identify Improvement Actions

When additional risk reduction is required, suitable actions should be identified.

An action should ideally have:

Clearly defined action
Responsible person
Target completion date
Status
Effectiveness verification

For example:

Action: Introduce poka-yoke for component orientation.

Responsible: Production Engineering

Target Date: Defined by project team

Verification: Confirm incorrect orientation cannot proceed through the process.

10. Verify Effectiveness

Completing an action does not automatically mean the risk has been eliminated.

The team should verify whether the action actually works.

For example, if a poka-yoke is installed, the team should verify that the error condition is genuinely prevented.

If a parameter-monitoring system is introduced, the team should verify that it detects or prevents the intended failure.

After verification, the PFMEA should be updated to represent the current process.

Severity in FMEA

Severity represents the seriousness of the effect of a potential failure.

Traditional FMEA systems commonly use a 1–10 ranking scale, although the exact criteria depend on the applicable methodology.

A lower Severity generally represents a less serious effect, while a higher Severity represents a more serious effect.

However, the actual rating should always be established using the applicable FMEA methodology, customer requirements and approved organizational criteria.

One important point is:

Severity relates to the effect of the failure, not simply to the cause.

For example:

Cause: Tool wear

Failure Mode: Hole oversize

Effect: Assembly or functional problem

Severity is associated with the consequence represented by the effect.

Occurrence in FMEA

Occurrence represents how frequently a failure cause or mechanism is expected to occur according to the applicable FMEA criteria.

Occurrence should preferably be supported by objective information.

Useful sources include:

Historical rejection data
Customer complaints
Warranty data
Process capability
Similar process data
Defect trends
Production records
Trial results

For example, if historical production data shows repeated defects caused by tool wear, this information should be considered during the occurrence evaluation.

Using actual evidence is generally more useful than simply selecting a rating based on personal opinion.

Detection in FMEA

Detection evaluates the effectiveness of existing controls in detecting a failure or its cause according to the applicable FMEA methodology.

Possible detection controls include:

Visual inspection
Vernier inspection
Micrometer
Go/No-Go gauge
Automated inspection
Sensor
Functional test
SPC monitoring
Camera inspection
Measurement system

However, detection should not become the only strategy.

Whenever practical, the team should ask:

Can we prevent the failure instead of only detecting it?

For example, suppose incorrect component orientation is possible during assembly.

A final inspection may detect the problem.

However, a properly designed poka-yoke may prevent the incorrect orientation from occurring in the first place.

This is why prevention should receive serious consideration during PFMEA development.

Understanding Risk Prioritization

Traditional FMEA has historically used the combination of Severity, Occurrence and Detection to support risk evaluation.

A commonly known calculation is:

RPN = Severity × Occurrence × Detection

For example:

Severity = 7

Occurrence = 5

Detection = 4

Therefore:

RPN = 7 × 5 × 4 = 140

However, RPN should not be treated as the only basis for deciding whether an action is required.

For example, a high-severity failure may require attention even if its calculated RPN is not the highest number in the PFMEA.

The AIAG & VDA FMEA methodology introduced Action Priority (AP) as a structured approach for prioritizing actions.

Therefore, organizations should clearly distinguish between traditional RPN-based approaches and the AIAG & VDA Action Priority methodology.

Practical PFMEA Example

Consider a CNC machining process used to manufacture an automotive component.

The requirement is that the hole diameter and position must meet the drawing specification.

A simplified PFMEA example is shown below.

Process	Failure Mode	Potential Effect	Potential Cause	Prevention Control	Detection Control
CNC Drilling	Hole oversize	Assembly problem	Tool wear	Tool-life monitoring	Diameter inspection
CNC Drilling	Hole undersize	Assembly problem	Incorrect tool	Tool specification	Gauge inspection
CNC Drilling	Hole position incorrect	Assembly rejection	Fixture misalignment	Fixture poka-yoke	Position inspection
CNC Drilling	Burr formation	Functional/assembly problem	Incorrect cutting condition	Parameter control	Visual inspection

The basic PFMEA relationship is:

Process → Failure Mode → Effect → Cause → Control

The actual risk ratings should be established using the applicable FMEA methodology and relevant customer requirements.

How to Select Effective PFMEA Controls

One common weakness in PFMEA is listing inspection activities without adequately considering prevention.

For example:

Weak approach

Inspect every component after production.

This may identify defective components, but it does not necessarily prevent the defect from being produced.

Stronger approach

Use a poka-yoke to prevent incorrect component loading.

The same principle can be applied to torque tightening.

Instead of depending only on manual verification after tightening, the process could use a controlled torque tool with parameter monitoring and appropriate error-proofing.

The general principle is:

Prevent the failure whenever reasonably possible instead of depending only on detection.

PFMEA Review and Update

PFMEA should be treated as a living document.

It should be reviewed whenever new information or process changes can affect manufacturing risk.

Typical review triggers include:

Customer complaints
Internal rejection
Recurring defects
Warranty issues
Engineering changes
Process changes
New machines
New tooling
New materials
Supplier changes
New inspection methods
Changes in process parameters
New products
New processes
Lessons learned
Corrective actions

For example, if a new machine is installed, the team should consider whether the new equipment introduces new risks.

Similarly, if a fixture is redesigned, the team should evaluate whether the fixture-related failure modes remain valid.

The PFMEA should represent the actual current manufacturing process.

Horizontal Deployment of PFMEA Lessons

An important part of effective quality management is learning from problems that have already occurred.

Suppose a production line experiences a problem because of incorrect fixture loading.

The organization should not only correct that particular line.

The team should also ask:

Could the same problem occur on another machine, line, product or process?

If the answer is yes, the lesson should be evaluated for horizontal deployment.

For example, if a poka-yoke successfully prevents incorrect component orientation on one production line, the organization can evaluate whether similar processes require comparable controls.

Horizontal deployment helps prevent the same type of failure from appearing elsewhere.

Common PFMEA Mistakes

A technically formatted PFMEA can still be ineffective if the analysis is weak.

Here are some common mistakes.

1. Preparing PFMEA Only for Audit

PFMEA should not be treated as an audit document created only because an auditor or customer may ask for it.

The purpose is to understand and reduce process risk.

2. Blindly Copying an Old PFMEA

Previous PFMEA information can be extremely useful.

However, copying an old PFMEA without reviewing the current process can result in missing important risks.

The current:

Machine
Tool
Material
Method
Process parameters
Inspection method
Product requirements

should be considered.

3. Poor Failure-Mode Descriptions

Failure modes should clearly describe what could go wrong.

For example:

Hole oversize

is clearer than writing:

Drilling issue

A specific failure mode makes subsequent analysis easier.

4. Confusing Causes and Effects

For example:

Failure Mode: Hole oversize

Effect: Assembly problem

Cause: Tool wear

The cause explains why the failure can occur.

The effect explains what happens because of the failure.

5. Depending Only on Inspection

Inspection can detect problems, but detection alone does not necessarily prevent the problem from being created.

Whenever possible, the team should investigate prevention controls.

6. Ignoring Process Data

Actual data such as:

Rejection
Scrap
Rework
Complaints
Process capability
Defect trends

can provide valuable evidence for the risk analysis.

7. Not Updating PFMEA After Changes

A changed process should trigger a review to determine whether the existing risk analysis is still valid.

8. Poor Linkage with Control Plan

Important controls identified through PFMEA should be appropriately reflected in the Control Plan.

The two documents should support each other.

9. No Cross-Functional Participation

PFMEA can become incomplete when it is prepared by only one department.

Production, quality, process, tooling, maintenance and other relevant functions can contribute different perspectives.

PFMEA and IATF 16949

PFMEA supports preventive quality management and risk-based thinking in automotive manufacturing.

It is closely connected with:

Process risk analysis
Product and process development
Process control
Control Plan development
Special-characteristic management
Lessons learned
Manufacturing process improvement
Customer-specific requirements

Organizations should distinguish between:

IATF 16949 requirements
Customer-specific requirements
AIAG & VDA FMEA methodology

These are related but should not be treated as exactly the same thing.

For specific compliance decisions, the applicable standard, customer requirements and approved organizational procedures should always be consulted.

PFMEA and Automotive Core Tools

PFMEA is closely connected with the other automotive Core Tools.

A simplified relationship can be represented as:

APQP → Process Flow → PFMEA → Control Plan → Work Instructions → SPC/MSA → PPAP

Each tool has its own purpose.

APQP

APQP provides structured quality planning for product and process development.

Process Flow

Process Flow defines the sequence of manufacturing operations.

PFMEA

PFMEA identifies potential process risks.

Control Plan

Control Plan defines how important characteristics and process controls will be managed.

Work Instructions

Work Instructions provide detailed operating instructions.

SPC

SPC helps monitor process variation and process performance.

MSA

MSA evaluates the suitability of measurement systems.

PPAP

PPAP provides evidence that the production process can meet applicable requirements.

Therefore, PFMEA should be developed as part of an integrated Core Tools system rather than as an independent document.

PFMEA Checklist

Before approving or releasing a PFMEA, the team can use the following practical checklist.

Process

Is the Process Flow available?
Does the PFMEA cover all relevant operations?
Are process functions clearly defined?
Does the PFMEA reflect the actual manufacturing process?

Failure Analysis

Are potential failure modes identified?
Are effects clearly defined?
Are causes identified?
Are the causes technically realistic?
Are important failure modes supported by process knowledge or historical information?

Controls

Are prevention controls identified?
Are detection controls identified?
Are important characteristics appropriately controlled?
Are prevention opportunities considered?

Risk

Are Severity ratings justified?
Are Occurrence ratings supported by available information?
Are Detection ratings appropriate?
Is the correct FMEA methodology being used?
Has the applicable customer requirement been considered?

Actions

Are improvement actions clearly defined?
Is responsibility assigned?
Is a target date defined?
Is action completion tracked?
Is effectiveness verified?

Linkage

Is PFMEA consistent with Process Flow?
Is PFMEA appropriately linked with the Control Plan?
Are applicable Work Instructions consistent?
Are lessons learned incorporated?
Has horizontal deployment been considered?

FMEA Occurrence Data Sheet

Historical process data can be useful when evaluating occurrence.

An FMEA Occurrence Data Sheet can help the PFMEA team record historical defect information and use evidence when considering occurrence ratings.

Such information can be useful for:

Quality Engineers
Process Engineers
Production Engineers
PFMEA teams
Automotive suppliers
Internal auditors
Quality trainees

The important point is that occurrence evaluation should ideally be supported by available process evidence rather than being based entirely on assumption.

Frequently Asked Questions About FMEA

What is FMEA?

FMEA stands for Failure Mode and Effects Analysis. It is a structured method used to identify potential failures, understand their effects and causes, evaluate associated risks and define actions to reduce those risks.

What is PFMEA?

PFMEA stands for Process Failure Mode and Effects Analysis. It is used to identify and manage potential failures associated with manufacturing and assembly processes.

What is the difference between FMEA and PFMEA?

FMEA is the broader failure-analysis methodology, while PFMEA specifically focuses on manufacturing and process risks.

What is DFMEA?

DFMEA stands for Design Failure Mode and Effects Analysis. It focuses on potential failures associated with product design and design requirements.

What is Severity in FMEA?

Severity represents the seriousness of the effect associated with a potential failure.

What is Occurrence in FMEA?

Occurrence represents how frequently a potential failure cause or mechanism is expected to occur according to the applicable FMEA criteria.

What is Detection in FMEA?

Detection evaluates the effectiveness of existing controls in detecting a failure or its cause according to the applicable FMEA methodology.

What is RPN in FMEA?

RPN stands for Risk Priority Number.

In traditional FMEA:

RPN = Severity × Occurrence × Detection

For example:

7 × 5 × 4 = 140

However, RPN should not be treated as the only basis for risk decisions.

Is RPN used in AIAG & VDA FMEA?

The AIAG & VDA methodology introduced Action Priority (AP) as a structured approach for prioritizing actions rather than relying only on the traditional RPN approach.

What are the 7 steps of AIAG & VDA FMEA?

The AIAG & VDA approach consists of:

Planning and Preparation
Structure Analysis
Function Analysis
Failure Analysis
Risk Analysis
Optimization
Results Documentation

For detailed information about these seven steps, refer to the dedicated AIAG & VDA Process FMEA article.

What is the relationship between PFMEA and Control Plan?

PFMEA identifies potential process risks and relevant controls, while the Control Plan defines how applicable product and process characteristics will be controlled during production.

When should PFMEA be reviewed?

PFMEA should be reviewed when there are process changes, customer complaints, internal failures, engineering changes, new products, new processes, lessons learned or other information that can affect process risk.

Who should participate in PFMEA?

PFMEA is ideally developed by a cross-functional team that may include Quality, Production, Process Engineering, Tooling, Maintenance, Manufacturing Engineering and other relevant technical functions.

Why is cross-functional participation important in PFMEA?

Different functions understand different parts of the process. A quality engineer may understand defect trends, a process engineer may understand machine parameters, while a tooling engineer may understand tool-related risks. Combining these perspectives can make the analysis more practical.

Should PFMEA be updated after a customer complaint?

A customer complaint should be evaluated as a potential PFMEA review trigger. If the complaint reveals a process risk that is missing or inadequately controlled, the PFMEA and related documents should be reviewed and updated as appropriate.

Should PFMEA contain only inspection controls?

No. PFMEA should consider both prevention and detection controls. Wherever reasonably possible, the team should look for ways to prevent the failure rather than depending only on final inspection.

Final Thoughts on FMEA and PFMEA

FMEA is an important preventive quality-management tool because it encourages organizations to identify risks before those risks become actual problems.

In automotive manufacturing, PFMEA provides a structured way to connect:

Process → Function → Failure Mode → Effect → Cause → Control → Risk → Action

A strong PFMEA should not be prepared simply because it is required for an audit, customer submission or project document.

It should be a practical engineering tool used by the people who understand the process.

The most useful PFMEA is based on:

Actual process knowledge
Historical data
Customer requirements
Previous problems
Process capability
Cross-functional experience
Lessons learned
Effective prevention and detection controls

It should also remain connected with the other automotive Core Tools.

The overall relationship can be summarized as:

APQP → Process Flow → PFMEA → Control Plan → Work Instructions → SPC/MSA → PPAP

The most important principle is simple:

Identify the risk before the failure reaches the customer, prevent the failure whenever reasonably possible, and continuously improve the process using evidence and lessons learned.

For automotive quality professionals, understanding PFMEA is therefore not just about knowing the terminology or filling an FMEA format. The real skill is being able to look at a manufacturing process and ask the right questions:

What can go wrong? Why can it happen? What happens if it happens? How can we prevent it? How will we detect it? And how do we know that our control is actually effective?

That is the practical thinking behind an effective PFMEA.