Perform Custom Mapping (Optional) - Intergraph Smart 3D - Administration & Configuration

Intergraph Smart 3D Export PDS to Smart 3D

Language
English
Product
Intergraph Smart 3D
Subproduct
Plant Design System
Search by Category
Administration & Configuration
Smart 3D Version
12.1 (2019)

Mapping ensures a meaningful translation of data display and property labeling from PDS. Mapping takes an object property from exported PDS data and maps it to the same or a similar property in Smart 3D. Smart Interop Publisher provides Excel-based (.xls) mapping files and includes an out-of-the-box or default mapping file for PDS published v. 11.0 and later data. This default PDS mapping file provides the class definitions, interfaces, properties, and mappings for a basic set of objects common to PDS.

Additionally, for each default mapping file, Smart Interop Publisher provides a corresponding custom mapping file to include any custom PDS classes and objects. The two mapping files work together during translation to provide coverage of all your PDS model objects.

PDS Published Files

The Material Data and SmartPlant Publisher utility (MDP) allows you to generate graphics (.zvf), database (.xml), and object range information (.xrg) files. An .xrg file is required for a translated Smart Model .zvf project that is going to be opened in SmartPlant Foundation. The Material Data and SmartPlant Publisher uses selection set files to determine what data to publish. The MDP interface allows you to select specific disciplines, model areas, and models within the project to publish, and to save different sets of models in separate selection set files. For more information, see Material Data Publishing Workflow in the Plant Design System (PDS) Material Data and SmartPlant Publisher User's Guide.

Requirements and Considerations

  • All PDS 3D source file types must be in the input location.

  • PDS-published source files (.zvf + .xml + .xrg) are translated to a Smart Model .zvf project containing .zvf, .mdb2, and .xrg files.

  • The export cannot contain duplicate linkages.

  • Custom mapping for Smart 3D requires you to specify the source interfaces.

  • You must add new classes, interfaces, and properties to the CustomR3DSchema.xls file delivered with Smart 3D.

Workflow

The steps below summarize the custom mapping process. Custom mapping is optional; you can use the default mapping already available. However, if you have new classes or objects in PDS, you must use custom mapping to get this data into Smart 3D. A delivered SPIOPSchema.xlsx file provides a list of classes, interfaces, and properties that Smart 3D supports. The Schema sheet provides the class-to-class and interface/property-to-interface/property mapping for Smart 3D. Use this file only as a reference for custom mapping. By default, this file is delivered in [drive]:\Program Files\SmartPlant\Interop Publisher.

  1. Review the PDSToR3DMapping.xls or PDSLegacyToR3DMapping.xls default mapping file to see the classes and properties that are currently mapped.

  2. Make a copy of the customPDSToR3DMapping.xls or customPDSLegacyToR3DMapping.xls file located in the CustomMappingFiles folder, and place the copy in another folder location.

  3. Edit the custom mapping file to either modify property labels or add classes and properties.

    • Any new custom interface names must contain the “R3D” substring. Otherwise, the software does not map the properties contained in the interface.

    • The exclamation point (!) in the A column comments out or excludes that row.

    1. To add a new class in the ClassMap sheet:

      1. Add a new row, and then enter the new class in the Source Class column.

      2. In the Target Class column, type in the Smart 3D class name that relates to the class you are adding. Use the SPIOPSchema.xlsx to look up the available classes.

    2. To add a new property in the PropertyMap sheet:

      1. Add a new row and enter the new class in the Source Class column.

      2. In the Source Property column for the new class, type in the new property name.

      3. In the Target Property column, type in a property from SPIOPSchema.xlsx file that relates to your new property.

    3. To display unit strings such as 'meters' or 'inches' with specific property values in the translated model, you can define the Units G column in the custom mapping file. For more information, see Set the units of measure (UoM) in custom mapping.

    4. Repeat for each new class and property.

  4. Save the edited mapping spreadsheet file in the Microsoft Excel 97-2003 Workbook (.xls) format.

Next: Create a Project in Smart Interop Publisher

See Also

Exercise: Map Custom Properties and Convert to SIOs