Stop reason setup
Before you can explain why a machine has stopped, you must first define your list of available reasons. You can create and assign these on the page linked here.
Configuration Guidelines
We recommend assigning 6 to 9 reasons per asset. Providing too many options often leads to a reduced in accuracy in the stop reasons that are selected by operators. There is a hard cap of 20 reasons per asset. However, there is no limit to the total number of reasons you can create in the global library.
Understanding Stop Categories
Every reason you create will have one of three categories. These categories dictate how the downtime affects your OEE data:
- Planned Downtime:
These are scheduled interruptions where no production is planned (e.g., holiday shutdowns, lunch breaks, or staff meetings). This time is not included in the planned production time, and therefore these stops do not impact your OEE score. - Regular Operations Downtime:
These are delays that occur as part of standard operations (e.g., product transitions, required cleaning, or routine inspections). These stops do impact Availability and OEE scores because they represent valuable time that could potentially be recovered through process improvements. - Unexpected Downtime:
These are unscheduled interruptions that disrupt production (e.g., equipment breakdowns, pump failures, or material defects). These losses also impact Availability and OEE scores.
Advise on selecting categories: It can be tempting to categorize more stops as Planned Downtime than is strictly accurate, as this increases the OEE score and makes performance look better on paper. Remember OEE is not simply an exercise to reach the highest possible number. The goal is to gain insight into where processes can be improved and to use that data as a tool for continuous improvement.
Explaining Downtime
Operator View
The operator view notifies users of downtime so they can provide the necessary context for each event. Whenever a stop is detected, or if there are unexplained stops from the past 24 hours, a yellow banner will appear at the top of the screen. Stops are also visualized in the status graph at the bottom of the dashboard.
Explaining a stop
Click directly on the stop in the graph or select "Explain Losses" in the yellow banner. Select the appropriate preconfigured reason from the list. Once saved, the color of the stop in the graph will update to match its category. Optionally an operator can add a note in the input field for further detail. They also have the option to split the stop to provide a unique reason for each part. Note: A stop can only be split once it is no longer ongoing.
By default, operators are not prompted to explain stops shorter than the Micro-stop cutoff or stops that fall outside of the Shift Schedule. If you wish to see and explain these events, you can toggle them on through the Display Options in the stops drawer.
