FMEA Template: Failure Mode and Effects Analysis

Comprehensive FMEA template and guide for systematic risk assessment and failure prevention

Introduction to FMEA

Failure Mode and Effects Analysis (FMEA) is a systematic, proactive method for evaluating a process, product, or system to identify potential failure modes and their causes and effects. FMEA helps teams prioritize potential failures based on their severity, occurrence, and detectability, enabling focused improvement efforts and risk mitigation strategies.

Originally developed by the U.S. military in the 1940s and later adopted by the aerospace and automotive industries, FMEA has become a cornerstone tool in Six Sigma, quality management, and risk assessment. It provides a structured approach to prevent failures before they occur, reducing costs, improving quality, and enhancing customer satisfaction.

Key Benefits of FMEA

Proactive Risk Management

Identifies potential failures before they occur in production or service delivery

Cost Reduction

Prevents costly failures, recalls, and customer dissatisfaction

Improved Quality

Enhances product and process reliability through systematic analysis

Knowledge Capture

Documents team expertise and lessons learned for future reference

Regulatory Compliance

Supports compliance with industry standards and regulatory requirements

Team Collaboration

Facilitates cross-functional teamwork and knowledge sharing

Types of FMEA

Different types of FMEA are used depending on the focus and stage of development. Understanding when and how to use each type is crucial for effective risk management.

Design FMEA (DFMEA)

Purpose

Analyzes potential failure modes in product or system design before production begins.

Focus Areas

  • Component failures and their effects
  • Interface and integration issues
  • Design specification violations
  • Safety and performance concerns

When to Use

  • During product design phase
  • Before design freeze decisions
  • When modifying existing designs
  • For safety-critical applications

Process FMEA (PFMEA)

Purpose

Analyzes potential failure modes in manufacturing or service processes.

Focus Areas

  • Process step failures
  • Equipment malfunctions
  • Human errors
  • Material defects
  • Environmental factors

When to Use

  • During process development
  • Before process implementation
  • When processes are changed
  • For continuous improvement

System FMEA (SFMEA)

Purpose

Analyzes potential failure modes at the system or subsystem level.

Focus Areas

  • System-level interactions
  • Interface failures
  • Integration issues
  • System performance degradation

When to Use

  • Early in system design
  • For complex system integration
  • When defining system requirements
  • For system-level safety analysis

Service FMEA

Purpose

Analyzes potential failure modes in service delivery processes.

Focus Areas

  • Service delivery failures
  • Customer interaction issues
  • Information processing errors
  • Communication breakdowns

When to Use

  • For service process design
  • Customer experience improvement
  • Service quality enhancement
  • Risk management in services

FMEA Template

The FMEA template provides a structured format for conducting failure mode and effects analysis. This standardized approach ensures consistency and completeness in the analysis process.

FMEA Header Information

FMEA Information

  • FMEA Type: Design/Process/System/Service
  • FMEA Title: Descriptive name of the analysis
  • FMEA Number: Unique identifier
  • Page: ___ of ___

Project Information

  • Product/Process: Name of item being analyzed
  • Model/Part Number: Specific identifier
  • Revision: Current version
  • Core Team: Team member names

Dates and Responsibility

  • FMEA Date: Original creation date
  • Revision Date: Latest update date
  • Prepared By: Primary analyst
  • Approved By: Authorization signature

FMEA Analysis Table

Item/
Function		 Potential
Failure Mode		 Potential Effect(s)
of Failure		 SEV Potential Cause(s)/
Mechanism(s)		 OCC Current Process
Controls		 DET RPN Recommended Action Action
Results
Actions Responsibility Target
Date		 Action
Taken
[Function or
Component]		 [How it could fail] [Impact of failure] [1-10] [Why it fails] [1-10] [Current controls] [1-10] [S×O×D] [Improvement
actions]		 [Who] [When] [What was done] [New S,O,D,RPN]
Template Instructions:
• Fill out one row for each potential failure mode
• Use team consensus for severity, occurrence, and detection ratings
• Focus on highest RPN values for improvement actions
• Track action items to completion and re-evaluate ratings

Column Definitions

Item/Function

The component, process step, or function being analyzed

Potential Failure Mode

The way in which the item could potentially fail to meet requirements

Potential Effects of Failure

The consequences or impact of the failure on the customer or next process

SEV (Severity)

Rating (1-10) of how serious the effect of failure would be

Potential Causes

The underlying reasons or mechanisms that could cause the failure

OCC (Occurrence)

Rating (1-10) of how frequently the cause is likely to occur

Current Controls

Existing measures to prevent the cause or detect the failure

DET (Detection)

Rating (1-10) of how likely current controls will detect the problem

RPN (Risk Priority Number)

Calculated risk score (Severity × Occurrence × Detection)

FMEA Process Steps

Conducting an effective FMEA requires a systematic approach following established steps. This process ensures thorough analysis and actionable results.

1

Planning and Preparation

Key Activities

  • Define the scope and boundaries of the analysis
  • Assemble a cross-functional team with relevant expertise
  • Gather necessary documentation (drawings, specifications, procedures)
  • Schedule sufficient time for thorough analysis
  • Set up meeting logistics and documentation tools

Team Composition

  • Design Engineers: Technical expertise on the product/process
  • Manufacturing Engineers: Production and assembly knowledge
  • Quality Engineers: Quality systems and failure analysis experience
  • Field Service/Customer Service: Customer perspective and field failure data
  • Suppliers: Component and material expertise (when applicable)
2

Define Functions and Requirements

Key Activities

  • List all functions performed by the item being analyzed
  • Define performance requirements and specifications
  • Identify customer expectations and critical-to-quality characteristics
  • Document interfaces and interactions with other systems
  • Consider both intended and unintended functions

Function Definition Guidelines

  • Use verb-noun format (e.g., "transmit power," "seal connection")
  • Be specific about what the function accomplishes
  • Include quantitative requirements when possible
  • Consider functions under different operating conditions
3

Identify Potential Failure Modes

Key Activities

  • Brainstorm ways each function could fail to meet requirements
  • Consider complete failure, partial failure, and intermittent failure
  • Review historical failure data and lessons learned
  • Think about failure modes under different conditions
  • Consider both immediate and gradual failure modes

Common Failure Mode Categories

  • Performance: Does not meet specification limits
  • Structural: Cracks, breaks, deforms
  • Functional: Does not operate as intended
  • Appearance: Cosmetic or aesthetic issues
  • Timing: Early or late operation
4

Analyze Effects and Causes

Effects Analysis

  • Determine the consequences of each failure mode
  • Consider local effects, system effects, and end effects
  • Think from the customer's perspective
  • Include safety, regulatory, and business impacts

Cause Analysis

  • Identify root causes for each failure mode
  • Use techniques like 5-Whys or fishbone diagrams
  • Consider design, process, material, and environmental causes
  • Be specific about cause mechanisms
5

Rate Severity, Occurrence, and Detection

Rating Guidelines

  • Use team consensus for all ratings
  • Base ratings on current design and process
  • Use company-specific rating scales when available
  • Document rationale for ratings
  • Review and validate ratings with subject matter experts

Rating Consistency

  • Calibrate team on rating scales before starting
  • Use examples to establish common understanding
  • Compare similar items for consistency
  • Have external reviewers validate critical ratings
6

Calculate RPN and Prioritize

RPN Calculation

  • Calculate RPN = Severity × Occurrence × Detection
  • Identify highest RPN values for priority attention
  • Consider other prioritization criteria beyond RPN
  • Look for patterns in high-risk areas

Prioritization Considerations

  • High severity ratings (≥8) regardless of RPN
  • Safety and regulatory requirements
  • Customer critical characteristics
  • Cost and feasibility of improvements
  • Available resources and timeline
7

Develop Action Plans

Action Planning

  • Focus on highest priority failure modes
  • Develop specific, actionable improvement plans
  • Assign responsibility and target dates
  • Consider prevention vs. detection approaches
  • Evaluate cost-benefit of proposed actions

Types of Actions

  • Design Changes: Modify design to eliminate failure modes
  • Process Improvements: Enhance manufacturing or service processes
  • Control Enhancements: Add or improve detection methods
  • Procedure Updates: Improve work instructions and training
  • Testing Additions: Add validation and verification activities
8

Implement and Follow Up

Implementation

  • Execute improvement actions according to plan
  • Track progress against milestones
  • Communicate status to stakeholders
  • Document changes and lessons learned

Follow-Up Activities

  • Re-evaluate ratings after actions are implemented
  • Calculate new RPNs and verify improvement
  • Update FMEA documentation
  • Plan for ongoing review and maintenance
  • Share learnings with other projects

FMEA Rating Scales

Consistent rating scales are essential for effective FMEA. These scales provide standardized criteria for evaluating severity, occurrence, and detection.

Severity Rating Scale (1-10)

Rates the seriousness of the effect of the potential failure mode on the customer.

Rating Severity Level Criteria Examples
10 Hazardous without warning Failure could cause death or serious injury without warning Loss of braking, toxic emission
9 Hazardous with warning Failure could cause death or serious injury with warning Warning lights for critical systems
8 Very High Failure causes loss of primary function, non-compliance Vehicle won't start, regulatory violation
7 High Failure causes reduced performance, customer dissatisfaction Reduced fuel economy, noise
6 Moderate Failure causes loss of comfort or convenience function Radio doesn't work, minor leaks
5 Low Failure causes customer annoyance Squeaks, minor fit issues
4 Very Low Failure noticed by most customers Minor cosmetic defects
3 Minor Failure noticed by discriminating customers Slight color variation
2 Very Minor Failure may not be noticed by customers Very minor appearance issues
1 None No effect on customer No discernible impact

Occurrence Rating Scale (1-10)

Rates how frequently the cause or mechanism of failure is likely to occur.

Rating Occurrence Level Possible Failure Rate Criteria
10 Very High ≥ 1 in 2 Failure is almost certain
9 Very High 1 in 3 Very high occurrence rate
8 High 1 in 8 High occurrence rate
7 High 1 in 20 Moderately high occurrence
6 Moderate 1 in 80 Moderate occurrence rate
5 Moderate 1 in 400 Occasional occurrences
4 Low 1 in 2,000 Relatively few occurrences
3 Low 1 in 15,000 Low occurrence rate
2 Very Low 1 in 150,000 Very low occurrence rate
1 Remote ≤ 1 in 1,500,000 Occurrence is remote

Detection Rating Scale (1-10)

Rates the likelihood that current controls will detect the failure mode or its cause.

Rating Detection Level Criteria Types of Controls
10 Absolute Uncertainty Controls cannot or will not detect No controls in place
9 Very Remote Very remote chance of detection Random inspection only
8 Remote Remote chance of detection Manual inspection methods
7 Very Low Very low chance of detection Visual inspection only
6 Low Low chance of detection Manual measurement methods
5 Moderate Moderate chance of detection Statistical sampling methods
4 Moderately High Moderately high chance 100% manual inspection
3 High High chance of detection Automated inspection methods
2 Very High Very high chance of detection 100% automated inspection
1 Almost Certain Controls almost certain to detect Error-proofing methods

RPN Calculation and Interpretation

The Risk Priority Number (RPN) provides a numerical ranking to help prioritize improvement efforts. Understanding how to calculate and interpret RPN values is crucial for effective FMEA implementation.

RPN Formula and Calculation

RPN = Severity × Occurrence × Detection

Range: 1 to 1,000

Calculation Examples

High Risk Example
  • Severity: 9 (Safety critical)
  • Occurrence: 6 (Moderate frequency)
  • Detection: 8 (Poor detection)
  • RPN = 9 × 6 × 8 = 432
Medium Risk Example
  • Severity: 5 (Customer annoyance)
  • Occurrence: 4 (Low frequency)
  • Detection: 6 (Fair detection)
  • RPN = 5 × 4 × 6 = 120
Low Risk Example
  • Severity: 3 (Minor effect)
  • Occurrence: 2 (Very low frequency)
  • Detection: 3 (Good detection)
  • RPN = 3 × 2 × 3 = 18

RPN Interpretation Guidelines

Critical Priority (RPN ≥ 500)

Requires immediate action and management attention. These failure modes pose significant risk and must be addressed urgently.

  • Stop production/implementation if applicable
  • Assign dedicated resources
  • Implement interim containment actions
  • Develop comprehensive corrective action plan

High Priority (RPN 200-499)

Requires planned corrective action with defined timeline and responsibility.

  • Assign specific responsibility
  • Set target completion dates
  • Monitor progress regularly
  • Consider interim risk mitigation

Medium Priority (RPN 100-199)

Should be addressed as resources and priorities allow.

  • Include in improvement planning
  • Consider during design reviews
  • Address during regular maintenance cycles
  • Monitor for changes in risk level

Low Priority (RPN < 100)

May be acceptable as-is but should be monitored.

  • Document for future reference
  • Consider during continuous improvement
  • Review periodically for changes
  • Share lessons learned

RPN Limitations and Considerations

Mathematical Limitations

  • Different rating combinations can yield same RPN
  • Doesn't distinguish between severity levels
  • Assumes equal weighting of all factors
  • May not reflect true risk priority

Additional Prioritization Factors

  • All severity ratings of 9 or 10
  • Regulatory or safety requirements
  • Customer critical characteristics
  • Cost and feasibility of actions

Best Practices

  • Use RPN as one prioritization input
  • Consider severity ratings independently
  • Apply business judgment and context
  • Review and validate prioritization

Practical FMEA Examples

Real-world examples help illustrate how FMEA is applied across different industries and applications. These examples demonstrate the practical use of FMEA methodology.

Process FMEA Example: Welding Process

Process Step: Arc Welding

Function Failure Mode Effect S Cause O Controls D RPN
Join metal parts with continuous weld bead Incomplete penetration Weak joint, potential structural failure 8 Insufficient amperage, wrong electrode angle 4 Visual inspection, welding procedure 6 192
Join metal parts with continuous weld bead Porosity in weld Reduced strength, leak path 6 Contaminated base metal, poor gas shielding 3 Material cleaning, gas flow check 4 72
Join metal parts with continuous weld bead Excessive spatter Poor appearance, cleanup required 4 Wrong welding parameters, dirty material 5 Parameter setup sheet, material prep 3 60

Action Plan for Highest RPN (192)

  • Action: Implement automated welding parameter control system
  • Responsibility: Manufacturing Engineering
  • Target Date: 30 days
  • Expected Result: Reduce occurrence from 4 to 2, detection from 6 to 3
  • New RPN: 8 × 2 × 3 = 48

Design FMEA Example: Electronic Control Unit

Component: Microprocessor

Function Failure Mode Effect S Cause O Controls D RPN
Process sensor inputs and control outputs Complete failure (no output) System shutdown, safety concern 9 Power supply failure, chip burnout 2 Power monitoring, thermal design 2 36
Process sensor inputs and control outputs Intermittent operation Erratic system behavior 7 Loose connections, thermal cycling 3 Vibration testing, thermal testing 5 105
Process sensor inputs and control outputs Wrong output signals Incorrect system response 8 Software bug, corrupted memory 2 Software validation, memory checks 3 48

Action Plan for Highest RPN (105)

  • Action: Add connection reliability testing and conformal coating
  • Responsibility: Design Engineering
  • Target Date: Next design revision
  • Expected Result: Reduce occurrence from 3 to 2, detection from 5 to 3
  • New RPN: 7 × 2 × 3 = 42

Service FMEA Example: Customer Order Processing

Process Step: Order Entry

Function Failure Mode Effect S Cause O Controls D RPN
Accurately capture customer order details Wrong product ordered Customer dissatisfaction, returns 6 Miscommunication, similar part numbers 4 Order confirmation email 6 144
Accurately capture customer order details Incorrect quantity Inventory issues, customer impact 5 Data entry error, system glitch 3 Quantity verification prompt 4 60
Accurately capture customer order details Wrong delivery address Delayed delivery, additional costs 4 Outdated customer information 5 Address validation system 3 60

Action Plan for Highest RPN (144)

  • Action: Implement product selection wizard with photos
  • Responsibility: IT Systems
  • Target Date: 60 days
  • Expected Result: Reduce occurrence from 4 to 2, detection from 6 to 2
  • New RPN: 6 × 2 × 2 = 24

FMEA Best Practices

Following established best practices ensures effective FMEA implementation and maximizes the value of the analysis effort.

Team and Process Best Practices

  • Cross-Functional Teams: Include representatives from design, manufacturing, quality, and field service
  • Subject Matter Experts: Ensure team has deep knowledge of the product/process being analyzed
  • Structured Approach: Follow systematic methodology and use standard templates
  • Adequate Time: Allow sufficient time for thorough analysis and discussion
  • Facilitation: Use experienced facilitator to guide the process
  • Documentation: Maintain detailed records of analysis and decisions

Analysis Best Practices

  • Clear Scope: Define boundaries and level of detail before starting
  • Function Focus: Start with clear function definitions and requirements
  • One Failure Mode: Address one failure mode per row in the analysis
  • Specific Causes: Identify specific, actionable root causes
  • Customer Perspective: Consider effects from the customer's viewpoint
  • Current State: Base ratings on current design/process, not future improvements

Rating and Prioritization Best Practices

  • Consistent Scales: Use standardized rating scales across all FMEAs
  • Team Consensus: Achieve agreement on all ratings through discussion
  • External Validation: Have ratings reviewed by independent experts
  • Severity Focus: Pay special attention to high severity ratings regardless of RPN
  • Multiple Criteria: Use additional prioritization criteria beyond RPN
  • Regular Review: Periodically review and update ratings as conditions change

Action Planning Best Practices

  • Prevention Focus: Prioritize actions that prevent failures over detection methods
  • Specific Actions: Define clear, actionable improvement plans
  • Resource Allocation: Assign specific responsibility and target dates
  • Cost-Benefit: Consider implementation cost versus risk reduction
  • Feasibility Assessment: Ensure proposed actions are technically and economically viable
  • Follow-Through: Track completion and verify effectiveness of actions

Implementation and Maintenance Best Practices

  • Early Integration: Conduct FMEA early in design/process development
  • Living Document: Keep FMEA current as design/process evolves
  • Lessons Learned: Incorporate field experience and failure data
  • Knowledge Sharing: Share FMEA results across projects and teams
  • Training: Provide adequate training for all team members
  • Software Tools: Use appropriate FMEA software for documentation and analysis

Common FMEA Mistakes to Avoid

Understanding common pitfalls helps ensure more effective FMEA implementation and better results from the analysis effort.

Process and Team Mistakes

Wrong Team Composition

Problem: Missing key expertise or having too narrow representation

Solution: Ensure cross-functional team with relevant experience

Insufficient Time Allocation

Problem: Rushing through analysis leads to superficial results

Solution: Plan adequate time for thorough analysis and discussion

Poor Facilitation

Problem: Lack of structure leads to unfocused discussions

Solution: Use experienced facilitator and structured methodology

Starting Too Late

Problem: FMEA done after design freeze limits improvement options

Solution: Integrate FMEA early in development process

Analysis Content Mistakes

Vague Function Definitions

Problem: Unclear functions lead to missed failure modes

Solution: Use specific, measurable function descriptions

Multiple Failure Modes per Row

Problem: Combining failure modes confuses analysis

Solution: Address one failure mode per row

Generic Causes

Problem: Non-specific causes don't lead to actionable solutions

Solution: Identify specific, root cause mechanisms

Effects vs. Failure Modes

Problem: Confusing what fails with the consequence of failure

Solution: Clearly distinguish between failure modes and effects

Rating and Scoring Mistakes

Inconsistent Rating Scales

Problem: Different interpretations lead to invalid comparisons

Solution: Use standardized scales with clear criteria

Wishful Thinking

Problem: Rating based on desired future state rather than current

Solution: Base ratings on current design/process capabilities

RPN Tunnel Vision

Problem: Focusing only on RPN ignores other important factors

Solution: Consider severity independently and use multiple criteria

Rating Without Data

Problem: Guessing at occurrence rates without supporting data

Solution: Use historical data and field experience when available

Action Planning Mistakes

Vague Action Plans

Problem: Non-specific actions don't get implemented

Solution: Define specific, measurable improvement actions

Detection-Only Solutions

Problem: Only adding inspections doesn't prevent failures

Solution: Focus on prevention through design and process improvements

No Follow-Through

Problem: Actions planned but not implemented or verified

Solution: Track action completion and verify effectiveness

Unrealistic Expectations

Problem: Expecting dramatic RPN reductions from minor changes

Solution: Set realistic improvement targets based on action capabilities

FMEA Implementation Guide

Successful FMEA implementation requires careful planning, proper training, and ongoing support. This guide provides a roadmap for establishing effective FMEA practices in your organization.

Phase 1: Preparation and Planning

Key Activities

  • Define FMEA objectives and scope
  • Establish organizational commitment and resources
  • Select pilot projects for initial implementation
  • Develop FMEA standards and procedures
  • Choose appropriate software tools

Success Factors

  • Senior management sponsorship
  • Clear business case and expectations
  • Adequate budget and timeline
  • Integration with existing processes

Phase 2: Training and Capability Building

Training Program Components

  • Executive Overview: Benefits and role in quality management
  • Facilitator Training: Detailed methodology and facilitation skills
  • Team Member Training: FMEA basics and rating guidelines
  • Application Training: Hands-on practice with real projects

Capability Development

  • Train internal facilitators and experts
  • Develop templates and tools
  • Create reference materials and examples
  • Establish coaching and mentoring support

Phase 3: Pilot Implementation

Pilot Project Selection

  • Choose projects with supportive stakeholders
  • Select appropriate complexity and scope
  • Ensure adequate resources and expertise
  • Have clear success criteria and metrics

Pilot Execution

  • Follow structured FMEA process
  • Document lessons learned and improvements
  • Measure results and business impact
  • Refine procedures based on experience

Phase 4: Full Deployment

Deployment Strategy

  • Gradually expand to additional projects
  • Integrate FMEA into standard procedures
  • Establish review and approval processes
  • Create performance metrics and tracking

Support Systems

  • Ongoing training and refresher sessions
  • Expert consultation and support
  • Software tools and templates
  • Knowledge sharing and best practices

Phase 5: Sustaining and Improving

Sustainability Activities

  • Regular FMEA reviews and updates
  • Continuous improvement of processes
  • Integration with other quality tools
  • Knowledge management and retention

Performance Monitoring

  • Track FMEA completion rates
  • Monitor action item closure
  • Measure failure reduction results
  • Assess customer satisfaction impact

Master FMEA and Risk Assessment Techniques

FMEA is a powerful tool for preventing failures and improving quality. Get comprehensive training in risk assessment and failure analysis methodologies.

Get Six Sigma Training Learn Fishbone Analysis