Export PDMS Data and .att Files - Intergraph Smart 3D - 13.1 - Administration & Configuration - Hexagon PPM

Intergraph Smart 3D Integration - HxGN SDx

Language
English
Product
Intergraph Smart 3D
Search by Category
Administration & Configuration
Smart 3D Version
13.1
Smart Interop Publisher Version
16.2

Export Data Files

  1. Create the .rvm output file name with the path and extension. For example, in the AVEVA application, select Utilities > Export > Create.

  2. Ensure that you select the Binary option that is supported by Smart 3D.

  3. Select the sites to export.

  4. For the Rule Class, select User Defined Export Rules to add new color rules for the .rvm (binary only) file.

    1. Define the color rule class name and description.

    2. Define the rule for the component that requires a color.

    3. Define the rule description to identify the component.

    4. Define the color index number for each object type.

    5. Insert the new rule and then repeat to add as many color rules as required. The new rules display in Rules Class.

      For more information, see your AVEVA PDMS documentation.

  5. Make sure REPRESENTATION is ON and INSULATION/OBSTRUCTION values are between 12% and 87% to display aspects for piping and equipment objects, and to translate obstruction objects as transparent.

Export .att Files

  1. Locate the MACRO. The default path for the MACRO is:

    C:\AVEVA\Plant\PDMS[Version Number][Service Pack]\PMLLIB\reviewinterface\forms

    Version Number = your PDMS version number.
    Service Pack = the service pack number (if any) for the PDMS version. Example for PDMS version 12.1, Service Pack 4:

    C:\AVEVA\Plant\PDMS12.1SP4\PMLLIB\reviewinterface\forms

  2. If you require TUBI objects to be created as individual objects with attribute data, locate the TUBI information in the MACRO under Loop through the list of elements and add '--' for the comment in the following four lines as shown in the example:

    You must edit the MACRO (cdxattdump.pmlfrm) to add TUBI and other information such as port direction and connection. Otherwise, the software skips TUBI information by default.

  3. To get additional attribute data in the .att file such as APOS, LPOS, P1DIR, P1CONN, and CATREF, add ATTL (!ATTL.append(‘’)) entries as shown below to append the required properties.

    The CATREF property on the Pipe Components is used to create the Customized PortCatRef property on pipe ports. The Customized PortCatRef property is then mapped to the End Standard property.

  4. To export the .att file:

    1. Select Utilities > Export > Dump Attributes.

    2. Enter the output file name with the path and extension (.att only). This file name should be the same as the corresponding .rvm file name.

  5. To get multiple site .att files in a single .att file, select Database Elements under Export Attribute file.

  6. Ensure that the resulting .rvm file and its associated attribute (.att) file have the same base file name so that Smart 3D can create the label database (.mdb2) file during the translation process. For Smart Interop Object generation, only enhanced .att files with ports data generated by a customized ATT dump macro are supported.

There should be a one-to-one correlation between the graphic objects in the .att (if multiple .att files are not generated), and the .rvm file. The property information of all the graphic objects that are in the .rvm file should be present in the .att file to achieve a correct grouping of graphic objects.

NEXT: Translate PDMS Data Using Smart Interop Publisher