Failure Mode and Effects Analysis (FMEA) is a structured way to find what could go wrong with a product or process, judge how serious it would be, and decide what to do about it before it happens.
In automotive, the AIAG and VDA FMEA Handbook published in 2019 brought the American and German approaches together. It introduced a seven-step method and replaced the Risk Priority Number with Action Priority.
What is FMEA?
An FMEA looks at each function of a product or each step of a process and asks three questions: how could it fail, what would the effect be, and what causes the failure. For every cause, the team records the controls that prevent it or detect it, rates the risk and assigns actions where the risk is too high.
An FMEA is a living document. It should be updated when the design or process changes, when a customer complaint reveals a failure nobody predicted, and when actions are completed.
DFMEA vs PFMEA
The two most common types look at different sources of failure.
| Design FMEA (DFMEA) | Process FMEA (PFMEA) | |
|---|---|---|
| Focus | How the product design could fail to meet its function | How the manufacturing process could fail to make the part as designed |
| Owner | Design engineering | Manufacturing and process engineering |
| Typical causes | Wrong material choice, tolerance stack-up, weak geometry | Wrong setting, worn tool, missed operation, wrong part loaded |
| When | During product design and development | During process design, before the line is built |
| Feeds into | Design verification plan, special characteristics | Control plan, work instructions, error proofing |
The two are linked. A special characteristic identified in the DFMEA needs a matching control in the PFMEA and the control plan. The AIAG-VDA handbook also adds a supplemental FMEA for monitoring and system response (FMEA-MSR) for systems that detect and react to faults in use.
The 7 steps of the AIAG-VDA FMEA method
- Planning and preparation: define the scope, the team, the timing and the tools.
- Structure analysis: break the product or process into its elements, such as system, subsystem and component, or process item, process step and work element.
- Function analysis: describe what each element must do and the requirements it must meet.
- Failure analysis: link failure effects, failure modes and failure causes across the structure.
- Risk analysis: record prevention and detection controls and rate severity, occurrence and detection.
- Optimization: assign actions to reduce risk, with owners and dates, and re-rate once done.
- Results documentation: report the outcome and the actions taken to management and, where needed, the customer.
Steps two to four are what make the method different from older FMEAs. Building the structure and the function links first makes the failure chain explicit, so the causes in a PFMEA trace back to the effects that matter to the customer.
Action Priority vs RPN
Older FMEAs multiplied severity, occurrence and detection, each rated 1 to 10, into a Risk Priority Number (RPN). The problem is that very different risks can give the same number: a severity 10 with good controls can score lower than a minor issue with poor detection.
Action Priority (AP) replaces the multiplication with a lookup table that weights severity first, then occurrence, then detection. Each failure chain gets a priority of High, Medium or Low:
- High: action is required to improve prevention or detection, or a justification must be documented.
- Medium: action should be taken, or the reason for no action documented.
- Low: action could be taken.
Some customers still ask for RPN. Many teams keep both during the transition, but AP is the method the AIAG-VDA handbook expects.
From PFMEA to control plan
The control plan is where the PFMEA reaches the shop floor. Each prevention and detection control in the PFMEA should appear in the control plan with its method, sample size, frequency and reaction plan.
When the PFMEA and control plan are kept in separate files, they drift apart. A control is added to one but not the other, or a process step is renamed. Building the control plan directly from the PFMEA keeps them in step.
Common FMEA mistakes
- Writing the FMEA after the design or process is fixed, so it cannot change anything.
- Copying an old FMEA without reviewing what is different on the new part.
- Listing inspection as the only control for high-severity causes.
- Leaving actions open with no owner or due date.
- Never updating the FMEA after customer complaints or internal failures.
FMEA software
OperaHive FMEA software follows the seven AIAG-VDA steps for DFMEA and PFMEA, calculates Action Priority or RPN, tracks every action to closure and builds the control plan directly from the PFMEA.