Manufacturing Downtime Cost: How to Calculate It and Cut I

Unplanned downtime costs manufacturers anywhere from tens of thousands to more than $2 million per hour, depending on the industry and how critical the stopped line is. Published surveys put the median near $125,000 per hour, but your plant's real number is built from your own margins, labor and customer commitments. This guide gives you the benchmarks, a worked calculation you can copy, and the changes that reduce downtime most, including the IT side that plant-floor reports often leave out.

TL;DR

Survey medians sit around $125,000 per hour of unplanned downtime, but sector and plant figures range from about $39,000 to more than $2 million.
Your own hourly cost starts with lost contribution margin at the bottleneck, then adds recovery labor, scrap, expedited freight, restart waste and customer penalties.
Reactive maintenance is the biggest driver: NIST found the most reactive plants had 3.3 times more downtime than the least reactive.
Annual exposure is hourly cost times annual unplanned hours, plus per-event costs times the number of events. Compare that total with what prevention would cost.
Network, server, backup and security failures stop production too, so they belong in the same cost model.

What the benchmarks say an hour of downtime costs
What belongs in your downtime cost
How to calculate manufacturing downtime cost, step by step
What causes unplanned downtime
How to reduce downtime in manufacturing
Our perspective
Put your downtime number to work
FAQ
Sources

What the benchmarks say an hour of downtime costs

No single number fits every plant. The large surveys disagree because they sample different industries, company sizes and definitions of "cost." Read them as a range, then compute your own.

Source	Finding	Scope
ABB Value of Reliability survey (2023)	Median of $124,669 per hour of unplanned outage	3,215 industrial respondents worldwide
Fluke survey release (October 2025)	Average of $400,000 per hour	Decision-makers and maintenance professionals in the U.S., U.K. and Germany
Siemens large-plant study	About $39,000 per hour in fast-moving consumer goods to over $2 million in automotive	Large plants

The spread inside a single survey is just as telling. ABB's sector medians run from $71,047 in metals to $179,056 in energy and power. A metal fabricator and a power plant are not in the same cost bracket, and neither is a stamping line feeding an automotive customer on a just-in-time schedule.

The national picture is large too. NIST's survey of U.S. discrete manufacturing estimated $119.1 billion in preventable maintenance-related losses in 2016. That total included $18.1 billion from downtime, $0.8 billion from defects and $100.2 billion in lost sales caused by delays and defects. Notice where most of the money sits: in lost sales, not in the repair itself.

How often it happens

A 2025 L2L survey of more than 600 U.S. manufacturing leaders across 46 states found an average of 30 downtime hours per facility per month, with more than half unplanned. Six in ten companies reported more than $250,000 in annual downtime costs. ABB's North American results showed that 67% of plants had critical-equipment outages at least monthly.

For a small or mid-sized shop, the practical takeaway is simple. Even if your hourly cost is a fraction of the headline averages, a few dozen unplanned hours a year add up to a six-figure problem.

What belongs in your downtime cost

Most plants undercount. The L2L report cited by Fluke and others is not alone in finding that many companies cannot calculate the figure correctly. The usual mistake is counting only the repair bill or, at the other extreme, charging every fixed cost to the stoppage.

A defensible estimate, as described in this breakdown of pricing one hour of unplanned downtime, includes:

Lost contribution margin on output you cannot recover later.
Recovery labor and overtime to make up the schedule.
Scrap and rework from interrupted runs.
Emergency parts and contractors.
Premium freight, inbound and outbound.
Restart waste, such as warm-up, changeover and first-article rejects.
Customer penalties or chargebacks for late or short shipments.

It also says what to leave out: fixed costs you would have paid anyway. Rent, salaried staff and depreciation do not rise because a line stopped, so charging them to the event inflates the number and weakens your case when you take it to a budget meeting.

The hidden costs people skip

The L2L survey found that 73% of respondents reported quality harm and 52% reported missed production or shipping targets. Those are costs that never show up on a maintenance work order. A missed ship date can cost you a chargeback now and a smaller share of that customer's orders next year. Put what you can measure in the model, and note the rest as exposure.

How to calculate manufacturing downtime cost, step by step

Here is the method, then a worked example. The figures in the example are illustrative, not benchmarks. Replace them with your own.

Find the bottleneck. Downtime only costs you output if the stopped asset limits the whole flow. If a non-bottleneck machine stops and there is buffer stock, the true loss may be small.
Calculate contribution margin per unit. Selling price minus variable cost per unit. Per the same costing guidance, the hourly loss starts with good units per hour at the bottleneck times that margin.
Add the per-event costs. Overtime, scrap, expedited freight, restart waste, contractor calls and penalties.
Count the events and the hours. Use maintenance logs, shift reports and your IT ticket history for a full year.
Multiply. Annual exposure is the approved hourly cost times annual unplanned hours, plus per-event restart or scrap costs times the number of events.

Worked example

Say a machining cell produces 120 good units per hour at the bottleneck. Each sells for $48 and has $31 in variable cost.

Contribution margin: $48 minus $31 is $17 per unit.
Hourly lost margin: 120 units times $17 is $2,040 per hour.
Per-event costs: $1,800 overtime, $600 scrap, $1,200 expedited freight and $400 restart waste is $4,000 per event.

A four-hour stoppage then costs 4 times $2,040 plus $4,000, or $12,160.

If the plant logs 40 unplanned hours and 15 events in a year, annual exposure is 40 times $2,040 ($81,600) plus 15 times $4,000 ($60,000), or $141,600. That is the number to set against a prevention budget.

For a more formal model, NIST publishes the Manufacturing Cost Guide, which includes options for machinery-maintenance costs, losses from inadequate maintenance and downtime and defects.

Measure recovery, not just the stop

The Aberdeen Group's four-step approach recommends counting annual downtime events and measuring how long recovery takes to reach 90% of capacity. The outage itself may last 30 minutes, but if the line needs two more hours to run at normal rate, that recovery time is part of the cost. Plants that stop the clock at "machine restarted" understate every event.

What causes unplanned downtime

NIST's survey ties unplanned downtime largely to breakdowns, and it links reactive maintenance with the most downtime and defects. The gap is large: the top quarter of establishments most reliant on reactive maintenance had 3.3 times more downtime than the bottom quarter.

Other patterns from the survey data:

In L2L's survey, 67% of respondents used a reactive maintenance approach, and 72% said undocumented fixes or "hidden factories" contributed to recurring downtime.
ABB found that 21% of respondents ran equipment to failure, while 45% used time-based preventive maintenance and 33% used condition-based predictive maintenance.

The undocumented-fix finding matters more than it looks. When a technician clears a fault and nobody records the cause, the same fault returns. Documentation is cheap, and it is the first step in every serious reduction effort.

The IT side of downtime

Most downtime studies focus on mechanical equipment. In a modern plant, though, a line can stop for reasons that never touch a motor or a bearing: a failed switch, an unpatched server, an ERP or scheduling system that will not open, a ransomware infection, a dead backup or a connected machine that lost its network path. We see these as downtime events like any other, and they belong in the same log and the same cost model.

We cover the connected-equipment side in more detail in what industrial IoT security actually requires.

How to reduce downtime in manufacturing

The evidence points in one direction: move away from fix-it-when-it-breaks.

NIST associated more advanced maintenance with less downtime. ABB's respondents reported results too: 92% said maintenance had increased uptime in the prior year, and 38% reported gains above 25%. Condition-based users reported a 42% increase in uptime, against 35% for time-based users.

But effort alone does not guarantee results. In the L2L survey, 93% of organizations were acting to improve uptime, yet only 46% reported measurable downtime reduction. The difference usually comes down to measurement and follow-through.

A practical sequence

Log every stoppage with a cause code and duration. Include IT and network causes, not just mechanical ones.
Rank causes by hours lost times hourly cost. Fix the top three first, not the most annoying.
Standardize the fixes. Write down what worked so the next shift does not rediscover it. Whether you use a spreadsheet or maintenance tracking software, the record matters more than the tool.
Shift from time-based to condition-based work on your costliest assets as data allows.
Test your recovery plan. A backup that has never been restored is an assumption. Time the restore against the cost per hour you calculated.
Treat the network and servers as production equipment. Monitor them around the clock, patch them on a schedule and give them a named owner.
Budget as an ROI decision. Aberdeen's framing is to quantify event frequency, recovery duration and total hourly exposure before choosing the prevention budget.

If you want to turn operating data into automatic alerts, shift reports or work-order triggers, that is where custom code and automation can pay for itself, since manual data entry is often why logs are incomplete.

Our perspective

Manufacturers tend to treat IT the way they used to treat maintenance: wait for the failure, then call someone. The numbers on the plant floor show how that ends. The same logic applies to servers, networks, backups and security.

We built Collett Systems around the opposite idea. IT is infrastructure, and infrastructure should be owned, monitored and documented before it breaks. That is why we deliver one standardized, fully loaded stack at a fixed cost per user, with 24/7 monitoring, proactive support and security management included. There are no tiers to climb and no surprise invoice when something goes wrong at 2 a.m. on second shift.

For a manufacturer, predictability is the point. If you can price an hour of downtime, you can price prevention, and you can hold your IT partner to defined service levels instead of hoping for a quick callback. We work with more than 150 local organizations across Southeastern Wisconsin, and manufacturers that cannot afford security or downtime problems are exactly who our approach is designed for.

Start with your number. Once you know what an hour costs, every IT decision gets easier to defend.

Dustin Collett

Put your downtime number to work

Once you have an hourly cost, you can see what an IT outage would do to your plant. We start every engagement with the IT & Security Assessment, which looks at your infrastructure, backups, security posture and recovery readiness so you know where production is exposed.

If you want a fast first read, the free IT Risk Score takes about 60 seconds. For the ongoing work, our Managed IT for Manufacturers page explains how we keep production systems running, and Managed IT Services covers the fixed per-user model. If you already have an internal IT person, co-managed IT adds our monitoring and depth alongside your team. We serve plants in West Bend, Milwaukee and the surrounding communities.

FAQ

What is the average cost of manufacturing downtime?

Surveys vary widely. ABB's global industrial survey found a median of $124,669 per hour, while Fluke's 2025 release reported an average of $400,000 per hour. Your own figure depends on margin, bottleneck output and customer penalties, so calculate it from your own data.

How do you calculate downtime cost in manufacturing?

Multiply good units per hour at the bottleneck by the contribution margin per unit. Then add per-event costs such as overtime, scrap, expedited freight, restart waste and penalties. Leave out fixed costs you would have paid regardless. Multiply by annual unplanned hours for your yearly exposure.

What causes most unplanned downtime?

NIST links unplanned downtime largely to breakdowns and associates reactive maintenance with the most downtime and defects. In its data, the most reactive plants had 3.3 times more downtime than the least reactive. Undocumented fixes make the problem recur.

How can a small manufacturer reduce downtime without a big budget?

Start by logging every stoppage with a cause and duration, then fix the costliest causes first and write down each fix. Move critical assets from run-to-failure toward preventive work. Include servers, networks and backups in the same plan, since they stop production too.

Does IT downtime count toward manufacturing downtime cost?

Yes. If a network, server, scheduling system or security incident stops a line or delays a shipment, it costs you the same margin, overtime and penalties as a mechanical failure. Log it with the same cause codes and include it in your annual estimate.

Manufacturing Downtime Cost: How to Calculate It and Cut It