Fmea Risk Priority Number Interactive Calculator

If you let failures slip through your process without a way to size up the risk, the team ends up spending more time fixing problems than preventing them. That's what the FMEA Risk Priority Number (RPN) is built for. This calculator quickly tallies up a numerical risk score from Severity, Occurrence, and Detection ratings (all set from 1–10). The method turns up everywhere risky failures matter: manufacturing, automotive, aerospace, and medical devices. Below you'll find the RPN formula, a full worked example, some straight talk on rating scales, and a no-nonsense FAQ.

What is FMEA Risk Priority Number?

The FMEA Risk Priority Number (RPN) is a score from 1 to 1000 that flags how risky a given failure mode is. It's just Severity × Occurrence × Detection — so the higher the score, the higher the priority for fixing that problem.

Simple Explanation

You set three numbers: how bad the result is, how likely it happens, and how likely you’ll catch it before it causes trouble. Multiply them. Low numbers mean low worry. If your RPN is high, you’ve got something worth fixing. Don’t get hung up on chasing a “perfect” 10 or a “safe” single-digit. You’re looking for the points that stick out far above the rest, so you know where to focus your resources.

📐 Browse all 1000+ Interactive Calculators

How to Use This Calculator

1. Select your calculation mode from the dropdown — standard RPN, reverse-engineer a required rating, action priority, or revised RPN after improvements.
2. Enter your Severity (S), Occurrence (O), and Detection (D) ratings, each on a scale of 1 to 10.
3. If your mode requires it, enter a Target RPN, Action Threshold, or Revised ratings in the additional fields shown.
4. Click Calculate to see your result.

Simple Example

Severity = 7, Occurrence = 5, Detection = 4

RPN = 7 × 5 × 4 = 140

Risk level: HIGH — corrective action required. Focus on reducing severity or occurrence through engineering controls.

FMEA RPN Diagram

Interactive FMEA Risk Priority Number Calculator

Equations & Formulas

Here's the basic formula for the FMEA Risk Priority Number.

If you need to figure out what value you’d need on a particular rating to meet a target RPN, use the formulas below.

To see the effect of improving controls or process changes, calculate RPN reduction this way:

Theory & Engineering Applications

Failure Mode and Effects Analysis (FMEA) is a core tool for risk assessment in engineering. RPN is its practical number — a systematic way to stack-rank what to fix, factoring in how bad a failure is, how often it might happen, and how likely you’ll catch it before it reaches the end user. All three are needed to avoid chasing the wrong problems.

The Three-Dimensional Risk Model

Traditional risk looks at probability and impact, but FMEA adds detectability — because it’s just as relevant to ask: can we catch this before damage is done? Multiplying these three ratings gives an RPN scale of 1 (best possible: low impact, rare, easy to detect) to 1000 (worst: catastrophic, frequent, undetectable). This scale is blunt by design; it forces separation but doesn’t try to deliver an illusion of fine precision.

For severity, think about the most realistic “what if” outcome if the failure slips through — not the absolute worst physics-defying outcome, and not just the average. In automotive, a 9 or 10 often connects to a real safety concern or regulatory breach. In medical devices, these numbers tie right back to risk categories for patients. Use the highest reasonable scenario, not the apocalypse.

Occurrence is based on how often things have actually failed, or what your best engineering judgment says for new stuff. If you’ve got data — MTBFs, defect rates, even previous similar jobs — use it. If you lack data, use the highest estimate you can defend and adjust it later. Each industry rates occurrence a little differently, and mapping those numbers to something statistical (like MTBF in aerospace, or bug counts in software) is often more art than science.

Detection is about the actual chance your system will spot the failure before it matters. Beware the trap: just because a process is “100% inspected” doesn’t mean detection is near-perfect, especially with manual checks. Factory workers and camera systems don’t miss defects at the same rates, even if the form says “inspected.” Lean toward real-world performance, not what’s on the spec sheet.

RPN Thresholds and Action Priority Logic

Most organizations set an RPN threshold to trigger action, anywhere from 80 to 125 depending on their risk appetite. But just relying on a set RPN cutoff can be risky. For major problems (like a severity of 9 or 10), you need a rule that says any of these get flagged, no matter what Occurrence or Detection says. Otherwise, you get odd cases where a dangerous failure passes under the threshold just because it’s unlikely or easily detected — which isn’t good enough if the cost of even one is too high.

When figuring out where to put your resources, reducing a big number by half feels more satisfying — but a lower-priority RPN may be much cheaper to drop. A lot of teams now weigh the risk reduction against implementation costs. If you’re dealing with budgets, look to show which fixes give the “biggest bang for the buck,” rather than blindly chasing whichever RPN is highest.

Worked Engineering Example: Hydraulic Actuator Assembly

Take a hydraulic linear actuator on an automated welding cell. Suppose “Seal degradation causing fluid leakage” is identified as a possible failure mode. Walk through each rating based on what you can actually observe or defend:

Severity: If fluid leaks, you might get misaligned welds. There’s a feedback system, so most gross problems get caught before the weld. Realistically, worst case is some structural issues on parts that get through, but the feedback reduces the risk. Assign S = 7.

Occurrence: Seals are rated for high cycle counts, but data shows some degrade earlier — on average, failure every 1 in 150 maintenance cycles. That’s O = 4.

Detection: Position sensors catch most drift well before catastrophic leaks, but the sensor logic isn’t perfect (software issues in the past). Assign D = 4, since detection is above average but not bulletproof.

So, RPN = 7 × 4 × 4 = 112. If your company acts at 100 or above, you need to fix this.

Here’s how you might address it:
Option 1: Better seal material — drops Occurrence to 2. RPN = 56, cost is moderate.
Option 2: Add a pressure sensor — drops Detection to 2. Also RPN = 56, cost is higher and implementation is more complex.
Option 3: Redesign fixture to avoid misalignment impact — drops Severity to 4. RPN = 64, but major up-front costs.

In this case, the company chose the better seal as a practical, cost-effective fix. Each step is documented in the FMEA, and any retrofits or upgrades get rolled in during routine maintenance, not overnight.

Industry-Specific Applications

Automotive suppliers are usually stuck using FMEA and RPN because quality standards mandate it. Those numbers are subject to customer audits, and there are rating tables that tie your occurrence rating to measured process capability (like Cpk values). In aerospace, FMEA is run on both hardware and software; ratings may be tied to things like defect density or code coverage for detection. Medical device makers need FMEA for regulatory submissions, and auditors will question any severe risks, even if their mathematically low RPN says it’s “OK.”

In process industries (chemical, food, pharma), FMEA may also cover environmental and safety risks. If a catastrophic but rare event gives an RPN that’s lower than a routine quality issue, you may need an override rule to keep those hazards from slipping through unaddressed.

For more engineering calculators or reference tools, check out our calculator library. You'll find stuff for reliability, statistical process control, and Six Sigma without fluff.

Practical Applications

Frequently Asked Questions

Video Walkthrough - How to Use This Calculator