Stress Analysis

PDS Stress Analysis Interface (PD_Stress)
Reference Guide
June 1998 DEA503932
SE**006, SE**151, SE**040, SE**041 (06.00.00.**)
This document replaces DEA503920.
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. The information and the software discussed in this document are subject to change without notice and should not be considered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies.
Trademarks
CLIX, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DesignReview, DIALOG, EE Raceway, FrameWorks, IGDS, MicasPlus, ModelDraft, Project Engineer, and SEE are trademarks of Intergraph Corporation. All other brands and product names are trademarks of their respective owners.
Copyright
1996 Intergraph Corporation All Rights Reserved Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 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
Table of Contents iii
Table of Contents
__________________________________________________________________________________________________________________________________________________
iv Table of Contents
Table of Contents v
Table of Contents
__________________________________________________________________________________________________________________________________________________
Preface ......................................................................................................................... Finding Your Way Around ................................................................................... 1. 2. Introduction .......................................................................................................... PDS Environment ................................................................................................. 2.1 PD Shell ........................................................................................................ 2.1.1 2.1.2 3. PD_Shell Form Conventions ............................................................ Batch Processes ................................................................................
ix xiii 1-1 2-1 2-2 2-5 2-8 3-1 3-5 3-6 3-6 3-7 4-1 4-2 4 - 12 4 - 13 4 - 14 4 - 15 4 - 24 4 - 28 5-1 5-2 5-5 5-5 5-5 5-6 5-7 5-7 5-7
Generating Neutral Files ..................................................................................... 3.1 3.2 Model Files ................................................................................................... Pipeline Names ............................................................................................ 3.2.1 3.2.2 Extraction by Line Name Substring ................................................ Extraction By ID ..............................................................................
4.
Interpreting the HITS Report .............................................................................. 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Example HITS Report ................................................................................. Section 1: Basic Input Data and Raw Design File Data ............................ Section 2: Design File Data Sorted by Coordinate ..................................... Section 3: Tracing Data ............................................................................... Section 4: Design File Data Sorted by Topo ............................................... Section 5: Design File Data in STR Order .................................................. Using the HITS Report to Solve Problems .................................................
5.
The Stress Analysis Neutral File ......................................................................... 5.1 5.2 Neutral File Format ..................................................................................... Detailed Record Descriptions ...................................................................... 5.2.1 5.2.2 5.2.3 5.2.4 LOAD Record .................................................................................... LSET Record ..................................................................................... CODE Record .................................................................................... Component Records .......................................................................... 5.2.4.1 5.2.4.2 Overall Component Record ................................................ PROP Record ......................................................................
vi Table of Contents
5.2.5 5.2.6 5.3 5.4 6.
LNOD Record .................................................................................... NODE Record ...................................................................................
5-8 5-9 5 - 10 5 - 12 6-1 6-2 6-3 6-3 6-4 6-4 6-4 6-5 6-5 6-6 6-7 6-7 6 - 10 6 - 11 6 - 11 6 - 12 7-1 7-2 A-3 A-4 A-6 B-3 GL - 3 IN - 3
Node Numbering Conventions .................................................................... Example Neutral File ..................................................................................
The Options File ................................................................................................... 6.1 6.2 Options File Structure ................................................................................. Options File Keywords ................................................................................. 6.2.1 6.2.2 6.2.3 INTERGRAPH OPTIONS BLOCK ................................................. VENDOR NAME .............................................................................. EXTERNAL FILES .......................................................................... 6.2.3.1 6.2.4 6.2.5 6.2.6 6.2.7 6.2.8 6.2.9 6.2.10 6.2.11 6.3 PDS to Stress Symbol Map ................................................
CODE NAME OF CODE PARAMETER DATA TABLE ................ LOADING DATA (LOAD) TABLE .................................................. SERVICE LOADING (LSET) TABLE ............................................. ELEMENT CONNECTIVITY MAP TABLE ................................... ELEMENT PROPERTY / CONNECTIVITY TABLE ..................... END PREPARATION TABLE ......................................................... FITTING NOMENCLATURE TABLE .......................................... HANGER TYPE TABLE ................................................................
Example Options File ..................................................................................
7.
PDS to Stress Analysis Symbol Map ................................................................... 7.1 Example Component Map ........................................................................... Warning & Error Messages ................................................................
Appendix A: A.1 A.2
Warning Messages ............................................................................................. Error Messages .................................................................................................. PDS Design Database Format ............................................................
Appendix B:
Glossary ....................................................................................................................... Index ............................................................................................................................
Preface vii
Preface
__________________________________________________________________________________________________________________________________________________
viii Preface
Preface ix
Preface
__________________________________________________________________________________________________________________________________________________
Document Purpose
This document is a reference 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 three dimensional (3D) piping models. This document is designed as a reference guide; it is organized around the structure of the product rather than presenting a typical work flow. Use this guide when you need to look up a specific stress function.
Document Prerequisites / Audience

This document is intended for designers who have a working knowledge of the standard interactive graphics system. Knowledge of 3D design systems is helpful but not necessary. Also, you should be familiar with a text editor, such as vi or EMACS.
Related Documents/Products
Other related Plant Design documents pertaining to the PDS Stress Analysis Interface product include: PD Project Administrator Reference Guide PD Piping Design Graphics Reference Guide MicroStation 32 software is required to operate PD_STRESS. Information about MicroStation 32 capabilities can be found in the following documents: MicroStation 32 Reference Guide MicroStation 32 Users Guide Intergraph Corporations Relational Interface System (RIS) is required to operate the PDS Stress Analysis Interface product, along with a relational database management system (RDBMS) supported by RIS. Currently, these include Informix , Oracle , and Ingres . Information about RIS capabilities can be found in the following documents: Relational Interface System (RIS) Reference Manual Relational Interface System (RIS) Operator Training Guide
Preface
For more information on related aspects of the PD ISOGEN products, consult the following documents: Project Aministrator Reference Guide Piping Design Graphics Reference Guide
About this Document

This document contains front matter, numbered sections, appendices, a glossary, and an index. Section 1 Section 2 Provides an overview of the product. Describes the PDS workstation environment. This includes information on the PD Shell environment and On-Line Help. Describes how to generate neutral files interactively. This includes information on accessing the product and creating and manipulating product files. Describes how to interpret the HITS reports. This includes interpreting each section and using the report to solve problems. Describes the stress analysis neutral file. This includes record descriptions and node numbering conventions. Describes the defaults file. This includes the default file structure and keywords. Describes the PDS to Stress Analysis Symbool Map. Describes error messages and corrective actions. Displays the PDS Pipeline Design Database Format.
Section 3
Section 4
Section 5
Section 6
Section 7 Appendix A Appendix B
We would like to hear what you think about the reference manual. After you have used this document, please help us improve our products by responding to the questionnaire at the back of the document. If you have more than one response to a question, circle all the responses that apply.
Ordering and Support Information

To order documents: Within the United States, contact your Customer Engineer or Sales Account Representative.
Preface xi
For international locations, contact the Intergraph subsidiary or distributor from whom you purchased your workstation. For technical support of Intergraph hardware and software, contact Intergraph Customer Support: Outside Alabama: 1-800-633-7248 Inside Alabama: (256) 730-4384, 730-4385, 730-4397, 730-4398 International: Contact the Intergraph subsidiary or distributor from whom you purchased your workstation.
Additional Information
The following informational files are delivered with the PD_STRESS software in the /usr/ip32/pdstress directory. File Name README Contents Describes changes and additions to the product since the last version. Lists the names and dates of the files in the current release. For a fixes release, the files which have been modified are appended to the top of the initial file to provide a history of all changes to the product. Includes Comments and Trouble Report numbers which describe what problems have been fixed. Provides special notices to the customer. Lists any exceptions made to the certification. Lists all dependencies and related parts for the product.
product.def
xii Preface
Preface xiii
Finding Your Way Around

Visual Cues
__________________________________________________________________________________________________________________________________________________
This document contains many visual cues to help you better understand the meaning of certain words or phrases. The use of different fonts for different types of information allows you to scan the document for key concepts or commands. Symbols help abbreviate and identify commonly used words, phrases, or groups of related information.
Typefaces
Italic Indicates a system response, which is an explanation of what the software is doing. For example, The text is placed in the viewing plane. Bold Indicates a command name, parameter name, or dialog box title. Command paths 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 by the user. For example, Select first segment of alignment Normal Typewriter Indicates what you should literally type in. For example, Key in original.dat to load the ASCII file. Bold Typewriter Indicates an actual file or directory name. For example, The ASCII report is stored in the layout.rpt file.
xiv Preface
Symbols
This document uses the following symbols to represent mouse buttons and to identify special information: <C> <D> <R> <T> Command button Data button Reset/reject button Tentative 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 is doing 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 the exercise.
Keyboard Conventions
The following list outlines the abbreviations this document uses for keyboard keys and describes how to use them in combination. You can make some menu selections through the use of keyboard accelerators (also known as mnemonics), which map menu selections to key combinations. ALT CTRL DEL ENTER ESC CTRL+z ESC,k Alternate key Control key Delete key Return key Escape key To hold down the Control key and press Z. To press the Escape key, then K.
Preface xv
Terminology
Choose To use a mouse or key combination to pick an item that begins an action. For example, Choose Apply to initiate the curve calculation. Select To mark an item by highlighting it with key combinations or by picking it with your cursor. Selecting does not initiate an action. After selecting an item, you choose the action you want to affect the item. For example, Select the file original.dat from the list box, then choose Delete to remove it from the directory. In addition, you would select items to define parameters, such as selecting toggle buttons. This also applies to selecting graphic elements 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 design file. If you are using the CLIX operating system, you tentative-select by double-clicking with a mouse or pressing <T> on a hand-held cursor. If you are using the Windows NT operating system, you tentative-select by pressing a left-button, right-button chord. To select and execute a command by clicking the mouse or hand-held cursor button twice in rapid succession. This term implies that you are clicking the data button (<D>) as part of a menu or dialog box action. For example, Double-click on the file original.dat to load it into the new surface. Drag To press and hold the data button (<D>) while moving the mouse or hand-held cursor. To key a character string into a text box.
Double-click
Type
xvi Preface
Key in
To type in data and press ENTER to enter the data and execute the default action. In a dialog box, pressing TAB after typing in data will enter the data and move the cursor to the next field.
Introduction 1 - 1
1. Introduction
__________________________________________________________________________________________________________________________________________________
The PD_Stress Analysis Interface product generates neutral files from threedimensional (3D) piping models created by PDS modeling packages as input for third party stress analysis packages. The neutral file can be run on your own in-house pipe stress software or on any other commercially available package capable of processing the Intergraph neutral file. Because of its flexibility, you can change the contents of the neutral file and customize it for your specific use.
The Stress Analysis Interface product performs its function via: strinp (input collection)
1-2
PDS Stress Analysis Interface Reference Guide - June 1998
PDSSTR (neutral file generation) The strinp file collects user input and creates the ASCII file STRDEF.DAT which contains the defaults file NEUDFLTS. This defaults file contains switches, options and tables allowing you to control the information the Stress Analysis Interface enters into the neutral file. (Refer to the Defaults File section for more information on the contents of the defaults.) The strinp file then displays the Stress Analysis Interface form allowing you to enter data to the ASCII file pdsstr.dat. From the pdsstr.dat file, the Stress Analysis Interface reads the involved piping and equipment models, the pipeline names or stress ID and the defaults file. The pdsstr file then reads the 3D piping model and generates the stress analysis neutral files.
PDS Environment 2 - 1
2. PDS Environment
__________________________________________________________________________________________________________________________________________________
The PDS 3D software supports a variety of applications. All the supported applications use a common interface that is controlled by the PD Shell program. This ensures consistency across applications and minimizes the amount of time required to learn the product. The PDS 3D modules provide a simple user interface through extensive use of forms. The modules also provide an on-line Help capability for easy access to information while working in the product. The PDS 3D software uses available nucleus tools such as MicroStation and FORMS. It supports standard software such as NFS, NQS, and RIS required to set up data across a network. This design facilitates the use of non-PDS tools such as relational databases and third party software. The PD_Shell Environment and all batch jobs in the PDS 3D products interface to Intergraphs Network Licensing System.
2-2
2.1 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 Double-clicking the PD_Shell icon on Windows NT workstations. Keying in control.sh on CLIX workstations. 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.
This form identifies the active project(s) and provides access to all the PDS functions. Options Schematics Environment Provides access to the PDS 2D modules that are used to create and modify piping and instrumentation diagrams, process flow diagrams, and instrumentation database records.
Equipment Modeling Provides access to the Equipment Modeling module, which provides an interactive graphics environment that is used to create and revise equipment model graphics and database information. FrameWorks Environment Provides access to the FrameWorks module, which provides an environment that is used to create and revise structural models, create and revise structural drawings, and propagate structural models. Piping Designer Activates an interactive command environment that is used to create piping and in-line instrumentation in the model; revise existing model graphics and database information; and verify the integrity of the data in the model. Electrical Raceway Environment Provides access to the Electrical Raceway module, which provides an interactive environment that is used to create and revise raceway models and access raceway utilities. Piping Design Data Manager Provides access to a set of options that are used to verify the integrity of the graphic and database information that is associated with a model. Piping Model Builder Enables you to create piping graphics from a nongraphics environment. This module is used with PD_Design to create an accurate 3D model of the piping network. Pipe 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 DesignReview and to review data from a DesignReview 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.
2-4
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. Other Fields User ID Used for access control. This field also sets the Review User ID for use in the Interference Manager module. If access control has been defined, you must key in a valid user ID as defined by your system manager to gain access to the projects. 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 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.
2.1.1 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 workstations 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. Selecting Options 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.
2-6
The Shell button exits the active form and returns control to the base manager that is associated with the active form. For most forms this returns to the Plant Design System Environment form. The Top button exits the active form and returns control to the top form of the active branch. The Cancel button cancels or exits from the active form. Control returns to the immediately preceding form in the hierarchy. The Accept button accepts a selection or operation. Depending on the active form or option, the active form remains active so that you can repeat a similar operation or control returns to the preceding form. The Restart button clears any key-in fields on the form that have values you can modify. Scrolling List Some screen menus have a scrolling list of projects or applications. You need to scroll a list only if more options are available than can be displayed in the window. To scroll a list, select the arrow buttons on the side of the list. The list scrolls up or down depending on which arrow you select. The scrolling list has an arrow pointing up and an arrow pointing down. These arrows scroll lists line by line. There is a button that slides between these two arrows to indicate your position on the list. To page through the list, select the space above or below the sliding button. The list pages up or down accordingly. You can also select the slider and, while pressing <D>, slide the button up or down the bar. The items scroll through the window as you move the button. The size and position of the button on the scroll bar is an indication of the number of lines and the relative position within the list. All commands that display a list of design areas or models order the list alphanumerically by the design area number or model number in ascending order. In some forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button.
Key-in Fields Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark gray. You can select a key-in field and key in a new value. A bar cursor appears in the active key-in field. Key in your input, and press <Return>. To change a field, reselect the field and key in the new information. Key-in fields have a maximum number of characters depending on the item that is being defined. If you select a key-in field for a code-listed attribute, the system activates a form that lists the code list values for the selected field. MicroStation requires lowercase characters for the file specification and path name of all 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. 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.
2-8
Standard Window Icons When using this software in the CLIX environment, you can press <D> along the edge of a form or any area not occupied by a button, key-in field, or other gadget, to display a box of icons. You can manipulate form windows just like any other workstation window. The following list defines the available window icons. Collapse/Restore Repaint Pop-to-bottom Modify/Resize Pop-to-top Restore Size
2.1.2 Batch Processes __________________________________________________________________________________________________________________________________________________

When you install the PDS 3D applications, the system creates the necessary batch queues for that application. Refer to Loading PDS Products in the Project Administrator (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 while the system processes a request. Many of the batch processes can be delayed for submission at a specified time. When you submit a batch process the system sends an electronic mail message to the mail path of the default login reporting the jobs completion status. The mail message also includes any error log information. The setup of this functionality is optional on Windows NT.
Generating Neutral Files 3 - 1
3. 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 completed pipeline.
Operating Sequence
1. At the system prompt, enter the PD Shell environment using either: $ control.sh
Select the file, pds.cmd.
The system displays the Plant Design System form.
3-2
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.
3.
Enter 3-D Model Number(s) Select a Model No field and key in a valid model number. Do not key in the .dgn filename. See Model Files, page 3 - 5 for more information on defining a model number. The software checks the model number for validity and either accepts the entry and moves the cursor to the next Model No field or displays an error message in the message field.
4.
Select the Pipeline Names field adjacent to the Model No field selected in the previous step and key in a valid pipeline name. See Pipeline Names, page 3 - 6 for more information on defining a pipeline name. 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:/usr/stress. The Stress Output location should be in the format: nodename:drive:\users\stress.
A default setting can be set for Stress Output by exporting the following statement. For CLIX, in the control.sh file use the format: export STRESSPATH=nodename:/usr/stress For NT, in the pds.cmd file use the format: $ENV{STRESSPATH} = nodename:drive:\users\stress; 6. Select Stress Defaults File field and key in the location of the defaults file. The Stress Defaults File location should be in the format: nodename:/usr/stress/defaults.dat.
The Stress Defaults File location should be in the format: nodename:drive:\users\stress\defaults.dat. A default setting can be set for Stress Defaults File by exporting the following statement. For CLIX, in the control.sh file use the format: export STRESSOPTION=nodename:/usr/stress/defaults.dat For NT, in the pds.cmd file use the format: $ENV{STRESSOPTION} = nodename:drive:\users\stress\defaults.dat; 7. Select the Confirm button to accept the data displayed on the form and begin generating the neutral file. The system displays the message: Creating Neutral File When the neutral file generation is completed, the system displays a status form.
3-4
The status form displays any processing information, warning messages and/or error messages that occur during the generating process. Use the scroll bar and buttons to scroll through the information displayed on the status screen. Refer to the section Warning and Error Messages for detailed descriptions of each warning and error message.
3.1 Model Files __________________________________________________________________________________________________________________________________________________

The Model Number (model file) is a PDS Piping, Equipment Modeling, or Pipe file to be considered for stress analysis. You can specify up to eight files. Equipment Modeling files must be specified in order to generate nozzles in the neutral file. The first model number entered is considered to be the primary file and must be a Piping file and NOT an Equipment Modeling or Pipe file. Any reference database (RDB) data accessed during stress 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 the primary 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 the number 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.
3-6
3.2 Pipeline Names __________________________________________________________________________________________________________________________________________________

The Pipeline Names are pipe lines to be extracted into a single neutral file. You can specify up to eight pipeline names. The specified lines must be connected in the Piping model files. Because you are specifying a network of piping segments, you must not specify multiple disconnected piping sections such as vessel trim piping. For the lines to be connected, the segments that form these lines must also be connected. You can identify the pipelines you want to extract by line name substring or by Stress Analysis ID. The method you choose depends on the options you set in the defaults file. (Refer to the Defaults File section for more information). In either method, you identify the piping network to extract by specifying piping segment attributes. Piping segments usually correspond only to sections of piping and not to an entire pipeline (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 Node field.
3.2.1 Extraction by Line Name Substring __________________________________________________________________________________________________________________________________________________

When extracting by line namesubstring, you should key in any substring of the full PDS line name that uniquely identifies the pipeline you want to include in the neutral file. This method is 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 identify this line. You may not want to use 1C0031 because it is the spec name component of the line name and it would identify more than one line in the model. Likewise, you might not want to use 6IN-OWS10111 because it will only extract sections that have a NPD of 6 inches. This could be a problem if multiple 6 inch sections are connected together by sections that are not 6 inches. Extraction may fail if: The line name substring you want to extract, exists with lines that are similarly named in 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 segments exist error message might be displayed.
Example 2
If the line that you want to extract is 8IN-OWS1011-1C0031 and you use the substring OWS1011, you inadvertently specified that you want to extract 6IN-OWS10111-1C0031 because 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-. By including the dashes the substring specified is no longer a substring of 6IN-OWS10111-1C0031. specify the line IDs of the lines you want to extract.
3.2.2 Extraction By ID __________________________________________________________________________________________________________________________________________________

The ID is a segment attribute (table 12, column 52) that you must set prior to running the software. To extract by ID, you must establish the proper option in the Defaults File (Refer to the Defaults File section for more information).
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. For an 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 so that the header owns it. Branch components like tees (for example, tees, 3-way valves) are also owned by the header. 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 the segment underneath the branch of the component and give it the header line name.
3-8
Interpreting the HITS Report 4 - 1
4. Interpreting the HITS Report
__________________________________________________________________________________________________________________________________________________
The HITS report is a diagnostic tool generated by the Intergraph interface to PDSTRESS. You can use this report to analyze the data collected from the 3-D piping model when a problem extracting an isometric occurs. This report can help you determine whether or not the problem exists in your model, in the PDSTRESS interface or in PDSTRESS itself. The HITS report filename is formed from the output isometric design filename. Isometric design filename is concatenated with the file extension .h. For example, if the isometric design filename is OWS1101.ISO then the HITS report filename will be OWS1101.h. The report is created in the default directory at the time the iso is created. One of the options in the PDSTRESS interface defaults file allows you to generate a HITS report only and not an intermediate data file (IDF). You may not always want to generate an IDF with a HITS report. The run time to generate both an IDF and a HITS report is significantly longer than the run time to generate a HITS report only.
4-2
4.1 Example HITS Report __________________________________________________________________________________________________________________________________________________

The following section discusses an example of a HITS report. The HITS report is composed of 5 basic sections. Refer to the following figure for an illustration of each of the five sections. The example HITS report in this section was generated using the following line.
Sheet One of Two
Sheet Two of Two

Date: 30-MAR-1994 02:03:53 Project Database: pd_stdeng_o43 Model Files: skiso3 skiso1 38eqp01 40eqp01
Raw design file data Name COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP Occ 16 16 16 14 14 14 14 27 27 29 29 29 29 32 32 32 33 33 33 34 34 34 35 35 35 cp # 0 1 2 0 1 2 3 0 1 0 1 2 3 0 1 2 0 1 2 0 1 2 0 1 2 X 1369.58 1369.58 1369.58 1363.08 1363.08 1363.08 1362.40 1362.35 1362.40 1369.58 1370.05 1369.11 1369.58 1373.58 1373.58 1372.83 1373.58 1372.83 1373.58 1364.58 1364.58 1365.33 1364.58 1364.58 1364.58 Y 421.10 420.95 421.24 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 423.20 422.45 429.80 429.80 429.05 429.80 429.80 429.80 429.80 429.80 429.80 Z 13.46 13.46 13.46 15.18 14.42 15.94 15.18 15.18 15.18 18.46 18.46 18.46 17.99 18.46 18.46 18.46 18.46 18.46 18.46 18.46 19.21 18.46 19.35 19.51 19.21 Node Direct Section 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 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Flags 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 Topo 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 Seq Branch Sg_occ 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9 9 9 5 5 8 7 7 7 16 16 17 14 16 16 16 16 16 16 16 16 16 16 16 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
4-4
PIPE PIPE PIPE PIPE PIPE PIPE COMP COMP COMP PIPE PIPE COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP PIPE PIPE COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP SUPP SUPP COMP COMP COMP COMP COMP COMP SUPP SUPP COMP
5 5 6 6 7 7 30 30 30 3 3 17 17 17 17 6 6 6 15 15 15 31 31 31 4 4 7 7 7 7 8 8 8 9 9 9 10 10 10 11 11 26 26 26 22 22 22 23 23 23 24 24 24 24 4 4 12 12 12 13 13 13 3 3 25
1 2 1 2 1 2 0 1 2 1 2 0 1 2 3T 0 1 2 0 1 2 0 1 2 1 2 0 1 2 3T 0 1 2 0 1 2 0 1 2 0 1 0 1 2 0 1 2 0 1 2 0 1 2 3 1 2 0 1 2 0 1 2 1 2 0
1370.05 1372.83 1373.58 1373.58 1372.83 1365.33 1363.08 1363.08 1363.83 1369.11 1363.83 1369.58 1369.58 1369.58 1369.58 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1364.58 1364.58 1364.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1368.90 1369.58 1369.58 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1369.58
422.45 422.45 423.20 429.05 429.80 429.80 422.45 422.45 422.45 422.45 422.45 421.47 421.70 421.24 421.47 421.10 420.95 421.24 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 421.47 421.70 421.24 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 429.80 429.80 429.80 422.45 421.70 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 421.70 422.45 422.45 422.45 422.45 422.45 422.45 422.45
18.46 18.46 18.46 18.46 18.46 18.46 18.46 17.71 18.46 18.46 18.46 13.41 13.37 13.46 13.18 13.46 13.46 13.46 16.38 15.94 16.82 16.97 16.82 17.12 17.71 17.12 13.41 13.37 13.46 13.18 13.06 13.18 12.93 12.82 12.93 12.71 12.58 12.71 12.46 12.43 12.46 19.54 19.58 19.51 13.37 13.37 14.12 14.27 14.42 14.12 15.18 14.42 15.94 15.18 13.37 12.30 13.37 13.37 14.12 14.27 14.42 14.12 13.37 12.30 16.38
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 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 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 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 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 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 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 0 0 0 0 0 0
5 5 5 5 5 5 3 3 3 5 5 3 3 3 3 3 3 3 3 3 3 3 3 3 5 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 8 8 3 3 3 3 3 3 8 8 3
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 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 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 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 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 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 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 0 0 0 0 0 0
16 16 16 16 16 16 8 8 17 17 17 11 11 10 12 3 3 3 8 8 8 8 8 8 8 8 5 5 4 6 6 6 6 6 6 6 6 6 6 6 6 15 15 15 11 11 11 11 11 11 11 11 14 13 11 11 5 5 5 5 5 5 5 5 14
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90
COMP COMP COMP COMP COMP PIPE PIPE COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP
25 25 305 305 305 103 103 18 18 18 19 19 19 20 20 20 21 21 28 28
1 2 0 1 2 1 2 0 1 2 0 1 2 0 1 2 0 1 0 1
1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1368.85 1368.90
422.45 422.45 422.45 422.45 422.45 422.45 422.45 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 422.45 422.45
15.94 16.82 16.97 16.82 17.12 17.12 17.99 13.06 13.18 12.93 12.82 12.93 12.71 12.58 12.71 12.46 12.43 12.46 15.18 15.18
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 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 0 0 0 0 0 0
3 3 3 3 3 5 5 3 3 3 3 3 3 3 3 3 3 3 3 3
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 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 0 0 0 0 0 0
14 14 14 14 14 14 14 12 12 12 12 12 12 12 12 12 12 12 13 13
91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110
Design file data sorted by coordinate Name COMP COMP COMP NOZ NOZ COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP SUPP COMP SUPP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP PIPE Occ 27 27 14 1 1 6 6 6 7 11 11 10 10 9 10 9 9 8 8 7 8 7 12 7 3 12 3 13 12 13 13 14 14 15 14 15 31 15 31 31 4 cp # 0 1 3 1 2 1 0 2 2 0 1 2 0 2 1 0 1 2 0 3T 1 0 1 1 2 0 1 2 2 0 1 1 0 1 2 0 1 2 0 2 2 X 1362.35 1362.40 1362.40 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 Y 422.45 422.45 422.45 420.70 420.95 420.95 421.10 421.24 421.24 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.70 421.70 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 Z 15.18 15.18 15.18 13.46 13.46 13.46 13.46 13.46 13.46 12.43 12.46 12.46 12.58 12.71 12.71 12.82 12.93 12.93 13.06 13.18 13.18 13.41 13.37 13.37 12.30 13.37 13.37 14.12 14.12 14.27 14.42 14.42 15.18 15.94 15.94 16.38 16.82 16.82 16.97 17.12 17.12 Node Direct Section -2 1 1 -1 40 40 0 2 2 -2 3 3 0 4 4 0 5 5 0 6 6 0 7 7 -3 0 0 9 9 0 10 10 0 11 11 0 12 12 0 13 13 3 3 3 11 11 11 11 11 12 13 13 13 13 13 13 13 13 13 13 13 13 13 15 12 2 15 2 2 2 2 2 2 3 2 2 2 2 2 2 2 2 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Flags 3 3 3 22 22 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 8 3 8 3 3 3 3 3 3 3 3 3 3 3 3 3 5 Topo 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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Seq Branch Sg_occ 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 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 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 0 7 7 7 3 3 3 3 3 4 6 6 6 6 6 6 6 6 6 6 6 6 5 5 5 5 5 5 5 5 5 5 5 5 8 8 8 8 8 8 8 8 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
4-6
COMP PIPE COMP PIPE COMP COMP COMP COMP COMP COMP COMP COMP COMP NOZ NOZ COMP PIPE COMP COMP COMP PIPE COMP NOZ NOZ COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP SUPP COMP SUPP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP PIPE COMP PIPE COMP COMP COMP PIPE
30 4 30 3 30 34 35 34 35 35 26 26 26 7 7 34 7 28 24 28 3 29 3 3 16 16 16 17 21 21 20 20 20 19 19 18 19 18 17 18 17 22 17 4 22 4 22 23 23 23 24 24 24 25 25 25 305 305 103 305 103 29 29 29 5
1 1 0 2 2 0 2 1 0 1 2 0 1 2 1 2 2 0 3 1 1 2 1 2 1 0 2 2 0 1 2 0 1 2 0 2 1 0 3T 1 0 1 1 2 0 1 2 2 0 1 1 0 2 1 0 2 1 0 1 2 2 3 0 1 1
1363.08 1363.08 1363.08 1363.83 1363.83 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58 1365.33 1365.33 1368.85 1368.90 1368.90 1369.11 1369.11 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1370.05 1370.05
422.45 422.45 422.45 422.45 422.45 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 422.45 422.45 422.45 422.45 422.45 420.70 420.95 420.95 421.10 421.24 421.24 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.70 421.70 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45
17.71 17.71 18.46 18.46 18.46 18.46 19.21 19.21 19.35 19.51 19.51 19.54 19.58 19.58 20.58 18.46 18.46 15.18 15.18 15.18 18.46 18.46 13.46 13.46 13.46 13.46 13.46 13.46 12.43 12.46 12.46 12.58 12.71 12.71 12.82 12.93 12.93 13.06 13.18 13.18 13.41 13.37 13.37 12.30 13.37 13.37 14.12 14.12 14.27 14.42 14.42 15.18 15.94 15.94 16.38 16.82 16.82 16.97 17.12 17.12 17.99 17.99 18.46 18.46 18.46
14 14 0 15 15 0 16 16 0 17 17 0 41 41 -1 18 18 -2 19 19 20 20 -1 39 39 0 21 21 -2 22 22 0 23 23 0 24 24 0 25 25 0 26 26 -3 0 0 28 28 0 29 29 0 30 30 0 31 31 0 32 32 33 33 0 34 34
2 2 4 4 4 8 8 8 8 8 8 8 8 8 8 7 7 3 3 3 4 4 1 1 1 1 1 9 10 10 10 10 10 10 10 10 10 10 10 10 10 14 9 5 14 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 4 4
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 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 0 0 0 0 0 0 0 0 0 0 0
3 5 3 5 3 3 3 3 3 3 3 3 3 22 22 3 5 3 3 3 5 3 22 22 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 8 3 8 3 3 3 3 3 3 3 3 3 3 3 3 5 3 5 3 3 3 5
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 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 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 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 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 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 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 0 0 0 0 0 0
8 8 8 17 17 16 16 16 16 16 15 15 15 15 15 16 16 13 13 13 17 17 9 9 9 9 9 10 12 12 12 12 12 12 12 12 12 12 12 12 11 11 11 11 11 11 11 11 11 11 11 11 14 14 14 14 14 14 14 14 14 14 16 16 16
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106
PIPE COMP PIPE COMP COMP COMP PIPE COMP PIPE COMP
5 32 7 33 32 32 6 33 6 33
2 2 1 1 0 1 1 2 2 0
1372.83 1372.83 1372.83 1372.83 1373.58 1373.58 1373.58 1373.58 1373.58 1373.58
422.45 422.45 429.80 429.80 422.45 423.20 423.20 429.05 429.05 429.80
18.46 18.46 18.46 18.46 18.46 18.46 18.46 18.46 18.46 18.46
35 35 36 36 0 37 37 38 38 0
4 4 7 7 6 6 6 6 6 7
0 0 0 0 0 0 0 0 0 0
5 3 5 3 3 3 5 3 5 3
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 0 0 0
16 16 16 16 16 16 16 16 16 16
107 108 109 110 111 112 113 114 115 116
Tracing data Action 5 Next 5 Next 5 Next 5 Next 6 Push 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 6 Push 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 6 Push 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 7 Pull 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next Occ 3 16 16 17 17 17 22 22 23 23 24 24 24 25 25 305 305 103 103 29 29 29 5 5 32 32 6 6 33 33 7 7 34 34 35 35 26 26 7 7 29 29 3 3 30 30 4 4 31 31 15 Cp 2 1 2 2 3 1 1 2 2 1 1 3 2 1 2 1 2 1 2 3 2 1 1 2 2 1 1 2 2 1 1 2 2 1 2 1 2 1 2 1 2 2 1 2 2 1 1 2 2 1 2 Name NOZ COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP PIPE PIPE COMP COMP COMP PIPE PIPE COMP COMP PIPE PIPE COMP COMP PIPE PIPE COMP COMP COMP COMP COMP COMP NOZ NOZ COMP COMP PIPE PIPE COMP COMP PIPE PIPE COMP COMP COMP Node 39 39 21 21 25 26 26 28 28 29 29 19 30 30 31 31 32 32 33 33 20 34 34 35 35 37 37 38 38 36 36 18 18 16 16 17 17 41 41 -1 20 20 20 15 15 14 14 13 13 12 12 Ref Design 112 2 3 39 40 38 71 72 75 74 77 79 78 91 92 94 95 96 97 13 12 11 26 27 16 15 28 29 19 18 30 31 22 21 25 24 69 68 116 115 12 12 35 36 34 33 50 51 49 48 46 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 ++++ ++++ ++++ 1 1 1 1 0 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 0 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 1 2 3 4 0 5 6 7 8 9 10 0 11 12 13 14 15 16 17 18 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
4-8
5 Next 5 Next 6 Push 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 6 Push 5 Next 5 Next 5 Next 5 Next 5 Next 7 Pull 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 7 Pull 5 Next 5 Next 5 Next 7 Pull 5 Next 5 Next 5 Next 7 Pull 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next 5 Next -1 34 15 6 0
15 14 14 14 13 13 12 12 7 7 7 6 6 1 1 7 7 8 8 9 9 10 10 11 11 14 14 27 27 24 24 28 28 17 17 18 18 19 19 20 20 21 21 39 35 14 5
1 2 3 1 1 2 2 1 1 3 2 2 1 2 1 3 3 1 2 1 2 1 2 1 0 3 3 1 0 3 3 1 0 3 3 1 2 1 2 1 2 1 0 21 37 13 4
COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP NOZ NOZ COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP 26 38 12 3
11 11 1 10 10 9 9 7 7 6 2 2 40 40 -1 6 6 6 5 5 4 4 3 3 -2 1 1 1 -2 19 19 19 -2 25 25 25 24 24 23 23 22 22 -2
45 6 7 5 86 87 84 83 53 55 54 43 42 114 113 55 55 57 58 60 61 63 64 66 65 7 7 9 8 79 79 110 109 40 40 99 100 102 103 105 106 108 107 28 36 11 1 29 18 10 19
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 30 16 9 25 31 17 7 24 0 0 0 0 ++++ ++++
2 2 0 2 2 2 2 2 2 0 2 2 2 2 2
-11 -12 0 -13 -14 -15 -16 -17 -18 0 -19 -20 -21 -22 -23 0
3 3 3 3 3 3 3 3 3 0 4 4 4 0 5 5 5 0 6 6 6 6 6 6 6 6 6 32 41 2 23
1 2 3 4 5 6 7 8 9
1 2 3
1 2 3
1 2 3 4 5 6 7 8 9 33 20 40 22
# Sections: 1
Design file data sorted by topo Name COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP Occ 16 9 30 14 10 305 32 17 26 29 18 22 cp # 0 0 0 0 0 0 0 0 0 0 0 0 X 1369.58 1363.08 1363.08 1363.08 1363.08 1369.58 1373.58 1369.58 1364.58 1369.58 1369.58 1369.58 Y 421.10 421.47 422.45 422.45 421.47 422.45 422.45 421.47 429.80 422.45 421.47 422.45 Z 13.46 12.82 18.46 15.18 12.58 16.97 18.46 13.41 19.54 18.46 13.06 13.37 Node Direct Section 0 0 0 0 0 0 0 0 0 0 0 0 1 13 4 3 13 5 6 10 8 5 10 14 0 0 0 0 0 0 0 0 0 0 0 0 Flags 3 3 3 3 3 3 3 3 3 3 3 3 Topo 0 0 0 0 0 0 0 0 0 0 0 0 Seq Branch Sg_occ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9 6 8 5 6 14 16 11 15 16 12 11 1 2 3 4 5 6 7 8 9 10 11 12
COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP SUPP SUPP SUPP SUPP
13 8 23 15 33 24 31 34 12 19 35 6 25 20 7 4 3 3 4
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 2 2
1363.08 1363.08 1369.58 1363.08 1373.58 1369.58 1363.08 1364.58 1363.08 1369.58 1364.58 1363.08 1369.58 1369.58 1363.08 1369.58 1363.08 1363.08 1369.58
422.45 421.47 422.45 422.45 429.80 422.45 422.45 429.80 422.45 421.47 429.80 421.10 422.45 421.47 421.47 422.45 422.45 422.45 422.45
14.27 13.06 14.27 16.38 18.46 15.18 16.97 18.46 13.37 12.82 19.35 13.46 16.38 12.58 13.41 13.37 13.37 12.30 12.30
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -3 -3
2 13 5 2 7 5 2 8 15 10 8 11 5 10 13 5 2 2 5
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 8 8 8 8
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 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 0 0 0
5 6 11 8 16 11 8 16 5 12 16 3 14 12 5 11 5 5 11
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
NOZ NOZ COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP PIPE PIPE COMP
3 3 16 16 17 17 22 22 23 23 24 24 25 25 305 305 103 103 29
1 2 1 2 2 1 1 2 2 1 1 2 1 2 1 2 1 2 3
1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58
420.70 420.95 420.95 421.24 421.24 421.70 421.70 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45
13.46 13.46 13.46 13.46 13.46 13.37 13.37 14.12 14.12 14.42 14.42 15.94 15.94 16.82 16.82 17.12 17.12 17.99 17.99
-1 39 39 21 21 26 26 28 28 29 29 30 30 31 31 32 32 33 33
1 1 1 1 9 9 14 5 5 5 5 5 5 5 5 5 5 5 5
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
22 22 3 3 3 3 3 3 3 3 3 3 3 3 3 3 5 5 3
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
0 0 0 0 108 108 0 0 0 0 105 105 0 0 0 0 0 0 -73
9 9 9 9 10 11 11 11 11 11 11 14 14 14 14 14 14 14 14
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
NOZ NOZ COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP COMP PIPE PIPE COMP COMP PIPE PIPE COMP COMP PIPE
1 1 6 6 7 7 12 12 13 13 14 14 15 15 31 31 4 4 30 30 3 3 29 29 5
1 2 1 2 2 1 1 2 2 1 1 2 1 2 1 2 2 1 1 2 2 1 2 1 1
1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.83 1363.83 1369.11 1369.11 1370.05 1370.05
420.70 420.95 420.95 421.24 421.24 421.70 421.70 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45 422.45
13.46 13.46 13.46 13.46 13.46 13.37 13.37 14.12 14.12 14.42 14.42 15.94 15.94 16.82 16.82 17.12 17.12 17.71 17.71 18.46 18.46 18.46 18.46 18.46 18.46
-1 40 40 2 2 7 7 9 9 10 10 11 11 12 12 13 13 14 14 15 15 20 20 34 34
11 11 11 11 12 12 15 2 2 2 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
22 22 3 3 3 3 3 3 3 3 3 3 3 3 3 3 5 5 3 3 5 5 3 3 5
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
-23 -22 -21 -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 1 2
0 0 0 0 93 93 0 0 0 0 102 102 0 0 0 0 0 0 0 0 0 0 50 50 0
3 3 3 3 4 5 5 5 5 5 5 8 8 8 8 8 8 8 8 17 17 17 17 16 16
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
4 - 10
PIPE COMP COMP PIPE PIPE COMP COMP PIPE PIPE COMP COMP COMP COMP COMP COMP NOZ NOZ
5 32 32 6 6 33 33 7 7 34 34 35 35 26 26 7 7
2 2 1 1 2 2 1 1 2 2 1 2 1 2 1 2 1
1372.83 1372.83 1373.58 1373.58 1373.58 1373.58 1372.83 1372.83 1365.33 1365.33 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58 1364.58
422.45 422.45 423.20 423.20 429.05 429.05 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80 429.80
18.46 18.46 18.46 18.46 18.46 18.46 18.46 18.46 18.46 18.46 19.21 19.21 19.51 19.51 19.58 19.58 20.58
35 35 37 37 38 38 36 36 18 18 16 16 17 17 41 41 -1
4 4 6 6 6 6 7 7 7 7 8 8 8 8 8 8 8
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
5 3 3 5 5 3 3 5 5 3 3 3 3 3 3 22 22
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
16 16 16 16 16 16 16 16 16 16 16 16 16 15 15 15 15
76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92
COMP COMP COMP COMP COMP COMP COMP COMP COMP
7 8 8 9 9 10 10 11 11
3T 1 2 1 2 1 2 1 0
1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08
421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47
13.18 13.18 12.93 12.93 12.71 12.71 12.46 12.46 12.43
6 6 5 5 4 4 3 3 -2
13 13 13 13 13 13 13 13 13
1 1 1 1 1 1 1 1 1
3 3 3 3 3 3 3 3 3
3 3 3 3 3 3 3 3 3
1 2 3 4 5 6 7 8 9
-55 0 0 0 0 0 0 0 0
6 6 6 6 6 6 6 6 6
93 94 95 96 97 98 99 100 101
COMP COMP COMP
14 27 27
3 1 0
1362.40 1362.40 1362.35
422.45 422.45 422.45
15.18 15.18 15.18
1 1 -2
3 3 3
1 1 1
3 3 3
4 4 4
1 2 3
-61 0 0
7 7 7
102 103 104
COMP COMP COMP
24 28 28
3 1 0
1368.90 1368.90 1368.85
422.45 422.45 422.45
15.18 15.18 15.18
19 19 -2
3 3 3
1 1 1
3 3 3
5 5 5
1 2 3
-42 0 0
13 13 13
105 106 107
COMP COMP COMP COMP COMP COMP COMP COMP COMP
17 18 18 19 19 20 20 21 21
3T 1 2 1 2 1 2 1 0
1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58 1369.58
421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47
13.18 13.18 12.93 12.93 12.71 12.71 12.46 12.46 12.43
25 25 24 24 23 23 22 22 -2
10 10 10 10 10 10 10 10 10
1 1 1 1 1 1 1 1 1
3 3 3 3 3 3 3 3 3
6 6 6 6 6 6 6 6 6
1 2 3 4 5 6 7 8 9
-36 0 0 0 0 0 0 0 0
12 12 12 12 12 12 12 12 12
108 109 110 111 112 113 114 115 116
Design file data in IDF order Name NOZ BLSP FWN E90L E90L PIPE E90L E90L PIPE E90L E90L PIPE T T PIPE FWN X 33274000 33274000 33274000 33274000 33274000 33292288 33475168 33493456 33493456 33493456 33493456 33475168 33407350 33395920 33395920 33395920 Y 10480294 10480294 10480294 10480294 10480294 10480294 10480294 10480294 10462006 10319258 10300970 10300970 10300970 10300970 10300970 10300970 Z 501904 477393 475615 468376 450088 450088 450088 450088 450088 450088 450088 450088 450088 450088 438658 417449 X 33274000 33274000 33274000 33274000 33292288 33475168 33493456 33493456 33493456 33493456 33475168 33407350 33395920 33395920 33395920 33395920 Y 10480294 10480294 10480294 10480294 10480294 10480294 10480294 10462006 10319258 10300970 10300970 10300970 10300970 10300970 10300970 10300970 Z 477520 475615 468376 450088 450088 450088 450088 450088 450088 450088 450088 450088 450088 438658 417449 410210 Occ 7 26 35 34 34 7 33 33 6 32 32 5 29 29 103 305 in_cp Out_cp Leg Dn_occ Sg_occ 1 1 1 1 0 2 1 0 2 1 0 2 1 0 2 2 2 2 2 0 2 1 0 2 1 0 2 1 0 3 1 1 in in in in ou in in ou in in ou in in b1 in in 26 35 34 0 7 33 0 6 32 0 5 29 0 103 305 25 15 15 16 16 16 16 16 16 16 16 16 16 16 14 14 14 Dash
GAT STRT STRT FBLD STRT FWN E90L PSP2 E90L REDE REDE NIP GATR NIP CAPO FWN NOZ T PIPE E90L E90L PIPE FWN GAT STRT STRT FBLD STRT FWN E90L PSP2 E90L REDE REDE NIP GATR NIP CAPO FWN NOZ
33395920 33395920 33395920 33379283 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33384490 33255712 33237424 33237424 33237424 33237424 33237424 33237424 33220787 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424
10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10282682 10277094 10277094 10277094 10277094 10277094 10271506 10264394 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10282682 10277094 10277094 10277094 10277094 10277094 10271506 10264394
410210 388620 370078 370078 370078 351536 344297 326009 326009 326009 327089 321501 315405 309817 303721 328168 328168 450088 450088 450088 450088 431800 417449 410210 388620 370078 370078 370078 351536 344297 326009 326009 326009 327089 321501 315405 309817 303721 328168 328168
33395920 33395920 33379283 33378140 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33395920 33384490 33255712 33237424 33237424 33237424 33237424 33237424 33237424 33220787 33219644 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424 33237424
10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10282682 10271506 10277094 10277094 10277094 10277094 10277094 10264521 10258298 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10300970 10282682 10271506 10277094 10277094 10277094 10277094 10277094 10264521 10258298
388620 370078 370078 370078 351536 344297 326009 299847 326009 328168 321501 315405 309817 303721 303213 328168 328168 450088 450088 450088 431800 417449 410210 388620 370078 370078 370078 351536 344297 326009 299847 326009 328168 321501 315405 309817 303721 303213 328168 328168
25 24 24 28 24 23 22 4 22 17 17 18 19 20 21 16 3 29 3 30 30 4 31 15 14 14 27 14 13 12 3 12 7 7 8 9 10 11 6 1
2 2 0 1 0 1 2 1 0 1 0 1 1 1 1 2 2 0 1 2 0 1 2 2 2 0 1 0 1 2 1 0 1 0 1 1 1 1 2 2
1 0 3 0 1 2 0 2 1 2 3 2 2 2 0 1 1 2 2 0 1 2 1 1 0 3 0 1 2 0 2 1 2 3 2 2 2 0 1 1
in in b1 in ou in in in ou in ta in in in in in in ou in in ou in in in in b1 in ou in in in ou in ta in in in in in in
24 0 28 0 23 22 0 0 17 16 18 19 20 21 0 3 0 3 30 0 4 31 15 14 0 27 0 13 12 0 0 7 6 8 9 10 11 0 1 0
14 14 13 13 11 11 11 11 11 11 12 12 12 12 12 9 9 17 17 17 8 8 8 8 8 7 7 5 5 5 5 5 5 6 6 6 6 6 3 3 End Dash End End End Dash End End
4 - 12
4.2 Section 1: Basic Input Data and Raw Design File Data __________________________________________________________________________________________________________________________________________________
The first section of the HITS report consists of basic input data and raw design data. The basic input data consists of the date the report was executed, project name and a list of model names that were extracted. Each column of the raw design file data is described below. Name occ The first four characters of the component item name. The component database occurrence number (excluding the partition number). Note that some PIPE components have an occurrence number greater than 30000. This occurs whenever olet type components are attached to a pipe. The software breaks these pipes into multiple sections. The newly created pieces of pipe receive occurrence numbers in the 30000+ range to distinguish them from the original pipe. cp # x,y,z The connect point number The coordinate in the design file coordinate system and is not adjusted for the global origin A node number assigned to all connect points other than the origin. A special node number, -1, is reserved for line endpoints. Two connect points that have the same node number are connected to each other in the model. A direction list number. The direction list number identifies all those connect points that lie together on a straight line. Section number [always 0] A bit mask used internally by the software Topos [always 0] Branch flag [always 0] The segment occurrence number. All connect points belong to or are owned by a segment in the piping model. This is the occurrence number of that owner segment.
node
direct
sect flags topo branch sg_occ
4.3 Section 2: Design File Data Sorted by Coordinate __________________________________________________________________________________________________________________________________________________

The second section of the HITS report consists of raw design file data for each connect point of the piping components that make up the network that is being extracted. The database search criteria from section 1 is used to find all of the appropriate segments. Once the segments are found, the software collects all of the components that are attached to the segments. Section 2 is the result of this activity. Section 2 contains several columns of data. Each column is described below: Name occ Is the first four characters of the component item name. The database occurrence number of the component (excluding the partition number). [Note that some PIPE components have an occurrence number greater than 30000. This occurs whenever olet type components are attached to a pipe. The software "breaks" these pipes into multiple sections. The newly created pieces of pipe receive occurrence numbers in the 30000+ range to distinguish them from the original pipe.] The connect point number. The coordinate in the design file coordinate system and is unadjusted for the global origin. A node number assigned to all connect points other than the origin. A special node number , -1, is reserved for line endpoints. Note that two connect points that have the same node number are "connected" to each other in the model. A direction list number. The direction list number identifies all those connect points that lie together on a straight line. Always 0 here. Section number is described later in this section. A bit mask used internally by the software. Always 0 here. Topos are discussed later in this section. Always 0 here. The branch flag is discussed later in this section. The segment occurrence number. All connect points "belong to" or "are owned" by a segment in the piping model. sg_occ is the occurrence number of that owner segment.
cp # x,y,z
node
direct
sect flags topo branchsg_occ-
Section 2 is primarily used for examining the amount of data pulled in from the models through the database search criteria. Some of the data for a specific connect point is sometimes useful particularly the occurrence number.
4 - 14
4.4 Section 3: Tracing Data __________________________________________________________________________________________________________________________________________________

Section 3 of the report, Tracing Data is a record of the actions the software is taking in building the internal data structure of the piping network. This section is primarily useful to Intergraph for investigating software problems. The last statement in section 3 states how many disconnected sections of piping exist in the network identified in the database search criteria. If the number of sections is greater than 1 then the line is not extracted and the intermediate data file is not generated. PDSTRESS does not allow multiple, disconnected sections of piping to be extracted into a single iso. The following is a list of possible reasons why a network might be disconnected and some suggested solutions: 1. The database search criteria identified more than one pipeline and the pipelines are not connected together. The solution here is to change the search criteria so that only the piping that you really want to extract is pulled in.
2.
The pipeline being extracted is incomplete and portions of it do not have components on it. The solution is to place all of the components on the line.
3.
Although the line is finished, there is a part of it that appears to be connected but really is not. To be considered connected, the connect points from two different components must be within about 20 uors of each other. In this case you should examine section 2 of the HITS report to find a connect point whose node number is -1 (which indicates that it is a line endpoint) even though you know it should be connected to something. This is usually quite simple when the line is small. When you find the connect point, use the coordinate to view and repair the disconnected graphics. When the line is complicated, you can use section 4 of the HITS report (see the section Tracing Data) to make a sketch that identifies the disconnected point.
4.5 Section 4: Design File Data Sorted by Topo __________________________________________________________________________________________________________________________________________________

Section 4 of the HITS report is probably the most important one. This section is really a printout of the internal data structure that represents the piping network. This data is organized on the basis of topos. A topo is a construction used to group the data representing the pipeline topology. By definition a topo is a string of piping that starts at a network endpoint or a branch point and ends at a network endpoint or another branch point. A pipeline network may consist of a single topo or dozens of topos depending upon its configuration.
Figure 4 - 1. Example line consisting of one topo The line in Figure 4-1 consists of one topo because it does not contain any branch points. The beginning of the topo is a line endpoint as is the end of the topo.
4 - 16
Figure 4 - 2. Example line consisting of two topos The line in Figure 4-2 contains two topos due to the branch component in it (the tee). The first topo consists of the line from endpoint 1 to endpoint 2 (the header of the pipeline). The second topo consists of the piping from the center of the tee to line endpoint 3.
Figure 4 - 3. Example line consisting of three topos The line in Figure 4-3 contains three topos because there are two branches in it. The first topo again consists of the line from endpoint 1 to endpoint 2. The second topo consists of the line from connect point 1 of weldolet 1 to endpoint 3. The third topo consists of the line from connect point 1 of weldolet 2 to endpoint 4.
4 - 18
Figure 4 - 4. Topos on a line that contains a loop The line in Figure 4-4 consists of two topos. One topo is comprised of the line header from endpoint 1 to endpoint 2. The other topo starts at the center of one tee and goes to the center of the other tee. The data in section 4 of the HITS report is sorted primarily by topo number. At the very beginning there are several lines where the topo number is zero. These are component origins which do not receive topo numbers or node numbers they should be ignored. Subsequent to the lines where the topo number is zero are lines for the first, second and subsequent topos. The secondary sort key for the data in section 4 of the report is node number. Thus, within a topo the data is sorted by node number. This results in connect points with the same node number being adjacent to each other in the report. The result is that section 4 of the HITS report contains a trace of each topo of the line.
Example 1: The following is an excerpt from a HITS report section 4:
Name E90L E90L PIPE PIPE E90L E90L PIPE PIPE GATR GATR PIPE PIPE
cp# 1 2 1 2 2 1 2 1 1 2 1 2
node -1 1 1 2 2 3 3 4 4 5 5 -1
topo 1 1 1 1 1 1 1 1 1 1 1 1
This trace consists of a single topo. The first endpoint is connect point 1 of a 90 degree elbow. Connect point 2 of the elbow is connected to connect point 1 of a pipe. Following this logic, the sequence of components starting from the top is: elbow -> pipe -> elbow -> pipe -> valve -> pipe. This same procedure may be followed to sketch out each network topo. Topo sketches are useful if you are interested only in the sequence of components in a particular region of the line. If you are interested in the entire network, connect the topos together. The topos are connected together by the branch column in section 4 of the report. The branch column is used together with the last column. The last column in section 4 is a report line number. You can see by looking back at Figure 4-1 that the last column starts out at 1 and is incremented for each line in section 4. When the branch column contains a nonzero value then this indicates that the node is a branch point. The value of branch refers you to the line number of the report where the connecting topo begins. Example 2: The following is an excerpt from a HITS report section 4:
Name PIPE PIPE PIPE PIPE WOL WOL PIPE PIPE
occ# 10 10 30001 30001 15 15 35 35
cp# 1 2 1 2 1 2 1 2
node -1 1 1 2 1 3 3 -1
topo 1 1 1 1 2 2 2 2
branch 0 5 5 0 -2 0 0 0 1 2 3 4 5 6 7 8
The network is composed of two topos. Topo 1 is simply two pipes. Topo 2 consists of a weldolet connected to a piece of pipe. Note that the occurrence number of the second pipe in topo 1 indicates the model contains a single pipe
4 - 20
which the software split into two at the olet. Figure 4-5 shows the Network for Example 2.
Figure 4 - 5. Network for Example 2 The value for branch at node 1 is 5. Looking at line 5 in the report we see that it is the first line of topo 2. Thus topo 2 connects to topo 1 at node 1. This is confirmed by the fact that the node numbers where topo 2 connects to topo 1 match. That is, the WOL cp1, PIPE (occ 10) cp2, and PIPE (occ 30001) cp1 are all node number 1. The value of branch for cp1 of the WOL is -2. The negative sign indicates that this is a "back pointer". The back pointer is exactly the same as any other branch value except that it (usually) points back to a previous topo rather than forward to a subsequent topo. Note that where two or more topos are connected together the branch numbers must agree. In Example 5 they do. The back pointer on topo 2 points back to line 2 while the forward pointer on topo 1 points to line 5. In Example 2, the branch flag pointed to the start point of the connecting topo. It can also happen that the branch flag points to the endpoint of the connecting topo. In this case you traverse the topo in reverse order. Example 3:
Name
occ#
cp#
node . . . 20 21 21
topo
branch
PIPE PIPE 90E
10 10 35
1 2 2
3 3 3
0 0 0
20 21 22
90E PIPE PIPE PIPE PIPE
35 46 46 30003 30003
1 1 2 1 2
PLUG PLUG BLV BLV NIPL NIPL SOL SOL
76 76 82 82 103 103 110 110
2 1 1 2 2 1 2 1
22 22 23 23 24 . . . -1 10 10 11 11 12 12 23 . . .
3 3 3 3 3
0 0 53 53 0
23 24 25 26 27
7 7 7 7 7 7 7 7
0 0 0 0 0 0 0 -25
46 47 48 49 50 51 52 53
In Example 3, topo 3 consists of pipe, elbow, pipe, pipe. Topo 7 is a typical drain assembly plug, block valve, nipple, sockolet. Topo 7 connects to topo 3 at line 53 in the report (the value of branch on line 25 is 53 and the value of branch of line 53 is -25). In this case, the value of branch on topo 3 points to the bottom of topo 7 and the network structure is obtained by moving up topo 3 rather than down (See Figure 4-6).
Figure 4 - 6. Network for Example 3
4 - 22
Example 4: The following data is from section 4 of a HITS report:
Name 90E 90E PIPE PIPE FLWN FLWN GAT GAT FLWN FLWN T T PIPE PIPE T PIPE PIPE
Occ 37 37 101 101 22 22 54 54 11 11 36 36 11 11 36 12 12
cp# 1 2 1 2 2 1 1 2 1 2 1 2 1 2 3 1 2
Node -1 1 1 2 2 3 3 4 4 5 5 6 6 -1 7 7 -1
Topo 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2
Branch 0 0 0 0 0 0 0 0 0 0 15 15 0 0 -11 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
In Example 4, the tee is slightly different from the olet type components. Branch flags are set on both connect points 1 and 2 of the T and the node numbers do not match where topo 2 connects to topo 1. This is a consequence of the fact that node numbers are not assigned to component origins. See Figure 4-7 which shows the Network for Example 4.
Figure 4 - 7. Network for example 4
Example 5:
Name PIPE PIPE REDE REDE PIPE PIPE SOL SOL PIPE PIPE PIPE PIPE
Occ 23 23 24 24 13 13 56 56 42 42 26 26
cp# 1 2 1 2 1 2 1 2 1 2 1 2
Node -1 1 1 2 2 -1 3 4 4 -1 5 -1
Topo 1 1 1 1 1 1 2 2 2 2 3 3
Branch 0 0 7 11 0 0 -3 0 0 0 -4 0 1 2 3 4 5 6 7 8 9 10 11 12
In Example 5, topo 1 consists of a pipe connected to an eccentric reducer which in turn is connected to another pipe. Notice, however, that the branch flag is set to two different numbers on the reducer. This indicates that the reducer is tapped twice. The branch flag on the first connect point points to the topo connected at the first tap while the branch flag on the second connect point points to the topo connected to the second tap. A tap is always a branch starting point and thus is always the start point of a new topo. Refer to Figure 4-8, which shows the network for Example 5.
Figure 4 - 8. Network for Example 5 If you generate some HITS reports and practice sketching out the pipeline networks, you will become familiar with the report contents and better understand the concepts presented in the examples above.
4 - 24
4.6 Section 5: Design File Data in STR Order __________________________________________________________________________________________________________________________________________________

Section 5 of the HITS report contains a record of how the network is traversed as the neutral file is being generated. The software examines the network of piping and chooses the best (that is, the one least likely to result in problems from PDSTRESS) topo to begin the network traversal on. PDSTRESS prefers certain navigation sequences over others and the interface software tries to choose the optimal sequence. PDSTRESS also requires that the traversal of the network be branch first order. This means that whenever a branch is encountered in the network, the traversal must head down the branch before continuing down the header. To traverse the network in branch first order manner you start on the header topo and travel connect point by connect point until the value of branch is greater than 0 at some node. When branch is positive then you jump down to the new topo and start traversing it until you come to another branch or to the end. If you encounter another branch then you must jump again to another topo. When the end of the topo is found then you return to the topo from which you jumped and continue tracing. Example 6: The following is an example of a network:
Name PIPE PIPE T T PIPE PIPE T PIPE PIPE
Occ 10 10 11 11 12 12 11 13 13
cp# 1 2 1 2 1 2 3 1 2
Node -1 1 1 2 2 -1 3 3 -1
Topo 1 1 1 1 1 1 2 2 2
Branch 0 0 7 7 0 0 -3 0 0 1 2 3 4 5 6 7 8 9
In Example 6, topo 1 consists of a header, two pipes, and the run of a tee. Topo 2 consists of a branch, the branch leg of a tee and a branch pipe. Following the rules given above for traversal of the network would yield the following trace:
Name PIPE T T PIPE T PIPE
Occ 10 11 11 13 11 12
cp in 1 1 0 1 0 1
cp out 2 0 3 2 2 2
Leg 1 1 2 1 4 1
Step 1 travels from one end of the first pipe to the other. Following the first pipe we travel into the tee. Notice that although the origins do not have node numbers they appear in the traversal whenever a change in direction occurs. This means that, for the tee, the traversal occurs from connect point 1 to the origin in step 2. At this point the branch flag is positive and so a jump occurs to topo 2. On topo 2 we travel from the origin of the tee to connect point 3 (which is the branch connect point) in step 3. In step 4 we travel down a pipe which is the last component on the topo. We then jump back to topo 1 and in step 5 travel from the tee origin to connect point 2. Finally, in the last step we traverse the remaining pipe on topo 1. Refer to Figure 4-9 for an illustration of this traversal. The header topo number can be found by examining the first line in the traversal. In this case the first line consists of PIPE occurrence 10. Looking at the network description, observe that PIPE occurrence 10 is on topo number 1. This makes topo 1 the header topo.
Figure 4 - 9. Traversal in Example 6 In PDSTRESS terminology one step in the above trace is termed a component leg. Straight through components like pipe, flanges, and valves consist of one leg. Change of direction components like elbows, angle valves and so on consist of two legs. Branch components like tees, olets, 3-way and 4-way valves and crosses consist of three or four legs. In Example 9, the last leg of the tee is given a leg number of 4. By definition only 4-way components have a leg 3 (which would correspond to the 2nd branch leg). Branches off from components formed by taps are termed branch legs and are not given a number. Branch legs are treated as other branches are though. When a tapped component is encountered in the network then all the tapped legs must be traced before continuing down the topo. Although olet type components have a different connect point skeleton than tees do they are treated similarly in the network trace. This is highlighted in the next example:
4 - 26
Example 7: The following is a network:
Name 90E 90E PIPE PIPE PIPE PIPE WOL WOL PIPE PIPE
Occ 8 8 10 10 30001 30001 6 6 9 9
cp# 1 2 1 2 1 2 1 2 2 1
Node -1 1 1 2 2 -1 1 2 2 -1
Topo 1 1 1 1 1 1 2 2 2 2
Branch 0 0 0 7 7 0 -4 0 0 0 1 2 3 4 5 6 7 8 9 10
The network trace for this network is:
Name 90E 90E PIPE WOL WOL PIPE WOL
Occ 8 8 10 6 6 9 6
cp in 1 0 1 1 1 2 1
cp out 0 2 2 1 2 1 1
leg 1 2 1 1 2 1 4
In Example 7, the first leg of the olet goes from connect point 1 to connect point 1. It is analogous to the step with the tee where traversal goes from connect point to the origin. In this case the traversal does not go anywhere and therefore is called a zero length leg. The second leg traverses from cp1 to cp2 analogous to the previous examples traversal from the tee origin to cp3. After the branch topo has been traversed we return to the olet for leg 4 which again goes from cp1 to cp1 another zero length leg. This step is analogous to going from the origin to cp3 in the previous example. Notice also the traversal through the elbow. Since the elbow causes a change of direction, it is traversed in two legs: 1) from cp1 to the origin and 2) from the origin to cp2. Sometimes the traversal of the network requires traveling into the branch leg of a branch component. When this happens the leg numbers are assigned somewhat differently on the branch component.
Example 8: The following is a partial network:
Name
Occ
cp#
Node . . . 20 21 21 . . . -1 52 52 53 53 -1
Topo
Branch
PIPE PIPE T
10 10 15
1 2 3
4 4 4
0 0 -61
46 47 48
PIPE PIPE T T PIPE PIPE
12 12 15 15 17 17
1 2 1 2 2 1
7 7 7 7 7 7
0 0 48 48 0 0
59 60 61 62 63 64
In Example 8, a lower numbered topo (topo 4) contains a back pointer to a higher numbered topo (topo 7). Whenever this happens, the traversal will enter branch. The trace for this part of the network would be:
Name PIPE T T PIPE T PIPE
Occ 10 15 15 12 15 17
cp in 1 3 0 2 0 2
cp out 2 0 1 1 2 1
leg 1 1 2 1 4 1
In this example, the branch leg of the tee is leg 1 since it is traversed first. Legs 2 and 4 are assigned arbitrarily in this situation and so tracing may go either way (PDSTRESS has no preference). Refer to Figure 4-10 which shows this network traversal.
Figure 4 - 10. Network traversal in example 8
4 - 28
4.7 Using the HITS Report to Solve Problems __________________________________________________________________________________________________________________________________________________

When you have difficulty extracting a line, the first thing you should do in analyzing the problem is to sketch out the network. Often this is enough to identify the problem. If the structure in section 4 of the report is incorrect that is, the topos are not correctly defined and connected or the pointers appear incorrect then PDSTRESSs input will be wrong and the drawing will definitely be incorrect. When the data structure represented in section 4 of the report is incorrect then you can conclude that either the interface has a bug or there is a problem in the model. Typical model problems include such things as disconnected sections and overlapping components or pipes. When the modeler has inadvertently placed two pipes on top of each other you will get an error message at the top of the HITS report stating this. The message will also report a node number where the problem was detected. By getting the coordinate of the node you can pinpoint where in the model the problem occurs. This can also occur where the connect points of components overlap each other and are not properly connected. Notice that one of the columns in section 4 of the report is called section. In a correct network all of the topos should have a value of 1 in this column. When the network is composed of multiple disconnected sections, however, some topos will contain a value other than 1. In this case the network for each section should be sketched out. It should be apparent after doing this where the different sections should have been connected in the model and, therefore, where the trouble spot is. Another problem that might occur is that components that should all be colinear are not. This is detected by examining the direction list number. If the direction list changes for example from one pipe to another then a problem exists in the model and the line can not be extracted properly. Mismatches between the design file and database can also cause iso extraction failures but these types of problems should be trapped and reported adequately in other areas of the software. You should not need to rely on the HITS report to find these kinds of problems. When the data structure in section 4 of the report is correct then the traversal in section 5 should be examined. Even if the network is correct, some other bug can cause the network traversal to fail. Again, if the traversal is incorrect then PDSTRESS will definitely fail. When both the network and the traversal are correct, there is most likely a problem with PDSTRESS. When PDSTRESS is at fault, then one of the following scenarios is true: 1. The drawing appears correct for the most part but some aspect of it is incorrect.
When this happens there is usually some option or combination of options that have been enabled that resulted in the problem. The best way to find the cause of the problem is to start with a basic drawing generation setup that contains few "special" options. Then add a few options at a time until the problem is reproduced. Finally, through a process of elimination identify the option that is causing the problem. All failures of this type should be reported to Intergraph.
2.
The drawing or one sheet of it is scrambled a total failure. When this happens it is usually the case that disabling options will not result in the drawing working though sometimes it does. The best thing to do when this happens is to try and reextract a smaller portion of the line if possible. The failure should also be reported to Intergraph. When any sheet of an PDSTRESS drawing fails, ALL sheets from the same pipeline may contain errors and are suspect.
4 - 30
The Stress Analysis Neutral File 5 - 1
5. The Stress Analysis Neutral File
__________________________________________________________________________________________________________________________________________________
5-2
5.1 Neutral File Format __________________________________________________________________________________________________________________________________________________

The neutral file produced by the PD_Stress Analysis Interface consists of eight sections of data. Each section of the file is composed of one or more records in the neutral file. Each record 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 the neutral 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 file section where the record keyword is LOAD. Data about each component in a network is put in a file section where records begin with PROP. A common text string (the pointer) in each of the record types associates a set of temperatures and pressures with a given component. These pointers keep the file reasonably compact. 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 the model files and line names used in the extraction. The date and time of the run is also included. Single record containing fields that identify the run. (Use of this record is not fully supported at this time.) Several records, each beginning with the keyword LOAD, which contain the temperatures 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 of temperatures and pressures with a given component. More than one LOAD record may be generated for a segment depending on how many temperature/pressure pairs you put on a single record. Section 4 Records that begin with the keyword LSET. These records specify the temperature/pressure pair used from each segment when analyzing the line for different loading conditions (that is, deadweight, cold condition, hot condition and wind condition cases). The PD_Stress Analysis Interface puts values in these records based upon criteria you specified in the defaults file. (Refer to the Defaults File section for more information.) Records beginning with keyword CODE. A CODE record is generated for each unique value of the analysis code attribute stored in the piping segment entities. Each component has a pointer pointing back to one of these CODE records.
Section 2
Section 3
Section 5
Section 6
Set of records for each component in the network. The first record of each set is an overall component record. It does not begin with a keyword. Instead, the first field consists of the component name obtained from the PDS to Stress Interface Symbol Map. The second field contains a component ID or pointer that groups this record with the records that follow for the same component. This first record also contains network connectivity information through a list of node numbers corresponding to the component. Node numbering conventions for components are discussed later in this section. Following this first record are a series of records each of which begin with the keyword PROP. Each PROP record contains the component ID pointing back to the overall component record. Each of these records also has a form type identifying the data contained 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 the bend radius and the bend angle. connect point data. This data includes size and schedule. It also includes the segment pointer that associates each connect point with LOAD and LSET records.
Section 7
Records beginning with the keyword LNOD. These records are generated at equipment nozzles (indicating that the nozzle is an anchor) and when data associated with a pipe support indicates that the support is acting as a node restraint. When a support acts only as a restraint, the component records are not generated for it. LNOD records define which directions and/or rotations are restrained at a node. Records beginning with the keyword NODE. These records hold the coordinate of each node in the network.
Section 8
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, ... . . . LSET, SEGIDn, ...
5-4
CODE, CODEID1, ... CODE, CODEID2, ... . . . CODE, CODEIDn, ... NAME1, COMPID1, CODEID1, ... N1, N2 PROP, NAME1, COMPID1, FORM1, ... . . . PROP, NAME1, COMPID1, FORMn, ... , SEGID1 PROP, NAME1, COMPID1, FORMm, ... , SEGID1 NAME2, COMPID2, CODEID1, ... N3, N4, N5 PROP, NAME2, COMPID2, FORM1, ... . . . PROP, NAME2, COMPID2, FORMn, ... , SEGID1 PROP, NAME2, COMPID2, FORMm, ... , SEGID2 PROP, NAME2, COMPID2, FORMo, ... , SEGID3 . . . NAMEn, COMPIDn, CODEIDn, ... , Nm, Nm PROP, NAMEn, COMPIDn, FORM1, ... . . . PROP, NAME2, COMPID2, FORMn, ... , SEGIDn PROP, NAME2, COMPID2, FORMm, ... , SEGIDn LNOD, Nn, ... LNOD, Nm, ... NODE, N1, x1, y1, z1 NODE, N2, x2, y2, z2, . . . NODE, Nn, xn, yn, zn Within the form or skeleton outlined above, you can map attributes from the database into the neutral file by modifying the stress analysis defaults file.
5.2 Detailed Record Descriptions __________________________________________________________________________________________________________________________________________________

LOAD LSET CODE LNOD NODE
5.2.1 LOAD Record __________________________________________________________________________________________________________________________________________________

The general LOAD record format is:
LOAD, segid, i, j, Ti, Pi, ... , Tj, Pj
where: LOAD segid is the record keyword (MLOAD for metric models) is a pointer used to associate a LOAD record with each component in the piping network is the subscript of the lowest temperature/pressure pair on the record is the subscript of the highest temperature/pressure pair on the record. Record elements i and j define a range of subscripts. is a temperature, pressure pair of subscript n
i j
Tn,Pn Example
LOAD, 1117654, 1, 3, 100, 150, 100, 175, 300, 200 LOAD, 1117654, 4, 6, 175, 200, 175, 250, 225, 250 In this example, the segment ID is 1117654. The first LOAD record defines T,P pairs 1, 2 and 3 while the second LOAD defines T,P pairs 4, 5 and 6. You can force the interface software to generate a single record containing pairs 1 through 6, though the record would most likely be longer than 80 characters.
5.2.2 LSET Record __________________________________________________________________________________________________________________________________________________

The general format of the LSET record is as follows:
LSET, segid, s1, s2, s3, s4
where:
5-6
LSET segid
is the record keyword is the segment pointer used to associate an LSET record with each component in the piping network identifies the T,P pair used when analyzing under case 1 conditions (for example, deadweight) identifies the T,P pair used when analyzing under case 2 conditions (for example, hot) identifies the T,P pair used when analyzing under case 3 conditions (for example, cold) identifies the T,P pair used when analyzing under case 4 conditions (for example, wind)
s1
s2
s3
s4
In the defaults file, you can either hard code the numbers that are actually placed in LSET records for each segment or you can set them based upon the value of any attribute stored in the segment. Refer to the Default File section for more information.
5.2.3 CODE Record __________________________________________________________________________________________________________________________________________________

The general format of a code record is:
CODE, codeid, string
where: CODE codeid is the record keyword is a label used to associate each component in the piping network with a CODE record is a string defining the analysis code name
string Example
CODE, CODE6, ASME2 1977 B In this example, the code ID is the string CODE6 formed by appending the code list number from the segment attribute that defines the code to the characters CODE. The string ASME2 1977 B is defined by you in the defaults. The definition states that when the code attribute in the segment is set to code list number 6, a given string is generated in the neutral file CODE record.
5.2.4 Component Records __________________________________________________________________________________________________________________________________________________

Overall Component PROP
5.2.4.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 is a label uniquely identifying the component (much the same as the segment ID uniquely identifies a segment) is the label pointing back to a particular CODE record is a list of component attributes defined by you in the defaults file that apply to the component as a whole and are not specific to the component type. These attributes may come from either the segment or component entities. is the node list for the component. The node list defines the node numbers for each node of the component. The number of nodes in the node list is a function of the component type. The nodes are ordered in the list so that the first corresponds to connect point 1, the second to connect point 2 and so on. Refer to the Node Numbering Conventions section for more information.
compid
codeid data
nodes
5.2.4.2 PROP Record __________________________________________________________________________________________________________________________________________________

The general form of a PROP record is:
PROP, name, compid, form, data
where: PROP name is the record keyword (MPROP for metric models) is the component name and is the same name as appears on the overall component record.
5-8
compid
is the unique ID of the component which also appears on the overall component record is a form number you defined in the defaults file. The component name together with the form number uniquely defines the data that follows on the record. is a list of attributes you defined in the defaults file. Each component type and form number combination has its own set of attributes.
form
data
5.2.5 LNOD Record __________________________________________________________________________________________________________________________________________________

The general format of the LNOD record is:
LNOD, node, type, service, Dx, Dy, Dz, Ax, Ay, Az
where: LNOD node type is the record keyword is the restrained node number identifies the action taking place at the node. Currently the only allowed value for this item is RE (for restraint). is set to 1 if the node is restrained in the x direction and 0 if not is set to 1 if the node is restrained in the y direction and 0 if not is set to 1 if the node is restrained in the z direction and 0 if not is set to 1 if rotation is restrained about the x axis and 0 if not is set to 1 if rotation is restrained about the y axis and 0 if not is set to 1 if rotation is restrained about the z axis and 0 if not Using this record requires that movement be restrained in both the positive and negative directions. When Intergraph option switch 17 is set to a one a second LNOD record will be generated with the following format.
LNOD, node, type, service, NX, NY, NZ, AX, AY, AZ
Dx Dy Dz Ax Ay Az
where: LNOD node is the record keyword is the restrained node number
type
identifies the action taking place at the node. Currently, the only allowed value for this item is MV (for movement). identifies the service condition. Currently the only allowed value for this item is 1. is the nozzle normal thermal growth in the X direction. Refer to the equipment schema table 22 column 19. is the nozzle normal thermal growth in the Y direction. Refer to the equipment schema table 22 column 20. is the nozzle normal thermal growth in the Z direction. Refer to the equipment schema table 22 column 21. is the nozzle alternate thermal growth in the X direction. Refer to the equipment schema table 22 column 22. is the nozzle alternate thermal growth in the Y direction. Refer to the equipment schema table 22 column 23. is the nozzle alternate thermal growth in the Z direction. Refer to the equipment schema table 22 column 24.
service
NX
NY
NZ
AX
AY
AZ
5.2.6 NODE Record __________________________________________________________________________________________________________________________________________________

The general format of the NODE record is:
NODE, node, x, y, z, flag, intens
where: NODE node x,y,z flag intens is the record keyword (MNODE with a metric model) is the node number of the node is the coordinate of the node in subunits (in or mm) is a coordinate system identifier is a stress intensification factor to be applied to the node. This value is not calculated but taken from a database attribute you already set.
5 - 10
5.3 Node Numbering Conventions __________________________________________________________________________________________________________________________________________________

The last set of fields generated on each overall component record is the node number set for the component. The node number set identifies the node number of each node on a component. The following conventions are used in assigning the node numbers in the set: Straight through components (pipe, reducer, rigid bodies, flanges, etc.) Only the connect points are given nodes. These types of components will only have two nodes. Internal nodes are never generated. Straight through valves with hand-wheel operators Nodes 1 and 2 are generated at the valve connect points. Node 3 is generated at the valve center. If the valve operator has a center-ofgravity defined, a fourth node is generated at the center-of-gravity. Tee type components Nodes 1 and 2 are generated at the connect points on the run of the tee. Node 3 is generated at the branch connect point and node 4 is generated at the center of the tee. Olet and branch weld type components Only two nodes are generated, one for each connect point. Elbows and bent pipe Nodes 1 and 2 are generated at connect points. Node 3 is generated at the component origin. Eccentric reducers Nodes 1 and 2 correspond to the two connect points. Elements 3, 4, and 5 in the node list are the components of a vector that orients the flat side of the reducer. Two-way valves Nodes 1 and 2 are generated at the connect points. Node 3 is generated at the component center. If the valve operator has a center of gravity, node 4 is generated at the center of gravity. Three-way valves Nodes 1 and 2 are generated at the connect points from the run of the valve. Node 3 is generated at the branch connect point and node 4 is generated at the component center. If the valve operator has a center of gravity defined, node 5 is generated at the center of gravity.
Pipe supports Pipe supports that are not converted to node restraints by the interface will have two nodes. The first node is generated at the point that the pipe support attaches to the pipe line. The second node is a dummy node and simply defines an orientation for the support. To a certain extent, you can control the node numbers assigned to nodes. You do this using the defaults file options. The PD_Stress Analysis Interface distinguishes between three types of nodes in a piping network: nodes at connections between components nodes internal to components (nodes at the center of elbows or valves) nodes at network endpoints. You can specify the starting node number for each of the different node types. For nodes at component connections, you can also specify the increment to use in generating the next node number. Refer to the Defaults File section for more information.
5 - 12
5.4 Example Neutral File __________________________________________________________________________________________________________________________________________________

! Model Design file(s) : sriso03 ! Line name(s) : 3002 ! Date : 22-MAY-91 20:16:31 DRAW ,3002,3002 LOAD, 300001G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LOAD, 300001G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LSET, 300001G,3,6,5,3 LOAD, 300002G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LOAD, 300002G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LSET, 300002G,3,6,5,3 LOAD, 300005G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LOAD, 300005G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LSET, 300005G,3,6,5,3 LOAD, 300006G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LOAD, 300006G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LSET, 300006G,3,6,5,3 LOAD, 300003G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LOAD, 300003G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00 LSET, 300003G,3,6,5,3 CODE,CODE0,B31.1,1983 FL, 3300001,4"STDFAAABAWAAA,,CODE0, 901, 1 PROP,FL, 3300001, 1,A105,15.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300001, 3,4.,9.000000,WN,0.,CL150, 300001G PROP,FL, 3300001, 4,4.,4.500000,BW,0.237,CL150, 300001G ER, 3300002,6"x4"STDWRBAAAWAAA,,CODE0, 3, 1, 0, 0.00, 0.00, -1.00 PROP,ER, 3300002, 1,A234-WPB,8.000000,-32768.000000,0.000000,0,0,0. PROP,ER, 3300002, 2,0.,0.,0.,0.,0. PROP,ER, 3300002, 3,6.,6.625000,BW,0.28,, 300002G PROP,ER, 3300002, 4,4.,4.500000,BW,0.237,, 300001G PI, 5300001,6"STDPAAAAAWAAA,,CODE0, 3, 5 PROP,PI, 5300001, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00 PROP,PI, 5300001, 3,6.,6.625000,BW,0.28,, 300002G PROP,PI, 5300001, 4,6.,6.625000,BW,0.28,, 300002G FL, 3300003,6"STDFAAABAWAAA,,CODE0, 7, 5 PROP,FL, 3300003, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300003, 3,6.,11.000000,WN,0.,CL150, 300002G PROP,FL, 3300003, 4,6.,6.625000,BW,0.28,CL150, 300002G FL, 3300004,6"STDFAAABAWAAA,,CODE0, 7, 9 PROP,FL, 3300004, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300004, 3,6.,11.000000,WN,0.,CL150, 300002G PROP,FL, 3300004, 4,6.,6.625000,BW,0.28,CL150, 300002G EL, 3300005,6"STDWAAAAAWAAA,,CODE0, 9, 12, 951 PROP,EL, 3300005, 1,A234-WPB,24.000000,-32768.000000,0.000000,0,0,0. PROP,EL, 3300005, 2,9.000000,90.000000,0,0. PROP,EL, 3300005, 3,6.,6.625000,BW,0.28,, 300002G PROP,EL, 3300005, 4,6.,6.625000,BW,0.28,, 300002G FL, 3300006,6"STDFAAABAWAAA,,CODE0, 13, 12 PROP,FL, 3300006, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300006, 3,6.,11.000000,WN,0.,CL150, 300002G PROP,FL, 3300006, 4,6.,6.625000,BW,0.28,CL150, 300002G VA, 3300007,6"VAABAHCCAA,,CODE0, 13, 14, 952 PROP,VA, 3300007, 1,A216-WCB,175.000000,-32768.000000,0.000000,0,0,0. PROP,VA, 3300007, 2,0.000000,GTE,0.,0.,1. PROP,VA, 3300007, 3,6.,0.000000,WN,0.,CL150, 300002G PROP,VA, 3300007, 4,6.,0.000000,WN,0.,CL150, 300002G FL, 3300008,6"STDFAAABAWAAA,,CODE0, 14, 15 PROP,FL, 3300008, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.
PROP,FL, 3300008, 3,6.,11.000000,WN,0.,CL150, 300002G PROP,FL, 3300008, 4,6.,6.625000,BW,0.28,CL150, 300002G TE, 3300013,6"STDWTAAAAWAAA,,CODE0, 16, 18, 24, 953 PROP,TE, 3300013, 1,A234-WPB,29.000000,-32768.000000,0.000000,0,0,0. PROP,TE, 3300013, 2,0.000000,0.0,90.000000 PROP,TE, 3300013, 3,6.,6.625000,BW,0.28,, 300002G PROP,TE, 3300013, 4,6.,6.625000,BW,0.28,, 300005G PROP,TE, 3300013, 5,6.,6.625000,BW,0.28,, 300006G PI, 5300006,6"STDPAAAAAWAAA,,CODE0, 16, 15 PROP,PI, 5300006, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00 PROP,PI, 5300006, 3,6.,6.625000,BW,0.28,, 300002G PROP,PI, 5300006, 4,6.,6.625000,BW,0.28,, 300002G HA, 8300001,psupport,SPT-001,CODE0, 954, 902 PROP,HA, 8300001, 1,,0.000000,99,0 PROP,HA, 8300001, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000 PROP,HA, 8300001, 4,1.,0.,0.,0.,0.,-1. HA, 8300003,psupport,SPT-003,CODE0, 955, 903 PROP,HA, 8300003, 1,,0.000000,99,0 PROP,HA, 8300003, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000 PROP,HA, 8300003, 4,0.,1.,0.,0.,0.,-1. FL, 3300009,4"STDFAAABAWAAA,,CODE0, 904, 2 PROP,FL, 3300009, 1,A105,15.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300009, 3,4.,9.000000,WN,0.,CL150, 300003G PROP,FL, 3300009, 4,4.,4.500000,BW,0.237,CL150, 300003G ER, 330000A,6"x4"STDWRBAAAWAAA,,CODE0, 4, 2, 0, 0.00, 0.00, -1.00 PROP,ER, 330000A, 1,A234-WPB,8.000000,-32768.000000,0.000000,0,0,0. PROP,ER, 330000A, 2,0.,0.,0.,0.,0. PROP,ER, 330000A, 3,6.,6.625000,BW,0.28,, 300005G PROP,ER, 330000A, 4,4.,4.500000,BW,0.237,, 300003G PI, 5300002,6"STDPAAAAAWAAA,,CODE0, 4, 6 PROP,PI, 5300002, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00 PROP,PI, 5300002, 3,6.,6.625000,BW,0.28,, 300005G PROP,PI, 5300002, 4,6.,6.625000,BW,0.28,, 300005G FL, 330000B,6"STDFAAABAWAAA,,CODE0, 8, 6 PROP,FL, 330000B, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 330000B, 3,6.,11.000000,WN,0.,CL150, 300005G PROP,FL, 330000B, 4,6.,6.625000,BW,0.28,CL150, 300005G FL, 330000C,6"STDFAAABAWAAA,,CODE0, 8, 10 PROP,FL, 330000C, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 330000C, 3,6.,11.000000,WN,0.,CL150, 300005G PROP,FL, 330000C, 4,6.,6.625000,BW,0.28,CL150, 300005G EL, 330000D,6"STDWAAAAAWAAA,,CODE0, 10, 22, 956 PROP,EL, 330000D, 1,A234-WPB,24.000000,-32768.000000,0.000000,0,0,0. PROP,EL, 330000D, 2,9.000000,90.000000,0,0. PROP,EL, 330000D, 3,6.,6.625000,BW,0.28,, 300005G PROP,EL, 330000D, 4,6.,6.625000,BW,0.28,, 300005G FL, 330000E,6"STDFAAABAWAAA,,CODE0, 21, 22 PROP,FL, 330000E, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 330000E, 3,6.,11.000000,WN,0.,CL150, 300005G PROP,FL, 330000E, 4,6.,6.625000,BW,0.28,CL150, 300005G VA, 330000F,6"VAABAHCCAA,,CODE0, 21, 20, 957 PROP,VA, 330000F, 1,A216-WCB,175.000000,-32768.000000,0.000000,0,0,0. PROP,VA, 330000F, 2,0.000000,GTE,0.,0.,1. PROP,VA, 330000F, 3,6.,0.000000,WN,0.,CL150, 300005G PROP,VA, 330000F, 4,6.,0.000000,WN,0.,CL150, 300005G FL, 3300010,6"STDFAAABAWAAA,,CODE0, 20, 19 PROP,FL, 3300010, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300010, 3,6.,11.000000,WN,0.,CL150, 300005G PROP,FL, 3300010, 4,6.,6.625000,BW,0.28,CL150, 300005G PI, 5300005,6"STDPAAAAAWAAA,,CODE0, 18, 19 PROP,PI, 5300005, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00 PROP,PI, 5300005, 3,6.,6.625000,BW,0.28,, 300005G PROP,PI, 5300005, 4,6.,6.625000,BW,0.28,, 300005G HA, 8300002,psupport,SPT-002,CODE0, 958, 905 PROP,HA, 8300002, 1,,0.000000,99,0
5 - 14
PROP,HA, 8300002, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000 PROP,HA, 8300002, 4,1.,0.,0.,0.,0.,-1. FL, 3300011,6"STDFAAABAWAAA,,CODE0, 906, 28 PROP,FL, 3300011, 1,A105,24.000000,-32768.000000,0.000000,0,0,0. PROP,FL, 3300011, 3,6.,11.000000,WN,0.,CL150, 300006G PROP,FL, 3300011, 4,6.,6.625000,BW,0.28,CL150, 300006G EL, 3300012,6"STDWAAAAAWAAA,,CODE0, 27, 25, 959 PROP,EL, 3300012, 1,A234-WPB,24.000000,-32768.000000,0.000000,0,0,0. PROP,EL, 3300012, 2,9.000000,90.000000,0,0. PROP,EL, 3300012, 3,6.,6.625000,BW,0.28,, 300006G PROP,EL, 3300012, 4,6.,6.625000,BW,0.28,, 300006G PI, 5300003,6"STDPAAAAAWAAA,,CODE0, 28, 27 PROP,PI, 5300003, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00 PROP,PI, 5300003, 3,6.,6.625000,BW,0.28,, 300006G PROP,PI, 5300003, 4,6.,6.625000,BW,0.28,, 300006G PI, 5300004,6"STDPAAAAAWAAA,,CODE0, 25, 24 PROP,PI, 5300004, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00 PROP,PI, 5300004, 3,6.,6.625000,BW,0.28,, 300006G PROP,PI, 5300004, 4,6.,6.625000,BW,0.28,, 300006G HA, 8300004,psupport,SPT-004,CODE0, 960, 907 PROP,HA, 8300004, 1,,0.000000,99,0 PROP,HA, 8300004, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000 PROP,HA, 8300004, 4,1.,0.,0.,0.,0.,-1. NODE, 1, 202.124016, 120.000000, 18.000000, 2, 0.000000 NODE, 2, 202.124016, 240.000000, 18.000000, 2, 0.000000 NODE, 3, 207.623524, 120.000000, 16.937500, 2, 0.000000 NODE, 4, 207.623524, 240.000000, 16.937500, 2, 0.000000 NODE, 5, 231.623031, 120.000000, 16.937500, 2, 0.000000 NODE, 6, 231.623031, 240.000000, 16.937500, 2, 0.000000 NODE, 7, 235.185039, 120.000000, 16.937500, 2, 0.000000 NODE, 8, 235.185039, 240.000000, 16.937500, 2, 0.000000 NODE, 9, 238.747047, 120.000000, 16.937500, 2, 0.000000 NODE, 10, 238.747047, 240.000000, 16.937500, 2, 0.000000 NODE, 12, 247.746555, 129.000000, 16.937500, 2, 0.000000 NODE, 13, 247.746555, 132.562500, 16.937500, 2, 0.000000 NODE, 14, 247.746555, 143.187500, 16.937500, 2, 0.000000 NODE, 15, 247.746555, 146.750000, 16.937500, 2, 0.000000 NODE, 16, 247.746555, 174.374508, 16.937500, 2, 0.000000 NODE, 18, 247.746555, 185.624508, 16.937500, 2, 0.000000 NODE, 19, 247.746555, 213.250000, 16.937500, 2, 0.000000 NODE, 20, 247.746555, 216.812500, 16.937500, 2, 0.000000 NODE, 21, 247.746555, 227.437500, 16.937500, 2, 0.000000 NODE, 22, 247.746555, 231.000000, 16.937500, 2, 0.000000 NODE, 24, 253.371555, 180.000000, 16.937500, 2, 0.000000 NODE, 25, 291.000000, 180.000000, 16.937500, 2, 0.000000 NODE, 27, 300.000000, 180.000000, 25.937500, 2, 0.000000 NODE, 28, 300.000000, 180.000000, 92.375000, 2, 0.000000 NODE, 901, 199.062008, 120.000000, 18.000000, 2, 0.000000 NODE, 902, 247.746555, 120.000000, 12.016240, 2, 0.000000 NODE, 903, 247.746555, 180.000000, 12.016240, 2, 0.000000 NODE, 904, 199.062008, 240.000000, 18.000000, 2, 0.000000 NODE, 905, 247.746555, 240.000000, 12.016240, 2, 0.000000 NODE, 906, 300.000000, 180.000000, 95.937500, 2, 0.000000 NODE, 907, 300.000000, 180.000000, 12.016240, 2, 0.000000 NODE, 951, 247.746555, 120.000000, 16.937500, 2, 0.000000 NODE, 952, 247.746555, 137.875000, 16.937500, 2, 0.000000 NODE, 953, 247.746555, 180.000000, 16.937500, 2, 0.000000 NODE, 954, 247.746555, 120.000000, 16.937500, 2, 0.000000 NODE, 955, 247.746555, 180.000000, 16.937500, 2, 0.000000 NODE, 956, 247.746555, 240.000000, 16.937500, 2, 0.000000 NODE, 957, 247.746555, 222.125000, 16.937500, 2, 0.000000 NODE, 958, 247.746555, 240.000000, 16.937500, 2, 0.000000 NODE, 959, 300.000000, 180.000000, 16.937500, 2, 0.000000 NODE, 960, 300.000000, 180.000000, 16.937500, 2, 0.000000
5 - 16
The Options File 6 - 1
6. The Options File
__________________________________________________________________________________________________________________________________________________
The options file contains switches, options, and tables that drive the PD_Stress Analysis Interface. This file gives 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 obtained by translating the variable name NEUDFLTS. The logical name is defined at the system level when the Stress Analysis product is installed on your system. You can override this system level assignment (and thus the screen default) by exporting the variable to your own customized options file.
6-2
6.1 Options File Structure __________________________________________________________________________________________________________________________________________________

The options file is composed of one set of options and several tables. The option block and each table is preceded in the options file by a keyword identifying the option or table. The keyword must be in upper case and begin in column 1 and should not be surrounded by single quotes. The keywords and data that follow them can appear in any order in the options file. The end of each table is delimited by the same keyword string prefixed with the characters ENDOF. Comments, identified by an ! in column one, can be placed anywhere between the two keyword strings which delimit 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. The general form for tables is: TABLE_KEYWORD n1, n2, c1, n3, ... !here is a comment . !here is another comment . m1, m2, cm, m3, ... ENDOF TABLE_KEYWORD where: TABLE_KEYWORD n1, n2, ... c1 m1, m2, ... cmENDOF TABLE_KEYWORD is the table keyword are numbers in the first table entry is a character string in the first entry are numbers in the last table entry is a character string in the last entry defines the end of the table
6.2 Options File Keywords __________________________________________________________________________________________________________________________________________________

The options file keywords include: INTERGRAPH OPTIONS BLOCK VENDOR NAME CODE NAME OF CODE PARAMETER DATA TABLE LOADING DATA (LOAD) TABLE SERVICE LOADING (LSET) TABLE ELEMENT CONNECTIVITY MAP TABLE ELEMENT PROPERTY / CONNECTIVITY TABLE END PREPARATION TABLE FITTING NOMENCLATURE TABLE HANGER TYPE TABLE
6.2.1 INTERGRAPH OPTIONS BLOCK __________________________________________________________________________________________________________________________________________________

The Intergraph Options Block is a group of options that directly controlling the actions of the stress analysis interface. The specific meaning of each option is outlined below: Word 1 2 Value val val Meaning Initial (first) node number for nodes generated at component connections Increment to be used in generating subsequent node numbers - starting from the value specified in word 1 Initial node number for numbering nodes at network endpoints Initial node number for numbering nodes internal to components (for example, the nodes at elbow origins) Turn warning messages off Turn warning messages on Magnitude of spring constant indicating a support is rigid - where val implies a magnitude of 10**val must be set to 1 must be set to 1 not used at this time must be set to 1 must be set to 1
3 4
val val
0 1 val
7 8 9 10 11
1 1 0 1 1
6-4
12
0 1 2 3
Extracts the network by substring of the pipeline name attribute (table 12, column 2) Extracts the network by stress analysis ID attribute (table 12, column 52) Extracts the network by equality of the pipeline name attribute (table 12, column 2) Extracts the network by equality of the stress analysis ID attribute (table 12, column 52) Does not print the UNITS record containing the length and weight units of the neutral file Prints the UNITS record in the neutral file Model file component connectivity tolerance in uors Does not print the VERSION record containing the stress interface file format version number Prints the VERSION record in the neutral file Does not print the VENDOR record containing the pipe stress vendors name Prints the VENDOR record in the neutral file Do not generate thermal movement for nozzles. Generate a record indicating the normal XYZ and alternate XYZ thermal growth of nozzles. (Refer to the equipment schema table 22 columns 19 through 24 for more information)
13
0 1
14 15
20 0
1 16 0 1 17 0 1
6.2.2 VENDOR NAME __________________________________________________________________________________________________________________________________________________

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

The files table contains the names of external files used by the stress analysis interface. Use 40 characters maximum for each file name. The entries in this table are order dependent.
6.2.3.1 PDS to Stress Symbol Map __________________________________________________________________________________________________________________________________________________

This table maps PDS component names to generic stress analysis components. This library is required and must be specified. Refer to the PDS to Stress Analysis Symbol Map for more information on the format and contents of the table.
6.2.4 CODE NAME OF CODE PARAMETER DATA TABLE __________________________________________________________________________________________________________________________________________________

This table is used to associate a text string with each value of the segment design code attribute. When the neutral file is generated, this table is entered with the value held in table 12, column 53. If a match is found, the text string from the table is put in the neutral file CODE record. If no match is found, the code list text is placed in the record. The format of an entry in this table is:
VAL, STRING
where: VAL STRING is the code list value from table 12, column 53 is a text string defining the code description, year and seismic level
6.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 the record. You can not change this number or its position in the record. subscript of the lowest temperature, pressure pair subscript of the highest temperature, pressure pair table, column pair identifying the column for obtaining a pressure from the database table, column pair identifying the column for obtaining a temperature from the database
I J PATT(n)
TATT(n)
Example The table entries below define six different pressure, temperature pairs taken from the database and written to the neutral file for each segment in the piping network: -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
6-6
The first table entry defines pairs 1 through 3. The second entry defines pairs 4 through 6.
6.2.6 SERVICE LOADING (LSET) TABLE __________________________________________________________________________________________________________________________________________________

This table is used to identify the pressure/temperature pairs used from each segment for analysis under deadweight, hot conditions, cold conditions, and wind loading conditions. This table allows you to specify the T,P pair used under each of the analysis conditions for each segment. The simplest case uses the same T,P from each segment for each of the different analysis conditions. A more complicated situation is also allowed where some segment attribute dictates that a given set of P,T pairs should be used for that specific segment. 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 with VAL. The first table entry contains 0,0 for this item. This defines the default set of T,P pairs to be used. If there are no other table entries, the same T,P pairs will be used from each segment for all analysis conditions. set to 1 if VAL is a code list number set to 0 if VAL is not a code list number value of the database attribute triggering use of the following T,P pairs for a segment Pressure, temperature pair for deadweight analysis of this segment Pressure, temperature pair for hot condition analysis of this segment Pressure, temperature pair for cold condition analysis of this segment Pressure, temperature pair for wind analysis of this segment
FLAG
VAL
DW HOT COLD WIND Example
The following table entries indicate the default P,T pairs be 1, 2, 3 and 4. However, when the fluid code of a segment is HF, the pairs 1, 2, 5, and 6 should be used instead. 0, 0, 0, 0, 1, 2, 3, 4 12, 9, 0, HF,1, 2, 5, 6
6.2.7 ELEMENT CONNECTIVITY MAP TABLE __________________________________________________________________________________________________________________________________________________

This table provides information about each stress analysis generic component. There is one entry in this table for each generic stress analysis component used in the PDS to stress analysis symbol map. The format of an element in this table is:
NAME, CAT, NODES, ONODE
where: NAME CAT generic component name generic component category. Use one of the following values for category: 1 2 3 NODES ONODE simple component valve support
number of nodes the component generates. defines which node in the node list is the origin node. If this item is 0, then no node will be generated for the component origin. This item should always be set so that origin nodes appear in the node list after nodes at connect points.
Example Consider the example: EL, 1, 3, 3 In this example the generic item EL is classed as a simple component. It has three nodes. The node corresponding to the component center will be the third node in the node list on the overall component record.
6.2.8 ELEMENT PROPERTY / CONNECTIVITY TABLE __________________________________________________________________________________________________________________________________________________

This table forms the overall component records in the neutral file forms the PROP records containing component properties. When the interface generates the records for a component, it first gathers all the entries in 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
6-8
where: NAME generic component name obtained from the PDS to stress analysis symbol map number identifying the component type. You should use one of the following: 1 2 3 4 PDS component is a component or engineered item PDS component is a pipe PDS component is an instrument PDS component is a pipe support
PDSTYP
When a generic pipe stress component can be generated from either a component or an instrument in the model, there must be a set of entries in this table for each type. -1 special flag indicating to the interface that the record will contain a component ID. This table entry must be set to -1. data list format number. This number together with the generic component name allows you to identify all of the data on a particular record. The Intergraph options file contains form numbers adhering to the following convention: 0 1 2 3 4 5 6 ATTLST element connectivity (the overall component rcd) general component data specific component data connect point 1 data connect point 2 data connect point 3 data connect point 4 data
FORMNO
list of table, column pairs specifying columns from which to obtain values to insert in output records. The table, column pairs can specify either segment or component level columns. The entity specified in an table, column pair must correspond to the PDSTYP of the table entry. You can also specify one of the following special table, column pairs to map a composite column in the output record. 0, 0 0,-1 0,-2 0,-3 0,-4 0,-5 0,-6 0,-7 0,-8 0,-9 insert a blank field into the record unique component ID special label formed by concatenating the commodity code, size and schedule attributes insulation unit weight (pipe only) insulation weight (components and instruments only) component or pipe thickness. unique segment ID fitting type from the FITTING NOMENCLATURE TABLE flare radius, large end (reducer only) large end cylinder length (reducer only)
0,10 0,11 0,12 0,13 0,14 0,15 0,16 0,17 0,18 0,19 0,20 0,21 0,22 0,23 Example
flare radius, small end (reducer only) small end cylinder length (reducer only) cone angle (reducer only) pad angle (reinforced tee only) unique analysis code ID (pointer to a CODE record) valve type from the PDS to stress analysis symbol map (valves only) valve angle (valves only) hanger type from the HANGER TYPE TABLE local coordinate system primary axis for a pipe support local coordinate system secondary axis for a pipe support end prep code from END PREPARATION TABLE segment length (miter elbow only) dry unit weight (pipe only) wet unit weight (pipe only)
The following table entries define the contents of the overall component record and each of the PROP records. EL, 1, -1, 0, 0,-2, 3,3, 0,-14 Elbows are mapped to the generic component name EL. The PDS elbow types are component, hence PDSTYP is set to 1. For the overall component record, the form type is 0. Attributes mapped into the overall component record include: special label (0,-2) component tag (3,3) the pointer to a CODE record. The node list is appended to the end of the record. EL, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4 This table entry for form 1 is different from the entry for the overall component record only in the form number and the attribute pairs list. This form 1 entry includes the following attributes: material code (34,18)
6 - 10
dry weight (34,26) wet weight (34,27) stress intensification (34,42) iso drawing reference (4,8) fitting type (0,-7) insulation weight (0,-4) EL, 1, -1, 2, 34,19, 34,20, 34,30, 0,-21 This form 2 entry contains the following data: bend radius (34,19) bend angle (34,20) number of mitre joints (34,30) mitre segment length (0,-21) EL, 1, -1, 34, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6 EL, 1, -1, 4, 34,16, 34,63, 0,-20, 0,-5, 34,66, 0,-6 These entries for forms 3 and 4 (corresponding to connect points 1 and 2) contain the following data: npd (34,49 and 34,16) outside diameter (34,50 and 34,63) end prep code (0,-20) wall thickness (0,-5) pressure rating (34,53 and 34,66) segment ID (0,-6)
6.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 from the model database. The format of an entry in this table is:
GENTYP, TEXT
where:
GENTYP TEXT
generic termination type for an end prep two character max string identifying the end prep. This text string should be identifiable by the pipe stress software you want to use.
6.2.10 FITTING NOMENCLATURE TABLE __________________________________________________________________________________________________________________________________________________

This table allows you to assign a fitting type number to a specific component based upon the commodity code of the fitting. If no commodity code in the table matches that of the component, the first entry in the table is used for 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. stress analysis fitting code
CTYPE
6.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 support type attribute (entity 8, attribute 3). The format of an entry in this table is:
PDSCODE, STYPE
where: PDSCODE STYPE the PDS code number identifying the support type support type number recognized by your stress analysis software
6 - 12
6.3 Example Options File __________________________________________________________________________________________________________________________________________________

!note: ! ! ! general rules (1) upper case words are reserved words. (2) all data should be separated by commas (3) exclamation ! for comments; tab, spaces are accepted between tables
INTERGRAPH OPTIONS BLOCK !note: Maximum 45 options 1, 1, 901, 951, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ENDOF INTERGRAPH OPTIONS BLOCK
6, 0, 0,
1, 0, 0,
1, 0, 0,
1, 0, 0,
1, 0, 0,
1, 0, 0,
0, 0, 0,
0, 0, 0,
20, 0, 0,
0, 0, 999
VENDOR NAME !note: 40 characters maximum for vendor name INTERGRAPH ENDOF VENDOR NAME EXTERNAL FILES !note: maximum 5 files, 40 characters maximum for each file ! 1234567890123456789012345678901234567890 /usr/ip32/pdstress/dat/pdsstress.tbl !PDS TO STRESS MAP ENDOF EXTERNAL FILES CODE NAME OF CODE PARAMETER DATA TABLE !note: 50 codes maximum. default (0) to B31.1 1983. maximum 20 characters (type//year//level) for each code !attribute (12,35) is table input !2345678901234567890 0, B31.1,1983 !default 1, B31.3 2, B31.4 3, ASME1 4, ASME2,1972,A 5, ASME2,1972,B 6, ASME2,1972,C 7, ASME2,1972,D 8, ASME2,1974,A 9, ASME2,1974,B 10, ASME2,1974,C 11, ASME2,1974,D 12, ASME2,1977,A 13, ASME2,1977,B 14, ASME2,1977,C 15, ASME2,1977,D 16, ASME2,1980,A 17, ASME2,1980,B 18, ASME2,1980,C 19, ASME2,1980,D 20, ASME2,1982,A 21, ASME2,1982,B 22, ASME2,1982,C 23, ASME2,1982,D 24, ASME3,1972 25, ASME3,1977 26, ASME3,1980 27, ASME3,1982 28, B31.1,1973 29, B31.1,1977 30, B31.1,1980 31, B31.1,1983 32, BS806 50, BS3351 ENDOF CODE NAME OF CODE PARAMETER DATA TABLE LOADING DATA (LOAD) TABLE !a.: Intergraph segment id !b.: table entry number for first set of pressure/temperature pairs !c.: table entry number for last set of pressure/temperature pairs !d., f., h.: pressure !e., g., i.: temperature ! 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 ENDOF LOADING DATA (LOAD) TABLE
SERVICE LOADING (LSET) TABLE !note: 50 maximum service loading pair !a.: DDL pair to fetch service loading code. !b.: flag. =0, c. is code list no.; =1, c. is code list text !b.: code list. 16 characters maximum. DEFAULT as default. !c.: deadweight condition pair number from loading data !d.: design temperature condition pair number from loading data !e.: room temperature pair number from loading data !f.: wind loading condition pair number from loading data ! a. b. c. d. e. f. g. !234567890123456 0,0, 0, 0, 3, 6, 5, 3 !default 12,9, 0, 1, 1, 2, 3, 4 12,9, 1, VAL, 3, 6, 5, 3 12,9, 1, FC, 1, 2, 3, 4 12,9, 1, OWS, 3, 4, 5, 6 12,9, 1, 8, 3, 4, 5, 1 12,9, 0, 8, 3, 4, 5, 2 ENDOF SERVICE LOADING (LSET) 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 generated) ! a. b. c. d. 3W, 2, 4, 4 4W, 2, 5, 5 AV, 2, 3, 3 CR, 1, 5, 5 EL, 1, 3, 3 ER, 1, 2, 0 FL, 1, 2, 0 HA, 3, 2, 0 MT, 1, 3, 3 PI, 1, 2, 0 RB, 1, 2, 0 RD, 1, 2, 0 RI, 1, 3, 3 TE, 1, 4, 4 TF, 1, 2, 0 VA, 2, 3, 3 ENDOF ELEMENT CONNECTIVITY MAP TABLE ELEMENT PROPERTY / CONNECTIVITY TABLE !note: (1) for this table, generic name, component type, and form type are used to form the unique key to distinguish each record. ! records can be arbitrary order. ! (2) for ddl pair: (0,0) means dummy, no value; (0,-n) means reserved by PDSSTRESS interface system, where n = 1, ... ! (3) maximum 15 ddl pairs (including user defined ddls) for each table entry ! !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 (TE, TF) !(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 TABLE will 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) ! !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
6 - 14
!g.: code name of code parameter ! a. b. c. d. e. f. PI, 2, -1, 0, 0,-2, 50,2, !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. PI, 2, -1, 1, 50,21, 0,-22, !e.: OD nominal !f.: OD !g.: end prep code. !h.: thickness !i.: pressure rating !j.: segment id ! a. b. c. d. e. f. ! gn type occ form npd od PI, 2, -1, 3, 50,7, 50,8, PI, 2, -1, 4, 50,7, 50,8, RI, RI, RI, RI, RB, ! RB, RB, RB, 1, 1, 1, -1, -1, -1, 1, 3, 4, 34,18, 34,49, 34,62, 34,26, 34,50, 34,63, 1, 1, 1, 1, 1, -1, -1, -1, -1, -1, 0, 1, 3, 4, 0, 0,-2, 34,18, 34,49, 34,62, 0,-2, 34,2, 34,26, 34,50, 34,63, 34,2,
g. 0,-14,
h. i. j. !here for user defined DDLs
g. h. 0,-23, 0,0,
i. 50,32,
j. 0,0,
k. 0,-3
g. h. endP thick 0,-20, 0,-5, 0,-20, 0,-5, 0,-14, 34,27, 0,-20, 0,-20, 0,-14,
i. rating 50,11, 50,11,
seg id 0,-6 0,-6
!here for user defined DDLs 34,42, 34,37, 34,19, 0,-3 0,-5, 34,53, 0,-6 0,-5, 34,66, 0,-6
!here for user defined DDLs fitting insulW 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6
! for instrument RB, 3, -1, RB, 3, -1, RB, 3, -1, RB, 3, -1, EL, EL, EL, EL, EL, MT, MT, MT, MT, MT, TE, TE, TE, TE, TE, TE, TF, TF, TF, TF, TF, RD, RD, RD, RD, RD, ER, ER, ER, ER, ER, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
0, 1, 3, 4, 0, 1, 2, 3, 4, 0, 1, 2, 3, 4, 0, 1, 2, 3, 4, 5, 0, 1, 2, 3, 4, 0, 1, 2, 3, 4, 0, 1, 2, 3, 4,
0,-2, 67,15, 67,55, 67,68, 0,-2, 34,18, !bRad 34,19, !npd 34,49, 34,62, 0,-2, 34,18, 34,19, 34,49, 34,62,
67,2, 67,21, 67,56, 67,69, 34,2, 34,26, bAng 34,20, od 34,50, 34,63, 34,2, 34,26, 34,20, 34,50, 34,63,
0,-14, !here for user defined DDLs 67,22, 67,48, 67,43, 0,-7, 0,-4 0,-20, 0,-5, 67,59, 0,-6 0,-20, 0,-5, 67,72, 0,-6 0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 miterJ miterL 34,30, 0,-21 endP thick rating seg id 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6 0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 34,30, 0,-21 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6
0,-2, 34,2, 0,-14, !here for user defined DDLs 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4 !rThick pad ang pad len 34,19, 0,-13, 34,20 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6 0,-2, 34,18, 34,19, 34,49, 34,62, 0,-2, 34,18, 0,-8, 34,49, 34,62, 0,-2, 34,18, 0,-8, 34,49, 34,62, 34,2, 34,26, 0,-13, 34,50, 34,63, 34,2, 34,26, 0,-9, 34,50, 34,63, 34,2, 34,26, 0,-9, 34,50, 34,63, 0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 34,20 34,51, 0,-5, 34,53, 0,-6 34,64, 0,-5, 34,66, 0,-6 0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-10, 0,-11, 0,-12 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6 0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-10, 0,-11, 0,-12 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6
FL, FL, FL, FL, VA, VA, VA, VA, VA,
1, 1, 1, 1, 1, 1, 1, 1, 1,
-1, -1, -1, -1, -1, -1, -1, -1, -1,
0, 1, 3, 4, 0, 1, 2, 3, 4,
0,-2, 34,18, 34,49, 34,62, 0,-2, 34,18, 34,28, 34,49, 34,62,
34,2, 34,26, 34,50, 34,63,
0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6
34,2, 0,-14, !here for user defined DDLs 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-15, 0,-16 34,50, 0,-20, 0,-5, 34,53, 0,-6 34,63, 0,-20, 0,-5, 34,66, 0,-6
! for instrument VA, 3, -1, VA, 3, -1, VA, 3, -1, VA, 3, -1, VA, 3, -1, AV, AV, AV, AV, AV, 1, 1, 1, 1, 1, -1, -1, -1, -1, -1,
0, 1, 2, 3, 4, 0, 1, 2, 3, 4,
0,-2, 67,15, 67,23, 67,55, 67,68, 0,-2, 34,18, 34,28, 34,49, 34,62,
67,2, 0,-14, !here for user defined DDLs 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4 0,-15, 0,-16 67,56, 0,-20, 0,-5, 67,59, 0,-6 67,69, 0,-20, 0,-5, 67,72, 0,-6 34,2, 0,-14, !here for user defined DDLs 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-15, 0,-16 34,50, 0,-20, 0,-5, 34,53, 0,-6 34,63, 0,-20, 0,-5, 34,66, 0,-6
! for instrument AV, 3, -1, AV, 3, -1, AV, 3, -1, AV, 3, -1, AV, 3, -1, CR, CR, CR, CR, CR, CR, 3W, 3W, 3W, 3W, 3W, 3W, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1,
0, 1, 2, 3, 4, 0, 1, 3, 4, 5, 6, 0, 1, 2, 3, 4, 5,
0,-2, 67,15, 67,23, 67,55, 67,68, 0,-2, 34,18, 34,49, 34,62, 34,75, 34,88, 0,-2, 34,18, 34,28, 34,49, 34,62, 34,75,
67,2, 0,-14, !here for user defined DDLs 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4 0,-15, 0,-16 67,56, 0,-20, 0,-5, 67,59, 0,-6 67,69, 0,-20, 0,-5, 67,72, 0,-6 34,2, 34,26, 34,50, 34,63, 34,76, 34,89, 0,-14, !here for user defined DDLs 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-20, 0,-5, 34,53, 0,-6 0,-20, 0,-5, 34,66, 0,-6 0,-20, 0,-5, 34,79, 0,-6 0,-20, 0,-5, 34,92, 0,-6
34,2, 0,-14, !here for user defined DDLs 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-15, 0,-16 34,50, 0,-20, 0,-5, 34,53, 0,-6 34,63, 0,-20, 0,-5, 34,66, 0,-6 34,76, 0,-20, 0,-5, 34,79, 0,-6
! for instrument 3W, 3, -1, 3W, 3, -1, 3W, 3, -1, 3W, 3, -1, 3W, 3, -1, 3W, 3, -1, 4W, 4W, 4W, 4W, 4W, 4W, 4W, 1, 1, 1, 1, 1, 1, 1, -1, -1, -1, -1, -1, -1, -1,
0, 1, 2, 3, 4, 5, 0, 1, 2, 3, 4, 5, 6,
0,-2, 67,15, 67,23, 67,55, 67,68, 67,81, 0,-2, 34,18, 34,28, 34,49, 34,62, 34,75, 34,88,
67,2, 0,-14, !here for user defined DDLs 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4 0,-15, 0,-16 67,56, 0,-20, 0,-5, 67,59, 0,-6 67,69, 0,-20, 0,-5, 67,72, 0,-6 67,82, 0,-20, 0,-5, 67,85, 0,-6 34,2, 0,-14, !here for user defined DDLs 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4 0,-15, 0,-16 34,50, 0,-20, 0,-5, 34,53, 0,-6 34,63, 0,-20, 0,-5, 34,66, 0,-6 34,76, 0,-20, 0,-5, 34,79, 0,-6 34,89, 0,-20, 0,-5, 34,92, 0,-6
! for instrument 4W, 3, -1, 4W, 3, -1, 4W, 3, -1, 4W, 3, -1, 4W, 3, -1, 4W, 3, -1, 4W, 3, -1, !support HA, 4, HA, HA, ! HA, 4, -1, 4, 4,
0, 1, 2, 3, 4, 5, 6,
0,-2, 67,15, 67,23, 67,55, 67,68, 67,81, 67,94,
67,2, 0,-14, !here for user defined DDLs 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4 0,-15, 0,-16 67,56, 0,-20, 0,-5, 67,59, 0,-6 67,69, 0,-20, 0,-5, 67,72, 0,-6 67,82, 0,-20, 0,-5, 67,85, 0,-6 67,95, 0,-20, 0,-5, 67,98, 0,-6
-1, -1, -1,
0, 1, 2, 4,
0,-2, 80,2, 0,-14, !matl weight H type 0,0, 80,15, 0,-17, !k1 k2 k3 80,28, 80,29, 80,30, local x local y 0,-18, 0,-19
!here for user defined DDLs sym id 80,19 kp1 kp2 kp3 (this 6 positions are fixed to test node restrain) 80,31, 80,32, 80,33
ENDOF ELEMENT PROPERTY / CONNECTIVITY TABLE
6 - 16
END PREPARATION TABLE !note: maximum 2 character for end prep. 0, BW !default 20, WN !flange 80, LJ !lap joint 300, BW !butt weld, as welded 310, FL !butt weld, flush 390, PL !plain end 420, SO !socket fitting 440, SP !screwed pipe joint ENDOF END PREPARATION TABLE FITTING NOMENCLATURE TABLE !note: default to 0, if corresponding commodity code NOT found from here ! maximum 16 characters for commodity code, 200 maximum codes !234567890123456 DEFAULT, 0 !default PAAAABBAAA, 2 WRAAABBAAA, 4 WAAAABBAAA, 23 LSBZZZZAAA, 21 VABBAALYAA, 19 WOAAABBAFA, 20 WAAAABBASA, 21 VBBWAAOHAA, 25 FAABBBBAAA, 18 FCV123, 17 VCBWAANHAA, 16 WOAAABBAAA, 15 VCABAAYYAA, 14 ENDOF FITTING NOMENCLATURE TABLE HANGER TYPE TABLE !note: default to 99, if corresponding DDL value NOT found from here. !a.: data base (DDL) attribute value (80,5) !b.: hanger type ! a. b. 0, 99 1, 99 135, 99 ENDOF HANGER TYPE TABLE
50 ddl values maximum.
PDS to Stress Analysis Symbol Map 7 - 1
7. PDS to Stress Analysis Symbol Map
__________________________________________________________________________________________________________________________________________________
The PDS to Stress Analysis Symbol Map is used to map each PDS component to a generic stress analysis component. The table itself is composed of three columns of data that are position dependent. You can add comments to the table by placing an ! in column 1. A table entry consists of one row of data. Each column in a row is discussed below. 1. PDS Item Name The PDS item name is the index into the table. Each PDS item existing in a pipeline must have an entry for it in this table. As a component is processed, this table is searched for an entry for the current component. Only the first 4 characters of the item name are used by the symbol map. 2. Stress Analysis Generic Name The STRESS symbol name is the primary output from this table. The symbol names are two characters in length. The Intergraph default generic names include: 3W 3-WAY VALVES 4W 4-WAY VALVES AV ANGLE VALVES CR CROSSES EL ELBOWS and MITERS ER ECCENTRIC REDUCERS FL FLANGES FX</TA>EXPANSION JOINTS HA PIPE SUPPORTS and HANGERS PI PIPE RB RIGID BODIES RD CONCENTRIC REDUCERS RI BENT PIPE TE TEES TF OLETS and BRANCH WELDS VA INLINE VALVES 3. Valve Type Descriptor Another output from this table is a valve type used for valves only. You can map the valve type into a PROP record. (Refer to the Defaults File section for more information.)
7-2
7.1 Example Component Map __________________________________________________________________________________________________________________________________________________

! !a.: item name. only the first 4 characters are used !b.: generic name. maximum 2 characters !c.: type descriptor (for VA, AV, 3W only), maximum 4 character !a. b. c. !234567890123456789 1BF1 1BL1 1BL3W1 1CKAR1 1D1 1GL1 1GL3W1 1KNF1 1PL1 1PL3W1 1S1 1SA1 2PRD1 2PRVA1 3OP1 3UNO1 3VFDR1 3VFDV1 3VFUR1 3VFUV1 4BOX 4BOX3 4BOX4 4CYL 4CYL3 BAL3W BALF BALLP BALR BALSP BDA BDY BFY BFYHP BFYLP BLSPO BUSH CAPBV CAPOT CKAL CKALSP CKAR B CKAST CKBP CKL CKLF CKLR CKLSP CKS CKSF RB RB TE 3W RB RB TE RB RB TE RB RB RB RB RB RB RB RB RB RB RB RB RB RB TE 3W VA VA VA VA VA VA VA VA VA RB RB RB RB AV AV 3W AV VA VA VA VA VA VA VA
***
*** BAL BAL BAL BAL GLA *** BFL BFL BFL
*** *** *** *** CKE CKE CKE CKE CKE CKE CKE
CKSR CKSSP CKST CKSY COMP CKYST CONV CPD04 CPD05 CPD07 CPD10 CPL CPLH CPLR CRO DEL DIA DIAGL DIAPL DIASP E45 E453D E45L E45LR E45S E45ST E45T E45T3D E45TLR E45U E90 E90LR E90R E90SR E90T E90T3D E90TLR E90U EOLLR EOLSR FBLD FFIL FL FLO FLRSC FLSL FLSSO FLSW FLWN FOOT FOSOA FOSOAW FOSOB FOSOBW FOSWA FOSWAW FOSWB FOSWBW FOTHDA FOWNA FOWNAW FOWNB FOWNBW FPL FTHD
VA VA VA VA VA VA VA XX XX XX XX XX XX XX CR VA VA VA VA VA EL EL EL EL EL EL EL EL EL EL EL EL EL EL EL EL EL EL TF TF RB FL FL VA FL FL FL FL FL VA FL FL FL FL FL FL FL FL FL FL FL FL FL FL FL
CKE CKE CKE CKE CKE CKE CKE
GTE PLG PLG PLG PLG
GTE
***
7-4
FSO FSSL FSSPL FS FSW COMP COMP COMPF COMPBL COMPCON COMPEX COMPEXB COMPR COMPSP GLO GLO3W GLOA GLOASP GLOF GLOR GLOSP GLOY GLOYF GLOYR HD21 HDHEMI HOP HOS HOSA I2WAY IGEN01 IGEN02 IGEN03 IGEN04 IGEN05 KNF LOL NEE NIP NIPL NOL NOZ PIN PIPB PIPE PLU PLU3W PLU4W PLUFB PLUF PLUR PLUSP PLUVP PS1 PS3 PS5 PS15 PS19 R180 R180CL R180MD R180LR R180OP R180SR REDC
FL FL FL FL FL FL VA VA VA VA VA VA VA VA VA 3W AV AV VA VA VA VA VA VA RB RB XX VA AV RB RB RB TE RB RB VA TF VA PI PI TF HA VA RI PI VA 3W 4W VA VA VA VA VA HA HA HA HA HA EL EL EL EL EL EL RD
GTE GTE GTE GTE GTE GTE GTE GTE PMD *** GLV GLV PMD PMD PMD *** *** ***
*** ***
*** GTE
PLG
PLG 3W 4W PLG PLG PLG PLG PLG
REDC3 REDE RELVAL RWELD SLI SLI3W SOL SOP SPRTA STRB1 STUB SWGC T TKDR TOL TRB TRI TRRB TST TUOB UN UND UNO WOL B X XRB Y
RD ER AV TF VA 3W TF XX HA RB TF RD TE VA TF TE TE TE TE TE RB RB RB TF CR CR TE
*** GTE ***
GTE
7-6
Appendix A: Warning & Error Messages A - 1
Appendix A
__________________________________________________________________________________________________________________________________________________
Warning & Error Messages
A-2
Appendix A
__________________________________________________________________________________________________________________________________________________
Warning & Error Messages

This section lists the warning and error messages issued by the various components of the stress analysis software and, when possible, suggests a corrective action. The messages that are issued by the PD_Stress Analysis Interface are recorded in an error message file along with the neutral file when errors occur. If no errors occur, an error file is not created. There are two categories of messages issued by the software: A Warning message indicates an error occurred which may cause a problem in the neutral file. The neutral file should be checked. An Error message indicates an error occurred and is serious enough to cause extraction to abort. The neutral file is either not produced or incomplete.
A-4
A.1 Warning Messages __________________________________________________________________________________________________________________________________________________

Message # W1 Message/Comment Reuse counter mismatch The reuse counter stored in the design file does not match that stored in the database. This is potentially a serious problem that could indicate that components in the model are linked to incorrect database records. It is strongly recommended that the model be analyzed to determine the extent of the problem and to correct the situation. W2 Standard note not found, default value used This message indicates there was no note for the code list numbers and a blank (" ") was used. This can be fixed by placing a valid note into the Standard Note Library for that code list number. W3 Unable to locate stress code, default code used This message means there was no match in the CODE NAME OF CODE PARAMETER DATA TABLE in the defaults file for the design_code_requirements attribute for the segment currently being extracted. The first record in the table was used instead. W4 Unable to locate end prep, default end prep used This message means there was no match in the END PREPARATION TABLE in the defaults file for the component which is currently being processed. The first record in the table was used to generate the end prep code. W5 Component has undefined commodity code This message indicates that the current component or pipe does not have a commodity code and a blank was used. W6 Unable to locate fitting type, default fitting type used This message means there was no match in the FITTING NOMENCLATURE TABLE in the defaults file for the commodity code of the current component. W7 Nominal piping diameter has been truncated The text string generated from the nominal piping diameter has exceeded the maximum size allowed in the software and was truncated. Contact Intergraph.
W8
Unable to locate hanger type, default hanger type used This means there was no match in the HANGER TYPE TABLE of the defaults file for the pipe_support_type attribute of the current pipe support/hanger and the first entry of the table was used.
W9
Reducer size table not found, default values used This means there was no reducer size table found in the commodity library and default values were used for flare radius, length and cone angle. This can be fixed by modifying the RD_SIZE.TBL in the /usr/ip32/pdstress/dat directory to contain the needed information and place it into the commodity library.
W10
Wall thickness table not found, default values used This message indicates there was no thickness table found in the commodity library for the current component and zero was used. This message usually occurs on components with schedule thicknesses set to NREQD.
W12
Outside Diameter attribute undefined - Insulation Unit Weight defaulted to 0.0 This means that Insulation Unit Weight can not be calculated because the outside diameter for the component or pipe being processed is undefined in the database. Check all components and pipes in the line being extracted to make sure the outside diameter has a valid value.
W13
Dry Weight attribute undefined - Dry Unit Weight defaulted to 0.0 This means that the dry weight attribute in the database is undefined. Check all components and pipes in the line being extracted to make sure the dry weight has a valid value.
W14
Wet Weight attribute undefined - Wet Unit Weight defaulted to 0.0 This means that the wet weight attribute in the database is undefined. Check all components and pipes in the line being extracted to make sure the wet weight has a valid value.
A-6
A.2 Error Messages __________________________________________________________________________________________________________________________________________________

Message # E1 Message/Comment Error opening error message file - pdsstr.err An error occurred while trying to open the error message file. Check to make sure that the file pdsstr.err is not opened by another user in the default directory. E3 Error opening input data file - PDSSTR.DAT An error occurred while attempting to open the input file to the stress analysis interface. Check to make sure that the file PDSSTR.DAT exists in the default directory. E4 Word 11 in the INTERGRAPH OPTIONS BLOCK is undefined Word 11 in the options block must be set to 1. E5 No model files found in input data file - PDSSTR.DAT An error occurred generating PDSSTR.DAT or the user entered a blank first line in the input data file and no model file names were found. Check to make sure there are valid model file names in PDSSTR.DAT in the default directory. E6 No line names found in input data file - PDSSTR.DAT An error occurred generating PDSSTR.DAT or the user entered two blank lines between the last model file name and the first line name. Check to make sure there is only one blank line between the last model file name and the first line name in PDSSTR.DAT in the default directory. E7 Word 12 in the INTERGRAPH OPTIONS BLOCK is undefined Word 12 in the options block must be set to 1. E8 E9 Error opening stress options file Fatal SEQUENCER error An error occurred while organizing the design file components. Check the model design file to verify that the pipeline being extracted is free of modeling errors. If the pipeline is correct, contact Intergraph. E10 Error reading input data file - PDSSTR.DAT
An error occurred reading information from the input data file. Check the record format of the input data file PDSSTR.DAT in the default directory. E11 E15 Logical name STRESSOPTION is undefined or file does not exist Number of connect points exceeded internal limit of 2000 connect points. The maximum number of connect points per extraction is 2000. Break the line into two separate line names and re-extract the line as two separate isometrics. E16 Error reading FORM type from defaults file An error occurred reading in the FORM type from a record in the ELEMENT PROPERTY / CONNECTIVITY TABLE section of the defaults file. Valid values for form type are 0-6. For more information on property and connectivity record refer to the Defaults File section. E17 Error reading database occurrence An error occurred in trying to read a record from the database on a design file linkage. This error indicates potentially serious problems in the model. It is strongly recommended that the model be analyzed to determine the extent of the problem and to correct the situation. E18 Error retrieving DDL pair This message means that an error occurred trying to read an attribute from the database. Check the database DDL to make sure the DDL pair in question consists of a valid entity and attribute number. E19 Error retrieving DDL table An undefined entity number has been read in from either the LOADING DATA (LOAD) TABLE, the SERVICE LOADING (LSET) TABLE or the ELEMENT PROPERTY / CONNECTIVITY TABLE in the defaults file. Check to make sure only valid entity numbers are used in the DDL pairs section of the above tables. E20 Error writing CODE record An error occurred while trying to write a CODE record to the STRESS ANALYSIS neutral file. E21 Error converting Segment occurrence number from decimal to hex An error occurred while trying to convert a Segment occurrence number from decimal format into a hexadecimal format. Contact Intergraph. E22 Error writing header information into neutral file
A-8
An error occurred while trying to write the header records to the beginning of the stress analysis neutral file. E23 Error writing DRAW record An error occurred while trying to write a DRAW record to the stress analysis neutral file. E24 Error converting nominal piping diameter This message means there was an error trying to convert the nominal piping diameter from the database format to an ASCII format. Contact Intergraph. E25 E26 Error loading record from options file Invalid table for Insulation Weight An error occurred trying to retrieve insulation weight for a table which does not have an insulation weight attribute. Verify that the DDL pair "0,-3" or "0,-4" is not in any of the pipe support/hanger records in the ELEMENT PROPERTY / CONNECTIVITY TABLE section of the defaults file. E27 End node number is too small for current line An error occurred trying to assign an end node number to the current line being extracted. This can be fixed by increasing the end node number (word 3) of the INTERGRAPH OPTIONS BLOCK section of the defaults file. E28 Internal table limits exceeded for PDS to STRESS map The internal table size for the PDS to STRESS map has reached its limits and the remainder of the map can not be stored. Reduce the number of records in the PDS to STRESS map. Contact Intergraph for information about increasing the maximum table size. E29 Error initializing spec table access information An error occurred while trying to open and initialize the piping job specification tables. Check the project files to make sure they exist and you have read access to them. E30 Error reading record from options file An error occurred while trying to read a record from the options file. Check the bad record to make sure it is in the proper format. E31 Error opening neutral file An error occurred while trying to open the stress analysis output neutral file. E34 Error writing LNOD record
An error occurred trying to write a LNOD record to the stress analysis neutral file. E35 Error searching for PDS item name in PDS to stress analysis symbol map An error occurred searching for PDS item name in the PDS to stress analysis symbol map. Check to make sure the PDS item name is in the PDS to STRESS table. E36 Undefined generic name in PDS to STRESS map An error occurred in reading the generic name from the PDS to stress analysis symbol map. Check to make sure that the generic name is defined in the table. E37 Error locating PROPERTY/CONNECTIVITY records for generic name An error occurred searching for the PROPERTY / CONNECTIVITY record(s) from the ELEMENT PROPERTY / CONNECTIVITY TABLE section of the defaults file. Check to make sure all the necessary form records are in this table. E38 Error reading standard note library An error occurred while reading the standard note library. Check the standard note library to make sure the standard note exist. E39 Error writing LSET record An error occurred while trying to write a LSET record to the neutral file. E40 Error writing NODE record An error occurred while trying to write a NODE record to the neutral file. E41 Error writing CONNECTIVITY record An error occurred while trying to write a CONNECTIVITY record to the neutral file. E42 Error writing PROPERTY record An error occurred while trying to write a PROPERTY record to the neutral file. E43 Error accessing or opening PDS to STRESS map An error occurred while trying to open the PDS to stress analysis symbol map. Check to make sure the file exists and that you have read access to it.
A - 10
E44
Error reading PDS to STRESS map An error occurred while trying to read a record from the PDS to stress analysis symbol map. Check to make sure the table is in the correct format.
E49
Error writing LOAD record An error occurred while trying to write LOAD record to the neutral file.
E50
Error searching for segment occurrence number An error occurred while searching for the segment occurrence number from the current component. Check the model to make sure that components are owned by the correct segments.
E51
Error accessing wall thickness table An error occurred while accessing information from the wall thickness table. Check the commodity library to make sure the wall thickness table exists.
Appendix B: PDS Design Database Format B - 1
Appendix B
__________________________________________________________________________________________________________________________________________________
PDS Design Database Format
B-2
Appendix B
__________________________________________________________________________________________________________________________________________________
PDS Design Database Format

This section contains a PDS DDL which shows the format of the PDS design database.
# Piping Design Database # Default Relational Database Definition
# Piping Segment Data table number = 12 , number of columns = 72 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , system_unique_no line_number_label line_id unit_number unit_code module_no package_system_no train_number fluid_code line_sequence_no nominal_piping_dia piping_mater_class gasket_separation insulation_purpose insulation_thick insulation_density heat_tracing_reqmt heat_tracing_media heat_tracing_temp construction_stat hold_status approval_status schedule_override nor_oper_pres nor_oper_temp alt_oper_pres alt_oper_temp nor_dgn_pres nor_dgn_temp alt_dgn_pres alt_dgn_temp steam_outlet_temp mater_of_construct safety_class design_standard design_area_number design_resp construction_resp supply_resp coating_reqmts cleaning_reqmts fluid_category nor_op_pres_units , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , integer character(40) character(16) character(12) character(3) character(16) character(12) character(2) short character(16) short character(16) character(8) short double double short short double short short short character(8) double double double double double double double double double character(6) short short character(12) short short short short short character(4) short , index 1
, standard note 125
, standard note 220 , standard note 1074 (units) , standard note 200 , standard note 210 , standard note 130 , standard note 50 , standard note 35
, standard note 340 , standard note 570 , , , , , standard standard standard standard standard note note note note note 160 160 160 190 230
, standard note 1064
B-4
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72
, , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
nor_op_temp_units alt_op_pres_units alt_op_temp_units nor_dgn_pres_units nor_dgn_temp_units alt_dgn_pres_units alt_dgn_temp_units steam_temp_units stress_system_no stress_reqmts hyd_system_no hyd_reqmts specific_gravity_a specific_gravity_b specific_gravity_c viscosity density spec_heat_ratio sonic_velocity surface_roughness test_system_no test_fluid test_pressure PID_id_part_a PID_id_part_b end_1_nozzle_id end_2_nozzle_id alpha_descript_id standard_note_no
, , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
short short short short short short short short character(12) short character(12) short double double double double double double double double character(6) short double character(4) character(4) integer integer character(12) short
, , , , , , , ,
standard standard standard standard standard standard standard standard
note note note note note note note note
1056 1064 1056 1064 1056 1064 1056 1056
, standard note 360 , standard note 360
, standard note 125
, standard note 499
# Piping Component Data table number = 34 , number of columns = 113 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , system_unique_no piping_comp_no commodity_name model_code option_code maximum_temp sched_thick_basis commodity_code MTO_requirements fabrication_cat source_of_data PDS_sort_code physical_data_id geometric_standard weight_code table_suffix_green table_suffix_red materials_grade bend_radius bend_angle face_to_face_dim dimension_a dimension_b dimension_c surface_area empty_weight water_weight operator_weight operator_sym_name chain_operator_no opening_action , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , integer character(20) character(6) character(6) short double character(8) character(16) short short short character(6) character(8) short short short short short double double double double double double double double double double character(6) short short , index 1
, standard note 400
, standard note 365 , standard note 180 , standard note 420
, , , , ,
standard standard standard standard standard
note note note note note
575 578 576 577 145
, standard note 1010 (units) , standard note 1028 (units) , standard note 1028 (units)
, standard note 390
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
construction_stat hold_status heat_tracing_reqmt heat_tracing_media heat_tracing_temp iso_dwg_index_no isometric_sheet_no piece_mark_no color_code stress_node_no stress_intens_fact head_loss_factor piping_assembly component_group_no remarks standard_note_no_a standard_note_no_b cp_1_nom_pipe_diam cp_1_outside_diam cp_1_end_prep cp_1_sch_thk cp_1_rating cp_1_face_to_ctr cp_1_weld_no cp_1_weld_type cp_1_gasket_gap cp_1_gasket_option cp_1_stress_node cp_1_stress_factor cp_1_head_loss cp_2_nom_pipe_diam cp_2_outside_diam cp_2_end_prep cp_2_sch_thk cp_2_rating cp_2_face_to_ctr cp_2_weld_no cp_2_weld_type cp_2_gasket_gap cp_2_gasket_option cp_2_stress_node cp_2_stress_factor cp_2_head_loss cp_3_nom_pipe_diam cp_3_outside_diam cp_3_end_prep cp_3_sch_thk cp_3_rating cp_3_face_to_ctr cp_3_weld_no cp_3_weld_type cp_3_gasket_gap cp_3_gasket_option cp_3_stress_node cp_3_stress_factor cp_3_head_loss cp_4_nom_pipe_diam cp_4_outside_diam cp_4_end_prep cp_4_sch_thk cp_4_rating
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
short short short short double integer character(2) character(10) character(8) short double double character(12) short character(16) short short short double short character(8) character(8) double character(8) short double short short double double short double short character(8) character(8) double character(8) short double short short double double short double short character(8) character(8) double character(8) short double short short double double short double short character(8) character(8)
, , , ,
standard standard standard standard
note note note note
130 50 200 210
, standard note 330
, standard note 1100 / 400 (bolt option) , standard note 400
, standard note 330
, standard note 330
, standard note 330
B-6
93 , 94 , 95 , 96 , 97 , 98 , 99 , 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113,
cp_4_face_to_ctr cp_4_weld_no cp_4_weld_type cp_4_gasket_gap cp_4_gasket_option cp_4_stress_node cp_4_stress_factor cp_4_head_loss cp_5_nom_pipe_diam cp_5_outside_diam cp_5_end_prep cp_5_sch_thk cp_5_rating cp_5_face_to_ctr cp_5_weld_no cp_5_weld_type cp_5_gasket_gap cp_5_gasket_option cp_5_stress_node cp_5_stress_factor cp_5_head_loss
, , , , , , , , , , , , , , , , , , , , ,
double character(8) short double short short double double short double short character(8) character(8) double character(8) short double short short double double
, standard note 330
# Piping/Tubing Data table number = 50 , number of columns = 56 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , system_unique_no piping_comp_no commodity_name model_code option_code maximum_temp nominal_piping_dia outside_diameter schedule_thickness sched_thick_basis rating commodity_code MTO_requirements fabrication_cat source_of_data PDS_sort_code geometric_standard weight_code table_suffix_green table_suffix_red materials_grade pipe_length surface_area empty_weight water_weight cold_spring_length construction_stat hold_status heat_tracing_reqmt heat_tracing_media heat_tracing_temp iso_dwg_index_no isometric_sheet_no piece_mark_no color_code piping_assembly component_group_no remarks , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , integer character(20) character(6) character(6) short double short double character(8) character(8) character(8) character(16) short short short character(6) short short short short short double double double double double short short short short double integer character(2) character(10) character(8) character(12) short character(16) , index 1
, standard note 400
, standard note 365 , standard note 180 , standard note 425 , , , , , standard standard standard standard standard note note note note note 575 578 576 577 145
, standard note 1010 (units) , standard note 1028 (units) , standard note 1028 (units) , , , , standard standard standard standard note note note note 130 50 200 210
39 , standard_note_no_a , short 40 , standard_note_no_b , short 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 , , , , , , , , , , , , , , , , end_1_end_prep end_1_weld_no end_1_weld_type end_1_gasket_gap end_1_gasket_opt end_1_stress_node end_1_stres_int end_1_head_loss end_2_end_prep end_2_weld_no end_2_weld_type end_2_gasket_gap end_2_gasket_opt end_2_stress_node end_2_stres_int end_2_head_loss , , , , , , , , , , , , , , , , short character(8) short double short short double double short character(8) short double short short double double
, standard note 499 , standard note 499 , standard note 330 , standard note 1100 / 400 (bolt option) , standard note 400
, standard note 330 , standard note 1100 / 400 (bolt option) , standard note 400
# Instrument Component Data table number = 67 , number of columns = 119 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , system_unique_no instrument_comp_no model_code option_code sched_thick_basis MTO_requirements fabrication_cat source_of_data PDS_sort_code physical_data_id geometric_standard weight_code table_suffix_green table_suffix_red materials_grade face_to_face_dim dimension_a dimension_b dimension_c surface_area empty_weight water_weight operator_weight operator_type operator_sym_name chain_operator_no chain_length opening_action construction_stat hold_status design_resp construction_resp heat_tracing_reqmt heat_tracing_media heat_tracing_temp insulation_purpose insulation_thick insulation_density cleaning_reqmts safety_class , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , integer character(20) character(6) short character(8) short short short character(6) character(8) short short short short short double double double double double double double double double character(6) short double short short short short short short short double short double double short short , index 1
, standard note 400 , standard note 365 , standard note 180 , standard note 430
, , , , ,
standard standard standard standard standard
note note note note note
575 578 576 577 145
, , , ,
note note note note
1010 1028 1028 1028
(units) (units) (units) (units)
, , , , , , ,
standard standard standard standard standard standard standard
note note note note note note note
390 130 50 160 160 200 210
, standard note 220 , standard note 1074 (units) , standard note 230 , standard note 340
B-8
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
module_no package_system_no iso_dwg_index_no isometric_sheet_no piece_mark_no color_code stress_node_no stress_intens_fact head_loss_factor piping_assembly component_group_no remarks standard_note_no_a standard_note_no_b cp_1_nom_pipe_diam cp_1_outside_diam cp_1_end_prep cp_1_sch_thk cp_1_rating cp_1_face_to_ctr cp_1_weld_no cp_1_weld_type cp_1_gasket_gap cp_1_gasket_option cp_1_stress_node cp_1_stress_factor cp_1_head_loss cp_2_nom_pipe_diam cp_2_outside_diam cp_2_end_prep cp_2_sch_thk cp_2_rating cp_2_face_to_ctr cp_2_weld_no cp_2_weld_type cp_2_gasket_gap cp_2_gasket_option cp_2_stress_node cp_2_stress_factor cp_2_head_loss cp_3_nom_pipe_diam cp_3_outside_diam cp_3_end_prep cp_3_sch_thk cp_3_rating cp_3_face_to_ctr cp_3_weld_no cp_3_weld_type cp_3_gasket_gap cp_3_gasket_option cp_3_stress_node cp_3_stress_factor cp_3_head_loss cp_4_nom_pipe_diam cp_4_outside_diam cp_4_end_prep cp_4_sch_thk cp_4_rating cp_4_face_to_ctr cp_4_weld_no cp_4_weld_type
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
character(16) character(12) integer character(2) character(10) character(8) short double double character(12) short character(16) short short short double short character(8) character(8) double character(8) short double short short double double short double short character(8) character(8) double character(8) short double short short double double short double short character(8) character(8) double character(8) short double short short double double short double short character(8) character(8) double character(8) short
, standard note 330
, standard note 330
, standard note 330
94 , 95 , 96 , 97 , 98 , 99 , 100, 101,
, standard note 330
, standard note 1100 / 400 (bolt option)
102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119,
cp_4_gasket_gap cp_4_gasket_option cp_4_stress_node cp_4_stress_factor cp_4_head_loss cp_5_nom_pipe_diam cp_5_outside_diam cp_5_end_prep cp_5_sch_thk cp_5_rating cp_5_face_to_ctr cp_5_weld_no cp_5_weld_type cp_5_gasket_gap cp_5_gasket_option cp_5_stress_node cp_5_stress_factor cp_5_head_loss
, , , , , , , , , , , , , , , , , ,
double short short double double short double short character(8) character(8) double character(8) short double short short double double
, standard note 400
, standard note 330
# Pipe Support Data table number = 80 , number of columns = 36 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , system_unique_no pipe_support_no model_code_phy model_code_log iso_support_type_a iso_support_type_b iso_support_type_c iso_support_type_d details_for_shop details_for_field fabrication_orient commodity_code MTO_requirements fabrication_cat weight construction_stat hold_status standard_note_no iso_dwg_index_no isometric_sheet_no piece_mark_no color_code isometric_dim_a isometric_dim_b isometric_dim_c isometric_dim_d isometric_dim_e trans_rigidity_x trans_rigidity_y trans_rigidity_z rot_rigidity_x rot_rigidity_y rot_rigidity_z spring_gap_length sping_gap_direct number_of_springs , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , integer character(20) character(6) character(6) short short short short character(50) character(50) character(20) character(16) short short double short short short integer character(2) character(10) character(8) double double double double double double double double double double double double short short , index 1
, , , ,
note note note note
380 380 380 380
, , , , , ,
standard standard standard standard standard standard
note note note note note note
365 180 1028 (units) 130 50 499
B - 10
Glossary GL - 1
Glossary
__________________________________________________________________________________________________________________________________________________
GL - 2
Glossary GL - 3
Glossary
__________________________________________________________________________________________________________________________________________________
absolute path name
The sequence of directories, beginning with the root directory (/) that locates a file. See also path name and relative path name. The plane in a 3-D design upon which you can place elements and perform manipulations. The process which is displayed in the Process ID field; it controls the message fields, the menus, and the keyboard. The active process has a highlighted window icon strip. Software designed to meet specific needs, unlike system software which runs other software. A method of processing data which collects a series of operations into a group (or batch) and executes the group in a continuous stream without user intervention. A queue, or channel for moving requests, created through NQS. A batch queue handles scheduling for processes submitted through the Batch options screen menu. A point on a pipeline which separates piping segments so that they can be assigned different segment parameters. A branch point allows for placement of branch components. The button located in the upper right corner of a form containing a red X or the word cancel. Select the cancel button to exit the form or option. A permanent association of elements that can be stored and placed as a group, and then manipulated as individual elements. A column data type that stores alphanumeric character data. In network operations, a node which accesses data or performs a function on the remote resource (usually a server). All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. An attribute of a database table. A group of columns defines a table in a database. Instructions from the user to perform a function on specified data.
active depth
active process
application software
batch processing
batch queue
branch point
cancel button
cell
character client
column
command
GL - 4
confirm button
A button that appears in the upper right corner of a form and contains a green check mark or the word confirm. Select the confirm button to initiate a specified option. The location of a point along the X, Y, or Z axis. A geometric relation used to denote the location of points in the design cube. The most common coordinate system is the rectangular coordinate system, whereby points are located by traversing the X, Y, and Z axes of the design cube. Normally, coordinate systems have their origin defined as 0,0,0, though this is not required. Other coordinate systems are used to more easily express the coordinates of specific geometric entities. For example, you can use a spherical coordinate system to help define points on a sphere, and you can use a cylindrical coordinate system to help define points on a cylinder. An ordered set of absolute or relative data values that specify a location in a coordinate system. The image files written by System V for a number of reasons, the most common of which are memory violations, illegal instructions, bus errors, and user-generated quit signals. The pointer that the user moves on the screen to indicate an item or area. The mouse button used to place data points and tentative points, to accept previously selected elements, and to select commands from forms and menus. The field on a screen used to accept user-supplied data. Also known as key-in field. A point placed by pressing the data button on the mouse. Data points select commands from the panel menus and Menu Bar, place elements, identify and accept elements, and activate windows and perform window manipulations. A collection of comprehensive informational files having predetermined structure and organization that can then be communicated, interpreted, or processed by a specific program. The part of the database that is made of rows and columns and contains information about the project and design elements. The predetermined value of a parameter that is automatically supplied by the system or program whenever a value is not specified by the user.
coordinate coordinate system
coordinates
core files
cursor
data button
data entry field
data point
database
database table
default
Glossary GL - 5
delete delimiter
To remove, destroy, eliminate, or erase. A separating mark or space; a character or sequence of contiguous characters that mark the end of a string of characters. A nonaddressable component of a network, that is, a component onto which a user cannot log, for example, tape drive, disk drive, and floppy disk. A file that contains the names of other files. A small box with horizontal dashes located at the end of a form key-in field. When selected, a list of the data available for that field is displayed. Input can then be selected from the list with a data point instead of keying in the information. The set of acceptable values for a value within a component. Another term for the dynamic function that attaches the cursor to an element so you can see it move. A term used in plane surveying that describes an east, or positive, difference in longitude. An object (project, drawing, element, and so forth.) of interest about which information is stored; a relational database table. See interference envelope. A UNIX path name that tells the system where to locate a file. A user-defined name given to an interactively created file. The name should be relevant to the contents of the file. An interface or screen menu designed with the I/FORMS product. Because many of the screen menus in the application software are built with I/FORMS, you must have the FORMS_S product on your workstation. The name of the entire path or directory hierarchy to a file, including the file name. See also relative path name. A portion of a form, such as a button, a field, or a checklist, that responds to information. Gadgets can display default values or act as data entry areas. The first items of information in a file which precede any actual data. The header contains information on the structure and contents of the file. A classified structure with superiors (roots) and subordinates (dependents) for grouping files or commands.
device
directory display-list box
domain dragging
easting
entity
envelope file file specification
filename
form
full path name
gadget
header
hierarchy
GL - 6
icon
A pictorial representation or image; a symbol that graphically identifies a command. A relational database management system supported by RIS. A relational database management system supported by RIS. An equipment modeling primitive or parametric component that is used in conjunction with or instead of model graphics for interference checking. Interference envelopes are given different levels and display symbology to distinguish them from primitives. The lowest point on the internal diameter of the pipe. Relating to or being a drafting system characterized by three equal axes at right angles; a view in which the horizontal lines of an element are drawn at an angle to the horizontal and all verticals are projected at an angle from the base. An attribute (column) in a table which is chosen as the access vehicle to individual rows of the table. The field on a screen used to accept user-supplied data. Also known as a data entry field. A point on an element, including vertices, to which you can snap. A word recognized by the software that provides access to a certain function. The strip at the top of the screen that contains icons for selecting commands. The area that appears in the MicroStation Command Window when you are working in a design file. It is divided into the Command Status field, the Current Command field, the Prompt field, and the Key-in field. A graphic representation or schema. An interconnection of host computers and workstations that enables them to share data and control. The term network can mean the devices that connect the system, or it can mean the connected system. Network File System, the system that provides access to data that is distributed among machines through an interconnection of host computers and workstations. NFS allows you to mount a remote resource to your local workstation so you can access the data as though it were local. NFS is usually used to access centralized data on a server.
Informix Ingres interference envelope
invert elevation isometric
key
key-in field
keypoint
keyword
menubar
message area
model network
NFS
Glossary GL - 7
node
Any addressable device (such as a workstation or a server) that is connected to a network. The network enables the connected nodes to share data and system control. The hard-wired Ethernet address assigned to each node when it is manufactured. It is necessary for each node to identify and communicate with another node in the network. A name, or alias, that can be assigned to the node address of a device on a network. A term used to describe a north coordinate location in the plant coordinate system. A special equipment modeling primitive that contains the connection point to piping. This point does NOT include a gasket allowance, but rather represents the face-of-flange coordinate. Network Queuing System, the software package that allows you to define network-wide batch and device queues. Use of NQS involves setting up local resource queues on the system(s) where the resources reside and setting up pipe queues on the systems that are to have access to the resources. A relational database management system supported by RIS. In coordinate geometry, the point where the x, y, and z-axes intersect. The point at which the coordinate system is placed. A view which is a projection of the model onto a plane along lines which are orthogonal to the plane. A property whose value determines the characteristics or behavior of something. A sequence of directories leading to a file or a sequence of menus leading to a command. The sequence of directories leading to a file. See also absolute path name and relative path name. Plant Design System A controlled channel for moving requests to batch or device queues on remote systems and for receiving status and/or data in response. To identify a specific element, or indicate a specific point in the design file.
node address
node name
northing
nozzle
NQS
Oracle origin
origin point orthogonal view
parameter
path
path name
PDS pipe queue
place data point
GL - 8
plane
A spatial element in geometry that may or may not have a boundary, but is level, having no elevations or depressions, and is three-dimensional. Reference Database. A collection of reference data containing information relative to industry design codes, vendors catalog data, job specifications, commodity libraries, graphics symbology, label descriptions, report formats and other information of a similar manner. The sequence of directories leading from the current directory to a particular file. See also path name and absolute path name. To turn; to change the angular orientation; to transform by revolution about a specific axis. A unit of related information in a table. One collection of column values for a table. The animation dynamic that enables you to specify the position of a data point while the element changes as you move the cursor. A description of the overall structure of the rulebase or database. A file that outlines the overall logical structure of a rule base or a database. In network operations, the node which maintains common data or performs a common task needed by clients. All network operations (database, NFS, NQS) between two or more nodes establish a client/server relationship. Language developed by IBM for creating, modifying, and querying relational databases. The symbology of an element such as continuous dashes, dash-dot, solid, and so forth. The skin of a three-dimensional geometric element. The display style of an element, including color, style, and weight. A collection of data for quick reference, either stored in sequential locations in memory or printed as an array of rows and columns of data items of the same type. To switch; to change between two alternatives.
RDB reference database
relative path name
rotate
row
rubberbanding
schema
schema file
server
Structured Query Language SQL style
surface symbology
table
toggle
Glossary GL - 9
user name values
A name that provides access to an account on the system. Data, either entered by the user or determined by the software, that are stored in an attribute. A quantity that may assume any one of a set of values. A quantity possessing both magnitude and direction, generally represented as a line. Vectors can be manipulated geometrically and are represented as a coordinate triple (x,y,z). The defined area of vision on a screen. A view allows you to see a prescribed volume of the design cube. Views are created with their own x, y, and z axes. The x,y plane of the view is parallel to the screen, while the z-axis can be thought of as coming straight out of the view towards you. The view axes maintain this relationship regardless of the rotation with respect to the design cube. See also active depth. External memory for a computer that can be used as if it were an extension of the computers internal memory. The software uses virtual memory to store data. This means that unneeded files and data, stay on the disk until they are called for. Because the internal processing memory stores a minimal amount of data, the software can perform processing more quickly. The directory from which you are accessing files.
variable vector
view
virtual memory
working directory
GL - 10
Index IN - 1
Index
__________________________________________________________________________________________________________________________________________________
IN - 2
Index IN - 3
Index
__________________________________________________________________________________________________________________________________________________
3-way valves 7-1 4-way valves 7-1 A angle valves 7-1 assumptions about line names 3-7 B basic input data 4-12 batch processes 2-8 bent pipe 7-1 branch components 3-7 first order 4-24 welds 7-1 branches 3-7 C code 5-2 name of code parameter data table 6-3, 6-5 string 6-5 val 6-5 record 5-6 code 5-6 codeid 5-6 string 5-6 codeid 5-7 commodity code 6-11 component map 7-2 records 5-7 overall 5-7 prop 5-7 concentric reducers 7-1 conventions forms 2-5 crosses 7-1 D .dat pdsstr 1-2 strdef 1-2 database material/specification 3-5 DDL B-3 defaults file 1-2, 6-1, 6-12 keywords 6-2 6-3 code name of code parameter data table 6-5 parameter data table 6-3 element connectivity map table 6-3, 6-7 property / connectivity table 6-3, 6-7 end preparation table 6-3, 6-10 external files 6-3 6-4 fitting nomenclature table 6-3, 6-11 hanger type table 6-3, 6-11 intergraph options block 6-3 loading data (load) table 6-3, 6-5 options block 6-3 service loading (lset) table 6-3, 6-6 vendor name 6-3 6-4 structure 6-2 c1 6-2 cm- 6-2 endof table_keyword 6-2 m1 6-2 n1 6-2 table_keyword 6-2 generic names 3-way valves 7-1 4-way valves 7-1 angle valves 7-1 bent pipe 7-1 branch welds 7-1 concentric reducers 7-1 crosses 7-1 eccentric reducers 7-1 elbows 7-1 expansion joints 7-1 flanges 7-1 hangers 7-1 inline valves 7-1 miters 7-1 olets 7-1 pipe 7-1 pipe supports 7-1
IN - 4
defaults (continued) generic names (continued) rigid bodies 7-1 tees 7-1 descriptions detailed record 5-5 design database format B-3 file data in str order 4-24 raw 4-12 sorted by coordinate 4-13 sorted by topo 4-15 detailed record descriptions 5-5 disconnected sections 4-14 document organization x purpose ix E eccentric reducers 5-10, 7-1 elbows 6-9, 7-1 and bent pipe 5-10 types 6-9 element connectivity map table 6-3, 6-7 cat 6-7 name 6-7 nodes 6-7 onodes 6-7 property / connectivity table 6-3, 6-7 -1 6-8 attlst 6-8 form 1 attributes dry weight (34,26) 6-10 fitting type (0, -7) 6-10 insulation weight (0, -4) 6-10 iso drawing reference (4, 8) 6-10 material code (34,18) 6-9 stress intensification (34,42) 6-10 weight weight (34,27) 6-10 form 2 attributes bend angle ( 4, 23) 6-10 bend radius (4, 22) 6-10 mitre segment length (0, -21) 6-10 number of mitre joints (34, 30) 6-10 form 3 attributes end prep code (0,-20) 6-10 npd (34,49 and 34,16) 6-10 npd (34,50 and 34,63) 6-10 pressure rating (34,53 and 34,66) 6-10
element (continued) property / connectivity table (continued) form 3 attributes (continued) segment ID (0,-6) 6-10 wall thickness (0,-5) 6-10 form 4 attributes end prep code (0,-20) 6-10 npd (3,10 and 3,15) 6-10 npd (34,49 and 34,16) 6-10 pressure rating (3,13 and 3,18) 6-10 segment ID (0,-6) 6-10 wall thickness (0,-5) 6-10 formno 6-8 name 6-8 overall component attributes component tag (3,3) 6-9 special label (0,-2) 6-9 pdstyp 6-8 end preparation table 6-3, 6-10 gentyp 6-11 text 6-11 endof 6-2 error messages A-3, A-6 examples component map 7-2 HITS report 4-2 neutral file 5-12 options file 6-12 expansion joints 7-1 external files 6-3 6-4 F fitting nomenclature table 6-3, 6-11 ccode 6-11 ctype 6-11 type 6-11 flanges 7-1 forms conventions 2-5 G gadgets conventions 2-5 generating neutral files 3-1 model number 3-5 pipeline names 3-6 graphic commodity library 3-5 H hanger type table 6-3, 6-11 pdscode 6-11
Index IN - 5
hanger type table (continued) stype 6-11 hangers 7-1 header 3-7 header topo 4-25 HITS report 4-1, 4-28 branch 4-12 cp # 4-12 direct 4-12 flags 4-12 name 4-12 node 4-12 occ 4-12 sect 4-12 section 1 basic input data and raw design file data 4-12 section 2 design file data sorted by coordinate 4-13 section 3 tracing data 4-14 section 4 design file data sorted by topo 4-15 section 5 design file data in str order 4-24 sg_occ 4-12 topo 4-12 x 4-12 y 4-12 z 4-12 I inline valves 7-1 input collection 1-1 input data 4-12 intergraph options block 6-3 interpreting the HITS report 4-1 basic input data 4-12 design file data in str order 4-24 sorted by coordinate 4-13 sorted by topo 4-15 example HITS report 4-2 raw design file data 4-12 tracing data 4-14 using the HITS report to solve problems 4-28 introduction 1-1
J joint expansion 7-1 L label description library 3-5 libraries graphic commodity 3-5 label description 3-5 material descriptions 3-5 physical commodity 3-5 piping job spec tables 3-5 specialty and instrument descriptions 3-5 standard notes 3-5 line names assumptions 3-7 lnod 5-3 record 5-8 ax 5-8 ay 5-8 az 5-8 dx 5-8 dy 5-8 dz 5-8 lnod 5-8 node 5-8 type 5-8 load 5-2 5-3 record 5-5 i 5-5 j 5-5 load 5-5 pn 5-5 segid 5-5 tn 5-5 loading data (load) table 6-3, 6-5 -6 6-5 i 6-5 j 6-5 patt 6-5 tatt 6-5 lset 5-2 5-3 record lset 5-6 s1 5-6 s2 5-6 s3 5-6 s4 5-6 segid 5-6 M map stress symbol 6-4
IN - 6
material descriptions library 3-5 specification database 3-5 messages error A-3, A-6 warning A-3 A-4 miters 7-1 model files 3-5 number 3-5 N network problems 4-14 neudflts 6-1 neutral file 5-12 format 5-2 code 5-2 lnod 5-3 load 5-2 lset 5-2 node 5-3 section 1 5-2 section 2 5-2 section 3 5-2 section 4 5-2 section 5 5-2 section 6 5-3 section 7 5-3 section 8 5-3 generating 1-2, 3-1 stress analysis 5-1 node 5-3 number set 5-10 numbering conventions 5-10 eccentric reducers 5-10 elbows and bent pipe 5-10 olet and branch weld type components 5-10 pipe supports 5-11 straight through components 5-10 through valves 5-10 tee type components 5-10 three-way valves 5-10 two-way valves 5-10 record 5-9 flag 5-9 node 5-9 x 5-9 y 5-9 z 5-9
number fitting type 6-11 numbering conventions 5-10 O occurrence numbers 4-12 olets 3-7, 7-1 branch weld type components 5-10 options block 6-3 overall component record 5-7 compid 5-7 data 5-7 name 5-7 overlap 4-28 P PDS design database format B-3 item name 7-1 stress analysis symbol map 7-1 PDS item name 7-1 stress analysis generic name 7-1 valve type descriptor 7-1 to stress symbol map 6-4 PDS environment 2-1 PD_Shell 2-2 PD_Shell 2-2 form conventions 2-5 pdshell environment 2-1 pdsstr.dat 1-2 physical commodity libraries 3-5 pipe 7-1 supports 5-11, 7-1 pipeline names 3-6 piping job spec tables library 3-5 prop 5-2 5-3, 6-7, 7-1 record 5-7, 6-7 compid 5-8 data 5-8 form 5-8 name 5-7 prop 5-7 R raw design file data 4-12 RDB 3-5 record descriptions code 5-6 component 5-7 component record overall 5-7 prop 5-7 detailed 5-5 lnod 5-8 load 5-5
Index IN - 7
record descriptions (continued) lset 5-5 node 5-9 reference database 3-5 rigid bodies 7-1 S service loading (lset) table 6-3, 6-6 cold 6-6 dw 6-6 entatt 6-6 flag 6-6 hot 6-6 val 6-6 wind 6-6 set record 5-5 specialty and instrument descriptions library 3-5 specifying pipings segments 3-6 standard notes library 3-5 straight through components 5-10 through valves 5-10 strdef.dat 1-2 stress 7-1 analysis generic name 7-1 interface 1-2 neutral file 5-1 symbol map 6-4 strinp 1-2 symbol map PDS to stress analysis 7-1 T tee 3-7 type components 5-10 tees 7-1 three-way valves 5-10 topo 4-15 design file data sorted by 4-15 header 4-25 tracing data 4-14 traversing a network 4-24, 4-26 4-27 two-way valves 5-10 typefaces xiii U user input collecting 1-1 using HITS report to solve problems 4-28
V valve type descriptor 7-1 vendor name 6-3 6-4 W warning messages A-3 A-4 Z zero length leg 4-26
IN - 8

Stress Analysis

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Stress Analysis

Caricato da

Copyright:

Formati disponibili

PDS Stress Analysis Interface (PD_Stress)

This document replaces DEA503920.

Warranties and Liabilities

Table of Contents iii

5.2.5 5.2.6 5.3 5.4 6.

LNOD Record .................................................................................... NODE Record ...................................................................................

Node Numbering Conventions .................................................................... Example Neutral File ..................................................................................

Example Options File ..................................................................................

Appendix A: A.1 A.2

Glossary ....................................................................................................................... Index ............................................................................................................................

Document Prerequisites / Audience

About this Document

Section 7 Appendix A Appendix B

Ordering and Support Information

Finding Your Way Around

PDS Stress Analysis Interface Reference Guide - June 1998

PDS Stress Analysis Interface Reference Guide - June 1998

2.1 PD Shell __________________________________________________________________________________________________________________________________________________

PDS Stress Analysis Interface Reference Guide - June 1998

2.1.1 PD_Shell Form Conventions __________________________________________________________________________________________________________________________________________________

Common Tools on the PD Shell Forms

PDS Stress Analysis Interface Reference Guide - June 1998

PDS Stress Analysis Interface Reference Guide - June 1998

2.1.2 Batch Processes __________________________________________________________________________________________________________________________________________________

Generating Neutral Files 3 - 1

3. Generating Neutral Files

This section describes how to generate neutral files interactively.

Before Using This Command

Select the file, pds.cmd.

The system displays the Plant Design System form.

PDS Stress Analysis Interface Reference Guide - June 1998

Generating Neutral Files 3 - 3

PDS Stress Analysis Interface Reference Guide - June 1998

Generating Neutral Files 3 - 5

3.1 Model Files __________________________________________________________________________________________________________________________________________________

PDS Stress Analysis Interface Reference Guide - June 1998

3.2 Pipeline Names __________________________________________________________________________________________________________________________________________________

3.2.1 Extraction by Line Name Substring __________________________________________________________________________________________________________________________________________________

Generating Neutral Files 3 - 7

3.2.2 Extraction By ID __________________________________________________________________________________________________________________________________________________

Assumptions about Line Names

PDS Stress Analysis Interface Reference Guide - June 1998

Interpreting the HITS Report 4 - 1

4. Interpreting the HITS Report

PDS Stress Analysis Interface Reference Guide - June 1998

4.1 Example HITS Report __________________________________________________________________________________________________________________________________________________

Sheet One of Two

Interpreting the HITS Report 4 - 3

Sheet Two of Two

PDS Stress Analysis Interface Reference Guide - June 1998

Interpreting the HITS Report 4 - 5

25 25 305 305 305 103 103 18 18 18 19 19 19 20 20 20 21 21 28 28

PDS Stress Analysis Interface Reference Guide - June 1998

30 4 30 3 30 34 35 34 35 35 26 26 26 7 7 34 7 28 24 28 3 29 3 3 16 16 16 17 21 21 20 20 20 19 19 18 19 18 17 18 17 22 17 4 22 4 22 23 23 23 24 24 24 25 25 25 305 305 103 305 103 29 29 29 5

42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106

Interpreting the HITS Report 4 - 7

PDS Stress Analysis Interface Reference Guide - June 1998

Interpreting the HITS Report 4 - 9

3 3 16 16 17 17 22 22 23 23 24 24 25 25 305 305 103 103 29

0 0 0 0 108 108 0 0 0 0 105 105 0 0 0 0 0 0 -73

PDS Stress Analysis Interface Reference Guide - June 1998

COMP COMP COMP COMP COMP COMP COMP COMP COMP

1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08 1363.08

421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47 421.47