Stress Analysis

Reference Guide

PDS Stress AnalysisInterface (PD_Stress)

June 1998

DEA503932SE**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 oramendment of such warranties.

The information and the software discussed in this document are subject to change without notice and should not beconsidered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for anyerror 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 accordancewith the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied byIntergraph or its affiliated companies.

TrademarksCLIX, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DesignReview, DIALOG, EERaceway, FrameWorks, IGDS, MicasPlus, ModelDraft, Project Engineer, and SEE are trademarks of IntergraphCorporation. All other brands and product names are trademarks of their respective owners.

Copyright 1996 Intergraph CorporationAll Rights Reserved

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software licenseagreement; contains confidential and proprietary information of Intergraph and/or third parties which is protectedby copyright and trade secret law and may not be provided or otherwise made available without properauthorization.

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) ofThe 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 CorporationHuntsville, Alabama 35894-0001

Table of Contents iii

Table of Contents__________________________________________________________________________________________________________________________________________________

iv Table of Contents

Table of Contents v

__________________________________________________________________________________________________________________________________________________Table of Contents

Preface ......................................................................................................................... ix

Finding Your Way Around ................................................................................... xiii

1. Introduction .......................................................................................................... 1 - 1

2. PDS Environment ................................................................................................. 2 - 1

2.1 PD Shell ........................................................................................................ 2 - 2

2.1.1 PD_Shell Form Conventions ............................................................ 2 - 52.1.2 Batch Processes ................................................................................ 2 - 8

3. Generating Neutral Files ..................................................................................... 3 - 1

3.1 Model Files ................................................................................................... 3 - 53.2 Pipeline Names ............................................................................................ 3 - 6

3.2.1 Extraction by Line Name Substring ................................................ 3 - 63.2.2 Extraction By ID .............................................................................. 3 - 7

4. Interpreting the HITS Report .............................................................................. 4 - 1

4.1 Example HITS Report ................................................................................. 4 - 24.2 Section 1: Basic Input Data and Raw Design File Data ............................ 4 - 124.3 Section 2: Design File Data Sorted by Coordinate ..................................... 4 - 134.4 Section 3: Tracing Data ............................................................................... 4 - 144.5 Section 4: Design File Data Sorted by Topo ............................................... 4 - 154.6 Section 5: Design File Data in STR Order .................................................. 4 - 244.7 Using the HITS Report to Solve Problems ................................................. 4 - 28

5. The Stress Analysis Neutral File ......................................................................... 5 - 1

5.1 Neutral File Format ..................................................................................... 5 - 25.2 Detailed Record Descriptions ...................................................................... 5 - 5

5.2.1 LOAD Record .................................................................................... 5 - 55.2.2 LSET Record ..................................................................................... 5 - 55.2.3 CODE Record .................................................................................... 5 - 65.2.4 Component Records .......................................................................... 5 - 7

5.2.4.1 Overall Component Record ................................................ 5 - 75.2.4.2 PROP Record ...................................................................... 5 - 7

vi Table of Contents

5.2.5 LNOD Record .................................................................................... 5 - 85.2.6 NODE Record ................................................................................... 5 - 9

5.3 Node Numbering Conventions .................................................................... 5 - 105.4 Example Neutral File .................................................................................. 5 - 12

6. The Options File ................................................................................................... 6 - 1

6.1 Options File Structure ................................................................................. 6 - 26.2 Options File Keywords ................................................................................. 6 - 3

6.2.1 INTERGRAPH OPTIONS BLOCK ................................................. 6 - 36.2.2 VENDOR NAME .............................................................................. 6 - 46.2.3 EXTERNAL FILES .......................................................................... 6 - 4

6.2.3.1 PDS to Stress Symbol Map ................................................ 6 - 4

6.2.4 CODE NAME OF CODE PARAMETER DATA TABLE ................ 6 - 56.2.5 LOADING DATA (LOAD) TABLE .................................................. 6 - 56.2.6 SERVICE LOADING (LSET) TABLE ............................................. 6 - 66.2.7 ELEMENT CONNECTIVITY MAP TABLE ................................... 6 - 76.2.8 ELEMENT PROPERTY / CONNECTIVITY TABLE ..................... 6 - 76.2.9 END PREPARATION TABLE ......................................................... 6 - 106.2.10 FITTING NOMENCLATURE TABLE .......................................... 6 - 116.2.11 HANGER TYPE TABLE ................................................................ 6 - 11

6.3 Example Options File .................................................................................. 6 - 12

7. PDS to Stress Analysis Symbol Map ................................................................... 7 - 1

7.1 Example Component Map ........................................................................... 7 - 2

Appendix A: Warning & Error Messages ................................................................ A - 3

A.1 Warning Messages ............................................................................................. A - 4A.2 Error Messages .................................................................................................. A - 6

Appendix B: PDS Design Database Format ............................................................ B - 3

Glossary ....................................................................................................................... GL - 3

Index ............................................................................................................................ IN - 3

Preface vii

Preface__________________________________________________________________________________________________________________________________________________

viii Preface

Preface ix

__________________________________________________________________________________________________________________________________________________Preface

Document Purpose

This document is a reference guide for Intergraph Corporation’s PDS Stress AnalysisInterface (PD_STRESS) software package. You can use the PDS Stress Analysis Interfaceproduct 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 theproduct rather than presenting a typical work flow. Use this guide when you need to look upa specific stress function.

Document Prerequisites / Audience

This document is intended for designers who have a working knowledge of the standardinteractive 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 Interfaceproduct include:

PD Project Administrator Reference Guide

PD Piping Design Graphics Reference Guide

MicroStation 32 software is required to operate PD_STRESS. Information aboutMicroStation 32 capabilities can be found in the following documents:

MicroStation 32 Reference Guide

MicroStation 32 User’s Guide

Intergraph Corporation’s Relational Interface System (RIS) is required to operate the PDSStress 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

x Preface

For more information on related aspects of the PD ISOGEN products, consult the followingdocuments:

Project Aministrator Reference Guide

Piping Design Graphics Reference Guide

About this Document

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

Section 1 Provides an overview of the product.

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

Section 3 Describes how to generate neutral files interactively. This includesinformation on accessing the product and creating and manipulating productfiles.

Section 4 Describes how to interpret the HITS reports. This includes interpreting eachsection and using the report to solve problems.

Section 5 Describes the stress analysis neutral file. This includes record descriptionsand node numbering conventions.

Section 6 Describes the defaults file. This includes the default file structure andkeywords.

Section 7 Describes the PDS to Stress Analysis Symbool Map.

Appendix A Describes error messages and corrective actions.

Appendix B Displays the PDS Pipeline Design Database Format.

We would like to hear what you think about the reference manual. After you have used thisdocument, please help us improve our products by responding to the questionnaire at theback of the document. If you have more than one response to a question, circle all theresponses that apply.

Ordering and Support Information

To order documents:

Within the United States, contact your Customer Engineer or Sales AccountRepresentative.

Preface xi

For international locations, contact the Intergraph subsidiary or distributor from whomyou purchased your workstation.

For technical support of Intergraph hardware and software, contact Intergraph CustomerSupport:

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 youpurchased your workstation.

Additional Information

The following informational files are delivered with the PD_STRESS software in the/usr/ip32/pdstress directory.

File Name Contents

README Describes changes and additions to the product since the lastversion. Lists the names and dates of the files in the currentrelease. For a fixes release, the files which have been modified areappended to the top of the initial file to provide a history of allchanges to the product. Includes Comments and Trouble Reportnumbers which describe what problems have been fixed. Providesspecial notices to the customer. Lists any exceptions made to thecertification.

product.def Lists all dependencies and related parts for the product.

xii Preface

Preface xiii

__________________________________________________________________________________________________________________________________________________Finding Your Way Around

Visual Cues

This document contains many visual cues to help you betterunderstand the meaning of certain words or phrases. The useof different fonts for different types of information allows youto scan the document for key concepts or commands. Symbolshelp abbreviate and identify commonly used words, phrases,or groups of related information.

Typefaces

Italic Indicates a system response, which is anexplanation of what the software is doing. Forexample,

The text is placed in the viewing plane.

Bold Indicates a command name, parameter name,or dialog box title. Command paths are shownusing an arrow between command names. Forexample,

Choose File > Open to load a new file.

Sans serif Indicates a system prompt or message, whichrequires an action be taken by the user. Forexample,

Select first segment of alignment

NormalTypewriter

Indicates what you should literally type in.For example,

Key in original.dat to load the ASCII file.

BoldTypewriter

Indicates an actual file or directory name. Forexample,

The ASCII report is stored in the layout.rptfile.

xiv Preface

Symbols

This document uses the following symbols to represent mousebuttons and to identify special information:

<C> Command button<D> Data button<R> Reset/reject button<T> Tentative button

Note - Important supplemental information.

Warning - Critical information that could cause theloss of data if not followed.

Technical tip or information - providesinformation on what the software is doing orhow it processes information.

Map or path - shows you how to get to a specificcommand or form.

More information - indicates there is additionalor 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 documentuses for keyboard keys and describes how to use them incombination. You can make some menu selections throughthe use of keyboard accelerators (also known as mnemonics),which map menu selections to key combinations.

ALT Alternate keyCTRL Control keyDEL Delete keyENTER Return keyESC Escape key

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

Preface xv

Terminology

Choose To use a mouse or key combination to pick anitem that begins an action. For example,

Choose Apply to initiate the curvecalculation.

Select To mark an item by highlighting it with keycombinations or by picking it with your cursor.Selecting does not initiate an action. Afterselecting an item, you choose the action youwant to affect the item. For example,

Select the file original.dat from the list box,then choose Delete to remove it from thedirectory.

In addition, you would select items to defineparameters, such as selecting toggle buttons.This also applies to selecting graphic elementsfrom the design file. For example,

Select the line string to define the graphictemplate.

Tentative-select To place a tentative point on an existinggraphic element in a design file. If you areusing the CLIX operating system, youtentative-select by double-clicking with amouse or pressing <T> on a hand-held cursor.If you are using the Windows NT operatingsystem, you tentative-select by pressing aleft-button, right-button chord.

Double-click To select and execute a command by clickingthe mouse or hand-held cursor button twice inrapid succession. This term implies that youare clicking the data button (<D>) as part of amenu or dialog box action. For example,

Double-click on the file original.dat to loadit into the new surface.

Drag To press and hold the data button (<D>) whilemoving the mouse or hand-held cursor.

Type To key a character string into a text box.

xvi Preface

Key in To type in data and press ENTER to enter the

data and execute the default action.

In a dialog box, pressingTAB after typing in datawill enter the data and movethe cursor to the next field.

Introduction 1 - 1

__________________________________________________________________________________________________________________________________________________1. Introduction

The PD_Stress Analysis Interface product generates neutral files from three-dimensional (3D) piping models created by PDS modeling packages as inputfor third party stress analysis packages.

The neutral file can be run on your own in-house pipe stress software or onany other commercially available package capable of processing theIntergraph neutral file. Because of its flexibility, you can change the contentsof 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.DATwhich contains the defaults file NEUDFLTS. This defaults file containsswitches, options and tables allowing you to control the information theStress Analysis Interface enters into the neutral file. (Refer to the DefaultsFile section for more information on the contents of the defaults.) The strinpfile then displays the Stress Analysis Interface form allowing you to enterdata to the ASCII file pdsstr.dat.

From the pdsstr.dat file, the Stress Analysis Interface reads the involvedpiping and equipment models, the pipeline names or stress ID and thedefaults file.

The pdsstr file then reads the 3D piping model and generates the stressanalysis neutral files.

PDS Environment 2 - 1

__________________________________________________________________________________________________________________________________________________2. PDS Environment

The PDS 3D software supports a variety of applications. All the supportedapplications use a common interface that is controlled by the PD Shellprogram. This ensures consistency across applications and minimizes theamount of time required to learn the product.

The PDS 3D modules provide a simple user interface through extensive use offorms. The modules also provide an on-line Help capability for easy access toinformation while working in the product.

The PDS 3D software uses available nucleus tools such as MicroStation andFORMS. It supports standard software such as NFS, NQS, and RIS requiredto set up data across a network. This design facilitates the use of non-PDStools such as relational databases and third party software.

The PD_Shell Environment and all batch jobs in the PDS 3D productsinterface to Intergraph’s Network Licensing System.


__________________________________________________________________________________________________________________________________________________2.1 PD Shell

The PD Shell program provides access to the various functions that areassociated with the PDS 3D Modules. You can access the Plant DesignSystem 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 variablesthat are needed to run the product, and it identifies the location of theproduct files. These files can be located on the workstation or a server on thenetwork. See pds.cmd for more information on this file. The script alsoactivates the Plant Design System Environment form.

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

Options

Schematics Environment — Provides access to the PDS 2D modulesthat are used to create and modify piping and instrumentationdiagrams, process flow diagrams, and instrumentation databaserecords.


Equipment Modeling — Provides access to the Equipment Modelingmodule, which provides an interactive graphics environment that isused to create and revise equipment model graphics and databaseinformation.

FrameWorks Environment — Provides access to the FrameWorksmodule, which provides an environment that is used to create andrevise structural models, create and revise structural drawings, andpropagate structural models.

Piping Designer — Activates an interactive command environmentthat is used to create piping and in-line instrumentation in the model;revise existing model graphics and database information; and verify theintegrity of the data in the model.

Electrical Raceway Environment — Provides access to theElectrical Raceway module, which provides an interactive environmentthat is used to create and revise raceway models and access racewayutilities.

Piping Design Data Manager — Provides access to a set of optionsthat are used to verify the integrity of the graphic and databaseinformation that is associated with a model.

Piping Model Builder — Enables you to create piping graphics from anongraphics environment. This module is used with PD_Design tocreate an accurate 3D model of the piping network.

Pipe Stress Analysis — Activates a set of forms that are used toextract information from piping models for input to third-party pipestress analysis products.

Interference Manager — Activates a set of forms that are used tocheck for interferences among project models and to control approvedinterferences.

Isometric Drawing Manager — Activates a set of forms that are usedto extract isometric drawings from piping models and to review or plotthe created isometric drawings.

Drawing Manager — Activates a set of forms that are used to createand manipulate drawings and drawing views; provide access to theinteractive graphics environment for drawings; and provide access to aplot manager and vector hiddenline manager.

DesignReview Integrator — Activates a set of forms that are used toextract information to form label files for use in DesignReview and toreview data from a DesignReview session.

Report Manager — Activates a set of forms that are used to createand revise report format files and report on information in a projectincluding Material Take-Off reports.


Project Administrator — Provides access to a set of forms that areused to create a project, create and revise project files, define projectseed data, and control the project.

Reference Data Manager — Provides access to a set of forms that areused to control the reference data for a project including Piping JobSpecification data, Graphic Commodity Data, Alphanumeric CommodityData, Standard Note Library, Label Description Library, and PipingAssembly Library.

Other Fields

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

If access control has been defined, you must key in a valid user ID asdefined 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 andallows you to select the active project. The system lists all the definedPDS projects (2D-only, 3D-only, and 2D & 3D). An error is displayed ifyou select an option that is incompatible with the active project. Forexample, if the active project is a 2D-only project, you cannot access thethe Interference Manager module.

If access control has been defined, only those projects for which youhave some level of access are displayed.

Message Area — Displays prompts and messages that are associatedwith 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 formsand dialog boxes in the non-Microstation graphics environment areindependent of the size of the workstation’s display system. Most formscontain the same basic features: buttons, fields, text, and other gadgets. Ingeneral, anything you find on a form is called a gadget.

Selecting Options

You move through the PD Shell forms by selecting function buttons or othergadgets from the form. Select means to place the screen cursor (whichappears 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 toselect and accept the data in that row. This performs the same action asselecting a row (which highlights) and then selecting the Accept button.

You use the select action to select functions, access other forms, activate datafields, toggle buttons, select from lists, scroll through data displayed on thescreen, 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 alsopress <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 allof the forms. The following describes these tools.

Standard Commands

The PD Shell forms have a set of standard buttons in the upper right cornerof most of the form windows. The available commands vary from form toform depending on the type of operation.

The Help button activates on-line Help for the active form. Help remainsactive until you delete the Help window.


The Shell button exits the active form and returns control to the basemanager that is associated with the active form. For most forms this returnsto the Plant Design System Environment form.

The Top button exits the active form and returns control to the top form ofthe active branch.

The Cancel button cancels or exits from the active form. Control returns tothe immediately preceding form in the hierarchy.

The Accept button accepts a selection or operation. Depending on the activeform or option, the active form remains active so that you can repeat asimilar operation or control returns to the preceding form.

The Restart button clears any key-in fields on the form that have values youcan modify.

Scrolling List

Some screen menus have a scrolling list of projects or applications. You needto scroll a list only if more options are available than can be displayed in thewindow. To scroll a list, select the arrow buttons on the side of the list. Thelist scrolls up or down depending on which arrow you select.

The scrolling list has an arrow pointing up and an arrowpointing down. These arrows scroll lists line by line. There is abutton that slides between these two arrows to indicate yourposition on the list. To page through the list, select the spaceabove or below the sliding button. The list pages up or downaccordingly.

You can also select the slider and, while pressing <D>, slide the button up ordown 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 thenumber of lines and the relative position within the list.

All commands that display a list of design areas or models order the listalphanumerically by the design area number or model number in ascendingorder.

In some forms with scrolling lists, you can double-click on a row to select andaccept 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. Thesefields are box-shaped and dark gray. You can select a key-infield and key in a new value. A bar cursor appears in the activekey-in field. Key in your input, and press <Return>. To changea field, reselect the field and key in the new information. Key-infields have a maximum number of characters depending on theitem that is being defined.

If you select a key-in field for a code-listed attribute, the system activates aform that lists the code list values for the selected field.

MicroStation requires lowercase characters for the file specification and pathname of all design files. Therefore, the system automatically converts anyinput for the file specification and path name of a design file (such as a modelor 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. Itlets you select data from a list instead of keying in information.For example, there is a display list associated with theAuthorization key-in field shown. At the end of the field, there isa small box with horizontal dashes. When you select this displaylist box with the screen cursor, an associated list of valid inputvalues displays. Select an item from the list to enter its valueinto the field.

Shift Left and Shift Right buttons

At the bottom of some key-in and display fields, there are two buttonsmarked with arrows. These buttons are called shift left and shiftright buttons.

Often, you can key in more characters than a field display shows. Shift Leftmoves the text display to the front of the field; Shift Right moves the textdisplay to the end of the field.

Toggle

A toggle field on a screen menu enables you to select one of two possiblechoices, one of which is always displayed. Place a data point on the togglefield to toggle between the two choices.

Roll-Through List

A roll-through list shows one choice at a time of a list that can beseveral items long. Place a data point on the roll-through list to scrollthrough the available options. The option displayed is active.


Standard Window Icons

When using this software in the CLIX environment, you can press <D> alongthe edge of a form or any area not occupied by a button, key-in field, or othergadget, to display a box of icons. You can manipulate form windows just likeany other workstation window.

The following list defines the available window icons.

Collapse/RestoreRepaint

Pop-to-bottomModify/Resize

Pop-to-topRestore Size

__________________________________________________________________________________________________________________________________________________2.1.2 Batch Processes

When you install the PDS 3D applications, the system creates the necessarybatch queues for that application. Refer to Loading PDS Products in theProject Administrator (PD_Project) Reference Guide for a listing of the batchqueues.

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

When you submit a batch process the system sends an electronic mailmessage to the mail path of the default login reporting the jobs completionstatus. The mail message also includes any error log information. The setupof 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 acompleted 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.


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 keyin the .dgn filename. See Model Files, page 3 - 5 for more informationon defining a model number.

The software checks the model number for validity and either accepts theentry and moves the cursor to the next Model No field or displays anerror message in the message field.

4. Select the Pipeline Names field adjacent to the Model No fieldselected in the previous step and key in a valid pipeline name. SeePipeline Names, page 3 - 6 for more information on defining a pipelinename.

The software accepts the entry and moves to the next Pipeline Namesfield.

5. Select the Stress Output Node:Path field and key in the location ofthe 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 byexporting 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 defaultsfile.

The Stress Defaults File location should be in theformat: nodename:/usr/stress/defaults.dat .

The Stress Defaults File location should be in theformat:nodename:drive:\users\stress\defaults.dat .

A default setting can be set for Stress Defaults File byexporting the following statement.

For CLIX, in the control.sh file use the format:

exportSTRESSOPTION=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 andbegin generating the neutral file.

The system displays the message:

Creating Neutral File

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


The status form displays any processing information, warning messagesand/or error messages that occur during the generating process. Use thescroll bar and buttons to scroll through the information displayed on thestatus screen. Refer to the section Warning and Error Messages for detaileddescriptions of each warning and error message.


__________________________________________________________________________________________________________________________________________________3.1 Model Files

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

Equipment Modeling files must be specified in order to generatenozzles in the neutral file.

The first model number entered is considered to be the primary file and mustbe a Piping file and NOT an Equipment Modeling or Pipe file. Any referencedatabase (RDB) data accessed during stress analysis is obtained via theprimary model (through its type 63 data).

RDB data accessed by the PD_Stress Analysis Interface product and properlyattached 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 fourteencharacters or if the number contains a underbar (_) characters or if it does notexist in the project database.

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


__________________________________________________________________________________________________________________________________________________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 youare specifying a network of piping segments, you must not specify multipledisconnected piping sections such as vessel trim piping. For the lines to beconnected, the segments that form these lines must also be connected.

You can identify the pipelines you want to extract by line name substring orby Stress Analysis ID. The method you choose depends on the options you setin the defaults file. (Refer to the Defaults File section for more information).

In either method, you identify the piping network to extract by specifyingpiping segment attributes. Piping segments usually correspond only tosections 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 theStress Output Node field.

__________________________________________________________________________________________________________________________________________________3.2.1 Extraction by Line Name Substring

When extracting by line namesubstring, you should key in any substring ofthe full PDS line name that uniquely identifies the pipeline you want toinclude in the neutral file. This method is the default way of identifyingpipelines to extract.

Example 1

If the line name is 6IN-OWS10111-1C0031, you can use the substringOWS10111 to identify this line. You may not want to use 1C0031 because itis the spec name component of the line name and it would identify more thanone line in the model. Likewise, you might not want to use 6IN-OWS10111because it will only extract sections that have a NPD of 6 inches. This couldbe a problem if multiple 6 inch sections are connected together by sectionsthat are not 6 inches.

Extraction may fail if:

The line name substring you want to extract, exists with lines that aresimilarly named in the same models.

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


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 thesubstring OWS1011, you inadvertently specified that you want to extract6IN-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 toextract.

In the case above, the larger substring may be -OWS1011-.By including the dashes the substring specified is no longera 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 torunning the software. To extract by ID, you must establish the proper optionin 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 3Dmodel:

Branch components like olets are owned by the header to which they areattached. For an identified line, all of the olets (or olet-like components)are extracted with that line. It is not necessary to break the segmentunderneath the olet and change the line name so that the header ownsit.

Branch components like tee’s (for example, tee’s, 3-way valves) are alsoowned by the header. The header is defined as the part of the line thatcontains the run of the tee (from connect point 1 to connect point 2).Again, it is not necessary to break the segment underneath the branchof the component and give it the header line name.


Interpreting the HITS Report 4 - 1

__________________________________________________________________________________________________________________________________________________4. Interpreting the HITS Report

The HITS report is a diagnostic tool generated by the Intergraph interface toPDSTRESS. You can use this report to analyze the data collected from the3-D piping model when a problem extracting an isometric occurs. This reportcan help you determine whether or not the problem exists in your model, inthe PDSTRESS interface or in PDSTRESS itself.

The HITS report filename is formed from the output isometric designfilename. Isometric design filename is concatenated with the file extension.h. For example, if the isometric design filename is OWS1101.ISO then theHITS report filename will be OWS1101.h. The report is created in thedefault directory at the time the iso is created.

One of the options in the PDSTRESS interface defaults file allows you togenerate a HITS report only and not an intermediate data file (IDF). Youmay not always want to generate an IDF with a HITS report. The run timeto generate both an IDF and a HITS report is significantly longer than therun time to generate a HITS report only.


__________________________________________________________________________________________________________________________________________________4.1 Example HITS Report

The following section discusses an example of a HITS report. The HITSreport is composed of 5 basic sections. Refer to the following figure for anillustration of each of the five sections. The example HITS report in thissection 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 Occ cp # X Y Z Node Direct Section Flags Topo Seq Branch Sg_occ

COMP 16 0 1369.58 421.10 13.4 6 0 0 0 3 0 0 0 9 1

COMP 16 1 1369.58 420.95 13.4 6 0 0 0 3 0 0 0 9 2

COMP 16 2 1369.58 421.24 13.4 6 0 0 0 3 0 0 0 9 3

COMP 14 0 1363.08 422.45 15.1 8 0 0 0 3 0 0 0 5 4

COMP 14 1 1363.08 422.45 14.4 2 0 0 0 3 0 0 0 5 5

COMP 14 2 1363.08 422.45 15.9 4 0 0 0 3 0 0 0 8 6

COMP 14 3 1362.40 422.45 15.1 8 0 0 0 3 0 0 0 7 7

COMP 27 0 1362.35 422.45 15.1 8 0 0 0 3 0 0 0 7 8

COMP 27 1 1362.40 422.45 15.1 8 0 0 0 3 0 0 0 7 9

COMP 29 0 1369.58 422.45 18.4 6 0 0 0 3 0 0 0 16 10

COMP 29 1 1370.05 422.45 18.4 6 0 0 0 3 0 0 0 16 11

COMP 29 2 1369.11 422.45 18.4 6 0 0 0 3 0 0 0 17 12

COMP 29 3 1369.58 422.45 17.9 9 0 0 0 3 0 0 0 14 13

COMP 32 0 1373.58 422.45 18.4 6 0 0 0 3 0 0 0 16 14

COMP 32 1 1373.58 423.20 18.4 6 0 0 0 3 0 0 0 16 15

COMP 32 2 1372.83 422.45 18.4 6 0 0 0 3 0 0 0 16 16

COMP 33 0 1373.58 429.80 18.4 6 0 0 0 3 0 0 0 16 17

COMP 33 1 1372.83 429.80 18.4 6 0 0 0 3 0 0 0 16 18

COMP 33 2 1373.58 429.05 18.4 6 0 0 0 3 0 0 0 16 19

COMP 34 0 1364.58 429.80 18.4 6 0 0 0 3 0 0 0 16 20

COMP 34 1 1364.58 429.80 19.2 1 0 0 0 3 0 0 0 16 21

COMP 34 2 1365.33 429.80 18.4 6 0 0 0 3 0 0 0 16 22

COMP 35 0 1364.58 429.80 19.3 5 0 0 0 3 0 0 0 16 23

COMP 35 1 1364.58 429.80 19.5 1 0 0 0 3 0 0 0 16 24

COMP 35 2 1364.58 429.80 19.2 1 0 0 0 3 0 0 0 16 25


PIPE 5 1 1370.05 422.45 18.4 6 0 0 0 5 0 0 0 16 26

PIPE 5 2 1372.83 422.45 18.4 6 0 0 0 5 0 0 0 16 27

PIPE 6 1 1373.58 423.20 18.4 6 0 0 0 5 0 0 0 16 28

PIPE 6 2 1373.58 429.05 18.4 6 0 0 0 5 0 0 0 16 29

PIPE 7 1 1372.83 429.80 18.4 6 0 0 0 5 0 0 0 16 30

PIPE 7 2 1365.33 429.80 18.4 6 0 0 0 5 0 0 0 16 31

COMP 30 0 1363.08 422.45 18.4 6 0 0 0 3 0 0 0 8 32

COMP 30 1 1363.08 422.45 17.7 1 0 0 0 3 0 0 0 8 33

COMP 30 2 1363.83 422.45 18.4 6 0 0 0 3 0 0 0 17 34

PIPE 3 1 1369.11 422.45 18.4 6 0 0 0 5 0 0 0 17 35

PIPE 3 2 1363.83 422.45 18.4 6 0 0 0 5 0 0 0 17 36

COMP 17 0 1369.58 421.47 13.4 1 0 0 0 3 0 0 0 11 37

COMP 17 1 1369.58 421.70 13.3 7 0 0 0 3 0 0 0 11 38

COMP 17 2 1369.58 421.24 13.4 6 0 0 0 3 0 0 0 10 39

COMP 17 3T 1369.58 421.47 13.1 8 0 0 0 3 0 0 0 12 40

COMP 6 0 1363.08 421.10 13.4 6 0 0 0 3 0 0 0 3 41

COMP 6 1 1363.08 420.95 13.4 6 0 0 0 3 0 0 0 3 42

COMP 6 2 1363.08 421.24 13.4 6 0 0 0 3 0 0 0 3 43

COMP 15 0 1363.08 422.45 16.3 8 0 0 0 3 0 0 0 8 44

COMP 15 1 1363.08 422.45 15.9 4 0 0 0 3 0 0 0 8 45

COMP 15 2 1363.08 422.45 16.8 2 0 0 0 3 0 0 0 8 46

COMP 31 0 1363.08 422.45 16.9 7 0 0 0 3 0 0 0 8 47

COMP 31 1 1363.08 422.45 16.8 2 0 0 0 3 0 0 0 8 48

COMP 31 2 1363.08 422.45 17.1 2 0 0 0 3 0 0 0 8 49

PIPE 4 1 1363.08 422.45 17.7 1 0 0 0 5 0 0 0 8 50

PIPE 4 2 1363.08 422.45 17.1 2 0 0 0 5 0 0 0 8 51

COMP 7 0 1363.08 421.47 13.4 1 0 0 0 3 0 0 0 5 52

COMP 7 1 1363.08 421.70 13.3 7 0 0 0 3 0 0 0 5 53

COMP 7 2 1363.08 421.24 13.4 6 0 0 0 3 0 0 0 4 54

COMP 7 3T 1363.08 421.47 13.1 8 0 0 0 3 0 0 0 6 55

COMP 8 0 1363.08 421.47 13.0 6 0 0 0 3 0 0 0 6 56

COMP 8 1 1363.08 421.47 13.1 8 0 0 0 3 0 0 0 6 57

COMP 8 2 1363.08 421.47 12.9 3 0 0 0 3 0 0 0 6 58

COMP 9 0 1363.08 421.47 12.8 2 0 0 0 3 0 0 0 6 59

COMP 9 1 1363.08 421.47 12.9 3 0 0 0 3 0 0 0 6 60

COMP 9 2 1363.08 421.47 12.7 1 0 0 0 3 0 0 0 6 61

COMP 10 0 1363.08 421.47 12.5 8 0 0 0 3 0 0 0 6 62

COMP 10 1 1363.08 421.47 12.7 1 0 0 0 3 0 0 0 6 63

COMP 10 2 1363.08 421.47 12.4 6 0 0 0 3 0 0 0 6 64

COMP 11 0 1363.08 421.47 12.4 3 0 0 0 3 0 0 0 6 65

COMP 11 1 1363.08 421.47 12.4 6 0 0 0 3 0 0 0 6 66

COMP 26 0 1364.58 429.80 19.5 4 0 0 0 3 0 0 0 15 67

COMP 26 1 1364.58 429.80 19.5 8 0 0 0 3 0 0 0 15 68

COMP 26 2 1364.58 429.80 19.5 1 0 0 0 3 0 0 0 15 69

COMP 22 0 1369.58 422.45 13.3 7 0 0 0 3 0 0 0 11 70

COMP 22 1 1369.58 421.70 13.3 7 0 0 0 3 0 0 0 11 71

COMP 22 2 1369.58 422.45 14.1 2 0 0 0 3 0 0 0 11 72

COMP 23 0 1369.58 422.45 14.2 7 0 0 0 3 0 0 0 11 73

COMP 23 1 1369.58 422.45 14.4 2 0 0 0 3 0 0 0 11 74

COMP 23 2 1369.58 422.45 14.1 2 0 0 0 3 0 0 0 11 75

COMP 24 0 1369.58 422.45 15.1 8 0 0 0 3 0 0 0 11 76

COMP 24 1 1369.58 422.45 14.4 2 0 0 0 3 0 0 0 11 77

COMP 24 2 1369.58 422.45 15.9 4 0 0 0 3 0 0 0 14 78

COMP 24 3 1368.90 422.45 15.1 8 0 0 0 3 0 0 0 13 79

SUPP 4 1 1369.58 422.45 13.3 7 0 0 0 8 0 0 0 11 80

SUPP 4 2 1369.58 422.45 12.3 0 0 0 0 8 0 0 0 11 81

COMP 12 0 1363.08 422.45 13.3 7 0 0 0 3 0 0 0 5 82

COMP 12 1 1363.08 421.70 13.3 7 0 0 0 3 0 0 0 5 83

COMP 12 2 1363.08 422.45 14.1 2 0 0 0 3 0 0 0 5 84

COMP 13 0 1363.08 422.45 14.2 7 0 0 0 3 0 0 0 5 85

COMP 13 1 1363.08 422.45 14.4 2 0 0 0 3 0 0 0 5 86

COMP 13 2 1363.08 422.45 14.1 2 0 0 0 3 0 0 0 5 87

SUPP 3 1 1363.08 422.45 13.3 7 0 0 0 8 0 0 0 5 88

SUPP 3 2 1363.08 422.45 12.3 0 0 0 0 8 0 0 0 5 89

COMP 25 0 1369.58 422.45 16.3 8 0 0 0 3 0 0 0 14 90


COMP 25 1 1369.58 422.45 15.9 4 0 0 0 3 0 0 0 14 91

COMP 25 2 1369.58 422.45 16.8 2 0 0 0 3 0 0 0 14 92

COMP 305 0 1369.58 422.45 16.9 7 0 0 0 3 0 0 0 14 93

COMP 305 1 1369.58 422.45 16.8 2 0 0 0 3 0 0 0 14 94

COMP 305 2 1369.58 422.45 17.1 2 0 0 0 3 0 0 0 14 95

PIPE 103 1 1369.58 422.45 17.1 2 0 0 0 5 0 0 0 14 96

PIPE 103 2 1369.58 422.45 17.9 9 0 0 0 5 0 0 0 14 97

COMP 18 0 1369.58 421.47 13.0 6 0 0 0 3 0 0 0 12 98

COMP 18 1 1369.58 421.47 13.1 8 0 0 0 3 0 0 0 12 99

COMP 18 2 1369.58 421.47 12.9 3 0 0 0 3 0 0 0 12 100

COMP 19 0 1369.58 421.47 12.8 2 0 0 0 3 0 0 0 12 101

COMP 19 1 1369.58 421.47 12.9 3 0 0 0 3 0 0 0 12 102

COMP 19 2 1369.58 421.47 12.7 1 0 0 0 3 0 0 0 12 103

COMP 20 0 1369.58 421.47 12.5 8 0 0 0 3 0 0 0 12 104

COMP 20 1 1369.58 421.47 12.7 1 0 0 0 3 0 0 0 12 105

COMP 20 2 1369.58 421.47 12.4 6 0 0 0 3 0 0 0 12 106

COMP 21 0 1369.58 421.47 12.4 3 0 0 0 3 0 0 0 12 107

COMP 21 1 1369.58 421.47 12.4 6 0 0 0 3 0 0 0 12 108

COMP 28 0 1368.85 422.45 15.1 8 0 0 0 3 0 0 0 13 109

COMP 28 1 1368.90 422.45 15.1 8 0 0 0 3 0 0 0 13 110

Design file data sorted by coordinate

————————————-


COMP 27 0 1362.35 422.45 15.18 - 2 3 0 3 0 0 0 7 1

COMP 27 1 1362.40 422.45 15.1 8 1 3 0 3 0 0 0 7 2

COMP 14 3 1362.40 422.45 15.1 8 1 3 0 3 0 0 0 7 3

NOZ 1 1 1363.08 420.70 13.46 -1 11 0 2 2 0 0 0 3 4

NOZ 1 2 1363.08 420.95 13.46 40 11 0 2 2 0 0 0 3 5

COMP 6 1 1363.08 420.95 13.46 40 1 1 0 3 0 0 0 3 6

COMP 6 0 1363.08 421.10 13.46 0 1 1 0 3 0 0 0 3 7

COMP 6 2 1363.08 421.24 13.46 2 1 1 0 3 0 0 0 3 8

COMP 7 2 1363.08 421.24 13.46 2 1 2 0 3 0 0 0 4 9

COMP 11 0 1363.08 421.47 12.43 -2 1 3 0 3 0 0 0 6 10

COMP 11 1 1363.08 421.47 12.46 3 1 3 0 3 0 0 0 6 11

COMP 10 2 1363.08 421.47 12.46 3 1 3 0 3 0 0 0 6 12

COMP 10 0 1363.08 421.47 12.58 0 1 3 0 3 0 0 0 6 13

COMP 9 2 1363.08 421.47 12.71 4 1 3 0 3 0 0 0 6 14

COMP 10 1 1363.08 421.47 12.71 4 1 3 0 3 0 0 0 6 15

COMP 9 0 1363.08 421.47 12.82 0 1 3 0 3 0 0 0 6 16

COMP 9 1 1363.08 421.47 12.93 5 1 3 0 3 0 0 0 6 17

COMP 8 2 1363.08 421.47 12.93 5 1 3 0 3 0 0 0 6 18

COMP 8 0 1363.08 421.47 13.06 0 1 3 0 3 0 0 0 6 19

COMP 7 3T 1363.08 421.47 13.18 6 1 3 0 3 0 0 0 6 20

COMP 8 1 1363.08 421.47 13.18 6 1 3 0 3 0 0 0 6 21

COMP 7 0 1363.08 421.47 13.41 0 1 3 0 3 0 0 0 5 22

COMP 12 1 1363.08 421.70 13.37 7 1 5 0 3 0 0 0 5 23

COMP 7 1 1363.08 421.70 13.37 7 1 2 0 3 0 0 0 5 24

SUPP 3 2 1363.08 422.45 12.30 - 3 2 0 8 0 0 0 5 25

COMP 12 0 1363.08 422.45 13.37 0 1 5 0 3 0 0 0 5 26

SUPP 3 1 1363.08 422.45 13.3 7 0 2 0 8 0 0 0 5 27

COMP 13 2 1363.08 422.45 14.1 2 9 2 0 3 0 0 0 5 28

COMP 12 2 1363.08 422.45 14.1 2 9 2 0 3 0 0 0 5 29

COMP 13 0 1363.08 422.45 14.2 7 0 2 0 3 0 0 0 5 30

COMP 13 1 1363.08 422.45 14.42 1 0 2 0 3 0 0 0 5 31

COMP 14 1 1363.08 422.45 14.42 1 0 2 0 3 0 0 0 5 32

COMP 14 0 1363.08 422.45 15.1 8 0 3 0 3 0 0 0 5 33

COMP 15 1 1363.08 422.45 15.94 1 1 2 0 3 0 0 0 8 34

COMP 14 2 1363.08 422.45 15.94 1 1 2 0 3 0 0 0 8 35

COMP 15 0 1363.08 422.45 16.3 8 0 2 0 3 0 0 0 8 36

COMP 31 1 1363.08 422.45 16.82 1 2 2 0 3 0 0 0 8 37

COMP 15 2 1363.08 422.45 16.82 1 2 2 0 3 0 0 0 8 38

COMP 31 0 1363.08 422.45 16.9 7 0 2 0 3 0 0 0 8 39

COMP 31 2 1363.08 422.45 17.12 1 3 2 0 3 0 0 0 8 40

PIPE 4 2 1363.08 422.45 17.12 1 3 2 0 5 0 0 0 8 41


COMP 30 1 1363.08 422.45 17.71 1 4 2 0 3 0 0 0 8 42

PIPE 4 1 1363.08 422.45 17.71 1 4 2 0 5 0 0 0 8 43

COMP 30 0 1363.08 422.45 18.4 6 0 4 0 3 0 0 0 8 44

PIPE 3 2 1363.83 422.45 18.46 1 5 4 0 5 0 0 0 17 45

COMP 30 2 1363.83 422.45 18.46 1 5 4 0 3 0 0 0 17 46

COMP 34 0 1364.58 429.80 18.4 6 0 8 0 3 0 0 0 16 47

COMP 35 2 1364.58 429.80 19.21 1 6 8 0 3 0 0 0 16 48

COMP 34 1 1364.58 429.80 19.21 1 6 8 0 3 0 0 0 16 49

COMP 35 0 1364.58 429.80 19.3 5 0 8 0 3 0 0 0 16 50

COMP 35 1 1364.58 429.80 19.51 1 7 8 0 3 0 0 0 16 51

COMP 26 2 1364.58 429.80 19.51 1 7 8 0 3 0 0 0 15 52

COMP 26 0 1364.58 429.80 19.5 4 0 8 0 3 0 0 0 15 53

COMP 26 1 1364.58 429.80 19.58 4 1 8 0 3 0 0 0 15 54

NOZ 7 2 1364.58 429.80 19.58 41 8 0 2 2 0 0 0 15 55

NOZ 7 1 1364.58 429.80 20.58 -1 8 0 2 2 0 0 0 15 56

COMP 34 2 1365.33 429.80 18.46 1 8 7 0 3 0 0 0 16 57

PIPE 7 2 1365.33 429.80 18.46 1 8 7 0 5 0 0 0 16 58

COMP 28 0 1368.85 422.45 15.18 - 2 3 0 3 0 0 0 13 59

COMP 24 3 1368.90 422.45 15.18 1 9 3 0 3 0 0 0 13 60

COMP 28 1 1368.90 422.45 15.18 1 9 3 0 3 0 0 0 13 61

PIPE 3 1 1369.11 422.45 18.46 2 0 4 0 5 0 0 0 17 62

COMP 29 2 1369.11 422.45 18.46 2 0 4 0 3 0 0 0 17 63

NOZ 3 1 1369.58 420.70 13.46 -1 1 0 2 2 0 0 0 9 64

NOZ 3 2 1369.58 420.95 13.46 39 1 0 2 2 0 0 0 9 65

COMP 16 1 1369.58 420.95 13.46 3 9 1 0 3 0 0 0 9 66

COMP 16 0 1369.58 421.10 13.4 6 0 1 0 3 0 0 0 9 67

COMP 16 2 1369.58 421.24 13.46 2 1 1 0 3 0 0 0 9 68

COMP 17 2 1369.58 421.24 13.46 2 1 9 0 3 0 0 0 10 69

COMP 21 0 1369.58 421.47 12.43 -2 1 0 0 3 0 0 0 12 70

COMP 21 1 1369.58 421.47 12.46 22 1 0 0 3 0 0 0 12 71

COMP 20 2 1369.58 421.47 12.46 22 1 0 0 3 0 0 0 12 72

COMP 20 0 1369.58 421.47 12.58 0 1 0 0 3 0 0 0 12 73

COMP 20 1 1369.58 421.47 12.71 23 1 0 0 3 0 0 0 12 74

COMP 19 2 1369.58 421.47 12.71 23 1 0 0 3 0 0 0 12 75

COMP 19 0 1369.58 421.47 12.82 0 1 0 0 3 0 0 0 12 76

COMP 18 2 1369.58 421.47 12.93 24 1 0 0 3 0 0 0 12 77

COMP 19 1 1369.58 421.47 12.93 24 1 0 0 3 0 0 0 12 78

COMP 18 0 1369.58 421.47 13.06 0 1 0 0 3 0 0 0 12 79

COMP 17 3T 1369.58 421.47 13.18 25 1 0 0 3 0 0 0 12 80

COMP 18 1 1369.58 421.47 13.18 25 1 0 0 3 0 0 0 12 81

COMP 17 0 1369.58 421.47 13.41 0 1 0 0 3 0 0 0 11 82

COMP 22 1 1369.58 421.70 13.37 26 1 4 0 3 0 0 0 11 83

COMP 17 1 1369.58 421.70 13.37 2 6 9 0 3 0 0 0 11 84

SUPP 4 2 1369.58 422.45 12.30 - 3 5 0 8 0 0 0 11 85

COMP 22 0 1369.58 422.45 13.37 0 1 4 0 3 0 0 0 11 86

SUPP 4 1 1369.58 422.45 13.3 7 0 5 0 8 0 0 0 11 87

COMP 22 2 1369.58 422.45 14.12 2 8 5 0 3 0 0 0 11 88

COMP 23 2 1369.58 422.45 14.12 2 8 5 0 3 0 0 0 11 89

COMP 23 0 1369.58 422.45 14.2 7 0 5 0 3 0 0 0 11 90

COMP 23 1 1369.58 422.45 14.42 2 9 5 0 3 0 0 0 11 91

COMP 24 1 1369.58 422.45 14.42 2 9 5 0 3 0 0 0 11 92

COMP 24 0 1369.58 422.45 15.1 8 0 5 0 3 0 0 0 11 93

COMP 24 2 1369.58 422.45 15.94 3 0 5 0 3 0 0 0 14 94

COMP 25 1 1369.58 422.45 15.94 3 0 5 0 3 0 0 0 14 95

COMP 25 0 1369.58 422.45 16.3 8 0 5 0 3 0 0 0 14 96

COMP 25 2 1369.58 422.45 16.82 3 1 5 0 3 0 0 0 14 97

COMP 305 1 1369.58 422.45 16.82 3 1 5 0 3 0 0 0 14 98

COMP 305 0 1369.58 422.45 16.9 7 0 5 0 3 0 0 0 14 99

PIPE 103 1 1369.58 422.45 17.12 3 2 5 0 5 0 0 0 14 100

COMP 305 2 1369.58 422.45 17.12 3 2 5 0 3 0 0 0 14 101

PIPE 103 2 1369.58 422.45 17.99 3 3 5 0 5 0 0 0 14 102

COMP 29 3 1369.58 422.45 17.99 3 3 5 0 3 0 0 0 14 103

COMP 29 0 1369.58 422.45 18.4 6 0 5 0 3 0 0 0 16 104

COMP 29 1 1370.05 422.45 18.46 3 4 4 0 3 0 0 0 16 105

PIPE 5 1 1370.05 422.45 18.46 3 4 4 0 5 0 0 0 16 106


PIPE 5 2 1372.83 422.45 18.46 3 5 4 0 5 0 0 0 16 107

COMP 32 2 1372.83 422.45 18.46 3 5 4 0 3 0 0 0 16 108

PIPE 7 1 1372.83 429.80 18.46 3 6 7 0 5 0 0 0 16 109

COMP 33 1 1372.83 429.80 18.46 3 6 7 0 3 0 0 0 16 110

COMP 32 0 1373.58 422.45 18.4 6 0 6 0 3 0 0 0 16 111

COMP 32 1 1373.58 423.20 18.46 3 7 6 0 3 0 0 0 16 112

PIPE 6 1 1373.58 423.20 18.46 3 7 6 0 5 0 0 0 16 113

COMP 33 2 1373.58 429.05 18.46 3 8 6 0 3 0 0 0 16 114

PIPE 6 2 1373.58 429.05 18.46 3 8 6 0 5 0 0 0 16 115

COMP 33 0 1373.58 429.80 18.4 6 0 7 0 3 0 0 0 16 116

Tracing data

————

Action Occ Cp Name Node Ref Design

5 Next 3 2 NOZ 39 112 1 1 1

5 Next 16 1 COMP 39 2 1 1 2

5 Next 16 2 COMP 21 3 1 1 3

5 Next 17 2 COMP 21 39 1 1 4

6 Push 17 3 COMP 25 40 1 ++++ 0 0

5 Next 17 1 COMP 26 38 1 1 5

5 Next 22 1 COMP 26 71 1 1 6

5 Next 22 2 COMP 28 72 1 1 7

5 Next 23 2 COMP 28 75 1 1 8

5 Next 23 1 COMP 29 74 1 1 9

5 Next 24 1 COMP 29 77 1 1 10

6 Push 24 3 COMP 19 79 1 ++++ 0 0

5 Next 24 2 COMP 30 78 1 1 11

5 Next 25 1 COMP 30 91 1 1 12

5 Next 25 2 COMP 31 92 1 1 13

5 Next 305 1 COMP 31 94 1 1 14

5 Next 305 2 COMP 32 95 1 1 15

5 Next 103 1 PIPE 32 96 1 1 16

5 Next 103 2 PIPE 33 97 1 1 17

5 Next 29 3 COMP 33 13 1 1 18

6 Push 29 2 COMP 20 12 1 ++++ 0 0

5 Next 29 1 COMP 34 11 1 2 1

5 Next 5 1 PIPE 34 26 1 2 2

5 Next 5 2 PIPE 35 27 1 2 3

5 Next 32 2 COMP 35 16 1 2 4

5 Next 32 1 COMP 37 15 1 2 5

5 Next 6 1 PIPE 37 28 1 2 6

5 Next 6 2 PIPE 38 29 1 2 7

5 Next 33 2 COMP 38 19 1 2 8

5 Next 33 1 COMP 36 18 1 2 9

5 Next 7 1 PIPE 36 30 1 2 10

5 Next 7 2 PIPE 18 31 1 2 11

5 Next 34 2 COMP 18 22 1 2 12

5 Next 34 1 COMP 16 21 1 2 13

5 Next 35 2 COMP 16 25 1 2 14

5 Next 35 1 COMP 17 24 1 2 15

5 Next 26 2 COMP 17 69 1 2 16

5 Next 26 1 COMP 41 68 1 2 17

5 Next 7 2 NOZ 41 116 1 2 18

5 Next 7 1 NOZ -1 115 1 2 19

7 Pull 29 2 COMP 20 12 1 —- 2 0

5 Next 29 2 COMP 20 12 1 2 -1

5 Next 3 1 PIPE 20 35 1 2 -2

5 Next 3 2 PIPE 15 36 1 2 -3

5 Next 30 2 COMP 15 34 1 2 -4

5 Next 30 1 COMP 14 33 1 2 -5

5 Next 4 1 PIPE 14 50 1 2 -6

5 Next 4 2 PIPE 13 51 1 2 -7

5 Next 31 2 COMP 13 49 1 2 -8

5 Next 31 1 COMP 12 48 1 2 -9

5 Next 15 2 COMP 12 46 1 2 -10


5 Next 15 1 COMP 11 45 1 2 -11

5 Next 14 2 COMP 11 6 1 2 -12

6 Push 14 3 COMP 1 7 1 ++++ 0 0

5 Next 14 1 COMP 10 5 1 2 -13

5 Next 13 1 COMP 10 86 1 2 -14

5 Next 13 2 COMP 9 87 1 2 -15

5 Next 12 2 COMP 9 84 1 2 -16

5 Next 12 1 COMP 7 83 1 2 -17

5 Next 7 1 COMP 7 53 1 2 -18

6 Push 7 3 COMP 6 55 1 ++++ 0 0

5 Next 7 2 COMP 2 54 1 2 -19

5 Next 6 2 COMP 2 43 1 2 -20

5 Next 6 1 COMP 40 42 1 2 -21

5 Next 1 2 NOZ 40 114 1 2 -22

5 Next 1 1 NOZ -1 113 1 2 -23

7 Pull 7 3 COMP 6 55 1 —- 0 0

5 Next 7 3 COMP 6 55 1 3 1

5 Next 8 1 COMP 6 57 1 3 2

5 Next 8 2 COMP 5 58 1 3 3

5 Next 9 1 COMP 5 60 1 3 4

5 Next 9 2 COMP 4 61 1 3 5

5 Next 10 1 COMP 4 63 1 3 6

5 Next 10 2 COMP 3 64 1 3 7

5 Next 11 1 COMP 3 66 1 3 8

5 Next 11 0 COMP -2 65 1 3 9

7 Pull 14 3 COMP 1 7 1 —- 0 0

5 Next 14 3 COMP 1 7 1 4 1

5 Next 27 1 COMP 1 9 1 4 2

5 Next 27 0 COMP -2 8 1 4 3

7 Pull 24 3 COMP 19 79 1 —- 0 0

5 Next 24 3 COMP 19 79 1 5 1

5 Next 28 1 COMP 19 110 1 5 2

5 Next 28 0 COMP -2 109 1 5 3

7 Pull 17 3 COMP 25 40 1 —- 0 0

5 Next 17 3 COMP 25 40 1 6 1

5 Next 18 1 COMP 25 99 1 6 2

5 Next 18 2 COMP 24 100 1 6 3

5 Next 19 1 COMP 24 102 1 6 4

5 Next 19 2 COMP 23 103 1 6 5

5 Next 20 1 COMP 23 105 1 6 6

5 Next 20 2 COMP 22 106 1 6 7

5 Next 21 1 COMP 22 108 1 6 8

5 Next 21 0 COMP -2 107 1 6 9

-1 39 21 26 28 29 30 31 32 33

34 35 37 38 36 18 16 17 41 20

15 14 13 12 11 10 9 7 2 40

6 5 4 3 1 19 25 24 23 22

0

# Sections: 1

Design file data sorted by topo

——————————-


COMP 16 0 1369.58 421.10 13.4 6 0 1 0 3 0 0 0 9 1

COMP 9 0 1363.08 421.47 12.82 0 1 3 0 3 0 0 0 6 2

COMP 30 0 1363.08 422.45 18.4 6 0 4 0 3 0 0 0 8 3

COMP 14 0 1363.08 422.45 15.1 8 0 3 0 3 0 0 0 5 4

COMP 10 0 1363.08 421.47 12.58 0 1 3 0 3 0 0 0 6 5

COMP 305 0 1369.58 422.45 16.9 7 0 5 0 3 0 0 0 14 6

COMP 32 0 1373.58 422.45 18.4 6 0 6 0 3 0 0 0 16 7

COMP 17 0 1369.58 421.47 13.41 0 1 0 0 3 0 0 0 11 8

COMP 26 0 1364.58 429.80 19.5 4 0 8 0 3 0 0 0 15 9

COMP 29 0 1369.58 422.45 18.4 6 0 5 0 3 0 0 0 16 10

COMP 18 0 1369.58 421.47 13.06 0 1 0 0 3 0 0 0 12 11

COMP 22 0 1369.58 422.45 13.37 0 1 4 0 3 0 0 0 11 12


COMP 13 0 1363.08 422.45 14.2 7 0 2 0 3 0 0 0 5 13

COMP 8 0 1363.08 421.47 13.06 0 1 3 0 3 0 0 0 6 14

COMP 23 0 1369.58 422.45 14.2 7 0 5 0 3 0 0 0 11 15

COMP 15 0 1363.08 422.45 16.3 8 0 2 0 3 0 0 0 8 16

COMP 33 0 1373.58 429.80 18.4 6 0 7 0 3 0 0 0 16 17

COMP 24 0 1369.58 422.45 15.1 8 0 5 0 3 0 0 0 11 18

COMP 31 0 1363.08 422.45 16.9 7 0 2 0 3 0 0 0 8 19

COMP 34 0 1364.58 429.80 18.4 6 0 8 0 3 0 0 0 16 20

COMP 12 0 1363.08 422.45 13.37 0 1 5 0 3 0 0 0 5 21

COMP 19 0 1369.58 421.47 12.82 0 1 0 0 3 0 0 0 12 22

COMP 35 0 1364.58 429.80 19.3 5 0 8 0 3 0 0 0 16 23

COMP 6 0 1363.08 421.10 13.46 0 1 1 0 3 0 0 0 3 24

COMP 25 0 1369.58 422.45 16.3 8 0 5 0 3 0 0 0 14 25

COMP 20 0 1369.58 421.47 12.58 0 1 0 0 3 0 0 0 12 26

COMP 7 0 1363.08 421.47 13.41 0 1 3 0 3 0 0 0 5 27

SUPP 4 1 1369.58 422.45 13.3 7 0 5 0 8 0 0 0 11 28

SUPP 3 1 1363.08 422.45 13.3 7 0 2 0 8 0 0 0 5 29

SUPP 3 2 1363.08 422.45 12.30 - 3 2 0 8 0 0 0 5 30

SUPP 4 2 1369.58 422.45 12.30 - 3 5 0 8 0 0 0 11 31

NOZ 3 1 1369.58 420.70 13.46 -1 1 1 2 2 1 0 0 9 32

NOZ 3 2 1369.58 420.95 13.46 39 1 1 2 2 1 1 0 9 33

COMP 16 1 1369.58 420.95 13.46 3 9 1 1 3 1 2 0 9 34

COMP 16 2 1369.58 421.24 13.46 2 1 1 1 3 1 3 0 9 35

COMP 17 2 1369.58 421.24 13.46 2 1 9 1 3 1 4 108 10 36

COMP 17 1 1369.58 421.70 13.37 2 6 9 1 3 1 5 108 11 37

COMP 22 1 1369.58 421.70 13.37 26 1 4 1 3 1 6 0 11 38

COMP 22 2 1369.58 422.45 14.12 2 8 5 1 3 1 7 0 11 39

COMP 23 2 1369.58 422.45 14.12 2 8 5 1 3 1 8 0 11 40

COMP 23 1 1369.58 422.45 14.42 2 9 5 1 3 1 9 0 11 41

COMP 24 1 1369.58 422.45 14.42 2 9 5 1 3 1 10 105 11 42

COMP 24 2 1369.58 422.45 15.94 3 0 5 1 3 1 11 105 14 43

COMP 25 1 1369.58 422.45 15.94 3 0 5 1 3 1 12 0 14 44

COMP 25 2 1369.58 422.45 16.82 3 1 5 1 3 1 13 0 14 45

COMP 305 1 1369.58 422.45 16.82 3 1 5 1 3 1 14 0 14 46

COMP 305 2 1369.58 422.45 17.12 3 2 5 1 3 1 15 0 14 47

PIPE 103 1 1369.58 422.45 17.12 3 2 5 1 5 1 16 0 14 48

PIPE 103 2 1369.58 422.45 17.99 3 3 5 1 5 1 17 0 14 49

COMP 29 3 1369.58 422.45 17.99 3 3 5 1 3 1 18 -73 14 50

NOZ 1 1 1363.08 420.70 13.46 -1 11 1 22 2 -23 0 3 51

NOZ 1 2 1363.08 420.95 13.46 40 11 1 22 2 -22 0 3 52

COMP 6 1 1363.08 420.95 13.46 40 1 1 1 3 2 -21 0 3 53

COMP 6 2 1363.08 421.24 13.46 2 1 1 1 3 2 -20 0 3 54

COMP 7 2 1363.08 421.24 13.46 2 1 2 1 3 2 -19 93 4 55

COMP 7 1 1363.08 421.70 13.37 7 1 2 1 3 2 -18 93 5 56

COMP 12 1 1363.08 421.70 13.37 7 1 5 1 3 2 -17 0 5 57

COMP 12 2 1363.08 422.45 14.1 2 9 2 1 3 2 -16 0 5 58

COMP 13 2 1363.08 422.45 14.1 2 9 2 1 3 2 -15 0 5 59

COMP 13 1 1363.08 422.45 14.42 1 0 2 1 3 2 -14 0 5 60

COMP 14 1 1363.08 422.45 14.42 1 0 2 1 3 2 -13 102 5 61

COMP 14 2 1363.08 422.45 15.94 1 1 2 1 3 2 -12 102 8 62

COMP 15 1 1363.08 422.45 15.94 1 1 2 1 3 2 -11 0 8 63

COMP 15 2 1363.08 422.45 16.82 1 2 2 1 3 2 -10 0 8 64

COMP 31 1 1363.08 422.45 16.82 1 2 2 1 3 2 -9 0 8 65

COMP 31 2 1363.08 422.45 17.12 1 3 2 1 3 2 -8 0 8 66

PIPE 4 2 1363.08 422.45 17.12 1 3 2 1 5 2 -7 0 8 67

PIPE 4 1 1363.08 422.45 17.71 1 4 2 1 5 2 -6 0 8 68

COMP 30 1 1363.08 422.45 17.71 1 4 2 1 3 2 -5 0 8 69

COMP 30 2 1363.83 422.45 18.46 1 5 4 1 3 2 -4 0 17 70

PIPE 3 2 1363.83 422.45 18.46 1 5 4 1 5 2 -3 0 17 71

PIPE 3 1 1369.11 422.45 18.46 2 0 4 1 5 2 -2 0 17 72

COMP 29 2 1369.11 422.45 18.46 2 0 4 1 3 2 -1 50 17 73

COMP 29 1 1370.05 422.45 18.46 3 4 4 1 3 2 1 50 16 74

PIPE 5 1 1370.05 422.45 18.46 3 4 4 1 5 2 2 0 16 75


PIPE 5 2 1372.83 422.45 18.46 3 5 4 1 5 2 3 0 16 76

COMP 32 2 1372.83 422.45 18.46 3 5 4 1 3 2 4 0 16 77

COMP 32 1 1373.58 423.20 18.46 3 7 6 1 3 2 5 0 16 78

PIPE 6 1 1373.58 423.20 18.46 3 7 6 1 5 2 6 0 16 79

PIPE 6 2 1373.58 429.05 18.46 3 8 6 1 5 2 7 0 16 80

COMP 33 2 1373.58 429.05 18.46 3 8 6 1 3 2 8 0 16 81

COMP 33 1 1372.83 429.80 18.46 3 6 7 1 3 2 9 0 16 82

PIPE 7 1 1372.83 429.80 18.46 3 6 7 1 5 2 10 0 16 83

PIPE 7 2 1365.33 429.80 18.46 1 8 7 1 5 2 11 0 16 84

COMP 34 2 1365.33 429.80 18.46 1 8 7 1 3 2 12 0 16 85

COMP 34 1 1364.58 429.80 19.21 1 6 8 1 3 2 13 0 16 86

COMP 35 2 1364.58 429.80 19.21 1 6 8 1 3 2 14 0 16 87

COMP 35 1 1364.58 429.80 19.51 1 7 8 1 3 2 15 0 16 88

COMP 26 2 1364.58 429.80 19.51 1 7 8 1 3 2 16 0 15 89

COMP 26 1 1364.58 429.80 19.58 4 1 8 1 3 2 17 0 15 90

NOZ 7 2 1364.58 429.80 19.58 41 8 1 22 2 18 0 15 91

NOZ 7 1 1364.58 429.80 20.58 -1 8 1 22 2 19 0 15 92

COMP 7 3T 1363.08 421.47 13.18 6 1 3 1 3 3 1 -55 6 93

COMP 8 1 1363.08 421.47 13.18 6 1 3 1 3 3 2 0 6 94

COMP 8 2 1363.08 421.47 12.93 5 1 3 1 3 3 3 0 6 95

COMP 9 1 1363.08 421.47 12.93 5 1 3 1 3 3 4 0 6 96

COMP 9 2 1363.08 421.47 12.71 4 1 3 1 3 3 5 0 6 97

COMP 10 1 1363.08 421.47 12.71 4 1 3 1 3 3 6 0 6 98

COMP 10 2 1363.08 421.47 12.46 3 1 3 1 3 3 7 0 6 99

COMP 11 1 1363.08 421.47 12.46 3 1 3 1 3 3 8 0 6 100

COMP 11 0 1363.08 421.47 12.43 -2 1 3 1 3 3 9 0 6 101

COMP 14 3 1362.40 422.45 15.1 8 1 3 1 3 4 1 -61 7 102

COMP 27 1 1362.40 422.45 15.1 8 1 3 1 3 4 2 0 7 103

COMP 27 0 1362.35 422.45 15.18 - 2 3 1 3 4 3 0 7 104

COMP 24 3 1368.90 422.45 15.18 1 9 3 1 3 5 1 -42 13 105

COMP 28 1 1368.90 422.45 15.18 1 9 3 1 3 5 2 0 13 106

COMP 28 0 1368.85 422.45 15.18 - 2 3 1 3 5 3 0 13 107

COMP 17 3T 1369.58 421.47 13.18 25 1 0 1 3 6 1 -36 12 108

COMP 18 1 1369.58 421.47 13.18 25 1 0 1 3 6 2 0 12 109

COMP 18 2 1369.58 421.47 12.93 24 1 0 1 3 6 3 0 12 110

COMP 19 1 1369.58 421.47 12.93 24 1 0 1 3 6 4 0 12 111

COMP 19 2 1369.58 421.47 12.71 23 1 0 1 3 6 5 0 12 112

COMP 20 1 1369.58 421.47 12.71 23 1 0 1 3 6 6 0 12 113

COMP 20 2 1369.58 421.47 12.46 22 1 0 1 3 6 7 0 12 114

COMP 21 1 1369.58 421.47 12.46 22 1 0 1 3 6 8 0 12 115

COMP 21 0 1369.58 421.47 12.43 -2 1 0 1 3 6 9 0 12 116

Design file data in IDF order

—————————–

Name X Y Z X Y Z Occ in_cp Out_cp Leg Dn_occ Sg_occ

NOZ 33274000 10480294 501904 33274000 10480294 47752 0 7 1 2 in 26 15 Dash

BLSP 33274000 10480294 477393 33274000 10480294 475615 26 1 2 in 35 15

FWN 33274000 10480294 475615 33274000 10480294 468376 35 1 2 in 34 16

E90L 33274000 10480294 468376 33274000 10480294 450088 34 1 0 in 0 16

E90L 33274000 10480294 450088 33292288 10480294 450088 34 0 2 ou 7 16

PIPE 33292288 10480294 450088 33475168 10480294 45008 8 7 2 1 in 33 16

E90L 33475168 10480294 450088 33493456 10480294 450088 33 1 0 in 0 16

E90L 33493456 10480294 450088 33493456 10462006 450088 33 0 2 ou 6 16

PIPE 33493456 10462006 450088 33493456 10319258 45008 8 6 2 1 in 32 16

E90L 33493456 10319258 450088 33493456 10300970 450088 32 1 0 in 0 16

E90L 33493456 10300970 450088 33475168 10300970 450088 32 0 2 ou 5 16

PIPE 33475168 10300970 450088 33407350 10300970 45008 8 5 2 1 in 29 16

T 33407350 10300970 450088 33395920 10300970 450088 29 1 0 in 0 16

T 33395920 10300970 450088 33395920 10300970 438658 29 0 3 b1 103 14

PIPE 33395920 10300970 438658 33395920 10300970 417449 103 2 1 in 305 14

FWN 33395920 10300970 417449 33395920 10300970 410210 305 2 1 in 25 14


GAT 33395920 10300970 410210 33395920 10300970 388620 25 2 1 in 24 14

STRT 33395920 10300970 388620 33395920 10300970 370078 24 2 0 in 0 14

STRT 33395920 10300970 370078 33379283 10300970 370078 24 0 3 b1 28 13

FBLD 33379283 10300970 370078 33378140 10300970 370078 28 1 0 in 0 13 End

STRT 33395920 10300970 370078 33395920 10300970 351536 24 0 1 ou 23 11

FWN 33395920 10300970 351536 33395920 10300970 344297 23 1 2 in 22 11

E90L 33395920 10300970 344297 33395920 10300970 326009 22 2 0 in 0 11

PSP2 33395920 10300970 326009 33395920 10300970 29984 7 4 1 2 in 0 11

E90L 33395920 10300970 326009 33395920 10282682 326009 22 0 1 ou 17 11

REDE 33395920 10282682 326009 33395920 10271506 328168 17 1 2 in 16 11

REDE 33395920 10277094 327089 33395920 10277094 321501 17 0 3 ta 18 12

NIP 33395920 10277094 321501 33395920 10277094 315405 18 1 2 in 19 12

GATR 33395920 10277094 315405 33395920 10277094 309817 19 1 2 in 20 12

NIP 33395920 10277094 309817 33395920 10277094 303721 20 1 2 in 21 12

CAPO 33395920 10277094 303721 33395920 10277094 303213 21 1 0 in 0 12 End

FWN 33395920 10271506 328168 33395920 10264521 328168 16 2 1 in 3 9

NOZ 33395920 10264394 328168 33395920 10258298 32816 8 3 2 1 in 0 9 End Dash

T 33395920 10300970 450088 33384490 10300970 450088 29 0 2 ou 3 17

PIPE 33384490 10300970 450088 33255712 10300970 45008 8 3 1 2 in 30 17

E90L 33255712 10300970 450088 33237424 10300970 450088 30 2 0 in 0 17

E90L 33237424 10300970 450088 33237424 10300970 431800 30 0 1 ou 4 8

PIPE 33237424 10300970 431800 33237424 10300970 41744 9 4 1 2 in 31 8

FWN 33237424 10300970 417449 33237424 10300970 410210 31 2 1 in 15 8

GAT 33237424 10300970 410210 33237424 10300970 388620 15 2 1 in 14 8

STRT 33237424 10300970 388620 33237424 10300970 370078 14 2 0 in 0 8

STRT 33237424 10300970 370078 33220787 10300970 370078 14 0 3 b1 27 7

FBLD 33220787 10300970 370078 33219644 10300970 370078 27 1 0 in 0 7 End

STRT 33237424 10300970 370078 33237424 10300970 351536 14 0 1 ou 13 5

FWN 33237424 10300970 351536 33237424 10300970 344297 13 1 2 in 12 5

E90L 33237424 10300970 344297 33237424 10300970 326009 12 2 0 in 0 5

PSP2 33237424 10300970 326009 33237424 10300970 29984 7 3 1 2 in 0 5

E90L 33237424 10300970 326009 33237424 10282682 326009 12 0 1 ou 7 5

REDE 33237424 10282682 326009 33237424 10271506 32816 8 7 1 2 in 6 5

REDE 33237424 10277094 327089 33237424 10277094 32150 1 7 0 3 ta 8 6

NIP 33237424 10277094 321501 33237424 10277094 31540 5 8 1 2 in 9 6

GATR 33237424 10277094 315405 33237424 10277094 30981 7 9 1 2 in 10 6

NIP 33237424 10277094 309817 33237424 10277094 303721 10 1 2 in 11 6

CAPO 33237424 10277094 303721 33237424 10277094 303213 11 1 0 in 0 6 End

FWN 33237424 10271506 328168 33237424 10264521 32816 8 6 2 1 in 1 3

NOZ 33237424 10264394 328168 33237424 10258298 32816 8 1 2 1 in 0 3 End Dash


__________________________________________________________________________________________________________________________________________________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 rawdesign data. The basic input data consists of the date the report wasexecuted, project name and a list of model names that were extracted.

Each column of the raw design file data is described below.

Name The first four characters of the component item name.

occ The component database occurrence number (excluding the partitionnumber).

Note that some PIPE components have an occurrence number greater than30000. This occurs whenever olet type components are attached to a pipe.The software breaks these pipes into multiple sections. The newly createdpieces of pipe receive occurrence numbers in the 30000+ range to distinguishthem from the original pipe.

cp # The connect point number

x,y,z The coordinate in the design file coordinate system and is not adjusted for theglobal origin

node A node number assigned to all connect points other than the origin. A specialnode number, -1, is reserved for line endpoints. Two connect points that havethe same node number are connected to each other in the model.

direct A direction list number. The direction list number identifies all those connectpoints that lie together on a straight line.

sect Section number [always 0]

flags A bit mask used internally by the software

topo Topos [always 0]

branch Branch flag [always 0]

sg_occ The segment occurrence number. All connect points belong to or are ownedby a segment in the piping model. This is the occurrence number of thatowner segment.


__________________________________________________________________________________________________________________________________________________4.3 Section 2: Design File Data Sorted by Coordinate

The second section of the HITS report consists of raw design file data for eachconnect point of the piping components that make up the network that isbeing extracted. The database search criteria from section 1 is used to findall of the appropriate segments. Once the segments are found, the softwarecollects all of the components that are attached to the segments. Section 2 isthe result of this activity.

Section 2 contains several columns of data. Each column is described below:

Name Is the first four characters of the component item name.

occ The database occurrence number of the component (excluding the partitionnumber). [Note that some PIPE components have an occurrence numbergreater than 30000. This occurs whenever olet type components are attachedto a pipe. The software "breaks" these pipes into multiple sections. Thenewly created pieces of pipe receive occurrence numbers in the 30000+ rangeto distinguish them from the original pipe.]

cp # The connect point number.

x,y,z The coordinate in the design file coordinate system and is unadjusted for theglobal origin.

node A node number assigned to all connect points other than the origin. A specialnode number , -1, is reserved for line endpoints. Note that two connect pointsthat have the same node number are "connected" to each other in the model.

direct A direction list number. The direction list number identifies all those connectpoints that lie together on a straight line.

sect Always 0 here. Section number is described later in this section.

flags A bit mask used internally by the software.

topo Always 0 here. Topos are discussed later in this section.

branch- Always 0 here. The branch flag is discussed later in this section.

sg_occ- The segment occurrence number. All connect points "belong to" or "areowned" by a segment in the piping model. sg_occ is the occurrence number ofthat owner segment.

Section 2 is primarily used for examining the amount of data pulled in fromthe models through the database search criteria. Some of the data for aspecific connect point is sometimes useful — particularly the occurrencenumber.


__________________________________________________________________________________________________________________________________________________4.4 Section 3: Tracing Data

Section 3 of the report, Tracing Data is a record of the actions the software istaking in building the internal data structure of the piping network. Thissection is primarily useful to Intergraph for investigating software problems.

The last statement in section 3 states how many disconnected sections ofpiping exist in the network identified in the database search criteria. If thenumber of sections is greater than 1 then the line is not extracted and theintermediate 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 bedisconnected and some suggested solutions:

1. The database search criteria identified more than one pipeline and thepipelines are not connected together. The solution here is to change thesearch criteria so that only the piping that you really want to extract ispulled in.

2. The pipeline being extracted is incomplete and portions of it do not havecomponents on it. The solution is to place all of the components on theline.

3. Although the line is finished, there is a part of it that appears to beconnected but really is not. To be considered connected, the connectpoints from two different components must be within about 20 uors ofeach other.

In this case you should examine section 2 of the HITS report to find aconnect point whose node number is -1 (which indicates that it is a lineendpoint) even though you know it should be connected to something.This is usually quite simple when the line is small. When you find theconnect point, use the coordinate to view and repair the disconnectedgraphics. When the line is complicated, you can use section 4 of theHITS report (see the section Tracing Data) to make a sketch thatidentifies 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 sectionis really a print—out of the internal data structure that represents the pipingnetwork. This data is organized on the basis of topos.

A topo is a construction used to group the data representing the pipelinetopology. By definition a topo is a string of piping that starts at a networkendpoint or a branch point and ends at a network endpoint or another branchpoint. A pipeline network may consist of a single topo or dozens of toposdepending 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 anybranch points. The beginning of the topo is a line endpoint as is the end ofthe topo.


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 (theheader of the pipeline). The second topo consists of the piping from the centerof 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 init. 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 toendpoint 3. The third topo consists of the line from connect point 1 ofweldolet 2 to endpoint 4.


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 lineheader from endpoint 1 to endpoint 2. The other topo starts at the center ofone 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 nodenumbers — they should be ignored. Subsequent to the lines where the toponumber 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 inconnect points with the same node number being adjacent to each other inthe report. The result is that section 4 of the HITS report contains a trace ofeach topo of the line.


Example 1:

The following is an excerpt from a HITS report section 4:

Name cp# node topo

E90L 1 -1 1E90L 2 1 1PIPE 1 1 1PIPE 2 2 1E90L 2 2 1E90L 1 3 1PIPE 2 3 1PIPE 1 4 1GATR 1 4 1GATR 2 5 1PIPE 1 5 1PIPE 2 -1 1

This trace consists of a single topo. The first endpoint is connect point 1 of a90 degree elbow. Connect point 2 of the elbow is connected to connect point 1of a pipe. Following this logic, the sequence of components starting from thetop is: elbow -> pipe -> elbow -> pipe -> valve -> pipe.

This same procedure may be followed to sketch out each network topo. Toposketches are useful if you are interested only in the sequence of componentsin 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 thereport. The branch column is used together with the last column. The lastcolumn in section 4 is a report line number. You can see by looking back atFigure 4-1 that the last column starts out at 1 and is incremented for eachline in section 4. When the branch column contains a nonzero value then thisindicates that the node is a branch point. The value of branch refers you tothe line number of the report where the connecting topo begins.

Example 2:

The following is an excerpt from a HITS report section 4:

Name occ# cp# node topo branch

PIPE 10 1 -1 1 0 1PIPE 10 2 1 1 5 2PIPE 30001 1 1 1 5 3PIPE 30001 2 2 1 0 4WOL 15 1 1 2 -2 5WOL 15 2 3 2 0 6PIPE 35 1 3 2 0 7PIPE 35 2 -1 2 0 8

The network is composed of two topos. Topo 1 is simply two pipes. Topo 2consists of a weldolet connected to a piece of pipe. Note that the occurrencenumber of the second pipe in topo 1 indicates the model contains a single pipe


which the software split into two at the olet. Figure 4-5 shows the Networkfor 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 seethat 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 totopo 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 indicatesthat this is a "back pointer". The back pointer is exactly the same as anyother branch value except that it (usually) points back to a previous toporather than forward to a subsequent topo. Note that where two or more toposare connected together the branch numbers must agree. In Example 5 theydo. The back pointer on topo 2 points back to line 2 while the forward pointeron topo 1 points to line 5.

In Example 2, the branch flag pointed to the start point of the connectingtopo. It can also happen that the branch flag points to the endpoint of theconnecting topo. In this case you traverse the topo in reverse order.

Example 3:

Name occ# cp# node topo branch

.

.

.PIPE 10 1 20 3 0 20PIPE 10 2 21 3 0 2190E 35 2 21 3 0 22


90E 35 1 22 3 0 23PIPE 46 1 22 3 0 24PIPE 46 2 23 3 53 25PIPE 30003 1 23 3 53 26PIPE 30003 2 24 3 0 27

.

.

.PLUG 76 2 -1 7 0 46PLUG 76 1 10 7 0 47BLV 82 1 10 7 0 48BLV 82 2 11 7 0 49NIPL 103 2 11 7 0 50NIPL 103 1 12 7 0 51SOL 110 2 12 7 0 52SOL 110 1 23 7 -25 53

.

.

.

In Example 3, topo 3 consists of pipe, elbow, pipe, pipe. Topo 7 is a typicaldrain assembly— plug, block valve, nipple, sockolet. Topo 7 connects to topo3 at line 53 in the report (the value of branch on line 25 is 53 and the value ofbranch of line 53 is -25). In this case, the value of branch on topo 3 points tothe bottom of topo 7 and the network structure is obtained by moving up topo3 rather than down (See Figure 4-6).



Example 4:

The following data is from section 4 of a HITS report:

Name Occ cp# Node Topo Branch

90E 37 1 -1 1 0 190E 37 2 1 1 0 2PIPE 101 1 1 1 0 3PIPE 101 2 2 1 0 4FLWN 22 2 2 1 0 5FLWN 22 1 3 1 0 6GAT 54 1 3 1 0 7GAT 54 2 4 1 0 8FLWN 11 1 4 1 0 9FLWN 11 2 5 1 0 10T 36 1 5 1 15 11T 36 2 6 1 15 12PIPE 11 1 6 1 0 13PIPE 11 2 -1 1 0 14T 36 3 7 2 -11 15PIPE 12 1 7 2 0 16PIPE 12 2 -1 2 0 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 nodenumbers do not match where topo 2 connects to topo 1. This is a consequenceof the fact that node numbers are not assigned to component origins. SeeFigure 4-7 which shows the Network for Example 4.

Figure 4 - 7. Network for example 4


Example 5:


PIPE 23 1 -1 1 0 1PIPE 23 2 1 1 0 2REDE 24 1 1 1 7 3REDE 24 2 2 1 11 4PIPE 13 1 2 1 0 5PIPE 13 2 -1 1 0 6SOL 56 1 3 2 -3 7SOL 56 2 4 2 0 8PIPE 42 1 4 2 0 9PIPE 42 2 -1 2 0 10PIPE 26 1 5 3 -4 11PIPE 26 2 -1 3 0 12

In Example 5, topo 1 consists of a pipe connected to an eccentric reducerwhich in turn is connected to another pipe. Notice, however, that the branchflag is set to two different numbers on the reducer. This indicates that thereducer is tapped twice. The branch flag on the first connect point points tothe topo connected at the first tap while the branch flag on the second connectpoint points to the topo connected to the second tap. A tap is always a branchstarting point and thus is always the start point of a new topo. Refer toFigure 4-8, which shows the network for Example 5.


If you generate some HITS reports and practice sketching out the pipelinenetworks, you will become familiar with the report contents and betterunderstand the concepts presented in the examples above.


__________________________________________________________________________________________________________________________________________________4.6 Section 5: Design File Data in STR Order

Section 5 of the HITS report contains a record of how the network istraversed as the neutral file is being generated. The software examines thenetwork of piping and chooses the best (that is, the one least likely to result inproblems from PDSTRESS) topo to begin the network traversal on.PDSTRESS prefers certain navigation sequences over others and theinterface software tries to choose the optimal sequence.

PDSTRESS also requires that the traversal of the network be branch firstorder. 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 headertopo and travel connect point by connect point until the value of branch isgreater than 0 at some node. When branch is positive then you jump down tothe new topo and start traversing it until you come to another branch or tothe end. If you encounter another branch then you must jump again toanother topo. When the end of the topo is found then you return to the topofrom which you jumped and continue tracing.

Example 6:

The following is an example of a network:


PIPE 10 1 -1 1 0 1PIPE 10 2 1 1 0 2T 11 1 1 1 7 3T 11 2 2 1 7 4PIPE 12 1 2 1 0 5PIPE 12 2 -1 1 0 6T 11 3 3 2 -3 7PIPE 13 1 3 2 0 8PIPE 13 2 -1 2 0 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 thefollowing trace:

Name Occ cp in cp out Leg

PIPE 10 1 2 1T 11 1 0 1T 11 0 3 2PIPE 13 1 2 1T 11 0 2 4PIPE 12 1 2 1


Step 1 travels from one end of the first pipe to the other. Following the firstpipe we travel into the tee. Notice that although the origins do not have nodenumbers 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 theorigin in step 2. At this point the branch flag is positive and so a jump occursto 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 pipewhich is the last component on the topo. We then jump back to topo 1 and instep 5 travel from the tee origin to connect point 2. Finally, in the last stepwe traverse the remaining pipe on topo 1. Refer to Figure 4-9 for anillustration of this traversal.

The header topo number can be found by examining the first line in thetraversal. In this case the first line consists of PIPE — occurrence 10.Looking at the network description, observe that PIPE — occurrence 10 is ontopo 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 componentleg. Straight through components like pipe, flanges, and valves consist of oneleg. Change of direction components like elbows, angle valves and so onconsist of two legs. Branch components like tee’s, olets, 3-way and 4-wayvalves and crosses consist of three or four legs. In Example 9, the last leg ofthe tee is given a leg number of 4. By definition only 4-way components havea leg 3 (which would correspond to the 2nd branch leg).

Branches off from components formed by taps are termed branch legs and arenot given a number. Branch legs are treated as other branches are though.When a tapped component is encountered in the network then all the tappedlegs must be traced before continuing down the topo. Although olet typecomponents have a different connect point skeleton than tee’s do they aretreated similarly in the network trace. This is highlighted in the nextexample:


Example 7:

The following is a network:


90E 8 1 -1 1 0 190E 8 2 1 1 0 2PIPE 10 1 1 1 0 3PIPE 10 2 2 1 7 4PIPE 30001 1 2 1 7 5PIPE 30001 2 -1 1 0 6WOL 6 1 1 2 -4 7WOL 6 2 2 2 0 8PIPE 9 2 2 2 0 9PIPE 9 1 -1 2 0 10

The network trace for this network is:

Name Occ cp in cp out leg

90E 8 1 0 190E 8 0 2 2PIPE 10 1 2 1WOL 6 1 1 1WOL 6 1 2 2PIPE 9 2 1 1WOL 6 1 1 4

In Example 7, the first leg of the olet goes from connect point 1 to connectpoint 1. It is analogous to the step with the tee where traversal goes fromconnect point to the origin. In this case the traversal does not go anywhereand therefore is called a zero length leg. The second leg traverses from cp1 tocp2 — analogous to the previous example’s traversal from the tee origin tocp3. After the branch topo has been traversed we return to the olet for leg 4which again goes from cp1 to cp1 — another zero length leg. This step isanalogous to going from the origin to cp3 in the previous example.

Notice also the traversal through the elbow. Since the elbow causes a changeof direction, it is traversed in two legs: 1) from cp1 to the origin and 2) fromthe origin to cp2.

Sometimes the traversal of the network requires traveling into the branch legof a branch component. When this happens the leg numbers are assignedsomewhat differently on the branch component.


Example 8:

The following is a partial network:


.

.

.PIPE 10 1 20 4 0 46PIPE 10 2 21 4 0 47T 15 3 21 4 -61 48

.

.

.PIPE 12 1 -1 7 0 59PIPE 12 2 52 7 0 60T 15 1 52 7 48 61T 15 2 53 7 48 62PIPE 17 2 53 7 0 63PIPE 17 1 -1 7 0 64

In Example 8, a lower numbered topo (topo 4) contains a back pointer to ahigher numbered topo (topo 7). Whenever this happens, the traversal willenter branch.

The trace for this part of the network would be:

Name Occ cp in cp out leg

PIPE 1 0 1 2 1T 15 3 0 1T 15 0 1 2PIPE 1 2 2 1 1T 15 0 2 4PIPE 1 7 2 1 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 goeither way (PDSTRESS has no preference). Refer to Figure 4-10 which showsthis network traversal.

Figure 4 - 10. Network traversal in example 8


__________________________________________________________________________________________________________________________________________________4.7 Using the HITS Report to Solve Problems

When you have difficulty extracting a line, the first thing you should do inanalyzing the problem is to sketch out the network. Often this is enough toidentify 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 pointersappear incorrect — then PDSTRESS’s input will be wrong and the drawingwill definitely be incorrect.

When the data structure represented in section 4 of the report is incorrectthen you can conclude that either the interface has a bug or there is aproblem in the model. Typical model problems include such things asdisconnected sections and overlapping components or pipes.

When the modeler has inadvertently placed two pipes on top of each otheryou will get an error message at the top of the HITS report stating this. Themessage will also report a node number where the problem was detected. Bygetting the coordinate of the node you can pinpoint where in the model theproblem occurs. This can also occur where the connect points of componentsoverlap each other and are not properly connected.

Notice that one of the columns in section 4 of the report is called section. In acorrect 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 foreach section should be sketched out. It should be apparent after doing thiswhere 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 becolinear are not. This is detected by examining the direction list number. Ifthe direction list changes for example from one pipe to another then aproblem exists in the model and the line can not be extracted properly.

Mismatches between the design file and database can also cause isoextraction failures but these types of problems should be trapped andreported adequately in other areas of the software. You should not need torely on the HITS report to find these kinds of problems.

When the data structure in section 4 of the report is correct then thetraversal in section 5 should be examined. Even if the network is correct,some other bug can cause the network traversal to fail. Again, if thetraversal is incorrect then PDSTRESS will definitely fail. When both thenetwork and the traversal are correct, there is most likely a problem withPDSTRESS.

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


When this happens there is usually some option or combination ofoptions that have been enabled that resulted in the problem. The bestway to find the cause of the problem is to start with a basic drawinggeneration setup that contains few "special" options. Then add a fewoptions at a time until the problem is reproduced. Finally, through aprocess 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 thishappens it is usually the case that disabling options will not result inthe drawing working — though sometimes it does. The best thing to dowhen this happens is to try and reextract a smaller portion of the line ifpossible. The failure should also be reported to Intergraph.

When any sheet of an PDSTRESS drawing fails, ALL sheetsfrom the same pipeline may contain errors and are suspect.


The Stress Analysis Neutral File 5 - 1

__________________________________________________________________________________________________________________________________________________5. The Stress Analysis Neutral File


__________________________________________________________________________________________________________________________________________________5.1 Neutral File Format

The neutral file produced by the PD_Stress Analysis Interface consists ofeight sections of data. Each section of the file is composed of one or morerecords in the neutral file. Each record is composed of several fields. Fieldsin neutral file records are separated by commas.

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

Different sections of the file are related to each other through pointers. Forexample, temperatures and pressures stored at the segment level in a 3Dmodel 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 recordsbegin with PROP. A common text string (the pointer) in each of the recordtypes 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) listingall of the model files and line names used in the extraction. The date andtime of the run is also included.

Section 2 Single record containing fields that identify the run. (Use of this record isnot fully supported at this time.)

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

The second field contains a segment ID or pointer that is used to associate aset of temperatures and pressures with a given component. More than oneLOAD record may be generated for a segment depending on how manytemperature/pressure pairs you put on a single record.

Section 4 Records that begin with the keyword LSET. These records specify thetemperature/pressure pair used from each segment when analyzing the linefor different loading conditions (that is, deadweight, cold condition, hotcondition and wind condition cases). The PD_Stress Analysis Interface putsvalues in these records based upon criteria you specified in the defaults file.(Refer to the Defaults File section for more information.)

Section 5 Records beginning with keyword CODE. A CODE record is generated foreach unique value of the analysis code attribute stored in the pipingsegment entities. Each component has a pointer pointing back to one ofthese CODE records.


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 thePDS to Stress Interface Symbol Map.

The second field contains a component ID or pointer that groups this recordwith the records that follow for the same component. This first record alsocontains network connectivity information through a list of node numberscorresponding to the component. Node numbering conventions forcomponents are discussed later in this section.

Following this first record are a series of records each of which begin withthe keyword PROP. Each PROP record contains the component ID pointingback to the overall component record. Each of these records also has a formtype 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 mightcontain the bend radius and the bend angle.

- connect point data. This data includes size and schedule. It alsoincludes the segment pointer that associates each connect point withLOAD and LSET records.

Section 7 Records beginning with the keyword LNOD. These records are generatedat equipment nozzles (indicating that the nozzle is an anchor) and whendata associated with a pipe support indicates that the support is acting as anode restraint. When a support acts only as a restraint, the componentrecords are not generated for it. LNOD records define which directionsand/or rotations are restrained at a node.

Section 8 Records beginning with the keyword NODE. These records hold thecoordinate of each node in the network.

The overall file structure is outlined in general form below:

!! Comments!

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

.

.

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

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

.

.

.LSET, SEGIDn, ...


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

.

.

.CODE, CODEIDn, ...

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

.

.

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

.

.

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

.

.

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

.

.

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

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

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

.

.

.NODE, Nn, xn, yn, zn

Within the form or skeleton outlined above, you can map attributes from thedatabase into the neutral file by modifying the stress analysis defaults file.


__________________________________________________________________________________________________________________________________________________5.2 Detailed Record Descriptions

LOAD LNODLSET NODECODE

__________________________________________________________________________________________________________________________________________________5.2.1 LOAD Record

The general LOAD record format is:

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

where:

LOAD is the record keyword (MLOAD for metric models)

segid is a pointer used to associate a LOAD record with each component in thepiping network

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

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

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

Example

LOAD, 1117654, 1, 3, 100, 150, 100, 175, 300, 200LOAD, 1117654, 4, 6, 175, 200, 175, 250, 225, 250

In this example, the segment ID is 1117654. The first LOAD record definesT,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 containingpairs 1 through 6, though the record would most likely be longer than 80characters.

__________________________________________________________________________________________________________________________________________________5.2.2 LSET Record

The general format of the LSET record is as follows:

LSET, segid, s1, s2, s3, s4

where:


LSET is the record keyword

segid is the segment pointer used to associate an LSET record with eachcomponent in the piping network

s1 identifies the T,P pair used when analyzing under case 1 conditions (forexample, deadweight)

s2 identifies the T,P pair used when analyzing under case 2 conditions (forexample, hot)

s3 identifies the T,P pair used when analyzing under case 3 conditions (forexample, cold)

s4 identifies the T,P pair used when analyzing under case 4 conditions (forexample, wind)

In the defaults file, you can either hard code the numbers that are actuallyplaced in LSET records for each segment or you can set them based upon thevalue of any attribute stored in the segment. Refer to the Default File sectionfor more information.

__________________________________________________________________________________________________________________________________________________5.2.3 CODE Record

The general format of a code record is:

CODE, codeid, string

where:

CODE is the record keyword

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

string is a string defining the analysis code name

Example

CODE, CODE6, ASME2 1977 B

In this example, the code ID is the string CODE6 formed by appending thecode list number from the segment attribute that defines the code to thecharacters CODE.

The string ASME2 1977 B is defined by you in the defaults. The definitionstates that when the code attribute in the segment is set to code list number6, a given string is generated in the neutral file CODE record.


__________________________________________________________________________________________________________________________________________________5.2.4 Component Records

Overall ComponentPROP

__________________________________________________________________________________________________________________________________________________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 symbolmap

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

codeid is the label pointing back to a particular CODE record

data is a list of component attributes defined by you in the defaults file thatapply to the component as a whole and are not specific to the componenttype. These attributes may come from either the segment or componententities.

nodes is the node list for the component. The node list defines the node numbersfor each node of the component. The number of nodes in the node list is afunction of the component type. The nodes are ordered in the list so thatthe first corresponds to connect point 1, the second to connect point 2 andso on. Refer to the Node Numbering Conventions section for moreinformation.

__________________________________________________________________________________________________________________________________________________5.2.4.2 PROP Record

The general form of a PROP record is:

PROP, name, compid, form, data

where:

PROP is the record keyword (MPROP for metric models)

name is the component name and is the same name as appears on the overallcomponent record.


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

component record

form is a form number you defined in the defaults file. The component nametogether with the form number uniquely defines the data that follows onthe record.

data is a list of attributes you defined in the defaults file. Each component typeand form number combination has its own set of attributes.

__________________________________________________________________________________________________________________________________________________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 is the record keyword

node is the restrained node number

type identifies the action taking place at the node. Currently the only allowedvalue for this item is RE (for restraint).

Dx is set to 1 if the node is restrained in the x direction and 0 if not

Dy is set to 1 if the node is restrained in the y direction and 0 if not

Dz is set to 1 if the node is restrained in the z direction and 0 if not

Ax is set to 1 if rotation is restrained about the x axis and 0 if not

Ay is set to 1 if rotation is restrained about the y axis and 0 if not

Az 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 boththe positive and negative directions.

When Intergraph option switch 17 is set to a one a second LNOD record willbe generated with the following format.

LNOD, node, type, service, NX, NY, NZ, AX, AY, AZ

where:

LNOD is the record keyword

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

service identifies the service condition. Currently the only allowed value for thisitem is 1.

NX is the nozzle normal thermal growth in the X direction. Refer to theequipment schema table 22 column 19.

NY is the nozzle normal thermal growth in the Y direction. Refer to theequipment schema table 22 column 20.

NZ is the nozzle normal thermal growth in the Z direction. Refer to theequipment schema table 22 column 21.

AX is the nozzle alternate thermal growth in the X direction. Refer to theequipment schema table 22 column 22.

AY is the nozzle alternate thermal growth in the Y direction. Refer to theequipment schema table 22 column 23.

AZ is the nozzle alternate thermal growth in the Z direction. Refer to theequipment schema table 22 column 24.

__________________________________________________________________________________________________________________________________________________5.2.6 NODE Record

The general format of the NODE record is:

NODE, node, x, y, z, flag, intens

where:

NODE is the record keyword (MNODE with a metric model)

node is the node number of the node

x,y,z is the coordinate of the node in subunits (in or mm)

flag is a coordinate system identifier

intens is a stress intensification factor to be applied to the node. This value is notcalculated but taken from a database attribute you already set.


__________________________________________________________________________________________________________________________________________________5.3 Node Numbering Conventions

The last set of fields generated on each overall component record is the nodenumber set for the component. The node number set identifies the nodenumber of each node on a component. The following conventions are used inassigning 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 componentswill 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 isgenerated at the valve center. If the valve operator has a center-of-gravity 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 generatedat 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 atthe component origin.

Eccentric reducers

Nodes 1 and 2 correspond to the two connect points. Elements 3, 4, and5 in the node list are the components of a vector that orients the flatside of the reducer.

Two-way valves

Nodes 1 and 2 are generated at the connect points. Node 3 is generatedat 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 thevalve. Node 3 is generated at the branch connect point and node 4 isgenerated at the component center. If the valve operator has a center ofgravity defined, node 5 is generated at the center of gravity.


Pipe supports

Pipe supports that are not converted to node restraints by the interfacewill have two nodes. The first node is generated at the point that thepipe support attaches to the pipe line. The second node is a dummynode and simply defines an orientation for the support.

To a certain extent, you can control the node numbers assigned to nodes. Youdo this using the defaults file options. The PD_Stress Analysis Interfacedistinguishes 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 touse in generating the next node number. Refer to the Defaults File sectionfor more information.


__________________________________________________________________________________________________________________________________________________5.4 Example Neutral File

! Model Design file(s) : sriso03! Line name(s) : 3002! Date : 22-MAY-91 20:16:31

DRAW ,3002,3002LOAD, 300001G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LOAD, 300001G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LSET, 300001G,3,6,5,3LOAD, 300002G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LOAD, 300002G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LSET, 300002G,3,6,5,3LOAD, 300005G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LOAD, 300005G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LSET, 300005G,3,6,5,3LOAD, 300006G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LOAD, 300006G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LSET, 300006G,3,6,5,3LOAD, 300003G, 1, 3, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LOAD, 300003G, 4, 6, 0.00, 0.00, 0.00, 0.00, 0.00, 0.00LSET, 300003G,3,6,5,3CODE,CODE0,B31.1,1983FL, 3300001,4"STDFAAABAWAAA,,CODE0, 901, 1PROP,FL, 3300001, 1,A105,15.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300001, 3,4.,9.000000,WN,0.,CL150, 300001GPROP,FL, 3300001, 4,4.,4.500000,BW,0.237,CL150, 300001GER, 3300002,6"x4"STDWRBAAAWAAA,,CODE0, 3, 1, 0, 0.00, 0.00, -1.00PROP,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,, 300002GPROP,ER, 3300002, 4,4.,4.500000,BW,0.237,, 300001GPI, 5300001,6"STDPAAAAAWAAA,,CODE0, 3, 5PROP,PI, 5300001, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00PROP,PI, 5300001, 3,6.,6.625000,BW,0.28,, 300002GPROP,PI, 5300001, 4,6.,6.625000,BW,0.28,, 300002GFL, 3300003,6"STDFAAABAWAAA,,CODE0, 7, 5PROP,FL, 3300003, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300003, 3,6.,11.000000,WN,0.,CL150, 300002GPROP,FL, 3300003, 4,6.,6.625000,BW,0.28,CL150, 300002GFL, 3300004,6"STDFAAABAWAAA,,CODE0, 7, 9PROP,FL, 3300004, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300004, 3,6.,11.000000,WN,0.,CL150, 300002GPROP,FL, 3300004, 4,6.,6.625000,BW,0.28,CL150, 300002GEL, 3300005,6"STDWAAAAAWAAA,,CODE0, 9, 12, 951PROP,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,, 300002GPROP,EL, 3300005, 4,6.,6.625000,BW,0.28,, 300002GFL, 3300006,6"STDFAAABAWAAA,,CODE0, 13, 12PROP,FL, 3300006, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300006, 3,6.,11.000000,WN,0.,CL150, 300002GPROP,FL, 3300006, 4,6.,6.625000,BW,0.28,CL150, 300002GVA, 3300007,6"VAABAHCCAA,,CODE0, 13, 14, 952PROP,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, 300002GPROP,VA, 3300007, 4,6.,0.000000,WN,0.,CL150, 300002GFL, 3300008,6"STDFAAABAWAAA,,CODE0, 14, 15PROP,FL, 3300008, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.


PROP,FL, 3300008, 3,6.,11.000000,WN,0.,CL150, 300002GPROP,FL, 3300008, 4,6.,6.625000,BW,0.28,CL150, 300002GTE, 3300013,6"STDWTAAAAWAAA,,CODE0, 16, 18, 24, 953PROP,TE, 3300013, 1,A234-WPB,29.000000,-32768.000000,0.000000,0,0,0.PROP,TE, 3300013, 2,0.000000,0.0,90.000000PROP,TE, 3300013, 3,6.,6.625000,BW,0.28,, 300002GPROP,TE, 3300013, 4,6.,6.625000,BW,0.28,, 300005GPROP,TE, 3300013, 5,6.,6.625000,BW,0.28,, 300006GPI, 5300006,6"STDPAAAAAWAAA,,CODE0, 16, 15PROP,PI, 5300006, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00PROP,PI, 5300006, 3,6.,6.625000,BW,0.28,, 300002GPROP,PI, 5300006, 4,6.,6.625000,BW,0.28,, 300002GHA, 8300001,psupport,SPT-001,CODE0, 954, 902PROP,HA, 8300001, 1,,0.000000,99,0PROP,HA, 8300001, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000PROP,HA, 8300001, 4,1.,0.,0.,0.,0.,-1.HA, 8300003,psupport,SPT-003,CODE0, 955, 903PROP,HA, 8300003, 1,,0.000000,99,0PROP,HA, 8300003, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000PROP,HA, 8300003, 4,0.,1.,0.,0.,0.,-1.FL, 3300009,4"STDFAAABAWAAA,,CODE0, 904, 2PROP,FL, 3300009, 1,A105,15.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300009, 3,4.,9.000000,WN,0.,CL150, 300003GPROP,FL, 3300009, 4,4.,4.500000,BW,0.237,CL150, 300003GER, 330000A,6"x4"STDWRBAAAWAAA,,CODE0, 4, 2, 0, 0.00, 0.00, -1.00PROP,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,, 300005GPROP,ER, 330000A, 4,4.,4.500000,BW,0.237,, 300003GPI, 5300002,6"STDPAAAAAWAAA,,CODE0, 4, 6PROP,PI, 5300002, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00PROP,PI, 5300002, 3,6.,6.625000,BW,0.28,, 300005GPROP,PI, 5300002, 4,6.,6.625000,BW,0.28,, 300005GFL, 330000B,6"STDFAAABAWAAA,,CODE0, 8, 6PROP,FL, 330000B, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 330000B, 3,6.,11.000000,WN,0.,CL150, 300005GPROP,FL, 330000B, 4,6.,6.625000,BW,0.28,CL150, 300005GFL, 330000C,6"STDFAAABAWAAA,,CODE0, 8, 10PROP,FL, 330000C, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 330000C, 3,6.,11.000000,WN,0.,CL150, 300005GPROP,FL, 330000C, 4,6.,6.625000,BW,0.28,CL150, 300005GEL, 330000D,6"STDWAAAAAWAAA,,CODE0, 10, 22, 956PROP,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,, 300005GPROP,EL, 330000D, 4,6.,6.625000,BW,0.28,, 300005GFL, 330000E,6"STDFAAABAWAAA,,CODE0, 21, 22PROP,FL, 330000E, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 330000E, 3,6.,11.000000,WN,0.,CL150, 300005GPROP,FL, 330000E, 4,6.,6.625000,BW,0.28,CL150, 300005GVA, 330000F,6"VAABAHCCAA,,CODE0, 21, 20, 957PROP,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, 300005GPROP,VA, 330000F, 4,6.,0.000000,WN,0.,CL150, 300005GFL, 3300010,6"STDFAAABAWAAA,,CODE0, 20, 19PROP,FL, 3300010, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300010, 3,6.,11.000000,WN,0.,CL150, 300005GPROP,FL, 3300010, 4,6.,6.625000,BW,0.28,CL150, 300005GPI, 5300005,6"STDPAAAAAWAAA,,CODE0, 18, 19PROP,PI, 5300005, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00PROP,PI, 5300005, 3,6.,6.625000,BW,0.28,, 300005GPROP,PI, 5300005, 4,6.,6.625000,BW,0.28,, 300005GHA, 8300002,psupport,SPT-002,CODE0, 958, 905PROP,HA, 8300002, 1,,0.000000,99,0


PROP,HA, 8300002, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000PROP,HA, 8300002, 4,1.,0.,0.,0.,0.,-1.FL, 3300011,6"STDFAAABAWAAA,,CODE0, 906, 28PROP,FL, 3300011, 1,A105,24.000000,-32768.000000,0.000000,0,0,0.PROP,FL, 3300011, 3,6.,11.000000,WN,0.,CL150, 300006GPROP,FL, 3300011, 4,6.,6.625000,BW,0.28,CL150, 300006GEL, 3300012,6"STDWAAAAAWAAA,,CODE0, 27, 25, 959PROP,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,, 300006GPROP,EL, 3300012, 4,6.,6.625000,BW,0.28,, 300006GPI, 5300003,6"STDPAAAAAWAAA,,CODE0, 28, 27PROP,PI, 5300003, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00PROP,PI, 5300003, 3,6.,6.625000,BW,0.28,, 300006GPROP,PI, 5300003, 4,6.,6.625000,BW,0.28,, 300006GPI, 5300004,6"STDPAAAAAWAAA,,CODE0, 25, 24PROP,PI, 5300004, 1,A53-B,0.1581E+01,0.1043E+01,,0,,0.0000E+00PROP,PI, 5300004, 3,6.,6.625000,BW,0.28,, 300006GPROP,PI, 5300004, 4,6.,6.625000,BW,0.28,, 300006GHA, 8300004,psupport,SPT-004,CODE0, 960, 907PROP,HA, 8300004, 1,,0.000000,99,0PROP,HA, 8300004, 2,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000PROP,HA, 8300004, 4,1.,0.,0.,0.,0.,-1.NODE, 1, 202.124016, 120.000000, 18.000000, 2, 0.000000NODE, 2, 202.124016, 240.000000, 18.000000, 2, 0.000000NODE, 3, 207.623524, 120.000000, 16.937500, 2, 0.000000NODE, 4, 207.623524, 240.000000, 16.937500, 2, 0.000000NODE, 5, 231.623031, 120.000000, 16.937500, 2, 0.000000NODE, 6, 231.623031, 240.000000, 16.937500, 2, 0.000000NODE, 7, 235.185039, 120.000000, 16.937500, 2, 0.000000NODE, 8, 235.185039, 240.000000, 16.937500, 2, 0.000000NODE, 9, 238.747047, 120.000000, 16.937500, 2, 0.000000NODE, 10, 238.747047, 240.000000, 16.937500, 2, 0.000000NODE, 12, 247.746555, 129.000000, 16.937500, 2, 0.000000NODE, 13, 247.746555, 132.562500, 16.937500, 2, 0.000000NODE, 14, 247.746555, 143.187500, 16.937500, 2, 0.000000NODE, 15, 247.746555, 146.750000, 16.937500, 2, 0.000000NODE, 16, 247.746555, 174.374508, 16.937500, 2, 0.000000NODE, 18, 247.746555, 185.624508, 16.937500, 2, 0.000000NODE, 19, 247.746555, 213.250000, 16.937500, 2, 0.000000NODE, 20, 247.746555, 216.812500, 16.937500, 2, 0.000000NODE, 21, 247.746555, 227.437500, 16.937500, 2, 0.000000NODE, 22, 247.746555, 231.000000, 16.937500, 2, 0.000000NODE, 24, 253.371555, 180.000000, 16.937500, 2, 0.000000NODE, 25, 291.000000, 180.000000, 16.937500, 2, 0.000000NODE, 27, 300.000000, 180.000000, 25.937500, 2, 0.000000NODE, 28, 300.000000, 180.000000, 92.375000, 2, 0.000000NODE, 901, 199.062008, 120.000000, 18.000000, 2, 0.000000NODE, 902, 247.746555, 120.000000, 12.016240, 2, 0.000000NODE, 903, 247.746555, 180.000000, 12.016240, 2, 0.000000NODE, 904, 199.062008, 240.000000, 18.000000, 2, 0.000000NODE, 905, 247.746555, 240.000000, 12.016240, 2, 0.000000NODE, 906, 300.000000, 180.000000, 95.937500, 2, 0.000000NODE, 907, 300.000000, 180.000000, 12.016240, 2, 0.000000NODE, 951, 247.746555, 120.000000, 16.937500, 2, 0.000000NODE, 952, 247.746555, 137.875000, 16.937500, 2, 0.000000NODE, 953, 247.746555, 180.000000, 16.937500, 2, 0.000000NODE, 954, 247.746555, 120.000000, 16.937500, 2, 0.000000NODE, 955, 247.746555, 180.000000, 16.937500, 2, 0.000000NODE, 956, 247.746555, 240.000000, 16.937500, 2, 0.000000NODE, 957, 247.746555, 222.125000, 16.937500, 2, 0.000000NODE, 958, 247.746555, 240.000000, 16.937500, 2, 0.000000NODE, 959, 300.000000, 180.000000, 16.937500, 2, 0.000000NODE, 960, 300.000000, 180.000000, 16.937500, 2, 0.000000



The Options File 6 - 1

__________________________________________________________________________________________________________________________________________________6. The Options File

The options file contains switches, options, and tables that drive the PD_Stress AnalysisInterface. This file gives you considerable flexibility in customizing the stress analysisneutral file.

When the input screen is first displayed on your workstation, this input field contains adefault value obtained by translating the variable name NEUDFLTS. The logical name isdefined 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 thevariable to your own customized options file.


__________________________________________________________________________________________________________________________________________________6.1 Options File Structure

The options file is composed of one set of options and several tables. The option block andeach table is preceded in the options file by a keyword identifying the option or table. Thekeyword must be in upper case and begin in column 1 and should not be surrounded bysingle quotes. The keywords and data that follow them can appear in any order in theoptions file. The end of each table is delimited by the same keyword string prefixed with thecharacters ENDOF.

Comments, identified by an ! in column one, can be placed anywhere between the twokeyword 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 bycommas. The general form for tables is:

TABLE_KEYWORDn1, n2, c1, n3, ... !here is a comment.!here is another comment.m1, m2, cm, m3, ...ENDOF TABLE_KEYWORD

where:

TABLE_KEYWORD is the table keyword

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

c1 is a character string in the first entry

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

cm- is a character string in the last entry

ENDOF TABLE_KEYWORD defines the end of the table


__________________________________________________________________________________________________________________________________________________6.2 Options File Keywords

The options file keywords include:

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

__________________________________________________________________________________________________________________________________________________6.2.1 INTERGRAPH OPTIONS BLOCK

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

Word Value Meaning

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

2 val Increment to be used in generating subsequent node numbers - startingfrom the value specified in word 1

3 val Initial node number for numbering nodes at network endpoints

4 val Initial node number for numbering nodes internal to components (forexample, the nodes at elbow origins)

5 0 Turn warning messages off1 Turn warning messages on

6 val Magnitude of spring constant indicating a support is rigid - where valimplies a magnitude of 10**val

7 1 must be set to 1


9 0 not used at this time




12 0 Extracts the network by substring of the pipeline name attribute (table

12, column 2)1 Extracts the network by stress analysis ID attribute (table 12, column

52)2 Extracts the network by equality of the pipeline name attribute (table

12, column 2)3 Extracts the network by equality of the stress analysis ID attribute

(table 12, column 52)

13 0 Does not print the UNITS record containing the length and weight unitsof the neutral file

1 Prints the UNITS record in the neutral file

14 20 Model file component connectivity tolerance in uor’s

15 0 Does not print the VERSION record containing the stress interface fileformat version number

1 Prints the VERSION record in the neutral file

16 0 Does not print the VENDOR record containing the pipe stress vendorsname

1 Prints the VENDOR record in the neutral file

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

growth of nozzles. (Refer to the equipment schema table 22 columns 19through 24 for more information)

__________________________________________________________________________________________________________________________________________________6.2.2 VENDOR NAME

The vendor name table contains the name of the pipe stress software vendor. Use 40characters maximum for the vendor name. This table is used to associate a particularoptions file with a specific pipe stress package. It results in a record in the neutral file whichcan 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. Use40 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 libraryis required and must be specified. Refer to the PDS to Stress Analysis Symbol Map for moreinformation 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 codeattribute. When the neutral file is generated, this table is entered with the value held intable 12, column 53. If a match is found, the text string from the table is put in the neutralfile 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 is the code list value from table 12, column 53

STRING 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 tableentry 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 begenerated in the record. You can not change this number or its positionin the record.

I subscript of the lowest temperature, pressure pair

J subscript of the highest temperature, pressure pair

PATT(n) table, column pair identifying the column for obtaining a pressure fromthe database

TATT(n) table, column pair identifying the column for obtaining a temperaturefrom the database

Example

The table entries below define six different pressure, temperature pairs taken from thedatabase 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


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 foranalysis 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 foreach segment. The simplest case uses the same T,P from each segment for each of thedifferent analysis conditions. A more complicated situation is also allowed where somesegment attribute dictates that a given set of P,T pairs should be used for that specificsegment.

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 becompared with VAL. The first table entry contains 0,0 for this item. Thisdefines the default set of T,P pairs to be used. If there are no other tableentries, the same T,P pairs will be used from each segment for allanalysis conditions.

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

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

DW Pressure, temperature pair for deadweight analysis of this segment

HOT Pressure, temperature pair for hot condition analysis of this segment

COLD Pressure, temperature pair for cold condition analysis of this segment

WIND Pressure, temperature pair for wind analysis of this segment

Example

The following table entries indicate the default P,T pairs be 1, 2, 3 and 4. However, whenthe 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, 412, 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 oneentry in this table for each generic stress analysis component used in the PDS to stressanalysis symbol map. The format of an element in this table is:

NAME, CAT, NODES, ONODE

where:

NAME generic component name

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

1 simple component2 valve3 support

NODES number of nodes the component generates.

ONODE defines which node in the node list is the origin node. If this item is 0, thenno node will be generated for the component origin. This item shouldalways be set so that origin nodes appear in the node list after nodes atconnect 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 theoverall component record.

__________________________________________________________________________________________________________________________________________________6.2.8 ELEMENT PROPERTY / CONNECTIVITY TABLE

This table forms the overall component records in the neutral file forms the PROP recordscontaining 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 itemname of the component and the PDS database type (component, pipe, instrument or support)identify the table entries that apply.

The format of an entry in the table is:

NAME, PDSTYP, -1, FORMNO, ATTLST


where:

NAME generic component name obtained from the PDS to stress analysissymbol map

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

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

When a generic pipe stress component can be generated from either acomponent or an instrument in the model, there must be a set of entriesin this table for each type.

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

FORMNO data list format number. This number together with the genericcomponent name allows you to identify all of the data on a particularrecord. The Intergraph options file contains form numbers adhering tothe following convention:

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

ATTLST list of table, column pairs specifying columns from which to obtainvalues to insert in output records. The table, column pairs can specifyeither segment or component level columns. The entity specified in antable, column pair must correspond to the PDSTYP of the table entry.

You can also specify one of the following special table, column pairs tomap a composite column in the output record.

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

schedule attributes0,-3 insulation unit weight (pipe only)0,-4 insulation weight (components and instruments only)0,-5 component or pipe thickness.0,-6 unique segment ID0,-7 fitting type from the FITTING NOMENCLATURE TABLE0,-8 flare radius, large end (reducer only)0,-9 large end cylinder length (reducer only)


0,-10

flare radius, small end (reducer only)

0,-11

small end cylinder length (reducer only)

0,-12

cone angle (reducer only)

0,-13

pad angle (reinforced tee only)

0,-14

unique analysis code ID (pointer to a CODE record)

0,-15

valve type from the PDS to stress analysis symbol map (valvesonly)

0,-16

valve angle (valves only)

0,-17

hanger type from the HANGER TYPE TABLE

0,-18

local coordinate system primary axis for a pipe support

0,-19

local coordinate system secondary axis for a pipe support

0,-20

end prep code from END PREPARATION TABLE

0,-21

segment length (miter elbow only)

0,-22

dry unit weight (pipe only)

0,-23

wet unit weight (pipe only)

Example

The following table entries define the contents of the overall component record and each ofthe 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 arecomponent, 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 inthe form number and the attribute pairs list. This form 1 entry includes the followingattributes:

material code (34,18)


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,-6EL, 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 thefollowing 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 generictermination type from the model database. The format of an entry in this table is:

GENTYP, TEXT

where:


GENTYP generic termination type for an end prep

TEXT two character max string identifying the end prep. This text stringshould 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 thecommodity code of the fitting. If no commodity code in the table matches that of thecomponent, the first entry in the table is used for the fitting type field in a PROP record. Theformat of an entry in this table is:

CCODE, CTYPE

where:

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

CTYPE stress analysis fitting code

__________________________________________________________________________________________________________________________________________________6.2.11 HANGER TYPE TABLE

With this table, you can assign a support type number to a pipe support based upon thevalue of the pipe support type attribute (entity 8, attribute 3).

The format of an entry in this table is:

PDSCODE, STYPE

where:

PDSCODE the PDS code number identifying the support type

STYPE support type number recognized by your stress analysis software


__________________________________________________________________________________________________________________________________________________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, 6, 1, 1, 1, 1, 1, 0, 0, 20, 0,

0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,

0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 999

ENDOF INTERGRAPH OPTIONS BLOCK

VENDOR NAME

!note: 40 characters 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 t o 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, wher e 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 it’s engineered item then (3,3), else NULL


!g.: code name of code parameter

! a. b. c. d. e. f. g. h. i. j.

PI, 2, -1, 0, 0,-2, 50,2, 0,-14, !here for user defined DDLs

!e.: material code

!f.: dry weight (dry unit weight for PI)

!g.: wet weight (wet unit weight for PI)

!h.: intensification at component center

!i.: symbol i.d.

!j.: radius of curvature (RI only)

!k.: insulation unit weight

! a. b. c. d. e. f. g. h. i. j. k.

PI, 2, -1, 1, 50,21, 0,-22, 0,-23, 0,0, 50,32, 0,0, 0,-3

!e.: OD nominal

!f.: OD

!g.: end prep code.

!h.: thickness

!i.: pressure rating

!j.: segment id

! a. b. c. d. e. f. g. h. i.

! gn type occ form npd od endP thick rating seg id

PI, 2, -1, 3, 50,7, 50,8, 0,-20, 0,-5, 50,11, 0,-6

PI, 2, -1, 4, 50,7, 50,8, 0,-20, 0,-5, 50,11, 0,-6

RI, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

RI, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 34,19, 0,-3

RI, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

RI, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

RB, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

! fitting insulW

RB, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

RB, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

RB, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! for instrument

RB, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLs

RB, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4

RB, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6

RB, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

EL, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

EL, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

!bRad bAng miterJ miterL

EL, 1, -1, 2, 34,19, 34,20, 34,30, 0,-21

!npd od endP thick rating seg id

EL, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

EL, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

MT, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

MT, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

MT, 1, -1, 2, 34,19, 34,20, 34,30, 0,-21

MT, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

MT, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

TE, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

TE, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

!rThick pad ang pad len

TE, 1, -1, 2, 34,19, 0,-13, 34,20

TE, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

TE, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

TE, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

TF, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

TF, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

TF, 1, -1, 2, 34,19, 0,-13, 34,20

TF, 1, -1, 3, 34,49, 34,50, 34,51, 0,-5, 34,53, 0,-6

TF, 1, -1, 4, 34,62, 34,63, 34,64, 0,-5, 34,66, 0,-6

RD, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

RD, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

RD, 1, -1, 2, 0,-8, 0,-9, 0,-10, 0,-11, 0,-12

RD, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

RD, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

ER, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

ER, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

ER, 1, -1, 2, 0,-8, 0,-9, 0,-10, 0,-11, 0,-12

ER, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

ER, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6


FL, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

FL, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

FL, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

FL, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

VA, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

VA, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

VA, 1, -1, 2, 34,28, 0,-15, 0,-16

VA, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

VA, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! for instrument

VA, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLs

VA, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4

VA, 3, -1, 2, 67,23, 0,-15, 0,-16

VA, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6

VA, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

AV, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

AV, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

AV, 1, -1, 2, 34,28, 0,-15, 0,-16

AV, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

AV, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

! for instrument

AV, 3, -1, 0, 0,-2, 67,2, 0,-14, !here for user defined DDLs

AV, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4

AV, 3, -1, 2, 67,23, 0,-15, 0,-16

AV, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6

AV, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

CR, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

CR, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

CR, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

CR, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

CR, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

CR, 1, -1, 6, 34,88, 34,89, 0,-20, 0,-5, 34,92, 0,-6

3W, 1, -1, 0, 0,-2, 34,2, 0,-14, !here for user defined DDLs

3W, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

3W, 1, -1, 2, 34,28, 0,-15, 0,-16

3W, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

3W, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

3W, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

! for instrument


3W, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4

3W, 3, -1, 2, 67,23, 0,-15, 0,-16

3W, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6

3W, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

3W, 3, -1, 5, 67,81, 67,82, 0,-20, 0,-5, 67,85, 0,-6


4W, 1, -1, 1, 34,18, 34,26, 34,27, 34,42, 34,37, 0,-7, 0,-4

4W, 1, -1, 2, 34,28, 0,-15, 0,-16

4W, 1, -1, 3, 34,49, 34,50, 0,-20, 0,-5, 34,53, 0,-6

4W, 1, -1, 4, 34,62, 34,63, 0,-20, 0,-5, 34,66, 0,-6

4W, 1, -1, 5, 34,75, 34,76, 0,-20, 0,-5, 34,79, 0,-6

4W, 1, -1, 6, 34,88, 34,89, 0,-20, 0,-5, 34,92, 0,-6

! for instrument


4W, 3, -1, 1, 67,15, 67,21, 67,22, 67,48, 67,43, 0,-7, 0,-4

4W, 3, -1, 2, 67,23, 0,-15, 0,-16

4W, 3, -1, 3, 67,55, 67,56, 0,-20, 0,-5, 67,59, 0,-6

4W, 3, -1, 4, 67,68, 67,69, 0,-20, 0,-5, 67,72, 0,-6

4W, 3, -1, 5, 67,81, 67,82, 0,-20, 0,-5, 67,85, 0,-6

4W, 3, -1, 6, 67,94, 67,95, 0,-20, 0,-5, 67,98, 0,-6

!support

HA, 4, -1, 0, 0,-2, 80,2, 0,-14, !here for user defined DDLs

!mat’l weight H type sym id

HA, 4, -1, 1, 0,0, 80,15, 0,-17, 80,19

!k1 k2 k3 kp1 kp2 kp3 (this 6 positions are fixed to test node restrain)

HA, 4, -1, 2, 80,28, 80,29, 80,30, 80,31, 80,32, 80,33

! local x local y

HA, 4, -1, 4, 0,-18, 0,-19

ENDOF ELEMENT PROPERTY / CONNECTIVITY TABLE


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. 50 ddl values maximum.

!a.: data base (DDL) attribute value (80,5)

!b.: hanger type

! a. b.

0, 99

1, 99

135, 99

ENDOF HANGER TYPE TABLE

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 genericstress analysis component. The table itself is composed of three columns of data that areposition dependent. You can add comments to the table by placing an ! in column 1. A tableentry 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 pipelinemust have an entry for it in this table. As a component is processed, this table issearched 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 aretwo characters in length. The Intergraph default generic names include:

3W 3-WAY VALVES4W 4-WAY VALVESAV ANGLE VALVESCR CROSSESEL ELBOWS and MITERSER ECCENTRIC REDUCERSFL FLANGESFX</TA>EXPANSIONJOINTSHA PIPE SUPPORTS and HANGERSPI PIPERB RIGID BODIESRD CONCENTRIC REDUCERSRI BENT PIPETE TEESTF OLETS and BRANCH WELDSVA INLINE VALVES

3. Valve Type Descriptor

Another output from this table is a valve type used for valves only. You can map thevalve type into a PROP record. (Refer to the Defaults File section for more information.)


__________________________________________________________________________________________________________________________________________________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 RB1BL1 RB1BL3W1 TE1CKAR1 3W ***1D1 RB1GL1 RB1GL3W1 TE1KNF1 RB1PL1 RB1PL3W1 TE1S1 RB1SA1 RB2PRD1 RB2PRVA1 RB3OP1 RB3UNO1 RB3VFDR1 RB3VFDV1 RB3VFUR1 RB3VFUV1 RB4BOX RB4BOX3 RB4BOX4 RB4CYL RB4CYL3 TEBAL3W 3W ***BALF VA BALBALLP VA BALBALR VA BALBALSP VA BALBDA VA GLABDY VA ***BFY VA BFLBFYHP VA BFLBFYLP VA BFLBLSPO RBBUSH RBCAPBV RBCAPOT RBCKAL AV ***CKALSP AV ***CKAR 3W ***BCKAST AV ***CKBP VA CKECKL VA CKECKLF VA CKECKLR VA CKECKLSP VA CKECKS VA CKECKSF VA CKE


CKSR VA CKECKSSP VA CKECKST VA CKECKSY VA CKECOMP VA CKECKYST VA CKECONV VA CKECPD04 XXCPD05 XXCPD07 XXCPD10 XXCPL XXCPLH XXCPLR XXCRO CRDEL VA GTEDIA VA PLGDIAGL VA PLGDIAPL VA PLGDIASP VA PLGE45 ELE453D ELE45L ELE45LR ELE45S ELE45ST ELE45T ELE45T3D ELE45TLR ELE45U ELE90 ELE90LR ELE90R ELE90SR ELE90T ELE90T3D ELE90TLR ELE90U ELEOLLR TFEOLSR TFFBLD RBFFIL FLFL FLFLO VA GTEFLRSC FLFLSL FLFLSSO FLFLSW FLFLWN FLFOOT VA ***FOSOA FLFOSOAW FLFOSOB FLFOSOBW FLFOSWA FLFOSWAW FLFOSWB FLFOSWBW FLFOTHDA FLFOWNA FLFOWNAW FLFOWNB FLFOWNBW FLFPL FLFTHD FL


FSO FLFSSL FLFSSPL FLFS FLFSW FLCOMP FLCOMP VA GTECOMPF VA GTECOMPBL VA GTECOMPCON VA GTECOMPEX VA GTECOMPEXB VA GTECOMPR VA GTECOMPSP VA GTEGLO VA PMDGLO3W 3W ***GLOA AV GLVGLOASP AV GLVGLOF VA PMDGLOR VA PMDGLOSP VA PMDGLOY VA ***GLOYF VA ***GLOYR VA ***HD21 RBHDHEMI RBHOP XXHOS VA ***HOSA AV ***I2WAY RBIGEN01 RBIGEN02 RBIGEN03 TEIGEN04 RBIGEN05 RBKNF VA ***LOL TFNEE VA GTENIP PINIPL PINOL TFNOZ HAPIN VA PLGPIPB RIPIPE PIPLU VA PLGPLU3W 3W 3WPLU4W 4W 4WPLUFB VA PLGPLUF VA PLGPLUR VA PLGPLUSP VA PLGPLUVP VA PLGPS1 HAPS3 HAPS5 HAPS15 HAPS19 HAR180 ELR180CL ELR180MD ELR180LR ELR180OP ELR180SR ELREDC RD


REDC3 RDREDE ERRELVAL AV ***RWELD TFSLI VA GTESLI3W 3W ***SOL TFSOP XXSPRTA HASTRB1 RBSTUB TFSWGC RDT TETKDR VA GTETOL TFTRB TETRI TETRRB TETST TETUOB TEUN RBUND RBUNO RBWOL TFBX CRXRB CRY TE


Appendix A: Warning & Error Messages A - 1

Appendix A__________________________________________________________________________________________________________________________________________________

Warning & Error Messages

A - 2 PDS Stress Analysis Interface Reference Guide - June 1998


__________________________________________________________________________________________________________________________________________________Appendix A

Warning & Error Messages

This section lists the warning and error messages issued by the various components of thestress analysis software and, when possible, suggests a corrective action.

The messages that are issued by the PD_Stress Analysis Interface are recorded in an errormessage file along with the neutral file when errors occur. If no errors occur, an error file isnot created.

There are two categories of messages issued by the software:

A Warning message indicates an error occurred which may cause a problem in theneutral file. The neutral file should be checked.

An Error message indicates an error occurred and is serious enough to cause extractionto abort. The neutral file is either not produced or incomplete.


__________________________________________________________________________________________________________________________________________________A.1 Warning Messages

Message # Message/Comment

W1 Reuse counter mismatch

The reuse counter stored in the design file does not match that stored inthe database. This is potentially a serious problem that could indicatethat components in the model are linked to incorrect database records. Itis strongly recommended that the model be analyzed to determine theextent 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 ablank (" ") was used. This can be fixed by placing a valid note into theStandard 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 CODEPARAMETER DATA TABLE in the defaults file for thedesign_code_requirements attribute for the segment currently beingextracted. 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 PREPARATIONTABLE in the defaults file for the component which is currently beingprocessed. The first record in the table was used to generate the end prepcode.

W5 Component has undefined commodity code

This message indicates that the current component or pipe does not have acommodity 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 FITTINGNOMENCLATURE TABLE in the defaults file for the commodity code ofthe current component.

W7 Nominal piping diameter has been truncated

The text string generated from the nominal piping diameter has exceededthe maximum size allowed in the software and was truncated. ContactIntergraph.


W8 Unable to locate hanger type, default hanger type used

This means there was no match in the HANGER TYPE TABLE of thedefaults file for the pipe_support_type attribute of the current pipesupport/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 commoditylibrary and default values were used for flare radius, length and coneangle. This can be fixed by modifying the RD_SIZE.TBL in the/usr/ip32/pdstress/dat directory to contain the needed information andplace it into the commodity library.

W10 Wall thickness table not found, default values used

This message indicates there was no thickness table found in thecommodity library for the current component and zero was used. Thismessage usually occurs on components with schedule thicknesses set toNREQD.

W12 Outside Diameter attribute undefined - Insulation Unit Weightdefaulted to 0.0

This means that Insulation Unit Weight can not be calculated because theoutside diameter for the component or pipe being processed is undefined inthe database. Check all components and pipes in the line being extractedto 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 surethe 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 surethe wet weight has a valid value.


__________________________________________________________________________________________________________________________________________________A.2 Error Messages

Message # Message/Comment

E1 Error opening error message file - pdsstr.err

An error occurred while trying to open the error message file. Check tomake sure that the file pdsstr.err is not opened by another user in thedefault directory.

E3 Error opening input data file - PDSSTR.DAT

An error occurred while attempting to open the input file to the stressanalysis interface. Check to make sure that the file PDSSTR.DAT existsin 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 blankfirst line in the input data file and no model file names were found. Checkto make sure there are valid model file names in PDSSTR.DAT in thedefault directory.

E6 No line names found in input data file - PDSSTR.DAT

An error occurred generating PDSSTR.DAT or the user entered two blanklines between the last model file name and the first line name. Check tomake sure there is only one blank line between the last model file nameand 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 Error opening stress options file

E9 Fatal SEQUENCER error

An error occurred while organizing the design file components. Check themodel design file to verify that the pipeline being extracted is free ofmodeling 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 therecord format of the input data file PDSSTR.DAT in the default directory.

E11 Logical name STRESSOPTION is undefined or file does not exist

E15 Number of connect points exceeded internal limit of 2000 connectpoints.

The maximum number of connect points per extraction is 2000. Break theline into two separate line names and re-extract the line as two separateisometrics.

E16 Error reading FORM type from defaults file

An error occurred reading in the FORM type from a record in theELEMENT PROPERTY / CONNECTIVITY TABLE section of the defaultsfile. Valid values for form type are 0-6. For more information on propertyand 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 designfile linkage. This error indicates potentially serious problems in themodel. It is strongly recommended that the model be analyzed todetermine 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 attributefrom the database. Check the database DDL to make sure the DDL pairin 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 LOADINGDATA (LOAD) TABLE, the SERVICE LOADING (LSET) TABLE or theELEMENT PROPERTY / CONNECTIVITY TABLE in the defaults file.Check to make sure only valid entity numbers are used in the DDL pairssection of the above tables.

E20 Error writing CODE record

An error occurred while trying to write a CODE record to the STRESSANALYSIS neutral file.

E21 Error converting Segment occurrence number from decimal tohex

An error occurred while trying to convert a Segment occurrence numberfrom decimal format into a hexadecimal format. Contact Intergraph.

E22 Error writing header information into neutral file


An error occurred while trying to write the header records to thebeginning of the stress analysis neutral file.

E23 Error writing DRAW record

An error occurred while trying to write a DRAW record to the stressanalysis neutral file.

E24 Error converting nominal piping diameter

This message means there was an error trying to convert the nominalpiping diameter from the database format to an ASCII format. ContactIntergraph.

E25 Error loading record from options file

E26 Invalid table for Insulation Weight

An error occurred trying to retrieve insulation weight for a table whichdoes 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 theELEMENT PROPERTY / CONNECTIVITY TABLE section of the defaultsfile.

E27 End node number is too small for current line

An error occurred trying to assign an end node number to the current linebeing extracted. This can be fixed by increasing the end node number(word 3) of the INTERGRAPH OPTIONS BLOCK section of the defaultsfile.

E28 Internal table limits exceeded for PDS to STRESS map

The internal table size for the PDS to STRESS map has reached its limitsand the remainder of the map can not be stored. Reduce the number ofrecords in the PDS to STRESS map. Contact Intergraph for informationabout increasing the maximum table size.

E29 Error initializing spec table access information

An error occurred while trying to open and initialize the piping jobspecification tables. Check the project files to make sure they exist andyou 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 neutralfile.

E34 Error writing LNOD record


An error occurred trying to write a LNOD record to the stress analysisneutral file.

E35 Error searching for PDS item name in PDS to stress analysissymbol map

An error occurred searching for PDS item name in the PDS to stressanalysis symbol map. Check to make sure the PDS item name is in thePDS to STRESS table.

E36 Undefined generic name in PDS to STRESS map

An error occurred in reading the generic name from the PDS to stressanalysis symbol map. Check to make sure that the generic name isdefined in the table.

E37 Error locating PROPERTY/CONNECTIVITY records for genericname

An error occurred searching for the PROPERTY / CONNECTIVITYrecord(s) from the ELEMENT PROPERTY / CONNECTIVITY TABLEsection of the defaults file. Check to make sure all the necessary formrecords are in this table.

E38 Error reading standard note library

An error occurred while reading the standard note library. Check thestandard 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 theneutral file.

E42 Error writing PROPERTY record

An error occurred while trying to write a PROPERTY record to the neutralfile.

E43 Error accessing or opening PDS to STRESS map

An error occurred while trying to open the PDS to stress analysis symbolmap. Check to make sure the file exists and that you have read access toit.


E44 Error reading PDS to STRESS map

An error occurred while trying to read a record from the PDS to stressanalysis symbol map. Check to make sure the table is in the correctformat.

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 numberfrom the current component. Check the model to make sure thatcomponents are owned by the correct segments.

E51 Error accessing wall thickness table

An error occurred while accessing information from the wall thicknesstable. Check the commodity library to make sure the wall thickness tableexists.

Appendix B: PDS Design Database Format B - 1

Appendix B__________________________________________________________________________________________________________________________________________________

PDS Design Database Format

B - 2 PDS Stress Analysis Interface Reference Guide - June 1998


__________________________________________________________________________________________________________________________________________________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 , system_unique_no , integer , index 12 , line_number_label , character(40)3 , line_id , character(16)4 , unit_number , character(12)5 , unit_code , character(3)6 , module_no , character(16)7 , package_system_no , character(12)8 , train_number , character(2)9 , fluid_code , short , standard note 12510 , line_sequence_no , character(16)11 , nominal_piping_dia , short12 , piping_mater_class , character(16)13 , gasket_separation , character(8)14 , insulation_purpose , short , standard note 22015 , insulation_thick , double16 , insulation_density , double , standard note 1074 (units)17 , heat_tracing_reqmt , short , standard note 20018 , heat_tracing_media , short , standard note 21019 , heat_tracing_temp , double20 , construction_stat , short , standard note 13021 , hold_status , short , standard note 5022 , approval_status , short , standard note 3523 , schedule_override , character(8)24 , nor_oper_pres , double25 , nor_oper_temp , double26 , alt_oper_pres , double27 , alt_oper_temp , double28 , nor_dgn_pres , double29 , nor_dgn_temp , double30 , alt_dgn_pres , double31 , alt_dgn_temp , double32 , steam_outlet_temp , double33 , mater_of_construct , character(6)34 , safety_class , short , standard note 34035 , design_standard , short , standard note 57036 , design_area_number , character(12)37 , design_resp , short , standard note 16038 , construction_resp , short , standard note 16039 , supply_resp , short , standard note 16040 , coating_reqmts , short , standard note 19041 , cleaning_reqmts , short , standard note 23042 , fluid_category , character(4)43 , nor_op_pres_units , short , standard note 1064


44 , nor_op_temp_units , short , standard note 105645 , alt_op_pres_units , short , standard note 106446 , alt_op_temp_units , short , standard note 105647 , nor_dgn_pres_units , short , standard note 106448 , nor_dgn_temp_units , short , standard note 105649 , alt_dgn_pres_units , short , standard note 106450 , alt_dgn_temp_units , short , standard note 105651 , steam_temp_units , short , standard note 105652 , stress_system_no , character(12)53 , stress_reqmts , short , standard note 36054 , hyd_system_no , character(12)55 , hyd_reqmts , short , standard note 36056 , specific_gravity_a , double57 , specific_gravity_b , double58 , specific_gravity_c , double59 , viscosity , double60 , density , double61 , spec_heat_ratio , double62 , sonic_velocity , double63 , surface_roughness , double64 , test_system_no , character(6)65 , test_fluid , short , standard note 12566 , test_pressure , double67 , PID_id_part_a , character(4)68 , PID_id_part_b , character(4)69 , end_1_nozzle_id , integer70 , end_2_nozzle_id , integer71 , alpha_descript_id , character(12)72 , standard_note_no , short , standard note 499

# Piping Component Data


1 , system_unique_no , integer , index 12 , piping_comp_no , character(20)3 , commodity_name , character(6)4 , model_code , character(6)5 , option_code , short , standard note 4006 , maximum_temp , double7 , sched_thick_basis , character(8)8 , commodity_code , character(16)9 , MTO_requirements , short , standard note 36510 , fabrication_cat , short , standard note 18011 , source_of_data , short , standard note 42012 , PDS_sort_code , character(6)13 , physical_data_id , character(8)14 , geometric_standard , short , standard note 57515 , weight_code , short , standard note 57816 , table_suffix_green , short , standard note 57617 , table_suffix_red , short , standard note 57718 , materials_grade , short , standard note 14519 , bend_radius , double20 , bend_angle , double21 , face_to_face_dim , double22 , dimension_a , double23 , dimension_b , double24 , dimension_c , double25 , surface_area , double , standard note 1010 (units)26 , empty_weight , double , standard note 1028 (units)27 , water_weight , double , standard note 1028 (units)28 , operator_weight , double29 , operator_sym_name , character(6)30 , chain_operator_no , short31 , opening_action , short , standard note 390


32 , construction_stat , short , standard note 13033 , hold_status , short , standard note 5034 , heat_tracing_reqmt , short , standard note 20035 , heat_tracing_media , short , standard note 21036 , heat_tracing_temp , double37 , iso_dwg_index_no , integer38 , isometric_sheet_no , character(2)39 , piece_mark_no , character(10)40 , color_code , character(8)41 , stress_node_no , short42 , stress_intens_fact , double43 , head_loss_factor , double44 , piping_assembly , character(12)45 , component_group_no , short46 , remarks , character(16)47 , standard_note_no_a , short , standard note 49948 , standard_note_no_b , short , standard note 499

49 , cp_1_nom_pipe_diam , short50 , cp_1_outside_diam , double51 , cp_1_end_prep , short , standard note 33052 , cp_1_sch_thk , character(8)53 , cp_1_rating , character(8)54 , cp_1_face_to_ctr , double55 , cp_1_weld_no , character(8)56 , cp_1_weld_type , short , standard note 1100 / 400 (bolt option)57 , cp_1_gasket_gap , double58 , cp_1_gasket_option , short , standard note 40059 , cp_1_stress_node , short60 , cp_1_stress_factor , double61 , cp_1_head_loss , double



88 , cp_4_nom_pipe_diam , short89 , cp_4_outside_diam , double90 , cp_4_end_prep , short , standard note 33091 , cp_4_sch_thk , character(8)92 , cp_4_rating , character(8)


93 , cp_4_face_to_ctr , double94 , cp_4_weld_no , character(8)95 , cp_4_weld_type , short , standard note 1100 / 400 (bolt option)96 , cp_4_gasket_gap , double97 , cp_4_gasket_option , short , standard note 40098 , cp_4_stress_node , short99 , cp_4_stress_factor , double100, cp_4_head_loss , double

101, cp_5_nom_pipe_diam , short102, cp_5_outside_diam , double103, cp_5_end_prep , short , standard note 330104, cp_5_sch_thk , character(8)105, cp_5_rating , character(8)106, cp_5_face_to_ctr , double107, cp_5_weld_no , character(8)108, cp_5_weld_type , short , standard note 1100 / 400 (bolt option)109, cp_5_gasket_gap , double110, cp_5_gasket_option , short , standard note 400111, cp_5_stress_node , short112, cp_5_stress_factor , double113, cp_5_head_loss , double

# Piping/Tubing Data


1 , system_unique_no , integer , index 12 , piping_comp_no , character(20)3 , commodity_name , character(6)4 , model_code , character(6)5 , option_code , short , standard note 4006 , maximum_temp , double7 , nominal_piping_dia , short8 , outside_diameter , double9 , schedule_thickness , character(8)10 , sched_thick_basis , character(8)11 , rating , character(8)12 , commodity_code , character(16)13 , MTO_requirements , short , standard note 36514 , fabrication_cat , short , standard note 18015 , source_of_data , short , standard note 42516 , PDS_sort_code , character(6)17 , geometric_standard , short , standard note 57518 , weight_code , short , standard note 57819 , table_suffix_green , short , standard note 57620 , table_suffix_red , short , standard note 57721 , materials_grade , short , standard note 14522 , pipe_length , double23 , surface_area , double , standard note 1010 (units)24 , empty_weight , double , standard note 1028 (units)25 , water_weight , double , standard note 1028 (units)26 , cold_spring_length , double27 , construction_stat , short , standard note 13028 , hold_status , short , standard note 5029 , heat_tracing_reqmt , short , standard note 20030 , heat_tracing_media , short , standard note 21031 , heat_tracing_temp , double32 , iso_dwg_index_no , integer33 , isometric_sheet_no , character(2)34 , piece_mark_no , character(10)35 , color_code , character(8)36 , piping_assembly , character(12)37 , component_group_no , short38 , remarks , character(16)


39 , standard_note_no_a , short , standard note 49940 , standard_note_no_b , short , standard note 499

41 , end_1_end_prep , short , standard note 33042 , end_1_weld_no , character(8)43 , end_1_weld_type , short , standard note 1100 / 400 (bolt option)44 , end_1_gasket_gap , double45 , end_1_gasket_opt , short , standard note 40046 , end_1_stress_node , short47 , end_1_stres_int , double48 , end_1_head_loss , double

49 , end_2_end_prep , short , standard note 33050 , end_2_weld_no , character(8)51 , end_2_weld_type , short , standard note 1100 / 400 (bolt option)52 , end_2_gasket_gap , double53 , end_2_gasket_opt , short , standard note 40054 , end_2_stress_node , short55 , end_2_stres_int , double56 , end_2_head_loss , double

# Instrument Component Data


1 , system_unique_no , integer , index 12 , instrument_comp_no , character(20)3 , model_code , character(6)4 , option_code , short , standard note 4005 , sched_thick_basis , character(8)6 , MTO_requirements , short , standard note 3657 , fabrication_cat , short , standard note 1808 , source_of_data , short , standard note 4309 , PDS_sort_code , character(6)10 , physical_data_id , character(8)11 , geometric_standard , short , standard note 57512 , weight_code , short , standard note 57813 , table_suffix_green , short , standard note 57614 , table_suffix_red , short , standard note 57715 , materials_grade , short , standard note 14516 , face_to_face_dim , double17 , dimension_a , double18 , dimension_b , double19 , dimension_c , double20 , surface_area , double , standard note 1010 (units)21 , empty_weight , double , standard note 1028 (units)22 , water_weight , double , standard note 1028 (units)23 , operator_weight , double , standard note 1028 (units)24 , operator_type , double25 , operator_sym_name , character(6)26 , chain_operator_no , short27 , chain_length , double28 , opening_action , short , standard note 39029 , construction_stat , short , standard note 13030 , hold_status , short , standard note 5031 , design_resp , short , standard note 16032 , construction_resp , short , standard note 16033 , heat_tracing_reqmt , short , standard note 20034 , heat_tracing_media , short , standard note 21035 , heat_tracing_temp , double36 , insulation_purpose , short , standard note 22037 , insulation_thick , double38 , insulation_density , double , standard note 1074 (units)39 , cleaning_reqmts , short , standard note 23040 , safety_class , short , standard note 340


41 , module_no , character(16)42 , package_system_no , character(12)43 , iso_dwg_index_no , integer44 , isometric_sheet_no , character(2)45 , piece_mark_no , character(10)46 , color_code , character(8)47 , stress_node_no , short48 , stress_intens_fact , double49 , head_loss_factor , double50 , piping_assembly , character(12)51 , component_group_no , short52 , remarks , character(16)53 , standard_note_no_a , short , standard note 49954 , standard_note_no_b , short , standard note 499




94 , cp_4_nom_pipe_diam , short95 , cp_4_outside_diam , double96 , cp_4_end_prep , short , standard note 33097 , cp_4_sch_thk , character(8)98 , cp_4_rating , character(8)99 , cp_4_face_to_ctr , double100, cp_4_weld_no , character(8)101, cp_4_weld_type , short , standard note 1100 / 400 (bolt option)


102, cp_4_gasket_gap , double103, cp_4_gasket_option , short , standard note 400104, cp_4_stress_node , short105, cp_4_stress_factor , double106, cp_4_head_loss , double

107, cp_5_nom_pipe_diam , short108, cp_5_outside_diam , double109, cp_5_end_prep , short , standard note 330110, cp_5_sch_thk , character(8)111, cp_5_rating , character(8)112, cp_5_face_to_ctr , double113, cp_5_weld_no , character(8)114, cp_5_weld_type , short , standard note 1100 / 400 (bolt option)115, cp_5_gasket_gap , double116, cp_5_gasket_option , short , standard note 400117, cp_5_stress_node , short118, cp_5_stress_factor , double119, cp_5_head_loss , double

# Pipe Support Data


1 , system_unique_no , integer , index 12 , pipe_support_no , character(20)3 , model_code_phy , character(6)4 , model_code_log , character(6)5 , iso_support_type_a , short , standard note 3806 , iso_support_type_b , short , standard note 3807 , iso_support_type_c , short , standard note 3808 , iso_support_type_d , short , standard note 3809 , details_for_shop , character(50)10 , details_for_field , character(50)11 , fabrication_orient , character(20)12 , commodity_code , character(16)13 , MTO_requirements , short , standard note 36514 , fabrication_cat , short , standard note 18015 , weight , double , standard note 1028 (units)16 , construction_stat , short , standard note 13017 , hold_status , short , standard note 5018 , standard_note_no , short , standard note 49919 , iso_dwg_index_no , integer20 , isometric_sheet_no , character(2)21 , piece_mark_no , character(10)22 , color_code , character(8)23 , isometric_dim_a , double24 , isometric_dim_b , double25 , isometric_dim_c , double26 , isometric_dim_d , double27 , isometric_dim_e , double28 , trans_rigidity_x , double29 , trans_rigidity_y , double30 , trans_rigidity_z , double31 , rot_rigidity_x , double32 , rot_rigidity_y , double33 , rot_rigidity_z , double34 , spring_gap_length , double35 , sping_gap_direct , short36 , number_of_springs , short


Glossary GL - 1

Glossary__________________________________________________________________________________________________________________________________________________

GL - 2 PDS Stress Analysis Interface Reference Guide - June 1998

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

active depth The plane in a 3-D design upon which you can place elementsand perform manipulations.

active process The process which is displayed in the Process ID field; itcontrols the message fields, the menus, and the keyboard.The active process has a highlighted window icon strip.

application software Software designed to meet specific needs, unlike systemsoftware which runs other software.

batch processing A method of processing data which collects a series ofoperations into a group (or ‘‘batch’’) and executes the group ina continuous stream without user intervention.

batch queue A queue, or channel for moving requests, created throughNQS. A batch queue handles scheduling for processessubmitted through the Batch options screen menu.

branch point A point on a pipeline which separates piping segments so thatthey can be assigned different segment parameters. A branchpoint allows for placement of branch components.

cancel button The button located in the upper right corner of a formcontaining a red X or the word cancel. Select the cancelbutton to exit the form or option.

cell A permanent association of elements that can be stored andplaced as a group, and then manipulated as individualelements.

character A column data type that stores alphanumeric character data.

client In network operations, a node which accesses data orperforms a function on the remote resource (usually a server).All network operations (database, NFS, NQS) between two ormore nodes establish a client/server relationship.

column An attribute of a database table. A group of columns definesa table in a database.

command Instructions from the user to perform a function on specifieddata.


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 theconfirm button to initiate a specified option.

coordinate The location of a point along the X, Y, or Z axis.

coordinate system A geometric relation used to denote the location of points inthe design cube. The most common coordinate system is therectangular coordinate system, whereby points are located bytraversing the X, Y, and Z axes of the design cube. Normally,coordinate systems have their origin defined as 0,0,0, thoughthis is not required. Other coordinate systems are used tomore easily express the coordinates of specific geometricentities. For example, you can use a spherical coordinatesystem to help define points on a sphere, and you can use acylindrical coordinate system to help define points on acylinder.

coordinates An ordered set of absolute or relative data values that specifya location in a coordinate system.

core files The image files written by System V for a number of reasons,the most common of which are memory violations, illegalinstructions, bus errors, and user-generated quit signals.

cursor The pointer that the user moves on the screen to indicate anitem or area.

data button The mouse button used to place data points and tentativepoints, to accept previously selected elements, and to selectcommands from forms and menus.

data entry field The field on a screen used to accept user-supplied data. Alsoknown as key-in field.

data point A point placed by pressing the data button on the mouse.Data points select commands from the panel menus andMenu Bar, place elements, identify and accept elements, andactivate windows and perform window manipulations.

database A collection of comprehensive informational files havingpredetermined structure and organization that can then becommunicated, interpreted, or processed by a specificprogram.

database table The part of the database that is made of rows and columnsand contains information about the project and designelements.

default The predetermined value of a parameter that is automaticallysupplied by the system or program whenever a value is notspecified by the user.

Glossary GL - 5

delete To remove, destroy, eliminate, or erase.

delimiter A separating mark or space; a character or sequence ofcontiguous characters that mark the end of a string ofcharacters.

device A nonaddressable component of a network, that is, acomponent onto which a user cannot log, for example, tapedrive, disk drive, and floppy disk.

directory A file that contains the names of other files.

display-list box A small box with horizontal dashes located at the end of aform key-in field. When selected, a list of the data availablefor that field is displayed. Input can then be selected from thelist with a data point instead of keying in the information.

domain The set of acceptable values for a value within a component.

dragging Another term for the dynamic function that attaches thecursor to an element so you can see it move.

easting A term used in plane surveying that describes an east, orpositive, difference in longitude.

entity An object (project, drawing, element, and so forth.) of interestabout which information is stored; a relational database table.

envelope file See interference envelope.

file specification A UNIX path name that tells the system where to locate afile.

filename A user-defined name given to an interactively created file.The name should be relevant to the contents of the file.

form An interface or screen menu designed with the I/FORMSproduct. Because many of the screen menus in theapplication software are built with I/FORMS, you must havethe FORMS_S product on your workstation.

full path name The name of the entire path or directory hierarchy to a file,including the file name. See also relative path name.

gadget A portion of a form, such as a button, a field, or a checklist,that responds to information. Gadgets can display defaultvalues or act as data entry areas.

header The first items of information in a file which precede anyactual data. The header contains information on thestructure and contents of the file.

hierarchy A classified structure with superiors (roots) and subordinates(dependents) for grouping files or commands.


icon A pictorial representation or image; a symbol that graphically

identifies a command.

Informix A relational database management system supported by RIS.

Ingres A relational database management system supported by RIS.

interference envelope An equipment modeling primitive or parametric componentthat is used in conjunction with or instead of model graphicsfor interference checking. Interference envelopes are givendifferent levels and display symbology to distinguish themfrom primitives.

invert elevation The lowest point on the internal diameter of the pipe.

isometric Relating to or being a drafting system characterized by threeequal axes at right angles; a view in which the horizontallines of an element are drawn at an angle to the horizontaland all verticals are projected at an angle from the base.

key An attribute (column) in a table which is chosen as the accessvehicle to individual rows of the table.

key-in field The field on a screen used to accept user-supplied data. Alsoknown as a data entry field.

keypoint A point on an element, including vertices, to which you cansnap.

keyword A word recognized by the software that provides access to acertain function.

menubar The strip at the top of the screen that contains icons forselecting commands.

message area The area that appears in the MicroStation Command Windowwhen you are working in a design file. It is divided into theCommand Status field, the Current Command field, thePrompt field, and the Key-in field.

model A graphic representation or schema.

network An interconnection of host computers and workstations thatenables them to share data and control. The term network canmean the devices that connect the system, or it can mean theconnected system.

NFS Network File System, the system that provides access to datathat is distributed among machines through aninterconnection of host computers and workstations. NFSallows you to mount a remote resource to your localworkstation so you can access the data as though it werelocal. NFS is usually used to access centralized data on aserver.

Glossary GL - 7

node Any addressable device (such as a workstation or a server)

that is connected to a network. The network enables theconnected nodes to share data and system control.

node address The hard-wired Ethernet address assigned to each node whenit is manufactured. It is necessary for each node to identifyand communicate with another node in the network.

node name A name, or alias, that can be assigned to the node address of adevice on a network.

northing A term used to describe a north coordinate location in theplant coordinate system.

nozzle A special equipment modeling primitive that contains theconnection point to piping. This point does NOT include agasket allowance, but rather represents the face-of-flangecoordinate.

NQS Network Queuing System, the software package that allowsyou to define network-wide batch and device queues. Use ofNQS involves setting up local resource queues on thesystem(s) where the resources reside and setting up ‘‘pipequeues’’ on the systems that are to have access to theresources.

Oracle A relational database management system supported by RIS.

origin In coordinate geometry, the point where the x, y, and z-axesintersect.

origin point The point at which the coordinate system is placed.

orthogonal view A view which is a projection of the model onto a plane alonglines which are orthogonal to the plane.

parameter A property whose value determines the characteristics orbehavior of something.

path A sequence of directories leading to a file or a sequence ofmenus leading to a command.

path name The sequence of directories leading to a file. See also absolutepath name and relative path name.

PDS Plant Design System

pipe queue A controlled channel for moving requests to batch or devicequeues on remote systems and for receiving status and/ordata in response.

place data point To identify a specific element, or indicate a specific point inthe design file.


plane A spatial element in geometry that may or may not have a

boundary, but is level, having no elevations or depressions,and is three-dimensional.

RDB Reference Database.

reference database A collection of reference data containing information relativeto industry design codes, vendor’s catalog data, jobspecifications, commodity libraries, graphics symbology, labeldescriptions, report formats and other information of a similarmanner.

relative path name The sequence of directories leading from the current directoryto a particular file. See also path name and absolute pathname.

rotate To turn; to change the angular orientation; to transform byrevolution about a specific axis.

row A unit of related information in a table. One collection ofcolumn values for a table.

rubberbanding The animation dynamic that enables you to specify theposition of a data point while the element changes as youmove the cursor.

schema A description of the overall structure of the rulebase ordatabase.

schema file A file that outlines the overall logical structure of a rule baseor a database.

server In network operations, the node which maintains commondata or performs a common task needed by clients. Allnetwork operations (database, NFS, NQS) between two ormore nodes establish a client/server relationship.

Structured QueryLanguage SQL

Language developed by IBM for creating, modifying, andquerying relational databases.

style The symbology of an element such as continuous dashes,dash-dot, solid, and so forth.

surface The skin of a three-dimensional geometric element.

symbology The display style of an element, including color, style, andweight.

table A collection of data for quick reference, either stored insequential locations in memory or printed as an array of rowsand columns of data items of the same type.

toggle To switch; to change between two alternatives.

Glossary GL - 9

user name A name that provides access to an account on the system.

values Data, either entered by the user or determined by thesoftware, that are stored in an attribute.

variable A quantity that may assume any one of a set of values.

vector A quantity possessing both magnitude and direction,generally represented as a line. Vectors can be manipulatedgeometrically and are represented as a coordinate triple(x,y,z).

view The defined area of vision on a screen. A view allows you tosee a prescribed volume of the design cube. Views are createdwith their own x, y, and z axes. The x,y plane of the view isparallel to the screen, while the z-axis can be thought of ascoming straight out of the view towards you. The view axesmaintain this relationship regardless of the rotation withrespect to the design cube. See also active depth.

virtual memory External memory for a computer that can be used as if it werean extension of the computer’s internal memory. Thesoftware uses virtual memory to store data. This means thatunneeded files and data, stay on the disk until they are calledfor. Because the internal processing memory stores aminimal amount of data, the software can perform processingmore quickly.

working directory The directory from which you are accessing files.


Index IN - 1

Index__________________________________________________________________________________________________________________________________________________

IN - 2 PDS Stress Analysis Interface Reference Guide - June 1998

Index IN - 3

__________________________________________________________________________________________________________________________________________________Index

3-way valves 7-1

4-way valves 7-1

Aangle valves 7-1assumptions about line names 3-7

Bbasic input data 4-12batch

processes 2-8bent pipe 7-1branch

components 3-7first order 4-24welds 7-1

branches 3-7

Ccode 5-2

name of code parameter data table 6-3,6-5

string 6-5val 6-5

record 5-6code 5-6codeid 5-6string 5-6

codeid 5-7commodity code 6-11component

map 7-2records 5-7

overall 5-7prop 5-7

concentric reducers 7-1conventions

forms 2-5crosses 7-1

D.dat

pdsstr 1-2strdef 1-2

databasematerial/specification 3-5

DDL B-3defaults

file 1-2, 6-1, 6-12keywords 6-2 − 6-3

codename of code parameter data

table 6-5parameter data table 6-3

elementconnectivity map table 6-3, 6-7property / connectivity table

6-3, 6-7end preparation table 6-3, 6-10external files 6-3 − 6-4fitting nomenclature table 6-3,

6-11hanger type table 6-3, 6-11intergraph options block 6-3loading data (load) table 6-3, 6-5options block 6-3service loading (lset) table 6-3, 6-6vendor name 6-3 − 6-4

structure 6-2c1 6-2cm- 6-2endof table_keyword 6-2m1 6-2n1 6-2table_keyword 6-2

generic names3-way valves 7-14-way valves 7-1angle valves 7-1bent pipe 7-1branch welds 7-1concentric reducers 7-1crosses 7-1eccentric reducers 7-1elbows 7-1expansion joints 7-1flanges 7-1hangers 7-1inline valves 7-1miters 7-1olets 7-1pipe 7-1pipe supports 7-1


defaults (continued)

generic names (continued)rigid bodies 7-1tees 7-1

descriptionsdetailed record 5-5

designdatabase format B-3file

datain str order 4-24raw 4-12sorted by coordinate 4-13sorted by topo 4-15

detailed record descriptions 5-5disconnected sections 4-14document

organization xpurpose ix

Eeccentric reducers 5-10, 7-1elbows 6-9, 7-1

and bent pipe 5-10types 6-9

elementconnectivity map table 6-3, 6-7

cat 6-7name 6-7nodes 6-7onodes 6-7

property / connectivity table 6-3, 6-7-1 6-8attlst 6-8form 1 attributes

dry weight (34,26) 6-10fitting type (0, -7) 6-10insulation weight (0, -4) 6-10iso drawing reference (4, 8) 6-10material code (34,18) 6-9stress intensification (34,42) 6-10weight weight (34,27) 6-10

form 2 attributesbend angle ( 4, 23) 6-10bend radius (4, 22) 6-10mitre segment length (0, -21) 6-10number of mitre joints (34, 30)

6-10form 3 attributes

end prep code (0,-20) 6-10npd (34,49 and 34,16) 6-10npd (34,50 and 34,63) 6-10pressure rating (34,53 and 34,66)

6-10

element (continued)property / connectivity table

(continued)form 3 attributes (continued)

segment ID (0,-6) 6-10wall thickness (0,-5) 6-10

form 4 attributesend prep code (0,-20) 6-10npd (3,10 and 3,15) 6-10npd (34,49 and 34,16) 6-10pressure rating (3,13 and 3,18)

6-10segment ID (0,-6) 6-10wall thickness (0,-5) 6-10

formno 6-8name 6-8overall component attributes

component tag (3,3) 6-9special label (0,-2) 6-9

pdstyp 6-8end preparation table 6-3, 6-10

gentyp 6-11text 6-11

endof 6-2error messages A-3, A-6examples

component map 7-2HITS report 4-2neutral file 5-12options file 6-12

expansion joints 7-1external files 6-3 − 6-4

Ffitting

nomenclature table 6-3, 6-11ccode 6-11ctype 6-11

type 6-11flanges 7-1forms

conventions 2-5

Ggadgets

conventions 2-5generating neutral files 3-1

model number 3-5pipeline names 3-6

graphic commodity library 3-5

Hhanger type table 6-3, 6-11

pdscode 6-11

Index IN - 5

hanger type table (continued)

stype 6-11hangers 7-1header 3-7header topo 4-25HITS

report 4-1, 4-28branch 4-12cp # 4-12direct 4-12flags 4-12name 4-12node 4-12occ 4-12sect 4-12section 1

basic input data and raw designfile data 4-12

section 2design file data sorted by

coordinate 4-13section 3

tracing data 4-14section 4

design file data sorted by topo4-15

section 5design file data in str order 4-24

sg_occ 4-12topo 4-12x 4-12y 4-12z 4-12

Iinline valves 7-1input

collection 1-1input data 4-12intergraph options block 6-3interpreting the HITS report 4-1

basic input data 4-12design

file datain str order 4-24sorted by coordinate 4-13sorted by topo 4-15

example HITS report 4-2raw design file data 4-12tracing data 4-14using the HITS report to solve problems

4-28introduction 1-1

Jjoint

expansion 7-1

Llabel description library 3-5libraries

graphic commodity 3-5label description 3-5material descriptions 3-5physical commodity 3-5piping job spec tables 3-5specialty and instrument descriptions

3-5standard notes 3-5

line namesassumptions 3-7

lnod 5-3record 5-8

ax 5-8ay 5-8az 5-8dx 5-8dy 5-8dz 5-8lnod 5-8node 5-8type 5-8

load 5-2 − 5-3record 5-5

i 5-5j 5-5load 5-5pn 5-5segid 5-5tn 5-5

loading data (load) table 6-3, 6-5-6 6-5i 6-5j 6-5patt 6-5tatt 6-5

lset 5-2 − 5-3record

lset 5-6s1 5-6s2 5-6s3 5-6s4 5-6segid 5-6

Mmap

stress symbol 6-4


material

descriptions library 3-5specification database 3-5

messageserror A-3, A-6warning A-3 − A-4

miters 7-1model

files 3-5number 3-5

Nnetwork

problems 4-14neudflts 6-1neutral

file 5-12format 5-2

code 5-2lnod 5-3load 5-2lset 5-2node 5-3section 1 5-2section 2 5-2section 3 5-2section 4 5-2section 5 5-2section 6 5-3section 7 5-3section 8 5-3

generating 1-2, 3-1stress analysis 5-1

node 5-3number set 5-10numbering conventions 5-10

eccentric reducers 5-10elbows and bent pipe 5-10olet and branch weld type components

5-10pipe supports 5-11straight

through components 5-10through valves 5-10

tee type components 5-10three-way valves 5-10two-way valves 5-10

record 5-9flag 5-9node 5-9x 5-9y 5-9z 5-9

number fitting type 6-11numbering conventions 5-10

Ooccurrence numbers 4-12olets 3-7, 7-1

branch weld type components 5-10options block 6-3overall component record 5-7

compid 5-7data 5-7name 5-7

overlap 4-28

PPDS

design database format B-3item name 7-1stress analysis symbol map 7-1

PDS item name 7-1stress analysis generic name 7-1valve type descriptor 7-1

to stress symbol map 6-4PDS environment 2-1

PD_Shell 2-2PD_Shell 2-2

form conventions 2-5pdshell environment 2-1pdsstr.dat 1-2physical commodity libraries 3-5pipe 7-1

supports 5-11, 7-1pipeline names 3-6piping job spec tables library 3-5prop 5-2 − 5-3, 6-7, 7-1

record 5-7, 6-7compid 5-8data 5-8form 5-8name 5-7prop 5-7

Rraw design file data 4-12RDB 3-5record descriptions

code 5-6component 5-7component record

overall 5-7prop 5-7

detailed 5-5lnod 5-8load 5-5

Index IN - 7

record descriptions (continued)

lset 5-5node 5-9

reference database 3-5rigid bodies 7-1

Sservice loading (lset) table 6-3, 6-6

cold 6-6dw 6-6entatt 6-6flag 6-6hot 6-6val 6-6wind 6-6

set record 5-5specialty and instrument descriptions

library 3-5specifying pipings segments 3-6standard notes library 3-5straight

through components 5-10through valves 5-10

strdef.dat 1-2stress 7-1

analysisgeneric name 7-1interface 1-2neutral file 5-1

symbol map 6-4strinp 1-2symbol map

PDS to stress analysis 7-1

Ttee 3-7

type components 5-10tees 7-1three-way valves 5-10topo 4-15

design file datasorted by 4-15

header 4-25tracing

data 4-14traversing a network 4-24, 4-26 − 4-27two-way valves 5-10typefaces xiii

Uuser input

collecting 1-1using

HITS report to solve problems 4-28

Vvalve type descriptor 7-1vendor name 6-3 − 6-4

Wwarning messages A-3 − A-4

Zzero length leg 4-26
