UCO attribute inheritance and planning the templates and instances

A recommended strategy for creating the UCO templates and instances is to first identify the generic raw reason codes that are common to all of the MES entities in the model and define these in a top-level template. Then you can create child templates for categories or classes of MES entities that share subsets of raw reason codes. This approach makes it easier to add or make changes to raw reason codes, as these changes will ripple down to all child UCOs and their corresponding MES entities.

For example, you might have raw reason codes that apply to an area of a plant or to a class of machines. So you could create a sub-template that includes those area or class-specific raw reason codes and from which specific UCO instances of that area or class would be created.

Note that, in the UCO templates, you can also define and lock any utilization, OEE, or production attributes that are generic to areas or classes of equipment.

Once the UCO templates configured with raw reason codes are created, you can create instances of them and assign the UCO instances to the appropriate MES entity application objects. For each UCO instance, you can then define the attributes that are specific to individual entities (these attributes will be those that are unlocked in the instance’s parent templates).