How can we help?

Automatically Classify Short Unknown Downtimes

You are here:
< All Topics

Overview

Some downtimes are short enough that it may not be worth the time for an operator to manually set a downtime. In these cases, automatically converting Unknown Downtime when it lasts less than a certain amount of time will set it to a specified status.

Steps

First, determine the timeframe and the desired status. In this example we will use 2 minutes as the maximum Unknown Downtime to be set automatically and a status of Other, an Unplanned Downtime with a default status code of 308. Downtime codes can be found under Manage → Equipment Status → Cycle/Planned Downtime/Unplanned Downtime Statuses.

The following expression will check for the following:

  1. Current Status is Cycle
  2. Previous Status is Unknown Downtime
  3. Previous Status Timeframe was 2 minutes or less.

([PCSDB.general_equipment_status] = [PCSDB.CYCLING]) AND ([PCSDB.prev_general_equipment_status] = [PCSDB.UNKNOWN_DOWNTIME]) AND ([PCSDB.prev_general_equipment_status_time] <= 2)

This means the expression will only trigger when going from Unknown Downtime to Cycling, and when the Unknown Downtime was 2 minutes or less. Set the Target to Scytec PCS Database and the Result to the following:

[PCSDB.send_unplanned_DT_start_historical] {308, |'[PCSDB.unknown_downtime_start_time]'|}

This starts an Unplanned Downtime status at the start time of the Unknown Downtime, effectively overwriting it. If you want to use a Planned Downtime instead of Unplanned, the following Result should be used:

[PCSDB.send_planned_DT_start_historical] {###, |'[PCSDB.unknown_downtime_start_time]'|}

Replace ### with the desired Planned Downtime Code.

Table of Contents