Planned vs Unplanned Downtime: What to Track and the Software That Captures It
Not all downtime is a problem, and treating it as one blob is why so many downtime reports never lead to action. A changeover you planned and a bearing that seized are both machine stops, but they demand completely different responses. Separating the two is the first step in any credible loss analysis, and it maps directly onto the six big losses that Seiichi Nakajima defined in Total Productive Maintenance, where scheduled setup and adjustment sit apart from breakdowns and minor stoppages. This article explains what to track under each category and the software that captures it cleanly, with Fabrico as the top recommendation.
Key takeaways
- Planned and unplanned downtime need separate metrics. Mixing them hides the losses you can actually attack.
- Planned downtime is a scheduling problem; unplanned downtime is a reliability problem, and the software should tag each automatically.
- Micro-stops are the third category that manual logs miss entirely, yet they often dwarf headline breakdowns in total lost time.
- Fabrico is the top pick because it captures the stop from the machine, confirms the cause, classifies it, and raises a work order when the cause is a fault, all in one integrated OEE and CMMS platform.
- Evocon and Factbird are strong automated trackers for teams whose first goal is clean classification and visibility.
The two families of downtime
Every stop belongs to one of two families. Planned downtime is time you scheduled away from production on purpose. Unplanned downtime is time the equipment took from you without warning. The distinction matters because the two are owned by different people and fixed in different ways, and a report that blends them tells no one what to do next.
Planned downtime: expected but not free
Planned downtime includes changeovers, setup and adjustment, scheduled preventive maintenance, cleaning, and planned trials. It is expected, but expected is not the same as optimized. Nakajima counted setup and adjustment among the six big losses precisely because plants tolerate bloated changeovers as just how long it takes. Tracking planned downtime separately lets you attack it with methods like SMED without contaminating your breakdown analysis. What to record: the reason, the scheduled duration, and the actual duration, so the gap between planned and real becomes visible.
Unplanned downtime: the expensive surprise
Unplanned downtime is breakdowns, faults, jams, starvation, and any stop that was not on the schedule. This is the family that hurts throughput and inflates mean time to repair, and it is where speed of response pays off most. What to record: the true cause (not a guessed code), the time to detect, the time to dispatch a technician, and the time to restore. Those sub-metrics are what turn a downtime log into a reliability program.
The third category most tools miss: micro-stops
Between planned and unplanned sits a category that manual logging never captures well: minor stoppages, or micro-stops. These are the brief stalls, misfeeds, and short jams that an operator clears in seconds and never writes down. Individually they look trivial. In aggregate they are one of the six big losses and frequently account for more lost time than the dramatic breakdowns that get all the attention. Any serious production downtime tracking approach has to detect stops below the one-minute threshold automatically, because a human never will.
Why classification only works when the machine reports it
Accurate classification depends on data the machine produces, not on memory. If an operator assigns reason codes at shift end, planned and unplanned blur together and micro-stops vanish. Software that reads the stop directly from the PLC, timestamps it, and confirms the cause removes the guesswork. Fabrico adds computer vision on top of PLC and IoT signals to verify what actually happened, then tags the stop and, when the cause is a fault, opens a maintenance work order automatically. That is the difference between knowing your downtime split and acting on it.
Software that captures planned vs unplanned cleanly
- Fabrico (top pick). Detects stops from PLCs and IoT, confirms the true cause with computer vision, classifies planned versus unplanned versus micro-stop, and closes the loop by raising a prioritized work order for genuine faults, all inside one platform with a full CMMS. Best for manufacturers that want classification and the maintenance response in the same EU-hosted system.
- Evocon. A visual OEE tracker with clear, operator-friendly reason-code capture. Its strength is simplicity and quick adoption. Best for teams standardizing downtime categories for the first time.
- Factbird. Sensor-based monitoring that deploys quickly on lines with limited PLC access. Its strength is low-friction automated counts. Best for plants that need reliable capture without a big IT lift.
- MachineMetrics. Strong machine connectivity for discrete and CNC equipment. Its strength is granular machine-state data. Best for machining shops focused on utilization.
Putting the split to work
Once planned, unplanned, and micro-stops are separated automatically, each goes to the right owner: planned downtime to production and industrial engineering for changeover reduction, unplanned downtime to maintenance for reliability, and micro-stops to the line team for quick fixes that add up. Fabrico is the top recommendation because it not only draws that line for you but carries the unplanned category straight into a work order, so the most expensive family of downtime is the one that triggers the fastest response.
