Load XGL

Load exports graphical data together with metadata to XGL/ZGL format. You can select the graphical data output type XGL/ZGL format under the Load/XGL panel.

After you select the required settings, click Save Settings to save the Load geometry settings of graphical data.

The XGL setting contains the following options:

• Graphics Output Type: Select the output file type for storing the graphics, such as XGL (XML format) or ZGL (compressed XGL format). You can use None option if no 3D graphical data is needed, for example, if only the EIWM file is needed. Selecting None means that no graphical data is written, for example, if only the engineering data via EIWM XML is to be imported into AIM.

• Output Destination: Select whether the output will be written to a File System or an AWS or AVEVA Cloud Storage.

  • File System:

    • Output Path: Type the Output file path or click the Browse for Folder tab to enter the output folder path.

  • S3: To access an S3 bucket requires the relevant authentication details like credential file, region information, bucket name and output directory. For more information, see Accessing an AWS S3 Bucket.

  • AVEVA Cloud Storage: For more information about accessing AVEVA Cloud Storage, see Accessing AVEVA Cloud Storage.

• Replicate Input Structure: Select this option if the input folder contains subfolders and you want the relevant output files to be located in the same subfolders of the output location.

• Generate Trigger File: After output file generation, to trigger the Import Controller, a trigger.start file is created in the staging area. It passes through three stages: start, process and finish. When the file reaches the finish stage, the output files are imported into AIM. The generateTriggerStart option is used to generate a trigger start file which directs the AIM Import Controller to start importing the output files in to AIM. The trigger file will be created after all processing has completed, if no errors have occurred. Configure this using the generateTriggerStart element, for example, <generateTriggerStart apply="true" />.

  Note: The apply value must be an xsd schema supported Boolean value. The valid values for xsd:boolean are true, false, 0 and 1. Attribute values that are capitalized (for example, TRUE) or abbreviated (for example, T) are not valid.

• Background: You can select the background colour of drawings. The background colour of the ZGL or XGL files generated by the project can be selected by any of these methods:

  • Colour: Select the required colour from the Colour list, for example, Black.

  • R, G, B: Enter the RGB values of the colour in the fields provided.

  • Pick Colour: Click Pick Colour and select the required colour from the standard colour selection dialog. A preview of the selected colour is displayed next to the Pick Colour button.

• View Direction: From the View Direction list, select the direction from which the drawings are initially viewed. You can select only one option from the list, for example, View from the Front.

• Save Settings: Click Save Settings to save the settings.

  Notes:

• You can set tracking of changes provided by XGL Load on data using annotations feature. For information about annotations, see Appendix C: Tracking Changes in Data.

• If during saving ID (object's or context's) to output EIWM or XGL/ZGL they contain any of illegal characters: "{" "|" "}", they are automatically converted to "_" to prevent issues with loading these files to AIM and warning message is added to the log.

  You can consider applying explicit transformation to change them to any other characters before reaching this stage of the processing.

  Log messages are as follows:

  • (EIWM Loader): The text: '{ABC123}' contains some of the illegal characters: "{" "|" "}" and they are replaced with '_'. Consider applying explicit transformation to change them.

  • (XGL Loader): The text: '{ABC123}' contains some of the illegal characters: "{" "|" "}" and they are replaced with '_'. Consider applying explicit transformation to change them.

    Such messages may repeat in the log due to multiple occurrences in EIWM and XGL files.