Configure extended production attributes

You can extend the amount of data you want to record when the PEM instance is triggered by configuring extended production attributes (EPAs) in the Extended Production Attributes section.

If any PEM extended production attributes are inherited from a parent OCO template, they appear in the Inherited Extended Production Attributes list.

Up to 48 EPAs can be created for each PEM instance. You can create an extended PEM attribute only if you select to log its value to the database. You can specify the type of data such as Boolean, String, Float, Double, or Integer that is logged for the extended PEM attribute to the database. Extended production attributes can be directly configured using a derived template or instance of an OCO with a PEM instance, or can be inherited from a parent template.

You can specify the name and data type of an extended production attribute if you want the extended production attribute to be recorded when the PEM instance is triggered.

If you want to associate an extended production attribute with a System Platform attribute, then provide an input source reference.

You can configure extended PEM attributes for a PEM instance only after configuring PEM attributes. A single PEM instance supports extended PEM attributes only for a specific command (for example, add production or add consumption).

The set of extended production attributes configured for a PEM instance are grouped under one data log group in the MES database. The data log group name obtained for this PEM instance will be unique across all OCO instances. And, each extended production attribute (name) is added as a value_name in the Data_Log_Value table, corresponding to its data log group. Each value name in the Data_Log_Value table for a data log group is uniquely identified by the value_index. Thus, a value specified at run time for an extended production attribute is logged in the Data_Log table corresponding to its value index column that is related to the value name for a data log group.

After the extended production attributes are configured for a PEM instance, and when the OCO instance is deployed, the Entity Model Builder automatically creates the necessary data log group and data log values in the MES database, so that the value from these extended attributes can be properly logged into the corresponding value* columns in the Data_Log table.

For example, the data log group name for the PEM extended attributes are typically represented as:

• OCO_001|Mixing|ProductionData

• OCO_100|Blending|MaterialConsumption

When the extended attribute data is triggered:

• The middleware queries the Data_Log_Value table using the supplied data log group name and value name (extended attribute name) to retrieve the value index.

• After the value index is retrieved, the supplied extended attribute value is copied to the corresponding value* column in the Data_Log table.

• This process is repeated for all the supplied extended attributes.

• The extended attributes that match those of the value_name column for a data log group in the Data_Log_Value table are the only attributes that gets logged into the Data_Log table, and the remaining value* columns are updated with (blank) values. An exception will be thrown to the caller if the supplied extended attribute name does not exist in the Data_Log_Value table for the supplied data log group.

The values collected at runtime from these extended attributes will always be recorded in the Data_Log table.