Choose AVEVA AIM Schema & Enable Automapping

The AVEVA™ Gateway for Unified Engineering (gateway) provides an option to map classes and their attributes automatically through the Perform automapping when adding classes check box in the Settings dialog box. The check box enables you to specify if you want the class and attribute mappings to be done automatically and is selected by default. Clear the check box if you do not want the mappings to be done automatically.

The gateway also enables you to specify the AVEVA AIM schema or ISM that can be used as a reference while adding the mappings. In addition to automapping of classes, attributes and associations, the schema you specify here is used to highlight the classes, attributes and associations of a class that are not present in the schema in yellow. However, this is just a visual representation and does not affect the export process.

To choose an AVEVA AIM schema:

1. On the Gateway Setup window, click Settings. The Settings dialog box is displayed.

   

2. On the AVEVA AIM Model tab, make sure that the AVEVA AIM option is is selected. The Active AVEVA AIM Server Information area with Active AIM Server details is displayed. Click Check Update to check for updates or click OK.

   Note: If you have not selected any active AVEVA AIM server, the AVEVA AIM Schema area is empty. Use the Add Server functionality in the AVEVA AIM group of the Admin tab if you want to add a new server or change the location of the server. The server you select as the default server in the Dashboard Server Selection dialog box is set as the active server for the gateway. For more information about the Add Server functionality and the Dashboard Server Selection dialog box, refer to the AVEVA™ E3D Design User Guide.

   Alternatively, you can also specify the mappings in a .csv file and place it in the Tables folder. Click Tables Folder and select the file that contains the mappings. The mappings defined in the file are considered when the !!ToMapped() and !!ToMappedSafe() PML functions are used for defining mappings.

   !!ToMapped(STRING, STRING) – the first argument is the input value that you are mapping from; the second argument is the table name (CSV file name) where the mappings are available. If this function fails to find the mapped value in specified table, an error is logged to the log file.

   !!ToMappedSafe(STRING, STRING, STRING) – This function works in a similar way except that you can define a third argument value that can be used as the default value if the mapping is not found. In such cases, the default value is used for mapping instead of logging an error.

   The following image illustrates an example usage.

   

To choose ISM:

3. On the Model schema tab, make sure that the ISM option is selected.

   

   Note: Import from ISM feature will allow to import GEICL file. By default, global settings are changed to ISM after importing the ISM file . It is recommended to choose the required Mapping Mode before exporting.

4. In the Nomenclature area, perform the following actions:

   1. Click Import from ISM option and select a GEICL XML file that contains ISM class and attributes model.

   2. Select the Source nomenclature from the available dropdown menu.

   3. Select the Target nomenclature from the available dropdown menu that will be used to translate class and attributes name from source nomenclature.

   Note: Source and Target fields will be enabled and populates naming conventions only after ISM Model has been imported.

   4. Expand ISM class and attributes model information to view the imported ISM details.

      

5. In the Project class mapping and Project attribute mapping area, perform the following actions:

   5. Select a Name source from the dropdown menu.

   6. Select an action to perform When not mapped.

   7. Select a Logging severity of mapping process when no mapped class was found for project class.