What is FMEA (failure mode and effects analysis)?

    Short answer

    Failure mode and effects analysis (FMEA) is a structured, team-based method for identifying the ways a product or process could fail, the effect of each failure, its causes and the controls in place, then ranking the risks by severity, occurrence and detection so that the highest can be reduced before the failure happens.

    Last updated · TeamAssurance

    Types of FMEA

    • Design FMEA (DFMEA) examines a product design for failure modes before it is released.
    • Process FMEA (PFMEA) examines a manufacturing or service process step by step.
    • System FMEA looks at interactions between subsystems.

    PFMEA is the most common on the shop floor and is required in automotive (IATF 16949) and expected in medical device and aerospace quality systems.

    The steps

    1. Define the scope and assemble a cross-functional team.
    2. List the process steps or functions.
    3. For each step, list the failure modes: the ways it could go wrong.
    4. Identify the effects of each failure on the customer or the next step and rate severity (S).
    5. Identify the causes and rate how often each occurs: occurrence (O).
    6. Identify current controls and rate how likely they are to catch the failure: detection (D).
    7. Prioritise. Traditionally S × O × D gives a risk priority number (RPN); the AIAG-VDA 2019 handbook replaced RPN with an action priority (AP) table.
    8. Define and take actions to reduce occurrence or improve detection, then re-rate.

    Common mistakes

    • Treating the FMEA as a document for the auditor rather than a living analysis.
    • Rating in a meeting room without the people who run the process.
    • Chasing the RPN total instead of the high-severity rows.
    • Never revisiting it after a failure actually occurs.

    FMEA and daily management

    An FMEA is a prediction; the tier board records what actually happened. Defects, near misses and breakdowns raised daily should feed back into the FMEA, and the actions the FMEA generates belong on the same action list as everything else, with owners and dates, rather than in a spreadsheet nobody opens.

    How TeamAssurance helps

    In TeamAssurance, the actions from an FMEA are tracked on the team's board with owners and due dates, the controls it relies on run as scheduled checks and layered audits, and the defects and near misses raised daily give the team the evidence to revisit the ratings.

    Frequently asked questions

    What is the difference between FMEA and root cause analysis?

    FMEA is done before a failure to prevent it; root cause analysis is done after a failure to find why it happened. Findings from one should update the other.

    What is a risk priority number?

    The product of severity, occurrence and detection ratings (each 1–10) in traditional FMEA. The newer AIAG-VDA method uses an action priority table instead, so that high severity is never outweighed by low occurrence.

    Who should be on an FMEA team?

    The people who run the process, plus engineering, quality and maintenance. An FMEA done by one engineer misses most of the real failure modes.