Professional Documents
Culture Documents
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.
Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every
part of it (including source code, object code, any data contained in it, the manual and any other
documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.
All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective license agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
First published September 2007
AVEVA Solutions Ltd, and its subsidiaries
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.
Page
Design Conventions
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Who Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Purpose of the Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
What the Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Other Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Datasets
2:2
2:2
2:2
2:3
2:3
2:4
2:4
2:4
2:4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10
Specification for Structural Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:11
12.0
2:11
2:12
2:13
2:14
3:2
3:2
3:2
3:4
5:21
5:22
5:22
5:24
5:24
5:25
5:26
ii
12.0
1.1
1.2
1.3
Chapter 2 details the conventions used for setting up the structural Catalogues and
Specifications used by the Beams & Columns and Panels & Plates applications.
Chapter 3 details the conventions used for setting up the structural Catalogues and
Specifications used by the Hangers & Supports applications.
Chapter 5 lists the full Specification Tables used to hold data specific to the Hangers &
Supports application.
1:1
12.0
1.4
1:2
12.0
2.1
Catalogues
You must use the following conventions for structural catalogues so that the DESIGN
applications can recognise them and so that the PARAGON applications can use them:
The PURPose of the CATAlogue must be set to one of the following: STL, FITT, JOIN
or PFIT. This ensures that any specifications and applications which are built can
recognise the correct catalogue element. Thus the steel Profile specification looks for
the purpose STL, the Joint specification looks for the purpose JOIN, the Fitting
specification looks for the purpose FITT and the Panel Fitting specification looks for the
purpose PFIT. A meaningful DESCription is also beneficial.
The PURPose of the STSEction must be set to REF for Reference Data, PRFL for
Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.
The PURPose of the STCAtegory must be set to REF for Reference Data, PRFL for
Profiles, FITT for Fittings, JOIN for Joints and PFIT for Panel Fittings.
The GTYPE of the Profile, Fitting, Joint or Panel Fitting must be set. This ensures that
specific restrictions can be applied to Joints and Fittings when building the
specifications. For example: any Section with a GTYPE set to BEAM can be used with
a Joint which has its GTYPE set to BEAM; any Fitting with a GTYPE set to FITT can be
used with any Fitting specification.
The purpose of a CSTANdard is to let you define in a text string the type of standard
that is being used. It is used purely for information and administration of the Catalogue.
For example, the CSTANdard for British Sections is BS 5950.
The diagrams in the following subsection illustrate the structure of the catalogues.
2.1.1
PROFILES
JOINTS
The basic layout of the catalogues is the same as for piping, i.e. where the reference data is
stored, but the way in which the data is separated differs.
2:1
12.0
2.1.2
Administrative Elements
CATAlogue
Description
Description of catalogue
Purpose
Cstandard
Catalogue standard
Description
Description of Section
Gtype-
Description
Description of category
Purpose
Function
Description
Gtype
2:2
12.0
Description
Description of category
Skey
not applicable
Ptref
Gmref
Ngmref
DataSetRef
Pstreference
Gstreference
CDetail
Detail reference
Ownconn
Attconn
CPlot
Icon
Icon name
Cstandard
Standard
Description
Gtype
Skey
Purpose
Description
Gtype
Purpose
2:3
12.0
2.2
Description
Gtype
Purpose
DTSE - Datasets
Description
Description of dataset
Gtype
Purpose
Purpose of dataset
Description
Gtype
Purpose
Description
Gtype
Purpose
Datasets
The general purpose of Datasets is twofold :
To let you input design parameters via simple forms and menus
2.2.1
2:4
12.0
same serial size, whereas in DIN standards the same class should be used (IPE, IPB, etc.).
In most instances there will only be one profile set and one geometry set for each generic
type of profile.
2.2.2
2:5
12.0
2.2.3
2:6
12.0
2:7
12.0
2:8
12.0
2:9
12.0
2.3
Specifications
The following conventions for structural specifications must be followed to ensure that a
correct specification is built. The application follows strict rules when building these
specifications and reads the specification in a tabulated format. Description should be given
at the correct level and any question of Tanswers must be input for the forms and menus to
be correctly built. The steelwork specifications work in a different way to piping
specifications, where there can be more than one answer. For example, a typical
connection for two beams can either be a bolted or welded connection; hence there can be
two answers to one question.
2:10
12.0
2.3.1
Attribute
Data
Description
SPEC
Description
{ str }
Purpose
STL
spec purpose
Question
GYTP
Matref
{ ref }
Description
{ str }
Tanswer
{ word }
Catref
{ ref }
Detref
{ ref }
SELE
SPCO
2.3.2
2:11
12.0
Type
Attribute
Data
Description
SPEC
Description
{ str }
Question
THK
Purpose
PLT
spec purpose
Tquestions
thickness
Ans
real
min thickness
Maxans
real
max thickness
SPCO
2.3.3
2:12
12.0
Attribute
Data
Description
SPEC
Description
{ str }
Purpose
FITT
spec purpose
Question
TYPE
Matref
{ ref }
Description
{ str }
Tanswer
{ word }
Questions
STYP
Description
{ str }
Tanswer
{ word }
Catref
{ ref }
Detref
{ ref }
SELE
SELE
SPCO
2.3.4
2:13
12.0
Type
Attribute
Data
Description
SPEC
Description
{ str }
Purpose
PFIT
spec purpose
Question
TYPE
Matref
{ ref }
Description
{ str }
Question
STYP
Tanswer
{ word }
Description
{ str }
Tanswer
{ word }
Catref
{ ref }
Detref
{ ref }
SELE
SELE
SPCO
2.3.5
2:14
12.0
Attribute
Data
Description
SPEC
Description
{ str }
Purpose
JOIN
spec purpose
Question
OTYP
Matref
{ ref }
Description
{ str }
Tanswer
{ word }
Question
ATYP
SELE
SELE
SPCO
2.4
Description
{ str }
Tanswer
{ word }
Question
STYP
Catref
{ ref }
Detref
{ ref }
Materials in DESIGN
For the materials of a structural element (MATR) to be set in DESIGN, you must be able to
see a Properties DB containing the available materials.
To create a Material World, carry out the following steps:
1. In ADMIN, change the module definition for PARAGON so that it has Read/Write
access to the Properties DB, thus:
$m/%PDMSUI%/DES/DATA/MLOADPROP
By default, the DENSITY.DAT data in the PDMSDFLTS directory will be loaded into the
first Material World found. Where elements already exist, the macro will modify them to
the values contained in the file.
2:15
12.0
If new material densities are required to be added to the system, DENSITY.DAT can be
modified to include your new materials. The format of the file is as follows:
# NAME
\Description
\Density kg/cu m
AL-CAST
\Aluminium, cast
\2560
Al-WROUGHT
\Aluminium, wrought
\2700
DURALUMIN
\Aluminium, Duralumin
\2790
.
.
.
The hash character ( # ) signifies a comment line: any line beginning with it will be ignored.
Note: All densities are in kg/cu m.
To load the new/modified materials into the system, follow step 4 above. If you moved the
file to some other directory, run the macro by passing the full pathname of the file, thus:
$m/%PDMSUI%/DES/DATA/MLOADPROP <pathname>
2:16
12.0
3.1
Introduction
3.1.1
3:1
12.0
P-Point
Connection Types:
NONE
No connection
WELD
Welded connection
FPIN
Female pin
MPIN
Male pin
BOLT
Bolted connection
RHOL
Right-hand-threaded hole
RROD
Right-hand-threaded rod
LHOL
Left-hand-threaded hole
LROD
Left-hand-threaded rod
CLAM
Clamped connection
HOLE
FSWA
MSWA
Material Texts
The supplied catalogue uses the XTEX attribute of HMTE elements to store material data
Detail Texts
The supplied catalogue uses the RTEX attribute of HDTE elements to store long
descriptions of components for drawings, etc.; the STEX attribute to store concise ordering
codes for MTO, etc.; and the TTEX attribute to store details of additional items which form
part of the component but which need to be ordered separately.
Datasets
The Hangers & Supports application makes great use of the catalogue Datasets. The
following rules apply to their use.
For Datakeys which tell the appware to set certain Design Parameters:
The PPROP attribute must be set to an expression which gives the value of the design
parameter; for example, (ATTRIB DESPARA[1]).
The NUMB attribute must be set to the number of the relevant design parameter.
3:2
12.0
The following Datakeys are reserved for use by the application and have the special
meaning shown:
POD
SWID
FLTH
CRAD
RINA
RINB
VSLO
VSEX
DATA
A special case where the design parameter is not set automatically, but
rather prompts the user to enter the data.
.(* These values are calculated from the Rod take-out values of the Prev/Next components
and represent the distance between the P1/P2 points and the actual ends of the
component.)
Datakeys which give information either to DESIGN appware for sizing purposes or to ADP
(automatic drawing production) appware for drawing data etc. are usually set to component
parameters or hard data. The PURP attribute is set to PARA to indicate that, while the
information is used by the DESIGN appware, it is not required for ADP or MTO:
RTVA
RTVB
THLA
Thread length at P1
THLB
Thread length at P2
VSPR
MNLO
DHEI
(# These values represent the distances from P1/P2 that attached rods should extend in the
fitted position.)
Other Datakeys may be defined as a means of forcing an ADP application to output
database information on drawings and MTO lists. The PURP attribute of these Datakeys
should be set to DATA. The following settings of this type are used in the supplied
catalogue:
OLEN
HEIG
Height
DIMA
3:3
12.0
Naming Conventions
A naming convention for catalogue components has been developed following the
conventions of the ISOCAT style in use by AVEVA and a number of customers for many
years. This convention is detailed later in this section.
3.2
Hanger Specifications
In order for the CHOOSE command to function correctly, the first question in the hanger
specification must be PBOR0.
The sample specification supplied uses the more descriptive TANS instead of the usual
ANS, and this is recommended to make the configuration macro code more readable.
Because, by default, the system uses the CHOOSE command, it is safe to assume that
some questions will be left unanswered at design time. The specification should be
constructed taking this into consideration. For ease of use, the selectors STYP, TTYP and
UTYP have been used, in that order, where multiple levels of selector are required.
It is important to set the DESC, PURP and :VISI attributes of the hanger specification.
PURP and :VISI should be set to HANG and True, respectively.
Any Hangers & Supports specifications should reside in a SPWL with its PURP attribute set
to HSUP.
3.3
3:4
12.0
3:5
12.0
3:6
12.0
3:7
12.0
3:8
12.0
3:9
12.0
3:10
12.0
3:11
12.0
3:12
12.0
3:13
12.0
3:14
12.0
3:15
12.0
3:16
12.0
3:17
12.0
3:18
12.0
3:19
12.0
3:20
12.0
3:21
12.0
3:22
12.0
4:1
12.0
4:2
12.0
5.1
5:1
12.0
5:2
12.0
5:3
12.0
5:4
12.0
5:5
12.0
5:6
12.0
5:7
12.0
5:8
12.0
5:9
12.0
5:10
12.0
5:11
12.0
5:12
12.0
5:13
12.0
5:14
12.0
5:15
12.0
5:16
12.0
5:17
12.0
5:18
12.0
5.2
5.2.1
Configurations
The Hangers & Supports application makes use of catalogue information which describes
both support template and hanger configurations. This data is stored in catalogue elements
and is accessed by means of a specification. Configurations are thus similar to a
Specification Reference (SPREF) and both the Subframe (SBFR) and Hanger (HANG)
elements have :CONFIG UDAs. The referenced SPCO points, via an ACOM and a GMSE,
to a CATE which actually holds all the configuration data.
5.2.2
Hanger Configurations
Hanger Configurations store the following data:
5:19
12.0
PURP
Set to DATA
GTYP
:HCONN
:TCONN
:DESINFO
:DRAINFO
:MAXLEN
:MINLEN
:PSLOPE
:ASLOPE
:PARHANG
Members
The configuration CATE may own any number of TEXT elements which are used to
describe the components used in the hanger. Each component has a TEXT element placed
in the correct order in the members list; the description is stored in the STEX attribute.
Hanger Build Macros
Every hanger configuration has an associated build macro which is situated in the DES/
SUPP applicationware directory. The macros have the form MHB-{suffix} (see CATE GTYP
above). These macros are PML-based, but make use of a specially designed toolkit which
lets you create a build macro for almost any hanger configuration.
5:20
12.0
It is recommended that you follow an example, of which there are many supplied with the
product, to aid your understanding of this section.
The toolkit subroutines which you can call in your build macros are as follows:
XHBPCLA
XHBFITT
XHBHELE
XHBHORI
XHBSCLA
XHBSTART
XHBSTART
XHBSPAC
XHBHCLN
Apart from these, the amount of PML writing you need to do is minimal, although some
knowledge of PML and macro writing would be useful. In some cases, the order of element
creation means that some additional work needs to be done by the build macro. For an
example of this, see the supplied macro MHB-CBWA.
Each of these subroutines is called by using the syntax
CALLSUP
<subroutine name>
<args>
and requires arguments which enable it to perform its task correctly. Each argument should
be enclosed in the delimiters $< ... $> if there is any whitespace. Each macro may also
require that a global variable is set, or may in turn set a global variable. For descriptions of
RTO values, see the section which details hanger catalogues and datasets.
XHBPCLA:
Arguments
1
PCLA STYP(s)
For tube ATTAs, single value (quoted if using TANS)
For component ATTAs, space or / separated list for TEE, ELBO, BEND components
(NONE if not applicable)
COMP or TUBE
Hanger Direction p-point (for TUBE). This p-point will be orientated to point in the
direction of the hanger Rotation Direction p-point (for COMP). This p-point will be
orientated to point in the perpendicular direction of BENDs or ELBOs.
Angle flag. True if the component has a DDANG which needs to be deduced.
Connection/Fitting instructions:
5:21
12.0
PCLA STYP(s)
ATTA: Sets PCLA height to distance P0 to P3 of ATTA
FITH: Sets PCLA height to distance HH to HT
FITP: Sets PCLA height to half pipe OD
CONN: Does not set PCLA height
Globals used
None
Globals set
!!CDSNHB.RTOVAL1
!!CDSNHB.RTOVAL2
XHBFITT:
Arguments
None
Globals used
None
Globals set
None
XHBHELE:
Arguments
1
HELE STYP
HELE GTYP. Unique WORD attribute used to identify HELE for later operations
GTYP of element which will be at the arrive end of the new HELE
GTYP of element which will be at the leave end of the new HELE
5:22
12.0
HELE STYP
N.B. If argument 4 identifies an element which occurs later in the hanger's
members list than argument 5, this will cause the new element to be created in
backwards mode. This can be very useful in some circumstances
Connection/Fitting instructions:
FIT: Fit the HELE into the available space (by setting HEIGHT attribute)
CONN: Connect the HELE to the previous element (or HH/HT)
DIST: Set the HELE at a specified distance from the previous element
PROP: Set the HELE at a specified proportional distance between the previous and
the next elements
DIST and PROP both have the format <keyword> <value> <p-point> (the p-point
designation is optional and defaults to P0)
Angle flag. True if the component has a DDANG which needs to be deduced.
Globals used
!!CDSNHB.RINS1
!!CDSNHB.RINS2
Globals set
!!CDSNHB.RTOVAL1
!!CDSNHB.RTOVAL2
5:23
12.0
XHBHORI:
Arguments:
1
HELE GTYP
Connection/Fitting instructions
FIT: Fit the HELE into the available space (by setting HEIGHT attribute)
CONN: Connect the HELE to the previous element (or HH/HT)
DIST: Set the HELE at a specified distance from the previous element
PROP: Set the HELE at a specified proportional distance between the previous
and the next elements
DIST and PROP both have the format <value> {<p-point>}
The default p-point is P0.
Globals used:
!!CDSNHB.RINS1
!!CDSNHB.RINS2
Globals set:
!!CDSNHB.RTOVAL1
!!CDSNHB.RTOVAL2
XHBSCLA:
Arguments
1
SCLA STYP
Default orientation:
TUBE: Pipe flow direction
5:24
12.0
SCLA STYP
STEEL: Steel direction (can be SCTN Y or X direction depending on hanger Tail
connection type)
Globals used
None
Globals set
!!CDSNHB.RTOVAL1
!!CDSNHB.RTOVAL2
XHBHCLN:
Arguments
1
Minimum/Maximum distance:
Explicit value
Parameter number (e.g. PARAM 1)
Globals used
None
Globals set
None
5:25
12.0
XHBSPAC
Arguments:
1
Globals used
None
Globals set
None
5.2.3
Template Configurations which have a fixed length and can be used to determine the
positions of support steel when creating a steelwork template
Tube Configurations which have variable length which can be applied to tube type
hangers.
Component Configurations which have variable or fixed length which can be applied
to component type hangers.
Support Configurations
Support configurations store the following data:
5:26
12.0
FUNC
PURP
DATA
GTYP
Joint type:
BUTT - Butt welded to joint owner
BACK - Back to back jointing
:DESINFO
DRAINFO
Members
The configuration CATE may own any number of TEXT elements which are used to
describe the support template. The TEXT element's role is determined by the setting of the
:DESCR UDA and the data is stored in the STEX attribute.
The following TEXT elements are mandatory and are used to determine the numbers of
support members expected before and after configuration:
DESCR = #ST
STEX = <value>
where <value> represents the number of stanchions expected in the final
configuration and must be a non-negative integer or the letter N to indicate
any number, but it can have the following modifiers:
> There must be greater than zero before configuration
= The number before configuration must be the same as the number specified
DESCR = #XM
STEX = <value>
where <value> represents the number of cross-members expected in the final
configuration and must be a non-negative integer or the letter N to indicate
any number, but it can have the following modifiers:
> There must be greater than zero before configuration
= The number before configuration must be the same as the number specified
5:27
12.0
Each type of member enumerated above must be described by another TEXT element:
DESCR = <member type>_<member number>
where <member type> is XM or ST and <member number> is the number of
the stanchion/cross-member being described
STEX = <start connection info> <end connection info>
where <start connection info> takes the form
S:<member at start>/<joint position>/<Attached or Owner>:<clearance
code>
and <end connection info> takes the form
E:<member at end>/<joint position>/<joint ownership>:<clearance code>
<member at start> is a support member identifier of the start connection
<member at end> is a support member identifier of the end connection
Member identifiers can have the following forms:
<value>
<
>
Attached
Owner
<clearance code> refers to the minimum clearance between the nearest pipe
and the respective end as defined in the clearance data table:
A
Free end
5:28
12.0
5.2.4
5.2.5
Data Tables
Data tables use the existing PDMS specification hierarchy as a way to extract crossreferenced 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
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
5:29
12.0
DESC
QUES
SMAT
QUES
PMAT
QUES
HTYP
SPCO level
ANS
TANS
COMM
**
application
defaults
from
the
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.
A2
Perpendicular joint
5:30
12.0
A1
C1
Angled end (braced free end - only really used in the Braced Cantilever type
configuration) before profiles set
C2
PBOR
:VISI
false
PURP
HCLR
DESC
<clearance code>
QUES
HTYP
SPCO Level
TANS
COMM
Code corresponds to the Hanger Build Macro suffix and the GTYP of the
configuration CATE
5:31
12.0
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 pseudoattribute 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.
5:32
12.0
Index
Numerics
DIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
F
Fittings catalogue . . . . . . . . . . . . . . . . . . 2-5
A
Administrative Elements . . . . . . . . . 2-1, 2-2
Attconn . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Automatic Drawing Production . . . . . . . . 3-3
H
Hanger Build Macros . . . . . . . . . . . . . .
Hanger Clearance Table . . . . . . . . . . .
Hanger Length Table . . . . . . . . . . . . . .
Hash character . . . . . . . . . . . . . . . . . . .
5-20
5-30
5-29
2-16
Bores . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
British Standards . . . . . . . . . . . . . . . . . . . 2-4
BS 5950 . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
D
Datakeys . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Datasets . . . . . . . . . . . . . . . . . . . . . 2-4, 3-2
Densities . . . . . . . . . . . . . . . . . . . . . . . . 2-16
DENSITY.DAT . . . . . . . . . . . . . . 2-15, 2-16
Detail Texts . . . . . . . . . . . . . . . . . . . . . . . 3-2
ISOCAT . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
L
LSRO . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
M
Material codes . . . . . . . . . . . . . . . . . . . 5-30
Material Texts . . . . . . . . . . . . . . . . . . . . . 3-2
Material World . . . . . . . . . . . . . . . . . . . 2-15
MATR . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Maximum Unsupported Span Table . . . 5-31
Member identifiers . . . . . . . . . . . . . . . . 5-28
Members . . . . . . . . . . . . . . . . . . .5-20, 5-27
Index page 1
12.0
N
Naming Conventions . . . . . . . . . . . . . . . . 3-4
Negative Geometry Sets . . . . . . . . . . . . . 2-4
O
Ownconn . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
P
PBOR . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Pipe Clamps . . . . . . . . . . . . . . . . . . . . . . 3-1
Point sets . . . . . . . . . . . . . . . . . . . . 2-3, 2-4
Profile catalogue . . . . . . . . . . . . . . . . . . . 2-4
Properties DB . . . . . . . . . . . . . . . . . . . . 2-15
R
Rod take-out values . . . . . . . . . . . . . . . . 3-3
S
Sample Catalogue . . . . . . . . . . . . . . . . . 3-1
Specification Reference . . . . . . . . . . . . 5-19
Steel Clamps . . . . . . . . . . . . . . . . . . . . . . 3-1
Structural Category . . . . . . . . . . . . . . . . . 2-2
Structural Section . . . . . . . . . . . . . . . . . . 2-2
Subframe . . . . . . . . . . . . . . . . . . . . . . . 5-19
Subroutines . . . . . . . . . . . . . . . . . . . . . . 5-21
Support Configurations . . . . . . . . . . . . . 5-26
T
Tabulated format . . . . . . . . . . . . . . . . . . 2-10
TANS . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Tanswers . . . . . . . . . . . . . . . . . . . . . . . 2-10
Template Configurations . . . . . . . . . . . . 5-26
Template-type configurations . . . . . . . . 5-29
Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Tube Configurations . . . . . . . . . . . . . . . 5-26
U
User-defined configurations . . . . . . . . . 5-29
V
Variable Height Components . . . . . . . . . 3-1
Index page 2
12.0