Failure Mode and Effects Analysis (FMEA) is a structured method for identifying how a process, product or system could fail, what the consequences would be, why the failure might occur, and which controls should prevent or detect it. In supply-chain management, FMEA can be applied to procurement, warehousing, transportation, planning, order fulfilment, supplier quality and other operational processes.
The value of FMEA is not the score itself. The objective is to identify meaningful risks early, strengthen prevention and detection controls, assign actions and verify that risk has been reduced.
The Four Core FMEA Questions
| FMEA Element | Question | Supply Chain Example |
|---|---|---|
| Failure Mode | What could go wrong? | Supplier delivers late |
| Effect | What happens if it goes wrong? | Production stoppage or customer delay |
| Cause | Why could it happen? | Supplier capacity constraint |
| Control | What prevents or detects it? | Capacity review, order confirmation and exception monitoring |
Where FMEA Can Be Used in Supply Chains
- Procurement: supplier failure, incorrect specification, contract gaps, single-source dependency.
- Inbound logistics: late shipment, document error, customs hold, damaged cargo.
- Warehousing: wrong receipt, incorrect put-away, picking error, stock mismatch.
- Inventory planning: forecast error, incorrect parameter, stockout, expiry or obsolescence.
- Order fulfilment: wrong item, wrong quantity, late dispatch or incomplete documentation.
- Supplier quality: defect escape, inspection failure or inadequate corrective action.
A Practical FMEA Workflow
- Define the scope. Choose the process, product, supplier or operation to analyze.
- Map the process. Break the activity into clear steps so risks can be assessed at the right level.
- Identify the function of each step. Define what the step is supposed to achieve.
- Identify failure modes. Ask what could prevent the step from performing as intended.
- Identify effects. Record the operational, customer, quality, cost, compliance or safety consequences.
- Identify causes. Determine credible reasons the failure could occur.
- Document current prevention and detection controls.
- Assess risk. Use Severity, Occurrence and Detection ratings according to the organization’s chosen FMEA method.
- Prioritize and implement actions. Prefer prevention or error-proofing where practical.
- Reassess and close actions. Confirm that controls actually reduced risk.
Severity, Occurrence and Detection
| Rating | What It Represents |
|---|---|
| Severity (S) | How serious the effect would be if the failure occurred |
| Occurrence (O) | How likely the cause/failure is to occur |
| Detection (D) | How likely existing controls are to detect the issue before the effect reaches the customer or next process |
Organizations often use 1-to-10 rating scales, but the exact definitions should come from the FMEA standard or internal methodology being used. A number without a defined rating table is not meaningful.
Risk Priority Number (RPN)
The traditional Risk Priority Number is calculated as:
RPN = Severity × Occurrence × Detection
For example, consider a supplier delivery failure with:
- Severity = 8
- Occurrence = 5
- Detection = 6
RPN = 8 × 5 × 6 = 240.
After actions such as capacity monitoring, firm order confirmation and an alternate-source trigger, assume the ratings become:
- Severity = 8
- Occurrence = 2
- Detection = 2
Revised RPN = 8 × 2 × 2 = 32.
Why RPN Should Not Be Used Alone
Different combinations of Severity, Occurrence and Detection can produce the same RPN even though the risks are not equally important. A high-severity risk can therefore be hidden by a moderate overall number. For that reason, teams should review the individual ratings and the actual consequences rather than simply sorting a spreadsheet from highest to lowest RPN.
Action Priority in AIAG/VDA FMEA
In the automotive sector, the AIAG & VDA FMEA approach uses Action Priority (AP) rather than relying on RPN as the main prioritization method. AP evaluates combinations of Severity, Occurrence and Detection and classifies the need for action as High, Medium or Low. The methodology is designed to give appropriate weight to severity and encourage stronger prevention and detection controls.
RPN is still widely encountered in legacy FMEAs and in non-automotive organizations, so supply-chain professionals should understand both approaches and follow the methodology required by their company or customer.
Worked Supply Chain FMEA Example
| Process Step | Failure Mode | Effect | Cause | Current Control | Possible Action |
|---|---|---|---|---|---|
| Purchase order release | Incorrect quantity ordered | Excess stock or shortage | Wrong planning parameter / manual error | PO review | Automated tolerance check and parameter governance |
| Supplier delivery | Late shipment | Stockout or production delay | Capacity or transport issue | Supplier confirmation | Capacity review, milestone tracking, alternate-source trigger |
| Warehouse receiving | Wrong item accepted | Inventory error / wrong material issued | Identification error | Manual document check | Barcode verification and quarantine exception process |
| Customs clearance | Incorrect classification | Delay, reassessment or compliance exposure | Weak classification governance | Broker review | Controlled HS master and documented classification rationale |
Prevention Controls vs Detection Controls
Prevention controls reduce the chance that the failure occurs. Examples include approved-supplier qualification, system validation, capacity checks, standard work, poka-yoke and automated master-data rules.
Detection controls identify a problem before it progresses further. Examples include inspection, reconciliation, exception reports, barcode scanning, invoice matching and shipment milestone alerts.
Where practical, prevention is generally stronger than relying only on final detection.
Good FMEA Action Management
- Assign a clear action owner.
- Set a due date.
- Define the expected risk reduction.
- Verify implementation rather than closing on verbal confirmation.
- Re-rate the risk after the action is effective.
- Update related process maps, control plans, procedures or training where necessary.
- Review the FMEA after major process, supplier, system or product changes.
Common FMEA Mistakes
- Using vague failure modes such as “supplier problem.”
- Confusing the failure mode with its cause or effect.
- Assigning scores without defined rating criteria.
- Using RPN as the only decision rule.
- Listing existing controls that are not actually performed.
- Creating actions without owners or due dates.
- Completing the FMEA once and never updating it.
- Performing FMEA without first understanding the process flow.
Interview Question: How Would You Use FMEA in Supply Chain?
A strong answer is: I would map the process, identify each step’s potential failure modes, effects and causes, document prevention and detection controls, assess risk using the organization’s FMEA method, prioritize actions, assign owners and then reassess the ratings after the controls are implemented. I would not rely on RPN alone for high-severity risks.
Related SCMANA Guides
References
- American Society for Quality (ASQ), Failure Mode and Effect Analysis (FMEA)
- AIAG, AIAG & VDA FMEA Handbook
Download the Practical Workbook
Use the SCMANA FMEA RPN Template to document failure modes, score Severity, Occurrence and Detection, calculate RPN and track actions.
