Manufacturing decision tools

Downtime economics · Analyzer

True Downtime Cost & Decision Analyzer

Estimate realizable economic loss from an unplanned equipment stoppage, test uncertainty, and calculate the downtime reduction needed to justify an improvement.

Deterministic methodology · Explicit assumptions · No raw plant inputs sent to analytics

Most downtime calculators multiply a revenue rate by stopped time. That is useful as a theoretical exposure, but it can overstate the cash or contribution actually at risk.

This analyzer keeps theoretical lost revenue separate from realizable economic loss. The realizable layer uses expected good output, contribution or another documented avoidable value, plus non-overlapping incremental incident costs.

Worked-example values are prefilled. Replace them with your plant-specific values before using the result for a decision.

Production loss

Use the demonstrated rate of the constrained or actually affected process. Example values are prefilled only to demonstrate the model.

Incremental incident costs

Add only costs attributable to the incident and not already represented in the contribution-value loss.

Decision and uncertainty

Enter the proposed investment and your explicit uncertainty range. These values are not industry benchmarks.

How the downtime-cost model works

  1. Expected good units lost = downtime hours × demonstrated constrained-process rate × expected yield.
  2. Realizable production loss = expected good units lost × contribution or documented avoidable value per good unit.
  3. Realizable economic loss = realizable production loss + idle labor + overtime/recovery + startup scrap + non-overlapping downstream consequences.
  4. The low/high sensitivity cases adjust only the demonstrated rate and downstream consequence by the percentages you enter. All other cost categories remain unchanged.
  5. Break-even downtime avoided = proposed improvement investment ÷ realizable economic loss per downtime minute.

Worked example: a two-hour stoppage

At 100 units/hour, 95% expected yield, and $12 contribution per good unit, two hours of downtime represents $2,280 of forgone contribution. Adding $600 idle labor, $500 recovery overtime, $250 startup scrap, and $400 of non-overlapping downstream consequence produces $4,030 of realizable economic loss. The same event at $20 revenue per good unit shows $3,800 of theoretical lost revenue, but that revenue figure is deliberately not added to the $4,030 realizable loss.

Assumptions and limitations

  • The model is a decision-support estimate, not an accounting posting or probability model.
  • Do not use full selling price as realizable loss unless the full revenue is genuinely avoidable and not replaced later.
  • Do not add cost categories that duplicate the same economic consequence.
  • The affected-process rate should reflect the actual production constraint. A nameplate rate can materially overstate loss.
  • Safety, regulatory, customer-critical, and technical feasibility constraints can override a purely economic recommendation.

Frequently asked questions

Should downtime cost use revenue or contribution margin?

For an economic decision, contribution or another documented avoidable production value is usually more defensible than full revenue. Revenue can still be useful as theoretical exposure, which is why this tool reports it separately.

How do I avoid double counting downtime costs?

Treat each category as a distinct consequence. If lost contribution already captures the economic effect of missed production, do not add another downstream amount for the same missed units. Add only incremental labor, scrap, logistics, disruption, or other costs that are genuinely separate.

What production rate should I enter?

Use the demonstrated sustainable rate of the constrained or actually affected process during the relevant production context. Avoid an unconstrained nameplate rate unless it is demonstrably achievable and economically relevant.

Is the low/high range a confidence interval?

No. It is a deterministic sensitivity range based on the uncertainty percentages you enter. It does not assign probabilities to the low, base, or high cases.

How should I use the break-even result?

Compare the required avoided downtime with what the proposed improvement can realistically prevent over the same decision horizon. For recurring failures, use observed annual incident frequency instead of assuming a generic industry rate.

Decision guides

Related manufacturing decisions