A downtime chart becomes actionable only when event boundaries, reason ownership, production context, PLC and alarm evidence, human confirmation, root-cause method, and corrective-action verification are consistent. The largest Pareto bar is a prioritization signal, not proof of cause.
The short answer
Define a downtime event with consistent start, end, equipment scope and production context. Capture automatic facts separately from the operator’s reason selection, use a small governed hierarchy, and allow a provisional reason to be corrected with history. Prioritize by duration, frequency and operational consequence, then investigate repeated losses with evidence and verify the corrective action against a baseline over an agreed observation period.
- Separate detected symptom, selected reason, contributing conditions and verified root cause.
- Use stable equipment, product, shift, mode and event identities with trustworthy timestamps.
- Keep reason codes few enough to use consistently and detailed enough to assign action.
- Verify corrective action by recurrence, duration and process outcome—not by closure status alone.
Decision guide
| Record | Owner and timing | Use in analysis |
|---|---|---|
| Automatic event | Control or event system at occurrence | Start, end, equipment, state, alarms and signal context |
| Operator classification | Authorized production user near the event | Observed reason, comments, material or operating context |
| Investigation | Cross-functional owner after triage | Evidence, causal chain, contributing factors and confidence |
| Corrective action | Named action owner through verification | Change, due date, risk, test, result and recurrence monitoring |
A practical workflow
- 01
Agree event boundaries, planned/unplanned rules, overlapping-event logic, ownership, time source and reason hierarchy.
- 02
Collect events and context; expose missing, unknown, microstop and manually edited periods instead of hiding them.
- 03
Validate the Pareto by duration, frequency, equipment, product, shift and mode; sample source evidence before prioritizing.
- 04
Investigate selected losses with a suitable causal method and distinguish containment from root-cause correction.
- 05
Assign actions, control changes, verify results over a defined window and update standards or reason codes when learning changes.
Evidence and acceptance
Retain event definitions, reason-code dictionary and versions, time quality, source mappings, operator changes, alarm and PLC extracts, production context, Pareto filters, investigation notes, hypotheses, tests, root-cause approval, containment, corrective actions, controlled revisions and post-change verification.
Common mistakes
- Calling the first alarm or largest Pareto category the root cause.
- Using hundreds of overlapping reason codes or one “other” code for most events.
- Overwriting provisional classifications without audit history.
- Mixing planned stops, starved/blocked states and equipment faults without explicit rules.
- Closing an action immediately after a change without measuring recurrence.
Engineering and security boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
How many downtime reason codes should we use?
Use the smallest governed hierarchy that directs accountable action. Review unknown and rarely used categories before adding detail.
Is the first PLC alarm the root cause?
Usually it is evidence of a symptom or sequence consequence. Confirm the causal chain with context and controlled tests.
Should operators edit automatic events?
Preserve automatic facts and allow authorized classification or correction as a separate audited layer.
Does AutoNexit calculate OEE from live signals?
No. It organizes exported evidence, decisions, changes and verification around the investigation.