Qhubio

    What is FMEA? Complete Guide to Failure Mode and Effects Analysis

    FMEA (Failure Mode and Effects Analysis) is a structured risk analysis method used to identify and prevent failures in processes, products, or systems based on their impact, likelihood, and detectability.

    This guide explains FMEA methodology, steps, and real-world application.

    FMEA is a proactive method used before failures occur, not after. It is applied across manufacturing, automotive, aerospace, and quality management systems to identify and mitigate potential failures before they reach customers.

    FMEA is widely used in automotive, aerospace, and manufacturing industries and is required by standards such as IATF 16949 and ISO 9001.

    Want to see how FMEA works in a real scenario? See a real Process FMEA example

    FMEA Steps: How Failure Mode and Effects Analysis Works

    The six-step logic behind every failure analysis

    1

    Process Step

    What is being done?

    2

    Failure Mode

    What could go wrong?

    3

    Effect

    What is the impact?

    4

    Cause

    Why does it happen?

    5

    Controls

    How do we catch it?

    6

    Action

    What do we do?

    What is FMEA?

    FMEA is a bottom-up analytical technique that systematically examines each potential failure mode in a process or design. For every failure mode identified, the team evaluates its effect on the system, its root cause, and the effectiveness of current controls. FMEA is often referred to as PFMEA (Process FMEA) when applied to manufacturing processes.

    If you are searching for "what is FMEA" or "FMEA explained", this guide covers both fundamentals and real applications.

    The goal is not to eliminate all risk — it is to prioritize actions where they matter most. FMEA is required or recommended by ISO 9001, IATF 16949, AS9100, and numerous industry-specific quality standards.

    See a real Process FMEA example to understand how ratings are applied in practice.

    To understand how FMEA is applied step by step, see the FMEA steps.

    Why Use FMEA?

    FMEA helps organizations prevent failures before they occur by systematically identifying risks and prioritizing actions.

    FMEA helps reduce audit findings, customer complaints, and field failures by identifying risks early.

    It is used to:

    • Improve product quality and process reliability
    • Reduce warranty costs and defects
    • Ensure compliance with standards such as IATF 16949 and ISO 9001
    • Focus engineering effort on the highest-risk issues

    Common FMEA Mistakes (From Real Practice)

    • Overestimating detection capability — assuming controls are more effective than they actually are, leading to hidden risks
    • Treating FMEA as documentation instead of an active risk management tool used in decision-making
    • Using vague failure modes (e.g., "defect") instead of specific mechanisms that can be analyzed
    • Jumping directly to actions without identifying root causes, reducing effectiveness of mitigation
    • Using RPN thresholds instead of AIAG-VDA Action Priority logic, leading to incorrect prioritization

    These mistakes often lead to underestimated risks and audit findings in real-world implementations.

    Types of FMEA

    Process FMEA (P-FMEA)

    Focuses on manufacturing and assembly processes. Examines how process variables, tooling, operator actions, and environmental factors can lead to defective output.

    Design FMEA (D-FMEA)

    Analyzes potential failures in product design before manufacturing begins. Focuses on material selection, geometry, tolerances, and functional interfaces.

    System / Application FMEA

    Examines interactions between subsystems at a higher level. Used in early development to identify failure modes from system integration or functional dependencies.

    Core Elements: Severity, Occurrence, Detection

    Every failure mode in an FMEA is evaluated against three independent scales, each rated from 1 to 10:

    Severity (S)

    Impact on the customer or downstream process
    Low (1–3)

    Minor cosmetic defect

    Medium (4–7)

    Product rework required

    High (8–10)

    Safety hazard / regulatory breach

    Occurrence (O)

    Likelihood the root cause will produce the failure
    Low (1–3)

    Rare — proven, stable process

    Medium (4–7)

    Occasional — known variability

    High (8–10)

    Frequent — no effective prevention

    Detection (D)

    Ability of current controls to catch the failure
    Low (1–3)

    Automated 100% inspection

    Medium (4–7)

    Periodic sampling / SPC

    High (8–10)

    No detection method exists

    Risk Matrix (Severity × Occurrence)

    The risk matrix visualizes how Severity and Occurrence combine to determine the overall risk level of a failure mode. Each cell represents the relative risk level based on the combination of Severity and Occurrence.

    • Severity (Y-axis) — Impact of the failure on the customer or system
    • Occurrence (X-axis) — Likelihood of the failure cause occurring

    Higher severity and higher occurrence result in higher risk, requiring prioritized action.

    Med
    High
    High
    High
    High
    Med
    Med
    High
    High
    High
    Low
    Med
    Med
    High
    High
    Low
    Low
    Med
    Med
    Med
    Low
    Low
    Low
    Med
    Med
    Occurrence →
    Severity ↑

    Action Priority (AIAG-VDA) vs. RPN

    The traditional Risk Priority Number (RPN = S × O × D) has a well-documented flaw: it treats all combinations equally. An RPN of 120 could mean S=10, O=3, D=4 (safety-critical) or S=3, O=5, D=8 (minor nuisance) — same number, vastly different risk.

    The AIAG-VDA FMEA Handbook (1st Edition, 2019) replaced RPN with Action Priority (AP), a logic-based classification. The AIAG-VDA methodology harmonizes American (AIAG) and German (VDA) standards into a unified approach widely used in the automotive industry.

    Action Priority (AP) uses a rule-based approach to determine whether action is required. Unlike RPN, AP prioritizes Severity first, ensuring that high-impact failures are always addressed — even if occurrence is low or detection is strong. Each cell in the grid below indicates the required Action Priority (H, M, L) based on Severity and Occurrence.

    M
    M
    H
    H
    H
    L
    M
    M
    H
    H
    L
    L
    M
    M
    H
    L
    L
    L
    M
    M
    L
    L
    L
    L
    M
    Occurrence →
    Severity ↑
    High — Mandatory action required
    Medium — Action recommended
    Low — Action optional

    Unlike RPN, Action Priority ensures Severity always dominates the decision. A safety-critical failure is never masked by low occurrence.

    Simplified Process FMEA Example

    Below is a condensed example from a manufacturing welding process:

    Process StepFailure ModeEffectCauseSODAP
    Spot WeldingCold weld / incomplete fusionJoint separation under loadElectrode wear946High
    Surface TreatmentInsufficient coating thicknessCorrosion within warranty periodBath concentration drift654Medium
    Final InspectionMissed dimensional deviationCustomer complaintGauge calibration error423Low

    Or compare manual vs structured approaches: FMEA template comparison

    Frequently Asked Questions

    Stop Building FMEAs Manually

    Generate a complete, AIAG-VDA compliant Process FMEA in seconds — with calculated Action Priority and export-ready output.

    Try the FMEA Generator