Escolar Documentos
Profissional Documentos
Cultura Documentos
Administrator Guide
Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.
Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every
part of it (including source code, object code, any data contained in it, the manual and any other
documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.
All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective license agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.
First published September 2007
AVEVA Solutions Ltd, and its subsidiaries
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.
Contents
Page
Administrator Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Overview of the MDS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Administrators Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
MDS Catalogue and Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Project Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
12.0
3:3
3:4
3:4
3:4
3:5
3:6
3:7
3:7
3:8
3:8
3:9
3:9
3:9
3:10
3:10
3:11
3:11
3:11
3:11
3:12
3:12
3:12
3:13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3
ii
12.0
5:3
5:3
5:3
5:3
5:3
5:3
5:3
5:4
5:4
5:4
5:4
5:4
5:4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:9
iii
12.0
7:2
7:2
7:2
7:3
7:3
7:3
7:3
7:3
7:4
7:4
7:4
7:4
iv
8:2
8:2
8:2
8:2
8:2
8:2
8:3
12.0
8:3
8:3
8:3
8:3
8:4
9:1
9:2
9:2
9:2
9:2
9:2
9:2
9:2
9:2
9:2
9:2
12.0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:3
Ancillaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:4
Branch Reinforcements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:12
U bolts
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:17
vi
12.0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:24
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:27
vii
12.0
viii
12.0
Introduction
1.1
1.2
1.3
Administrators Role
The administrator is responsible for the initial setup of the defaults associated with the MDS
application. This document describes the defaults that can be modified by the administrator
in order to configure MDS to specific project requirements.
Most of the MDS defaults are stored in a PARAGON database, and are viewed or modified
using a series of forms. The remainder of the defaults are stored in four text files, in which
the appropriate fields are modified in a text editor by the administrator.
Six default forms are provided, as follows:
1:1
12.0
MDS-REPORT-DEFS - holds the pre-defined MDS reports available for the project.
Note: the last two files work in conjunction with each other.
1.4
1.5
Project Setup
The recommended Project setup when using MDS in the AVEVA Plant/Marine project
environment is explained in the MDS Project Setup section of the MDS Customisation
Guide.
1:2
12.0
2.1
Overview
This chapter provides guidance to the MDS administrator on how to upgrade an existing
MDS11.6 project to MDS12 using the MDS12 Defaults Conversion Upgrade utility in the
Multi Discipline Supports (MDS) application.
It is assumed that the MDS administrator has an expert understanding of the MDS
application.
The MDS12 Defaults Conversion Upgrade utility only applies to six of the current MDS
defaults files, i.e.:
DES-SUPP-DEFS
DES-SUPP-PARS
DES-SUPP-HANG
DES-SUPP-ALTD
DES-SUPP-ID
DES-SUPP-ICONS
The MDS12 Defaults Conversion Upgrade utility allows the MDS administrator to
automatically convert the above six MDS default files, defined for the existing MDS11.6
project, into eight individual PARAGON CATALOGUE elements contained in a single
nominated PARAGON database, i.e.:
CATA /MDS/OPTION/DEFAULTS
CATA /MDS/ANCILLARY/DEFAULTS
CATA /MDS/TRUNNION/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
CATA /MDS/HANGER/DEFAULTS
CATA /MDS/PRELIMINARY/DEFAULTS
CATA /MDS/ZONEID/DEFAULTS
CATA /MDS/ICON/DEFAULTS
Important: Any existing MDS ATTA components in the project's DESIGN databases will
NOT be modified. The MDS12 Defaults Conversion Upgrade utility will only
create/modify elements contained within the eight PARAGON CATALOGUE
elements converted from the six MDS default files.
2:1
12.0
2.2
2.3
Preliminary Requirements
The existing Project to be converted, via the MDS12 Defaults Conversion Upgrade
utility, must already be operating at version 12 of AVEVA Plant/Marine.
The MDS administrator should ensure that the existing project is backed-up,
copied and saved, prior to entering the project and running the MDS12 Defaults
Conversion Upgrade utility.
The standard MDS12 appware version of the application files and projects must be
installed and included into the evars search paths for the Project, PMLLIB and
PDMSUI in the batch entry files.
The MDS12 Defaults Conversion Upgrade utility requires the new MDS12 version of
the Project.
Expunge all other PARAGON users from the existing Project to be upgraded to
MDS12.
The MDS administrator responsible for running the MDS12 Defaults Conversion
Upgrade utility MUST have WRITE access to the nominated PARAGON database. The
nominated PARAGON database must be the first CATALOGUE database in list order of
the selected MDB, but not necessarily the first database in the MDB.
The MDS administrator responsible for running the MDS12 Defaults Conversion
Upgrade utility MUST be a member of the Project CATALOGUE Administration Team,
CATADMIN or the Team Master.
A typical example for the MDS12 Defaults Conversion Upgrade utility evar setting
required for the Version 12 project and MDS12 application defaults directory search
path is shown below:
set <projectcode>dflts - which may be a search path and where the example working
project <projectcode> = TWD, and where possibly the clients CORPORATE project code =
COR, and <DL> = Drive Letter,
e.g.
settwddflts=
<DL>:\working\project\TWD\TWDdflts
<DL>:\corporate\project\COR\CORdflts
<DL>:\AVEVA\MDS12\project\MDS\MDSdflts
AVEVA recommend that the project PARAGON database to be used to store the
converted MDS12 application default settings should only contain the eight MDS12
defaults CATALOGUE elements shown in Overview of this document.
2:2
12.0
Using an independent PARAGON database to store the MDS12 defaults will simplify
the process of including and/or excluding as a foreign database, copying a foreign
database or reconfiguring the database into another project. The MDS12 master MDS
project defaults CATALOGUE database is named MDS/MDSAPPDEFAULTS. The
AVEVA Database Number is 7351 and the associated Database File Number is
also 7351, i.e. /%MDS000%/mds7351.
Note: Only AVEVA Solutions Ltd can assign project database numbers of 7000 and above.
2.4
The client MDS12 project defaults CATALOGUE databases should follow a similar
naming convention, but including the three letter project code, e.g. for a project named
"TWD", the local project MDS12 PARAGON CATALOGUE database should be named
MDSTWD/MDSAPPDEFAULTS.
A typical client corporate project named "COR", the corporate project MDS12
PARAGON CATALOGUE database should be named MDSCOR/MDSAPPDEFAULTS.
However if the eight MDS12 project defaults CATALOGUE elements are to be included
into another existing PARAGON CATALOGUE database along with other project
specific CATALOGUE data, then this is also acceptable, but not recommended
because of the reasons stated above.
Figure 2:1.
2. Select MDS12 - Upgrade to PARAGON Defaults from the pull-down menu. The
MDS12 Defaults Conversion Upgrade utility form will be displayed as shown in Figure
2:2.: MDS12 Defaults Conversion Upgrade Form.
2:3
12.0
Figure 2:2.
The MDS12 Defaults Conversion and Upgrade form displayed above, shows that all six
of the MDS12 default files have been successfully located somewhere in the search
path of MDS12 default directories, defined in the project TWD evar %TWDDFLTS%.
Note: All six of the MDS12 default files have been located, therefore the OK button will be
activated, allowing the MDS administrator to continue with MDS12 Defaults
Conversion Upgrade.
Click the OK button to continue with the MDS12 Default Files Conversion and Upgrade
or click the Cancel button to abort.
3. However, if any of the six of the MDS12 default files have NOT been successfully
located they will be displayed on then form as de-activated, i.e. "greyed out", and
suitable text will be shown on the form advising the MDS administrator the process is
unable to continue, e.g.
Example:
2.
Therefore the OK button will be de-activated, and thus NOT allow the MDS administrator to
continue with MDS12 Defaults Conversion Upgrade. Refer to Figure 2:3.: MDS12 Defaults
Conversion Upgrade Form.
2:4
12.0
Figure 2:3.
After clicking the OK button a Confirm form will be displayed, as shown below, asking
if you wish to CONTINUE with this upgrade.
Click Yes to CONTINUE and run the MDS12 Upgrade or Click No to abort.
Figure 2:4.
After clicking the Yes button on the Confirm form, the MDS12 Defaults Files
Conversion Upgrade will commence and no further user interaction with the user is
required.
Clicking the No button will abort the upgrade procedure.
2:5
12.0
2.5
2.5.1
DES-SUPP-DEFS
CATA /MDS/OPTION/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
CATA /MDS/HANGER/DEFAULTS
CATA /MDS TRUNNION/DEFAULTS
CATA /MDS/PRELIMINARY/DEFAULTS
DES-SUPP-PARS
CATA /MDS/ANCILLARY/DEFAULTS
CATA /MDS/TRUNNION/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
DES-SUPP-HANG
CATA /MDS/HANGER/DEFAULTS
DES-SUPP-ALTD
CATA /MDS/STRUCTURE/DEFAULTS
DES-SUPP-ID
CATA /MDS/ZONEID/DEFAULTS
DES-SUPP-ICONS
CATA /MDS/ICON/DEFAULTS
Shown below is a table depicting which MDS default file is partially or wholly
transferred into which MDS12 PARAGON CATALOGUE element.
CATA /MDS/OPTION/DEFAULTS
DES-SUPP-DEFS
CATA /MDS/STRUCTURE/DEFAULTS
DES-SUPP-DEFS
DES-SUPP-PARS
DES-SUPP-ALTD
CATA /MDS/ANCILLARY/DEFAULTS
DES-SUPP-DEFS
DES-SUPP-PARS
2:6
12.0
2.5.2
2.6
CATA /MDS/TRUNNION/DEFAULTS
DES-SUPP-DEFS
DES-SUPP-PARS
CATA /MDS/HANGER/DEFAULTS
DES-SUPP-DEFS
DES-SUPP-HANG
CATA /MDS/PRELIMINARY/DEFAULTS
DES-SUPP-DEFS
CATA /MDS/ZONEID/DEFAULTS
DES-SUPP-ID
CATA /MDS/ICON/DEFAULTS
DES-SUPP-ICONS
The MDS12 upgrade utility will generate its own LOG file detailing the actions
performed during the MDS12 upgrade.
The LOG file will be created and located in the MDS12-DEFAULTS directory found in
the project information directory defined in the evar %<project code>INFO%, and
found in the normal project directory structure, e.g. for a project code of TWD the
information directory would be located in /<pdms project directory>/twd/twdinfo/
MDS12-DEFAULTS. If the MDS12-DEFAULTS directory does not exist, it will
automatically be created along with the LOG file
The LOG file for a project code of TWD will typically be named as shown below;
%TWDINFO%/MDS12-DEFAULTS\MDS-DEFAULTS-CONVERSION-to-CATA-DB31Jan2006-154739.pmllog
or
%PDMSUSER%/MDS12-DEFAULTS\MDS-DEFAULTS-CONVERSION-to-CATA-DB31Jan2006-154739.pmllog
IMPORTANT NOTE: The date and time the MDS12 upgrade commenced will always
be appended to the name of the LOG file.
For Reference ONLY - A copy of a typical example of a MDS12 Upgrade LOG file can
be found in the MDS12 release directory i.e.
/AVEVA/mds12dev/MDS12-Upgrade-Example-LOG-file/ MDS-DEFAULTSCONVERSION-to-CATA-DB-31Jan2006-154739.pmllog
2:7
12.0
Objective
To generate an Upgrade macro file in an existing 11.6 project currently using the MDS
application.
The Upgrade macro file contains the names of all the current MDS ATTA and PLAT
element types in the current MDB along with the attribute values for the SPREF and the
UDA :MDSMATREF for these element types.
Note: In the MDS12 the UDA :MDSMATREF has been replaced by the AVEVA PDMS
standard attribute MATREF at all ATTA element types.
The UDA :MDSMATREF still applies to all MDS PLAT element types in the MDS12.
Important: Only run the generated Upgrade macro file in an already Upgraded 12 version
of the project. This is an existing 11.6 project version which has already been
Upgraded to a 12 project version via the standard AVEVA PLANT 12 Upgrade
procedure for an existing 11.6 project. Plus the existing 11.6 project running
MDS has been Upgraded via the standard AVEVA MDS12 Defaults Upgrade
utility found in the PARAGON module.
2.6.1
Update Process
Note: The Upgrade may be run multiple times on the same or different MDB's in the same
project without causing any corruption. However you must make sure that all
databases containing MDS supports are run through this Upgrade procedure at least
once.
It is advisable but NOT compulsory to complete this Upgrade process before any new MDS
supports or any other new database elements are created in a project.
It is good housekeeping for you to Date stamp all of the upgraded 12 project databases
before proceeding with this Upgrade process on an Upgraded 12 project.
The Upgrade process should be started in the MDS 11.6 project application and completed
in MDS12 project application.
The DESIGN module Upgrade process for the MDS12 version is as follows:
1. Copy the new MDS12 PML function supplied with the MDS12.0.SP5 version: i.e.
"...\pmllib\design\functions\mds116DesignFor12Upgrade.pmlfnc"
into
the
corresponding PMLIB folder, ...\pmllib\design\functions, in the existing MDS11.6
appware.
2. From within the existing 11.6 project MONITOR module, type PML REHASH ALL on
the command line.
Note: The user MUST have write access to the MDS11.6 PMLLIB folders for this to update
the "pml.index" file.
3. Enter an appropriate MDB containing MDS supports and generate the Upgrade macro
file for the selected MDB by running the new PML function via the command line: For
example !!mds116DesignFor12Upgrade().
4. Transfer the Upgrade macro file from the current 11.6 project folder into the
corresponding folder of the target Upgraded 12 version of the project.
5. Run the Upgrade macro on the command of the DESIGN module of the Upgraded 12
project.
For
example
$M/C:\AVEVA\Plant\MDS12.0.SP4\project\mde\mdeinfo\
2:8
12.0
MDS12DesignAttaUpgrade\MDS116-to-MDS12-DESIGN-ATTA-UPGRADE-MACRO27Aug2009-105747.pmlmac
6. Running the Upgrade macro file will automatically generate an Upgrade Log file in the
same folder of the Upgraded12 project as the Upgrade macro file itself. For example
C:\AVEVA\Plant\MDS12.0.SP4\project\mde\mdeinfo\MDS12DesignAttaUpgrade\MDS
12-DESIGN-ATTA-UPGRADE-LOG-FILE-27Aug2009-105747.pmllog.
7. A successful Upgrade will not generate any other data except for that shown below:
<START of MDS12 DESIGN Module PROJECT UPGRADE LOG FILE>
*** If there are NO SCREEN ERRORS and the UPGRADE LOG FILE is EMPTY the
MDS ATTA and PLAT DESIGN Module PROJECT UPGRADE was SUCCESSFUL
***
<END of MDS12 DESIGN Module PROJECT UPGRADE LOG FILE>
2:9
12.0
2:10
12.0
3.1
Overview
The MDS Admin Data form is the main control form for the MDS application. It allows the
administrator to control some of the design limits within which supports can be created. The
form also allows the administrator to set the criteria that MDS uses to locate support zones
etc.
The default values/settings shown on the forms are those that exist when the MDS
application is first installed.
Note that some of the defaults on the Options(1) tab can be modified by the designer using
the MDS Application Defaults form (refer to the MDS User Guide).
The MDS Admin Data form modifies values in /MDS/OPTION/DEFAULTS, which are the
defaults that are set for the MDS Application Defaults form in MDS design.
Changes made are only applied to the database when the Apply button is pressed. To keep
the changes Save Work operation needs to be performed.
The Dismiss button removes the form. If changes have been made, but not applied, a
window is displayed asking if the changes are to be applied before exiting.
3.2
3:1
12.0
Figure 3:1.
Modify menu
The following form is displayed, which shows the Options (1) tab selected:
Figure 3:2.
3:2
12.0
3.3
3.3.1
Default
value
Session/default
catalogue modifiable
Description
1/10
Session
This is the slope value above which MDS creates a framework type support perpendicular to
the pipe (see Figure 3:3.: MDSSUPPMS slope > 1/10). Below this slope value, MDS allows
the pipe to sit at an angle relative to the vertical framework (see Figure 3:4.: MDSSUPPMS
slope < 1/10).
Figure 3:3.
Figure 3:4.
3:3
12.0
3.3.2
Default value
(mm)
Session/default
catalogue modifiable
Description
10
Session
Steelwork overlap.
This value determines the overlap distance for steelwork overlap type joints on the support
frameworks (see Figure 3:7.: MDSSUPPCL and MDSSUPPOV).
3.3.3
Default value
(mm)
Session/default
catalogue modifiable
Description
50
Session
Figure 3:5.
3.3.4
MDSPACKDI
Default value
(mm)
Session/default
catalogue modifiable
Description
Session
This is the maximum allowable overlap that can occur between a support attachment and its
associated supporting steelwork (see Figure 3:6.: MDSPACKMO).
3:4
12.0
Figure 3:6.
3.3.5
MDSPACKMO
Default value
(mm)
Session/default
Description
catalogue modifiable
100
Session
This value is overridden by the new MDS ancillary default values declared in the MDS
PARAGON module defaults catalogue, i.e. in the DATA members found in a typical MDS
ancillary default DTSE element. For example, DTSE /MDS/ATTA/DEFAULTS/AT01/100/
FRMW (see Framework Clearance Option, Closed End Clearance, Open End Clearance).
When a designer chooses to build a support using the Clearance option, this value is used
to determine the clearance on both sides of the support attachment (see Figure 3:7.:
MDSSUPPCL and MDSSUPPOV), For example, if the MDS ancillary default values are not
found.
3:5
12.0
Figure 3:7.
3.3.6
Default value
(degrees)
Session/default
catalogue modifiable
Description
30
Default catalogue
This default determines the maximum allowable angle in the horizontal plane with respect to
the datum pipe centreline that a pipe can have in order to be added to a framework (see
Figure 3:8.: MDSMAXHANG).
3:6
12.0
Figure 3:8.
3.3.7
3.3.8
MDSMAXHANG
Default value
(mm)
Session/default
catalogue modifiable
Description
150
Default catalogue
Minimum hanger
information only.
rod
length
for
MDS
Default value
(degrees)
Session/default
catalogue modifiable
Description
30
Default catalogue
This default determines the maximum allowable slope for a horizontal pipe that can be
supported by a hanger. If the user attempts to support a section of pipe whose slope is
greater than the MDSMAXPIVA angle an error is displayed (see Figure 3:9.: MDSMAXPIVA
and MDSPIVWARN).
3:7
12.0
3.3.9
3.3.10
Default value
Session/default
Description
catalogue modifiable
Standard
MDS
Default catalogue
Default value
(degrees)
Session/default
catalogue modifiable
Description
Default catalogue
This default is also associated with hangers and determines the angle above which a
warning is displayed to the user. If the user attempts to support a section of pipe whose
slope is greater than or equal to the MDSPIVWARN angle, an error is displayed but the user
is allowed to continue with the design process.
Note: It is essential that the value of MDSPIVWARN is always less than the value of
MDSMAXPIVA.
In the example given in Figure 3:9.: MDSMAXPIVA and MDSPIVWARN, the designer would
have received a warning alert, as the slope of the pipe is greater than the MDSPIVWARN
angle but less than the MDSMAXPIVA angle.
Note: The MDS manufacturers hanger interfaces (LICAD, PSDesigner and Witch Hanger)
will override these default settings.
Figure 3:9.
3:8
12.0
3.3.11
3.3.12
Default value
(mm)
Session/default
catalogue modifiable
Description
150
Default catalogue
Create (MDSCONNS)
Default value
Session/default
catalogue modifiable
Description
With
Geometry
Default catalogue
If the Create option is set to No Connections, the connection icons on all support forms
become inactive. If the Create option is set to Without Geometry, the create and delete
connection icons become active, and the modify and force connect icons remain inactive.
This is because these icons are only used for modifying joint geometry attributes. If the
Create option is set to With Geometry, then all icons become active.
3.3.13
Default value
Session/default
catalogue modifiable
Description
WARNING
Default catalogue
The Modify Support option enables MDS to know what to do if the support is connected.
This option dictates the error messages when modifying a connected support in the normal
way.
Default setting available:
WARNING: a warning message is displayed, asking the user if she or he wishes to
continue, every time a support is modified.
ERROR: the user will be asked to delete the connection before continuing.
CONTINUE: the user will not receive any messages before the support is modified.
3:9
12.0
3.4
3.4.1
Default value
(mm)
Session/default
catalogue modifiable
Description
Default catalogue
This is the value used for flange gap control when the flange gap toggle is true on the MDS
Application Defaults form. Refer to the Support Application Defaults, for more information.
3.4.2
Default value
Session/default
catalogue modifiable
Description
Default catalogue
3:10
12.0
3.4.3
Default value
Session/default
Description
catalogue modifiable
Default catalogue
TRANSPORTATION#
/SUPPORT
Default catalogue
The default MDSTRANPREF contains the prefix string that identifies a transportation
support. If the support name starts with the transport prefix, the STEX of all support
attachments associated with the support will have the transportation#/support text string,
contained in the default MDSTRANISO. This is appended to the support name in the
Attachment Stext attribute and will appear on the relevant Piping Isometric.
3.4.4
3.4.5
3.4.6
Default value
Session/default
catalogue modifiable
Description
Default catalogue
Default value
Session/default
catalogue modifiable
Description
Kgs
Default catalogue
Default
value
Session/default
catalogue modifiable
Description
SPS
Default catalogue
false
Default catalogue
false
Default catalogue
3:11
12.0
The MDSSPECPRE default is the special support number prefix and is used when special
supports are created. The prefix is used in combination with the standard support name. It
can be made to be unique within the current MDB by setting the MDSSPECFLA default to
true. Setting the default value to false allows the special support number to exist at more
than one support. Setting MDSSPECON to true prevents the user from proceeding until a
special support number is entered.
3.4.7
Default value
Session/default
catalogue modifiable
Description
Default catalogue
All catalogue weights are stored in the database in kg. This setting is used in weight
calculations and enables output in lbs, or any other desired units. The options are:
3.4.8
1 (kg) =
output in kg
2.2046 (lbs) =
output in lbs
Other =
Any other weight units. Enter the appropriate conversion factor in the
numeric entry box.
Default value
Session/default
catalogue modifiable
Description
Default catalogue
3.4.9
Default value
Session/default
catalogue modifiable
Description
true
Default catalogue
3:12
12.0
3.4.10
Default value
Session/default
catalogue modifiable
Description
true
Default catalogue
notes
3.5
Miscellaneous Tab
The defaults on the Miscellaneous tab are grouped into three sections: Form Size Control,
Active Icons and Zone ID.
Figure 3:11.
3.5.1
3:13
12.0
3.5.2
Active Icons
Depending on project requirements and conditions, it may be necessary to deactivate
certain icons on the MDS toolbar. This is done by ticking/unticking the appropriate check
boxes, and determines the range of ancillaries that are available during the design process.
3.5.3
Zone ID
The settings within the Zone ID section represent the criteria that the MDS application uses
to select suitable zones for creation of support frameworks. MDS uses the attributes and
values set here to determine (a) the list of zones where MDS support frameworks may be
created, and (b) the zones for the PIPING, HVAC and CABLE TRAY elements where MDS
ancillary supports may be created.
3.6
3.6.1
The items on this form are self explanatory except for Flange Gaps. This function only works
in creation by cursor mode. The setting for this functionality is available by pressing the
Flange Gaps button. This will display the following form:
3:14
12.0
Note: ID1 is the first member identified and ID2 is the second member identified (if
applicable). This can make a significant difference to the structure as shown in the
examples below. The positioning of the framework legs can be used with either the
identified sections or gensecs geometry or the sections or gensecs origin.
The following examples show the effect of selecting the members in different orders. In
Figure 3:13.: ID1 = off, ID2 = off both flange gaps are set to off. In Figure 3:14.: Left first, ID1
= Inside, ID2 = Outside and Figure 3:15.: Right first, ID1 = Inside, ID2 = Outside, ID1 and
ID2 have the same settings but have been selected in different orders. The same is also
true for Figure 3:16.: Left first, ID1 = Inside, ID2 = Off and Figure 3:17.: Right first, ID1 =
Inside, ID2 = Off, resulting in a mirrored structure in both cases.
3:15
12.0
3:16
12.0
4.1
Overview
The MDS Active Control form enables the administrator to change the active state of all
support types in the MDS catalogue. This controls whether the supports will be available for
use on the project by the MDS designer.
Active: Ancillary included in selection lists.
Inactive: Ancillary excluded from selection lists.
Tabs along the top of the form allow the user to select support type and the grid below
displays the corresponding supports. The active status for each support is shown by the
colour of the first column, green for active and red for inactive. Multiple supports can be
selected in the grid and the buttons below allow the user to Activate or Deactivate them
respectively. If a single support is selected, the active status of individual bore sizes can also
be set using the grid on the right-hand side of the form.
Changes made are only applied to the database when the Apply button is clicked. The
Dismiss button closes the form. If changes have been made, but not applied, a window is
displayed asking if the changes are to be applied before exiting.
4.2
4:1
12.0
Figure 4:1.
Modify Menu
If any other forms that have similar functionality are open such as:
Figure 4:2.
Yes: Will close the form and open the MDS Active Control form.
No/Cancel: Will leave the form open and will not open the MDS Active Control form.
If the user selects Yes and changes on that form have been made but not applied the user
my also me asked to apply changes.
4:2
12.0
Figure 4:3.
Yes: Will apply changes before closing the form and opening the MDS Active Control form.
No: Will not apply changes before closing the form and opening the MDS Active Control
form.
Cancel: Will leave the form open and will not open the MDS Active Control form.
The MDS Active Control form will then be displayed.
Figure 4:4.
4.3
Tabs
Along the top of the form are tabs for all the available support types, plus the last tab which
contains all the support types.
There is a button in the top-right corner of the form that allows a key to popup with
descriptions of the support types.
4:3
12.0
Figure 4:5.
4.4
Main Grid
The main grid lists all the supports for the selected support type tab. There are three
columns giving information on the MDS Name, Replacement Name and Description. The
active status of each support is indicated by the colour of the first column:
Green = Activated
Red = Deactivated
The user can multi-select rows in the grid and change their active status by either clicking on
the Activate or Deactivate buttons below the grid or by right-clicking on the grid and
selecting the appropriate command from the menu. There is also a Select All option at the
bottom-left of the grid.
4:4
12.0
Above the grid on the left hand side is a summary displaying the number of active supports.
Changes made are only applied to the database when the Apply button is clicked. The
Dismiss button closes the form. If changes have been made, but not applied, a window is
displayed asking if the changes are to be applied before exiting.
4.5
Side Grid
The grid on the right-hand side lists all the available bores for the selected support. This grid
is shown if only one support is selected in the main grid and this support has individual bore
sizes.
Figure 4:6.
The user can multi-select rows in the grid and change their active status by either clicking on
the Activate or Deactivate buttons below the grid or by right-clicking on the grid and
selecting the appropriate command from the menu. There is also a Select All option at the
bottom-left of the grid.
Changes made are only applied to the database when the Apply button is clicked. The
Dismiss button closes the form. If changes have been made, but not applied, a window is
displayed asking if the changes are to be applied before exiting.
4.6
Right-Click Menu
Right-clicking on either the main grid or the side grid will show a popup menu.
4:5
12.0
Figure 4:7.
Right-Click Menu
4.7
Figure 4:8.
4:6
12.0
5.1
Overview
The MDS Ancillary Defaults form contains the design parameter definitions for all the
ancillary support components that can be modelled using design parameters in the MDS
catalogue. It allows the administrator to define the physical dimensions of all the ancillaries
to match a given vendor. The supplied parameters are generally based on, but not
exclusively:
Carpenter & Paterson Ltd
Pipe Suspension Equipment Catalogue No. 7/94
References to the supplier figure numbers are provided on the relevant section of the form.
The form also provides material descriptions. The forms allows the administrator to set
minimum and maximum design values associated with certain attributes of the ancillary, and
contains information used during Material Take Off (MTO) extraction by the MDS Automatic
Drawing Production application.
The component descriptions can also contain rules that modify the geometry of the
component in certain situations, e.g. by adding stiffening webs for pipe shoes where the
height of the shoe exceeds a given value.
Changes made are only applied to the database when the Apply button is pressed. The
Dismiss button removes the form. If changes have been made, but not applied, a window is
displayed asking if the changes are to be applied before exiting.
5.2
5:1
12.0
Figure 5:1.
5.3
Standard Tab
The left hand side of the form lists the available MDS ancillary support standards.
Hanger and trunnion support types are described in MDS Hanger Data Form and MDS
Trunnion Defaults Form.
MDS lighting support types are described in section MDS Lighting Support Defaults.
MDS Structural Framework Support types are described in section MDS Structure Defaults
Form.
The buttons below the list provide filtering on specific support types.
When a support type is highlighted, the support standard name, its replacement name and
description appear at the top of the form (described below). This information is outside of
the tabbed areas and is displayed on all tabs.
The plotfile for the selected standard is displayed on the right of the form. To zoom in on an
area of the plotfile, click and drag with the middle mouse button. To restore the original size,
use the right-click menu and select Reset Limits.
The information on the form is grouped into two sections. Design detail in the Standard
section applies to all signs of the component. The Bore Specific section contains data
associated with the specified size (bore) of component.
The Apply button should be used before selecting another standard, otherwise any
changes will be lost.
5:2
12.0
5.3.1
Support Standard
The support type selected in the list is copied here, and cannot be changed. The Support
Standard is the code used internally within the software by the MDS application.
5.3.2
5.3.3
Description
The text in this field is configurable to suit each design project, and is only displayed to the
user in the DESIGN module during the creation of supports. The description in this field
does not affect any associated Material Take Off (MTO) details output in MDS Automatic
Drawing Production, as these details are stored in the MDS catalogue database.
The following defaults are located in the Standard section of the form:
5.3.4
Active
This option enables the administrator to specify which of the available ancillaries will be
available for use on the project by the MDS designer, as follows:
True =
False =
This Active setting overrides any subsequent Active setting shown on the Active/Shop Flag
tab (Figure 5:5.: MDS Ancillary Defaults - Active/Shop Flag Tab).
5.3.5
Vendor Reference
Details the vendor figure number associated with the component build parameters that are
detailed on the MDS Ancillary Defaults form.
5.3.6
Elevation Restriction
Specifies the elevation (height) at which an ancillary can be created at. For example, setting
a value of 5000 means the ancillary can be created at any elevation up to and including
5000mm. If a value of -1000 is entered, the ancillary can be created at any elevation below
1000mm.
The default setting is *, meaning there is no restriction on the elevation at which the ancillary
can be created.
5.3.7
CS Carbon Steel
SS Stainless Steel
5:3
12.0
FG Fibre Glass
GV Galvanised
PL Plastic
CN Cupro Nickel
ALL represents ANY material, i.e. valid for all pipe specifications.
This text value, e.g. CS, represents the setting stored at a valid PIPE specification, at the
uda :MDSPipeMat, for use by the MDS application. These settings are totally configurable
and NOT restricted to the example values shown here.
5.3.8
5.3.9
False =
The Isometric MTOC Flag overrides any subsequent Shop Flag settings shown on the
Active/Shop Flag Tab (Figure 5:5.: MDS Ancillary Defaults - Active/Shop Flag Tab)
The following defaults are located in the Bore Specific section of the form.
5.3.10
Bore
The size (bore) of the pipe (in mm) is specified by clicking on the up/down arrows. The
following pipe defaults apply to the size of the pipe selected.
5.3.11
5.3.12
5.3.13
5:4
12.0
Additional overlap (clearance) values are stored within the catalogue held dimensional
parameters of the ancillary. The two values cater for different clearances, dependent on the
type of standard framework being created, designated as the Open End and Closed End
clearances, as shown below.
Figure 5:2.
An additional parameter for the ancillaries is used to instruct MDS how the overlap
(clearance) is applied, whether from the centreline or the geometry of the pipe and the
MDS ancillary (e.g. the outside of the pipe). See the example below.
Figure 5:3.
There is also a build style parameter which is held as a user defined attribute (uda) that
specifies the way the support frame dimensions are applied when the frame is built up, i.e.
whether the inside or outside of the steelwork at the closed end is used. This uda is copied
from the support frame template. See the figure below:
5:5
12.0
Figure 5:4.
The Build Style of the MDS Framework is controlled via the uda :MDSBuildStyl at the
STRCTURE element of a MDS Framework template. There are two options, i.e. INSIDE
(default) or OUTSIDE, which currently may only be set via the command line in the MDS
Framework template DESIGN databases.
Note: Changing this uda manually at design instance of the template will have no effect as
it is always copied form the template each time the support frame is modified by the
application.
Limitations
The overlap (clearance) functionality described above has only been added to the following
support frame types:
FT03 to FT15 inclusive
FT35
FT17
FT36
FT18
FT37
FT19
FT38
FT21
FT39
FT25
FT40
FT29
FT42
FT31
FT43
FT32
FT51
FT33
FT56
FT34A, B, C
5:6
12.0
5.4
Figure 5:5.
5.4.1
Active
The setting of these check boxes determines the pipe bore sizes that the selected ancillary
can be attached to.
When Active is true on the Standard tab, all check boxes are ticked (true) by default, but the
administrator can untick boxes as required for the project.
When Active is False on the Standard tab, this setting overrides all the check box settings,
and are treated as False, even if they are ticked (true).
5.4.2
Shop Flag
The setting of these check boxes determines whether the material for a MDS ancillary
appears in the piping isometric material list under the FABRICATION MATERIALS (SHOP
TRUE) or ERECTION MATERIALS (SHOP FALSE) heading of the MTO.
When the Isometric MT0C Flag is true on the Standard tab, all check boxes are ticked
(true) by default, but the Administrator can untick boxes as required for the project.
When the Isometric MTOC Flag is false on the Standard tab, this setting overrides all the
check box settings shown on this tab, and are treated as false, even if they are ticked (true).
5:7
12.0
5.5
Parameters Tab
Figure 5:6.
The Parameters tab displays a table of the design parameters for the selected MDS
ancillary for each bore size. The bore sizes that appear in this table are NOT dependent on
the Active check box settings of the previous tab. The parameters listed here are for display
purposes only (not editable). Parameters are changed in the Size tab.
The width of the columns can be altered by clicking and dragging the vertical column
separator lines.
Selecting a row (by left-clicking) selects that bore size in the Size, Alt Expression and User
Des Pars tabs. For example, when switching to the Size tab, that bore will already be
selected, but can be changed using the Bore selection control.
5:8
12.0
5.6
Size Tab
Figure 5:7.
The Size tab allows all the design parameters for a specific bore size to be edited. The
design parameters listed here correspond to the applicable row of the table in the
Parameters tab.
The description of the design parameters shown in the Size (and Parameter) tabs are taken
from the DTREF of the SCOM of the CATE in the CATA in the MDS-Standards-Supports
(e.g. for an AT01, all the SCOM are collected for /ATTA-AT01). Where the CATE cannot be
found, the descriptions are shown as unset, and the message Cannot collect SCOM
DBREFS and get descriptions is displayed on the status bar. If the CATE is found, but one
or more design parameter descriptions are unset, it is displayed as unset.
When the Apply button is clicked, the changes for the selected bore size will be reflected in
the applicable row of the Parameters tab.
On returning to the Parameters tab, all the changes made can be viewed together. If these
are satisfactory, all the changes can be applied at once to the database by clicking on the
Apply button.
5:9
12.0
5.7
Parameter Tab
Figure 5:8.
The Parameter tab allows a selected design parameter to be changed for a specific bore
size, or range of bore sizes. This corresponds to editing a column of the table in the
Parameters tab.
The design parameter to be edited is selected from the Column drop-down list and the new
value is entered into the Value box. The range of bore sizes that the value is applicable to is
specified using the From Bore and To Bore drop-down lists.
When the Apply button is clicked, the list at the left of the form is updated with the new
value. The changes will also be reflected in the relevant columns of the table in the
Parameters tab. On returning to the Parameters tab, the changes made can be viewed
together. If these are satisfactory, all the changes can be applied at once to the database by
clicking on the Apply button.
5:10
12.0
5.8
Figure 5:9.
The Alt Expression tab provides for alternative expressions and alternative design
parameters for a particular bore. This feature is used to change the geometry of a
component in certain situations.
The MDS application checks the alternative expression each time the component is
modified. if the expression is true, the alternative design parameters to the right of the
expression are used. In the example screenshot above, when design parameter 5 is greater
than 100mm, design parameter 7 is set to 6mm and design parameter 9 is set to 25mm.
This creates stiffeners on the AT01 pipe shoe 6mm thick and located 25mm from each end
of the shoe.
5:11
12.0
5.9
This tab lists the design parameters that the MDS designer can modify during the creation or
subsequent modification of a support. The example screenshot shows component AT01,
bore size 20mm. The designer would only be allowed to modify two of the design
parameters for AT01:
Design Parameter 2 - support length, which has minimum and maximum values of
100mm and 350mm
Design Parameter 5 - support height, which has minimum and maximum values of
50mm and 180mm
When the designer modifies these values using the MDS application, the minimum and
maximum values are checked and a warning message is displayed if any values are outside
their allowable ranges. The administrators must ensure suitable minimum and maximum
values are entered for the design parameters.
In some situations if may be necessary to restrict a user-editable parameter to a single
value. For example, for AT01 with 20mm bore, we may wish to fix the shoe height at 100mm
to match the component available in a given supplier catalogue. In this case the minimum
and maximum values are both set to 100.
5.9.1
5:12
12.0
3. Click on the New User Editable Design Parameter button. A form is displayed asking
you to enter the number of the new design parameter.
Figure 5:11.
Input form
4. Enter the design parameter number (e.g. 1 for Flange Width) and click OK to create the
new user design parameter. The new design parameter appears on the form, with
default minimum and maximum values of 0.
Important: This new design parameter will appear on the form for ALL BORE SIZES in the
standard. Ensure the values required are entered at each bore size.
5. Enter suitable minimum and maximum allowable values for the design parameter as
shown above.
6. Click Apply to apply the changes to the database.
5:13
12.0
5.9.2
3. The selected user design parameter is now deleted from all bores of the MDS Ancillary
standard, as shown Figure 5:10.: MDS Ancillary Defaults - User Des Pars Tab.
4. Click Apply to apply the changes to the database.
5:14
12.0
6.1
Overview
Important: The MDS hanger template configurations displayed in the MDS Hanger Data
form Figure 6:1.: MDS Hanger Data - Standard Tab MUST represent the same
hanger components included in the actual hanger templates defined in the SITE
called /MDS/HANGERS. This holds the modelled hanger templates for each
hanger component manufacturer/supplier in their respective databases. (See
Hangers Design Templates for further information).
The MDS Hanger Data form is used to define the configuration of the MDS hanger
templates. Each hangers configuration can have a replacement name more meaningful to
the MDS designer, and a description to suit a particular design project.
These MDS Hanger templates only apply to the MDS application when the Project Hanger
Interface (MDSHANGIF) default value is set to MDS (see Project Hanger Interface
(MDSHANGIF). Three sets of MDS hanger templates are supplied with the application, one
for each of the hanger components manufacturer/supplier, i.e. PSL, GRINNELL (now
ANVIL) and PIHASA.
Changes made are only applied to the database when the Apply button is clicked. The
Dismiss button removes the form. If changes have been made, but not applied, a window is
displayed asking if the changes are to be applied before exiting.
6.2
6:1
12.0
Figure 6:1.
6.3
Standard Tab
The left hand side of the forms lists the available MDS hanger template types; each type
represents a hanger configuration. There are two basic hanger types: Fixed hangers (FH)
and Variable Hangers (VH).
When a hanger configuration is highlighted, the MDS support standard, its replacement
name and description appear at the top of the form (described below). This information is
outside of the tabbed areas and is displayed on all four tabs,
The plotfiles for all of the selected hanger configurations are displayed on the right of the
form. To zoom in on an area of the plotfile, click and drag with the middle mouse button. To
restore the original size, use the right-click menu and select Reset Limits.
The Apply button should be clicked before selecting another standard, otherwise any
changes will be lost.
6.3.1
Support Standard
The MDS hanger template configuration selected in the list is copied here, and cannot be
changed.
6.3.2
6:2
12.0
The replacement name is based on the hanger configuration, see Hanger Template
Configuration.
6.3.3
Description
The text in this field is configurable to suit each design project, and is only displayed to the
user in the DESIGN module during the creation of supports. The description in this field
does not affect any associated MTOC details output in MDS Automatic Drawing Production,
as these details are stored in the MDS catalogue database.
6.3.4
If it is a variable spring hanger, where is the spring located? Is it below the pipe? Is it
located above the pipe but below the steelwork? Is it located on top of the steelwork?
Is the hanger connected to the pipe using a pipe clamp or to a welded lug?
6.3.5
Active
This option enables the administrator to specify which of the available MDS hanger template
configurations will be available for use on the project by the MDS designer, as follows:
True =
False =
6:3
12.0
6.4
Aliases Tab
Figure 6:2.
This tab is used for viewing hanger template configuration aliases. These configurations use
the same template as the hanger configuration defined in the Alias column, but are handled
differently by the MDS application.
Note: The hanger template configuration in the Alias column is the master template used
by the MDS hanger standard shown in the Standard column.
6:4
12.0
6.5
Figure 6:3.
Where the hanger is supporting a pipe through a lug, ancillary or trunnion, this tab defines
which standard supports can be used for that support.
Click on a component in the Bottom Hanger Types column. Listed in the Support
Standards column are the MDS standard types it may be associated with.
These associations can only be changed using the Command Line Interface.
6:5
12.0
6.6
Figure 6:4.
This tab enables the administrator to view the range of available rod sizes for a given
hanger configuration.
Click on an entry in the Nominal Pipe Size column. The available rod sizes for the selected
bore and hanger configuration are listed in the Allowed Rod Sizes column. These can only
be changed using the Command Line Interface.
6:6
12.0
7.1
Overview
The MDS Structure Defaults form defines which of the available support standards can be
used in a project, and clients replacement support names and descriptions can be specified.
MDS Framework types prefixed FT can be organised into groups, which makes selection of
a framework easier for the MDS designer.
The form also defines which ancillaries will be available to the designer for a particular
framework support.
Alternative codes can be defined to replace the MDS application default codes to suit the
clients standard.
Changes are only applied to the database when the Apply button is clicked. The Dismiss
button removes the form. If changes have been made, but not applied, a window is
displayed asking if the changes are to be applied before exiting.
Note: Only the first three tabs are used in the majority of cases.
7.2
7:1
12.0
Figure 7:1.
7.3
Standard Tab
The left hand side of the form lists the available framework support types. The buttons below
the list provide filtering on specific support types.
When a support type is highlighted, the support standard name, its replacement name and
description appear at the top of the form (described below). This information is outside of
the tabbed areas and is displayed on all tabs.
The plotfile for the selected standard is displayed on the right of the form. To zoom in on an
area of the plotfile, click and drag with the middle mouse button. To restore the original size,
use the right-click menu and select Restore Limits.
The Apply button should be clicked before selecting another standard, otherwise any
changes will be lost.
7.3.1
Support Standard
The support type selected in the list is copied here, and cannot be changed.
7.3.2
7.3.3
Description
The text in this field is configurable to suit each design project, and is only displayed to the
user in the DESIGN module during the creation of supports. The description in this field
7:2
12.0
does not affect any associated Material Take Off (MTO) details output in MDS Automatic
Drawing Production, as these details are stored in the MDS catalogue database.
7.3.4
Active
This option enables the administrator to specify which of the available support standards will
be available for use on the project by the MDS designer, as follows:
7.3.5
True =
False =
7.3.6
Framework Groups
During the creation of a multi-discipline support, prefix FT, the Multi-Discipline Frameworks
form is displayed, from which the MDS designer selects a framework type to create. An
initial selection is done by choosing one of seven framework groups, from which the
required framework is selected. Icons are used to represent the groups, which are as
follows:
L Brackets
Cantilevers/Posts
Pedestals
Frames
Braced Brackets
T Posts
Miscellaneous
These icons are available for selection from the Framework Groups drop-down list.
Selecting an icon associates the selected framework with that group. The groups name is
shown underneath the Framework Groups text.
7.3.7
False =
Note: The settings detailed in Vendor Reference to Isometric MTOC Flag are only available
for certain framework types selected in the list.
7.3.8
Vendor Reference
Details the vendor figure number associated with the component build parameters that are
detailed on the MDS Structure Defaults form.
7:3
12.0
7.3.9
Elevation Restriction
Specifies the elevation (height) at which a support can be created at. For example, setting a
value of 5000 means the support can be created at any elevation up to and including
5000mm. If a value of -1000 is entered, the support can be created at any elevation below
1000mm.
The default setting is *, this means there is no restriction on the elevation at which the
support can be created.
7.3.10
CS Carbon Steel
SS Stainless Steel
FG Fibre Glass
GV Galvanised
PL Plastic
CN Cupro Nickel
ALL represents ANY material, i.e. valid for all pipe specifications.
This text value, e.g. CS, represents the setting stored at a valid PIPE specification, at the
uda :MDSPipeMat, for use by the MDS application. These settings are totally configurable
and NOT restricted to the example values shown here.
7.3.11
7.3.12
False =
The Isometric MTOC Flag overrides any subsequent Shop Flag settings shown on the
Active/Shop Flag Tab (Figure 5:5.: MDS Ancillary Defaults - Active/Shop Flag Tab).
7:4
12.0
7.4
Figure 7:2.
This tab is used to specify what ancillaries are available to the MDS designer during
framework support creation. The fields at the top of the form show which framework is
currently selected (see Standard tab).
The left hand Selections list contains all available MDS ancillaries. The buttons below the
list provide filtering on specific ancillary types. To make an ancillary available, click on the
item in the list then click on the right arrow icon at the side of the list. This transfers the item
to the adjacent list. Clicking on the left arrow icon reverses this action. The * character
represents all MDS ancillary types.
The Restrictions list is used in a similar way, but is for MDS ancillaries that are to be
excluded.
The combination of both of these lists defines the list of MDS ancillary types the designer
can select from. In the example screenshot above, the * in the Selections list means that all
ancillary types are to be made available, but the Restrictions list shows that AN06, AN61
and all LT types are to be excluded from use by the MDS application.
7:5
12.0
7.5
Framework Codes
Figure 7:3.
The Framework Codes tab contains alternative descriptions for the support codes used by
the MDS application. For example, if we take the FT09 support and list some of the possible
support codes, the list will be as follows:
FT09-1-1
FT09-2-1
FT09-3-1
FT09-4-1
FT09-5-1
FT09-6-1
FT09-1-2
FT09-2-2
FT09-3-2
FT09-4-2
FT09-5-2
FT09-6-2
FT09-1-3
FT09-2-3
FT09-3-3
FT09-4-3
FT09-5-3
FT09-6-3
FT09-1-4
FT09-2-4
FT09-3-4
FT09-4-4
FT09-5-4
FT09-6-4
FT09-1-5
FT09-2-5
FT09-3-5
FT09-4-5
FT09-5-5
FT09-6-5
FT09-1-6
FT09-2-6
FT09-3-6
FT09-4-6
FT09-5-6
FT09-6-6
These codes depend on the steelwork size used and the numbers of cross bars. In some
circumstances the clients standard may have a different standard code for different
steelwork sizes but the same configuration. The settings defined here may be used to print
the correct code in the MDS Design module, on the ADP drawing and in the material list of
the piping isometric and output in a MDS Report if required.
For example, if an alternative code of M10A1 is specified for FT09-1-1, the Design, ADP
and isometric applications will replace the FT09-1-1 code with M10A1.
7.5.1
7:6
12.0
If an alternative code is required for an individual support code, it is entered into the
Alternative Code text box, to replace the * character.
7.5.2
Edit Column
An alternative code can be specified for a range of fixed codes, by making appropriate
selections in the From and To drop-down lists. Enter an Alternative Code into the text box to
replace current values stored in the From and To list gadgets.
7:7
12.0
7:8
12.0
8.1
Overview
The MDS Trunnion Data form defines which of the available trunnion types can be used on
a project, and which trunnion bore sizes can be used with each pipe bore.
The form also enables the administrator to specify the pipe sizes that the selected trunnion
can be attached to, and whether the trunnion material type appears on the piping isometric.
The administrator can also select which trunnion base plate standards will be available to
the designer.
Changes are only applied to the database when the Apply button is clicked. The Dismiss
button removes the form. If changes have been made but not applied, a window is displayed
asking if the changes are to be applied before exiting.
8.2
Figure 8:1.
8:1
12.0
8.3
Standard Tab
The left hand side of the form lists the available trunnion support types (TT series). When a
trunnion name is highlighted, its support standard name, replacement name and description
appear at the top of the form (described below). This information is outside of the tabbed
areas and is displayed on all tabs.
The plotfile for the selected standard is displayed on the right of the form. To zoom in on an
area of the plotfile, click and drag with the middle mouse button. To restore the original size,
use the right click menu and select Reset Limits.
The Apply button should be clicked before selecting another trunnion type, otherwise any
changes will be lost.
8.3.1
Support Standard
The trunnion name selected in the list is copied here and cannot be changed.
8.3.2
8.3.3
Description
The text in this field is configurable to suit each design project, and is only displayed to the
user in the DESIGN module during the creation of supports. The description in this field
does not affect any associated Material Take Off (MTO) details output in MDS Automatic
Drawing Production, as these details are stored in the MDS catalogue database.
8.3.4
Active
This option enables the administrator to specify which of the available trunnion types will be
available for use on the project by the MDS designer, as follows:
True =
False =
This Active setting overrides any subsequent Active setting shown on the Active/Shop Flag
tab (see Figure 8:2.: MDS Trunnion Data - Active/Shop Flag Tab).
8.3.5
Vendor Reference
Not applicable.
8.3.6
Elevation Restriction
Specifies the elevation (height) at which an trunnion can be created at. For example, setting
a value of 5000 means the trunnion can be created at any elevation up to and including
5000mm. If a value of -1000 is entered, the trunnion can be created at any elevation below
1000mm.
8:2
12.0
The default setting is *, meaning there is no restriction on the elevation at which the trunnion
can be created.
8.3.7
CS Carbon Steel
SS Stainless Steel
FG Fibre Glass
GV Galvanised
PL Plastic
CN Cupro Nickel
ALL represents ANY material, i.e. valid for all pipe specifications.
This text value, e.g. CS, represents the setting stored at a valid PIPE specification, at the
uda :MDSPipeMat, for use by the MDS application. These settings are totally configurable
and NOT restricted to the example values shown here.
8.3.8
8.3.9
False =
The Isometric MTOC Flag overrides any subsequent SHOP Flag settings shown on the
Active/Shop Flag tab (see Figure 8:2.: MDS Trunnion Data - Active/Shop Flag Tab).
8.3.10
8.3.11
Standard List
The available standards for the trunnion base plate for the selected trunnion type are shown
in the Avail. Standard list.
8:3
12.0
To make a particular standard available to the MDS designer, click on the item in the Avail.
Standard list then click on the left arrow icon on the left side of the list. This transfers the
item to the adjacent Standard list. Clicking on the right arrow reverses this action.
The MDS trunnion type will determine if one or more trunnion base plates are required as
the default. The supplied MDS defaults will take account of this.
8.3.12
Trunnion Sizes
The Trunnion Size is the length of the trunnion from the bottom of the trunnion baseplate,
(not the bearing plate) to the centre of the pipe to which it is welded/clamped.
The minimum and maximum trunnion size for the selected trunnion type and pipe bore can
be set here, as well as the default trunnion size (length).
8.4
Figure 8:2.
8.4.1
Active
The setting of these check boxes determines the pipe bore sizes that the selected trunnion
type can be attached to.
When Active is true on the Standard tab, all check boxes are ticked (true) by default, but the
administrator can untick boxes as required for the project.
When Active is False on the Standard tab, this setting overrides all the check box settings,
and are treated as False, even if they are ticked (true).
8:4
12.0
8.4.2
Shop Flag
The setting of these check boxes determines whether the material for a MDS trunnion
appears in the piping isometric material list under the FABRICATION MATERIALS (SHOP
TRUE) or ERECTION MATERIALS (SHOP FALSE) headings of the MTO.
When the Isometric MTOC Flag is true on the Standard tab, all check boxes are ticked
(true) by default, but the Administrator can untick boxes as required for the project.
When the Isometric MTOC Flag is false on the Standard tab, this setting overrides all the
check box settings shown on this tab, and are treated as false, even if they are ticked.
8.5
8:5
12.0
8:6
12.0
9.1
Overview
The MDS Lighting Support Defaults form allows the administrator to set up the defaults
required by the create lighting support function.
Changes are only applied to the database when the Apply button is clicked. The Dismiss
button removes the form. If any changes have been made but not applied, a window is
displayed asking if the changes are to be applied before exiting. The Reset button cancels
any changes that have been made to the form, but leaves the form displayed for further use.
9.2
Figure 9:1.
9.2.1
Support : Type
The text in this field is used to identify a lighting type support.
9:1
12.0
9.2.2
Support : Code
PML (programmable macro language) string expression giving the support code of the
lighting support that is used for output in Draft or MDS reports.
9.2.3
Supports : Origin
Defines the origin of the support that will be used when positioning the support. Any
positional attribute or p-point reference may be specified.
9.2.4
9.2.5
9.2.6
9.2.7
9.2.8
Lighting : Type
Specifies the item within the design database that represents the lighting equipment that is
to be supported.
9.2.9
Lighting : Filter
This is a PML expression specifying the lighting more precisely.
9.2.10
Lighting : Origin
Specifies the origin of the lighting. When the support is created, its origin will be placed at
the lighting origin. Any positional attributes or p-point reference (e.g. DP1, P2) may be
specified. It should be in the middle of the lighting when viewing from the Z (vertical)
direction.
9.2.11
Lighting : Y Direction
This setting is used during lighting support creation to orient the support so that its Y axis is
aligned with the Y direction of the lighting specified on this form. Any positional attribute,
local axis of lighting (e.g. Y45N) or p-point reference (e.g. DP1 or P1) of the lighting may be
used. Lighting is assured to be in the horizontal plane.
9:2
12.0
10
10.1
Overview
The two default files MDS-REPORT-DEFS and MDS-REPORT-HEADINGS work in
conjunction with each other and Heading numbers must align in both files.
MDS-REPORT-DEFS contains the pre-defined MDS Reports available for the project. The
contents of this file are shown as the output file and description on the MDS Reports Menu
form accessed from Utilities>MDS Reports. The default file contains the details of each
column in each of the pre-defined reports. The administrator can add to, or edit, the default
file to create reports for any project or client specific requirements.
The MDS-REPORT-HEADINGS file contains the definition of a list of Alternative Report
Headings that are applicable to the Reports generated by selecting Utilities>MDS Reports
from the main menu. The contents of MDS-REPORT-HEADINGS manifest themselves on
the MDS Report Headings form. This is accessed by selecting Report>User Defined from
the menu on the MDS Reports Menu form. The administrator can add to, or edit, the default
file to create reports for any project or client specific requirements.
10.2
10:1
12.0
10.2.1
Fields
Description
Output
File
Name
Example
MDS
Support
Summary Index
Summary
1(),2(),3(),4(),
5()
5
List Types
Atta stru
(match(name of
spref,/MDS) eq 1)
and (match(name
of spref,/MDS/.)
neq 1) or
(:MDSsupptype eq
FT22)
Field 1:
The filename on the operating system to which the report will be sent.
Field 2:
The title of the report appearing on the top of the Report.
Field 3:
The required heading numbers as selected from the MDS Report Headings form. This
field also controls the associated column sorting, subtotalling, and totalling options (see
Field 3 Sorting, Totalling and Sub-totalling Options).
Field 4:
The database extraction functions for the required data.
Field 5:
The database element types to be searched for the data required in Field 4.
The parentheses () for each heading contain the sorting and totalling options for each
heading column. These options are described in the following table and have the following
format:
heading_number(totalling/sorting_precedence/sort_ascending/
subtot_sort_col/subtot_values)
10:2
12.0
Parameter
Value
heading_number [REAL]
Refers to the column headers described in the MDS-REPORTHEADINGS file
totalling
[BOOLEAN]
Turns totalling on/off for the column.
TRUE = totalling ON
FALSE = totalling OFF
Default empty field = FALSE
sorting_
precedence
[REAL]
sort_ascending
[BOOLEAN]
[REAL]
If this column is to be subtotalled then this value determines which
sorted column is to be used to determine the subtotalling. Basically
each time the sorted column values change then a subtotal is output in
this column. If this column does NOT require subtotalling then this
value should be ZERO (0)
Default empty field = 0
subtot_values
[STRING]
This option controls when values in this column will be output. There
are two basic options for ALL columns:
ON = column values are always output.
OFF = column values are not output.
However, if this column has subtotalling on, a subtotal value will be
output when the associated subtotal_sort_col column values changes
and triggers a subtotal for this column. There are two additional value
options that are relevant if subtotalling is in effect in the report:
SUB = column values are only output when a subtotal is output in any
column
FIRST = column values are output for the first row in a group of sorted
values. This option can ONLY be used if this column is being sorted
(sort_precedence > 0)
Default empty field = ON
10:3
12.0
The data above appears in the MDS-REPORT-DEFS file in the format shown in Figure
10:1.: Extract from MDS-REPORT-DEFS.
# Output File Name \ Report Title \ Heading Numbers \ Main Report Filter \ List Types
# Field
1>
\
<2>
\
<3>*
\
<4>
\
<5>
MDS Summary\Support Index Summary\1(F/1/T/0/SUB),2(F/2/T/0/SUB),3(F/3/T/0/SUB),4(F/
4/T/0/SUB),5(T/0/T/1/OFF)\((matchwild(name of spref,/MD*/*)) and (match(name of
spref,/MDS/.) neq 1)) or (:MDSsupptype eq FT22)\atta stru
MDS Overall-Index \ Overall Support Index \ 9(F/1/T/0/ON),1(F/2/T/0/ON),4(F/3/T/0/
ON),3,6,7,8 \ (matchwild(name of spref,/MD*/*)) and (match(name of spref,/MDS/.) neq
1) or (SKEY eq BEDP)\ atta stru
MDS Area \ Support Index by AREA \ 9(F/1/T/0/ON),1(F/2/T/0/ON),4(F/3/T/0/
ON),3,6,7,10 \ (matchwild(name of spref,/MD*/*)) and (match(name of spref,/MDS/.) neq
1) \ atta
MDS Bedplate Index \ Bed Plate Index \ 11(F/1/T/0/ON),12(F/2/T/0/ON),13(F/3/T/0/
ON),14(F/4/T/0/ON),15(F/5/T/0/ON) \(:MDSsupptype eq FT22) and (SKEY eq BEDP)\ stru
10.3
Column Details
Read the following information in conjunction with details at the top of MDS-REPORTHEADINGS file.
Note: The Mandatory number of fields/columns is 1 to 9 inclusive.
Column Num
Description
Description
Column
Heading
Expression
PML
Function
Justify
Column
Type/Options
text
text
PDMS
Expression
Example
MDS
Standard
Standard
(after
(name of
spref
,MDS/))
MDSmatma
ncofg
Optional (O) or
Mandatory (M)
Optional
left
Optional
Empty =
left
Column 1:
Text that appears on the Output Report
Column 2:
Text that appears on form MDS Report Headings along side the Heading number
Column 3:
PDMS PML Expression
Column 4:
PML Function enabling interfacing to external programmes
Column 5:
Output Report column text justification
10:4
12.0
Column Num
Description
Client Code
Unset text
Client
Description
Output Data
Type
Type/Options
True(T) /
False(F)
text
True(T) /
False(F)
ASCII (A) /
Numeric (N)
Example
true
Non-found
true
Numeric
Optional (O) or
Mandatory (M)
Optional
Empty = false
Optional
Empty = ---
Optional
Empty = false
Optional
Empty = ASCII
Column 6:
This is the clients Replacement Support Code as defined in file DES-SUPP-DEFS.
Column 7:
This column enables substitute descriptive text to be added into the report for
clarification purposes (like non-found rather than ---)
Column 8:
In some circumstances an office standard may have a different standard code for
different steelwork sizes but the same configuration. The alternative descriptions are
defined in the MDS Structure Defaults Form.
Column 9:
Defines the format of the Output Data giving either a real number or an ASCII string.
The data above appears in the MDS-REPORT-HEADINGS file in the format shown in Figure
10:2.: Extract from MDS-REPORT-HEADINGS.
# M = MANDATORY
# O = OPTIONAL
# Description \ Column Heading \
Expression
\
PML Function
\
Justify Column
\
Client Code
\
Unset Text
\ Client Description
\ Output Data Type
#
<1>
\
<2>
\
<3>
\
<4>
\
<5>
\
<6>
\
<7>
\
<8>
\
<9>
#
<Text>
\
<Text>
\ <PDMS Expression> \ <Name of PML Function> \
<Left,Centre or Right> \ <T, True or F, False> \
<Text>
\ <T, True or F,
False> \<A, ASCII or N, NUMERIC>
# Optional=O \ Mandatory=M
\
Either <3> or <4>=M, but <3> and <4>=O
\
O(Empty Field=Left) \ O(Empty Field=False) \ O(Empty Field= --- \ O(Empty
Field=False) \ O(Empty Field=ASCII)
#
\If True Field<8>=False \
\ If True Field<6>=False\
10:5
12.0
10:6
12.0
11
11.1
Overview
An auto naming facility is available in the project default area, which is common to multiple
users. By default the DES-SUPP-NAMES auto naming file is used, but users can select any
other available auto naming file with the DES-SUPP-NAMES prefix.
11.2
or
2. Select the Settings>MDS AutoNaming menu item and the form in Figure 11:1.: MDS
AutoNaming form is displayed.
11:1
12.0
Figure 11:1.
The AutoNaming form allows the user to select a different Auto Naming file for the session
or to set a different Auto Naming file, stored against the Default Zone, by pressing the Set
AutoNaming File to Default Zone button. The Auto Naming file is stored in a uda named
:MDSAutofile at the Zone level.
The default file uses the concept of a prefix, index, and suffix value. An example of the
contents of the file is shown in Figure 11:2.: Extract from DES-SUPP-NAMES. The
Administrator may change these values or create another file with the DES-SUPP-NAMES
prefix.
# MDS Support Naming File
# Description: Default naming file
#
# The support name will be made up from the following parts
# Prefix
# Index
# Suffix
#
# These values may be expressions which will be evaluated before they are used.
# Last will be the last index used
Prefix \ ( substring (namn of zone,1,9))
Index \ 1001
Suffix \ ( substring (namn of zone,10,1))
IWidth \5
MinIndex \1000
11:2
12.0
MaxIndex\1999
Figure 11:2.
The default file can also use an index that starts at a value named MinIndex and up to a
value called MaxIndex. This allows the user to have a predefined range of support numbers.
Another value stored in this file is called the IWidth. This allows a predefined format for the
support number i.e. when IWidth is set to 5 the support number contains 5 numbers e.g.
PS01234.
11:3
12.0
11:4
12.0
12
12.1
Overview
The standard supports, which are designed using structural sections, are template driven. A
default set of templates, in the database site called /MDS/TEMPLATES, is supplied with the
application. To make changes to templates the Administrator requires READ/WRITE access
to this database.
Each standard support template type has its own zone, below which a maximum of eight (8)
Structural Templates may exist. All of the supplied default templates are based on the
steelwork sections available from the British Standards for Steelwork Sections. Users may
configure the template database to suit any other National Standard for steelwork sections
as required.
For details on how this can be achieved and complete instructions on how to configure the
MDS application Structural Design Templates, please refer to the Framework Template
Administration section of the MDS Customisation Guide.
12:1
12.0
12:2
12.0
13
13.1
Overview
Hangers designed using supplier-specific hanger components are template driven. A default
set of templates, in a SITE called /MDS/HANGERS, is supplied with the application. Each
hanger configurations template has its own ZONE. Each size of a given hangers
configuration is represented by a REST component. Two sets of hanger templates are
supplied with the application, one for each hanger components supplier (GRINNELL and
PSL).
Data sheets
Each hangers configuration, whether fixed, variable, single or double, has an associated
application standard data sheet. For some companies it might be a data sheet for the
available hangers components; in other companies it might be a data sheet for the specific
hangers configuration.
All of the application standard data sheets are accessible to the designer, either via the MDS
- User Guide or from within DESIGN module on the Create and/or Modify Support form(s)
for each support type, via a View... button on the form(s).
To configure templates the Administrator requires read/write access to the hangers design
templates database.
13.2
/MDS/FH**
is used for fixed hangers (e.g. /MDS/FH01).
/MDS/VH**
is used for variable hangers (e.g. /MDS/VH01).
(** denotes a two digits sequence number)
Each zone owns several REST elements. Each REST represents a hangers size for that
configuration. The name of the REST templates has the following format:
/MDS/FH**/pipe_size_in_mm
For example, a REST having the name /MDS/FH01/100 represents a template for a hanger
with a FH01 configuration, used for a 100mm pipe. In some cases the hanger designer may
need different hanger sizes for the same pipe size. A good example of this is when a hanger
13:1
12.0
is attached to a welded elbow lug. The lug may have a range of holes sizes. So, although
the hanger configuration type is the same and the pipe size is the same, a lug with a larger
hole will require a larger pin and a hanger with larger rods. This is handled by adding a oneletter suffix to the name of the REST and is compatible with AVEVAs standard naming
convention used in the hangers catalogue for rod sizes. For example, suffix A is used for an
M6 rod size, B for an M8 rod size etc. A typical template name for such a hanger may be: /
MDS/FH01/100/A. This template is for hangers with the FH01 configuration, connected to a
100mm pipe and having M6 rod size.
For further information about AVEVAs naming convention, refer to the AVEVA Conventions
for Catalogues and Specifications manual.
The range of sizes available for a given hangers configuration, as well as other specific
configuration data, is set when the hangers feature of the MDS application is used for the
first time in a session. The application then scans the MDS hangers template site: /MDS/
HANGERS, reads the zones attributes, and saves it in memory for later use. The range of
available hanger sizes for each configuration is determined from the restraints elements
below the zone.
Each hanger has its own specific design characteristics, as defined in the MDS Hangers
Data form (refer to MDS Hanger Data Form).
13:2
12.0
14
14.1
Overview
MDS uses the standard ABA (Area Based Automatic Drawing Production) facilities to
produce its hanger and framework detail drawings from Draft. Using ABA certain MDS
specific elements have been added into the delivered project (MDS). In summary these are:
MDS specific Sheet Templates (SHTMPLs) and their associated Views Layers and Tasks,
plus some referenced Library (LIBY) elements.
MDS specifics only are documented below. For other details of the administration of ABA
see the MDS Customisation Guide.
One of the principles of ABA is that it works on an area of the database defined by coordinates. MDS-ABA does not make use of this part of the functionality initially but
calculates the area required around a support or hanger and then back-fills the requirement
into the ABA forms.
A sample DRA-MDS-ABA-Defaults file is supplied with MDS default values, as shown
below:
--- ========================================
-- General Defaults For Area Based ADP Use.
-- ========================================
--- Section 1
!!abadefaults.libr.val = '/Aba/graphical_reports_library'
!!abadefaults.dlib.val = '/MDS-Drawing-Templates'
!!abadefaults.alib.val = '/MDS-ABA-Area-Library'
!!abadefaults.disl.val = '/PROJ/ABA/CLASS'
!!abadefaults.keyp.val = '/Aba/keyplans_library'
!!abadefaults.symb.val = '/Aba/symbols_library'
!!abadefaults.labl.val = '/Aba/tag_rule_library'
!!abadefaults.task.val = '/PROJ/ABA/TASK'
!!abadefaults.logf.val = '%PDMSABALOG%'
!!abadefaults.batf.val = '%PDMSABABATCH%'
!!abadefaults.logpath = '%PDMSABALOG%'
!!abadefaults.batpath = '%PDMSABABATCH%'
!!abadefaults.ustring = 'SYSTEM'
!!abadefaults.string
= 'XXXXXX'
!!abadefaults.startbat = '%PDMSABABATCH%\pdmsBatch.bat'
14:1
12.0
--------
End Section 1
=============================================
Permitted View Scales
=============================================
Section 2
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Metric
\MET
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Architectural \ARC
Engineering
\ENG
Engineering
\ENG
Engineering
\ENG
Engineering
\ENG
Engineering
\ENG
Engineering
\ENG
Engineering
\ENG
Engineering
\ENG
-- End Section 2
\1/1
\1/2
\1/3
\1/5
\1/10
\1/20
\1/25
\1/33.1/3
\1/50
\1/75
\1/100
\1/150
\1/200
\1/250
\1/500
\1/1000
\1/1250
\1/2500
\3"
= 1'-0"
\1 1/2" = 1'-0"
\1"
= 1'-0"
\3/4"
= 1'-0"
\1/2"
= 1'-0"
\3/8"
= 1'-0"
\1/4"
= 1'-0"
\3/16" = 1'-0"
\1/8"
= 1'-0"
\1/16" = 1'-0"
\1" = 10'-0"
\1" = 20'-0"
\1" = 30'-0"
\1" = 40'-0"
\1" = 50'-0"
\1" = 60'-0"
\1" = 75'-0"
\1" = 100'-0"
\1 1
\1 2
\1 3
\1 5
\1 10
\1 20
\1 25
\1 33.1/3
\1 50
\1 75
\1 100
\1 150
\1 200
\1 250
\1 500
\1 1000
\1 1250
\1 2500
\3Inch 1'
\1.1/2Inch 1'
\1Inch 1'
\0.3/4Inch 1'
\0.1/2Inch 1'
\0.3/8Inch 1'
\0.1/4Inch 1'
\0.3/16Inch 1'
\0.1/8Inch 1'
\0.1/16Inch 1'
\1Inch 10'
\1Inch 20'
\1Inch 30'
\1Inch 40'
\1Inch 50'
\1Inch 60'
\1Inch 75'
\1Inch 100'
\1
\0.5
\0.333333,0.3333,0.33
\0.2
\0.1
\0.05
\0.04
\0.0303,0.03
\0.02
\0.013333,0.0133,0.013
\0.01
\0.006667,0.0067
\0.005
\0.004
\0.002
\0.001
\0.0008
\0.0004
\0.25
\0.125
\0.083333,0.0833
\0.0625
\0.041667,0.0417
\0.03125 ,0.0313
\0.020833,0.0208
\0.015625,0.0156
\0.010417,0.0104
\0.005208,0.0052
\0.008333,0.0083
\0.004167,0.0042
\0.002778,0.0028
\0.002083,0.002
\0.001667,0.0017
\0.001389,0.0014
\0.001111,0.0011
\0.000833,0.0008
--- =============================================
-- Symbol Templates
-- =============================================
--- Section 3
-- Plan View E/W axis
/Aba/SAM/grids/EW
-- Plan View N/S axis
/Aba/SAM/grids/NS
-- Elevation View EW axis
14:2
12.0
/Aba/SAM/grids/vert_EW
-- Elevation View NS axis
/Aba/SAM/grids/vert_NS
-- North Arrow
/Aba/north_arrow
-- End Section 3
--- =============================================
-- Auto Number Task
-- =============================================
--- Section 4
/Aba/AutoNumber
-- End Section 4
--- =============================================
-- Imperial Paper Sizes
-- =============================================
--- Section 5
A \8.5 11
B \17 11
C \22 17
D \34 22
E \44 34
-- End Section 5
--- =============================================
-- Metric Paper Sizes
-- =============================================
--- Section 6
A0 \1189 841
A1 \841 594
A2 \594 420
A3 \420 297
A4 \297 210
A5 \210 148
-- End Section 6
14.2
14:3
12.0
14.2.1
View Element
The standard VIEW element has two user-defined attributes associated with it that are
significant to MDS. They are:
14.3
:ABAUpdate
:MDSABAOption
14.3.1
Sheet tasks
View tasks
Sheet Tasks
SheetLayout
Task name:
MDS_aba_sheet_task
14:4
12.0
SheetLayout
Function name:
Mdsabasheettask.pmlfnc
Description:
RunData
Task name:
MDS_aba_rundata
Function name:
MdsAbaRunData.pmlfnc
Description:
This task adds run time data of the User, with options of login
Name or User at a predefined location, and text size to the MDS
Detail Sheet.
TitleBlock
Task name:
MDS_aba_titleblock
Function name:
MdsAbaTitleBlock.pmlfnc
Description:
This task adds and positions Drawing Name and Title, View
Scale, and Total Support Weight information to the Detail Sheet,
in the given size and linestyle. Options exist to position the data
explicitly using x-y co-ordinates or cursor input.
SheetComment
Task name:
MDS_aba_comment
Function name:
MDSabacomment.pmlfnc
Description:
This task adds any Support Comment set by the designer during
the Support Creation sequence. It is positioned at the bottom of
the MTO Table on the Sheet.
Support type
Task name:
MDS_aba_supptype
Function name:
MDSabasupptype.pmlfnc
Description:
14:5
12.0
Support code
Task name:
MDS_aba_suppcode
Function name:
MDSabasuppcode.pmlfnc
Description:
MDS_aba_overlay
Function name:
MDSabaoverlay.pmlfnc
Description:
14.3.2
View tasks
MainView
Task name:
MDS_aba_view_task
Function name:
MDSabaviewtask.pmlfnc
Description:
MDS_aba_location_plan_task
Function name:
MDSabalocplan.pmlfnc
Description:
Gets the nearest Gridline for location and adds to the View
14:6
12.0
MDS_aba_mtosteel
Function name:
MDSabamtosteel.pmlfnc
Description:
MDS_aba_mtocomp
Function name:
MDSabamtocomp.pmlfnc
Description:
MDS_aba_ancil_tags
Function name:
MDSabaanctags.pmlfnc
Description:
MDS_aba_steel_tags
Function name:
MDSabasteeltags.pmlfnc
Description:
MDS_aba_ix_joint_tags
Function name:
MDSabasteeltags.pmlfnc
Description:
14:7
12.0
MDS_aba_iso_view_axes
Function name:
MDSabaisoview.pmlfnc
Description:
Support data
Task name:
MDS_aba_supp_data
Function name:
MDSabasuppdata.pmlfnc
Description:
MDS_aba_weld_tags
Function name:
MDSabaweldtags.pmlfnc
Description:
MDS_aba_ubolt_hole_tags
Function name:
MDSabaubolttags.pmlfnc
Description:
14:8
12.0
15
15.1
Overview
The MDS application allows the MDS Administrator to create a set of ancillary standards
with their own geometry. Configuration of standards dimensionally is covered in MDS
Ancillary Defaults Form.
The term user in this section is the term used to represent client/customer.
The user defined ancillary standards comprise a number of support types. The following
table shows the user defined ancillary types that have been created and which can be
configured geometrically:
Standard
Description
Range
Total
From
To
AT
Ancillary
AT500
AT700
201
LT
Lug
LT500
LT700
201
BT
U-Bolt
BT500
BT700
201
AN
AN500
AN569
70
AN
AN570
AN639
70
AN
AN640
GT700
61
GT
GT500
GT569
70
GT
GT570
GR639
70
GT
GT640
GT700
61
ST
ST500
ST569
70
ST
ST570
ST639
70
ST
ST640
ST700
61
The ability to create these user defined ancillary types is achieved by MDS being configured
to use a blank set of ancillaries of the above types, so that users can complete their own
geometry. A new MDS user project called MDU has been created; a hierarchy /MDU prefix
is used instead of the /MDS prefix where applicable. The following diagrams shows how this
is implemented into an MDS project environment.
15:1
12.0
The MDU project has the geometry and point sets pre-created and linked into the MDS
catalogue and specification. The geometry sets are empty and the point sets have the
minimum p-point requirements for MDS. 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 in Overview.
15.2
Geometry Sets
The geometry sets have been created in project MDU. The following diagrams show what
has been added and detail any properties that are being used. The MDS Administrator can
add geometry using these properties if needed and add additional properties as necessary.
AT500 to AT700, BT500 to BT700, LT500 to LT700
Simple Box Representation
15:2
12.0
This is set to a length of 10, and uses the pipe outside diameter (OD) as the x and y length.
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following are the parameters that have been preset, i.e. to -1. All other design
parameters are set to 0 (zero), as shown in the form displayed above.
Number
Description
Dkey
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
15:3
12.0
AN500 to AN569
Anchor for Shoes
Simple Anchor Representation
These user standards will ask for a pipe shoe to be identified so it will read the shoe
parameters HEI (shoe height) and WID (flange width) in order to size the anchor. It will then
ask for a section or box to be identified to read the anchor width across the section of box.
15:4
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset, i.e. to -1, 100, 102 and 165. All
other design parameters are set to 0 (zero), as shown in the form displayed above.
Number
Description
Dkey
HEI
WID
SBFW
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
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 as shown.
AN570 to AN639
Anchor for Pipes
Simple Box Representation
15:5
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset i.e. to -1. All other design
parameters are set to 0 (zero), as shown in the form displayed above.
Number
Description
Dkey
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
15:6
12.0
These user standards will ask for a pipe shoe to be identified so it will read the shoe
parameters HEI (shoe height) and WID (flange width) in order to size the guide.
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
15:7
12.0
The following list the parameters that have been preset, i.e. to -1, 100 and 102. All other
design parameters are set to 0 (zero), as shown in the form displayed above.
Number
Description
Dkey
HEI
WID
Clearance
CLR
Length
LEN
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
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 as shown.
GT570 to GT639
Guide for Pipes
Simple Guide Representation
15:8
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset, i.e. to -1 and 0. All other design
parameters are set to 0 (zero), as shown in the form displayed above.
Number
Description
Dkey
Height
HEI
Width
WID
Clearance
CLR
Length
LEN
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
15:9
12.0
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 as shown.
ST500 to ST569
Stop for Shoes
Simple Stop Representation
15:10
12.0
These user standards will ask for a pipe shoe to be identified so it will read the shoe
parameters HEI (shoe height) and WID (flange width) in order to size the anchor. It will then
ask for a section or box to be identified to read the anchor width across the section of box.
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset, i.e. to -1, 100 102 and 165. All other
design parameters are set to 0 (zero), as shown in form displayed above.
Number
Description
Dkey
HEI
WID
SBFW
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
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 as shown.
ST570 to ST639
Stop for Pipes
Simple Box Representation
15:11
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset, i.e. to -1. All other design
parameters are set to 0 (zero) as shown in the form displayed above.
Number
Description
Dkey
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
AN640 to AN700
Anchor for Trunnions
Simple Anchor Representation
15:12
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset. The plate length (PLEN), plate
15:13
12.0
width (PWID) and plate thickness (PTHK) will be obtained from the identified base plate, i.e.
to -1. All other design parameters are set to 0 (zero) as shown in the form displayed above.
Number
Description
Dkey
Plate Length
PLEN
Plate Width
PWID
Plate Thickness
PTHK
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
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 as shown.
ST640 to ST700
Stop for Trunnions
Simple Stop Representation
15:14
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset. The plate length (PLEN), plate
width (PWID) and plate thickness (PTHK) will be obtained from the identified base plate. All
other design parameters are set to 0 (zero) as shown in the form displayed above.
Number
Description
Dkey
Plate Length
PLEN
Plate Width
PWID
Plate Thickness
PTHK
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
15:15
12.0
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 as shown.
GT640 to GT700
Guide for Trunnions
Simple Guide Representation
15:16
12.0
The three standard catalogue parameters have been added, nominal bore (NB), outside
diameter (OD) and connection type (CONN) and 25 design parameters have been created.
The following list the parameters that have been preset. The plate length (PLEN), plate
width (PWID) and plate thickness (PTHK) will be obtained from the identified base plate. All
other design parameters are set to 0 (zero) as shown in the form displayed above.
Number
Description
Dkey
Plate Length
PLEN
Plate Width
PWID
Plate Thickness
PTHK
22
Minimum Insulation
MNIN
23
Maximum Insulation
MXIN
24
Minimum Temperature
MINT
25
Maximum Temperature
MAXT
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 as shown.
15.3
Point Sets
These have been created with the minimum points required by MDS. These are:
P-Point
Description
Arrive Point
Leave Point
Bottom of Pipe (BOP) -5mm, i.e. bottom of the ancillary geometry -5mm
10
Left of Pipe
11
Right of Pipe
12
BOP
The diagram below shows the position and directions of the p-points, P1 and P2 are arriving
and leave points along the centreline of the pipe.
15:17
12.0
Note: The MDS default p-points provided cannot be deleted or modified, but additional ppoints can be created if required.
15.4
Data Sets
These have been created with the minimum number of elements required by MDS. These
are:
Data Name
Description
DataKey DefaultProperty
/Prefix-DESC
DESC
'AT500'
/Prefix-RNAM
MDS Standard
Replacement Name
RNAM
/Prefix-PA1
Nominal Bore
NB
PARA 1
/Prefix-PA2
Outside Diameter
OD
PARA 2
/Prefix-PA3
Connection Type
CONN
PARA 3
15:18
12.0
Data Name
Description
DataKey DefaultProperty
/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
/Prefix-CODE
Support Code
CODE
/Prefix-CDES
MDS Configurable
Description
CDES
/Prefix-DP1
Design Parameter 1
Unset
DESP[1]
15.5
Description
Current Range
MDS Project
User Range
MDS Project
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
15:19
12.0
The MDU project catalogue hierarchy has been created as above for a size range of 8mm
(1/4") to 1200mm (48") in the bore sizes shown below:
Metric NB
Imperial NB
Actual OD
PDMS OD
1/4
13.7
14
15
3/8
21.3
21
20
1/2
26.7
26
25
33.4
33
32
1.1/4
42.2
42
40
1.1/2
48.3
48
50
60.3
61
65
2.1/2
73
73
80
88.9
89
100
114.3
115
125
141.3
141
150
168.3
169
200
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
15:20
12.0
15.6
Metric NB
Imperial NB
Actual OD
PDMS OD
1150
46
1168
1168
1200
48
1219
1219
(Catalogue Reference)
PTREF
GMREF
DTREF
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.
15:21
12.0
15:22
12.0
16
16.1
Overview
Users can use their own plotfiles, including logos and client-specific information instead of
the MDS plotfiles.
To do this, put the user plots into a parallel file structure, and then get MDS to search in the
user area before the AVEVA area. Set the search path on the MDSPLOTS environment
variable, which is set in the evars.bat batch file.
Example:
Setenv MDSPLOTS S:\AVEVA\MDS12.0.0\user_plots S:\AVEVA\pdmsui\des\mds\plots
16:1
12.0
16:2
12.0
A.1
Plotfiles
Each plotfile used by MDS is located in the following directory:
{Software Location}/MDS?.?.?/PDMSui/des/MDS/plot.
Plotfiles can be viewed and printed using AVEVAs plot viewer software (Figure A:1.: PDMS
Plot Viewer).
Figure A:1.
A:1
12.0
A.2
Associated Ancillaries
The following standards are available in the MDS application, but are automatically created
when creating an Ancillary Standard (see Ancillaries for more information).
The standards marked with a * are not available in the MDS application. These standards
are obsolete and have been replaced by other new standards.
MDS Standard
Name
Replacement
Name
Default Description
AC01*
XAC01
AC02*
XAC02
AC03*
XAC03
Turnbuckle.
AC04*
XAC04
Clevis.
AC05*
XAC05
AC06*
XAC06
AC07*
XAC07
Welding lug.
AC08*
XAC08
Clevis plate.
AC09*
XAC09
Spherical washer.
AC10
XAC10
AC11*
XAC11
AC12*
XAC12
AC13*
XAC13
AC14*
XAC14
AC15*
XAC15
AC16*
XAC16
Riser clamp.
AC17
XAC17
AC18
XAC18
Base Plate
AC19
XAC19
Bearing Plate
AC20
XAC20
Collar
AC21
XAC21
AC22
XAC22
AC24
XAC24
Reinforcing Pad
AC25
XAC25
AC27
XAC27
AC28
XAC28
AC29
XAC29
A:2
12.0
A.3
MDS Standard
Name
Replacement
Name
Default Description
AC30
XAC30
Adjustable Baseplate
AC31
XAC31
AC32
XAC32
AC33
XAC33
AC34
XAC34
Reinforcing Pad
AC35
XAC35
Pipe Clamp
AC36
XAC36
U Strap
AC37
XAC37
AC38
XAC38
Guide Trunnions
AC39
XAC39
AC40
XAC40
AC41
XAC41
AC44
XAC44
AC45
XAC45
AC46
XAC46
AC47
XAC47
AC48
XAC48
AC49
XAC49
AC50
XAC50
AC51
XAC51
AC52
XAC52
AC53
XAC53
AC54
XAC54
AC55
XAC55
AC56
XAC56
AC57
XAC56
Adjustable Baseplate
AC58
XAC58
AC59
XAC59
Anchors
The following standards are available in the MDS application.
A:3
12.0
The standards marked with a * are not available in the MDS application. These standards
are obsolete and have been replaced by other new standards.
See Modifying User Defined Ancillary Geometry for information on User Defined Anchor
Standards.
A.4
MDS Standard
Name
Replacement
Name
Default Description
AN01A*
XAN01A
AN01B*
XAN01B
AN02
XAN02
AN03
XAN03
AN04
XAN04
AN05
XAN05
AN06
XAN06
AN07A
XAN07
AN07B
XAN07
AN07C
XAN07
AN08
XAN08
AN09
XAN09
AN10
XAN10
AN11
XAN11
AN12A
XAN12A
AN12B
XAN12B
AN13
XAN13
AN17
SC47
AN18
SC15
AN19
XAN19
Ancillaries
The following standards are available in the MDS application.
The standards marked with a * are not available in the MDS application. These standards
are obsolete and have been replaced by other new standards.
A:4
12.0
See Modifying User Defined Ancillary Geometry for information on User Defined Ancillary
Standards.
.
MDS Standard
Name
PIPE-REST
XRT01
Pipe Rest
PIPE-RESTINLINE
XRT02
AT01
XAT01
AT02
XAT02
AT03
XAT03
AT04
XAT04
Clamp on pipe shoe for N.B. for pipe Cu-Ni 2" to 20"
AT05
XAT05
AT06
XAT06
AT07
XAT07
AT08
XAT08
AT09
XAT09
AT10A*
XAT10A
AT10B*
XAT10B
AT11A*
XAT11A
AT11B*
XAT11B
AT12
XAT12
AT13
XAT13
AT14
XAT14
AT15
XAT15
AT16
XAT16
AT17
XAT17
AT18
XAT18
AT19
XAT19
AT20
XAT20
A:5
12.0
MDS Standard
Name
AT21
XAT21
AT22
XAT22
AT23
XAT23
AT24
XAT24
AT25
XAT25
AT26
XAT26
AT27
XAT27
AT28
XAT28
AT29
XAT29
AT30
XAT30
AT31
XAT31
AT32
XAT32
Pipe Strap (Lined) for Galv. and S.S Lines NPS 1.1/2 8
AT33A
XAT33A
AT33B
XAT33B
AT33C
XAT33C
AT33D
XAT33D
AT33E
XAT33E
AT33F
XAT33F
AT34A
XAT34A
AT34B
XAT34B
AT34C
XAT34C
AT34D
XAT34D
A:6
12.0
MDS Standard
Name
AT34E
XAT34E
AT34F
XAT34F
AT35
XAT35
AT36
XAT36
AT37
XAT37
AT38
XAT38
AT39
XAT39
AT40A
XAT40A
AT40B
XAT40B
AT40C
XAT40C
AT40D
XAT40D
AT40E
XAT40E
AT40F
XAT40F
AT41A
XAT41A
AT41B
XAT41B
AT41C
XAT41C
AT41D
XAT41D
AT41E
XAT41E
AT41F
XAT41F
AT42
XAT42
AT43
XAT43
A:7
12.0
MDS Standard
Name
AT44
XAT44
AT45
XAT45
AT46
XAT46
AT47
XAT47
AT48
XAT48
AT49
XAT49
AT50
XAT50
AT51
XAT51
AT52A
XAT52A
AT52B
XAT52B
AT52C
XAT52C
AT52D
XAT52D
AT52E
XAT52E
AT52F
XAT52F
AT53A
XAT53A
AT53B
XAT53B
AT54
XAT54
AT55A
XAT55A
AT55B
XAT55B
AT55C
XAT55C
AT56
XAT56
AT57
XAT57
AT58
XAT58
AT59
XAT59
AT60
XAT60
A:8
12.0
MDS Standard
Name
AT61
XAT61
AT62
XAT62
AT63
XAT63
AT64
XAT64
AT65
XAT65
AT66
XAT66
AT67
XAT67
AT68
XAT68
AT69
XAT69
AT70
XAT70
AT71
XAT71
AT72
XAT72
AT73
XAT73
GRE Pipe shoes height 100 to 200 for diam 26" to 40"
AT74A
XAT74A
AT74B
XAT74B
AT75A
XAT75A
AT75B
XAT75B
AT76
XAT76
AT87
XAT87
AT93
XAT93
AT94
XAT94
AT95A
XAT95A
AT95B
XAT95B
AT96
XAT96
AT97
XAT97
AT98
XAT98
A:9
Offset
to
Pipe
Bolts
12.0
MDS Standard
Name
AT99
XAT99
AT100A
XAT100A
AT100B
XAT100B
AT101A
XAT101A
AT101B
XAT101B
AT102
XAT102
Pipe Strap
AT109
XAT109
Pipe Strap
AT103A
2134
AT103B
2134
AT103C
2134
AT103D
2134
AT104A
2136
AT104B
2136
AT105
XAT105
AT108A
49xx11
AT108B
49xx12
AT108C
49xx13
AT108D
49xx14
AT108E
49xx25
AT108F
49xx35
AT108G
49xx45
AT108H
49xx64
AT108AX
49xx11
A:10
12.0
MDS Standard
Name
AT108BX
49xx12
AT108CX
49xx13
AT108DX
49xx14
AT108EX
49xx25
AT108FX
49xx35
AT108GX
49xx45
AT108HX
49xx64
AT111
XAT111
AT112
XAT112
AT113
XAT113
AT114
XAT114
AT115
XAT115
AT116
XAT116
AT117
XAT117
AT118
XAT118
AT119
XAT119
AT120
XAT120
AT121
XAT121
AT122
XAT122
AT123
XAT123
AT124
XAT124
AT125
XAT125
A:11
12.0
A.5
MDS Standard
Name
AT126
XAT126
AT127
XAT127
AT128
XAT128
AT129
XAT129
AT130
XAT130
AT131
XAT131
AT132
XAT132
AT133
XAT133
AT134
XAT134
AT135
XAT135
AT136
XAT136
Branch Reinforcements
The following standards are available in the MDS application.
A.6
MDS Standard
Name
Replacement
Name
Default Description
BR01
XBR01
BR02
XBR02
BR03
XBR03
BR04
XBR04
BR05
XBR05
BR06
XBR06
U bolts
The following standards are available in the MDS application. See Modifying User Defined
Ancillary Geometry for information on User Defined U Bolt Standards.
MDS Standard
Name
Replacement
Name
Default Description
BT01A
XBT01
BT01B
XBT01
BT02
XBT02
A:12
12.0
A.7
MDS Standard
Name
Replacement
Name
Default Description
BT03
XBT03
BT04A
XBT04
BT04B
XBT04
BT04C
XBT04
BT05
XBT05
BT06
XBT06
BT07
XBT07
BT09
XBT09
BT10
XBT10
BT11
XBT11
BT12
XBT12
BT13
XBT13
BT14
XBT14
BT15
XBT15
BT16
XBT16
BT17
XBT17
BT18
XBT18
BT19
XBT19
Cable Clips
The following standards are available in the MDS application.
MDS Standard Name
Replacement
Name
Default Description
RACK-REST
XCA01
Rack Rest
CA02A
XCA02
CA02B
XCA02
Cable Clip
A:13
12.0
A.8
A.9
MDS Standard
Name
Replacement
Name
Default Description
CT01
XCT01
CT02
XCT02
CT03
XCT03
CT04
XCT04
Goal post.
CT05
XCT05
Support frame.
CT06
XCT06
Cantilever bracket.
CT07
XCT07
CT08
XCT08
Replacement
Name
Default Description
DT01
XDT01
DT02
XDT02
DT03
XDT03
DT04
XDT04
Replacement
Name
Default Description
FT01*
XFT01
FT02*
XFT02
Trapeze hanger.
FT03
XFT03
FT04
XFT04
FT05
XFT05
A:14
12.0
MDS Standard
Name
Replacement
Name
Default Description
FT06
XFT06
FT07
XFT07
Post.
FT08
XFT08
Goal post.
FT09
XFT09
Support frame.
FT10
XFT10
FT11
XFT11
FT12
XFT12
FT13
XFT13
Braced bracket.
FT14
XFT14
Cantilever bracket.
FT15
XFT15
Beam supports.
FT16
XFT16
Cantilevered Hangertrue
FT17
XFT17
FT18
XFT18
FT19
XFT19
FT20*
XFT20
FT21
XFT21
FT22
XFT22
Bedplate.
FT23
XFT23
Pedestal support.
FT24
XFT24
Steel sleeper.
FT25
XFT25
Packing piece.
FT26
XFT26
Relief Valve.
FT27
XFT27
Rodding point.
FT28
XFT28
Beam penetration.
FT29
XFT29
FT30
XFT30
FT31
XFT31
FT32
XFT32
FT33
XFT33
FT34A
XFT34A
A:15
from
Steel
for
12.0
MDS Standard
Name
Replacement
Name
Default Description
FT34B
XFT34B
FT34C
XFT34C
FT35
XFT35
FT36
XFT36
FT37
XFT37
FT38
XFT38
FT39
XFT39
FT40
XFT40
FT41
XFT41
FT42
XFT42
FT43
XFT43
FT44
XFT44
FT45
XFT45
FT46
XFT46
FT47
XFT47
FT48A
XFT48A
FT48B
XFT48B
FT48C
XFT48C
FT48D
XFT48D
FT49
XFT49
FT50
XFT50
FT51
XFT51
FT52
XFT52
FT53
XFT53
FT57
XFT57
A:16
12.0
A.11
MDS Standard
Name
Replacement
Name
Default Description
FT58
XFT58
FT59
XFT59
FT60
XFT60
FT61
XFT61
Guides
The following standards are available in the MDS application.
The standards marked with a * are not available in the MDS application. These standards
are obsolete and have been replaced by other new standards. See Modifying User Defined
Ancillary Geometry for information on User Defined Guide Standards.
.
MDS Standard
Name
Replacement
Name
Default Description
GT01
XGT01
GT02
XGT02
GT03
XGT03
GT04*
XGT04
GT05
XGT05
GT06
XGT06
GT07
XGT07
GT08
XGT08
GT09
XGT09
GT10
XGT10
GT11
XGT11
GT12A
XGT12
GT12B
XGT12
GT13
XGT13
A:17
12.0
MDS Standard
Name
Replacement
Name
Default Description
GT14
XGT14
GT15
XGT15
GT16
XGT16
GT17
XGT17
GT18
XGT18
GT19
XGT19
GT20
XGT20
GT21
XGT21
GT22
XGT22
GT23A
XGT23A
GT23B
XGT23B
GT24
XGT24
GT25
XGT25
GT26
XGT26
GT27A
XGT27
GT27B
XGT27
GT28
XGT28
GT29
XGT29
GT38
XGT38
GT39
XGT39
GT40
XGT40
GT44
XGT44
GT45
XGT45
GT46
XGT46
GT47
XGT47
GT48
XGT48
GT49
XGT49
A:18
12.0
MDS Standard
Name
Replacement
Name
Default Description
GT50
XGT50
GT52
XGT52
GT54
XGT54
GT55
XGT55
Replacement Name
Default Description
FH01
FH T1 M1 B1
FH02
FH T1 M1 B2
FH03
FH T1 M1 B5
FH04
FH T1 M1 B6
FH05
FH T1 M2 B1
FH06
FH T1 M2 B2
FH07
FH T1 M2 B5
FH08
FH T1 M2 B6
FH09
FH T3 M2 B1
FH10
FH T3 M2 B2
FH11
FH T3 M2 B5
FH12
FH T3 M2 B6
FH13
FH T1 M1 B7
FH13
FH T1 M1 B9
FH14
FH T1 M2 B7
FH14
FH T1 M2 B9
FH15
FH T4 M1 B1
FH16
FH T4 M1 B2
FH17
FH T4 M1 B5
FH18
FH T4 M1 B6
A:19
12.0
Replacement Name
Default Description
FH19
FH T4 M2 B1
FH20
FH T4 M2 B2
FH21
FH T4 M2 B5
FH22
FH T4 M2 B6
FH23
FH T1 M1 B8
FH24
FH T1 M2 B8
FH25
FH T3 M2 B8
FH26
FH T4 M1 B8
FH27
FH T4 M2 B8
FH28
FH T1 M1 B10
FH29
FH T1 M2 B10
FH30
FH T3 M2 B10
FH31
FH T3 M2 B7
FH31
FH T3 M2 B9
FH51
FH T3 B1
FH52
FH T3 B2
FH53
FH T3 B5
FH54
FH T3 B6
FH55
FH T3 B7
FH55
FH T3 B9
FH56
FH T3 B8
FH57
FH T3 B10
FH58
FH T4 M1 B7
FH58
FH T4 M1 B9
FH59
FH T4 M1 B10
FH60
FH T4 M2 B10
FH61
FH T4 M2 B7
FH61
FH T4 M2 B9
VH01
VH T1 M3 B1
VH02
VH T1 M3 B2
VH03
VH T1 M3 B5
VH04
VH T1 M3 B6
VH05
VH T3 M3 B1
A:20
12.0
Replacement Name
Default Description
VH06
VH T3 M3 B2
VH07
VH T3 M3 B5
VH08
VH T3 M3 B6
VH09
VH T9 M1 B1
VH10
VH T9 M1 B2
VH11
VH T9 M1 B5
VH12
VH T9 M1 B6
VH13
VH T9 M2 B1
VH14
VH T9 M2 B2
VH15
VH T9 M2 B5
VH16
VH T9 M2 B6
VH17
VH T10 M1 B1
VH18
VH T10 M1 B2
VH19
VH T10 M1 B5
VH20
VH T10 M1 B6
VH21
VH T10 M2 B1
VH22
VH T10 M2 B2
VH23
VH T10 M2 B5
VH24
VH T10 M2 B6
VH25
VH T1 M3 B7
VH25
VH T1 M3 B9
VH26
VH T3 M2 B14
VH27
VH T3 M3 B7
VH27
VH T3 M3 B9
VH28
VH T9 M1 B7
VH28
VH T9 M1 B9
VH29
VH T9 M2 B7
VH29
VH T9 M2 B9
VH30
VH T10 M1 B7
VH30
VH T10 M1 B9
VH31
VH T10 M2 B7
VH31
VH T10 M2 B9
VH32
VH T4 M3 B1
A:21
12.0
Replacement Name
Default Description
VH33
VH T4 M3 B2
VH34
VH T4 M3 B5
VH35
VH T4 M3 B6
VH36
VH T13 M1 B1
VH37
VH T13 M1 B2
VH38
VH T13 M1 B5
VH39
VH T13 M1 B6
VH40
VH T13 M2 B1
VH41
VH T13 M2 B2
VH42
VH T13 M2 B5
VH43
VH T13 M2 B6
VH44
VH T14 M1 B1
VH45
VH T14 M1 B2
VH46
VH T14 M1 B5
VH47
VH T14 M1 B6
VH52
VH T1 M3 B8
VH53
VH T3 M3 B8
VH54
VH T4 M3 B8
VH55
VH T9 M1 B8
VH56
VH T9 M2 B8
VH57
VH T10 M1 B8
VH58
VH T10 M2 B8
VH59
VH T13 M1 B8
VH60
VH T13 M2 B8
VH61
VH B15
VH62
VH B16
VH63
VH T1 M1 B13
VH64
VH T1 M2 B13
VH65
VH T3 M2 B13
VH66
VH T4 M1 B13
VH67
VH T4 M2 B13
VH68
VH T1 M3 B10
VH69
VH T3 M3 B10
A:22
12.0
Replacement Name
Default Description
VH70
VH T4 M3 B10
VH71
VH B17
VH80
VH T1 M3 B11
VH81
VH T3 M3 B11
VH82
VH T4 M3 B11
VH83
VH T9 M1 B11
VH84
VH T9 M2 B11
VH85
VH T10 M1 B11
VH86
VH T10 M2 B11
VH87
VH T13 M1 B11
VH88
VH T13 M2 B11
VH89
VH T14 M1 B11
VH101
VH T3 B13
VH102
VH T3 B14
VH103
VH T1 M1 B14
VH104
VH T4 M1 B14
VH105
VH T9 M1 B10
VH106
VH T10 M1 B10
VH107
VH T13 M1 B10
VH108
VH T14 M1 B10
VH109
VH T13 M1 B7
VH109
VH T13 M1 B9
VH110
VH T14 M1 B7
VH110
VH T14 M1 B9
VH111
VH T14 M1 B8
VH113
VH T9 M2 B10
VH114
VH T10 M2 B10
VH115
VH T13 M2 B10
VH117
VH T13 M2 B7
VH117
VH T13 M2 B9
VH118
VH T4 M2 B14
VH120
VH T1 M2 B14
A:23
12.0
Replacement Name
Default Description
VH121
VH T4 M3 B7
VH121
VH T4 M3 B9
A.14 Lugs
The following standards are available in the MDS application. See Modifying User Defined
Ancillary Geometry for information on User Defined Lug Standards.
MDS Standard
Name
Replacement
Name
Default Description
LT01A
XLT01A
LT01B
XLT01B
LT01C
XLT01C
LT02
XLT02
LT03A
XLT03
LT03B
XLT03
LT03C
XLT03
LT03D
XLT03
LT04
XLT04
A:24
12.0
MDS Standard
Name
Replacement
Name
Default Description
LT05A
XLT05
LT05B
XLT05
LT05C
XLT05
LT05D
XLT05
LT05E
XLT05
LT05F
XLT05
LT05G
XLT05
LT05H
XLT05
LT06
XLT06
Single Support Bracket Reinforced Vertical Pipe (CuNi Pipes) NPS 2-24
LT07
XLT07
LT08A
XLT08
LT08B
XLT08
LT08C
XLT08
LT08D
XLT08
LT08E
XLT08
LT08F
XLT08
LT08G
XLT08
LT08H
XLT08
LT09
XLT09
LT10
XLT10
A:25
12.0
MDS Standard
Name
Replacement
Name
Default Description
LT11
XLT11
LT12
XLT12
LT13A
XLT13A
LT13B
XLT13B
LT14A
XLT14A
LT14B
XLT14B
LT15
XLT15
LT16A
XLT16A
LT16B
XLT16B
LT17
XLT17
Replacement
Name
Default Description
PR01
ANCHOR
Preliminary Anchor
PR02
GUIDE
Preliminary Guide
PR03
CONSTANT
PR04
FIXED
PR05
VARIABLE
PR06
HOLD-DOWN
PR07
REST
Preliminary Rest
PR08
STOP
Preliminary Stop
PR09
xxxx
Preliminary xxxx
PR10
xxxx
Preliminary xxxx
A:26
12.0
MDS Standard
Name
Replacement
Name
Default Description
PR11
xxxx
Preliminary xxxx
PR12
xxxx
Preliminary xxxx
PR13
xxxx
Preliminary xxxx
PR14
xxxx
Preliminary xxxx
PR15
xxxx
Preliminary xxxx
PR16
xxxx
Preliminary xxxx
PR17
xxxx
Preliminary xxxx
PR18
xxxx
Preliminary xxxx
PR30
xxxx
Preliminary xxxx
A.16 Stops
The following standards are available in the MDS application. See Modifying User Defined
Ancillary Geometry for information of User Defined Stop Standards.
MDS Standard
Name
Replacement
Name
Default Description
ST01
XST01
ST02
XST02
ST03
XST03
ST04
XST04
ST05
XST05
ST06
XST06
ST07
XST07
ST08
XST08
ST09A
XST09A
ST09B
XST09B
ST10A
XST10A
ST10B
XST10B
ST11A
XST11A
ST11B
XST11B
ST12
XST12
A:27
12.0
MDS Standard
Name
Replacement
Name
Default Description
ST13A
XST13A
ST13B
XST13B
ST14
XST14
ST15
XST15
ST16
XST16
ST20
XST20
Shoe Stop
ST24A
XST24A
ST24B
XST24B
ST24C
XST24C
ST24D
XST24D
ST30
XST30
ST31
XST31
ST32
XST32
ST33
XST33
ST34
XST34
ST36
XST36
ST37
XST37
ST38
XST38
A:28
12.0
Replacement
Name
Default Description
SU01A1
XSU01
SU01A2
XSU01
SU01A3
XSU01
SU01A4
XSU01
SU01B1
XSU01
SU01B2
XSU01
SU01B3
XSU01
SU01B4
XSU01
SU01C1
XSU01
SU01C2
XSU01
SU01C3
XSU01
SU01C4
XSU01
SU02A1
XSU02
SU02A2
XSU02
SU02A3
XSU02
SU02A4
XSU02
SU02B1
XSU02
SU02B2
XSU02
SU02B3
XSU02
SU02B4
XSU02
SU02C1
XSU02
SU02C2
XSU02
SU02C3
XSU02
SU02C4
XSU02
SU03
XSU03
SU04
XSU04
A.18 Trunnions
The following standards are available in the MDS application.
A:29
12.0
The standards marked with a * are not available in the MDS application. These standards
are obsolete and have been replaced by other new standards.
MDS Standard
Name
Replacement
Name
Default Description
TT01*
XTT01
TT02*
XTT02
TT03*
XTT03
TT04
XTT04
TT05
XTT05
TT06
XTT06
TT07
XTT07
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
TT11
XTT11
TT12
XTT12
TT13
XTT13
TT14
XTT14
TT15
XTT15
TT16
XTT16
TT17
XTT17
TT18
XTT18
TT19
XTT19
TT20
XTT20
TT21
XTT21
TT22
XTT22
TT23
XTT23
TT24
XTT24
TT25
XTT25
TT26
XTT26
A:30
12.0
MDS Standard
Name
Replacement
Name
Default Description
TT27
XTT27
TT28
XTT28
TT29
XTT29
TT30
XTT30
TT31
XTT31
TT32
XTT32
TT33
XTT33
TT34
XTT34
TT35
XTT35
TT36
XTT36
TT37
XTT37
TT38
XTT38
TT39
XTT39
TT40
XTT40
TT41
XTT41
Replacement
Name
Default Description
VT01
XVT01
VT02
XVT02
VT03
XVT03
VT04
XVT04
VT05
XVT05
VT06
XVT06
VT07
XVT07
VT08
XVT08
VT09
XVT09
VT10
XVT10
A:31
12.0
MDS Standard
Name
Replacement
Name
Default Description
VT11
XVT11
VT12
XVT12
VT13
XVT13
VT14
XVT14
VT15
XVT15
VT16
XVT16
VT17
XVT17
VT18
XVT18
VT19
XVT19
VT20
XVT20
VT21
XVT21
VT22
XVT22
VT23
XVT23
VT24
XVT24
A:32
12.0
Index
Active
allowed pipe bores for trunnion . . . . 8:4
available ancillaries . . . . . . . . . . . . . 5:3
available framework standards . . . . . 7:3
available hanger configurations . . . . 6:3
available pipe bores . . . . . . . . . . . . . 5:7
available trunnion types . . . . . . . . . . 8:2
Active Icons . . . . . . . . . . . . . . . . . . . . . . 3:14
Administrators Role . . . . . . . . . . . . . . . . 1:1
Aliases
hanger configuration . . . . . . . . . . . . . 6:4
Allowed rod sizes
hangers . . . . . . . . . . . . . . . . . . . . . . 6:6
Alternate Representation Level . . . . . . . 3:10
Alternative Expression . . . . . . . . . . . . . 5:11
Anchors
standards . . . . . . . . . . . . . . . . . . . . . A:3
Ancillaries
standards . . . . . . . . . . . . . . . . . . . . . A:4
Ancillary support standards . . . . . . . . . . . 5:2
Associated Ancillaries
standards . . . . . . . . . . . . . . . . . . . . . A:2
Auto Naming default files . . . . . . . . . . . 11:1
Cable Clips
standards . . . . . . . . . . . . . . . . . . . . A:13
Cable Tray Framework Supports
standards . . . . . . . . . . . . . . . . . . . . A:14
Closed End Clearance . . . . . . . . . . . . . . 5:4
Create . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
B
Bore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4
Bore size . . . . . . . . . . . . . . . . . 5:7, 5:9, 5:10
Bottom associated support standards
hangers . . . . . . . . . . . . . . . . . . . . . . 6:5
Branch Reinforcements
standards . . . . . . . . . . . . . . . . . . . . A:12
D
Data Sets . . . . . . . . . . . . . . . . . . . . . . 15:18
Dataset Code Conversion Factor . . . . . 3:12
Default forms . . . . . . . . . . . . . . . . . . . . . 1:1
Default text files . . . . . . . . . . . . . . . . . . . 1:1
Description
ancillary support standard . . . . . . . . 5:3
framework standard . . . . . . . . . . . . . 7:2
hanger configuration standard . . . . . 6:3
trunnion standard . . . . . . . . . . . . . . . 8:2
Design parameter definitions . . . . . . . . . 5:1
Design Parameters
user editable . . . . . . . . . . . . . . . . . 5:12
Design parameters . . . . . . . . . 5:8, 5:9, 5:10
Determine if Notes Appear on Isometric Drawing
3:13
Display Orientation in Support Tag on Isometric
3:12
Drawing production
MDS specific sheet template libraries 14:3
MDS specific tasks . . . . . . . . . . . . 14:4
sheet tasks . . . . . . . . . . . . . . . . . . . 14:4
view tasks . . . . . . . . . . . . . . . . . . . 14:6
Drawing Production Defaults . . . . . . . . 14:1
Index page 1
12.0
E
Elevation Restriction
ancillary . . . . . . . . . . . . . . . . . . . . . . 5:3
framework . . . . . . . . . . . . . . . . . . . . . 7:4
trunnion . . . . . . . . . . . . . . . . . . . . . . 8:2
F
Flange Gapping Valve . . . . . . . . . . . . . 3:10
Flange Gaps . . . . . . . . . . . . . . . . . . . . . 3:14
Form Size Control . . . . . . . . . . . . . . . . . 3:13
Framework Clearance Option . . . . . . . . . 5:4
Framework Codes . . . . . . . . . . . . . . . . . . 7:6
Framework Groups . . . . . . . . . . . . . . . . . 7:3
Framework MTOC Flag . . . . . . . . . . . . . 7:3
Framework Selections/Restrictions . . . . . 7:5
G
Geometry Sets . . . . . . . . . . . . . . . . . . . 15:2
Guides
standards . . . . . . . . . . . . . . . . . . . . A:17
Hanger configuration
aliases . . . . . . . . . . . . . . . . . . . . . . . 6:4
Hanger Manufacturers Design Interfaces A:24
Hanger Template Configuration . . . . . . . 6:3
Hangers Design Templates . . . . . . . . . 13:1
configuration . . . . . . . . . . . . . . . . . . 13:1
HVAC Framework Supports
standards . . . . . . . . . . . . . . . . . . . . A:14
O
Open End Clearance . . . . . . . . . . . . . . . 5:4
Overview of the MDS Application . . . . . . 1:1
I
Isometric MTOC Flag
ancillary . . . . . . . . . . . . . . . . . . . . . . 5:4
framework . . . . . . . . . . . . . . . . . . . . . 7:4
trunnion . . . . . . . . . . . . . . . . . . . . . . 8:3
J
Joint Offset . . . . . . . . . . . . . . . . . . . . . . . 3:9
L
Lugs
standards . . . . . . . . . . . . . . . . . . . . A:24
M
Max. Horizontal Angle . . . . . . . . . . . . . . . 3:6
Index page 2
12.0
framework . . . . . . . . . . . . . . . . . . . . . 7:4
R
Reports Defaults . . . . . . . . . . . . . . . . . . 10:1
S
Shop Flag
ancillary . . . . . . . . . . . . . . . . . . . . . . 5:7
trunnion . . . . . . . . . . . . . . . . . . . . . . 8:5
Size Tab . . . . . . . . . . . . . . . . . . . . . . . . . 5:9
Slip Units
standards . . . . . . . . . . . . . . . . . . . . A:29
Special Support Number Checker . . . . 3:11
Special Support Number Prefix . . . . . . . 3:11
Special Support Number Unique . . . . . 3:11
Standard list
trunnion base plate . . . . . . . . . . . . . . 8:3
Standard Replacement Name
ancillary . . . . . . . . . . . . . . . . . . . . . . 5:3
framework . . . . . . . . . . . . . . . . . . . . . 7:2
hanger . . . . . . . . . . . . . . . . . . . . . . . 6:2
trunnion . . . . . . . . . . . . . . . . . . . . . . 8:2
Steelwork Overlap . . . . . . . . . . . . . . . . . . 3:4
Stops
standards . . . . . . . . . . . . . . . . . . . . A:27
Structural Design Templates . . . . . . . . . 12:1
Support Standard
ancillary . . . . . . . . . . . . . . . . . . . . . . 5:3
framework . . . . . . . . . . . . . . . . . . . . . 7:2
hanger configuration . . . . . . . . . . . . . 6:2
trunnion . . . . . . . . . . . . . . . . . . . . . . 8:2
Support Standard Icon . . . . . . . . . . . . . . 7:3
V
Vendor Reference
ancillary . . . . . . . . . . . . . . . . . . . . . . 5:3
framework . . . . . . . . . . . . . . . . . . . . 7:3
Vessel Framework Supports
standards . . . . . . . . . . . . . . . . . . . . A:31
W
Weight Unit . . . . . . . . . . . . . . . . . . . . . . 3:12
Z
Zone ID . . . . . . . . . . . . . . . . . . . . . . . . 3:14
T
Transport Prefix . . . . . . . . . . . . . . . . . . 3:11
Transport Text . . . . . . . . . . . . . . . . . . . . 3:11
Trunnion Bore List . . . . . . . . . . . . . . . . . . 8:3
Trunnion Sizes . . . . . . . . . . . . . . . . . . . . 8:4
Trunnions
standards . . . . . . . . . . . . . . . . . . . . A:29
U
U bolts
standards . . . . . . . . . . . . . . . . . . . . A:12
User defined ancillary geometry . . . . . . 15:1
User defined ancillary standards 15:1, 15:21
User Modified Defaults . . . . . . . . . . . . . 3:14
User Plotfiles . . . . . . . . . . . . . . . . . . . . . 16:1
User Warning Angle . . . . . . . . . . . . . . . . 3:8
Index page 3
12.0