Export issues - Intergraph Smart 3D - 13.1 - Administration & Configuration - Hexagon PPM

Intergraph Smart 3D PDMS Conversion to Smart 3D

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

Consider the issues listed below when exporting Smart 3D model data to PDMS:

Hierarchy exported from Smart 3D to PDMS

PDMS has a fixed hierarchy for model objects across the various disciplines, whereas Smart 3D can have a deep hierarchy of systems in place prior to the creation of model objects. In the PDMS hierarchy, the parent of equipment, pipeline systems, and structural objects is created as a zone object, and the parent of a duct run is created as an HVAC object. In the current release of the software, you can control how the hierarchy is created based on the option CreateHierarchy in the PDMSExportTranslator.ini file.

Names of objects in Smart 3D and PDMS do not match

Typically caused by object names being duplicated during Smart 3D modeling. During export, the unique name generator mechanism creates new unique names for objects whose names are duplicated. For more information about recommended naming conventions, see Best Practices in Export Smart 3D Model Data to PDMS.

The way pipes and ducts are split into branches is inconsistent with the way that they would be modeled in PDMS

Smart 3D provides two options:

  • A break at the pipe/duct run level can cause this problem. Check the pipe/duct run for breaks.

  • Merge all pipeline/duct components between two free ends, two nozzles, one free end and one nozzle, one branch and one free end, and so on to construct the branch in PDMS. This is controlled using the default setting of the MergesS3DRuns/MergeS3DDuctRuns option in the PDMSExportTranslator.ini file. When this option is used, the run names in Smart 3D and the branch names in PDMS can change and be reflected differently in the isometric drawing output.

Specifications are from PDMS and not from Smart 3D

Piping and HVAC data are transferred using mapping to the equivalent specification present in PDMS. To resolve this issue, create the needed specifications in Smart 3D, provide the required mapping, and then perform the transfer.

Update of objects

Updating objects that have been exported to PDMS is supported in the current release of the software based on ExportOption in the PDMSExportTranslator.ini file.

Incremental transfer of the model

The same model can be broken into multiple filters or sizes and exported incrementally. If the objects already exist in PDMS, they can be overwritten or skipped based on ExportOption in the PDMSExportTranslator.ini file.

Label size in Smart 3D

While defining labels on Smart 3D objects, make sure the length is less than 50 characters. PDMS produces errors if a label longer than 50 characters is mapped to any user-specified attribute in PDMS.

Smart 3D piping data

When exporting a piping model from Smart 3D using an object type filter, select the Piping node, and then under the Systems node, select Piping Systems and Pipelines .