Pds Guide

(1)

SmartPlant 3D

Plant Design System (PDS) Guide

(2)

Copyright

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.

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the

Contractor Rights in Technical Data clause at DFARS 252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of

the License clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of Commercial Computer

Software---Restricted Rights at 48 CFR 52.227-19, as applicable.

Unpublished---rights reserved under the copyright laws of the United States. Intergraph Corporation

Huntsville, Alabama 35894-0001

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. 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 discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. 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.

Trademarks

Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, IntelliShip, INtools, ISOGEN, PDS, and MARIAN are registered trademarks of Intergraph Corporation. 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. Portions of 2D DCM, 3D DCM, and HLM from D-Cubed Limited are incorporated. All rights reserved. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other brands and product names are trademarks of their respective owners.

(3)

Preface

This document describes how to intergrate Plant Design System (PDS®) with SmartPlant® 3D. This document pulls together information from several other

SmartPlant 3D administrative and user documentation guides. The content includes a list of referencing PDS projects, exporting data from PDS and importing data into SmartPlant, conversion of EDEN symbols, and other administrative tasks.

(6)

SmartPlant 3D Documentation Set

The SmartPlant® 3D documentation set is available as Adobe® PDF files. The content of the PDF files is the same content as online Help. To access these PDF documents in the software, click Help > Printable Guides.

The documentation set is divided into four categories:

• Administrative guides contain information about installing, configuring, customizing, and troubleshooting SmartPlant 3D.

• User's guides provide command reference and how-to information for working in each SmartPlant 3D task.

• Reference data guides define the reference data workbooks. Not all tasks have reference data.

• Third-party guides from other vendors for software that works with SmartPlant 3D.

Administrative Guides

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, managing interference detection, defining and managing locations for Global Workshare, controlling duplication and

consolidation of plants, tools for synchronization, regeneration of report databases, and version upgrade.

SmartPlant 3D Database Integrity Guide - Provides information about the error messages in the database integrity reports, including meaning, cause, and possible corrective action.

SmartPlant 3D Installation Guide - Provides instructions on installing and configuring the software on both the client and server computers.

SmartPlant 3D/IntelliShip Programmer's Guide - Provides information about custom commands, naming rules, and symbol programming.

SmartPlant 3D Interference Checking Guide - Provides information on installing, configuring, and using the interference detection service.

SmartPlant 3D Plant Design System (PDS) Guide - Provides all information needed to use PDS with SmartPlant 3D. Topics include referencing active PDS projects in SmartPlant 3D, exporting PDS data and importing that data into SmartPlant 3D, converting PDS reference data to SmartPlant 3D reference data, and converting EDEN symbols to Visual Basic symbols.

(7)

SmartPlant 3D Release Bulletin - Provides what's new, hardware/software requirements, and support information for the current release.

SmartPlant 3D The Engineering Framework Reference Guide - Provides information about installing, configuring, and using The Engineering Framework with SmartPlant 3D.

SmartPlant 3D Troubleshooting Guide - Provides information on how to resolve errors that you may encounter in the software by documenting troubleshooting tips, error messages, and to do list messages.

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, navigating in the model, precision input, filtering, manipulating views, and running reports. Drawings and Reports User's Guide - Provides information about creating drawing and report deliverables.

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.

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, cableway, and conduit supports in the model.

HVAC User's Guide - Provides instructions for routing HVAC duct.

Piping User's Guide - Provides instructions for routing pipe and placing valves, taps, and pipe joints.

Space Management User's Guide - Provides instructions for placing volumes (such as drawing volumes, obstruction zones) 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.

(8)

Structure User's Guide - Provides instructions for placing structural members such as: beams, columns, braces, slabs, openings, stairs, ladders, equipment foundations, and handrails.

Systems and Specifications User's Guide - Provides instructions for creating systems and their hierarchies and selecting which specifications are available for each system type.

SmartPlant 2D Symbols User's Guide - Provides instructions for creating cross section symbols.

Reference Data Guides

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.

Equipment and Furnishings Reference Data Guide - Provides information about equipment reference data and name rules.

Hangers and Supports Reference Data Guide - Provides information about hangers and supports reference data.

HVAC Reference Data Guide - Provides information about HVAC reference data. Piping Reference Data Guide - Provides information about piping reference data including piping specifications, piping specification rules, piping parts, piping symbols, and name rules.

SmartPlant 3D Reference Data Guide - Provides instructions about the Bulkload utility, codelists, and the reference data common to several disciplines.

SmartPlant 3D Symbols Reference Data Guide - Provides information about the Visual Basic Part Definition Wizard and the three-dimensional symbols used in all tasks.

Space Management Reference Data Guide - Provides information about space management reference data.

Structure Reference Data Guide - Provides information about structural reference data and name rules.

(9)

ISOGEN Guides

AText Reference Guide - Provides information about alternative text for isometric drawings. This guide is from Alias, the makers of ISOGEN®.

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

Documentation Comments

(10)

What's New with Plant Design System (PDS)

Integration

The following changes have been made to the PDS® integration with SmartPlant guide.

Version 2007.2

• A topic explaining software limitations is now available in the documentation. For more information, refer to Limitations.

• You can validate the data contained in the XML import file against its corresponding XML schema. For more information, refer to Validate XML Import File with the XML Schema.

• You can export different raceway models to several different XML files using the Raceway Model Data Exporter utility. For more information, refer to Export Raceway Model Data to an XML File.

Version 2007.1

• G-Type equipment is placed in SmartPlant 3D when the correct mapping between the XML and SP3D Catalog is not found and

@ImportAsGTypeShape = "true" is defined in the XML. The G-Type

equipment is placed in SmartPlant 3D with a defined Aspect mapping. For more information, refer to PDS Exporter Configuration Files: An Overview.

Version 2007

• PMC files (Any file(s) with a .pmc extension, in the PDSAsciiFiles directory, will be translated. This information is available in the Create PDS Export Data Files section.

• PDS Model Data Exporter and the Import menu commands can now be installed using a separate setup.exe. This setup.exe is delivered on the SmartPlant 3D product CD. This functionality must be purchased separately and requires a separate serial number for installation.

(11)

PDS Plant Design System: An Overview

PDS® Plant Design System is a comprehensive, intelligent computer-aided design/engineering (CAD/CAE) application for plant design, construction, and operations. The market's leading solution for plant design and engineering, PDS fits into corporate computing strategies - on a global scale and at the project level, with projects ranging from small plant revamps to multibillion-dollar offshore platform construction.

Intergraph has a well-established track record of providing migration paths to our newest technologies, including the SmartPlant environment, the most advanced plant design architecture in the industry. This document provides the information needed to migrate PDS to SmartPlant® 3D - helping you make the most of your investment. For more information or help with migration from PDS to SmartPlant 3D, please contact your local Intergraph representative or visit our Web site at

ppm.intergraph.com.

Important

• Only PDS Version 8.0, or later, is supported by SmartPlant 3D.

Referencing Existing PDS Projects

Even without translation of PDS data, SmartPlant 3D leverages your existing designs by enabling PDS design data to be referenced in the SmartPlant 3D model similar to the reference model capability within PDS. SmartPlant 3D is immediately useful for revamp projects with no PDS translation effort necessary. For more information, see Referencing a PDS Model: An Overview, page 13.

Specifications and Other RDB Information Translation

The capability to translate piping specifications from PDS to SmartPlant 3D is available and has been successfully applied to hundreds of piping specifications. You can migrate other RDB information, such as raceway, HVAC, and custom piping parts and parametric equipment, as well as naming rules to replace PDS labels. If you want to migrate your customized PDS RDB information to SmartPlant 3D, we can provide piping specification migration training if you want to carry out the migration internally, or you can have Intergraph turnkey this process since it is typically a one-time effort. For more information about doing it yourself, see Using the PDS

(12)

Projects/Model Translation

SmartPlant 3D supports the translation of objects and models from PDS.

Specifications for any special components need to be defined in SmartPlant 3D first before you can translate the special components from PDS. Intergraph consulting services are recommended for project and model translation to prepare data maps and PDS 3D data, import to SmartPlant 3D, and validate and make any needed

corrections and/or changes. Project/model translation tools require a separate license unless used in conjunction with Intergraph services. For more information, see Exporting Data from PDS: An Overview, page 21.

EDEN Code Translation

SmartPlant 3D also provides tools for translating customized EDEN code. These tools will save time versus creating new Microsoft® Visual Basic® symbols supported by SmartPlant 3D. Alternatively, Intergraph delivers a comprehensive set of symbols with SmartPlant 3D, possibly limiting the amount of EDEN code translation

necessary depending on your specific needs. If you desire to migrate your customized EDEN code to SmartPlant 3D, we can work with you to provide recommendations and estimates for your exact requirements. For more information about the EDEN translation tools, see Converting PDS EDEN to SmartPlant Visual Basic Symbols: An Overview, page 83.

Intergraph – Your Migration Partner

To help make your migration from PDS to SmartPlant 3D a seamless one, while at the same time allowing you to move at your own pace, Intergraph offers migration consulting services to support the entire process. With a 35-year tradition of innovation and customer commitment, Intergraph has the expertise and experience needed to help you make a painless transition from PDS to SmartPlant 3D. Uniquely combining the principles of data centricity, integration, and automation of best practices, our solutions deliver high value with an economical, quickly returned start-up investment. Contact us today at ppm.intergraph.com and let us help you with your unique migration needs.

Related Topics

• Converting PDS EDEN to SmartPlant Visual Basic Symbols: An Overview, page 83

• Exporting Data from PDS: An Overview, page 21

• Referencing a PDS Model: An Overview, page 13

(13)

Referencing a PDS Model: An Overview

You can enable your PDS design data to be referenced from the SmartPlant 3D model using the Database > New > PDS Model Reference command in the Project

Management task. Referencing a PDS project can only be performed on a computer on which the Project Management and SmartPlant 3D Server Connectivity options are installed.

Important

• You must have the PDS software installed on the computer from which you are creating the PDS reference. In addition to the standard PDS setup, an additional set of files external to PDS are also required. For

information about installing the required component and setting up your computer to reference PDS projects, see Install PDS Data Access, page 14.

After the PDS project is attached to the Plant, the referenced PDS model database name is displayed on the Database tab on the Plant Properties dialog box.

(14)

In a Global Workshare situation, PDS projects are manually copied from the Host to each Satellite location by a SmartPlant 3D administrator. After replication is

complete, you can use the Database tab on the Plant Properties dialog box to rename the PDS project to make it more distinguishable from referenced PDS projects at other Satellite locations. For example, you can name one AL_PDS and another Texas_PDS.

Related Topics

• Reference a PDS Project, page 18

• Un-reference a PDS Project, page 20

Install PDS Data Access

SmartPlant 3D integrates with PDS version 8.0 and higher, thereby extending your plant design capabilities. When you install the PDS data access setup files, you enable the software to communicate with PDS. As such, you can reference PDS design data in your model. You can also use the software to migrate piping specifications and associated catalog data from PDS, or directly translate PDS data into the software. You need to install the PDS Data Access component on the administration computer where you will use the Project Management task to reference the PDS project and on each client workstation that needs to reference the PDS project.

Before installing the PDS Data Access component, you must install the following prerequisite software on a computer on which the Project Management and

SmartPlant 3D Server Connectivity options are also installed:

• Batch Services

• RIS_Share (RIS Shared Components)

• SmartPlant License Manager

(15)

If you are accessing PDS projects from the same computer, then you need to install SmartPlant License Manager along with the other PDS products as required. For more information about acquiring these components, please contact Intergraph Support.

Locate the Schema File

1. Log on with a user account that has administrator privileges. 2. Install RIS if you have not already done so.

3. Click Start > All Programs > RISX.X > RIS Schema Manager. 4. In the RIS Schema Manager dialog box, click Schema File. 5. In the Schema File dialog box, click Locate Schema File. 6. Define the location of your PDS project schema file. 7. Click Apply.

8. Click Close.

Configure the Plant Design System Environment (PD_Shell)

1. Log on with a user account that has administrator privileges. 2. Install PD_Shell if you have not already done so.

3. Click Start > All Programs > PD_Shell > PDS Configure. 4. Click Modify.

5. Type the Proj_File information for the PDS project. 6. Type the Proj_Addr information for the PDS project. 7. Click Continue.

8. Click OK.

Create Batch Queues

1. Log on with a user account that has administrator privileges. 2. Install Batch Services if you have not already done so. 3. Click Start > All Programs > PD_Shell > PDS Queue. 4. Create a batch queue for PD_Shell.

Verify Access to the Project in PD_Shell

1. Click Start > All Programs > PD_Shell > PD_Shell.

2. Verify that the PDS project that you want to reference displays in the PD_Shell environment. If it is not available in the PD_Shell environment, you will not be able to reference it.

(16)

Install PDS Data Access

1. Log on with a user account that has administrator privileges. 2. Insert the Intergraph SmartPlant 3D Product CD.

Tip

• If the CD does not start automatically, double-click Setup.exe in the root folder of the CD.

3. Select Prerequisite Software.

4. Select PDS Data Access Installation. 5. Click Continue on the Welcome page. 6. Click OK when the installation is complete.

(17)

New PDS Model Reference Command

Creates a reference to a PDS project in the model. The command is only enabled if you select a Plant (Model database) in the tree view of the Project Management task. You can only reference one PDS project per Plant

After the PDS project is attached to the plant, the referenced PDS model database name is displayed on the Databases tab on the Plant Properties dialog box.

Note

• MicroStation SmartSolids are not rendered when they are in a reference file.

Related Topics

(18)

PDS Model Reference Dialog Box

Referencing a PDS project into the model is performed on an administrator's computer on which the Project Management option is installed. PDS software is required in order to associate a PDS project with a SmartPlant 3D Plant (Model database).

Select PDS project (plant) to reference - Select the PDS project you want to

reference into the model. The software populates the list with the projects retrieved from PDS. Additionally, the list contains None as an option, so that the PDS project can be unreferenced.

Related Topics

• New PDS Model Reference Command, page 17

Reference a PDS Project

You must have the PDS software installed on the computer from which you are creating the PDS reference. An additional component, PDSDataAccess.dll, is also required. For information about installing this .DLL and setting up your computer to reference PDS projects, see Install PDS Data Access, page 14.

Note

• You can only reference one PDS project per Plant

1. Start the Project Management task, click Start > Programs > Intergraph

SmartPlant 3D > Project Management.

2. In the tree view, select the Plant (Model database) to which you want to associate a PDS project.

3. Click Database > New > PDS Model Reference.

Tip

• You can also right-click on a Plant (Model database) in the tree view, and then select New PDS Model Reference on the shortcut menu.

4. In the PDS Model Reference dialog box, select the PDS project that you want to reference.

(19)

5. Click OK to create the reference between the PDS project and the model.

Notes

• Referencing a PDS project into a SmartPlant 3D model can only be performed on a computer on which the Project Management option is installed.

• When you reference a PDS project, its information displays on the

Databases tab of the Plant Properties dialog box for the associated

model.

• The software reads in the categories as defined in the PDS project. Additionally, the software uses the PDS project seedfile to determine the working units to use for proper conversion. Consequently, in order to reference the model in the correct size, all the files in the PDS project must have the same working units.

• When you refresh the workspace, if you do not see the update for

discipline index numbers greater than 6, you must detach and reattach the PDS project to get the new files.

• MicroStation SmartSolids are not rendered when they are in a reference file.

• By default, access permissions on a referenced PDS project are identical to the access permissions for the model to which it is associated. The only way to change access permissions on the referenced PDS file is to change the access permissions of the associated model.

(20)

Un-reference a PDS Project

You can remove a reference between a Plant (Model database) and a PDS project on computer on which the Project Management option is installed. You can have only one PDS project referenced at a time. If you want to reference a different PDS project, you must first un-reference the current PDS project.

1. Start the Project Management task, click Start > Programs > Intergraph

SmartPlant 3D > Project Management.

2. In the Project Management tree view, right-click the Plant (Model database) that has been referenced with a PDS project.

3. Select New PDS Model Reference on the shortcut menu.

4. In the PDS Model Reference dialog box, select None in the Select PDS project

(plant) to reference list and click OK.

Related Topics

• New PDS Model Reference Command, page 17

(21)

Exporting Data from PDS: An Overview

You can export Piping, HVAC, Electrical, Equipment, and FrameWorks Plus data from PDS that can then be imported into SmartPlant 3D. The PDS Model Data Exporter, a utility delivered external to the product, exports Piping, HVAC,

Electrical, and Equipment data. FrameWorks Plus uses its own export command to create CIS/2 files for data transfer. The PDS Model Data Exporter utility requires the separate lease and installation of the SmartPlant 3D PDS Project Translators

(SEBY801AA).

Notes

• You can use the PDS Model Data Exporter with PDS version 8.0 or higher. If the PDS project is an earlier version, you need to upgrade the project before using the utility to export data.

The transfer of Piping, HVAC, Electrical, and Equipment PDS data is a multi-step operation:

1. Edit the configuration files to reflect the customizations you have made to PDS attributes. For more information about the configuration files, see PDS Exporter Configuration Files: An Overview, page 22.

2. Edit the mapping workbooks to reflect the customizations that you have made to the SmartPlant 3D properties. For more information about the mapping

workbooks, see Appendix A: Importer Workbooks, page 97.

3. The data must be exported from PDS to an XML formatted file for import into SmartPlant 3D. The PDS Model Data Exporter is delivered with SmartPlant 3D to create the necessary XML file for importing. Sample data files are delivered for all disciplines in the [Product Directory]\Translators\Samples. You can write third-party XML data files using the delivered sample files as an example. For more information on the PDS Model Data Exporter, see PDS Model Data Exporter, page 28.

4. You import the XML file data using the appropriate File > Import command in SmartPlant 3D. For more information, see Importing Data from PDS: An Overview, page 39.

Related Topics

(22)

PDS Exporter Configuration Files: An Overview

The PDS Model Data Exporter utility 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 SmartPlant 3D. For example, Insulation Material, Coatings, Cleaning Responsibility, and so forth. 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.

(23)

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

(24)

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 SmartPlant 3D when the correct mapping between the XML and SP3D Catalog is not found and @ImportAsGTypeShape = "true" is defined in the XML. The G-Type equipment is placed in SmartPlant 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 it's 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 it's primitive category as 'Undefined' and hence it is exported as blank to the XML.

(25)

• 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

SmartPlant 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 SP3D 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.

(26)

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, Steam Out

Requirement, and so forth).

• 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.

(27)

Install PDS Export Tools

Installing the PDS Export Tools component further extends the PDS integration capabilities by allowing you to export Piping, HVAC, Electrical, Equipment, and Structure model data from PDS into SmartPlant 3D.

Before installing the PDS Export Tools component, you must install the following prerequisite software on a computer on which the Project Management and

SmartPlant 3D Server Connectivity options are also installed:

• Batch Services

• RIS_Share (RIS Shared Components)

• MicroStation

• SmartPlant License Manager

• PD_Shell (Plant Design System environment)

For more information about acquiring these components, please contact Intergraph Support.

Important

• The PDS Export Tools component is a separately licensed product. Before attempting to install the component, please contact Intergraph Support for licensing information.

1. Log on to the computer with a user account that has administrator privileges. 2. Insert the Intergraph SmartPlant 3D Product CD.

Tip

• If the CD does not start automatically, double-click Setup.exe in the root folder of the CD.

3. Select Prerequisite Software.

4. Select PDS Export Tools Installation. 5. Click Continue on the Welcome page.

Tip

• If the setup determines that PDS is not installed, an error message appears. Click OK. Install PD_Shell and then re-try this procedure.

Note

• For more information about exporting PDS model data into the software, see the Common User's Guide available with the Help > Printable

(28)

PDS Model Data Exporter

Generates a discipline-specific XML data file that can be read for import by the File

> Import command in SmartPlant 3D. You access this dialog by executing the PDSModelDataExporter.exe located in [Product Directory]\Translators\Util\bin.

You can use the PDS Model Data Exporter with PDS version 8.0. If the PDS

project is an earlier version, you need to upgrade the project before using the utility to export data.

The PDS Model Data Exporter requires the separate lease and installation of the

SmartPlant 3D PDS Project Translators (SEBY801AA).

The PDS Model Data Exporter is available for the following disciplines:

• Piping - In the Piping discipline, because you can have piping networks

connected across models, a single XML file is specified for a set of model files being exported.

• Equipment - For the Equipment discipline, the PDS Model Data Exporter

generates a single XML file per model. Therefore, you specify the folder where the XML files will be placed. The file names will be named with the model name.

• Electrical (Raceway) - When you import the data in SmartPlant 3D, you

use the Import Electrical command to import the route data and the

Import Equipment command to import the electrical equipment data. For

the Raceway (Electrical) discipline, the PDS Model Data Exporter behaves much the same as with Equipment. However, two XML files are created, one for the route and one for the equipment. When you import the data in SmartPlant 3D, you use the Import Electrical command to import the route data and the Import Equipment command to import the

electrical equipment data.

• HVAC - For the HVAC discipline, the PDS Model Data Exporter does

not have access to the HVAC_PROJ_NODE or HVAC_PROJ_PATH environment variables. Instead, the executable sets the

HVAC_PROJ_PATH to the path of the default HVAC model location as obtained from pdtable_115. The executable requires that a projlist.txt file reside in the parent directory. For example, an HVAC project named stdeng is integrated with a PDS project as follows:

PDS Project Location : PDSServer E:\stdeng\project.

HVAC Models location : PDSServer E:\stdeng\models\hvac\stdeng. This information is in pdtable_115.

In this configuration, the PDS Model Data Exporter sets the HVAC environment variables as follows:

HVAC_PROJ_NODE : PDSServer

(29)

The HVAC project list file named projlist.txt should be available in this directory for the export process to work.

Because you can have HVAC networks connected across models, you specify a single XML file for a set of model files to be exported.

Note

• The PDS Model Data Exporter is not used to export Structure data from FrameWorks Plus.

You can define export configuration files for each discipline. The configuration files include both user-configurable attributes and user attributes. Sample export

configuration files are delivered with the PDExportToSP3D utility to be customized as needed.

Project - Specifies the PDS project to export. The dropdown provides a list of

available PDS projects.

Discipline - Specifies the discipline to export. You can select: Pipeline, Raceway

(Electrical), Equipment, and HVAC.

Area list - Displays a checkbox list of all the design areas in the selected discipline.

You check the boxes within the list to select the models in those Areas that will be exported.

(30)

Model Name list - Shows a list of the models in the selected Areas.

New Session - Resets the dialog box to start fresh from Project selection.

Open Session - Displays the Select Export Set File dialog from which to select a

different PDS export set file (.exp).

Next - Displays the next dialog box for exporting. This dialog shows a summary of

the selected PDS project and models. You specify the output XML file/folder as applicable, the export configuration file, and the export set file entries.

Summary - Displays what you have selected to export.

Output XML file - Define the path and filename for the XML file to write. This is

the XML file that SmartPlant 3D will use to import the data.

Export configuration file - Specify the path and file name of the export

configuration file to use. There are configuration files delivered in the

\PDShell\PDExportToSP3D\config folder for the "out-of-the-box" PDS attributes. If you have added custom attributes to PDS, you will need to edit the configuration files before you can use them. For more information about the export configuration files, see PDS Exporter Configuration Files: An Overview, page 22.

(31)

Export set file - Specify the path and file name for the export set file. This file is a

settings file that you can use with the Open Session command in case you need to rerun the export process. The PDS Model Data Exporter also creates an export log file in the same folder as the Export Set file.

Finish - Exports the data to the specified XML file using the configuration file

specified.

Related Topics

• Export PDS Equipment Data to an XML File, page 31

• Export PDS HVAC Data to an XML File, page 32

• Export PDS Piping Data to an XML File, page 33

• Export PDS Raceway Data to an XML File, page 34

Export PDS Equipment Data to an XML File

1. Create the configuration file that you will use. There is configuration file delivered in the ..\PDShell\PDExportToSP3D\config folder called

EquipmentExportConfig.txt for the "out-of-the-box" PDS attributes. If you have added custom attributes to PDS, you will need to edit this configuration file before you can use it. For more information about the export configuration files, see PDS Exporter Configuration Files: An Overview, page 22.

2. Execute the PDSModelDataExporter.exe in [Product

Directory]\Translators\Util\bin. The PDS Model Data Exporter dialog box appears.

3. Select a PDS project.

4. Select the Equipment discipline.

5. Select the Area(s)/model(s) that you want to export.

6. Click Next to verify the model information and preview the format of the XML file being created.

7. Select the Output XML file/folder as applicable.

8. Select the Export configuration file to use from step 1 above. 9. Provide a name for the Export set file and specify the file location. 10. Click Finish.

Related Topics

(32)

Export PDS HVAC Data to an XML File

HVACExportConfig.txt for the "out-of-the-box" PDS attributes. If you have added custom attributes to PDS, you will need to edit this configuration file before you can use it. For more information about the export configuration files, see PDS Exporter Configuration Files: An Overview, page 22.

4. Select the HVAC discipline.

5. Select the Area(s)/model(s) that you want to export.

Related Topics

(33)

Export PDS Piping Data to an XML File

You can export different piping models to several different XML files. However, if you want the piping runs connected in the SmartPlant 3D model, you need to export all connected piping models to a single XML file.

PipingExportConfig.txt for the "out-of-the-box" PDS attributes. If you have added custom attributes to PDS, you will need to edit this configuration file before you can use it. For more information about the export configuration files, see PDS Exporter Configuration Files: An Overview, page 22.

3. Select a PDS project. 4. Select the Piping discipline.

5. Select the Area(s)/model(s) that you want to export. You should export everything that you want connected at the same time.

Related Topics

(34)

Export PDS Raceway Data to an XML File

ElectricalExportConfig.txt for the "out-of-the-box" PDS attributes. If you have added custom attributes to PDS, you will need to edit this configuration file before you can use it. For more information about the export configuration files, see PDS Exporter Configuration Files: An Overview, page 22.

4. Select the Raceway discipline.

5. Select the Area(s)/model(s) you want to export.

Related Topics

(35)

Exporting from FrameWorks Plus

The CIS/2 translator for FrameWorks Plus is part of a product called SmartPlant 3D

PDS Project Translators (SEBY801AA), which is leased separately from

FrameWorks Plus, PDS, and SmartPlant 3D. Contact Intergraph for software availability. To use this command, open the model that you want to export to

SmartPlant 3D. Be sure to attach all reference models that are needed. Then, type mdl

load SPExport in the MicroStation key-in field.

Note

• FrameWorks Plus does not write tapered member, arc members, or generic solid members to the CIS/2 file.

Criteria - Activate a dialog box used to select what members to write to the CIS/2

file. For more information, see Member Criteria, page 37.

Description - Enter a description for the CIS/2 file.

Author - Enter your name.

Organization - Enter your organization name.

(36)

Log file - Enter a name and location for the log file.

Units - Specify the units for the CIS/2 file.

OK - Writes the CIS/2 file and closes the dialog box. You cannot review the log file

using the View Log command if you click OK. Use Apply if you want to review the log file at the end of the process.

Cancel - Exits the dialog box without writing the CIS/2 file.

Apply - Writes the CIS/2 file without closing the dialog box. Use this command if

you want to review the log file at the end of the process.

View Log - Opens the log file for review.

Status - Displays the CIS/2 writing progress.

Based-on CIS/2 Statement for Export

Application Name: SmartPlant 3D PDS Project Translators

Application Version: 2007 SP2 Date: June 2007 Translator Version: 2007 SP2 Date: June 2007

Software Vendor: Intergraph Process, Power & Marine 300 Intergraph Way

Madison, Alabama 35758 U.S.A.

The translators for this application have been implemented in accordance with the second release of the CIMsteel Integration Standards (CIS/2.0) for the following (combination of) Conformance Classes:

• CC312, CC110, CC118, CC255, CC331, CC100, CC308

Type of CIS Translator: Basic | DMC | IDI | PMR-enabled

Unit Systems supported: SI | US Imperial

The vendor places the following riders on the operation of the translators:

• managed_data_deleted, managed_data_creation, and managed_data_transaction are not exported.

Date of Statement: June 2007

(37)

If you have any questions about using this translator, please contact Intergraph support. You can find support information on our web site

http://support.intergraph.com.

Related Topics

• Exporting Models from FrameWorks Plus, page 38

• Member Criteria, page 37

Member Criteria

The Criteria > Member Criteria command is used to define which members you want to write to the CIS/2 file. Because you define the criteria for what members to write to the file here, the settings in the Select Filter Settings command are ignored.

Type - Toggle on the member design types you want to write to the file.

Class - Toggle on the member classes you want to write to the file.

Include Reference Model - Defines whether to write members from attached models

to the file in addition to the members in the active model. You can attach models using the File > Attach Models command. You can detach models using the File >

Detach Models command.

Criteria - Defines whether to write members from a selection set or to write all the

(38)

All On - Toggles on all Design Type and Member Class settings. The default is that

all settings are selected.

All Off - Toggles off all Design Type and Member Class settings.

OK - Saves any changes you have made and exits the dialog box.

Cancel - Ignores any changes you have made and exits the dialog box.

Related Topics

• Exporting from FrameWorks Plus, page 35

Exporting Models from FrameWorks Plus

1. Start FrameWorks Plus.

2. Open the model that you want to export to SmartPlant 3D. 3. Attach all reference models that are needed.

4. Type mdl load SPExport in the MicroStation key-in field. 5. Define the Criteria for member selection.

6. Type a description for the file.

7. Type your name and your organization's name.

8. In the File box, enter a name and location for the CIS/2 step file. 9. In the Log file box, enter a log file name.

10. Select whether to write the SI units or Imperial Units to the file. 11. Click Apply.

12. Click View Log.

13. Carefully review the log file for errors.

Related Topics

(39)

Importing Data from PDS: An Overview

You import the XML file data using the appropriate File > Import command in SmartPlant 3D.

Import log files are generated in the same directory as the source XML file. The To

Do List also includes any objects that require attention after importing. For more

information on importing PDS data into SmartPlant 3D, see:

• Import Electrical Command, page 39

• Import Equipment Command, page 42

• Import HVAC Command, page 44

• Import Piping Command, page 46

• Import Structure Command, page 49

Related Topics

• Exporting Data from PDS: An Overview, page 21

Import Electrical Command

Imports Electrical data from an XML file, using mapping defined in an XLS

(Microsoft Excel workbook) file. The input XML file is validated against the defined electrical import schema to make sure the file is valid for import.

The Import Electrical command uses a mapping configuration workbook to specify mapping of Electrical specifications. An example mapping configuration file is delivered in [Product Directory]\Translators\ConfigurationFiles. In the delivered sample mapping workbook, ElectricalTranslationMap.xls, several sheets describe the mapping used for raceway. For example, the CabletraySpec sheet specifies the mapping of all the XML cableway specifications. While the ConduitSpec sheet maps the XML conduit run specifications. For more information about this workbook, see Electrical Translation Map, page 98.

When you import electrical data, the command does the following:

• Creates cableways and conduit runs

• Imports the route network

• Imports branching configurations

• Imports components

(40)

If there is an item in the XML file that has the model system set to blank or

Undefined, the Import Electrical command creates a generic system under the root with the naming convention xxxxxxImport-Date-Time. For example, the name might be ElectricalImport-6-27-2005 09:09:57AM. All objects with the blank or Undefined parent system import to this new system. After import, you can move the objects to your own System hierarchies.

Notes

• You should import Electrical Equipment using File > Import >

Equipment.

• You can use the PDS Model Data Exporter to create the input XML file for importing. For more information, see PDS Model Data Exporter, page 28.

Import Electrical Data Dialog Box

Sets options for importing Electrical data.

XML file - Specifies the XML file to use for import. Click the button next to the box

to browse for the XML file.

Map file - Specifies the XLS map workbook to use for import. Click the button next

to the field to browse for the map workbook. For more information about this workbook, see Electrical Translation Map, page 98.

Related Topics

• Import Electrical Command, page 39

(41)

Import Electrical Data

1. Use the PDS Model Data Exporter to create an import XML file. For more information, see PDS Model Data Exporter, page 28.

2. Select File > Import > Electrical. The Import Electrical Data dialog box appears.

3. Click the button next to the XML file box to select the XML file to use for import.

4. Click the button next to the Map file box to select the XLS map workbook to use for import. For more information about this workbook, see Electrical Translation Map, page 98.

5. Click OK to import the electrical data as specified. If problems occur, check the import log file created in the same location as the input XML file.

6. Check the To Do List for items that require attention after importing. If there is an item in the XML file that has the model system set to blank or Undefined, the Import Electrical command creates a generic system under the root with the naming convention xxxxxxImport-Date-Time. For example, the name might be ElectricalImport-6-27-2005 09:09:57AM. All objects with the blank or Undefined parent system import to this new system. After import, you can move the objects to your own System hierarchies.

Note

• The input XML file is validated against the defined electrical import schema to make sure the file is valid for import.

Related Topics

(42)

Import Equipment Command

Imports Equipment data from an XML file, using a mapping defined in an Microsoft Excel workbook file. The input XML file is validated against the defined equipment import schema to make sure the file is valid for import.

The Import Equipment command uses a mapping configuration workbook to specify part class, part number, and attribute mapping. An example mapping

configuration file is delivered in [Product Directory]\Translators\ConfigurationFiles called EQPTranslationMap.xls. For more information about this workbook, see Equipment Translation Map, page 101.

When you import equipment data, the command does the following:

• Creates the design equipment

• Adds shapes, nozzles, and parametrics to the design equipment

• Imports equipment attributes, nozzles, shapes, parametric dimensional attribute, and orientation

• Imports user attributes for equipment and nozzles

Note

Undefined, the Import Equipment command creates a generic system under the root with the naming convention xxxxxxImport-Date-Time. For example, the name might be EquipmentImport-6-27-2005 09:09:57AM. All objects with the blank or Undefined parent system import to this new system. After import, you can move the objects to your own System hierarchies.

Import Equipment Data Dialog Box

Sets options for importing Equipment data.

XML file - Specifies the XML file to use for import. Click the button next to the box

to the box to browse for the map workbook. For more information about this workbook, see Equipment Translation Map, page 101.

Related Topics

• Import Equipment Command, page 42

(43)

Import Equipment Data

2. Select File >Import > Equipment. The Import Equipment Data dialog box appears.

3. Click the button next to the XML file box to select the XML file to use for import.

4. Click the button next to the Map file box to select the XLS map workbook to use for import. For more information about this workbook, see Equipment Translation Map, page 101.

5. Click OK to import the equipment data as specified. If problems occur, check the import log file created in the same location as the input XML file.

6. Check the To Do List for items that require attention after importing. If there is an item in the XML file that has the model system set to blank or Undefined, the Import Equipment command creates a generic system under the root with the naming convention xxxxxxImport-Date-Time. For example, the name might be EquipmentImport-6-27-2005 09:09:57AM. All objects with the blank or Undefined parent system import to this new system. After import, you can move the objects to your own System hierarchies.

Note

• The input XML file is validated against the defined equipment import schema to make sure the file is valid for import.

Related Topics

(44)

Import HVAC Command

Imports HVAC data from an XML file, using a mapping defined in an Microsoft Excel workbook file. The input XML file is validated against the defined HVAC import schema to make sure the file is valid for import.

The Import HVAC command uses a mapping configuration file to specify configuration and attribute mapping. An example mapping configuration files is delivered in [Product Directory]\Translators\ConfigurationFiles called

HVACTranslationMap.xls. For more information about this workbook, see HVAC

Translation Map, page 112.

When you import HVAC data, the command does the following:

• Creates DuctRuns

• Imports the route network

• Imports branching configurations

• Imports components

• Imports attributes and user attributes

Undefined, the Import HVAC command creates a generic system under the root with the naming convention xxxxxxImport-Date-Time. For example, the name might be HVACImport-6-27-2005 09:09:57AM. All objects with the blank or Undefined parent system import to this new system. After import, you can move the objects to your own System hierarchies.

Note

Import HVAC Data Dialog Box

Sets options for importing HVAC data.

XML file - Specifies the XML file to use for import. Click the button next to the field

to the field to browse for the map workbook. For more information about this workbook, see HVAC Translation Map, page 112.

Related Topics

(45)

Import HVAC Data

2. Select File > Import > HVAC. The Import HVAC Data dialog box appears. 3. Click the button next to the XML file box to select the XML file to use for

import.

4. Click the button next to the Map file box to select the XLS map workbook to use for import. For more information about this workbook, see HVAC Translation Map, page 112.

5. Click OK to import the HVAC data as specified. If you checked any of the logging options, you can review the log file for extra information.

6. Check the To Do List for items that require attention after importing. If there is an item in the XML file that has the model system set to blank or Undefined, the Import HVAC command creates a generic system under the root with the naming convention xxxxxxImport-Date-Time. For example, the name might be HVACImport-6-27-2005 09:09:57AM. All objects with the blank or Undefined parent system import to this new system. After import, you can move the objects to your own System hierarchies.

Note

• The input XML file is validated against the defined HVAC import schema to make sure the file is valid for import.

Related Topics

(46)

Import Piping Command

Imports piping data from an XML file, using a mapping defined in an XLS

(Microsoft Excel workbook) file. The input XML file is validated against the existing piping schema file to make sure the file is valid for import.

The Import Piping command uses a mapping configuration to specify configuration and attribute mapping. An example mapping configuration file is delivered in

[Product Directory]\Translators\ConfigurationFiles. In the delivered sample mapping file, PipingTranslationMap.xls, several sheets describe the mapping used for piping. For example, the Generic-ItemCode-Map sheet specifies a map between the piping item's ItemCode and the SmartPlant 3D ShortCode/Tag. For more information about this workbook, see Piping Translation Map, page 115.

Another example is the PMC-Specific-ItemCode-Map sheet, which specifies the overriding map per specification (over the Generic mapping) between the ItemCode and the SmartPlant 3D ShortCode/Tag. You should only use this mapping if some specifications have a different ShortCode on the SmartPlant 3D side, which is different from the mapping in the Generic-ItemCode-Map sheet.

Other mapping sheets defined are for specialties, instruments, and supports.

User Attribute mapping is provided on sheets identified with the naming convention xxxxUA, where UA means user attribute. For each user-defined attribute in the

XML, a mapping entry indicates the SmartPlant 3D Interface.Attribute to which it maps.

When you import piping data, the command:

• Creates pipeline systems if they do not already exist. If the parent Piping system is identified in the input XML file, the pipelines are created under the Piping system(s). Otherwise, the pipelines are created under the plant root.

• Creates piperuns, route network, branching.

• Imports piping components along the network. However, items not listed in the mapping XLS are not imported. Some PDS instruments and specialties may not have equivalents in SmartPlant 3D. Also, some SmartPlant 3D implied parts are handled differently than in PDS.

Therefore, some mapping entries may be hard-coded to take care of them. Examples include branching components like flanges around valves.

• Creates SmartPlant 3D supports using G-Type graphics for PDS Physical Pipe Supports. In order to import G-Type graphics using Pipe Import, load the HS_System.xls file located in the product installation

directory\Translators\ConfigurationFiles\ to the existing catalog database.

• Imports tap information, specified as GenericNotes added on associated piperun ends indicating tap details.

Pds Guide

SmartPlant 3D

Plant Design System (PDS) Guide

Table of Contents

Preface

SmartPlant 3D Documentation Set

Administrative Guides

User's Guides

Reference Data Guides

ISOGEN Guides

What's New with Plant Design System (PDS)

Integration

PDS Plant Design System: An Overview

Referencing a PDS Model: An Overview

Install PDS Data Access

New PDS Model Reference Command

PDS Model Reference Dialog Box

Reference a PDS Project

Un-reference a PDS Project

Exporting Data from PDS: An Overview

PDS Exporter Configuration Files: An Overview

Install PDS Export Tools

PDS Model Data Exporter

Export PDS Equipment Data to an XML File

Export PDS HVAC Data to an XML File

Export PDS Piping Data to an XML File

Export PDS Raceway Data to an XML File

Exporting from FrameWorks Plus

Member Criteria

Exporting Models from FrameWorks Plus

Importing Data from PDS: An Overview

Import Electrical Command

Import Electrical Data Dialog Box

Import Electrical Data

Import Equipment Command

Import Equipment Data Dialog Box

Import Equipment Data

Import HVAC Command

Import HVAC Data Dialog Box

Import HVAC Data

Import Piping Command