Cost of Downtime by Industry: Benchmarks

The cost of downtime varies enormously by industry: published 2024 benchmarks put an hour of unplanned downtime at roughly $2.3 million in automotive but around $36,000 in fast-moving consumer goods, with cross-sector medians near $125,000 per hour. The spread reflects how tightly coupled and capacity-constrained each sector's production is, the benchmark is a starting point, not your number.

Ask "how much does downtime cost?" and you will find figures ranging from a few thousand dollars an hour to millions, all quoted confidently. Both can be right, because the answer depends heavily on the industry, and even more on the specific line. This guide lays out the published per-hour downtime benchmarks by sector, explains why the spread is so wide, and shows why the only figure that should drive your maintenance budget is the one you calculate for your own plant.

How much does downtime cost by industry?

Downtime cost by industry spans several orders of magnitude. The most-cited recent source, an industry analysis published by Siemens in 2024, anchors the extremes: automotive manufacturing at roughly $2.3 million per hour and fast-moving consumer goods (FMCG) at roughly $36,000 per hour. Broad cross-sector surveys land in between, with medians around $125,000 per hour. Treat every figure below as an order-of-magnitude benchmark, not a quote for your line.

Why is the cost of downtime so different across industries?

Downtime costs differ across industries because three things vary: how tightly coupled the production line is, how capacity-constrained the plant is, and how expensive the product and its spoilage are. An automotive final-assembly line is the extreme case on all three, a single stopped station backs up welding, paint, assembly, and outbound shipping at once, on a plant that is often sold to capacity. An FMCG line with buffer stock and the ability to catch up costs far less per stopped hour.

The factors that move a plant up or down the scale:

• Coupling. Tightly linked, single-flow lines (automotive, continuous process) lose far more per stop than buffered, parallel lines, because one stop halts everything downstream.
• Capacity constraint. A sold-out plant loses real margin on every stopped minute; a plant with slack can often make the units up later, so its stop cost is mostly labor and restart.
• Product value and perishability. High-value units and perishable product (a spoiled batch, a broken cold chain) raise the cost of a stop sharply, one reason food and beverage downtime hits harder than the headline FMCG figure suggests.
• Restart cost. Processes that scrap product or need long re-warm, re-sterilize, or re-prime cycles after a stop carry a heavy fixed penalty per event.
• Safety and compliance exposure. In regulated sectors, a stop can trigger holds, investigations, or product at risk, costs the per-hour number rarely captures.

What is the total cost of downtime across industry?

At the macro level, the numbers are staggering. The Siemens 2024 analysis estimates unplanned downtime costs the world's 500 largest companies about $1.4 trillion a year roughly 11% of their annual revenue up sharply from an estimated $864 billion in 2019–2020. Whether or not your plant is anywhere near the sectors that dominate that figure, the direction of travel is the point: as lines get more automated and more tightly coupled, the cost of a stopped hour keeps climbing.

• Unplanned downtime costs the world's 500 biggest firms an estimated $1.4 trillion per year, about 11% of revenue (Siemens, True Cost of Downtime 2024).
• Automotive is quoted at roughly $2.3 million per hour and FMCG at roughly $36,000 per hour in the same Siemens True Cost of Downtime report.
• Cross-sector reliability surveys of plant maintenance leaders put the median nearer $125,000 per hour, and older large-plant averages near $260,000, the wide spread reflecting different plant sizes and methodologies.

Where does food and beverage fit?

Food and beverage plants usually sit toward the lower end of the headline benchmarks, closer to the FMCG figure than to automotive, but that undersells the real cost, because the per-hour average hides what makes food downtime bite. A stop that breaks a cold chain, ruins an in-process batch, or forces a re-sanitation cycle carries costs a generic per-hour number never sees: scrapped product, re-cleaning and re-validation time, and in the worst case product placed on hold. A ten-minute stop on a filler is cheap; a ten-minute stop that spoils a tank of product is not. For food and beverage operations, the perishability and restart factors matter more than the sector average, which is exactly why the plant-specific calculation beats the benchmark here more than almost anywhere.

Why don't the published downtime numbers agree?

Because they measure different things. Some studies count only lost production; others add labor, scrap, restart, penalties, and reputational cost. Some survey the largest global firms; others sample mid-size plants. Some ask maintenance leaders to estimate; others reconstruct from records. That is why an "average" can be $36,000 in one source and $260,000 in another without either being wrong, they are answering different questions on different populations. The practical lesson is not to chase the "right" benchmark but to define your own number precisely and apply it consistently.

Why the benchmark is not your number

An industry benchmark is useful for context and for making the case that downtime is worth attacking, but it is a bad basis for a budget, because your line is not the industry average. Two plants in the same sector can differ tenfold: one runs a sold-out, tightly coupled line where every minute is lost margin; the other has buffer stock and slack and loses mostly labor and restart. The benchmark cannot see that difference. Your own per-minute math can.

This is where a benchmark article and a cost calculation part ways. A per-industry figure answers "roughly what is downtime worth in my sector?" The question that actually sets priorities is "what does a stopped minute cost on this line?", computed from lost contribution margin, idle labor, and scrap and restart cost. Our machine downtime guide walks the full per-minute method, and you can run your own lines through it directly with the downtime cost calculator which handles both the capacity-constrained and non-constrained cases.

How do you use a downtime benchmark responsibly?

Use the benchmark to start the conversation, then replace it with your own figure as fast as you can. The sequence:

1. Find your sector's rough figure. Locate your industry in the benchmarks above to set an order of magnitude. This is for framing, not budgeting.
2. Calculate your own per-minute rate. For your critical lines, add lost margin per minute (if capacity-constrained), idle labor per minute, and scrap and restart cost per minute. This one number outranks any published benchmark.
3. Do it per line, not per plant. The spread between lines inside one plant is usually large; a single plant-wide average hides where the money actually is.
4. Attach the rate to your downtime data. Multiply each reason code's minutes by the line rate to get dollars per cause. Dollars-per-code is a sharper priority list than minutes-per-code, because a short stop on the bottleneck outranks a long stop on a line with slack.
5. Rank the fixes by dollars, then act. Take the top one or two dollar-weighted causes and drive them out, through better PM, condition monitoring, or a defect elimination program for the chronic ones.

From benchmark to action

Knowing your sector loses six figures an hour is only useful if it moves effort upstream. That is the entire argument for climbing the equipment reliability ladder: every dollar of downtime the benchmark implies is a dollar of reason to shift from reactive firefighting toward preventive work, condition-based maintenance and predictive maintenance on critical assets, and operator-led care through total productive maintenance. The benchmark sizes the prize; your own downtime data and per-minute rate tell you where to collect it. Watch the six big losses and keep your maintenance backlog from feeding the reactive share.

Turning a per-hour benchmark into per-line action needs downtime, quality, and machine data in one place, priced. Harmony ties stops, reason codes, and machine signals into one operational layer, applies your per-minute rate automatically so losses show up in dollars by cause, and surfaces the patterns worth fixing first, flag it, notify the right person, draft the work order for approval. It layers onto the ERP, MES, and machines you already run. No rip-and-replace. See how CLS moved from paper logs to same-shift intervention or how the platform works.

Start by finding your sector's order of magnitude above, then spend an afternoon calculating the real per-minute rate for your worst line. The gap between the two is usually the most useful number you will produce this quarter.