Product Risk & Critical-to-Quality FMEA Matrix

The formula

This is the expression the tool evaluates. Every term is named underneath, with the unit it must be supplied in.

How the result is derived

Step by step, from the values you type to the figure on screen.

1. The 6 inputs are read from the form on every keystroke: Severity, Occurrence, Detection, Action Threshold, Occurrence After Action and Detection After Action.
2. Each value is checked against the accepted range in the input table below. A value outside its range stops the calculation rather than producing a misleading figure — the results blank out and a message appears.
3. The validated values are substituted into the expression above, which resolves Risk Priority Number together with every supporting figure in one pass — no value is carried over from a previous entry.
4. The supporting outputs — Criticality, RPN After Actions, Risk Reduction, Margin Over Threshold, RPN if Only Detection Improves and RPN if Only Occurrence Improves — come from the same pass, so they always describe the same case as the headline figure.
5. Results are rounded for display only. The full-precision value is used throughout the chain, so reading a rounded intermediate figure back into the tool by hand can shift the last digit.

What each input means

Where to read each value on the floor, the unit it must be in, and the range the tool accepts.

What the tool returns

The headline figure and every supporting value it is built from.

Worked example

The tool loads with this case already solved — the Risk Priority Number shown above is its answer. Change one value and the difference from this baseline is the sensitivity of the result to that variable.

How to use it

1. Work through the input groups in order — Current Risk and Planned Actions. The defaults are a realistic case, so you can change one value at a time and watch what moves.
2. There is no calculate button. Every figure recalculates as you type or drag, which is what makes this usable for a what-if sweep rather than a single answer.
3. Read Risk Priority Number in the dark results panel — that is the headline figure, expressed in RPN.
4. Check the supporting rows underneath (Criticality, RPN After Actions, Risk Reduction, Margin Over Threshold, RPN if Only Detection Improves and RPN if Only Occurrence Improves) before acting on the headline — they are where an implausible input usually shows itself first.
5. Reset to defaults returns every field to the reference case, which is the quickest way to check whether a surprising result came from the tool or from an input you had changed earlier.

Where this is used

• Process planning — establishing Risk Priority Number before a trial is booked, so machine time and material in Product Engineering, Specifications & Feasibility are committed against a calculated figure rather than an estimate.
• Costing and quotation — Risk Priority Number is an input to the cost sheet, and quoting from a worked number rather than a remembered one is what keeps a margin intact.
• Troubleshooting — when the floor result drifts from plan, entering the measured values (starting with Severity) shows how much of the gap in Risk Priority Number each variable explains.
• Teaching and study — the accepted ranges bracket normal Product Engineering, Specifications & Feasibility practice, so moving one variable at a time shows the shape of the relationship rather than a single answer.

Assumptions and limits

• RPN multiplies ordinal ratings as though they were measurements, which they are not — a severity of 8 is not twice a 4, so the product has no physical meaning and identical RPNs can represent very different risks. Newer FMEA practice has largely replaced RPN with an action priority table precisely because of this, and a high severity should trigger action regardless of how low the product is. Use the number to rank a list, never to decide that a risk is acceptable. Improving detection also does nothing to prevent the failure: it catches defects that were still made, and where severity is high, occurrence is the only honest lever.
• Every input is bounded to the range normal practice occupies (Severity 1 to 10 1–10, Occurrence 1 to 10 1–10 and Detection 1 to 10 1–10, and so on for the rest). Those bounds are guard rails against typing errors, not a claim that the formula fails one unit outside them.
• The calculation is deterministic: the same inputs always give the same result. It carries no allowance for machine condition, operator skill, ambient conditions or lot-to-lot material variation unless an input above explicitly represents one.
• Nothing is sent anywhere. The maths runs in your browser, so the numbers you type never leave the page.

Questions people ask