How do you calculate a configuration complexity risk score?

Multiply the severity, occurrence, and detection ratings on a consistent scale. This calculator combines a severity of 6, occurrence of 4, and detection of 3 into a normalized risk score of about 4.55.

What is a high configuration complexity score?

On a normalized scale, scores in the top quartile of your own catalog are the ones to act on first. Absolute cutoffs vary; what matters is ranking consistently against comparable config risks.

What does the detection rating mean here?

It rates how hard the mistake is to catch before the machine reaches the field. A silent misconfiguration that only surfaces when a customer's card is declined earns a high detection score because it evades your checks.

Severity vs. occurrence — which matters more?

Neither dominates; the product is the point. A rare but catastrophic config error and a frequent but harmless one can score similarly, which is exactly why FMEA multiplies all three dimensions.

How do I lower a configuration complexity score?

You cannot change severity easily, so attack occurrence with defaults and templates and attack detection with automated validation. Adding a pre-ship config check that catches the error drops the detection rating and the overall score.

Do I need the same scale across all my config risks?

Yes. The score is only meaningful for comparison if every failure mode is rated on the identical scale for severity, occurrence, and detection — otherwise the rankings are meaningless.

Vending, Kiosk & Self-Service Equipment calculator

Configuration Complexity Calculator

Configuration Complexity is an FMEA-style risk score for the setup mistakes that plague vending and self-service equipment — planogram mappings, payment endpoint settings, price files, and telemetry parameters. Product and deployment engineers use it to rank which configuration failure modes deserve poka-yoke, better tooling, or a validation step before a machine ships to the field. It matters because a mis-mapped price file or a wrong payment endpoint can silently reject sales across dozens of machines before anyone notices, and the cost of that is far higher than the setup itself. Multiplying severity, occurrence, and detection turns a fuzzy "this config is tricky" into a comparable number that drives where you invest.

What this calculator does

Estimate configuration complexity for vending, kiosk and self-service equipment using production-ready inputs so teams can rank risks and decide which issue needs containment, controls, or escalation first.
Use it when configuration complexity in vending, kiosk and self-service equipment needs a defensible ranking against other vending, kiosk and self-service equipment risks for the next review.
It multiplies severity, occurrence, and detection ratings into a single risk priority score for a specific configuration failure mode.

Formula used

Configuration complexity risk score = configuration complexity severity score × configuration complexity occurrence score × configuration complexity detection score
Use the same scoring scale across comparable configuration complexity risks.

Inputs explained

Failure severity rating:
Misconfiguration occurrence rating:
Detection difficulty rating:

How to use the result

Use it during new-machine onboarding design, config-tool reviews, or after a field incident to prioritize which setup risks to engineer out first.
The score is ordinal — a 4.55 is not literally half as risky as a 9.1 — so it ranks failure modes rather than yielding an absolute risk in dollars.

Current U.S. benchmarks

Global copper trades at $13,484 per tonne (IMF via FRED, May 2026), up 41.5% in a year, and U.S. industrial electricity averages 8.66 cents per kWh. Both feed electrified-hardware unit economics.
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 complexity risk score? Multiply the severity, occurrence, and detection ratings on a consistent scale. This calculator combines a severity of 6, occurrence of 4, and detection of 3 into a normalized risk score of about 4.55.
What is a high configuration complexity score? On a normalized scale, scores in the top quartile of your own catalog are the ones to act on first. Absolute cutoffs vary; what matters is ranking consistently against comparable config risks.
What does the detection rating mean here? It rates how hard the mistake is to catch before the machine reaches the field. A silent misconfiguration that only surfaces when a customer's card is declined earns a high detection score because it evades your checks.
Severity vs. occurrence — which matters more? Neither dominates; the product is the point. A rare but catastrophic config error and a frequent but harmless one can score similarly, which is exactly why FMEA multiplies all three dimensions.
How do I lower a configuration complexity score? You cannot change severity easily, so attack occurrence with defaults and templates and attack detection with automated validation. Adding a pre-ship config check that catches the error drops the detection rating and the overall score.

Last reviewed 2026-05-12.