Professional Documents
Culture Documents
3D Theory
February 2009
DPDS3-PB-200010E
Copyright
Copyright 1984-2009 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 and Limited Product Warranty ("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 ............................................................................................................................................... vii
What is the Plant Design System? ............................................................................................................. 1
What are the 2D modules? ..................................................................................................................... 2
Process Flow Diagram (PFD) .......................................................................................................... 2
Process & Instrumentation Diagram (P&ID) .................................................................................. 3
Instruments and Instrument Loops .................................................................................................. 3
What are the 3D modules? ..................................................................................................................... 4
Equipment Modeling (PD_EQP) ..................................................................................................... 4
FrameWorks Plus (FWP)................................................................................................................. 4
Piping Design Graphics (PD_Design) ............................................................................................. 5
Reference Data Manager (PD_Data) ............................................................................................... 6
Drawing Manager (PD_Draw) ........................................................................................................ 7
PDS Stress Analysis Interface (PD_Stress) ..................................................................................... 7
Interference Checker/Manager (PD_Clash)..................................................................................... 8
PDS Isometric Interface (PD_ISO, PD_ISOGEN) .......................................................................... 9
Report Manager (PD_Report)........................................................................................................ 10
Project Engineer HVAC (PE-HVAC) ........................................................................................... 10
EE Raceway Modeling .................................................................................................................. 11
Design Review Integrator (PD_Review) ....................................................................................... 11
Project Setup ........................................................................................................................................ 12
System Setup ................................................................................................................................. 12
2DSetup ......................................................................................................................................... 13
3D Setup ........................................................................................................................................ 14
About licensing .............................................................................................................................. 14
Project Organization............................................................................................................................. 15
Working in Three Dimensions ............................................................................................................. 16
Working Units ............................................................................................................................... 19
Recommended Working Units - English ....................................................................................... 20
Recommended Working Units - Metric ........................................................................................ 21
Reasoning ...................................................................................................................................... 22
3D Coordinate Systems ................................................................................................................. 22
Plant Coordinate System ............................................................................................................... 23
Design Volume Coordinate System............................................................................................... 28
Examples ....................................................................................................................................... 30
Database Overview ................................................................................................................................... 35
PDS and the Relational Interface System (RIS) ................................................................................... 36
PDS System Configurations ................................................................................................................. 37
Client/Server Relationship ............................................................................................................. 38
PDS 3D Databases ............................................................................................................................... 39
Database Information .................................................................................................................... 40
iii
vi
Preface PDS
This document provides command reference information and procedural instructions for the
Plant Design System 3D Theory Guide task.
vii
Preface PDS
viii
SECTION 1
In This Section
What are the 2D modules? ............................................................. 2
What are the 3D modules? ............................................................. 3
Project Setup .................................................................................. 12
Project Organization ...................................................................... 14
Working in Three Dimensions....................................................... 16
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
through either distributive control systems (DCS), programmable logic controllers (PLC), or
stand-alone controller philosophy.
When doing propagation (taking graphic information from the drawing and writing it to the
database), the drawing is checked for conformance to design rules and the drawing information
is loaded into a relational database.
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.
Within PD_EQP, designers can create a physical envelope defining the space occupied by an
equipment item along with space envelopes defining maintenance and access areas. This process
is instrumental for interference checking later in the modeling process.
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
Plant Design System 3D Theory
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.
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.
PDS Isometric Interface (PD_ISO, PD_ISOGEN) allows designers to extract isometric drawings
from the plant model, either interactively or through a batch process. The interactive extraction
can be used for testing the interface and verifying a specific pipeline. Batch generation of
isometrics is used for generating production drawings on a project. With either function, a bill of
materials is automatically generated and attached to the isometric drawing. An optional MTO
file can be generated which can be printed or used as input to a material control system.
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.
Material take-off reports (MTOs) can be generated on piping and equipment models through
PD_Report. The MTO process generates reports by using the graphical data in the specified
models to refer to the Design Database, Reference Database, Project Database, and Material
Description Libraries for the data on which to report. This data includes implied materials, such
as bolts, gaskets, and welds, that are not represented in the model but are necessary for the
specified connectivity.
The Report Manager also maintains the data that defines the format, content, and approval status
of the reports.
10
EE Raceway Modeling
11
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:
12
Design data, such as temperature and pressure values associated with graphic elements.
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.
The pr ojcr eate 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.
13
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 either loaded on the workstation using the client option or
installed locally.
A 3D project uses three database schemas:
A material/reference database,
A design database.
The 2D and 3D project share a common project control database. The Pr oject Administr ator is
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.
14
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
Plant Design System 3D Theory
15
Drawings are produced from the model. Although drawings can be created at different scales,
they all reference the actual model graphics to avoid discrepancies with the model.
Each model represents a unique partition of the design database. This enables you to access all
the data for a single model (independently of the other project data) for the purpose of creating
or modifying information. However, you can also perform interference checking and create
reports based on the combined data from all the models in a project.
The Project Administrator module controls the creation and modification of the PDS 3D
projects. Each project consists of a project control database, design database, piping and
equipment models, reference models (structural, HVAC, and raceway), a set of drawings, and a
collection of reference data. The reference data may be specific to one project or shared by more
than one project.
16
All graphic elements must be placed in the design cube. The design cube is a volume of threedimensional 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.
17
Notice that the isometric view (also called the rotated view) shows the design cube from an
apparent angle of 30. Actually, the view is rotated 45 in two directions: the cube is displayed
from the top front right.
18
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.
19
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.
20
File
MU
SU
PU
Area
1 FT
12 IN
2032
176138 FT
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
21
Reasoning
The recommended PDS settings for English working units results in 24,384 UORs per foot
(1x12x2032). Dividing this number into the available UORs in the design file yields an area of
coverage of 176,138.75 feet or 33.3 miles.
Working units establish the scale of the data. The actual SU and PU values do not matter as long
as the total UORs per master unit are the same. Therefore the English units can be converted to
metric units to create compatible models.
Dividing the total UORs per foot by the metric conversion factor provides the UORs per meter.
This value was used to assign the metric values 1:1000:80. Therefore, the values of 1:12:2032
for English units and 1:1000:80 for metric units are compatible.
The recommended English (2032) and metric (80) values allow a file created using the English
system to be viewed and edited in metric mode without scaling or altering data. The positional
units for drawings should be defined so that the drawing has the same
resolution as the model. To maintain the same resolution, the smallest drawing view scale is used
so that the PUs of the drawing file are no less than the maximum factor times the PUs used in the
model.
For English units, the smallest drawing view scale for the delivered drawing seed files is 1/8" =
1' (12"). This yields a factor of 96 to be applied to the model units to determine the drawing
units.
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.
22
23
As previously mentioned, the default working units yield an area of coverage of 176,138.75
(33.3 miles, or 53.58 Kilometers). Since the plant monument is always in the center of the design
cube, you can divide 176,135.75 by 2 to determine the extents of the Plant Coordinate System.
The maximum Easting, Northing, and Westing, Southing, Up, or Down coordinate is 88,069 4.5"
Entering the Easting value of -5000 is the same as entering Westing 5000; Northing 20,000 is the same as Southing 20,000.
Do not modify the MicroStation Global Origin for piping or equipment seed files or
models. In general, this is also not necessary for other disciplines seed or design files. Only if it
appears that there will not be enough design plane to contain all graphics (such as may be the
case for large material-conveying systems spanning several miles) should you even consider a
global origin change. It would always be a good idea to consult a PDS Support contact before
making such a change.
If only positive Easting, Northing, and Westing values are entered, and the default plant
monument values were accepted, you are restricted to using only half of the available design
volume. To work within the contraints of positive Easting and Northing values and still use the
24
With these settings, the Plant Coordinate System would be defined as follows:
25
26
27
28
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 Pr oject Data Manager .
The system uses the global coordinate system to maintain the relationship among the various
reference models attached to the working model.
Plant Design System 3D Theory
29
Examples
The following examples show various ways of modifying the Plant Coordinate System or
Design Volume Coordinate System for various working conditions
30
31
Note that, in the example, a unique design volume coordinate system has been defined for
each model.
While placing components in Building 1, the user might prefer to enter values relative to the SW
corner of the building, rather than entering the large values associated with the Plant Coordinate
system. To do this, the project administrator should create a model with a Design Volume
Monument located at the SW corner. In Plant Coordinate System, this coordinate would be
Easting -60,000 (Westing 60,000), Northing -75,000 (Southing 75,000), and Elevation 0. In the
Design Volume coordinate system, the location should be Easting 0, Northing 0, and Elevation
0.
When a Design Volume Coordinate System has been defined, the user has the choice of viewing
and entering coordinates using the Design Volume Coordinate System or the Plant Coordinate
System.
This capability becomes even more valuable when placing components in buildings such as
Building 2 and Building 3, which are rotated with respect to Plant North. Review the coordinates
for these buildings in the next three screen images.
Building 1
32
Building 2
Notice that the design volume is ROTATED 330 DEGREES with respect to the PCS.
33
Notice that the design volume is ROTATED 30 DEGREES with respect to the PCS.
34
SECTION 2
Database Overview
PDS uses relational databases to store information about virtually all aspects of the project
including:
Design data, such as temperature and pressure values associated with graphic elements.
35
Database Overview
In This Section
PDS and the Relational Interface System (RIS) ............................ 36
PDS System Configurations .......................................................... 37
PDS 3D Databases ......................................................................... 39
Database Definition Files .............................................................. 41
36
Database Overview
3D RIS Overview
2D RIS Overview
The Intergraph product numbers for the relational database products and the corresponding RIS
products are documented in the latest 'workstation newsletter'. All ISS products (nucleus
software) should also be up to date and compatible.
37
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 three categories:
Database Server
This is the location of the Relational Databases. All databases will be created and stored on
this machine.
Software Server
This is the location of the PDS application products. By using a software server, you can
load all of the PDS software in a central location and have individual workstations access the
software through the network.
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.
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.
38
Database Overview
PDS 3D Databases
A 3D project uses three database schemas as outlined in the following illustration.
The Pr oject Administr ator is 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
39
Database Overview
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.
Attrib u te Typ e s
The following conventions are used to designate the field type for database attributes.
character(n)
integer
short
short integer
double
Co d e -Lis te d Attrib u te s
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)
indicates that fluid_code is defined in terms of code list numbers belonging to Standard Note
125, Fluid Code/Connector Type. A possible entry for this attribute would be 197 for chlorine
gas (GCL).
CL125, Fluid Code/Connector Type (999)
1 = [Blank]
11 = A
[Air]
14 = AC
[Combustion air]
17 = AE
[Aeration air]
20 = AI
[Instrument air]
:
:
40
Database Overview
191 = G
194 = GCD
[Gas]
[Carbon dioxide gas]
197 = GCL
[Chlorine gas]
198 = GCN
[Chlorination gas]
200 = GF
[Fuel gas]
203 = GG
[Flue gas]
206 = GH
[Hydrogen gas]
209 = GHS
table number
101
, number of columns
, system_unique_no
, integer
, project_no
, character(15)
, project_name
, character(40)
, job_no
, character(40)
, company_name
, character(40)
, plant_name
, character(40)
, site_id
, character(10)
table number
, type_of_rdb_data
, short
, approval_status
, short
, rdb_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, lock_owner
, character(10)
, lock_status
, short
, lock_date
, integer
, revision_date
, integer
table number
103
, number of columns
41
41
Database Overview
1
, product_version_no
, short
, report_path
, character(36)
, report_node
, character(26)
, report_format_path
, character(36)
, report_format_node
, character(26)
, report_filter_path
, character(36)
, report_filter_node
, character(26)
, piping_eden_path
, character(36)
, piping_eden_node
, character(26)
10, eden_table_path
, character(36)
11, eden_table_node
, character(26)
12, piping_spec_path
, character(36)
13, piping_spec_node
, character(26)
14, assembly_path
, character(36)
15, assembly_node
, character(26)
16, model_builder_path
, character(36)
17, model_builder_node
, character(26)
18, design_review_path
, character(36)
19, design_review_node
, character(26)
20, std_note_lib_path
, character(36)
21, std_note_lib_node
, character(26)
22, eqp_eden_path
, character(36)
23, eqp_eden_node
, character(26)
24, tdf_table_path
, character(36)
25, tdf_table_node
, character(26)
26, clash_report_path
, character(36)
27, clash_report_node
, character(26)
28, clash_plot_path
, character(36)
29, clash_plot_node
, character(26)
30, mdl_status_low_dr
, short
31, mdl_status_high_dr
, short
32, mdl_status_low_ic
33, mdl_status_high_ic
, short
, short
34, area_owner_opt_ic
, short
35, eqp_insul_opt_ic
, short
36, eqp_con_tol_opt_ic
, short
37, clash_rpt_index_no
, integer
38, report_search_path
, character(36)
39, report_search_node
, character(26)
40, sup_tdf_table_path
, character(36)
41, sup_tdf_table_node
, character(26)
, standard note
1605
, standard note
1605
, standard note
1605
, standard note
1605
42
Database Overview
table number
11
, archival_index_no
, integer
, archival_number
, character(24)
, archival_descript
, character(40)
, archival_file_spec
, path_name
, character(36)
, network_address
, character(26)
, month_map
, integer
, day_of_week_map
, integer
, character(14)
, day_map
, integer
10, time_of_day
, integer
11, schedule_type
, short
13
, site_id
, character(10)
, site_description
, character(40)
, min_model_range
, integer
, max_model_range
, integer
, min_dwg_range
, integer
, max_dwg_range
, integer
, min_dwg_view_range
, integer
, max_dwg_view_range
, integer
, min_pip_partition
, integer
10, max_pip_partition
, integer
11, min_eqp_partition
, integer
12, max_eqp_partition
, integer
13, master_flag
, short
111
, number of columns
, discipline_indx_no
, discipline_name
, intra_disc_ifc_flg
, discipline_mtrx_a, integer
, discipline_mtrx_b, integer
, short
, character(20)
, short
112
, number of columns
15
, discipline_indx_no
, short
, area_index_no
, short
, area_name
, character(10)
, area_description
, character(40)
, volume_low_x
, integer
43
Database Overview
6
, volume_low_y
, integer
, volume_low_z
, integer
, volume_high_x
, integer
, volume_high_y
, integer
10, volume_high_z
, integer
11, interference_mode
, short
12, area_lock_owner
, character(10)
13, area_lock_status
, short
14, area_lock_date
, integer
15, clash_rpt_index_no
, integer
# Model Data
table number
113
, number of columns
17
, model_index_no
, discipline_indx_no
, integer
, area_index_no
, short
, partition_no
, short
, model_no
, character(10)
, model_description
, character(40)
, model_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, index
, short
10, lock_owner
, character(10)
11, lock_status
, short
12, lock_date
, integer
13, verification_date
, integer
14, revision_date
, integer
15, responsible_disc
, short
16, model_type
, short
17, model_status
, short
, standard note
1605
114
, number of columns
, partition_no
, short
, max_segment_number
, max_piping_number
, integer
, max_pipe_number
, integer
, max_instr_number
, integer
, max_support_number
, integer
, integer
306
115
, number of columns
, discipline_indx_no
44
, short
Database Overview
2
, default_path_name
, character(36)
, default_node
, character(26)
, ref_mdl_symbology
, short
, symbology_display
, short
, sub_project_ndx_no
, short
, sub_project_no
, character(15)
, sub_project_name
, character(40)
, sub_project_path
, character(36)
, sub_project_node
, character(26)
, sub_project_mount
, character(50)
, area_index_no
, sub_project_ndx_no
2
, short
, short
, inspection_iso_id
, inspection_status
, max_inspection_key
3
, character(24)
, short
, short
, model_index_no
, integer
, site_id
, character(10)
, index
34
, 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
10, drawing_type
index
, standard note
35
, short
, standard note
1202
, short
, standard note
2000 ,
11, last_revision_no
, character(2)
12, drawing_file_spec
, character(14)
45
Database Overview
13, path_name
, character(36)
14, network_address
, 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
, standard note
499
24, standard_note_no_b
, short
, standard note
499
25, custom_1
, character(40)
26, custom_2
, character(40)
27, custom_3
, character(16)
28, custom_4
, character(16)
29, custom_5
, character(16)
30, custom_6
, character(16)
31, custom_7
, character(16)
32, custom_8
, character(16)
33, custom_9
, integer
34, custom_10
, integer
16
, dwg_view_index_no
, integer
, index
, dwg_view_no
, character(24)
, index
, dwg_view_name
, character(40)
, dwg_view_scale
, character(16)
, dwg_index_no
, integer
, saved_view_name
, character(6)
, viewing_direction
, composition_status
, dwg_view_x_low
, short
, short
1620 optional
, standard note
1630
, double
10, dwg_view_y_low
, double
11, dwg_view_z_low
, double
12, dwg_view_x_high
, double
13, dwg_view_y_high
, double
14, dwg_view_z_high
, double
15, vhl_category_index
, standard note
, short
16, drawing_view_type
, short
46
Database Overview
1
, dwg_view_index_no
, integer
, model_index_no
, integer
15
, comp_dwg_index_no
, integer
, comp_dwg_view_no
, character(24)
, comp_dwg_view_name
, comp_dwg_v_scale
, character(16)
, dwg_index_no
, integer
, dwg_view_index_a
, integer
, dwg_view_index_b
, integer
, dwg_view_index_c
, integer
, dwg_view_index_d
, integer
, index
, character(40)
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
16
, 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)
, appr_by_1
, character(4)
, appr_by_2
, character(4)
10, appr_by_3
, character(4)
11, appr_by_4
, character(4)
12, appr_by_1_date
, integer
13, appr_by_2_date
, integer
14, appr_by_3_date
, integer
15, appr_by_4_date
, integer
16, checked_date
, integer
26
, drawing_type
, short
, standard note
2000
, drawing_size
, short
, standard note
1202
, drawing_scale
, character(16)
47
Database Overview
4
, default_path_name
, character(36)
, default_node
, character(26)
, discipline_mask
, short
, alternate_seed_opt
, cell_file_spec
, character(14)
, cell_path_name
, character(36)
, short
10, cell_net_address
, character(26)
11, plot_catgy_mask_a
, integer
12, plot_catgy_mask_b
, integer
13, label_mask_a
, integer
14, label_mask_b
, integer
15, label_mask_c
, integer
16, label_mask_d
, integer
17, custom_1
, character(40)
18, custom_2
, character(40)
19, custom_3
, character(16)
20, custom_4
, character(16)
21, custom_5
, character(16)
22, custom_6
, character(16)
23, custom_7
, character(16)
24, custom_8
, character(16)
25, custom_9
, integer
26, custom_10
, integer
12
, drawing_type
, short
, discipline_indx_no
, category_mask_a
, integer
, category_mask_b
, integer
, category_mask_c
, integer
, category_mask_d
, integer
, vhl_category_msk_a
, integer
, vhl_category_msk_b
, integer
, vhl_category_msk_c
, integer
10, vhl_category_msk_d
, standard note
2000
, short
, integer
11, vhl_ref_symbology
, short
12, vhl_symbology
, short
, iplot_index_no
, integer
, iplot_number
, character(24)
, iplot_description
, character(40)
48
Database Overview
4
, iplot_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, dwg_index_no
, integer
, site_id
, character(10)
, index
, index
15
, system_unique_no
, integer
, discipline_indx_no
, area_index_no
, unique_sequence_no
, completion_date
, integer
, control_user_no
, short
, env_creation_date
, integer
, clash_check_option
, volume_filter_opt
, short
, short
, integer
, short
, short
10, volume_low_x
, integer
11, volume_low_y
, integer
12, volume_low_z
, integer
13, volume_high_x
, integer
14, volume_high_y
, integer
15, volume_high_z
, integer
, standard note
1208
, standard note
1209
16
, unique_clash_id
, integer
, if_approval_status
, comp_a_unique_id
, integer
, comp_b_unique_id
, integer
, model_index_no_a
, integer
, model_index_no_b
, integer
, discipline_index_a
, short
, discipline_index_b
, short
, recent_clash_type
, short
, short
10, recent_plot_date
, index
, standard note
1203
, standard note
1204
, integer
11, recent_review_date
, integer
12, recent_sequence_no
, integer
, index
13, area_index_no
, short
14, action_discipline
, short
15, recent_seq_no_b
, integer
49
Database Overview
16, area_index_no_b
, short
, system_unique_no
, unique_clash_id
, unique_sequence_no
4
5
17
, integer
, index
, integer
, index
, clash_type
, short
, standard note
1204
, comp_a_range_x_lo
, integer
, comp_a_range_y_lo
, integer
, comp_a_range_z_lo
, integer
, comp_a_range_x_hi
, integer
, comp_a_range_y_hi
, integer
1204
, integer
10, comp_a_range_z_hi
, integer
11, comp_b_range_x_lo
, integer
12, comp_b_range_y_lo
, integer
13, comp_b_range_z_lo
, integer
14, comp_b_range_x_hi
, integer
15, comp_b_range_y_hi
, integer
16, comp_b_range_z_hi
, integer
17, env_pair_type
, short
, standard note
, index
, unique_comp_id
, integer
, comp_table_number
, short
, comp_row_number
, integer
, model_index_no
, integer
, primary_descript
, character(20)
, secondary_descript
, comp_model_status
, character(40)
, short
, system_unique_no
, integer
, index
, unique_clash_id
, integer
, index
, review_date
, integer
, review_user_no
, short
, responsib_user_no
, short
, action
, short
, review_comment
, character(100)
, approval_method
, standard note
1205
, short
, standard note
1207
, integer
, index
, system_unique_no
50
4
1
Database Overview
2
, unique_clash_id
, integer
, plot_date
, integer
, plot_user_no
, short
# Report Data
table number
20
, report_index_no
, integer
, index
, report_no
, character(24)
, index
, report_title
, character(40)
, approval_initials
, character(4)
, approval_date
, integer
, approval_status
, short
, last_revision_no
, character(2)
, report_file_spec
, character(14)
, path_name
, character(36)
, standard note
35
10, network_address
, character(26)
11, lock_owner
, character(10)
12, lock_status
, short
13, lock_date
, integer
14, revision_date
, integer
15, format_index_no
, integer
16, filter_index_no
, integer
17, last_rev_index_no
, short
18, report_source
, short
, standard note
1310
19, report_type
, short
, standard note
1312
20, search_index_no
, integer
11
, format_index_no
, integer
, format_number
, character(24)
, format_description
, format_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, lock_owner
, character(10)
, lock_status
, short
, index
, character(40)
, lock_date
, integer
10, revision_date
, integer
11, rpt_format_source
, short
, standard note
, integer
, index
1310
, filter_index_no
11
1
51
Database Overview
2
, filter_number
, character(24)
, filter_description
, filter_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, lock_owner
, character(10)
, lock_status
, short
, lock_date
, integer
10, revision_date
, integer
11, rpt_filter_source
, short
, character(40)
, standard note
1310
, report_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)
11
, search_index_no
, integer
, search_number
, character(24)
, search_description
, search_file_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, lock_owner
, character(10)
, lock_status
, short
, lock_date
, integer
10, revision_date
, integer
11, rpt_search_source
, short
, standard note
, index
, index
, character(40)
1310
table number
25
, review_index_no
, integer
, review_no
, character(24)
, review_title
, character(40)
, review_type
, short
, control_file_spec
, character(14)
, control_path_name
, character(36)
, control_node
, character(26)
, control_lock_owner
52
, standard note
1410
, character(10)
Database Overview
9
, control_lock_stat
, short
10, control_lock_date
, integer
11, tag_file_spec
, character(14)
12, tag_path_name
, character(36)
13, tag_node
, character(26)
14, tag_lock_owner
, character(10)
15, tag_lock_status
, short
16, tag_lock_date
, integer
17, session_rev_date
, integer
18, label_rev_date
, integer
19, label_file_spec
, character(14)
20, label_path_name
, character(36)
21, label_net_address
, character(26)
22, month_map
, integer
23, day_of_week_map
, integer
24, day_map
, integer
25, time_of_day
, integer
Package Data
table number
, package_index_no
, integer
, package_no
, character(24)
, package_title
, character(40)
, release_revision
, character(2)
, release_date
, integer
, index
Document Data
table number
, document_index_no
, integer
, package_index_no
, integer
, document_source
, short
, standard note
1710
, document_type
, short
, standard note
1720
16
, 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)
53
Database Overview
10, support_lineid
, character(40)
11, material_index
, character(20)
, integer
14, drawing_status
, short
15, sheet_no
, short
16, sheet_total
table number
, short
1, weld_id
11
, character(80)
2, weld_id_data
, character(40)
3, last_modified_date
, integer
, isofile_indx_no
, integer
, isodflt_indx_no
, integer
, isofile_type
, short
, isofile_spec
, character(14)
, path_name
, character(36)
, network_address
, character(26)
, iso_description
, character(40)
, lock_owner
, character(10)
, lock_status
, short
10, lock_date
, integer
11, revision_date
, integer
12
, isoproj_indx_no
, integer
, isoproj_task_opt
, short
, isoproj_name_opt
, short
, isoproj_dwg_opt
, short
, isodflt_indx_no
, integer
, reserved_1
, character(26)
, reserved_2
, character(36)
, reserved_3
, character(20)
, batch_options
, character(20)
10, isoproj_name_label
, index
, short
11, isoproj_dwg_label
, short
12, sub_directory_opt
, short
, isodflt_indx_no
54
4
, integer
Database Overview
2
, isodflt_tag
, character(12)
, isodflt_descr
, character(40)
, isodflt_rev_date
, integer
, index
, index
32
, iso_area_indx_no
, integer
, area_indx_no1
, short
, area_indx_no2
, short
, area_indx_no3
, short
, area_indx_no4
, short
, area_indx_no5
, short
, area_indx_no6
, short
, selection_mode
, short
, iso_area_name
, character(10)
10, iso_area_desc
, character(40)
11, user_data_indx_no
, integer
12, isodflt_indx_no
, integer
13, cont_indx_no1
, short
14, cont_indx_no2
, short
15, cont_indx_no3
, short
16, cont_indx_no4
, short
17, cont_indx_no5
, short
18, cont_indx_no6
, short
19, cont_indx_no7
, short
20, cont_indx_no8
, short
21, cont_indx_no9
, short
22, cont_indx_no10
, short
23, cont_indx_no11
, short
24, cont_indx_no12
, short
25, cont_indx_no13
, short
26, cont_indx_no14
, short
27, cont_indx_no15
, short
28, cont_indx_no16
, short
29, cont_indx_no17
, short
30, cont_indx_no18
, short
31, cont_indx_no19
, short
32, cont_indx_no20
, short
12
, user_data_indx_no
, integer
, type_of_user_data
, short
, user_data_1
, character(40)
55
Database Overview
4
, user_data_2
, character(40)
, user_data_3
, character(40)
, user_data_4
, character(40)
, user_data_5
, character(40)
, user_data_6
, character(40)
, user_data_7
, character(40)
10, user_data_8
, character(40)
11, user_data_9
, character(40)
12, user_data_10
, character(40)
185
, number of columns
19
, drawing_indx_no
, integer
, iso_area_indx_no
, integer
, index
, lineid_1
, character(24)
, index
, lineid_2
, character(24)
, lineid_3
, number_of_sections
, drawing_number
, character(24)
, batch_ref_no
, character(12)
, iso_dgn_name
, character(24)
, index
, character(24)
, short
10, model_status_code
, character(2)
11, model_revised_date
, integer
, short
14, no_sheets_extract
, short
15, last_mto_date
, integer
16, mto_to_mtl_control
, integer
17, no_of_revisions
, short
18, user_data_indx_no
, integer
19, iso_type
, short
186
, number of columns
12
, draw_rev_indx_no
, integer
, draw_sht_indx_no
, integer
, index
, type_of_revision
, short
, index
, revision_number
, short
, index
, generated_by
, character(3)
, checked_by
, character(3)
, approved_by
, character(3)
, extraction_date
, integer
, extraction_no
, short
10, sheets_extracted
, short
56
Database Overview
11, rev_description
, character(60)
12, isodflt_indx_no
, integer
187
, number of columns
, table_no
, integer
, last_used
, integer
188
, number of columns
, sheet_indx_no
, integer
, drawing_indx_no
, integer
, index
, sheet_no
, integer
, index
, last_extract_date
, integer
, tot_no_extractions
, last_mto_date
, integer
, no_of_revisions
, integer
, integer
189
, number of columns
, drawing_indx_no
, integer
, index
, section_no
, short
, index
, start_traversal_x
, integer
, start_traversal_y
, integer
, start_traversal_z
, integer
, start_entity
, short
, start_comp_occ
, integer
, start_seg_occ
, integer
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.
# Piping Segment Data
table number
12
, number of columns
79
1 , system_unique_no
, integer
2 , line_number_label
, character(40)
3 , line_id
, character(24)
4 , unit_number
, character(12)
5 , unit_code
, character(3)
6 , module_no
, character(16)
, index
57
Database Overview
7 , package_system_no
, character(12)
8 , train_number
, character(2)
9 , fluid_code
, short
10
, line_sequence_no
, character(16)
11
, nominal_piping_dia
, short
12
, piping_mater_class
, character(16)
13
, gasket_separation
14
, insulation_purpose
15
, insulation_thick
16
, insulation_density
, double
17
, heat_tracing_reqmt
18
, heat_tracing_media
19
, heat_tracing_temp
, double
20
, construction_stat
21
, standard note
125
, standard note
220
, standard note
(units)
, standard note
1074
, short
, short
, standard note
210
, short
, standard note
130
, hold_status
, short
, standard note
50
22
, approval_status
, short
, standard note
35
23
, schedule_override
, character(8)
, standard note
332
24
, nor_oper_pres
, double
25
, nor_oper_temp
, double
26
, alt_oper_pres
, double
27
, alt_oper_temp
, double
28
, nor_dgn_pres
, double
29
, nor_dgn_temp
, double
30
, alt_dgn_pres
, double
31
, alt_dgn_temp
, double
32
, steam_outlet_temp
33
, mater_of_construct
34
, safety_class
, short
, standard note
340
35
, design_standard
, short
, standard note
570
36
, design_area_number
37
, design_resp
, short
, standard note
160
38
, construction_resp
, short
, standard note
160
39
, supply_resp
, short
, standard note
160
40
, coating_reqmts
, short
, standard note
190
41
, cleaning_reqmts
, short
, standard note
230
42
, fluid_category
, character(4)
43
, nor_op_pres_units
, short
, standard note
1064
44
, nor_op_temp_units
, short
, standard note
1056
45
, alt_op_pres_units
, short
, standard note
1064
46
, alt_op_temp_units
, short
, standard note
1056
47
, nor_dgn_pres_units
, short
, standard note
1064
48
, nor_dgn_temp_units
, short
, standard note
1056
58
, character(8)
, short
, double
200
, double
, character(6)
, character(10)
Database Overview
49
, alt_dgn_pres_units
, short
50
, alt_dgn_temp_units
, short
51
, steam_temp_units
, short
52
, stress_system_no
, character(12)
53
, stress_reqmts
, short
54
, hyd_system_no
, character(12)
55
, hyd_reqmts
56
, specific_gravity_a
, double
57
, specific_gravity_b
, double
58
, specific_gravity_c
, double
59
, viscosity
, double
60
, density
, double
61
, spec_heat_ratio
, double
62
, sonic_velocity
, double
63
, surface_roughness
, double
64
, test_system_no
, character(6)
65
, test_fluid
, short
66
, test_pressure
, double
67
, PID_id_part_a
, character(4)
68
, PID_id_part_b
, character(4)
69
, end_1_nozzle_id
, integer
70
, end_2_nozzle_id
, integer
71
, alpha_descript_id
, character(12)
72
, standard_note_no
, short
73
, pid_index_no
, integer
74
, color_code
, character(8)
75
, inspection_iso_id
, character(24)
76
, index_to_pi_dwg
, integer
77
, weld_id
78
, sppid_piperun_guid
, character(32)
79
, sppid_drawing_guid
, character(32)
, short
, standard note
1064
, standard note
1056
, standard note
1056
, standard note
360
, standard note
360
, standard note
125
, standard note
499
, character(80)
34
, number of columns
126
1 , system_unique_no
, integer
2 , piping_comp_no
, character(20)
3 , commodity_name
, character(6)
4 , model_code
, character(6)
5 , option_code
, short
6 , maximum_temp
, double
7 , sched_thick_basis
, character(8)
8 , commodity_code
, character(16)
9 , MTO_requirements
, short
, index
, standard note
400
, standard note
332
, standard note
365
59
Database Overview
10
, fabrication_cat
, short
, standard note
180
11
, source_of_data
, short
, standard note
420
12
, PDS_sort_code
, character(6)
13
, physical_data_id
, character(8)
14
, geometric_standard
, standard note
575
15
, weight_code
, standard note
578
16
, table_suffix_green
, standard note
576
17
, table_suffix_red
, short
, standard note
577
18
, materials_grade
, short
, standard note
145
19
, bend_radius
, double
20
, bend_angle
, double
21
, face_to_face_dim
, double
22
, dimension_a
, double
23
, dimension_b
, double
24
, dimension_c
, double
25
, surface_area
, double
, empty_weight
, double
27
, water_weight
, double
, standard note
(units)
, standard note
(units)
, standard note
(units)
1010
26
28
, operator_weight
, double
29
, operator_sym_name
, character(6)
30
, chain_operator_no
, short
31
, opening_action
, short
, standard note
390
32
, construction_stat
, short
, standard note
130
33
, hold_status
, short
, standard note
50
34
, heat_tracing_reqmt
, short
, standard note
200
35
, heat_tracing_media
, short
, standard note
210
36
, heat_tracing_temp
, double
37
, iso_dwg_index_no
, integer
38
, isometric_sheet_no
39
, piece_mark_no
, character(60)
40
, color_code
, character(8)
41
, stress_node_no
, short
42
, stress_intens_fact
43
, head_loss_factor
, double
44
, piping_assembly
, character(12)
45
, component_group_no
46
, remarks
47
, standard_note_no_a
, short
, standard note
499
48
, standard_note_no_b
, short
, standard note
499
49
, cp_1_nom_pipe_diam
, short
50
, cp_1_outside_diam
, double
51
, cp_1_end_prep
, short
, standard note
330
60
, short
, short
, short
1028
1028
, character(2)
, double
, short
, character(50)
Database Overview
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
, standard note
332
, standard note
400
1100
, standard note
400
(bolt option)
57
, cp_1_gasket_gap
58
, cp_1_gasket_option
, double
59
, cp_1_stress_node
60
, cp_1_stress_factor
61
, cp_1_head_loss
62
, cp_2_nom_pipe_diam
63
, cp_2_outside_diam
, double
64
, cp_2_end_prep
, short
, standard note
330
65
, cp_2_sch_thk
, character(8)
, standard note
332
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
, standard note
400
1100
, standard note
400
, short
, short
, double
, double
, short
(bolt option)
70
, cp_2_gasket_gap
71
, cp_2_gasket_option
, double
72
, cp_2_stress_node
73
, cp_2_stress_factor
74
, cp_2_head_loss
75
, cp_3_nom_pipe_diam
76
, cp_3_outside_diam
, double
77
, cp_3_end_prep
, short
, standard note
330
78
, cp_3_sch_thk
, character(8)
, standard note
332
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
, standard note
400
1100
, standard note
400
, standard note
330
, short
, short
, double
, double
, short
(bolt option)
83
, cp_3_gasket_gap
, double
84
, cp_3_gasket_option
85
, cp_3_stress_node
86
, cp_3_stress_factor
87
, cp_3_head_loss
88
, cp_4_nom_pipe_diam
89
, cp_4_outside_diam
, double
90
, cp_4_end_prep
, short
, short
, short
, double
, double
, short
61
Database Overview
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
, standard note
332
, standard note
400
1100
, standard note
400
(bolt option)
96
, cp_4_gasket_gap
97
, cp_4_gasket_option
, double
98
, cp_4_stress_node
99
, cp_4_stress_factor
, short
, short
, 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
, standard note
330
104, cp_5_sch_thk
, character(8)
, standard note
332
105, cp_5_rating
, character(8)
106, cp_5_face_to_ctr
, double
107, cp_5_weld_no
, character(8)
108, cp_5_weld_type
, short
, standard note
400
1100
, standard note
400
(bolt option)
109, cp_5_gasket_gap
, double
110, cp_5_gasket_option
, short
111, cp_5_stress_node
, short
112, cp_5_stress_factor
, double
113, cp_5_head_loss
, double
114, unique_name
, character(12)
115, vlv_operator_dim_a
, double
116, vlv_operator_dim_b
, double
117, vlv_operator_dim_c
, double
118, vlv_operator_dim_d
, double
119, last_placed_date
, integer
120, generic_comp_no
, character(20)
121, inspection_key
, short
122, cp_1_inspect_key
, short
123, cp_2_inspect_key
, short
124, cp_3_inspect_key
, short
125, cp_4_inspect_key
, short
126, cp_5_inspect_key
, short
# Piping/Tubing Data
table number
50
, number of columns
61
1 , system_unique_no
, integer
2 , piping_comp_no
, character(20)
62
, index
Database Overview
3 , commodity_name
, character(6)
4 , model_code
, character(6)
5 , option_code
, short
6 , maximum_temp
, double
7 , nominal_piping_dia
, standard note
400
, standard note
332
, standard note
332
, short
8 , outside_diameter
9 , schedule_thickness
, double
, character(8)
10
, sched_thick_basis
, character(8)
11
, rating
, character(8)
12
, commodity_code
, character(16)
13
, MTO_requirements
, short
, standard note
365
14
, fabrication_cat
, short
, standard note
180
15
, source_of_data
, short
, standard note
425
16
, PDS_sort_code
, character(6)
17
, geometric_standard
, standard note
575
18
, weight_code
, standard note
578
19
, table_suffix_green
, standard note
576
20
, table_suffix_red
, short
, standard note
577
21
, materials_grade
, short
, standard note
145
22
, pipe_length
, double
23
, surface_area
, double
, empty_weight
, double
25
, water_weight
, double
, standard note
(units)
, standard note
(units)
, standard note
(units)
1010
24
26
, cold_spring_length
27
, construction_stat
, short
, standard note
130
28
, hold_status
, short
, standard note
50
29
, heat_tracing_reqmt
, short
, standard note
200
30
, heat_tracing_media
, short
, standard note
210
31
, heat_tracing_temp
, double
32
, iso_dwg_index_no
, integer
33
, isometric_sheet_no
34
, piece_mark_no
, character(60)
35
, color_code
, character(8)
36
, piping_assembly
37
, component_group_no
38
, remarks
39
, standard_note_no_a
, short
, standard note
499
40
, standard_note_no_b
, short
, standard note
499
41
, end_1_end_prep
, short
, standard note
330
42
, end_1_weld_no
, character(8)
43
, end_1_weld_type
, short
, standard note
400
1100
, short
, short
, short
1028
1028
, double
, character(2)
, character(12)
, short
, character(50)
(bolt option)
63
Database Overview
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
, standard note
400
, standard note
330
, standard note
400
1100
, standard note
400
(bolt 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
, last_placed_date
, integer
59
, inspection_key
, short
60
, end_1_inspect_key
, short
61
, end_2_inspect_key
, short
67
, number of columns
1 , system_unique_no
133
2 , instrument_comp_no
, integer
, index
, character(20)
3 , model_code
, character(6)
4 , option_code
, short
, standard note
5 , sched_thick_basis
, character(8)
, standard note
332
6 , MTO_requirements
, short
, standard note
365
7 , fabrication_cat
, short
, standard note
180
8 , source_of_data
, short
, standard note
430
9 , PDS_sort_code
, character(6)
, standard note
575
, standard note
578
400
10
, physical_data_id
11
, geometric_standard
12
, weight_code
13
, table_suffix_green
, standard note
576
14
, table_suffix_red
, short
, standard note
577
15
, materials_grade
, short
, standard note
145
16
, face_to_face_dim
, double
17
, dimension_a
, double
18
, dimension_b
, double
19
, dimension_c
, double
20
, surface_area
, double
1010
21
, empty_weight
, double
, standard note
(units)
, standard note
(units)
64
, character(8)
, short
, short
, short
1028
Database Overview
22
, water_weight
, double
, standard note
(units)
, standard note
(units)
1028
23
, operator_weight
, double
24
, operator_type
, double
25
, operator_sym_name
, character(6)
26
, chain_operator_no
, short
27
, chain_length
, double
28
, opening_action
29
, construction_stat
, short
, standard note
390
, short
, standard note
130
30
, hold_status
, short
, standard note
50
31
, design_resp
, short
, standard note
160
32
, construction_resp
, short
, standard note
160
33
, heat_tracing_reqmt
, short
, standard note
200
34
, heat_tracing_media
, short
, standard note
210
35
, heat_tracing_temp
36
, insulation_purpose
, standard note
220
37
, insulation_thick
38
, insulation_density
1074
39
, cleaning_reqmts
, short
, standard note
(units)
, standard note
40
, safety_class
, short
, standard note
340
41
, module_no
, character(16)
42
, package_system_no
, character(12)
43
, iso_dwg_index_no
, integer
44
, isometric_sheet_no
45
, piece_mark_no
, character(60)
46
, color_code
, character(8)
47
, stress_node_no
48
, stress_intens_fact
49
, head_loss_factor
50
, piping_assembly
51
, component_group_no
52
, remarks
53
, standard_note_no_a
, short
, standard note
499
54
, standard_note_no_b
, short
, standard note
499
55
, cp_1_nom_pipe_diam
, short
56
, cp_1_outside_diam
, double
57
, cp_1_end_prep
, short
, standard note
330
58
, cp_1_sch_thk
, character(8)
, standard note
332
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
, standard note
400
1100
1028
, double
, short
, double
, double
230
, character(2)
, short
, double
, double
, character(12)
, short
, character(50)
(bolt option)
65
Database Overview
63
, cp_1_gasket_gap
, double
64
, cp_1_gasket_option
65
, cp_1_stress_node
66
, cp_1_stress_factor
67
, cp_1_head_loss
68
, cp_2_nom_pipe_diam
69
, cp_2_outside_diam
, double
70
, cp_2_end_prep
71
, short
, standard note
400
, short
, standard note
330
, cp_2_sch_thk
, character(8)
, standard note
332
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
, standard note
400
1100
, standard note
400
, short
, double
, double
, short
(bolt option)
76
, cp_2_gasket_gap
, double
77
, cp_2_gasket_option
78
, cp_2_stress_node
79
, cp_2_stress_factor
80
, cp_2_head_loss
81
, cp_3_nom_pipe_diam
82
, cp_3_outside_diam
, double
83
, cp_3_end_prep
, short
, standard note
330
84
, cp_3_sch_thk
, character(8)
, standard note
332
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
, standard note
400
1100
, standard note
400
, short
, short
, double
, double
, short
(bolt option)
89
, cp_3_gasket_gap
90
, cp_3_gasket_option
, double
91
, cp_3_stress_node
92
, cp_3_stress_factor
93
, cp_3_head_loss
94
, cp_4_nom_pipe_diam
95
, cp_4_outside_diam
, double
96
, cp_4_end_prep
, short
, standard note
330
97
, cp_4_sch_thk
, character(8)
, standard note
332
98
, cp_4_rating
, character(8)
99
, cp_4_face_to_ctr
, double
, standard note
400
1100
, short
, short
, double
, double
, short
100, cp_4_weld_no
, character(8)
101, cp_4_weld_type
, short
(bolt option)
66
Database Overview
102, cp_4_gasket_gap
, double
103, cp_4_gasket_option
, short
104, cp_4_stress_node
, standard note
400
, short
105, cp_4_stress_factor
, double
106, cp_4_head_loss
, double
107, cp_5_nom_pipe_diam
, short
108, cp_5_outside_diam
, double
109, cp_5_end_prep
, short
, standard note
330
110, cp_5_sch_thk
, character(8)
, standard note
332
111, cp_5_rating
, character(8)
112, cp_5_face_to_ctr
, double
113, cp_5_weld_no
, character(8)
114, cp_5_weld_type
, short
, standard note
400
1100
, standard note
400
(bolt option)
115, cp_5_gasket_gap
, double
116, cp_5_gasket_option
, short
117, cp_5_stress_node
, short
118, cp_5_stress_factor
, double
119, cp_5_head_loss
, double
120, unique_name
, character(12)
121, bend_angle
, double
122, vlv_operator_dim_a
, double
123, vlv_operator_dim_b
, double
124, vlv_operator_dim_c
, double
125, vlv_operator_dim_d
, double
126, last_placed_date
, integer
127, generic_comp_no
, character(20)
128, inspection_key
, short
129, cp_1_inspect_key
, short
130, cp_2_inspect_key
, short
131, cp_3_inspect_key
, short
132, cp_4_inspect_key
, short
133, cp_5_inspect_key
, short
80
, number of columns
50
1 , system_unique_no
, integer
2 , pipe_support_no
, character(20)
3 , model_code_phy
, character(6)
4 , model_code_log
, character(6)
, index
5 , iso_support_type_a
, short
, standard note
380
6 , iso_support_type_b
, short
, standard note
380
7 , iso_support_type_c
, short
, standard note
380
67
Database Overview
8 , iso_support_type_d
, short
, standard note
380
9 , details_for_shop
, character(50)
10
, details_for_field
, character(50)
11
, fabrication_orient
12
, commodity_code
, character(16)
13
, MTO_requirements
, short
, standard note
365
14
, fabrication_cat
, short
, standard note
180
15
, weight
, double
1028
16
, construction_stat
, short
, standard note
(units)
, standard note
17
, hold_status
, short
, standard note
50
18
, standard_note_no
, short
, standard note
499
19
, iso_dwg_index_no
, integer
20
, isometric_sheet_no
21
, piece_mark_no
, character(60)
22
, color_code
, character(8)
23
, isometric_dim_a
, double
24
, isometric_dim_b
, double
25
, isometric_dim_c
, double
26
, isometric_dim_d
, double
27
, isometric_dim_e
, double
28
, trans_rigidity_x
, double
29
, trans_rigidity_y
, double
30
, trans_rigidity_z
, double
31
, rot_rigidity_x
, double
32
, rot_rigidity_y
, double
33
, rot_rigidity_z
, double
34
, spring_gap_length
, double
35
, sping_gap_direct
, short
36
, number_of_springs
, short
37
, last_placed_date
, integer
38
, inspection_key
, short
39
, mark_number
, character(80)
40
, group_id
, integer
41
, gang_id
, integer
42
, material_grade
, short
, standard note
145
43
, weld_code
, short
44
, material_index
, character(16)
45
, operating_load
, double
46
, installed_load
, double
47
, hydrostatic_load
, double
48
, total_movement_1
, double
, character(20)
130
, character(2)
, in subunits
-- distance
attribute
68
Database Overview
49
, total_movement_2
, double
, in subunits
, double
, in subunits
-- distance
attribute
50
, rod_diameter
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
23
, system_unique_no
, integer
, piping_mater_class
, revision_no
, character(2)
, version_no
, character(2)
, revision_date
, character(10)
, fluid_code
, character(6)
, mater_of_construct
, corrosion_allow
, double
, mat_description
, short
, character(16)
125
, standard note
148
, character(6)
10, service_lim_table
, character(6)
11, diameter_table
, character(6)
12, thickness_table
, character(6)
13, materials_table
, character(6)
14, thickness_equation
, standard note
, character(6)
15, branch_table
, character(6)
16, tap_data_table
, character(6)
17, vent_drain_macro
, character(6)
18, gasket_separation
, character(8)
19, standard_note_no_a
, short
, standard note
499
20, standard_note_no_b
, short
, standard note
499
21, revision_mngt_date
, integer
22, bend_deflect_table
, character(6)
23, pipe_length_table
, character(6)
28
, system_unique_no
, piping_mater_class
, integer
, commodity_name
, character(6)
, option_code
, short
, maximum_temp
, double
, character(16)
, index
, standard note
400
69
Database Overview
6
, gcp_from_nom_diam
, short
, gcp_to_nom_diam
, short
, gcp_end_prep
, short
, gcp_rating
, character(8)
10, gcp_sch_thk
, character(8)
11, gcp_table_suffix
, short
12, rcp_from_nom_diam
, short
13, rcp_to_nom_diam
, short
14, rcp_end_prep
, short
15, rcp_rating
, character(8)
16, rcp_sch_thk
, character(8)
17, rcp_table_suffix
, short
18, commodity_code
, character(16)
19, model_code
, character(6)
20, PDS_sort_code
, character(6)
21, modifier
, standard note
330
, standard note
576
, standard note
330
, standard note
577
, standard note
575
, double
22, geometric_standard
, short
23, weight_code
, short
, standard note
578
24, fabrication_cat
, short
, standard note
180
25, materials_grade
, short
, standard note
145
26, standard_note_no_a
, short
, standard note
499
27, standard_note_no_b
, short
, standard note
499
, standard note
990
, standard note
400
, standard note
330
, standard note
576
, standard note
330
, standard note
577
28, input_form_type
, short
26
, system_unique_no
, integer
, piping_comp_no
, character(20)
, model_code
, character(6)
, option_code
, short
, gcp_from_nom_diam
, short
, gcp_to_nom_diam
, short
, gcp_end_prep
, short
, gcp_rating
, character(8)
, gcp_sch_thk
, character(8)
10, gcp_table_suffix
, short
11, rcp_from_nom_diam
, short
12, rcp_to_nom_diam
, short
13, rcp_end_prep
, short
14, rcp_rating
, character(8)
15, rcp_sch_thk
, character(8)
16, rcp_table_suffix
, short
17, physical_data_id
, character(8)
70
Database Overview
18, PDS_sort_code
, character(6)
19, modifier
, double
20, geometric_standard
, short
, standard note
575
21, weight_code
, short
, standard note
578
22, fabrication_cat
, short
, standard note
180
23, materials_grade
, short
, standard note
145
24, standard_note_no_a
, short
, standard note
499
25, standard_note_no_b
, short
, standard note
499
, standard note
990
, standard note
400
, standard note
330
, standard note
576
, standard note
330
, standard note
577
26, input_form_type
, short
26
, system_unique_no
, integer
, instrument_comp_no
, model_code
, character(6)
, option_code
, short
, gcp_from_nom_diam
, short
, gcp_to_nom_diam
, short
, gcp_end_prep
, short
, gcp_rating
, character(8)
, gcp_sch_thk
, character(8)
, character(20)
10, gcp_table_suffix
, short
11, rcp_from_nom_diam
, short
12, rcp_to_nom_diam
, short
13, rcp_end_prep
, short
14, rcp_rating
, character(8)
15, rcp_sch_thk
, character(8)
16, rcp_table_suffix
, short
17, physical_data_id
, character(8)
18, PDS_sort_code
, character(6)
19, modifier
, double
20, geometric_standard
, standard note
575
21, weight_code
, short
, short
, standard note
578
22, fabrication_cat
, short
, standard note
180
, short
23, materials_grade
, standard note
145
24, standard_note_no_a
, short
, standard note
499
25, standard_note_no_b
, short
, standard note
499
, standard note
990
26, input_form_type
, short
, system_unique_no
, integer
, tap_table_name
, character(6)
, nominal_piping_dia
, short
71
Database Overview
4
, option_code
, short
, standard note
400
, end_preparation
, short
, standard note
330
, rating
, character(8)
, sched_thick
, character(8)
, tap_material_code
, character(10)
10
, system_unique_no
, integer
, sys_commodity_code
, gcp_nom_diam
, short
, rcp_nom_diam
, short
, gcp_sch_thk
, character(8)
, rcp_sch_thk
, character(8)
, commodity_code
, character(16)
, weld_weight
, double
, unit_price
, double
, character(16)
10, manhours
, index
, index
, double
10
, system_unique_no
, integer
, sys_commodity_code
, gcp_from_nom_diam
, short
, gcp_to_nom_diam
, short
, rcp_from_nom_diam
, short
, rcp_to_nom_diam
, short
, commodity_code
, character(16)
, quantity
, double
, fabrication_cat
, short
10, standard_note_no
, short
, character(16)
, specialty_rev_date
, instr_rev_date
, tap_data_rev_date
, size_data_rev_date
, implied_rev_date
, cmp_insul_rev_date
, integer
, flg_insul_rev_data
, integer
, con_tol_excl_data
, integer
, integer
, integer
, integer
, integer
, integer
, system_unique_no
72
13
, integer
Database Overview
2
, commodity_name
, character(6)
, model_code
, character(6)
, gcp_npd_from
, short
, gcp_npd_to
, short
, rcp_npd_from
, short
, rcp_npd_to
, short
, heat_tracing_from
, short
, standard note
200
, heat_tracing_to
, short
, standard note
200
, standard note
220
, standard note
220
10, insul_purpose_from
, short
11, insul_purpose_to
12, nor_oper_temp_from
, short
, double
13, nor_oper_temp_to
, double
, system_unique_no
, integer
, bolted_npd_from
, short
, bolted_npd_to
, short
, heat_tracing_from
, short
, standard note
200
, heat_tracing_to
, short
, standard note
200
, insul_purpose_from
, standard note
220
, insul_purpose_to
, standard note
220
, nor_oper_temp_from
, nor_oper_temp_to
, short
, short
, double
, double
, system_unique_no
, integer
, commodity_name
, character(6)
, model_code
, character(6)
, gcp_npd_from
, short
, gcp_npd_to
, short
, rcp_npd_from
, short
, rcp_npd_to
, short
, system_unique_no
, integer
, support_group
, character(6)
, group_descr
, character(40)
11
, system_unique_no
, integer
, support_group
, character(6)
, commodity_name
, character(6)
73
Database Overview
4
, npd_from
, short
, npd_to , short
, tdf_table_name
, character(8)
, temp_table
, character(8)
, sched_table
, character(8)
, attachment_type
, short
10, model_code
, character(6)
11, material_desr
, character(50)
10
, system_unique_no
, integer
, commodity_name
, character(6)
, npd_from
, short
, npd_to , short
, geometric_standard
, short
, standard note
, material_index
, character(16)
, drawing_seed
, character(16)
, item_key0
, character(2)
, item_key1
, character(2)
10
, item_key2
575
, character(2)
, system_unique_no
, integer
, material_index
, character(16)
, sequence_number
, short
, quantity
, short
, dimension_att_no
, short
, implied_status
, short
, material_descr
, character(80)
74
SECTION 3
Reference Data
The Refer ence 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
Label Descriptions
Piping Assembly Definitions
The following illustrates the basic components of the Reference Data for PDS 3D.
The Refer ence 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.
75
Reference Data
In This Section
Delivered Reference Data .............................................................. 76
Piping Job Specification ................................................................ 77
Graphic Commodity Data and Physical Dimension Data............. 87
Material Description Data.............................................................. 87
Standard Note Library ................................................................... 89
Label Description Library.............................................................. 89
Piping Assembly Library ............................................................... 89
File Description
Object
Text
us_pcdim.l
us_pcdim.l.t
us_pjstb.l
us_pjstb.l.t
us_shbom.l
us_lgbom.l
File Description
Object
Text
pip_gcom.l
pip_gcom.l.t
assembly.l
assembly.l.t
labels.l
76
Reference Data
File Description
Object
Text
zi_eqpms.li
b
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. The script mkpdsdir.sh will copy the reference data to
the appropriate directories after 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.
Spec Table Library - library containing the specification tables referenced in the PJS.
The information in the Specification/Material Reference database and Spec Table Library tables
is also delivered in the form of neutral files which you can extract and modify.
You can use the Piping J ob Specification Manager to create or revise the PJS. The Spec
Manager enables you to define or revise the PJS data, and process neutral ASCII files to define
data in the PJS.
499
499
77
Reference Data
22, bend_deflect_table
23, pipe_length_table
, character(6)
, character(6)
Co n n e c t P o in t Da ta
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:
78
If data is only shown under the green connect point, it applies to all ends of the component.
If a component has ends with different nominal diameters (regardless of other end
properties) the larger nominal diameter is designated as the green connect point.
If a component has ends with the same nominal diameter but other end properties which
differ, the following rules apply:
Reference Data
If the ends have different termination types (regardless of the values for
schedule/thickness) the end(s) whose end preparations have the lowest codelist number
are designated as the green connect point.
If the termination types are the same but the values for rating, schedule, or thickness
differ, the stronger end(s) is designated as the green connect point.
system_unique_no
, integer
piping_mater_class , character(16) , index 1
commodity_name , character(6)
option_code
, short
, standard note 400
maximum_temp
, double
gcp_from_nom_diam
, short
gcp_to_nom_diam
, short
gcp_end_prep
, short
, standard note 330
gcp_rating
, character(8)
gcp_sch_thk
, character(8)
gcp_table_suffix
, short
, standard note 576
rcp_from_nom_diam , short
rcp_to_nom_diam , short
rcp_end_prep , short , standard note 330
rcp_rating , character(8)
rcp_sch_thk , character(8)
rcp_table_suffix , short , standard note 577
commodity_code , character(16)
model_code , character(6)
PDS_sort_code , character(6)
modifier , double
geometric_standard , short , standard note 575
weight_code , short , standard note 578
fabrication_cat , short , standard note 180
materials_grade , short , standard note 145
standard_note_no_a , short , standard note 499
standard_note_no_b , short , standard note 499
input_form_type , short , standard note 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
79
Reference Data
system_unique_no
, integer
2,
piping_comp_no
, character(20)
3,
model_code
, character(6)
4,
option_code
, short
5,
gcp_from_nom_diam
, short
6,
gcp_to_nom_diam
, short
7,
gcp_end_prep
, short
8,
gcp_rating
, character(8)
9,
gcp_sch_thk
, character(8)
10
,
11
,
12
,
13
,
14
,
15
,
16
,
17
,
18
,
19
,
20
,
21
,
22
,
23
,
24
,
25
,
gcp_table_suffix
, short
rcp_from_nom_diam
, short
rcp_to_nom_diam
, short
rcp_end_prep
, short
rcp_rating
, character(8)
rcp_sch_thk
, character(8)
rcp_table_suffix
, short
physical_data_id
, character(8)
PDS_sort_code
, character(6)
modifier
, double
geometric_standard
, short
, standard
note
400
, standard
note
330
, standard
note
576
, standard
note
330
, standard
note
577
, standard
note
575
weight_code
, short
, standard
note
578
fabrication_cat
, short
, standard
note
180
materials_grade
, short
, standard
note
145
standard_note_no_a
, short
, standard
note
499
standard_note_no_b
, short
, standard
note
499
80
Reference Data
, system_unique_no
, integer
, instrument_comp_no
, model_code
, character(6)
, option_code
, short
, gcp_from_nom_diam
, short
, gcp_to_nom_diam
, short
, gcp_end_prep
, short
, gcp_rating
, character(8)
, gcp_sch_thk
, character(8)
, character(20)
10, gcp_table_suffix
, short
11, rcp_from_nom_diam
, short
12, rcp_to_nom_diam
, short
13, rcp_end_prep
, short
14, rcp_rating
, character(8)
15, rcp_sch_thk
, character(8)
16, rcp_table_suffix
, short
17, physical_data_id
, character(8)
18, PDS_sort_code
, character(6)
19, modifier
, double
20, geometric_standard
, short
, standard note
400
, standard note
330
, standard note
576
, standard note
330
, standard note
577
, standard note
575
21, weight_code
, short
, standard note
578
22, fabrication_cat
, short
, standard note
180
, short
23, materials_grade
, standard note
145
24, standard_note_no_a
, short
, standard note
499
25, standard_note_no_b
, short
, standard note
499
81
Reference Data
A sample neutral file is delivered in the file win32app\ingr\pddata\sample\data\instrment.data .
,
,
,
,
,
,
,
,
system_unique_no ,
tap_table_name ,
nominal_piping_dia ,
option_code ,
end_preparation ,
rating ,
sched_thick ,
tap_material_code ,
integer
character(6)
short
short ,
standard note 400
short ,
standard note 330
character(8)
character(8)
character(10)
Order=
2
By=GJH
Date=12-May-1988
Table=
82
4
6
Ckd By=RJW
7
Rev=2
C001
Description= SWE CL3000
Diam
0.375
Opt
691
>
0.5
0.5
691
0.75
0.75
691
>
Prp
591
Sc/Th
NREQD
Tap Code
E$37591XXX
CL3000
421
NREQD
E$50421064
591
NREQD
E$50591XXX
421
NREQD
E$75421064
591
NREQD
E$75591XXX
CL3000
-
default
Rating
taps
Reference Data
>
CL3000
691
>
1.25
1
691
1
>
1.25
1.5
1.5
2
691
1
>
691
2.5
3
691
1
691
3.5
4
691
1
691
5
6
>
>
421
NREQD
E001421064
591
NREQD
E001591XXX
CL3000
421
NREQD
E1
$2,421,064
CL3000
591
421
NREQD
NREQD
E1
E1
$2591XXX
$5,421,064
CL3000
591
421
NREQD
NREQD
E1
$5591XXX
E002421064
591
NREQD
E002591XXX
591
421
NREQD
NREQD
E2
$5591XXX
E003421064
591
NREQD
E003591XXX
591
421
NREQD
NREQD
E3
$5591XXX
E004421064
591
NREQD
E004591XXX
691
591
NREQD
E005591XXX
691
591
NREQD
E006591XXX
691
591
NREQD
E008591XXX
10
691
591
NREQD
E010591XXX
12
691
591
NREQD
E012591XXX
14
691
591
NREQD
E014591XXX
16
691
591
NREQD
E016591XXX
18
691
591
NREQD
E018591XXX
20
691
591
NREQD
E020591XXX
24
691
591
NREQD
E024591XXX
26
691
591
NREQD
E026591XXX
28
691
591
NREQD
E028591XXX
30
691
591
NREQD
E030591XXX
32
691
591
NREQD
E032591XXX
34
691
591
NREQD
E034591XXX
36
691
591
NREQD
E036591XXX
42
691
591
NREQD
E042591XXX
48
691
591
NREQD
E048591XXX
CL3000
CL3000
,
,
,
system_unique_no ,
sys_commodity_code ,
gcp_nom_diam
,
integer
character(16)
short
83
Reference Data
4
5
6
7
8
9
10,
,
rcp_nom_diam
,
short
,
gcp_sch_thk ,
character(8)
,
rcp_sch_thk ,
character(8)
,
commodity_code
,
character(16)
,
weld_weight ,
double
,
unit_price ,
double
manhours
,
double
index 1
84
, system_unique_no
, integer
, sys_commodity_code
, character(16)
, gcp_from_nom_diam
, short
, gcp_to_nom_diam
, short
, rcp_from_nom_diam
, short
, rcp_to_nom_diam
, short
, commodity_code
, character(16)
, quantity
, double
, fabrication_cat
, short
10, standard_note_no
, short
, index
Reference Data
A sample neutral file for US practice is delivered in the file
win32app\ingr\rdusrdb\spec_data\implied.data .
85
Reference Data
This table includes the sets of temperatures and pressures that define the boundaries of
acceptability for a piping materials class.
The NPD tables lists the diameters for piping and tubing which are valid within any piping
materials class which references this table.
86
Reference Data
Graphic Commodity Library - contains the parametric definitions for the commodity items.
Entries in this library use the EDEN programming language.
Physical Dimension Libraries - contains dimension data for the commodity items. (A
different Physical Dimension Library is required for each type of practice such as, U.S.,
DIN, or British Standard)
The parametric descriptions and dimension tables are also delivered in the form of text libraries
which you can extract and modify using the Gr aphic Data Libr ar y Manager and Physical
Data Libr ar y Manager .
Refer to Chapter 4, How PDS Works, for examples of parametric definitions and dimension
tables.
Material Take-off (MTO) reporting from the Design Database Other miscellaneous reporting
Stress analysis
Isometric drawing extraction.
The Material Description Data consists of the commodity item data which is not stored in the
Design Database, which is not required for the creation of graphic symbologies, and which is not
part of the geometric data. This data is contained in the following files:
Short Material Description Library - contains the short material descriptions for commodity
items and taps.
Long Material Description Library - contains the long material descriptions for commodity
items.
Specialty Material Description Library - contains the material descriptions for specialty
items.
87
Reference Data
The material descriptions are also delivered in the form of neutral files which you can modify
and post to the libraries. The following shows a portion of a neutral file for the short material
description library.
!
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
'45 deg LR elbow, [403], BE, ASTM-A420-WPL6, ANSI-B16.9'
WBAFBAWIKB
'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'
88
Reference Data
The Mater ial Descr iption Libr ar y 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.
Alphanumeric labels
Displayable attribute messages
These labels are intelligent graphics with links to the material database.
The Label Descr iption Libr ar y Manager enables you to define the graphic parameters for a
label (such as level, line weight, and color code) and to define the format of the label (what
information comprises the label.)
89
Reference Data
The resulting graphics created by the PAL file look like this:
90
SECTION 4
uses the active parameters (such as piping materials class and nominal diameter) to search
for the selected item name in the Specification Material Reference Database. If the selected
item is found in the RDB, the system reads the specification data for the parameters required
to place the component. Included in this information is the model code (or specialty item
number) for the selected component and the names of the spec tables defined for the Piping
Materials Class.
uses the model code (or specialty item number), derived from the RDB, to access the
Graphic Commodity Library. The definitions in the Graphic Commodity Library determine
the physical tables required to place the component and call the tables in the Physical
Dimension Library.
places the symbol graphics in the model design file and writes the nongraphic information
for the component in the database.
91
92
93
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.
94
P ip in g Ma te ria ls Cla s s Co d e
The delivered reference data uses a 6 character code for the PMC based on the following
convention.
F
- Pressure Rating
- Material Group
-CL150
- Carbon Steels
0031
Therefore, PMC 1C003 1 equals 150# Carbon Steel, Standard Raised Face, with trim 8.
Refer to the listing of Code List Set 148 in the PDS Piping Component Data Reference Guide
for information on all the codes.
An alternate naming scheme is also described under Code List Set 148. This alternate
scheme uses the convention:
A - Materials Group
B - Materials Type
C - Detail Features
D - Corrosion Allowance
E
- Service
- Pressure Rating
- 0.063"
-CL150
You can use either of these conventions or use any standard character code up to 16
characters.
95
Te m p e ra tu re P re s s u re Ta b le
This attribute identifies the table used to determine maximum pressure as a function of
temperature. This table includes the pressure and temperature sets that form the boundary for
which the commodity items included in this piping materials class are suitable.
Dia m e te r Ta b le
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
96
Th ic kn e s s Ta b le
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.
97
Ma te ria ls Ta b le
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
!
!Mat Gr Temp
Thick
Range
Y
S
116
-20
.4
20000
116
100
.4
20000
116
200
.4
20000
116
300
.4
20000
116
400
.4
20000
116
500
.4
18900
116
600
.4
17300
116
650
.4
17000
116
700
.4
16500
116
750
.4
13000
116
800
.4
10800
142
-20
.4
20000
142
100
.4
20000
142
200
.4
20000
142
300
.4
20000
142
400
.4
20000
142
500
.4
18900
142
600
.4
17300
142
650
.4
17000
142
700
.4
16500
142
750
.4
13000
142
800
.4
10800
162
-20
.4
20000
162
100
.4
20000
162
200
.4
20000
162
300
.4
20000
162
400
.4
20000
162
500
.4
18900
162
600
.4
17300
162
650
.4
17000
162
700
.4
16500
162
750
.4
13000
162
800
.4
10800
Mill
%
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
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
12.5
Tolrnce
Value
-
Th ic kn e s s Eq u a tio n s
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
98
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
Ga s ke t Ga p / Ta b le
This attribute defines either a single gasket gap value or a table used to determine the gasket gap
based on nominal diameter and maximum temperature. If a table is specified, the system uses the
NPD of each bolted end and the maximum temperature for the gasket at that end to determine
the gap thickness.
In this example, the actual gap value (.125) is used rather than a table name.
99
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.
Ite m Na m e a n d Mo d e l Co d e
When you select the Gate option from the Place Component form, the system sets the Item
Name to 6Q1C01. This is the item name for a gate valve in the delivered reference data. The
corresponding Model Code for this Item Name is GAT.
The item name is also called the AABBCC code because it is composed of a number of
parameters. For example, the code 6Q1C01 breaks down as follows
100
AA 6Q
BB 1C
Valves
CC 01
Gate Valve
Op tio n Co d e
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.
Gre e n a n d Re d Co n n e c t P o in t Da ta
Since a standard gate valve has the same properties at both ends (connect points) only green
connect point data is required.
! AABBCC
Green CP
! Code Opt From To
6Q1C01 1 3
12
The Fr om To values define the range of NPD values supported by this definition in this example
3" to 12".
The End Pr epar ation (Prp) is a code-listed attribute that identifies the end preparation for the
connect point. The system determines the termination type based on the range of values
2 - 199 bolted terminations
300 - 399 male terminations
400 - 599 female terminations
Using the values defined in Code List Set 330, the setting 21 indicates RFFE (Raised-Face
Flanged End).
The Rating identifies the pressure rating for the connect point. The setting CL 150 refers to
ANSI pressure rating CL 150. The system interprets the first set of sequential numeric characters
as the pressure rating value (150 in this example).
The Schedule Thickness (Sc/Th) exists as alphanumeric data. The value NREQD is used in
cases where all of the following conditions apply:
Either stress analysis is not applicable or, if applicable, the component is to be considered
infinitely rigid in stress analysis calculations.
The Table Suffix (TS) is a code-listed attribute (CL576) used to further reference the source of
the generic dimensional data, such as flange data or piping outside diameter data.
For AMS standards, it represents the table suffix for the green connect point. The value 5 is the
default for US practice. It represents the basis on which most US-practice generic piping tables
for dimensional parameters is defined.
End Termination Type
Raised-face flanged
101
Co m m o d ity Co d e
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.
Ge o m e tric In d u s try S ta n d a rd
This code-listed attribute (CL575) identifies the source of the data (which is usually an industry
standard, such as ANSI, ISO, or DIN, or a company standard) from which the specific geometry
of the commodity item can be deduced. This parameter represents the vendor or industry
standard, and the material if either affects the dimensions of the commodity item.
Code list numbers 2-6999 are reserved for geometry standards that apply to US piping practices.
The value 40 indicates
40 = ANSI-B16.10 [Dimensions of Ferrous Valves ||]
Mo d ifie r
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.
102
Ma te ria ls Gra d e
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 A216-WCB.
We ig h t c o d e
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
52 = 490 pcf [Carbon steel, low Cr alloy steel, stainless steel]
Fa b ric a tio n Ca te go ry
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 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.
103
The Place Component Er r or Data form displays the physical data libraries and Eden modules
that were accessed to place the component. The initial display lists the Eden modules that were
accessed. Indented lines indicate a module which was called from another module. The system
places an asterisk (*) beside the module name where Eden stopped executing.
The system uses the model code (or specialty item number) to access the graphic commodity
library. The definitions in the graphic commodity library determine the physical tables required
to place the component and call the tables in the physical commodity library.
The Graphic Commodity Library (GCL) provides data for commodity items, engineered items,
and instruments. It is basically a catalog of component data which is accessed to
determine physical data based on user specifications (such as NPD and end preparation)
assign connect point data from the Specification Material Reference Database
PDS Piping uses the Eden Parametric Language to define and place components, specialty items,
operators, and envelopes. Eden is a high- level programming language which uses information
from the Material Reference Database and model to access parametric and dimensional data.
Eden is composed of three major types of modules
104
Symbol Processors
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
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
105
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
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 subsymbol 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
106
The module name for a physical data module consists of a symbol type (such as V1, V2, and so
forth for valves) and a generic type of geometric industry standard (such as AMS or DIN). You
can define multiple physical data modules for the same symbol depending on the type of
standard being referenced (for example, V1_AMS for American standards and V 1_DIN for
European standards).
You can manage ten different sets of logic for table naming conventions for the following
industry practices. The corresponding table suffix ranges and the suffix for the Piping Eden
physical data modules are indicated below.
Practice
Range
Suffix
U.S. Practice
1-99
AMS
European - DIN
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.
107
Ge n e ric P h ys ic a l Da ta Mo d u le s
The generic modules contain information which is common to more than one symbol such as
flange thickness, gasket separation, and outside diameter. The physical data module V1_AMS
calls another physical data module VALVE_2_AMS which contains the generic dimension data
for all valves with two connect points.
Physical_Data_Definition VALVE_2_AMS
Input_1 = Nom_Pipe_D_1
If ( Gen_Type_1 .EQ. BOLTED ) Then
table_name = BLT // Term_Type_1 // Pr_Rating_1 //
Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_1
Thickness_1 = Output_2
Seat_Depth_1 = Output_3
Thickness_1 = Thickness_1 - Seat_Depth_1
CP_Offset_1 = Gasket_Sep_1
If ( Symbology .EQ. MODEL ) Then
Thickness_1 = 0.0
Depth_1 = 0.0
Pipe_OD_1 = 0.0
Body_OD_1 = Facing_OD_1
Else
table_name = MAL_300_5
108
109
110
111
Parametric shape definitions are divided into three basic types: model parametric shapes,
detailed parametric shapes, and interference envelopes. The first line of the Eden module
indicates the module type and the module name.
The module name for a parametric shape module consists of a symbol type (such as V1, V2, and
so forth, for valves).
The parametric shape module V1 determines the model graphics for a valve. This is the module
called by the symbol processor GAT. The parametric shape module OP3 determines the model
graphics for a hand wheel operator. This is the module called by the sub-symbol processor
OP_3.
Model _Parametric _Shape _Def inition 'V1'
Call Define_Connect_Point_Geometry ( LINEAR )
Call Place_Connect_Point ( CP1 )
Call Move_By_Distance ( CP_Offset_1 )
Call Draw_Cylinder_With_Capped_Ends ( Depth_1, Facing_OD_1 )
length = F_to_C_Dim_1 - Thickness_1
diameter = 0.0
Call Draw_Cone ( length, Body_OD_1, diameter )
Call Place_Connect_Point ( CP0 )
Call Place_COG_Location ( DRY_COG )
Call Place_COG_Location ( WET_COG )
Call Place_Connect_Point ( CP2 )
Return
End
112
Physical Data
Selecting the Component Data option of the Place Component Error Data form displays the
physical data used to place the component.
113
Ge n e ric Ta b le s
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).
114
S p e c ific Ta b le s
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:
Plant Design System 3D Theory
115
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.
116
The bend deflection table is used when placing components at the vertex of an existing piping
segment. The system uses the bend angle at the segment vertex to determine the type of
component to be placed.
This table defines which full size and reducing size component types will be placed for a
specified angle range. The angle is defined as the smallest angle that the continuation of one pipe
run makes with the other run. The component types are defined in the commodity item name
table.
117
Weld-in components actually making the intersection such as laterals and tees.
During branch component placement, the comparison test of header segment data will include
nominal piping diameter, override schedule/thickness and construction status.
Placement Examples
This section outlines the placement data for a bend, reducer, and tee placed on an existing
segment.
118
119
120
SECTION 5
Creating 3D Models
This chapter describes the basics of 3D modeling using the Equipment Modeling and Piping
Designer Tasks.
In This Section
Modeling Setup Requirements....................................................... 121
Graphics Environment for PDS 3D ............................................... 125
Creating Equipment Models .......................................................... 138
Equipment Modeling Commands .................................................. 147
Creating Piping Models ................................................................. 149
Piping Design Commands ............................................................. 163
121
Creating 3D Models
Project Setup
A project and all of its accompanying files must be defined with the Pr oject Administr ator
before you can use the Piping Designer or Equipment Modeling. Refer to the Project
Administrator Reference Guide for information on
Editing the control script to identify the location of the project data.
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 Pr oject 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.
122
Creating 3D Models
This seed data is discussed throughout the remainder of this chapter. Before creating models,
you should define the seed data to reflect your company practices so that all models will be
created with the same settings.
See chapter 6 of the Project Administrator (PD_Project) Reference Guide for detailed
information on the Pr oject Data Manager .
Model Files
The Pr oject Envir onment 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.
123
Creating 3D Models
In this example, there are 63 active levels and 252 referenced levels which you can control (the
two equipment models use the same levels and symbology). If a certain type of duct in the
HVAC model resides on Level 30 in that model, and all unapproved Instruments are to be placed
on Level 30 in the piping model, these are treated as two completely different levels.
That is, you can turn off the display for the duct types on Level 30 in the HVAC model (via the
Reference Model controls) without affecting the display of unapproved instruments in the active
piping model.
All PDS users are encouraged to develop a logical, organized level control standard to manage
interdiscipline design files. The delivered seed file parameters for each application provide a
logical, organized, and coordinated level designation and control scheme. You can customize the
delivered parameters, but it is highly recommended that careful thought be given to the custom
setup.
Once you develop a convention, whether it be the standard deliverable settings or an inhouse standard, do not change the level or symbology settings after model gr aphics have
been cr eated. There is no easy way to propagate these changes to the existing graphics in all the
design files. The existing graphics will reflect the old settings and any new graphics will reflect
the modified settings.
Since some applications rely on level assignments to perform basic functions (such as
placement of approved or unapproved items) which are transparent to the user, there is a very
real chance of destroying the integrity of the project if a symbology change is initiated after the
project is under way.
For this reason, Intergraph recommends that you do not change the basic structure of the
symbology without careful thought. Attributes such as line weights, colors, and line types are
124
Creating 3D Models
open to customization, but they should be established prior to project creation and should not
change throughout the life of the active design. Level assignments are also customizable;
however, they should be established before any components are placed in the model files.
PE-HVAC
Graphic symbology and level control is defined in an ASCII file named hvacSym.defe in the
project directory. The default data can be changed by editing the hvacSym.defe and
hvacSym.defm files in the project directory.
125
Creating 3D Models
The system verifies that you have write access to the selected model. If so, it activates the
graphical user interface for the selected modelfile.
126
Creating 3D Models
Me n u s
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.
127
Creating 3D Models
P a le tte s
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.
Dia lo g Bo xe s
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.
128
Creating 3D Models
Vie w Win d o ws
Closedeletes a window.
129
Creating 3D Models
Minimizecollapses a window.
Maximizeenlarges a window to its maximum size. If you choose the
maximize button on a window that is already at its maximum size, the
window is restored to its previous size and location.
Horizontal slider bar allows you to drag the view to the left or right in
the window.
Ver tical slider bar allows you to drag the view up or down in the
window.
Move Ar r owsdrag the data button on the title bar to move the window
to a new location on the screen.
Ver tical Ar r owsappear 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.
Hor izontal Ar r owsappear 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 Ar r owsappear 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.
Fo rm s
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.
130
Creating 3D Models
The Cr eate Dr awing form from the Dr awing Manager (PD_Dr aw) 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.
S e le c tin g Op tio n s
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 Confir m ( ).
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:
Retur n 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.
131
Creating 3D Models
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.
132
Creating 3D Models
Key-in Fields
Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark
gray. You can select a key-in field and key in a new value. A bar cursor appears in the active
key-in field. Key in your input and press <Return>. To change afield, reselect the field and key
in the desired information. Key-in fields have a maximum number of characters depending on
the item being defined.
Key-in fields that appear on forms built with Form Builder accept EMACS editing commands.
If you select a key-in field for a code-listed attribute, the system activates a form which lists the
code list values for the selected field.
Microstation requires lowercase characters for the file specification and path name of all
dlistesign files. Therefore, the system will automatically convert any input for the file
specification and path name of a design file (such as a model or drawing) to lowercase before
loading into the Project Control Database.
Display-list Boxes
A display-list box is located at the end of some key-in fields and lets you select data from a list
instead of keying in information. For example, there is a display list associated with the
Authorization key-in field shown. At the end of the field, there is a small box with horizontal
dashes. When you select this display list box with the screen cursor, an associated list of valid
input values displays. Select the desired item from the list to input its value into the field.
Shift Left and Shift Right buttons
At the bottom of some key-in and display fields, there are two buttons marked with arrows.
These buttons are called shift left and shift right buttons.
Often, you can key in more characters than a field display shows. Shift Left moves the text
display to the front of field; Shift Right moves the text display to the end of the field.
Toggle
A toggle field on a screen menu is used to select one of two possible choices, one of which is
always displayed. Place a data point on the toggle field to toggle between the two choices.
133
Creating 3D Models
Roll-Thr ough 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.
Standar d 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, the box of icons shown at right displays. You can manipulate form windows just
like any other workstation window.
The following list defines in order the available window icons.
Collapse/Restor e
Pop-to-bottom
Pop-to-top
Repaint
Modify/Resize
Restor e Size
Ba s e Fo rm
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.
134
Cancel any other forms. The base form should be the only form displayed. Move the form to
the desired location.
Creating 3D Models
Select the File Design command to save the active form location. All subsequent forms will
display in the saved location.
3D Seed Data
You can use the Pr oject Data Manager to modify seed information for the project seed files or
for a specified model. These options affect all of the project seed files and the project marker
file.
Select the option for the type of 3D data to be revised. The following report shows the delivered
settings for the 3D data.
Plant Coordinate System Definition
Plant Coordinate System Description :
Plant Coordinate System
Plant Coordinate System Monument :
Easting :
E 0 0" Plant
Northing :
N 0 0" Plant
Elevation :
El 0 0" Plant
Design Volume Coordinate System Definition
Design Volume
Coordinate System Description :
Design Volume
Coordinate System
Design Volume
Coordinate System Monument :
Monument in Design Volume Coordinate System :
Easting :
E 0 0" Plant
Northing :
N 0 0" Plant
Elevation :
El 0 0" Plant
135
Creating 3D Models
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
Orientation of Design Volume Coordinate System as clockwise Angular
Offset of Design Volume North from Plant North :
0.000000
Coordinate Label/Readout Descriptions
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
Dimensioning :
English
Coordinate Label
Prefix/Suffix
Match Line :
Match Line
Center Line :
CL
Top Of Steel :
TOS
Top of Concrete :
TOC
Battery Limit :
Battery Limit
Bottom of Pipe :
BOP
Invert Elevation :
Invert
Platform Elevation :
Face of Flange :
F/F
User Define 1 :
User Define 2 :
User Define 3 :
User Define 4 :
User Define 5 :
User Define 6 :
User Define 7 :
User Define 8 :
User Define 9 :
User Define 10 :
User Define 11 :
User Define 12 :
User Define 13 :
User Define 14 :
User Define 15 :
136
Creating 3D Models
User Define 16 :
User Define 17 :
User Define 18 :
User Define 19 :
User Define 20 :
Coordinate Label/Readout Format
Coordinate Label Formats :
10 East Plant
10 Plant East
East 10 Plant
(Active)
East Plant 10
Plant 10 East
Plant East 10
Label Description On
Coordinate Readout :
10 E Plant
10 Plant E
E 10 Plant
(Active)
E Plant 10
Plant 10 E
Plant E 10
Readout Description On
Coordinate Label/Readout
Units
Label Units : Master Units and Subunits
Readout Units :
Master Units and Subunits
Metric System of Units Label :
Subunits Only
Label Descritions :
Master Units Short Description :
137
Creating 3D Models
Text Font :
Coordinate Labels :
23
Witness Line and Terminator :
125
Symbol for Line Terminator :
42
Plot Gap Size :
0.250000
Line Spacing :
0
Angular Label/Readout
Angular Label Decimal Degrees Accuracy :
1 Decimal Place
Angular Readout Decimal Degrees Accuracy :
1 Decimal Place
Angular Input is Clockwise from North
Slope Readout Accuracy :
Number of Inches per Foot
138
Creating 3D Models
Place basic three-dimensional building blocks such as cylinders, cones and boxes called
primitives.
Create complex parametrics using the EDEN language and add them to the Reference
Database for future placement. Refer to the PDS Eden Interface Reference Guide for details.
Pr imitive
Par ametr ic
139
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.
Project
Data
Manager
Equipment Graphic
Symbology
Primitives/
Parametrics
Category
140
Level
Color
Weight
Symbology
Physical
10
Solid
Eqp Category 2
White
Solid
Eqp Category 3
White
Solid
Eqp Category 4
White
Solid
Eqp Category 5
White
Solid
Eqp Category 6
White
Solid
Eqp Category 7
White
Solid
Eqp Category 8
White
Solid
Creating 3D Models
Eqp Category 9
White
Solid
Eqp Category 10
White
Solid
Eqp Category 11
White
Solid
Eqp Category 12
White
Solid
Eqp Category 13
White
Solid
Eqp Category 14
White
Solid
Eqp Category 15
White
Solid
Eqp Category 16
White
Solid
Eqp Category 17
White
Solid
Eqp Category 18
White
Solid
Eqp Category 19
White
Solid
Eqp Category 20
White
Solid
Category
Level
Color
Weight
Symbology
Nozzle Category
Small
12
Solid
Nozzle Category
Medium
12
Solid
Nozzle Category
Large
12
Solid
Level
Color
Weight
Symbology
40
Solid
41
Solid
42
10
Solid
43
10
Solid
44
11
Solid
45
11
Solid
46
12
Solid
47
12
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)
Equipment Graphic
Symbology
Steel
Category
(continue
d)
Level
Color
Weight
Symbology
Ladders
20
White
Solid
Platforms
21
White
Solid
Handrails
22
White
Solid
Miscellaneous
Light Steel
166
23
White
Solid
Level
Color
Weight
Symbology
Dumb Category 1
30
White
Solid
Dumb Category 2
White
Solid
Dumb Category 3
White
Solid
141
Creating 3D Models
Dumb Category 4
White
Solid
Dumb Category 5
White
Solid
Dumb Category 6
White
Solid
Dumb Category 7
White
Solid
Dumb Category 8
White
Solid
Dumb Category 9
White
Solid
Dumb Category 10
White
Solid
Dumb Category 11
White
Solid
Dumb Category 12
White
Solid
Dumb Category 13
White
Solid
Dumb Category 14
White
Solid
Dumb Category 15
White
Solid
Level
Color
Weight
Symbology
Place Point
48
15
Solid
Datum Point
50
13
10
Solid
Hole Elements
15
White
Solid
2-D Shadows
12
Solid
Miscellaneous
Category
Semi Intelligent
Graphics
Category
Semi-Intelligent
Category
Semi-Ingelligent
Category
Semi-Intelligent
Category
Semi-Intelligent
Category
Semi-Intelligent
Category
Level
Color
Weight
Symbology
51
White
Solid
52
White
Solid
53
White
Solid
54
White
Solid
55
White
Solid
Project
Data
Manager
Nozzle
Default
Placement
Options
Nominal Piping
Diameter
System of Units
English
Small is <=
Large is
Table Name
>=
Define Table
Suffix by End Type
:
: 2IN
: 14IN
:
D036
: Bolted 5
Female 5
Male - 5
Project
Data
Manager
Equipment Reference Database
Management
167
PDS 3D Theory
April 2002
Graphic Commodity
Library
142
Creating 3D Models
Approved
wegl
Tutorial
Definition Library
Approved :
wegl
\win32app\i
ngr\pdeqp\d
at\
zi_eqpms.lib
\win32app\i
ngr\pdeqp\d
at\
zi_tutlib.lib
\win32app\i
ngr\rdusrdb
\
us_pcdim.l
\win32app\i
ngr\pdshell
\lib\
std_note.l
\win32app\i
ngr\rdusrdb
\
us_pjstb.l
\win32app\i
ngr\pdeqp\d
at\
equip.cel
Piping Physical
Data Library
Approved :
wegl
Cell library
Approved
wegl
Forms Directory
Location
Approved :
wegl
\win32app\i
ngr\pdeqp\
Project
Data
Manager
Interference Envelope
Emulation Data
: 1"
:
:
1"
1"
143
Creating 3D Models
1. At the Plant Design System form, select the Equipment Modeling option.
The system displays the Equipment Modeling form listing the available design area numbers
and their corresponding descriptions.
144
Creating 3D Models
Select the 3D design area to modify and click Confir m.
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 Confir m.
The primary axis originates at the active place point and is aligned with the equipment item
center line.
145
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 Refr esh Manipulation commands via the coordinate axis system.
The coordinate axis system display consists of a refresh line originating at the active place point
and pointing in one of six coordinate directions: North, East, Up, South, West and Down.
If the coordinate axis system display is turned on, the refresh tee appears at the active place point
when you select a secondary command such as Absolute PDS XYZ or Delta PDS XYZ.
You can confirm the direction of the active axis by viewing the status field. The system displays
the directional information using a few simple symbols.
**P-IN S-
146
-primary axis
- secondary axis
**
Creating 3D Models
-IN or - indicating the direction the active axis is pointing depending on the active view.
-OUT In a specified view (other than Iso), IN points away from you when looking at a model.
OUT points toward you when looking at a model. For example when looking at a north view, IN
points north (away from you) and OUT points south (toward you).
In the example above, the primary axis is the active axis and points IN toward the displayed
view. The secondary axis is only visible in the displayed view. Since the primary axis is active, it
can be rotated by a Refr esh 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).
It can be manipulated when the active point is defined using the ACTIVE POINT
command. After selecting this command, you can use any of the pocket menu options to
manipulate the tee. Angles of rotation cannot be entered with this command.
When placing equipment and components using a form or a parametric tutorial for
equipment or component generation and manipulation. Angles of rotation can be keyed in,
where positive angles are measured in the counterclockwise direction looking from the
direction where the non-rotating axis is pointing. To change the axis to be rotated, select the
CHANGE AXIS option.
147
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.
148
Creating 3D Models
Secondary Commands
These commands provide support for the primary commands. A Secondary Command will not
function unless a primary command is active. These commands are used to orient the screen
views, defines precision input, adjust the orientation of the refresh tee, or define the coordinate
system.
149
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.
150
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
BEND_DEFLECTION
COMMODITY_ITEM_NAME
PIPE_LENGTH
PIPE_RUN_LENGTH
WELD_TYPE_TABLE
PIPING
TUBE
(Automated Component)
Vicinity Tolerance
0.500000
: 4.000000
Project Data Manager
Piping Data Control
Commodity Name
: Off
On
151
Creating 3D Models
Branch Component Association for Isometric Drawings
Copy Option
Header
Append Prefix
Expanded
: IN
Project Data Manager
Physical Units Options
Insulation Density
Surface Area
lb/ft3
ft2
Dry/Wet Weights
lb
Maximum Temperature
(Spec) : degF
Project Data Manager
Nozzle Data Transfer List
Piping Commodity
: 2
Piping Specialty
: 2
Instrument
: 2
Piping/Tubing
Pipe Support
: 2
: 2
Model Symbology
Color
Simple
Model Category
Project Data Manager
Graphic Symbology
152
Small is
<=
2IN
Large is
>=
14IN
- Model Category
Level
Color
Piping Segment
Not Approved
Small
Blue
Piping Segment
Not Approved
Medium
11
Blue
Piping Segment
Not Approved
Large
21
Blue
Piping Segment
Approved
Small
31
Blue
Piping Segment
Approved
Medium
41
Blue
Piping Segment
Approved
Large
51
Blue
Piping/Tubing
Not Approved
Small
Green
Piping/Tubing
Not Approved
Medium
13
Green
Piping/Tubing
Not Approved
Large
23
Green
Piping/Tubing
Approved
Small
33
Green
Piping/Tubing
Approved
Medium
43
Green
Creating 3D Models
Piping/Tubing
Approved
Large
53
Green
Piping Commodity
Not Approved
Small
Green
Piping Commodity
Not Approved
Medium
12
Green
Piping Commodity
Not Approved
Large
22
Green
Piping Commodity
Approved
Small
32
Green
Piping Commodity
Approved
Medium
42
Green
Piping Commodity
Approved
Large
52
Green
Piping Specialty
Not Approved
Small
Orange
Piping Specialty
Not Approved
Medium
14
Orange
Piping Specialty
Not Approved
Large
24
Orange
Piping Specialty
Approved
Small
34
Orange
Piping Specialty
Approved
Medium
44
Orange
Piping Specialty
Approved
Large
54
Orange
Instrument
Not Approved
Small
Orange
Instrument
Not Approved
Medium
15
Orange
Instrument
Not Approved
Large
25
Orange
Instrument
Approved
Small
35
Orange
Instrument
Approved
Medium
45
Orange
Instrument
Approved
Large
55
Orange
Pipe Support
- Logical
Not Approved
N/A
Violet
Pipe Support
- Physical
Not Approved
N/A
10
White
Pipe Support
- Logical
Approved
N/A
37
Violet
Pipe Support
- Physical
Approved
N/A
40
White
Miscellaneous Graphics
58
Red
Diagnostic Markers
59
Red
62
Red
63
Red
Diagnostic Markers
: 2
: 2
: 2
: 2
: 125
: 6"
: 6"
:
Project Data Manager
Material Takeoff Options
153
Creating 3D Models
Commodity Code
Size Independent
Length Calculation
Almost Precise
English
Off
: Off
: 6Q3C95
: 6Q3C97
: 6Q3C98
BOLT_DATA
:
:
FLANGE_DATA_MTO
BOLT_LENGTH
Undefined
<125,0>
Undefined
<220,0>
Undefined
<1064,0>
Undefined
<1056,0>
Undefined
<1064,0>
Undefined
<1056,0>
unit_code
line_sequence_no
nominal_piping_dia
100-3/4IN
piping_mater_class
154
insulation_purpose
insulation_thick
nor_oper_pres
0.000
nor_op_pres_units
nor_oper_temp
0.000
nor_op_temp_units
nor_dgn_pres
0.000
nor_dgn_pres_units
nor_dgn_temp
0.000
nor_dgn_temp_units
insulation_density
heat_tracing_reqmt
Undefined
<200,0>
heat_tracing_media
Undefined
<210,0>
heat_tracing_temp
design_resp
Undefined
<160,0>
0"
lb/ft3
degF
Creating 3D Models
supply_resp
Undefined
<160,0>
construction_resp
Undefined
<160,0>
construction_stat
Undefined
<130,0>
hold_status
Undefined
<50,0>
Undefined
<1064,0>
Undefined
<1056,0>
Undefined
<1064,0>
Undefined
<1056,0>
design_area_number
alt_oper_pres
0.000
alt_op_pres_units
alt_oper_temp
0.000
alt_op_temp_units
alt_dgn_pres
0.000
alt_dgn_pres_units
alt_dgn_temp
0.000
alt_dgn_temp_units
steam_outlet_temp
0.000
steam_temp_units
Standard Note
Number is Undefined
<1056,0>
safety_class
Standard Note
Number is Undefined
<340,0>
design_standard
Standard Note
Number is Undefined
<570,0>
coating_reqmts
Standard Note
Number is Undefined
<190,0>
cleaning_reqmts
Standard Note
Number is Undefined
<230,0>
train_number
mater_of_construct
fluid_category
package_system_no
Project Data Manager
Default Segment Parameters
(continued)
module_no
specific_gravity_a
0.000
specific_gravity_b
0.000
specific_gravity_c
0.000
viscosity
0.000
density
0.000
spec_heat_ratio
0.000
sonic_velocity
0.000
surface_roughness
0.000
test_system_no
test_fluid
Standard Note
test_pressure
0.000
Number is Undefined
<125,0>
schedule_override
Project Data Manager
Design Consistency Checks
155
Creating 3D Models
Data
Flow Direction
Flow Centerline
Hard Check
:
Hard Check
Outside Diameter :
No
Check
Schedule/Thickness :
No
Check
Piping Materials Class :
Soft Check
Materials of Construction Class
Insulation Thickness :
Soft Check
Insulation Purpose :
Tolerances
Soft Check
Soft Check
0.500000
Insulation Thickness
1/4"
:
:
156
Creating 3D Models
LMFE LMLFE
FFLFE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG
RFLFE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG
RJLFE RJFE RJLFE RJTBE MRJTBEWG
STLFE SGFE SGLFE
LTLFE LGFE LGLFE
SMLFE SFFE SFLFE
LMLFE LFFE LFLFE
SGLFE STFE STLFE
Project Data Manager
End Prep Compatibilities
Bolted End Preps
LGLFE LTFE LTLFE FFTBCSEWG
SFLFE SMFE SMLFE
LFLFE LMFE LMLFE
FFTBE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSE
FFTBEWG FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG FFTBCSEWG
RFTBE FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSE
RFTBEWG FFFE FFFEWG RFFE RFFEWG FFLFE RFLFE FFTBE FFTBEWG RFTBE RFTBEWG RFTBCSEWG
RJTBE RJFE RJLFE RJTBE MRJTBEWG RJTBCSE
MRJTBEWG RJFE RJLFE RJTBE
FFTBCSE FFFE FFFEWG FFTBE
FFTBCSEWG -
157
Creating 3D Models
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
Project Data Manager
End Prep Compatibilities
Male End Preps
BE BE TBE PE SE SWE HCE
TBE BE TBE PE SWE HCE
MFE MFE
MTE FTE
MGE FGE
MQCE FQCE
MFRE FFRE
MHE FHE
SPE BLE
158
Creating 3D Models
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
wegl
..\win32app\ingr\rdusrdb\
us_pjstb.l
..\win32app\ingr\rdusrdb\
us_shbom.l
..\win32app\ingr\rdusrdb\
us_lgbom.l
..\win32app\ingr\rdusrdb\
us_spbom.l
..\win32app\ingr\pdshell\lib\
std_note.l
..\win32app\ingr\pdshell\lib\
labels.l
..\win32app\ingr\pdshell\lib\
assembly.l
wegl
wegl
wegl
wegl
wegl
wegl
wegl
Approved
pip_gcom.l
..\win32app\ingr\rdusrdb\
us_pcdim.l
- U.S. Practice
wegl
..\win32app\ingr\pdshell\lib\
- DIN
- British Standard
159
Creating 3D Models
Approved
- International A
- Australian
- JIS
- European B
- European A
- International B
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.
P ip in g S e g m e n ts
The centerline routing within a model is represented by geographically connected piping
segments. A piping segment defines the geometry of the pipeline and contains the non- graphical
data associated with that pipeline. A single piping segment can define changes of direction, but
an additional segment is created at a branch point or an attribute break, such as a size change or a
spec break.
The following illustrates the terminology associated with a piping segment.
160
Creating 3D Models
A pipeline consists of a set of graphically connected piping segments including all the branches.
Ac tive P la c e m e n t P o in t
The term active placement point refers to the coordinate location used by the Place Component
command. It defines the point at which piping and instrumentation are placed. You can use
Connect to Design to place a piping or instrument component at an existing, intelligent location
in the model, such as a piping or instrumentation connect point, a nozzle, or a piping segment.
The system uses the orientation tee to indicate the location of the Active Placement Point.
Co o rd in a te S ys te m In d ic a to r a n d Orie n ta tio n Te e Co o rd in a te
S ys te m In d ic a to r
The coordinate system indicator is a temporary display symbol which represents the six
orthogonal directions (North, South, East, West, Up, and Down) of the coordinate system.
Piping Designer uses the coordinate system indicator to indicate the active coordinate location
when
161
Creating 3D Models
Orientation Tee
The orientation tee is a temporary display symbol which enables you to orient a component
before placement. The orientation tee is composed of two lines:
a secondary axis used to orient components which are not symmetrical about the flow
centerline (for example, a valve with an operator).
When the Place Component command is active, the system displays the orientation tee at the
Active Placement Point and displays related information in the screen message fields.
P **S-OUT
The stars (**) indicate the active axis of rotation (the secondary in the above message). When
either axis is rotated such that its orientation is not in the plane of the view, the suffix IN or OUT
is displayed next to P (primary) or S (secondary) indicating whether that axis is pointing in or
out of that view. For example, when the secondary axis is perpendicular to the screen and
oriented toward the designer, the message P S-OUT is displayed.
When placing a component with the orientation tee, you can adjust the orientation by pressing
<R> or selecting one of the Orientation Control commands.
162
Creating 3D Models
P ip in g Co n n e c t P o in ts
Each component has a center and at least one connect point or pressurized end. A connect point
is usually an end of a piping component to which another component or pipe (with compatible
properties) is connected. The connect point stores the description of the component at that end. It
indicates the flow centerline orientation, and properties such as diameter, end preparation
(flanged, welded,...), and rating.
The following rules (in order of priority) are used to determine the assignment of connect point
numbers:
1. Connect Point 1 is always at the larger end (NPD).
2. If the ends have the same NPD, but different end preparations, then Connect Point 1 is
assigned an end preparation in the following precedence: Bolted, Male, Female.
Refer to the PDS Piping Component Data Reference Guide for a detailed explanation of connect
point assignments.
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.
The Copy Piping, Copy and Mir r or 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.
163
Creating 3D Models
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 Suppor t command by connecting to previously
placed, approved piping.
Place new pipe supports in the Place Logical Suppor t 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.
164
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.
165
Creating 3D Models
166
SECTION 6
Update segment data. You can transfer segment data from the P&ID to update the active
segment data, to define line attributes while sketching, or to revise a segment attribute or set
of attributes.
Review component names. You can select a component on the P&ID to define the
commodity item to be placed.
Compar e data. You can compare data in the model against data in the P&ID to verify that
all the information is in agreement.
Gr aphical inter face. The easiest way to transfer or review data is to use the graphical data
transfer options. This allows you to display the P&ID drawing in a view while working in
the model and select items directly from the drawing graphics.
PDS also supports transfer by line ID or by identifying an equipment nozzle as the start of a
pipeline.
In This Section
Database Requirements .................................................................. 167
P&ID Correlation Table ................................................................. 168
P&ID Graphical Data Transfer Setup ............................................ 174
P&ID Node Numbers ..................................................................... 176
Update Segment Data from P&ID ................................................. 177
P&ID Data ...................................................................................... 179
Name From P&ID .......................................................................... 180
P&ID Data Comparison Options.................................................... 180
167
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.
Pr opagated Dr awings
Only those P&ID drawings which have been successfully propagated can be referenced for
P&ID to Piping data transfer.
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
168
1
3
module_no
79
package_system_no
81
train_number
23
fluid_code
line_sequence_no
nominal_piping_dia
22
1
0
1
1
2
4
1
5
1
6
2
5
2
6
npd_units -1
piping_mater_class
insulation_purpose
1
2
1
4
insulation_thick
15
28
insulation_thick_units
-1
29
insulation_density
16
30
insulation_density_units
-1
31
heat_tracing_reqmt
17
heat_tracing_media
heat_tracing_temp
73
18
74
19
75
heat_tracing_temp_units
-1
76
construction_stat
20
60
hold_status
21
83
schedule_override
23
66
nor_oper_pres
24
39
nor_oper_temp
25
41
alt_oper_pres
26
43
alt_oper_temp
27
45
nor_dgn_pres
28
47
nor_dgn_temp
29
49
alt_dgn_pres
30
51
alt_dgn_temp
31
53
steam_outlet_temp
32
86
mater_of_construct
33
61
safety_class
34
59
design_resp
37
69
construction_resp
38
78
supply_resp
39
71
coating_reqmts
40
72
77
cleaning_reqmts
41
fluid_category
42
84
nor_op_pres_units
43
40
169
44
42
alt_op_pres_units
45
44
alt_op_temp_units
46
46
nor_dgn_pres_units
47
48
nor_dgn_temp_units
48
50
alt_dgn_pres_units
49
52
alt_dgn_temp_units
50
54
steam_temp_units
51
87
test_system_no
64
55
test_fluid
65
56
test_pressure
66
57
# upstrm_node_no
pid_node_number_a
10
pid_node_number_b
11
flow_direction
14
21
drawing_segment_index_no
line_id
12
# dwnstrm_node_no
# line_no_label
line_number_label
# dwg_occ_no
# piping_thk_flag
piping_thickness_flag
Equipment Table
Database:
-
equipment_number
### Data extracted from the
68
( eq_group,
nozzle_number
106
( eq_nozz,
108
) of the
# 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:
170
aabbcc_code
commodity_code_flag
28
cmdty_code
29
27
# pid_seg_occ_no
comp_segment_index_no
# dwg_occ_no
comp_drawing_index_no
# generic_tag_no
specialty_generic_tag_no
here.
44
#attribute name
NOTE:
(any thing)
const_status
piping attr no
attr no
p&id
3
2
heat_tracing_media
23
35
3
4
3
3
ht_tracing_media_temp
3
6
opening_action
3
1
remarks
4
6
### Data extracted from the Instrument Component Table
34
heat_tracing_reqmts
33
hold_status
41
35
17
20
( instr_comp,
131
10
# pid_seg_occ_no
instr_segment_index_no
# aabbcc_code
instr_aabbcc_code
# dwg_occ_no
instr_drawing_index_no
#generic_tag_no
instr_generic_tag_no
#any attributes you desire to transfer
#
here.
80
171
#attribute name
NOTE:
Complete,
(any thing)
cleaning_reqmts
piping
39
p&id attr no
35
29
24
dgn_resp 31
25
fail_action_1
28
56
heat_tracing_media
34
28
heat_tracing_reqmts
33
27
hold_status
30
40
ht_tracing_media_temp
35
29
insulation_purpose
36
31
insulation_thick
37
33
module_no 41
package_system_no
no
60
const_resp 32
const_status
attr
36
42
38
remark_2 52
22
safety_classification
40
the
20
Drawing
drawing_number
Table
( dwg,
unit_index_number
drawing_title
16
network_address
path_name
file_specification
propagation_status
10
approval_initials
21
approval_date
22
revision_id
27
for_comments_date
29
for_design_date
30
for_construct_date
31
#unit_occ_no
task_name
### Data extracted from
the
Unit Table
unit_number
unit_name
172
unit_code -
( task_rdb,
98
pid_task_name
pid_task_rdb_node
pid_task_rdb_path
( pid_seg,
piping_segment_index_no
110
### Data extracted from the PID Drawing Revision Data Table
###
103
) of the P&ID
( dwg_rev_data,
dwg_occ_no
(piping_connector,
124) of
#matching_criteria is the criteria to be used for matching the P&ID and Piping
#segments together.
Nodea
(piping attribute
(piping attribute
68)
67
68
The default
#is
END which
FIRST
#is found, the software evaluates all of the matches for an exact match of the
#transfer data.
search_mode FIRST
#exclusion_criteria has been a part of the submission process in the past.
#have added the capability to default this value.
#check the transfer disabled segments and
#segments.
Values are
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.
174
Select P&I Dr awing 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 Dr awing 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.
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
Transferring piping segment data from the P&ID Database by any means results in the P&ID
node numbers being stored with the piping segment that is to be created by either the Place
Component or Sketch command.
If you continue creating new piping segments in the model, either by explicitly placing a
piping segment or by placing a component that results in the placement of a piping segment,
the new piping segments continue to include the P&ID node numbers from the initial piping
segment.
If, at any time, you update the piping segment data manually with the Active Segment Data
option, the P&ID node numbers for the subsequent piping segment is assigned as undefined
(blank).
Using the Fir st Size or Second Size option to place a reducing component will not result in
the P&ID node numbers being assigned as undefined unless you also use the Active
Segment Data option.
176
If you place a component after specifying the active placement point with the Connect to
Design option, the P&ID node numbers for the subsequent piping segment is derived from
those of the connected piping.
The P&ID node numbers are assigned as undefined when you connect to a nozzle, unless the
active segment data is then updated from the P&ID Database.
If you place a component after specifying the active placement point with the Point in
Space option, the P&ID node numbers for the subsequent piping segment is assigned as
undefined (blank).
If, in the Sketch command, you place a piping segment after specifying the active placement
point with the Constr uct Point option, the P&ID node numbers for the subsequent piping
segment are assigned as undefined (blank).
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 Attr ibutes
You can update the data for a previously placed piping segment using the Revise Attr ibutes
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.
Attr ibute Br eak
You can load the piping segment data for an attribute break, using the Attr ibute Br eak
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
the ability to mark a piping segment to have segment data comparisons inhibited (or
enabled) in the P&ID Data Comparison Report. This option is intended to assist the user by
not reporting extraneous piping segments which do not exist in the P&ID Database and have
not been assigned P&ID node numbers in the piping model, i.e. segment data has not been
transferred from the P&ID database. Note that the default mode for all piping segments
created in the model is to have P&ID data comparisons enabled. Thus it is not necessary for
the user to take any action to enable P&ID data comparisons, unless the user had previously
and inadvertently designated that P&ID data comparisons be inhibited for a particular piping
segment.
181
182
SECTION 7
183
184
SECTION 8
185
186
SECTION 9
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.
The software versions supported for SmartPlant P&ID to Piping Data Transfer are:
SmartPlant P&ID plant database in Oracle 9.2 or 10g. You can also use Microsoft SQL
Server 2000 Service Pack 3a.
SmartPlant P&ID server with Windows XP with Service Pack 2
We recommend that you always start with a fresh installation of Windows XP with Service Pack
2. If you must use a computer that already has Windows installed, we recommend that you:
1. Remove any SmartPlant P&ID entries such as Intergraph SmartPlant Attribute Mapper,
Intergraph SmartPlant P&ID WorkStation, and SmartPlant Engineering Manager that appear
in Add/Remove Pr ogr ams.
2. Remove PD_Shell and restart your computer. Then verify that the PDSHELL directory and
and all the PDS entries in the registry are deleted.
3. Run a registry cleaning utility.
4. If your computer is running Windows XP, install Windows XP Service Pack 2.
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, at
http://ppocrm.intergraph.com/ecustomer/start.swe?SWECmd= Login
(https://crmweb.intergraph.com/ecustomer_enu/start.swe?SWECmd=Start&SWEHo=crmweb.in
tergraph.com).
Install Oracle
1. Start Oracle Database Configuration Assistant, select the Local Net Ser vice Name
configur ation option from the list, and click Next.
2. Click Add, and then click Next.
3. Select the Oracle database version that you want to access.
4. In the Ser vice Name box, type the oracle SID name of the SmartPlant database. Click Next.
5. In the protocol form, accept the default TCP option. Click Next.
6. In the Host Name box, type the P&ID site server name. Accept the default port number
1521. Click Next.
7. Click Yes to perform the test, and then click Next.
8. 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.
187
The Oracle Net8 configuration for a new database alias might be different from one Oracle
version to another. Refer to the proper Oracle documentation for further details on a specific
Oracle version.
For Oracle 9i configuration, you can refer to the cheat sheet on the Siebel e- customer web
site at http://ppocrm.intergraph.com/ecustomer/start.swe?SWECmd= Login
(https://crmweb.intergraph.com/ecustomer_enu/start.swe?SWECmd=Start&SWEHo=crmwe
b.intergraph.com). Look for "Technical Tips for PDS System and Project Setup Issues" on
the PDS 3D Product Information page.
Installation Guide.
10. Accept the default Pr ogr am Folder s or select a new Pr ogr am Folder name, then click
Next.
11. Review your Cur r ent Settings, then click Next to install SmartPlant Engineering Manager.
12. Click Finish to close the installation wizard.
188
If you are reinstalling SmartPlant Engineering Manager, you must first use the Add/Remove
Pr og rams Control Panel application to remove the previous SmartPlant Engineering
Manager installation.
Be sure to apply all available SmartPlant Engineering Manager service packs for the version
you are installing. For more information, please contact Intergraph Customer Support.
If you need to install SmartSketch on the same computer, be sure to install it first. If you
require SmartSketch for PDS 7.3 (for example, for the pipe support explorer), SmartSketch
4.0 is the compatible version.
For more information on full installation of SmartPlant Engineering Manager, see The
SmartPlant P&ID Installation Guide.
Click Star t > Pr ogr ams > Inter graph Smar tPlant P&ID > Dr awing Manager .
Click File > Open Database.
Click Site Ser ver s and browse to a SmartPlant initialization (.ini) file.
Select the file and click OK.
Select the plant structure in the Open Plant Str uctur e dialog box.
Click Open, and the selected plant with its drawings appears in the Drawing Manager view.
If you experience problems connecting to the SmartPlant P&ID site or getting into the
plant structure, verify that the site server is running and ask the SmartPlant P&ID administrator
Plant Design System 3D Theory
189
190
SECTION 10
191
192
Use the Data fr om P&ID command often while routing new piping in PDS.
When creating a pipeline by copying existing piping, use the Revise Attr ibute > Update
fr om 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 Attr ibute > Update fr om
P&ID command to load the data from SmartPlant P&ID.
If a branch is not shown on the P&ID for example, drains and small bore lines then make
sure that pid_id_part_a and pid_id_part_b are completed to match those options for the
Plant Design System 3D Theory
The matching criteria defined in the pid_to_piping file in the plant directory. For more
information, see Map an Ignored Attribute (on page 198) or Map an Unmapped Attribute
(on page 198).
The Compar e Segment with Node Number s/Compar e All Segments setting.
While running this report, the Compar e All Segments setting should be used, and matching
criteria should be node numbers.
Based on the availability of P&IDs during the initial piping design stage, the number of
discrepancies can be very high on the first run. Our experience shows that a piping designer,
who has good knowledge of the piping involved and the related P&ID, takes approximately two
to four minutes to resolve a discrepancy. Successive uses of this procedure should reduce the
numbers of discrepancies. If plant design resources or time do not allow resolving all
discrepancies, then you should consider alternative methods to running the Segment Data
Comparison Report.
One alternative is to change the matching criteria. Matching criteria directs the software to
establish associations between SmartPlant P&ID and PDS piping segments based on the value of
the attributes specified. For example, the default criteria of node numbers means that node
numbers for a PDS piping segment must match with a P&ID segment. If the SmartPlant P&ID to
PDS Piping Data Transfer has not been done for a piping segment, then no node number is
defined for that segment. This situation generates a Node Number s Undefined only
discrepancy. If the majority of the piping falls under this category, then the number of
discrepancies can be very high. To reduce this number, change the matching criteria to
something other than node numbers. Typically, any of the individual properties of a line number
193
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.
194
For more information about mapping attributes, see Map an Unmapped Attribute (on page
198) or Map an Ignored Attribute (on page 198).
195
196
SECTION 11
Mapping Attributes
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,
Ignor ed, and All. For SmartPlant P&ID to PDS 3D data transfer, the Ignor ed map status is the
same as the Unmapped status.
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.
197
Properties mapped with the Tr ansfer Mode option set to Par tial are transferred when you
use the Par tial Data Tr ansfer toggle within PDS.
Properties mapped with the Tr ansfer Mode option set to Default receive the default value,
which you enter in the Default box, during partial data transfer.
Properties mapped with the Tr ansfer Mode option set to No Default do not get a default
value and do not get transferred during partial data transfer.
198
Properties mapped with the Tr ansfer Mode option set to Par tial are transferred when you
use the Par tial Data Tr ansfer toggle within PDS.
Properties mapped with the Tr ansfer Mode option set to Default receive the default value,
which you enter in the Default box, during partial data transfer.
Properties mapped with the Tr ansfer Mode option set to No Default do not get a default
value and do not get transferred during partial data transfer.
SECTION 12
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 Compar ison Repor t command.)
A non-printable, sorted file named model_number .pca (This file is used by the P&ID Data
Compar ison, Update Model, Segment Data Compar ison Repor t, and Review P&ID
Compar ison Repor t commands for the approval of data discrepancies. The .pca file is
initially created when you approve a discrepancy, and the file is appended to with each
additional approval.)
You can format the title page and the heading for each page of the Segment Data Comparison
Report using the \win32app\ingr\pddesign\sample\pid_cmprpt.fmt format file. The remainder of
the report is in the following format:
199
Attribute
Value in Model
Value in P&ID
line_number_label
2"A-A5A2F-N55011
2"A-A5A2F-P550107
line_sequence_no
550111
550107
insulation_purpose
N
P
Data in the Segment Data Comparison Report is sorted first by line number label and then by the
SmartPlant P&ID node numbers, if applicable.
200
SECTION 13
SmartPlant P&ID
Consider the following points when planning for data transfer from a SmartPlant P&ID plant to
a PDS 3D project.
Symbol Pr oper ties 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.
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 Refer ence File > Use Color Table setting under User > User
Pr efer ences > Refer ence File in PDS. This action displays the drawing using the active
color scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID.
Method 2: Change the Background color of the piping model to a light color by using
Settings > Color s.
201
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.
Layer s and Dr awing Filter s 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
202
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 Attr ibutes 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.
SECTION 14
203
204
SECTION 15
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.
205
206
Because SmartPlant databases are unit-dependent and PDS databases are design areadependent, one PDS piping design area can include data from different SmartPlant units.
Consequently, you must specify the correct unit number in the active segment data prior to
requesting a list of P&IDs from a SmartPlant database.
SECTION 16
207
208
SECTION 17
209
210
SECTION 18
211
212
SECTION 19
213
214
SECTION 20
215
216
SECTION 21
217
218
SECTION 22
219
220
SECTION 23
The named components in the piping design database are included and are compared on the
basis of the following data:
Tagged piping commodities are compared on the basis of their piping component
number
Piping specialties are compared on the basis of their piping component number
Inline instruments are compared on the basis of their instrument component number
Tagged piping commodities in the SmartPlant database that have the following data are
included:
The Commodity Code flag is set to by system or by user and the commodity code is
defined
Piping specialties in the SmartPlant database are determined by those piping components
that have the following data:
Only those instruments that are applicable to the PDS 3D model, such as those requiring
dimension definition in the RDB, as determined by an Instrument Correlation List
221
You can format the title page and the heading for each page of the Named Component Existence
report using the win32app\ingr\pddesign\sample\pid_cmprpt.fmt file. The remainder of the
report contains the following sections:
222
The list of line IDs that determine the basis for the report
Named components in the SmartPlant database, that are not in the PDS 3D model, are
reported with the component number and the drawing number
Named components in the PDS 3D model that are not in the SmartPlant database are
reported with the component number, the design area number, and the model number
SECTION 24
Appendix A: Troubleshooting
Some common difficulties that you may encounter are listed here, along with possible solutions.
MapPathName is the complete UNC path to the SmartPlant P&ID plant SPMap.mdb file
Save changes made to the SPMap.mdb file, and run the SP PID to PDS 3D command again.
If a client computer experiences problems connecting to the project, remove the
Intergraph SmartPlant Attribute Mapper and Intergraph SmartPlant P&ID Automation
components using Add/Remove Pr ogr ams. Restart the computer and reinstall PD_Shell and
SmartPlant P&ID Integration Tools using the silent installation. Be aware that for PDS users to
set up the attribute map and perform data transfer, they must have permission to access the
SmartPlant server through SmartPlant Engineering Manager.
Display
Start PD_Shell, and go to piping. Inside the PDS piping model but before using the Gr aphical
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 Refer ence File > Use Color Table setting under User > User
Pr efer ences > Refer ence 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 > Color s.
Temperature/Pressure Units
Select lines for piperun and component data for the Name fr om P&ID option. For Pipeline data,
four sets of temperature/pressure values with units must be set in the SmartPlant P&ID or you
223
\Program Files\SmartPlant
If you need to remove the components for the silent installation and have SmartSketch on the
computer, remove SmartSketch and its associated components first. Continue by removing
PD_Shell from the PDS r emove pr oduct utilities. This action prompts you to confirm deletion
of the Intergraph SmartPlant Attribute Mapper. Select Yes, and confirm the deletion of all shared
files.
This step does not delete Intergraph SmartPlant P&ID Automation. To remove
automation, go to Add/Remove Pr ogr ams, select Inter graph SPP&ID Automation from the
list, accept its deletion, and confirm deletion of all shared files. Then restart your computer.
Before re-installing any software in the client computer, delete the three folders specified above,
and any files contained in them.
224
The Gr aphical 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 fr om 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 Gr aphics 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-alwayspresent MicroStation font and causes unreadable labels on the screen.
225
226
SECTION 25
Software setup
Clash detection
The second section is a review of project organization and the different units into which a
plant/project can be broken for ease of manipulation.
The third section describes how to set up a system to support interference detection.
The fourth and final section is a general description of interference envelopes, the various types
of interferences (clashes) and what happens during interference detection and management.
In This Section
Interference Checking Process Overview ...................................... 227
Project Organization ...................................................................... 229
Setting Up a System to Support Interference Detection ................ 235
Understanding Interference Envelopes .......................................... 236
To disable interference checking between certain disciplines, use the Intr a Discipline
Inter fer ence Check toggle when defining the Discipline data.
227
The construction tolerance, the necessary space allocated beyond that which is necessary
for the component and its insulation, for each discipline is defined with the
Constr uction Toler ance form.
The action discipline is used to assign responsibility for a clash to a certain discipline.
The action discipline is defined using the Select Action Discipline option on the
Inter fer ence Check Data form.
The defined action discipline appears on plots and in the Action Discipline: field on the
Inter fer ence Manager form in the Inter fer ence Checker /Manager module.
HVAC =4
Architecture = 6
11. The Interference Report is created during the interference detection process and is named
after the project or design area, depending on the option selected for interference detection,
with an .int file extension. It contains only the unapproved clashes for that run.
Tr acking and Managing:
12. Edit and review existing clashes, manipulate views, and approve exisiting clashes with the
Inter fer ence Manager option. This option displays and highlights clashes within a graphics
environment, which can then be reviewed, edited or approved.
13. For unsuspected clashes, review envelopes in question using the Envelope Diagnostics
command. This command generates a report with a .evd file extension. For example, this
report contains instances such as when two or more groups of sub-components are contained
within one component but are not geometrically connected, in other words do not have
overlapping ranges.
14. Clashes can be plotted any time after interference detection using the Inter fer ence Plot
Manager option.
15. Aside from the Interferences Report, which is automatically generated during interference
detection with the Inter fer ence Checker option, reporting on the Project Control Data is
done using the Inter fer ence Repor t Manager . Discrimination data and format files are
used to generate specific types of reports. This sort of report might include a list of clashes
involving the structural discipline, the approval status of those clashes, and the action
discipline assigned to these clashes.
Project Organization
As discussed in Chapter 1, PDS uses the following organization to break the plant into smaller
units that can be handled more easily.
A project is a convenient grouping of all of the items that constitute a plant. The project is the
fundamental structure for working in PDS. The project constitutes the entire volume of the
project.
A design area represents a specified volume or logical area of the project for a specific
discipline. Design areas can be used to break up the project into smaller areas for interference
checking or reporting. This speeds up processing when only a portion of the project has changed.
The models or model components that are not within the area/volume will not be checked.
A design area pre-defined volume represents a pre-defined volume of the project for a specific
discipline. The volume is defined by using the Pr oject Envir onment Manager . Make sure that
the pre-defined volume encompasses all the models that you want to be checked. The models or
229
P ro je c t
This option on the Inter fer ence 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 Pr oject option.
230
P ip in g De s ig n Are a a n d De s ig n Are a
These options display a list of design areas for the specified discipline that are available for clash
checking. After a design area has been selected, the system defines a volume that encompasses
all models within the selected design area. It then performs an interference check on all models
and parts of models, including models from all other disciplines, that are in the defined volume.
To specify a smaller volume for a single interference check, set the Volume Filter toggle to On
after selecting a design area.
The dotted rectangle signifies the volume that is processed using the Design Ar ea option. The
name of the selected design area is DesA1.
231
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.
Vo lu m e Filte r
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.
232
233
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.
234
Marker files are used by the software to place graphic markers for clashes that are
detected during interference checking.
235
If the envelope file which corresponds to the model is Up-To-Date with respect to the model,
the envelope builder will not re-create the envelope file.
If the envelope file which corresponds to the model is Not-Up-To-Date with respect to the
model, but it has interference envelopes in the volume of the selected design area, then the
envelope file for the model is re-created.
If the envelope file which corresponds to the model is Not-Up-To-Date with respect to the
model and it does not have any interference envelopes which fall within the volume of the
selected design area, then the envelope builder determines if the model has any components
which falls in the volume of the selected design area. If so, the envelope file for that model is
re-created.
Log files are batch queue error reports for the envelope builder data server that contain
information regarding any errors. These files have the extension .ebl and are created in the
\temp directory on the server or workstation from which the process was submitted. You
should review this file.
Envelope Verification
The Envelope Ver ification 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.
236
The Pr oject option is the largest area of the project and encompasses every model file.
The Design Ar ea options process a smaller division of a project with a limited number of
model files.
The Pr e-Defined Volume option allows you to control the volume checked by specifying
specific volume coordinates. If not used, the system determines the volume based on the
volume of the envelope files in the area being checked (which can vary over the life of a
project).
The Volume Filter toggle specifies a smaller volume of any of the options above.
Once the Inter fer ence Checker has been run, you can review the clashes interactively with the
Interference Manager.
The Piping Designer provides a command to check interferences interactively while
working in the piping design file. This option only checks one pipeline (or a group) against
reference files that have a previously created envelope file. Unlike the Interference Checker, the
Piping Design command does not write clash information to the database. It is intended as a
quick check for the piping designer.
In te rfe re n c e Ch e c ke r In p u t
The following are used as input by the PDS Interference Checker:
Information in the Project Control Database. The approval status of each known interference
is stored in the Project Control Database. When an interference is approved, it is no longer
included in future interference reports. This allows all interferences within a project to be
resolved, either by changing the approval status of the interference to Approved or by
revising the model.
Information in the Material Reference Database. The following database tables can be used
to exclude items from interference checking.
The Flange Insulation Exclusion Data table (PD_table 232) provides for partial
exclusion of flange insulation thickness from the generation of interference envelopes.
This is an optional data table; if no data is defined for this table the insulation thickness
is completely included in the component's interference envelope.
237
In te rfe re n c e Ch e c ke r Ou tp u t
The following are generated by running the Interference Checker:
PDS Inter fer ence Report. This report contains all unapproved clashes, sorted first by
model combinations then by the type of clash. For instance, all clashes detected between
model A and model B are grouped together. A synopsis of the clashes is included at the
beginning of the report. This report also includes the model status of any components
involved in a clash for the piping, structural, HVAC, and equipment disciplines. This status
is that of the model and not of the clash.
These reports are named after the project or design area with an .int file extension and are
created each time the checker is run. The interference report is created at the location
specified with the Inter fer ence Repor t Management Data option. The report begins with a
synopsis of all clashes found during interference processing and includes a report of the
clashing items within each of the design files represented in the synopsis.
PDS Interference Synopsis
mbpip2
.env
Number of clashes
14
Date:
Model
PDS
Interference
Report
23-Jun-93
Time:
13:42:13
X Coord
Y Coord
Z Coord
mbpip2
No
48
2CPINSTRUMENT
meblabels-6IN-1C0031-0
Hard/Hard
Clashes
Row
6
4194305
E 1 3
15/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
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
"
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
238
2CPSPECIALTY
"
Not approved
50
PIPE
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
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"
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
"
Not approved
54
PIPE
ifcclash pipe-1IN-1C0031-0
"
Not approved
55
PIPE
ifcclash pipe-1IN-1C0031-0
"
Not approved
55
CKS
1construct-6IN-1C0031-0
"
Not approved
Inter fer ence Mar ker s. All interferences within the project are graphically represented by
markers and are used by the Inter fer ence 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.
239
Er r o r 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 Inter fer ence 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.
Pr oject Contr ol Database Recor ds. The following tables are updated by Interference
Checking:
Clash Management Data (131). A record is created each time Interference Checking is
run.
Inter fer ence Clash Data Per Pr oject (132). A record is created for each clash in the
project. The unique_clash_id uniquely identifies a clash.
Inter fer ence Clash Data Per J ob (133). A record is created each time a clash is
encountered.
Component Clash Data Per Pr oject (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.
In te rfe re n c e Ma n a g e r
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.
Cla s h Ca te g o rie s
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.
240
Har d. 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.
Constr uction. 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.
Cla s h P re c e d e n c e
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.
Ha rd - Ha rd Exa m p le
The following example contains clashes between actual physical components. It would be
categorized as a Hard - Hard clash.
241
Ha rd - S o ft Exa m ple
The following example displays a clash between an actual component and space that has been
allocated for maintenance accessways. It would be categorized as a Hard - Soft clash.
The Inter fer ence Clash Plot Management option defines a default node and path for future
clash plot files.
This is a required step in the Interference Checking Process. Problems could occur
later in the process if this step has not been completed.
242
243
244
SECTION 26
Reporting Process
The following outlines the basic steps associated with the Material Take-Off process.
1. Pre-defined report data determines the discrimination data (such as which models to process)
and the format (content and layout) of the report.
2. For the specified models (and using any additional discrimination data, such as line size), the
system scans the physical elements in the model.
3. The system determines the number of items present in the model by unique commodity
code. In addition to the physical elements, it determines any implied items based on
configuration of mating components or designations in the Piping Commodity Specification
Data (PCD).
4. The system looks up the material descriptions for the located components and implied items
in the Material Description Library.
5. The system writes a report of the located and calculated items based on pre-defined report
format.
There are two main user tasks necessary for creating reports:
Maintaining the data that defines the format, content and approval status of the reports.
Processing reports by activating the interface to extract data from all of the PDS models,
databases, and libraries that are involved in a project.
245
Fo rm a t 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:
246
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.
Descr iption 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.
Number Defines a unique number to name the record with up to 24 characters in the
Project Control Database. This number is a short name to identify the record of the
discrimination data file.
Descr iption Describes the discrimination data file with up to 40 characters in the Project
Control Database.
File Specification Defines the file name of the discrimination data file to reference. The
system verifies that the file does not already have a record in the project.
Path Defines the disk location of the discrimination data file. This field retains the active
setting.
Node Defines the nodename where the discrimination data file is located. This field
retains the active setting.
Re p o rt Re c o rd
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:
Repor t Number Creates a unique report number in the Project Control Database that acts
as a name or identifier for a report record.
Repor t Title Describes the report file. It is not the title in the actual report. That title is
specified in the format file.
Repor t File Spec Defines the file name of the report output file. Each time a file is regenerated 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.
Repor t File Path Defines the directory for the report output file. Repor t Node
Specifies the nodename for the report output file.
Report For mat File Specifies the record number that contains the address of the report
format file to be used.
Report Discr imination Data Specifies the record number that contains the address of
the discrimination data to be used.
247
Re p o rt Ou tp u t
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 Repor t Manager and Drawing reports with the
report manager module of Dr awing Manager . Depending on the definition data used and the
module that executes the process, you can create MTO reports, drawing reports, spec reports,
table checker reports, project reports, or interference reports.
The following section describes the various report types, how they are generated, and their
corresponding sample format files:
Report Types
Various modules in the PDS Suite generate reports. The following section describes the various
report types, how they are generated, and their corresponding sample format files:
248
MTO Repor t (with implied mater ials) 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 Repor t Manager .
Dr awing Repor t 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
Repor t Manager . Format files used in this type of report primarily use A and B prefixed
indices. This report is generated using the Dr awing 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 Refer ence Data Manager .
Table Checker Repor t 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 Refer ence Data Manager .
Pr oject Repor t 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
Pr oject Administr ator.
Inter fer ence 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 Inter fer ence Manager /Checker .
(Brackets [] indicate data that is only used for certain field types; all other data is required in
every field type.)
Syntax Example
249
Definitions
Fie ld _Fu n c tio n
0 Null Field Used to send a data field (index) to sort on an unreported item.
1 Page Field - All Pages Places the specified field once on every page of the report.
2 Page Field - First Page Only Places the specified field once on the first page of the
report.
3 Page Field - Last Page Only Places the specified field once on the last page of the
report.
4 Output Field Places the specified field a variable number of times on every page of the
report based on rows/page and spacing.
5 New Page Marker Forces a new page (form feed) after all the previous statements have
been processed. All the lines in the format file after this marker are placed on a new
(repeated) page. In other words, this enables you to append a complete format file to the
previous format file and use the same data sources and sorting as the previous lines of the
format file.
6 Continuous Page Marker Forces everything after this marker in the format file up to a
New Page Marker or the end of file to be continuously output as one page. The specified
fields are continuously output without any page divisions. (This code overrides the value for
Rows/Page)
This function can be used to generate an intermediate data file in a fixed form that contains
only raw data (without headings and other annotation). This output can then be used as input
to your own report generation software.
7 Turn On Output Field Appending Control Forces all output fields after this marker in
the format file to begin after the previous output field (above 7) is completed, that is, all
output fields will initially begin at the last output fields finishing row.
8 Turn Off Output Field Appending Control If7 is in effect for an output field this code
will turn the effect off making output fields normal.
9 Start of output field loop
250
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.
Ro w
Starting line number to be used in placing the field in the report. The maximum number of rows
in a report is 66.
Co l
Starting column number to be used in placing the field within the specified row. The maximum
number of columns in a report is 132.
Fie ld _Le n
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.
Da ta _Typ e
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.)
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.
251
Fie ld _Typ e
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.)
For MTO reporting, the first character of the index is always A or B. Refer to the description
of the indices for MTO Reporting (with implied materials).
For spec reporting, the first character of the index is always C. Refer to the description of the
indices for Spec Reporting. These indices are also used for the Table Checker.
For project and interference reporting, the first character of the index is always D. Refer to
the description of the indices for Project and Interference Reporting.
[Ro ws /P a g e ]
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.
252
[S p a c in g]
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).
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.
253
S a m p le MTO Re p o rt Fo rm a t File s
The following files are provided in the product delivery in win32app\ingr\pdreport\sample
directory.
segment.fmt This report format includes piping segment data. It demonstrates 'control'
sorting and output field 'looping' (field functions 9 and 10).
This report format reports a list of piping segments grouped by the Model Builder's
alphanumeric description id. The report includes all piping lines that are associated with a
specific Model Builder alphanumeric input file.
(report type = 687)
piping_a.fmt This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, nuts, and welds. It demonstrates the use of 'standard' output
fields.
This report includes each category of data in a fixed area of a repeated report page using
'normal sorting' and 'standard output fields' (field function 4).
(report type = 689)
piping_b.fmt This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, nuts, and welds. It demonstrates the technique for grouping
blocks of output fields on the same page of the report.
This report format reports data similar to 'piping_a.fmt'. It differs only in that it demonstrates
another method to format the data on the repeated page of the report.
(report type = 689)
piping_c.fmt This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, nuts, welds, pipe supports, implied piping components,
equipment, and nozzles. It demonstrates the use of different pages of output within one
report.
This report format reports data similar to 'piping_b.fmt' with the addition of pipe_supports,
implied piping components, equipment, and nozzles. It uses 'page break markers' (field
function 5) to break each category of data onto a different repeated page of the report.
(report type = 689)
piping_d.fmt This report format reports the material descriptions for piping components,
pipes, instrument components, pipe supports, gaskets, and bolts.
This report format uses identical report indices to create two columns to continue data on the
same report page. It also uses page breaks to separate the different categories of data onto
different repeated pages of the report.
254
piping_e.fmt This report format reports data similar to 'piping_c.fmt', but without any
equipment and nozzle data.
This report format uses a 'continuous page marker' (field function 6) to create a report with
no page boundaries and continuous output (typically used for creating a neutral file format).
It also demonstrates the use of report indices to create a summary of standard notes used in
the report.
report type = 689)
piping_f.fmt This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, and pipe supports similar to 'piping_e.fmt'.
Each category of data is grouped (using 'global control sorting') under a common line
number label for each page of output. It uses 'output field appending' (field functions 7 and
8) to have the different categories of data reported on the same page and column of output.
(report type = 689)
piping_g.fmt This report format includes data for piping components, pipes, instrument
components, gaskets, bolts, and pipe supports similar to 'piping_f.fmt' with the same line
number grouping.
This report format uses 'output field looping' (field functions 9 and 10) to utilize all of the
report page space available. The report includes a line number followed by all components
that are associated with that line number label with one or more line number labels being
reported per page, depending upon the amount of data and the space available.
(report type = 689)
weight.fmt This report format includes weight and center of gravity data for piping
components, pipes, instrument components, gaskets, bolts, pipe supports, implied piping
components, and equipment.
The output is similar in format to 'piping_e.fmt' and demonstrates the weight and cog
calculation reporting indices.
(report type = 689)
equip_a.fmt This report format reports equipment data (including location data) and
nozzle data (including location and orientation data). It demonstrates the full range of
equipment and nozzle reporting indices.
(report type = 661)
weldno.fmt This format reports weld information, such as the weld number, type and the
first and second connect point NPD.
pr oject_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.
255
S a m p le S p e c Re po rt Fo rm a t File s
The following files are provided in the product delivered in the win32app\pddata\sample\format
directory.
piping_rdb.fmt This report format includes piping material class data and piping
commodity data from the Material Reference Database. It reports the 'partial' (without
embedded commodity code labels) material descriptions.
(report type = 601)
tbl_chk_1.fmt This report format includes Table Checker data for one piping material
class. It reports the piping commodities with the dimension tables and Piping Eden modules
used, including a list of all entries read in the dimension tables.
This report also includes a list of all dimension tables and Piping Eden modules that were
required for those piping commodities, but not available in the Reference Database. This
report format is a combination of the following report formats tbl_chk_2.fmt,
tblk_chk_3.fmt, and tbl_chk_4.fmt. It provides full Table Checker output for a specific
piping materials class.
(report type = 601)
tbl_chk_2.fmt This report format includes Table Checker data for one piping material
class. It reports the dimension tables and Piping Eden modules used by each piping
commodity in that piping materials class.
(report type = 601)
tbl_chk_3.fmt This report format includes Table Checker data for one piping material
class. It lists all entries read in dimension tables.
(report type = 601)
tbl_chk_4.fmt This report format includes Table Checker data for one piping material
class. It includes a list of all dimension tables and Piping Eden modules used by the piping
commodities in that piping materials class.
This report also includes a list of all dimension tables and Piping Eden modules that were
required for those piping commodities, but not available in the Reference Database.
(report type = 601)
256
iso_r ev.fmt This format file reports isometric drawing revision management data.
S a m p le P &ID Co ns is te n c y Ch e c k Re p o rt Fo rm a t File
The following example is delivered in the win32app\pddesign\sample directory.
pid_cmpr pt.fmt This format file specifies the format of the title page and heading for
each page of the P&ID Consistency Check reports. The remainder of the report is predefined
by the product.
257
In addition to the engineering data in the design database, PDS 3D uses the Material Description
Library and the material data in the Material Reference Database to provide material descriptions
for commodity items and specialty items.
Material Descriptions
The material description data is made up of four major parts:
1. Mater ial Tables in the Mater ial Refer ence 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
258
2. Shor t Mater ial Descr iption Libr ar y - 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 Mater ial Descr iption Libr ar y - 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 Mater ial Descr iption Libr ar y - 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.
259
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 Mater ial Takeoff Options form of the Pr oject 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:
260
Tubing Fittings
Steam Specialties
Socketwelded Fittings
Flanges
Threaded Fittings
Flanged Specialties
Underground Fittings
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.
261
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.
262
Commodity codes with neither an * or a + prefix in the PCD, indicate a commodity item that
has no associated implied components.
Report Output
The following is a sample report using the format file piping_a.fmt. It reports on a very simple
pipeline containing the component examples covered in Chapter 4 and the connecting pipes.
263
264
265
PDS MTO
REPORT
Page: 1
PDS Project
tcproj
tc101
Huntsville,
Alabama
35894-0001
RoXXon Corp.
(205)730-2000
Commodity Code
Nth Projector
Qty/Length
1st Size
2nd Size
Material Description
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
FAAABAWAAA
3IN
LINE NUMBER:
P403-3IN1C0031-N
3IN
XDAABZZQSG
3"
YZZZHZZFFF
5/8"
4IN
LINE NUMBER:
P403-4IN1C0031-N
4IN
FAAABAWAAA
4IN
4IN
VAABAHCCAA
4IN
4IN
VBABAHCFAA
4IN
4IN
WAAAAAWAAA
4IN
4IN
WRBAAAWAAA
4IN
3IN
WTAAAAWAAA
4IN
4IN
1st Size
PDS MTO
REPORT
2nd Size
3/4"
*
Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, SSTD bore
47
Date/Time : 15-Apr93
Commodity Code
Qty/Length
LINE NUMBER:
P403-4IN1C0031-N
266
9/16"
4IN
XDAABZZQSG
4"
YZZZHZZFFF
32
5/8"
supp2
4IN
3/4"
FAAABAWAAA
11
6IN
LINE NUMBER:
P403-6IN1C0031-N
6IN
FGPBBAWAAA
6IN
6IN
GJGABZZADA
6IN
6IN
VAABAHCCAA
6IN
6IN
304
spiral wnd,
47
VCABAHOBAA
6IN
6IN
WAAAAAWAAA
6IN
6IN
WADAAAWAAA
6IN
6IN
WOAAAAWAFA
6IN
4IN
WOBSABQAFA
6IN
3/4IN
90 deg LR elbow,
B16.9
45 deg LR elbow,
B16.9
Weldolet, S-STD x
A105
Sockolet, CL3000,
WRAAAAWAAA
6IN
4IN
WTAAAAWAAA
6IN
6IN
PAAAAAWAAA
6IN
XDAABZZQSG
131 1
3/16"
12
6"
XDABBZZQSG
6"
YZZZHZZFFF
80
3/4"
4"
YZZZHZZFFF
20
3/4"
5"
supp1
6IN
Date/Time : 15-Apr93
Commodity Code
Qty/Length
1st Size
PDS MTO
REPORT
2nd Size
S-STD, BE, ASTM-A234-WPB, ANSIS-STD, BE, ASTM-A234-WPB, ANSIS-STD, BE, ASTMBE/SWE, ASTM-A105
304
spiral wnd,
304
spiral wnd,
Page: 3
Material Description
LINE NUMBER:
P403-6IN1C0031-N
supp3
6IN
Date/Time : 15-Apr93
GRAND TOTALS
Components Pipes
8719
*
PDS MTO
REPORT
Instrument
s
2
Page: 4
Gaskets
Bolts
Pipe Supports
18
136
267
Bolts
Gaskets
Nuts
Welds
The Mater ial Takeoff Options form is part of the Project Administrator module, and its setting
greatly affect the way mating implied items are reported.
For more information on mating implied item reporting see the Material Takeoff Options
section.
The definition of the spec implied item has the same search parameters as the primary
component, except in the following instances:
The value for the option attribute of the spec implied component is equal to 5000 plus
the option value for the primary component.
The definition of the spec implied component can be divided into several NPD ranges.
The output parameters of the spec implied component may differ from those of the primary
component in the following instances:
268
Only the primary component is included in the model depiction; the spec implied
component only appears in reports.
Only the primary component is displayed on an isometric drawing; the spec implied
component only appears in the materials list.
Jacketed components when the outer jackets are obtained independently of the internal
components.
Nte lng
PIPING 1 2
PIPING 5001 2
6
6
301 301 -
PIPE
PIPE
The output parameters of the table implied item may differ from those of the primary
component in the following situations:
If only the primary component is included in the model depiction, the table implied
items appear only in the report.
If the primary component is displayed on an isometric drawing, The materials list only
includes the short description of the primary component. The descriptions of the table
implied items are displayed as notes on the drawing, pointing to the primary component.
The text for these notes is derived from the short descriptions of the applicable
commodity codes. The short description can contain $ symbols to force the text to a new
line in the label.
The commodity codes prefixed by a '+' are used to define the following items:
269
6Q2C01 1
3
+FAAABAWAAA -
Secondly, notice the table entries that are related to the primary component,
F
212
Sequence=
Single_Spacing
!Comm Code
10
!
FAAABAWAAA
IMPFLG2A
1.5
IMPFLG2B
0.5
IMPFLG2C
1.0
1
2
1
2
1
2
2
FAAABAWAAA
FAAABAWAAA
VAABAHCCAA
VAABAHCCAA
IMPVAL2A
0.5
IMPVAL2B
2.5
PAAAAAWAAA
IMPPIP2 1.0
WAAAAAWAAA
IMPELB2 2.0
WRAAAAWAAA
1
2
1
0
IMPRED 1.0
270
Operating Sequence
1. Specify the bolt information.
Bolt Length Roundoff Select the option for the means to determine the reported bolt
length.
Pr efer r ed Bolt Length Tablethe system uses the preferred bolt length table.
Bolt Roundoff Factor the system rounds up the calculated length by the specified
factor.
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 Pr ecise) or using termination type, rating, and table suffix (Pr ecise).
This also affects bolt lengths for lap joint flanges.
Bolt Commodity Code Select the method to be used in determining the commodity code for
bolts for use in material take-off. Piping J ob Specification or Bolt Commodity Code
Table.
Bolt Diameter Units Select the system of units for bolt diameter.
271
Sour ce 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).
Sour ce of Mater ial Descr iption 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.
272
Processed Library
23
14:16:58
1992
/usr/newpipe/refdata/us_shbom.l
!Cmdty Code
====================================Description======================
CHAIN_1003
CHAIN_1005
CHAIN_1251
DAABAXAABE
DAABAXAABF
station type,
Monitor, CL150
outlet, [427],
in-let by
station type
DACBAXABBC
4" CL150
[402]
4" CL150
in-let by
FFFE,
4" CL150
in-let by
w/drain coupling, w/shapertip nozzle and two reaction supports, Stang BB2999-
273
6" CL300
in-let by
DBAAAXBAAB
FFFE,
274
300#, FTE,
2.5"
DCBGDXEADA
Hose rack,
30-333
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
[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|
125
Ra finish,
FAAADBDFFC
125
FAABBADIIA
FAABBADIIB
FAABBADIIF
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
[409]|bore to match|
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
Ra finish, S-160
Ra finish,
125
125
bore
[409]|bore to match|
Ra finish,
Ra finish,
125
bore
[409]|bore to match|
[409]|bore to match|
Ra finish,
[409]|bore to
275
FAADBADIIF
FAADBAOAAA
FAADBAOABE
FAADBAWAAA
FAADBAWABE
FAADBAWFFC
FAADBAWFFH
[409]|bore to match|
FAADBAWFFL
[409]|bore to match|
FAADBAWIIA
bore
bore
[409]|bore to match|
[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:
276
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
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.
Although data for bolts and gaskets is not recorded in the Piping Component Data Table
(pdtable_34_x) in the Piping Design Database (dd_projname), bolt and gasket labels are
classified as Piping Component Data labels. The system retrieves the bolt and gasket
information for reporting using related attributes in the Piping Component Data Table
(pdtable_202).
Although all of the attributes for piping components are available when you define a bolt or
gasket label using the Piping Component Data labels option, only the following attributes
contain data that is pertinent to bolt and gasket reporting. The following list displays the formattribute/table-attribute relationships which define what data is actually reported from the Piping
Component Data Table (pdtable_202):
Form Attr ibutes
Related (pdtable_202)
Attr ibutes
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
277
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
In s e rt Da ta
1. Set the option to Inser t Data.
2. Set the toggle to Inser t after or Inser t befor e.
3. Select Line or Item to Insert Data
Select a line field to create a new line (before or after) the selected line.
OR
Select an item field to create a new item in the current line (before or after) the selected item.
The system activates a form that displays the Attribute Data Types. The following form
illustrates the display for a drawing view specific label.
4. Select Option
Select Piping Component Data to define the attribute data type for the bolt or gasket label.
279
The system displays the attributes for the selected data type.
5. Enter Data
Select the attribute to be reported from the form. The system sets the Format Data
automatically. You can modify the total length and the number of decimal places (if
applicable).
All of the attributes that apply to gaskets and bolts are listed in the Labels in Mater ial
Descr iptions section.
OR
For drawing view specific labels, you can select User Keyin Attr ibute to specify text to be
entered by the user at label creation.
OR
Select Text Only and key in the text for a literal expression to be inserted in the label.
OR
Select Spacing Only and key in the number of spaces to define spacing between attributes.
6. Repeat the previous step to add additional attribute text information. This allows you to
combine attribute values and pre-formatted text.
You can only define one user-defined key-in in a specific label.
7. Select one of the Optional Data options to specify a modifier to the active format. Master
Units = MicroStation master units, Sub Units = MicroStation sub units.
8. Select Confir m ( ) to accept the specified attribute data.
280
De le te Da ta
1. Set the option to Delete Data.
2. Select the line or item to be deleted.
3. Select Confir m ( ) to delete the highlighted line or item. When you select a line, the system
deletes all the associated items.
Ed it Da ta
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 For mat 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 Attr ibute 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 Confir m ( ) to accept the edits.
281
282
SECTION 27
Intergraph 3D software packages which create input for ISOGEN and perform other
functions necessary in final drawing creation.
ISOGEN, which draws the piping isometric and places it in a MicroStation design file and
The software allows you to extract isometrics from a 3D plant model: single isometrics
interactively or multiple isometrics in a batch mode.
283
In addition to the isometric drawing, the software also generates several nongraphic outputs, the
most important of which is a completely user-definable MTO neutral file. This neutral file is
extremely useful for those who want to combine a material control system with Intergraph's 3D
modeling software.
The above features are collectively referred to as software customization and are dealt with at
length in the PDS ISOGEN Interface Reference Guide.
In This Section
Overview of Isometric Extraction.................................................. 285
Batch Software Organization ......................................................... 287
284
285
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:
286
287
288
In SEED.DAT, the seed iso design file name is followed by records containing the plot request
file name, the output file directory, the output iso file name, extraction number and number of
sections.
pdssk:h: \proj\iso\ref\isoc .def
pdssk:h: \proj\iso\ref\isoc.sed
pdssk:h: \proj\iso\ref\isoc_sml .i
pdssk:h: \proj\iso\isof iles
380105 13
1.fi
289
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.
290
SECTION 28
The Dr awing 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.
291
In This Section
Drawing Manager Features............................................................ 292
Drawing Manager Setup ................................................................ 292
Drawing Seed Data ........................................................................ 297
Using Labels in Drawing ............................................................... 301
Create a drawing for any of the PDS 3D disciplines, along with a key plan drawing.
292
Editing the control script to identify the location of the project data.
Model Files
A set of model files for the project must be defined before you can use the Dr awing Manager .
Refer to the following documents for information on creating and manipulating PDS 3D Models.
Drawing Categories
When a project is created, the Pr oject Administr ator 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
Pr oject Administr ator as a part of project creation. The Dr awing 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 Dr awing 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 Refer ence Data Manager . This setting is stored in the Project
Control Database for access by the Dr awing 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.
293
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 .
294
Dr awing Size Std Note is the standard note, which is referenced from the Standard Note
Type 1202, for the drawing size selected.
Cutting Edge Size reflects the actual size of the cutting edge around the border that is
associated with the drawing size.
X-l defines the horizontal distance from the left cutting edge for composition.
X-t defines the horizontal distance from the right cutting edge for composition.
Y-r defines the vertical distance from the top cutting edge for composition.
Y-b defines the vertical distance from the bottom cutting edge for composition.
Dr awing Size is the standard note text for the drawing size.
# Drawing Data
table number = 121, number of columns
=
1 , dwg_index_no
24
, 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
, short
10, drawing_type
, short
11, last_revision_no
, character(2)
12, drawing_file_spec
, character(14)
13, path_name
, character(36)
14, network_address
, 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
, standard note 35
, index 3
23, standard_note_no_a
, short
24, standard_note_no_b
, short
16
295
, 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
, composition_status
, dwg_view_x_low
, short
, 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
, double
15, vhl_category_index
, short
16, drawing_view_type
, short
, integer
, model_index_no
, integer
15
, 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
, dwg_view_index_c
, integer
, dwg_view_index_d
, integer
, integer
, index
, character(40)
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
296
, revision_index_no
, short
, revision_no
, character(2)
, integer
, revision_date
, integer
, revision_by
, character(4)
, checked_by
, character(4)
, rev_description
, character(40)
7
, short
, drawing_size
, short
, drawing_scale
, character(16)
, default_path_name
, character(36)
, default_node
, character(26)
, discipline_mask
, short
, alternate_seed_opt
, short
# Reference Model Display Category Setup Data
table number
, drawing_type
, discipline_indx_no
, short
, category_mask_a
, integer
, category_mask_b
, integer
, category_mask_c
, integer
, category_mask_d
, integer
, short
, 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)
297
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
298
Coordinate Labels
Dimensioning
10
Hold Clouds
11
Reports
12
Battery Limits
36
Matchlines
37
Centerlines
38
Dumb Details
39
40
41
42
43
44
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
299
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
300
Color
Battery Limits
Weight
Symbology
0 Solid
Matchlines
0 Solid
White
Centerlines
0 Solid
White
Dumb Details
0 Solid
White
0 Solid
White
0 Solid
White
0 Solid
White
0 Solid
White
0 Solid
White
White
Terminator
Text
Size
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
Text
Spacing
Font
Factor
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0 Solid
White
11
0 Solid
White
12
0 Solid
White
13
0 Solid
White
14
0 Solid
White
15
0 Solid
White
16
0 Solid
White
17
0 Solid
White
18
0 Solid
White
19
0 Solid
White
20
0 Solid
White
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
1/4",
1/4"
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
0.0000
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.
Dis p la ya b le Attribu te La b e ls
Each type of displayable attribute label has a description in the Label Description Library. This
description identifies the label characteristics such as level, color code, style, and font, and the
attribute data associated with the label.
A displayable attribute label consists of the text and optionally, a leader line, a line terminator,
and some label enclosure graphics. This label type is further divided into the following
categories.
301
Alp h a n u m e ric La b e ls
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.
Dis p la ya b le Attribu te Me s s a g e
Each type of displayable attribute message has a description in the Label Description Library.
Unlike the other label types, the description of a displayable attribute message only contains the
attribute data. Therefore, you cannot define label description data such as color, weight, style,
and text size for a displayable attribute message.
A displayable attribute message has all or part of its text derived from the alphanumeric data that
is linked to a specified named item in the model.
A displayable attribute message is displayed temporarily at the terminal either as an
identification message or as a reporting message. Some of these messages are displayed in the
terminal's refresh message fields. Other messages are displayed temporarily in the model. The
system does not place any graphics in the model for this type of label.
A displayable attribute message can also be used to create a value for another attribute, for
example, the Line Number Label attribute.
302
303
304
Index
3D Coordinate Systems 22
3D Seed Data 135
3D Setup 14
About licensing 14
About the Reference Database (RDB) 139
Activating the Orientation Tee 147
Active Placement Point 161
Alphanumeric Labels 302
Analyze Data 165
Appendix A
Troubleshooting 223
ASCII to Binary Conversion 286
Attribute Types 40
Data_Type 251
Database Definition Files 41
Database Information 40
Database Overview 35
Database Requirements 168
Define Commands 148
Definitions 250
Delete Data 281
Delivered Reference Data 76
Design Area and Piping Design Area
Predefined Volume 231
Design Database 57
Design Review Integrator (PD_Review) 11
Design Volume Coordinate System 28
Detecting and Managing Interferences 227
Dialog Boxes 128
Diameter Table 96
Disable Display of P&ID Drawing
Command 217
Discrimination Data File 247
'
'*' Spec Implied Items 268
[
[Buffer] = Field Definition 252
[Rows/Page] 252
[Spacing] 253
'
'+' Table Implied Example 270
'+' Table Implied Items 269
2
2DSetup 13
B
Base Form 134
Batch Software Organization 287
Bend Deflection Table 117
Branch Insertion Tables 117
C
Cells 293
Choosing Data Transfer Options 201
Plant Design System 3D Theory
305
Index
Displayable Attribute Label 304
Displayable Attribute Labels 301
Displayable Attribute Message 302
Drawing Borders 293
Drawing Categories 293
Drawing Manager (PD_Draw) 7
Drawing Manager Database Table
Information 295
Drawing Manager Features 292
Drawing Manager Setup 292, 293
Drawing Plot Size Table 294
Drawing Seed Data 297
Drawing View Specific Labels 303
DVCS Oriented From Plant North 31
E
Edit Data 281
EE Raceway Modeling 11
Equipment Manipulation Commands 148
Equipment Model Seed Data 140
Equipment Modeling (PD_EQP) 4
Equipment Modeling Commands 148
Equipment Modeling Concepts 145
Equipment Modeling Environment 143
Establish a SmartPlant/PDS Link 194
Examples 30, 261
Extracting Isometric Drawings 283
F
Fabrication Category 103
Field_Function 250
Field_Len 251
Field_Type 252
Format File 246
Format File Syntax 249
Forms 130
FrameWorks Plus (FWP) 4
Functions of PDS Equipment Modeling
(PD_EQP) 139
G
Gasket Gap / Table 99
Generic Physical Data Modules 108
Generic Tables 114
Geometric Industry Standard 102
Graphic Commodity Data and Physical
Dimension Data 87
306
H
Hard - Hard Example 241
Hard - Soft Example 242
How PDS Works 91
I
Implied Data 262
Insert Data 279
Install Oracle 187
Install SmartPlant Engineering Manager
188
Install SmartPlant P&ID 189
Installation 187
Instrument Component Specification Data
81
Instruments and Instrument Loops 3
Interference Checker Input 237
Interference Checker Output 238
Interference Checker/Manager (PD_Clash)
8
Interference Checking Process Overview
227
Interference Manager 240
ISOGEN 286, 290
Item Name and Model Code 100
L
Label Definition Data 302
Label Description Library 89
Labels in Material Descriptions 273
LabelTypes 301
Level and Symbology Defaults 125
Level Control and Graphical Symbology
124
Line Processing (pdsidf) 289
Load From P&ID Options 203
M
Maintaining Report Definition Data 246
Map an Ignored Attribute 198
Map an Unmapped Attribute 198
Mapping Attributes 197
Index
Material Data Publisher 281
Material Description Data 87
Material Descriptions 258
Material Takeoff Options 270
Material Takeoff Reporting (Report
Manager) 263
Materials Grade 103
Materials Table 98
Mating Implied Items 268
Menus 127
Miscellaneous Commands 148
Model Data 165
Model Files 123, 293
Model Parametric Shape Definitions 112
Modeling Setup Requirements 122
Modifier 102
N
Name From P&ID 180
Name from P&ID Option 219
Named Component Existence Report
Command 221
Nozzle Manipulation 148
O
Option Code 101
Optional Report Type Line 253
Orientation Tee 162
Output Fields 253
Overview of Isometric Extraction 285
P
P&ID Correlation Table 168
P&ID Data 180
P&ID Data Comparison Options 181
P&ID Drawing Display Categories
Command 213
P&ID Graphical Data Transfer Setup 174
P&ID Node Numbers 176
P&ID to Piping Data Transfer 167
Palettes 128
Parametric Shape Definitions 111
PDS 3D Databases 39
PDS and the Relational Interface System
(RIS) 36
PDS Isometric Interface (PD_ISO,
PD_ISOGEN) 9
R
Reasoning 22
Recommended Working Units - English 20
Recommended Working Units - Metric 21
Reference Data 75
Reference Data Manager (PD_Data) 6
Reference Data Setup 122
307
Index
Reference Database 69
Report Format File 249
Report Manager (PD_Report) 10
Report Output 248, 263
Report Record 247
Report Types 248
Reporting Process 245
Restore View of Piping Model Command
215
Review Data 165
Review P&ID Drawing Details Command
211
Review/Revise Commands 148
Revise Data 165
Revising Linked Models 195
Revision Commands 164
Row 251
S
Sample Format Files 254
Sample Interference Report Format File
257
Sample MTO Format (piping_g.fmt) 264
Sample MTO Output 266
Sample MTO Report Format Files 254
Sample P&ID Consistency Check Report
Format File 257
Sample Project Control Report Format Files
257
Sample Spec Report Format Files 256
Secondary Commands 149
Seed Files 122
Segment Data Comparison Report 199
Segment Vertex Commands 164
Select P&ID by Line ID Command 207
Select P&ID Drawing by Nozzle Command
209
Selecting Options 131
Setting Up a System to Support Interference
Detection 235
Single/Dual Ownership of Clashes 233
SmartPlant P&ID to PDS Piping Data
Transfer 183
Spec Access 94
Specific Physical Data Modules 108
Specific Tables 115
Standard Note Library 89
Sub-Symbol Processor 106
308
T
Table Access 103
Tap Properties Data 82
Temperature Pressure Table 96
Test the SmartPlant Connection 189
The Batch Job Input File 288
The Intergraph Interface to ISOGEN 286
The ISOGEN Interface 289
Thickness Equations 98
Thickness Table 97
Transfer by Equipment Number and Nozzle
Number 178
Transferring Piping Data 185
U
Understanding Design Areas and Volumes
230
Understanding Implied Items 268
Understanding Interference Checking 237
Understanding Interference Envelopes 236
Understanding Interference Plotting 242
Understanding Interference Reporting 243
Understanding Report Files and Records
246
Update by Node Number 178
Update From Active P&I Drawing 179
Update Segment Data from P&ID 177
Using Labels in Drawing 301
V
View Windows 129
Volume Filter 232
W
Weight code 103
What are the 2D modules? 2
What are the 3D modules? 4
What Happens When I Place a Component?
91
What Happens When I Report On a
Component? 258
What is the Plant Design System? 1
Working in Three Dimensions 16
Working Units 19
Index
Working with the Graphical User Interface
126
309