Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and scope
Downtime categories should support investigation and improvement. Separate the observed reason, confirmed cause and free-text note. Keep a small number of distinguishable categories with definitions and examples. A very long list encourages rushed choices, while one generic category used for everything obscures who should investigate the incident.
Illustrative example
Illustrative example: a machine stops because a component is missing. The operator records a material wait, although purchasing later confirms a reservation error. Preserve the observed event and add the investigated cause. Do not overwrite the observation so the record falsely suggests the cause was known immediately.
Acceptance check
Test changed causes, overlapping stoppages and missing diagnoses. Allow an unknown reason with an investigation owner rather than treating it as zero downtime. Accept the record when two supervisors classify the same examples consistently and a later explanation does not increase the total stopped time.
Key takeaways
- Accept the record when two supervisors classify the same examples consistently and a later explanation does not increase the total stopped time.