Import AVEVA Recipe Management Model

The AVEVA Recipe Management Import utility imports all Draft and Approved Equipment and creates instances from the AVEVA Recipe Management object template.

The import utility retains several of the key settings between imports. The settings it retains are typically not changed from one run to the next. If you are importing in preview mode, the settings are not retained.

The settings are only saved for the current IDE node. If you run the import on a different IDE, make sure the settings are identically configured.

After you perform the import, check the Operations Control Logger for warnings. In the case of name conflicts, you must correct them manually and then retry the import.

To import a AVEVA Recipe Management model

1. In AVEVA System Platform, on the AVEVA Recipe Management menu, click Import AVEVA Recipe Management Model. The Import AVEVA Recipe Management Model dialog box appears.

2. In the AVEVA Recipe Management Server area, type the Host Name for the AVEVA Recipe Management server to which you want to connect.
   For more information, see the AVEVA Recipe Management Installation Guide.

3. Click Connect.
   After the utility connects to the server, the remainder of the dialog box becomes available.
   If you cannot connect to the AVEVA Recipe Management server, check the Operations Control Logger for more details.

4. In the Base Template area, type the base template name for the AVEVA Recipe Management Application Object. This defaults to the imported template name, but should be changed to a new derived template name.

5. In the Equipment List section, select the Equipment you want to import. By default, all the available pieces of Equipment are selected. Click to deselect individual pieces of Equipment. You also have the option to Clear All or Select All.

6. In the Options area, configure the optional import options.
   
   Select the Preview only mode checkbox for the utility to perform the import actions without actually making any changes to the Galaxy database. This allows you to see (and possibly verify) what changes are made by a normal import.
   
   Click Prefix or Suffix for the utility to perform the import normally, but add a prefix or suffix to every Equipment object. This allows you to avoid possible naming conflicts with existing objects in a Galaxy.

7. Click Import.

   NOTE:
   - If you make changes to Equipment using the AVEVA Recipe Management web client, you must re-import the object. Obsolete objects are not automatically deleted. You must manually delete them from the Galaxy. Objects that are checked out are skipped.
   
   - Objects that do not contain the latest approved Equipment model will cause Formula/Recipes to be Aborted after they are assigned.
   
   - The Remote Registry service should be enabled (if disabled) on the AVEVA Recipe Management server node to read the AVEVA Recipe Management https port number, which is, required for communication.