How do you calculate a configuration RPN?

Multiply the severity, occurrence, and detection scores, each rated 1 to 10. With severity 6, occurrence 4, and detection 5, the RPN is 120 on the standard 1 to 1000 scale, the number you rank against other failure modes.

What RPN requires corrective action?

Many instrument-manufacturing teams act on RPNs above roughly 80 to 125, and treat anything near or above 100 as a priority. A score in that band means the combination of impact, frequency, and detectability is no longer acceptable as-is.

What do severity, occurrence, and detection mean here?

Severity is how bad the impact of a mis-configuration is, occurrence is how likely the error happens during the build, and detection is how hard it is to catch before shipment, where a high detection score means it is easily missed.

Why is a high detection score bad?

In FMEA, a 10 on detection means the error is almost impossible to catch before the customer sees it, so it inflates the RPN. Improving detectability through automated configuration checks is often the cheapest way to drop the score.

RPN vs criticality: what is the difference?

RPN blends all three factors into one number, while criticality emphasizes severity and occurrence and is often used when a low-detection score might otherwise mask a dangerous failure. Use criticality as a cross-check when severity is high.

How do I lower a configuration RPN?

Reduce occurrence with guided ordering and module keying, improve detection with automated build-verification and end-of-line config audits, and where possible cut severity by designing options so a wrong choice degrades gracefully rather than failing hard.

Lab Equipment & Scientific Instrument Manufacturing calculator

Configuration Complexity Risk Score Calculator

Configuration option complexity uses an FMEA-style Risk Priority Number to rank the danger of a build-configuration error on a configurable instrument. Quality and product engineers in scientific-instrument manufacturing use it to triage which option combinations deserve poka-yoke, extra verification, or design simplification. It matters because highly configurable instruments multiply the ways a wrong module, firmware load, or option flag can ship undetected. By scoring severity, occurrence, and detection, teams turn a vague sense of risk into a comparable number that drives where corrective action goes first.

What this calculator does

Score the manufacturing risk associated with a specific instrument configuration or custom option combination. Uses a severity-occurrence-detection (SOD) framework to produce a risk priority number (RPN). Helps engineering and operations teams prioritize which custom configurations need additional validation, assembly instructions, or test protocols before committing to production.
Use when evaluating new configuration options, reviewing custom build requests, or deciding which instrument variants need additional manufacturing controls. High RPN scores indicate configurations that may cause assembly errors, test failures, or field issues without additional process controls.
It multiplies severity, occurrence, and detection scores to produce a Risk Priority Number for a specific configuration failure mode.

Formula used

Risk Priority Number (RPN) = severity x occurrence x detection
RPN above 80 to 125 typically requires corrective action in instrument manufacturing.

Inputs explained

Severity of configuration error:
Occurrence likelihood:
Detection difficulty:

How to use the result

Use it during design FMEA or process FMEA of a configurable product line to prioritize which configuration risks to mitigate.
RPN is ordinal, not a true probability, and equal RPNs can hide very different severities; a high-severity, low-occurrence mode may need action even when its RPN looks moderate.

Current U.S. benchmarks

Steel mill PPI stands at 348.53 (BLS, May 2026), up 6.7% from a year earlier. New factory orders are up 2.3% year over year (Census).

Common questions

How do you calculate a configuration RPN? Multiply the severity, occurrence, and detection scores, each rated 1 to 10. With severity 6, occurrence 4, and detection 5, the RPN is 120 on the standard 1 to 1000 scale, the number you rank against other failure modes.
What RPN requires corrective action? Many instrument-manufacturing teams act on RPNs above roughly 80 to 125, and treat anything near or above 100 as a priority. A score in that band means the combination of impact, frequency, and detectability is no longer acceptable as-is.
What do severity, occurrence, and detection mean here? Severity is how bad the impact of a mis-configuration is, occurrence is how likely the error happens during the build, and detection is how hard it is to catch before shipment, where a high detection score means it is easily missed.
Why is a high detection score bad? In FMEA, a 10 on detection means the error is almost impossible to catch before the customer sees it, so it inflates the RPN. Improving detectability through automated configuration checks is often the cheapest way to drop the score.
RPN vs criticality: what is the difference? RPN blends all three factors into one number, while criticality emphasizes severity and occurrence and is often used when a low-detection score might otherwise mask a dangerous failure. Use criticality as a cross-check when severity is high.

Last reviewed 2026-05-12.