Downtime cost calculator: how to put a real number on lost production
Just a 22-minute read
Most plants can tell you a machine was down for six hours. Few can tell you what that actually cost, beyond a shrug and a round number.
This article breaks down the formula behind ManWinWin’s downtime cost calculator, now live under maintenance tools, and shows the research each coefficient is checked against.
Introduction
Ask ten maintenance managers what an hour of downtime costs their line and you’ll get ten different answers, most of them guesses. That’s not a knock on the people asking. Downtime cost is genuinely hard to pin down because it hides across departments: production tracks lost units, finance tracks margin, HR tracks overtime, and nobody owns the total. Fewer than a quarter of manufacturers track this figure with any precision, which means most CMMS and reliability investment decisions get made without the one number that should drive them.
A calculator only earns its keep if the formula behind it is honest about what it includes and what it leaves out. Direct production loss is the easy part. The number that actually moves a budget conversation is the fully loaded figure, the one that adds idle labor, wasted material, and contractual exposure on top of lost output. Below is the structure ManWinWin’s calculator uses, the reasoning behind each input, and the published research it’s checked against so you’re not working from a vendor’s optimistic assumption.
1. The downtime cost formula, input by input
A usable downtime cost figure needs four inputs, and most plants already have three of them somewhere in production or finance records.
- Lost production value per hour — units not produced during the stoppage, multiplied by contribution margin per unit, not sale price. Using sale price overstates the loss because it ignores materials you didn’t consume.
- Idle labor cost — headcount on the affected line multiplied by fully loaded hourly cost, for every minute they’re paid but not producing. This applies whether they’re reassigned or standing around, since payroll doesn’t pause either way.
- Secondary costs — scrapped work in progress, expedited freight to recover schedule, overtime to make up lost units, and contractual penalties for late delivery. This category is where most back of envelope estimates fall apart, because it’s the one nobody remembers to add until the invoice arrives.
- Downtime duration — measured from stoppage to full production rate, not to the moment the machine restarts. A line running at 60% output for the first twenty minutes after repair is still losing money, just less visibly.
The output is a cost per hour, applied against your logged unplanned downtime hours for the period you’re analyzing. Multiply carefully here. A single dramatic outage skews an annual average, so most reliability teams run this at the line level, monthly, rather than as one blended plant-wide figure.
Where this gets interesting is the gap between what plants think downtime costs and what it actually costs once secondary costs are included. Independent research on unplanned downtime puts average manufacturing downtime cost at roughly $260,000 per hour across all sectors, though the range runs from under $10,000 for light assembly to well over $2 million for automotive and semiconductor lines. The Siemens True Cost of Downtime 2024 report found unplanned downtime now costs the world’s 500 largest manufacturers a combined $1.4 trillion a year, equivalent to 11% of total revenue, up from 8% five years earlier. That jump wasn’t caused by more downtime hours. Reported incidents actually fell. Costs rose because each hour of downtime now carries more secondary cost than it used to, which is exactly the part a rough estimate misses.
Downtime cost Calculator
Calculate the true cost of downtime and see how much you could save by reducing equipment failures.
ManWinWin Software is the result of 40+ years of experience and know-how
With thousands of users in 120+ countries in the World. Created by Portuguese Engineers has been improved with implementations, and listening to thousands of clients worldwide using the system.
Get a personalized demo of ManWinWin CMMS
Please fill out the form and wait for one of our specialists to contact you to schedule a date at your convenience.
- Discover how ManWinWin solves your specific challenges.
- See ManWinWin’s core features, tailored to your needs.
- Gain best practices from the world’s most experienced CMMS company, specific for your success.
- Discover your ideal ManWinWin license, investment, and timing of implementation.
2. What most estimates leave out, and why the calculator doesn’t
A number built only from lost output looks conservative and defensible right up until finance compares it against the actual invoice trail from the last major stoppage. Here’s what closes that gap.
1. Idle and reassigned labor
Technicians and operators standing around a stopped line, or shifted to low-value tasks, are still on the clock. This cost is easy to overlook because nobody files a report for “did nothing productive for ninety minutes,” but the payroll cost is identical to if they’d been working. A downtime cost calculator should count this hour for hour, not just for the maintenance crew responding to the fault.
2. Scrap and quality loss
Machines that fail mid-cycle often leave work in progress unsalvageable, and restarts frequently produce out-of-spec units until the process stabilizes. This is a materials cost, not a maintenance cost, but it belongs in the total because it’s a direct consequence of the stoppage.
3. Expedited recovery costs
Rush freight to make a delivery window, overtime to claw back lost units, and subcontracted capacity to cover a shortfall are all costs that only exist because production stopped unexpectedly. They’re invisible on the maintenance ledger and show up weeks later in a completely different budget line, which is precisely why they get missed.
4. Contractual and customer impact
Late delivery penalties, expedited shipping clauses, and the quieter cost of a customer who starts dual-sourcing after a missed order are real, though harder to quantify per incident. Where contracts specify penalties, include the actual figure. Where the impact is reputational, note it as a qualitative flag rather than forcing a number that won’t survive scrutiny.
References
Downtime cost figures in this article draw on named industry research rather than round-number estimates. Average unplanned downtime cost across manufacturing sectors is estimated at $260,000 per hour, per Aberdeen Group benchmarking, with wide variance by industry and asset criticality. Fortune Global 500 companies lose a combined $1.4 trillion annually to unplanned downtime, equivalent to 11% of total revenue, up from 8% ($864 billion) five years earlier, according to Siemens’ True Cost of Downtime 2024 report. Fewer than 25% of manufacturers track downtime cost with precision, a gap that limits how well reliability investment can be prioritized.
Aberdeen Group. Unplanned downtime cost benchmarking (average $260,000 per hour across manufacturing sectors). aberdeen.com
Siemens. True Cost of Downtime 2024 (Fortune Global 500 companies lose $1.4 trillion/year, 11% of revenue, up from 8% in 2019–2020). press.siemens.com
- Aberdeen link — I linked to aberdeen.com generally rather than a specific report page. I wasn’t able to locate the original Aberdeen study URL directly (most citations I found were secondary sources quoting it, e.g., eWorkOrders, ReliaMag). The $260K figure is consistently attributed to Aberdeen across multiple independent sources, but if you want a fully primary citation here, it may need a direct Aberdeen report link from your own files/subscriptions, or I can swap it for a secondary source that does link cleanly.
- “Fewer than 25% track downtime cost precisely” — this stat appeared in vendor blog content (OxMaint), not a named research house, so I’d treat it as a soft claim rather than one to cite formally. I left it unlinked in the article itself for that reason; want me to remove it entirely, or keep it as an uncited observation?
3. Frequently asked questions
Everything you need to know before running the numbers
dummy
1. How accurate does my downtime cost figure need to be?
Accurate enough to prioritize decisions, not accurate to the dollar. A number within 20% of reality, built from real production and labor data, is far more useful than a precise-looking figure built on assumptions. Use it to rank which lines or failure modes deserve attention first.
2. Should I use sale price or margin when calculating lost production value?
Margin, not sale price. Sale price counts revenue you’d have earned on materials you never consumed, which overstates the loss. Contribution margin per unit reflects what the stoppage actually cost you.
3. Do I need separate downtime cost figures for each production line?
Yes, if the lines differ meaningfully in output value, staffing, or criticality. A single blended plant-wide number will mask which specific line or asset justifies priority maintenance investment, the same issue that shows up when modeling CMMS ROI across a multi-site organization.
4. How do I account for downtime that doesn't stop the whole line?
Calculate it as a percentage of full output value. A bottleneck station running at 50% capacity for two hours isn’t free just because the line kept moving, it’s losing half the value of two hours of full production.
5. What's the difference between downtime cost and MTTR?
Downtime cost is a monetary figure. Mean time to repair (MTTR) is a duration metric, tracked separately in a CMMS, that measures how fast you recover. They’re related but not interchangeable, MTTR tells you how long the clock ran, downtime cost tells you what each minute on that clock was worth.
6. Does reducing downtime hours automatically reduce downtime cost proportionally?
Not always. If secondary costs like expedited freight or contractual penalties are concentrated in the first hour of any stoppage, cutting a six-hour outage to four hours saves less than the hourly rate suggests. Track both duration and cost per incident, not just the average, to see where the real leverage is.
Discover ManWinWin services in maintenance management consulting
Implementation
The implementation consultancy is the component that turns a good software into a good solution.
Training
Training is the component that consolidates and sustains the solution on the client.
Conclusion: what the numbers tell you to do next
A downtime cost figure only earns its place in a maintenance budget conversation when it’s built from measurable inputs, checked against published research rather than optimistic assumptions, and broken down by line rather than blended into a single plant-wide average.
Lost production value, idle labor, and the secondary costs that show up weeks later are the three components every maintenance manager should quantify before the next capital request, and every one of them is a figure your team should already be tracking inside a structured maintenance management system rather than reconstructing after the fact.
ManWinWinis a globally proven CMMS platform positioned between lightweight SaaS tools and heavy enterprise EAM suites, offering structured, scalable, and practical maintenance management for industrial and multi-site organizations worldwide.
For a deeper look at how downtime reduction feeds directly into a CMMS business case, see the maintenance software ROI calculator methodology, or check whether predictive maintenance is the right next step for your operation. The downtime cost calculator itself is available under ManWinWin’s maintenance tools.
ManWinWin Software – Maintenance Tools
Maintenance Software ROI Calculator
Estimate the return on investment of implementing a CMMS across your operation
About the Author
José Fernandes is the Managing Partner at ManWinWin Software (Navaltik Management), leading company in maintenance management consultancy and CMMS (Computerized Maintenance Management System) solutions.
With a technical background in industrial organization, José Fernandes has been with Navaltik since the 1990s, progressing from consultant to strategic leader and a key figure in the development of the ManWinWin software.
Throughout his career, he has overseen hundreds of maintenance system implementations across more than 30 countries, including regions in Africa, Australia, the Middle East, and East Asia.
