During the execution of a Work Order, it is possible to capture two different types of interruptions: pause (“Pause”) and stop (“Stop”). Each type of interruption can be associated with specific reasons previously defined in auxiliary catalogs. This distinction allows for more precise traceability and a deeper analysis of operational downtime.
Definition: Pause vs Stop
Pause (“Pause”): It is a temporary interruption of a task with the intention to resume it later. It is commonly used to wait for some supply, during meal preparation, at the end of a shift to transfer the activity, or for quick coordination between teams.
Stop (“Stop”): Refers to an interruption that is considerably more critical or prolonged compared to a simple pause. This type of stop may imply the total completion of the task that was being performed, meaning that the work will not continue at that moment and may not resume without prior review.
Configuration of reasons in Auxiliary Catalogs
The configuration of pause and stop reasons is done through the Auxiliary Catalogs. In the configuration module, there is a specific “Work Orders” catalog where reasons for pauses and stops can be created.
It is essential to define separate motivations for each type: a “pause” reason must belong to the set of pauses, and a “stop” reason to the set of stops. This ensures that when registering an interruption, the technician selects the appropriate category.
Operational registration during Work Order execution
When a technician starts a task of a Work Order, they must click “Start” to begin execution.
If they need to pause the task momentarily, they can use the “Pause” option. When doing so:
To continue the task after the pause, the technician must click “Resume,” and the system will save the pause time in the records (“Records”).
If the task has been completed or has ended for any reason, the technician must register a stop by selecting a reason from the stop catalog (Stop).
This indicates that the task has concluded and will not be resumed.
Once the stop has been registered and when attempting to exit the task execution section, the system will present an automatic confirmation.
This window will validate that the task progress has reached 100% and will offer the option to change the status of the Work Order to "Under Review," thus facilitating the transition to the next step in the workflow and ensuring consistency of the WO status.
Note: After registering a stop and the task is shown as completed, if the Work Order has not been sent to a "Completed WO" queue, it will still be possible to access it and restart the execution of the task.