Stress

PDS Stress Analysis Interface (PD_Stress) Reference Guide Document Number Version Date Pages DPDS3-PB-200025A PDS 7.1 April 2002 1-168 DPDS3-PB-200025B PDS 7.3 October 2004 Cover/Notice DPDS3-PB-200025C PDS 8.0 SE November 2005 169-182

Copyright Copyright 1984-2005 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.

Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Contractor Rights in Technical Data clause at DFARS 252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the License clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of Commercial Computer Software---Restricted Rights at 48 CFR 52.227-19, as applicable.

Unpublished---rights reserved under the copyright laws of the United States.

Intergraph Corporation

Huntsville, Alabama 35894-0001

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. 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.

Trademarks Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, and PDS are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. ISOGEN is a registered trademark of Alias Limited. Other brands and product names are trademarks of their respective owners.

If You Need Assistance________________

If You Need Assistance

Intergraph Online

Our web site brings you fast, convenient, up-to-the-minute information about Intergraphsproducts, services, and direction. Our web address is: http://www.intergraph.com.

Support

For the lasest Support Services information, use a World Wide Web browser to connect tohttp://www.intergraph.com/ppo/services/support.asp.

If you are outside of the United States, please call your local Intergraph office. The most up-to-date list of international offices and distributors is available on the web athttp://www.intergraph.com.

Intergraph Directory

The following numbers are only valid in the United States unless otherwise indicated. If youare outside the United States, please call your local Intergraph office.

Intergraph General Information

All countries 1-256-730-2000

Training Registration

1-800-766-7701 (U.S. Only)

1-256-730-5400 (Outside the U.S.)

Mailing Address

Intergraph Process, Power & Offshore300 Intergraph WayMadison, Alabama 35758U.S.A.

You can also reach us by electronic mail at [email protected].

3

________________

Documentation Contacts

We are constantly working on updates and improvements to the documents and othereducational media. If you have any suggestions on where we can improve the documentationor where you think more information is needed, let us know. You can reach us by:

Mail Intergraph Process, Power & OffshoreDocumentation Manager300 Intergraph WayMadison, AL 35758

4

Table of Contents________________

Table of Contents

If You Need Assistance ........................................................................................................ 3Intergraph Directory ............................................................................................................. 3

Preface ................................................................................................................................................. 9

Document Purpose ................................................................................................................ 9Document Prerequisites / Audience ...................................................................................... 9About this Document ............................................................................................................ 9Additional Information ......................................................................................................... 10

General Conventions .................................................................................................................... 11

Keyboard Conventions ......................................................................................................... 12Terminology ......................................................................................................................... 13

1. Introduction .................................................................................................................................. 15

2. PDS Environment ........................................................................................................................ 17

2.1 PD Shell .............................................................................................................................. 18

2.1.1 Batch Processes ....................................................................................................... 20

3. The Options File ........................................................................................................................... 21

3.1 Options File Structure ......................................................................................................... 223.2 Options File Keywords ....................................................................................................... 23

3.2.1 INTERGRAPH OPTIONS BLOCK ....................................................................... 233.2.2 VENDOR NAME ................................................................................................... 243.2.3 EXTERNAL FILES ................................................................................................ 25

3.2.3.1 PDS to Stress Symbol Map ...................................................................... 25

3.2.4 CODE NAME OF CODE PARAMETER DATA TABLE .................................... 253.2.5 LOADING DATA (LOAD) TABLE ...................................................................... 273.2.6 SERVICE LOADING (LSET) TABLE .................................................................. 273.2.7 ELEMENT CONNECTIVITY MAP TABLE ........................................................ 293.2.8 ELEMENT PROPERTY / CONNECTIVITY TABLE .......................................... 303.2.9 END PREPARATION TABLE .............................................................................. 323.2.10 FITTING NOMENCLATURE TABLE ............................................................... 323.2.11 HANGER TYPE TABLE ..................................................................................... 33

3.3 Example Options File .......................................................................................................... 34

5

PDS Stress Analysis Interface Users Guide - April 2002________________

Lab 1 - Project Setup & Options File .................................................................................. 40

4. Generating Neutral Files .............................................................................................................. 41

4.1 Model Files ......................................................................................................................... 444.2 Pipeline Names .................................................................................................................... 45

4.2.1 Extraction by Line Name Substring ........................................................................ 454.2.2 Extraction By Stress Analysis ID ............................................................................ 46Lab 2 - Generate a Neutral File ........................................................................................... 47

5. The Stress Analysis Neutral File .................................................................................................. 49

5.1 Neutral File Format ............................................................................................................. 495.2 Detailed Record Descriptions ............................................................................................. 52

5.2.1 INFO Record ........................................................................................................... 525.2.2 LOAD Record ......................................................................................................... 535.2.3 LSET Record ........................................................................................................... 535.2.4 CODE Record ......................................................................................................... 545.2.5 Component Records ................................................................................................ 55

5.2.5.1 Overall Component Record ...................................................................... 555.2.5.2 PROP Record ........................................................................................... 55

5.2.6 LNOD Record ......................................................................................................... 565.2.7 NODE Record ......................................................................................................... 58

5.3 Node Numbering Conventions ............................................................................................ 595.4 Example Neutral File .......................................................................................................... 61

6. Interpreting the HITS Report ....................................................................................................... 65

6.1 Example HITS Report ......................................................................................................... 666.2 Section 1: Basic Input Data and Raw Design File Data ...................................................... 726.3 Section 2: Design File Data Sorted by Coordinate ............................................................. 746.4 Section 3: Tracing Data ....................................................................................................... 766.5 Section 4: Design File Data Sorted by Topo ....................................................................... 786.6 Section 5: Design File Data in STR Order .......................................................................... 826.7 Using the HITS Report to Solve Problems ......................................................................... 84

Appendix A: Standard Note Library ................................................................................................ 87

A.1 Codelist 145 - Materials Grade ................................................................................................. 88A.2 Codelist 330 - CP Type/Termination/Preparation ..................................................................... 114A.3 Codelist 380 - Piping Component Type .................................................................................... 117A.4 Codelist 570 - Design Standard ................................................................................................. 124

Appendix B: PDS Design Database Format .................................................................................... 125

6

Table of Contents________________

B.1 Table 12 - Piping Segment Data ................................................................................................ 126B.2 Table 22 - Nozzles ..................................................................................................................... 128B.3 Table 34 - Piping Component Data ........................................................................................... 129B.4 Table 50 - Piping/Tubing Data .................................................................................................. 131B.5 Table 67 - Instrument Component Data .................................................................................... 133B.6 Table 80 - Pipe Support Data .................................................................................................... 136

Appendix C: PDS to Stress Analysis Symbol Map Table ............................................................... 137

C.1 Example PDSTRESS.TBL ........................................................................................................ 139

Appendix D: Warning & Error Messages ........................................................................................ 147

D.1 Warning Messages .................................................................................................................... 148D.2 Error Messages .......................................................................................................................... 150

Glossary ............................................................................................................................................... 155

Index .................................................................................................................................................... 163

7


8

Preface________________

Preface

Document Purpose

This document is a users guide for Intergraph Corporations PDS Stress Analysis Interface (PD_STRESS)software package. You can use the PDS Stress Analysis Interface product to perform stress analysis on threedimensional (3D) piping models.

This document is designed as a users guide; it is organized around the typical work flow of the product ratherthan presenting the comprehensive structure of the product.

Document Prerequisites / Audience

This document is intended for designers who are responsible for generating stress neutral files and have aworking knowledge of the standard interactive graphics system. Knowledge of 3D design systems is helpful butnot necessary. Also, you should be familiar with a text editor, such as Notepad or PFE.

About this Document

This document contains front matter, numbered sections, appendices, a glossary, and an index.

Section 1 Provides an overview of the product.

Section 2 Describes the PDS workstation environment. This includes information on the PD Shellenvironment and On-Line Help.

Section 3 Describes the options file. This includes the default file structure and keywords.

Section 4 Describes how to generate neutral files interactively. This includes information onaccessing the product and creating and manipulating product files.

Section 5 Describes the stress analysis neutral file. This includes record descriptions and nodenumbering conventions.

Section 6 Describes how to interpret the HITS reports. This includes interpreting each section andusing the report to solve problems.

Appendix A Displays the codelists pertaining to PD_Stress.

Appendix B Displays the PDS Piping Design Database Format.

Appendix C Describes the PDS to Stress Analysis Symbol Map.

9


Appendix D Describes error messages and corrective actions.

Additional Information

The following informational files are delivered with the PD_STRESS software in the win32app\ingr\pdstressdirectory.

File Name Contents

README Describes changes and additions to the product since the last version. Lists thenames and dates of the files in the current release. For a fixes release, the fileswhich have been modified are appended to the top of the initial file to providea history of all changes to the product. Includes Comments and TroubleReport numbers which describe what problems have been fixed. Providesspecial notices to the customer. Lists any exceptions made to the certification.

10

Preface________________

General Conventions

This document contains many visual cues to help you understand the meaning of certainwords or phrases. The use of different fonts for different types of information allows you toscan the document for key concepts or commands. Symbols help abbreviate and identifycommonly used words, phrases, or groups of related information.

Typefaces

Italic Indicates a system response, which is an explanation of what the software isdoing. For example,

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name, or dialog box title. Commandpaths are shown using an arrow between command names. For example,

Choose File > Open to load a new file.

Sans serif Indicates a system prompt or message, which requires an action be taken bythe user. For example,

Select first segment of alignment

Bold TypewriterIndicates what you should literally type in. For example,

Key in original.dat to load the ASCII file.

Normal TypewriterIndicates an actual file or directory name. For example,

The ASCII report is stored in the layout.rpt file.

11


SymbolsThis document uses the following symbols to represent mouse buttons and to identify specialinformation:

Command button Data button (usually the left mouse button) Reset/reject button (usually the right mouse button) Tentative button (usually the center mouse button)

Note Important supplemental information.

Warning Critical information that could cause the loss of data if not followed.

Technical tip or information provides information on what the software isdoing or how it processes information.

Map or path shows you how to get to a specific command or form.

More information indicates there is additional or related information.

Need a hint used with activities and labs, provides a tip or hint for doing theexercises.

Keyboard Conventions

The following list outlines the abbreviations this document uses for keyboard keys anddescribes how to use them in combination. You can make some menu selections through theuse of keyboard accelerators, which map menu selections to key combinations.

ALT Alternate keyCTRL Control keyDEL Delete keyENTER Enter keyESC Escape key

CTRL+z To hold down the Control key and press Z.ESC,k To press the Escape key, then K.

12

Preface________________

Terminology

Click To use a mouse or key combination to pick an item that begins anaction. For example,

Click Apply to save the changes.

Select To mark an item by highlighting it with key combinations or by pickingit with your cursor. Selecting does not initiate an action. Afterselecting an item, you click the action you want to affect the item. Forexample,

Select the file original.dat from the list box, then click Delete toremove it from the directory.

In addition, you would select items to define parameters, such asselecting toggle buttons. This also applies to selecting graphicelements from the design file. For example,

Select the line string to define the graphic template.

Tentative-select To place a tentative point on an existing graphic element in a designfile. If you are using the CLIX operating system, you tentative-selectby double-clicking with a mouse or pressing on a hand-heldcursor. If you are using the Windows NT operating system, youtentative-select by pressing a left-button, right-button chord.

Double-click To select and execute a command by clicking the mouse or hand-heldcursor button twice in rapid succession. This term implies that you areclicking the data button () as part of a menu or dialog box action.For example,

Double-click on the file original.dat to load it into the newsurface.

Drag To press and hold the data button () while moving the mouse orhand-held cursor.

Type To key a character string into a text box.

Key in To type in data and press ENTER to enter the data and execute thedefault action.

In a dialog box, pressing TAB after keying in data willenter the data and move the cursor to the next field.

13


14

Introduction________________

1. Introduction

The PD_Stress Analysis Interface product generates neutral output files from three-dimensional (3D) piping models created by PDS modeling packages as input for third partystress analysis packages.

The neutral file can be run on your own in-house pipe stress software or on any othercommercially available package capable of processing the Intergraph neutral file. Because ofits flexibility, you can change the contents of the neutral file and customize it for your specificuse.

The STRINP file collects user input and creates the ASCII file STRDEF.DAT which containsthe options file NEUDFLTS. This options file contains switches, options and tables allowingyou to control the information the Stress Analysis Interface enters into the neutral file. (Referto the Options File section for more information on the contents of the options.) The STRINPfile then displays the Stress Analysis Interface form allowing you to enter data to the ASCIIfile pdsstr.dat.

15


From the pdsstr.dat file, the Stress Analysis Interface reads the involved piping andequipment models, the pipeline names or stress ID and the options file.

The PDSSTR file then reads the 3D piping model and generates the stress analysis neutralfiles.

16

PDS Environment________________

2. PDS Environment

The PDS 3D software supports a variety of applications. All the supported applications use acommon interface that is controlled by the PD Shell program. This ensures consistencyacross 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. Themodules also provide an on-line Help capability for easy access to information while workingin the product.

The PDS 3D software uses available nucleus tools such as MicroStation and FORMS. Itsupports standard software such as NFS, NQS, and RIS required to set up data across anetwork. This design facilitates the use of non-PDS tools such as relational databases andthird party software.

The PD_Shell Environment and all batch jobs in the PDS 3D products interface toIntergraphs Network Licensing System.

17


2.1 PD Shell

The PD Shell program provides access to the various functions that are associated with thePDS 3D Modules. You can access the Plant Design System Environment form by

Double-clicking the PD_Shell icon.

This executes a control script that defines all of the environment variables that are needed torun the product, and it identifies the location of the product files. These files can be locatedon 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.

This form identifies the active project(s) and provides access to all the PDS functions.

Options

Schematics Environment Provides access to the PDS 2D modules that are used tocreate and modify piping and instrumentation diagrams, process flow diagrams, andinstrumentation database records.

Equipment Modeling Provides access to the Equipment Modeling module, whichprovides an interactive graphics environment that is used to create and revise equipmentmodel graphics and database information.

FrameWorks Environment Provides access to the FrameWorks module, whichprovides an environment that is used to create and revise structural models, create andrevise structural drawings, and propagate structural models.

18

PD Shell________________

Piping Designer Activates an interactive command environment that is used tocreate piping and in-line instrumentation in the model; revise existing model graphicsand database information; and verify the integrity of the data in the model.

Electrical Raceway Environment Provides access to the Electrical Racewaymodule, which provides an interactive environment that is used to create and reviseraceway models and access raceway utilities.

Piping Design Data Manager Provides access to a set of options that are used toverify the integrity of the graphic and database information that is associated with amodel.

Piping Model Builder Enables you to create piping graphics from a nongraphicsenvironment. This module is used with PD_Design to create an accurate 3D model ofthe piping network.

Pipe Stress Analysis Activates a set of forms that are used to extract informationfrom piping models for input to third-party pipe stress analysis products.

Interference Manager Activates a set of forms that are used to check forinterferences among project models and to control approved interferences.

Isometric Drawing Manager Activates a set of forms that are used to extractisometric drawings from piping models and to review or plot the created isometricdrawings.

Drawing Manager Activates a set of forms that are used to create and manipulatedrawings and drawing views; provide access to the interactive graphics environment fordrawings; and provide access to a plot manager and vector hiddenline manager.

DesignReview Integrator Activates a set of forms that are used to extractinformation to form label files for use in DesignReview and to review data from aDesignReview session.

Report Manager Activates a set of forms that are used to create and revise reportformat files and report on information in a project including Material Take-Off reports.

19


Project Administrator Provides access to a set of forms that are used to create aproject, 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 controlthe reference data for a project including Piping Job Specification data, GraphicCommodity Data, Alphanumeric Commodity Data, Standard Note Library, LabelDescription Library, and Piping Assembly Library.

Other Fields

User ID Used for access control. This field also sets the Review User ID for use inthe Interference Manager module.

If access control has been defined, you must key in a valid user ID as defined by yoursystem manager to gain access to the projects.

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 toselect 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 incompatiblewith the active project. For example, if the active project is a 2D-only project, youcannot access the the Interference Manager module.

If access control has been defined, only those projects for which you have some level ofaccess are displayed.

Message Area Displays prompts and messages that are associated with the activeprocess. Error messages are displayed in red.

2.1.1 Batch Processes

When you install the PDS 3D applications, the system creates the necessary batch queues forthat application. Refer to Loading PDS Products in the Project Administrator (PD_Project)Reference Guide for a listing of the batch queues.

PDS 3D uses these batch queues to allow you to continue working in the environment whilethe system processes a request. Many of the batch processes can be delayed for submission ata specified time.

When you submit a batch process the system sends an electronic mail message to the mailpath of the default login reporting the jobs completion status. The mail message also includesany error log information. The setup of this functionality is optional on Windows NT.

20

The Options File________________

3. The Options File

The options file contains switches, options, and tables that drive the PD_Stress Analysis Interface. This filegives you considerable flexibility in customizing the stress analysis neutral file.

When the input screen is first displayed on your workstation, this input field contains a default value obtainedby translating the variable name NEUDFLTS. The logical name is defined at the system level when the StressAnalysis product is installed on your system. You can override this system level assignment (and thus thescreen default) by exporting the variable to your own customized options file.

Intergraph delivers four options files, defaults.dat, caesarII.dat, adlpipe.dat andtriflex.dat, located in the c:\win32app\ingr\pdstress\dat\ directory. Thedefaults.dat file can be modified to the requirements of your third party stress analysis software. Thetriflex.dat file is set up to work with the AAA Technology and Specialties Co. stress analysis software.The caesarII.dat file is set up to work with the COADE, Inc. CAESAR II stress analysis software. Theadlpipe.dat file is set up to work with the Rebis ADL Pipe stress analysis sofware.

21


3.1 Options File Structure

The options file is composed of one set of options and several tables. The option block and each table ispreceded in the options file by a keyword identifying the option or table. The keyword must be in upper caseand begin in column 1 and should not be surrounded by single quotes. The keywords and data that follow themcan appear in any order in the options file. The end of each table is delimited by the same keyword stringprefixed with the characters ENDOF.

Comments, identified by an ! in column one, can be placed anywhere between the two keyword strings whichdelimit a table. Comments cannot be placed outside of a table.

Entries in tables consist of a row of numbers and sometimes character strings separated by commas. Thegeneral form for tables is:

TABLE_KEYWORDn1, n2, c1, n3, ... !here is a comment.

!here is another comment.

m1, m2, cm, m3, ...ENDOF TABLE_KEYWORD

where:

TABLE_KEYWORD is the table keyword

n1, n2, ... are numbers in the first table entry

c1 is a character string in the first entry

m1, m2, ... are numbers in the last table entry

cm- is a character string in the last entry

ENDOF TABLE_KEYWORD defines the end of the table

22

Options File Keywords________________

3.2 Options File Keywords

The options file keywords include:

INTERGRAPH OPTIONS BLOCKVENDOR NAMEEXTERNAL FILESCODE NAME OF CODE PARAMETER DATA TABLELOADING DATA (LOAD) TABLESERVICE LOADING (LSET) TABLEELEMENT CONNECTIVITY MAP TABLEELEMENT PROPERTY / CONNECTIVITY TABLEEND PREPARATION TABLEFITTING NOMENCLATURE TABLEHANGER TYPE TABLE

3.2.1 INTERGRAPH OPTIONS BLOCK

The Intergraph Options Block is a group of options that directly controlling the actions of the stress analysisinterface. The specific meaning of each option is outlined below:

Word Value Meaning

1 val Initial (first) node number for nodes generated at component connections

2 val Increment to be used in generating subsequent node numbers - starting from thevalue specified in word 1, 3 and 4

3 val Initial node number for numbering nodes at network endpoints

4 val Initial node number for numbering nodes internal to components (for example, thenodes at elbow or tee origins)

Val cannot be greater than four digits.

5 0 Turn warning messages off1 Turn warning messages on

6 val Magnitude of spring constant indicating a support is rigid - where val implies amagnitude of 10**val

7 1 must be set to 1


9 0 not used at this time


23



12 0 Extracts the network by substring of the pipeline name attribute,LINE_NUMBER_LABEL (Refer to Appendix B, table 12, column 2.)

1 Extracts the network by substring of the stress analysis ID attribute,STRESS_SYSTEM_NO (Refer to Appendix B, table 12, column 52.)

2 Extracts the network by equality of the pipeline name attribute,LINE_NUMBER_LABEL (Refer to Appendix B, table 12, column 2.)

3 Extracts the network by equality of the stress analysis ID attribute,STRESS_SYSTEM_NO (Refer to Appendix B, table 12, column 52.)

13 0 Does not print the UNITS record containing the length and weight units of theneutral file

1 Prints the UNITS record in the neutral file

14 20 Model file component connectivity tolerance in uors

15 0 Does not print the VERSION record containing the stress interface file formatversion number

1 Prints the VERSION record in the neutral file

16 0 Does not print the VENDOR record containing the pipe stress vendors name1 Prints the VENDOR record in the neutral file

17 0 Do not generate thermal movement for nozzles.1 Generate a record indicating the normal XYZ and alternate XYZ thermal growth of

nozzles. (Refer to Appendix B, table 22, columns 19 through 24)

18 0 Default to output pipeline with one connected item from each connected pipeline1 Suppress any continuation item on connected pipelines

19 0 Default to use filename of up to 12 characters for file specification1 Use long filename of up to 40 characters for file specification

Sample Intergraph Options Block Table

INTERGRAPH OPTIONS BLOCK!NOTE: Only 17 options in use , 45 maximum! 1-16 2-17 3 4 5 6 7 8 9 10 11 12 13 14 15

1, 5, 950, 951, 0, 6, 1, 1, 1, 1, 1, 1, 1, 20, 1,1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 999

ENDOF INTERGRAPH OPTIONS BLOCK

3.2.2 VENDOR NAME

The vendor name table contains the name of the pipe stress software vendor. Use 40 characters maximum forthe vendor name. This table is used to associate a particular options file with a specific pipe stress package. Itresults in a record in the neutral file which can be checked by the interface software.

24


Sample Vendor Name Table

VENDOR NAME!NOTE: 40 characters maximum!234567890123456789012345678901234567890TRIFLEX Rel 2.6.8 Aug 97ENDOF VENDOR NAME

3.2.3 EXTERNAL FILES

The files table contains the names of external files used by the stress analysis interface. Use 40 charactersmaximum for each file name. The entries in this table are order dependent.

Sample External Files Table

EXTERNAL FILES!NOTE: 40 characters maximum, 5 files maximum! 1234567890123456789012345678901234567890d:\stress\input\pdstress.tbl !PDS TO STRESS MAP (path is user defined)ENDOF EXTERNAL FILES

3.2.3.1 PDS to Stress Symbol Map

This table maps PDS component names to generic stress analysis components. This library is required and mustbe specified. Refer to PDS to Stress Analysis Symbol Map Table, page 137 for more information on the formatand contents of the table.

3.2.4 CODE NAME OF CODE PARAMETER DATATABLE

This table is used to associate a code number with each value of a segments design standard attribute (Refer toAppendix B, table 12, column 35). When the neutral file is generated, the code number is entered with thevalue held in Piping Segment table 12, column 35. If a match is found, the code number from the table is put inthe neutral file CODE record. If no match is found, the default code number is placed in the record.

The design standard attribute is the piping designers input responsibility. If this attribute is leftblank, the default value is used.

The format of an entry in this table is:

VAL, STRING

where:

25


VAL is the code number from Piping Segment Design Standard (Refer to Appendix B, table12, column 35).

STRING is a text string defining the code description, year and seismic level

The VAL, STRING combination must match the standard note CL570 in the Standard NoteLibrary. (Refer to Appendix A.)

Sample Code Name of Code Parameter Data Table

CODE NAME OF CODE PARAMETER DATA TABLE!NOTE: 20 characters maximum (type//year//level), 50 codes maximum!attribute (12,35) is table input! 12345678901234567890

0, B31.1,1983 !default1, ASME2,1982,B2, B31.43, ASME14, ASME2,1972,A5, ASME2,1972,B6, ASME2,1972,C7, ASME2,1972,D8, ASME2,1974,A9, ASME2,1974,B10, ASME2,1974,C11, ASME2,1974,D12, ASME2,1977,A13, ASME2,1977,B14, ASME2,1977,C15, ASME2,1977,D16, ASME2,1980,A17, ASME2,1980,B18, ASME2,1980,C19, ASME2,1980,D20, ASME2,1982,A21, B31.322, ASME2,1982,C23, ASME2,1982,D24, ASME3,197225, ASME3,197726, ASME3,198027, ASME3,198228, B31.1,197329, B31.1,197730, B31.1,198031, B31.1,198332, BS80650, BS3351

ENDOF CODE NAME OF CODE PARAMETER DATA TABLE

26


3.2.5 LOADING DATA (LOAD) TABLE

This table is used to generate the LOAD records in the neutral file. The format of a table entry is:

-6, I, J, PATT(I), TATT(I), ... PATT(J), TATT(J)

where:

-6 is a code that indicates to the interface that a segment ID should be generated in therecord. You can not change this number or its position in the record.

I subscript of the lowest temperature, pressure pair

J subscript of the highest temperature, pressure pair

PATT(n) table, column pair identifying the column for obtaining a pressure from the database(Refer to Appendix B.)

TATT(n) table, column pair identifying the column for obtaining a temperature from thedatabase (Refer to Appendix B.)

Sample Loading Data (Load) Table

LOADING DATA (LOAD) TABLE!a.: Intergraph segment id (do not change)!b.: table entry number for first set of pressure/temperature pairs!c.: table entry number for last set of pressure/temperature pairs!d. & e.: LSET 1 = normal operating pressure & temperature (1st row)!f. & g.: LSET 2 = alternate operating pressure & temperature (1st row)!h. & i.: LSET 3 = normal design pressure & temperature (1st row)! a. b. c. d. e. f. g. h. i.

-6, 1, 3, 12,24, 12,25, 12,26, 12,27, 12,28, 12,29-6, 4, 6, 12,24, 12,25, 12,26, 12,27, 12,30, 12,31

!d. & e.: LSET 4 = normal operating pressure/temperature (2nd row)!f. & g.: LSET 5 = alternate operating pressure/temperature (2nd row)!h. & i.: LSET 6 = alternate design pressure/temperature (2nd row)ENDOF LOADING DATA (LOAD) TABLE

3.2.6 SERVICE LOADING (LSET) TABLE

This table is used to identify the pressure/temperature pairs used from each segment for analysis underdeadweight, hot conditions, cold conditions, and wind loading conditions.

This table allows you to specify the pressure/temperature pair used under each of the analysis conditions foreach segment. The simplest case uses the same pressure/temperature from each segment for each of thedifferent analysis conditions. A more complicated situation is also allowed where some segment attributedictates that a given set of pressure/temperature pairs should be used for that specific segment.

27


The format of a single entry in this table is:

TABATT, FLAG, VAL, DWT, HOT, COLD, WIND

where:

TABATT table, column pair identifying the attribute from the segment to be compared withVAL. The first table entry contains 0,0 for this item. This defines the default set ofT,P pairs to be used. If there are no other table entries, the same T,P pairs will beused from each segment for all analysis conditions.

FLAG set to 1 if VAL is a code list numberset to 0 if VAL is not a code list number

VAL value of the database attribute triggering use of the following T,P pairs for a segment

DW Pressure/temperature|load set|pair for deadweight analysis of this segmentHOT Pressure/temperature|load set|pair for hot condition analysis of this segmentCOLD Pressure/temperature|load set|pair for cold condition analysis of this segmentWIND Pressure/temperature|load set|pair for wind analysis of this segment

The pressure/temperature attributes are the piping designers responsibility.

Sample Service Loading (LSET) Table

SERVICE LOADING (LSET) TABLE!NOTE: 50 maximum service loading pair!a.: DB attribute pair to retrieve search value.!b.: flag. = 0, c. is code list number; flag = 1, c. is code list text!c.: code list. 16 characters maximum. 0 = default.!d.: deadweight condition with loading number (LOAD #)!e.: hot temperature condition with loading number (LOAD #)!f.: cold temperature condition with loading number (LOAD #)!g.: wind loading condition with loading number (LOAD #)! a. b. c. d. e. f. g.

!2345678901234560,0, 0, 0, 3, 6, 5, 3 !default

12,9, 0, 1, 1, 2, 3, 412,9, 1, VAL, 3, 6, 5, 312,9, 1, FC, 1, 2, 3, 412,9, 1, OWS, 3, 4, 5, 612,9, 1, 8, 3, 4, 5, 112,9, 0, 8, 3, 4, 5, 2

ENDOF SERVICE LOADING (LSET) TABLE

28


3.2.7 ELEMENT CONNECTIVITY MAP TABLE

This table provides information about each stress analysis generic component. There is one entry in this tablefor each generic stress analysis component used in the PDS to stress analysis symbol map. The format of anelement in this table is:

NAME, CAT, NODES, ONODE

where:

NAME generic component name (Refer to Appendix C.)

CAT generic component category. Use one of the following values for category:

1 simple component2 valve3 support

NODES number of nodes the component generates.

ONODE defines which node in the node list is the origin node. If this item is 0, then no nodewill be generated for the component origin. This item should always be set so thatorigin nodes appear in the node list after nodes at connect points.

Sample Element Connectivity Map Table

ELEMENT CONNECTIVITY MAP TABLE!note: 25 maps maximum!a.: generic name, maximum 2 characters!b.: category, 1=simple; 2=valve; 3=support!c.: number of connectivity nodes.!d.: cp 0. if (cp 0 not equal to 0 a node will be generatd)! a. b. c. d.3W, 2, 4, 44W, 2, 5, 5AV, 2, 3, 3CR, 1, 5, 5EL, 1, 3, 3ER, 1, 2, 0FL, 1, 2, 0HA, 3, 2, 0MT, 1, 3, 3PI, 1, 2, 0NP, 1, 2, 0RB, 1, 2, 0RD, 1, 2, 0RI, 1, 3, 3TW, 1, 4, 4TR, 1, 2, 0TU, 1, 2, 0TS, 1, 2, 0TE, 1, 4, 4TO, 1, 2, 0VA, 2, 3, 3ENDOF ELEMENT CONNECTIVITY MAP TABLE

29


3.2.8 ELEMENT PROPERTY / CONNECTIVITYTABLE

This table forms the overall component records in the neutral file forms the PROP records containingcomponent properties. When the interface generates the records for a component, it first gathers all the entriesin this table applying to the component. The generic item name of the component and the PDS database type(component, pipe, instrument or support) identify the table entries that apply.

The format of an entry in the table is:

NAME, PDSTYP, -1, FORMNO, ATTLST

where:

NAME generic component name obtained from the PDS to stress analysis symbol map

PDSTYP number identifying the component type. You should use one of the following:

1 PDS component is a component or engineered item2 PDS component is a pipe3 PDS component is an instrument4 PDS component is a pipe support

When a generic pipe stress component can be generated from either a componentor an instrument in the model, there must be a set of entries in this table for eachtype.

-1 special flag indicating to the interface that the record will contain a component ID.This table entry must be set to -1.

FORMNO data list format number. This number together with the generic component nameallows you to identify all of the data on a particular record. The Intergraph optionsfile contains form numbers adhering to the following convention:

0 element connectivity (the overall component rcd)1 general component data2 specific component data3 connect point 1 data4 connect point 2 data5 connect point 3 data6 connect point 4 data

ATTLST list of table, column pairs specifying columns from which to obtain values to insertin output records. The table, column pairs can specify either segment orcomponent level columns. The entity specified in an table, column pair mustcorrespond to the PDSTYP of the table entry.

30


You can also specify one of the following special table, column pairs to map acomposite column in the output record.

0, 0 insert a blank field into the record0,-1 unique component ID0,-2 special label formed by concatenating the size, schedule and commodity code

attributes0,-3 insulation unit weight (pipe only)0,-4 insulation weight (components and instruments only)0,-5 component or pipe thickness.0,-6 unique segment ID0,-7 fitting type from the FITTING NOMENCLATURE TABLE0,-8 flare radius, large end (reducer only)0,-9 large end cylinder length (reducer only)0,-10 flare radius, small end (reducer only)0,-11 small end cylinder length (reducer only)0,-12 cone angle (reducer only)0,-13 pad angle (reinforced tee only)0,-14 unique analysis code ID (pointer to a CODE record)0,-15 valve type from the PDS to stress analysis symbol map (valves only)0,-16 valve angle (valves only)0,-17 hanger type from the HANGER TYPE TABLE0,-18 local coordinate system primary axis for a pipe support0,-19 local coordinate system secondary axis for a pipe support0,-20 end prep code from END PREPARATION TABLE0,-21 segment length (miter elbow only)0,-22 dry unit weight (pipe only)0,-23 wet unit weight (pipe only)0,-24 actual pipe length for each split pipe section

Sample Element Property/Connectivity Table

PI, 2, -1, 0, 0,-2, 50,2, 0,-14, !here for user defined DDLsPI, 2, -1, 1, 50,21, 0,-22, 0,-23, 0,0, 12,15, 0,0, 0,-3PI, 2, -1, 3, 50,7, 50,8, 0,-20, 0,-5, 50,11, 0,-6PI, 2, -1, 4, 50,7, 50,8, 0,-20, 0,-5, 50,11, 0,-6

Sample Property Record

PI, 5B00031G,6"STDPAAAAAWAAA,,CODE20, 5, 10PROP,PI, 5B00031G, 1,A53-B,0.1581E+01,0.1043E+01,,-32768.000000,,-0.6395E+11PROP,PI, 5B00031G, 3,6.0,6.625000,BW,0.28,, B00031GPROP,PI, 5B00031G, 4,6.0,6.625000,BW,0.28,, B00031G

31


3.2.9 END PREPARATION TABLE

This table is used to determine an endprep code to insert in the neutral file given a generic termination type fromthe model database. The format of an entry in this table is:

GENTYP, TEXT

where:

GENTYP generic termination type for an end prep (Refer to CL330, Appendix A.)

TEXT two character max string identifying the end prep. This text string should beidentifiable by the stress analysis software.

Sample End Preparation Table

END PREPARATION TABLE!NOTE: 2 character maximum for end prep.

0, BW !default20, WN !flange80, LJ !lap joint300, BW !butt weld, as welded310, FL !butt weld, flush390, PL !plain end420, SO !socket fitting440, SP !screwed pipe joint

ENDOF END PREPARATION TABLE

3.2.10 FITTING NOMENCLATURE TABLE

This table allows you to assign a fitting type number to a specific component based upon the commodity code ofthe fitting. If no commodity code in the table matches that of the component, the first entry in the table is usedfor the fitting type field in a PROP record. The format of an entry in this table is:

CCODE, CTYPE

where:

CCODE is a component commodity code. Should be set to DEFAULT for the default entry.

CTYPE stress analysis fitting code. This text string should be identifiable by the stressanalysis software.

32


Sample Fitting Nomenclature Table

FITTING NOMENCLATURE TABLE!NOTE: 16 characters maximum for commodity code, 200 maximum codes

!234567890123456DEFAULT, 0 !defaultPAAAABBAAA, 2WRAAABBAAA, 4WAAAABBAAA, 23LSBZZZZAAA, 21VABBAALYAA, 19WOAAABBAFA, 20WAAAABBASA, 21VBBWAAOHAA, 25FAABBBBAAA, 18FCV123, 17VCBWAANHAA, 16WOAAABBAAA, 15VCABAAYYAA, 14

ENDOF FITTING NOMENCLATURE TABLE

3.2.11 HANGER TYPE TABLE

With this table, you can assign a support type number to a pipe support based upon the value of the pipe supporttype attribute (Refer to Appendix B, table 80, attribute 5.).

The format of an entry in this table is:

PDSCODE, STYPE

where:

PDSCODE the PDS code number identifying the support type (Refer to CL380, Appendix A.)

STYPE support type number recognized by your stress analysis software

Sample Hanger Type Table

HANGER TYPE TABLE!NOTE: 50 attribute values maximum.!a.: data base attribute value ( table 80, attribute 5)!b.: hanger type, numeric values only! a. b.

0, 99 ! default1, 99 ! default

909, 99 ! anchor911, 99 ! 1-way restraint913, 99 ! 2-way restraint923, 99 ! variable spring927, 99 ! damping support

ENDOF HANGER TYPE TABLE

33


3.3 Example Options File

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! INTERGRAPH VERSION 2! MODIFICATIONS / REVISIONS!!! Added NP generic name for nipples 27-APR-1998! Added TR, TU, TW, TS, TO generic names for branch elements 27-JUNE-1998!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!note: general rules! (1) upper case words are reserved words.! (2) all data should be seperated by commas! (3) exclaimation ! for comments; tab, spaces are acceptedbetween tables

INTERGRAPH OPTIONS BLOCK!NOTE: Only 17 options in use, 45 maximum! 1-16 2-17 3 4 5 6 7 8 9 10 11 12 13 14 15

5, 5, 6005, 7005, 0, 6, 1, 1, 1, 1, 1, 1, 1, 20, 1,1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 999

ENDOF INTERGRAPH OPTIONS BLOCK

VENDOR NAME!NOTE: 40 characters mamimum!234567890123456789012345678901234567890TRIFLEX Rel 2.6.8 Aug 97ENDOF VENDOR NAME

EXTERNAL FILES!NOTE: 40 characters maximum, 5 files maximum! 1234567890123456789012345678901234567890d:\stress\input\pdstress.tbl !PDS TO STRESS MAP(path is user defined)ENDOF EXTERNAL FILES

CODE NAME OF CODE PARAMETER DATA TABLE!NOTE: 20 characters maximum (type//year//level), 50 codes maximum!attribute (12,35) is table input! 123456789012345678900, B31.1,1983 !default1, ASME2,1982,B2, B31.43, ASME14, ASME2,1972,A5, ASME2,1972,B6, ASME2,1972,C7, ASME2,1972,D8, ASME2,1974,A9, ASME2,1974,B10, ASME2,1974,C11, ASME2,1974,D12, ASME2,1977,A13, ASME2,1977,B14, ASME2,1977,C15, ASME2,1977,D16, ASME2,1980,A17, ASME2,1980,B18, ASME2,1980,C19, ASME2,1980,D20, ASME2,1982,A21, B31.322, ASME2,1982,C23, ASME2,1982,D24, ASME3,197225, ASME3,197726, ASME3,198027, ASME3,198228, B31.1,197329, B31.1,197730, B31.1,198031, B31.1,1983

34

Example Options File________________

32, BS80650, BS3351

ENDOF CODE NAME OF CODE PARAMETER DATA TABLE

LOADING DATA (LOAD) TABLE!a.: Intergraph segment id (do not change)!b.: table entry number for first set of pressure/temperature pairs!c.: table entry number for last set of pressure/temperature pairs!d. & e.: LOAD 1 = normal operating pressure & temperature (1st row)!f. & g.: LOAD 2 = alternate operating pressure & temperature (1st row)!h. & i.: LOAD 3 = normal design pressure & temperature (1st row)! a. b. c. d. e. f. g. h. i.-6, 1, 3, 12,24, 12,25, 12,26, 12,27, 12,28, 12,29-6, 4, 6, 12,24, 12,25, 12,26, 12,27, 12,30, 12,31

!d. & e.: LOAD 4 = normal operating pressure/temperature (2nd row)!f. & g.: LOAD 5 = alternate operating pressure/temperature (2nd row)!h. & i.: LOAD 6 = alternate design pressure/temperature (2ndst row)ENDOF LOADING DATA (LOAD) TABLE

SERVICE LOADING (LSET) TABLE!NOTE: 50 maximum service loading pair!a.: DB attribute pair to retrieve search value.!b.: flag. = 0, c. is code list number; flag = 1, c. is code list text!c.: code list. 16 characters maximum. 0 = default.!d.: deadweight condition with loading number (LOAD #)!e.: hot temperature condition with loading number (LOAD #)!f.: cold temperature condition with loading number (LOAD #)!g.: wind loading condition with loading number (LOAD #)! a. b. c. d. e. f. g.

!2345678901234560,0, 0, 0, 3, 6, 5, 3 !default12,9, 0, 1, 1, 2, 3, 412,9, 1, VAL, 3, 6, 5, 312,9, 1, FC, 1, 2, 3, 412,9, 1, OWS, 3, 4, 5, 612,9, 1, 8, 3, 4, 5, 112,9, 0, 8, 3, 4, 5, 2ENDOF SERVICE LOADING (LSET) TABLE

ELEMENT CONNECTIVITY MAP TABLE!NOTE: 25 maps maximum!a.: generic name, 2 characters maximum!b.: category, 1=simple; 2=valve; 3=support!c.: number of connectivity nodes.!d.: cp 0. if (cp 0 not equal to 0 a node will be generatd)!a. b. c. d.3W, 2, 4, 44W, 2, 5, 5AV, 2, 3, 3CR, 1, 5, 5EL, 1, 3, 3ER, 1, 2, 0FL, 1, 2, 0HA, 3, 2, 0MT, 1, 3, 3PI, 1, 2, 0NP, 1, 2, 0RB, 1, 2, 0RD, 1, 2, 0RI, 1, 3, 3TW, 1, 4, 4TR, 1, 2, 0TU, 1, 2, 0TS, 1, 2, 0TE, 1, 4, 4TO, 1, 2, 0VA, 2, 3, 3ENDOF ELEMENT CONNECTIVITY MAP TABLE

ELEMENT PROPERTY / CONNECTIVITY TABLE!NOTE:1-for this table, generic name, component type, and form typeare used to form the unique key to distinguish each record.! records can be arbitary order.! 2-for attribute pair: (0,0) means dummy, no value; (0,-n)means reserved by PDSSTRESS interface system, where n = 1, ...! 3-15 attribute pairs maximum (including user definedattributes) for each table entry!

35


!data base attributes reserved by interface system:!-1 : Intergraph component id!(0,-2) : special label!(0,-3) : insulation unit weight (PI, RI)!(0,-4) : insulation weight (component/instrument)!(0,-5) : component, pipe thickness!(0,-6) : seg. id!(0,-7) : fitting type!(0,-8) : flare radius, large end (RD, ER)!(0,-9) : length, large end cylinder (RD, ER)!(0,-10): flare radius, small end (RD, ER)!(0,-11): length, small end cylinder (RD, ER)!(0,-12): cone angle (RD, ER)!(0,-13): pad angle (TR, TU, TW, TS, TO, TE)!(0,-14): code name of code parameter data!(0,-15): type descriptor (VA, AV, 3W)!(0,-16): valve angle (VA, AV, 3W)!(0,-17): hanger type!(0,-18): local x (HA, BD, BE)!(0,-19): local y (HA, BD, BE)!(0,-20): end prep code. If this field (0,-..) then END PREP TABLEwill be output, else PDS end prep code text is output.!(0,-21): segment length (miter) (EL, MT)!(0,-22): dry unit weight (PI, RI)!(0,-23): wet unit weight (PI, RI)! FOR PIPING/TUBING!a.: generic name, maximum 2 characters.!b.: component type: 1=component, 2=pipe, 3=instrument, 4=support!c.: Intergraph component id!d.: form type 0 = connectivity record, others = property records!e.: pipe specification (special label)!f.: tag (for component, if its engineered item then (3,3), else NULL!g.: code name of code parameter! a. b. c. d. e. f. g. h. i. j.PI, 2, -1, 0, 0,-2, 50,2, 0,-14, !here for user defined DDLs

!e.: material code!f.: dry weight (dry unit weight for PI)!g.: wet weight (wet unit weight for PI)!h.: intensification at component center!i.: symbol i.d.!j.: radius of curvature (RI only)!k.: insulation unit weight! a. b. c. d. e. f. g. h. i. j. k.PI, 2, -1, 1, 50,21, 0,-22, 0,-23, 0,0, 12,15, 0,0, 0,-3

!e.: OD nominal!f.: OD!g.: end prep code.!h.: thickness!i.: pressure rating!j.: segment id! a. b. c. d. e. f. g. h. i. j.PI, 2, -1, 3, 50,7, 50,8, 0,-20, 0,-5, 50,11, 0,-6PI, 2, -1, 4, 50,7, 50,8, 0,-20, 0,-5, 50,11, 0,-6

! FOR NIPPLES-NP, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsNP, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 34,19, 0,-3NP, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6NP, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR BENT PIPERI, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsRI, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 34,19, 0,-3RI, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6RI, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR RIGID BODIES-COMPONENTS-RB, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsRB, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4RB, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6RB, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR RIGID BODIES-INSTRUMENTS-RB, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLsRB, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 12,15, 0,-7, 0,-4RB, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6RB, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

! FOR ELBOWS & MITERS-EL, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsEL, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4EL, 1, -1, 2, 34,19, 34,20, 34,30, 0,-21EL, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

36


EL, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6! FOR FUTURE USEMT, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsMT, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4MT, 1, -1, 2, 34,19, 34,20, 34,30, 0,-21MT, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6MT, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR TEESTW, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsTW, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4TW, 1, -1, 2, 34,19, 0,-13, 34,20TW, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6TW, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6TW, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

! FOR REINFORCING PADSTR, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsTR, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4TR, 1, -1, 2, 34,19, 0,-13, 34,20TR, 1, -1, 3, 34,49, 34,50, 34,51, 0,-5, 34,53, 0,-6TR, 1, -1, 4, 34,62, 34,63, 34,64, 0,-5, 34,66, 0,-6

! FOR BRANCH COMPONENTSTU, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsTU, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4TU, 1, -1, 2, 34,19, 0,-13, 34,20TU, 1, -1, 3, 34,49, 34,50, 34,51, 0,-5, 34,53, 0,-6TU, 1, -1, 4, 34,62, 34,63, 34,64, 0,-5, 34,66, 0,-6

! FOR SWEPOLETS-TS, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsTS, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4TS, 1, -1, 2, 34,19, 0,-13, 34,20TS, 1, -1, 3, 34,49, 34,50, 34,51, 0,-5, 34,53, 0,-6TS, 1, -1, 4, 34,62, 34,63, 34,64, 0,-5, 34,66, 0,-6

! FOR TEESTE, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsTE, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4TE, 1, -1, 2, 34,19, 0,-13, 34,20TE, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6TE, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6TE, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

! FOR OLETSTO, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsTO, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4TO, 1, -1, 2, 34,19, 0,-13, 34,20TO, 1, -1, 3, 34,49, 34,50, 34,51, 0,-5, 34,53, 0,-6TO, 1, -1, 4, 34,62, 34,63, 34,64, 0,-5, 34,66, 0,-6

! FOR CONCENTRIC REDUCERSRD, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsRD, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4RD, 1, -1, 2, 0,-8, 0,-9, 0,-10, 0,-11, 0,-12RD, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6RD, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR ECCENTRIC REDUCERS-ER, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsER, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4ER, 1, -1, 2, 0,-8, 0,-9, 0,-10, 0,-11, 0,-12ER, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6ER, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR FLANGESFL, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsFL, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4FL, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6FL, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR INLINE VALVES-COMPONENTS-VA, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsVA, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4VA, 1, -1, 2, 34,28, 0,-15, 0,-16VA, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6VA, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR INLINE VALVES-INSTRUMENTSVA, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLsVA, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 12,15, 0,-7, 0,-4VA, 3, -1, 2, 67,23, 0,-15, 0,-16VA, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6VA, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

! FOR ANGLE VALVES-COMPONENTSAV, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsAV, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4AV, 1, -1, 2, 34,28, 0,-15, 0,-16

37


AV, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6AV, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! FOR ANGLE VALVES-INSTRUMENTS-AV, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLsAV, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 12,15, 0,-7, 0,-4AV, 3, -1, 2, 67,23, 0,-15, 0,-16AV, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6AV, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

! FOR CROSSESCR, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLsCR, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-4CR, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6CR, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6CR, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6CR, 1, -1, 6, 34,88, 34,89, 0,-20, 0,-5, 34,92, 0,-6

! FOR 3-WAY VALVES-COMPONENTS3W, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs3W, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-43W, 1, -1, 2, 34,28, 0,-15, 0,-163W, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-63W, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-63W, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

! FOR 3-WAY VALVES-INSTRUMENTS-3W, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLs3W, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 12,15, 0,-7, 0,-43W, 3, -1, 2, 67,23, 0,-15, 0,-163W, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-63W, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-63W, 3, -1, 5, 67,81, 67,82, 0,-20, 0,-5, 67,85, 0,-6

! FOR 4-WAY VALVES-COMPONENT4W, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs4W, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 12,15, 0,-7, 0,-44W, 1, -1, 2, 34,28, 0,-15, 0,-164W, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-64W, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-64W, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-64W, 1, -1, 6, 34,88, 34,89, 0,-20, 0,-5, 34,92, 0,-6

! FOR 4-WAY VALVES-INSTRUMENT4W, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLs4W, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 12,15, 0,-7, 0,-44W, 3, -1, 2, 67,23, 0,-15, 0,-164W, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-64W, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-64W, 3, -1, 5, 67,81, 67,82, 0,-20, 0,-5, 67,85, 0,-64W, 3, -1, 6, 67,94, 67,95, 0,-20, 0,-5, 67,98, 0,-6

! FOR PIPE SUPPORTS & HANGERSHA, 4, -1, 0, 0,-2, 80,2, 0,-14, !here for user defined DDLsHA, 4, -1, 1, 0,0, 80,15, 0,-17, 80,19HA, 4, -1, 2, 80,28, 80,29, 80,30, 80,31, 80,32, 80,33HA, 4, -1, 4, 0,-18, 0,-19

! local x local yENDOF ELEMENT PROPERTY / CONNECTIVITY TABLE

END PREPARATION TABLE!NOTE: 2 character maximum for end prep.0, BW !default20, WN !flange80, LJ !lap joint300, BW !butt weld, as welded310, FL !butt weld, flush390, PL !plain end420, SO !socket fitting440, SP !screwed pipe joint

ENDOF END PREPARATION TABLE

FITTING NOMENCLATURE TABLE!NOTE: 16 characters maximum for commodity code, 200 maximum codes!234567890123456DEFAULT, 0 !defaultPAAAABBAAA, 2WRAAABBAAA, 4WAAAABBAAA, 23LSBZZZZAAA, 21VABBAALYAA, 19WOAAABBAFA, 20WAAAABBASA, 21VBBWAAOHAA, 25FAABBBBAAA, 18

38


FCV123, 17VCBWAANHAA, 16WOAAABBAAA, 15VCABAAYYAA, 14

ENDOF FITTING NOMENCLATURE TABLE

HANGER TYPE TABLE!NOTE: 50 attribute values maximum.!a.: data base attribute value ( table 80, attribute 5)!b.: hanger type, numeric values only! a. b.

0, 99 ! default1, 99 ! default

909, 99 ! anchor911, 99 ! 1-way restraint913, 99 ! 2-way restraint923, 99 ! variable spring927, 99 ! damping supportENDOF HANGER TYPE TABLE

39


Lab 1 - Project Setup & Options File

1. In the project location create the following directories:

e:\pbs_train\stresse:\pbs_train\stress\inpute:\pbs_train\stress\output

2. Copy the delivered files to the project location using drag and drop:

c:\win32app\ingr\pdstress\dat\*.* -> e:\pbs_train\stress\input

3. Rename the options file:

defaults.dat -> stress.dat

4. Modify CL570 in the Standard Note Library to match the values in the Code Parameters DataTable section in the stress.dat file. Do not forget to post the unapproved data to the approveddatabase.

5. Modify the Intergraph Options Block section in the stress.dat file to reflect thefollowing node number convention:

First Node = 5Increment by = 5End Nodes Start = 6005Intermediate Node Start = 7005

You can change other option switches at your own discretion.

6. Add your third party stress software in the Vendor Name section in the stress.dat file.

7. Modify the External Files section in the stress.dat file to reflect the project location.

8. Modify the Service Loading Table in the stress.dat file by removing the search criterialines and to reflect the following for the default condition:

DW + Normal Design Operation ConditionsHOT + Alternate Design Operating ConditionsCOLD + Normal Design Operation ConditionsWIND + Normal Design Operation Conditions

9. Modify the Fitting Nomenclature Table in the stress.dat file by removing the searchcriteria commodity codes.

10. Modify the Hanger Type Table in the stress.dat file to match the values in CL380 in theStandard Note Library.

11. When done modifying the stress.dat file, save it.

40

Generating Neutral Files________________

4. Generating Neutral Files

This section describes how to generate neutral files interactively.

Before Using This Command

You must have access to an existing PDS Piping model containing a completedpipeline.

Operating Sequence

1. Select the PDS icon.

The system displays the Plant Design System form.

2. Select Project Number

Select the PDS project from which the neutral file will be generated.

THEN

Select the Pipe Stress Analysis button.

The system displays the Plant Design - Stress Analysis form.

41


3. Enter 3-D Model Number(s)

Select a Model No field and key in a valid model number. Do not key in the .dgnfilename.

The software checks the model number for validity and either accepts the entry andmoves the cursor to the next Model No field or displays an error message in themessage field.

4. Select the Pipeline Names field adjacent to the Model No field selected in the previousstep and key in a valid pipeline name. See Pipeline Names, page 45 for moreinformation on defining a pipeline name or stress analysis number.

The software accepts the entry and moves to the next Pipeline Names field.

5. Select the Stress Output Node:Path field and key in the location of the neutral file.

The Stress Output location should be in the format:nodename:drive:\users\stress.

A default setting can be set for Stress Output by exporting thefollowing statement in the pds.cmd file.

$ENV{STRESSPATH} =nodename:drive:\users\stress;

6. Select Stress Options File field and key in the location of the options file.

42

Generating Neutral Files________________

The Stress Options File location should be in the format:nodename:drive:\users\stress\defaults.dat.

If any setting of the Stress Options File is changed after the completionof a previous run or before selecting Accept for the next run, thechanged setting is recognized by pressing Enter in the Stress OptionsFile input field.

A default setting can be set for Stress Options File by exporting thefollowing statement in the pds.cmd file.

$ENV{STRESSOPTION} =nodename:drive:\users\stress\defaults.dat;

7. Select the Confirm button to accept the data displayed on the form and begingenerating the neutral file.

The system displays the message:

Creating Neutral File

When the neutral file generation is completed, the system displays a status form.

The status form displays any processing information, warning messages and/or error messagesthat occur during the generating process. Use the scroll bar and buttons to scroll through theinformation displayed on the status screen. Refer to the section Warning and Error Messagesfor detailed descriptions of each warning and error message.

43


4.1 Model Files

The Model Number (model file) is a PDS Piping or Equipment Modeling file to beconsidered for stress analysis. You can specify up to eight files.

Equipment Modeling files must be specified in order to generate nozzles in theneutral file.

The first model number entered is considered to be the primary file and must be a Piping fileand NOT an Equipment Modeling file. Any reference database (RDB) data accessed duringstress analysis is obtained via the primary model (through its type 63 data).

RDB data accessed by the PD_Stress Analysis Interface product and properly attached to theprimary file includes:

Material/Specification Database

Graphic Commodity Library

Physical Commodity Libraries

Piping Job Spec Tables Library

Standard Notes Library

Material Descriptions Library

Specialty and Instrument Descriptions Library

Label Description Library

Miscellaneous data stored in the design file itself.

A Model No is considered invalid if the number is longer than fourteen characters or if thenumber contains a underbar (_) characters or if it does not exist in the project database.

An empty carriage return in any of these fields moves the cursor to the Pipeline Names field.

44

Pipeline Names________________

4.2 Pipeline Names

The Pipeline Names are pipe lines to be extracted into a single neutral file. You can specifyup to eight pipeline names.

The specified lines must be connected in the Piping model files. Because you are specifying anetwork of piping segments, you must not specify multiple disconnected piping sections suchas vessel trim piping. For the lines to be connected, the segments that form these lines mustalso be connected.

You can identify the pipelines you want to extract by line name substring or by StressAnalysis ID. The method you choose depends on the options you set in the options file.

In either method, you identify the piping network to extract by specifying piping segmentattributes. Piping segments usually correspond only to sections of piping and not to an entirepipeline (unless the line is trivial). Enter the pipeline name(s) in the available fields.

An empty carriage return in any of these fields moves the cursor to the Stress Output Nodefield.

4.2.1 Extraction by Line Name Substring

When extracting by line name substring, you should key in any substring of the full PDS linename that uniquely identifies the pipeline you want to include in the neutral file. This methodis the default way of identifying pipelines to extract.

Example 1

If the line name is 6IN-OWS10111-1C0031, you can use the substring OWS10111 to identifythis line. You may not want to use 1C0031 because it is the spec name component of the linename and it would identify more than one line in the model. Likewise, you might not want touse 6IN-OWS10111 because it will only extract sections that have a NPD of 6 inches. Thiscould be a problem if multiple 6 inch sections are connected together by sections that are not 6inches.

Extraction may fail if:

The line name substring you want to extract, exists with lines that are similarly namedin the same models.

The substring you want to extract is also a substring of another line name.

When this type of extraction failure occurs, a multiple disconnected segmentsexist error message might be displayed.

45


Example 2

If the line that you want to extract is 8IN-OWS1011-1C0031 and you use the substringOWS1011, you inadvertently specified that you want to extract 6IN-OWS10111-1C0031because OWS1011 is a substring of OWS10111.

To avoid this conflict:

specify a larger substring of the line name for the line you want to extract.

In the case above, the larger substring may be -OWS1011-. Byincluding the dashes the substring specified is no longer a substring of6IN-OWS10111-1C0031.

specify the line IDs of the lines you want to extract.

4.2.2 Extraction By Stress Analysis ID

The Stress Analysis ID is a segment attribute (table 12, column 52) in the design database thatyou must set prior to running the software. To extract by Stress Analysis ID, you mustestablish the proper option in the Options File.

Assumptions about Line Names

The following assumptions are made concerning line name changes in the 3D model:

Branch components like olets are owned by the header to which they are attached. Foran identified line, all of the olets (or olet-like components) are extracted with that line.It is not necessary to break the segment underneath the olet and change the line name sothat the header owns it.

Branch components like tees (for example, tees, 3-way valves) are also owned by theheader. The header is defined as the part of the line that contains the run of the tee(from connect point 1 to connect point 2). Again, it is not necessary to break thesegment underneath the branch of the component and give it the header line name.

46

Lab 2 - Generate a Neutral File________________

Lab 2 - Generate a Neutral File

1. Modify the PDS.CMD file to reflect the stress path and options file location:

$ENV{STRESSPATH} = nodename:E:\PBS_TRAIN\STRESS\OUTPUT\;

$ENV{STRESSOPTION} =nodename:E:\PBS_TRAIN\STRESS\INPUT\STRESS.DAT;

2. Enter the Pipe Stress Analysis module. For Model No, key in pstress and estress. For PipelineNames, key in 112901. Then select Accept.

3. If any errors occur, fix them and repeat step 2 until there are no more errors.

4. Review the output files you have generated.









13. Review the output files you have generated.

47


48

The Stress Analysis Neutral File________________

5. The Stress Analysis Neutral File

5.1 Neutral File Format

The neutral file produced by the PD_Stress Analysis Interface consists of eight sections ofdata. Each section of the file is composed of one or more records in the neutral file. Eachrecord is composed of several fields. Fields in neutral file records are separated by commas.

Records in each section of the neutral file generally begin with a fixed keyword. When theneutral file is generated from a metric model file, the keywords add the prefix M (for example,NODE becomes MNODE).

Different sections of the file are related to each other through pointers. For example,temperatures and pressures stored at the segment level in a 3D model are generated in the filesection where the record keyword is LOAD.

Data about each component in a network is put in a file section where records begin withPROP. A common text string (the pointer) in each of the record types associates a set oftemperatures and pressures with a given component. These pointers keep the file reasonablycompact.

The data contained in each section of the neutral file is outlined below:

Section 1 Set of comment records (with an exclamation mark in column one) listing all of themodel files and line names used in the extraction. The date and time of the run is alsoincluded.

Section 2 Single record containing fields that identify the run. (Use of this record is not fullysupported at this time.)

Section 3 Several records, each beginning with the keyword LOAD, which contain thetemperatures and pressures of each piping segment in the piping network.

The second field contains a segment ID or pointer that is used to associate a set oftemperatures and pressures with a given component. More than one LOAD record maybe generated for a segment depending on how many temperature/pressure pairs you puton a single record.

Section 4 Records that begin with the keyword LSET. These records specify thetemperature/pressure pair used from each segment when analyzing the line for differentloading conditions (that is, deadweight, cold condition, hot condition and windcondition cases). The PD_Stress Analysis Interface puts values in these records basedupon criteria you specified in the options file. (Refer to the Options File section formore information.)

49


Section 5 Records beginning with keyword CODE. A CODE record is generated for each uniquevalue of the analysis code attribute stored in the piping segment entities. Eachcomponent has a pointer pointing back to one of these CODE records.

Section 6 Set of records for each component in the network. The first record of each set is anoverall component record. It does not begin with a keyword. Instead, the first fieldconsists of the component name obtained from the PDS to Stress Interface SymbolMap.

The second field contains a component ID or pointer that groups this record with therecords that follow for the same component. This first record also contains networkconnectivity information through a list of node numbers corresponding to thecomponent. Node numbering conventions for components are discussed later in thissection.

Following this first record are a series of records each of which begin with the keywordPROP. Each PROP record contains the component ID pointing back to the overallcomponent record. Each of these records also has a form type identifying the datacontained on the PROP record.

Data held in PROP records is of two types:

- component type data. For example a bent pipe PROP record might contain thebend radius and the bend angle.

- connect point data. This data includes size and schedule. It also includes thesegment pointer that associates each connect point with LOAD and LSET records.

Section 7 Records beginning with the keyword LNOD. These records are generated at equipmentnozzles (indicating that the nozzle is an anchor) and when data associated with a pipesupport indicates that the support is acting as a node restraint. When a support acts onlyas a restraint, the component records are not generated for it. LNOD records definewhich directions and/or rotations are restrained at a node.

Section 8 Records beginning with the keyword NODE. These records hold the coordinate of eachnode in the network.

The overall file structure is outlined in general form below:

!! Comments!

LOAD, SEGID1, T1, P1, T2, P2, ...LOAD, SEGID2, T1, P1, T2, P2, ...

.

.

.

LOAD, SEGIDn, T1, P1, T2, P2, ...

LSET, SEGID1, ...LSET, SEGID2, ...

50

The Stress Analysis Neutral File________________

.

.

.

LSET, SEGIDn, ...

CODE, CODEID1, ...CODE, CODEID2, ...

.

.

.

CODE, CODEIDn, ...

NAME1, COMPID1, CODEID1, ... N1, N2PROP, NAME1, COMPID1, FORM1, ...

.

.

.

PROP, NAME1, COMPID1, FORMn, ... , SEGID1PROP, NAME1, COMPID1, FORMm, ... , SEGID1NAME2, COMPID2, CODEID1, ... N3, N4, N5PROP, NAME2, COMPID2, FORM1, ...

.

.

.

PROP, NAME2, COMPID2, FORMn, ... , SEGID1PROP, NAME2, COMPID2, FORMm, ... , SEGID2PROP, NAME2, COMPID2, FORMo, ... , SEGID3

.

.

.

NAMEn, COMPIDn, CODEIDn, ... , Nm, NmPROP, NAMEn, COMPIDn, FORM1, ...

.

.

.

PROP, NAME2, COMPID2, FORMn, ... , SEGIDnPROP, NAME2, COMPID2, FORMm, ... , SEGIDn

LNOD, Nn, ...LNOD, Nm, ...

NODE, N1, x1, y1, z1NODE, N2, x2, y2, z2,

.

.

.

NODE, Nn, xn, yn, zn

Within the form or skeleton outlined above, you can map attributes from the database into theneutral file by modifying the stress analysis options file.

51


5.2 Detailed Record Descriptions

INFOLOADLSETCODELNODNODE

5.2.1 INFO Record

The general INFO record format is:

INFOModel Design File(s)Line name(s)DatePDSSTR versionUNITSVENDORDRAW

where:

INFO is the record keyword

ModelDesignFile(s)

is the name of the model design file

LineName(s)

is the name of the line

Date is the creation date and time of the neutral file

PDSSTRversion

is the PD_STRESS version number

UNITS are the units used in the neutral file

VENDOR is the name of the vendor of the third party stress analysis software

DRAW is the name of the drawing presented in the neutral file

52

Detailed Record Descriptions________________

Sample INFO Record

! Model Design file(s) : lee! Line name(s) : 36310! Date : 24-NOV-1999 14:48:22PDSSTR version 06.04.00.13UNITS, IN, LBVENDOR, TRIFLEX Rel 2.6.8 Aug 97DRAW,36310,36310

5.2.2 LOAD Record

The general LOAD record format is:

LOAD, segid, i, j, Ti, Pi, ... , Tj, Pj

where:

LOAD is the record keyword (MLOAD for metric models)

segid is a pointer used to associate a LOAD record with each component in the pipingnetwork

i is the subscript of the lowest pressure/temperature pair on the record

j is the subscript of the highest pressure/temperature pair on the record. Recordelements i and j define a range of subscripts.

Tn,Pn is a pressure/temperature pair of subscript n

Sample LOAD Record

LOAD, B00031G, 1, 3, 100.00, 100.00, 102.00, 102.00, 103.00, 103.00LOAD, B00031G, 4, 6, 100.00, 100.00, 102.00, 102.00, 106.00, 106.00

5.2.3 LSET Record

The general format of the LSET record is as follows:

LSET, segid, s1, s2, s3, s4

where:

LSET is the record keyword

53


segid is the segment pointer used to associate an LSET record with each component in thepiping network

s1 identifies the pressure/temperature pair used when analyzing under case 1 conditions(for example, deadweight)

s2 identifies the pressure/temperature pair used when analyzing under case 2 conditions(for example, hot)

s3 identifies the pressure/temperature pair used when analyzing under case 3 conditions(for example, cold)

s4 identifies the pressure/temperature pair used when analyzing under case 4 conditions(for example, wind)

In the options file, you can either hard code the numbers that are actually placed in LSETrecords for each segment or you can set them based upon the value of any attribute stored inthe segment.

Sample LSET Record

LSET, B00031G,3,6,5,3

5.2.4 CODE Record

The general format of a code record is:

CODE, codeid, string

where:

CODE is the record keyword

codeid is a label used to associate each component in the piping network with a CODE record

string is a string defining the analysis code name

Sample CODE Record

CODE,CODE20,ASME2,1982,A

54

Detailed Record Descriptions________________

5.2.5 Component Records

Overall ComponentPROP

5.2.5.1 Overall Component Record

The general form of the overall component record is:

name, compid, codeid, data, nodes

where:

name is the component name obtained from the PDS to stress interface symbol map

compid is a label uniquely identifying the component (much the same as the segment IDuniquely identifies a segment)

codeid is the label pointing back to a particular CODE record

data is a list of component attributes defined by you in the options file that apply to thecomponent as a whole and are not specific to the component type. These attributesmay come from either the segment or component entities.

nodes is the node list for the component. The node list defines the node numbers for eachnode of the component. The number of nodes in the node list is a function of thecomponent type. The nodes are ordered in the list so that the first corresponds toconnect point 1, the second to connect point 2 and so on. Refer to the NodeNumbering Conventions section for more information.

Sample Overall Component Record

PI, 5B00031G,6"STDPAAAAAWAAA,,CODE20, 5, 10

5.2.5.2 PROP Record

The general form of a PROP record is:

PROP, name, compid, form, data

where:

PROP is the record keyword (MPROP for metric models)

55


name is the component name and is the same name as appears on the overall componentrecord.

compid is the unique ID of the component which also appears on the overall component record

form is a form number you defined in the options file. The component name together withthe form number uniquely defines the data that follows on the record.

data is a list of attributes you defined

Documents

Stress