Enter Stoppage Reason
This Activity Template is related to the OEE measurement where the required effective running hours will be derived. This template introduces a pre-defined Stoppage Reason Tree for easy reference.
The stoppage tree consists of three (3) levels and complies with the best practice definition:
- Level 1: Stoppage Group – The stoppage group represents the actual organisational group who will take responsibility for the issue resolution
- Level 2: Stoppage Category – The stoppage category will provide the classification of whether the stoppage is either a planned or unplanned activity. This classification is already defined in TilliT DO and each stoppage reason is already mapped in the background
- Level 3: Stoppage Reason – This is the actual list of stoppage reasons, where the operator will be able to select the applicable reason
In the template definition, there are three (3) stoppage reasons where the automation can automatically provide the reason:
- Upstream Fault – Starve
- Downstream Fault – Blocked
- Machine Breakdown - Faulted
This allows TilliT to comply with the best practice definition where if the stoppage reason is known, it should be displayed/made available for the user. Usually, the same stoppage reason is available in the automation HMI.
The activity template makes the stoppage duration available upon completion of the event. Here, TilliT uses the following equipment status transitions to automatically create the stoppage event.
Once the stoppage duration is known, then the activity template will be launched for the operator to confirm the activity.
Confirming the stoppage reason means that the operator can either;
- *Split the stoppage duration into several stoppage events where the operator can specify the time cut-off between the different stoppage events
- Specify the appropriate stoppage reason (for the given stoppage duration) as to why the operator stopped the machine
*Note: This function will not be part of the TilliT DO version 01.
The below lists the reason tree which is currently defined in TilliT DO under the Options setup;
The below workflow describes the TilliT DO setup in generating the stoppage reason confirmation event.
