Design Conventions for Catalogues and Specifications
Hangers and Supports : Hangers & Supports Configurations and Data Tables : Data Tables
Data Tables
Data tables use the existing AVEVA E3D™ specification hierarchy as a way to extract cross-referenced data, using many parameters, without having to read a lot of external files. There are currently three forms of data which are stored this way:
•
Hanger Lengths
•
Hanger/Steel Clearances
•
Maximum Unsupported Spans
Data tables for Hangers & Supports should exist in a SPWL with PURP set to HSUP.
Hanger Length Table
The Hanger Length Table is used by the application to determine the minimum and maximum Head to Tail lengths for a given configuration. This is checked every time a hanger is created, but it is most important for template-type configurations which use the minimum length to position the supporting members. The values derived from this table override the values set in the configuration CATE :MAXLEN and :MINLEN attributes.
The Hanger Length Table should be in a SPEC with PURP set to HMML. An example named /CADC/HS/SAMPLE/SPEC/HANGLEN is supplied with the product.
The following hierarchy is mandatory for the Hanger Length Table:
SPEC
 
QUES
PBOR
 
:VISI
false
 
PURP
HMML
 
DESC
<optional text description>
1st Level of SELE
 
ANS
<pipe nominal bore>
 
QUES
SMAT
2nd Level of SELE
 
TANS
<steel material code> *
 
QUES
PMAT
3rd Level of SELE
 
TANS
<pipe material code> *
 
QUES
HTYP
SPCO level
 
ANS
<length type code> **
 
TANS
<hanger configuration type code> ***
 
COMM
<min length>/<max length> (including units, e.g. 0mm/60mm)
*
Material codes are defined in the application defaults from the Settings>Admin>Materials menu option.
**
This can be set to 0 or 1:
1 - Lengths are calculated from outside of pipe. This is the default mode if a configuration is not defined in the Hanger Length Table.
0 ‑ Lengths are calculated from the C/L of the pipe. In this mode, the application selects the PCLA to calculate the minimum length when creating support templates
***
Code corresponds to the Hanger Build Macro suffix and the GTYP of the configuration CATE.
Hanger Clearance Table
This table is used at two stages during the creation of a support (with steelwork). First when initially applying a configuration to deduce the lengths of the supporting members, and again when the profiles have been selected to maintain the minimum clearance between hanger attachment points and supporting member ends. There are three types of clearance code, depending on the type of joint at the member end:
A1
Free end (no joint) before profiles set
A2
Free end after profiles set
B
Perpendicular joint
C1
Angled end (braced free end - only really used in the ‘Braced Cantilever’ type configuration) before profiles set
C2
Angled end after profiles set
The following hierarchy is mandatory for the Hanger Clearance Table:
SPEC
 
QUES
PBOR
 
:VISI
false
 
PURP
HCLR
 
DESC
<optional text description>
1st Level of SELE
 
ANS
<pipe nominal bore>
2nd Level of SELE
 
TANS
<clearance code>
 
QUES
HTYP
SPCO Level
 
TANS
<hanger configuration type code> *
 
COMM
<clearance> (measured from pipe C/L including units, e.g. 75mm)
*
Code corresponds to the Hanger Build Macro suffix and the GTYP of the configuration CATE
Maximum Unsupported Span Table
Some users base maximum unsupported spans for pipes on ‘Span Tables’. The Hangers & Supports application provides a method whereby these tables can be entered into a data table and the maximum spans can be graphically indicated in the 3D model by partially highlighting the supported branches.
The PURP attribute of the Span Table SPEC should be set to HSPT, the :VISI set to false, and the DESC attribute may have an optional description text.
The hierarchy for this data table is variable, depending on the number of parameters which you wish to cross-reference, but the format is as follows:
At SELE/SPCO Owner
 
TDEF
<expression>
 
This expression can be anything which yields a single numeric or text value based on the current HANGER. It is recommended that the supplied user function SELEATT be used, as this will return the value of any attribute or any pseudo-attribute of any part of the hanger or related support or pipe. For example:
USRFUNC (SELEATT ATTA LBOR) returns the leave bore of the ATTA.
USRFUNC (SELEATT ATTA $<part (RTEX of DETREF of LSTU , 2)$>) returns the schedule of the attached pipe (for the standard AVEVA pipe specs).
USRFUNC (SELEATT BRAN TEMP) returns the temperature rating of the attached branch.
 
(See the internal macro documentation of SELEATT for further details of this function.)
At SELE/SPCO
 
TANS
<test>
 
This test is used for the data returned by the owner's TDEF expression to yield a logical true or false.
 
Suitable tests might be (for the above examples):
eq 20
eq 'SCH80' (notice the use of quotes '...' and not vertical bars |...| )
lt 177
 
Tests are performed in list order, so if multiple matches are possible, the first is assumed. In this way, ranges can be defined (as with the temperature example above) by using lt or gt and putting the test values in increasing or decreasing order as applicable.
The actual span is stored in the COMM attribute of the SPCO. The application will return an error value if matches cannot be made from the Span Table.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo