Finding And Editing Outstanding Downtimes
In the left navigation menu, each downtime area will have a prompt that shows how many downtimes haven't been given a cause/equipment either from the automated downtime detection or via a manual process like the OpStation. In the case below, the Machine Module has 4 outstanding downtimes that need to be edited:
Clicking the link will take you to the downtime entry page and will show only outstanding downtimes for the Machine Module area:
By convention, default causes are Select a Cause and default equipment are N/A. Your particular configuration may differ, especially when it comes to how causes relate to equipment and what will determine the final detail code. In the examples, equipment depends on cause and the final determinator of the detail code is the equipment.
Current downtime for a stopped machine shows Pending for the start.
To edit a downtime, simply click the Edit button. From there, you can (depending on your security role) edit the various parts of the downtime.
Once a cause, equipment, and detail are selected a comment is usually required. After entering all the required information, click Update and the downtime will disappear from the list in the left navigation.
Advanced Editing (Splitting, Editing Start/End, Deleting)
With the right roles, more options will be available for editing downtime: change the start and end times, split a downtime, or delete it entirely. To work with advanced options, use the Downtime Entry page that is usually available in the top navigation menu under Downtime:
Once on the Downtime Entry page, you'll be able to see all the downtime for a given area or areas. Select the start and end time to look at, then the area under consideration. You can also filter out short downtimes by increasing the minimum duration to view. After clicking Refresh, you'll see the list.
Full permissions allow complete control of the downtime, including modifying the start and end times. A common use case is splitting a downtime: the machine went down for one reason, but during the downtime the reason changed.
First, click the split button. Second, you'll need to specify the time where the original event ends and the new event begins:
In this case, the new time was set to be 12:30 instead of 7:12, so the original downtime was shortened from 5h 50m to 5h 17m:
After updating the details of the original downtime, you'll see it and the new split in the list:
Finally, edit the new split downtime to be the correct cause/equipment.
Important point: the new split downtime does not count as a stop! There is only one stop, but two different reasons it was down. You can of course change that if you want to include another stop that perhaps wasn't captured by the downtime system.
Table of Contents
| Table of Contents | ||
|---|---|---|
|