Glossary

What Is FMEA (Failure Mode and Effects Analysis)? Manufacturing Guide

User Solutions TeamUser Solutions Team
|
5 min read
Industrial worker inspecting materials on a factory floor as part of a quality control process
Industrial worker inspecting materials on a factory floor as part of a quality control process

FMEA (Failure Mode and Effects Analysis) is a systematic, proactive method for identifying potential failure modes in a product or manufacturing process before they occur, assessing their consequences, and prioritizing corrective actions to prevent defects and downtime.

Definition

Failure Mode and Effects Analysis originated in the U.S. military in the 1940s (MIL-P-1629) and was later formalized by NASA and the automotive industry. Today it is a required practice in automotive (AIAG/VDA FMEA handbook), aerospace (AS9100), medical device (ISO 13485), and food manufacturing (analogous to HACCP hazard analysis).

At its core, FMEA asks three questions for every potential failure: How bad would it be if this failed? (Severity) How likely is it to happen? (Occurrence) How likely are we to catch it before it reaches the customer? (Detection). The answers drive a single priority score called the Risk Priority Number.

There are two primary types relevant to manufacturers. Design FMEA (DFMEA) is conducted during product development to assess whether the design itself could fail to meet requirements — it is owned by engineering. Process FMEA (PFMEA) is conducted for manufacturing and assembly operations to assess how process steps could fail to produce conforming parts — it is owned by operations and quality, and is the type most directly connected to production scheduling.

The FMEA RPN Formula

The Risk Priority Number is the central output of any FMEA:

RPN = Severity (S) × Occurrence (O) × Detection (D)

Each factor is scored on a 1–10 scale:

Factor1 (Low Risk)5 (Moderate)10 (High Risk)
SeverityNo effectDegraded performanceSafety/regulatory failure
OccurrenceFailure unlikelyOccasional failureFailure almost certain
DetectionCurrent controls will always detectControls may detectControls unlikely to detect

Maximum possible RPN is 1,000 (10 × 10 × 10). Teams typically flag all RPNs above 100–125 for corrective action. Any failure mode with a Severity of 9 or 10 should be addressed regardless of RPN — a highly severe failure that almost never happens and is always detected still warrants design controls.

The 7 FMEA Steps

  1. Define scope — which process, product, or sub-system is being analyzed, and what are the boundaries
  2. Identify function and requirements — what each process step must accomplish
  3. Brainstorm failure modes — for each function, list every way it could fail to perform
  4. Assess effects and rate Severity — what happens downstream if this failure mode occurs
  5. Identify causes and rate Occurrence — what causes the failure and how often it occurs under current controls
  6. Identify current controls and rate Detection — what inspections, sensors, or procedures exist to catch the failure before it reaches the customer
  7. Calculate RPN, prioritize, and assign corrective actions — implement controls, update the FMEA, and re-evaluate RPN after actions are verified

Manufacturing Example: CNC Milling PFMEA

A job shop running a CNC milling operation identifies three failure modes in its PFMEA:

Failure ModeEffectSCauseOCurrent ControlDRPN
Tool wear exceeds limitOversized part — customer reject8Insufficient tool life tracking6Operator visual check7336
Coolant flow failurePoor surface finish — rework required6Coolant pump wear4Weekly PM check5120
Fixture misalignmentPositional error — scrap9Worn fixture locating pin3First-article inspection4108

The tool wear failure mode (RPN 336) is the top priority. Corrective actions might include adding automatic tool-life monitoring in the CNC controller, inserting a mandatory tool change at a defined cycle count, and adding an intermediate dimensional check after every 50th part. After implementing controls, the team re-rates Detection from 7 to 3, dropping the RPN to 144.

Why FMEA Matters for Production Scheduling

FMEA directly informs how production schedules are built. High-RPN failure modes should have quality inspection holds built into the routing for that work center — a scheduler who does not know about a critical PFMEA risk may release jobs without adequate inspection time, only to discover scrap or rework late in the sequence.

FMEA also reveals where shorter scheduling intervals are needed. A process with an Occurrence rating of 8 or 9 requires more frequent sampling than one rated 2. Schedulers building capacity models should account for the time cost of the detection controls FMEA requires: in-process gauging, first-article inspections, and hold points are not free — they consume labor and equipment time that must appear in the schedule.

Industries where FMEA is mandatory or strongly expected include automotive (AIAG/VDA), aerospace (AS9100), medical device (ISO 13485 CAPA requirements), and food & beverage (HACCP-analogous hazard analysis).

How to Implement FMEA

  • Start with PFMEA for your highest-volume or highest-risk processes — do not attempt to FMEA everything at once
  • Cross-functional team is mandatory — include operators, process engineers, quality engineers, and (for DFMEA) design engineers
  • Use the current AIAG/VDA FMEA handbook (2019) — it replaced standalone AIAG 4th edition and VDA Volume 4 with a harmonized 7-step approach
  • Set an RPN threshold before scoring, not after — agreeing on 100 or 125 as the action threshold before scoring prevents motivated reasoning
  • Link corrective actions to the production schedule — each FMEA action item should have an owner, a due date, and a verification step that shows up in your production plan
  • Re-evaluate and close the loop — FMEA is not complete until revised RPN values are calculated after corrective actions are verified effective

FMEA (Failure Mode and Effects Analysis) is a structured, proactive risk assessment technique that identifies potential failure modes in a product or process, assesses their severity, likelihood of occurrence, and likelihood of detection, then calculates a Risk Priority Number (RPN) to guide corrective action prioritization.

RPN = Severity (1–10) × Occurrence (1–10) × Detection (1–10). The higher the RPN, the higher the risk priority. Teams typically address all failure modes with an RPN above a threshold (commonly 100–125) or any item with a Severity score of 9–10 regardless of RPN.

DFMEA (Design FMEA) evaluates potential failures in a product's design before it goes to production — it is owned by engineering. PFMEA (Process FMEA) evaluates potential failures in a manufacturing or assembly process — it is owned by operations and quality. PFMEA is the most directly relevant to production scheduling and shop-floor execution.


Learn more: See how RMDB and EDGEBI support FMEA-driven quality gate scheduling and process risk visibility. Contact User Solutions for a demo.

Expert Q&A: Deep Dive

Q: How often should a PFMEA be updated, and who owns it?

A: From 35 years of working with manufacturers, the teams that get the most value from PFMEA treat it as a living document, not a one-time compliance exercise. Update it whenever a process changes, a new failure mode is discovered on the floor, or a customer complaint triggers a corrective action. Ownership belongs to the process engineer or quality engineer for each work center, with sign-off from operations. If your PFMEA has not been touched in two years, it is almost certainly out of date.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together