Log utilization events

The Log Utilization Events attribute allows for stopping the UCO from logging utilization events. The events can then be entered manually by an operator using a .NET controls-based UI (such as MES Operator or a custom UI) or using MES Web Portal.

• If selected, the UCO will automatically log utilization events.

• If cleared, the UCO will stop logging utilization events. Utilization events can be logged manually.

This capability can be useful when, for example, the PLC providing the equipment raw reason code fails or malfunctions for some reason. The UCO can then be switched to manual mode by an operator or through script detection switches. Although the UCO will stop logging utilization events, it will continue to update other UCO attributes, such as OEE attributes, so that current utilization data can continue to be viewed in the UI.

To change the logging mode during configuration by value

1. Clear the Use Input Source check box.

2. Select or clear the Value or Input Source check box.

   

3. Save your changes and deploy the UCO.

To change the logging mode during configuration using script detection switches

4. Select the attribute or command’s Use Input Source check box.

   The control in the Value or Input Source column becomes a box.

   

5. To specify the input source, do one of the following:

   • Manually enter the input source.

   • Click the attribute's Browse button. In the Galaxy Browser dialog box that appears, select the object and its attribute that is the input source.

     

To change the logging mode during run time

• Open the application object in Object Viewer and set the Log Utilization Events to True or False.

Automatic Mode Behavior

When the utilization event logging is in automatic mode, raw reason code expressions are evaluated, run-time attributes are read from the MES database, and utilization events are logged into the MES database.

Manual Mode Behavior

When the utilization event logging is in manual mode, the object continues to evaluate the raw reason codes and sets the following attributes. However, no events are logged to the MES database. The object does not read current reasons from the database. Instead, it continues evaluating its logic to determine the correct raw reason code to log when it transitions back to automatic mode.

• PreviousRawReasonCode

• RawReasonCode

• RawReasonCodeDefaultReason

• RawReasonCodeDescription

• TimeEntered

• TimeInRawReasonCode

The following run-time attributes continue to be read from the MES database:

• CurrentOEEPercent

• CurrentPerformancePercent

• CurrentQualityPercent

• CurrentAvailabilityPercent

Failover Behavior

During failover, the current mode will continue to be active. For example, if the utilization event logging is in manual mode and a failover occurs, the logging will continue to be in manual mode.