The Real Cost of Factory Downtime (and How to Measure It)

Downtime costs far more than the stopped machine. Measure it per hour as: lost good units × contribution margin, plus idle labour, plus overhead that keeps burning. A mid-size Indian line losing 120 parts/hour at ₹85 margin, with 6 idle operators, bleeds roughly ₹12,000 (~US$125) every downtime hour — and most of it never reaches a report.

Formula: downtime cost per hour = (lost good units/hour × margin per unit) + idle labour per hour + overhead per hour.

Key takeaways

• Bill lost parts at contribution margin (price minus variable cost), not full sale price — the popular online calculators use full price and overstate your loss.
• The true number depends on one fork almost no calculator asks: can you catch up? Sold out → every lost hour is full margin, gone for good. Can recover on overtime → it costs only the overtime premium plus overhead.
• One CNC cell losing 10% of runtime can cost ~₹62 lakh a year (~US$65k) — a seven-figure line item that never appears as one.
• In a cheap-labour Indian plant the expensive part of a stop is unsold margin, ~14× the idle labour — which is exactly why owners under-count downtime.
• Micro-stops and slow running are the biggest, least-logged bucket. World-class OEE is ~85% (Nakajima/TPM); plants that have just started measuring often sit at 40–60%.

The formula, and the fork every calculator skips

When a line stops, most owners picture the repair bill. That is the cheapest part. The real loss has three parts running at once:

1. Lost output you can't sell — every good part not made is margin gone.
2. Idle labour — operators are paid whether the line runs or not.
3. Overhead that doesn't pause — rent, depreciation, supervision, baseline power and interest keep accruing while nothing ships.

But before you multiply anything, answer one question the online calculators (Tractian, scw.ai, arda and the rest) all skip — and it can swing the real number 5–10×:

Can you catch up? - You're turning away orders / this is your bottleneck → the parts are gone for good. Full contribution margin, permanently. This is the formula in full. - You can recover next week on overtime or a spare shift → the parts get made later. The real cost is the overtime premium plus overhead, not full margin. - The stopped machine is a non-bottleneck that never starves the constraint → it may cost close to ₹0 (Theory of Constraints, Goldratt).

Every consensus calculator quietly assumes case one — sold out, every lost part permanently lost. That's why they read high. Decide which case you're in before you trust a number, including ours below.

Why most downtime calculators overstate your loss

Two rules keep the number honest:

• Use contribution margin, not price. You never bought the material for a part you never made, so subtract variable cost (material, consumables, per-unit power) from the sale price. The calculators that bill "lost revenue" at full value double-count — you didn't spend the input either.
• Overhead is mostly sunk. Rent and depreciation burn identically whether this hour runs or stops, so eliminating the stop doesn't put that cash back in your pocket. Split the number into cash you actually lose (lost margin + any overtime) versus capacity value burned (allocated overhead). Overhead only becomes a real loss when the stop reduces what you can sell — i.e. when you're capacity-constrained. Same root as the fork above.

A worked ₹ example (auto-components CNC line)

A mid-size auto-components plant running a CNC machining cell, selling everything it makes (bottleneck case — full margin applies). Figures are indicative July 2026 estimates — plug in your own.

One hour of downtime:

• Lost margin: 120 × ₹85 = ₹10,200
• Idle labour: 6 × ₹120 = ₹720
• Overhead still burning: ₹1,500
• Total ≈ ₹12,420 (~US$130) per downtime hour

Look at the split before you move on. The idle labour everyone watches — the paid operators standing around — is ₹720. The unsold margin is ₹10,200, about 14× bigger. This is the trap in Indian plants: "labour is cheap, so a stop isn't costly." The cheap labour is precisely why the stop gets waved off — and the expensive part, the margin, is the part nobody is looking at.

Now annualise. Two shifts, 26 days/month (~416 planned hours/month), losing 10% to downtime — breakdowns, changeover overruns, material waits and micro-stops. That's ~42 lost hours/month:

• 42 × ₹12,420 ≈ ₹5.2 lakh/month ≈ ₹62 lakh/year (~US$65k) — on one cell.

Even if your real figures are half of this, the point holds: downtime is a seven-figure annual line item that rarely appears as one. And on this cell each recovered point of availability is worth about ₹6 lakh a year (₹62 lakh ÷ ~10 points) — a clean way to price any fix.

¹ India's Annual Survey of Industries put the average factory daily wage at about ₹563 in 2021–22 (CEDA, Ashoka University, on ASI data); load it up for statutory contributions and overhead. MoSPI has since released ASI 2022–23, showing average emolument of ₹3.46 lakh/person, up 6.3% (MoSPI, ASI 2022–23). Use your own payroll where you have it.

Costs the hourly formula doesn't capture — but that can dwarf it

For a Tier-1/Tier-2 auto-components supplier, the on-floor loss above is often the smaller number:

• OEM line-stop penalties. A stop that starves your customer's assembly line can trigger a late-delivery or line-stop charge that dwarfs your own lost margin — a real, feared figure in Indian auto supply.
• Premium freight to recover the schedule (air/express instead of road).
• Scrap and rework at restart — the parts sitting in the machine when it stopped, plus warm-up rejects.
• Repair/maintenance spend on the breakdown itself.

None of these show up in "units × margin." Add them when the stop touches a customer commitment.

How this ties to OEE

OEE (Overall Equipment Effectiveness) expresses these losses as one percentage:

OEE = Availability × Performance × Quality (OEE.com)

• Availability — the line stopped (breakdowns, changeovers, no material).
• Performance — the line runs slow or micro-stops (up, but below rate).
• Quality — good parts vs. total (scrap and rework).

The world-class benchmark is ~85%, set by Seiichi Nakajima, the originator of TPM — roughly 90% availability × 95% performance × 99.9% quality (Lean Production). Almost nobody hits it. Plants that have just started measuring usually land at 40–60%, climbing toward 60–75% as they mature — a rule of thumb, not a promise, so measure your own. The gap between your OEE and 85% is your downtime cost as a ratio.

Why most downtime stays hidden

Manual logs capture the loud, obvious stops — a breakdown someone had to call maintenance for. They miss the losses that quietly eat the most. These are TPM's Six Big Losses; here's where they hide:

Micro-stops and speed losses are usually the biggest bucket — and the least recorded. Do the arithmetic: a 40-second stall a hundred times a shift is ~67 minutes of lost runtime that no one logs. That's how a plant swears it has "a couple of breakdowns a month" and still runs at 55% OEE. Nobody counts these hours, so nobody costs them. You can't cost what you never counted.

Surfacing the hidden hours — read the cameras you already own

A person can't stand at every cell with a stopwatch. A camera can watch one continuously — an unmanned station, a cell idle while an operator hunts for a trolley, a changeover that ran 40 minutes instead of 15, a machine cycling below rate. Those are the Availability and Performance losses manual logs drop, each carrying the ₹/hour tag from the formula.

Here's the part the CCTV vendors won't tell you: most plants already bought cameras for theft and security. That's a sunk asset you can re-read for downtime with no new capital — you don't need a new analytics system, you need to read the one you already paid for.

On a woodworking line we monitor, a single power outage idled the cell for 110 minutes in one afternoon — logged nowhere as a costed event, invisible in every report the owner saw. That is the norm, not the exception.

This is the wedge Mama is built around: record a short phone walkthrough of the floor, and it returns a camera placement plan (how many, where, ceiling vs wall) for the zones where downtime actually accrues, then reads those feeds into a plain-language efficiency summary. The idle 40-minute changeover stops being invisible and starts carrying its ₹/hour tag.

Do this on Monday: a 4-step downtime-cost checklist

1. Pick your worst cell or line. Get its ideal output/hour and contribution margin/unit.
2. Decide the fork — sold out (full margin) or can catch up (overtime premium).
3. Compute its cost per downtime hour with the formula.
4. For two weeks, capture all stops — micro-stops and slow running, not just breakdowns — then multiply. That annualised figure is your business case.

The measurement is cheap. Not measuring is the expensive part.

FAQ

How do you calculate the cost of downtime in a factory? Per hour: lost good units × contribution margin per unit, plus idle labour, plus overhead that keeps running. Use contribution margin (price minus variable cost), not full price, or you'll overstate the loss. Then check whether you can catch up — if you can, the real cost is the overtime premium, not full margin.

What's the difference between downtime cost and OEE? OEE expresses losses as a percentage (Availability × Performance × Quality); downtime cost expresses the same losses in rupees. OEE tells you how much capability you're losing; the ₹/hour formula tells you what it's worth. On a sold-out cell, each recovered point of availability can be worth around ₹6 lakh/year.

What is a good OEE score for an Indian factory? Around 85% is world-class (Nakajima's TPM benchmark), and 40–60% is typical for plants that have just started measuring. For a mid-size Indian plant, a trustworthy 55% you actually track beats a guessed 80% — you can't improve what you don't yet count.

Why is so much downtime "hidden"? Manual logs catch loud breakdowns but miss micro-stops, slow running, changeover overruns and material waits — often the biggest bucket. A 40-second stall a hundred times a shift is over an hour lost, and no machine visibly "fails," so nothing gets recorded even though it costs money every shift.

How do cameras help measure downtime? Video can be read continuously across every cell, catching idle stations, slow cycles and over-long changeovers no one has time to log by hand. Those are Availability and Performance losses; tagging each with its ₹/hour cost turns a blind spot into a quantified line item — and if you already have security cameras, it needs no new hardware.