How to Calculate the Rpn in Fmea: Step-by-step Practical Approach

by

Table of Contents

Failure Mode and Effects Analysis (FMEA) is a systematic, proactive methodology used across industries to identify potential failures in processes, products, and systems before they occur. At the heart of FMEA lies the Risk Priority Number (RPN), a quantitative tool that helps organizations prioritize risks and allocate resources effectively. The Risk Priority Number (RPN) is a numerical tool used within Failure Modes and Effects Analysis (FMEA) to assess and prioritize potential risks. Understanding how to calculate and interpret RPN is essential for effective risk management, quality improvement, and ensuring product reliability and safety.

This comprehensive guide will walk you through the step-by-step process of calculating RPN in FMEA, explain the three critical components that make up this calculation, provide practical examples from various industries, and share best practices for implementing RPN-based risk prioritization in your organization.

What is FMEA and Why Does It Matter?

FMEA is a systematic, proactive method for evaluating processes to identify where and how they might fail and to assess the relative impact of different failures. This analytical approach helps organizations identify potential failure modes, determine their effect on operations, and prioritize actions to reduce risk. The methodology has evolved significantly since its origins and now serves as a cornerstone of quality management across diverse sectors.

The Evolution and Applications of FMEA

The methodology originated in the aerospace industry during the 1960s but has since expanded across manufacturing, healthcare, software development, and service industries. Today, FMEA is widely recognized as one of the most effective tools for proactive risk management, helping organizations prevent costly failures, improve product quality, and enhance customer satisfaction.

Failure Modes and Effects Analysis (FMEA) is integral to reliability, quality and safety programs in a wide variety of industries. It’s a collaborative cross-functional methodology that aims to anticipate and address potential failures in products, processes or services before they happen. The structured approach enables teams to systematically evaluate potential problems and implement preventive measures before issues reach customers or end users.

Understanding the Risk Priority Number (RPN)

The Risk Priority Number represents a numerical scoring system used within Failure Modes and Effects Analysis (FMEA) to evaluate and rank potential failure modes. This assessment tool helps responsible teams prioritize risks and decide on corrective actions by providing a score to rank how concerning a particular failure mode is. Essentially, RPN transforms complex risk scenarios into manageable numerical values, enabling organizations to allocate resources efficiently toward addressing the most critical potential failures.

The RPN gives us a relative risk ranking. Higher the RPN, the higher the potential risk. This numerical assessment provides teams with a consistent framework for comparing different failure modes and making data-driven decisions about where to focus improvement efforts.

The Three Dimensions of Risk Assessment

Unlike simpler risk models that consider only probability and impact, the FMEA RPN methodology incorporates a critical third dimension: detectability. This reflects the engineering reality that not all failures can be prevented, but many can be caught before causing harm. This three-dimensional approach provides a more comprehensive view of risk than traditional two-factor models.

The Three Components of RPN: A Detailed Breakdown

FMEA RPN is calculated by multiplying Severity (S), Occurrence (O) Or Probability (P), and Detection (D) indexes. Each of these three factors plays a distinct role in assessing the overall risk associated with a potential failure mode. Let’s examine each component in detail.

Component 1: Severity (S)

Severity (S): The seriousness of the consequences if the failure occurs. This rating assesses the impact of the failure mode on the end user, customer, or system. It assesses the impact of the failure mode (the error in the process) and is determined without regard to the likelihood of occurrence or detection.

The severity ranking is based on a relative scale ranging from 1 to 10. A “10” means the effect has a dangerously high severity leading to a hazard without warning. Conversely, a ranking of “1” means the severity is extremely low. Organizations typically define severity criteria based on their specific industry requirements, regulatory standards, and customer expectations.

Severity Rating Guidelines:

  • 1-2 (Minor): Minimal impact, minor inconvenience to user, no significant effect on performance
  • 3-4 (Low): Low impact, some customer dissatisfaction, minor performance degradation
  • 5-6 (Moderate): Moderate impact, customer dissatisfaction, noticeable performance issues
  • 7-8 (High): High impact, significant customer dissatisfaction, major performance degradation
  • 9-10 (Critical): Critical impact, safety hazard, regulatory non-compliance, potential for injury or death

In most cases, processes with severity scores exceeding 8 may require a fault tree analysis, which estimates the probability of the failure mode by breaking it down into further sub-elements. High severity ratings demand special attention regardless of other factors.

Component 2: Occurrence (O)

Occurrence (O): The likelihood of the failure happening. This factor evaluates how frequently the failure cause is expected to occur during the product’s or process’s lifecycle. The probability of occurrence is the likelihood of failure, or relative number of failures, expected during the item’s useful life.

For the entire FMEA system, occurrence scoring should be consistent. The scoring of occurrence should be an appropriate number, as determined by the discussions of the special case team. Moreover, scoring should be set as ranging from “1” to “10”, as supported by the subjective norms. Organizations often base occurrence ratings on historical data, process capability indices, or statistical analysis.

Occurrence Rating Guidelines:

  • 1 (Remote): Failure is unlikely, less than 1 in 1,000,000 occurrences
  • 2-3 (Low): Relatively few failures, 1 in 20,000 to 1 in 150,000 occurrences
  • 4-6 (Moderate): Occasional failures, 1 in 400 to 1 in 2,000 occurrences
  • 7-8 (High): Frequent failures, 1 in 80 to 1 in 400 occurrences
  • 9-10 (Very High): Failure is almost inevitable, more than 1 in 20 occurrences

The automotive industry has developed detailed rating tables linking occurrence ratings to Cpk values (process capability indices), enabling statistical rigor in occurrence assessments. A process with Cpk = 1.67 (5σ capability) typically warrants O = 2, while Cpk = 1.00 (3σ) corresponds to O = 5-6. This approach provides objective, data-driven occurrence ratings.

Component 3: Detection (D)

Detection (D): The probability that the failure will be identified before it causes a problem. This rating assesses the effectiveness of current controls in detecting the failure cause or failure mode before the product reaches the customer or the failure effect is realized.

Detection (D) is the probability that control (design, in-process, inspection, alert/warning) will eliminate, mitigate, or catch the defect. A critical aspect of detection ratings is that higher numbers indicate worse detection capability—meaning the failure is less likely to be caught.

Detection involves detecting the causes for failures through the completion of special cases and setting the scoring scope (from “1” to “10”). In the detection analysis, it is necessary to assume that the failure mode has been initiated, and then, analyze the abilities of existing control methods to detect the failure mode.

Detection Rating Guidelines:

  • 1-2 (Very High): Detection is almost certain, automated detection with fail-safe mechanisms
  • 3-4 (High): High likelihood of detection, automated detection systems with statistical validation
  • 5-6 (Moderate): Moderate detection capability, manual inspection or testing methods
  • 7-8 (Low): Low detection capability, random sampling or visual inspection
  • 9-10 (Very Low): Detection is unlikely or impossible, no known controls

A 100% inspection process that relies on visual examination by fatigued operators may warrant a detection rating of 5-7, while automated vision systems with statistical validation might justify a rating of 2-3, despite both being “100% inspection” on paper. The quality and reliability of detection methods matter more than their frequency.

The RPN Calculation Formula: Step-by-Step Process

The calculation of the Risk Priority Number is straightforward, yet powerful. We simply multiply the severity (S), occurrence (O), and detection (D) ratings, each measured on a scale from 1 to 10, to arrive at the RPN score.

RPN Formula:

RPN = Severity (S) × Occurrence (O) × Detection (D)

Since each factor is rated on a scale from 1 to 10, the RPN can range from 1 (lowest risk) to 1,000 (highest risk). This range provides sufficient granularity for meaningful differentiation while avoiding the false precision that would come from continuous probability distributions.

Step-by-Step Calculation Process

Follow these detailed steps to calculate the RPN for each potential failure mode identified in your FMEA:

Step 1: Identify the Failure Mode

Begin by clearly defining the specific way in which a process, product, or system component could fail. Be specific and focus on one failure mode at a time. For example, “pump delivers inadequate outlet pressure” rather than simply “pump fails.”

Step 2: Determine the Failure Effects

Identify the consequences of the failure at multiple levels: local effects (on the component itself), next-level effects (on the subsystem), and end-user effects (on the customer or final user). This helps establish the severity rating.

Step 3: Assign the Severity Rating

Based on the most serious effect identified, assign a severity rating from 1 to 10 using your organization’s severity criteria. Consider safety implications, regulatory requirements, customer impact, and business consequences. Document the rationale for your rating.

Step 4: Identify Potential Causes

List all possible causes that could lead to the failure mode. Each cause will receive its own occurrence and detection ratings, as different causes may have different likelihoods and detection capabilities.

Step 5: Assign the Occurrence Rating

For each cause, estimate how frequently it is likely to occur based on historical data, process capability, or expert judgment. Assign an occurrence rating from 1 to 10 using your organization’s occurrence criteria.

Step 6: Identify Current Controls

Document the existing prevention and detection controls that are currently in place to either prevent the cause from occurring or detect the failure before it reaches the customer.

Step 7: Assign the Detection Rating

Evaluate the effectiveness of current controls in detecting the cause or failure mode. Assign a detection rating from 1 to 10, remembering that higher numbers indicate lower detection capability.

Step 8: Calculate the RPN

Multiply the three ratings together: RPN = S × O × D. Record this value in your FMEA worksheet.

Step 9: Rank and Prioritize

Rank failure modes in order from the highest RPN number to the smallest. This ranking helps teams identify which failure modes require immediate attention and corrective action.

Practical RPN Calculation Examples

Let’s examine several real-world examples to illustrate how RPN calculations work in different scenarios and industries.

Example 1: Manufacturing Process – Component Installation

Consider a manufacturing process where a component might be installed incorrectly: Severity: 8 (could cause product failure affecting customer safety) Occurrence: 3 (happens rarely due to trained operators) Detection: 4 (quality inspection catches most errors)

RPN Calculation:

RPN = 8 × 3 × 4 = 96

This moderate RPN suggests that while the severity is high, the combination of trained operators (low occurrence) and quality inspection (moderate detection) reduces the overall risk to a manageable level. However, given the high severity rating, the team should still consider additional controls.

Example 2: Automotive Component – Power Steering Pump

For example, consider a failure cause with S=10, O=4 and D=2. Its RPN would be 10x4x2 = 80.

In this scenario:

  • Severity = 10: Critical safety issue, potential for accident
  • Occurrence = 4: Occasional failures observed
  • Detection = 2: Excellent detection capability through testing

RPN = 10 × 4 × 2 = 80

Despite the relatively moderate RPN, the severity rating of 10 indicates this failure mode requires immediate attention due to safety implications, regardless of the RPN value.

Example 3: Process FMEA – Quality Characteristic

A certain characteristic has a criticality/severity of 4, a probability of occurrence of 3, and a probability of detection of 3. The RPN is calculated as follows: RPN = Severity x Occurrence x Detection = 4 x 3 x 3= 36

This lower RPN indicates a relatively lower priority for corrective action compared to higher-risk failure modes. However, the team should still monitor this characteristic and consider improvements if resources allow.

Example 4: Aerospace Manufacturing – CNC Machining

For the highest-priority failure mode—”Coolant contamination causing surface finish degradation” with S=6, O=7, D=6 (RPN=252)

RPN = 6 × 7 × 6 = 252

This high RPN clearly indicates a priority for corrective action. The combination of moderate severity, high occurrence, and poor detection creates an unacceptable risk level that requires immediate improvement efforts.

Interpreting RPN Values: Thresholds and Action Criteria

Once you’ve calculated RPN values for all failure modes, the next critical step is interpreting these numbers and determining which failures require corrective action.

Understanding RPN Thresholds

Organizations establish RPN thresholds to trigger mandatory corrective action, typically ranging from 80 to 125 depending on industry risk tolerance. Typically, thresholds for High, Medium, and Low risk will be defined, and a class of risk will be assigned to every failure cause. If we define RPN >100 as High risk and RPN<50 as Low risk and everything in between as Medium, we would assign a Medium risk to this failure cause.

There’s no universal threshold. The acceptable RPN varies by industry, company, and project. For instance: In medical FMEA, where patient safety is paramount, even an RPN of 100 might be deemed too high. Aerospace and medical device manufacturers typically use thresholds between 75-100, while consumer goods manufacturers might accept thresholds of 125-150.

The Limitations of Single-Threshold Approaches

There is no ‘magic’ RPN number above which you must take action. This is simply a method of highlighting and prioritising risks. You can take action on whatever you like but it does makes sense to reduce the highest risks first.

However, it is essential to avoid relying exclusively on the RPN as the sole criterion for decision-making. There are no universal RPN thresholds that mandate action or exempt the team from taking action based on their value. Relying solely on RPN thresholds can create dangerous blind spots in risk management.

Multi-Criteria Decision Framework

Many advanced FMEA practitioners employ dual criteria: any RPN exceeding the global threshold (e.g., 100) requires action, but so does any failure mode where severity equals 9 or 10, regardless of RPN. This prevents the mathematical artifact where a catastrophic failure (S=10) with very low occurrence (O=1) and excellent detection (D=2) yields an RPN of 20—below the action threshold but clearly unacceptable from a safety perspective.

Best practice involves implementing a multi-criteria decision matrix: any RPN above your organizational threshold requires action, AND any failure mode with severity ≥9 requires action regardless of RPN, AND any failure mode with detection ≥8 should trigger action even with moderate RPN.

Tip – Action should be mandatory for any severity rating of 9 or above. This ensures that high-severity failures receive appropriate attention even when other factors suggest lower overall risk.

The Problem with Equal Weighting

Also, the RPN value that is calculated weights each score equally, which may not always be proper. Typically severity is seen as more important than occurrence or detection, and failure causes associated with safety or regulatory concerns, as the severity of 10 in the first cause would indicate, should receive higher priority even with lower RPN values.

A high RPN failure does not necessarily indicate a high risk for the process or product. Moreover, two failure modes with the same RPN value may not have the same risk level. In the following example from the automotive industry, Failure Mode 1 should be provided a higher priority than Failure Mode 2 although they have the same RPN value because it has a higher Severity value.

Using RPN for Risk Prioritization: Practical Strategies

Organizations can employ several strategies for using RPN values to prioritize corrective actions and allocate improvement resources effectively.

Strategy 1: RPN Threshold Method

Many organizations use an RPN limit to determine which failure mode requires corrective action and which risks are acceptable. The RPN threshold is easy to use. This straightforward approach establishes a clear cutoff point above which action is mandatory.

However, using an RPN threshold may cause team members to spend excessive time trying to reduce the Detection, Occurrence, and Severity rankings for lowering the RPN. This situation sometimes places the organization and its customers in danger. Teams may focus on manipulating numbers rather than implementing meaningful improvements.

Strategy 2: Top RPN Ranking Method

The other organizations may address the corrective action for the top failure modes/failures causes by Risk Priority Number. After that, the team will work with other top RPNs to continuously improve the process. This approach focuses on addressing the highest-risk items first, then systematically working down the list.

Once all high-severity issue have been addressed, the FMEA team can take up high RPN issues, in sequence. This ensures that critical safety and regulatory issues receive priority attention before moving to other high-RPN items.

Strategy 3: Risk Matrix Approach

The team can combine the criteria for the RPN and Severity, Occurrence, and Detection rankings by using a matrix. The following is an example of a risk matrix for the RPN and Severity ranking. The following example of a risk matrix includes a combination of severity and occurrence.

Risk matrices provide visual representations that help teams quickly identify high-priority issues by plotting multiple risk factors simultaneously. Color coding (red, yellow, green) makes risk levels immediately apparent to all stakeholders.

Strategy 4: Action Priority Tables

One of the major changes with the new AIAG-VDA FMEA process is the use of the RPN has been eliminated. The RPN has been replaced by an action priority (AP) table. The AP tables assign one of three suggested rankings for each action based upon the S, O, and D values.

As a supplement or alternative to RPNs and SxOs, many FMEA programs have developed risk ranking tables to assist with the decision-making process. These tables typically identify whether action is required based on some combination of Severity, Occurrence, and/or Detection. Recent versions of both the AIAG-VDA and SAE J1739 FMEA standards (published in 2019 and 2021) now also provide sample ranking tables that FMEA teams can adapt to fit their particular needs.

Developing Corrective Actions to Reduce RPN

After identifying high-priority failure modes through RPN analysis, the next critical step is developing and implementing effective corrective actions to reduce risk.

Strategies for Reducing Severity

Severity reduction typically requires design changes or process modifications that lessen the impact of the failure. This might involve adding redundancy, implementing fail-safe mechanisms, or redesigning systems to minimize consequences. Severity is often the most difficult factor to reduce because it requires fundamental changes to the design or process.

Examples of severity reduction strategies include:

  • Implementing redundant systems or backup components
  • Adding fail-safe or fail-operational features
  • Redesigning to eliminate hazardous materials or conditions
  • Incorporating protective barriers or containment systems
  • Reducing energy levels or operating pressures

Strategies for Reducing Occurrence

Lowering occurrence involves preventing the failure from happening in the first place. Strategies include improving process controls, enhancing training programs, implementing error-proofing devices, or upgrading equipment. Occurrence reduction often provides the most cost-effective approach to risk mitigation.

Examples of occurrence reduction strategies include:

  • Implementing poka-yoke (error-proofing) devices
  • Improving process capability through statistical process control
  • Enhancing operator training and competency verification
  • Upgrading equipment or implementing preventive maintenance
  • Standardizing procedures and work instructions
  • Improving material quality or supplier controls

Strategies for Improving Detection

Better detection means implementing controls that identify failures before they reach customers. This could involve adding inspection points, implementing automated testing, or improving quality assurance procedures. While improving detection doesn’t prevent failures, it can significantly reduce their impact on customers.

Examples of detection improvement strategies include:

  • Implementing automated inspection systems with vision technology
  • Adding in-process monitoring and sensors
  • Increasing inspection frequency or sample sizes
  • Implementing statistical sampling plans
  • Adding functional testing or validation steps
  • Implementing mistake-proofing verification systems

Recalculating RPN After Improvements

Once Action has been taken to improve a process, new severity, frequency and detection rating should be determined and the resulting PRN calculated. A significant reduction in the RPN should be noted. If not, the actions taken to improve the process were not sufficient to reduce the severity, frequency and detection rating and additional actions should be taken.

For the revised risk assessment, the analysis team assigns a second set of Severity, Occurrence and Detection ratings for each potential failure cause, either after the actions are completed or based on the expectation that they will be completed. This provides an indication of the effectiveness of improvement activities and may also be used to evaluate the value to the organization of performing the FMEA.

Industry-Specific Applications of RPN

Different industries apply RPN calculations with specific considerations tailored to their unique requirements and risk profiles.

Automotive Industry

The aerospace and automotive industries are two sectors where the Risk Priority Number has been particularly impactful. In these high-stakes industries, where product safety and reliability are of paramount importance, the RPN has become an integral part of the risk management toolbox.

For example, in the production of a critical automotive component, the RPN would help identify and address the most pressing risks, such as a lack of success related to a faulty part that could lead to a safety hazard. By addressing this high-risk area with targeted corrective actions, manufacturers can significantly reduce the likelihood of costly and potentially dangerous product recalls.

Aerospace Industry

Aerospace applications employ FMEA for both hardware and software systems, with severity ratings often tied directly to SAE ARP4761 safety assessment categories. The consequence of software FMEA is that occurrence ratings may reflect code complexity metrics, cyclomatic complexity, or historical defect density rather than physical failure rates. Detection ratings for software incorporate code coverage metrics from automated testing, with 95% branch coverage potentially justifying D = 3-4 depending on test quality.

Medical Device Manufacturing

A failure mode with S = 10 (potential patient death) and RPN below the action threshold due to low occurrence or high detection will draw questions about risk acceptance criteria. Medical device manufacturers must maintain extremely conservative risk thresholds due to patient safety considerations and regulatory requirements.

Process Industries

Process industries including chemical manufacturing, pharmaceuticals, and food production increasingly use FMEA for process safety management and HACCP (Hazard Analysis Critical Control Points) programs. In these applications, severity ratings may reflect environmental impact, regulatory compliance consequences, or public health risks beyond traditional quality metrics. The multiplication logic of RPN can create challenges here: should a low-probability environmental catastrophe (S=10, O=1, D=8, RPN=80) receive lower priority than a frequent quality issue (S=5, O=8, D=3, RPN=120)? Many organizations supplement RPN with independent severity gates to address this concern.

Best Practices for Effective RPN Implementation

Implementing RPN-based risk prioritization effectively requires following established best practices and avoiding common pitfalls.

Assemble Cross-Functional Teams

However, achieving consensus on ratings often requires cross-functional collaboration, leveraging diverse perspectives and domain expertise within the organization. Assemble a Diverse Team: Include experts from engineering, quality, and operations to ensure accurate ratings. Different perspectives help ensure comprehensive risk assessment and prevent blind spots.

Use Data-Driven Ratings

Use historical data and objective evidence when assigning ratings whenever possible. While expert judgment plays an important role, grounding ratings in actual performance data, warranty claims, field failure data, or process capability studies increases objectivity and credibility.

Document Assumptions and Rationale

Document assumptions and rationale for scoring decisions to ensure consistency and enable future reviews. This documentation helps new team members understand the basis for ratings and supports continuous improvement efforts.

Maintain Living Documents

Remember that FMEA is a living document that should evolve with your processes. Tip – A process and machine FMEA should be reviewed and revised with time (it is a ‘live document’) to reflect new equipment, processes and procedures. This will allow the control plan to be reviewed with the experience gained.

Regular Reviews and Updates

Review and update FMEAs regularly as processes change to ensure they remain relevant and accurate. Changes in materials, equipment, procedures, or customer requirements may affect risk ratings and require FMEA updates.

Track Effectiveness of Actions

Track the effectiveness of implemented corrective actions to verify that improvements actually reduce risk as intended. This feedback loop enables continuous improvement and validates the FMEA process.

Focus on Prevention, Not Just Numbers

The key to success lies not just in calculating numbers but in creating a culture that values continuous improvement and systematic problem prevention. The ultimate goal is preventing failures and improving quality, not simply generating documentation or achieving target RPN values.

Common Pitfalls and Limitations of RPN

While RPN is a powerful tool, understanding its limitations helps teams use it more effectively and avoid common mistakes.

Subjectivity in Ratings

Subjectivity: Severity, occurrence, and detection ratings depend on human judgment, which can vary. Different team members may interpret rating criteria differently, leading to inconsistent assessments. Establishing clear rating criteria and using historical data helps reduce subjectivity.

Equal Weighting Issues

Equal Weighting: The RPN formula treats all three factors equally, but a high severity (e.g., 10) might warrant action even if the RPN is low. This mathematical limitation means that catastrophic but rare failures may receive lower priority than frequent but minor issues.

Non-Continuous Scale

RPNs or SxOs can be compared to other metrics in the same FMEA but may not be comparable to metrics in another analysis. RPN values from different FMEAs or different organizations cannot be directly compared because rating criteria and scales may differ.

Same RPN, Different Risks

However, because they have the same RPN value, an inappropriate action plan for critical failure may be selected. For this reason, the RPN should not be the only index used to evaluate the risk of each failure mode. The team should also use Severity, Occurrence, and Detection to prioritize risks.

Overcoming Limitations

Prioritizing high-severity issues, regardless of RPN. Regularly updating FMEA as new data emerges. Using complementary tools like fault tree analysis for deeper insights. These strategies help teams work around RPN limitations and make better risk management decisions.

Integrating RPN with Other Quality Tools

RPN works most effectively when integrated with other quality management and continuous improvement methodologies.

RPN and Lean Six Sigma

Within lean six sigma frameworks, FMEA plays a vital role throughout the DMAIC (Define, Measure, Analyze, Improve, Control) process. Organizations using lean six sigma principles frequently incorporate FMEA during the analyze phase, though it can be valuable during the recognize phase when identifying critical processes that require improvement.

The structured approach of FMEA aligns perfectly with lean six sigma principles of reducing variation and eliminating waste. By systematically identifying and prioritizing risks, organizations can focus their limited resources on improvements that deliver the greatest impact.

RPN and CAPA Systems

Another key aspect of integrating the Risk Priority Number into a comprehensive risk management approach is the linkage to Corrective and Preventive Actions (CAPA). Once the RPN has been calculated and the high-risk areas have been identified, the CAPA process can be used to develop and implement specific actions to mitigate those risks.

The FMEA provides the foundation for the RPN, as it helps to identify the potential low success modes, their causes, and their effects. The RPN then builds upon this information by quantifying the severity, occurrence, and detection of each mode, allowing teams to prioritize their efforts and focus on the most critical risks. By integrating these two powerful tools, organizations can create a comprehensive, data-driven risk management framework that supports informed decision-making, enhances process reliability, and ultimately leads to improved product quality and customer satisfaction.

Advanced RPN Concepts and Alternatives

As FMEA methodology evolves, several alternative approaches to traditional RPN have emerged to address its limitations.

Critical Number (CN)

Critical Number (CN) = Severity (S) x Occurrence (O) Some organizations use this simplified approach when detection ratings are difficult to determine or when they want to focus solely on preventing failures rather than detecting them.

Action Priority (AP) Method

It may be time to consider eliminating the use of the traditional RPN score and transitioning to the use of AP ratings. AP ratings are much simpler to use, do not require a calculation (eliminating the validation of a spreadsheet), and provides a single simple table reference to determine the appropriate level of action.

SO Matrix (Qualitative Criticality Analysis)

An SO matrix visually displays the severity risk on one axis and the occurrence risk on a second axis to show the level of overall risk. Colors, such as red, yellow, and green can be used to differentiate the corresponding risk. This visual approach helps teams quickly identify high-risk areas without calculating numerical RPN values.

Creating an Effective FMEA Worksheet

A well-structured FMEA worksheet is essential for documenting your analysis and tracking RPN calculations effectively.

Essential FMEA Worksheet Columns:

  • Item/Function: The component, process step, or function being analyzed
  • Potential Failure Mode: The specific way the item could fail
  • Potential Effects: Consequences of the failure at various levels
  • Severity (S): Rating from 1-10
  • Potential Causes: Root causes that could lead to the failure
  • Occurrence (O): Rating from 1-10
  • Current Controls: Existing prevention and detection methods
  • Detection (D): Rating from 1-10
  • RPN: Calculated value (S × O × D)
  • Recommended Actions: Proposed improvements
  • Responsibility: Person or team assigned to implement actions
  • Target Date: Deadline for completion
  • Actions Taken: Description of implemented improvements
  • Revised S, O, D: New ratings after improvements
  • Revised RPN: New calculated value

Real-World Implementation: Step-by-Step Case Study

Let’s walk through a complete FMEA process for a manufacturing scenario to illustrate how RPN calculations work in practice.

Scenario: Injection Molding Process for Automotive Interior Components

Step 1: Define the Process

Function: Inject molten plastic into mold cavity to form dashboard trim piece with specified dimensions and surface finish.

Step 2: Identify Failure Mode

Failure Mode: Short shot (incomplete filling of mold cavity)

Step 3: Determine Effects

  • Local Effect: Incomplete part with missing material
  • Next Level Effect: Part fails dimensional inspection
  • End User Effect: Assembly line stoppage, potential vehicle quality issue

Step 4: Assign Severity Rating

Severity = 7 (High impact on production, potential customer quality issue)

Step 5: Identify Causes and Assign Occurrence

Cause 1: Insufficient injection pressure

  • Occurrence = 4 (Occasional occurrence based on historical data)

Step 6: Evaluate Current Controls and Assign Detection

Current Controls: Visual inspection by operator, periodic dimensional checks

  • Detection = 5 (Moderate detection capability, some defects may escape)

Step 7: Calculate Initial RPN

RPN = 7 × 4 × 5 = 140

This RPN exceeds typical thresholds, indicating corrective action is required.

Step 8: Develop Corrective Actions

  • Install pressure monitoring system with automatic alerts (reduces Occurrence to 2)
  • Implement automated vision inspection system (reduces Detection to 2)

Step 9: Calculate Revised RPN

Revised RPN = 7 × 2 × 2 = 28

The significant reduction in RPN demonstrates the effectiveness of the implemented improvements.

Tools and Software for RPN Calculation

While RPN can be calculated manually, various tools and software solutions can streamline the FMEA process and improve accuracy.

Spreadsheet-Based Solutions

Many organizations use Microsoft Excel or Google Sheets to create FMEA worksheets with built-in RPN calculations. Because of the structure of the FMEA worksheet, the Severity cell is not linked one to one with the Occurrence and Detection cell, and the RPN formula needs to be created manually one by one. RPN will be calculated automatically within a second for the whole FMEA worksheet.

Dedicated FMEA Software

ReliaSoft’s XFMEA software was an early promoter of this approach and has provided flexible support for configurable risk ranking logic since Version 5 (released in 2010). Specialized FMEA software offers features like automatic RPN calculation, risk visualization, action tracking, and integration with other quality management systems.

Training Your Team on RPN Calculation

Effective RPN implementation requires proper training for all team members involved in the FMEA process.

Key Training Topics:

  • FMEA fundamentals and methodology
  • Understanding severity, occurrence, and detection rating scales
  • Proper identification of failure modes, effects, and causes
  • RPN calculation mechanics and interpretation
  • Risk prioritization strategies and decision-making
  • Developing effective corrective actions
  • Documentation requirements and best practices
  • Industry-specific standards and requirements

Regulatory and Standards Considerations

Various industry standards provide guidance on FMEA and RPN implementation:

  • AIAG-VDA FMEA Handbook: Joint automotive industry standard published in 2019
  • SAE J1739: Potential Failure Mode and Effects Analysis in Design (Design FMEA), Potential Failure Mode and Effects Analysis in Manufacturing and Assembly Processes (Process FMEA)
  • IEC 60812: Analysis techniques for system reliability – Procedure for failure mode and effects analysis (FMEA)
  • MIL-STD-1629A: Military standard for FMEA procedures
  • ISO 14971: Application of risk management to medical devices

Understanding applicable standards ensures your FMEA process meets regulatory requirements and industry expectations.

Tracking RPN values over time provides valuable insights into the effectiveness of your risk management efforts.

Key Metrics to Monitor:

  • Average RPN across all failure modes
  • Number of failure modes exceeding threshold values
  • Percentage reduction in RPN after corrective actions
  • Time to implement corrective actions
  • Number of high-severity failure modes
  • Correlation between RPN and actual field failures

As an example, the following image shows a partial FMEA worksheet in the ReliaSoft Cloud web-based software with both initial and revised RPNs and action priorities (APs). If the FMEA team uses a commonly agreed logic to assign potential failure causes to different risk levels (aka “action priorities”) such as High, Medium or Low, they can also visualize a risk profile like the example shown next. In this dashboard tile generated in the ReliaSoft Cloud software, the FMEA team has identified 28 potential failure causes for the design, with 21% initially assessed as high priority and reduced through improvement efforts.

Conclusion: Maximizing the Value of RPN in Your Organization

FMEA scoring through Risk Priority Numbers provides organizations with a powerful framework for identifying, prioritizing, and addressing potential failures before they impact customers. By systematically evaluating severity, occurrence, and detection, teams can make informed decisions about where to invest improvement resources. Whether you are implementing lean six sigma initiatives or working through the recognize phase of process improvement, mastering FMEA scoring enables your organization to proactively manage risk and enhance quality.

Calculating RPN is more than a mathematical exercise—it’s a systematic approach to understanding and managing risk. The RPN gives us an excellent tool to prioritize focused improvement efforts. When implemented effectively with cross-functional teams, data-driven ratings, and a commitment to continuous improvement, RPN becomes a cornerstone of organizational excellence.

Implementing FMEA is a practice that delivers significant benefits for organizations seeking to manage risks proactively and efficiently. Through a detailed analysis of failure modes and their impacts, this methodology helps prevent problems and fosters a safer and more productive environment. The key is maintaining focus on the ultimate goal: preventing failures, improving quality, and delivering value to customers.

By following the step-by-step approach outlined in this guide, understanding the three components of RPN, applying appropriate prioritization strategies, and implementing effective corrective actions, your organization can harness the full power of RPN to drive quality improvement, reduce risk, and achieve operational excellence. Remember that FMEA and RPN are living tools that should evolve with your processes, products, and organizational learning—regular reviews, updates, and continuous improvement ensure they remain valuable assets in your quality management toolkit.

For additional resources on quality management and risk assessment methodologies, visit the American Society for Quality FMEA resources and the Automotive Industry Action Group for industry-specific standards and best practices.