How do you calculate unit-of-measure conversion risk?

Multiply the three FMEA scores: severity x occurrence x detection. With severity 6, occurrence 4, and detection 3, the risk priority number is the product on your chosen scale — higher means a more urgent conversion to fix.

What is a high RPN for a UoM conversion?

On a 1-10 scale per factor, RPNs above ~100 are high priority and above ~200 are critical. Any conversion with a severity of 9-10 deserves attention regardless of the total, because a single error can scrap product.

Why use FMEA scoring for unit-of-measure errors?

UoM conversions are a textbook silent failure: they pass system validation, look correct, and only surface as a 12x over-order or a short shipment. FMEA forces you to rate how hard the error is to detect, which is where these defects hide.

What drives the detection score for a UoM conversion?

Detection is high (bad) when nothing catches the error before it ships — no reasonableness check on order quantity, no receiving count reconciliation. It is low (good) when a hard ERP rule rejects implausible conversion factors at entry.

Severity vs occurrence — which matters more for UoM risk?

Treat them separately. Occurrence tells you how often a wrong conversion is used; severity tells you the damage when it is. A rarely-used conversion that scraps a $50k batch (high severity) still needs a control even if its RPN looks moderate.

How do I lower a UoM conversion risk score?

Attack detection first — it is usually the cheapest lever. Add an ERP plausibility rule or a receiving reconciliation step, and the detection score (and the whole RPN) drops without changing the part or the supplier.

Manufacturing Master Data & Data Governance calculator

Unit of Measure Conversion Risk Calculator

Unit-of-measure conversion risk scores how dangerous a UoM mapping is in your item master — for example, a part stocked in feet but purchased in meters, or ordered each but issued by the box. It uses the classic FMEA risk priority structure: severity times occurrence times detection. Master data stewards and supply-chain quality engineers use it to rank which conversions to audit first, because a single bad base-to-alternate factor can over-order by 12x or scrap a production run. The higher the score, the sooner that conversion needs a hard validation rule.

What this calculator does

Estimate unit of measure conversion risk for manufacturing master data and data governance using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when unit of measure conversion risk in manufacturing master data and data governance needs a defensible ranking against other manufacturing master data and data governance risks for the next review.
It computes a risk priority number for one unit-of-measure conversion by multiplying its severity, occurrence, and detection scores.

Formula used

Unit of measure conversion risk score = unit of measure conversion risk severity score × unit of measure conversion risk occurrence score × unit of measure conversion risk detection score
Use the same scoring scale across comparable unit of measure conversion risk risks.

Inputs explained

UoM conversion error severity (impact):
UoM conversion error occurrence (frequency):
UoM conversion error detection difficulty:

How to use the result

Use it when triaging UoM mappings during a data-quality audit, ERP cutover, or after a conversion-driven inventory or order error.
RPN treats all three factors as equally weighted multiplicatively, so a catastrophic but rare error can score the same as a trivial frequent one — always review severity in isolation too.

Common questions

How do you calculate unit-of-measure conversion risk? Multiply the three FMEA scores: severity x occurrence x detection. With severity 6, occurrence 4, and detection 3, the risk priority number is the product on your chosen scale — higher means a more urgent conversion to fix.
What is a high RPN for a UoM conversion? On a 1-10 scale per factor, RPNs above ~100 are high priority and above ~200 are critical. Any conversion with a severity of 9-10 deserves attention regardless of the total, because a single error can scrap product.
Why use FMEA scoring for unit-of-measure errors? UoM conversions are a textbook silent failure: they pass system validation, look correct, and only surface as a 12x over-order or a short shipment. FMEA forces you to rate how hard the error is to detect, which is where these defects hide.
What drives the detection score for a UoM conversion? Detection is high (bad) when nothing catches the error before it ships — no reasonableness check on order quantity, no receiving count reconciliation. It is low (good) when a hard ERP rule rejects implausible conversion factors at entry.
Severity vs occurrence — which matters more for UoM risk? Treat them separately. Occurrence tells you how often a wrong conversion is used; severity tells you the damage when it is. A rarely-used conversion that scraps a $50k batch (high severity) still needs a control even if its RPN looks moderate.

Last reviewed 2026-05-12.