UCO Run-Time Behavior
- Last UpdatedMay 17, 2023
- 1 minute read
Once you deploy the configured UCO OnScan, you can start evaluating raw reason codes and logging utilization events when the active raw reason code changes.
At run time you can:
-
Monitor the raw reason code attributes:
-
RawReasonCode
-
PreviousRawReasonCode
-
RawReasonCodeDefaultReason
-
RawReasonCodeDelay
-
RawReasonCodeDescription
-
TimeEntered
-
TimeInRawReasonCode
-
-
Monitor for errors using the ErrorCode, ErrorMessage, and Status attributes.
-
Reset any error condition using the Reset attribute.
-
Enable/disable logging of utilization events to the MES database.
-
Monitor current performance parameter values are based on the current shift.
Related Links
- Production Run-Time Operations
- Utilization Run-Time Attributes
- UCO Run-Time Deployment and Execution
- UCO Run-Time Status
- Switching the UCO Between Automatic and Manual Mode to Record Downtime Events
- Resetting Error Attribute Values
- How Rejected Messages Are Handled
- Effect of Stopping and Restarting the Middleware Connection When the UCO Is Deployed
- Background User