PDS 3D Theory Guide

Plant Design System
3D Theory
Version 2011 R1 (12.1)
June 2016
Copyright
Copyright © 1984-2016 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.
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
305 Intergraph Way
Madison, AL 35758
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 Intergraph Smart Support,
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 use. 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.
Plant Design System 3D Theory 2

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
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, http://www.treas.gov/offices/enforcement/ofac/, and the U.S.
Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.
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, and SupportModeler 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. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its
affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product names are
trademarks of their respective owners.

Contents
Preface PDS ........................................................................................................................................... 9
What is the Plant Design System? ...................................................................................................... 10

What are the 2D modules? .............................................................................................................. 11
Process Flow Diagram (PFD) .................................................................................................... 11
Process & Instrumentation Diagram (P&ID) ............................................................................... 11
Instruments and Instrument Loops ............................................................................................. 12
What are the 3D modules? .............................................................................................................. 12
Equipment Modeling (PD_EQP) ................................................................................................ 12
FrameWorks Plus (FWP) ........................................................................................................... 13
Piping Design Graphics (PD_Design) ........................................................................................ 14
Reference Data Manager (PD_Data) ......................................................................................... 15
Drawing Manager (PD_Draw) .................................................................................................... 15
PDS Stress Analysis Interface (PD_Stress) ............................................................................... 16
Interference Checker/Manager (PD_Clash) ............................................................................... 16
PDS Isometric Interface (PD_ISO, PD_ISOGEN)....................................................................... 17
Report Manager (PD_Report) .................................................................................................... 18
Project Engineer HVAC (PE-HVAC) .......................................................................................... 18
EE Raceway Modeling............................................................................................................... 19
Design Review Integrator (PD_Review) ..................................................................................... 19
Project Setup ................................................................................................................................... 20
System Setup ............................................................................................................................ 20
2DSetup .................................................................................................................................... 21
3D Setup ................................................................................................................................... 22
About Licensing......................................................................................................................... 22
Project Organization ........................................................................................................................ 23
Working in Three Dimensions .......................................................................................................... 24
Working Units ............................................................................................................................ 27
Recommended Working Units - English ..................................................................................... 28
Recommended Working Units - Metric ....................................................................................... 29
Reasoning ................................................................................................................................. 30
3D Coordinate Systems ............................................................................................................. 30
Plant Coordinate System ........................................................................................................... 31
Design Volume Coordinate System ........................................................................................... 36
Examples .................................................................................................................................. 38
Database Overview .............................................................................................................................. 43

PDS and the Relational Interface System (RIS)................................................................................ 43
PDS System Configurations............................................................................................................. 45
Client/Server Relationship ......................................................................................................... 45
PDS 3D Databases.......................................................................................................................... 47
Database Information ................................................................................................................ 48
Database Definition Files ................................................................................................................. 50
Project Control Database ........................................................................................................... 50
Design Database ....................................................................................................................... 67

Contents
Reference Database.................................................................................................................. 84
Reference Data..................................................................................................................................... 89
Delivered Reference Data ................................................................................................................ 90
Piping Job Specification ................................................................................................................... 91
Piping Materials Class Data ....................................................................................................... 91
Piping Commodity Specification Data ........................................................................................ 92
Piping Specialty Specification Data ............................................................................................ 94
Instrument Component Specification Data ................................................................................. 95
Tap Properties Data .................................................................................................................. 96
Piping Commodity Size-Dependent Material Data ...................................................................... 97
Piping Commodity Implied Material Data.................................................................................... 98
PJS Tables and Functions ....................................................................................................... 100
Graphic Commodity Data and Physical Dimension Data ................................................................ 101
Material Description Data ............................................................................................................... 101
Standard Note Library .................................................................................................................... 103
Label Description Library ............................................................................................................... 103
Piping Assembly Library ................................................................................................................ 104
How PDS Works ................................................................................................................................. 105

What Happens When I Place a Component? ................................................................................. 105
Example of Piping Software ........................................................................................................... 106
Place Component Command ......................................................................................................... 107
Spec Access ........................................................................................................................... 107
Piping Materials Class Data ..................................................................................................... 107
Piping Commodity Data ........................................................................................................... 113
Table Access........................................................................................................................... 117
Symbol Processors.................................................................................................................. 119
Sub-Symbol Processor ............................................................................................................ 120
Physical Data Definitions ......................................................................................................... 120
Specific Physical Data Modules ............................................................................................... 121
Parametric Shape Definitions .................................................................................................. 124
Physical Data .......................................................................................................................... 126
Placing Components On Existing Segments .................................................................................. 128
Commodity Item Name Table .................................................................................................. 129
Bend Deflection Table ............................................................................................................. 130
Branch Insertion Tables ........................................................................................................... 130
Placement Examples ............................................................................................................... 131
Creating 3D Models............................................................................................................................ 134

Modeling Setup Requirements ....................................................................................................... 135
Project Setup........................................................................................................................... 135
Reference Data Setup ............................................................................................................. 135
Seed Files ............................................................................................................................... 135
Model Files .............................................................................................................................. 136
Level Control and Graphical Symbology .................................................................................. 137
Level and Symbology Defaults................................................................................................. 138
Graphics Environment for PDS 3D................................................................................................. 139
Working with the Graphical User Interface ............................................................................... 139

Contents
Common Tools on Forms ........................................................................................................ 144

3D Seed Data.......................................................................................................................... 147
Creating Equipment Models ........................................................................................................... 151
Functions of PDS Equipment Modeling (PD_EQP) .................................................................. 152
About the Reference Database (RDB) ..................................................................................... 152
Equipment Model Seed Data ................................................................................................... 153
Equipment Modeling Environment ........................................................................................... 156
Equipment Modeling Concepts ................................................................................................ 158
Activating the Orientation Tee .................................................................................................. 160
Equipment Modeling Commands ................................................................................................... 161
Equipment Manipulation Commands ....................................................................................... 161
Component Manipulation Commands ...................................................................................... 161
Nozzle Manipulation ................................................................................................................ 161
Review/Revise Commands ...................................................................................................... 161
Define Commands................................................................................................................... 161
Miscellaneous Commands....................................................................................................... 161
Secondary Commands ............................................................................................................ 162
Creating Piping Models .................................................................................................................. 162
Piping Model Seed Data .......................................................................................................... 164
Graphic Concepts for Piping Design ........................................................................................ 169
Orientation Tee........................................................................................................................ 171
Piping Design Commands.............................................................................................................. 172
Placement Commands ............................................................................................................ 172
Revision Commands ............................................................................................................... 173
Component Revision ............................................................................................................... 173
Segment Vertex Commands .................................................................................................... 173
Piping Revision........................................................................................................................ 173
Model Data .............................................................................................................................. 174
Review Data ............................................................................................................................ 174
Revise Data............................................................................................................................. 174
Analyze Data ........................................................................................................................... 174
PDS P&ID to Piping Data Transfer .................................................................................................... 175

Database Requirements ................................................................................................................ 175
P&ID Correlation Table .................................................................................................................. 176
P&ID Graphical Data Transfer Setup.............................................................................................. 180
P&ID Node Numbers ..................................................................................................................... 182
Update Segment Data from P&ID .................................................................................................. 183
Update by Node Number ......................................................................................................... 184
Transfer by Equipment Number and Nozzle Number ............................................................... 184
Update From Active P&I Drawing............................................................................................. 185
P&ID Data ..................................................................................................................................... 186
Name From P&ID .......................................................................................................................... 186
P&ID Data Comparison Options..................................................................................................... 187
SmartPlant P&ID to PDS Piping Data Transfer ................................................................................. 188

Transferring Piping Data ................................................................................................................ 188
Installation ............................................................................................................................... 189
Creating and Maintaining Links ................................................................................................ 191

Contents
Mapping Attributes_WRAPPER ............................................................................................... 196

Segment Data Comparison Report .......................................................................................... 198
Choosing Data Transfer Options.............................................................................................. 199
Load from P&ID Options .......................................................................................................... 201
Graphical P&ID Setup Command ............................................................................................ 201
Select P&ID by Line ID Command ........................................................................................... 202
Select P&ID Drawing by Nozzle Command .............................................................................. 202
Review P&ID Drawing Details Command................................................................................. 203
P&ID Drawing Display Categories Command........................................................................... 203
Restore View of Piping Model Command ................................................................................. 203
Disable Display of P&ID Drawing Command ............................................................................ 203
Name from P&ID Option .......................................................................................................... 203
Named Component Existence Report Command ..................................................................... 203
Troubleshooting....................................................................................................................... 205
Detecting and Managing Interferences ............................................................................................. 208

Interference Checking Process Overview ....................................................................................... 208
Project Organization ...................................................................................................................... 210
Understanding Design Areas and Volumes .............................................................................. 211
Setting Up a System to Support Interference Detection .................................................................. 215
Understanding Interference Envelopes .......................................................................................... 216
Understanding Interference Checking ...................................................................................... 217
Understanding Interference Plotting ......................................................................................... 223
Understanding Interference Reporting ..................................................................................... 223
Creating Material Takeoffs and Other Reports ................................................................................. 224

Reporting Process ......................................................................................................................... 224
Maintaining Report Definition Data ................................................................................................. 224
Understanding Report Files and Records................................................................................. 225
Processing Reports ....................................................................................................................... 227
Report Types ................................................................................................................................. 227
Report Format File ......................................................................................................................... 228
Format File Syntax .................................................................................................................. 228
Definitions ............................................................................................................................... 229
Output Fields ........................................................................................................................... 232
Sample Format Files ............................................................................................................... 232
What Happens When I Report On a Component? .......................................................................... 235
Material Descriptions ............................................................................................................... 236
Commodity Codes ................................................................................................................... 237
Examples ................................................................................................................................ 239
Implied Data ............................................................................................................................ 239
Report Output.......................................................................................................................... 240
Material Takeoff Reporting (Report Manager) ................................................................................ 241
Sample MTO Format (piping_g.fmt)......................................................................................... 241
Sample MTO Output................................................................................................................ 244
Understanding Implied Items ......................................................................................................... 246
Mating Implied Items ............................................................................................................... 246
'*' Spec Implied Items .............................................................................................................. 246
'+' Table Implied Items ............................................................................................................. 247

Contents
Material Takeoff Options ................................................................................................................ 249

Labels in Material Descriptions ...................................................................................................... 251
Create Label Attribute Data ..................................................................................................... 257
Material Data Publisher.................................................................................................................. 260
Extracting Isometric Drawings .......................................................................................................... 261

Overview of Isometric Extraction .................................................................................................... 263
The Intergraph Interface to ISOGEN........................................................................................ 264
ASCII to Binary Conversion ..................................................................................................... 264
ISOGEN .................................................................................................................................. 264
Batch Software Organization ......................................................................................................... 265
The Batch Job Input File .......................................................................................................... 265
Line Processing (pdsidf) .......................................................................................................... 266
The ISOGEN Interface............................................................................................................. 267
ISOGEN .................................................................................................................................. 267
Plotting .................................................................................................................................... 267
Creating Orthographic Drawings ...................................................................................................... 268

Drawing Manager Features............................................................................................................ 269
Drawing Manager Setup ................................................................................................................ 269
Project Setup........................................................................................................................... 269
Model Files .............................................................................................................................. 269
Drawing Manager Setup .......................................................................................................... 270
Drawing Categories ................................................................................................................. 270
Cells ........................................................................................................................................ 270
Drawing Borders...................................................................................................................... 270
Drawing Plot Size Table .......................................................................................................... 271
Drawing Manager Database Table Information ........................................................................ 271
Project Control Database ......................................................................................................... 272
Drawing Seed Data........................................................................................................................ 275
Using Labels in Drawing ................................................................................................................ 278
LabelTypes ............................................................................................................................. 278
Label Definition Data ............................................................................................................... 279
Drawing View Specific Labels .................................................................................................. 280
Displayable Attribute Label ...................................................................................................... 281
Index ................................................................................................................................................... 282

Preface PDS
This document provides command reference information and procedural instructions for the
Plant Design System 3D Theory Guide task.
List of PDS Documentation

 DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide
 DPDS3-PB-200004 - Drawing Manager (PD_Draw) User's Guide
 DPDS3-PB-200005 - EE Raceway Modeling Reference Guide
 DPDS3-PB-200006 - Interference Checker/Manager (PD_Clash) User's Guide
 DPDS3-PB-200010 - PDS 3D Theory User's Guide
 DPDS3-PB-200013 - PDS EDEN Interface Reference Guide Volume I : Piping
 DPDS3-PB-200015 - PDS Equipment Modeling (PD_EQP) User's Guide
 DPDS3-PB-200017 - PDS ISOGEN Reference Guide, Vol. 1
 DPDS3-PB-200022 - PDS Piping Component Data Reference Guide
 DPDS3-PB-200023 - PDS Project Setup Technical Reference
 DPDS3-PB-200025 - PDS Stress Analysis Interface (PD_Stress) User's Guide
 DPDS3-PB-200026 - Pipe Supports Modeler Reference Guide
 DPDS3-PB-200028 - Piping Design Graphics (PD_Design) Reference Guide
 DPDS3-PB-200030 - Project Administrator (PD_Project) Reference Guide
 DPDS3-PB-200033 - Project Engineer HVAC (PE-HVAC) Reference Guide
 DPDS3-PB-200034 - Reference Data Manager (PD_Data) Reference Guide
 DPDS3-PB-200035 - Report Manager (PD_Report) User's Guide
 DPDS3-PB-200041 - PDS EDEN Interface Reference Guide Volume 2 : Equipment
 DPDS3-PB-200042 - PDS EDEN Interface Reference Guide Volume 3 : Pipe Supports
 DPDS3-PE-200016 - PDS Express Project Creation Quick Start Guide
 DPDS3-PE-200052 - PDS Ortho Draw User's Guide
 DPDS3-PE-200029 - Piping Model Builder (PD_Model) Reference Guide
 DPDS3-PE-200031 - Project Engineer HVAC Getting Started Guide
 DPDS3-PE-200032 - Project Engineer HVAC Overview
 DPDS3-PE-200045 - PDS Label Library Merger Utility
 DPDS3-PE-200047 - PDS Reference Data Auditing Tool
 DPDS3-PE-200048 - Pipe Supports Explorer Utility
 DPDS3-PE-200050 - Batch Services Quick Start Guide
 DPDS3-PE-200051 - Batch Services User's Guide

What is the Plant Design System?
SECTION 1
Intergraph’s plant design software can be used to design any type of plant—from petrochemical
plants, offshore platforms, chemical and pharmaceutical plants, consumer products (food,
beverages, cosmetics, soap, paper, and so forth), to power plants, waste water treatment plants,
and cogeneration facilities.
Specifically, the Plant Design System (PDS) integrates many discipline-specific software
modules; these modules automate the many phases of a plant design project. Instrument Data
Manager is one of these modules. Designing a plant with the modular Intergraph plant design
software system comprises four phases:
1. Project Setup—2D and 3D design files, project files, databases.
2. Preliminary Design —feasibility studies, cost estimates, general layouts and process flow
diagrams.
3. Detailed Design —process, instrumentation, piping layouts, material control.
4. Design Review—3D model walk-through.

What are the 2D modules?

PDS 2D is used to create schematic diagrams and to provide the associated reports and MTOs,
and to define and purchase all equipment, instruments, pipe, and so forth, necessary to build the
plant. All of the needed data is stored in databases. These are relational databases which you
can query, add, delete, or edit information to suit your own or your client's needs.
The PDS 2D modules are briefly discussed in the following sections.
Process Flow Diagram (PFD)
Conceptual design of a plant includes feasibility studies, cost estimates, and process
simulations. Third-party process simulation packages such as ASPEN or SimSci allow
engineers to perform preliminary calculations such as chemical equilibriums, reactions, heat and
material balances and/or design pressures and temperatures. The data produced from these
calculations are transferred to PDS where a process flow diagram (PFD) is developed.
Process & Instrumentation Diagram (P&ID)
Equipment, instrumentation, and piping schematics are drawn from process flow data using the
Process & Instrumentation Diagrams (P&ID) product.
The P&IDs display the overall process in much greater detail than the PFD. The P&ID shows all
piping, instrumentation, and controls associated with a particular process area, as well as all
process vessels, pumps, motors, and so forth.

The P&ID identifies the types of instrumentation and controls required by the process and
assigns tag numbers to each instrument item. The P&ID reflects the overall process control
through either distributive control systems (DCS), programmable logic controllers (PLC), or
stand-alone controller philosophy.
When doing propagation (taking graphic information from the drawing and writing it to the
database), the drawing is checked for conformance to design rules and the drawing information
is loaded into a relational database.
Instruments and Instrument Loops
After the P&ID defines the process controls, the instruments must be defined with all of the
individual data values. The Instrument Data Manager (IDM) is the database that maintains an
entry for each instrument in a project.
What are the 3D modules?

PDS 3D is used to create three-dimensional plant models, create equipment models, extract
isometric drawings, and perform design interference checks and equipment clashes. As with the
2D modules, all of the needed data is stored in relational databases which can be queried or
edited. The PDS 3D modules are briefly discussed in the following sections.
Equipment Modeling (PD_EQP)
Equipment Modeling (PD_EQP) allows designers to model the equipment defined in the P&ID.

Stylistic representations of equipment items are produced, with or without nozzles, by entering
data from equipment data sheets noting dimensions and weights. Upon completion, the
equipment item is placed in the 3D model.
Within PD_EQP, designers can create a physical envelope defining the space occupied by an
equipment item along with space envelopes defining maintenance and access areas. This
process is instrumental for interference checking later in the modeling process.
FrameWorks Plus (FWP)

Structures must be designed to carry the loads from piping, equipment, personnel and other
factors to the ground. FrameWorks Plus is used to layout structural frames, foundations, slabs
and walls. Piping designers, equipment modelers and structural designers, by sharing reference
files, can see the location of each other's objects. The structural engineer referencing other
models can place loads in the 3D model, and apply other analytical characteristics to use with a
third-party analysis solver. After a design run, the new cross section properties can be read back
into the model to automatically update all the associated symbolized 2D drawings.
Other outputs can be obtained from the data model such as material lists, output to third-party
steel detailing programs, interference envelopes, and graphic and nongraphic data made
available to the rendering and walk- through products such as SmartPlant Review.

Piping Design Graphics (PD_Design)
PD_Design allows designers to create a 3D model of the piping and in-line instruments defined
in the P&ID by routing the pipelines through space.
When placing the instruments and valves, designers take into account pipeline flexibility, method
of construction, and ease of access for maintenance and operations. Designers can route pipe
in the 3D model as a centerline representation; moreover, a 3D shaded model can be displayed
when necessary. The centerline is intelligent and contains all the information relating to a
pipeline, such as the piping material class, nominal diameter, fluid code, insulation parameters,
temperatures and pressures, and so forth.
The alphanumeric data required for each pipeline can be entered interactively or transferred
from the P&ID. This can be done during centerline routing, or it can be added/revised later.
A pipeline can be connected to a specific nozzle or routed from a point in space. Components
such as valves, instruments and branches can be placed on the pipeline as it is routed. Values
for the alphanumeric data—such as line sequence number, nominal diameter, material class,
temperatures and pressures—can be set during routing.
Interactive design checks are performed for each component placement. These checks ensure
matching or compatible diameters, pressure ratings, end preparations, and other consistency
criteria. Pipe supports can be modeled giving either a detailed space envelope or a logical
representation of the function of the support, such as an anchor, spring, or guide.

Reference Data Manager (PD_Data)

Placement of the piping components is specification-driven. The reference data provides the
selection criteria for the piping commodity items found in the piping job specification and piping
commodity libraries delivered with the product. This data is contained in the RDB and can be
used by other projects.
The delivered reference data contains 140 piping materials classes, defining over 100,000
different components for pressure ratings from 125-1500 pounds. It also contains an extensive
set of catalog data including 2200 engineering tables.
Reference Data Manager (PD_Data) is specifically designed to define and modify the reference
data for the PDS 3D modules. This reference data ensures consistency in the definition of piping
specifications and commodity libraries. It is used to control and standardize the PDS 3D
modules to reflect company practices and standards.
Drawing Manager (PD_Draw)
Designers use the Drawing Manager (PD_Draw) product to create and/or revise orthographic
production drawings. PD_Draw can be used with other PDS 3D products to place annotation
labels identifying intelligent items and model coordinates, to plot the drawings, and to produce
reports for drawings and model data.

PDS Stress Analysis Interface (PD_Stress)
The stress analyst uses the PDS Stress Analysis Interface (PD_Stress) module to generate a
neutral file from the 3D piping and equipment models for stress analysis. PD_Stress interfaces
to a number of commercial packages which accept ASCII format.
Interference Checker/Manager (PD_Clash)
Interference Checker/Manager (PD_Clash) creates envelope files for all models in the specified
project, design area, or for individual models which have an envelope builder specific to each
discipline in the Interference Checker/Manager. It also collects envelope data for the models that
have envelope files which were previously created by one of the other PDS modules. The
checker/manager processes the specified design volume and identifies all of the interference
clashes.
It then produces reports which allow the designer to review interferences and review and/or
revise the approval status of the interferences. The software places graphical markers for the
project, produces plots of clashes, and produces an interference report file.

PDS Isometric Interface (PD_ISO, PD_ISOGEN)

PDS Isometric Interface (PD_ISO,PD_ISOGEN) allows designers to extract isometric drawings
from the plant model, either interactively or through a batch process. The interactive extraction
can be used for testing the interface and verifying a specific pipeline. Batch generation of
isometrics is used for generating production drawings on a project. With either function, a bill of
materials is automatically generated and attached to the isometric drawing. An optional MTO file
can be generated which can be printed or used as input to a material control system.

Report Manager (PD_Report)
Material take-off reports (MTOs) can be generated on piping and equipment models through
PD_Report. The MTO process generates reports by using the graphical data in the specified
models to refer to the Design Database, Reference Database, Project Database, and Material
Description Libraries for the data on which to report. This data includes implied materials, such
as bolts, gaskets, and welds, that are not represented in the model but are necessary for the
specified connectivity.
The Report Manager also maintains the data that defines the format, content, and approval
status of the reports.
Project Engineer HVAC (PE-HVAC)

PE-HVAC allows designers to place fittings and devices while laying out duct routes. You can
define the active parameters for duct characteristics such as width, depth, shape, material,
construction status, and service.

EE Raceway Modeling
Electrical Engineer Raceway Modeling (EERWAY) is specification-driven software which allows

designers to extract data from the RDB and create 3D models of cable trays, conduits, wire
ways, underground duct banks, and cable trenches. These models can be created using the
centerline and/or 3-line component graphics. With these 3D models, you can create interference
envelopes and run interference detection, produce MTOs, and extract raceway drawings.
Design Review Integrator (PD_Review)

The PD_Review interface provides an intelligent link to Intergraph's SmartPlant Review. You
can use SmartPlant Review to walk through a PDS model—in full shaded mode—and review
the design and alphanumeric data.

Engineering data such as instrument numbers, equipment numbers, line numbers, and line
sizes are available when walking through the model.
Comments are stored in a separate tag file and can be accessed later during the review
session. On subsequent walk-throughs, the original comment can be reviewed along with the
responsible designer's actions.
Also with SmartPlant Review, the model can be used to train operations and maintenance
personnel before or after the plant is constructed. SmartPlant Review is not included in the PDS
package and must be purchased separately.
Project Setup
Before work can begin on a project, extensive system setup needs to be completed. The
following outlines the basic flow for initial system setup and project creation. This system and
project setup is usually done by the system manager. Once the project has been set up, other
tasks are done by the designer.
System Setup
PDS can run either stand-alone on a workstation or configured in a server/client relationship.
Due to the size and scope of PDS projects, most companies use a server/client relationship. A
PDS server can act as a database server, a file server, and/or a product server.
PDS uses relational databases to store informational about virtually all aspects of the project
including:
 Project data, such as file names and locations.
 Reference data, such as piping commodity descriptions.
 Design data, such as temperature and pressure values associated with graphic elements.

The PDS products attach to the relational databases through RIS. RIS supports popular
Relational Database Management Systems, such as Oracle and MS SQL.
2DSetup
The PDS2D product is the base platform loaded on each workstation that will be using PDS 2D
application software, such as PFD, P&ID, and IDM.
PDS2D is the interface to the PDS 2D application product line. It can be either loaded with the
client option to access software on a product server or installed locally. PDS2D allows you to
perform project administrative functions such as establish and modify reference data files,
projects, units and drawings.
 A 2D project uses a minimum of two database schemas: A project control database
 A "task" (or design) database
The projcreate utility creates the schema information for the installed database. Once the
database files have been created, you can access the 2D environment to create units and
drawings for the project. Units are logical divisions of the schematic world of a plant.

3D Setup
The PD Shell product is loaded on each workstation that will be using the PDS 3D products.
Other PDS 3D products can be loaded on the workstation.
A 3D project uses a minimum of three database schemas:
 A project control database,
 A material/reference database,
 A design database.
The 2D and 3D project share a common project control database. The Express Project
Creation and Project Administrator commands are used to create the database files, seed
files, and project environment files.
A 3D project is divided into design areas by disciplines. Disciplines represent the various 3D
modeling applications (such as Piping, Equipment, and HVAC). A design area represents a
specific portion of the project for a given discipline. Each design area comprises a set of models
that contains the actual design data.
About Licensing
SmartPlant License Manager is client/server based; one or more central servers can be used to
maintain licensing information for all PDS products in a network. Though the licensing
information can be on a single server, the licenses themselves float, that is, they can be used by
any workstation in the network. Both the client machine and license server must have
SmartPlant License Manager installed. Any machine can be a license server; the licensing has
little impact on workstation/server performance.
PDS software is purchased or leased by the license. For example, if you purchased 30 licenses,
you are licensed for 30 processes to concurrently access the various PDS software applications.
SmartPlant License Manager keeps a running inventory of how many licenses are in use and
how many are available for use. When a PDS application module is started, the application
sends a request to run the software; this request is sent to one or more PDS license servers to
obtain a license to run. If not all licenses are in use, the server grants the license and the
application starts. If all licenses are in use when a batch job requests a license, SmartPlant
License Manager waits until a license is released (in other words, a user logs out), and
processes the request to run. If all licenses are in use when an interactive user requests a
license, an error message displays indicating that all PDS licenses are currently in use. You
must wait until a license becomes available.
For more information on this topic, consult the SmartPlant License Manager User's Guide.

Project Organization
Since a process plant such as a refinery can be extremely large, PDS uses the following
organization to break the plant into smaller pieces that can be handled more easily.
A PDS project is comprised of the items that constitute a plant, or the portion of the plant being
modified. The project is the fundamental structure for working in PDS. Each project contains all
the information required to work in a PDS task.
A 3D project is divided into design areas by discipline. Disciplines represent the various
categories of 3D modeling data such as Piping, Equipment, and Structural. A design area
represents a specific volume or logical area of the project for a given discipline. Design areas
are used to break up the project into smaller areas for interference checking and reporting. This
speeds up processing when only a portion of the project has changed.
Each design area contains a set of models that correspond to a 3D design volume. Although the
illustration above shows only piping areas, each discipline is free to define its areas
independently of all other disciplines. The location of a model and the details of the Design
Volume Coordinate System are specified as seed data in the model definition. The model is
created at full scale.
A model is a MicroStation design file that contains pipelines, equipment items, cable trays,
conduit, structural steel and other items placed by the individual PDS applications such as
Piping Design, Equipment Modeling, Raceway, FrameWorks Plus, respectively. For example, a
piping model may contain only one pipeline or it may contain several pipelines. This is up to the
discretion of the project team to satisfy the needs of a specific project.
Each model may be constructed with respect to a master point of reference, known as the Plant
Monument (PM) or it may be constructed with respect to a local or auxiliary point of reference,
known as the Design Volume Monument (DVM). The use of the DVM in PDS is analogous to the
use of an Auxiliary Coordinate System (ACS) in MicroStation or a secondary coordinate system
in other CAD software systems.
For most PDS projects, the PM corresponds to a survey benchmark or some well-known
immovable landmark at the plant site from which measurements can be made. The DVM may
also correspond to a benchmark or well-known point, but it usually differs from one
corresponding to the BM. For instance, if it is convenient to route piping in an out-building with
respect to the southwest corner of the building, then that corner of the building may be

designated as the DVM so that specifying locations within the building during the design process
may be more convenient. In either case, PDS always knows how to cross-convert from the two
coordinate systems, so both systems may be used interchangeably for the purposes of routing
or for annotation of design documents.
Drawings are produced from the model. Although drawings can be created at different scales,
they all reference the actual model graphics to avoid discrepancies with the model.
Each model represents a unique partition of the design database. This enables you to access all
the data for a single model (independently of the other project data) for the purpose of creating
or modifying information. However, you can also perform interference checking and create
reports based on the combined data from all the models in a project.
The Project Administrator module controls the creation and modification of the PDS 3D projects.
Each project consists of a project control database, design database, piping and equipment
models, reference models (structural, HVAC, and raceway), a set of drawings, and a collection
of reference data. The reference data may be specific to one project or shared by more than one
project.
Working in Three Dimensions

All PDS models exist in three dimensions. Many design manipulations can be executed in a
2D-like manner, but difficult routing situations and precise device placement require an
understanding of working in a three dimensional environment. Any work done in PDS can be
viewed in 3D from any angle.
PDS drawings are also created in three dimensions. However, all the graphics you draw lie on a
single plane. Think of this plane as a sheet of drawing paper on a drafting board.
Everything you draw on this sheet of paper is contained within one plane only (has only height
and width).

This single drawing plane in which you place 2D graphics can be located anywhere within the
3D graphics system. When you place graphics in a plane other than this one, you create a 3D
file. Therefore, a design file with graphics on only one plane is two dimensional; one with
graphics on more than one plane is three dimensional. The graphic components placed in a
PDS model have designated height, depth, and width, making the design file a 3D file.
All graphic elements must be placed in the design cube. The design cube is a volume of
three-dimensional space you can think of as being inside the display terminal (as depicted by
the dashed lines in the figure below).
PDS has the tools to place graphics at any point in the design cube and to look at the design
cube from any angle.
Imagine that a design cube actually does exist within your terminal. If that were so, you would
look into the 3D design cube from the terminal screen in the same way you would look at a box
from one side.

You normally think of looking at the design cube from one side or direction at a time. However,
you can also look at more than one view, such as the top, front, right, and isometric views at the
same time. These views represent the cube from the corresponding sides.
Notice that the isometric view (also called the rotated view) shows the design cube from an
apparent angle of 30°. Actually, the view is rotated 45° in two directions: the cube is displayed
from the top front right.

When a three-dimensional component is drawn or placed in the design cube, you are able to
see different sides of the component by looking at different sides of the design cube.
The cube is built around a Cartesian (or Rectangular) coordinate system with the view from the
top such that the y axis is up, the x axis is to the right, and the z axis out (toward you), as shown
below.
Design Cube Showing Cartesian Coordinate System
Working Units
The working units for a design volume define the extent of the design volume and the precision
of operations. You can revise the working units to be used for any model or drawing files created
in the project.

For interference checking and reference models to work properly, any changes to the
working units should be made for all the 3D models for the project.
Each 3D design file is composed of over 4,000,000,000 units of resolution (UORs). Working
units relate UORs to a measurement unit such as feet or meters and define how these units are
divided. The total units of resolution are divided into master units, sub units, and positional units
(MU:SU:PU) which define the number of addressable points and thereby the precision of
operations. The following outlines the standard working unit definitions for PDS.
Recommended Working Units - English

File MU SU PU Area
Models (Piping, Equipment, 1 FT 12 IN 2032 176138 FT

Structural, Raceway, HVAC, Civil
Architecture, MicroStation)
Drawing 1 FT 12 IN 195072 1834 FT
Recommended Working Units - Metric
File MU SU PU Area
Models 1M 1000 MM 80 53687 M
Drawing 1M 1000 MM 7680 536 M

Reasoning
The recommended PDS settings for English working units results in 24,384 UORs per foot
(1x12x2032). Dividing this number into the available UORs in the design file yields an area of
coverage of 176,138.75 feet or 33.3 miles.
Working units establish the scale of the data. The actual SU and PU values do not matter as
long as the total UORs per master unit are the same. Therefore the English units can be
converted to metric units to create compatible models.
Dividing the total UORs per foot by the metric conversion factor provides the UORs per meter.
This value was used to assign the metric values 1:1000:80. Therefore, the values of 1:12:2032
for English units and 1:1000:80 for metric units are compatible.
The recommended English (2032) and metric (80) values allow a file created using the English
system to be viewed and edited in metric mode without scaling or altering data. The positional
units for drawings should be defined so that the drawing has the same
resolution as the model. To maintain the same resolution, the smallest drawing view scale is
used so that the PUs of the drawing file are no less than the maximum factor times the PUs
used in the model.
For English units, the smallest drawing view scale for the delivered drawing seed files is 1/8" = 1'
(12"). This yields a factor of 96 to be applied to the model units to determine the drawing units.
For metric units, the factor is 100 (96 x 80 = 7680).
3D Coordinate Systems
The 3D coordinate systems used in PDS are Cartesian, or rectangular, coordinate systems,
which define points within the space of the design cube by measuring distances along the x, y,
and z axes.
Rather than use x, y, and z axes, which change according to the view alignment, PDS uses
Easting, Northing, and Elevation axes.

Plant Coordinate System

The Plant Coordinate System (PCS) is defined in terms of a plant monument. The plant
monument defines the Easting, Northing, and Elevation coordinates to be assigned to the center
of the MicroStation design volume. The following form, found in Project Data Manager, is used
to specify the Easting, Northing, and Elevation values of the plant monument.

The plant monument is located at the MicroStation point designated as 0, 0, 0. The following
diagram illustrates the Plant Coordinate system when accepting the default values (0, 0, 0) for
the plant monument and when the recommended working units are used:
As previously mentioned, the default working units yield an area of coverage of 176,138.75’
(33.3 miles, or 53.58 Kilometers). Since the plant monument is always in the center of the
design cube, you can divide 176,135.75’ by 2 to determine the extents of the Plant Coordinate
System. The maximum Easting, Northing, and Westing, Southing, Up, or Down coordinate is
88,069’ - 4.5"
Entering the Easting value of -5000 is the same as entering Westing 5000; Northing
-20,000 is the same as Southing 20,000.
Do not modify the MicroStation Global Origin for piping or equipment seed files or
models. In general, this is also not necessary for other disciplines’ seed or design files. Only if it
appears that there will not be enough design plane to contain all graphics (such as may be the
case for large material-conveying systems spanning several miles) should you even consider a
global origin change. It would always be a good idea to consult a PDS Support contact before
making such a change.
If only positive Easting, Northing, and Westing values are entered, and the default plant
monument values were accepted, you are restricted to using only half of the available design
volume. To work within the constraints of positive Easting and Northing values and still use the
entire design cube, you must modify the Easting and Northing values of the plant monument.

For example, let us assume that the Plant monument is defined to be Easting 88,069’ - 4.5",
Northing 88,069’ - 4.5", and Elevation 0, as shown below.
With these settings, the Plant Coordinate System would be defined as follows:


The orientation of the plant coordinate system changes as you look at different views of the
graphic component, but it stays the same in relation to the component.

The graphic below shows a plant model with preliminary piping and equipment. The front of the
plant is seen in the front view, the top of the plant in the top view, and so forth. The coordinate
system stays the same in relation to the design. Looking at each view, however, gives you a
different perspective of the coordinate system.
Design Volume Coordinate System

The Design Volume Coordinate System (DVCS) is a second coordinate system (in addition to
the Plant Coordinate System) that can be defined for an individual model. A DVCS is only
required if different models need to have their coordinates referenced from a different point; it is
analogous to the MicroStation Auxiliary Coordinate System.

The DVCS is defined in terms of a Design Volume Monument, which defines the Easting,
Northing, and Elevation coordinates to be assigned to the center of the design volume of the
model.
You can select from two orientations (or use the Other button to select the preferred degree
value) to define the plan view for the design volume, through the Project Data Manager.
 North defines North at the top of the screen in a plan view.
 North  defines North at the right of the screen in a plan view.
 Other allows you to define North as a keyed-in degree value.
The system uses the global coordinate system to maintain the relationship among the various
reference models attached to the working model.

Examples
The following examples show various ways of modifying the Plant Coordinate System or Design
Volume Coordinate System for various working conditions

DVCS Oriented From Plant North

With values keyed into the Design Volume Coordinate System Definition form as shown
below, the design volume monument would be located at 350, 325, 0, and it would be rotated
350 degrees (clockwise) from Plant North.

If a plant consisted of 3 buildings within a 33.3-mile range, with each building at a different angle
than the other two, then the files might be defined as follows:

Note that, in the example, a unique design volume coordinate system has been defined
for each model.
While placing components in Building 1, the user might prefer to enter values relative to the SW
corner of the building, rather than entering the large values associated with the Plant Coordinate
system. To do this, the project administrator should create a model with a Design Volume
Monument located at the SW corner. In Plant Coordinate System, this coordinate would be
Easting -60,000 (Westing 60,000), Northing -75,000 (Southing 75,000), and Elevation 0. In the
Design Volume coordinate system, the location should be Easting 0, Northing 0, and Elevation
0.
When a Design Volume Coordinate System has been defined, the user has the choice of
viewing and entering coordinates using the Design Volume Coordinate System or the Plant
Coordinate System.
This capability becomes even more valuable when placing components in buildings such as
Building 2 and Building 3, which are rotated with respect to Plant North. Review the coordinates
for these buildings in the next three screen images.
Building 1
Notice that the design volume is NOT ROTATED with respect to the PCS.

Building 2
Notice that the design volume is ROTATED 330 DEGREES with respect to the PCS.
Building 3
Notice that the design volume is ROTATED 30 DEGREES with respect to the PCS.

SECTION 2
Database Overview
PDS uses relational databases to store information about virtually all aspects of the project
including:
 Project data, such as file names and locations.
 Reference data, such as piping commodity descriptions.
 Design data, such as temperature and pressure values associated with graphic elements.
PDS provides a consistent interface for the maintenance of these databases.
All databases you create will be relational databases, meaning that they are based on a
relational data model–a relation being a two-dimensional table made up of rows and columns.
Most relational databases have a Structured Query Language (SQL) interface. The PDS
products attach to the relational databases through Intergraph Corporation's Relational Interface
System (RIS). RIS is a generic relational database interface that isolates the SQL interface
differences in specific vendors' relational database management systems (RDBMSs). It provides
a generic networked access to all databases generated with popular RDBMSs supported by
RIS, including Oracle and MS SQL.
PDS and the Relational Interface System (RIS)

PDS uses RIS to define information in an RDBMS. An RIS schema identifies a unique
database/user combination in the commercial database system.
Users are established for different RDBMSs in different ways; in fact, the concept of a database
differs greatly from one RDBMS to another. The various interfaces provided in PDS let you
maintain databases through RIS efficiently, without requiring you to know the differences
between RDBMSs or the syntax of the RIS create schema statement.
RIS works in conjunction with existing databases. You must have RIS implemented on your
network and also have one of the Relational Database Management Systems (RDBMSs)
supported by RIS, such as Oracle or MS SQL.
Intergraph Corporation recommends that database creation and manipulations be performed at
the System Manager level. The System Manager should be familiar with the theory and practice
of the Relational Interface System to be successful. See the Relational Interface System (RIS)
Reference Manual for full information.

Database Overview
The database installation program involves significant decisions regarding the size of the
database to be created, the maximum number of users to be supported, the frequency of
automatic backups, and other important issues. Intergraph Corporation recommends that a
system manager who has reviewed the database installation programs install and configure the
databases.
See the Product Compatibility Matrix for a list of RIS Data Server and RIS Client versions to
use with a particular Relational Database version.

Database Overview
PDS System Configurations

This section describes the configuration options for PDS. PDS can be implemented on a
network consisting of file servers, database servers, and client nodes.
Client/Server Relationship
PDS is scalable and can be run on a single node or distributed across a number of client and
server nodes. Client nodes are Intel workstations running Windows.
Server nodes are multi-processor type Intel servers running Windows server software. Server
nodes can be classified into the following categories:
 Database Server
This is the location of the Relational Databases. All databases will be created and stored on
this machine.
 File Server
This is the central location used to store the project files such as reference data libraries,
seed files, model files, drawings, and reports.
 Compute Server
A compute or process server has the same configuration as a client workstation, but has a
powerful CPU and a large amount of memory. It is used for process intensive operations
such as interference checking, reporting or isometric drawing generation.

Database Overview
 Plot Server
A plot server can optimize your printing and plotting processes depending on the number of
plotting devices in use, the number of plots being produced, and the size and type of the
plots. InterPlot is designed on a client-server model similar to RIS. PDS Client computers
submit plots through InterPlot Organizer, which route the plot to the InterPlot Server.
Printers and plotters must be created on the Plot Server and shared for use by the InterPlot
client machines.
 License Server
When you purchase or lease PDS, you are given a key that provides a number of license
seats. Licenses are graded by functionality such as 3D, 2D, and Batch Iso. A SmartPlant
License Manager key contains encoded information that tells the server how many of each
license you have and when they expire. SmartPlant License Manager distributes these
licenses as requested by the clients. It keeps track of how many licenses of which type have
been given out and how many remain in the pool.
Acting as a PDS license server places very little load on the selected computer. The
SmartPlant License Manager server must have a static TCP/IP address and must also be
accessible to the administrator and all client machines.
Depending on system requirements you can designate one server to perform all of these duties
or distribute them among multiple machines.
A client is a node which accesses data or performs a function on the remote resource (usually a
server). In most PDS configurations, the files reside on the server and processing takes place
on the client workstation.

Database Overview
PDS 3D Databases
A 3D project uses three database schemas for piping and equipment data as outlined in the
following illustration.

Database Overview
The 2D and 3D project share a common project control database.
The Express Project Creation and Project Administrator commands are used to create the
database files, seed files, and project environment files. A 3D project is divided into design
areas by disciplines. Disciplines represent the various 3D modeling applications (such as Piping,
Equipment, and HVAC). A design area represents a specific volume of the project for a given
discipline. Each design area comprises a set of models which contain the actual design data.
Database Information
A database is a collection of formatted data which conforms to a set of predefined rules. The
PDS Databases are composed of a set of tables (entities) which represent categories of data.
A table is a defined set of columns (attributes) which describe an item, such as the Piping
Commodity Data table.
An attribute is a single type of information to be stored about an item, such as nominal diameter
or end preparation. Each attribute has a column number in the database table and a name
which describes the piece of information to be stored. The actual information stored in the
database is referred to as the attribute value.

Database Overview
Attribute Types
The following conventions are used to designate the field type for database attributes.
character(n)
alphanumeric field n characters in length
integer
double word integer
short
short integer
double
real (floating point) value
standard note nnnn
Standard Note Type for code-listed attribute
Code-Listed Attributes
A code-listed attribute is an attribute whose value must be defined using one of the selections
from a particular code list in the Standard Note Library. In the database definition files, attributes
which are code-listed are identified by a standard note number at the end of the line following
the field type description. For example, the line
6. fluid_code , character(6) , standard note 125
indicates that fluid_code is defined in terms of code list numbers belonging to Standard Note
125, Fluid Code/Connector Type. A possible entry for this attribute would be 197 for chlorine gas
(GCL).
CL125, Fluid Code/Connector Type (999), 1 = [Blank]
11 = A [Air]
14 = AC [Combustion air]
17 = AE [Aeration air]
20 = AI [Instrument air]
:
:
191 = G [Gas]
194 = GCD [Carbon dioxide gas]
197 = GCL [Chlorine gas]
198 = GCN [Chlorination gas]
200 = GF [Fuel gas]
203 = GG [Flue gas]
206 = GH [Hydrogen gas]
209 = GHS [Hydrogen sulphide gas]

Database Overview
Database Definition Files

This section lists the delivered database definition (ddl) files for Workstation PDS. These files
are delivered with the PD_Shell product in the directory win32app\ingr\pdshell\ddl. When you
create a project, the system copies these files to the project directory and uses them to create
the database tables and columns.
Project Control Database

# Project Control Database
# Default Relational Database Definition
# The user must not revise this database definition other than to change
# column names.
# Project Description Data
table number = 101 , number of columns = 7
1 , system_unique_no , integer
2 , project_no , character(15)
3 , project_name , character(40)
4 , job_no , character(40)
5 , company_name , character(40)
6 , plant_name , character(40)
7 , site_id , character(10)
# Reference Database Management Data
table number = 102, number of columns = 9
1 , type_of_rdb_data , short
2 , approval_status , short
3 , rdb_file_spec , character(14)
4 , path_name , character(36)
5 , network_address , character(26)
6 , lock_owner , character(10)
7 , lock_status , short
8 , lock_date , integer
9 , revision_date , integer
# Project Control Data
1 , product_version_no , short
2 , report_path , character(36)

Database Overview
3 , report_node , character(26)
4 , report_format_path , character(36)
5 , report_format_node , character(26)
6 , report_filter_path , character(36)
7 , report_filter_node , character(26)
8 , piping_eden_path , character(36)
9 , piping_eden_node , character(26)
10, eden_table_path , character(36)
11, eden_table_node , character(26)
12, piping_spec_path , character(36)
13, piping_spec_node , character(26)
14, assembly_path , character(36)
15, assembly_node , character(26)
16, model_builder_path , character(36)
17, model_builder_node , character(26)
18, design_review_path , character(36)
19, design_review_node , character(26)
20, std_note_lib_path , character(36)
21, std_note_lib_node , character(26)
22, eqp_eden_path , character(36)
23, eqp_eden_node , character(26)
24, tdf_table_path , character(36)
25, tdf_table_node , character(26)
26, clash_report_path , character(36)
27, clash_report_node , character(26)
28, clash_plot_path , character(36)
29, clash_plot_node , character(26)
30, mdl_status_low_dr , short , standard note 1605
31, mdl_status_high_dr , short , standard note 1605
32, mdl_status_low_ic , short , standard note 1605
33, mdl_status_high_ic , short , standard note 1605
34, area_owner_opt_ic , short
35, eqp_insul_opt_ic , short
36, eqp_con_tol_opt_ic , short
37, clash_rpt_index_no , integer
38, report_search_path , character(36)
39, report_search_node , character(26)
40, sup_tdf_table_path , character(36)
41, sup_tdf_table_node , character(26)
# Project Archival Management Data
1 , archival_index_no , integer
2 , archival_number , character(24)
3 , archival_descript , character(40)
4 , archival_file_spec , character(14)
7 , month_map , integer
8 , day_of_week_map , integer

Database Overview
9 , day_map , integer
10, time_of_day , integer
11, schedule_type , short
# Site Description Data
2 , site_description , character(40)
3 , min_model_range , integer
4 , max_model_range , integer
5 , min_dwg_range , integer
6 , max_dwg_range , integer
7 , min_dwg_view_range , integer
8 , max_dwg_view_range , integer
9 , min_pip_partition , integer
10, max_pip_partition , integer
11, min_eqp_partition , integer
12, max_eqp_partition , integer
13, master_flag , short
# Model Management Data
# Engineering Discipline Data
1 , discipline_indx_no , short
2 , discipline_name , character(20)
3 , intra_disc_ifc_flg , short
4 , discipline_mtrx_a, integer
5 , discipline_mtrx_b, integer
# Design Area Data
2 , area_index_no , short
3 , area_name , character(10)
4 , area_description , character(40)
5 , volume_low_x , integer
6 , volume_low_y , integer
7 , volume_low_z , integer
8 , volume_high_x , integer
9 , volume_high_y , integer
10, volume_high_z , integer
11, interference_mode , short

Database Overview
12, area_lock_owner , character(10)

13, area_lock_status , short
14, area_lock_date , integer
15, clash_rpt_index_no , integer
# Model Data
1 , model_index_no , integer , index 1

4 , partition_no , short
5 , model_no , character(10)
6 , model_description , character(40)
7 , model_file_spec , character(14)
10, lock_owner , character(10)
11, lock_status , short
12, lock_date , integer
13, verification_date , integer
14, revision_date , integer
15, responsible_disc , short
16, model_type , short
17, model_status , short , standard note 1605
# Piping Model Data
1 , partition_no , short
2 , max_segment_number , integer
3 , max_piping_number , integer
4 , max_pipe_number , integer
5 , max_instr_number , integer
6 , max_support_number , integer
# Model Setup Data
2 , default_path_name , character(36)
3 , default_node , character(26)
4 , ref_mdl_symbology , short
5 , symbology_display , short
# Structural Management Data

Database Overview
# Structural Sub-Project Control Data
1 , sub_project_ndx_no , short
2 , sub_project_no , character(15)
3 , sub_project_name , character(40)
4 , sub_project_path , character(36)
5 , sub_project_node , character(26)
6 , sub_project_mount , character(50)
# Structural Design Area Per Sub-Project Data
2 , sub_project_ndx_no , short
# Inspection Iso Data
1 , inspection_iso_id , character(24)
2 , inspection_status , short
3 , max_inspection_key , short
# Model Ownership Data
1 , model_index_no , integer , index 1

# Drawing Management Data
# Drawing Data
1 , dwg_index_no , integer , index 1

2 , drawing_no , character(24) , index 2

Database Overview
3 , drawing_title , character(40)
4 , default_scale , character(16)
5 , approval_initials , character(4)
6 , approval_date , integer
7 , approval_status , short , standard note 35
8 , completion_status , short
9 , drawing_size , short , standard note 1202
10, drawing_type , short , standard note 2000 , index
3
11, last_revision_no , character(2)
12, drawing_file_spec , character(14)
13, path_name , character(36)
14, network_address , character(26)
19, last_rev_index_no , short
20, release_revision , character(2)
21, release_date , integer
22, checking_status , short
23, standard_note_no_a , short , standard note 499
24, standard_note_no_b , short , standard note 499
25, custom_1 , character(40)
33, custom_9 , integer
# Drawing View Data
1 , dwg_view_index_no , integer , index 1

2 , dwg_view_no , character(24) , index 2
3 , dwg_view_name , character(40)
4 , dwg_view_scale , character(16)
5 , dwg_index_no , integer
6 , saved_view_name , character(6)
7 , viewing_direction , short , standard note 1620 optional
8 , composition_status , short , standard note 1630
9 , dwg_view_x_low , double
10, dwg_view_y_low , double
11, dwg_view_z_low , double
12, dwg_view_x_high , double
13, dwg_view_y_high , double
14, dwg_view_z_high , double

Database Overview
15, vhl_category_index , short

16, drawing_view_type , short
# Drawing View Reference Model Data
1 , dwg_view_index_no , integer
2 , model_index_no , integer
# Composite Drawing View Data
1 , comp_dwg_index_no , integer , index 1

2 , comp_dwg_view_no , character(24)
3 , comp_dwg_view_name , character(40)
4 , comp_dwg_v_scale , character(16)
6 , dwg_view_index_a , integer
7 , dwg_view_index_b , integer
8 , dwg_view_index_c , integer
9 , dwg_view_index_d , integer
10, dwg_view_index_e , integer
11, dwg_view_index_f , integer
12, dwg_view_index_g , integer
13, dwg_view_index_h , integer
14, dwg_view_index_i , integer
15, dwg_view_index_j , integer
# Drawing Revision Data
2 , revision_index_no , short
3 , revision_no , character(2)
5 , revision_by , character(4)
6 , checked_by , character(4)
7 , rev_description , character(40)
8 , appr_by_1 , character(4)
9 , appr_by_2 , character(4)
10, appr_by_3 , character(4)
11, appr_by_4 , character(4)
12, appr_by_1_date , integer
16, checked_date , integer

Database Overview
# Drawing Setup Data
1 , drawing_type , short , standard note 2000

3 , drawing_scale , character(16)
6 , discipline_mask , short
7 , alternate_seed_opt , short
8 , cell_file_spec , character(14)
9 , cell_path_name , character(36)
10, cell_net_address , character(26)
11, plot_catgy_mask_a , integer
12, plot_catgy_mask_b , integer
13, label_mask_a , integer
14, label_mask_b , integer
15, label_mask_c , integer
16, label_mask_d , integer
# Reference Model Display Category Setup Data

3 , category_mask_a , integer
4 , category_mask_b , integer
5 , category_mask_c , integer
6 , category_mask_d , integer
7 , vhl_category_msk_a , integer
8 , vhl_category_msk_b , integer
9 , vhl_category_msk_c , integer
10, vhl_category_msk_d , integer
11, vhl_ref_symbology , short
12, vhl_symbology , short
# Plotting Default Data

Database Overview
1 , iplot_index_no , integer
2 , iplot_number , character(24)
3 , iplot_description , character(40)
4 , iplot_file_spec , character(14)
# Drawing Ownership Data

###################################################
# Interference Management Data
# Clash Management Data
1 , system_unique_no , integer , index 1

4 , unique_sequence_no , integer
5 , completion_date , integer
6 , control_user_no , short
7 , env_creation_date , integer
8 , clash_check_option , short , standard note 1208
9 , volume_filter_opt , short , standard note 1209
10, volume_low_x , integer
11, volume_low_y , integer
12, volume_low_z , integer
13, volume_high_x , integer
14, volume_high_y , integer
15, volume_high_z , integer
# Clash Data Per Project
1 , unique_clash_id , integer , index 1

2 , if_approval_status , short , standard note 1203
3 , comp_a_unique_id , integer
4 , comp_b_unique_id , integer
5 , model_index_no_a , integer
6 , model_index_no_b , integer

Database Overview
7 , discipline_index_a , short
8 , discipline_index_b , short
9 , recent_clash_type , short , standard note 1204
10, recent_plot_date , integer
11, recent_review_date , integer , index 2
12, recent_sequence_no , integer
13, area_index_no , short
14, action_discipline , short
15, recent_seq_no_b , integer
16, area_index_no_b , short
# Clash Data Per Job

3 , unique_sequence_no , integer
4 , clash_type , short , standard note 1204
5 , comp_a_range_x_lo , integer
6 , comp_a_range_y_lo , integer
7 , comp_a_range_z_lo , integer
8 , comp_a_range_x_hi , integer
9 , comp_a_range_y_hi , integer
10, comp_a_range_z_hi , integer
11, comp_b_range_x_lo , integer
12, comp_b_range_y_lo , integer
13, comp_b_range_z_lo , integer
14, comp_b_range_x_hi , integer
15, comp_b_range_y_hi , integer
16, comp_b_range_z_hi , integer
17, env_pair_type , short , standard note 1204
# Component Clash Data Per Project
1 , unique_comp_id , integer , index 1

2 , comp_table_number , short
3 , comp_row_number , integer
5 , primary_descript , character(20)
6 , secondary_descript , character(40)
7 , comp_model_status , short
# Clash Review History Information

Database Overview

3 , review_date , integer
4 , review_user_no , short
5 , responsib_user_no , short
6 , action , short , standard note 1205
7 , review_comment , character(100)
8 , approval_method , short , standard note 1207
# Clash Plot History Information

2 , unique_clash_id , integer
3 , plot_date , integer
4 , plot_user_no , short
# Report Management Data
# Report Data
1 , report_index_no , integer , index 1

2 , report_no , character(24) , index 2
3 , report_title , character(40)
7 , last_revision_no , character(2)
8 , report_file_spec , character(14)
15, format_index_no , integer
16, filter_index_no , integer
18, report_source , short , standard note 1310
19, report_type , short , standard note 1312
20, search_index_no , integer
# Report Format Data

Database Overview
1 , format_index_no , integer , index 1

2 , format_number , character(24)
3 , format_description , character(40)
4 , format_file_spec , character(14)
11, rpt_format_source , short , standard note 1310
# Report Discrimination Data
1 , filter_index_no , integer , index 1

2 , filter_number , character(24)
3 , filter_description , character(40)
4 , filter_file_spec , character(14)
11, rpt_filter_source , short , standard note 1310
# Report Revision Data
1 , report_index_no , integer
# Report Search Criteria Data
1 , search_index_no , integer , index 1

2 , search_number , character(24)
3 , search_description , character(40)
4 , search_file_spec , character(14)

Database Overview
11, rpt_search_source , short , standard note 1310
# DesignReview Management Data
1 , review_index_no , integer , index 1

2 , review_no , character(24)
3 , review_title , character(40)
4 , review_type , short , standard note 1410
5 , control_file_spec , character(14)
6 , control_path_name , character(36)
7 , control_node , character(26)
8 , control_lock_owner , character(10)
9 , control_lock_stat , short
10, control_lock_date , integer
11, tag_file_spec , character(14)
12, tag_path_name , character(36)
13, tag_node , character(26)
14, tag_lock_owner , character(10)
15, tag_lock_status , short
16, tag_lock_date , integer
17, session_rev_date , integer
18, label_rev_date , integer
19, label_file_spec , character(14)
20, label_path_name , character(36)
21, label_net_address , character(26)
22, month_map , integer
23, day_of_week_map , integer
24, day_map , integer
25, time_of_day , integer
# Package/Release Management Data
# Package Data
1 , package_index_no , integer , index 1

2 , package_no , character(24)

Database Overview
3 , package_title , character(40)
4 , release_revision , character(2)
5 , release_date , integer
# Document Data
1 , document_index_no , integer
2 , package_index_no , integer
3 , document_source , short , standard note 1710
4 , document_type , short , standard note 1720
# Pipe Support Drawing Management Data
1 , support_unique_no , integer
2 , ganged_id , integer
3 , grouped_id , integer
5 , model_index_no , short
7 , drawing_file_spec , character(40)
10, support_lineid , character(40)
11, material_index , character(20)
12, revision_no , short
14, drawing_status , short
15, sheet_no , short
16, sheet_total , short

1, weld_id , character(80)
2, weld_id_data , character(40)
3, last_modified_date , integer
# Isometric Drawing Management Data
# Isometric Files Data

Database Overview
1 , isofile_indx_no , integer
2 , isodflt_indx_no , integer
3 , isofile_type , short
4 , isofile_spec , character(14)
7 , iso_description , character(40)
# Project Options Data
1 , isoproj_indx_no , integer , index 1

2 , isoproj_task_opt , short
3 , isoproj_name_opt , short
4 , isoproj_dwg_opt , short
6 , reserved_1 , character(26)
9 , batch_options , character(20)
10, isoproj_name_label , short
11, isoproj_dwg_label , short
12, sub_directory_opt , short
# Defaults Set Data
2 , isodflt_tag , character(12) , index 1
3 , isodflt_descr , character(40)
4 , isodflt_rev_date , integer
# Isometric Design Area Definition Data
1 , iso_area_indx_no , integer
2 , area_indx_no1 , short , index 1
3 , area_indx_no2 , short
8 , selection_mode , short

Database Overview
9 , iso_area_name , character(10)
10, iso_area_desc , character(40)
11, user_data_indx_no , integer
12, isodflt_indx_no , integer
13, cont_indx_no1 , short
# Isometric User Data
1 , user_data_indx_no , integer
2 , type_of_user_data , short
3 , user_data_1 , character(40)
10, user_data_8 , character(40)
# Isometric Drawing Extraction Data
1 , drawing_indx_no , integer
2 , iso_area_indx_no , integer , index 1
3 , lineid_1 , character(24) , index 2
4 , lineid_2 , character(24)
5 , lineid_3 , character(24)

Database Overview
6 , number_of_sections , short
7 , drawing_number , character(24)
8 , batch_ref_no , character(12)
9 , iso_dgn_name , character(24)
10, model_status_code , character(2)
11, model_revised_date , integer
12, lst_extraction_date, integer
13, tot_no_extractions , short
14, no_sheets_extract , short
15, last_mto_date , integer
16, mto_to_mtl_control , integer
17, no_of_revisions , short
18, user_data_indx_no , integer
19, iso_type , short , index 3
# Isometric Drawing Revision Information
1 , draw_rev_indx_no , integer
2 , draw_sht_indx_no , integer , index 1
3 , type_of_revision , short , index 2
4 , revision_number , short , index 3
5 , generated_by , character(3)
7 , approved_by , character(3)
8 , extraction_date , integer
9 , extraction_no , short
10, sheets_extracted , short
11, rev_description , character(60)
12, isodflt_indx_no , integer
# Isometric Last Used Occurrence Data
1 , table_no , integer
2 , last_used , integer
# Isometric Sheet Extraction Data
1 , sheet_indx_no , integer
2 , drawing_indx_no , integer , index 1
3 , sheet_no , integer , index 2
4 , last_extract_date , integer
5 , tot_no_extractions , integer
6 , last_mto_date , integer
7 , no_of_revisions , integer

Database Overview
# Isometric Drawing Re-Extraction Data
1 , drawing_indx_no , integer , index 1

2 , section_no , short , index 2
3 , start_traversal_x , integer
4 , start_traversal_y , integer
5 , start_traversal_z , integer
6 , start_entity , short
7 , start_comp_occ , integer
8 , start_seg_occ , integer
Design Database
# Piping Design Database
# The user must not revise this database definition other than to change
# column names. Adding user-defined columns and changing lengths of
# character data, where valid, must be performed in the Project
Administrator
# when the project is created.
# Piping Segment Data

2 , line_number_label , character(40)
3 , line_id , character(24)
4 , unit_number , character(12)
5 , unit_code , character(3)
6 , module_no , character(16)
7 , package_system_no , character(12)
8 , train_number , character(2)
9 , fluid_code , short , standard note 125
10 , line_sequence_no , character(16)
11 , nominal_piping_dia , short
12 , piping_mater_class , character(16)
13 , gasket_separation , character(8)
14 , insulation_purpose , short , standard note 220
15 , insulation_thick , double
16 , insulation_density , double , standard note 1074 (units)
17 , heat_tracing_reqmt , short , standard note 200
18 , heat_tracing_media , short , standard note 210
19 , heat_tracing_temp , double
20 , construction_stat , short , standard note 130

Database Overview
21 , hold_status , short , standard note 50

23 , schedule_override , character(8) , standard note 332
24 , nor_oper_pres , double
25 , nor_oper_temp , double
26 , alt_oper_pres , double
27 , alt_oper_temp , double
28 , nor_dgn_pres , double
29 , nor_dgn_temp , double
30 , alt_dgn_pres , double
31 , alt_dgn_temp , double
32 , steam_outlet_temp , double
33 , mater_of_construct , character(6)
34 , safety_class , short , standard note 340
35 , design_standard , short , standard note 570
36 , design_area_number , character(10)
37 , design_resp , short , standard note 160
38 , construction_resp , short , standard note 160
39 , supply_resp , short , standard note 160
40 , coating_reqmts , short , standard note 190
41 , cleaning_reqmts , short , standard note 230
42 , fluid_category , character(4)
43 , nor_op_pres_units , short , standard note 1064
44 , nor_op_temp_units , short , standard note 1056
45 , alt_op_pres_units , short , standard note 1064
46 , alt_op_temp_units , short , standard note 1056
47 , nor_dgn_pres_units , short , standard note 1064
48 , nor_dgn_temp_units , short , standard note 1056
49 , alt_dgn_pres_units , short , standard note 1064
50 , alt_dgn_temp_units , short , standard note 1056
51 , steam_temp_units , short , standard note 1056
52 , stress_system_no , character(12)
53 , stress_reqmts , short , standard note 360
54 , hyd_system_no , character(12)
55 , hyd_reqmts , short , standard note 360
56 , specific_gravity_a , double
57 , specific_gravity_b , double
58 , specific_gravity_c , double
59 , viscosity , double
60 , density , double
61 , spec_heat_ratio , double
62 , sonic_velocity , double
63 , surface_roughness , double
64 , test_system_no , character(6)
65 , test_fluid , short , standard note 125
66 , test_pressure , double
67 , PID_id_part_a , character(4)
68 , PID_id_part_b , character(4)
69 , end_1_nozzle_id , integer
70 , end_2_nozzle_id , integer
71 , alpha_descript_id , character(12)
72 , standard_note_no , short , standard note 499
73 , pid_index_no , integer

Database Overview
74 , color_code , character(8)
75 , inspection_iso_id , character(24)
76 , index_to_pi_dwg , integer
77 , weld_id , character(80)
78 , sppid_piperun_guid , character(32)
79 , sppid_drawing_guid , character(32)
# Piping Component Data

2 , piping_comp_no , character(20)
3 , commodity_name , character(6)
4 , model_code , character(6)
5 , option_code , short , standard note 400
6 , maximum_temp , double
7 , sched_thick_basis , character(8) , standard note 332
8 , commodity_code , character(16)
9 , MTO_requirements , short , standard note 365
10 , fabrication_cat , short , standard note 180
11 , source_of_data , short , standard note 420
12 , PDS_sort_code , character(6)
13 , physical_data_id , character(8)
14 , geometric_standard , short , standard note 575
15 , weight_code , short , standard note 578
16 , table_suffix_green , short , standard note 576
17 , table_suffix_red , short , standard note 577
18 , materials_grade , short , standard note 145
19 , bend_radius , double
20 , bend_angle , double
21 , face_to_face_dim , double
22 , dimension_a , double
23 , dimension_b , double
24 , dimension_c , double
25 , surface_area , double , standard note 1010 (units)
26 , empty_weight , double , standard note 1028 (units)
27 , water_weight , double , standard note 1028 (units)
28 , operator_weight , double
29 , operator_sym_name , character(6)
30 , chain_operator_no , short
31 , opening_action , short , standard note 390
37 , iso_dwg_index_no , integer
38 , isometric_sheet_no , character(2)
39 , piece_mark_no , character(60)
41 , stress_node_no , short

Database Overview
42 , stress_intens_fact , double
43 , head_loss_factor , double
44 , piping_assembly , character(12)
45 , component_group_no , short
46 , remarks , character(50)
47 , standard_note_no_a , short , standard note 499
48 , standard_note_no_b , short , standard note 499
49 , cp_1_nom_pipe_diam , short
50 , cp_1_outside_diam , double
51 , cp_1_end_prep , short , standard note 330
52 , cp_1_sch_thk , character(8) , standard note 332
53 , cp_1_rating , character(8)
54 , cp_1_face_to_ctr , double
55 , cp_1_weld_no , character(8)
56 , cp_1_weld_type , short , standard note 1100 / 400 (bolt
option)
57 , cp_1_gasket_gap , double
58 , cp_1_gasket_option , short , standard note 400
59 , cp_1_stress_node , short
60 , cp_1_stress_factor , double
61 , cp_1_head_loss , double
option)
option)

Database Overview
option)
100, cp_4_head_loss , double
101, cp_5_nom_pipe_diam , short

102, cp_5_outside_diam , double
103, cp_5_end_prep , short , standard note 330
104, cp_5_sch_thk , character(8) , standard note 332
105, cp_5_rating , character(8)
106, cp_5_face_to_ctr , double
107, cp_5_weld_no , character(8)
108, cp_5_weld_type , short , standard note 1100 / 400 (bolt
option)
109, cp_5_gasket_gap , double
110, cp_5_gasket_option , short , standard note 400
111, cp_5_stress_node , short
112, cp_5_stress_factor , double
114, unique_name , character(12)

115, vlv_operator_dim_a , double
116, vlv_operator_dim_b , double
117, vlv_operator_dim_c , double
118, vlv_operator_dim_d , double
119, last_placed_date , integer

120, generic_comp_no , character(20)
121, inspection_key , short
122, cp_1_inspect_key , short
# Piping/Tubing Data


Database Overview
8 , outside_diameter , double
9 , schedule_thickness , character(8) , standard note 332
11 , rating , character(8)
22 , pipe_length , double
26 , cold_spring_length , double
41 , end_1_end_prep , short , standard note 330

42 , end_1_weld_no , character(8)
43 , end_1_weld_type , short , standard note 1100 / 400 (bolt
option)
44 , end_1_gasket_gap , double
45 , end_1_gasket_opt , short , standard note 400
46 , end_1_stress_node , short
47 , end_1_stres_int , double
48 , end_1_head_loss , double
49 , end_2_end_prep , short , standard note 330

50 , end_2_weld_no , character(8)
51 , end_2_weld_type , short , standard note 1100 / 400 (bolt
option)
52 , end_2_gasket_gap , double

Database Overview
53 , end_2_gasket_opt , short , standard note 400

54 , end_2_stress_node , short
55 , end_2_stres_int , double
56 , end_2_head_loss , double
57 , unique_name , character(12)
58 , last_placed_date , integer
59 , inspection_key , short
60 , end_1_inspect_key , short
61 , end_2_inspect_key , short
# Instrument Component Data

2 , instrument_comp_no , character(20)
16 , face_to_face_dim , double
23 , operator_weight , double , standard note 1028 (units)
24 , operator_type , double
25 , operator_sym_name , character(6)
26 , chain_operator_no , short
27 , chain_length , double
28 , opening_action , short , standard note 390
31 , design_resp , short , standard note 160
32 , construction_resp , short , standard note 160
37 , insulation_thick , double
38 , insulation_density , double , standard note 1074 (units)

Database Overview
39 , cleaning_reqmts , short , standard note 230

40 , safety_class , short , standard note 340
41 , module_no , character(16)
42 , package_system_no , character(12)
47 , stress_node_no , short
48 , stress_intens_fact , double
49 , head_loss_factor , double
option)
option)

Database Overview
option)
option)
107, cp_5_nom_pipe_diam , short

108, cp_5_outside_diam , double
109, cp_5_end_prep , short , standard note 330
110, cp_5_sch_thk , character(8) , standard note 332
111, cp_5_rating , character(8)
112, cp_5_face_to_ctr , double
option)
120, unique_name , character(12)

121, bend_angle , double
122, vlv_operator_dim_a , double
123, vlv_operator_dim_b , double
124, vlv_operator_dim_c , double
125, vlv_operator_dim_d , double
126, last_placed_date , integer

127, generic_comp_no , character(20)
128, inspection_key , short

Database Overview
# Pipe Support Data

2 , pipe_support_no , character(20)
3 , model_code_phy , character(6)
4 , model_code_log , character(6)
5 , iso_support_type_a , short , standard note 380
6 , iso_support_type_b , short , standard note 380
7 , iso_support_type_c , short , standard note 380
8 , iso_support_type_d , short , standard note 380
9 , details_for_shop , character(50)
10 , details_for_field , character(50)
11 , fabrication_orient , character(20)
15 , weight , double , standard note 1028 (units)
18 , standard_note_no , short , standard note 499
23 , isometric_dim_a , double
24 , isometric_dim_b , double
25 , isometric_dim_c , double
26 , isometric_dim_d , double
27 , isometric_dim_e , double
28 , trans_rigidity_x , double
29 , trans_rigidity_y , double
30 , trans_rigidity_z , double
31 , rot_rigidity_x , double
32 , rot_rigidity_y , double
33 , rot_rigidity_z , double
34 , spring_gap_length , double
35 , sping_gap_direct , short
36 , number_of_springs , short
37 , last_placed_date , integer
38 , inspection_key , short
39 , mark_number , character(80)
40 , group_id , integer
41 , gang_id , integer
42 , material_grade , short , standard note 145
43 , weld_code , short
44 , material_index , character(16)
45 , operating_load , double
46 , installed_load , double
47 , hydrostatic_load , double

Database Overview
48 , total_movement_1 , double , in subunits -- distance attribute

49 , total_movement_2 , double , in subunits -- distance attribute
50 , rod_diameter , double , in subunits
# equip_group
1 , equip_indx_no , integer
2 , equip_no , character(30)
3 , equip_descr_1 , character(40)
4 , equip_descr_2 , character(40)
5 , tutorial_no , character(6)
6 , equip_class , character(2)
7 , dry_weight , double
8 , oper_weight_1 , double
9 , oper_weight_2 , double
10 , insulation_thk , double
12 , equipment_division , short , standard note 69
# equip_nozzle
1 , nozzle_indx_no , integer
2 , nozzle_no , character(10)
6 , preparation , short , standard note 330
8 , unit_no , character(12)
9 , fluid_code , short , standard note 125
10 , unit_code , character(3)
11 , line_sequence_no , character(16)
15 , insulation_thk , double
16 , table_suffix , short , standard note 576
17 , service , character(20)
18 , schedule_thickness , character(8)
19 , nor_therm_growth_X , double
20 , nor_therm_growth_Y , double
21 , nor_therm_growth_Z , double
22 , alt_therm_growth_X , double
23 , alt_therm_growth_Y , double
24 , alt_therm_growth_Z , double

Database Overview
# equip_nozzle_extended
1 , nozzle_indx_no , integer
3 , parm_indx_no , integer
4 , parm_noz_no , short
5 , face_of_flange_x , double
6 , face_of_flange_y , double
7 , face_of_flange_z , double
8 , face_flange_pri_1 , double
11 , face_flange_sec_1 , double
14 , face_flange_nor_1 , double
17 , nozzle_type , short
18 , nozzle_length_1 , double
19 , nozzle_length_2 , double
20 , nozzle_radius , double
21 , reference_item , character(11)
22 , ref_loc_x , double
23 , ref_loc_y , double
24 , ref_loc_z , double
25 , ref_loc_pri_1 , double
28 , ref_loc_sec_1 , double
31 , ref_loc_nor_1 , double
34 , orientation_1 , double
38 , dimension_1 , double
44 , c_face_of_flange_x , character(41)
45 , c_face_of_flange_y , character(41)
46 , c_face_of_flange_z , character(41)
47 , c_face_flange_pri , character(31)
48 , c_face_flange_sec , character(31)
49 , c_face_flange_nor , character(31)

Database Overview
50 , c_nozzle_length_1 , character(31)
51 , c_nozzle_length_2 , character(31)
52 , c_nozzle_radius , character(31)
53 , c_ref_loc_x , character(41)
54 , c_ref_loc_y , character(41)
55 , c_ref_loc_z , character(41)
56 , c_ref_loc_pri , character(31)
57 , c_ref_loc_sec , character(31)
58 , c_ref_loc_nor , character(31)
59 , c_orientation_1 , character(11)
63 , c_dimension_1 , character(31)
#equip_datum_point
3 , point_type , short
4 , point_indx_no , short
5 , loc_x , double
6 , loc_y , double
7 , loc_z , double
8 , loc_pri_1 , double
11 , loc_sec_1 , double
14 , loc_nor_1 , double
17 , c_loc_x , character(41)
18 , c_loc_y , character(41)
19 , c_loc_z , character(41)
20 , c_loc_pri , character(31)
21 , c_loc_sec , character(31)
22 , c_loc_nor , character(31)
# equip_primitive
2 , prim_name , character(20)

Database Overview
3 , place_pnt_no , short
4 , place_by_x , double
5 , place_by_y , double
6 , place_by_z , double
7 , place_by_pri_1 , double
10 , place_by_sec_1 , double
13 , place_by_nor_1 , double
16 , category_type , short
20 , dimension_d , double
21 , dimension_e , double
22 , c_place_by_x , character(41)
23 , c_place_by_y , character(41)
24 , c_place_by_z , character(41)
25 , c_place_by_pri , character(31)
26 , c_place_by_sec , character(31)
27 , c_place_by_nor , character(31)
28 , c_dimension_a , character(31)
29 , c_dimension_b , character(31)
30 , c_dimension_c , character(31)
31 , c_dimension_d , character(31)
32 , c_dimension_e , character(31)
# equip_primitive_usr_proj_shape
2 , prim_name , character(20)
3 , place_point_no , short
13 , category_type , short
14 , number_vertices , short
15 , projection , double
16 , vertex_1_x , double
17 , vertex_1_y , double

Database Overview
59 , c_projection , character(31)
60 , c_vertex_1_x , character(31)
61 , c_vertex_1_y , character(31)

Database Overview
# equip_parametric
3 , symbol_name , character(10)
4 , place_pnt_no , short
5 , place_by_x , double
6 , place_by_y , double
7 , place_by_z , double
17 , c_place_by_x , character(41)
18 , c_place_by_y , character(41)
19 , c_place_by_z , character(41)

Database Overview
# equip_parametric_extended
2 , form_indx_no , short
3 , form_name , character(10)
4 , form_fld , short
5 , data_type , short
6 , dimension_no , short
7 , nozzle_fld , short
8 , fld_attribute , short
9 , fld_default , character(21)
10 , fld_name , character(13)
11 , value_real , double
12 , value_char , character(41)

Database Overview
Reference Database
# Specification/Material Reference Database
# The user must not revise this database definition other than to
# change column names.
# Piping Materials Class Data

4 , version_no , character(2)
5 , revision_date , character(10
6 , fluid_code , character(6) , standard note 125
8 , corrosion_allow , double
9 , mat_description , short , standard note 148
10, service_lim_table , character(6)
11, diameter_table , character(6)
12, thickness_table , character(6)
13, materials_table , character(6)
14, thickness_equation , character(6)
15, branch_table , character(6)
16, tap_data_table , character(6)
17, vent_drain_macro , character(6)
18, gasket_separation , character(8)
21, revision_mngt_date , integer
22, bend_deflect_table , character(6)
23, pipe_length_table , character(6)
# Piping Commodity Specification Data

2 , piping_mater_class , character(16) , index 1
6 , gcp_from_nom_diam , short
7 , gcp_to_nom_diam , short
8 , gcp_end_prep , short , standard note 330
9 , gcp_rating , character(8)
10, gcp_sch_thk , character(8)
11, gcp_table_suffix , short , standard note 576
12, rcp_from_nom_diam , short
13, rcp_to_nom_diam , short
14, rcp_end_prep , short , standard note 330

Database Overview
15, rcp_rating , character(8)

16, rcp_sch_thk , character(8)
17, rcp_table_suffix , short , standard note 577
18, commodity_code , character(16)
19, model_code , character(6)
20, PDS_sort_code , character(6)
21, modifier , double
22, geometric_standard , short , standard note 575
23, weight_code , short , standard note 578
24, fabrication_cat , short , standard note 180
25, materials_grade , short , standard note 145
28, input_form_type , short , standard note 990
# Piping Specialty Specification Data

9 , gcp_sch_thk , character(8)
17, physical_data_id , character(8)
# Instrument Component Specification Data


Database Overview
# Tap Properties Data

2 , tap_table_name , character(6)
5 , end_preparation , short , standard note 330
7 , sched_thick , character(8)
8 , tap_material_code , character(10)
# Piping Commodity Size-Dependent Material Data

2 , sys_commodity_code , character(16) , index 1
3 , gcp_nom_diam , short
4 , rcp_nom_diam , short
6 , rcp_sch_thk , character(8)
8 , weld_weight , double
9 , unit_price , double
10, manhours , double
# Piping Commodity Implied Material Data

2 , sys_commodity_code , character(16) , index 1

Database Overview
5 , rcp_from_nom_diam , short
6 , rcp_to_nom_diam , short
8 , quantity , double
9 , fabrication_cat , short
10, standard_note_no , short
# Reference Database Revision Management Data

1 , specialty_rev_date , integer
2 , instr_rev_date , integer
3 , tap_data_rev_date , integer
4 , size_data_rev_date , integer
5 , implied_rev_date , integer
6 , cmp_insul_rev_date , integer
7 , flg_insul_rev_data , integer
8 , con_tol_excl_data , integer
# Component Insulation Exclusion Data

4 , gcp_npd_from , short
5 , gcp_npd_to , short
6 , rcp_npd_from , short
7 , rcp_npd_to , short
8 , heat_tracing_from , short , standard note 200
9 , heat_tracing_to , short , standard note 200
10, insul_purpose_from , short , standard note 220
11, insul_purpose_to , short , standard note 220
12, nor_oper_temp_from , double
13, nor_oper_temp_to , double
# Flange Insulation Exclusion Data

2 , bolted_npd_from , short
3 , bolted_npd_to , short
4 , heat_tracing_from , short , standard note 200
5 , heat_tracing_to , short , standard note 200
6 , insul_purpose_from , short , standard note 220
7 , insul_purpose_to , short , standard note 220
8 , nor_oper_temp_from , double
9 , nor_oper_temp_to , double
# Piping Construction Tolerance Exclusion Data

Database Overview

4 , gcp_npd_from , short
5 , gcp_npd_to , short
6 , rcp_npd_from , short
7 , rcp_npd_to , short
# Piping Support Group

2 , support_group , character(6)
3 , group_descr , character(40)
# Piping Support Commodity Reference Data

2 , support_group , character(6)
4 , npd_from , short
5 , npd_to , short
6 , tdf_table_name , character(8)
7 , temp_table , character(8)
8 , sched_table , character(8)
9 , attachment_type , short
11, material_desr , character(50)
# Piping Support Material Reference Data

3 , npd_from , short
4 , npd_to , short
7 , drawing_seed , character(16)
8 , item_key0 , character(2)
# Piping Support Description Data

3 , sequence_number , short
4 , quantity , short
5 , dimension_att_no , short
6 , implied_status , short
7 , material_descr , character(80)

SECTION 3
Reference Data
The Reference Data Manager (PD_Data) enables you to define and modify the reference data
for the PDS 3D modules. This reference data is used to ensure consistency in the definition of
piping specifications and commodity libraries. It enables you to control and standardize the PDS
3D tasks. You can also modify the reference data to reflect company practices and standards.
The Reference Data for PDS 3D is composed of the following basic components: Piping Job
Specification
 Graphic Commodity Data and Physical Dimension Data
 Material Description Data
 Standard Notes / Code Lists
 Label Descriptions
 Piping Assembly Definitions
The following illustrates the basic components of the Reference Data for PDS 3D.
The Reference Data Manager supports both approved and unapproved reference data for a
project. The Project Control Database contains complete file management data for both an
approved and unapproved version of each type of reference data such as the Piping Job
Specification or the Graphic Commodity Library. This allows revisions to take place in
unapproved files while other activities such as the Piping Designer read the approved files.
Once the information in the unapproved files has been verified, it can be posted to the approved
reference data files.

Reference Data
Delivered Reference Data

The following reference data is delivered in the reference database products for the
corresponding practices (such as RDUSRDB for U.S. practice data or RDDINRDB for DIN
practice data).
Library
File Description Object Text
Physical Dimension Table Library us_pcdim.l us_pcdim.l.t
Piping Job Specification Table Library us_pjstb.l us_pjstb.l.t
Short Material Description Library us_shbom.l -
Long Material Description Library us_lgbom.l -
Specialty Material Description Library us_spbom.l -
For the DIN RDB substitute din_ for us_ in the listed library file names.
The following reference data, which is not unique to any specific practice, is delivered in the
PD_Shell product in the win32app\ingr\pdshell\lib directory.
Library
Graphic Commodity Library pip_gcom.l pip_gcom.l.t
Piping Assembly Library assembly.l assembly.l.t
Label Description Library labels.l -
Standard Note Library std_note.l std_note.l.t
The following reference data for Equipment Modeling is delivered in the PD_EQP product in the
win32app\ingr\pdeqp\dat directory.
Library
Graphic Commodity Library zi_eqpms.lib -
Tutorial Definition Library zi_tutlib.lib -
Cell Library equip.cel -
You should never point to the delivered files for your reference data since this could cause
potential problems when you receive a new version of the software. Instead, you should copy

Reference Data
the reference data files to a separate location. Express Project Creation copies the reference
data to the appropriate directories while creating the project directory files.
For each of the reference data libraries, you can copy the delivered libraries or create a new
(empty) library to which you can load customized data.
Piping Job Specification

The Piping Job Specification (PJS) provides selection criteria for piping commodity items, piping
specialty items, and instruments. The information for the Piping Job Specification is contained in
the following files:
 Specification/Material Reference Database - database containing the definitions for piping
materials classes, commodity items, specialty items, and tap properties tables.
 Spec Table Library - library containing the specification tables referenced in the PJS.
The information in the Specification/Material Reference database and Spec Table Library tables
is also delivered in the form of neutral files which you can extract and modify.
You can use the Piping Job Specification Manager to create or revise the PJS. The Spec
Manager enables you to define or revise the PJS data, and process neutral ASCII files to define
data in the PJS.
Piping Materials Class Data

A piping materials class defines a classification of components based on design data and
service limits. Much of the design data is stored in tables so that common information can be
accessed by more than one piping materials class.
The Piping Materials Class Data table contains 23 attributes.
1 , system_unique_no, integer
4 , version_no , character(2)
5 , revision_date , character(10)
6 , fluid_code , character(6) , standard note 125
8 , corrosion_allow , double
9 , mat_description , short , standard note 148
10, service_lim_table , character(6)
11, diameter_table , character(6)
12, thickness_table , character(6)
13, materials_table , character(6)
14, thickness_equation , character(6)
15, branch_table , character(6)
16, tap_data_table , character(6)
17, vent_drain_macro , character(6)
18, gasket_separation , character(8)
21, revision_mngt_date , integer
22, bend_deflect_table , character(6)
23, pipe_length_table , character(6)

Reference Data
A sample neutral file for US practice is delivered in the file

win32app\ingr\rdusrdb\spec_data\classes.pmc. The following is a partial listing for this neutral
file. Entries in this table should be sorted alphanumerically by Piping Materials Class.
Piping Commodity Specification Data

The Piping Commodity Specification Data defines all the components, pipes, bolts, and gaskets
associated with a particular Piping Materials Class. It defines the standard components found in
a manufacturers catalog (commonly referred to as off-the-shelf components). Because the
Piping Commodity Specification Data is linked to the Piping Materials Class, a separate set of
commodity items must be defined for each Piping Materials Class database table.
Connect Point Data
Information for connect point data is defined in terms of two types of connect points known as
green and red connect points. The following conventions are used to coordinate the two sets of
data:
 If data is only shown under the green connect point, it applies to all ends of the component.
 If a component has ends with different nominal diameters (regardless of other end
properties) the larger nominal diameter is designated as the green connect point.
 If a component has ends with the same nominal diameter but other end properties which
differ, the following rules apply:

Reference Data
 If the ends have different termination types (regardless of the values for
schedule/thickness) the end(s) whose end preparations have the lowest codelist
number are designated as the green connect point.
 If the termination types are the same but the values for rating, schedule, or thickness
differ, the stronger end(s) is designated as the green connect point.
The Piping Commodity Specification Data table contains 28 attributes:
2 , piping_mater_class , character(16) , index 1
10, gcp_sch_thk , character(8)
18, commodity_code , character(16)
The following is a sample neutral file for the Piping Commodity Specification Data. Entries in this
table should be sorted alphanumerically by commodity_name.

Reference Data
A set of neutral files for US practice are delivered in the files

win32app\ingr\rdusrdb\spec_data\*.pcd (one for each piping materials class specified in the
classes.pmc file).
A set of sample files depicting various options are delivered in the
win32app\ingr\pddata\sample\data directory.
bend_tbl.pcd fpipe.pcd metric_npd.pcd
equiv_npd.pcd gasket.pcd piplen_tbl.pcd
fluid_code.pcd gskt_tbl.pcd thickness.pcd
Piping Specialty Specification Data

This database table contains data for a specific specialty item. It is used to define those
specialty items which are used frequently by a particular company or installation. The specialty
items are defined for the entire project, they are not partitioned by Piping Materials Class.
You can also place specialty items interactively in the model by defining the necessary
parameters at the time of placement. No entries in the Material Reference Database are
required for these interactive definitions.
The Piping Specialty Specification Data table contains 25 attributes.
10 , gcp_table_suffix , short , standard note 576
13 , rcp_end_prep , short , standard note 330
14 , rcp_rating , character(8)
16 , rcp_table_suffix , short , standard note 577
19 , modifier , double

Reference Data
A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\specialty.data.
Instrument Component Specification Data

This table contains the data for a specific instrument item. It is used to define the instruments
which are used frequently by a particular company or installation. The instruments are defined
for the entire project, they are not partitioned by PMC.
You can also place instruments interactively in the model by defining the necessary
parameters at the time of placement. No entries in the Material Reference Database are
required for these interactive definitions.

Reference Data
A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\instrment.data.
Tap Properties Data

This table contains the tap properties data that is a function of the tap properties table name and
the nominal piping diameter. These tables define the piping taps which can be added to any of
the components included in a piping materials class. The system uses the information in these
tables and the nominal diameter to provide values for rating, end preparation,
schedule/thickness, and tap code. Tap tables do not allow a NPD range; there must be an
individual entry for each tap diameter.
2 , tap_table_name , character(6)
5 , end_preparation , short , standard note 330
7 , sched_thick , character(8)
8 , tap_material_code , character(10)
win32app\ingr\rdusrdb\spec_data\taps.data.
Double_Spacing
Order= 2 3 5 4 6 7
! By=GJH Ckd By=RJW Rev=2 Date=12-May-1988
Table = C001
! Description= SWE CL3000 default taps
! Diam Opt Rating Prp Sc/Th Tap Code
0.375 691 - 591 NREQD E$37591XXX
> 0.5 1 CL3000 421 NREQD E$50421064

Reference Data
0.5 691 - 591 NREQD E$50591XXX

> 0.75 1 CL3000 421 NREQD E$75421064
0.75 691 - 591 NREQD E$75591XXX
> 1 1 CL3000 421 NREQD E001421064
1 691 - 591 NREQD E001591XXX
> 1.25 1 CL3000 421 NREQD E1 $2,421,064
1.25 691 - 591 NREQD E1 $2591XXX
> 1.5 1 CL3000 421 NREQD E1 $5,421,064
1.5 691 - 591 NREQD E1 $5591XXX
> 2 1 CL3000 421 NREQD E002421064
2 691 - 591 NREQD E002591XXX
2.5 691 - 591 NREQD E2 $5591XXX
> 3 1 CL3000 421 NREQD E003421064
3 691 - 591 NREQD E003591XXX
3.5 691 - 591 NREQD E3 $5591XXX
> 4 1 CL3000 421 NREQD E004421064
4 691 - 591 NREQD E004591XXX
5 691 - 591 NREQD E005591XXX
6 691 - 591 NREQD E006591XXX
8 691 - 591 NREQD E008591XXX
10 691 - 591 NREQD E010591XXX
12 691 - 591 NREQD E012591XXX
14 691 - 591 NREQD E014591XXX
16 691 - 591 NREQD E016591XXX
18 691 - 591 NREQD E018591XXX
20 691 - 591 NREQD E020591XXX
24 691 - 591 NREQD E024591XXX
26 691 - 591 NREQD E026591XXX
28 691 - 591 NREQD E028591XXX
30 691 - 591 NREQD E030591XXX
32 691 - 591 NREQD E032591XXX
34 691 - 591 NREQD E034591XXX
36 691 - 591 NREQD E036591XXX
42 691 - 591 NREQD E042591XXX
48 691 - 591 NREQD E048591XXX
Piping Commodity Size-Dependent Material Data

The Size-Dependent Data table contains the data for a specific commodity item that is
dependent on the commodity code, nominal piping diameter, and schedule/thickness.
This table is used for miscellaneous batch reporting, such as construction cost reports and
requisition orders, and interfaces to material control, stress analysis, and isometric drawing
extraction.
There are multiple occurrences for a specific commodity code and a specific pair of green and
red nominal piping diameters in the Piping Commodity Size-Dependent Material Data table
because schedule/thickness is not included in the commodity code.
2 , sys_commodity_code , character(16)
3 , gcp_nom_diam , short
4 , rcp_nom_diam , short

Reference Data
7 , commodity_code , character(16) , index 1
8 , weld_weight , double
9 , unit_price , double
10 , manhours , double
A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\pcd_size.data.
Piping Commodity Implied Material Data

The Implied Material Data table contains the implied material data for a specific commodity item
that is dependent on both the piping commodity code and nominal piping diameter range.
This data is used strictly for generating implied material for MTO reporting and material control.
It is not used for welds, bolts, nuts, or gaskets, but is reserved for other types of implied
material, such as caps or stubs, for a specific commodity item. It is also used for reporting the
implied components of a commodity item (for example, cap screws).
A unique commodity code must be defined for each commodity definition. For example, if a
commodity code is defined for gate valves from 2" to 14", but you want a different description for
a 12" gate valve, you must assign a new commodity code to the 12" valve.
2 , sys_commodity_code , character(16)
7 , commodity_code , character(16) , index 1
8 , quantity , double
9 , fabrication_cat , short
10 , standard_note_no , short

Reference Data

win32app\ingr\rdusrdb\spec_data\implied.data.

Reference Data
PJS Tables and Functions

The following tables, equations, and calculations are considered part of the Piping Job
Specification even though they are not stored in the Reference Database. The table/equation
names are defined in the Piping Materials Class Data. The actual tables and equations are
stored in the Piping Job Specification Table Library.
 Temperature and Pressure Service Limits table
This table includes the sets of temperatures and pressures that define the boundaries of
acceptability for a piping materials class.
 Nominal Piping Diameter table
The NPD tables lists the diameters for piping and tubing which are valid within any piping
materials class which references this table.
 Thickness Data table
Thickness data is determined as a function of the table name and nominal piping diameter.
These tables include the minimum, retirement, thread, and preferred thicknesses required in
the calculation of piping wall thickness. The tables provide the actual thickness; not a
schedule. Therefore, there must be an individual entry for each diameter. You cannot use an
NPD range.
 Materials Data table
This table consists of the materials data that is a function of the table name, material grade,
wall thickness range, and temperature. These tables include the properties which are
required for the calculation of piping wall thickness.
 Piping Wall Thickness equation and Branch Reinforcement calculation
These tables define formulas for the calculation of piping wall thickness and branch
reinforcement to resist positive pressure. The actual equations and their logic are hardcoded
in the software.
 Branch Insertion table
A branch insertion table defines the selection criteria for tee and lateral branches. Branch
tables define the reinforcement to be used at tee and lateral branches as a function of the
acute angle of intersection and the nominal diameters for the intersecting lines.
The types of branch connections include reinforcing weld, coupling, threadolet, reducing tee,
nipolet, reinforcing pad, sockolet, tee, weldolet, and so forth.
 Gasket Separation table
These tables define the gasket gap to be used for a given nominal diameter and maximum
temperature. For each bolted end, the system uses the applicable table, the NPD of the end,
and the maximum temperature for the gasket to be used to determine the gap thickness to
be used at the end. Lines in this table are sorted by NPD first and maximum temperature
second.

Reference Data
Graphic Commodity Data and Physical Dimension

Data
The graphic commodity data is used to define commodity items, specialty items, instruments,
and pipe supports. The Graphic Commodity Library contains the parametric symbol definitions
required to place piping and instrument components in a 3D model. When you place a
component the system uses the Piping Job Specification to select the appropriate component
from the parametric symbol definition library which then accesses the component dimensional
data.
The graphic commodity data is contained in the following object libraries:
 Graphic Commodity Library - contains the parametric definitions for the commodity items.
Entries in this library use the EDEN programming language.
 Physical Dimension Libraries - contains dimension data for the commodity items. (A different
Physical Dimension Library is required for each type of practice such as, U.S., DIN, or
British Standard)
The parametric descriptions and dimension tables are also delivered in the form of text libraries
which you can extract and modify using the Graphic Data Library Manager and Physical Data
Library Manager.
Refer to Chapter 4, How PDS Works, for examples of parametric definitions and dimension
tables.
Material Description Data

The Material Description Data is accessed for
 Material Take-off (MTO) reporting from the Design Database Other miscellaneous reporting
 Interfaces to material control systems
 Stress analysis
 Isometric drawing extraction.
The Material Description Data consists of the commodity item data which is not stored in the
Design Database, which is not required for the creation of graphic symbologies, and which is not
part of the geometric data. This data is contained in the following files:
 Material Data in the Specification/Material Database - database tables containing definitions
for commodity items, criteria for implied material, and weld data.
 Short Material Description Library - contains the short material descriptions for commodity
items and taps.
 Long Material Description Library - contains the long material descriptions for commodity
items.
 Specialty Material Description Library - contains the material descriptions for specialty items.
The material descriptions are also delivered in the form of neutral files which you can modify and
post to the libraries. The following shows a portion of a neutral file for the short material
description library.

Reference Data
! DEFINE SHORT DESCRIPTIONS
! Date/Time: Wed Jul 7 14:38:03 1993
! Processed Library \..\win32app\ingr\rdusrdb\us_shbom.l
!Cmdty Code ====================================Description========================================

CHAIN_1003 'Chainwheel operator each with [422] of total chain length for [426] NPD valve with commodity code [400]'
CHAIN_1005 'Chainwheel operator each with [422] of total chain length for [426] NPD valve with commodity code [400]'
DAABAXAABE 'Monitor, CL150 FFFE, station type, 4" CL150 in-let by 2.5" NHT stainless steel outlet w/stainless steel stem
lock knobs with 0.75" coupling in base, w/shapertip nozzle, Stang BB0309-21'
DBAAAXBAAB 'Fire hydrant, CL125 FFFE, 5" size, counterclockwise open, 4.5" steamer nozzle, two 2.5" hose nozzles equipped
w/caps and chains, [428], American Darling B-50-B'
DCBGDXEADA 'Hose rack, 300#, FTE, w/valve, wall mount, rt hand w/100 ft hose & fog nozzle, Powhatan 30-333'
DDAXCJDAAA 'Spray sprinkler, MTE, filled cone w/rupture disc, 304, Grinnell, Mulsifyre Projector S-1'
FAAAAAWAAA 'Flange, CL150, FFFE/BE, ASTM-A105, ANSI-B16.5, WN, [409] |bore to match|'
FAAAAAWWAA 'Flange, CL150, FFFE/BE, ASTM-A105, ANSI-B16.5, WN, cement lined, [409] |bore to match|'
FAAABADIIF 'Flange, CL150, RFFE/BE, ASTM-A182-F316, ANSI-B16.5, WN, S-80S bore'
FAAADBDFFC 'Flange, CL150, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-XXS bore'
GEAAAZZADF 'Paddle spacer, CL150, FFTBE, ASTM-A516-70, Aitken Z1, [429]'
PAAAAACIIA 'Pipe, S-104, BE, '
PAAAAAJAAA 'Pipe, S-60, BE, ASTM-A53-B Type S'
PAAAAAWWXM 'Pipe, [401], BE, ASTM-A53-B Type S, cement lined, treated & wrapped'
PAAAABBAAE 'Pipe, S-STD, BE, ASTM-A106-B'
PADAABDGFD 'Pipe, S-XXS, PE, ASME-SA335-P11'
PAFAAAWAAA 'Pipe bend, [403], BE, 6 NPD rad, ASTM-A53-B Type S'
POAAAADIIA 'Nipple, BE, S-80S, 3" long, ASTM-A312-TP304 smls'
PRPAXZZAAA 'Reinforcing pad, [425], ASTM-A53-B '
PUBZZAWVAA 'Pipe, [401], SPE/BLE, push-on jt, 10 ft lay lngth, ASTM-A74 w/rubber gskt'
QAEZZAKTAB 'Reducing coupling, S-80, SE, ASTM-D2467'
SAAQZZZAAA 'Coupling, CL3000, SWE, ASTM-A105, ANSI-B16.11'
SCAQZZZAAA 'Cap, CL3000, SWE, ASTM-A105'
SHAQZZZABB 'Union, CL3000, SWE, ASTM-A350-LF2, MSS-SP-83'
SLAQZZZAAA '90 deg elbow, CL3000, SWE, ASTM-A105, ANSI-B16.11'
SLAQZZZABB '90 deg elbow, CL3000, SWE, ASTM-A350-LF2, ANSI-B16.11'
SLCQZZZAAA '45 deg elbow, CL3000, SWE, ASTM-A105, ANSI-B16.11'
SLCQZZZABB '45 deg elbow, CL3000, SWE, ASTM-A350-LF2, ANSI-B16.11'
STAQZZZAAA 'Tee, CL3000, SWE, ASTM-A105, ANSI-B16.11'
STBQZZZAAA 'Reducing branch tee, CL3000, SWE, ASTM-A105, ANSI-B16.11'
STLQZZZAAA 'Lateral, CL3000, SWE, ASTM-A105, ANSI-B16.11'
STMQZZZABB 'Reducing branch lateral, CL3000, SWE, ASTM-A350-LF2, ANSI-B16.11'
TPAZVZZAAA 'Plug, MTE, ASTM-A105, ANSI-B16.11'
UAAEGZZVBB '1/4 bend, CL250, PE/MJBE, AWWA-C110, dbl thk cement lined w/gskt, glnd & blt'
URAEKZZVBB 'Concentric reducer, CL250, PLE/MJBSE, AWWA-C110, dbl thk cement lined w/gskt, glnd & blt'
VAAAUXJAAA 'Gate valve, CL150, FFFE, BB, OS&Y, ASTM-A395, brnz trim, Stockham D-623'
VAAAUXJAGR 'Gate valve, CL150, FFFE, BB, OS&Y, ASTM-A395, brnz trim, GO w/side handwheel, Stockham D-623'
VAABAHCCAA 'Gate valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8, Crane 47'
VBABALCFAA 'Globe valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 12, Crane 143'
VBABALCFRE 'Globe valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, NACE, trim 12, Crane 143'
VCAAUXJCAA 'Check valve, CL150, FFFE, BC, swing, ASTM-A395, brnz trim, Stockham D-931'
VDABAUIBAA 'Ball valve, CL150, RFFE, red. port, end entry, firesafe, ASTM-A216-WCB, plated CS ball, CS trim, Jamesbury
5150'
VEADAZEBAA 'Plug valve, CL150, RFFE, lubricated, ASTM-A216-WCB, 125 Ra finish, Rockwell 1945'
VEADAZECGR 'Plug valve, CL150, RFFE, lubricated, ASTM-A216-WCB, 125 Ra finish, GO w/side handwheel, Rockwell 4149'
VFLAUQRJGR 'Butterfly valve, CL125, FFFE, ASTM-A395, trim 316, EPT seat, GO w/side handwheel, Centerline Series 504'
VYFSAHEEAA 'Y globe valve, CL1500, SWE, WB, OS&Y, ASTM-A105, trim 8, Rockwell/Edward 36124'
WAAAAAWAAA '90 deg LR elbow, [403], BE, ASTM-A234-WPB, ANSI-B16.9'
WADAAAWABL 'Stub end, RFLFE/BE, ASTM-A403-WP304, ANSI-B16.9, [409] |bore to match|'
WCAAAAWAAA 'Cap, [403], BE, ASTM-A234-WPB, ANSI-B16.9'
WOAAAAWIFB 'Weldolet, [412], BE, |weldolet, |ASTM-A182-F304L'
WOBSABQAFA 'Sockolet, CL3000, BE/SWE, |sockolet, |ASTM-A105'
WOCTABQAFB 'Thredolet, CL3000, BE/FTE, |thredolet, |ASTM-A350-LF2'
WODAAAWAFA 'Elbolet, [412], BE, |elbolet, |ASTM-A105'
WOIAAAWAFA 'Latrolet, [412], BE, |latrolet, |ASTM-A105'
WOUSABQAFA 'Flatolet, CL3000, BE/SWE, |flatolet, |ASTM-A105'
WRAAAAWAAA 'Concentric reducer, [414], BE, ASTM-A234-WPB, ANSI-B16.9'
WRBAAAWAAA 'Eccentric reducer, [414], BE, ASTM-A234-WPB, ANSI-B16.9'
WTAAAAWFAL 'Tee, [403], BE, ASTM-A234-WP9, ANSI-B16.9'
WTBAAAWAAA 'Reducing branch tee, [416], BE, ASTM-A234-WPB, ANSI-B16.9'
WZBZZZZAZA 'Reinforcing weld, [423], carbon steel '
XAAAAZZICC 'Gasket, CL150, G52, 0.0625" thk comp sheet, org fiber/nitrile binder, full face, ANSI-B16.21'
XDAABZZQSG 'Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph filled, CS center ring, API-601'
YAJBPFCFFW 'Cap screws, ASTM-A193-B7,$0.625" diam x 1.5" lg'
YBJIPFKFFW 'Cap screws, ASTM-A193-B7,$1" diam x 3.5" lg'
YZZZHZZFFB 'B44, ASTM-A193-B8C Cl.1 studs w/ASTM-A194-8C hvy hex nuts'
YZZZMZZAAA 'B71, ASTM-A307-B machine bolts w/ASTM-A563-A hvy hex nuts'
The Material Description Library Manager enables you to create, revise, and delete data in
the Material Description Libraries. You can use the Piping Job Specification Manager to load
the material data tables in the Specification/Material Database.
Refer to Creating Material Takeoffs and Other Reports, page 231 for more information on
material descriptions.

Reference Data
Standard Note Library

The text for code-listed attributes and standard notes is stored in the Standard Note Library. All
attributes identified as code-listed are actually stored as integer values. The code list text
associated with the integer is stored in the Standard Note Library. Information in the Standard
Note Library is identified by note number and note type. Output from the library consists of
free-format text which forms the standard note.
Label Description Library

The Label Description Library contains the definitions for the following label types used in PDS
3D:
 Drawing view specific labels
 Drawing view identification labels
 Drawing block labels
 Alphanumeric labels
 Displayable attribute messages
 Material description attribute messages
 Isometric drawing labels.
These labels are intelligent graphics with links to the material database.
The Label Description Library Manager enables you to define the graphic parameters for a
label (such as level, line weight, and color code) and to define the format of the label (what
information comprises the label.)

Reference Data
Piping Assembly Library

The Piping Assembly Library (PAL) contains the piping assembly definitions which define the
parameters necessary to place a piping assembly (group of components) automatically in the
model.
A Piping Assembly object library and text library which contain the definitions for basic
assemblies are included in the product delivery.
# Drain assembly
PAL 'DRAIN'
!
! This assembly will place a drain. The user needs to place a 1"
! sockolet at the point the drain is desired.
!
PLACE FITTING, 6Q3C88 , BY CP1
!
! The data from the component spec is read into the keywords.
! TERM_TYPE_1 TO 5 gets the numeric value for end preparation (eg. 21)
! PR_RATING_1 TO 5 gets the pressure rating
! GEN_TYPE_1 TO 5 gets the textual value for end preparation (eg. MALE)
!
LOAD_SPEC_DATA = '6Q1C76'
!
! This 'IF' statement determines if an optional flange is needed before
! the gate valve is placed.
!
IF ( GEN_TYPE_1 .EQ. BOLTED ) THEN
OPTION_RATING = PR_RATING_1
OPTION_END_PREP = TERM_TYPE_1
PLACE OPTIONAL , 6Q2C01 , BY CP2
ENDIF
!
! Places a gate valve. Notice in the spec that this type of gate valve
! is different than a 6Q2C01.
!
PLACE VALVE, 6Q1C76 , BY CP1
IF ( GEN_TYPE_2 .EQ. BOLTED ) THEN
OPTION_RATING = PR_RATING_2
OPTION_END_PREP = TERM_TYPE_2
PLACE OPTIONAL , 6Q2C01 , BY CP1
ENDIF
!
! This command allows the user to pick which component to place. If the
! option command is not used the s/w will choose option 1. In this instance,
! without the OPTION_CODE command will cause an error because there are no
! option 1 attributes available for 6Q2C16. Another possiblilty would be to
! use OPTION_CODE = PROMPT. The user will be prompted for which component is
! desired.
!
OPTION_CODE = 163
PLACE FITTING, 6Q2C16 , BY CP1
END
The resulting graphics created by the PAL file look like this:

SECTION 4
How PDS Works
This section provides an overview of how the various parts of PDS are used to place
components in a model. It also outlines how the information in the model and the accompanying
engineering data in the Databases are used for material control.
All of the examples used in this chapter use the delivered reference data. This chapter is
intended to illustrate how PDS uses the reference data rather than point out various
customizable features. Detailed customization information is provided in the Spec Writing for
PDS 3D Course Guide and in the Reference Data Manager (PD_Data) Reference Guide.
What Happens When I Place a Component?

This is a good starting point for a discussion of the various parts that make up PDS and how
these parts work together. The figure on the following page illustrates what happens when you
place a Gate Valve in a piping model.
PDS makes extensive use of reference data to control the design process. Because PDS uses
reference data to control placement operations, it is said to be specification-driven.
When you select a component for placement in the model, the system
 uses the active parameters (such as piping materials class and nominal diameter) to search
for the selected item name in the Specification Material Reference Database. If the selected
item is found in the RDB, the system reads the specification data for the parameters
required to place the component. Included in this information is the model code (or specialty
item number) for the selected component and the names of the spec tables defined for the
Piping Materials Class.
 uses the model code (or specialty item number), derived from the RDB, to access the
Graphic Commodity Library. The definitions in the Graphic Commodity Library determine the
physical tables required to place the component and call the tables in the Physical
Dimension Library.
 places the symbol graphics in the model design file and writes the nongraphic information
for the component in the database.

How PDS Works
Example of Piping Software

The Piping Designer provides a graphics environment for the creation and modification of piping
and instrumentation. The graphics environment will be discussed in more detail in Chapter 5.

How PDS Works
Place Component Command

The Place Component command activates a form used to control the placement operation.
Spec Access
The system uses the active parameters to access information in the Specification/Material
Reference Database. The active segment parameters define the data that will be used to place
the component.
Piping Materials Class Data

The Piping Materials Class setting defines a number of basic parameters. In this example the
Piping Materials Class is set to 1C0031.

How PDS Works
Piping Materials Class Code

The delivered reference data uses a 6 character code for the PMC based on the following
convention.
F - Pressure Rating
A - Material Group
XXXX - Sequence Number from Code List Set 148
Following this convention, 1C003 1 is interpreted as
1 -CL150
C - Carbon Steels
0031 - CL150 RFFE, CS, Trim 8
Therefore, PMC 1C003-1 equals 150# Carbon Steel, Standard Raised Face, with trim 8.
Refer to the listing of Code List Set 148 in the PDS Piping Component Data Reference Guide for
information on all the codes.
An alternate naming scheme is also described under Code List Set 148. This alternate
scheme uses the convention:
A - Materials Group
B - Materials Type
C - Detail Features
D - Corrosion Allowance
E - Service
F - Pressure Rating
Following this convention, CAC5C1 is interpreted as
C - Carbon Steels
A -CS
C - Std RF. std trim
5 - 0.063"
C - Process. hot (-20 to 800° F)
1 -CL150
You can use either of these conventions or use any standard character code up to 16
characters.

How PDS Works
Temperature Pressure Table

This attribute identifies the table used to determine maximum pressure as a function of
temperature. This table includes the pressure and temperature sets that form the boundary for
which the commodity items included in this piping materials class are suitable.
Table _Data _Definition 'L1001'

! Description = B16.5 CL150-1.1, -20 to 800
! By=DCG Ckd By=DG Rev=0 Date=13-Feb-1987
No_Inputs 1 No_Outputs 1
Input_Interpolation 1, Next_One
Units= DF, PSIG
! Temperature Pressure
-20 285
100 285
200 260
300 230
400 200
500 170
600 140
650 125
700 110
750 95
800 80
END
Diameter Table
This attribute identifies the table used to determine the nominal piping diameter (NPD) values for
piping and tubing which are valid for this piping materials class. The following table will allow the
placement of 1/2" to 36"piping:
Table_Data_Definition 'D036'
! Description= From 0.5 to 36
! By=NP Ckd By=DG Rev=0 Date=22-Jan-1987
Units= NPD_IN
! Diam
0.5
0.75
1
1.5
2
3
4

How PDS Works
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
END
Thickness Table
This attribute defines a table to be used for optional wall thickness and branch reinforcement
calculations. When the table is used, thickness data is determined as a function of nominal
piping diameter. The thickness table includes the minimum, retirement, thread, and preferred
thicknesses required in the calculation of piping wall thickness. It provides the actual thickness;
not a schedule. Therefore, there must be an individual entry for each diameter.

How PDS Works
Materials Table
This parameter defines a materials data table used to determine the material properties for
optional wall thickness calculations. The units of measure used in this table must be consistent
with those used in the corresponding Temperature-Pressure Table.
Table_Data_Definition 'ML01'
! Description= Materials per ANSI-B31.3b-1988
! By=EPZ Ckd By=RSM Rev=3 Date=03-Oct-1989
Input_Interpolation 2, Next_One
Units= INT, DF, IN, IN, DEC, PSI, DEC, IN
! Mill Tolrnce
! Mat Gr Temp Thick Range Y S % Value
116 -20 - - .4 20000 12.5 -
116 100 - - .4 20000 12.5 -
116 200 - - .4 20000 12.5 -
116 300 - - .4 20000 12.5 -
116 400 - - .4 20000 12.5 -
116 500 - - .4 18900 12.5 -
116 600 - - .4 17300 12.5 -
116 650 - - .4 17000 12.5 -
116 700 - - .4 16500 12.5 -
116 750 - - .4 13000 12.5 -
116 800 - - .4 10800 12.5 -
142 -20 - - .4 20000 12.5 -
142 100 - - .4 20000 12.5 -
142 200 - - .4 20000 12.5 -
142 300 - - .4 20000 12.5 -
142 400 - - .4 20000 12.5 -
142 500 - - .4 18900 12.5 -
142 600 - - .4 17300 12.5 -
142 650 - - .4 17000 12.5 -
142 700 - - .4 16500 12.5 -
142 750 - - .4 13000 12.5 -
142 800 - - .4 10800 12.5 -
162 -20 - - .4 20000 12.5 -
162 100 - - .4 20000 12.5 -
162 200 - - .4 20000 12.5 -
162 300 - - .4 20000 12.5 -
162 400 - - .4 20000 12.5 -
162 500 - - .4 18900 12.5 -
162 600 - - .4 17300 12.5 -
162 650 - - .4 17000 12.5 -
162 700 - - .4 16500 12.5 -
162 750 - - .4 13000 12.5 -
162 800 - - .4 10800 12.5 -

How PDS Works
Thickness Equations
Thickness equations define formulas for the optional calculation of piping wall thickness and
branch reinforcement to resist positive pressure. The actual equations and their logic are
hardcoded in the software.
EL01
Source - ANSI-B 31 .3c. 1986 [Chemical Plant and Petroleum Refinery Piping] Thickness logic
from paragraph 304.1, equation 3a.
Reinforcement logic from paragraph 304.3.3 & Code - Appendix H.
where
P = Design pressure
D = Pipe outside diameter
S = Allowable stress read from the Materials table
E = Joint quality factor determined from the wall thickness attribute Cxxx where xxx is 100
times E
Y = Coefficient Y read from the Materials table
A = Additional Thickness (in inches or mm)
Gasket Gap / Table

This attribute defines either a single gasket gap value or a table used to determine the gasket
gap based on nominal diameter and maximum temperature. If a table is specified, the system
uses the NPD of each bolted end and the maximum temperature for the gasket at that end to
determine the gap thickness.
In this example, the actual gap value (.125) is used rather than a table name.

How PDS Works
Piping Commodity Data

The following shows the delivered commodity item data as defined in 1c0031.pcd.
The active segment parameters define the data that will be used to place the component.
Continuing with our example, we will use the information for a 6 inch gate valve.
Item Name and Model Code

When you select the Gate option from the Place Component form, the system sets the Item
Name to 6Q1C01. This is the item name for a gate valve in the delivered reference data. The
corresponding Model Code for this Item Name is GAT.
The item name is also called the AABBCC code because it is composed of a number of
parameters. For example, the code 6Q1C01 breaks down as follows:
AA 6Q Piping In-Line Component
BB 1C Valves
CC 01 Gate Valve

How PDS Works
Option Code
The option code is a code-listed value that tells the system to retrieve the primary commodity
item, a secondary commodity item, or another special option from the Piping Commodity Data.
This parameter allows you to select from predefined options at placement. If no option is
specified, the system defaults to option 1 (primary commodity item). Option 2 is reserved as the
secondary commodity item. The other options are determined by values for Code List Set 400.
Green and Red Connect Point Data

Since a standard gate valve has the same properties at both ends (connect points) only green
connect point data is required.
! AABBCC Green CP
! Code Opt From To Prp Rating Sc/Th TS
6Q1C01 1 3 12 21 CL150 NREQD 5
The From To values define the range of NPD values supported by this definition in this example
3" to 12".
The End Preparation (Prp) is a code-listed attribute that identifies the end preparation for the
connect point. The system determines the termination type based on the range of values
2 - 199 bolted terminations
300 - 399 male terminations
400 - 599 female terminations
Using the values defined in Code List Set 330, the setting 21 indicates RFFE (Raised-Face
Flanged End).
The Rating identifies the pressure rating for the connect point. The setting CL 150 refers to
ANSI pressure rating CL 150. The system interprets the first set of sequential numeric
characters as the pressure rating value (150 in this example).
The Schedule Thickness (Sc/Th) exists as alphanumeric data. The value NREQD is used in
cases where all of the following conditions apply:
 The thickness value is not required in purchasing the component.
 Empty weights are not significantly affected by actual thickness values.
 Either stress analysis is not applicable or, if applicable, the component is to be considered
infinitely rigid in stress analysis calculations.
The Table Suffix (TS) is a code-listed attribute (CL576) used to further reference the source of
the generic dimensional data, such as flange data or piping outside diameter data.
For AMS standards, it represents the table suffix for the green connect point. The value 5 is the
default for US practice. It represents the basis on which most US-practice generic piping tables
for dimensional parameters is defined.
End Termination Type Basis for Table Values
Raised-face flanged......ANSI-B16.1, B16.5, API-605 or MSS-SP-42,
in this order of precedence

How PDS Works
Commodity Code
The commodity code is a user-assigned code that together with the NPD and
schedule/thickness uniquely defines the component. It defines the customer's commodity code
(or part number). This attribute is the index into the Material Description Library.
Using the delivered reference data, the commodity code VAABAHCCAA represents
V - Valve
A - Gate Valve
A -CL150
B - Raised Face Flanged Ends
A - Carbon Steel
H - Trim 8 CC - Crane 47
AA - Blank
For valves, the commodity code also defines the name of the dry weight table (required for
stress analysis). Refer to Appendix E in the PDS Piping Component Data Reference Guide for a
listing of the delivered commodity codes.
Geometric Industry Standard

This code-listed attribute (CL575) identifies the source of the data (which is usually an industry
standard, such as ANSI, ISO, or DIN, or a company standard) from which the specific geometry
of the commodity item can be deduced. This parameter represents the vendor or industry
standard, and the material if either affects the dimensions of the commodity item.
Code list numbers 2-6999 are reserved for geometry standards that apply to US piping
practices. The value 40 indicates the following:
40 = ANSI-B16.10 [Dimensions of Ferrous Valves ||]
Modifier
This attribute has various uses depending on the type of commodity item. For a valve, it
represents the code list number from CL550 (operator/actuator type) which defines the symbol
description and the source of the physical data. If this value is a negative number (such as -3)
the operator is not displayed when placing the component.
Reviewing CL550, the value 3 indicates a handwheel operator.

How PDS Works
Materials Grade
This code-listed attribute (CL145) identifies the material code, specification, grade-temper, and
joint efficiency for the component. This data is used in wall thickness calculations. It can also be
used to access physical data in the Graphic Commodity Library.
Reviewing CL145, the value 252 indicates the following:
A216-WCB.
Weight code
This code-listed attribute (CL578) defines the weight code for the component. It determines the
table to be used in finding the dry weight of the component. It is required for those cases where
material causes the dry weight data but not the dimensional data to differ for a specific
geometric industry standard.
Reviewing CL578, the value 52 indicates the following:
52 = 490 pcf [Carbon steel, low Cr alloy steel, stainless steel]
Fabrication Category
This code-listed attribute (CL180) identifies the shop/field fabrication and purchase status of a
component. It defines how the component was supplied and how the component was fabricated.
The value 7 indicates the following:
Contractor supplied, field fabricated (CSFF).

How PDS Works
Table Access
If all the required information is found in the Specification/Material Reference Database, the
system performs table access to determine the geometry and dimensions of the component.
Using the Review Component Placement option of the Diagnostics command, you can
review the table access operations used to place the component.
The Place Component Error Data form displays the physical data libraries and Eden modules
that were accessed to place the component. The initial display lists the Eden modules that were
accessed. Indented lines indicate a module which was called from another module. The system
places an asterisk (*) beside the module name where Eden stopped executing.
The system uses the model code (or specialty item number) to access the graphic commodity
library. The definitions in the graphic commodity library determine the physical tables required to
place the component and call the tables in the physical commodity library.
The Graphic Commodity Library (GCL) provides data for commodity items, engineered items,
and instruments. It is basically a catalog of component data which is accessed to do the
following:
 Determine physical data based on user specifications (such as NPD and end preparation).
 Assign connect point data from the Specification Material Reference Database.
 Define the parametric shape for the model graphics.
PDS Piping uses the Eden Parametric Language to define and place components, specialty
items, operators, and envelopes. Eden is a high- level programming language which uses
information from the Material Reference Database and model to access parametric and
dimensional data.
Eden is composed of the following three major types of modules:
 Symbol Processors

How PDS Works
 Physical Data Subroutines

 Parametric Shape Definitions
These modules are designed to carry out two functions: data definition and graphic presentation.
The modular approach provides for efficient storage of information in these libraries by enabling
common information to be shared by different symbols.
Eden Module Relationships

How PDS Works
Symbol Processors
A symbol processor is the controlling function or logic used to produce the graphics for a
commodity item, piping specialty, instrument, pipe support, or interference envelope. During
component placement, the symbol processor
 accesses the active component design parameters
 assigns connect points
 Calls the required physical data modules
 determines and calls the required parametric shape modules.
The system retrieves the active component parameters which are dependent upon a connect
point from the RDB in terms of green, red, or tap connect point properties. The symbol definition
assigns the data corresponding to these connect point types (green, red, or tap) to the physical
connect point numbers (CP1, CP2, CP3, CP4 or CP5).
The first line of the Eden module defines the type of module and the module name. The
following statement is used in the Eden modules to indicate a symbol processor module:
Symbol _Processor 'module name'
The module name is determined by the type of component being placed (commodity item or
specialty item). For a commodity item, the system searches for the Model Code of the
commodity item as the module name. If the Model Code is blank in the Piping Commodity
Specification Data, the system searches for the Item Name as the module name.
The following lists the symbol processor GAT which is used to control the placement of a gate
valve.
! REGULAR PATTERN, BOLTED OR MALE ENDS GATE VALVE
Symbol_Processor ’GAT’
Call Assign_Connect_Point ( GREEN, CP1 )
Call Assign_Connect_Point ( RED, CP2 )
physical_data_source = ’V1’ // Standard_Type
Call Get_Physical_Data ( physical_data_source )
parametric_shape = ’V1’
Call Draw_Parametric_Shape ( parametric_shape )
Valve_Operator = DABS ( Valve_Operator )
If ( Valve_Operator .NE. 0 ) Then
If ( Valve_Operator .LT. 1000 ) Then
Subcomponent = ’OP’ // Valve_Operator
Else
Subcomponent = ’A’ // Valve_Operator
EndIf
Operator_Orient = FALSE
EndIf
Stop
End

How PDS Works
Sub-Symbol Processor
A subcomponent call in a symbol processor module indicates a sub-symbol processor.
Subcomponents are additions to symbols such as an operator on a valve.
The first line of a sub-symbol processor module indicates the module type and the module
name.
Sub _Symbol _Processor 'module name'
The sub-symbol processor name for operators is a concatenation of the characters OP_ and the
modifier value from the Piping Commodity Specification Data in the RDB. The value is
expressed as a code list number from CL550 (operator/actuator type). If the value is a
positive number (such as 3) the operator is placed with the valve. If the value is a negative
number (such as -3) the operator is not placed with the valve. (This is useful in segregating large
diameter valves which almost always have a valve operator from small diameter valves which
frequently do not have an operator.)
The symbol processor for the gate valve calls a sub-symbol processor (Subcomponent = 'OP'
// Valve_Operator) which places an operator on the valve. The following depicts the
sub-symbol processor OP_3 which is used to control the placement of a hand wheel operator on
the valve.
! HANDWHEEL OPERATOR
Sub _Symbol _Processor 'OP_3'
If ( Operator_Orient .EQ. TRUE ) Then
prompt = 1.0
Call Prompt_to_Orient_Operator ( prompt )
EndIf
physical_data_source = 'OPERATOR_3'
parametric_shape = 'OP3'
Call Draw_Parametric_Shape ( parametric_shape )
Stop
End
Listing for Sub-Symbol Processor OP_3
Physical Data Definitions

The system uses the physical data definitions to determine the dimension data, weight data, and
surface area data using the active design parameters. Physical data modules are identified by
the statement
Physical_Data_Definition 'module name' as the first line in the Eden module.
The module name for a physical data module consists of a symbol type (such as V1, V2, and so
forth for valves) and a generic type of geometric industry standard (such as AMS or DIN). You
can define multiple physical data modules for the same symbol depending on the type of
standard being referenced (for example, V1_AMS for American standards and V 1_DIN for
European standards).
You can manage ten different sets of logic for table naming conventions for the following
industry practices. The corresponding table suffix ranges and the suffix for the Piping Eden
physical data modules are indicated below.

How PDS Works
Practice Range Suffix
U.S. Practice 1-99 AMS
European – DIN 100-199 DIN
European - British Standard 200-299 BRITISH_STD
European - Practice A 300-399 EURO_A
European - Practice B 400-499 EURO_B
International – JIS 500-599 JIS
International – Australian 600-699 AUS
International - Practice A 700-799 INT_A
International - Practice B 800-899 INT_B
Company Practice 900-999 COMPANY
The geometric industry standard for a component is defined in the Piping Commodity Data table
of the Material Reference Database. Each component must be assigned a geometric industry
standard if it is to use physical data tables.
For most of the delivered symbols, the physical data modules are classified into two categories:
specific and generic. The specific physical data module is called by the symbol processor. This
module then calls a generic physical data module.
Specific Physical Data Modules

The physical data module V1_AMS determines the specific dimensions (face-to-center and
face-to-face) and other physical properties for a gate valve. This is the module called by the
symbol processor GAT
Physical_Data_Definition 'V1_AMS'
physical_data_source = 'VALVE_2_AMS'
Call Read_Table ( Table_Name_A, input, output )
Surface_Area = Output_1
Wet _Weight = Output _2
F_to_C_Dim_1 = Output _3
If ( Term_Type_1 .EQ. Term_Type_2 ) Then F _to _C _Dim _2 =
F _to _C _Dim _1
Else
F_to_C_Dim_2 = Output _4
EndIf
F _to _F _Dim = F _to _C _Dim _1+ F _to _C _Dim _2
If ( Valve_Operator .LE. 24.0 ) Then
Call Read_Table ( Table _Name _W, input, output )
Dry _Weight = Output_1

How PDS Works
EndIf
Return
End
Generic Physical Data Modules

The generic modules contain information which is common to more than one symbol such as
flange thickness, gasket separation, and outside diameter. The physical data module V1_AMS
calls another physical data module VALVE_2_AMS which contains the generic dimension data
for all valves with two connect points. The following is the Listing for Physical Data Module
VALVE_2_AMS:
Physical_Data_Definition ’VALVE_2_AMS’
Input_1 = Nom_Pipe_D_1
If ( Gen_Type_1 .EQ. BOLTED ) Then
table_name = ’BLT’ // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_1
Thickness_1 = Output_2
Seat_Depth_1 = Output_3
Thickness_1 = Thickness_1 - Seat_Depth_1
CP_Offset_1 = Gasket_Sep_1
If ( Symbology .EQ. MODEL ) Then
Thickness_1 = 0.0
Depth_1 = 0.0
Pipe_OD_1 = 0.0
Body_OD_1 = Facing_OD_1
Else
table_name = ’MAL_300_5’
Depth_1 = Thickness_1
Pipe_OD_1 = Output_2
Body_OD_1 = Pipe_OD_1
EndIf
Else
If ( Gen_Type_1 .EQ. MALE ) Then
table_name = ’MAL’ // Term_Type_1 // Gen_Flag_Green
Thickness_1 = 0.0
Depth_1 = 0.0
Seat_Depth_1 = 0.0
CP_Offset_1 = 0.0
Pipe_OD_1 = Facing_OD_1
Else
table_name = ’FEM’ // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green
Depth_1 = Output_2
Seat_Depth_1 = 0.0
Thickness_1 = 0.0
If ( symbology .EQ. MODEL ) Then
Depth_1 = 0.0
CP_Offset_1 = 0.0
Pipe_OD_1 = 0.0
Else
CP_Offset_1 = -Depth_1
EndIf
EndIf
EndIf
If ( Term_Type_2 .EQ. Term_Type_1 .AND. Nom_Pipe_D_1 .EQ. Nom_Pipe_D_2 )
Then
Facing_OD_2 = Facing_OD_1
Pipe_OD_2 = Pipe_OD_1
Body_OD_2 = Body_OD_1
Thickness_2 = Thickness_1
Depth_2 = Depth_1
Seat_depth_2 = Seat_Depth_1
CP_Offset_2 = CP_Offset_1
Else
If ( Gen_Type_2 .EQ. BOLTED ) Then
table_name = ’BLT’ // Term_Type_2 // Pr_Rating_2 // Gen_Flag_Red

How PDS Works
Thickness_2 = Output_2
Seat_Depth_2 = Output_3
Thickness_2 = Thickness_2 - Seat_Depth_2
CP_Offset_2 = Gasket_Sep_2
Thickness_2 = 0.0
Depth_2 = 0.0
Pipe_OD_2 = 0.0
Else
Depth_2 = Thickness_2
EndIf
Else
table_name = ’MAL’ // Term_Type_2 // Gen_Flag_Red
Thickness_2 = 0.0
Depth_2 = 0.0
Seat_Depth_2 = 0.0
CP_Offset_2 = 0.0
Pipe_OD_2 = Facing_OD_2
Else
table_name = ’FEM’ // Term_Type_2 // Pr_Rating_2 // Gen_Flag_Red
Depth_2 = Output_2
Seat_Depth_2 = 0.0
Thickness_2 = 0.0
Depth_2 = 0.0
CP_Offset_2 = 0.0
Pipe_OD_2 = 0.0
Else
CP_Offset_2 = -Depth_2
EndIf
EndIf
EndIf
EndIf
Table_Name_A = Item_Name // Geo_Ind_Std // Term_Type_1
Table_Name_W = Commodity_Code
If ( Term_Type_1 .EQ. Term_Type_2 .AND. Nom_Pipe_D_1 .EQ. Nom_Pipe_D_2 )
Then
Table_Name_A = Table_Name_A // Pr_Rating_1 // ’A’
Else
If ( Gen_Type_1 .EQ. Gen_Type_2 ) Then
! Male X Male or Bolted X Bolted
! or Female X Female
Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 //
Pr_Rating_2 // ’A’
Else
! Male X Bolted and Male X Female
Table_Name_A = Table_Name_A // Term_Type_2 // Pr_Rating_2 // ’A’
Else
! Bolted X Male and Female X Male
Else
! Bolted X Female and Female X
Bolted
Pr_Rating_2 // ’A’
EndIf
EndIf
EndIf
EndIf
Return
End

How PDS Works
Parametric Shape Definitions

The parametric shape definition describes the graphics symbol (such as bend, flange, or valve
body) which is placed for the component in the model.
Parametric shape definitions are used to place symbol graphics in the model or define
interference envelopes. This involves the following major functions
 defining connect point geometry
 placing connect points
 moving the active location a specified distance
 drawing a specific graphic shape
 placing a center of gravity location.
Parametric shape definitions are divided into three basic types: model parametric shapes,
detailed parametric shapes, and interference envelopes. The first line of the Eden module
indicates the module type and the module name.
Model Parametric Shape Definitions

Model parametric shapes define the symbol graphics to be placed in the model. For example,
the parametric shape module for a valve consists of a cylinder, two cones, and a cylinder
(flange, valve body, flange).
The first line for these modules is of the form
Model_Parametric_Shape_Definition 'module name'
The module name for a parametric shape module consists of a symbol type (such as V1, V2,
and so forth, for valves).
The parametric shape module V1 determines the model graphics for a valve. This is the module
called by the symbol processor GAT. The parametric shape module OP3 determines the model
graphics for a hand wheel operator. This is the module called by the sub-symbol processor
OP_3.
Model _Parametric _Shape _Def inition 'V1'
Call Define_Connect_Point_Geometry ( LINEAR )
Call Place_Connect_Point ( CP1 )
Call Move_By_Distance ( CP_Offset_1 )
Call Draw_Cylinder_With_Capped_Ends ( Depth_1, Facing_OD_1 )
length = F_to_C_Dim_1 - Thickness_1
diameter = 0.0
Call Draw_Cone ( length, Body_OD_1, diameter )
Call Place_COG_Location ( DRY_COG )
Call Place_COG_Location ( WET_COG )

How PDS Works
Return
End
Model _Parametric _Shape _Def inition 'OP3'

Call Define_Connect_Point_Geometry ( OPERATOR ) Call
Convert_NPD_to_Subunits ( Nom_Pipe_D_1, dia )
dist = dia + Min_Cyl_Dia * 0.5
angle = 90.0
radius = ( Dimension_2 - Min_Cyl_Dia ) * 0.5
Call Draw_Cylinder_With_Capped_Ends ( Dimension _1, Min_Cyl_Dia )
Call Move_by_Distance ( -dist )
Call Rotate_Orientation ( angle, Secondary )
Call Rotate_Orientation ( angle, Normal )
Call Move_Along_Axis ( -radius, Secondary )
Call Draw_Torus ( radius, angle, Min_Cyl_Dia )
Return
End

How PDS Works
Physical Data
Selecting the Component Data option of the Place Component Error Data form displays the
physical data used to place the component.
To place a 6" gate valve, the system references the following tables.

How PDS Works
Generic Tables
The spec access for a six-inch gate valve defines the end preparation at both connect points as
Raised Face Flanged End (code list value 21) which is a bolted connection. As shown in the
listing for VALVE_2_AMS, the table name for a bolted connection on a two-connect point valve
is
table_name= 'BLT' // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green
Using the values from the Piping Job Specification (PMC=1C003 1, Item Name=6Q1C01), the
actual table name will be
BLT _20 _150 _5
This table returns the outside diameter, flange thickness, and the seating depth for each end of
the valve. Note that the termination type (20) is used rather than the actual end preparation
value (21).
You can use the Display Table option to display the contents of a table.
Specific Tables
The specific tables are used to define the main body of the valve. Since the termination type is
the same at both ends of the valve (bolted), no red connect point data is required. The required
tables are found by referring to the Bolted(G) termination type.
 MC_GS_Term(G)_Rat(G)_A (P15A)
 MC_GS_Term(G)_Rat(G)_B (P15B) - This table is only required if more than eight outputs
are necessary to define a commodity item.
 Commodity Code (P59)
Using this information, the dimension tables for a 6" gate valve are:

How PDS Works
 GAT_40_20_150_A
This table returns the face-to-center dimension for the valve. Table P15B is not required for
a gate valve.
 VAABAHCCAA
This table returns the empty weight of the valve, including the weight of the operator.
If the end preparations were different at each end of the valve (such as female threaded by
socket welded) then a different set of tables would be required.
An additional table look-up is required to access the dimensional data for the valve operator.
The following table is required to define the valve operator.
MC_Type(G)_Rat(G)_Op_A (P3 1A)
Using this table name format, the dimension table for a hand wheel operator on a 6" gate valve
is:
GAT_BLT_150_3_A
This table returns the stem length and the wheel diameter for the handwheel operator.
Placing Components On Existing Segments

Piping segments are used to define the basic geometry of a pipeline and to carry common
attributes such as material class and NPD. All components placed in a piping model have an
underlying segment.
Segment data is stored in table 12 of the Design Database.
Data specific to a component is stored in table 34 of the Design Database.
When you place components on an existing piping segment (with Place Component or
Automated Placement), the system determines what type of component should be placed
based on the configuration and attributes of the segment(s) at the active placement point.
The Spec Table Library contains a set of tables which are used to determine the type of
component to place and basic information about the components. Refer to the Reference Data
Manager Reference Guide for more information on these tables.

How PDS Works
Commodity Item Name Table

The Piping Designer reads the Commodity Item Name table when placing a component at the
vertex of an existing piping segment. This table lists the Item Names of the components to be
used at different segment configurations (such as reduction, branching, or direction changes). It
enables you to relate the component types hard-coded in the software with the applicable
commodity item codes (item names). As the system processes the segment for component
placement, it uses the derived item name from the table to reference the Piping Commodity
Specification Data table of the Material/Reference Database.
When placing change of direction components, this table is used in conjunction with the Bend
Deflection Table.

How PDS Works
Bend Deflection Table

The bend deflection table is used when placing components at the vertex of an existing piping
segment. The system uses the bend angle at the segment vertex to determine the type of
component to be placed.
This table defines which full size and reducing size component types will be placed for a
specified angle range. The angle is defined as the smallest angle that the continuation of one
pipe run makes with the other run. The component types are defined in the commodity item
name table.
Branch Insertion Tables

Each Piping Materials Class references a set of branch tables: one for 90-degree branches, one
for 45- degree branches, and one for 45-to90 degree branches.
Branch tables define the reinforcement to be used at tee and lateral branches as a function of
the acute angle of intersection and the nominal diameters (first and second size) for the
intersecting lines.
The system accesses the branch table when placing a component at an intersection when no
branch component exists at that location.

How PDS Works
The system uses the information in the table and the first and second size to provide the item
name of the component to be used at the intersection. Typically, the codes are from one of the
following types:
 Reinforcing elements, such as reinforcing welds and pads.

 Weld-on components reinforcing the intersection such as saddles and weldolets.
 Weld-in components actually making the intersection such as laterals and tees.
During branch component placement, the comparison test of header segment data will include
nominal piping diameter, override schedule/thickness and construction status.
Placement Examples
This section outlines the placement data for a bend, reducer, and tee placed on an existing
segment.

How PDS Works
90 Degree Bend
Reducer (6"x4")

How PDS Works
Branch (4"x4")

SECTION 5
Creating 3D Models
This chapter describes the basics of 3D modeling using the Equipment Modeling and Piping
Designer Tasks.

Creating 3D Models
Modeling Setup Requirements

The following operations must be completed before any modeling activities can take place.
Project Setup
A project and all of its accompanying files must be defined with the Project Administrator
before you can use the Piping Designer or Equipment Modeling. Refer to the PDS Project
Setup Technical Reference for information on
 Loading PDS 3D products.
 Editing the control script to identify the location of the project data.
 Setting up a project and creating the associated database schemas.
Reference Data Setup

Refer to the Reference Data Manager Reference Guide for information on defining the reference
data for a project. This data must be defined before you can work in a model. Also refer to the
Project Data Manager in the Project Administrator Reference Guide for information on selecting
whether to use the approved or unapproved version of the reference data for a model file.
Seed Files
When you create a project, the system copies a set of seed files from the PD_Shell directory to
the project directory: drwsdz.dgn, eqpsdz.dgn, and mdlsdz.dgn. You can use the Project Data
Manager to modify the setting in these seed files. This data is often referred to as Type 63 data
because it is stored in the Type 63 elements of the design files.

Creating 3D Models
This seed data is discussed throughout the remainder of this chapter. Before creating models,
you should define the seed data to reflect your company practices so that all models will be
created with the same settings.
See chapter 6 of the Project Administrator (PD_Project) Reference Guide for detailed
information on the Project Data Manager.
Model Files
The Project Environment Manager is used to create, revise, or delete model files. Refer to the
Project Administrator Reference Guide for information on creating a piping model and database
files.
You can attach reference models defined in the other PDS 3D disciplines while working in a
piping model. Refer to the following documents for information on creating and manipulating
models for the PDS 3D disciplines.
 PDS Piping Design Graphics Reference Guide
 PDS Equipment Modeling Reference Guide
 Frame Works Plus Reference Guide
 PE HVAC Modeling Reference Guide
 EE Raceway Modeling Reference Guide

Creating 3D Models
Level Control and Graphical Symbology

The use of reference files provides for 63 display levels in the active design file plus 63 levels for
each referenced discipline. The following example illustrates the levels for a piping model with
attached reference models:
In this example, there are 63 active levels and 252 referenced levels which you can control (the
two equipment models use the same levels and symbology). If a certain type of duct in the
HVAC model resides on Level 30 in that model, and all unapproved Instruments are to be
placed on Level 30 in the piping model, these are treated as two completely different levels.
That is, you can turn off the display for the duct types on Level 30 in the HVAC model (via the
Reference Model controls) without affecting the display of unapproved instruments in the active
piping model.
All PDS users are encouraged to develop a logical, organized level control standard to manage
interdiscipline design files. The delivered seed file parameters for each application provide a
logical, organized, and coordinated level designation and control scheme. You can customize
the delivered parameters, but it is highly recommended that careful thought be given to the
custom setup.
 Once you develop a convention, whether it be the standard deliverable settings or an

in-house standard, do not change the level or symbology settings after model graphics
have been created. There is no easy way to propagate these changes to the existing
graphics in all the design files. The existing graphics will reflect the old settings and any new
graphics will reflect the modified settings.
 Since some applications rely on level assignments to perform basic functions (such as
placement of approved or unapproved items) which are transparent to the user, there is a
very real chance of destroying the integrity of the project if a symbology change is initiated
after the project is under way.
 When defining levels, it is important to provide plenty of separation between component
types. For example, instead of placing all Not Approved items in the same level, separate
them by type.

Creating 3D Models
For this reason, Intergraph recommends that you do not change the basic structure of the
symbology without careful thought. Attributes such as line weights, colors, and line types are
open to customization, but they should be established prior to project creation and should not
change throughout the life of the active design. Level assignments are also customizable;
however, they should be established before any components are placed in the model files.
Level and Symbology Defaults

The following outlines the delivered symbology schemes and describes how you can access
them for review and/or customization.
 PDS 3D (Equipment, Piping, and Drawing)
Graphic symbology and level assignments are stored as Type 63 data in the project or
model seed files. Changes in project seed data will be reflected in all subsequent models or
drawings, while changes in a model or drawing file's seed data will apply only to that design
file. The delivered settings are shown in Chapter 6 of the Project Administrator (PD_Project)
Reference Guide.
The seed data is accessed through the Project Data Manager function of the Project
Administrator. You can create a report of all Type 63 data at any time. Settings are
changed through a forms interface in the Project Data Manager session.
 Structural (FrameWorks Plus)
The graphic symbology and level assignments are stored in an ASCII file in the delivery
directory of the FrameWorks Plus product, and are copied into the project directory during
project creation. There are both predefined and user-definable categories (such as New and
Existing).
The default data can be changed using a text editor such as Notepad. The saved changes
are then adapted into the model. The file used for FrameWorks Plus models is framewks.txt
 Electrical (EE Raceway)
The graphic symbology is delivered with all categories set to Level 1. This is the only
application within Process & Power which leaves symbology definition totally up to the user,
and it is required prior to accessing a design file.
The default data is defined through a forms interface during project setup. The procedure is
outlined in the EE Raceway Modeling Reference Guide.
 PE-HVAC
Graphic symbology and level control is defined in an ASCII file named hv_symb.txt in the
project directory. The default data can be changed by editing the hv_symb.txt and
hv_symbm.txt files in the project directory.

Creating 3D Models
Graphics Environment for PDS 3D

The PDS 3D products provide an interactive graphics environment (based on MicroStation) for
the creation and manipulation of design elements. Like the other modules of PDS these
graphics environments are accessed through PD_Shell. The following outlines the basic steps to
access the graphic environment for most PDS 3D products:
1. Select the project from the PD Shell form and select the product you wish to use.
2. Select the 3D design area for the model to be entered.
3. Select the model to be entered.
The system verifies that you have write access to the selected model. If so, it activates the
graphical user interface for the selected model file.
Working with the Graphical User Interface

The main method of communication between you and the software application is through the
graphical interface. This interface is organized into functional parts; menus, palettes, dialog
boxes, view windows, and command menus.
Menus
Menus are your main source of interaction with the software application. It is from menus that
you access all other pieces of the application's interface.

Creating 3D Models
Palettes
Palettes are icon-based menus that provide access to dialog boxes or commands. These
palettes are organized into functional parts of the software, with each part represented by an
icon on the main palette. An icon is a graphical depiction of a command name that appears on a
menu.
Dialog Boxes
Dialog boxes are another type of menu available and represent the most detailed method of
interaction between you and the software.
Dialog boxes contain fields or boxes, menu bars, and buttons that help you to easily
communicate what you want to the software.

Creating 3D Models
View Windows
Control Menu—displays a list of window actions. Double-clicking on this

button deletes the window. To choose an action from the menu, drag the
data button to move the cursor through the list, releasing when the correct
item is selected.
 Restore—restores a minimized or maximized window to the previous
size and location.
 Move—moves a window around the workspace.
 Size—changes the height and width of the window in the direction
indicated by the pointer.
 Minimize—collapses a window down to its smallest size. Clicking on
this icon once the window has been collapsed will restore it to its
original size.
 Maximize—enlarges a window to its maximum size. If you choose this
menu entry on a window that is already at its maximum size, the
window is restored to its previous size and location.
 Lower—moves a window to the bottom of the window hierarchy.
 Close—deletes a window.

Creating 3D Models
Minimize—collapses a window.
Maximize—enlarges a window to its maximum size. If you choose the

maximize button on a window that is already at its maximum size, the
window is restored to its previous size and location.
Horizontal slider bar—allows you to drag the view to the left or right in
the window.
Vertical slider bar—allows you to drag the view up or down in the

window.
Move Arrows—drag the data button on the title bar to move the window to
a new location on the screen.
Vertical Arrows—appear when the cursor is over the top or bottom of the
frame. Drag the data button to change the height of the window as you
move the cursor.
Horizontal Arrows—appear when the cursor is over the left or right side
of the frame. Drag the data button to change the width of the window as
you move the cursor.
Diagonal Arrows—appear when the cursor is over the frame corners.

Click and drag the data button to change both the height and width of the
window without changing the position of the opposite corner.
Forms
Many PDS 3D commands activate forms. Forms are used for a variety of purposes within the
PDS environment. Most forms are activated when a command is selected and stay displayed as
long as that command is active. When the command terminates, the form is erased.

Creating 3D Models
The Create Drawing form from the Drawing Manager (PD_Draw) product is shown below.
Most forms contain the same basic features: buttons, fields, text, and other gadgets. In general,
anything you find on a form is called a gadget.
Selecting Options
You move through the forms by selecting function buttons or other gadgets from the form. Select
means to place the screen cursor (which appears as an arrow) on top of a screen gadget and
press <D>.
For most of the forms with scrolling lists, you can double-click on a row to select and accept the
data in that row. This performs the same action as selecting a row (which highlights) and then
selecting Confirm ().
You will use the select action to select functions, access other forms, activate data fields, toggle
buttons, select from lists, scroll through data displayed on the screen, and so on.
The following summarizes other basic actions you will use in the environments:
 Return — When keying in any data in a key-in field, press the <Return> key for the data to
be entered into the system. You can also press <Return> to move through a set of key-in
fields.
 Delete — If you make a mistake while keying in text, press the <Delete> key to erase
character(s) to the left of the cursor.
 Windows Editing — You can use standard Windows editing commands to edit key-in fields.

Creating 3D Models
Common Tools on Forms

There are many gadgets in the environments that are common to most or all of the forms. These
tools and their functionality are described below.
The Help command activates on-line Help for the active form. Help remains active until
you delete the Help window.
The Cancel command is used to exit the active software, and return to the system
prompt.
The Confirm () is used to accept a selection or operation. Depending on the active form
or option, the active form will remain active so that you can repeat a similar operation or control
returns to the preceding form.
The Reset command with the curved arrow abandons the current form, returning to the
immediately preceding form in the hierarchy.
Scrolling List
Some screen menus have a scrolling list of projects or applications. You need to scroll a list only
if more options are available than can be displayed in the window. To scroll a list, select the
arrow buttons on the side of the list. The list scrolls up or down depending on which arrow you
choose. To scroll one line at a time, select the smaller arrows. To scroll one window at a time,
select the larger arrows.
You can also drag the slider up or down the bar by selecting it with the <D> button, keeping the
<D> button depressed, and moving the mouse up or down. The items scroll through the window
as you move the button. The size and position of the slider on the scroll bar is an indication of
the number of lines and the relative position within the list.
All commands which display a list of design areas or models will order the list alphanumerically
by the design area number or model number in ascending order.

Creating 3D Models
Key-in Fields
Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark
gray. You can select a key-in field and key in a new value. A bar cursor appears in the active
key-in field. Key in your input and press <Return>. To change afield, reselect the field and key in
the desired information. Key-in fields have a maximum number of characters depending on the
item being defined.
Key-in fields that appear on forms built with Form Builder accept EMACS editing commands.
If you select a key-in field for a code-listed attribute, the system activates a form which lists the
code list values for the selected field.
Microstation requires lowercase characters for the file specification and path name of all design
files. Therefore, the system will automatically convert any input for the file specification and path
name of a design file (such as a model or drawing) to lowercase before loading into the Project
Control Database.
Display-list Boxes
A display-list box is located at the end of some key-in fields and lets you select data from a list
instead of keying in information. For example, there is a display list associated with the
Authorization key-in field shown. At the end of the field, there is a small box with horizontal
dashes. When you select this display list box with the screen cursor, an associated list of valid
input values displays. Select the desired item from the list to input its value into the field.
Shift Left and Shift Right buttons
At the bottom of some key-in and display fields, there are two buttons marked with arrows.
These buttons are called shift left and shift right buttons.
Often, you can key in more characters than a field display shows. Shift Left moves the text
display to the front of field; Shift Right moves the text display to the end of the field.
Toggle
A toggle field on a screen menu is used to select one of two possible choices, one of which is
always displayed. Place a data point on the toggle field to toggle between the two choices.

Creating 3D Models
Roll-Through List
A roll-through list shows one choice at a time of a list that can be several items long. Place a
data point on the roll-through list to scroll through the available options. The option displayed is
active.
Standard Window Icons
If you press <D> along the edge of a form or any area not occupied by a button, key-in field, or
other gadget, a box of icons displays. You can manipulate form windows just like any other
workstation window.
The following list defines in order the available window icons.
Collapse/Restore Pop-to-bottom Pop-to-top
Repaint Modify/Resize Restore Size
Base Form
When you enter the graphics environment, the system displays the base form. This form
indicates the product creation date, software version number, active project number, and the
active model number.
You can also use this form to define the location on the screen to display all of the Piping Design
forms.
 To revise the location of the form display,
 Cancel any other forms. The base form should be the only form displayed. Move the form to
the desired location.

Creating 3D Models
 Select the File Design command to save the active form location. All subsequent forms will
display in the saved location.
3D Seed Data
You can use the Project Data Manager to modify seed information for the project seed files or
for a specified model. These options affect all of the project seed files and the project marker
file.
Select the option for the type of 3D data to be revised. The following report
shows the delivered settings for the 3D data.
Plant Coordinate System Definition
Plant Coordinate System Description : Plant Coordinate System
Plant Coordinate System Monument :

Easting : E 0' 0" Plant
Northing : N 0' 0" Plant
Elevation : El 0' 0" Plant
Design Volume Coordinate System

Definition
Design Volume Coordinate System Description : Design Volume Coordinate

System

Creating 3D Models
Design Volume Coordinate System Monument :

Monument in Design Volume Coordinate System :
Design Volume Monument in Plant Coordinate System :
Orientation of Design Volume Coordinate: East
Orientation of Design Volume Coordinate System as clockwise Angular

Offset of Design Volume North from Plant North :
0.000000
Angular Label/Readout
Angular Label Decimal Degrees Accuracy : 1 Decimal Place

Angular Readout Decimal Degrees Accuracy : 1 Decimal Place
Angular Input is Clockwise from North
Slope Readout Accuracy : Number of Inches per Foot
Date/Time Format
Date/Time Format is : Wed Apr 13 14:34:27 2011
Coordinate Label/Readout
Descriptions
Active Coordinate Label Format : East 1' 6 3/8" Plant

Active Coordinate Readout Format : E 1' 6 3/8" Plant
Coordinate System Label :

Design Volume : Site
Plant : Plant
World : World
Coordinate System Readout :

Design Volume :
Plant : Plant
World : World
Coordinate Axis Label :

East : East
West : West
North : North
South : South
Elevation : Elev
Coordinate Axis Readout :

Creating 3D Models
East : E
West : W
North : N
South : S
Elevation : El
Dimensioning : English
Coordinate Label/Readout Format
Coordinate Label Formats :

1' 6 3/8" East Plant
1' 6 3/8" Plant East
East 1' 6 3/8" Plant (Active)
East Plant 1' 6 3/8"
Plant 1' 6 3/8" East
Plant East 1' 6 3/8"
Label Description On
Coordinate Readout :
1' 6 3/8" E Plant
1' 6 3/8" Plant E
E 1' 6 3/8" Plant (Active)
E Plant 1' 6 3/8"
Plant 1' 6 3/8" E
Plant E 1' 6 3/8"
Readout Description On
Coordinate Label/Readout Units

Label Units : Master Units and Subunits
Readout Units : Master Units and Subunits
Metric System of Units Label : Subunits Only
Label Descriptions :
Master Units Short Description : '
Subunits Short Description : "
Master Units and Subunits Separator :
Subunits and Fraction of Subunits Separator :
Readout Descriptions :
Master Units Short Description : '

Creating 3D Models
Subunits Short Description : "

Secondary Units Descriptions :

Master Units Short Description : M
Subunits Short Description : MM
Coordinate Label/Readout Precision

Label Precision : Decimal to nearest 1/16

Label Alphanumeric Fraction
Readout Precision : Decimal to nearest 1/16
Secondary Precision : Decimal to nearest integer

Creating 3D Models
Creating Equipment Models

The PDS Equipment Modeling (PD_EQP) product models equipment and equipment items for
later connection to PDS piping components created through the Piping Designer software. The
Equipment Modeling product defines equipment volumes and positions nozzles on the
equipment.

Creating 3D Models
Functions of PDS Equipment Modeling (PD_EQP)

With PDS Equipment Modeling (PD_EQP), you can perform the following tasks:
 Place basic three-dimensional building blocks such as cylinders, cones and boxes called
primitives.
 Place three-dimensional equipment and components called parametrics, which are
predefined and delivered in a library with the product.
 Create complex parametrics using the EDEN language and add them to the Reference
Database for future placement. Refer to the PDS Eden Interface Reference Guide for
details.
Primitive Parametric
About the Reference Database (RDB)

The following libraries comprise the RDB and are used to define the equipment and make it
compatible with existing piping specs:
 Graphic Commodity Library
 Tutorial Definition Library
 Piping Physical Data Library
 Piping Design Standard Note Library
 Piping Specification Tables Library.

Creating 3D Models
Equipment Model Seed Data

The Project Data Manager is used to revise the seed data for a specified Equipment model or
create a report of the RDB data. You can revise both 3D data and model data. The Revise
Equipment Data option is used to revise the model data for the selected equipment model file.
The system activates the following form which provides access to the modification options.
Select the option for the type of model data to be revised. The following report shows the
delivered settings for the Equipment Model Data.
Equipment
Data Manager
Equipment Graphic
Symbology
Primitives/
Parametrics
Category Level Color Weight Symbology
Physical 10 9 2 Solid
Eqp Category 2 1 White 0 Solid

Creating 3D Models
Nozzles
Nozzle Category Small 12 9 3 Solid
Nozzle Category Medium 12 9 3 Solid
Nozzle Category Large 12 9 3 Solid
Envelopes
Maintanence Envelope 40 8 1 Solid
(Hard)
Maintanence Envelope 41 8 0 Solid
(Soft)
Access Envelope 42 10 1 Solid
(Hard)
Access Envelope 43 10 0 Solid
(Soft)
Safety Envelope 44 11 1 Solid
(Hard)
Safety Envelope 45 11 0 Solid
(Soft)
Construction 46 12 1 Solid
Envelope (Hard)
Construction 47 12 0 Solid
Envelope (Soft)
Insulation Envelope 56 White 2 Solid
Equipment Graphic (continued
Symbology )
Steel

Ladders 20 White 1 Solid
Platforms 21 White 1 Solid
Handrails 22 White 1 Solid
Miscellaneous Light 23 White 1 Solid
Steel
166
Semi-Intelligent
Graphics
Semi-Intelligent 51 White 0 Solid
Category 1
Category 2
Category 3
Category 4
Category 5
Creating Equipment Models
Dumb Graphics

Dumb Category 1 30 White 0 Solid
Miscellaneous

Creating 3D Models
Place Point 48 15 8 Solid
Datum Point 50 13 10 Solid
Hole Elements 15 White 0 Solid
2-D Shadows 12 9 3 Solid

Project Data
Manager
Nozzle Options
Default
Placement
Nominal Piping
Diameter
System of Units :
English
Small is <= : 2IN
Large is >= : 14IN
Table Name : D036
Define Table Suffix : Bolted -
by End Type 5
Female - 5
Male - 5
Project Data
Manager
Equipment Reference Database Management
167
PDS 3D Theory — April

2002
Graphic Commodity
Library
Approved : E:\pdsproj\rd zi_eqpms.lib
PDSSERVER b\eqp\approve
d\
Tutorial Definition
Library
Approved : E:\pdsproj\rd zi_tutlib.lib
d\
Equipment Physical Data Library
Approved : E:\pdsproj\rd us_pcdim.l

d\
Piping Physical Data
Library
Approved : E:\pdsproj\rd us_pcdim.l
d\
Piping Design Standard Note Library
Approved : E:\pdsproj\rd std_note.l

d\
Piping Job Specification Table
Library
Approved : E:\pdsproj\rd us_pjstb.l
d\
Cell library
Approved : E:\pdsproj\rd equip.cel
d\
Forms Directory
Location
Approved :
Project Data
Manager
Interference Envelope
Emulation Data
Distance Between Two Planes for Clash Checking : 1"
Number of Emulated Cylinders Per 90 Degree Torus : 4

Length of Emulated Cylinders for Cone : 1"
Length of Emulated Cylinders for Semi-Ellipsoid : 1"

Creating 3D Models
Equipment Modeling Environment

The Equipment Modeling Interface is accessed through PD_Shell. This interface allows you to
enter the Equipment Modeling graphics environment, create or modify Eden and Tutorial
Definition files, print reports and define or edit filenames and locations for libraries.
Operating Sequence
1. At the Plant Design System form, select the Equipment Modeling option.
The system displays the Equipment Modeling Options form.
2. Select the Equipment Modeling option to enter the graphics environment.

Creating 3D Models
The system displays the Equipment Modeling form listing the available design area numbers
and their corresponding descriptions.
3. Select Design Area

Select the 3D design area to modify and click Confirm.

Creating 3D Models
The system lists the equipment models for the selected design area and their corresponding
descriptions.
4. Select Model
Select the Model Number to modify and click Confirm.
The system enters the graphics design file.
Equipment Modeling Concepts

You can orient equipment items in a 3D design file using the refresh (orientation) tee and the
coordinate axis system. The refresh tee provides you with both the active point location and the
active orientation. The active point displays where the graphics will be placed while the active
orientation displays the graphic's orientation.
The term refresh denotes graphics which are temporarily drawn on the screen and can be
moved dynamically. The refresh tee appears at the active place point when selecting placement
commands. It consists of two lines.
 The primary axis originates at the active place point and is aligned with the equipment item
center line.

Creating 3D Models
 The secondary axis is aligned perpendicular to the primary axis with its origin at the
bisecting point with the primary axis. This axis is used to define the auxiliary orientation.
When placing an equipment item with the refresh tee, you can adjust the orientation by one of
the following methods:
 Selecting the reset button (<R>) to adjust the orientation 90 ° around the active axis.
 Keying in a specific angle.
 Using the Refresh Manipulation commands via the coordinate axis system.
The coordinate axis system display consists of a refresh line originating at the active place point
and pointing in one of six coordinate directions: North, East, Up, South, West and Down.
If the coordinate axis system display is turned on, the refresh tee appears at the active place
point when you select a secondary command such as Absolute PDS XYZ or Delta PDS XYZ.
You can confirm the direction of the active axis by viewing the status field. The system displays
the directional information using a few simple symbols.
**P-IN S-
P -primary axis
S - secondary axis
** - indicating the active axis

Creating 3D Models
-IN or - indicating the direction the active axis is pointing depending on the active view.
-OUT In a specified view (other than Iso), IN points away from you when looking at a model.
OUT points toward you when looking at a model. For example when looking at a north view, IN
points north (away from you) and OUT points south (toward you).
In the example above, the primary axis is the active axis and points IN toward the displayed
view. The secondary axis is only visible in the displayed view. Since the primary axis is active, it
can be rotated by a Refresh Manipulation command.
The refresh tee cannot be displayed on a screen if it is located outside of the screen
view.
Also, a 3D representation of the orientation axes with their center located on the placement point
appears in place of the orientation tee previous to its displacement. This axis is called the
Coordinate Axis or the Coordinate System Indicator (CSI).
Activating the Orientation Tee

When activating the orientation tee, the system displays the coordinate axis in its place previous
to its displacement. The orientation tee can be manipulated only in the following instances:
 It can be manipulated when the active point is defined using the ACTIVE POINT command.
After selecting this command, you can use any of the pocket menu options to manipulate
the tee. Angles of rotation cannot be entered with this command.
 When placing equipment and components using a form or a parametric tutorial for
equipment or component generation and manipulation. Angles of rotation can be keyed in,
where positive angles are measured in the counterclockwise direction looking from the
direction where the non-rotating axis is pointing. To change the axis to be rotated, select the
CHANGE AXIS option.
 When an equipment or component manipulation command (Move, Copy, Rotate, Mirror,
etc.) is active. Angles of rotation for primary or secondary axis cannot be entered in this
mode.

Creating 3D Models
Equipment Modeling Commands

This section lists the Equipment Modeling commands that are available.
Equipment Manipulation Commands

These commands allow you to create, copy, move, delete, rotate and mirror entire pieces of
equipment defined either individually or by a fence. You can create equipment using user
defined primitives or parametrics.
Component Manipulation Commands

These commands allow you to add components or equipment items to existing pieces of
equipment and also copy, move, delete, rotate, mirror, and modify equipment items.
Nozzle Manipulation
This command allows you to place nozzles in reference to a datum point or another nozzle. The
new nozzle will be added to the same equipment tag owning the referenced datum point or
nozzle.
Review/Revise Commands
These commands allow you to view or revise data associated with the current project or
drawing. This data includes project file data and equipment attributes.
Define Commands
These commands allow you to define the active placement point, the view orientation, and
display categories.
Miscellaneous Commands
These commands perform a variety of manipulations including envelope file generation, datum
point manipulation, dimension checking, viewing specific equipment groups, attaching graphics,
controlling display categories, reviewing error messages, attaching reference models, and
defining saved views.

Creating 3D Models
Secondary Commands
These commands provide support for the primary commands. A Secondary Command will not
function unless a primary command is active. These commands are used to orient the screen
views, defines precision input, adjust the orientation of the refresh tee, or define the coordinate
system.
Creating Piping Models

The Piping Designer (PD_Design) is one module of PDS 3D products. It is specifically intended
for the creation and revision of 3D models in the design of the piping and in-line instrumentation
within the plant. The resulting piping models can be used for checking interferences, extracting
drawings, and generating bills of material.
The following illustration shows a typical piping model with reference models attached. The
piping model contains fully dimensioned graphics for piping, piping components, instruments,
piping specialties, and pipe supports. You can access coordinate points from the reference
models and review database attributes.
Piping Model With Attached Reference Models

Creating 3D Models
Each component in a piping model is linked to a database record which contains non-graphic
information about the component. When a component or segment is placed in the model, the
system creates a row in the appropriate database table(s). A row represents one instance or
record in the database.
Database Attributes Associated with Graphics

Creating 3D Models
Piping Model Seed Data

The Revise Model Data option is used to revise the Model data in the project seed file or a
specific piping model. The system activates the following form which enables you to access the
modification options.
Select the option for the type of model data to be revised. The following report shows the
delivered settings for the Piping Model Data.
Project Data Manager
Component Placement
Bend Deflection Table : BEND_DEFLECTION

Commodity Name Table : COMMODITY_ITEM_NAME
Pipe Length Threshold Table : PIPE_LENGTH
Segment Pipe Run Length Threshold Table : PIPE_RUN_LENGTH
Weld Type Table : WELD_TYPE_TABLE
Flange Data Module :
Reinforcing Weld Data Module :
Reinforcing Pad Data Module :
Pipe Commodity Name : PIPING
Tube Commodity Name : TUBE
Field Weld Symbol Name :
Isometric Drawing Symbol Name :
Angular Tolerance (Automated Component): 0.500000
Vicinity Tolerance : 4.000000

Piping Data Control
P&ID Component Name : Commodity Name

Fluid Code Update : Off
Weight Table : On
Branch Component Association for Isometric Drawings : Header
Copy Option : Append Prefix
Geometric Industry Standard : Expanded
Schedule Thickness Override Option : Larger of Override and Spec
System of Units for Nominal Piping Diameter : English
Field Name for Nominal Piping Diameter : IN

Physical Units Options
Insulation Density : lb/ftˆ3

Surface Area : ftˆ2
Dry/Wet Weights : lb
Maximum Temperature (Spec) : degF

Nozzle Data Transfer List
There are currently NO nozzle attributes selected for transfer

Creating 3D Models
Project Data manager
Graphic Symbology
Weights :
Piping Commodity : 2
Piping Specialty : 2
Instrument : 2
Piping/Tubing : 2
Pipe Support : 2
Model Symbology : Simple
Color : Model Category
Project Data manager

Graphic Symbology - Model Category
Nominal Piping Diameter :

Small is <= 2IN
Large is >= 14IN
Level Color
Piping Segment Not Approved Small 1 Blue
Piping Segment Not Approved Medium 11 Blue
Piping Segment Not Approved Large 21 Blue
Piping Segment Approved Small 31 Blue
Piping Segment Approved Medium 41 Blue
Piping Segment Approved Large 51 Blue
Piping/Tubing Not Approved Small 3 Green
Piping/Tubing Not Approved Medium 13 Green
Piping/Tubing Not Approved Large 23 Green
Piping/Tubing Approved Small 33 Green
Piping/Tubing Approved Medium 43 Green
Piping/Tubing Approved Large 53 Green
Piping Commodity Not Approved Small 2 Green
Piping Commodity Not Approved Medium 12 Green
Piping Commodity Not Approved Large 22 Green
Piping Commodity Approved Small 32 Green
Piping Commodity Approved Medium 42 Green
Piping Commodity Approved Large 52 Green
Piping Specialty Not Approved Small 4 Orange
Piping Specialty Not Approved Medium 14 Orange
Piping Specialty Not Approved Large 24 Orange
Piping Specialty Approved Small 34 Orange
Piping Specialty Approved Medium 44 Orange
Piping Specialty Approved Large 54 Orange
Instrument Not Approved Small 5 Orange
Instrument Not Approved Medium 15 Orange
Instrument Not Approved Large 25 Orange
Instrument Approved Small 35 Orange
Instrument Approved Medium 45 Orange
Instrument Approved Large 55 Orange
Pipe Support - Logical Not Approved N/A 7 Violet
Pipe Support - Physical Not Approved N/A 10 White
Pipe Support - Logical Approved N/A 37 Violet
Pipe Support - Physical Approved N/A 40 White
Miscellaneous Graphics 58 Red
Diagnostic Markers 59 Red
Automated Component/Pipe Placement Markers 62 Red
Model Reconstruction Markers 63 Red

Symbology for Markers
Weights :
Diagnostic Markers : 2
Design Check Markers : 2
Automated Placement Markers : 2
Model Reconstruction Markers : 2
Field Weld and Isometric Drawing Symbol : 2
Symbol Font Number : 125
Text Height : 6"
Text Width : 6"
Field Weld Symbol Name :
Isometric Drawing Symbol Name :

Material Takeoff Options
Commodity Code : Size Independent

Length Calculation : Almost Precise
Bolt Commodity Code : Piping Job Spec
Bolt Diameter Units : English
Bolt Length Units : English
Bolt Roundoff Option : Preferred Bolt Length
Alternate Gasket Search : Off
Field Fit Length : Off
Gasket Commodity Name : 6Q3C95
Bolt Commodity Name : 6Q3C97

Creating 3D Models
Nut Commodity Name : 6Q3C98
Bolt Data Module : BOLT_DATA
Flange Data Module : FLANGE_DATA_MTO
Bolt Length Table : BOLT_LENGTH

Design Review Label Option
Selected Labels :
There are NO Design Review Labels Selected

Default Segment Parameters
unit_number
fluid_code Standard Note Number is Undefined <125,0>
unit_code
line_sequence_no
nominal_piping_dia 100-3/4IN
piping_mater_class
insulation_purpose Standard Note Number is Undefined <220,0>
insulation_thick 0’ 0"
nor_oper_pres 0.000
nor_op_pres_units Standard Note Number is Undefined <1064,0>
nor_oper_temp 0.000
nor_op_temp_units Standard Note Number is Undefined <1056,0>
nor_dgn_pres 0.000
nor_dgn_pres_units Standard Note Number is Undefined <1064,0>
nor_dgn_temp 0.000
nor_dgn_temp_units Standard Note Number is Undefined <1056,0>
insulation_density 0 lb/ftˆ3
heat_tracing_reqmt Standard Note Number is Undefined <200,0>
heat_tracing_media Standard Note Number is Undefined <210,0>
heat_tracing_temp 0 degF
design_resp Standard Note Number is Undefined <160,0>
supply_resp Standard Note Number is Undefined <160,0>
construction_resp Standard Note Number is Undefined <160,0>
construction_stat Standard Note Number is Undefined <130,0>
hold_status Standard Note Number is Undefined <50,0>
design_area_number
alt_oper_pres 0.000
alt_op_pres_units Standard Note Number is Undefined <1064,0>
alt_oper_temp 0.000
alt_op_temp_units Standard Note Number is Undefined <1056,0>
alt_dgn_pres 0.000
alt_dgn_pres_units Standard Note Number is Undefined <1064,0>
alt_dgn_temp 0.000
alt_dgn_temp_units Standard Note Number is Undefined <1056,0>
steam_outlet_temp 0.000
steam_temp_units Standard Note Number is Undefined <1056,0>
train_number
mater_of_construct
safety_class Standard Note Number is Undefined <340,0>
design_standard Standard Note Number is Undefined <570,0>
fluid_category
coating_reqmts Standard Note Number is Undefined <190,0>
cleaning_reqmts Standard Note Number is Undefined <230,0>
package_system_no
module_no
specific_gravity_a 0.000
specific_gravity_b 0.000
specific_gravity_c 0.000
viscosity 0.000
density 0.000
spec_heat_ratio 0.000
sonic_velocity 0.000
surface_roughness 0.000
test_system_no
test_fluid Standard Note Number is Undefined <125,0>
test_pressure 0.000
schedule_override

Design Consistency Checks
Data :
Flow Direction : Hard Check
Flow Centerline : Hard Check
Outside Diameter : No Check
Schedule/Thickness : No Check
Piping Materials Class : Soft Check
Materials of Construction Class : Soft Check
Insulation Thickness : Soft Check
Insulation Purpose : Soft Check
Tolerances :
Flow Centerline Alighment : 0.500000

Creating 3D Models
Insulation Thickness : 1/4"

End Prep Compatibilities Bolted End Preps
FFFE -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE FFTBCSEWG FFFTBE FFFTBEWG
FFFEWG -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE FFTBCSEWG FFFTBE FFFTBEWG
RFFE -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE RFTBCSEWG
RFFEWG -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE RFTBCSEWG
RJFE -
RJFE RJLFE RJTBE MRJTBEWG RJTBCSE
STFE -
SGFE SGLFE
LTFE -
LGFE LGLFE
SMFE -
SFFE SFLFE
LMFE -
LFFE LFLFE
SGFE -
STFE STLFE
LGFE -
LTFE LTLFE
SFFE -
SMFE SMLFE
LFFE -
LMFE LMLFE
FFLFE -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG
RFLFE -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG
RJLFE -
RJFE RJLFE RJTBE MRJTBEWG
STLFE -
SGFE SGLFE
LTLFE -
LGFE LGLFE
SMLFE -
SFFE SFLFE
LMLFE -
LFFE LFLFE
SGLFE -
STFE STLFE
LGLFE -
LTFE LTLFE FFTBCSEWG
SFLFE -
SMFE SMLFE
LFLFE -
LMFE LMLFE
FFTBE -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE
FFTBEWG -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSEWG
RFTBE -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE
RFTBEWG -
FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSEWG
RJTBE -
RJFE RJLFE RJTBE MRJTBEWG RJTBCSE
MRJTBEWG -
RJFE RJLFE RJTBE
FFTBCSE -
FFFE FFFEWG FFTBE
FFTBCSEWG -
FFFE FFFEWG LGLFE FFTBEWG
RFTBCSE -
RFFE RFFEWG RFTBE
RFTBCSEWG -
RFFE RFFEWG RFTBEWG
RJTBCSE -
RJFE RJTBE
FFFTBE -
FFFE FFFEWG FFFTBE
FFFTBEWG -
FFFE FFFEWG FFFTBEWG
MJE -
MJE

End Prep Compatibilities Male End Preps
BE -
BE TBE PE SE SWE HCE

Creating 3D Models
TBE -
BE TBE PE SWE HCE
MFE -
MFE
MTE -
FTE
MGE -
FGE
MQCE -
FQCE
MFRE -
FFRE
MHE -
FHE
SPE -
BLE
PE -
BE TBE PE SE SWE FTE HCE
3"FFPE -
HCE

End Prep Compatibilities Female End Preps
SE -
BE PE
SWE -
BE TBE PE
FTE -
MTE PE
FGE -
MGE
FQCE -
MQCE
FFRE -
MFRE
FHE -
MHE
BLE -
SPE
HCE -
BE TBE PE 3"FFPE

Reference Database Management
Material/Specification Reference Database

Approved : ra_tcproj
Piping Job Specification Table Library
Approved : wegl ..\win32app\ingr\rdusrdb\ us_pjstb.l
Short Material Description Library
Approved : wegl ..\win32app\ingr\rdusrdb\ us_shbom.l
Long Material Description Library
Approved : wegl ..\win32app\ingr\rdusrdb\ us_lgbom.l
Specialty Material Description Library
Approved : wegl ..\win32app\ingr\rdusrdb\ us_spbom.l
Standard Note Library
Approved : wegl ..\win32app\ingr\pdshell\lib\ std_note.l
Label Description Library
Approved : wegl ..\win32app\ingr\pdshell\lib\ labels.l
Piping Assembly Library
Approved : wegl ..\win32app\ingr\pdshell\lib\ assembly.l
Graphic Commodity Library
Approved : wegl ..\win32app\ingr\pdshell\lib\ pip_gcom.l
Physical Data Library - U.S. Practice
Approved : wegl ..\win32app\ingr\rdusrdb\ us_pcdim.l
Physical Data Library - DIN
Approved :
Physical Data Library - British Standard
Approved :
Physical Data Library - European A
Approved :
Physical Data Library - European B
Approved :
Physical Data Library - JIS
Approved :
Physical Data Library - Australian
Approved :
Physical Data Library - International A
Approved :
Physical Data Library - International B
Approved :

Creating 3D Models
Graphic Concepts for Piping Design

The screen working area is used to display and manipulate graphic information. This information
is managed by MicroStation; refer to the MicroStation documentation for details.
Refresh graphics are graphics which are temporarily drawn on the screen. Piping Designer
uses refresh graphics to display placement aids such as the orientation tee and coordinate
system indicator.
Graphics are frequently highlighted to provide visual feedback pertaining to the active input.
Highlighting is normally followed by an Accept/Reject step allowing you to accept the highlighted
graphics as the desired input or to reject the highlighted graphics and select another graphic.
This following concepts and terms are common to the Piping Designer operations.
Piping Segments
The centerline routing within a model is represented by geographically connected piping
segments. A piping segment defines the geometry of the pipeline and contains the non-
graphical data associated with that pipeline. A single piping segment can define changes of
direction, but an additional segment is created at a branch point or an attribute break, such as a
size change or a spec break.
The following illustrates the terminology associated with a piping segment.
A pipeline consists of a set of graphically connected piping segments including all the branches.

Creating 3D Models
Active Placement Point

The term active placement point refers to the coordinate location used by the Place
Component command. It defines the point at which piping and instrumentation are placed. You
can use Connect to Design to place a piping or instrument component at an existing, intelligent
location in the model, such as a piping or instrumentation connect point, a nozzle, or a piping
segment.
The system uses the orientation tee to indicate the location of the Active Placement Point.
Coordinate System Indicator and Orientation Tee Coordinate

System Indicator
The coordinate system indicator is a temporary display symbol which represents the six
orthogonal directions (North, South, East, West, Up, and Down) of the coordinate system.
Piping Designer uses the coordinate system indicator to indicate the active coordinate location
when
 defining or manipulating a piping segment
 identifying a point on a piping segment
 identifying a component center or connect point
 sketching a pipeline.

Creating 3D Models
Orientation Tee
The orientation tee is a temporary display symbol which enables you to orient a component
before placement. The orientation tee is composed of two lines:
 a primary axis representing the flow centerline
 a secondary axis used to orient components which are not symmetrical about the flow
centerline (for example, a valve with an operator).
When the Place Component command is active, the system displays the orientation tee at the
Active Placement Point and displays related information in the screen message fields.
P **S-OUT
The stars (**) indicate the active axis of rotation (the secondary in the above message). When
either axis is rotated such that its orientation is not in the plane of the view, the suffix IN or OUT
is displayed next to P (primary) or S (secondary) indicating whether that axis is pointing in or out
of that view. For example, when the secondary axis is perpendicular to the screen and oriented
toward the designer, the message P S-OUT is displayed.
When placing a component with the orientation tee, you can adjust the orientation by pressing
<R> or selecting one of the Orientation Control commands.

Creating 3D Models
Piping Connect Points

Each component has a center and at least one connect point or pressurized end. A connect
point is usually an end of a piping component to which another component or pipe (with
compatible properties) is connected. The connect point stores the description of the component
at that end. It indicates the flow centerline orientation, and properties such as diameter, end
preparation (flanged, welded,...), and rating.
The following rules (in order of priority) are used to determine the assignment of connect point
numbers:
1. Connect Point 1 is always at the larger end (NPD).
2. If the ends have the same NPD, but different end preparations, then Connect Point 1 is
assigned an end preparation in the following precedence: Bolted, Male, Female.
Refer to the PDS Piping Component Data Reference Guide for a detailed explanation of connect
point assignments.
Piping Design Commands

The following Piping Design commands are available.
Placement Commands
Placement commands enable you to place pipe, piping components, pipe supports, and
instrument components. You can also place assemblies (predefined sets of components).
These commands can be used at any time in the design process. In the process of creating a
piping model you will use a combination of these commands depending on the desired result. A
typical approach is to use
 Sketch to route the layout of a pipeline and define the attribute data for the pipeline. The
attribute data can be defined manually, copied from another segment, or updated from
information in the P&ID database.
 Place Component to place components such as valves, instruments, or commodity
overrides along the segment pipeline.
 Automated Placement to populate the pipeline with fittings and pipe.
The Copy Piping, Copy and Mirror Piping, and Copy and Rotate Piping commands
automatically change the approval status of piping segments and piping components to not
approved during the copy operation.
You cannot make any of the following changes to approved piping.

Creating 3D Models
 Create a new piping segment in the Sketch command by connecting to previously placed,
approved piping.
 Place new piping components, instrument components, piping, or tubing in the Place
Component command by connecting to previously placed, approved piping.
 Place new pipe supports in the Place Pipe Support command by connecting to previously
placed, approved piping.
 Place new pipe supports in the Place Logical Support command by connecting to
previously placed, approved piping.
Revision Commands
The Revision commands enable you to move, delete, and rotate existing piping. You can revise
individual components, piping segments, or all the elements on a pipeline or defined by a group
operation.
These commands can be used at any time in the design process to move, modify, or delete a
component, a piping segment, or a group of elements such as a pipeline.
Any rotation, addition, reconstruction, or deletion of PDS piping components and segments must
be done through these commands and not through MicroStation manipulations due to the
interdependence of graphic and database information.
Component Revision
These commands revise/append different positional and/or database information on PDS piping
components. Any rotation, addition, or reconstruction of PDS piping components must be done
through these commands and not through MicroStation manipulations due to the
interdependence of graphic and database information. You cannot use MicroStation commands
to change piping as they will not update the user data associated with the piping segment or
component.
Segment Vertex Commands

These commands enable you to revise piping segments in the active model. You can add,
move, or delete an imbedded vertex for an existing piping segment. These commands cannot
be used if the segment has been populated with pipes or components.
Piping Revision
These commands enable you to move, delete, rotate, and reconstruct existing piping. You can
revise a pipeline or those elements defined by an active group. The commands perform both
graphical and database revisions.

Creating 3D Models
Model Data
These commands enable you to review or revise the model data stored in the Design Database
and Project Control Database. Each component in a piping model is linked to a database record
which contains non-graphic information about the component. When a component or segment is
placed in the model, the system creates a row in the appropriate database table.
These commands can be used at any time in the design process to review or revise the model
data stored in the Design Database.
Review Data
These commands enable you to review information in the Design Database or review existing
report files. You can only view the information you cannot make any changes. You can review
data for elements in the active model and attached reference models.
Revise Data
These commands enable you to revise information in the Design Database and define additional
information for components. You can only revise information for items in the active model.
Analyze Data
These commands enable you to review information related to the model analysis operations.
You can also check for interferences within the active model file. Many of these command are
dependent on data from the Design Data Management commands.
Refer to the Chapter on Interference Detection for more information on detecting and reviewing
interference clashes.

SECTION 6
PDS P&ID to Piping Data Transfer
PDS provides capabilities for distributing data from one part of the design process to another.
One aspect of this integration is the transfer and comparison of data between the P&ID task and
the Piping task. This section describes the conventions that apply to the loading, updating, and
comparison of data between the P&ID Database and the piping model.
Features
 Update segment data. You can transfer segment data from the P&ID to update the active
segment data, to define line attributes while sketching, or to revise a segment attribute or set
of attributes.
 Review component names. You can select a component on the P&ID to define the
commodity item to be placed.
 Compare data. You can compare data in the model against data in the P&ID to verify that
all the information is in agreement.
 Graphical interface. The easiest way to transfer or review data is to use the graphical data
transfer options. This allows you to display the P&ID drawing in a view while working in the
model and select items directly from the drawing graphics.
PDS also supports transfer by line ID or by identifying an equipment nozzle as the start of a
pipeline.
Database Requirements
For the P&ID Database to be linked to the Piping Design Database, the two applications must
share the same Project Control Database schema. This can be achieved by using the same
project number when creating the schematic project and the 3D project. Although the Project
Control Database schema must be shared, the P&ID Database schema and the Piping Design
Database schema are otherwise independent.
Unit Number
The unit number attribute is used to locate the relevant P&ID data within the P&ID Task and
Master Database. The unit number should be set in the active segment data to match the Unit
Number setting within the P&ID database.
Propagated Drawings
Only those P&ID drawings which have been successfully propagated can be referenced for
P&ID to Piping data transfer.

P&ID Correlation Table

The P&ID Correlation Table is an ASCII file used to correlate a particular column or columns in
the P&ID segment table of the P&ID Database with a corresponding column in the piping
segment table of the Piping Design Database.
The P&ID Correlation Table defines which database columns are to be transferred and
compared.
Any columns not specified in the Correlation Table will not be transferred.
The P&ID column numbers required in the Correlation table are from the relational database and
are not the P&ID attribute numbers.
During the interactive loading of segment data, you can specify that either a complete or partial
set of data be considered. The Correlation Table specifies which columns are to be loaded,
updated, or compared for both complete and partial data transfer.
The Correlation Table is expected to exist in the project directory for the applicable project, (the
directory that includes the seed model, seed drawings, etc.) A default Correlation Table is
delivered in the PD_Shell product and is automatically copied to the project directory when a
new project is created. You can edit the Correlation Table, if required, to add columns to or
delete columns from both the complete and partial data transfer processes. An asterisk (*)
signifies that data transfer and comparison is applicable for that particular column. You can also
add user-defined columns of piping segment data to the Correlation Table.
The default Correlation Table is defined as follows:
# Segment Data Model P&ID Complete Partial
#If you desire to default the ’non-partial’ attributes during a partial transfer of #data, in the partial column place
a ’-’, skip at least one space, and define the #default value. The default value will be used whenever an interactive
transfer #occurs, or if the toggle is set for the batch update. The complete, #partial and default values are supported
ONLY in this section of the file.
#example: attribute_one 99 100 * - default_value
unit_number 4 13
unit_code 5 2 * *
module_no 6 79 *
package_system_no 7 81 *
train_number 8 23 * *
fluid_code 9 22 * *
line_sequence_no 10 24 * *
nominal_piping_dia 11 15 *
npd_units -1 16
piping_mater_class 12 25 * *
insulation_purpose 14 26 * *
insulation_thick 15 28 *
insulation_thick_units -1 29
insulation_density 16 30 * *
insulation_density_units -1 31
heat_tracing_reqmt 17 73 * *
heat_tracing_media 18 74 * *
heat_tracing_temp 19 75 * *
heat_tracing_temp_units -1 76
construction_stat 20 60 * *
hold_status 21 83 * *
schedule_override 23 66 *

nor_oper_pres 24 39 *
nor_oper_temp 25 41 *
alt_oper_pres 26 43 *
alt_oper_temp 27 45 *
nor_dgn_pres 28 47 *
nor_dgn_temp 29 49 *
alt_dgn_pres 30 51 *
alt_dgn_temp 31 53 *
steam_outlet_temp 32 86 *
mater_of_construct 33 61 *
safety_class 34 59 *
design_resp 37 69 *
construction_resp 38 78 *
supply_resp 39 71 *
coating_reqmts 40 72 *
cleaning_reqmts 41 77 *
fluid_category 42 84 *
nor_op_pres_units 43 40 *
nor_op_temp_units 44 42 *
alt_op_pres_units 45 44 *
alt_op_temp_units 46 46 *
nor_dgn_pres_units 47 48 *
nor_dgn_temp_units 48 50 *
alt_dgn_pres_units 49 52 *
alt_dgn_temp_units 50 54 *
steam_temp_units 51 87 *
test_system_no 64 55 *
test_fluid 65 56 *
test_pressure 66 57 *
### Data extracted from the Piping Segment Table ( piping_seg, 112 ) of the P&ID Design Database:
# upstrm_node_no
pid_node_number_a - 10
# dwnstrm_node_no
pid_node_number_b - 11
flow_direction - 14
# line_no_label
line_number_label - 21
# dwg_occ_no
drawing_segment_index_no - 3
line_id - 12
# piping_thk_flag
piping_thickness_flag - 68
### Data extracted from the Equipment Table ( eq_group, 106 ) of the P&ID Design Database:
equipment_number - 7
### Data extracted from the Equipment Nozzle Table ( eq_nozz, 108 ) of the P&ID
Design Database:
nozzle_number - 5
# pid_seg_occ_no
nozzle_segment_index - 4
# eq_grp_occ_no
equipment_nozzle_index - 2
# node_no
equip_nozzle_node_no - 13
### Data extracted from the Piping Component Table ( piping_comp, 120 ) of the P&ID Design Database:
#piping_comp_table is the delimiter to signal the information below belongs to

# P&ID’s piping_comp table and Piping’s pdtable_34_<partition_number>.
# piping_comp_table signals that the following attributes belong to pdtable_34.

piping_comp_table
piping_comp_number 2 6
aabbcc_code 3 9
commodity_code_flag - 28
cmdty_code 8 29
# opt attribute in P&ID is placed into the option_code attribute in Piping
commodity_option_code 5 27
# pid_seg_occ_no
comp_segment_index_no - 3
# dwg_occ_no
comp_drawing_index_no - 2
# generic_tag_no
specialty_generic_tag_no - 44
#any attributes you desire to transfer (beyond those defined above) are listed
# here. You determine which are transferred between P&ID piping_comp table
# and piping pdtable_34. NOTE: Complete, partial and default do NOT
# apply to these attributes.
#attribute name (any thing) piping attr no p&id attr

no
const_status 32 23
heat_tracing_media 35 34
heat_tracing_reqmts 34 33
hold_status 33 41
ht_tracing_media_temp 36 35
opening_action 31 17
remarks 46 20
### Data extracted from the Instrument Component Table ( instr_comp, 131 )of the P&ID Design Database
#instr_comp_table is the delimiter to signal the information below belongs to
# P&ID’s instr_comp table and Piping’s pdtable_67_<partition_number>.
# instr_comp_table signals that the following attributes belong to pdtable_67.
instr_comp_table
instrument_tag_number - 5
# pid_seg_occ_no
instr_segment_index_no - 4
# aabbcc_code
instr_aabbcc_code - 10
# dwg_occ_no
instr_drawing_index_no - 3
#generic_tag_no
instr_generic_tag_no - 80
#any attributes you desire to transfer (beyond those defined above) are listed
# here. You determine which are transferred between P&ID instr_comp table
# and piping pdtable_67. NOTE: Complete, partial and default do NOT
# apply to these attributes.
#attribute name (any thing) piping attr no p&id attr no

cleaning_reqmts 39 60
const_resp 32 35
const_status 29 24
dgn_resp 31 25
fail_action_1 28 56
heat_tracing_media 34 28
heat_tracing_reqmts 33 27
hold_status 30 40
ht_tracing_media_temp 35 29
insulation_purpose 36 31
insulation_thick 37 33

module_no 41 36
package_system_no 42 38
remark_2 52 22
safety_classification 40 20
### Data extracted from the Drawing Table ( dwg, 102 ) of the P&ID Project Database:
drawing_number - 3
#unit_occ_no
unit_index_number - 2
drawing_title - 16
network_address - 7
path_name - 8
file_specification - 5
propagation_status - 10
approval_initials - 21
approval_date - 22
revision_id - 27
for_comments_date - 29
for_design_date - 30
for_construct_date - 31
task_name - 4
### Data extracted from the Unit Table ( unit, 101 ) of the P&ID Project Database:
unit_number - 4
unit_code - 3
unit_name - 5
### Data extracted from the Task RDB Table ( task_rdb, 98 ) of the P&ID Project Database:
pid_task_name - 2
pid_task_rdb_node - 3
pid_task_rdb_path - 4
### Data extracted from the PID Segment Table ( pid_seg, 110 ) of the P&ID Design
Database:
# net_type_occ_no
piping_segment_index_no - 4
### Data extracted from the PID Drawing Revision Data Table ( dwg_rev_data,
### 103 ) of the P&ID Design Database includes the following:
dwg_occ_no - 2
### Data extracted from the Piping Connector Table (piping_connector, 124) of
### the P&ID Design Database includes the following:
connector_no - 4
#dwg_occ_no of the piping connector table
connect_dwg_occ_no - 2
#pid_seg_occ_no of the piping connector table
connect_pid_seg_occ_no - 3
#matching_criteria is the criteria to be used for matching the P&ID and Piping
#segments together. Nodea (piping attribute 67) and Nodeb (piping attribute 68)
#are the default criteria. The matching criteria is defined by listing the
#piping attribute numbers separated by a space on the line below.

matching_criteria 67 68
#search_mode is the method for searching for the matching criteria. The default
#is ’FIRST’ - stop on the first match found. The other option is ’END’ which
#means to search the entire database looking for a match. If more than one match
#is found, the software evaluates all of the matches for an exact match of the
#transfer data.
search_mode FIRST

#exclusion_criteria has been a part of the submission process in the past. We
#have added the capability to default this value. Values are ’YES’ for do not
#check the transfer disabled segments and ’NO’ to check the transfer disabled
#segments. This option can still be modified at submission.
exclusion_criteria YES
P&ID Graphical Data Transfer Setup

You can select and view an active P&ID while working in a piping model. This enables the
graphical transfer of piping segment data by snapping to graphics in the active P&ID. You can
also specify a component name for placement by selecting a component in the P&ID.
You can use the following options to select the active P&ID to be displayed. Only one P&ID can
be active for the purposes of data transfer.
 You can select a drawing from a list of P&IDs extracted from the Project Control Database.
This list of drawings is limited to those P&IDs which have been propagated for the active
unit number in the piping model. The applicable drawings are listed in alphanumeric order
by drawing number.
Since the P&ID Database is unit dependent and the Piping Design Database is design area
dependent, one Piping design area may include data from different P&ID units. Therefore,
you must specify the correct unit number in the active segment data prior to requesting a list
of P&I drawings from the P&ID Database.
 Select P&I Drawing by Line ID - You can specify a line ID by identifying piping in the piping
model or by accepting the active line id. The system determines the P&ID (or list of
drawings) from the line id. It searches the Segment Table of the P&ID Database using the
system unique number for the drawing and the line ID for the segment.
 Select P&I Drawing by Nozzle - You can specify an equipment number and nozzle number
by locating a component connected to a nozzle, by keying in an equipment number and

nozzle number, or by snapping to a nozzle in an equipment model. The system determines

the P&ID from the equipment number and nozzle number and data in the P&ID Database.
You can use the Review P&I Drawing Details option to display information about a selected
P&I Drawing in the active unit.
Once you select a drawing by any of the described methods, the P&I drawing and the
corresponding drawing border are attached as reference files.
A selected screen view is used to display the P&ID. The system stores this view number in the
Type 63 data for the piping model.

P&ID Node Numbers

When piping segment data is transferred from the P&ID Database to the piping model, the P&ID
node numbers derived from that database are reflected in the model as a form of associativity
between the P&ID and the piping model. The following rules dictate how P&ID node numbers
are assigned during the creation of piping segments in the model.
 Transferring piping segment data from the P&ID Database by any means results in the P&ID
node numbers being stored with the piping segment that is to be created by either the Place
Component or Sketch command.
 If you continue creating new piping segments in the model, either by explicitly placing a
piping segment or by placing a component that results in the placement of a piping segment,
the new piping segments continue to include the P&ID node numbers from the initial piping
segment.
 If, at any time, you update the piping segment data manually with the Active Segment Data
option, the P&ID node numbers for the subsequent piping segment is assigned as undefined
(blank).
Using the First Size or Second Size option to place a reducing component will not result in
the P&ID node numbers being assigned as undefined unless you also use the Active
Segment Data option.
 If you place a component after specifying the active placement point with the Connect to
Design option, the P&ID node numbers for the subsequent piping segment is derived from
those of the connected piping.
 The P&ID node numbers are assigned as undefined when you connect to a nozzle, unless
the active segment data is then updated from the P&ID Database.
 If you place a component after specifying the active placement point with the Point in
Space option, the P&ID node numbers for the subsequent piping segment is assigned as
undefined (blank).
 If, in the Sketch command, you place a piping segment after specifying the active
placement point with the Construct Point option, the P&ID node numbers for the
subsequent piping segment are assigned as undefined (blank).

Update Segment Data from P&ID

You can update the active segment data by node number, by equipment/nozzle ID, or by
snapping to graphics in the active P&ID.
You can specify that the piping segment data transfer be complete or partial on the basis of the
Correlation Table. The default mode is complete, and once the piping segment has been
created in the model the active mode is restored to complete. In other words, the next operation
will revert to complete data transfer, unless you explicitly select partial data transfer.
A warning message is displayed if any one of the following conditions occurs in the process of
loading the active data from the P&ID Database.
 The piping materials class from the P&ID Database is undefined in the Reference Database
 The nominal piping diameter from the P&ID Database is invalid for the piping materials class
from the P&ID Database on the basis of the NPD Table in the Piping Specification Table
Library
 The active nominal piping diameter is invalid for the piping materials class from the P&ID
Database on the basis of the NPD Table in the Piping Specification Table Library in partial
data transfer, where nominal piping diameter is not loaded
 The fluid code from the P&ID Database is invalid for the piping materials class from the
P&ID Database on the basis of the Fluid Code Table in the Piping Specification Table
Library for a piping materials class where a Fluid Code Table is applicable

Update by Node Number

You can update the active segment data by specifying two P&ID node numbers. This option is
provided in both the Place Component and Sketch commands. You can accept both or either
of the two active (previously specified) P&ID node numbers.
The P&ID Database is referenced using the P&ID project number. A single table is read from
this database using unit number, P&ID node number 'A', and P&ID node number 'B'. Since the
P&ID Database is unit dependent and the Piping Design Database is design area dependent,
one Piping design area may include data from different P&ID units, each unit being designated
by a unique unit number.
The order of the P&ID node numbers, as specified by the user, determines the assignment of
flow direction in the piping model. By convention, P&ID node number 'A' is at the Active
Placement Point. As a part of the data transfer process, the P&ID node numbers are stored in
the piping model for subsequent use and to retain the associativity between the segment in the
P&ID Database and the segment(s) in the piping model. Likewise, the unique index into the
P&ID segment table is stored in the piping model in order to enable the later comparison and
update of P&ID node numbers from the P&ID Database into the piping model. It is possible that
the P&ID node numbers may be changed by the P&ID propagation process for a specific
segment in the P&ID Database as a result of changes to the P&ID.
Transfer by Equipment Number and Nozzle Number

You can update the active segment data by specifying an equipment number and nozzle
number. If you are actively connected to a nozzle in the model, this option automatically
searches the P&ID Database using the 'active' equipment number and nozzle number.
Otherwise, you must either snap to the appropriate nozzle or key in the equipment number and
nozzle number for the appropriate nozzle. This option is provided in both the Place Component
and Sketch commands.
The system accesses the P&ID Database using the P&ID project number. A single table is read
from this database using the unit number, the equipment number, and the nozzle number.
The assignment of flow direction in the piping model is determined by the flow direction at the
nozzle end of the segment in the P&ID. As a part of the data transfer process, the P&ID node
numbers determined from reading the segment table in the P&ID Database are stored in the
piping model for subsequent use and to retain the associativity between the segment in the
P&ID Database and the segment(s) in the piping model. Likewise, the unique index into the
P&ID segment table is stored in the piping model in order to enable the later comparison and
update of P&ID node numbers from the P&ID Database into the piping model. It is possible that
the P&ID node numbers may be changed by the P&ID propagation process for a specific
segment in the P&ID Database as a result of changes to the P&ID.

Update From Active P&I Drawing

You can update the active segment data by snapping to graphics in the active P&ID. The
system reads a single table from the P&ID Database using the unit number and the attribute
linkage from the segment in the P&ID.
If you identify a component in the P&ID that is associated with more than one segment, such as
a reducer, the active segment data is derived from the segment associated with the connect
point nearest the identification point.
The order of the P&ID node numbers determines the assignment of flow direction in the piping
model. By convention, P&ID node number A is at the Active Placement Point. As a part of the
data transfer process, the P&ID node numbers are stored in the piping model for subsequent
use and to retain the associativity between the segment in the P&ID Database and the
segment(s) in the piping model. The unique index into the P&ID Segment Table is also stored in
the piping model to enable the comparison and update of P&ID node numbers from the P&ID
Database into the piping model. The P&ID node numbers may be changed by the P&ID
propagation process for a specific segment in the P&ID Database as a result of changes to the
P&I drawing.

P&ID Data
Revise Attributes
You can update the data for a previously placed piping segment using the Revise Attributes
command, by specifying two P&ID node numbers.
The order of the input of the two P&ID node numbers is used to control the assignment of flow
direction in the piping model. P&ID node number 'A' is associated with 'end 1' of the segment,
while P&ID node number 'B' will be associated with 'end 2'.
As with the previously described option, the piping segment data will be updated based upon the
Correlation Table. Likewise, the user has the option to specify that the piping segment data
transfer is to be complete or partial on the basis of the Correlation Table. You can also update
the data for a previously placed piping segment by snapping to graphics in the active P&ID.
Attribute Break
You can load the piping segment data for an attribute break, using the Attribute Break
command, by specifying two P&ID node numbers.
The order of the input of the two P&ID node numbers is used to control the assignment of flow
direction in the piping model. P&ID node number A is associated with the end of the piping
segment being placed at the attribute break's location, while P&ID node number B is associated
with other end of the piping segment being placed.
Under user control, the revised piping segment will retain the existing piping segment data,
including the P&ID node numbers. The new piping segment is created from the original piping
segment with data being transferred from the P&ID Database using those P&ID node numbers
specified by the user. This piping segment is created with the 'new' P&ID node numbers.
As with the previously described option, the piping segment data is updated based upon the
Correlation Table. Likewise, the user has the option to specify that the piping segment data
transfer is to be complete or partial on the basis of the Correlation Table. You can also load the
piping segment data for an attribute break by snapping to graphics in the active P&ID.
Name From P&ID

You can use the Name From P&ID option on the Place Component form to select the piping or
instrument component to be placed by identifying a component in the P&ID. It retrieves the
piping commodity name for a piping commodity, the piping component number for a piping
specialty, or the instrument component number for an instrument for use in reading from the
Reference Database. No other component data is read from the P&ID database.

P&ID Data Comparison Options

The P&ID Data Comparison Options command is provided as part of the Diagnostics
command for the purpose of specifying the data comparison option for piping segments in the
model. You have two options with this command.
 the ability to mark a piping segment to have segment data comparisons inhibited (or
enabled) in the P&ID Data Comparison Report. This option is intended to assist the user by
not reporting extraneous piping segments which do not exist in the P&ID Database and
have not been assigned P&ID node numbers in the piping model, i.e. segment data has not
been transferred from the P&ID database. Note that the default mode for all piping
segments created in the model is to have P&ID data comparisons enabled. Thus it is not
necessary for the user to take any action to enable P&ID data comparisons, unless the user
had previously and inadvertently designated that P&ID data comparisons be inhibited for a
particular piping segment.
 a rules-based command for the purpose of automatically marking piping segments
corresponding to vents, drains, and off-line instrument connections for being optionally
ignored in P&ID data comparisons. The option is intended to assist the user by not reporting
extraneous piping segments which may not exist in the P&ID Database and usually are not
assigned P&ID node numbers in the piping model.
These piping segments representing vents, drains, and off-line instrument connections are
marked in the user data of the piping segment. Such designations will only have an impact,
if the user chooses to have these piping segments excluded from the P&ID Data
Comparison Report.
The limit for the maximum number of vent/drain valves and instrument connections that can
be processed in one piping model is 200 for each (expanded from 100).

SECTION 7
SmartPlant P&ID to PDS Piping Data
Transfer
Transferring Piping Data

Piping data defined in SmartPlant® P&ID can be transferred to PDS® using the SmartPlant
P&ID to PDS Piping Data Transfer capability. The ability to transfer PDS P&ID data to PDS 3D
is documented in the PDS documentation and is therefore not covered here.
Piping System Schematic and Physical Representations

Although both SmartPlant P&ID and PDS describe the same plant, a one-to-one
correspondence between the components in the two models does not always exist. SmartPlant
P&ID to PDS piping data transfer is essentially the transfer of data from the SmartPlant P&ID
segment table to the PDS piping segment table, pdtable_12_xx.
The conceptual definition of a segment is the same in both applications, however that does not
mean that there is a one-to-one correspondence between these two tables. For example, the
number of segments is not the same, even if the SmartPlant P&ID and PDS piping model
exactly match from a design point of view. This situation is caused by the different drafting
practices of SmartPlant P&ID and PDS. For example, drains are shown as macro symbols on
the SmartPlant P&ID drawing. However, drains are branch segments in the PDS model. Also,
process connections to instruments are recorded as instrument signal lines in the SmartPlant
P&ID database, but on the PDS side, process connections are piping segments.
Due to these differences, the data transfer process requires establishing a logical link between
the corresponding segments. This linkage can either be in the form of interactive input from the
PDS designer, who can choose a piping segment in a drawing by clicking it, or be a combination
of attributes defined as unique criteria in the SPTransferOpt file. For more information on
attribute mapping, see Mapping Attributes.
Data Transfer in the Real World

When you model a new line in PDS, use the Data from P&ID option, and then click a
SmartPlant P&ID segment. By doing this, you are establishing the logical link. After this link is
established, future data transfers can be fully automated.
However, as with most plants, there is a time when SmartPlant P&ID drafting and PDS modeling
continues in parallel. The P&IDs are changing while piping modeling continues in PDS. When
the designer models a particular pipeline, the equivalent SmartPlant P&ID segments may not yet
exist in the SmartPlant database, creating a significant amount of piping that does not have the
associative link between SmartPlant P&ID and PDS. This is just one example of how creating
and updating links is an ongoing process rather than a one-time effort. For more information
about maintaining links between SmartPlant and PDS, see Creating and Maintaining Links.

SmartPlant P&ID to PDS Piping Data Transfer
Installation
You can set up SmartPlant P&ID using a full installation. Full installation works with the full
SmartPlant P&ID Installation on the local computer.
For details of supported SmartPlant P&ID software versions, see the SmartPlant P&ID
Installation and Upgrade Guide > Hardware and Software Recommendations.
 Piping Data Transfer capability is supported for PDS 8.0 or higher.

If you have a customer ID and password, you can access the latest compatibility matrix that
explains which Intergraph software is compatible with each operating system, on the Intergraph
Smart Support web page (https://smartsupport.intergraph.com).
Install Oracle
1. Start Oracle Database Configuration Assistant, select the Local Net Service Name
configuration option from the list, and click Next.
2. Click Add, and then click Next.
3. In the Service Name box, type the oracle SID name of the SmartPlant database. Click
Next.
4. In the protocol form, accept the default TCP option. Click Next.
5. In the Host Name box, type the P&ID site server name. Accept the default port number
1521. Click Next.
6. Click Yes to perform the test, and then click Next.
7. To test the service, click Change Login and specify a valid username/password
combination of the SmartPlant database, and then click OK. You should see the
Connecting...Test successful message. Click Next.
8. In the Net Service Name box, type the name of the database alias to use for the data
transfer. The Net Service Name must be exactly the same as it was defined in the
SmartPlant database server. Click Next three times, and then click Finish.
Install SmartPlant Engineering Manager
 You need to install SmartPlant Engineering Manager 2009 SP 2. Loading SmartPlant

Engineering Manager creates an entry in the system PATH variable. For example,
"..\..\SmartPlant\Engineering Manager\Program;".
 If you are reinstalling SmartPlant Engineering Manager, you must first use the Add/Remove
Programs Control Panel application to remove the previous SmartPlant Engineering
Manager installation.
 Be sure to apply all available SmartPlant Engineering Manager service packs for the version
you are installing. For more information, please contact Intergraph Customer Support.

 If you need to install SmartSketch® on the same computer, be sure to install it first. If you
require SmartSketch for PDS 9.0 (for example, for the pipe support explorer), SmartSketch
2007 SP 5 is the compatible version.
1. Insert the product CD into the CD-ROM drive. If the installation does not start automatically,
double-click setup.exe in the main folder.
2. Click SmartPlant Engineering Manager Installation.
3. Click Next to start the installation wizard.
4. Type your User Name, Company Name, and Serial Number, then click Next.
5. Verify your Name, Company, and Serial Number, then click Yes.
6. Click Display to view and read the license agreement. You must have a PDF reader
installed to be able to view the Software License Agreement.
7. Close the Software License Agreement window, and then click Yes to accept the license
agreement.
8. Specify the Destination Folder, then click Next.
9. Verify that the appropriate components are selected, then click Next.
If you want to upgrade your SmartPlant Engineering Manager data, be sure you select
Upgrade Utility to install the SmartPlant Engineering Upgrade Utility. For more information,
see Using the SmartPlant Engineering Upgrade Utility in the SmartPlant P&ID Installation
Guide.
10. Accept the default Program Folders or select a new Program Folder name, then click
Next.
11. Review your Current Settings, then click Next to install SmartPlant Engineering Manager.
12. Click Finish to close the installation wizard.
For more information on full installation of SmartPlant Engineering Manager, see The
SmartPlant P&ID Installation Guide.
Install SmartPlant P&ID

If you need to install SmartSketch® on the same computer, be sure to install it first.
If you require SmartSketch for PDS 9.0 (for example, for the pipe support explorer),
SmartSketch 2007.5 is the compatible version.
SmartPlant P&ID Full Installation

1. Insert the SmartPlant P&ID CD into the CD-ROM drive. If the installation does not start
automatically, double-click setup.exe in the main folder.
2. Click SmartPlant P&ID Installation.
3. Click Next to start the installation wizard.
4. Type your User Name, Company Name, and Serial Number, then click Next.
5. Verify your Name, Company, and Serial Number, then click Yes.
6. Click Display to view and read the license agreement. You must have a PDF reader
installed to be able to view the Software License Agreement.

7. Close the Software License Agreement window, and then click Yes to accept the license
agreement.
8. Specify the Destination Folder, then click Next.
9. Verify that the appropriate components are selected, then click Next.
10. Accept the default Program Folders or select a new Program Folder name, then click
Next.
11. Review your Current Settings, then click Next to install SmartPlant P&ID.
12. Click Finish to close the installation wizard.
For more information on full installation of SmartPlant P&ID, see The SmartPlant P&ID
Installation Guide.
Test the SmartPlant Connection

If you chose the full installation of SmartPlant P&ID, then you can test the connection with a
plant structure that is already configured.
1. Click Start > Programs > Intergraph SmartPlant P&ID > Drawing Manager.
2. Click File > Open Database.
3. Click Site Servers and browse to a SmartPlant initialization (.ini) file.
4. Select the file and click OK.
5. Select the plant structure in the Open Plant Structure dialog box.
6. Click Open, and the selected plant with its drawings appears in the Drawing Manager view.
If you experience problems connecting to the SmartPlant P&ID site or getting into the
plant structure, verify that the site server is running and ask the SmartPlant P&ID administrator
to set the PDS 3D users as SmartPlant P&ID administrators during this configuration. You need
administrator privileges until you start doing restrictions per plant structure. SmartPlant P&ID
permissions are handled in SmartPlant Engineering Manager.
Creating and Maintaining Links

Understanding the SmartPlant P&ID to Piping Data Transfer process during PDS project
execution helps you make the most of the benefits offered by this feature. Careful use of the
procedures in this document, combined with delta training for piping designers and other
personnel, produces considerable time savings as opposed to manually checking P&ID against
PDS piping data. If you would like to use this feature but need help, Intergraph Process, Power
& Marine offers consulting services to guide you. For more information, see the Customer
Support links on the About SmartPlant P&ID dialog box.
The key factor in these benefits is creating and maintaining links between the SmartPlant P&ID
and the PDS segments. The following flowchart shows the workflow for resolving data transfer
discrepancies during the plant design.

PDS Design Considerations

 Use the Data from P&ID command often while routing new piping in PDS.
 When creating a pipeline by copying existing piping, use the Revise Attribute > Update
from P&ID command to load the data from SmartPlant P&ID.
 When creating a branch using an existing segment or pipe, check whether the branch is
shown in SmartPlant P&ID. If it is shown, then use the Revise Attribute > Update from
P&ID command to load the data from SmartPlant P&ID.
 Verify that the Partial P&ID Data Transfer option at the end of the Segment Attribute list is
selected. You can change this value by using the Revise Attribute command. Default
transfer modes are set such that during a partial transfer all diameter- independent
properties are transferred. This option allows the drain to share the line sequence number,
pressure, temperature, and so forth, with the header and still have a different diameter and
line number label. This action is controlled in the SPMap.mdb file.

 Instrument connections or drains on equipment with no equivalent segment in SmartPlant

P&ID, can be excluded from future comparison reports. Simply select the Inhibit Future
Transfer option when you review a comparison report error related to these segments.
Synchronizing P&ID and Piping Data

Synchronizing SmartPlant P&ID and PDS piping data should be done only a few times during
plant design. The best times to synchronize are when the majority of the P&IDs are completed,
revised, or issued. This synchronization involves running a P&ID Segment Data Comparison
Report and then resolving any discrepancies and helps to build the association between
SmartPlant and PDS that is then maintained throughout the plant lifetime.
This synchronization involves running a P&ID Segment Data Comparison Report and then
resolving any discrepancies, and is outlined in the flowchart above.
Running a Segment Data Comparison Report

Running a Segment Data Comparison Report is the starting point on the flowchart. The results
of this report depend on two key factors:
 The matching criteria defined in the SPTransferOpt file in the plant directory. For more
information, see Map an Ignored Attribute (on page 197) or Map an Unmapped Attribute (on
page 198).
 The Compare Segment with Node Numbers/Compare All Segments setting.
While running this report, the Compare All Segments setting should be used, and matching
criteria should be node numbers.
Based on the availability of P&IDs during the initial piping design stage, the number of
discrepancies can be very high on the first run. Our experience shows that a piping designer,
who has good knowledge of the piping involved and the related P&ID, takes approximately two
to four minutes to resolve a discrepancy. Successive uses of this procedure should reduce the
numbers of discrepancies. If plant design resources or time do not allow resolving all
discrepancies, then you should consider alternative methods to running the Segment Data
Comparison Report.
One alternative is to change the matching criteria. Matching criteria directs the software to
establish associations between SmartPlant P&ID and PDS piping segments based on the value
of the attributes specified. For example, the default criteria of node numbers means that node
numbers for a PDS piping segment must match with a P&ID segment. If the SmartPlant P&ID to
PDS Piping Data Transfer has not been done for a piping segment, then no node number is
defined for that segment. This situation generates a Node Numbers Undefined only
discrepancy. If the majority of the piping falls under this category, then the number of
discrepancies can be very high. To reduce this number, change the matching criteria to
something other than node numbers. Typically, any of the individual properties of a line
number label such as NPD, line sequence number, insulation purpose, and so forth, can be
used. It is better to use as many properties as possible so that they form a unique combination.
All properties specified as matching criteria should have some value assigned to them on both
sides.
Another alternative to running the comparison report is to specify segment search criteria. This
method can be used if all instrument connections on equipment or drain lines not shown on the
P&ID contain common attributes such as different fluid codes or prefixes to line sequence
numbers, and so forth.

Another possibility is to use a range of diameters so that small diameter segments can be
eliminated.
Establish a SmartPlant/PDS Link
 When setting up data transfer for multiple plants, if the PDS 3D and SmartPlant P&ID
plants have the same set of properties and the same intended mapping, then you can
copy the SPMap.mdb file from one plant to another. The Attribute Mapper always
verifies that the SmartPlant site in the .mdb file is the same as the map for the selected
PDS project. However, if you are not sure if the plants have the same set of properties,
we recommend that you copy the delivered SPMap.mdb file from the PDSHELL\pid\
folder.
 For a project where data transfer was set up to work with an earlier version of
SmartPlant P&ID, some attribute mappings have changed. You can use either the new
SPMap.mdb file delivered in the PDSHELL\pid\ folder or follow the procedure mentioned
for CR32693 in the PDS README file.
 Even if you are going to work with the default attribute mapping, you must start
SmartPlant Attribute Mapper at least once. If necessary, you can back up the updated
SPMap.mdb file, delete the changes, and copy a fresh SPMap.mdb to go through the
mapping process again.
1. Copy \WIN32APP\INGR\PDSHELL\pid\SPMap.mdb and SPTransferOpt to the PDS project
directory. For projects created with version 6.4.1 or later, these files are copied automatically
from the PDSHELL\pid folder at the time of project creation.
2. Click Start > Programs > PD_Shell > SP PID to PDS 3D to display a list of available PDS
projects.
 The software reads the list of PDS projects from the PDS proj_file.
 The Attribute Mapper does not honor any other variables defined in the pds.cmd file,
such as RIS parameter file locations, and so forth.
3. Double-click the PDS project to use with SmartPlant P&ID and locate the SmartPlant
initialization (.ini) file.

The SmartPlant Migrator for P&ID utility opens and shows the PDS attributes for the
selected project.
The location of the SmartPlant initialization (.ini) file must be specified using a
complete UNC path. If path to this .ini file is mapped on a network drive and the mapped
network drive path is used to locate it, this results in errors.
 After a relationship between attributes is established, the SmartPlant Attribute Mapper

opens. The link between the SmartPlant P&ID plant and the PDS 3D project is established
and updated automatically in the SPMap.mdb file. For the attribute mapper to run properly,
the following path to SmartPlant Engineering Manager must be added to the system PATH
environment variable:
"..\..\SmartPlant\Engineering Manager\bin"
 For more information about mapping attributes, see Map an Unmapped Attribute (on page
198) or Map an Ignored Attribute (on page 197).

Revising Linked Models

Modification in SmartPlant P&ID
The SmartPlant P&ID software generates node numbers during consistency checking. If existing
segments on the P&ID are modified, then those node numbers may also be modified. This
situation occurs when placing either a branch on an existing segment or a segment break,
causing the link between SmartPlant P&ID and PDS to become outdated. In most cases,
changes in SmartPlant P&ID mean changes in the piping model. Resolving this type of
discrepancy improves the integrity of the design data.
Modification of a PDS Model

Physical modification of segments with PDS commands such as Move Piping, Move Vertex,
Move Pipeline End, and so forth, do not affect SmartPlant P&ID to PDS Piping Data Transfer.
All branch component placement commands break the segments and potentially lose links with
SmartPlant. While placing drain connections, which are not shown on P&IDs, it is better to use
the Revise Attributes > Load from P&ID command on the header segment before placing the
drain connection or branch components. Then all three segments are linked with the proper
segment in SmartPlant P&ID. After creating the branch drain segment, make sure that the P&ID
to Piping Transfer mode attribute is set to Partial for the branch segment. Transfers done after
placing a drain require that you use the Revise Attribute command three times.
Mapping Attributes_WRAPPER
SmartPlant P&ID to Piping Data Transfer relies on an attribute map stored in a Microsoft Access
database located in the PDS project folder. This map database file is named SPMap.mdb, and
contains information about the Smart Plant P&ID site server and plant. The Attribute Mapper
utility is used to manipulate this map database. The Attribute Mapper is started from a shortcut
provided in the PD_Shell program group named SP PID to PDS 3D.
The Attribute Mapper utility maps, un-maps, or ignores attributes between PDS 3D and
SmartPlant P&ID. The Attribute Mapper interface is similar to Windows Explorer in that it
displays a tree view on the left side and list view on the right side. Attributes for piping segment,
piping component, and instrument tables from the PDS 3D design database are available to
map with corresponding SmartPlant P&ID tables, specifically the PipeRun, PipingComp and
Instrument tables.
The tree view divides attributes into four categories based on map status: Mapped, Unmapped,
Ignored, and All. For SmartPlant P&ID to PDS 3D data transfer, the Ignored map status is the
same as the Unmapped status.
The Default Map

PDS software includes a default map in the PDSHELL\pid folder. This map has a set of
attributes that are pre-mapped with known SmartPlant P&ID properties. When you create a new
project using PDS software, this map is copied to the project folder. For older projects, the
SPMap.mdb file should be manually copied from the PDSHELL\pid folder into the 3D project
folder.
The default map is functionally equivalent to the pid_to_piping file used for PDS 2D to 3D
data transfer with a few exceptions. For example, units are not required to map because of the
way unit information is stored. This applies to attributes like pressure and temperature. The

SPTransferOpt file includes the three options that you can find at the bottom of the pid_to_piping
file. For PDS 2D to PDS 3D data transfer, the mapper specifies the database attributes that are
considered in order to perform the data transfer. By default, for PDS 2D transfer the mapper is
mapping NodeA (piping attribute 67) and NodeB (piping attribute 68). For SmartPlant P&ID to
PDS 3D data transfer, because there are no node numbers in SmartPlant, the mapper is
mapping piping attribute sppid_piperun_guid (piping attribute 78).
Select Lists
Select-listed SmartPlant P&ID properties are transferred based on their text value instead of
number. The Attribute Mapper creates a map of PDS codelist entries for every SmartPlant select
list used in the mapped properties.
For example, fluid code "P" is represented by the PDS 3D codelist entry 25 and by entry 35 in
the SmartPlant P&ID select list. When the fluid code property is transferred, the property value
changes from 35 in the SmartPlant database to attribute value 25 in the PDS Database. This
functionality has removed the requirement of maintaining the same select list and codelist
values in SmartPlant P&ID and PDS 3D.
Map an Ignored Attribute

This procedure includes only the major steps involved in mapping an attribute. Refer to PDS
Online Help or documentation for detailed instructions.
1. Open the SmartPlant Migrator for P&ID utility. For more information, see Establish a
SmartPlant/PDS Link (on page 194).
2. Select the Ignored category.
3. Select the table in the tree view.
4. Select a PDS attribute in the list view.
 Properties mapped with the Transfer Mode option set to Partial are transferred when you
use the Partial Data Transfer toggle within PDS.
 Properties mapped with the Transfer Mode option set to Default receive the default value,
which you enter in the Default box, during partial data transfer.
 Properties mapped with the Transfer Mode option set to No Default do not get a default
value and do not get transferred during partial data transfer.
 All Mapped properties are transferred during complete data transfer.

Map an Unmapped Attribute

This procedure includes only the major steps involved in mapping an attribute. Refer to PDS
Online Help or documentation for detailed instructions.
1. Open the SmartPlant Migrator for P&ID utility. For more information, see Establish a
SmartPlant/PDS Link (on page 194).
2. Expand the Unmapped category.
3. Select the table in the tree view.
4. Select a PDS attribute in the list view.
 Properties mapped with the Transfer Mode option set to Partial are transferred when you
use the Partial Data Transfer toggle within PDS.
 Properties mapped with the Transfer Mode option set to Default receive the default value,
which you enter in the Default box, during partial data transfer.
 Properties mapped with the Transfer Mode option set to No Default do not get a default
value and do not get transferred during partial data transfer.
 All Mapped properties are transferred during complete data transfer.
Segment Data Comparison Report

The software compares segment data on the basis of the matching criteria defined in the
SPTransferOpt correlation table. If no matching criteria are defined, the software compares
segment data on the basis of the SmartPlant P&ID node numbers that are common to both the
SmartPlant database and the PDS database, or the node numbers and line number labels,
depending on what you specify using the available options.
The piping segment data is also compared on the basis of the Complete or Partial data transfer
options.
If a match is found, each attribute value, as specified in the SPMap.mdb correlation table and
filtered for either complete or partial data transfer, is compared with the corresponding property
value in the SmartPlant database. For any pair of corresponding attribute values that differ, the
discrepancy is reported in the Segment Data Comparison Report.
This report includes a comparison of the flow direction for the PDS piping segment and the
SmartPlant P&ID segment by using the P&ID node numbers. If no corresponding segment is
found in the SmartPlant database for a PDS piping segment with valid matching criteria, an error
is reported.
If the search mode is set to END in the SPTransferOpt file, the software compares all of the
SmartPlant P&ID segments that have matching search criteria to the applicable PDS piping
segment and uses the SmartPlant P&ID segment that best matches the PDS piping segment for
the comparison. Otherwise, the search mode is FIRST, and comparison is made with the first
P&ID segment that has matching criteria.

 The Segment Data Comparison Report also includes line sequence numbers.
 Because the data comparisons are performed on the basis of the PDS piping segments, not
all segments in the SmartPlant database are checked for matches.
The software creates the following files in the same directory location as the processed model
file:
 A report file named model_number.pc (model_number is the number of the model that is
extracted from the PDS Project Database).
 A non-printable, sorted file named model_number.pci (this file is used by the Review P&ID
Comparison Report command).
 A non-printable, sorted file named model_number.pca (this file is used by the P&ID Data
Comparison, Update Model, Segment Data Comparison Report, and Review P&ID
Comparison Report commands for the approval of data discrepancies. The .pca file is
initially created when you approve a discrepancy, and the file is appended to with each
additional approval).
You can format the title page and the heading for each page of the Segment Data Comparison
Report using the \win32app\ingr\pddesign\sample\pid_cmprpt.fmt format file. The remainder of
the report is in the following format:
<line number> <P&ID Node Numbers> <P&ID Drawing Number>
Attribute Value in Model Value in P&ID
line_number_label 2"A-A5A2F-N- 55011 2"A-A5A2F-P- 550107
line_sequence_no 550111 550107
insulation_purpose N P
Data in the Segment Data Comparison Report is sorted first by line number label and then by
the SmartPlant P&ID node numbers, if applicable.
Choosing Data Transfer Options

Matching Criteria
PDS uses matching criteria to generate the Segment Data Comparison report. In order to
compare segment records, the records must first be matched or correlated. Matching criteria
defines the correlating attribute in the PDS 3D database. The default attribute map reserves the
pid_index_no attribute for matching criteria. This fact means that the Segment Data Comparison
report compares piping segment attributes from the PDS and SmartPlant databases if the
pid_index_no in the PDS database matches the unique sp_id in the SmartPlant database.

SmartPlant P&ID
Consider the following points when planning for data transfer from a SmartPlant P&ID plant to a
PDS 3D project.
 Symbol Properties — By default, PDS searches the piping specification based on
predefined aabbcc codes. SmartPlant P&ID symbols must have a property mapped to the
aabbcc_code attribute in the PDS database. The delivered SmartPlant P&ID piping
component symbols have a property called aabbcc_code, which can be viewed and edited
in Catalog Manager. Any new symbols must have this value defined, either at symbol
creation or later.
 Naming Conventions — PDS 3D is not capable of handling spaces in the path names to
any files. Therefore, this PDS restriction also applies to P&IDs. While creating units and
drawings in the SmartPlant P&ID site, take care to avoid creating paths with spaces.
 Symbology — SmartPlant P&ID stores drawings in a format other than IGDS
(MicroStation). These drawings are converted to IGDS format to display in PDS. By default,
PDS and MicroStation use a black background, while SmartPlant P&ID uses a white
background. When converted to IGDS format, this difference can make some SmartPlant
P&ID graphics barely visible on the black background. Consideration should be given to this
fact while defining symbology within SmartPlant P&ID plants. SmartPlant P&ID symbology is
defined in Options Manager.
 Two methods exist to manipulate the display so that all of the graphics are clearly visible in
their new format:
 Method 1: Turn off the Reference File > Use Color Table setting under User > User
Preferences > Reference File in PDS. This action displays the drawing using the active
color scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID.
 Method 2: Change the Background color of the piping model to a light color by using
Settings > Colors.
 Additional Attributes — If properties added to the SmartPlant database need to be
transferred to PDS, be careful to match attribute type and length on either side. The
maximum string length supported by RIS / PDS 3D is 240 characters. If a property has an
associated select list in SmartPlant P&ID, then it should have a corresponding codelist in
3D. You must run the Attribute Mapper to map new properties if you want the data to
transfer.
 Codelists and Select Lists — Even though having the same number and sequence for
entries within a codelist or select list is not required, for any mapped attributes, the PDS 3D
codelist should have all entries from the SmartPlant P&ID select list. If a new text entry is
added to a SmartPlant P&ID select list, the same text entry should be created in the
corresponding PDS 3D codelist. The Attribute Mapper must be run after any such change.
 Layers and Drawing Filters — PDS uses the concept of layers in a piping design to display
selected elements of a drawing; whereas, SmartPlant P&ID uses drawing filters. The
ExportLayer.xlsx file defines how the layers in PDS are related to the different drawing
objects. The location of this Excel file is defined in Options Manager.
 You can assign layer alphanumeric names to item types in order to assure that graphics
appear in the designated layers in PDS. Items are named according to filters, which are
defined in Filter Manager. For more information, see the topics dealing with layers in the
SmartPlant P&ID Online Help.

PDS 3D
 Codelists — A PDS 3D codelist can be a super set of a SmartPlant P&ID select list. This
means that a PDS code list can have extra entries not contained in the SmartPlant select list
because the data transfer works one way; that is, from SmartPlant P&ID to PDS 3D.
 User Attributes — Attributes can be created in PDS 3D independent of the SmartPlant
P&ID plant if data transfer is not required. If transfer is required, care should be taken when
adding attributes. A SmartPlant database does not distinguish between short and long
integers. Any new integer property that is added to such a database must be created as a
long integer in the PDS database.
Load from P&ID Options

Updates the active segment data based on information defined in the SmartPlant P&ID. The
system verifies the temperature and pressure service limits when loading segment data from the
SmartPlant database into an existing piping segment for which data was previously transferred.
Complete Data Transfer Option — Transfers all mapped attributes from the selected
SmartPlant P&ID segment into the active PDS segment data. Attributes that are transferred are
shown in yellow. Attributes that are not mapped are shown in black.
Partial Data Transfer Option — Transfers those mapped attributes that have the Partial option
chosen during attribute mapping, from the selected SmartPlant P&ID segment into active PDS
segment data. Attributes that are transferred are shown in blue.
Equipment and Nozzle Numbers Option — Updates the active segment data from the
SmartPlant P&ID using the segment data attached to the specified Equipment/Nozzle ID.
Graphical P&ID Setup Command

This command searches, selects, and displays the SmartPlant P&ID within the PDS piping
design environment. This display enables the graphical transfer of piping segment data by
snapping to graphics in the active P&ID. You can also specify a component name for placement
by selecting a component in the P&ID.
For data transfer purposes, only one P&ID can be active. You can select a P&ID to display from
the list of P&IDs extracted from the SmartPlant database. The list of P&IDs is limited to P&IDs
for the active unit number in the PDS piping model, or if the active unit number is undefined,
then all P&IDs from the SmartPlant database are listed in alphanumeric order by drawing
number.
The Graphical P&ID Setup command checks for the existence of SmartPlant P&ID data in the
PDS project. If P&ID data is found, then PDS 2D starts the old software component to allow data
transfer from P&ID. If the project is PDS 3D only, then the data transfer from SmartPlant P&ID to
PDS 3D starts.
You can use the following options to select the P&ID to display.
P&ID Conversion Option — Launches SmartPlant P&ID automation to convert the selected
P&ID from its native format to IGDS format. The converted drawing is placed in a temporary
folder. The drawing is closed automatically upon exiting the design session.
Units of Measure Option — Converts SI units in SmartPlant P&ID using unit-related codelists
from the Standard Note library in PDS. SmartPlant P&ID stores all properties with a unit of
measure in SI units. For example, length is stored in meters regardless of your plant settings.
The software then checks another property that determines how you want length values to

appear. When a property represents a quantity based on units (for example, pressure,
temperature, and so forth) data transfer looks at the active segment data, or type 63 settings, to
determine the unit of measure to use. The SI value stored in the database is then converted
using unit- related code lists from the Standard Note library.
Code-listed Attributes Option — Uses a codelist map to translate the codelisted attributes.
The Attribute Mapper stores mapping of codelist numbers such that their text values match.
Data transfer uses this codelist map to translate the codelisted attributes from the database to
the PDS database.
 If the SmartPlant database participates in Workshare environment, then the P&ID list is a
combination of the P&IDs owned and subscribed to (that is, published by remote location)
by the site.
 Use the LocalModelItemLookupTable.sql utility if your connected Workshare satellite
experiences performance problems when transferring piping data from SmartPlant P&ID to
PDS. This script converts a satellite database view (namely, the T_ModelItemLookup) that
references a host table into a local table, allowing the data transfer to proceed without using
a DBLink. SmartPlant P&ID uses the DBLink to fetch unique Long IDs from the Host when
running from a connected Workshare satellite. If the performance of opening the PID file in
PDS is an issue or if maintaining the correlation between SmartPlant P&ID and PDS after
the merge is not an issue, then you can run this script to change the lookup for the Long ID
from a view to the host to a local query. This utility is delivered as an SQL script to the
..\SmartPlant\P&ID Workstation\bin folder and can be executed using any Oracle user
interface, such as SQLPlus. Do not use this script if the transferred PDS data will be
merged back into a host PDS database because the Long IDs will not be unique at the host.
 Because SmartPlant databases are unit-dependent and PDS databases are design
area-dependent, one PDS piping design area can include data from different SmartPlant
units. Consequently, you must specify the correct unit number in the active segment data
prior to requesting a list of P&IDs from a SmartPlant database.
Select P&ID by Line ID Command

This command specifies a line ID by identifying piping in the PDS piping model or by accepting
the active line ID. The system determines the SmartPlant P&ID (or list of P&IDs) from the line
ID. It searches the Segment Table of the SmartPlant database using the system-unique number
for the drawing and the line ID for the segment. All P&ID segments belonging to the specified
line ID are highlighted.
Select P&ID Drawing by Nozzle Command

This command specifies an equipment number and nozzle number by locating a component
connected to a nozzle, by typing in an equipment number and nozzle number, or by placing a
data point over a nozzle in a model. The system determines the SmartPlant P&ID from the
equipment number and nozzle number and data in the SmartPlant database. All P&ID segments
that have the same line ID as the segment connected to the active nozzle are highlighted.
Currently, only the first segment coming off the nozzle is highlighted, not the entire line.

Review P&ID Drawing Details Command

Displays information about a selected SmartPlant P&ID in the active unit.
P&ID Drawing Display Categories Command

Displays SmartPlant P&ID display categories. Categories that are currently displayed are
highlighted on this dialog box. Selecting a category toggles its setting. P&ID controls display and
symbology through the use of drawing filters. The P&ID graphics in the converted IGDS format
are not organized into familiar categories such as piping, equipment, or instruments, instead the
software displays MicroStation levels 1 through 63 as SmartPlant P&ID drawing filters. Some of
the categories are turned off automatically to hide blank label enclosures and inactive heat
tracing graphics.
Restore View of Piping Model Command

Restores the PDS 3D model view in the window where the SmartPlant P&ID is currently
displayed.
Disable Display of P&ID Drawing Command

Closes the currently displayed SmartPlant P&ID and restores the PDS 3D model view.
Name from P&ID Option

Selects the piping or instrument component that you want to place by identifying a component in
the SmartPlant P&ID. If the selected instrument has a tag number that does not exist in the
Piping Job Specification, the system displays the Instrument Placement dialog box with both
Data From Reference Database and Data From User options. Select the Data from User
option, select the shape that you want, and enter the dimensions that are required. This
procedure allows the tag number and the properties that were mapped in the attribute map to
transfer from the SmartPlant to the PDS database.
This mechanism also applies to piping specialties.
Named Component Existence Report Command

Compares the existence of user-specified named components between the PDS and the
SmartPlant databases in batch mode on the basis of a user-defined list of lines and then
generates a report of the results.
If a PDS 2D P&ID database exists, then it is used with the PDS model as the basis for
comparison. If it does not exist, then the SmartPlant database is used as the basis for
comparison. As part of the report, the software includes the database that the comparison was
based on. The comparison does not make use of either the P&ID drawing or the PDS piping
model. Therefore, the order of components is not considered in the report.
A user-defined list, design area, or model is used to define those items that are included in the
report. The user-defined list must have one line ID per line. Whether you create a list or use a
design area or model, the list of line IDs used to perform the comparison is included in the
report.

The comparison considers the entire pipe run in both the SmartPlant database and the PDS
database. If a line ID is used in multiple SmartPlant P&IDs or is included in multiple PDS
models, the complete definition of all P&IDs or models is included in the report regardless of the
line-ID option that is selected.
The following items are included in the comparison report:
 The named components in the piping design database are included and are compared on
the basis of the following data:
 Tagged piping commodities are compared on the basis of their piping component
number
 Piping specialties are compared on the basis of their piping component number
 Inline instruments are compared on the basis of their instrument component number
 Tagged piping commodities in the SmartPlant database that have the following data are
included:
 The Commodity Code flag is set to by system or by user and the commodity code is
defined
 The Piping Component Number is defined
 Piping specialties in the SmartPlant database are determined by those piping components
that have the following data:
 The Commodity Code flag is set by the user or is blank
 The Piping Component Number is defined
 Instruments in the SmartPlant database are determined by the following criterion:
 Only those instruments that are applicable to the PDS 3D model, such as those
requiring dimension definition in the RDB, as determined by an Instrument Correlation
List
The Instrument Correlation List, which is necessary to define the applicable instruments for
transfer, is a user-defined ASCII file in the project folder and is named pid_instrument. With this
list you can specify the inclusion or exclusion of SmartPlant P&ID instruments on the basis of
their aabb or aabbcc codes. You can include or exclude groups of instruments on the basis of
the aabb code for that instrument by using the appropriate keyword, either Include or Exclude,
followed by the aabb code. You can specify exceptions to the aabb codes on the basis of
specific aabbcc codes so that you can exclude from an Include group, or you can add those
entries to an Exclude group by adding the exceptions under the line containing the Include or
Exclude statement.
The ! character signifies a comment line in this ASCII file.
The following text represents the default Instrument Correlation List that defines the SmartPlant
P&ID instruments that are applicable to the PDS 3D model. In this example, the aabb code
represents a substring search of the aabbcc code.
!Include all control valves
Include 7P1E
!Include all relief devices
Include 7P2C
!Include all other in-line instruments
Include 7P3C
!except for the following

7P3C44
7P3C46
!Exclude all off-line instruments
Exclude 7Q4D
!except for the following
7Q4D21
7Q4D24
7Q4D27
7Q4D28
7Q4D29
7Q4D30
7Q4D31
7Q4D32
7Q4D33
! Exclude all system functions
Exclude 7Q5A
You can format the title page and the heading for each page of the Named Component
Existence report using the win32app\ingr\pddesign\sample\pid_cmprpt.fmt file. The remainder of
the report contains the following sections:
 The list of line IDs that determine the basis for the report
 Named components in the SmartPlant database, that are not in the PDS 3D model, are
reported with the component number and the drawing number
 Named components in the PDS 3D model that are not in the SmartPlant database are
reported with the component number, the design area number, and the model number
Troubleshooting
Some common difficulties that you may encounter are listed here, along with possible solutions.
No Projects on This Site

On some systems, you receive the No projects on this site error when you try to connect to
the SmartPlant P&ID site server. As a workaround, you can edit the Microsoft Access file
\projectname\project\SPMap.mdb directly and add a line in the connection table as follows:
 Project Number is the PDS project name (case sensitive)
 MapPathName is the complete UNC path to the SmartPlant P&ID plant SPMap.mdb file
located in the PDS project directory
 IsThreeD has to be selected
 SPSiteNode is the UNC path to the SmartPlant initialization file
 SPProjectName is the SmartPlant P&ID plant name
Save changes made to the SPMap.mdb file, and run the SP PID to PDS 3D command again.
If a client computer experiences problems connecting to the project, remove the
Intergraph SmartPlant Attribute Mapper and Intergraph SmartPlant P&ID Automation
components using Add/Remove Programs. Restart the computer and reinstall PD_Shell and
SmartPlant P&ID Integration Tools using the silent installation. Be aware that for PDS users to
set up the attribute map and perform data transfer, they must have permission to access the
SmartPlant server through SmartPlant Engineering Manager.

Display
Start PD_Shell, and go to piping. Inside the PDS piping model but before using the Graphical
P&ID Setup command, select one of the two methods below so that all of the P&ID items are
clearly visible in order to display properly the converted P&ID within PDS:
 Method 1: Turn off the Reference File > Use Color Table setting under User > User
Preferences > Reference File. This action displays the drawing using the active color
scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID.
 Method 2: Change the Background color of the piping model to a lighter color by using
Settings > Colors.
Display by Unit Filter

Run the Graphical P&ID Setup command as with PDS 2D, unless the unit is simply a filter. If
not specified, all plant P&IDs are shown. Note that the P&ID Drawing Name is what you see on
the data transfer dialog boxes, not the drawing number.
Temperature/Pressure Units
Select lines for pipe run and component data for the Name from P&ID option. For Pipeline data,
four sets of temperature/pressure values with units must be set in the SmartPlant P&ID or you
will receive an error about temperature/pressure limits. You can choose the No Minimum T-P
Data for Service Limits Verification option in the PDS project data manager to prevent that
error. When using this option, the lower range of the temperature/pressure values is not
checked, thus allowing undefined values in PDS: -9999.
Removing Software from a Silent Installation Configuration

For a silent installation, when you accept the SmartPlant P&ID Integration Tools option on the
PDS component loader dialog box, the following components are installed and the following
folders created:
 Intergraph SmartPlant Attribute Mapper
 Intergraph SmartPlant P&ID Automation, including
 ..\Common Files\Intergraph\RAD (used by SmartPlant P&ID and SmartSketch)
 ..\Common Files\Intergraph Shared\SmartPlant
 ..\SmartPlant
If you need to remove the components for the silent installation and have SmartSketch on the
computer, remove SmartSketch and its associated components first. Continue by removing
PD_Shell from the PDS remove product utilities. This action prompts you to confirm deletion of
the Intergraph SmartPlant Attribute Mapper. Select Yes, and confirm the deletion of all shared
files.
This step does not delete Intergraph SmartPlant P&ID Automation. To remove
automation, go to Add/Remove Programs, select Intergraph SPP&ID Automation from the
list, accept its deletion, and confirm deletion of all shared files. Then restart your computer.
Before re-installing any software in the client computer, delete the three folders specified above,
and any files contained in them.

Known Issues and Limitations

 The Graphical P&ID Setup command cannot convert and display a P&ID that has a space
in the P&ID file path. Make sure the paths and filenames to the P&IDs have no spaces in
them. You get the same result if you use a comma in the P&ID title.
 When the P&ID plant hierarchy does not contain the Unit item, an error occurs when
snapping to a piping segment or a component in the PD_Design environment.
 You must define the Option Code property for a component in SmartPlant P&ID if you are
planning to use the Name from P&ID command for transferring any other component
information. The implication is that your piping specifications must be created before
drawing the P&IDs if you use this command for any data transfer.
 You must dismiss the Graphics Setup menu after selecting the P&ID that you want to
display. Sometimes this form may be hidden, and you must dismiss it before you can
transfer data from a pipeline.
 Levels settings (that is, displays of drawing filters) are not saved for a SmartPlant P&ID
drawing. You must select the correct levels each time that you enter the drawing.
If you want to see the P&ID labels and line types correctly, you must map your P&ID fonts to
proper MicroStation fonts in one of the .ini files. ISO Plus RDB fonts and borders.txt contain this
information. Also, the standard RDB Arial Narrow is mapped to a not-always-present
MicroStation font and causes unreadable labels on the screen.

SECTION 8
Detecting and Managing Interferences
This chapter provides information required to understand the terminology and philosophy
involved with interference detection.
Interference Checker/Manager (PD_Clash) processes a specified design volume for interference
clashes. You can check for, review, and revise interferences at any stage of the design process.
The first section in this chapter is an overview of the interference management process; it briefly
covers the following topics:
 Software setup
 Interference envelope generation
 Clash detection
 Clash management and tracking
The second section is a review of project organization and the different units into which a
plant/project can be broken for ease of manipulation.
The third section describes how to set up a system to support interference detection.
The fourth and final section is a general description of interference envelopes, the various types
of interferences (clashes) and what happens during interference detection and management.
Interference Checking Process Overview

The following outlines the basic steps associated with interference detection and management.
Setup (outside the Interference Manager module)

1. Define data with the Project Environment Manager.
 Volume/Area definitions determine the extent of the project to process. The extent may
be physical by defining pre-defined volumes or logical by grouping models in a design
area.
 To disable interference checking between certain disciplines, use the Intra Discipline
Interference Check toggle when defining the Discipline data.
2. Define interference data with the Project Data Manager.
 The construction tolerance, the necessary space allocated beyond that which is
necessary for the component and its insulation, for each discipline is defined with the
Construction Tolerance form.
 The action discipline is used to assign responsibility for a clash to a certain discipline.
The action discipline is defined using the Select Action Discipline option on the
Interference Check Data form.
The defined action discipline appears on plots and in the Action Discipline: field on the
Interference Manager form in the Interference Checker/Manager module.

Interference Envelopes:
3. The system accesses the model files to generate envelope files. The envelope files have an
.env file extension. It is the envelope file and not the design file that is compared
during interference detection.
4. The graphical volume for each component is defined by an interference envelope parametric
shape definition. This is an Eden module similar to the parametric shape module used to
place the component in graphics.
Before performing interference detection on newly created or modified interference envelope
parametric shape definitions, use the Envelope Diagnostics option to generate a
MicroStation-type graphic from the interference envelope. The graphics file is named after
the envelope with a .til file extension.
5. Verify the consistency between the dates of envelope files and current design files using the
Envelope Verification option. The results of the verification indicate which envelopes need
to be updated.
Clash Detection:
6. Run the Interference Checker option to compare the envelope files for clashes within the
specified area or volume.
7. A volume filter can be set for single runs of interference detection. Only the clashes found
within the specified volume are available for review after an interference detection run using
this option.
8. For pre-defined volume design areas, the system checks all models within the prevolume.
This includes the portion of any model envelope file that encroaches within that volume
regardless of its discipline.
— OR —
For regular design areas, the system defines the volume as that which encompasses all
model envelope files within the selected design area. This includes the portion of any model
envelope file that encroaches within that volume regardless of its discipline or design area
assignment.
9. For the specified area/volume, the system processes all of the portions of model envelopes
or pairs of envelopes, for example:
Model A vs Model B
Model A vs Model C
Model A vs Model D
Model B vs Model C
Model B vs Model D
Model C vs Model D
10. When a clash is detected, it is written to the database, and the graphics representing the
clashing elements are written to the appropriate marker file. If you checked the entire
project, the clashes are written to the project marker file. If you checked a design area, the
marker file is named after the design area with the extension which represents the
discipline:
Piping = 1 Structural = 3 Raceways = 5

Equipment =2 HVAC =4 Architecture = 6

11. The Interference Report is created during the interference detection process and is named
after the project or design area, depending on the option selected for interference detection,
with an .int file extension. It contains only the unapproved clashes for that run.
Tracking and Managing:
12. Edit and review existing clashes, manipulate views, and approve exisiting clashes with the
Interference Manager option. This option displays and highlights clashes within a graphics
environment, which can then be reviewed, edited or approved.
13. For unsuspected clashes, review envelopes in question using the Envelope Diagnostics
command. This command generates a report with a .evd file extension. For example, this
report contains instances such as when two or more groups of sub-components are
contained within one component but are not geometrically connected, in other words do not
have overlapping ranges.
14. Clashes can be plotted any time after interference detection using the Interference Plot
Manager option.
15. Aside from the Interferences Report, which is automatically generated during interference
detection with the Interference Checker option, reporting on the Project Control Data is
done using the Interference Report Manager. Discrimination data and format files are used
to generate specific types of reports. This sort of report might include a list of clashes
involving the structural discipline, the approval status of those clashes, and the action
discipline assigned to these clashes.
Project Organization
As discussed in Chapter 1, PDS uses the following organization to break the plant into smaller
units that can be handled more easily.
A project is a convenient grouping of all of the items that constitute a plant. The project is the
fundamental structure for working in PDS. The project constitutes the entire volume of the
project.
A design area represents a specified volume or logical area of the project for a specific
discipline. Design areas can be used to break up the project into smaller areas for interference
checking or reporting. This speeds up processing when only a portion of the project has
changed. The models or model components that are not within the area/volume will not be
checked.
A design area pre-defined volume represents a pre-defined volume of the project for a specific
discipline. The volume is defined by using the Project Environment Manager. Make sure that
the pre-defined volume encompasses all the models that you want to be checked. The models
or model components that are not within the volume will not be checked. The Prevolume is used
to encompass models and model components that might not have been grouped together
otherwise, or to define a design area that is smaller than usual.
A model is a 3D Microstation file that has a defined discipline and is located within the volume of
the project. A model represents a subdivision of the project based on work responsibility,
completion of schedules, and computer response time.
A volume filter can be used to decrease the volume of a project, area, or pre-defined volume to
further decrease the processing time when only a sub-part requires checking or reporting.

Understanding Design Areas and Volumes

This section describes design areas and volumes and how they pertain to interference checking.
Running the Interference Checker for an entire project takes considerably longer than running it
for a design area. If the project workload is being shared, one of the design area options would
be the most efficient. The design area options are less time consuming and create individual
sets of reports rather than one set of reports for the entire project. Adhere to using either the
Project option or one of the Design Area options for the life of the project for the most
consistent results.
Project
This option on the Interference Checker form performs clash checking for all of the envelope
files defined for the project and creates interference, difference, and batch queue error reports.
To specify a smaller volume for a single clash check, set the Volume Filter toggle to On.
The dotted rectangle signifies the volume that is processed using the Project option.
Piping Design Area and Design Area

These options display a list of design areas for the specified discipline that are available for
clash checking. After a design area has been selected, the system defines a volume that
encompasses all models within the selected design area. It then performs an interference check
on all models and parts of models, including models from all other disciplines, that are in the
defined volume. To specify a smaller volume for a single interference check, set the Volume
Filter toggle to On after selecting a design area.

The dotted rectangle signifies the volume that is processed using the Design Area option. The
name of the selected design area is DesA1.
Design Area and Piping Design Area Predefined Volume

These options display a list of design areas with pre-defined volumes available for clash
checking. After a design area has been selected, the system uses the pre-defined volume (as
specified through the Project Environment Manager). It then performs an interference check
on all models and parts of models, including models from all other disciplines, that are in the
pre-defined volume.
The Interference Checker does not include models or parts of models that are in the
selected design area that do not fall within the pre-defined volume.
The dotted rectangle signifies the volume that is processed using the Design Area PreVolume
option. The name of the selected design area is DesAPreV1.
If you use Pre-defined Volumes as your method of checking, it is recommended that you
run a project wide check at the end of the project to ensure that nothing was missed. However,
you should not switch between Pre-defined Volume and Project on a consistent basis.

Volume Filter
This option creates a Volume Filter for one run of the Interference Checker. When set to
Volume Filter On, you can define the low and high Easting, Northing, and Elevation coordinates
for one run of the Interference Checker in the following fields. When set to Volume Filter Off the
system will use the default or pre-defined volume.
A volume filter can be used to decrease the volume of a project, area, or pre-defined volume to
further decrease the processing time when only a sub-part requires checking or reporting. The
dotted rectangle signifies the volume that is processed when the Volume Filter has been
activated and the volume to be checked has been specified.

Single/Dual Ownership of Clashes

PD_Clash can be set up to allow single or dual ownership of clashes. This is very useful when
more than one design area needs to own, review, or approve a clash.
PD_Clash provides the capability for dual ownership–ownership available to each design area
that CONTAINS a component involved in a clash (when interference detection is run on that
area) or single ownership–ownership assigned to the first design area to find the clash.
Dual ownership does not mean that ownership is automatically given to both design areas when
a clash is found. It means that ownership is available to both design areas when interference
detection is run on each.
Since clashes are stored in the database, reports can still be run on both design areas
involved in a clash, even if interference detection has not been run on both design areas.
However, clashes are only written to the applicable design area's marker file during the
interference detection process for each design area. Therefore, clashes can only be reviewed
and approved in design areas on which interference detection has been run.
This option does not define ownership assignments once clashes have been found. It acts a
filter in the interference-detection process.
By default clash checking is done in Single (1) Design Area Ownership mode. In this mode,
each clash belongs to the design area in which it was first found. When clash checking is done
in this mode, clashes involving models that do not belong to the design area being checked are
still assigned to that design area.
For instance, if design area C were checked for interferences in the Single (1) Design Area
Ownership mode, the system would compare all models that fall within the specified volume
including:
 all models against themselves
 all design area A models against design area B models
 all design area C models against design area A models
 all design area C models against design area B models.
All of the clashes would belong to design area C.

In the Dual (2) Design Area Ownership mode, ownership is not based on the first design area
to find the clashes but on the design areas which own the components involved in a clash.
Interference checking is performed between models belonging to the design area being checked
and all other models that fall within the volume of that design area. Clashes that do not involve
at least one component from the design area being checked would not be found.
For instance, if design area C were checked for interferences in the Dual (2) Design Area
Ownership mode, the system would compare models in design area C with models falling
within the specified volume including:

 all design area C models against themselves

 all design area C models against design area A models
 all design area C models against design area B models.
The clashes found involving, for instance, design area C models against design area A models
would be owned by design area C. Clashes could be reviewed and approved in design area C
and reports could be run on either design area C or design area A. You could not review or
approve clashes in design area A until you had run interference detection on it.
Clashes that do not involve at least one component from design area C models would not be
found.
Setting Up a System to Support Interference

Detection
The following project setup considerations are necessary to support interference checking.
1. Load software
All PDS servers and workstations must be loaded with the same release of PDS and
nucleus software. The PDS software between servers and workstations must be compatible
to run correctly. It is highly recommended that you read the Release Notes of the
PD_CLASH README file when new releases are issued so that you will be informed of any
changes made to the product. The CAD Support person would most likely do this.
2. Set up plot queues.
The Interference Manager provides one default and four optional plot queues for different
types of plotters. The selection of the plot queue applies to all graphic interference clash
plots in a batch process. Multiple queues provide the flexibility in situations that arise which
require different plotters for different paper types. This step would be completed by the CAD
Support/System or Project Manager.
3. Define discipline responsibilities.
 The interference software uses area and model data to locate the models within a
specific design area for processing. This is done when the areas and model files are
created. The location of the area marker file and model design file are stored by the
system using data provided via the Project Environment Manager.
 Marker files are used by the software to place graphic markers for clashes that are
detected during interference checking.
4. Decide on Project or Area processing.

Interference checking can be done for the entire project or it can be divided into small
portions called design areas. The processing time for an entire project is much greater than
for a design area. Also, it is often the case that only a certain design area or set of design
areas need to be checked.
Once you decide which method to use, either the Project option or the design area
options, remain consistent. The more consistent you are with your option selection, the more
consistent the results will be. For example, you might select a design area option and
receive the results for one design area. You might correct a few of the interferences and
then run interference checking with the Project option. Remember, the interference checker
will only report new clashes, therefore, old clashes would not be reported again although
they may still exist in the design area that was first checked. This step would be done by the
Interference Manager.
5. Define model graphics.
A set of model files for the project must be defined before you can use the Interference
Checker/Manager.
Understanding Interference Envelopes

Envelope Builder
Piping, equipment, structural, raceway, and HVAC envelope files are created through the PDS
Interference Manager module. All Architectural files will have their interference envelope files
created within the Architecture product.
The envelope builder command performs the following tests to detect the situation where the
graphics for a model, that is not associated with the selected design area, encroaches into the
volume represented by that design area:
 If the envelope file which corresponds to the model is Up-To-Date with respect to the model,
the envelope builder will not re-create the envelope file.
 If the envelope file which corresponds to the model is Not-Up-To-Date with respect to the
model, but it has interference envelopes in the volume of the selected design area, then the
envelope file for the model is re-created.
 If the envelope file which corresponds to the model is Not-Up-To-Date with respect to the
model and it does not have any interference envelopes which fall within the volume of the
selected design area, then the envelope builder determines if the model has any
components which falls in the volume of the selected design area. If so, the envelope file for
that model is re-created.
 Log files are batch queue error reports for the envelope builder data server that contain
information regarding any errors. These files have the extension .ebl and are created in the
\temp directory on the server or workstation from which the process was submitted. You
should review this file.
Envelope Verification
The Envelope Verification command sorts the models being verified into one of the following
categories:
 Up-To-Date: those interference envelopes that are consistent with respect to the model.

 Not Up-To-Date: those interference envelopes that are inconsistent with respect to the
model and may require being re-created. This is because either the model has been revised
since the interference envelopes were created, or the interference envelope file is
non-existent.
 Not Mounted: an error occurred while mounting the file system where the model resides.
Any discrepancies found during this verification process indicate problems in the applicable
Envelope Builder and will be reported in a file in the \temp directory named after the project or
design area with an .evd file extension.
Envelope Diagnostics
The Envelope Diagnostics command creates MicroStation graphics from the interference
envelopes for the model, in a file named <model name>. til. This file, placed in the same
directory as the model, is used to view the interference envelopes interactively through
MicroStation to verify if the envelopes are correct.
Understanding Interference Checking

Once an interference philosophy has been determined, select the option to run the batch
Interference Checker. Use your choice of either the Project option or any of the design area
options consistently throughout the interference checking process.
 The Project option is the largest area of the project and encompasses every model file.
 The Design Area options process a smaller division of a project with a limited number of
model files.
 The Pre-Defined Volume option allows you to control the volume checked by specifying
specific volume coordinates. If not used, the system determines the volume based on the
volume of the envelope files in the area being checked (which can vary over the life of a
project).
 The Volume Filter toggle specifies a smaller volume of any of the options above.
Once the Interference Checker has been run, you can review the clashes interactively with the
The Piping Designer provides a command to check interferences interactively while
working in the piping design file. This option only checks one pipeline (or a group) against
reference files that have a previously created envelope file. Unlike the Interference Checker, the
Piping Design command does not write clash information to the database. It is intended as a
quick check for the piping designer.
Interference Checker Input

The following are used as input by the PDS Interference Checker:
 The data collected by the forms interface.
 Interference envelope files which correspond to model volumes or design areas.
 Information in the Project Control Database. The approval status of each known interference
is stored in the Project Control Database. When an interference is approved, it is no longer
included in future interference reports. This allows all interferences within a project to be

resolved, either by changing the approval status of the interference to Approved or by

revising the model.
 Information in the Material Reference Database. The following database tables can be used
to exclude items from interference checking.
 The Component Insulation Exclusion Data table (PDtable_23 1) allows you to
completely or partially exclude the insulation of components that are on insulated lines,
during interference checking. If this table is not loaded, the insulation thickness is
completely included in the component's interference envelope.
 The Flange Insulation Exclusion Data table (PD_table 232) provides for partial exclusion
of flange insulation thickness from the generation of interference envelopes. This is an
optional data table; if no data is defined for this table the insulation thickness is
completely included in the component's interference envelope.
Interference Checker Output

The following are generated by running the Interference Checker:
 PDS Interference Report. This report contains all unapproved clashes, sorted first by
model combinations then by the type of clash. For instance, all clashes detected between
model A and model B are grouped together. A synopsis of the clashes is included at the
beginning of the report. This report also includes the model status of any components
involved in a clash for the piping, structural, HVAC, and equipment disciplines. This status is
that of the model and not of the clash.
These reports are named after the project or design area with an .int file extension and are
created each time the checker is run. The interference report is created at the location
specified with the Interference Report Management Data option. The report begins with a
synopsis of all clashes found during interference processing and includes a report of the
clashing items within each of the design files represented in the synopsis.
PDS Interference Synopsis
mbpip2.e
nv
Number of clashes = 14
PDS Interference
Report
Date: 23-Jun-93 Time: 13:42:13
Model ’A’ Design File Name: mbpip2
Entire Design Volume Included In Report
PDS 3D Theory — April 2002
PDS Interference
Clashes
Hard/Hard Clashes
No Item Name Table Row X Coord Y Coord Z Coord
48 2CPINSTRUMENT 6 4194305 E 1’ 3 15/16" 2000’ 0" El 0’ 0" Plant

Plant N Plant
meblabels-6IN-1C0031-0 "
Not approved

48 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0" Plant
Plant N Plant
ifc’clash pipe’-1IN-1C0031-0 "
Not approved
49 3CPINSTRUMENT 6 4194306 E 8’ 4" Plant N 2000’ 0" El 0’ 0" Plant

Plant
Not approved
49 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0" Plant

Plant N Plant
Not approved
50 2CPSPECIALTY 3 4194306 E 13’ 4 1/8" N 2000’ 0" El 0’ 0" Plant

Plant Plant
Not approved
50 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0" Plant

Plant N Plant
Not approved
51 3CPSPECIALTY 3 4194307 E 18’ 4 1/4" N 2000’ 0" El 0’ 0" Plant

Plant Plant
Not approved
51 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0" Plant

Plant N Plant
Not approved
52 T 3 4194309 E 26’ 8 9/16" 2000’ 0" El 0’ 0" Plant

Plant N Plant
Not approved
52 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0" Plant

Plant N Plant
Not approved
53 PIPE 5 4194305 E 30’ 2 3/16" 2000’ 0" El 0’ 0" Plant

Plant N Plant
Not approved
53 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0" Plant

Plant N Plant
Not approved
54 pipesupport 8 4194305 E 31’ 2 3/16" 2000’ 6" El -1’ 1

Plant N Plant 9/16" Plant
Not approved
54 PIPE 5 4194308 E 40’ 2 3/16" 1999’ 4" El -6" Plant

Plant N Plant
ifcclash pipe-1IN-1C0031-0 "
Not approved
55 PIPE 5 4194306 E 40’ 2 3/16" 1999’ 10" El 0’ 0"

Plant N Plant Plant
Not approved

55 CKS 3 4194321 E 22’ 6 1/16" 2000’ 0" El 0’ 0"
Plant N Plant Plant
1construct-6IN-1C0031-0 "
Not approved
 Interference Markers. All interferences within the project are graphically represented by
markers and are used by the Interference Manager. Each time the Interference Checker
detects an interference within the project, a marker is written to one of the marker design
files. The project marker file is created in the project directory during project creation. It is
named after the project database with a .dgn extension. Area marker files can be created as
each piping or equipment design area is defined in the Project Control Database.
The interference markers are numbered in the .int report with a system-assigned sequential
number starting with 1. Any previously approved markers (interferences) will not be replaced
unless the corresponding model items have been graphically modified.
 Error File. If an error is found while running the Interference Checker, the system writes the
item name and an error code in a file named after either the project or design area,
depending on the option selected to run the Interference Checker, with an .icl file
extension. Runtime errors are written to a file with a .err extension.
 Log files. Each batch job creates a log file which is placed in the \temp directory. Any run
time errors will be listed in these log files.
 Project Control Database Records. The following tables are updated by Interference
Checking:
 Clash Management Data (131). A record is created each time Interference Checking is
run.
 Interference Clash Data Per Project (132). A record is created for each clash in the
project. The unique_clash_id uniquely identifies a clash.
 Interference Clash Data Per Job (133). A record is created each time a clash is
encountered.
 Component Clash Data Per Project (134). A record is created for each model item
which is involved in one or more clashes.
These records are used by subsequent executions of the Interference Checker and
 Clash Plots. These files are named by the system as the marker number with the extension
.plt and placed in the \temp directory (or you may use the Interference Clash Plot Manager
to specify a different node and directory). The system automatically generates the plots
through the PDifc_plot queue.
Interference Manager
The interference manager is used to review all interferences in a project or area and revise the
approval status of a single interference marker or a group of interference markers.

Clash Categories
The Interference Manager and the reports created by the Interference Checker distinguish
between three categories of interference clashes. See the graphics on the following page for
examples of clashes.
 Hard. A clash which exists between actual physical components, equipment, or structures.
 Soft. A clash which exists between non-physical space envelopes, such as, insulation,
maintenance access ways, or safety envelopes.
 Construction. A clash or discrepancy which exists between the user-defined distance and
the actual distance of two components in specified disciplines defined using PD_Project. For
instance, if piping components are required to be at least 1" away from all structural
components but one is found closer, a Construction clash is reported.
Clash Precedence
The precedence for reporting clashes is Hard, Soft, and Construction. This results in the
interference clash being reported in one of the following categories. The report will contain only
the category of clashes with the highest precedence in accordance with the following
precedence table:
Hard - Hard
Hard - Soft
Hard - Construction
Soft - Soft
Soft - Construction
Construction - Construction.

Hard - Hard Example

The following example contains clashes between actual physical components. It would be
categorized as a Hard - Hard clash.
Hard - Soft Example

The following example displays a clash between an actual component and space that has been
allocated for maintenance access ways. It would be categorized as a Hard - Soft clash.

Understanding Interference Plotting

The Interference Plot Manager option plots clashes generally by project or design area. Within
these choices, you can plot clashes by:
 The clash plot status.
 The clash approval status.
 The clash review status.
 The clash category.
 The group or individual clash selections from a list of clashes in marker file.
The Interference Clash Plot Management option defines a default node and path for future
clash plot files.
This is a required step in the Interference Checking Process. Problems could occur
later in the process if this step has not been completed.
Understanding Interference Reporting

The interferences report is generated automatically during interference detection with the
Interference Checker option. You can create user-defined reports on the Project Control Data
using the Interference Report Manager. Discrimination data and format files are used to
generate specific types of reports, such as a list of clashes involving the structural discipline, the
approval status of those clashes, and the action discipline assigned to these clashes.
The interface and process for interference reporting is similar to that used in the PDS Report
Manager module.

SECTION 9
Creating Material Takeoffs and Other
Reports
Reporting Process
The following outlines the basic steps associated with the Material Take-Off process.
1. Pre-defined report data determines the discrimination data (such as which models to
process) and the format (content and layout) of the report.
2. For the specified models (and using any additional discrimination data, such as line size),
the system scans the physical elements in the model.
3. The system determines the number of items present in the model by unique commodity
code. In addition to the physical elements, it determines any implied items based on
configuration of mating components or designations in the Piping Commodity Specification
Data (PCD).
4. The system looks up the material descriptions for the located components and implied items
in the Material Description Library.
5. The system writes a report of the located and calculated items based on pre-defined report
format.
There are two main user tasks necessary for creating reports:
 Maintaining the data that defines the format, content and approval status of the reports.
 Processing reports by activating the interface to extract data from all of the PDS models,
databases, and libraries that are involved in a project.
Maintaining Report Definition Data

The Report Manager uses both report definition files, such as discrimination data files and
format files, along with database records that represent these files to generate reports.
The two most important files that must be maintained in a report creation process are the
discrimination data file and the format file. The discrimination data file, which defines the search
criteria for a report, is maintained interactively with the Report Manager. The format file is
generated outside of the interface using an ASCII text editor. There are several sample format
files that are delivered with the PDS 3D products. You can use these files as examples for
creating format files to meet your specific needs.

Creating Material Takeoffs and Other Reports
Understanding Report Files and Records

The following definitions explain all of the files and records in the reporting process.
Format File
The format file is a user-defined, ASCII-text file which contains special indices identifying what
data appears in the report, how the data is sorted, and how the data is formatted in the report. A
set of basic format files are delivered for several types of reports. Using the Report Format
option, you can create a database record for each format file so that it can be accessed for
report processing. Without the format record, the Report Manager is unable to access format
files.
Format Record
The format record is a record in the Project Control Database used to name and locate a
specific format file. It is called a record to classify it as a block of data that is used for report
processing but, it is not an actual file. It is created interactively. There are five format definitions
in the format record:
 Number — Defines a unique number to name the record with up to 24 characters in the
Project Control Database. This number is a short name to identify the record of the format
file.
 Description — Describes the format file with up to 40 characters in the Project Control
Database.
 File Specification — Defines the file name of the ASCII format file. The system verifies that
the file does not already have a record in the project.
 Path — Defines the disk location of the format file. This field retains the active setting.
 Node — Defines the nodename where the format file is located. This field retains the active
setting.
Discrimination Data File

The discrimination data file defines the search criteria which is used to limit the report to only the
specified database occurrences. It is an ASCII file that is created interactively using the Report
Manager. You also create a uniquely-numbered record for each discrimination data file so that it
can be accessed for report processing.
Discrimination Data Record

The discrimination data record is a record in the Project Control Database used to name and
locate a specific discrimination data file. It is called a record to classify it as a block of data that
is used for report processing but is not an actual file. It is created using the Report Manager.
There are five discrimination data definitions in the discrimination data record:
 Number — Defines a unique number to name the record with up to 24 characters in the
Project Control Database. This number is a short name to identify the record of the
discrimination data file.
 Description — Describes the discrimination data file with up to 40 characters in the Project
Control Database.

 File Specification — Defines the file name of the discrimination data file to reference. The
system verifies that the file does not already have a record in the project.
 Path — Defines the disk location of the discrimination data file. This field retains the active
setting.
 Node — Defines the nodename where the discrimination data file is located. This field
retains the active setting.
Report Record
The report record defines locations for all of the files that are necessary to generate a report,
including the report output. (It is called a record to classify it as a block of data that is used for
report processing but is not an actual file.) It is created using the Report Manager. There are
seven report definitions in the report record:
 Report Number — Creates a unique report number in the Project Control Database that
acts as a name or identifier for a report record.
 Report Title — Describes the report file. It is not the title in the actual report. That title is
specified in the format file.
 Report File Spec — Defines the file name of the report output file. Each time a file is
re-generated using the same report file, the report output file is overwritten. Change this field
to save the old report output file and generate a new one.
 Report File Path — Defines the directory for the report output file. Report Node —
Specifies the nodename for the report output file.
 Report Format File — Specifies the record number that contains the address of the report
format file to be used.
 Report Discrimination Data — Specifies the record number that contains the address of
the discrimination data to be used.
Report Output
The Report Manager creates a report using the specified format and discrimination data files
and places it in the directory specified.

Processing Reports
Since there are reporting capabilities in various PDS modules, the format file, the discrimination
data file and the module where the report process is activated determine what type of report is
created.
For instance, you can create MTO reports with Report Manager and Drawing reports with the
report manager module of Drawing Manager. Depending on the definition data used and the
module that executes the process, you can create MTO reports, drawing reports, spec reports,
table checker reports, project reports, or interference reports.
The following section describes the various report types, how they are generated, and their
corresponding sample format files:
Report Types
Various modules in the PDS Suite generate reports. The following section describes the various
report types, how they are generated, and their corresponding sample format files:
 MTO Report (with implied materials) — Generates reports on PDS piping and equipment
models involving data from the Design Database, Reference Database, Project Database,
and Material Description Libraries. This type of report will also include implied mating data,
such as bolts, gaskets, and welds by determining the connectivity of the piping and
equipment. Format files used in this type of report primarily use A and B prefixed indices.
This report is generated using the Report Manager.
 Drawing Report — Generates reports on PDS Piping and Equipment drawing views and
drawing files. This report is the same type of report as the MTO report generated by the
Report Manager. Format files used in this type of report primarily use A and B prefixed
indices. This report is generated using the Drawing Manager.
 Spec Report — Generates reports on the Reference Database and Material Description
Libraries. The spec report is used to report on data in the reference database. Format files
used to create this type of report primarily use C prefixed indices. This report is generated
by the Reference Data Manager.
 Table Checker Report — Generates reports on the Reference Database and Material
Description Libraries. The table checker report is used to test Eden modules and tables that
would be executed by the Piping Commodity items within the Reference Database. Format
files used to create this type of report primarily use C prefixed indices. This report is
generated by the Reference Data Manager.
 Project Report — Generates reports on the Project Control Database. Format files used in
this type of report primarily use D prefixed indices. This report is generated using the
Project Administrator.
 Interference Report — Generates reports on the project control database. clash area,
clash type, and clash approval along with the search criteria specified in the discrimination
data define what interference data is reported. Format files used in this type of report
primarily use D prefixed indices. This report is generated using the Interference
Manager/Checker.

Report Format File

The reporting process is driven by a format file that determines the contents and format of the
report. It must be created with a text editor prior to report processing.
The format file is a standard ASCII file which contains all the needed criteria for creating the
actual report, such as text position, special indices for input into the report, and sorting
instructions for the indices.
Format File Syntax

The format file is based on fields. A field contains a complete description of a given piece of data
to be placed in an ASCII report file.
Each line of the format file contains the entire description of one field. All fields are independent
of each other; if they have a common order in the report, you are responsible for placing these
fields in such a way that the orders match in the report. In other words, you are responsible for
defining your format file in such a way that your columns and headings will fall under one
another.
Each line in the format file can contain the following data:
Field _Function,Row, Col ,Field _Len,Data _Type, Field _Type, [Buffer],
[Rows/Page], [Spacing]
(Brackets [] indicate data that is only used for certain field types; all other data is required in
every field type.)
Syntax Example

Definitions
Field_Function
 0 Null Field — Used to send a data field (index) to sort on an unreported item.
 1 Page Field - All Pages — Places the specified field once on every page of the report.
 2 Page Field - First Page Only — Places the specified field once on the first page of the
report.
 3 Page Field - Last Page Only — Places the specified field once on the last page of the
report.
 4 Output Field — Places the specified field a variable number of times on every page of the
report based on rows/page and spacing.
 5 New Page Marker — Forces a new page (form feed) after all the previous statements
have been processed. All the lines in the format file after this marker are placed on a new
(repeated) page. In other words, this enables you to append a complete format file to the
previous format file and use the same data sources and sorting as the previous lines of the
format file.
 6 Continuous Page Marker — Forces everything after this marker in the format file up to a
New Page Marker or the end of file to be continuously output as one page. The specified
fields are continuously output without any page divisions. (This code overrides the value for
Rows/Page)
This function can be used to generate an intermediate data file in a fixed form that contains
only raw data (without headings and other annotation). This output can then be used as
input to your own report generation software.
 7 Turn On Output Field Appending Control — Forces all output fields after this marker in the
format file to begin after the previous output field (above 7) is completed, that is, all output
fields will initially begin at the last output fields finishing row.
 8 Turn Off Output Field Appending Control — If7 is in effect for an output field this code will
turn the effect off making output fields normal.
 9 Start of output field loop
 10 End of output field loop — Repeats all output fields defined between codes 9 and 10 until
out of data or the maximum number of lines per output field has been exceeded by the
number of lines of data between the 9 and 10 codes. These options are used to prevent
control sorts from breaking to a new page by using the remaining space on the page before
proceeding to a new page.

Row
Starting line number to be used in placing the field in the report. The maximum number of rows
in a report is 66.
Col
Starting column number to be used in placing the field within the specified row. The maximum
number of columns in a report is 132.
Field_Len
The maximum number of characters that a field can occupy for the active row. The starting
column plus the field length must not exceed 132. A negative value will truncate a field rather
than wrap around a field (default). If the text being placed in the field exceeds the field length,
the text is continued on the next row indented one space (col + 1) until it is completed or the
page ends.
Data_Type
Code used to determine the type of translation required to convert the data to text. (Refer to the
index listings to determine the applicable data type for a particular attribute.)
 1 character or '[Am]', where m is the number of characters
 2 single precision integer or '[Im]'
 3 double precision integer or '[Im]'
 where m is the number of characters for the integer field
 4 single precision decimal (float) or '[Fm.n]'
 5 double precision decimal (float) or '[Fm.n]'
where m is the total number of characters for the decimal value including the decimal point
and n is the number of decimal places
Optional text can precede and/or follow the formatted data type within the quotation marks.
'optional text [Format] optional text'
[Format] can be any legal FORTRAN format statement that matches an expected output.

Field_Type
1. 1 Text Field. Sets the buffer for hard-coded text.
2. 2 Data Field. Sets the buffer for an index number or code used to generate the data to be
placed in the field.
3. 3 Generate Date/Time. No buffer required. When the report is generated, the system date
and time is placed at the designated row/col position.
4. 4 Generate Page Number. No buffer required. When the report is generated, the system
calculates the page number and places the number at the designated row/col position.
5. 5 Generate Date. No buffer required. When the report is generated, the system date is
placed at the designated row/col position.
A negative value will underline the generated output for the field. (This causes the report to be in
a stream line feed file, rather than a stream carriage return file. This may impact an existing
interface to a material control system.)
[Buffer] = Field Definition

The form of the buffer depends on the value for Field_Type.
 Hard coded text is enclosed in single quotes (').
 For MTO reporting, the first character of the index is always A or B. Refer to the description
of the indices for MTO Reporting (with implied materials).
 For spec reporting, the first character of the index is always C. Refer to the description of the
indices for Spec Reporting. These indices are also used for the Table Checker.
 For project and interference reporting, the first character of the index is always D. Refer to
the description of the indices for Project and Interference Reporting.
[Rows/Page]
This setting is only required for output fields. It indicates the number of vertical spaces (lines) in
which to repeat the field contents on a given page. For example, a setting of 20 reserves 20
lines starting from a given row for use in placing the field contents (dependent on spacing).
This does not take into account the extended fields due to exceeded field length.
This is NOT the total number of times that the field is repeated (that value is based on number of
occurrences for the specified attribute); it is only the vertical space allotted for repeating the field
on a page.

[Spacing]
This setting is only required for output fields. It indicates how much space (in rows) is allowable
between repeated fields. This is useful for reserving space for extended fields due to exceeded
field length.
(Rows/Page)/Spacing = the number of times an output field can appear on a page. For example,
if Rows/Page=40 and Spacing = 2, 20 occurrences of the specified attribute are placed on a
page (until the number of occurrences is reached).
Optional Report Type Line

There is an optional line that will determine the type of report the format record creates. It must
be the first line of the format file when used. This line contains an integer variable that
corresponds to a name in the standard note type 1720 in the Standard Note Library. You can
modify the standard note type 1720 to add report types. For instance, the following line would
define the report type as Piping Components MTO Report:
report_type=689
Output Fields
Most report formats involve reporting multiple variables for a given component. This is
accomplished by using output fields (Field_Type = 2) with the necessary index numbers.
Each field is processed independently of the other fields on the report; there are no safeguards
to assure that information in different fields corresponds to the same item. Therefore, you are
responsible for placing these fields in such a way that the orders match in the report. To ensure
that items match, you should make sure that the same number of common items are reported
on each page. The Rows/Page divided by the Spacing determines the number of times an
output field can appear on a page. Therefore, all the common fields should use identical settings
for Rows/Page and Spacing.
The Spacing enables you to reserve space for extended fields due to exceeded field length. For
example, if you use a Field length of 20 for a field which may be up to 50 characters long, you
should set the spacing at 3 to leave adequate space for any
If there is no data for the specified output field(s) on a page, that page will not be printed.
Sample Format Files

Different format files are used by the system to generated specific types of reports. The
following sections explain all of the delivered sample format files, their delivery locations, and
what type of report they generate. In some instances, report output is also included.

Sample MTO Report Format Files

The following files are provided in the product delivery in win32app\ingr\pdreport\sample
directory.
 segment.fmt — This report format includes piping segment data. It demonstrates 'control'
sorting and output field 'looping' (field functions 9 and 10).
This report format reports a list of piping segments grouped by the Model Builder's
alphanumeric description id. The report includes all piping lines that are associated with a
specific Model Builder alphanumeric input file.
(report type = 687)
 piping_a.fmt — This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, nuts, and welds. It demonstrates the use of 'standard' output
fields.
This report includes each category of data in a fixed area of a repeated report page using
'normal sorting' and 'standard output fields' (field function 4).
(report type = 689)
 piping_b.fmt — This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, nuts, and welds. It demonstrates the technique for grouping
blocks of output fields on the same page of the report.
This report format reports data similar to 'piping_a.fmt'. It differs only in that it demonstrates
another method to format the data on the repeated page of the report.
(report type = 689)
 piping_c.fmt — This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, nuts, welds, pipe supports, implied piping components,
equipment, and nozzles. It demonstrates the use of different pages of output within one
report.
This report format reports data similar to 'piping_b.fmt' with the addition of pipe_supports,
implied piping components, equipment, and nozzles. It uses 'page break markers' (field
function 5) to break each category of data onto a different repeated page of the report.
(report type = 689)
 piping_d.fmt — This report format reports the material descriptions for piping components,
pipes, instrument components, pipe supports, gaskets, and bolts.
This report format uses identical report indices to create two columns to continue data on
the same report page. It also uses page breaks to separate the different categories of data
onto different repeated pages of the report.
(report type = 689)
 piping_e.fmt — This report format reports data similar to 'piping_c.fmt', but without any
equipment and nozzle data.
This report format uses a 'continuous page marker' (field function 6) to create a report with
no page boundaries and continuous output (typically used for creating a neutral file format).
It also demonstrates the use of report indices to create a summary of standard notes used in
the report.

(report type = 689)

 piping_f.fmt — This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, and pipe supports similar to 'piping_e.fmt'.
Each category of data is grouped (using 'global control sorting') under a common line
number label for each page of output. It uses 'output field appending' (field functions 7 and
8) to have the different categories of data reported on the same page and column of output.
(report type = 689)
 piping_g.fmt — This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, and pipe supports similar to 'piping_f.fmt' with the same line
number grouping.
This report format uses 'output field looping' (field functions 9 and 10) to utilize all of the
report page space available. The report includes a line number followed by all components
that are associated with that line number label with one or more line number labels being
reported per page, depending upon the amount of data and the space available.
(report type = 689)
 weight.fmt — This report format includes weight and center of gravity data for piping
components, pipes, instrument components, gaskets, bolts, pipe supports, implied piping
components, and equipment.
The output is similar in format to 'piping_e.fmt' and demonstrates the weight and cog
calculation reporting indices.
(report type = 689)
 equip_a.fmt — This report format reports equipment data (including location data) and
nozzle data (including location and orientation data). It demonstrates the full range of
equipment and nozzle reporting indices.
(report type = 661)
 weldno.fmt — This format reports weld information, such as the weld number, type and the
first and second connect point NPD.
 project_a.fmt — This format reports project information such as the client and project
location and uses information from the Drawing Management Data table and the Drawing
Revision Data table for reporting.
Sample Spec Report Format Files

The following files are provided in the product delivered in the win32app\pddata\sample\format
directory.
 piping_rdb.fmt — This report format includes piping material class data and piping
commodity data from the Material Reference Database. It reports the 'partial' (without
embedded commodity code labels) material descriptions.
(report type = 601)
 tbl_chk_1.fmt — This report format includes Table Checker data for one piping material
class. It reports the piping commodities with the dimension tables and Piping Eden modules
used, including a list of all entries read in the dimension tables.

This report also includes a list of all dimension tables and Piping Eden modules that were
required for those piping commodities, but not available in the Reference Database. This
report format is a combination of the following report formats tbl_chk_2.fmt, tblk_chk_3.fmt,
and tbl_chk_4.fmt. It provides full Table Checker output for a specific piping materials class.
(report type = 601)
class. It reports the dimension tables and Piping Eden modules used by each piping
commodity in that piping materials class.
(report type = 601)
class. It lists all entries read in dimension tables.
(report type = 601)
class. It includes a list of all dimension tables and Piping Eden modules used by the piping
commodities in that piping materials class.
This report also includes a list of all dimension tables and Piping Eden modules that were
required for those piping commodities, but not available in the Reference Database.
(report type = 601)
Sample Project Control Report Format Files

The following examples are delivered in the win32app\pdprojec\sample directory.
 model_mgt.fmt — This format file reports model management data.
 draw_mgt.fmt — This format file reports orthographic drawing management data.
 iso_mgt.fmt — This format file reports isometric drawing management data.
 iso_rev.fmt — This format file reports isometric drawing revision management data.
Sample Interference Report Format File

The following example is delivered in the win32app\pdclash\sample directory.
 clash_mgt.fmt — This format file reports interference checker data.
Sample P&ID Consistency Check Report Format File

The following example is delivered in the win32app\pddesign\sample directory.
 pid_cmprpt.fmt — This format file specifies the format of the title page and heading for
each page of the P&ID Consistency Check reports. The remainder of the report is
predefined by the product.
What Happens When I Report On a Component?

When you place a component the system writes the engineering data for the component to the
design database. For the gate valve placed in Chapter 4, the system writes information to the

Piping Segment Data table and the Piping Component Data table. When you create a Material
Take-Off (MTO) report using the Report Manager the system will use this data and information
in the project reference data for reporting.
In addition to the engineering data in the design database, PDS 3D uses the Material
Description Library and the material data in the Material Reference Database to provide material
descriptions for commodity items and specialty items.
Material Descriptions
The material description data is made up of four major parts:
1. Material Tables in the Material Reference Database - These database tables (211 and
212) contain commodity definitions which enable you to further classify the commodity items
defined in the Piping Job Specification. This database information tends to be
customer-specific.
 Piping Commodity Size-Dependent Material Data (211)
The Size-Dependent Data table contains the data for a specific commodity item that is
dependent on the commodity code, nominal piping diameter, and schedule/thickness. It
is used for miscellaneous reporting and interfaces to material control, stress analysis,
and isometric drawing extraction.
 Piping Commodity Implied Material Data (212)
The Implied Material Data table contains the implied material data for a specific
commodity item that is dependent on both the commodity code and nominal piping
diameter range. This data is used for generating implied materials for MTO reporting

and material control. It is not used for welds, bolts, nuts, or gaskets, but is reserved for
other types of implied material, such as caps or stubs, for a specific commodity item. It
is also used for reporting the implied components of a commodity item (such as cap
screws).
2. Short Material Description Library - This library contains the short bill-of-material (BOM)
descriptions for all piping commodity items and the description addenda for taps. The short
material descriptions can be up to 240 characters in length.
3. Long Material Description Library - This library contains the long bill-of-material
descriptions for all piping commodity items. The long material descriptions can be up to 500
characters in length.
4. Specialty Material Description Library - This Library contains the material descriptions for
any piping specialties, in-line instruments, or pipe supports which are reported by MTO or
material control. These material descriptions are job specific and are accessed by the
specialty item's tag number. The specialty material descriptions can be up to 240 characters
in length.
The material description data in these files is used for reporting and material control and is not
required for the interactive placement of symbols in the model. This data is normally accessed
during a batch (non-interactive) process.
Commodity Codes
The system uses the commodity code as an index to access the descriptions in the material
description libraries. You can use the commodity code defined in the Piping Commodity
Specification Data table (Table 202 attribute 18) or a user-defined commodity code defined in
the Size-Dependent Material Data table (Table 211 attribute 7).

The source of the commodity code and other processing options for reporting are defined for a
model with the Material Takeoff Options form of the Project Data Manager.
The commodity code represents that set of parameters that completely describe a commodity
item, exclusive of nominal piping diameter and thickness. The character length for the
commodity code is determined from the character length of the commodity code in the Size
Dependent Data table of the database, or from the character length of the commodity code in
the Piping Commodity Data table of the database, depending on which is being used to access
the material descriptions.
The delivered commodity codes use a 10 character code to fully identify the item. The first letter
of the commodity code identifies the basic type of component, such as a valve or flange. The
remaining characters provide a detailed description of the component. The first character
designations are:
B Flanged and Misc. Fittings Q Socket End Fittings
D Fire and Safety Components R Tubing Fittings
E Steam Specialties S Socketwelded Fittings
F Flanges T Threaded Fittings
G Flanged Specialties U Underground Fittings
H Strainers V Valves
M Misc. Wetted Components W Welded Fittings
N Misc. Non-Wetted Components X Gaskets
O Tubing and Hose Y Bolting
P Pipe

Examples
Refer to the PDS Piping Component Data Reference Guide for a complete listing of the
delivered commodity codes.
You can use the delivered commodity codes or create your own naming scheme. Regardless of
the scheme used, all the codes must be unique and there must be an exact match between the
commodity code specified for an item in the Material Reference Database and commodity codes
used to define the material descriptions in the Material Description Library.
Implied Data
When the system creates a bill of materials for the elements in a model it lists both the items
physically defined in the model and any implied items which are associated with the physical
items. Implied materials can be defined in any of the following ways.
 Mating Implied Data (gaskets, bolts, and welds)
During reporting, the system scans the components and their relationship to determine any
mating implied material. The system uses a set of rules to determine the implied materials
based on the end conditions of mating components. These rules are described in detail in
the Report Manager (PD_Report) Reference Guide.
Item definitions for mating implication such as bolts and gaskets are defined in the Piping
Commodity Specification Data Table (pdtable_202) of the Specification/Material Reference
Database.
 Spec Implied Data

An asterisk(*) in front of a commodity code in the Piping Commodity Specification Data

(PCD) indicates that there is another line item in the PCD for the implied component. For
example, a lap joint flange and stub end. The lap joint flange is placed in the model but the
stub end is not. However, the stub end will show up in reports.
This is a Parent/Child relationship with a one-to-one relation.
Parent = option number
Child = 5000 + parent option number
 Table 212 Implied Data
A plus (+) in front of a commodity code in the PCD tells the software to look in table 212 for
that commodity code. This method indicates a primary component which has one or more
associated implied components.
This is a Parent/Child relationship with a one-to-many relation.
 Commodity codes with neither an * or a + prefix in the PCD, indicate a commodity item that
has no associated implied components.
Report Output
The following is a sample report using the format file piping_a.fmt. It reports on a very simple
pipeline containing the component examples covered in Chapter 4 and the connecting pipes.

Material Takeoff Reporting (Report Manager)

Material Takeoff reporting (with implied materials) generates reports on PDS piping and
equipment models involving data from the Design Database, Reference Database, Project
Database, and Material Description Libraries. This type of report also includes implied mating
data, such as bolts, gaskets, and welds by determining the connectivity of the piping and
equipment. Format files used in this type of report primarily use A and B prefixed indices. This
report is generated using Report Manager.
The active Piping Materials Class must be defined for a model for MTO processing to
work. Before creating an MTO report for a model or set of models, the Piping Materials Class
should be set in the active segment data for each model and the setting should be saved with
File Design.
The sample format files for creating MTO reports are: segment.fmt, piping_a.fmt through
piping_g.fmt, weight.fmt, equip_a.fmt, and weldno.fmt and are delivered in the
win32app\pdreport\sample directory.
Sample MTO Format (piping_g.fmt)

report_type=689 ! Piping Components MTO Report
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,1,50,-40,1,1,’PDS MTO REPORT’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
2,3,10,-40,1,1,’Corporate Headquarters’
2,4,10,-40,1,1,’Intergraph Corporation’
2,5,10,-40,1,1,’Huntsville, Alabama 35894-0001’
2,6,10,-40,1,1,’(205)730-2000’
2,3,90,-20,1,2,B**Q5
2,3,110,-20,1,2,B**Q9
2,4,90,-20,1,2,B**Q6
2,5,90,-20,1,2,B**Q7
2,6,90,-20,1,2,B**Q8
1,8,1,-25,1,-1,’Commodity Code’
1,8,27,-16,1,-1,’Qty/Length’
1,8,45,-10,1,-1,’1st Size’
1,8,57,-10,1,-1,’2nd Size’
1,8,69,-63,1,-1,’Material Description’
9
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BI2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BB2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*I2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BT1G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BX1G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B**K2G1,45,2

7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*S2G1,45,2
8
4,12,1,-25,1,2,BG8S2,45,2
4,12,27,-16,2,2,BS,45,2
4,12,45,-10,1,2,BN49S3,45,2
4,12,57,-10,1,2,BN-49S4,45,2
4,12,69,63,1,2,BM1S5,45,2
7
4,12,1,-25,1,2,BA12S2,45,2
4,12,27,-16,1,2,BA22,45,2
4,12,45,-10,1,2,BA7S3,45,2
4,12,69,63,1,2,BF1S4,45,2
7
4,12,1,-25,1,2,B*G2S2,45,2
4,12,27,-16,2,2,B*O,45,2
4,12,45,-10,1,2,B*L55S3,45,2
4,12,57,-10,1,2,B*L-55S4,45,2
4,12,69,63,1,2,B*K1S5,45,2
7
4,12,1,-25,1,2,BT13S2,45,2
4,12,27,-16,2,2,BV,45,2
4,12,45,-10,1,2,BT2S3,45,2
4,12,57,-10,1,2,BT23,45,2
4,12,69,63,1,2,BT21S4,45,2
7
4,12,1,-25,1,2,BX12S2,45,2
4,12,27,-16,2,2,BZ,45,2
4,12,45,-10,1,2,BX4S3,45,2
4,12,57,-10,1,2,BX5S4,45,2
4,12,69,63,1,2,BX20S5,45,2
7
4,12,1,-25,1,2,B**J7S2,45,2
4,12,27,-16,1,2,B**O,45,2
4,12,69,63,1,2,B**M1S3,45,2
7
4,12,1,-25,1,2,B*P12S2,45,2
4,12,27,-16,2,2,B*R,45,2
4,12,45,-10,1,2,B*S11S3,45,2
4,12,69,63,1,2,B*U1S4,45,2
10
5
1,3,1,-13,1,1,’Date/Time :’
1,3,14,-23,1,5
1,3,50,-40,1,1,’PDS MTO REPORT’
1,3,120,-6,1,1,’Page: ’
1,3,127,-3,2,4
1,11,1,-34,1,-1,’GRAND TOTALS’
1,13,1,-15,1,-1,’Components’
1,13,20,-15,1,-1,’Pipes’
1,13,40,-15,1,-1,’Instruments’
1,13,60,-15,1,-1,’Gaskets’
1,13,80,-15,1,-1,’Bolts’

1,13,100,-15,1,-1,’Pipe Supports’
1,14,1,-15,2,2,BST
1,14,20,-15,2,2,BRT
1,14,40,-15,2,2,B*OT
1,14,60,-15,2,2,BVT
1,14,80,-15,2,2,BZT
1,14,100,-15,2,2,B*RT

Sample MTO Output

Date/Time : 15-Apr-93 PDS MTO REPORT Page: 1
Corporate Headquarters PDS Project

tcproj
Intergraph Corporation tc101
Huntsville, Alabama 35894-0001 RoXXon Corp.
(205)730-2000 Nth Projector
Commodity Code Qty/Length 1st Size 2nd Size Material Description
LINE NUMBER: P403-1/2IN-1C0031-N
PDS 3D Theory — April 2002
POCAAAOAAE 1 1/2IN 1/2IN Nipple, PE, S-160, 3" long, ASTM-A106-B
PPCAAAOAAE 1 1/2IN 1/2IN Nipple, PE, S-160, 6" long, ASTM-A106-B
VAUHAHGAAA 2 1/2IN 1/2IN Gate valve, CL800, SWE/FTE, BB, OS&Y, ASTM-A105, trim 8,
Smith
800
LINE NUMBER: P403-3/4IN-1C0031-N
POCAAAOAAE 9 3/4IN 3/4IN Nipple, PE, S-160, 3" long, ASTM-A106-B
TPAZVZZAAA 7 3/4IN - Plug, MTE, ASTM-A105, ANSI-B16.11
VAUHAHGAAA 9 3/4IN 3/4IN Gate valve, CL800, SWE/FTE, BB, OS&Y, ASTM-A105, trim 8,
Smith
800
38-PI-6 1 3/4IN 3/4IN *
39-PI-9 1 3/4IN 3/4IN *
LINE NUMBER:
P403-3IN-1C003
1-N
FAAABAWAAA 2 3IN 3IN Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD
bore
XDAABZZQSG 1 3" - Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph
filled,
CS center ring, API-601
YZZZHZZFFF 4 5/8" 3 3/4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H

hvy hex nuts
LINE NUMBER:
P403-4IN-1C003
1-N
1 4IN 4IN *
bore
VAABAHCCAA 1 4IN 4IN
47
VBABAHCFAA 1 4IN 4IN Globe valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim
8,
Crane 143
WAAAAAWAAA 2 4IN 4IN 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
WRBAAAWAAA 2 4IN 3IN Eccentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB,
ANSI-B16.9
WTAAAAWAAA 1 4IN 4IN Tee, S-STD, BE, ASTM-A234-WPB,

ANSI-B16.9
LINE NUMBER:
P403-4IN-1C003

1-N
PAAAAAWAAA 4’ 8 9/16" 4IN Pipe, S-STD, BE, ASTM-A53-B Type S
filled,
YZZZHZZFFF 32 5/8" 3 3/4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H

hvy hex nuts
supp2 1 4IN *
LINE NUMBER:
P403-6IN-1C003
1-N
bore
FGPBBAWAAA 2 6IN 6IN Orifice flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.36,
WN, one
0.5" SWE tap, S-STD bore
GJGABZZADA 1 6IN 6IN Spectacle blank, CL150, RFTBE, ASTM-A516-70, API-590Z1,

0.75
thk
VAABAHCCAA 4 6IN 6IN
47
VCABAHOBAA 2 6IN 6IN Check valve, CL150, RFFE, BC, swing, ASTM-A216-WCB, trim
8,
Pacific 180
WAAAAAWAAA 9 6IN 6IN 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
WADAAAWAAA 1 6IN 6IN 45 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
WOAAAAWAFA 1 6IN 4IN Weldolet, S-STD x S-STD, BE, ASTM-A105
WOBSABQAFA 4 6IN 3/4IN Sockolet, CL3000, BE/SWE, ASTM-A105
WRAAAAWAAA 4 6IN 4IN Concentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB,
ANSI-B16.9
WTAAAAWAAA 3 6IN 6IN Tee, S-STD, BE, ASTM-A234-WPB,

ANSI-B16.9
PAAAAAWAAA 131’ 1 3/16" 6IN Pipe, S-STD, BE, ASTM-A53-B Type S
filled,
XDABBZZQSG 1 6" - Gasket, CL300, G653, 0.125" thk, 304 spiral wnd, graph
filled,
YZZZHZZFFF 80 3/4" 4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H

hvy hex nuts
YZZZHZZFFF 20 3/4" 5" B31, ASTM-A193-B7 studs w/ASTM-A194-2H
hvy hex nuts
supp1 1 6IN *
LINE NUMBER:
P403-6IN-1C003
1-N
supp3 1 6IN *
GRAND TOTALS
Components Pipes Instruments Gaskets Bolts Pipe Supports
8719 2 18 136 3

Understanding Implied Items

This section discusses the various types of implied items and a few miscellaneous items and
how they are reported. It also covers some of the features within the PDS suite of products that
are outside of the Report Manager module.
When reporting on components, there are sometimes additional parts necessary to complete
that component that are not represented graphically in the piping model or stored in the Piping
Design database. These additional components are mating, spec, or table implied items.
If an implied item is part of an implied connection, it is called a mating implied item. Otherwise,
the naming conventions for implied items are defined by the location where the implied item data
is retrieved. The system retrieves these implied items from either the Piping Component
Specification Data Table (pdtable_202) or from Piping Commodity Implied Material Data Table
(pdtable_212). The following sections explain the mating, spec, and table implied items and how
data is retrieved for each:
Mating Implied Items

Mating implied items are found by the system while scanning related mating components and
defining the items necessary to complete those connections. The following items termed mating
implied.
 Bolts
 Gaskets
 Nuts
 Welds
The Material Takeoff Options form is part of the Project Administrator module, and its setting
greatly affect the way mating implied items are reported.
For more information on mating implied item reporting see the Material Takeoff Options
section.
'*' Spec Implied Items

Commodity codes prefixed by an '*' in Material Description Code field in the Piping Job
Specification indicate a primary component that has one associated spec implied item.
 The definition of the spec implied item has the same search parameters as the primary
component, except in the following instances:
 The value for the option attribute of the spec implied component is equal to 5000 plus
the option value for the primary component.
 The definition of the spec implied component can be divided into several NPD ranges.
 The output parameters of the spec implied component may differ from those of the primary
component in the following instances:
 Only the primary component is included in the model depiction; the spec implied
component only appears in reports.

 Only the primary component is displayed on an isometric drawing; the spec implied
component only appears in the materials list.
 The commodity codes prefixed by an '*' are used to define:
 Stub-ends used in conjunction with lap, slip-on, and plate flanges.
 Jacketed components when the outer jackets are obtained independently of the internal
components.
'*' Spec Implied Example
Both the primary component and the implied item in the following Piping Job Specification
example would be reported:
! AABBCC ————Green CP———– ————Red CP————- Commodity Model Geo Mat Wt FF
! Code Opt From To Prp Rating Sc/Th TS From To Prp Rating Sc/Th TS code TMx Code Std Mod Grd Cd FC Nte
lng
PIPING 1 2 6 301 - S-STD 5 ------*PAAAAAWAAA - PIPE 100 100 142 52 15 - 240
PIPING 5001 2 6 301 - S-STD 5 ------newcommcode - PIPE 100 100 142 52 15 - -
'+' Table Implied Items

Commodity codes prefixed by a '+' in the Commodity Code field in the Piping Job Specification
indicate the primary component has one or more associated table implied items. The system
searches for the definition of the implied item in the Piping Commodity Implied Material Data
(pdtable_212), which contains the commodity code of the primary component, the applicable
NPD range, and the commodity code of the table implied components.
To use this option, pdtable_212 must be loaded.
 The output parameters of the table implied item may differ from those of the primary
component in the following situations:
 If only the primary component is included in the model depiction, the table implied items
appear only in the report.
 If the primary component is displayed on an isometric drawing, The materials list only
includes the short description of the primary component. The descriptions of the table
implied items are displayed as notes on the drawing, pointing to the primary component.
The text for these notes is derived from the short descriptions of the applicable
commodity codes. The short description can contain $ symbols to force the text to a
new line in the label.
 The commodity codes prefixed by a '+' are used to define the following items: –
 Cap screws for valves requiring caps.
 Safety covers for required components.
 Housings for required components.

'+' Table Implied Example

First, notice the '+' indicating a table implied item in a line taken from the Piping Job
Specification.
6Q2C01 1 3 24 21 CL150 NREQD 5 - - 421 CL150 MATCH 5
+FAAABAWAAA - FWN 35 - 150 52 15 -
Secondly, notice the table entries that are related to the primary component,
F ! Implied data for table 212
Single_Spacing
Sequence= 2 3 4 5 6 7 8 9 10
!Comm Code GFr GTo RFr RTo Imp Code Qty FC Note
FAAABAWAAA 2 12 0 0 IMPFLG2A 1.5 7 -
FAAABAWAAA 2 12 0 0 IMPFLG2B 0.5 7 -
FAAABAWAAA 2 12 0 0 IMPFLG2C 1.0 7 -
VAABAHCCAA 2 2 0 0 IMPVAL2A 0.5 7 -
VAABAHCCAA 2 2 0 0 IMPVAL2B 2.5 7 -
PAAAAAWAAA 2 2 0 0 IMPPIP2 1.0 7 -
WAAAAAWAAA 2 2 0 0 IMPELB2 2.0 7 -
WRAAAAWAAA 3 12 2 10 IMPRED 1.0 7 -

Material Takeoff Options

The Material Takeoff Options form of the Project Data Manager specifies the source of
commodity information, units for bolt length and diameter, and specifies item names used to
reference a commodity item in the Piping Job Specification and Graphic Commodity Library.
These options are essential to material takeoff reporting.
Refer to the Project Administrator Reference Guide for more information on the Project Data
Manager. Refer to the Reference Data Manager Reference Guide for information on the stud
table, bolt length calculations, and the bolt commodity code table.
Operating Sequence
1. Specify the bolt information.
Bolt Length Roundoff — Select the option for the means to determine the reported bolt
length.
 Preferred Bolt Length Table—the system uses the preferred bolt length table.
 Bolt Roundoff Factor—the system rounds up the calculated length by the specified
factor.
 No Roundoff—the exact length is used.

Length Calculation — Select the method to be used in calculating bolt length. The bolt
length is read from the stud table. The table name can be determined using the rating and
table suffix (Almost Precise) or using termination type, rating, and table suffix (Precise).
This also affects bolt lengths for lap joint flanges.
Bolt Commodity Code Select the method to be used in determining the commodity code
for bolts for use in material take-off. Piping Job Specification or Bolt Commodity Code
Table.
Bolt Diameter Units — Select the system of units for bolt diameter.
Bolt Length Units — Select the system of units for bolt length.
2. Gasket Search
Select this field to toggle the setting between Default or Alternate.
3. Field Fit Length
Select this field to toggle the setting between Off or On. If this field is On, the system
displays a field to input the Field Fit Length Table name.
4. Commodity Code Select this field to toggle the setting between Size Independent or Size
Dependent.
For a detailed description and graphical examples of how these options work, see the
Size Dependent and Independent Reporting section.
When the Size Dependent option is enabled, the system provides two additional options.
Source of Implied Data This option specifies the source of the commodity code for
reporting implied data from the Piping Commodity Implied Material Data Table.
The default option (System Commodity Code) tells the system to use the commodity code
defined in the Piping Commodity Specification Data Table (pdtable_202 attribute 18).
The Size-Dependent Commodity Code option tells the system to use the commodity code
defined in the Piping Commodity Size-Dependent Material Data Table (pdtable_21 1
attribute 7).
Source of Material Description —This option specifies the source of the commodity code
for reporting a component's material description.
The default option (System Commodity Code) tells the system to use the commodity code
defined in the Piping Commodity Specification Data Table (pdtable_202 attribute 18). This
option will result in a smaller Material Description Library.
The Size-Dependent Commodity Code option tells the system to use the commodity code
defined in the Piping Commodity Size-Dependent Material Data Table (pdtable_21 1
attribute 7). This option will result in a larger Material Description Library.

5. Key in the commodity item names to be used for reporting mating implied materials.
Gasket Commodity Name
Bolt Commodity Name
Nut Commodity Name
6. Key in the Eden Module names.
Bolt Data Module — This field defines the name of the Eden Module which determines the
values for the bolt diameter, the number of bolts per mating, and the bolt extension.
Flange Data Module — This field defines the name of the Eden Module which defines
values for flange outside diameter, thickness, and seat depth.
7. Key in the bolt length values. The display of these fields is dependent on the setting for Bolt
Roundoff Option.
Bolt Length Table — This table defines the low and high range for calculated bolt lengths
and corresponding preferred or purchased lengths of the bolt. This field is only used if
Preferred Bolt Length Table is the active Bolt Roundoff Option.
Bolt Length Roundoff Factor — This field defines the value for the bolt roundoff factor in
subunits. This value is only used if Bolt Roundoff Factor is the active Bolt Roundoff Option.
8. Select Confirm () to accept any changes to the Material Takeoff options.
Labels in Material Descriptions

The material descriptions for commodity items can be loaded in the Material Description library
via neutral files. The neutral file includes a unique Commodity Code followed by at least one
space and a description enclosed in single quotes. It also contains the implied material
descriptions associated with a commodity item.
The following shows a portion of the neutral file used to load the Short Material Descriptions.
! DEFINE SHORT DESCRIPTIONS
! Date/Time: Thu Apr 23 14:16:58 1992
! Processed Library /usr/newpipe/refdata/us_shbom.l
!Cmdty Code ====================================Description======================
CHAIN_1003 ’Chainwheel operator each with [422] of total chain length for [426] NPD valve with commodity code [400]’
CHAIN_1005 ’Chainwheel operator each with [422] of total chain length for [426] NPD valve with commodity code [400]’
CHAIN_1251 ’Chainwheel operator each with [424] of total chain length for valve with tag no [402]’
DAABAXAABE ’Monitor, CL150 FFFE, ˆstation type, 4" CL150 in-let by 2.5" NHT stainless steel outlet w/stainless
steel stem
lock knobs with 0.75" coupling in base, w/shapertip nozzle, Stang BB0309-21’

DAABAXAABF ’Monitor, CL150 FFFE, ˆstation type 4" CL150 in-let by 2.5" NHT stainless steel outlet
w/stainless steel
stem lock knobs with 0.75" coupling in base, w/fog nozzle, Stang BB0309-21’
DACBAXABBC ’Monitor, CL150 FFFE, êlevated type, free standing, 4" CL150 in-let by 2.5" NHT stainless steel
outlet, [427],
w/drain coupling, w/shapertip nozzle and two reaction supports, Stang BB2999-’
DACBAXABBD ’Monitor, CL300 FFFE, êlevated type, supported, 6" CL300 in-let by 2.5" NHT stainless steel
outlet, [427],
w/drain coupling, w/shapertip nozzle, Stang BB3561’
DBAAAXBAAB ’Fire hydrant, CL125 FFFE, ˆ5" size, counterclockwise open, 4.5" steamer nozzle, two 2.5" hose
nozzles
equipped w/caps and chains, [428], American Darling B-50-B’
DCBGDXEADA ’Hose rack, 300#, FTE, ˆw/valve, wall mount, rt hand w/100 ft hose & fog nozzle, Powhatan 30-333’
DDAXCJDAAA ’Spray sprinkler, MTE, filled cone w/rupture disc, 304, Grinnell, Mulsifyre Projector S-1’
FAAAAAWAAA ’Flange, CL150, FFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’
FAAAAAWWAA ’Flange, CL150, FFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, cement lined, [409]|bore to match|’
FAAABADIIA ’Flange, CL150, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, S-80S bore’
FAAABADIIF ’Flange, CL150, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’
FAAABADNPF ’Flange, CL150, RFFE/BE, ÂSTM-B166-600, ANSI-B16.5, WN, S-80S bore’
FAAABAOAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-160 bore’
FAAABAOABB ’Flange, CL150, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, S-160 bore’
FAAABAOFFH ’Flange, CL150, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, S-160 bore’
FAAABAWAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWABB ’Flange, CL150, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWFFH ’Flange, CL150, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWFFL ’Flange, CL150, RFFE/BE, ÂSTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWGFD ’Flange, CL150, RFFE/BE, ÂSME-SA182-F11, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWIIA ’Flange, CL150, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWIIF ’Flange, CL150, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, [409]|bore to match|’
FAAABAWNPF ’Flange, CL150, RFFE/BE, ÂSTM-B166-600, ANSI-B16.5, WN, [409]|bore to match|’

FAAABBDAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-XXS bore’
FAAADAOAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’
FAAADAOFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’
FAAADAWAAA ’Flange, CL150, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’
FAAADAWFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’
FAAADBDFFC ’Flange, CL150, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-XXS bore’
FAABBADIIA ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, S-80S bore’
FAABBADIIB ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304L, ANSI-B16.5, WN, S-80S bore’
FAABBADIIF ’Flange, CL300, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’
FAABBAOAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-160 bore’
FAABBAOABB ’Flange, CL300, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, S-160 bore’
FAABBAOFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, S-160 bore’
FAABBAOFFH ’Flange, CL300, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, S-160 bore’
FAABBAWAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWABB ’Flange, CL300, RFFE/BE, ÂSTM-A350-LF2, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWFFH ’Flange, CL300, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWFFL ’Flange, CL300, RFFE/BE, ÂSTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWIIA ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWIIB ’Flange, CL300, RFFE/BE, ÂSTM-A182-F304L, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWIIF ’Flange, CL300, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, [409]|bore to match|’
FAABBAWNPF ’Flange, CL300, RFFE/BE, ÂSTM-B166-600, ANSI-B16.5, WN, [409]|bore to match|’
FAABBBDAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-XXS bore’
FAABDADIIJ ’Flange, CL300, RFFE/BE, ÂSTM-A182-F321, ANSI-B16.5, WN, 125 Ra finish, S-80S bore’
FAABDAOAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’
FAABDAOFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-160 bore’

FAABDAWAAA ’Flange, CL300, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’
FAABDAWFFC ’Flange, CL300, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’
FAABDAWFFH ’Flange, CL300, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’
FAABDAWIIJ ’Flange, CL300, RFFE/BE, ÂSTM-A182-F321, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|’
FAADBADIIA ’Flange, CL600, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, S-80S bore’
FAADBADIIF ’Flange, CL600, RFFE/BE, ÂSTM-A182-F316, ANSI-B16.5, WN, S-80S bore’
FAADBAOAAA ’Flange, CL600, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, S-160 bore’
FAADBAOABE ’Flange, CL600, RFFE/BE, ÂSME-SA105, ANSI-B16.5, WN, S-160 bore’
FAADBAWAAA ’Flange, CL600, RFFE/BE, ÂSTM-A105, ANSI-B16.5, WN, [409]|bore to match|’
FAADBAWABE ’Flange, CL600, RFFE/BE, ÂSME-SA105, ANSI-B16.5, WN, [409]|bore to match|’
FAADBAWFFC ’Flange, CL600, RFFE/BE, ÂSTM-A182-F11, ANSI-B16.5, WN, [409]|bore to match|’
FAADBAWFFH ’Flange, CL600, RFFE/BE, ÂSTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|’
FAADBAWFFL ’Flange, CL600, RFFE/BE, ÂSTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|’
FAADBAWIIA ’Flange, CL600, RFFE/BE, ÂSTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|’
The following conventions are used to identify different types of information in the material
descriptions:
 ˆ All information to the left of the carat (ˆ) is used in MTO reporting and isometric
extraction, but is excluded from Spec reporting.
 | | Information appearing in |Pipes| indicates information for Spec descriptions only. This
information is excluded from the descriptions for MTO reporting and isometric extraction.
 [] Information appearing in [brackets] indicates a label type from the Label
Description Library. The system uses the label format to determine the information to be
included in the material description for MTO reporting and isometric extraction. The label
information is never used in Spec reporting.

The following label types are provided in the product delivery:
Label No Data in Label Source of Data
401 Piping sch/thk 1 Pipe
403 Component Sch/thk 1 Component
405 Component sch/thk 1 b Component
407 Component sch/thk 2 Component
409 Component sch/thk 2 b Component
411 Component sch/thk 1 x 2 Component
413 Component sch/thk 1 x 2 b Component
415 Component sch/thk 1 x 3 Component
417 Component sch/thk 1 x 3 b Component
421 Bonnet length Component
423 Reinforcing weld size Component
425 Pad width x pad thick Component
Attributes for mating implied items, specifically bolts and gaskets, are not stored in the Design
Database (dd_projname) where attributes for independent components are stored. You can
insert labels in Material Description Library for bolt and gasket entries, but these labels must be
classified as Piping Component Data labels when they are created.
Although data for bolts and gaskets is not recorded in the Piping Component Data Table
(pdtable_34_x) in the Piping Design Database (dd_projname), bolt and gasket labels are
classified as Piping Component Data labels. The system retrieves the bolt and gasket
information for reporting using related attributes in the Piping Component Data Table
(pdtable_202).
Although all of the attributes for piping components are available when you define a bolt or
gasket label using the Piping Component Data labels option, only the following attributes
contain data that is pertinent to bolt and gasket reporting. The following list displays the
form-attribute/table-attribute relationships which define what data is actually reported from the
Piping Component Data Table (pdtable_202):
Form Attributes Related (pdtable_202)

Attributes
commodity_name commodity_name
option_code option_code

maximum_temp maximum_temp
cp_1_nom_pip_diam gcpjrom_nom_diam
cp_1_end_prep gcp_to_nom_diam
cp_1_outside_diam gcp_end_prep
cp_1_rating gcp_rating
cp_1_sch_thk gcp_sch_thk
table_suffix_green gcp_table_suffix
cp_2_nom_pipe_diam rcpjrom_nom_diam
cp_2_outside_diam rcp_to_nom_diam
cp_2_end_prep rcp _end_p rep
cp_2_rating rcp_rating
cp_2_sch_thk rcp_sch_thk
table_suffix_red rcp_table_suffix
commodity_code commodity_code
model_code model_code
PDS_sort_code PDS_sort_code
bend_radius modifier
geometric_standard geometric_standard
weight_code weight_code
fabrication_cat fabrication_cat
materials_grade materials_grade
standard_note_no_a standard_note_no_a
standard_note_no_b standard_note_no_b
A Label Description Library is delivered in win32app\pdshell\lib\labels. l and should be edited to

suit the needs of your project.

Create Label Attribute Data

The Label Description Library Manager is used to create and revise label data for the PDS 3D
modules. The Create Label Attribute Data form allows you to create and define a label. The Line
and Item fields are used to define the attributes that make up the label and the order of the
attributes within the label.
Set the option at the upper left of the form.

Insert Data — used to add a line or item to the label description.
Delete Data — used to delete a selected line or item from the label description. Edit Data —
used to revise a selected line or item in the label description.

Insert Data
1. Set the option to Insert Data.
2. Set the toggle to Insert after or Insert before.
3. Select Line or Item to Insert Data
Select a line field to create a new line (before or after) the selected line.
—OR —
Select an item field to create a new item in the current line (before or after) the selected
item.
The system activates a form that displays the Attribute Data Types. The following form
illustrates the display for a drawing view specific label.
4. Select Option
Select Piping Component Data to define the attribute data type for the bolt or gasket label.

The system displays the attributes for the selected data type.
5. Enter Data
Select the attribute to be reported from the form. The system sets the Format Data
automatically. You can modify the total length and the number of decimal places (if
applicable).
All of the attributes that apply to gaskets and bolts are listed in the Labels in Material
Descriptions section.
—OR —
For drawing view specific labels, you can select User Keyin Attribute to specify text to be
entered by the user at label creation.
—OR —
Select Text Only and key in the text for a literal expression to be inserted in the label.
—OR —
Select Spacing Only and key in the number of spaces to define spacing between attributes.
6. Repeat the previous step to add additional attribute text information. This allows you to
combine attribute values and pre-formatted text.
You can only define one user-defined key-in in a specific label.
7. Select one of the Optional Data options to specify a modifier to the active format. Master
Units = MicroStation master units, Sub Units = MicroStation sub units.
8. Select Confirm () to accept the specified attribute data.

Delete Data
1. Set the option to Delete Data.
2. Select the line or item to be deleted.
3. Select Confirm () to delete the highlighted line or item. When you select a line, the system
deletes all the associated items.
Edit Data
1. Set the option to Edit Data.
2. Select Item to Edit Select the item to be revised.
The system displays the attributes definition form for the selected item. The active setting is
highlighted or shown in the display fields.
Select an attribute from the form to change the type of data. —OR —
3. Select the Format Data option. You can modify the total length and the number of decimal
places (if applicable).
—OR —
For drawing view specific labels, you can select User Keyin Attribute to specify text to be
entered by the user at label creation.
—OR —
Select Text Only and key in the text for a literal expression to be inserted in the label.
—OR —
Select Spacing Only and key in the number of spaces to define spacing between attributes.
4. Repeat the previous steps to edit additional items.
—THEN — Select Confirm () to accept the edits.
Material Data Publisher

The Material Data Publisher utility (MDP) allows PDS users to generate relational database
tables containing all the material data associated with a PDS model and publish these tables to
a new database schema (MTO_PROJNAME). These tables make the model data available for
easier reporting outside of PD_Report.
The Material Data Publisher uses selection set files to determine what data to publish. The
MDP interface allows you to select specific disciplines, model areas, and models within the
project to publish, and to save different sets of models in separate selection set files.
When the data is published, it can be accessed through ORACLE, SQL, ODBC clients such as
Microsoft Access, and other database utilities for reporting, tracking, and ordering.
The PDS project to be published must contain at least one piping model before running
Material Data Publisher.

Extracting Isometric Drawings
SECTION 10
The PDS Isometric Extraction Software creates piping isometric drawings from 3D piping
models created by the Piping Designer.
The software consists of two principal components:

 Intergraph 3D software packages which create input for ISOGEN and perform other
functions necessary in final drawing creation.
 ISOGEN, which draws the piping isometric and places it in a MicroStation design file and

The software allows you to extract isometrics from a 3D plant model: single isometrics
interactively or multiple isometrics in a batch mode.
The ISOGEN software is designed to be flexible because drawing practices vary from one
company to another. The following features of Intergraph's isometric extraction package allow
you to specify drawing format:
 User-controlled ISOGEN option switches
 The capability to use an alternate or foreign text
 A large set of Intergraph option switches
 User-controlled attribute breaks shown on drawings
 A flexible method for generating notes
 Attribute-driven symbology (solid or dotted lines)
 User-defined component symbology
 User-controlled mapping of attributes to the title block.
In addition to the isometric drawing, the software also generates several nongraphic outputs, the
most important of which is a completely user-definable MTO neutral file. This neutral file is
extremely useful for those who want to combine a material control system with Intergraph's 3D
modeling software.
The above features are collectively referred to as software customization and are dealt with at
length in the PDS ISOGEN Interface Reference Guide.

Overview of Isometric Extraction

This section outlines the software components and how they are organized for interactively
extracting isometrics.

The Intergraph Interface to ISOGEN

The core software module in isometric extraction (both interactive and batch) is the ISOGEN
interface. This program reads data from the 3D model files and generates an input file for
ISOGEN. ISOGEN knows nothing of PDS or any of its files. It reads only the input file created
for it by the ISOGEN interface. While ISOGEN is primarily responsible for generating the
drawing graphics (including dimensioning) the ISOGEN interface is responsible for most
everything else — including note generation, recognition of attribute changes, defining which
symbols to use and so on.
The primary input to the ISOGEN interface is an ASCII file named pdsidf.dat. The interface
reads from this file the piping and equipment models involved, the output isometric file name,
and identification of all of the pipelines in the drawing. The interface also reads in data from the
options file.
The options file consists of a collection of switches, options and tables that gives you some
control over what the ISOGEN interface puts in its output file (called the intermediate data file or
idf) and therefore what appears in the final drawing.
Once this data is read in, the interface collects from the model files all of the components that
make up the piping network. Data from the components is then used to form an internal data
structure which represents the network. Finally, this network is traversed (the software traces a
path through the piping network) and records are generated in the idf. The order of the records
in the idf is in the order of the network traversal. Drawing notes and other features such as bill of
material information are dealt with component by component as the network is traversed.
If the components in the piping models are not properly connected or other problems exist, the
internal data structure will not be properly built and isometric extraction will fail. The HITS report
can help you to find problems in the piping model and tell you when the interface software is not
working properly.
ASCII to Binary Conversion

The Intergraph interface to ISOGEN creates an ASCII data file containing the input to ISOGEN.
Since ISOGEN requires the input data to be in binary format, a program named ISOA_BGEN is
run to convert this ASCII data file to binary. ISOA_BGEN creates the binary output file
FOR036.# which IZOD2 uses to generate the isometric drawing.
ISOGEN
ISOGEN takes the binary input file and generates graphics in a 2D MicroStation design file. The
graphics consist of the completed isometric drawing. ISOGEN can also generate several
nongraphic outputs, including:
 An ISOGEN MTO neutral file
 A parts list (bill of material)
 A cut pipe report
 A component VRS sheet number file
The parts list file contains the same bill of material that is shown on the isometric drawing. It is
possible to turn the drawing bill of material off and attach the printed ASCII file to the drawing
instead. The cut pipe report, which shows the length of each piece of pipe in the line, can be

useful. The component VRS sheet number file is used by the batch extraction software and is
discussed elsewhere.
Batch Software Organization

This section provides an overview of the batch extraction software components and
organization. The purpose of this section is to explain to software support personnel how the
software works so that problems can be tracked down and reported.
The batch extraction software is driven by an executable (pdsidf) and a script file (batch.cmd).
When you submit a batch job using the Schedule Batch Job form the batch extraction is
submitted to a batch queue named PDisocreate. This queue is created with a job limit of 1 and a
priority of 16. You should not change the job limit.
In order to run batch isometric's, the pd_iso.cmd, located in ~pdiso\bin, must define locations for
required software. This script is executed from the batch queue and allows the batch extraction
process to run on a node other than the one from which it was submitted. The following
variables must be exported:
PD_SHELL
PD_ISO
PD_ISOGEN
The Batch Job Input File

The input to the batch procedure is an ASCII data file generated by the Batch Environment
called the Batch Job Input File. This file is structured as shown.
The first record in the file contains a file format version number and the name of the Batch Data
File from which the Batch Job Input file was generated. The software checks the version number
to see if it matches the software version number, and, if it does match, passes the Batch Data
File name on to other software modules as needed.
The second record is called an option record. The option record contains all of the batch
processing options and revision block data that was entered into the BATCH form. Each option
is separated from the others by at least one space. This record contains an exclamation point (!)
in column 1 which flags it as an option record.
The third record holds the name of the default set which was specified in the Create Batch Job
Input form. This record also contains an exclamation point in column 1.

Subsequent records, which initially contain a space in column 1, hold the area and primary line
name for an isometric drawing which will be extracted. After the line is extracted, it is marked by
an asterisk (*) in column 1 to indicate that it has been processed.
The drawing records can be repeated any number of times in the batch job input file. Each time
you select the Accept button from the Create Batch Job Input form, you write out a set of
drawing records to the batch input file. An example batch job input file is shown below.
When a batch iso job is submitted using the Schedule Batch Job form, the batch job input file
name is passed to the pdsidf executable as a parameter. The system then reads the batch job
input file and drawing creation begins.
Line Processing (pdsidf)

Given the options from the batch input file and the identification of the line, two files are created,
seed.dat and pdsidf.dat. These are the same two files that are created during interactive
extraction.
The Project database is accessed to obtain the list of model files, secondary pipeline names, the
seed file names, the options file for the piping area, the output file directory, the iso design file
name and the extraction number for the drawing.
Type 63 information is read from the first piping model in the area specified in each record of the
batch input file. Note that his model may not be the piping model that contains the pipeline being
extracted.
The two files produced are different from the ones produced for interactive extraction. In
pdsidf.dat, the first line name in the line name list is followed by a backslash and the piping area
name. Following the line list is a record that contains the default set name. Next is a record that
contains batch processing options. The last record contains the extraction number for the
drawing.
skiso5
skiso4
skiso6
skiso7
*skiso3
40eqp01
40eqp00
pdssk:h:\proj\iso\isofiles\380105wc. i*
380105\skiso\1
proj
N Y N * * Y * * 04-Aug-1998 *
13
10

In SEED.DAT, the seed iso design file name is followed by records containing the plot request
file name, the output file directory, the output iso file name, extraction number and number of
sections.
pdssk:h: \proj\iso\ref\isoc.def
pdssk:h: \proj\iso\ref\isoc.sed
pdssk:h: \proj\iso\ref\isoc_sml.i
pdssk:h: \proj\iso\isofiles
380105 13
1.fi
The ISOGEN Interface

The ISOGEN interface performs the same function in batch extraction as in interactive
extraction. It generates an Intermediate Data File (IDF), which is the input to ISOGEN. In
addition to the IDF the interface may also produce an mto neutral file and three files containing
text for the drawing title block.
ISOGEN
Isometrics generated by the batch software are always created one sheet to a design file. The
iso design file name is passed to the interface as name.i*. Therefore, the first sheet will be in a
file with the extension .i01, the second in .i02 and so on.
When isometrics are created in batch, you must set Intergraph options block word 4 to 1. This
causes ISOGEN to create a file that identifies which sheet each component in the line is drawn
on. This file (called the sheet data file) is used downstream to split up the mto neutral file by
sheet and also to prepare the segment summary table for each isometric sheet.
Plotting
After drawings are created in batch they can be plotted with the IP_IPLOT plotting software.
To submit a plot, the batch software submits a job to the batch queue named PDisoplot. The job
that runs in PDisoplot actually launches the plot.
Since the plot jobs are launched from a separate batch queue, you can accumulate the jobs in
the queue and release them at some later time. You might also hold the jobs in PDisoplot to
prevent normal production plotting queues from getting loaded down with isometric plots.

SECTION 11
Creating Orthographic Drawings
Designers use the Drawing Manager (PD_Draw) product to create and/or revise orthographic
production drawings. PD_Draw creates windows (drawing views) to the live 3D Models created
with PD_Design and the other modeling products. PD_Draw is used to place annotation labels
identifying intelligent items and model coordinates, to plot the drawings, and to produce reports
for drawings and model data.
The Drawing Manager is used to create and revise orthographic production drawings. It can be
used by any of the 3D disciplines within PDS for drawing management.
A drawing is a sheet or a plot used to describe the design of a model design volume (work
area). Many drawings can be created from one model to completely document a design volume.
A drawing can contain more than one drawing view of a model or models.
A drawing view is a view of a model or models. Each drawing view within a drawing can have a
different scale and each label within a drawing can have a different character size.
You can create a drawing during any stage of the design process. It consists of the reference
model attachments for the model graphics used in the drawing and the graphics for the drawing
itself. The model graphics reside in the design file for that model. These model graphics are
attached to the drawing as reference files through the use of drawing views.

Drawing Manager Features

The Drawing Manager can be used to:
 Create a drawing for any of the PDS 3D disciplines, along with a key plan drawing.
 Create multiple drawing views for a given drawing.
 Revise definition information for existing drawings or drawing views.
 Delete drawings and drawing views
 Place annotation labels on a drawing to identify intelligent items and model coordinates.
 Create hidden-line-removed model graphics.
 Plot a drawing or set of drawings.
 Create a key plan model for the project.
Drawing Manager Setup

Project Setup
A project and all of its accompanying files must be defined with the Project Administrator before
you can use the Drawing Manager. Refer to the Project Administrator Reference Guide for
information on
 Loading PDS 3D products.
 Editing the control script to identify the location of the project data.
 Setting up a project and creating the associated database schemas.
 Accessing the PDS 3D products remotely using NFS.
Model Files
A set of model files for the project must be defined before you can use the Drawing Manager.
Refer to the following documents for information on creating and manipulating PDS 3D Models.
 Piping Design Graphics Reference Guide
 PDS Equipment Modeling Reference Guide
 MicasPlus ModelDraft Reference Guide
 PE HVAC Modeling Reference Guide
 EE Raceway Modeling Reference Guide

Drawing Manager Setup

Complete the following operations before using the Drawing Manager.
Drawing Categories
When a project is created, the Project Administrator copies the default drawing category
names to the project directory. The name of the copied file is drwcats.txt. You can edit this file to
change the names that are displayed for drawing categories.
Although you can modify the drawing category names, the meaning of a specific category
will not be altered by this change.
Cells
The flow arrow symbol for drawing annotation is provided in the cell library
win32app\pdshell\cell\drawing.cel. This cell library is copied to the project directory by the
Project Administrator as a part of project creation. The Drawing Manager attaches this cell
library each time you select a drawing for the purpose of drawing annotation.
The drawing.cel library in the project directory must be used for any cells, other than the flow
arrow, which you intend to use for drawing annotation.
Drawing Borders
The Drawing Manager uses the following guidelines to determine which drawing border to
attach.
 The directory and network address for the drawing border is defined in the RDB
Management Data with the Reference Data Manager. This setting is stored in the Project
Control Database for access by the Drawing Manager.
 The file specifications for the drawing borders are determined by the following naming
convention.
dwgbrd_<drawing_type>.<drawing_size>
drawing_type is the standard note number in Standard Note Type 2000 for drawing types.
drawing_size is the text for the standard note value corresponding to the drawing size in the
Standard Note Type 1202.
For example, the drawing border name for an 'A' size piping drawing is dwgbrd_2.a.

Drawing Plot Size Table

This table is located in the drawplotsize file and is copied from the PD_Shell delivery directory at
the time a project is created. It contains the drawing size standard notation, plot size, the
standard text for the size, and the four margins for the cutting edge. An example of a
drawplotsize file and definitions of each field follows:
! Drawing Plot Size Table
!
!Drawing Size Cutting Edge Margins from Cutting Edge (Drawing
Size)
!Std Note Size X-l Y-t X-r Y-b
!
1 8.5"x11" 0.8125" 0.625" 2.125" 0.625 (A)
2 11"x17" 1" 0.6875" 3" 0.6875" (B)
3 17"x22" 1.1875" 0.75" 3.75" 0.75" (C)
4 24"x36" 1.375" 0.8125" 5.4375" 0.8125" (D)
5 34"x44" 1.5625" 0.875" 6.875" 0.875" (E)
6 28"x40" 1.625" 0.9375" 5.625" 0.9375" (F)
101 840mmx1189mm 56mm 35mm 198mm 35mm (A0)
102 595mmx840mm 47mm 30mm 193mm 30mm (A1)
103 420mmx595mm 38mm 27mm 190mm 27mm (A2)
104 297mmx420mm 33mm 25mm 155mm 72mm (A3)
105 210mmx297mm 28mm 24mm 65mm 24mm (A4)
 Drawing Size Std Note is the standard note, which is referenced from the Standard Note
Type 1202, for the drawing size selected.
 Cutting Edge Size reflects the actual size of the cutting edge around the border that is
associated with the drawing size.
 Margins from Cutting Edge
 X-l defines the horizontal distance from the left cutting edge for composition.
 X-t defines the horizontal distance from the right cutting edge for composition.
 Y-r defines the vertical distance from the top cutting edge for composition.
 Y-b defines the vertical distance from the bottom cutting edge for composition.
 Drawing Size is the standard note text for the drawing size.
Drawing Manager Database Table Information

This section describes and includes the tables from the Default Relational Database Definition,
which is stored in the project.ddl file, that are used during the drawing process.
These tables are dedicated to the Drawing Manager task. There is interaction between these
tables and other various tables in the Project Control Database (PDTABLE_1 12 Design Area
Data, for example).

Project Control Database

This section describes and includes the tables from the Project Control Database that are
affected during the drawing process.
Do not edit database definitions except to modify column names.
# Drawing Data
2 , drawing_no , character(24) , index 2
4 , default_scale , character(16)
8 , completion_status , short
10, drawing_type , short , standard note 2000 , index 3
11, last_revision_no , character(2)
12, drawing_file_spec , character(14)
13, path_name , character(36)
20, release_revision , character(2)
21, release_date , integer
22, checking_status , short , standard note 1610
# Drawing View Data
1 , dwg_view_index_no , integer , index 1
2 , dwg_view_no , character(6) , index 2
3 , dwg_view_name , character(40)
4 , dwg_view_scale , character(16)
6 , saved_view_name , character(6)
7 , viewing_direction , short , standard note 1620

8 , composition_status , short , standard note 1630
9 , dwg_view_x_low , double
10, dwg_view_y_low , double
11, dwg_view_z_low , double
12, dwg_view_x_high , double
13, dwg_view_y_high , double
14, dwg_view_z_high , double
15, vhl_category_index , short
16, drawing_view_type , short
# Drawing View Reference Model Data
1 , dwg_view_index_no , integer
# Composite Drawing View Data
1 , comp_dwg_index_no , integer , index 1
2 , comp_dwg_view_no , character(6)
3 , comp_dwg_view_name , character(40)
4 , comp_dwg_v_scale , character(16)
6 , dwg_view_index_a , integer
7 , dwg_view_index_b , integer
8 , dwg_view_index_c , integer
9 , dwg_view_index_d , integer
10, dwg_view_index_e , integer
11, dwg_view_index_f , integer
12, dwg_view_index_g , integer
13, dwg_view_index_h , integer
14, dwg_view_index_i , integer
15, dwg_view_index_j , integer
# Drawing Revision Data
# Drawing Setup Data

3 , drawing_scale , character(16)
6 , discipline_mask , short
7 , alternate_seed_opt , short
# Reference Model Display Category Setup Data
3 , category_mask_a , integer
4 , category_mask_b , integer
5 , category_mask_c , integer
6 , category_mask_d , integer
# Plotting Default Data
1 , iplot_index_no , integer
2 , iplot_number , character(24)
3 , iplot_description , character(40)
4 , iplot_file_spec , character(14)

Drawing Seed Data

The Project Data Manager is used to revise the seed data for a specified drawing or create a
report of the RDB data. You can revise both 3D data and drawing data.
The Revise Drawing option is used to revise the seed data for a selected drawing file. The
system activates the following form which provides access to the modification options.
Select the option for the type of drawing data to be revised. The following report shows the
delivered settings for the Drawing Data.
Drawing Category
Data
Level
Drawing View Specific Labels 4
Drawing View Identification Labels 5
Coordinate Labels 7
Dimensioning 9
Revision Triangles and Revision Clouds 10
Hold Clouds 11
Reports 8
Miscellaneous Drawing Graphics 3
Non-Plotted Drawing Graphics 12
Battery Limits 36
Matchlines 37
Centerlines 38
Dumb Details 39

Leader Lines for Dumb Details 40
Extension Lines for Dumb Details 41
Dimensions for Dumb Details 42
Coordinates for Dumb Details 43
Like Line No Labels 44
Like Equipment No Labels 45
User-defined drawing annotation category 11 46
Hidden Line Category for View Number 1 21
Dashed Hidden Line Category for View Number 1 13

Drawing Graphic Symbology
Weight Colors Name
Revision Cloud 0 White
Flow Arrow 0 White FLOARR
Report 0 White
Dimension White
Miscellaneous Violet
Field Name for Nominal Piping Diameter
Symbol Font 50
Character Size for Undefined,Undefined

Report
Line Spacing Factor 0.500000
Maximum Blank Line 3
Drawing Label Sizes
Text Height Text Width
1/16" 1/16"
1/8" 1/8"
1/4" 1/4"
5/16" 5/16"
3/8" 3/8"
1/2" 1/2"
5/8" 5/8"
11/16" 11/16"
7/8" 7/8"
3/4" 3/4"
Drawing Annotation
Line
Line Text Spacing
Category Weight Color Terminator Text Size Font Factor

Symbology
Battery Limits 0 Solid White 1/4", 1/4" 0 0.0000
Matchlines 0 Solid White 1/4", 1/4" 0 0.0000
Centerlines 0 Solid White 1/4", 1/4" 0 0.0000
Dumb Details 0 Solid White 1/4", 1/4" 0 0.0000
Leader Lines for Dumb 0 Solid White 1/4", 1/4" 0 0.0000

Details

Extension Lines for 0 Solid White 1/4", 1/4" 0 0.0000
Dumb Detail
Dimensions for Dumb 0 Solid White 1/4", 1/4" 0 0.0000
Details
Coordinates for Dumb 0 Solid White 1/4", 1/4" 0 0.0000
Details
Like Line No Labels 0 Solid White 1/4", 1/4" 0 0.0000
Like Equipment No 0 Solid White 1/4", 1/4" 0 0.0000

Labels
User-defined drawing 11 0 Solid White 1/4", 1/4" 0 0.0000
annotation category
annotation category
annotation category
annotation category
annotation category
annotation category
annotation category
annotation category
annotation category
annotation category
Project Data
Manager
Drawing Hidden
Line Symbology
Use Default Weight
Use User Defined

Symbology
Use Default Color
Using Labels in Drawing

The Label Description Library contains the definitions for all the labels used in the PDS 3D
modules. Labels can be placed in the drawing as intelligent graphics with linkages to the design
database. You can update existing drawing view specific labels to reflect the latest data in the
database.
A Label Description Library is delivered in the file win32app\pdshell\lib\labels. l. You can use the
Label Description Library Manager to edit the labels to suit the needs of your project.
LabelTypes
The following label types are used for annotation in drawings.
Displayable Attribute Labels

Each type of displayable attribute label has a description in the Label Description Library. This
description identifies the label characteristics such as level, color code, style, and font, and the
attribute data associated with the label.
A displayable attribute label consists of the text and optionally, a leader line, a line terminator,
and some label enclosure graphics. This label type is further divided into the following
categories.
 Drawing View Specific Label

displayable attribute labels for named model items which are placed in a drawing.
 Drawing View Identification Label
labels with attribute linkages to the Drawing View Data (table 122) that report information
about the drawing view such as drawing view name and view scale
Drawing View Specific Labels are further divided into subcategories for Piping, SMS, HVAC, and
Raceways. Drawing View Specific Labels for Piping and View Independent Labels are divided
into sub-ranges for system-defined labels and user labels.
Alphanumeric Labels
Alphanumeric labels are non-intelligent user-defined labels. Each type of alphanumeric label has
a description in the Label Description Library. This description identifies the label characteristics
such as level, color code, style, and font. An alphanumeric label consists of the text and
optionally, a leader line, a line terminator, and some label enclosure graphics.
Displayable Attribute Message

Each type of displayable attribute message has a description in the Label Description Library.
Unlike the other label types, the description of a displayable attribute message only contains the
attribute data. Therefore, you cannot define label description data such as color, weight, style,
and text size for a displayable attribute message.
A displayable attribute message has all or part of its text derived from the alphanumeric data
that is linked to a specified named item in the model.
A displayable attribute message is displayed temporarily at the terminal either as an
identification message or as a reporting message. Some of these messages are displayed in the
terminal's refresh message fields. Other messages are displayed temporarily in the model. The
system does not place any graphics in the model for this type of label.
A displayable attribute message can also be used to create a value for another attribute, for
example, the Line Number Label attribute.
Label Definition Data

The Label Description Library Manager is part of the Reference Data Manager. The following
forms show the label definition data used to define the line number label.

Drawing View Specific Labels

Label 001 defines the label definition data used to place a line number label in a drawing view.

Displayable Attribute Label

Label 310 defines the structure of the line number label.

Index
Col • 230
' Commodity Code • 115
Commodity Codes • 237
'*' Spec Implied Items • 246 Commodity Item Name Table • 129
Common Tools on Forms • 144
[ Component Manipulation Commands • 161
[Buffer] = Field Definition • 231 Component Revision • 173
[Rows/Page] • 231 Connect Point Data • 92
[Spacing] • 232 Coordinate System Indicator and
Orientation Tee Coordinate System
Indicator • 170
' Create Label Attribute Data • 257
'+' Table Implied Example • 248 Creating 3D Models • 134
'+' Table Implied Items • 247 Creating and Maintaining Links • 191
Creating Equipment Models • 151
2 Creating Material Takeoffs and Other
2DSetup • 21 Reports • 224
Creating Orthographic Drawings • 268
Creating Piping Models • 162
3
3D Coordinate Systems • 30 D
3D Seed Data • 147
3D Setup • 22 Data_Type • 230
Database Definition Files • 50
Database Information • 48
A Database Overview • 43
About Licensing • 22 Database Requirements • 175
About the Reference Database (RDB) • 152 Define Commands • 161
Activating the Orientation Tee • 160 Definitions • 229
Active Placement Point • 170 Delete Data • 260
Alphanumeric Labels • 279 Delivered Reference Data • 90
Analyze Data • 174 Design Area and Piping Design Area
ASCII to Binary Conversion • 264 Predefined Volume • 212
Attribute Types • 49 Design Database • 67
Design Review Integrator (PD_Review) • 19
B Design Volume Coordinate System • 36
Detecting and Managing Interferences • 208
Base Form • 146 Dialog Boxes • 140
Batch Software Organization • 265 Diameter Table • 109
Bend Deflection Table • 130 Disable Display of P&ID Drawing Command
Branch Insertion Tables • 130 • 203
Discrimination Data File • 225
C Displayable Attribute Label • 281
Cells • 270 Displayable Attribute Labels • 278
Choosing Data Transfer Options • 199 Displayable Attribute Message • 279
Clash Categories • 221 Drawing Borders • 270
Clash Precedence • 221 Drawing Categories • 270
Client/Server Relationship • 45 Drawing Manager (PD_Draw) • 15
Code-Listed Attributes • 49

Index
Drawing Manager Database Table I

Information • 271
Implied Data • 239
Drawing Manager Features • 269
Insert Data • 258
Drawing Manager Setup • 269, 270
Install Oracle • 189
Drawing Plot Size Table • 271
Install SmartPlant Engineering Manager •
Drawing Seed Data • 275
189
Drawing View Specific Labels • 280
Install SmartPlant P&ID • 190
DVCS Oriented From Plant North • 39
Installation • 189
Instrument Component Specification Data •
E 95
Edit Data • 260 Instruments and Instrument Loops • 12
EE Raceway Modeling • 19 Interference Checker Input • 217
Equipment Manipulation Commands • 161 Interference Checker Output • 218
Equipment Model Seed Data • 153 Interference Checker/Manager (PD_Clash)
Equipment Modeling (PD_EQP) • 12 • 16
Equipment Modeling Commands • 161 Interference Checking Process Overview •
Equipment Modeling Concepts • 158 208
Equipment Modeling Environment • 156 Interference Manager • 220
Establish a SmartPlant/PDS Link • 194 ISOGEN • 264, 267
Examples • 38, 239 Item Name and Model Code • 113
Extracting Isometric Drawings • 261
L
F Label Definition Data • 279
Fabrication Category • 116 Label Description Library • 103
Field_Function • 229 Labels in Material Descriptions • 251
Field_Len • 230 LabelTypes • 278
Field_Type • 231 Level and Symbology Defaults • 138
Format File • 225 Level Control and Graphical Symbology •
Format File Syntax • 228 137
Forms • 142 Line Processing (pdsidf) • 266
FrameWorks Plus (FWP) • 13 Load from P&ID Options • 201
Functions of PDS Equipment Modeling
(PD_EQP) • 152 M
Maintaining Report Definition Data • 224
G Map an Ignored Attribute • 197
Gasket Gap / Table • 112 Map an Unmapped Attribute • 198
Generic Physical Data Modules • 122 Mapping Attributes_WRAPPER • 196
Generic Tables • 127 Material Data Publisher • 260
Geometric Industry Standard • 115 Material Description Data • 101
Graphic Commodity Data and Physical Material Descriptions • 236
Dimension Data • 101 Material Takeoff Options • 249
Graphic Concepts for Piping Design • 169 Material Takeoff Reporting (Report
Graphical P&ID Setup Command • 201 Manager) • 241
Graphics Environment for PDS 3D • 139 Materials Grade • 116
Green and Red Connect Point Data • 114 Materials Table • 111
Mating Implied Items • 246
H Menus • 139
Miscellaneous Commands • 161
Hard - Hard Example • 222 Model Data • 174
Hard - Soft Example • 222 Model Files • 136, 269
How PDS Works • 105 Model Parametric Shape Definitions • 124

Index
Modeling Setup Requirements • 135 Piping Materials Class Data • 91, 107
Modifier • 115 Piping Model Seed Data • 164
Piping Revision • 173
N Piping Segments • 169
Piping Specialty Specification Data • 94
Name From P&ID • 186 PJS Tables and Functions • 100
Name from P&ID Option • 203 Placement Commands • 172
Named Component Existence Report Placement Examples • 131
Command • 203 Placing Components On Existing Segments
Nozzle Manipulation • 161 • 128
Plant Coordinate System • 31
O Plotting • 267
Option Code • 114 Preface PDS • 9
Optional Report Type Line • 232 Process & Instrumentation Diagram (P&ID)
Orientation Tee • 171 • 11
Output Fields • 232 Process Flow Diagram (PFD) • 11
Overview of Isometric Extraction • 263 Processing Reports • 227
Project • 211
Project Control Database • 50, 272
P Project Engineer HVAC (PE-HVAC) • 18
P&ID Correlation Table • 176 Project Organization • 23, 210
P&ID Data • 186 Project Setup • 20, 135, 269
P&ID Data Comparison Options • 187
P&ID Drawing Display Categories
Command • 203
R
P&ID Graphical Data Transfer Setup • 180 Reasoning • 30
P&ID Node Numbers • 182 Recommended Working Units - English • 28
Palettes • 140 Recommended Working Units - Metric • 29
Parametric Shape Definitions • 124 Reference Data • 89
PDS 3D Databases • 47 Reference Data Manager (PD_Data) • 15
PDS and the Relational Interface System Reference Data Setup • 135
(RIS) • 43 Reference Database • 84
PDS Isometric Interface (PD_ISO, Report Format File • 228
PD_ISOGEN) • 17 Report Manager (PD_Report) • 18
PDS P&ID to Piping Data Transfer • 175 Report Output • 226, 240
PDS Stress Analysis Interface (PD_Stress) Report Record • 226
• 16 Report Types • 227
PDS System Configurations • 45 Reporting Process • 224
Physical Data • 126 Restore View of Piping Model Command •
Physical Data Definitions • 120 203
Piping Assembly Library • 104 Review Data • 174
Piping Commodity Data • 113 Review P&ID Drawing Details Command •
Piping Commodity Implied Material Data • 203
98 Review/Revise Commands • 161
Piping Commodity Size-Dependent Material Revise Data • 174
Data • 97 Revising Linked Models • 196
Piping Commodity Specification Data • 92 Revision Commands • 173
Piping Connect Points • 172 Row • 230
Piping Design Area and Design Area • 211
Piping Design Commands • 172 S
Piping Design Graphics (PD_Design) • 14 Sample Format Files • 232
Piping Job Specification • 91
Piping Materials Class Code • 108

Index
Sample Interference Report Format File • Understanding Interference Envelopes •

235 216
Sample MTO Format (piping_g.fmt) • 241 Understanding Interference Plotting • 223
Sample MTO Output • 244 Understanding Interference Reporting • 223
Sample MTO Report Format Files • 233 Understanding Report Files and Records •
Sample P&ID Consistency Check Report 225
Format File • 235 Update by Node Number • 184
Sample Project Control Report Format Files Update From Active P&I Drawing • 185
• 235 Update Segment Data from P&ID • 183
Sample Spec Report Format Files • 234 Using Labels in Drawing • 278
Secondary Commands • 162
Seed Files • 135 V
Segment Data Comparison Report • 198
Segment Vertex Commands • 173 View Windows • 141
Select P&ID by Line ID Command • 202 Volume Filter • 213
Select P&ID Drawing by Nozzle Command •
202 W
Selecting Options • 143 Weight code • 116
Setting Up a System to Support What are the 2D modules? • 11
Interference Detection • 215 What are the 3D modules? • 12
Single/Dual Ownership of Clashes • 214 What Happens When I Place a
SmartPlant P&ID to PDS Piping Data Component? • 105
Transfer • 188 What Happens When I Report On a
Spec Access • 107 Component? • 235
Specific Physical Data Modules • 121 What is the Plant Design System? • 10
Specific Tables • 127 Working in Three Dimensions • 24
Standard Note Library • 103 Working Units • 27
Sub-Symbol Processor • 120 Working with the Graphical User Interface •
Symbol Processors • 119 139
System Setup • 20
T
Table Access • 117
Tap Properties Data • 96
Temperature Pressure Table • 109
Test the SmartPlant Connection • 191
The Batch Job Input File • 265
The Intergraph Interface to ISOGEN • 264
The ISOGEN Interface • 267
Thickness Equations • 112
Thickness Table • 110
Transfer by Equipment Number and Nozzle
Number • 184
Transferring Piping Data • 188
Troubleshooting • 205
U
Understanding Design Areas and Volumes •
211
Understanding Implied Items • 246
Understanding Interference Checking • 217

PDS 3D Theory Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDS 3D Theory Guide

Uploaded by

Copyright:

Available Formats

Plant Design System

Version 2011 R1 (12.1)

U.S. Government Restricted Rights Legend

Plant Design System 3D Theory 2

Plant Design System 3D Theory 3

What is the Plant Design System? ...................................................................................................... 10

Database Overview .............................................................................................................................. 43

Plant Design System 3D Theory 4

How PDS Works ................................................................................................................................. 105

Creating 3D Models............................................................................................................................ 134

Plant Design System 3D Theory 5

Common Tools on Forms ........................................................................................................ 144

PDS P&ID to Piping Data Transfer .................................................................................................... 175

SmartPlant P&ID to PDS Piping Data Transfer ................................................................................. 188

Plant Design System 3D Theory 6

Mapping Attributes_WRAPPER ............................................................................................... 196

Detecting and Managing Interferences ............................................................................................. 208

Creating Material Takeoffs and Other Reports ................................................................................. 224

Plant Design System 3D Theory 7

Material Takeoff Options ................................................................................................................ 249

Extracting Isometric Drawings .......................................................................................................... 261

Creating Orthographic Drawings ...................................................................................................... 268

Index ................................................................................................................................................... 282

Plant Design System 3D Theory 8

List of PDS Documentation

Plant Design System 3D Theory 9

Plant Design System 3D Theory 10

What are the 2D modules?

Process Flow Diagram (PFD)

Process & Instrumentation Diagram (P&ID)

Plant Design System 3D Theory 11

Instruments and Instrument Loops

What are the 3D modules?

Equipment Modeling (PD_EQP)

Plant Design System 3D Theory 12

FrameWorks Plus (FWP)

Plant Design System 3D Theory 13

Piping Design Graphics (PD_Design)

Plant Design System 3D Theory 14

Reference Data Manager (PD_Data)

Drawing Manager (PD_Draw)

Plant Design System 3D Theory 15

PDS Stress Analysis Interface (PD_Stress)

Interference Checker/Manager (PD_Clash)

Plant Design System 3D Theory 16

PDS Isometric Interface (PD_ISO, PD_ISOGEN)

Plant Design System 3D Theory 17

Report Manager (PD_Report)

Project Engineer HVAC (PE-HVAC)

Plant Design System 3D Theory 18

Electrical Engineer Raceway Modeling (EERWAY) is specification-driven software which allows

Design Review Integrator (PD_Review)

Plant Design System 3D Theory 19

Plant Design System 3D Theory 20

Plant Design System 3D Theory 21

Plant Design System 3D Theory 22

Plant Design System 3D Theory 23

Working in Three Dimensions

Plant Design System 3D Theory 24

Plant Design System 3D Theory 25

Plant Design System 3D Theory 26

Design Cube Showing Cartesian Coordinate System

Plant Design System 3D Theory 27

Recommended Working Units - English