Plant Utilities worked example

Utility Shutdown Risk Score with production impact severity of 20 score: a worked example

What does the result look like when production impact severity reaches 20 score? The full calculation is worked below with real intermediate numbers. Use it when reviewing utility shutdown risk score for a utility budget, maintenance priority, capacity check, energy project, or production support plan.

The inputs for this scenario

  • Production impact severity: 20 score (raised for this scenario; the documented default is 8)
  • Failure likelihood: 5 score (unchanged)
  • Detection and redundancy weakness: 4 score (unchanged)

Working through the calculation

  • Applying the documented formula (Risk score = severity × 0.40 + likelihood × 0.35 + detection or redundancy weakness × 0.25) to the inputs above produces each figure below.
  • At this operating point the engine returns 10.75 score for utility shutdown risk score, the number this scenario is built around.
  • At this operating point the engine returns 20 score for severity.
  • At this operating point the engine returns 5 score for occurrence.
  • At this operating point the engine returns 4 score for detection.

How this compares with the baseline

  • Against the tool's baseline example, where production impact severity sits at 8 score and the headline result is 5.95 score, this scenario comes in 80.67% above the baseline at 10.75 score.
  • A figure at this level is achievable when production impact severity is genuinely sustained, not just peaked for a shift. The weights are fixed and the scale is subjective; two teams scoring the same event can differ, so calibrate anchors and use scores for relative ranking, not absolute probability.

Results at a glance

  • Utility shutdown risk score: 10.75 score (headline result)
  • Severity: 20 score
  • Occurrence: 5 score
  • Detection: 4 score

Run it with your numbers

  • Every input above is editable in the live Utility Shutdown Risk Score calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.