PDS Piping Eden Interface

(1)

Plant Design System (PDS)

Piping Eden Interface

Version 2011 (V12) May 2011

(2)

Copyright

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.

U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

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

P.O. Box 240000 Huntsville, AL 35813

Terms of Use

Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks

Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle

(3)

Plant Design System (PDS) Piping Eden Interface

3

4 Plant Design System (PDS) Piping Eden Interface

Define Active Orientation ... 47

Draw Cone ... 48

Draw Cylinder ... 49

Draw Eccentric Cone ... 49

Draw Projected Rectangle ... 50

Draw Projected Triangle ... 51

Draw Semi-Ellipsoid ... 51

Draw Sphere ... 52

Draw Torus ... 53

Assign Connect Point ... 53

Assign Generic Tap ... 54

Assign Tap ... 54

Compute Perpendicular Vector ... 55

Define Connect Point Geometry ... 55

Display Tutorial ... 56

Draw Cone With Capped Ends ... 57

Draw Cylinder With Capped Ends ... 57

Draw Eccentric Cone With Capped Ends... 58

Draw Hexagon ... 59

Draw Mitered Torus ... 59

Draw Octagon ... 60

Draw Parametric Shape ... 61

Draw Torus with Capped Ends ... 61

Get Physical Data ... 62

Move Along Axis ... 63

Move By Distance ... 63

Move To Connect Point ... 64

Place COG Location ... 64

Place Connect Point ... 65

Prompt to Orient Operator ... 65

Read Table ... 65

Rotate Orientation ... 66

Connect Point Geometry ... 67

Creating a New Piping Component ... 73

Reference Database Management Data ... 75

Default Project Control Data ... 79

Extracting Sample Modules ... 80

Editing Modules... 81

Compiling New Modules ... 82

Revising Modules ... 82

Basic Use of Forms ... 83

Piping Specialty Components ... 84

Appendix: EDEN Error Messages ... 101

Index ... 105

(5)

Plant Design System (PDS) Piping Eden Interface

5

This document provides command reference information and procedural instructions for the Plant Design System (PDS) Piping Eden Interface taks.

List of PDS Documentation

 DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide  DPDS3-PB-200004 - Drawing Manager (PD_Draw) User's Guide

 DPDS3-PB-200005 - EE Raceway Modeling Reference Guide

 DPDS3-PB-200006 - Interference Checker/Manager (PD_Clash) User's Guide  DPDS3-PB-200010 - PDS 3D Theory User's Guide

 DPDS3-PB-200013 - PDS EDEN Interface Reference Guide Volume I : Piping  DPDS3-PB-200015 - PDS Equipment Modeling (PD_EQP) User's Guide  DPDS3-PB-200017 - PDS ISOGEN Reference Guide, Vol. 1

 DPDS3-PB-200022 - PDS Piping Component Data Reference Guide  DPDS3-PB-200023 - PDS Project Setup Technical Reference

 DPDS3-PB-200025 - PDS Stress Analysis Interface (PD_Stress) User's Guide  DPDS3-PB-200026 - Pipe Supports Modeler Reference Guide

 DPDS3-PB-200028 - Piping Design Graphics (PD_Design) Reference Guide  DPDS3-PB-200030 - Project Administrator (PD_Project) Reference Guide  DPDS3-PB-200033 - Project Engineer HVAC (PE-HVAC) Reference Guide  DPDS3-PB-200034 - Reference Data Manager (PD_Data) Reference Guide  DPDS3-PB-200035 - Report Manager (PD_Report) User's Guide

 DPDS3-PB-200041 - PDS EDEN Interface Reference Guide Volume 2 : Equipment  DPDS3-PB-200042 - PDS EDEN Interface Reference Guide Volume 3 : Pipe Supports  DPDS3-PE-200016 - PDS Express Project Creation Quick Start Guide

 DPDS3-PE-200052 - PDS Ortho Draw User's Guide

 DPDS3-PE-200029 - Piping Model Builder (PD_Model) Reference Guide  DPDS3-PE-200031 - Project Engineer HVAC Getting Started Guide  DPDS3-PE-200032 - Project Engineer HVAC Overview

 DPDS3-PE-200045 - PDS Label Library Merger Utility  DPDS3-PE-200047 - PDS Reference Data Auditing Tool  DPDS3-PE-200048 - Pipe Supports Explorer Utility  DPDS3-PE-200050 - Batch Services Quick Start Guide  DPDS3-PE-200051 - Batch Services User's Guide

(6)

6 Plant Design System (PDS) Piping Eden Interface

The following changes have been made to the Piping Eden Interface:

Version 2011 (V12)

 No changes were made for this release. Version 2010

 Added key numbers and gadget numbers for the following commands: Piping on Segment,

Point on Pipe, Move from Active Point, Move from Reference Point, Move to

Coordinate Axis, Intersection with Steel, and Connect to Piping. For more information,

see Piping Specialty Components (on page 84) (P4 PB:110372).

(7)

Plant Design System (PDS) Piping Eden Interface

7 S

E C T I O N

1

Eden is a high-level symbol definition language modeled on the FORTRAN programming language. The Eden language syntax is not case sensitive, except for module names, which are upper case. You can write code with whatever case conventions make it easiest for you to read.

Eden allows you to design your own symbols for piping, instrumentation, specialty items, and equipment. While you do not need a programming background to write Eden programs, any programming experience is highly recommended. You also need to be familiar with an ASCII text editor, such as vi, emacs, or Notepad.

Most of the symbol definition functions are built into Eden's command structure. This high-level command structure makes it easier to share code among several symbol definitions. For example, when designing a gate valve, the symbol definitions are used:

GATSP short pattern gate valve

GAT long pattern, bolted or male ends gate valve GATF regular pattern, female ends, full port gate valve GATR regular pattern, female ends, reduced port gate valve

These symbol definitions identify four specifically unique gate valves; however, each of these valves refers to the same:

 Primary physical data module (V1_AMS), which defines the specific dimensions and physical properties of a gate valve.

 Generic physical data module (VALVE_2_AMS), which defines flange thickness, gasket separation, and outside separation.

 Model graphic (V1).

By sharing these modules, you will not fill up valuable disk space with redundant data, which can also increase valuable processing time.

Eden is flexible enough to allow you to design codes specific to your company's needs, yet offers predefined subroutines, called primitives, which carry out functions often repeated within symbol definitions.

For example, the following primitive draws a cone with a length of X units, a diameter at the active point (first end) of Y units and a diameter at the opposite end of Z units:

Call Draw_Cone (X, Y, Z)

The output produced will look similar to the following graphic:

You can call up to five nested subroutines within a program.

(8)

8 Plant Design System (PDS) Piping Eden Interface

Graphic Commodity Data

The graphic commodity data is contained in the following object libraries:

 Graphic Commodity Library (on page 8) --- The delivered file ~\pdshell\lib\pip_gcom.l contains parametric definitions for the components.

 Physical Data (Dimensions) Library (see "Physical Data Tables" on page 10) --- The delivered file ~\rdusrdb\us_pcdim.l contains American dimension data for components.  Piping Job Specification Table Library --- The delivered file ~\rdusrdb\us_pjstb.l contains

specification tables referenced in the Piping Job Specification. See the Piping Job

Specification section in the Reference Data Manager Reference Guide for more information. Refer to Reference Data Overview section in the Reference Data Manager Reference Guide for more information.

When you select a component for placement in the model, the system:

 Uses the active parameters (such as piping materials class and nominal diameter) to search the Piping Job Specification (PJS) for the selected item name. If the selected item is found in the PJS database, the system reads the PJS for the parameters required to place the component. Included in this information is the model code (or specialty item number) for the selected component and the names of the spec tables defined for the Piping Materials Class.

 Uses the model code (or specialty item number), derived from the PJS, to access the graphic commodity library. The definitions in the graphic commodity library determine the physical tables required to place the component and call the tables in the physical

commodity library.

 Places the symbol graphics in the model design file and writes the nongraphic information for the component in the database.

This section describes the graphic commodity data used in placing components in the piping model. Refer to the Piping Design Graphics Reference Guide for a detailed description of the actual placement process.

Graphic Commodity Library

The Graphic Commodity Library (GCL) provides data for commodity items, engineered items, and instruments. It is basically a catalog of component data which is accessed to:

 Determine physical data based on user specifications (such as NPD and end preparation)  Assign connect point data from the Piping Job Specification

 Define the parametric shape for the model graphics. The Graphic Commodity Library includes data required for model creation, resymbolization for model presentation, interference detection, and any special functions of the Piping Job Specification, piping industry standards, or company design practices.

PDS Piping uses the Eden Parametric Language to define and place components, specialty items, operators, and envelopes. Eden is a high level language (similar to FORTRAN) which uses information from the Piping Job Specification and model to access parametric and dimensional data.

Eden is composed of three major modules.

(9)

The Eden Basics

Plant Design System (PDS) Piping Eden Interface

9

2. Physical Data Subroutines 3. Parametric Shape Definitions

These modules are designed to carry out two functions: data definition and graphic presentation. The data associated with these modules is delivered in the following files:

~\pdshell\lib\pip_gcom.l --- object library ~\pdshell\lib\pip_gcom.l.t --- text library

The modular approach provides for more efficient storage of information in these libraries by enabling common information to be shared by different symbols.

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

(10)

10 Plant Design System (PDS) Piping Eden Interface

The entries in the library use the following prefixes to identify the type of data:

SP Symbol Processor

PD Physical Data Definition Module UF User Function Module

MG Model Parametric Shape Definition Module

IG Interference Envelope Parametric Shape Definition Module SS Sub-Symbol Processor Module

Each module must be given a unique name within the graphic commodity library.

Physical Data Tables

The physical data tables contain the physical data (dimensions, weights, and surface area) required for symbol creation, interference detection, stress analysis, and MTO reporting. These tables are segregated for commodity item data, engineered item data, and instrument data. Refer to the Reference Data Manager Reference Guide for a detailed description of the physical data tables and the table naming conventions used in PDS.

The physical data tables for US Practice are delivered in the following files: ~\rdusrdb\us_pcdim.l --- object library

~\rdusrdb\us_pcdim.l.t --- text library ~\rdusrdb\us_pcdim.l.r --- revision library

These libraries contain physical data for American standards. The physical data can be stored in one of ten physical data libraries. The system uses the geometric industry standard for a

particular commodity item (or specialty item) to determine which library to reference for the physical data tables.

Geometric industry standard is expressed as a code list value from Standard Note Type 575. Code list numbers 2-6999 are reserved for standards that apply to American piping practices. Code list numbers 7000-27999 are reserved for standards that apply to European piping practices. Numbers 28000-31999 are reserved for specific company practices.

By segregating data into separate physical data libraries, you can access a subset of the total physical data available for a project. You can also build a specific set of physical data for a particular project. The following table types are required for piping and instrument components:  Generic dimensional data

Generic tables contain data that is not specific to a particular symbol (such as flange outside diameter or flange thickness). These tables are identified by the prefix BLT, FEM, or MAL (for the termination type) and end with the extension .TBL (the table name is independent of the name of the physical data module).

 Specific commodity data

Specific tables contain commodity data that is specific to a particular component (such as dimensions, water weight, and surface area). These specific tables use the model code or commodity code as part of the table name to classify data by symbol type.

 The system uses the water weight data to compute the wet weight using the specific gravity of the operating fluid.

fluid weight = water weight * specific gravity for fluid operating weight = dry weight + fluid weight

(11)

The Eden Basics

Plant Design System (PDS) Piping Eden Interface

11

 The surface area data enables the system to perform paint requirement calculations and insulation weight calculations.

 Specific commodity dry weight data  Piping Specialty physical data

The dimensions, dry weight, water weight, and surface area for specialty items can be stored in a set of tables or defined at placement.

 Instrument physical data

The dimensional data, dry weight, water weight, and surface area for instruments can be stored in a set of tables or defined at placement.

You can form the name of a physical data table from attributes for the component (such as geometry standard and end preparation). However, the table name cannot exceed 46 characters.

Data Retrieval from the Physical Data Library

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

Example of Physical Data Look-Up

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

Generic Tables

The spec access for a six-inch gate valve defines the end preparation at both connect points as Raised Face Flanged End (code list value 21), which is a bolted connection. As shown in the listing for VALVE_2_AMS, the table name for a bolted connection on a two-connect point valve is

table_name= 'BLT' // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green Using the values from the Piping Job Specification (PMC=1C0031, Item Name=6Q1C01), the actual table name will be:

BLT_20_150_5

This table returns the outside diameter, flange thickness, and the seating depth for each end of the valve. Note that the termination type (20) is used rather than the actual end preparation value (21).

Specific Tables

The specific tables are used to define the main body of the valve. Refer to the Table Requirement section in the Reference Data Manager Reference Guide for an outline of the types of tables that are required to place a valve. Since the termination type is the same at both ends of the valve (bolted), no red connect point data is required. The required tables are found by referring to the Bolted(G) termination type.

(12)

12 Plant Design System (PDS) Piping Eden Interface

 MC_GS_Term(G)_Rat(G)_B (P15B) --- This table is only required if more than eight

outputs are necessary to define a commodity item.  Commodity Code (P59).

Using this information, the dimension tables for a 6" gate valve are:  GAT_40_20_150_A

This table returns the face-to-center dimension for the valve. Table P15B is not required for a gate valve.

 VAABAHCCAA

This table returns the empty weight of the valve, including the weight of the operator. If the end preparations were different at each end of the valve (such as female threaded by socket welded), then a different set of tables would be required.

An additional table look-up is required to access the dimensional data for the valve operator. The following table is required to define the valve operator:

MC_Type(G)_Rat(G)_Op_A (P31A)

Using this table name format, the dimension table for a handwheel operator on a 6" gate valve is:

GAT_BLT_150_3_A

(13)

Plant Design System (PDS) Piping Eden Interface

13 S

E C T I O N

2

This section provides a step-by-step example of how PDS uses Eden and the information in the physical dimension tables to place components in a model.

Eden Modules

Eden is composed of three major modules:

1. Symbol Processors (on page 15) Sub-Symbol Processors (see "Sub-Symbol Processor" on page 16)

2. Physical Data Subroutines (see "Physical Data Definitions" on page 17) 3. Parametric Shape Definitions (on page 23)

These modules are designed to carry out two functions: data definition and graphic presentation. The data associated with these modules is delivered in the following files:

~\pdshell\lib\pip_gcom.l --- object library ~\pdshell\lib\pip_gcom.l.t --- text library

The modular approach provides for more efficient storage of information in these libraries by enabling common information to be shared by different symbols.

(14)

14 Plant Design System (PDS) Piping Eden Interface

The following graphic, Eden Module Relationships, illustrates the relationship among these modules:

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

The entries in the library use the following prefixes to identify the type of data: SP Symbol Processor

PD Physical Data Definition Module UF User Function Module

(15)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

15

IG Interference Envelope Parametric Shape Definition Module SS Sub-Symbol Processor Module

Each module must be given a unique name within the graphic commodity library.

Symbol Processors

A symbol processor is the controlling function or logic used to produce the graphics for a commodity item, piping specialty, instrument, pipe support, or interference envelope. During component placement, the symbol processor:

 Accesses the active component design parameters  Assigns connect points

 Calls the required physical data modules

 Determines and calls the required parametric shape modules.

The system retrieves the active component parameters which are dependent upon a connect point from the PJS in terms of green, red, or tap connect point properties. The symbol

definition assigns the data corresponding to these connect point types (green, red, or tap) to the physical connect point numbers (CP1, CP2, CP3, CP4, or CP5).

The first line of the Eden module defines the type of module and the module name. The following statement is used in the Eden modules to indicate a symbol processor module.

Symbol_Processor 'MODULE NAME'

This statement tells the system to use the category code SP for the prefix. You should use the following conventions in assigning the module name (the module name must be in UPPER CASE). The module name is determined by the type of component being placed (commodity item or specialty item).

 For a commodity item, the system searches for the New Item Name (model code) of the commodity item as the module name. If the New Item Name is blank in the Commodity Item entity, the system searches for the Item Name as the module name.

 For a specialty item, the system searches for the specialty item name (derived from the PJS) as the module name.

 For an instrument, the system searches for the instrument name (derived from the PJS) as the module name.

The delivered symbol processors are identified in the library with the prefix SP.

The following lists the symbol processor SPGAT, which is used to control the placement of a gate valve.

(16)

16 Plant Design System (PDS) Piping Eden Interface

Listing for Symbol Processor SPGAT

! REGULAR PATTERN, BOLTED OR MALE ENDS GATE VALVE Symbol_Processor 'GAT'

Call Assign_Connect_Point ( GREEN, CP1 ) Call Assign_Connect_Point ( RED, CP2 )

physical_data_source = 'V1' // Standard_Type Call Get_Physical_Data ( physical_data_source ) parametric_shape = 'V1'

Call Draw_Parametric_Shape ( parametric_shape ) Valve_Operator = DABS ( Valve_Operator ) If ( Valve_Operator .NE. 0 ) Then

If ( Valve_Operator .LT. 1000 ) Then Subcomponent = 'OP' // Valve_Operator Else

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

Sub-Symbol Processor

A subcomponent call in a symbol processor module indicates a sub-symbol processor. Subcomponents are additions to symbols such as an operator on a valve.

The first line of a sub-symbol processor module indicates the module type and the module name.

Sub_Symbol_Processor 'module name'

This statement tells the system to use the category code SS for the prefix.

The sub-symbol processor name for operators is a concatenation of the characters OP_ and the modifier value from the Commodity Item entity in the PJS database. The value is expressed as a code list number from CL550 (operator/actuator type). If the value is a positive number (such as 3) the operator is placed with the valve. If the value is a negative number (such as -3) the operator is not placed with the valve. (This is useful in segregating large diameter valves which almost always display a valve operator from small diameter valves, which frequently do not display an operator in the model.)

The symbol processor for the gate valve calls a sub-symbol processor (Subcomponent = 'OP' // Valve_Operator), which places an operator on the valve. The following depicts the sub-symbol processor SSOP_3, which is used to control the placement of a handwheel operator on the valve.

(17)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

17 Listing for Sub-Symbol Processor SSOP_3

! HANDWHEEL OPERATOR

Sub_Symbol_Processor 'OP_3'

If ( Operator_Orient .EQ. TRUE ) Then prompt = 1.0

Call Prompt_to_Orient_Operator ( prompt ) EndIf

physical_data_source = 'OPERATOR_3' Call Get_Physical_Data ( physical_data_source ) parametric_shape = 'OP3'

Call Draw_Parametric_Shape ( parametric_shape ) Stop

End

Physical Data Definitions

The system uses the physical data definitions to determine the dimension data, weight data, and surface area data using the active design parameters. Physical data modules are identified by the statement:

Physical_Data_Definition 'MODULE NAME'

as the first line in the Eden module. This statement tells the system to use the category code PD for the prefix. This prefix is only used by the system; it should not be keyed in as part of the module name.

The module name for a physical data module consists of a symbol type (such as V1, V2,... for valves) and a generic type of geometric industry standard (such as AMS or DIN). You can define multiple physical data modules for the same symbol depending on the type of standard being referenced (for example, V1_AMS for American standards and V1_DIN for European standards).

You can manage ten different sets of logic for table naming conventions for the following industry practices. The corresponding table suffix ranges and the suffix for the Piping Eden physical data modules are indicated below.

Practice Range Suffix

U.S. Practice 1-99 AMS

European - DIN 100-199 DIN

European - British Standard 200-299 BRITISH_STD

European - Practice A 300-399 EURO_A

International - JIS 400-499 JIS

International - Australian 500-599 AUS

European - Practice B 600-699 EURO_B

International - Practice A 700-799 INT_A International - Practice B 800-899 INT_B

Company Practice 900-999 COMPANY

The table suffix standard for a component is defined in the Piping Commodity Data table of the Material Reference Database. Each component must be assigned a geometric industry standard if it is to use physical data tables.

(18)

18 Plant Design System (PDS) Piping Eden Interface

For most of the delivered symbols, the physical data modules are classified into two categories: specific and generic. The specific physical data module is called by the symbol processor. This module then calls a generic physical data module.

Specific Physical Data Modules

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

Listing for Physical Data Module PDV1_AMS

Physical_Data_Definition 'V1_AMS'

physical_data_source = 'VALVE_2_AMS' Call Get_Physical_Data ( physical_data_source ) Call Read_Table ( Table_Name_A, input, output ) Surface_Area = Output_1

Wet_Weight = Output_2 F_to_C_Dim_1 = Output_3

If ( Term_Type_1 .EQ. Term_Type_2 ) Then F_to_C_Dim_2 = F_to_C_Dim_1

Else

F_to_C_Dim_2 = Output_4 EndIf

F_to_F_Dim = F_to_C_Dim_1 + F_to_C_Dim_2 If ( Valve_Operator .LE. 24.0 ) Then

Call Read_Table ( Table_Name_W, input, output ) Dry_Weight = Output_1

EndIf Return End

Generic Physical Data Modules

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

(19)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

19 Listing for Physical Data Module PDVALVE_2_AMS

Physical_Data_Definition 'VALVE_2_AMS' Input_1 = Nom_Pipe_D_1 If ( Gen_Type_1 .EQ. BOLTED ) Then

table_name = 'BLT' // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green Call Read_Table ( table_name, input, output )

Facing_OD_1 = Output_1 Thickness_1 = Output_2 Seat_Depth_1 = Output_3

Thickness_1 = Thickness_1 - Seat_Depth_1 CP_Offset_1 = Gasket_Sep_1

If ( Symbology .EQ. MODEL ) Then Thickness_1 = 0.0 Depth_1 = 0.0 Pipe_OD_1 = 0.0 Body_OD_1 = Facing_OD_1 Else table_name = 'MAL_300_5' Depth_1 = Thickness_1 Input_1 = Nom_Pipe_D_1

Call Read_Table ( table_name, input, output ) Pipe_OD_1 = Output_2

Body_OD_1 = Pipe_OD_1 EndIf

Else

If ( Gen_Type_1 .EQ. MALE ) Then

table_name = 'MAL' // Term_Type_1 // Gen_Flag_Green Call Read_Table ( table_name, input, output )

Facing_OD_1 = Output_2 Thickness_1 = 0.0 Depth_1 = 0.0 Seat_Depth_1 = 0.0 CP_Offset_1 = 0.0 Pipe_OD_1 = Facing_OD_1 Body_OD_1 = Facing_OD_1 Else

table_name = 'FEM' // Term_Type_1 // Pr_Rating_1 // Gen_Flag_Green

Call Read_Table ( table_name, input, output ) Facing_OD_1 = Output_1

Depth_1 = Output_2 Seat_Depth_1 = 0.0 Thickness_1 = 0.0

(20)

20 Plant Design System (PDS) Piping Eden Interface

If ( symbology .EQ. MODEL ) Then

Depth_1 = 0.0 CP_Offset_1 = 0.0 Pipe_OD_1 = 0.0 Body_OD_1 = Facing_OD_1 Else CP_Offset_1 = -Depth_1 table_name = 'MAL_300_5'

EndIf EndIf

If ( Term_Type_2 .EQ. Term_Type_1 .AND. Nom_Pipe_D_1 .EQ. Nom_Pipe_D_2 ) Then Facing_OD_2 = Facing_OD_1 Pipe_OD_2 = Pipe_OD_1 Body_OD_2 = Body_OD_1 Thickness_2 = Thickness_1 Depth_2 = Depth_1 Seat_depth_2 = Seat_Depth_1 CP_Offset_2 = CP_Offset_1 Else Input_1 = Nom_Pipe_D_2

If ( Gen_Type_2 .EQ. BOLTED ) Then

table_name = 'BLT' // Term_Type_2 // Pr_Rating_2 // Gen_Flag_Red Call Read_Table ( table_name, input, output )

Facing_OD_2 = Output_1 Thickness_2 = Output_2 Seat_Depth_2 = Output_3

Thickness_2 = Thickness_2 - Seat_Depth_2 CP_Offset_2 = Gasket_Sep_2

If ( Symbology .EQ. MODEL ) Then Thickness_2 = 0.0 Depth_2 = 0.0 Pipe_OD_2 = 0.0 Body_OD_2 = Facing_OD_2 Else Depth_2 = Thickness_2 table_name = 'MAL_300_5' Input_1 = Nom_Pipe_D_2

(21)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

21

Else

table_name = 'MAL' // Term_Type_2 // Gen_Flag_Red Call Read_Table ( table_name, input, output ) Facing_OD_2 = Output_2 Thickness_2 = 0.0 Depth_2 = 0.0 Seat_Depth_2 = 0.0 CP_Offset_2 = 0.0 Pipe_OD_2 = Facing_OD_2 Body_OD_2 = Facing_OD_2 Else

table_name = 'FEM' // Term_Type_2 // Pr_Rating_2 // Gen_Flag_Red

Call Read_Table ( table_name, input, output ) Facing_OD_2 = Output_1

Depth_2 = Output_2 Seat_Depth_2 = 0.0 Thickness_2 = 0.0

If ( Symbology .EQ. MODEL ) Then Depth_2 = 0.0 CP_Offset_2 = 0.0 Pipe_OD_2 = 0.0 Body_OD_2 = Facing_OD_2 Else CP_Offset_2 = -Depth_2 table_name = 'MAL_300_5' Input_1 = Nom_Pipe_D_2

Call Read_Table ( table_name, input, output ) Pipe_OD_2 = Output_2 Body_OD_2 = Pipe_OD_2 EndIf EndIf EndIf EndIf

Table_Name_A = Item_Name // Geo_Ind_Std // Term_Type_1 Table_Name_W = Commodity_Code

Input_1 = Nom_Pipe_D_1 Input_2 = Nom_Pipe_D_2

If ( Term_Type_1 .EQ. Term_Type_2 .AND. Nom_Pipe_D_1 .EQ. Nom_Pipe_D_2 )

Then

Table_Name_A = Table_Name_A // Pr_Rating_1 // 'A' Else

If ( Gen_Type_1 .EQ. Gen_Type_2 ) Then

! Male X Male or Bolted X Bolted

! or Female X Female

Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 // Pr_Rating_2 // 'A'

(22)

22 Plant Design System (PDS) Piping Eden Interface

! Male X Bolted and Male X Female

Table_Name_A = Table_Name_A // Term_Type_2 // Pr_Rating_2 // 'A'

Else

! Bolted X Male and Female X Male

Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 //

Else

! Bolted X Female and Female X

Bolted

Table_Name_A = Table_Name_A // Pr_Rating_1 // Term_Type_2 // Pr_Rating_2 // 'A' EndIf EndIf EndIf EndIf Return End

Listing for Physical Data Module OPERATOR_3

Physical_Data_Definition 'OPERATOR_3' Input_1 = Nom_Pipe_D_1

If ( Gen_Type_1 .EQ. BOLTED ) Then

Table_Name_A = Item_Name // 'BLT' // Pr_Rating_1 // Valve_Operator // 'A'

Else

Table_Name_A = Item_Name // 'MAL' // Pr_Rating_1 // Valve_Operator // 'A'

Else

If ( Gen_Type_1 .EQ. FEMALE ) Then

Table_Name_A = Item_Name // 'FEM' // Pr_Rating_1 // Valve_Operator // 'A'

EndIf EndIf EndIf

Call Read_Table ( Table_Name_A, input, output ) Dimension_1 = Output_1

Dimension_2 = Output_2 OP_Weight = 0.0

Return End

(23)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

23 Parametric Shape Definitions

The parametric shape definition describes the graphics symbol (such as bend, flange, or valve body) that is placed for the component in the model.

Parametric shape definitions are used to place symbol graphics in the model or define interference envelopes. This involves the following major functions:

 Defining connect point geometry  Placing connect points

 Moving the active location a specified distance  Drawing a specific graphic shape

 Placing a center of gravity location.

Parametric shape definitions are divided into two basic types: model parametric shapes and interference envelopes. The first line of the Eden module indicates the module type and the module name.

Model Parametric Shape Definitions

Model parametric shapes are used to define the symbol graphics to be placed in the model. For example, the parametric shape module for a valve consists of a cylinder, two cones, and a cylinder (flange, valve body, flange).

The first line for these modules is of the form

Model_Parametric_Shape_Definition 'MODULE NAME'

This statement tells the system to use the category code MG for the prefix. This prefix is only used by the system; it should not be keyed in as part of the module name.

The module name for a parametric shape module consists of a symbol type (such as V1, V2,... for valves).

The parametric shape module MGV1 determines the model graphics for a valve. This is the module called by the symbol processor SPGAT. The parametric shape module MGOP3 determines the model graphics for a handwheel operator. This is the module called by the sub-symbol processor SSOP_3.

Listing for Parametric Shape Module MGV1

Model_Parametric_Shape_Definition 'V1'

Call Define_Connect_Point_Geometry ( LINEAR ) Call Place_Connect_Point ( CP1 )

Call Move_By_Distance ( CP_Offset_1 )

Call Draw_Cylinder_With_Capped_Ends ( Depth_1, Facing_OD_1 ) length = F_to_C_Dim_1 - Thickness_1

diameter = 0.0

Call Draw_Cone ( length, Body_OD_1, diameter ) Call Place_Connect_Point ( CP0 )

Call Place_COG_Location ( DRY_COG ) Call Place_COG_Location ( WET_COG )

length = F_to_C_Dim_2 - Thickness_2 Call Draw_Cone ( length, diameter, Body_OD_2 )

Call Draw_Cylinder_With_Capped_Ends ( Depth_2, Facing_OD_2 ) Call Move_By_Distance ( CP_offset_2 )

Call Place_Connect_Point ( CP2 ) Return

(24)

24 Plant Design System (PDS) Piping Eden Interface

Listing for Parametric Shape Module MGOP3

Model_Parametric_Shape_Definition 'OP3'

Call Define_Connect_Point_Geometry ( OPERATOR ) Call Convert_NPD_to_Subunits ( Nom_Pipe_D_1, dia ) dist = dia + Min_Cyl_Dia * 0.5

angle = 90.0

radius = ( Dimension_2 - Min_Cyl_Dia ) * 0.5

Call Draw_Cylinder_With_Capped_Ends ( Dimension_1, Min_Cyl_Dia ) Call Move_by_Distance ( -dist )

Call Rotate_Orientation ( angle, Secondary ) Call Rotate_Orientation ( angle, Normal ) Call Move_Along_Axis ( -radius, Secondary ) Call Draw_Torus ( radius, angle, Min_Cyl_Dia ) Call Draw_Torus ( radius, angle, Min_Cyl_Dia ) Call Draw_Torus ( radius, angle, Min_Cyl_Dia ) Call Draw_Torus ( radius, angle, Min_Cyl_Dia ) Return

End

Interference Parametric Shape Definition

Interference parametric shapes are not used during component placement. They are referenced during interference detection to determine the volume (interference envelope) to be compared for clashes with other elements. If a clash is detected during the interference detection process, the interference parametric shape is used to place an interference marker. Refer to the PDS Interference Checker/Manager (PD_Clash) User's Guide for more information on interference envelopes.

Interference_Parametric_Shape_Definition 'MODULE NAME' This statement tells the system to use the category code IG for the prefix.

The module name for the interference parametric shape definition should be the same as the module name for the model parametric shape definition.

If no interference module is found for a component, the system uses the model graphics module to determine the interference parametric shape.

(25)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

25 Listing for VI IFC

Interference_Parametric_Shape_Definition 'V1' Call Define_Connect_Point_Geometry ( LINEAR ) dist = 0.0

If ( Gen_Type_1 .EQ. BOLTED ) Then extra1 = CP_Offset_1

Else

extra1 = 0.0

dist = CP_Offset_1 EndIf

If ( Gen_Type_2 .EQ. BOLTED ) Then extra2 = CP_Offset_2

Else

extra2 = 0.0 EndIf

sec1 = Depth_1 + extra1 sec2 = Depth_2 + extra2

diameter1 = Facing_OD_1 + Insulation * 2.0 diameter2 = Facing_OD_2 + Insulation * 2.0 diameter3 = Body_OD_1 + Insulation * 2.0

length = F_to_C_Dim_1 - Thickness_1 + F_to_C_Dim_2 - Thickness_2 Call Move_By_Distance ( dist )

If ( diameter1 .GE. diameter2 ) Then

Call Draw_Cylinder_With_Capped_Ends ( sec1+sec2+length, diameter1 )

Else

Call Draw_Cylinder_With_Capped_Ends ( sec1+sec2+length, diameter2 )

EndIf Return

End

Listing for OP3 IFC

Interference_Parametric_Shape_Definition 'OP3' Call Define_Connect_Point_Geometry ( OPERATOR ) Call Convert_NPD_to_Subunits ( Nom_Pipe_D_1, dia ) dist = dia + Min_Dimension * 0.5

Call Draw_Cone_With_Capped_Ends ( Dimension_1 - dia, 0.0, Dimension_2 )

Call Draw_Cylinder_With_Capped_Ends ( dia, Dimension_2 ) Return

(26)

26 Plant Design System (PDS) Piping Eden Interface

Forms Interface

Forms in piping design serve to collect input via key-in fields or command buttons. They also provide feedback information to the user through message fields.

The data gathered through the forms serves as the input that defines the values of the global variables used by the Eden modules. When a new specialty item is defined through Eden a form specific to that item can be created using the Form Builder and Symbol Editor products, or the DBAccess product.

Notes for Graphic Commodity Data

The following sections provide additional information about graphic commodity data.  Connect Point Data (on page 26)

 Bends and Branches (on page 28)  Bolts, Gaskets, and Flanges (on page 28)  Pipe, Tubing, and Hose (on page 29)

Connect Point Data

As described in the Piping Job Specification description, connect point information for commodity items, piping specialties, and instruments is classified in terms of green and red connect points. The following conventions are used to coordinate the two sets of data:  For full-size components, data is only defined for the green connect point and applies to all

ends of the component.

 For size change components, data for commodity items, speciality items, or instruments should be created with the green connect point representing the larger diameter (first size) of the component and the red connect point diameter representing the smaller diameter

(second size).

If the end preparation is different at each end of the component, the end preparation should be defined to match the required green and red connect points.

 If a component has ends with the same nominal diameter but other end properties that differ, the following rules apply:

 If the ends have different end preparations (regardless of the values for

schedule/thickness) the end(s) whose end preparations have the lowest code list number are designated as the green connect point.

 If the end preparations are the same but the values for rating, schedule, or thickness differ, the "stronger" end(s) are designated as the green connect point.

 Schedule or thickness values should be defined for all applicable components. Refer to the PJS Tables and Functions section in the Reference Data Manager (PD_DATA) Reference Guide for a detailed description of the methods for defining the schedule or thickness value.  A flow direction component (such as a check valve) must be defined so that the flow is

(27)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

27

 A tee type branch must be defined with connect point three on the branch leg of the tee.

 The origin of a component must lie between connect point 1 and connect point 2.  Flanges should be defined with the green connect point representing the flanged connect

point and the red connect point representing the non-flanged connect point.

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

 To ensure consistency in pipe cut length calculations, the connect points of a component should be located using face-to-face or face-to-center dimension rather than end-to-end or end-to-center dimension.

 A change of direction component placed by component center must be defined such that connect point 1 is on the primary axis.

(28)

28 Plant Design System (PDS) Piping Eden Interface

Bends and Branches

 For bend components (specific and generic), the item name must be unique with respect to the angle of the bend. In other words, you specify the angle of the bend by selecting the item name for the corresponding angle of the bend.

 The number of joints in a miter is required to compute the stress intensification factor (SIF). The graphics symbol description in the Graphic Commodity Library sets an attribute in the piping design database that defines the number of joints.

For miter bend components, the system requires that the item name and the new item name be unique with respect to the number of miter joints of the bend. In other words, the item name specifies the number of miter joints of the bend.

 For branches (tees and laterals), the system uses the first and second size to access the branch table and to determine the item name of the component to be placed at the branch point (intersection). Depending on the active values, the branch table may define a single component or a set of two or three components.

Bolts, Gaskets, and Flanges

 The data for the number of bolts and the bolt diameter is available with the flange data in the Physical Dimension Table Library as a function of nominal piping diameter, pressure rating, termination type, and geometric industry standard. However, the bolt data and the flange data are stored in separate tables. Refer to the Report Manager (PD_Report) User's Guide for a description of the table access.

 A lap joint flange is defined with the end preparation at one end as flanged and the other end as lap.

 The system determines the gasket separation at each connect point of a piping component, speciality item, and an instrument component by the following rules:

 If the end preparation for the connect point is flanged, the gasket separation for the connect point is set to one-half the Active Gasket Separation. However, some flanged connections (lug, ring type joint, or wafer) have integral gaskets and do not have a gasket separation. In this situation, the gasket separation at each connect point is set to zero.

 If the end preparation for the connect point is not flanged, the gasket separation for the connect point will be set to zero.

 Flange data exists in two tables.

 The first table (BLT_Term_Rat_TS) contains the flange data required for modeling activities (such as flange outside diameter and flange thickness).

 The second table (STUD_Rat_TS) contains flange data required for reporting or analysis activities (such as bolt diameter, number of bolt holes, and nut extension).

(29)

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

29 Pipe, Tubing, and Hose

 All tubing (such as fiberglass and copper) is specified in terms of piping outside diameter rather than nominal piping diameter. All commodity item data in the Physical Dimension Table Library exists in terms of nominal piping diameter.

 Mechanical joint and cast iron pipe can have various fixed lengths. Polypropylene-lined tube is purchased with flanged ends in various fixed lengths.

 Piping wall thickness is defined in terms of NPD units rather than model units.

 A piping converter component (which converts nominal piping diameter from one system of units to another system of units) must be defined in the PJS database for each specific pair of nominal piping diameters. You cannot specify a converter component for a range of nominal piping diameters.

(30)

(31)

Plant Design System (PDS) Piping Eden Interface

31 S

E C T I O N

3

Eden is similar to the FORTRAN programming language. Therefore, the general rules for evaluating expressions in Eden are identical to those in FORTRAN.

You do not need to know FORTRAN to use the Eden language.

Eden definitions are usually simpler than FORTRAN programs. To use Eden, you must be able to visualize the symbol (in 3D) that you want to develop.

The Eden language structure incorporates:  Statements  Beginning  Ending  Variables  Local  Global  Keywords

 Connect Point Geometry (piping only)  Operators  Arithmetic  Relational  Logical  Expressions  Functions

 Primitives (or Subroutines)

Beginning Statements

Beginning statements define the types of modules being entered. Names within the single quotes must be all upper case.

SP - Symbol_Processor '6CHAR' SS - Sub_Symbol_Processor '6CHAR' PD - Physical_Data_Definition '28CHAR' UF - User_Function_Definition '28CHAR' MG - Model_Parametric_Shape_Definition '28CHAR' IG - Interference_Parametric_Shape_Definition '28CHAR'

Examples

Symbol_Processor 'GAT' Physical_Data_Definition 'V1_AMS'

(32)

32 Plant Design System (PDS) Piping Eden Interface

Ending Statements

Ending statements mark the end of the module in which the system has been processing. Ending statements in the symbol and subsymbol processor (beginning statements SP and SS) include:

Stop End

Ending statements in the children processor (beginning statements PD, UF, MG, and IG) include:

Return End

Variables

Variables in Eden can be either local or global. They can contain either numeric or alphanumeric data. Internally, numeric data is stored as REAL*8 (double precision). If a different data type is required in the context of an expression, then the conversion is performed at the time the expression is evaluated.

Variable names can be either upper or lower case. Symbols tend to be easier to read when you use all lower case for local symbols and all upper case for global symbols or vice versa.

Examples

 When converting a floating point number to an integer, the fractional part of the floating point number is truncated.

 A variable used in a logical expression evaluates to TRUE when the value of the variable is 1 and 0 when the logical value is FALSE.

 Variables that hold values representing distances are assumed to be in subunits. A variable containing the value 25 represents 25 inches in an English unit design file and 25 millimeters in a metric unit design file.

Be careful when using hard coded numbers or when using the system_of_units variable.

Local Variables

Local variables are user defined and declared in the symbol definition. You can refer to a local variable only when you are in the same module as the local variable.

Local variable names are formed using alphanumeric (a-z), numeric (1-9), and special (_ and $) characters. They must begin with an alphanumeric character and must be less than or equal to 31 characters in length.

The Eden compiler does not verify the spelling of local variables within call

statements. It assumes a null value for the misspelled variable at component placement time. The Eden language refers to constants as local variables. Both character strings and numeric constants are valid; however, character string constants must be surrounded by single quotes. In most cases, character strings and constants are case sensitive. Thus, a and A are

(33)

Eden Language Structure

Plant Design System (PDS) Piping Eden Interface

33 Examples

diameter 13.25

shell_thickness 'A TEXT STRING' projection_1 radius [2]

25

Only in Pipe Support and Equipment Modeling can you declare local variable types. The variable types default to either CHARACTER or REAL depending on the context. To override this default, you can use a local variable type declaration statement anywhere before the variable(s) is (are) actually referenced. Variable types INT2, R8, and LOCATION are recognized by the compiler.

Example

In the following example, variables a, B, and C are declared as type short integers. They hold values ranging from -32767 to 32767.

Int2 a Int2 B, C

Example

In the example below, variable d is declared as a type REAL, capable of holding decimal fractional values. This is the usual default type for numeric variables. However, explicit typing to this category may be necessary to declare local arrays.

R8 d

As a recommendation, all declaration statements should be placed at the very beginning of the symbol code and not interspersed among statements to be executed during symbol placement. This improves program readability.

Also in Pipe Support and Equipment Modeling, referencing a variable using subscripts is extremely useful when coding repetitive statements such as the body of a loop. Prior to use, variables must appear in a type declaration in which its subscript or index range is also specified.

Example

Below, LENGTHS is an array of 10 REAL variables. They are referenced as LENGTHS [1] ... LENGTHS [10].

(34)

34 Plant Design System (PDS) Piping Eden Interface

Global Variables Common to Piping, Equipment, and Pipe

Support Modeling

Global variables are system-defined names allowing you to refer to them at any subroutine level. More specifically, you can use them for passing values between subroutine levels or for

communicating input values to the symbol. The following list shows the global variables common to all Eden applications. Refer to the application-specific section for detailed information concerning specific global variables.

Global variables are system-defined. You cannot declare global or subscripted global variables.

Input_n (Input_1 through Input_20) An array with up to 20 variables used to define the input parameters for table lookups. (Input_11 through Input_20 are specifically designed for user function arguments in equipment and pipe support modeling.)

Output_n (Output_1 through Output_20) An array with up to 20 variables where the results of the table lookup are stored. (Output_11 through Output_20 are specifically designed for user function return arguments in equipment and pipe support modeling.) Dimension_n (Dimension_1 through Dimension_20) General purpose

variables used for communicating input to the symbol logic. You can also use these variables for passing values between subroutines or simply for local storage. (Dimension_20 is for angle; Dimension_1 through Dimension_19 is for linear piping.) Pr_Rating_n Variable containing the current item pressure rating value. Nom_Pipe_D_n Variable containing the current item nominal pipe diameter. This

variable contains the nominal diameter in coded units. A special primitive is provided to help you convert from coded units to subunits.

Gen_Type_n Variable containing the current item end preparation generic type (BLT, MAL, FEM). This is a read-only variable.

Term_Type_n Variable containing the current item end preparation termination type (21, 22, and 23 will fall into Term_Type_1=20). This is a read-only variable.

Standard_Type Variable containing the current item standard type value. This is a read-only variable and is a function of TABLE_SUFFIX. System_Of_Units Variable defining the current system of measurement. Valid

(35)

Eden Language Structure

Plant Design System (PDS) Piping Eden Interface

35 Piping Eden Global Variables

Bend_Angle The bend angle is defined at placement for a component that has a variable sweep angle.

Bend_Radius The bend radius is defined through the component itself by means of a table lookup.

Bend_Radius_NPD The bend radius in terms of NPD from the PCD file for the bend component.

Body_OD_n (n = 1-5) The body outside diameter is the outer diameter of either a bolted, male, or female end of the indicated termination type.

BOLT_DIAMETER BOLT_EXTENSION

Diameter information not used when placing a flanged

component. Table lookups are performed during the execution of the MTO process when two mating flanges are found. These keywords are used to hold the data retrieved for the table and then pass on to the MTO process.

Br_Ref_Thick The branch reinforcement thickness. Br_Ref_Width The branch reinforcement width. Branch_Angle Used for a table name lookup.

Branch_Table Identifies the branch insertion table used to determine the name of the branch commodity item to be used for tee and lateral branches.

Commodity_Code A user-assigned code that together with the NPD and schedule/thickness uniquely defines the component.

CP_Offset_n (n = 1-5) The connect point offset adjusts the graphics relative to the connect point (for flanges, it adjusts for the gaskets) for female, adjust for penetration. Male is set to zero.

CP_Normal_n (n = 1-5) The normal vector.

CP_Primary_n (n = 1-5) The flow centerline vector. CP_Secondary_n (n = 1-5) The secondary vector. CP_to_Origin_n (n = 1-5) The CP to origin dimension.

Depth_n (n = 1-4) The connect point depth is the depth of a socket as defined in the table FEM_Term_Rat_TS. It determines a component's dimensional parameters by calculating the depth of the socket minus 1/16 inches.

DIM_TOLERANCE = 1/64 in.

The minimum dimension standards are the minimal values permitted in the Eden program. The minimum distance used for checking connect point separation if 400 units of resolution (USRs), which is approximately equal to 1/5 inch.

Dry_COG The center of gravity dry. Dry_Weight The dry weight.

(36)

36 Plant Design System (PDS) Piping Eden Interface

Facing_OD_n (n = 1-5) The facing outside diameter is the outer diameter of

either a bolted, male, or female end of the indicated termination type.

F_to_C_Dim_n F_to_F_Dim

(n = 1-5) The face-to-center and face-to-face dimensions retrieve information from a dimension table and pass that information to the database for the appropriate connect point or face to face dimension.

Gasket_Sep_n (n = 1-5) The gasket separation.

Gen_Flag_Red Gen_Flag_Green

The generic flag retrieves the table suffix for use with table identification.

Geo_Ind_Std The geometric industry standard is used to define table lengths. The data comes from the piping component data entry.

Insulation The insulation thickness is defined by the designer at time of pipeline placement. It is used to increase the volume of the interference detection and the display of the Insulation Graphics. Insulation_n (n=1 to 4) This variable is used to exclude insulation by connect

point.

Item_Name This variable equates to the model code used in defining a table name.

MIN_CYL_DIA = 1/32 in.

The minimum cylinder diameter permitted in the Eden program.

MIN_DIMENSION = 5/8 in.

Hard-coded global variable. The minimum linear dimension value permitted by the Eden program is approximately 1/16 inch.

Min_Weld_Size The minimum weld size retrieves output from the Branch_Angle/Branch_Table.

Nipple_Length The nipple length is retrieved from the modifier column in piping component data from the reference database.

(37)

Eden Language Structure

Plant Design System (PDS) Piping Eden Interface

37

Nom_Bend_Rad The nominal bend radius. This variable will write to the database and allow reconstruction of the component.

NUMBER_BOLTS Table lookups are performed during the execution of the MTO process when two mating flanges are found. This keyword is used to hold the data retrieved for the table and then pass on to the MTO process.

Number_Miter The number of miter joints is the number of miters to be used in a mitered joint. It is retrieved from the modifier column in the piping component data from the reference database.

Number_of_Taps The number of taps is retrieved from the modifier column in the piping component data from the reference database.

Operator_Orient Prompts for a secondary orientation of an operator. For example, a handle for a lever or gear operator.

Op_COG The operator center of gravity.

Op_Weight The operator weight data referenced from a table and stored in the database.

Or_Port_Size The orifice port size is defined in the Eden code. Pipe_OD_n (n = 1-5) The piping outside diameter.

Seat_Depth_n (n = 1-5) The seating depth is the depth as defined in the table BLT_Term_RAT_TS. The dimension represents the distance from the outermost surface of the bolted end to the seating surface of the gasket.

Sch_Thick_n (n = 1-5) The schedule/thickness is the wall thickness of the applicable end of a component of the indicated nominal diameter as defined in the table MALWT_Term_Sc/Th_TS_WC.

Stem_Length The stem length table lookup/calculated --- stored in database. Surface_Area The surface area data referenced from a table and stored in the

database.

Symbology Defines the use of simple or detailed graphics. Table_Name_A

Table_Name_B

Stores the dimension table name.

Table_Name_W Stores the weight table name.

Thick_Table_Name Identifies the thickness data table used in piping wall thickness calculations for this piping material class.

Toggle_n (n = 1-5) Currently used only for valve operations.

Valve_Operator The valve operator is the value retrieved from the modifier data and tells what valve operator to place.

Weight_Code Defines the weight code for the component and determines the table to be used in finding the dry weight.

(38)

38 Plant Design System (PDS) Piping Eden Interface

Wet_COG The wet center of gravity.

Wet_Weight The fluid volume weight data referenced from a table stored in the database.

Common Keywords

Eden uses keywords for labeling specific values or groups of values. All keywords except TRUE and FALSE can appear as arguments in system-defined primitives (or subroutines). Keywords can be upper or lower case. For consistency, this reference guide displays keywords in upper case.

TRUE Logical true. Used in logical expressions. FALSE Logical false. Used in logical expressions. MALE

FEMALE BOLTED

Keywords for generic end preparation.

PRIMARY SECONDARY NORMAL

Keywords used to identify or refer to individual refresh tee axes.

ENGLISH METRIC

Names used to define the units of a constant used in the symbol definition.

Keywords (Piping Specific)

The following keywords are specific to the Piping Eden interface. GREEN

RED

The spec connect point properties assign connect point properties to a given connect point (that is, end prep, schedule, pressure, table suffix) retrieved from the active material class.

CPn The connect point numbers.

NULL_GEN_TYPE The generic term type is used in testing the current end preparation retrieved from the commodity to determine the necessary graphics and dimensions needed to construct the components connection graphics.

THICKNESS_n (n = 1-5) The fitting CP thickness (flange_depth,

thread_depth, or socket_depth) represents the distance from the outermost face of the flange to the back surface of the flange on which the nut rests including any projections on the flange.

NULL_PRESSURE 0 WALL_THICKNESS SCHEDULE

CALCULATE

PDS Piping Eden Interface

Plant Design System (PDS)

Piping Eden Interface

Plant Design System (PDS) Piping Eden Interface

3

Contents

4

Plant Design System (PDS) Piping Eden Interface

Plant Design System (PDS) Piping Eden Interface

5

List of PDS Documentation

6

Plant Design System (PDS) Piping Eden Interface

Plant Design System (PDS) Piping Eden Interface

7

S

E C T I O N

1

8

Plant Design System (PDS) Piping Eden Interface

Graphic Commodity Data

See Also

Graphic Commodity Library

The Eden Basics

Plant Design System (PDS) Piping Eden Interface

9

10

Plant Design System (PDS) Piping Eden Interface

Physical Data Tables

The Eden Basics

Plant Design System (PDS) Piping Eden Interface

11

See Also

Data Retrieval from the Physical Data Library

Example of Physical Data Look-Up

Generic Tables

Specific Tables

12

Plant Design System (PDS) Piping Eden Interface

Plant Design System (PDS) Piping Eden Interface

13

S

E C T I O N

2

Eden Modules

14

Plant Design System (PDS) Piping Eden Interface

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

15

Symbol Processors

16

Plant Design System (PDS) Piping Eden Interface

Listing for Symbol Processor SPGAT

Sub-Symbol Processor

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

17

Listing for Sub-Symbol Processor SSOP_3

Physical Data Definitions

18

Plant Design System (PDS) Piping Eden Interface

Specific Physical Data Modules

Listing for Physical Data Module PDV1_AMS

Generic Physical Data Modules

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

19

Listing for Physical Data Module PDVALVE_2_AMS

20

Plant Design System (PDS) Piping Eden Interface

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

21

22

Plant Design System (PDS) Piping Eden Interface

Listing for Physical Data Module OPERATOR_3

Component Placement Example

Plant Design System (PDS) Piping Eden Interface

23