About Importing Models

The following are important points regarding the Batch Server Name and importing from multiple AVEVA Batch Management Servers:

• When you import from a Batch Server, the Batch Server Name (defined in the EnvEdit System Parameters) is written into each object’s BatchServer attribute. This connects imported objects to a particular Batch Server.

• That Batch Server Name is also used as the Template Toolset name in the IDE. If a Batch Server Name is not defined, the name "Default" is used.

  Important:
  
  If you change the Batch Server Name for a particular Batch Server (in EnvEdit system parameters), you will need to delete all objects and re-import the model. Or, alternatively, a utility (BatchObjectUtility.exe) is available on the Developer Network to help change the BatchServer attribute value in the existing AVEVA Batch Management objects. See the Tech Note named "Tech Note 932 - Using the Batch Object Utility".
  
  If you are importing from multiple Batch Servers, each with its own Process Model, the servers cannot contain the same Process, Transfer, Unit, Connection, or Segment names. In other words, equipment cannot be shared between the Process Models. If this is the case, you can use the prefix/suffix option within the import utility to help solve the conflicts.

The following are points regarding communication with the AVEVA Batch Management Server:

• The base AVEVA Batch Management Server services must be running to do the import (SecMngr, Middleware, and so on).

• You cannot do an import while ModelEdit, TagLinker, or TrainEdit is running. You cannot run any of these editors while an import is in progress.

• If AVEVA Batch Management application security is enabled on ModelEdit or TagLinker, you must enter security credentials at the time of the import that satisfy both security requirements.

• The import can be time consuming. For a very large Process Model with thousands of objects, it can take well over an hour. Subsequent imports, even with minor changes, can take about 25% of the original import time, just to check for differences (results may vary).

  Important: Tag Links are automatically updated in the Tag Linker database to map the AVEVA Batch Management tags to the ApplicationObject attributes. The Galaxy Access is set to point to the current Galaxy. All tags in the AVEVA Batch Management Process Model are linked, including System Tags. Links should not be modified in TagLinker. They could be overwritten during the next import.

The following are important points regarding object creation.

• Template objects are created for each Process and Transfer. Phase Template objects are created beneath each Process/Transfer.

• Instance objects are created for each Unit and Connection. Phase Instance objects are created beneath each Unit/Connection.

  The generated Phase instance objects are named by concatenating the Unit or Connection and the Phase name, creating a unique "tagname". The "contained name" of the instance will be the original Phase name. This allows the phase instance to be accessed using the expected hierarchical name.

• Instance objects are created for each Segment.

• Subsequent imports will add new Process, Transfer, Unit, Connection, Phase, and Segment objects. A subsequent import will not delete existing objects. Within each object, all attributes will be synchronized with the AVEVA Batch Management Process Model.

• During the import, the following characters in object names or attributes are replaced with an underscore: !@%&?

• If an object already exists with the same name, or if a conflicting attribute already exists (for example, a UDA), the import reports a warning. Check the ArchestrA Logger for warnings after an import.