Transformers, Coils & Magnetics Manufacturing worked example

Core Loss Estimate with severity of core-loss failure of 15 score: a worked example

Push severity of core-loss failure up to 15 score and the picture changes. This example computes every intermediate figure at that operating point. Use it when core loss estimate in transformers, coils and magnetics manufacturing needs a defensible ranking against other transformers, coils and magnetics manufacturing risks for the next review.

The inputs for this scenario

  • Severity of core-loss failure: 15 score (raised for this scenario; the documented default is 6)
  • Occurrence likelihood of excess core loss: 4 score (unchanged)
  • Detection difficulty before shipment: 3 score (unchanged)

Working through the calculation

  • Applying the documented formula (Core Loss Estimate risk score = severity × 0.40 + occurrence × 0.35 + detection × 0.25) to the inputs above produces each figure below.
  • At this operating point the engine returns 8.15 score for risk score, the number this scenario is built around.
  • At this operating point the engine returns 15 score for severity.
  • At this operating point the engine returns 4 score for occurrence.
  • At this operating point the engine returns 3 score for detection.

How this compares with the baseline

  • Against the tool's baseline example, where severity of core-loss failure sits at 6 score and the headline result is 4.55 score, this scenario comes in 79.12% above the baseline at 8.15 score.
  • It computes a weighted core-loss risk score using 40% severity, 35% occurrence and 25% detection. The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.

Results at a glance

  • Risk score: 8.15 score (headline result)
  • Severity: 15 score
  • Occurrence: 4 score
  • Detection: 3 score

Run it with your numbers

  • Every input above is editable in the live Core Loss Estimate calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.