Downtime Pareto and reason codes: make the stop log useful
Design a small reason-code tree, separate frequency from duration, reconcile overlapping events, and attach cost assumptions to the constraint.
The time included in a defined production plan after explicitly agreed exclusions.
State which breaks, maintenance and schedule conditions are excluded. Do not remove a loss merely to improve an OEE denominator. Use the same boundary for run time and included downtime, and keep customer-demand pace distinct from actual losses. Compare takt, cycle and lead time and the OEE loss tree.
Use the concept: Downtime log template · SMED changeover observation template · Takt time calculator
Design a small reason-code tree, separate frequency from duration, reconcile overlapping events, and attach cost assumptions to the constraint.
Why one OEE percentage is not a diagnosis, and how a loss tree turns downtime, speed loss, and defects into work the plant can actually prioritize.
A worked shift example separates customer pace, observed process speed and end-to-end delivery time, with practical checks before changing the line.