Академический Документы
Профессиональный Документы
Культура Документы
3D Theory
Copyright
Copyright 1984-2011 Intergraph Corporation. All Rights Reserved.
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.
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this 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. 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.
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? .......................................................................................................... 11
What are the 2D modules? ................................................................................................................... 12
Process Flow Diagram (PFD) ......................................................................................................... 12
Process & Instrumentation Diagram (P&ID) ................................................................................... 12
Instruments and Instrument Loops ................................................................................................. 13
What are the 3D modules? ................................................................................................................... 13
Equipment Modeling (PD_EQP) ..................................................................................................... 13
FrameWorks Plus (FWP)................................................................................................................ 14
Piping Design Graphics (PD_Design) ............................................................................................ 15
Reference Data Manager (PD_Data) ............................................................................................. 16
Drawing Manager (PD_Draw) ........................................................................................................ 16
PDS Stress Analysis Interface (PD_Stress) ................................................................................... 17
Interference Checker/Manager (PD_Clash) ................................................................................... 17
PDS Isometric Interface (PD_ISO, PD_ISOGEN) .......................................................................... 18
Report Manager (PD_Report) ........................................................................................................ 18
Project Engineer HVAC (PE-HVAC) .............................................................................................. 19
EE Raceway Modeling ................................................................................................................... 19
Design Review Integrator (PD_Review) ......................................................................................... 20
Project Setup......................................................................................................................................... 21
System Setup ................................................................................................................................. 21
2DSetup .......................................................................................................................................... 22
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 ...................................................................................................................................... 29
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 ............................................................................................................................... 46
Database Information ..................................................................................................................... 47
Database Definition Files ...................................................................................................................... 49
Project Control Database ............................................................................................................... 49
Design Database ............................................................................................................................ 66
Reference Database ....................................................................................................................... 82
Contents
Reference Data .......................................................................................................................................... 87
Delivered Reference Data ..................................................................................................................... 88
Piping Job Specification ........................................................................................................................ 89
Piping Materials Class Data ........................................................................................................... 89
Piping Commodity Specification Data ............................................................................................ 90
Piping Specialty Specification Data ................................................................................................ 92
Instrument Component Specification Data ..................................................................................... 93
Tap Properties Data ....................................................................................................................... 94
Piping Commodity Size-Dependent Material Data ......................................................................... 95
Piping Commodity Implied Material Data ....................................................................................... 96
PJS Tables and Functions ............................................................................................................. 98
Graphic Commodity Data and Physical Dimension Data ..................................................................... 99
Material Description Data ...................................................................................................................... 99
Standard Note Library ......................................................................................................................... 101
Label Description Library .................................................................................................................... 101
Piping Assembly Library ..................................................................................................................... 102
How PDS Works ....................................................................................................................................... 103
What Happens When I Place a Component? ..................................................................................... 103
Example of Piping Software ................................................................................................................ 104
Place Component Command .............................................................................................................. 105
Spec Access ................................................................................................................................. 105
Piping Materials Class Data ......................................................................................................... 105
Piping Commodity Data ................................................................................................................ 110
Table Access ................................................................................................................................ 113
Symbol Processors....................................................................................................................... 115
Sub-Symbol Processor ................................................................................................................. 116
Physical Data Definitions .............................................................................................................. 116
Specific Physical Data Modules ................................................................................................... 117
Parametric Shape Definitions ....................................................................................................... 120
Physical Data ................................................................................................................................ 121
Placing Components On Existing Segments ...................................................................................... 124
Commodity Item Name Table ....................................................................................................... 125
Bend Deflection Table .................................................................................................................. 126
Branch Insertion Tables................................................................................................................ 126
Placement Examples .................................................................................................................... 127
Creating 3D Models ................................................................................................................................. 129
Modeling Setup Requirements............................................................................................................ 129
Project Setup ................................................................................................................................ 129
Reference Data Setup .................................................................................................................. 130
Seed Files ..................................................................................................................................... 130
Model Files ................................................................................................................................... 131
Level Control and Graphical Symbology ...................................................................................... 131
Level and Symbology Defaults ..................................................................................................... 132
Graphics Environment for PDS 3D ..................................................................................................... 133
Working with the Graphical User Interface ................................................................................... 133
Common Tools on Forms ............................................................................................................. 138
3D Seed Data ............................................................................................................................... 142
Creating Equipment Models................................................................................................................ 145
Functions of PDS Equipment Modeling (PD_EQP) ..................................................................... 146
About the Reference Database (RDB) ......................................................................................... 146
Contents
Equipment Model Seed Data ....................................................................................................... 147
Equipment Modeling Environment ............................................................................................... 150
Equipment Modeling Concepts .................................................................................................... 152
Activating the Orientation Tee ...................................................................................................... 154
Equipment Modeling Commands ........................................................................................................ 155
Equipment Manipulation Commands ........................................................................................... 155
Component Manipulation Commands .......................................................................................... 155
Nozzle Manipulation ..................................................................................................................... 155
Review/Revise Commands .......................................................................................................... 155
Define Commands ........................................................................................................................ 155
Miscellaneous Commands ........................................................................................................... 155
Secondary Commands ................................................................................................................. 155
Creating Piping Models ....................................................................................................................... 156
Piping Model Seed Data ............................................................................................................... 158
Graphic Concepts for Piping Design ............................................................................................ 162
Orientation Tee ............................................................................................................................. 164
Piping Design Commands .................................................................................................................. 166
Placement Commands ................................................................................................................. 166
Revision Commands .................................................................................................................... 166
Component Revision .................................................................................................................... 166
Segment Vertex Commands ........................................................................................................ 167
Piping Revision ............................................................................................................................. 167
Model Data ................................................................................................................................... 167
Review Data ................................................................................................................................. 167
Revise Data .................................................................................................................................. 167
Analyze Data ................................................................................................................................ 167
PDS P&ID to Piping Data Transfer ......................................................................................................... 169
Database Requirements ..................................................................................................................... 169
P&ID Correlation Table ....................................................................................................................... 170
P&ID Graphical Data Transfer Setup .................................................................................................. 174
P&ID Node Numbers .......................................................................................................................... 176
Update Segment Data from P&ID ....................................................................................................... 177
Update by Node Number .............................................................................................................. 178
Transfer by Equipment Number and Nozzle Number .................................................................. 178
Update From Active P&I Drawing ................................................................................................. 179
P&ID Data ........................................................................................................................................... 180
Name From P&ID ................................................................................................................................ 180
P&ID Data Comparison Options ......................................................................................................... 181
SmartPlant P&ID to PDS Piping Data Transfer ..................................................................................... 183
Transferring Piping Data ..................................................................................................................... 183
Installation .................................................................................................................................... 184
Creating and Maintaining Links .................................................................................................... 187
Mapping Attributes_WRAPPER ................................................................................................... 190
Segment Data Comparison Report .............................................................................................. 192
Choosing Data Transfer Options .................................................................................................. 193
Load From P&ID Options ............................................................................................................. 194
Graphical P&ID Setup Command ................................................................................................. 195
Select P&ID by Line ID Command ............................................................................................... 196
Select P&ID Drawing by Nozzle Command ................................................................................. 196
Review P&ID Drawing Details Command .................................................................................... 196
Contents
P&ID Drawing Display Categories Command .............................................................................. 196
Restore View of Piping Model Command..................................................................................... 196
Disable Display of P&ID Drawing Command ............................................................................... 196
Name from P&ID Option ............................................................................................................... 196
Named Component Existence Report Command ........................................................................ 197
Troubleshooting ............................................................................................................................ 198
Detecting and Managing Interferences ................................................................................................. 201
Interference Checking Process Overview ........................................................................................... 201
Project Organization ........................................................................................................................... 203
Understanding Design Areas and Volumes ................................................................................. 203
Setting Up a System to Support Interference Detection ..................................................................... 207
Understanding Interference Envelopes .............................................................................................. 208
Understanding Interference Checking .......................................................................................... 209
Understanding Interference Plotting ............................................................................................. 215
Understanding Interference Reporting ......................................................................................... 215
Creating Material Takeoffs and Other Reports ..................................................................................... 217
Reporting Process .............................................................................................................................. 217
Maintaining Report Definition Data ..................................................................................................... 217
Understanding Report Files and Records .................................................................................... 218
Processing Reports ............................................................................................................................. 219
Report Types....................................................................................................................................... 220
Report Format File .............................................................................................................................. 220
Format File Syntax ....................................................................................................................... 221
Definitions ..................................................................................................................................... 221
Output Fields ................................................................................................................................ 224
Sample Format Files .................................................................................................................... 224
What Happens When I Report On a Component? ............................................................................. 227
Material Descriptions .................................................................................................................... 228
Commodity Codes ........................................................................................................................ 229
Examples ...................................................................................................................................... 230
Implied Data ................................................................................................................................. 231
Report Output ............................................................................................................................... 232
Material Takeoff Reporting (Report Manager) .................................................................................... 232
Sample MTO Format (piping_g.fmt) ............................................................................................. 233
Sample MTO Output..................................................................................................................... 234
Understanding Implied Items .............................................................................................................. 236
Mating Implied Items .................................................................................................................... 237
'*' Spec Implied Items ................................................................................................................... 237
'+' Table Implied Items .................................................................................................................. 238
Material Takeoff Options ..................................................................................................................... 239
Labels in Material Descriptions ........................................................................................................... 241
Create Label Attribute Data .......................................................................................................... 246
Material Data Publisher ....................................................................................................................... 249
Extracting Isometric Drawings ............................................................................................................... 251
Overview of Isometric Extraction ........................................................................................................ 253
The Intergraph Interface to ISOGEN ............................................................................................ 254
ASCII to Binary Conversion .......................................................................................................... 254
ISOGEN ........................................................................................................................................ 254
Contents
Batch Software Organization .............................................................................................................. 255
The Batch Job Input File............................................................................................................... 255
Line Processing (pdsidf) ............................................................................................................... 256
The ISOGEN Interface ................................................................................................................. 257
ISOGEN ........................................................................................................................................ 257
Plotting .......................................................................................................................................... 257
Creating Orthographic Drawings ........................................................................................................... 259
Drawing Manager Features ................................................................................................................ 260
Drawing Manager Setup ..................................................................................................................... 260
Project Setup ................................................................................................................................ 260
Model Files ................................................................................................................................... 260
Drawing Manager Setup ............................................................................................................... 260
Drawing Categories ...................................................................................................................... 261
Cells .............................................................................................................................................. 261
Drawing Borders ........................................................................................................................... 261
Drawing Plot Size Table ............................................................................................................... 261
Drawing Manager Database Table Information ........................................................................... 262
Project Control Database ............................................................................................................. 262
Drawing Seed Data ............................................................................................................................. 265
Using Labels in Drawing ..................................................................................................................... 268
LabelTypes ................................................................................................................................... 268
Label Definition Data .................................................................................................................... 269
Drawing View Specific Labels ...................................................................................................... 270
Displayable Attribute Label ........................................................................................................... 271
Index ......................................................................................................................................................... 273
Contents
Preface PDS
This document provides command reference information and procedural instructions for the
Plant Design System (PDS) software .
Preface PDS
10
SECTION 1
11
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.
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
12
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.
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.
13
14
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 datasuch as line sequence number, nominal diameter, material class,
temperatures and pressurescan 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.
15
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.
16
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) 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.
17
18
EE Raceway Modeling
19
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.
20
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.
21
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.
22
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 analagous 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
23
24
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.
25
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 45in two directions: the cube is displayed
from the top front right.
26
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.
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.
27
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.
28
File
MU
SU
PU
Area
1 FT
12 IN
2032
176138 FT
Drawing
1 FT
12 IN
195072
1834 FT
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.
29
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.
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.
30
31
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.
32
With these settings, the Plant Coordinate System would be defined as follows:
33
34
35
36
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.
37
Examples
The following examples show various ways of modifying the Plant Coordinate System or Design
Volume Coordinate System for various working conditions
38
39
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.
40
41
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.
42
Database Overview
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 modela 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.
43
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.
44
Database Overview
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.
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.
45
Database Overview
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.
PDS 3D Databases
A 3D project uses three database schemas for piping and equipment data as outlined in the
following illustration.
46
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.
47
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
14
17
20
=
=
=
=
A
AC
AE
AI
[Air]
[Combustion air]
[Aeration air]
[Instrument air]
:
:
191
194
197
198
200
203
206
209
48
=
=
=
=
=
=
=
=
G
GCD
GCL
GCN
GF
GG
GH
GHS
[Gas]
[Carbon dioxide gas]
[Chlorine gas]
[Chlorination gas]
[Fuel gas]
[Flue gas]
[Hydrogen gas]
[Hydrogen sulphide gas]
Database Overview
,
,
,
,
,
,
,
system_unique_no
project_no
project_name
job_no
company_name
plant_name
site_id
,
,
,
,
,
,
,
integer
character(15)
character(40)
character(40)
character(40)
character(40)
character(10)
,
,
,
,
,
,
,
,
,
type_of_rdb_data
approval_status
rdb_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
revision_date
,
,
,
,
,
,
,
,
,
short
short
character(14)
character(36)
character(26)
character(10)
short
integer
integer
49
Database Overview
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
26,
27,
28,
29,
30,
31,
32,
33,
34,
35,
36,
37,
38,
39,
40,
41,
report_format_path
report_format_node
report_filter_path
report_filter_node
piping_eden_path
piping_eden_node
eden_table_path
eden_table_node
piping_spec_path
piping_spec_node
assembly_path
assembly_node
model_builder_path
model_builder_node
design_review_path
design_review_node
std_note_lib_path
std_note_lib_node
eqp_eden_path
eqp_eden_node
tdf_table_path
tdf_table_node
clash_report_path
clash_report_node
clash_plot_path
clash_plot_node
mdl_status_low_dr
mdl_status_high_dr
mdl_status_low_ic
mdl_status_high_ic
area_owner_opt_ic
eqp_insul_opt_ic
eqp_con_tol_opt_ic
clash_rpt_index_no
report_search_path
report_search_node
sup_tdf_table_path
sup_tdf_table_node
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
character(36)
character(26)
short
short
short
short
short
short
short
integer
character(36)
character(26)
character(36)
character(26)
,
,
,
,
standard
standard
standard
standard
note
note
note
note
1605
1605
1605
1605
50
archival_index_no
archival_number
archival_descript
archival_file_spec
path_name
network_address
month_map
day_of_week_map
day_map
time_of_day
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(14)
character(36)
character(26)
integer
integer
integer
integer
Database Overview
11, schedule_type
, short
site_id
site_description
min_model_range
max_model_range
min_dwg_range
max_dwg_range
min_dwg_view_range
max_dwg_view_range
min_pip_partition
max_pip_partition
min_eqp_partition
max_eqp_partition
master_flag
,
,
,
,
,
,
,
,
,
,
,
,
,
character(10)
character(40)
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
short
,
,
,
,
,
discipline_indx_no
discipline_name
intra_disc_ifc_flg
discipline_mtrx_a,
discipline_mtrx_b,
, short
, character(20)
, short
integer
integer
discipline_indx_no
area_index_no
area_name
area_description
volume_low_x
volume_low_y
volume_low_z
volume_high_x
volume_high_y
volume_high_z
interference_mode
area_lock_owner
area_lock_status
area_lock_date
,
,
,
,
,
,
,
,
,
,
,
,
,
,
short
short
character(10)
character(40)
integer
integer
integer
integer
integer
integer
short
character(10)
short
integer
51
Database Overview
15, clash_rpt_index_no , integer
# Model Data
table number = 113 , number of columns = 17
1 ,
2 ,
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
16,
17,
model_index_no
discipline_indx_no
area_index_no
partition_no
model_no
model_description
model_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
verification_date
revision_date
responsible_disc
model_type
model_status
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
short
short
character(10)
character(40)
character(14)
character(36)
character(26)
character(10)
short
integer
integer
integer
short
short
short
, index 1
,
,
,
,
,
,
partition_no
max_segment_number
max_piping_number
max_pipe_number
max_instr_number
max_support_number
,
,
,
,
,
,
short
integer
integer
integer
integer
integer
,
,
,
,
,
discipline_indx_no
default_path_name
default_node
ref_mdl_symbology
symbology_display
,
,
,
,
,
short
character(36)
character(26)
short
short
52
Database Overview
table number = 116, number of columns = 6
1
2
3
4
5
6
,
,
,
,
,
,
sub_project_ndx_no
sub_project_no
sub_project_name
sub_project_path
sub_project_node
sub_project_mount
,
,
,
,
,
,
short
character(15)
character(40)
character(36)
character(26)
character(50)
, integer
, character(10)
, index 1
,
,
,
,
,
,
,
dwg_index_no
drawing_no
drawing_title
default_scale
approval_initials
approval_date
approval_status
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(16)
character(4)
integer
short
, index 1
, index 2
, standard note 35
53
Database Overview
8 ,
9 ,
10,
3
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
26,
27,
28,
29,
30,
31,
32,
33,
34,
completion_status , short
drawing_size
, short
drawing_type
, short
last_revision_no
drawing_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
revision_date
last_rev_index_no
release_revision
release_date
checking_status
standard_note_no_a
standard_note_no_b
custom_1
custom_2
custom_3
custom_4
custom_5
custom_6
custom_7
custom_8
custom_9
custom_10
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
character(2)
character(14)
character(36)
character(26)
character(10)
short
integer
integer
short
character(2)
integer
short
short
short
character(40)
character(40)
character(16)
character(16)
character(16)
character(16)
character(16)
character(16)
integer
integer
, index
dwg_view_index_no
dwg_view_no
dwg_view_name
dwg_view_scale
dwg_index_no
saved_view_name
viewing_direction
composition_status
dwg_view_x_low
dwg_view_y_low
dwg_view_z_low
dwg_view_x_high
dwg_view_y_high
dwg_view_z_high
vhl_category_index
drawing_view_type
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(16)
integer
character(6)
short
short
double
double
double
double
double
double
short
short
, index 1
, index 2
54
Database Overview
table number = 123, number of columns = 2
1 , dwg_view_index_no
2 , model_index_no
, integer
, integer
comp_dwg_index_no
comp_dwg_view_no
comp_dwg_view_name
comp_dwg_v_scale
dwg_index_no
dwg_view_index_a
dwg_view_index_b
dwg_view_index_c
dwg_view_index_d
dwg_view_index_e
dwg_view_index_f
dwg_view_index_g
dwg_view_index_h
dwg_view_index_i
dwg_view_index_j
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(16)
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
, index 1
dwg_index_no
revision_index_no
revision_no
revision_date
revision_by
checked_by
rev_description
appr_by_1
appr_by_2
appr_by_3
appr_by_4
appr_by_1_date
appr_by_2_date
appr_by_3_date
appr_by_4_date
checked_date
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
character(2)
integer
character(4)
character(4)
character(40)
character(4)
character(4)
character(4)
character(4)
integer
integer
integer
integer
integer
, short
, short
55
Database Overview
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
26,
drawing_scale
default_path_name
default_node
discipline_mask
alternate_seed_opt
cell_file_spec
cell_path_name
cell_net_address
plot_catgy_mask_a
plot_catgy_mask_b
label_mask_a
label_mask_b
label_mask_c
label_mask_d
custom_1
custom_2
custom_3
custom_4
custom_5
custom_6
custom_7
custom_8
custom_9
custom_10
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
character(16)
character(36)
character(26)
short
short
character(14)
character(36)
character(26)
integer
integer
integer
integer
integer
integer
character(40)
character(40)
character(16)
character(16)
character(16)
character(16)
character(16)
character(16)
integer
integer
drawing_type
discipline_indx_no
category_mask_a
category_mask_b
category_mask_c
category_mask_d
vhl_category_msk_a
vhl_category_msk_b
vhl_category_msk_c
vhl_category_msk_d
vhl_ref_symbology
vhl_symbology
,
,
,
,
,
,
,
,
,
,
,
,
short
short
integer
integer
integer
integer
integer
integer
integer
integer
short
short
56
,
,
,
,
,
,
iplot_index_no
iplot_number
iplot_description
iplot_file_spec
path_name
network_address
,
,
,
,
,
,
integer
character(24)
character(40)
character(14)
character(36)
character(26)
Database Overview
# Drawing Ownership Data
table number = 129, number of columns = 2
1 , dwg_index_no
2 , site_id
, integer
, character(10)
, index 1
###################################################
# Interference Management Data
# Clash Management Data
table number = 131, number of columns = 15
1 ,
2 ,
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
system_unique_no
discipline_indx_no
area_index_no
unique_sequence_no
completion_date
control_user_no
env_creation_date
clash_check_option
volume_filter_opt
volume_low_x
volume_low_y
volume_low_z
volume_high_x
volume_high_y
volume_high_z
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
short
integer
integer
short
integer
short
short
integer
integer
integer
integer
integer
integer
, index 1
unique_clash_id
if_approval_status
comp_a_unique_id
comp_b_unique_id
model_index_no_a
model_index_no_b
discipline_index_a
discipline_index_b
recent_clash_type
recent_plot_date
recent_review_date
recent_sequence_no
area_index_no
action_discipline
recent_seq_no_b
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
integer
integer
integer
integer
short
short
short
integer
integer
integer
short
short
integer
, index 1
, standard note 1203
57
Database Overview
16, area_index_no_b
, short
system_unique_no
unique_clash_id
unique_sequence_no
clash_type
comp_a_range_x_lo
comp_a_range_y_lo
comp_a_range_z_lo
comp_a_range_x_hi
comp_a_range_y_hi
comp_a_range_z_hi
comp_b_range_x_lo
comp_b_range_y_lo
comp_b_range_z_lo
comp_b_range_x_hi
comp_b_range_y_hi
comp_b_range_z_hi
env_pair_type
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
integer
integer
short
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
short
, index 1
, index 2
, standard note 1204
,
,
,
,
,
,
,
unique_comp_id
comp_table_number
comp_row_number
model_index_no
primary_descript
secondary_descript
comp_model_status
,
,
,
,
,
,
,
integer
short
integer
integer
character(20)
character(40)
short
, index 1
,
,
,
,
,
,
,
,
system_unique_no
unique_clash_id
review_date
review_user_no
responsib_user_no
action
review_comment
approval_method
,
,
,
,
,
,
,
,
integer
integer
integer
short
short
short
character(100)
short
, index 1
, index 2
58
Database Overview
table number = 136, number of columns = 4
1
2
3
4
,
,
,
,
system_unique_no
unique_clash_id
plot_date
plot_user_no
,
,
,
,
integer
integer
integer
short
, index 1
# Report Data
table number = 141, number of columns = 20
1 ,
2 ,
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
report_index_no
report_no
report_title
approval_initials
approval_date
approval_status
last_revision_no
report_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
revision_date
format_index_no
filter_index_no
last_rev_index_no
report_source
report_type
search_index_no
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(4)
integer
short
character(2)
character(14)
character(36)
character(26)
character(10)
short
integer
integer
integer
integer
short
short
short
integer
, index 1
, index 2
, standard note 35
format_index_no
format_number
format_description
format_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
revision_date
rpt_format_source
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(14)
character(36)
character(26)
character(10)
short
integer
integer
short
, index 1
59
Database Overview
filter_index_no
filter_number
filter_description
filter_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
revision_date
rpt_filter_source
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(14)
character(36)
character(26)
character(10)
short
integer
integer
short
, index 1
,
,
,
,
,
,
,
report_index_no
revision_index_no
revision_no
revision_date
revision_by
checked_by
rev_description
,
,
,
,
,
,
,
integer
short
character(2)
integer
character(4)
character(4)
character(40)
60
search_index_no
search_number
search_description
search_file_spec
path_name
network_address
lock_owner
lock_status
lock_date
revision_date
rpt_search_source
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
character(14)
character(36)
character(26)
character(10)
short
integer
integer
short
, index 1
Database Overview
table number = 151, number of columns = 25
1 ,
2 ,
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
review_index_no
review_no
review_title
review_type
control_file_spec
control_path_name
control_node
control_lock_owner
control_lock_stat
control_lock_date
tag_file_spec
tag_path_name
tag_node
tag_lock_owner
tag_lock_status
tag_lock_date
session_rev_date
label_rev_date
label_file_spec
label_path_name
label_net_address
month_map
day_of_week_map
day_map
time_of_day
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(24)
character(40)
short
character(14)
character(36)
character(26)
character(10)
short
integer
character(14)
character(36)
character(26)
character(10)
short
integer
integer
integer
character(14)
character(36)
character(26)
integer
integer
integer
integer
Package Data
, index 1
, standard note 1410
,
,
,
,
,
package_index_no
package_no
package_title
release_revision
release_date
,
,
,
,
,
integer
character(24)
character(40)
character(2)
integer
, index 1
Document Data
,
,
,
,
document_index_no
package_index_no
document_source
document_type
,
,
,
,
integer
integer
short
short
61
Database Overview
support_unique_no
, integer
ganged_id
, integer
grouped_id
, integer
area_index_no
, short
model_index_no
, short
drawing_title
, character(40)
drawing_file_spec
, character(40)
path_name
, character(40)
network_address
, character(40)
support_lineid
, character(40)
material_index
, character(20)
revision_no
, short
revision_date
, integer
drawing_status
, short
sheet_no
, short
sheet_total
, short
isofile_indx_no
isodflt_indx_no
isofile_type
isofile_spec
path_name
network_address
iso_description
lock_owner
lock_status
lock_date
revision_date
,
,
,
,
,
,
,
,
,
,
,
integer
integer
short
character(14)
character(36)
character(26)
character(40)
character(10)
short
integer
integer
62
Database Overview
table number = 181, number of columns = 12
1 ,
2 ,
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
isoproj_indx_no
isoproj_task_opt
isoproj_name_opt
isoproj_dwg_opt
isodflt_indx_no
reserved_1
reserved_2
reserved_3
batch_options
isoproj_name_label
isoproj_dwg_label
sub_directory_opt
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
short
short
integer
character(26)
character(36)
character(20)
character(20)
short
short
short
, index 1
,
,
,
,
isodflt_indx_no
isodflt_tag
isodflt_descr
isodflt_rev_date
,
,
,
,
integer
character(12)
character(40)
integer
, index 1
iso_area_indx_no
area_indx_no1
area_indx_no2
area_indx_no3
area_indx_no4
area_indx_no5
area_indx_no6
selection_mode
iso_area_name
iso_area_desc
user_data_indx_no
isodflt_indx_no
cont_indx_no1
cont_indx_no2
cont_indx_no3
cont_indx_no4
cont_indx_no5
cont_indx_no6
cont_indx_no7
cont_indx_no8
cont_indx_no9
cont_indx_no10
cont_indx_no11
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
short
short
short
short
short
short
character(10)
character(40)
integer
integer
short
short
short
short
short
short
short
short
short
short
short
, index 1
63
Database Overview
24,
25,
26,
27,
28,
29,
30,
31,
32,
cont_indx_no12
cont_indx_no13
cont_indx_no14
cont_indx_no15
cont_indx_no16
cont_indx_no17
cont_indx_no18
cont_indx_no19
cont_indx_no20
,
,
,
,
,
,
,
,
,
short
short
short
short
short
short
short
short
short
user_data_indx_no
type_of_user_data
user_data_1
user_data_2
user_data_3
user_data_4
user_data_5
user_data_6
user_data_7
user_data_8
user_data_9
user_data_10
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
character(40)
character(40)
character(40)
character(40)
character(40)
character(40)
character(40)
character(40)
character(40)
character(40)
64
drawing_indx_no
,
iso_area_indx_no
,
lineid_1
,
lineid_2
,
lineid_3
,
number_of_sections ,
drawing_number
,
batch_ref_no
,
iso_dgn_name
,
model_status_code ,
model_revised_date ,
lst_extraction_date,
tot_no_extractions ,
no_sheets_extract ,
last_mto_date
,
mto_to_mtl_control ,
no_of_revisions
,
user_data_indx_no ,
iso_type
,
integer
integer
, index 1
character(24)
, index 2
character(24)
character(24)
short
character(24)
character(12)
character(24)
character(2)
integer
integer
short
short
integer
integer
short
integer
short
, index 3
Database Overview
# Isometric Drawing Revision Information
table number = 186 , number of columns = 12
1 ,
2 ,
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
draw_rev_indx_no
draw_sht_indx_no
type_of_revision
revision_number
generated_by
checked_by
approved_by
extraction_date
extraction_no
sheets_extracted
rev_description
isodflt_indx_no
,
,
,
,
,
,
,
,
,
,
,
,
integer
integer
, index 1
short
, index 2
short
, index 3
character(3)
character(3)
character(3)
integer
short
short
character(60)
integer
, integer
, integer
,
,
,
,
,
,
,
sheet_indx_no
drawing_indx_no
sheet_no
last_extract_date
tot_no_extractions
last_mto_date
no_of_revisions
, integer
, integer
, integer
, integer
, integer
, integer
, integer
, index 1
, index 2
,
,
,
,
,
,
,
,
drawing_indx_no
section_no
start_traversal_x
start_traversal_y
start_traversal_z
start_entity
start_comp_occ
start_seg_occ
,
,
,
,
,
,
,
,
integer
short
integer
integer
integer
short
integer
integer
, index 1
, index 2
65
Database Overview
Design Database
# Piping Design Database
# Default Relational Database Definition
# 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.
66
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
system_unique_no
line_number_label
line_id
unit_number
unit_code
module_no
package_system_no
train_number
fluid_code
line_sequence_no
nominal_piping_dia
piping_mater_class
gasket_separation
insulation_purpose
insulation_thick
insulation_density
heat_tracing_reqmt
heat_tracing_media
heat_tracing_temp
construction_stat
hold_status
approval_status
schedule_override
nor_oper_pres
nor_oper_temp
alt_oper_pres
alt_oper_temp
nor_dgn_pres
nor_dgn_temp
alt_dgn_pres
alt_dgn_temp
steam_outlet_temp
mater_of_construct
safety_class
design_standard
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(40)
character(24)
character(12)
character(3)
character(16)
character(12)
character(2)
short
character(16)
short
character(16)
character(8)
short
double
double
short
short
double
short
short
short
character(8)
double
double
double
double
double
double
double
double
double
character(6)
short
short
, index 1
standard
standard
standard
standard
note
note
note
note
130
50
35
332
Database Overview
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
design_area_number
design_resp
construction_resp
supply_resp
coating_reqmts
cleaning_reqmts
fluid_category
nor_op_pres_units
nor_op_temp_units
alt_op_pres_units
alt_op_temp_units
nor_dgn_pres_units
nor_dgn_temp_units
alt_dgn_pres_units
alt_dgn_temp_units
steam_temp_units
stress_system_no
stress_reqmts
hyd_system_no
hyd_reqmts
specific_gravity_a
specific_gravity_b
specific_gravity_c
viscosity
density
spec_heat_ratio
sonic_velocity
surface_roughness
test_system_no
test_fluid
test_pressure
PID_id_part_a
PID_id_part_b
end_1_nozzle_id
end_2_nozzle_id
alpha_descript_id
standard_note_no
pid_index_no
color_code
inspection_iso_id
index_to_pi_dwg
weld_id
sppid_piperun_guid
sppid_drawing_guid
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
character(10)
short
short
short
short
short
character(4)
short
short
short
short
short
short
short
short
short
character(12)
short
character(12)
short
double
double
double
double
double
double
double
double
character(6)
short
double
character(4)
character(4)
integer
integer
character(12)
short
integer
character(8)
character(24)
integer
character(80)
character(32)
character(32)
,
,
,
,
,
standard
standard
standard
standard
standard
note
note
note
note
note
160
160
160
190
230
,
,
,
,
,
,
,
,
,
standard
standard
standard
standard
standard
standard
standard
standard
standard
note
note
note
note
note
note
note
note
note
1064
1056
1064
1056
1064
1056
1064
1056
1056
,
,
,
,
system_unique_no
piping_comp_no
commodity_name
model_code
,
,
,
,
integer
character(20)
character(6)
character(6)
, index 1
67
Database Overview
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
option_code
maximum_temp
sched_thick_basis
commodity_code
MTO_requirements
fabrication_cat
source_of_data
PDS_sort_code
physical_data_id
geometric_standard
weight_code
table_suffix_green
table_suffix_red
materials_grade
bend_radius
bend_angle
face_to_face_dim
dimension_a
dimension_b
dimension_c
surface_area
empty_weight
water_weight
operator_weight
operator_sym_name
chain_operator_no
opening_action
construction_stat
hold_status
heat_tracing_reqmt
heat_tracing_media
heat_tracing_temp
iso_dwg_index_no
isometric_sheet_no
piece_mark_no
color_code
stress_node_no
stress_intens_fact
head_loss_factor
piping_assembly
component_group_no
remarks
standard_note_no_a
standard_note_no_b
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
short
double
character(8)
character(16)
short
short
short
character(6)
character(8)
short
short
short
short
short
double
double
double
double
double
double
double
double
double
double
character(6)
short
short
short
short
short
short
double
integer
character(2)
character(60)
character(8)
short
double
double
character(12)
short
character(50)
short
short
49 , cp_1_nom_pipe_diam , short
50 , cp_1_outside_diam , double
51 , cp_1_end_prep
, short
52 , cp_1_sch_thk
, character(8)
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
option)
68
standard
standard
standard
standard
standard
note
note
note
note
note
575
578
576
577
145
,
,
,
,
,
standard
standard
standard
standard
standard
note
note
note
note
note
390
130
50
200
210
Database Overview
57
58
59
60
61
,
,
,
,
,
cp_1_gasket_gap
cp_1_gasket_option
cp_1_stress_node
cp_1_stress_factor
cp_1_head_loss
,
,
,
,
,
double
short
short
double
double
62 , cp_2_nom_pipe_diam , short
63 , cp_2_outside_diam , double
64 , cp_2_end_prep
, short
65 , cp_2_sch_thk
, character(8)
66 , cp_2_rating
, character(8)
67 , cp_2_face_to_ctr
, double
68 , cp_2_weld_no
, character(8)
69 , cp_2_weld_type
, short
option)
70 , cp_2_gasket_gap
, double
71 , cp_2_gasket_option , short
72 , cp_2_stress_node
, short
73 , cp_2_stress_factor , double
74 , cp_2_head_loss
, double
75 , cp_3_nom_pipe_diam , short
76 , cp_3_outside_diam , double
77 , cp_3_end_prep
, short
78 , cp_3_sch_thk
, character(8)
79 , cp_3_rating
, character(8)
80 , cp_3_face_to_ctr
, double
81 , cp_3_weld_no
, character(8)
82 , cp_3_weld_type
, short
option)
83 , cp_3_gasket_gap
, double
84 , cp_3_gasket_option , short
85 , cp_3_stress_node
, short
86 , cp_3_stress_factor , double
87 , cp_3_head_loss
, double
88 , cp_4_nom_pipe_diam , short
89 , cp_4_outside_diam , double
90 , cp_4_end_prep
, short
91 , cp_4_sch_thk
, character(8)
92 , cp_4_rating
, character(8)
93 , cp_4_face_to_ctr
, double
94 , cp_4_weld_no
, character(8)
95 , cp_4_weld_type
, short
option)
96 , cp_4_gasket_gap
, double
97 , cp_4_gasket_option , short
98 , cp_4_stress_node
, short
99 , cp_4_stress_factor , double
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
69
Database Overview
104, cp_5_sch_thk
105, cp_5_rating
106, cp_5_face_to_ctr
107, cp_5_weld_no
108, cp_5_weld_type
option)
109, cp_5_gasket_gap
110, cp_5_gasket_option
111, cp_5_stress_node
112, cp_5_stress_factor
113, cp_5_head_loss
, character(8)
, character(8)
, double
, character(8)
, short
,
,
,
,
,
double
short
short
double
double
114,
115,
116,
117,
118,
unique_name
vlv_operator_dim_a
vlv_operator_dim_b
vlv_operator_dim_c
vlv_operator_dim_d
,
,
,
,
,
character(12)
double
double
double
double
119,
120,
121,
122,
123,
124,
125,
126,
last_placed_date
generic_comp_no
inspection_key
cp_1_inspect_key
cp_2_inspect_key
cp_3_inspect_key
cp_4_inspect_key
cp_5_inspect_key
,
,
,
,
,
,
,
,
integer
character(20)
short
short
short
short
short
short
# Piping/Tubing Data
table number = 50 , number of columns = 61
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
70
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
system_unique_no
piping_comp_no
commodity_name
model_code
option_code
maximum_temp
nominal_piping_dia
outside_diameter
schedule_thickness
sched_thick_basis
rating
commodity_code
MTO_requirements
fabrication_cat
source_of_data
PDS_sort_code
geometric_standard
weight_code
table_suffix_green
table_suffix_red
materials_grade
pipe_length
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(20)
character(6)
character(6)
short
double
short
double
character(8)
character(8)
character(8)
character(16)
short
short
short
character(6)
short
short
short
short
short
double
, index 1
standard
standard
standard
standard
standard
note
note
note
note
note
575
578
576
577
145
Database Overview
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
surface_area
empty_weight
water_weight
cold_spring_length
construction_stat
hold_status
heat_tracing_reqmt
heat_tracing_media
heat_tracing_temp
iso_dwg_index_no
isometric_sheet_no
piece_mark_no
color_code
piping_assembly
component_group_no
remarks
standard_note_no_a
standard_note_no_b
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
double
double
double
double
short
short
short
short
double
integer
character(2)
character(60)
character(8)
character(12)
short
character(50)
short
short
41 , end_1_end_prep
, short
42 , end_1_weld_no
, character(8)
43 , end_1_weld_type
, short
option)
44 , end_1_gasket_gap
, double
45 , end_1_gasket_opt
, short
46 , end_1_stress_node , short
47 , end_1_stres_int
, double
48 , end_1_head_loss
, double
49 , end_2_end_prep
, short
50 , end_2_weld_no
, character(8)
51 , end_2_weld_type
, short
option)
52 , end_2_gasket_gap
, double
53 , end_2_gasket_opt
, short
54 , end_2_stress_node , short
55 , end_2_stres_int
, double
56 , end_2_head_loss
, double
57 , unique_name
, character(12)
58
59
60
61
,
,
,
,
last_placed_date
inspection_key
end_1_inspect_key
end_2_inspect_key
,
,
,
,
standard
standard
standard
standard
note
note
note
note
130
50
200
210
integer
short
short
short
,
,
,
,
,
system_unique_no
instrument_comp_no
model_code
option_code
sched_thick_basis
,
,
,
,
,
integer
character(20)
character(6)
short
character(8)
, index 1
, standard note 400
, standard note 332
71
Database Overview
72
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
MTO_requirements
fabrication_cat
source_of_data
PDS_sort_code
physical_data_id
geometric_standard
weight_code
table_suffix_green
table_suffix_red
materials_grade
face_to_face_dim
dimension_a
dimension_b
dimension_c
surface_area
empty_weight
water_weight
operator_weight
operator_type
operator_sym_name
chain_operator_no
chain_length
opening_action
construction_stat
hold_status
design_resp
construction_resp
heat_tracing_reqmt
heat_tracing_media
heat_tracing_temp
insulation_purpose
insulation_thick
insulation_density
cleaning_reqmts
safety_class
module_no
package_system_no
iso_dwg_index_no
isometric_sheet_no
piece_mark_no
color_code
stress_node_no
stress_intens_fact
head_loss_factor
piping_assembly
component_group_no
remarks
standard_note_no_a
standard_note_no_b
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
short
short
short
character(6)
character(8)
short
short
short
short
short
double
double
double
double
double
double
double
double
double
character(6)
short
double
short
short
short
short
short
short
short
double
short
double
double
short
short
character(16)
character(12)
integer
character(2)
character(60)
character(8)
short
double
double
character(12)
short
character(50)
short
short
55
56
57
58
,
,
,
,
cp_1_nom_pipe_diam
cp_1_outside_diam
cp_1_end_prep
cp_1_sch_thk
,
,
,
,
short
double
short
character(8)
standard
standard
standard
standard
standard
note
note
note
note
note
575
578
576
577
145
,
,
,
,
standard
standard
standard
standard
note
note
note
note
1010
1028
1028
1028
,
,
,
,
,
,
,
standard
standard
standard
standard
standard
standard
standard
note
note
note
note
note
note
note
390
130
50
160
160
200
210
(units)
(units)
(units)
(units)
Database Overview
59 , cp_1_rating
, character(8)
60 , cp_1_face_to_ctr
, double
61 , cp_1_weld_no
, character(8)
62 , cp_1_weld_type
, short
option)
63 , cp_1_gasket_gap
, double
64 , cp_1_gasket_option , short
65 , cp_1_stress_node
, short
66 , cp_1_stress_factor , double
67 , cp_1_head_loss
, double
68 , cp_2_nom_pipe_diam , short
69 , cp_2_outside_diam , double
70 , cp_2_end_prep
, short
71 , cp_2_sch_thk
, character(8)
72 , cp_2_rating
, character(8)
73 , cp_2_face_to_ctr
, double
74 , cp_2_weld_no
, character(8)
75 , cp_2_weld_type
, short
option)
76 , cp_2_gasket_gap
, double
77 , cp_2_gasket_option , short
78 , cp_2_stress_node
, short
79 , cp_2_stress_factor , double
80 , cp_2_head_loss
, double
81 , cp_3_nom_pipe_diam , short
82 , cp_3_outside_diam , double
83 , cp_3_end_prep
, short
84 , cp_3_sch_thk
, character(8)
85 , cp_3_rating
, character(8)
86 , cp_3_face_to_ctr
, double
87 , cp_3_weld_no
, character(8)
88 , cp_3_weld_type
, short
option)
89 , cp_3_gasket_gap
, double
90 , cp_3_gasket_option , short
91 , cp_3_stress_node
, short
92 , cp_3_stress_factor , double
93 , cp_3_head_loss
, double
94 , cp_4_nom_pipe_diam
95 , cp_4_outside_diam
96 , cp_4_end_prep
97 , cp_4_sch_thk
98 , cp_4_rating
99 , cp_4_face_to_ctr
100, cp_4_weld_no
101, cp_4_weld_type
option)
102, cp_4_gasket_gap
103, cp_4_gasket_option
104, cp_4_stress_node
105, cp_4_stress_factor
, short
, double
, short
, character(8)
, character(8)
, double
, character(8)
, short
,
,
,
,
double
short
short
double
73
Database Overview
106, cp_4_head_loss
107, cp_5_nom_pipe_diam
108, cp_5_outside_diam
109, cp_5_end_prep
110, cp_5_sch_thk
111, cp_5_rating
112, cp_5_face_to_ctr
113, cp_5_weld_no
114, cp_5_weld_type
option)
115, cp_5_gasket_gap
116, cp_5_gasket_option
117, cp_5_stress_node
118, cp_5_stress_factor
119, cp_5_head_loss
, double
, short
, double
, short
, character(8)
, character(8)
, double
, character(8)
, short
,
,
,
,
,
double
short
short
double
double
120,
121,
122,
123,
124,
125,
unique_name
bend_angle
vlv_operator_dim_a
vlv_operator_dim_b
vlv_operator_dim_c
vlv_operator_dim_d
,
,
,
,
,
,
character(12)
double
double
double
double
double
126,
127,
128,
129,
130,
131,
132,
133,
last_placed_date
generic_comp_no
inspection_key
cp_1_inspect_key
cp_2_inspect_key
cp_3_inspect_key
cp_4_inspect_key
cp_5_inspect_key
,
,
,
,
,
,
,
,
integer
character(20)
short
short
short
short
short
short
74
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
system_unique_no
pipe_support_no
model_code_phy
model_code_log
iso_support_type_a
iso_support_type_b
iso_support_type_c
iso_support_type_d
details_for_shop
details_for_field
fabrication_orient
commodity_code
MTO_requirements
fabrication_cat
weight
construction_stat
hold_status
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(20)
character(6)
character(6)
short
short
short
short
character(50)
character(50)
character(20)
character(16)
short
short
double
short
short
, index 1
,
,
,
,
standard
standard
standard
standard
note
note
note
note
380
380
380
380
,
,
,
,
,
standard
standard
standard
standard
standard
note
note
note
note
note
365
180
1028 (units)
130
50
Database Overview
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
, standard_note_no
, short
, standard
, iso_dwg_index_no
, integer
, isometric_sheet_no , character(2)
, piece_mark_no
, character(60)
, color_code
, character(8)
, isometric_dim_a
, double
, isometric_dim_b
, double
, isometric_dim_c
, double
, isometric_dim_d
, double
, isometric_dim_e
, double
, trans_rigidity_x
, double
, trans_rigidity_y
, double
, trans_rigidity_z
, double
, rot_rigidity_x
, double
, rot_rigidity_y
, double
, rot_rigidity_z
, double
, spring_gap_length , double
, sping_gap_direct
, short
, number_of_springs , short
, last_placed_date
, integer
, inspection_key
, short
, mark_number
, character(80)
, group_id
, integer
, gang_id
, integer
, material_grade
, short
, standard
, weld_code
, short
, material_index
, character(16)
, operating_load
, double
, installed_load
, double
, hydrostatic_load
, double
, total_movement_1
, double
, in subunits -, total_movement_2
, double
, in subunits -, rod_diameter
, double
, in subunits
note 499
note 145
distance attribute
distance attribute
# equip_group
table number = 21, number of columns = 14
1
2
3
4
5
6
7
8
9
10
11
12
13
14
,
,
,
,
,
,
,
,
,
,
,
,
,
,
equip_indx_no
equip_no
equip_descr_1
equip_descr_2
tutorial_no
equip_class
dry_weight
oper_weight_1
oper_weight_2
insulation_thk
construction_stat
equipment_division
approval_status
insulation_purpose
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(30)
character(40)
character(40)
character(6)
character(2)
double
double
double
double
short
short
short
short
# equip_nozzle
75
Database Overview
table number = 22, number of columns = 25
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
nozzle_indx_no
, integer
nozzle_no
, character(10)
equip_indx_no
, integer
nominal_piping_dia , short
rating
, character(8)
preparation , short
, standard note 330
piping_mater_class , character(16)
unit_no
, character(12)
fluid_code
, short
, standard note 125
unit_code
, character(3)
line_sequence_no
, character(16)
heat_tracing_reqmt , short
, standard note 200
heat_tracing_media , short
, standard note 210
insulation_purpose , short
, standard note 220
insulation_thk
, double
table_suffix
, short
, standard note 576
service
, character(20)
schedule_thickness , character(8)
nor_therm_growth_X , double
nor_therm_growth_Y , double
nor_therm_growth_Z , double
alt_therm_growth_X , double
alt_therm_growth_Y , double
alt_therm_growth_Z , double
construction_stat , short
, standard note 130
# equip_nozzle_extended
table number = 23, number of columns = 68
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
76
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
nozzle_indx_no
equip_indx_no
parm_indx_no
parm_noz_no
face_of_flange_x
face_of_flange_y
face_of_flange_z
face_flange_pri_1
face_flange_pri_2
face_flange_pri_3
face_flange_sec_1
face_flange_sec_2
face_flange_sec_3
face_flange_nor_1
face_flange_nor_2
face_flange_nor_3
nozzle_type
nozzle_length_1
nozzle_length_2
nozzle_radius
reference_item
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
integer
integer
short
double
double
double
double
double
double
double
double
double
double
double
double
short
double
double
double
character(11)
Database Overview
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
ref_loc_x
ref_loc_y
ref_loc_z
ref_loc_pri_1
ref_loc_pri_2
ref_loc_pri_3
ref_loc_sec_1
ref_loc_sec_2
ref_loc_sec_3
ref_loc_nor_1
ref_loc_nor_2
ref_loc_nor_3
orientation_1
orientation_2
orientation_3
orientation_4
dimension_1
dimension_2
dimension_3
dimension_4
dimension_5
dimension_6
c_face_of_flange_x
c_face_of_flange_y
c_face_of_flange_z
c_face_flange_pri
c_face_flange_sec
c_face_flange_nor
c_nozzle_length_1
c_nozzle_length_2
c_nozzle_radius
c_ref_loc_x
c_ref_loc_y
c_ref_loc_z
c_ref_loc_pri
c_ref_loc_sec
c_ref_loc_nor
c_orientation_1
c_orientation_2
c_orientation_3
c_orientation_4
c_dimension_1
c_dimension_2
c_dimension_3
c_dimension_4
c_dimension_5
c_dimension_6
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
character(41)
character(41)
character(41)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(41)
character(41)
character(41)
character(31)
character(31)
character(31)
character(11)
character(11)
character(11)
character(11)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
#equip_datum_point
table number = 24, number of columns = 22
1
2
, equip_indx_no
, parm_indx_no
, integer
, integer
77
Database Overview
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
point_type
point_indx_no
loc_x
loc_y
loc_z
loc_pri_1
loc_pri_2
loc_pri_3
loc_sec_1
loc_sec_2
loc_sec_3
loc_nor_1
loc_nor_2
loc_nor_3
c_loc_x
c_loc_y
c_loc_z
c_loc_pri
c_loc_sec
c_loc_nor
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
short
short
double
double
double
double
double
double
double
double
double
double
double
double
character(41)
character(41)
character(41)
character(31)
character(31)
character(31)
# equip_primitive
table number = 25, number of columns = 32
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
78
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
equip_indx_no
prim_name
place_pnt_no
place_by_x
place_by_y
place_by_z
place_by_pri_1
place_by_pri_2
place_by_pri_3
place_by_sec_1
place_by_sec_2
place_by_sec_3
place_by_nor_1
place_by_nor_2
place_by_nor_3
category_type
dimension_a
dimension_b
dimension_c
dimension_d
dimension_e
c_place_by_x
c_place_by_y
c_place_by_z
c_place_by_pri
c_place_by_sec
c_place_by_nor
c_dimension_a
c_dimension_b
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(20)
short
double
double
double
double
double
double
double
double
double
double
double
double
short
double
double
double
double
double
character(41)
character(41)
character(41)
character(31)
character(31)
character(31)
character(31)
character(31)
Database Overview
30 , c_dimension_c
31 , c_dimension_d
32 , c_dimension_e
, character(31)
, character(31)
, character(31)
# equip_primitive_usr_proj_shape
table number = 26, number of columns = 99
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
equip_indx_no
prim_name
place_point_no
place_by_pri_1
place_by_pri_2
place_by_pri_3
place_by_sec_1
place_by_sec_2
place_by_sec_3
place_by_nor_1
place_by_nor_2
place_by_nor_3
category_type
number_vertices
projection
vertex_1_x
vertex_1_y
vertex_2_x
vertex_2_y
vertex_3_x
vertex_3_y
vertex_4_x
vertex_4_y
vertex_5_x
vertex_5_y
vertex_6_x
vertex_6_y
vertex_7_x
vertex_7_y
vertex_8_x
vertex_8_y
vertex_9_x
vertex_9_y
vertex_10_x
vertex_10_y
vertex_11_x
vertex_11_y
vertex_12_x
vertex_12_y
vertex_13_x
vertex_13_y
vertex_14_x
vertex_14_y
vertex_15_x
vertex_15_y
vertex_16_x
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
character(20)
short
double
double
double
double
double
double
double
double
double
short
short
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
double
79
Database Overview
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
80
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
vertex_16_y
vertex_17_x
vertex_17_y
vertex_18_x
vertex_18_y
vertex_19_x
vertex_19_y
vertex_20_x
vertex_20_y
c_place_by_pri
c_place_by_sec
c_place_by_nor
c_projection
c_vertex_1_x
c_vertex_1_y
c_vertex_2_x
c_vertex_2_y
c_vertex_3_x
c_vertex_3_y
c_vertex_4_x
c_vertex_4_y
c_vertex_5_x
c_vertex_5_y
c_vertex_6_x
c_vertex_6_y
c_vertex_7_x
c_vertex_7_y
c_vertex_8_x
c_vertex_8_y
c_vertex_9_x
c_vertex_9_y
c_vertex_10_x
c_vertex_10_y
c_vertex_11_x
c_vertex_11_y
c_vertex_12_x
c_vertex_12_y
c_vertex_13_x
c_vertex_13_y
c_vertex_14_x
c_vertex_14_y
c_vertex_15_x
c_vertex_15_y
c_vertex_16_x
c_vertex_16_y
c_vertex_17_x
c_vertex_17_y
c_vertex_18_x
c_vertex_18_y
c_vertex_19_x
c_vertex_19_y
c_vertex_20_x
c_vertex_20_y
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
double
double
double
double
double
double
double
double
double
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
character(31)
Database Overview
# equip_parametric
table number = 27, number of columns = 22
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
equip_indx_no
parm_indx_no
symbol_name
place_pnt_no
place_by_x
place_by_y
place_by_z
place_by_pri_1
place_by_pri_2
place_by_pri_3
place_by_sec_1
place_by_sec_2
place_by_sec_3
place_by_nor_1
place_by_nor_2
place_by_nor_3
c_place_by_x
c_place_by_y
c_place_by_z
c_place_by_pri
c_place_by_sec
c_place_by_nor
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
integer
integer
character(10)
short
double
double
double
double
double
double
double
double
double
double
double
double
character(41)
character(41)
character(41)
character(31)
character(31)
character(31)
# equip_parametric_extended
table number = 28, number of columns = 12
1
2
3
4
5
6
7
8
9
10
11
12
,
,
,
,
,
,
,
,
,
,
,
,
parm_indx_no
form_indx_no
form_name
form_fld
data_type
dimension_no
nozzle_fld
fld_attribute
fld_default
fld_name
value_real
value_char
,
,
,
,
,
,
,
,
,
,
,
,
integer
short
character(10)
short
short
short
short
short
character(21)
character(13)
double
character(41)
81
Database Overview
Reference Database
# Specification/Material Reference Database
# Default Relational Database Definition
# The user must not revise this database definition other than to
# change column names.
# Piping Materials Class Data
table number = 201, number of
1 , system_unique_no
,
2 , piping_mater_class
,
3 , revision_no
,
4 , version_no
,
5 , revision_date
,
6 , fluid_code
,
7 , mater_of_construct
,
8 , corrosion_allow
,
9 , mat_description
,
10, service_lim_table
,
11, diameter_table
,
12, thickness_table
,
13, materials_table
,
14, thickness_equation
,
15, branch_table
,
16, tap_data_table
,
17, vent_drain_macro
,
18, gasket_separation
,
19, standard_note_no_a
,
20, standard_note_no_b
,
21, revision_mngt_date
,
22, bend_deflect_table
,
23, pipe_length_table
,
columns = 23
integer
character(16)
character(2)
character(2)
character(10
character(6)
character(6)
double
short
character(6)
character(6)
character(6)
character(6)
character(6)
character(6)
character(6)
character(6)
character(8)
short
short
integer
character(6)
character(6)
82
, standard note
125
, standard note
148
, standard note
, standard note
499
499
, index
, standard note
400
, standard note
330
, standard note
576
, standard note
330
Database Overview
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
26,
27,
28,
rcp_rating
rcp_sch_thk
rcp_table_suffix
commodity_code
model_code
PDS_sort_code
modifier
geometric_standard
weight_code
fabrication_cat
materials_grade
standard_note_no_a
standard_note_no_b
input_form_type
,
,
,
,
,
,
,
,
,
,
,
,
,
,
character(8)
character(8)
short
character(16)
character(6)
character(6)
double
short
short
short
short
short
short
short
, standard note
577
,
,
,
,
,
,
,
note
note
note
note
note
note
note
575
578
180
145
499
499
990
, standard note
400
, standard note
330
, standard note
576
, standard note
330
, standard note
577
,
,
,
,
,
,
,
note
note
note
note
note
note
note
575
578
180
145
499
499
990
, standard note
400
standard
standard
standard
standard
standard
standard
standard
standard
standard
standard
standard
standard
standard
standard
83
Database Overview
7 , gcp_end_prep
8 , gcp_rating
9 , gcp_sch_thk
10, gcp_table_suffix
11, rcp_from_nom_diam
12, rcp_to_nom_diam
13, rcp_end_prep
14, rcp_rating
15, rcp_sch_thk
16, rcp_table_suffix
17, physical_data_id
18, PDS_sort_code
19, modifier
20, geometric_standard
21, weight_code
22, fabrication_cat
23, materials_grade
24, standard_note_no_a
25, standard_note_no_b
26, input_form_type
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
short
character(8)
character(8)
short
short
short
short
character(8)
character(8)
short
character(8)
character(6)
double
short
short
short
short
short
short
short
84
, standard note
330
, standard note
576
, standard note
330
, standard note
577
,
,
,
,
,
,
,
575
578
180
145
499
499
990
standard
standard
standard
standard
standard
standard
standard
note
note
note
note
note
note
note
, standard note
, standard note
, index
, index
400
330
Database Overview
5 , rcp_from_nom_diam
6 , rcp_to_nom_diam
7 , commodity_code
8 , quantity
9 , fabrication_cat
10, standard_note_no
,
,
,
,
,
,
short
short
character(16)
double
short
short
,
,
,
,
standard
standard
standard
standard
note
note
note
note
200
200
220
220
,
,
,
,
standard
standard
standard
standard
note
note
note
note
200
200
220
220
85
Database Overview
3
4
5
6
7
,
,
,
,
,
model_code
gcp_npd_from
gcp_npd_to
rcp_npd_from
rcp_npd_to
,
,
,
,
,
character(6)
short
short
short
short
, standard note
575
86
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.
87
Reference Data
Object
Text
us_pcdim.l
us_pcdim.l.t
us_pjstb.l.t
us_shbom.l
us_lgbom.l
Object
Text
pip_gcom.l
pip_gcom.l.t
assembly.l
assembly.l.t
labels.l
Object
Text
zi_eqpms.lib
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
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.
88
Reference Data
89
Reference 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:
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:
1 , system_unique_no
, integer
2 , piping_mater_class
, character(16)
, index 1
90
Reference Data
3 ,
4 ,
5 ,
6 ,
7 ,
8 ,
9 ,
10,
11,
12,
13,
14,
15,
16,
17,
18,
19,
20,
21,
22,
23,
24,
25,
26,
27,
28,
commodity_name
option_code
maximum_temp
gcp_from_nom_diam
gcp_to_nom_diam
gcp_end_prep
gcp_rating
gcp_sch_thk
gcp_table_suffix
rcp_from_nom_diam
rcp_to_nom_diam
rcp_end_prep
rcp_rating
rcp_sch_thk
rcp_table_suffix
commodity_code
model_code
PDS_sort_code
modifier
geometric_standard
weight_code
fabrication_cat
materials_grade
standard_note_no_a
standard_note_no_b
input_form_type
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
,
character(6)
short
double
short
short
short
character(8)
character(8)
short
short
short
short
character(8)
character(8)
short
character(16)
character(6)
character(6)
double
short
short
short
short
short
short
short
,
,
,
,
,
,
,
standard
standard
standard
standard
standard
standard
standard
note
note
note
note
note
note
note
575
578
180
145
499
499
990
The following is a sample neutral file for the Piping Commodity Specification Data. Entries in this
table should be sorted alphanumerically by commodity_name.
fpipe.pcd
metric_npd.pcd
equiv_npd.pcd
gasket.pcd
piplen_tbl.pcd
fluid_code.pcd
gskt_tbl.pcd
thickness.pcd
91
Reference Data
92
Reference Data
93
Reference Data
A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\instrment.data.
94
Sc/Th
NREQD
NREQD
NREQD
default taps
Tap Code
E$37591XXX
E$50421064
E$50591XXX
Reference Data
> 0.75
0.75
> 1
1
> 1.25
1.25
> 1.5
1.5
> 2
2
2.5
> 3
3
3.5
> 4
4
5
6
8
10
12
14
16
18
20
24
26
28
30
32
34
36
42
48
1
691
1
691
1
691
1
691
1
691
691
1
691
691
1
691
691
691
691
691
691
691
691
691
691
691
691
691
691
691
691
691
691
691
CL3000
CL3000
CL3000
CL3000
CL3000
CL3000
CL3000
-
421
591
421
591
421
591
421
591
421
591
591
421
591
591
421
591
591
591
591
591
591
591
591
591
591
591
591
591
591
591
591
591
591
591
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
NREQD
E$75421064
E$75591XXX
E001421064
E001591XXX
E1 $2,421,064
E1 $2591XXX
E1 $5,421,064
E1 $5591XXX
E002421064
E002591XXX
E2 $5591XXX
E003421064
E003591XXX
E3 $5591XXX
E004421064
E004591XXX
E005591XXX
E006591XXX
E008591XXX
E010591XXX
E012591XXX
E014591XXX
E016591XXX
E018591XXX
E020591XXX
E024591XXX
E026591XXX
E028591XXX
E030591XXX
E032591XXX
E034591XXX
E036591XXX
E042591XXX
E048591XXX
95
Reference Data
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.
96
Reference Data
A sample neutral file for US practice is delivered in the file
win32app\ingr\rdusrdb\spec_data\implied.data.
97
Reference Data
98
Reference Data
99
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.
100
Reference Data
101
Reference Data
The resulting graphics created by the PAL file look like this:
102
SECTION 4
103
104
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.
105
106
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
No_Inputs 1 No_Outputs 0
Units= NPD_IN
! Diam
0.5
0.75
1
1.5
2
3
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
END
107
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.
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
No_Inputs 2 No_Outputs 6
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
-
108
800
-20
100
200
300
400
500
600
650
700
750
800
-20
100
200
300
400
500
600
650
700
750
800
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
.4
10800
20000
20000
20000
20000
20000
18900
17300
17000
16500
13000
10800
20000
20000
20000
20000
20000
18900
17300
17000
16500
13000
10800
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
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)
109
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.
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
110
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.
111
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.
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.
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.
112
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).
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.
113
114
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
115
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'
Call Get_Physical_Data ( physical_data_source )
parametric_shape = 'OP3'
Call Draw_Parametric_Shape ( parametric_shape )
Stop
End
Listing for Sub-Symbol Processor OP_3
116
Practice
Range
Suffix
U.S. Practice
1-99
AMS
100-199
DIN
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.
117
118
119
120
Physical Data
Selecting the Component Data option of the Place Component Error Data form displays the
physical data used to place the component.
121
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).
122
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:
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.
123
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.
124
When placing change of direction components, this table is used in conjunction with the Bend
Deflection Table.
125
126
Placement Examples
This section outlines the placement data for a bend, reducer, and tee placed on an existing
segment.
90 Degree Bend
127
Branch (4"x4")
128
SECTION 5
Creating 3D Models
This chapter describes the basics of 3D modeling using the Equipment Modeling and Piping
Designer Tasks.
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.
129
Creating 3D Models
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.
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.
130
Creating 3D Models
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
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.
131
Creating 3D Models
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.
132
Creating 3D Models
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.
133
Creating 3D Models
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.
134
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.
135
Creating 3D Models
View Windows
Closedeletes a window.
Minimizecollapses a window.
Maximizeenlarges a window to its maximum size. If you choose the
136
Creating 3D Models
maximize button on a window that is already at its maximum size, the
window is restored to its previous size and location.
Horizontal slider barallows you to drag the view to the left or right in
the window.
Vertical slider barallows you to drag the view up or down in the
window.
Move Arrowsdrag the data button on the title bar to move the window to
a new location on the screen.
Vertical Arrowsappear 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 Arrowsappear 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 Arrowsappear 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.
137
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.
138
Creating 3D Models
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.
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
139
Creating 3D Models
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.
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.
140
Collapse/Restore
Pop-to-bottom
Pop-to-top
Repaint
Modify/Resize
Restore Size
Creating 3D Models
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.
Select the File Design command to save the active form location. All subsequent forms will
display in the saved location.
141
Creating 3D Models
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 :
142
Creating 3D Models
Northing : N 0' 0" Plant
Elevation : El 0' 0" Plant
Design Volume Monument in Plant Coordinate System :
Easting : E 0' 0" Plant
Northing : N 0' 0" Plant
Elevation : El 0' 0" Plant
Orientation of Design Volume Coordinate:
East
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 :
East : E
West : W
North : N
South : S
Elevation : El
143
Creating 3D Models
Dimensioning :
English
Coordinate Label/Readout Format
(Active)
Readout Description On
Coordinate Label/Readout Units
Active Coordinate Label Format : East 1' 6 3/8" Plant
Active Coordinate Readout Format : E 1' 6 3/8" Plant
Label Units :
Readout Units :
Subunits Only
Label Descritions :
Master Units Short Description : '
Subunits Short Description : "
Master Units and Subunits Separator :
Subunits and Fraction of Subunits Separator :
Readout Descriptions :
Master Units Short Description : '
Subunits Short Description : "
Master Units and Subunits Separator :
Subunits and Fraction of Subunits Separator :
Secondary Units Descriptions :
Master Units Short Description :
144
Creating 3D Models
Subunits Short Description : MM
Master Units and Subunits Separator :
Subunits and Fraction of Subunits Separator :
Coordinate Label/Readout Precision
Active Coordinate Label Format : East 1' 6 3/8" Plant
Active Coordinate Readout Format : E 1' 6 3/8" Plant
Label Precision : Decimal to nearest 1/16
Label Alphanumeric Fraction
Readout Precision : Decimal to nearest 1/16
Secondary Precision : Decimal to nearest integer
145
Creating 3D Models
146
Creating 3D Models
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
Physical
Category
Level
10
Color
9
Weight
2
Symbology
Solid
Eqp Category 2
White
Solid
Eqp Category 3
Eqp Category 4
1
1
White
White
0
0
Solid
Solid
Eqp Category 5
Eqp Category 6
1
1
White
White
0
0
Solid
Solid
Eqp Category 7
Eqp Category 8
1
1
White
White
0
0
Solid
Solid
Eqp Category 9
White
Solid
Eqp Category 10
White
Solid
Eqp Category 11
Eqp Category 12
1
1
White
White
0
0
Solid
Solid
Eqp Category 13
Eqp Category 14
1
1
White
White
0
0
Solid
Solid
Eqp Category 15
White
Solid
147
Creating 3D Models
Eqp Category 16
White
Solid
Eqp Category 17
Eqp Category 18
1
1
White
White
0
0
Solid
Solid
Eqp Category 19
Eqp Category 20
1
1
White
White
0
0
Solid
Solid
Category
Level
Color
Weight
Symbology
Nozzle Category
Nozzle Category
Small
Medium
12
12
9
9
3
3
Solid
Solid
Nozzle Category
Large
12
Solid
Level
40
Color
8
Weight
1
Symbology
Solid
41
Solid
42
10
Solid
43
10
Solid
44
11
Solid
45
11
Solid
46
12
Solid
47
12
Solid
56
White
Solid
Nozzles
Envelopes
Category
Maintanence Envelope
(Hard)
Maintanence Envelope
(Soft)
Access Envelope
(Hard)
Access Envelope
(Soft)
Safety Envelope
(Hard)
Safety Envelope
(Soft)
Construction
Envelope (Hard)
Construction
Envelope (Soft)
Insulation Envelope
Equipment Graphic
Symbology
Steel
Category
(continued
)
Ladders
Level
20
Color
White
Weight
1
Symbology
Solid
Platforms
Handrails
21
22
White
White
1
1
Solid
Solid
Miscellaneous Light
Steel
166
23
White
Solid
Level
51
Color
White
Weight
0
Symbology
Solid
52
White
Solid
53
White
Solid
54
White
Solid
55
White
Solid
Semi-Intelligent
Graphics
Category
Semi-Intelligent
Category 1
Semi-Intelligent
Category 2
Semi-Intelligent
Category 3
Semi-Intelligent
Category 4
Semi-Intelligent
Category 5
Level
Color
Weight
Symbology
Dumb Category 1
Dumb Category 2
30
1
White
White
0
0
Solid
Solid
Dumb Category 3
Dumb Category 4
1
1
White
White
0
0
Solid
Solid
Dumb Category 5
Dumb Category 6
1
1
White
White
0
0
Solid
Solid
Dumb Category 7
Dumb Category 8
1
1
White
White
0
0
Solid
Solid
Dumb Category 9
Dumb Category 10
1
1
White
White
0
0
Solid
Solid
Dumb Category 11
Dumb Category 12
1
1
White
White
0
0
Solid
Solid
Dumb Category 13
Dumb Category 14
1
1
White
White
0
0
Solid
Solid
White
Solid
Level
48
Color
15
Weight
8
Symbology
Solid
Dumb Category 15
Miscellaneous
Category
Place Point
148
Creating 3D Models
Datum Point
50
13
10
Solid
Hole Elements
15
White
Solid
2-D Shadows
12
Solid
Project Data
Manager
Nozzle
Default
Placement
Options
Nominal Piping
Diameter
System of Units
English
Small is <=
:
: 2IN
Large is >=
Table Name
: 14IN
:
D036
: Bolted 5
Female - 5
Male - 5
Project Data
Manager
Equipment Reference Database Management
167
E:\pdsproj\rd
b\eqp\approve
d\
zi_eqpms.lib
E:\pdsproj\rd
b\eqp\approve
d\
zi_tutlib.lib
E:\pdsproj\rd
b\eqp\approve
d\
us_pcdim.l
E:\pdsproj\rd
b\eqp\approve
d\
us_pcdim.l
E:\pdsproj\rd
b\eqp\approve
d\
std_note.l
E:\pdsproj\rd
b\eqp\approve
d\
us_pjstb.l
E:\pdsproj\rd
b\eqp\approve
d\
equip.cel
90
Degree Torus
1"
1"
149
Creating 3D Models
150
Creating 3D Models
2. Select the Equipment Modeling option to enter the graphics environment.
The system displays the Equipment Modeling form listing the available design area numbers
and their corresponding descriptions.
151
Creating 3D Models
3. Select Design Area
Select the 3D design area to modify and click Confirm.
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.
152
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 SP -primary axis
S - secondary axis
** - indicating the active axis
-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).
153
Creating 3D Models
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).
154
Creating 3D Models
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.
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.
155
Creating 3D Models
156
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.
157
Creating 3D Models
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
:
Commodity Name Table
:
Pipe Length Threshold Table
:
Segment Pipe Run Length Threshold Table :
Weld Type Table
:
Flange Data Module
:
Reinforcing Weld Data Module
:
Reinforcing Pad Data Module
:
Pipe Commodity Name
:
Tube Commodity Name
:
Field Weld Symbol Name
:
Isometric Drawing Symbol Name
:
Angular Tolerance (Automated Component):
Vicinity Tolerance
:
BEND_DEFLECTION
COMMODITY_ITEM_NAME
PIPE_LENGTH
PIPE_RUN_LENGTH
WELD_TYPE_TABLE
PIPING
TUBE
0.500000
4.000000
:
:
:
:
:
:
:
:
:
Commodity Name
Off
On
Header
Append Prefix
Expanded
Larger of Override and Spec
English
IN
:
:
:
(Spec) :
lb/ft3
ft2
lb
degF
158
Creating 3D Models
Weights
Piping Commodity
Piping Specialty
Instrument
Piping/Tubing
Pipe Support
Model Symbology
Color
:
:
:
:
:
:
:
:
2
2
2
2
2
Simple
Model Category
Piping Segment
Not Approved
Small
Piping Segment
Not Approved
Medium
Piping Segment
Not Approved
Large
Piping Segment
Approved
Small
Piping Segment
Approved
Medium
Piping Segment
Approved
Large
Piping/Tubing
Not Approved
Small
Piping/Tubing
Not Approved
Medium
Piping/Tubing
Not Approved
Large
Piping/Tubing
Approved
Small
Piping/Tubing
Approved
Medium
Piping/Tubing
Approved
Large
Piping Commodity
Not Approved
Small
Piping Commodity
Not Approved
Medium
Piping Commodity
Not Approved
Large
Piping Commodity
Approved
Small
Piping Commodity
Approved
Medium
Piping Commodity
Approved
Large
Piping Specialty
Not Approved
Small
Piping Specialty
Not Approved
Medium
Piping Specialty
Not Approved
Large
Piping Specialty
Approved
Small
Piping Specialty
Approved
Medium
Piping Specialty
Approved
Large
Instrument
Not Approved
Small
Instrument
Not Approved
Medium
Instrument
Not Approved
Large
Instrument
Approved
Small
Instrument
Approved
Medium
Instrument
Approved
Large
Pipe Support - Logical Not Approved
N/A
Pipe Support - Physical Not Approved
N/A
Pipe Support - Logical Approved
N/A
Pipe Support - Physical Approved
N/A
Miscellaneous Graphics
Diagnostic Markers
Automated Component/Pipe Placement Markers
Model Reconstruction Markers
Level
1
11
21
31
41
51
3
13
23
33
43
53
2
12
22
32
42
52
4
14
24
34
44
54
5
15
25
35
45
55
7
10
37
40
58
59
62
63
Color
Blue
Blue
Blue
Blue
Blue
Blue
Green
Green
Green
Green
Green
Green
Green
Green
Green
Green
Green
Green
Orange
Orange
Orange
Orange
Orange
Orange
Orange
Orange
Orange
Orange
Orange
Orange
Violet
White
Violet
White
Red
Red
Red
Red
:
:
:
:
:
:
:
:
:
:
:
2
2
2
2
2
125
6"
6"
:
:
:
:
:
:
:
:
:
:
:
:
:
Size Independent
Almost Precise
Piping Job Spec
English
English
Preferred Bolt Length
Off
Off
6Q3C95
6Q3C97
6Q3C98
BOLT_DATA
FLANGE_DATA_MTO
159
Creating 3D Models
Bolt Length Table
BOLT_LENGTH
Undefined
<125,0>
Undefined
<220,0>
100-3/4IN
Standard Note
0 0"
0.000
Standard Note
0.000
Standard Note
0.000
Standard Note
0.000
Standard Note
0 lb/ft3
Standard Note
Standard Note
0 degF
Standard Note
Standard Note
Standard Note
Standard Note
Standard Note
0.000
Standard
0.000
Standard
0.000
Standard
0.000
Standard
0.000
Standard
Number is
Number is
Undefined
<1064,0>
Number is
Undefined
<1056,0>
Number is
Undefined
<1064,0>
Number is
Undefined
<1056,0>
Number is
Number is
Undefined
Undefined
<200,0>
<210,0>
Number
Number
Number
Number
Number
is
is
is
is
is
Undefined
Undefined
Undefined
Undefined
Undefined
<160,0>
<160,0>
<160,0>
<130,0>
<50,0>
Note Number is
Undefined
<1064,0>
Note Number is
Undefined
<1056,0>
Note Number is
Undefined
<1064,0>
Note Number is
Undefined
<1056,0>
Note Number is
Undefined
<1056,0>
Standard Note
Standard Note
Number is Undefined
Number is Undefined
<340,0>
<570,0>
Standard Note
Standard Note
Number is Undefined
Number is Undefined
<190,0>
<230,0>
Number is Undefined
<125,0>
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Standard Note
0.000
:
:
:
:
:
:
:
:
Hard Check
Hard Check
No Check
No Check
Soft Check
Soft Check
Soft Check
Soft Check
: 0.500000
: 1/4"
160
Creating 3D Models
End Prep Compatibilities Bolted End Preps
FFFE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
FFFEWG FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
RFFE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
RFFEWG FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
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
RFLFE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
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
FFTBEWG FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
RFTBE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
RFTBEWG FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE
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
161
Creating 3D Models
FTE
MGE FGE
MQCE FQCE
MFRE FFRE
MHE FHE
SPE BLE
PE BE TBE PE SE SWE FTE HCE
3"FFPE HCE
Project Data Manager
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
Project Data Manager
Reference Database Management
Material/Specification Reference Database
Approved :
ra_tcproj
Piping Job Specification Table Library
Approved :
wegl
..\win32app\ingr\rdusrdb\
Short Material Description Library
Approved :
wegl
..\win32app\ingr\rdusrdb\
Long Material Description Library
Approved :
wegl
..\win32app\ingr\rdusrdb\
Specialty Material Description Library
Approved :
wegl
..\win32app\ingr\rdusrdb\
Standard Note Library
Approved :
wegl
..\win32app\ingr\pdshell\lib\
Label Description Library
Approved :
wegl
..\win32app\ingr\pdshell\lib\
Piping Assembly Library
Approved :
wegl
..\win32app\ingr\pdshell\lib\
Graphic Commodity Library
Approved :
wegl
..\win32app\ingr\pdshell\lib\
Physical Data Library - U.S. Practice
Approved :
wegl
..\win32app\ingr\rdusrdb\
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 :
us_pjstb.l
us_shbom.l
us_lgbom.l
us_spbom.l
std_note.l
labels.l
assembly.l
pip_gcom.l
us_pcdim.l
162
Creating 3D Models
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 nongraphical 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.
163
Creating 3D Models
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.
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.
164
Creating 3D Models
When placing a component with the orientation tee, you can adjust the orientation by pressing
<R> or selecting one of the Orientation Control commands.
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.
165
Creating 3D Models
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.
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.
166
Creating 3D Models
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.
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.
167
Creating 3D Models
168
SECTION 6
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.
169
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
13
unit_code
module_no
5
6
2
79
*
*
package_system_no
train_number
7
8
81
23
*
*
fluid_code
line_sequence_no
10
24
22
*
nominal_piping_dia
11
15
npd_units -1
16
piping_mater_class
12
25
insulation_purpose
insulation_thick
14
26
15
*
28
insulation_thick_units
insulation_density
-1
16
29
30
insulation_density_units
heat_tracing_reqmt
-1
17
31
73
heat_tracing_media
heat_tracing_temp
18
19
74
75
*
*
*
*
heat_tracing_temp_units
construction_stat
-1
20
76
60
hold_status
170
21
83
schedule_override
nor_oper_pres
23
24
66
39
*
*
nor_oper_temp
alt_oper_pres
25
26
41
43
*
*
alt_oper_temp
27
45
28
47
nor_dgn_temp
alt_dgn_pres
29
30
49
51
*
*
alt_dgn_temp
steam_outlet_temp
31
53
32
*
86
mater_of_construct
safety_class
33
34
61
59
*
*
design_resp
construction_resp
37
38
69
78
*
*
supply_resp
coating_reqmts
39
40
71
72
*
*
*
cleaning_reqmts
fluid_category
42
41
84
77
*
nor_op_pres_units
43
40
nor_op_temp_units
44
42
alt_op_pres_units
alt_op_temp_units
45
46
44
46
nor_dgn_pres_units
nor_dgn_temp_units
47
48
48
50
*
*
alt_dgn_pres_units
alt_dgn_temp_units
49
50
52
54
*
*
*
*
steam_temp_units
test_system_no
51
64
87
55
*
*
test_fluid
test_pressure
65
66
56
57
*
*
# upstrm_node_no
pid_node_number_a
# dwnstrm_node_no
10
pid_node_number_b
flow_direction
11
14
# line_no_label
line_number_label
21
# dwg_occ_no
drawing_segment_index_no
line_id
# piping_thk_flag
12
piping_thickness_flag
### Data extracted from the
Equipment Table
equipment_number
nozzle_number
( eq_group,
106
68
) of the P&ID Design Database:
7
( eq_nozz,
108
) of the P&ID
5
# pid_seg_occ_no
nozzle_segment_index
# eq_grp_occ_no
equipment_nozzle_index
# node_no
equip_nozzle_node_no
( piping_comp,
13
120
) of the P&ID
Design Database:
2
3
6
9
commodity_code_flag
28
171
29
27
# pid_seg_occ_no
comp_segment_index_no
# dwg_occ_no
comp_drawing_index_no
# generic_tag_no
specialty_generic_tag_no
#any attributes you desire to transfer
#
here.
44
(beyond those defined above) are listed
#attribute name
NOTE:
(any thing)
piping attr no
no
p&id attr
const_status
heat_tracing_media
32
23
heat_tracing_reqmts
hold_status
34
33
41
ht_tracing_media_temp
36
35
opening_action
remarks
31
46
17
20
35
34
33
( instr_comp,
131
instr_segment_index_no
# aabbcc_code
instr_aabbcc_code
10
# dwg_occ_no
instr_drawing_index_no
#generic_tag_no
instr_generic_tag_no
#any attributes you desire to transfer
3
80
#
#
here.
You determine which are transferred between P&ID instr_comp table
and piping pdtable_67.
NOTE:
Complete,
partial and default do NOT
#attribute name
cleaning_reqmts
(any thing)
const_resp 32
const_status
piping
39
attr
60
no
p&id attr no
35
29
24
dgn_resp 31
fail_action_1
28
56
heat_tracing_media
heat_tracing_reqmts
34
33
28
27
hold_status
ht_tracing_media_temp
30
35
40
29
insulation_purpose
36
31
insulation_thick
37
module_no 41
package_system_no
172
25
33
36
42
remark_2 52
safety_classification
40
the
38
22
20
Drawing
Table
( dwg,
#unit_occ_no
unit_index_number
drawing_title
network_address
16
7
path_name
file_specification
8
5
propagation_status
approval_initials
10
21
approval_date
22
revision_id
for_comments_date
27
29
for_design_date
for_construct_date
30
31
task_name
### Data extracted from
Unit Table
the
unit_number
unit_code unit_name
4
3
( task_rdb,
5
98
pid_task_name
pid_task_rdb_node
pid_task_rdb_path
### Data extracted from the PID Segment Table
Database:
# net_type_occ_no
( pid_seg,
4
110
piping_segment_index_no
4
### Data extracted from the PID Drawing Revision Data Table
###
103
4
unit, 101 ) of the P&ID Project Database:
( dwg_rev_data,
dwg_occ_no
2
(piping_connector,
124) of
#matching_criteria is the criteria to be used for matching the P&ID and Piping
#segments together.
Nodea
#are the default criteria.
68)
The default
#is
END which
FIRST
We
exclusion_criteria YES
173
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.
174
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.
175
176
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
177
178
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.
179
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.
180
181
182
SECTION 7
183
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
eCustomer login web page (https://crmweb.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, then click Finish.
184
185
186
187
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.
188
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.
189
For more information about mapping attributes, see Map an Unmapped Attribute (on page
191) or Map an Ignored Attribute (on page 191).
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.
190
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.
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.
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.
191
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.
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).
192
Value in Model
Value in P&ID
line_number_label
line_sequence_no
550111
550107
insulation_purpose
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.
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.
193
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.xls 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 numbers between 10 and 63 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.
194
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\Program 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
195
196
197
Troubleshooting
Some common difficulties that you may encounter are listed here, along with possible solutions.
198
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.
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.
199
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.
200
SECTION 8
201
202
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.
203
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.
204
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.
205
206
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.
207
208
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.
209
14
Date:
Model
PDS Interference
Report
23-Jun-93
Time:
13:42:13
mbpip2
210
48
2CPINSTRUMENT
meblabels-6IN-1C0031-0
Row
X Coord
Y Coord
Z Coord
4194305
E 1 3
Plant N
2000 0"
Plant
El 0 0" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0 0" Plant
4194306
E 8
N 2000 0"
Plant
El 0 0" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0 0" Plant
4194306
E 13 4 1/8"
Plant
N 2000 0"
Plant
El 0 0" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0 0" Plant
4194307
E 18 4 1/4"
Plant
N 2000 0"
Plant
El 0 0" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0 0" Plant
4194309
E 26 8 9/16"
Plant N
2000 0"
Plant
El 0 0" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0 0" Plant
4194305
E 30 2 3/16"
Plant N
2000 0"
Plant
El 0 0" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0 0" Plant
4194305
E 31 2 3/16"
Plant N
2000 6"
Plant
El -1 1
9/16" Plant
15/16"
"
Not approved
48
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
49
3CPINSTRUMENT
meblabels-6IN-1C0031-0
4" Plant
"
Not approved
49
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
50
2CPSPECIALTY
meblabels-6IN-1C0031-0
"
Not approved
50
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
51
3CPSPECIALTY
meblabels-6IN-1C0031-0
"
Not approved
51
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
52
T
meblabels-6IN-1C0031-0
"
Not approved
52
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
53
PIPE
meblabels-6IN-1C0031-0
"
Not approved
53
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
54
pipesupport
meblabels-6IN-1C0031-0
"
211
PIPE
ifcclash pipe-1IN-1C0031-0
4194308
E 40 2 3/16"
Plant N
1999 4"
Plant
El -6" Plant
4194306
E 40 2 3/16"
Plant N
1999 10"
Plant
El 0
Plant
0"
4194321
E 22 6 1/16"
Plant N
2000 0"
Plant
El 0
Plant
0"
"
Not approved
55
PIPE
ifcclash pipe-1IN-1C0031-0 "
Not approved
55
CKS
1construct-6IN-1C0031-0
"
Not approved
212
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
Interference Manager.
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 accessways, 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.
213
214
215
216
SECTION 9
217
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.
218
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:
219
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.
220
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)
221
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.
222
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.)
[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).
223
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.
224
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)
225
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.
226
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.
227
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.
228
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
Tubing Fittings
Steam Specialties
Socketwelded Fittings
Flanges
Threaded Fittings
Flanged Specialties
Underground Fittings
229
Strainers
Valves
Welded Fittings
Gaskets
Bolting
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.
230
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.
231
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.
232
233
: 15-Apr-93
Page: 1
Corporate Headquarters
PDS Project
tcproj
Intergraph Corporation
tc101
Huntsville,
Alabama
35894-0001
RoXXon Corp.
(205)730-2000
Commodity Code
Nth Projector
Qty/Length
1st Size
2nd Size
Material Description
234
1/2IN
1/2IN
PPCAAAOAAE
1/2IN
1/2IN
VAUHAHGAAA
1/2IN
1/2IN
POCAAAOAAE
3/4IN
3/4IN
TPAZVZZAAA
3/4IN
VAUHAHGAAA
3/4IN
3/4IN
38-PI-6
3/4IN
3/4IN
39-PI-9
3/4IN
3/4IN
8,
FAAABAWAAA
3IN
LINE NUMBER:
P403-3IN-1C003
1-N
3IN
XDAABZZQSG
3"
YZZZHZZFFF
5/8"
3/4"
8,
studs w/ASTM-A194-2H
4IN
LINE NUMBER:
P403-4IN-1C003
1-N
4IN
FAAABAWAAA
4IN
4IN
VAABAHCCAA
4IN
4IN
VBABAHCFAA
4IN
4IN
WAAAAAWAAA
4IN
4IN
90
WRBAAAWAAA
4IN
3IN
WTAAAAWAAA
4IN
4IN
*
Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD
bore
47
ANSI-B16.9
Date/Time
: 15-Apr-93
Commodity Code
1st Size
2nd Size
Page: 2
Material Description
LINE NUMBER:
P403-4IN-1C003
1-N
PAAAAAWAAA
9/16"
4IN
XDAABZZQSG
4"
YZZZHZZFFF
32
5/8"
supp2
4IN
FAAABAWAAA
11
6IN
LINE NUMBER:
P403-6IN-1C003
1-N
6IN
FGPBBAWAAA
6IN
6IN
B31, ASTM-A193-B7
hvy hex nuts
*
304
studs w/ASTM-A194-2H
235
6IN
6IN
VAABAHCCAA
6IN
6IN
47
VCABAHOBAA
6IN
6IN
WAAAAAWAAA
6IN
6IN
90
WADAAAWAAA
6IN
6IN
45
WOAAAAWAFA
6IN
4IN
WOBSABQAFA
6IN
3/4IN
WRAAAAWAAA
6IN
4IN
WTAAAAWAAA
PAAAAAWAAA
131
XDAABZZQSG
12
XDABBZZQSG
6IN
6"
304
6"
304
YZZZHZZFFF
80
3/4"
4"
YZZZHZZFFF
20
3/4"
5"
supp1
6IN
B31, ASTM-A193-B7
hvy hex nuts
B31, ASTM-A193-B7
hvy hex nuts
*
Qty/Length
1st Size
Date/Time
6IN
1
3/16"
6IN
: 15-Apr-93
Commodity Code
studs w/ASTM-A194-2H
studs w/ASTM-A194-2H
Page: 3
Material Description
LINE NUMBER:
P403-6IN-1C003
1-N
supp3
Date/Time
6IN
: 15-Apr-93
*
PDS MTO REPORT
Page: 4
GRAND TOTALS
Components Pipes
Instruments
Gaskets
Bolts
Pipe Supports
8719
18
136
236
lng
PIPING 1 2
PIPING 5001 2
6
6
301 301 -
PIPE
PIPE
237
212
Sequence=
Single_Spacing
!Comm Code
10
238
FAAABAWAAA
12
IMPFLG2A
1.5
FAAABAWAAA
12
IMPFLG2B
0.5
FAAABAWAAA
12
IMPFLG2C
1.0
VAABAHCCAA
IMPVAL2A
0.5
VAABAHCCAA
IMPVAL2B
2.5
PAAAAAWAAA
IMPPIP2 1.0
WAAAAAWAAA
IMPELB2 2.0
WRAAAAWAAA
12
10
IMPRED 1.0
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 Tablethe system uses the preferred bolt length table.
Bolt Roundoff Factorthe system rounds up the calculated length by the specified
factor.
No Roundoffthe 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.
239
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.
240
Processed Library
23
14:16:58
1992
/usr/newpipe/refdata/us_shbom.l
!Cmdty Code
====================================Description======================
CHAIN_1003
[400]
CHAIN_1005
[400]
CHAIN_1251
DAABAXAABE
Monitor, CL150
steel stem
FFFE,
DAABAXAABF
DACBAXABBC
Monitor, CL150
outlet, [427],
station type,
station type
4" CL150
4" CL150
in-let by
in-let by
[402]
FFFE,
4" CL150
in-let by
w/drain coupling, w/shapertip nozzle and two reaction supports, Stang BB2999-
DACBAXABBD
Monitor, CL300
outlet, [427],
FFFE,
6" CL300
in-let by
DBAAAXBAAB
FFFE,
2.5" hose
241
242
DCBGDXEADA
Hose rack,
300#, FTE,
DDAXCJDAAA
FAAAAAWAAA
FAAAAAWWAA
FAAABADIIA
FAAABADIIF
FAAABADNPF
FAAABAOAAA
FAAABAOABB
FAAABAOFFH
FAAABAWAAA
FAAABAWABB
FAAABAWFFH
[409]|bore to match|
FAAABAWFFL
[409]|bore to match|
FAAABAWGFD
[409]|bore to match|
FAAABAWIIA
[409]|bore to match|
FAAABAWIIF
[409]|bore to match|
FAAABAWNPF
FAAABBDAAA
FAAADAOAAA
FAAADAOFFC
FAAADAWAAA
FAAADAWFFC
125
Ra finish,
FAAADBDFFC
125
FAABBADIIA
FAABBADIIB
30-333
[409]|bore to match|
[409]|bore to match|
bore
bore
bore
[409]|bore to match|
[409]|bore to match|
125
125
[409]|bore to match|
Ra finish, S-160
125
bore
Ra finish, S-160
Ra finish,
bore
[409]|bore to match|
[409]|bore to match|
FAABBAOAAA
FAABBAOABB
bore
FAABBAOFFC
bore
FAABBAOFFH
FAABBAWAAA
FAABBAWABB
[409]|bore to match|
FAABBAWFFC
[409]|bore to match|
FAABBAWFFH
[409]|bore to match|
FAABBAWFFL
[409]|bore to match|
FAABBAWIIA
FAABBAWIIB
FAABBAWIIF
FAABBAWNPF
FAABBBDAAA
FAABDADIIJ
125
FAABDAOAAA
Ra finish, S-160
FAABDAOFFC
FAABDAWAAA
FAABDAWFFC
FAABDAWFFH
FAABDAWIIJ
FAADBADIIA
FAADBADIIF
FAADBAOAAA
FAADBAOABE
bore
bore
[409]|bore to match|
[409]|bore to match|
[409]|bore to match|
[409]|bore to match|
[409]|bore to match|
125
125
125
bore
Ra finish, S-160
Ra finish,
125
[409]|bore to match|
Ra finish,
125
Ra finish,
125
bore
Ra finish,
[409]|bore to match|
[409]|bore to match|
[409]|bore to match|
bore
bore
243
[409]|bore to match|
FAADBAWABE
FAADBAWFFC
FAADBAWFFH
[409]|bore to match|
FAADBAWFFL
[409]|bore to match|
FAADBAWIIA
[409]|bore to match|
[409]|bore to match|
[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
Component
425
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.
244
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
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
245
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.
246
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.
247
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.
248
249
250
SECTION 10
251
252
253
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.
254
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.
255
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.
256
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.
257
258
SECTION 11
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.
259
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
260
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.
261
# Drawing Data
table number
262
24
, dwg_index_no
, integer
, index
, drawing_no
, character(24)
, index
, drawing_title
, character(40)
, default_scale
, character(16)
, approval_initials
, character(4)
, approval_date
, integer
, approval_status
, short
, completion_status
, short
, drawing_size
, standard note 35
, short
10, drawing_type
, short
11, last_revision_no
, character(2)
12, drawing_file_spec
, character(14)
13, path_name
, character(36)
, index 3
, character(26)
15, lock_owner
, character(10)
16, lock_status
, short
17, lock_date
, integer
18, revision_date
, integer
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
24, standard_note_no_b
, short
16
, dwg_view_index_no
, integer
, index
, dwg_view_no
, character(6)
, index
, dwg_view_name
, character(40)
, dwg_view_scale
, character(16)
, dwg_index_no
, integer
, saved_view_name
, character(6)
, viewing_direction
, short
, composition_status
, dwg_view_x_low
, short
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
15, vhl_category_index
, double
, short
16, drawing_view_type
, short
, dwg_view_index_no
, integer
, model_index_no
, integer
15
, comp_dwg_index_no
, integer
, comp_dwg_view_no
, character(6)
, comp_dwg_view_name
, comp_dwg_v_scale
, character(16)
, dwg_index_no
, integer
, dwg_view_index_a
, integer
, dwg_view_index_b
, integer
, index
, character(40)
263
, dwg_view_index_c
, integer
, 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
, dwg_index_no
, integer
, revision_index_no
, short
, revision_no
, character(2)
, revision_date
, integer
, revision_by
, character(4)
, checked_by
, character(4)
, rev_description
, character(40)
, drawing_type
, short
, drawing_size
, short
, drawing_scale
, character(16)
, default_path_name
, character(36)
, default_node
, character(26)
, discipline_mask
, alternate_seed_opt
, short
, short
# Reference Model Display Category Setup Data
table number
, drawing_type
, short
, discipline_indx_no
, category_mask_a
, integer
, category_mask_b
, integer
, category_mask_c
, integer
, category_mask_d
, integer
, short
264
, iplot_index_no
, integer
, iplot_number
, character(24)
, iplot_description
, character(40)
, iplot_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
Select the option for the type of drawing data to be revised. The following report shows the
delivered settings for the Drawing Data.
Project Data Manager
Drawing Category
Data
Level
Drawing View Specific Labels
Coordinate Labels
Dimensioning
10
Hold Clouds
11
Reports
12
Battery Limits
36
Matchlines
37
Centerlines
38
Dumb Details
39
265
40
41
42
43
44
266
45
11
46
12
47
13
48
14
49
15
50
16
51
17
52
18
53
19
54
20
55
21
22
23
24
25
26
27
28
29
10
30
11
31
12
32
13
33
14
34
15
35
13
14
15
16
17
18
19
20
56
10
57
11
58
12
59
13
60
14
61
15
62
Colors
Revision Cloud
White
Flow Arrow
White
Report
White
Dimension
White
Miscellaneous
Violet
Name
FLOARR
50
Undefined,Undefined
0.500000
3
Project Data Manager
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"
Project Data Manager
Drawing Annotation
Line
Line
Category
Spacing
Weight
Symbology
0 Solid
Color
Text Size
Font
Factor
Battery Limits
White
1/4",
1/4"
0.0000
Matchlines
0 Solid
White
1/4",
1/4"
0.0000
Centerlines
0 Solid
White
1/4",
1/4"
0.0000
Dumb Details
0 Solid
White
1/4",
1/4"
0.0000
0 Solid
White
1/4",
1/4"
0.0000
Terminator
Text
267
0 Solid
White
1/4",
1/4"
0.0000
0 Solid
White
1/4",
1/4"
0.0000
0 Solid
White
1/4",
1/4"
0.0000
0 Solid
White
1/4",
1/4"
0.0000
Like Equipment No
Labels
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
User-defined drawing
annotation category
0 Solid
White
1/4",
1/4"
0.0000
11
0 Solid
White
1/4",
1/4"
0.0000
12
0 Solid
White
1/4",
1/4"
0.0000
13
0 Solid
White
1/4",
1/4"
0.0000
14
0 Solid
White
1/4",
1/4"
0.0000
15
0 Solid
White
1/4",
1/4"
0.0000
16
0 Solid
White
1/4",
1/4"
0.0000
17
0 Solid
White
1/4",
1/4"
0.0000
18
0 Solid
White
1/4",
1/4"
0.0000
19
0 Solid
White
1/4",
1/4"
0.0000
20
0 Solid
White
1/4",
1/4"
0.0000
Project Data
Manager
Drawing Hidden
Line Symbology
Use Default Weight
Use User Defined
Symbology
Use Default Color
LabelTypes
The following label types are used for annotation in drawings.
268
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.
269
270
271
272
Index
'
'*' Spec Implied Items 237
[
[Buffer] = Field Definition 223
[Rows/Page] 223
[Spacing] 223
'
'+' Table Implied Example 238
'+' Table Implied Items 238
2
2DSetup 22
3
3D Coordinate Systems 30
3D Seed Data 142
3D Setup 22
A
About Licensing 22
About the Reference Database (RDB) 146
Activating the Orientation Tee 154
Active Placement Point 163
Alphanumeric Labels 269
Analyze Data 167
ASCII to Binary Conversion 254
Attribute Types 48
B
Base Form 141
Batch Software Organization 255
Bend Deflection Table 126
Branch Insertion Tables 126
C
Cells 261
Choosing Data Transfer Options 193
Clash Categories 213
Clash Precedence 213
Client/Server Relationship 45
Code-Listed Attributes 48
Col 222
Commodity Code 112
Commodity Codes 229
Commodity Item Name Table 125
Common Tools on Forms 138
Component Manipulation Commands 155
Component Revision 166
Connect Point Data 90
Coordinate System Indicator and
Orientation Tee Coordinate System
Indicator 164
Create Label Attribute Data 246
Creating 3D Models 129
Creating and Maintaining Links 187
Creating Equipment Models 145
Creating Material Takeoffs and Other
Reports 217
Creating Orthographic Drawings 259
Creating Piping Models 156
D
Data_Type 222
Database Definition Files 49
Database Information 47
Database Overview 43
Database Requirements 169
Define Commands 155
Definitions 221
Delete Data 248
Delivered Reference Data 88
Design Area and Piping Design Area
Predefined Volume 205
Design Database 66
Design Review Integrator (PD_Review) 20
Design Volume Coordinate System 36
Detecting and Managing Interferences 201
Dialog Boxes 135
Diameter Table 107
Disable Display of P&ID Drawing Command
196
Discrimination Data File 218
Displayable Attribute Label 271
Displayable Attribute Labels 268
Displayable Attribute Message 269
Drawing Borders 261
Drawing Categories 261
Drawing Manager (PD_Draw) 16
Drawing Manager Database Table
Information 262
273
Index
Drawing Manager Features 260
Drawing Manager Setup 260
Drawing Plot Size Table 261
Drawing Seed Data 265
Drawing View Specific Labels 270
DVCS Oriented From Plant North 39
E
Edit Data 248
EE Raceway Modeling 19
Equipment Manipulation Commands 155
Equipment Model Seed Data 147
Equipment Modeling (PD_EQP) 13
Equipment Modeling Commands 155
Equipment Modeling Concepts 152
Equipment Modeling Environment 150
Establish a SmartPlant/PDS Link 189
Examples 38, 230
Extracting Isometric Drawings 251
H
Hard - Hard Example 214
Hard - Soft Example 214
How PDS Works 103
274
Index
Modeling Setup Requirements 129
Modifier 112
N
Name From P&ID 180
Name from P&ID Option 196
Named Component Existence Report
Command 197
Nozzle Manipulation 155
O
Option Code 111
Optional Report Type Line 224
Orientation Tee 164
Output Fields 224
Overview of Isometric Extraction 253
P
P&ID Correlation Table 170
P&ID Data 180
P&ID Data Comparison Options 181
P&ID Drawing Display Categories
Command 196
P&ID Graphical Data Transfer Setup 174
P&ID Node Numbers 176
Palettes 135
Parametric Shape Definitions 120
PDS 3D Databases 46
PDS and the Relational Interface System
(RIS) 43
PDS Isometric Interface (PD_ISO,
PD_ISOGEN) 18
PDS P&ID to Piping Data Transfer 169
PDS Stress Analysis Interface (PD_Stress)
17
PDS System Configurations 45
Physical Data 121
Physical Data Definitions 116
Piping Assembly Library 102
Piping Commodity Data 110
Piping Commodity Implied Material Data
96
Piping Commodity Size-Dependent Material
Data 95
Piping Commodity Specification Data 90
Piping Connect Points 165
Piping Design Area and Design Area 204
Piping Design Commands 166
Piping Design Graphics (PD_Design) 15
Piping Job Specification 89
Piping Materials Class Code 105
R
Reasoning 29
Recommended Working Units - English 28
Recommended Working Units - Metric 29
Reference Data 87
Reference Data Manager (PD_Data) 16
Reference Data Setup 130
Reference Database 82
Report Format File 220
Report Manager (PD_Report) 18
Report Output 219, 232
Report Record 219
Report Types 220
Reporting Process 217
Restore View of Piping Model Command
196
Review Data 167
Review P&ID Drawing Details Command
196
Review/Revise Commands 155
Revise Data 167
Revising Linked Models 190
Revision Commands 166
Row 222
S
Sample Format Files 224
Sample Interference Report Format File
227
275
Index
Sample MTO Format (piping_g.fmt) 233
Sample MTO Output 234
Sample MTO Report Format Files 224
Sample P&ID Consistency Check Report
Format File 227
Sample Project Control Report Format Files
226
Sample Spec Report Format Files 226
Secondary Commands 155
Seed Files 130
Segment Data Comparison Report 192
Segment Vertex Commands 167
Select P&ID by Line ID Command 196
Select P&ID Drawing by Nozzle Command
196
Selecting Options 138
Setting Up a System to Support
Interference Detection 207
Single/Dual Ownership of Clashes 206
SmartPlant P&ID to PDS Piping Data
Transfer 183
Spec Access 105
Specific Physical Data Modules 117
Specific Tables 123
Standard Note Library 101
Sub-Symbol Processor 116
Symbol Processors 115
System Setup 21
V
View Windows 136
Volume Filter 205
W
Weight code 113
What are the 2D modules? 12
What are the 3D modules? 13
What Happens When I Place a
Component? 103
What Happens When I Report On a
Component? 227
What is the Plant Design System? 11
Working in Three Dimensions 24
Working Units 27
Working with the Graphical User Interface
133
T
Table Access 113
Tap Properties Data 94
Temperature Pressure Table 106
Test the SmartPlant Connection 186
The Batch Job Input File 255
The Intergraph Interface to ISOGEN 254
The ISOGEN Interface 257
Thickness Equations 109
Thickness Table 108
Transfer by Equipment Number and Nozzle
Number 178
Transferring Piping Data 183
Troubleshooting 198
U
Understanding Design Areas and Volumes
203
Understanding Implied Items 236
Understanding Interference Checking 209
Understanding Interference Envelopes
208
Understanding Interference Plotting 215
276