PDS Exporter Configuration Files - Intergraph Smart 3D - Administration & Configuration - Hexagon

Intergraph Smart 3D PDS Conversion to Smart 3D

Language
English
Product
Intergraph Smart 3D
Subproduct
Plant Design System
Search by Category
Administration & Configuration
Smart 3D Version
13.1
Smart Interop Publisher Version
17

The PDS Model Data Exporter Command uses configuration files delivered in the ..\PDShell\PDExportToSP3D\config folder to map PDS electrical, equipment, HVAC, and piping attributes to XML attribute tags. You can use the delivered configuration files without editing if you have not customized any of the PDS "out-of-the-box" attributes. However, if you have customized PDS attributes, you must edit the configuration files to match your changes.

In addition, PDS does not have some attributes that are required for importing into Smart 3D. Examples include Insulation Material, Coatings, and Cleaning Responsibility. These attributes are given a hard coded text in the delivered configuration file and are marked with a comment "Not available in PDS." If you have added a user defined attribute to your PDS project to maintain any of these attributes, please change the configuration file accordingly to map those user attributes to the appropriate XML attributes.

The most common format in the configuration file to map the PDS attributes to the XML tags is the 'ExxAnn' notation, where 'xx' is the table number and 'nn' is the attribute number in the ..\PDShell\ddl\design.ddl, ..\PDShell\ddl\eqp.ddl, and the ..\PDShell\ddl\project.ddl files.

Electrical Configuration File

The electrical configuration file is named ElectricalExportConfig.txt. This file maps XML attributes to EE Raceway attributes and to any user defined user attributes.

You can define attributes using one of three formats:

  • @xmlAttribute = EErwayAttribute notation. For example, @spec = ee_spec_key.

  • @xmlAttribute = "Some string" notation. This hard coded text is useful when attributes that are required to imported, but are not available in PDS (for example, Insulation Material or Insulation Temperature).

@xmlAttribute = 'ExxAnn' notation, where 'xx' is the table number and 'nn' is the attribute number in the ..\PDShell\ddl\project.ddl file. Use this option to map PDS project database attributes. This format is only available for PDS integrated raceway projects. The available table numbers are:

  • 101 = Project Data Attribute
    111 = Discipline Data Attribute
    112 = Area Data Attribute
    113 = Model Data Attribute

Equipment Configuration File

The equipment configuration file is named EquipmentExportConfig.txt. This file defines:

  • the user configurable equipment attributes on equipment.

  • which datum point's origin and orientation should be used to export to the XML file as the parametric's origin and orientation.

To specify an attribute, you can define using:

  • hard coded text such as "Required". This hard coded text is useful when attributes that are required to imported, but are not available in PDS (for example, Insulation Material or Insulation Temperature).

Using the 'ExxAnn' notation, where 'xx' is the table number and 'nn' is the attribute number in the ..\PDShell\ddl\eqp.ddl and the ..\PDShell\ddl\project.ddl files. The available table numbers are:

  • 21 = Equipment
    22 = Nozzle
    101 = Project Data Attribute
    111 = Discipline Data Attribute
    112 = Area Data Attribute
    113 = Model Data Attribute Implicit entity relations can also be used. For example, using a E113A5 on an equipment item would get the model_no of the equipment model containing the equipment being exported. Similarly, using a E112A3 on an equipment's data would get the Area_no of the model containing the equipment being exported.

Importing and Placing G-Type Equipment

To import G-Type equipment (graphics only), add @ImportAsGTypeShape = "true", as shown in the following example:

G-Type equipment is placed in Smart 3D when the correct mapping between the XML and Smart 3D Catalog is not found and @ImportAsGTypeShape = "true" is defined in the XML. The G-Type equipment is placed in Smart 3D with a defined Aspect mapping.

The following is an example of a PDS Equipment model containing the parametric A031 (Side Ladder).

  • Equipment Export exports this Equipment to XML as a 'Parametric' (corresponding to the A031 Parametric Attributes) + 'CustomShape' (corresponding to its Access Envelope) + 'CustomShape' (Corresponding to the actual A031 graphic).

  • A031's Access Envelope has the primitive Category as "Access Hard" and hence, the corresponding XML custom shape's aspect is exported as "Access Hard".

  • The second Custom Shape which actually represents the A031's graphic has its primitive category as 'Undefined' and hence it is exported as blank to the XML.

  • The Equipment Export exports 'undefined' primitive categories as blank aspects to the XML and Equipment Import takes care of setting those blank aspects as Simple Physical.

The following are the primitive categories and their corresponding XML Aspects.

PDS Primitive Category XML Aspect
not defined blank
physical Simple Physical
maint_hard Maintenance Hard
maint_soft Maintenance Soft
access_hard Access Hard
access_soft Access Soft
safty_hard Safety Hard
safty_soft Safety Soft
const_hard Construction Hard
const_soft Construction Soft
hole Hole

Smart 3D has the following Aspects available that can be set on a Shape.

SimplePhysical
ReferenceGeometry
Operation
Maintenance
Insulation
DetailPhysical

You can map the XML aspects to these Smart 3D aspects using the AspectMap sheet in Import Configuration.

HVAC Configuration File

The HVAC configuration file is named HVACExportConfig.txt. This file maps XML attributes to HVAC attributes and to any user defined user attributes.

You can define attributes using two formats:

  • @xmlAttribute = "Some string" notation. This hard coded text is useful when attributes that are required to imported, but are not available in PDS (for example, Insulation Material or Insulation Temperature).

  • @xmlAttribute = 'ExxAnn' notation, where 'xx' is the HVAC table number and 'nn' is the attribute number in that table.

Piping Configuration File

The piping configuration file is named PipingExportConfig.txt. This file defines:

  • the user configurable Piping Segment Attributes on: Piping System data, Pipeline System data, and Pipe Run data.

  • the user configurable attributes on: components, pipes, and instruments.

  • defines the user attributes to export on: pipe runs, components, pipes, and instruments.

To specify an attribute, you can define using:

  • hard coded text such as "Required". This hard coded text is useful when attributes which are required to imported, but are not available in PDS (for example, Insulation Material, Steam Out Pressure, and Steam Out Requirement).

  • Using the 'ExxAnn' notation, where 'xx' is the table number and 'nn' is the attribute number in the ..\PDShell\ddl\design.ddl and the ..\PDShell\ddl\project.ddl files. The available table numbers are:

12 = Piping Segment
34 = Piping Component
50 = Pipe
67 = Piping Instrument
101 = Project Data Attribute
111 = Discipline Data Attribute
112 = Area Data Attribute
113 = Model Data Attribute

Implicit entity relations can also be used. For example, using a E113A5 on a pipe run would get the model_no of the Piping Model containing the segment of the pipe run being exported. Similarly, using a E112A3 on a pipe's data would get the Area_no of the model containing the pipe being exported.

Port attributes are specified using the ExxPAnn notation, in which 'PA' means the Port Attribute. 'nn' is the serial number of the port attribute, which could be 1 to 14 for Components, 1 to 9 for Pipes, or 1 to 14 for Instruments.