PDS 3D options - Intergraph Smart Interop Publisher - Help

Intergraph Smart Interop Publisher Help

Language
English
Product
Intergraph Smart Interop Publisher
Search by Category
Help
Smart Interop Publisher Version
16.2

PDS Published

Allows you to translate PDS-published source files (.zvf, .xml, and .xrg) into a Smart Model .zvf. Set the following locations of the configuration files you can modify to translate PDS 3D-generated files. The files can be opened in Smart Review, Smart 3D, and SmartPlant Foundation.

Schema

Specifies the PDSComponent.xml file which is required to obtain the property definitions and to decipher the contents of the label files published from PDS 3D. The software defaults to the file in the source file location. Otherwise, the software uses the file in the Smart Interop Publisher installation folder.

Relationship Mapping

Specifies the RelationshipMapping.txt file you can use to filter out the component relationships from PDS 3D that are not required. The software defaults to the RelationshipMapping.txt file in the source file location. Otherwise, the software uses the file in the Smart Interop Publisher installation folder.

PDS Legacy

Allows you to specify pipeline and equipment data from .dgn/.drv source files exported from PDS for translation to a Smart Model.

Nozzle Parent Identifier

Specifies the label name in the .drv source files that relates a nozzle to its parent equipment. Nozzles belong to a parent equipment. By default, the software uses Equip no as the label name that specifies the parent equipment for a nozzle. Type in the required label name if Equip no is not used in your .drv files.

Pipeline Number Identifier

Specifies the label name in the .drv source files that defines a GenericSystemHierarchy relationship between a pipe part and its parent pipeline. Pipe parts belong to a parent pipeline. If you use a label other than Line no in your .drv files, type in the label name used for the pipeline parent. If you require part of that label to be mapped as the pipeline name, define the Pipeline Number Delimiter indicating the position where the string should be truncated.

Pipeline Number Delimiter

Specifies the delimiter used to create the pipeline names from the .drv source files. The default Pipeline Number Delimiter value is the hyphen (-). You can enter a space for no delimiter setting, which causes the entire name (string) of the label specified as the Pipeline Number Identifier to be used as the pipeline number. If another character is specified, the string occurring before the Pipeline Number Delimiter character is used as the pipeline name.

The property format displays as [pipeline]-[specification]-[insulation purpose]. For example, a Line no property value of WC800101-260036-N results in the pipeline number WC800101, which is the string occurring before the first hyphen (-).

Resolve duplicate linkages

Allows you to publish PDS legacy .dgn files with duplicate linkages to SmartPlant Foundation. This option causes the software to create new, unique linkages for PDS objects. By default, the option is not active.

We recommend that you select this option if you are having publishing issues, or if your PDS legacy source files have duplicate linkages. If you have already translated and published source files containing either unique or mixed linkages, and are satisfied with the resulting objects in SmartPlant Foundation and Smart Review, then do not select this option.

Impacts to published files:

For SmartPlant Foundation and downstream clients:

If you select this option and then run an update on the PDS legacy-based Smart Models, the software re-publishes the model and creates new objects. The new objects are assigned new UIDs. For downstream SPF clients such as SmartPlant Construction, the new UIDs cause object assignments to be updated. For example, any work packages containing specific objects must be updated.

For Smart Review:

If you select this option, update the PDS legacy-based Smart Models, and then open them in Smart Review, any display sets that were created based on DMRS linkages must be re-created.