Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

Export the entity model

  • Last UpdatedFeb 10, 2025
  • 2 minute read

You can manually export the System Platform Equipment Model to MES using the following methods:

  • Cascade export

  • Repeat export

For more information, see Creating entities with Entity Model Builder.

You can attempt a repeat export or cascade export, even if no changes are made to the System Platform equipment model.

Cascade export

You can select a root application object (for example, an Area) or a leaf application object (for example, a UCO, OCO, or SRO) to start the export. This enables a cascade export in a similar way as a cascade deploy. The export focuses primarily on the selected application object and its children. The parents of the selected application objects are also exported, but only to build the hierarchy until the selected application object.

If multiple application objects are selected, they will all be part of the export.

If the selected application object is not a UCO, OCO, or SRO and does not have a child UCO, OCO, or SRO below, then no object is exported. The user is informed that no object was exported via the normal progress dialog.

Repeat export

Repeat exports essentially check that the MES configuration is the same in the System Platform equipment model and in the MES entity model. If there are any differences, the MES configuration is updated to match the System Platform configuration. This ensures that any OEE/Utilization changes made via MES Client are overwritten on the next export when there is a contained UCO. Similarly, repeat exports check that the job exec configuration that exists in the System Platform equipment model also exists in the MES entity model. If there are any differences, the MES configuration is also updated to match the System Platform configuration.

This ensures that any job execution changes made via MES Client are overwritten on the next export when there is a contained OCO. Other changes such as labor, data log, and shipping capabilities made within MES Client are retained.

The SRO has no design-time impact and does not need to be re-exported.

In This Topic
TitleResults for “How to create a CRG?”Also Available in