Export To PDMS User's Guide PDF

Download as pdf or txt
Download as pdf or txt
You are on page 1of 145

Export to PDMS

User's Guide

Version 2014 (10.0)

September 2013

DSHIP-PE-2000103C
Copyright
Copyright © 2010-2013 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
Portions of this software are owned by Spatial Corp. © 1986-2013. All Rights Reserved.
Portions of the user interface copyright 2012-2013 Telerik AD.
U.S. Government Restricted Rights Legend
Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the
United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
300 Intergraph Way
Huntsville, AL 35813
Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.
Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on eCustomer, SharePoint, or
box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph as guidance for
using a software product.
Terms of Use
a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the
software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the
Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take
precedence and govern the use of this software product and Documentation. Subject to the terms contained within the
applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the
Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal,
non-commercial use. The Documentation may not be printed for resale or redistribution.
b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license
agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a
reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial. The Other Documentation may
not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and for any
reason by Intergraph Corporation by giving written notice to Licensee.

Disclaimer of Warranties
Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph
Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability
and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed
a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its
publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used
or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Limitation of Damages
IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL,
SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF

2 Export to PDMS User's Guide


REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT
INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS
MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN
CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2)
YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED.
IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS
LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.
Export Controls
Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its
subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are
subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software
Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access)
under the following circumstances:
a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce
Denied Persons, Entities, and Unverified Lists, http://www,bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S.
Department of Treasury Specially Designated Nationals List,
www.treas.gov/offices/enforcement/ofac/http://www.pmddtc.state.gov/compliance/debar.html, and the U.S. Department of State
Debarred List.
c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design,
development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive
nuclear uses.
d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export
Compliance Department, Huntsville, Alabama 35894, USA.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, SupportModeler, and Intergraph Smart are trademarks or
registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows
are registered trademarks of Microsoft Corporation. ACIS is a registered trademark of SPATIAL TECHNOLOGY, INC. Infragistics,
Presentation Layer Framework, ActiveTreeView Ctrl, ProtoViewCtl, ActiveThreed Ctrl, ActiveListBar Ctrl, ActiveSplitter,
ActiveToolbars Ctrl, ActiveToolbars Plus Ctrl, and ProtoView are trademarks of Infragistics, Inc. Incorporates portions of 2D DCM,
3D DCM, and HLM by Siemens Product Lifecycle Management Software III (GB) Ltd. All rights reserved. Gigasoft is a registered
trademark, and ProEssentials a trademark of Gigasoft, Inc. VideoSoft and VXFlexGrid are either registered trademarks or
trademarks of ComponentOne LLC 1991-2013, All rights reserved. Oracle, JD Edwards, PeopleSoft, and Retek are registered
trademarks of Oracle Corporation and/or its affiliates. Tribon is a trademark of AVEVA Group plc. Alma and act/cut are trademarks of
the Alma company. Other brands and product names are trademarks of their respective owners.

Export to PDMS User's Guide 3


4 Export to PDMS User's Guide
Contents
Preface PDMS Guide ................................................................................................................................... 9
Documentation Set ................................................................................................................................. 9
Documentation Comments ................................................................................................................... 12
What's New in Export to PDMS ............................................................................................................ 12

Exporting Model Data to PDMS ................................................................................................................ 13


Set up the PDMS and Smart 3D catalogs ............................................................................................ 21
Configure the PDMS export initialization file ......................................................................................... 23
PDMS Export Initialization File Options.......................................................................................... 23
PDMS Export Validation ....................................................................................................................... 31
Validate mapping details ................................................................................................................ 31
PDMS Export Validation Dialog Box .............................................................................................. 32
Export Model ......................................................................................................................................... 36
Generate catalog and reference data in Smart 3D and PDMS formats for PDMS
export .............................................................................................................................................. 36
Export model data to PDMS ........................................................................................................... 38
Export Model to PDMS Datal Dialog Box ....................................................................................... 39

Troubleshooting ........................................................................................................................................ 41
Performance Tips .................................................................................................................................. 41
Import/Export Issues ............................................................................................................................. 42
Project Creation Estimates ................................................................................................................... 43
Mapping Tips .................................................................................................................................. 43

Appendix: Export to PDMS Workbook .................................................................................................... 45


Electrical Translation Maps ................................................................................................................... 46
ElectricalClassMap ......................................................................................................................... 46
CPElectricalSystemAttrMap ........................................................................................................... 47
CPCablewayAttrMap ...................................................................................................................... 48
CPRteCableTrayComponentAttrMap ............................................................................................. 48
ElectricalSupportAttrsMap .............................................................................................................. 49
ElectricalGlobalsMap ...................................................................................................................... 50
ElectricalRunSpecMap ................................................................................................................... 51
ElectricalPartIdentifierMap ............................................................................................................. 51
ElectricalComponentSPREFMap ................................................................................................... 52
Equipment Translation Maps ................................................................................................................ 53
EquipmentClassMap ...................................................................................................................... 54
CPSmartEquipmentMap ................................................................................................................. 55
CPEquipmentComptMap ................................................................................................................ 55
CPShapeMap ................................................................................................................................. 56
CPPipeNozzleMap ......................................................................................................................... 57
CPHVACNozzleMap....................................................................................................................... 58
CPConduitNozzleMap .................................................................................................................... 59
CPCableTrayNozzleMap ................................................................................................................ 60
CPStraightNozzleCatRefMap ......................................................................................................... 61
CPElbowNozzleCAtRefMap ........................................................................................................... 61

Export to PDMS User's Guide 5


Contents

CPHvacNozzleCatRefMap ............................................................................................................. 62
EquipGlobalsMap ........................................................................................................................... 62
PartNumberValueMap .................................................................................................................... 63
PartNumberAdditionalAttributes ..................................................................................................... 64
DesParamAdditionalAttrMap .......................................................................................................... 65
CPShapeValueMap ........................................................................................................................ 66
CPShapeAdditionalAttributes ......................................................................................................... 66
CPNozzleAdditionalAttributes ........................................................................................................ 67
NozzDesParamAdditionalAttrMap .................................................................................................. 68
Hierarchy Translation Maps .................................................................................................................. 69
HierarchyClassMap ........................................................................................................................ 69
CPMSystemMap............................................................................................................................. 70
CPAreaSystemMap ........................................................................................................................ 70
CPConduitSystemMap ................................................................................................................... 71
CPDuctingSystemMap ................................................................................................................... 72
CPElectricalSystemMap ................................................................................................................. 73
CPMachinerySystemMap ............................................................................................................... 73
CPPipelineSystemMapEx .............................................................................................................. 74
CPPipingSystemMap...................................................................................................................... 75
CPStructuralSystemMap ................................................................................................................ 76
CPUnitSystemMap ......................................................................................................................... 77
HVAC Translation Maps ....................................................................................................................... 78
HVACClassMap .............................................................................................................................. 79
CPDuctingSystemAttrMap .............................................................................................................. 79
CPMSystemAttrMap ....................................................................................................................... 80
CPDuctRunAttrMap ........................................................................................................................ 80
DuctComponentAttrsMap ............................................................................................................... 81
DuctSupportAttrsMap ..................................................................................................................... 82
DesignSupportAttrsMap ................................................................................................................. 82
HVACGlobalsMap .......................................................................................................................... 83
HVACPartIdentifierMap .................................................................................................................. 84
HVACEndPreparationMap ............................................................................................................. 85
HVACComponentSPREFMap ........................................................................................................ 85
DuctRunSpecMap .......................................................................................................................... 86
HVACDesParamMap...................................................................................................................... 86
Piping Translation Maps ....................................................................................................................... 88
PipingClassMap .............................................................................................................................. 89
CPPipelineSystemMap ................................................................................................................... 89
CPMPipeRunMap ........................................................................................................................... 90
PipingGlobalsMap .......................................................................................................................... 91
PipeRunSpecMap ........................................................................................................................... 92
SP3DPartIdentifierMap ................................................................................................................... 92
CatalogComponentSPREFMap ..................................................................................................... 93
NPDSpecificSPREFMap ................................................................................................................ 93
CatalogSpecialtySPREFMap ......................................................................................................... 94
CatalogInstrumentSPREFMap ....................................................................................................... 94
OnFlySpecialtySPREFMap ............................................................................................................ 95
OnFlyInstrumentSPREFMap .......................................................................................................... 95
PipeComponentAttrsMap ............................................................................................................... 96
PipeInstrumentAttrsMap ................................................................................................................. 97
PipeSpecialtyAttrsMap ................................................................................................................... 98
PipeSupportAttrsMap ..................................................................................................................... 98
EndConnectionMap ........................................................................................................................ 99

6 Export to PDMS User's Guide


Contents

Structure Translation Maps ................................................................................................................. 100


StructureClassMap ....................................................................................................................... 102
CoordinateSystemMap ................................................................................................................. 102
ElevationPlaneMap ....................................................................................................................... 103
GridLineMap ................................................................................................................................. 104
LinearMemberPartAttrsMap ......................................................................................................... 104
CurvedMemberPartAttrsMap ........................................................................................................ 105
InsulationAttrsMap ........................................................................................................................ 106
SlabAttrsMap ................................................................................................................................ 107
StairAttrsMap ................................................................................................................................ 107
LadderAttrsMap ............................................................................................................................ 108
HandRailAttrsMap ........................................................................................................................ 109
FootingAttrsMap ........................................................................................................................... 110
EquipmentFoundationAttrsMap .................................................................................................... 110
LeafPlateSystemAttrsMap ............................................................................................................ 111
PlanarPlatePartAttrsMap .............................................................................................................. 112
CurvedPlatePartAttrsMap ............................................................................................................. 112
LeafStiffenerSystemAttrsMap ....................................................................................................... 113
LinearStiffenerPartAttrsMap ......................................................................................................... 114
CurvedStiffenerPartAttrsMap ....................................................................................................... 115
LeafERSystemAttrsMap ............................................................................................................... 115
LinearERProfilePartAttrsMap ....................................................................................................... 116
CurvedERProfilePartAttrsMap ...................................................................................................... 117
LeafBeamSystemAttrsMap ........................................................................................................... 118
BeamPartAttrsMap ....................................................................................................................... 118
LinearSAStiffenerPartAttrsMap .................................................................................................... 119
CurvedSAStiffenerPartAttrsMap ................................................................................................... 120
HoleFittingAttrsMap ...................................................................................................................... 121
StructureGlobalsMap .................................................................................................................... 122
InsulationAttrMap .......................................................................................................................... 123
InsulationSpecAttrMap ................................................................................................................. 123
StructureMatSpecMap .................................................................................................................. 124
SmartItemMaterialMap ................................................................................................................. 125
StructPartNumbersMap ................................................................................................................ 125
StructClassAdditionalAttributes .................................................................................................... 126
Cross-Section Maps ..................................................................................................................... 127
Cardinal Point Maps ..................................................................................................................... 128
Marine Cross-Section Maps ......................................................................................................... 129
Load Point Maps ........................................................................................................................... 129
Supports Translation Maps ................................................................................................................. 130
SupportsClassMap ....................................................................................................................... 130
CHgrPipeSupport ......................................................................................................................... 131
CHgrDuctSupport ......................................................................................................................... 131
CHgrCableTraySupport ................................................................................................................ 132
CHgrDesignSupport ..................................................................................................................... 133
CHgrSupportComponent .............................................................................................................. 134
HgrSupportGlobals ....................................................................................................................... 135
SupportPartNumber...................................................................................................................... 136
SupportGTYPE ............................................................................................................................. 136
SupportUserAttributes .................................................................................................................. 137
Units Translation Maps ....................................................................................................................... 138
UnitsClassMap ............................................................................................................................. 138
UnitsGlobalsMap .......................................................................................................................... 138

Export to PDMS User's Guide 7


Contents

UnitsAdditionalAttributeMap ......................................................................................................... 139

Index ......................................................................................................................................................... 143

8 Export to PDMS User's Guide


Preface PDMS Guide
TM
This document describes how to export model data from Intergraph Smart 3D to Plant Design
Management Software (PDMS). The content includes a list of supported model object types,
known limitations associated with the export functionality, best practices, and other
administrative tasks.

Documentation Set
TM
Intergraph Smart 3D documentation is available as Adobe PDF files. The content is the same
as the online Help. To access these PDF documents, click Help > Printable Guides in the
software.
The documentation set is divided into four categories:
 Administrative guides contain information about installing, configuring, customizing, and
troubleshooting.
 User's guides provide command reference and how-to information for working in each task.
 Reference data guides define the reference data workbooks. Not all tasks have reference
data.
 ISOGEN guides.

Administrative Guides
TM
Intergraph Smart 3D Installation Guide - Provides instructions on installing and configuring the
software.
Project Management User's Guide - Provides instructions for setting up the databases, creating
permission groups, backing up and restoring project data, assigning access permissions to the
model, defining and managing locations for Global Workshare, and version upgrade.
Global Workshare Guide - Provides instructions for setting up the software and the databases to
work in a workshare environment.
Interference Checking Guide - Provides information on installing, configuring, and using the
interference detection service.
Integration Reference Guide - Provides information about installing, configuring, and using
Smart 3D in an integrated environment.
Interpreting Human Piping Specifications - Provides information about how to interpret human
piping specifications so that you can create the corresponding piping specification in the
software.
Export to PDMS - Provides information about how to export model data from Smart 3D to
PDMS. Specific guidelines relating to best practices and known limitations of the export
functionality are also included.
Point Cloud Reference - Provides information for referencing point cloud files provided by point
cloud vendors in Smart 3D.
Troubleshooting Reference Guide - Provides information on how to resolve errors that you might
encounter in the software by documenting troubleshooting tips, error messages, and To Do List
messages.
Plant Design System (PDS) Guide - Provides all information needed to use PDS with Smart 3D.
Topics include referencing active PDS projects in Smart 3D, exporting PDS data and importing
that data into Smart 3D, and converting PDS reference data to Smart 3D reference data.

Export to PDMS User's Guide 9


Preface PDMS Guide
TM
Intergraph Smart 3D Programmer's Guide - Provides information about custom commands,
naming rules, and symbol programming. If you install the Programming Resources, this
document is delivered to the [Product Folder]\Programming\Help folder.

User's Guides
Catalog User's Guide - Provides information about viewing, editing, and creating reference data
and select lists (codelists).
Common User's Guide - Provides information about defining workspaces, manipulating views,
and running reports.
Compartmentation User's Guide - Provides instruction for placing volume objects such as
compartments and zones in the model.
Electrical User's Guide - Provides information about routing electrical cable, cableway, cable
tray, and conduit.
Equipment and Furnishings User's Guide - Provides information about placing equipment.
Geometry Analysis and Repair User's Guide - Provides instructions for importing and exporting
model data, checking the data against a defined set of requirements, and repairing the data.
Grids User's Guide - Provides instructions for creating coordinate systems, elevation grid
planes, vertical grid planes, radial cylinders, radial planes, grid arcs, and grid lines.
Hangers and Supports User's Guide - Provides instructions on placing piping, duct, and
cableway supports in the model.
Hole Management User's Guide - Provides instructions for placing, reviewing, and approving
holes in a structure.
HVAC User's Guide - Provides instructions for routing HVAC duct.
Molded Forms User's Guide - Provides instructions for placing hull, bulkheads, major openings,
stiffeners, and other major structural components in the model.
Orthographic Drawings User's Guide - Provides information about creating and managing
orthographic drawings.
Piping Isometric Drawings User's Guide - Provides information about creating and managing
piping isometric drawings.
Piping User's Guide - Provides instructions for routing pipe and placing valves, taps, and pipe
joints.
Planning User's Guide - Provides instructions about defining the assembly hierarchy (production
bill of material) by creating blocks and assemblies and by specifying the assembly sequence.
Reports User's Guide - Provides information about creating and managing spreadsheet reports.
Space Management User's Guide - Provides instructions for placing space objects such as
areas, zones, interference volumes, and drawing volumes in the model.
Structural Analysis User's Guide - Provides instructions for defining loads, load cases, load
combinations, and the importing and exporting of analytical data.
Structural Detailing User's Guide - Provides instructions for creating, detailing, and maintaining
the structural members of a model.
Structural Manufacturing User's Guide - Provides instructions for creating and maintaining
manufacturing objects such as templates, jigs, and margins.
Structure User's Guide - Provides instructions for placing structural members, such as beams,
columns, slabs, openings, stairs, ladders, equipment foundations, and handrails.
Systems and Specifications User's Guide - Provides instructions for creating systems and
selecting the available specifications for each system type.

10 Export to PDMS User's Guide


Preface PDMS Guide

Reference Data Guides


2D Symbols User's Guide - Provides command reference information and procedural
instructions for creating 2D symbols used to represent collars, clips, profiles, brackets, and other
items.
2D Symbols Reference Data Guide - Provides information about the two-dimensional symbols
used in all tasks.
Compartmentation Reference Data Guide - Provides information about compartmentation
reference data.
Drawings and Reports Reference Data Guide - Provides information about reports reference
data.
Electrical Reference Data Guide - Provides information about electrical cable, cableway, cable
tray, and conduit reference data.
Electrical 3D Symbols Reference - Provides information about the cable tray and conduit 3D
symbols that are available.
Equipment and Furnishings Reference Data Guide - Provides information about equipment
reference data.
Equipment 3D Symbols Reference - Provides information about the equipment, equipment
component, design shapes, and design aides 3D symbols that are available.
Hangers and Supports Reference Data Guide - Provides information about hangers and
supports reference data.
Hangers and Supports 3D Symbols Reference - Provides information about the hanger and
support 3D symbols that are available.
Hangers and Supports SmartPart Symbols Reference - Provides information about the hanger
and support SmartPart symbols that are available.
Hole Management Reference Data Guide - Provides information about hole reference data.
HVAC Reference Data Guide - Provides information about HVAC reference data.
HVAC 3D Symbols Reference - Provides information about the HVAC 3D symbols that are
available.
Reference Data Guide - Provides instructions about the Bulkload utility, codelists, and the
reference data common to several disciplines.
Piping Reference Data Guide - Provides information about piping reference data including piping
specifications, piping specification rules, piping parts, and piping symbols.
Piping 3D Symbols Reference - Provides information about the piping 3D symbols that are
available.
Space Management Reference Data Guide - Provides information about space management
reference data.
Structure Reference Data Guide - Provides information about structural reference data.
Structure 3D Symbols Reference - Provides information about the stair, ladder, footings, and
equipment foundation 3D symbols that are available.
Structural Reference Data Overview - Provides an overview of the marine mode structural
reference data library.

ISOGEN Guides
Symbol Keys Reference Guide - Provides information about the symbol keys for isometric
drawings. This guide is from Alias, the makers of ISOGEN.

Export to PDMS User's Guide 11


Preface PDMS Guide

Documentation Comments
We welcome comments or suggestions about this documentation. You can send us an email at:
[email protected].
Documentation updates for supported software versions are available from eCustomer
https://crmweb.intergraph.com.

What's New in Export to PDMS


The following changes have been made to the Export to PDMS User's Guide.
Version 2014 (10.0)
 Export to PDMS functionality now supports the export of Equipment HVAC nozzles into
PDMS. For more information, see Exporting Model Data to PDMS (on page 13) and
CPHVACNozzleMap (on page 57). (P3 CP:193940)
 Export to PDMS functionality is extended to support Smart 3D Electrical data to PDMS. For
more information, see Exporting Model Data to PDMS (on page 13) and
ElectricalComponentSPREFMap (on page 52). (P2 CP:173766)
 A new .INI option, CreatePDMSLogFile, has been added that can generate a log file during
import in PDMS. For more information, see PDMS Export Initialization File Options (on page
23). (CP:20125)
 Export to PDMS functionality can now override the exported object data while re-importing
the datal into PDMS so that you do not need to delete the imported data from PDMS during
re-import. This applies to graphical data and property data. (P3 CP:201256)
 Export to PDMS functionality now uses End Preparation and Pressure Rating in a
combined string to map to the connection type in PDMS. The SP3DEndPreparation attribute
has been replaced with SP3DEndConnection. For more information, see HVACGlobalsMap
(on page 83), and PipingGlobalsMap (on page 90). (CP:214678)
 Export to PDMS functionality option can now map a component of one Smart 3D
specification with a different specification component of PDMS. (CP:204831)
 Export to PDMS functionality CreateHierarchy.ini option can now create the same hierarchy
in PDMS through DATAL files. For more information, see PDMS Export Initialization File
Options (on page 23). (P3 CP:195552)
 Export to PDMS functionality can now create multiple sites in PDMS using the
CreateMultipleSites attribute. For more information, see PDMS Export Initialization File
Options (on page 23). (P3 CP:213303)
 The enhanced Validation tool can now validate the missing mapping for electrical objects.
For more information, see PDMS Export Validation (on page 31). (CP:20914)
 Export to PDMS functionality can now export all Electrical data to PDMS. For more
information, see Exporting Model Data to PDMS (on page 13). (P3 CP:173766)
 Export to PDMS functionality now has a progress bar on the Export command to show the
real-time export progress. (P3 CP:204826)
 Added steps for using labels to map properties of related objects. For more information, see
Mapping Tips (on page 43).
 The DumpUnitsToDatal option has been added to the PDMSExportTranslator.ini file. You
can use this option to write units for all the values being written to the datal file. For more
information, see PDMS Export Initialization File Options (on page 23).

12 Export to PDMS User's Guide


Exporting Model Data to PDMS

SECTION 1

Exporting Model Data to PDMS


You can export equipment, piping, HVAC, hangers and supports, electrical, and structure model
TM
data from Intergraph Smart 3D that can then be imported into PDMS. The software uses the
File > Export > PDMS Datal Export > Export Model command to create datal files that are
subsequently used by PDMS.
The Export to PDMS functionality needs a S3X license key installed on the License
server.
The transfer of Smart 3D model data is a multi-step operation:
1. Ensure that the Smart 3D and PDMS catalogs are set up properly. For more information,
see Set up the PDMS and Smart 3D catalogs (on page 20).
2. Edit the options in the delivered initialization file to define the parameters used in the export
process. For more information about defining these parameters, see Configure the PDMS
export initialization file (on page 23).
3. Edit the mapping workbook to reflect the customizations that you have made to the Smart
3D object properties. For more information about the translation maps delivered with the
software, see Appendix: Export to PDMS Workbook (on page 45).
4. Use the PDMS Export Validation command to validate the mapping details that you have
defined. For more information, see PDMS Export Validation (on page 31).
5. Export the model data using the File > Export > PDMS Datal Export > Export Model
command in Smart 3D. For more information, see Export Model (on page 36).

Supported Object Types


Not all model data can be exported to PDMS. The following tables list the Smart 3D object
types, by discipline, that are currently supported for export by the software.
Equipment Objects:

Smart 3D Object Type PDMS Object Type Export Options


Catalog equipment Standard equipment  Mapping
 Breaking into primitives
Design equipment Design equipment Breaking into primitives
Catalog equipment component Sub-equipment Breaking into primitives
Design equipment component Sub-equipment Breaking into primitives
Shape Primitive  Mapping
 Breaking into primitives
Imported shape from SAT or Design equipment Breaking into primitives
DGN files
Design solid Primitive Breaking into primitives
Pipe nozzle Nozzle Mapping

Export to PDMS User's Guide 13


Exporting Model Data to PDMS

Smart 3D Object Type PDMS Object Type Export Options


HVAC nozzle Nozzle Mapping
Conduit nozzle Nozzle Mapping
CableTray nozzle Nozzle Mapping

Piping Objects:

Smart 3D Object Type PDMS Object Type Comments


Pipeline system Pipe The specification attribute on the
PDMS pipe object is controlled
by the PipelineSpec option in
the PDMSExportTranslator.ini
file.
Pipe run Branch It is not necessary for both
definitions to match exactly
because a Smart 3D pipe run
cannot contain components with
multiple diameters, whereas the
PDMS branch can. The
MergeSP3DRuns option in the
PDMSExportTranslator.ini file
combines all of the pipe runs
under a Pipeline system and
splits them into appropriate
PDMS branches. Consequently,
pipe run names in Smart 3D and
branch names in PDMS differ.
Piping component Relevant object in The appropriate component is
PDMS based on created based on the mapped
GType GType of the component.
Gasket Gasket Gasket dimensions in PDMS
should match those that are
present in Smart 3D; otherwise,
the isometric drawings
generated from PDMS may fail.
Pipe support (logical) Attachment Pipe supports from Smart 3D
are created as attachments
which appear in the isometric
drawings obtained from PDMS.
Pipe bend Bend Pipe bends from Smart 3D are
exported as bend objects.

14 Export to PDMS User's Guide


Exporting Model Data to PDMS

Smart 3D Object Type PDMS Object Type Export Options


Underground and sanitary FTUBE Underground and sanitary
piping piping; that is, piping that is
plain-ended, is exported as
FTUBE from Smart 3D. The
relevant FTUBE components
must be created in the PDMS
catalog and mapped
appropriately.
In addition to the piping object types listed in the above table, the necessary PML
commands are written in the data file to establish connectivity of piping with equipment nozzles
and the interconnectivity between branches.
Structure Objects:

Smart 3D Object Type PDMS Object Type Comments


 Linear member part  Section  PNODE, PJOINT,
 Curved member part  Generic Section SNODE, SJOINT are
created.
 PNODE, PJOINT,
JLDATUM, PLDATUM,
FIXING are created.
Connections between the
SECTION and JOINTS are
written to the PDMS data file.
Openings on slab Negative extrusion Openings on slab are exported
as a negative extrusion under
the FLOOR element.
Slab Floor

Stair, ladder, handrail Structure The software creates the


appropriate primitives in
PDMS during export.
Equipment foundation, footing Structure The software creates the
appropriate primitives in
PDMS during export.
Rectangular grid Section
Assembly connection
components:  Panel
 Custom plate part  Negative
 Cuts on member part Primitives
Insulation on member part Fitting The software optionally uses
the mapping file or creates the
appropriate primitives in
PDMS during export.

Export to PDMS User's Guide 15


Exporting Model Data to PDMS

Smart 3D Object Type PDMS Object Type Export Options


Openings, trim on member Negative Primitives
part
Plate part: The software creates the
 Planar  Panel appropriate primitives in
PDMS during export.
 Curved  Sub-structure
Profile part: All stiffener, edge
 Linear  SCTN reinforcement, and beam parts
are profile parts.
 Curved  GENSEC
For twisted profile parts, the
 Twisted  SUBSTRUCTURE
part is exported by breaking it
into planes.
Openings on plate Negative extrusion Openings on plate are
exported as a negative
extrusion under the PANEL
element.
Built-up member components: Structure: The software creates the
 Planar plate part  Panel fitting appropriate primitives in
PDMS during export.
 Curved plate part  Sub-structure
Hole fittings: The software creates the
 Planar plate part  Panel fitting appropriate primitives in
PDMS during export.
 Curved plate part  Sub-structure

Hangers and Supports Objects

Smart 3D Object Type PDMS Object Type Comments


Standard support components  PCLAMP  Pipe clamps in Smart 3D are
 HELEMENT created as PCLAMP.
 SCLAMP  Structure clamps in Smart
3D are created as SCALMP.
 Other components are
created as HELEMENT.
Design support components  PCLAMP  Pipe clamps in Smart 3D are
 HELEMENT created as PCLAMP.
 SCLAMP  Structure clamps in Smart
3D are created as SCALMP.
 Other components are
created as HELEMENT.

16 Export to PDMS User's Guide


Exporting Model Data to PDMS

HVAC Objects

Smart 3D Object Type PDMS Object Type Comments


Ducting system HVAC The specification attribute on the
PDMS HVAC object is controlled
by the HVACSpec option in the
PDMSExportTranslator.ini file.
Generic system HVAC The specification attribute on the
PDMS HVAC object is controlled
by the HVACSpec option in the
PDMSExportTranslator.ini file as
there is no specification property
on the Generic system in Smart
3D.
Duct run BRANCH It is not necessary for both
definitions to match exactly
because a Smart 3D duct run
cannot contain run change
components only at the ends of
the run, whereas the PDMS
branch can contain similar
components in the middle of the
branch. The
MergeSP3DDuctRuns option in
the PDMSExportTranslator.ini
file combines all of the duct runs
under a Ducting system/Generic
system and splits them into
appropriate PDMS branches.
Consequently, duct run names in
Smart 3D differ from branch
names in PDMS.
Duct component Relevant object in The appropriate component is
PDMS based on created based on the mapped
GType GType of the component.
Gasket GASKET Gasket dimensions in PDMS
should match those that are
present in Smart 3D. Otherwise,
the isometric drawings
generated from PDMS may fail.
Duct bend BEND Smart 3D duct bends are
exported as bend objects in
PDMS.
Duct support ATTACHMENT Smart 3D duct supports are
created as attachments which
appear in the isometric drawings
obtained from PDMS.

Export to PDMS User's Guide 17


Exporting Model Data to PDMS

Smart 3D Object Type PDMS Object Type Export Options


Design support ATTACHMENT Smart 3D design supports are
created as attachments which
appear in the isometric drawings
obtained from PDMS.

Electrical Objects

Smart 3D Object Type PDMS Object Export Options


Type
Electrical system PIPE The specification attribute on the
PDMS electrical object is
controlled by the Electrical Spec
option in the
PDMSExportTranslator.ini.
Cable ways BRANCH
Electrical supports ATTACHMENT Smart 3D electrical supports are
created as attachments that
appear in the drawings extracted
from PDMS.
Conduit system PIPE The specification attribute on the
PDMS electrical object is
controlled by the Electrical Spec
option in the
PDMSExportTranslator.ini file.
Generic system PIPE The specification attribute on the
PDMS electrical object is
controlled by the Electrical Spec
option in the
PDMSExportTranslator.ini file
because there is no specification
property on the Electrical system
in Smart 3D.
Conduit run BRANCH
Conduit component ELECCOMP The appropriate component is
created based on the mapped
GType of the component.
Cable tray component ELECCOMP The appropriate component is
created based on the mapped
GType of the component.

18 Export to PDMS User's Guide


Exporting Model Data to PDMS

Best Practices
During export, if the software encounters a name that does not meet one of these conventions, it
modifies the name before writing it to the datal file, resulting in mismatched object names
between the two models. As such, Intergraph recommends that you use the following naming
conventions when modeling in Smart 3D:
 Create a unique name for each modeled object so that no duplicates exist.
 Make sure object names contain no spaces.
 Make sure object names do not exceed 50 characters.

Limitations
The following limitations are known to exist when importing piping, equipment, HVAC, hangers
and supports, structure, and electrical model data to PDMS from Smart 3D:
Global:
 When exporting a hierarchy, a recursive user-defined element type cannot be created in
PDMS. For example, if a piping system is created once, it can neither be its own parent or
child, but it can be a sibling.
Equipment Models:
 If the catalog is not set up or if mapping is not provided for an object, the software breaks
the object into GTypes and objects in exports them as primitives. As such, the equipment
item may be difficult to modify after it is imported into PDMS.
 Imported shapes are placed under a sub-equipment node, but they should be treated as
primitives because they are shapes in Smart 3D.
 In the current release of the software, the catalog equipment component is transferred only
through GTypes. Mapping is not supported.
Piping Models:
 Because there is no concept of on-the-fly specialty components and on-the-fly instruments
in PDMS, these Smart 3D piping objects must be created as explicit components in PDMS.
It is assumed that there is one on-the-fly specialty component or instrument for every
different end preparation, pressure rating, schedule thickness, and end standard.
 Supports are exported only as logical supports and appear as attachments in the PDMS
piping isometric drawing output.
 No bolt sets or washers from the model are transferred from Smart 3D to PDMS. These are
considered implied items and the catalog should be set up properly before the export
process is started. Bolt lengths, bolt diameters, and number of bolts should match the Smart
3D data.
Structure Models:
 The software sets the PLine attribute for JLine and MLine on sections and joints to NA
(Neutral Axis) by default.
 Cuts, features on members, and objects created during assembly connections are exported
as fittings. Negative geometries are created for cuts, and panels are created for additional
objects.
Export using catalog joints is not supported in the current release of the software.
 The software breaks stair, ladder, handrail, footing, and equipment foundation objects into
GTypes and exports them as primitives under the STRUCTURE element.
 Curved plate parts on both plate systems and built-up members are exported as smaller
triangular planes which make-up the total curved surface.

Export to PDMS User's Guide 19


Exporting Model Data to PDMS

 The hole fitting object on the planar plate part is exported as a panel fitting under the PANEL
element (planar plate part). Curved plate parts are exported as SUBSTRUCTURE, because
the PANEL element is not created for a curved plate part.
 Openings, trim, corner, and end cut features on the profile part are not exported.
 Twisted stiffeners are exported by breaking the profile part into primitives and exporting
them under the SUBSTRUCTURE element.
Hanger and Support Models:
 If the catalog is not set up or if mapping is not provided for all hanger and support
Components present in Smart 3D, then the software breaks the object into GTypes and
exports them as primitives.
 Because the export of hanger and support model data is dependent on structure model
data, the structure model data must be imported into PDMS before the hanger and support
model data.
HVAC Models:
 Supports are exported only as logical supports and appear as attachments in the PDMS
isometric drawing output.
 No bolt sets or washers from the model are transferred from Smart 3D to PDMS. These are
considered implied items and the catalog should be set up properly before the export
process is started. Bolt lengths, bolt diameters, and number of bolts should match the Smart
3D data.
Electrical Models:
 If the catalog is not set up or if mapping is not provided for an object, the software breaks all
electrical objects into GTypes, and exports them as equipment objects for space reservation
purposes only. Consequently, an equipment item from PDMS can be difficult to modify after
it is imported.
 Imported geometries are placed under a sub-equipment node. The behavior of the imported
data can be correlated to equipment designs of electrical objects.

20 Export to PDMS User's Guide


Exporting Model Data to PDMS

Set up the PDMS and Smart 3D catalogs


Prior to exporting Smart 3D model data, a catalog with corresponding objects, parts, and
specifications must already exist in PDMS. You can generate the required piping catalogs in
Smart 3D and PDMS formats using Intergraph's materials management software, SmartPlant
Reference Data. For more information, see Generate catalog and reference data in Smart 3D
and PDMS formats for PDMS export (on page 36). For a successful export, ensure that the
PDMS catalog meets the criteria outlined below.

Equipment Model Data


 The PDMS catalog must contain the same equipment shapes and nozzles that exist in the
Smart 3D catalog.
 To export catalog equipment using a mapping file, the Smart 3D symbol definition template
must also be present in the PDMS catalog.
 To export nozzles, all nozzle data must exist in the PDMS catalog prior to export and must
match the nozzle data in the Smart 3D catalog.
 You must provide mapping information for any new shape. The shape in PDMS must be an
exact match of the shape in Smart 3D.

Piping Model Data


 All of the piping specifications in the PDMS catalog must also exist in the Smart 3D catalog
 All of the components used in a piping specification must be present in the PDMS catalog
and should match those in the Smart 3D catalog. Component properties and dimensional
data must also match between the two catalogs.
 All end preparations must be set up in the PDMS catalog.
 All of the piping specialties and instruments of both the catalog and on-the-fly types must be
set up in PDMS as either PCOMP or INST. Their dimensional data must match that of the
components in the Smart 3D catalog.
 All gaskets and welds with exact thickness must be set up and available in the PDMS
catalog.
 Insulation and tracing specifications must be set up the same in both catalogs.
 Bolt sets in the PDMS catalog must match those in the Smart 3D catalog. Any difference
between these two sets of data adversely impact how bolts are reported in the isometric
drawing output. Bolt and washer model data are not exported to PDMS and are treated as
implied items by the export process.

HVAC Model Data


 All of the HVAC specifications in the PDMS catalog must also exist in the Smart 3D catalog.
 All of the components used in a HVAC specification must be present in the PDMS catalog
and should match those in the Smart 3D catalog. Component properties and dimensional
data must also match between the two catalogs.
 All end preparations must be set up in the PDMS catalog.
 All gaskets and welds with exact thickness must be set up and available in the PDMS
catalog.
 Insulation and tracing specifications must be set up the same in both catalogs.

Export to PDMS User's Guide 21


Exporting Model Data to PDMS

 Bolt sets in the PDMS catalog must match those in the Smart 3D catalog. Any difference
between these two sets of data adversely impacts how bolts are reported in the isometric
drawing output. Bolt and washer model data are not exported to PDMS and are treated as
implied items by the export process.

Structure Model Data


 To export members, the dimensions, properties, and cardinal points of the cross-section in
the PDMS catalog must match those in the Smart 3D catalog.
 To export insulation on members using mapping, an exact match for the encasement must
be present in the PDMS catalog. For each cross-section type, a corresponding PDMS
catalog fitting must be present; the geometry of the catalog fitting should match exactly with
the insulation encasement for that particular cross-section type.
 To export the material property on a structure object, each material in the Smart 3D catalog
must be mapped to appropriate material in the PDMS catalog.
 To export a material property, you must provide mapping for any new structural catalog
object in Smart 3D. Mapping for default supported objects, such as stairs, ladders, handrails,
footings, equipment foundations, and hole fittings, is already provided.
 To export profile parts, the dimensions, properties, and cardinal points (with Load Points in
Smart 3D) of the cross section in the PDMS catalog must match those in the Smart 3D
catalog.

Hangers and Support Model Data


 To transfer hangers and supports by mapping, the PDMS catalog should be exactly the
same as the Smart 3D catalog. Otherwise there are mismatches in the geometry and
orientation of the transferred support components.

Electrical Model Data


 All of the electrical specifications in the PDMS catalog must also exist in the Smart 3D
catalog.
 All of the components used in an electrical specification must be present in the PDMS
catalog and should match those in the Smart 3D catalog. Component properties and
dimensional data must also match between the two catalogs.
 Insulation and tracing specifications must be the same in both catalogs.
See also
Project Creation Estimates (on page 43)

22 Export to PDMS User's Guide


Exporting Model Data to PDMS

Configure the PDMS export initialization file


The PDMSExportTranslator.ini file controls the export of Smart 3D model data to PDMS. You
can modify the default values to suit your specific project needs.
1. In Windows Explorer, browse to [Product
Folder]\3DRefData\SharedContent\Data\Translators\S3DPDMSExport.
2. Open the PDMSExportTranslator.ini file and modify the options as needed.
3. Save your changes.
SharedContent is delivered in reference data setup.

PDMS Export Initialization File Options


The PDMSExportTranslator.ini file is divided into several sections: Globals, Equipment, Piping,
Structure, Hangers and Supports, Electrical, and HVAC. Each section contains a specific set of
default options that are used during export.

Globals
DeveloperLogging - Creates the end-user or detailed developer log file.
 0 - Create end-user logging. This is the default value.
 1 - Create developer logging.
Precision - Provides the precision for rounding position coordinates.
 Value - Type the number of digits to round the position coordinates, ideally in range 0 to 6.
The default value is 3.
CreatePDMSLogFile - Generates an error log during import into PDMS.
 0 - Suppress generation of an error log file.
 1 - Generate an error log file. The log file is saved to the PDMS Error Log file path, which is
created in the %PDMSUSER% file path on the PDMS computer. This is the default value.
ExportOption - Determines which objects are written to a datal file.
 ALL - Write all objects in the selected filter to the datal file. This is the default value.
 MODIFIED - Write only the modified objects in the selected filter to the datal file.
CreateHierarchy - Controls the hierarchy information written to a datal file.
 0 - Create a single site, defined as Smart 3D ProjectConfigRoot.
 1 - Export the Smart 3D Hierarchy to Smart 3D ProjectConfigRoot, and export the ZONE in
PDMS as a child to Smart 3D ProjectConfigRoot. This is the default value.
CreateMultipleSites - Controls the creation of multiple sites in PDMS.
 0 - Create a single site, defined as Smart 3D ProjectConfigRoot.
 1 - Create multiple sites, with SITE in PDMS defined as the parent and its object defined as
ZONE from Smart 3D.
When CreateHierarchy is set to 1, CreateMultipleSites is ignored.
DumpUnitstoDatal - Writes the units to the datal file.
 0 - Units are not dumped to the datal file. This is the default value.
 1 - All values are written to the datal file per the units specified in the mapping file.

Export to PDMS User's Guide 23


Exporting Model Data to PDMS

Equipment
UseMappingToCreateShapes - Determines whether shapes are exported through mapping or
by breaking them into GTypes and creating the appropriate primitives in PDMS.
 0 - Break shapes into GTypes and create appropriate primitives in PDMS. If any errors
occur, the software uses the mapping file as an alternative for creating corresponding
primitives. This is the default value.
 1 - Export shapes using the mapping file. If any mapping is missing for any shape, the
software breaks the shape into GTypes and creates the appropriate primitives in PDMS.
UseMappingToCreateCatalogEquipment - Determines whether catalog equipment is exported
through mapping or by breaking them into GTypes and creating the appropriate primitives in
PDMS.
 0 - Break catalog equipment into GTypes and create appropriate primitives in PDMS. If any
errors occur, the software uses the mapping file as an alternative for creating corresponding
equipment. This is the default value.
 1 - Export catalog equipment using the mapping file. If any mapping is missing for any
catalog equipment, the software breaks the catalog equipment into GTypes and creates the
appropriate primitives in PDMS.
DumpNozzleUnderSubEquipment - Determines whether a sub-equipment node is created in
the PDMS hierarchy for placement of equipment nozzles.
 0 - Suppress the creation of a sub-equipment node. All nozzles are placed under the
equipment node. This is the default value
 1 - Create a sub-equipment node, and place all nozzles under it.
DumpShapeUnderSubEquipment - Determines whether a sub-equipment node is created in
the PDMS hierarchy for placement of shapes equipment.
 0 - Suppress the creation of a sub-equipment node. All shapes are placed under the
equipment node. This is the default value.
 1 - Create a sub-equipment node, and place all shapes under it.
IgnoreIndependentPlane - Controls how independent planes are handles during export.
Independent planes are usually caps on projections, extra planes in equipment foundation, and
so on. These planes do not affect the graphical output, but they do appear as additional objects
in the PDMS workspace.
 0 - Process independent planes. This is the default value.
 1 - Ignore processing of independent planes.
SurfaceQualityForBSplineSurface - Surface quality for BSplineSurface.
 COARSE - Best performance with poor surface quality.
 MEDIUM COARSE - Better performance with moderate surface quality. This is the default
value.
 MEDIUM FINE - Better performance with improved surface quality.
 FINE - Poor performance with best surface quality.
ToleranceForPlanesHavingCurvedBoundaries - Controls how the software handles curved
boundaries during import. PDMS does not support planes with curved boundaries. During
export, these curved boundaries are approximated to small lines. By specifying the angle of arc,
you can approximate an arc to a line. The lesser the angle specified, the smoother the plane
boundary obtained in PDMS.
 Value - Type a number (angle in degrees) in range 5-30. The default value is 5.

24 Export to PDMS User's Guide


Exporting Model Data to PDMS

SurfaceQualityForBSPlineSurface - Controls the fineness and surface quality for complex


surfaces. Finer surface quality affects performance during export and import of the complex
surface.
 COARSE - Poor surface quality with best performance.
 MEDIUM_COARSE - Moderate surface quality with better performance. This is the default
value.
 MEDIUM_FINE - Better surface quality with moderate performance.
 FINE - Best surface quality with poor performance.
SurfaceQualityForDesignSolid - Controls the fineness and surface quality for design solids.
Finer surface quality affects performance during export and import of the complex surface.
 COARSE - Poor surface quality with best performance.
 MEDIUM_COARSE - Moderate surface quality with better performance. This is the default
value.
 MEDIUM_FINE - Better surface quality with moderate performance.
 FINE - Best surface quality with poor performance.
ExportSimpleGeometry - Controls if the geometry of the equipment is simplified and
transferred into PDMS.
 0 - Transfer equipment shapes as shown. This is the default value.
 1 - Simplify equipment shapes before transfer. The holes on complex surfaces are removed
and the outer boundaries are truncated to straight lines or a singular circular arc. Holes are
removed from cones, cylinders, torus, spheres, and plane objects in Smart 3D equipment.
MaximumEdgeLengthForComplexSurfacesRangeBox - Defines the maximum edge length
for the range box of the complex geometry that cannot be simplified for export to PDMS. This
option is useful for transferring complex geometries, such as b-spline surfaces, ruled surfaces,
non-linear and non-orthogonal projections, and complex revolutions. If the value is large, no
complex geometry is transferred. ExportSimpleGeometry must be set to 1.
 Value - Type a number (in mm) with minimum value 10. The default value is 25.

Piping
MergeSP3DRuns - Controls how branches are exported to PDMS.
 0 - Create one branch in PDMS per Smart 3D pipe run.
 1 - Merge Smart 3D pipe runs, and export as per PDMS's definition. This is the default
value.
PipelineSpec - Controls what value is output in the datal file for the PSPE attribute on the
pipeline.
 MAX_OCCURRENCES - Output the specification used by the maximum number of runs
under the pipeline. This is the default value.
 FIRST_OCCURENCES - Output the specification used by the first run under the pipeline.
 MAPPING - Output the specification using the mapping file (either ProgID or Label).
GenerateSeparateFileForPipingConnections - Controls if a separate file is written for piping
connections in the model. After all piping data is imported into PDMS, these connection files can
be collected and then run to create connections. This reduces the effort spent in the filter
creation stage so that lesser dependencies are created.
 0 - Write connections in the same file as the output file.
 1 - Write connections in a separate file as the output file. Names of the new files are
appended with "_PipingConnections." This is the default value.

Export to PDMS User's Guide 25


Exporting Model Data to PDMS

Structure
TransferInsulationAsGTypes - Determines whether insulation on members is exported
through mapping or by breaking into GTypes and creating appropriate primitives in PDMS.
 0 - Transfer insulation on members as mapped objects.
 1 - Transfer insulation on members as GTypes. This is the default value.
SurfaceQualityForBSplineSurface - Surface quality for BSplineSurface.
 COARSE - Best performance with poor surface quality.
 MEDIUM COARSE - Better performance with moderate surface quality. This is the default
value.
 MEDIUM FINE - Better performance with improved surface quality.
 FINE - Poor performance with best surface quality.
ToleranceForPlanesHavingCurvedBoundaries - Controls how the software handles curved
boundaries during import. PDMS does not support planes with curved boundaries. During
export, these curved boundaries are approximated to mall lines. By specifying the angle of arc,
you can approximate an arc to a line. The lesser the angle specified, the smoother the plane
boundary obtained in PDMS.
 Value - Type a number (angle in degrees) in range 5-30. The default value is 5.
IgnoreIndependentPlane - Controls how independent planes are handled during export.
Independent planes are usually caps on projections, extra planes in equipment foundation, and
so on. These planes do not affect the graphical output, but they do appear as additional objects
in the PDMS workspace.
 0 - Process independent planes. This is the default value.
 1 - Ignore processing of independent planes.
SurfaceQualityForCurvedPlate - Surface quality for CurvedPlates.
 COARSE - Best performance with poor surface quality.
 MEDIUM_COARSE - Better performance with moderate surface quality. This is the default
value
 MEDIUM_FINE - Better performance with improved surface quality.
 FINE - Poor performance with best surface quality.
ExportTwistedStiffeners - Export the twisted stiffener parts in the Smart 3D models as
primitives.
 0 - Do not export twisted stiffener parts.
 1 - Export twisted stiffener parts as GTypes. This is the default value.
ToleranceForMemberCutGeometry - Provides a balance between performance and the quality
of the imported model. When cut geometry is encountered during export, the software breaks
the surfaces into small planes, which are used to create a negative solid polyhedron. The more
planes that are created, the smoother the surface, which can adversely impact the amount of
time required to import the model into PDMS. You can adjust the value as necessary to
compromise between performance and smoothness.
 Value - Type a number in range 5 to 70. The default value is 5.

26 Export to PDMS User's Guide


Exporting Model Data to PDMS

SurfaceQualityForBSPlineSurface - Controls the fineness and surface quality for complex


surfaces. Finer surface quality affects performance during export and import of the complex
surface.
 COARSE - Poor surface quality with best performance.
 MEDIUM_COARSE - Moderate surface quality with better performance. This is the default
value.
 MEDIUM_FINE - Better surface quality with moderate performance.
 FINE - Best surface quality with poor performance.
SurfaceQualityForCurvedPlate - Controls the fineness and surface quality for curved plates
and twisted stiffeners. Finer surface quality affects performance during export and import of the
complex surface.
 COARSE - Poor surface quality with best performance.
 MEDIUM_COARSE - Moderate surface quality with better performance. This is the default
value.
 MEDIUM_FINE - Better surface quality with moderate performance.
 FINE - Best surface quality with poor performance.
GenerateSeparateFileForStructuralConnections - Controls if a separate file is written for
connections for structural members and joints in the model. After all structural data is imported
into PDMS, these connection files can be collected and then run to create connections. This
reduces the effort spent in the filter creation stage so that lesser dependencies are created.
 0 - Write connections in the same file as the output file.
 1 - Write connections in a separate file from the output file. Names of the new files are
appended with "_StructuralConnections." This is the default value.
ExportSimpleGeometry - Controls if the geometry of the structure, such as stairs, ladders,
handrails, equipment foundations and footings, is simplified and transferred into PDMS.
 0 - Transfer equipment shapes as shown. This is the default value.
 1 - Simplify equipment shapes before transfer. The holes on complex surfaces are removed
and the outer boundaries are truncated to straight lines or a singular circular arc. Holes are
removed from cones, cylinders, torus, spheres, and plane objects in Smart 3D equipment.
MaximumEdgeLengthForComplexSurfacesRangeBox - Defines the maximum edge length
for the range box of the complex geometry that cannot be simplified for export to PDMS. This
option is useful for transferring complex geometries, such as b-spline surfaces, ruled surfaces,
non-linear and non-orthogonal projections, and complex revolutions. If the value is large, no
complex geometry is transferred. ExportSimpleGeometry must be set to 1.
 Value - Type a number (in mm) with minimum value 10. The default value is 25.

Supports
UseMappingToCreateSupports - Determines whether supports need to be exported through
mapping or through breaking up into GTypes and creating appropriate primitives in PDMS.
 0 - Transfer supports through GTypes. This is the default value.
 1 - Transfer supports through mapping.
SurfaceQualityForBSplineSurface - Surface quality for BSplineSurface.
 COARSE - Best performance with poor surface quality.
 MEDIUM COARSE - Better performance with moderate surface quality. This is the default
value.
 MEDIUM FINE - Better performance with improved surface quality.
 FINE - Poor performance with best surface quality.

Export to PDMS User's Guide 27


Exporting Model Data to PDMS

ToleranceForPlanesHavingCurvedBoundaries - Controls how the software handles curved


boundaries during import. PDMS does not support planes with curved boundaries. During
export, these curved boundaries are approximated to mall lines. By specifying the angle of arc,
you can approximate an arc to a line. The lesser the angle specified, the smoother the plane
boundary obtained in PDMS.
 Value - Type a number (angle in degrees) in range 5-30. The default value is 30.
GenerateSeparateFileForSupportsConnections - Determines whether support connections
need to be exported through mapping or by breaking them into GTypes and creating appropriate
primitives in PDMS.
 0 - Transfer supports connections in the same data file in which Supports are transferred.
 1 - Transfer supports connections in a separate file. This is the default value.
ExportSimpleGeometry - Controls if the geometry of a support is simplified and transferred into
PDMS.
 0 - Transfer supports as shown. This is the default value.
 1 - Simplify supports before transfer. The holes on complex surfaces are removed and the
outer boundaries are truncated to straight lines or a singular circular arc.
MaximumEdgeLengthForComplexSurfacesRangeBox - Defines the maximum edge length
for the range box of the complex geometry that cannot be simplified for export to PDMS. This
option is useful for transferring complex geometries, such as b-spline surfaces, ruled surfaces,
non-linear and non-orthogonal projections, and complex revolutions. If the value is large, no
complex geometry is transferred. ExportSimpleGeometry must be set to 1.
 Value - Type a number (in mm) with minimum value 10. The default value is 25.

HVAC
MergeSP3DDuctRuns - Controls how branches are exported to PDMS.
 0 - Create one branch in PDMS per Smart 3D duct run.
 1 - Merge Smart 3D duct runs, and export as per PDMS's definition. This is the default
value.
HVACSpec- Controls what value is output in the data file for the PSPE attribute on the HVAC.
 MAX_OCCURRENCES - Output the specification used by the maximum number of runs
under the DuctingSystem/GenericSystem. This is the default value.
 FIRST_OCCURRENCE - Output the specification used by the first run under the
DuctingSystem/GenericSystem.
 MAPPING - Output the specification using the mapping file (either ProgID or Label).
GenerateSeparateFileForHVACConnections - Controls whether to write connection
information in the same data file where model data is written or in a separate file.
 0 - Write HVAC connection information in the same data file where model data is written.
 1 - Write HVAC connection information in a separate data file. This is the default value.

28 Export to PDMS User's Guide


Exporting Model Data to PDMS

Electrical
TransferAsGTypes - Determines whether electrical cable trays and conduit runs are transferred
using mapping or as GTypes.
 0 - Transfer using mapping.
 1 - Transfer as GTypes. EQUIPMENT is created for the run, and the parts are dumped as
SUBEQUIPMENT. This is the default value.
DumpRangeBox - Determines which object information is dumped.
 0 - Dump the true geometry of the object.
 1 - Dump the range box data of the object. This is the default value.
GenerateSeparateFileForElectricalConnections - Controls if a separate file is written for
electrical connections in the model. After all electrical data is imported into PDMS, these
connection files can be collected and then run to create connections. This reduces the effort
spent in the filter creation stage so that fewer dependencies are created.
 0 - Write connections in the same file as the output file.
 1 - Write connections in a separate file as the output file. Names of the new files are
appended with "_ElectricalConnections." This is the default value.
ElectricalSpec- Controls what value is output in the data file for the PSPE attribute on Electrical
runs.
 MAX_OCCURRENCES - Output the specification used by the maximum number of runs
under the DuctingSystem. This is the default value.
 FIRST_OCCURRENCE - Output the specification used by the first run under the
DuctingSystem.
 MAPPING - Output the specification using the mapping file (either ProgID or Label).
IgnoreIndependentPlane - Controls how independent planes are handles during export.
Independent planes are usually caps on projections, extra planes in equipment foundation, and
so on. These planes do not affect the graphical output, but they do appear as additional objects
in the PDMS workspace.
 0 - Process independent planes. This is the default value.
 1 - Ignore processing of independent planes.
SurfaceQualityForBSplineSurface - Surface quality for BSplineSurface.
 COARSE - Best performance with poor surface quality.
 MEDIUM COARSE - Better performance with moderate surface quality. This is the default
value.
 MEDIUM FINE - Better performance with improved surface quality.
 FINE - Poor performance with best surface quality.
ToleranceForPlanesHavingCurvedBoundaries - Controls how the software handles curved
boundaries during import. PDMS does not support planes with curved boundaries. During
export, these curved boundaries are approximated to small lines. By specifying the angle of arc,
you can approximate an arc to a line. The lesser the angle specified, the smoother the plane
boundary obtained in PDMS.
 Value - Type a number (angle in degrees) in range 5-30. The default value is 5.

Export to PDMS User's Guide 29


Exporting Model Data to PDMS

SurfaceQualityForBSPlineSurface - Controls the fineness and surface quality for complex


surfaces. Finer surface quality affects performance during export and import of the complex
surface.
 COARSE - Poor surface quality with best performance.
 MEDIUM_COARSE - Moderate surface quality with better performance. This is the default
value.
 MEDIUM_FINE - Better surface quality with moderate performance.
 FINE - Best surface quality with poor performance.
ExportSimpleGeometry - Controls if the geometry of a support is simplified and transferred into
PDMS.
 0 - Transfer supports as shown. This is the default value.
 1 - Simplify supports before transfer. The holes on complex surfaces are removed and the
outer boundaries are truncated to straight lines or a singular circular arc.
MaximumEdgeLengthForComplexSurfacesRangeBox - Defines the maximum edge length
for the range box of the complex geometry that cannot be simplified for export to PDMS. This
option is useful for transferring complex geometries, such as b-spline surfaces, ruled surfaces,
non-linear and non-orthogonal projections, and complex revolutions. If the value is large, no
complex geometry is transferred. ExportSimpleGeometry must be set to 1.
 Value - Type a number (in mm) with minimum value 10. The default value is 25.

30 Export to PDMS User's Guide


Exporting Model Data to PDMS

PDMS Export Validation


With the File > Export > PDMS Datal Export > PDMS Export Validation command, you can
validate the mapping data that you have defined in the S3DPDMSExportMapping.xls
workbook. The command uses a specified set of user-defined criteria to locate missing mapping
details, and then updates the mapping file as follows:
 A sheet named Smart 3D Objects-Missing Mapping is created in the mapping file. This
sheet lists the missing mapping information.
 Individual worksheets are updated with missing mapping information. For easy identification,
updated cells are highlighted in red.
The results of the validation process are also written to a log file.
See Also
PDMS Export Validation Dialog Box (on page 32)

Validate mapping details


Before running the PDMS Export Validation command, close the mapping
workbook that you are attempting to validate.
1. Click File > Export > PDMS Datal Export > PDMS Export Validation.
2. Click Browse , and select the necessary filter. By default, the software displays the
session file's active filter.
3. Select Validate from mapping file.
4. In the Validation criteria list, select the object types whose mapping is to be validated. You
must select at least one criterion from the list.
5. In the Log file details box, type the name and folder location of the log file.
6. Click Validate.

 By default, the validation tool updates the mapping file located in [Product
Folder]\3DRefData\SharedContent\Data\Translators\S3DPDMSExport. To specify a
mapping file in a different location, select Specify alternative location and then type the full
path location and file name of the appropriate file in the Datal/Mapping file to validate box.
 If the mapping file is read-only, the software creates a copy of the mapping file with the
name <Mapping file name>_COPY.xls and saves it in the same location as the original
mapping file. The software updates the copy of the mapping file with the missing mapping
details.

Export to PDMS User's Guide 31


Exporting Model Data to PDMS

PDMS Export Validation Dialog Box


Filter - Displays the active filter of the session file. Click Browse to navigate to and select
a different filter.
Target (PDMS) object selection criteria - Specify the selection criteria. The current release of
the software supports only the Validate from mapping file option.
Specify alternative location - Allows you to specify a mapping file other than the one in the
default location. By default, the software updates the mapping file located in [Product
Folder]SharedContent\Data\Translators\S3DPDMSExport. To specify a different location, select
this option and then type the full path location and file name in the Datal/Mapping file path box.
Datal/Mapping file path - Type the full path location and name of the mapping file to be
validated. This option is available only if you select Specify alternative location. Updating datal
files is not supported in the current release of the software.
Validation criteria - Select the Smart 3D objects whose mapping you want to validate. Objects
are listed by discipline. For each criterion that you select, the software validates the
corresponding worksheet in the mapping file. You must select at least one object in the
Validation criteria list.

Validation Criteria Details


Equipment Models
For more information about any of the equipment mapping sheets referenced in the
following rows, see Equipment Translation Maps (on page 52).
Reports missing mapping for pipe nozzle CATRef attributes in the
CPStraightNozzleCAtRefMap and CPElbowNozzleCAtRefMap
Nozzles sheets.
Reports missing mapping for HVAC nozzle CATRef attributes in the
CPHvacNozzleCatRefMap sheet.
Reports missing mapping for PartNumber and TempPartNumber
Catalog equipment attributes in the PartNumberValueMap and the
DesParamAdditonalAttrMap sheets, respectively.
Reports missing mapping for ShapePartClass in the
Shapes
CPShapeValueMap sheet.

32 Export to PDMS User's Guide


Exporting Model Data to PDMS

Validation Criteria Details


Piping Models
For more information about any of the piping mapping sheets referenced in the
following rows, see Piping Translation Maps (on page 87).
Reports missing mapping for the following:
 Smart 3D part identifiers for pipe parts in the
SP3DPartIdentifierMap sheet.
 Smart 3D catalog components in the
CatalogComponentSPREFMap sheet.
 Smart 3D catalog specialty items in the
Components CatalogSpecialtySPREFMap sheet.
 Smart 3D catalog instrument items in the
CatalogInstrumentSPREFMap sheet.
 Smart 3D on-the-fly specialty items in the
OnFlySpecialitySPREFMap sheet.
 Smart 3D on-the-fly instrument items in the
OnFlyInstrumentSPREFMap sheet.
Reports missing mapping for pipe run specification in the
Specification
PipeRunSpecMap sheet.
Reports missing mapping for the end connection of pipe parts in the
End Connection
PipingEndConnectionMap sheet.
Reports missing mapping for stock parts SpecRef attributes in the
Stock parts
CatalogComponentSPREFMap sheet.
Reports missing mapping for gaskets SpecRef attributes in the
Connections
CatalogComponentSPREFMap sheet.
Reports missing mapping for pipe supports in the
Supports
CatalogComponentSPREFMap sheet.
Structure Models
For more information about any of the structure mapping sheets referenced in the
following rows, see Structure Translation Maps (on page 99).
Reports missing insulation on member parts in the
Fire proofing InsulationAttrMap sheet. The tool also reports the missing
insulation SpecRef attributes in the InsulationSpecAttrMap sheet.
Reports missing mapping for cross-section of member parts in the
Cross sections
StrucClassAdditionalAttributes sheet.

Reports missing mapping for materials for objects such as plate


Materials
parts and hole fittings in the StructureMatSpecMap sheet.

Reports missing mapping for cross section of profile parts in the


MarineCrosssections
MarineCSAdditionalAttributes sheet.

Export to PDMS User's Guide 33


Exporting Model Data to PDMS

Validation Criteria Details


HVAC Models
For more information about any of the HVAC mapping sheets referenced in the
following rows, see HVAC Translation Maps (on page 77).
Reports missing mapping for the following:
 Smart 3D part identifiers for HVAC parts in the
Components HVACPartIdentifierMap sheet.
 Smart 3D catalog components in the
HVACComponentSPREFMap sheet.
Reports missing mapping for duct run specifications in the
Specification
DuctRunSpecMap sheet.
Reports missing mapping for the end connection of duct parts in the
EndConnection
HVACEndConnectionMap sheet.
Reports missing mapping for duct parts SpecRef attributes in the
DuctParts
HVACComponentSPREFMap sheet.
Reports missing mapping for gaskets SpecRef attributes in the
Connections
HVACComponentSPREFMap sheet.
Reports missing mapping for duct/design supports in the
Supports
HVACComponentsSPREFMap sheet.
Hangers and Supports Models
For more information about any of the piping mapping sheets referenced in the
following rows, see Supports Translation Maps (on page 130).
 Reports missing PartNumber mapping for support components
in the SupportPartNumber sheet.
Supports
 Reports the missing mapping for a support component's GType
attribute in the SupportGTYPE sheet.
 Reports the missing mapping for a support component's
Attributes in the SupportUserAttributes sheet.
Electrical Models
For more information about any of the electrical mapping sheets referenced in the
following rows, see Electrical Translation Maps (on page 45).
Reports missing mapping for conduit and cable tray parts in the
Components ElectricalPartIdentifierMap and ElectricalComponentSPREFMap
sheets.
Reports missing mapping for electrical specifications in the
Specifications
ElectricalRunSpecMap sheet.
Reports missing mapping for conduit and cable tray stock parts in
ElectricalStockParts the ElectricalPartIdentifierMap and
ElectricalComponentSPREFMap sheets.
Reports missing mapping for electrical end preparations in the
EndPreparation
ElectricalEndConnectionMap sheet.

34 Export to PDMS User's Guide


Exporting Model Data to PDMS

Log file details - Specify the full path location and file name of the log file to be created.
Alternatively, you can click Browse and navigate to the necessary location and file.
Validate - Runs the PDMS Export Validation command based on the criteria that you have
specified.
Cancel - Closes the dialog box.

Export to PDMS User's Guide 35


Exporting Model Data to PDMS

Export Model
The File > Export > PDMS Datal Export > Export Model command exports model data from
Smart 3D for subsequent import into PDMS. The process involves transferring Smart 3D objects
and their attribute values to PDMS's native datal file format. For information about the types of
Smart 3D model data that you can export to PDMS, see Exporting Model Data to PDMS (on
page 13).
Prior to using the PDMS export functionality, you must perform the following tasks:
1. Ensure that the Smart 3D and PDMS catalogs are set up properly. For more information,
see Set up the PDMS and Smart 3D Catalogs (on page 20).
2. Edit the options in the delivered initialization file to define the parameters used in the export
process. For more information about the initialization file, see Configure the PDMS Export
Initialization File (on page 23).
3. Edit the mapping workbooks to reflect the customizations that you have made to the Smart
3D model object attributes. For more information about the mapping worksheets, see
Appendix: Export to PDMS Workbook (on page 45).
4. Ensure that the mapping and INI (PDMSExportTranslator.ini) files are in the same file path
before exporting model data to PDMS.
5. Use the PDMS Export Validation command to validate the mapping details that you have
defined. For more information, see PDMS Export Validation (on page 31).

Generate catalog and reference data in Smart 3D and PDMS


formats for PDMS export
You can extract piping catalogs and reference data in Smart 3D and PDMS formats, and
associate the mapping between the two formats. You can generate piping catalog and reference
data simultaneously in either of the formats. The flow diagram below illustrates the parallel
generation process for PDMS export.
You must have a SmartPlant Materials 2011 (7.0.5) license to extract piping
specifications from the standard database (SDB).

36 Export to PDMS User's Guide


Exporting Model Data to PDMS

Load piping specification from SDB into Smart 3D catalog


Piping specification and component data can be exported from the standard database to
Microsoft Excel workbooks, and then bulkloaded into the catalog or they can be exported
directly to the Smart 3D catalog database. For more information on the integration procedure,
see SmartPlant Reference Data Smart 3D Interface User’s Guide which is delivered with the
SmartPlant Materials software.

Extract piping specification data from SDB/SPRD in PDMS format


Any piping specification data can be extracted in PDMS format from the standard database.
Extracted specification data can be loaded into the PDMS catalog using PDMS
PARAGON/SPECON modules. For more information on the integration procedure, see
SmartPlant Reference Data PDMS Interface User’s Guide, which is delivered with the
SmartPlant Materials software.

Load SDB specification data into PDMS catalog


When the piping specification is extracted from the SDB in PDMS format, piping specification
data generates materials, detailed text, specification, and component catref link files. These files
should be loaded into the PDMS catalog in the order specified below using PDMS
PARAGON/SPECON modules. For more information on the integration procedure, see
SmartPlant Reference Data PDMS Interface User’s Guide, which is delivered with the
SmartPlant Materials software.

PDMS format files to load Loading order


Materials file 1
Detailed text file 2
Specification file 3
Component Catref link file 4
PDMS does not allow the materials and detailed text to be loaded if the line count in the
above generated files is more than 5000.

 Before loading the specification files ensure that the materials and detailed text files exist in
PDMS catalog.
 PDMS administrators need to make arrangements to load the component/dimensional data
into PDMS catalog.
 You cannot use loaded specification files from PDMS unless all of the
component/dimensional data along with the point sets and geometry sets are generated for
the specification. Also, ensure that the SCOMs are created in PDMS before the Component
Catref link file is run.
 SmartPlant Reference Data integration does not transfer instruments and specialties in SDB
to PDMS. You need to manually transfer and create appropriate mapping between
instruments and specialties.

Export to PDMS User's Guide 37


Exporting Model Data to PDMS

Extract mapping information between Smart 3D and PDMS piping data


The extracted mapping data between Smart 3D and PDMS piping data can be used in the
S3DPDMSExportmapping.xls workbook. You can also use this workbook to export PDMS
data. To extract a mapping file in .XLS format, use the Company Menu > CO.SD SDB-Tools >
COM.PX.02.02 Export PDMS/SP3D-Data standard database tools. Mapping configuration also
generates additional data related to size independent commodity codes used in either tool, so
that the additional data can be used to generate dimensional data for components in PDMS.

Mapping information can be extracted for each component per specification with
corresponding Idents and size independent Smart 3D commodity codes along with its Idents
that can be used in PDMS.
Remove */ from the PDMS value when appending the mapping information to the
S3DPDMSExportmapping.xls workbook.

Export model data to PDMS


Prior to exporting Smart 3D data to PDMS, verify that the appropriate mapping has
been completed and that both catalogs have been set up appropriately. For more information
about mapping and setting up the catalog, see Appendix: Export to PDMS Workbook (on page
45) and Set up the PDMS and Smart 3D catalogs (on page 20), respectively
1. In the Common task, click File > Export > PDMS Datal Export > Export Model.
2. Select the filter to use to select the objects to export.
3. Type a description.
4. Type your name in the Author box and your company name in the Organization box.
5. Specify the file name and folder for the output datal file.
6. Navigate to the mapping file.
7. Define a log file name and folder.
8. Click OK.

 You must create the filter before you can export the model objects.
 The mapping file is an Excel workbook that is used to map all the objects and their
properties in Smart 3D and PDMS. This workbook is delivered to the [Product
Folder]\3DRefData\SharedContent\Translators\S3DPDMSExport folder during setup.
 If you want the software to create a separate data file for each discipline, you must select
Separate file for each discipline.
 To export the profile parts, the plate parts that connect to the profile parts must be selected
in the filter.

38 Export to PDMS User's Guide


Exporting Model Data to PDMS

Export Model to PDMS Datal Dialog Box


Provides options that control how Smart 3D model objects are written to the PDMS output datal
file.
If you have any questions about using this translator, please contact Intergraph Support. You
can find support information on our web site at http://support.intergraph.com.
Filter - Select the filter to use to identify the model objects to export.
Description - Type a description of the model. This description is included in the output datal
file.
Author - Specifies the person who creates the output datal file.
Organization - Specifies your company or organization name to use in the output datal file.
Datal file - Define the file name and folder path of the output datal file to write. The datal file is a
native file format for PDMS.
Mapping file - Specify the mapping file to use in the export process. The mapping file is an
Excel workbook that is used to map all the objects and their properties in Smart 3D and PDMS.
For more information, see Appendix: Export to PDMS Workbook (on page 45).
Log file - Specify a log file name. You can view the log file by clicking View Log.
Generate separate file for each discipline - Creates a separate output datal file for each
discipline.
OK - Exports the data as specified and closes the Export Model to PDMS Datal dialog box.
Apply - Exports the data as specified without closing the Export Model to PDMS Datal dialog
box.
Cancel - Cancels the operation and closes the Export Model to PDMS Datal dialog box.
View File - Opens the output datal file for viewing.
View Log - Displays the export log file. You must click Apply when exporting in order to view
the log at the end of processing. If you click OK, the dialog box is closed at the end of
processing and you cannot click View Log.

Export to PDMS User's Guide 39


Exporting Model Data to PDMS

40 Export to PDMS User's Guide


SECTION 2

Troubleshooting
The following topics list solutions to common problems that you may have when exporting model
data to PDMS. Tips for improving performance are also provided.

Performance Tips
 Export/Import performance and file size -The following table provides a summary of data
transfer performance for a sample model:

File Export Import


Discipline Number of first class objects
size Time Time
 334 equipment items (37
designed equipment items and
297 catalog equipment items 180
Equipment 7.2 MB 600 seconds
seconds
 1,109 nozzles
 350 shapes
2,000 pipe parts/components,
Piping consisting of 90 pipelines and 210 57 7KB 40 seconds 65 seconds
pipe runs
 790 members
 19 handrails 240
Structure 6 MB 360 seconds
 9 ladders seconds
 6 stairs

 Recommended file size for PDMS import - The following table summarizes the time taken
to import two sample datasets of equipment, piping, and structure model data into PDMS.
The filter Smart 3D size can be chosen accordingly.
These are only guidelines, which can be modified and refined with real projects.

Discipline File Size Import Time


 7.2 MB  10 minutes
Equipment
 23 MB  40 minutes
 577KB  1 minute
Piping
 3 MB  3 minutes
 6 MB  6 minutes
Structure
 23 MB  33 minutes

Export to PDMS User's Guide 41


Troubleshooting

 Equipment imported using SAT and DGN files in Smart 3D is slow - PDMS does not
support complex curved surfaces; consequently, b-spline surfaces stored in the Smart 3D
databases are broken into smaller polyhedrons, which adversely impacts export and import
performance.

Import/Export Issues
 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. Currently, the parent of equipment,
pipeline systems, and structural objects are created as a zone object, and the parent of a
duct run is created as an HVAC object in PDMS hierarchy. 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
Exporting Model Data to PDMS (on page 13).
 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
MergesSP3DRuns/MergeSP3DDuctRuns 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 - The piping and HVAC data is
being transferred using mapping to the equivalent specification present in PDMS. To resolve
this issue, create the needed specifications in Smart 3D, provide the necessary 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/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 errors if a label longer than 50 characters is mapped to
any user-defined attribute in PDMS.

42 Export to PDMS User's Guide


Troubleshooting

Project Creation Estimates


PDMS reference data creation for a typical project - The following list summarizes the
approximate time usually needed to create various catalog items in PDMS:
 Catalog equipment, if needed - Allow 1 to 4 days for each template, depending upon
complexity.
 Nozzle data - Depends upon the number of records of nozzle data; easy to create.
 Piping specifications (Data) - Depends upon the size of specification and common parts
used within specifications. Can vary from 3 to 5 days for each specification when created
manually with in PDMS.
 SmartPlant Reference Data (SPRD) to PDMS approach can be considered as one of
the solutions.
 Use a tool on the internet to create specification data.
 Point set and geometry set used by the piping specifications (equal to piping symbols) -
Allow 1 to 2 days for each point set and geometry set, depending upon complexity.
 Sections - Allow 2 days for each section type to create catalog.
 Material - Depends upon number of records; easy to create.
 Joints specification - Joints references are similar to assembly connections in Smart 3D.
Allow 1 to 2 days for each new joint. Generally, PDMS delivered joints should be adequate
for a typical project.

Mapping Tips
Labels in Smart 3D can be used to map direct objects or properties of related objects, such as
traverse relationships, during export in the mapping file.
The steps below illustrate how to export the equipment part number that is present on the
related catalog part to the PDMS datal file.
1. In the Smart 3D Catalog task, create a label that gives the part number of the placed
equipment.
For more information about creating labels, see Label Editor Command in the
Catalog User's Guide. You can access this document using the Help > Printable Guides
command in the software.
2. Open the CPSmartEquipmentMap equipment translation mapping file.
The CPSmartEquipmentMap mapping file is located in the
S3DPDMSExportMapping.xls workbook. By default, this workbook is delivered in the
[Product Folder]\3DRefData\SharedContent\Data\Translators\S3DPDMSExport folder during
setup.
3. Map the SP3D Attribute to the corresponding PDMS Attribute.
4. Type TRUE in the Label column. An example is shown below.

5. Save the mapping file.

Export to PDMS User's Guide 43


Troubleshooting

44 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

APPENDIX A

Appendix: Export to PDMS Workbook


The File > Export > PDMS Datal Export > Export Model command uses the Microsoft Excel
workbook S3DPDMSExportMapping.xls to map all of the Smart 3D objects and object
properties to the corresponding objects in PDMS. By default, the workbook is delivered in the
[Product Folder]\3DRefData\SharedContent\Data\Translators\S3DPDMSExport folder during
setup.
The S3DPDMSExportMapping.xls workbook consists of all required types of translation
mapping worksheets. Before you export Smart 3D model data, you must modify these mapping
worksheets to ensure that all of the necessary criteria have been met.
The S3DPDMSExportMapping_DIN.xls workbook is also delivered in the [Product
Folder]\3DRefData\SharedContent\Data\Translators\S3DPDMSExport folder during setup.
Default mapping is done according to the DIN standards for structural cross-sections.
See the comments in the delivered mapping file sheets for more information on configuring the
mapping files.
 Electrical Translation Maps (on page 45)
 Equipment Translation Maps (on page 52)
 Hierarchy Translation Maps (on page 68)
 HVAC Translation Maps (on page 77)
 Piping Translation Maps (on page 87)
 Structure Translation Maps (on page 99)
 Supports Translation Maps (on page 130)
 Units Translation Maps (on page 137)
See Also
Set up the PDMS and Smart 3D Catalogs (on page 20)

Export to PDMS User's Guide 45


Appendix: Export to PDMS Workbook

Electrical Translation Maps


Use the electrical translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D electrical properties to the correct PDMS electrical attributes. Before exporting
Smart 3D electrical model data to PDMS, you must modify these sheets to ensure that all of the
catalog electrical components in the Smart 3D model are mapped to corresponding electrical
component objects in PDMS.
After mapping is completed in the S3DPDMSExportMapping.xls workbook, run
the PDMS Export Validation command to validate the mapping data in the workbook. Any
missing entries reported by the validation tool should be resolved. For more information, see
PDMS Export Validation (on page 31).
The following electrical translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
ElectricalClassMap - Maps the supported electrical classes between Smart 3D and PDMS.
This is the main mapping sheet for the electrical discipline. For more information, see
ElectricalClassMap (on page 46).
CPElectricalSystemAttrMap - Maps electrical system attributes between Smart 3D and PDMS.
For more information, see CPElectricalSystemAttrMap (on page 47).
CPCablewayAttrMap - Maps cableway attributes in Smart 3D to electrical branches in PDMS.
For more information, see CPCablewayAttrMap (on page 47).
CPRteCableTrayComponentAttrMap - Maps electrical component attributes between Smart
3D and PDMS. For more information, see CPRteCableTrayComponentAttrMap (on page 48).
ElectricalSupportAttrsMap - Maps electrical support attributes between Smart 3D and PDMS.
For more information, see ElectricalSupportAttrsMap (on page 49).
ElectricalGlobalsMap - Defines the global settings for electrical export. For more information,
see ElectricalGlobalsMap (on page 50).
ElectricalRunSpecMap - Maps electrical tray specification names between Smart 3D and
PDMS. For more information, see ElectricalRunSpecMap (on page 50).
ElectricalPartIdentifierMap - Maps Smart 3D electrical part identifiers to PDMS GTypes. For
more information, see ElectricalPartIdentifierMap (on page 51).
ElectricalComponentSPREFMap - Defines the mapping between the unique string created for
Smart 3D electrical components and the PDMS SPREF attribute. For more information, see
ElectricalComponentSPREFMap (on page 52).

ElectricalClassMap
The ElectricalClassMap sheet displays the electrical class mapping between Smart 3D and
PDMS. The electrical classes that are displayed on this sheet are the only ones that are
currently supported for export to PDMS.
Do not modify any of the values on this sheet.
SP3D Class Name - Displays the Smart 3D electrical class to be mapped.
PDMS Class Name - Displays the PDMS electrical class to which the SP3D Class Value Name
is mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExport.xls workbook that maps
Smart 3D electrical class properties to PDMS.

46 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CPElectricalSystemAttrMap
The CPElectricalSystemAttrMap sheet maps electrical system attributes between Smart 3D
and PDMS.
SP3D Attribute - Defines the Smart 3D electrical system attribute to be mapped.
PDMS Attribute - Defines the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 47


Appendix: Export to PDMS Workbook

CPCablewayAttrMap
The CPCablewayAttrMap sheet maps cable way attributes between Smart 3D and PDMS.
SP3D Attribute - Defines the Smart 3D cable way attribute to be mapped.
PDMS Attribute - Defines the name of the PDMS attribute to which to map the SP3D Attribute
value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPRteCableTrayComponentAttrMap
The CPRteCableTrayComponentAttrMap sheet maps electrical component attributes between
Smart 3D and PDMS.
SP3D Attribute - Defines the Smart 3D electrical component attribute to be mapped.
PDMS Attribute - Defines the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

48 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

ElectricalSupportAttrsMap
The ElectricalSupportAttrsMap sheet maps electrical support attributes between Smart 3D
and PDMS.
SP3D Value - Defines the name of the Smart 3D electrical support to be mapped.
PDMS Value - Defines the name of the PDMS attribute to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.

Export to PDMS User's Guide 49


Appendix: Export to PDMS Workbook

Value - Specifies the value of the PDMS attribute.


Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

ElectricalGlobalsMap
The ElectricalGlobalsMap sheet displays mapping between Smart 3D PartIdentifier,
CatalogComponentUniqueCode, Spec, and PartNumber properties and PDMS. The first
three properties cross-reference their respective value mapping sheets, and the last property
cross-references its additional attribute sheet.
The values contained on this sheet define the global settings for Electrical model
export and should not be modified.
SP3D Attribute - Defines the name of the Smart 3D attribute to map.
PDMS Attribute - Defines the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

50 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

ElectricalRunSpecMap
The ElectricalRunSpecMap sheet maps electrical specification names between Smart 3D and
PDMS.
SP3D Value - Defines the name of the Smart 3D electrical specification to be mapped.
PDMS Value - Defines the name of the PDMS specification to which the SP3D Value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

ElectricalPartIdentifierMap
The ElectricalPartIdentifierMap sheet maps attributes between Smart 3D part identifiers and
PDMS GTypes.
SP3D Attribute - Defines the Smart 3D part identifier to be mapped.
PDMS Attribute - Defines the name of the PDMS GType to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

Export to PDMS User's Guide 51


Appendix: Export to PDMS Workbook

ElectricalComponentSPREFMap
The ElectricalComponentSPREFMap sheet defines mapping between Smart 3D part numbers
of electrical components and the PDMS SPREF attribute.
SP3D Value – Defines the part number or a concatenated string for the tray, tray bend, or
gasket that includes the specification name and electrical component type.
PDMS Value - Defines the value for the SPREF attribute to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

52 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Equipment Translation Maps


Use the equipment translation mapping sheets in the S3DPDMSExportMapping.xls workbook
to map Smart 3D equipment properties to the correct PDMS equipment attributes. Before
exporting Smart 3D equipment model data to PDMS, you must modify these sheets to ensure
that the following criteria have been met:
 All of the catalog equipment objects in the Smart 3D model are mapped to corresponding
equipment objects in PDMS.
 All of the shapes in the Smart 3D model are mapped to corresponding primitives in PDMS.
 All of the nozzles in the Smart 3D model are mapped to corresponding nozzles in PDMS.
This is mandatory for the transfer of nozzles from Smart 3D regardless of the options that
are defined in the PDMSExportTranslation.ini file.
After all of the mapping is completed in the S3DPDMSExportMapping.xls
workbook, run the PDMS Export Validation command to validate the mapping data in the
workbook. Any missing entries reported by the validation tool should be resolved. For more
information, see PDMS Export Validation (on page 31).
The following equipment translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
EquipmentClassMap - Maps the supported equipment classes between Smart 3D and PDMS.
This is the main mapping sheet for equipment discipline. For more information, see
EquipmentClassMap (on page 54).
CPSmartEquipmentMap - Maps equipment attributes between Smart 3D and PDMS. For more
information, see CPSmartEquipmentMap (on page 54).
CPEquipmentComptMap - Maps equipment component attributes between Smart 3D and
PDMS. For more information, see CPEquipmentComptMap (on page 55).
CPShapeMap - Contains the mapping between the Smart 3D Shape class and the equivalent
PDMS primitive (GeometricPrimitive class). For more information, see CPShapeMap (on page
56).
CPPipeNozzleMap - Maps pipe nozzle attributes between Smart 3D and PDMS. For more
information, see CPPipeNozzleMap (on page 57).
CPHVACNozzleMap - Maps HVAC nozzle attributes between Smart 3D and PDMS. For more
information, see CPHVACNozzleMap (on page 57).
CPConduitNozzleMap - Maps conduit nozzle attributes between Smart 3D and PDMS. For
more information, see CPConduitNozzleMap (on page 58).
CPCableTrayNozzleMap - Maps cable tray nozzle attributes between Smart 3D and PDMS. For
more information, see CPCableTrayNozzleMap (on page 59).
CPStraightNozzleCatRefMap - Contains concatenated values for NPD, EndPreparation and
PressureRating properties, which are mapped to PDMS CATRef attribute values for piping
straight nozzles. For more information, see CPStraightNozzleCatRefMap (on page 60).
CPElbowNozzleCAtRefMap - Contains concatenated values for NPD, EndPreparation and
PressureRating properties, which are mapped to PDMS CATRef attribute values for piping
elbow nozzles. For more information, see CPElbowNozzleCAtRefMap (on page 61).
CPHvacNozzleCatRefMap - Contains concatenated values for Smart 3D Width,
Cross-section, and EndPreparation of the HVAC nozzle, which are mapped to their
corresponding nozzle CATRef values in PDMS. For more information, see
CPHvacNozzleCatRefMap (on page 62).

Export to PDMS User's Guide 53


Appendix: Export to PDMS Workbook

EquipGlobalsMap - Contains mapping for Smart 3D PartNumber, PartClass and NozzleType


properties. The first two properties cross-reference their respective value mapping sheets, and
the last property cross-references an additional attribute sheet. For more information, see
EquipGlobalsMap (on page 62).
PartNumberValueMap - Maps Smart 3D part numbers to PDMS. A cross-reference to an
additional attribute sheet is also provided. For more information, see PartNumberValueMap (on
page 63).
PartNumberAdditionalAttributes - Contains additional properties for Smart 3D part numbers
and cross-references to additional attribute sheets containing design parameters. For more
information, see PartNumberAdditionalAttributes (on page 64).
DesParamAdditionalAttrMap - Contains additional properties, or design parameters, for
different part numbers. For more information, see DesParamAdditionalAttrMap (on page 64).
CPShapeValueMap - Contains the mapping between the shape PartClass in Smart 3D and the
equivalent PDMS primitive. For more information, see CPShapeValueMap (on page 66).
CPShapeAdditionalAttributes - Contains additional attributes for PDMS primitives. The part
class of the shape is mapped to the corresponding name of the primitive in the
CPShapeValueMap sheet. For more information, see CPShapeAdditionalAttributes (on page
66).
CPNozzleAdditionalAttribute - Maps Smart 3D nozzle parameters to PDMS attributes. For
more information, see CPNozzleAdditionalAttributes (on page 67).
NozzDesParamAdditionalAttrMap - Contains design parameter values for HVAC nozzles.
Design parameters for HVAC nozzles vary according to the nozzle cross-section, like
rectangular, flat oval, and round. For more information, see NozzDesParamAdditionalAttrMap
(on page 67).

EquipmentClassMap
The EquipmentClassMap sheet displays the equipment class mapping between Smart 3D and
PDMS. The equipment classes that are displayed on this sheet are the only ones that are
currently supported for export to PDMS.
Do not modify any of the values on this sheet.
SP3D Class Name - Displays the Smart 3D equipment class to be mapped.
PDMS Class Name - Displays the PDMS equipment class to which the Smart 3D Class Name
value is mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExport.xls workbook that maps
the Smart 3D equipment class properties to PDMS.

54 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CPSmartEquipmentMap
The CPSmartEquipmentMap sheet maps equipment attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D equipment property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPEquipmentComptMap
The CPEquipmentComptMap sheet maps equipment component attributes between Smart 3D
and PDMS.
SP3D Attribute - Type the name of the Smart 3D equipment component property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

Export to PDMS User's Guide 55


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPShapeMap
The CPShapeMap sheet contains the attribute mapping between the Smart 3D shape and
equivalent PDMS primitive.
SP3D Attribute - Type the name of the Smart 3D shape property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.

56 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Value - Specifies the value of the PDMS attribute.


Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPPipeNozzleMap
The CPPipeNozzleMap sheet maps pipe elbow nozzle attributes between Smart 3D and
PDMS. Fixed attributes Elbow Pipe Nozzle and Straight Pipe Nozzle have ValueDef maps
that are the concatenated values of NPD, end preparation, and pressure rating of the piping
straight nozzle and piping elbow nozzle respectively, which cross-references the
CPElbowNozzleCAtRefMap and CPStraightNozzleCAtRefMap sheets respectively
SP3D Attribute - Type the name of the Smart 3D pipe property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 57


Appendix: Export to PDMS Workbook

CPHVACNozzleMap
The CPHVACNozzleMap sheet maps HVAC nozzle attributes between Smart 3D and PDMS.
Fixed attributes Rectangular, Flat Oval, and Round Nozzle have ValueDef maps that are the
concatenated values of Width, Cross-section and EndPreparation of the HVAC nozzle, which
cross-references the CPHvacNozzleCatRefMap sheet.
SP3D Attribute - Type the name of the Smart 3D HVAC nozzle property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

58 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CPConduitNozzleMap
The CPConduitNozzleMap sheet maps conduit nozzle attributes between Smart 3D and
PDMS. Fixed attribute StraightNozzle has ValueDef maps that are concatenated values of
NCD and EndPreparation of the conduit nozzle, which cross-references the
CPStraightConduitNozzCatRefMap sheet.
SP3D Attribute - Type the name of the Smart 3D conduit nozzle property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 59


Appendix: Export to PDMS Workbook

CPCableTrayNozzleMap
The CPCableTrayNozzleMap sheet maps cable tray nozzle attributes between Smart 3D and
PDMS. Fixed attribute Rectangular nozzle has a ValueDef map that is the concatenated values
of Nominal Width and Nominal Depth of the cable tray nozzle, which cross-references the
CPCableTrayNozzleCatRefMap sheet.
SP3D Attribute - Type the name of the Smart 3D cable tray nozzle property to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

60 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CPStraightNozzleCatRefMap
The CPStraightNozzleCatRefMap sheet contains concatenated values for Smart 3D NPD,
EndPreparation and PressureRating properties. These values are mapped to their
corresponding nozzle CATRef values in PDMS.
SP3D Value - Type the Smart 3D parameter to map.
PDMS Attribute - Type CATRef.
Attribute Value - Type the PDMS CATRef attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

CPElbowNozzleCAtRefMap
The CPElbowNozzleCatRefMap sheet contains concatenated values for Smart 3D NPD,
EndPreparation and PressureRating properties. These values are mapped to their
corresponding nozzle CATRef values in PDMS.
SP3D Value - Type the Smart 3D parameter to map.
PDMS Attribute - Type CATRef.
Attribute Value - Type the PDMS CATRef attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

Export to PDMS User's Guide 61


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

CPHvacNozzleCatRefMap
The CPHvacNozzleCatRefMap sheet contains concatenated values for Smart 3D Width,
Cross-section and EndPreparation of the HVAC nozzle. These values are mapped to their
corresponding nozzle CATRef values in PDMS.
SP3D Value - Type the Smart 3D concatenated values to be mapped.
PDMS Value - Type the PDMS CatRef attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

EquipGlobalsMap
The EquipGlobalsMap sheet displays mapping between Smart 3D PartNumber, PartClass
and NozzleType properties and PDMS. The first two properties cross-reference their respective
value mapping sheets, and the last property cross-references its additional attribute sheet.
The values contained on this sheet define the global settings for equipment model
export and should not be modified.
SP3D Attribute - Displays the name of the Smart 3D attribute to map.
PDMS Attribute - Displays the name of the PDMS attribute to which the SP3D Attribute value
is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

62 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.
See Also
PartNumberValueMap (on page 63)
DesParamAdditionalAttrMap (on page 64)
CPShapeValueMap (on page 66)
CPNozzleAdditionalAttributes (on page 67)

PartNumberValueMap
The PartNumberValueMap sheet maps Smart 3D part numbers to PDMS. A cross-reference to
the corresponding additional attributes sheet is also provided.
SP3D Value - Type the Smart 3D part number to be mapped.
PDMS Value - Type the PDMS part number to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 63


Appendix: Export to PDMS Workbook

PartNumberAdditionalAttributes
The PartNumberAdditionalAttributes sheet maps additional attributes for PDMSA part
numbers. Each additional attribute cross-references to its additional attribute sheet containing
design parameters.
PDMS Value - Type the PDMS part number to be mapped.
PDMS Attribute - Type the PDMS attribute to which the PDMS Value is mapped.
Attribute Value - Type the required attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

64 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

DesParamAdditionalAttrMap
The DesParamAdditionalAttriMap sheet maps additional attributes for PDMS part numbers.
Each additional attribute cross-references to its additional attribute sheet containing design
parameters.
PDMS Value - Type the PDMS part number to be mapped.
PDMS Attribute - Type the PDMS attribute to which the PDMS Value is mapped.
Attribute Value - Type the required attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 65


Appendix: Export to PDMS Workbook

CPShapeValueMap
The CPShapeValueMap sheet maps the shape part class to the corresponding PDMS primitive.
SP3D Value - Type the Smart 3D shape part class to map.
PDMS Value - Type the PDMS primitive name to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

CPShapeAdditionalAttributes
The CPShapeAdditionalAttributes sheet maps additional attributes for PDMS primitives. The
part class of the shape is mapped to the corresponding name of the primitive in the
CPShapeValueMap sheet.
PDMS Value - Type the PDMS primitive type.
Attribute Name - Type the name of the PDMS attribute to which the PDMS Value is mapped.
Attribute Value - Type the required value for the attribute.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.

66 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

CPNozzleAdditionalAttributes
The CPNozzleAdditionalAttributes sheet maps Smart 3D nozzle parameters to PDMS
attributes.
SP3D Value - Type the Smart 3D nozzle parameter to map.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Value is mapped.
Attribute Value - Type the required attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

Export to PDMS User's Guide 67


Appendix: Export to PDMS Workbook

NozzDesParamAdditionalAttrMap
The NozzDesParamAdditionalAttrMap sheet maps additional design parameters for PDMS
HVAC nozzles. Each design parameters is mapped to its value in Smart 3D.
SP3D Value - Type the Smart 3D nozzle to be mapped.
PDMS Attribute - Type the PDMS attribute to which the SP3D Value is mapped.
Attribute Value - Type the required attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

68 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Hierarchy Translation Maps


Use the hierarchy translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D hierarchy properties to the correct PDMS hierarchy attributes.
UDETS (User Defined Element Types) of PDMS are used to create a hierarchy similar to
that of the Smart 3D hierarchy. Before importing the UDETS defined in the mapping file, you
have to create them in PDMS. The delivered mapping sheet has all Smart 3D systems under the
Smart 3D Class Name. You have to define all the required UDETS, map them correspondingly
to those from Smart 3D and then export the model to DATAL. The generated DATAL emulates
the hierarchy of Smart 3D in PDMS when imported.
The following hierarchy translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
Hierarchy Class Map - Maps the supported hierarchy classes between Smart 3D and PDMS.
This is the main mapping sheet for the hierarchy discipline. For more information, see
HierarchyClassMap (on page 69).
CPMSystemMap - Maps system attributes between Smart 3D and PDMS. For more
information, see CPMSystemMap (on page 70).
CPAreaSystemMap - Maps area system attributes between Smart 3D and PDMS. For more
information, see CPAreaSystemMap (on page 70).
CPConduitSystemMap - Maps conduit system attributes between Smart 3D and PDMS. For
more information, see CPConduitSystemMap (on page 71).
CPDuctingSystemMap - Maps ducting system attributes between Smart 3D and PDMS. For
more information, see CPDuctingSystemMap (on page 72).
CPElectricalSystemMap - Maps electrical system attributes between Smart 3D and PDMS. For
more information, see CPElectricalSystemMap (on page 72).
CPMachinerySystemMap - Maps machinery system attributes between Smart 3D and PDMS.
For more information, see CPMachinerySystemMap (on page 73).
CPPipelineSystemMapEx - Maps pipeline system attributes between Smart 3D and PDMS. For
more information, see CPPipelineSystemMapEx (on page 74).
CPPipingSystemMap - Maps piping system attributes between Smart 3D and PDMS. For more
information, see CPPipingSystemMap (on page 75).
CPStructuralSystemMap - Maps structural system attributes between Smart 3D and PDMS.
For more information, see CPStructuralSystemMap (on page 75).
CPUnitSystemMap - Maps unit system attributes between Smart 3D and PDMS. For more
information, see CPUnitSystemMap (on page 77).

HierarchyClassMap
The HierarchyClassMap sheet displays the hierarchy class mapping between Smart 3D and
PDMS. The hierarchy classes that are displayed on this sheet are the only ones that are
currently supported for export to PDMS.
Do not modify any of the values on this sheet.
SP3D Class Name - Displays the Smart 3D hierarchy class to be mapped.
PDMS Class Name - Displays the PDMS hierarchy class to which the SP3D Class Name is
mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExport.xls workbook that maps
Smart 3D hierarchy class properties to PDMS.

Export to PDMS User's Guide 69


Appendix: Export to PDMS Workbook

CPMSystemMap
The CPMSystemMap sheet maps system attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPAreaSystemMap
The CPAreaSystemMap sheet maps area system attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D area system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

70 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPConduitSystemMap
The CPConduitSystemMap sheet maps conduit system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D conduit system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.

Export to PDMS User's Guide 71


Appendix: Export to PDMS Workbook

Value - Specifies the value of the PDMS attribute.


Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPDuctingSystemMap
The CPDuctingSystemMap sheet maps ducting system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D ducting system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

72 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CPElectricalSystemMap
The CPElectricalSystemMap sheet maps electrical system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D electrical system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPMachinerySystemMap
The CPMachinerySystemMap sheet maps machinery system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D machinery system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

Export to PDMS User's Guide 73


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPPipelineSystemMapEx
The CPPipelineSystemMapEx sheet maps pipeline system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D pipeline system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.

74 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Value - Specifies the value of the PDMS attribute.


Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CPPipingSystemMap
The CPPipingSystemMap sheet maps piping system attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D piping system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 75


Appendix: Export to PDMS Workbook

CPStructuralSystemMap
The CPStructuralSystemMap sheet maps structural system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D structural system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

76 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CPUnitSystemMap
The CPUnitSystemMap sheet maps unit system attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D unit system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 77


Appendix: Export to PDMS Workbook

HVAC Translation Maps


Use the HVAC translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D HVAC properties to the correct PDMS HVAC attributes. Before exporting Smart
3D HVAC model data to PDMS, you must modify these sheets to ensure that the following
criteria have been met:
 All of the components in the Smart 3D model are mapped to corresponding components in
PDMS.
 All of the gaskets, stock parts, bends, and supports in the Smart 3D model are mapped to
corresponding ones in PDMS.
 Specifications and end preparations are mapped between the two systems.
After all of the mapping is completed in the S3DPDMSExportMapping.xls workbook, run the
PDMS Export Validation command to validate the mapping data in the workbook. Any missing
entries reported by the validation tool should be resolved. For more information, see PDMS
Export Validation (on page 31).
The following HVAC translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
HVACClassMap - Maps the supported HVAC classes between Smart 3D and PDMS. This is
the main mapping sheet for the HVAC discipline. For more information, see HVACClassMap (on
page 79).
CPDuctingSystemAttrMap - Maps Ducting system attributes from Smart 3D to that of HVAC in
PDMS. For more information, see CPDuctingSystemAttrMap (on page 79).
CPMSystemAttrMap - Maps Generic system attributes from Smart 3D to that of HVAC in
PDMS. For more information, see CPMSystemAttrMap (on page 79).
CPDuctRunAttrMap - Maps HVAC run properties from Smart 3D to that of BRANCH in PDMS.
For more information, see CPDuctRunAttrMap (on page 80).
DuctComponentAttrsMap - Maps HVAC component properties from Smart 3D to PDMS. For
more information, see DuctComponentAttrsMap (on page 81).
DuctSupportAttrsMap - Maps HVAC support properties from Smart 3D to PDMS. For more
information, see DuctSupportAttrsMap (on page 82).
DesignSupportAttrsMap - Maps HVAC design support properties from Smart 3D to PDMS. For
more information, see DesignSupportAttrsMap (on page 82).
HVACGlobalsMap - Defines the global settings for HVAC export. For more information, see
HVACGlobalsMap (on page 83).
DuctRunSpecMap - Maps HVAC specification names between Smart 3D and PDMS. For more
information, see DuctRunSpecMap (on page 86).
HVACPartIdentifierMap - Maps Smart 3D part identifier to PDMS GTypes. For more
information, see HVACPartIdentifierMap (on page 84).
HVACComponentSPREFMap - Defines the mapping between the unique string created for
Smart 3D piping components and the PDMS SPREF attribute. For more information, see
HVACComponentSPREFMap (on page 85).
HVACEndPreparationMap – Maps end preparations between Smart 3D and PDMS. For more
information, see HVACEndPreparationMap (on page 84).
HVACDesParamMap– Maps component design parameters from Smart 3D to PDMS. For more
information, see HVACDesParamMap (on page 86).

78 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

HVACClassMap
The HVACClassMap sheet defines the HVAC class mapping between Smart 3D and PDMS.
The HVAC classes that are displayed on the HVACClassMap sheet are the only ones that are
currently supported for export to PDMS. Do not modify any of the values on this sheet.
SP3D Class Name - Displays the Smart 3D piping class to be mapped.
PDMS Class Name - Displays the PDMS piping class to which the Smart 3D Class Value
Name is mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExportMapping.xls workbook
that maps Smart 3D HVAC class attributes to PDMS.

CPDuctingSystemAttrMap
The CPDuctingSystemAttrMap sheet maps ducting system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D ducting system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 79


Appendix: Export to PDMS Workbook

CPMSystemAttrMap
The CPMSystemAttrMap sheet maps Generic system attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D Generic system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

CPDuctRunAttrMap
The CPDuctRunAttrMap sheet maps duct run attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D duct run attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

80 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

DuctComponentAttrsMap
The DuctComponentAttrsMap sheet maps duct component attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D duct component attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).

Export to PDMS User's Guide 81


Appendix: Export to PDMS Workbook

Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

DuctSupportAttrsMap
The DuctSupportAttrsMap sheet maps duct support attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D duct support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

DesignSupportAttrsMap
The DuctComponentAttrsMap sheet maps design support attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D design support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

82 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

HVACGlobalsMap
The HVACGlobalsMap sheet displays mapping between Smart 3D SP3DPartIdentifier,
SP3DEndConnection, SP3DCatalogComponentUniqueCode, Spec, and SP3DPartNumber
properties and PDMS. The first four properties cross-reference their respective value mapping
sheets, and the last property cross-references its additional attribute sheet.
The values contained on this sheet define the global settings for HVAC model export and should
not be modified.
SP3D Attribute - Displays the name of the Smart 3D attribute to map.
PDMS Attribute - Displays the name of the PDMS attribute to which the SP3D Attribute value
is mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.

Export to PDMS User's Guide 83


Appendix: Export to PDMS Workbook

Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.
See Also
HVACPartIdentifierMap (on page 84)
HVACEndPreparationMap (on page 84)
HVACComponentSPREFMap (on page 85)
DuctRunSpecMap (on page 86)
HVACDesParamMap (on page 86)

HVACPartIdentifierMap
The HVACPartIdentifierMap sheet maps attributes between Smart 3D part identifiers and
PDMS GTypes.
SP3D Attribute - Type the Smart 3D part identifier to be mapped.
PDMS Attribute - Type the name of the PDMS GType to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

84 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

HVACEndPreparationMap
The HVACEndPreparationMap sheet maps end preparation values between Smart 3D and
PDMS.
SP3D Value - Type the Smart 3D end preparation value to be mapped.
PDMS Value - Type the PDMS end preparation value to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

HVACComponentSPREFMap
The HVACComponentSPREFMap sheet defines mapping between Smart 3D part numbers of
HVAC components and the PDMS SPREF attribute.
SP3D Value – For ducts, duct bends, supports, and gaskets, this value can be a part number or
a concatenated string that includes the specification name, HVAC component type (ducting/duct
bend/duct support/gasket), cross section type (round/rectangular/oval/flat oval/UShape), width,
and depth, separated by a dash "-". For example, you can type Lindab
Spec-Ducting-Round-100-100.
PDMS Value - Type the value for the SPREF attribute to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 85


Appendix: Export to PDMS Workbook

DuctRunSpecMap
The DuctRunSpecMap sheet maps HVAC specification names between Smart 3D and PDMS.
SP3D Value - Type the name of the Smart 3D HVAC specification to be mapped.
PDMS Value - Type the name of the PDMS specification to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

HVACDesParamMap
The HVACDesParamMap sheet maps additional attributes for Smart 3D part numbers.
SP3D Value - Type the Smart 3D part number to be mapped.
PDMS Attribute - Type the PDMS attributes that are created as additional attributes for SP3D
Value.
Attribute Value - Type the required attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.

86 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 87


Appendix: Export to PDMS Workbook

Piping Translation Maps


Use the piping translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D piping properties to the correct PDMS piping attributes. Before exporting Smart
3D piping model data to PDMS, you must modify these sheets to ensure that the following
criteria have been met:
 All of the components in the Smart 3D model are mapped to corresponding components in
PDMS.
 All of the Smart 3D piping specialties and instruments are mapped to corresponding
PCOMPs and INSTs in PDMS.
 All of the gaskets in the Smart 3D model are mapped to corresponding ones in PDMS.
 Pipe stock from Smart 3D and PDMS is mapped.
After all of the mapping is completed in the S3DPDMSExportMapping.xls
workbook, run the PDMS Export Validation command to validate the mapping data in the
workbook. Any missing entries reported by the validation tool should be resolved. For more
information, see PDMS Export Validation (on page 31).
The following piping translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
PipingClassMap - Maps the supported piping classes between Smart 3D and PDMS. This is
the main mapping sheet for the piping discipline. For more information, see PipingClassMap (on
page 89).
CPPipelineSystemMap - Maps pipeline system attributes between Smart 3D and PDMS. For
more information, see CPPipelineSystemMap (on page 89).
CPMPipeRunMap - Maps pipe run attributes between Smart 3D and PDMS. For more
information, see CPMPipeRunMap (on page 90).
PipingGlobalsMap - Defines the global settings for piping export. For more information, see
PipingGlobalsMap (on page 90).
PipeRunSpecMap - Maps piping specification names between Smart 3D and PDMS. For more
information, see PipeRunSpecMap (on page 92).
SP3DPartIdentifierMap - Maps Smart 3D part identifier properties and PDMS GTypes. For
more information, see SP3DPartIdentifierMap (on page 92).
CatalogComponentSPREFMap - Defines the mapping between the unique string created for
Smart 3D piping components and the PDMS SPREF attribute. For more information, see
CatalogComponentSPREFMap (on page 93).
NPDSpecificSPREFMap - Defines the mapping between the unique string created for Smart 3D
piping components and the PDMS SPREF attribute. This sheet is used if the SPREF of a
component changes with a given NPD. For more information, see NPDSpecificSPREFMap (on
page 93).
CatalogSpecialtySPREFMap - Defines the mapping between the unique string created for
Smart 3D catalog specialty components and the PDMS SPREF attribute. For more information,
see CatalogSpecialtySPREFMap (on page 94).
CatalogInstrumentSPREFMap - Defines the mapping between the unique string created for
Smart 3D catalog instrument components and the PDMS SPREF attribute. For more
information, see CatalogInstrumentSPREFMap (on page 94).
OnFlySpecialtySPREFMap - Defines the mapping between the unique string created for Smart
3D on-the-fly specialty components and the PDMS SPREF attribute. For more information, see
OnFlySpecialtySPREFMap (on page 95).

88 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

OnFlyInstrumentSPREFMap - Defines the mapping between the unique string created for
Smart 3D on-the-fly instruments and the PDMS SPREF attribute. For more information, see
OnFlyInstrumentSPREFMap (on page 95).
PipeComponentAttrsMap - Defines the attribute mapping for Smart 3D pipe components. For
more information, see PipeComponentAttrsMap (on page 96).
PipeInstrumentAttrsMap - Defines the attribute mapping for Smart 3D pipe instruments (both
catalog and on-the-fly). For more information, see PipeInstrumentAttrsMap (on page 97).
PipeSpecialtyAttrsMap - Defines the attribute mapping for Smart 3D pipe specialties (both
catalog and on-the-fly). For more information, see PipeSpecialtyAttrsMap (on page 97).
PipeSupportAttrsMap - Defines the attribute mapping for Smart 3D pipe supports. For more
information, see PipeSupportAttrsMap (on page 98).
EndConnectionMap - Maps end preparation values between Smart 3D and PDMS. For more
information, see EndConnectionMap (on page 99).

PipingClassMap
The PipingClassMap sheet defines the piping class mapping between Smart 3D and PDMS.
The piping classes that are displayed on the PipingClassMap sheet are the only ones that are
currently supported for export to PDMS.
Do not modify any of the values on this sheet.
SP3D Class Name - Displays the Smart 3D piping class to be mapped.
PDMS Class Name - Displays the PDMS piping class to which the Smart 3D Class Value
Name is mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExport.xls workbook that maps
Smart 3D piping class properties to PDMS.

CPPipelineSystemMap
The CPPipelineSystemMap sheet maps pipeline system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D pipeline system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 89


Appendix: Export to PDMS Workbook

Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

CPMPipeRunMap
The CPMPipeRunMap sheet maps pipe run attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D pipe run attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which to map the SP3D Attribute
value is mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

90 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

PipingGlobalsMap
The PipingGlobalsMap sheet displays mapping between Smart 3D SP3DPartIdentifier,
SP3DEndConnection, SP3DCatalogComponentUniqueCode,
SP3DCatalogSpecialtyUniqueCode, SP3DCatalogInstrumentUniqueCode,
SP3DOnFlyInstrumentUniqueCode, SP3DNPDSpecificSPREFMap properties and PDMS.
The first six properties cross-reference their respective value mapping sheets, and the last
property cross-references its additional attribute sheet.
The values contained on this sheet define the global settings for piping model
export and should not be modified.
SP3D Attribute - Displays the name of the Smart 3D attribute to map.
PDMS Attribute - Displays the name of the PDMS attribute to which the SP3D Attribute value
is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.
See Also
SP3DPartIdentifierMap (on page 92)
EndConnectionMap (on page 99)
CatalogComponentSPREFMap (on page 93)
CatalogSpecialtySPREFMap (on page 94)
CatalogInstrumentSPREFMap (on page 94)
OnFlySpecialtySPREFMap (on page 95)
OnFlyInstrumentSPREFMap (on page 95)

Export to PDMS User's Guide 91


Appendix: Export to PDMS Workbook

PipeRunSpecMap
The PipeRunSpecMap sheet maps piping specification names between Smart 3D and PDMS.
SP3D Value - Type the name of the Smart 3D piping specification to be mapped.
PDMS Value - Type the name of the PDMS specification to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

SP3DPartIdentifierMap
The SP3DPartIdentifierMap sheet maps attributes between Smart 3D part identifiers and
PDMS GTypes.
SP3D Value - Type the Smart 3D part identifier to be mapped.
PDMS Gtype - Type the name of the PDMS GType to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

92 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CatalogComponentSPREFMap
The CatalogComponentSPREFMap sheet defines mapping between the unique string created
for Smart 3D piping components and the PDMS SPREF attribute.
SP3D Value - Type the Smart 3D unique string to be mapped. The string is created by
appending the Smart 3D specification name, component short code, and option code. Separate
each entry with a dash ( - ). For example, you can type 1C0031-Piping-1 or
2C0032-Concentric Reducer-1.
PDMS Value - Type the value for the SPREF attribute to which SP3D Value is mapped. The
PDMS Value may also contain the Spec name prefixed to the SPREF attribute.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

NPDSpecificSPREFMap
The NPDSpecificSPREFMap sheet defines mapping between the unique string created for
Smart 3D piping components and the PDMS SPREF attribute. This sheet is used if the SPREF
of a component changes with a given NPD.
If no values are defined on this sheet, the software uses the values defined on the
CatalogComponentSPREFMap sheet.
SP3D Value - Type the Smart 3D unique string to be mapped. The string is created by
appending the Smart 3D specification name, component short code, option code, and NPD of
each port. Separate each entry with a dash ( - ). For example, you can type
1C0031-Piping-1-20-20 or 1C0031-Flange-211-125-125.
PDMS Value - Type the value for the SPREF attribute to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

Export to PDMS User's Guide 93


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

CatalogSpecialtySPREFMap
The CatalogSpecialtySPREFMap sheet defines the mapping between the unique string
created for Smart 3D catalog specialty components and the PDMS SPREF attribute.
SP3D Value - Type the Smart 3D unique string to be mapped. The string is created by
appending the Smart 3D tag number or generic tag number and NPD of each port. Separate
each entry with a dash ( - ). For example, you can type ST-1001-15-15.
PDMS Value - Type the value for the SPREF attribute to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

CatalogInstrumentSPREFMap
The CatalogInstrumentSPREFMap sheet defines the mapping between the unique string
created for Smart 3D catalog instrument components and the PDMS SPREF attribute.
SP3D Value - Type the Smart 3D unique string to be mapped. The string is created by
appending the Smart 3D tag number or generic tag number and NPD of each port. Separate
each entry with a dash ( - ). For example, you can type BV-1001-15-15.
PDMS Value - Type the value for the SPREF attribute to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

94 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

OnFlySpecialtySPREFMap
The OnFlySpecialtySPREFMap sheet defines the mapping between the unique string created
for Smart 3D on-the-fly specialty components and the PDMS SPREF attribute.
SP3D Value - Type the Smart 3D unique string to be mapped. The string is created by
appending the Smart 3D part number along with the end preparation, pressure rating, schedule
thickness, and end standard of the specialty component ports. Separate each entry with a dash
( - ). For example, you can type CS3WayBallCVal-21-35-1-5-21-35-1-5.
PDMS Value - Type the value for the SPREF attribute to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

OnFlyInstrumentSPREFMap
The OnFlyInstrumentSPREFMap sheet defines the mapping between the unique string
created for Smart 3D on-the-fly instruments and the PDMS SPREF attribute.
SP3D Value - Type the Smart 3D unique string to be mapped. The string is created by
appending the Smart 3D part number along with the end preparation, pressure rating, schedule
thickness, and end standard of the instrument ports. Separate each entry with a dash ( - ). For
example, you can type ISSDS4-21-35-1-5-21-35-1-5.
PDMS Value - Type the value for the SPREF attribute to which the SP3D Value is mapped.

Export to PDMS User's Guide 95


Appendix: Export to PDMS Workbook

MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

PipeComponentAttrsMap
The PipeComponentsAttrsMap sheet defines attribute mapping for Smart 3D pipe
components.
SP3D Attribute - Type the Smart 3D pipe component attribute to be mapped.
PDMS Attribute - Type the name of PDMS pipe component attribute to which the SP3D
Attribute value is mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.

96 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

PipeInstrumentAttrsMap
The PipeInstrumentAttrsMap sheet defines attribute mapping for Smart 3D pipe instruments
(both Catalog and on-the-fly).
SP3D Attribute - Type the Smart 3D pipe instrument attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 97


Appendix: Export to PDMS Workbook

PipeSpecialtyAttrsMap
The PipeSpecialtyAttrsMap sheet defines attribute mapping for Smart 3D pipe specialties
(both Catalog and on-the-fly).
SP3D Attribute - Type the Smart 3D pipe specialty component attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

PipeSupportAttrsMap
The PipeSupportAttrsMap sheet defines attribute mapping for Smart 3D pipe supports.
SP3D Attribute - Type the Smart 3D pipe support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

98 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

EndConnectionMap
The EndConnectionMap sheet maps end connection values between Smart 3D and PDMS.
SP3D Value - Type the Smart 3D end connection value to be mapped. This value can be a
combined string of End Connection and Pressure Rating, or any other property.
PDMS Value - Type the PDMS end preparation value to which the SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 99


Appendix: Export to PDMS Workbook

Structure Translation Maps


Use the structure translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D structure properties to the correct PDMS structure attributes. Before exporting
Smart 3D structure model data to PDMS, you must modify these sheets to ensure that the
following criteria have been met:
 All of the cross-sections and respective cardinal points in the Smart 3D model are mapped
to the corresponding cross-sections and PLine attributes in the PDMS catalog. This is
mandatory for the export of members from Smart 3D.
 All of the Marine cross-sections and respective load points in the Smart 3D model are
mapped to the corresponding cross-sections and PLine attributes in the PDMS catalog. This
is mandatory for the export of profile parts from Smart 3D.
 In the PDMSExportTranslator.ini file, TransferInsulationAsGTypes is set so that insulation
is exported using the mapping file, then the catalog must be set up for insulation on
members. Also, all insulation encasements in the model must be created in the PDMS
catalog and mapped to the corresponding fitting in PDMS.
After all of the mapping is completed in the S3DPDMSExportMapping.xls
workbook, run the PDMS Export Validation command to validate the mapping data in the
workbook. Any missing entries reported by the validation tool should be resolved. For more
information, see PDMS Export Validation (on page 31).
The following structure translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
StructureClassMap - Maps the supported structure classes between Smart 3D and PDMS.
This is the main mapping sheet for the structure discipline. For more information, see
StructureClassMap (on page 102).
CoordinateSystemMap - Maps coordinate system attributes between Smart 3D and PDMS.
For more information, see CoordinateSystemMap (on page 102).
ElevationPlaneMap - Maps elevation plane attributes between Smart 3D and PDMS. For more
information, see ElevationPlaneMap (on page 103).
GridLineMap - Maps grid line attributes between Smart 3D and PDMS. For more information,
see GridLineMap (on page 104).
LinearMemberPartAttrsMap - Maps linear member part attributes between Smart 3D and
PDMS. For more information, see LinearMemberPartAttrsMap (on page 104).
CurvedMemberPartAttrsMap - Maps curved member part attributes between Smart 3D and
PDMS. For more information, see CurvedMemberPartAttrsMap (on page 105).
InsulationAttrsMap - Maps insulation attributes between Smart 3D and PDMS. For more
information, see InsulationAttrsMap (on page 106).
SlabAttrsMap - Maps slab attributes between Smart 3D and PDMS. For more information, see
SlabAttrsMap (on page 106).
StairAttrsMap - Maps stair attributes between Smart 3D and PDMS. For more information, see
StairAttrsMap (on page 107).
LadderAttrsMap - Maps ladder attributes between Smart 3D and PDMS. For more information,
see LadderAttrsMap (on page 108).
HandRailAttrsMap - Maps handrail attributes between Smart 3D and PDMS. For more
information, see HandRailAttrsMap (on page 109).
FootingAttrsMap - Maps footing attributes between Smart 3D and PDMS. For more
information, see FootingAttrsMap (on page 109).

100 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

EquipmentFoundationAttrsMap - Maps equipment foundation attributes between Smart 3D


and PDMS. For more information, see EquipmentFoundationAttrsMap (on page 110).
LeafPlateSystemAttrsMap - Maps leaf plate system attributes between Smart 3D and PDMS.
For more information, see LeafPlateSystemAttrsMap (on page 111).
PlanarPlatePartAttrsMap - Maps planar plate system attributes between Smart 3D and PDMS.
For more information, see PlanarPlatePartAttrsMap (on page 112).
CurvedPlatePartAttrsMap - Maps curved plate part attributes between Smart 3D and PDMS.
For more information, see CurvedPlatePartAttrsMap (on page 112).
LeafStiffenerSystemAttrsMap - Maps leaf stiffener system attributes between Smart 3D and
PDMS. For more information, see LeafStiffenerSystemAttrsMap (on page 113).
LinearStiffenerPartAttrsMap - Maps linear stiffener part attributes between Smart 3D and
PDMS. For more information, see LinearStiffenerPartAttrsMap (on page 114).
CurvedStiffenerPartAttrsMap - Maps curved stiffener part attributes between Smart 3D and
PDMS. For more information, see CurvedStiffenerPartAttrsMap (on page 114).
LeafERSystemAttrsMap - Maps leaf edge reinforcement system attributes between Smart 3D
and PDMS. For more information, see LeafERSystemAttrsMap (on page 115).
LinearERProfilePartAttrsMap - Maps linear edge reinforcement profile part attributes between
Smart 3D and PDMS. For more information, see LinearERProfilePartAttrsMap (on page 116).
CurvedERProfilePartAttrsMap - Maps curved edge reinforcement profile part attributes
between Smart 3D and PDMS. For more information, see CurvedERProfilePartAttrsMap (on
page 117).
LeafBeamSystemAttrsMap - Maps leaf beam system attributes between Smart 3D and PDMS.
For more information, see LeafBeamSystemAttrsMap (on page 117).
BeamPartAttrsMap - Maps beam part attributes between Smart 3D and PDMS. For more
information, see BeamPartAttrsMap (on page 118).
LinearSAStiffenerPartAttrsMap - Maps linear SA stiffener part attributes between Smart 3D
and PDMS. For more information, see LinearSAStiffenerPartAttrsMap (on page 119).
CurvedSAStiffenerPartAttrsMap - Maps curved SA stiffener part attributes between Smart 3D
and PDMS. For more information, see CurvedSAStiffenerPartAttrsMap (on page 120).
HoleFittingAttrsMap - Maps hole fitting object attributes between Smart 3D and PDMS. For
more information, see HoleFittingAttrsMap (on page 120).
StructureGlobalsMap - Defines global settings for structural export. For more information, see
StructureGlobalsMap (on page 121).
InsulationAttrMap - Defines insulation encasement type design parameters for each
cross-section type. For more information, see InsulationAttrMap (on page 122).
InsulationSpecAttrMap - Defines insulation encasement type SpecRef attributes for each
cross-section type. For more information, see InsulationSpecAttrMap (on page 123).
StructureMatSpecMap - Defines value mapping of the MatRef attribute for each Smart 3D
material type. For more information, see StructureMatSpecMap (on page 124).
SmartItemMaterialMap - Defines the value mapping of the MatRef attribute for each footing
and equipment foundation objects and their assemblies. For more information, see
SmartItemMaterialMap (on page 124).
StructPartNumbersMap - Defines value mapping of the MatRef attribute for each structural
object part number. For more information, see StructPartNumbersMap (on page 125).
StructClassAdditionalAttributes - Maps additional attributes for Smart 3D cross-sections. For
more information, see StructClassAdditionalAttributes (on page 126).

Export to PDMS User's Guide 101


Appendix: Export to PDMS Workbook

AISC-LRFD-HSSC, AISC-LRFD-PIPE, AISC-LRFD-L, AISC-LRFD-C, AISC-LRFD-WT,


AISC-LRFD-HSSR, AISC-LRFD-W, AISC-LRFD-M, AISC-LRFD-S, AISC-LRFD-ST,
AISC-LRFD-HP, AISC-LRFD-MC - Defines value mapping between a Smart 3D cross-section
name and the PDMS cross-section SpecRef attribute for each specific cross-section type. For
more information, see Cross-Section Maps (on page 127).
TUBE_PLine, ANG_PLine, DINU_PLine, TEE_PLine, BOX_PLine, BEAM_PLine,
SBM_PLine, STEE_PLine - Defines value mapping between Smart 3D cardinal points and the
PDMS PLine attribute for each specific cross-section type. For more information, see Cardinal
Point Maps (on page 127).
MarineCSAdditionalAttributes - Maps additional attributes for Smart 3D cross-sections.
ShipShapes-I, ShipShapes-B, ShipShapes-FB, ShipShapes-ISType, ShipShapes-CSType,
ShipShapes-H, ShipShapes-T_XType, ShipShapes-TSType, ShipShapes-EA,
ShipShapes-RT, ShipShapes-P, ShipShapes-BUT, ShipShapes-C_SS, ShipShapes-UA,
ShipShapes-BUTL2, ShipShapes-BUTL3, ShipShapes-HalfR, ShipShapes-R - Defines value
mapping between a Smart 3D cross-section name and the PDMS cross-section SpecRef
attribute for each specific cross-section type.
I_PLine, B_Pline, FB_Pline, ISType_Pline, CSType_Pline, H_Pline, T_XType_Pline,
TSType_Pline, EA_Pline, RT_Pline, P_Pline, BUT_Pline, C_SS_Pline, UA_Pline,
BUTL2_Pline, BUTL3_Pline, HalfR_Pline, R_Pline - Defines value mapping between Smart
3D load points and the PDMS PLine attribute for each specific cross-section type.

StructureClassMap
The StructureClassMap sheet defines the structure class mapping between Smart 3D and
PDMS. The structure classes that are displayed on this sheet are the only ones that are
currently supported for export to PDMS.
Do not modify any of the values on this sheet.
Source Class Name - Displays the Smart 3D structure class to be mapped.
Target Class Name - Displays the PDMS structure class to which the Source Class Name
value is mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExport.xls workbook that maps
Smart 3D structure class properties to PDMS.

CoordinateSystemMap
The CoordinateSystemMap sheet maps coordinate system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D coordinate system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

102 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

ElevationPlaneMap
The ElevationPlaneMap sheet maps elevation plane attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D elevation plane attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 103


Appendix: Export to PDMS Workbook

GridLineMap
The GridLineMap sheet maps grid line attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D grid line attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LinearMemberPartAttrsMap
The LinearMemberPartAttrsMap maps linear member part attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the name of the Smart 3D linear member part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

104 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

CurvedMemberPartAttrsMap
The CurvedrMemberPartAttrsMap sheet maps curved member part attributes between Smart
3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D curved member part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 105


Appendix: Export to PDMS Workbook

Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

InsulationAttrsMap
The InsulationAttrsMap sheet maps insulation attributes between Smart 3D and PDMS.
Value - Type the Smart 3D insulation parameter to map.
Attribute Name - Type the name of the PDMS attribute to which Value is mapped.
Attribute Value - Type the required attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

106 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

SlabAttrsMap
The SlabAttrsMap sheet maps slab attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D slab attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

StairAttrsMap
The StairAttrsMap sheet maps stair attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D stair attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

Export to PDMS User's Guide 107


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LadderAttrsMap
The LadderAttrsMap sheet maps ladder attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D ladder attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

108 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

HandRailAttrsMap
The HandRailAttrsMap sheet maps handrail attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D handrail attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 109


Appendix: Export to PDMS Workbook

FootingAttrsMap
The FootingAttrsMap sheet maps footing attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D footing attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

EquipmentFoundationAttrsMap
The EquipmentFoundationAttrsMap sheet maps equipment foundation attributes between
Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D equipment foundation attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

110 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LeafPlateSystemAttrsMap
The LeafPlateSystemAttrsMap sheet maps leaf plate system attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D leaf plate system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

Export to PDMS User's Guide 111


Appendix: Export to PDMS Workbook

PlanarPlatePartAttrsMap
The PlanarPlatePartAttrsMap sheet maps planar plate part attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D planar plate part system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

CurvedPlatePartAttrsMap
The CurvedPlatePartAttrsMap sheet maps curved plate part attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D curved plate part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

112 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LeafStiffenerSystemAttrsMap
The LeafStiffenerSystemAttrsMap sheet maps leaf stiffener system attributes between Smart
3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D leaf stiffener system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 113


Appendix: Export to PDMS Workbook

Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LinearStiffenerPartAttrsMap
The LeafStiffenerPartAttrsMap sheet maps linear stiffener part attributes between Smart 3D
and PDMS.
SP3D Attribute - Type the name of the Smart 3D linear stiffener part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

114 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CurvedStiffenerPartAttrsMap
The CurvedStiffenerPartAttrsMap sheet maps curved stiffener part attributes between Smart
3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D curved stiffener part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LeafERSystemAttrsMap
The LeafERSystemPartAttrsMap sheet maps leaf reinforcement system part attributes
between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D leaf edge reinforcement system part attribute
to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

Export to PDMS User's Guide 115


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LinearERProfilePartAttrsMap
The LinearERProfilePartAttrsMap sheet maps linear edge reinforcement profile part attributes
between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D linear edge reinforcement profile part attribute
to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.

116 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

CurvedERProfilePartAttrsMap
The CurvedERProfilePartAttrsMap sheet maps curved edge reinforcement profile part
attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D curved edge reinforcement profile part
attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 117


Appendix: Export to PDMS Workbook

LeafBeamSystemAttrsMap
The LeafBeamSystemAttrsMap sheet maps leaf beam system attributes between Smart 3D
and PDMS.
SP3D Attribute - Type the name of the Smart 3D leaf beam system attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

BeamPartAttrsMap
The BeamPartAttrsMap sheet maps beam part attributes between Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D beam part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

118 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

LinearSAStiffenerPartAttrsMap
The LinearSAStiffenerPartAttrsMap sheet maps linear SA stiffener part attributes between
Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D linear SA stiffener part attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.

Export to PDMS User's Guide 119


Appendix: Export to PDMS Workbook

Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

CurvedSAStiffenerPartAttrsMap
The CurvedSAStiffenerPartAttrsMap sheet maps curved SA stiffener part attributes between
Smart 3D and PDMS.
SP3D Attribute - Type the name of the Smart 3D curved SA stiffener part attribute to be
mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

120 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

HoleFittingAttrsMap
The HoleFittingAttrsMap sheet maps hole fitting object attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D hole fitting attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute is
mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 121


Appendix: Export to PDMS Workbook

StructureGlobalsMap
The StructureGlobalsMap sheet defines value mapping between Smart 3D Insulation,
InsulationSpecRef, SP3DMaterial, SmartItemMaterial, CrossSection, and PartNumber
attributes and PDMS.
The values contained on this sheet define the global settings for structure model
export and should not be modified.
SP3D Attribute - Displays the name of the Smart 3D attribute to map.
PDMS Attribute - Displays the name of the PDMS attribute to which the SP3D Attribute value
is mapped.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Label – Specify whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specify whether the item should be ignored during export. Type TRUE/YES or
FALSE/NO. Entries can be in lowercase or uppercase.
See Also
InsulationAttrMap (on page 122)
InsulationSpecAttrMap (on page 123)
StructureMatSpecMap (on page 124)
StructClassAdditionalAttributes (on page 126)
StructPartNumbersMap (on page 125)

122 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

InsulationAttrMap
The InsulationAttrMap sheet defines insulation encasement type design parameters for each
cross-section type.
Value - Type the Smart 3D insulation encasement type design parameter to be mapped.
Attribute Name - Type the name of the PDMS attribute to which Value is mapped.
Attribute Value - Type the PDMS attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

InsulationSpecAttrMap
The InsulationSpecAttrMap sheet defines insulation encasement type SpecRef attributes for
each cross-section type.
Value - Type the Smart 3D insulation encasement type design parameter to be mapped.
Attribute Name - Type the name of the PDMS attribute to which Value is mapped.
Attribute Value - Type the PDMS attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

Export to PDMS User's Guide 123


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

StructureMatSpecMap
The StructureMatSpecMap sheet defines the value mapping of the MatRef attribute for each
Smart 3D material type.
SP3D Value - Type the value of the Smart 3D MatRef attribute to be mapped.
PDMS Value - Type the value of the PDMS attribute to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

124 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

SmartItemMaterialMap
Then SmartItemMaterialMap sheet defines mapping between Smart 3D footing and equipment
foundation objects and their assemblies and PDMS MatRef attributes.
Value - Type the Smart 3D footing, equipment foundation, or assembly object to be mapped.
Attribute Name - Type the appropriate PDMS MatRef attribute to which Value is mapped.
Attribute Value - Type the required attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

StructPartNumbersMap
The StructPartNumbersMap sheet maps Smart 3D structural object part numbers to the
appropriate PDMS MatRef attribute.
Value - Type the Smart 3D structural object part number to be mapped.
PDMS Attribute - Type the PDMS MatRef attribute value.
Attribute Value - Type the required MatRef attribute value.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

Export to PDMS User's Guide 125


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.
Ignore - Specify whether the item should be ignored during export.

StructClassAdditionalAttributes
The StructClassAdditionalAttributes sheet maps additional attributes between Smart 3D
cross-sections and PDMS.
Value - Type the Smart 3D cross-section attribute to be mapped.
Attribute Name - Type the name of the PDMS attribute to which Value is mapped. The
attributes GType, spre, and PLine are required.
Attribute Value - Type the required values for each of the PDMS attributes.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute called NPD in the source system and one called NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute. You must define a SheetName
for the spre and PLine attributes.
GType is a direct map; thus, no additional mapping information is necessary.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Rather the value used for Diameter would result from the following calculation: Diameter =
2 * Radius.
Ignore - Specify whether the item should be ignored during export.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

126 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Cross-Section Maps
The sheets listed in the following table define value mapping between the Smart 3D
cross-section name and the PDMS cross-section SpecRef attribute for that specific
cross-section type.
Each sheet name is identified by a unique string constructed by appending the
cross-section standard with the cross-section type separated by a dash ( - ).
 AISC-LRFD-HSSC  AISC-LRFD-W
 AISC-LRFD-PIPE  AISC-LRFD-M
 AISC-LRFD-L  AISC-LRFD-S
 AISC-LRFD-C  AISC-LRFD-ST
 AISC-LRFD-WT  AISC-LRFD-HP
 AISC-LRFD-HSSR  AISC-LRFD-MC
SP3D Value - Type the name of the Smart 3D cross-section to be mapped.
PDMS Value - Type the PDMS cross-section SpecRef attribute to which SP3D Value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

Export to PDMS User's Guide 127


Appendix: Export to PDMS Workbook

Cardinal Point Maps


The sheets listed in the following table define value mapping between Smart 3D cardinal points
and the PDMS PLine attribute for a specific cross-section type.
Each sheet name is identified by a unique string constructed by appending the GType
value of that cross-section type with the string PLine separated by an underscore ( _ ).
 TUBE_PLine  BOX_PLine
 ANG_PLine  BEAM_PLine
 DINU_PLine  SBM_PLine
 TEE_PLine  STEE_PLine
SP3D Value - Type the value of the Smart 3D cardinal point to be mapped.
PDMS Value - Type the value of the PDMS PLine attribute to which SP3D Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Remarks - Provides additional comments from Intergraph on default delivered mapping.

128 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Marine Cross-Section Maps


The sheets listed in the following table define value mapping between the Smart 3D
cross-section name and the PDMS cross-section SpecRef attribute for that specific
cross-section type.
Each sheet name is identified by a unique string constructed by appending the
cross-section standard with the cross-section type separated by a dash (-).
ShipShapes-I ShipShapes-B ShipShapes-FB
ShipShapes-ISType ShipShapes-CSType ShipShapes-H
ShipShapes-T_XType ShipShapes-TSType ShipShapes-EA
ShipShapes-RT ShipShapes-P ShipShapes-BUT
ShipShapes-C_SS ShipShapes-UA ShipShapes-BUTL2
ShipShapes-BUTL3 ShipShapes-HalfR ShipShapes-R
SP3D Value - Type the name of the Smart 3D cross-section to be mapped.
PDMS Value - Type the PDMS cross-section SpecRef attribute to which the Smart 3D
cross-section is mapped.

Load Point Maps


The sheets listed in the following table define value mapping between Smart 3D load/key points
and the PDMS PLine attribute for a specific cross-section type.
Each sheet name is identified by a unique string constructed by appending the GType
value of that cross-section type with the string PLine separated by an underscore (_).
I_PLine B_Pline FB_Pline
ISType_Pline CSType_Pline H_Pline
T_XType_Pline TSType_Pline EA_Pline
RT_Pline P_Pline BUT_Pline
C_SS_Pline UA_Pline BUTL2_Pline
BUTL3_Pline HalfR_Pline R_Pline
SP3D Value - Type the name of the Smart 3D load point/key point to be mapped.
PDMS Value - Type the PDMS PLine attribute to which the specified Smart 3D load point/key
point is mapped.

Export to PDMS User's Guide 129


Appendix: Export to PDMS Workbook

Supports Translation Maps


Use the Supports translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D support properties to the correct PDMS support attributes. Before exporting
Smart 3D supports model data to PDMS, you must modify these sheets to ensure that the
following criteria have been met:
 All of the support components in the Smart 3D model are mapped to corresponding
HANGER elements in PDMS.
The following Supports translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
SupportsClassMap - Maps the supported Supports classes between Smart 3D and PDMS.
This is the main mapping sheet for the Supports discipline. For more information, see
SupportsClassMap (on page 130).
CHgrPipeSupport - Maps piping supports attributes between Smart 3D and PDMS. For more
information, see CHgrPipeSupport (on page 131).
CHgrDuctSupport - Maps duct supports attributes between Smart 3D and PDMS. For more
information, see CHgrDuctSupport (on page 131).
CHgrCableTraySupport - Maps cable tray supports attributes between Smart 3D and PDMS.
For more information, see CHgrCableTraySupport (on page 132).
CHgrDesignSupport - Maps design supports attributes between Smart 3D and PDMS. For
more information, see CHgrDesignSupport (on page 133).
CHgrSupportComponent - Maps support component attributes between Smart 3D and PDMS.
For more information, see CHgrSupportComponent (on page 133).
HgrSupportGlobals - Defines global settings for hangers and support export. For more
information, see HgrSupportGlobals (on page 134).
SupportPartNumber - Defines PDMS SpecRef attributes for each type of support component.
For more information, see SupportPartNumber (on page 135).
SupportGTYPE - Defines PDMS GTypes for each type of Smart 3D support component. For
more information, see SupportGTYPE (on page 136).
SupportUserAttributes - Defines PDMS attributes and PDMS design parameters for each type
of support component. For more information, see SupportUserAttributes (on page 137).

SupportsClassMap
The SupportsClassMap sheet defines the Support class mapping between Smart 3D and
PDMS. The Support classes that are displayed on the SupportsClassMap sheet are the only
ones that are currently supported for export to PDMS. Do not modify any of the values on this
sheet.
SP3D Class Name - Displays the Smart 3D Support class to be mapped.
PDMS Class Name - Displays the PDMS Support class to which the Smart 3D Class Value
Name is mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExportMapping.xls workbook
that maps Smart 3D Support class attributes to PDMS.

130 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

CHgrPipeSupport
The CHgrPipeSupport sheet maps pipe support attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D pipe support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CHgrDuctSupport
The CHgrDuctSupport sheet maps duct support attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D duct support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.

Export to PDMS User's Guide 131


Appendix: Export to PDMS Workbook

 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CHgrCableTraySupport
The CHgrCableTraySupport sheet maps cable tray support attributes between Smart 3D and
PDMS.
SP3D Attribute - Type the Smart 3D cable tray support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.

132 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

CHgrDesignSupport
The CHgrDesignSupport sheet maps design support attributes between Smart 3D and PDMS.
SP3D Attribute - Type the Smart 3D design support attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 133


Appendix: Export to PDMS Workbook

CHgrSupportComponent
The CHgrSupportComponent sheet maps support component attributes between Smart 3D
and PDMS.
SP3D Attribute - Type the Smart 3D support component attribute to be mapped.
PDMS Attribute - Type the name of the PDMS attribute to which the SP3D Attribute value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

134 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

HgrSupportGlobals
The HgrSupportGlobals sheet displays mapping between Smart 3D SP3DPartNumber,
SP3DPartNumber_GTYPE, SP3DPartNumber_UA, and PDMS elements. The first two
properties cross-reference to their respective value mapping sheets and the third property in this
sheet cross-references to its respective attribute mapping sheet. The values contained on this
sheet define the global settings for Hangers and Supports model export and should not be
modified.
SP3D Attribute - Displays the name of the Smart 3D property to map.
PDMS Attribute - Displays the name of the PDMS attribute to which the SP3D Attribute value
is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.
See Also
SupportPartNumber (on page 135)
SupportGTYPE (on page 136)
SupportUserAttributes (on page 137)

Export to PDMS User's Guide 135


Appendix: Export to PDMS Workbook

SupportPartNumber
The SupportPartNumber sheet maps part numbers of support components to the PDMS
SpecRef attribute of PDMS HANGER elements.
SP3D Value - Type the part number of the Smart 3D support component to be mapped.
PDMS Value - Type the SpecRef attribute of the PDMS HANGER element to which SP3D
Value is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

SupportGTYPE
The SupportGTYPE sheet maps part numbers of support components to the GTYPE of PDMS
HANGER elements.
SP3D Value - Type the part number of the Smart 3D support component to be mapped.
PDMS Value - Type the GTYPE of the PDMS HANGER element to which SP3D Value is
mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.

136 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

SupportUserAttributes
The SupportUserAttributes sheet maps additional properties for Smart 3D support component
part numbers.
Value - Type the Smart 3D support component part number to be mapped.
Attribute Name - Type the PDMS attribute which is created as an additional attribute for Value.
Attribute Value - Type the required attribute value.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

Export to PDMS User's Guide 137


Appendix: Export to PDMS Workbook

Units Translation Maps


Use the units translation mapping sheets in the S3DPDMSExportMapping.xls workbook to
map Smart 3D systems of units to the correct PDMS units attributes. Before exporting Smart 3D
units data to PDMS, you must modify these sheets to ensure that all of the system of units in the
Smart 3D model are mapped to corresponding system of units in PDMS.
After all of the mapping is completed in the S3DPDMSExportMapping.xls
workbook, run the PDMS Export Validation command to validate the mapping data in the
workbook. Any missing entries reported by the validation tool should be resolved. For more
information, see PDMS Export Validation (on page 31).
The following unit translation maps are delivered in the S3DPDMSExportMapping.xls
workbook:
UnitsClassMap - Defines the system of units mapping between Smart 3D and PDMS. The unit
systems that are displayed on this sheet are the only ones that are currently supported for
export to PDMS. For more information, see UnitsClassMap (on page 138).
UnitsGlobalsMap - Displays mapping between Smart 3D system of units and PDMS system of
units. For more information, see UnitsGlobalsMap (on page 138).
UnitsAdditionalAttributeMap - Maps Smart 3D measuring parameters and their units to those
on PDMS. For more information, see UnitsAdditionalAttributeMap (on page 139).

UnitsClassMap
The UnitsClassMap sheet defines the system of units mapping between Smart 3D and PDMS.
The unit systems that are displayed on this sheet are the only ones that are currently supported
for export to PDMS.
Do not modify any of the values on this sheet.
SP3D Class Name - Displays the Smart 3D units class to be mapped.
PDMS Class Name - Displays the PDMS units class to which the SP3D Class Name value is
mapped.
Attributes Sheet - Displays the sheet name in the S3DPDMSExport.xls workbook that maps
Smart 3D units class properties to PDMS.

UnitsGlobalsMap
The UnitsGlobalsMap sheet displays mapping between Smart 3D system of units and PDMS
system of units.
The values contained on this sheet define the global settings for piping model export and should
not be modified.
SP3D Attribute - Displays the name of the Smart 3D attribute to map.
PDMS Attribute - Displays the name of the PDMS attribute to which the SP3D Attribute value
is mapped.
MapType – Defines the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.

138 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes


for the value of a given attribute.
 PatternDef - Used to create a new value of an attribute that is based on a specific pattern.
 A value can be any valid regular expression.
 CharacterDef - Used to split the value of an attribute using a delimiter or character position
and string length to generate new attributes.
SheetName – Defines the name of the sheet in the S3DPDMSExportMapping.xls workbook
that contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to mapped, if one is
needed. For example, if the source system has an attribute Radius that needs to be mapped to
the destination system's attribute Diameter, the software cannot substitute one value for the
other. Instead the value used for Diameter would result from the following calculation: Diameter
= 2 * Radius.
Value - Specifies the value of the PDMS attribute.
Label – Specifies whether the Smart 3D attribute is a label. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase. For more information, see Mapping Tips (on page
43).
Ignore - Specifies whether the item is ignored during export. Type TRUE/YES or FALSE/NO.
Entries can be in lowercase or uppercase.

UnitsAdditionalAttributeMap
The UnitsAdditionalAttributeMap sheet maps Smart 3D measuring parameters and their units
to those on PDMS.
SP3D Value – Do not modify this entry.
PDMS Attribute - Do not modify this entry.
Attribute Value - You can change these values so that PDMS can accept these strings but
there are some limitations.
MapType – Type the map type of the attribute. Acceptable values are as follows:
 NameDef - Used when the value needs to be directly transferred. For example, there is an
attribute named NPD in the source system and one named NominalDiameter in the
destination system. Because both attributes have the same meaning, the value just needs to
be transferred between the two systems. By default, if no MapType is specified, NameDef is
used.
 ValueDef - Used when the value of an attribute needs to be mapped before it is transferred.
 AdditionalAttributeDef - Used when it is necessary to create new or additional attributes
for the value of a given attribute.
SheetName – Type the name of the sheet in the S3DPDMSExportMapping.xls workbook that
contains additional mapping information related to the attribute, if any exists.
Formula – Type the formula used to calculate the value of the attribute to map, if one is needed.
For example, if the source system has an attribute Radius that needs to be mapped to the
destination system's attribute Diameter, the software cannot substitute one value for the other.
Rather the value used for Diameter would result from the following calculation: Diameter = 2 *
Radius.

Export to PDMS User's Guide 139


Appendix: Export to PDMS Workbook

Ignore - Specify whether the item should be ignored during export.

 You can change the way a unit is written to the datal file but should not change it into its
derived forms. For example, if distance is written in millimeters, the mapping sheet can be
modified to write MM, mm, or Millimeter but not centimeter or kilometer.
 You cannot add new measuring parameters to the sheet.

140 Export to PDMS User's Guide


Appendix: Export to PDMS Workbook

Export to PDMS User's Guide 141


Appendix: Export to PDMS Workbook

142 Export to PDMS User's Guide


Index
CPShapeValueMap • 66
A CPSmartEquipmentMap • 55
CPStraightNozzleCatRefMap • 61
Appendix CPStructuralSystemMap • 76
Export to PDMS Workbook • 45 CPUnitSystemMap • 77
Cross-Section Maps • 127
B CurvedERProfilePartAttrsMap • 117
BeamPartAttrsMap • 118 CurvedMemberPartAttrsMap • 105
CurvedPlatePartAttrsMap • 112
CurvedSAStiffenerPartAttrsMap • 120
C CurvedStiffenerPartAttrsMap • 115
Cardinal Point Maps • 128
CatalogComponentSPREFMap • 93
CatalogInstrumentSPREFMap • 94
D
CatalogSpecialtySPREFMap • 94 DesignSupportAttrsMap • 82
CHgrCableTraySupport • 132 DesParamAdditionalAttrMap • 65
CHgrDesignSupport • 133 Documentation Comments • 12
CHgrDuctSupport • 131 Documentation Set • 9
CHgrPipeSupport • 131 DuctComponentAttrsMap • 81
CHgrSupportComponent • 134 DuctRunSpecMap • 86
Configure the PDMS export initialization file DuctSupportAttrsMap • 82
• 23
CoordinateSystemMap • 102 E
CPAreaSystemMap • 70 Electrical Translation Maps • 46
CPCableTrayNozzleMap • 60 ElectricalClassMap • 46
CPCablewayAttrMap • 48 ElectricalComponentSPREFMap • 52
CPConduitNozzleMap • 59 ElectricalGlobalsMap • 50
CPConduitSystemMap • 71 ElectricalPartIdentifierMap • 51
CPDuctingSystemAttrMap • 79 ElectricalRunSpecMap • 51
CPDuctingSystemMap • 72 ElectricalSupportAttrsMap • 49
CPDuctRunAttrMap • 80 ElevationPlaneMap • 103
CPElbowNozzleCAtRefMap • 61 EndConnectionMap • 99
CPElectricalSystemAttrMap • 47 EquipGlobalsMap • 62
CPElectricalSystemMap • 73 Equipment Translation Maps • 53
CPEquipmentComptMap • 55 EquipmentClassMap • 54
CPHvacNozzleCatRefMap • 62 EquipmentFoundationAttrsMap • 110
CPHVACNozzleMap • 58 Export Model • 36
CPMachinerySystemMap • 73 Export model data to PDMS • 38
CPMPipeRunMap • 90 Export Model to PDMS Datal Dialog Box •
CPMSystemAttrMap • 80 39
CPMSystemMap • 70 Exporting Model Data to PDMS • 13
CPNozzleAdditionalAttributes • 67
CPPipelineSystemMap • 89
CPPipelineSystemMapEx • 74 F
CPPipeNozzleMap • 57 FootingAttrsMap • 110
CPPipingSystemMap • 75
CPRteCableTrayComponentAttrMap • 48
CPShapeAdditionalAttributes • 66
CPShapeMap • 56

Export to PDMS User's Guide 143


Index

G P
Generate catalog and reference data in PartNumberAdditionalAttributes • 64
Smart 3D and PDMS formats for PDMS PartNumberValueMap • 63
export • 36 PDMS Export Initialization File Options • 23
GridLineMap • 104 PDMS Export Validation • 31
PDMS Export Validation Dialog Box • 32
H Performance Tips • 41
PipeComponentAttrsMap • 96
HandRailAttrsMap • 109 PipeInstrumentAttrsMap • 97
HgrSupportGlobals • 135 PipeRunSpecMap • 92
Hierarchy Translation Maps • 69 PipeSpecialtyAttrsMap • 98
HierarchyClassMap • 69 PipeSupportAttrsMap • 98
HoleFittingAttrsMap • 121 Piping Translation Maps • 88
HVAC Translation Maps • 78 PipingClassMap • 89
HVACClassMap • 79 PipingGlobalsMap • 91
HVACComponentSPREFMap • 85 PlanarPlatePartAttrsMap • 112
HVACDesParamMap • 86 Preface PDMS Guide • 9
HVACEndPreparationMap • 85 Project Creation Estimates • 43
HVACGlobalsMap • 83
HVACPartIdentifierMap • 84
S
I Set up the PDMS and Smart 3D catalogs •
21
Import/Export Issues • 42 SlabAttrsMap • 107
InsulationAttrMap • 123 SmartItemMaterialMap • 125
InsulationAttrsMap • 106 SP3DPartIdentifierMap • 92
InsulationSpecAttrMap • 123 StairAttrsMap • 107
StructClassAdditionalAttributes • 126
L StructPartNumbersMap • 125
LadderAttrsMap • 108 Structure Translation Maps • 100
LeafBeamSystemAttrsMap • 118 StructureClassMap • 102
LeafERSystemAttrsMap • 115 StructureGlobalsMap • 122
LeafPlateSystemAttrsMap • 111 StructureMatSpecMap • 124
LeafStiffenerSystemAttrsMap • 113 SupportGTYPE • 136
LinearERProfilePartAttrsMap • 116 SupportPartNumber • 136
LinearMemberPartAttrsMap • 104 Supports Translation Maps • 130
LinearSAStiffenerPartAttrsMap • 119 SupportsClassMap • 130
LinearStiffenerPartAttrsMap • 114 SupportUserAttributes • 137
Load Point Maps • 129
T
M Troubleshooting • 41
Mapping Tips • 43
Marine Cross-Section Maps • 129 U
Units Translation Maps • 138
N UnitsAdditionalAttributeMap • 139
NozzDesParamAdditionalAttrMap • 68 UnitsClassMap • 138
NPDSpecificSPREFMap • 93 UnitsGlobalsMap • 138

O V
OnFlyInstrumentSPREFMap • 95 Validate mapping details • 31
OnFlySpecialtySPREFMap • 95

144 Export to PDMS User's Guide


Index

W
What's New in Export to PDMS • 12

Export to PDMS User's Guide 145

You might also like