Example: Entity creation

In the following example, if you select the UCO that is a child of the AAS_1_SQA_1 object, Entity Model Builder creates the objects above it as entities up to and including the Bearing Plant (area). Only the objects that contain one of the MES objects have the capabilities defined by the MES object. Other entities that are created to support the hierarchy and do not have MES capabilities enabled are not included in the license count of the enforced capabilities.

Since the other UCOs in the same equipment model are not directly part of the selected equipment tree hierarchy, they are not included in the entity creation because it isn’t part of the direct parent/child equipment structure.

You can similarly create entities by using the OCO or SRO.

You can also select any parent application object that has a UCO, OCO, or SRO descendant attached to it to create the same structure.

In the example above, you could have selected the parent application object AAS_1_SQA_1 directly and the result would have been the same.

If MES already has an entity created in the database, Entity Model Builder overwrites the entity information with the new configured information in a UCO, OCO, or SRO when you run Entity Model Builder.

Entity Model Builder does not delete an existing entity or remove any capabilities (including utilization/OEE capabilities.) It can re-parent entities at any level to reflect new structural changes to the System Platform equipment model hierarchy.

The new entity model is defined in the database with the same structure as the IDE model view. The utilization/OEE configuration information is extracted from the UCOs and stored in the corresponding entities. Similarly, the job execution and storage information is extracted from the OCOs and stored in the corresponding entities. An application object can contain only one UCO, OCO, and SRO.