Downtime Tracking: From Operator Excuses to Root-Cause Pareto

If your downtime tracking system has three categories and the third is "Other", you do not have downtime tracking. You have downtime logging. Logging tells you that the machine stopped. Tracking tells you why it stopped, who could have prevented it, and what to do next time.

The Three-Level Taxonomy

The structure we standardise on:

• Level 1 (6 categories): Mechanical, Electrical / Instrumentation, Material, Quality, Planned, Organisational.
• Level 2 (~30 subcategories): e.g. Mechanical → Bearing, Drive, Hydraulic, Pneumatic, Conveyor.
• Level 3 (~120 specific reasons): e.g. Bearing → Outboard motor bearing failure on Line 3 conveyor.

Auto-Detect + Operator Tagging

The PLC tells you that the line stopped. The operator tells you why. The system must do both:

1. Auto-detect the stop within 30 seconds (idle time, no parts produced, energy drop).
2. Prompt the operator on the workstation tablet with the Level-1 picker.
3. Drill into Level 2 and Level 3 with auto-suggested common reasons for that machine.
4. Allow a free-text "exception" field that goes into the weekly review for taxonomy refinement.
5. Hard-escalate after 5 minutes of uncategorised state.

The Pareto That Actually Drives Capex

A real downtime Pareto, refreshed weekly, is the most undervalued maintenance management tool in Indian manufacturing. Once the taxonomy is clean for 90 days, the top 10 reasons typically account for 70 – 80% of total downtime hours — and these are exactly the items that justify capex requests, retrofit projects and supplier escalations.

The Weekly Review Loop

Downtime data without a review loop is theatre. The cadence we install:

• Daily 15-minute shift handover with the top 3 downtime reasons of the shift.
• Weekly 60-minute downtime review chaired by the maintenance head.
• Monthly 90-minute cross-functional review with production, quality, and engineering.
• Quarterly capex sign-off prioritised by downtime Pareto — not by opinion.