PDS Piping Model Builder PD Model

Plant Design System (PDS)
Piping Model Builder Reference Guide
Version 2011 (V12)

June 2011
DPDS3-PE-200029G
Copyright
Copyright 1984-2011 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement;
contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade
secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from
Intergraph Corporation.
U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of
the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless
the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed
license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use
of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives
licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement
and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for
resale or redistribution.
Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software
or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this
document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes
the information in this publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the
terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not
supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph, the Intergraph logo, 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 ................................................................................................................................................. 5
Piping Model Builder (PD_Model) Overview ............................................................................................. 7
Alphanumeric Piping Language ................................................................................................................ 9
Alphanumeric Piping Language Requirements ...................................................................................... 9
The Language File ................................................................................................................................ 10
Header Line .................................................................................................................................... 11
Synonym Line ................................................................................................................................. 11
Command Lines ............................................................................................................................. 13
Default Keywords ........................................................................................................................... 23
Sample Alphanumeric Piping Language Files ............................................................................... 25
Piping Model Builder ................................................................................................................................. 31
Index ........................................................................................................................................................... 35
Plant Design System (PDS) Piping Model Builder Reference Guide
Contents
Preface PDS
This document provides command reference information and procedural instructions for the
Plant Design System (PDS) Piping Model Builder (PD_Model) task.
List of PDS Documentation
DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide

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

Overview
The Piping Model Builder (PD_Model) enables you to create piping graphics from a
non-graphics environment.
This module is used with PD_Design to create an accurate 3D model of the piping network. The
resulting piping models can be used for checking interferences, extracting drawings, and
generating bills of material.
The following illustration shows a typical piping model. The piping model contains fully
dimensioned graphics for piping, piping components, instruments, piping specialties, and pipe
supports.
Piping Model Builder (PD_Model) Overview
SECTION 2
Alphanumeric Piping Language

The Alphanumeric Piping Language provides a set of commands which enable you to perform
modeling in an alphanumeric environment. The commands are stored in a standard ASCII file
and submitted in batch.
The Alphanumeric Piping Language provides the following basic features:
A combination of movement and placement commands (similar to SKETCH and PLACE
COMPONENT in graphics) is used to define the basic piping segments and piping
components.
Instruments and engineered items can be defined out of spec or placed from data in the
reference database.
Automated Placement can be invoked automatically after all the commands are executed.
A special ID is used to identify an existing pipeline that was created with the Piping Model
Builder. Before processing the ASCII file, the system deletes all the existing pipelines in the
file with the specified identifier. The identifier is stored in table 12, column 71,
alpha_descript_id.
P&ID data can be transferred to a segment by node numbers.
Synonyms can be used to assign complex or frequently used command strings to
user-defined names.
All coordinates are defined in the Plant Coordinate System.
All characters in the language file are translated to UPPERCASE letters before compilation,
making the language case-insensitive.
Lines can contain up to 132 characters. You can use a hyphen (-) anywhere a keyword is
expected (generally following a comma) to continue a line.
Some attributes can be updated using the attribute value or the code list value. Those
attributes which cannot be updated in the language are identified in the DDL by the suffix_R
at the end of the attribute name.
See Also
Alphanumeric Piping Language Requirements (on page 9)
The Language File (on page 10)
Piping Model Builder (on page 31)
Alphanumeric Piping Language Requirements

The Project Database and Model file to be used by the language must already exist.
The Alphanumeric Piping Language uses the following files during processing.
Language File (required)
The Language File contains the modeling instructions to be performed. This file is identified
at compilation.
Keyword File (optional)
The Keyword file can be used to change the keywords used by the Alphanumeric Piping
Language. This file is always defined as KEYWORD.ALPHA. The system writes a message to
the log file indicating whether this file was located and used.
Synonym File (optional)

The Synonym file can be used to assign a command string to a user- defined name (text
string). All synonyms defined in this file and the Language file are literal translations and will
replace all occurrences of the identified synonym. This file is located in the same directory
as the Language File and has the file name SYNONYM.ALPHA. The system writes a
message to the log file indicating whether this file was located and used.
Before you can use the Synonym file with Model Builder, you must set the type 63
setting for the model to Enable Commodity Synonyms and locate the Synonym file
through the Reference Database Management Data. For more information about changing
type 63 settings, refer to the Component Placement section of the Project Administration
(PD_Project) Reference Guide, and for further information about the Reference Database
Management Data, refer to the Reference Data Location section of the Reference Data
Manager (PD_Data) Reference Guide.
Item Synonym File (optional)
The Item Synonym file can be used to substitute the exact string of characters defined as
the synonym. These synonyms are specific and are only used for item names (such as
substitution for component names, instrument names, etc.). This file is always defined as
ITEMSYN.ALPHA. The system writes a message to the log file indicating whether this file
was located and used.
A set of sample files are delivered with the product in the \win32app\ingr\pdmodel\sample
directory. This is also the location where the software expects to find the .ALPHA files.
The Language File

The language file is a user-defined ASCII file that contains all the necessary modeling
instructions required by the Alphanumeric Model Builder. The language file instructions are in
standard ASCII text format. The language file is interpreted by the system using the three
optional files described in Alphanumeric Piping Language Requirements (on page 9). Each
instruction should be completed in one line or a continued line. The following types of instruction
lines can be used in the language file:
Header Line (on page 11)
This line is defined once and must appear before any command lines. The Header Line may
include a revision date.
Synonym Line (on page 11)
These lines can be placed anywhere in the language file to define how the system will
interpret certain strings of characters within the file. Synonyms are interpreted in the order
that they are defined. These synonyms have the same function as the synonyms within the
Synonym File.
Command Lines (on page 13)
These lines must occur after the Header Line. The command line contains the modeling
instructions to be performed. Each Command Line contains one complete instruction.
Comment Line
These lines are indicated by an exclamation point (!) and may occur anywhere in the file.
Any text to the right of the exclamation point (!) on any line will be ignored by the system.
Blank Line
Blank or empty lines can be placed anywhere in the file.
Language File Conventions

The following conventions are used to describe the language file instructions in this document.
10
Instructions are shown in a special typeface.

Keywords are represented by UPPERCASE letters, numbers, and symbols.
Lowercase letters indicate descriptive text.
Brackets [ ] indicate optional data.
Dashes (-) indicate continued lines.
See Also
Default Keywords (on page 23)
Sample Alphanumeric Piping Language Files (on page 25)
Header Line
This line is defined once and must appear before any command lines. It defines the Project and
Model to be used for alphanumeric processing and may optionally include a unique piping
segment identifier and a revision date.
FILE= *, PRO= * [,ID=identifier] ,DATE=date [,AUTOFF]
filename -- This argument is no longer used. The name of the Piping Model to be used for
processing is specified at compilation. The system places all the modeling performed by the
language into the identified piping model.
project_name -- This argument is no longer used.
identifier (optional) -- This is a 12 character code used to identify the created pipeline(s) in
attribute 71 of the piping segment data. The identifier is assigned to all the segments placed
by the language. The system also uses the identifier to delete all existing segments in the
piping model that have the same value. It is very important that the identifier be unique, as
all segments and items on those segments will be deleted before the modeling instructions
are executed.
If the identifier is blank or the ID keyword is not present, no deletions will occur and all
segments will have a blank entry in the associated attribute.
date -- Defines a 30-character revision date. This value is not used by the system.
AUTOFF (optional) -- Turns off Automatic Placement. By default, Automated Placement is
initiated at the conclusion of the model building process. This automatic placement will only
execute on the last pipeline placed by the language.
The ID keyword is useful in developing the language file since it assigns a unique ID
to all lines placed by the language. This enables you to delete the elements associated with
old versions of the language file before placing the new versions.
Synonym Line
Synonym lines can be placed anywhere in the language file to define how the system will
interpret certain strings of characters within the file.
$synonym$synonym_definition
$ -- Synonym keyword. The $ must be the first character in the line.

synonym -- Character string to be used in the language file. All characters (including
blanks) between the $ signs are part of the synonym.
synonym_definition -- String of characters that the system will interpret when the synonym
is encountered in the language file. This includes all characters (including blanks) to the end
of the line.
Synonyms define literal character string to character string translations. For each line of text
encountered in the language file, the system uses all the currently defined synonyms up to that
line to translate the line. The first synonym defined is compared to the line and any occurrences
11

of that synonym (string of characters) is replaced with that synonym's definition (string of
characters). The next synonym that was defined is then used in the same manner. This is
repeated until all the defined synonyms are translated.
A synonym definition can contain up to 30 previously defined synonyms within its definition. A
synonym cannot be repeated in its own synonym definition.
The system returns an error if the interpreted language line is greater than 132 characters. If this
occurs, you should break the line and/or synonyms using a continuation line so that no part of
the continued line exceeds 132 characters.
Synonyms replace text; they do not store calculated results or other such intelligent
functions. If synonyms are used to replace calculations, those calculations are performed
exactly as the text appears at run time (when the translated line is executed not when the
synonym is defined).
Example 1
$FLANGE$PLACE, PF=6Q2C01
FLANGE, CP = 2
FLANGE
The two command lines below the synonym would be translated by the system as follows:
PLACE, PF=6Q2C01, CP = 2
PLACE, PF=6Q2C01
Example 2
This example shows a possible error which results from using a non- unique character string as
the synonym:
$FLANGE2$PLACE, PF =6Q2C01, CP= 2
FLANGE2
FLANGE
The two command lines below the synonym would be translated by the system as follows:
PLACE, PF=6Q2C012
PLACE, PF=6Q2C01
This garbled translation was caused by the first synonym being translated and then being used
by the second synonym. The system used the first synonym to replace all occurrences of
FLANGE with the synonym definition, including the characters in FLANGE2. The second
synonym never gets translated because no occurrence of FLANGE2 is left in the translated
lines. You can solve this problem by making the first synonym (FLANGE) unique (such as
enclosing it in quotes or parentheses), or reorder the synonyms so that the second synonym
(which contains the first synonym as a substring) is defined first.
$"FLANGE"$PLACE, PF=6Q2C01
FLANGE2
"FLANGE"
or
FLANGE2
FLANGE
12

Example 3
This example shows the use of embedded synonyms.
$TOP OF RACK$N/AC= HEIGHT OF RACK + POD + ITK
$HEIGHT OF RACK$500FT
MOVE, TOP OF RACK
$HEIGHT OF RACK$400FT
MOVE, TOP OF RACK
The system would translate these command lines as follows:
MOVE, N/AC= 500FT + POD + ITK
MOVE, N/AC= 400FT + POD + ITK
The synonym HEIGHT OF RACK is redefined during the execution of the language and thereby
changes the value for TOP OF RACK.
Command Lines
The command line contains the modeling instructions to be performed. Each Command Line
contains one complete instruction including any options associated with the command. There
are two types of command lines:
Movement Commands: FR, SHIFT, JOIN, and MOVE (with optional data options).
Placement Commands: PLACE (with optional data options).
See Also
FR (on page 13)
SHIFT (on page 16)
JOIN (on page 16)
MOVE (on page 16)
Data Options for Movement Commands (on page 16)
PLACE (on page 17)
Placement Data Options (on page 19)
Coordinate Values (on page 22)
Default Units (on page 22)
FR
The FR command (from) is similar to the CONNECT TO DESIGN and POINT IN SPACE graphic
commands. It specifies the location of the active place point.
Syntax
FR, movement option [& movement option] [,data option]
The movement option is one of the following:
EQ=equipment id/nozzle id
This option updates the active point from its current position to the nozzle connect point location.
The equipment item and nozzle must exist in a reference file attached to the specified model
with the locate option ON.
NA=previously named point.
This option requires that a named point be defined by a previous command line. It updates the
active point from its current position to the location of the named point.
vector/movement_type
where vector is
13

E, W, N, S, D, or U for directions
AFC for move Along the Flow Centerline
vector-angle-vector (such as N30E) to move at an angle *
vector-angle-vector-angle-vector (such as E45N30U)
(The three vectors must represent three different axes of the
active coordinate system.)
where movement_type is
EQ=equipment id/nozzle id
The equipment item and nozzle must exist in a reference file attached to the specified model
with the locate option ON. The system moves the active point from its current position to an
intercept point along the vector into one of the three planes at the nozzle location. First, the
plane normal to the nozzle's secondary axis is used to determine an intercept point. If this
calculation fails, the plane normal to the nozzle's normal axis is used. If this also fails, a final
attempt is made to find the intercept with the plane normal to the nozzle's primary axis. If all the
methods fail, an error will result. This option should be used carefully to ensure the desired
results.
Connecting to a nozzle updates the active primary and secondary axis from that of the nozzle.
NA=named point (optional equation)
This option requires that a named point be defined by a previous command line. It uses the
vector to determine which coordinate of the named point location will be used to update the
active point coordinate. The active point is moved to one of the named point's coordinates or the
resulting coordinate value from the equation using the named point(s).
AC=absolute coordinate value (optional equation)
This movement_type uses the vector to determine which coordinate of the active point to update
with the resulting coordinate value of the equation or value.
DC=delta coordinate value (optional equation) *
This movement_type updates the active point by moving a delta distance along the given vector,
where the delta distance is determined by the value or equation.
P/vector/plane_def=coordinate value
where vector is E,W,N,S,D,U, AFC, or vector-angle-vector (See the discussion for these options
above.)
where plane_def is HOR, VER_N, or VER_E
This option updates the active point by moving along the specified vector to the point of
intersection with the specified plane. The plane to intercept is determined by defining one of the
infinite xy (horizontal - HOR), xz (vertical north - VER_N), or yz (vertical east - VER_E) planes
and a corresponding coordinate value (or equation which defines an exact plane along the axis
of infinite planes). For example, the coordinate for the
xy (HOR) planes is an elevation coordinate xz (VER_E) planes is an east-west coordinate (+-)
the yz (VER_N) planes is a north-south coordinate (+-).
U_NAM/REFconnect_point_number=<unique_name>
This option updates the active point by connecting to a component with a unique name and
connect point. For example, you can connect to a branch component (such as connect point 2
of a weldolet) where the header line has been modeled in a different piping model or using a
different Piping Model Builder description.
where connect_point_number is a number from 0 to 5 for the connect of the named component.
where unique_name is a name applied to the component at placement or defined with the
Revise Attribute command.
14

The unique name may have been defined in a different piping model. If so, that reference model
must be attached to the active piping model in order for the system to properly connect to the
component with the unique name. The Piping Model Builder will not search any other piping
models in the project for this unique name. You can use the following options to limit the extent
of the search for the 'unique name'.
SC_AREA=piping_design_area_name
This keyword defines the piping design area in which to search for the component with the
unique name. This option automatically disables any piping model number search criteria that
might be active.
SC_MODEL=piping_model_number
This keyword defines the piping model in which to search for the component with the unique
name. This option automatically disables any piping design area search criteria that might be
active.
SC_PIPING
SC_PIPE
SC_INSTR
These keywords specify the type of component data table to search for the unique name.
Unless you specify otherwise, all three types, piping components, pipes/tubes, and instrument
components, are searched.
SC_ALL
This keyword restores the search criteria to its default mode. It disables any previously specified
search criteria for piping design area, piping model number, or component type.
The system searches all piping models within the active model's design area, which are
attached to the active model as reference models. It searches the active piping model first
before any other piping models in that design area.
On the basis of the specified options, the system connects to the first component found having
the unique name and connect point number specified. Once you specify a search option, that
search option remains active for any subsequent unique name operations until you specify a
different search option. If no component is found with this unique name, the Piping Model
Builder terminates with an appropriate error message.
You can use the & symbol to concatenate multiple movement options together on the same line
and form one final active point. If the EQ= or NA= options are used in a concatenation, only
one or the other (EQ or NA) can be used and it must be the first option in the command line.
Examples
FR, EQ=P-300B/N1 & E/DC=2FT 3 1/2IN
This example moves the active point to the equipment nozzle P- 300B/N1 and then moves east
2' 3 1/2" inches from that point to define the final active point.
FR, U_NAM/REF2=olet01, SC_AREA=pdarea1, SC_PIPING
This example connects to connect point two of a piping component named olet01 in piping
design area pdarea1.
FR, U_NAM/REF3=in05a1, SC_MODEL=pipe01, SC_INSTR
This example connects to connect point three of an instrument component named in05a1 in
piping model pipe01.
Tap placement is a special case. The supported movement options are marked by *.
Taps use the vector- angle-vector value to determine the offset from the reference connect
point. Taps use the DC= delta value to determine the offset from the reference connect point.
Refer to the discussion of placement options for more information on taps.
15
SHIFT
The SHIFT command is used to save the location of the active point and then move the active
point to a specified new location. The saved point can be used with a subsequent JOIN
command to sketch a segment back to that point.
Syntax
SHIFT, movement option [& movement option] [,data option]
The available movement options are the same as those discussed for FR.
JOIN
The JOIN command is used in conjunction with the SHIFT command. It sketches a segment
back to the coordinate point saved by the last SHIFT command. There are no options for this
command.
Syntax
JOIN
MOVE
The MOVE command sketches a segment from the active point to a specified location.
Syntax
MOVE, movement option [& movement option] [,data option]
The available movement options are the same as those discussed for FR. You can specify
active segment data for the purpose of creating an attribute break, using the data options.
Data Options for Movement Commands

The following data options can be added to the command line for the FR, SHIFT, and MOVE
commands. JOIN has no options.
PID=node1-node2
This option transfers P&ID data, identified by the two nodes, to the active segment. This is the
only method of P&ID transfer supported by the Alphanumeric Piping Language. The Unit
Number parameter for the segment involved in the transfer of data must be defined (in entity 12
attribute 4) and match that of the P&ID data. Example:
PID=010A-010B
E#eA#a=value
This option defines the value for a specified segment attribute. For a code-listed attribute, you
can specify the integer value or the code list text. Example:
$DEGF$,E#12A#44=1
E#12A#25=60DEGF
Translated by the system this would be
E#12A#25=60,E#12A#44=1
FLO+
FLOFLO=
These options define the flow direction for the active segment. Example:
16

PLACE, PF=6Q2C01, FLO+
INT=R
INT=B OUT=R
OUT=B
These options establish the in and out directions for use in connecting to a specific CP of a
branch component. R indicates a point on the Run and B indicates a point on the Branch. The
system determines the appropriate CP number that this represents.
REF=n
Where n is a number from 0 to 5. This option refers to the CP of the last component placed
and uses this point as a reference point from which the move is made. If an F precedes the
connect point number (REF=F1), the face of flange CP (1-5) is used as the reference point from
which the move is made.
REF=name
where name is a previously named point. This option refers to a previously named point and
uses this point as a reference point from which the move is made.
NA/REFX=name
This option names the active point resulting from the move.
PLACE
The PLACE command is similar to the Place Component graphics command. It enables you to
place piping, components, instruments, engineered items, and taps.
Syntax
PLACE, placement option [data option]
Options
PP, L=length -- place pipe of specified length
PC=item_name -- place component by item name
PI=tag_number
PI=instrument_name -- place instrument by tag number or by name (if the tag number is not
found)
PS=tag_number
PS=specialty_item_name -- place specialty by tag number or by name (if the tag number is not
found)
Instruments or specialty items that are placed by user-defined (out of spec) data require
the name instead of the tag number. The data options used will determine if an item is
user-defined.
PPS=pipe_support_model_code -- place pipe support by model code. For logical pipe
supports use PSL as the model code.
PF=flange_item_name -- place flange by item name. This option allows correct option code
selection to mate to a previously placed component, as in graphics)
PB=angle -- place branch by accessing the branch table (where angle indicates the branch
table: 90, 45, ...)
PIB -- place an isometric limit break. This symbol is placed last after automated placement. The
system places an isometric limit break in both items at the connection. If the break is placed at
the end of line, the system reports an error in placing the second break. This error can be
disregarded.
17

PFW -- place a field weld. This symbol is placed last after automated placement. The system
places a field weld in both items at the connection. If the weld is placed at the end of line, the
system reports an error in placing the second weld. This error can be disregarded.
PT=REF0 through 5 -- place tap at reference connect point. The reference point determines the
initial location of the tap and the initial tap data.
PT=ELB1 or 2 -- place tap at elbow. The tap is placed at the origin of the elbow. (special
calculations required)
The PT option is a specialized placement command that uses both movement options and data
options. The initial reference point determines both the tap location and the tap data. The
movement options for taps are limited to delta movements and are used to determine the
location of the tap relative to the reference connect point in the Plant coordinate system. The
data options are limited and are listed in the placement data options.
Unique Name
You can create a unique name when placing a piping component, pipe, piping specialty, or
instrument in a piping model. The unique name is added to the appropriate relational database
table in the Piping Design Database when the component is placed. The length of the unique
name attribute is defined when you create a project. The default length is 12 characters and it
can be increased to a maximum length of 20. Refer to the Project Administrator Reference
Guide for more information on setting the length of this attribute.
The unique name is considered to be unique within a piping model for the particular type of
component (piping component, pipe, or instrument component) although you may choose to
have it be unique within the project. The latter situation requires care to assign the unique
names such that there are no duplicates from one piping model to the next.
The following is an example of the default keyword for specifying the unique name in a
placement command.
PLACE, PB=90, U_NAM=unique_name, SS=0.75, INT=R, OUT=B, S1=E
After you provide a unique name for a component, it can be used as a connector for the
continuation of that piping network in the following situations.
in the same piping model, using the same Model Builder description
in the same piping model, using a different Model Builder description
in a different piping model within the same project, using a different Model Builder
description
For example, you can uniquely name a branch component, where the branch line is to be
modeled in a different piping model or using a different Model Builder description.
The Piping Model Builder verifies that the unique name is unique within that Model Builder
description for the type of component being placed. Before creating any piping in the model, the
system verifies that the unique name is unique within that specific piping model on the basis of
the type of component being placed. If the unique name is not unique, the system will not place
the component and will terminate with an appropriate error message.
You can change the unique name in the piping model by using the Revise Attributes
command. However, that command will not verify the unique name within the active model or
any other piping model.
18
Placement Data Options

The PIB and PFW placement options have only one data option: REF to locate the point.
Example:
PLACE, PIB, REF=A1
The PT option has both movement options and data options and is a special case for placement
commands. The data options for taps are described below with *.
The following data options are available for all placement options (other than PT, PIB, and
PFW):
PID=node1-node2
This option transfers P&ID data, identified by the two nodes, to the active segment. This is the
only method of P&ID transfer supported by the Alphanumeric Piping Language. The name of the
transfer (.PIP) file must be defined as the active Unit Number parameter for the model. Example:
PID=010A-010B
E#eA#a=value
This option defines the value for a specified segment or component attribute. (For pipe supports
it can be used to define the table 80 attributes. For a code-listed attribute, you can specify the
integer value or the code list text.
OPT=integer
This option defines a commodity option by option code. Example:
PLACE, PC=6Q2C16, OPT=163
* For taps, specify the tap option code if a tap table lookup is to be used for the tap data instead
of the reference connect point. This option must be accompanied by tap size for the tap table
lookup to be completed.
PLACE, PT=REF1, W/DC=0:3 1/2 & D/DC=0:3 5/16, FS=0.75, OPT=691, P1=D
FS=size
This option sets the first size to the specified value (such as 6IN).
This only sets the first size. Use E#12A#11 to set first AND second size.
* Taps use FS=tap size if a tap table lookup is to be used for the tap data instead of the
reference connect point. This must be accompanied by the tap option code for the tap table
lookup to be completed.
SS=size
This option sets the second size to the specified value (such as 3/4IN)
FLO+
FLOFLO=
These options define the flow direction for the component. Example:
PLACE, PF=6Q2C01, FLO+
P1=vector
This option orients the primary axis in the specified direction (E, W, N, S, D, U, or angle as
N30E). Use -P1 as the vector to invert the primary axis.
S1=vector
This option orients the secondary axis in the specified direction (E, W, N, S, D, U, or angle as
N30E). Use -S1 as the vector to invert the secondary axis.
P2=vector
19

S2=vector
These options are used to orient the operator of a valve.
INT=R INT=B
OUT=R OUT=B
These options establish the in and out directions for use in placing or connecting to a specific
CP of a branch component. R indicates a point on the Run and B indicates a point on the
Branch.
When returning to the named run (CP1) of an Olet branch, specify the direction when
moving and do not use AFC.
CP=n
This option places a component by the specified connect point (0 through 5)
CP=Fn
This option places a component by face of flange at the specified connect point (1 through 5).
NA/REFn=name
This option assigns a name to the specified component connect point (0 through 5)
The NA/REFn option is limited to ten characters.
NA/REFFn=name
This option assigns a name to the face of flange at the specified component CP (1 through 5).
NA/REFR=name
NA/REFB=name
This option assigns a name to the Run or Branch CP.
Taps use NA/REFX=name only for naming a tap connect point.
DE
This option places a component at the segment end (without extending the segment) and with
the active connect point set to segment end (placement CP).
DEB
This option places a component at the segment end (without extending the segment). The active
connect point is set to the CP back along the line (not the placement CP).
Specialty Options
The following keywords are used to place instruments and specialty items when the
corresponding data is not to be extracted from the PJS.
TAG=tag_number
This option defines the tag number for user-defined instruments and specialty items.
TUT=tutorial_name
This option defines the name of the tutorial or form used to place a user-defined instrument or
specialty item. This option is required to make the item reconstructable. The actual form fields
(such as dimensions and parameters) are defined by the following keywords.
FEP=first_end_preparation *
SEP=second_end_preparation *
FPR=first_pressure_rating
SPR=second_pressure_rating
FSCH=first_schedule_thickness
SSCH=second_schedule_thickness
20

FSUF=first_table_suffix *
SSUF=second_table_suffix *
DESC="material_description"
The value defined by the DESC variable is added to the approval specialty description
library.
DIMn=dimension_coordinate_value
Where n = 1 to 19. Dimensions 1-5 are used for the body and dimensions 6-19 are used for the
operator.
ANG=angle
Dimension 20 in EDEN language definition.
OPER=operator_type
DRYW=dry_weight_in_active_units
WETW=wet_weight_in_active_units
AREA=surface_area_in_active_units
FAB=fabrication_category *
Those keywords designated with a * are code-listed using the Standard Note Library. You can
specify the code list textual value or the code list number.
The system automatically updates the connect point specification data (such as end prep,
pressure rating, schedule/thickness, and table suffix) to the active design check data for placing
the instrument or specialty. It is not necessary to specify any of the connect point specification
data, unless it differs from the previous component placed or unless the data for second size
differs from the corresponding first size.
Pipe Support Options

The following keywords are used to place pipe supports.
TAG=pipe_support_number
This option is required for pipe supports. It defines the pipe support number for the pipe support
to be placed.
TUT=tutorial_name
This option defines the name of the tutorial or form used to place a pipe support. This option is
required to make the item reconstructable. The actual form fields (such as dimensions and
parameters) are defined by the following keywords.
DIMn=dimension_coordinate_value
Where n = 1 to 19. Dimensions 1-5 are used for the body and dimensions 6-19 are used for the
operator.
ANG=angle
Dimension 20 in EDEN language definition.
DRYW=dry_weight_in_active_units
Example
The following is an example for the placement of a physical pipe support requiring the input of
three dimensions.
21

PLACE, PPS=PSP2, TAG=PS-001, TUT=PSP001, P1=E, S1=D, dim1=4ft, E#80A#12=supp2
The following is an example for the placement of a logical pipe support.
PLACE, PPS=PSL, TAG=PS-001, E#80A#12=commodity_code
Coordinate Values
All coordinates are defined in the Plant Coordinate System. The following operators are allowed
when specifying absolute or delta coordinates:
+ addition
- subtraction
* multiplication
/ division
( open parenthesis
) closed parenthesis
Named points can also be used in the equation as in the following:
MOVE, E/NA=B3 - 2FT
where B3 is a named point. This would move east to the east coordinate of B3 minus 2 feet.
The following keywords can be used in an equation, to facilitate bottom of pipe routing:
POD (for 1/2 pipe OD), FOD (for 1/2 flange OD), ITK (for insulation thickness)
MOVE, U/DC=30FT 9 3/4IN - (POD + ITK)
Negative numbers used in coordinate values must be enclosed in parentheses as in the
following examples:
FR, AFC/DC=(-3FT)
FR, E/DC=B1 - (-B2)
Default Units
FT or M for master units (defined in keywords)
IN or MM for sub units (defined in keywords)
: to separate master and sub units
The following are examples of the different coordinate forms that are allowed by the language:
22
2 sub units of active file
1 5/16
1 and 5/16 sub units
3:
3 master units of active file
5:6
5 master units, 6 sub units of active file
5 1/2:6 3/4
5 1/2 master units, 6 3/4 sub units of active file
2IN
2 inches in any file
3FT
3 feet in any file
4MM
4 millimeters in any file
5M
5 meters in any file
5M 300MM
5 meters and 300 millimeters in any file

3FT 6 1/2IN
3 feet 6 and 1/2 inches in any file
Units can be mixed in equations but not mixed within an individual value.
Default Keywords
$
synonym delimiter
A#
Attribute number
AC
Absolute Coordinate
AFC
Along Flow Centerline vector
ANG
angle
AREA
surface area (in active units of model)
Branch of branch
CP
Connect Point
Down vector
DATE
30 character DATE (currently not used)
DC
Delta Coordinate
DE
Do not Extend segment (active point at placement CP)
DEB
Do not Extend segment (active point Back along line)
DESC
material description
DIMn
dimension parameters, where n may be 1 through 19
DRYW
dry weight (in active units of model)
East vector
E#
Entity number
EQ
Equipment location
FAB
fabrication category
FEP
end preparation for first size (green data)
FILE
piping design FILEname without extension
FLO
FLOw direction
FOD
1/2 Flange Outside Diameter
FPR
pressure rating for first size (green data)
FR
FRom command
FS
First Size
FSCH
schedule/thickness for first size (green data)
FSUF
table suffix for first size (green data)
FT
FeeT (English masterunits)
23
24
HOR
HORizontal plane (xy plane)
ID
IDentifier attribute 1.21 used during deletion
IN
INch (English sub units)
INT
INTo branch
ITK
Insulation ThicKness
JOIN
JOIN command
Length of pipe
Meter (Metric master units)
MM
Millimeter (Metric sub units)
MOVE
MOVE command
North vector
NA
NAme location
OPER
operator type
OPT
OPTion Code
OUT
OUT of branch
Plane intersect
P1
Primary vector (1 = component)
P2
Primary vector (2 = operator)
PB
Place Branch
PC
Place Component
PF
Place Flange
PFW
Place Field Weld
PI
Place Instrument
PIB
Place Iso Break
PID
P & ID Transfer
PLACE
PLACE command
POD
1/2 Piping Outside Diameter
PP
Place Pipe
PPS
Place Pipe Support
PRO
PROject name
PS
Place Specialty (engineered item)
PSL
model code for logical pipe supports
PT
Place Tap
Run of branch
REF
REFerence Point

S
South vector
S1
Secondary vector (1 = component)
S2
Secondary vector (2 = operator)
SC_AREA
search criteria for piping design area
SC_ALL
set default search criteria
SC_INSTR
search criteria for instruments
SC_MODEL
search criteria for piping model
SC_PIPE
search criteria for piping/tubing
SC_PIPING
search criteria for piping component
SEP
end preparation for second size (red data)
SHIFT
SHIFT command
SPR
pressure rating for second size (red data)
SS
Second Size
SSCH
schedule/thickness for second size (red data)
SSUF
table suffix for second size (red data)
TAG
tag number
TUT
tutorial/form name
Up vector
U_NAM
unique name
VER_E
VERtical-East plane (xz plane)
VER_N
VERtical-North plane (yz plane)
West vector
WETW
water weight (in active units of model)
Sample Alphanumeric Piping Language Files

sample_a
$DEGF$,E#12A#44=1
$PSIG$,E#12A#43=1
FILE = *, PRO = *, ID = INPIPE, DATE= 6-DEC-1990
25

FR, E/AC=0 & N/AC=0 & U/AC=0, E#12A#12=1C0031, E#12A#25=60DEGF,
E#12A#24=100PSIG, E#12A#4=01
!FR, E/AC=0 & N/AC=0 & U/AC=0, E#12A#4=01, PID=010A-010B
!FR, EQ=38P-101B/DISCH, E#12A#25=60DEGF, E#12A#24=100PSIG, E#12A#4=01
PLACE, PF=6Q2C01, FS=4, SS=4, FLO+, P1=U
!PLACE, PF=6Q2C01, FLO+
! Option Code determined by PF
PLACE, PC=6Q2C23, FS = 6, CP=2, NA/REFR=A10
PLACE, PT=REF2, E/DC=3 5/16IN & U/DC=3 1/2IN, FS=0.75, OPT=691, P1=E
PLACE, PFW
PLACE, PC=6Q3C88
PLACE, PC=6Q1C80, S1=N
PLACE, PI=4CYL4, TAG=38-PI-6, TUT=INB009, dim1=1ft, dim2 = 7in, dim3=3in,
ang=120, fep=MTE,dryw=1000.5, wetw=400.3, area=24.75, S1=N
FR, NA=A10
PLACE, PF=6Q2C01, CP=2
PLACE, PC=6Q1C38
PLACE, PF=6Q2C01
PLACE, PP, L=6IN, NA/REF2=B1
FR, afc/dc=(-3IN)
! Branch must be placed in middle of pipe
PLACE, PB=90, SS=0.75, INT=R, OUT=B, S1=E
! Branch is in pipe no name
necessary
PLACE, PC=6Q3C88
FR, NA=B1
PLACE, PC=6Q1C01, S1=W
! If needed Place chain wheel in
graphics
MOVE, U/DC=1FT 9 9/16IN
MOVE, W/DC=1FT, NA/REFX=B2
PLACE, PB=90, SS=0.75, INT=R, OUT=B, S1=U
! Name was placed at end
of previous segment
PLACE, PFW
PLACE, PC=6Q3C88
FR, NA=B2
!MOVE, W/EQ=38P-101A/DISCH
MOVE, W/DC=5:
!SHIFT, EQ=38P-101A/DISCH
SHIFT, D/DC=10FT
!PLACE, PF=6Q2C01, FLO+
PLACE, PF=6Q2C01, FS=4, SS=4, FLO+, P1=U
PLACE, PC=6Q2C23, FS = 6, CP=2, NA/REFR=A11
PLACE, PT=REF2, W/DC=3 5/16IN & U/DC=3 1/2IN, FS=0.75, OPT=691, P1=W
PLACE, PT=REF2, E/DC=3 5/16IN & U/DC=3 1/2IN, FS=0.75, OPT=691, P1=E,
NA/REFX=TAP1
FR, NA=A11
PLACE, PC=6Q1C38
PLACE, PF=6Q2C01
PLACE, PP, L=6IN, NA/REF2=B4
26

FR, afc/dc=(-3IN)
! Branch must be placed in middle
of pipe
PLACE, PB=90, SS=0.75, INT=R, OUT=B, S1=E
! Branch is in pipe no
name necessary
PLACE, PC=6Q3C88
FR, NA=TAP1
PLACE, PFW
PLACE, PC=6Q3C88
PLACE, PI=I3WAY, TAG=39-PI-9, TUT=INB003, dim1=3in, dim2 = 3in, dim3=3in,
dim6=14in, dim7=3in, fep=MTE, fpr=800,fsch=S-STD, fsuf=5, fab=7, oper=27, dryw=1000.5, wetw=400.3,
area=24.75,S1=S, p2=u,s2=e
FR, NA=B4
PLACE, PC=6Q1C01, S1=W
! If needed Place chain wheel
in graphics
JOIN
MOVE, W/DC=3FT 3 1/4IN
PLACE, PFW
PLACE, PC=6Q2C76, S1=S
MOVE, S/DC=420FT 3 3/8IN - 418FT 3 3/8IN
PLACE, PPS=PSP2, TAG=test1, TUT=PSP001, P1=E, S1=D, dim1=15ft,
E#80A#12=supp1
MOVE, S/DC=15FT 5 5/8IN - 2FT
PLACE, PC=6Q2C06, CP = F1, OUT=B, S1=W, NA/REF1=FL1, DE
FR, NA=FL1
PLACE, PC=6Q2C06, S1=W, INT=R, OUT=B, NA/REFR=FL2, NA/REFF1=TAP2
PLACE, PC=6Q3C88
FR, NA=FL2
MOVE, S/DC=3FT 6IN, REF=TAP2
MOVE, W/DC=1FT 3IN
PLACE, PIB
MOVE, W/DC=9IN
MOVE, D/DC=6FT 3 1/16IN - 2FT 11 3/4IN, NA/REFX=B5
PLACE, PB=90, SS=4, S1=E, INT=R, OUT=B
! Name at previous
segment end
PLACE, PC=6Q1C11, S1=S, NA/REF2=V1
FR, NA=B5
SHIFT, afc/dc=2FT 11 3/4IN
PLACE, PF=6Q2C01, NA/REF1=FL3, FS=4, P1=-P1, CP=F1
PLACE, PC=6Q2C23, FS=6, SS=4, CP=2
JOIN
27

FR, NA=FL3
PLACE, PF=6Q2C01
PLACE, PC=6Q2C76, S1=E, NA/REF0=SUPP2
PLACE, PC=6Q2C24, FS=4, SS=3, S1=U, NA/REFR=A12
PLACE, PT=REF1, E/DC=2IN & D/DC=2 1/4IN, FS=0.75, OPT=691, P1=D
PLACE, PFW
PLACE, PC=6Q3C88
FR, NA=A12
!PLACE, PI=PRV02
!PLACE, PI=PRV02, CP=2
PLACE, PF=6Q2C01
PLACE, PC=6Q2C24, FS=4, SS=3, CP=2, S1=U, NA/REFR=A13
PLACE, PT=REF1, W/DC=0:2 & D/DC=0:2 1/4, FS=0.75, OPT=691, P1=D
PLACE, PFW
PLACE, PC=6Q3C88
FR, NA=A13
PLACE, PS=YSTR, TAG=SPECIAL_ENGR, TUT=PSB010, dim1=18in, dim2 = 8in,
dim3=9in, fep=BE, fpr=150,fsch=S-STD, fsuf=5, fab=7, dryw=1000.5, wetw=400.3, area=24.75, S1=U
PLACE, PB=90, S1=U, NA/REFB=B6, INT=R, OUT=R
PLACE, PC=6Q2C23, FS=6, SS=4, CP=2, NA/REFR=A14
PLACE, PT=REF1, W/DC=0:3 1/2 & D/DC=0:3 5/16, FS=0.75, OPT=691, P1=D
PLACE, PFW
PLACE, PC=6Q3C88
FR, NA=A14
PLACE, PB=90, S1=U, NA/REFR=B7, INT=R, OUT=B, NA/REF0=SUPP3
PLACE, PC=6Q1C01, S1=S, U_NAM=A14_EXT
FR, NA=B7
PLACE, PC=6Q2C76, S1=U
MOVE, U/DC=13FT 9 5/16IN
PLACE, PC=6Q2C76, cp=0, S1=N
PLACE, PFW
MOVE, N/AC=30FT 1 5/8IN
MOVE, P/U/HOR= 30FT + (POD + ITK)
MOVE, E/DC=4FT 10 3/4IN
MOVE, U/DC=4FT 11 3/8IN - 5 1/2IN, NA/REFX=B8
PLACE, PB=90, FS=6, SS=3/4, S1=E, INT=R, OUT=B
! Name at
previous end of segment
PLACE, PFW
PLACE, PC=6Q3C88
PLACE, PC=6Q1C76
28

FR, NA=B8
MOVE, U/DC=5 1/2IN
PLACE, PF=6Q2C01, CP=F1, DE
PLACE, PC=6Q2C10, S1=E
PLACE, PC=6Q1C01, S1=N45E
MOVE, U/DC = 5:
MOVE, U30W60N/DC = 5:3
PLACE, PB=90, U_NAM=B8_EXT, S1=E, INT=R, OUT=B
FR, NA=V1
MOVE, E/NA=B6
MOVE, NA=B6
FR, NA=SUPP2
E#80A#12=supp2
FR, NA=SUPP3
E#80A#12=supp3
sample_b
FILE = *, PRO = *, ID = INPIPE2, DATE= 8-NOV-1991
FR, U_NAM/REF2 = B8_EXT, SC_PIPING, SC_MODEL=perry
! other search options SC_AREA=<area_name> or SC_MODEL=<model_name> and/or
SC_(ALL,PIPE,INST)
MOVE, U30W60N/DC = 3ft
MOVE, U/DC = 3FT, NA/REFX= TOP
FR, U_NAM/REF2 = A14_EXT
PLACE, PF=6Q2C01
MOVE, U/DC = 10Ft
MOVE, N/U_NAM/REF0=B8_EXT
MOVE, U/NA=TOP
SHIFT, NA=TOP
JOIN
29
30
SECTION 3
Piping Model Builder

The Piping Model Builder is used to process alphanumeric piping language files for use in
creating model graphics. This operation is processed as a batch job. You can define a list of
model builder files and their corresponding model numbers to be processed together.
The entire list displayed in the List of Model Builder Jobs field is processed when you select
Confirm ().
The system verifies that you have write access to the specified model files before processing
them.
Additional Information
Refer to the article on the Alphanumeric Piping Language (on page 9) for more information on
the files processed by the Piping Model Builder.
If the executable is stopped while the file is opened, the terminal FB subprocess must
be stopped by logging out or stopping the subprocess.
Add -- Adds a row in the List of Model Builder Jobs and copies the active model number into
the new row. Edit is automatically activated so that you can edit the new entry.
Edit -- Places the highlighted field from the List of Model Builder Jobs into the fields on the left
to allow you to edit them. Your changes are automatically updated when you press <Return>.
Delete -- Allows you to specify the field in the List of Model Builder Jobs to delete.
Reorder -- Allows you to reorder the file names in the list file. You select the entry that you want
to move and place a data point over the field where you want the entry to be placed.
31

Read List File -- Allows you to define the list file to be displayed in the List of Model Builder
Jobs field.
Write List File -- Allows you to write the displayed list to a file. Also, when you have selected
the Read List File option and want to return to the main form without reading a new file, use this
option.
Submit Batch Immediately / Delayed Batch Submit Time -- Allows you to submit the job
immediately or delay it by specifying a later time. Set the time of day to submit the batch job.
Model Builder File Name -- Key in the name of the language file to be processed. If you are
generating a list of files and model numbers, select the Add command, and the system will add
the file name and the active model number to the list of model builder jobs.
Directory Path -- Key in the file path and node name for the location of the model builder
language file.
Node Name -- Key in the node name where the model builder file resides.
32

Model Number -- Place a data point in this field. The system will display all of the design areas
in the project. Select a design area for the model to be processed and select the model to
receive the graphics.
Graphics Placed By Piping Model Builder
33
34
Index
A
Alphanumeric Piping Language 9

Requirements 9
The Language File 10
C
Command Lines 13
Coordinate Values 22
D
Data Options for Movement Commands
16
Default Keywords 23
Default Units 22
F
FR 13
H
Header Line 11
J
JOIN 16
M
MOVE 16
P
Piping Model Builder 31
Piping Model Builder (PD_Model) Overview
7
PLACE 17
Placement Data Options 19
Preface PDS 5
S
Sample Alphanumeric Piping Language
Files 25
SHIFT 16
Synonym Line 11
35

PDS Piping Model Builder PD Model

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PDS Piping Model Builder PD Model

Încărcat de

Drepturi de autor:

Formate disponibile

Plant Design System (PDS)

Piping Model Builder Reference Guide

Version 2011 (V12)

U.S. Government Restricted Rights Legend

Warranties and Liabilities

Plant Design System (PDS) Piping Model Builder Reference Guide

Plant Design System (PDS) Piping Model Builder Reference Guide

List of PDS Documentation

DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide

Plant Design System (PDS) Piping Model Builder Reference Guide

Plant Design System (PDS) Piping Model Builder Reference Guide

Piping Model Builder (PD_Model)

Plant Design System (PDS) Piping Model Builder Reference Guide

Piping Model Builder (PD_Model) Overview

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Alphanumeric Piping Language Requirements

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

The Language File

Language File Conventions

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Instructions are shown in a special typeface.

$ -- Synonym keyword. The $ must be the first character in the line.

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Data Options for Movement Commands

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Placement Data Options

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

Pipe Support Options

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

2 sub units of active file

1 and 5/16 sub units

3 master units of active file

5 master units, 6 sub units of active file

5 1/2 master units, 6 3/4 sub units of active file

2 inches in any file

3 feet in any file

4 millimeters in any file

5 meters in any file

5 meters and 300 millimeters in any file

Plant Design System (PDS) Piping Model Builder Reference Guide

Alphanumeric Piping Language

3 feet 6 and 1/2 inches in any file

Along Flow Centerline vector