operations-quality · quality-six-sigma · risk-analysis-fmea

FMEA RPN Calculator

Scores failure modes by severity, occurrence and detection to a risk priority number, with a severity gate for high-harm modes. Use it to rank and triage risks in an FMEA.

Last updated
Repeating-Item Builder

Calculator overview

Inputs and outputs

This summary comes from the calculator's published input and output contract.

Inputs

Medium Priority Risk Priority Number Threshold
About this input

The risk priority number at or above which a mode is at least medium priority. Modes between this and the high threshold are counted as medium.

Unit RPN Default 100 Range 1 to 1000
Severity Escalation Threshold
About this input

The severity rating, on the 1 to 10 scale, at or above which a mode is escalated regardless of its risk priority number. A high-severity failure can matter even when occurrence and detection are low.

Unit severity Default 8 Range 1 to 10
Failure Modes
About this input

One row per failure mode: its description and its severity, occurrence and detection ratings, each from 1 to 10. The tool multiplies the three ratings to get each mode's risk priority number and ranks the set.

Default 10 rows
ColumnRange or allowed values
Item Not declared
Failure mode Not declared
S 1 to 10
O 1 to 10
D 1 to 10
High Priority Risk Priority Number Threshold
About this input

The risk priority number at or above which a failure mode is flagged high priority. Modes reaching this value are counted and highlighted for action.

Unit RPN Default 200 Range 1 to 1000

Outputs

Modes Caught By The Severity Gate Alone
About this output

How many modes are escalated only because their severity reaches the escalation threshold, in count, and would otherwise sit below the risk priority thresholds. It surfaces high-harm failures that a low risk priority number can hide.

Unit count
Model Status
About this output

The overall check on your entries, shown above the results. It reads OK when the inputs are usable, NOT VALID with a reason when an entry makes the model meaningless, or CHECK with a reason when a result is valid but worth a second look. Read it before you trust the numbers below.

No unit declared
Modes Entered
About this output

How many failure modes have been entered, in count. It is the number of rows the summary is based on.

Unit count
Total Risk Priority Number
About this output

The sum of the risk priority numbers of all entered modes. It is a rough gauge of overall risk and the base for the top-three share.

Unit RPN
Share Of Total Risk Priority Number In The Top Three
About this output

The combined risk priority number of the highest-ranked modes as a share of the total, between 0 and 1. Ties are included: if four modes share the third-highest number, all four count, so the share can cover more than three modes. A large share means risk is concentrated at the top of the list.

Unit %
Medium Priority Modes
About this output

How many modes fall in the medium-priority band, in count, at or above the medium threshold but below the high threshold.

Unit count
Highest Criticality
About this output

The largest product of severity and occurrence among the entered modes, expressed as severity times occurrence. It ranks risk by how often harm occurs, ignoring how well it is detected.

Unit S x O
High Priority Modes
About this output

How many modes reach the high-priority threshold, in count. These are the ones to address first.

Unit count
Highest Risk Priority Number
About this output

The largest risk priority number among the entered modes, out of a maximum of 1000 (ratings run 1 to 10 and multiply). This is the classic RPN method: simple to read, but it treats severity, occurrence and detection as equally weighted, which the AIAG-VDA action-priority tables deliberately do not. Use it to rank, not to certify.

Unit RPN
Mean Risk Priority Number
About this output

The average risk priority number across the entered modes. Read it alongside the highest value, since one severe mode can sit behind a modest average.

Unit RPN
Low Priority Modes
About this output

How many modes fall below the medium threshold, in count. Lower priority does not mean no action; review them after the higher bands.

Unit count

What it is

The FMEA RPN Calculator scores a list of failure modes and ranks them. You enter one row per mode with its severity, occurrence and detection ratings on the usual 1 to 10 scales, and it computes each mode's risk priority number, sorts the list into priority bands against thresholds you set, and escalates any mode whose severity alone is high enough to demand attention regardless of its score.

It reports how many modes fall in each band, the highest and mean risk priority numbers, the largest severity-by-occurrence product, and how much of the total risk is concentrated in the top three modes.

Use it to triage an FMEA worksheet. This is the classic risk priority number method, which is deliberately not the Action Priority approach that the current AIAG-VDA handbook uses in its place.

Methodology

Purpose and model boundary

This calculator ranks up to 15 entered failure modes with the traditional FMEA risk priority number (RPN), summarizes the distribution of risk, and applies user-authored high, medium, and severity-escalation thresholds. It is a prioritization aid. It does not perform an AIAG-VDA Action Priority lookup, prove that controls are effective, establish an acceptable residual risk, or certify an FMEA.

Inputs and units

Each used grid row contains an item label, a failure-mode label, and integer severity (S), occurrence (O), and detection (D) ratings from 1 through 10. A row is either complete or wholly blank: blank rows are unused capacity, while a partly filled row is rejected before calculation. Labels are descriptive; the arithmetic is driven by the three ratings. The high- and medium-priority thresholds are RPN values from 1 through 1000. The severity-escalation threshold is a rating from 1 through 10. The high RPN threshold must exceed the medium threshold.

Governing relationships

For each entered mode i, the workbook calculates

  • RPN_i = S_i * O_i * D_i;
  • Criticality_i = S_i * O_i;
  • SeverityGate_i = 1 when S_i >= severity threshold, otherwise 0.

The priority band is evaluated in this order:

  1. High when RPN_i >= high threshold or the severity gate is true;
  2. Medium when it is not High and RPN_i >= medium threshold;
  3. Low otherwise.

The summary uses MAX, SUM, and the arithmetic mean of positive RPN rows. Modes are ranked with Excel RANK. The reported top-three share is sum(RPN_i where rank_i <= 3) / total RPN; tied modes at the third rank are all included.

Calculation sequence

  1. Read every row's three ratings and compute RPN, criticality, severity-gate flag, priority band, and rank.
  2. Count positive-RPN rows and summarize maximum, mean, total, and counts by priority band.
  3. Count modes escalated by severity whose RPN would otherwise remain below the high threshold.
  4. Compute the maximum criticality and the ranked top-three share.
  5. Send the per-mode RPN and criticality series to the comparison chart.

Outputs and interpretation

The highest and total RPN values show scale and aggregate exposure, while the mean gives context across the entered set. High/medium/low counts reflect the thresholds selected for this analysis, not universal boundaries. The severity-gate-only count identifies modes whose possible harm elevates them despite a lower product score. Criticality deliberately excludes detection; it emphasizes how severe and frequent a failure is before detection controls are considered.

Validation and status logic

The workbook evaluates status in this order:

Condition Returned status
No row has a positive RPN NOT VALID: enter at least one failure mode with non-zero ratings
Any rating exceeds 10 NOT VALID: ratings must not exceed the maximum on the Data sheet
A used row has an incomplete rating triplet NOT VALID: every entered failure mode needs whole-number ratings from 1 up to the maximum on the Data sheet
Severity-escalation threshold is outside 1 through 10 NOT VALID: the severity escalation threshold must be a severity rating between 1 and the maximum on the Data sheet
High RPN threshold is less than or equal to the medium threshold NOT VALID: the high threshold must exceed the medium threshold
None of the above OK

The input rules additionally declare S, O, and D as integers bounded from 1 through 10, declare the RPN threshold bounds, and treat blanks in all five fields as forbidden once any field in that row is entered. Wholly blank rows remain legal spare capacity. Those input checks occur before the workbook status formula.

Assumptions and limitations

RPN multiplication gives equal mathematical weight to three ordinal ratings and can assign the same product to very different risk profiles. The custom severity gate mitigates one weakness but is not the licensed AIAG-VDA Action Priority method. Ratings depend on the team's definitions, evidence, and calibration; scores from different organizations are not automatically comparable. The top-three share includes all ties at rank three and can therefore cover more than three rows. Every scored row must carry both labels so the result remains identifiable and actionable.

Restrictions and non-computing states

The workbook accepts only the authored number of FMEA rows and the rating bounds it publishes. It does not compute the licensed AIAG-VDA Action Priority method. A partly filled row is rejected by the input rules; a wholly blank row is ignored. Missing or out-of-range severity, occurrence, or detection ratings that reach the workbook produce a non-computing state identified by the status message.

Errors and warnings

A rejected entry means a rating, limit, or grid entry did not meet the published input rules. A workbook NOT VALID result means the entered set or thresholds cannot be classified consistently. This workbook has no CHECK branch: a valid entered set returns OK, but that does not imply that the risk is acceptable. A connection or calculation-service failure is a service error rather than an FMEA finding.

References

The workbook derives its relations rather than reproducing any table, chart or figure from a specification, standard or agency publication. The risk priority number is a product of three ratings and the banding is a comparison against thresholds you set; no rating scale definitions are reproduced here.

The first two are cited to identify what this tool is not. If you are required to work to the AIAG-VDA handbook, its Action Priority tables are the method, and this calculator does not implement them.

Rating scale definitions (what a severity of 7 or an occurrence of 4 means for your product) come from your organisation's FMEA procedure. No trademark or organisation name appearing here implies endorsement by its owner.

Additional source notes migrated from Methodology

The workbook implements the traditional S * O * D RPN and S * O criticality relationships plus a custom user-set severity gate. It reproduces no proprietary FMEA table and makes no AIAG-VDA conformity claim; see the dedicated References section for licensing and non-endorsement details.

Frequently asked questions

Is this AIAG-VDA compliant?
No, and deliberately so. The 2019 AIAG-VDA FMEA handbook replaced risk priority number thresholds with Action Priority tables, which look up High, Medium or Low from the combination of the three ratings rather than from their product. This tool implements the classic risk priority number method with an added severity gate. If you are required to work to the handbook, use its Action Priority tables; nothing here should be presented as an Action Priority result.
Why does a mode with a low RPN show up as high priority?
That is the severity gate doing its job. A failure that injures someone but is rare and easily caught might score 10 x 2 x 2 = 40, far below a nuisance failure at 200, and ranking on the product alone would put the nuisance first. Any mode whose severity reaches the escalation threshold is escalated whatever its score, and the number of modes escalated on severity alone is reported separately so you can see how much the gate is doing.
Two modes have the same RPN but feel very different. Is that a bug?
No, it is the method's best-known weakness. 2 x 3 x 4, 1 x 4 x 6 and 1 x 24 all give 24, so the product throws away the information about which rating was high. It is why criticality (severity times occurrence, ignoring detection) is reported alongside, and why the AIAG-VDA handbook moved to Action Priority tables. Read the ratings, not only the product.
Why is criticality reported separately from the RPN?
Because detection is a different kind of thing from the other two. Good detection catches a problem after it has occurred; it does not make the failure less likely or less harmful. A frequent, severe mode with excellent detection controls gets a flattering risk priority number, and criticality strips detection out so that mode cannot hide behind an inspection step.
What thresholds should I use?
There is no universal answer, which is why they are inputs rather than constants. The defaults of 100 and 200 are common conventions and nothing more. Because only 120 of the integers from 1 to 1000 are attainable as a product of three ratings, and they bunch unevenly, any round threshold cuts the list somewhat arbitrarily, so treat the bands as a triage aid and read the modes near a boundary individually.
Does this replace an FMEA?
No. It scores and ranks a list of failure modes, which is one step of an FMEA and not the valuable one. It does not capture causes, effects, current controls, recommended actions, owners, target dates, or the recalculated ratings after actions are taken. The analysis is the team discussion that produces the ratings; this tool only does the arithmetic on the result.
This page is provided by LogicCommons for informational purposes only. Results are analysis outputs computed from the inputs you supply and are not engineering advice, a design, or a substitute for review by a licensed professional under the codes adopted where the work is built. Verify all inputs and results independently.

LogicCommons is in beta. If a result, label, or reference looks wrong, tell us here; we read every message.