What it means
A factory can lose hours for many reasons. If all downtime is classified as "machine failure," maintenance may be blamed for material shortages or schedule changes it cannot control, and if every stop is "planned," the business may hide unreliable equipment.
A clear coding scheme separates causes while allowing a temporary unknown category until investigation is complete. Define when downtime starts and ends, whether a short pause is counted and what the equipment was scheduled to do.
A machine idle because there was no customer order is not necessarily downtime under a production plan. Record asset ID, time, duration, affected output and person reporting, and use the same definition across sites if results are compared, since a code without accurate timestamps cannot show the true effect.
Keep the code list practical, because too few categories hide the cause and too many lead to inconsistent choices. Provide examples and decision rules for overlapping events.
A line may stop because a part failed after poor lubrication, so the immediate cause and root cause can be recorded separately, with operators entering the best current fact quickly and a supervisor refining it after diagnosis without erasing the original entry. Use evidence: maintenance work orders, sensor logs, quality records and material-delivery notes can support classification, and a machine alarm may show what happened but not why.
Do not assume an operator caused a stop because they were present. In safety incidents, follow the required investigation and reporting process rather than relying on a simple downtime code.
Analyse frequency and duration, because ten short setup delays may cost more than one long outage if they repeatedly disrupt a bottleneck. A high share of "unknown" means the process needs better training or diagnostics.
Compare causes with preventive-maintenance plans, supplier performance and staffing, then assign corrective actions with owners and dates and see whether the pattern changes. Beware incentives: if a maintenance team is judged only on mechanical downtime, it may push ambiguous cases into "operations," and a production team may do the opposite.
Review samples across functions and reward accurate reporting, since the purpose is to improve throughput and reliability, not to win an argument about which department owns a red bar. For owners, cause codes turn lost time into a decision about whether to repair equipment, adjust material supply, change setup methods or revise the schedule.
In practice
Real-world examples.
Example
A packaging line stops for 40 minutes because film is unavailable; the code points to material supply rather than machine failure. Purchasing sees the pattern and adjusts reorder points, instead of maintenance being sent to inspect a healthy machine.
Example
An operator records a motor fault, and maintenance later links repeated faults to a bearing issue with a corrective plan. The original entry stays on file, and the refined root cause is added beside it. After the repair, the team watches whether motor stops fall.
Example
A planned cleaning window is coded separately from an unexpected breakdown so availability is interpreted honestly. A food plant can then show auditors that cleaning is scheduled, while the breakdown data points to genuine reliability work.
Formula
Calculation
Cause share of downtime = Minutes assigned to a cause code / Total recorded downtime minutes x 100
Worked example. An invented plant records 600 downtime minutes in a week, split by cause code: 180 minutes of missing materials, 150 of mechanical failure, 120 of setup and changeover, 90 of planned cleaning and 60 still marked unknown (180 + 150 + 120 + 90 + 60 = 600).
- Material-supply share = 180 / 600 x 100 = 30%.
- Mechanical share = 150 / 600 x 100 = 25%, setup share = 120 / 600 x 100 = 20%, planned cleaning share = 90 / 600 x 100 = 15% and unknown share = 60 / 600 x 100 = 10%.
- Managers check the underlying stops and their effect on output before choosing a remedy; the 10% unknown share also tells them the coding discipline needs attention.
The percentage depends on consistent definitions of scheduled time and downtime.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Willow Pack, an invented packaging producer. Its weekly report said a filling machine caused eight hours of downtime. Maintenance replaced several components, but the next week the number barely changed. Operators explained that the line also waited for labels and frequently stopped during product changeovers.
Willow separated immediate causes in its log and linked material waits to warehouse records. It found three hours of true mechanical failure, two hours of label shortages and several short setup delays. Maintenance addressed the failing component, purchasing changed label replenishment and production tested a quicker changeover sequence. The total lost time fell because each cause had a suitable owner.
The owner also asked supervisors to sample coded events, keeping the data honest rather than shifting blame between teams. Within a couple of months the unknown share of coded stops had dropped, because operators saw that accurate entries led to action rather than blame. Weekly meetings moved from arguing about whose fault a stop was to choosing the next corrective action.
Watch out
Common mistakes.
- Using one generic "breakdown" code for every reason a line is not running.
- Changing codes to meet a department target without preserving original evidence.
- Counting idle time with no planned work as a breakdown without defining the metric.
Questions
People also ask.
Can one stop have more than one cause?
Yes. Record the immediate reason and contributing or root causes separately where the system allows it.
Should unknown be an available code?
It can be useful temporarily, but old unknowns need review rather than becoming a permanent dumping ground.
How should the codes be used?
Compare time and recurrence, verify samples, assign corrective action and check whether lost output falls.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%