Skip to content

KPIs, strategy & continuous improvement

FMEA explained: failure mode and effects analysis with an example

How to run an FMEA: identifying failure modes, rating severity, occurrence and detection, calculating RPN, prioritizing actions, with a worked example.

Failure mode and effects analysis (FMEA) is a structured way to anticipate what could go wrong in a process or product, how serious it would be, and what to do about it before it happens. Where CAPA reacts to problems that occurred, FMEA prevents them. It is widely used in manufacturing, healthcare, food safety and any process where failures are costly.

Key terms

TermMeaning
Failure modeHow a step could fail (for example, wrong label applied)
EffectWhat happens if it fails (customer receives wrong product)
CauseWhy the failure could happen (similar labels stored together)
Severity (S)How serious the effect is, rated 1 (minor) to 10 (hazardous)
Occurrence (O)How likely the cause is, rated 1 (rare) to 10 (frequent)
Detection (D)How likely current controls catch it before it reaches the customer, rated 1 (certain) to 10 (unlikely)
RPNRisk priority number = S × O × D

The FMEA process

  1. Define scope: which process or product, and its boundaries.
  2. Build the team: people who know the process, quality and engineering.
  3. Map the process steps.
  4. List failure modes for each step.
  5. Identify effects and causes for each failure mode.
  6. List current controls for prevention and detection.
  7. Rate S, O and D using agreed scales.
  8. Prioritize failure modes by severity first, then RPN or action priority.
  9. Define actions to reduce occurrence or improve detection, with owners and dates.
  10. Re-rate after actions are implemented.

Worked example: product labeling

StepFailure modeEffectCauseCurrent controlSODRPN
Apply labelWrong label appliedWrong product information reaches customer; possible recallSimilar labels stored togetherVisual check by operator845160
Print batch codeBatch code missingCannot trace productPrinter ribbon runs outHourly check63472
Seal packageWeak sealProduct spoilsHeater temperature driftStart-of-shift test736126

Actions for the highest risk: separate label storage by product, add barcode verification at the labeling station. After implementation: S stays 8, O falls to 2, D falls to 2. New RPN = 32.

Prioritizing well

  • Severity first: a high-severity failure deserves attention even with a modest RPN.
  • RPN limitations: different combinations can produce the same RPN. Some industry handbooks now use an action priority approach that weighs severity, occurrence and detection in combination rather than multiplying them. Use the approach your customers or standards require.
  • Prefer prevention: reducing occurrence is usually better than relying on detection.

Where FMEA is useful

  • New production lines or product launches
  • Changes in materials, suppliers or equipment
  • Processes with safety or regulatory risk
  • High-cost failures, such as payroll errors affecting thousands of employees
  • After a serious incident, to look for similar risks elsewhere

Keeping FMEAs alive

An FMEA filed away after launch loses value. Update it when processes change, when failures occur that were not anticipated, and when actions are completed. Link high-risk items to CAPA and to quality control plans.

Where Cirquolus fits

The Cirquolus improvement portfolio includes FMEA workspaces along with DMAIC, DMADV, PDCA, CAPA, Kaizen, Lean and project management, connected to Business Compass KPI.

Frequently asked questions

What is FMEA?

A structured method for identifying potential failures in a process or product, assessing their risk and planning actions to prevent them.

How is RPN calculated?

Risk priority number = severity × occurrence × detection, each rated on a scale, commonly 1 to 10.

What is the difference between FMEA and CAPA?

FMEA anticipates potential failures before they happen. CAPA addresses problems that have occurred or been identified.

Who should participate in an FMEA?

People who know the process well, including operators, engineers and quality staff, guided by a facilitator.

Bring this workflow to a Cirquolus demo.

Show us your current process, companies and branches. We will map it to the modules you need and propose a realistic rollout.