Menu
The Iceberg Effect of Downtime: Why You Underestimate Losses by 300%

The Iceberg Effect of Downtime: Why You Underestimate Losses by 300%

Key Takeaways

 

  • The "Visible" vs. "Hidden": Most downtime reports only track direct labor and maintenance parts. This is just the tip of the iceberg (10% of total cost).

  • The Opportunity Cost: The biggest loss isn't what you spent fixing the machine; it's the revenue you didn't make while the machine was stopped. In sold-out plants, this is pure profit loss.

  • The "Ripple" Effect: Downtime causes quality defects (startup scrap), energy waste (idling machines), and employee burnout. The best way to stop the bleeding is to Automate Data Collection to see the full financial picture.

The Iceberg Effect of Downtime: Why You Underestimate Losses by 300%

The Iceberg: 10% Visible, 90% Hidden

Most plant downtime reports track labor hours and replacement parts. That is the visible 10% of the iceberg.

The other 90% never appears in the Excel report:

  • Opportunity cost: revenue you did not make while the machine was stopped
  • Quality cascade: defects after restart, scrap from startup, rework
  • Labor reallocation: idle operators on payroll, overtime to catch up

 

EU benchmark: typical packaging plant reports €120/hour downtime cost. Full cost: €440-€560/hour when measured properly. The 300% gap is the iceberg.

See OEE benchmarks by sector for comparable cost-per-hour data.

The 3 Hidden Cost Categories

1. Opportunity cost. The biggest hidden category. In a sold-out plant, every minute of downtime is a minute of margin lost forever.

  • Math: planned production rate × idle minutes × margin per unit
  • EU packaging benchmark: €180-€240/hour in sold-out condition
  • Why it is hidden: revenue you did not make does not appear in any cost report

 

2. Quality cascade. Restarting after downtime is not free. Startup defects, parameter drift, and rework eat 5-15% of the next batch.

  • Math: scrap units × full unit cost (material + labor + overhead)
  • EU benchmark: €60-€120/hour cascade cost on typical lines
  • Why it is hidden: scrap is logged in the next shift, not the downtime event

 

3. Labor reallocation. Operators stay on payroll during the stop. Catch-up shifts add overtime. Other lines wait for upstream throughput.

  • Math: (idle operator-hours × loaded hourly cost) + (overtime hours × 1.5x premium)
  • EU benchmark: €80-€140/hour in fully-staffed plants
  • Why it is hidden: payroll is fixed and looks separate from the event

 

See how this maps to the 6 OEE losses.

Why Excel Hides 88% of the Cost

Excel does not hide costs maliciously. It hides them structurally.

Each hidden cost category lives in a different system: opportunity cost in the ERP, quality cascade in the QMS, labor reallocation in payroll. The downtime event lives in maintenance.

A modern OEE solution with native CMMS pulls all four together automatically: the downtime event triggers ERP margin loss calculation, QMS startup defect tracking, and payroll idle-cost capture.

That is the difference between Fabrico and four disconnected spreadsheets. The iceberg becomes visible.

How to Calculate the True Cost

True cost per downtime hour =

(Visible: labor + parts) + (Opportunity cost) + (Quality cascade) + (Labor reallocation)

Worked example: typical European packaging line, 1 hour of unplanned downtime in sold-out condition:

  • Labor + parts (visible): €120
  • Opportunity cost (margin × production rate): €220
  • Quality cascade (startup defects on 30-minute restart curve): €90
  • Labor reallocation (8 operators idle + 4-hour overtime catch-up): €110
  • True cost: €540/hour

 

The Excel report showed €120. Reality: €540. The 4.5x gap is the iceberg.

See how to calculate OEE with a real-world example using the same numbers.

Related articles

Latest from our blog

Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration