OCO run-time behavior

The run-time behavior indicates the state of the OCO at run time. When you deploy the OCO OnScan, it starts using the configured OCO information for run-time operations.

During OnScan, the OCO checks for a client session on the engine. If the OCO is the first object on the engine, the OCO creates a special stateful client session for its use. All the new OCO objects use the same client session that is created by the first OCO object.

Since the OCO creates a special client session, the Stateful API cannot be used on a engine that contains the OCO. The Stateless API can be used on a engine that contains the OCO.

Once the object has a client session, the object initializes all the configured production and consumption counters by reading the latest value from the I/O (if configured). The object will not write any production or consumption counts to the MES database until the values change from the initialized readings.