Mapping ensures a meaningful translation of data display and property labeling from PDMS. Mapping takes an object property from exported PDMS 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 PDMS data published from version 11.0 and later. This default PDMS mapping file provides the class definitions, interfaces, properties, and mappings for a basic set of objects common to PDMS.
Additionally, for each default mapping file, Smart Interop Publisher provides a corresponding custom mapping file so that you can include any custom PDMS classes and objects. The two mapping files work together during translation to provide coverage of all your PDMS model objects.
Requirements and Considerations
-
Smart Interop Publisher allows you to translate PDMS models with multiple attribute (.att) files in the same folder as the PDMS source file.
-
Review supported properties. See Supported PDMS Cross-section Properties.
-
Review the source .att files that contain Level (LEVE) and Obstruction (OBST) tags. Using custom mapping, you can specify an aspect using these tag values for equipment objects. See Map PDMS Equipment to Aspects.
Edit the Custom Spreadsheet
You can include new classes and properties, map any unmapped properties that you have added, and define unit of measure strings for property values using the customPDMSToR3DMapping.xls mapping template files. Here are the basic custom mapping steps:
-
Review the PDMSToR3DMapping.xls default mapping file to see the classes and properties that are currently mapped.
-
In the CustomMappingFiles folder, make a copy of the customPDMSToR3DMapping.xls file and place it in another location.
-
Edit custom mapping:
-
Modify property labels or add classes and properties. See Edit the custom mapping template file.
-
Specify an aspect for equipment objects. See Map PDMS Equipment to Aspects.
-
Define mapping for piping properties. See Map Custom End Standard Pipe Port Properties and Map Custom Pipe Properties.
-
Specify cardinal points for structure objects which are required in Smart 3D As-Built workflows. See Map Cardinal Point for Structures.
-
-
You can use the AspectMap sheet in customPDMSToR3DMapping.xls to specify an aspect for equipment objects.
-
The default object type is PIPE which causes Smart 3D to treat all object type specs as PIPE unless you specify your HVAC, cable tray, and conduit types contained in the .att file. To define the HVAC, cable tray, and conduit specs, go to the PDMS options in the Translation Settings for your project. See Define Translation Settings and PDMS options.
-
You can map codelist values to Smart 3D EndPrep and Pressure Rating port properties using the PipingPortEndConnectionTable sheet in the default and custom PDMS mapping sheets. See Map Custom PDMS Port Properties.
-
To customize the PortCatRef (End Standard) property of pipe ports, use the CodeListValues worksheet in the CustomPDMStoR3D mapping file. See Map Custom End Standard Pipe Port Properties.
-
Map the PDMS pipes to the corresponding HVAC, Cable tray, and Conduit classes of Smart 3D reference data with types provided for different pipe disciplines. For example, ELEC pipe type can be mapped to R3DCableTray class.
-
Primitives of pipe have the parent pipe attributes. The name of the pipe primitive would have its parent name appended, such as in HVAC PRIMITIVE.
-
Pipe component type names use the parent type as the suffix. For example, a new type for Branch (BRAN) of a pipe is PIPEBRAN. For an Elbow, the type name is PIPEELBO, and for Pipe primitives the type would be PIPEPART, HVACPART. You can map these pipe components in Smart 3D reference data with the types that are provided. For example, HVACNOZZ can be mapped to the R3DHVACNozzle class, and ELECPART can be mapped to the R3DCableTrayComponent class.
