Select Classes

The Classes tab of the Gateway Setup window enables you to select the classes to be exported. The classes you select here are included in the EIWM/JSON/SVG files.

The following image shows the Class selections area. The classes that have been selected in the Classes Tree tab of the Settings dialog box are listed in this area and are available for selection in the configuration. For more information about the Classes Tree tab, see Enable Draw Classes for Selection in the Configuration.

To select classes:

1. Select the check box corresponding to the class you want to select for export.

   Note: If you want to remove a class, clear the check box for the class. If you want to select a sub class, drill-down the corresponding parent class. The SHEET class is selected by default.

2. By default, the graphical data option is selected. This is indicated by the presence of an image symbol adjacent to the SHEET class. If you do not want to generate graphical data, then click the symbol. The symbol is struck off and removed to indicate the graphical data will not be generated.

3. Repeat step 1 for selecting more classes.

After selecting the classes, you can apply filters on them and specify the mappings. For information on how to apply filters, see Apply Filters and for information on how to map items, see Map Element Types.

Class Selection Strategies

Due to the complex nature of AVEVA™ E3D Design and the associated project data, it is advised to create the configurations so as to ensure that the publishing performance of the AVEVA™ Gateway for Unified Engineering remains optimal.

Models in AVEVA™ E3D Design could often have large number of sub classes under a parent class. For such projects, publishing the graphical data of the topmost parent as a single model (single SVG file) can result in memory-related issues and sub optimal performance of the AVEVA™ Gateway for Unified Engineering. Therefore, it is advised to create configurations in such ways that generated SVG drawings would be split into multiple files of smaller sizes.

Dividing models into smaller parts for publishing is also beneficial in case of future model updates. Consider the case where a large SITE has been published as one model to AVEVA™ Asset Information Management and at a later point in time, it must be updated due to changes in source model. In such cases, the entire SITE need not be published once again if the graphical data has been split into multiple files.