A machine stops at 10:15 AM. The operator waits for the supervisor. The supervisor checks the controller, calls maintenance. Maintenance arrives at 10:31. The fix takes 6 minutes. The machine restarts at 10:47.
Total stoppage: 32 minutes. Nobody wrote it down as 32 minutes — it got logged as “about 20 minutes” at shift end, if it got logged at all.
This is how unplanned downtime quietly disappears from your records — and from your understanding of what’s actually happening on the floor.
Here’s how to calculate it properly, and a calculator that does it for you.
- Unplanned downtime is any unscheduled stoppage — breakdowns, material shortages, power outages, quality holds
- Downtime in minutes = Stop Time − Start Time, summed across every stoppage in the period
- Planned downtime (changeovers, breaks, PM) is excluded from availability — unplanned downtime directly reduces it
- Manual logs miss small stoppages under 5 minutes — real unplanned downtime is usually higher than what’s reported
- An outage calculator converts raw stop/start times into total minutes, downtime %, and availability instantly
What you’ll learn:
What is unplanned downtime?
Unplanned downtime is any period when a machine stops producing due to an event that wasn’t scheduled in advance. A bearing fails. A sensor jams. The power trips. A part comes out of tolerance and the line halts for inspection. None of these were on the production plan — they happened, and they cost time.
It’s the opposite of planned downtime — changeovers, scheduled maintenance, tool changes, shift breaks — all of which are accounted for before the shift even starts. Unplanned downtime is the disruptive one. It’s why a shift that should have produced 240 parts ends with 190.
Why it matters more than planned downtime:
Planned downtime is built into your schedule — you account for it and plan around it. Unplanned downtime is the variable that breaks your plan. It’s unpredictable, it cascades into delivery delays, and it’s the loss category every OEE and production report needs to track precisely.
Planned vs unplanned downtime
- Changeovers and tool changes
- Scheduled preventive maintenance
- Shift breaks and lunch
- Planned line stoppage for inspection
- Machine breakdowns and failures
- Material shortages or supply delays
- Power fluctuations or outages
- Quality holds and unplanned inspection stops
How to calculate downtime in minutes
The core calculation is simple — but doing it consistently, across every stoppage in a shift, is where most manual systems break down.
10:47 − 10:15 = 32 minutes of unplanned downtime for that event
Availability = (Planned Time − Total Downtime) ÷ Planned Time
Worked example — a full shift
| Stop Time | Resume Time | Duration | Reason |
|---|---|---|---|
| 08:42 | 08:49 | 7 min | Tool change — unplanned wear |
| 10:15 | 10:47 | 32 min | Coolant pump fault |
| 11:58 | 12:03 | 5 min | Small stop — sensor reset |
| 13:20 | 13:24 | 4 min | Small stop — chip jam |
| 14:50 | 15:12 | 22 min | Material shortage — waiting for stock |
70min
across an 8-hour (480 min) planned shift
of planned production time lost to unplanned stoppages
(480 − 70) ÷ 480 — the Availability input for OEE
5 minutes and 4 minutes. These are exactly the kind of stoppages that vanish from manual end-of-shift logs. If this operator filled in a paper form at 6 PM, those two events — 9 minutes combined — would almost certainly be forgotten, understating real downtime by over 12%.
Common causes of unplanned downtime
| Low Hanging Fruit | High Effort, High Impact |
|---|---|
|
|
How much unplanned downtime is normal?
World-class manufacturers target unplanned downtime below 5–10% of planned production time. Most Indian SME factories, when they measure it accurately for the first time using real-time data instead of manual logs, discover it’s actually in the 15–30% range.
A factory that believes it has 8% downtime based on shift reports often has 18–22% in reality. The difference isn’t that the floor got worse — it’s that small stops and underreported durations were never being captured in the first place.
How to reduce unplanned downtime
1. Measure it accurately first
You can’t fix what you’re not capturing. Replace manual shift logs with a system that records every stoppage automatically — including the small ones under 5 minutes.
2. Run a Pareto of downtime reasons
Rank every cause by total minutes lost, not just frequency. Usually 2-3 reasons account for the majority of your total downtime — that’s where to focus first.
3. Do root cause analysis on repeat failures
If the same machine breaks down for the same reason more than twice, a 5 Why analysis usually reveals a fixable systemic issue — not bad luck.
4. Shift from breakdown to preventive maintenance
Most unplanned downtime is actually predictable downtime that wasn’t prevented. Track MTBF per machine and adjust PM intervals before failures recur.
5. Alert teams the moment a stoppage happens
Real-time alerts cut response time from minutes to seconds. The faster someone responds, the shorter the downtime event — and the more output you recover.
Unplanned downtime — captured automatically, every shift
Leanworx connects to your machines and logs every stoppage — including the small ones manual logs always miss — with timestamp, duration, and reason code.
Every stoppage captured to the second
No manual entry, no rounding, no forgotten small stops. Downtime in minutes is always exact — calculated automatically from machine signals.
Instant real-time alerts on stoppage
The moment a machine stops, supervisors get notified. Response time drops from minutes to seconds — directly shortening every downtime event.
Downtime Pareto — built in
Every reason ranked by total minutes lost automatically. Know your top downtime causes without a manual spreadsheet.
Works with existing machines
CNC, VMC, lathe, press — connects to any machine, any age. Deployed in days, capturing real downtime data from day one.
Try Leanworx for Free.
For 1 Machine
Get live reports, real-time dashboards, mobile alerts, and full production visibility exactly like our paid customers.
