Escolar Documentos
Profissional Documentos
Cultura Documentos
(PD_Data)
Reference Guide
All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or
implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties.
The information and the software discussed in this document are subject to change without notice and should not be considered
commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this
license.
No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its
affiliated companies.
Trademarks
CLIX, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DBACCESS, DesignReview, DIALOG, EE Raceway,
FrameWorks, Project Engineer, and SEE are trademarks of Intergraph Corporation. All other brands and product names are trademarks of
their respective owners.
Copyright
1984-2002 Intergraph Corporation
All Rights Reserved
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright and trade secret law and may not
be provided or otherwise made available without proper authorization.
Unpublished rights reserved under the copyright laws of the United States.
Intergraph Corporation
Huntsville, Alabama 35894-0001
________________ If You Need Assistance
Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraphs
products, services, and direction. Our web address is: http://www.intergraph.com.
Support
For the lasest Support Services information, use a World Wide Web browser to connect to
http://www.intergraph.com/ppo/services/support.asp.
If you are outside of the United States, please call your local Intergraph office. The most up-
to-date list of international offices and distributors is available on the web at
http://www.intergraph.com.
Intergraph Directory
The following numbers are only valid in the United States unless otherwise indicated. If you
are outside the United States, please call your local Intergraph office.
Training Registration
1-800-766-7701 (U.S. Only)
Mailing Address
Intergraph Process, Power & Offshore
300 Intergraph Way
Madison, Alabama 35758
U.S.A.
3
________________
Documentation Contacts
We are constantly working on updates and improvements to the documents and other
educational media. If you have any suggestions on where we can improve the documentation
or where you think more information is needed, let us know. You can reach us by:
4
________________ Table of Contents
Table of Contents
If You Need Assistance ........................................................................................................ 3
Intergraph Directory ............................................................................................................. 3
Preface ................................................................................................................................................. 15
1. Introduction .................................................................................................................................. 21
PD Shell ....................................................................................................................................... 34
Help .............................................................................................................................................. 41
5
________________
Reference Data Manager Reference Guide April 2002
6
________________ Table of Contents
5.4.1 Load, Replace, and Replace Commodity Subset Options ....................................... 148
5.4.2 Delete Option .......................................................................................................... 151
5.4.3 Report Option .......................................................................................................... 152
7
________________
Reference Data Manager Reference Guide April 2002
7.2.1 Data Retrieval from the Physical Data Library ....................................................... 267
7.2.2 Example of Physical Data Look-Up ....................................................................... 268
8
________________ Table of Contents
9
________________
Reference Data Manager Reference Guide April 2002
10
________________ Table of Contents
11
________________
Reference Data Manager Reference Guide April 2002
12
________________ Table of Contents
13
________________
Reference Data Manager Reference Guide April 2002
14
________________ Preface
Preface
Document Purpose
This document is a reference guide for the Reference Data Manager module of the
PDS 3D products. PDS 3D uses interactive graphics and database management
techniques to integrate the engineering and design/drafting execution of plant design.
The Reference Data Manager module is one part of the overall Plant Design System.
It is specifically designed to define and modify the reference data for the PDS 3D
modules. It enables you to control and standardize the PDS 3D tasks. You can also
modify the reference data to reflect company practices and standards.
Related Documents/Products
Intergraph Corporations Relational Interface System (RIS)TM is required to operate
PDS 3D, along with a relational database management system (RDBMS) supported
by RIS. Currently, these include Informix, Oracle, and Ingres. Information
about RIS capabilities can be found in the following documents:
For more information on related aspects of the PDS 3D products, consult the
following documents:
15
________________
Reference Data Manager Reference Guide April 2002
Section 3 Describes the main Reference Data Manager form used to access
the product.
Sections 4-16 Describe the individual libraries and managers which make up
the Reference Data Manager including operating steps for each
form within the manager.
Additional Information
The following informational files are delivered with the software in the directory.
readme.txt Describes changes and additions to the product since the last
version. For a fixes release, the fixes are appended to the top of
the initial file to provide a history of all changes to the product.
Includes Comments and Trouble Report numbers which describe
what problems have been fixed. Provides special notices to the
customer. Lists any exceptions made to the certification.
16
________________ Preface
General Conventions
This document contains many visual cues to help you understand the meaning of certain
words or phrases. The use of different fonts for different types of information allows you to
scan the document for key concepts or commands. Symbols help abbreviate and identify
commonly used words, phrases, or groups of related information.
Typefaces
Italic Indicates a system response, which is an explanation of what the software is
doing. For example,
Bold Indicates a command name, parameter name, or dialog box title. Command
paths are shown using an arrow between command names. For example,
Sans serif Indicates a system prompt or message, which requires an action be taken by
the user. For example,
Bold Typewriter
Indicates what you should literally type in. For example,
Normal Typewriter
Indicates an actual file or directory name. For example,
17
________________
Reference Data Manager Reference Guide April 2002
Symbols
This document uses the following symbols to represent mouse buttons and to identify special
information:
Warning Critical information that could cause the loss of data if not followed.
Need a hint used with activities and labs, provides a tip or hint for doing the
exercises.
Keyboard Conventions
The following list outlines the abbreviations this document uses for keyboard keys and
describes how to use them in combination. You can make some menu selections through the
use of keyboard accelerators, which map menu selections to key combinations.
18
________________ Preface
Terminology
Click To use a mouse or key combination to pick an item that begins an
action. For example,
Select the file original.dat from the list box, then click Delete to
remove it from the directory.
Drag To press and hold the data button (<D>) while moving the mouse or
hand-held cursor.
Key in To type in data and press ENTER to enter the data and execute the
default action.
19
________________
Reference Data Manager Reference Guide April 2002
20
________________ Introduction
1. Introduction
1. Introduction
Welcome to the Reference Data Manager (PD_Data) module of the Plant Design System of software.
Intergraphs plant design software can be used to design any type of plantfrom 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.
21
________________
Reference Data Manager Reference Guide April 2002
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.
22
________________ Reference Data Overview
1. Introduction
The Reference Data Manager (PD_Data) enables you to define and modify the reference
data for the PDS 3D modules. This reference data is used to ensure consistency in the
definition of piping specifications and commodity libraries. It enables you to control and
standardize the PDS 3D tasks. You can also modify the reference data to reflect company
practices and standards.
The Reference Data for PDS 3D is composed of the following basic components:
Spec/Material Database
Table 201 - Piping Material Class Data
23
________________
Reference Data Manager Reference Guide April 2002
The Reference Data Manager supports both approved and unapproved reference data for a
project. The Project Control Database contains complete file management data for both an
approved and unapproved version of each type of reference data such as the Piping Job
Specification or the Graphic Commodity Library. This allows revisions to take place in
unapproved files while other processes read the approved files. Once the information in the
unapproved files has been verified, it can be posted to the approved reference data files.
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.
24
________________
Reference Data Overview
1. Introduction
25
________________
Reference Data Manager Reference Guide April 2002
26
________________ Piping Job Specification Introduction
1. Introduction
The Piping Job Specification (PJS) provides selection criteria for piping commodity items,
piping specialty items, and instruments. The information for the Piping Job Specification is
contained in the following files:
Spec Table Library - library containing the specification tables referenced in the PJS.
The information in the Specification/Material Reference database and Spec Table Library
tables is also delivered in the form of neutral files which you can extract and modify.
The Piping Job Specification Manager enables you to create or revise the specificaton data
in the Material Reference Database. You can use the interactive (forms-driven) specification
writer or define/revise the data using ASCII neutral files.
The Piping Job Spec Tables command enables you to create, revise, and delete tables in the
Spec Table Library.
Graphic Commodity Library - contains the parametric definitions for the commodity
items.
Physical Dimension Libraries - contains dimension data for the commodity items. (A
different Physical Dimension Library is required for each type of practice such as, U.S.,
DIN, or British Standard)
Spec Table Library - contains the specification tables referenced in the PJS.
The parametric descriptions and dimension tables are also delivered in the form of text
libraries which you can extract and modify using the Graphic Commodity Library
Manager and Physical Data Library Manager.
27
________________
Reference Data Manager Reference Guide April 2002
Stress analysis
The Material Description Data consists of the commodity item data which is not stored in the
Design Database, which is not required for the creation of graphic symbologies, and which is
not part of the geometric data. This data is contained in the following files:
Short Material Description Library - contains the short material descriptions for
commodity items and taps.
Long Material Description Library - contains the long material descriptions for
commodity items.
Specialty Material Description Library - contains the material descriptions for specialty
items.
The material descriptions are also delivered in the form of neutral files which you can modify
and post to the libraries.
The Material Description Library Manager enables you to create, revise, and delete data in
the Material Description Libraries. You can use the Piping Job Specification Manager to
load the material data tables in the Specification/Material Database.
28
________________ Piping Job Specification Introduction
1. Introduction
The Label Description Library contains the definitions for the following label types used in
PDS 3D:
Report labels
These labels are intelligent graphics with links to the material database.
The Label Description Library Manager enables you to define the graphic parameters for a
label (such as level, line weight, and color code) and to define the format of the label (what
information comprises the label.)
A Piping Assembly object library and text library which contain the definitions for basic
assemblies are included in the product delivery.
29
________________
Reference Data Manager Reference Guide April 2002
numeric data types can be either real (decimal) or integer. These attributes are used for
quantitative values such as pressure or temperature.
alphanumeric data types (also called character) are used for textual information such as
component names or descriptions.
code-listed data types are a special integer values which help standardize and speed up
data entry. A code list is a set of acceptable values for a particular attribute which can
be referred to by an index number. A code-listed attribute is an attribute whose value is
defined using one of the selections from a particular code list set.
30
________________ Delivered Reference Data
1. Introduction
The following reference data is delivered in the reference database products for the
corresponding practices (such as RDUSRDB or RDDINRDB).
Library
File Description Object Text
For the DIN RDB substitute din_ for us_ in the listed library file names.
The following reference data, which is not unique to any specific practice, is delivered in the
PD Shell product in the \win32app\ingr\pdshell\lib directory.
Library
File Description Object Text
31
________________
Reference Data Manager Reference Guide April 2002
Editing the control script to identify the location of the project data.
In addition to the information specified in the Project Administrator Reference Guide, you
should complete the following steps before using the Reference Data Manager.
Load the appropriate Reference Data product (such as RDUSRDB for U.S. Practice or
RDDINRDB for DIN Practice).
Edit the pds.cmd file to identify the text editor to be used when revising reference data
through the Reference Data Manager forms. You can specify any text editor that has
been loaded on the workstation. The default setting for Windows NT systems is
Notepad.
Identify the location of the Reference Data files as described in Reference Data
Location, page 47.
32
________________ PDS Environment
2. 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 PDS 3D software uses available nucleus tools such as MicroStation and FORMS. It
2. Environment
supports standard software such as NFS, NQS, and RIS required to set up data across a
network. This design facilitates the use of non-PDS tools such as relational databases and
third party software.
The PD_Shell Environment and all batch jobs in the PDS 3D products interface to
Intergraphs Network Licensing System.
33
________________
Reference Data Manager Reference Guide April 2002
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
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 in the Project Administrator
Reference Guide for more information on this file. The script also activates the Plant Design
System Environment form.
This form identifies the active project(s) and provides access to all the PDS functions.
Options
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.
34
________________ PD Shell
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
2. Environment
environment. This module is used with PD_Design to create an accurate 3D model of
the piping network.
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.
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.
35
________________
Reference Data Manager Reference Guide April 2002
Other Fields
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 the Access Control Manger in
the Project Administrator (PD_Project) Reference Guide, for more information on
using access control.
If access control has not been defined, no entry is required for this field.
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 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.
36
________________ PD_Shell Form Conventions
Selecting Options
You move through the PD Shell forms by selecting function buttons or other gadgets from the
2. Environment
form. Select means to place the screen cursor (which appears as an arrow) on top of a screen
gadget and press <D>.
For most of the forms with scrolling lists, you can double-click on a row to select and accept
the data in that row. This performs the same action as selecting a row (which highlights) and
then selecting the Accept button.
You use the select action to select functions, access other forms, activate data fields, toggle
buttons, select from lists, scroll through data displayed on the screen, and so on.
The following summarizes other basic actions you use in the environments:
Enter When keying in any data in a key-in field, press the <ENTER> or <Tab> key
for the data to be entered into the system. You can also press <ENTER> or <Tab> to
move through a set of key-in fields.
Delete If you make a mistake while keying in text, press the <Delete> key to erase
character(s) to the left of the cursor.
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.
37
________________
Reference Data Manager Reference Guide April 2002
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.
The Accept button accepts a selection or operation. Depending on the active form or option,
the active form remains active so that you can repeat a similar operation or control returns to
the preceding form.
The Restart button clears any key-in fields on the form that have values you can modify.
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.
38
________________ PD_Shell Form Conventions
Key-in Fields
Screens that accept keyboard input have key-in fields. These fields are box-
shaped and dark gray. You can select a key-in field and key in a new value. A
bar cursor appears in the active key-in field. Key in your input, and press
<Return>. To change a field, reselect the field and key in the new information.
Key-in fields have a maximum number of characters depending on the item that
is being defined.
If you select a key-in field for a code-listed attribute, the system activates a form that lists the
code list values for the selected field.
MicroStation requires lowercase characters for the file specification and path name of all
2. Environment
design files. Therefore, the system automatically converts any input for the file specification
and path name of a design file (such as a model or drawing) to lowercase before loading into
the Project Control Database.
Display-List Boxes
A display-list box is located at the end of some key-in fields. It lets you select
data from a list instead of keying in information. For example, there is a
display list associated with the Authorization key-in field shown. At the end of
the field, there is a small box with horizontal dashes. When you select this
display list box with the screen cursor, an associated list of valid input values
displays. Select an item from the list to enter its value into the field.
At the bottom of some key-in and display fields, there are two buttons marked with
arrows. These buttons are called shift left and shift right buttons.
Often, you can key in more characters than a field display shows. Shift Left moves the text
display to the front of the field; Shift Right moves the text display to the end of the field.
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.
39
________________
Reference Data Manager Reference Guide April 2002
When using this software in the CLIX environment, 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.
Batch Processes
When you install the PDS 3D applications, the system creates the necessary batch queues for
that application. Refer to Loading PDS 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.
When you submit a batch process the system sends an electronic mail message to the mail
path of the default login reporting the jobs completion status. The mail message also includes
any error log information.
40
________________ Help
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
2. Environment
software.
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:
41
________________
Reference Data Manager Reference Guide April 2002
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.
Operating Sequence
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.
OR
Exit Help.
42
________________ Reference Data Manager
Data Manager
3. Reference
Select the option to be performed.
Spec Writer Used to create, modify, and delete information in the Material
Reference Database using a forms interface. See Spec Writer, page 103.
Piping Job Specification Manager Used to create, modify, and delete information
in the Material Reference Database using neutral files. See Piping Job Specification,
page 55 and Piping Job Specification Manager, page 145.
Piping Job Specification Tables Used to create, modify, and delete information in
the Piping Job Spec Table Library. See Piping Job Specification Tables, page 189 and
Piping Job Specification Tables Command, page 239.
Piping Job Spec Report Manager Used to define and generate reports of data in
the Material Reference Database. See Piping Job Spec Report Manager, page 154.
Graphic Commodity Library Manager Used to create, modify, and delete graphic
commodity library data (Eden modules). See Graphic Commodity Library, page 254
and Graphic Commodity Library Manager, page 275.
Physical Data Library Manager Used to create, modify, and delete physical data
(dimension tables) in object and text libraries. See Physical Data Tables, page 266 and
Physical Data Library Manager, page 287.
43
________________
Reference Data Manager Reference Guide April 2002
Support Tutorial Definition Manager Used to create, revise, and delete data in the
Tutorial Definition Library. See Pipe Support Tutorial Definition Manager, page 437.
Standard Note Library Manager Used to create, revise, and report the code lists
and standard notes associated with the PDS 3D modules. See Standard Note Library,
page 449 and Standard Note Library Manager, page 453.
Label Description Library Manager Used to define the graphic parameters for a
label (such as level, line weight, and color code) and to define the format of the label
(what information comprises the label). See Label Description Library, page 465 and
Label Description Library Manager, page 471.
Piping Assembly Library Manager Used to create, revise, and delete piping
assembly definitions in the Piping Assembly Library. The Piping Assembly Language
(PAL) enables you to define the parameters necessary to place a piping assembly (group
of components) automatically in the model. See Piping Assembly Library, page 505
and Piping Assembly Library Manager, page 525.
Table Checker Used 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.
See Table Checker Form, page 389.
Reference Database Management Data Used to define the filenames for Reference
Database Files, graphic commodity data, dimension tables, and spec tables. You can
define both approved or unapproved RDB data for each item. See Reference Database
Management Data, page 48.
Default Project Control Data Used to define the default location for the source
files used to load the RDB files (such as neutral files, program files, and report files).
See Default Project Control Data, page 53.
44
________________ Data Security
When you enter the Reference Data Manager to create, revise, or delete data in any of the
these libraries, the system creates a temporary file for that library. This temporary file is
named <library_specification>.c and will be created in the same directory location as the
Data Manager
3. Reference
object libary. Once you successfully exit the applicable library manager, the system deletes
the temporary file. If a PDS user is unable to exit the Reference Data Manager for any
reason (such as a power failure), the system displays a dialog box when the next user enters
the Reference Data Manager to revise that library. You must decide which of the following
situations applies and respond accordingly.
If you are certain that the warning results from a previous unusual exit, make one of the
following decisions.
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.
45
________________
Reference Data Manager Reference Guide April 2002
46
________________ Reference Data Location
Default Project Control Data Defines the default location for the source files used
to load the RDB files (such as neutral files, language files, and report files). See page
53.
Data Location
4. Reference
47
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select Reference Database Management Data from the Reference Data Manager
form.
Select the RDB file from the list of files. You can use the scroll arrows to scroll
through the listed files.
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.
Piping Job Specification Table Library This field identifies the location of
the Piping Job Spec Table library.
48
________________ Reference Database Management Data
Standard Note Library This field identifies the location of the standard
note library.
Label Description Library This field identifies the location for the label
description library.
Piping Assembly Library This field identifies the location for the Piping
Assembly library. This library contains the symbol definitions for assemblies.
Physical Data Library These fields identify the library files which contain
the physical data tables for a range of geometric industry standards.
Data Location
4. Reference
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, page
31, 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.
49
________________
Reference Data Manager Reference Guide April 2002
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
Options
Key in a default network address and pathname to be used for all approved Reference
Database libraries and a network address and pathname to be used for all unapproved
libraries.
The file specifications for all libraries are determined automatically on the basis of the
industry practice and the following naming convention.
When copying the Not Approved library to the Approved library, the copy will not
occur if the approved library is the most recent or has the same date as the
unapproved library.
50
________________ Reference Database Management Data
Library Filename
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
Data Location
4. Reference
Project Control database.
This option provides a new user with a simple method to create a Reference Database using
RDB products delivered by Intergraph. This is not intended for use in a production
environment.
The following Reference Database libraries are copied from the PD Shell product.
The following Reference Database libraries are copied from the applicable Reference
Database product (such as, rdusrdb or rddinrdb).
51
________________
Reference Data Manager Reference Guide April 2002
The system also copies the applicable Table Revision Management Libraries for the Piping
Spec Table Library and Physical Data Libraries.
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
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
are 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.
52
________________ Default Project Control Data
Operating Sequence
1. Select Default Project Control Data from the Reference Data Manager form to
define the default location for the RDB source files.
Data Location
4. Reference
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.
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.
53
________________
Reference Data Manager Reference Guide April 2002
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.
54
________________ Piping Job Specification
Specification
5. Piping Job
55
________________
Reference Data Manager Reference Guide April 2002
The Piping Commodity Specification Data is linked to the Piping Materials Class Data.
Attribute Types
The following conventions are used to designate the field type for database attributes.
56
________________ Material Reference Database Structure
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
descriptions 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
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 B for a listing of the code list sets associated with
PDS 3D.
If data is only shown under the green connect point, it applies to all ends of the
component.
If a component has ends with different nominal diameters (regardless of other end
properties) the larger nominal diameter is designated as the green connect point.
If a component has ends with the same nominal diameter but other end properties which
differ, the following rules apply:
If the ends have different termination types (regardless of the values for
schedule/thickness) the end(s) whose end preparations have the lowest codelist
number are designated as the green connect point.
If the termination types are the same but the values for rating, schedule, or thickness
differ, the "stronger" ends(s) are designated as the green connect point.
Specification
5. Piping Job
57
________________
Reference Data Manager Reference Guide April 2002
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.
58
________________ Neutral File Input
There must be an entry for each user-defined parameter in the Material Reference
Database. For certain attributes you can use a dash (-) to indicate that a default value be
used.
The SEQUENCE statement can be used to define the order of entries in the neutral file.
Each entry (attribute) can begin at any point along the input. You can set the spacing
between each entry by specifying SINGLE_SPACING or DOUBLE_SPACING as the
first item in the file. If you do not define the spacing, double spacing is used.
For single line comments, place an exclamation point (!) at the beginning of the line.
All comments are disregarded by the system.
You can place blank lines anywhere in the file for readability. These lines do not effect
the information being copied.
You can use any of the three PDS conventions to enter fractional Nominal Piping
Diameters. The entries
You can use both metric and English units. The default system of units must be
declared once in the beginning and each time the default system is changed. Entries are
automatically interpreted as English. To declare the system of units add the appropriate
units marker to the entry:
Specification
5. Piping Job
mm for metric
" for English
The Tap Properties Table must include the Table Name along with other data by using
the TABLE statement.
59
________________
Reference Data Manager Reference Guide April 2002
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.
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.
At least two spaces must separate the keyword and each parameter.
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.
60
________________ Neutral File Input
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
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
Specification
5. Piping Job
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
61
________________
Reference Data Manager Reference Guide April 2002
1. system_unique_no , integer
2. piping_mater_class , character(16)
This attribute identifies the service number, spec class, spec name, or spec number.
3. revision_no , character(2)
This attribute identifies the revision number for the data in the piping materials class. It
is user-defined and is not updated automatically when the piping commodity data for
that piping materials class is revised.
4. version_no , character(2)
This attribute represents the version number, as determined by the system, for the data
in this piping materials class (including the Commodity Item data). The version
number starts with A and is incremented (B,C,D,...) when you revise the piping
materials class. This attribute is under the complete control of the system.
The Piping Job Spec Manager increments this attribute when the piping commodity
data for that piping materials class is revised or reloaded. When that piping materials
class is posted from the unapproved to the approved Material Reference Database, the
version number for that piping materials class is reset to A in the unapproved Material
Reference Database.
5. revision_date , character(10)
This user-defined attribute can be used to define a date for the latest revision to the data
in a piping materials class.
This attribute can be used to define the type of fluid for which the piping materials class
is intended.
62
________________ Piping Materials Class Data (201)
a single fluid code value (such as 521 for process) from code list set 125.
the name of a fluid code table to define a set of fluid code values. Refer to Fluid
Code Table, page 214, for more information.
To use the specified fluid code(s), you must also set the Fluid Code Control toggle to
Yes on the Piping Data Control form of the Project Data Manager. Refer to the
Project Administrator (PD_Project) Reference Guide for more information on this
form.
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.
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.
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, page 191, for more
information on this table.
Specification
5. Piping Job
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, page 194, for more inforamtion.
63
________________
Reference Data Manager Reference Guide April 2002
This attribute identifies the thickness data table used in piping wall thickness
calculations for this piping materials class. Refer to Thickness Data Tables, page 197,
for more information.
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, page 200, for more information.
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, page 203,
for more information.
This attribute identifies the branch insertion table used to determine the name of the
branch commodity item to be used for tee and lateral branches. The item name is
determined as a function of branch geometry, run size, and branch size. The output of
the branch table is the item name of a commodity item (AABBCC code).
This attribute defines the name of the tap properties table which includes those
parameters required to define a tap on a specific commodity item. Refer to Tap
Properties Data (205), page 85, for more information.
This attribute is not currently used by the PDS software. Several vent and drain
definitions are contained in the delivered Piping Assembly Library.
This attribute is used to determine the actual gap that is assumed between seating
surfaces of two mating bolted ends. It can coincide with, but is not necessarily the
compressed gasket thickness. You can override this value during a design session by
changing the type of gasket that applies to the joint. (You cannot override this value by
defining a specific gasket gap override value.)
64
________________ Piping Materials Class Data (201)
All other values are assumed to identify a table name for gasket separation data as
a function of nominal piping diameter in the Piping Graphic Commodity Library.
Refer to Gasket Separation Table, page 212, for more information.
Refer to the description of gaskets in the PDS Piping Component Data Reference Guide
for more details.
These code-listed attributes provide the index numbers to CL499 for notes that apply to
this piping materials class. The input to the Standard Note Library is the note number.
The output is the free- format text which forms the standard note.
In the delivered data, note numbers 1 through 199 are allocated for defining the PJS.
This system-defined attribute identifies the date of the latest revision for the data in this
piping materials class.
This attribute identifies the Bend Deflection Table to be used for this piping materials
class. This attribute is useful for defining specs for underground piping.
If this column is undefined (blank), the system will use the default Bend Deflection
Table specified in the Type 63 data through the Project Data Manager. Therefore,
you need not define a Bend Deflection Table for each piping materials class in the
Material Reference Database. Likewise, you need not revise any existing neutral files
to include this column.
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), page 219, for more information.
Specification
5. Piping Job
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.
65
________________
Reference Data Manager Reference Guide April 2002
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), page 222, for more information.
The Sequence= keyword in a piping materials class data neutral file does not require *21 for
the revision management date. Any previously created piping materials class data neutral
files will not require any revision as a result of this change.
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.
66
________________ Piping Commodity Specification Data (202)
Information for connect point data is defined in terms of two types of connect points known as
green and red connect points. Refer to Connect Point Data, page 270, for more information
on green and red connect points.
1. system_unique_no , integer
This attribute identifies the Piping Materials Class for the piping commodity.
3. commodity_name , character(6)
a PDS commodity item name. Refer to the PDS Piping Component Data
Reference Guide for more information on item names.
a Piping Job Specification access name. If you do not use the AABBCC code,
you must define a Commodity Synonym Library for proper communication with
the P&ID Task. The PDS commodity item names are also used with the
delivered Place Component forms. If you use a different code, you should create
a forms customization file as defined in the Piping Designer.
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 commodity
item, a secondary commodity item, or another special option from the Piping Job
Specification.
Specification
5. Piping Job
This parameter is used as a commodity override in Piping Design. You can select the
unique options (as defined in CL400) from a form. If no option is specified at
placement, this attribute defaults to option 1 (primary commodity item). Option 2 is
reserved as the secondary commodity item.
Option codes 4001 to 4010 are used to specify manual input of bend data for pipe
bends.
67
________________
Reference Data Manager Reference Guide April 2002
Option codes 4500 to 4999 are reserved for company practice (user-defined).
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 (-).
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.
68
________________ Piping Commodity Specification Data (202)
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
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:
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
Specification
5. Piping Job
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.
69
________________
Reference Data Manager Reference Guide April 2002
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.
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, page 203, for more information on this attribute.) In order of
preference, schedule and thickness are expressed in terms of:
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:
Trailing zeroes are not included. Decimal points are not included for numbers
without decimals.
An asterisk (*) followed by a name (of the form Cyyy) defines the specific
calculation or table lookup to be used for wall thickness. Refer to Wall Thickness
and Branch Reinforcement Equations, page 203 for a more detailed description of
the naming conventions for these calculations.
MATCH indicates the need to match the thickness of a component to that of the
pipe of the same diameter and of option 1.
70
________________ Piping Commodity Specification Data (202)
This code-listed attribute is used to further reference the source of the generic
dimensional data, such as flange data or piping outside diameter data. This attribute is
also referred to as the table suffix.
For AMS standards, it represents the table suffix for the green connect point.
For DIN standards, it represents the piping outside diameter selection flag (reihe
number) for pipes and fittings.
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the red connect point (second size). 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.
For a full size component, you should set these parameters to - (hyphen). In cases such
as a concentric reducer or weldolet, this value must be less than the corresponding green
value.
See gcp_end_prep.
See gcp_rating.
See gcp_sch_thk.
This attribute is used to further reference the dimensional data for a specific component.
For AMS standards, it represents the table suffix for the red connect point.
For DIN standards, it represents the built-in length selection flag (or reihe
number) for valves and wall thickness selection flag for pipes and fittings.
Specification
5. Piping Job
A parametric definition is used when connection graphics are required in the model and
orthographic drawings.
The commodity code is a user-assigned code that together with the NPD and
schedule/thickness uniquely defines the component. It defines the customers
commodity 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:
71
________________
Reference Data Manager Reference Guide April 2002
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 202 (Piping Commodity Specification Data), modify the value in column
18.
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.
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.
72
________________ Piping Commodity Specification Data (202)
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 to a single Item Name (for example,
GAT, GATR, and GATF are all used for 6Q1C01).
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.
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.
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.
73
________________
Reference Data Manager Reference Guide April 2002
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 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.
This code-listed attribute identifies the source of the data (which is usually an industry
standard, such as ANSI, ISO, or DIN, or a company standard) from which the specific
geometry of the commodity item can be deduced. This parameter represents the vendor
or industry standard, and the material if either affects the dimensions of the commodity
item.
Code list numbers 2-6999 are reserved for geometry standards that apply to US piping
practices. Numbers 7000-27999 are reserved for geometry standards that apply to
European piping practices. Numbers 28000-31999 are reserved for specific company
practices.
This code-listed attribute defines the weight code for the component. It determines the
table to be used in finding the dry weight of the component. It is required for those
cases where material causes the dry weight data but not the dimensional data to differ
for a specific geometric industry standard.
This code-listed attribute identifies the shop/field fabrication and purchase status of a
component. It defines how the component was supplied and how the component was
fabricated (for example, Shop Supplied, Field Fabricated).
74
________________ Piping Commodity Specification Data (202)
This code-listed attribute identifies the material code, specification, grade-temper, and
joint efficiency for the component. This data is used in wall thickness calculations. It
can also be used to access physical data in the Physical Data Library.
These code-listed attributes provide index numbers to standard notes in standard note
type 499 that apply to this commodity item. The input to the Standard Note File is the
note number. The output is the free- format text which forms the standard note.
In the delivered data, note numbers 200 through 599 are allocated for piping commodity
items.
This code-listed attribute defines the type of input form to be used to define data with
the Spec Writer command.
The Sequence= keyword in a piping commodity data neutral file does not require the *2 for
the piping materials class name. Any previously created piping commodity data neutral files
will not require any revision as a result of this change.
Specification
5. Piping Job
75
________________
Reference Data Manager Reference Guide April 2002
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).
76
________________ Piping Specialty Specification Data (203)
You can also place specialty items interactively in the model by defining the
necessary parameters at the time of placement. No entries in the PJS database
are required for these interactive definitions. Refer to the Piping Design
Graphics Reference Guide for more information on placing specialty items.
1. system_unique_no , integer
2. piping_comp_no , character(20)
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.
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.
These coded attributes identify the range of nominal piping diameters (lower bound to
Specification
5. Piping Job
77
________________
Reference Data Manager Reference Guide April 2002
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
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.)
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.
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the red connect point. For a full size component, these values are set
to zero.
See gcp_end_prep.
See gcp_rating.
78
________________ Piping Specialty Specification Data (203)
See gcp_sch_thk.
16.
See gcp_table_suffix
This parameter can be used to identify the name of the physical dimension table in the
Physical Data Library to be used for this engineered item.
This attribute can be used to define an arbitray index to a geometric data table for
piping specialties. This is an optional input.
This attribute is used for pipe bends, elbows, and miters. It represents the bend radius in
terms of the nominal piping diameter.
This attribute provides a reference to the source of the data (which is usually an industry
standard, such as ANSI, ISO, or DIN, or a company standard) from which the specific
geometry of the commodity item can be deduced.
This code-listed attribute defines the weight code for the component. It determines the
table to be used in finding the dry weight of the component. It is required for those
cases where material causes the dry weight data but not the dimensional data to differ
for a specific geometric industry standard.
This code-listed attribute identifies the shop/field fabrication and purchase status of a
component. It defines how the component was supplied and how the component was
fabricated (for example, Shop Supplied, Field Fabricated).
Specification
5. Piping Job
This code-listed attribute identifies the material code, specification, grade-temper, and
joint efficiency for the component. It can be used to access physical data in the Graphic
Commodity Library.
79
________________
Reference Data Manager Reference Guide April 2002
These attributes provide index numbers to standard notes in 499 that apply to this
specialty item. The input to the Standard Note File is the note number. The output is
the free-format text which forms the standard note.
In the delivered data, note numbers 600 through 799 are allocated for piping specialties.
This code-listed attribute defines the type of input form to be used to define data with
the Spec Writer command.
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.
80
________________ Instrument Component Specification Data (204)
You can also place instruments interactively in the model by defining the
necessary parameters at the time of placement. No entries in the PJS database
are required for these interactive definitions. Refer to the Piping Design
Graphics Reference Guide for more information on placing instruments.
1. system_unique_no , integer
2. instrument_comp_no , character(20)
This attribute identifies the tag number for the instrument item. You can modify the
character length for this attribute.
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.
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.
These coded attributes identify the range of nominal piping diameters (low bound to
high bound) for the green connect point.
81
________________
Reference Data Manager Reference Guide April 2002
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
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.)
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.
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.
See gcp_end_prep.
See gcp_rating.
See gcp_sch_thk.
82
________________ Instrument Component Specification Data (204)
See gcp_table_suffix.
This parameter can be used to reference the set of physical data from the Physical Data
Library to be used for this instrument item.
This attribute can be used to define an arbitrary index in the geometric data table for
instruments. This is an optional input.
This parameter, if applicable, is used to determine the type of valve operator for
instrument valves. It specifies the identification of the symbol description and the
source of the physical data for a valve operator.
This code-listed attribute identifies the source of the data (which is usually an industry
standard such as ANSI, ISO, or DIN; or a company standard) from which the specific
geometry of the commodity item can be deduced.
This code-listed attribute defines the weight code for the instrument. It determines the
table to be used in finding the dry weight of the instrument. It is required for those
cases where material causes the dry weight data but not the dimensional data to differ
for a specific geometric industry standard.
This code-listed attribute identifies the shop/field fabrication and purchase status of a
component. It defines how the component was supplied and how the component was
fabricated (for example, Shop Supplied, Field Fabricated).
This code-listed attribute identifies the material code, specification, grade-temper, and
Specification
5. Piping Job
joint efficiency for the instrument. It can be used to access physical data in the Piping
Graphic Commodity Library.
These code-listed attributes provide the index number to standard notes in NL499 that
apply to this instrument. The input to the Standard Note File is the note number. The
output is the free- format text which forms the standard note.
83
________________
Reference Data Manager Reference Guide April 2002
In the delivered data, note numbers 800 through 999 are allocated for instruments.
This code-listed attribute defines the type of input form to be used to define data with
the Spec Writer command.
Sample Files
A sample neutral file is delivered in the file
\win32app\ingr\pddata\sample\data\instrment.data.
84
________________ Tap Properties Data (205)
The NPD entry in the tap table should be either imperial units or metric units depending on
the NPD requirements of the project. For imperial units, enter the specified NPD, such as
0.375. The software will provide a default unit of inches when the value is loaded into the
project. For metric NPD units, enter the units after the value on the first NPD entry.
For example:
No-hole taps that permit the subsequent placement of a pipe support trunnion. For
example, a no-hole tap may be placed on an elbow or tee to allow the subsequent
placement of a pipe trunnion for a pipe support; the diameter of this no-hole tap must be
defined to have the same nominal diameter as the component part on which placed.
Hole taps that permit the subsequent placement of piping, piping components, and
instrument components. For example, a hole tap may be placed on a cap to allow the
subsequent placement of a reducing component such as a flatolet; the diameter of this
hole tap must be defined to have the same nominal diameter as the component part on
which placed. A hole tap can also be placed on a blind flange to allow the placement of
plain piping; the diameter of this hole tap must be defined to have the same nominal
diameter as the plain piping.
Hole taps that permit the venting or draining of a piping and/or instrument component.
For example, a hole tap can be placed on an elbow downstream of a relief valve; the
diameter of this hole tap must be defined to have the same nominal diameter as the
Specification
5. Piping Job
desired drain hole.
Component taps that represent a tap connection, rather than a hole. For example, a
socketwelded component tap may be placed on a gate valve to represent a socketwelded
connection furnished by the valve manufacturer. The diameter of this component tap
must be defined to have the same nominal diameter as the desired connection.
1. system_unique_no , integer
85
________________
Reference Data Manager Reference Guide April 2002
2. tap_table_name , character(6)
This attribute identifies the name of the Tap Properties Data Table. These tables use the
following naming conventions:
first character: C
next three characters: numbers from 001 through 999 used to make the table
name unique.
The combination of the tap properties table name, the tap NPD, and the tap option, must
be unique.
3. nominal_piping_dia , short
This attribute defines the value for the nominal tap diameter.
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. If no
option is specified at placement, this attribute defaults to option 1 (primary item). This
parameter is used as a component override in Piping Design.
This code-listed attribute identifies the end preparation. The system recognizes a
certain range of values as being flanged termination types, another range as being butt
welded termination types, etc.
6. rating , character(8)
This attribute 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 Piping Commodity Data for more information on
standard formats.)
7. sched_thick , character(8)
8. tap_material_code , character(10)
This optional attribute can be used to access the Material Description Library for the
taps 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.
86
________________ Tap Properties Data (205)
This attribute is also referred to as the Tap Code. Refer to the listing of the tap
descriptions in the Short Material Description Library, page 367, 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
24 691 - 591 NREQD E024591XXX
26 691 - 591 NREQD E026591XXX
28 691 - 591 NREQD E028591XXX
30 691 - 591 NREQD E030591XXX
32 691 - 591 NREQD E032591XXX
34 691 - 591 NREQD E034591XXX
36 691 - 591 NREQD E036591XXX
42 691 - 591 NREQD E042591XXX
48 691 - 591 NREQD E048591XXX
Sample Files
A sample neutral file for US practice is delivered in the file
Specification
5. Piping Job
\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.
87
________________
Reference Data Manager Reference Guide April 2002
This table is used for miscellaneous batch reporting, such as construction cost reports and
requisition orders, and interfaces to material control, stress analysis, and isometric drawing
extraction.
There are multiple occurrences for a specific commodity code and a specific pair of green and
red nominal piping diameters in the Piping Commodity Size-Dependent Material Data table
because schedule/thickness is not included in the commodity code.
1. system_unique_no , integer
2. sys_commodity_code , character(16)
This parameter identifies the customers commodity code (or part number). You can
modify the character length for this attribute.
3. gcp_nom_diam , short
4. rcp_nom_diam , short
These coded attributes identify the nominal piping diameter for the green/red connect
point in NPD Units.
5. gcp_sch_thk , character(8)
6. rcp_sch_thk , character(8)
These attributes identify the schedule thickness value for the green/red connect point.
This parameter exist as alphanumeric data.
A generic schedule such as S-STD, S-XS and S-XXS. If the schedule name
exceeds the provided field length it is defined in terms of its wall thickness.
A value with all numeric characters is interpreted as a wall thickness value in the
same physical units as nominal piping diameter.
88
________________ Piping Commodity Size-Dependent Material Data (211)
An asterisk (*) followed by a name (of the form Cyyy) defines the specific
calculation or table lookup to be used for wall thickness.
This attribute identifies the customers commodity code or vendors part number. It is
not required for the customers commodity code, if the customers 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.
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.
89
________________
Reference Data Manager Reference Guide April 2002
outputs
customers commodity code or vendors part number
weld data
price data (materials cost) - unit price
labor data - unit manhours
90
________________ Piping Commodity Implied Material Data (212)
This data is used strictly for generating implied material for MTO reporting and material
control. It is reserved for spec implied material, such as caps or stubs, for a specific
commodity item. It is also used for reporting the implied components of a commodity item
(for example, cap screws).
The entries in this tables should not be confused with mating implied items
(such as welds, bolts, nuts, or gaskets) which are generated automatically by
the system. Refer to the Report Manager (PD_Report) Users Guide for more
information on implied items.
A unique commodity code must be defined for each commodity definition. For example, if a
commodity code is defined for gate valves from 2" to 14", but you want a different description
for an 11" gate valve, you must assign a new commodity code to the 11" valve.
1. system_unique_no , integer
2. sys_commodity_code , character(16)
This parameter identifies the customers commodity code (or part number), if it is not
dependent upon nominal piping diameter. You can modify the character length for this
attribute.
3. gcp_from_nom_diam , short
4. gcp_to_nom_diam , short
These coded attributes identify the range of nominal piping diameters for the green
connect point in NPD units. These values are not necessarily the same as the range in
the Piping Job Specification.
for Metric units, the coded number equals the size (in millimeters)
Specification
5. Piping Job
for English Units, the coded number equals the size (in inches) times 32 plus
5000. coded number = 32*diameter + 5000 (in)
91
________________
Reference Data Manager Reference Guide April 2002
5. rcp_from_nom_diam , short
6. rcp_to_nom_diam , short
These coded attributes identify the range of nominal piping diameters for the red
connect point in NPD units. These values are not necessarily the same as the range in
the Piping Job Specification. For a full size component, these parameters should be set
to -.
This attribute identifies the Piping Commodity code of the implied material. It is used
to generate an MTO line item as a result of a piping commodity item in the Piping
Design model. The implied material is generated by accessing the Piping Commodity
Library - not by accessing the Piping Design database.
8. quantity , double
9. fabrication_cat , short
This code-listed attribute identifies the shop/field fabrication and purchase status of a
component. It defines how the component was supplied and how the component was
fabricated (for example, Shop Supplied, Field Fabricated).
This code-listed attribute provides index numbers to standard notes in CL499 that apply
to this implied material.
92
________________ Piping Commodity Implied Material Data (212)
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
Specification
5. Piping Job
\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.
93
________________
Reference Data Manager Reference Guide April 2002
outputs
Commodity code of the implied material
Quantity of the implied material
Fabrication category of the implied material
Standard note for the implied material
94
________________ Component Insulation Exclusion Data (231)
For each piping component, piping specialty, or instrument component (excluding pipes) on
an insulated line, the Piping Envelope Builder will search the Component Insulation
Exclusion Data Table on the basis of the following data to determine whether or not insulation
should be completely excluded from that components interference envelope.
For piping commodities, the Piping Envelope Builder searches for the components
commodity name in the Component Insulation Exclusion Data Table using the preceding data.
If the piping commodity is defined in the exclusion table for those conditions, the
applicable insulation thickness will not be added to the components interference
envelope.
If the commodity name is not specified in the exclusion table for those conditions, the
Piping Envelope Builder searches for the components model code using the same data.
If a match for those conditions is found on the basis of model code, the applicable
insulation thickness will not be added to the components interference envelope.
For piping specialties and instrument components, the Piping Envelope Builder searches for
the components model code in the Component Insulation Exclusion Data Table using the
preceding data. If the component is defined in the exclusion table for those conditions, the
applicable insulation thickness will not be added to the components interference envelope.
Otherwise, the insulation thickness will be included in the components interference envelope.
Specification
5. Piping Job
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.
1. system_unique_no , integer
95
________________
Reference Data Manager Reference Guide April 2002
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.
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.
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.
96
________________ Component Insulation Exclusion Data (231)
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.
These attributes identify the range of temperature values (lower bound to higher bound)
for 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.
Single_Spacing
Sequence= 2 3 4 5 6 7 8 9 10 11 12 13
Specification
5. Piping Job
97
________________
Reference Data Manager Reference Guide April 2002
The Piping Envelope Builder searches for matching data in this table for each bolted end of
each piping component or instrument component on an insulated line that are determined to
be insulated. The system only searches for components that passed the component insulation
exclusion test, as described in Component Insulation Exclusion Data (231), page 95.
The Piping Envelope Builder searches for matching data on the basis of the following data to
determine whether or not insulation should be excluded from the flange outside diameter of
that bolted end of the component.
If matching criteria is found in the exclusion table for these conditions, the applicable
insulation thickness will not be added to the flange outside diameter of the bolted end of that
components interference envelope. Otherwise, the insulation thickness will be included in
the components interference envelope.
The piping segment data (heat tracing requirements, insulation purpose, and normal operating
temperature) are determined on the basis of the piping segment associated with the first
connect point of the applicable component.
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:
98
________________ Flange Insulation Exclusion Data (232)
RETURN
END
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.
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.
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
Specification
5. Piping Job
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.
99
________________
Reference Data Manager Reference Guide April 2002
Single_Spacing
Sequence= 2 3 4 5 6 7 8 9
4 12 3 3 5 5 150 200
4 12 3 3 5 5 150 200
4 12 3 3 5 5 150 200
100
________________ Piping Construction Tolerance Exclusion Data (233)
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 components interference
envelope.
For piping commodities, the Piping Envelope Builder searches for the components
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 components interference
envelope.
If the commodity name is not specified in the exclusion table for those conditions, the
Piping Envelope Builder will search for the components 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 components interference
envelope.
Specification
5. Piping Job
For piping specialties and instrument components, the Piping Envelope Builder searches for
the components 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 components
interference envelope. Otherwise, the construction tolerance will be included in the
components interference envelope.
101
________________
Reference Data Manager Reference Guide April 2002
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.
Single_Spacing
Sequence= 2 3 4 5 6 7
- I15AS 4 12 - -
6Q2C76 - 4 12 - -
- REDE 4 12 2 10
102
________________ Spec Writer
Features
Specification
5. Piping Job
On-line validation for the existence of a material description, once the commodity code
(or component number) has been defined.
103
________________
Reference Data Manager Reference Guide April 2002
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.
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 Component Data Reference Guide
and the Reference Data Manager Reference Guide.
104
________________ RDB Options File
! RDB_options
!
! general items = three main toggles
!
SHORT_COMMODITY_MATERIAL_DESCRIPTION = OFF
LONG_COMMODITY_MATERIAL_DESCRIPTION = OFF
SPECIALTY_MATERIAL_DESCRIPTION = OFF
!
! PDtable_201 items
!
SERVICE_LIMITS_TABLE = LIST, L
NOMINAL_PIPING_DIAMETER_TABLE = LIST, D
BRANCH_TABLE = LIST, B
TAP_PROPERTIES_TABLE = DATABASE
GASKET_SEPARATION_TABLE = KEYIN
THICKNESS_DATA_TABLE = LIST, T
MATERIALS_DATA_TABLE = LIST, M
FLUID_CODE = VALUE
MATERIALS_DESCRIPTION = LIST
!BEND_DEFLECTION_TABLE = LIST, BENDEF
!PIPE_LENGTH_TABLE = LIST, PIPLEN
STANDARD_NOTE = LIST
PROMPT_FOR_TAP_ORIENTATION
!
! PDtable_202 items
!
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
Specification
5. Piping Job
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
105
________________
Reference Data Manager Reference Guide April 2002
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
106
________________ RDB Options File
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, M9
!
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
Specification
5. Piping Job
6Q3C80 = RPAD, RPAD2
6Q3C82 = RWELD, RWELD2
6Q3C84 = BWELD, BWELD2, BWELD3
6Q3C88 = NIP
6Q3C89 = NIPIL
!6Q3C95 = GASKET
!6Q3C97 = STUD
!6Q3C98 = NUT
!
!
!
VALVE_OPERATOR_LIST
!
! Handwheels
!
107
________________
Reference Data Manager Reference Guide April 2002
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.
108
________________ RDB Options File
If this keyword is not specified in the RDB options file, the default setting is OFF.
If this keyword is not specified in the RDB options file, the default setting is OFF.
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.
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
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
Specification
5. Piping Job
109
________________
Reference Data Manager Reference Guide April 2002
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
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).
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
FLUID_CODE = VALUE Specify a default fluid code value to be used for the
piping materials class.
If this keyword is not specified in the RDB options file, the default mode is that you do
not intend to define this data, unless you specify the name of a Fluid Code Table.
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
If this keyword is not specified in the RDB options file, the default mode is to key in
the value.
110
________________ RDB Options File
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
If this keyword is not specified in the RDB options file, the default mode is to key in
the table name.
If this keyword is not specified in the RDB options file, the default mode will to key in
the value of the standard note.
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.
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.
If this keyword is not included in the RDB options list, the relative tap orientation for
two taps will always be 180 degrees.
111
________________
Reference Data Manager Reference Guide April 2002
The association between a commodity name and the acceptable model codes for that
commodity name is defined as follows.
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.
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.
112
________________ Piping Materials Class Data Command
Options
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.
Specification
5. Piping Job
113
________________
Reference Data Manager Reference Guide April 2002
Field Descriptions
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, page 105 for information on defining list options for the
applicable input fields.
Refer to Piping Materials Class Data (201), page 62 for more information on the attributes
for the Piping Materials Class Data table (201).
Gasket Separation (keyin) Key in the value for the gasket separation for this piping
materials class.
OR
114
________________ Create/Revise Piping Materials Class Data
Gasket Table (keyin or list) Key in the table name or select from the list of tables
(as defined in the approved Piping Job Specification Table Library). The list of Gasket
Separation Tables will exclude the pressure rating value.
Service Limits (keyin or list) Key in the name of the Service Limits Table for this
piping materials class or select from a list of Service Limits Tables (as defined in the
approved Piping Job Specification Table Library).
Diameter (keyin or list) Key in the name of the Nominal Piping Diameter Table for
this piping materials class or select from a list of Nominal Piping Diameter Tables (as
defined in the approved Piping Job Specification Table Library).
Branch Table (keyin or list) Key in the name of the Branch Table for this piping
materials class or select from a list of Branch Tables (as defined in the approved Piping
Job Specification Table Library). The list will only include the unique tables, where the
branch angle is 90 degrees.
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 detect this problem.
Tap Data (keyin or list) Key in the name of the Tap Properties Data Table for this
piping materials class or select from a list of Tap Properties Data Tables (as defined in
PDtable_205 of the unapproved Material Reference Database).
The unapproved tap properties data is referenced, since all specification data within the
Material Reference Database is approved in one operation.
Thickness Equation (list) Select one of the displayed wall thickness equations.
The corresponding name for the thickness equation is loaded into the Piping Materials
Class Data Table.
Thickness Table (keyin or list) Key in the name of the Thickness Data Table for
this piping materials class or select from a list of Thickness Data Tables (as defined in
the approved Piping Job Specification Table Library).
115
________________
Reference Data Manager Reference Guide April 2002
Materials Data Table (keyin or list) Key in the name of the Materials Data Table
for this piping materials class or select from a list of Materials Data Tables (as defined
in the approved Piping Job Specification Table Library).
Optional Data
The following data is not 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).
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).
116
________________ Piping Commodity Data Command
Options
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, then select Accept. Select the
destination piping materials class from the displayed list and select Accept.
Specification
5. Piping Job
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.
117
________________
Reference Data Manager Reference Guide April 2002
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.
118
________________ Create/Revise Piping Commodity Specification Data
Field Descriptions
Refer to RDB Options File, page 105, for information on defining options for the applicable
input fields.
Refer to Piping Commodity Specification Data (202), page 67, 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.
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.
119
________________
Reference Data Manager Reference Guide April 2002
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.
Pressure Rating - First Size (keyin) This data is automatically set to undefined
(blank) for the branch reinforcement commodity type.
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.
You can use the Implied Data option to specify implied data for this piping
commodity. Refer to Commodity Implied Data Command, page 140 for information on
project-specific implied data. Refer to Implied Data, page 126 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).
120
________________ Create/Revise Piping Commodity Specification Data
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.
Pressure Rating - Second Size (keyin) This data is set to undefined (blank) for the
branch reinforcement commodity type.
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
Specification
5. Piping Job
and the corresponding descriptions are defined in the RDB options list.
Modifier (keyin) You can define this value for specific piping commodities not
covered by the previous list.
121
________________
Reference Data Manager Reference Guide April 2002
You can define the following optional data depending on your requirements.
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.
Joint Quality Factor (keyin) (For wall thickness calculations) In lieu of the
schedule/thickness, you can request that the wall thickness be computed automatically
by the system by specifying the joint quality factor for wall thickness calculations. The
system multiplies the joint quality factor by 100, add a *C prefix to designate that the
default calculation is to be used, and loads the value into the schedule/thickness
column. For example, if the joint quality factor is 0.95, this value will be *C095.
Note that this is not the joint quality factor that is to be used in the branch reinforcement
calculations.
Model Code (toggle) Set the toggle to By System (PIPE) or By User (*FPIPE).
122
________________ Create/Revise Piping Commodity Specification Data
E, Reinforcement (keyin) Define the joint quality factor (E) for piping for which
branch reinforcement calculations apply. The system multiplies the joint quality factor
by 100 and loads it in the modifier column.
This is not the joint quality factor that is to be used in the wall thickness calculations for
the piping.
Purchased Length (keyin) You can key in the purchased length of the piping in
sub-units. This value is stored in the PDS sort code attribute.
123
________________
Reference Data Manager Reference Guide April 2002
Gasket Thickness (keyin) Key in the gasket thickness to be reported through the
Report Manager. This value is loaded into the modifier column.
You must define the following specification data for gaskets, when the alternate gasket search
option has been enabled for MTO through the Project Data Manager. Otherwise, the input
fields will be disabled.
Alternate End Preparation (list) Select from the list of end preparation values as
defined in the approved Standard Note Library.
Alternate Table Suffix (list) Select from the list of table suffix values as defined in
the approved Standard Note Library.
You can optionally define the following data on the basis of the user-specific requirements for
gaskets.
124
________________ Create/Revise Piping Commodity Specification Data
You can optionally define the following data on the basis of user-specific requirements for
bolts.
You can optionally define the following data on the basis of user-specific requirements for
nuts.
Specification
5. Piping Job
125
________________
Reference Data Manager Reference Guide April 2002
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, page 140 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.
Field Descriptions
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 Option The commodity option code for the implied component is set to
the primary components commodity option code plus 5000.
126
________________ Implied Data
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.
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.
PDS Sort Code (keyin) (optional). The system converts the value to upper-case.
Specification
5. Piping Job
127
________________
Reference Data Manager Reference Guide April 2002
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.
128
________________ Piping Specialty Data Command
Options
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 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.
Specification
5. Piping Job
129
________________
Reference Data Manager Reference Guide April 2002
Field Descriptions
Refer to RDB Options File, page 105, for information on defining options for the applicable
input fields.
Refer to Piping Specialty Specification Data (203), page 77, 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.
130
________________ Create/Revise Piping Specialty Specification Data
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.
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.
Specification
5. Piping Job
131
________________
Reference Data Manager Reference Guide April 2002
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 depending on you requirements for piping
specialties.
132
________________ Instrument Data Command
Options
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 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.
Specification
5. Piping Job
133
________________
Reference Data Manager Reference Guide April 2002
Field Descriptions
Refer to RDB Options File, page 105, for information on defining options for the applicable
input fields.
Refer to Instrument Component Specification Data (204), page 81, for information on the
attributes for the Instrument Specification Data table.
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.
134
________________ Create/Revise Instrument Specification Data
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.
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, then select the preferred data type.
The system stores the specialty type as the input_form_type within the Piping Specialty
Specification
5. Piping Job
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.
135
________________
Reference Data Manager Reference Guide April 2002
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.
136
________________ Tap Properties Data Command
Options
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.
Specification
5. Piping Job
137
________________
Reference Data Manager Reference Guide April 2002
Field Descriptions
Refer to RDB Options File, page 105 for information on defining list options for the
applicable input fields.
Refer to Tap Properties Data (205), page 85 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.
138
________________ Create/Revise Tap Properties Data
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 taps 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, page 361, for more information on material descriptions.
Specification
5. Piping Job
Key in the material description for the specified commodity code and select Accept.
This code must be a unique index into the projects Material Description Libraries.
The system converts the specified tap material code to upper-case, then adds the
specified entry into the appropriate Material Description Libraries.
139
________________
Reference Data Manager Reference Guide April 2002
Options
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.
140
________________Create/Revise Piping Commodity Implied Material Data
Field Descriptions
Refer to RDB Options File, page 105 for information on defining list options for the
applicable input fields.
Refer to Piping Commodity Implied Material Data (212), page 91 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
5. Piping Job
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.
141
________________
Reference Data Manager Reference Guide April 2002
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, page 361, 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 projects Material Description Libraries.
142
________________
Create/Revise Piping Commodity Implied Material Data
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.
Specification
5. Piping Job
143
________________
Reference Data Manager Reference Guide April 2002
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, page 389 for more information on creating a Table Checker
report definition.
144
________________ Piping Job Specification Manager
You must have installed the applicable reference database files (such as USRDB or
DINRDB).
Use the Default Project Control Data option to set default settings for Piping
Spec Path and Piping Spec Node to point to the location of the neutral files.
The default settings are maintained in the Project Control Database.
You can also change these settings during the operation of the Piping Job Spec
Manager. However, such changes are temporary; they will not update the default
locations.
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.
Specification
5. Piping Job
145
________________
Reference Data Manager Reference Guide April 2002
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.
Toggle between Submit Immediately to submit the report for immediate processing, or
Delayed Submit to specify a time to submit the report for delayed processing.
When delayed submission is selected, you will be prompted Accept Time or Re-
specify Submit Time. Enter the day, hour, and minute, then select AM or PM.
OR
The system displays the options for the selected item. The following illustration reflects
the screen for Piping Materials Class.
146
________________ Piping Job Specification Manager
Select Option
Load, Replace, or Replace Commodity Subset from a neutral file. See page 148.
Report on the entity data (create a neutral file). See page 152
Specification
5. Piping Job
147
________________
Reference Data Manager Reference Guide April 2002
The Replace Commodity Subset option is only available for the Size
Dependent Material Data and Project Implied Material Data commands.
Refer to the database descriptions earlier in this section for a listing of the neutral file formats
used in defining the delivered PJS and material data.
Load adds the contents of the neutral file(s) to the information currently in that
database table of the Specification/Material Reference Database.
Replace deletes all entries in the respective database table and then loads new entries
from the neutral file.
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.
\win32app\ingr\pddata\sample\data
148
________________
Load, Replace, and Replace Commodity Subset Options
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.
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 list each neutral file on a separate
line. The file list.pcd contains a list of all the delivered neutral files.
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.
Specification
5. Piping Job
For Delayed Submit, set the time to process the neutral file(s).
149
________________
Reference Data Manager Reference Guide April 2002
The system submits the load/replace request as a batch job. Once the job is completed
the system sends a mail message indicating the completion status of the load (successful
or unsuccessful).
The system also creates a set of log files in the \tmp directory.
The line number that caused the failure if the neutral file was not loaded.
150
________________ Delete Option
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.
Specification
5. Piping Job
151
________________
Reference Data Manager Reference Guide April 2002
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.
Key in the name of the neutral file to be created. You can change the Node Name and
File Path information.
For Delayed Submit, set the time to process the neutral file(s).
The system creates the neutral file and a log file named specmgr.log.
152
________________ Report Option
Specification
5. Piping Job
153
________________
Reference Data Manager Reference Guide April 2002
Options
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, page 157.
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, page
163.
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, page
173.
154
________________ Using the Report Commands
Using the Report Format option, you can create a numbered record for each format file so
that it can be accessed for report processing. The format record is a record in the Project
Control Database used to name and locate a specific format file. Unlike the format file, the
format record is created interactively. It is called a record to classify it as a block of data that
is used for report processing but is not an actual file.
The discrimination data record is a record in the Project Control Database used to name and
locate a specific discrimination data file. There is a uniquely-numbered record for each
discrimination data file so that it can be accessed for report processing. This is the same way
that the format record is used to access a format file.
The report record names or defines locations for all of the files that are necessary to generate a
report, including the report output. (It is called a record to classify it as a block of data that is
used for report processing but is not an actual file.)
155
________________
Reference Data Manager Reference Guide April 2002
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.
156
________________ Report Format Form
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 files
location has been entered into the project control database.
Options
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, page 159.
Specification
5. Piping Job
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, page
159.
157
________________
Reference Data Manager Reference Guide April 2002
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, page 161.
158
________________ Format Creation/Revision Form
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.
Field Descriptions
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.
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.
You must have created an ASCII format file. A set of basic format files is delivered with the
PD_Report product in the win32app\ingr\pddata\sample\format directory. The file for
Spec Reporting reporting is named piping_rdb.fmt.
For more information on the delivered sample format files, see the PD_Report Users Guide.
159
________________
Reference Data Manager Reference Guide April 2002
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.
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.
Type information in each of the displayed fields, taking care to press return in each
field. Then select Accept.
160
________________ Format Deletion 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.
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.
Specification
5. Piping Job
Operating Sequence
1. Select Report Format
161
________________
Reference Data Manager Reference Guide April 2002
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.
162
________________ Report Discrimination Data Form
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.
Options
Create Displays the Discrimination Data Creation form, which creates a new
discrimination data file. The associated project control database record is also created.
Specification
5. Piping Job
For more information, see Discrimination Data Creation Form, page 165.
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, page 169.
163
________________
Reference Data Manager Reference Guide April 2002
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, page 171.
164
________________ Discrimination Data Creation Form
Commands
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
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.
Specification
5. Piping Job
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.
165
________________
Reference Data Manager Reference Guide April 2002
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.
166
________________ Search Criteria Form
If you do not restrict the piping materials class attribute for Piping Commodity
Data, all piping materials classes will be reported.
Operating Sequence
1. Select the Search Criteria option from the Discrimination Data form.
2. Select Entity
The system displays the selected attribute and displays a list of operators.
167
________________
Reference Data Manager Reference Guide April 2002
4. Select Operator
The system displays the selected operator and prompts you to key in an 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.
OR
168
________________ Discrimination Data Revision Form
First, the system displays the Record Number display list as shown below on the left. After
you select and Accept the discrimination data file you need, the system then displays the
discrimination data identification fields. These fields are used to define the record as shown
below on the right.
Commands
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Field Descriptions
Number Key in a unique number to name the discrimination data record with up to
Specification
5. Piping Job
24 characters in the Project Control Database. This number is a short name to identify
the record of the discrimination data file.
File Specification Key in the filename of the discrimination data file to reference.
169
________________
Reference Data Manager Reference Guide April 2002
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.
170
________________ Discrimination Data Deletion 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.
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.
Specification
5. Piping Job
Operating Sequence
1. Select Report Format
171
________________
Reference Data Manager Reference Guide April 2002
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.
172
________________ Report Form
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.
Specification
5. Piping Job
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.
173
________________
Reference Data Manager Reference Guide April 2002
Options
Create Displays the Report Creation form, which creates a report record and
generates a report. For more information, see Report Creation Form, page 175.
Revise Displays the Revise Report form, which regenerates a report from an
existing or revised report record. For more information, see Revise Report Form, page
178.
Delete Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form, page 181.
Approve Displays the Report Approval form, which approves an existing report.
For more information, see Report Approval Form, page 183.
Multi-Create Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form, page
184.
174
________________ Report Creation Form
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 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).
Specification
5. Piping Job
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 Dataform. For more information, see Report Management
Defaults Form, page 186.
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, page 186.
175
________________
Reference Data Manager Reference Guide April 2002
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.
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.
176
________________ Report Creation Form
Operating Sequence
1. From the Report form, select Create.
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.
Specification
5. Piping Job
177
________________
Reference Data Manager Reference Guide April 2002
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 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.
178
________________ Revise Report Form
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.
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.
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
Specification
5. Piping Job
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
Data Only, 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.
179
________________
Reference Data Manager Reference Guide April 2002
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.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
180
________________ Report Deletion 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.
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.
Specification
5. Piping Job
Operating Sequence
1. Select Report Format
181
________________
Reference Data Manager Reference Guide April 2002
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.
182
________________ Report Approval Form
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.
Options
Number The 24-character unique name (also called short name) of the report record.
Operating Sequence
1. From the Report form, select Approve.
2. From the displayed list, select a report to approve. Then click Accept.
For more information, see the Approve Report section of the PD_Report Users
Guide.
183
________________
Reference Data Manager Reference Guide April 2002
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.
184
________________ Report Multiple Submit Form
Operating Sequence
1. From the Report form, select Multi-Create.
From the displayed list, select the reports to submit. Highlighed 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.
Specification
5. Piping Job
185
________________
Reference Data Manager Reference Guide April 2002
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.
Fields
Report Path Specifies the default path of the report output files.
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.
186
________________ Report Management Defaults Form
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.
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.
Specification
5. Piping Job
187
________________
Reference Data Manager Reference Guide April 2002
188
________________ Piping Job Specification Tables
These libraries contain the Piping Job Specification tables and the other special tables which
contain nonphysical data.
The data in the Spec Table Library falls into two basic categories.
RDB Tables - Referenced in the Component Placement and Material TakeOff forms
of the Project Data Manager. See page 215.
You can use the Piping Job Specification Tables command to create a new Piping Job
Specification Table library or to create, modify, or delete tables in an existing library. See
page 239.
Spec Tables
6. Piping Job
189
________________
Reference Data Manager Reference Guide April 2002
190
________________ Temperature and Pressure Service Limits Table
You can define both positive and negative values for temperature. However, you can only
define positive values for pressure. The units of measure for the pressure and temperature
values in the table are defined as a part of the table description.
The highest temperature from the TDB does not exceed the highest temperature value in
the table
The lowest temperature in the TDB is not less than the lowest value in the table
For a given temperature, the pressure from the table is not less than any of the
corresponding pressure(s) from the TDB.
191
________________
Reference Data Manager Reference Guide April 2002
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:
third, fourth, and fifth characters: numbers from 001 through 999 used to make the
table name unique.
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.
192
________________ Temperature and Pressure Service Limits Table
Pressure (real) This field identifies the value for pressure corresponding to the
previously defined temperature. Negative (-) values are not accepted in this field.
Spec Tables
6. Piping Job
193
________________
Reference Data Manager Reference Guide April 2002
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
194
________________ Nominal Piping Diameters Table
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
195
________________
Reference Data Manager Reference Guide April 2002
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.
196
________________ Thickness Data Tables
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 - - -
Spec Tables
6. Piping Job
197
________________
Reference Data Manager Reference Guide April 2002
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.
third character: the corrosion allowance of the piping materials class for which the
table is intended, per the following criteria:
fourth and fifth characters: numbers from 01 through 99 used to make the table
name unique.
Diam - Nominal Piping Diameter (integer) This parameter identifies the desired
value for nominal diameter.
198
________________ Thickness Data Tables
Min Thick - Minimum Required Thickness (real) This parameter represents the
least thickness, inclusive of corrosion allowance and mill tolerance, which is acceptable
for a given NPD. Either a positive number or a blank entry must be provided. This
value is only used in piping wall thickness calculations.
Ret Thick - Retirement Thickness (real) This parameter represents the least
thickness, exclusive of corrosion allowance, thread allowance, or mill tolerance, which
is acceptable for a given NPD. Either a positive number or a blank entry must be
provided. This value is only used in piping wall thickness calculations.
Thread Thick - Thread Thickness (real) This parameter represents the thickness
for threaded pipe that must be added to the calculated wall thickness to account for the
presence of threads. Either a positive number or a blank entry must be provided. It is
only used in piping wall thickness calculations.
Spec Tables
6. Piping Job
199
________________
Reference Data Manager Reference Guide April 2002
Note that you can express the mill tolerance as either a thickness percentage or a tolerance
value. Only one value can exist per table entry. If values exist for both, the system only uses
the mill thickness percentage.
The system uses the materials grade and temperature to access the information in the table and
provide the values of thickness range, coefficient Y, allowable stress (S), and the applicable
mill tolerance. Once the actual thickness is calculated for the component, the calculation
software compares that value with the thickness range. If the thickness range is exceeded, the
next entry in the materials table for the applicable materials grade and temperature is sought
and the calculation process is repeated.
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
200
________________ Materials Data Table
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 -
142 200 - - .4 20000 12.5 -
142 300 - - .4 20000 12.5 -
142 400 - - .4 20000 12.5 -
142 500 - - .4 18900 12.5 -
142 600 - - .4 17300 12.5 -
142 650 - - .4 17000 12.5 -
142 700 - - .4 16500 12.5 -
142 750 - - .4 13000 12.5 -
142 800 - - .4 10800 12.5 -
162 -20 - - .4 20000 12.5 -
162 100 - - .4 20000 12.5 -
162 200 - - .4 20000 12.5 -
162 300 - - .4 20000 12.5 -
162 400 - - .4 20000 12.5 -
162 500 - - .4 18900 12.5 -
162 600 - - .4 17300 12.5 -
162 650 - - .4 17000 12.5 -
162 700 - - .4 16500 12.5 -
162 750 - - .4 13000 12.5 -
162 800 - - .4 10800 12.5 -
116 -20 - - .4 20000 12.5 -
116 100 - - .4 20000 12.5 -
116 200 - - .4 20000 12.5 -
116 300 - - .4 20000 12.5 -
116 400 - - .4 20000 12.5 -
116 500 - - .4 18900 12.5 -
116 600 - - .4 17300 12.5 -
116 650 - - .4 17000 12.5 -
116 700 - - .4 16500 12.5 -
116 750 - - .4 13000 12.5 -
116 800 - - .4 10800 12.5 -
END
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:
201
________________
Reference Data Manager Reference Guide April 2002
third and fourth characters: numbers from 01 through 99 used to make the table
name unique.
Temp - Temperature (real) This field identifies the applicable temperature for a
set of material properties.
Range - Wall Thickness Range - high (real) These fields identify the lower and
upper wall thickness bounds for a set of material properties. You can enter positive
numbers or blanks. A blank indicates that the properties apply regardless of the
thickness of the component. You cannot define this range in terms of schedule.
Mill Tol % - Mill Thickness Percentage (real) This parameter represents the per
cent of the wall thickness that is to be considered as mill tolerance for pipe material.
Enter the mill tolerance to be considered for the material as a percent of nominal
thickness; such as 12.5%.
Mill Tol Value - Mill Thickness Value (real) This parameter represents the actual
wall thickness that is to be considered as mill tolerance for plate material. Enter the
value of mill tolerance to be considered for the material; such as 0.01 inch.
202
________________ Wall Thickness and Branch Reinforcement Equations
Thickness equations have project unique names which must follow the following convention:
first character: E
second character: the applicable design code, per the following convention:
third and fourth characters: numbers from 01 through 99 used to make the equation
name unique.
Spec Tables
6. Piping Job
203
________________
Reference Data Manager Reference Guide April 2002
Delivered Equations
The thickness and branch reinforcement logic for the following equations are hardcoded in the
software.
EJ01
PD
tm = _________ + A
2(SE+Py)
EL01
PD
t = _________
2(SE+PY)
where
P Design pressure
D Pipe outside diameter
S Allowable stress read from the Materials table
E Joint quality factor determined from the wall thickness attribute Cxxx where
xxx is 100 times E
Y Coefficient Y read from the Materials table
A Additional Thickness (in inches)
Refer to the spec access example below for more information on how the wall thickness
equation is used to determine the actual wall thickness value.
General Considerations
The following considerations apply to both thickness equations and branch reinforcement
calculations.
204
________________ Delivered Equations
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. Refer to the descriptions of the
Temperature-Pressure Table and Materials Table to insure consistency between units of
measure. Conversions are performed using the procedures and conversion factors
defined for the Units of Measure in the PDS Piping Component Data Reference Guide.
Only positive pressure is considered. The system reports an error if you request a
thickness calculation involving a vacuum condition (negative pressure).
Thickness Equations
The following considerations apply to thickness equations.
yyy is 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 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
be calculated, as determined by specific *Cyyy entries in the Piping Commodity
Specification Data table. 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 *Cyyy, 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 *Cyyy, 24"
end and a *Cyyy, 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.
Spec Tables
6. Piping Job
205
________________
Reference Data Manager Reference Guide April 2002
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 *Cyyy made
under the Schedule Thickness attribute for the Commodity Item under consideration.
Branch Reinforcement
The following considerations apply to branch reinforcement calculations.
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.
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.
Once 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 design database.
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
206
________________ Delivered Equations
Spec Tables
6. Piping Job
207
________________
Reference Data Manager Reference Guide April 2002
Branch tables define the reinforcement to be used at tee and lateral branches in the piping
system as a function of the acute angle of intersection and the nominal diameters for the
intersecting lines. These tables do not include the reinforcement required at Ys and crosses.
For them, the required reinforcement must be specified in Piping Design.
The types of tee branch connections include branch weld, coupling, threadolet, reducing tee,
tee with reducing insert, nipolet, branch weld with reinforcing pad, sockolet, tee, weldolet, tee
with reducing bushing, and reducing tee with reducer(s).
The system accesses the branch table when placing a component at an intersection when no
reinforcement component has been specifically defined.
The system uses the information in this table and the header nominal diameter (first size) and
branch nominal diameter (second size) to provide the item name of the component to be used
at the intersection. Neither interpolation nor extrapolation is allowed.
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
208
________________ Branch Insertion Tables
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
! Header Branch AABBCC Codes
0.75 0.75 6Q3C22 - -
1 0.75 6Q3C24 - -
1 1 6Q3C22 - -
1.5 0.75 6Q3C24 - -
1.5 1 6Q3C24 - -
1.5 1.5 6Q3C22 - -
2 0.75 6Q3C74 - -
2 1 6Q3C74 - -
2 1.5 6Q3C74 - -
2 2 6Q3C22 - -
3 0.75 6Q3C74 - -
3 1 6Q3C74 - -
3 1.5 6Q3C74 - -
> 3 2 6Q3C73 - -
3 3 6Q3C22 - -
4 0.75 6Q3C74 - -
4 1 6Q3C74 - -
4 1.5 6Q3C74 - -
> 4 2 6Q3C73 - -
> 4 3 6Q3C73 - -
4 4 6Q3C22 - -
6 0.75 6Q3C74 - -
6 1 6Q3C74 - -
6 1.5 6Q3C74 - -
> 6 2 6Q3C73 - -
> 6 3 6Q3C73 - -
> 6 4 6Q3C73 - -
6 6 6Q3C22 - -
8 0.75 6Q3C74 - -
8 1 6Q3C74 - -
8 1.5 6Q3C74 - -
> 8 2 6Q3C73 - -
> 8 3 6Q3C73 - -
> 8 4 6Q3C73 - -
> 8 6 6Q3C73 - -
8 8 6Q3C22 - -
10 0.75 6Q3C74 - -
10 1 6Q3C74 - -
10 1.5 6Q3C74 - -
> 10 2 6Q3C73 - -
> 10 3 6Q3C73 - -
> 10 4 6Q3C73 - -
10 6 6Q3C82 - -
10 8 6Q3C82 - -
10 10 6Q3C22 - -
12 0.75 6Q3C74 - -
12 1 6Q3C74 - -
12 1.5 6Q3C74 - -
> 12 2 6Q3C73 - -
> 12 3 6Q3C73 - -
> 12 4 6Q3C73 - -
12 6 6Q3C82 - -
12 8 6Q3C82 - -
12 10 6Q3C82 - -
12 12 6Q3C22 - -
END
Spec Tables
6. Piping Job
209
________________
Reference Data Manager Reference Guide April 2002
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.
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.
third character: the corrosion allowance of the piping materials class for which the
table is intended, per the following criteria:
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).
210
________________ Branch Insertion Tables
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.
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.
Weld-in components actually making the intersection such as laterals and tees.
Spec Tables
6. Piping Job
211
________________
Reference Data Manager Reference Guide April 2002
For each bolted end, the system uses the applicable table, the NPD of the end, and the
maximum temperature for the gasket to be used at the end, to determine the gap thickness to
be used at the end. Lines in this table are sorted by NPD first and maximum temperature
second.
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
0.75 1001 .16
1 1001 .16
1.5 1001 .16
2 1001 .12
3 1001 .12
212
________________ Gasket Separation Table
4 1001 .12
6 1001 .12
8 1001 .16
10 1001 .16
12 1001 .19
14 1001 .22
16 1001 .31
18 1001 .31
20 1001 .38
24 1001 .44
END
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.
Spec Tables
6. Piping Job
213
________________
Reference Data Manager Reference Guide April 2002
Specify the name of the Fluid Code Table in the fluid_code attribute of the Piping
Materials Class definition.
Set the Fluid Code Control toggle to Yes on the Piping Data Control form of the
Project Data Manager. Refer to the Project Administrator (PD_Project) Reference
Guide for more information on this form.
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:
third, forth, and fifth characters: numbers from 001 to 999 used to make the table
name unique.
Fld Cd (integer) This field list the code list numbers for the valid fluid codes from
code list set 125.
214
________________ RDB Tables
G02 COMMODITY_ITEM_NAME
G04 BEND_DEFLECTION
G06 PIPE_RUN_LENGTH
G07 PIPE_LENGTH
G11 BOLT_LENGTH
WELD_TYPE_TABLE
WELD_C10031
DRV_WELD_DEF
FIELD_FIT_LENGTH
Component_Mirror_Table
Operator_Mirror_Table
Default_End_Prep
The system uses the settings in the Component Placement and Material TakeOff forms of the
Project Data Manager to determine the applicable names for these basic tables.
Refer to Table Formats and Naming Conventions, page 303, for information
on the basic conventions used for PDS tables.
Spec Tables
6. Piping Job
215
________________
Reference Data Manager Reference Guide April 2002
When placing change of direction components, this table is used in conjunction with the Bend
Deflection Table.
TNF=G02 COMMODITY_ITEM_NAME
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 -
216
________________ Commodity Item Name Table (G02)
35 -
36 -
37 -
38 IND
39 -
40 -
41 6Q2C49
42 6Q2C51
43 6Q2C53
44 6Q2C06
45 6Q3C89
END
217
________________
Reference Data Manager Reference Guide April 2002
If you do not want to place one of the above component types as part of automatic component
placement, place a hyphen (-) for the Item Name.
218
________________ Bend Deflection Table (G04)
index into the Commodity Item Name table for a full size bend
index into the Commodity Item Name table for a reducing bend
This table defines which full size and reducing size component types will be placed for a
specified angle range. The angle is defined as the smallest angle that the continuation of one
pipe run makes with the other run. The component types are defined in the commodity item
name table. (See Commodity Item Name Table (G02), page 216.) A value of 0 for the type
indicates that no reducing component should be placed for an angle range.
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.
TNF=G04 BEND_DEFLECTION
Spec Tables
6. Piping Job
219
________________
Reference Data Manager Reference Guide April 2002
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.
220
________________ Segment Pipe Run Length Threshold Table (G06)
The Piping Designer insures that the length of any pipe run of a piping segment exceeds the
active segment run length threshold. The threshold is determined from this table as a function
of nominal piping diameter. The only exception to this is for the small pipe run required for
the offset of an eccentric reducer. This threshold is used to insure that the pipe run between
two connected bends exceeds the fabrication length of the two bends.
Diam
Entry Range of Diameters Covered
n1 nominal diameter < n1
n2 n1 <= nominal diameter < n2
n3 n2 <= nominal diameter < n3
....
n8
n9 n8 <= nominal diameter
Using this scheme, you should look on the line following the actual segment NPD to
determine the minimum length. Only lengths greater than the minimum length in the table are
allowed. For example, if you are placing a segment with 12 inch NPD, you can only place
segments greater than .75 inches in length.
TNF=G06 PIPE_RUN_LENGTH
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
Spec Tables
6. Piping Job
221
________________
Reference Data Manager Reference Guide April 2002
The Piping Designer insures that the length of any pipe or tube exceeds the pipe length
threshold, as defined in this table. The threshold is determined as a function of the nominal
piping diameter. This table is used during model creation and model revision activities to
verify the nominal or theoretical pipe (or tube) length.
Diam
Entry Range of Diameters Covered
n1 nominal diameter < n1
n2 n1 <= nominal diameter < n2
n3 n2 <= nominal diameter < n3
....
n8
n9 n8 <= nominal diameter
Using this scheme, you should look on the line following the actual NPD to determine the
minimum length. Only lengths greater than the minimum length in the table are allowed. For
example, if you are placing a pipe with 12 inch NPD, you can only place pipe runs greater
than 3 inches in length.
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
END
222
________________ Preferred Bolt Length Table (G11)
Refer to the Report Manager Reference Guide for more information on bolt tables and bolt
table logic.
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
Spec Tables
6. Piping Job
223
________________
Reference Data Manager Reference Guide April 2002
224
________________
Preferred Bolt Length Table (G11)
26.7501 27 27
27.0001 27.25 27.25
27.2501 27.5 27.5
27.5001 27.75 27.75
27.7501 28 28
28.0001 28.25 28.25
28.2501 28.5 28.5
28.5001 28.75 28.75
28.7501 29 29
29.0001 29.25 29.25
29.2501 29.5 29.5
29.5001 29.75 29.75
29.7501 30 30
30.0001 30.25 30.25
30.2501 30.5 30.5
30.5001 30.75 30.75
30.7501 31 31
31.0001 31.25 31.25
31.2501 31.5 31.5
31.5001 31.75 31.75
31.7501 32 32
32.0001 32.25 32.25
32.2501 32.5 32.5
32.5001 32.75 32.75
32.7501 33 33
33.0001 33.25 33.25
33.2501 33.5 33.5
33.5001 33.75 33.75
33.7501 34 34
34.0001 34.25 34.25
34.2501 34.5 34.5
34.5001 34.75 34.75
34.7501 35 35
35.0001 35.25 35.25
35.2501 35.5 35.5
35.5001 35.75 35.75
35.7501 36 36
END
Spec Tables
6. Piping Job
225
________________
Reference Data Manager Reference Guide April 2002
WELD_TYPE_TABLE
Example
Table_Data_Definition Weld_Type_Table
! This Table nas NOT been Checked
No_Inputs 2 No_Outputs 1
Units= INT, INT, INT
1 1 1
1 5 21
1 7 21
1 15 21
1 16 21
1 17 21
1 25 21
1 27 21
1 35 21
1 37 21
1 45 21
1 47 21
1 95 21
1 97 21
5 5 11
5 7 21
5 15 11
5 16 21
5 17 21
5 25 11
5 27 21
5 35 11
5 37 21
5 45 11
5 47 21
5 95 11
5 97 21
7 7 21
7 15 21
7 16 21
7 17 21
7 25 21
7 27 21
7 35 21
7 37 21
7 45 21
7 47 21
7 95 21
7 97 21
15 15 11
15 16 21
15 17 21
15 25 11
226
________________
Weld Type Table
15 27 21
15 35 11
15 37 21
15 45 11
15 47 21
15 95 11
15 97 21
16 16 12
16 17 21
16 25 21
16 27 21
16 35 21
16 37 21
16 45 21
16 47 21
16 95 21
16 97 21
17 17 21
17 25 21
17 27 21
17 35 21
17 37 21
17 45 21
17 47 21
17 95 21
17 97 21
25 25 11
25 27 21
25 35 11
25 37 21
25 45 11
25 47 21
25 95 11
25 97 21
27 27 21
27 35 21
27 37 21
27 45 21
27 47 21
27 95 21
27 97 21
35 35 11
35 37 21
35 45 11
35 47 21
35 95 11
35 97 21
37 37 21
37 45 21
37 47 21
37 95 21
37 97 21
45 45 11
45 47 21
45 95 11
45 97 21
47 47 21
47 95 21
47 97 21
95 95 11
95 97 21
97 97 21
Spec Tables
6. Piping Job
227
________________
Reference Data Manager Reference Guide April 2002
WELD_SpecName
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.
Overall_Length (integer) This parameter identifies the length of the cylinder for
the weld construction tolerance envelope.
228
________________ Weld Graphics Dimensions Table
DRV_WELD_DEF
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
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.
229
________________
Reference Data Manager Reference Guide April 2002
If you define a bolt commodity code which is less than 17 characters, you should code a
hyphen (-) in the third column.
Cmdty Code_BLT
230
________________ Gasket Diameter Table
Cmdty Code_GKT
Spec Tables
6. Piping Job
231
________________
Reference Data Manager Reference Guide April 2002
This table is only used if the Field Fit Length option is activated on the Material Takeoff
Options form in the Project Data Manager. MTO reads the specified table and increases the
pipe length at each welded end of the pipe based on the weld type at that specific end.
No_Inputs 1 No_Outputs 1
Units= INT, IN
1 ZZZZZZZ
11 ZZZZZZZ
21 ZZZZZZZ
22 ZZZZZZZ
232
________________ Component Mirror Table
Example
Table_Data_Definition Component_Mirror_Table
No_Inputs 1 No_Outputs 3
Units= AN*6, INT, INT, INT
Parameters
Model Code This columns list the model codes for components which require non-
symmetrical mirroring. The model codes is used as input by the calling Eden module.
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.
The Model Code item will be rotated due to a specific non symmetrical definition
where there are no non symmetrical connect points involved.
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.
233
________________
Reference Data Manager Reference Guide April 2002
Example
Table_Data_Definition Operator_Mirror_Table
No_Inputs 1 No_Outputs 3
Units= AN*6, INT, INT, INT
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 columns list the model codes for operator which support
mirroring. The model codes is used as input by the calling Eden module.
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.
234
________________ Operator Mirror Table
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.
Spec Tables
6. Piping Job
235
________________
Reference Data Manager Reference Guide April 2002
The system looks for a table with the name Default_End_Prep in the spec table library.
If the table does not exist in the library, the end prep for the instrument/specialty
defaults to the end prep of the connected piping component.
If the table exists in the spec table library and the active placement point is connected to
previously placed piping or a nozzle, the end preparation for the instrument or piping
specialty is set based on entries in the table.
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).
236
________________ MTO Tables and Functions
Spec Tables
6. Piping Job
237
________________
Reference Data Manager Reference Guide April 2002
238
________________ Piping Job Specification Tables Command
The spec tables for US practice are delivered in the file us_pjstb.l in the RDUSRDB product
directory.
The system tracks revision dates for table entries when a table is revised. This revision
management data is recorded in a separate Table Revision Management Library, named
<table_library>.l.r. If the library has been removed or deleted, the software regenerates the
library file.
With the 4.2 release, the limitation on the size of tables in the Piping Job Spec Table Library
was increased from approximately 16,000 bytes per table to 20,000 bytes per table.
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.
You must have write access to the specified file and directory path.
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.
Spec Tables
6. Piping Job
239
________________
Reference Data Manager Reference Guide April 2002
6.3.1 Options
Create Library used to create a new Piping Job Spec Table Library. See page
242.
Compress Library used to compress the Piping Job Spec Table library. See page
242.
Unapproved ==> Approved used to copy the unapproved Piping Job Spec Table
library to the approved library. See page 242.
Create/Interactive 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. See page 243.
Create/Batch used to compile and add tables to the library via batch processing.
See page 244.
Revise used to select a table from the library for editing and compile the revised
table definition. See page 245.
Delete used to delete a specified table from the library. See page 247.
Report used to create a report of the library contents. See page 248.
List used to list the files contained in the library. See page 250.
Extract used to extract a table file from the library for editing or printing. See
page 251.
240
________________ Piping Job Specification Tables Command
Field Descriptions
Refer to Default Project Control Data, page 53, for information on defining the default
location for library files. You can also change the default file locations for each option at any
time.
Spec Tables
6. Piping Job
241
________________
Reference Data Manager Reference Guide April 2002
The system displays the approved and unapproved Piping Job Spec Table Library names as
defined in the RDB Management Data.
Select Accept to create the specified library files. If you specify an existing library file, the
system displays an error indicating the library already exists.
Select Accept to copy the unapproved library file to the approved library.
242
________________ Create/Interactive Spec Tables
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.
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, page 190, for information on the table
formats.)
Spec Tables
6. Piping Job
243
________________
Reference Data Manager Reference Guide April 2002
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.
Key in the name of the table file or list file to be added to the active library.
For Delayed Submit, set the time to process the table files.
244
________________ Revise Spec Tables
Operating Sequence
1. Select the Revise option from the Specification Tables Library/Data Management form.
3. The system extracts the specified table from the library and activates the text editor
(specified for PD_EDITOR in the control.sh file) to enable you to modify the file.
Spec Tables
6. Piping Job
245
________________
Reference Data Manager Reference Guide April 2002
When you exit the text editor, the system compiles the revised file and inserts it back
into the library.
If an error occurs in revising a table, the editor screen is invoked automatically to give
you an opportunity to correct the problem.
246
________________ Delete Spec Tables
Operating Sequence
1. Select the Delete option from the Specification Tables Library/Data Management form.
Select the table files to be deleted from the list of tables. You can use the scroll bar to
scroll through the available tables.
The system deletes the tables from the Spec Table Library. Spec Tables
6. Piping Job
247
________________
Reference Data Manager Reference Guide April 2002
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.
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.
248
________________ Report on Spec Tables
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.
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set
the time to process the request.
Spec Tables
6. Piping Job
249
________________
Reference Data Manager Reference Guide April 2002
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.
250
________________ Extract Spec 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.
Spec Tables
6. Piping Job
251
________________
Reference Data Manager Reference Guide April 2002
252
________________ Graphic Commodity Data
Commodity Data
7. Graphic
The graphic commodity data is contained in the following object libraries:
Refer to Reference Data Overview, page 23, for an illustration of the relationships among
these libraries.
When you select a component for placement in the model, the system
uses the active parameters (such as piping materials class and nominal diameter) to
search the Piping Job Specification (PJS) for the selected item name. If the selected
item is found in the PJS database, the system reads the PJS for the parameters required
to place the component. Included in this information is the model code (or specialty
item number) for the selected component and the names of the spec tables defined for
the Piping Materials Class.
uses the model code (or specialty item number), derived from the PJS, to access the
graphic commodity library. The definitions in the graphic commodity library determine
the physical tables required to place the component and call the tables in the physical
commodity library.
places the symbol graphics in the model design file and writes the nongraphic
information for the component in the database.
This section describes the graphic commodity data used in placing components in the piping
model. Refer to the Piping Design Graphics Reference Guide for a detailed description of the
actual placement process.
253
________________
Reference Data Manager Reference Guide April 2002
determine physical data based on user specifications (such as NPD and end preparation)
define the parametric shape for the model graphics. The Graphic Commodity Library
includes data required for model creation, resymbolization for model presentation,
interference detection, and any special functions of the Piping Job Specification, piping
industry standards, or company design practices.
PDS Piping uses the Eden Parametric Language to define and place components, specialty
items, operators, and envelopes. Eden is a high- level language (similar to FORTRAN) which
uses information from the Piping Job Specification and model to access parametric and
dimensional data.
Symbol Processors
These modules are designed to carry out two functions: data definition and graphic
presentation.
The data associated with these modules is delivered in the following files:
The modular approach provides for more efficient storage of information in these libraries by
enabling common information to be shared by different symbols.
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.
254
________________ Graphic Commodity Library
Commodity Data
7. Graphic
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
IG Interference Envelope Parametric Shape
Definition Module
SS Sub-Symbol Processor Module
Each module must be given a unique name within the graphic commodity library. Refer to
the PDS Eden Interface Reference Guide for information on creating or modifying these
modules.
255
________________
Reference Data Manager Reference Guide April 2002
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.
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.
256
________________ Symbol Processors
Commodity Data
7. Graphic
physical_data_source = V1 // Standard_Type
Call Get_Physical_Data ( physical_data_source )
parametric_shape = V1
Call Draw_Parametric_Shape ( parametric_shape )
Valve_Operator = DABS ( Valve_Operator )
If ( Valve_Operator .NE. 0 ) Then
If ( Valve_Operator .LT. 1000 ) Then
Subcomponent = OP // Valve_Operator
Else
Subcomponent = A // Valve_Operator
EndIf
Operator_Orient = FALSE
EndIf
Stop
End
257
________________
Reference Data Manager Reference Guide April 2002
The first line of a sub-symbol processor module indicates the module type and the 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
258
________________ Physical Data Definitions
Commodity Data
7. Graphic
The system uses the physical data definitions to determine the dimension data, weight data,
and surface area data using the active design parameters. Physical data modules are identified
by the statement
as the first line in the Eden module. This statement tells the system to use the category code
PD for the prefix. This prefix is only used by the system; it should not be keyed-in as part of
the module name.
The module name for a physical data module consists of a symbol type (such as V1, V2,... for
valves) and a generic type of geometric industry standard (such as AMS or DIN). You can
define multiple physical data modules for the same symbol depending on the type of standard
being referenced (for example, V1_AMS for American standards and V1_DIN for European
standards).
You can manage ten different sets of logic for table naming conventions for the following
industry practices. The corresponding table suffix ranges and the suffix for the Piping Eden
physical data modules are indicated below.
The geometric industry standard for a component is defined in the Piping Commodity Data
table of the Material Reference Database. Each component must be assigned a geometric
industry standard if it is to use physical data tables.
For most of the delivered symbols, the physical data modules are classified into two
categories: specific and generic. The specific physical data module is called by the symbol
processor. This module then calls a generic physical data module.
259
________________
Reference Data Manager Reference Guide April 2002
Physical_Data_Definition V1_AMS
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
260
________________ Physical Data Definitions
Commodity Data
7. Graphic
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
261
________________
Reference Data Manager Reference Guide April 2002
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
! Male X Male or Bolted X Bolted
! or Female X Female
Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 //
Pr_Rating_2 // A
Else
262
________________ Parametric Shape Definitions
Commodity Data
7. Graphic
The parametric shape definition describes the graphics symbol (such as bend, flange, or valve
body) which is placed for the component in the model.
Parametric shape definitions are used to place symbol graphics in the model or define
interference envelopes. This involves the following major functions
Parametric shape definitions are divided into three basic types: model parametric shapes,
detailed parametric shapes, and interference envelopes. The first line of the Eden module
indicates the module type and the module name.
This statement tells the system to use the category code MG for the prefix. This prefix is only
used by the system; it should not be keyed- in as part of the module name.
The module name for a parametric shape module consists of a symbol type (such as V1, V2,...
for valves).
The parametric shape module MGV1 determines the model graphics for a valve. This is the
module called by the symbol processor SPGAT. The parametric shape module MGOP3
determines the model graphics for a hand wheel operator. This is the module called by the
sub-symbol processor SSOP_3.
263
________________
Reference Data Manager Reference Guide April 2002
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
This statement tells the system to use the category code DG for the prefix.
264
________________ Parametric Shape Definitions
This statement tells the system to use the category code IG for the prefix.
Commodity Data
7. Graphic
If no interference module is found for a component, the system uses the model
graphics module to determine the interference parametric shape.
265
________________
Reference Data Manager Reference Guide April 2002
The physical data tables for US Practice are delivered in the following files:
These libraries contain physical data for American standards. The physical data can be stored
in one of ten physical data libraries. The system uses the geometric industry standard for a
particular commodity item (or specialty item) to determine which library to reference for the
physical data tables.
Geometric industry standard is expressed as a code list value from Standard Note Type 575.
Code list numbers 2-6999 are reserved for standards that apply to American piping practices.
Code list numbers 7000-27999 are reserved for standards that apply to European piping
practices. Numbers 28000-31999 are reserved for specific company practices.
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 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).
The system uses the water weight data to compute the wet weight using the specific
gravity of the operating fluid.
266
________________ Physical Data Tables
The surface area data enables the system to perform paint requirement calculations
and insulation weight calculations.
Commodity Data
7. Graphic
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.
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.
267
________________
Reference Data Manager Reference Guide April 2002
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
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, page 315, 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)
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.
268
________________ Example of Physical Data Look-Up
VAABAHCCAA
This table returns the empty weight of the valve, including the weight of the operator.
Commodity Data
7. Graphic
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.
269
________________
Reference Data Manager Reference Guide April 2002
For full-size components, data is only defined for the green connect point and applies to
all ends of the component.
For size change components, data for commodity items, engineered items, or
instruments should be created with the green connect point representing the larger
diameter (first size) of the component and the red connect point diameter representing
the smaller diameter (second size).
If the end preparation is different at each end of the component, the end preparation
should be defined to match the green and red connect points.
If a component has ends with the same nominal diameter but other end properties which
differ, the following rules apply:
If the ends have different end preparations (regardless of the values for
schedule/thickness) the end(s) whose end preparations have the lowest code list
number are designated as the green connect point.
If the end preparations are the same but the values for rating, schedule, or thickness
differ, the "stronger" ends(s) are designated as the green connect point.
Schedule or thickness values should be defined for all applicable components. Refer to
PJS Tables and Functions, page 190, for a detailed description of the methods for
defining the schedule or thickness value.
A flow direction component (such as a check valve) must be defined so that the flow is
directed from connect point 1 to connect point 2.
A tee type branch must be defined with connect point three on the branch leg of the tee.
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.
270
________________ Notes for Graphic Commodity Data
A valve operator is always placed at the component origin of the corresponding valve
body.
Commodity Data
7. Graphic
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.
The number of joints in a mitre is required to compute the stress intensification factor
(SIF). The graphics symbol description in the Graphic Commodity Library sets an
attribute in the piping design database that defines the number of joints.
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.
271
________________
Reference Data Manager Reference Guide April 2002
A lap joint flange is defined with the end preparation at one end as flanged and the other
end as lap.
The system determines the gasket separation at each connect point of a piping
component and an instrument component by the following rules.
If the end preparation for the connect point is flanged, the gasket separation for the
connect point is set to one-half the Active Gasket Separation. However, some
flanged connections (lug, ring type joint, or wafer) have integral gaskets and do not
have a gasket separation. In this situation, the gasket separation at each connect
point is set to zero.
If the end preparation for the connect point is not flanged, the gasket separation for
the connect point will be set to zero.
The first table (BLT_Term_Rat_TS) contains the flange data required for modeling
activities (such as flange outside diameter and flange thickness).
The second table (STUD_Rat_TS) contains flange data required for reporting or
analysis activities (such as bolt diameter, number of bolt holes, and nut extension).
272
________________ Pipe, Tubing, and Hose
Commodity Data
7. Graphic
All tubing (such as fiberglass and copper) is specified in terms of piping outside
diameter rather than nominal piping diameter. All commodity item data in the
Alphanumeric Commodity Library exists in terms of nominal piping diameter.
Mechanical joint and cast iron pipe can have various fixed lengths. Polypropylene-
lined tube is purchased with flanged ends in various fixed lengths.
Piping wall thickness is defined it terms of NPD units rather than model units.
A piping converter component (which converts nominal piping diameter from one
system of units to another system of units) must be defined in the PJS database for each
specific pair of nominal piping diameters. You cannot specify a convertor component
for a range of nominal piping diameters.
273
________________
Reference Data Manager Reference Guide April 2002
274
________________ Graphic Commodity Library Manager
Commodity Data
7. Graphic
This command enables you to create a new graphic commodity library or create and modify
data (Eden modules) in an existing library. Refer to Graphic Commodity Library, page 254,
for more information on this library.
You can compile Eden source code, review and delete object code files, and insert, extract,
and delete Eden source files from the library.
Select the Graphic Commodity Library Manager command from the Reference Data
Manager form.
Options
Create Library Used to create a new Graphic Commodity Library.
Create/Interactive 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 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 Used to select an Eden module from the library, edit the file, and put the
recompiled file back into the library.
275
________________
Reference Data Manager Reference Guide April 2002
Extract 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.
276
________________ Create Library
Commodity Data
7. Graphic
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.
Select Accept to create the specified library files. If you specify an existing library file, the
system displays an error indicating the library already exists.
7.4.2 Compress
This option is used to compress the Graphic Commodity library. Any tables which have been
deleted from the library will be removed.
Select Accept to copy the unapproved library file to the approved library.
277
________________
Reference Data Manager Reference Guide April 2002
To add more than one Eden file to the library, create a list file which identifies the
names of the Eden source files to be added. The list file should contain one entry
(source file name) per line. The list file and all of the source files should reside in the
source file directory.
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.
Key in the name of the Eden file or list file to be compiled and added to the active
library.
4. 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.
278
________________ Create/Batch Graphic Commodity Data
Commodity Data
7. Graphic
This option enables you to compile Eden source code and insert the specified files into the
graphic commodity library via batch processing. You can process a single file or specify a list
of files to be created. Refer to the description of the Graphic Commodity Library, page 254,
for information on naming conventions for Eden modules.
To add more than one Eden file to the library, create a list file which identifies the
names of the Eden source files to be added. The list file should contain one entry
(source file name) per line. The list file and all of the source files should reside in the
source file directory.
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.
Key in the name of the Eden file or list file to be compiled and added to the active
library.
4. 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.
279
________________
Reference Data Manager Reference Guide April 2002
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set
the time to process the source files.
280
________________ Revise Graphic Commodity Data
Commodity Data
7. Graphic
This option enables you to select Eden modules 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 Eden modules in the Graphic Commodity Library.
281
________________
Reference Data Manager Reference Guide April 2002
3. 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.
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 will not be recompiled.)
If the file compiles successfully, the system returns to Step 2. You can select another
Eden module to be revised or select Exit.
If an error occurs in revising a Piping Eden module or table, the system invokes the
editor automatically to give you an opportunity to correct the problem.
282
________________ Delete Graphic Commodity Data
Commodity Data
7. Graphic
This option enables you to delete Eden modules from the graphic commodity library.
Operating Sequence
1. Select the Delete option.
The system displays the Eden modules in the Graphic Commodity Library.
Select the Eden modules to be deleted from the list of modules. You can use the scroll
bar to scroll through the available files.
The system deletes the modules from the Graphic Commodity Library.
283
________________
Reference Data Manager Reference Guide April 2002
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.
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.
284
________________ List Graphic Commodity Data
Commodity Data
7. Graphic
This option displays a list of Eden modules in the Graphic Commodity Library. The display
includes
a description of the type of Piping Eden module, such as Physical Data Definition or
Model Parametric Shape, at the end of each line.
The module names are sorted alphanumerically within the list for each type of Piping Eden
module.
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.
285
________________
Reference Data Manager Reference Guide April 2002
Set the toggle to Full List or Sub-string to determine the Eden modules to be listed.
Operating Sequence
1. Select Extract from the Data Management form.
Select the modules from the list of files and select Accept. You can use the scroll bar to
scroll through the available files. You can extract multiple files at one time.
OR
Select Extract ALL to bulk extract all the Piping Eden modules in one operation.
The system pulls the files out of the library and places them in the default eden
directory. The system also writes the names of the extracted files to a file named
PD_gc_list.
If the list file is less than 24 hours old, the system appends the entries to the file,
otherwise it overwrites the file.
286
________________ Physical Data Library Manager
Commodity Data
7. Graphic
This command enables you to access the library management options for the Physical Data
Library. You can create a new library file or create, modify, and delete data in an existing
library. You can also create reports of the data in the library and post the contents of the
unappoved library to the approved library. Refer to Physical Data Tables, page 266, for more
information on this library.
The system tracks revision dates for table entries when a table is being revised. This revision
management data recorded in a Table Revision Management Library, named
<table_library>.l.r. If the library has been removed or deleted, the software will regenerate
the library file.
This feature can be used to create revision management reports of components that require
reconstructing as a result of changes to any dimension tables since a specified date.
With the 4.2 release, the limitation on the size of tables in the Physical Data Library was
increased from approximately 16,000 bytes per table to 20,000 bytes per table.
With the 7.1 release, the limitation on the size of tables in the Physical Data Library was
increased from approximately 20,000 bytes to 60,000 bytes or 750 lines.
You must have write access to the specified file and directory path.
Operating Sequence
1. Select Physical Data Library Manager command from the Reference Data Manager
form.
287
________________
Reference Data Manager Reference Guide April 2002
Select the active practice (such as U.S. Practice or European - Din) from the display
list and select Accept.
The system loads the table list for the selected practice into memory.
3. You can set the toggle at the bottom of the form to determine the physical data tables to
be listed.
Full List lists all the tables in the Physical Data Library.
Sub-string limits the list to those tables which contain a specified substring.
Options
Create Library Used to create a new Physical Dimension Library.
Create/Interactive 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.
288
________________ Physical Data Library Manager
Create/Batch Used to compile and add table files to the active library via batch
processing.
Revise Used to select a table file from the library for editing and put the revised file
Commodity Data
7. Graphic
back into the library.
Extract Used to extract a table file from the library for editing or printing.
289
________________
Reference Data Manager Reference Guide April 2002
The system displays the approved and unapproved Physical Dimension Library names as
defined in the RDB Management Data.
Select Accept to create the specified library files. If you specify an existing library file, the
system displays an error indicating the library already exists.
7.5.2 Compress
This option is used to compress the Physical Dimension library. Any tables which have been
deleted from the library will be removed.
Select Accept to copy the unapproved library file to the approved library.
290
________________ Create/Interactive Physical Commodity Data
Commodity Data
7. Graphic
This option enables you to process physical dimension table source files and insert the
specified files into the active library. You can process a single table file or specify a list of
files to be created. Refer to the description of the applicable table file for information on
naming conventions and file formats.
To add more than one table file to the library, create a list file which identifies the
names of the table source files to be added. The list file should contain one entry
(source file name) per line. The list file and all the source files should reside in the
defined default table directory.
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.
Key in the name of the table file or list file to be processed and added to the active
library.
4. 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.
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.
291
________________
Reference Data Manager Reference Guide April 2002
To add more than one table file to the library, create a list file which identifies the
names of the table source files to be added. The list file should contain one entry
(source file name) per line. The list file and all the source files should reside in the
define default table directory.
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.
Key in the name of the table file or list file to be processed and added to the active
library.
4. 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.
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set
the time to process the source files.
292
________________ Create/Batch Physical Commodity Data
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.
Commodity Data
7. Graphic
293
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Revise option.
294
________________ Revise Physical Commodity Data
3. 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.
Commodity Data
7. Graphic
Make any changes to the displayed file.
When you exit the text editor, the system compiles the revised file and inserts it back
into the library. (If you quit the editor, the table is not recompiled.)
The system returns to Step 2. You can select another table to be revised or select Exit.
295
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Delete option.
Select the tables to be deleted from the list of tables. You can use the scroll bar to scroll
through the available files.
The system deletes the table files from the active library.
296
________________ Report Physical Commodity Data
Commodity Data
7. Graphic
This option enables you to create a report file of all the table files in the active library or those
defined by the substring search criteria.
Operating Sequence
1. Select the Report option from the Data Management form.
Set the toggle to Default Report to create a report that list the tables in the physical
data library.
OR
Set the toggle to Revision Dates Report and key in a date in the Revision Date field 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. Key in the file information for the location of the report file to be created.
297
________________
Reference Data Manager Reference Guide April 2002
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 Save or Print/Save option, the system will create a file named
<standard>_tables in the default source file location (where <standard> is a prefix
depending on the active practice).
6. Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set
the time to process the request.
298
________________ List Physical Commodity Data
Commodity Data
7. Graphic
This option displays all the table files for the active library with the revision date of each
table.
Operating Sequence
1. Select the List option.
2. You can use the scroll bar to scroll through the available files.
299
________________
Reference Data Manager Reference Guide April 2002
Set the toggle to Full List or Sub-string to determine the tables to be listed.
Operating Sequence
1. Select Extract from the Data Management form.
Select the tables from the list of files and select Accept. You can use the scroll bar to
scroll through the available files.
The system pulls the files out of the library and places them in the default table
directory. The system also writes the names of the extracted files to a file named
PD_tbl_list. For example,
The current date and time is: Wed Apr 29 15:59:41 1992
300
________________ Extract Physical Commodity Data
If the list file is less than 24 hours old, the system appends the entries to the file,
otherwise it overwrites the file.
Commodity Data
7. Graphic
301
________________
Reference Data Manager Reference Guide April 2002
302
________________ Table Formats and Naming Conventions
8. Table Formats
303
________________
Reference Data Manager Reference Guide April 2002
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.
8.1.2 Comments
You can include any number of comments in a table, using the conventions described below:
! XXXXXXXXXXXXXXXXXXXXXXXXXX , or
< XXXXXXXXXXXXXXXXXXXXXXXXXX >
< XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >
304
________________ Table Conventions
8. Table Formats
8.1.4 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
305
________________
Reference Data Manager Reference Guide April 2002
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
8.1.5 Units
Units are defined for each column of a table as follows:
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
306
________________ Table Conventions
Rating RAT
CLxxx and xxx# are expressed as xxx
8. Table Formats
Schedule/thickness, millimeters SC_TH_MM
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
307
________________
Reference Data Manager Reference Guide April 2002
Field locations and field lengths defined with XXXXs, WWWWs and ZZZZZs in this
document are observed.
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.
308
________________ Table Conventions
8. Table Formats
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
8.1.8 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:
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.
309
________________
Reference Data Manager Reference Guide April 2002
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.
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.
8.1.9 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.
NREQD: This value is used in cases where all of the following conditions apply:
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.
*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.
310
________________ Table Conventions
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
8. Table Formats
and in the data tables.
311
NomD S-5S S-10S S-10 S-20 S-30 S-STD S-40 S-40S S-60 S-XS S-80 S-80S S-100 S-120 S-140 S-160 S-XXS
0.125 S-10S S-STD S-STD S-40S S-XS S-XS S-80S
0.250 S-10S S-STD S-STD S-40S S-XS S-XS S-80S
0.375 S-10S S-STD S-STD S-40S S-XS S-XS S-80S
312
0.500 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
0.750 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
1.000 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
1.250 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
1.500 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
2.000 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
2.500 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
3.000 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-160 S-XXS
3.500 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S
4.000 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-120 S-160 S-XXS
5.000 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-120 S-160 S-XXS
6.000 S-5S S-10S S-STD S-STD S-40S S-XS S-XS S-80S S-120 S-160 S-XXS
8.000 S-5S S-10S S-20 S-30 S-STD S-STD S-40S S-60 S-XS S-XS S-80S S-100 S-120 S-140 S-160 S-XXS
10.00 S-5S S-10S S-20 S-30 S-STD S-STD S-40S S-XS S-XS S-80 S-80S S-100 S-120 S-XXS S-160 S-XXS
12.00 S-5S S-10S S-20 S-30 S-STD S-40 S-40S S-60 S-XS S-80 S-80S S-100 S-XXS S-140 S-160 S-XXS
14.00 S-5S S-10S S-10 S-20 S-STD S-STD S-40 S-60 S-XS S-80 S-100 S-120 S-140 S-160
16.00 S-5S S-10S S-10 S-20 S-STD S-STD S-XS S-60 S-XS S-80 S-100 S-120 S-140 S-160
18.00 S-5S S-10S S-10 S-20 S-30 S-STD S-40 S-60 S-XS S-80 S-100 S-120 S-140 S-160
20.00 S-5S S-10S S-10 S-STD S-XS S-STD S-40 S-60 S-XS S-80 S-100 S-120 S-140 S-160
22.00 S-5S S-10S S-10 S-STD S-XS S-STD S-60 S-XS S-80 S-100 S-120 S-140 S-160
24.00 S-5S S-10S S-10 S-STD S-30 S-STD S-40 S-60 S-XS S-80 S-100 S-120 S-140 S-160
26.00 S-10 S-XS S-STD S-XS
28.00 S-10 S-XS S-30 S-STD S-XS
30.00 S-5S S-10S S-10 S-XS S-30 S-STD S-XS
32.00 S-10 S-XS S-30 S-STD S-40 S-XS
Reference Data Manager Reference Guide April 2002
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.
8. Table Formats
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.
313
________________
Reference Data Manager Reference Guide April 2002
8.1.11 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 and Variables for Specific Tables 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.
314
________________ Table Requirements
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.
8. Table Formats
Typically, the tables in the table combinations are used to store:
The empty weight of the component and/or data about valve operators.
Valves (6Q1C)
315
________________
Reference Data Manager Reference Guide April 2002
316
________________ Specialty Piping Components (6P6C and 6Q6C)
8. Table Formats
317
________________
Reference Data Manager Reference Guide April 2002
I80 Inbody_Specific_AABBCC_MC_n
Inbody_Typical_AABBCC_MC_n
I81 Inoper_Specific_AABBCC_MC_n
Inoper_Typical_AABBCC_MC_n
318
________________ Generic Tables
G10 BLT_Term_Rat_TS
G12 STUD_Rat_TS
8. Table Formats
G12T
STUD_Term_Rat_TS
G20 MAL_Term_TS
G30 FEM_Term_Rat/Sc/Th_TS
G50 MALWT_Term_Rat/Sc/Th_TS_WC
319
________________
Reference Data Manager Reference Guide April 2002
For PVC and CPVC female ends, use the same as the value
of P for the corresponding male termination type.
For all other female ends, use 30% of the fitting OD at the
female end plus 70% of the matching pipe OD.
Male The value of this variable is "0" for all male ends.
320
________________ Variables for Generic Tables
8. Table Formats
This parameter is primarily used to calculate stud length.
When dealing with specialty components (such as relief
valves), you might have to develop many generic tables for
precise values. A practical alternative would be to create a
table in which values for this parameter are large enough to
insure that short studs do not result.
T Bolted This is half of the gasket gap thickness, as defined in the PJS
for the applicable piping materials class.
321
________________
Reference Data Manager Reference Guide April 2002
322
________________ Variables for Generic Tables
8. Table Formats
Thread Engagement, inches, as Reported By
NPD in NAVCO ANSI-B1.20.1 Stockham Crane Average PDS
0.125 0.3125 0.2726 0.25 0.25 0.2713 0.25
0.25 0.4375 0.3945 0.375 0.375 0.3955 0.375
0.375 0.4375 0.4067 0.375 0.375 0.3986 0.375
0.5 0.5625 0.5343 0.5 0.5 0.5242 0.5
0.75 0.5625 0.5533 0.5625 0.5625 0.5602 0.5625
1 0.6875 0.6609 0.6875 0.6875 0.6809 0.6875
1.25 0.6875 0.6809 0.6875 0.6875 0.6859 0.6875
1.5 0.6875 0.6809 0.6875 0.6875 0.6859 0.6875
2 0.75 0.6969 0.75 0.75 0.7367 0.75
2.5 1.0625 0.932 0.9375 0.9375 0.9674 0.9375
3 1.125 1.016 1 1 1.0353 1
3.5 1.1875 1.071 1.0625 1.107 1.0625
4 1.1875 1.094 1.125 1.1355 1.125
5 1.3125 1.187 1.25 1.2483 1.25
6 1.375 1.208 1.3125 1.2985 1.3125
8 1.4375 1.313 1.4375 1.396 1.4375
10 1.625 1.46 1.625 1.57 1.5625
12 1.75 1.61 1.75 1.7033 1.75
323
________________
Reference Data Manager Reference Guide April 2002
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
324
________________ Generic Table for Bolted Ends (G10)
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
8. Table Formats
58 65.9375 2.9375 0 63.4375
60 67.9375 3 0 65.4375
END
325
________________
Reference Data Manager Reference Guide April 2002
The W_n columns are used to classify the bolt extension. The n applies to the value defined
in the Piping Commodity Data for the bolt diameter being considered. For example, if the
modifier value for the PCD is 0, the value in the W_0 column is used for nut allowance. This
capability enables the system to handle special nut allowances, such as when stud tensioning
devices are utilized.
This table is accessed using values for rating and table suffix derived from the applicable
flanged end.
Example
Table_Data_Definition STUD_150_5
! Description= CL150 bolting
! Source= PIPING RDB DATA MANUAL
! TNF=G12 By=GJH Ckd By=RJW Rev=1 Date=03-Nov-1987
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.25 4 0.375 0.5938 - - - - -
0.375 4 0.375 0.5938 - - - - -
0.5 4 0.5 0.6563 1 - - - -
0.75 4 0.5 0.6563 0.875 - - - -
1 4 0.5 0.6563 1 - - - -
326
________________
Generic Table for Studs used in Bolted Connections (G12)
8. Table Formats
26 36 0.75 0.9688 1.375 - - - -
28 40 0.75 0.9688 1.375 - - - -
30 44 0.75 0.9688 1.375 - - - -
32 48 0.75 0.9688 1.5 - - - -
34 40 0.875 1.0938 1.75 - - - -
36 44 0.875 1.0938 1.75 - - - -
38 40 1 1.2188 1.75 - - - -
40 44 1 1.2188 2 - - - -
42 48 1 1.2188 1.75 - - - -
44 52 1 1.2188 1.875 - - - -
46 40 1.125 1.3751 2 - - - -
48 44 1.125 1.3438 2 - - - -
50 48 1.125 1.3438 2 - - - -
52 52 1.125 1.3438 2.125 - - - -
54 56 1.125 1.3438 2 - - - -
56 60 1.125 1.3438 2.125 - - - -
58 48 1.25 1.4688 2.25 - - - -
60 52 1.25 1.4688 2.125 - - - -
END
327
________________
Reference Data Manager Reference Guide April 2002
The W_n columns are used to classify the bolt extension. The n applies to the value defined
in the Piping Materials Class for the bolt diameter being considered. For example, if the
modifier value for the PMC is 0, the value in the W_0 column is used for nut allowance. This
capability enables the system to handle special nut allowances, such as when stud tensioning
devices are utilized.
STUD_Term_Rat_TS
This table is accessed using values for termination type, rating and table suffix derived from
the applicable flanged 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 - - - -
328
________________
Generic Table for Studs in Bolted Connections w/ Term Type (G12T)
8. Table Formats
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
329
________________
Reference Data Manager Reference Guide April 2002
! 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
3 0.916 3.5 1.75
3.5 1.047 4 2
4 1.178 4.5 2.25
5 1.456 5.5625 2.7813
6 1.73 6.625 3.3125
8 2.26 8.625 4.3125
10 2.81 10.75 5.375
12 3.34 12.75 6.375
14 3.67 14 7
16 4.19 16 8
330
________________
Generic Table for Male Ends (G20)
18 4.71 18 9
20 5.24 20 10
22 5.76 22 11
24 6.28 24 12
26 6.81 26 13
28 7.33 28 14
30 7.85 30 15
32 8.38 32 16
34 8.9 34 17
36 9.42 36 18
38 9.95 38 19
40 10.47 40 20
42 10.99 42 21
44 11.52 44 22
46 12.04 46 23
48 12.57 48 24
52 13.61 52 26
8. Table Formats
56 14.66 56 28
60 15.71 60 30
64 16.76 64 32
68 17.80 68 34
72 18.85 72 36
76 19.90 76 38
80 20.94 80 40
END
331
________________
Reference Data Manager Reference Guide April 2002
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 dias, 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
332
________________
Generic Table for Weight and Thickness Data, Male Ends (G50)
8. Table Formats
Table_Data_Definition MALWT_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G50 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 1 No_Outputs 3
Units= NPD_IN, LBF, LBF, IN
! GCP Unit Wt Unit Wt
! Diam Empty Water X
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 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
333
________________
Reference Data Manager Reference Guide April 2002
Use tables P11*-P20* for piping component data based only on green connect point data.
Use tables P21*-P30* for piping component data based on green and red connect point data.
For more information, refer to Piping Component Table Green and Red CP Data
(P21A,P25A,P26A,P27A,P28A,P29A), page 342 and Piping Component Table Green and
Red CP Overflow Data (P21B,P25B,P26B,P27B,P28B), page 344 .
Use tables P31*-P40* for dimensional data based on green connect point data of piping valve
operators whose operator code list values (as defined in CL550 - Operator/Actuator Type) are
equal to or less than 24.
Use tables P51-P58 for non-valve piping component empty weights based on green connect
point data.
334
________________ Piping Component Tables
Use table P59 for empty weights of piping valves, including weight of operators, whose
operator code list values (as defined in CL550 - Operator/Actuator Type) are less than or
equal to 24, regardless of whether only green connect point or both green and red connect
point data applies to the valve.
Use tables P60* for empty weights of piping valves, weights and centers of gravity of valve
operators, model codes of valve operators and for dimensional data of piping valve operators
whose operator code list values (as defined in CL550 - Operator/Actuator Type) exceed 24
and are less than or equal to 40, regardless of whether only green connect point or both green
and red connect point data applies to the valve.
8. Table Formats
P60A Cmdty Code_WOPD_A
P60B Cmdty Code_WOPD_B
Use tables P61-P70 for non-valve piping component empty weights based on green and red
connect point data. Refer to Piping Component Table for Empty Weight based on GCP and
RCP Data (P61,P62,P63,P64,P65), page 352
for more information.
Use tables P80 and P81 for data about piping specialty components defined in the Material
Reference Database.
Piping Component Tables for Specialty Components, page 354 for more information.
335
________________
Reference Data Manager Reference Guide April 2002
336
________________ Variables for Specific Tables
8. Table Formats
Bolted This value is included in the appropriate dimension table.
337
________________
Reference Data Manager Reference Guide April 2002
I,J,K,L,M,N Any These values are used in dimension tables for specific
components as required by the component being defined.
338
________________ Piping Component Table for GCP Data (P11A, P15A)
8. Table Formats
Neutral File Format
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
339
________________
Reference Data Manager Reference Guide April 2002
16 - - 8
18 - - 8.5
20 - - 9
24 - - 10
26 - - 11
28 - - 12
30 - - 12
36 - - 14
END
340
________________
Piping Component Table GCP Overflow Data (P11B, P15B)
8. Table Formats
Neutral File Format
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
341
________________
Reference Data Manager Reference Guide April 2002
TNF=P21A MC_GS_Term(G)_Term(R)_A
TNF=P25A MC_GS_Term(G)_Rat(G)_Term(R)_A
TNF=P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
TNF=P27A MC_GS_Term(G)_Term(R)_Rat(R)_A
TNF=P28A MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_A
TNF=P29A MC_GS_BrchTbl_Angle_A
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
342
________________
Piping Component Table Green and Red CP Data (P21A,P25A,P26A,P27A,P28A,P29A)
8. Table Formats
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
343
________________
Reference Data Manager Reference Guide April 2002
344
________________
Piping Component Table for Operators and Actuators (P31A)
8. Table Formats
where Type can have the following possible values:
Preparation Type
2-199 BLT
300-399 MAL
400-599 FEM
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
345
________________
Reference Data Manager Reference Guide April 2002
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
346
________________
Piping Component Table for Operators and Actuators, Overflow Data (P31B)
8. Table Formats
Preparation Type
2-199 BLT
300-399 MAL
400-599 FEM
347
________________
Reference Data Manager Reference Guide April 2002
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.
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
348
________________
Piping Component Table for Empty Weight based on GCP Data (P51,P52,P59)
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
8. Table Formats
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
349
________________
Reference Data Manager Reference Guide April 2002
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
350
________________
Piping Component Table For Empty Weight of Valves, Overflow Data (P60B)
8. Table Formats
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
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 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
351
________________
Reference Data Manager Reference Guide April 2002
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 -
352
________________
Piping Component Table for Empty Weight based on GCP and RCP Data (P61,P62,P63,P64,P65)
24 20 397
24 18 397
END
8. Table Formats
353
________________
Reference Data Manager Reference Guide April 2002
The tables used to to define the physical data for piping specialty components have the same
format as those used to define instrument components. The table names are of the format:
Refer to Instrument Component Tables, page 355 for more information on these tables.
354
________________ Instrument Component Tables
Input to these tables is defined in the physical_data_id attribute of the Instrument Component
Specification Data (Table 204 attribute 17). The entries in the tables must agree with the
entries in the Instrument Component Specification Data of the Material Reference Database.
8. Table Formats
Each table is limited to approximately 60,000 bytes or 750 lines.
When the tables are created in the Physical Data Library, you should define the values for the
physical units for length, surface area, and weight to match the seed data defined for the
project.
The default prefix for these table names is Inbody. You can specify a user-defined prefix up
to 6 characters for the table names. If you use a user-defined prefix, you must revise the
appropriate Piping Eden modules for the instruments.
The prefix is followed by either Specific or Typical, the instrument pds_sort_code, the model
code, and a letter indicating the table (A-C).
355
________________
Reference Data Manager Reference Guide April 2002
Inbody_Specific_PSC_MC_A
The first four output fields are the surface area, the dry weight, the water weight, and the
number of connect points for the instrument.
The remaining output fields are the dimensional parameters P2 through P6, as prescribed in
the PDS Piping Component Data Reference Guide.
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.
356
________________ Instrument Component Tables
Inbody_Specific_PSC_MC_C
8. Table Formats
The output fields are the dimensional parameters P16 through P24, as prescribed in the PDS
Piping Component Data Reference Guide.
357
________________
Reference Data Manager Reference Guide April 2002
The default prefix for these table names is Inoper. You can specify a user-defined prefix, up
to 6 characters, for the table names. If you specify a user-defined prefix, you must revise the
appropriate Piping Eden modules for these instrument operators.
The prefix is followed by either Specific or Typical, the instrument pds_sort_code, the model
code, and a letter indicating the table (A - C).
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.
358
________________ Instrument Operator (I81 and P81)
Inoper_Specific_PSC_MC_B
8. Table Formats
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.
359
________________
Reference Data Manager Reference Guide April 2002
360
________________ Material Description Data
Stress analysis.
Material Tables in the Material Reference Database - These database tables (211 and
212) contain commodity definitions which enable you to further classify the commodity
Description Data
9. Material
items defined in the Piping Job Specification. This database information tends to be
customer-specific.
Short Material Description Library - This library contains the short bill-of-material
(BOM) descriptions for all piping commodity items and the BOM description addenda
for taps.
Long Material Description Library - This library contains the long bill-of-material
descriptions for all piping commodity items. The long BOM description is only used
for requisitions.
The material description data in these files is used for reporting and material control and is not
required for the interactive placement of symbols in the model. This data is only accessed
during a batch (non-interactive) process.
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).
361
________________
Reference Data Manager Reference Guide April 2002
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:
362
________________ Material Description Data
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)
Description Data
9. Material
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 Appendix E of 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.
363
________________
Reference Data Manager Reference Guide April 2002
where
A E if English.
BBB the nominal diameter value of the tap such as $50, $75, or 001. The use of
leading and trailing zeroes is specific to this table naming convention. ($
represents a decimal point.)
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
364
________________ Material Description Data
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.
Description Data
9. Material
365
________________
Reference Data Manager Reference Guide April 2002
The Size-Dependent Data table contains the data for a specific commodity item that is
dependent on the commodity code, nominal piping diameter, and schedule/thickness. It
is used for miscellaneous batch reporting, such as construction cost reports and
requisition orders, and interfaces to material control, stress analysis, and isometric
drawing extraction.
The Implied Material Data table contains the implied material data for a specific
commodity item that is dependent on both the Piping Commodity Library code and
nominal piping diameter range. This data is used strictly for generating implied
material for MTO reporting and material control. It is not used for welds, bolts, nuts, or
gaskets, but is reserved for other types of implied material, such as caps or stubs, for a
specific commodity item. It is also used for reporting the implied components of a
commodity item (such as cap screws).
Refer to Material Reference Database Structure, page 56, for information on the structure of
these database tables. Also refer to the description of the Piping Job Specification Manager,
page 145, for information on loading material data into these database tables via neutral files.
366
________________ Short Material Description Library
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 in the following files:
The Short Material Description Library is created from two neutral files. (These can be
Description Data
9. Material
created with a text editor such as EMACS or vi.)
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 customers
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.
367
________________
Reference Data Manager Reference Guide April 2002
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.
Data Retrieval
The system uses the commodity code to retrieve the short material descriptions from the
Material Description Library.
368
________________ Short Material Description Library
Description Data
9. Material
FAAABAOABB Flange, CL150, RFFE/BE, ASTM-A350-LF2, ANSI-B16.5, WN, S-160 bore
FAAABAOFFH Flange, CL150, RFFE/BE, ASTM-A182-F5, ANSI-B16.5, WN, S-160 bore
FAAABAWAAA Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWABB Flange, CL150, RFFE/BE, ASTM-A350-LF2, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWFFH Flange, CL150, RFFE/BE, ASTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWFFL Flange, CL150, RFFE/BE, ASTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWGFD Flange, CL150, RFFE/BE, ASME-SA182-F11, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWIIA Flange, CL150, RFFE/BE, ASTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWIIF Flange, CL150, RFFE/BE, ASTM-A182-F316, ANSI-B16.5, WN, [409]|bore to match|
FAAABAWNPF Flange, CL150, RFFE/BE, ASTM-B166-600, ANSI-B16.5, WN, [409]|bore to match|
FAAABBDAAA Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-XXS bore
FAAADAOAAA Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, 125 Ra finish, S-160 bore
FAAADAOFFC Flange, CL150, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-160 bore
FAAADAWAAA Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|
FAAADAWFFC Flange, CL150, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|
FAAADBDFFC Flange, CL150, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-XXS bore
FAABBADIIA Flange, CL300, RFFE/BE, ASTM-A182-F304, ANSI-B16.5, WN, S-80S bore
FAABBADIIB Flange, CL300, RFFE/BE, ASTM-A182-F304L, ANSI-B16.5, WN, S-80S bore
FAABBADIIF Flange, CL300, RFFE/BE, ASTM-A182-F316, ANSI-B16.5, WN, S-80S bore
FAABBAOAAA Flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-160 bore
FAABBAOABB Flange, CL300, RFFE/BE, ASTM-A350-LF2, ANSI-B16.5, WN, S-160 bore
FAABBAOFFC Flange, CL300, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, S-160 bore
FAABBAOFFH Flange, CL300, RFFE/BE, ASTM-A182-F5, ANSI-B16.5, WN, S-160 bore
FAABBAWAAA Flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWABB Flange, CL300, RFFE/BE, ASTM-A350-LF2, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWFFC Flange, CL300, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWFFH Flange, CL300, RFFE/BE, ASTM-A182-F5, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWFFL Flange, CL300, RFFE/BE, ASTM-A182-F9, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWIIA Flange, CL300, RFFE/BE, ASTM-A182-F304, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWIIB Flange, CL300, RFFE/BE, ASTM-A182-F304L, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWIIF Flange, CL300, RFFE/BE, ASTM-A182-F316, ANSI-B16.5, WN, [409]|bore to match|
FAABBAWNPF Flange, CL300, RFFE/BE, ASTM-B166-600, ANSI-B16.5, WN, [409]|bore to match|
FAABBBDAAA Flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-XXS bore
FAABDADIIJ Flange, CL300, RFFE/BE, ASTM-A182-F321, ANSI-B16.5, WN, 125 Ra finish, S-80S bore
FAABDAOAAA Flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, 125 Ra finish, S-160 bore
FAABDAOFFC Flange, CL300, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, S-160 bore
FAABDAWAAA Flange, CL300, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|
FAABDAWFFC Flange, CL300, RFFE/BE, ASTM-A182-F11, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|
FAABDAWFFH Flange, CL300, RFFE/BE, ASTM-A182-F5, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|
FAABDAWIIJ Flange, CL300, RFFE/BE, ASTM-A182-F321, ANSI-B16.5, WN, 125 Ra finish, [409]|bore to match|
FAADBADIIA Flange, CL600, RFFE/BE, ASTM-A182-F304, ANSI-B16.5, WN, S-80S bore
FAADBADIIF Flange, CL600, RFFE/BE, ASTM-A182-F316, ANSI-B16.5, WN, S-80S bore
FAADBAOAAA Flange, CL600, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-160 bore
369
________________
Reference Data Manager Reference Guide April 2002
370
________________
Short Material Description Library
Description Data
9. Material
371
________________
Reference Data Manager Reference Guide April 2002
This data is used strictly for MTO reporting and material control.
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 customers 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.
372
________________ Long Material Description Library
Description Data
9. Material
FAAABAOAAA Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A105, Sch 160 bore
FAAABAOABB Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A350 Gr.LF2, Sch 160 bore
FAAABAOFFH Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A182 Gr.F5, Sch 160 bore
FAAABAWAAA Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A105, [409]
FAAABAWABB Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A350 Gr.LF2, [409]
FAAABAWFFH Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A182 Gr.F5, [409]
FAAABAWFFL Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A182 Gr.F9, [409]
FAAABAWGFD Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASME-SA182 Gr.F11, [409]
FAAABAWIIA Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A182 Gr.F304, [409]
FAAABAWIIF Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A182 Gr.F316, [409]
FAAABAWNPF Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-B166 Gr.600 UNS N06600, hot finish, [409]
FAAABBDAAA Flange, weld neck, raised face flanged end, ANSI-B16.5 CL150, ASTM-A105, XX-strong bore
FAAADAOAAA Flange, weld neck, raised face flanged end, 125 Ra finish, ANSI-B16.5 CL150, ASTM-A105, Sch 160 bore
FAAADAOFFC Flange, weld neck, raised face flanged end, 125 Ra finish, ANSI-B16.5 CL150, ASTM-A182 Gr.F11, Sch 160 bore
FAAADAWAAA Flange, weld neck, raised face flanged end, 125 Ra finish, ANSI-B16.5 CL150, ASTM-A105, [409]
FAAADAWFFC Flange, weld neck, raised face flanged end, 125 Ra finish, ANSI-B16.5 CL150, ASTM-A182 Gr.F11, [409]
FAAADBDFFC Flange, weld neck, raised face flanged end, 125 Ra finish, ANSI-B16.5 CL150, ASTM-A182 Gr.F11, XX-strong bore
FAABBADIIA Flange, weld neck, raised face flanged end, ANSI-B16.5 CL300, ASTM-A182 Gr.F304, Sch 80S bore
FAABBADIIB Flange, weld neck, raised face flanged end, ANSI-B16.5 CL300, ASTM-A182 Gr.F304L, Sch 80S bore
373
________________
Reference Data Manager Reference Guide April 2002
This data is used strictly for MTO reporting and material control. The specialty material
descriptions can be up to 240 characters in length.
Neutral Files
Three neutral files are used to insert data into or replace data for the specialty material
descriptions.
These files contain the specialty tag number and the text for the material description. The
specialty tag number is appended by a specialty type which is used to distinguish between
engineered items, in-line instruments, and pipe supports.
374
________________ Specialty Material Description Library
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.
Description Data
9. Material
375
________________
Reference Data Manager Reference Guide April 2002
You can use the copy and paste commands to copy existing library data from another project
and make the necessary revisions using the Material Description Library Manager.
Operating Sequence
1. Select Material Description Library Manager from the Reference Data Manager
form.
376
________________ Material Description Library Manager
3. The data manipulation options for each of the libraries is similar. You can perform the
following activities for each of the libraries.
Create Library Creates a new (empty) Short Material Description Library, Long
Description Data
9. Material
Material Description Library, or Specialty Material Description Library.
Unapprove ==> Approve Copies data from the unapproved library to the
approved library.
Load/Revise Interactive 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 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 Batch Deletes all entries in the respective Material Description Library
file and then loads new entries from a neutral file.
Report Used to create a report file or a neutral file of the contents of the material
description library.
377
________________
Reference Data Manager Reference Guide April 2002
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
If the approved and unapproved library names are the same, the system displays an error
message.
378
________________ Load/Revise Interactive
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.
Select the type of material data to be loaded into the specified library from the display
Description Data
9. Material
list and select Accept.
Key in the file specification for the neutral file that contains the data to be processed.
379
________________
Reference Data Manager Reference Guide April 2002
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.
Select the type of material data to be loaded into the specified library from the display
list and select Accept.
Key in the file specification for the neutral file that contains the data to be processed
and select Accept.
Set the toggle to Submit Batch Immediately or Delayed Batch Submit Time.
For delayed submission, set the time to process the neutral file.
380
________________ Replace Interactive
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.
Select the type of material data to be loaded into the specified library from the display
Description Data
9. Material
list and select Accept.
Key in the file specification for the neutral file that contains the data to be processed.
381
________________
Reference Data Manager Reference Guide April 2002
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.
Select the type of material data to be loaded into the specified library from the display
list and select Accept.
Key in the file specification for the neutral file that contains the data to be processed
and select Accept.
Set the toggle to Submit Batch Immediately or Delayed Batch Submit Time.
For delayed submission, set the time to process the neutral file.
382
________________ Report Option
Operating Sequence
1. Select the Report option from one of the library forms.
Select the type of material data to be extracted from the specified library from the
display list and select Accept.
Description Data
9. Material
3. 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.
5. Set the toggle to Unapproved Library or Approved Library 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.
6. Set the toggle to Create Neutral File to create a neutral file which can be revised and
reloaded into the library.
OR
Set the toggle to Create Report to create a report file of the information in the library.
The report output is the same as the neutral file except that the system aligns subsequent
lines of the material description left-justified to the beginning of the material
description rather than the commodity code.
383
________________
Reference Data Manager Reference Guide April 2002
For the report selection, the system displays the following options.
Print / Delete submit the generated report output file to the specified print
queue and delete the output file.
Print / Save submit the generated report output file to the specified print
queue and save the output file.
For either of the Print options, the system displays a list of queues based on information
in the project Queue Description Library. Refer to the Project Administrator Reference
Guide, for more information on the Queue Description Library and setting up print
queues.
384
________________ Table Checker
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
Checker
10. Table
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.
385
________________
Reference Data Manager Reference Guide April 2002
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.
386
________________ Table Checker
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.
Checker
10. Table
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
387
________________
Reference Data Manager Reference Guide April 2002
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.
388
________________ Table Checker Form
Options
Checker
10. Table
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, page 392.
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, page 398.
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, page
406.
389
________________
Reference Data Manager Reference Guide April 2002
Using the Report Format option, you can create a numbered record for each format file so
that it can be accessed for report processing. The format record is a record in the Project
Control Database used to name and locate a specific format file. Unlike the format file, the
format record is created interactively. It is called a record to classify it as a block of data that
is used for report processing but is not an actual file.
The discrimination data record is a record in the Project Control Database used to name and
locate a specific discrimination data file. There is a uniquely-numbered record for each
discrimination data file so that it can be accessed for report processing. This is the same way
that the format record is used to access a format file.
The report record names or defines locations for all of the files that are necessary to generate a
report, including the report output. (It is called a record to classify it as a block of data that is
used for report processing but is not an actual file.)
390
________________ Using the Report Commands
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.
Checker
10. Table
391
________________
Reference Data Manager Reference Guide April 2002
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 files
location has been entered into the project control database.
Options
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, page 394.
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, page
394.
392
________________ Report Format Form
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, page 396.
Checker
10. Table
393
________________
Reference Data Manager Reference Guide April 2002
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.
Field Descriptions
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.
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.
394
________________ Format Creation/Revision Form
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.
From the displayed list, select the record to be copied or revised. Then click Accept.
Key-in fields are displayed for you to specify the required database information.
Type information in each of the displayed fields, taking care to press return in each
field. Then click Accept.
Checker
10. Table
395
________________
Reference Data Manager Reference Guide April 2002
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.
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
396
________________ Format Deletion Form
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.
Checker
10. Table
397
________________
Reference Data Manager Reference Guide April 2002
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.
Options
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, page 400.
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, page 402.
398
________________ Discrimination Data Form
control database. For more information, see Discrimination Data Revision Form, page
402.
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, page 404.
Checker
10. Table
399
________________
Reference Data Manager Reference Guide April 2002
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.
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.
400
________________ Discrimination Data Creation Form
File Node The nodename of the system on which the discrimination data file is
located. This field retains the active settings.
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.
Operating Sequence
1. From the Report Discrimination Data form, select Create
In the fields provided, key in the number, description, and file specification, path, and
node.
3. Select additional options as needed to define the report discrimination data. Then select
Accept.
Checker
10. Table
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, however, the
discrimination data file is not actually created until you select Accept on the
Report Discrimination Data form.
401
________________
Reference Data Manager Reference Guide April 2002
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.
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.
402
________________ Discrimination Data Revision Form
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.
Operating Sequence
1. From the Report Discrimination Data form, select Copy or Revise.
In the fields provided, key in the number, description, and 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, however, the
discrimination data file is not actually updated until you select Accept on the
Checker
10. Table
Report Discrimination Data form.
403
________________
Reference Data Manager Reference Guide April 2002
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.
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
404
________________ Discrimination Data Deletion Form
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.
Checker
10. Table
405
________________
Reference Data Manager Reference Guide April 2002
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.
406
________________ Report Form
Options
Create Displays the Report Creation form, which creates a report record and
generates a report. For more information, see Report Creation Form, page 408.
Revise Displays the Revise Report form, which regenerates a report from an
existing or revised report record. For more information, see Revise Report Form, page
411.
Delete Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form, page 414.
Approve Displays the Report Approval form, which approves an existing report.
For more information, see Report Approval Form, page 416.
Multi-Create Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form, page
418.
Checker
10. Table
407
________________
Reference Data Manager Reference Guide April 2002
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.
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 Dataform. For more information, see Report Management
Defaults Form, page 420.
408
________________ Report Creation Form
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, page 420.
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
Checker
10. Table
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.
409
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. From the Report form, select Create.
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.
410
________________ Revise Report Form
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.
Checker
10. Table
Fields and Options
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.
411
________________
Reference Data Manager Reference Guide April 2002
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.
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.
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
412
________________ Revise Report Form
file and the report output file, make the necessary changes, set this toggle to Revise
Data Only, 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.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
Checker
10. Table
413
________________
Reference Data Manager Reference Guide April 2002
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.
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
414
________________ Report Deletion Form
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.
Checker
10. Table
415
________________
Reference Data Manager Reference Guide April 2002
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.
Options
Number The 24-character unique name (as called short name) of the report record.
Operating Sequence
1. From the Report form, select Approve.
416
________________ Report Approval Form
2. From the displayed list, select a report to approve. Then click Accept.
For more information, see the Approve Report section of the PD_Report Users
Guide.
Checker
10. Table
417
________________
Reference Data Manager Reference Guide April 2002
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.
418
________________ Report Multiple Submit Form
Operating Sequence
1. From the Report form, select Multi-Create.
From the displayed list, select the reports to submit. Highlighed 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.
Checker
10. Table
419
________________
Reference Data Manager Reference Guide April 2002
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.
Fields
Report Path Specifies the default path of the report output files.
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.
420
________________ Report Management Defaults Form
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.
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.
Checker
10. Table
421
________________
Reference Data Manager Reference Guide April 2002
21-Apr-92 Page: 1
SIZE-INDEPENDENT SPEC DATA
__________________________
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
422
________________ Sample Table Checker Output
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)
Checker
10. Table
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
423
________________
Reference Data Manager Reference Guide April 2002
21-Apr-92 Page: 3
SIZE-INDEPENDENT SPEC DATA
__________________________
Rating(s): CL150
Modifier: 3
Note 2: -
AABBCC: 6Q1C01
Commodity Code: VAABAHGGAA
Weight Code: 490 pcf (52)
EDEN Modules Tables
______
GAT BLT_20_150_5
V1_AMS GAT_40_20_150_A
VALVE_2_AMS VAABAHGGAA
V1 GAT_BLT_150_3_A
OP_3 STUD_20_150_5
OPERATOR_3
OP3
424
________________ Sample Table Checker Output
1IN 1IN
6.25Lb 1.4538In, 0.4375In Undefined, Undefined, 1.375In 13In, 5.5In
1-1/2IN 1-1/2IN
12Lb 2.0575In, 0.4375In Undefined, Undefined, 1.5625In 16.125In, 5.75In
1IN 1IN
9.75Lb 1.4538In, 0.4375In Undefined, Undefined, 1.375In 13In, 5.5In
1-1/2IN 1-1/2IN
21.75Lb 2.0575In, 0.4375In Undefined, Undefined, 1.5625In 16.125In, 5.75In
Checker
10. Table
425
________________
Reference Data Manager Reference Guide April 2002
426
________________ Sample Table Checker Output
Checker
10. Table
BLSPC_146_120_300_NREQD_52 Physical Data Library Thu Jan 3 09:28:59 1991
427
________________
Reference Data Manager Reference Guide April 2002
428
________________ Sample Table Checker Output
Checker
10. Table
429
________________
Reference Data Manager Reference Guide April 2002
430
________________ Sample Table Checker Output
Checker
10. Table
MALWT_300_S$XS_5_52 Physical Data Library Thu Jan 3 10:23:10 1991
431
________________
Reference Data Manager Reference Guide April 2002
432
________________ Sample Table Checker Output
Checker
10. Table
F17D
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
433
________________
Reference Data Manager Reference Guide April 2002
F6_AMS
F8
F8_AMS
434
________________ Sample Table Checker Output
Checker
10. Table
RPAD
RWELD
SOL
SWGC
SWGE
T
TRB
UN
V1
V11
V1_AMS
V26
V38
V6
VALVE_2_AMS
WOL
435
________________
Reference Data Manager Reference Guide April 2002
1 - ERROR - EDEN error (-3) for pmc 1C0031 item 6Q1C26 with 1st size 32IN and 2nd size 32IN
Error in module MGOP_32768
2 - ERROR - EDEN error (-3) for pmc 1C0031 item 6Q1C26 with 1st size 34IN and 2nd size 34IN
Error in module MGOP_32768
Error Codes
The following error codes are used in the reported error messages.
436
________________ Pipe Support Tutorial Definition Manager
For more information on TDFs, refer to the Pipe Supports Modeler Reference Guide.
437
________________
Reference Data Manager Reference Guide April 2002
You must have write access to the specified file and directory path.
Options
Create Library Used to create a new Tutorial Definition Library.
Create Data 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.
438
________________ Support Tutorial Definition Manager
Revise Data Used to select a tutorial definition file from the library for editing and
compile the revised tutorial definition file.
Delete Data Used to delete a specified tutorial definition file from the library.
Extract Data 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.
439
________________
Reference Data Manager Reference Guide April 2002
The system displays the approved and unapproved Tutorial Definition Library names as
defined in the RDB Management Data.
Select Accept to create the specified library files. If you specify an existing library file, the
system displays an error indicating the library already exists.
11.1.2 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.
Select Accept to copy the unapproved library file to the approved library.
440
________________ Create Data
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.
Key in the name of the source file or list file to be compiled and added to the active
library.
4. 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.
If a fatal error occurs while loading files, the Tutorial Definition File Library is left
unchanged.
441
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Revise option.
The system displays the tutorial definition files in the Tutorial Definition Library.
The system extracts the specified file from the library and activates the text editor to
enable you to modify the file.
442
________________ Revise Data
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.)
443
________________
Reference Data Manager Reference Guide April 2002
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.
For the Print/Delete or Print/Save options, select the print queue from the list of
displayed queues.
For the Save or Print/Save options, the system generates a report named ppsm_tdf in
the default directory based on the contents of the Pipe Support Tutorial Definition
Library.
444
________________ List Data
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.
445
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Delete option.
The system displays the tutorial definition files in the Tutorial Definition Library.
Select the tutorial definition file to be deleted from the list of files. You can use the
scroll bar to scroll through the available files.
The system deletes the tutorial definition file from the Tutorial Definition Library.
446
________________ Extract Data
Operating Sequence
1. Select Extract Data from the Library/Data Management form.
Select the tutorial definition file from the list of files and select Accept. You can use
the scroll bar to scroll through the available files.
OR
Select the Extract All button to extract all the available files.
The system pulls the file out of the library and places it in the default directory defined
in the Default Project Control Data. See Default Project Control Data, page 53. 11. TDF Library
447
________________
Reference Data Manager Reference Guide April 2002
448
________________ Standard Note Library
The standard code list text is delivered in the file \win32app\ingr\pdshell\lib\std_note.l. The
accompanying source listing for this file is contained in the file std_note.l.t. You can add,
delete, or revise code list sets in the library to reflect your own practices, terminology, and
language. Entries in these files are in the form Standard Note Type xxxx where xxxx is the
number of the code list set.
2 = Hydrogen Gas
Entries enclosed in single quotes can take up more than one line. When an entry continues
onto a new line, a blank character is automatically appended to the end of the previous line.
449
________________
Reference Data Manager Reference Guide April 2002
General Rules
EACH standard note type or code list type should be contained in a separate neutral file.
C100
; This is a comment line !!!!!!
; This file contains a code list for type 100.
1 = Inert Gas
2 = Natural Gas
5 = Oxygen Gas
6 = Standard note or code list descriptions can extend
beyond one line of text up to a maximum of 80 characters
12 = Purge Gas
14 = Waste Gas
The first entry in each neutral file should be the note/code TYPE (C100 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.
Additionally, 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 following numbering conventions are used for standard note type 499:
The first entry can contain additional characters following the TYPE, but they are all
ignored.
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.
450
________________ Standard Note Library
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 (i.e. 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.
451
________________
Reference Data Manager Reference Guide April 2002
452
________________ Standard Note Library Manager
You must have write access to the specified file and directory path.
Options
Create Library Used to create a new Standard Note Library.
Unapproved ==> Approved Used to copy the unapproved Standard Note Library
to the approved library.
Create 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.
Note Library
12. Standard
453
________________
Reference Data Manager Reference Guide April 2002
Revise Used to select a standard note set from the library for editing and compile
the revised standard note definition.
Delete Used to delete a specified standard note set from the library.
Extract Used to extract a standard note set from the library for editing or printing.
Load Database Used to load the contents of the Standard Note Library into the
applicable schemas of the projects relational database to support DBAccess reporting
of PDS data.
454
________________ Create Library
The system displays the approved and unapproved Standard Note Library names as defined in
the RDB Management Data.
Select Accept to create the specified library files. If you specify an existing library file, the
system displays an error indicating the library already exists.
12.1.2 Compress
This option is used to compress the Standard Note Library. Any tables which have been
deleted from the library will be removed.
Select Accept to copy the unapproved library file to the approved library.
Note Library
12. Standard
455
________________
Reference Data Manager Reference Guide April 2002
You can define the default path for standard note neutral files using the Default Project
Control Data option. See Default Project Control Data, page 53.
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.
Key in the name of the source file or list file to be compiled and added to the active
library.
4. 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.
If a fatal error occurs while loading neutral files, the Standard Note Library is left unchanged.
456
________________ Revise Standard Note Type
Operating Sequence
1. Select the Revise option.
The system displays the standard note types in the Standard Note Library.
Note Library
12. Standard
457
________________
Reference Data Manager Reference Guide April 2002
3. 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.
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.)
458
________________ Report Standard Note Library Contents
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.
For the Print/Delete or Print/Save options, select the print queue from the list of
displayed queues.
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.
Note Library
12. Standard
459
________________
Reference Data Manager Reference Guide April 2002
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.
460
________________ Delete Standard Note Data
Operating Sequence
1. Select the Delete option.
The system displays the Standard note types in the Standard Note Library.
Select the Standard note type to be deleted from the list of note types. You can use the
scroll bar to scroll through the available files.
The system deletes the standard note type from the Standard Note Library.
Note Library
12. Standard
461
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select Extract from the Data Management form.
Select the standard note type from the list of files and select Accept. You can use the
scroll bar to scroll through the available files.
The system pulls the file out of the library and places it in the default directory defined
in the Default Project Control Data. See Default Project Control Data, page 53.
462
________________ Load Database
You must specify the maximum length of the text for each standard note type in the Standard
Note Library in an ASCII file namedstnote_max_len. This maximum length is used to load
the standard note data in the relational database. This is the same file used in the Project
Administrator to modify the database structure to support DBAccess. It must reside in the
project directory.
Entries in this file consist of one line for each standard note type with the following format.
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.
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
Note Library
12. Standard
Select Delayed Submit to Batch to specify a day and time to process the request.
463
________________
Reference Data Manager Reference Guide April 2002
464
________________ Label Description Library
Description Lib.
13. Label
The Label Description Library contains the definitions for the following basic types of labels.
(The numbers in parentheses indicate the range of label numbers for each group of label
types.) Refer to Label Types, page 466 for more information.
These labels are intelligent graphics which represent information from the non-graphical data
(databases, user data, etc.). You can update existing drawing view specific labels (1-49, 70-
130) to reflect the latest data in the database.
465
________________
Reference Data Manager Reference Guide April 2002
A displayable attribute label consists of the text and optionally, a leader line, a line terminator,
and some label enclosure graphics. There are four sub-types of Displayable Attribute Labels:
displayable attribute labels for named model items which are placed in a drawing.
labels with attribute linkages to the Drawing View Data (table 122) that report
information about the drawing view such as drawing view name and view scale
Drawing View Specific Labels are further divided into subcategories for Piping, Structural,
HVAC, and Raceway. Drawing View Specific Labels for Piping and View Independent
Labels are divided into sub-ranges for system-defined labels and user labels.
PDS delivers Design Review Labels (317-330). These labels are the only ones
processed by PDS Design Review. You can create new Design Review labels,
but the system will not access them.
A displayable attribute message has all or part of its text derived from the alphanumeric data
that is linked to a specified named item in the model.
466
________________ Label Types
Description Lib.
13. Label
these labels is always the same regardless of the screen view scale.
A displayable attribute message can also be used to create a value for another attribute, for
example, the Line Number Label attribute.
Displayable attribute messages also define the hard-coded values for Design Review labels.
U.S. practice
DIN practice
British Standard
European practice A
European practice B
International practice A
International practice B
Company practice
467
________________
Reference Data Manager Reference Guide April 2002
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 models 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.
468
________________ Label Types
Description Lib.
13. 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
2294 HVAC - Primary Label for Filter
2295 HVAC - Secondary Label for Filter
2296 HVAC - Primary Label for Damper
2297 HVAC - Secondary Label for Damper
2298 HVAC - Primary Label for Coil
2299 HVAC - Secondary Label for Coil
2300 HVAC - Primary Label for Terminal Device
2301 HVAC - Secondary Label for Terminal Device
2302 HVAC - Primary Label for Equipment
2303 HVAC - Secondary Label for Equipment
2304 HVAC - Primary Label for Hood
2305 HVAC - Secondary Label for Hood
The 2 CP clash management labels are used when the number of connect points, excluding
taps, is less than or equal to two. The 3 CP clash management labels are used when the
number of connect points, excluding taps, is greater than or equal to three.
The primary description is limited to 20 characters and the secondary description is limited to
40 characters.
469
________________
Reference Data Manager Reference Guide April 2002
470
________________ Label Description Library Manager
Description Lib.
13. Label
The Label Description Library Manager enables you to define the graphic parameters for a
label (such as level, line weight, and color code) and to define the format of the label (what
information comprises the label). You can create a new (empty) label description library or
create, revise, or delete label descriptions in an existing library.
Options
Create Library Used to create a new Label Description Library.
Create Label Data Used to create a new label description and insert it in the Label
Description Library.
Revise Label Data Used to select a label from the library, edit the file, and put the
revised file back into the library.
Delete Label Data Used to remove a label description from the library.
471
________________
Reference Data Manager Reference Guide April 2002
The system displays the approved and unapproved Label Description Library names as
defined in the RDB Management Data.
Select Accept to create the specified library file. If you specify an existing library file, the
system displays an error indicating the library already exists.
Select Accept to copy the unapproved library file to the approved library.
472
________________ Create Label Data
Description Lib.
13. Label
This option enables you to add a label description of a specified type to the Label description
Library.
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 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, page 475 for more information.
473
________________
Reference Data Manager Reference Guide April 2002
Label Subtypes
Depending on the Option selected, the system may activate one of the following screens to
further classify the type of label to be created.
474
________________ Create Label Graphic Data
Description Lib.
13. Label
Options
Create Label Attribute Data Enables you to specify the attributes which make up
the label and the format of the label.
Refer to Create Label Attribute Data, page 478 for more information.
Mass Annotation Options Enables you so 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.)
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.
475
________________
Reference Data Manager Reference Guide April 2002
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.
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 drawings 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.
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.
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.
476
________________ Create Label Graphic Data
Label Category The form displays the name label category and the user-defined
Description Lib.
13. Label
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 nonrequired
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 on to
set up the Mass Annotation options. Refer to Mass Annotation Options, page 484 for more
details.
477
________________
Reference Data Manager Reference Guide April 2002
Delete Data used to delete a selected line or item from the label description.
Edit Data used to revise a selected line or item in the label description.
Insert Data
1. Set the option to Insert Data.
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.
478
________________ Create Label Attribute Data
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.)
Description Lib.
13. Label
4. Select Option
You can select Other Data to select the attribute data type for Raceway data.
479
________________
Reference Data Manager Reference Guide April 2002
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.
480
________________ Create Label Attribute Data
6. Repeat the previous step to add additional attribute text information. This allows you to
combine attribute values and pre-formatted text.
Description Lib.
13. 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.
Delete Data
1. Set the option to Delete Data.
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.
The system displays the attributes definition form for the selected item. The active
setting is highlighted or shown in the display fields.
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.
481
________________
Reference Data Manager Reference Guide April 2002
THEN
Examples
[1][2][3]-[5]-[7]-[9]
1 - Line no:
[2] line_number_label - Character (30)
3 - Construction status:
[4] construction_stat - Character (15)
5 - Nor oper press:
[6] nor_oper_pres - Real (8.2)
[7] nor_op_pres_units - Character (10)
8 - Nor oper temp:
[9] nor_oper_temp - Real (5.0)
[10] nor_op_temp_units - Character (5)
11 - Steam out temp:
[12] steam_outlet_temp - Real (5.0)
[13] nor_op_temp_units - Character (5)
14 - Heat tracing:
[15] heat_tracing_media - Character (5)
16 - Insulation:
[17] insulation_thick - Real (5.2) with sub units (ex. ",IN,MM,etc.)
482
________________ Create Label Attribute Data
18 - Cleaning:
[19] cleaning_reqmts - Character (10)
Description Lib.
13. Label
483
________________
Reference Data Manager Reference Guide April 2002
This form allows you to specify the following options for use with the Mass Annotation
command in PD_Draw:
Steps
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.
484
________________ Revise Label Data
Description Lib.
13. Label
This option enables you to revise the graphic data or attribute data for an existing label
description.
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 for a description of all the label
types and subtypes.
The system displays the existing label for the selected label type.
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.
485
________________
Reference Data Manager Reference Guide April 2002
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 for information on these options.
7. When finished, select Accept to save the changes and return to the Revise Label
Description form.
OR
486
________________ Delete Label Data
Description Lib.
13. Label
This option enables you to delete an existing label description.
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 for a description of all the label
types and subtypes.
The system displays the existing labels for the selected label type.
The system deletes the description and refreshes the selection screen to enable you to
delete another label type.
487
________________
Reference Data Manager Reference Guide April 2002
488
________________ Report Label Data
Description Lib.
13. Label
This option creates a listing of the label types defined in the Label Description Library.
Operating Sequence
1. Select Report Label Data from the Data Management menu.
Print/Delete submits the generated report output file to the specified print
queue and deletes the output file.
Print/Save submits the generated report output file to the specified print
queue and saves the output file.
For either of the Print options, the system displays a list of queues based on information
in the Project Queue Description Library.
Report Completed
489
________________
Reference Data Manager Reference Guide April 2002
For either of the Save options, the system creates a file named LABEL.RPT in the
default directory. Portions of the listing for the delivered labels are provided below.
[1]
***************************************
[1]
490
________________ Report Label Data
***************************************
Description Lib.
13. Label
**************** Label Type = 200 ****************
Attribute Data
***************************************
***************************************
491
________________
Reference Data Manager Reference Guide April 2002
5 - Component Center
***************************************
Weld Attributes
1 - Weld Number:
[2] weld_id - Character (16)
3 - -
[4] weld_no_A - Character (8)
5 - Weld Type:
[6] weld_type_A - Character (20)
7 - Piping NPD/OD:
[8] nom_pipe_diam_A - Character (20)
9 - -
[10] outside_diam_A - Real (15.4)
11 - PMC:
[12] piping_mater_class - Character (16)
***************************************
[1]
***************************************
[1]
Piping/Tubing Data
***************************************
[1]
[1] CP_1_NOM_PIPE_DIAM
492
________________ Report Label Data
***************************************
Description Lib.
13. Label
Label Name = 2CP RED COMP GCP X RCP
[1] X [3]
[1] CP_1_NOM_PIPE_DIAM
2 X
[3] CP_2_NOM_PIPE_DIAM
***************************************
***************************************
***************************************
[1] [3]
Nozzle Data
***************************************
[1][2]-[4][5]
***************************************
493
________________
Reference Data Manager Reference Guide April 2002
[1][2]-[4]
***************************************
[1][2]-[4][5]
***************************************
[1]
***************************************
[1]
***************************************
494
________________ Label Library Merger
Description Lib.
13. Label
The Label Library Merger utility allows PDS users to copy labels from one or two
label description libraries into another library and to modify the destination library as
necessary. You can only add and remove labels with this command. To edit an
existing label or create a new label definition, use the Label Description Library
Manager command.
Features
Copy labels from one library to another.
495
________________
Reference Data Manager Reference Guide April 2002
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.
496
________________ File Menu
Description Lib.
13. Label
the Message Window, and exit the Label Library Merger.
To create a new destination library, browse to the appropriate folder in the Open
Destination Library dialog box, type a new library name in the File name text box,
and click Open. The system will then create the new label description library in the
specified location.
13.3.1.1.4 Information
This command displays information in the Message Window regarding the source
and destination libraries.
Example
MESSAGE: D:\WIN32APP\INGR\PDSHELL\lib\labels.l Opened as Source Label Library 1
MESSAGE: D:\WIN32APP\INGR\PDSHELL\lib\company_labels.l Opened as Source Label Li
MESSAGE: D:\WIN32APP\INGR\PDSHELL\lib\all_labels.l Opened as Destination Label L
497
________________
Reference Data Manager Reference Guide April 2002
13.3.1.1.5 Exit
This command closes the Label Library Merger utility.
498
________________ Edit Menu
Description Lib.
13. Label
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.
13.3.1.2.6 Delete
This command removes the selected labels from the destination library.
13.3.1.2.7 Validate
This command checks the labels in the destination library for valid label numbers,
and reports any invalid label numbers in the Message Window.
499
________________
Reference Data Manager Reference Guide April 2002
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:
500
________________ Help Menu
Description Lib.
13. Label
the Label Library Merger utility.
13.3.1.3.1 Contents
This command displays the Label Library Merger online Help file.
501
________________
Reference Data Manager Reference Guide April 2002
13.3.2 Workflow
This section describes the general workflow for the Label Library Merger utility.
1. Click Start > Programs > PD_Shell > PDS Label Library Merger to start
the Label Library Merger utility.
3. Browse to the location of the first label description library, select the library,
and click Open.
The system displays the contents of the library in the Library 1 View.
4. Repeat the previous two steps for the second label description library.
The system displays the contents of the library in the Library 2 View.
5. Click File > Open Destination Library. You can either open an existing
library for update or create a new library.
The system displays the contents of the destination library in the Destination
Library View.
502
________________ Workflow
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.
Description Lib.
13. Label
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.
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.
503
________________
Reference Data Manager Reference Guide April 2002
504
________________ Piping Assembly Library
The PAL definition is compiled and stored in Piping Assembly Language object library and
its text stored in the text library.
A Piping Assembly Library which contain the definitions for basic assemblies (macros) is
included in the product delivery.
Assembly Lib.
14. Piping
\win32app\ingr\pdshell\lib\assembly.l
The PAL definition must be processed and stored in the Piping Assembly Library.
505
________________
Reference Data Manager Reference Guide April 2002
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.
The forms delivered by Intergraph can be used as examples for customization. The following
list the form builder data for the standard form gadgets.
506
________________ Piping Assembly Language
Help
key: 456
gadget number: 995
button: automatic
Form Size
key: 403
gadget number: 997
button: automatic
Assembly Lib.
14. Piping
Exit
key: 4001
gadget number: 998
button: manual
Accept
key: 4002
gadget number: 999
button: manual
507
________________
Reference Data Manager Reference Guide April 2002
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
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.
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.
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.
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.
508
________________ Piping Assembly Language
These keywords are used with the PLACE keyword to define the type of item to be placed.
Example:
Assembly Lib.
14. Piping
PLACE BRANCH , 90_DEG , BY CP1
PLACE PIPE TO REF_PNT_A
PLACE OPTIONAL , 6Q2C01, BY CP2
RDB_INSTRUMENT, RDB_SPECIALTY
These keywords are used to place instruments and specialty items that have been defined in
the PJS using the tag number.
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.
INLET_ELEVATION
Example:
REF_PNT_A = ACTIVE_PP
COORDINATE_1 = INLET_ELEVATION
509
________________
Reference Data Manager Reference Guide April 2002
Orientation
ACTIVE
EAST, NORTH, UP
WEST, SOUTH, DOWN
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.
These keywords define an assembly end point as a specified coordinate value. An assembly
end definition is used to define the endpoints of an assembly. This is required when the
assembly is being placed into a pipe so that the pipe is broken properly and the assembly
inserted (as in the case of a valve assembly: flange - valve - flange).
These keywords set reference points at specified coordinate values. You can define up to 20
points on the assembly for future reference in the PAL definition.
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).
510
________________ Piping Assembly Language
These keywords specify the generic termination type for use in conditional testing.
This keyword contains the number of connect points of the component just placed. It can be
Assembly Lib.
14. Piping
used in branch placement to determine whether to use CP2 or CP3 as a reference point.
Example:
COMPONENT_TAG (3246)
This keyword defines the tag for the component to be placed. You can prompt for the tag or
use the tutorial interface using the designated field and command numbers.
This keyword defines the number of UORs per Subunit defined in the model. It can be used
to calculate tap location.
511
________________
Reference Data Manager Reference Guide April 2002
These keywords define the active placement point which can be used in the connect to
segment and point in space routines. These keywords are initially set to the active placement
point of the assembly at the start of the assembly placement.
These keywords are used to receive user input from the tutorial to define the active placement
point. The Coordinate keywords identify actual points and the Dimension keywords identify
distances and offsets. The Coordinate keywords are only used for elevation values, not
Easting or Northing values.
These keywords are defined as the active primary, secondary and normal axis at the time the
assembly is placed. They are automatically set internally at the start of placement and cannot
be modified.
Dimension Definition
DIMENSION_1 (3141), DIMENSION_2 (3142), ... DIMENSION_20 (3160)
This keyword moves a specified distance in the direction of the active primary. It is useful in
placing a variable length pipe by moving out a specified distanced and calling place pipe.
Example:
MOVE_DISTANCE = DIMENSION_1
PLACE PIPE TO REF_PNT_A
512
________________ Piping Assembly Language
This keyword reads the spec record for the commodity item and assigns values for the
following keywords:
Example:
Assembly Lib.
14. Piping
LOAD_SPEC_DATA = 6Q1C80
IF ( GEN_TYPE_1 .EQ. BOLTED ) THEN
OPTION_RATING = PR_RATING_1
OPTION_END_PREP = TERM_TYPE_1
PLACE OPTIONAL , 6Q2C01 , BY CP2
ENDIF
These keywords set the active first size or second size placement parameter a step down/up in
the NPD piping material class table. (The system uses the next entry in the NPD table from
the active size as the first/second size for a step up or next higher size and uses the previous
entry in the NPD table from the active size as the first/second size for a step down or lower
size). This particular statement in PAL is used as the active size (first or second) in the
placement of all the following components, until the active size is redefined. If you do not
include a line size in the PAL definition, the active size at the time of placement of the piping
assembly will be used.
These keywords define coordinate values for the component just placed.
513
________________
Reference Data Manager Reference Guide April 2002
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.
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.
DISPLAY_TUTORIAL = PALCST
DISPLAY = prompt_message
used to display any ascii keyword.
DISPLAY_NUMERIC = npd_a
used to display any numeric keyword.
COMMAND = GET_TUTORIAL_DATA
used to get data from the user at placement via a tutorial.
The variables APP_X, APP_Y, and APP_Z are assigned the X, Y, and Z values of the
current active placement point. This command is useful for variable distance changes in
assemblies, and you need to know the new coordinates.
514
________________ Piping Assembly Language
Point in Space
Example: COMMAND = POINT_IN_SPACE
The values of the keywords APP_X, APP_Y, 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.
Assembly Lib.
14. Piping
The command syntax is the same as for connecting to a reference point except that the
keywords APP_X, APP_Y, APP_Z are used as the coordinates. These points are assumed
to lie on a piping segment whereas a reference point identifies a connect point. The keywords
should be set before this command is called.
ORIENT_PRIMARY = LOCAL_X
This statement orients the primary axis to be the same as the primary at the beginning of the
assembly placement.
ORIENT_SECONDARY = LOCAL_Y
This statement orients the secondary to be the same as the secondary at placement.
ORIENT_SECONDARY = INVERT
This statement allows the secondary to be inverted from its current position. You can also use
INVERT for the primary axis.
This statement performs a table lookup on the 90 degree branch table to determine the branch
component type given the current first and second size. If the branch is on a piping segment
or in free space, then Placement BY CENTER should be used. If you are placing fitting to
fitting, you should specify connect point placement (BY CP1).
515
________________
Reference Data Manager Reference Guide April 2002
Example:
IF ( END_PREP_A .GE. 2.0 .and. END_PREP_A .LE. 199) THEN
OPTION_RATING = RATING_A
OPTION_END_PREP = END_PREP_A
PLACE OPTIONAL, 6Q2C01 , BY CP2
ENDIF
OPTION_TBL_SUFFIX
TBL_SUFFIX_GREEN, TBL_SUFFIX_RED
END_PREP_1, END_PREP_2, ... END_PREP_5
TBL_SUFFIX_A (301), TBL_SUFFIX_B (302), ... TBL_SUFFIX_E (305)
These keywords provide the ability to select the correct optional flange, when the flange is
being placed by its welded end.
Examples:
OPTION_CODE = PROMPT
OPTION_CODE = 790
This keyword sets the option code for the next component placed. If the PROMPT keyword
is used, the system activates the Option Code Selection tutorial at placement to enable the user
to select the option code. Otherwise the option code is hard-coded.
Logical Marks
CHECK_MARK
516
________________ Piping Assembly Language
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.
Assembly Lib.
14. Piping
MATERIALS_CLASS_D (3264), MATERIALS_CLASS_E (3265), ...
MATERIALS_CLASS_J (3270)
Example:
MATERIALS_CLASS_B = USER_INPUT
ACTIVE_MATERIALS_CLASS = MATERIALS_CLASS_B
The values for MATERIALS_CLASS_A, through _J are stored locally until a statement
with ACTIVE_MATERIALS_CLASS is executed. At that time, the Materials Class in the
active data is updated to the assigned value. This enables you to obtain up to three different
classes from the tutorial at the start which can be used as needed in the definition.
Component Attributes
NPD_A (3221), NPD_B (3222), NPD_C (3223)
NPD_D (3284), NPD_E (3285), ... NPD_J (3290)
517
________________
Reference Data Manager Reference Guide April 2002
Example:
BEND_ANGLE_A = PROMPT
ACTIVE_BEND_ANGLE = BEND_ANGLE_B
The active bend angle in the model is not set until a statement with ACTIVE_BEND_ANGLE
is executed. At that time, the active bend angle is assigned the appropriate value and the next
component placed uses that value. The active bend angle is set to 0 after placement.
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.
You can use these keywords to test specific values of the active segment data or active
component data, where # refers to the column (attribute) number for the applicable database
table. The active component data is represented by the last component placed or the
component to which the user is connected.
518
________________ Piping Assembly Language
You can use these keywords to pre-define specific values for the component to be placed,
where # refers to the column (attribute) number for the applicable database table. This
functionality is similar to the Pre-Define Component Data option of the Place Component
command.
Assembly Lib.
14. Piping
designated as having the fabrication category defined by user versus by system
such that reconstructing the component will not override the user value with
the value in the Reference Database.
Having the ability to pre-define the fabrication category within a control station piping
assembly will enable you to automatically override the RDB specification of the fabrication
category of a single field component, such as a small diameter control valve, in what would
otherwise be a shop spool.
519
________________
Reference Data Manager Reference Guide April 2002
The following PAL definitions should be used to specify the tap location before making the
PLACE TAP request.
TAP_LOCATION = COMPONENT_CENTER
CP_1_LOCATION
CP_2_LOCATION
COMPUTE_FOR_ELBOLET_USING_CP1
COMPUTE_FOR_ELBOLET_USING_CP2
OR
The tap orientation should also be set before making the PLACE TAP request using the PAL
orientation commands. The active orientation at time of placement (tap) is used.
520
________________ Sample Piping Assembly Files
DRAIN
# Drain assembly
PAL DRAIN
Assembly Lib.
14. Piping
!
! 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
521
________________
Reference Data Manager Reference Guide April 2002
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
FIRST_SIZE = NPD_A
NPD_C = SECOND_SIZE
DISPLAY_NUMERIC = NPD_C
PROMPT_MESSAGE = Enter Branch Size
DISPLAY = PROMPT_MESSAGE
COMMAND = GET_TUTORIAL_DATA
SECOND_SIZE = NPD_C
PLACE BRANCH , 90_DEG , BY CP1
OPTION_CODE = PROMPT
PLACE FITTING , 6Q3C88 , BY CP1
522
________________ Sample Piping Assembly Files
ORIENTATION = PROMPT
PLACE VALVE , 6Q1C80 , BY CP1
CONNECT TO REF_PNT_A
PLACE FLANGE , 6Q2C01 , BY CP2
ORIENTATION = PROMPT
PLACE VALVE , 6Q1C01 , BY CP1
Assembly Lib.
14. Piping
Graphics Placed by Pump Discharge Assembly
523
________________
Reference Data Manager Reference Guide April 2002
524
________________ Piping Assembly Library Manager
Refer to Piping Assembly Library, page 505, for more information on this library and refer to
Piping Assembly Language, page 506, for more information on the PAL files.
Assembly Lib.
14. Piping
Before using this command
Define the location of the approved and unapproved (if applicable) Assembly Library
files in the Reference Database Management Data.
You must have write access to the specified file and directory path.
14.2.1 Options
Create Library used to create a new Piping Assembly Library. See page 527.
Compress used to compress the Piping Assembly library. See page 527.
525
________________
Reference Data Manager Reference Guide April 2002
Create/Batch Data used to compile Piping Assembly Language Source files via
batch processing. See page 529.
Revise Data used to select an PAL module from the library, edit the file, and put
the revised file back into the library. See page 530.
Delete Data used to remove an PAL module from the library. See page 532.
Report Data used to create a report of the library contents. See page 533.
List Data used to display the Eden modules in the library. See page 534.
Extract Data used to extract an Eden module from the library for editing or
printing. See page 535.
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.
526
________________ Create Library
The system displays the approved and unapproved Piping Assembly Library names as defined
in the RDB Management Data.
Select Accept to create the specified library files. If you specify an existing library file, the
system displays an error indicating the library already exists.
Assembly Lib.
14. Piping
14.2.3 Compress
This option is used to compress the Piping Assembly library. Any tables which have been
deleted from the library will be removed.
Select Accept to copy the unapproved library file to the approved library.
527
________________
Reference Data Manager Reference Guide April 2002
Set Assembly Path and Assembly Node in the RDB Management Data to the location
of the assembly source files.
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.
Key in the name of the PAL file or list file to be compiled and added to the active
library.
4. 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.
528
________________ Create/Batch Assembly Data
Assembly Lib.
14. Piping
Set Assembly Path and Assembly Node in the RDB Management Data to the location
of the assembly source files.
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.
Key in the name of the PAL file or list file to be compiled and added to the active
library and select Accept.
4. 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.
For Delayed Submit set the time and day to process the files.
529
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Revise option.
The system displays the PAL modules in the Piping Assembly Library.
530
________________ Revise Piping Assembly Data
3. 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.
Assembly Lib.
14. Piping
Make any changes to the displayed file.
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.)
If an error occurs in revising a piping assembly, the system invoke the editor
automatically to give you an opportunity to correct the problem.
4. You can select other files to edit or select exit to return to the data management form.
531
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Delete option.
Select the modules to be deleted from the list of modules. You can use the scroll bar to
scroll through the available files.
The system deletes the modules from the Piping Assembly Library.
532
________________ Report Assembly Data
Operating Sequence
1. Select the Report option from the Data Management form.
Assembly Lib.
14. Piping
2. Revise Report Parameters
Key in the file information for the location of the report file to be created.
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 assemblies in
the default source file location.
533
________________
Reference Data Manager Reference Guide April 2002
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.
534
________________ Extract Assembly Data
Define the node name and path for the location of the PAL files in the Default Project
Control Data or using the fields at the bottom of the Assembly Data Management form.
Assembly Lib.
14. Piping
Operating Sequence
1. Select Extract from the Data Management form.
Select the modules from the list of files and select Accept. You can use the scroll bar to
scroll through the available files.
The system pulls the files out of the library and places them in the default directory
specified in the Project Control Data. The system also writes the names of the
extracted files to a file named PD_pal_list.
If the list file is less than 24 hours old, the system appends the entries to the file,
otherwise it overwrites the file.
535
________________
Reference Data Manager Reference Guide April 2002
536
________________ Reference Database Revision Manager
Creation of any of these reports also generates a summary report. The summary report is
created and named according to user-specified information provided on the Reference
Database Revision Manager form. Selecting the option to print the summary report will
also force the printing of the individual report that initiated the creation of the summary
report.
Manager
15. Revision
Options
Reference Data Conflict Report
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 .
537
________________
Reference Data Manager Reference Guide April 2002
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 wish to determine which components need to be
reconstructed or updated from the RDB.
If your project was created with PDS version 6.0, use the Reference Data
Conflict Report instead.
Proposed RDB Changes Report 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.
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.
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.
538
________________ Reference Database Revision Manager
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:
Manager
15. Revision
1. Item not found in the spec.
4. Discrepancy between model and RDB for any of the following attributes:
539
________________
Reference Data Manager Reference Guide April 2002
This command is used to coordinate between revisions in the Reference Database and the
implied changes which are required in the model. It also reports piping and instrument
components that require reconstruction or recalculations as a result of piping segment data
changes in the model.
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.
540
________________ Reference Data Conflict Report
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.
The first size and second size are determined from the piping segment data and not from the
component itself.
Manager
15. Revision
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. That data which may impact the geometry and/or the
symbology in the model is designated by an asterisk.
Note that user overrides of fabrication category and schedule/thickness will not be included in
the report.
541
________________
Reference Data Manager Reference Guide April 2002
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 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:
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.
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.
542
________________ Reference Data Conflict Report
The system compares the following data for consistency between the model and the Reference
Database for piping specialties and instruments. That data which may impact the geometry
and/or the symbology in the model is designated by an asterisk.
The system compares the gasket thickness for each bolted end of a piping specialty or
instrument 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 green specification data in the Reference Database with all connect
points for that component in the model which are designated as having green connect point
properties.
Manager
15. Revision
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:
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.
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.
543
________________
Reference Data Manager Reference Guide April 2002
Operating Sequence
1. Select the Reference Data Conflict Report option.
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.
Set the toggle to Submit Immediately or select Delayed Submit and fill in the day and
time to process the request.
544
________________ Reference Data Conflict Report
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
Reference Data Conflict report file has an extension of .rpt and is created in the model
directory as <model_number>.rpt . If the summary report is printed as a result of
creating this report, this report will also be printed.
Manager
15. Revision
545
________________
Reference Data Manager Reference Guide April 2002
The RBD was revised and you did not reconstruct the affected components. Then you
upgraded the project to PDS version 6.0, at which time all components were updated
to have the new last_placed_date attribute set to the date the upgrade occurred.
You will need to know the date the RDB was modified in order to find which
components require reconstruction as a result of the RDB change. This report may
return false discrepancies because it will include those items that were placed after the
RDB was changed.
In short, we recommend using this report only when the RDB is changed prior to
upgrading to PDS version 6.0, and affected components have not been reconstructed
to reflect the RDB change.
The Reconstruct Component command is required for any component which has a
dimension table revised and the Update from Reference Database command is required for
any component which has a weight table revised.
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.
546
________________ Table Change Report
The title page for the report will include the sub-title, Table Change Report.
Piping specialties and instruments are excluded from this report when the specification data
and the geometry data have been defined by the user (not defined in the Reference Database).
You can use the Review Reference Database Revision Management Report command to
review any component in the model requiring reconstruction or updating as a result of the
components geometric or weight data being changed by a table revision. In support of this
review capability, the system creates an indexed file, the RDB Revision Management
Component List, 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 the Review
Reference Data Revision Report command.
Any component, previously reported as needing 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.
Piping and instrument components in any model which do not have a corresponding record in
the applicable table of the Piping Design Database are ignored and excluded from the report.
These components, if any, are reported through the Database Verification command of the
Project Administrator.
Manager
15. Revision
Operating Sequence
1. Select the Table Change Report option.
547
________________
Reference Data Manager Reference Guide April 2002
Select the Physical Data Library to process, such as U.S. Practice, DIN, or Company
Practice and select Accept.
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.
Set the toggle to Full List or Sub-String. For Sub-String, key in a string to limit the
tables to be listed.
THEN
The system displays a list of all dimension and weight tables (or those which match a
specified substring).
548
________________ Table Change Report
Select the dimension tables to be considered in the creation of the revision management
report.
OR
You can select Process All to process all the listed tables (those which meet the
specified revision date and substring).
THEN
For each of the selected tables, the system displays the table data in the Table Data
Display form.
Manager
15. Revision
6. Select Table Entry
For each table, you can specify which entries (up to a total of 200 entries) in the table
have been revised.
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.
549
________________
Reference Data Manager Reference Guide April 2002
8. The summary report path and report node are determined by the settings defined with
the Report Manager.
You can change the location or name for the summary report output or use the defaults.
9. Select the desired output method for the summary report: Print/Delete, Print/Save, or
Save.
Set the toggle to Submit Immediately or select Delayed Submit and fill in the day and
time to process the request.
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
table change report file has an extension of .tcr and is created in the model directory as
<model_number>.tcr . If the summary report is printed as a result of creating this
report, this report will also be printed.
550
________________ Reference Data Impact Report
Manager
15. Revision
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, etc. 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.
15.3.1 Examples
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.
551
________________
Reference Data Manager Reference Guide April 2002
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
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
The system displays the selected operator and prompts you to key in an 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).
552
________________ Reference Data Impact Report
If the attribute is code-listed, the system displays a list of values from the Standard Note
Library.
The system validates the input and displays the defined search criteria in the Search
Criteria display field.
OR
Accept the defined search criteria and activate the Reference Database Revision
Manager form.
Manager
15. Revision
7. Revise the search criteria, if necessary, using the Revise Search Criteria option.
OR
553
________________
Reference Data Manager Reference Guide April 2002
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.
Set the toggle to Submit Immediately or select Delayed Submit and fill in the day and
time to process the request.
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
reference data impact report file has an extension of .imp and is created in the model
directory as <model_number>.imp . If the summary report is printed as a result of
creating this report, this report will also be printed.
554
________________ Proposed RDB Changes Report
You must make changes to the unapproved Material Reference Database in order to
assess the effect of these changes. You are responsible for restoring the unapproved
Material Reference Database to its original state if you decide not to pursue these
changes.
Manager
15. Revision
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.
555
________________
Reference Data Manager Reference Guide April 2002
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. That data which may impact the geometry and/or the
symbology in the model is designated by an asterisk.
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:
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.
556
________________ Proposed RDB Changes Report
The system compares the following data for consistency between the model and the Reference
Database for piping specialties and instruments. That data which may impact the geometry
and/or the symbology in the model is designated by an asterisk.
Manager
15. Revision
* table suffix - green * geometric industry standard
* end preparation - red weight code
* pressure rating - red fabrication category
* schedule/thickness - red materials grade
* table suffix - red
The system compares the gasket thickness for each bolted end of a piping specialty or
instrument 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 specialty or
instrument which has been designated as a tap with the appropriate data, i.e. either the
specification data from the Tap Properties Data in the Reference Database or from another
connect point. Piping specialties and instruments are excluded from this report when the
specification data and the geometry data is defined by the user (not defined in the Reference
Database).
The system compares the green specification data in the Reference Database with all connect
points for that component in the model which are designated as having green connect point
properties.
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:
557
________________
Reference Data Manager Reference Guide April 2002
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.
Operating Sequence
1. Select the Proposed RDB Changes Report option.
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.
558
________________ Proposed RDB Changes Report
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.
Set the toggle to Submit Immediately or select Delayed Submit and fill in the day and
time to process the request.
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.
Manager
15. Revision
559
________________
Reference Data Manager Reference Guide April 2002
560
________________ Verify RDB Library
As a final step within the project upgrade process, the system verifies the integrity of the
binary tree structure within each of the reference data libraries. If an error is detected, a
specific warning message will be reported, both interactively and in the upgrade log. In this
event, you should contact Intergraph immediately for assistance in repairing the library.
The Verify RDB Library utility has been provided to allow the capability to verify the
integrity of the binary tree structure on demand.
The Verify RDB Library icon is located in the PD_Shell program group on systems upon
which the PD_Data software has been loaded locally; double-click on this icon to activate the
command.
Steps
1. Execute the command by double-clicking on the Verify RDB Library icon in the
PD_Shell program group.
Library
16. Verify RDB
The system activates the Reference Database Library Verification Utility form, and
prompts you to select the appropriate project number from the list.
561
________________
Reference Data Manager Reference Guide April 2002
2. Select the desired project number, 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:
562
________________ Verify RDB Library
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
Library
16. Verify RDB
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
563
________________
Reference Data Manager Reference Guide April 2002
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
564
________________
Appendix A: Reference Data Manager Error Messages
Messages
A. Error
Messages
The PDS 3D products share common message files contained in the
win32app\ingr\pdshell\msg directory.
565
________________
Reference Data Manager Reference Guide April 2002
566
________________ Appendix B: Codelists
Appendix B Codelists
This section details the codelists used in PDS.
B. Codelists
CL36 Structural Approval Status 573
CL37 HVAC Approval Status 573
CL50 Hold Status 574
CL69 Equipment Divisions/Form Code 574
567
________________
Reference Data Manager Reference Guide April 2002
568
________________ Appendix B: General Comments
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 parenthesis following the name of the codelist set.
B. Codelists
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.
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.
569
________________
Reference Data Manager Reference Guide April 2002
Codelist set This is the number of the codelist set that identifies a specific quantity.
For example, codelist set 1028 includes the units of measure that apply to
the quantity "mass".
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 Two sets of columns define the conversion of variables expressed in the
destination unit: 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,
Similarly,
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.
570
________________ Appendix B: General Comments
Conversion to Two sets of columns define the conversion of the units shown under the
first unit in CL: 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.
B. Codelists
A is the factor in the column captioned Factor A.
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:
571
________________
Reference Data Manager Reference Guide April 2002
572
________________ Appendix B: General Comments
B. Codelists
NOTE: In editing this codelist set, do not change the meaning
of existing codelist values. Some data displays require that only
values to the left of the "=" sign be shown; other reports require
that only values to the right of the "=" sign be displayed.
The following are the requirements in use of the "approval status."
2 reserved for approved
3 reserved for not approved
11-20 reserved for approved
21-30 reserved for not approved
1 = [Blank]
2 = A =Approved
3 = NA=Not approved
0= New
1 = Existing
2 = Future
3 = User 1
4 = User 2
1 = New
2 = Existing
3 = Dismantle
4 = Future
573
________________
Reference Data Manager Reference Guide April 2002
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]
574
________________ Appendix B: General Comments
161 = F [Foam]
191 = G [Gas]
B. Codelists
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]
212 = GI [Inert gas]
215 = GLP [LP gas]
218 = GM [Make-up gas]
221 = GN [Natural gas]
224 = GNI [Nitrogen gas]
227 = GOX [Oxygen gas]
230 = GP [Purge gas]
233 = GR [Reformed gas]
236 = GS [Synthesis gas]
239 = GSO [Sour gas]
242 = GSW [Sweet gas]
245 = GW [Waste gas
250 = GZ [Other 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]
575
________________
Reference Data Manager Reference Guide April 2002
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]
576
________________ Appendix B: General Comments
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]
767 = WCR [Cooling water return]
768 = WCS [Cooling water supply]
771 = WPT [Potable water]
772 = [Blank] [Potable water or instrument air]
773 = WDM [Demineralized water]
775 = WFA [Aboveground fire water]
777 = WFI [Filtered water]
B. Codelists
779 = WFU [Underground fire water]
781 = WG [Glycol water]
783 = WGL [Gland water]
785 = WGR [Glycol water return]
786 = WGS [Glycol water supply]
789 = WH [Hot water]
791 = WHR [Hot water return]
792 = WHS [Hot water supply]
795 = WI [Chilled water]
797 = WIR [Chilled water return]
798 = WIS [Chilled water supply]
801 = WK [Treated water]
803 = WN [Brine water]
805 = WP [Process water]
807 = WR [Raw water]
809 = WS [Sea water]
811 = WSR [Sea water return]
812 = WSS [Sea water supply]
815 = WT [Test water]
817 = WU [Utility water]
819 = WW [Waste water]
830 = WZ [Other 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]
577
________________
Reference Data Manager Reference Guide April 2002
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
578
________________ Appendix B: General Comments
B. Codelists
170 = A120
180 = A134-A36
182 = A134-A283-A
183 = A134-A283-B
184 = A134-A283-C
185 = A134-A283-D
186 = A134-A285-A
187 = A134-A285-B
188 = A134-A285-C
190 = A134-A570-30
191 = A134-A570-33
192 = A134-A570-36
193 = A134-A570-40
194 = A134-A570-45
195 = A134-A570-50
200 = A135-A
202 = A135-B
210 = A139-A
212 = A139-B
214 = A139-C
216 = A139-D
218 = A139-E
220 = A179
230 = A181-CL60
234 = A181-CL70
240 = A211-A570-30
241 = A211-A570-33
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
579
________________
Reference Data Manager Reference Guide April 2002
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
580
________________ Appendix B: General Comments
B. Codelists
536 = A182-F22a
540 = A202-A
542 = A202-B
550 = A203-A
552 = A203-B
554 = A203-D
556 = A203-E
560 = A204-A
562 = A204-B
564 = A204-C
576 = A217-C5
578 = A217-C12
580 = A217-CA15
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
581
________________
Reference Data Manager Reference Guide April 2002
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
760 = A385-7 Cl.1
761 = A385-7 Cl.2
770 = A387-2 Cl.1
771 = A387-2 Cl.2
774 = A387-5 Cl.1
775 = A387-5 Cl.2
778 = A387-9 Cl.1
779 = A387-9 Cl.2
780 = A387-11 Cl.1
781 = A387-11 Cl.2
782 = A387-12 Cl.1
783 = A387-12 Cl.2
784 = A387-21 Cl.1
785 = A387-21 Cl.2
786 = A387-22 Cl.1
787 = A387-22 Cl.2
794 = A420-WPL3
798 = A420-WPL8
800 = A426-CP1
802 = A426-CP2
804 = A426-CP5
806 = A426-CP5b
808 = A426-CP7
810 = A426-CP9
812 = A426-CP11
814 = A426-CP12
816 = A426-CP15
817 = A426-CPCA15
820 = A426-CP21
822 = A426-CP22
830 = A553-Type I
832 = A553-Type II
835 = A645
840 = A671-CF70
842 = A671-CF71
850 = A672-L65
852 = A672-L70
854 = A672-L75
860 = A691-CM65
862 = A691-CM70
864 = A691-CM75
582
________________ Appendix B: General Comments
866 = A691-0.5Cr
868 = A691-1Cr
870 = A691-1.25Cr
872 = A691-2.25Cr
874 = A691-3Cr
876 = A691-5Cr
878 = A691-9Cr
B. Codelists
934 = A167-309
935 = A167-309S
938 = A167-310
939 = A167-310S
942 = A167-316
943 = A167-316L
946 = A167-317
947 = A167-317L
950 = A167-321
952 = A167-347
954 = A167-348
960 = A182-F10
964 = A182-F304
965 = A182-F304H
966 = A182-F304L
968 = A182-F310
970 = A182-F316
971 = A182-F316H
972 = A182-F316L
974 = A182-F321
975 = A182-F321H
978 = A182-F347
979 = A182-F347H
982 = A182-F348
983 = A182-F348H
990 = A240-X8M
992 = A240-302
994 = A240-304
995 = A240-304L
996 = A240-304H
998 = A240-305
1000 = A240-309S
1004 = A240-310S
1006 = A240-316
1007 = A240-316L
1010 = A240-317
1011 = A240-317L
1014 = A240-321
1016 = A240-347
1018 = A240-348
1020 = A240-405
1022 = A240-410
1023 = A240-410S
1026 = A240-429
1028 = A240-430
1040 = A268-TP329
583
________________
Reference Data Manager Reference Guide April 2002
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
584
________________ Appendix B: General Comments
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
B. Codelists
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
585
________________
Reference Data Manager Reference Guide April 2002
586
________________ Appendix B: General Comments
B. Codelists
1606 = B167-600 (N06600) hot fin/hot fin annld, <=5in OD
1607 = B167-600 (N06600) hot fin/hot fin annld, >5in OD
1610 = B168-600 (N06600) hot rolled plt annld
1611 = B168-600 (N06600) hot rolled plt AR
1614 = B333-B (N10001) sln annld plt
1615 = B333-B (N10001) sln annld sheet
1616 = B333-B-2 (N10665) sln annld
1620 = B335-B-2 (N10665) sln annld
1624 = B366-WPHB (N10001)
1626 = B366-WPHX (N06002)
1628 = B366-WPN (N02200)
1630 = B366-WPNC (N04400)
1632 = B366-WPNC1 (N06600)
1634 = B366-WPNL (N02201)
1636 = B366-WPNLWX
1638 = B366-WPNWX
1642 = B407-800 (N08800) cold drwn annld
1643 = B407-800 (N08800) hot fin/hot fin annld
1646 = B407-800H (N08810) cold drwn sln annld/hot fin
1648 = B443-625 (N06625) annld
1650 = B444-625 (N06625) annld
1652 = B446-625 (N06625) annld
1654 = B464-20Cb (N08020) annld
1656 = A494-CW-12M-1
1658 = A494-CW-12M-2
1660 = A494-CY-40
1664 = B574-C-4 (N06455) sln annld
1666 = B574-C-276 (N10276) sln annld
1670 = B575-C-4 (N06455) sln annld
1672 = B575-C-276 (N10276) sln annld
1676 = B581-G (N06007) sln annld
1680 = B582-G (N06007) sln annld
1684 = B612-200 (N02200) hot rolled plt AR
1688 = B619-20-Mod (N08320) sln annld
1700 = B619-B (N10001) sln annld
1702 = B619-B-2 (N10665) sln annld
1704 = B619-C-4 (N06455) sln annld
1706 = B619-C-276 (N10276) sln annld
1708 = B619-G1 (N06007) sln annld
1710 = B619-X (N06002) sln annld
1714 = B620-20-Mod (N08320) sln annld
1718 = B621-20-Mod (N08320) sln annld
1722 = B622-B (N10001) sln annld
1724 = B622-B-2 (N10655) sln annld
1726 = B622-C-4 (N06455) sln annld
1728 = B622-C-276 (N10276) sln annld
587
________________
Reference Data Manager Reference Guide April 2002
588
________________ Appendix B: General Comments
B. Codelists
1936 = B210-3003 temper 0
1938 = B210-3003 temper H14
1940 = B210-3003 temper H18
1942 = B210-3003 temper H112
1944 = B210-5052 temper 0
1946 = B210-5052 temper H32
1948 = B210-5052 temper H34
1950 = B210-5083 temper 0
1952 = B210-5083 temper H112
1954 = B210-5086 temper 0
1956 = B210-5086 temper H32
1958 = B210-5086 temper H34
1960 = B210-5086 temper H112
1962 = B210-5154 temper 0
1964 = B210-5154 temper H34
1966 = B210-5456 temper 0
1968 = B210-5456 temper H112
1970 = B210-6061 temper T4
1972 = B210-6061 temper T4, wld
1974 = B210-6061 temper T6
1976 = B210-6061 temper T6, wld
1978 = B210-6063 temper T4
1980 = B210-6063 temper T4, wld
1982 = B210-6063 temper T5, wld
1984 = B210-6063 temper T6
1986 = B210-6063 temper T6, wld
1988 = B210-Alclad 3002 temper 0
1990 = B210-Alclad 3003 temper H14
1992 = B210-Alclad 3003 temper H18
1994 = B210-Alclad 3002 temper H112
2010 = B221-1060 temper 0
2012 = B221-1060 temper H112
2014 = B221-1100 temper 0
2016 = B221-1100 temper H112
2018 = B221-3003 temper 0
2020 = B221-3003 temper H112
2022 = B221-5052 temper 0
2024 = B221-5053 temper 0
2026 = B221-5086 temper 0
2028 = B221-5154 temper 0
2030 = B221-5454 temper 0
2032 = B221-5456 temper 0
2034 = B221-6061 temper T4
2036 = B221-6061 temper T4, wld
2038 = B221-6061 temper T6
2040 = B221-6061 temper T6, wld
589
________________
Reference Data Manager Reference Guide April 2002
590
________________ Appendix B: General Comments
B. Codelists
2240 = B361-WP6061 temper T6
2242 = B361-WP6061 temper T6, wld
2244 = B361-WP6063 temper T4
2246 = B361-WP6063 temper T4, wld
2248 = B361-WP6063 temper T6
2250 = B361-WP6063 temper T6, wld
2252 = B361-AP Alclad 3003 temper 0
2254 = B361-AP Alclad 3003 temper H112
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]
3154 = G154 [Flat, Buna-N]
3171 = G171 [Flat, Hypalon]
3175 = G175 [Flat, Kel-F]
3189 = G189 [Flat, neoprene]
3195 = G195 [Flat, polyethylene]
3204 = G204 [Flat, Teflon]
3210 = G210 [Flat, Viton]
3231 = G231 [Flat, soft-iron]
3234 = G234 [Flat, 304]
3236 = G236 [Flat, 321/347
591
________________
Reference Data Manager Reference Guide April 2002
592
________________ Appendix B: General Comments
B. Codelists
3661 = G661 [Sprl-wnd, 304-W, mica/graph-F, CS-CR, 304-IR]
3663 = G663 [Sprl-wnd, 304-W, graph-F, CS-CR, 304-IR]
3665 = G665 [Sprl-wnd, 304-W, asb-F, CS-CR, 304-IR]
3669 = G669 [Sprl-wnd, 304-W, Teflon-F, CS-CR, 304-IR
593
________________
Reference Data Manager Reference Guide April 2002
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]
4045 = B45 [A193-B8C Cl.1, lub, w/A194-8C]
4046 = B46 [A193-B8 Cl.1, lub, w/A194-8]
4047 = B47 [A193-B8M Cl.1, >=1.5" lub, w/A194-8M]
4048 = B48 [A193-B8M Cl.1, lub, w/A194-8M
4050 = B50 [A193-B8T Cl.1, >=1.5" lub, w/A194-8T]
4051 = B51 [A193-B8T Cl.1, lub, w/A194-8T]
4061 = B61 [A193-B16, >=1.5" lub, w/A194-3]
4062 = B62 [A193-B16, lub, w/A194-3]
4064 = B64 [A193-B16, >=1.5" lub, w/A194-4]
4065 = B65 [A193-B16, lub, w/A194-4]
4066 = B66 [A193-B16, >=1.5" lub, w/A194-7]
4067 = B67 [A193-B16, lub, w/A194-7]
4068 = B68 [A193-B16, >=1.5" lub, w/A194-8M]
4069 = B69 [A193-B16, lub, w/A194-8M]
4071 = B71 [A307-B w/A563-A]
4074 = B74 [A320-L7, >=1.5" lub, w/A194-4]
4075 = B75 [A320-L7, lub, w/A194-4]
4076 = B76 [A320-B8, >=1.5" lub, w/A194-8]
4077 = B77 [A320-B8, lub, w/A194-8]
4078 = B78 [A320-B8, >=1.5" lub, w/A194-B8]
4079 = B79 [A320-B8, lub, w/A194-B8]
4080 = B80 [A320-B8T Cl.1 >=1.5" lub, w/A194-B8]
4081 = B81 [A320-B8T Cl.1 lub, w/A194-B8]
4082 = B82 [A325 w/A325]
4084 = B84 [A453-660, >=1.5" lub, w/A453-660]
4085 = B85 [A453-660, lub, w/A453-660
4500 = Undefined
594
________________ Appendix B: General Comments
B. Codelists
6025 = BS3602:PART 1:ERW430:Cat 2
6026 = BS3602:PART 1:CEW360:Cat 1
6027 = BS3602:PART 1:CEW360:Cat 2
6028 = BS3602:PART 1:CEW430:Cat 1
6029 = BS3602:PART 1:CEW430:Cat 2
595
________________
Reference Data Manager Reference Guide April 2002
596
________________ Appendix B: General Comments
B. Codelists
6224 = BS1501-164 400A LT20
6225 = BS1501-164 400B RT
6226 = BS1501-164 400B LT0
6227 = BS1501-164 400B LT20
6228 = BS1501-223 460A RT
6229 = BS1501-223 460A LT0
6230 = BS1501-223 460A LT15
6231 = BS1501-223 460A LT30
6232 = BS1501-223 460B RT
6233 = BS1501-223 460B LT0
6234 = BS1501-223 460B LT15
6235 = BS1501-223 460B LT30
6236 = BS1501-223 490A RT
6237 = BS1501-223 490A LT0
6238 = BS1501-223 490A LT15
6239 = BS1501-223 490A LT30
6240 = BS1501-223 490B RT
6241 = BS1501-223 490B LT0
6242 = BS1501-223 490B LT15
6243 = BS1501-223 490B LT30
6244 = BS1501-224 400A RT
6245 = BS1501-224 400A LT0
6246 = BS1501-224 400A LT20
6247 = BS1501-224 400A LT30
6248 = BS1501-224 400A LT40
6249 = BS1501-224 400A LT50
6250 = BS1501-224 400B RT
6251 = BS1501-224 400B LT0
6252 = BS1501-224 400B LT20
6253 = BS1501-224 400B LT30
6254 = BS1501-224 400B LT40
6255 = BS1501-224 400B LT50
6256 = BS1501-224 430A RT
6257 = BS1501-224 430A LT0
6258 = BS1501-224 430A LT20
6259 = BS1501-224 430A LT30
6260 = BS1501-224 430A LT40
6261 = BS1501-224 430A LT50
6262 = BS1501-224 430B RT
6263 = BS1501-224 430B LT0
6264 = BS1501-224 430B LT20
6265 = BS1501-224 430B LT30
6266 = BS1501-224 430B LT40
6267 = BS1501-224 430B LT50
6268 = BS1501-224 460A RT
6269 = BS1501-224 460A LT0
597
________________
Reference Data Manager Reference Guide April 2002
598
________________ Appendix B: General Comments
6332 = BS1501-316S37A
6333 = BS1501-316S49A
6334 = BS1501-320S17A
6335 = BS1501-310S24A
6336 = BS1501-NA15A
6337 = BS1501-NA16A
6338 = BS1501-460S52A
6339 = BS1501-304S62A
6340 = BS1501-304S65A
6341 = BS1501-304S87A
6342 = BS1501-347S67A
6343 = BS1501-316S62A
6344 = BS1501-316S66A
6345 = BS1501-316S82A
6351 = BS1501-403S17B
6352 = BS1501-405S17B
B. Codelists
6353 = BS1501-304S12B
6354 = BS1501-304S15B
6355 = BS1501-304S49B
6356 = BS1501-351S12B
6357 = BS1501-351S49B
6358 = BS1501-347S17B
6359 = BS1501-347S49B
6360 = BS1501-316S12B
6361 = BS1501-316S16B
6362 = BS1501-316S37B
6363 = BS1501-316S49B
6364 = BS1501-320S17B
6365 = BS1501-310S24B
6366 = BS1501-NA15B
6367 = BS1501-NA16B
6368 = BS1501-460S52B
6369 = BS1501-304S62B
6370 = BS1501-304S65B
6371 = BS1501-304S87B
6372 = BS1501-377S67B
6373 = BS1501-316S62B
6374 = BS1501-316S66B
6375 = BS1501-316S82B
6376 = BS1501-460S52A LT70
599
________________
Reference Data Manager Reference Guide April 2002
600
________________ Appendix B: General Comments
B. Codelists
6472 = BS1503 316S31E
6473 = BS1503 316S33E
6474 = BS1503 316S51E
601
________________
Reference Data Manager Reference Guide April 2002
602
________________ Appendix B: General Comments
6589 = BS1506-410S21-720
6590 = BS1506-410S21-760
6591 = BS1506-410S21-750
6592 = BS1506-410S21-770
6593 = BS1506-416S29
6594 = BS1506-286S31
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
B. Codelists
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
32 = [CAC5C2] [2C0032] CL300 RFFE, CS, Trim 8
33 = [CAC5C4] [4C0033] CL600 RFFE, CS, Trim 8
35 = [CAC5G1] [1C0035] CL150 RFFE, CS, Trim 8
603
________________
Reference Data Manager Reference Guide April 2002
604
________________ Appendix B: General Comments
B. Codelists
1678 = [LPH7B2] [2L1678] CL300 RFFE-SF, 1.25Cr-0.5Mo, Trim 8
1679 = [LPH7B4] [4L1679] CL600 RFFE-SF, 1.25Cr-0.5Mo, Trim 8
1691 = [LPH9B4] [4L1691] CL600 RFFE-SF, 1.25Cr-0.5Mo, Trim 8
1864 = [LPU5B6] [6L1864] CL1500 BE/RJFE, 1.25Cr-0.5Mo, Trim 8
1868 = [LPU5P5] [5L1868] CL900 BE/RFFE, 1.25Cr-0.5Mo, Trim 5, (ASME-I)
1869 = [LPU5P6] [6L1869] CL1500 BE/RJFE, 1.25Cr-0.5Mo, Trim 5, (ASME-I)
1874 = [LPU5Q5] [5L1874] CL900 BE/RFFE, 1.25Cr-0.5Mo, Trim 5, (ANSI-B31.1)
1875 = [LPU5Q6] [6L1875] CL1500 BE/RJFE, 1.25Cr-0.5Mo, Trim 5, (ANSI-B31.1
1882 = [LPU5R6] [6L1882] CL1500 BE/RJFE, 1.25Cr-0.5Mo, Trim 5, (ANSI-B31.3
1885 = [LPU7B6] [6L1885] CL1500 BE/RJFE, 1.25Cr-0.5Mo, Trim 8
3013 = [LTC5B1] [1L3013] CL150 RFFE, 5Cr-0.5Mo, Trim 8
3014 = [LTC5B2] [2L3014] CL300 RFFE, 5Cr-0.5Mo, Trim 8
3027 = [LTC7B1] [1L3027] CL150 RFFE, 5Cr-0.5Mo, Trim 8
3028 = [LTC7B2] [2L3028] CL300 RFFE, 5Cr-0.5Mo, Trim 8
3029 = [LTC7B4] [4L3029] CL600 RFFE, 5Cr-0.5Mo, Trim 8
3040 = [LTC8B1] [1L3040] CL150 RFFE, 5Cr-0.5Mo, Trim 8
3041 = [LTC8B2] [2L3041] CL300 RFFE, 5Cr-0.5Mo, Trim 8
3042 = [LTC8B4] [4L3042] CL600 RFFE, 5Cr-0.5Mo, Trim 8
3048 = [LTC9B1] [1L3048] CL150 RFFE, 5Cr-0.5Mo, Trim 8
3049 = [LTC9B2] [2L3049] CL300 RFFE, 5Cr-0.5Mo, Trim 8
3193 = [LTH7B5] [5L3193] CL900 RFFE-SF, 5Cr-0.5Mo, Trim 8
3203 = [LTH9B2] [2L3203] CL300 RFFE-SF, 5Cr-0.5Mo, NACE, Trim 8
3204 = [LTH9B4] [4L3204] CL600 RFFE-SF, 5Cr-0.5Mo, NACE, Trim 8
3390 = [LTU7B6] [6L3390] CL1500 BE/RJFE, 5Cr-0.5Mo, Trim 8
3725 = [LVC7B1] [1L3725] CL150 RFFE, 9Cr-1Mo, Trim 8
3726 = [LVC7B2] [2L3726] CL300 RFFE, 9Cr-1Mo, Trim 8
3746 = [LVC9B1] [1L3746] CL150 RFFE, 9Cr-1Mo, Trim 8
3747 = [LVC9B2] [2L3747] CL300 RFFE, 9Cr-1Mo, Trim 8
3748 = [LVC9B4] [4L3748] CL600 RFFE, 9Cr-1Mo, Trim 8
3749 = [LVC9B5] [5L3749] CL900 RFFE, 9Cr-1Mo, 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
605
________________
Reference Data Manager Reference Guide April 2002
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
o The name of a Piping Materials Class is then determined from the conventi
FAXXX, where:
F.......pressure rating
A.......material group
XXX.....sequence number from list in 2090-41-SN
606
________________ Appendix B: General Comments
Irons, F
A= Gray iron
D= Ductile iron
G= Ferritic ductile iron
J= Austenitic ductile iron
Z= Other 1
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
B. Codelists
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
607
________________
Reference Data Manager Reference Guide April 2002
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
608
________________ Appendix B: General Comments
W= Zirconium
X= Other 1
Y= Other 2
Z= Other 3
B. Codelists
K= RFSF, Monel trim
L= RFSF, other
M= RTJ, std trim
N= RTJ, SS trim
0= RTJ, Monel trim
P= RTJ, other
Q= MJ, std trim
R= MJ, SS trim
S= MJ, Monel trim
T= MJ, other
U= BE, std trim
V= BE, SS trim
W= BE, Monel trim
X= BE, other
Y= Other 1
Z= Other 2
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
609
________________
Reference Data Manager Reference Guide April 2002
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
610
________________ Appendix B: General Comments
B. Codelists
25 = By Others
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
611
________________
Reference Data Manager Reference Guide April 2002
19 = PS8.01
20 = PS9.01
21 = PS10.01
22 = PS10.02
23 = PS11.01
24 = PS12.01
25 = PS13.01
26 = PS14.01
27 = PS16.01
28 = PS18.01
40 = Varies
1 = [Blank]
2 = NT [Not heat traced]
3 = HT [Heat traced]
4 = PHT [Partially heat traced]
612
________________ Appendix B: General Comments
B. Codelists
21 = S [Sound attenuation insulated]
22 = SV [Sound attenuation insulation with vapor barrier]
30 = R11 [Refractory lined, insulation]
32 = R15 [Refractory lined, insulation/erosion]
34 = R18 [Refractory lined, erosion]
40 = Varies
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]
613
________________
Reference Data Manager Reference Guide April 2002
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]
126 = RFTBEWG [Raised-face thru-bolted end with integral gasket]
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]
614
________________ Appendix B: General Comments
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
B. Codelists
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]
615
________________
Reference Data Manager Reference Guide April 2002
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
616
________________
Appendix B: General Comments
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
B. Codelists
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
617
________________
Reference Data Manager Reference Guide April 2002
0 = None
1 = reconstruct
2 = re-calculate
618
________________ Appendix B: General Comments
18 = Gate valve
19 = Extended body gate valve
20 = Conduit gate valve
21 = Blank gate valve
22 = 3-way valve
23 = Ball valve [2-way]
24 = 2-way valve
25 = 3-way ball valve
28 = Globe valve [2-way]
29 = Angle globe valve [2-way]
30 = 3-way globe valve
31 = Y globe valve
B. Codelists
33 = Plug valve [2-way]
34 = 4-way valve
35 = 3-way plug valve
36 = 4-way plug valve
39 = Needle valve
43 = Butterfly valve
47 = Diaphragm valve
49 = Knife gate valve
50 = Slide valve [2-way]
51 = 3-way slide valve
54 = Angle valve
55 = Check valve
56 = Wafer check valve
57 = Angle check valve
58 = Stop check valve
59 = Angle stop check valve
60 = Y stop check valve
67 = Backflow preventer
68 = Automatic recirculation valve
70 = Angle blowdown valve
71 = Y blowdown valve
73 = Pinch valve
74 = Float valve
75 = Foot valve
79 = Tank drain valve
86 = Deluge valve
89 = Hose valve
90 = Angle hose valve
93 = Vent/drain valve
97 = Instrument root valve
98 = 3-way instrument root valve
99 = 4-way instrument root 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
131 = Open spacer
132 = End
133 = Head
619
________________
Reference Data Manager Reference Guide April 2002
135 = Plug
137 = Cap
138 = Diameter change
139 = Concentric diameter change
140 = Eccentric diameter change
141 = Coupling/connector
142 = Half coupling
143 = Concentric reducer
144 = Eccentric reducer
148 = Reducing coupling
151 = Concentric swage
152 = Eccentric swage
155 = Union
156 = Orifice union
157 = Dielectric union
159 = Hose connection
160 = Bushing
162 = Reducing insert
163 = Pipe bend
165 = 5.625 deg elbow
167 = 11.25 deg elbow
169 = 22.5 deg elbow
171 = <45 deg direction change
172 = 45 deg direction change
173 = 45 deg elbow
175 = 45 deg LR elbow
176 = 45 deg long tangent elbow
177 = 45 deg 3D elbow
179 = 45 deg union elbow
181 = 45 deg street elbow
182 = 45 deg short elbow
184 = 45 deg long elbow
189 = 60 deg elbow
191 = 45-90 deg direction change
192 = 90 deg direction change
193 = 90 deg elbow
195 = 90 deg SR elbow
196 = 90 deg LR elbow
198 = 90 deg LR long tangent elbow
200 = 90 deg reducing elbow
202 = 90 deg 3D elbow
204 = 90 deg union elbow
206 = 90 deg street elbow
207 = 90 deg reducing street elbow
209 = 90 deg short elbow
210 = 90 deg long elbow
216 = 180 deg return
218 = 180 deg SR return
220 = 180 deg LR return
222 = 180 deg close return
223 = 180 deg medium return
224 = 180 deg open return
229 = Miter
231 = 45 deg miter
233 = 90 deg miter
237 = Tee
239 = Reducing branch tee
240 = Reducing run and branch tee
242 = On-run union tee
243 = On-branch union tee
246 = Street tee
249 = Reducing instrument tee
620
________________ Appendix B: General Comments
B. Codelists
288 = Weldolet
289 = Sockolet
290 = Thredolet
291 = Nippolet
292 = Elbolet
293 = Latrolet
294 = Endolet
295 = Reinforcing pad
297 = Reinforcing weld
299 = Buttweld
303 = Branch nipple
304 = In-line nipple
310 = Gasket
312 = Stud
313 = Nut
621
________________
Reference Data Manager Reference Guide April 2002
909 = Anchor
911 = 1-way support
913 = 2-way support
923 = Spring support
927 = Damping support
622
________________ Appendix B: General Comments
B. Codelists
1075 = FBM off-unit piping connector
1079 = To off-site piping connector
1083 = From off-site piping connector
623
________________
Reference Data Manager Reference Guide April 2002
624
________________ Appendix B: General Comments
2 = NO [Normally open]
3 = NC [Normally closed]
5 = CSO [Car seal open]
6 = CSC [Car seal closed]
10 = LO [Locked open]
B. Codelists
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]
625
________________
Reference Data Manager Reference Guide April 2002
626
________________ Appendix B: General Comments
B. Codelists
226 = RFFEWG [Raised-face flanged end w/ integral gasket]
231 = RJFE [RTJ-face flanged end]
241 = STFE [Small-tongue-face flanged end]
242 = LTFE [Large-tongue-face flanged end]
243 = SMFE [Small-male-face flanged end]
244 = LMFE [Large-male-face flanged end]
251 = SGFE [Small-groove-face flanged end]
252 = LGFE [Large-groove-face flanged end]
253 = SFFE [Small-female-face flanged end]
254 = LFFE [Large-female-face flanged end]
261 = FFLFE [Flat-face lap-flanged end]
271 = RFLFE [Raised-face lap-flanged end]
281 = RJLFE [RTJ-face lap-flanged end]
291 = STLFE [Small-tongue-face lap-flanged end]
292 = LTLFE [Large-tongue-face lap-flanged end]
293 = SMLFE [Small-male-face lap-flanged end]
294 = LMLFE [Large-male-face lap-flanged end]
301 = SGLFE [Small-groove-face lap-flanged end]
302 = LGLFE [Large-groove-face lap-flanged end]
303 = SFLFE [Small-female-face lap-flanged end]
304 = LFLFE [Large-female-face lap-flanged end]
311 = FFTBE [Flat-face thru-bolted end]
316 = FFTBEWG [Flat-face thru-bolted end w/ integral gasket]
321 = RFTBE [Raised-face thru-bolted end]
326 = RFTBEWG [Raised-face thru-bolted end w/ integral gasket]
331 = RJTBE [RTJ-face thru-bolted end]
346 = MRJTBEWG [Male RTJ-face thru-bolted end w/ integral gasket]
351 = FFTBCSE [Flat-face thru-bolted-w/-cap-screws end]
356 = FFTBCSEWG [Flat-face thru-bolted-w/-cap-screws end w/ integra
361 = RFTBCSE [Raised-face thru-bolted-w/-cap-screws end]
366 = RFTBCSEWG [Raised-face thru-bolted-w/-cap-screws end w/ integ
371 = RJTBCSE [RTJ-face thru-bolted-w/-cap-screws end]
381 = FFFTBE [Flat-full-face thru-bolted end]
386 = FFFTBEWG [Flat-full-face thru-bolted end w/ integral gasket]
391 = MJE [Mechanical joint end]
627
________________
Reference Data Manager Reference Guide April 2002
628
________________ Appendix B: General Comments
B. Codelists
752 = 1O.0"(250mm) PE [10.0" long, PE]
753 = 11.0"(275mm) PE [11.0" long, PE]
754 = 12.0"(300mm) PE [12.0" long, PE]
755 = HEX [Hexagon]
629
________________
Reference Data Manager Reference Guide April 2002
831 = CL20000
835 = CL30000
836 = SCH 40
838 = SCH 80
840 = GRAVHD
630
________________ Appendix B: General Comments
960 = AWWA-C207 Cl.B & D, ring [Steel slip-on flanges CL86, CL150, CL175]
961 = AWWA-C207 Cl.B & D, hub [Steel slip-on flanges CL86, CL150, CL175]
962 = AWWA-C207 Cl.E, hub [Steel slip-on flanges CL275]
970 = API-5LE [Polyethylene fittings]
975 = API-6A [Wellhead flanges and fittings]
979 = API-605 [API-605 flanges]
980 = MSS-SP-44-NB [MSS non-blind flanges]
981 = MSS-SP-44-B [MSS blind flanges]
B. Codelists
996 = American DI Pipe
997 = Gladding McBean [Vitrified clay S-XS pipe and fittings]
998 = Taylor Forge
999 = ITT VALVES
631
________________
Reference Data Manager Reference Guide April 2002
632
________________ Appendix B: General Comments
B. Codelists
211 = Use of this component under certain pressure/temperature
conditions may provide less than 3/16 inch CA.
214 = Use where full port is required.
220 = Install in the horizontal position only.
221 = Valve shall be in accordance with NACE MR-01-75.
222 = Use 0.75 inch diameter only at orifice flange taps.
223 = Use 0.5 inch diameter only at orifice flange taps.
224 = To be used only where specifically required. Valve sizes
16" and larger require electric motor operators.
253 = Use of unions and threaded fittings shall be limited to a
maximum temperature of 500 degF.
257 = When mating stainless steel flanges to ferritic steel
flanges, use studs corresponding to the ferritic flange.
259 = Double hub fittings are available in 90 degrees and 45
degrees elbows.
260 = Cement lined per AWWA-C205-80. Minimum lining thickness
shall be 0.3125 inch thick. Lining shall be Type II cement per
ASTM-C150 with a minimum 28-day compressive strength of
3000 psi. Lining shall be flush with ends.
276 = Remove internals of valves containing Teflon seats and/or
seals prior to welding or backwelding.
304 = For use in deluge systems.
325 = Do not use over 100 degF.
326 = Do not use over 150 degF.
328 = Do not use over 180 degF.
329 = Do not use over 200 degF.
330 = Do not use over 250 degF.
331 = Do not use over 300 degF.
332 = Do not use over 350 degF.
333 = Do not use over 400 degF.
334 = Do not use over 450 degF.
335 = Do not use over 500 degF.
336 = Do not use over 550 degF.
337 = Do not use over 600 degF.
338 = Do not use over 650 degF.
339 = Do not use over 700 degF.
340 = Do not use over 750 degF.
341 = Do not use over 800 degF.
633
________________
Reference Data Manager Reference Guide April 2002
1 = [Blank]
634
________________ Appendix B: General Comments
Actuators, 41-99
41 = Diaphragm
42 = Electro-Pneumatic
43 = Press-balanced diaphragm
45 = Regulator
49 = Single acting cylinder
B. Codelists
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
635
________________
Reference Data Manager Reference Guide April 2002
1 = [Blank]
636
________________ Appendix B: General Comments
B. Codelists
141 = API-526 [Flanged Steel Safety Relief Valves]
145 = API-590 [Steel Line Blanks ||]
146 = API-590Z1 [Steel Line Blanks - with 0.125" CA ||]
147 = API-590Z2 [Steel Line Blanks - with 0.25" CA ||]
153 = API-593 [Ductile Iron Plug Valves]
154 = API-594 [Wafer Check Valves]
155 = API-595 [Cast Iron Gate Valves]
157 = API-597 [Steel Venturi Gate Valves]
159 = API-599 [Steel Plug Valves]
160 = API-600 [Steel Gate Valves ||]
161 = API-601 [Metallic Gaskets for Raised Face Pipe Flanges and
Flanged Connections ||]
162 = API-602 [Compact Steel Gate Valves]
163 = API-603 [Class 150 Cast Flanged End Gate Valves]
164 = API-604 [Ductile Iron Gate Valves]
165 = API-605 [Large Diameter Carbon Steel Flanges ||]
166 = API-606 [Compact Carbon Steel Gate Valves]
169 = API-609 [Butterfly Valves Lug and Wafer Type]
637
________________
Reference Data Manager Reference Guide April 2002
298 = NFPA-1963 [Screw Threads and Gaskets for Fire Hose connections]
300 = ASME BPE-97
[Geometry standards that follow apply to specific manufacturers.
If one of these standards is used to define a component, the
following information will be shown in brackets to the right of the
geometry standard:
o For valves: the applicable model codes and vendors designations
o For fittings: the applicable model codes will be shown unless
the vendors designation is required to differentiate between
components requiring a different geometry standard to assign them
to the proper data table.
1000 = Adamson 1
1001 = Adams 1
1025 = Aitken 1 [BLPAD; BLSPA; TDRA; TDRB; TDRBW ||]
1026 = Aitken Z1 [BLPAD; BLSPA - with 0.125" CA ||]
1027 = Aitken Z2 [BLPAD; BLSPA - with 0.25" CA ||]
1050 = Allied Pipe Products 1
1075 = Aldo Colombo 1
1100 = Aloyco 1 [GATR-Fig_114; GATR-Fig_114DB; GATR-Fig_114EB; GATR-Fig_124;
GATR-Fig_2214A; GLOR-Fig_2310A; GLOR-Fig_2314A; GLOR-Fig_314; GLOR-Fig_31
GLOR-Fig_314EB; GLOR-Fig_504; CKLR-Fig_554; CKLR-Fig_2554A; CKSR-Fig_2374
CKSR-Fig_374; TKDR-Fig_751 ||]
1101 = Aloyco 2 [GATR-Fig_2110; GATR-Fig_2114 ||]
1125 = American Darling 1 [H3W1-Fig_B-50-B ||]
1130 = American DI Pipe [PIPE; L; LRB ||]
1150 = American Valve 1
1175 = Amri 1
1200 = Anaconda 1
1225 = Anderson Greenwood 1
1250 = Anvil 1
1275 = A.O.Smith 1
1300 = Apollo 1
1325 = Argus 1
1350 = Armstrong 1 [S51AC-Fig_K1SC; S70AC-Fig_2011; S70BC-Fig_2011 ||]
1375 = Asahi/American 1
1400 = Babbitt 1
1425 = Babcock and Wilcox 1
1450 = Badger Meters 1
1475 = Bailey Co 1
638
________________ Appendix B: General Comments
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 ||]
B. Codelists
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
2155 = Dur-O-Lock 1 [CPL ||]
2175 = Durco 1
2200 = Elkhart 1
2225 = Enpro 1
2250 = Epsco 1
2275 = Everest 1
639
________________
Reference Data Manager Reference Guide April 2002
2575 = Garlok 1
2600 = General 1
2625 = Geosource 1
2650 = Gestra 1
2660 = Gladding McBean 1 [REDC; E45; E90; M451; M452; L ||]
2675 = Graylock 1
2700 = Grinnell 1 [BALR-Fig_3022; CAPOT; UNO; E45U; E90RST; TOUB; TOUR ||]
2715 = Grinnell Fire Prot 1 [DEL-Model_A-4; SSP-Mulsifyre-Projector ||]
2725 = Grove 1
2750 = Gulf 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
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
640
________________ Appendix B: General Comments
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
B. Codelists
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
641
________________
Reference Data Manager Reference Guide April 2002
& 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;
NEE-Series_22461; NEE-Series_SW22461; CAPOT; UN; E90U; E90ST; L ||]
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
642
________________ Appendix B: General Comments
5650 = Zurn 1
General Specifications
7000 = DIN 2401-1 Pressure, nominal
7001 = DIN 2401-2 Pressure, nominal
7002 = DIN 2402 Diameter,nominal
Pipes
B. Codelists
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
7103 = DIN 2533 ;Cast iron flanges, PN 16
7104 = DIN 2534 ;Cast iron flanges, PN 25
7105 = DIN 2535 ;Cast iron flanges, PN 40
7106 = DIN 2543 ;Cast steel flanges, PN 16
7107 = DIN 2544 ;Cast steel flanges, PN 25
7108 = DIN 2545 ;Cast steel flanges, PN 40
7109 = DIN 2546 ;Cast steel flanges, PN 64
7110 = DIN 2547 ;Cast steel flanges, PN 100
7111 = DIN 2548 ;Cast steel flanges, PN 160
7112 = DIN 2549 ;Cast steel flanges, PN 250
7113 = DIN 2550 ;Cast steel flanges, PN 320
7114 = DIN 2551 ;Cast steel flanges, PN 400
7115 = DIN 2558 ;Plain face oval screwed flange PN 6
7116 = DIN 2561 ;Oval screwed flange w/ socket PN 10,16
7117 = DIN 2565 ;Screwed flange PN 6 rund
7118 = DIN 2566 ;Screwed flange PN 10,16
7119 = DIN 2567 ;Screwed flange PN 25,40
7120 = DIN 2568 ;Screwed flange PN 64
7121 = DIN 2569 ;Screwed flange PN 100
7122 = DIN 2630 ;Welding neck flange PN 1
7123 = DIN 2631 ;Welding neck flange PN 6
7124 = DIN 2632 ;Welding neck flange PN 10
7125 = DIN 2633 ;Welding neck flange PN 16
7126 = DIN 2634 ;Welding neck flange PN 25
7127 = DIN 2635 ;Welding neck flange PN 40
7128 = DIN 2636 ;Welding neck flange PN 64
643
________________
Reference Data Manager Reference Guide April 2002
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
644
________________ Appendix B: General Comments
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
B. Codelists
7410 = DIN 2848 ;Flanged lined steel fittings, T
7411 = DIN 2873 ;Flanged steel fittings enamelled, T
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
645
________________
Reference Data Manager Reference Guide April 2002
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
VALVES
646
________________ Appendix B: General Comments
12660 = BS5158
12661 = BS5158 and app A
12665 = BS5159
12666 = BS5159 and app A
12670 = BS5160
12671 = BS5160 and app A
gaskets
bolting
13200 = BS4882 metric series bolting
13210 = BS4882 inch series bolting
B. Codelists
dummy
13999 = dummy BS code
1 = [Blank]
647
________________
Reference Data Manager Reference Guide April 2002
49 =
AWWA-C110 [Iron fittings]
50 =
AWWA-C115 [Iron pipe and fittings]
55 =
AWWA-C151 [Ductile iron pipe]
60 =
AWWA-C207 Cl.B & D, ring
[Steel slip-on flanges CL86, CL150, CL175]
61 = AWWA-C207 Cl.B & D, hub
[Steel slip-on flanges CL86, CL150, CL175]
62 = AWWA-C207 Cl.E, hub
[Steel slip-on flanges CL275]
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
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
648
________________ Appendix B: General Comments
B. Codelists
RTJ-face thru-bolted with cap screws........................None
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 engageme
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
649
________________
Reference Data Manager Reference Guide April 2002
British Standards
650
________________ Appendix B: General Comments
1 = [Blank]
B. Codelists
33 = ANSI-B1.20.3 [Dryseal pipe threads]
37 = ANSI-B1.20.7 [Hose coupling screw threads]
49 =
AWWA-C110 [Iron fittings]
50 =
AWWA-C115 [Iron pipe and fittings]
55 =
AWWA-C151 [Ductile iron pipe]
60 =
AWWA-C207 Cl.B & D, ring
[Steel slip-on flanges CL86, CL150, CL175]
61 = AWWA-C207 Cl.B & D, hub
[Steel slip-on flanges CL86, CL150, CL175]
62 = AWWA-C207 Cl.E, hub
[Steel slip-on flanges CL275]
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
651
________________
Reference Data Manager Reference Guide April 2002
table are required in defining the component but the component ends
are other than male termination. The basis for this table suffix
will be as follows:
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
652
________________ Appendix B: General Comments
Female ferrule....................
Female hose.......................
B. Codelists
Gasket............................Not applicable
Bolt..............................Not applicable
Nut...............................Not applicable
User defined......................None
653
________________
Reference Data Manager Reference Guide April 2002
British Standards
1 = [Blank]
654
________________ Appendix B: General Comments
B. Codelists
147 = 17 [Acc. to DIN 3202-F17]
148 = 18 [Acc. to DIN 3202-F18]
149 = 19 [Acc. to DIN 3202-F19]
150 = - [Not existent under DIN 3202]
151 = 21 [Acc. to DIN 3202-V21]
152 = - [Not existent under DIN 3202]
153 = - [Not existent under DIN 3202]
154 = - [Not existent under DIN 3202]
155 = - [Not existent under DIN 3202]
156 = - [Not existent under DIN 3202]
157 = - [Not existent under DIN 3202]
158 = - [Not existent under DIN 3202]
159 = - [Not existent under DIN 3202]
160 = - [Not existent under DIN 3202]
161 = 31 [Acc. to DIN 3202-S31]
162 = 32 [Acc. to DIN 3202-F32/M32]
163 = 33 [Acc. to DIN 3202-F33/M33]
164 = 34 [Acc. to DIN 3202-F34]
165 = - [Not existent under DIN 3202]
166 = 36 [Acc. to DIN 3202-M36]
167 = - [Not existent under DIN 3202]
168 = - [Not existent under DIN 3202]
169 = - [Not existent under DIN 3202]
201 = [Blank]
655
________________
Reference Data Manager Reference Guide April 2002
656
________________ Appendix B: General Comments
B. Codelists
572 = Wall Thickness Equation
575 = Geometry Standard
576 = Table Suffix / End Standard - Green
577 = Table Suffix / End Standard - Red
578 = Weight Code
990 = Spec Writer Data Form Type
999 = Standard Note Title
1010 = Area Units
1028 = Weight Units
1056 = Temperature Units
1064 = Pressure Units
1074 = Density Units
1100 = Weld Type
1162 = Force Units
1201 = Drawing Scale
1202 = Drawing Size
1203 = Interference Manager Approval Status
1204 = Interference Clash Type
1205 = Interference Manager Action
1207 = Interference Manager Approval Method
1208 = Clash Checking Option
1209 = Clash Checking Volume Filter Option
1310 = Report Source
1312 = Report Type
1410 = Design Review Type
1605 = Model Status
1610 = Force Units for FrameWorks Plus
1620 = Drawing View Direction
1630 = Drawing View Composition Status
1710 = Document Type
1720 = Document Sub-Type
1900 = Isometric Drawing Type
2000 = Orthographic Drawing Type
657
________________
Reference Data Manager Reference Guide April 2002
658
________________ Appendix B: General Comments
B. Codelists
CL1100, Weld Type (100)
NOTE: Codelist numbers 0-19 have been reserved for shop welds,
numbers 20-29 have been reserved for field welds, and 30-39 have
been reserved for offshore welds. In editing this codelist set, do not
change the meaning of existing codelist values.
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
659
________________
Reference Data Manager Reference Guide April 2002
660
________________ Appendix B: General Comments
B. Codelists
3 = Design Area Mode
4 = Pre-defined Volume Mode
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
661
________________
Reference Data Manager Reference Guide April 2002
1 = Client Review
2 = Informal Review
662
________________ Appendix B: General Comments
B. Codelists
46 = Piping Specialty RDB report
47 = Piping Specialty TDB report
663
________________
Reference Data Manager Reference Guide April 2002
664
________________ Appendix B: General Comments
B. Codelists
723 = Instrument Loop Diagrams | 75
731 = Instrument Location Plans | 65
733 = Instrument Control House/Panel Drawings | 99
735 = Instrument Hook Up Drawings | 75
737 = Instrument Heat Tracing Drawings | 75
739 = Instrument Wiring Drawings | 99
771 = Instrument Index | 72
799 = Other Instrument Documents | 99
665
________________
Reference Data Manager Reference Guide April 2002
666
________________ Glossary
Glossary
absolute path name The sequence of directories, beginning with the root directory (/) that
locates a file. See also path name and relative path name.
active depth The plane in a 3-D design upon which you can place elements and perform
manipulations.
active process The process which is displayed in the Process ID field; it controls the
message fields, the menus, and the keyboard. The active process has a
highlighted window icon strip.
application software Software designed to meet specific needs, unlike system software which
runs other software.
batch processing A method of processing data which collects a series of operations into a
group (or batch) and executes the group in a continuous stream without
user intervention.
batch queue A queue, or channel for moving requests, created through NQS. A batch
Glossary
queue handles scheduling for processes submitted through the Batch
options screen menu.
branch point A point on a pipeline which separates piping segments so that they can be
assigned different segment parameters. A branch point allows for
placement of branch components.
cancel button The button located in the upper right corner of a form containing a red X or
the word cancel. Select the cancel button to exit the form or option.
confirm button A button that appears in the upper right corner of a form and contains a
green check mark or the word confirm. Select the confirm button to initiate
a specified option.
667
________________
Reference Data Manager Reference Guide April 2002
coordinate system A geometric relation used to denote the location of points in the design
cube. The most common coordinate system is the rectangular coordinate
system, whereby points are located by traversing the X, Y, and Z axes of the
design cube. Normally, coordinate systems have their origin defined as
0,0,0, though this is not required. Other coordinate systems are used to more
easily express the coordinates of specific geometric entities. For example,
you can use a spherical coordinate system to help define points on a sphere,
and you can use a cylindrical coordinate system to help define points on a
cylinder.
coordinates An ordered set of absolute or relative data values that specify a location in a
coordinate system.
core files The image files written by System V for a number of reasons, the most
common of which are memory violations, illegal instructions, bus errors,
and user-generated quit signals.
cursor The pointer that the user moves on the screen to indicate an item or area.
data button The mouse button used to place data points and tentative points, to accept
previously selected elements, and to select commands from forms and
menus.
data entry field The field on a screen used to accept user-supplied data. Also known as
key-in field.
data point A point placed by pressing the data button on the mouse. Data points select
commands from the panel menus and Menu Bar, place elements, identify
and accept elements, and activate windows and perform window
manipulations.
database table The part of the database that is made of rows and columns and contains
information about the project and design elements.
668
________________ Glossary
display-list box A small box with horizontal dashes located at the end of a form key-in field.
When selected, a list of the data available for that field is displayed. Input
can then be selected from the list with a data point instead of keying in the
information.
dragging Another term for the dynamic function that attaches the cursor to an element
so you can see it move.
easting A term used in plane surveying that describes an east, or positive, difference
in longitude.
entity An object (project, drawing, element, and so forth.) of interest about which
information is stored; a relational database table.
file specification A UNIX path name that tells the system where to locate a file.
filename A user-defined name given to an interactively created file. The name should
Glossary
be relevant to the contents of the file.
form An interface or screen menu designed with the I/FORMS product. Because
many of the screen menus in the application software are built with
I/FORMS, you must have the FORMS_S product on your workstation.
full path name The name of the entire path or directory hierarchy to a file, including the file
name. See also relative path name.
header The first items of information in a file which precede any actual data. The
header contains information on the structure and contents of the file.
669
________________
Reference Data Manager Reference Guide April 2002
invert elevation The lowest point on the internal diameter of the pipe.
key-in field The field on a screen used to accept user-supplied data. Also known as a
data entry field.
menubar The strip at the top of the screen that contains icons for selecting
commands.
message area The area that appears in the MicroStation Command Window when you are
working in a design file. It is divided into the Command Status field, the
Current Command field, the Prompt field, and the Key-in field.
NFS Network File System, the system that provides access to data that is
distributed among machines through an interconnection of host computers
and workstations. NFS allows you to mount a remote resource to your local
workstation so you can access the data as though it were local. NFS is
usually used to access centralized data on a server.
node address The hard-wired Ethernet address assigned to each node when it is
manufactured. It is necessary for each node to identify and communicate
with another node in the network.
node name A name, or alias, that can be assigned to the node address of a device on a
network.
northing A term used to describe a north coordinate location in the plant coordinate
system.
670
________________ Glossary
nozzle A special equipment modeling primitive that contains the connection point
to piping. This point does NOT include a gasket allowance, but rather
represents the face-of-flange coordinate.
NQS Network Queuing System, the software package that allows you to define
network-wide batch and device queues. Use of NQS involves setting up
local resource queues on the system(s) where the resources reside and
setting up pipe queues on the systems that are to have access to the
resources.
origin In coordinate geometry, the point where the x, y, and z-axes intersect.
orthogonal view A view which is a projection of the model onto a plane along lines which
are orthogonal to the plane.
Glossary
a command.
path name The sequence of directories leading to a file. See also absolute path name
and relative path name.
pipe queue A controlled channel for moving requests to batch or device queues on
remote systems and for receiving status and/or data in response.
place data point To identify a specific element, or indicate a specific point in the design file.
plane A spatial element in geometry that may or may not have a boundary, but is
level, having no elevations or depressions, and is three-dimensional.
relative path name The sequence of directories leading from the current directory to a particular
file. See also path name and absolute path name.
671
________________
Reference Data Manager Reference Guide April 2002
row A unit of related information in a table. One collection of column values for
a table.
rubberbanding The animation dynamic that enables you to specify the position of a data
point while the element changes as you move the cursor.
schema file A file that outlines the overall logical structure of a rule base or a database.
server In network operations, the node which maintains common data or performs
a common task needed by clients. All network operations (database, NFS,
NQS) between two or more nodes establish a client/server relationship.
Structured Query Language developed by IBM for creating, modifying, and querying
Language SQL relational databases.
symbology The display style of an element, including color, style, and weight.
table A collection of data for quick reference, either stored in sequential locations
in memory or printed as an array of rows and columns of data items of the
same type.
values Data, either entered by the user or determined by the software, that are
stored in an attribute.
view The defined area of vision on a screen. A view allows you to see a
prescribed volume of the design cube. Views are created with their own x,
y, and z axes. The x,y plane of the view is parallel to the screen, while the
z-axis can be thought of as coming straight out of the view towards you.
The view axes maintain this relationship regardless of the rotation with
respect to the design cube. See also active depth.
virtual memory External memory for a computer that can be used as if it were an extension
of the computers internal memory. The software uses virtual memory to
store data. This means that unneeded files and data, stay on the disk until
they are called for. Because the internal processing memory stores a
minimal amount of data, the software can perform processing more quickly.
672
________________ Glossary
working directory The directory from which you are accessing files.
Glossary
673
________________
Reference Data Manager Reference Guide April 2002
674
________________ Index
Index
A bolts 272
abbreviations 314 branch
accessory/item type 634 insertion tables 208
action 625 reinforcement equations 203
actuator type 634
alphanumeric C
labels 466 clash
approval status 573 management
HVAC 573 labels 468
structural 573 clash approval action 660
area units 657 clash approval method 661
assembly clash checking
data management volume filter option 661
create/batch 529 clash checking option 661
create/interactive 528 clash type 660
delete 532 cleaning requirements 613
extract 535 coating requirements 611
list 534 code lists
report 533 sets 449
revise 530 codelist
1010 657
B 1028 658
basic 1056 658
tables 215 1064 658
bend deflection table 219 1074 659
bolt commodity code 230 1100 659
commodity item name 216 1162 659
component mirror 233 1201 659
Index
field fit length 232, 234 1202 660
gasket diameter table 231 1203 660
pipe length threshold table 222 1204 660
preferred bolt length table 223 1205 660
segment pipe run length threshold table 221 1207 661
weld clearance 228 1208 661
weld graphics dimensions 229 1209 661
weld type 226 125 574
batch 1310 661
processes 40 1312 661
bend deflection table 219 1410 662
bends and branches 271 148 603
bolt 160 611
commodity code table 230 1605 662
bolted 1610 662
connections 326, 328 1620 662
ends 324 1630 662
1710 662
675
________________
Reference Data Manager Reference Guide April 2002
676
________________ Index
delete example
graphic commodity data 283 physical data look-up 268
label data 487 extract
physical commodity data 296 assembly data 535
piping assembly data 532 graphic commodity data 286
PJS table 247 physical commodity data 300
spec data 151 PJS tables 251
standard note data 461 standard note type 462
tutorial definition file 446 tutorial definition file 447
delivered reference data 31
density units 659 F
design review type 662 fabrication category 611
design standard 635 female ends 332
dimension data field
example of data look-up 268 fit length table 232, 234
directions fire and safety components 316
drawing view 662 fittings 316
discrimination flange
data file 155, 390 insulation exclusion data 98
displayable attribute flanges 272
labels 466 fluid code 574
message 466 force units 659, 662
document forms
organization 16 conventions 37
purpose 15 piping commodity data 656
document source 662
document type 663, 666 G
drawing scale 659 gadgets
drawing size 660 conventions 37
drawing type gaskets 272
isometric 665 diameter table 231
drawing view separation table 212
Index
composition status 662 generic tables 319
directions 662 bolted ends 324
female ends 332
E male ends 330
empty weight studs in bolted connections 326
GCP and RCP data 352 w/ term type 328
GCP data 348 variables 320
valves 350 weight and thickness data, male ends 333
overflow data 351 geometry standard 636
end prep 613 graphic
end standard commodity
green 647 data 27
red 650 library 254
equation manager 275
wall thickness 636 parametric shape definitions 263
equipment and piping codelist names 656 physical data definitions 259
equipment divisions/form code 574 sub-symbol processor 258
error symbol processors 256
messages 565 data
677
________________
Reference Data Manager Reference Guide April 2002
678
________________ Index
Index
piping definitions 259
commodity 67 library
materials class 62 manager 287
specialty 77 management
size-dependent data 88 create 291
tap properties 85 create/batch 292
materials data table 200 delete 296
materials grade 578 extract 300
model status 662 list 299
MTO report 297
tables and functions 237 revise 294
MTO flag 618 tables 266
data look-up 268
N data retrieval 267
naming conventions pipe 273
tables 303 length
neutral files threshold table 222
location 53 piping
spec data 59 assembly
679
________________
Reference Data Manager Reference Guide April 2002
680
________________ Index
Index
label data 489 sample
labels 468 piping assembly language file 521
material description library 383 table checker output 422
output 155, 390 schedule/thickness override 616
physical commodity data 297 segment
PJS tables 248 pipe run length threshold table 221
proposed RDB changes 555 short material description library 367
records 155, 390 size-dependent material data 88
reference data conflict 540 source files
reference data impact 551 location 53
spec data 152 spec 55
standard note library contents 459 spec tables
table change 546 library 239
tutorial definition file 444 spec writer 103
report data special tables and functions
discrimination data file 155, 390 piping job specification 190
files and records 155, 390 specialty
format file 155, 390 material description library 374
report output 155, 390 piping components 317
681
________________
Reference Data Manager Reference Guide April 2002
682
________________
Index
units (continued)
temperature 658
units of measure 569
V
valves 315
variables
generic tables 320
specific tables 336
verify
RDB library 561
tables 385
W
wall thickness
equations 203
wall thickness equation 636
weight and thickness data
male ends 333
weight code 654
weld
clearance table 228
graphics dimensions 229
type table 226
weld type 659
Index
683
________________
Reference Data Manager Reference Guide April 2002
684
Reference Data Manager
(PD_Data)
Reference Guide Addendum
February 2003
DPDS3-PB-200034B
For PDS version 07.02.00.**
Table of Contents
Branch Insertion Tables (replaces 6.1.6) ................................................................. 687
CL1204, Interference Clash Types .......................................................................... 691
686
Branch Insertion Tables (replaces 6.1.6)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Reference Data Manager Reference Guide (pp 208-
211 in the PDS 7.1 version of the document).
The following information has been modified:
Removed tee with reducing inserts, tee with reducing bushing,
and reducing tee with reducer(s) from list of tee branch
connections
See the following text for details.
A branch insertion table defines the selection criteria for tee and lateral branches. You
must specify the type of wye or cross to be placed in the model and specify the
reinforcement data.
Branch tables define the reinforcement to be used at tee and lateral branches in the piping
system as a function of the acute angle of intersection and the nominal diameters for the
intersecting lines. These tables do not include the reinforcement required at Ys and
crosses.
For them, the required reinforcement must be specified in Piping Design. The types of tee
branch connections include branch weld, coupling, threadolet, reducing tee, nipolet,
branch weld with reinforcing pad, sockolet, tee, and weldolet.
The system accesses the branch table when placing a component at an intersection when
no reinforcement component has been specifically defined.
The system uses the information in this table and the header nominal diameter (first size)
and branch nominal diameter (second size) to provide the item name of the component to
be used at the intersection. Neither interpolation nor extrapolation is allowed.
Neutral File Format
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
687
Reference Data Manager Reference Guide Addendum February 2003
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
! Header Branch AABBCC Codes
0.75 0.75 6Q3C22 - -
1 0.75 6Q3C24 - -
1 1 6Q3C22 - -
1.5 0.75 6Q3C24 - -
1.5 1 6Q3C24 - -
1.5 1.5 6Q3C22 - -
2 0.75 6Q3C74 - -
2 1 6Q3C74 - -
2 1.5 6Q3C74 - -
2 2 6Q3C22 - -
3 0.75 6Q3C74 - -
3 1 6Q3C74 - -
3 1.5 6Q3C74 - -
> 3 2 6Q3C73 - -
3 3 6Q3C22 - -
4 0.75 6Q3C74 - -
4 1 6Q3C74 - -
4 1.5 6Q3C74 - -
> 4 2 6Q3C73 - -
> 4 3 6Q3C73 - -
4 4 6Q3C22 - -
6 0.75 6Q3C74 - -
6 1 6Q3C74 - -
6 1.5 6Q3C74 - -
> 6 2 6Q3C73 - -
> 6 3 6Q3C73 - -
> 6 4 6Q3C73 - -
6 6 6Q3C22 - -
8 0.75 6Q3C74 - -
8 1 6Q3C74 - -
8 1.5 6Q3C74 - -
> 8 2 6Q3C73 - -
> 8 3 6Q3C73 - -
> 8 4 6Q3C73 - -
> 8 6 6Q3C73 - -
8 8 6Q3C22 - -
10 0.75 6Q3C74 - -
10 1 6Q3C74 - -
10 1.5 6Q3C74 - -
> 10 2 6Q3C73 - -
> 10 3 6Q3C73 - -
> 10 4 6Q3C73 - -
10 6 6Q3C82 - -
10 8 6Q3C82 - -
10 10 6Q3C22 - -
12 0.75 6Q3C74 - -
12 1 6Q3C74 - -
12 1.5 6Q3C74 - -
688
> 12 2 6Q3C73 - -
> 12 3 6Q3C73 - -
> 12 4 6Q3C73 - -
12 6 6Q3C82 - -
12 8 6Q3C82 - -
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:
689
Reference Data Manager Reference Guide Addendum February 2003
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 fields 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.)
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.
690
CL1204, Interference Clash Types
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Reference Data Manager Reference Guide (p. 660 in
the PDS 7.1 version of the document).
The following information has been added:
New clash types
691
Reference Data Manager Reference Guide Addendum February 2003
692
2104 = ' SoftAccess vs CT' ;
2106 = ' SoftAccess vs Insul' ;
2120 = ' SoftAccess vs SoftMain' ;
2121 = ' SoftAccess vs SoftAccess' ;
2122 = ' SoftAccess vs SoftSafety' ;
2123 = ' SoftAccess vs SoftOperat' ;
2202 = ' SoftSafety vs Soft' ;
2204 = ' SoftSafety vs CT' ;
2206 = ' SoftSafety vs Insul' ;
2220 = ' SoftSafety vs SoftMain' ;
2221 = ' SoftSafety vs SoftAccess' ;
2222 = ' SoftSafety vs SoftSafety' ;
2223 = ' SoftSafety vs SoftOperat' ;
2302 = ' SoftOperat vs Soft' ;
2304 = ' SoftOperat vs CT' ;
2306 = ' SoftOperat vs Insul' ;
2320 = ' SoftOperat vs SoftMain' ;
2321 = ' SoftOperat vs SoftAccess' ;
2322 = ' SoftOperat vs SoftSafety' ;
2323 = ' SoftOperat vs SoftOperat' ;
693
Reference Data Manager Reference Guide Addendum February 2003
Index
branch codelist
insertion tables, 687 1204, 691
694