What is an FMEA?
An FMEA is a team-based risk analysis that lists potential failures, rates each one and defines actions to reduce the highest risks. Teams use it in development, production and maintenance, and it is widely used in automotive and other manufacturing sectors.
Think of it as a pre-flight checklist for a process. Pilots check the engine before takeoff, and an FMEA does the same for your production line.
The US military developed FMEA in the 1940s, and the method later spread to other industries. Today, the AIAG & VDA FMEA Handbook from the US and German automotive industry groups is the common reference in automotive.
Three types cover most needs:
Design FMEA (DFMEA): It checks how a product design could fail before production starts.
Process FMEA (PFMEA): It checks how each manufacturing or assembly step could produce a defect.
System FMEA: It checks how subsystems and their interfaces could fail as a whole.
On a production line, the PFMEA is usually where you start, and this article focuses on it.
How to run an FMEA step by step
The AIAG/VDA approach structures an FMEA in seven steps, from planning the scope to documenting the results. Work through them in order with a cross-functional team.
1. Planning and preparation
Set the scope, boundaries, team and timeline before rating any risk. Invite people from quality, production, maintenance and engineering, because each group sees different failures.
2. Structure analysis
Break the process into its individual steps, usually as a process flow. For a PFMEA, that could be one assembly line split into receiving, pressing, testing and packing.
3. Function analysis
Describe what each step must achieve. Write each function as a verb plus a noun, such as "press bearing into housing," and add the requirement it must meet, such as full seating depth. Clear functions make failures visible, because a failure is any way the function falls short.
4. Failure analysis
Build the failure chain for each function: the failure effect, the failure mode and the failure cause. The effect is what the customer or the next step experiences. The mode is how the step fails, and the cause is why. Keeping them apart separates symptoms from root causes.
5. Risk analysis
Rate each failure chain for severity, occurrence and detection on a scale of 1 to 10. First, list the current prevention and detection controls, because they shape the occurrence and detection scores.
6. Optimization
Define actions for the risks with the highest priority. Every action needs one owner and one deadline, or it tends to stall after the workshop. Once an action is complete, re-rate the failure chain to confirm the risk dropped.
7. Results documentation
Record the results and share them with management and, where required, the customer. Feed confirmed controls into the control plan and your ISO 9001 documentation. Treat the FMEA as a living document and update it whenever the process, product or failure data changes.
Risk priority number vs. action priority
The risk priority number (RPN) multiplies the ratings for severity, occurrence and detection, each from 1 to 10. The AIAG/VDA handbook uses Action Priority (AP) instead, which ranks risks as high, medium or low and gives severity more weight.
A quick calculation shows the problem. A failure with severity 7, occurrence 5 and detection 6 has an RPN of 7 x 5 x 6, or 210. A failure with severity 9, occurrence 2 and detection 3 scores only 54. Ranked by RPN, the more severe risk drops far down the list.
AP uses lookup tables instead of multiplication. Each combination of the three ratings maps to high, medium or low, and the tables give severity the most weight.
When the RPN still works:
Legacy customer requirements: Older customer requirements may still refer to RPN values.
Non-automotive sectors: Many teams outside automotive use the RPN because their standards or customers never moved to AP.
Internal comparison: The RPN lets you compare older and newer FMEAs on one scale.
Any RPN threshold that triggers action is a company convention. Agree on it with your team and customers.
FMEA example from production
A process FMEA for a single production step shows the method at small scale: one process step, two or three failure modes, their ratings and the actions that bring the risk down. Here is a PFMEA for pressing a bearing into a housing.
The first failure mode carries the highest risk:
Failure mode: Bearing not fully seated in the housing
Effect: Noise and early bearing failure at the customer
Cause: Press force drifts over time
Ratings: Severity 8, occurrence 5, detection 6 for an RPN of 240
Action: Add force-displacement monitoring to the press
Owner and deadline: Maintenance lead, due in four weeks
The second failure mode is less severe:
Failure mode: Bearing damaged during pressing
Cause: Misaligned fixture
Ratings: Severity 7, occurrence 3, detection 5 for an RPN of 105
Action: Add a poka-yoke locating pin to the fixture
Owner: Production engineer
After the maintenance lead installs the monitoring, the team re-rates failure mode 1. Severity stays at 8, because the effect on the customer hasn't changed.
Occurrence drops to 3 and detection drops to 2, so the RPN falls to 48. Teams that use AP look up each severity, occurrence and detection combination in the handbook's AP table.
FMEA template
An FMEA template captures each failure mode in one row: process step, failure mode, effect, cause, severity, occurrence, detection, priority, action, owner, deadline and status. Most teams start in a spreadsheet.
Process step: The operation you analyze
Failure mode: How the step can fail
Effect: What the customer or next step experiences
Cause: Why the failure happens
Severity: Rating from 1 to 10 for the effect
Occurrence: Rating from 1 to 10 for how often the cause occurs
Detection: Rating from 1 to 10, where 10 means controls will likely miss it
Priority: RPN or AP level
Action: The measure that lowers the risk
Owner: One named person
Deadline: Date the action is due
Status: Open, in progress, verifying or done
For a PFMEA, add columns for current prevention and detection controls. Dedicated FMEA software helps with many linked analyses, while a spreadsheet covers most single-line FMEAs.
The template works best when you separate analysis from execution. Keep the analysis in the FMEA sheet. Then move each action into MeisterTask as a task with an owner, a due date and a link back to the FMEA row.
How to track FMEA actions to completion in MeisterTask
An FMEA only lowers risk if its actions get done and their effect is checked. In MeisterTask, each action becomes a task with one owner and one deadline, and sections show where every action stands.
FMEAs often hold sensitive production data, and MeisterTask is hosted in Germany and ISO 27001 certified. The setup below follows the press-fit action until the fix is verified.
1. Set up one project per FMEA
Create one MeisterTask project for each FMEA, such as "PFMEA press-fit line 2." Add four sections: Open, In progress, Verify effectiveness and Done.
2. Turn each action into a task
Each action becomes a task with one named assignee and a due date. For failure mode 1, the task "Add force-displacement monitoring" goes to the maintenance lead, due in four weeks. A checklist holds the sub-steps, such as ordering, installing and testing the sensor. The description holds the FMEA row reference, so anyone can trace the task to its risk.
3. Schedule the review meeting as a recurring task
Set up a recurring task for the FMEA review meeting, for example every two weeks. In each review, the team checks tasks in Verify effectiveness and agrees on new ratings. Log those ratings in the task comments, such as "O 3, D 2, RPN 48," and update the FMEA sheet to match. The team does the rating, and MeisterTask keeps the record.
4. Add rule-based automations
MeisterTask's rule-based automations take over routine follow-up. For example, set an automation that notifies the quality lead when a task moves into Verify effectiveness. Automations are rule-based: they run when a condition you set is met, and they make no AI predictions.
In the press-fit example, the task moves to In progress when the maintenance lead orders the sensor. It lands in Verify effectiveness once monitoring runs, and moves to Done after the review confirms the new ratings.
Common FMEA mistakes
Most FMEAs fail for four reasons: the analysis is done alone instead of as a team, ratings are guessed instead of based on data, actions have no owner and nobody checks whether the actions worked.
Working alone. When one engineer fills in the FMEA at their desk, the analysis reflects one point of view. Operators and technicians know failure causes that never reach a report. Run the workshop with the cross-functional team from step one.
Guessing the ratings. Gut-feeling ratings make the priority meaningless. Back up each occurrence and detection score with scrap rates, complaints and test results. If you plan preventive maintenance, its logs add failure history too.
Leaving actions without an owner. An action assigned to "production" belongs to nobody. Name one person and one deadline for every action, and track it where you coordinate production work without ERP.
Skipping the effectiveness check. A completed action doesn't prove that the risk dropped. Re-rate the failure chain once the action is done, and confirm the new scores with data.
Turn risk analysis into finished work
An FMEA template gives your team a shared structure, and the seven steps keep the analysis thorough. Risk only goes down when someone completes each action and the team proves it worked.
With project management for manufacturing, MeisterTask keeps that follow-up visible and secure. Every action has an owner, a due date and a clear status. Start with one FMEA project, and let your next review show how many risks you've closed.
