Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Introduction ................................................................................................................................................ 1
Project Organization............................................................................................................................... 1
Reference Data Overview ...................................................................................................................... 2
Piping Job Specification Introduction ............................................................................................. 4
Graphic Commodity Data Introduction ........................................................................................... 4
Material Description Data Introduction ........................................................................................... 4
Standard Note Library Introduction................................................................................................. 5
Label Description Library Introduction ........................................................................................... 5
Piping Assembly Library Introduction ............................................................................................ 6
Reference Database Introduction ........................................................................................................... 6
Delivered Reference Data ...................................................................................................................... 6
Reference Data Setup ............................................................................................................................. 7
Introduction
Welcome to the Reference Data Manager (PD_Data) module of the Plant Design System of
software. Intergraph's plant design software can be used to design any type of plant from
petrochemical plants, offshore platforms, chemical and pharmaceutical plants, consumer
products (food, beverages, cosmetics, soap, paper, and so forth), to power plants, waste water
treatment plants, and cogeneration facilities.
Specifically, the Plant Design System (PDS) integrates many discipline-specific software
modules; these modules automate the many phases of a plant design project. Reference Data
Manager (PD_Data) is one of these modules.
In PDS, placement of piping components is driven by the specification. The PDS reference data
provides the selection criteria for the piping commodity items that are found in the piping job
specification and the piping commodity libraries that are delivered with the product. This data is
contained in the reference database (RDB) and can be used by other projects.
The Reference Data Manager (PD_Data) is specifically designed to define and modify the
reference data for the PDS 3D modules. This reference data ensures consistency in the
definition of piping specifications and commodity libraries. It is used to control and standardize
the PDS 3D modules to reflect company practices and standards.
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 project is a convenient grouping of either all or part of the items that constitute a plant. The
project is the fundamental structure for working in PDS. Each project contains all the
information required to work in a PDS task.
The Project Administrator controls the creation and modification of Piping projects. Each
Piping project consists of a project control database, project design database, piping and
equipment models, reference models (structural, HVAC, and electrical 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.
A project and all of its accompanying files must be defined with the Project Administrator
before you can use any of the other 3D PDS modules. Refer to the Project Administrator
Reference Guide for more information on setting up a project.
Spec/Material Database
Piping Materials Class Data (201) (on page 34)
Piping Commodity Specification Data (202) (on page 38)
Piping Specialty Specification Data (203) (on page 45)
Instrument Component Specification Data (204) (on page 48)
Tap Properties Data (205) (on page 51)
Piping Commodity Size-Dependent Material Data (211) (on page 54)
Piping Commodity Implied Material Data (212) (on page 56)
Component Insulation Exclusion Data (231) (on page 59)
Flange Insulation Exclusion Data (232) (on page 61)
The following figure illustrates the various pieces of reference data required to place a 6" gate
valve in a piping model and report on the placed component. It depicts how the various parts that
make up PDS work together. Whenever possible, this placement example will be used
throughout the rest of this document. For example, the discussion of the physical dimension
tables will use the tables called to place the gate valve as examples.
See Also
Project Organization (on page 1)
Reference Database Introduction (on page 6)
Delivered Reference Data (on page 6)
Reference Data Setup (on page 7)
PDS Environment
The PDS 3D software supports a variety of applications. All the supported applications use a
common interface that is controlled by the PD Shell program. This ensures consistency across
applications and minimizes the amount of time required to learn the product.
The PDS 3D modules provide a simple user interface through extensive use of forms. The
modules also provide an on-line Help capability for easy access to information while working in
the product.
The PD_Shell Environment and all batch jobs in the PDS 3D products interface to Intergraph's
Network Licensing System.
See Also
PD Shell (on page 9)
Help (on page 16)
PD Shell
The PD Shell program provides access to the various functions that are associated with the PDS
3D Modules. You can access the Plant Design System Environment form by clicking Start >
All Programs > PD_Shell > PD_Shell. This executes a control script that defines all of the
environment variables that are needed to run the product, and it identifies the location of the
product files. These files can be located on the workstation or a server on the network. See
pds.cmd for more information on this file. The script also activates the Plant Design System
Environment form.
To make colors easier to read on flat screens and projectors, a zip file with modified color for
PDS forms is delivered as alternatecolorfb.zip.
This form identifies the active project(s) and provides access to all the PDS functions.
Schematics Environment Provides access to the PDS 2D modules that are used to create and
modify piping and instrumentation diagrams, process flow diagrams, and instrumentation
database records.
Equipment Modeling Provides access to the Equipment Modeling module, which provides
an interactive graphics environment that is used to create and revise equipment model graphics
and database information.
FrameWorks Environment Provides access to the FrameWorks module, which provides an
environment that is used to create and revise structural models, create and revise structural
drawings, and propagate structural models.
Piping Designer Activates an interactive command environment that is used to create piping
and in-line instrumentation in the model; revise existing model graphics and database
information; and verify the integrity of the data in the model.
Electrical Raceway Environment Provides access to the Electrical Raceway module, which
provides an interactive environment that is used to create and revise raceway models and access
raceway utilities.
Piping Design Data Manager Provides access to a set of options that are used to verify the
integrity of the graphic and database information that is associated with a model.
Piping Model Builder Enables you to create piping graphics from a nongraphics
environment. This module is used with PD_Design to create an accurate 3D model of the piping
network.
Pipe Support Designer Activates an interactive command environment that is used to create
pipe supports in the model, and revise existing pipe support model graphics and database
information.
Pipe Stress Analysis Activates a set of forms that are used to extract information from piping
models for input to third-party pipe stress analysis products.
Interference Manager Activates a set of forms that are used to check for interferences
among project models and to control approved interferences.
Isometric Drawing Manager Activates a set of forms that are used to extract isometric
drawings from piping models and to review or plot the created isometric drawings.
Drawing Manager Activates a set of forms that are used to create and manipulate drawings
and drawing views; provide access to the interactive graphics environment for drawings; and
provide access to a plot manager and vector hiddenline manager.
DesignReview Integrator Activates a set of forms that are used to extract information to
form label files for use in SmartPlant Review and to review data from a SmartPlant Review
session.
Report Manager Activates a set of forms that are used to create and revise report format
files and report on information in a project including Material Take-Off reports.
Project Administrator Provides access to a set of forms that are used to create a project,
create and revise project files, define project seed data, and control the project.
Reference Data Manager Provides access to a set of forms that are used to control the
reference data for a project including Piping Job Specification data, Graphic Commodity Data,
Alphanumeric Commodity Data, Standard Note Library, Label Description Library, and Piping
Assembly Library.
User ID Used for access control. This field also sets the Review User ID for use in the
Interference Manager module.
If access control has been defined, you must key in a valid user ID as defined by your system
manager to gain access to the projects. Refer to Access Control Manager, page 467, for more
information on using access control.
If access control has not been defined, no entry is required for this field.
Password Key in the password for the specified user ID.
Project List Field Displays the defined projects for the network and allows you to select the
active project. The system lists all the defined PDS projects (2D-only, 3D-only, and 2D & 3D).
An error is displayed if you select an option that is incompatible with the active project. For
example, if the active project is a 2D-only project, you cannot access the Interference Manager
module.
If access control has been defined, only those projects for which you have some level of access
are displayed.
Message Area Displays prompts and messages that are associated with the active process.
Error messages are displayed in red.
Standard Commands
The PD_Shell forms have a set of standard buttons in the upper right corner of most of the form
windows. The available commands vary from form to form depending on the type of operation.
The Help button activates on-line Help for the
active form. Help remains active until you
delete the Help window.
The Shell button exits the active form and
returns control to the base manager that is
associated with the active form. For most
forms this returns to the Plant Design System
Environment form.
The Top button exits the active form and
returns control to the top form of the active
branch.
The Cancel button cancels or exits from the
active form. Control returns to the
immediately preceding form in the hierarchy.
Scrolling List
Some screen menus have a scrolling list of
projects or applications. You need to scroll a
list only if more options are available than can
be displayed in the window. To scroll a list,
select the arrow buttons on the side of the list.
The list scrolls up or down depending on
which arrow you select.
The scrolling list has an arrow pointing
up and an arrow pointing down. These arrows
scroll lists line by line. There is a button that
slides between these two arrows to indicate
your position on the list. To page through the
list, select the space above or below the
sliding button. The list pages up or down
accordingly.
You can also select the slider and, while
pressing <D>, slide the button up or down the
bar. The items scroll through the window as
you move the button. The size and position of
the button on the scroll bar is an indication of
the number of lines and the relative position
within the list.
All commands that display a list of design
areas or models order the list
alphanumerically by the design area number
or model number in ascending order.
In some 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 the Accept button.
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
Toggle
A toggle field on a screen menu enables you
to select one of two possible choices, one of
which is always displayed. Place a data point
on the toggle field to toggle between the two
choices.
Roll-Through List
A roll-through list shows one choice at a time
of a list that can be several items long. Place
a data point on the roll-through list to scroll
through the available options. The option
displayed is active.
Standard Window Icons
When using this software, you can press <D>
along the edge of a form or any area not
occupied by a button, key-in field, or other
gadget, to display a box of icons. You can
manipulate form windows just like any other
workstation window.
The following list defines the available
window icons.
Collapse/Restore
Repaint
Pop-to-bottom
Modify/Resize
Pop-to-top
Restore Size
Batch Processes
When you install the PDS 3D applications, the system creates the necessary batch queues for
that application. Refer to Loading Products in the Project Administrator Reference Guide for a
listing of the batch queues.
PDS 3D uses these batch queues to allow you to continue working in the environment while the
system processes a request. Many of the batch processes can be delayed for submission at a
specified time.
Help
On-line Help is a special feature of your application software. Help provides
instant access to information from the application reference documents, such as
command descriptions and explanations, prompt sequences, and much more.
There are several avenues you can take to find information about a command or subject. For
instance, Help provides
A table of contents that lists subjects by topic and subtopic (in a hierarchy).
An alphabetized index of every command or subject that has been documented for the
software.
A glossary to help you become familiar with product-specific terms.
The ability to move up, down, back, and forth through Help by using cross-references and
links to primary and secondary commands.
The ability to quickly search through Help for information on a specific subject or
command.
When you first select Help, the Help Table of Contents is displayed in a pop-up window. Select
a topic from this list or select a command from the menu to display an article in the pop-up
window.
Whenever possible, PDS Help is context sensitive. For example, if you select the help icon for a
given form, Help that is specific to that form is displayed.
The Help window has buttons that you can use to manipulate either Help or the window itself as
follows:
Scroll Bar - Moves up or down in an article that is displayed in the Help window.
Help Command Buttons - Enable you to move around in the Help file.
Cancel or File > Exit - Exits Help and closes the Help window.
1. Select the Help button from the command window or form.
If you select Help while using a command, help on the active command is displayed. If no
command is active, the table of contents is displayed.
Data Security
The Reference Data Manager provides data security features for the following reference data
libraries in the event of accidents such as, electrical power surges and network failures. These
features also protect the libraries in the event that a library is being shared by multiple projects,
and different users in different projects mistakenly attempt to revise one of the libraries
simultaneously.
Graphic Commodity Library
Physical Data Library
Piping Job Specification Table Library
Short Material Description Library
Long Material Description Library
Specialty Material Description Library
If you are certain that the warning results from a previous unusual exit, make one of the
following decisions.
If a corrupted library (including the corresponding source library and revision library)
has been restored from a backup, select the accept option.
If you are concerned with the integrity of the library for any reason, select the exit
option. Then restore the library, the corresponding source library, and the corresponding
revision library to their previous state (before the last revisions).
If you are aware that a different user may be revising that library within a different project,
select the exit option.
This feature requires that PDS users have write access to the directory in which the
libraries reside. The Reference Data Manager will display an error message, if the user does
not have privileges for write access to the applicable directory and the user will not be able
to revise that library.
When a PDS user exits a data creation or revision session, the Reference Data Manager verifies
the integrity of the binary tree structure within the library. The system displays an error if the
Reference Data Manager determines that an error exists in the binary tree structure. In this event,
you should contact Intergraph immediately for assistance in repairing the library.
Operating Sequence
1. Select Default Project Control Data from the Reference Data Manager form to define the
default location for the RDB source files.
2. Select the field to be defined and key in the location of the source files and the associated
node name.
Piping Eden Path / Node The default location for the Eden source files.
Dimension/Spec Table Path / Node The default location of the Dimension Table
and Spec Table source files.
Piping Spec Path / Node The default location for the neutral files to be used to load
the Specification/Material Reference Database and Material Description Libraries.
Assembly Path / Node The default location for the Piping Assembly Language
source files.
Standard Note Library Path / Node The default location for the Standard Note
(code list) source files.
Equipment Eden Path / Node The default location for the Equipment Eden source
files.
TDF Table Path / Node The default location for the Equipment table definition files.
Model Builder Path / Node The default location for the model builder language
source files.
3. Accept any changes to the Project Control Data.
Operating Sequence
1. Select Reference Database Management Data from the Reference Data Manager form.
The system identifies the file for the selected field in the fields at the bottom of the form.
There are no default settings for these files; you must define the applicable file locations
before you can continue.
Material/Specification Reference Database This field identifies the Material
Reference Database for the project. Refer to the Project Setup Manager in the Project
Administrator Reference Guide for more information on this database.
Piping Job Specification Tables (on page 131) Library This field identifies the
location of the Piping Job Spec Table library.
Short Material Description Library (on page 277) This field identifies the library
which contains the short bill-of-material description for all piping commodity items and
the BOM description addenda for taps.
Long Material Description Library (on page 283) This field identifies the library
which contains the long BOM description for all piping commodity items. The long
BOM description is only used for requisitions.
Specialty Material Description Library (on page 286) This field identifies the library
which contains the BOM description for engineered items, in-line instruments, and pipe
supports. This library tends to be customer-specific.
Standard Note Library (on page 335) This field identifies the location of the standard
note library.
Label Description Library (on page 347) This field identifies the location for the
label description library.
Piping Assembly Library (on page 379) This field identifies the location for the
Piping Assembly library. This library contains the symbol definitions for assemblies.
Graphic Commodity Library (on page 183) This field identifies the library which
contains the Eden modules used to place components in the model.
Physical Data Tables (on page 194) Library These fields identify the library files
which contain the physical data tables for a range of geometric industry standards.
Commodity Synonym Library This field identifies the user-defined library which
contains the map for translating the default piping commodity names used in the P&ID
Task to names specified by the user in the Piping Job Specification.
Orthographic Drawing Borders This field identifies the drawing border files to be
used when creating drawings. A set of border files are delivered to the directory
win32app\ingr\pddraw\border. You must specify which style of borders is to be used.
3. Key in any changes to the selected RDB files. Refer to Delivered Reference Data (on page
6) for a listing of the delivered reference data files.
If you specify an unapproved file, the system will use the unapproved file for all Reference
Data Manager operations (such as revising entries in a library.)
Refer to the Project Data Manager in the Project Administrator Reference Guide for
information on setting the choice of data for a model file or drawing.
4. You can select Approved --> Not Approved to copy the approved definition of the selected
RDB file to the Not Approved fields. Select confirm to update the information.
Refer to the individual managers for information on posting the unapproved information to
the approved files.
5. You can select Default All Library Locations to define a default location for all approved
and all unapproved library files.
6. You can select Copy All Standard Libraries to copy the delivered library files to a
specified location.
7. Select Accept following each change to the reference data to accept the specified file
location.
THEN
Select Cancel to exit the form.
The text to be used for the <standard> is determined in the following manner.
Practice Prefix
U.S. Practice us
European - DIN din
European - British Standard bs
European - Practice A eua
European - Practice B eub
International - JIS jis
International - Australian aus
International - Practice A ina
International - Practice B inb
Company Practice cmp
The text to be used for the standard is determined in the following manner.
Practice Prefix
U.S. Practice us
European - DIN din
European - British Standard bs
International - JIS jis
International - Australian aus
The list of available products is determined from the list of exported variables as specified in the
pds.cmd shell script. Therefore, this command presently searches for the following exported
variables:
Product Practice
RD_USRDB U.S. Practice
RD_DINRDB DIN
RD_BSRDB British Standards
RD_JISRDB JIS
RD_AUSRDB Australian
The file specification recorded in the Project Control Database, and not that of the library in the
delivered product, will be used for the destination library.
If the RDB product resides on a remote server (or workstation), you must manually mount
the directory that includes the RDB product and change the exported variable in the pds.cmd
shell script accordingly.
The system will display an error message for any of the following conditions.
Any of the active Reference Database libraries for the project are in use (locked). None of
the libraries are copied.
The network address for any of the active Reference Database libraries for the project is
undefined. None of the libraries are copied.
The network address and path name for any of the active Reference Database libraries for
the project cannot be mounted. None of the subsequent libraries are copied.
Attribute Types
The following conventions are used to designate the field type for database attributes.
character(n) alphanumeric field n characters in length
integer long (double word) integer
short short integer
double real (floating point) value
standard note Standard Note Type for code-listed attribute
nnnn
Code-Listed Attributes
A code-listed attribute is an attribute whose value must be defined using one of the selections
from a particular code list in the Standard Note Library. In the following database description,
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) , SN 125
indicates that fluid_code is defined in terms of code list numbers belonging to Standard Note
125, Fluid Code/Connector Type. A possible entry for this attribute would be 197 for chlorine
gas (GCL). Refer to Appendix: Codelists (see "Table Checker" on page 295) for a listing of the
code list sets associated with PDS 3D.
NPD Units
Nominal piping diameter is defined as a special coded number (NPD units) with the following
formula.
For metric units, the coded number equals the size (in millimeters).
For English units, the coded number equals the size (in inches) times 32 plus 5000.
This allows nominal piping diameter to range from 1 mm to 5000 mm in 1 mm increments for
metric units, and to range from 1/32" to at least 200" in 1/32" increments for English units.
SEQUENCE Statement
The SEQUENCE statement is an optional statement which can be used to define the order of the
parameters in the neutral file. If the SEQUENCE statement is used, it must be placed before any
entries. The SEQUENCE statement can only be used once per file.
If the SEQUENCE statement is omitted, it is assumed that the parameters appear in the
order defined by PDS.
Format
SEQUENCE= P1 P2 P3 P4 ... Pn
where:
SEQUENCE= keyword which can be entered in either upper or lower case
letters.
P1,P2,...Pn parameters 1 through n. The values of P1...Pn are the
parameter numbers assigned by PDS, and their position tells the
system the order in which to enter them.
Examples
SEQUENCE= 5 3 4 1 2
The first parameter read corresponds to PDS parameter #5, the second to PDS parameter #3, the
third to PDS parameter #4, the fourth to PDS parameter #1, and the fifth to PDS parameter #2.
You can use the convention *Pn to indicate an attribute that is not defined in the neutral file. All
of the *Pn attributes should be placed at the end of the SEQUENCE statement following the list
of included attributes. For example,
SEQUENCE= 2 3 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 *4 *5 *21 *22
ORDER Statement
Neutral files translated from VAX PDS data may contain an ORDER statement rather than a
SEQUENCE statement. This statement performs the same function as the SEQUENCE
statement except that it lists the order of the attributes as they were defined in the VAX Piping
Job Specification Database.
TABLE Statement
The TABLE statement defines a table name to be associated with a particular set of data. The
active table name remains unchanged until another TABLE statement is encountered. The
TABLE statement can be used more than once in a neutral file.
Format
TABLE= table_name
where
TABLE= keyword which can be entered in upper or lower case
letters.
table_name the name of the table associated with the following data.
There must be at least one/two spaces (depending on the default spacing selected) between the
keyword and the table_name.
For example, the Tap Properties Table below defines two tables (C001, and C002) by using the
Table keyword to segregate the data for each table being defined.
Double_Spacing
Order= 2 3 5 4 6 7
! By=GJH Ckd By=RJW Rev=2 Date=12-May-1995
Table= C001
! Description= SWE CL3000 default taps
! Diam Opt Rating Prp Sc/Th Tap Code
0.375 691 - 591 NREQD E$37591XXX
> 0.5 1 CL3000 421 NREQD E$50421064
0.5 691 - 591 NREQD E$50591XXX
:
:
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
Table= C002
! Description= SWE CL6000 default taps
! Diam Opt Rating Prp Sc/Th Tap Code
0.375 691 - 591 NREQD E$37591XXX
> 0.5 1 CL6000 421 NREQD E$50421072
0.5 691 - 591 NREQD E$50591XXX
:
:
34 691 - 591 NREQD E034591XXX
36 691 - 591 NREQD E036591XXX
42 691 - 591 NREQD E042591XXX
48 691 - 591 NREQD E048591XXX
7. mater_of_construct, character(6)
This attribute defines the materials of construction class for the piping materials class. This
code has a detailed definition outside the scope of PDS that represents the decision of the
Project Metallurgist regarding the piping system. It is required for reporting and making
matches and comparisons with values for this parameter from the Piping Design Database.
This parameter includes the material code.
8. corrosion_allow, double
This attribute defines the corrosion/erosion allowance that applies to the piping materials
class. It is required for reporting and to calculate the wall thickness of piping components
whose thickness is not specifically included in the piping materials class.
9. mat_description, short, SN 148
This code-listed attribute is a generic description of the materials used for this piping
materials class (such as carbon steel). This attribute is only used for reporting.
10. service_lim_table, character(6)
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, engineered items, and instruments included in this piping
materials class are suitable (unless you define a lower maximum temperature limit for a
specific commodity item). You must insure that all commodity items within the piping
materials class are acceptable within the boundary of this table.
Refer to Temperature and Pressure Service Limits Table (on page 131) for more information
on this table.
11. diameter_table, character(6)
This attribute identifies the nominal piping diameter table used to verify valid nominal
piping diameters in this piping materials class. Refer to Nominal Piping Diameters Table
(on page 133) for more information.
12. thickness_table, character(6)
This attribute identifies the thickness data table used in piping wall thickness calculations for
this piping materials class. Refer to Thickness Data Tables (on page 136) for more
information.
13. materials_table, character(6)
This parameter defines the materials data table used to determine the material properties
required for piping wall thickness calculations in the piping materials class. Refer to
Materials Data Table (on page 139) for more information.
14. thickness_equation, character(6)
This attribute identifies the default piping wall thickness equation to be used for this piping
materials class. If a schedule/thickness parameter for an item specifies the default
calculation, then this equation is used to perform the piping wall thickness calculation.
Refer to Wall Thickness and Branch Reinforcement Equations (on page 141) for more
information.
Note that the Bend Deflection Table name in the Piping Materials Class data is limited to 6
characters to be consistent with the other tables referenced in this data. The maximum
length of the default Bend Deflection Table name, as specified with the Project Data
Manager can be as many as 20 characters.
Refer to Bend Deflection Table (G04) (on page 156) for more information.
23. pipe_length_table, character(6)
This attribute identifies the Pipe Length Threshold Table to be used for this piping materials
class. This attribute is useful in defining specs for underground piping.
If this column is undefined (blank), the system will use the default Pipe Length Threshold
Table specified in the Type 63 data through the Project Data Manager. Therefore, you
need not define a Pipe Length Threshold Table for each piping materials class in the
Material Reference Database.
Note that the Pipe Length Threshold Table name in the piping materials class data is limited
to 6 characters to be consistent with the other tables referenced in this data. The maximum
length of the default Pipe Length Threshold Table name, as specified with the Project Data
Manager can be as many as 13 characters.
Refer to Pipe Length Threshold Table (G07) (on page 158) for more information.
Sample Files
A sample neutral file for US practice is delivered in the file
\win32app\ingr\rdusrdb\spec_data\classes.pmc. A set of sample files depicting various options
are delivered in the \win32app\ingr\pddata\sample\data directory.
bend_tbl.pmc gasket.pmc pharm.pmc
equiv_npd.pmc gskt_tbl.pmc piplen_tbl.pmc
fluid_code.pmc metric_npd.pmc thickness.pmc
fpipe.pmc
5. maximum_temp, double
This attribute is used if the commodity item is temperature dependent. It represents the
maximum temperature for which this commodity item is acceptable. When a commodity
item is retrieved from the Piping Job Specification, the system verifies that the normal
operating temperature, the alternate operating temperature, the normal design temperature,
and the alternate design temperature are less than this maximum allowable temperature. If
this maximum is exceeded by any of these temperatures, the system automatically searches
for another occurrence of the same commodity item.
For gaskets, to help determine the gap thickness at bolted joints, the maximum
temperature value is used as an input to the Gasket Gap Table. Proper entry of
temperature values in the PJS assists the definition of gap thicknesses when gaskets with
different gap thicknesses are used in the same piping materials class.
If you specify the default value (-9999), no test is performed. Any reports created from
the Piping Job Specification depict this default value as alphanumeric blanks.
The order in which entries of the same piping commodities with different maximum
temperature values are made in the PJS (PDtable_202) is not considered by the system;
however, these entries must have the same option code in order to be considered by the
commodity selection in the Place Component command. When you do define the piping
commodity, a maximum temperature value must be defined for each entry or an error
message is displayed. To define the highest maximum temperature for the same piping
commodity, set the maximum temperature equal to or greater than the maximum
temperature of the spec limits table for the applicable piping materials class instead of using
an undefined value ('-').
6. gcp_from_nom_diam, short (NPD Units)
7. gcp_to_nom_diam, short (NPD Units)
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point (first size) in NPD units. The to value must equal
or exceed the from value. These values are not necessarily the same as the range in Tables
211 and 212. The applicable NPD value specified at placement is used to search for the
suitable component in the Piping Job Specification.
The default system of units (" for inches, or mm for millimeters) must be declared once in
the beginning and each time the default system is changed. If no units are given, the value is
automatically interpreted as inches.
8. gcp_end_prep, short, SN 330
This code-listed attribute identifies the end preparation for the green 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
You can define end compatibilities by using the End Preparation Compatibility Table.
(Refer to the Project Data Manager in the Project Administrator Reference Guide.)
9. gcp_rating, character(8)
This attribute identifies the pressure rating for the green connect point. This parameter
exists as alphanumeric data. The system interprets the first set of sequential numeric
characters as being the pressure rating value.
Ratings can be expressed in any of the following formats: CLxxxx, xxxx#, or OTxxxx.
However, table entries and file names representing the rating exclude the CL, #, or OT
characters. This enables the same table to be used regardless of how the rating is defined. In
the delivered PJS, these rating formats are used in accordance with the following criteria:
CLxxxx refers to an ANSI or API pressure rating
xxxx# refers to a pressure rating defined by an organization other than ANSI or API.
OTxxxx refers to the rating of a connect point that meets the applicable ANSI or API
rating geometrically but not from a pressure carrying standpoint. An example is a valve
supplied with flanged ends that meets the bolting pattern of ANSI CL150 pressure rating
but has pressure carrying characteristics different from those of that ANSI rating.
For bolts and gaskets, you must use a numeric pressure rating (do not use the
characters CL, #, or OT). If any character entries are encountered, the system will be unable
to locate the proper information.
Female ends for plastic pipe are usually defined in terms of schedule/thickness and not in
terms of rating. To make female ends for plastic pipe follow the rules for other female ends,
the applicable schedule/thickness is used as the value for rating. If such rating values consist
of alphanumeric characters, the system strips all alpha characters from the rating value and
uses only the numeric values in accessing the applicable tables.
If the rating in the PJS is expressed in terms of alphabetic characters only, the system uses
the characters in accessing the data tables. The names of the data tables include all the
alphabetic characters included in the PJS.
GRAVHD can be used to identify the rating for components rated to sustain a nominal
fluid head. This value can be used in the PJS and in the data tables.
OTHER can be used to identify a non standard rating value.
NONE can be used to identify the rating for components whose ends would normally
require the attribute rating as part of the table name, but for which a rating does not
apply. This value can be used in the PJS and in the data tables.
10. gcp_sch_thk, character(8)
This attribute identifies the schedule thickness value for the green connect point. This
parameter exist as alphanumeric data. (Refer to Wall Thickness and Branch Reinforcement
Equations (on page 141) for more information on this attribute.) In order of preference,
schedule, and thickness are expressed in terms of:
A generic schedule such as S-STD, S-XS, and S-XXS. If a schedule name exceeds the
provided field length (for example, S-SDR13.5), it is defined in terms of its wall
thickness.
A specific schedule such as S-40, S-40S, and S-80.
NREQD is used in cases where all of the following conditions apply:
The thickness value is not required in purchasing the component.
Empty weights are not significantly affected by actual thickness values.
Either stress analysis is not applicable, or, if applicable, the component is to be
considered infinitely rigid in stress analysis calculations.
A value with all numeric characters is interpreted as a wall thickness value in the same
physical units as nominal piping diameter. To insure compatibility between the PJS,
data tables, and wall thickness calculations, thickness is expressed in the form:
code (or part number). This attribute is the index into the Material Data Tables and the
Material Description Library. The commodity code can be defined in one of three ways:
Commodity codes with neither an * or a + prefix, indicate a commodity item that has no
associated implied components.
Commodity codes prefixed by an *, indicate a commodity item (primary component)
which has one associated implied component (such as a lap joint flange and stub end).
For more information on defining * implied items, refer to the PD_Report User's Guide.
It is not recommended that specification implied (*) items be generated by
size change components (that is, reducers, reducing flanges, and so forth) as the NPD
assigned by the system for the implied component can be either the larger or smaller
(green or red) NPD of the implying item based on how the system traces the line.
Commodity codes prefixed by a +, indicate a commodity item (primary component)
which has one or more associated implied components as defined in Table 212.
The default length for a commodity code is 16 characters, but you can modify this length if
needed. This value is specified in two files: design.ddl and reference.ddl. To customize the
character length, modify the design.ddl file as follows:
In table 34 (Piping Component Data), modify the value in column 8.
In table 50 (Piping/Tubing Data), modify the value in column 12.
Modify the reference.ddl file as follows:
In table 202 (Piping Commodity Specification Data), modify the value in column 18.
In table 211 (Piping Commodity Size-Dependent Material Data), modify the values in
column 2 and column 7.
In table 212 (Piping Commodity Implies Material Data), modify the values in column 2
and column 7.
When you modify these values, set the character limit to be one more than the
number of characters you actually want in the commodity code. This is necessary for
you to add a * or + prefix if needed. For example, to create a 20-character commodity
code, set the specified values to 21.
You must make these modifications before the project is created.
For valves, the commodity code also defines the name of the dry weight table (required for
stress analysis). For large diameter valves (25"+), it is used to build the name of the operator
dimension table.
19. model_code, character(6)
This attribute identifies the specific item name for generic bends, spec flanges, or spec
valves. Each model code is classified by:
Item name
option
size ranges
end preparations
ratings
The model code includes the definition of the graphic representation of the component in the
piping model. Depending upon the circumstances:
One or more model codes can be assigned to a single Item Name (for example, GAT,
GATR, and GATF are all used for 6Q1C01).
The same model code can be assigned to different Item Names.
For gaskets, this attribute can be used to prioritize gasket entries in the Piping Materials
Class. The priority is set with a numeric value (integer or decimal) greater than zero. Non-
numeric values are ignored by MTO and not considered to be a priority selection. The
smaller the value the higher the priority. A value of 999999 is interpreted as an undefined
priority.
20. PDS_sort_code, character(6)
This field can be used to specify the length (in subunits) for Purchased length pipe, or to
specify the gasket diameter for gaskets. The gasket diameter table is used if the
pds_sort_code for the gasket spec entry is set to _GKT. The system uses the NPD to
determine the gasket inside and outside diameters.
If the pds_sort_code for the gasket spec entry is set to "_GKT", the gasket outside and
inside diameters are generated using the table gasket_commodity_code_GKT.TBL.
If the pds_sort_code for the gasket spec entry is not "_GKT", the gasket outside
diameter is equivalent to the NPD of the rated component and the gasket inside diameter
is undefined.
21. modifier, double
This attribute is used for pipe bends, elbows, miters, and valves. It has various uses
depending on the type of commodity item as defined below.
For pipe bends, it defines the bend radius of the pipe in terms of the numeric factor by
which the nominal diameter of the pipe is to be multiplied to obtain the bend radius.
For pipe, it defines the joint quality factor (E) times 100 to be used during branch
reinforcement calculations in those cases where the wall thickness is not calculated.
For orifice flanges and drip ring tees, it defines the number of taps to be provided. A
value of 1 defines a single tap. A value of 2 defines 2 taps, 180 degrees apart. A value
of negative 2 (-2) defines 2 taps, 90 degrees apart.
For nippolets and nipples, it defines the length of the component.
For reinforcing pads and welds, it defines whether data about the component is to be
derived from tables in the system (0) or from the user by prompting (1).
For gaskets, it defines the gasket thickness to be used in procuring the gasket. This is
the actual gasket thickness for MTO reports - not the compressed gasket thickness
(gasket separation), which is derived from the Piping Materials Class data.
For bolts, it defines whether the bolt is a stud bolt (0 or positive), or machine bolt
(negative). The absolute value of this modifier, which ranges from 0 to 5, determines
the applicable bolt extension.
For valves, it represents the code list number from CL550 (operator/actuator type) which
defines the symbol description and the source of the physical data for the valve operator.
If this value is a negative number (such as -3), the operator is not displayed when
placing the component.
Sample Files
A set of neutral file for US practice are delivered in the files
\win32app\ingr\rdusrdb\spec_data\*.pcd (one for each piping materials class specified in the
classes.pmc file).
A set of sample files depicting various options are delivered in the
\win32app\ingr\pddata\sample\data directory.
bend_tbl.pcd gasket.pcd pharmf.pcd
equiv_npd.pcd gskt_tbl.pcd pharmk.pcd
fluid_code.pcd metric_npd.pcd piplen_tbl.pcd
fpipe.pcd pharm.pcd thickness.pcd
2. piping_comp_no, character(20)
This attribute uniquely identifies the specialty component number. It is sometimes referred
to as Item Number.
3. model_code, character(6)
This attribute identifies the piping specialty name. This can be a Piping Job Specification
access name or a PDS commodity item name.
4. option_code, short, SN 400
This code-listed attribute identifies the option code which determines the search criteria.
This parameter enables you to request that the system retrieve the primary item, a secondary
item, or another special option from the Piping Job Specification. You can select the unique
options (as defined in standard note 400) from a form. If no option is specified at placement,
the primary item is used. Option 2 is reserved as the secondary item. This parameter is used
as a component override in the Piping Designer.
5. gcp_from_nom_diam, short (NPD Units)
6. gcp_to_nom_diam, short (NPD Units)
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point.
7. gcp_end_prep, short, SN 330
These attributes identify the end preparation for the green/red connect point. This value is
an intelligent code list. The system determines the termination type based on the range of
values:
2 - 199 bolted terminations
300 - 399 male terminations
400 - 599 female terminations
8. gcp_rating, character(8)
These attributes identify the pressure rating for the green/red connect point. This parameter
exists as alphanumeric data. The system interprets the first set of sequential numeric
characters as being the pressure rating value. (Refer to the description of pressure rating
under Piping Commodity Data for more information on standard formats.)
9. gcp_sch_thk, character(8)
These attributes identify the schedule or thickness value for the green/red connect point.
This parameter exist as alphanumeric data. (Refer to the description of schedule and
thickness for more information on standard formats.)
10. gcp_table_suffix, short, SN 576
These code-listed attributes identify 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 connect point.
For DIN standards, it represents the piping outside diameter selection flag (reihe
number) for pipes and fittings.
11. rcp_from_nom_diam, short (NPD Units)
Sample Files
A sample neutral file is delivered in the file \win32app\ingr\pddata\sample\data\specialty.data.
A sample file containing various bio-pharmaceutical specialty items is delivered in the file
\win32app\ingr\pddata\sample\data\pharms.data.
3. model_code, character(6)
This attribute identifies the specific item name for generic bends, spec flanges, or spec
valves. This can be a Piping Job Specification access name or a PDS commodity item name.
Refer to the PDS Piping Component Data Reference Guide for more information on item
names.
4. option_code, short, SN 400
This code-listed attribute identifies the option code which determines the search criteria.
This parameter enables you to request that the system retrieve the primary item, a secondary
item, or another special option from the Piping Job Specification. You can select the unique
options (defined in a standard note) from a form. If no option is specified at placement, the
default option 1 is used. Option 2 is reserved as the secondary item. This parameter is used
as a component override in Piping Design.
5. gcp_from_nom_diam, short (NPD Units)
6. gcp_to_nom_diam , short (NPD Units)
These coded attributes identify the range of nominal piping diameters (low bound to high
bound) for the green connect point.
7. gcp_end_prep, short, SN 330
These code-listed attributes identify the end preparation for the green/red 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
8. gcp_rating, character(8)
These attributes identify the pressure rating for the green/red connect point. This parameter
exists as alphanumeric data. The system interprets the first set of sequential numeric
characters as being the pressure rating value. (Refer to the description of pressure rating for
more information on standard formats.)
9. gcp_sch_thk, character(8)
These attributes identify the schedule thickness value for the green/red connect point. (Refer
to the description of schedule and thickness for more information on standard formats.)
10. gcp_table_suffix, short, SN 576
These code-listed attributes 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 connect point.
For DIN standards, it represents the piping outside diameter selection flag (reihe
number) for pipes and fittings.
11. rcp_from_nom_diam, short (NPD Units)
12. rcp_to_nom_diam, short (NPD Units)
These coded attributes identify the range of nominal piping diameters (low bound to high
bound) for the red connect point. For a full size component, these parameters are set to zero.
13. rcp_end_prep, short, SN 330
See gcp_end_prep.
Sample Files
A sample neutral file is delivered in the file \win32app\ingr\pddata\sample\data\instrment.data.
A sample file containing various bio-pharmaceutical instruments is delivered in the file
\win32app\ingr\pddata\sample\data\pharmi.data.
7. sched_thick, character(8)
This attribute identifies the generic or specific schedule, a thickness value, or a calculation.
(Refer to the description of schedule and thickness for Piping Commodity Data for more
information on standard formats.)
8. tap_material_code, character(10)
This optional attribute can be used to access the Material Description Library for the tap's
material description addendum. It must be a unique reference to the Material Description
Library, including material descriptions for commodity items. In reporting or isometric
extraction, this text can be appended to either the short or long descriptions of the
component to which the tap applies.
This attribute is also referred to as the Tap Code. Refer to the listing of the tap descriptions
in the Short Material Description Library (on page 277) for more information on the tap
commodity code.
Table= C001
! Description= SWE CL3000 default taps
! Diam Opt Rating Prp Sc/Th Tap Code
0.375 691 - 591 NREQD E$37591XXX
> 0.5 1 CL3000 421 NREQD E$50421064
0.5 691 - 591 NREQD E$50591XXX
> 0.75 1 CL3000 421 NREQD E$75421064
0.75 691 - 591 NREQD E$75591XXX
> 1 1 CL3000 421 NREQD E001421064
1 691 - 591 NREQD E001591XXX
> 1.25 1 CL3000 421 NREQD E1$2421064
1.25 691 - 591 NREQD E1$2591XXX
> 1.5 1 CL3000 421 NREQD E1$5421064
1.5 691 - 591 NREQD E1$5591XXX
> 2 1 CL3000 421 NREQD E002421064
2 691 - 591 NREQD E002591XXX
2.5 691 - 591 NREQD E2$5591XXX
> 3 1 CL3000 421 NREQD E003421064
3 691 - 591 NREQD E003591XXX
3.5 691 - 591 NREQD E3$5591XXX
> 4 1 CL3000 421 NREQD E004421064
4 691 - 591 NREQD E004591XXX
5 691 - 591 NREQD E005591XXX
6 691 - 591 NREQD E006591XXX
8 691 - 591 NREQD E008591XXX
10 691 - 591 NREQD E010591XXX
12 691 - 591 NREQD E012591XXX
14 691 - 591 NREQD E014591XXX
16 691 - 591 NREQD E016591XXX
18 691 - 591 NREQD E018591XXX
20 691 - 591 NREQD E020591XXX
Sample Files
A sample neutral file for US practice is delivered in the file
\win32app\ingr\rdusrdb\spec_data\taps.data.
A sample file containing various bio-pharmaceutical tap properties is delivered in the file
\win32app\ingr\pddata\sample\data\pharm_tap.data.
NREQD is used if the thickness value is not required in purchasing the component,
empty weights are not significantly affected by actual thickness values, and stress
analysis is not applicable.
A value with all numeric characters is interpreted as a wall thickness value in the same
physical units as nominal piping diameter.
An asterisk (*) followed by a name (of the form Cyyy) defines the specific calculation or
table lookup to be used for wall thickness.
7. commodity_code, character(16), index 1
This attribute identifies the customer's commodity code or vendor's part number. It is not
required for the customer's commodity code if the customer's commodity code is not
dependent upon nominal piping diameter or thickness.
8. weld_weight, double
This parameter represents the total weld required at all welded ends of the commodity item.
9. unit_price, double
This attribute identifies the unit price (materials cost) for the commodity item.
10. manhours, double
This attribute identifies the unit manhours associated with the commodity item.
Data Retrieval
The data retrieval from the Size-Dependent Data table involves data for a commodity item that is
dependent upon nominal piping diameter and schedule/thickness. This form of data retrieval is
used during the MTO report creation process.
outputs
customer's commodity code or vendor's part number
weld data
Sample Files
A sample neutral file for US practice is delivered in the file
\win32app\ingr\rdusrdb\spec_data\implied.data.
A sample file containing various bio-pharmaceutical gasket data is delivered in the file
\win32app\ingr\pddata\sample\data\pharm_212.data.
Data Retrieval
Data retrieval from the Implied Material Data table involves implied material data for a
commodity item that is dependent on nominal piping diameter range. This form of data retrieval
is used during the MTO Report Creation process and Material Control.
outputs
Commodity code of the implied material
Quantity of the implied material
Fabrication category of the implied material
Standard note for the implied material
data. If the component is defined in the exclusion table for those conditions, the applicable
insulation thickness will not be added to the component's interference envelope. Otherwise, the
insulation thickness will be included in the component's interference envelope.
The piping segment data (heat tracing requirements, insulation purpose, and normal operating
temperature) are determined on the basis of the piping segment that is associated with the first
connect point of the applicable component.
The Component Insulation Exclusion Data table contains 13 attributes.
1. system_unique_no, integer
2. commodity_name, character(6)
This attribute identifies the commodity item name of a piping component as defined in the
Piping Commodity Specification Data (Table 202 attribute 3).
If this attribute is blank, the system will search for a match by model code.
3. model_code, character(6)
For piping commodities, this attribute identifies the model code as defined in the Piping
Commodity Specification Data (Table 202 attribute 19).
For piping specialties, this attribute identifies the model code as defined in the Piping
Specialty Specification Data (Table 203 attribute 3).
For instruments, this attribute identifies the model code as defined in the Instrument
Component Specification Data (Table 204 attribute 3).
4. gcp_npd_from, short
5. gcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point of the component or instrument in NPD units.
6. rcp_npd_from, short
7. rcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the red connect point of the component or instrument in NPD units.
For full size components, use a dash (-) for these attributes.
8. heat_tracing_from, short, SN 200
9. heat_tracing_to, short, SN 200
These code-listed attributes identify the range of heat tracing values (lower bound to higher
bound) using values from code list set 200, Heat Tracing Requirements.
A dash (-) can be used for the from value to indicate that heat tracing requirements are not to
be considered as part of the discrimination process.
10. insul_purpose_from, short, SN 220
11. insul_purpose_to, short, SN 220
These code-listed attributes identify the range of insulation purpose values (lower bound to
higher bound) using values from Standard Note type 220, Insulation Purpose.
A dash (-) can be used for the from value to indicate that insulation purpose is not to be
considered as part of the discrimination process.
12. nor_oper_temp_from , double
The Piping Eden modules for the interference envelopes that are to consider the
partial exclusion of insulation from the flange outside diameter of a bolted end must be
revised to accommodate this option. If you do not change any or all of the Piping Eden
modules for the interference envelopes, this table will have no impact and the interference
envelopes will include complete insulation, when applicable.
For example, the required modification to the interference parametric for the weldneck
flange (FWN) is as follows:
!FLANGE - Interference Module
Interference_Parametric_Shape_Definition 'F1A'
Call Define_Connect_Point_Geometry ( LINEAR )
Thickness_1 = Thickness_1 + CP_Offset_1
Thickness_2 = Thickness_2 + CP_Offset_2
!Original Line
! Facing_OD_1 = Facing_OD_1 + Insulation * 2
!Modified Line
Facing_OD_1 = Facing_OD_1 + Insulation_1 * 2
Facing_OD_2 = Facing_OD_2 + Insulation * 2
Call Draw_Cylinder ( Thickness_1, Facing_OD_1 )
Call Draw_Cylinder ( Thickness_2, Facing_OD_2 )
RETURN
END
The Flange Insulation Exclusion Data table has 9 attributes.
1. system_unique_no, integer
2. bolted_npd_from, short
3. bolted_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the bolted end of the component or instrument in NPD units.
4. heat_tracing_from, short, SN 200
5. heat_tracing_to, short, SN 200
These code-listed attributes identify the range of heat tracing values (lower bound to higher
bound) using values from code list set 200, Heat Tracing Requirements.
A dash (-) can be used for the from value to indicate that heat tracing requirements are not to
be considered as part of the discrimination process.
6. insul_purpose_from, short, SN 220
7. insul_purpose_to, short, SN 220
These code-listed attributes identify the range of insulation purpose values (lower bound to
higher bound) using values from Standard Note type 220, Insulation Purpose.
A dash (-) can be used for the from value to indicate that insulation purpose is not to be
considered as part of the discrimination process.
8. nor_oper_temp_from, double
9. nor_oper_temp_to, double
These attributes identify the range of temperature values (lower bound to higher bound) for
the bolted end of the component or instrument.
A dash (-) can be used for the from value to indicate that temperature is not to be considered
as part of the discrimination process.
The system of units for the temperature range is the same as the system of units for the
maximum temperature in the Piping Commodity Specification Data Table. Note that normal
design temperature, alternate operating temperature, and alternate design temperature are not
considered.
This is an optional data table; if no data is defined for this table, the Piping Envelope builder will
continue to function as it has in previous releases of PDS.
For each piping or instrument component, excluding pipes, the Piping Envelope Builder searches
Table 233 on the basis of the following data to determine whether the Piping versus Piping
construction tolerance should be excluded from that component's interference envelope.
green NPD of the component (range search)
red NPD of the component (range search)
For piping commodities, the Piping Envelope Builder searches for the component's commodity
name in the Piping Construction Tolerance Exclusion Data Table using the preceding data.
If the piping commodity is defined in the exclusion table for those conditions, the applicable
construction tolerance will not be added to the component's interference envelope.
If the commodity name is not specified in the exclusion table for those conditions, the Piping
Envelope Builder will search for the component's model code using the same data. If a
match for those conditions is found on the basis of the model code, the applicable
construction tolerance will not be added to the component's interference envelope.
Otherwise, the construction tolerance will be included in the component's interference
envelope.
For piping specialties and instrument components, the Piping Envelope Builder searches for the
component's model code in the Piping Construction Tolerance Exclusion Data Table using the
preceding data. If the component is defined in the exclusion table for those conditions, the
applicable construction tolerance will not be added to the component's interference envelope.
Otherwise, the construction tolerance will be included in the component's interference envelope.
The Piping Construction Tolerance Exclusion Data table has 7 attributes.
1. system_unique_no, integer
2. commodity_name, character(6)
This attribute identifies the commodity item name of a piping component as defined in the
Piping Commodity Specification Data (Table 202 attribute 3).
If this attribute is blank, the system will search for a match by model code.
3. model_code, character(6)
For piping commodities, this attribute identifies the model code as defined in the Piping
Commodity Specification Data (Table 202 attribute 19).
For piping specialties, this attribute identifies the model code as defined in the Piping
Specialty Specification Data (Table 203 attribute 3).
For instruments, this attribute identifies the model code as defined in the Instrument
Component Specification Data (Table 204 attribute 3).
4. gcp_npd_from, short
5. gcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point of the component or instrument in NPD units.
6. rcp_npd_from, short
7. rcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the red connect point of the component or instrument in NPD units.
For full size components, use a dash (-) for these attributes.
Spec Writer
This command provides a forms interface for interactively creating, revising, and managing the
following specification data. This interface provides more simplicity and flexibility to a beginner
or a casual user than defining specs with their respective neutral files:
Piping Materials Class Data (201) (on page 34)
Piping Commodity Specification Data (202) (on page 38)
Piping Specialty Specification Data (203) (on page 45)
Instrument Component Specification Data (204) (on page 48)
Tap Properties Data (205) (on page 51)
Piping Commodity Implied Material Data (212) (on page 56)
See Also
Features (on page 65)
RDB Options File (on page 66)
Features
The Spec Writer provides the following general features:
User-specified options for customizing the input of data (RDB_options).
A direct interface to the unapproved Specification Material Reference Database.
On-line validation for the existence of a material description, once the commodity code (or
component number) has been defined.
Optional on-line Table Checker validation using pre-defined Table Checker reports.
Automated selections from the Standard Note Library for code-listed data. The approved
Standard Note Library must have been defined to include the correct data for use in the
Material Reference Database.
Selectable list of acceptable model codes for a specified commodity name.
Context-sensitive user interface. The form options will vary depending on the item being
defined. For example, the creation (and revision) of specification data for bolts and gaskets
will display only those inputs relevant for bolts or gaskets.
Context-sensitive on-line help that is linked to the Piping Component Data Reference Guide
and the Reference Data Manager Reference Guide.
MODEL_CODE = LIST
VALVE_OPERATOR = LIST
!
!
COMMODITY_NAME<===>MODEL_CODES
!
! Pipe/Tube
PIPING = PIPE, TUBE
!
! Valves (6Q1C)
!
6Q1C01 = GATSP, GAT, GATF, GATR
6Q1C02 = GATEX, GATEXB, GATEXBB
6Q1C03 = GATCON
6Q1C04 = GATBL
!
! Generic 3-way
6Q1C05 = BAL3P, GLO3W, PLU3W, SLI3W, 3WRV1
!
6Q1C06 = BALF, BALR, BALSP, BALLP, BALVP
6Q1C08 = BAL3P
6Q1C11 = GLOSP, GLO, GLOF, GLOR
6Q1C12 = GLOASP, GLOA
6Q1C13 = GLO3W
6Q1C14 = GLOY, GLOYF, GLOYR
6Q1C16 = PLUSP, PLU, PLUVP, PLUFB, PLUF, PLUR
6Q1C18 = PLU3W
6Q1C19 = PLU4W
6Q1C22 = NEE
6Q1C26 = BFYLP, BFYHP
6Q1C30 = DIA, DIASP, DIAPL, DIAGL
6Q1C32 = KNF
6Q1C33 = SLI
6Q1C34 = SLI3W
6Q1C37 = CKALSP, CKAL, CKST, BDA, HOSA
6Q1C38 = CKLSP, CKSSP, CKL, CKLF, CKLR, CKS, CKSF, CKSR, CKSY, CKLRY
6Q1C39 = CKWF, CKWFSP
6Q1C40 = CKALSP, CKAL
6Q1C41 = CKST
6Q1C42 = CKAST
6Q1C43 = CKYST
6Q1C50 = CKBP
6Q1C51 = CKAR
6Q1C53 = BDA
6Q1C54 = BDY
6Q1C56 = PIN
6Q1C57 = FLO
6Q1C58 = FOOT
6Q1C62 = TKDR
6Q1C69 = DEL
6Q1C72 = HOS
6Q1C73 = HOSA
!
! Generic Vent/Drain Valve
6Q1C76 = GATSP, GAT, GATF, GATR, BALF, BALR, BALSP, BALLP, BALVP
!
! Generic Instrument Root Valve
6Q1C80 = GATSP, GAT, GATF, GATR, BALF, BALR, BALSP, BALLP, BALVP
!
6Q1C81 = 3WRV1
6Q1C82 = 4WRV1
!
! On-line Fittings (6P2C) and In-line Fittings (6Q2C)
!
6Q2C01 = FWN, FLWN, FSO, FL, FPL, FSSSO, FSSL, FSSPL, FLSSO, FLSL,
FFIL, FS, FSW, FTHD, FCP
6Q2C03 = FRWN, FRSO, FRPL, FRS, FRSW, FRTHD
6Q2C04 = FEWN
6Q2C06 = FOWNA, FOWNAW, FOWNB, FOWNBW, FOSOA, FOSOAW, FOSOB, FOSOBW,
FOSWA, FOSWAW, FOSWB, FOSWBW, FOTHDA
6Q2C08 = FBLD
6Q2C10 = BLSPO
6Q2C11 = BLSPC
6Q2C12 = BDISC
6Q2C13 = BLPAD
6Q2C14 = T1SPA, T2SPA1
6Q2C15 = BLSPA, OPSPA
!
! Generic End
6Q2C16 = FBLD, HDHEMI, HDELIP, HD21, PLUG, CAPBV, CAPOT
!
6Q2C17 = HDHEMI, HDELIP, HD21
6Q2C19 = PLUG
6Q2C21 = CAPBV, CAPOT
!
! Generic Conentric Diameter Change
6Q2C23 = REDC, SWGC, CPLR, INSR1, INSR2
!
! Generic Eccentric Diameter Change
6Q2C24 = REDE, SWGE
!
6Q2C25 = CPL
6Q2C26 = CPLH
6Q2C27 = REDC
6Q2C28 = REDE
6Q2C32 = CPLR
6Q2C35 = SWGC
6Q2C36 = SWGE
6Q2C39 = UN
6Q2C40 = UNO
6Q2C41 = UND
6Q2C43 = HC
6Q2C44 = BUSH
6Q2C46 = INSR1, INSR2
6Q2C47 = PIPB, PIPB2
6Q2C49 = E5
6Q2C51 = E11
6Q2C53 = E22
!
! Generic <45 Degree Direction Change
6Q2C55 = E5, E11, E22, E45TLR, PIPB, PIPB2
!
! Generic 45 Degree Direction Change
6Q2C56 = E45LR, E45, PIPB, PIPB2, E45LT, E453D, E45T3D, E45U, E45ST,
E45S, E45L, M451, M452
!
6Q2C57 = E45
6Q2C59 = E45LR, E45TLR
6Q2C60 = E45LT
6Q2C61 = E453D, E45T3D
6Q2C63 = E45U
6Q2C65 = E45ST
6Q2C66 = E45S
6Q2C68 = E45L
6Q2C73 = E60
!
! Generic 45-90 Degree Direction Change
6Q2C75 = E90TLR, PIPB, PIPB2
!
! Generic 90 Degree Direction Change
6Q2C76 = E90LR, E90, E90SR, E90LT, E90R, E903D, E903T3D, E90U, E90ST,
E90RST, E90S, E90L, PIPB, PIPB2, E90LT, M901, M902, M903, M904
!
6Q2C77 = E90
6Q2C79 = E90SR
6Q2C80 = E90LR, E90TLR
6Q2C82 = E90LT
6Q2C84 = E90R
6Q2C86 = E903D, E903T3D
6Q2C88 = E90U
6Q2C90 = E90ST
6Q2C91 = E90RST
6Q2C93 = E90S
6Q2C94 = E90L
!
! On-line Fittings (6P3C) and In-line Fittings (6Q3C)
!
6Q3C01 = R180
6Q3C03 = R180SR
6Q3C05 = R180LR
6Q3C07 = R180CL
6Q3C08 = R180MD
6Q3C09 = R180OP
6Q3C14 = M1, M2, M3, M4
6Q3C16 = M451, M452
6Q3C18 = M901, M902, M903, M904
6Q3C22 = T, TBT
6Q3C24 = TRB, TRBT
6Q3C25 = TRRB
6Q3C27 = TUOR
6Q3C28 = TUOB
6Q3C31 = TST
6Q3C34 = TRI
6Q3C36 = TDRA, TDRAW, TDRB, TDRBW
6Q3C38 = TBA
6Q3C45 = Y
6Q3C47 = L
6Q3C49 = LRB
6Q3C50 = LRRB
6Q3C52 = S90YB
6Q3C53 = S90YRB
6Q3C54 = L90YB
6Q3C55 = L90YRB
6Q3C60 = X
6Q3C62 = XRB
6Q3C63 = XRRB
6Q3C64 = XBA
6Q3C70 = SAD
6Q3C72 = SWOL
6Q3C73 = WOL
6Q3C74 = SOL
6Q3C75 = TOL
6Q3C76 = NOL
6Q3C77 = EOLLR, EOLSR
6Q3C78 = LOL
6Q3C79 = FOLHC
6Q3C80 = RPAD, RPAD2
6Q3C82 = RWELD, RWELD2
6Q3C84 = BWELD, BWELD2, BWELD3
6Q3C88 = NIP
6Q3C89 = NIPIL
!6Q3C95 = GASKET
!6Q3C97 = STUD
!6Q3C98 = NUT
!
!
!
VALVE_OPERATOR_LIST
!
! Handwheels
!
OP_0 = None Required
OP_3 = Handwheel
OP_4 = Handwheel if GCP>RCP
OP_5 = Handwheel, inclined
OP_9 = Wrench, short
OP_11 = Wrench, long
OP_17 = Lever
OP_19 = T-handle, short
OP_21 = T-handle, long
OP_25 = Handwheel, special
OP_27 = Wrench, special
OP_29 = Gear, top mounted handwheel
OP_31 = Gear, top mounted inclined handwheel
OP_33 = Gear, side mounted handwheel
OP_35 = Gear, side mounted inclined handwheel
You can use the following keywords to customize the settings in the RDB options file.
General Items
For piping commodities, you can verify that a material description has been defined in the Short
Material Description Library and/or the Long Material Description Library. For piping
specialties and instruments, you can verify that a material description has been defined in the
Specialty Material Description Library.
SHORT_COMMODITY_MATERIAL_DESCRIPTION = ON or OFF If set to ON, the short
material description is displayed when you specify the commodity code.
If this keyword is not specified in the RDB options file, the default setting is OFF.
LONG_COMMODITY_MATERIAL_DESCRIPTION = ON or OFF If set to ON, the long
material description is displayed when you specify the commodity code.
If this keyword is not specified in the RDB options file, the default setting is OFF.
SPECIALTY_MATERIAL_DESCRIPTION = ON or OFF If set to ON, the specialty
material description is displayed when you specify the commodity code.
If this keyword is not specified in the RDB options file, the default setting is OFF.
PDtable_201 items
SERVICE_LIMITS_TABLE = LIST, <prefix> If set to LIST, a list of Service Limits
Tables (as defined in the approved Piping Job Specification Table Library) is displayed.
You must specify a prefix to use as a substring search to determine the list of tables. (Use L
for the delivered tables.)
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
NOMINAL_PIPING_DIAMETER_TABLE = LIST, <prefix> If set to LIST, a list of
Nominal Piping Diameter Tables (as defined in the approved Piping Job Specification Table
Library) is displayed. You must specify a prefix to use as a substring search to determine
the list of tables. (Use D for the delivered tables.)
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
BRANCH_TABLE = LIST, <prefix> If set to LIST, a list of Branch Tables (as defined
in the approved Piping Job Specification Table Library) is displayed. You must specify a
prefix to be used as a substring search to determine the list of tables. (Use B for the
delivered tables.) The list is filtered to only include the unique tables, where the branch
angle is 90 degrees.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
You should not assign the same Branch Table to be used in two different piping
materials classes if, for example, one allows intersections at both 45 degrees and 90 degrees,
and the other only allows 90 degree intersections. The Reference Data Manager will not
detect this problem.
TAP_PROPERTIES_TABLE = KEYIN or DATABASE If set to DATABASE, a list of Tap
Properties Data Tables (as defined in PDtable_205 of the unapproved Material Reference
Database) is displayed.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
GASKET_SEPARATION_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of
Gasket Separation Tables (as defined in the approved Piping Job Specification Table
Library) is displayed. You must specify a prefix to be used as a substring search to
determine the list of tables. (Use G for the delivered tables.)
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
When listing the Gasket Separation Tables, the list of tables is restricted to unique
names, excluding the underbar (_) and the pressure rating value that follows. In other words,
the list of Gasket Separation Tables will not include the pressure rating (G001 instead of
G001_1500).
PDtable_202 items
MODEL_CODE = KEYIN or LIST If set to LIST, a list of acceptable model codes
(determined by the commodity name) is displayed. (See keyword COMMODITY_NAME
<===> MODEL_CODES for more information.)
If this keyword is not specified in the RDB options file or the list of acceptable model codes
is not defined, the default mode is to key in the value.
VALVE_OPERATOR = KEYIN or LIST If set to LIST, a list of valve operator types (as
defined in the RDB options file) is displayed. (See keyword VALVE_OPERATOR_LIST for
more information.)
If this keyword is not specified in the RDB options file or the list of valve operator types is
not defined, the default mode is to key in the value.
PROMPT_FOR_TAP_ORIENTATION This keyword is used if you require that all (or some)
orifice flanges have two taps oriented 90 degrees apart. By default orifice taps are oriented
180 degrees apart on the outside diameter of the flange.
If this keyword is not included in the RDB options list, the relative tap orientation for two
taps will always be 180 degrees.
COMMODITY_NAME <===> MODEL_CODES This keyword precedes the list of
associations between commodity names and their acceptable model codes. This list must be
defined to use the LIST option for MODEL_CODE.
The association between a commodity name and the acceptable model codes for that
commodity name is defined as follows.
<commodity_name> = <model_code_A>,<model_code_B>, ...
6Q1C01 = GATSP, GAT, GATF, GATR
6Q1C02 = GATEX, GATEXB, GATEXBB
You can define as many as 50 model codes, separated by a comma, for each commodity
name.
The delivered RDB options list includes a list of acceptable model codes for the reference
data provided with PDS.
VALVE_OPERATOR_LIST This keyword precedes the list of valve operator types and
their corresponding descriptions.
The list of valve operator types is defined as follows.
<valve operator type> = <description>
OP_0 = None Required
OP_3 = Handwheel
The delivered RDB options file includes a list of valve operator types for the reference data
provided with PDS. The description is for information only to aid the user in selecting the
proper valve operator type.
END_VALVE_OPERATOR_LIST This keyword must follow the valve operator list as a
delimiter.
Create The system activates the Create Piping Materials Class Data form.
Revise By Keyin The system activates the Revise Piping Materials Class Data form.
Key in the name of the piping materials class to revise in the Piping Materials Class field.
Revise By List Select the piping materials class to be revised from the displayed list of
piping materials classes (as defined in the Unapproved Material Reference Database) and
select Accept. The system activates the Revise Piping Materials Class Data form with the
data for the selected piping materials class.
The system highlights the mandatory input fields (those that must be specified). Once you define
a valid input for a mandatory field the system will drop the highlight for that field.
Refer to RDB Options File (on page 66) for information on defining list options for the
applicable input fields.
Refer to Piping Materials Class Data (201) (on page 34) for more information on the attributes
for the Piping Materials Class Data table (201).
angle is 90 degrees. For more information, see Bends and Tee-type Branches and Branch
Components in Piping Design Reference Guide.
Optional Data
The following data is not required and can be defined or not defined based on your company
practices.
Materials Description (keyin or list) Key in the numeric value for the materials
description in the Standard Note Library for this piping materials class or select from the list
of materials descriptions (as defined in the approved Standard Note Library).
Revision (keyin) Key in up to two alphanumeric characters for the revision number.
Revision Date (keyin) Key in up to ten alphanumeric characters for the date. The
current date will not be entered automatically.
Note that the Reference Data Manager creates and maintains a separate revision
management date on the basis of the current date and time which can be used in the
reporting of reference data.
Fluid Code (keyin list) Define a default fluid code to be used for the piping materials
class.
OR
Fluid Code Table (keyin list) Key in the name of the Fluid Code Table for this piping
materials class or select from a list of Fluid Code Tables (as defined in the approved Piping
Job Specification Table Library).
Materials of Construction (keyin) Key in up to six alphanumeric characters.
Bend Deflect Table (keyin or list) Key in the name of the Bend Deflection Table for this
piping materials class or select from a list of Bend Deflection Tables (as defined in the
approved Piping Job Specification Table Library).
Pipe Length Table (keyin or list) Key in the name of the Pipe Length Table for this
piping materials class or select from a list of Pipe Length Tables (as defined in the approved
Piping Job Specification Table Library).
Standard Note Number (keyin or list) Key in the note number in the Standard Note
Library for this piping materials class or select from the list of standard notes (as defined in
the approved Standard Note Library).
Create Select the Piping Materials Class for the commodity item to be created from the
list of piping materials classes (as defined in the Unapproved Material Reference Database)
and select Accept. The system activates the Create Piping Commodity Specification Data
form.
Revise By Keyin Key in the name of the piping materials class for the commodity item
to be modified. Then select the piping commodity to be revised from the displayed List of
Piping Commodities and select Accept. The system activates the Revise Piping Commodity
Specification Data form with the data for the selected piping commodity.
Revise By List Select the piping materials class for the commodity item to be revised
from the displayed list of piping materials classes and select Accept. Then select the piping
commodity to be revised from the displayed List of Piping Commodities and select Accept.
The system activates the Revise Piping Commodity Specification Data form with the data
for the selected piping commodity.
Copy You can use the Copy option in conjunction with the Revise options as a cut-and-
paste feature. This command requires that both the source piping materials class data and the
destination piping materials class have been created.
You can copy a complete piping materials class, including the piping commodity
specification data or selectively copy specific commodities. Select the option for the items
to be copied.
Source and Destination Piping Materials Class - These are active fields that, when selected,
display the piping materials class list. Select the source piping materials class from the
displayed list, and then select Accept. Select the destination piping materials class from the
displayed list and select Accept.
Select All - This option copies the specification data for all piping commodities within the
selected source piping materials class to the specified destination piping materials class.
Select From List - Select the source piping materials class from the displayed list and select
Accept. Select the destination piping materials class from the displayed list and select Accept.
Then select the piping commodity to be copied from the list of all piping commodities within the
source piping materials class.
Select Gaskets - Select the source piping materials class from the displayed list and select
Accept. Select the destination piping materials class from the displayed list and select Accept.
The system copies the specification data for all gaskets within the source piping materials class
to the destination piping materials class. Gaskets are recognized on the basis of the gasket
commodity name, as specified through the Project Data Manager.
Select Bolts - Select the source piping materials class from the displayed list and select Accept.
Select the destination piping materials class from the displayed list and select Accept. The
system copies the specification data for all bolts within the source piping materials class to the
destination piping materials class. Bolts are recognized on the basis of the bolt commodity
name, as specified through the Project Data Manager.
Short Commodity Material Description ON/OFF You can set this toggle to ON to
verify that the material description for a specified commodity code has been defined in the
Short Material Description Library.
Long Commodity Material Description ON/OFF You can set this toggle to ON to
verify that the material description for a specified commodity code has been defined in the
Long Material Description Library.
Refer to RDB Options File (on page 66) for information on defining options for the applicable
input fields.
Refer to Piping Commodity Specification Data (202) (on page 38) for information on the
attributes for the Piping Commodity Specification Data table.
Where possible, the system verifies that the specified value is valid for the applicable piping
materials class. For example, NPD values are checked against the associated diameters table in
the approved Piping Job Spec Table Library.
Commodity Type This field can be used to select the type of piping commodity data to
be created based on the settings in Standard Note Type 990 of the Standard Note Library.
General Fittings Piping
Pipe Bends Tubing
Orifice Flanges Gaskets
Branch Nipples Bolts
Branch Reinforcement Nuts
Valves
The system will modify the form fields to reflect the data that is specific to that type of
component. The system stores the commodity type as the input_form_type within the Piping
Commodity Specification Data Table of the Material Reference Database.
Any input fields that are not used for a specific piping commodity type will be de-activated.
The General Fittings category will allow input in all the input fields. This form is used for
any piping commodity that does not fall within any of the other types.
General Fittings, Pipe Bends, Orifice Flanges, Branch Nipples, Branch Reinforcement, and
Valves
Commodity Name (keyin)
From NPD - First Size (keyin)
To NPD - First Size (keyin)
End Preparation - First Size (list)
Pressure Rating - First Size (keyin) This data is automatically set to undefined (blank)
for the branch reinforcement commodity type.
Table Suffix - First Size (list)
Schedule/Thickness - First Size (list) Attribute 10. This data is automatically set to
undefined (blank) for the branch reinforcement commodity type.
Commodity Code (keyin) Key in the commodity code for the piping commodity. When
size-dependent commodity codes are required, this will represent a system commodity code
and will be used by the Report Manager to reference the size-dependent commodity code in
the Piping Commodity Size-Dependent Material Data Table.
The system automatically translates the specified commodity code to be upper-case.
You can use the Implied Data option to specify implied data for this piping commodity.
Refer to Commodity Implied Data Command (on page 98) for information on project-
specific implied data. Refer to Implied Data (on page 87) for information on class-specific
implied data. The default is that implied data does not apply.
For the revise command, the prefixes for implied data are not displayed as part of the
commodity code, although the prefix will be loaded in the database. For implied data
(project-wide or class-specific), the system will display the toggle setting rather than
showing the prefix in the commodity code field.
Model Code (keyin or list) Attribute 19. Key in the model code or select the model code
from a list of acceptable model codes (as defined by commodity name in the RDB options
file).
Geometric Industry Standard (list)
Weight Code (list)
fabrication category (list)
Define the following data for any reducing components. This data will not apply to either the
orifice flange or branch nipple commodity type.
From NPD - Second Size (keyin) Attribute 12. Key in the lowest second size for which
this specification data applies.
To NPD - Second Size (keyin) Attribute 13. Key in the highest second size for which
this specification data applies.
You can optionally define the following fields when two ends of that component require
different data. By PDS convention, if you specify a red End Preparation, you must specify the
corresponding pressure rating, table suffix, and schedule/thickness.
End Preparation - Second Size (list)
Pressure Rating - Second Size (keyin) This data is set to undefined (blank) for the
branch reinforcement commodity type.
Table Suffix - Second Size (list)
Schedule/Thickness - Second Size (list) This data is set to undefined (blank) for the
branch reinforcement commodity type.
The following data must be defined for the designated [component types]. The setting is stored
in the modifier attribute.
Bend Radius (keyin) [Pipe Bend] Key in the bend radius for the pipe bend.
Number of Taps (toggle) [Orifice Flanges] Set the toggle for the number of taps (1 or
2) on the orifice flange. If applicable, set the orientation of the taps as 90 degrees or 180
degrees. This toggle only appears for orifice flanges that have two taps.
Nipple Length (keyin) [Branch Nipples] Key in length of the branch nipple.
Reinforcement Data (toggle) [Branch Reinforcement] Set the toggle for the source of
the branch reinforcement data to By System or By User.
If you select the by user branch reinforcement option, the commodity option code is
automatically defined with a value of 699 (User-defined), as required by PDS.
Valve Operator (keyin or list) [Valves] Key in the valve operator type or select the
valve operator type from a list of valve operator types. The list of valve operator types and
the corresponding descriptions are defined in the RDB options list.
Valve Operator Display (toggle) [Valves] Set the toggle to ON or OFF to determine
whether the valve operator is displayed in the model.
Modifier (keyin) You can define this value for specific piping commodities not covered
by the previous list.
You can define the following optional data depending on your requirements.
Commodity Option (list) Attribute 4.
Max Temperature (keyin) Attribute 5. If no value is specified, the default value
(undefined) is assigned automatically.
Materials Grade (list) Attribute 25.
Standard Note Number (list) Attributes 26 and 27. Select the note for this commodity
from the list of standard notes defined in the approved Standard Note Library.
PDS Sort Code (keyin) Attribute 20. The specified value is automatically converted to
upper-case.
You can optionally define the following data on the basis of the user-specific requirements for
gaskets.
Commodity Option (list)
Max Temperature (keyin)
Fabrication Category (list)
Materials Grade (list)
Standard Note Number (list)
Implied Data
When defining a piping commodity, you can select the Implied Data option to indicate that the
commodity will have an associated implied item that will be included in MTO reports. After
selecting the option, set the toggle to Class Specific.
This option is intended for implied components that are not unique within the project. A lap-
joint flange is an example of the primary component, where the stub-end is the implied
component.
Refer to Commodity Implied Data Command (on page 98) for information on Project Specific
implied data.
When you select Accept to define a primary component, the system modifies the form display to
allow you to define the specification data for the implied component.
When you accept the specification data for the implied component, the system prefixes an
asterisk (*) to the commodity code of the primary component to indicate that implied data is
present.
The following specification data for the implied component are determined by the corresponding
data for the primary component. This data is displayed in review only fields.
Commodity Name Same as the primary component.
Commodity Option The commodity option code for the implied component is set to the
primary component's commodity option code plus 5000.
From NPD same as the primary component.
To NPD same as the primary component.
Model Code same as the primary component.
You can optionally define the following specification data for the implied component based on
your reporting requirements. The values for the implied component default to the corresponding
values for the primary component, except for the commodity code.
End Preparation (list)
Pressure Rating (keyin)
Table Suffix (list)
Schedule/Thickness (list)
Commodity Code (keyin) Key in the commodity code for the implied item. The system
converts this value to upper-case.
When size-dependent commodity codes are required, this will represent a somewhat
arbitrary value, referred to as the system commodity code, and will be used by the Report
Manager to reference the size-dependent commodity code.
Geometric Industry Standard (list)
Weight Code (list)
Fabrication Category (list)
Modifier (keyin)
Max Temperature (keyin)
Materials Grade (list)
Standard Note Number (list)
PDS Sort Code (keyin) (optional). The system converts the value to upper-case.
Requirements
The Material Description toggle must be set to ON.
If you have defined size-dependent commodity codes, this option will be ignored, unless both of
the following conditions are met:
The option for MTO to use the system commodity code to reference the material description
has been enabled through the Material Takeoff Options of the Project Data Manager.
The material descriptions have been created with embedded commodity code labels as the
means of inserting the size-dependent data into the material description.
Description Key in the material description for the specified commodity code and select
Accept.
The system adds the specified entry to the Material Description Library.
Create Select the type of specialty (Piping Specialty or Valves) from the list. Then key
in the component number for the specialty item to be created and select Accept. The system
activates the Create Piping Specialty Specification Data form.
Revise By Keyin Key in the component number of the specialty to be modified and
select Accept. The system activates the Revise Piping Specialty Specification Data form
with the data for the selected piping specialty.
Revise By List Select the piping specialty to be revised from the displayed List of Piping
Commodities and select Accept. The system activates the Revise Piping Specialty
Specification Data form with the data for the selected piping specialty.
Specialty Material Description You can set this toggle to ON to verify that the material
description for a specified commodity code has been defined in the Specialty Material
Description Library.
If no corresponding material description is found, the system activates the Add Entry to
Material Description Library form. See Add Entry to Material Description Library (on page
88).
Refer to RDB Options File (on page 66) for information on defining options for the applicable
input fields.
Refer to Piping Specialty Specification Data (203) (on page 45) for information on the attributes
for the Piping Specialty Specification Data table.
From NPD - First Size (keyin) Key in the first size value for the piping specialty. Both
the from and to values are loaded on the basis of this input.
To NPD - First Size (keyin) Key in the first size value for the piping specialty. Both the
from and to values are loaded on the basis of this input. The TO NPD field is only visible if
an applicable specialty type is selected.
End Preparation - First Size (list) Select from the list of end preparation values as
defined in the approved Standard Note Library.
Pressure Rating - First Size (keyin) Key in up to eight characters to define the pressure
rating.
Table Suffix - First Size (list) Select from the list of table suffix values as defined in the
approved Standard Note Library.
Schedule/Thickness (list) Select from the list of schedule/thickness values as defined in
the approved Standard Note Library.
Model Code (keyin) Key in the model code to be used to parametrically define the
piping specialty.
Physical Data ID (keyin) Key in the ID to be used as an arbitrary index into the
geometric data table for piping specialties.
Sort Code (keyin) Key in the sort code to be used as an arbitrary index into the
geometric data table for piping specialties. The system will convert the value to upper-case.
Fabrication Category (list) Select from the list of fabrication category values as defined
in the approved Standard Note Library.
You must define the following data for any reducing component.
NPD - Second Size (keyin) Key in the second size value for the piping specialty. Both
the from and to values are loaded on the basis of this input.
You must define the following data for valves. This data is stored in the modifier attribute.
Valve Operator (keyin or list) Key in the valve operator type or select the valve
operator type from a list of valve operator types (as defined in the RDB options file).
Valve Operator Display ON/OFF (toggle) Set the toggle to determine whether the
valve operator will be displayed in the model.
Specialty Type (field) This field can be used to select the type of piping specialty data to
be created based on settings in Standard Note Type 990 of the Standard Note Library. Place
a data point in this field to activate the Spec Writer Data Form Type pick list, then select
the preferred data type.
The system stores the specialty type as the input_form_type within the Piping Specialty Data
Table as a code-listed attribute for Standard Note Type 990.
Create Select the type of instrument (Instruments or Valves) from the list. Then key in
the component number for the instrument to be created and select Accept. The system
activates the Create Instrument Specification Data form.
Revise By Keyin Key in the component number of the instrument to be modified and
select Accept. The system activates the Revise Instrument Specification Data form with the
data for the selected instrument.
Revise By List Select the instrument to be revised from the displayed List of Instruments
and select Accept. The system activates the Revise Instrument Specification Data form with
the data for the selected instrument.
Specialty Material Description You can set this toggle to ON to verify that the material
description for a specified commodity code has been defined in the Specialty Material
Description Library.
If no corresponding material description is found, the system activates the Add Entry to
Material Description Library form. See Add Entry to Material Description Library (on page
88).
Refer to RDB Options File (on page 66) for information on defining options for the applicable
input fields.
Refer to Instrument Component Specification Data (204) (on page 48) for information on the
attributes for the Instrument Specification Data table.
Instrument Component Number (keyin) Key in the component number, which
uniquely identifies the instrument. The system verifies that the component number does not
already exist in the Unapproved Material Reference Database.
From NPD - First Size (keyin) Key in the first size value for the instrument. Both the
from and to values are loaded on the basis of this input.
To NPD - First Size (keyin) Key in the first size value for the instrument. Both the from
and to values are loaded on the basis of this input. The TO NPD field is only visible if an
applicable instrument type is selected.
End Preparation - First Size (list) Select from the list of end preparation values as
defined in the approved Standard Note Library.
Pressure Rating - First Size (keyin) Key in up to eight characters to define the pressure
rating.
Table Suffix - First Size (list) Select from the list of table suffix values as defined in the
approved Standard Note Library.
Schedule/Thickness (list) Select from the list of schedule/thickness values as defined in
the approved Standard Note Library.
Model Code (keyin) Key in the model code to be used to parametrically define the
instrument.
Physical Data ID (keyin) Key in the ID to be used as an arbitrary index into the
geometric data table for instruments.
Sort Code (keyin) Key in the code to be used as an arbitrary index into the geometric
data table for instruments. The system will convert the value to upper-case.
Fabrication Category (list) Select from the list of fabrication category values as defined
in the approved Standard Note Library.
You must define the following data for any reducing component.
NPD - Second Size (keyin) Key in the second size value for the instrument. Both the
from and to values are loaded on the basis of this input.
Instrument Type (field) This field can be used to select the type of instrument
component data to be created based on settings in Standard Note Type 990 of the Standard
Note Library. Place a data point in this field to activate the Spec Writer Data Form Type
pick list, and then select the preferred data type.
The system stores the specialty type as the input_form_type within the Piping Specialty Data
Table as a code-listed attribute for Standard Note Type 990.
You can optionally define the following data when two ends of the component require different
data. By PDS convention, if you specify the red end preparation, you must specify the
corresponding pressure rating, table suffix, and schedule/thickness.
End Preparation (list)
Pressure Rating (keyin)
Table Suffix (list)
Schedule/Thickness (list)
You must define the following data for valves. This information is stored in the modifier
attribute.
Valve Operator (keyin or list) Key in the valve operator type or select the valve
operator type from a list of valve operator types (as defined in the RDB options file).
Valve Operator Display ON/OFF (toggle) Set the toggle to determine whether the
valve operator will be displayed in the model.
You can optionally define the following data depending on your requirements for instruments.
Weight Code (list)
Geometric Industry Standard (list)
Modifier (keyin)
Materials Grade (list)
Standard Note Number (list)
Create Key in the name of the tap table to be defined. The system activates the Create
Tap Properties Data form.
Revise By Keyin Key in the name of the tap table to be modified. The system activates
the Revise Tap Properties Data form with the data for the selected tap table.
Revise By List Select the tap table to be revised from the displayed List of Tap
Properties Data (as defined in the Unapproved Material Reference Database) and select
Accept. The system activates the Revise Tap Properties Data form with the data for the
selected tap table.
Refer to RDB Options File (on page 66) for information on defining list options for the
applicable input fields.
Refer to Tap Properties Data (205) (on page 51) for more information on the attributes for the
Tap Properties Data.
Tap Table Name (keyin) Key in up to six characters for the table name. The combination of
the tap properties table name, the tap nominal piping diameter, and the tap option code must be
unique.
Nom Piping Diameter (keyin) Key in the nominal piping diameter for this tap
properties definition.
Tap Option (list) Select from the list of tap option codes as defined in the approved
Standard Note Library. If you do not select a tap option code, the default value (one) is
assigned automatically.
End Preparation (list) Select from the list of end preparation values as defined in the
approved Standard Note Library.
Rating (keyin) Key in up to eight characters to define the pressure rating.
Schedule/Thickness (list) Select from the list of schedule/thickness values as defined in
the approved Standard Note Library.
Tap Material Code (keyin) During the tap properties data creation process, if the Short
and Long Commodity Description toggles are set to ON, you are allowed to insert Tap
Material Code data into the Short Material Description Library. This is the code that may
optionally be used by MTO for appending the tap's material description to that of the
component which has been tapped.
If you have defined size-dependent commodity codes, this option will be ignored, unless
both of the following conditions are met:
The option for MTO to use the system commodity code to reference the material
description has been enabled through the Material Takeoff Options of the Project Data
Manager.
The material descriptions have been created with embedded commodity code labels as
the means of inserting the size-dependent data into the material description.
This form is used to define the material description for a specified commodity code in the
appropriate (short) Material Description Library. Refer to Material Description Data (on page
273) for more information on material descriptions.
Key in the material description for the specified commodity code and select Accept. This code
must be a unique index into the project's Material Description Libraries.
The system converts the specified tap material code to upper-case, and then adds the specified
entry into the appropriate Material Description Libraries.
Create Key in the system commodity code of the implied component to be created. The
system activates the Create Piping Commodity Implied Material Data form.
Revise By Keyin Key in the name of the piping materials class for the commodity item
to be modified. Then select the piping commodity to be revised from the displayed List of
Piping Commodities and select Accept. The system activates the Revise Piping Commodity
Specification Data form with the data for the selected piping commodity.
Revise By List Select the implied component definition to be revised from the displayed
list of Commodity Implied Data and select Accept. The system activates the Revise Piping
Commodity Implied Data form with the data for the implied component definition.
Refer to RDB Options File (on page 66) for information on defining list options for the
applicable input fields.
Refer to Piping Commodity Implied Material Data (212) (on page 56) for more information on
the attributes for the Piping Commodity Implied Material Data table.
System Commodity Code Key in the commodity code for the primary component. The
system converts the value to upper-case.
For this type of implied data to be reported with the primary component, the specification
data for the primary component must have enabled the option in each piping materials class
for which this implied data applies.
From Diameter (First Size) Key in the lowest first size value for which this implied
specification data applies.
To Diameter (First Size) Key in the highest first size value for which this implied
specification data applies. The to value must equal or exceed the from value.
From Diameter (Second Size) For reducing components, key in the lowest second size
value for which this implied specification data applies. In cases where the piping
commodity represents both a full-size component and a reducing component, this value
should equal the corresponding first size NPD. Otherwise, for a reducing component, this
value must be less than the corresponding first size value.
To Diameter (Second Size) For reducing components, key in the highest second size
value for which this implied specification data applies. The to value must equal or exceed
the from value.
Commodity Code (keyin) During the commodity implied data creation process, if the
Short and Long Commodity Description toggles are set to ON, you are allowed to insert
Commodity Code data into the Short and Long Material Description Libraries.
If you have defined size-dependent commodity codes, this option will be ignored, unless
both of the following conditions are met:
The option for MTO to use the system commodity code to reference the material
description has been enabled through the Material Takeoff Options of the Project Data
Manager.
The material descriptions have been created with embedded commodity code labels as
the means of inserting the size-dependent data into the material description.
This form is used to define the material description for a specified commodity code in the
appropriate Material Description Library (short or long). Refer to Material Description
Data (on page 273) for more information on material descriptions.
Key in the material description for the specified commodity code and select Accept. This
code must be a unique index into the project's Material Description Libraries.
The system converts the specified commodity code to upper-case, then adds the specified
entry into the appropriate Material Description Libraries.
Quantity (keyin) Key in a whole number or a decimal value for the quantity of the
implied component per primary component.
Fabrication Category (list) Select from the list of fabrication category values as defined
in the approved Standard Note Library.
Standard Note Number (list) You can optionally select from the list of standard notes
as defined in the approved Standard Note Library.
Select a Piping Material Class commodity and click Accept.
Table Checker
You can use the Table Checker option to perform on-line Table Checker validation for the
defined piping commodity specification data. When this option is enabled, table checker
validation will be performed for all piping commodities, except:
implied data specific to the piping materials class
gaskets
bolts
nuts
When you enable this option, the system displays a list of the defined Table Checker reports for
the project. Select the report validation to be performed and select Accept.
Refer to Table Checker Form (on page 298) for more information on creating a Table Checker
report definition.
Operating Sequence
1. Select the Piping Job Specification Manager option from the Reference Data Manager
form.
The system displays the Piping Job Specification Manager main form used to select the type
of data to process.
The data manipulation procedure for each of the database tables is similar. You can perform
the following activities for each of the entities.
2. Select Option
Select Unapprove ==> Approve to post the data from the unapproved
Specification/Material Reference Database to the approved database.
Select Option
Replace Commodity Subset revises (deletes and replaces) previously created size-
dependent or implied commodity data for a specific commodity or group of commodity
codes specified in a neutral file. This option is only available for the Size Dependent
Material Data and Project Implied Material Data commands.
The neutral files for the delivered USRDB data are in the directory
\win32app\ingr\rdusrdb\spec_data
classes.pmc the neutral file for the Piping Materials Class Data.
*.pcd The neutral files for the Piping Commodity Data are stored in a set of files of the
format pmcname.pcd. (For example, 1c0031.pcd defines all the commodity items for
piping materials class 1c0031.)
list.pcd a file that lists the neutral file names of all the delivered pcd files for the different
piping materials classes.
taps.data the neutral file for Tap Properties Data.
implied.data the neutral file for Project Implied Material Data.
A set of sample neutral files are delivered in the directory
\win32app\ingr\pddata\sample\data
specialty.data --- a sample neutral file for Piping Specialty Data.
instrment.data --- a sample neutral file for Instrument Data.
pcd_size.data --- a sample neutral file for Size Dependent Material Data.
You can copy the files and make changes before loading the information into the database.
Operating Sequence
1. Select the Load/Replace (or other load or replace) option. See the description above for
differences in Load, Replace, and Replace Commodity Subset.
2. Specify Neutral File Name
Key in the file specification for the neutral file that contains the data to be copied.
For Piping Commodity Data, you can load or replace a single file or a list of files. To
process a list of files, create a list file which lists each neutral file on a separate line. The
file list.pcd contains a list of all the delivered neutral files.
For Size-Dependent or Implied Commodity Data, you can replace specific commodity
codes or all the entries in the database. To replace specific commodity codes, create a
neutral file which contains only the commodity codes to be replaced.
For the Load option, the system displays a dialog box to indicate that the data loaded will be
appended to existing data. Select Accept to continue.
Delete Option
This option enables you to delete entries from the Piping Job Specification.
Operating Sequence
1. Select the Delete option.
The system displays a list of all the items in the database for the selected class of data.
Report Option
The Report options enable you to create neutral files using the information in the
Specification/Material Reference database. The order and field lengths of the data in the neutral
file is determined by a format file named spec_order.max. This format file is expected to reside
in the same network address and directory specified for the report output. A default format file
is delivered with the PD_Data product in the file
\win32app\ingr\pddata\sample\format\spec_order.max. If the spec_order.max file is not found
at the specified output directory, the system will use the default spec order.
If an unapproved Specification/Material Reference database exists for the active project, you can
select the database to process: approved or unapproved.
Operating Sequence
1. Select the Report option from one of the data forms (such as the Piping Commodity Data
form).
For Piping Commodity Data, select the appropriate PCD from the list.
2. Specify Neutral File Name
Key in the name of the neutral file to be created. You can change the Node Name and File
Path information.
3. Set the toggle to Submit Immediately or Delayed Submit.
For Delayed Submit, set the time to process the neutral file(s).
!
! This file contains the spec attribute order and their maximum
attribute
! lengths required for creating spec output neutral files. When
creating
! spec reports the system will default an attribute order and set of
! attribute lengths. The user can edit these attribute orders and
! lengths in this file ( spec_order.max ). If this file is in the
! directory where the software is being run the orders defined in
! this file will be used as the default attribute order and lengths.
201 = 2,16 3,3 4,3 5,10 6,7 7,7 8,8 9,6 10,6 11,6 12,6 13,6 14,6 15,6
16,6 17,6 18,8 19,6 20,6
202 = 3,6 4,6 5,7 6,6 7,6 8,6 9,8 10,8 11,8 12,8 13,8 14,8 15,8 16,8
17,6 18,16 19,6 20,6 21,7 22,6 23,6 24,6 25,6 26,6 27,6
203 = 2,20 3,6 4,6 5,8 6,8 7,6 8,8 9,8 10,6 11,8 12,8 13,8 14,8 15,8
16,6 17,8 18,6 19,7 20,6 21,6 22,6 23,6 24,6 25,6
204 = 2,20 3,6 4,6 5,8 6,8 7,6 8,8 9,8 10,6 11,8 12,8 13,8 14,8 15,8
16,6 17,8 18,6 19,7 20,6 21,6 22,6 23,6 24,6 25,6
205 = 3,8 4,6 5,8 6,8 7,8 8,10
211 = 2,16 3,8 4,8 5,8 6,8 7,16 8,8 9,8 10,8
212 = 2,16 3,8 4,8 5,8 6,8 7,16 8,8 9,6 10,6
Report Format Displays the Report Format form, which you can use to create, revise,
copy, or delete the record of a format file (not the format file). For more information, see
Report Format Form (on page 111).
Report Discrimination Data Displays the Discrimination Data form, which you can
use to create, revise, copy, or delete the record of a discrimination data file as well as the file
itself. For more information, see Report Discrimination Data Form (on page 114).
Report Displays the Report form, which you can use to create, revise, delete, and
approve report records and report files. For more information, see Report Form (on page
119).
Report Management Data Displays the Report Management Defaults form, which
you can use to create a record in the project control database of the default nodename and
path for the report definition files. This option is primarily used for setup. For more
information, see Report Management Defaults Form (on page 128).
Group Workflow
There is a definite workflow for at least the first time you create a report. First, use the Report
Management Data option to specify defaults for the nodename and path of the report definition
files. By defining the defaults first, you can prevent keying in a nodename and path on each
form. If you want to use a different nodename or path than the defined default, simply place a
data point in that field and key in the modification.
The following steps can be done in any order: create your format record, discrimination data
record, and discrimination data file using the Report Format and Report Discrimination Data
options. Reports cannot be generated until the format file, the discrimination data file, and their
corresponding records have been established.
This form enables you to create, copy, revise, or delete a record of the location of the format file
in the project control database. An option is also provided that enables you to copy a record and
its corresponding ASCII format files.
The format file defines the data that will be reported and the way in which that data will be
displayed. Reports cannot be generated unless a format file exists and a record of the file's
location has been entered into the project control database.
Create Displays the Format Creation/Revision form, which enables you to add a new
record of a format file in the project control database. For more information, see Format
Creation/Revision Form (on page 112).
Copy Displays the Format Creation/Revision form, which copies the record of an
existing format file from the project control database along with the corresponding ASCII
format file. For more information, see Format Creation/Revision Form (on page 112).
Revise Displays the Format Creation/Revision form, which modifies a record of an
existing format file in the project control database. For more information, see Format
Creation/Revision Form (on page 112).
Delete Displays the Deletion form, which deletes an existing record of a format file from
the project control database. If the record of the format file is deleted, reporting cannot be
performed. For more information, see Format Deletion Form (on page 113).
This form creates, copies, or revises a record in the project control database; this record defines
the location of a format file. The format file itself defines the contents and format of the report.
Both the location specification and the format file must exist to report on PDS data.
Number A unique number of up to 24 characters. Specifies the short name in the project
control database used to identify the record of the format file.
Description A description of up to 40 characters for the format file.
File Specification The file name of the format file to reference.
File Path The disk location of the format file. This field retains the active setting.
File Node The nodename of the system on which the format file is located. This field
retains the active setting.
Operating Sequence
1. Select Create, Copy, or Revise.
A list of available records displays for copy or revision. To create a database record, go to
Step 3.
2. Select Report Format
3. From the displayed list, select the record to be copied or revised. Then select Accept.
Key-in fields are displayed for you to specify the required database information.
4. Specify Report Format Data
Type information in each of the displayed fields, taking care to press Enter in each field.
Then select Accept.
The project control database is updated.
This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
This form creates, copies, revises, and deletes a discrimination data file from the specified
directory. The associated record in the project control database is also copied, revised, or
deleted as needed.
A discrimination data file is an ASCII file that designates which models will be included in a
report. That is, discrimination data specifies the scope of the report. The project control
database record specifies the name and location of the discrimination data file that is to be
associated with a specific report.
Create Displays the Discrimination Data Creation form, which creates a new
discrimination data file. The associated project control database record is also created. For
more information, see Discrimination Data Creation Form (on page 115).
Copy Displays the Discrimination Data Revision form, which copies an existing data
file. The associated project control database record is also copied. For more information,
see Discrimination Data Revision Form (on page 117).
Revise Displays the Discrimination Data Revision form, which modifies discrimination
data. You can use this option to revise the contents of the discrimination data file, the
location of the discrimination file, and the associated record in the project control database.
For more information, see Discrimination Data Revision Form (on page 117).
Delete Displays the Deletion form, which deletes a discrimination data file as well as its
associated record in the project control database. For more information, see Discrimination
Data Deletion Form (on page 119).
Commands
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Search Criteria Defines search criteria for specified attributes in the
Specification/Material Reference Database. For more information, see Search Criteria
Form (on page 116).
Field Descriptions
Number --- Key in a unique number to name the discrimination data record to be created by
discrimination. The number can be up to 24 characters in the Project Control Database.
This number is a short name to identify the record of the discrimination data file.
Description --- Key in a description of the discrimination data file with up to 40 characters
in the Project Control Database.
File Specification --- Key in the filename of the discrimination data file to create.
The system verifies that the file does not already have a record in the project.
File Path --- Displays the disk location of the discrimination data file. This field retains the
active setting.
File Node --- Displays the nodename where the discrimination data file is located. This field
retains the active setting.
Operating Sequence
1. Select the Search Criteria option from the Discrimination Data form.
2. Select Entity
Select the database entity that contains the data to be restricted.
The system displays the attributes for the selected entity.
3. Select Attribute
Select the attribute to be restricted.
The system displays the selected attribute and displays a list of operators.
4. Select Operator
Select the required operator to define the search criteria.
The system displays the selected operator and prompts you to key in an attribute value.
5. Enter Attribute Value
Key in the attribute value. For a sub-string search, key in a string to appear anywhere within
the attribute value (do not use wild cards).
If the attribute is code-listed, the system displays a list of values from the standard note
library. Select the value and select Accept.
The system validates the input and displays the defined search criteria.
6. Accept or Select And/Or Operator.
Select AND to specify an additional condition or select OR to specify an alternative
condition.
OR
Accept the defined search criteria.
Commands
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Search Criteria Defines search criteria for specified attributes in the
Specification/Material Reference Database. For more information, see Search Criteria
Form (on page 116).
Field Descriptions
Number Key in a unique number to name the discrimination data record with up to 24
characters in the Project Control Database. This number is a short name to identify the
record of the discrimination data file.
Description Key in a description of the discrimination data file with up to 40 characters
in the Project Control Database.
File Specification Key in the filename of the discrimination data file to reference.
The system verifies that the file does not already have a record in the project.
File Path Displays the disk location of the discrimination data file. This field retains the
active setting.
File Node Displays the nodename where the discrimination data file is located. This field
retains the active setting.
If prompted to... Do this:
Select Discrimination Data Select the record number of the discrimination data file to
revise and select Accept.
Specify Discrimination Key in any changes to the discrimination data record displayed
Data in the information fields, and select as many of the
Discrimination Data options as necessary to define the
discrimination data file.
This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
Report Form
When you select Report from the Report Manager form, the Report form is displayed.
This form creates, revises, and deletes report records and report files. A report record holds
specifications for a report; these specifications include the report name, the report description,
and which format file, discrimination data file, and search criteria data file to use to generate a
report.
The report name is not the title that is printed on the report; the title is included in the
format file.
At the end of each report, a parameters page is included that contains the following information:
Report Output The report number, report title, report creation/revision date, and report
node, path, and file name.
Format The report format number, description, and node, path, and file name.
Discrimination Data The report discrimination data number, description, and file
location (network address, path, and file name). The following discrimination data is also
included: list of model numbers (with discipline), volume (if applicable), search criteria (if
applicable), and sorting sequence.
Search Criteria The report search criteria number, description, and file location (node,
path, and file name. The following search criteria data is also included: list of model
numbers (with discipline), volume (if applicable), search criteria (if applicable), and sorting
sequence.
Options
Create Displays the Report Creation form, which creates a report record and generates
a report. For more information, see Report Creation Form (on page 121).
Revise Displays the Revise Report form, which regenerates a report from an existing or
revised report record. For more information, see Revise Report Form (on page 123).
Delete Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form (on page 125).
Approve Displays the Report Approval form, which approves an existing report. For
more information, see Report Approval Form (on page 125).
Multi-Create Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form (on page
126).
Use this form to create a report record and to generate a report. Because report records are stored
in the project control database, you can use them repeatedly.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings, and it is automatically populated if you have specified this data on the Report
Management Data form. For more information, see Report Management Defaults Form
(on page 128).
Report Node The name of the system on which the report output file will be located.
This field retains the active settings, and it is automatically populated if you have specified
this data on the Report Management Data form. For more information, see Report
Management Defaults Form (on page 128).
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit Immediately/Submission is Delayed Specifies when the report will be
processed. When this toggle is set to Submission is Delayed, additional fields display for
you to specify the date and time that the report is to be generated.
Operating Sequence
1. From the Report form, select Create.
The Report Creation form is displayed.
2. Specify Report Data
Key in the report record information. Then select the appropriate report format file,
discrimination data file, and search criteria data file.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
This form revises an existing report record and generates a report from the project control
database. An option is also provided to update (in some cases) the report record without
generating a report output file. Similarly, you can choose to generate an updated report output
file without updating the report record.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings.
Report Node The name of the system on which the report output file will be located.
This field retains the active settings.
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.
Revise Data Only/Revise Report and Data Specifies revision of the report data only
(Revise Data Only) or revision of the report data and the report output file (Revise Report
and Data). To revise the report specification without updating the report output file, make
the necessary changes, set this toggle to Revise Data Only, and click Accept. To revise the
report output file only, set this toggle to Revise Report and Data without modifying any of
the fields, and click Accept. To modify both the report file and the report output file, make
the necessary changes, set this toggle to Revise Report and Data, and click Accept.
If you update any field other than Report Number and Report Title, this toggle is
automatically set to Revise Report and Data, and the report output file is generated.
Operating Sequence
1. From the Report form, select Revise.
The Report Creation form is displayed with a list of available report files.
2. Select Report
From the displayed list, select the report to be revised. Then click Accept.
The fields update to display the selected report file specifications.
3. Revise Report Information
Update the report record information as needed.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
5. Specify whether the report is to be generated now (Submit Immediately) or later
(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.
This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
Use this form to select a report to approve. Approving a report means that a database attribute is
set from not approved (the default) to approved. This approval status provides a way for you to
flag reports that you have run and verified that the output data is valid. When a report is revised,
the approval status is automatically reset to not approved.
Number The 24-character unique name (also called short name) of the report record.
Description The 40-character description of the report record.
Operating Sequence
1. From the Report form, select Approve.
The Report Approval form is displayed.
2. From the displayed list, select a report to approve. Then click Accept.
The Approval form is displayed.
For more information, see the PD_Report User's Guide.
Operating Sequence
1. From the Report form, select Multi-Create.
The Report Multiple Submit form is displayed.
2. Select Reports for Submission
From the displayed list, select the reports to submit. Highlighted reports are selected; select a
highlighted report to remove the highlight and to not submit the report.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
4. Specify whether the report is to be generated now (Submit to Batch Immediately) or later
(Delayed Submit to Batch). If you choose delayed submission, specify the date and time
that the report is to be submitted.
5. Click Accept to submit the reports.
This form creates a record in the project control database of the node name and path of the report
definition files. This option is used primarily for setup.
Report Path Specifies the default path of the report output files.
It is recommended that you not send output reports to your system's temporary (that
is, tmp or temp) directory.
Report Node Specifies the default node name of the system on which report output files
are located.
Report Format Path Specifies the default path of the format files.
Report Format Node Specifies the default node name of the system on which format
files are located.
Report Discrimination Data Path Specifies the default path of the discrimination data
files.
Report Discrimination Data Node Specifies the default node name of the system on
which discrimination data files are located.
Report Search Criteria Data Path Specifies the default path of the report search criteria
data files.
Report Search Criteria Data Node Specifies the default node name of the system on
which report search criteria data files are located.
Operating Sequence
1. From the Report Manager form, select Report Management Data.
The Report Management Defaults form is displayed.
2. Accept or Exit
In the fields provided, key in the default paths and node names for the report output files,
format files, discrimination data files, and search criteria data files. Then click Accept.
Example
Table_Data_Definition 'L1001'
! Description= B16.5 CL150-1.1, -20 to 800
! By=DCG Ckd By=DG Rev=0 Date=13-Feb-1987
No_Inputs 1 No_Outputs 1
Input_Interpolation 1, Next_One
Units= DF, PSIG
! Temperature Pressure
-20 285
100 285
200 260
300 230
400 200
500 170
600 140
650 125
700 110
750 95
800 80
END
Parameters
Table_Data_Definition (character-6) This parameter specifies the name of the
Temperature and Pressure Service Limits Table. These tables use the following naming
conventions.
first character: L
second character: the pressure rating of the piping materials class as defined by the
following code:
1= CL150 8= GRAVHD K= CL5000
2= CL300 9= OTHER L= CL6000
3= CL400 A= CL125 M= CL9000
4= CL600 F= CL800 N= CL10000
5= CL900 G= CL2000 R= CL15000
6= CL1500 H= CL3000 T= CL20000
7= CL2500 J= CL4500 V= CL30000
third, fourth, and fifth characters: numbers from 001 through 999 used to make the table
name unique.
Input_Interpolation 1, Next_One This statement tells the system to interpolate between
known values for the temperature value. The statement must be included as shown in the
table format for the desired interpolation to take place.
Temperature (real) This field identifies the maximum temperature value. You can use
both positive (+) and negative (-) values. Values are assumed to be positive unless
otherwise indicated.
Pressure (real) This field identifies the value for pressure corresponding to the
previously defined temperature. Negative (-) values are not accepted in this field.
Table_Data_Definition 'DWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 1 No_Outputs 0
Units= NPD_IN
! Diam
WWWWW
WWWWW
WWWWW
WWWWW
WWWWW
WWWWW
WWWWW
END
This table can also be used to define the equivalency for English and metric diameters. The
output column defines the English equivalent for the matching metric size.
Table_Data_Definition 'DWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 1 No_Outputs 1
Units= NPD_MM, NPD_IN
! Metric Diam
WWWWW WWWWW
WWWWW WWWWW
WWWWW WWWWW
WWWWW WWWWW
WWWWW WWWWW
END
Examples
Table_Data_Definition 'D036'
! Description= From 0.5 to 36
! By=NP Ckd By=DG Rev=0 Date=22-Jan-1987
No_Inputs 1 No_Outputs 0
Units= NPD_IN
! Diam
0.5
0.75
1
1.5
2
3
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
END
Table_Data_Definition 'DB001'
! Description= From 6mm to 900mm (0.375 to 36)
! By=aw Ckd By= Rev=1 Date=17_jul 1989
No_Inputs 1 No_Outputs 1
Units= NPD_MM, NPD_IN
! metric diam, imperial diam
10 0.375
15 0.5
20 0.75
25 1
40 1.5
50 2
80 3
100 4
150 6
200 8
250 10
300 12
350 14
400 16
450 18
500 20
550 22
600 24
650 26
700 28
750 30
800 32
850 34
900 36
END
Parameters
Table_Data_Definition (character 6) This field identifies the name of the NPD table.
These tables use the following naming conventions:
first character: D
second, third, and fourth characters: numbers from 001 through 999 used to make the
table name unique.
Diam - Nominal Piping Diameter (integer) This field identifies the value for nominal
diameter. You can use the value ET_AL to indicate that any nominal diameter value from
the TDB which is equal to or greater than the value in the preceding line is an acceptable
nominal diameter for the PMC.
Table_Data_Definition 'TWWWW
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, SC_TH_IN, SC_TH_IN, SC_TH_IN, SC_TH_IN,
SC_TH_IN
! Diam Min Thick Ret Thick Thread Thick Preferred
Schedules/Thicknesses
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
WWWWW ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ ZZZZZ
ZZZZZ ZZZZZ
END
Example
Table_Data_Definition 'TA501'
! Description= A,0.063CA,0.0071D<=24, 0.0075D>=26
! By=DCG Ckd By=DG Rev=0 Date=31-Jan-1987
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, SC_TH_IN, SC_TH_IN, SC_TH_IN, SC_TH_IN,
SC_TH_IN
! Diam Min Thick Ret Thick Thread Thick Preferred
Schedules/Thicknesses
0.5 .147 .06 - S-160 - - - -
0.75 .154 .06 - S-XS - - - -
1 .179 .06 - S-XS - - - -
1.5 .2 .06 - S-XS - - - -
2 .154 .06 - S-STD - - - -
3 .216 .06 - S-STD - - - -
4 .237 .07 - S-STD - - - -
6 .28 .1 - S-STD - - - -
8 .250 .1 - S-STD - - - -
10 .250 .1 - S-STD - - - -
12 .250 .1 - S-STD - - - -
14 .250 .12 - S-STD - - - -
16 .250 .12 - S-STD - - - -
18 .250 .12 - S-STD - - - -
20 .250 .13 - S-STD - - - -
22 .250 .15 - S-STD - - - -
24 .250 .15 - S-STD - - - -
26 .3125 .17 - S-10 S-STD - - -
28 .3125 .19 - S-10 S-STD - - -
30 .3125 .20 - S-10 S-STD - - -
32 .3125 .21 - S-10 S-STD - - -
34 .3125 .23 - S-STD - - - -
36 .3125 .24 - S-STD S-XS - - -
END
Parameters
Table_Data_Definition - Thickness Data Table Name (character 6) This field
identifies the name of the table. These tables use the following naming conventions:
first character: T
second character: code which combines the criteria type with the maximum size for
which threaded components are used in the piping materials class, as defined below.
Criteria 1 applies to carbon steels and low-alloy steels; criteria 2 applies to aluminum
alloys, stainless steels, and non-ferrous alloys.
A= Criteria 1 with no threaded components
B= Criteria 1 with threaded components up to 1 inch diameter
C= Criteria 1 with threaded components up to 1.5 inch diameter
D= Criteria 1 with threaded components up to 2 inch diameter
F= Criteria 2 with no threaded components
G= Criteria 2 with threaded components up to 1 inch diameter
Table_Data_Definition 'MWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 2 No_Outputs 6
Input_Interpolation 2, Next_One
Units= INT, DF, IN, IN, DEC, PSI, DEC, IN
! Mill Tol
! Mat Gr Temp Thick Range Y S % Value
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
END
Example
Table_Data_Definition 'ML01'
! Description= ASTM A53-B, A106, API 5L-B
! By=DCG Ckd By=DG Rev=0 Date=24-Feb-87
No_Inputs 2 No_Outputs 6
Input_Interpolation 2, Next_One
Units= INT, DF, IN, IN, DEC, PSI, DEC, IN
! Mill Tolrnce
! Mat Gr Temp Thick Range Y S % Value
142 -20 - - .4 20000 12.5 -
142 100 - - .4 20000 12.5 -
Parameters
Table_Data_Definition - Materials Data Table Name (character 6) This field
identifies the number of the table. These tables use the following naming conventions:
first character: M
second character: the applicable design code, per the following convention:
A= ASME Section I [Power Boilers] L= ANSI-B31.3 [Petroleum]
B= ASME Section III [Nuclear] M= ANSI-B31.4 [Oil Transport]
C= Do not use N= ANSI-B31.5 [Refrigeration]
D= ASME Section VIII-1 [Unfired Vessels] P= ANSI-B31.8 [Gas Transmission]
E= ASME Section VIII-2 [Unfired Vessels] Q= ANSI-B31.9 [Building Services]
J= ANSI-B31.1 [Power] T= API
K= ANSI-B31.2 [Fuel Gas] V= AWWA
third and fourth characters: numbers from 01 through 99 used to make the table name
unique.
Delivered Equations
The thickness and branch reinforcement logic for the following equations are hardcoded in the
software.
EJ01
Source - ANSI-B31.1.1986 [Power Piping]
Thickness logic from paragraph 104.1, equation 3
Reinforcement logic from paragraph 104.3.1(D)
EL01
Source - ANSI-B31.3c.1986 [Chemical Plant and Petroleum Refinery Piping]
Thickness logic from paragraph 304.1, equation 3a
Reinforcement logic from paragraph 304.3.3 & Code - Appendix H
The following considerations apply to both thickness equations and branch reinforcement
calculations.
Pressures and temperatures used in thickness/branch reinforcement calculations are derived
from data in the Piping Design Database. Both normal and alternate pressure and
temperature conditions are considered. If actual values exist for the normal design or the
alternate design pressure/temperatures, the corresponding operating conditions are ignored.
If default values exist for BOTH sets of design conditions, both normal and alternate
operating conditions are used. At least one complete set of conditions must be defined.
Once the proper pressure and temperature sets are determined, their units of measure are
converted to those used in the Temperature-Pressure Table associated with the Piping
Materials Class to which the component belongs. Conversions are performed using the
procedures and conversion factors defined for the Units of Measure in Appendix F.
Only positive pressure is considered. The system reports an error if you request a thickness
calculation involving a vacuum condition (negative pressure).
Independent sets of thickness/reinforcement calculations are carried out for each applicable
pressure/temperature set. In each calculation set, table values that are temperature dependent
are determined on the basis of the temperature applicable to the calculation set being
considered. The thicker calculated thickness is used.
Thickness Equations
The following considerations apply to thickness equations.
Thickness calculations are triggered by specifying an equation name in the
Schedule/Thickness attribute of the Piping Commodity Specification Data. An asterisk (*)
followed by a name (of the form xyyy) defines the specific calculation or table lookup to be
used for wall thickness. The letters that form this code have the following meaning:
x alphanumeric code that defines the equation to use in the calculation. Possible values and
their definitions are:
If this character is C, the schedule/thickness for the applicable end of the component is
determined by calculations using the thickness equation defined in the
DEFAULT_WALL_THICK_EQUATION attribute of the Piping Materials Class
database table.
If the code is any character other than C, the schedule/thickness for the applicable end of
the component is determined by calculations using the thickness equation with the name
EX.
yyy casting, joint or structural grade quality factor (E) times 100.
This factor is one of the parameters used in the thickness calculation. If you are defining a
calculation to be performed on a seamless fitting (E=1) but want to match the thickness for
the mating welded pipe (E=0.85), the quality factor for the pipe should be entered here.
For components with ends having different nominal diameters, independent sets of thickness
determinations are performed for each NPD. One or more ends may need to calculated, as
determined by specific *xyyy entries in the Commodity Item entity. The larger thickness
(calculated or predefined) is used. For example:
A 20" x 10" reducer is defined in the Piping Commodity Table to have a *xyyy 20" end
and a 0.55" thick, 10" end. The calculation of the 20" end results in a 0.5" thickness. A
0.55" thick reducer is used.
A 24" x 20" reducer is defined in the Piping Commodity Table to have a *XYYY 24"
end and a *XYYY 20" end. The calculation of the 24" end results in a 0.6" thickness.
The calculation of the 20" end results in a 0.5" thickness. A 0.6" thick reducer is used.
All thickness calculations involve a casting, joint, or structural grade quality factor (E).
The value for this factor is YYY/100, where YYY is defined in the entry *XYYY made
under the Schedule Thickness attribute for the Commodity Item under consideration.
Branch Reinforcement
The following considerations apply to branch reinforcement calculations.
The need to perform a branch reinforcement calculation is triggered by
the placement of a generic branch component with the actual item name determined
from a branch table. (See Branch Insertion Tables.)
the presence of more than one item name in the Preferred Branch AABBCC Codes
fields of the applicable branch table.
the applicable branch reinforcement being either a reinforcing weld or a reinforcing pad.
All calculations involve a casting, joint, or structural grade quality factor (E). The value for
this factor is YYY/100, where YYY is defined in the Modifier attribute for entries with an
item name of PIPING.
The fillet welds joining reinforcing pads to the header and to the branch are considered in
determining the available reinforcement area.
Spec Access
The execution of a pipe wall thickness calculation is performed when the variable PIPE_OD_n is
encountered in the physical data definition of a pipe or component. Therefore, pipe outside
diameter must be calculated or retrieved from a table before the wall thickness can be used as
part of a table name.
After the actual thickness is calculated, it is compared against the thickness range in the
Materials table and the retirement thickness in the Thickness Data table. The system uses the
greater of these values as the uncorroded wall thickness. Then the system adds the corrosion
allowance from the PMC, the thread thickness from the wall thickness table, and the mill
tolerance from the Materials table. This revised thickness is compared against the minimum
thickness value in the Thickness Data table. The larger of these two values is compared against
the preferred thickness value in the Thickness Data table, and the next largest preferred value is
used for table look-ups and is stored in the TDB.
If the Thickness Data table uses schedules as preferred thickness, the schedules are translated to
an actual thickness by a table look-up from a table of the form
MALWT//Term_type//shc_thick//generic_flag//weight_code
and output 2 gives the actual wall thickness.
Table_Data_Definition 'BWWWW_WW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 2 No_Outputs 3
Units= NPD_IN, NPD_IN, AN*6, AN*6, AN*6
! Nom Diam Preferred Branch
! Header Branch AABBCC Codes
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
WWWWW WWWWW 'ZZZZZZ' 'ZZZZZZ' 'ZZZZZZZ'
END
Example
Table_Data_Definition 'BA501_90'
! Description= A,0.063CA, Use with TA501
! By=DCG Ckd By=DCG Rev=3 Date=17-Aug-1988
No_Inputs 2 No_Outputs 3
Units= NPD_IN, NPD_IN, AN*6, AN*6, AN*6
! Nom Diam Preferred Branch
12 10 '6Q3C82' - -
12 12 '6Q3C22' - -
END
Parameters
Table_Data_Definition - Branch Insertion Table Name (character 6) This field
identifies the name of the table. This name results from the compounding of the Branch
Table entry defined in the Piping Materials Class with the acute angle of intersection
between the header and the branch.
These tables use the following naming conventions:
first character: B
second character: a code which combines the criteria type with the maximum size for
which threaded components are used in the PMC, as defined below. Criteria 1 applies to
carbon steels and low-alloy steels; criteria 2 applies to aluminum alloys, stainless steels
and non-ferrous alloys.
A= Criteria 1 with no threaded components
B= Criteria 1 with threaded components up to 1 inch diameter
C= Criteria 1 with threaded components up to 1.5 inch diameter
D= Criteria 1 with threaded components up to 2 inch diameter
F= Criteria 2 with no threaded components
G= Criteria 2 with threaded components up to 1 inch diameter
H= Criteria 2 with threaded components up to 1.5 inch diameter
I= Criteria 2 with threaded components up to 2 inch diameter
Z= Special criteria
third character: the corrosion allowance of the piping materials class for which the table
is intended, per the following criteria:
1= None C= 304 clad P= Polyester lined
2= 0.020" D= 304L clad Q= Polypropylene lined
3= 0.030" E= 316 clad R= PTFE lined
4= 0.050" F= 316L clad S= Saran lined
5= 0.063" G= 317 clad T= Teflon lined
6= 0.10" H= 317L clad U= TK31 lined
7= 0.125" J=321 clad V= R11 lined
8= 0.188" L= Cement lined W= R15 lined
9= 0.250" M= Epoxy lined X= R18 lined
A= 405 clad N= Glass lined Y= Other 1
B= 410S clad O= Kynar lined Z= Other 2
fourth and fifth characters: numbers from 01 through 99 used to make the table name
unique.
The second part of the table name defines the acute angle of intersection. Negative
values and values less than 45 degrees or greater than 90 degrees are not valid.
However, when dealing with branch reinforcements, negative values and values less
than 20 degrees or greater than 90 degrees are not valid (per ANSI B31.1 and ANSI
B31.3).
The data fields are sorted by header NPD and then by branch NPD.
Nom Diam Header - NPD for Run (integer) --- This field identifies the nominal diameter
of the header at the intersection. This is the member with the largest nominal diameter.
Nom Diam Branch - NPD for Branch (integer) --- This field identifies the nominal
diameter of the branch member at the intersection. This is the member with the smallest
nominal diameter.
Preferred Branch AABBCC Codes (character 6) --- These field identify the commodity
item name of the component used to reinforce the intersection.
If only one item name is listed, no branch reinforcement calculation is performed. The
specified item is placed at the intersection.
If two or more item names apply in one line, the system calculates the branch
reinforcement thickness. The system tests the listed item names sequentially (from left
to right) until the applicable strength criteria are satisfied.
Therefore, these codes should be arranged in ascending strength sequence (for example,
reinforcing welds, followed by reinforcing pads, followed by weldolets.)
If you enter a value of LOOKUP in the AABBCC field, it will refer to the
BRANCHID.LN file in the \project directory. You must create this file and edit the
attributes. For an example of the file format, see BRANCHID.LN File (on page 148)
Typically, the codes are from one of the following types:
Reinforcing elements, such as reinforcing welds and pads.
Weld-on components reinforcing the intersection such as saddles and weldolets.
Weld-in components actually making the intersection such as laterals and tees.
BRANCHID.LN File
The BRANCHID.LN file must be placed in the \project directory and is formatted as shown
below:
MATCHING_ATTRIBUTES: 3
LINE_DEF: WC-0104
BRANCH_DEF: 5192; 5192; 6Q3C22
BRANCH_DEF: 5768; 5320; 6Q3C80
LINE_DEF: WC-0105
BRANCH_DEF: 5192; 5032; ATECH
LINE_DEF - Used with the MATCHING_ATTRIBUTES value. In the example above, the
first MATCHING_ATTRIBUTES: 3 value is WC-0104. The software searches for pipeline
WC-0104 to place the branching component.
BRANCH_DEF - Determines which branch value is placed on the pipeline based on the
first and second size attributes. If the first and second size attributes match, the branch value
is used. For example, in the second BRANCH_DEF line of the WC-0104 LINE_DEF
section, the first and second size attributes are 5768 and 5320, respectively. If these
attributes match up, then the value 6Q3C80 is placed on the WC-0104 pipeline.
BRANCH_DEF - Determines which branch value is placed on the pipeline based on the
first and second size attributes. If the first and second size attributes match, the branch value
is used. For example, in the second BRANCH_DEF line of the WC-0105 LINE_DEF
section, the first and second size attributes are 5192 and 5032, respectively. If these
attributes match up, then the value ATECH is placed on the WC-0105 pipeline.
END
Table_Data_Definition 'GWWW_WWWWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 2 No_Outputs 1
Units= NPD_IN, DF, IN
! Diam TMx Gaskt Gap
WWWWW ZZZ ZZZZZ WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
END
Example
Table_Data_Definition 'G001_1500'
! Description= SP-1000 deg F , RJ-1001 deg F
! By=DCG Ckd By=DCG Rev=0 Date=24-Jun-1987
No_Inputs 2 No_Outputs 1
Units= NPD_IN, DF, IN
! Diam TMx Gaskt Gap
0.5 1000 .125
0.75 1000 .125
1 1000 .125
1.5 1000 .125
2 1000 .125
3 1000 .125
4 1000 .125
6 1000 .125
8 1000 .125
10 1000 .125
12 1000 .125
14 1000 .125
16 1000 .125
18 1000 .125
20 1000 .125
24 1000 .125
0.5 1001 .16
Parameters
Table_Data_Definition - Gasket Gap Table Name (character 6) This field identifies
the name of the table. This name results from the compounding of the entry defined in the
Piping Materials Class with the rating of the bolted end to which the gasket gap applies.
These tables use the following naming conventions:
first character: G
next three characters: numbers from 001 through 999 used to make the table name
unique.
The second part of the table name is the rating of the components to which it applies.
The characters CL and # are not included in the rating designation.
Diam - Nominal Piping Diameter This field identifies the applicable NPD value. The
units of measure used to define the NPD must match the NPD units to be used in the Piping
model.
TMx - Maximum Temperature This field identifies the maximum temperature for the
gasket as defined in the Piping Commodity Specification Data (Table 202 attribute 5). (The
system must find a match of the commodity item temperature and the value in this column
for successful retrieval of data.)
The units of measure used to define the temperature must be the same as the units used in the
Temperature Pressure Service Limits table.
Gasket Gap This field identifies the full gasket gap to be used.
Table_Data_Definition 'FC001'
! Description= By Process Vendor
! By=SCC Ckd By=SCC Rev=1 Date=12-OCT-90
No_Inputs 1 No_Outputs 0
Units= INT
521
522
524
527
530
533
536
539
542
545
550
END
Parameters
Table_Data_Definition (character 6) This field identifies the name of the Fluid Code
table. These tables use the following naming conventions:
first and second character: FC
third, forth, and fifth characters: numbers from 001 to 999 used to make the table name
unique.
Fld Cd (integer) This field lists the code list numbers for the valid fluid codes from code
list set 125.
RDB Tables
The following reference data tables are defined in the Spec Table Library. These tables are
required to provide basic data for the performance of the software.
Example
Table_Data_Definition 'COMMODITY_ITEM_NAME'
! Description= Correlation of hardcoded component types and AABBCC
codes
! By=GJH Ckd By=DCG Rev=2 Date=16-May-1989
No_Inputs 1 No_Outputs 1
Units= INT, AN*6
! Comp AABBCC
! Type Code
1 'PIPING'
2 'TUBING'
3 'HOSE'
4 '6Q2C23'
5 '6Q2C01'
6 '6Q2C01'
7 '6Q2C76'
8 '6Q2C75'
9 '6Q2C56'
10 '6Q2C55'
11 '6Q3C45'
12 '6Q3C60'
13 '6Q2C47'
14 '6Q2C84'
15 '6Q3C47'
16 '6Q3C49'
17 '6Q3C50'
18 '6Q3C25'
19 '6Q3C47'
20 '6Q3C77'
21 '6Q3C82'
22 '6Q3C80'
> 23 '6Q3C88'
> 24 '6Q2C24'
25 '6Q1C76'
26 -
27 -
28 '6Q2C16'
29 '6Q2C19'
30 '6Q2C21'
31 '6Q2C08'
32 -
33 -
34 -
35 -
36 -
37 -
38 'IND'
39 -
40 -
41 '6Q2C49'
42 '6Q2C51'
43 '6Q2C53'
44 '6Q2C06'
45 '6Q3C89'
END
The meaning of the various component types is outlined below:
The system uses the bend angle to search this table for the matching range of bend angles. The
system uses the index into the Commodity Item Name table for either a full size bend or a
reducing bend depending upon the nominal piping diameters of the line route segments that form
the bend. The system searches for an entry in the table where the angle is greater than or equal
to the low bend angle and less than the high bend angle.
You can define more than one bend deflection table for a project provided they are given
different names. For example, one table can apply to underground piping and the other to
aboveground piping. Refer to the Component Placement form in the Project Data Manager
for information on defining the bend deflection table for a project or model.
The table name format that applies to this table is:
TNF=G04 BEND_DEFLECTION
Example
Table_Data_Definition 'BEND_DEFLECTION'
! Description= Component type to use as function of angle between runs
! By=EPZ Ckd By=DCG Rev=2 Date=09-Nov-1987
No_Inputs 2 No_Outputs 2
Units= DEC, DEC, INT, INT
! Angle Comp Type To Use
! Low High Full Red
0.1 44.9 10 0
44.9 45.1 9 0
45.1 89.9 8 0
89.9 90.1 7 14
90.1 179.9 13 0
END
The following listing shows the component types used in this example.
bend angle index
low high full size reducing size
0.1 44.9 10 ( < 45 trimmed bend) N/A
44.9 45.1 9 (45 bend) N/A
45.1 89.9 8 (45-90 trimmed bend) N/A
89.9 90.1 7 (90 bend) 14 (reducing 90 bend)
90.1 179.9 13 ( > 90 trimmed bend) N/A
Example
Table_Data_Definition 'PIPE_RUN_LENGTH'
! Description= Minimum allowable piping segment run length
! By=DCG Ckd By=GJH Rev=1 Date=04-Aug-1987
No_Inputs 1 No_Outputs 1
Units= NPD_IN, IN
! Diam Min Length
2 0.25
6 0.50
12 0.50
24 0.75
36 1.00
96 1.00
144 1.00
192 1.00
END
Example
Table_Data_Definition 'PIPE_LENGTH'
! Description= Minimum and preferred allowable plain piping length
! By=DCG Ckd By=GJH Rev=1 Date=04-Aug-1987
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! Min Preferred
! Diam Length Length
2 2 2
6 2 3
12 2 4
24 3 6
36 3 9
96 3 12
144 6 12
192 6 12
Example
Table_Data_Definition 'BOLT_LENGTH'
! Description= Preferred bolt lengths (maximum of 300 entries)
! By=GJH Ckd By=DCG Rev=1 Date=04-Aug-1987
No_Inputs 2 No_Outputs 1
Units= IN, IN, IN
! Bolt Length Preferred
! Low High Bolt Length
0.0 1.5 1.5
1.5001 1.75 1.75
1.7501 2 2
2.0001 2.25 2.25
2.2501 2.5 2.5
2.5001 2.75 2.75
2.7501 3 3
3.0001 3.25 3.25
3.2501 3.5 3.5
3.5001 3.75 3.75
3.7501 4 4
4.0001 4.25 4.25
4.2501 4.5 4.5
4.5001 4.75 4.75
4.7501 5 5
5.0001 5.25 5.25
5.2501 5.5 5.5
5.5001 5.75 5.75
5.7501 6 6
6.0001 6.25 6.25
6.2501 6.5 6.5
6.5001 6.75 6.75
6.7501 7 7
7.0001 7.25 7.25
7.2501 7.5 7.5
7.5001 7.75 7.75
7.7501 8 8
8.0001 8.25 8.25
8.2501 8.5 8.5
8.5001 8.75 8.75
8.7501 9 9
9.0001 9.25 9.25
9.2501 9.5 9.5
9.5001 9.75 9.75
9.7501 10 10
10.0001 10.25 10.25
10.2501 10.5 10.5
10.5001 10.75 10.75
10.7501 11 11
11.0001 11.25 11.25
11.2501 11.5 11.5
11.5001 11.75 11.75
11.7501 12 12
12.0001 12.25 12.25
12.2501 12.5 12.5
Example
Table_Data_Definition 'BOLT_LENGTH'
! Description= Preferred bolt lengths (maximum of 300 entries)
! By=GJH Ckd By=DCG Rev=1 Date=04-Aug-1987
No_Inputs 2 No_Outputs 1
Units= IN, IN, IN
! Bolt Length Preferred
! Low High Bolt Length
0.0 1.5 1.5
1.5001 1.75 1.75
1.7501 2 2
2.0001 2.25 2.25
2.2501 2.5 2.5
2.5001 2.75 2.75
2.7501 3 3
3.0001 3.25 3.25
3.2501 3.5 3.5
3.5001 3.75 3.75
3.7501 4 4
4.0001 4.25 4.25
4.2501 4.5 4.5
4.5001 4.75 4.75
4.7501 5 5
5.0001 5.25 5.25
5.2501 5.5 5.5
5.5001 5.75 5.75
5.7501 6 6
6.0001 6.25 6.25
6.2501 6.5 6.5
6.5001 6.75 6.75
6.7501 7 7
7.0001 7.25 7.25
7.2501 7.5 7.5
7.5001 7.75 7.75
7.7501 8 8
8.0001 8.25 8.25
8.2501 8.5 8.5
8.5001 8.75 8.75
8.7501 9 9
9.0001 9.25 9.25
9.2501 9.5 9.5
9.5001 9.75 9.75
9.7501 10 10
Table_Data_Definition 'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_BLT'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
No_Inputs 2 No_Outputs 4
Units= IN, IN, IN, AN*8, AN*8, AN*8
! Bolt Bolt Length Bolt Commodity Code
! Diam Low High 1 2 3
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
END
Do not load the Bolt Commodity Code table with more than 900 lines.
If Bolt Commodity Code is set to Bolt Commodity Code Table, the Commodity Code and
Bolt Description is reported from this table.
Example
Table_Data_Definition 'WELD_1C0031'
! Description= Weld Clearance Table
By=XXX Ckd By=XXX Rev=1 Date=01-22-1999
No_Inputs 2 No_Outputs 4
Units= NPD_IN, INT, NPD_IN, INT, IN, IN
Weld Weld
NPD Type NPD Type Radius Overall
From From To To Increase Length
1 1 2 25 6 18
3 1 4 25 8 24
5 1 6 25 10 30
7 1 8 25 6 18
9 1 10 20 10 18
9 21 10 22 12 24
9 23 10 25 14 30
11 1 12 25 10 30
END
Parameters
NPD From - NPD To (integer) These parameters identify the range of nominal piping
diameters (lower bound to higher bound) for the weld in NPD units. The To value must
equal or exceed the From value.
Weld_Type_From - Weld_Type_To (integer) These parameters identify the range of
weld type values (from standard note 1100). The To value must equal or exceed the From
value.
Radius_Increase (integer - NPD Units) This parameter identifies the increase to be
applied to the NPD of the weld for use in generating a cylinder to represent the construction
tolerance envelope for the weld.
Overall_Length (integer) This parameter identifies the length of the cylinder for the
weld construction tolerance envelope.
Example
Table_Data_Definition 'DRV_WELD_DEF'\
Description= WELD GRAPHICS DIMENSIONS
! TNF=G12T By=XXX Ckd By=XX Rev=0 Date= 04-Oct-2000
No_Inputs 2 No_Outputs 4
Units= NPD_IN, INT, NPD_IN, INT, DEC, DEC
! From_NPD From_Weld_Type TO_NPD To_Weld_Type Weld_Dia_Increase
Weld_Thickness_NPD_Units
2 10 7 22 0.25 0.25
6 12 10 22 0.25 0.25
8 10 12 22 0.25 0.25
END
Parameters
From NPD - TO _NPD (integer) These parameters identify the range of nominal piping
diameters (lower bound to higher bound) for the weld in NPD units. The To value must
equal or exceed the From value.
From_Weld_Type - To_Weld_Type (integer) These parameters identify the range of
the weld type values (from standard note 1100). The To value must equal or exceed the
From value.
Weld_Dia_Increase (decimal) This parameter identifies the percentage increase to be
applied to the NPD of the weld for use in displaying a cylinder to represent the weld in
SmartPlant Review. For example, if the NPD is 6" and the increase is .25, the diameter of
the weld cylinder would be 7 1/2" (6 x 1.25 = 7.5).
Weld_Thickness (decimal) This parameter identifies the percentage to be applied to the
NPD of the weld to determine the thickness of the cylinder.
If this table is absent or if there is no NPD range encapsulating the WELD NPD, the
weld graphics dimensions will be determined as follows:
Diameter = 130% of the NPD at the weld.
Thickness = 25% of the NPD at the weld.
Table_Data_Definition 'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_GKT'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! Gasket Diameter
! NPD Inside Outside
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
END
Table_Data_Definition 'Fit_Length_Table'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
No_Inputs 1 No_Outputs 1
Units= INT, IN
! Weld Type Adjust.
1 ZZZZZZZ
11 ZZZZZZZ
21 ZZZZZZZ
22 ZZZZZZZ
Example
Table_Data_Definition 'Component_Mirror_Table'
No_Inputs 1 No_Outputs 3
Units= AN*6, INT, INT, INT
! Model Code Option 1 Option 2 Option 3
Parameters
Model Code This column lists the model codes for components which require non-
symmetrical mirroring. The model code is used as input by the calling Eden module.
Option 1 This column represents the TOGGLE_<INT> Eden variable or specific
command instruction used to control a non symmetrical mirror operation. This column can
have any of the following values.
mirror logic in the Eden module. All items with these setting must have a tutorial
accessed in the Eden module to allow the user to change the TOGGLE during
placement.
For example, if Option 1 = 1, check the TOGGLE_1 Eden variable in the Eden module
to perform specific logic to compensate for a mirrored component.
degrees instead of mirroring it.
The Model Code item will be rotated due to a specific non symmetrical definition where
there are no non symmetrical connect points involved.
the specific item.
The item will not be mirrored due to specific non symmetrical definition. In other
words, the item is only stocked in one non symmetrical configuration which has non
symmetrical connect points involved.
Option 2 & Option 3 These columns are not currently used.
Example
Table_Data_Definition 'Operator_Mirror_Table'
! This Table has NOT been Checked
!
No_Inputs 1 No_Outputs 3
Units= AN*6, INT, INT, INT
! Model Code Option 1 Option 2 Option 3
OI_33 1 - -
OI_35 1 - -
OI_43 1 - -
OI_53 1 - -
A_1033 1 - -
OP_331 1 - -
OP_332 1 - -
OP_333 1 - -
OP_334 1 - -
OP_351 1 - -
OP_493 1000 - -
OP_494 1000 - -
OP_573 1000 - -
OP_574 1000 - -
OP_711 1000 - -
OP_853 1000 - -
OP_854 1000 - -
Parameters
Model Code This column lists the model codes for operators which support mirroring.
The model code is used as input by the calling Eden module.
Option 1 This column represents the TOGGLE_<INT> Eden variable or specific
command instruction used to control a non symmetrical mirror operation. This column can
have any of the following values.
mirror logic in the Eden module. All items with these setting must have a tutorial
accessed in the Eden module to allow the user to change the TOGGLE during
placement.
For example, if Option 1 = 1, check the TOGGLE_1 Eden variable in the Eden module
to perform specific logic to compensate for a mirrored component.
degrees instead of mirroring it.
For example, if Option 1 = 1000, the Model Code item will be rotated due to a specific
non symmetrical definition where there are no non symmetrical connect points involved.
tell the Mirror command to rotate the component 180 degrees instead of mirroring it.
The item is only stocked in one non symmetrical configuration and does not have non
symmetrical connect points involved.
Option 2 & Option 3 These columns are not currently used.
Example
Table_Data_Definition 'Default_End_Prep'
!
No_Inputs 1 No_Outputs 1
Units= INT, INT
!
!E_P_in E_P_out
331 441
392 421
441 331
421 391
Data Retrieval
The system performs a table look-up using the active end preparation value. In the table above,
the last line (421 391) indicates that the end prep for an instrument/specialty connected to a
SWE (421) component will default to PE (391).
If the table does not exist in RDB, the end prep for the instrument/ specialty defaults to the end
prep of the connected piping component. In the example above, the instrument/specialty end
prep would default to SWE (421).
With the 7.1 release, the limitation on the size of tables in the Piping Job Spec Table Library was
increased from approximately 20,000 bytes to 60,000 bytes or 750 lines.
Operating Sequence
The Piping Job Specification Tables command activates the Specification Tables Library/Data
Management form used to control the contents of the spec table library.
Create Library (on page 174) used to create a new Piping Job Spec Table Library.
Compress Library (on page 174) used to compress the Piping Job Spec Table library.
Unapproved ==> Approved (on page 174) used to copy the unapproved Piping Job Spec
Table library to the approved library.
Create/Interactive (see "Create/Interactive Spec Tables" on page 174) used to compile
table files and add the resulting code to the Piping Job Spec Table library. You can create a
single table or specify a list of tables to be created.
Create/Batch (see "Create/Batch Spec Tables" on page 175) used to compile and add
tables to the library via batch processing.
Revise (see "Revise Spec Tables" on page 176) used to select a table from the library for
editing and compile the revised table definition.
Delete (see "Delete Spec Tables" on page 177) used to delete a specified table from the
library.
Report (see "Report on Spec Tables" on page 178) used to create a report of the library
contents.
List (see "List Spec Tables" on page 180) used to list the files contained in the library.
Extract (see "Extract Spec Tables" on page 180) used to extract a table file from the
library for editing or printing.
Refer to Default Project Control Data (on page 23) for information on defining the default
location for library files. You can also change the default file locations for each option at any
time.
Create Library
This option is used to create a new Piping Job Spec Table Library. It automatically creates the
object library (.l), the text library (.l.t), and table revision management library (.l.t.r) for the
library that is being created.
The system displays the approved and unapproved Piping Job Spec Table Library names as
defined in the RDB Management Data.
Compress Library
This option is used to compress the Piping Job Spec Table library. Any tables which have been
deleted from the library will be removed.
Operating Sequence
1. Select the Create option from the Specification Tables Library/Data Management form.
2. Set the toggle to Single to process a single table file or to List to process a list file.
3. Specify Filename for processing
Key in the name of the table file or list file to be compiled and added to the active library.
(Refer to PJS Tables and Functions (on page 131) for information on the table formats.)
4. Accept or Select Other Option
Accept the file and begin processing.
Operating Sequence
1. Select the Create/Batch option from the Specification Tables Library/Data Management
form.
2. Set the toggle to Single to process a single table file or to List to process a list file.
3. Specify Filename for Processing
Key in the name of the table file or list file to be added to the active library.
4. Accept to Submit or Set Submit Time
Set the toggle to Submit Immediately or Delayed Submit.
For Delayed Submit, set the time to process the table files.
5. Accept the file and begin processing.
The system submits the request to the batch queue PDreference.
Operating Sequence
1. Select the Revise option from the Specification Tables Library/Data Management form.
Operating Sequence
1. Select the Delete option from the Specification Tables Library/Data Management form.
Operating Sequence
1. Select the Report option from the Specification Tables Library/Data Management form.
2. Set the toggle to Default Report to create a list file of all the table files in the library.
OR
Set the toggle to Revision Dates Report and key in a revision date to process all tables
modified since the specified revision date. The report lists the full contents of the modified
tables with individual revision dates per line.
3. Set the toggle to Report on Unapproved or Report on Approved to define the source of
information to be reported. This toggle is only displayed when both the approved and the
unapproved library are being used.
4. Accept to Form Report or Revise Report Parameters
Select Accept to form the report using the default parameters, and proceed to step 6.
OR
Key in the file information (Node Name and File Path) for the location of the neutral file to
be created.
5. Select Save, Print, or Print/Save.
For Print or Print/Save, select the print queue from the list of displayed queues. Refer to
the section on Plot and Print Queues in the Project Administrator Reference Guide for more
information on setting up multiple print queues.
If you select the Save or Print/Save option, the system creates a file named spec_tables in
the default source file location or in the location you specified.
6. Accept to Submit or Specify Submit Time
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set the
time to process the request.
7. Accept to Create Report
Select Accept to create the specified report file.
Operating Sequence
1. Select the List option from the Specification Tables Library/Data Management form.
2. You can use the scroll bar to scroll through the available tables.
Operating Sequence
1. Select the Extract option from the Specification Tables Library/Data Management form.
2. Select the tables from the list of files and select Accept. You can use the scroll bar to scroll
through the available files. You can extract multiple tables at one time.
OR
Select Extract All to to bulk extract all the tables in one operation.
The system pulls the files out of the library and places them in the default directory for
Piping Spec Data. The system also writes the names of the extracted files to a file named
PD_tbl_list.
If the list file is less than 24 hours old, the system appends the entries to the file; otherwise,
it overwrites the file.
The first line of each Eden module defines the type of module (such as symbol processor) and
the module name. This statement determines a two- character category code to be prefixed to
the module name in the object library. This prefix is only used by the system; it should not be
keyed-in as part of the module name.
The entries in the library use the following prefixes to identify the type of data.
SP Symbol Processor
PD Physical Data Definition Module
UF User Function Module
MG Model Parametric Shape Definition Module
DG Detailed Parametric Shape Definition Module
Symbol Processors
A symbol processor is the controlling function or logic used to produce the graphics for a
commodity item, piping specialty, instrument, pipe support, or interference envelope. During
component placement, the symbol processor:
accesses the active component design parameters
assigns connect points
calls the required physical data modules
determines and calls the required parametric shape modules.
The system retrieves the active component parameters which are dependent upon a connect point
from the PJS in terms of green, red, or tap connect point properties. The symbol definition
assigns the data corresponding to these connect point types (green, red, or tap) to the physical
connect point numbers (CP1, CP2, CP3, CP4, or CP5).
The first line of the Eden module defines the type of module and the module name. The
following statement is used in the Eden modules to indicate a symbol processor module.
Symbol_Processor 'module name'
This statement tells the system to use the category code SP for the prefix. You should use the
following conventions in assigning the module name. The module name is determined by the
type of component being placed (commodity item or specialty item).
For a commodity item, the system searches for the New Item Name (model code) of the
commodity item as the module name. If the New Item Name is blank in the Commodity
Item entity, the system searches for the Item Name as the module name.
For a specialty item, the system searches for the specialty item name (derived from the PJS)
as the module name.
For an instrument, the system searches for the instrument name (derived from the PJS) as the
module name.
The delivered symbol processors are identified in the library with the prefix SP.
The following lists the symbol processor SPGAT 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
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'
This statement tells the system to use the category code SS for the prefix.
The sub-symbol processor name for operators is a concatenation of the characters OP_ and the
modifier value from the Commodity Item entity in the PJS database. The value is expressed as a
code list number from CL550 (operator/actuator type). If the value is a positive number (such as
3) the operator is placed with the valve. If the value is a negative number (such as -3) the
operator is not placed with the valve. (This is useful in segregating large diameter valves which
almost always have a valve operator from small diameter valves which frequently do not have an
operator.)
The symbol processor for the gate valve calls a sub-symbol processor (Subcomponent = 'OP' //
Valve_Operator) which places an operator on the valve. The following depicts the sub-symbol
processor SSOP_3 which is used to control the placement of a hand wheel operator on the valve.
! HANDWHEEL OPERATOR
Sub_Symbol_Processor 'OP_3'
If ( Operator_Orient .EQ. TRUE ) Then
prompt = 1.0
Call Prompt_to_Orient_Operator ( prompt )
EndIf
physical_data_source = 'OPERATOR_3'
Call Get_Physical_Data ( physical_data_source )
parametric_shape = 'OP3'
Call Draw_Parametric_Shape ( parametric_shape )
Stop
End
physical_data_source = 'VALVE_2_AMS'
Call Get_Physical_Data ( physical_data_source )
Call Read_Table ( Table_Name_A, input, output )
Surface_Area = Output_1
Wet_Weight = Output_2
F_to_C_Dim_1 = Output_3
If ( Term_Type_1 .EQ. Term_Type_2 ) Then
F_to_C_Dim_2 = F_to_C_Dim_1
Else
F_to_C_Dim_2 = Output_4
EndIf
F_to_F_Dim = F_to_C_Dim_1 + F_to_C_Dim_2
If ( Valve_Operator .LE. 24.0 ) Then
Call Read_Table ( Table_Name_W, input, output )
Dry_Weight = Output_1
EndIf
Return
End
Physical_Data_Definition 'VALVE_2_AMS'
Input_1 = Nom_Pipe_D_1
If ( Gen_Type_1 .EQ. BOLTED ) Then
table_name = 'BLT' // Term_Type_1 // Pr_Rating_1 //
Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_1
Thickness_1 = Output_2
Seat_Depth_1 = Output_3
Thickness_1 = Thickness_1 - Seat_Depth_1
CP_Offset_1 = Gasket_Sep_1
If ( Symbology .EQ. MODEL ) Then
Thickness_1 = 0.0
Depth_1 = 0.0
Pipe_OD_1 = 0.0
Body_OD_1 = Facing_OD_1
Else
table_name = 'MAL_300_5'
Depth_1 = Thickness_1
Input_1 = Nom_Pipe_D_1
Call Read_Table ( table_name, input, output )
Pipe_OD_1 = Output_2
Body_OD_1 = Pipe_OD_1
EndIf
Else
If ( Gen_Type_1 .EQ. MALE ) Then
table_name = 'MAL' // Term_Type_1 // Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_2
Thickness_1 = 0.0
Depth_1 = 0.0
Seat_Depth_1 = 0.0
CP_Offset_1 = 0.0
Pipe_OD_1 = Facing_OD_1
Body_OD_1 = Facing_OD_1
Else
table_name = 'FEM' // Term_Type_1 // Pr_Rating_1 //
Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_1
Depth_1 = Output_2
Seat_Depth_1 = 0.0
Thickness_1 = 0.0
If ( symbology .EQ. MODEL ) Then
Depth_1 = 0.0
CP_Offset_1 = 0.0
Pipe_OD_1 = 0.0
Body_OD_1 = Facing_OD_1
Else
CP_Offset_1 = -Depth_1
table_name = 'MAL_300_5'
Call Read_Table ( table_name, input, output )
Pipe_OD_1 = Output_2
Body_OD_1 = Pipe_OD_1
EndIf
EndIf
EndIf
If ( Term_Type_2 .EQ. Term_Type_1 .AND. Nom_Pipe_D_1 .EQ.
Nom_Pipe_D_2 )
Then
Facing_OD_2 = Facing_OD_1
Pipe_OD_2 = Pipe_OD_1
Body_OD_2 = Body_OD_1
Thickness_2 = Thickness_1
Depth_2 = Depth_1
Seat_depth_2 = Seat_Depth_1
CP_Offset_2 = CP_Offset_1
Else
Input_1 = Nom_Pipe_D_2
If ( Gen_Type_2 .EQ. BOLTED ) Then
table_name = 'BLT' // Term_Type_2 // Pr_Rating_2 //
Gen_Flag_Red
Call Read_Table ( table_name, input, output )
Facing_OD_2 = Output_1
Thickness_2 = Output_2
Seat_Depth_2 = Output_3
Thickness_2 = Thickness_2 - Seat_Depth_2
CP_Offset_2 = Gasket_Sep_2
If ( Symbology .EQ. MODEL ) Then
Thickness_2 = 0.0
Depth_2 = 0.0
Pipe_OD_2 = 0.0
Body_OD_2 = Facing_OD_2
Else
Depth_2 = Thickness_2
table_name = 'MAL_300_5'
Input_1 = Nom_Pipe_D_2
Call Read_Table ( table_name, input, output )
Pipe_OD_2 = Output_2
Body_OD_2 = Pipe_OD_2
EndIf
Else
If ( Gen_Type_2 .EQ. MALE ) Then
table_name = 'MAL' // Term_Type_2 // Gen_Flag_Red
Call Read_Table ( table_name, input, output )
Facing_OD_2 = Output_2
Thickness_2 = 0.0
Depth_2 = 0.0
Seat_Depth_2 = 0.0
CP_Offset_2 = 0.0
Pipe_OD_2 = Facing_OD_2
Body_OD_2 = Facing_OD_2
Else
table_name = 'FEM' // Term_Type_2 // Pr_Rating_2 //
Gen_Flag_Red
Call Read_Table ( table_name, input, output )
Facing_OD_2 = Output_1
Depth_2 = Output_2
Seat_Depth_2 = 0.0
Thickness_2 = 0.0
If ( Symbology .EQ. MODEL ) Then
Depth_2 = 0.0
CP_Offset_2 = 0.0
Pipe_OD_2 = 0.0
Body_OD_2 = Facing_OD_2
Else
CP_Offset_2 = -Depth_2
table_name = 'MAL_300_5'
Input_1 = Nom_Pipe_D_2
Call Read_Table ( table_name, input, output )
Pipe_OD_2 = Output_2
Body_OD_2 = Pipe_OD_2
EndIf
EndIf
EndIf
EndIf
Table_Name_A = Item_Name // Geo_Ind_Std // Term_Type_1
Table_Name_W = Commodity_Code
Input_1 = Nom_Pipe_D_1
Input_2 = Nom_Pipe_D_2
If ( Term_Type_1 .EQ. Term_Type_2 .AND. Nom_Pipe_D_1 .EQ.
Nom_Pipe_D_2 )
Then
Table_Name_A = Table_Name_A // Pr_Rating_1 // 'A'
Else
If ( Gen_Type_1 .EQ. Gen_Type_2 ) Then
Model_Parametric_Shape_Definition '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 )
length = F_to_C_Dim_2 - Thickness_2
Call Draw_Cone ( length, diameter, Body_OD_2 )
Call Draw_Cylinder_With_Capped_Ends ( Depth_2, Facing_OD_2 )
Call Move_By_Distance ( CP_offset_2 )
Call Place_Connect_Point ( CP2 )
Return
End
Model_Parametric_Shape_Definition 'OP3'
Call Define_Connect_Point_Geometry ( OPERATOR )
Call Convert_NPD_to_Subunits ( Nom_Pipe_D_1, dia )
dist = dia + Min_Cyl_Dia * 0.5
angle = 90.0
radius = ( Dimension_2 - Min_Cyl_Dia ) * 0.5
Call Draw_Cylinder_With_Capped_Ends ( Dimension_1, Min_Cyl_Dia
)
Call Move_by_Distance ( -dist )
Call Rotate_Orientation ( angle, Secondary )
Call Rotate_Orientation ( angle, Normal )
Call Move_Along_Axis ( -radius, Secondary )
Call Draw_Torus ( radius, angle, Min_Cyl_Dia )
Call Draw_Torus ( radius, angle, Min_Cyl_Dia )
Call Draw_Torus ( radius, angle, Min_Cyl_Dia )
Call Draw_Torus ( radius, angle, Min_Cyl_Dia )
Return
End
By segregating data into separate physical data libraries you can access a subset of the total
physical data available for a project. You can also build a specific set of physical data for a
particular project. The following table types are required for piping and instrument components.
Generic dimensional data
Generic tables contain data which is not specific to a particular symbol (such as flange
outside diameter or flange thickness). These tables are identified by the prefix BLT, FEM,
or MAL (for the termination type) and end with the extension .TBL (the table name is
independent of the name of the physical data module).
Specific commodity data
Specific tables contain commodity data which is specific to a particular component (such as
dimensions, water weight, and surface area). These specific tables use the model code or
commodity code as part of the table name to classify data by symbol type.
The system uses the water weight data to compute the wet weight using the specific
gravity of the operating fluid.
fluid weight = water weight * specific gravity for fluid
operating weight = dry weight + fluid weight
The surface area data enables the system to perform paint requirement calculations and
insulation weight calculations.
Specific commodity dry weight data
Piping Specialty physical data
The dimensions, dry weight, water weight, and surface area for specialty items can be stored
in a set of tables or defined at placement.
Instrument physical data
The dimensional data, dry weight, water weight, and surface area for instruments can be
stored in a set of tables or defined at placement.
You can form the name of a physical data table from attributes for the component (such as
geometry standard and end preparation). However, the table name cannot exceed 46 characters.
Additional Information
Data Retrieval from the Physical Data Library (on page 195)
Example of Physical Data Look-Up (on page 195)
Generic Tables
The spec access for a six-inch gate valve defines the end preparation at both connect points as
Raised Face Flanged End (code list value 21) which is a bolted connection. As shown in the
listing for VALVE_2_AMS, the table name for a bolted connection on a two-connect point valve
is
table_name= 'BLT' // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green
Using the values from the Piping Job Specification (PMC=1C0031, 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).
Specific Tables
The specific tables are used to define the main body of the valve. Refer to Table Requirements
(on page 228) for an outline of the types of tables which are required to place a 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 (P31A)
Using this table name format, the dimension table for a hand wheel operator on a 6" gate valve
is:
GAT_BLT_150_3_A
This table returns the stem length and the wheel diameter for the handwheel operator.
The origin of a component must lie between connect point 1 and connect point 2.
Flanges should be defined with the green connect point representing the flanged connect
point and the red connect point representing the non-flanged connect point.
A valve operator is always placed at the component origin of the corresponding valve body.
To insure consistency in pipe cut length calculations, the connect points of a component
should be located using face-to-face or face- to-center dimension rather than end-to-end or
end-to-center dimension.
A change of direction component placed by component center must be defined such that
connect point 1 is on the primary axis.
For miter bend components, the system requires that the item name and the new item name
be unique with respect to the number of miter joints of the bend. In other words, the item
name specifies the number of miter joints of the bend.
For branches (tees and laterals), the system uses the first and second size to access the
branch table and determine the item name of the component to be placed at the branch point
(intersection). Depending on the active values, the branch table may define a single
component, or a set of two or three components.
Create Library (on page 201) Used to create a new Graphic Commodity Library.
Compress (on page 201) Used to compress the Graphic Commodity library.
Unapproved ==> Approved (on page 201) Used to copy the unapproved Graphic
Commodity library to the approved library.
Create/Interactive (see "Create/Interactive Graphic Commodity Data" on page 201) Used
to compile Eden source files and insert them in the Graphic Commodity Library. You can
create a file or specify a list of files to be created.
Create/Batch (see "Create/Batch Graphic Commodity Data" on page 202) Used to
compile Eden source files and add the files to the library via batch processing. Used to
compile Eden source files via batch processing.
Revise (see "Revise Graphic Commodity Data" on page 203) Used to select an Eden
module from the library, edit the file, and put the recompiled file back into the library.
Delete (see "Delete Graphic Commodity Data" on page 204) Used to remove an Eden
module from the library.
Report (see "Report Graphic Commodity Data" on page 205) Used to create a report
listing the library contents.
List (see "List Graphic Commodity Data" on page 206) Used to display the Eden modules
in the library.
Extract (see "Extract Graphic Commodity Data" on page 207) Used to extract an Eden
module from the library for editing or printing.
You can set the toggle at the bottom of the form to determine the Eden modules to be listed.
Full List - Lists all the Eden modules in the Graphic Commodity Library.
Sub-string - Limits the list to those Eden modules which contain a specified substring.
Create Library
This option is used to create a new Graphic Commodity Library. It automatically creates the
object library (.l) and the text library (.l.t) for the library that is being created.
The system displays the approved and unapproved Graphic Commodity Library names as
defined in the RDB Management Data.
Compress
This option is used to compress the Graphic Commodity library. Any tables which have been
deleted from the library will be removed.
Operating Sequence
1. Select the Create option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
4. Key in the name of the Eden file or list file to be compiled and added to the active library.
The system verifies the existence of the specified file.
The system displays the default node name and path for the Eden modules, as specified in
the Default Project Control Data, at the bottom of the form.
You can use the default setting or modify these fields to override the default location for this
operation.
5. Accept or Select Other Option
Accept the file and begin processing.
Operating Sequence
1. Select the Batch Load option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
4. Key in the name of the Eden file or list file to be compiled and added to the active library.
The system confirms the existence of the specified file.
The system displays the default node name and path for the Eden modules, as specified in
Operating Sequence
1. Select the Revise option.
The system displays the Eden modules in the Graphic Commodity Library.
The system extracts the specified file from the library and activates the text editor (specified
for PD_EDITOR in the control.sh file) to enable you to modify the file.
Operating Sequence
1. Select the Delete option.
The system displays the Eden modules in the Graphic Commodity Library.
Operating Sequence
1. Select the Report option from the Data Management form.
2. Key in the file information for the location of the report file to be created or use the
displayed defaults.
3. Select Print or Print/Save.
Then select the print queue from the list of displayed queues. Refer to the section on Plot
and Print Queues in the Project Administrator Reference Guide for information on setting
up multiple print queues.
If you select the Print/Save option, the system will create a file named piping_eden in the
defined default source file location.
4. Accept to Form Report or Revise Report Parameters
Select Accept to create the report file.
Operating Sequence
1. Select the List option.
The system displays the Eden modules in the Graphic Commodity Library.
2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.
Operating Sequence
1. Select Extract from the Data Management form.
Operating Sequence
1. Select Physical Data Library Manager command from the Reference Data Manager
form.
Options
Create Library (on page 211) Used to create a new Physical Dimension Library.
Compress (on page 211) Used to compress the Physical Dimension library.
Unapproved ==> Approved (see "Unapproved to Approved" on page 211) Used to copy
the unapproved Physical Dimension library to the approved library.
Create/Interactive (see "Create/Interactive Physical Commodity Data" on page 211) Used
to process table files and add the resulting code to the active Physical Dimension library.
You can create a single table or specify a list of tables to be created.
Create/Batch (see "Create/Batch Physical Commodity Data" on page 212) Used to
compile and add table files to the active library via batch processing.
Revise (see "Revise Physical Commodity Data" on page 213) Used to select a table file
from the library for editing and put the revised file back into the library.
Delete (see "Delete Physical Commodity Data" on page 214) Used to remove a table file
from the library.
Report (see "Report Physical Commodity Data" on page 215) Used to create a report of
the library contents.
List (see "List Physical Commodity Data" on page 217) Used to display the table files in
the active library.
Extract (see "Extract Physical Commodity Data" on page 217) Used to extract a table file
from the library for editing or printing.
Create Library
This option is used to create a new Physical Dimension Library. It automatically creates the
object library (.l), the text library (.l.t), and table revision management library (.l.t.r) for the
library that is being created.
The system displays the approved and unapproved Physical Dimension Library names as defined
in the RDB Management Data.
Compress
This option is used to compress the Physical Dimension library. Any tables which have been
deleted from the library will be removed.
Unapproved to Approved
This option copies the unapproved Physical Dimension library to the approved library.
Operating Sequence
1. Select the Create option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
Key in the name of the table file or list file to be processed and added to the active library.
The system displays the default node name and path for the table files, as specified in the
Default Project Control Data, at the bottom of the form.
You can use the default setting or modify these fields to override the default location for this
operation.
4. Accept or Select Other Option
Accept the file and begin processing.
The system processes the source file and, if successful, it stores the resulting object file in the
active library and stores the source file in the associated text library.
Operating Sequence
1. Select the Create option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
Key in the name of the table file or list file to be processed and added to the active library.
The system displays the default node name and path for the table files, as specified in the
Operating Sequence
1. Select the Revise option.
The system displays the table files in the active library.
Operating Sequence
1. Select the Delete option.
The system displays the table files in the active library.
Operating Sequence
1. Select the Report option from the Data Management form.
Operating Sequence
1. Select the List option.
The system displays the table files in the active library.
2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.
Operating Sequence
1. Select Extract from the Data Management form.
Table Conventions
Table Names
Unless otherwise indicated, values for specific and generic parameters are stored in tables whose
names are derived from parameters in the PJS. When naming ASCII files in the text libraries, if a
dot (.) or a hyphen (-) is included in the Sc/Th column of the piping job specification, the dot or
hyphen will be converted to a dollar sign ($) when the table name or ASCII file name is created.
The actual character, and not the $, is displayed in all fields representing the actual attribute
involved. The following examples illustrate how thicknesses are represented on the basis of the
above rule:
Actual Characters ASCII
equivalent
.25 $25
1 1
1.375 1$375
With version 5.0, the Physical Data Library Manager will respect the use of a dash (-) in a table
name. This allows you to include a dash in the commodity code for a piping commodity valve,
where the commodity code is used to form the name of the dimension table.
Commodity codes are read verbatim when they are used to create table names. No
conversion of dots (.) or hyphens (-), as described above, takes place. Also note that a dot (.) is
not a valid character to include in a table name. For this reason, they should not be included as
part of commodity codes for valves.
Comments
You can include any number of comments in a table, using the conventions described below:
For single-line comments:
! XXXXXXXXXXXXXXXXXXXXXXXXXX , or
< XXXXXXXXXXXXXXXXXXXXXXXXXX >
For multi-line comments:
< XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >
where XXXX... represents the comment text.
Revision Markers
Table entries preceded by a karat (>) have been revised since their original release. For
example, the section of the table shown below has been revised three times since it was first
delivered.
Component Tables
The following conventions apply to the definition of columns in all the tables except tables for
specialty items.
The following line is required to define the number of input and output columns:
No_Inputs x No_Outputs x
The number of input columns must not exceed 2. The number of output columns must not
exceed 9; it can be 0.
The following statements are used in some tables to indicate that values will be interpolated.
Input_Interpolation 1, Next_One
Input_Interpolation 2, Next_One
A definition must be made using the following format regarding the units of measure used in
each column of a table:
Units= NPD_IN, SF, LB, INT, DEC, IN, RAT, IN, IN, IN
Units
Units are defined for each column of a table as follows:
Angle, degrees DEG
Angle between runs, degrees DEC
Area FT2
IN2
YD2
MI2
SCM
SKM
Density LBF3
LB_UKGAL
LB_USGAL
KIPFT3
USTONFT3
KG_L
KG_DM3
KGM3
Length, inches IN
Length, millimeter MM
Length, inches decimal IN_DEC
Length, mm decimal MM_DEC
Mass GRAIN
USTON
UKTON
MG
G
Rating RAT
CLxxx and xxx# are expressed as xxx
Surface area/unit,
square feet per foot SFF
square meter per meter SM_M
square millimeter per meter SMM_M
Weight, pounds LB
Weight, kilogram KG
If a value in a table is not known, a hyphen (-) must be used in the corresponding field. The
system interprets this entry as a blank value and displays a blank in reports, drawings, and
other data outputs.
Real numbers without decimals can be expressed with or without a decimal point. For
example, a nominal diameter of twenty inches can be expressed as 20, 20. , or 20.0. For
consistency, all delivered tables use the value 20
All alphanumeric values in a table must be enclosed in single quotes (' '). For example,
'ZZZZZ'.
For tables with only one input column, the generic value ET_AL can be used in the input
column. The system translates this entry to indicate that values in the immediately
preceding line apply to any input value equal to or greater than the value in the current line.
NPD Values
The following table is used to correlate English nominal pipe diameters with their corresponding
metric values.
Nominal Pipe Diameter Nominal Pipe Diameter
inches mm inches mm
0.125 6 14.00 350
0.250 8 16.00 400
0.375 10 18.00 450
0.500 15 20.00 500
0.750 20 22.00 550
1.000 25 24.00 600
1.250 32 26.00 650
1.500 40 28.00 700
2.000 50 30.00 750
2.500 65 32.00 800
3.000 80 34.00 850
3.500 90 36.00 900
4.000 100 38.00 950
5.000 125 40.00 1000
6.000 150 42.00 1050
8.000 200 44.00 1100
10.00 250 46.00 1150
12.00 300 48.00 1200
Rating
The following conventions apply to the rating attribute with respect to the naming of data tables:
Ratings can be expressed in the PJS in any of the following formats: CLxxxx, xxxx#, or
OTxxxx. However, table entries and file names representing the rating exclude the CL, #, or
OT characters. This enables the same table to be used regardless of how the rating is
defined. In the delivered PJS, these rating formats are used in accordance with the following
criteria:
CLxxxx refers to an ANSI or API pressure rating
xxxx# refers to a pressure rating defined by an organization other than ANSI or API.
OTxxxx refers to a rating that meets the applicable ANSI or API rating geometrically but not
from a pressure carrying standpoint. An example is a valve supplied with flanged ends
meeting the bolting pattern of ANSI CL150 pressure rating but with pressure carrying
characteristics different from those of that ANSI rating.
Female ends for plastic pipe are usually defined in terms of schedule/thickness and not in
terms of rating. To make female ends for plastic pipe follow the rules for other female ends,
the applicable schedule/thickness is used as the value for rating. If such rating values
contain alphanumeric characters, the system strips all the alpha characters from the rating
value and uses only the numeric values in accessing the applicable tables.
If the rating in the PJS is expressed in alphabetic characters only, the system uses the
characters to access a data table. The names of the data tables include all the alphabetic
characters included in the PJS.
GRAVHD can be used to identify the rating for components rated to sustain a nominal fluid
head. This value can be used in the PJS and in the data tables.
OTHER can be used to identify a nonstandard rating value.
NONE can be used to identify the rating for components whose ends would normally require
the rating value as part of the table name, but for which a rating does not apply. This value
can be used in the PJS and in the data tables.
Schedule/Thickness
Schedule or thickness values are shown for all applicable components. In order of preference,
schedule and thickness are expressed in terms of:
Generic schedules, such as S-STD, S-XS, and S-XXS. If the schedule name exceeds the
provided field length (for example, S-SDR13.5), it is defined in terms of its wall thickness.
Specific schedules, such as S-40, S-60, and S-80.
NREQD: This value is used in cases where all of the following conditions apply:
The thickness value is not required to purchase the component.
Empty weights are not significantly affected by actual thickness values.
Either stress analysis is not applicable, or the component is considered to be infinitely
rigid in stress analysis calculations.
Specific wall thicknesses: To insure compatibility between the data tables, the PJS, and wall
thickness calculations, thickness is expressed as defined below. Trailing zeroes are not
included. Decimal points are not included for numbers without decimals.
.xxxx if the thickness is less than 1 inch
x if the thickness is an even inch
x.xxx if the thickness is 1 inch or larger
*Cyyy: The need to perform a thickness calculation is triggered by an entry with the format
*Cyyy in the Schedule/Thickness attribute of the Commodity Item entity. The letters that
make up this code have the following meaning:
The character C ensures that the schedule/thickness for the applicable end of the
component is determined by calculations using the thickness equation defined for the
piping materials class in the Default Wall Thickness Equation attribute of the Piping
Materials Class entity.
The characters yyy define the casting, joint or structural grade quality factor (E) times
100. This factor is one of the parameters used in the thickness calculation. If you are
defining a calculation for a seamless fitting (E=1) but want to match the thickness for
the mating welded pipe (E=0.85), the quality factor for the pipe should be used.
MATCH: The need to match the thickness of a component to that of the pipe of the same
diameter and of option 1 is triggered by an entry with the format MATCH in the
Schedule/Thickness attribute of the Commodity Item entity.
To minimize duplication when the same thickness can be expressed for metallic materials in
terms of either a generic or a specific schedule, the following convention is used. For a given
nominal diameter, only the schedules shown in the line for that diameter are used in the PJS and
in the data tables.
Weight Tables
Weight tables are required for the following thicknesses:
For components made from pipe material:
If the thickness involved is covered by a schedule, tables are required for all
commercially available schedules to the full range of their nominal diameter.
If the thickness involved is not covered by a schedule, tables are required in 1/16 inch
increments from 0.25 to 1.25 inches (inclusive), and from 22 inches to the full range of
their nominal diameter.
For components made from plate material, tables are required in 1/16 inch increments from
0.25 to 1.25 inches and in 1 inch increments from 12 to 144 inches.
Abbreviations
The following abbreviations are used to describe the table name formats in this document.
(G) Green
(R) Red
BrchTbl Branch Table
Cmdty Code Commodity Code
GCP Green Connect Point
GS Geometric Industry Standard (from
CL575)
MC Model Code
Op Operator/actuator type (from CL550)
Rat Pressure Rating
RCP Red Connect Point
Sc/Th Schedule/Thickness
Term End Preparation (from CL330)
TNF Table Name Format
TS Table Suffix (from CL576 and CL577)
Type Termination type (BLT, FEM, or MAL)
WC Weight Code (from CL578)
Refer to Variables for Generic Tables (on page 233) and Variables for Specific Tables (on page
249) for a description of the variables used in table definitions. Generally, values appearing in
all uppercase characters (such as BLT or STUD) indicate a hard-coded value.
Table Requirements
This section indicates which tables are required to place a particular type of component (such as
a valve or fitting). The table groups listed in this section are used to store data required for
interactive processing of piping and instrument components. The applicability of the various
table groups is defined as a function of the termination types of the components as defined in the
Piping Job Specification (PJS).
Refer to the PDS Piping Component Data Reference Guide for a detailed description of the
requirements for specific commodity items, instruments, and miscellaneous piping and
instrument items.
Typically, the tables in the table combinations are used to store:
The surface area and weight of water for the component.
The dimensional parameters for the component.
The empty weight of the component and/or data about valve operators.
Tables Required for Piping Components (on page 229)
Tables Required for Instrument Components (on page 232)
Valves (6Q1C)
Termination Types Applicable Tables
Bolted(G) P15A MC_GS_Term(G)_Rat(G)_A
Male(G) P15B MC_GS_Term(G)_Rat(G)_B
Female(G) P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Bolted(G)-Male(R) P25A MC_GS_Term(G)_Rat(G)_Term(R)_A
Female(G)-Male(R) P25B MC_GS_Term(G)_Rat(G)_Term(R)_B
P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Bolted(G)-Bolted(R) P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
Bolted(G)-Female(R) P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B
Female(G)-Female(R) P59 Cmdty Code (if operator code <=24)
Female(G)-Bolted(R) P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Male(G)-Male(R) P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B
P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Male(G)-Female(R) P27A MC_GS_Term(G)_Term(R)_Rat(R)_A
Male(G)-Bolted(R) P27B MC_GS_Term(G)_Term(R)_Rat(R)_B
P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Operators P31A MC_Term(G)_Rat(G)_Op_A (if operator code
<=24)
P31B MC_Term(G)_Rat(G)_Op_B (if operator code
<=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
P60B Cmdty Code_WOPD_B (if operator code >24 &
<=40)
Generic Tables
This section describes the neutral file formats used to define generic piping and instrument data.
The following tables are required to store generic data which applies to both piping and
instrument components:
Male The value of this variable is "0" for all male ends.
Example
Table_Data_Definition 'BLT_20_150_5'
! Description= CL150 raised face flange dimensions
! Source= MSS-SP-42 1/4 & 3/8", ANSI-B16.5-1981 1/2" - 24" & API 605
above 24"
! TNF=G10 By=GJH Ckd By=RJW Rev=1 Date=15-Oct-
1987
No_Inputs 1 No_Outputs 4
Units= NPD_IN, IN, IN, IN, IN
! Diam P R S BCD
0.25 2.5 0.3438 0 1.6875
0.375 2.5 0.3438 0 1.6875
0.5 3.5 0.4375 0 2.375
0.75 3.875 0.5 0 2.75
1 4.25 0.5625 0 3.125
1.25 4.625 0.625 0 3.5
1.5 5 0.6875 0 3.875
2 6 0.75 0 4.75
2.5 7 0.875 0 5.5
3 7.5 0.9375 0 6
3.5 8.5 0.9375 0 7
4 9 0.9375 0 7.5
5 10 0.9375 0 8.5
6 11 1 0 9.5
8 13.5 1.125 0 11.75
10 16 1.1875 0 14.25
12 19 1.25 0 17
14 21 1.375 0 18.75
16 23.5 1.4375 0 21.25
18 25 1.5625 0 22.75
20 27.5 1.6875 0 25
24 32 1.875 0 29.5
26 30.9375 1.625 0 29.3125
28 32.9375 1.75 0 31.3125
30 34.9375 1.75 0 33.3125
32 37.0625 1.8125 0 35.4375
34 39.5625 1.9375 0 37.6875
36 41.625 2.0625 0 39.75
38 44.25 2.125 0 42.125
40 46.25 2.1875 0 44.125
42 48.25 2.3125 0 46.125
44 50.25 2.375 0 48.125
46 52.8125 2.4375 0 50.5625
48 54.8125 2.5625 0 52.5625
50 56.8125 2.6875 0 54.5625
52 58.8125 2.75 0 56.5625
54 61 2.8125 0 58.75
56 63 2.875 0 60.75
58 65.9375 2.9375 0 63.4375
60 67.9375 3 0 65.4375
END
Table_Data_Definition
'STUD_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G12 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
Example
Table_Data_Definition
'STUD_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G12 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END
Table_Data_Definition
'STUD_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source= PIPING RDB DATA MANUAL
! Parameter W_2 equals 50% of applicable stud diameter plus W_0.
! TNF=G12T By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END
Example
Table_Data_Definition 'STUD_20_150_5'
! Description= CL150 bolting
! Source= PIPING RDB DATA MANUAL
! Parameter W_2 equals 50% of applicable stud diameter plus W_0.
! TNF=G12T By=GJH Ckd By=NP Rev=0 Date=04-Oct-
1989
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
0.5 4 0.5 0.625 1 - - - -
0.75 4 0.5 0.6875 0.875 - - - -
1 4 0.5 0.625 1 - - - -
1.25 4 0.5 0.6875 0.875 - - - -
1.5 4 0.5 0.625 1 - - - -
2 4 0.625 0.8125 1.125 - - - -
2.5 4 0.625 0.8125 1.125 - - - -
3 4 0.625 0.75 1 - - - -
3.5 8 0.625 0.75 1 - - - -
4 8 0.625 0.75 1 - - - -
5 8 0.75 0.875 1.25 1.25 - - -
6 8 0.75 0.9375 1.125 1.3125 - - -
8 8 0.75 0.9375 1.125 1.3125 - - -
10 12 0.875 1 1.5 1.4375 - - -
12 12 0.875 1.0625 1.375 1.5 - - -
14 12 1 1.1875 1.625 1.6875 - - -
16 16 1 1.125 1.5 1.625 - - -
18 16 1.125 1.25 1.75 1.8125 - - -
20 20 1.125 1.375 2 1.9375 - - -
24 20 1.25 1.4375 2.125 2.0625 - - -
26 36 0.75 1.0625 1.375 1.4375 - - -
28 40 0.75 1.0625 1.375 1.4375 - - -
30 44 0.75 1.0625 1.375 1.4375 - - -
32 48 0.75 1 1.5 1.375 - - -
34 40 0.875 1.125 1.75 1.5625 - - -
36 44 0.875 1.125 1.75 1.5625 - - -
38 40 1 1.3125 1.875 1.8125 - - -
40 44 1 1.25 2 1.75 - - -
42 48 1 1.25 1.75 1.75 - - -
44 52 1 1.3125 1.875 1.8125 - - -
46 40 1.125 1.5 2 2.0625 - - -
48 44 1.125 1.375 2 1.9375 - - -
50 48 1.125 1.375 2 1.9375 - - -
52 52 1.125 1.4375 2.125 2 - - -
54 56 1.125 1.375 2 1.9375 - - -
56 60 1.125 1.4375 2.125 2 - - -
58 48 1.25 1.5 2.25 2.125 - - -
60 52 1.25 1.5625 2.125 2.1875 - - -
END
Table_Data_Definition
'MAL_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G20 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 3
Units= NPD_IN, SFF, IN, IN
! Unt Sur
! Diam Area P P/2
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
END
Example
Table_Data_Definition 'MAL_300_5'
! Description= Pipe outside diameters
! Source= ANSI-B-36.10M, 36.19M, API-5L, 5LE, 5LP, 5LS & 5LU
! TNF=G20 By=GJH Ckd By=RJW Rev=0 Date=10-Sep-
1987
No_Inputs 1 No_Outputs 3
Units= NPD_IN, SFF, IN, IN
! Unt Sur
! Diam Area P P/2
0.125 0.106 0.405 0.2025
0.25 0.141 0.54 0.27
0.375 0.177 0.675 0.3375
0.5 0.22 0.84 0.42
0.75 0.275 1.05 0.525
1 0.344 1.315 0.6575
1.25 0.434 1.66 0.83
1.5 0.497 1.9 0.95
2 0.622 2.375 1.1875
2.5 0.753 2.875 1.4375
Table_Data_Definition
'FEM_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G30 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 2
Example
Table_Data_Definition 'FEM_420_150_5'
! Description= CL150 socketwelded flange hub O.D. and socketwelded
valve O.D.
! Source= ANSI-B16.11 CL3000 for .125 to .375 dia's, ANSI-B16.5 above
.375 dia.
! TNF=G30 By=GJH Ckd By=JPF Rev=0 Date=29-May-
1986
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! Diam P Q
0.125 0.486 0.3125
0.25 0.6353 0.3125
0.375 0.7755 0.3125
0.5 0.9443 0.3125
0.75 1.185 0.375
1 1.5018 0.4375
1.25 1.8558 0.5
1.5 2.0988 0.5625
2 2.5813 0.625
2.5 3.0813 0.6875
3 3.725 0.75
END
Table_Data_Definition
'MALWT_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
Example
Table_Data_Definition 'MALWT_300_S$40_5_52'
! Description= Schedule 40 wall thickness
! Source= ANSI-B36.10M-1985
! TNF=G50 By=GJH Ckd By=RJW Rev=0 Date=10-Sep-
1987
No_Inputs 1 No_Outputs 3
Units= NPD_IN, LBF, LBF, IN
! GCP Unit Wt Unit Wt
! Diam Empty Water X
12 53.52 48.5 0.406
14 63.44 58.63 0.438
18 104.67 96.92 0.562
20 123.11 120.45 0.594
24 171.29 174.22 0.688
32 230.08 319.2 0.688
34 244.77 362.25 0.688
36 282.35 405.09 0.75
END
P62 MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_Sc/Th(R)_W
C
P63 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Sc/Th(R)_WC
P64 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat(R)_WC
P65 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_WC
Use tables P80 and P81 for data about piping specialty components defined in the Material
Reference Database. See Piping Component Tables for Specialty Components (on page 266) for
more information.
P80 Specialty Body Data
P81 Operator/Actuator
Data
See Also
Variables for Specific Tables (on page 249)
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ Par 6=ZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, SF, LB, IN, IN, IN, IN, IN, IN
! GCP Surf Water Dimensional Parameters
! Diam Area Weight Par 1 Par 2 Par 3 Par 4 Par 5
Par 6
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END
Example
Table_Data_Definition 'GAT_40_20_150_A'
! Description= CL150 gate valve raised face flanged ends
! Source= ANSI-B16.10-1986
! TNF=P15A By=GJH Ckd By=RJW Rev=1 Date=29-Oct-
1987
! SN=V1 Par 1=A
No_Inputs 1 No_Outputs 3
Units= NPD_IN, SF, LB, IN
! GCP Surf Water Dimensional Parameters
! Diam Area Weight Par 1
0.25 - - 2
0.375 - - 2
0.5 - - 2.125
0.75 - - 2.3125
1 - - 2.5
1.25 - - 2.75
1.5 - - 3.25
2 - - 3.5
2.5 - - 3.75
3 - - 4
4 - - 4.5
5 - - 5
6 - - 5.25
8 - - 5.75
10 - - 6.5
12 - - 7
14 - - 7.5
16 - - 8
18 - - 8.5
20 - - 9
24 - - 10
26 - - 11
28 - - 12
30 - - 12
36 - - 14
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ Par 6=ZZ Par 7=ZZ Par 8=ZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2 Par 3 Par 4 Par 5 Par 6 Par 7
Par 8
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ
No_Inputs 2 No_Outputs 7
Units= NPD_IN, NPD_IN, SF, LB, IN, IN, IN, IN, IN
! Nom Diam Surf Weight Dimensional Parameters
Example
Table_Data_Definition 'E90R_39_300_300_A'
! Description= 90 deg long radius reducing elbow beveled ends
! Source= ANSI-B16.9-1978
! TNF=P21A By=GJH Ckd By=JPF Rev=0 Date=15-May-
1986
! SN=F84 Par 1=E Par 2=K Par 3=F Par 4=L
No_Inputs 2 No_Outputs 6
Units= NPD_IN, NPD_IN, SF, LB, IN, IN, IN, IN
! Nom Diam Surf Weight Dimensional Parameters
! GCP RCP Area Water Par 1 Par 2 Par 3 Par 4
2 1 - - 3 0.53 3 0.53
2 1.25 - - 3 0.3575 3 0.3575
2 1.5 - - 3 0.2375 3 0.2375
2.5 1.25 - - 3.75 0.6075 3.75 0.6075
2.5 1.5 - - 3.75 0.4875 3.75 0.4875
2.5 2 - - 3.75 0.25 3.75 0.25
3 1.5 - - 4.5 0.8 4.5 0.8
3 2 - - 4.5 0.5625 4.5 0.5625
3 2.5 - - 4.5 0.3125 4.5 0.3125
3.5 2 - - 5.25 0.8125 5.25 0.8125
3.5 2.5 - - 5.25 0.5625 5.25 0.5625
3.5 3 - - 5.25 0.25 5.25 0.25
4 2 - - 6 1.0625 6 1.0625
4 2.5 - - 6 0.8125 6 0.8125
4 3 - - 6 0.5 6 0.5
4 3.5 - - 6 0.25 6 0.25
5 2.5 - - 7.5 1.3438 7.5 1.3438
5 3 - - 7.5 1.0313 7.5 1.0313
5 3.5 - - 7.5 0.7813 7.5 0.7813
5 4 - - 7.5 0.5313 7.5 0.5313
6 3 - - 9 1.5625 9 1.5625
6 3.5 - - 9 1.3125 9 1.3125
6 4 - - 9 1.0625 9 1.0625
6 5 - - 9 0.5312 9 0.5312
8 4 - - 12 2.0625 12 2.0625
8 5 - - 12 1.5312 12 1.5312
8 6 - - 12 1 12 1
10 5 - - 15 2.5937 15 2.5937
10 6 - - 15 2.0625 15 2.0625
10 8 - - 15 1.0625 15 1.0625
12 6 - - 18 3.0625 18 3.0625
12 8 - - 18 2.0625 18 2.0625
12 10 - - 18 1 18 1
14 8 - - 21 2.6875 21 2.6875
14 10 - - 21 1.625 21 1.625
14 12 - - 21 0.625 21 0.625
16 10 - - 24 2.625 24 2.625
16 12 - - 24 1.625 24 1.625
16 14 - - 24 1 24 1
18 10 - - 27 3.625 27 3.625
18 12 - - 27 2.625 27 2.625
18 14 - - 27 2 27 2
18 16 - - 27 1 27 1
20 10 - - 30 4.625 30 4.625
20 12 - - 30 3.625 30 3.625
20 14 - - 30 3 30 3
20 16 - - 30 2 30 2
20 18 - - 30 1 30 1
24 12 - - 36 5.625 36 5.625
24 14 - - 36 5 36 5
24 16 - - 36 4 36 4
24 18 - - 36 3 36 3
24 20 - - 36 2 36 2
24 22 - - 36 1 36 1
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
Preparation Type
2-199 BLT
300-399 MAL
400-599 FEM
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P31Y By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ Par 6=ZZ Par 7=ZZ Par 8=ZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2 Par 3 Par 4 Par 5 Par 6 Par 7
Par 8
Example
Table_Data_Definition 'GAT_BLT_150_3_A'
! Description=Stem and handwheel operator
! Source=PDS Document 2630-33-OP
! TNF=P31A By=GJH Ckd By=RJW Rev=0 Date=26-Feb-
1987
! SN=OP3 Par 1=Y1 Par 2=Y2
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2
0.25 8.375 3.75
0.375 8.375 3.75
0.5 8.375 3.75
0.75 9.25 4.125
1 11.875 6
1.25 12.5 6
1.5 17.75 10
2 17.813 10
2.5 20.125 10
3 22.375 12
4 28.188 13.75
5 31.75 13.75
6 35.375 15.5
8 45 19.5
10 52.5 19.5
12 61.125 20
14 70.5 24
16 79.75 28
18 89 30
20 97.25 30
22 105 30
24 112.75 36
26 116 36
28 123.25 36
30 140 36
32 145 36
34 150 36
36 155.5 36
END
Preparation Type
2-199 BLT
300-399 MAL
400-599 FEM
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P31B By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ Par 6=ZZ Par 7=ZZ Par 8=ZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2 Par 3 Par 4 Par 5 Par 6 Par 7
Par 8
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 1
Units= NPD_IN, LB
! GCP Weight
! Diam Empty
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
END
Examples
Table_Data_Definition 'VAABAHCCAA'
! Description= CL150 gate valve raised face flanged ends weight
! Source= CRANE catalog for figure 47XU
! TNF=P59 By=GJH Ckd By=RJW Rev=0 Date=29-May-
1987
No_Inputs 1 No_Outputs 1
Units= NPD_IN, LB
! GCP Weight
! Diam Empty
2 46
2.5 70
3 76
4 110
5 155
6 175
8 310
10 455
12 650
14 860
16 1120
18 1400
20 2125
24 3120
30 4250
END
Table_Data_Definition 'E90LR_39_300_S$STD_52'
! Description= 90 deg long radius elbow beveled ends
! Source= Taylor Forge Cat. 722
! TNF=P51 By=GJH Ckd By=JPF Rev=0 Date=24-Apr-
1986
No_Inputs 1 No_Outputs 1
Units= NPD_IN, LB
! GCP Weight
! Diam Empty
0.5 0.17
0.75 0.17
1 0.34
1.25 0.58
1.5 0.84
2 1.5
2.5 3
3 4.7
3.5 6.6
4 8.9
5 15
6 24
8 47
10 83
12 123
14 158
16 207
18 263
20 323
22 392
24 468
26 550
28 625
30 733
32 825
34 -
36 1061
38 -
40 -
42 1442
44 -
46 -
48 -
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_WOPD_A'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P60A By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, LB, LB, IN, IN, IN, DEG, IN, IN
! GCP Weight Weight Oper Dimensional Parameters
! Diam Vlv Emp Oper Code Y1 Y2 Y3 Y4
Y5
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END
Example
Table_Data_Definition 'VAABAHCCGR_WOPD_A'
! Description=Crane 47 gate valve with gear operator 3X-N for 14",
! 4X-N for 16, 18 & 20", & 6X-N for 24" valve.
! Par "Y4" includes a 8" mounting adaptor.
! Source=CRANE catalog for Converto-Gear valve operators
! TNF=P60A By=GJH Ckd By=DCG Rev=1 Date=01-Dec-
1987
! SN=VARIES
No_Inputs 1 No_Outputs 8
Units= NPD_IN, LB, LB, INT, IN, IN, DEG, IN, IN
! GCP Weight Weight Oper Dimensional Parameters
! Diam Vlv Emp Oper Code Y1 Y2 Y3 Y4
Y5
14 860 75 331 57.625 2.375 0 61.1875
8.75
16 1120 109 331 62 3.625 0 65.9688
10.625
18 1400 126 331 69.8125 4.25 0 73.7188
10.625
20 2125 150 331 80.375 5.5 0 84.2188
10.625
24 3120 248 331 92.75 4.625 0 99.375
15.25
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_WOPD_B'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P60B By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Y6 Y7 Y8 Y9 Y10 Y11 Y12
Y13
Example
Table_Data_Definition 'VAABAHCCGR_WOPD_B'
! Description=Crane 47 gate valve with gear operator 3X-N for 14",
! 4X-N for 16, 18 & 20", & 6X-N for 24" valve.
! Source=CRANE catalog for Converto-Gear valve operators
! TNF=P60B By=GJH Ckd By=DCG Rev=0 Date=22-May-
1987
! SN=VARIES
No_Inputs 1 No_Outputs 7
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Y6 Y7 Y8 Y9 Y10 Y11 Y12
14 3.375 6.6875 12.375 20 0 - -
16 3.625 7.2188 15.25 20 0 - -
18 3.625 7.2188 15.25 24 0 - -
20 3.625 7.2188 15.25 30 0 - -
24 5.375 11.375 18.5 30 0 - -
END
Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 2 No_Outputs 1
Units= NPD_IN, NPD_IN, LB
! Nom Diam Weight
! GCP RCP Empty
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
END
Example
Table_Data_Definition 'REDC_39_300_S$60_300_S$40_52'
! Description= Concentric reducer beveled ends weight.
! Source= TAYLOR FORGE Cat. 722, weights for schedule 60 fitting
! TNF=P63 By=GJH Ckd By=JPF Rev=0 Date=15-Aug-
1986
No_Inputs 2 No_Outputs 1
Units= NPD_IN, NPD_IN, LB
! Nom Diam Weight
! GCP RCP Empty
14 12 92
16 14 125
16 12 125
18 14 173
18 12 173
20 18 278
20 14 278
20 12 278
22 20 -
22 18 -
22 14 -
24 20 397
24 18 397
END
Inbody_Specific_PSC_MC_A
Inbody_Specific_PSC_MC_B
The output fields are the dimensional parameters P7 through P15, as prescribed in the PDS
Piping Component Data Reference Guide.
Inbody_Specific_PSC_MC_C
The output fields are the dimensional parameters P16 through P24, as prescribed in the PDS
Piping Component Data Reference Guide.
Inoper_Specific_PSC_MC_A
The first two output fields for this table are the operator weight and the operator type. The
operator type must be loaded in the modifier attribute of the Instrument Component
Specification Data of the Material Reference Database. The operator type is the number (such as
411) representing the operator and not the symbol name (such as OP_411).
The remaining output fields are dimensional parameters Y2 through Y8, as prescribed in the
PDS Piping Component Data Reference Guide. For some operators, the first three dimensional
parameters, Y2 through Y4, define the center of gravity for the operator in terms of offsets from
the instrument center.
Inoper_Specific_PSC_MC_B
The output fields are the dimensional parameters Y9 through Y17, as prescribed in the PDS
Piping Component Data Reference Guide.
Inoper_Specific_PSC_MC_C
The output fields are the dimensional parameters Y18 through Y24, as prescribed in the PDS
Piping Component Data Reference Guide.
Commodity Code
The system uses the commodity code as an index to access the descriptions in the material
description libraries. You can use the commodity code defined in the Piping Commodity
Specification Data table (Table 202 attribute 18) or a user-defined commodity code defined in
the Size-Dependent Material Data table (Table 211 attribute 7).
The source of the commodity code and other processing options for reporting are defined for a
model with the Material Takeoff Options form of the Project Data Manager.
The commodity code represents that set of parameters that completely describe a commodity
item, exclusive of nominal piping diameter and thickness. The character length for the
commodity code is determined from the character length of the commodity code in the Size
Dependent Data table of the database, or from the character length of the commodity code in the
Piping Commodity Data table of the database, depending on which is being used to access the
material descriptions.
The delivered commodity codes use a 10 character code to fully identify the item. The first
letter of the commodity code identifies the basic type of component, such as a valve or flange.
The remaining characters provide a detailed description of the component. The first character
designations are:
B Flanged and Misc. Fittings Q Socket End Fittings
D Fire and Safety Components R Tubing Fittings
E Steam Specialties S Socketwelded Fittings
F Flanges T Threaded Fittings
G Flanged Specialties U Underground Fittings
H Strainers V Valves
M Misc. Wetted Components W Welded Fittings
N Misc. Non-Wetted Components X Gaskets
O Tubing and Hose Y Bolting
P Pipe
Examples
1 2 3 4 5 6 7 8 9 0
P A D A A B C A A E
P - Pipe
AD - Pipe, Plain Ends
AA - Seamless
BC - X-Strong (s-xs)
AAE - ASTM A106 Gr. B
V A A B A H C C A A
V - Valve
A - Gate Valve
A - CL150
B - Raised Face Flanged Ends
A - Carbon Steel
H - Trim 8
CC - Crane 47
AA - Blank
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 Descriptions Library.
Example
1 2 3 4 5 6 7 8 9 0
E $ 5 0 4 2 1 0 6 4
E - English
$50 - NPD = 0.5 inches
421 - SWE - socketwelded end
064 - unique number
Example
Tri-Clover part number:
BS14AM-4"-316L-PL
BS14AM = Part Description
4" = Size
316L = Material Grade
PL = Surface Finish Description
Tri-Clover commodity code:
BS14AM316LPL
In the Tri-Clover commodity code, the dashes ("-") and size are removed so that the commodity
code is less than 18 characters. The commodity code description lists the full part number.
Neutral Files
You can use neutral files to insert data into the Short Material Description Library or replace
existing data. The neutral files for the delivered material descriptions are contained in the text
library. You can use the neutral files in the following files:
The Short Material Description Library is created from two neutral files. (These can be created
with a text editor such as Notepad.)
A neutral file containing the short material descriptions for commodity items. The neutral
file contains unique Commodity Codes followed by at least one space and a description
enclosed in single quotes. It also contains the chain wheel descriptions and implied material
descriptions associated with a commodity item.
The commodity code identifies the Piping Commodity Library code or customer's
commodity code. The character length for this 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 library code in the Piping Commodity Data table of the
database, depending on which is being used to access the material descriptions.
For chain wheels, the commodity code has the format CHAIN_xx, where xx represents the
chain wheel number (for example, CHAIN_12). The chain wheel number is defined in the
component and instrument analysis entities of the TDB.
A neutral file containing the material description addenda for taps. This file contains the tap
code and the text for the tap description. The tap code identifies the unique identification of
a tap.
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:
Data Retrieval
The system uses the commodity code to retrieve the short material descriptions from the
Material Description Library.
Commodity Material Descriptions
! DEFINE SHORT DESCRIPTIONS
! Date/Time: Thu Apr 23 14:16:58 1992
! Processed Library c:
ewpipe\refdata\us_shbom.l
!Cmdty Code
====================================Description========================
================
CHAIN_1003 'Chainwheel operator each with [422] of total chain
length for [426] NPD valve with commodity code [400]'
CHAIN_1005 'Chainwheel operator each with [422] of total chain
length for [426] NPD valve with commodity code [400]'
CHAIN_1251 'Chainwheel operator each with [424] of total chain
length for valve with tag no [402]'
DAABAXAABE 'Monitor, CL150 FFFE, ^station type, 4" CL150 in-let
by 2.5" NHT stainless steel outlet
w/stainless steel stem lock knobs with 0.75"
coupling in base, w/shapertip nozzle, Stang BB0309-21'
DAABAXAABF 'Monitor, CL150 FFFE, ^station type 4" CL150 in-let
by 2.5" NHT stainless steel
outlet w/stainless steel stem lock knobs with 0.75"
coupling in base, w/fog nozzle,
Stang BB0309-21'
DACBAXABBC 'Monitor, CL150 FFFE, ^elevated type, free standing,
4" CL150 in-let by 2.5" NHT
stainless steel outlet, [427], w/drain coupling,
w/shapertip nozzle and two reaction supports,
Stang BB2999-'
DACBAXABBD 'Monitor, CL300 FFFE, ^elevated type, supported, 6"
CL300 in-let by 2.5" NHT stainless
steel outlet, [427], w/drain coupling, w/shapertip
nozzle, Stang BB3561'
DBAAAXBAAB 'Fire hydrant, CL125 FFFE, ^5" size,
counterclockwise open, 4.5" steamer nozzle,
two 2.5" hose nozzles equipped w/caps and chains,
[428], American Darling B-50-B'
DCBGDXEADA 'Hose rack, 300#, FTE, ^w/valve, wall mount, rt hand
w/100 ft hose & fog nozzle Powhatan 30-333'
DDAXCJDAAA 'Spray sprinkler, MTE, filled cone w/rupture disc,
304, Grinnell, Mulsifyre Projector S-1'
Neutral Files
The Long Material Description Library is created through a neutral file which contains the long
material descriptions for commodity items. The neutral file contains unique commodity codes
followed by at least one space and a description enclosed in single quotes.
You can use neutral files to insert data into the Long Material Description Library or replace
existing data.
The commodity code identifies the Piping Commodity Library code or customer's commodity
code. The character length for this code is determined from the character length of the
commodity code in the Size Dependent Data database table, or from the character length of the
commodity library code in the Piping Commodity Data table of the PJS database, depending on
which is being used to access the material descriptions.
The long description can be up to 500 characters. Because this description may include label
numbers which are translated to text strings, the reported (compiled) length of the description
can be up to 600 characters.
Prior to the 5.0 release, there was a restriction that no more than 255 characters could be
specified per line in the neutral file. This required that long descriptions be continued on
multiple lines. With the 5.0 release, a neutral file for long material descriptions may contain up
to 600 characters per line.
Data Retrieval
The system uses the Piping Commodity Library code or commodity code to access the text for
the long description in the Long Material Description Library.
Listing for Long Material Descriptions
! DEFINE LONG DESCRIPTIONS
! Date/Time: Fri Apr 24 10:48:13 1992
! Processed Library c:
ewpipe\refdata\us_lgbom.l
!Cmdty Code
====================================Description========================
================
DAABAXAABE 'Monitor, 750 GPM at 100 psig, CL150 flat face
flange end, 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
or approved equal'
DAABAXAABF 'Monitor, 750 GPM at 100 psig, CL150 flat face
flange end, station type 4" CL150 in-let by 2.5" NHT stainless
steel outlet w/stainless steel stem lock knobs with
0.75" coupling in base, w/fog nozzle, Stang BB0309-21
or approved equal'
DACBAXABBC 'Monitor, 750 GPM at 100 psig, CL150 flat face
flange end, elevated type, free standing, 4" CL150 in-let by
2.5" NHT stainless steel outlet, w/drain coupling,
w/shapertip nozzle and two reaction supports,
Stang BB2999-[427] high or approved equal'
DACBAXABBD 'Monitor, 750 GPM at 100 psig, CL300 flat face
flange end, elevated type, supported, 6" CL300 in-let by 2.5"
NHT stainless steel outlet, w/drain coupling,
w/shapertip nozzle, Stang BB3561-[427] high or approved equal'
DBAAAXBAAB 'Fire hydrant, CL125 flat face flange end, 5" size,
regular rating, ductile iron barrel, bronze trim,
bituminous paint below grade, red epoxy paint above
grade, counterclockwise open, 4.5" steamer nozzle, two 2.5"
hose nozzles equipped w/caps and chains, [428],
American Darling B-50-B or approved equal'
DCBGDXEADA 'Hose rack w/bronze angle valve, 300#, female
threaded end, wall mount, right hand w/100 ft synthetic single
jacketed hose, rack nipple & fog nozzle, Powhatan
30-333 or approved equal'
DDAXCJDAAA 'Spray sprinkler, male threaded end, filled cone
w/rupture disc, .313" orifice, Type 304 stainless steel,
!Cmdty Code
====================================Description========================
======
SUPP1 'PIPE SUPPORT NUMBER 1.'
SUPP1 8 'PIPE SUPPORT NUMBER 1.'
SUPP1 @fffffe"ffff98O 'PIPE SUPPORT NUMBER 1.'
SUPP2 'PIPE SUPPORT NUMBER 2.'
SUPP2 8 'PIPE SUPPORT NUMBER 2.'
SUPP2 @fffffe"ffff98O 'PIPE SUPPORT NUMBER 2.'
SUPP3 'PIPE SUPPORT NUMBER 3.'
SUPP3 8 'PIPE SUPPORT NUMBER 3.'
SUPP3 @fffffe"ffff98O 'PIPE SUPPORT NUMBER 3.'
Data Retrieval
The system uses the specialty tag number and specialty type to access the text for the material
descriptions in the Specialty Material Description Library.
Operating Sequence
1. Select Material Description Library Manager from the Reference Data Manager form.
The system displays the Material Description Library Manager form.
Create Library (on page 289) Creates a new (empty) Short Material Description Library,
Long Material Description Library, or Specialty Material Description Library.
Unapprove ==> Approve (see "Unapproved ==> Approved" on page 289) Copies data
from the unapproved library to the approved library.
Load/Revise Interactive (on page 289) Adds the contents of the neutral files to the
information currently in an existing Material Description Library or revises an existing table
in the library.
Load/Revise Batch (on page 290) Adds the contents of the neutral files to the information
currently in an existing Material Description Library or revises an existing table in the
library.
Replace Interactive (on page 291) Deletes all entries in the respective Material
Description Library file and then loads new entries from a neutral file.
Replace Batch (on page 291) Deletes all entries in the respective Material Description
Library file and then loads new entries from a neutral file.
Report (see "Report Option" on page 292) Used to create a report file or a neutral file of
the contents of the material description library.
Create Library
This option is used to create a new Material Description Library. This option is disabled if the
library already exists.
1. Select Create Library from the Material Description Library Manager form.
The system displays the approved and unapproved Library names as defined in the RDB
Management Data.
2. The system prompts Accept to Create or Exit to Avoid Creating New Library
Select Accept to create the specified library files.
Load/Revise Interactive
This option enables you to load entries from a neutral ASCII file into the Material Description
Library. Refer to the library descriptions earlier in this section for a listing of the neutral file
formats used in defining the delivered material data.
This option adds the contents of the neutral files to the information currently in the library or
revises an existing table in the library.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.
Operating Sequence
1. Select the Load/Revise option.
Load/Revise Batch
This option enables you to load entries from a neutral ASCII file into the Material Description
Library via batch processing. Refer to the library descriptions earlier in this section for a listing
of the neutral file formats used in defining the delivered material data.
This option adds the contents of the neutral files to the information currently in the library or
revises an existing table in the library.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.
Operating Sequence
1. Select the Load/Revise option.
2. Select File Type
Select the type of material data to be loaded into the specified library from the display list
and select Accept.
3.
Replace Interactive
This option enables you to load entries from a neutral ASCII file into the Material Description
Library. Refer to the library descriptions earlier in this section for a listing of the neutral file
formats used in defining the delivered material data.
This option deletes all entries in the respective library file and then loads new entries from the
neutral file.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.
Operating Sequence
1. Select the Replace Interactive option from the Material Description Library form.
2. Select File Type
Select the type of material data to be loaded into the specified library from the display list
and select Accept.
Replace Batch
This option enables you to load entries from a neutral file into the Material Description Library
via batch processing. Refer to the library descriptions earlier in this section for a listing of the
neutral file formats used in defining the delivered material data.
This option deletes all entries in the respective library file and then loads new entries from the
neutral file.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.
Operating Sequence
1. Select the Replace Batch option from the Material Description Library form.
2. Select File Type
Select the type of material data to be loaded into the specified library from the display list
and select Accept.
Report Option
The Report option enables you to create neutral files or report files using the information in the
Material Description Library. Refer to the description of the Short Material Description Library
(on page 277), Long Material Description Library (on page 283), and Specialty Material
Description Library (on page 286) for more information on the types of neutral files.
Operating Sequence
1. Select the Report option from one of the library forms.
Table Checker
The Table Checker enables you to verify that all the commodity spec tables, entries, and Eden
modules for a piping materials class exist in the graphic data libraries for the project.
This process accesses the Eden code for each commodity item in the piping material class and
checks that the table names created in the physical dimension modules exist in the project
Physical Data Library. This routine checks for the existence of the tables and checks the contents
of the tables.
For Table Checker to function, there MUST be at least one piping model file created in the
project, and it must have a piping materials class (spec) defined in the Active Segment
Parameters.
The Type 63 settings of the model with the highest alphanumeric name are used as defaults
for the Table Checker reports. If weight tables are set to 'yes' for this model, then Table
Checker will search for and report on found and missing weight tables. If MTO Bolt
Calculation is set to 'almost precise,' Table Checker will search for the 'almost precise' tables
(table naming format = G12). If set to 'precise,' Table Checker will search for 'precise' tables
(table naming format = G12T).
When the spec contains PIPING/TUBE and PIPE/TUBING, Table Checker will report as per
Type 63 data settings.
If Component Placement is set to PIPING for Pipe Commodity Name and TUBE for Tube
Commodity Name, Table Checker uses these commodity names and searches for PDPIPING
and PDTUBE in the Graphic Commodity Library. If there are any other PIPE and TUBING
values found in the spec that do not match with Type 63, Table Checker assumes that this is a
regular commodity item. It uses the model_code and searches for SPmodel_Code in the
Graphic Commodity Library.
If Component Placement is set to PIPE for Pipe Commodity Name and TUBING for Tube
Commodity Name, Table Checker uses these commodity names and searches for PDPIPE and
PDTUBING in the Graphic Commodity Library. If there are any other PIPING and TUBE values
found in the spec that do not match with Type 63, Table Checker assumes that this is a regular
commodity item. It uses the model_code and searches for SPmodel_code in the Graphic
Commodity Library.
In such cases, if the model_code of the item is the same as the commodity_name that matches
with Type 63 data, the Table Checker may report the same value under both Eden Found and
Eden Not Found. In other words, Table Checker reports the commodity_name under Eden
Found and the model_code under Eden Not Found.
Features
The Table Checker provides the following features.
Reports on one piping material class selected from the available entries in the
Specification/Material Database.
Reports on all valid sizes in the size range for each piping commodity using the Nominal
Piping Diameter table for that piping materials class.
Reports dimensional tables used during the placement of each piping commodity in the
piping materials class. This includes the table names, the types of tables, the existence of
those tables (found or not found), and the output values from those tables.
Reports Piping Eden modules used during the placement of each piping commodity in the
piping materials class. This includes the Piping Eden module names and the existence of
those modules (found or not found).
Reports dimensional tables used for all piping commodities in the entire report (the piping
materials class). This includes the table names, the revision dates for those tables, and the
source Dimension Table Library.
Reports bolt tables for each piping commodity with bolted ends.
Reports Piping Eden modules used for all piping commodities in the entire report (the piping
materials class). This includes the Piping Eden module names and the existence of those
modules (found or not found).
Verifies that a material description exists in the Material Description Library for any piping
commodities defined in the Material Reference Database. The commodity code as defined
in the Piping Commodity Specification Data Table (PDtable_202) or the Piping Commodity
Size-Dependent Material Data Table (PDtable_211) is used to verify the material
description.
Verifies that a material description exists in the Material Description Library for any implied
component defined in the Piping Commodity Implied Material Data Table (PDtable_212) of
the Material Reference Database.
Verifies that a material description exists in the Specialty Material Description Library for
any piping specialty or instrument defined in the Material Reference Database.
Provides a detailed error report of any tables or table entries that were found missing during
the processing of the piping materials class.
For tables containing schedule thickness calculations as part of the name, the
calculations are replaced with preferred thickness unless no preferred thickness is found for
that size or PMC thickness table.
If any errors are encountered during execution, the system appends the errors to the end of the
report output. In the case of severe errors, it creates a file named RPT_ERR.LOG.
Commodity items with option codes greater than 5000 (spec implied components) are not
checked.
Format Files
The Table Checker uses report format files to define the report output. It uses the same reporting
indices as any other report from the Piping Job Specification data (the C indices). Refer to
Format Files in the Report Manager Reference Guide for more information on these indices.
The following example report formats for the Table Checker are included in the PD_DATA
sample directory (\win32app\ingr\pddata\sample\format/). Refer to the Report Manager
Reference Guide for more information on report type.
tbl_chk_1.fmt
This report format reports on virtually all data generated by the Table Checker. It is a
combination of the following sample report formats: tbl_chk_2.fmt, tbl_chk_3.fmt, and
tbl_chk_4.fmt.
It reports the piping commodities in the selected piping materials class with the dimension
tables and Piping Eden modules used, including a list of all entries read in the dimension
tables. It also lists all dimension tables and Piping Eden modules required for those piping
commodities, but not available in the Reference Database.
tbl_chk_2.fmt
This report format reports the dimension tables and Piping Eden modules used by each
piping commodity in the applicable piping materials class.
tbl_chk_3.fmt
This report lists all entries read in dimension tables for the applicable piping materials class.
tbl_chk_4.fmt
This report format reports a total list of dimension tables and Piping Eden modules used for
the applicable piping materials class. It also lists all dimension tables and Piping Eden
modules required for those piping commodities, but not available in the Reference Database.
tbl_chk_5.fmt
This report verifies the reference data for any piping specialties defined in the Reference
Database (pdtable_203).
tbl_chk_6.fmt
This report verifies the reference data for any instruments defined in the Reference Database
(pdtable_204).
Table format 5 or 6 must be used when the discrimination file is created with the No
Piping Material Class button selected.
Report Format Displays the Report Format form, which you can use to create, revise,
copy, or delete the record of a format file (not the format file). For more information, see
Report Format Form (on page 300).
Report Discrimination Data Displays the Discrimination Data form, which you can
use to create, revise, copy, or delete the record of a discrimination data file as well as the file
itself. For more information, see Discrimination Data Form (on page 303).
Report Displays the Report form, which you can use to create, revise, delete, and
approve report records and report files. For more information, see Report Form (on page
308).
Report Management Data Displays the Report Management Defaults form, which
you can use to create a record in the project control database of the default nodename and
path for the report definition files. This option is primarily used for setup. For more
information, see Report Management Defaults Form (on page 316).
Group Workflow
There is a definite workflow for at least the first time you create a report. First, use the Report
Management Data option to specify defaults for the nodename and path of the report definition
files. By defining the defaults first, you can prevent keying in a nodename and path on each
form. If you want to use a different nodename or path than the defined default, simply place a
data point in that field and key in the modification.
The following steps can be done in any order: create your format record, discrimination data
record, and discrimination data file using the Report Format and Report Discrimination Data
options. Reports cannot be generated until the format file, the discrimination data file, and their
corresponding records have been established.
Finally, use the Report option to create the actual report.
This form enables you to create, copy, revise, or delete a record of the location of the format file
in the project control database. An option is also provided that enables you to copy a record and
its corresponding ASCII format files.
The format file defines the data that will be reported and the way in which that data will be
displayed. Reports cannot be generated unless a format file exists and a record of the file's
location has been entered into the project control database.
Create Displays the Format Creation/Revision form, which enables you to add a new
record of a format file in the project control database. For more information, see Format
Creation/Revision Form (on page 301).
Copy Displays the Format Creation/Revision form, which copies the record of an
existing format file from the project control database along with the corresponding ASCII
format file. For more information, see Format Creation/Revision Form (on page 301).
Revise Displays the Format Creation/Revision form, which modifies a record of an
existing format file in the project control database. For more information, see Format
Creation/Revision Form (on page 301).
Delete Displays the Deletion form, which deletes an existing record of a format file from
the project control database. If the record of the format file is deleted, reporting cannot be
performed. For more information, see Format Deletion Form (on page 302).
This form creates or revises a record in the project control database; this record defines the
location of a format file. The format file itself defines the contents and format of the report.
Both the location specification and the format file must exist to report on PDS data.
Number A unique number of up to 24 characters. Specifies the short name in the project
control database used to identify the record of the format file.
Description A description of up to 40 characters for the format file.
File Specification The file name of the format file to reference.
Path The disk location of the format file. This field retains the active setting.
Node The nodename of the system on which the format file is located. This field retains
the active setting.
Operating Sequence
1. Select Create, Copy, or Revise.
A list of available records displays for copy or revision. To create a database record, go to
Step 3.
This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
This form creates, copies, revises, and deletes a discrimination data file from the specified
directory. The associated record in the project control database is also copied, revised, or
deleted as needed.
A discrimination data file is an ASCII file that designates which models will be included in a
report. That is, discrimination data specifies the scope of the report. The project control
database record specifies the name and location of the discrimination data file that is to be
associated with a specific report.
Create Displays the Discrimination Data Creation form, which creates a new
discrimination data file. The associated project control database record is also created. For
more information, see Discrimination Data Creation Form (on page 304).
Copy Displays the Discrimination Data Revision form, which copies an existing data
file. The associated project control database record is also copied. For more information,
see Discrimination Data Revision Form (on page 305).
Revise Displays the Discrimination Data Revision form, which modifies discrimination
data. You can use this option to revise the contents of the discrimination data file, the
location of the discrimination file, and the associated record in the project control database.
For more information, see Discrimination Data Revision Form (on page 305).
Delete Displays the Deletion form, which deletes a discrimination data file as well as its
associated record in the project control database. For more information, see Discrimination
Data Deletion Form (on page 306).
This form creates a discrimination data file in a specified directory. It also creates a
corresponding record in the project control database. In addition, you can use this form to
specify segment and component search criteria.
If you use this form to specify search criteria data and you specify search criteria data
using the Report Search Criteria option, the data specified using the Report Search Criteria
option takes precedence.
Number The unique number, up to 24 characters, that is the short name of the
discrimination data record in the project control database.
Description The description, up to 40 characters, of the discrimination data record in the
project control database.
File Specification The file name of the discrimination data record to be created.
File Path The disk location of the discrimination data file. This field retains the active
settings.
File Node The nodename of the system on which the discrimination data file is located.
This field retains the active settings.
Piping Materials Class Key in up to 16 alphanumeric characters for the piping materials
class.
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Select Piping Materials Class Sets the piping materials class(es) in the
Specification/Material Reference Database which defines the tables to be checked.
No Piping Materials Class When selected, indicates to the system that either the piping
specialties or instruments will be verified by Table Checker.
Either format 5 or 6 must be used when the discrimination data is created with the No
Piping Materials Class button selected.
Operating Sequence
1. From the Report Discrimination Data form, select Create.
The Discrimination Data Creation form displays.
2. Specify Discrimination Data
In the fields provided, key in the number, description, file specification, path, and node.
3. Select additional options as needed to define the report discrimination data. Then select
Accept.
After including any models or search criteria for the discrimination data file, be
sure to select the final Accept. Because you must accept many forms while specifying the
discrimination data, it is easy to forget this step. Even though you may have accepted many
of the specifications, the discrimination data file is not actually created until you select
Accept on the Report Discrimination Data form.
This form revises an existing discrimination data file. It also copies an existing discrimination
data file; you can then use the revision options to modify the copy as needed. The corresponding
records in the project control database are copied and/or modified as needed. In addition,
options are provided for you to modify segment and component search criteria data.
If you use this form to specify search criteria data and you specify search criteria data
using the Report Search Criteria option, the data specified using the Report Search Criteria
option takes precedence.
Number The unique number, up to 24 characters, that is the short name of the
discrimination data record in the project control database.
Description The description, up to 40 characters, of the discrimination data record in the
project control database.
File Specification The file name of the discrimination data record to be created.
File Path The disk location of the discrimination data file. This field retains the active
settings.
File Node The nodename of the system on which the discrimination data file is located.
This field retains the active settings.
Piping Materials Class Select one or more piping materials classes from this list of
loaded classes.
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Select Piping Materials Class Sets the piping materials class(es) in the
Specification/Material Reference Database which defines the tables to be checked.
No Piping Materials Class When selected, indicates to the system that either the piping
specialties or instruments will be verified by Table Checker.
Either format 5 or 6 must be used when the discrimination data is created with the No
Piping Materials Class button selected.
Operating Sequence
1. From the Report Discrimination Data form, select Copy or Revise.
The Discrimination Data Revision form is displayed.
2. Specify Discrimination Data
In the fields provided, key in the number, description, file specification, path, and node.
3. Select additional options as needed to define the report discrimination data. Then select
Accept.
After updating any models or search criteria for the discrimination data file, be
sure to select the final Accept. Because you must accept many forms while specifying the
discrimination data, it is easy to forget this step. Even though you may have accepted many
of the specifications, the discrimination data file is not actually updated until you select
Accept on the Report Discrimination Data form.
This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
Report Form
When you select Report from the Report Manager form, the Report form is displayed.
This form creates, revises, and deletes report records and report files. A report record holds
specifications for a report; these specifications include the report name, the report description,
and which format file, discrimination data file, and search criteria data file to use to generate a
report.
The report name is not the title that is printed on the report; the title is included in the
format file.
At the end of each report, a parameters page is included that contains the following information:
Report Output The report number, report title, report creation/revision date, and report
node, path, and file name.
Format The report format number, description, and node, path, and file name.
Discrimination Data The report discrimination data number, description, and file
location (network address, path, and file name). The following discrimination data is also
included: list of model numbers (with discipline), volume (if applicable), search criteria (if
applicable), and sorting sequence.
Search Criteria The report search criteria number, description, and file location (node,
path, and file name. The following search criteria data is also included: list of model
numbers (with discipline), volume (if applicable), search criteria (if applicable), and sorting
sequence.
Options
Create Displays the Report Creation form, which creates a report record and generates
a report. For more information, see Report Creation Form (on page 309).
Revise Displays the Revise Report form, which regenerates a report from an existing or
revised report record. For more information, see Revise Report Form (on page 311).
Delete Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form (on page 313).
Approve Displays the Report Approval form, which approves an existing report. For
more information, see Report Approval Form (on page 314).
Multi-Create Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form (on page
315).
Use this form to create a report record and to generate a report. Because report records are
stored in the project control database, you can use them over and over again as needed.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
The Table Checker Report Number must not contain spaces. If there are spaces in the
number, the report will not be submitted to the batch queue.
Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings, and it is automatically populated if you have specified this data on the Report
Management Data form. For more information, see Report Management Defaults Form
(on page 316).
Report Node The name of the system on which the report output file will be located.
This field retains the active settings, and it is automatically populated if you have specified
this data on the Report Management Data form. For more information, see Report
Management Defaults Form (on page 316).
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit Immediately/Submission is Delayed Specifies when the report will be
processed. When this toggle is set to Submission is Delayed, additional fields display for
you to specify the date and time that the report is to be generated.
Operating Sequence
1. From the Report form, select Create.
The Report Creation form is displayed.
2. Specify Report Data
Key in the report record information. Then select the appropriate report format file,
discrimination data file, and search criteria data file.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
4. Specify whether the report is to be generated now (Submit Immediately) or later
(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.
5. Click Accept to save the report file.
This form revises an existing report record and generates a report from the project control
database. An option is also provided to update (in some cases) the report record without
generating a report output file. Similarly, you can choose to generate an updated report output
file without updating the report record.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings.
Report Node The name of the system on which the report output file will be located.
This field retains the active settings.
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.
Revise Data Only/Revise Report and Data Specifies revision of the report data only
(Revise Data Only) or revision of the report data and the report output file (Revise Report
and Data). To revise the report specification without updating the report output file, make
the necessary changes, set this toggle to Revise Data Only, and click Accept. To revise the
report output file only, set this toggle to Revise Report and Data without modifying any of
the fields, and click Accept. To modify both the report file and the report output file, make
the necessary changes, set this toggle to Revise Report and Data, and click Accept.
If you update any field other than Report Number and Report Title, this toggle is
automatically set to Revise Report and Data, and the report output file is generated.
Operating Sequence
1. From the Report form, select Revise.
The Report Creation form is displayed with a list of available report files.
2. Select Report
From the displayed list, select the report to be revised. Then click Accept.
The fields update to display the selected report file specifications.
3. Revise Report Information
Update the report record information as needed.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
5. Specify whether the report is to be generated now (Submit Immediately) or later
(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.
6. Click Accept to save the report file.
This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
Use this form to select a report to approve. Approving a report means that a database attribute is
set from not approved (the default) to approved. This approval status provides a way for you to
flag reports that you have run and verified that the output data is valid. When a report is revised,
the approval status is automatically reset to not approved.
Number The 24-character unique name (as called short name) of the report record.
Description The 40-character description of the report record.
Operating Sequence
1. From the Report form, select Approve.
The Report Approval form is displayed.
2. From the displayed list, select a report to approve. Then click Accept.
The Approval form is displayed.
For more information, see Approval/Revision Interface Form in the PD_Report User's
Guide.
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.
Operating Sequence
1. From the Report form, select Multi-Create.
The Report Multiple Submit form is displayed.
2. Select Reports for Submission
From the displayed list, select the reports to submit. Highlighted reports are selected; select a
highlighted report to remove the highlight and to not submit the report.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
4. Specify whether the report is to be generated now (Submit to Batch Immediately) or later
(Delayed Submit to Batch). If you choose delayed submission, specify the date and time
that the report is to be submitted.
5. Click Accept to submit the reports.
This form creates a record in the project control database of the node name and path of the report
definition files. This option is used primarily for setup.
Report Path Specifies the default path of the report output files.
It is recommended that you not send output reports to your system's temporary (that
is, tmp or temp) directory.
Report Node Specifies the default node name of the system on which report output files
are located.
Report Format Path Specifies the default path of the format files.
Report Format Node Specifies the default node name of the system on which format
files are located.
Report Discrimination Data Path Specifies the default path of the discrimination data
files.
Report Discrimination Data Node Specifies the default node name of the system on
which discrimination data files are located.
Report Search Criteria Data Path Specifies the default path of the report search criteria
data files.
Report Search Criteria Data Node Specifies the default node name of the system on
which report search criteria data files are located.
Operating Sequence
1. From the Report Manager form, select Report Management Data.
The Report Management Defaults form is displayed.
2. Accept or Exit
In the fields provided, key in the default paths and node names for the report output files,
format files, discrimination data files, and search criteria data files. Then click Accept.
Option:
Rating(s): CL800
Modifier: 3
Note 1: -
Note 2: -
AABBCC: 6Q1C01
Commodity Code: VAUSAHGAAA
Weight Code: 490 pcf (52)
EDEN Modules Tables
______
GATR FEM_420_800_5
V1_AMS GATR_4625_420_800_A
VALVE_2_AMS VAUSAHGAAA
V1 GATR_FEM_800_3_A
OP_3
OPERATOR_3
OP3
21-Apr-92 Page: 2
SIZE-INDEPENDENT SPEC DATA
__________________________
Rating(s): CL800
Modifier: 3
Note 1: -
Note 2: -
AABBCC: 6Q1C01
Commodity Code: VAUSAHGCAA
Weight Code: 490 pcf (52)
EDEN Modules Tables
______
GATF FEM_420_800_5
V1_AMS GATF_4625_420_800_A
VALVE_2_AMS VAUSAHGCAA
V1 GATF_FEM_800_3_A
OP_3
OPERATOR_3
OP3
21-Apr-92 Page: 3
SIZE-INDEPENDENT SPEC DATA
__________________________
Description: Gate valve, CL150, RFFE, BB, OS&Y,
ASTM-A105, trim 8, Smith 815
Rating(s): CL150
Modifier: 3
Note 2: -
AABBCC: 6Q1C01
F17D_AMS
F180
F180_AMS
F182
F182_AMS
F188
F188_AMS
F19
F19_AMS
F1A
F1A_AMS
F25
F25_AMS
F27
F27_AMS
F28
F39
F39_AMS
F47
F47T_AMS
F47_AMS
F6
F6_AMS
F8
F8_AMS
OPERATOR_33
OPERATOR_9
OP_17
OP_3
OP_33
OP_331
OP_332
OP_9
PIPING
PLUG
REDC
REDE
RPAD
RWELD
SOL
SWGC
SWGE
T
TRB
UN
V1
V11
V1_AMS
V26
V38
V6
VALVE_2_AMS
WOL
Error Codes
The following error codes are used in the reported error messages.
-3 Eden Module Not Found
-4 Entry Not Found in Table
-7 Table Not Found
Options
Create Library (on page 328) Used to create a new Tutorial Definition Library.
Compress Library (see "Compress" on page 328) Used to compress the Tutorial
Definition Library.
Unapproved ==> Approved (on page 328) Used to copy the unapproved Tutorial
Definition Library to the approved library.
Create Data (on page 329) Used to compile source files and add the resulting code to the
Tutorial Definition Library. You can create a single tutorial definition file or specify a list
of tutorial definition files to be created.
Revise Data (on page 329) Used to select a tutorial definition file from the library for
editing and compile the revised tutorial definition file.
Delete Data (on page 330) Used to delete a specified tutorial definition file from the
library.
Report Data (on page 331) Used to create a report file of the library contents.
List Data (on page 333) Used to list the files contained in the library.
Extract Data (on page 333) Used to extract a tutorial definition file from the library for
editing or printing.
Full List/Sub-string Use this toggle to determine the data to be listed. Full List returns
all the definition in the Tutorial Definition Library. Sub-string limits the list to those files
that contain the substring you enter in the corresponding box.
Node Name Key in the node name of the location of the table definition files for pipe
supports.
File Path Key in the path to the location where you store table definition files for pipe
supports.
Create Library
This option is used to create a new Tutorial Definition Library.
The system displays the approved and unapproved Tutorial Definition Library names as defined
in the RDB Management Data.
Compress
This option is used to compress the Pipe Support Tutorial Definition Library. Any tables which
have been deleted from the library will be removed.
Create Data
This option enables you to create a new tutorial definition file. You can process a single file or
specify a list of files to be created.
Operating Sequence
1. Select the Create Data option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
Key in the name of the source file or list file to be compiled and added to the active library.
The system displays the default node name and path for the tutorial definition files as
specified in the Default Project Control Data at the bottom of the form.
You can use the default setting or modify these fields to override the default location for this
operation.
4. Accept or Select Other Option
Accept the file to begin processing.
If a fatal error occurs while loading files, the Tutorial Definition File Library is left unchanged.
Revise Data
This option enables you to replace an existing tutorial definition file. This option enables you to
select a tutorial definition file from the library, edit the file, and then compile the file and put it
back in the library.
Operating Sequence
1. Select the Revise option.
The system displays the tutorial definition files in the Tutorial Definition Library.
When you exit the text editor, the system compiles the revised file and inserts it back into the
library. (If you quit the text editor, the file is not recompiled.)
Delete Data
This option enables you to delete a tutorial definition file from the Tutorial Definition Library.
Operating Sequence
1. Select the Delete option.
The system displays the tutorial definition files in the Tutorial Definition Library.
Report Data
This option enables you to create a report on the contents of the Tutorial Definition Library.
This report lists all the tutorial definition files in the Tutorial Definition Library.
Operating Sequence
1. Select the Report Data option from the Library/Data Management form.
2. Set the toggle to Report on Unapproved or Report on Approved to define the source of
information to be reported. This toggle is only displayed when both the approved and the
unapproved library are being used.
3. Select the report option: Save, Print/Delete, or Print/Save.
For the Print/Delete or Print/Save options, select the print queue from the list of displayed
queues.
List Data
This option displays all the tutorial definition files for the Tutorial Definition Library.
Operating Sequence
1. Select the List option.
The system displays the tutorial definition files in the Tutorial Definition Library.
2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.
Extract Data
This option enables you to extract a tutorial definition file from the Tutorial Definition Library
for editing or printing.
Operating Sequence
1. Select Extract Data from the Library/Data Management form.
Library List
The Library List form allows you to select database tables in order to revise, delete, list or
extract the tables.
Operating Sequence
1. Select Table.
Select a table to manipulate.
2. Accept or Select Other Table(s).
Select more tables to manipulate.
OR
Select Accept to continue the workflow.
OR
Select Cancel to exit the form.
N499
; Piping Notes
1 = ' '
;
; Notes Applicable to the Piping Materials Class, 2-199
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
;
; Notes Applicable to a Piping Component, 200-499
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
;
; Notes Applicable to a Piping Specialty, 500-699
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
;
; Notes Applicable to an Instrument Specialty, 700-899
WWW =
'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
General Rules
EACH standard note type or code list type should be contained in a separate neutral file.
Neutral files should have the following basic format:
C125 DF='WRK_DD_CODLST:CODE0125.ENT' MAX=999
; This is a comment line !!!!!!
; This file contains a code list for type 125.
0125, Fluid Code/Connector Type (999)
NOTE: In editing this codelist set, do not change the meaning
of existing codelist values 950-999.
1 = ' '
6 = 'Standard note or code list descriptions can extend
beyond one line of text up to a maximum of 80 characters'
11 = 'A'
14 = 'AC'
17 = 'AE'
The first entry in each neutral file should be the note/code TYPE (C125 in the above
example). The first letter must be either: C for a codelist set or N for a standard note.
This character is followed by a number, which identifies the specific codelist set or standard
note. This number must be a valid short integer.
This entry should also include the text used for extracting information from the Standard
Note Library. This text may contain up to 80 characters.
The first line should also contain the maximum number of entries for the codelist or standard
note.
The following numbering conventions are used for standard note type 499:
Piping Job Specification: note numbers 1 through 199.
Piping Commodity Item: note numbers 200 through 599.
Specialty Item: note numbers 600 through 799.
Instrument Item: note numbers 800 through 999.
You can include the keyword PID_RDB in the neutral file on the line following the standard
note type to load the standard note into both the Piping Reference Database and the P&ID
Reference Database simultaneously. (Optional)
Each note/code entry is comprised of three parts (triplet) which must appear in the following
sequence.
<Note/Code number> <equal sign> <Note/code description>
2 = 'Sulfuric Acid'
The description text must be enclosed in single quotes.
The description text can extend for more than one line.
Code list description text can contain up to 80 characters.
Standard note description text can contain up to 400 characters.
The Note/code description text can be on a line by itself.
The equal sign must have a blank character on either side of it.
The equal sign can be on a separate line by itself.
The note/code number must be a valid I*2 integer.
The note/code number must begin a new line; it cannot be on the same line with any
part of another triplet.
The note/code number can be on a line by itself.
The only valid edit you can make to code list 1056 (temperature units) and code list 1064
(pressure units) is to modify the displayed text string. Modifications to this field affect only
the display of the text; the actual units (for example, degrees) cannot be modified. You
cannot add any entries to code lists 1056 and 1064.
Comments are indicated with a semicolon (;) or exclamation point (!). Any information on a
line to the right of either of these characters is considered a comment and is ignored. These
comment lines can only occur following a description; they cannot break up a triplet.
Valid Comments
1 = 'Caustic'
; Comment line.
2 = 'Sulfur' ! Another Comment line.
! Another Comment line.
3 = 'Hydrogen Sulfide' ; Another Comment line.
Invalid Comments
1 =
; Invalid Comment line.
'Caustic'
2 = ! Invalid Comment line. 'Sulfur'
Any text enclosed in < angle brackets > is considered a comment and is ignored. These
comments can appear anywhere in the neutral file except within a description.
Blank lines can occur anywhere in a neutral files for readability. These lines are ignored.
Each entry can begin at any point along an input line but must be separated from adjacent
entries by one or more spaces.
Note/code numbers need not be in sequential order.
Options
Create Library (on page 340) Used to create a new Standard Note Library.
Compress Library (see "Compress" on page 340) Used to compress the Standard Note
Library.
Unapproved ==> Approved (on page 340) Used to copy the unapproved Standard Note
Library to the approved library.
Create (see "Create Standard Note Type" on page 340) Used to compile source files and
add the resulting code to the Standard Note Library. You can create a single standard note
set or specify a list of standard notes to be created.
Revise (see "Revise Standard Note Type" on page 341) Used to select a standard note set
from the library for editing and compile the revised standard note definition.
Report (see "Report Standard Note Library Contents" on page 342) Used to create a
report file of the library contents.
List (see "List Standard Note Data" on page 343) Used to list the files contained in the
library.
Delete (see "Delete Standard Note Data" on page 343) Used to delete a specified standard
note set from the library.
Extract (see "Extract Standard Note Type" on page 344) Used to extract a standard note
set from the library for editing or printing.
Load Database (on page 345) Used to load the contents of the Standard Note Library into
the applicable schemas of the project's relational database to support DBAccess reporting of
PDS data.
Create Library
This option is used to create a new Standard Note Library. It automatically creates the object
library (.l) and the text library (.l.t) for the library that is being created.
The system displays the approved and unapproved Standard Note Library names as defined in
the RDB Management Data.
Compress
This option is used to compress the Standard Note Library. Any tables which have been deleted
from the library will be removed.
Operating Sequence
1. Select the Create option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
Key in the name of the source file or list file to be compiled and added to the active library.
The system displays the default node name and path for the standard note neutral files as
specified in the Default Project Control Data at the bottom of the form.
You can use the default setting or modify these fields to override the default location for this
operation.
4. Accept or Select Other Option
Accept the file to begin processing.
If a fatal error occurs while loading neutral files, the Standard Note Library is left unchanged.
Operating Sequence
1. Select the Revise option.
The system displays the standard note types in the Standard Note Library.
Operating Sequence
1. Select the Report option from the Data Management form.
2. Set the toggle to Report on Unapproved or Report on Approved to define the source of
information to be reported. This toggle is only displayed when both the approved and the
unapproved library are being used.
3. Select the report option: Save, Print/Delete, or Print/Save.
For the Print/Delete or Print/Save options, select the print queue from the list of displayed
queues.
4. Select Accept to create the report.
For the Save or Print/Save options, the system generates a report named stnotelib.rpt in the
default directory based on the contents of the Standard Note Library.
Operating Sequence
1. Select the List option.
The system displays the Standard note types in the Standard Note Library.
2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.
Operating Sequence
1. Select the Delete option.
The system displays the Standard note types in the Standard Note Library.
Operating Sequence
1. Select Extract from the Data Management form.
Load Database
This option loads the contents of the Standard Note Library into the applicable schemas of the
project's relational database to support DBAccess reporting of PDS data.
The note type and the maximum length are separated by one or more spaces or tabs. An asterisk
(*) following the maximum length indicates that the short version of the standard note data be
loaded into the relational database. The default is that the long version be loaded. Comments
can be placed anywhere in the file and must be preceded by an exclamation point (!).
You can determine which standard note data is loaded or not loaded into the relational database.
If the maximum length for a standard note type is defined as zero (0) or the standard note type is
not included in stnote_max_len, the data for that standard note type will not be loaded.
Standard notes loaded into the schema are listed below.
In DD_SCHEMA, the following codelists required by designing purposes are loaded:
design_cls[36]={35,
35,50,69,125,130,145,160,180,190,200,210,220,230,330,340,360,365,380,390,400,420,425,
430,499, 570,575,576,577,578,1010,1028,1056,1064,1074,1100};
In PD_SCHEMA, the following codelist tables required at the project level are loaded:
project_cls[17]={16,
35,499,1202,1203,1204,1205,1207,1310,1312,1410,1610,1620,1630,1710,1720,2000};
In RU/RA_SCHEMA, the following codelist tables required at the database level are loaded:
reference_cls [12] = {11,125,145,148,180,330,400,499,575,576,577,578};
A default note length file is delivered with the PD_Shell product in the file
\win32app\ingr\pdshell\lib\stnote_max_len. These maximum lengths were determined on the
basis of the long option of standard note data reporting. To minimize relational database size,
you should exercise discretion in specifying the maximum length. The maximum length for any
standard note type is restricted to 240 characters by RIS.
Operating Sequence
1. Select Load Database from the Data Management form.
2. Select Submit to Batch Immediately to begin processing as soon as you exit the form.
OR
Select Delayed Submit to Batch to specify a day and time to process the request.
3. Accept the specified time.
The system submits the request to the batch queue PDreference.
Label Types
Displayable Attribute Labels (on page 348)
Alphanumeric Labels (on page 348)
Displayable Attribute Message (on page 348)
Commodity Code Attribute Message (on page 349)
Isometric Drawing Labels (on page 349)
Report Labels (on page 349)
Clash Management Labels (on page 349)
Alphanumeric Labels
Alphanumeric labels are non-intelligent user-defined labels. Each type of alphanumeric label has
a description in the Label Description Library. This description identifies the label
characteristics such as level, color code, style, and font. An alphanumeric label consists of the
text and optionally, a leader line, a line terminator, and some label enclosure graphics.
Report Labels
A range of report labels (1150-2149) is reserved in the Label Description Library for use in
formatting fields in a report. This is accomplished by using the special report indices for the
Label Description Library. (Refer to the Report Manager Reference Guide for information on
the report indices.)
When report labels are used, you cannot sort on an individual attribute used to form the
report label. However, you can sort on the complete report label.
The label to be used is determined on the basis of the model's discipline and the type of
component. The following label numbers are reserved in the Label Description Library for use
in clash management.
Envelope builders for disciplines other than piping and equipment do not implement the
labels reserved below.
2200 Piping - primary description for piping specialty - 2 cp's
2201 Piping - primary description for piping specialty - 3 cp's
2202 Piping - primary description for piping commodity - 2 cp's
2203 Piping - primary description for piping commodity - 3 cp's
2204 Piping - primary description for piping/tubing
2205 Piping - primary description for instrument component - 2 cp's
2206 Piping - primary description for instrument component - 3 cp's
2207 Piping - primary description for pipe support
2208 Piping - secondary description for piping segment
2220 Equipment - primary description for equipment
2221 Equipment - primary description for nozzle
2222 Equipment - secondary description for equipment
2223 Equipment - secondary description for nozzle
2240 PLANTGEN - pipe
2241 PLANTGEN - piping component
2242 PLANTGEN - equipment/miscellaneous
2243 PLANTGEN - nozzle
2244 PLANTGEN - structural/civil
2245 PLANTGEN - HVAC
2246 PLANTGEN - raceway
2247 PLANTGEN - pipe support
2260 Raceway - Straight Primary Label
2262 Raceway - Straight Secondary Label
2261 Raceway - Fitting Primary Label
2263 Raceway - Fitting Secondary Label
2264 Raceway - Panel Primary Label
2265 Raceway - Panel Secondary Label
2266 Raceway - Ductbank Primary Label
2267 Raceway - Ductbank Secondary Label
2280 HVAC - Primary Label for Connector
2281 HVAC - Secondary Label for Connector
2282 HVAC - Primary Label for Fitting
2283 HVAC - Secondary Label for Fitting
2284 HVAC - Primary Label for Duct
2285 HVAC - Secondary Label for Duct
2286 HVAC - Primary Label for Diffuser
2287 HVAC - Secondary Label for Diffuser
2288 HVAC - Primary Label for Grille
2289 HVAC - Secondary Label for Grille
2290 HVAC - Primary Label for Register
2291 HVAC - Secondary Label for Register
2292 HVAC - Primary Label for Humidifier
2293 HVAC - Secondary Label for Humidifier
Create Library (on page 352) Used to create a new Label Description Library.
Compress Library (on page 352) Used to compress the Label Description library.
Unapproved ==> Approved (on page 352) Used to copy the unapproved Label
Description library to the approved library.
Create Label Data (on page 352) Used to create a new label description and insert it in
the Label Description Library.
Revise Label Data (on page 362) Used to select a label from the library, edit the file, and
put the revised file back into the library.
Delete Label Data (on page 365) Used to remove a label description from the library.
Report Label Data (on page 365) Used to create a report of the library contents.
Create Library
This option is used to create a new Label Description Library. This option will be deactivated if
the specified library already exists.
The system displays the approved and unapproved Label Description Library names as defined
in the RDB Management Data.
Compress Library
This option is used to compress the Label Description library. Any labels which have been
deleted from the library will be removed.
Operating Sequence
1. Select Create Label Data from the Data Management form.
The system displays a form listing the types of labels which can be created.
2. Select Option
Select the type of label to be created. See Label Types (on page 348) for a description of all
the label types and subtypes.
The system adds a label number in the range for the selected label type, and activates one of
the following screens to enable you to define the description data and/or attribute data for
the label to be created.
For Drawing View Specific Labels and Drawing View Identification Labels, you can
define both graphic data and attribute data.
For User Input Labels, you can define graphic data only. Refer to Create Label
Graphic Data (on page 355) for more information.
For Isometric Drawing Labels, Displayable Attribute Labels, Commodity Code
Labels, Report Labels, or Clash Management, you can define attribute data only.
Refer to Create Label Attribute Data (on page 357) for more information.
Label Subtypes
Depending on the Option selected, the system may activate one of the following basic types of
labels to further classify the type of label to be created. (The numbers in parentheses indicate the
range of label numbers for each group of label types.)
Create Label Attribute Data (on page 357) Enables you to specify the attributes which
make up the label and the format of the label.
Mass Annotation Options (on page 362) Enables you to set up the Mass Annotation
options for use with PD_Draw.
Field Descriptions
Label Type Number of the label being created. (This field is filled in automatically by
the system.)
Label Description Short description for the label (up to 20 characters).
Graphics Color Activates the Select Color form used to set the color for the label
enclosure, leader line, and line terminator.
Graphics Weight Line weight (0-31) for the label enclosure, leader line, and line
terminator.
Graphics Style Line Style (0-7) for the label enclosure, leader line, and line terminator.
Alternate Style Alternate (centerline) line style (0-7) for name label leader lines. The
default is the same as the Graphics Style.
Text Color Activates the Select Color form used to set the color for the label text.
Text Weight Line weight (0-31) for the label text.
Character Size Activates the Define Active Character Size form used to set the character
plot size (text height and text width). You can select one of the default settings (A - J) or
key in a size. The default settings are defined in the drawing's type 63 data. Refer to the
Project Data Manager in the Project Administrator Reference Guide for information on
setting the default sizes.
Maximum Length Maximum line length (1-80) for the text. This setting is also used to
determine the label enclosure size.
Line Spacing Line spacing between label text represented as a fraction of text height (0. -
10.). Also used to determine label enclosure size.
Maximum Lines Maximum number of lines in the label text (1-30). Also used to
determine label enclosure size.
Text Font Font (0-255) for the label text.
Enclosure Option Displays a set of options at the bottom of the form for setting the type
of label enclosure. The default is No Label Enclosure.
The User Defined Enclosure Option places as a cell, with no Leader Line. When this
option is chosen, the Leader Line Option toggle is no longer available.
Diameter (Used with Label Enclosure Options 2 and 3) Diameter of the circle enclosure
graphic.
Cell Name (Used with Label Enclosure Option 8) Name of the Label Enclosure cell.
Leader Line Option Toggle to define whether to use a Leader Line for the label.
Terminator Char. Character that represents the line terminator symbol in the attached
Font Library.
Terminator Font Font (0-255) for the line terminator.
Underline Spacing Underline spacing below text represented as a fraction of text height
(0. - 10.). If this value is 0, no underlining is performed.
Label Category The form displays the name label category and the user-defined drawing
annotation categories. You can select one of the 20 user-defined drawing annotation
categories or use the default category. The default category is that of the name label
category. The text for the drawing annotation categories is extracted from the drawing
category descriptions (drwcats.txt) in the project directory.
All of these parameters do not apply to each label type; the system skips over any non-required
parameters.
Once you have defined all the applicable parameters, select Attribute Label Data to specify the
attributes which make up the label and the format of the label (or select Accept for graphics only
labels). If your project will be using the Mass Annotation command in PD_Draw to simplify
label placement, select the Mass Annotation Options command to set up the Mass Annotation
options. Refer to Mass Annotation Options (on page 362) for more details.
Insert Data
1. Set the option to Insert Data.
2. Set the toggle to Insert after or Insert before.
3. Select Line or Item to Insert Data
Select a line field to create a new line (before or after) the selected line.
OR
Select an item field to create a new item in the current line (before or after) the selected item.
The system activates a form that displays the Attribute Data Types. The following forms
illustrates the displays for a drawing view specific label. (The second form appears when
Other Data is selected.)
4. Select Option
Select the attribute data type for the label.
You can select Other Data to select the attribute data type for Raceway data.
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).
For labels that include an angle value (such as the bend angle of a piping component), select
the Angle format to display the value in angle units (such as degrees and minutes). The
angle units are determined by the angular format defined through the Project Data
Manager.
For labels that include a distance attribute (such as the face-to-face dimension of a piping
component), you can select Fraction to format decimal attributes as a coordinate readout.
This option is restricted to those decimal attributes that represent dimensions.
OR
For drawing view specific labels, you can select User Keyin Attribute to specify text to be
entered by the user at label creation.
OR
Select Text Only and key in the text for a literal expression to be inserted in the label.
OR
Select Spacing Only and key in the number of spaces to define spacing between attributes.
6. Repeat the previous step to add additional attribute text information. This allows you to
combine attribute values and pre-formatted text.
You can only define one user-defined keyin 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. Accept the specified attribute data.
Delete Data
1. Set the option to Delete Data.
2. Select the line or item to be deleted.
3. Select Accept to delete the highlighted line or item. When you select a line, the system
deletes all the associated items.
Edit Data
1. Set the option to Edit Data.
2. Select Item to Edit
Select the item to be revised.
The system displays the attributes definition form for the selected item. The active setting is
highlighted or shown in the display fields.
3. Select an attribute from the form to change the type of data.
OR
Select the Format Data option. You can modify the total length and the number of decimal
places (if applicable).
OR
For drawing view specific labels, you can select User Keyin Attribute to specify text to be
entered by the user at label creation.
OR
Select Text Only and key in the text for a literal expression to be inserted in the label.
OR
Select Spacing Only and key in the number of spaces to define spacing between attributes.
4. Repeat the previous steps to edit additional items.
THEN
Accept the edits.
Examples
This form allows you to specify the following options for use with the Mass Annotation
command in PD_Draw:
Are Previously Labeled Objects to be Labeled?
Are Objects Clipped by Drawing View Bounds to be Labeled?
Are Objects Hidden by Other Objects to be Labeled?
Operating Sequence
1. Place a data point on the desired selection under each question.
2. Accept the selections and return to the Create Label Graphic Data form.
Operating Sequence
1. Select Revise from the Data Management form.
The system activates the following form which enables you to select the type of label to be
modified.
2. Select Option
Select the type of label to be revised. See Label Types (on page 348) for a description of all
the label types and subtypes.
The system displays the existing label for the selected label type.
3. Select Label Type
Select the specific label description to be revised.
Depending on the label type selected, the system displays the graphic data form or the
attribute data form.
For example, if you select label type 011, the system displays the following form.
4. Select the parameter to be modified and key in the new value for that parameter.
5. You can select Attribute Label Data to activate the attribute data form.
6. Set the option to Insert Data, Delete Data, or Edit Data. The default is Edit Data. Refer
to Create Label Attribute Data (on page 357) for information on these options.
7. When finished, select Accept to save the changes and return to the Revise Label Description
form.
OR
Operating Sequence
1. Select Delete Label Data from the Data Management form.
The system activates the following form which enables you to select the type of label to be
deleted.
2. Select Option
Select the type of label to be deleted. See Label Types (on page 348) for a description of all
the label types and subtypes.
The system displays the existing labels for the selected label type.
3. Select Label Type
Select the specific label description to be deleted.
4. Accept to Delete Label Type xxx
Select Accept to delete the selected label type.
The system deletes the description and refreshes the selection screen to enable you to delete
another label type.
5. Select Cancel to return to the Data Management form.
Operating Sequence
1. Select Report Label Data from the Data Management menu.
Features
Copy labels from one library to another.
Delete an existing label from the destination library.
Rename an existing label in the destination library.
Compress the destination library.
Validate the destination library.
The Label Library Merger dialog box contains three label description library views. The two
views on the left display the contents of the source libraries, and the view on the right displays
the contents of the destination library. Each library view is divided into two columns, Number
and Description, which display the appropriate data for each label. You can click a heading in
any library view to sort the labels by that heading.
The bottom pane of the Label Library Merger dialog box is the message window, which
displays errors and other informational messages during the library merge workflow.
File Menu
The commands on the File menu allow you to open libraries, display information in the Message
Window, and exit the Label Library Merger.
Information
This command displays information in the Message Window regarding the source and
destination libraries.
Example
Exit
This command closes the Label Library Merger utility.
Edit Menu
The commands on the Edit menu allow you to modify your selections in the various views on
the Label Library Merger dialog box, modify and delete the label information in the
destination library, and check the destination library for errors.
Select All
This command selects all the labels in the active view.
Unselect All
This command resets selections so that no labels in the active view are selected.
Invert Selection
This command switches the selection status of the labels in the active view, so that labels that are
currently selected become unselected, and labels that are currently not selected become selected.
Delete
This command removes the selected labels from the destination library.
Validate
This command checks the labels in the destination library for valid label numbers, and reports
any invalid label numbers in the Message Window.
Copy to Destination
This command copies the selected labels from the source libraries to the destination library. The
system uses the following criteria to determine label numbers:
If there is no label in the destination library with the same label number as the label being
copied, the label is copied with its original label number.
If there is a label in the destination library with the same label number as the label being
copied, the label is copied with a new label number, which is assigned using the following
criteria:
If there is an unassigned label number in the copied label's category in the destination
library, the system assigns the next available label number in that category.
If there is no unassigned label number in the copied label's category in the destination
library, the system adds 5000 to the label number and copies the label. For example,
label number 23 in the source library is copied to label 5023 in the destination library.
Label numbers above 5000 generate errors in PDS. The Validate command
reports any such label numbers in the Message Window.
Refer to Label Description Library (on page 347) for more information on label
categories.
Help Menu
The commands on the Help menu display online Help and other information about the Label
Library Merger utility.
Contents
This command displays the Label Library Merger online Help file.
6. Select labels in the existing label description libraries to copy to the destination library. Use
CTRL+click to select multiple labels, or SHIFT+click to select a range of labels. Use the
selection commands on the Edit menu to select all labels, unselect all labels, or invert your
selections.
7. Click Edit > Copy to Destination to copy the selected labels to the destination library.
The system displays the copied labels in the Destination Library View.
8. Click Edit > Edit Label Number or Edit > Edit Label Description to modify labels in the
destination library as necessary.
9. Click Edit > Validate to check the destination library for errors.
The system displays any warnings in the Message View.
10. Click Edit > Compress Destination Library to compress the destination library.
11. When you are finished modifying the destination library, click File > Exit to exit the Label
Library Merger utility.
PAL Keywords
The following list outlines all the keywords that can be used to create a PAL definition.
Keywords followed by a number in (parentheses) such as
NPD_A (3221), NPD_B (3222), NPD_C (3223)
are used to create form gadgets for defining and placing piping assemblies. The number
represents the application command number for the keyword. The key entry field number is this
number minus 3000. (Therefore, the key entry field number for NPD_A is 221.)
Formbuilder Guidelines
You can customize forms for the purpose of inputting data in the creation of a piping assembly,
such as a control station. You can use the gadget numbers for the corresponding input fields.
You must adhere to the following conventions when customizing form input fields for the
applicable piping assembly. If not documented, any other gadgets on the form should remain
consistent with those delivered by Intergraph.
All input fields should be sequenced and must have the following characteristics. The Edit
Field Options setting in the Form Builder should be Change Mode.
The characteristics form in the Form Builder should have the following settings.
Notify Upon Completion - off (NOT the default)
Notify at Initial Selection - off
The forms delivered by Intergraph can be used as examples for customization. The following
list the form builder data for the standard form gadgets.
Help
key: 456
gadget number: 995
button: automatic
Form Size
key: 403
gadget number: 997
button: automatic
Exit
key: 4001
gadget number: 998
button: manual
Accept
key: 4002
gadget number: 999
button: manual
Material description
display
gadget number: 150
characters: 80
lines deep: 3
edit mode: review only
font size: 12
Description
#
This keyword is used to specify a description for the piping assembly from within the assembly
language file. Place a # in the first column of any line followed by a description of as many as
100 characters.
Examples:
# Control Station
Commands
COMMAND
This keyword is used with other keywords to initiate a defined action.
Examples:
COMMAND = GET_TUTORIAL_DATA
COMMAND = UPDATE_APP
COMMAND = POINT_IN_SPACE
CONNECT
This keyword defines the active point for the next component placed in the PAL definition. The
specified reference point must be defined before using this option.
Example: CONNECT TO REF_PNT_A
PLACE
This keyword defines the type of item to be placed. Refer to the PLACE Command Component
keywords for a list of component/instrument types.
Example: PLACE FITTING , 6Q2C01 ,
BY
This keyword is used with the PLACE keyword to set the placement mode to be used in placing
the specified component. Refer to the Connect Point keywords for a list of viable placement
modes.
Example: PLACE FITTING , 6Q2C01 , BY CP1
STEM
This keyword is used with an orientation keyword to define the direction of the secondary axis.
It can be used at the end of a PLACE statement.
Example: PLACE FITTING , 6Q2C01 , BY CP1 , STEM = UP
These keywords are used to place instruments and specialty items that have been defined in the
PJS using the tag number.
Example: PLACE RDB_INSTRUMENT, INSVLV1, BY CP1
Connect Point
CENTER, CP1, CP2, CP3, CP4, CP5
ACTIVE_PP
FACE_OF_FLANGE_CP1, FACE_OF_FLANGE_CP2,
FACE_OF_FLANGE_CP3
These keywords identify the connect point for an operation. They can be used with the BY
keyword to indicate the means of placement.
Example: PLACE VALVE, 6Q1C38, BY CP1
INLET_ELEVATION
This keyword sets the starting elevation or point of connection.
Example:
REF_PNT_A = ACTIVE_PP
COORDINATE_1 = INLET_ELEVATION
Orientation
ACTIVE
EAST, NORTH, UP
WEST, SOUTH, DOWN
These keywords identify the orientation direction.
Example: PLACE FITTING, 6Q2C01, BY CP1, STEM = UP
No Material TakeOff
NO_MTO=1
This keyword can be used immediately before a PLACE statement to specify that the component
is not reportable. The system automatically resets MTO processing after placement.
Once a reference point is defined, it can be used by a following statement in the PAL definition
to indicate a coordinate location (for example, CONNECT TO REF_PNT_A).
Dimension Definition
DIMENSION_1 (3141), DIMENSION_2 (3142), ... DIMENSION_20 (3160)
The Dimension keywords identify distances and offsets.
These keywords define coordinate values for the component just placed.
Example: TAP_LOCATION_Y = COMPONENT_CENTER_Y + DELTA_DISTANCE *
UORS_PER_SUBUNIT
Outside Diameter
PIPE_OD_CP1, PIPE_OD_CP2
These keywords contain the pipe outside diameter at each connect point for the component just
placed. These values can be used to calculate a tap location.
Example: DELTA_DISTANCE = ( PIPE_OD_CP1 - PIPE_OD_CP2 ) / 4.0
FLANGE_OD_CP1, FLANGE_OD_CP2
These keywords contain the flange outside diameter at each connect point for the component just
placed. These values can be used to calculate a tap location.
Point in Space
Example: COMMAND = POINT_IN_SPACE
The values of the keywords APP_X, APP_Y, and APP_Z are used to define the active placement
point that is not connected to piping or a piping segment. These keywords need to be set before
POINT_IN_SPACE is called.
Logical Marks
CHECK_MARK
CHECK_MARK_1 (3161), CHECK_MARK_2 (3163), ... CHECK_MARK_20 (3180)
The check marks are logical keywords that can be accessed through the tutorial. They can be
used for testing for placement of components, etc. Initially, they are all set to true.
Component Attributes
NPD_A (3221), NPD_B (3222), NPD_C (3223)
NPD_D (3284), NPD_E (3285), ... NPD_J (3290)
These keywords store nominal piping diameter values.
END_PREP_A (3231), END_PREP_B (3232)
These keywords store end preparation values.
RATING_A (3236), RATING_B (3237)
These keywords store pressure rating values.
SCHEDULE_A (3241), SCHEDULE_B (3242)
These keywords store schedule/thickness values.
Component Group
COMPONENT_GROUP, ON, OFF
Example: COMPONENT_GROUP = ON
This statement causes the system to search for the next available component group number. This
number is assigned to the component group number attribute of each subsequent component
placed until the statement COMPONENT_GROUP = OFF is executed or the assembly is completed.
Local Variables
You can use local variables to store values for use in defining a piping assembly. You can use
any alphanumeric string as long as it is not reserved as a keyword.
table. The active component data is represented by the last component placed or the component
to which the user is connected.
DRAIN
# Drain assembly
PAL 'DRAIN'
!
! This assembly will place a drain. The user needs to place a 1"
! sockolet at the point the drain is desired.
!
PLACE FITTING, 6Q3C88 , BY CP1
!
! The data from the component spec is read into the keywords.
! TERM_TYPE_1 TO 5 gets the numeric value for end preparation (eg. 21)
! PR_RATING_1 TO 5 gets the pressure rating
! GEN_TYPE_1 TO 5 gets the textual value for end preparation (eg. MALE)
!
LOAD_SPEC_DATA = '6Q1C76'
!
! This 'IF' statement determines if an optional flange is needed before
! the gate valve is placed.
!
IF ( GEN_TYPE_1 .EQ. BOLTED ) THEN
OPTION_RATING = PR_RATING_1
OPTION_END_PREP = TERM_TYPE_1
PLACE OPTIONAL , 6Q2C01 , BY CP2
ENDIF
!
! Places a gate valve. Notice in the spec that this type of gate valve
! is different than a 6Q2C01.
!
PLACE VALVE, 6Q1C76 , BY CP1
IF ( GEN_TYPE_2 .EQ. BOLTED ) THEN
OPTION_RATING = PR_RATING_2
OPTION_END_PREP = TERM_TYPE_2
PLACE OPTIONAL , 6Q2C01 , BY CP1
ENDIF
!
! This command allows the user to pick which component to place. If
the
! option command is not used the s/w will choose option 1. In this
instance,
! without the OPTION_CODE command will cause an error because there are
no
! option 1 attributes available for 6Q2C16. Another possiblilty would
be to
! use OPTION_CODE = PROMPT. The user will be prompted for which
component is
! desired.
!
OPTION_CODE = 163
PLACE FITTING, 6Q2C16 , BY CP1
END
# Pump Discharge
PAL 'PDISC1'
!
! Pump Discharge
!
!
DISPLAY_TUTORIAL = 'PAS010'
NPD_A = FIRST_SIZE
DISPLAY_NUMERIC = NPD_A
NPD_B = SECOND_SIZE
DISPLAY_NUMERIC = NPD_B
PROMPT_MESSAGE = 'Enter Reducer First Size '
DISPLAY = PROMPT_MESSAGE
COMMAND = GET_TUTORIAL_DATA
PLACE FLANGE , 6Q2C01 , BY CP1
FIRST_SIZE = NPD_A
DELTA_DISTANCE = ( PIPE_OD_CP1 * 0.5 - PIPE_OD_CP2 * 0.5) / 2.0
PLACE FITTING , 6Q2C23 , BY CP2
Refer to Piping Assembly Library (on page 379) for more information on this library, and refer
to Piping Assembly Language (on page 379) for more information on the PAL files.
Options
Create Library (on page 395) used to create a new Piping Assembly Library.
Compress (on page 395) used to compress the Piping Assembly library.
Unapproved ==> Approved (on page 395) used to copy the unapproved Piping
Assembly library to the approved library.
Create/Interactive Data (see "Create/Interactive Piping Assembly Data" on page 395)
used to compile Piping Assembly Language source files and insert them in the Piping
Assembly Library.
Create/Batch Data (see "Create/Batch Assembly Data" on page 396) used to compile
Piping Assembly Language Source files via batch processing.
Revise Data (see "Revise Piping Assembly Data" on page 397) used to select an PAL
module from the library, edit the file, and put the revised file back into the library.
Delete Data (see "Delete Piping Assembly Data" on page 398) used to remove an PAL
module from the library.
Report Data (see "Report Assembly Data" on page 399) used to create a report of the
library contents.
List Data (see "List Assembly Data" on page 400) used to display the Eden modules in
the library.
Extract Data (see "Extract Assembly Data" on page 401) used to extract an Eden module
from the library for editing or printing.
Full List / Sub-string You can set the toggle at the bottom of the form to determine the
assembly data tables to be listed.
Full List lists all the assembly definitions in the Assembly Library.
Sub-string limits the list to those files which contain a specified substring.
Create Library
This option is used to create a new Piping Assembly Library. It automatically creates the object
library (.l) and the text library (.l.t) for the library that is being created.
The system displays the approved and unapproved Piping Assembly Library names as defined in
the RDB Management Data.
Compress
This option is used to compress the Piping Assembly library. Any tables which have been
deleted from the library will be removed.
Operating Sequence
1. Select the Create/Interactive option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for Processing
Key in the name of the PAL file or list file to be compiled and added to the active library.
The system displays the default node name and path for the location of the PAL files at the
bottom of the form.
You can use the default options or override the values for this operation.
4. Accept or Select Other Option
Accept the file to begin processing.
Operating Sequence
1. Select the Create/Batch option.
2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for Processing
Key in the name of the PAL file or list file to be compiled and added to the active library and
select Accept.
The system displays the default node name and path for the location of the PAL files at the
bottom of the form.
You can use the default values or override the values for this operation.
Operating Sequence
1. Select the Revise option.
The system displays the PAL modules in the Piping Assembly Library.
Operating Sequence
1. Select the Delete option.
The system displays the table files in the active library.
Operating Sequence
1. Select the Report option from the Data Management form.
Operating Sequence
1. Select the List option.
The system displays the PAL modules in the Piping Assembly Library.
2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.
Operating Sequence
1. Select Extract from the Data Management form.
Reference Data Conflict Report (on page 407) - Creates a report of piping or instrument
components (including piping and tubing) in any model within the project that have any
specification data that is in conflict with the appropriate Piping Commodity Data, Piping
Specialty Data, or Instrument Data of the Material Reference Database. The RDB Conflict
Report file has an extension of .rpt and is created in the model directory as
<model_number>.rpt.
Refer to the section titled Summary of Report Parameters and Discrepancy Hierarchy
found at the beginning of this chapter for information on the order of significance of reported
problems.
You should run this report when segment data or RDB data (such as in the Piping Job
Specification Database, the Piping Job Spec Tables, and the Physical Dimension Tables) have
been changed and you want to determine which components need to be reconstructed or updated
from the RDB.
Table Change Report (on page 412) - Creates a report of all piping or instrument components
(including pipes) in any model within the project that are affected by a change to a specific table
for a specific input or set of inputs. Both geometric changes as a result of revisions to dimension
tables and changes in weight data as a result of revisions to weight tables are reported. The
Table Change Report file has an extension of .tcr and is created in the model directory as
<model_number>.tcr.
If your project was created with PDS version 6.0, use the Reference Data Conflict
Report instead.
Reference Data Impact Report (on page 417) - Creates a report, based on user-defined search
criteria, of the effects of modifying individual component attributes in the current approved
RDB. The RDB Impact Report file has an extension of .imp and is created in the model
directory as <model_number>.imp.
Proposed RDB Changes Report (on page 420) - Creates a single report assessing the effect of
multiple changes in the unapproved Material Reference Database. The Proposed RDB Changes
Report file has an extension of .pcs and is created in the model directory as
<model_number>.pcs. This report does not update the model.
Scheduled Reference Data Conflict Report - This is the same report as the Reference Data
Conflict Report (on page 407) except that you can schedule the report to run on a regular basis
using Batch Services.
Field Descriptions
Report Node Specifies the node on which the summary report will be created.
Report Path Specifies the directory in which the summary report will be created.
Report Name Specifies the name that will be used for the summary report file.
Print/Delete This option deletes the summary report after it is printed. Selecting this option
activates the queue pick list which allows you to select the appropriate print queue.
Print/Save This option does not delete the summary report after it is printed. Selecting this
option activates the queue pick list which allows you to select the appropriate print queue.
Save Saves the report in the model directory, and saves the summary report in the user-
specified directory. This option does not print the summary report.
Discrepancies are reported according to the significance of the problem they represent. In all
cases, the most severe problem will be the problem that is reported. The hierarchy of the
problems reported is as follows:
1. Item not found in the spec.
2. Dimension tables have changed.
3. Discrepancy between component connect point NPD and segment NPD.
4. Discrepancy between model and RDB for any of the following attributes:
end preparation - green commodity code
pressure rating - green model code
schedule/thickness - green modifier
table suffix - green geometric industry standard
end preparation weight code
pressure rating - red fabrication category
schedule/thickness - red materials grade
table suffix - red
5. Weight tables have changed.
The Reconstruct Component command is required for any component which has geometric
type specification data revised.
The Update from Reference Database command is required for any component which has
non-geometric specification data (such as commodity code or weight table) revision.
The Re-Compute Thickness command is required for any component which has been
reported as requiring calculations as a result of changes in the material tables or thickness
tables.
You can use the Review Reference Database Revision Management Report command to
review any component in the model requiring reconstruction or an update of the specification
data as a result of changes to the Material Reference Database. This command allows you to
review any component in the model requiring reconstruction or replacement as a result of RDB
changes or deletions from the Material Reference Database. In support of this review capability,
an indexed file, the RDB Revision Management Component List, is created in the same
directory as the model with the name <model_number>.rdb. Refer to the Piping Design
Graphics Reference Guide for more information on this command.
Any component, previously reported as having required reconstructing or updating, which has
been deleted from the model, will not be included in any future reports or in the RDB Revision
Management Component List. Likewise, the RDB Revision Management Component List will
be automatically compressed as part of the report creation process.
The system will not report a component as requiring reconstruction or updating from the RDB
solely on the basis of the requirement to reconstruct flag being set for the piping segment
associated with that component. The Reference Data Conflict Report will clear the requirement
to reconstruct (or recalculate) flag if it determines there are no discrepancies for the component
associated with that piping segment.
The system will not report a component as requiring reconstruction or updating from the RDB as
the result of changing any attributes of an Implied Item.
Processing
Piping Commodities
The system extracts the following data from the model for the purpose of reading piping
commodity specification data from the Material Reference Database. This is the same data that
is used for the placement or reconstruction of a piping commodity.
piping materials class second size
commodity name option code
first size maximum temperature
The first size and second size are determined from the piping segment data and not from the
component itself.
If the piping commodity in the model is a branch that was initially placed using a branch table
from the Reference Database, the system reads the appropriate branch table from the Piping
Materials Class data to determine if there has been a change in the commodity name for the
branch. If so, this component is flagged as requiring reconstruction.
The system compares the following data for consistency between the model and the Reference
Database for piping commodities. The data which may impact the geometry and/or the
symbology in the model is designated by an asterisk.
* end preparation - green * commodity code
* pressure rating - green * model code
* schedule/thickness - green * modifier
* table suffix - green * geometric industry standard
* end preparation - red weight code
* pressure rating - red fabrication category
* schedule/thickness - red materials grade
* table suffix - red
Note that user overrides of fabrication category and schedule/thickness will not be included in
the report.
The system compares the gasket thickness for each bolted end of a piping commodity with the
gasket separation in the corresponding Piping Materials Class data. If a value is defined in the
Reference Database, the gasket thickness at the bolted end is compared with that value. If a
Gasket Separation Table name is defined, that table is used to determine a gasket separation
value for comparison with the gasket thickness at the bolted end.
When a component is placed next to an integral gasket, the gasket thickness is set to zero
in the model. As a result, the Reference Data Conflict Report may report a gasket thickness
error for such components. The report compares the component gasket thickness in the model (0)
with the component gasket thickness defined in the reference data, which may be different from
0, without considering the mating component data. Such errors should be ignored.
The system compares the NPD at each connect point of the component with the NPD of the
segment.
The system compares the schedule thickness data for a component in the model to the
corresponding data in the Material Reference Database. The comparison will consider the
following issues at a minimum:
the application of the schedule/override in the model.
changes to the value for the schedule thickness in the Piping Commodity Data within the
Material Reference Database.
changes to the joint efficiency value in the Piping Commodity Data within the Material
Reference Database.
changes to the value for the thickness equation in the Piping Materials Class Data within the
Material Reference Database.
changes to the joint efficiency value in the Piping Commodity Data within the Material
Reference Database.
changes to the value for the thickness equation in the Piping Materials Class Data within the
Material Reference Database.
changes to the Thickness Data Table or the Materials Data Table.
The RDB Conflict Report does not identify discrepancies between taps placed in the
model and the RDB Tap Properties Data tables used to place the taps.
Operating Sequence
1. Select the Reference Data Conflict Report option.
The system activates the Reference Data Conflict form.
Processing
The system performs a virtual component placement for each component in a piping model (in a
manner similar to that used by the Table Checker) to determine if that component has had any
of its geometric or weight data derived from the specified tables. The system searches all piping
and instrument components in all piping models within the project for the use of such tables and
creates a report.
In searching the model for components that have dimensional and weight data derived from the
list of revised tables, the first size and second size are determined from the components data -
not the piping segment data. This is due to the fact that reconstruction of the component will be
required, if the nominal piping diameter of any segment associated with the component differs
from the corresponding connect point size.
The contents of this report include the following data, which is sorted by the piping model
number and the line id within each piping model.
piping model number
line id
component number (if applicable)
Operating Sequence
1. Select the Table Change Report option.
The system displays a list of Physical Data Libraries.
Select the Physical Data Library to process, such as U.S. Practice, DIN, or Company
Practice and select Accept.
3. Enter Date for Search ( dd-mmm-yy )
Key in a date (such as 10-Aug-95) in the Revision Date field to list all the tables that have
been revised since the specified date.
4. Accept, Re-enter Date or Choose Extent
Set the toggle to Full List or Sub-String. For Sub-String, key in a string to limit the tables
to be listed.
THEN
Select Accept to begin processing.
The system displays a list of all dimension and weight tables (or those which match a
specified substring).
For each of the selected tables, the system displays the table data in the Table Data Display
form.
Although the performance of the Reference Data Manager in creating the report will not be
impacted by the number of dimension table entries that are to be considered for revision
management, the list of components in the model will be impacted. For example, if you
inadvertently identify entries which had not actually changed, you may create significant,
unnecessary work.
This report is based on user-defined search criteria of attributes such as piping materials class,
commodity code, commodity name, option code, maximum temperature, nominal diameter, end
preparation, schedule thickness, table suffix, and so forth. The purpose of this report is to find
which components (constrained by your search criteria) will be impacted by a change in the
attributes as they exist in the current approved RDB. The RDB Impact Report search criteria
are valid for Piping Material Class Data (pdtable_201) and Piping Component Specification
Data (pdtable_202).
The RDB Impact Report file has an extension of .imp and is created in the model directory as
<model_number>.imp. This report does not include a graphical review capability.
Example 1
As an example, assume that you want to know the impact of changing the vendor for a specific
type of valve. You could define the search criteria to find all instances of valves with that
specific geometric industry standard that would need to be reconstructed if the vendor were
changed.
Example 2
As a second example, assume that you are working with a project that uses spec A and spec B.
Both of these specs contain the value X, for the vendor of gate valves. A model has been created
that uses both spec A and B, and valves have been placed from both of these specs.
Also, assume that spec B has been modified since the valves have been placed so that the vendor
in spec B now has a value of Y (instead of X), and the model has not been updated to reflect this
spec change.
If the Reference Data Impact Report was run now to determine the impact of changing the
vendor X, the system would scan the RDB for all occurrences of vendor X (which, at this time,
would be only those placed from spec A), check the portions of the design you specified for
occurrences of vendor X, then report the matching occurrences back to you.
The resulting report would not list those valves from vendor X that were placed from spec B,
because the occurrences of those valves in the model did not match the occurrences in the RDB
(due to the model not being updated after the spec change).
Operating Sequence
1. Select the Reference Data Impact Report command from the Reference Data Revision
Manager form.
The system activates the Search Criteria form, which prompts you to select the attribute to
be restricted.
2. Select Attribute
Select the attribute to be restricted.
After selecting attribute from the attribute display list, the system displays the selected
attribute in a separate field and displays a list of operators.
3. Select Operator
Select an operator to define the search criteria.
The system displays the selected operator and prompts you to key in an attribute value.
4. Enter Attribute Value
Key in the attribute value. For a sub-string search, key in a string to appear anywhere within
the attribute value (do not use wild cards).
If the attribute is code-listed, the system displays a list of values from the Standard Note
Library.
5. Select the value and select Accept.
The system validates the input and displays the defined search criteria in the Search
Criteria display field.
7. Revise the search criteria, if necessary, using the Revise Search Criteria option.
OR
Select the extent of the project to be processed.
Project Process all piping models for the entire project.
Piping Design Area Process the selected piping design areas.
Models Process the selected models within a selected design area.
8. You can key in changes to the Report Node, Report Path, and Report Name for the
summary report output or use the default location and name.
The default location for the summary report is determined by the Report Management
Data of the Report Manager.
9. Select the desired output method for the summary report: Print/Delete, Print/Save, or Save.
If you will be printing the summary report, select a queue from the pick list.
Piping Commodities
The system extracts the following data from the model for the purpose of reading piping
commodity specification data from the Material Reference Database. This is the same data that is
used for the placement or reconstruction of a piping commodity.
piping materials class second size
commodity name option code
first size maximum temperature
The first size and second size are determined from the piping segment data and not from the
component itself.
If the piping commodity in the model is a branch that was initially placed using a branch table
from the Reference Database, the system reads the appropriate branch table from the Piping
Materials Class data to determine if there has been a change in the commodity name for the
branch. If so, this component is flagged as requiring reconstruction.
The system compares the following data for consistency between the model and the Reference
Database for piping commodities. The data which may impact the geometry and/or the
symbology in the model is designated by an asterisk.
* end preparation - green * commodity code
* pressure rating - green * model code
* schedule/thickness - green * modifier
* table suffix - green * geometric industry standard
* end preparation - red weight code
* pressure rating - red fabrication category
* schedule/thickness - red materials grade
* table suffix - red
Note that user overrides of fabrication category and schedule/thickness will not be included in
the report.
The system compares the gasket thickness for each bolted end of a piping commodity with the
gasket separation in the corresponding Piping Materials Class data. If a value is defined in the
Reference Database, the gasket thickness at the bolted end is compared with that value. If a
Gasket Separation Table name is defined, that table is used to determine a gasket separation
value for comparison with the gasket thickness at the bolted end.
The system compares the specification data for any connect point of a piping commodity which
has been designated as a tap with the appropriate data (either the specification data from the Tap
Properties Data in the Reference Database or from another connect point.
The system compares the NPD at each connect point of the component with the NPD of the
segment.
The system compares the schedule thickness data for a component in the model to the
corresponding data in the Material Reference Database. The comparison will consider the
following issues at a minimum:
the application of the schedule/override in the model.
changes to the value for the schedule thickness in the Piping Commodity Data within the
Material Reference Database.
changes to the joint efficiency value in the Piping Commodity Data within the Material
Reference Database.
changes to the value for the thickness equation in the Piping Materials Class Data within the
Material Reference Database.
changes to the Thickness Data Table or the Materials Data Table.
Refer to the section titled Summary of Report Parameters and Discrepancy Hierarchy
found at the beginning of this chapter for information on the order of significance of reported
problems.
The system compares the red specification data in the Reference Database with all connect
points, if any, which are designated as having red connect point properties.
The system compares the schedule thickness data for a component in the model to the
corresponding data in the Material Reference Database. The comparison will consider the
following issues at a minimum:
the application of the schedule/override in the model.
changes to the value for the schedule thickness in the Piping Commodity Data within the
Material Reference Database.
changes to the joint efficiency value in the Piping Commodity Data within the Material
Reference Database.
changes to the value for the thickness equation in the Piping Materials Class Data within the
Material Reference Database.
changes to the Thickness Data Table or the Materials Data Table.
Operating Sequence
1. Select the Proposed RDB Changes Report option.
The system activates the Proposed RDB Changes form.
3. You can key in changes to the Report Node, Report Path, and Report Name for the
summary report output or use the default location and name.
The default location for the summary report is determined by the Report Management
Data of the Report Manager.
4. Select the desired output method for the summary report: Print/Delete, Print/Save, or Save.
If you will be printing the summary report, select a queue from the pick list.
5. Accept to Submit Job, Restart or Exit
Set the toggle to Submit Immediately or select Delayed Submit and fill in the day and time
to process the request.
6. Select Accept to submit the request for processing.
The system submits the request to the batch queue PDreport. It updates the batch log file
periodically to include a list of piping models which have been processed. The proposed
RDB changes report file has an extension of .pcs and is created in the model directory as
<model_number>.pcs. If the summary report is printed as a result of creating this report,
this report will also be printed.
Reference Data Conflict Report (on page 407)
Proposed RDB Changes Report (on page 420)
Operating Sequence
1. Execute the command by double-clicking on the Verify RDB Library icon in the PD_Shell
program group.
The system activates the Reference Database Library Verification Utility form, and prompts
you to select the appropriate project number from the list.
2. Select the desired project number, and then select the Verify Reference Database Library
command.
The system begins the verification process and displays the Verifying RDB Library Files
message. When processing is complete, the system returns a message similar to the one
shown below:
A typical output file has been excerpted below. No errors were found in this example.
Opening : /onneso3a/rdb/lib/approved/618pjstb.l
header number keys = 234
tree number keys = 234
Opening : /onneso3a/rdb/lib/approved/618pjstb.l.t
header number keys = 234
tree number keys = 234
Opening : /onneso3a/rdb/lib/approved/618pjstb.l.r
header number keys = 234
tree number keys = 234
Opening : /onneso3a/rdb/lib/approved/618shbom.l
header number keys = 2877
tree number keys = 2877
Opening : /onneso3a/rdb/lib/approved/618lgbom.l
header number keys = 2629
tree number keys = 2629
Opening : /onneso3a/rdb/lib/approved/618spbom.l
Empty file, no keys.
Opening : /onneso3a/rdb/lib/approved/618note.l
header number keys = 4162
tree number keys = 4162
Opening : /onneso3a/rdb/lib/approved/618note.l.t
header number keys = 65
tree number keys = 65
Counting implied keys for code31
Counting implied keys for code35
Counting implied keys for code36
Counting implied keys for code37
Counting implied keys for code50
Counting implied keys for code69
Counting implied keys for code125
.
.
.
Counting implied keys for code2000
Opening : /onneso3a/rdb/lib/approved/618label.l
header number keys = 217
tree number keys = 217
Opening : /onneso3a/rdb/lib/approved/618assem.l
header number keys = 110
tree number keys = 110
Opening : /onneso3a/rdb/lib/approved/618assem.l.t
header number keys = 110
tree number keys = 110
Opening : /onneso3a/rdb/lib/approved/618gcom.l
header number keys = 1509
tree number keys = 1509
Opening : /onneso3a/rdb/lib/approved/618gcom.l.t
header number keys = 1509
tree number keys = 1509
Opening : /onneso3a/rdb/lib/approved/618pcdim.l
header number keys = 4820
tree number keys = 4820
Opening : /onneso3a/rdb/lib/approved/618pcdim.l.t
header number keys = 4820
tree number keys = 4820
Opening : /onneso3a/rdb/lib/approved/618pcdim.l.r
header number keys = 4820
tree number keys = 4820
Total files with errors : 0
Appendix: Codelists
This section details the codelists used in PDS.
The data contained within this appendix is for informational purposes only and may not
exactly match the codelists delivered with the product.
General Comments
Codelist sets in this document define the values for all codelisted attributes used in the PDS
Piping Task which are specific to US plant design practices.
You can add, delete, or revise codelist sets to reflect your own practices, terminology, and
language. A task user, however, cannot revise a codelist set from a work session. Revisions to a
codelist set, can only be made in the General RDB or Standard Note Library.
In listings that follow, the maximum number of entries that may be expected for a specific
codelist set is shown in parentheses following the name of the codelist set.
For PDS users that wish to modify codelist files delivered with the PDS software to reflect their
own practices, two approaches are possible:
Make the modifications within the range of codelist numbers defined in the codelist library
delivered with the PDS software. This has the advantage of resulting in the best organized
set of codelisted definitions. The disadvantage is that numbers added by the user may
conflict with numbers added in future versions of software.
Increase the maximum number of entries allowed for the codelist set and make additions to
it in the range of extended numbers. This will minimize possible conflicts assigned numbers
but will require compiling of the codelists and of the associated databases.
Values enclosed in brackets [ ] in pages that follow represent descriptive information. The
values stored in the codelist sets will exclude this bracketed information from the codelist
descriptions.
The net length of a codelist entry cannot exceed 50 characters. Other considerations may,
however, require that a shorter description be made. For example:
For the P&ID Task, the total compressed length of a label part can not exceed 36 characters.
The formats of specification type reports for the Instrument Task require that applicable
codelist descriptions do not exceed 25 characters.
Codelist no This is the number that defines a specific unit of measure within
a codelist set. For example, codelist number 1 in codelist set
1028 refers to the "lb" units of measure.
Unit type This code is not explicitly shown in the tables. The unit type
equals the number of the codelist set minus 1000. For example,
reference to unit type 28 refers to "mass".
Quantity name Entries in this column define the quantity whose units of
measure are being defined.
Unit name Several unit names are provided for a given codelist set. Any of
these names can be used to define the quantity.
Conversion to destination Two sets of columns define the conversion of variables
unit expressed in the units shown under the column "Unit Name" to
the unit shown under the column "Destination Unit". The
following explanations apply:
The column captioned Destination Unit defines the unit to
which the unit included under the column Unit Name will be
converted using the value shown under the column Factor.
The column captioned Factor provides the actual conversion
factor to be used for the conversion. For example, in codelist
set 1028, to convert a mass measurement in "lb" to "kg",
multiply the value in the former units by the conversion
factor, 4.535 924 E-01. In some cases, such as temperature,
summation may also be required to effect the desired
conversion. All conversion factors are taken or derived from
API Publication 2564. Groups of three digits are separated
by spaces with no commas. For example,
3.048 000 E-01 = 3.048 000 x 10-1 = 0.3048000.
Similarly,
9.290 304 E+02 = 9.290 304 x 102 = 929.0304.
An asterisk (*) indicates that all following digits are zeros. If a
conversion factor happens to end in several zeros but does not
have an asterisk, any subsequent digits would not necessarily be
zeros. Most of the conversion factors are shown to six or seven
significant figures. Those shown to fewer than six significant
figures are limited by the precision of the known or
determinable value of a physical property, such as the density of
distilled water at a reference temperature.
Conversion to first unit in Two sets of columns define the conversion of the units shown
CL under the column Unit Name to the first unit shown in that
column. The conversion is done per the equation:
y= A + Bx
where,
x applies to the value of the variable expressed in the units
shown in the column captioned Unit Name.
y applies to the value of the variable expressed in the units
shown in the first line of the column captioned Unit Name.
A is the factor in the column captioned Factor A.
B is the factor in the column captioned Factor B.
The distinction between upper case and lower case symbols is very important. For example:
K= kelvin
k= kilo= 103
M= mega= 106
m= milli= 10-3 (when m is used as a prefix)
m= metre (when m is used alone)
N= newton
n= nano= 10-9
In editing any of the codelist sets for units, do not change the meaning of existing codelist
values.
In all codelist sets for units, a blank space is provided as the first character in the unit name. The
blank space is used to silence the units in the formation of labels.
Nomenclature:
g gram mass
kg kilogram mass
m metre length
Pa pascal pressure
0= New
1 = Existing
2 = Future
3 = User 1
4 = User 2
1 = New
2 = Existing
3 = Dismantle
4 = Future
1 = NH=Not held
2 = H =Hold
1 = A= All
2 = B= Vessels
3 = C= Heat transfer
4 = D= Mechanical
5 = E= Civil/Structural
6 = F= Piping
7 = H= Electrical
8 = I= Other
11 = A [Air]
14 = AC [Combustion air]
17 = AE [Aeration air]
20 = AI [Instrument air]
23 = AO [Operational air]
26 = AP [Plant air]
29 = APU [Purge air]
32 = AR [Regeneration air]
35 = AS [Starting air]
40 = AZ [Other air]
71 = C [Refrigerant]
75 = CA [Ammonia refrigerant]
79 = CE [Ethylene refrigerant]
83 = CF [Freon refrigerant]
87 = CLP [LP refrigerant]
91 = CPR [Propylene refrigerant]
100 = CZ [Other refrigerant]
101 = D [Sewer]
103 = DC [Caustic sewer]
105 = DCH [Chemical sewer]
107 = DGR [Drain to grade]
109 = DOW [Oily water sewer]
111 = DP [Process sewer]
113 = DPH [Heated process sewer]
115 = DS [Sanitary sewer]
117 = DSP [Press sanitary sewer]
119 = DST [Storm sewer]
121 = DW [Clean water sewer]
123 = DWS [Sour water sewer]
125 = DX [Acid sewer]
127 = [Blank] [Storm, oily water or sanitary sewer]
128 = [Blank] [Storm or oily water sewer]
130 = DZ [Other sewer]
161 = F [Foam]
191 = G [Gas]
194 = GCD [Carbon dioxide gas]
197 = GCL [Chlorine gas]
198 = GCN [Chlorination gas]
200 = GF [Fuel gas]
203 = GG [Flue gas]
206 = GH [Hydrogen gas]
209 = GHS [Hydrogen sulphide gas]
341 = K [Solvent]
346 = KG [Glycol]
351 = KF [Furfural]
356 = KD [Dewaxing]
370 = KZ [Other solvent]
401 = M [Chemical]
402 = [Blank] [Chemical injection]
405 = MAA [Anhydrous ammonia]
409 = MAC [Aluminum chloride]
413 = MAW [Aqueous ammonia]
417 = MC5 [0-50% caustic solution]
421 = MCL [Dry chlorine]
425 = MEO [Ethylene oxide]
429 = MHC [Hydrogen chloride]
433 = MIA [Inhibitor A]
434 = MIB [Inhibitor B]
440 = MLA [Lube oil additives]
444 = MMA [Methyl alcohol]
448 = MS [Sulfur]
452 = MSL [Liquid sulfur]
460 = MZ [Other chemical]
491 = O [Oil]
493 = OD [Diesel fuel oil]
495 = ODS [Dry slop oil]
497 = OF [Flushing oil]
499 = OFR [Fuel oil return]
500 = OFS [Fuel oil supply]
503 = OH [Hydraulic oil]
505 = OL [Lube]
507 = OLS [Lube and seal oil]
509 = OS [Seal oil]
511 = OSO [Sour oil]
513 = OSW [Sweet oil]
515 = OWS [Wet slop oil]
520 = OZ [Other oil]
521 = P [Process]
522 = [Blank] [Special process]
524 = PA [Process w/ rich/lean amine]
527 = PAS [Process w/ severe amine]
530 = PB [Process w/ benzene]
533 = PH [Process w/ H2]
536 = PHH [Process w/ H2 & H2S]
539 = PHW [Process w/ aqueous H2S]
542 = PL [Low temperature process]
545 = PS [Process w/ S]
550 = PZ [Other process]
611 = S [Steam]
613 = [Blank] [Boiler feed water or steam]
615 = [Blank] [Boiler feed water, steam or condensate]
617 = [Blank] [Steam or condensate]
621 = SE [Extr press CL1500 steam]
623 = SH [High press CL900 steam]
625 = SL [Low press CL150 steam]
627 = SM [Med press CL600 steam]
629 = SN [Nor press CL300 steam]
631 = SS [Superheated steam]
633 = SV [Vacuum steam]
635 = SX [Exhaust CL125 steam]
640 = SZ [Other steam]
721 = V [Vent]
731 = VA [Vent to atmosphere]
741 = VF [Vent to flare]
750 = VZ [Other vent]
751 = W [Water]
753 = WB [Boiler feed water]
755 = WBA [Ballast water]
757 = WBB [Water boiler blowdown]
759 = WC [Cooling water]
761 = [Blank] [Cooling or utility water]
763 = WCH [Chlorinated water]
764 = WCL [Chlorine in water]
765 = WCF [Clarified water]
831 = X [Acid]
835 = XH [Hydrofluoric acid]
839 = XN [Nitric acid]
843 = XSD [Dilute sulfuric acid]
847 = XS3 [30% sulfuric acid]
851 = XS8 [75-80% sulfuric acid]
853 = XS9 [93-97% sulfuric acid]
860 = XZ [Other acid]
861 = Y [Catalyst]
865 = YA [Catalyst addition]
869 = YG [General catalyst]
873 = YH [Catalyst w/ H2]
877 = YL [Catalyst lift lines]
881 = YW [Catalyst withdrawal lines]
890 = YZ [Other catalyst]
1 = [Blank]
2 = New
3 = Existing
4 = Revamp
5 = Relocate
6 = Temporary
7 = Dismantle
8 = Future
1 = [Blank]
Irons, 10-99
10 = A47-32510
12 = A47-35018
15 = A48-20
16 = A48-25
17 = A48-30
18 = A48-35
19 = A48-40
20 = A48-45
21 = A48-50
22 = A48-55
23 = A48-60
25 = A74
30 = A126-A
31 = A126-B
32 = A126-C
35 = A197
40 = A278-20
41 = A278-25
42 = A278-30
43 = A278-35
44 = A278-40
45 = A278-50
46 = A278-60
47 = A278-70
48 = A278-80
55 = A338
60 = A395-Ductile
62 = A395-Ferritic Ductile
70 = A571
75 = AWWA-C110-Ductile
76 = AWWA-C151-Ductile
242 = A211-A570-36
243 = A211-A570-40
244 = A211-A570-45
245 = A211-A570-50
250 = A216-WCA
252 = A216-WCB
254 = A216-WCC
264 = A234-WPB
266 = A234-WPC
270 = A283-A
272 = A283-B
274 = A283-C
276 = A283-D
280 = A285-A
282 = A285-B
284 = A285-C
290 = A333-1
293 = A333-6
295 = A334-1
298 = A334-6
300 = A350-LF1
302 = A350-LF2
305 = A352-LCB
310 = A369-FPA
312 = A369-FPB
320 = A381-Y35
321 = A381-Y42
322 = A381-Y46
323 = A381-Y48
325 = A381-Y50
327 = A381-Y52
334 = A420-WPL6
340 = A515-55
342 = A515-60
344 = A515-65
346 = A515-70
350 = A516-55
352 = A516-60
354 = A516-65
356 = A516-70
360 = A520-30
361 = A520-33
362 = A520-36
363 = A520-40
364 = A520-45
365 = A520-50
370 = A524-I
372 = A524-II
375 = A537-CL1
380 = A587
390 = A671-CA55
392 = A671-CB60
394 = A671-CB65
396 = A671-CB70
398 = A671-CC60
400 = A671-CC65
402 = A671-CC70
404 = A671-CD70
406 = A671-CE55
408 = A671-CE60
410 = A671-CK75
420 = A672-A45
422 = A672-A50
424 = A672-A55
426 = A672-B55
428 = A672-B60
430 = A672-B65
432 = A672-B70
434 = A672-C55
436 = A672-C60
438 = A672-C65
440 = A672-C70
442 = A672-D70
444 = A672-E55
446 = A672-E60
448 = A672-N75
460 = A691-CMS75
464 = A691-CMSH70
582 = A217-WC1
584 = A217-WC4
586 = A217-WC5
588 = A217-WC6
590 = A217-WC9
600 = A225-A
602 = A225-B
610 = A234-WP1
614 = A234-WP5
616 = A234-WP7
618 = A234-WP9
620 = A234-WP11
622 = A234-WP12
624 = A234-WP22
630 = A302-A
632 = A302-B
634 = A302-C
636 = A302-D
644 = A333-3
646 = A333-4
648 = A333-7
650 = A333-8
652 = A333-9
664 = A334-3
666 = A334-7
668 = A334-8
670 = A334-9
680 = A335-P1
682 = A335-P2
684 = A335-P5
686 = A335-P5b
687 = A335-P5c
690 = A335-P7
692 = A335-P9
694 = A335-P11
696 = A335-P12
698 = A335-P15
700 = A335-P21
702 = A335-P22
710 = A350-LF3
720 = A352-LC1
722 = A352-LC2
724 = A352-LC3
730 = A353
740 = A369-FP1
742 = A369-FP2
744 = A369-FP3b
746 = A369-FP5
748 = A369-FP7
750 = A369-FP9
752 = A369-FP11
754 = A369-FP12
756 = A369-FP21
758 = A369-FP22
1044 = A268-TP405
1046 = A268-TP409
1048 = A268-TP410
1050 = A268-TP430
1051 = A268-TP430Ti
1054 = A268-TP443
1056 = A268-TP446
1060 = A269-TP304
1061 = A269-TP304L
1064 = A269-TP316
1065 = A269-TP316L
1066 = A270-TP316L
1070 = A312-TP304
1071 = A312-TP304H
1072 = A312-TP304L
1074 = A312-TP309
1076 = A312-TP310
1078 = A312-TP316
1079 = A312-TP316H
1080 = A312-TP316L
1082 = A312-TP317
1084 = A312-TP321
1085 = A312-TP321H
1088 = A312-TP347
1089 = A312-TP347H
1092 = A312-TP348
1095 = A351-CA15
1100 = A351-CF3
1102 = A351-CF3A
1104 = A351-CF3M
1106 = A351-CF8
1108 = A351-CF8A
1110 = A351-CF8C
1112 = A351-CF8M
1113 = A351-CF10
1114 = A351-CF10MC
1116 = A351-CN7M
1118 = A351-CH8
1120 = A351-CH10
1122 = A351-CH20
1124 = A351-CK20
1126 = A351-HK30
1128 = A351-HK40
1130 = A351-HT30
1140 = A358-304
1141 = A358-304L
1144 = A358-309S
1146 = A358-310S
1148 = A358-316
1149 = A358-316L
1152 = A358-321
1154 = A358-347
1156 = A358-348
1160 = A376-16-8-2H
1162 = A376-TP304
1163 = A376-TP304H
1166 = A376-TP316
1167 = A376-TP316H
1170 = A376-TP321
1171 = A376-TP321H
1174 = A376-TP347
1175 = A376-TP347H
1178 = A376-TP348
1179 = A376-TP348H
1190 = A403-WP304
1191 = A403-WP304H
1192 = A403-WP304L
1194 = A403-WP309
1196 = A403-WP310
1198 = A403-WP316
1199 = A403-WP316H
1200 = A403-WP316L
1202 = A403-WP317
1204 = A403-WP321
1205 = A403-WP321H
1206 = A403-WP347
1207 = A403-WP347H
1210 = A403-WP348
1220 = A409-TP304
1222 = A409-TP309
1224 = A409-TP310
1226 = A409-TP316
1228 = A409-TP317
1230 = A409-TP321
1232 = A409-TP347
1234 = A409-TP348
1240 = A430-FP304
1241 = A430-FP304H
1244 = A430-FP316
1245 = A430-FP316H
1248 = A430-FP321
1249 = A430-FP321H
1252 = A430-FP347
1253 = A430-FP347H
1260 = A451-CHP10
1262 = A451-CHP20
1264 = A451-CPF8C
1266 = A451-CPF8M
1268 = A451-CPF10MC
1270 = A451-CPH8
1272 = A451-CPK20
1280 = A452-TP304H
1282 = A452-TP316H
1284 = A452-TP347H
1300 = ASME SA479-316L
Gaskets 3000-3999]
3051 = G51 [Flat, org fib, nitrile binder]
3052 = G52 [Flat, org fib, nitrile binder, full face]
3076 = G76 [Flat, graph]
3077 = G77 [Flat, graph, full face]
3078 = G78 [Flat, graph, 304 tang reinf]
3079 = G79 [Flat, graph, 304 wire mesh reinf]
3101 = G101 [Flat, asb]
3102 = G102 [Flat, asb, full face]
3103 = G103 [Flat, asb, wire mesh reinf]
3111 = G111 [Flat, blue-asb]
3112 = G112 [Flat, blue-asb, full face]
Bolting 4000-4999]
4011 = B11 [A193-B5, >=1.5" lub, w/A194-3]
4012 = B12 [A193-B5, lub, w/A194-3]
4014 = B14 [A193-B5, >=1.5" lub, w/A194-4]
4015 = B15 [A193-B5, lub, w/A194-4]
4021 = B21 [A193-B6, >=1.5" lub, w/A194-6]
4022 = B22 [A193-B6, lub, w/A194-6]
4031 = B31 [A193-B7, >=1.5" lub, w/A194-2H]
4032 = B32 [A193-B7, lub, w/A194-2H]
4033 = B33 [A193-B7 zinc coated w/A194-2H zinc coated]
4035 = B35 [A193-B7 galv w/A194-2H galv]
4038 = B38 [A193-B7M, >=1.5" lub, w/A194-2H]
4039 = B39 [A193-B7M, lub, w/A194-2H]
4041 = B41 [A193-B8 Cl.1, >=1.5" lub, w/A194-8]
4042 = B42 [A193-B8 Cl.1, lub, w/A194-8]
4044 = B44 [A193-B8C Cl.1, >=1.5" lub, w/A194-8C]
4500 = Undefined
6316 = BS1501-622-690
6317 = BS1501-660
6318 = BS1501-503
6319 = BS1501-510
6320 = BS1501-828
6373 = BS1501-316S62B
6374 = BS1501-316S66B
6375 = BS1501-316S82B
6376 = BS1501-460S52A LT70
6536 = BS1504-629A
6537 = BS1504-660A
6538 = BS1504-420C29A
6539 = BS1504-425C11A
6540 = BS1504-304C15A
6541 = BS1504-304C15A-LT196
6542 = BS1504-304C12A
6543 = BS1504-304C12A-LT196
6544 = BS1504-347C17A
6545 = BS1504-347C17A-LT196
6546 = BS1504-315C16A
6547 = BS1504-315C16A-LT196
6548 = BS1504-316C12A
6549 = BS1504-316C16A
6550 = BS1504-316C71A
6551 = BS1504-318C17A
6552 = BS1504-316C16E
6553 = BS1504-316C71E
6554 = BS1504-316C12A-LT196
6555 = BS1504-316C16A-LT196
6556 = BS1504-316C71A-LT196
6557 = BS1504-317C12A
6558 = BS1504-317C16A
6559 = BS1504-364C11A
6560 = BS1504-332C11A
6561 = BS1504-310C40A
6562 = BS1504-330C11A
6595 = BS1506-286S31-LT196
6596 = BS1506-304S31
6597 = BS1506-304S31-LT196
6598 = BS1506-304S51
6599 = BS1506-304S61
6600 = BS1506-304S61-LT196
6601 = BS1506-304S71
6602 = BS1506-304S71-LT196
6603 = BS1506-303S22
6604 = BS1506-316S31
6605 = BS1506-316S31-LT196
6606 = BS1506-316S33
6607 = BS1506-316S33-LT196
6608 = BS1506-316S51
6609 = BS1506-316S53
6610 = BS1506-316S61
6611 = BS1506-316S61-LT196
6612 = BS1506-316S63
6613 = BS1506-316S63-LT196
6614 = BS1506-316S65
6615 = BS1506-316S65-LT196
6616 = BS1506-316S67
6617 = BS1506-316S67-LT196
6618 = BS1506-321S31
6619 = BS1506-321S31-LT196
6620 = BS1506-321S51-490
6621 = BS1506-321S51-520
6622 = BS1506-347S31
6623 = BS1506-347S31-LT196
6624 = BS1506-347S51
7999 = undefined
Carbon Steels, C
14 = [CAA5UA] [AC0014] CL125 FFFE, CS, Brnz Trim
16 = [CAA5VA] [AC0016] CL125 FFFE, Brnz Trim
19 = [CAALV1] [1C0019] CL150 FFFE, CS Cement Lined
31 = [CAC5C1] [1C0031] CL150 RFFE, CS, Trim 8
Stainless Steels, S
3977 = [SAC3T1] [1S3977] CL150 RFFE, 304/CS Valves, Trim 8
3978 = [SAC3T2] [2S3978] CL300 RFFE, 304/CS Valves, Trim 8
3979 = [SAC3T4] [4S3979] CL600 RFFE, 304/CS Valves, Trim 8
3980 = [SAC3T5] [5S3980] CL900 RFFE, 304/CS Valves, Trim 8
3984 = [SAD3C1] [1S3984] CL150 RFFE, 304/316 Valves, Trim 12
3985 = [SAD3C2] [2S3985] CL300 RFFE, 304/316 Valves, Trim 12
3988 = [SAD3E1] [1S3988] CL150 RFFE, 304, Trim 2
3989 = [SAD3E2] [2S3989] CL300 RFFE, 304, Trim 2
3991 = [SAD3F1] [1S3991] CL150 RFFE, 304, Trim 2
4104 = [SAFYG1] [1S4104] CL150 RFFE, 304, 316 Trim
4218 = [SAM3T6] [6S4218] CL1500 RJFE, 304/CS Valves, Trim 8
4396 = [SBD3C2] [2S4396] CL300 RFFE, 304L/316 Valves, Trim 12
4488 = [SBF3U1] [1S4488] CL150 RFFE, 304/316 Valves, Trim 2
5135 = [SED5C1] [1S5135] CL150 RFFE, 316, Trim 12
5187 = [SEF3C1] [1S5187] CL150 RFFE, 316, Trim 12
5188 = [SEF3C2] [2S5188] CL300 RFFE, 316, Trim 12
5189 = [SEF3C4] [4S5189] CL600 RFFE, 316, Trim 12
5197 = [SEF3G1] [1S5197] CL150 RFFE, 316, Trim 12
6246 = [SHJ3B2] [2S6246] CL300 RFFE-SF, 321/347 Valves, 347HF Trim
6247 = [SHJ3B4] [4S6247] CL600 RFFE-SF, 321/347 Valves, 347HF Trim
6258 = [SHJ5B2] [2S6258] CL300 RFFE-SF, 321/347 Valves, 347HF Trim
6449 = [SHV3B5] [5S6449] CL900 BE/RFFE-SF, 321/347 Valves, 347HF Trim
6450 = [SHV3B6] [6S6450] CL1500 BE/RJFE, 321/347 Valves, 347HF Trim
6457 = [SHV5B6] [6S6457] CL1500 BE/RJFE, 321/347 Valves, 347HF Trim
Copper Alloys, K
Nickel Alloys, N
7540 = [NGF5G1] [1N7540] CL150 RFFE, Inconel 600, Inconel Trim
Aluminum Alloys, A
Other Materials, X
7687 = [XCY1W8] [8X7687] Gravity Head, Vitrified Clay
7689 = [XEY1W8] [8X7689] Gravity Head, Reinforced Concrete
7733 = [XTY1U9] [9X7733] SCH-80, SE, PVC
9999 = Undefined
A.......materials group
B.......materials type
C.......detail features
D.......corrosion allowance or type of lining
E.......service description
F.......pressure rating
F.......pressure rating
A.......material group
XXX.....sequence number from list in 2090-41-SN
Carbon Steels, C
A= CS
D= CS, galvanized
G= CS, jacketed
J= CS, killed
M= CS, killed, jacketed
P= CS, low temp
X= Other 1
Y= Other 2
Z= Other 3
N= 1Cr-0.5Mo
P= 1.25Cr-0.5Mo
Q= 2Cr-0.5Mo
R= 2.25Cr-1Mo
S= 3Cr-1Mo
T= 5Cr-0.5Mo
U= 7Cr-0.5Mo
V= 9Cr-1Mo
X= Other 1
Y= Other 2
Z= Other 3
Stainless Steels, S
A= 304
B= 304L
C= 304H
D= 310
E= 316
F= 316L
G= 316H
H= 321
J= 321H
K= 410S
L= CHP10
M= CHP20
N= CPF10MC
O= CPH8
P= CPK20
Q= UNS S31200
R= UNS S31250
S= UNS S31500
T= UNS S31803
U= UNS S32304
V= UNS S32550
W= Alloy 20
X= Other 1
Y= Other 2
Z= Other 3
Copper Alloys, K
A= Brass
F= Bronze
K= Copper
P= 90Cu-10Ni
R= 70Cu-30Ni
X= Other 1
Y= Other 2
Z= Other 3
Nickel Alloys, N
A= Low C Ni
D= Monel
E= K-Monel
F= R-Monel
G= Inconel 600
H= Inconel 601
J= Inconel 625
L= Incoloy 800
M= Incoloy 800H
N= Incoloy 801
P= Incoloy 802
Q= Incoloy 825
T= Hastelloy B
U= Hastelloy C
V= Hastelloy G
X= Other 1
Y= Other 2
Z= Other 3
Aluminum Alloys, A
C= 3002 aluminum
D= 3003 aluminum
E= 3004 aluminum
F= 5050 aluminum
G= 5052 aluminum
Q= 6061 aluminum
R= 6063 aluminum
S= Alclad
X= Other 1
Y= Other 2
Z= Other 3
Other Materials, X
A= Asbestos cement
B= Borosilicate glass
C= Clay, vitrified
D= Concrete, prestressed
E= Concrete, reinforced
F= CPVC
G= Epoxy/Glass fib
J= Furan/Carbon
K= Furan/Glass fib
L= Kynar
N= Nylon
P= Polyester/Glass fib
Q= Polyethylene, high dens
R= Polyethylene, low dens
S= Polypropylene
T= PVC
U= Teflon
V= Titanium
W= Zirconium
X= Other 1
Y= Other 2
Z= Other 3
1= None
2= 0.020"
3= 0.030"
4= 0.050"
5= 0.063"
6= 0.10"
7= 0.125"
8= 0.188"
9= 0.250"
A= 405 clad
B= 410S clad
C= 304 clad
D= 304L clad
E= 316 clad
F= 316L clad
G= 317 clad
H= 317L clad
J= 321 clad
L= Cement lined
M= Epoxy lined
N= Glass lined
O= Kynar lined
P= Polyester lined
Q= Polypropylene lined
R= PTFE lined
S= Saran lined
T= Teflon lined
U= TK31 lined
V= R11 lined
W= R15 lined
X= R18 lined
Y= Other 1
Z= Other 2
1= CL150
2= CL300
3= CL400
4= CL600
5= CL900
6= CL1500
7= CL2500
8= GRAVHD
9= OTHER
A= CL125
F= CL800
G= CL2000
H= CL3000
J= CL4500
K= CL5000
L= CL6000
M= CL9000
N= CL10000
R= CL15000
T= CL20000
V= CL30000
1 = [Blank]
5 = CSSF, Contractor supplied, shop fabricated
7 = CSFF, Contractor supplied, field fabricated
15 = SSSF, Shop supplied, shop fabricated
17 = SSFF, Shop supplied, field fabricated
25 = FSSF, Field supplied, shop fabricated
27 = FSFF, Field supplied, field fabricated
35 = ASSF, A supplied, shop fabricated
37 = ASFF, A supplied, field fabricated
45 = BSSF, B supplied, shop fabricated
47 = BSFF, B supplied, field fabricated
95 = OSSF, Owner supplied, shop fabricated
97 = OSFF, Owner supplied, field fabricated
1 = [Blank]
2 = NT [Not heat traced]
3 = HT [Heat traced]
4 = PHT [Partially heat traced]
2 = FE [Flanged end]
Use 11-15 for ends without integral gaskets; 16-19 for ends with
integral gaskets.
10 = FFTP (11-19) [Flat-face flanged termination type]
11 = FFFE [Flat-face flanged end]
16 = FFFEWG [Flat-face flanged end with integral gasket]
Use 21-25 for ends without integral gaskets; 26-29 for ends with
integral gaskets.
20 = RFTP (21-29) [Raised-face flanged termination type]
21 = RFFE [Raised-face flanged end]
26 = RFFEWG [Raised-face flanged end with integral gasket]
Use 31-35 for ends without integral gaskets; 36-39 for ends with
integral gaskets.
30 = RJFTP (31-39) [RTJ-face flanged termination type]
31 = RJFE [RTJ-face flanged end]
Use 41-45 for ends without integral gaskets; 46-49 for ends with
integral gaskets.
40 = TMFTP (41-49) [Tongue/male-face flanged termination type]
41 = STFE [Small-tongue-face flanged end]
42 = LTFE [Large-tongue-face flanged end]
43 = SMFE [Small-male-face flanged end]
44 = LMFE [Large-male-face flanged end]
Use 51-55 for ends without integral gaskets; 56-59 for ends with
integral gaskets.
50 = GFFTP (51-59) [Groove/female-face flanged termination type]
51 = SGFE [Small-groove-face flanged end]
52 = LGFE [Large-groove-face flanged end]
53 = SFFE [Small-female-face flanged end]
54 = LFFE [Large-female-face flanged end]
Use 61-65 for lap-flanged ends without integral gaskets; 66-69 for
lap-flanged ends with integral gaskets.
60 = FFLFTP (61-69) [Flat-face lap-flanged termination type]
61 = FFLFE [Flat-face lap-flanged end]
Use 71-75 for lap-flanged ends without integral gaskets; 76-79 for
lap-flanged ends with integral gaskets.
70 = RFLFTP (71-79) [Raised-face lap-flanged termination type]
71 = RFLFE [Raised-face lap-flanged end]
Use 81-85 for lap-flanged ends without integral gaskets; 86-89 for
lap-flanged ends with integral gaskets.
80 = RJFLFTP (81-89) [RTJ-face lap-flanged termination type]
81 = RJLFE [RTJ-face lap-flanged end]
Use 91-95 for lap-flanged ends without integral gaskets; 96-99 for
lap-flanged ends with integral gaskets.
90 = TMFLFTP (91-99) [Tongue/male-face lap-flanged termination
type]
91 = STLFE [Small-tongue-face lap-flanged end]
92 = LTLFE [Large-tongue-face lap-flanged end]
93 = SMLFE [Small-male-face lap-flanged end]
94 = LMLFE [Large-male-face lap-flanged end]
Use 111-115 for ends without integral gaskets; 116-119 for ends
with integral gaskets.
110 = FFTBTP (111-119)[Flat-face thru-bolted termination type]
111 = FFTBE [Flat-face thru-bolted end]
116 = FFTBEWG [Flat-face thru-bolted end with integral
gasket]
Use 121-125 for ends without integral gaskets; 126-129 for ends
with integral gaskets.
120 = RFTBTP (121-129)[Raised-face thru-bolted termination type]
121 = RFTBE [Raised-face thru-bolted end]
Use 131-135 for ends without integral gaskets; 136-139 for ends
with integral gaskets.
130 = RJTBTP (131-139)[RTJ-face thru-bolted termination type]
131 = RJTBE [RTJ-face thru-bolted end]
Use 141-145 for ends without integral gaskets; 146-149 for ends
with integral gaskets.
140 = MRJTBTP (141-149)[Male RTJ-face thru-bolted termination type]
146 = MRJTBEWG [Male RTJ-face thru-bolted end with integral
gasket]
Use 151-155 for ends without integral gaskets; 156-159 for ends
with integral gaskets.
150 = FFTBCSTP (151-159)[Flat-face thru-bolted-with-cap-screws
termination ty
151 = FFTBCSE [Flat-face thru-bolted-with-cap-screws end]
156 = FFTBCSEWG [Flat-face thru-bolted-with-cap-screws end
with integ
Use 161-165 for ends without integral gaskets; 166-169 for ends
with integral gaskets.
160 = RFTBCSTP (161-169)[Raised-face thru-bolted-with-cap-screws
termination
161 = RFTBCSE [Raised-face thru-bolted-with-cap-screws end]
166 = RFTBCSEWG [Raised-face thru-bolted-with-cap-screws end
with int
Use 171-175 for ends without integral gaskets; 176-179 for ends
with integral gaskets.
170 = RJTBCSTP (171-179)[RTJ-face thru-bolted-with-cap-screws
termination typ
171 = RJTBCSE [RTJ-face thru-bolted-with-cap-screws end]
Use 181-185 for ends without integral gaskets; 186-189 for ends
with integral gaskets.
180 = FFFTBTP (181-189)[Flat-full-face thru-bolted termination type]
181 = FFFTBE [Flat-full-face thru-bolted end]
186 = FFFTBEWG [Flat-full-face thru-bolted end with integral
gasket]
1 = [Blank]
10 = .0625
11 = .125
12 = .1875
13 = .25
14 = .3125
15 = .375
16 = .4375
17 = .5
18 = .5625
19 = .625
20 = .6875
21 = .75
22 = .8125
23 = .875
24 = .9375
25 = 1
30 = 1.0625
31 = 1.125
32 = 1.1875
33 = 1.25
34 = 1.3125
35 = 1.375
36 = 1.4375
37 = 1.5
38 = 1.5625
39 = 1.625
40 = 1.6875
41 = 1.75
42 = 1.8125
43 = 1.875
44 = 1.9375
45 = 2
50 = 2.0625
51 = 2.125
52 = 2.1875
53 = 2.25
54 = 2.3125
55 = 2.375
56 = 2.4375
57 = 2.5
58 = 2.5625
59 = 2.625
60 = 2.6875
61 = 2.75
62 = 2.8125
63 = 2.875
64 = 2.9375
65 = 3
100 = S-5S
101 = S-10S
102 = S-40S
103 = S-80S
110 = S-10
111 = S-20
112 = S-30
113 = S-40
114 = S-60
115 = S-80
116 = S-100
117 = S-120
118 = S-140
119 = S-160
130 = S-STD
131 = S-XS
132 = S-XXS
0 = None
1 = reconstruct
2 = re-calculate
18 = Gate valve
117 = Flange
119 = Reducing flange
120 = Expander flange
122 = Orifice flange
124 = Blind flange
126 = Open spectacle blank
127 = Closed spectacle blank
128 = Blank disc
129 = Blind spacer
130 = Tapered spacer
909 = Anchor
911 = 1-way support
913 = 2-way support
923 = Spring support
927 = Damping support
2 = NO [Normally open]
3 = NC [Normally closed]
5 = CSO [Car seal open]
6 = CSC [Car seal closed]
10 = LO [Locked open]
11 = LC [Locked closed]
15 = FO [Fail open]
16 = FC [Fail closed]
18 = FL [Fail locked]
19 = FLO [Fail locked open]
20 = FLC [Fail locked closed]
24 = FI [Fail indeterminate]
30 = EO [Energize to open]
31 = EC [Energize to close]
34 = DEO [De-energize to open]
35 = DEC [De-energize to close]
62 =
Refer to AWWA-C151 for suitable installation types.
63 =
Underground pipe and fittings shall be coated and wrapped.
64 =
Pipe and fittings shall be cement lined.
79 =
Extra thickness has been included.
80 =
All components shall be bored to suit thickness of pipe.
Taper bore flanges to a depth of 1.5 inches as required to match
inside diameter of all connecting piping and valves. Welds
shall be ground smooth to match inside diameter of pipe.
82 = Use long radius bends with radius as specified on the P&IDs
for all changes in direction.
83 = Do not allow galvanized or any other zinc bearing material
to come in contact with stainless steel or high nickel
alloys components. This includes supports, nipples, weld
splatter, wire, bolts, paint, or any other type of contact.
1 = [Blank]
Actuators, 41-99
41 = Diaphragm
42 = Electro-Pneumatic
43 = Press-balanced diaphragm
45 = Regulator
49 = Single acting cylinder
51 = Double acting cylinder
53 = Pilot operated cylinder
57 = Motor
61 = Digital
65 = Electro-hydraulic
69 = Single solenoid
71 = Single solenoid w/reset
73 = Double solenoid
77 = Pilot
81 = Weight
85 = Manual
89 = Spring
91 = Capacitance sensor
93 = Ball float
95 = Displacement float
97 = Paddle wheel
60 = BS806
61 = BS3351
1 = [Blank]
1400 = Babbitt 1
1425 = Babcock and Wilcox 1
1450 = Badger Meters 1
1475 = Bailey Co 1
1500 = Balon 1
1525 = Basic Engineering 1
1550 = Bestobel 1
1560 = Bete 1 [SSP1-Series_N ||]
1575 = Bonney Forge 1 [GAT-Fig_9HLF-10; GATR-Fig_9H-10; GATR-
Fig_9W-10;
GATEXB-Fig_VLL-10; GATEXB-Fig_VOLL-10; GLOR-Fig_HL-30; GLOR-
Fig_9HL-30;
GLOR-Fig_9WL-30; CKLR-Fig_9HL-40; CKLR-Fig_9HL-50; CKLR-Fig_9HL-
60;
CKLR-Fig_9WL-40; CKLR-Fig_9WL-50; CKLR-Fig_9WL-60; CKLR-Fig_HL-40;
CKLR-Fig_9HLF-40; CKLRY-Fig_9Y-40; CKLRY-Fig_25Y-40; CAPOT; UN; L;
LRB;
SWOL; WOL; SOL; TOL; NOL; EOLLR; EOLSR; LOL ||]
1576 = Bonney Forge 2 [GATR-Fig_9H-10; GATR-Fig_25W-10; GLOR-Fig_9HL-
30;
GLOR-Fig_9WL-30; GLOR-Fig_25W-30; GLOY-Fig_25Y-30; CKLR-Fig_9HL-
40;
CKLR-Fig_9HL-50; CKLR-Fig_9HL-60; CKLR-Fig_9WL-40; CKLR-Fig_9WL-
50;
CKLR-Fig_9WL-60 ||]
1577 = Bonney Forge 3 [GATF-Fig_H-10; GATF-Fig_W-10; GATR-Fig_HL-10;
GATR-Fig_WL-10; CKLR-Fig_HL-40; CKLR-Fig_WL-40 ||]
1585 = Boots & Coots 1 [MN1-Spectrum_Allpha_6235 ||]
1590 = Bray 1
1600 = Brooks Meters 1
1625 = Cameron 1
1650 = Carbone 1
1675 = Ciba-Geigy 1
1700 = Clark Reliance 1
1725 = Clayton Automatic Valves 1 [CKBP-Model_D; FLO-Series_427-01
||]
1750 = Clayton Mark 1
1775 = Clow 1
1800 = Cochrane 1
1825 = Condren 1
1850 = Continental Emsco 1
1875 = Cooper Valve 1
1900 = Crane 1 [GATF-Fig_3904U; GATR-Fig_424; GATR-Fig_431UB; BALR-
Fig_9302;
GLOF-Fig_3944U; GLOR-Fig_14 1/2P; GLOR-Fig_70; GLOY-Fig_7189; NEE-
Fig_88;
CKS-Fig_373;CKLF-Fig_3973U; CKSR-Fig_36; CKSR-Fig_137; FOOT-
Fig_394;
FOOT-Fig_395; FLWN; FSO; L; LRB ||]
1925 = Crosby 1
1950 = Daniel 1
1975 = Demco 1
2000 = Dezurik 1
2025 = Dixon 1
2050 = Dresser 1
2075 = Dover 1
2100 = DOW 1 [TRI-Lining_SL; TRI-Lining_PPL, TRI-Lining_KL ||]
2150 = Duo Seal 1
2200 = Elkhart 1
2225 = Enpro 1
2250 = Epsco 1
2275 = Everest 1
2775 = Hammond 1
2800 = Hancock 1 [BDA-Fig_5505W ||]
2825 = Haws 1 [SSEW1-Fig_8309; SSEW1-Fig 8309CRP ||]
2850 = Heaton 1
2860 = Hex 1
2875 = Hindle-Hamer 1
2900 = Hitachi 1
2915 = Hoke 1
2925 = Hydril 1
3075 = Jerguson 1
3100 = Judd Valve 1
3125 = Kamyr-Neles 1
3150 = Kemp 1
3175 = Kennedy 1
3200 = Keystone 1
3225 = Kinka Kikai 1
3250 = Kitz 1
3275 = KTM 1
3300 = Kubota 1
3445 = Mac-Iron 1
3450 = Magnetrol 1
3475 = Malbranque 1
3500 = Maloney 1
3525 = Mark Controls/Centerline 1 [BFYLP-Series_A; BFYLP-Series_LT;
BYFLP-Series_504 ||]
3550 = Mark Controls/Flowseal 1 [BFYHP-Style_1LB ||]
3575 = Mark Controls/Marpac 1
3600 = Mark Controls/Pacific 1 [GATSP-Fig_21555; GATSP-Fig_55509;
GATSP-Fig_5
GLOSP-Fig_56009; GLOSP-Fig_56015; CKSSP-Fig_58809-5-WE; CKSSP-
Fig_58815-7-WE;
CKST-Fig_160S ||]
3625 = Marlin 1
3650 = Marwin 1
3675 = Masoneilan 1
3700 = Media 1 [BFYLP]
3725 = Milwaukee 1
3750 = Mueller/Muessco Brass 1
3775 = Mueller/Muessco Steam Specialty 1 [S51AC-Fig_761WE; S51AC-
Fig_862BC;
S51AC-Fig_762 ||]
3800 = Navco 1
3825 = Nells 1
3850 = Newco 1
3860 = Nibco 1
3875 = Nicholson 1 [S78AC-Fig_N302L ||]
3900 = Nippon-Benkan 1 [BW fittings above 48" ||]
3925 = Nupro 1
3950 = OPW 1
3975 = Orbit 1
4000 = Oseco 1
4520 = Sarco 1
4522 = Saunders 1
4525 = Sella 1
4550 = Serck Audco 1
4575 = Serfilco 1
4600 = Shoritsu 1
4625 = Smith 1 [GATF-Fig_888; GATF-Fig_5870; GATR-Fig_800; GATR-
Fig_870;
GATR-Fig_1500; GATR-Fig_1570; GATEX-Fig_811 & 812 MPE/THD; GATEX-
Fig_876
& 877 MPE/THD; GATEXB-Fig_874 & 875 OLET/THD; GATXBA-Fig_874 & 875
OLET/S
GATXBB-Fig_874 & 875 OLET/THD; GLOR-Fig_G80; GLOR-Fig_G87; GLOR-
Fig_G150;
GLOR-Fig_G157; CKLR-Fig_B80; CKLR-Fig_C80; CKLR-Fig_C150; CKLR-
Fig_SB80;
CKLR-Fig_SC80 ||]
4626 = Smith 2 [GATEX-Fig_813 & 814 MPE/SW; GATEX-Fig_878 & 879
MPE/SW ||]
4650 = Spraying Systems 1
4675 = Spirax Sarco 1
4700 = Stanco 1
4725 = Standard Fittings 1 [CAPOT; SWGC; SWGE ||]
4750 = Stang Hydronics 1 [M1-Fig BB0309-21 w/shapertip nozzle; ME1-
Fig BB3561
4751 = Stang Hydronics 2 [M1-Fig_BB0309-21 w/fog nozzle; ME1-Fig
B22999 ||]
4752 = Stang Hydronics 3 [ME1-Fig_BB3561 composite, w/monitor nozzle
||]
4753 = Stang Hydronics 4 [ME1-Fig_BB3377 composite, w/monitor nozzle
||]
4775 = Stockham 1
4800 = Strahman 1
4825 = Swagelok 1
4850 = Tapco 1
4875 = Taylor 1
4900 = Taylor Forge 1
4901 = Taylor Forge 2, Rev 1957 [L; S-STD WT ||]
4925 = Teledyne Farris 1
4950 = Texas Bolt 1
4975 = Thevignot 1
5000 = Titeflex 1
5025 = TK 1
5050 = TKM 1 [GAT-Fig_100 ||]
5060 = Top Line 1
5075 = Triangle 1
5085 = Tri-Clover 1
5100 = Truflo 1
5125 = TRW/Mission 1 [||]
5150 = Tubeturn 1 [FWN; FEWN; FOWNA; FOWNB; CAPBV; E453D; E90LT;
E903D; L; SA
5175 = Tufline 1
5200 = Tyler 1 [CPL; REDC; E45LT; E90LT; L ||]
5225 = Valvotecnic 1
5250 = Vanessa 1
5275 = Velan 1 [S3AC-Fig_N675 ||]
5300 = Victaulic 1
5325 = Viking 1
5350 = Vitas 1
5375 = Vogt 1 [GATR-Series_15373; GLOR-Series_15141; CKLR-
Series_15701;
5400 = Wada 1
5425 = Wallworth 1
5450 = Watts Regulator 1
5475 = Weco 1
5500 = WFI 1
5525 = Winston 1 [S49AC-T-Strainer Type-59 W/flgd cover; S53AC-
Basket-Strain
Fig 51-WIP W/CL150 flgd cover & 3/4" SWE drain||]
5535 = Wirt & Knox 1
5550 = WKM 1
5575 = Worcester 1
General Specifications
7000 = DIN 2401-1 Pressure, nominal
7001 = DIN 2401-2 Pressure, nominal
7002 = DIN 2402 Diameter,nominal
Pipes
7010 = DIN 2448 ;Steel pipes, seamless
7011 = DIN 2458 ;Steel pipes, welded
7012 = DIN 2440 ;Threaded pipes, medium weight
7013 = DIN 2441 ;Threaded pipes, heavy weight
7014 = DIN 2442 ;Threaded pipes, spec. qualty
7015 = DIN 2445 ;Seamless steel pipes,dyn. load
7016 = DIN 2460 ;Steel pipes for water
7017 = DIN 2462 ;Seamless ferritic steel pipes
7018 = DIN 2463 ;Seamless austenitic steel pipes
7019 = DIN 2391 ;Seamless precision steel tubes
7020 = DIN 2393 ;Welded precision steel tubes
Flanges
7100 = DIN 2530 ;Cast iron flanges, PN 2,5
7101 = DIN 2531 ;Cast iron flanges, PN 6
7102 = DIN 2532 ;Cast iron flanges, PN 10
Elbows
7200 = DIN 2605 ;Tube bends f. butt wldg
7201 = DIN 2606 ;Tube bends, steel 5d
7202 = DIN 2916 ;Bending radii, seaml.& wld pipes
7203 = DIN 2983 ;Threaded steel pipe fittings, bends
7204 = DIN 2987 ;Threaded steel pipe fittings, elbows
7205 = DIN 2987 ;Threaded steel pipe fittings, elbows,
reduced
7206 = DIN 2950 ;Malleable cast iron fittings, elbows
Reducers
7300 = DIN 2616 ;Steel fittings, reducers
7301 = DIN 2990 ;Threaded steel pipe fittings, Bushings
7302 = DIN 2988 ;Threaded steel pipe fittings, Reducing
sockets
7303 = DIN 2950 ;Malleable cast iron fittings, Reducing
sockets
7304 = DIN 2950 ; - " - , male and female connections,
Bushings
Branches
7400 = DIN 2615 ;Butt wldg steel fittings;T
7401 = DIN 2618 ;Welding saddles, short
7402 = DIN 2618 ;Welding saddles, long
7403 = DIN 2619 ;Bends for welding
7404 = DIN 2987 ;Threaded steel fittings;cross;T
7405 = DIN 2987 ;Threaded steel fittings;cross;T;redcd
7406 = DIN 2950 ;Malleable cast iron fittings, Tees, Crosses
Caps
7500 = DIN 2617 ;Butt wldg steel fittings, Caps
7501 = DIN 2991 ;Threaded steel fittings, Caps
7502 = DIN 2950 ;Malleable cast iron fittings, Caps
Other fittings
7600 = DIN 2981 ;Threaded steel fittings with long screw
thread
7601 = DIN 2982 ;Threaded steel fittings, Parallel Nipples
7602 = DIN 2982 ;Threaded steel fittings, Taper Nipples
7603 = DIN 2986 ;Threaded steel fittings, Sockets
7604 = DIN 2990 ;Threaded steel fittings, Hexagon Nipples
7605 = DIN 2991 ;Threaded steel fittings, Plain plugs
7606 = DIN 2993 ;Threaded steel fittings, Pipe unions
Gaskets
8100 = DIN 2690 ;Gasket for plain face C
8101 = DIN 2691 ;Gasket for tongue & groove
8102 = DIN 2692 ;Gasket for recessed faces
8103 = DIN 2693 ;Rings for grooved faces
8104 = DIN 2695 ;Diaphragm
8105 = DIN 2696 ;Lenticular gaskets
8106 = DIN 2697 ;Grooved O- rings
8107 = DIN 2698 ;Corrugated steel sheet
Valves
9000 = Non conform DIN 3202
9010 = DIN 3202-F ; Teil 1
9020 = DIN 3202-S ; Teil 2
9030 = DIN 3202-K ; Teil 3
9040 = DIN 3202-M ; Teil 4
9050 = DIN 3202-F ; Teil 5
Dummy standard
9999 = Dummy DIN Std ; Used for engineered items and instruments
PIPES
12000 = BS3600 table 1 carbon and low alloy steel tubes
12001 = BS3600 table 2 austenitic stainless steel tubes
12002 = BS3600 table 3 high alloy ferritic steel tubes
12003 = BS3600 table 4 cs tubes for compression fitting - tbi
12004 = BS3600 table 5 ss tubes for compression fitting - tbi
FLANGES
FITTINGS
12200 = BS1740 part 1 screwed wrought steel pipe fittings
12210 = BS1965 part 1 butt welding pipe fittings - CS
12220 = BS3799 steel pipe fittings screwed and socket welding (mm)
12221 = BS3799 steel pipe fittings screwed and socket welding (in)
12230 = BS1640 part 3/4 steel butt-welding pipe fittings
VALVES
gaskets
bolting
13200 = BS4882 metric series bolting
13210 = BS4882 inch series bolting
dummy
13999 = dummy BS code
1 = [Blank]
85 = Crosby
86 = Consolidated
87 = Lonergan
88 = Top Line
90 = Tube-Turn
91 = Dow
92 = Aloyco
93 = Yarway
94 = Teledyne Farris 1
95 = R & G Sloane
96 = American DI Pipe
RTJ-face flanged..................ANSI-B16.5
Tongue/male-face flanged..........ANSI-B16.5
Groove/female-face flanged........ANSI-B16.5
Flat-full-face thru-bolted........DOW
Female threaded
thread engagement per Table 2.4 of
2630-33
..................................Forged steel.For pressure ratings
XXXX#s,
defined in the applicable generic
tables; for
pressure ratings CLXXXXs and OTXXXXs,
per ANSI
and ANSI-B16.5. In all cases, thread
engagement
will be per Table 2.4 of 2630-33
descriptions in the applicable
generic tables.
In all cases, thread engagement will
be per
Table 2.4 of 2630-33
Female ferrule....................
Female hose.......................
Gasket............................Not applicable
Bolt..............................Not applicable
Nut...............................Not applicable
User defined......................None
British Standards
1 = [Blank]
85 = Crosby
86 = Consolidated
87 = Lonergan
90 = Tube-Turn
91 = Dow
92 = Aloyco
93 = Yarway
94 = Teledyne Farris 1
95 = R & G Sloane
96 = American DI Pipe
97 = Gladding McBean [Vitrified clay S-XS pipe and fittings]
98 = Taylor Forge
99 = Vendor 4
RTJ-face flanged..................ANSI-B16.5
Tongue/male-face flanged..........ANSI-B16.5
Groove/female-face flanged........ANSI-B16.5
Flat-full-face thru-bolted........DOW
Female threaded
thread engagement per Table 2.4 of
2630-33
..................................Forged steel.For pressure ratings
XXXX#s,
defined in the applicable generic
tables; for
pressure ratings CLXXXXs and OTXXXXs,
per ANSI
Female ferrule....................
Female hose.......................
Gasket............................Not applicable
Bolt..............................Not applicable
Nut...............................Not applicable
User defined......................None
o European practices 1 (DIN) 100-199
British Standards
1 = [Blank]
201 = [Blank]
1 = [Blank]
2 = Pipe connector
11 = Shop weld
21 = Field weld at assembly site
22 = Field weld at job site
23 = Field weld at job site for loose flange
24 = Field fit weld at job site
1 = MTO Report
2 = Drawing Report
3 = PID Report Header
11 = Project Control Report
12 = Clash Management Report
21 = Piping Job Spec Report
22 = Table Checker Report
1 = Client Review
2 = Informal Review
1 = Fabrication
2 = Spool
3 = Stress
This form allows you to manipulate various data libraries and database tables.
For more information on specific data and libraries, see Graphic Commodity Library Manager
(on page 200), Piping Assembly Library Manager (on page 393), and Physical Data Library
Manager (on page 208).