Sunteți pe pagina 1din 569

Plant Design System (PDS)

Reference Data Manager (PD_Data)

Version 2010 (V11) November 2009 DPDS3-PB-200034G


Copyright
Copyright 1984-2009 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
U.S. Government Restricted Rights Legend
Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at
private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the
Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors,
and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"):
This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS
227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Street address: 170 Graphics Drive, Madison, AL 35758
Terms of Use
Use of this software product is subject to the End User License Agreement and Limited Product Warranty ("EULA") delivered with this
software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid
signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this
software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to
print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software
product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.
Warranties and Liabilities
All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or
applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document or its
contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this
publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable technical
product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this
license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its
affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE
USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should
verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools, ISOGEN,
MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph
Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft
Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. MicroStation is
a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product names are trademarks of their respective owners.
Contents
Preface PDS ................................................................................................................................................ ix
What's New in Reference Data Manager (PD_Data) ............................................................................. x

Introduction ................................................................................................................................................ 1
Project Organization............................................................................................................................... 1
Reference Data Overview ...................................................................................................................... 2
Piping Job Specification Introduction ............................................................................................. 4
Graphic Commodity Data Introduction ........................................................................................... 4
Material Description Data Introduction ........................................................................................... 4
Standard Note Library Introduction................................................................................................. 5
Label Description Library Introduction ........................................................................................... 5
Piping Assembly Library Introduction ............................................................................................ 6
Reference Database Introduction ........................................................................................................... 6
Delivered Reference Data ...................................................................................................................... 6
Reference Data Setup ............................................................................................................................. 7

PDS Environment ....................................................................................................................................... 9


PD Shell ................................................................................................................................................. 9
PD_Shell Form Conventions ......................................................................................................... 12
Common Tools on the PD_Shell Forms ........................................................................................ 12
Batch Processes ............................................................................................................................. 16
Help ...................................................................................................................................................... 16

Reference Data Manager ......................................................................................................................... 19


Data Security ........................................................................................................................................ 20
Reference Data Archival ...................................................................................................................... 22

Reference Data Location .......................................................................................................................... 23


Default Project Control Data ................................................................................................................ 23
Reference Database Management Data................................................................................................ 24

Piping Job Specification ........................................................................................................................... 29


Material Reference Database Structure ................................................................................................ 29
Neutral File Input ................................................................................................................................. 31
Piping Materials Class Data (201) ................................................................................................. 34
Piping Commodity Specification Data (202) ................................................................................ 38
Piping Specialty Specification Data (203) ..................................................................................... 45
Instrument Component Specification Data (204) .......................................................................... 48
Tap Properties Data (205).............................................................................................................. 51
Piping Commodity Size-Dependent Material Data (211).............................................................. 54
Piping Commodity Implied Material Data (212) ........................................................................... 56

Plant Design System (PDS) Reference Data Manager (PD_Data) i


Contents

Component Insulation Exclusion Data (231) ................................................................................ 59


Flange Insulation Exclusion Data (232) ........................................................................................ 61
Piping Construction Tolerance Exclusion Data (233) ................................................................... 63
Spec Writer .......................................................................................................................................... 65
Features.......................................................................................................................................... 66
RDB Options File .......................................................................................................................... 66
Piping Materials Class Data Command ......................................................................................... 75
Piping Commodity Data Command............................................................................................... 79
Piping Specialty Data Command ................................................................................................... 89
Instrument Data Command ............................................................................................................ 92
Tap Properties Data Command ...................................................................................................... 95
Commodity Implied Data Command............................................................................................. 98
Table Checker .............................................................................................................................. 101
Piping Job Specification Manager...................................................................................................... 101
Load, Replace, or Replace Commodity Subset Options .............................................................. 104
Delete Option ............................................................................................................................... 106
Report Option .............................................................................................................................. 107
Piping Job Spec Report Manager ....................................................................................................... 109
Using the Report Commands ....................................................................................................... 110
Report Format Form .................................................................................................................... 111
Report Discrimination Data Form ............................................................................................... 114
Report Form................................................................................................................................. 120
Report Management Defaults Form ............................................................................................ 128

Piping Job Specification Tables ............................................................................................................. 131


PJS Tables and Functions................................................................................................................... 131
Temperature and Pressure Service Limits Table ......................................................................... 132
Nominal Piping Diameters Table ................................................................................................ 134
Thickness Data Tables ................................................................................................................. 136
Materials Data Table ................................................................................................................... 139
Wall Thickness and Branch Reinforcement Equations ............................................................... 141
Branch Insertion Tables ............................................................................................................... 145
Gasket Separation Table .............................................................................................................. 150
Fluid Code Table ......................................................................................................................... 152
RDB Tables ........................................................................................................................................ 153
Commodity Item Name Table (G02) ........................................................................................... 154
Bend Deflection Table (G04) ...................................................................................................... 156
Segment Pipe Run Length Threshold Table (G06) ..................................................................... 157
Pipe Length Threshold Table (G07) ............................................................................................ 158
Preferred Bolt Length Table (G11).............................................................................................. 159
Weld Type Table ......................................................................................................................... 163
Bolt Commodity Code Table ....................................................................................................... 166
Weld Clearance Table ................................................................................................................. 167
Weld Graphics Dimensions Table ............................................................................................... 168
Gasket Diameter Table ................................................................................................................ 169
Field Fit Length Table ................................................................................................................. 169
Component Mirror Table ............................................................................................................. 170
Operator Mirror Table ................................................................................................................. 170

ii Plant Design System (PDS) Reference Data Manager (PD_Data)


Contents

Default End Preparation Table .................................................................................................... 171


MTO Tables and Functions ......................................................................................................... 172
Piping Job Specification Tables Command ....................................................................................... 172
Create Library .............................................................................................................................. 174
Compress Library ........................................................................................................................ 174
Unapproved ==> Approved ......................................................................................................... 174
Create/Interactive Spec Tables .................................................................................................... 174
Create/Batch Spec Tables ............................................................................................................ 175
Revise Spec Tables ...................................................................................................................... 176
Delete Spec Tables ...................................................................................................................... 177
Report on Spec Tables ................................................................................................................. 178
List Spec Tables........................................................................................................................... 180
Extract Spec Tables ..................................................................................................................... 180

Graphic Commodity Data ...................................................................................................................... 183


Graphic Commodity Library .............................................................................................................. 184
Symbol Processors ....................................................................................................................... 186
Sub-Symbol Processor ................................................................................................................. 187
Physical Data Definitions ............................................................................................................ 188
Parametric Shape Definitions ...................................................................................................... 192
Physical Data Tables .......................................................................................................................... 194
Data Retrieval from the Physical Data Library ........................................................................... 195
Example of Physical Data Look-Up ............................................................................................ 196
Notes for Graphic Commodity Data .................................................................................................. 197
Connect Point Data ...................................................................................................................... 197
Bends and Branches..................................................................................................................... 198
Bolts, Gaskets, and Flanges ......................................................................................................... 199
Pipe, Tubing, and Hose................................................................................................................ 199
Graphic Commodity Library Manager ............................................................................................... 200
Create Library .............................................................................................................................. 201
Compress ..................................................................................................................................... 201
Unapproved ==> Approved ......................................................................................................... 201
Create/Interactive Graphic Commodity Data .............................................................................. 201
Create/Batch Graphic Commodity Data ...................................................................................... 202
Revise Graphic Commodity Data ................................................................................................ 203
Delete Graphic Commodity Data ................................................................................................ 204
Report Graphic Commodity Data ................................................................................................ 205
List Graphic Commodity Data..................................................................................................... 206
Extract Graphic Commodity Data ............................................................................................... 207
Graphic Commodity Modules List .............................................................................................. 208
Physical Data Library Manager.......................................................................................................... 209
Create Library .............................................................................................................................. 211
Compress ..................................................................................................................................... 211
Unapproved to Approved ............................................................................................................ 211
Create/Interactive Physical Commodity Data ............................................................................. 211
Create/Batch Physical Commodity Data ..................................................................................... 212
Revise Physical Commodity Data ............................................................................................... 213
Delete Physical Commodity Data ................................................................................................ 214

Plant Design System (PDS) Reference Data Manager (PD_Data) iii


Contents

Report Physical Commodity Data ............................................................................................... 215


List Physical Commodity Data .................................................................................................... 217
Extract Physical Commodity Data............................................................................................... 217

Table Formats and Naming Conventions ............................................................................................. 219


Table Conventions ............................................................................................................................. 219
Abbreviations............................................................................................................................... 228
Table Requirements ........................................................................................................................... 229
Tables Required for Piping Components ..................................................................................... 229
Tables Required for Instrument Components .............................................................................. 232
Generic Tables ................................................................................................................................... 233
Variables for Generic Tables ....................................................................................................... 234
Generic Table for Bolted Ends (G10) .......................................................................................... 237
Generic Table for Studs used in Bolted Connections (G12) ....................................................... 239
Generic Table for Studs in Bolted Connections w/ Term Type (G12T)...................................... 241
Generic Table for Male Ends (G20) ............................................................................................ 243
Generic Table for Female Ends (G30)......................................................................................... 244
Generic Table for Weight and Thickness Data, Male Ends (G50) .............................................. 245
Piping Component Tables .................................................................................................................. 247
Variables for Specific Tables....................................................................................................... 249
Piping Component Table for GCP Data (P11A, P15A) .............................................................. 253
Piping Component Table GCP Overflow Data (P11B, P15B) .................................................... 254
Piping Component Table Green and Red CP Data (P21A, P25A, P26A, P27A,
P28A, P29A) ................................................................................................................................ 255
Piping Component Table Green and Red CP Overflow Data
(P21B,P25B,P26B,P27B,P28B) .................................................................................................. 257
Piping Component Table for Operators and Actuators (P31A) ................................................... 258
Piping Component Table for Operators and Actuators, Overflow Data (P31B) ......................... 260
Piping Component Table for Empty Weight based on GCP Data (P51,P52,P59) ...................... 261
Piping Component Table For Empty Weight of Valves (P60A) ................................................. 263
Piping Component Table For Empty Weight of Valves, Overflow Data (P60B) ....................... 264
Piping Component Table for Empty Weight based on GCP and RCP Data
(P61,P62,P63,P64,P65) ............................................................................................................... 265
Piping Component Tables for Specialty Components ................................................................. 267
Instrument Component Tables ........................................................................................................... 267
Instrument Body (I80 and P80) ................................................................................................... 267
Instrument Operator (I81 and P81) .............................................................................................. 269

Material Description Data ..................................................................................................................... 273


Material Data in the Material Reference Database ............................................................................ 277
Short Material Description Library .................................................................................................... 277
Long Material Description Library .................................................................................................... 283
Specialty Material Description Library .............................................................................................. 286
Material Description Library Manager .............................................................................................. 287
Create Library .............................................................................................................................. 289
Unapproved ==> Approved ......................................................................................................... 289
Load/Revise Interactive ............................................................................................................... 289

iv Plant Design System (PDS) Reference Data Manager (PD_Data)


Contents

Load/Revise Batch ....................................................................................................................... 290


Replace Interactive ...................................................................................................................... 291
Replace Batch .............................................................................................................................. 291
Report Option .............................................................................................................................. 292

Table Checker ......................................................................................................................................... 295


Table Checker Form ........................................................................................................................... 298
Using the Report Commands ....................................................................................................... 299
Report Format Form .................................................................................................................... 300
Discrimination Data Form ........................................................................................................... 303
Report Form................................................................................................................................. 308
Report Management Defaults Form ............................................................................................ 316
Sample Table Checker Output ........................................................................................................... 317

Pipe Support Tutorial Definition Manager .......................................................................................... 327


Support Tutorial Definition Manager ................................................................................................. 327
Create Library .............................................................................................................................. 328
Compress ..................................................................................................................................... 328
Unapproved ==> Approved ......................................................................................................... 329
Create Data .................................................................................................................................. 329
Revise Data .................................................................................................................................. 329
Delete Data .................................................................................................................................. 331
Report Data .................................................................................................................................. 332
List Data ...................................................................................................................................... 333
Extract Data ................................................................................................................................. 333
Library List .................................................................................................................................. 334

Standard Note Library ........................................................................................................................... 335


Standard Note Library Manager ......................................................................................................... 338
Create Library .................................................................................................................................... 340
Compress ............................................................................................................................................ 340
Unapproved ==> Approved ............................................................................................................... 340
Create Standard Note Type ................................................................................................................ 340
Revise Standard Note Type ................................................................................................................ 341
Report Standard Note Library Contents ............................................................................................. 342
List Standard Note Data ..................................................................................................................... 343
Delete Standard Note Data ................................................................................................................. 343
Extract Standard Note Type ............................................................................................................... 344
Load Database .................................................................................................................................... 345
Standard Note Types List ................................................................................................................... 346

Label Description Library ..................................................................................................................... 347


Label Types ........................................................................................................................................ 348
Displayable Attribute Labels ....................................................................................................... 348
Alphanumeric Labels ................................................................................................................... 348
Displayable Attribute Message .................................................................................................... 348
Commodity Code Attribute Message .......................................................................................... 349

Plant Design System (PDS) Reference Data Manager (PD_Data) v


Contents

Isometric Drawing Labels ........................................................................................................... 349


Report Labels ............................................................................................................................... 349
Clash Management Labels ........................................................................................................... 349
Label Description Library Manager ................................................................................................... 351
Create Library .............................................................................................................................. 352
Compress Library ........................................................................................................................ 352
Unapproved ==> Approved ......................................................................................................... 352
Create Label Data ........................................................................................................................ 352
Revise Label Data ........................................................................................................................ 363
Delete Label Data ........................................................................................................................ 365
Report Label Data ........................................................................................................................ 366
Label Library Merger ......................................................................................................................... 371
Label Library Merger Interface ................................................................................................... 371
Label Library Merge Workflow .................................................................................................. 374

Piping Assembly Library ....................................................................................................................... 379


Piping Assembly Language................................................................................................................ 379
Placing Taps in Assemblies ......................................................................................................... 390
Sample Piping Assembly Files .................................................................................................... 391
Piping Assembly Library Manager .................................................................................................... 393
Create Library .............................................................................................................................. 395
Compress ..................................................................................................................................... 395
Unapproved ==> Approved ......................................................................................................... 395
Create/Interactive Piping Assembly Data .................................................................................... 395
Create/Batch Assembly Data ....................................................................................................... 396
Revise Piping Assembly Data ..................................................................................................... 397
Delete Piping Assembly Data ...................................................................................................... 398
Report Assembly Data ................................................................................................................. 399
List Assembly Data ..................................................................................................................... 400
Extract Assembly Data ................................................................................................................ 401

Reference Database Revision Manager ................................................................................................ 405


Reference Data Conflict Report ......................................................................................................... 407
Table Change Report.......................................................................................................................... 412
Reference Data Impact Report ........................................................................................................... 417
Proposed RDB Changes Report ......................................................................................................... 420

Verify RDB Library ............................................................................................................................... 425

Appendix: Reference Data Manager Error Messages ......................................................................... 429

Appendix: Codelists ................................................................................................................................ 431


CL31, Object Types for Orthographic Drawings (40) ....................................................................... 434
CL35, Approval Status (10) ............................................................................................................... 435
CL36, Structural Approval Status (15) .............................................................................................. 435
CL37, HVAC Approval Status (10) ................................................................................................... 436
CL50, Hold Status (10) ...................................................................................................................... 436

vi Plant Design System (PDS) Reference Data Manager (PD_Data)


Contents

CL69, Equipment Divisions/Form Code (99) .................................................................................... 436


CL125, Fluid Code/Connector Type (999) ........................................................................................ 437
CL130, Construction Status (15) ........................................................................................................ 441
CL145, Materials Grade (4500) ......................................................................................................... 441
CL148, Piping Materials Class Description (31999) ......................................................................... 470
CL160, Responsibility (25) ................................................................................................................ 479
CL180, Fabrication Category (99) ..................................................................................................... 479
CL190, Coating Requirements (99) ................................................................................................... 480
CL200, Heat Tracing Requirements (10) ........................................................................................... 480
CL210, Heat Tracing Media (60) ....................................................................................................... 481
CL220, Insulation Purpose (40) ......................................................................................................... 481
CL230, Cleaning Requirements (99) ................................................................................................. 482
CL330, CP Type/Termination/Preparation (999)............................................................................... 482
CL332, Schedule / Thickness Override.............................................................................................. 486
CL340, Safety Classification (99) ...................................................................................................... 487
CL360, Stress Analysis Requirements (15) ....................................................................................... 488
CL365, Reporting Requirements (25) ................................................................................................ 488
CL366, Requirement to Reconstruct (10) .......................................................................................... 488
CL380, Piping Component Type (2500) ............................................................................................ 488
CL390, Action (40) ............................................................................................................................ 496
CL400, Option (999) .......................................................................................................................... 496
CL420, Piping Component Type/Source (25).................................................................................... 503
CL425, Piping/Tubing Type (25) ....................................................................................................... 504
CL430, Instrument Component Type/Source (25) ............................................................................. 504
CL499, Piping Notes (999) ................................................................................................................ 504
CL530, Accessory/Item Type (125) ................................................................................................... 506
CL550, Operator Actuator Type (200) ............................................................................................... 507
CL570, Design Standard (200) .......................................................................................................... 508
CL572, Wall Thickness Equation ...................................................................................................... 508
CL575, Geometry Standard (31999) .................................................................................................. 509
CL576, Table Suffix/End Standard - Green (999) ............................................................................. 523
CL577, Table Suffix/End Standard - Red (999) ................................................................................ 528
CL578, Weight Code (399) ................................................................................................................ 532
CL990, Types of Piping Commodity Data Forms ............................................................................. 534
CL999, Standard Note Title (2000).................................................................................................... 535
CL1010, Area Units (25).................................................................................................................... 536
CL1028, Mass Units (40) ................................................................................................................... 537
CL1056, Temperature Units (15) ....................................................................................................... 537
CL1064, Pressure Units (40) .............................................................................................................. 538
CL1074, Density Units (35) ............................................................................................................... 539
CL1100, Weld Type (100) ................................................................................................................. 539
CL1162, Force Units (40) .................................................................................................................. 540
CL1201, Drawing Scale (540) ........................................................................................................... 540
CL1202, Drawing Size (199) ............................................................................................................. 540
CL1203, Interference Manager Approval Status (99) ........................................................................ 541
CL1204, Interference Clash Type (10) .............................................................................................. 541
CL1205, Interference Manager Action (10) ....................................................................................... 543
CL1207, Interference Manager Approval Method(10) ...................................................................... 543

Plant Design System (PDS) Reference Data Manager (PD_Data) vii


Contents

CL1208, Clash Checking Option ....................................................................................................... 544


CL1209, Clash Checking Volume Filter Option ................................................................................ 544
CL1310, Report Source (99) .............................................................................................................. 544
CL1312, Report Type (999) ............................................................................................................... 544
CL1410, Design Review Type (10) ................................................................................................... 545
CL1605, Model Status ....................................................................................................................... 545
CL1610, Force Units for FrameWorks Plus (40) ............................................................................... 545
CL1620, Drawing View Directions (7) .............................................................................................. 545
CL1630, Drawing View Composition Status (4) ............................................................................... 545
CL1710, Document Source (99) ........................................................................................................ 546
CL1720, Document Type (999) ......................................................................................................... 547
CL1900, Isometric Drawing Type ..................................................................................................... 549
CL2000, PD_Draw Document Type (999) ........................................................................................ 549

Index ........................................................................................................................................................ 553

viii Plant Design System (PDS) Reference Data Manager (PD_Data)


Preface PDS
This document provides command reference information and procedural instructions for the
Plant Design System (PDS) Reference Data Manager (PD_Data) task.

List of PDS Documentation


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

Plant Design System (PDS) Reference Data Manager (PD_Data) ix


Preface PDS

What's New in Reference Data Manager (PD_Data)


The following changes have been made to Reference Data Manager (PD_Data):
Version 2010
You can now schedule the Reference Data Conflict Report to run at regular intervals using
Batch Services. For more information, see Reference Database Revision Manager (on page
405). (P3 PB:73730)
Additional information added to Branch Table topic Create/Revise Piping Materials Class
Data. (see "Create/Revise Piping Materials Class Data" on page 75) (P3 PB:96483)
An additional piping wall thickness calculation (EL06) has been added. See Wall Thickness
and Branch Reinforcement Equations (on page 141) for more information.

x Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 1

Introduction
Welcome to the Reference Data Manager (PD_Data) module of the Plant Design System of
software. Intergraph's plant design software can be used to design any type of plant from
petrochemical plants, offshore platforms, chemical and pharmaceutical plants, consumer
products (food, beverages, cosmetics, soap, paper, and so forth), to power plants, waste water
treatment plants, and cogeneration facilities.
Specifically, the Plant Design System (PDS) integrates many discipline-specific software
modules; these modules automate the many phases of a plant design project. Reference Data
Manager (PD_Data) is one of these modules.
In PDS, placement of piping components is driven by the specification. The PDS reference data
provides the selection criteria for the piping commodity items that are found in the piping job
specification and the piping commodity libraries that are delivered with the product. This data is
contained in the reference database (RDB) and can be used by other projects.
The Reference Data Manager (PD_Data) is specifically designed to define and modify the
reference data for the PDS 3D modules. This reference data ensures consistency in the
definition of piping specifications and commodity libraries. It is used to control and standardize
the PDS 3D modules to reflect company practices and standards.

Project Organization
Since a process plant such as a refinery can be extremely large, PDS uses the following
organization to break the plant into smaller pieces that can be handled more easily.
A project is a convenient grouping of either all or part of the items that constitute a plant. The
project is the fundamental structure for working in PDS. Each project contains all the
information required to work in a PDS task.
The Project Administrator controls the creation and modification of Piping projects. Each
Piping project consists of a project control database, project design database, piping and
equipment models, reference models (structural, HVAC, and electrical raceway), a set of
drawings, and a collection of reference data. The reference data may be specific to one project or
shared by more than one project.
A project and all of its accompanying files must be defined with the Project Administrator
before you can use any of the other 3D PDS modules. Refer to the Project Administrator
Reference Guide for more information on setting up a project.

Plant Design System (PDS) Reference Data Manager (PD_Data) 1


Introduction

Reference Data Overview


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
Piping Materials Class Data (201) (on page 34)
Piping Commodity Specification Data (202) (on page 38)
Piping Specialty Specification Data (203) (on page 45)
Instrument Component Specification Data (204) (on page 48)
Tap Properties Data (205) (on page 51)
Piping Commodity Size-Dependent Material Data (211) (on page 54)
Piping Commodity Implied Material Data (212) (on page 56)
Component Insulation Exclusion Data (231) (on page 59)
Flange Insulation Exclusion Data (232) (on page 61)

Practice Specific Reference Data


Physical Data Tables (on page 194)
Piping Job Specification Tables (on page 131)
Short Material Description Library (on page 277)
Long Material Description Library (on page 283)
Specialty Material Description Library (on page 286)

Practice Independent Reference Data


Graphic Commodity Data (on page 183)
Standard Note Library (on page 335)
Label Description Library (on page 347)
Piping Assembly Library (on page 379)
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.

2 Plant Design System (PDS) Reference Data Manager (PD_Data)


Introduction

The following figure illustrates the various pieces of reference data required to place a 6" gate
valve in a piping model and report on the placed component. It depicts how the various parts that
make up PDS work together. Whenever possible, this placement example will be used
throughout the rest of this document. For example, the discussion of the physical dimension
tables will use the tables called to place the gate valve as examples.

See Also
Project Organization (on page 1)
Reference Database Introduction (on page 6)
Delivered Reference Data (on page 6)
Reference Data Setup (on page 7)

Plant Design System (PDS) Reference Data Manager (PD_Data) 3


Introduction

Piping Job Specification 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:
Specification/Material Reference Database - database containing the definitions for piping
materials classes, commodity items, specialty items, and tap properties tables.
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 specification 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 Data Introduction


The graphic commodity data is used to define commodity items, specialty items, and
instruments. The Graphic Commodity Library contains the parametric symbol definitions
required to place piping and instrument components in a 3D model. When you place a
component the system uses the Piping Job Specification to select the appropriate component
from the parametric symbol definition library which then accesses the component dimensional
data.
The graphic commodity data is contained in the following object libraries:
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.

Material Description Data Introduction


The Material Description Data is accessed for:
Material Take-off (MTO) reporting from the Design Database
Other miscellaneous reporting
Interfaces to the material control system
Stress analysis
Isometric drawing extraction.
The Material Description Data consists of the commodity item data which is not stored in the
Design Database, which is not required for the creation of graphic symbologies, and which is not
part of the geometric data. This data is contained in the following files:

4 Plant Design System (PDS) Reference Data Manager (PD_Data)


Introduction

Material Data in the Specification/Material Database - database tables containing


definitions for commodity items, criteria for implied material, and weld data.
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.

Standard Note Library Introduction


The text for code-listed attributes and standard notes is stored in the Standard Note Library. All
attributes identified as code-listed are actually stored as integer values. The code list text
associated with the integer is stored in the Standard Note Library. Information in the Standard
Note Library is identified by note number and note type. Output from the library consists of free-
format text which forms the standard note.

Label Description Library Introduction


The Label Description Library contains the definitions for the following label types used in PDS
3D:
Orthographic drawing view specific labels
Orthographic drawing view identification labels
Orthographic drawing - user input
Displayable attribute messages
Commodity code attribute messages
Isometric drawing labels
Report labels
Clash management 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).

Plant Design System (PDS) Reference Data Manager (PD_Data) 5


Introduction

Piping Assembly Library Introduction


The Piping Assembly Library contains the piping assembly definitions which define the
parameters necessary to place a piping assembly (group of components) automatically in the
model.
A Piping Assembly object library and text library which contain the definitions for basic
assemblies are included in the product delivery.

Reference Database Introduction


A database is a collection of formatted data which conforms to a set of pre-defined rules. The
Specification/Material Reference Database is composed of a set of tables (entities) which
represent categories of data. A table is a defined set of attributes which describe an item, such as
the Piping Commodity Data table.
An attribute is a single type of information to be stored about an item, such as nominal diameter
or end preparation. Each attribute has a column number in the database table and a name which
describes the piece of information to be stored. The actual information stored in the database is
referred to as the attribute value. This value is a fixed data type; it can be either numeric,
alphanumeric, or code-listed.
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 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.

Delivered Reference Data


The following reference data is delivered in the reference database products for the
corresponding practices (such as RDUSRDB or RDDINRDB).

File Description Library Object Library Text

Physical Dimension Table Library us_pcdim.l us_pcdim.l.t


Piping Job Specification Table Library us_pjstb.l us_pjstb.l.t
Short Material Description Library us_shbom.l -
Long Material Description Library us_lgbom.l -
Specialty Material Description Library us_spbom.l -
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.

6 Plant Design System (PDS) Reference Data Manager (PD_Data)


Introduction

File Description Library Object Library Text


Graphic Commodity Library pip_gcom.l pip_gcom.l.t
Piping Assembly Library assembly.l assembly.l.t
Label Description Library labels.l -
Standard Note Library std_note.l std_note.l.t

Reference Data Setup


A project and all of its accompanying files must be defined with the Project Administrator
before you can use the Reference Data Manager. Refer to the Project Administrator Reference
Guide for information on:
Loading PDS 3D products.
Editing the control script to identify the location of the project data.
Setting up a project and creating the associated database schemas.
Accessing the PDS 3D products remotely using NFS.
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 systems is Notepad.
$ENV {'PD_EDITOR'} = '<absolute path to preferred editor
executable>';
Edit the pds.cmd file to define PDS_COMMIT_INTERVAL to control the commit interval
for use in loading specification data into the Material Reference Database. This has the same
impact as adjusting the -c option in a risload command line. The default commit value is 25.
Increasing this variable may improve performance.
Identify the location of the Reference Data files as described in Reference Data Location (on
page 23).

Plant Design System (PDS) Reference Data Manager (PD_Data) 7


Introduction

8 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 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 PD_Shell Environment and all batch jobs in the PDS 3D products interface to Intergraph's
Network Licensing System.
See Also
PD Shell (on page 9)
Help (on page 16)

PD Shell
The PD Shell program provides access to the various functions that are associated with the PDS
3D Modules. You can access the Plant Design System Environment form by clicking Start >
All Programs > PD_Shell > PD_Shell. This executes a control script that defines all of the
environment variables that are needed to run the product, and it identifies the location of the
product files. These files can be located on the workstation or a server on the network. See
pds.cmd for more information on this file. The script also activates the Plant Design System
Environment form.

Plant Design System (PDS) Reference Data Manager (PD_Data) 9


PDS Environment

To make colors easier to read on flat screens and projectors, a zip file with modified color for
PDS forms is delivered as alternatecolorfb.zip.

This form identifies the active project(s) and provides access to all the PDS functions.
Schematics Environment Provides access to the PDS 2D modules that are used to create and
modify piping and instrumentation diagrams, process flow diagrams, and instrumentation
database records.
Equipment Modeling Provides access to the Equipment Modeling module, which provides
an interactive graphics environment that is used to create and revise equipment model graphics
and database information.
FrameWorks Environment Provides access to the FrameWorks module, which provides an
environment that is used to create and revise structural models, create and revise structural
drawings, and propagate structural models.
Piping Designer Activates an interactive command environment that is used to create piping
and in-line instrumentation in the model; revise existing model graphics and database
information; and verify the integrity of the data in the model.
Electrical Raceway Environment Provides access to the Electrical Raceway module, which
provides an interactive environment that is used to create and revise raceway models and access
raceway utilities.
Piping Design Data Manager Provides access to a set of options that are used to verify the
integrity of the graphic and database information that is associated with a model.
Piping Model Builder Enables you to create piping graphics from a nongraphics
environment. This module is used with PD_Design to create an accurate 3D model of the piping
network.

10 Plant Design System (PDS) Reference Data Manager (PD_Data)


PDS Environment

Pipe Support Designer Activates an interactive command environment that is used to create
pipe supports in the model, and revise existing pipe support model graphics and database
information.
Pipe Stress Analysis Activates a set of forms that are used to extract information from piping
models for input to third-party pipe stress analysis products.
Interference Manager Activates a set of forms that are used to check for interferences
among project models and to control approved interferences.
Isometric Drawing Manager Activates a set of forms that are used to extract isometric
drawings from piping models and to review or plot the created isometric drawings.
Drawing Manager Activates a set of forms that are used to create and manipulate drawings
and drawing views; provide access to the interactive graphics environment for drawings; and
provide access to a plot manager and vector hiddenline manager.
DesignReview Integrator Activates a set of forms that are used to extract information to
form label files for use in SmartPlant Review and to review data from a SmartPlant Review
session.
Report Manager Activates a set of forms that are used to create and revise report format
files and report on information in a project including Material Take-Off reports.
Project Administrator Provides access to a set of forms that are used to create a project,
create and revise project files, define project seed data, and control the project.
Reference Data Manager Provides access to a set of forms that are used to control the
reference data for a project including Piping Job Specification data, Graphic Commodity Data,
Alphanumeric Commodity Data, Standard Note Library, Label Description Library, and Piping
Assembly Library.
User ID Used for access control. This field also sets the Review User ID for use in the
Interference Manager module.
If access control has been defined, you must key in a valid user ID as defined by your system
manager to gain access to the projects. Refer to Access Control Manager, page 467, for more
information on using access control.
If access control has not been defined, no entry is required for this field.
Password Key in the password for the specified user ID.
Project List Field Displays the defined projects for the network and allows you to select the
active project. The system lists all the defined PDS projects (2D-only, 3D-only, and 2D & 3D).
An error is displayed if you select an option that is incompatible with the active project. For
example, if the active project is a 2D-only project, you cannot access the Interference Manager
module.
If access control has been defined, only those projects for which you have some level of access
are displayed.
Message Area Displays prompts and messages that are associated with the active process.
Error messages are displayed in red.

Plant Design System (PDS) Reference Data Manager (PD_Data) 11


PDS Environment

PD_Shell Form Conventions


The following conventions describe how to respond to the various buttons, lists, and prompts
that make up the environments. The display size of forms and dialog boxes in the non-
Microstation graphics environment are independent of the size of the workstation's display
system. Most forms contain the same basic features: buttons, fields, text, and other gadgets. In
general, anything you find on a form is called a gadget.
You move through the PD_Shell forms by selecting function buttons or other gadgets from the
form. Select means to place the screen cursor (which appears as an arrow) on top of a screen
gadget and press <D>.
For most of the forms with scrolling lists, you can double-click on a row to select and accept the
data in that row. This performs the same action as selecting a row (which highlights) and then
selecting 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.

Common Tools on the PD_Shell Forms


There are many gadgets in the environments that are common to most or all of the forms. The
following describes these tools.

Standard Commands
The PD_Shell forms have a set of standard buttons in the upper right corner of most of the form
windows. The available commands vary from form to form depending on the type of operation.
The Help button activates on-line Help for the
active form. Help remains active until you
delete the Help window.
The Shell button exits the active form and
returns control to the base manager that is
associated with the active form. For most
forms this returns to the Plant Design System
Environment form.
The Top button exits the active form and
returns control to the top form of the active
branch.
The Cancel button cancels or exits from the
active form. Control returns to the
immediately preceding form in the hierarchy.

12 Plant Design System (PDS) Reference Data Manager (PD_Data)


PDS Environment

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.
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

Plant Design System (PDS) Reference Data Manager (PD_Data) 13


PDS Environment

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, re-select
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
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.
Shift Left and Shift Right buttons
At the bottom of some key-in and display
fields, there are two buttons marked with
arrows. These buttons are called shift left and
shift right buttons. Often, you can key in more
characters than a field display shows. Shift
Left moves the text display to the front of the
field; Shift Right moves the text display to
the end of the field.

14 Plant Design System (PDS) Reference Data Manager (PD_Data)


PDS Environment

Toggle
A toggle field on a screen menu enables you
to select one of two possible choices, one of
which is always displayed. Place a data point
on the toggle field to toggle between the two
choices.
Roll-Through List
A roll-through list shows one choice at a time
of a list that can be several items long. Place
a data point on the roll-through list to scroll
through the available options. The option
displayed is active.
Standard Window Icons
When using this software, you can press <D>
along the edge of a form or any area not
occupied by a button, key-in field, or other
gadget, to display a box of icons. You can
manipulate form windows just like any other
workstation window.
The following list defines the available
window icons.
Collapse/Restore
Repaint
Pop-to-bottom
Modify/Resize
Pop-to-top
Restore Size

Path Location Fields


Some key-in fields are used to specify paths for various files and folders, such as project folders,
model files, reference data files, drawing files, and isometric drawing files. Prior to PDS 8.0,
these path fields required the user to enter a full path, including the drive name, such as
d:\project1\piping\models. Beginning with PDS 8.0, path fields accept share names as input. For
example, if you have the project1 folder set up as a share, you could enter
\project1\piping\models or project1\piping\models as the path for piping models.
This new functionality allows administrators to set different permissions for shares used by
different sets of users. For more information on setting up shares and permissions, see the PDS
Project Setup Technical Reference.

Plant Design System (PDS) Reference Data Manager (PD_Data) 15


PDS Environment

Batch Processes
When you install the PDS 3D applications, the system creates the necessary batch queues for
that application. Refer to Loading Products in the Project Administrator Reference Guide for a
listing of the batch queues.
PDS 3D uses these batch queues to allow you to continue working in the environment while the
system processes a request. Many of the batch processes can be delayed for submission at a
specified time.

Help
On-line Help is a special feature of your application software. Help provides
instant access to information from the application reference documents, such as
command descriptions and explanations, prompt sequences, and much more.
There are several avenues you can take to find information about a command or subject. For
instance, Help provides
A table of contents that lists subjects by topic and subtopic (in a hierarchy).
An alphabetized index of every command or subject that has been documented for the
software.
A glossary to help you become familiar with product-specific terms.
The ability to move up, down, back, and forth through Help by using cross-references and
links to primary and secondary commands.
The ability to quickly search through Help for information on a specific subject or
command.

When you first select Help, the Help Table of Contents is displayed in a pop-up window. Select
a topic from this list or select a command from the menu to display an article in the pop-up
window.
Whenever possible, PDS Help is context sensitive. For example, if you select the help icon for a
given form, Help that is specific to that form is displayed.

16 Plant Design System (PDS) Reference Data Manager (PD_Data)


PDS Environment

The Help window has buttons that you can use to manipulate either Help or the window itself as
follows:
Scroll Bar - Moves up or down in an article that is displayed in the Help window.
Help Command Buttons - Enable you to move around in the Help file.
Cancel or File > Exit - Exits Help and closes the Help window.
1. Select the Help button from the command window or form.
If you select Help while using a command, help on the active command is displayed. If no
command is active, the table of contents is displayed.

2. Use the command buttons or scroll bar to move around in Help.


OR
Exit Help.

Plant Design System (PDS) Reference Data Manager (PD_Data) 17


PDS Environment

18 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 3

Reference Data Manager


The Reference Data Manager provides access to the various functions associated with the PDS
3D Reference Database. Select the Reference Data Manager option from the PD Shell form.

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 (on page 64).
Piping Job Specification Manager Used to create, modify, and delete information in the
Material Reference Database using neutral files. See Piping Job Specification (on page 29) and
Piping Job Specification Manager (on page 101).
Piping Job Specification Tables Used to create, modify, and delete information in the
Piping Job Spec Table Library. See Piping Job Specification Tables (on page 131) and Piping
Job Specification Tables Command (on page 172).
Piping Job Spec Report Manager Used to define and generate reports of data in the
Material Reference Database. See Piping Job Spec Report Manager (on page 109).
Graphic Commodity Library Manager Used to create, modify, and delete graphic
commodity library data (Eden modules). See Graphic Commodity Library (on page 183) and
Graphic Commodity Library Manager (on page 200).
Physical Data Library Manager Used to create, modify, and delete physical data
(dimension tables) in object and text libraries. See Physical Data Tables (on page 194) and
Physical Data Library Manager (on page 208).

Plant Design System (PDS) Reference Data Manager (PD_Data) 19


Reference Data Manager

Material Description Library Manager Used to create and modify alphanumeric


commodity data. See Material Description Data (on page 273) and Material Description
Library Manager (on page 287).
Support Tutorial Definition Manager Used to create, revise, and delete data in the Tutorial
Definition Library. See Pipe Support Tutorial Definition Manager (on page 327).
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 (on page 335)
and Standard Note Library Manager (on page 338).
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 (on page 347) and Label Description
Library Manager (on page 351).
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 (on page 379) and Piping Assembly
Library Manager (on page 393).
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 (on page 298).
Reference Database Revision Manager Used to create a set of reports for coordinating
revisions in the Reference Database and the implied changes which are required in the model.
See Reference Database Revision Manager (on page 405).
Reference Database Management Data Used to define the file names 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
(on page 24).
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 (on page 23).

Data Security
The Reference Data Manager provides data security features for the following reference data
libraries in the event of accidents such as, electrical power surges and network failures. These
features also protect the libraries in the event that a library is being shared by multiple projects,
and different users in different projects mistakenly attempt to revise one of the libraries
simultaneously.
Graphic Commodity Library
Physical Data Library
Piping Job Specification Table Library
Short Material Description Library
Long Material Description Library
Specialty Material Description Library

20 Plant Design System (PDS) Reference Data Manager (PD_Data)


Reference Data Manager

Standard Note Library


Label Description Library
Piping Assembly Library
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 object library.
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 a corrupted library (including the corresponding source library and revision library)
has been restored from a backup, select the accept option.
If you are concerned with the integrity of the library for any reason, select the exit
option. Then restore the library, the corresponding source library, and the corresponding
revision library to their previous state (before the last revisions).
If you are aware that a different user may be revising that library within a different project,
select the exit option.
This feature requires that PDS users have write access to the directory in which the
libraries reside. The Reference Data Manager will display an error message, if the user does
not have privileges for write access to the applicable directory and the user will not be able
to revise that library.
When a PDS user exits a data creation or revision session, the Reference Data Manager verifies
the integrity of the binary tree structure within the library. The system displays an error if the
Reference Data Manager determines that an error exists in the binary tree structure. In this event,
you should contact Intergraph immediately for assistance in repairing the library.

Plant Design System (PDS) Reference Data Manager (PD_Data) 21


Reference Data Manager

Reference Data Archival


PDS includes a Project Archival Manager to provide archival and retrieval facilities for
projects, including reference data. For more information about the Project Archival Manager,
see Project Archival Manager in the Project Administrator Reference Guide. For specific
information about archiving reference data, see Reference Data in the Project Administrator
Reference Guide.

22 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 4

Reference Data Location


This section describes the options used to define the location of the Reference Data files on the
network.
Reference Database Management Data (on page 24) Defines the location for Reference
Database Files, graphic commodity data, dimension tables, and spec tables. You can define
both approved or unapproved RDB data for each item.
Default Project Control Data (on page 23) Defines the default location for the source
files used to load the RDB files (such as neutral files, language files, and report files).

Default Project Control Data


This option defines the default location for common reference files used by the project (such as
neutral files, report files, and library files). You can also change these file locations during the
operation of the applicable managers

Operating Sequence
1. Select Default Project Control Data from the Reference Data Manager form to define the
default location for the RDB source files.
2. Select the field to be defined and key in the location of the source files and the associated
node name.
Piping Eden Path / Node The default location for the Eden source files.

Plant Design System (PDS) Reference Data Manager (PD_Data) 23


Reference Data Location

Dimension/Spec Table Path / Node The default location of the Dimension Table
and Spec Table source files.
Piping Spec Path / Node The default location for the neutral files to be used to load
the Specification/Material Reference Database and Material Description Libraries.
Assembly Path / Node The default location for the Piping Assembly Language
source files.
Standard Note Library Path / Node The default location for the Standard Note
(code list) source files.
Equipment Eden Path / Node The default location for the Equipment Eden source
files.
TDF Table Path / Node The default location for the Equipment table definition files.
Model Builder Path / Node The default location for the model builder language
source files.
3. Accept any changes to the Project Control Data.

Reference Database Management Data


This option activates the Reference Database Management Data form used to define the file
names for Reference Database Files, graphic commodity data, dimension tables, and spec tables.
You can define both approved or unapproved RDB data for each item.

Operating Sequence
1. Select Reference Database Management Data from the Reference Data Manager form.

2. Select RDB File Type


Select the RDB file from the list of files. You can use the scroll arrows to scroll through the
listed files.

24 Plant Design System (PDS) Reference Data Manager (PD_Data)


Reference Data Location

The system identifies the file for the selected field in the fields at the bottom of the form.
There are no default settings for these files; you must define the applicable file locations
before you can continue.
Material/Specification Reference Database This field identifies the Material
Reference Database for the project. Refer to the Project Setup Manager in the Project
Administrator Reference Guide for more information on this database.
Piping Job Specification Tables (on page 131) Library This field identifies the
location of the Piping Job Spec Table library.
Short Material Description Library (on page 277) This field identifies the library
which contains the short bill-of-material description for all piping commodity items and
the BOM description addenda for taps.
Long Material Description Library (on page 283) This field identifies the library
which contains the long BOM description for all piping commodity items. The long
BOM description is only used for requisitions.
Specialty Material Description Library (on page 286) This field identifies the library
which contains the BOM description for engineered items, in-line instruments, and pipe
supports. This library tends to be customer-specific.
Standard Note Library (on page 335) This field identifies the location of the standard
note library.
Label Description Library (on page 347) This field identifies the location for the
label description library.
Piping Assembly Library (on page 379) This field identifies the location for the
Piping Assembly library. This library contains the symbol definitions for assemblies.
Graphic Commodity Library (on page 183) This field identifies the library which
contains the Eden modules used to place components in the model.
Physical Data Tables (on page 194) Library These fields identify the library files
which contain the physical data tables for a range of geometric industry standards.
Commodity Synonym Library This field identifies the user-defined library which
contains the map for translating the default piping commodity names used in the P&ID
Task to names specified by the user in the Piping Job Specification.
Orthographic Drawing Borders This field identifies the drawing border files to be
used when creating drawings. A set of border files are delivered to the directory
win32app\ingr\pddraw\border. You must specify which style of borders is to be used.
3. Key in any changes to the selected RDB files. Refer to Delivered Reference Data (on page
6) for a listing of the delivered reference data files.
If you specify an unapproved file, the system will use the unapproved file for all Reference
Data Manager operations (such as revising entries in a library.)
Refer to the Project Data Manager in the Project Administrator Reference Guide for
information on setting the choice of data for a model file or drawing.
4. You can select Approved --> Not Approved to copy the approved definition of the selected
RDB file to the Not Approved fields. Select confirm to update the information.
Refer to the individual managers for information on posting the unapproved information to
the approved files.

Plant Design System (PDS) Reference Data Manager (PD_Data) 25


Reference Data Location

5. You can select Default All Library Locations to define a default location for all approved
and all unapproved library files.
6. You can select Copy All Standard Libraries to copy the delivered library files to a
specified location.
7. Select Accept following each change to the reference data to accept the specified file
location.
THEN
Select Cancel to exit the form.

Default All Library Locations


This option assigns a default network address, pathname, and file specification to the various
Reference Database libraries for both the approved and unapproved libraries. You can override
any of these default specifications by selecting the appropriate library and keying in the file
information.
Specify Default Nodename
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.

Library File name


Graphic Commodity Library pipe_gcom.l
Label Description Library labels.l
Standard Note Library std_note.l
Piping Assembly Library assembly.l
Piping Spec Table Library pjs_tbl.l
Short Material Description Library short_bom.l
Long Material Description Library long_bom.l
Specialty Description Library spclty_bom.l
Physical Data Library <standard>_pcdim.l

26 Plant Design System (PDS) Reference Data Manager (PD_Data)


Reference Data Location

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

Copy All Standard Libraries


This option copies the delivered Reference Database libraries from the applicable product
directories to the disk locations specified in the Reference Database Management data of the
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.
Graphic Commodity Library Standard Note Library
Label Description Library Piping Assembly Library
The following Reference Database libraries are copied from the applicable Reference Database
product (such as rdusrdb or rddinrdb).
Physical Data Library Long Material Description
Library
Piping Spec Table Library Specialty Description Library
Short Material Description Library
The system also copies the applicable Table Revision Management Libraries for the Piping Spec
Table Library and Physical Data Libraries.

Plant Design System (PDS) Reference Data Manager (PD_Data) 27


Reference Data Location

The text to be used for the standard is determined in the following manner.

Practice Prefix
U.S. Practice us
European - DIN din
European - British Standard bs
International - JIS jis
International - Australian aus
The list of available products is determined from the list of exported variables as specified in the
pds.cmd shell script. Therefore, this command presently searches for the following exported
variables:

Product Practice
RD_USRDB U.S. Practice
RD_DINRDB DIN
RD_BSRDB British Standards
RD_JISRDB JIS
RD_AUSRDB Australian
The file specification recorded in the Project Control Database, and not that of the library in the
delivered product, will be used for the destination library.
If the RDB product resides on a remote server (or workstation), you must manually mount
the directory that includes the RDB product and change the exported variable in the pds.cmd
shell script accordingly.
The system will display an error message for any of the following conditions.
Any of the active Reference Database libraries for the project are in use (locked). None of
the libraries are copied.
The network address for any of the active Reference Database libraries for the project is
undefined. None of the libraries are copied.
The network address and path name for any of the active Reference Database libraries for
the project cannot be mounted. None of the subsequent libraries are copied.

28 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 5

Piping Job Specification


The Piping Job Specification (PJS) defines the characteristics, properties, design standards, and
company practices associated with piping commodity items, piping engineered items, and
instruments. When you select an item 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 for the selected item. Then the system reads the PJS for the parameters required to
define the item.
See Also
Material Reference Database Structure (on page 29)
Spec Writer (on page 64)
Piping Job Specification Manager (on page 101)
Piping Job Spec Report Manager (on page 109)

Material Reference Database Structure


The Material Reference Database contains a set of tables which define the Piping Job
Specification data. The numbers in parentheses indicate the database table number.
Piping Materials Class Data (201) (on page 34)
Piping Commodity Specification Data (202) (on page 38)
Piping Specialty Specification Data (203) (on page 45)
Instrument Component Specification Data (204) (on page 48)
Tap Properties Data (205) (on page 51)
Piping Commodity Size-Dependent Material Data (211) (on page 54)
Piping Commodity Implied Material Data (212) (on page 56)
Component Insulation Exclusion Data (231) (on page 59)
Flange Insulation Exclusion Data (232) (on page 61)
Piping Construction Tolerance Exclusion Data (233) (on page 63)
The Piping Commodity Specification Data is linked to the Piping Materials Class Data.
The Reference Database Revision Management Data table is totally system-defined. It
stores the revision dates for the other database tables in the Material Reference Database. The
revision dates are updated automatically when you use the Piping Job Spec Manager to load,
revise, or delete data in these database tables.

Plant Design System (PDS) Reference Data Manager (PD_Data) 29


Piping Job Specification

Attribute Types
The following conventions are used to designate the field type for database attributes.
character(n) alphanumeric field n characters in length
integer long (double word) integer
short short integer
double real (floating point) value
standard note Standard Note Type for code-listed attribute
nnnn

Code-Listed Attributes
A code-listed attribute is an attribute whose value must be defined using one of the selections
from a particular code list in the Standard Note Library. In the following database description,
attributes which are code-listed are identified by a standard note number at the end of the line
following the field type description. For example, the line
6. fluid_code , character(6) , SN 125
indicates that fluid_code is defined in terms of code list numbers belonging to Standard Note
125, Fluid Code/Connector Type. A possible entry for this attribute would be 197 for chlorine
gas (GCL). Refer to Appendix: Codelists (see "Table Checker" on page 295) for a listing of the
code list sets associated with PDS 3D.

Connect Point Data


The Piping Commodity, Piping Specialty, and Instrument database tables classify connect point
dependent data about a component in terms of green and red connect points. The following
conventions are used to coordinate the two sets of data:
If data is only shown under the green connect point, it applies to all ends of the component.
If a component has ends with different nominal diameters (regardless of other end
properties), the larger nominal diameter is designated as the green connect point.
If a component has ends with the same nominal diameter but other end properties which
differ, the following rules apply:
If the ends have different termination types (regardless of the values for
schedule/thickness), the end(s) whose end preparations have the lowest codelist number
are designated as the green connect point.
If the termination types are the same but the values for rating, schedule, or thickness
differ, the "stronger" ends(s) are designated as the green connect point.

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.

30 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Neutral File Input


A neutral file is an ASCII text file used to load information into the Material Reference
Database. The neutral file must conform to the following rules:
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.
The system_unique_no attribute is never user-defined. Therefore, it should not be
included in the neutral file data or in the list of attributes defined by the SEQUENCE
statement.
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 affect the
information being copied.
You can use any of the three PDS conventions to enter fractional Nominal Piping Diameters.
The entries
2-1/2 2.5 2 1/2
are all equivalent ways of entering the same figure.
If you use the SINGLE_SPACING option, 2 1/2 can be used only if enclosed by
single quotes ('2 1/2').
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:
mm for metric
" for English
The Tap Properties Table must include the Table Name along with other data by using the
TABLE statement.

Plant Design System (PDS) Reference Data Manager (PD_Data) 31


Piping Job Specification

SEQUENCE Statement
The SEQUENCE statement is an optional statement which can be used to define the order of the
parameters in the neutral file. If the SEQUENCE statement is used, it must be placed before any
entries. The SEQUENCE statement can only be used once per file.
If the SEQUENCE statement is omitted, it is assumed that the parameters appear in the
order defined by PDS.
Format
SEQUENCE= P1 P2 P3 P4 ... Pn
where:
SEQUENCE= keyword which can be entered in either upper or lower case
letters.
P1,P2,...Pn parameters 1 through n. The values of P1...Pn are the
parameter numbers assigned by PDS, and their position tells the
system the order in which to enter them.

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.

32 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

TABLE Statement
The TABLE statement defines a table name to be associated with a particular set of data. The
active table name remains unchanged until another TABLE statement is encountered. The
TABLE statement can be used more than once in a neutral file.
Format
TABLE= table_name
where
TABLE= keyword which can be entered in upper or lower case
letters.
table_name the name of the table associated with the following data.
There must be at least one/two spaces (depending on the default spacing selected) between the
keyword and the table_name.
For example, the Tap Properties Table below defines two tables (C001, and C002) by using the
Table keyword to segregate the data for each table being defined.
Double_Spacing
Order= 2 3 5 4 6 7
! By=GJH Ckd By=RJW Rev=2 Date=12-May-1995
Table= C001
! Description= SWE CL3000 default taps
! Diam Opt Rating Prp Sc/Th Tap Code
0.375 691 - 591 NREQD E$37591XXX
> 0.5 1 CL3000 421 NREQD E$50421064
0.5 691 - 591 NREQD E$50591XXX
:
:
30 691 - 591 NREQD E030591XXX
32 691 - 591 NREQD E032591XXX
34 691 - 591 NREQD E034591XXX
36 691 - 591 NREQD E036591XXX
42 691 - 591 NREQD E042591XXX
48 691 - 591 NREQD E048591XXX
Table= C002
! Description= SWE CL6000 default taps
! Diam Opt Rating Prp Sc/Th Tap Code
0.375 691 - 591 NREQD E$37591XXX
> 0.5 1 CL6000 421 NREQD E$50421072
0.5 691 - 591 NREQD E$50591XXX
:
:
34 691 - 591 NREQD E034591XXX
36 691 - 591 NREQD E036591XXX
42 691 - 591 NREQD E042591XXX
48 691 - 591 NREQD E048591XXX

Plant Design System (PDS) Reference Data Manager (PD_Data) 33


Piping Job Specification

Piping Materials Class Data (201)


The piping materials class data is independent of nominal piping diameter and commodity item.
A piping materials class defines a classification of components based on design data and service
limits. Much of the design data is stored in tables so that common information can be accessed
by more than one piping materials class.
The Piping Materials Class Data table contains 23 attributes.
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.
The revision number of the unapproved Material Reference Database is incremented
only, when you specify a new revision number in the neutral file.
The revision number of the approved Material Reference Database is updated to that of
the unapproved Material Reference Database, when the unapproved data is posted to the
approved Material Reference Database.
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.
6. fluid_code, character(6), SN 125
This attribute can be used to define the type of fluid for which the piping materials class is
intended.
You can specify:
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 (on page 151) 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.

34 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

7. mater_of_construct, character(6)
This attribute defines the materials of construction class for the piping materials class. This
code has a detailed definition outside the scope of PDS that represents the decision of the
Project Metallurgist regarding the piping system. It is required for reporting and making
matches and comparisons with values for this parameter from the Piping Design Database.
This parameter includes the material code.
8. corrosion_allow, double
This attribute defines the corrosion/erosion allowance that applies to the piping materials
class. It is required for reporting and to calculate the wall thickness of piping components
whose thickness is not specifically included in the piping materials class.
9. mat_description, short, SN 148
This code-listed attribute is a generic description of the materials used for this piping
materials class (such as carbon steel). This attribute is only used for reporting.
10. service_lim_table, character(6)
This attribute identifies the table used to determine maximum pressure as a function of
temperature. This table includes the pressure and temperature sets that form the boundary
for which the commodity items, engineered items, and instruments included in this piping
materials class are suitable (unless you define a lower maximum temperature limit for a
specific commodity item). You must insure that all commodity items within the piping
materials class are acceptable within the boundary of this table.
Refer to Temperature and Pressure Service Limits Table (on page 131) for more information
on this table.
11. diameter_table, character(6)
This attribute identifies the nominal piping diameter table used to verify valid nominal
piping diameters in this piping materials class. Refer to Nominal Piping Diameters Table
(on page 133) for more information.
12. thickness_table, character(6)
This attribute identifies the thickness data table used in piping wall thickness calculations for
this piping materials class. Refer to Thickness Data Tables (on page 136) for more
information.
13. materials_table, character(6)
This parameter defines the materials data table used to determine the material properties
required for piping wall thickness calculations in the piping materials class. Refer to
Materials Data Table (on page 139) for more information.
14. thickness_equation, character(6)
This attribute identifies the default piping wall thickness equation to be used for this piping
materials class. If a schedule/thickness parameter for an item specifies the default
calculation, then this equation is used to perform the piping wall thickness calculation.
Refer to Wall Thickness and Branch Reinforcement Equations (on page 141) for more
information.

Plant Design System (PDS) Reference Data Manager (PD_Data) 35


Piping Job Specification

15. branch_table, character(6)


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).
Refer to Branch Insertion Tables (on page 144) for more information.
16. tap_data_table, character(6)
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)
(on page 51) for more information.
17. vent_drain_macro, character(6)
This attribute is not currently used by the PDS software. Several vent and drain definitions
are contained in the delivered Piping Assembly Library.
18. gasket_separation, character(8)
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.)
This attribute exists as alphanumeric data.
A value with all numeric characters is interpreted as a gasket separation value in the
physical subunits specified for the model.
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 (on page 150) for more information.
Refer to the description of gaskets in the PDS Piping Component Data Reference Guide for
more details.
19. standard_note_no_a, short , SN 499
20. standard_note_no_b, short , SN 499
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.
21. revision_mngt_date, integer
This system-defined attribute identifies the date of the latest revision for the data in this
piping materials class.
22. bend_deflect_table, character(6)
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.

36 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Note that the Bend Deflection Table name in the Piping Materials Class data is limited to 6
characters to be consistent with the other tables referenced in this data. The maximum
length of the default Bend Deflection Table name, as specified with the Project Data
Manager can be as many as 20 characters.
Refer to Bend Deflection Table (G04) (on page 156) for more information.
23. pipe_length_table, character(6)
This attribute identifies the Pipe Length Threshold Table to be used for this piping materials
class. This attribute is useful in defining specs for underground piping.
If this column is undefined (blank), the system will use the default Pipe Length Threshold
Table specified in the Type 63 data through the Project Data Manager. Therefore, you
need not define a Pipe Length Threshold Table for each piping materials class in the
Material Reference Database.
Note that the Pipe Length Threshold Table name in the piping materials class data is limited
to 6 characters to be consistent with the other tables referenced in this data. The maximum
length of the default Pipe Length Threshold Table name, as specified with the Project Data
Manager can be as many as 13 characters.
Refer to Pipe Length Threshold Table (G07) (on page 158) for more information.

Neutral File Format


The following is a sample neutral file for the Piping Material Class database table. Entries in
this table should be sorted alphanumerically by Piping Materials Class.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 37


Piping Job Specification

Sample Files
A sample neutral file for US practice is delivered in the file
\win32app\ingr\rdusrdb\spec_data\classes.pmc. A set of sample files depicting various options
are delivered in the \win32app\ingr\pddata\sample\data directory.
bend_tbl.pmc gasket.pmc pharm.pmc
equiv_npd.pmc gskt_tbl.pmc piplen_tbl.pmc
fluid_code.pmc metric_npd.pmc thickness.pmc
fpipe.pmc

Piping Commodity Specification Data (202)


The Piping Commodity Specification Data defines all the components, pipes, bolts, and gaskets
associated with a particular Piping Materials Class. It defines the standard components found in
a manufacturers catalog (commonly referred to as off-the-shelf components). Because the Piping
Commodity Specification Data is linked to the Piping Materials Class, a separate set of
commodity items must be defined for each Piping Materials Class.
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 (on page 197) for more information
on green and red connect points.
The Piping Commodity Specification Data table contains 28 attributes:
1. system_unique_no, integer
2. piping_mater_class, character(16), index 1
This attribute identifies the Piping Materials Class for the piping commodity.
3. commodity_name, character(6)
This attribute identifies the commodity item name. This can be:
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.
4. option_code, short, SN 400
This code-listed attribute identifies the option code which determines the search criteria.
This parameter enables you to request that the system retrieve the primary commodity item,
a secondary commodity item, or another special option from the Piping Job Specification.
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.
Option codes 4500 to 4999 are reserved for company practice (user-defined).
Option codes 5000 to 5999 are used to refer to implied components.

38 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

5. maximum_temp, double
This attribute is used if the commodity item is temperature dependent. It represents the
maximum temperature for which this commodity item is acceptable. When a commodity
item is retrieved from the Piping Job Specification, the system verifies that the normal
operating temperature, the alternate operating temperature, the normal design temperature,
and the alternate design temperature are less than this maximum allowable temperature. If
this maximum is exceeded by any of these temperatures, the system automatically searches
for another occurrence of the same commodity item.
For gaskets, to help determine the gap thickness at bolted joints, the maximum
temperature value is used as an input to the Gasket Gap Table. Proper entry of
temperature values in the PJS assists the definition of gap thicknesses when gaskets with
different gap thicknesses are used in the same piping materials class.
If you specify the default value (-9999), no test is performed. Any reports created from
the Piping Job Specification depict this default value as alphanumeric blanks.
The order in which entries of the same piping commodities with different maximum
temperature values are made in the PJS (PDtable_202) is not considered by the system;
however, these entries must have the same option code in order to be considered by the
commodity selection in the Place Component command. When you do define the piping
commodity, a maximum temperature value must be defined for each entry or an error
message is displayed. To define the highest maximum temperature for the same piping
commodity, set the maximum temperature equal to or greater than the maximum
temperature of the spec limits table for the applicable piping materials class instead of using
an undefined value ('-').
6. gcp_from_nom_diam, short (NPD Units)
7. gcp_to_nom_diam, short (NPD Units)
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point (first size) in NPD units. The to value must equal
or exceed the from value. These values are not necessarily the same as the range in Tables
211 and 212. The applicable NPD value specified at placement is used to search for the
suitable component in the Piping Job Specification.
The default system of units (" for inches, or mm for millimeters) must be declared once in
the beginning and each time the default system is changed. If no units are given, the value is
automatically interpreted as inches.
8. gcp_end_prep, short, SN 330
This code-listed attribute identifies the end preparation for the green connect point. The
system determines the termination type based on the range of values:
2 - 199 bolted terminations
300 - 399 male terminations
400 - 599 female terminations
You can define end compatibilities by using the End Preparation Compatibility Table.
(Refer to the Project Data Manager in the Project Administrator Reference Guide.)
9. gcp_rating, character(8)
This attribute identifies the pressure rating for the green connect point. This parameter
exists as alphanumeric data. The system interprets the first set of sequential numeric
characters as being the pressure rating value.

Plant Design System (PDS) Reference Data Manager (PD_Data) 39


Piping Job Specification

Ratings can be expressed in any of the following formats: CLxxxx, xxxx#, or OTxxxx.
However, table entries and file names representing the rating exclude the CL, #, or OT
characters. This enables the same table to be used regardless of how the rating is defined. In
the delivered PJS, these rating formats are used in accordance with the following criteria:
CLxxxx refers to an ANSI or API pressure rating
xxxx# refers to a pressure rating defined by an organization other than ANSI or API.
OTxxxx refers to the rating of a connect point that meets the applicable ANSI or API
rating geometrically but not from a pressure carrying standpoint. An example is a valve
supplied with flanged ends that meets the bolting pattern of ANSI CL150 pressure rating
but has pressure carrying characteristics different from those of that ANSI rating.
For bolts and gaskets, you must use a numeric pressure rating (do not use the
characters CL, #, or OT). If any character entries are encountered, the system will be unable
to locate the proper information.
Female ends for plastic pipe are usually defined in terms of schedule/thickness and not in
terms of rating. To make female ends for plastic pipe follow the rules for other female ends,
the applicable schedule/thickness is used as the value for rating. If such rating values consist
of alphanumeric characters, the system strips all alpha characters from the rating value and
uses only the numeric values in accessing the applicable tables.
If the rating in the PJS is expressed in terms of alphabetic characters only, the system uses
the characters in accessing the data tables. The names of the data tables include all the
alphabetic characters included in the PJS.
GRAVHD can be used to identify the rating for components rated to sustain a nominal
fluid head. This value can be used in the PJS and in the data tables.
OTHER can be used to identify a non standard rating value.
NONE can be used to identify the rating for components whose ends would normally
require the attribute rating as part of the table name, but for which a rating does not
apply. This value can be used in the PJS and in the data tables.
10. gcp_sch_thk, character(8)
This attribute identifies the schedule thickness value for the green connect point. This
parameter exist as alphanumeric data. (Refer to Wall Thickness and Branch Reinforcement
Equations (on page 141) for more information on this attribute.) In order of preference,
schedule, and thickness are expressed in terms of:
A generic schedule such as S-STD, S-XS, and S-XXS. If a schedule name exceeds the
provided field length (for example, S-SDR13.5), it is defined in terms of its wall
thickness.
A specific schedule such as S-40, S-40S, and S-80.
NREQD is used in cases where all of the following conditions apply:
The thickness value is not required in purchasing the component.
Empty weights are not significantly affected by actual thickness values.
Either stress analysis is not applicable, or, if applicable, the component is to be
considered infinitely rigid in stress analysis calculations.
A value with all numeric characters is interpreted as a wall thickness value in the same
physical units as nominal piping diameter. To insure compatibility between the PJS,
data tables, and wall thickness calculations, thickness is expressed in the form:

40 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

.xxxx if the thickness is less than 1 inch


x if the thickness is an even inch
x.xxx if the thickness is 1 inch or larger
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 (on page 141) 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.
11. gcp_table_suffix, short, SN 576
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.
12. rcp_from_nom_diam, short
13. rcp_to_nom_diam, short
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.
14. rcp_end_prep, short, SN 330
See gcp_end_prep.
15. rcp_rating, character(8)
See gcp_rating.
16. rcp_sch_thk, character(8)
See gcp_sch_thk.
17. rcp_table_suffix, short, SN 577
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.
A parametric definition is used when connection graphics are required in the model and
orthographic drawings.
18. commodity_code, character(16)
The commodity code is a user-assigned code that together with the NPD and
schedule/thickness uniquely defines the component. It defines the customer's commodity

Plant Design System (PDS) Reference Data Manager (PD_Data) 41


Piping Job Specification

code (or part number). This attribute is the index into the Material Data Tables and the
Material Description Library. The commodity code can be defined in one of three ways:
Commodity codes with neither an * or a + prefix, indicate a commodity item that has no
associated implied components.
Commodity codes prefixed by an *, indicate a commodity item (primary component)
which has one associated implied component (such as a lap joint flange and stub end).
For more information on defining * implied items, refer to the PD_Report User's Guide.
It is not recommended that specification implied (*) items be generated by
size change components (that is, reducers, reducing flanges, and so forth) as the NPD
assigned by the system for the implied component can be either the larger or smaller
(green or red) NPD of the implying item based on how the system traces the line.
Commodity codes prefixed by a +, indicate a commodity item (primary component)
which has one or more associated implied components as defined in Table 212.
The default length for a commodity code is 16 characters, but you can modify this length if
needed. This value is specified in two files: design.ddl and reference.ddl. To customize the
character length, modify the design.ddl file as follows:
In table 34 (Piping Component Data), modify the value in column 8.
In table 50 (Piping/Tubing Data), modify the value in column 12.
Modify the reference.ddl file as follows:
In table 202 (Piping Commodity Specification Data), modify the value in column 18.
In table 211 (Piping Commodity Size-Dependent Material Data), modify the values in
column 2 and column 7.
In table 212 (Piping Commodity Implies Material Data), modify the values in column 2
and column 7.
When you modify these values, set the character limit to be one more than the
number of characters you actually want in the commodity code. This is necessary for
you to add a * or + prefix if needed. For example, to create a 20-character commodity
code, set the specified values to 21.
You must make these modifications before the project is created.
For valves, the commodity code also defines the name of the dry weight table (required for
stress analysis). For large diameter valves (25"+), it is used to build the name of the operator
dimension table.
19. model_code, character(6)
This attribute identifies the specific item name for generic bends, spec flanges, or spec
valves. Each model code is classified by:
Item name
option
size ranges
end preparations
ratings

42 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

The model code includes the definition of the graphic representation of the component in the
piping model. Depending upon the circumstances:
One or more model codes can be assigned to a single Item Name (for example, GAT,
GATR, and GATF are all used for 6Q1C01).
The same model code can be assigned to different Item Names.
For gaskets, this attribute can be used to prioritize gasket entries in the Piping Materials
Class. The priority is set with a numeric value (integer or decimal) greater than zero. Non-
numeric values are ignored by MTO and not considered to be a priority selection. The
smaller the value the higher the priority. A value of 999999 is interpreted as an undefined
priority.
20. PDS_sort_code, character(6)
This field can be used to specify the length (in subunits) for Purchased length pipe, or to
specify the gasket diameter for gaskets. The gasket diameter table is used if the
pds_sort_code for the gasket spec entry is set to _GKT. The system uses the NPD to
determine the gasket inside and outside diameters.
If the pds_sort_code for the gasket spec entry is set to "_GKT", the gasket outside and
inside diameters are generated using the table gasket_commodity_code_GKT.TBL.
If the pds_sort_code for the gasket spec entry is not "_GKT", the gasket outside
diameter is equivalent to the NPD of the rated component and the gasket inside diameter
is undefined.
21. modifier, double
This attribute is used for pipe bends, elbows, miters, and valves. It has various uses
depending on the type of commodity item as defined below.
For pipe bends, it defines the bend radius of the pipe in terms of the numeric factor by
which the nominal diameter of the pipe is to be multiplied to obtain the bend radius.
For pipe, it defines the joint quality factor (E) times 100 to be used during branch
reinforcement calculations in those cases where the wall thickness is not calculated.
For orifice flanges and drip ring tees, it defines the number of taps to be provided. A
value of 1 defines a single tap. A value of 2 defines 2 taps, 180 degrees apart. A value
of negative 2 (-2) defines 2 taps, 90 degrees apart.
For nippolets and nipples, it defines the length of the component.
For reinforcing pads and welds, it defines whether data about the component is to be
derived from tables in the system (0) or from the user by prompting (1).
For gaskets, it defines the gasket thickness to be used in procuring the gasket. This is
the actual gasket thickness for MTO reports - not the compressed gasket thickness
(gasket separation), which is derived from the Piping Materials Class data.
For bolts, it defines whether the bolt is a stud bolt (0 or positive), or machine bolt
(negative). The absolute value of this modifier, which ranges from 0 to 5, determines
the applicable bolt extension.
For valves, it represents the code list number from CL550 (operator/actuator type) which
defines the symbol description and the source of the physical data for the valve operator.
If this value is a negative number (such as -3), the operator is not displayed when
placing the component.

Plant Design System (PDS) Reference Data Manager (PD_Data) 43


Piping Job Specification

22. geometric_standard, short, SN 575


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.
23. weight_code, short, SN 578
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.
24. fabrication_cat, short, SN 180
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).
25. materials_grade, short, SN 145
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.
26. standard_note_no_a, short, SN 499
27. standard_note_no_b, short, SN 499
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.
28. input_form_type, short, SN 990
This code-listed attribute defines the type of input form to be used to define data with the
Spec Writer command.

44 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Neutral File Format


The following is a partial listing of the sample neutral file for the Piping Commodity
Specification Data. Entries in this table should be sorted alphanumerically by commodity_name.
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.

Sample Files
A set of neutral file for US practice are delivered in the files
\win32app\ingr\rdusrdb\spec_data\*.pcd (one for each piping materials class specified in the
classes.pmc file).
A set of sample files depicting various options are delivered in the
\win32app\ingr\pddata\sample\data directory.
bend_tbl.pcd gasket.pcd pharmf.pcd
equiv_npd.pcd gskt_tbl.pcd pharmk.pcd
fluid_code.pcd metric_npd.pcd piplen_tbl.pcd
fpipe.pcd pharm.pcd thickness.pcd

Piping Specialty Specification Data (203)


This database table contains data for a specific specialty item. It is used to define those specialty
items which are used frequently by a particular company or installation. The specialty items are
defined for the entire project, they are not partitioned by Piping Materials Class.
The Piping Specialty Specification Data table contains 26 attributes.
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

Plant Design System (PDS) Reference Data Manager (PD_Data) 45


Piping Job Specification

2. piping_comp_no, character(20)
This attribute uniquely identifies the specialty component number. It is sometimes referred
to as Item Number.
3. model_code, character(6)
This attribute identifies the piping specialty name. This can be a Piping Job Specification
access name or a PDS commodity item name.
4. option_code, short, SN 400
This code-listed attribute identifies the option code which determines the search criteria.
This parameter enables you to request that the system retrieve the primary item, a secondary
item, or another special option from the Piping Job Specification. You can select the unique
options (as defined in standard note 400) from a form. If no option is specified at placement,
the primary item is used. Option 2 is reserved as the secondary item. This parameter is used
as a component override in the Piping Designer.
5. gcp_from_nom_diam, short (NPD Units)
6. gcp_to_nom_diam, short (NPD Units)
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point.
7. gcp_end_prep, short, SN 330
These attributes identify the end preparation for the green/red connect point. This value is
an intelligent code list. The system determines the termination type based on the range of
values:
2 - 199 bolted terminations
300 - 399 male terminations
400 - 599 female terminations
8. gcp_rating, character(8)
These attributes identify the pressure rating for the green/red connect point. This parameter
exists as alphanumeric data. The system interprets the first set of sequential numeric
characters as being the pressure rating value. (Refer to the description of pressure rating
under Piping Commodity Data for more information on standard formats.)
9. gcp_sch_thk, character(8)
These attributes identify the schedule or thickness value for the green/red connect point.
This parameter exist as alphanumeric data. (Refer to the description of schedule and
thickness for more information on standard formats.)
10. gcp_table_suffix, short, SN 576
These code-listed attributes identify the source of the generic dimensional data, such as
flange data or piping outside diameter data.
For AMS standards, it represents the table suffix for the connect point.
For DIN standards, it represents the piping outside diameter selection flag (reihe
number) for pipes and fittings.
11. rcp_from_nom_diam, short (NPD Units)

46 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

12. rcp_to_nom_diam , short (NPD Units)


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.
13. rcp_end_prep, short, SN 330
See gcp_end_prep.
14. rcp_rating, character(8)
See gcp_rating.
15. rcp_sch_thk, character(8)
See gcp_sch_thk.
16. rcp_table_suffix , short, SN 577
See gcp_table_suffix.
17. physical_data_id , character(8)
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.
18. PDS_sort_code, character(6)
This attribute can be used to define an arbitrary index to a geometric data table for piping
specialties. This is an optional input.
19. modifier, double
This attribute is used for pipe bends, elbows, and miters. It represents the bend radius in
terms of the nominal piping diameter.
20. geometric_standard , short, SN 575
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.
21. weight_code, short, SN 578
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.
22. fabrication_cat, short, SN 180
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).
23. materials_grade, short, SN 145
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.
24. standard_note_no_a, short, SN 499

Plant Design System (PDS) Reference Data Manager (PD_Data) 47


Piping Job Specification

25. standard_note_no_b, short, SN 499


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.
26. input_form_type, short, SN 990
This code-listed attribute defines the type of input form to be used to define data with the
Spec Writer command.

Neutral File Format

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.

Instrument Component Specification Data (204)


This table contains the data for a specific instrument item. It is used to define the instruments
which are used frequently by a particular company or installation. The instruments are defined
for the entire project; they are not partitioned by PMC. The following data exists in the
Instrument table.
The Instrument Component Specification Data table contains 26 attributes.
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.

48 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

3. model_code, character(6)
This attribute identifies the specific item name for generic bends, spec flanges, or spec
valves. This can be a Piping Job Specification access name or a PDS commodity item name.
Refer to the PDS Piping Component Data Reference Guide for more information on item
names.
4. option_code, short, SN 400
This code-listed attribute identifies the option code which determines the search criteria.
This parameter enables you to request that the system retrieve the primary item, a secondary
item, or another special option from the Piping Job Specification. You can select the unique
options (defined in a standard note) from a form. If no option is specified at placement, the
default option 1 is used. Option 2 is reserved as the secondary item. This parameter is used
as a component override in Piping Design.
5. gcp_from_nom_diam, short (NPD Units)
6. gcp_to_nom_diam , short (NPD Units)
These coded attributes identify the range of nominal piping diameters (low bound to high
bound) for the green connect point.
7. gcp_end_prep, short, SN 330
These code-listed attributes identify the end preparation for the green/red connect point. The
system determines the termination type based on the range of values:
2 - 199 bolted terminations
300 - 399 male terminations
400 - 599 female terminations
8. gcp_rating, character(8)
These attributes identify the pressure rating for the green/red connect point. This parameter
exists as alphanumeric data. The system interprets the first set of sequential numeric
characters as being the pressure rating value. (Refer to the description of pressure rating for
more information on standard formats.)
9. gcp_sch_thk, character(8)
These attributes identify the schedule thickness value for the green/red connect point. (Refer
to the description of schedule and thickness for more information on standard formats.)
10. gcp_table_suffix, short, SN 576
These code-listed attributes reference the source of the generic dimensional data, such as
flange data or piping outside diameter data.
For AMS standards, it represents the table suffix for the connect point.
For DIN standards, it represents the piping outside diameter selection flag (reihe
number) for pipes and fittings.
11. rcp_from_nom_diam, short (NPD Units)
12. rcp_to_nom_diam, short (NPD Units)
These coded attributes identify the range of nominal piping diameters (low bound to high
bound) for the red connect point. For a full size component, these parameters are set to zero.
13. rcp_end_prep, short, SN 330
See gcp_end_prep.

Plant Design System (PDS) Reference Data Manager (PD_Data) 49


Piping Job Specification

14. rcp_rating, character(8)


See gcp_rating.
15. rcp_sch_thk, character(8)
See gcp_sch_thk.
16. rcp_table_suffix, short, SN 577
See gcp_table_suffix.
17. physical_data_id , character(8)
This parameter can be used to reference the set of physical data from the Physical Data
Library to be used for this instrument item.
18. PDS_sort_code, character(6)
This attribute can be used to define an arbitrary index in the geometric data table for
instruments. This is an optional input.
19. modifier, double
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.
20. geometric_standard, short, SN 575
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.
21. weight_code, short, SN 578
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.
22. fabrication_cat, short, SN 180
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).
23. materials_grade, short, SN 145
This code-listed attribute identifies the material code, specification, grade-temper, and joint
efficiency for the instrument. It can be used to access physical data in the Piping Graphic
Commodity Library.
24. standard_note_no_a, short, SN 499
25. standard_note_no_b, short, SN 499
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.
In the delivered data, note numbers 800 through 999 are allocated for instruments.
26. input_form_type, short, SN 990
This code-listed attribute defines the type of input form to be used to define data with the
Spec Writer command.

50 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Neutral File Format

Sample Files
A sample neutral file is delivered in the file \win32app\ingr\pddata\sample\data\instrment.data.
A sample file containing various bio-pharmaceutical instruments is delivered in the file
\win32app\ingr\pddata\sample\data\pharmi.data.

Tap Properties Data (205)


This table contains the tap properties data that is a function of the tap properties table name and
the nominal piping diameter. These tables define the piping taps which can be added to any of
the components included in a piping materials class. The system uses the information in these
tables and the nominal diameter to provide values for rating, end preparation, schedule/thickness,
and tap code. Tap tables do not allow a NPD range; there must be an individual entry for each
tap diameter.
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:
! Diam Opt Rating Prp SC/Th Tap Code
10mm 1 - 591 NREQD E$37591XXX
20 691 - 591 NREQD E$37581XXX

The Tap Properties Data table contains 8 attributes.

Plant Design System (PDS) Reference Data Manager (PD_Data) 51


Piping Job Specification

The following kinds of taps may be defined in this table:


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 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
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.
4. option_code, short, SN 400
This code-listed attribute identifies the option code which determines the search criteria.
This parameter enables you to request that the system retrieve the primary item, a secondary
item, or another special option from the Piping Job Specification. 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.
5. end_preparation, short, SN 330
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, and so forth.
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.)

52 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

7. sched_thick, character(8)
This attribute identifies the generic or specific schedule, a thickness value, or a calculation.
(Refer to the description of schedule and thickness for Piping Commodity Data for more
information on standard formats.)
8. tap_material_code, character(10)
This optional attribute can be used to access the Material Description Library for the tap's
material description addendum. It must be a unique reference to the Material Description
Library, including material descriptions for commodity items. In reporting or isometric
extraction, this text can be appended to either the short or long descriptions of the
component to which the tap applies.
This attribute is also referred to as the Tap Code. Refer to the listing of the tap descriptions
in the Short Material Description Library (on page 277) for more information on the tap
commodity code.

Neutral File Format


6 8
Double_Spacing
Sequence= 3 4 6 5 7 8
! By=GJH Ckd By=RJW Rev=2 Date=12-May-1988

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

Plant Design System (PDS) Reference Data Manager (PD_Data) 53


Piping Job Specification

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
\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.

Piping Commodity Size-Dependent Material Data (211)


The Size-Dependent Data table contains the data for a specific commodity item that is dependent
on the commodity code, nominal piping diameter, and schedule/thickness.
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.
The Piping Commodity Size-Dependent Material Data table contains 10 attributes.
1. system_unique_no, integer
2. sys_commodity_code, character(16)
This parameter identifies the customer's 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 specific schedule such as S-40, S-60, and S-80.

54 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

NREQD is used if the thickness value is not required in purchasing the component,
empty weights are not significantly affected by actual thickness values, and stress
analysis is not applicable.
A value with all numeric characters is interpreted as a wall thickness value in the same
physical units as nominal piping diameter.
An asterisk (*) followed by a name (of the form Cyyy) defines the specific calculation or
table lookup to be used for wall thickness.
7. commodity_code, character(16), index 1
This attribute identifies the customer's commodity code or vendor's part number. It is not
required for the customer's commodity code if the customer's commodity code is not
dependent upon nominal piping diameter or thickness.
8. weld_weight, double
This parameter represents the total weld required at all welded ends of the commodity item.
9. unit_price, double
This attribute identifies the unit price (materials cost) for the commodity item.
10. manhours, double
This attribute identifies the unit manhours associated with the commodity item.

Neutral File Format

A sample neutral file is delivered in the file \win32app\ingr\pddata\sample\data\pcd_size.data.

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.

inputs (search criteria)


pointer to the commodity item dependent data
NPD green - first size
NPD red - second size
schedule/thickness - green connect point
schedule/thickness - red connect point

outputs
customer's commodity code or vendor's part number
weld data

Plant Design System (PDS) Reference Data Manager (PD_Data) 55


Piping Job Specification

price data (materials cost) - unit price


labor data - unit manhours

Piping Commodity Implied Material Data (212)


The Implied Material Data table contains the implied material data for a specific commodity
item that is dependent on both the 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 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 Piping Commodity Implies Material Data table contains 10 attributes.
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) User's 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 customer's 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.
NPD is defined as a special coded number 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.
coded number = 32*diameter + 5000 (in)
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 the English
System of Units.
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 '-'.

56 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

7. commodity_code , character(16) , index 1


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
This attribute identifies the quantity of the implied material.
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).
10. standard_note_no , short
This code-listed attribute provides index numbers to standard notes in CL499 that apply to
this implied material.

Plant Design System (PDS) Reference Data Manager (PD_Data) 57


Piping Job Specification

Neutral File Format

58 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Sample Files
A sample neutral file for US practice is delivered in the file
\win32app\ingr\rdusrdb\spec_data\implied.data.
A sample file containing various bio-pharmaceutical gasket data is delivered in the file
\win32app\ingr\pddata\sample\data\pharm_212.data.

Data Retrieval
Data retrieval from the Implied Material Data table involves implied material data for a
commodity item that is dependent on nominal piping diameter range. This form of data retrieval
is used during the MTO Report Creation process and Material Control.

inputs (search criteria)


pointer to the commodity item dependent data

outputs
Commodity code of the implied material
Quantity of the implied material
Fabrication category of the implied material
Standard note for the implied material

Component Insulation Exclusion Data (231)


The Component Insulation Exclusion Data is used to completely or partially exclude the
insulation of components on insulated lines with respect to interference checking.
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 component's interference envelope.
green nominal piping diameter of the component (range search)
red nominal piping diameter of the component (range search)
heat tracing requirements (range search)
insulation purpose (range search)
normal operating temperature (range search)
For piping commodities, the Piping Envelope Builder searches for the component's 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 component's interference envelope.
If the commodity name is not specified in the exclusion table for those conditions, the Piping
Envelope Builder searches for the component's 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 component's interference envelope.
Otherwise, the insulation thickness will be included in the component's interference
envelope.
For piping specialties and instrument components, the Piping Envelope Builder searches for the
component's model code in the Component Insulation Exclusion Data Table using the preceding

Plant Design System (PDS) Reference Data Manager (PD_Data) 59


Piping Job Specification

data. If the component is defined in the exclusion table for those conditions, the applicable
insulation thickness will not be added to the component's interference envelope. Otherwise, the
insulation thickness will be included in the component's interference envelope.
The piping segment data (heat tracing requirements, insulation purpose, and normal operating
temperature) are determined on the basis of the piping segment that is associated with the first
connect point of the applicable component.
The Component Insulation Exclusion Data table contains 13 attributes.
1. system_unique_no, integer
2. commodity_name, character(6)
This attribute identifies the commodity item name of a piping component as defined in the
Piping Commodity Specification Data (Table 202 attribute 3).
If this attribute is blank, the system will search for a match by model code.
3. model_code, character(6)
For piping commodities, this attribute identifies the model code as defined in the Piping
Commodity Specification Data (Table 202 attribute 19).
For piping specialties, this attribute identifies the model code as defined in the Piping
Specialty Specification Data (Table 203 attribute 3).
For instruments, this attribute identifies the model code as defined in the Instrument
Component Specification Data (Table 204 attribute 3).
4. gcp_npd_from, short
5. gcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point of the component or instrument in NPD units.
6. rcp_npd_from, short
7. rcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the red connect point of the component or instrument in NPD units.
For full size components, use a dash (-) for these attributes.
8. heat_tracing_from, short, SN 200
9. heat_tracing_to, short, SN 200
These code-listed attributes identify the range of heat tracing values (lower bound to higher
bound) using values from code list set 200, Heat Tracing Requirements.
A dash (-) can be used for the from value to indicate that heat tracing requirements are not to
be considered as part of the discrimination process.
10. insul_purpose_from, short, SN 220
11. insul_purpose_to, short, SN 220
These code-listed attributes identify the range of insulation purpose values (lower bound to
higher bound) using values from Standard Note type 220, Insulation Purpose.
A dash (-) can be used for the from value to indicate that insulation purpose is not to be
considered as part of the discrimination process.
12. nor_oper_temp_from , double

60 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

13. nor_oper_temp_to , double


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.

Neutral File Format

! DEFINE COMPONENT INSULATION EXCLUSION DATA


Single_Spacing
Sequence= 2 3 4 5 6 7 8 9 10 11 12 13
- I15AS 4 12 - - 3 3 5 5 150 200
6Q2C76 - 4 12 - - 3 3 5 5 150 200
- REDE 4 12 2 10 3 3 5 5 150 200

A sample neutral file is delivered in the file


\win32app\ingr\pddata\sample\data\component.data.

Flange Insulation Exclusion Data (232)


The Flange Insulation Exclusion Data provides for partial exclusion of flange insulation
thickness from the generation of interference envelopes. This is an optional data table; if no data
is defined for this table, the Piping Envelope builder will continue to function as it has in
previous releases of PDS.
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) (on page 59).
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.
nominal piping diameter of the bolted end (range search)
heat tracing requirements (range search)
insulation purpose (range search)
normal operating temperature (range search)
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 component's
interference envelope. Otherwise, the insulation thickness will be included in the component's
interference envelope.
The piping segment data (heat tracing requirements, insulation purpose, and normal operating
temperature) are determined on the basis of the piping segment associated with the first connect
point of the applicable component.

Plant Design System (PDS) Reference Data Manager (PD_Data) 61


Piping Job Specification

The Piping Eden modules for the interference envelopes that are to consider the
partial exclusion of insulation from the flange outside diameter of a bolted end must be
revised to accommodate this option. If you do not change any or all of the Piping Eden
modules for the interference envelopes, this table will have no impact and the interference
envelopes will include complete insulation, when applicable.
For example, the required modification to the interference parametric for the weldneck
flange (FWN) is as follows:
!FLANGE - Interference Module
Interference_Parametric_Shape_Definition 'F1A'
Call Define_Connect_Point_Geometry ( LINEAR )
Thickness_1 = Thickness_1 + CP_Offset_1
Thickness_2 = Thickness_2 + CP_Offset_2
!Original Line
! Facing_OD_1 = Facing_OD_1 + Insulation * 2
!Modified Line
Facing_OD_1 = Facing_OD_1 + Insulation_1 * 2
Facing_OD_2 = Facing_OD_2 + Insulation * 2
Call Draw_Cylinder ( Thickness_1, Facing_OD_1 )
Call Draw_Cylinder ( Thickness_2, Facing_OD_2 )
RETURN
END
The Flange Insulation Exclusion Data table has 9 attributes.
1. system_unique_no, integer
2. bolted_npd_from, short
3. bolted_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the bolted end of the component or instrument in NPD units.
4. heat_tracing_from, short, SN 200
5. heat_tracing_to, short, SN 200
These code-listed attributes identify the range of heat tracing values (lower bound to higher
bound) using values from code list set 200, Heat Tracing Requirements.
A dash (-) can be used for the from value to indicate that heat tracing requirements are not to
be considered as part of the discrimination process.
6. insul_purpose_from, short, SN 220
7. insul_purpose_to, short, SN 220
These code-listed attributes identify the range of insulation purpose values (lower bound to
higher bound) using values from Standard Note type 220, Insulation Purpose.
A dash (-) can be used for the from value to indicate that insulation purpose is not to be
considered as part of the discrimination process.
8. nor_oper_temp_from, double
9. nor_oper_temp_to, double
These attributes identify the range of temperature values (lower bound to higher bound) for
the bolted end of the component or instrument.

62 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

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.

Neutral File Format

! DEFINE FLANGE INSULATION EXCLUSION DATA


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

Piping Construction Tolerance Exclusion Data (233)


The Piping Construction Tolerance Exclusion Data can be used to completely or partially
exclude construction tolerance from the generation of interference envelopes. This feature only
applies to Piping vs. Piping construction tolerances.

This is an optional data table; if no data is defined for this table, the Piping Envelope builder will
continue to function as it has in previous releases of PDS.
For each piping or instrument component, excluding pipes, the Piping Envelope Builder searches
Table 233 on the basis of the following data to determine whether the Piping versus Piping
construction tolerance should be excluded from that component's interference envelope.
green NPD of the component (range search)
red NPD of the component (range search)
For piping commodities, the Piping Envelope Builder searches for the component's commodity
name in the Piping Construction Tolerance Exclusion Data Table using the preceding data.
If the piping commodity is defined in the exclusion table for those conditions, the applicable
construction tolerance will not be added to the component's interference envelope.
If the commodity name is not specified in the exclusion table for those conditions, the Piping
Envelope Builder will search for the component's model code using the same data. If a
match for those conditions is found on the basis of the model code, the applicable
construction tolerance will not be added to the component's interference envelope.
Otherwise, the construction tolerance will be included in the component's interference
envelope.

Plant Design System (PDS) Reference Data Manager (PD_Data) 63


Piping Job Specification

For piping specialties and instrument components, the Piping Envelope Builder searches for the
component's model code in the Piping Construction Tolerance Exclusion Data Table using the
preceding data. If the component is defined in the exclusion table for those conditions, the
applicable construction tolerance will not be added to the component's interference envelope.
Otherwise, the construction tolerance will be included in the component's interference envelope.
The Piping Construction Tolerance Exclusion Data table has 7 attributes.
1. system_unique_no, integer
2. commodity_name, character(6)
This attribute identifies the commodity item name of a piping component as defined in the
Piping Commodity Specification Data (Table 202 attribute 3).
If this attribute is blank, the system will search for a match by model code.
3. model_code, character(6)
For piping commodities, this attribute identifies the model code as defined in the Piping
Commodity Specification Data (Table 202 attribute 19).
For piping specialties, this attribute identifies the model code as defined in the Piping
Specialty Specification Data (Table 203 attribute 3).
For instruments, this attribute identifies the model code as defined in the Instrument
Component Specification Data (Table 204 attribute 3).
4. gcp_npd_from, short
5. gcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the green connect point of the component or instrument in NPD units.
6. rcp_npd_from, short
7. rcp_npd_to, short
These coded attributes identify the range of nominal piping diameters (lower bound to
higher bound) for the red connect point of the component or instrument in NPD units.
For full size components, use a dash (-) for these attributes.

Neutral File Format

! PIPING CONSTRUCTION TOLERANCE EXCLUSION DATA


Single_Spacing
Sequence= 2 3 4 5 6 7
- I15AS 4 12 - -
6Q2C76 - 4 12 - -
- REDE 4 12 2 10

A sample neutral file is delivered in the file \win32app\ingr\pddata\sample\data\constol.data.

64 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Spec Writer
This command provides a forms interface for interactively creating, revising, and managing the
following specification data. This interface provides more simplicity and flexibility to a beginner
or a casual user than defining specs with their respective neutral files:
Piping Materials Class Data (201) (on page 34)
Piping Commodity Specification Data (202) (on page 38)
Piping Specialty Specification Data (203) (on page 45)
Instrument Component Specification Data (204) (on page 48)
Tap Properties Data (205) (on page 51)
Piping Commodity Implied Material Data (212) (on page 56)

See Also
Features (on page 65)
RDB Options File (on page 66)

Plant Design System (PDS) Reference Data Manager (PD_Data) 65


Piping Job Specification

Features
The Spec Writer provides the following general features:
User-specified options for customizing the input of data (RDB_options).
A direct interface to the unapproved Specification Material Reference Database.
On-line validation for the existence of a material description, once the commodity code (or
component number) has been defined.
Optional on-line Table Checker validation using pre-defined Table Checker reports.
Automated selections from the Standard Note Library for code-listed data. The approved
Standard Note Library must have been defined to include the correct data for use in the
Material Reference Database.
Selectable list of acceptable model codes for a specified commodity name.
Context-sensitive user interface. The form options will vary depending on the item being
defined. For example, the creation (and revision) of specification data for bolts and gaskets
will display only those inputs relevant for bolts or gaskets.
Context-sensitive on-line help that is linked to the Piping Component Data Reference Guide
and the Reference Data Manager Reference Guide.

RDB Options File


The RDB Options File allows you to customize the data input operations for the Interactive Spec
Writer. You should define an RDB options list, named RDB_options in the project directory. A
default RDB options list is included in the PD_Data sample/data/ directory.
! 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
!

66 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

MODEL_CODE = LIST
VALVE_OPERATOR = LIST
!
!
COMMODITY_NAME<===>MODEL_CODES
!
! Pipe/Tube
PIPING = PIPE, TUBE
!
! Valves (6Q1C)
!
6Q1C01 = GATSP, GAT, GATF, GATR
6Q1C02 = GATEX, GATEXB, GATEXBB
6Q1C03 = GATCON
6Q1C04 = GATBL
!
! Generic 3-way
6Q1C05 = BAL3P, GLO3W, PLU3W, SLI3W, 3WRV1
!
6Q1C06 = BALF, BALR, BALSP, BALLP, BALVP
6Q1C08 = BAL3P
6Q1C11 = GLOSP, GLO, GLOF, GLOR
6Q1C12 = GLOASP, GLOA
6Q1C13 = GLO3W
6Q1C14 = GLOY, GLOYF, GLOYR
6Q1C16 = PLUSP, PLU, PLUVP, PLUFB, PLUF, PLUR
6Q1C18 = PLU3W
6Q1C19 = PLU4W
6Q1C22 = NEE
6Q1C26 = BFYLP, BFYHP
6Q1C30 = DIA, DIASP, DIAPL, DIAGL
6Q1C32 = KNF
6Q1C33 = SLI
6Q1C34 = SLI3W
6Q1C37 = CKALSP, CKAL, CKST, BDA, HOSA
6Q1C38 = CKLSP, CKSSP, CKL, CKLF, CKLR, CKS, CKSF, CKSR, CKSY, CKLRY
6Q1C39 = CKWF, CKWFSP
6Q1C40 = CKALSP, CKAL
6Q1C41 = CKST
6Q1C42 = CKAST
6Q1C43 = CKYST
6Q1C50 = CKBP
6Q1C51 = CKAR
6Q1C53 = BDA
6Q1C54 = BDY
6Q1C56 = PIN
6Q1C57 = FLO
6Q1C58 = FOOT
6Q1C62 = TKDR
6Q1C69 = DEL
6Q1C72 = HOS
6Q1C73 = HOSA
!
! Generic Vent/Drain Valve

Plant Design System (PDS) Reference Data Manager (PD_Data) 67


Piping Job Specification

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

68 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

!
! Generic <45 Degree Direction Change
6Q2C55 = E5, E11, E22, E45TLR, PIPB, PIPB2
!
! Generic 45 Degree Direction Change
6Q2C56 = E45LR, E45, PIPB, PIPB2, E45LT, E453D, E45T3D, E45U, E45ST,
E45S, E45L, M451, M452
!
6Q2C57 = E45
6Q2C59 = E45LR, E45TLR
6Q2C60 = E45LT
6Q2C61 = E453D, E45T3D
6Q2C63 = E45U
6Q2C65 = E45ST
6Q2C66 = E45S
6Q2C68 = E45L
6Q2C73 = E60
!
! Generic 45-90 Degree Direction Change
6Q2C75 = E90TLR, PIPB, PIPB2
!
! Generic 90 Degree Direction Change
6Q2C76 = E90LR, E90, E90SR, E90LT, E90R, E903D, E903T3D, E90U, E90ST,
E90RST, E90S, E90L, PIPB, PIPB2, E90LT, M901, M902, M903, M904
!
6Q2C77 = E90
6Q2C79 = E90SR
6Q2C80 = E90LR, E90TLR
6Q2C82 = E90LT
6Q2C84 = E90R
6Q2C86 = E903D, E903T3D
6Q2C88 = E90U
6Q2C90 = E90ST
6Q2C91 = E90RST
6Q2C93 = E90S
6Q2C94 = E90L
!
! On-line Fittings (6P3C) and In-line Fittings (6Q3C)
!
6Q3C01 = R180
6Q3C03 = R180SR
6Q3C05 = R180LR
6Q3C07 = R180CL
6Q3C08 = R180MD
6Q3C09 = R180OP
6Q3C14 = M1, M2, M3, M4
6Q3C16 = M451, M452
6Q3C18 = M901, M902, M903, M904
6Q3C22 = T, TBT
6Q3C24 = TRB, TRBT
6Q3C25 = TRRB
6Q3C27 = TUOR
6Q3C28 = TUOB
6Q3C31 = TST

Plant Design System (PDS) Reference Data Manager (PD_Data) 69


Piping Job Specification

6Q3C34 = TRI
6Q3C36 = TDRA, TDRAW, TDRB, TDRBW
6Q3C38 = TBA
6Q3C45 = Y
6Q3C47 = L
6Q3C49 = LRB
6Q3C50 = LRRB
6Q3C52 = S90YB
6Q3C53 = S90YRB
6Q3C54 = L90YB
6Q3C55 = L90YRB
6Q3C60 = X
6Q3C62 = XRB
6Q3C63 = XRRB
6Q3C64 = XBA
6Q3C70 = SAD
6Q3C72 = SWOL
6Q3C73 = WOL
6Q3C74 = SOL
6Q3C75 = TOL
6Q3C76 = NOL
6Q3C77 = EOLLR, EOLSR
6Q3C78 = LOL
6Q3C79 = FOLHC
6Q3C80 = RPAD, RPAD2
6Q3C82 = RWELD, RWELD2
6Q3C84 = BWELD, BWELD2, BWELD3
6Q3C88 = NIP
6Q3C89 = NIPIL
!6Q3C95 = GASKET
!6Q3C97 = STUD
!6Q3C98 = NUT
!
!
!
VALVE_OPERATOR_LIST
!
! Handwheels
!
OP_0 = None Required
OP_3 = Handwheel
OP_4 = Handwheel if GCP>RCP
OP_5 = Handwheel, inclined
OP_9 = Wrench, short
OP_11 = Wrench, long
OP_17 = Lever
OP_19 = T-handle, short
OP_21 = T-handle, long
OP_25 = Handwheel, special
OP_27 = Wrench, special
OP_29 = Gear, top mounted handwheel
OP_31 = Gear, top mounted inclined handwheel
OP_33 = Gear, side mounted handwheel
OP_35 = Gear, side mounted inclined handwheel

70 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

OP_39 = Lever, quick-action


OP_40 = Post indicator
!
! Actuators
!
OP_411 = Diaphragm, type 1
OP_412 = Diaphragm, type 2
OP_413 = Diaphragm, type 3
OP_431 = Press-balanced diaphragm type 1
OP_432 = Press-balanced diaphragm type 2
OP_433 = Press-balanced diaphragm type 3
OP_451 = Regulator type 1
OP_452 = Regulator type 2
OP_453 = Regulator type 3
OP_491 = Single acting cylinder type 1
OP_492 = Single acting cylinder type 2
OP_493 = Single acting cylinder type 3
OP_511 = Doulble acting cylinder type 1
OP_512 = Doulble acting cylinder type 2
OP_513 = Doulble acting cylinder type 3
OP_531 = Pilot operated cylinder type 1
OP_532 = Pilot operated cylinder type 2
OP_533 = Pilot operated cylinder type 3
OP_534 = Pilot operated cylinder type 4
OP_571 = Motor type 1
OP_572 = Motor type 2
OP_573 = Motor type 3
OP_574 = Motor type 4
OP_611 = Digital type 1
OP_651 = Electro-hydraulic type 1
OP_652 = Electro-hydraulic type 2
OP_811 = Weight type 1
OP_851 = Manual type 1
OP_852 = Manual type 2
OP_853 = Manual type 3
OP_854 = Manual type 4
OP_891 = Spring type 1
END_VALVE_OPERATOR_LIST

You can use the following keywords to customize the settings in the RDB options file.

General Items
For piping commodities, you can verify that a material description has been defined in the Short
Material Description Library and/or the Long Material Description Library. For piping
specialties and instruments, you can verify that a material description has been defined in the
Specialty Material Description Library.
SHORT_COMMODITY_MATERIAL_DESCRIPTION = ON or OFF If set to ON, the short
material description is displayed when you specify the commodity code.
If this keyword is not specified in the RDB options file, the default setting is OFF.
LONG_COMMODITY_MATERIAL_DESCRIPTION = ON or OFF If set to ON, the long
material description is displayed when you specify the commodity code.

Plant Design System (PDS) Reference Data Manager (PD_Data) 71


Piping Job Specification

If this keyword is not specified in the RDB options file, the default setting is OFF.
SPECIALTY_MATERIAL_DESCRIPTION = ON or OFF If set to ON, the specialty
material description is displayed when you specify the commodity code.
If this keyword is not specified in the RDB options file, the default setting is OFF.

PDtable_201 items
SERVICE_LIMITS_TABLE = LIST, <prefix> If set to LIST, a list of Service Limits
Tables (as defined in the approved Piping Job Specification Table Library) is displayed.
You must specify a prefix to use as a substring search to determine the list of tables. (Use L
for the delivered tables.)
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
NOMINAL_PIPING_DIAMETER_TABLE = LIST, <prefix> If set to LIST, a list of
Nominal Piping Diameter Tables (as defined in the approved Piping Job Specification Table
Library) is displayed. You must specify a prefix to use as a substring search to determine
the list of tables. (Use D for the delivered tables.)
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
BRANCH_TABLE = LIST, <prefix> If set to LIST, a list of Branch Tables (as defined
in the approved Piping Job Specification Table Library) is displayed. You must specify a
prefix to be used as a substring search to determine the list of tables. (Use B for the
delivered tables.) The list is filtered to only include the unique tables, where the branch
angle is 90 degrees.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
You should not assign the same Branch Table to be used in two different piping
materials classes if, for example, one allows intersections at both 45 degrees and 90 degrees,
and the other only allows 90 degree intersections. The Reference Data Manager will not
detect this problem.
TAP_PROPERTIES_TABLE = KEYIN or DATABASE If set to DATABASE, a list of Tap
Properties Data Tables (as defined in PDtable_205 of the unapproved Material Reference
Database) is displayed.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
GASKET_SEPARATION_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of
Gasket Separation Tables (as defined in the approved Piping Job Specification Table
Library) is displayed. You must specify a prefix to be used as a substring search to
determine the list of tables. (Use G for the delivered tables.)
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
When listing the Gasket Separation Tables, the list of tables is restricted to unique
names, excluding the underbar (_) and the pressure rating value that follows. In other words,
the list of Gasket Separation Tables will not include the pressure rating (G001 instead of
G001_1500).

72 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

THICKNESS_DATA_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of


Thickness Data Tables (as defined in the approved Piping Job Specification Table Library)
is displayed. You must specify a prefix to be used as a substring search to determine the list
of tables. (Use T 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.
MATERIALS_DATA_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of
Materials Data Tables (as defined in the approved Piping Job Specification Table Library) is
displayed. You must specify a prefix to be used as a substring search to determine the list of
tables. (Use M 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.
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.
FLUID_CODE_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of Fluid
Code Tables (as defined in the approved Piping Job Specification Table Library) is
displayed. You must specify a prefix (such as FC) to be used as a substring search to
determine the list of tables.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
MATERIALS_DESCRIPTION = KEYIN or LIST If set to LIST, a list of materials
descriptions (as defined in the approved Standard Note Library) is displayed.
If this keyword is not specified in the RDB options file, the default mode is to key in the
value.
BEND_DEFLECTION_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of
Bend Deflection Tables (as defined in the approved Piping Job Specification Table Library)
is displayed. You must specify a prefix to be used as a substring search to determine the list
of tables.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
PIPE_LENGTH_TABLE = KEYIN or LIST, <prefix> If set to LIST, a list of Pipe
Length Tables (as defined in the approved Piping Job Specification Table Library) is
displayed. You must specify a prefix to be used as a substring search to determine the list of
tables.
If this keyword is not specified in the RDB options file, the default mode is to key in the
table name.
STANDARD_NOTE = KEYIN or LIST If set to LIST, a list of standard notes (as defined
in the approved Standard Note Library) is displayed.
If this keyword is not specified in the RDB options file, the default mode is to key in the
value of the standard note.

Plant Design System (PDS) Reference Data Manager (PD_Data) 73


Piping Job Specification

PDtable_202 items
MODEL_CODE = KEYIN or LIST If set to LIST, a list of acceptable model codes
(determined by the commodity name) is displayed. (See keyword COMMODITY_NAME
<===> MODEL_CODES for more information.)
If this keyword is not specified in the RDB options file or the list of acceptable model codes
is not defined, the default mode is to key in the value.
VALVE_OPERATOR = KEYIN or LIST If set to LIST, a list of valve operator types (as
defined in the RDB options file) is displayed. (See keyword VALVE_OPERATOR_LIST for
more information.)
If this keyword is not specified in the RDB options file or the list of valve operator types is
not defined, the default mode is to key in the value.
PROMPT_FOR_TAP_ORIENTATION This keyword is used if you require that all (or some)
orifice flanges have two taps oriented 90 degrees apart. By default orifice taps are oriented
180 degrees apart on the outside diameter of the flange.
If this keyword is not included in the RDB options list, the relative tap orientation for two
taps will always be 180 degrees.
COMMODITY_NAME <===> MODEL_CODES This keyword precedes the list of
associations between commodity names and their acceptable model codes. This list must be
defined to use the LIST option for MODEL_CODE.
The association between a commodity name and the acceptable model codes for that
commodity name is defined as follows.
<commodity_name> = <model_code_A>,<model_code_B>, ...
6Q1C01 = GATSP, GAT, GATF, GATR
6Q1C02 = GATEX, GATEXB, GATEXBB
You can define as many as 50 model codes, separated by a comma, for each commodity
name.
The delivered RDB options list includes a list of acceptable model codes for the reference
data provided with PDS.
VALVE_OPERATOR_LIST This keyword precedes the list of valve operator types and
their corresponding descriptions.
The list of valve operator types is defined as follows.
<valve operator type> = <description>
OP_0 = None Required
OP_3 = Handwheel
The delivered RDB options file includes a list of valve operator types for the reference data
provided with PDS. The description is for information only to aid the user in selecting the
proper valve operator type.
END_VALVE_OPERATOR_LIST This keyword must follow the valve operator list as a
delimiter.

74 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Piping Materials Class Data Command


The Piping Materials Class Data command can be used to create a piping materials class
definition in Table 201 of the Material Reference Database or revise and existing piping
materials class definition.

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.

Create/Revise Piping Materials Class Data


The Create/Revise Piping Materials Class Data form is used to create or modify the definition of
a piping materials class. When creating a new definition, the system will jump to the input fields
for the mandatory data. You must specify a value for all the mandatory fields.

Plant Design System (PDS) Reference Data Manager (PD_Data) 75


Piping Job Specification

The system highlights the mandatory input fields (those that must be specified). Once you define
a valid input for a mandatory field the system will drop the highlight for that field.
Refer to RDB Options File (on page 66) for information on defining list options for the
applicable input fields.
Refer to Piping Materials Class Data (201) (on page 34) for more information on the attributes
for the Piping Materials Class Data table (201).

Mandatory Input Fields


Piping Materials Class (keyin) Key in up to 16 alphanumeric characters for the piping
materials class to be defined. The system verifies that specified piping materials class does
not already exist in the Unapproved Material Reference Database.
Gasket Separation (keyin) Key in the value for the gasket separation for this piping
materials class.
OR
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

76 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

angle is 90 degrees. For more information, see Bends and Tee-type Branches and Branch
Components in Piping Design Reference Guide.

The 90 degree button only works if a Branch Table exists.


You should not assign the same Branch Table to two different piping materials classes
if, for example, one allows intersections at both 45 degrees and 90 degrees, and the other
only allows 90 degree intersections. The Reference Data Manager will not detect this
problem.
You can place components without a Branch Table; you simply select the components
using the individual component buttons.
The Branch Table is the primary choice for picking branching components because of
the engineering calculations required.
Sometimes you can override the Branch Table based on company rules or the Stress
Group requirement. For example, the Branch Table can be overridden by not selecting
the 90 degree button and then selecting any other branching component. However, doing
so without direction from the rules or the Stress Group is a violation on the codes or
standards.
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.

Optional Data - Wall Thickness


This data is required for piping commodities, where the schedule or thickness is not explicitly
defined in the piping materials class or in a wall thickness table.
Corrosion Allowance (keyin) Key in a numeric value, if wall thickness calculations are
to be used.
Thickness Equation (list) Select one of the displayed wall thickness equations.
ANSI B31.3-1987 EL01
ANSI B31.1a-1986 EJ01
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).
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).

Plant Design System (PDS) Reference Data Manager (PD_Data) 77


Piping Job Specification

Optional Data
The following data is not required and can be defined or not defined based on your company
practices.
Materials Description (keyin or list) Key in the numeric value for the materials
description in the Standard Note Library for this piping materials class or select from the list
of materials descriptions (as defined in the approved Standard Note Library).
Revision (keyin) Key in up to two alphanumeric characters for the revision number.
Revision Date (keyin) Key in up to ten alphanumeric characters for the date. The
current date will not be entered automatically.
Note that the Reference Data Manager creates and maintains a separate revision
management date on the basis of the current date and time which can be used in the
reporting of reference data.
Fluid Code (keyin list) Define a default fluid code to be used for the piping materials
class.
OR
Fluid Code Table (keyin list) Key in the name of the Fluid Code Table for this piping
materials class or select from a list of Fluid Code Tables (as defined in the approved Piping
Job Specification Table Library).
Materials of Construction (keyin) Key in up to six alphanumeric characters.
Bend Deflect Table (keyin or list) Key in the name of the Bend Deflection Table for this
piping materials class or select from a list of Bend Deflection Tables (as defined in the
approved Piping Job Specification Table Library).
Pipe Length Table (keyin or list) Key in the name of the Pipe Length Table for this
piping materials class or select from a list of Pipe Length Tables (as defined in the approved
Piping Job Specification Table Library).
Standard Note Number (keyin or list) Key in the note number in the Standard Note
Library for this piping materials class or select from the list of standard notes (as defined in
the approved Standard Note Library).

78 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Piping Commodity Data Command


The Piping Commodity Data command can be used to create a piping commodity definition in
Table 202 of the Material Reference Database or revise an existing piping commodity definition.

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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 79


Piping Job Specification

Source and Destination Piping Materials Class - These are active fields that, when selected,
display the piping materials class list. Select the source piping materials class from the
displayed list, and then select Accept. Select the destination piping materials class from the
displayed list and select Accept.

Select All - This option copies the specification data for all piping commodities within the
selected source piping materials class to the specified destination piping materials class.
Select From List - Select the source piping materials class from the displayed list and select
Accept. Select the destination piping materials class from the displayed list and select Accept.
Then select the piping commodity to be copied from the list of all piping commodities within the
source piping materials class.
Select Gaskets - Select the source piping materials class from the displayed list and select
Accept. Select the destination piping materials class from the displayed list and select Accept.
The system copies the specification data for all gaskets within the source piping materials class
to the destination piping materials class. Gaskets are recognized on the basis of the gasket
commodity name, as specified through the Project Data Manager.
Select Bolts - Select the source piping materials class from the displayed list and select Accept.
Select the destination piping materials class from the displayed list and select Accept. The
system copies the specification data for all bolts within the source piping materials class to the
destination piping materials class. Bolts are recognized on the basis of the bolt commodity
name, as specified through the Project Data Manager.
Short Commodity Material Description ON/OFF You can set this toggle to ON to
verify that the material description for a specified commodity code has been defined in the
Short Material Description Library.

80 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

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.

If the Material Description toggle is set to ON and no corresponding material description is


found for a specified commodity code, the system activates the Add Entry to Material
Description Library form. See Add Entry to Material Description Library (on page 88).

Create/Revise Piping Commodity Specification Data


The Create/Revise Piping Commodity Specification Data form is used to create or modify the
definition of a piping commodity within a specified piping materials class. When creating a new
definition, the system will jump to the input fields for the mandatory data. You must specify a
value (by keyin or selection from a list) for all the mandatory fields.

Refer to RDB Options File (on page 66) for information on defining options for the applicable
input fields.
Refer to Piping Commodity Specification Data (202) (on page 38) for information on the
attributes for the Piping Commodity Specification Data table.

Plant Design System (PDS) Reference Data Manager (PD_Data) 81


Piping Job Specification

Where possible, the system verifies that the specified value is valid for the applicable piping
materials class. For example, NPD values are checked against the associated diameters table in
the approved Piping Job Spec Table Library.
Commodity Type This field can be used to select the type of piping commodity data to
be created based on the settings in Standard Note Type 990 of the Standard Note Library.
General Fittings Piping
Pipe Bends Tubing
Orifice Flanges Gaskets
Branch Nipples Bolts
Branch Reinforcement Nuts
Valves
The system will modify the form fields to reflect the data that is specific to that type of
component. The system stores the commodity type as the input_form_type within the Piping
Commodity Specification Data Table of the Material Reference Database.
Any input fields that are not used for a specific piping commodity type will be de-activated.
The General Fittings category will allow input in all the input fields. This form is used for
any piping commodity that does not fall within any of the other types.

General Fittings, Pipe Bends, Orifice Flanges, Branch Nipples, Branch Reinforcement, and
Valves
Commodity Name (keyin)
From NPD - First Size (keyin)
To NPD - First Size (keyin)
End Preparation - First Size (list)
Pressure Rating - First Size (keyin) This data is automatically set to undefined (blank)
for the branch reinforcement commodity type.
Table Suffix - First Size (list)
Schedule/Thickness - First Size (list) Attribute 10. This data is automatically set to
undefined (blank) for the branch reinforcement commodity type.
Commodity Code (keyin) Key in the commodity code for the piping commodity. When
size-dependent commodity codes are required, this will represent a system commodity code
and will be used by the Report Manager to reference the size-dependent commodity code in
the Piping Commodity Size-Dependent Material Data Table.
The system automatically translates the specified commodity code to be upper-case.
You can use the Implied Data option to specify implied data for this piping commodity.
Refer to Commodity Implied Data Command (on page 98) for information on project-
specific implied data. Refer to Implied Data (on page 87) for information on class-specific
implied data. The default is that implied data does not apply.
For the revise command, the prefixes for implied data are not displayed as part of the
commodity code, although the prefix will be loaded in the database. For implied data
(project-wide or class-specific), the system will display the toggle setting rather than
showing the prefix in the commodity code field.

82 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Model Code (keyin or list) Attribute 19. Key in the model code or select the model code
from a list of acceptable model codes (as defined by commodity name in the RDB options
file).
Geometric Industry Standard (list)
Weight Code (list)
fabrication category (list)
Define the following data for any reducing components. This data will not apply to either the
orifice flange or branch nipple commodity type.
From NPD - Second Size (keyin) Attribute 12. Key in the lowest second size for which
this specification data applies.
To NPD - Second Size (keyin) Attribute 13. Key in the highest second size for which
this specification data applies.
You can optionally define the following fields when two ends of that component require
different data. By PDS convention, if you specify a red End Preparation, you must specify the
corresponding pressure rating, table suffix, and schedule/thickness.
End Preparation - Second Size (list)
Pressure Rating - Second Size (keyin) This data is set to undefined (blank) for the
branch reinforcement commodity type.
Table Suffix - Second Size (list)
Schedule/Thickness - Second Size (list) This data is set to undefined (blank) for the
branch reinforcement commodity type.
The following data must be defined for the designated [component types]. The setting is stored
in the modifier attribute.
Bend Radius (keyin) [Pipe Bend] Key in the bend radius for the pipe bend.
Number of Taps (toggle) [Orifice Flanges] Set the toggle for the number of taps (1 or
2) on the orifice flange. If applicable, set the orientation of the taps as 90 degrees or 180
degrees. This toggle only appears for orifice flanges that have two taps.
Nipple Length (keyin) [Branch Nipples] Key in length of the branch nipple.
Reinforcement Data (toggle) [Branch Reinforcement] Set the toggle for the source of
the branch reinforcement data to By System or By User.
If you select the by user branch reinforcement option, the commodity option code is
automatically defined with a value of 699 (User-defined), as required by PDS.
Valve Operator (keyin or list) [Valves] Key in the valve operator type or select the
valve operator type from a list of valve operator types. The list of valve operator types and
the corresponding descriptions are defined in the RDB options list.
Valve Operator Display (toggle) [Valves] Set the toggle to ON or OFF to determine
whether the valve operator is displayed in the model.
Modifier (keyin) You can define this value for specific piping commodities not covered
by the previous list.
You can define the following optional data depending on your requirements.
Commodity Option (list) Attribute 4.
Max Temperature (keyin) Attribute 5. If no value is specified, the default value
(undefined) is assigned automatically.
Materials Grade (list) Attribute 25.

Plant Design System (PDS) Reference Data Manager (PD_Data) 83


Piping Job Specification

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.

Specification Data for Piping


You must define the following data for piping. The piping commodity name is defined
automatically, as specified through the Project Data Manager.
From NPD - First Size (keyin)
To NPD - First Size (keyin)
End Preparation (list)
Pressure Rating (keyin)
Table Suffix (list)
Schedule/Thickness (list)
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.
Commodity Code (keyin)
Model Code (toggle) Set the toggle to By System (PIPE) or By User (*FPIPE).
Geometric Industry Standard (list)
Weight Code (list)
Fabrication Category (list)
You can optionally define the following data for piping.
End Preparation - Second Size (list)
Commodity Option (list)
Max Temperature (keyin)
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.
Materials Grade (list)
Standard Note Number (list)
End Preparation - Other (list)

84 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Specification Data for Tubing


Define the following data for tubing. The tubing commodity name is defined automatically, as
specified through the Project Data Manager.
From NPD - First Size (keyin)
To NPD - First Size (keyin)
End Preparation - First Size (list)
Pressure Rating - First Size (keyin)
Table Suffix - First Size (list)
Schedule/Thickness - First Size (list)
Joint Quality Factor (keyin)
Commodity Code (keyin)
Geometric Industry Standard (list)
Weight Code (list)
Fabrication Category (list)
You can optionally define the following data for tubing.
End Preparation - Second Size (list)
Commodity Option (list)
Maximum Temperature (keyin)
E, Reinforcement (keyin)
Purchased Length (keyin)
Materials Grade (list)
Standard Note Number (list)
End Preparation - Other (list)

Specification Data for Gaskets


Define the following data for gaskets. The gasket's commodity name is defined automatically,
as specified through the Project Data Manager. The system displays the active project's
selection of MTO options applicable to gaskets for reference.
From NPD - First Size (keyin)
To NPD - First Size (keyin)
End Preparation - First Size (list)
Pressure Rating - First Size (keyin)
Table Suffix - First Size (list)
Commodity Code (keyin)
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 Pressure Rating (keyin) Key in up to eight characters to define the pressure
rating.
Alternate Table Suffix (list) Select from the list of table suffix values as defined in the
approved Standard Note Library.

Plant Design System (PDS) Reference Data Manager (PD_Data) 85


Piping Job Specification

You can optionally define the following data on the basis of the user-specific requirements for
gaskets.
Commodity Option (list)
Max Temperature (keyin)
Fabrication Category (list)
Materials Grade (list)
Standard Note Number (list)

Specification Data for Bolts


You must define the following data for bolts. The bolt's commodity name is defined
automatically, as specified through the Project Data Manager. The system displays the active
project's selection of MTO options applicable to bolts for reference.
From NPD - First Size (keyin)
To NPD - First Size (keyin)
Pressure Rating - First Size (keyin)
Table Suffix - First Size (list)
Commodity Code (keyin)
Bolt Extension (keyin)
You can optionally define the following data on the basis of user-specific requirements for bolts.
Commodity Option (list)
Fabrication Category (list)
Materials Grade (list)
Standard Note Number (list)

Specification Data for Nuts


You must define the following data for nuts. The commodity name is defined automatically, as
specified through the Project Data Manager.
Max Temperature (keyin)
Commodity Code (keyin)
You can optionally define the following data on the basis of user-specific requirements for nuts.
Fabrication Category (list)
Materials Grade (list)
Standard Note Number (list)

List of Piping Materials Classes Form


This form displays when you click any of the following commands:
Select Piping Materials Class. For more information, see Discrimination Data Form (on
page 303).
Create or Revise by List in the Piping Commodity Data Command. For more information,
see Piping Commodity Specification Data (PDtable_202) (see "Piping Commodity Data
Command" on page 78).
Select a Piping Materials Class by placing a data point over an entry in the list and selecting
Accept.

86 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Implied Data
When defining a piping commodity, you can select the Implied Data option to indicate that the
commodity will have an associated implied item that will be included in MTO reports. After
selecting the option, set the toggle to Class Specific.
This option is intended for implied components that are not unique within the project. A lap-
joint flange is an example of the primary component, where the stub-end is the implied
component.
Refer to Commodity Implied Data Command (on page 98) for information on Project Specific
implied data.
When you select Accept to define a primary component, the system modifies the form display to
allow you to define the specification data for the implied component.

When you accept the specification data for the implied component, the system prefixes an
asterisk (*) to the commodity code of the primary component to indicate that implied data is
present.
The following specification data for the implied component are determined by the corresponding
data for the primary component. This data is displayed in review only fields.
Commodity Name Same as the primary component.
Commodity Option The commodity option code for the implied component is set to the
primary component's commodity option code plus 5000.
From NPD same as the primary component.
To NPD same as the primary component.
Model Code same as the primary component.

Plant Design System (PDS) Reference Data Manager (PD_Data) 87


Piping Job Specification

You can optionally define the following specification data for the implied component based on
your reporting requirements. The values for the implied component default to the corresponding
values for the primary component, except for the commodity code.
End Preparation (list)
Pressure Rating (keyin)
Table Suffix (list)
Schedule/Thickness (list)
Commodity Code (keyin) Key in the commodity code for the implied item. The system
converts this value to upper-case.
When size-dependent commodity codes are required, this will represent a somewhat
arbitrary value, referred to as the system commodity code, and will be used by the Report
Manager to reference the size-dependent commodity code.
Geometric Industry Standard (list)
Weight Code (list)
Fabrication Category (list)
Modifier (keyin)
Max Temperature (keyin)
Materials Grade (list)
Standard Note Number (list)
PDS Sort Code (keyin) (optional). The system converts the value to upper-case.

Add Entry to Material Description Library


This form is used to define the material description for a specified commodity code in the
appropriate Material Description Library (short, long, or specialty). Refer to Material
Description Data (on page 273) for more information on material descriptions.

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.

88 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

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.

Piping Specialty Data Command


The Piping Specialty Data command can be used to create a piping specialty definition in Table
203 of the Material Reference Database or revise an existing piping specialty definition. You can
also add specialty descriptions to the Material Description Library.

Create Select the type of specialty (Piping Specialty or Valves) from the list. Then key
in the component number for the specialty item to be created and select Accept. The system
activates the Create Piping Specialty Specification Data form.
Revise By Keyin Key in the component number of the specialty to be modified and
select Accept. The system activates the Revise Piping Specialty Specification Data form
with the data for the selected piping specialty.
Revise By List Select the piping specialty to be revised from the displayed List of Piping
Commodities and select Accept. The system activates the Revise Piping Specialty
Specification Data form with the data for the selected piping specialty.

Plant Design System (PDS) Reference Data Manager (PD_Data) 89


Piping Job Specification

Specialty Material Description You can set this toggle to ON to verify that the material
description for a specified commodity code has been defined in the Specialty Material
Description Library.

If no corresponding material description is found, the system activates the Add Entry to
Material Description Library form. See Add Entry to Material Description Library (on page
88).

Create/Revise Piping Specialty Specification Data


The Create/Revise Piping Specialty Specification Data form is used to create or modify the
definition of a piping commodity within a specified piping materials class. When creating a new
definition, the system will jump to the input fields for the mandatory data. You must specify a
value (by keyin or selection from a list) for all the mandatory fields.

Refer to RDB Options File (on page 66) for information on defining options for the applicable
input fields.
Refer to Piping Specialty Specification Data (203) (on page 45) for information on the attributes
for the Piping Specialty Specification Data table.

Mandatory Input Fields


Piping Component Number (keyin) Key in the piping component number, which
uniquely identifies the piping specialty. The system verifies that the piping component
number does not already exist in the Unapproved Material Reference Database.

90 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

From NPD - First Size (keyin) Key in the first size value for the piping specialty. Both
the from and to values are loaded on the basis of this input.
To NPD - First Size (keyin) Key in the first size value for the piping specialty. Both the
from and to values are loaded on the basis of this input. The TO NPD field is only visible if
an applicable specialty type is selected.
End Preparation - First Size (list) Select from the list of end preparation values as
defined in the approved Standard Note Library.
Pressure Rating - First Size (keyin) Key in up to eight characters to define the pressure
rating.
Table Suffix - First Size (list) Select from the list of table suffix values as defined in the
approved Standard Note Library.
Schedule/Thickness (list) Select from the list of schedule/thickness values as defined in
the approved Standard Note Library.
Model Code (keyin) Key in the model code to be used to parametrically define the
piping specialty.
Physical Data ID (keyin) Key in the ID to be used as an arbitrary index into the
geometric data table for piping specialties.
Sort Code (keyin) Key in the sort code to be used as an arbitrary index into the
geometric data table for piping specialties. The system will convert the value to upper-case.
Fabrication Category (list) Select from the list of fabrication category values as defined
in the approved Standard Note Library.
You must define the following data for any reducing component.
NPD - Second Size (keyin) Key in the second size value for the piping specialty. Both
the from and to values are loaded on the basis of this input.
You must define the following data for valves. This data is stored in the modifier attribute.
Valve Operator (keyin or list) Key in the valve operator type or select the valve
operator type from a list of valve operator types (as defined in the RDB options file).
Valve Operator Display ON/OFF (toggle) Set the toggle to determine whether the
valve operator will be displayed in the model.
Specialty Type (field) This field can be used to select the type of piping specialty data to
be created based on settings in Standard Note Type 990 of the Standard Note Library. Place
a data point in this field to activate the Spec Writer Data Form Type pick list, then select
the preferred data type.

The system stores the specialty type as the input_form_type within the Piping Specialty Data
Table as a code-listed attribute for Standard Note Type 990.

Plant Design System (PDS) Reference Data Manager (PD_Data) 91


Piping Job Specification

Optional Input Fields


You can optionally define the following data, when two ends of the component require different
data. By PDS convention, if you specify the red end preparation, you must specify the
corresponding pressure rating, table suffix, and schedule/thickness.
End Preparation (list)
Pressure Rating (keyin)
Table Suffix (list)
Schedule/Thickness (list)
You can optionally define the following data depending on you requirements for piping
specialties.
Weight Code (list)
Geometric Industry Standard (list)
Modifier (keyin)
Materials Grade (list)
Standard Note Number (list)

Instrument Data Command


The Instrument Data command can be used to create an instrument definition in Table 204 of
the Material Reference Database or revise an existing instrument definition. You can also add
descriptions to the Material Description Library.

Create Select the type of instrument (Instruments or Valves) from the list. Then key in
the component number for the instrument to be created and select Accept. The system
activates the Create Instrument Specification Data form.
Revise By Keyin Key in the component number of the instrument to be modified and
select Accept. The system activates the Revise Instrument Specification Data form with the
data for the selected instrument.
Revise By List Select the instrument to be revised from the displayed List of Instruments
and select Accept. The system activates the Revise Instrument Specification Data form with
the data for the selected instrument.
Specialty Material Description You can set this toggle to ON to verify that the material
description for a specified commodity code has been defined in the Specialty Material
Description Library.

92 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

If no corresponding material description is found, the system activates the Add Entry to
Material Description Library form. See Add Entry to Material Description Library (on page
88).

Create/Revise Instrument Specification Data


The Create/Revise Instrument Specification Data form is used to create or modify the definition
of an instrument. hen creating a new definition, the system will jump to the input fields for the
mandatory data. You must specify a value (by keyin or selection from a list) for all the
mandatory fields.

Refer to RDB Options File (on page 66) for information on defining options for the applicable
input fields.
Refer to Instrument Component Specification Data (204) (on page 48) for information on the
attributes for the Instrument Specification Data table.
Instrument Component Number (keyin) Key in the component number, which
uniquely identifies the instrument. The system verifies that the component number does not
already exist in the Unapproved Material Reference Database.
From NPD - First Size (keyin) Key in the first size value for the instrument. Both the
from and to values are loaded on the basis of this input.
To NPD - First Size (keyin) Key in the first size value for the instrument. Both the from
and to values are loaded on the basis of this input. The TO NPD field is only visible if an
applicable instrument type is selected.
End Preparation - First Size (list) Select from the list of end preparation values as
defined in the approved Standard Note Library.
Pressure Rating - First Size (keyin) Key in up to eight characters to define the pressure
rating.

Plant Design System (PDS) Reference Data Manager (PD_Data) 93


Piping Job Specification

Table Suffix - First Size (list) Select from the list of table suffix values as defined in the
approved Standard Note Library.
Schedule/Thickness (list) Select from the list of schedule/thickness values as defined in
the approved Standard Note Library.
Model Code (keyin) Key in the model code to be used to parametrically define the
instrument.
Physical Data ID (keyin) Key in the ID to be used as an arbitrary index into the
geometric data table for instruments.
Sort Code (keyin) Key in the code to be used as an arbitrary index into the geometric
data table for instruments. The system will convert the value to upper-case.
Fabrication Category (list) Select from the list of fabrication category values as defined
in the approved Standard Note Library.
You must define the following data for any reducing component.
NPD - Second Size (keyin) Key in the second size value for the instrument. Both the
from and to values are loaded on the basis of this input.
Instrument Type (field) This field can be used to select the type of instrument
component data to be created based on settings in Standard Note Type 990 of the Standard
Note Library. Place a data point in this field to activate the Spec Writer Data Form Type
pick list, and then select the preferred data type.

The system stores the specialty type as the input_form_type within the Piping Specialty Data
Table as a code-listed attribute for Standard Note Type 990.
You can optionally define the following data when two ends of the component require different
data. By PDS convention, if you specify the red end preparation, you must specify the
corresponding pressure rating, table suffix, and schedule/thickness.
End Preparation (list)
Pressure Rating (keyin)
Table Suffix (list)
Schedule/Thickness (list)
You must define the following data for valves. This information is stored in the modifier
attribute.
Valve Operator (keyin or list) Key in the valve operator type or select the valve
operator type from a list of valve operator types (as defined in the RDB options file).
Valve Operator Display ON/OFF (toggle) Set the toggle to determine whether the
valve operator will be displayed in the model.

94 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

You can optionally define the following data depending on your requirements for instruments.
Weight Code (list)
Geometric Industry Standard (list)
Modifier (keyin)
Materials Grade (list)
Standard Note Number (list)

Tap Properties Data Command


The Tap Properties Data command can be used to create a tap properties definition in Table
205 of the Material Reference Database or revise and existing tap properties definition.

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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 95


Piping Job Specification

Create/Revise Tap Properties Data


The Create/Revise Tap Properties Data form is used to create or modify the specification data for
taps. When creating a new definition, the system will jump to the input fields for the mandatory
data. You must specify a value for all the mandatory fields.

Refer to RDB Options File (on page 66) for information on defining list options for the
applicable input fields.
Refer to Tap Properties Data (205) (on page 51) for more information on the attributes for the
Tap Properties Data.
Tap Table Name (keyin) Key in up to six characters for the table name. The combination of
the tap properties table name, the tap nominal piping diameter, and the tap option code must be
unique.
Nom Piping Diameter (keyin) Key in the nominal piping diameter for this tap
properties definition.
Tap Option (list) Select from the list of tap option codes as defined in the approved
Standard Note Library. If you do not select a tap option code, the default value (one) is
assigned automatically.
End Preparation (list) Select from the list of end preparation values as defined in the
approved Standard Note Library.
Rating (keyin) Key in up to eight characters to define the pressure rating.
Schedule/Thickness (list) Select from the list of schedule/thickness values as defined in
the approved Standard Note Library.
Tap Material Code (keyin) During the tap properties data creation process, if the Short
and Long Commodity Description toggles are set to ON, you are allowed to insert Tap
Material Code data into the Short Material Description Library. This is the code that may

96 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

optionally be used by MTO for appending the tap's material description to that of the
component which has been tapped.
If you have defined size-dependent commodity codes, this option will be ignored, unless
both of the following conditions are met:
The option for MTO to use the system commodity code to reference the material
description has been enabled through the Material Takeoff Options of the Project Data
Manager.
The material descriptions have been created with embedded commodity code labels as
the means of inserting the size-dependent data into the material description.
This form is used to define the material description for a specified commodity code in the
appropriate (short) Material Description Library. Refer to Material Description Data (on page
273) for more information on material descriptions.

Key in the material description for the specified commodity code and select Accept. This code
must be a unique index into the project's Material Description Libraries.
The system converts the specified tap material code to upper-case, and then adds the specified
entry into the appropriate Material Description Libraries.

Plant Design System (PDS) Reference Data Manager (PD_Data) 97


Piping Job Specification

Commodity Implied Data Command


The Commodity Implied Data command defines the specification data for implied components
in Table 212 or the Material Reference Database. These implied components are reported by
MTO with the primary component in situations where the implied data is independent of the
piping materials class (used throughout the project).

Create Key in the system commodity code of the implied component to be created. The
system activates the Create Piping Commodity Implied Material Data form.
Revise By Keyin Key in the name of the piping materials class for the commodity item
to be modified. Then select the piping commodity to be revised from the displayed List of
Piping Commodities and select Accept. The system activates the Revise Piping Commodity
Specification Data form with the data for the selected piping commodity.
Revise By List Select the implied component definition to be revised from the displayed
list of Commodity Implied Data and select Accept. The system activates the Revise Piping
Commodity Implied Data form with the data for the implied component definition.

Create/Revise Piping Commodity Implied Material Data


The Create/Revise Piping Commodity Implied Material Data form is used to create or modify
the definition of an implied component. When creating a new definition, the system will jump to
the input fields for the mandatory data. You must specify a value (by keyin or selection from a
list) for all the mandatory fields.

98 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Refer to RDB Options File (on page 66) for information on defining list options for the
applicable input fields.
Refer to Piping Commodity Implied Material Data (212) (on page 56) for more information on
the attributes for the Piping Commodity Implied Material Data table.
System Commodity Code Key in the commodity code for the primary component. The
system converts the value to upper-case.
For this type of implied data to be reported with the primary component, the specification
data for the primary component must have enabled the option in each piping materials class
for which this implied data applies.
From Diameter (First Size) Key in the lowest first size value for which this implied
specification data applies.
To Diameter (First Size) Key in the highest first size value for which this implied
specification data applies. The to value must equal or exceed the from value.
From Diameter (Second Size) For reducing components, key in the lowest second size
value for which this implied specification data applies. In cases where the piping
commodity represents both a full-size component and a reducing component, this value
should equal the corresponding first size NPD. Otherwise, for a reducing component, this
value must be less than the corresponding first size value.
To Diameter (Second Size) For reducing components, key in the highest second size
value for which this implied specification data applies. The to value must equal or exceed
the from value.
Commodity Code (keyin) During the commodity implied data creation process, if the
Short and Long Commodity Description toggles are set to ON, you are allowed to insert
Commodity Code data into the Short and Long Material Description Libraries.
If you have defined size-dependent commodity codes, this option will be ignored, unless
both of the following conditions are met:

Plant Design System (PDS) Reference Data Manager (PD_Data) 99


Piping Job Specification

The option for MTO to use the system commodity code to reference the material
description has been enabled through the Material Takeoff Options of the Project Data
Manager.
The material descriptions have been created with embedded commodity code labels as
the means of inserting the size-dependent data into the material description.
This form is used to define the material description for a specified commodity code in the
appropriate Material Description Library (short or long). Refer to Material Description
Data (on page 273) for more information on material descriptions.

Key in the material description for the specified commodity code and select Accept. This
code must be a unique index into the project's Material Description Libraries.
The system converts the specified commodity code to upper-case, then adds the specified
entry into the appropriate Material Description Libraries.
Quantity (keyin) Key in a whole number or a decimal value for the quantity of the
implied component per primary component.
Fabrication Category (list) Select from the list of fabrication category values as defined
in the approved Standard Note Library.
Standard Note Number (list) You can optionally select from the list of standard notes
as defined in the approved Standard Note Library.
Select a Piping Material Class commodity and click Accept.

100 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Table Checker
You can use the Table Checker option to perform on-line Table Checker validation for the
defined piping commodity specification data. When this option is enabled, table checker
validation will be performed for all piping commodities, except:
implied data specific to the piping materials class
gaskets
bolts
nuts
When you enable this option, the system displays a list of the defined Table Checker reports for
the project. Select the report validation to be performed and select Accept.

Refer to Table Checker Form (on page 298) for more information on creating a Table Checker
report definition.

Piping Job Specification Manager


This command enables you to load all of the database tables which make up the Piping Job
Specification portion of the Material Reference Database. You can also extract neutral files of
the data contained in the Material Reference Database.

Before Using This Command


Refer to the Project Administrator Reference Guide for information on creating a project and
creating the approved and unapproved Specification/Material Reference Database.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 101


Piping Job Specification

Operating Sequence
1. Select the Piping Job Specification Manager option from the Reference Data Manager
form.
The system displays the Piping Job Specification Manager main form used to select the type
of data to process.

The data manipulation procedure for each of the database tables is similar. You can perform
the following activities for each of the entities.
2. Select Option

102 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Select Unapprove ==> Approve to post the data from the unapproved
Specification/Material Reference Database to the approved database.

Accept to Create New Records or Exit


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, and then select AM or PM.
OR
Select the command for the database table to be loaded.
The system displays the options for the selected item. The following illustration reflects the
screen for Piping Materials Class.

Select Option

Plant Design System (PDS) Reference Data Manager (PD_Data) 103


Piping Job Specification

Select the option for the type of action to be performed.


Load, Replace, or Replace Commodity Subset (see "Load, Replace, or Replace Commodity
Subset Options" on page 104) from a neutral file.
Delete existing entries. For more information, see Delete Option (on page 106).
Report on the entity data (create a neutral file). For more information, see Report Option (on
page 107).
The manipulation procedure for each of type of piping data (listed below) is similar. See Piping
Job Specification Manager (on page 101).
Piping Material Class Data (Piping Materials Class Data (201) (on page 34))
Piping Commodity Data (Piping Commodity Specification Data (202) (on page 38))
Piping Specialty Data (Piping Component Tables for Specialty Components (on page 266))
Instrument Data (Instrument Component Specification Data (204) (on page 48))
Tap Properties Data (Tap Properties Data (205) (on page 51))
Size Dependent Material Data (Piping Commodity Size-Dependent Material Data (211)
(on page 54))
Project Implied Material Data (Piping Commodity Implied Material Data (212) (on page
56))
Component Insulation Exclusion Data (Component Insulation Exclusion Data (231) (on
page 59))
Flange Insulation Exclusion Data (Flange Insulation Exclusion Data (232) (on page 61))
Construction Tolerance Exclusion Data (Piping Construction Tolerance Exclusion Data
(233) (on page 63))
Pipe Support Group Data (Pipe Support Group Reference Data)
Pipe Support Commodity Data (Pipe Support Commodity Reference Data Table 241)
Pipe Support Material Data (Pipe Support Material Reference Data Table 242)
Pipe Support Material Description (Pipe Support Material Description Data Table 243)
Depending on the selected data, all or a few of the options below are available.
Load, Replace, or Replace Commodity Subset Options (on page 104)
Delete Option (on page 106)
Report Option (on page 107)

Load, Replace, or Replace Commodity Subset Options


These options enable you to load entries from a neutral ASCII file into the Material Reference
Database.
The Replace Commodity Subset option is only available for the Size Dependent
Material Data and Project Implied Material Data commands.
Refer to Material Reference Database Structure (on page 29) for a list of database tables and
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.

104 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Replace Commodity Subset revises (deletes and replaces) previously created size-
dependent or implied commodity data for a specific commodity or group of commodity
codes specified in a neutral file. This option is only available for the Size Dependent
Material Data and Project Implied Material Data commands.
The neutral files for the delivered USRDB data are in the directory
\win32app\ingr\rdusrdb\spec_data
classes.pmc the neutral file for the Piping Materials Class Data.
*.pcd The neutral files for the Piping Commodity Data are stored in a set of files of the
format pmcname.pcd. (For example, 1c0031.pcd defines all the commodity items for
piping materials class 1c0031.)
list.pcd a file that lists the neutral file names of all the delivered pcd files for the different
piping materials classes.
taps.data the neutral file for Tap Properties Data.
implied.data the neutral file for Project Implied Material Data.
A set of sample neutral files are delivered in the directory
\win32app\ingr\pddata\sample\data
specialty.data --- a sample neutral file for Piping Specialty Data.
instrment.data --- a sample neutral file for Instrument Data.
pcd_size.data --- a sample neutral file for Size Dependent Material Data.
You can copy the files and make changes before loading the information into the database.

Before Using This Command


You can define the variable PDS_COMMIT_INTERVAL= in the control.sh file to control the
commit interval in loading specification data into the Material Reference Database. This has the
same impact as adjusting the -c option in a risload command line. The default commit value is
25. Increasing this variable may improve performance.

Operating Sequence
1. Select the Load/Replace (or other load or replace) option. See the description above for
differences in Load, Replace, and Replace Commodity Subset.
2. Specify Neutral File Name
Key in the file specification for the neutral file that contains the data to be copied.
For Piping Commodity Data, you can load or replace a single file or a list of files. To
process a list of files, create a list file which lists each neutral file on a separate line. The
file list.pcd contains a list of all the delivered neutral files.
For Size-Dependent or Implied Commodity Data, you can replace specific commodity
codes or all the entries in the database. To replace specific commodity codes, create a
neutral file which contains only the commodity codes to be replaced.

Plant Design System (PDS) Reference Data Manager (PD_Data) 105


Piping Job Specification

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.

3. Set the toggle to Submit Immediately or Delayed Submit.


For Delayed Submit, set the time to process the neutral file(s).
4. Accept to Create New Records or Exit
Select Accept to begin processing the request.
Job Has Been Submitted
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.
pmc.log Piping Materials Class Data
pcd.log Piping Commodity Data
specialty.log Piping Specialty Data
instrument.log Instrument Data
taps.log Tap Properties Data
pcd_size.log Size-Dependent Material Data
implied.log Project Implied Material Data
These log files contain the following information.
The name of the neutral file being loaded
The completion status of the load (successful or unsuccessful)
The line number that caused the failure if the neutral file was not loaded.

Delete Option
This option enables you to delete entries from the Piping Job Specification.

Operating Sequence
1. Select the Delete option.

106 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

The system displays a list of all the items in the database for the selected class of data.

2. Select the item to be deleted from the database.


3. Accept to Delete Materials Class
Select Accept to begin deleting the data.

Report Option
The Report options enable you to create neutral files using the information in the
Specification/Material Reference database. The order and field lengths of the data in the neutral
file is determined by a format file named spec_order.max. This format file is expected to reside
in the same network address and directory specified for the report output. A default format file
is delivered with the PD_Data product in the file
\win32app\ingr\pddata\sample\format\spec_order.max. If the spec_order.max file is not found
at the specified output directory, the system will use the default spec order.
If an unapproved Specification/Material Reference database exists for the active project, you can
select the database to process: approved or unapproved.

Operating Sequence
1. Select the Report option from one of the data forms (such as the Piping Commodity Data
form).
For Piping Commodity Data, select the appropriate PCD from the list.
2. Specify Neutral File Name
Key in the name of the neutral file to be created. You can change the Node Name and File
Path information.
3. Set the toggle to Submit Immediately or Delayed Submit.
For Delayed Submit, set the time to process the neutral file(s).

Plant Design System (PDS) Reference Data Manager (PD_Data) 107


Piping Job Specification

4. Accept to Create Report


Select Accept to create the specified neutral file.
Job Has Been Submitted
The system creates the neutral file and a log file named specmgr.log.

Example spec_order.max File

!
! This file contains the spec attribute order and their maximum
attribute
! lengths required for creating spec output neutral files. When
creating
! spec reports the system will default an attribute order and set of
! attribute lengths. The user can edit these attribute orders and
! lengths in this file ( spec_order.max ). If this file is in the
! directory where the software is being run the orders defined in
! this file will be used as the default attribute order and lengths.
201 = 2,16 3,3 4,3 5,10 6,7 7,7 8,8 9,6 10,6 11,6 12,6 13,6 14,6 15,6
16,6 17,6 18,8 19,6 20,6
202 = 3,6 4,6 5,7 6,6 7,6 8,6 9,8 10,8 11,8 12,8 13,8 14,8 15,8 16,8
17,6 18,16 19,6 20,6 21,7 22,6 23,6 24,6 25,6 26,6 27,6
203 = 2,20 3,6 4,6 5,8 6,8 7,6 8,8 9,8 10,6 11,8 12,8 13,8 14,8 15,8
16,6 17,8 18,6 19,7 20,6 21,6 22,6 23,6 24,6 25,6
204 = 2,20 3,6 4,6 5,8 6,8 7,6 8,8 9,8 10,6 11,8 12,8 13,8 14,8 15,8
16,6 17,8 18,6 19,7 20,6 21,6 22,6 23,6 24,6 25,6
205 = 3,8 4,6 5,8 6,8 7,8 8,10
211 = 2,16 3,8 4,8 5,8 6,8 7,16 8,8 9,8 10,8
212 = 2,16 3,8 4,8 5,8 6,8 7,16 8,8 9,6 10,6

108 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Piping Job Spec Report Manager


This command activates the Piping Job Spec Report Manager form. It is used to generate
reports from the Specification/Material Reference Database with the report definition data. The
Piping Job Spec Report Manager stores the report record and location records for each
discrimination data file and format file in the Project Control Database. The numbered records
are used to locate ASCII files on their specified nodes.

Report Format Displays the Report Format form, which you can use to create, revise,
copy, or delete the record of a format file (not the format file). For more information, see
Report Format Form (on page 111).
Report Discrimination Data Displays the Discrimination Data form, which you can
use to create, revise, copy, or delete the record of a discrimination data file as well as the file
itself. For more information, see Report Discrimination Data Form (on page 114).
Report Displays the Report form, which you can use to create, revise, delete, and
approve report records and report files. For more information, see Report Form (on page
119).
Report Management Data Displays the Report Management Defaults form, which
you can use to create a record in the project control database of the default nodename and
path for the report definition files. This option is primarily used for setup. For more
information, see Report Management Defaults Form (on page 128).

Plant Design System (PDS) Reference Data Manager (PD_Data) 109


Piping Job Specification

Using the Report Commands


Understanding Report Files and Records
The Piping Job Spec Report Manager uses the discrimination data files, format files, and
database records that represent these files to generate reports. The following definitions explain
all of the files and records in the reporting process.

Format File and Record


The format file is a user-defined, ASCII file which must be created with a text editor outside of
the Piping Job Spec Report Manager. It contains special indices identifying what data appears
in the report and how the data is sorted. It also defines how the data is formatted in the report.
Without the format file(s), Piping Job Spec Report Manager reports cannot be processed. A
set of basic format files is delivered for each type of reporting.
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.

Discrimination Data File and Record


The discrimination data file limits the report to only the specified database occurrences. It is an
ASCII file that is created interactively using the Piping Job Spec Report Manager.
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.

Report Output and Record


The Piping Job Spec Report Manager creates a report using the specified format,
discrimination, and search criteria data files, and places it in the specified directory on the
specified node.
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.)

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.

110 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Finally, use the Report option to create the actual report.

Report Format Form


When you select the Report Format option from the Piping Job Spec Report Manager form,
the Report Format form is displayed.

This form enables you to create, copy, revise, or delete a record of the location of the format file
in the project control database. An option is also provided that enables you to copy a record and
its corresponding ASCII format files.
The format file defines the data that will be reported and the way in which that data will be
displayed. Reports cannot be generated unless a format file exists and a record of the file's
location has been entered into the project control database.
Create Displays the Format Creation/Revision form, which enables you to add a new
record of a format file in the project control database. For more information, see Format
Creation/Revision Form (on page 112).
Copy Displays the Format Creation/Revision form, which copies the record of an
existing format file from the project control database along with the corresponding ASCII
format file. For more information, see Format Creation/Revision Form (on page 112).
Revise Displays the Format Creation/Revision form, which modifies a record of an
existing format file in the project control database. For more information, see Format
Creation/Revision Form (on page 112).
Delete Displays the Deletion form, which deletes an existing record of a format file from
the project control database. If the record of the format file is deleted, reporting cannot be
performed. For more information, see Format Deletion Form (on page 113).

Plant Design System (PDS) Reference Data Manager (PD_Data) 111


Piping Job Specification

Format Creation/Revision Form


When you select Create, Copy, or Revise from the Report Format form, the Piping Job Spec
Report Manager form is displayed.

This form creates, copies, or revises a record in the project control database; this record defines
the location of a format file. The format file itself defines the contents and format of the report.
Both the location specification and the format file must exist to report on PDS data.
Number A unique number of up to 24 characters. Specifies the short name in the project
control database used to identify the record of the format file.
Description A description of up to 40 characters for the format file.
File Specification The file name of the format file to reference.
File Path The disk location of the format file. This field retains the active setting.
File Node The nodename of the system on which the format file is located. This field
retains the active setting.

Before Using this Form


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 a description of each of the delivered sample format files, see PDS Report Manager.

Operating Sequence
1. Select Create, Copy, or Revise.
A list of available records displays for copy or revision. To create a database record, go to
Step 3.
2. Select Report Format
3. From the displayed list, select the record to be copied or revised. Then select Accept.
Key-in fields are displayed for you to specify the required database information.
4. Specify Report Format Data

112 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Type information in each of the displayed fields, taking care to press Enter in each field.
Then select Accept.
The project control database is updated.

Format Deletion Form


When you choose Delete, the Deletion form is displayed.

This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.

Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.

Plant Design System (PDS) Reference Data Manager (PD_Data) 113


Piping Job Specification

Report Discrimination Data Form


When you select Report Discrimination Data from the Report Manager form, the
Discrimination Data form is displayed.

This form creates, copies, revises, and deletes a discrimination data file from the specified
directory. The associated record in the project control database is also copied, revised, or
deleted as needed.
A discrimination data file is an ASCII file that designates which models will be included in a
report. That is, discrimination data specifies the scope of the report. The project control
database record specifies the name and location of the discrimination data file that is to be
associated with a specific report.
Create Displays the Discrimination Data Creation form, which creates a new
discrimination data file. The associated project control database record is also created. For
more information, see Discrimination Data Creation Form (on page 115).
Copy Displays the Discrimination Data Revision form, which copies an existing data
file. The associated project control database record is also copied. For more information,
see Discrimination Data Revision Form (on page 117).
Revise Displays the Discrimination Data Revision form, which modifies discrimination
data. You can use this option to revise the contents of the discrimination data file, the
location of the discrimination file, and the associated record in the project control database.
For more information, see Discrimination Data Revision Form (on page 117).
Delete Displays the Deletion form, which deletes a discrimination data file as well as its
associated record in the project control database. For more information, see Discrimination
Data Deletion Form (on page 119).

114 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Discrimination Data Creation Form

Commands
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Search Criteria Defines search criteria for specified attributes in the
Specification/Material Reference Database. For more information, see Search Criteria
Form (on page 116).

Field Descriptions
Number --- Key in a unique number to name the discrimination data record to be created by
discrimination. The number can be up to 24 characters in the Project Control Database.
This number is a short name to identify the record of the discrimination data file.
Description --- Key in a description of the discrimination data file with up to 40 characters
in the Project Control Database.
File Specification --- Key in the filename of the discrimination data file to create.
The system verifies that the file does not already have a record in the project.
File Path --- Displays the disk location of the discrimination data file. This field retains the
active setting.
File Node --- Displays the nodename where the discrimination data file is located. This field
retains the active setting.

Plant Design System (PDS) Reference Data Manager (PD_Data) 115


Piping Job Specification

Search Criteria Form


You can define search criteria to restrict the elements to be reported based on database attributes.
The default is no search criteria. This option enables you to define search criteria for specified
attributes in the Spec Database.
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
Select the database entity that contains the data to be restricted.
The system displays the attributes for the selected entity.

3. Select Attribute
Select the attribute to be restricted.

116 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

The system displays the selected attribute and displays a list of operators.

4. Select Operator
Select the required operator to define the search criteria.
The system displays the selected operator and prompts you to key in an attribute value.
5. Enter Attribute Value
Key in the attribute value. For a sub-string search, key in a string to appear anywhere within
the attribute value (do not use wild cards).
If the attribute is code-listed, the system displays a list of values from the standard note
library. Select the value and select Accept.
The system validates the input and displays the defined search criteria.
6. Accept or Select And/Or Operator.
Select AND to specify an additional condition or select OR to specify an alternative
condition.

OR
Accept the defined search criteria.

Discrimination Data Revision Form


When you select Copy or Revise from the Discrimination Data form, the Discrimination Data
Revision form displays. This form enables you to copy or revise a discrimination data file from
the specified directory and its record from the Project Control Database. The copied
discrimination data file can then be modified.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 117


Piping Job Specification

Commands
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Search Criteria Defines search criteria for specified attributes in the
Specification/Material Reference Database. For more information, see Search Criteria
Form (on page 116).

Field Descriptions
Number Key in a unique number to name the discrimination data record with up to 24
characters in the Project Control Database. This number is a short name to identify the
record of the discrimination data file.
Description Key in a description of the discrimination data file with up to 40 characters
in the Project Control Database.
File Specification Key in the filename of the discrimination data file to reference.
The system verifies that the file does not already have a record in the project.
File Path Displays the disk location of the discrimination data file. This field retains the
active setting.
File Node Displays the nodename where the discrimination data file is located. This field
retains the active setting.
If prompted to... Do this:
Select Discrimination Data Select the record number of the discrimination data file to
revise and select Accept.
Specify Discrimination Key in any changes to the discrimination data record displayed
Data in the information fields, and select as many of the
Discrimination Data options as necessary to define the
discrimination data file.

118 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Discrimination Data Deletion Form


When you choose Delete, the Deletion form is displayed.

This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.

Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.

Plant Design System (PDS) Reference Data Manager (PD_Data) 119


Piping Job Specification

Report Form
When you select Report from the Report Manager form, the Report form is displayed.

This form creates, revises, and deletes report records and report files. A report record holds
specifications for a report; these specifications include the report name, the report description,
and which format file, discrimination data file, and search criteria data file to use to generate a
report.
The report name is not the title that is printed on the report; the title is included in the
format file.
At the end of each report, a parameters page is included that contains the following information:
Report Output The report number, report title, report creation/revision date, and report
node, path, and file name.
Format The report format number, description, and node, path, and file name.
Discrimination Data The report discrimination data number, description, and file
location (network address, path, and file name). The following discrimination data is also
included: list of model numbers (with discipline), volume (if applicable), search criteria (if
applicable), and sorting sequence.
Search Criteria The report search criteria number, description, and file location (node,
path, and file name. The following search criteria data is also included: list of model
numbers (with discipline), volume (if applicable), search criteria (if applicable), and sorting
sequence.

Options
Create Displays the Report Creation form, which creates a report record and generates
a report. For more information, see Report Creation Form (on page 121).

120 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Revise Displays the Revise Report form, which regenerates a report from an existing or
revised report record. For more information, see Revise Report Form (on page 123).
Delete Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form (on page 125).
Approve Displays the Report Approval form, which approves an existing report. For
more information, see Report Approval Form (on page 125).
Multi-Create Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form (on page
126).

Report Creation Form


When you select Create from the Report form, the Report Creation form is displayed.

Use this form to create a report record and to generate a report. Because report records are stored
in the project control database, you can use them repeatedly.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings, and it is automatically populated if you have specified this data on the Report
Management Data form. For more information, see Report Management Defaults Form
(on page 128).

Plant Design System (PDS) Reference Data Manager (PD_Data) 121


Piping Job Specification

Report Node The name of the system on which the report output file will be located.
This field retains the active settings, and it is automatically populated if you have specified
this data on the Report Management Data form. For more information, see Report
Management Defaults Form (on page 128).
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit Immediately/Submission is Delayed Specifies when the report will be
processed. When this toggle is set to Submission is Delayed, additional fields display for
you to specify the date and time that the report is to be generated.

Operating Sequence
1. From the Report form, select Create.
The Report Creation form is displayed.
2. Specify Report Data
Key in the report record information. Then select the appropriate report format file,
discrimination data file, and search criteria data file.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.

122 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

4. Specify whether the report is to be generated now (Submit Immediately) or later


(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.
5. Click Accept to save the report file.

Revise Report Form


When you select Revise from the Report form, the Revise Report form is displayed.

This form revises an existing report record and generates a report from the project control
database. An option is also provided to update (in some cases) the report record without
generating a report output file. Similarly, you can choose to generate an updated report output
file without updating the report record.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings.
Report Node The name of the system on which the report output file will be located.
This field retains the active settings.
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.

Plant Design System (PDS) Reference Data Manager (PD_Data) 123


Piping Job Specification

If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.
Revise Data Only/Revise Report and Data Specifies revision of the report data only
(Revise Data Only) or revision of the report data and the report output file (Revise Report
and Data). To revise the report specification without updating the report output file, make
the necessary changes, set this toggle to Revise Data Only, and click Accept. To revise the
report output file only, set this toggle to Revise Report and Data without modifying any of
the fields, and click Accept. To modify both the report file and the report output file, make
the necessary changes, set this toggle to Revise Report and Data, and click Accept.
If you update any field other than Report Number and Report Title, this toggle is
automatically set to Revise Report and Data, and the report output file is generated.

Operating Sequence
1. From the Report form, select Revise.
The Report Creation form is displayed with a list of available report files.
2. Select Report
From the displayed list, select the report to be revised. Then click Accept.
The fields update to display the selected report file specifications.
3. Revise Report Information
Update the report record information as needed.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
5. Specify whether the report is to be generated now (Submit Immediately) or later
(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.

124 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

6. Click Accept to save the report file.

Report Deletion Form


When you choose Delete, the Deletion form is displayed.

This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.

Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.

Plant Design System (PDS) Reference Data Manager (PD_Data) 125


Piping Job Specification

Report Approval Form


When you select Approve from the Report form, the Report Approval form is displayed.

Use this form to select a report to approve. Approving a report means that a database attribute is
set from not approved (the default) to approved. This approval status provides a way for you to
flag reports that you have run and verified that the output data is valid. When a report is revised,
the approval status is automatically reset to not approved.
Number The 24-character unique name (also called short name) of the report record.
Description The 40-character description of the report record.

Operating Sequence
1. From the Report form, select Approve.
The Report Approval form is displayed.
2. From the displayed list, select a report to approve. Then click Accept.
The Approval form is displayed.
For more information, see the PD_Report User's Guide.

126 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Report Multiple Submit Form


When you select Multi-Create from the Report form, the Report Multiple Submit form is
displayed.

Use this form to submit multiple reports at the same time.


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.
Description The 40-character descriptive name of the report file.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.

Operating Sequence
1. From the Report form, select Multi-Create.
The Report Multiple Submit form is displayed.
2. Select Reports for Submission
From the displayed list, select the reports to submit. Highlighted reports are selected; select a
highlighted report to remove the highlight and to not submit the report.

Plant Design System (PDS) Reference Data Manager (PD_Data) 127


Piping Job Specification

3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
4. Specify whether the report is to be generated now (Submit to Batch Immediately) or later
(Delayed Submit to Batch). If you choose delayed submission, specify the date and time
that the report is to be submitted.
5. Click Accept to submit the reports.

Report Management Defaults Form


When you select Report Management Data from the Report Manager form, the Report
Management Defaults form is displayed.

This form creates a record in the project control database of the node name and path of the report
definition files. This option is used primarily for setup.
Report Path Specifies the default path of the report output files.
It is recommended that you not send output reports to your system's temporary (that
is, tmp or temp) directory.
Report Node Specifies the default node name of the system on which report output files
are located.
Report Format Path Specifies the default path of the format files.
Report Format Node Specifies the default node name of the system on which format
files are located.
Report Discrimination Data Path Specifies the default path of the discrimination data
files.
Report Discrimination Data Node Specifies the default node name of the system on
which discrimination data files are located.

128 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification

Report Search Criteria Data Path Specifies the default path of the report search criteria
data files.
Report Search Criteria Data Node Specifies the default node name of the system on
which report search criteria data files are located.

Operating Sequence
1. From the Report Manager form, select Report Management Data.
The Report Management Defaults form is displayed.
2. Accept or Exit
In the fields provided, key in the default paths and node names for the report output files,
format files, discrimination data files, and search criteria data files. Then click Accept.

Plant Design System (PDS) Reference Data Manager (PD_Data) 129


Piping Job Specification

130 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 6

Piping Job Specification Tables


Nonphysical data such as branch calculations or gasket separation are stored in the Spec Table
Library or hard-coded in the system. The Spec Tables for US practice are delivered in the
following files:
\win32app\ingr\rdusrdb\us_pjstb.l - object library
\win32app\ingr\rdusrdb\us_pjstb.l.t - text library
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.
Specification Tables - Referenced in the Piping Materials Class Specification Data of the
Material Reference Database. For more information, see PJS Tables and Functions (on page
131).
RDB Tables - Referenced in the Component Placement and Material TakeOff forms of the
Project Data Manager. For more information, see RDB Tables (on page 152).
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. For more
information, see Piping Job Specification Tables Command (on page 172).
Piping Job Specification Table files are limited to a file size of approximately 60,000
bytes or 750 rows.

PJS Tables and Functions


The following special tables and functions are provided in the Spec Table Library. These
table/equation names are defined in the Piping Materials Class Specification Table of the
Specification Material Reference Database.
Temperature and Pressure Service Limits Table (on page 131)
Nominal Piping Diameter Table (on page 133)
Thickness Data Tables (on page 136)
Materials Data Table (on page 139)
Wall Thickness and Branch Reinforcement Equations (on page 141)
Branch Insertion Tables (on page 144)
Gasket Separation Table (on page 150)
Fluid Code Table (on page 151)

Plant Design System (PDS) Reference Data Manager (PD_Data) 131


Piping Job Specification Tables

Temperature and Pressure Service Limits Table


The temperature and pressure service limits table includes the sets of temperatures and pressures
that define the boundaries of acceptability for a piping materials class. These limits can be
dictated by factors such as strength of components and materials used. You must insure that
each of the components included in the piping materials class meet the indicated temperature and
pressure limits.
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 system uses the information in this table to insure:
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.
This table is limited to 100 temperature and pressure values.

Neutral File Format


Table_Data_Definition 'LWWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 1 No_Outputs 1
Input_Interpolation 1, Next_One
Units= DF, PSIG
! Temperature Pressure
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
WWWW ZZZZZZ
END

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

132 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

400 200
500 170
600 140
650 125
700 110
750 95
800 80
END

Parameters
Table_Data_Definition (character-6) This parameter specifies the name of the
Temperature and Pressure Service Limits Table. These tables use the following naming
conventions.
first character: L
second character: the pressure rating of the piping materials class as defined by the
following code:
1= CL150 8= GRAVHD K= CL5000
2= CL300 9= OTHER L= CL6000
3= CL400 A= CL125 M= CL9000
4= CL600 F= CL800 N= CL10000
5= CL900 G= CL2000 R= CL15000
6= CL1500 H= CL3000 T= CL20000
7= CL2500 J= CL4500 V= CL30000
third, fourth, and fifth characters: numbers from 001 through 999 used to make the table
name unique.
Input_Interpolation 1, Next_One This statement tells the system to interpolate between
known values for the temperature value. The statement must be included as shown in the
table format for the desired interpolation to take place.
Temperature (real) This field identifies the maximum temperature value. You can use
both positive (+) and negative (-) values. Values are assumed to be positive unless
otherwise indicated.
Pressure (real) This field identifies the value for pressure corresponding to the
previously defined temperature. Negative (-) values are not accepted in this field.

Plant Design System (PDS) Reference Data Manager (PD_Data) 133


Piping Job Specification Tables

Nominal Piping Diameter Table


The NPD Table consists of the diameters for piping and tubing which are valid within any piping
materials class which references this table. The system verifies any NPD input in the Piping
Design TDB.

Neutral File Format

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.

Neutral File Format - English/Metric Equivalency

Table_Data_Definition 'DWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 1 No_Outputs 1
Units= NPD_MM, NPD_IN
! Metric Diam
WWWWW WWWWW
WWWWW WWWWW
WWWWW WWWWW
WWWWW WWWWW
WWWWW WWWWW
END

Examples

Table_Data_Definition 'D036'
! Description= From 0.5 to 36
! By=NP Ckd By=DG Rev=0 Date=22-Jan-1987
No_Inputs 1 No_Outputs 0
Units= NPD_IN
! Diam
0.5
0.75

134 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

1
1.5
2
3
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
34
36
END
Table_Data_Definition 'DB001'
! Description= From 6mm to 900mm (0.375 to 36)
! By=aw Ckd By= Rev=1 Date=17_jul 1989
No_Inputs 1 No_Outputs 1
Units= NPD_MM, NPD_IN
! metric diam, imperial diam
10 0.375
15 0.5
20 0.75
25 1
40 1.5
50 2
80 3
100 4
150 6
200 8
250 10
300 12
350 14
400 16
450 18
500 20
550 22
600 24
650 26
700 28
750 30
800 32
850 34
900 36
END

Plant Design System (PDS) Reference Data Manager (PD_Data) 135


Piping Job Specification Tables

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.

Thickness Data Tables


Thickness data is determined as a function of the table name and nominal piping diameter.
These tables include the minimum, retirement, thread, and preferred thicknesses required in the
calculation of piping wall thickness. The tables provide the actual thickness, not a schedule.
Therefore, there must be an individual entry for each diameter. You cannot use an NPD range.
PDS requires that the schedule/thickness values be in inches.

Neutral File Format

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

136 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Example

Table_Data_Definition 'TA501'
! Description= A,0.063CA,0.0071D<=24, 0.0075D>=26
! By=DCG Ckd By=DG Rev=0 Date=31-Jan-1987
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, SC_TH_IN, SC_TH_IN, SC_TH_IN, SC_TH_IN,
SC_TH_IN
! Diam Min Thick Ret Thick Thread Thick Preferred
Schedules/Thicknesses
0.5 .147 .06 - S-160 - - - -
0.75 .154 .06 - S-XS - - - -
1 .179 .06 - S-XS - - - -
1.5 .2 .06 - S-XS - - - -
2 .154 .06 - S-STD - - - -
3 .216 .06 - S-STD - - - -
4 .237 .07 - S-STD - - - -
6 .28 .1 - S-STD - - - -
8 .250 .1 - S-STD - - - -
10 .250 .1 - S-STD - - - -
12 .250 .1 - S-STD - - - -
14 .250 .12 - S-STD - - - -
16 .250 .12 - S-STD - - - -
18 .250 .12 - S-STD - - - -
20 .250 .13 - S-STD - - - -
22 .250 .15 - S-STD - - - -
24 .250 .15 - S-STD - - - -
26 .3125 .17 - S-10 S-STD - - -
28 .3125 .19 - S-10 S-STD - - -
30 .3125 .20 - S-10 S-STD - - -
32 .3125 .21 - S-10 S-STD - - -
34 .3125 .23 - S-STD - - - -
36 .3125 .24 - S-STD S-XS - - -
END

Parameters
Table_Data_Definition - Thickness Data Table Name (character 6) This field
identifies the name of the table. These tables use the following naming conventions:
first character: T
second character: code which combines the criteria type with the maximum size for
which threaded components are used in the piping materials class, as defined below.
Criteria 1 applies to carbon steels and low-alloy steels; criteria 2 applies to aluminum
alloys, stainless steels, and non-ferrous alloys.
A= Criteria 1 with no threaded components
B= Criteria 1 with threaded components up to 1 inch diameter
C= Criteria 1 with threaded components up to 1.5 inch diameter
D= Criteria 1 with threaded components up to 2 inch diameter
F= Criteria 2 with no threaded components
G= Criteria 2 with threaded components up to 1 inch diameter

Plant Design System (PDS) Reference Data Manager (PD_Data) 137


Piping Job Specification Tables

H= Criteria 2 with threaded components up to 1.5 inch diameter


I= Criteria 2 with threaded components up to 2 inch diameter
Z= Special criteria
third character: the corrosion allowance of the piping materials class for which the table
is intended, per the following criteria:
1= None C= 304 clad P= Polyester lined
2= 0.020" D= 304L clad Q= Polypropylene lined
3= 0.030" E= 316 clad R= PTFE lined
4= 0.050" F= 316L clad S= Saran lined
5= 0.063" G= 317 clad T= Teflon lined
6= 0.10" H= 317L clad U= TK31 lined
7= 0.125" J=321 clad V= R11 lined
8= 0.188" L= Cement lined W= R15 lined
9= 0.250" M= Epoxy lined X= R18 lined
A= 405 clad N= Glass lined Y= Other 1
B= 410S clad O= Kynar lined Z= Other 2
fourth and fifth characters: numbers from 01 through 99 used to make the table name
unique.
Diam - Nominal Piping Diameter (integer) This parameter identifies the desired value
for nominal diameter.
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.
Preferred Schedule/Thicknesses 1 through 6 (real) These parameters represent the
schedules and/or thicknesses you prefer be used as a result of a piping wall thickness
calculation. Values in the table are arranged in ascending thickness sequence. The system
rounds the calculated wall thickness to the next higher preferred thickness. You are
restricted to a limit of six preferred thicknesses. PDS requires that these values be in inches.

138 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Materials Data Table


The Materials Data Table consists of the materials data that is a function of the table name,
material grade, wall thickness range, and temperature. These tables include the properties which
are required for the calculation of piping wall thickness. You must insure that units of measure
used in the Materials Table are consistent with those used in the corresponding Temperature-
Pressure Table(s).
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.

Neutral File Format

Table_Data_Definition 'MWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 2 No_Outputs 6
Input_Interpolation 2, Next_One
Units= INT, DF, IN, IN, DEC, PSI, DEC, IN
! Mill Tol
! Mat Gr Temp Thick Range Y S % Value
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
WWWW ZZZZ ZZZZZ ZZZZZ ZZZ ZZZZZZ ZZZZZ ZZZZZ
END

Example

Table_Data_Definition 'ML01'
! Description= ASTM A53-B, A106, API 5L-B
! By=DCG Ckd By=DG Rev=0 Date=24-Feb-87
No_Inputs 2 No_Outputs 6
Input_Interpolation 2, Next_One
Units= INT, DF, IN, IN, DEC, PSI, DEC, IN
! Mill Tolrnce
! Mat Gr Temp Thick Range Y S % Value
142 -20 - - .4 20000 12.5 -
142 100 - - .4 20000 12.5 -

Plant Design System (PDS) Reference Data Manager (PD_Data) 139


Piping Job Specification Tables

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:
A= ASME Section I [Power Boilers] L= ANSI-B31.3 [Petroleum]
B= ASME Section III [Nuclear] M= ANSI-B31.4 [Oil Transport]
C= Do not use N= ANSI-B31.5 [Refrigeration]
D= ASME Section VIII-1 [Unfired Vessels] P= ANSI-B31.8 [Gas Transmission]
E= ASME Section VIII-2 [Unfired Vessels] Q= ANSI-B31.9 [Building Services]
J= ANSI-B31.1 [Power] T= API
K= ANSI-B31.2 [Fuel Gas] V= AWWA
third and fourth characters: numbers from 01 through 99 used to make the table name
unique.

140 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Input_Interpolation 2, Next_One This statement must be included as shown for


interpolation to take place. Interpolation is used for all the output fields, if required.
Mat Gr - Material Grade (integer - standard note 145) This code-listed parameter
identifies the materials grade. This compound attribute includes the code, specification,
grade, temper, and joint efficiency to be used for the component.
Temp - Temperature (real) This field identifies the applicable temperature for a set of
material properties.
Thick - Wall Thickness Range - low (real)
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.
Y - Coefficient Y (real) This parameter represents the coefficient Y corresponding to
the previously defined parameters in the line. You can enter a positive number or a blank.
S - Allowable Stress (real) This parameter represents the allowable stress
corresponding to the previously defined parameters in the line. You can enter a positive
number or a blank. S is the basic allowable stress for the material excluding casting, joint or
structural grade quality factor (E).
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.

Wall Thickness and Branch Reinforcement Equations


These equations define formulas for the calculation of piping wall thickness and branch
reinforcement to resist positive pressure. The actual equations and their logic are hard-coded in
the software. PDS requires that the thickness value be defined in inches.
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:
A= ASME Section I [Power Boilers]
B= ASME Section III [Nuclear]
C= Do not use
D= ASME Section VIII-1 [Unfired Vessels]
E= ASME Section VIII-2 [Unfired Vessels]
J= ANSI-B31.1 [Power]
K= ANSI-B31.2 [Fuel Gas]
L= ANSI-B31.3 [Petroleum]

Plant Design System (PDS) Reference Data Manager (PD_Data) 141


Piping Job Specification Tables

M= ANSI-B31.4 [Oil Transport]


N= ANSI-B31.5 [Refrigeration]
P= ANSI-B31.8 [Gas Transmission]
Q= ANSI-B31.9 [Building Services]
T= API
V= AWWA
third and fourth characters: numbers from 01 through 99 used to make the equation
name unique.
If the equation name is provided as part of the definition *Cyyy in the Schedule/Thickness
attribute of the Piping Commodity Specification Data table, the equation name must be
limited to the format Ex; no third or fourth character can be defined.
These equations define formulas for the calculation of piping wall thickness and branch
reinforcement to resist positive pressure.

Delivered Equations
The thickness and branch reinforcement logic for the following equations are hardcoded in the
software.
EJ01
Source - ANSI-B31.1.1986 [Power Piping]
Thickness logic from paragraph 104.1, equation 3
Reinforcement logic from paragraph 104.3.1(D)

EL01
Source - ANSI-B31.3c.1986 [Chemical Plant and Petroleum Refinery Piping]
Thickness logic from paragraph 304.1, equation 3a
Reinforcement logic from paragraph 304.3.3 & Code - Appendix H

The following considerations apply to both thickness equations and branch reinforcement
calculations.
Pressures and temperatures used in thickness/branch reinforcement calculations are derived
from data in the Piping Design Database. Both normal and alternate pressure and
temperature conditions are considered. If actual values exist for the normal design or the
alternate design pressure/temperatures, the corresponding operating conditions are ignored.
If default values exist for BOTH sets of design conditions, both normal and alternate
operating conditions are used. At least one complete set of conditions must be defined.
Once the proper pressure and temperature sets are determined, their units of measure are
converted to those used in the Temperature-Pressure Table associated with the Piping
Materials Class to which the component belongs. Conversions are performed using the
procedures and conversion factors defined for the Units of Measure in Appendix F.

142 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Only positive pressure is considered. The system reports an error if you request a thickness
calculation involving a vacuum condition (negative pressure).
Independent sets of thickness/reinforcement calculations are carried out for each applicable
pressure/temperature set. In each calculation set, table values that are temperature dependent
are determined on the basis of the temperature applicable to the calculation set being
considered. The thicker calculated thickness is used.

Thickness Equations
The following considerations apply to thickness equations.
Thickness calculations are triggered by specifying an equation name in the
Schedule/Thickness attribute of the Piping Commodity Specification Data. An asterisk (*)
followed by a name (of the form xyyy) defines the specific calculation or table lookup to be
used for wall thickness. The letters that form this code have the following meaning:
x alphanumeric code that defines the equation to use in the calculation. Possible values and
their definitions are:
If this character is C, the schedule/thickness for the applicable end of the component is
determined by calculations using the thickness equation defined in the
DEFAULT_WALL_THICK_EQUATION attribute of the Piping Materials Class
database table.
If the code is any character other than C, the schedule/thickness for the applicable end of
the component is determined by calculations using the thickness equation with the name
EX.
yyy casting, joint or structural grade quality factor (E) times 100.
This factor is one of the parameters used in the thickness calculation. If you are defining a
calculation to be performed on a seamless fitting (E=1) but want to match the thickness for
the mating welded pipe (E=0.85), the quality factor for the pipe should be entered here.
For components with ends having different nominal diameters, independent sets of thickness
determinations are performed for each NPD. One or more ends may need to calculated, as
determined by specific *xyyy entries in the Commodity Item entity. The larger thickness
(calculated or predefined) is used. For example:
A 20" x 10" reducer is defined in the Piping Commodity Table to have a *xyyy 20" end
and a 0.55" thick, 10" end. The calculation of the 20" end results in a 0.5" thickness. A
0.55" thick reducer is used.
A 24" x 20" reducer is defined in the Piping Commodity Table to have a *XYYY 24"
end and a *XYYY 20" end. The calculation of the 24" end results in a 0.6" thickness.
The calculation of the 20" end results in a 0.5" thickness. A 0.6" thick reducer is used.
All thickness calculations involve a casting, joint, or structural grade quality factor (E).
The value for this factor is YYY/100, where YYY is defined in the entry *XYYY made
under the Schedule Thickness attribute for the Commodity Item under consideration.

Plant Design System (PDS) Reference Data Manager (PD_Data) 143


Piping Job Specification Tables

Branch Reinforcement
The following considerations apply to branch reinforcement calculations.
The need to perform a branch reinforcement calculation is triggered by
the placement of a generic branch component with the actual item name determined
from a branch table. (See Branch Insertion Tables.)
the presence of more than one item name in the Preferred Branch AABBCC Codes
fields of the applicable branch table.
the applicable branch reinforcement being either a reinforcing weld or a reinforcing pad.
All calculations involve a casting, joint, or structural grade quality factor (E). The value for
this factor is YYY/100, where YYY is defined in the Modifier attribute for entries with an
item name of PIPING.
The fillet welds joining reinforcing pads to the header and to the branch are considered in
determining the available reinforcement area.

Spec Access
The execution of a pipe wall thickness calculation is performed when the variable PIPE_OD_n is
encountered in the physical data definition of a pipe or component. Therefore, pipe outside
diameter must be calculated or retrieved from a table before the wall thickness can be used as
part of a table name.
After the actual thickness is calculated, it is compared against the thickness range in the
Materials table and the retirement thickness in the Thickness Data table. The system uses the
greater of these values as the uncorroded wall thickness. Then the system adds the corrosion
allowance from the PMC, the thread thickness from the wall thickness table, and the mill
tolerance from the Materials table. This revised thickness is compared against the minimum
thickness value in the Thickness Data table. The larger of these two values is compared against
the preferred thickness value in the Thickness Data table, and the next largest preferred value is
used for table look-ups and is stored in the TDB.
If the Thickness Data table uses schedules as preferred thickness, the schedules are translated to
an actual thickness by a table look-up from a table of the form
MALWT//Term_type//shc_thick//generic_flag//weight_code
and output 2 gives the actual wall thickness.

Verification of Schedule Thickness


You can set an option in the RDB to determine how the piping segment override
schedule/thickness value will be handled during wall thickness calculations. By default, the
piping segment schedule/thickness override is used in place of the value determined from the
Piping Job Specification.

144 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Branch Insertion Tables


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 Y's and crosses. For them, the
required reinforcement must be specified in Piping Design.
The types of tee branch connections include branch weld, coupling, thredolet, 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.
The Branch insertion table will not include the two components (for example, Tee and
Reducer) at the same time. The software cannot place two components based on one set of
criteria. If you are trying to place a 6"x6"x6" Tee and a 6"x2" Reducer, it can only be done
through manual placement. There is no rule in PDS that allows the placement of both
components.

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

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

Plant Design System (PDS) Reference Data Manager (PD_Data) 145


Piping Job Specification Tables

! 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' - -

146 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

12 10 '6Q3C82' - -
12 12 '6Q3C22' - -
END

Parameters
Table_Data_Definition - Branch Insertion Table Name (character 6) This field
identifies the name of the table. This name results from the compounding of the Branch
Table entry defined in the Piping Materials Class with the acute angle of intersection
between the header and the branch.
These tables use the following naming conventions:
first character: B
second character: a code which combines the criteria type with the maximum size for
which threaded components are used in the PMC, as defined below. Criteria 1 applies to
carbon steels and low-alloy steels; criteria 2 applies to aluminum alloys, stainless steels
and non-ferrous alloys.
A= Criteria 1 with no threaded components
B= Criteria 1 with threaded components up to 1 inch diameter
C= Criteria 1 with threaded components up to 1.5 inch diameter
D= Criteria 1 with threaded components up to 2 inch diameter
F= Criteria 2 with no threaded components
G= Criteria 2 with threaded components up to 1 inch diameter
H= Criteria 2 with threaded components up to 1.5 inch diameter
I= Criteria 2 with threaded components up to 2 inch diameter
Z= Special criteria
third character: the corrosion allowance of the piping materials class for which the table
is intended, per the following criteria:
1= None C= 304 clad P= Polyester lined
2= 0.020" D= 304L clad Q= Polypropylene lined
3= 0.030" E= 316 clad R= PTFE lined
4= 0.050" F= 316L clad S= Saran lined
5= 0.063" G= 317 clad T= Teflon lined
6= 0.10" H= 317L clad U= TK31 lined
7= 0.125" J=321 clad V= R11 lined
8= 0.188" L= Cement lined W= R15 lined
9= 0.250" M= Epoxy lined X= R18 lined
A= 405 clad N= Glass lined Y= Other 1
B= 410S clad O= Kynar lined Z= Other 2
fourth and fifth characters: numbers from 01 through 99 used to make the table name
unique.

Plant Design System (PDS) Reference Data Manager (PD_Data) 147


Piping Job Specification Tables

The second part of the table name defines the acute angle of intersection. Negative
values and values less than 45 degrees or greater than 90 degrees are not valid.
However, when dealing with branch reinforcements, negative values and values less
than 20 degrees or greater than 90 degrees are not valid (per ANSI B31.1 and ANSI
B31.3).
The data fields are sorted by header NPD and then by branch NPD.
Nom Diam Header - NPD for Run (integer) --- This field identifies the nominal diameter
of the header at the intersection. This is the member with the largest nominal diameter.
Nom Diam Branch - NPD for Branch (integer) --- This field identifies the nominal
diameter of the branch member at the intersection. This is the member with the smallest
nominal diameter.
Preferred Branch AABBCC Codes (character 6) --- These field identify the commodity
item name of the component used to reinforce the intersection.
If only one item name is listed, no branch reinforcement calculation is performed. The
specified item is placed at the intersection.
If two or more item names apply in one line, the system calculates the branch
reinforcement thickness. The system tests the listed item names sequentially (from left
to right) until the applicable strength criteria are satisfied.
Therefore, these codes should be arranged in ascending strength sequence (for example,
reinforcing welds, followed by reinforcing pads, followed by weldolets.)
If you enter a value of LOOKUP in the AABBCC field, it will refer to the
BRANCHID.LN file in the \project directory. You must create this file and edit the
attributes. For an example of the file format, see BRANCHID.LN File (on page 148)
Typically, the codes are from one of the following types:
Reinforcing elements, such as reinforcing welds and pads.
Weld-on components reinforcing the intersection such as saddles and weldolets.
Weld-in components actually making the intersection such as laterals and tees.

BRANCHID.LN File
The BRANCHID.LN file must be placed in the \project directory and is formatted as shown
below:
MATCHING_ATTRIBUTES: 3

LINE_DEF: WC-0104
BRANCH_DEF: 5192; 5192; 6Q3C22
BRANCH_DEF: 5768; 5320; 6Q3C80

LINE_DEF: WC-0105
BRANCH_DEF: 5192; 5032; ATECH

MATCHING_ATTRIBUTES - Defines the search criteria for the pipeline to be revised.


The value 3 is the attribute number as defined by the Design DDL and Piping Segment Data,
and 3 is therefore equal to line_id.

148 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

LINE_DEF - Used with the MATCHING_ATTRIBUTES value. In the example above, the
first MATCHING_ATTRIBUTES: 3 value is WC-0104. The software searches for pipeline
WC-0104 to place the branching component.
BRANCH_DEF - Determines which branch value is placed on the pipeline based on the
first and second size attributes. If the first and second size attributes match, the branch value
is used. For example, in the second BRANCH_DEF line of the WC-0104 LINE_DEF
section, the first and second size attributes are 5768 and 5320, respectively. If these
attributes match up, then the value 6Q3C80 is placed on the WC-0104 pipeline.
BRANCH_DEF - Determines which branch value is placed on the pipeline based on the
first and second size attributes. If the first and second size attributes match, the branch value
is used. For example, in the second BRANCH_DEF line of the WC-0105 LINE_DEF
section, the first and second size attributes are 5192 and 5032, respectively. If these
attributes match up, then the value ATECH is placed on the WC-0105 pipeline.

The piping assembly TECH must be proceeded by an A.


The BRANCHID.LN file references the Piping Assembly Library when a value of
"LOOKUP" is placed in the AABBCC field of the branch insertion table. Below is an
example of the lookup value in the branch insertion table:
! 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 'LOOKUP' - -
3 3 '6Q3C22' - -
4 0.75 '6Q3C74' - -
4 1 '6Q3C74' - -
4 1.5 '6Q3C74' - -
> 4 2 '6Q3C73' - -
> 4 3 'LOOKUP' - -
4 4 '6Q3C22' - -
6 0.75 '6Q3C74' - -
6 1 '6Q3C74' - -
6 1.5 '6Q3C74' - -
> 6 2 '6Q3C73' - -
> 6 3 '6Q3C73' - -
> 6 4 'LOOKUP' - -
6 6 '6Q3C22' - -

END

Plant Design System (PDS) Reference Data Manager (PD_Data) 149


Piping Job Specification Tables

Gasket Separation Table


These tables define the gasket gap to be used for a given nominal diameter and maximum
temperature.
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.

Neutral File Format

Table_Data_Definition 'GWWW_WWWWWW'
! Description= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-ZZZZ
No_Inputs 2 No_Outputs 1
Units= NPD_IN, DF, IN
! Diam TMx Gaskt Gap
WWWWW ZZZ ZZZZZ WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
WWWWW ZZZ ZZZZZ
END

Example

Table_Data_Definition 'G001_1500'
! Description= SP-1000 deg F , RJ-1001 deg F
! By=DCG Ckd By=DCG Rev=0 Date=24-Jun-1987
No_Inputs 2 No_Outputs 1
Units= NPD_IN, DF, IN
! Diam TMx Gaskt Gap
0.5 1000 .125
0.75 1000 .125
1 1000 .125
1.5 1000 .125
2 1000 .125
3 1000 .125
4 1000 .125
6 1000 .125
8 1000 .125
10 1000 .125
12 1000 .125
14 1000 .125
16 1000 .125
18 1000 .125
20 1000 .125
24 1000 .125
0.5 1001 .16

150 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

0.75 1001 .16


1 1001 .16
1.5 1001 .16
2 1001 .12
3 1001 .12
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 151


Piping Job Specification Tables

Fluid Code Table


Fluid Code tables can be used to limit the number of fluid codes which are valid for a particular
Piping Material Class. A Fluid Code table works much like the Diameters table. Where the
Diameters Table contains a valid set of diameters for a PMC, the Fluid Code table contains a set
of valid Fluid Codes for a PMC.
To use a Fluid Code table,
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.

Neutral File Format

Table_Data_Definition 'FC001'
! Description= By Process Vendor
! By=SCC Ckd By=SCC Rev=1 Date=12-OCT-90
No_Inputs 1 No_Outputs 0
Units= INT
521
522
524
527
530
533
536
539
542
545
550
END

Parameters
Table_Data_Definition (character 6) This field identifies the name of the Fluid Code
table. These tables use the following naming conventions:
first and second character: FC
third, forth, and fifth characters: numbers from 001 to 999 used to make the table name
unique.
Fld Cd (integer) This field lists the code list numbers for the valid fluid codes from code
list set 125.

152 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

RDB Tables
The following reference data tables are defined in the Spec Table Library. These tables are
required to provide basic data for the performance of the software.

TNF Table Name


G02 COMMODITY_ITEM_NAME (see "Commodity Item
Name Table (G02)" on page 154)
G04 BEND_DEFLECTION (see "Bend Deflection Table
(G04)" on page 156)
G06 PIPE_RUN_LENGTH (see "Segment Pipe Run Length
Threshold Table (G06)" on page 157)
G07 PIPE_LENGTH (see "Pipe Length Threshold Table
(G07)" on page 158)
G11 BOLT_LENGTH (see "Preferred Bolt Length Table
(G11)" on page 159)
WELD_TYPE_TABLE (see "Weld Type Table" on page
162)
WELD_C10031 (see "Weld Clearance Table" on page
167)
DRV_WELD_DEF (see "Weld Graphics Dimensions
Table" on page 168)
CommodityCode_BLT (Bolt Commodity Code Table
(on page 166))
CommodityCode_GKT (Gasket Diameter Table (on
page 168))
FIELD_FIT_LENGTH (see "Field Fit Length Table" on
page 169)
Component_Mirror_Table (see "Component Mirror
Table" on page 170)
Operator_Mirror_Table (see "Operator Mirror Table"
on page 170)
Default_End_Prep (see "Default End Preparation Table"
on page 171)
MTO Tables and Functions (on page 172)
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 (on page 219) for information on the
basic conventions used for PDS tables.

Plant Design System (PDS) Reference Data Manager (PD_Data) 153


Piping Job Specification Tables

Commodity Item Name Table (G02)


The commodity item name table is used when placing a component at the vertex of an existing
piping segment (in either automatic or manual component placement). It enables you to relate
the component types (1 to 70) hard-coded in the software with the applicable Item Names. As
the system processes the segment for component placement, it uses the derived Item Name from
this table to reference the Piping Commodity Specification data in the Specification Material
Reference Database.
When placing change of direction components, this table is used in conjunction with the Bend
Deflection Table.
The table name format that applies to this table is:
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'

154 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

29 '6Q2C19'
30 '6Q2C21'
31 '6Q2C08'
32 -
33 -
34 -
35 -
36 -
37 -
38 'IND'
39 -
40 -
41 '6Q2C49'
42 '6Q2C51'
43 '6Q2C53'
44 '6Q2C06'
45 '6Q3C89'
END
The meaning of the various component types is outlined below:

Comp Type Definition


1 Piping (not used by the software)
2 Tubing (not used by the software)
3 Hose (not used by the software)
4 Concentric diameter change
5 Flange in bends
6 Flange in other components
7 90 degree directional change
8 45-90 degree directional change
9 45 degree directional change
10 < 45 degree directional change
11 True Y
12 Equal size cross (if not equal size, software will handle as a
branch)
13 > 90 pipe bend
14 90 degree reducing elbow
15 Lateral (not used by the software)
16 Reducing lateral
17 Reducing run and branch lateral
18 Reducing run and branch tee
19 Lateral (not used by the software)

Plant Design System (PDS) Reference Data Manager (PD_Data) 155


Piping Job Specification Tables

Comp Type Definition


20 Elbolet (used by Compute for Elbolet under the Tap command)
21 Reinforcing weld
22 Reinforcing pad
23 Branch nipple
25-27 vent/drain valve A - C
28 end
29 plug
30 cap
31 blind flange
32-37 Closing component A - F
38-40 Instrument indicator A - C
41 5.625 degree bend
42 11.25 degree bend
43 22.5 degree bend
44 Orifice flange
45 In-line nipple
51-60 Pipe-like commodity item 1 - 10
61-70 Pipe-like model code 1 - 10
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.

Bend Deflection Table (G04)


The bend deflection table is used when placing a component at the vertex of an existing piping
segment (in either automatic or manual component placement). The system uses the bend angle
at the segment vertex to determine the type of component to be placed.
This table contains the following data:
bend angle - low
bend angle - high
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) (on page 154). A value of 0 for the type
indicates that no reducing component should be placed for an angle range.

156 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

The system uses the bend angle to search this table for the matching range of bend angles. The
system uses the index into the Commodity Item Name table for either a full size bend or a
reducing bend depending upon the nominal piping diameters of the line route segments that form
the bend. The system searches for an entry in the table where the angle is greater than or equal
to the low bend angle and less than the high bend angle.
You can define more than one bend deflection table for a project provided they are given
different names. For example, one table can apply to underground piping and the other to
aboveground piping. Refer to the Component Placement form in the Project Data Manager
for information on defining the bend deflection table for a project or model.
The table name format that applies to this table is:
TNF=G04 BEND_DEFLECTION

Example

Table_Data_Definition 'BEND_DEFLECTION'
! Description= Component type to use as function of angle between runs
! By=EPZ Ckd By=DCG Rev=2 Date=09-Nov-1987
No_Inputs 2 No_Outputs 2
Units= DEC, DEC, INT, INT
! Angle Comp Type To Use
! Low High Full Red
0.1 44.9 10 0
44.9 45.1 9 0
45.1 89.9 8 0
89.9 90.1 7 14
90.1 179.9 13 0
END
The following listing shows the component types used in this example.
bend angle index
low high full size reducing size
0.1 44.9 10 ( < 45 trimmed bend) N/A
44.9 45.1 9 (45 bend) N/A
45.1 89.9 8 (45-90 trimmed bend) N/A
89.9 90.1 7 (90 bend) 14 (reducing 90 bend)
90.1 179.9 13 ( > 90 trimmed bend) N/A

Segment Pipe Run Length Threshold Table (G06)


This table enables you to define the minimum allowable segment run length which can be placed
in the model during centerline routing. The values defined in this table do not apply to the
segment run automatically created by the software when placing components end to end.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 157


Piping Job Specification Tables

The value for nominal diameter is interpreted as follows:

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.
The table name format that applies to this table is:
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

Pipe Length Threshold Table (G07)


This table enables you to define the minimum and preferred allowable pipe lengths which can be
placed (manually or by automatic component placement).
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.

158 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Any value for nominal diameter is interpreted as follows:

Diam Entry Range of Diameters Covered


n1 nominal diameter <= n1
n2 n1 < nominal diameter <= n2
n3 n2 < nominal diameter <= n3
...
n8 n7 < nominal diameter <= n8
n9 n8 < nominal diameter <= n9
Using this scheme, you should look on the line following the actual NPD to determine the
minimum length, unless the NPD is equal to one of the diameter entries. Only lengths greater
than the minimum length in the table are allowed. For example, if you are placing a pipe with 14
inch NPD, you can only place pipe runs greater than 3 inches in length.
The table name format that applies to this table is:
For TNF=G07 PIPE_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

Preferred Bolt Length Table (G11)


The data for bolts and gaskets is a function of nominal diameter, end preparation for each mating
flange, and pressure rating for each mating flange. The bolt length table supplies data for
machine bolts, stud bolts, and cap screws. It determines the bolt data required for both regular
and bolt-thru bolts. This table enables you to define the low and high range for calculated bolt
lengths and the corresponding preferred or purchased lengths of the bolt.
You can define up to 300 entries in this table.
The table name format that applies to this table is:
For TNF=G11 BOLT_LENGTH
Refer to the Report Manager Reference Guide for more information on bolt tables and bolt table
logic.

Plant Design System (PDS) Reference Data Manager (PD_Data) 159


Piping Job Specification Tables

Example
Table_Data_Definition 'BOLT_LENGTH'
! Description= Preferred bolt lengths (maximum of 300 entries)
! By=GJH Ckd By=DCG Rev=1 Date=04-Aug-1987
No_Inputs 2 No_Outputs 1
Units= IN, IN, IN
! Bolt Length Preferred
! Low High Bolt Length
0.0 1.5 1.5
1.5001 1.75 1.75
1.7501 2 2
2.0001 2.25 2.25
2.2501 2.5 2.5
2.5001 2.75 2.75
2.7501 3 3
3.0001 3.25 3.25
3.2501 3.5 3.5
3.5001 3.75 3.75
3.7501 4 4
4.0001 4.25 4.25
4.2501 4.5 4.5
4.5001 4.75 4.75
4.7501 5 5
5.0001 5.25 5.25
5.2501 5.5 5.5
5.5001 5.75 5.75
5.7501 6 6
6.0001 6.25 6.25
6.2501 6.5 6.5
6.5001 6.75 6.75
6.7501 7 7
7.0001 7.25 7.25
7.2501 7.5 7.5
7.5001 7.75 7.75
7.7501 8 8
8.0001 8.25 8.25
8.2501 8.5 8.5
8.5001 8.75 8.75
8.7501 9 9
9.0001 9.25 9.25
9.2501 9.5 9.5
9.5001 9.75 9.75
9.7501 10 10
10.0001 10.25 10.25
10.2501 10.5 10.5
10.5001 10.75 10.75
10.7501 11 11
11.0001 11.25 11.25
11.2501 11.5 11.5
11.5001 11.75 11.75
11.7501 12 12
12.0001 12.25 12.25
12.2501 12.5 12.5

160 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

12.5001 12.75 12.75


12.7501 13 13
13.0001 13.25 13.25
13.2501 13.5 13.5
13.5001 13.75 13.75
13.7501 14 14
14.0001 14.25 14.25
14.2501 14.5 14.5
14.5001 14.75 14.75
14.7501 15 15
15.0001 15.25 15.25
15.2501 15.5 15.5
15.5001 15.75 15.75
15.7501 16 16
16.0001 16.25 16.25
16.2501 16.5 16.5
16.5001 16.75 16.75
16.7501 17 17
17.0001 17.25 17.25
17.2501 17.5 17.5
17.5001 17.75 17.75
17.7501 18 18
18.0001 18.25 18.25
18.2501 18.5 18.5
18.5001 18.75 18.75
18.7501 19 19
19.0001 19.25 19.25
19.2501 19.5 19.5
19.5001 19.75 19.75
19.7501 20 20
20.0001 20.25 20.25
20.2501 20.5 20.5
20.5001 20.75 20.75
20.7501 21 21
21.0001 21.25 21.25
21.2501 21.5 21.5
21.5001 21.75 21.75
21.7501 22 22
22.0001 22.25 22.25
22.2501 22.5 22.5
22.5001 22.75 22.75
22.7501 23 23
23.0001 23.25 23.25
23.2501 23.5 23.5
23.5001 23.75 23.75
23.7501 24 24
24.0001 24.25 24.25
24.2501 24.5 24.5
24.5001 24.75 24.75
24.7501 25 25
25.0001 25.25 25.25
25.2501 25.5 25.5
25.5001 25.75 25.75
25.7501 26 26

Plant Design System (PDS) Reference Data Manager (PD_Data) 161


Piping Job Specification Tables

26.0001 26.25 26.25


26.2501 26.5 26.5
26.5001 26.75 26.75
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

162 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Weld Type Table


This table defines the weld type code for a given pair of fabrication category values. The
fabrication category values are determined from the connect point data at each of the mating
welded ends.
The table name format that applies to this table is:
WELD_TYPE_TABLE

Example

Table_Data_Definition 'BOLT_LENGTH'
! Description= Preferred bolt lengths (maximum of 300 entries)
! By=GJH Ckd By=DCG Rev=1 Date=04-Aug-1987
No_Inputs 2 No_Outputs 1
Units= IN, IN, IN
! Bolt Length Preferred
! Low High Bolt Length
0.0 1.5 1.5
1.5001 1.75 1.75
1.7501 2 2
2.0001 2.25 2.25
2.2501 2.5 2.5
2.5001 2.75 2.75
2.7501 3 3
3.0001 3.25 3.25
3.2501 3.5 3.5
3.5001 3.75 3.75
3.7501 4 4
4.0001 4.25 4.25
4.2501 4.5 4.5
4.5001 4.75 4.75
4.7501 5 5
5.0001 5.25 5.25
5.2501 5.5 5.5
5.5001 5.75 5.75
5.7501 6 6
6.0001 6.25 6.25
6.2501 6.5 6.5
6.5001 6.75 6.75
6.7501 7 7
7.0001 7.25 7.25
7.2501 7.5 7.5
7.5001 7.75 7.75
7.7501 8 8
8.0001 8.25 8.25
8.2501 8.5 8.5
8.5001 8.75 8.75
8.7501 9 9
9.0001 9.25 9.25
9.2501 9.5 9.5
9.5001 9.75 9.75
9.7501 10 10

Plant Design System (PDS) Reference Data Manager (PD_Data) 163


Piping Job Specification Tables

10.0001 10.25 10.25


10.2501 10.5 10.5
10.5001 10.75 10.75
10.7501 11 11
11.0001 11.25 11.25
11.2501 11.5 11.5
11.5001 11.75 11.75
11.7501 12 12
12.0001 12.25 12.25
12.2501 12.5 12.5
12.5001 12.75 12.75
12.7501 13 13
13.0001 13.25 13.25
13.2501 13.5 13.5
13.5001 13.75 13.75
13.7501 14 14
14.0001 14.25 14.25
14.2501 14.5 14.5
14.5001 14.75 14.75
14.7501 15 15
15.0001 15.25 15.25
15.2501 15.5 15.5
15.5001 15.75 15.75
15.7501 16 16
16.0001 16.25 16.25
16.2501 16.5 16.5
16.5001 16.75 16.75
16.7501 17 17
17.0001 17.25 17.25
17.2501 17.5 17.5
17.5001 17.75 17.75
17.7501 18 18
18.0001 18.25 18.25
18.2501 18.5 18.5
18.5001 18.75 18.75
18.7501 19 19
19.0001 19.25 19.25
19.2501 19.5 19.5
19.5001 19.75 19.75
19.7501 20 20
20.0001 20.25 20.25
20.2501 20.5 20.5
20.5001 20.75 20.75
20.7501 21 21
21.0001 21.25 21.25
21.2501 21.5 21.5
21.5001 21.75 21.75
21.7501 22 22
22.0001 22.25 22.25
22.2501 22.5 22.5
22.5001 22.75 22.75
22.7501 23 23
23.0001 23.25 23.25
23.2501 23.5 23.5

164 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

23.5001 23.75 23.75


23.7501 24 24
24.0001 24.25 24.25
24.2501 24.5 24.5
24.5001 24.75 24.75
24.7501 25 25
25.0001 25.25 25.25
25.2501 25.5 25.5
25.5001 25.75 25.75
25.7501 26 26
26.0001 26.25 26.25
26.2501 26.5 26.5
26.5001 26.75 26.75
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

Plant Design System (PDS) Reference Data Manager (PD_Data) 165


Piping Job Specification Tables

Bolt Commodity Code Table


This table is used if the Basis of Bolt Commodity Code is set to Bolt Commodity Code Table in
the Project Data Manager. The system uses the bolt length and bolt diameter to find the
commodity code in the table.
If you define a bolt commodity code which is less than 17 characters, you should code a hyphen
(-) in the third column.
The table name format that applies to this table is:
Cmdty Code_BLT

Neutral File Format

Table_Data_Definition 'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_BLT'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
No_Inputs 2 No_Outputs 4
Units= IN, IN, IN, AN*8, AN*8, AN*8
! Bolt Bolt Length Bolt Commodity Code
! Diam Low High 1 2 3
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
WWWWW WWWWWWW WWWWWWW ZZZZZZZZ ZZZZZZZZ ZZZZZZZZ
END
Do not load the Bolt Commodity Code table with more than 900 lines.
If Bolt Commodity Code is set to Bolt Commodity Code Table, the Commodity Code and
Bolt Description is reported from this table.

Commodity Code Bolt Commodity PD Report PD MDP


Toggle Code Toggle

size_independent Piping Job Spec System Commodity System


Code (table_202) Commodity Code
(table_202)
size_independent Bolt Commodity Code Commodity Code Commodity Code
table from Bolt Commodity from Bolt
Code Table Commodity Code
Table
size_dependent Piping Job Spec Size Dependent Size Dependent
Commodity Code Commodity Code
(table_211) (table_211)

166 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Commodity Code Bolt Commodity PD Report PD MDP


Toggle Code Toggle

size_dependent Bolt Commodity Code Commodity Code Commodity Code


Table from Bolt Commodity from Bolt
Code Table Commodity Code
Table

Weld Clearance Table


This table contains information obtained from the NPD and the Weld Type table, which are
retrieved from the piping model. Add a version of this table to the Physical Data Library for each
spec.
The table name format that applies to this table is:
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.
Weld_Type_From - Weld_Type_To (integer) These parameters identify the range of
weld type values (from standard note 1100). The To value must equal or exceed the From
value.
Radius_Increase (integer - NPD Units) This parameter identifies the increase to be
applied to the NPD of the weld for use in generating a cylinder to represent the construction
tolerance envelope for the weld.
Overall_Length (integer) This parameter identifies the length of the cylinder for the
weld construction tolerance envelope.

Plant Design System (PDS) Reference Data Manager (PD_Data) 167


Piping Job Specification Tables

Weld Graphics Dimensions Table


This table provides the dimensions used to generate the graphical representation of welds in a
SmartPlant Review session. You may customize this table to modify the appearance of weld
graphics by weld type and diameter. The table name format that applies to this table is:
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
! From_NPD From_Weld_Type TO_NPD To_Weld_Type Weld_Dia_Increase
Weld_Thickness_NPD_Units
2 10 7 22 0.25 0.25
6 12 10 22 0.25 0.25
8 10 12 22 0.25 0.25
END

Parameters
From NPD - TO _NPD (integer) These parameters identify the range of nominal piping
diameters (lower bound to higher bound) for the weld in NPD units. The To value must
equal or exceed the From value.
From_Weld_Type - To_Weld_Type (integer) These parameters identify the range of
the weld type values (from standard note 1100). The To value must equal or exceed the
From value.
Weld_Dia_Increase (decimal) This parameter identifies the percentage increase to be
applied to the NPD of the weld for use in displaying a cylinder to represent the weld in
SmartPlant Review. For example, if the NPD is 6" and the increase is .25, the diameter of
the weld cylinder would be 7 1/2" (6 x 1.25 = 7.5).
Weld_Thickness (decimal) This parameter identifies the percentage to be applied to the
NPD of the weld to determine the thickness of the cylinder.
If this table is absent or if there is no NPD range encapsulating the WELD NPD, the
weld graphics dimensions will be determined as follows:
Diameter = 130% of the NPD at the weld.
Thickness = 25% of the NPD at the weld.

168 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

Gasket Diameter Table


This table is used if the pds_sort_code for the gasket spec entry is set to _GKT. The system uses
the NPD to find the gasket outside and inside diameters.
The table name format that applies to this table is:
Cmdty Code_GKT

Neutral File Format

Table_Data_Definition 'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_GKT'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! Gasket Diameter
! NPD Inside Outside
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
END

Field Fit Length Table


This table defines the pipe length adjustment for a given weld type. The weld type is determined
from the connect point data at the mating welded ends.
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.

Neutral File Format

Table_Data_Definition 'Fit_Length_Table'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
No_Inputs 1 No_Outputs 1
Units= INT, IN
! Weld Type Adjust.
1 ZZZZZZZ
11 ZZZZZZZ
21 ZZZZZZZ
22 ZZZZZZZ

Plant Design System (PDS) Reference Data Manager (PD_Data) 169


Piping Job Specification Tables

Component Mirror Table


This table is used for components which require non-symmetrical mirroring. It defines a mirror
option for a given Eden module. This table is called through the use of the Eden keyword
TOGGLE_<INT>, where <INT> is an integer value as defined below for Option 1.

Example

Table_Data_Definition 'Component_Mirror_Table'
No_Inputs 1 No_Outputs 3
Units= AN*6, INT, INT, INT
! Model Code Option 1 Option 2 Option 3

Parameters
Model Code This column lists the model codes for components which require non-
symmetrical mirroring. The model code is used as input by the calling Eden module.
Option 1 This column represents the TOGGLE_<INT> Eden variable or specific
command instruction used to control a non symmetrical mirror operation. This column can
have any of the following values.
mirror logic in the Eden module. All items with these setting must have a tutorial
accessed in the Eden module to allow the user to change the TOGGLE during
placement.
For example, if Option 1 = 1, check the TOGGLE_1 Eden variable in the Eden module
to perform specific logic to compensate for a mirrored component.
degrees instead of mirroring it.
The Model Code item will be rotated due to a specific non symmetrical definition where
there are no non symmetrical connect points involved.
the specific item.
The item will not be mirrored due to specific non symmetrical definition. In other
words, the item is only stocked in one non symmetrical configuration which has non
symmetrical connect points involved.
Option 2 & Option 3 These columns are not currently used.

Operator Mirror Table


This table is used for operators that require non-symmetrical mirroring. It defines a mirror option
for a given Eden module. This table is called through the use of the Eden keyword
TOGGLE_<INT>, where <INT> is an integer value as defined below for Option 1.

Example

Table_Data_Definition 'Operator_Mirror_Table'
! This Table has NOT been Checked
!
No_Inputs 1 No_Outputs 3
Units= AN*6, INT, INT, INT
! Model Code Option 1 Option 2 Option 3

170 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

OI_33 1 - -
OI_35 1 - -
OI_43 1 - -
OI_53 1 - -
A_1033 1 - -
OP_331 1 - -
OP_332 1 - -
OP_333 1 - -
OP_334 1 - -
OP_351 1 - -
OP_493 1000 - -
OP_494 1000 - -
OP_573 1000 - -
OP_574 1000 - -
OP_711 1000 - -
OP_853 1000 - -
OP_854 1000 - -

Parameters
Model Code This column lists the model codes for operators which support mirroring.
The model code is used as input by the calling Eden module.
Option 1 This column represents the TOGGLE_<INT> Eden variable or specific
command instruction used to control a non symmetrical mirror operation. This column can
have any of the following values.
mirror logic in the Eden module. All items with these setting must have a tutorial
accessed in the Eden module to allow the user to change the TOGGLE during
placement.
For example, if Option 1 = 1, check the TOGGLE_1 Eden variable in the Eden module
to perform specific logic to compensate for a mirrored component.
degrees instead of mirroring it.
For example, if Option 1 = 1000, the Model Code item will be rotated due to a specific
non symmetrical definition where there are no non symmetrical connect points involved.
tell the Mirror command to rotate the component 180 degrees instead of mirroring it.
The item is only stocked in one non symmetrical configuration and does not have non
symmetrical connect points involved.
Option 2 & Option 3 These columns are not currently used.

Default End Preparation Table


The Default End Preparation Table is an optional table that can be used to automatically set the
end preparation of instruments and piping specialties that are being placed in a piping model.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 171


Piping Job Specification Tables

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).

MTO Tables and Functions


The following special tables and functions are used by the system during Material Take-Off.
Refer to the Report Manager Reference Guide for more information on the reporting process.
field fit length tables (not currently implemented)
preferred bolt length tables
preferred bolt length roundoff factor
nut allowance table
bolt diameter and bolt pattern specification
Gasket Outside and Inside diameter tables
Bolt Length/Diameter Commodity Code tables

Piping Job Specification Tables Command


This command enables you to access the library management options for the Piping Job
Specification Table Library. You can create a new library file or create, modify, or delete data in
an existing Library. You can also create reports of the data in the library and post data from the
unapproved library to the approved library.
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.

172 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

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.

Before Using This Command


Define the location of the approved and unapproved (if applicable) Piping Job Spec Table
library files in the Reference Database Management Data.
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.

Create Library (on page 174) used to create a new Piping Job Spec Table Library.
Compress Library (on page 174) used to compress the Piping Job Spec Table library.
Unapproved ==> Approved (on page 174) used to copy the unapproved Piping Job Spec
Table library to the approved library.
Create/Interactive (see "Create/Interactive Spec Tables" on page 174) used to compile
table files and add the resulting code to the Piping Job Spec Table library. You can create a
single table or specify a list of tables to be created.
Create/Batch (see "Create/Batch Spec Tables" on page 175) used to compile and add
tables to the library via batch processing.
Revise (see "Revise Spec Tables" on page 176) used to select a table from the library for
editing and compile the revised table definition.
Delete (see "Delete Spec Tables" on page 177) used to delete a specified table from the
library.
Report (see "Report on Spec Tables" on page 178) used to create a report of the library
contents.

Plant Design System (PDS) Reference Data Manager (PD_Data) 173


Piping Job Specification Tables

List (see "List Spec Tables" on page 180) used to list the files contained in the library.
Extract (see "Extract Spec Tables" on page 180) used to extract a table file from the
library for editing or printing.
Refer to Default Project Control Data (on page 23) for information on defining the default
location for library files. You can also change the default file locations for each option at any
time.

Create Library
This option is used to create a new Piping Job Spec Table Library. It automatically creates the
object library (.l), the text library (.l.t), and table revision management library (.l.t.r) for the
library that is being created.
The system displays the approved and unapproved Piping Job Spec Table Library names as
defined in the RDB Management Data.

Accept to Create or Exit to Avoid Creating New Library


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.

Compress Library
This option is used to compress the Piping Job Spec Table library. Any tables which have been
deleted from the library will be removed.

Unapproved ==> Approved


This option copies the unapproved Piping Job Spec Table library to the approved library.

Accept to Copy or Exit to Avoid Copying


Select Accept to copy the unapproved library file to the approved library.

Create/Interactive Spec Tables


This option enables you to compile tables and add the resulting code to the spec table library.
You can create a single table or specify a list of tables to be created.

Before Using This Command


To add more than one table to the library, create a list file in the Piping Spec Path directory
which identifies the names of the table files to be added. This file should list one filename per
line with no directory paths. All of the listed files must reside in the Piping Spec Path
directory.

174 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification 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.
3. Specify Filename for processing
Key in the name of the table file or list file to be compiled and added to the active library.
(Refer to PJS Tables and Functions (on page 131) for information on the table formats.)
4. Accept or Select Other Option
Accept the file and begin processing.

Create/Batch Spec Tables


This option enables you to load table files into the Spec Table Library as a batch operation at a
specified time.

Before Using This Command


To add more than one table file to the library, create a list file which identifies the names of the
table files to be added. The list file should contain one entry (filename) per line.

Operating Sequence
1. Select the Create/Batch option from the Specification Tables Library/Data Management
form.

2. Set the toggle to Single to process a single table file or to List to process a list file.
3. Specify Filename for Processing
Key in the name of the table file or list file to be added to the active library.
4. Accept to Submit or Set Submit Time
Set the toggle to Submit Immediately or Delayed Submit.
For Delayed Submit, set the time to process the table files.
5. Accept the file and begin processing.
The system submits the request to the batch queue PDreference.

Plant Design System (PDS) Reference Data Manager (PD_Data) 175


Piping Job Specification Tables

Revise Spec Tables


This option enables you to revise selected table files from the library. For each table to be edited,
select the table, edit the file, and then compile the table and put it back in the library. The
system updates the revision date for revised table in the Table Revision Management Library.

Operating Sequence
1. Select the Revise option from the Specification Tables Library/Data Management form.

2. Select Table for Revision.


Select the table file to be revised and select Accept.
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.

176 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

3. 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 an error occurs in revising a table, the editor screen is invoked automatically to give you
an opportunity to correct the problem.
The system redisplays the list of table files.
4. You can select another table to be revised as specified in step 2.

Delete Spec Tables


This option enables you to delete tables from the Piping Job Spec Table Library. It also deletes
the revision date for the table from the Table Revision Management Library.

Operating Sequence
1. Select the Delete option from the Specification Tables Library/Data Management form.

Plant Design System (PDS) Reference Data Manager (PD_Data) 177


Piping Job Specification Tables

2. Select Module Name


Select the table files to be deleted from the list of tables. You can use the scroll bar to scroll
through the available tables.
3. Select Module Name, Accept or Exit
Accept the selected tables.
The system deletes the tables from the Spec Table Library.

Report on Spec Tables


This option creates a report of information in the Spec Table Library. You can create a list file of
all the table files in the Spec Table library or create a detailed report of all the tables modified
since a specified date.

Operating Sequence
1. Select the Report option from the Specification Tables Library/Data Management form.

178 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

2. Set the toggle to Default Report to create a list file of all the table files in the library.
OR
Set the toggle to Revision Dates Report and key in a revision date to process all tables
modified since the specified revision date. The report lists the full contents of the modified
tables with individual revision dates per line.
3. Set the toggle to Report on Unapproved or Report on Approved to define the source of
information to be reported. This toggle is only displayed when both the approved and the
unapproved library are being used.
4. Accept to Form Report or Revise Report Parameters
Select Accept to form the report using the default parameters, and proceed to step 6.
OR
Key in the file information (Node Name and File Path) for the location of the neutral file to
be created.
5. Select Save, Print, or Print/Save.
For Print or Print/Save, select the print queue from the list of displayed queues. Refer to
the section on Plot and Print Queues in the Project Administrator Reference Guide for more
information on setting up multiple print queues.
If you select the Save or Print/Save option, the system creates a file named spec_tables in
the default source file location or in the location you specified.
6. Accept to Submit or Specify Submit Time
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set the
time to process the request.
7. Accept to Create Report
Select Accept to create the specified report file.

Plant Design System (PDS) Reference Data Manager (PD_Data) 179


Piping Job Specification Tables

List Spec Tables


This option displays all the tables for the Spec Table Library with the revision date of each table.

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.

Extract Spec Tables


This option enables you to extract a table file or set of table files from the Spec Table Library for
editing or printing.

Operating Sequence
1. Select the Extract option from the Specification Tables Library/Data Management form.

180 Plant Design System (PDS) Reference Data Manager (PD_Data)


Piping Job Specification Tables

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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 181


Piping Job Specification Tables

182 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 7

Graphic Commodity Data


The graphic commodity data is contained in the following object libraries:
Graphic Commodity Library (on page 183) - The delivered file
\win32app\ingr\pdshell\lib\pip_gcom.l contains parametric definitions for the components.
Physical Data Tables (on page 194) - The delivered file \win32app\ingr\rdusrdb\us_pcdim.l
contains American dimension data for components.
Piping Job Specification Tables (on page 131) - The delivered file
\win32app\ingr\rdusrdb\us_pjstb.l contains specification tables referenced in the Piping Job
Specification.
Refer to Reference Data Overview (on page 1) 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.
Additional Information
Notes for Graphic Commodity Data (on page 197)
Graphic Commodity Library Manager (on page 200)

Plant Design System (PDS) Reference Data Manager (PD_Data) 183


Graphic Commodity Data

Graphic Commodity Library


The Graphic Commodity Library (GCL) provides data for commodity items, engineered items,
and instruments. It is basically a catalog of component data which is accessed to:
determine physical data based on user specifications (such as NPD and end preparation)
assign connect point data from the Piping Job Specification
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.
Eden is composed of three major modules:
Symbol Processors (on page 186) and Sub-Symbol Processor (on page 187)
Physical Data Definitions (on page 187)
Parametric Shape Definitions (on page 192)
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:
\win32app\ingr\pdshell\lib\pip_gcom.l - object library
\win32app\ingr\pdshell\lib\pip_gcom.l.t - text library
The modular approach provides for more efficient storage of information in these libraries by
enabling common information to be shared by different symbols.

184 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

The first line of each Eden module defines the type of module (such as symbol processor) and
the module name. This statement determines a two- character category code to be prefixed to
the module name in the object library. This prefix is only used by the system; it should not be
keyed-in as part of the module name.

The entries in the library use the following prefixes to identify the type of data.
SP Symbol Processor
PD Physical Data Definition Module
UF User Function Module
MG Model Parametric Shape Definition Module
DG Detailed Parametric Shape Definition Module

Plant Design System (PDS) Reference Data Manager (PD_Data) 185


Graphic Commodity Data

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.

Symbol Processors
A symbol processor is the controlling function or logic used to produce the graphics for a
commodity item, piping specialty, instrument, pipe support, or interference envelope. During
component placement, the symbol processor:
accesses the active component design parameters
assigns connect points
calls the required physical data modules
determines and calls the required parametric shape modules.
The system retrieves the active component parameters which are dependent upon a connect point
from the PJS in terms of green, red, or tap connect point properties. The symbol definition
assigns the data corresponding to these connect point types (green, red, or tap) to the physical
connect point numbers (CP1, CP2, CP3, CP4, or CP5).
The first line of the Eden module defines the type of module and the module name. The
following statement is used in the Eden modules to indicate a symbol processor module.
Symbol_Processor 'module name'
This statement tells the system to use the category code SP for the prefix. You should use the
following conventions in assigning the module name. The module name is determined by the
type of component being placed (commodity item or specialty item).
For a commodity item, the system searches for the New Item Name (model code) of the
commodity item as the module name. If the New Item Name is blank in the Commodity
Item entity, the system searches for the Item Name as the module name.
For a specialty item, the system searches for the specialty item name (derived from the PJS)
as the module name.
For an instrument, the system searches for the instrument name (derived from the PJS) as the
module name.
The delivered symbol processors are identified in the library with the prefix SP.
The following lists the symbol processor SPGAT which is used to control the placement of a
gate valve.
! REGULAR PATTERN, BOLTED OR MALE ENDS GATE VALVE
Symbol_Processor 'GAT'
Call Assign_Connect_Point ( GREEN, CP1 )
Call Assign_Connect_Point ( RED, CP2 )
physical_data_source = 'V1' // Standard_Type
Call Get_Physical_Data ( physical_data_source )
parametric_shape = 'V1'
Call Draw_Parametric_Shape ( parametric_shape )
Valve_Operator = DABS ( Valve_Operator )
If ( Valve_Operator .NE. 0 ) Then
If ( Valve_Operator .LT. 1000 ) Then

186 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Subcomponent = 'OP' // Valve_Operator


Else
Subcomponent = 'A' // Valve_Operator
EndIf
Operator_Orient = FALSE
EndIf
Stop
End

Sub-Symbol Processor
A subcomponent call in a symbol processor module indicates a sub-symbol processor.
Subcomponents are additions to symbols such as an operator on a valve.
The first line of a sub-symbol processor module indicates the module type and the module name.
Sub_Symbol_Processor 'module name'
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

Plant Design System (PDS) Reference Data Manager (PD_Data) 187


Graphic Commodity Data

Physical Data Definitions


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
Physical_Data_Definition 'module name'
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.

Practice Range Suffix


U.S. Practice 1-99 AMS
European - DIN 100-199 DIN
European - British Standard 200-299 BRITISH_STD
European - Practice A 300-399 EURO_A
European - Practice B 400-499 EURO_B
International - JIS 500-599 JIS
International - Australian 600-699 AUS
International - Practice A 700-799 INT_A
International - Practice B 800-899 INT_B
Company Practice 900-999 COMPANY
The geometric industry standard for a component is defined in the Piping Commodity Data table
of the Material Reference Database. Each component must be assigned a geometric industry
standard if it is to use physical data tables.
For most of the delivered symbols, the physical data modules are classified into two categories:
specific and generic. The specific physical data module is called by the symbol processor. This
module then calls a generic physical data module.

Specific Physical Data Modules


The physical data module PDV1_AMS determines the specific dimensions (face-to-center and
face-to-face) and other physical properties for a gate valve. This is the module called by the
symbol processor SP_GAT:
Physical_Data_Definition 'V1_AMS'

188 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

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

Generic Physical Data Modules


The generic modules contain information which is common to more than one symbol such as
flange thickness, gasket separation, and outside diameter. The physical data module V1_AMS
calls another physical data module VALVE_2_AMS which contains the generic dimension data
for all valves with two connect points.

Physical_Data_Definition 'VALVE_2_AMS'
Input_1 = Nom_Pipe_D_1
If ( Gen_Type_1 .EQ. BOLTED ) Then
table_name = 'BLT' // Term_Type_1 // Pr_Rating_1 //
Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_1
Thickness_1 = Output_2
Seat_Depth_1 = Output_3
Thickness_1 = Thickness_1 - Seat_Depth_1
CP_Offset_1 = Gasket_Sep_1
If ( Symbology .EQ. MODEL ) Then
Thickness_1 = 0.0
Depth_1 = 0.0
Pipe_OD_1 = 0.0
Body_OD_1 = Facing_OD_1
Else
table_name = 'MAL_300_5'
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 )

Plant Design System (PDS) Reference Data Manager (PD_Data) 189


Graphic Commodity Data

Facing_OD_1 = Output_2
Thickness_1 = 0.0
Depth_1 = 0.0
Seat_Depth_1 = 0.0
CP_Offset_1 = 0.0
Pipe_OD_1 = Facing_OD_1
Body_OD_1 = Facing_OD_1
Else
table_name = 'FEM' // Term_Type_1 // Pr_Rating_1 //
Gen_Flag_Green
Call Read_Table ( table_name, input, output )
Facing_OD_1 = Output_1
Depth_1 = Output_2
Seat_Depth_1 = 0.0
Thickness_1 = 0.0
If ( symbology .EQ. MODEL ) Then
Depth_1 = 0.0
CP_Offset_1 = 0.0
Pipe_OD_1 = 0.0
Body_OD_1 = Facing_OD_1
Else
CP_Offset_1 = -Depth_1
table_name = 'MAL_300_5'
Call Read_Table ( table_name, input, output )
Pipe_OD_1 = Output_2
Body_OD_1 = Pipe_OD_1
EndIf
EndIf
EndIf
If ( Term_Type_2 .EQ. Term_Type_1 .AND. Nom_Pipe_D_1 .EQ.
Nom_Pipe_D_2 )
Then
Facing_OD_2 = Facing_OD_1
Pipe_OD_2 = Pipe_OD_1
Body_OD_2 = Body_OD_1
Thickness_2 = Thickness_1
Depth_2 = Depth_1
Seat_depth_2 = Seat_Depth_1
CP_Offset_2 = CP_Offset_1
Else
Input_1 = Nom_Pipe_D_2
If ( Gen_Type_2 .EQ. BOLTED ) Then
table_name = 'BLT' // Term_Type_2 // Pr_Rating_2 //
Gen_Flag_Red
Call Read_Table ( table_name, input, output )
Facing_OD_2 = Output_1
Thickness_2 = Output_2
Seat_Depth_2 = Output_3
Thickness_2 = Thickness_2 - Seat_Depth_2
CP_Offset_2 = Gasket_Sep_2
If ( Symbology .EQ. MODEL ) Then
Thickness_2 = 0.0
Depth_2 = 0.0
Pipe_OD_2 = 0.0

190 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Body_OD_2 = Facing_OD_2
Else
Depth_2 = Thickness_2
table_name = 'MAL_300_5'
Input_1 = Nom_Pipe_D_2
Call Read_Table ( table_name, input, output )
Pipe_OD_2 = Output_2
Body_OD_2 = Pipe_OD_2
EndIf
Else
If ( Gen_Type_2 .EQ. MALE ) Then
table_name = 'MAL' // Term_Type_2 // Gen_Flag_Red
Call Read_Table ( table_name, input, output )
Facing_OD_2 = Output_2
Thickness_2 = 0.0
Depth_2 = 0.0
Seat_Depth_2 = 0.0
CP_Offset_2 = 0.0
Pipe_OD_2 = Facing_OD_2
Body_OD_2 = Facing_OD_2
Else
table_name = 'FEM' // Term_Type_2 // Pr_Rating_2 //
Gen_Flag_Red
Call Read_Table ( table_name, input, output )
Facing_OD_2 = Output_1
Depth_2 = Output_2
Seat_Depth_2 = 0.0
Thickness_2 = 0.0
If ( Symbology .EQ. MODEL ) Then
Depth_2 = 0.0
CP_Offset_2 = 0.0
Pipe_OD_2 = 0.0
Body_OD_2 = Facing_OD_2
Else
CP_Offset_2 = -Depth_2
table_name = 'MAL_300_5'
Input_1 = Nom_Pipe_D_2
Call Read_Table ( table_name, input, output )
Pipe_OD_2 = Output_2
Body_OD_2 = Pipe_OD_2
EndIf
EndIf
EndIf
EndIf
Table_Name_A = Item_Name // Geo_Ind_Std // Term_Type_1
Table_Name_W = Commodity_Code
Input_1 = Nom_Pipe_D_1
Input_2 = Nom_Pipe_D_2
If ( Term_Type_1 .EQ. Term_Type_2 .AND. Nom_Pipe_D_1 .EQ.
Nom_Pipe_D_2 )
Then
Table_Name_A = Table_Name_A // Pr_Rating_1 // 'A'
Else
If ( Gen_Type_1 .EQ. Gen_Type_2 ) Then

Plant Design System (PDS) Reference Data Manager (PD_Data) 191


Graphic Commodity Data

! 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
If ( Gen_Type_1 .EQ. MALE ) Then
! Male X Bolted and Male X
Female
Table_Name_A = Table_Name_A // Term_Type_2 // Pr_Rating_2
// 'A'
Else
If ( Gen_Type_2 .EQ. MALE ) Then
! Bolted X Male and Female
X Male
Table_Name_A = Table_Name_A // Pr_Rating_1 //
Term_Type_2 //
Else
! Bolted X Female and
Female X
Bolted
Table_Name_A = Table_Name_A // Pr_Rating_1 //
Term_Type_2 //
Pr_Rating_2 // 'A'
EndIf
EndIf
EndIf
EndIf
Return
End

Parametric Shape Definitions


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
defining connect point geometry
placing connect points
moving the active location a specified distance
drawing a specific graphic shape
placing a center of gravity location.
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.

192 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Model Parametric Shape Definitions


Model parametric shapes are used to define the symbol graphics to be placed in the model. For
example, the parametric shaped module for a valve consist of a cylinder, two cones, and a
cylinder (flange, valve body, flange).
The first line for these modules is of the form
Model_Parametric_Shape_Definition '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.

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

Plant Design System (PDS) Reference Data Manager (PD_Data) 193


Graphic Commodity Data

End

Detailed Parametric Shape Definition


Detailed parametric shapes are used to define more complex symbol graphics to be placed in the
model when the model symbology lock is set to detailed.
The first line for these modules is of the form
Detailed_Parametric_Shape_Definition 'module name'
This statement tells the system to use the category code DG for the prefix.

Interference Parametric Shape Definition


Interference parametric shapes are not used during component placement. They are referenced
during interference detection to determine the volume (interference envelope) to be compared
for clashes with other elements. If a clash is detected during the interference detection process,
the interference parametric shape is used to place an interference marker. Refer to the PDS
Interference Checker / Manager Reference Guide for more information on interference
envelopes.
Interference_Parametric_Shape_Definition 'module name'
This statement tells the system to use the category code IG for the prefix.
If no interference module is found for a component, the system uses the model graphics
module to determine the interference parametric shape.

Physical Data Tables


The physical data tables contain the physical data (dimensions, weights, and surface area)
required for symbol creation, interference detection, stress analysis, and MTO reporting. These
tables are segregated for commodity item data, engineered item data, and instrument data. Refer
to Section 4 for a detailed description of the physical data tables and the table naming
conventions used in PDS.
The physical data tables for US Practice are delivered in the following files:
\win32app\ingr\rdusrdb\us_pcdim.l - object library
\win32app\ingr\rdusrdb\us_pcdim.l.t - text library
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.

194 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

By segregating data into separate physical data libraries you can access a subset of the total
physical data available for a project. You can also build a specific set of physical data for a
particular project. The following table types are required for piping and instrument components.
Generic dimensional data
Generic tables contain data which is not specific to a particular symbol (such as flange
outside diameter or flange thickness). These tables are identified by the prefix BLT, FEM,
or MAL (for the termination type) and end with the extension .TBL (the table name is
independent of the name of the physical data module).
Specific commodity data
Specific tables contain commodity data which is specific to a particular component (such as
dimensions, water weight, and surface area). These specific tables use the model code or
commodity code as part of the table name to classify data by symbol type.
The system uses the water weight data to compute the wet weight using the specific
gravity of the operating fluid.
fluid weight = water weight * specific gravity for fluid
operating weight = dry weight + fluid weight
The surface area data enables the system to perform paint requirement calculations and
insulation weight calculations.
Specific commodity dry weight data
Piping Specialty physical data
The dimensions, dry weight, water weight, and surface area for specialty items can be stored
in a set of tables or defined at placement.
Instrument physical data
The dimensional data, dry weight, water weight, and surface area for instruments can be
stored in a set of tables or defined at placement.
You can form the name of a physical data table from attributes for the component (such as
geometry standard and end preparation). However, the table name cannot exceed 46 characters.
Additional Information
Data Retrieval from the Physical Data Library (on page 195)
Example of Physical Data Look-Up (on page 195)

Data Retrieval from the Physical Data Library


The data retrieval from tables in the Physical Data Library is restricted to two independent
variables and eight dependent variables. If only one independent variable is required, then nine
dependent variables are allowed. If more independent variables are required, the additional
independent variable(s) must be a part of the table name. If nominal diameter is one of the
independent variables, it must be listed first in the table.

Plant Design System (PDS) Reference Data Manager (PD_Data) 195


Graphic Commodity Data

Example of Physical Data Look-Up


In order to place the valve described earlier in this section, the system references the following
tables.

Generic Tables
The spec access for a six-inch gate valve defines the end preparation at both connect points as
Raised Face Flanged End (code list value 21) which is a bolted connection. As shown in the
listing for VALVE_2_AMS, the table name for a bolted connection on a two-connect point valve
is
table_name= 'BLT' // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green
Using the values from the Piping Job Specification (PMC=1C0031, Item Name=6Q1C01), the
actual table name will be
BLT_20_150_5
This table returns the outside diameter, flange thickness, and the seating depth for each end of
the valve. Note that the termination type (20) is used rather than the actual end preparation value
(21).
Specific Tables
The specific tables are used to define the main body of the valve. Refer to Table Requirements
(on page 228) for an outline of the types of tables which are required to place a valve. Since the
termination type is the same at both ends of the valve (bolted), no red connect point data is
required. The required tables are found by referring to the Bolted(G) termination type.
MC_GS_Term(G)_Rat(G)_A (P15A)
MC_GS_Term(G)_Rat(G)_B (P15B) - This table is only required if more than eight
outputs are necessary to define a commodity item.
Commodity Code (P59)
Using this information, the dimension tables for a 6" gate valve are:
GAT_40_20_150_A
This table returns the face-to-center dimension for the valve. Table P15B is not required for
a gate valve.
VAABAHCCAA
This table returns the empty weight of the valve, including the weight of the operator.
If the end preparations were different at each end of the valve (such as female threaded by socket
welded) then a different set of tables would be required.
An additional table look-up is required to access the dimensional data for the valve operator.
The following table is required to define the valve operator.
MC_Type(G)_Rat(G)_Op_A (P31A)
Using this table name format, the dimension table for a hand wheel operator on a 6" gate valve
is:
GAT_BLT_150_3_A
This table returns the stem length and the wheel diameter for the handwheel operator.

196 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Notes for Graphic Commodity Data


Connect Point Data (on page 197)
Bends and Branches (on page 198)
Bolts, Gaskets, and Flanges (on page 199)
Pipe, Tubing, and Hose (on page 199)

Connect Point Data


As described in the Piping Job Specification description, connect point information for
commodity items, piping specialties, and instruments is classified in terms of green and red
connect points. The following conventions are used to coordinate the two sets of data:
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 (on page 131) 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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 197


Graphic Commodity Data

Flanges should be defined with the green connect point representing the flanged connect
point and the red connect point representing the non-flanged connect point.

A valve operator is always placed at the component origin of the corresponding valve body.

To insure consistency in pipe cut length calculations, the connect points of a component
should be located using face-to-face or face- to-center dimension rather than end-to-end or
end-to-center dimension.
A change of direction component placed by component center must be defined such that
connect point 1 is on the primary axis.

Bends and Branches


For bend components (specific and generic), the item name and the new item name must be
unique with respect to the angle of the bend. In other words, you specify the angle of the
bend by selecting the item name for the corresponding angle of the bend.
The number of joints in a miter 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.

198 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

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.

Bolts, Gaskets, and Flanges


The data for the number of bolts and the bolt diameter is available with the flange data in the
Physical Commodity Library as a function of nominal piping diameter, pressure rating,
termination type, and geometric industry standard. However, the bolt data and the flange
data are stored in separate tables. Refer to the Report Manager Reference Guide for a
description of the table access.
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.
Flange data exists in two tables.
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).

Pipe, Tubing, and Hose


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.
Flexible hose has flanged, screwed, or quick disconnect end preparations.

Plant Design System (PDS) Reference Data Manager (PD_Data) 199


Graphic Commodity Data

Graphic Commodity Library Manager


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 (on page 183) 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.

Create Library (on page 201) Used to create a new Graphic Commodity Library.
Compress (on page 201) Used to compress the Graphic Commodity library.
Unapproved ==> Approved (on page 201) Used to copy the unapproved Graphic
Commodity library to the approved library.
Create/Interactive (see "Create/Interactive Graphic Commodity Data" on page 201) Used
to compile Eden source files and insert them in the Graphic Commodity Library. You can
create a file or specify a list of files to be created.
Create/Batch (see "Create/Batch Graphic Commodity Data" on page 202) Used to
compile Eden source files and add the files to the library via batch processing. Used to
compile Eden source files via batch processing.
Revise (see "Revise Graphic Commodity Data" on page 203) Used to select an Eden
module from the library, edit the file, and put the recompiled file back into the library.
Delete (see "Delete Graphic Commodity Data" on page 204) Used to remove an Eden
module from the library.
Report (see "Report Graphic Commodity Data" on page 205) Used to create a report
listing the library contents.

200 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

List (see "List Graphic Commodity Data" on page 206) Used to display the Eden modules
in the library.
Extract (see "Extract Graphic Commodity Data" on page 207) Used to extract an Eden
module from the library for editing or printing.
You can set the toggle at the bottom of the form to determine the Eden modules to be listed.
Full List - Lists all the Eden modules in the Graphic Commodity Library.
Sub-string - Limits the list to those Eden modules which contain a specified substring.

Create Library
This option is used to create a new Graphic Commodity Library. It automatically creates the
object library (.l) and the text library (.l.t) for the library that is being created.
The system displays the approved and unapproved Graphic Commodity Library names as
defined in the RDB Management Data.

Accept to Create or Exit to Avoid Creating New Library


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.

Compress
This option is used to compress the Graphic Commodity library. Any tables which have been
deleted from the library will be removed.

Unapproved ==> Approved


This option copies the unapproved Graphic Commodity library to the approved library.

Accept to Copy or Exit to Avoid Copying


Select Accept to copy the unapproved library file to the approved library.

Create/Interactive Graphic Commodity Data


This option enables you to compile Eden source code and add the resulting code to the graphic
commodity library. You can process a single file or specify a list of files to be created. Refer to
the description of the Graphic Commodity Library (on page 183) for information on naming
conventions for Eden modules.

Before Using This Command


Set Piping Eden Path and Piping Eden Node in the Default Project Control Data to the
location of the Eden source files.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 201


Graphic Commodity Data

Operating Sequence
1. Select the Create option.

2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
4. Key in the name of the Eden file or list file to be compiled and added to the active library.
The system verifies the existence of the specified file.
The system displays the default node name and path for the Eden modules, as specified in
the Default Project Control Data, at the bottom of the form.
You can use the default setting or modify these fields to override the default location for this
operation.
5. Accept or Select Other Option
Accept the file and begin processing.

Create/Batch Graphic Commodity Data


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 (on page 183) for
information on naming conventions for Eden modules.

Before Using This Command


Set Piping Eden Path and Piping Eden Node in the Default Project Control Data to the
location of the Eden source files.
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.
3. Specify Filename for processing
4. Key in the name of the Eden file or list file to be compiled and added to the active library.
The system confirms the existence of the specified file.
The system displays the default node name and path for the Eden modules, as specified in

202 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

the Default Project Control Data, at the bottom of the form.


You can use the default setting or modify these fields to override the default location for this
operation.
5. Accept or Select Other Option
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set the
time to process the source files.
6. Accept the file and begin processing.
The system submits the request to the batch queue PDreference.

Revise Graphic Commodity Data


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.

Before Using This Command


Set the toggle to Full List or Sub-string to determine the Eden modules to be listed.

Operating Sequence
1. Select the Revise option.
The system displays the Eden modules in the Graphic Commodity Library.

2. Select Module for Revision


Select the Eden modules to be revised and select Accept.

Plant Design System (PDS) Reference Data Manager (PD_Data) 203


Graphic Commodity Data

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.

3. 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 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.

Delete Graphic Commodity Data


This option enables you to delete Eden modules from the graphic commodity library.

Before Using This Command


Set the toggle to Full List or Sub-string to determine the Eden modules to be listed.

Operating Sequence
1. Select the Delete option.

204 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

The system displays the Eden modules in the Graphic Commodity Library.

2. Select Module for Deletion


Select the Eden modules to be deleted from the list of modules. You can use the scroll bar to
scroll through the available files.
3. Accept or Select Other Module
Accept the selected modules.
The system deletes the modules from the Graphic Commodity Library.

Report Graphic Commodity Data


This option enables you to create a list file of all the Eden modules in the Graphic Commodity
library and their creation dates.

Operating Sequence
1. Select the Report option from the Data Management form.

Plant Design System (PDS) Reference Data Manager (PD_Data) 205


Graphic Commodity Data

2. Key in the file information for the location of the report file to be created or use the
displayed defaults.
3. Select Print or Print/Save.
Then select the print queue from the list of displayed queues. Refer to the section on Plot
and Print Queues in the Project Administrator Reference Guide for information on setting
up multiple print queues.
If you select the Print/Save option, the system will create a file named piping_eden in the
defined default source file location.
4. Accept to Form Report or Revise Report Parameters
Select Accept to create the report file.

List Graphic Commodity Data


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 revision date of each Piping Eden module.
The module names are sorted alphanumerically within the list for each type of Piping Eden
module.

Before Using This Command


Set the toggle to Full List or Sub-string to determine the Eden modules to be listed.

Operating Sequence
1. Select the List option.

206 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

The system displays the Eden modules in the Graphic Commodity Library.

2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.

Extract Graphic Commodity Data


This option enables you to extract an Eden module or set of Eden modules from the Graphic
Commodity library for editing or printing.

Before Using This Command


Set Piping Eden Path and Piping Eden Node in the Default Project Control Data to the
location of the Eden source files.
Set the toggle to Full List or Sub-string to determine the Eden modules to be listed.

Plant Design System (PDS) Reference Data Manager (PD_Data) 207


Graphic Commodity Data

Operating Sequence
1. Select Extract from the Data Management form.

2. Select EDEN Module for Extraction


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.

Graphic Commodity Modules List


This form allows you to select an Eden module from the library in order to revise, delete, list, or
extract the modules.
For more information, see Revise Graphic Commodity Data (on page 203), Delete Graphic
Commodity Data (on page 204), List Graphic Commodity Data (on page 206), Extract Graphic
Commodity Data (on page 207).

208 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Physical Data Library Manager


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
unapproved library to the approved library. Refer to Physical Data Tables (on page 194) 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.

Before Using This Command


Define the location of the approved and unapproved (if applicable) Physical Data Library
and Spec Table Library files in the Default Project Control Data.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 209


Graphic Commodity Data

2. Select Table Library


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.
4. Select Table Data Management Option
Select the option to perform.

Options
Create Library (on page 211) Used to create a new Physical Dimension Library.
Compress (on page 211) Used to compress the Physical Dimension library.
Unapproved ==> Approved (see "Unapproved to Approved" on page 211) Used to copy
the unapproved Physical Dimension library to the approved library.
Create/Interactive (see "Create/Interactive Physical Commodity Data" on page 211) Used
to process table files and add the resulting code to the active Physical Dimension library.
You can create a single table or specify a list of tables to be created.
Create/Batch (see "Create/Batch Physical Commodity Data" on page 212) Used to
compile and add table files to the active library via batch processing.
Revise (see "Revise Physical Commodity Data" on page 213) Used to select a table file
from the library for editing and put the revised file back into the library.
Delete (see "Delete Physical Commodity Data" on page 214) Used to remove a table file
from the library.

210 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Report (see "Report Physical Commodity Data" on page 215) Used to create a report of
the library contents.
List (see "List Physical Commodity Data" on page 217) Used to display the table files in
the active library.
Extract (see "Extract Physical Commodity Data" on page 217) Used to extract a table file
from the library for editing or printing.

Create Library
This option is used to create a new Physical Dimension Library. It automatically creates the
object library (.l), the text library (.l.t), and table revision management library (.l.t.r) for the
library that is being created.
The system displays the approved and unapproved Physical Dimension Library names as defined
in the RDB Management Data.

Accept to Create or Exit to Avoid Creating New Library


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.

Compress
This option is used to compress the Physical Dimension library. Any tables which have been
deleted from the library will be removed.

Unapproved to Approved
This option copies the unapproved Physical Dimension library to the approved library.

Accept to Copy or Exit to Avoid Copying


Select Accept to copy the unapproved library file to the approved library.

Create/Interactive Physical Commodity Data


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.

Before Using This Command


Set the default table path and node in the Default Project Control Data.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 211


Graphic Commodity Data

Operating Sequence
1. Select the Create option.

2. Set the toggle to Single to process a single source file or to List to process a list file.
3. Specify Filename for processing
Key in the name of the table file or list file to be processed and added to the active library.
The system displays the default node name and path for the table files, as specified in the
Default Project Control Data, at the bottom of the form.
You can use the default setting or modify these fields to override the default location for this
operation.
4. Accept or Select Other Option
Accept the file and begin processing.
The system processes the source file and, if successful, it stores the resulting object file in the
active library and stores the source file in the associated text library.

Create/Batch Physical Commodity Data


This option enables you to process physical dimension table source files and insert the specified
files into the active library via batch processing. 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.

Before Using This Command


Set the default table path and node in the Default Project Control Data.
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.
3. Specify Filename for processing
Key in the name of the table file or list file to be processed and added to the active library.
The system displays the default node name and path for the table files, as specified in the

212 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Default Project Control Data, at the bottom of the form.


You can use the default setting or modify these fields to override the default location for this
operation.
4. Accept or Select Other Option
Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set the
time to process the source files.
5. Accept the file and begin processing.
The system submits the request to the batch queue PDreference.
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.

Revise Physical Commodity Data


This option enables you to select a table file from the library, edit the file, and then put it back in
the library.

Before Using This Command


Set the toggle to Full List or Sub-string to determine the tables to be listed.

Operating Sequence
1. Select the Revise option.
The system displays the table files in the active library.

Plant Design System (PDS) Reference Data Manager (PD_Data) 213


Graphic Commodity Data

2. Select Table for Revision


Select the table files to be revised and select Accept.
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.

3. 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.

Delete Physical Commodity Data


This option enables you to delete a table file or set of table files from the active library. It also
deletes the revision dates from the corresponding Table Revision Management Library.

Before Using This Command


Set the toggle to Full List or Sub-string to determine the tables to be listed.

214 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

Operating Sequence
1. Select the Delete option.
The system displays the table files in the active library.

2. Select Table for Deletion


Select the tables to be deleted from the list of tables. You can use the scroll bar to scroll
through the available files.
3. Accept or Select Other Option
Accept the files and begin processing.
The system deletes the table files from the active library.

Report Physical Commodity Data


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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 215


Graphic Commodity Data

The system displays the reporting options on the form.

2. Revise Report Parameters


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.
5. Select Save, Print, or Print/Save.
Then select the print queue from the list of displayed queues. Refer to the section on Plot
and Print Queues in the Project Administrator Reference Guide for information on setting
up multiple print queues.
If you select the 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).
U.S. Practice us International - JIS jis
European - DIN din International - Australian aus
European - British bs International - Practice A ina
Standard
European - Practice A eua International - Practice B inb

216 Plant Design System (PDS) Reference Data Manager (PD_Data)


Graphic Commodity Data

European - Practice B eub Company Practice cmp


6. Set the toggle to Submit Immediately or Delayed Submit. For Delayed Submit, set the
time to process the request.
7. Accept to Form Report or Revise Report Parameters
Select Accept to create the specified report file.

List Physical Commodity Data


This option displays all the table files for the active library with the revision date of each table.

Before Using This Command


Set the toggle to Full List or Sub-string to determine the tables to be listed.

Operating Sequence
1. Select the List option.
The system displays the table files in the active library.

2. You can use the scroll bar to scroll through the available files.
3. Select Cancel to exit the form.

Extract Physical Commodity Data


This option enables you to extract a table file out of the active library for editing or printing.

Before Using This Command


Set the default table path and node in the Default Project Control Data.
Set the toggle to Full List or Sub-string to determine the tables to be listed.

Plant Design System (PDS) Reference Data Manager (PD_Data) 217


Graphic Commodity Data

Operating Sequence
1. Select Extract from the Data Management form.

2. Select Table for Extraction


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
File: PD_tbl2 is TDINBODY_SPECIFIC_7P1E01_I15AS_A
File: PD_tbl3 is TDINBODY_SPECIFIC_7P1E01_I15AS_B
File: PD_tbl4 is TDINBODY_SPECIFIC_7P1E01_I15AS_C
File: PD_tbl5 is TDINOPER_SPECIFIC_7P1E01_I15AS_A
File: PD_tbl6 is TDINOPER_SPECIFIC_7P1E01_I15AS_B
File: PD_tbl7 is TDINOPER_SPECIFIC_7P1E01_I15AS_C
If the list file is less than 24 hours old, the system appends the entries to the file; otherwise,
it overwrites the file.

218 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 8

Table Formats and Naming Conventions


Tables are used to store data required for interactive processing of piping and instrument
components. This section describes the tables which are included in the physical data libraries.
Refer to Physical Data Tables (on page 194) for more information on these libraries. Also, refer
to Piping Job Specification Tables (on page 131) for more information on tables.
See Also
Table Conventions (on page 219)
Abbreviations (on page 228)
RDB Tables (on page 152)
Generic Tables (on page 232)
Piping Component Tables (on page 246)
Instrument Component Tables (on page 267)
Table Requirements (on page 228)

Table Conventions
Table Names
Unless otherwise indicated, values for specific and generic parameters are stored in tables whose
names are derived from parameters in the PJS. When naming ASCII files in the text libraries, if a
dot (.) or a hyphen (-) is included in the Sc/Th column of the piping job specification, the dot or
hyphen will be converted to a dollar sign ($) when the table name or ASCII file name is created.
The actual character, and not the $, is displayed in all fields representing the actual attribute
involved. The following examples illustrate how thicknesses are represented on the basis of the
above rule:
Actual Characters ASCII
equivalent
.25 $25
1 1
1.375 1$375
With version 5.0, the Physical Data Library Manager will respect the use of a dash (-) in a table
name. This allows you to include a dash in the commodity code for a piping commodity valve,
where the commodity code is used to form the name of the dimension table.
Commodity codes are read verbatim when they are used to create table names. No
conversion of dots (.) or hyphens (-), as described above, takes place. Also note that a dot (.) is
not a valid character to include in a table name. For this reason, they should not be included as
part of commodity codes for valves.

Plant Design System (PDS) Reference Data Manager (PD_Data) 219


Table Formats and Naming Conventions

Comments
You can include any number of comments in a table, using the conventions described below:
For single-line comments:
! XXXXXXXXXXXXXXXXXXXXXXXXXX , or
< XXXXXXXXXXXXXXXXXXXXXXXXXX >
For multi-line comments:
< XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX >
where XXXX... represents the comment text.

Revision Markers
Table entries preceded by a karat (>) have been revised since their original release. For
example, the section of the table shown below has been revised three times since it was first
delivered.

Component Tables
The following conventions apply to the definition of columns in all the tables except tables for
specialty items.
The following line is required to define the number of input and output columns:
No_Inputs x No_Outputs x
The number of input columns must not exceed 2. The number of output columns must not
exceed 9; it can be 0.
The following statements are used in some tables to indicate that values will be interpolated.
Input_Interpolation 1, Next_One
Input_Interpolation 2, Next_One
A definition must be made using the following format regarding the units of measure used in
each column of a table:
Units= NPD_IN, SF, LB, INT, DEC, IN, RAT, IN, IN, IN

220 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Units
Units are defined for each column of a table as follows:
Angle, degrees DEG
Angle between runs, degrees DEC

Area FT2
IN2
YD2
MI2
SCM
SKM

Code-listed attributes INT

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

Plant Design System (PDS) Reference Data Manager (PD_Data) 221


Table Formats and Naming Conventions

Nominal diameter, inches NPD_IN


Nominal diameter, mm NPD_MM

Pressure, psig PSIG


Pressure, pascal gage PAG
Pressure, bar BAR
Pressure, bar (gage) BAR_G
Pressure, atmospheres ATM
Pressure, inches water absolute INH20
Pressure, inches water at 32 deg INH20_32F
Pressure, inches mercury absolute INHG
Pressure, inches mercury at 32 deg INHG_32F
Pressure, kg per cm squared (gage) KG_CM2
Pressure kg per cm squared KG_CM2_A
(absolute)
Pressure, mm water at 4 deg MMH20
Pressure, mm mercury at 32 deg MMHG
Pressure, megaPascal (gage) MPa_g

Rating RAT
CLxxx and xxx# are expressed as xxx

Schedule/thickness, inches SC_TH_IN


Schedule/thickness, millimeters SC_TH_MM

Stress, psi PSI


Stress, pascal PA
Stress, kpa KPA
Stress, mpa MPA

Surface area, square feet SF


Surface area, square meter SM

222 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Surface area, square millimeter SMM

Surface area/unit,
square feet per foot SFF
square meter per meter SM_M
square millimeter per meter SMM_M

Temperature, degrees Celsius DC


Temperature, degrees Fahrenheit DF
Temperature, degrees Kelvin DK
Temperature, degrees Rankine DR

Unitless alphanumeric AN*xx where xx defines the number of


characters

Unitless integer INT


Unitless real number DEC

Weight, pounds LB
Weight, kilogram KG

Weight/unit, pounds per foot LBF


Weight/unit, kilograms per meter KGM

Fields (Input/Output Columns)


Attributes can consist of the following field types. The system determines the field type on
the basis of data provided in each table.
-NPD (for nominal diameter)
-INTEGER2
-REAL4 (floating point)
-AN*x (alphanumeric, where x defines the number of characters up to a maximum of 8)
All entries in the tables are left justified.
Field locations and field lengths defined with XXXXs, WWWWs, and ZZZZZs in this
document are observed.
Fractions are not used to define any table value.
Adjacent columns in a table are separated by one or more spaces.

Plant Design System (PDS) Reference Data Manager (PD_Data) 223


Table Formats and Naming Conventions

If a value in a table is not known, a hyphen (-) must be used in the corresponding field. The
system interprets this entry as a blank value and displays a blank in reports, drawings, and
other data outputs.
Real numbers without decimals can be expressed with or without a decimal point. For
example, a nominal diameter of twenty inches can be expressed as 20, 20. , or 20.0. For
consistency, all delivered tables use the value 20
All alphanumeric values in a table must be enclosed in single quotes (' '). For example,
'ZZZZZ'.
For tables with only one input column, the generic value ET_AL can be used in the input
column. The system translates this entry to indicate that values in the immediately
preceding line apply to any input value equal to or greater than the value in the current line.

NPD Values
The following table is used to correlate English nominal pipe diameters with their corresponding
metric values.
Nominal Pipe Diameter Nominal Pipe Diameter
inches mm inches mm
0.125 6 14.00 350
0.250 8 16.00 400
0.375 10 18.00 450
0.500 15 20.00 500
0.750 20 22.00 550
1.000 25 24.00 600
1.250 32 26.00 650
1.500 40 28.00 700
2.000 50 30.00 750
2.500 65 32.00 800
3.000 80 34.00 850
3.500 90 36.00 900
4.000 100 38.00 950
5.000 125 40.00 1000
6.000 150 42.00 1050
8.000 200 44.00 1100
10.00 250 46.00 1150
12.00 300 48.00 1200

Rating
The following conventions apply to the rating attribute with respect to the naming of data tables:
Ratings can be expressed in the PJS in any of the following formats: CLxxxx, xxxx#, or
OTxxxx. However, table entries and file names representing the rating exclude the CL, #, or
OT characters. This enables the same table to be used regardless of how the rating is
defined. In the delivered PJS, these rating formats are used in accordance with the following
criteria:
CLxxxx refers to an ANSI or API pressure rating
xxxx# refers to a pressure rating defined by an organization other than ANSI or API.
OTxxxx refers to a rating that meets the applicable ANSI or API rating geometrically but not
from a pressure carrying standpoint. An example is a valve supplied with flanged ends

224 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

meeting the bolting pattern of ANSI CL150 pressure rating but with pressure carrying
characteristics different from those of that ANSI rating.
Female ends for plastic pipe are usually defined in terms of schedule/thickness and not in
terms of rating. To make female ends for plastic pipe follow the rules for other female ends,
the applicable schedule/thickness is used as the value for rating. If such rating values
contain alphanumeric characters, the system strips all the alpha characters from the rating
value and uses only the numeric values in accessing the applicable tables.
If the rating in the PJS is expressed in alphabetic characters only, the system uses the
characters to access a data table. The names of the data tables include all the alphabetic
characters included in the PJS.
GRAVHD can be used to identify the rating for components rated to sustain a nominal fluid
head. This value can be used in the PJS and in the data tables.
OTHER can be used to identify a nonstandard rating value.
NONE can be used to identify the rating for components whose ends would normally require
the rating value as part of the table name, but for which a rating does not apply. This value
can be used in the PJS and in the data tables.

Schedule/Thickness
Schedule or thickness values are shown for all applicable components. In order of preference,
schedule and thickness are expressed in terms of:
Generic schedules, such as S-STD, S-XS, and S-XXS. If the schedule name exceeds the
provided field length (for example, S-SDR13.5), it is defined in terms of its wall thickness.
Specific schedules, such as S-40, S-60, and S-80.
NREQD: This value is used in cases where all of the following conditions apply:
The thickness value is not required to purchase the component.
Empty weights are not significantly affected by actual thickness values.
Either stress analysis is not applicable, or the component is considered to be infinitely
rigid in stress analysis calculations.
Specific wall thicknesses: To insure compatibility between the data tables, the PJS, and wall
thickness calculations, thickness is expressed as defined below. Trailing zeroes are not
included. Decimal points are not included for numbers without decimals.
.xxxx if the thickness is less than 1 inch
x if the thickness is an even inch
x.xxx if the thickness is 1 inch or larger
*Cyyy: The need to perform a thickness calculation is triggered by an entry with the format
*Cyyy in the Schedule/Thickness attribute of the Commodity Item entity. The letters that
make up this code have the following meaning:
The character C ensures that the schedule/thickness for the applicable end of the
component is determined by calculations using the thickness equation defined for the
piping materials class in the Default Wall Thickness Equation attribute of the Piping
Materials Class entity.
The characters yyy define the casting, joint or structural grade quality factor (E) times
100. This factor is one of the parameters used in the thickness calculation. If you are

Plant Design System (PDS) Reference Data Manager (PD_Data) 225


Table Formats and Naming Conventions

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.

226 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

To minimize duplication when the same thickness can be expressed for metallic materials in
terms of either a generic or a specific schedule, the following convention is used. For a given
nominal diameter, only the schedules shown in the line for that diameter are used in the PJS and
in the data tables.

Plant Design System (PDS) Reference Data Manager (PD_Data) 227


Table Formats and Naming Conventions

Weight Tables
Weight tables are required for the following thicknesses:
For components made from pipe material:
If the thickness involved is covered by a schedule, tables are required for all
commercially available schedules to the full range of their nominal diameter.
If the thickness involved is not covered by a schedule, tables are required in 1/16 inch
increments from 0.25 to 1.25 inches (inclusive), and from 22 inches to the full range of
their nominal diameter.
For components made from plate material, tables are required in 1/16 inch increments from
0.25 to 1.25 inches and in 1 inch increments from 12 to 144 inches.

Abbreviations
The following abbreviations are used to describe the table name formats in this document.
(G) Green
(R) Red
BrchTbl Branch Table
Cmdty Code Commodity Code
GCP Green Connect Point
GS Geometric Industry Standard (from
CL575)
MC Model Code
Op Operator/actuator type (from CL550)
Rat Pressure Rating
RCP Red Connect Point
Sc/Th Schedule/Thickness
Term End Preparation (from CL330)
TNF Table Name Format
TS Table Suffix (from CL576 and CL577)
Type Termination type (BLT, FEM, or MAL)
WC Weight Code (from CL578)
Refer to Variables for Generic Tables (on page 233) and Variables for Specific Tables (on page
249) for a description of the variables used in table definitions. Generally, values appearing in
all uppercase characters (such as BLT or STUD) indicate a hard-coded value.

228 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Table Requirements
This section indicates which tables are required to place a particular type of component (such as
a valve or fitting). The table groups listed in this section are used to store data required for
interactive processing of piping and instrument components. The applicability of the various
table groups is defined as a function of the termination types of the components as defined in the
Piping Job Specification (PJS).
Refer to the PDS Piping Component Data Reference Guide for a detailed description of the
requirements for specific commodity items, instruments, and miscellaneous piping and
instrument items.
Typically, the tables in the table combinations are used to store:
The surface area and weight of water for the component.
The dimensional parameters for the component.
The empty weight of the component and/or data about valve operators.
Tables Required for Piping Components (on page 229)
Tables Required for Instrument Components (on page 232)

Tables Required for Piping Components


Valves (6Q1C) (on page 230)
Fittings (6P2C, 6P3C, 6Q2C, and 6Q3C) (on page 231)
Fire and Safety Piping Components (6P4C and 6Q4C) (on page 232)
Specialty Piping Components (6P6C and 6Q6C) (on page 232)

Plant Design System (PDS) Reference Data Manager (PD_Data) 229


Table Formats and Naming Conventions

Valves (6Q1C)
Termination Types Applicable Tables
Bolted(G) P15A MC_GS_Term(G)_Rat(G)_A
Male(G) P15B MC_GS_Term(G)_Rat(G)_B
Female(G) P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Bolted(G)-Male(R) P25A MC_GS_Term(G)_Rat(G)_Term(R)_A
Female(G)-Male(R) P25B MC_GS_Term(G)_Rat(G)_Term(R)_B
P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Bolted(G)-Bolted(R) P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
Bolted(G)-Female(R) P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B
Female(G)-Female(R) P59 Cmdty Code (if operator code <=24)
Female(G)-Bolted(R) P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Male(G)-Male(R) P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B
P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Male(G)-Female(R) P27A MC_GS_Term(G)_Term(R)_Rat(R)_A
Male(G)-Bolted(R) P27B MC_GS_Term(G)_Term(R)_Rat(R)_B
P59 Cmdty Code (if operator code <=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
Operators P31A MC_Term(G)_Rat(G)_Op_A (if operator code
<=24)
P31B MC_Term(G)_Rat(G)_Op_B (if operator code
<=24)
P60A Cmdty Code_WOPD_A (if operator code >24 &
<=40)
P60B Cmdty Code_WOPD_B (if operator code >24 &
<=40)

230 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Fittings (6P2C, 6P3C, 6Q2C, and 6Q3C)


Termination Types Applicable Tables
Male(G) P11A MC_GS_Term(G)_A
P11B MC_GS_Term(G)_B
P51 MC_GS_Term(G)_Sc/Th(G)_WC
Bolted(G) P15A MC_GS_Term(G)_Rat(G)_A
Female(G) P15B MC_GS_Term(G)_Rat(G)_B
P52 MC_GS_Term(G)_Rat(G)_Sc/Th(G)_WC
Bolted(G)-Male(R) P25A MC_GS_Term(G)_Rat(G)_Term(R)_A
Female(G)-Male(R) P25B MC_GS_Term(G)_Rat(G)_Term(R)_B
P61
MC_GS_Term(G)_Rat(G)_Term(R)_Rat/Sc/Th(R)_WC
Bolted(G)-Bolted(R) P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
Bolted(G)-Female(R) P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B
Female(G)-Female(R) P62
MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_Sc/Th(R)_WC
Female(G)-Bolted(R)
Male(G)-Male(R) P21A MC_GS_Term(G)_Term(R)_A
P21B MC_GS_Term(G)_Term(R)_B
P63
MC_GS_Term(G)_Sc/Th(G)_Term(R)_Sc/Th(R)_WC
Excludes olet and stubbing type fittings
Male(G)-Bolted(R) P27A MC_GS_Term(G)_Term(R)_Rat(R)_A
Male(G)-Female(R) P27B MC_GS_Term(G)_Term(R)_Rat(R)_B
P64 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat(R)_WC
Excludes olet and stubbing type fittings
Olet fittings P28A
MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_A
P28B
MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_B
P65
MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_WC
Stubbing fittings P29A MC_GS_BrchTbl_Angle_A
Overflow and weight tables do not apply.

Plant Design System (PDS) Reference Data Manager (PD_Data) 231


Table Formats and Naming Conventions

Fire and Safety Piping Components (6P4C and 6Q4C)


Termination Types Applicable Tables
Male(G) P11A MC_GS_Term(G)_A
P11B MC_GS_Term(G)_B
P51 MC_GS_Term(G)_Sc/Th(G)_WC
Bolted(G) P15A MC_GS_Term(G)_Rat(G)_A
Female(G) P15B MC_GS_Term(G)_Rat(G)_B
P52 MC_GS_Term(G)_Rat(G)_Sc/Th(G)_WC
Bolted(G)-Male(R) P25A MC_GS_Term(G)_Rat(G)_Term(R)_A
Female(G)-Male(R) P25B MC_GS_Term(G)_Rat(G)_Term(R)_B
P61
MC_GS_Term(G)_Rat(G)_Term(R)_Rat/Sc/Th(R)_WC
Bolted(G)-Bolted(R) P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_A
Bolted(G)-Female(R) P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B
Female(G)-Female(R) P62
MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_Sc/Th(R)_WC
Female(G)-Bolted(R)
Male(G)-Male(R) P21A MC_GS_Term(G)_Term(R)_A
P21B MC_GS_Term(G)_Term(R)_B
P63
MC_GS_Term(G)_Sc/Th(G)_Term(R)_Sc/Th(R)_WC
Male(G)-Bolted(R) P27A MC_GS_Term(G)_Term(R)_Rat(R)_A
Male(G)-Female(R) P27B MC_GS_Term(G)_Term(R)_Rat(R)_B
P64 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat(R)_WC

Specialty Piping Components (6P6C and 6Q6C)


P80 Specialty Body Data
P81 Operator/Actuator Data

Tables Required for Instrument Components


The following table sets are used for instrument component classes 7P1E (Control Valves and
Regulators), 7P2C (Relief Devices), 7P3C (Other in-line Instruments), and 7Q4D (Off-Line
Instruments).
I80 Inbody_Specific_AABBCC_MC_n
Inbody_Typical_AABBCC_MC_n
I81 Inoper_Specific_AABBCC_MC_n
Inoper_Typical_AABBCC_MC_n

232 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Generic Tables
This section describes the neutral file formats used to define generic piping and instrument data.
The following tables are required to store generic data which applies to both piping and
instrument components:

TNF Attributes Used to Form Table Name


G10 BLT_Term_Rat_TS (see "Generic Table for Bolted Ends (G10)" on page
237)
G12 STUD_Rat_TS (see "Generic Table for Studs used in Bolted Connections
(G12)" on page 239)
G12T STUD_Term_Rat_TS (see "Generic Table for Studs in Bolted
Connections w/ Term Type (G12T)" on page 241)
G20 MAL_Term_TS (see "Generic Table for Male Ends (G20)" on page 243)
G30 FEM_Term_Rat/Sc/Th_TS (see "Generic Table for Female Ends (G30)"
on page 244)
G50 MALWT_Term_Rat/Sc/Th_TS_WC (see "Generic Table for Weight and
Thickness Data, Male Ends (G50)" on page 245)
These tables are stored in the physical data library.
Table format G14, COMPAT_Rat(low)_TS_Rat(high)_TS, which was used with the
VAX Piping Design product, is not used by the Workstation product. This table format may be
included in the physical data library but it will not be accessed by the product.
See Also
Variables for Generic Tables (on page 233)

Plant Design System (PDS) Reference Data Manager (PD_Data) 233


Table Formats and Naming Conventions

Variables for Generic Tables


The letters P through Z are used in the generic tables to represent the following generic
variables.

Variable End Type Explanation

P Bolted This is the outside diameter of a bolted end of the


indicated termination type, rating, and nominal
diameter, as defined in the table named
"BLT_Term_Rat_TS".
Male This is the outside diameter of a male end of the
indicated termination type and nominal diameter, as
defined in the table named "MAL_Term_TS".
Female The is the outside diameter of the female end of the
component of the indicated termination type, rating,
and nominal diameter, as defined in the table named
"FEM_Term_Rat_TS". For model graphics, it is
desirable for the value of this parameter to be larger
than the value of the matching male termination end.
However, components such as 90 degree elbows and
tees will not place if the value is too large. Therefore,
the following values have been defined for this
parameter:
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.

Q Bolted Not applicable.

Male The value of this variable is "0" for all male ends.

234 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Variable End Type Explanation

Female This is the depth of socket, as defined in the table


named "FEM_Term_Rat_TS".
For socketwelded ends, this value is the nominal depth
of the socket less 1/16". The actual depth of socket
less 1/16" is used to determine a component's
dimensional parameters.
For female threaded ends, this is the thread
engagement as defined: in Table 8-1 for components
complying with ANSI-B16.12 and in Table 8-2 for all
other components.

R Bolted This is the flange thickness, as defined in the table


named "BLT_Term_Rat_TS". This dimension
represents the distance from the outermost face of the
flange to the back surface of the flange on which the
nut rests. It includes any projections of the flange,
such as the raised face.
For lap-flanged ends, it includes the thickness of the
pipe or stub end plus the thickness of the loose flange
used. If the Source of Bolt Spec Data is set as a
function of termination type, rating, and table suffix in
the RDB, the entries for the lap type terminations in
the BLT_Term* and STUD_Term* generic tables
provide for the addition of wall thickness from the
TDB.
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.
Male Not applicable.

Female Not applicable.

Plant Design System (PDS) Reference Data Manager (PD_Data) 235


Table Formats and Naming Conventions

Variable End Type Explanation

S Bolted This is the seating depth, as defined in the table named


"BLT_Term_Rat_TS". This dimension represents the
distance from the outermost surface of the bolted end
to the seating surface of the gasket. It will only have a
value for small groove, large groove, small female and
large female flanged ends, and for mechanical joints.
The value of this parameter will be zero for all other
bolted ends.
Male Not applicable.
Female Not applicable.

T Bolted This is half of the gasket gap thickness, as defined in


the PJS for the applicable piping materials class.
Male Not applicable.
Female Not applicable.

V Bolted This is the diameter of bolts required at a bolted


connection, as defined in the table named
"STUD_Rat_TS" as a function of the nominal pipe
diameter, rating, and table suffix of the applicable
bolted end.
Male Not applicable.
Female Not applicable.

X Bolted Not applicable.


Male This is the wall thickness of the applicable end of a
component of the indicated nominal diameter, as
defined in the table named
"MALWT_Term_Sc/Th_TS_WC".
Female Not applicable.

Z Any No specific meaning is attached to this variable.

236 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Table 8-1. Thread Engagement for


Components per ANSI-B16.12
Thread Engagement, inches
NPD in ANSI-B16.12 PDS
1.25 0.42 0.42
1.5 0.42 0.42
2 0.44 0.44
2.5 0.68 0.68
3 0.77 0.77
4 0.84 0.84
5 0.94 0.94
6 0.96 0.96
8 1.06 1.06

Table 8-2. Thread Engagement for All Other


Components
Thread Engagement, inches

NPD NAVCO ANSI- Stockha Crane Average PDS


in B1.20.1 m
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.3751 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

Generic Table for Bolted Ends (G10)


This table enables you to define the outside diameter, flange thickness, seating depth, and bolt
circle diameter for components with bolted ends.
The table name format for this table is:
For TNF=G10 BLT_Term_Rat_TS

Plant Design System (PDS) Reference Data Manager (PD_Data) 237


Table Formats and Naming Conventions

Neutral File Format


Table_Data_Definition
'BLT_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G10 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 4
Units= NPD_IN, IN, IN, IN, IN
! Diam P R S BCD
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
END

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

238 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

24 32 1.875 0 29.5
26 30.9375 1.625 0 29.3125
28 32.9375 1.75 0 31.3125
30 34.9375 1.75 0 33.3125
32 37.0625 1.8125 0 35.4375
34 39.5625 1.9375 0 37.6875
36 41.625 2.0625 0 39.75
38 44.25 2.125 0 42.125
40 46.25 2.1875 0 44.125
42 48.25 2.3125 0 46.125
44 50.25 2.375 0 48.125
46 52.8125 2.4375 0 50.5625
48 54.8125 2.5625 0 52.5625
50 56.8125 2.6875 0 54.5625
52 58.8125 2.75 0 56.5625
54 61 2.8125 0 58.75
56 63 2.875 0 60.75
58 65.9375 2.9375 0 63.4375
60 67.9375 3 0 65.4375
END

Generic Table for Studs used in Bolted Connections (G12)


This table defines the number of bolts, the bolt diameter, and the bolt extension for a given NPD,
for studs in bolted connections. If the Length Calculation toggle on the Material Takeoff
Option form is set to Almost Precise in Project Administrator, the bolt spec data is set as a
function of rating and table suffix.
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.
The table name format for this table is:
For TNF=G12 STUD_Rat_TS
This table is accessed using values for rating and table suffix derived from the applicable flanged
end.

Neutral File Format

Table_Data_Definition
'STUD_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G12 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5

Plant Design System (PDS) Reference Data Manager (PD_Data) 239


Table Formats and Naming Conventions

WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ


ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

Example

Table_Data_Definition
'STUD_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G12 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

240 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Generic Table for Studs in Bolted Connections w/ Term Type


(G12T)
This table defines the number of bolts, the bolt diameter, and the bolt extension for a given NPD,
for studs in bolted connections. If the Length Calculation toggle on the Material Takeoff
Option form is set to Precise in Project Administrator, the bolt spec data is set as a function
of termination type, rating, and table suffix.
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.
The table name format for this table is:
STUD_Term_Rat_TS
This table is accessed using values for termination type, rating and table suffix derived from the
applicable flanged end.

Neutral File Format

Table_Data_Definition
'STUD_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source= PIPING RDB DATA MANUAL
! Parameter W_2 equals 50% of applicable stud diameter plus W_0.
! TNF=G12T By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

Plant Design System (PDS) Reference Data Manager (PD_Data) 241


Table Formats and Naming Conventions

Example

Table_Data_Definition 'STUD_20_150_5'
! Description= CL150 bolting
! Source= PIPING RDB DATA MANUAL
! Parameter W_2 equals 50% of applicable stud diameter plus W_0.
! TNF=G12T By=GJH Ckd By=NP Rev=0 Date=04-Oct-
1989
No_Inputs 1 No_Outputs 8
Units= NPD_IN, INT, IN, IN, IN, IN, IN, IN, IN
! Diam U V W_0 W_1 W_2 W_3 W_4
W_5
0.5 4 0.5 0.625 1 - - - -
0.75 4 0.5 0.6875 0.875 - - - -
1 4 0.5 0.625 1 - - - -
1.25 4 0.5 0.6875 0.875 - - - -
1.5 4 0.5 0.625 1 - - - -
2 4 0.625 0.8125 1.125 - - - -
2.5 4 0.625 0.8125 1.125 - - - -
3 4 0.625 0.75 1 - - - -
3.5 8 0.625 0.75 1 - - - -
4 8 0.625 0.75 1 - - - -
5 8 0.75 0.875 1.25 1.25 - - -
6 8 0.75 0.9375 1.125 1.3125 - - -
8 8 0.75 0.9375 1.125 1.3125 - - -
10 12 0.875 1 1.5 1.4375 - - -
12 12 0.875 1.0625 1.375 1.5 - - -
14 12 1 1.1875 1.625 1.6875 - - -
16 16 1 1.125 1.5 1.625 - - -
18 16 1.125 1.25 1.75 1.8125 - - -
20 20 1.125 1.375 2 1.9375 - - -
24 20 1.25 1.4375 2.125 2.0625 - - -
26 36 0.75 1.0625 1.375 1.4375 - - -
28 40 0.75 1.0625 1.375 1.4375 - - -
30 44 0.75 1.0625 1.375 1.4375 - - -
32 48 0.75 1 1.5 1.375 - - -
34 40 0.875 1.125 1.75 1.5625 - - -
36 44 0.875 1.125 1.75 1.5625 - - -
38 40 1 1.3125 1.875 1.8125 - - -
40 44 1 1.25 2 1.75 - - -
42 48 1 1.25 1.75 1.75 - - -
44 52 1 1.3125 1.875 1.8125 - - -
46 40 1.125 1.5 2 2.0625 - - -
48 44 1.125 1.375 2 1.9375 - - -
50 48 1.125 1.375 2 1.9375 - - -
52 52 1.125 1.4375 2.125 2 - - -
54 56 1.125 1.375 2 1.9375 - - -
56 60 1.125 1.4375 2.125 2 - - -
58 48 1.25 1.5 2.25 2.125 - - -
60 52 1.25 1.5625 2.125 2.1875 - - -
END

242 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Generic Table for Male Ends (G20)


This table enables you to define the surface area, water weight, outside diameter, and 1/2 pipe
OD for components with male ends.
The table name format for this table is:
For TNF=G20 MAL_Term_TS

Neutral File Format

Table_Data_Definition
'MAL_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G20 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 3
Units= NPD_IN, SFF, IN, IN
! Unt Sur
! Diam Area P P/2
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ
END

Example

Table_Data_Definition 'MAL_300_5'
! Description= Pipe outside diameters
! Source= ANSI-B-36.10M, 36.19M, API-5L, 5LE, 5LP, 5LS & 5LU
! TNF=G20 By=GJH Ckd By=RJW Rev=0 Date=10-Sep-
1987
No_Inputs 1 No_Outputs 3
Units= NPD_IN, SFF, IN, IN
! Unt Sur
! Diam Area P P/2
0.125 0.106 0.405 0.2025
0.25 0.141 0.54 0.27
0.375 0.177 0.675 0.3375
0.5 0.22 0.84 0.42
0.75 0.275 1.05 0.525
1 0.344 1.315 0.6575
1.25 0.434 1.66 0.83
1.5 0.497 1.9 0.95
2 0.622 2.375 1.1875
2.5 0.753 2.875 1.4375

Plant Design System (PDS) Reference Data Manager (PD_Data) 243


Table Formats and Naming Conventions

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
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
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

Generic Table for Female Ends (G30)


This table enables you to define the outside diameter and depth of socket for female ends.
The table name format for this table is:
For TNF=G30 FEM_Term_Rat/Sc/Th_TS

Neutral File Format

Table_Data_Definition
'FEM_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=G30 By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 2

244 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Units= NPD_IN, IN, IN


! Diam P Q
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ
END

Example

Table_Data_Definition 'FEM_420_150_5'
! Description= CL150 socketwelded flange hub O.D. and socketwelded
valve O.D.
! Source= ANSI-B16.11 CL3000 for .125 to .375 dia's, ANSI-B16.5 above
.375 dia.
! TNF=G30 By=GJH Ckd By=JPF Rev=0 Date=29-May-
1986
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! Diam P Q
0.125 0.486 0.3125
0.25 0.6353 0.3125
0.375 0.7755 0.3125
0.5 0.9443 0.3125
0.75 1.185 0.375
1 1.5018 0.4375
1.25 1.8558 0.5
1.5 2.0988 0.5625
2 2.5813 0.625
2.5 3.0813 0.6875
3 3.725 0.75
END

Generic Table for Weight and Thickness Data, Male Ends


(G50)
This table enables you to define empty weight and wall thickness data for male ends.
The table name format for this table is:
For TNF=G50 MALWT_Term_Rat/Sc/Th_TS_WC

Neutral File Format

Table_Data_Definition
'MALWT_WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Plant Design System (PDS) Reference Data Manager (PD_Data) 245


Table Formats and Naming Conventions

! 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

246 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Piping Component Tables


This section describes the table formats used to define component data. The following tables are
required to store component-specific data required for interactive processing of piping
components:
These tables are stored in the physical data library.
Use tables P11*-P20* for piping component data based only on green connect point data.

TNF Attributes Used to Form Table


Name
P11A MC_GS_Term(G)_A (see "Piping
Component Table for GCP Data (P11A,
P15A)" on page 253)
P11B MC_GS_Term(G)_B (see "Piping
Component Table GCP Overflow Data
(P11B, P15B)" on page 254)
P15A MC_GS_Term(G)_Rat(G)_A
P15B MC_GS_Term(G)_Rat(G)_B
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) (on page 255) and Piping Component Table Green and Red CP
Overflow Data (P21B, P25B, P26B, P27B, P28B) (see "Piping Component Table Green and Red
CP Overflow Data (P21B,P25B,P26B,P27B,P28B)" on page 257).

TNF Attributes Used to Form Table Name


P21A MC_GS_Term(G)_Term(R)_A
P21B MC_GS_Term(G)_Term(R)_B
P25A MC_GS_Term(G)_Rat(G)_Term(R)_A
P25B MC_GS_Term(G)_Rat(G)_Term(R)_B
P26A MC_GS_Term(G)_Rat(G)_Term(R)_Rat(
R)_A
P26B MC_GS_Term(G)_Rat(G)_Term(R)_Rat(
R)_B
P27A MC_GS_Term(G)_Term(R)_Rat(R)_A
P27B MC_GS_Term(G)_Term(R)_Rat(R)_B
P28A MC_GS_Term(G)_Sc/Th(G)_Term(R)_Ra
t/Sc/Th(R)_A
P28B MC_GS_Term(G)_Sc/Th(G)_Term(R)_Ra
t/Sc/Th(R)_B

Plant Design System (PDS) Reference Data Manager (PD_Data) 247


Table Formats and Naming Conventions

TNF Attributes Used to Form Table Name


P29A MC_GS_BrchTbl_Angle_A
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.

TNF Attributes Used to Form Table


Name
P31A MC_Type(G)_Rat(G)_Op_A (see "Piping
Component Table for Operators and
Actuators (P31A)" on page 258)
P31B MC_Type(G)_Rat(G)_Op_B (see "Piping
Component Table for Operators and
Actuators, Overflow Data (P31B)" on
page 260)
Use tables P51-P58 for non-valve piping component empty weights based on green connect
point data.

TNF Attributes Used to Form Table Name


P51 MC_GS_Term(G)_Sc/Th(G)_WC (see
"Piping Component Table for Empty
Weight based on GCP Data (P51,P52,P59)"
on page 260)
P52 MC_GS_Term(G)_Rat(G)_Sc/Th(G)_WC
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.
P59 Cmdty Code
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.
P60A Cmdty Code_WOPD_A
(see "Piping
Component Table For
Empty Weight of
Valves (P60A)" on
page 263)
P60B Cmdty Code_WOPD_B
(see "Piping

248 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Component Table For


Empty Weight of
Valves, Overflow Data
(P60B)" on page 264)
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) (see "Piping Component Table for Empty Weight based on
GCP and RCP Data (P61,P62,P63,P64,P65)" on page 265) for more information.

TNF Attributes Used to Form Table Name


P61 MC_GS_Term(G)_Rat(G)_Term(R)_Rat/Sc/Th(R)_WC

P62 MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_Sc/Th(R)_W
C
P63 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Sc/Th(R)_WC

P64 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat(R)_WC

P65 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_WC
Use tables P80 and P81 for data about piping specialty components defined in the Material
Reference Database. See Piping Component Tables for Specialty Components (on page 266) for
more information.
P80 Specialty Body Data
P81 Operator/Actuator
Data
See Also
Variables for Specific Tables (on page 249)

Variables for Specific Tables


Letters A through O represent variables which are specific to a component.

Variable End Type Explanation


A Any For components with identical end terminations
and branches (if any) that are normal to the main
axis of the component, this is the distance from
the origin of the component to the outermost face
of any of its ends.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to the outermost face of
the end in the vicinity of PCP1.

Plant Design System (PDS) Reference Data Manager (PD_Data) 249


Table Formats and Naming Conventions

Variable End Type Explanation


Bolted This value is included in the appropriate
dimension table.
Male Not applicable.
Female This value can be deduced from the expression E
+ Q using the values of E and Q from the
appropriate tables.

B Any For components with identical end terminations


and branches (if any) that are normal to the main
axis of the component, this parameter does not
apply.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to the outermost face of
the end in the vicinity of PCP2.
Bolted This value is included in the appropriate
dimension table.
Male Not applicable.
Female This value can be deduced from the expression F
+ Q using the values of F and Q from the
appropriate tables.

C Any For components with identical end terminations


and branches (if any) that are normal to the main
axis of the component, this parameter does not
apply.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to the outermost face of
the end in the vicinity of PCP3.
Bolted This value is included in the appropriate
dimension table.
Male Not applicable.
Female This value can be deduced from the expression G
+ Q using values of G and Q from the
appropriate tables.

250 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Variable End Type Explanation


D Any For components with identical end terminations
and branches (if any) that are normal to the main
axis of the component, this parameter does not
apply.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to the outermost face of
the end in the vicinity of PCP4.
Bolted This value is included in the appropriate
dimension table.
Male Not applicable.
Female This value can be deduced from the expression H
+ Q using values of H and Q from the
appropriate tables.

E Any For components with identical end terminations


and branches (if any) that are normal to the main
axis of the component, this is the distance from
the origin of the component to any of its PCPs.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to PCP1.
Bolted This parameter can be deduced from the
expression A + T using the values of A and T
from the appropriate tables.
Male This value is included in the appropriate
dimension table.
Female This value is included in the appropriate
dimension table.

F Any For components with identical end terminations


and branches (if any) that are normal to the main
axis of the component, this parameter does not
apply.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to PCP2.

Plant Design System (PDS) Reference Data Manager (PD_Data) 251


Table Formats and Naming Conventions

Variable End Type Explanation


Bolted This parameter can be deduced from the
expression B + T using the values of B and T
from the appropriate tables.
Male This value is included in the appropriate
dimension table.
Female This value is included in the appropriate
dimension table.

G Any For components with identical end terminations


and branches (if any) that are normal to the main
axis of the component, this parameter does not
apply.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to PCP3.
Bolted This parameter can be deduced from the
expression C + T using values of C and T from
the appropriate tables.
Male This value is included in the appropriate
dimension table.
Female This value is included in the appropriate
dimension table.

H Any For components with identical end terminations


and branches (if any) that are normal to the main
axis of the component, this parameter does not
apply.
For components with different end terminations
or branches that are not normal to the main axis
of the component, this is the distance from the
origin of the component to PCP4.
Bolted This parameter can be deduced from the
expression D + T using the values of D and T
from the appropriate tables.
Male This value is included in the appropriate
dimension table.
Female This value is included in the appropriate
dimension table.

252 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Variable End Type Explanation

I,J,K,L,M, Any These values are used in dimension tables for


N specific components as required by the
component being defined.

O Any This is the overall length of the component


considering the outermost surface at each end of
the component.

Piping Component Table for GCP Data (P11A, P15A)


This table enables you to define general parameters for components which require only green
connect point data.
The table name formats for this table are:
For TNF=P11A MC_GS_Term(G)_A For TNF=P15A MC_GS_Term(G)_Rat(G)_A

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

Plant Design System (PDS) Reference Data Manager (PD_Data) 253


Table Formats and Naming Conventions

Example

Table_Data_Definition 'GAT_40_20_150_A'
! Description= CL150 gate valve raised face flanged ends
! Source= ANSI-B16.10-1986
! TNF=P15A By=GJH Ckd By=RJW Rev=1 Date=29-Oct-
1987
! SN=V1 Par 1=A
No_Inputs 1 No_Outputs 3
Units= NPD_IN, SF, LB, IN
! GCP Surf Water Dimensional Parameters
! Diam Area Weight Par 1
0.25 - - 2
0.375 - - 2
0.5 - - 2.125
0.75 - - 2.3125
1 - - 2.5
1.25 - - 2.75
1.5 - - 3.25
2 - - 3.5
2.5 - - 3.75
3 - - 4
4 - - 4.5
5 - - 5
6 - - 5.25
8 - - 5.75
10 - - 6.5
12 - - 7
14 - - 7.5
16 - - 8
18 - - 8.5
20 - - 9
24 - - 10
26 - - 11
28 - - 12
30 - - 12
36 - - 14
END

Piping Component Table GCP Overflow Data (P11B, P15B)


This table enables you to define overflow parameters for components to which table name
formats P11A and P15A apply.
The table name formats for this table are:
For TNF=P11B MC_GS_Term(G)_B For TNF=P15B MC_GS_Term(G)_Rat(G)_B

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

254 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

! 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

Piping Component Table Green and Red CP Data (P21A,


P25A, P26A, P27A, P28A, P29A)
This table enables you to define parameters for components which require both green and red
connect point data.
The table name formats for this table are:
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

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
No_Inputs 2 No_Outputs 7
Units= NPD_IN, NPD_IN, SF, LB, IN, IN, IN, IN, IN
! Nom Diam Surf Weight Dimensional Parameters

Plant Design System (PDS) Reference Data Manager (PD_Data) 255


Table Formats and Naming Conventions

! GCP RCP Area Water Par 1 Par 2 Par 3 Par 4


Par 5
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

Example
Table_Data_Definition 'E90R_39_300_300_A'
! Description= 90 deg long radius reducing elbow beveled ends
! Source= ANSI-B16.9-1978
! TNF=P21A By=GJH Ckd By=JPF Rev=0 Date=15-May-
1986
! SN=F84 Par 1=E Par 2=K Par 3=F Par 4=L
No_Inputs 2 No_Outputs 6
Units= NPD_IN, NPD_IN, SF, LB, IN, IN, IN, IN
! Nom Diam Surf Weight Dimensional Parameters
! GCP RCP Area Water Par 1 Par 2 Par 3 Par 4
2 1 - - 3 0.53 3 0.53
2 1.25 - - 3 0.3575 3 0.3575
2 1.5 - - 3 0.2375 3 0.2375
2.5 1.25 - - 3.75 0.6075 3.75 0.6075
2.5 1.5 - - 3.75 0.4875 3.75 0.4875
2.5 2 - - 3.75 0.25 3.75 0.25
3 1.5 - - 4.5 0.8 4.5 0.8
3 2 - - 4.5 0.5625 4.5 0.5625
3 2.5 - - 4.5 0.3125 4.5 0.3125
3.5 2 - - 5.25 0.8125 5.25 0.8125
3.5 2.5 - - 5.25 0.5625 5.25 0.5625
3.5 3 - - 5.25 0.25 5.25 0.25
4 2 - - 6 1.0625 6 1.0625
4 2.5 - - 6 0.8125 6 0.8125
4 3 - - 6 0.5 6 0.5
4 3.5 - - 6 0.25 6 0.25
5 2.5 - - 7.5 1.3438 7.5 1.3438
5 3 - - 7.5 1.0313 7.5 1.0313
5 3.5 - - 7.5 0.7813 7.5 0.7813
5 4 - - 7.5 0.5313 7.5 0.5313
6 3 - - 9 1.5625 9 1.5625
6 3.5 - - 9 1.3125 9 1.3125
6 4 - - 9 1.0625 9 1.0625
6 5 - - 9 0.5312 9 0.5312
8 4 - - 12 2.0625 12 2.0625
8 5 - - 12 1.5312 12 1.5312
8 6 - - 12 1 12 1

256 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

10 5 - - 15 2.5937 15 2.5937
10 6 - - 15 2.0625 15 2.0625
10 8 - - 15 1.0625 15 1.0625
12 6 - - 18 3.0625 18 3.0625
12 8 - - 18 2.0625 18 2.0625
12 10 - - 18 1 18 1
14 8 - - 21 2.6875 21 2.6875
14 10 - - 21 1.625 21 1.625
14 12 - - 21 0.625 21 0.625
16 10 - - 24 2.625 24 2.625
16 12 - - 24 1.625 24 1.625
16 14 - - 24 1 24 1
18 10 - - 27 3.625 27 3.625
18 12 - - 27 2.625 27 2.625
18 14 - - 27 2 27 2
18 16 - - 27 1 27 1
20 10 - - 30 4.625 30 4.625
20 12 - - 30 3.625 30 3.625
20 14 - - 30 3 30 3
20 16 - - 30 2 30 2
20 18 - - 30 1 30 1
24 12 - - 36 5.625 36 5.625
24 14 - - 36 5 36 5
24 16 - - 36 4 36 4
24 18 - - 36 3 36 3
24 20 - - 36 2 36 2
24 22 - - 36 1 36 1
END

Piping Component Table Green and Red CP Overflow Data


(P21B,P25B,P26B,P27B,P28B)
This table enables you to define overflow parameters for components to which table name
formats P21A, P25A, P26A, P27A, and P28A apply.
The table name formats for this table are:
For TNF=P21B MC_GS_Term(G)_Term(R)_B For TNF=P25B
MC_GS_Term(G)_Rat(G)_Term(R)_B For TNF=P26B
MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_B For TNF=P27B
MC_GS_Term(G)_Term(R)_Rat(R)_B For TNF=P28B
MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_B

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ

Plant Design System (PDS) Reference Data Manager (PD_Data) 257


Table Formats and Naming Conventions

! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ


! Par 5=ZZ Par 6=ZZ Par 7=ZZ
No_Inputs 2 No_Outputs 7
Units= NPD_IN, NPD_IN, IN, IN, IN, IN, IN, IN, IN
! Nom Diam Dimensional Parameters
! GCP RCP Par 1 Par 2 Par 3 Par 4 Par 5 Par 6
Par 7
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

Piping Component Table for Operators and Actuators (P31A)


This table enables you to define parameters for valve operators of piping valves whose operator
code list values (as defined in CL550 - Operator/Actuator Type) are equal to or less than 24.
The table name format that applies to this table is:
For TNF=P31A MC_Type(G)_Rat(G)_Op_A
where Type can have the following possible values:

Preparation Type
2-199 BLT
300-399 MAL
400-599 FEM

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P31Y By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ Par 6=ZZ Par 7=ZZ Par 8=ZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2 Par 3 Par 4 Par 5 Par 6 Par 7
Par 8

258 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

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_BLT_150_3_A'
! Description=Stem and handwheel operator
! Source=PDS Document 2630-33-OP
! TNF=P31A By=GJH Ckd By=RJW Rev=0 Date=26-Feb-
1987
! SN=OP3 Par 1=Y1 Par 2=Y2
No_Inputs 1 No_Outputs 2
Units= NPD_IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2
0.25 8.375 3.75
0.375 8.375 3.75
0.5 8.375 3.75
0.75 9.25 4.125
1 11.875 6
1.25 12.5 6
1.5 17.75 10
2 17.813 10
2.5 20.125 10
3 22.375 12
4 28.188 13.75
5 31.75 13.75
6 35.375 15.5
8 45 19.5
10 52.5 19.5
12 61.125 20
14 70.5 24
16 79.75 28
18 89 30
20 97.25 30
22 105 30
24 112.75 36
26 116 36
28 123.25 36
30 140 36
32 145 36
34 150 36
36 155.5 36
END

Plant Design System (PDS) Reference Data Manager (PD_Data) 259


Table Formats and Naming Conventions

Piping Component Table for Operators and Actuators,


Overflow Data (P31B)
This table enables you to define overflow parameters for operators to which table name format
P31A applies.
The table name format that applies to this table is:
For TNF=P31B MC_Type(G)_Rat(G)_Op_B
where Type can have the following possible values:

Preparation Type
2-199 BLT
300-399 MAL
400-599 FEM

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P31B By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ Par 1=ZZ Par 2=ZZ Par 3=ZZ Par 4=ZZ
! Par 5=ZZ Par 6=ZZ Par 7=ZZ Par 8=ZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, IN, IN, IN, IN, IN, IN, IN, IN
! GCP Dimensional Parameters
! Diam Par 1 Par 2 Par 3 Par 4 Par 5 Par 6 Par 7
Par 8
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

260 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Piping Component Table for Empty Weight based on GCP


Data (P51,P52,P59)
This table enables you to define empty weights for components to which table name formats
P51, P52, and P59 apply.
The table name formats for this table are:
For TNF=P51 MC_GS_Term(G)_Sc/Th(G)_WC
For TNF=P52 MC_GS_Term(G)_Rat(G)_Sc/Th(G)_WC
For TNF=P59 Cmdty Code
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.

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 1 No_Outputs 1
Units= NPD_IN, LB
! GCP Weight
! Diam Empty
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
WWWWW ZZZZZZZ
END

Examples

Table_Data_Definition 'VAABAHCCAA'
! Description= CL150 gate valve raised face flanged ends weight
! Source= CRANE catalog for figure 47XU
! TNF=P59 By=GJH Ckd By=RJW Rev=0 Date=29-May-
1987
No_Inputs 1 No_Outputs 1
Units= NPD_IN, LB
! GCP Weight
! Diam Empty
2 46
2.5 70
3 76

Plant Design System (PDS) Reference Data Manager (PD_Data) 261


Table Formats and Naming Conventions

4 110
5 155
6 175
8 310
10 455
12 650
14 860
16 1120
18 1400
20 2125
24 3120
30 4250
END

Table_Data_Definition 'E90LR_39_300_S$STD_52'
! Description= 90 deg long radius elbow beveled ends
! Source= Taylor Forge Cat. 722
! TNF=P51 By=GJH Ckd By=JPF Rev=0 Date=24-Apr-
1986
No_Inputs 1 No_Outputs 1
Units= NPD_IN, LB
! GCP Weight
! Diam Empty
0.5 0.17
0.75 0.17
1 0.34
1.25 0.58
1.5 0.84
2 1.5
2.5 3
3 4.7
3.5 6.6
4 8.9
5 15
6 24
8 47
10 83
12 123
14 158
16 207
18 263
20 323
22 392
24 468
26 550
28 625
30 733
32 825
34 -
36 1061
38 -
40 -
42 1442

262 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

44 -
46 -
48 -
END

Piping Component Table For Empty Weight of Valves (P60A)


This table enables you to define empty weights of piping valves, weights and centers of gravity
of valve operators, model codes of valves operators and 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.
The table name format that applies to this table is:
For TNF=P60A Cmdty Code_WOPD_A

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW_WOPD_A'
! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=P60A By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
! SN=ZZZZZZ
No_Inputs 1 No_Outputs 8
Units= NPD_IN, LB, LB, IN, IN, IN, DEG, IN, IN
! GCP Weight Weight Oper Dimensional Parameters
! Diam Vlv Emp Oper Code Y1 Y2 Y3 Y4
Y5
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
WWWWW ZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ ZZZZZZZ
ZZZZZZZ
END

Plant Design System (PDS) Reference Data Manager (PD_Data) 263


Table Formats and Naming Conventions

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

Piping Component Table For Empty Weight of Valves,


Overflow Data (P60B)
This table enables you to define overflow parameters for
operators/actuators to which table name format P60A applies.
The table name format that applies to this table is:
For TNF=P60B Cmdty Code_WOPD_B

Neutral File Format

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

264 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

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

Piping Component Table for Empty Weight based on GCP


and RCP Data (P61,P62,P63,P64,P65)
This table enables you to define empty weights for components to which table name formats
P61, P62, P63, P64, and P65 apply:
The table name formats for this table are:
For TNF=P61 MC_GS_Term(G)_Rat(G)_Term(R)_Rat/Sc/Th(R)_WC
For TNF=P62 MC_GS_Term(G)_Rat(G)_Term(R)_Rat(R)_Sc/Th(R)_WC
For TNF=P63 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Sc/Th(R)_WC
For TNF=P64 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat(R)_WC
For TNF=P65 MC_GS_Term(G)_Sc/Th(G)_Term(R)_Rat/Sc/Th(R)_WC

Neutral File Format

Table_Data_Definition
'WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'

Plant Design System (PDS) Reference Data Manager (PD_Data) 265


Table Formats and Naming Conventions

! Description=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! Source=
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
! TNF=YYYY By=ZZZ Ckd By=ZZZ Rev=ZZ Date=ZZ-ZZZ-
ZZZZ
No_Inputs 2 No_Outputs 1
Units= NPD_IN, NPD_IN, LB
! Nom Diam Weight
! GCP RCP Empty
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
WWWWW WWWWW ZZZZZZZ
END

Example

Table_Data_Definition 'REDC_39_300_S$60_300_S$40_52'
! Description= Concentric reducer beveled ends weight.
! Source= TAYLOR FORGE Cat. 722, weights for schedule 60 fitting
! TNF=P63 By=GJH Ckd By=JPF Rev=0 Date=15-Aug-
1986
No_Inputs 2 No_Outputs 1
Units= NPD_IN, NPD_IN, LB
! Nom Diam Weight
! GCP RCP Empty
14 12 92
16 14 125
16 12 125
18 14 173
18 12 173
20 18 278
20 14 278
20 12 278
22 20 -
22 18 -
22 14 -
24 20 397
24 18 397
END

266 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Piping Component Tables for Specialty Components


Six dimension tables are used for each combination of piping specialty generic name (AABBCC
code) and piping specialty model code. The AABBCC code is defined in the PDS Sort Code
attribute of the Piping Specialty Specification Data of the Material Reference Database.
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:
EQBODY_SPECIFIC_<PSC>_<MC>_A, _B, _C - Specialty Body Data
EQOPER_SPECIFIC_<PSC>_<MC>_A, _B, _C - Specialty Operator/Actuator Data
Refer to Instrument Component Tables (on page 267) for more information on these tables.

Instrument Component Tables


Six dimension tables are used for each combination of instrument name (pds_sort_code) and
instrument model code. Multiple tables are required since tables with one input are limited to
nine outputs. The instrument pds_sort_code is defined in the Instrument Component
Specification Data of the Material Reference Database (Table 204 attribute 18). (For the
delivered examples, the pds_sort_code is the Instrument AABBCC code as defined in the PDS
Component Data Reference Guide.)
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.
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.
See Also
Instrument Body Data (see "Instrument Body (I80 and P80)" on page 267)
Instrument Operator/Actuator Data (see "Instrument Operator (I81 and P81)" on page 269)

Instrument Body (I80 and P80)


Three tables define the instrument body physical and geometric data for each combination of
instrument pds_sort_code and the model code in the Instrument Component Specification Data
of the Material Reference Database.
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).

Plant Design System (PDS) Reference Data Manager (PD_Data) 267


Table Formats and Naming Conventions

Inbody_Specific_PSC_MC_A

The input field is the physical_data_id for the instrument.


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.

268 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Inbody_Specific_PSC_MC_C

The output fields are the dimensional parameters P16 through P24, as prescribed in the PDS
Piping Component Data Reference Guide.

Instrument Operator (I81 and P81)


Three tables are required for the instrument operator/actuator geometric data for each
combination of instrument pds_sort_code and model code in the Instrument Component
Specification Data of the Material Reference Database.
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

Plant Design System (PDS) Reference Data Manager (PD_Data) 269


Table Formats and Naming Conventions

Specification Data of the Material Reference Database. The operator type is the number (such as
411) representing the operator and not the symbol name (such as OP_411).
The remaining output fields are dimensional parameters Y2 through Y8, as prescribed in the
PDS Piping Component Data Reference Guide. For some operators, the first three dimensional
parameters, Y2 through Y4, define the center of gravity for the operator in terms of offsets from
the instrument center.

Inoper_Specific_PSC_MC_B

The output fields are the dimensional parameters Y9 through Y17, as prescribed in the PDS
Piping Component Data Reference Guide.

Inoper_Specific_PSC_MC_C

The output fields are the dimensional parameters Y18 through Y24, as prescribed in the PDS
Piping Component Data Reference Guide.

270 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Formats and Naming Conventions

Plant Design System (PDS) Reference Data Manager (PD_Data) 271


SECTION 9

Material Description Data


The PDS 3D modules use the Material Description Library and the material data in the Material
Reference Database to provide material descriptions for commodity items and specialty items.
This data is accessed for:
Material Take-off (MTO) reporting from the Design Database.
Other miscellaneous reporting.
Interfaces to a material control system.
Stress analysis.
Isometric drawing extraction.
The alphanumeric commodity data is made up of four major parts:
Material Data in the Material Reference Database (on page 276) - These database tables
(211 and 212) contain commodity definitions which enable you to further classify the
commodity items defined in the Piping Job Specification. This database information tends
to be customer-specific.
Short Material Description Library (on page 277) - 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 (on page 283) - This library contains the long bill-of-
material descriptions for all piping commodity items. The long BOM description is only
used for requisitions.
Specialty Material Description Library (on page 286) - This library contains the bill-of-
material descriptions for engineered items, in-line instruments, and pipe supports.
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.
See Also
Material Description Library Manager (on page 287)

Plant Design System (PDS) Reference Data Manager (PD_Data) 273


Material Description Data

Commodity Code
The system uses the commodity code as an index to access the descriptions in the material
description libraries. You can use the commodity code defined in the Piping Commodity
Specification Data table (Table 202 attribute 18) or a user-defined commodity code defined in
the Size-Dependent Material Data table (Table 211 attribute 7).

The source of the commodity code and other processing options for reporting are defined for a
model with the Material Takeoff Options form of the Project Data Manager.
The commodity code represents that set of parameters that completely describe a commodity
item, exclusive of nominal piping diameter and thickness. The character length for the
commodity code is determined from the character length of the commodity code in the Size
Dependent Data table of the database, or from the character length of the commodity code in the
Piping Commodity Data table of the database, depending on which is being used to access the
material descriptions.
The delivered commodity codes use a 10 character code to fully identify the item. The first
letter of the commodity code identifies the basic type of component, such as a valve or flange.

274 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

The remaining characters provide a detailed description of the component. The first character
designations are:
B Flanged and Misc. Fittings Q Socket End Fittings
D Fire and Safety Components R Tubing Fittings
E Steam Specialties S Socketwelded Fittings
F Flanges T Threaded Fittings
G Flanged Specialties U Underground Fittings
H Strainers V Valves
M Misc. Wetted Components W Welded Fittings
N Misc. Non-Wetted Components X Gaskets
O Tubing and Hose Y Bolting
P Pipe

Examples

1 2 3 4 5 6 7 8 9 0
P A D A A B C A A E
P - Pipe
AD - Pipe, Plain Ends
AA - Seamless
BC - X-Strong (s-xs)
AAE - ASTM A106 Gr. B
V A A B A H C C A A
V - Valve
A - Gate Valve
A - CL150
B - Raised Face Flanged Ends
A - Carbon Steel
H - Trim 8
CC - Crane 47
AA - Blank
Refer to the PDS Piping Component Data Reference Guide for a complete listing of the
delivered commodity codes.
You can use the delivered commodity codes or create your own naming scheme. Regardless of
the scheme used, all the codes must be unique and there must be an exact match between the
commodity code specified for an item in the Material Reference Database and commodity codes
used to define the material descriptions in the Material Descriptions Library.

Plant Design System (PDS) Reference Data Manager (PD_Data) 275


Material Description Data

Tap Commodity Codes


The delivered tap codes use a 10 character code to full identify the tap's material description
addendum. The basic format of the tap commodity code is:
A BBB CCC DDD
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.)
CCC End preparation value as defined in code list set 330.
DDD user-defined value.

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

Tri-Clover Commodity Code Logic


The Tri-Clover commodity codes are based on Tri-Clover part numbers, but have been modified
so that they are less than 18 characters.

Example
Tri-Clover part number:
BS14AM-4"-316L-PL
BS14AM = Part Description
4" = Size
316L = Material Grade
PL = Surface Finish Description
Tri-Clover commodity code:
BS14AM316LPL
In the Tri-Clover commodity code, the dashes ("-") and size are removed so that the commodity
code is less than 18 characters. The commodity code description lists the full part number.

276 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

Material Data in the Material Reference Database


The Material Reference Database contains two database tables which contain Material Data.
Piping Commodity Size-Dependent Material Data (211)
The Size-Dependent Data table contains the data for a specific commodity item that is
dependent on the commodity code, nominal piping diameter, and schedule/thickness. It is
used for miscellaneous batch reporting, such as construction cost reports and requisition
orders, and interfaces to material control, stress analysis, and isometric drawing extraction.
Piping Commodity Implied Material Data (212)
The Implied Material Data table contains the implied material data for a specific commodity
item that is dependent on both the 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 (on page 29) for information on the structure of
these database tables. Also, refer to the description of the Piping Job Specification Manager (on
page 101) for information on loading material data into these database tables via neutral files.

Short Material Description Library


This library contains the short bill of materials description for all piping commodity items and
the description addenda for taps. The short BOM description is used for MTO reporting and for
reporting from the Piping Job Specification. This parameter is required during the creation of
the Piping Job Specification. Nominal piping diameter is not included in this description.
The short material descriptions are delivered in the files
\win32app\ingr\rdusrdb\us_shbom.l - object library
The short material descriptions can be up to 240 characters in length.

Neutral Files
You can use neutral files to insert data into the Short Material Description Library or replace
existing data. The neutral files for the delivered material descriptions are contained in the text
library. You can use the neutral files in the following files:
The Short Material Description Library is created from two neutral files. (These can be created
with a text editor such as Notepad.)
A neutral file containing the short material descriptions for commodity items. The neutral
file contains unique Commodity Codes followed by at least one space and a description
enclosed in single quotes. It also contains the chain wheel descriptions and implied material
descriptions associated with a commodity item.
The commodity code identifies the Piping Commodity Library code or customer's
commodity code. The character length for this code is determined from the character length
of the commodity code in the Size Dependent Data table of the database, or from the
character length of the commodity library code in the Piping Commodity Data table of the
database, depending on which is being used to access the material descriptions.

Plant Design System (PDS) Reference Data Manager (PD_Data) 277


Material Description Data

For chain wheels, the commodity code has the format CHAIN_xx, where xx represents the
chain wheel number (for example, CHAIN_12). The chain wheel number is defined in the
component and instrument analysis entities of the TDB.
A neutral file containing the material description addenda for taps. This file contains the tap
code and the text for the tap description. The tap code identifies the unique identification of
a tap.
The following conventions are used to identify different types of information in the material
descriptions:
^ All information to the left of the carat (^) is used in MTO reporting and isometric
extraction, but is excluded from Spec reporting.
|| Information appearing in |Pipes| indicates information for Spec descriptions only. This
information is excluded from the descriptions for MTO reporting and isometric
extraction.
[] Information appearing in [brackets] indicates a label type from the Label Description
Library. The system uses the label format to determine the information to be included in
the material description for MTO reporting and isometric extraction. The label
information is never used in Spec reporting.
The following label types are provided in the product delivery:

Label No Data in Label Source of Data


400 Comp cmdty code Component
401 Piping sch/thk 1 Pipe
402 Tag no Component
403 Component sch/thk 1 Component
406 Component sch/thk 1 b Component
407 Component sch/thk 2 Component
409 Component sch/thk 2 b Component
412 Component sch/thk 1 x 2 Component
414 Component sch/thk 1 x 2 Component
b
416 Component sch/thk 1 x 3 Component
417 Component sch/thk 1 x 3 Component
b
421 Bonnet length Component
422 Piping chain length Component
423 Reinforcing weld size Component
424 Instr chain length Component
425 RPAD width x thick Component

278 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

Label No Data in Label Source of Data


426 Comp NPD 1 Component
427 Monitor elev length Component
428 Hydrant cover Component
429 Blank/spacer thk Component

Data Retrieval
The system uses the commodity code to retrieve the short material descriptions from the
Material Description Library.
Commodity Material Descriptions
! DEFINE SHORT DESCRIPTIONS
! Date/Time: Thu Apr 23 14:16:58 1992
! Processed Library c:
ewpipe\refdata\us_shbom.l
!Cmdty Code
====================================Description========================
================
CHAIN_1003 'Chainwheel operator each with [422] of total chain
length for [426] NPD valve with commodity code [400]'
CHAIN_1005 'Chainwheel operator each with [422] of total chain
length for [426] NPD valve with commodity code [400]'
CHAIN_1251 'Chainwheel operator each with [424] of total chain
length for valve with tag no [402]'
DAABAXAABE 'Monitor, CL150 FFFE, ^station type, 4" CL150 in-let
by 2.5" NHT stainless steel outlet
w/stainless steel stem lock knobs with 0.75"
coupling in base, w/shapertip nozzle, Stang BB0309-21'
DAABAXAABF 'Monitor, CL150 FFFE, ^station type 4" CL150 in-let
by 2.5" NHT stainless steel
outlet w/stainless steel stem lock knobs with 0.75"
coupling in base, w/fog nozzle,
Stang BB0309-21'
DACBAXABBC 'Monitor, CL150 FFFE, ^elevated type, free standing,
4" CL150 in-let by 2.5" NHT
stainless steel outlet, [427], w/drain coupling,
w/shapertip nozzle and two reaction supports,
Stang BB2999-'
DACBAXABBD 'Monitor, CL300 FFFE, ^elevated type, supported, 6"
CL300 in-let by 2.5" NHT stainless
steel outlet, [427], w/drain coupling, w/shapertip
nozzle, Stang BB3561'
DBAAAXBAAB 'Fire hydrant, CL125 FFFE, ^5" size,
counterclockwise open, 4.5" steamer nozzle,
two 2.5" hose nozzles equipped w/caps and chains,
[428], American Darling B-50-B'
DCBGDXEADA 'Hose rack, 300#, FTE, ^w/valve, wall mount, rt hand
w/100 ft hose & fog nozzle Powhatan 30-333'
DDAXCJDAAA 'Spray sprinkler, MTE, filled cone w/rupture disc,
304, Grinnell, Mulsifyre Projector S-1'

Plant Design System (PDS) Reference Data Manager (PD_Data) 279


Material Description Data

FAAAAAWAAA 'Flange, CL150, FFFE/BE, ^ASTM-A105, ANSI-B16.5, WN,


[409]|bore to match|'
FAAAAAWWAA 'Flange, CL150, FFFE/BE, ^ASTM-A105, ANSI-B16.5, WN,
cement lined, [409]|bore to match|'
FAAABADIIA 'Flange, CL150, RFFE/BE, ^ASTM-A182-F304, ANSI-
B16.5, WN, S-80S bore'
FAAABADIIF 'Flange, CL150, RFFE/BE, ^ASTM-A182-F316, ANSI-
B16.5, WN, S-80S bore'
FAAABADNPF 'Flange, CL150, RFFE/BE, ^ASTM-B166-600, ANSI-B16.5,
WN, S-80S bore'
FAAABAOAAA 'Flange, CL150, RFFE/BE, ^ASTM-A105, ANSI-B16.5, WN,
S-160 bore'
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'

280 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

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'
FAADBAOABE 'Flange, CL600, RFFE/BE, ^ASME-SA105, ANSI-B16.5,
WN, S-160 bore'
FAADBAWAAA 'Flange, CL600, RFFE/BE, ^ASTM-A105, ANSI-B16.5, WN,
[409]|bore to match|'
FAADBAWABE 'Flange, CL600, RFFE/BE, ^ASME-SA105, ANSI-B16.5,
WN, [409]|bore to match|'
FAADBAWFFC 'Flange, CL600, RFFE/BE, ^ASTM-A182-F11, ANSI-B16.5,
WN, [409]|bore to match|'
FAADBAWFFH 'Flange, CL600, RFFE/BE, ^ASTM-A182-F5, ANSI-B16.5,
WN, [409]|bore to match|'

Plant Design System (PDS) Reference Data Manager (PD_Data) 281


Material Description Data

FAADBAWFFL 'Flange, CL600, RFFE/BE, ^ASTM-A182-F9, ANSI-B16.5,


WN, [409]|bore to match|'
FAADBAWIIA 'Flange, CL600, RFFE/BE, ^ASTM-A182-F304, ANSI-
B16.5, WN, [409]|bore to match|'

Tap Material Descriptions


! DEFINE SHORT DESCRIPTIONS
! Date/Time: Thu Apr 23 12:09:23 1992
! Processed Library c:
ewpipe\refdata\us_shbom.l
!Cmdty Code
====================================Description========================
========
E$12591XXX '0.125" diam hole'
E$25591XXX '0.25" diam hole'
E$37591XXX '0.375" diam hole'
E$50021018 '0.5" NPD, CL150 RFFE tap'
E$50021028 '0.5" NPD, CL300 RFFE tap'
E$50021036 '0.5" NPD, CL600 RFFE tap'
E$50401093 '0.5" NPD, Sch 80 SE tap'
E$50421064 '0.5" NPD, CL3000 SWE tap'
E$50421072 '0.5" NPD, CL6000 SWE tap'
E$50421076 '0.5" NPD, CL9000 SWE tap'
E$50441056 '0.5" NPD, CL2000 FTE tap'
E$50441064 '0.5" NPD, CL3000 FTE tap'
E$50441072 '0.5" NPD, CL6000 FTE tap'
E$50591XXX '0.5" diam hole'
E$75021018 '0.75" NPD, CL150 RFFE tap'
E$75021028 '0.75" NPD, CL300 RFFE tap'
E$75021036 '0.75" NPD, CL600 RFFE tap'
E$75401093 '0.75" NPD, Sch 80 SE tap'
E$75421064 '0.75" NPD, CL3000 SWE tap'
E$75421072 '0.75" NPD, CL6000 SWE tap'
E$75421076 '0.75" NPD, CL9000 SWE tap'
E$75441056 '0.75" NPD, CL2000 FTE tap'
E$75441064 '0.75" NPD, CL3000 FTE tap'
E$75441072 '0.75" NPD, CL6000 FTE tap'
E$75591XXX '0.75" diam hole'
E001021018 '1" NPD, CL150 RFFE tap'
E001021028 '1" NPD, CL300 RFFE tap'
E001021036 '1" NPD, CL600 RFFE tap'
E001401093 '1" NPD, Sch 80 SE tap'
E001421064 '1" NPD, CL3000 SWE tap'
E001421072 '1" NPD, CL6000 SWE tap'
E001421076 '1" NPD, CL9000 SWE tap'
E001441056 '1" NPD, CL2000 FTE tap'
E001441064 '1" NPD, CL3000 FTE tap'
E001441072 '1" NPD, CL6000 FTE tap'
E001591XXX '1" diam hole'
E002021018 '2" NPD, CL150 RFFE tap'
E002021028 '2" NPD, CL300 RFFE tap'
E002021036 '2" NPD, CL600 RFFE tap'
E002401093 '2" NPD, Sch 80 SE tap'

282 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

E002421064 '2" NPD, CL3000 SWE tap'


E002421072 '2" NPD, CL6000 SWE tap'
E002421076 '2" NPD, CL9000 SWE tap'
E002441056 '2" NPD, CL2000 FTE tap'
E002441064 '2" NPD, CL3000 FTE tap'
E002441072 '2" NPD, CL6000 FTE tap'
E002591XXX '2" diam hole'
E003021018 '3" NPD, CL150 RFFE tap'
E003021028 '3" NPD, CL300 RFFE tap'
E003021036 '3" NPD, CL600 RFFE tap'
E003401093 '3" NPD, Sch 80 SE tap'
E003421064 '3" NPD, CL3000 SWE tap'
E003441056 '3" NPD, CL2000 FTE tap'
E003441064 '3" NPD, CL3000 FTE tap'
E003441072 '3" NPD, CL6000 FTE tap'
E003591XXX '3" diam hole'
E004021018 '4" NPD, CL150 RFFE tap'
E004021028 '4" NPD, CL300 RFFE tap'
E004021036 '4" NPD, CL600 RFFE tap'
E004401093 '4" NPD, Sch 80 SE tap'
E004421064 '4" NPD, CL3000 SWE tap'
E004441056 '4" NPD, CL2000 FTE tap'
E004441064 '4" NPD, CL3000 FTE tap'
E004441072 '4" NPD, CL6000 FTE tap'
E004591XXX '4" diam hole'

Long Material Description Library


This library contains the long bill of materials description for all piping commodity items. The
long bill of materials description is only used for requisitions. It is usually a very long
description such as a paragraph. Nominal piping diameter is not included in the description.
This data is used strictly for MTO reporting and material control.
The long material descriptions are delivered in the file \win32app\ingr\rdusrdb\us_lgbom.l.
The long material descriptions can be up to 500 characters in length.

Neutral Files
The Long Material Description Library is created through a neutral file which contains the long
material descriptions for commodity items. The neutral file contains unique commodity codes
followed by at least one space and a description enclosed in single quotes.
You can use neutral files to insert data into the Long Material Description Library or replace
existing data.
The commodity code identifies the Piping Commodity Library code or customer's commodity
code. The character length for this code is determined from the character length of the
commodity code in the Size Dependent Data database table, or from the character length of the
commodity library code in the Piping Commodity Data table of the PJS database, depending on
which is being used to access the material descriptions.

Plant Design System (PDS) Reference Data Manager (PD_Data) 283


Material Description Data

The long description can be up to 500 characters. Because this description may include label
numbers which are translated to text strings, the reported (compiled) length of the description
can be up to 600 characters.
Prior to the 5.0 release, there was a restriction that no more than 255 characters could be
specified per line in the neutral file. This required that long descriptions be continued on
multiple lines. With the 5.0 release, a neutral file for long material descriptions may contain up
to 600 characters per line.

Data Retrieval
The system uses the Piping Commodity Library code or commodity code to access the text for
the long description in the Long Material Description Library.
Listing for Long Material Descriptions
! DEFINE LONG DESCRIPTIONS
! Date/Time: Fri Apr 24 10:48:13 1992
! Processed Library c:
ewpipe\refdata\us_lgbom.l
!Cmdty Code
====================================Description========================
================
DAABAXAABE 'Monitor, 750 GPM at 100 psig, CL150 flat face
flange end, station type, 4" CL150 in-let by 2.5" NHT stainless
steel outlet w/stainless steel stem lock knobs with
0.75" coupling in base, w/shapertip nozzle, Stang BB0309-21
or approved equal'
DAABAXAABF 'Monitor, 750 GPM at 100 psig, CL150 flat face
flange end, station type 4" CL150 in-let by 2.5" NHT stainless
steel outlet w/stainless steel stem lock knobs with
0.75" coupling in base, w/fog nozzle, Stang BB0309-21
or approved equal'
DACBAXABBC 'Monitor, 750 GPM at 100 psig, CL150 flat face
flange end, elevated type, free standing, 4" CL150 in-let by
2.5" NHT stainless steel outlet, w/drain coupling,
w/shapertip nozzle and two reaction supports,
Stang BB2999-[427] high or approved equal'
DACBAXABBD 'Monitor, 750 GPM at 100 psig, CL300 flat face
flange end, elevated type, supported, 6" CL300 in-let by 2.5"
NHT stainless steel outlet, w/drain coupling,
w/shapertip nozzle, Stang BB3561-[427] high or approved equal'
DBAAAXBAAB 'Fire hydrant, CL125 flat face flange end, 5" size,
regular rating, ductile iron barrel, bronze trim,
bituminous paint below grade, red epoxy paint above
grade, counterclockwise open, 4.5" steamer nozzle, two 2.5"
hose nozzles equipped w/caps and chains, [428],
American Darling B-50-B or approved equal'
DCBGDXEADA 'Hose rack w/bronze angle valve, 300#, female
threaded end, wall mount, right hand w/100 ft synthetic single
jacketed hose, rack nipple & fog nozzle, Powhatan
30-333 or approved equal'
DDAXCJDAAA 'Spray sprinkler, male threaded end, filled cone
w/rupture disc, .313" orifice, Type 304 stainless steel,

284 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

Grinnell Fire Protection, Mulsifyre Projector S-1


50-12 or approved equal'
FAAAAAWAAA 'Flange, weld neck, flat face flanged end, ANSI-
B16.5 CL150, ASTM-A105, [409]'
FAAAAAWWAA 'Flange, weld neck, flat face flanged end, ANSI-
B16.5 CL150, ASTM-A105, cement lined, [409]'
FAAABADIIA 'Flange, weld neck, raised face flanged end, ANSI-
B16.5 CL150, ASTM-A182 Gr.F304, Sch 80S bore'
FAAABADIIF 'Flange, weld neck, raised face flanged end, ANSI-
B16.5 CL150, ASTM-A182 Gr.F316, Sch 80S bore'
FAAABADNPF 'Flange, weld neck, raised face flanged end, ANSI-
B16.5 CL150, ASTM-B166 Gr.600 UNS N06600, hot finish, Sch 80S bore'
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'

Plant Design System (PDS) Reference Data Manager (PD_Data) 285


Material Description Data

Specialty Material Description Library


This Library contains the material descriptions for any engineered items or in-line instruments
which are reported by MTO or material control. These material descriptions are job-specific and
are accessed by the specialty item's tag number.
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.
Material descriptions for engineered items
(engineered item number = tag).
Material descriptions for instruments.
(instrument tag number = tag).
Material descriptions for pipe supports.
(commodity code = tag).
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.
The descriptions in Specialty Material Description Library tend to be customer-specific. The
following is a listing of sample neutral files for the specialty data.
! DEFINE SPECIALTY DESCRIPTIONS
! Date/Time: Thu Apr 30 09:02:24 1992
! Processed Library c:
ewpipe\refdata\us_spbom.l
!Cmdty Code
====================================Description========================
======
38-VI-9 'RELIEF CONTROL VALVE.'
INSTR 'Instrument'
PSPECIALTY 'Piping specialty component'
PSUPPORT '[970]'
! DEFINE SPECIALTY DESCRIPTIONS
! Date/Time: Thu Apr 30 09:02:39 1992
! Processed Library c:
ewpipe\refdata\us_spbom.l
!Cmdty Code
====================================Description========================
======
SPECIAL_ENGR 'SPECIAL ANGLE OUTLET.'
SPECIAL_ENGR 8 'SPECIAL ANGLE OUTLET.'
SPECIAL_ENGR @fffffe"ffff98O 'SPECIAL ANGLE OUTLET.'
! DEFINE SPECIALTY DESCRIPTIONS
! Date/Time: Thu Apr 30 09:02:56 1992
! Processed Library c:
ewpipe\refdata\us_spbom.l

286 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

!Cmdty Code
====================================Description========================
======
SUPP1 'PIPE SUPPORT NUMBER 1.'
SUPP1 8 'PIPE SUPPORT NUMBER 1.'
SUPP1 @fffffe"ffff98O 'PIPE SUPPORT NUMBER 1.'
SUPP2 'PIPE SUPPORT NUMBER 2.'
SUPP2 8 'PIPE SUPPORT NUMBER 2.'
SUPP2 @fffffe"ffff98O 'PIPE SUPPORT NUMBER 2.'
SUPP3 'PIPE SUPPORT NUMBER 3.'
SUPP3 8 'PIPE SUPPORT NUMBER 3.'
SUPP3 @fffffe"ffff98O 'PIPE SUPPORT NUMBER 3.'

Data Retrieval
The system uses the specialty tag number and specialty type to access the text for the material
descriptions in the Specialty Material Description Library.

Material Description Library Manager


The Material Description Library Manager enables you to create and modify alphanumeric
commodity data. You can initialize libraries, create material description data, append new data
to existing material description data, revise (delete and replace) existing data, and delete existing
data.
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.
The system displays the Material Description Library Manager form.

Plant Design System (PDS) Reference Data Manager (PD_Data) 287


Material Description Data

2. Select the option for the library to be modified.


Short Material Description Library
Long Material Description Library
Specialty Material Description Library
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 (on page 289) Creates a new (empty) Short Material Description Library,
Long Material Description Library, or Specialty Material Description Library.
Unapprove ==> Approve (see "Unapproved ==> Approved" on page 289) Copies data
from the unapproved library to the approved library.
Load/Revise Interactive (on page 289) Adds the contents of the neutral files to the
information currently in an existing Material Description Library or revises an existing table
in the library.
Load/Revise Batch (on page 290) Adds the contents of the neutral files to the information
currently in an existing Material Description Library or revises an existing table in the
library.
Replace Interactive (on page 291) Deletes all entries in the respective Material
Description Library file and then loads new entries from a neutral file.
Replace Batch (on page 291) Deletes all entries in the respective Material Description
Library file and then loads new entries from a neutral file.
Report (see "Report Option" on page 292) Used to create a report file or a neutral file of
the contents of the material description library.

288 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

Create Library
This option is used to create a new Material Description Library. This option is disabled if the
library already exists.
1. Select Create Library from the Material Description Library Manager form.
The system displays the approved and unapproved Library names as defined in the RDB
Management Data.

2. The system prompts Accept to Create or Exit to Avoid Creating New Library
Select Accept to create the specified library files.

Unapproved ==> Approved


This option is used to copy the data in the unapproved material description library to the
approved library.

Accept to Copy or Exit to Avoid Copying


Select Accept to copy the library file to the approved library.
If the approved and unapproved library names are the same, the system displays an error
message.

Load/Revise Interactive
This option enables you to load entries from a neutral ASCII file into the Material Description
Library. Refer to the library descriptions earlier in this section for a listing of the neutral file
formats used in defining the delivered material data.
This option adds the contents of the neutral files to the information currently in the library or
revises an existing table in the library.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.

Operating Sequence
1. Select the Load/Revise option.

Plant Design System (PDS) Reference Data Manager (PD_Data) 289


Material Description Data

2. Select File Type


Select the type of material data to be loaded into the specified library from the display list
and select Accept.

3. Specify Neutral File Name


Key in the file specification for the neutral file that contains the data to be processed.
4. Accept to Create New Records or Exit
Select Accept to begin processing the neutral file.
The system begins processing the load/revise request.

Load/Revise Batch
This option enables you to load entries from a neutral ASCII file into the Material Description
Library via batch processing. Refer to the library descriptions earlier in this section for a listing
of the neutral file formats used in defining the delivered material data.
This option adds the contents of the neutral files to the information currently in the library or
revises an existing table in the library.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.

Operating Sequence
1. Select the Load/Revise option.
2. Select File Type
Select the type of material data to be loaded into the specified library from the display list
and select Accept.

3.

290 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

4. Specify Neutral File Name


Key in the file specification for the neutral file that contains the data to be processed and
select Accept.
5. Accept to Submit or Specify Submit Time
Set the toggle to Submit Batch Immediately or Delayed Batch Submit Time.
For delayed submission, set the time to process the neutral file.
6. Select Accept to begin processing.
The system submits the request to the batch queue PDreference.

Replace Interactive
This option enables you to load entries from a neutral ASCII file into the Material Description
Library. Refer to the library descriptions earlier in this section for a listing of the neutral file
formats used in defining the delivered material data.
This option deletes all entries in the respective library file and then loads new entries from the
neutral file.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.

Operating Sequence
1. Select the Replace Interactive option from the Material Description Library form.
2. Select File Type
Select the type of material data to be loaded into the specified library from the display list
and select Accept.

3. Specify Neutral File Name


Key in the file specification for the neutral file that contains the data to be processed.
4. Accept to Create New Records or Exit
Select Accept to begin processing the neutral file.

Replace Batch
This option enables you to load entries from a neutral file into the Material Description Library
via batch processing. Refer to the library descriptions earlier in this section for a listing of the
neutral file formats used in defining the delivered material data.

Plant Design System (PDS) Reference Data Manager (PD_Data) 291


Material Description Data

This option deletes all entries in the respective library file and then loads new entries from the
neutral file.
The neutral files for the delivered RDB data are contained in the delivered material description
libraries. Refer to the Report option for information on extracting the neutral files.

Operating Sequence
1. Select the Replace Batch option from the Material Description Library form.
2. Select File Type
Select the type of material data to be loaded into the specified library from the display list
and select Accept.

3. Specify Neutral File Name


Key in the file specification for the neutral file that contains the data to be processed and
select Accept.
4. Accept to Submit or Specify Submit Time
Set the toggle to Submit Batch Immediately or Delayed Batch Submit Time.
For delayed submission, set the time to process the neutral file.
5. Select Accept to begin processing.
The system submits the request to the batch queue PDreference.

Report Option
The Report option enables you to create neutral files or report files using the information in the
Material Description Library. Refer to the description of the Short Material Description Library
(on page 277), Long Material Description Library (on page 283), and Specialty Material
Description Library (on page 286) for more information on the types of neutral files.

Operating Sequence
1. Select the Report option from one of the library forms.

292 Plant Design System (PDS) Reference Data Manager (PD_Data)


Material Description Data

2. Select File Type


Select the type of material data to be extracted from the specified library from the display list
and select Accept.

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.
4. Accept or Toggle to Create Report
Select Accept to create the specified neutral file.
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.
For the report selection, the system displays the following options.

Plant Design System (PDS) Reference Data Manager (PD_Data) 293


Material Description Data

7. Select the reporting option.


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.
Save save the output file and suppress printing.
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.
Select the queue for the required output device.
8. Select Accept to begin processing the request.

294 Plant Design System (PDS) Reference Data Manager (PD_Data)


SECTION 10

Table Checker
The Table Checker enables you to verify that all the commodity spec tables, entries, and Eden
modules for a piping materials class exist in the graphic data libraries for the project.
This process accesses the Eden code for each commodity item in the piping material class and
checks that the table names created in the physical dimension modules exist in the project
Physical Data Library. This routine checks for the existence of the tables and checks the contents
of the tables.

For Table Checker to function, there MUST be at least one piping model file created in the
project, and it must have a piping materials class (spec) defined in the Active Segment
Parameters.
The Type 63 settings of the model with the highest alphanumeric name are used as defaults
for the Table Checker reports. If weight tables are set to 'yes' for this model, then Table
Checker will search for and report on found and missing weight tables. If MTO Bolt
Calculation is set to 'almost precise,' Table Checker will search for the 'almost precise' tables
(table naming format = G12). If set to 'precise,' Table Checker will search for 'precise' tables
(table naming format = G12T).
When the spec contains PIPING/TUBE and PIPE/TUBING, Table Checker will report as per
Type 63 data settings.
If Component Placement is set to PIPING for Pipe Commodity Name and TUBE for Tube
Commodity Name, Table Checker uses these commodity names and searches for PDPIPING
and PDTUBE in the Graphic Commodity Library. If there are any other PIPE and TUBING
values found in the spec that do not match with Type 63, Table Checker assumes that this is a
regular commodity item. It uses the model_code and searches for SPmodel_Code in the
Graphic Commodity Library.
If Component Placement is set to PIPE for Pipe Commodity Name and TUBING for Tube
Commodity Name, Table Checker uses these commodity names and searches for PDPIPE and
PDTUBING in the Graphic Commodity Library. If there are any other PIPING and TUBE values
found in the spec that do not match with Type 63, Table Checker assumes that this is a regular
commodity item. It uses the model_code and searches for SPmodel_code in the Graphic
Commodity Library.
In such cases, if the model_code of the item is the same as the commodity_name that matches
with Type 63 data, the Table Checker may report the same value under both Eden Found and
Eden Not Found. In other words, Table Checker reports the commodity_name under Eden
Found and the model_code under Eden Not Found.

Plant Design System (PDS) Reference Data Manager (PD_Data) 295


Table Checker

Features
The Table Checker provides the following features.
Reports on one piping material class selected from the available entries in the
Specification/Material Database.
Reports on all valid sizes in the size range for each piping commodity using the Nominal
Piping Diameter table for that piping materials class.
Reports dimensional tables used during the placement of each piping commodity in the
piping materials class. This includes the table names, the types of tables, the existence of
those tables (found or not found), and the output values from those tables.
Reports Piping Eden modules used during the placement of each piping commodity in the
piping materials class. This includes the Piping Eden module names and the existence of
those modules (found or not found).
Reports dimensional tables used for all piping commodities in the entire report (the piping
materials class). This includes the table names, the revision dates for those tables, and the
source Dimension Table Library.
Reports bolt tables for each piping commodity with bolted ends.
Reports Piping Eden modules used for all piping commodities in the entire report (the piping
materials class). This includes the Piping Eden module names and the existence of those
modules (found or not found).
Verifies that a material description exists in the Material Description Library for any piping
commodities defined in the Material Reference Database. The commodity code as defined
in the Piping Commodity Specification Data Table (PDtable_202) or the Piping Commodity
Size-Dependent Material Data Table (PDtable_211) is used to verify the material
description.
Verifies that a material description exists in the Material Description Library for any implied
component defined in the Piping Commodity Implied Material Data Table (PDtable_212) of
the Material Reference Database.
Verifies that a material description exists in the Specialty Material Description Library for
any piping specialty or instrument defined in the Material Reference Database.
Provides a detailed error report of any tables or table entries that were found missing during
the processing of the piping materials class.
For tables containing schedule thickness calculations as part of the name, the
calculations are replaced with preferred thickness unless no preferred thickness is found for
that size or PMC thickness table.
If any errors are encountered during execution, the system appends the errors to the end of the
report output. In the case of severe errors, it creates a file named RPT_ERR.LOG.
Commodity items with option codes greater than 5000 (spec implied components) are not
checked.

Format Files
The Table Checker uses report format files to define the report output. It uses the same reporting
indices as any other report from the Piping Job Specification data (the C indices). Refer to
Format Files in the Report Manager Reference Guide for more information on these indices.

296 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

The following example report formats for the Table Checker are included in the PD_DATA
sample directory (\win32app\ingr\pddata\sample\format/). Refer to the Report Manager
Reference Guide for more information on report type.
tbl_chk_1.fmt
This report format reports on virtually all data generated by the Table Checker. It is a
combination of the following sample report formats: tbl_chk_2.fmt, tbl_chk_3.fmt, and
tbl_chk_4.fmt.
It reports the piping commodities in the selected piping materials class with the dimension
tables and Piping Eden modules used, including a list of all entries read in the dimension
tables. It also lists all dimension tables and Piping Eden modules required for those piping
commodities, but not available in the Reference Database.
tbl_chk_2.fmt
This report format reports the dimension tables and Piping Eden modules used by each
piping commodity in the applicable piping materials class.
tbl_chk_3.fmt
This report lists all entries read in dimension tables for the applicable piping materials class.
tbl_chk_4.fmt
This report format reports a total list of dimension tables and Piping Eden modules used for
the applicable piping materials class. It also lists all dimension tables and Piping Eden
modules required for those piping commodities, but not available in the Reference Database.
tbl_chk_5.fmt
This report verifies the reference data for any piping specialties defined in the Reference
Database (pdtable_203).
tbl_chk_6.fmt
This report verifies the reference data for any instruments defined in the Reference Database
(pdtable_204).
Table format 5 or 6 must be used when the discrimination file is created with the No
Piping Material Class button selected.

Plant Design System (PDS) Reference Data Manager (PD_Data) 297


Table Checker

Table Checker Form


The Report Manager form enables you to generate reports from the project, design, and
reference database files with the report definition data. The report record and the location
records for each discrimination data file and format file are stored in the project control database.
These numbered records are used to locate ASCII files on their specified nodes.

Report Format Displays the Report Format form, which you can use to create, revise,
copy, or delete the record of a format file (not the format file). For more information, see
Report Format Form (on page 300).
Report Discrimination Data Displays the Discrimination Data form, which you can
use to create, revise, copy, or delete the record of a discrimination data file as well as the file
itself. For more information, see Discrimination Data Form (on page 303).
Report Displays the Report form, which you can use to create, revise, delete, and
approve report records and report files. For more information, see Report Form (on page
308).
Report Management Data Displays the Report Management Defaults form, which
you can use to create a record in the project control database of the default nodename and
path for the report definition files. This option is primarily used for setup. For more
information, see Report Management Defaults Form (on page 316).

298 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Using the Report Commands


Understanding Report Files and Records
The Table Checker uses the discrimination data files, format files, and database records that
represent these files to generate reports. The following definitions explain all of the files and
records in the reporting process.

Format File and Record


The format file is a user-defined, ASCII file which must be created with a text editor outside of
the Table Checker. It contains special indices identifying what data appears in the report and
how the data is sorted. It also defines how the data is formatted in the report. Without the
format file(s), Table Checker reports cannot be processed. A set of basic format files is
delivered for each type of reporting.
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.

Discrimination Data File and Record


The discrimination data file limits the report to only the specified database occurrences. It is an
ASCII file that is created interactively using the Table Checker.
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.

Report Output and Record


The Table Checker creates a report using the specified format, discrimination, and search criteria
data files, and places it in the specified directory on the specified node.
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.)

Group Workflow
There is a definite workflow for at least the first time you create a report. First, use the Report
Management Data option to specify defaults for the nodename and path of the report definition
files. By defining the defaults first, you can prevent keying in a nodename and path on each
form. If you want to use a different nodename or path than the defined default, simply place a
data point in that field and key in the modification.
The following steps can be done in any order: create your format record, discrimination data
record, and discrimination data file using the Report Format and Report Discrimination Data
options. Reports cannot be generated until the format file, the discrimination data file, and their
corresponding records have been established.
Finally, use the Report option to create the actual report.

Plant Design System (PDS) Reference Data Manager (PD_Data) 299


Table Checker

Report Format Form


When you choose the Report Format option from the Report Manager form, the Report
Format form is displayed.

This form enables you to create, copy, revise, or delete a record of the location of the format file
in the project control database. An option is also provided that enables you to copy a record and
its corresponding ASCII format files.
The format file defines the data that will be reported and the way in which that data will be
displayed. Reports cannot be generated unless a format file exists and a record of the file's
location has been entered into the project control database.
Create Displays the Format Creation/Revision form, which enables you to add a new
record of a format file in the project control database. For more information, see Format
Creation/Revision Form (on page 301).
Copy Displays the Format Creation/Revision form, which copies the record of an
existing format file from the project control database along with the corresponding ASCII
format file. For more information, see Format Creation/Revision Form (on page 301).
Revise Displays the Format Creation/Revision form, which modifies a record of an
existing format file in the project control database. For more information, see Format
Creation/Revision Form (on page 301).
Delete Displays the Deletion form, which deletes an existing record of a format file from
the project control database. If the record of the format file is deleted, reporting cannot be
performed. For more information, see Format Deletion Form (on page 302).

300 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Format Creation/Revision Form


When you choose Create, Copy, or Revise from the Report Format form, the Format
Creation/Revision form is displayed.

This form creates or revises a record in the project control database; this record defines the
location of a format file. The format file itself defines the contents and format of the report.
Both the location specification and the format file must exist to report on PDS data.
Number A unique number of up to 24 characters. Specifies the short name in the project
control database used to identify the record of the format file.
Description A description of up to 40 characters for the format file.
File Specification The file name of the format file to reference.
Path The disk location of the format file. This field retains the active setting.
Node The nodename of the system on which the format file is located. This field retains
the active setting.

Before Using this Form


You must have created an ASCII format file. A set of basic format files is delivered with the
PD_Data product in the ~\pddata\sample\format directory. The file for MTO reporting is named
piping_#.fmt.

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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 301


Table Checker

2. Select Report Format


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.
3. Specify Report Format Data
Type information in each of the displayed fields, taking care to press Enter in each field.
Then click Accept.
The project control database is updated.

Format Deletion Form


When you choose Delete, the Deletion form is displayed.

This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.

Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.

302 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Discrimination Data Form


When you select Report Discrimination Data from the Report Manager form, the
Discrimination Data form is displayed.

This form creates, copies, revises, and deletes a discrimination data file from the specified
directory. The associated record in the project control database is also copied, revised, or
deleted as needed.
A discrimination data file is an ASCII file that designates which models will be included in a
report. That is, discrimination data specifies the scope of the report. The project control
database record specifies the name and location of the discrimination data file that is to be
associated with a specific report.
Create Displays the Discrimination Data Creation form, which creates a new
discrimination data file. The associated project control database record is also created. For
more information, see Discrimination Data Creation Form (on page 304).
Copy Displays the Discrimination Data Revision form, which copies an existing data
file. The associated project control database record is also copied. For more information,
see Discrimination Data Revision Form (on page 305).
Revise Displays the Discrimination Data Revision form, which modifies discrimination
data. You can use this option to revise the contents of the discrimination data file, the
location of the discrimination file, and the associated record in the project control database.
For more information, see Discrimination Data Revision Form (on page 305).
Delete Displays the Deletion form, which deletes a discrimination data file as well as its
associated record in the project control database. For more information, see Discrimination
Data Deletion Form (on page 306).

Plant Design System (PDS) Reference Data Manager (PD_Data) 303


Table Checker

Discrimination Data Creation Form


When you select Create from the Discrimination Data form, the Discrimination Data
Creation form is displayed.

This form creates a discrimination data file in a specified directory. It also creates a
corresponding record in the project control database. In addition, you can use this form to
specify segment and component search criteria.
If you use this form to specify search criteria data and you specify search criteria data
using the Report Search Criteria option, the data specified using the Report Search Criteria
option takes precedence.
Number The unique number, up to 24 characters, that is the short name of the
discrimination data record in the project control database.
Description The description, up to 40 characters, of the discrimination data record in the
project control database.
File Specification The file name of the discrimination data record to be created.
File Path The disk location of the discrimination data file. This field retains the active
settings.
File Node The nodename of the system on which the discrimination data file is located.
This field retains the active settings.
Piping Materials Class Key in up to 16 alphanumeric characters for the piping materials
class.
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Select Piping Materials Class Sets the piping materials class(es) in the
Specification/Material Reference Database which defines the tables to be checked.

304 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

No Piping Materials Class When selected, indicates to the system that either the piping
specialties or instruments will be verified by Table Checker.
Either format 5 or 6 must be used when the discrimination data is created with the No
Piping Materials Class button selected.

Operating Sequence
1. From the Report Discrimination Data form, select Create.
The Discrimination Data Creation form displays.
2. Specify Discrimination Data
In the fields provided, key in the number, description, file specification, path, and node.
3. Select additional options as needed to define the report discrimination data. Then select
Accept.
After including any models or search criteria for the discrimination data file, be
sure to select the final Accept. Because you must accept many forms while specifying the
discrimination data, it is easy to forget this step. Even though you may have accepted many
of the specifications, the discrimination data file is not actually created until you select
Accept on the Report Discrimination Data form.

Discrimination Data Revision Form


When you select Copy or Revise from the Discrimination Data form, the Discrimination Data
Revision form is displayed.

This form revises an existing discrimination data file. It also copies an existing discrimination
data file; you can then use the revision options to modify the copy as needed. The corresponding
records in the project control database are copied and/or modified as needed. In addition,
options are provided for you to modify segment and component search criteria data.
If you use this form to specify search criteria data and you specify search criteria data
using the Report Search Criteria option, the data specified using the Report Search Criteria
option takes precedence.
Number The unique number, up to 24 characters, that is the short name of the
discrimination data record in the project control database.
Description The description, up to 40 characters, of the discrimination data record in the
project control database.

Plant Design System (PDS) Reference Data Manager (PD_Data) 305


Table Checker

File Specification The file name of the discrimination data record to be created.
File Path The disk location of the discrimination data file. This field retains the active
settings.
File Node The nodename of the system on which the discrimination data file is located.
This field retains the active settings.
Piping Materials Class Select one or more piping materials classes from this list of
loaded classes.
Approved Piping Job Spec Defines the database to be reported: approved or
unapproved.
Select Piping Materials Class Sets the piping materials class(es) in the
Specification/Material Reference Database which defines the tables to be checked.
No Piping Materials Class When selected, indicates to the system that either the piping
specialties or instruments will be verified by Table Checker.
Either format 5 or 6 must be used when the discrimination data is created with the No
Piping Materials Class button selected.

Operating Sequence
1. From the Report Discrimination Data form, select Copy or Revise.
The Discrimination Data Revision form is displayed.
2. Specify Discrimination Data
In the fields provided, key in the number, description, file specification, path, and node.
3. Select additional options as needed to define the report discrimination data. Then select
Accept.
After updating any models or search criteria for the discrimination data file, be
sure to select the final Accept. Because you must accept many forms while specifying the
discrimination data, it is easy to forget this step. Even though you may have accepted many
of the specifications, the discrimination data file is not actually updated until you select
Accept on the Report Discrimination Data form.

Discrimination Data Deletion Form


When you choose Delete, the Deletion form is displayed.

306 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.

Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.

Plant Design System (PDS) Reference Data Manager (PD_Data) 307


Table Checker

Report Form
When you select Report from the Report Manager form, the Report form is displayed.

This form creates, revises, and deletes report records and report files. A report record holds
specifications for a report; these specifications include the report name, the report description,
and which format file, discrimination data file, and search criteria data file to use to generate a
report.
The report name is not the title that is printed on the report; the title is included in the
format file.
At the end of each report, a parameters page is included that contains the following information:
Report Output The report number, report title, report creation/revision date, and report
node, path, and file name.
Format The report format number, description, and node, path, and file name.
Discrimination Data The report discrimination data number, description, and file
location (network address, path, and file name). The following discrimination data is also
included: list of model numbers (with discipline), volume (if applicable), search criteria (if
applicable), and sorting sequence.
Search Criteria The report search criteria number, description, and file location (node,
path, and file name. The following search criteria data is also included: list of model
numbers (with discipline), volume (if applicable), search criteria (if applicable), and sorting
sequence.

308 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Options
Create Displays the Report Creation form, which creates a report record and generates
a report. For more information, see Report Creation Form (on page 309).
Revise Displays the Revise Report form, which regenerates a report from an existing or
revised report record. For more information, see Revise Report Form (on page 311).
Delete Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form (on page 313).
Approve Displays the Report Approval form, which approves an existing report. For
more information, see Report Approval Form (on page 314).
Multi-Create Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form (on page
315).

Report Creation Form


When you select Create from the Report form, the Report Creation form is displayed.

Use this form to create a report record and to generate a report. Because report records are
stored in the project control database, you can use them over and over again as needed.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.
The Table Checker Report Number must not contain spaces. If there are spaces in the
number, the report will not be submitted to the batch queue.

Plant Design System (PDS) Reference Data Manager (PD_Data) 309


Table Checker

Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings, and it is automatically populated if you have specified this data on the Report
Management Data form. For more information, see Report Management Defaults Form
(on page 316).
Report Node The name of the system on which the report output file will be located.
This field retains the active settings, and it is automatically populated if you have specified
this data on the Report Management Data form. For more information, see Report
Management Defaults Form (on page 316).
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit Immediately/Submission is Delayed Specifies when the report will be
processed. When this toggle is set to Submission is Delayed, additional fields display for
you to specify the date and time that the report is to be generated.

310 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Operating Sequence
1. From the Report form, select Create.
The Report Creation form is displayed.
2. Specify Report Data
Key in the report record information. Then select the appropriate report format file,
discrimination data file, and search criteria data file.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
4. Specify whether the report is to be generated now (Submit Immediately) or later
(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.
5. Click Accept to save the report file.

Revise Report Form


When you select Revise from the Report form, the Revise Report form is displayed.

This form revises an existing report record and generates a report from the project control
database. An option is also provided to update (in some cases) the report record without
generating a report output file. Similarly, you can choose to generate an updated report output
file without updating the report record.
Report Number The 24-character number that uniquely identifies the record of the
report file in the project control database. This is sometimes referred to as the report file
short name.

Plant Design System (PDS) Reference Data Manager (PD_Data) 311


Table Checker

Report Title The 40-character descriptive name of the report file. This is not the title in
the actual report, but is rather the title of the report record. The title of the report is
contained in the format file.
Report File Spec The name of the report output file (up to 14 characters).
Report File Path The disk location for the report output file. This field retains the active
settings.
Report Node The name of the system on which the report output file will be located.
This field retains the active settings.
Report Format File The name of the format file to be used to generate the active report.
When you select this field, a list of available format files is displayed. Select the appropriate
format file, and click Accept.
Report Discrimination File The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination data
files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria The name of the search criteria data file to be used to generate
the active report. When you select this field, a list of available search criteria files is
displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search criteria data
defined within it, and you specify a search criteria in this field, the search criteria specified
in the Report Search Criteria field takes precedence over the search criteria contained in
the discrimination data.
Revision Number The revision number (up to three characters) for the report.
Last Revision Number The revision number of the last report generated. This is a read-
only field; you cannot edit it.
Revised By The user (up to five characters) who checked the report. This field is
optional.
Revision Description The description (up to 40 characters) of the report revision. This
field is optional.
Print/Delete Submits the report output file to the specified print queue and then deletes
the report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Print/Save Submits the report output file to the specified print queue and saves the report
output file. When you select this option, a list of available print queues is displayed. Click
on a queue to select it.
Save Saves the report output file without printing the report.
Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.
Revise Data Only/Revise Report and Data Specifies revision of the report data only
(Revise Data Only) or revision of the report data and the report output file (Revise Report
and Data). To revise the report specification without updating the report output file, make
the necessary changes, set this toggle to Revise Data Only, and click Accept. To revise the
report output file only, set this toggle to Revise Report and Data without modifying any of

312 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

the fields, and click Accept. To modify both the report file and the report output file, make
the necessary changes, set this toggle to Revise Report and Data, and click Accept.
If you update any field other than Report Number and Report Title, this toggle is
automatically set to Revise Report and Data, and the report output file is generated.

Operating Sequence
1. From the Report form, select Revise.
The Report Creation form is displayed with a list of available report files.
2. Select Report
From the displayed list, select the report to be revised. Then click Accept.
The fields update to display the selected report file specifications.
3. Revise Report Information
Update the report record information as needed.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
5. Specify whether the report is to be generated now (Submit Immediately) or later
(Submission is Delayed). If you choose delayed submission, specify the date and time that
the report is to be submitted.
6. Click Accept to save the report file.

Report Deletion Form


When you choose Delete, the Deletion form is displayed.

Plant Design System (PDS) Reference Data Manager (PD_Data) 313


Table Checker

This form deletes a report record from the project control database and can optionally delete the
associated file. This form is used with format files and their database records, discrimination
data files and their database records, and search criteria files and their database records.
Number/Description Displays the 24-character short name and the 40-character
description of a report record in the project control database.
Delete File/Do Not Delete File Determines whether the associated file is deleted. When
set to Delete File, the database record is deleted along with the associated file. When set to
Do Not Delete File, only the database record is deleted.

Operating Sequence
1. Select Report Format
From the displayed list, select the database record to be deleted.
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.

Report Approval Form


When you select Approve from the Report form, the Report Approval form is displayed.

Use this form to select a report to approve. Approving a report means that a database attribute is
set from not approved (the default) to approved. This approval status provides a way for you to
flag reports that you have run and verified that the output data is valid. When a report is revised,
the approval status is automatically reset to not approved.
Number The 24-character unique name (as called short name) of the report record.
Description The 40-character description of the report record.

314 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Operating Sequence
1. From the Report form, select Approve.
The Report Approval form is displayed.
2. From the displayed list, select a report to approve. Then click Accept.
The Approval form is displayed.
For more information, see Approval/Revision Interface Form in the PD_Report User's
Guide.

Report Multiple Submit Form


When you select Multi-Create from the Report form, the Report Multiple Submit form is
displayed.

Use this form to submit multiple reports at the same time.


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.
Description The 40-character descriptive name of the report file.
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.

Plant Design System (PDS) Reference Data Manager (PD_Data) 315


Table Checker

Submit to Batch Immediately/Delayed Submit to Batch Specifies when the report will
be processed. When this toggle is set to Delayed Submit to Batch, additional fields display
for you to specify the date and time that the report is to be generated.

Operating Sequence
1. From the Report form, select Multi-Create.
The Report Multiple Submit form is displayed.
2. Select Reports for Submission
From the displayed list, select the reports to submit. Highlighted reports are selected; select a
highlighted report to remove the highlight and to not submit the report.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
4. Specify whether the report is to be generated now (Submit to Batch Immediately) or later
(Delayed Submit to Batch). If you choose delayed submission, specify the date and time
that the report is to be submitted.
5. Click Accept to submit the reports.

Report Management Defaults Form


When you select Report Management Data from the Report Manager form, the Report
Management Defaults form is displayed.

This form creates a record in the project control database of the node name and path of the report
definition files. This option is used primarily for setup.
Report Path Specifies the default path of the report output files.

316 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

It is recommended that you not send output reports to your system's temporary (that
is, tmp or temp) directory.
Report Node Specifies the default node name of the system on which report output files
are located.
Report Format Path Specifies the default path of the format files.
Report Format Node Specifies the default node name of the system on which format
files are located.
Report Discrimination Data Path Specifies the default path of the discrimination data
files.
Report Discrimination Data Node Specifies the default node name of the system on
which discrimination data files are located.
Report Search Criteria Data Path Specifies the default path of the report search criteria
data files.
Report Search Criteria Data Node Specifies the default node name of the system on
which report search criteria data files are located.

Operating Sequence
1. From the Report Manager form, select Report Management Data.
The Report Management Defaults form is displayed.
2. Accept or Exit
In the fields provided, key in the default paths and node names for the report output files,
format files, discrimination data files, and search criteria data files. Then click Accept.

Sample Table Checker Output


The following is a listing of selected pages from the table checker output for Piping Materials
Class 1C0031.
21-Apr-92 Page:
1
SIZE-INDEPENDENT SPEC DATA
__________________________
Description: Gate valve, CL800, SWE, BB, OS&Y,
ASTM-A105, trim 8, Smith 800

Piping Class: 1C0031

Size Range: 1st 3/4IN 1-1/2IN


2nd - -

Option:

End Preparation(s): SWE (421)

Rating(s): CL800

End geometry standard(s): Default (5)

Body geometry standard: Smith 1 (4625)

Plant Design System (PDS) Reference Data Manager (PD_Data) 317


Table Checker

Maximum allowable temperature: -9999

Material Grade: A105 (150)

Modifier: 3

Fabrication category: CSFF (7)

Note 1: -

Note 2: -

PDS Reference data

AABBCC: 6Q1C01
Commodity Code: VAUSAHGAAA
Weight Code: 490 pcf (52)
EDEN Modules Tables
______
GATR FEM_420_800_5
V1_AMS GATR_4625_420_800_A
VALVE_2_AMS VAUSAHGAAA
V1 GATR_FEM_800_3_A
OP_3
OPERATOR_3
OP3

21-Apr-92 Page: 2
SIZE-INDEPENDENT SPEC DATA
__________________________

Description: Gate valve, CL800, SWE, BB, OS&Y, full


port, ASTM-A105, trim 8, Smith 888

Piping Class: 1C0031

Size Range: 1st 3/4IN 1-1/2IN


2nd - -

Option: Full port (24)

End Preparation(s): SWE (421)

Rating(s): CL800

End geometry standard(s): Default (5)

Body geometry standard: Smith 1 (4625)

Maximum allowable temperature: -9999

Material Grade: A105 (150)

318 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

Modifier: 3

Fabrication category: CSFF (7)

Note 1: -

Note 2: -

PDS Reference data

AABBCC: 6Q1C01
Commodity Code: VAUSAHGCAA
Weight Code: 490 pcf (52)
EDEN Modules Tables
______
GATF FEM_420_800_5
V1_AMS GATF_4625_420_800_A
VALVE_2_AMS VAUSAHGCAA
V1 GATF_FEM_800_3_A
OP_3
OPERATOR_3
OP3

21-Apr-92 Page: 3
SIZE-INDEPENDENT SPEC DATA
__________________________
Description: Gate valve, CL150, RFFE, BB, OS&Y,
ASTM-A105, trim 8, Smith 815

Piping Class: 1C0031

Size Range: 1st 3/4IN 1-1/2IN


2nd - -

Option: RFFE (221)

End Preparation(s): RFFE (21)

Rating(s): CL150

End geometry standard(s): Default (5)

Body geometry standard: ANSI-B16.10 (40)

Maximum allowable temperature: -9999

Material Grade: A105 (150)

Modifier: 3

Fabrication category: CSFF (7)

Note 1: Use at flanged equipment connections.

Plant Design System (PDS) Reference Data Manager (PD_Data) 319


Table Checker

Note 2: -

PDS Reference data

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

21-Apr-92 Page: 133

SIZE-DEPENDENT SPEC DATA


________________________

Piping Class: 1C0031


AABBCC: 6Q1C01

1st Size 2nd Size Physical Data


Weight Generic Specific Sub-Component
________ ________ _______ ________ _____________
3/4IN 3/4IN
4.5Lb 1.1715In, 0.4375In Undefined, Undefined, 1.125In 11In, 4In
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
21-Apr-92 Page: 134

SIZE-DEPENDENT SPEC DATA


________________________

Piping Class: 1C0031


AABBCC: 6Q1C01

1st Size 2nd Size Physical Data


Weight Generic Specific Sub-Component
________ ________ _______ ________ _____________
3/4IN 3/4IN
6.25Lb 1.1715In, 0.4375In Undefined, Undefined, 1.125In 11In, 4In
1IN 1IN
9.75Lb 1.4538In, 0.4375In Undefined, Undefined, 1.375In 13In, 5.5In
1-1/2IN 1-1/2IN

320 Plant Design System (PDS) Reference Data Manager (PD_Data)


Table Checker

21.75Lb 2.0575In, 0.4375In Undefined, Undefined, 1.5625In 16.125In,


5.75In

21-Apr-92 Page: 376

TABLES NOT FOUND


________________
Tables Not Found Table Library
________________ _____________
REDC_39_300_S$10_300_S$XS_52 Physical Data Library
REDE_39_300_S$10_300_S$XS_52 Physical Data Library
STUD_120_150_5
STUD_120_150_80
STUD_120_300_5
STUD_160_150_5
STUD_160_150_80

21-Apr-92 Page: 377


TABLES FOUND
____________
Tables Found Table Library Table Revision Date
____________ _____________ ___________________
BALR_3028_420_600_A Physical Data Library Thu Jan 3 09:46:45 1991
BALR_FEM_600_9_A Physical Data Library Thu Jan 3 10:16:28 1991
BALSP_40_20_150_A Physical Data Library Thu Jan 3 10:01:23 1991
BALSP_BLT_150_9_A Physical Data Library Thu Jan 3 10:16:28 1991
BFYHP_4200_160_150_A Physical Data Library Thu Jan 3 10:08:15 1991
BFYHP_BLT_150_17_A Physical Data Library Thu Jan 3 10:16:33 1991
BLPAD_1026_120_150_A Physical Data Library Thu Jan 3 09:28:00 1991
BLPAD_1026_120_150_NREQD_52 Physical Data Library Thu Jan 3 09:28:01
1991
BLPAD_146_120_150_A Physical Data Library Thu Jan 3 09:28:48 1991
BLPAD_146_120_150_NREQD_52 Physical Data Library Thu Jan 3 09:28:51
1991
BLSPA_1026_120_150_A Physical Data Library Thu Jan 3 09:28:01 1991
BLSPA_1026_120_150_NREQD_52 Physical Data Library Thu Jan 3 09:28:02
1991
BLSPA_146_120_150_A Physical Data Library Thu Jan 3 09:28:49 1991
BLSPA_146_120_150_NREQD_52 Physical Data Library Thu Jan 3 0