Update MES entities with OCO changes

You can use the Entity Model Builder to update your MES entities with any of the following changes made to the OCOs in the System Platform IDE:

• Changing the configuration of an OCO.

• Adding an OCO at a higher level in the equipment model.

• Moving an OCO to a higher level in the equipment model (re-parenting).

• Renaming a parent to an OCO at a higher level in the equipment model. This creates a new entity in the MES database and re-parents the old entity's children, if there are any.

• Adding an OCO to the equipment model that has the same name as an entity manually configured using MES Web Portal or MES Client. The existing entity's children (if any) are re-parented.

• Moving an OCO to another parent application object. The old parent is no longer considered an entity from the perspective of Entity Model Builder. However, if the entity has already been created in the MES database, it will remain in the database. This creates a new entity and parent entities, if needed.

If you remove an entity in your IDE equipment model, the entity is not deleted in MES.

If you have not made any changes to the OCOs in the System Platform equipment model, the Entity Model Builder just checks that the OCO configuration in the System Platform equipment model also exists in the entity model in the MES database. If there are any differences (for example, if someone changed an entity's configuration using MES Client), the MES configuration is updated to match the System Platform configuration.

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.