Understand how OCO-enabled objects are added to the MES database as entities

In the following example, if you select the OCO that is a child of the AAS_1_SQA_1 object, the Entity Model Builder creates MES entities only for the objects above it in the branch, up to and including the Bearing Plant (area). The attribute configuration information is extracted from the OCOs and stored as the corresponding property settings for the target entity (in this case, the AAS_1_SQA_1 entity).

The following figure shows the resulting entity tree in MES Client. You could also have selected the parent application object that has a OCO child attached to it and then run Entity Model Builder to create the same structure.

Since the other OCOs in the same equipment model are not directly part of the selected equipment tree branch, they are not included in the entity creation because they are not part of the direct parent/child equipment structure to the AAS_1_SQA_1 object.

Note the following additional behaviors about OCOs and using Entity Model Builder to create or modify their entities in the MES database:

• If you select multiple application objects with OCOs, the Entity Model Builder creates entities for all of them.

• If the selected application object is not a OCO, does not have a OCO below it, and is not part of an MES operations configuration hierarchy, then the Entity Model Builder does not create any entities.

• The Entity Model Builder only creates new entities and new entity hierarchies that do not already exist.

• To delete an entity, you must delete it using MES Client. For more information on managing entities, see the MES Client User Guide.

• If there is already an entity in the MES database with the same name as the application object with a OCO, Entity Model Builder will overwrite its corresponding properties with the OCO attribute settings.

• Though the Entity Model Builder never deletes an existing entity or removes any capabilities (including OCO capabilities), it can re-parent entities at any level to reflect new structural changes to the System Platform equipment model hierarchy.

• The Entity Model Builder might not allow some modifications to an OCO. For example, if an entity was created that could run jobs and jobs have been created on the entity, then clearing the Entity Can Run Jobs attribute will fail when running Entity Model Builder. Since there are existing jobs on the entity, it is not possible to remove this option from the entity until all existing jobs are completed or canceled.

• When the Entity Model Builder encounters an error, the error will be indicated in the progress window and the OCO will remain in the unsynchronized state. It will not be possible to deploy or redeploy the OCO until it is synchronized with the MES database. Additional diagnostic information is also available in the Operations Control Management Console Log Viewer.