Overview

There are many scenarios where there may be a large block of time where an appropriate planned or unplanned downtime was not entered when it should have been.  There are cases where a downtime needs to be entered and the start time set to an earlier time, or cases where previous stopped need to be filled in after the machine has already gone back into cycle.  The Operator Data Interface provides the ability to modify Unknown Downtimes that have previously occurred for these scenarios. 

There are two methods of classifying unknown downtime from ODI, both of which are controlled by permissions.  The first method is to enter a planned or unplanned downtime and set the start time of the downtime to when the currently active unknown downtime began.  The second method is to view a list of previous unknown downtimes and back fill each with the appropriate downtime reason.

The Modify Time Stamp button has two possible options; Current and Previous.  If the permissions are enabled for only one of the options then when the Modify Time Stamp button is pressed the user will not see a drop down with the two choices.  The appropriate functionality will simply be displayed for the only available option.  If data is modified by either the Current or Previous option an audit record is written to capture the modification.  The modifications can be viewed with the Modified Data report.

Setting the Start Time for the Current Downtime Being Entered

The Current option is used when the equipment is currently in an unknown downtime and the start time needs to be adjusted to an earlier point in time. When the button is pressed a date and time selector will be displayed which will default to the time in which the unknown downtime started. The start time for the downtime that is about to be entered can be set to when the unknown downtime started simply by pressing the Set button. The time can also be set to any time from when the unknown downtime started up until the current time.  If the time stamp to be used has been modified the date and time will be blue to identify that it has been changed.  Once the time has been modified a downtime can be selected and submitted by pressing the Start New Status button.  Once the time has been modified it can be reset and changed back to the current time by pressing the Now button on the date and time selector.

Classifying Previous Unknown Downtimes

Using the Previous option within the Modify Time Stamp button on the Operator Data Interface screen allows users to alter historical unknown downtimes.  The Previous option will display a list of all unknown downtimes within the specified time frame that are greater than the minimum time for unknown downtimes that can be classified.  Rules that control the list of qualifying modifiable Unknown Downtimes can be configured on the Manage tab on the Operator Data Interface Settings form.

Backfilling Previous Unknown Downtimes

The Current option can also be used when the equipment is currently in an unknown downtime and the cycle status and time need to be backfilled. When the button is pressed a date and time selector will be displayed which will default to the time in which the unknown downtime started. The start time for the downtime that is about to be entered can be set to when the unknown downtime started simply by pressing the Set button. Then you can select the status you wish to use then Start New Status.

In order to begin using these the standard Planned Downtime Start and Unplanned Downtime start expressions will need to be removed and replaced with the first two expressions below.  Basically, these will not execute if the current status is unknown downtime.

ODI - Planned Downtime Start without Unknown Downtime

Starts a planned downtime for the specified downtime code as long as the current status is not Unknown Downtime.

([Listener.data] = [PCSDB.SI_Planned_DT_Start]{identifier.any}) AND ([PCSDB.general_equipment_status] != [PCSDB.UNKNOWN_DOWNTIME])

[PCSDB.send_planned_DT_start] {Listener.data{identifier.specific}}

ODI - Unplanned Downtime Start without Unknown Downtime

Starts an unplanned downtime for the specified downtime code as long as the current status is not Unknown Downtime.

([Listener.data] = [PCSDB.SI_Unplanned_DT_Start]{identifier.any}) AND ([PCSDB.general_equipment_status] != [PCSDB.UNKNOWN_DOWNTIME])

[PCSDB.send_unplanned_DT_start] {Listener.data{identifier.specific}}

These second two expressions are the replacements which will execute if the current status is unknown downtime, and will backfill to when the unknown downtime started. This basically automates the Modify Time Stamp - Current functionality. If the equipment was in an unknown downtime this variable [PCSDB.send_planned_DT_start_historical] {Listener.data{identifier.specific},[PCSDB.Unknown_Downtime_Start_Time]} will hold the time stamp when the unknown downtime started. Now, the Historical variables can be used along with this new variable to backfill the unknown downtime.

ODI - Planned Downtime Start with Unknown Downtime Backfill

Starts a planned downtime for the specified downtime code and backfills the previous unknown downtime.

([Listener.data] = [PCSDB.SI_Planned_DT_Start]{identifier.any}) AND ([PCSDB.general_equipment_status] = [PCSDB.UNKNOWN_DOWNTIME])

[PCSDB.send_planned_DT_start_historical] {Listener.data{identifier.specific},[PCSDB.Unknown_Downtime_Start_Time]}

ODI - Unplanned Downtime Start with Unknown Downtime Backfill

Starts an unplanned downtime for the specified downtime code and backfills the previous unknown downtime.

([Listener.data] = [PCSDB.SI_Unplanned_DT_Start]{identifier.any}) AND ([PCSDB.general_equipment_status] = [PCSDB.UNKNOWN_DOWNTIME])

[PCSDB.send_unplanned_DT_start_historical] {Listener.data{identifier.specific},[PCSDB.Unknown_Downtime_Start_Time]}

---