Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

Minimum Time Before Activation

  • Last UpdatedMar 19, 2016
  • 1 minute read

The period of time that determines how long a raw reason code’s expression has to be True before it is considered a candidate to be the active raw reason code. This value has the format hour:minute:second.millisecond (for example, 00:00:10.5 for 10 and a half seconds).

For a raw reason code to become the active raw reason code, the raw reason code expression must evaluate to True and meet the minimum time to activation requirement.

One use of this parameter is to filter out noise conditions. Another use would be to define two raw reason codes with identical expressions where one has a minimum activation time and the other has none. Once the event has been in a specific reason greater than the minimum activation time, the entity can change into a different reason that might have a different utilization state so as to classify the event time as performance instead of utilization.

If a raw reason code expression evaluates to True and stays True beyond the minimum time before activation, and has the highest priority of all the True raw reason codes, it becomes the active raw reason code.

The time logged for a new active raw reason code will be the time when the minimum activation time elapses.

All timers for raw reason code expressions that are still true after a higher priority raw reason code became true will not be reset and will continue to be evaluated as True.

Once an active raw reason code transitions from True, to False, and back to True, its timer is reset from the point it evaluates True once again.

TitleResults for “How to create a CRG?”Also Available in