Bad quality attributes in the OCO

When an OCO command is triggered and before the message is sent to the MES middleware, the OCO checks each attribute to be sent in the message for quality. If the quality for all of the attributes is Good, the data is sent to the middleware. If any of the attributes’ quality is Bad, a warning message is logged in the Logger and the command is aborted. The trigger for the particular function in the OCO is not reset; you must manually reset the object before the object is ready to be triggered again (see Reset the object to clear an error condition).

An example warning message is:

The quality of this attribute: ’WorkOrder’, Object:OCO_001, Entity:Machine_01 is not good to process the requested command.

In this scenario, no data is written and the ErrorCode and ErrorMessage attributes are not updated.