Sets the rules that are used to calculate both the X and Y sizes of the compensating plate.
The default values/settings indicated on the window are those that exist when the Supports application is first installed.
Click Reset to revert the Supports Compensation Sizes window to the default values/settings.
Changes made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must be performed.
Click Cancel to close the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.

The Supports Compensation Sizes window contains two tabs for specifying separate rules to calculate the X and Y sizes of the compensating plate.
The General Rule is used when a rule for a given support type is not defined.
The Default Value field defines the default X and Y sizes of the compensating plate.
Rules can be created for specific support types, input the support codes into the support code field, separated by a space. An asterisk can be used to identify all support types. If two rules are defined for the same support type, the first rule in the list for that support type is used and the second is ignored.
A rule must always be a Programmable Macro Language (PML) expression that returns a REAL value upon evaluation. If the expression contains references to attributes or properties, the expression is evaluated against the ANCI of the support. Therefore it can contain any attribute or property which is available on the ANCI element.
To access the width of the General Section (GENSEC) supporting the ANCI, the syntax 'VVAL( !WIDTH)' can be included into the expression. The profile width in this context is the width of the GENSEC face below the ANCI depending on the profile rotation and may not necessarily correspond to the catalog property WIDT.
If the evaluation of the rule expression fails, then the explicitly set default value is used instead.
To add a new rule to the list of available rules, click Add Entry to display the Add Entry window.

You can populate the Support Codes and X-Size Rule or Y-Size Rule fields with the relevant rule values.
Click OK to add the rule to the list of available rules or Cancel to discard any changes and close the Add Entry window.
Click Remove Entry to delete the currently selected rule.

Reset
Supports Compensation Sizes
Apply
Save Work
Cancel
Supports Compensation Sizes
General Rule
Default Value
Add Entry
Add Entry
Support Codes
X-Size Rule
Y-Size Rule
OK
Cancel
Add Entry
Remove Entry


Sets the available materials for a compensating plate.
The default values/settings indicated on the window are those that exist when the supports application is first installed.
Changes made are only applied to the database when Apply is clicked. To keep the changes the Save Work operation must be performed.
Click Cancel to close the window. If changes have been made, but not applied, a window displays asking if the changes are to be applied before exiting.

The Supports Compensation Materials window contains two lists, the first lists the different possible choices of materials and the second lists the available materials.
To set a material choice, select the appropriate choice from the list of available choices and then select the material for that choice from the list of available materials.
Duplicate choices are omitted from the material selection drop-down list in Model.
The default choice is the material that is initially set when a compensation is created. It is not possible to remove the default choice.
The available materials that can be assigned to a choice are populated from the MDS/PROP database and only solid materials are available for selection.

Apply
Save Work
Cancel
Supports Compensation Materials


Sets the current MDU catalog. Multiple copies of the MDU catalog can be created to support the use of different catalogs in a single session.
Select a catalog from the MDU drop-down list.

Copy MDU Catalog
Copies an existing MDU Catalog to support the use of multiple catalogs in a single session.

From
Select from the drop-down list to define the source MDU catalog to be copied.
To
Select from the drop-down list to define the target location of the created MDU catalog.
Description
Input a name for the created MDU catalog.
Messages
Describes what actions the application is carrying out.
Click Cancel to discard any changes and close the MDU Catalog Copy window.
Click Apply to copy the MDU catalog, a Confirm window displays informing you that the operation may take considerable time to complete.

Click Yes to continue with the copy process.
Support Configuration File
By default, support configuration files are read from the default path which is the installation directory. The default path can be overwritten by setting the environment variable MDS_SUPPORT_CONFIG_LOCATION.
The standard support configuration file is named SupportConfigurationFile.xml. Multiple support configuration files are supported.
New support catalogs must follow a defined folder path:
A folder named userSupportConfiguration must be added to the %MDS_SUPPORT_CONFIG_LOCATION% path.
All configuration information, for example, image files, the support configuration xml file and any other files specific to that support configuration must be stored in a unique configuration specific folder. This folder uses the naming convention Configuration-<MDU DB CODE>.
Plot files must be stored in the plots folder which is located in the configuration specific folder.
Specific naming conventions must be used, if the internally referenced MDU DB CODE is A, the naming convention is:
Configuration specific folder
Configuration-A
Support configuration file
SupportConfiguration-A.xml
Folder for configuration specific plot files
plots
Image names & plot file names
Same naming convention as existing support standards.
Configuration specific folder
Configuration-A
Support configuration file
SupportConfiguration-A.xml
Folder for configuration specific plot files
plots
Image names & plot file names
Same naming convention as existing support standards.
For example, if the %MDS_SUPPORT_CONFIG_LOCATION% is configured to a folder other than the installation directory, the default configuration xml file (SupportConfiguration.xml) must be located alongside the userSupportConfiguration folder. In the example, the %MDS_SUPPORT_CONFIG_LOCATION% folder is D:\localSupportConfigurations\.

The userSupportConfiguration folder contains a folder for each specific configuration.

The configuration specific folder contains the plots folder, image files and the support configuration file.

The plots folder contains the plot files.

A new support catalog that uses the key letter K may require a separate support configuration file, named SupportConfigurationFile-K.xml. The new support configuration file is stored in the configuration specific folder.

The DimensionsControlConfiguration id value, in the support configuration file, can be set to the defined key letter. For example:

Mapping and representation for a specific support type can be defined. For example, AT510 and AT03.
For mapping name "AT510", the image id is "at510". The application searches for the image named at510.png. The image is stored in the same path as the support configuration file.
For mapping name "AT03", the image id is "at03". An image file is not found, the application uses the support standard image.
If an external image or a support standard image is not found, a blank image displays.
<DimensionControlConfiguration id="K">
Note:
The Multiple Support Catalogs functionality is only available when all the databases, for example, MDS/CATA(DB No.7320), MDS/MDSAPPDEFAULTS(DB No.7351) and MDU/CATA(DB No.7355) are part of the selected MDB.
Note:
You are prompted to restart the session for the modifications to take effect.

Note
:
MDU
Copy MDU Catalog
From
To
Description
Messages
Cancel
MDU Catalog Copy
Apply
Confirm
Yes
Note
:
Support Configuration File
userSupportConfiguration
<DimensionControlConfiguration id="K">


The Supports application allows you to create a set of ancillary standards with their own geometry. Configuration of standards dimensionally is covered in Ancillary Data.
The user defined ancillary standards comprise a number of support types. The table displays the user defined ancillary types that have been created that can be configured geometrically:

From
To

AT
Ancillary
AT500
AT700
201
LT
Lug
LT500
LT700
201
BT
U-Bolt
BT500
BT700
201
AN
Anchor for shoes
AN500
AN569
70
AN
Anchor for pipes
AN570
AN639
70
AN
Anchor for trunnions
AN640
GT700
61
GT
Guide for shoes
GT500
GT569
70
GT
Guide for pipes
GT570
GT639
70
GT
Guide for trunnions
GT640
GT700
61
ST
Stops for shoes
ST500
ST569
70
ST
Stops for pipes
ST570
ST639
70
ST
Stops for trunnions
ST640
ST700
61
AC
Ancillary Components for Trunnions
AC500
AC599
100
AC
Plate Component for Trunnions
AC600
AC700
101
CA
Cable Tray Ancillaries
CA500
CA700
201
The ability to create the user defined ancillary types is achieved by supports being configured to use a blank set of ancillaries, so that users can complete their own geometry. A user project called MDU is created; a hierarchy /MDU prefix is used instead of the /MDS prefix where applicable. The example displays how this is implemented into a supports project environment.

The MDU project has the geometry and point sets pre-created and linked into the Multi Discipline Supports (MDS) catalog and specification. The geometry sets are empty and the point sets have the minimum p-point requirements. You can then create the geometry within the MDU project and set up any design parameters required for the component. The MDU project only stores geometry, point and data sets for the types and ranges detailed earlier.

Ancillary Data
Ancillary Data
From
To


The geometry sets are created in project MDU. The examples display what is added and details any properties that are used. You can add geometry using the properties if required and add additional properties as necessary.
Simple Box Representation

The box is set to a length of 10, and uses the pipe Outside Diameter (OD) as the X and Y length.

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.
No user editable design parameters have been defined.
Anchor for Shoes
Simple Anchor Representation

These user standards ask for a pipe shoe to be identified so it can read the shoe parameters Shoe Height and Flange Width in order to size the anchor. It then asks for a section or box to be identified to read the anchor width across the section of box.
The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1, 100, 102 and 133.2. All other design parameters are set to 0 (zero), as indicated in the Properties window.
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.
Anchor for Pipes
Simple Box Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.
No user editable design parameters have been defined.
Guide for Shoes
Simple Guide Representation

These user standards ask for a pipe shoe to be identified so it can read the shoe parameters Shoe Height and Flange Width in order to size the guide.
The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1, 100 and 102. All other design parameters are set to 0 (zero), as indicated in the Properties window.
Design parameters 1, 2, 3 and 4 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.
Guide for Pipes
Simple Guide Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1 and 0. All other design parameters are set to 0 (zero), as indicated in the Properties window.
Stop for Shoes
Simple Stop Representation

These user standards ask for a pipe shoe to be identified so it can read the shoe parameters Shoe Height and Flange Width in order to size the Anchor. It then asks for a section or box to be identified to read the anchor width across the section of box.
The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1, 100 102 and 133.2. All other design parameters are set to 0 (zero), as indicated in Properties window.
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.
Stop for Pipes
Simple Box Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero) as indicated in the Properties window.
Anchor for Trunnions
Simple Anchor Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset. The Plate Length, Plate Width and Plate Thickness are obtained from the identified Base Plate. All other design parameters are set to 0 (zero) as indicated in the Properties window.
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.
Stop for Trunnions
Simple Stop Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset. The Plate Length, Plate Width and Plate Thickness are obtained from the identified base plate. All other design parameters are set to 0 (zero) as indicated in the Properties window.
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.
Guide for Trunnions
Simple Guide Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset. The Plate Length, Plate Width and Plate Thickness are obtained from the identified base plate. All other design parameters are set to 0 (zero) as indicated in the Properties window.
Design parameters 1, 2 and 3 have been declared as user editable (with an allowable range of 0 to 1000) and default values have been added.
Ancillary Component for Trunnions
Simple Ancillary Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.
No user editable design parameters have been defined.
Plate Component for Trunnions
Simple Plate Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection Type and 25 design parameters have been created. The list displays the parameters that have been preset, for example, to -1. All other design parameters are set to 0 (zero), as indicated in the Properties window.
No user editable design parameters have been defined.
Cable Tray Ancillaries
Simple Cable Tray Ancillary Representation

The three standard catalog parameters have been added, Nominal Bore, Outside Diameter and Connection type and 21 design parameters have been created. The design parameters are set to 0 (zero) as indicated in the Properties window. Cable ancillaries do not include Minimum/Maximum Insulation and Minimum/Maximum Temperature parameters. The Outside Diameter is always set to 0 (zero) for cable tray ancillaries.

Properties
Properties
Properties
Properties
Properties
Properties
Properties
Properties
Properties
Properties
Properties
Properties
Properties


These have been created with the minimum points required. These are:
P-Point
Description
1
Arrive point
2
Leave point
3
Bottom of Pipe (BOP) -5mm. For example, bottom of the ancillary geometry -5mm
9
BOP (Including geometry if required). For example, bottom of the ancillary geometry
10
Left of pipe
11
Right of pipe
12
BOP
P-Point
Description
1
Arrive point
2
Leave point
3
Bottom of Pipe (BOP) -5mm. For example, bottom of the ancillary geometry -5mm
9
BOP (Including geometry if required). For example, bottom of the ancillary geometry
10
Left of pipe
11
Right of pipe
12
BOP
The diagram displays the position and directions of the p-points, P1 and P2 are arriving and leave points along the centerline of the pipe.

Note:
The default p-points provided cannot be deleted or modified, but additional p-points can be created if required.

Note
:


These have been created with the minimum number of elements required. These are:
/Prefix-DESC
Support standard
DESC
'AT500'
/Prefix-RNAM
Standard Replacement Name
RNAM
(BEF (AFT (ATTRIB PPRO of DATA /MDS/ATTA/DEFAULTS/AT500/GEN/CCOD , ‘(‘’’) , ‘’’ )’ ) )
/Prefix-PA1
Nominal Bore
NB
PARA 1
/Prefix-PA2
Outside Diameter
OD
PARA 2
/Prefix-PA3
Connection Type
CONN
PARA 3
/Prefix-WEIG
Component Weight
WEIG
(ATTRIB DENS of 1 OF 1 of :MDSMatRef * ATTRIB NVOL / 1000 / 1000 / 1000 * VVAL !!MDSWEIUNIT)
/Prefix-MATR
Component Material
MATR
(ATTRIB DESC of :MDSMatRef)
/Prefix-CODE
Support Code
CODE
(TRIM ( DIST ( NOMBORE ( false , ATTRIB CPAR[1 ] ) , false , false , true , 4 , false ) ) + '-' + ATTRIB PROPRNAM)
/Prefix-CDES
MDS Configurable
Description
CDES
(BEF (AFT (ATTRIB PPRO of DATA /MDS/ATTA/DEFAULTS/AT500/GEN/DESC , ‘( ‘’’ ) ‘’’ ) ) )
/Prefix-DP1
Design Parameter 1
Unset
DESP[1]
Where /Prefix is /Standard-DATA-, for example, /AT500-DATA-DESC and the standard used is AT500
You can add/modify the data set as necessary.


The catalog items for the user defined ancillaries have been created in the ranges detailed within the MDU project. The MDU project contains all the catalog elements, For example, SCOM, 3D Geomset Elemen (GMSE), Pointset Element (PTSE), Data Set (DTSE) and SDTE, where the user modifies the GMSE to suit their requirements. The specification components for ALL the user defined ancillaries are in the /MDS specification in the Multi Discipline Supports (MDS) project, which must not be modified by users.

From
To
From
To
AT
Ancillary
AT01
AT115
AT500
AT700
LT
Lug
LT01
LT16
LT500
LT700
BT
U-Bolt
BT01
BT11
BT500
BT700
AN
Anchor
AN01
AN18
AN500
AN700
GT
Guide
GT01
GT50
GT500
GT700
ST
Stop
ST01
ST33
ST500
ST700
The MDU project catalog hierarchy has been created for a size range of 8mm (1/4") to 1200mm (48") in the bore sizes that display:
8
1/4
13.7
14
15
3/8
21.3
21
20
1/2
26.7
26
25
1
33.4
33
32
1.1/4
42.2
42
40
1.1/2
48.3
48
50
2
60.3
61
65
2.1/2
73
73
80
3
88.9
89
100
4
114.3
115
125
5
141.3
141
150
6
168.3
169
200
8
219.1
220
250
10
273
273
300
12
323.8
324
350
14
355.6
358
400
16
406.4
407
450
18
457
457
500
20
508
508
550
22
559
559
600
24
610
610
650
26
660
660
700
28
711
711
750
30
762
762
800
32
813
813
850
34
864
864
900
36
914
914
950
38
965
965
1000
40
1016
1016
1050
42
1067
1067
1100
44
1118
1118
1150
46
1168
1168
1200
48
1219
1219

MDS
MDS


You can use the standard pipework application in AVEVA Catalog to modify the required elements within the MDU catalog database. For example,
MDU/CATA <dbnum7355,dbfile%MDU000/mdu7355>.
Within the MDU project, the following should not be deleted or modified (including name change):
CATREF
(Catalog Reference)
PTREF
(P-Point Set Reference)
(refer to the Note for further information)
GMREF
(Geometry Set Reference)
(refer to the Note for further information)
DTREF
(Data Set Reference)
(refer to the Note for further information)

CATREF
(Catalog Reference)

PTREF
(P-Point Set Reference)
(refer to the Note for further information)

GMREF
(Geometry Set Reference)
(refer to the Note for further information)

DTREF
(Data Set Reference)
(refer to the Note for further information)
Note:
Although the MDU default p-points provided cannot be deleted or modified, additional p-points can be created. Also, geometry can be added to the geometry sets, and additional properties included as necessary

Note
:


Various Support Standards are available.


The standards are available in the Supports application, but are automatically created when creating an ancillary standard (refer to Ancillaries for further information).
The standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.
AC01*
XAC01
Forged eye rod.
AC02*
XAC02
Fully threaded rod.
AC03*
XAC03
Turnbuckle.
AC04*
XAC04
Clevis.
AC05*
XAC05
Weldless eye nut (bow).
AC06*
XAC06
Beam welding attachment.
AC07*
XAC07
Welding lug.
AC08*
XAC08
Clevis plate.
AC09*
XAC09
Spherical washer.
AC10
XAC10
Pipe clamp (light).
AC11*
XAC11
Pipe clamp (heavy).
AC12*
XAC12
Pipe clamp for insulated pipe (light).
AC13*
XAC13
Pipe clamp for insulated pipe (heavy).
AC14*
XAC14
Pipe clamp for Cu-Ni pipe.
AC15*
XAC15
Pipe clamp for insulated Cu-Ni pipe.
AC16*
XAC16
Riser clamp.
AC17
XAC17
Vessel Support Lug
AC18A
XAC18A
Base Plate
AC18B
XAC18B
Base Plate
AC19A
XAC19A
Bearing Plate
AC19B
XAC19B
Bearing Plate
AC20
XAC20
Collar
AC21
XAC21
Base plate for RTJ Joints
AC22
XAC22
Bolt on base support
AC24
XAC24
Reinforcing Pad
AC25
XAC25
Dummy branch end plate
AC27
XAC27
Break Out Plates with Shim
AC28
XAC28
Strap On Clamp for RTR Pipe
AC29
XAC29
Bolted Clamp Assembly
AC30
XAC30
Adjustable Baseplate
AC31
XAC31
Anchor Bolted Clamp Assembly
AC32
XAC32
Break Out Plates with Shim
AC33
XAC33
End Plate for Rod Hanger Trunnion
AC34
XAC34
Reinforcing Pad
AC35
XAC35
Pipe Clamp
AC36
XAC36
U Strap
AC37
XAC37
Pipe Riser Clamp
AC38
XAC38
Guide Trunnions
AC39
XAC39
Isolation Block Acoustic/General for Trunnion XTT23
AC40
XAC40
General Slide Unit for Trunnion XTT23
AC41
XAC41
Cold Isolation Block for Trunnion XTT23
AC44
XAC44
Clamp for Trunnions for Diam 2" to 24"
AC45
XAC45
Clamp for Dummy Legs for Diam 2" to 24"
AC46
XAC46
LTCS Upper Break Out Plate for Trunnion XTT23
AC47
XAC47
CS Base Plate for Trunnion XTT23
AC48
XAC48
CS Lower Break Out Plate for Trunnion XTT23
AC49
XAC49
Base Plate 1.1/2" to 16"
AC50
XAC50
End Plate 2" to 24"
AC51
XAC51
Support Plate 2" to 24"
AC52
XAC52
Stiffener 2" to 24"
AC53
XAC53
GRE Pipe Clamps for diam 1.1/2" to 40"
AC54
XAC54
CPVC Pipe Clamps for diam 1.1/2" to 12"
AC55
XAC55
4 Bolt Clamp for Trunnions diam 2.1/2" to 24"
AC56
XAC56
Base Plate Circular
AC57
XAC57
Adjustable Trunnion Base Plate 1.1/2" to 24"
AC58
XAC58
Pipe Clamp for Trunnions - DN 20-250
AC59
XAC59
Base Plate for Trunnions - DN 20-250

Ancillaries
Ancillaries


The standards are available in the Supports application user defined anchor standard

The standards are available in the Supports application.
The standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.
Refer to Modify User Defined Ancillary Geometry for further information on user defined anchor standards.
AN01A*
XAN01A
Pedestal Anchor Type A.
AN01B*
XAN01B
Pedestal Anchor Type B.
AN02
XAN02
Pipe Shoe Anchor.
AN03
XAN03
Pipe Shoe Anchor.
AN04
XAN04
Bolted Anchor shoe for Hot insulated pipe or temp transport NPS 2-36.
AN05
XAN05
Temporary restraint NPS 2-20.
AN06
XAN06
Bolt on Shoe w/Directional Anchor Cold (Cryogenic) Service (50/100mm Insu) NPS 3 - 48
AN07A
XAN07
Anchor U Bolt (AB) Black, NPS 2 - 20.
AN07B
XAN07
Anchor U Bolt (AG) Galvanised, NPS 2 - 20.
AN07C
XAN07
Anchor U Bolt (AP) Plastic Coated, NPS 2 - 20.
AN08
XAN08
Pipe Clamp Anchor For RTR Pipe NPS 2-24.
AN09
XAN09
Overstrap Anchor (C.S./Alloy Pipes) NPS 1/2- 20
AN10
XAN10
Directional Anchor NPS 1-36.
AN11
XAN11
Bolt On Anchor For Galvanised Pipe NPS 6-12.
AN12A
XAN12A
Flat Clamp for CS pipes NPS 1.1/2-16.
AN12B
XAN12B
Flat Clamp with Neoprene Sleeve for SS pipes NPS 1.1/2-16.
AN13
XAN13
HALFEN Anchor HCS RADV NPS 1" 6"
AN17
XAN17
Anchor U Bolt for Cupro Nickel Lines, NPS 1/2- 8.
AN18
XAN18
Anchor U Bolt for Carbon Steel Lines, NPS 1/2- 8.
AN19
XAN19
Anchor - DN 15-1400
AN20
XAN20
U-Bolt Anchor
AN21
XAN21
Anchor Low
AN22
XAN22
Anchor Low
AN23
XAN23
Anchor Low 2-Sided
AN24
XAN24
Anchor Low 2-Sided
AN25
XAN25
Anchor High
AN26
XAN26
Anchor High 2-Sided
AN27
XAN27
Anchor High
AN28
XAN28
Anchor High 2-Sided
AN29
XAN29
Anchor High
AN30
XAN30
Anchor High 2-Sided
AN31
XAN31
Anchor Extra High
AN32
XAN32
Anchor Extra High 2-Sided
AN33
XAN33
Anchor Extra High
AN34
XAN34
Anchor Extra High 2-Sided
AN35
XAN35
Anchor Extra High
AN36
XAN36
Anchor Extra High 2-sided
AN37
XAN37
U-Bolt Guide
AN38
XAN38
Anchor Low
AN39
XAN39
Anchor Low 2-Sided

Modify User Defined Ancillary Geometry
Modify User Defined Ancillary Geometry


The standards are available in the Supports application User Defined Ancillary Standards.

The standards are available in the Supports application.
The standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.
Refer to Modify User Defined Ancillary Geometry for further information on User Defined Ancillary Standards.
PIPE-REST
XRT01
Pipe Rest
PIPE-REST-INLINE
XRT02
Pipe Rest Inline for Trunnions
AT01
XAT001
Pipe shoe for N.B. 3/4" to 20"
AT02
XAT002
Pipe shoe for N.B. 24" to 48"
AT03
XAT003
Clamp on pipe shoe for N.B. 3/4" to 20"
AT04
XAT004
Clamp on pipe shoe for N.B. for pipe Cu-Ni 2" to 20"
AT05
XAT005
Reinforcing plate (cut from pipe)
AT06
XAT006
Clamp on pipe shoe for stainless or galvanised pipe
AT07
XAT007
Pipe shoe with reinforcing plate for N.B. 3/4" to 20"
AT08
XAT008
Pipe shoe with reinforcing plate for N.B. 24" to 48"
AT09
XAT009
Reinforcing plate (cut from plate)
AT10A*
XAT10A
Pedestal support for elbows (type A)
AT10B*
XAT10B
Pedestal support for tube (type B)
AT11A*
XAT11A
Adjustable pedestal support for elbows (type A)
AT11B*
XAT11B
Adjustable pedestal support for tube (type B)
AT12
XAT012
Shoe for C.S. Pipe. Hot Service (63mm Maximum Insu.) NPS 2"-36"
AT13
XAT013
Shoe for C.S. Pipe. Hot Service (75mm/100mm Insu.) NPS 2"-36"
AT14
XAT014
Shoe for Low Temp C.S. Pipe. Inter. Service to -46 c (75mm/100mm Insu.) NPS 2"-36"
AT15
XAT015
Shoe for Low Temp C.S. Pipe. Inter. Service to -46 c (63mm Maximum Insu.) NPS 2"-36"
AT16
XAT016
Bolt on Shoe, Heat Insulated & Uninsulated C.S. NPS 2"-32"
AT17
XAT017
Shoe for RTR Pipe, NPS 2-14
AT18
XAT018
Shoe for Low Temp S.S. Pipe. Inter. Service <-46 c (63mm Maximum Insu.) NPS 2"-36"
AT19
XAT019
Shoe for Low Temp S.S. Pipe. Inter. Service <-46 c (75mm/100mm Insu.) NPS 2"-36"
AT20
XAT020
Clamp on shoe for Cu-Ni NPS 2 - 24
AT21
XAT021
Pipe Guide for reciprocating Compressor Pipe 2" to 24"
AT22
XAT022
Temporary Transport Anchor for NPS 6-36 Uninsulated C.S.
AT23
XAT023
Welded Cradle Support for Uninsulated Pipe or Shoe, NPS 2 1/2 - 36
AT24
XAT024
Cradle for RTR Pipe NPS 2 - 4
AT25
XAT025
Bolt On Shoe Cold (Cryogenic) Service (25mm/100mm Insu.) NPS 3" - 48"
AT26
XAT026
Cradle for Cold Service (30 - 150mm Insulation), NPS 1/2 - 2.
AT27
XAT027
Hanger Clamp for RTR Pipe NPS 2 - 24.
AT28
XAT028
U Bolt Guide for RTR pipe NPS 2 - 24.
AT29A
XAT029A
Reinforcing Pad for straight pipe for C.S. pipe.
AT29B
XAT029B
Reinforcing Pad for elbow for C.S. pipe.
AT30
XAT030
Special Shim Assembly for Sloping Lines NPS 2-36
AT31A
XAT031A
Reinforcing Pad for straight pipe for High Alloy/SST pipe.
AT31B
XAT031B
Reinforcing Pad for elbow for High Alloy/SST pipe.
AT32
XAT032
Pipe Strap (Lined) for Galv. and S.S Lines NPS 1.1/2 - 8
AT33A
XAT033A
Trunnion Isolation Pad(Type A - 140mm x 140mm) -Acoustic/General - NPS 1/2 - 24
AT33B
XAT033B
Trunnion Isolation Pad(Type B - 140mm x 250mm) - Acoustic/General - NPS 1/2 - 24
AT33C
XAT033C
Trunnion Isolation Pad(Type C - 140mm x 300mm) - Acoustic/General - NPS 1/2 - 24
AT33D
XAT033D
Trunnion Isolation Pad(Type D - 200mm x 200mm) - Acoustic/General - NPS 1/2 - 24
AT33E
XAT033E
Trunnion Isolation Pad(Type E - 250mm x 250mm) - Acoustic/General - NPS 1/2 - 24
AT33F
XAT033F
Trunnion Isolation Pad(Type F - Variable Size) - Acoustic/General - NPS 1/2 - 24
AT34A
XAT034A
Trunnion Slide Unit(Type A - 140mm x 140mm) - General - NPS 1/2 - 24
AT34B
XAT034B
Trunnion Slide Unit(Type B - 140mm x 250mm) - General - NPS 1/2 - 24
AT34C
XAT034C
Trunnion Slide Unit(Type C - 140mm x 300mm) - General - NPS 1/2 - 24
AT34D
XAT034D
Trunnion Slide Unit(Type D - 200mm x 200mm) - General - NPS 1/2 -24
AT34E
XAT034E
Trunnion Slide Unit(Type E - 250mm x 250mm) - General - NPS 1/2 - 24
AT34F
XAT034F
Trunnion Slide Unit(Type F - Variable Size) - General - NPS 1/2 - 24
AT35
XAT035
Cold Isolation Block with CS Cage for Trunnion XTT23
AT36
XAT036
Tico Isolation Wrap - Temp. -40 to +100 deg.C (C.S./Alloy/Cu-Ni Pipes) - NPS 1/2 - 24.
AT37
XAT037
Tico Isolation Wrap - Temp. +101 to +150 deg.C (C.S./Alloy/Cu-Ni Pipes) - NPS 1/2 - 24.
AT38
XAT038
Bonded Neoprene Rubber Isolation Wrap - Temp. -40 to +100 deg.C (CS/Alloy/Cu-Ni Pipes) - NPS 1/2 - 24
AT39
XAT039
Bonded Viton Rubber Isolation Wrap - Temp. +101 to +150 deg.C (CS/Alloy/Cu-Ni Pipes) - NPS 1/2 -24
AT40A
XAT040A
Isolation Pad(Type A - 140mm x 140mm) - Acoustic/General - NPS 1/2 - 24
AT40B
XAT040B
Isolation Pad(Type B - 140mm x 250mm) - Acoustic/General - NPS 1/2 - 24
AT40C
XAT040C
Isolation Pad(Type C - 140mm x 300mm) - Acoustic/General - NPS 1/2 - 24
AT40D
XAT040D
Isolation Pad(Type D - 200mm x 200mm) - Acoustic/General - NPS 1/2 - 24
AT40E
XAT040E
Isolation Pad(Type E - 250mm x 250mm) - Acoustic/General - NPS 1/2 - 24
AT40F
XAT040F
Isolation Pad(Type F - Variable Size) - Acoustic/General - NPS 1/2 - 24
AT41A
XAT041A
Slide Unit(Type A - 140mm x 140mm) - General - NPS 1/2 - 24
AT41B
XAT041B
Slide Unit(Type B - 140mm x 250mm) - General - NPS 1/2 - 24
AT41C
XAT041C
Slide Unit(Type C - 140mm x 300mm) - General - NPS 1/2 - 24
AT41D
XAT041D
Slide Unit(Type D - 200mm x 200mm) - General - NPS 1/2 - 24
AT41E
XAT041E
Slide Unit(Type E - 250mm x 250mm) - General - NPS 1/2 - 24
AT41F
XAT041F
Slide Unit(Type F - Variable Size) - General - NPS 1/2 - 24
AT42
XAT042
PTFE Isolation Pad - Bonded to Steel - NPS 1.1/2 - 24
AT43
XAT043
Pipe Penetration Single Seal (Packed) - Certified A0 & H0 Rating NPS 1/2 - 24
AT44
XAT044
Pipe Penetration Single Seal (Packed) - Certified A60 & H60 Rating - NPS 1/2 - 24
AT45
XAT045
Pipe Penetration Double Seal - Certified A0 & H0 Rating w/o Insulation & A60 H60 & H120 Rating with Insulation, NPS 1/2 - 24
AT46
XAT046
Pipe Penetration Double Seal - Certified upto J100 Jet Fire Resistance & A60 H60 & H120 Rating NPS 1/2 - 24
AT47
XAT047
Cold Isolation Shoe (C.S./Alloy Pipes) NPS 2 - 8
AT48
XAT048
Cold Isolation Shoe (C.S./Alloy Pipes) NPS 10 - 24
AT49
XAT049
2 Bolt Heavy Series Pipe Clamp with Circular Cold Isolation Block (CS/Alloy Pipes) - NPS 1/2 - 24
AT50
XAT050
Reinforcing Pad for Horizontal and Vertical Cu-Ni Pipes - NPS 2.1/2 - 24
AT51
XAT051
Full Encirclement Reinforcing Sleeve for Cu-Ni Pipes - NPS 2.1/2 - 24
AT52A
XAT052A
Type A Protection Shield for Diam 2" to 24"
AT52B
XAT052B
Type B Protection Shield for Diam 2" to 24"
AT52C
XAT052C
Type C Protection Shield for Diam 2" to 24"
AT52D
XAT052D
Type D Protection Shield for Diam 2" to 24"
AT52E
XAT052E
Type E Protection Shield for Diam 2" to 24"
AT52F
XAT052F
Type F Protection Shield for Diam 2" to 24"
AT53A
XAT053A
Type A 4 Point Shear Lug Bearing for Diam 2" to 24"
AT53B
XAT053B
Type B 2 Point Shear Lug Bearing for Diam 2" to 24"
AT54
XAT054
HP Mud and Cement High Pressure Clamps for Diam 2" to 6"
AT55A
XAT055A
Bolt on Shoe type A Uninsulated C.S. NPS 2"-6"
AT55B
XAT055B
Bolt on Shoe type B Uninsulated C.S. NPS 2"-6"
AT55C
XAT055C
Bolt on Shoe type C Uninsulated C.S. NPS 8"-24"
AT56
XAT056
Clamp for Vertical support NPS 2" to 8"
AT57
XAT057
HALFEN Pipe Shoe HRG-4 NPS 1/2" - 6"
AT58
XAT058
HALFEN Pipe Shoe HRG - 4 with Spacer Clip HCS AHS 5/1 NPS 1/2" - 6"
AT59
XAT059
Trunnion Cold Isolation Block with Integral Base Plate Light
AT60
XAT060
Flanged Supports for FRP/RTR Lines 1" - 32"
AT61
XAT061
Plate Attachment - Vertical Pipe (CS, LTCS, SS Pipes) - NPS 12"-48"
AT62
XAT062
Adjustable Guide Insert Bolts Parallel NPS 2"-48"
AT63
XAT063
Pipe Strap (Lined) for FRP / RTR Lines NPS 1 - 8
AT64
XAT064
Pipe Strap (Lined) for CuNi Lines NPS 1.1/2 - 8
AT65
XAT065
Full Encirclement Wrapper Plate (no longitudinal welding) for Pipes - NPS 2 - 48
AT66
XAT066
Stauff Clamp Heavy Series SPAL **,***,* xxx DPAL-AS NPS 1/2 - 6"
AT67
XAT067
Stauff Clamp Heavy Series SPAL/DUB **,***,* xxx DPAL-AS NPS 1/2" - 6"
AT68
XAT068
Trunnion Cold Isolation Block with Integral Base Plate Heavy
AT69
XAT069
Adjustable Guide Insert Bolts Perpendicular - NPS 2"-48"
AT70
XAT070
Adjustable Guide Insert Offset to Pipe Bolts Parallel - NPS 2"-48"
AT71
XAT071
Adjustable Guide Insert Offset to Pipe Bolts Perpendicular - NPS 2"-48"
AT72
XAT072
CPVC Pipe shoes height 100 to 200 for diam 1-1/2" to 24"
AT73
XAT073
GRE Pipe shoes height 100 to 200 for diam 26" to 40"
AT74A
XAT074A
CPVC Protection shield for diam 1/2" to 16" TYPE A
AT74B
XAT074B
CPVC Protection shield for diam 1/2" to 16" TYPE B
AT75A
XAT075A
Anti friction sliding plate for diam 1/2" to 40" TYPE A
AT75B
XAT075B
Anti friction sliding plate for diam 1/2" to 40" TYPE B
AT76
XAT076
Pipe Shoe NPS 18"-20"
AT87
XAT087
GRE Pipe shoes height 100 to 200 for diam 1-1/2" to 24"
AT88
XAT088
DN8 - DN50 - Single sided Pipe Slide
AT93
XAT093
GRE Pipe Clamps for diam 1.1/2" to 40"
AT94
XAT094
CPVC Pipe Clamps for diam 1.1/2" to 12"
AT95A
XAT095A
GRE Protection shield for diam 1/2" to 16" TYPE A
AT95B
XAT095B
GRE Protection shield for diam 1/2" to 16" TYPE B
AT96
XAT096
Welded Shoe for N.P.S. 1" - 36"
AT97
XAT097
Clamped Shoe (Unlined) for N.P.S. 1" - 24"
AT98
XAT098
Welded Shoe with re-pad for N.P.S. 1" - 36"
AT99
XAT099
Clamped Shoe (Lined) for N.P.S. 1" - 24"
AT100A
XAT100A
Trunnion Ptfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type A - NPS 1/2 - 24
AT100B
XAT100B
Trunnion Ptfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type B - NPS 1/2 - 24
AT101A
XAT101A
Ptfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type A - NPS 1/2 - 24
AT101B
XAT101B
Ptfe Faced Slide Unit (Suitable for Acoustic & Vibration Isolation) Type B - NPS 1/2 - 24
AT102
XAT102
Pipe Strap
AT103A
XAT103A
Clamped Pipe Shoe Pihasa 2134 IPE 160 NPS 1/2 - 4
AT103B
XAT103B
Clamped Pipe Shoe Pihasa 2134 IPE 200 NPS 1/2 - 16
AT103C
XAT103C
Clamped Pipe Shoe Pihasa 2134 IPE 240 NPS 3 - 16
AT103D
XAT103D
Clamped Pipe Shoe Pihasa 2134 IPE 270 NPS 5 - 16
AT104A
XAT104A
Clamped Pipe Shoe Pihasa 2136 Small NPS 1.1/2 - 30
AT104B
XAT104B
Clamped Pipe Shoe Pihasa 2136 Large NPS 1.1/2 - 30
AT105A
XAT105A
Reinforcing Pad for straight pipe/elbow for C.S. pipe.
AT105B
XAT105B
Reinforcing Pad for straight pipe/elbow for C.S. pipe.
AT108A
XAT108A
Lisega Type 49xx11 Pipe Clamp Base 0 to 350 deg.C - NPS 15 - 150
AT108B
XAT108B
Lisega Type 49xx12 Pipe Clamp Base - 0 to 350 deg.C - NPS 15 - 125
AT108C
XAT108C
Lisega Type 49xx13 Pipe Clamp Base - 0 to 350 deg.C - NPS 175 - 1000
AT108D
XAT108D
Lisega Type 49xx14 Pipe Clamp Base - 0 to 350 deg.C - NPS 15 - 900
AT108E
XAT108E
Lisega Type 49xx25 Pipe Clamp Base - 350 to 500 deg.C - NPS 15 - 900
AT108F
XAT108F
Lisega Type 49xx35 Pipe Clamp Base - 450 to 560 deg.C - NPS 15 - 900
AT108G
XAT108G
Lisega Type 49xx45 Pipe Clamp Base - 560 to 600 deg.C - NPS 15 - 900
AT108H
XAT108H
Lisega Type 49xx64 Pipe Clamp Base - 100 to 350 deg.C - NPS 15 - 125
AT108AX
XAT108AX
Lisega Type 49xx11 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 65,100,125,150 - ONLY
AT108BX
XAT108BX
Lisega Type 49xx12 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 65,100,125 - ONLY
AT108CX
XAT108CX
Lisega Type 49xx13 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 250,350,400 - ONLY
AT108DX
XAT108DX
Lisega Type 49xx14 (Larger Pipe Outside Diameter) Pipe Clamp Base - 0 to 350 deg.C - NPS 65,100,125,150,250,350,400 - ONLY
AT108EX
XAT108EX
Lisega Type 49xx25 (Larger Pipe Outside Diameter) Pipe Clamp Base - 350 to 500 deg.C - NPS 65,100,125,150,250,350,400 - ONLY
AT108FX
XAT108FX
Lisega Type 49xx35 (Larger Pipe Outside Diameter) Pipe Clamp Base - 450 to 560 deg.C - NPS 65,100,125,150,250,350,400 - ONLY
AT108GX
XAT108GX
Lisega Type 49xx45 (Larger Pipe Outside Diameter) Pipe Clamp Base - 560 to 600 deg.C - NPS 65,100,125,150,250,350,400 - ONLY
AT108HX
XAT108HX
Lisega Type 49xx64 (Larger Pipe Outside Diameter) Pipe Clamp Base - 100 to 350 deg.C - NPS 65,100,125 - ONLY
AT109
XAT109
Pipe Strap
AT111
XAT111
Slider Pad for diam 1/2" to 40"
AT112
XAT112
Loose Pipe Strap 1/4" to 36"
AT113
XAT113
Pipe Strap 1/4" to 36"
AT114
XAT114
Lisega Type 49xx63SP Pipe Clamp base - 0 to 350 deg.C - NPS 175 - 700
AT115
XAT115
Lisega Type 49xx63G Pipe Clamp base - 0 to 350 deg.C - NPS 250,700,900,1000
AT116
XAT116
Double Heavy Vertical Pipe Clamp - DN 15-1400
AT117
XAT117
Double Light Vertical Pipe Clamp - DN 15-1400
AT118
XAT118
Single Light Vertical Pipe Clamp - DN 15-1400
AT119
XAT119
Vertical Pipe Clamp for Spring Cans - DN 15-1400
AT120
XAT120
Single Light Vertical Pipe Clamp - DN 15-1400
AT121
XAT121
Single Heavy Vertical Pipe Clamp - DN15-1400
AT122
XAT122
Double Heavy Vertical Pipe Clamp - DN 15-1400
AT123
XAT123
Single Light Vertical Pipe Clamp - DN 15-1400
AT124
XAT124
Single Light Vertical Pipe Clamp - DN 15-1400
AT125
XAT125
Double Heavy Vertical Pipe Clamp - DN15-1400
AT126
XAT126
Pipe Shoe with Clamps - DN 15-1400
AT127
XAT127
Pipe Shoe with Clamps Cold Insulation - DN 15-800
AT128
XAT128
Pipe Shoe - DN 400-600
AT129
XAT129
Pipe Shoe - DN 650-1000
AT130
XAT130
Pipe Shoe with Clamps - DN 250-450
AT131
XAT131
Pipe Shoe with Clamps - DN 500-1000
AT132
XAT132
Pipe Clamp with Double Shoes - DN 50-1400
AT133
XAT133
Band for Copper Pipe NPS 2.5 - 8
AT134
XAT134
Pipe Strap (lined) NPS 3/8 -1
AT135
XAT135
Sliding Piece (Pipe Welded) NPS 1/2 - 40
AT136
XAT136
Lisega Type 49xx63G1SP Single-sided Pipe Slide - 0 to 350 deg. C - NPS 250,700,900,1000
AT140
XAT140
Clamped Pipe Shoe for S/S,6Mo & Duplex lines. - Temp -130 to 340 deg.C 4" to 24"
AT141
XAT141
Welded Pipe Shoe for S/S,6Mo & Duplex lines - Sch10s & below. Heavy Load or Vibration 6" to 24"
AT144
XAT144
Welded Pipe Shoe for CS & LTCS lines - 3/4" to 24"
AT145
XAT145
Clamped Pipe Shoe for CS & LTCS lines - 3/4" to 36"
AT146
XAT146
Welded Pipe Shoe for S/S Lines - 3/4" to 24"
AT147
XAT147
Welded Pipe Shoe for Duplex lines - 3/4" to 24"
AT148
XAT148
Welded Pipe Shoe for 6Mo lines - 3/4" to 24"
AT149
XAT149
Clamped Pipe Shoe for Galv,S/S 6Mo & Duplex lines - 3/4" to 36"
AT150
XAT150
Welded Pipe Shoe with Repad for S/S,6Mo and Duplex lines - 3/4" to 24"
AT151
XAT151
Welded Pipe Shoe with Repad for CS & LTCS lines - 3/4" to 24"
AT152
XAT152
Oglaend Pipe Clamp AISI 316L 1/2" to 2"
AT153
XAT153
Oglaend Pipe Clamp AISI 316L 1/2" to 2"
AT154
XAT154
Angle bracket for U-Bolt diam 1/2" to 8"
AT155
XAT155
Angle bracket for U-Bolt diam 1/2" to 8"
AT156
XAT156
Oglaend Pipe Clamp HDG 1/2" to 2"
AT157
XAT157
Oglaend Pipe Clamp HDG 1/2" to 2"
AT158
XAT158
Clamped Pipe Shoe for FRP Pipe - 2" to 36"
AT159
XAT159
Clamped Pipe Shoe for FRP Pipe - 2" to 36"
AT160A
XAT160
Type A - Clamped Pipe Short Shoe Linestop for FRP Pipe - 2" to 36"
AT160B
XAT160
Type B - Clamped Pipe Long Shoe Linestop for FRP Pipe - 2" to 36"
AT161
XAT161
DN3 - DN20 - Single-sided Pipe Slide
AT162
XAT162
DN8 - DN50 - Austenitic Single-sided Pipe Slide
AT163
XAT163
DN3 - DN20 - Austenitic Single-sided Pipe Slide
AT164
XAT164
Oglaend Single Clamp Shoe - Uninsulated pipe 1" to 6"
AT165
XAT165
Oglaend Single Clamp Shoe - Insulated pipe 1/2" to 6"
AT166
XAT166
Angle bracket for Pipe Clamp diam 1/2" to 2"
AT167
XAT167
Angle bracket for U-Bolt diam 1" to 4"
AT168
XAT168
Oglaend Pipe Clamp diam 1/2" to 1.1/2"
AT174
XAT174
Full Encirclement Reinforcing pad (cut from pipe)
AT175
XAT175
Part Encirclement Reinforcing pad (cut from pipe)
AT185
XAT185
Butterfly Valve Support F4
AT211
XAT211
Pipe Slide Low
AT212
XAT212
Pipe Slide Low 2-Sided
AT213
XAT213
Pipe Slide Low
AT214
XAT214
Pipe Slide Low 2-Sided
AT215
XAT215
Foot Support A2
AT216
XAT216
Foot Support A3
AT217
XAT217
Pipe Slide Low 3-Sided
AT218
XAT218
Pipe Slide Low 3-Sided
AT219
XAT219
Foot Support A1
AT220
XAT220
Foot Support B1
AT221
XAT221
Foot Support B2
AT222
XAT222
Foot Support B3
AT223
XAT223
Pipe Slide
AT224
XAT224
Pipe Slide
AT225
XAT225
Pipe Clamp A
AT226
XAT226
Pipe Slide High
AT227
XAT227
Pipe Slide High
AT228
XAT228
Pipe Slide Low
AT229
XAT229
Pipe Slide Low 4-Sided
AT230
XAT230
Pipe Slide Low 4-Sided
AT231
XAT231
Pipe Slide Extra High
AT232
XAT232
Pipe Slide Extra High
AT233
XAT233
Pipe Slide High
AT234
XAT234
Pipe Slide Extra High
AT235
XAT235
Pipe Slide Low 2-Sided
AT236
XAT236
Pipe Slide Low 3-Sided
AT237
XAT237
Pipe Slide Low 4-Sided
AT238
XAT238
Pipe Slide High 2-Sided
AT239
XAT239
Pipe Slide High 3-Sided
AT240
XAT240
Pipe Slide High 4-Sided
AT241
XAT241
Pipe Slide High 2-Sided
AT242
XAT242
Pipe Slide High 3-Sided
AT243
XAT243
Pipe Slide High 4-Sided
AT244
XAT244
Pipe Slide High 2-Sided
AT245
XAT245
Pipe Slide High 3-Sided
AT246
XAT246
Pipe Slide High 4-Sided
AT247
XAT247
Pipe Slide Extra High 2-Sided
AT248
XAT248
Pipe Slide Extra High 3-Sided
AT249
XAT249
Pipe Slide Extra High 4-Sided
AT250
XAT250
Pipe Slide Extra High 2-Sided
AT251
XAT251
Pipe Slide Extra High 3-Sided
AT252
XAT252
Pipe Slide Extra High 4-Sided
AT253
XAT253
Pipe Slide Extra High 2-sided
AT254
XAT254
Pipe Slide Extra High 3-sided
AT255
XAT255
Pipe Slide Extra High 4-sided
AT256
XAT256
Pipe Slide
AT257
XAT257
Pipe Slide
AT258
XAT258
Pipe Slide
AT259
XAT259
Pipe Slide

Modify User Defined Ancillary Geometry
Modify User Defined Ancillary Geometry


The standards are available in the Supports application BRAN.

The standards are available in the Supports application.
BR01
XBR01
2 Way Brace for Open Ended Connection to Pipe.
BR02
XBR02
2 Way Brace for Open Ended Connection to Flange.
BR03
XBR03
2 Way Bracing for Orifice Connections.
BR04
XBR04
4 Way Brace for Open Ended Connection to Pipe.
BR05
XBR05
3 Way Brace for Open Ended Connection to Flange.
BR06
XBR06
4 Way Brace for Open Ended Connection to Flange.
BR07
XBR07
2 Way Brace for Open Ended Connection to Pipe.
BR08
XBR08
2 Way Brace for Open Ended Connection to Flange.
BR09
XBR09
2 Way Brace for Open Ended Connection to Flange.


The standards are available in the Supports application. Refer to Modify User Defined Ancillary Geometry for further information on user defined U-bolt standards.
BT01A
XBT01
U Bolt gripped (type A)
BT01B
XBT01
U Bolt non-gripped (type B)
BT02
XBT02
U Bolt tico coated
BT03
XBT03
U Bolt PTFE coated insulation
BT04A
XBT04
U Bolt Guide (GB) Black, NPS 1/2 - 36.
BT04B
XBT04
U Bolt Guide (GG) Galvanized, NPS 1/2 - 36.
BT04C
XBT04
U Bolt Guide (GP) Plastic Coated, NPS 1/2 - 36.
BT05
XBT05
U Bolt gripped with sleeve, NPS 2 - 24.
BT06
XBT06
U Bolt Guide for Cupro Nickel Lines, NPS 1/2 - 8.
BT07
XBT07
U Bolt Guide for Carbon Steel Lines, NPS 1/2 - 8.
BT09
XBT09
Lined U-Bolt guided 2" TO 8"
BT10
XBT10
U Bolt Guide, NPS 1/2 - 36"
BT11
XBT11
Loose Type U Bolt Guide, NPS 1/2 - 36"
BT12
XBT12
U Bolt for steel pipe, NPS 1/2 - 3"
BT13
XBT13
U Bolt for steel pipe, NPS 4 - 32"
BT14
XBT14
Expansion U Bolt for steel pipe, NPS 1 - 32"
BT15
XBT15
Lined U Bolt NPS 1 1/4 - 2"
BT16
XBT16
Lined U Bolt NPS 2 1/2 - 36"
BT17
XBT17
U Bolt for use with slip pad NPS 1/2 - 32"
BT18
XBT18
U Bolt with Teflon Pad NPS 2 1/2 - 32"
BT19
XBT19
Expansion U Bolt with Slip Pad NPS 1 - 32"
BT21
XBT21-
U Bolt Guide for CS & LTCS Lines - 1/2" to 6"
BT22
XBT22-
U Bolt Grip for CS & LTCS Lines - 1/2" to 6"
BT23
XBT23-
U Bolt Guide for Galv,S/S,6Mo & Duplex lines - 1/2" to 6"
BT24
XBT24-
U Bolt Grip for Galv,S/S,6Mo & Duplex lines - 1/2" to 6"

Modify User Defined Ancillary Geometry
Modify User Defined Ancillary Geometry


The standards are available in the Supports application for Rack.

The standards are available in the Supports application.
RACK-REST
XCA01
Rack Rest
CA02A
XCA02
Cable Clip with Angles
CA02B
XCA02
Cable Clip


The standards are available in the Supports application.
CT01
XCT01
'L' Bracket up.
CT02
XCT02
'L' Bracket down.
CT03
XCT03
'L' Bracket Cantilever.
CT04
XCT04
Goal post.
CT05
XCT05
Support frame.
CT06
XCT06
Cantilever bracket.
CT07
XCT07
'T' Post. (Vertical down).
CT08
XCT08
'T' Post. (Vertical up).


The standards are available in the Supports application FB01XFB01.

The standards are available in the Supports application.
FB01
XFB01
Frame Bracing.
FB02
XFB02
Frame Bracing.


The standards are available in the Supports application DT01A1XSU01TICO.

The standards are available in the Supports application.
DT01
XDT01
HVAC duct support frame.
DT02
XDT02
HVAC duct support frame.
DT03
XDT03
HVAC duct cantilever bracket.
DT04
XDT04
HVAC duct 'L' bracket.


The standards are available in the Supports application SU01A1XSU01Tico.

The standards are available in the Supports application.
SU01A1
XSU01
TICO bondslip unit type A size 1.
SU01A2
XSU01
TICO bondslip unit type A size 2.
SU01A3
XSU01
TICO bondslip unit type A size 3.
SU01A4
XSU01
TICO bondslip unit type A size 4.
SU01B1
XSU01
TICO bondslip unit type B size 1.
SU01B2
XSU01
TICO bondslip unit type B size 2.
SU01B3
XSU01
TICO bondslip unit type B size 3.
SU01B4
XSU01
TICO bondslip unit type B size 4.
SU01C1
XSU01
TICO bondslip unit type C size 1.
SU01C2
XSU01
TICO bondslip unit type C size 2.
SU01C3
XSU01
TICO bondslip unit type C size 3.
SU01C4
XSU01
TICO bondslip unit type C size 4.
SU02A1
XSU02
PTFE. slide unit type A size 1.
SU02A2
XSU02
PTFE. slide unit type A size 2.
SU02A3
XSU02
PTFE. slide unit type A size 3.
SU02A4
XSU02
PTFE. slide unit type A size 4.
SU02B1
XSU02
PTFE. slide unit type B size 1.
SU02B2
XSU02
PTFE. slide unit type B size 2.
SU02B3
XSU02
PTFE. slide unit type B size 3.
SU02B4
XSU02
PTFE. slide unit type B size 4.
SU02C1
XSU02
PTFE. slide unit type C size 1.
SU02C2
XSU02
PTFE. slide unit type C size 2.
SU02C3
XSU02
PTFE. slide unit type C size 3.
SU02C4
XSU02
PTFE. slide unit type C size 4.
SU03
XSU03
Shoe Supports, Teflon Slide Plate (Upper Element) NPS 3-36.
SU04
XSU04
Shoe Supports, Teflon Slide Plate NPS 2-36.


The standards are available in the Supports application.
The standards marked with a * are not available in the Supports application. These standards are obsolete and have been replaced by other new standards.
TT01*
XTT01
Trunnions for straight piping.
TT02*
XTT02
Trunnions for pipe elbows.
TT03*
XTT03
Trunnions for CuNi straight piping.
TT04
XTT04
Base ELL and Pipe Support NPS 2-36
TT05
XTT05
Base ELL and Pipe Support NPS 2-36 with Bearing Plate
TT06
XTT06
Base ELL and Pipe Support Variable NPS 2-36
TT07
XTT07
Base ELL and Pipe Support Variable NPS 2-36 with Bearing Plate
TT08
XTT08
Base ELL and Pipe Support for RTJ Spools NPS 2-36
TT09
XTT09
Base ELL and Pipe Support for RTJ Spools NPS 2-36 with Bearing Plate
TT10
XTT10
Base Support for RTR Pipe NPS 2-14
TT11
XTT11
Base Support for RTR Pipe NPS 2-14 with Bearing Plate
TT12
XTT12
Base Support Bolt On NPS 2-36
TT13
XTT13
Base Support Bolt On with Bearing Plate NPS 2-36
TT14
XTT14
Type A Dummy Extension for Horizontal Pipe NPS 2-36
TT15
XTT15
Type B Dummy Extension for Horizontal Pipe NPS 2-36
TT16
XTT16
Type C Dummy Extension for Horizontal Pipe NPS 2-36
TT17
XTT17
Dummy Extension for Vertical Pipe NPS 2-36
TT18
XTT18
Base Support Adjustable Base NPS 2-24
TT19
XTT19
Base Support Adjustable Base with Bearing Plate NPS 2-8
TT20
XTT20
Support for Relief Valve Discharge Pipe NPS 2-12
TT21
XTT21
Rod Hanger Welded Elbow Trunnion NPS 12-24
TT22
XTT22
Base Support Anchor for RTR Pipe NPS 2-14
TT23
XTT23
Trunnion with an Integral Cold Isolation Block for C.S./Alloy Pipes NPS 1.1/2-20
TT24
XTT24
Trunnion Clamp for Vertical Pipe NPS 2-24
TT25
XTT25
90 Degree Cranked Vertical Dummy Leg for 2" - 24"
TT26
XTT26
Vertical Dummy Leg for 2" - 24"
TT27
XTT27
Trunnion With Integral Guide for 2" - 24"
TT28
XTT28
Base Support Anchor for RTR Pipe NPS 2-14 with Bearing Plate
TT29
XTT29
GRE Pipes Vertical Dummy Leg for diam 2" - 24"
TT30
XTT30
CPVC Pipes Vertical Dummy Leg for diam 2" - 24"
TT31
XTT31
GRE Pipes Trunnion for 2" - 24"
TT32
XTT32
CPVC Pipes Trunnion for 2" - 24"
TT33
XTT33
GRE Pipes Stanchion for 2" - 24"
TT34
XTT34
CPVC Pipes Stanchion for 2" - 24"
TT35
XTT35
Vertical Dummy Leg for diam 2" - 24"
TT36
XTT36
Trunnion NB 1.1/2" - 30"
TT37
XTT37
Adjustable Trunnion NB 2" - 12"
TT38
XTT38
Base Support Welded to pipe 2" TO 24"
TT39
XTT39
Base Support Welded to elbow 2" TO 24"
TT40
XTT40
Trunnion for uninsulated lines - NPS 20-250
TT41
XTT41
Trunnion for uninsulated lines - NPS 20-250
TT42
XTT42-
Trunnion for Elbow - 1" to 36"
TT43
XTT43-
Trunnion for Straight Pipe - 1" to 36"
TT44
XTT44-
Trunnion with Repad for Straight Pipe - 1" to 36"


The standards are available in the Supports application VT01XVT01.

The standards are available in the Supports application.
VT01
XVT01
Support from vessel for 2" to 10" N.B. Pipe.
VT02
XVT02
Support from vessel for 12" to 20" N.B. Pipe.
VT03
XVT03
Guide from vessel for 8" to 20" N.B. Insulated Pipe.
VT04
XVT04
Guide from vessel for 8" to 24" N.B. Pipe.
VT05
XVT05
Support from vessel for 2" to 6" N.B. Pipe.
VT06
XVT06
Guide from vessel for 2" to 4" N.B. Pipe.
VT07
XVT07
Support Bracket Uninsulated Pipe NPS 2 - 10
VT08
XVT08
Support Bracket Insulated/Uninsulated Pipe NPS 6 - 18
VT09
XVT09
Support Bracket Uninsulated Pipe NPS 8 - 18
VT10
XVT10
Support Bracket Uninsulated Pipe NPS 2 - 24
VT11
XVT11
Support Bracket Uninsulated Pipe NPS 2 - 4
VT12
XVT12
Support Bracket Guide for Uninsulated Pipe NPS 16 - 24
VT13
XVT13
Support Bracket Guide for Uninsulated CS Pipe NPS 10 - 14
VT14
XVT14
Support Bracket Guide for Uninsulated CS Pipe NPS 6 - 8
VT15
XVT15
Support Bracket Guide for Uninsulated CS Pipe NPS
1/2 - 4
VT16
XVT16
Special Guide for Vertical Pipe in the Splash Zone NPS 3 - 12
VT17
XVT17
Support Bracket Uninsulated/Insulated Pipe NPS 1/2 - 3
VT18
XVT18
Support Bracket Insulated Pipe NPS 3 - 14
VT19
XVT19
Support Bracket Guide for insulated Pipe NPS 16 - 24
VT20
XVT20
Cantilever support from vertical & horizontal vessel for 2" to 10" N.B. Pipe.
VT21
XVT21
Braced cantilever support from vertical & horizontal vessel for 2" to 10" N.B. Pipe.
VT22
XVT22
Cantilever support from vertical vessel for vertical pipes with lugs LT13 or LT15 2.1/2" to 20" N.B. Pipe.
VT23
XVT23
Cantilever support from vertical vessel for vertical pipes with Trunnions 2.1/2" to 14" N.B. Pipe.
VT24
XVT24
Cantilever braced support from vertical vessel for vertical pipes with Trunnions 2.1/2" to 14" N.B. Pipe.


You must use the following conventions for structural catalogues so that the Model applications can recognize them and so that the Paragon applications can use them:
The diagrams in the following subsection illustrate the structure of the catalogues.
The PURPose of the CATAlogue must be set to one of the following: STL, FITT, JOIN or PFIT. This makes sure that any specifications and applications which are built can recognized 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 makes sure 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 PURPose of the CATAlogue must be set to one of the following: STL, FITT, JOIN or PFIT. This makes sure that any specifications and applications which are built can recognized 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 CATAlogue must be set to one of the following: STL, FITT, JOIN or PFIT. This makes sure that any specifications and applications which are built can recognized 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 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 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 makes sure 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 GTYPE of the Profile, Fitting, Joint or Panel Fitting must be set. This makes sure 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 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.


As with the piping catalogue, there are many ways in which you can structure your steelwork catalogues. The same two ways of structuring both types of catalogue are preferred, the difference being the types of administrative elements used. However, whereas for piping there is only one type of catalogue (namely for piping components), the following three types of catalogue are used for steelwork:
The basic layout of the catalogues is the same as for piping, for example, where the reference data is stored, but the way in which the data is separated differs.

PROFILES
JOINTS
FITTINGS (FITT and PFIT)
PROFILES
PROFILES
JOINTS
JOINTS
FITTINGS (FITT and PFIT)
FITTINGS (FITT and PFIT)

The basic layout of the catalogues is the same as for piping, for example, where the reference data is stored, but the way in which the data is separated differs.


Purpose
Purpose should be the same as the SPEC with which the catalogue is to be used (STL, FITT, JOIN, PFIT etc.)
Cstandard
Catalogue standard
STSEction ‑ Structural Section
Description
Description of Section
Gtype-
Generic type of element contained in section; this should be the same as the type of element used in MODEL, e.g.BEAM
Description
Description of Section
Gtype-
Generic type of element contained in section; this should be the same as the type of element used in MODEL, e.g.BEAM
Purpose
Purpose should equate to the STYP of the items as defined in the Spec
Function
Description
Gtype
Identifies the Generic element type
Skey
not applicable
Ptref
Point set reference
Gmref
Geometry set reference
Ngmref
Negative geometry reference
DataSetRef
Data set reference
Pstreference
Pline set reference
Gstreference
Profile set reference
CDetail
Detail reference
Ownconn
Owning connection profile type
Attconn
Attached connection profile type
CPlot
Plot file for reference used in documentation
Icon
Icon name
Cstandard
Standard·
PTSE ‑ Point Sets
Description
Description of point set
Gtype
Identifies the Generic element type
Skey
Symbol Key to which point set relates
Purpose
Purpose of point set
Description
Description of point set
Gtype
Identifies the Generic element type
Skey
Symbol Key to which point set relates
Purpose
Purpose of point set
Gtype
Identifies the Generic element type
Purpose
Purpose of geometry set
NGMS ‑ Negative Geometry Sets
Description
Description of geometry set
Gtype
Identifies the Generic element type
Purpose
Purpose of geometry set
Description
Description of geometry set
Gtype
Identifies the Generic element type
Purpose
Purpose of geometry set
DTSE - Datasets
Description
Description of dataset
Gtype
Identifies the Generic element type
Purpose
Purpose of dataset
Description
Description of dataset
Gtype
Identifies the Generic element type
Purpose
Purpose of dataset
Gtype
Identifies the Generic element type
Purpose
Purpose of point set
Gtype
Identifies the Generic element type
Purpose
Purpose of geometry structural set


The general purpose of Datasets is twofold:
Refer to Catalogues and Specifications Reference Manual Section 3 for further information.
To let you query catalogue parameters.
To let you input design parameters via simple forms and menus.
To let you query catalogue parameters.
To let you query catalogue parameters.
To let you input design parameters via simple forms and menus.
To let you input design parameters via simple forms and menus.

Section 3


The Profile catalogue should be structured so that the separation of the data is sensible, for example, all sections of the same generic profile should be under the structural section. The segregation beneath the section should be used to associate groups within the generic type; for example, in the case of British Standards, each category should contain sections with the 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.


The Fittings catalogue should be structured so that all fittings of a given generic type are stored beneath the same section, for example, lifting lugs, stiffeners, etc. Within each section the fittings should be broken down into groups relating to the profile on which the fitting can be used, for example, I, H, L, COLU, BEAM.
The Panel Fitting catalogue should follow the same format as the Fitting catalogue except that the panel fitting element is called a PFIT.

except
PFIT


The Joints catalogue should be structured so that all joints of a given generic type are stored beneath the same section, for example, cleats, endplates, baseplates. Within each section the joints should be broken down into categories relating to the types of sections to which the joint can be connected, for example, I‑I, I‑Chan, I‑L. The generic types of the sections should be stored against Ownconn and Attconn attributes.


The following conventions for structural specifications must be followed to make sure 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.


Panel thickness availability in the Model module can be controlled via the catalogue Specification mechanism. Using ‘Ans’ ‘Maxans’ attributes on the SPCO can limit the allowable minimum and maximum panel thicknesses.

Type
Attribute
Data
Description
SPEC
Description
{ str }
display on form spec gadget
Question
THK
question for offspring
Purpose
PLT
spec purpose
Tquestions
thickness
specific question for offspring
SPCO
Ans
real
min thickness
Maxans
real
max thickness
SPEC
Description
{ str }
display on form spec gadget
Question
THK
question for offspring
Purpose
PLT
spec purpose
Tquestions
thickness
specific question for offspring
SPCO
Ans
real
min thickness
Maxans
real
max thickness

Note:
The CATREF is not used as the geometry is defined in the Model module.

Note
:
SPEC
str
SPCO


attributes for specification elements in hierachical order pupose FITT

Attributes for Specification elements in hierarchical order:
SPEC
Description
{ str }
display on form spec gadget
Purpose
FITT
spec purpose
Question
TYPE
question for offspring
Matref
{ ref }
material reference in Property DB
SELE
Description
{ str }
information on type of profile
Tanswer
{ word }
generic type of profile that can own the fitting. ANY will allow a fitting to be used on any profile type.
Questions
STYP
question for offspring
SELE
Description
{ str }
display on form stype gadget
Tanswer
{ word }
sub-type of fitting, for example, LUG, HOLE.
SPCO
Catref
{ ref }
pointer to HFIT in catalogue
Detref
{ ref }
pointer to detail text

str
ref
str
word
str
word
ref
ref


attributes for specification elements in hierachical order pupose PFIT

Attributes for Specification elements in hierarchical order:
SPEC
Description
{ str }
display on form spec gadget
Purpose
PFIT
spec purpose
Question
TYPE
question for offspring
Matref
{ ref }
material reference in Property DB
SELE
Description
{ str }
display generic type on form
Question
STYP
question for offspring
Tanswer
{ word }
generic type of fitting
SELE
Description
{ str }
display on form stype gadget
Tanswer
{ word }
sub-type of fitting, for example, Door, Window.
SPCO
Catref
{ ref }
pointer to PFIT in catalogue
Detref
{ ref }
pointer to detail text

SPEC
str
ref
SELE
SELE
str
word
SPCO
ref
ref


attributes for specification elements in hierachical order pupose Join

Attributes for Specification elements in hierarchical order:
SPEC
Description
{ str }
display on form spec gadget

Purpose
JOIN
spec purpose

Question
OTYP
question for offspring

Matref
{ ref }
material reference in Property DB
SELE
Description
{ str }
display on form stype gadget

Tanswer
{ word }
generic type of profile which joints can be owned by. ANY will allow joints to be owned by any profile, NONE will allow setting of PJOI specrefs.

Question
ATYP
question for offspring
SELE
Description
{ str }
information on type of profile
Tanswer
{ word }
generic type of profile that can be attached to joint. ANY will allow any type of profile to be attached to the joint.
Question
STYP
question for offspring
SPCO
Catref
{ ref }
pointer to PFIT in catalogue
Detref
{ ref }
pointer to detail text
SELE
Description
{ str }
information on type of profile

Tanswer
{ word }
generic type of profile that can be attached to joint. ANY will allow any type of profile to be attached to the joint.

Question
STYP
question for offspring
SPCO
Catref
{ ref }
pointer to PFIT in catalogue

Detref
{ ref }
pointer to detail text

SPEC
str
ref
SELE
str
word
SELE
SPCO


For the materials of a structural element (MATR) to be set in Model, you must be able to see a Properties Database (DB) containing the available materials.
To create a Material World, carry out the following steps:
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:
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.
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:
Note:
All densities are in kg/cu m.

edit module PARAGON mode PROP rw
$m/%PMLUI%/DES/DATA/MLOADPROP
Note
:
$m/%PMLUI%/DES/DATA/MLOADPROP
pathname


The .NET Customization User Guide gives software engineers, with experience of software development in C# using Visual Studio, guidance on the development of .NET customization for AVEVA products. The AVEVA .NET Customization User Guide is not intended to be used as an introduction to C#.


The introduction of a customization capability using Microsoft .NET technology has opened up a whole new world of customization and is particularly relevant for the integration of AVEVA products with other customer systems. .NET API's provide access to various aspects of the product including Graphical User Interface, Database and Geometry.
As part of AVEVA's strategy of 'continual progression' the .NET customization capability has been introduced in such a way that it can be used alongside the existing PML based customization. Through the use of PML.NET, an enhancement to PML which allows the PML programmer to call .NET code, customization which utilizes the strengths of .NET compiled code and PML can be achieved.

The above diagram illustrates the two new methods of customization using .NET technology. The first is via the concept of a .NET Addin and the second using PML.NET. Both methods provide a mechanism whereby a .NET assembly (dll) can be dynamically loaded into a module at runtime.


The Common Application Framework (CAF) is an extensible framework which provides the .NET programmer with access to various services which support both application development and customization. The foundations of the CAF are provided by the two interface assemblies:
These interfaces provide the following major services:
Simple customization can be achieved by creating User Defined Attributes in Lexicon, delivering them in C# and loading them using the Aveva.ApplicationFramework.dll. Refer to for further information.
It may be desirable to introduce extra GUI tools with complex customizations, this can be achieved using the Aveva.ApplicationFramework.Presentation.dll.
The Application Framework Interfaces are documented at https://help.aveva.com/API/CAF/index.html.
Aveva.ApplicationFramework.dll
Aveva.ApplicationFramework.Presentation.dll
Aveva.ApplicationFramework.dll
Aveva.ApplicationFramework.dll
Aveva.ApplicationFramework.Presentation.dll
Aveva.ApplicationFramework.Presentation.dll
AddinManager:
This class provides properties and methods for the management of ApplicationFramework Addins.
ServiceManager:
This class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. The ServiceManager also acts as a service provider responding to requests for services. It can also be used by applications and application addins to publish additional services.
SettingsManager:
This class provides properties and methods for the management of application settings which are stored in settings groups which are persisted between sessions.
AddinManager:
This class provides properties and methods for the management of ApplicationFramework Addins.
AddinManager:
This class provides properties and methods for the management of ApplicationFramework Addins.
ServiceManager:
This class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. The ServiceManager also acts as a service provider responding to requests for services. It can also be used by applications and application addins to publish additional services.
ServiceManager:
This class defines an interface which provides a means by which the various components of the ApplicationFramework can publish their services. The ServiceManager also acts as a service provider responding to requests for services. It can also be used by applications and application addins to publish additional services.
SettingsManager:
This class provides properties and methods for the management of application settings which are stored in settings groups which are persisted between sessions.
SettingsManager:
This class provides properties and methods for the management of application settings which are stored in settings groups which are persisted between sessions.
CommandBarManager:
This provides access to the ribbon menus and commandbars of a CAF based application. It also has methods to load the definition of menus and commandbars from User Interface customization (UIC) files.
CommandManager:
This class defines an interface to provide the presentation framework client with a mechanism for the management of command objects which can be associated with Tools or other User interface objects. The action of invoking a tool, for example: clicking a ButtonTool, will cause the execution of the associated command object. It is possible to associate the same command object with a number of different user interface objects, for example: ButtonTool on a Menu and a LinkLabel, thereby allowing for the centralization of these user interface object actions within a command. Various state-like properties of a command, for example: enabled/checked, would also be reflected in all user interface objects associated with a command; disabling a command would cause all associated user interface objects to be disabled. User interface objects are associated with a command via a CommandExecutor derived class.
ResourceManager:
This class defines an interface to provide Addins with a simplified mechanism to access localizable resources. The ResourceManager provides a number of methods which allows an addin to then access the various types of resources (string, image, cursor, icon etc.) which resource files may contain.
WindowManager:
This provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer with methods to create MDI and docked windows to host user controls.
CommandBarManager:
This provides access to the ribbon menus and commandbars of a CAF based application. It also has methods to load the definition of menus and commandbars from User Interface customization (UIC) files.
CommandBarManager:
This provides access to the ribbon menus and commandbars of a CAF based application. It also has methods to load the definition of menus and commandbars from User Interface customization (UIC) files.
CommandManager:
This class defines an interface to provide the presentation framework client with a mechanism for the management of command objects which can be associated with Tools or other User interface objects. The action of invoking a tool, for example: clicking a ButtonTool, will cause the execution of the associated command object. It is possible to associate the same command object with a number of different user interface objects, for example: ButtonTool on a Menu and a LinkLabel, thereby allowing for the centralization of these user interface object actions within a command. Various state-like properties of a command, for example: enabled/checked, would also be reflected in all user interface objects associated with a command; disabling a command would cause all associated user interface objects to be disabled. User interface objects are associated with a command via a CommandExecutor derived class.
CommandManager:
This class defines an interface to provide the presentation framework client with a mechanism for the management of command objects which can be associated with Tools or other User interface objects. The action of invoking a tool, for example: clicking a ButtonTool, will cause the execution of the associated command object. It is possible to associate the same command object with a number of different user interface objects, for example: ButtonTool on a Menu and a LinkLabel, thereby allowing for the centralization of these user interface object actions within a command. Various state-like properties of a command, for example: enabled/checked, would also be reflected in all user interface objects associated with a command; disabling a command would cause all associated user interface objects to be disabled. User interface objects are associated with a command via a CommandExecutor derived class.
ResourceManager:
This class defines an interface to provide Addins with a simplified mechanism to access localizable resources. The ResourceManager provides a number of methods which allows an addin to then access the various types of resources (string, image, cursor, icon etc.) which resource files may contain.
ResourceManager:
This class defines an interface to provide Addins with a simplified mechanism to access localizable resources. The ResourceManager provides a number of methods which allows an addin to then access the various types of resources (string, image, cursor, icon etc.) which resource files may contain.
WindowManager:
This provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer with methods to create MDI and docked windows to host user controls.
WindowManager:
This provides access to the main application window, the StatusBar and a collection of MDI and docked windows. It also provides the addin writer with methods to create MDI and docked windows to host user controls.

https://help.aveva.com/API/CAF/index.html

AddinManager
ServiceManager
SettingsManager
CommandBarManager
CommandManager
ResourceManager
WindowManager
https://help.aveva.com/API/CAF/index.html


The database related interfaces are provided by the interface assemblies:
Interfaces are available to allow customizations to query or write to the program database. Refer to Database Interface for further information.
Aveva.Core.Database.dll & Aveva.Core.Database.Filters.dll
Aveva.Core.Database.dll & Aveva.Core.Database.Filters.dll
Aveva.Core.Database.dll & Aveva.Core.Database.Filters.dll

Database Interface
Database Interface


The geometry related interfaces are provided by the interface assembly:
This interface has a number of geometry related classes. For example, position, orientation, direction, arc, line and plane.
Aveva.Core.Geometry.dll
Aveva.Core.Geometry.dll
Aveva.Core.Geometry.dll


The maths related interfaces are provided by the interface assembly:
This interface has a number of two dimensional and three dimensional low level geometry related classes.
Aveva.Core.Maths.Geometry.dll
Aveva.Core.Maths.Geometry.dll
Aveva.Core.Maths.Geometry.dll


Some general shared interfaces are provided in the interface assembly:
This provides current element, selection changed events and Datal listing facilities. You can use Visual Studio to find the classes and methods.
Aveva.Core.Shared.dll
Aveva.Core.Shared.dll
Aveva.Core.Shared.dll


Utility interfaces are provided in the interface assembly:
This provides messaging, string utilities, tracing, undo and units. It also provides access to the command line but this is not supported
Aveva.Core.Utilities.dll
Aveva.Core.Utilities.dll
Aveva.Core.Utilities.dll


Interfaces to access the drawlist and colours are provided in the interface assembly:
The rest of this user guide will cover in detail how to write a .NET addin and an assembly containing classes with methods which are callable from Programmable Macro Language (PML). It will describe the use of the various .NET interfaces via the use of sample code.
Aveva.Core3D.Graphics.dll
Aveva.Core3D.Graphics.dll
Aveva.Core3D.Graphics.dll


Interfaces to access Engineer API through the Programmable Macro Language (PML) are provided in the interface assembly:
This provides functionality to manage lists from macros, add and remove rows from grids, set colours and export to xlsx. All methods are PML callable and can be used with PML or C# (.NET) code.
Aveva.Engineering.Tags.Pml.dll
Aveva.Engineering.Tags.Pml.dll
Aveva.Engineering.Tags.Pml.dll


Zip file sample,zip sample using core/core3D

A zip file (Samples.zip) containing a number of samples using the Core/Core3D interfaces can be found in the installation directory. Each sample directory contains a number of C# source files and a Visual Studio project. Before opening and building a project in Visual Studio, set the environment variable %AVEVA_DESIGN_EXE% to include the product installation directory (this will make sure that all the project's assembly references are correct) and set %CAF_ADDINS_PATH% to include the directory where you want to build the sample (this will make sure that the project builds the example here). When running the product you also need to make sure that %CAF_ADDINS_PATH% is set to the same build directory to make sure that the example addin is loaded from here.


This is a C# addin containing a simple form which displays the attributes for the currently selected element. To use this within a module, copy the module's addins.xml file, for example, DesignAddins.xml, from the product directory to the directory set in CAF_ADDINS_PATH and then modify it to include AttributeBrowserAddin. To access the addin you will need to add the command to a State button on the ribbon or toolbar depending on the User Interface (UI) in the module. To do this in the application, open up the customization window and either create a new tab group/toolbar or use an existing one. Create a new State Button and in its properties specify the command to be "Aveva.ShowAttributeBrowserCommand", then click Apply and close the window. You should be able to open the attribute browser button by clicking on the new button.

Apply


This is a C# addin containing a number of code examples that can be run via a command. The command Aveva.Example.Command, is loaded when the addin is started. To add the addin to a module, copy the modules Addins.xml, for example, DesignAddins.xml from the product directory to the directory set in CAF_ADDINS_PATH. Edit this file adding the ExampleAddin to it (There is an example addins file in the ExamplesAddin directory). The command can be run from a ComboBox tool added to the ribbon or toolbar depending on the User Interface (UI) in the module. To do this in the application, create a new Tab group/toolbar using the Customization utility, add a ComboBox tool to it and attach the command to that. Each example can then be run by selecting it in the ComboBox. Since these examples create and claim Model elements they need to be run in a Design multi-write database.


This is a C# addin which contains a Flexible Explorer control on a window and can be used with any of the modules. You will need to build the Addin inside Visual Studio after updating the references and then copy the DLL (FlexibleExplorerAddin.dll) and the associated XML sample file (FlexibleExplorerSample.xml) to the executable directory.
In order to load the addin into the modules you will need to add a reference in the DesignAddins.XML file.
Finally, you will need to use the Customization tool to add a state button in the module in order to display the addin.
With the sample Flexible Explorer definition file (FlexibleExplorerSample.xml) the addin will display all the elements in the model.
Detailed information about the Flexible Explorer is available, refer to Use of Flexible Explorer Control for further information.

Use of Flexible Explorer Control
Use of Flexible Explorer Control


Installation for this example is exactly the same as with previous examples (refer to AttributeBrowserAddin or ExamplesAddin for further information). After following these instructions, enter the module you want to use and, once loaded, bring up the customization window. This example differs to the Attributes browser as it doesn't create a command, so in order to load the grid you need to create a state button as before, but the command is done differently. Open the command dialog by clicking on the "…" button to the right of the field. For the type, select Command Class and for the class select DockedWindowStateCommand, finally click OK. Next click on the "…" button in the Arguments field and select the Void .ctor(System.String) constructor. For the window key, enter Grid Control Addin and then click OK to close the dialog.
Once this has been done, close the customization window and click on the new state button. The grid control window should appear just like any other form.

AttributeBrowserAddin
ExamplesAddin
AttributeBrowserAddin
ExamplesAddin
Command Class
DockedWindowStateCommand
OK
Void .ctor(System.String)
Grid Control Addin
OK


This example provides a simple C# class which can be called from within the Programmable Macro Language (PML).


An example of an AVEVA Grid Control hosted on a Programmable Macro Language (PML) form can be found in the Samples.zip file.


Suggestions to minimize the speed of start-up of addins have been made above. There are 2 built-in ways to monitor this and investigate the reasons if poor performance is suspected.
Target start-up time for an Addin should be no more than 1 second, if possible. To find out how long your Addin takes to start-up set the following environment variable:
Output similar to the following will then be displayed in the Console Window:
The standard facilities found in the classes of the Aveva.Core.Utilities.Tracing namespace can be used for tracing performance problems as well as for other general coding investigations.
The PdmsTrace class gives access to all the facilities of the Plant Design Management System (PDMS) trace system and provides a means of outputting general trace messages and values during processing. PdmsTrace functions also enable querying and setting of PDMS trace flags; give access to the current state of the call stack; and allow starting and stopping of Central Processor Unit (CPU) time tracing.
The TraceEntry class provides the means to trace the entry and exit of functions as processing takes place. As the nesting of function calls gets deeper and deeper the function entry messages are indented further and further. Though this output can quickly get verbose it can frequently give evidence of problems in the code - for example functions being called too frequently … or not at all!
To work correctly in C#, TraceEntry needs to know about entry and exit from functions in correct chronological order. There is a difficulty with this in C# because of the way that "garbage collection" works in that language. This means, in particular, it is necessary to make sure that the function exit event occurs at the right moment. This can be achieved by using the Dispose method explicitly:
There are still problems with this however as you will need to catch every "return" statement individually. Also the Dispose() method will never be called if an exception occurs. A simpler and more robust way is to do this job using the C# "using" command as follows:
If you are using these facilities to investigate the start-up of an addin, you will need to set the chosen trace flag from your code:
And, finally, you can use the CPU time profiling options in conjunction with TraceEntry by using:
Reviewing Addin Start-up Time
set AVEVA_CAF_TRACING=PERFORMANCE
AVEVA Everything3D Design Mk2.1.0[10061]  (WINDOWS-NT 6.3)
Copyright 2012 to current year.  AVEVA Solutions Limited and its subsidiaries. All
      rights reserved.

Issued to UKCAMSPLS
Loading addins took: 0.282 secs.
Starting addin Explorer: 0.984 secs.
Starting addin DrawList: 0.024 secs.
Starting addin Collections: 1.264 secs.
Starting addin History: 0.011 secs.
Starting addin ReferenceList: 0.170 secs.
Starting addin PipeCheck: 0.447 secs.
Starting addin Find: 0.117 secs.
Starting addin Links Addin: 0.042 secs.
Starting addin Attributes: 0.706 secs.
Starting addin Status Controller: 0.016 secs.
Starting addin ModelChanges: 0.047 secs.
Starting addin SVGCompare: 0.612 secs.
Starting addin Aveva.Core.InstrumentationImport.Addin.DataUpdate: 0.114 secs.
Starting addin Aveva.Core.AVEVANetExportConfigAddin: 0.237 secs.
Starting addin Aveva.Core.ReportingAddin: 0.327 secs.
Starting addin MessageAddin: 0.240 secs.
Starting addin Integrator: 0.533 secs.
Total time starting addins: 5.905 secs.
Loading UIC file
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\MyDataAddin.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\StatusController.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\design.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\CoreSchematicMenu.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\SVGCompare.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\AVEVA.design.cabling.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\AVEVA.design.hvac.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\AVEVA.design.MDS.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\AVEVA.design.piping.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1.customisation\AVEVA.design.steelwork.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\MessageWindowCoreMenus.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\AVEVA.design.laser.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\Integrator.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\DiagramViewer.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1\InstrumentationImportAddin.uic
Defined new tools
Loading UIC file C:\AVEVA\Plant\E3D2.1.customisation\Model.Addin.uic
Defined new tools
Updating CommandBar Layout: 0.002 secs.
Loading CommandBar layout: 0.172 secs.
DockManager.LoadFromXML: 2.628 secs.
Loading Window Layout: 3.227 secs.
TraceEntry tr = TraceEntry.Enter("Start", (TraceNumber)101);

// ...
// code being traced ...
// ...
tr.Dispose();   // explicit call on exit
using (TraceEntry tr = TraceEntry.Enter("Start", (TraceNumber)101))

{
     // ...
     // code being traced ...
     // ...
}    // implicit call to Dispose() on exit from the block
     // even if there are exceptions or multiple return statements
PdmsTrace.SetTraceFlag((TraceNumber)101, 1);

PdmsTrace.StartCPUTrace();

// ...
// code being timed ...
// ...
PdmsTrace.StopCPUTrace(true);

PdmsTrace
TraceEntry
exit
TraceEntry
TraceEntry
(
"Start"
(
TraceNumber
)
// ...
// code being traced ...
// ...
// explicit call on exit
using
(
TraceEntry
TraceEntry
"Start"
, (
TraceNumber
)

// ...
     // code being traced ...
     // ...
// implicit call to Dispose() on exit from the block
     // even if there are exceptions or multiple return statements
PdmsTrace
((
TraceNumber
)
PdmsTrace
// ...
// code being timed ...
// ...
PdmsTrace
(
true
);


Exception Handling in a Common Application Framework Addin

The code of all components of a Common Application Framework (CAF) Addin is executed within the event loop of the host AVEVA program. Any exception raised within the Addin code, or any code called by it, that is not caught by the addin code itself will have to be handled in the event loop. The AVEVA host has effective ways to handle some classes of exceptions - namely PdmsExceptions and PMLNetExceptions. In the situation where the host program is in the process of executing Programmable Macro Language (PML), then the PML first has an opportunity to handle the exception itself. If the PML does not handle the exception, or if no PML is currently being executed, the host program handles these exceptions by notifying the user of the exception text and number interactively via the Status Bar, MessageBoxes or the CommandLine display as appropriate. Event loop processing then continues normally.
For all other classes of exception the host event loop has no standard procedure and the outcome is that the host program terminates untidily. It is therefore very poor programming style to allow general exceptions to escape from the Addin. A relatively easy way to prevent this is to trap exceptions systematically at every entry point between the host event loop and the component interfaces - for example in every Command.Execute function:
This recommendation does not, of course, replace the routine practice of handling exceptions at the appropriate points within the Addin code when they are anticipated and can be dealt with effectively. It simply provides a safety net for unanticipated and otherwise unhandled exceptions.
/// <summary>
/// Execute
/// </summary>
public override void Execute()

{
     try
     {

          // Do the required function.
             DoTheJob();
     }
     catch (System.Exception ex)

     {

          // Pass on PdmsExceptions and PMLNetExceptions.
          // Handle all others:
          //   (perhaps by raising a PdmsException).
     }

}

private void DoTheJob()
{
     // Do the required function...
}

/// <summary>
/// Execute
/// </summary>
public override void

{

try

catch
Exception

// Pass on PdmsExceptions and PMLNetExceptions.
          // Handle all others:
          //   (perhaps by raising a PdmsException).

private void
 DoTheJob()

  // Do the required function...


Thread safety in a Common Application Framework Addin

C# allows code to use multiple threads and there are situations where this can be useful in an Addin. However this technique should be used with care as the host AVEVA program is not itself multiple thread safe. Thus there can be only one thread at a time which executes functions in DbLayer, Common Application Framework (CAF) or other host core code.


TeleTypewriter (TTY) addins that implement the IAddinTty interface can also be defined in the <module>Addins.xml and will be loaded when the application starts. In graphics only those addins which implement the IAddin interface will be loaded and started as before. Addins can implement both interfaces but may need refactoring so that no User Interface (UI) elements are started in TTY mode. User Defined Attributes (UDAs) implemented as pseudo attributes can now be implemented in this way; refer to example implementation of IAddinTty interface below.
using System;

using System.IO;

using System.Windows.Forms;

using Aveva.ApplicationFramework;

using Aveva.ApplicationFramework.Presentation;

using Aveva.Core.Database;

using Ps = Aveva.Core.Database.DbPseudoAttribute;

using NOUN = Aveva.Core.Database.DbElementTypeInstance;

namespace Aveva.Core.Tests.AddinTty

    /// <summary>
    /// Summary description for AddinTtyTest
    /// </summary>
    public class AddinTty : IAddinTty, IAddin

    {
        /// <summary>
        /// Start the Addin
        /// </summary>
        /// <param name="serviceManager"></param>
        void IAddinTty.Start(ServiceManager serviceManager)

        {
            // get uda attribute
            DbAttribute uda = DbAttribute.GetDbAttribute(":UDADDIN");

            if (uda != null)
            {

                // Create instance of delegate containing method to evaluate
                // pseudo attribute
                Ps.GetStringDelegate dele =

new Ps.GetStringDelegate(AddinTtyValue);

                // and pass delegate instance to core.
                Ps.AddGetStringAttribute(uda, NOUN.EQUIPMENT, dele);

            }
        }

        void IAddinTty.Stop()

        {

        }

        String IAddinTty.Name

        {

            get { return "AddinTty"; }
        }

        get { return "AddinTty"; }IAddinTty.Description

        {

           get { return "AddinTty"; }

        }

        // String delegate for UDA
        static private string AddinTtyValue(DbElement ele, DbAttribute att, DbQualifier qualifier)

        {

            return "AddinTty";

        }
    }
}

using
using
using
using
using
using
using
using
namespace

/// <summary>

/// Summary description for AddinTtyTest
    /// </summary>

public class
    {

/// <summary>

/// Start the Addin

/// </summary>

/// <param name="serviceManager"></param>

void

// get uda attribute

null
)

// Create instance of delegate containing method to evaluate
                // pseudo attribute

new

  // and pass delegate instance to core.

void

String

get
{
return

"AddinTty"
; }

get
{
return

"AddinTty"

get
{
return

"AddinTty"

// String delegate for UDA

static private string

return

"AddinTty"


User access to functionality provided via an addin is normally provided through the use of ribbon menus and tools on a commandbar. Reference was made earlier, in the User Guide about addin commands, that the Common Application Framework (CAF) provides a mechanism to allow the use of ribbon menus and commandbars for an application to be defined in a User Interface Customization (UIC) file. This section provides details of how a CAF based application can be configured to load a UIC file, and how the UIC file can be edited using the applications interactive user interface customization tool. Newer modules, for example Model and Draw use the Ribbon commandbar, this is configured in the same way as the original toolbar (detailed below).


Configuring a Module to Load a User Interface Customization File

Each Common Application Framework (CAF) based application has an Extensible Markup Language (XML) configuration file which contains a list of User Interface Customization (UIC) files that the application should load at start-up. The default location for this file is in the same directory as the application executable. It has a filename of the form <Module Name>Customisation.xml. By default the UIC files are also expected to be in the same directory as the application executable. You can however specify the full path to the UIC file including the use of UNC pathnames. It is also possible to define a project specific UIC file. The string "$1" in the UIC path will be replaced with the current project name.
If during addin development you do not wish to modify the customization configuration file in the install directory (this is particularly likely to be the case if you are using a server based installation) then the default location of the customization configuration file can be overridden using the environment variable CAF_UIC_PATH. You can then edit a copy of the file and point this environment variable at the directory you copy it to.
The order of the UIC files in this configuration file is significant. They are loaded in order since it is possible for a UIC file to define a tool which is hosted in a menu or on a commandbar defined in a UIC file already loaded.
A new UIC file can be added to a module simply by adding a new line to the corresponding customization configuration file. The actual content of the UIC file will be created using the interactive user interface customization tool described below.
As well as adding to the customization configuration file, an addin can also load a UIC file directly using the AddUICustomisationFile method of the CommandBarManager.
This UIC file will be loaded before those define in the Customization configuration file, so it must create its own menu or commandbar to host its tools.
<?xml version="1.0" encoding="utf-8" ?>
 <UICustomizationSet xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <DefaultIcon>AvevaSharedIcons:ID_WARNING</DefaultIcon>
 <UICustomizationFiles>
 <CustomizationFile Name="Module" Path="design.uic" />
 <CustomizationFile Name="SchematicExplorerAddin" Path="CoreSchematicMenu.uic" />
 <CustomizationFile Name="Project" Path="$1.uic" Optional="true" />
 <CustomizationFile Name="SVGCompare" Path="SVGCompare.uic" />
 <CustomizationFile Name="Cabling" Path="AVEVA.design.cabling.uic" />
 <CustomizationFile Name="Hvac" Path="AVEVA.design.hvac.uic" />
 <CustomizationFile Name="Supports" Path="AVEVA.design.MDS.uic" />
 <CustomizationFile Name="Piping" Path="AVEVA.design.piping.uic" />
 <CustomizationFile Name="Steelwork" Path="AVEVA.design.steelwork.uic" />
 <CustomizationFile Name="MessageAddin" Path="MessageWindowCoreMenus.uic" />
 <CustomizationFile Name="Laser" Path="AVEVA.design.laser.uic" />
 <CustomizationFile Name="Integrator" Path="Integrator.uic" />
 <CustomizationFile Name="DiagramViewer" Path="DiagramViewer.uic" />
 <CustomizationFile Name="InstrumentationImportAddin" Path="InstrumentationImportAddin.uic"
      />

 </UICustomizationFiles>
 </UICustomizationSet>
// Load a UIC file for the AttributeBrowser.
ICommandBarManager commandBarManager = dependencyResolver.GetImple\-mentationOf<ICommandBarManager>();
commandBarManager.AddUICustomisationFile("AttributeBrowser.uic", "AttributeBrowser");

// Load a UIC file for the AttributeBrowser.
"AttributeBrowser.uic"
"AttributeBrowser"