MDSAG
MDSAG
MDSAG
Administrator Guide
AVEVA Solutions Limited
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
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, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited 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 Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, 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 Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
MDS Administrator Guide
Revision Sheet
Contents Page
Administrator Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Overview of the MDS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Administrators Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
MDS Catalogue and Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Project Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Anchors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:3
Ancillaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:4
Branch Reinforcements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:12
U bolts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:12
Cable Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:13
Cable Tray Framework Supports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:14
HVAC Framework Supports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:14
Multi-discipline Framework Supports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:14
Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:17
MDS Hanger Templates Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:19
MDS Hangers using Hanger Manufacturers Design Interfaces . . . . . . . . . . . . A:24
Lugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:24
Preliminary Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:26
Stops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:27
Slip Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:29
Trunnions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:29
Vessel Framework Supports for Pipes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:31
1 Introduction
The MDS Administrator Guide is designed to give the administrator guidance on setting
defaults and design limits for the Multi-Discipline Supports (MDS) application, and
configuring the application for specific project requirements.
It also contains details of the support standards available for the MDS application.
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.
The MDS12 application is supplied with an updated copy of the master MDS project
containing the MDS catalogue and specifications. The range of MDS components and bore
sizes stored in the master MDS project catalogue are fixed.
Caution: The master MDS project catalogue and associated specifications must NOT be
modified by the client, as this would compromise the integrity of the MDS application.
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 earlier in this document.
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 Limited can assign project database numbers of 7000 and
above.
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.
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.
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:
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.
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.
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.
Note: The MDS12 Application default values converted and upgraded from the six MDS
11.6 defaults files are all in DATA elements in their own DATASET element.
Shown below is a table depicting which MDS default file is partially or wholly
transferred into which MDS12 PARAGON CATALOGUE element.
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.
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\
MDS12DesignAttaUpgrade\MDS116-to-MDS12-DESIGN-ATTA-UPGRADE-MACRO-
27Aug2009-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>
If an Administrator wants to check the MDS application defaults database against the
standard set of defaults contained in the MDS project click Check Defaults option as
previously displayed.
The tool will check the Administrators defaults database to determine if any default
standards are missing or if any updates to existing standards need to be applied. If any
updates are found then they will be displayed as follows.
In the example shown we can see that the tool has finished checking the defaults database
and determined that there are 4 missing entries for standards that are available in the MDS
catalogue.
If the Administrator wants to add application defaults sets for these missing items click
Update Defaults option which will automatically create the defaults data in the project
defaults database. When it has finished a message window is displayed informing the user
that it has successfully created the required number of additional defaults.
Note: The same process is followed for any updates that need to be made to existing
defaults.
A log file is created during the defaults update which gives more detailed information about
what has been added to the database. The log file is created in the current %PDMSUSER%
directory and is named mdsDefaultsUpdate.log.
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.
This is the slope value above which MDS creates a framework type support perpendicular to
the pipe (see Figure 3:2.: 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:3.: MDSSUPPMS
slope < 1/10).
This value determines the overlap distance for steelwork overlap type joints on the support
frameworks (see Figure 3:6.: MDSSUPPCL and MDSSUPPOV).
This is the maximum allowable overlap that can occur between a support attachment and its
associated supporting steelwork (see Figure 3:5.: MDSPACKMO).
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:6.:
MDSSUPPCL and MDSSUPPOV), For example, if the MDS ancillary default values are not
found.
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:7.: MDSMAXHANG).
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:8.: MDSMAXPIVA
and MDSPIVWARN).
The administrator can define the hanger interfaces that are available for use in DESIGN.
The Default Hanger Interface is selected by the administrator and loaded automatically
when the user enters DESIGN. Only active default hanger interfaces are available from the
drop-down list.
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:8.: 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.
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.
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.
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.
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.
When the check box is ticked, functionality is made available for the user to create unique
support names and reference supports. When the check box is unticked, functionality for the
user to create unique support names and reference supports is disabled.
The unique support naming functionality allows the user to define the name of a newly
created ancillary for the pipe, HVAC or rack when they are being added to a support instead
of using the standard naming convention.
The main purpose of the reference support functionality is to allow the user to add an
existing ancillary to a framework.
For example, if when creating a new framework support there is an ancillary created on
another pipe that the user wishes to add to the framework, the user can select the ancillary
and it becomes part of the framework.
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.
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:
1 (kg) = output in kg
Other = Any other weight units. Enter the appropriate conversion factor in the
numeric entry box.
3.4.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 and
hangers may be created, and (b) the zones for the PIPING, HVAC and CABLE TRAY
elements where MDS ancillary supports may be created.
Note: Any changes made here are temporary, i.e. they apply only to the current session. To
make the changes to the defaults permanent, use the applicable administration
forms.
The items on this form are self explanatory except for Flange Gaps and Compensating
Plates.
This Flange Gaps 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:
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:12.: ID1 = off, ID2 = off both flange gaps are set to off. In Figure 3:13.: Left first, ID1
= Inside, ID2 = Outside and Figure 3:14.: 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:15.: Left first, ID1 = Inside, ID2 = Off and Figure 3:16.: Right first, ID1 =
Inside, ID2 = Off, resulting in a mirrored structure in both cases.
Figure 3:13. Left first, ID1 = Inside, Figure 3:14. Right first, ID1 = Inside,
ID2 = Outside ID2 = Outside
Figure 3:15. Left first, ID1 = Inside, ID2 = Off Figure 3:16. Right first, ID1 = Inside, ID2 =
Off
Pressing the Compensation Options button allows the user to view the Compensating Plate
options. Refer to MDS Compensating Plates for further information.
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.
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.
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.
Clicking Full allows the user to make all supports active, clicking Brief allows the user to
make only a small subset of supports for demonstration purposes active.
4.2 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.
selecting the appropriate command from the menu. There is also a Select All option at the
bottom-left of the grid.
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.
Figure 4:5. MDS Active Control Form with Side Grid Shown
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.
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:
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.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.2.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:
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).
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.
False = Ancillary material does not appear in the isometric material list
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.2.11 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.
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.
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:
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:
FT17 FT36
FT18 FT37
FT19 FT38
FT21 FT39
FT25 FT40
FT29 FT42
FT31 FT43
FT32 FT51
FT33 FT56
FT34A, B, C
5.3.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).
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.
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.
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.
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.
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.
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.
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.
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. (Refer
to 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 Interfaces
(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.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.2.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:
By default, ancillary, hanger and trunnion standards are assigned a default support function
corresponding to their MDS standard code. For example, AT, AN, FH, VH, TT, these are fully
configurable by the administrator.
To specify a support function for an ancillary, refer to MDS Ancillary Defaults Form for further
information.
To specify a support function for a trunnion, refer to MDS Trunnion Defaults Form for further
information.
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.
Figure 6:3. MDS Hanger Data - Bottom Associated Support Standards Tab
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.
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.
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.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.
7.2.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:
Note: The settings detailed in Vendor Reference to Isometric MTOC Flag are only available
for certain framework types selected in the list.
False = Ancillary material does not appear in the isometric material list
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).
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.
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:
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.
If an alternative code is required for an individual support code, it is entered into the
Alternative Code text box, to replace the * character.
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.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.2.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:
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).
The default setting is *, meaning there is no restriction on the elevation at which the trunnion
can be created.
False = trunnion material does not appear in the isometric material list
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).
To make a particular trunnion bore size available to the MDS designer, click on the item in
the Avail. bores list then click on the left arrow icon on the left side of the list. This transfers
the item to the adjacent Trunn. Bore list. Clicking on the right arrow, reverses the action.
Each bore for any of the MDS trunnion types may have one or more trunnion bores set as
the supplied MDS defaults. The maximum trunnion bore size is normally one pipe bore size
less than the main pipe bore size.
8.3.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).
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.
The MDS application contains functionality to include GRIDSY grids (available in DESIGN)
in the MDS ABA location plan. The use of SCTN based grid definitions is maintained.
This functionality enables the use of multiple grid systems across the model. Suitable grid
systems are automatically selected in the MDS ABA location plan during drawing
generation.
In order to include a GRIDSY grid in PARAGON, it is first necessary to set up a grid in
DESIGN. Refer to the Design Common Functionality User Guide for further information.
This administrator can define the list of available grids, the pattern for tagging of gridlines
(PML expression) and origin of support coordinates that display on the drawing.
The administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/
ABAGRIDDATA/DEFAULTS.
The default values/settings shown on the form are those that exist when the MDS
application is first installed.
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.
The Support Coordinates Origin drop down list contains the following types of support
datum calculation:
Matching Grid - The origin of the selected grid is used.
Zone, Site, World - The origin of the specified element in the hierarchy above the
support is used.
Named Item - The origin of the specified named item in the design database is used.
Figure 10:2. Add a Grid to the MDS ABA Grid Data form
The MDS application contains functionality to enable user defined ancillary selection criteria
when generating supports. These criteria are used in addition to the standard checks that
are performed on ancillaries when they are created. For example bore, temperature and
material checks.
The administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/
SELECTION-CRITERIA.
The default values/settings shown on the form are those that exist when the MDS
application is first installed.
The Reset button, reverts the User Defined Ancillary Selection Criteria form to the default
values/settings.
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.
--make sure that the paint spec of the of the pipe is one of the types
specified below
if !paintSpec.neq('12345-STD-PIP-001-RAL1069') and !paintSpec.neq('12345-
STD-PIP-001-RAL1070') then
return FALSE
else
return TRUE
endif
endfunction
The user defined check function must be created in a standard text file. As the function
name is checkCriteria1 the file should be saved as checkcriteria1.pmlfnc
It is recommended that check functions are saved in a separate folder to PDMS and that the
pmllib environment variable in PDMS startup is modified to point to it.
For example:
1. Create a folder called pmllib in c:\userpml\
2. Save checkcriteria1.pmlfnc to c:\userpml\pmllib\
3. Modify the environment variable for pmllib to add this new search path. For example:
set pmllib= c:\userpml\pmllib;%PMLLIB%
4. Enter DESIGN, type PML REHASH ALL into the command line and press enter. The
pml index is updated allowing the user defined file to be used.
Refer to the Software Customisation Guide for further information regarding PML
customisation.
The MDS application contains functionality to enable the creation and modification of
compensating plates in order to fill any gaps between frameworks and ancillaries.
In order to create compensating plates within DESIGN, it is first necessary to set up a
number of administrative options within PARAGON first.
The administration data is stored in the MDSAPPDEFAULTS database below CATA MDS/
COMPENSATING-PLATES/DEFAULTS.
12.1.2 Gap
The gap settings allow the administrator to define when a compensation can be used and
which type of compensation to use in a particular situation.
It is also possible to define the maximum gap for a plate to be used. If the gap is between
the maximum for a plate and the maximum for a profile, then a compensating profile (SCTN)
is created.
The dimensional value of the Minimum field defines the minimum space required for the
user to create a compensating plate. If the gap is less than this value then it is not regarded
as a gap and no compensation is created.
The dimensional value of the Maximum for Plates field defines the maximum space
required for the user to create a compensating plate. If the gap is equal or less than this
value (and not less than the Minimum) then plates (PANE) will be created to fill the gap.
The dimensional value of the Maximum for Profile field defines the maximum space
required for the user to create a compensating profile. If the gap is equal or less than this
value but greater than the maximum value for plates, then a profile (SCTN) will be placed to
fill the gap.
The Calculation Method drop down list contains the following types of plate thickness
calculation:
Greater or equal to the gap - The overall thickness of all plates must either fit the gap
or overlap it. There must be no remaining gap.
Less or equal to the gap - The overall thickness of all plates must never overlap the
gap. Plates either fit the gap or some gap remains.
Closest to the Gap - There can be either an overlap or a gap remaining, plates of
thicknesses are selected so the overall thickness is as close to the gap size as
possible.
The Visually Accomodate option can be set to either On or Off using the drop-down list. If
there is a gap or overlap, the actual thickness of the top plate can be accommodated so that
it fits the gap. This is done by adding an extra design parameter to the plate to alter the
height.
12.1.4 Rounding
The rounding settings allow the administrator to define the calculation process for the
rounding of the compensating plate.
The X and Y values for the compensating plate are the length and width values. In order to
obtain these sizes a calculation can be performed, refer to MDS Compensation Sizes Form
for further information.
After the X or Y size of the compensating plate is calculated, it is rounded according to the
specified parameters.
The Calculation Method drop-down list contains the following types of rounding
calculation:
Always Up - The resulting value from the calculation is always rounded upwards. For
example, if the resulting X size is 33mm and the rounding X value is set to 10mm then
it will be rounded up to 40mm.
Always Down - The resulting value from the calculation is always rounded
downwards. For example, if the resulting X size is 38mm and the rounding X value is
set to 10mm then it will be rounded down to 30mm.
To Closest Value - The resulting value from the calculation is rounded to the nearest
number. For example, if the resulting X size is 38mm and the rounding X value is set to
10mm then it will be rounded up to 40mm.
The X-size value and Y-size value fields allow the administrator to define the nearest value
to round to. For example, an X-size value of 10mm will round the result to the nearest
10mm.
To disable rounding, set the X and Y size values to 0mm.
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.
The administrator can populate the Support Codes and X-Size Rule or Y-Size Rule fields
with the relevant rule values.
Click OK to add the rule to the list of available rules or Cancel to discard any changes and
close the Add Entry window. The administrator is returned to the MDS Compensation Sizes
form.
Click Remove Entry to delete the currently selected rule.
The MDS Compensation Materials form contains two lists, the first lists the different possible
materials choices and the second lists the available materials.
To set a material choice, select the appropriate choice from the list of choices and then
select the material for that choice from the materials list.
Duplicate choices are omitted from the material selection drop down list in DESIGN.
The default choice is the material that is initially set when a compensation is created. It is
not possible to remove the default choice.
The list of materials that can be assigned to a choice is populated from the MDS/PROP
database and only the solid materials are available for selection.
Note: The maximum length of any line in this file must not exceed 256 Characters. If more
than 256 characters exist, the MDS Report Utility will error on initialisation with:
Fields 1 2 3 4 5
Description Output Report Title Heading Main Report Filter List Types
File Numbers and
Name optional sorting,
totalling and
subtotalling
controls in
parentheses ()
Example MDS Support 1(),2(),3(),4(), (match(name of Atta stru
Summary Index 5() spref,/MDS) eq 1)
Summary 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.
Field <3> also contains details of the sorting and totalling options for each column. The
format of this field is described below (comma separated):
\ heading_number1() , heading_number2(), ... heading_numbern() \
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)
Parameter Value
heading_number [REAL]
Refers to the column headers described in the MDS-REPORT-
HEADINGS file
totalling [BOOLEAN]
Turns totalling on/off for the column.
TRUE = totalling ON
FALSE = totalling OFF
Default empty field = FALSE
sorting_ [REAL]
precedence
If this column is to be sorted, then this value determines the
precedence of the sort. If the column does NOT require sorting, then
this value should be ZERO (0)
Default empty field = 0
sort_ascending [BOOLEAN]
This controls the order of the sort.
TRUE = ascending
FALSE = descending
Default empty field = TRUE
subtot_sort_col [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
The data above appears in the MDS-REPORT-DEFS file in the format shown in Figure
13: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
Figure 13:1. Extract from MDS-REPORT-DEFS
Column Num 1 2 3 4 5
Description Description Column Expression PML Justify
Heading Function Column
Type/Options text text PDMS Name of pml Left, centre
Expression Function or right
Example MDS Standard (after MDSmatma left
Standard (name of ncofg
spref
,MDS/))
Optional (O) or Optional Mandatory Mandatory -either Col 3 Optional
Mandatory (M) OR Col 4 Empty =
Optional -Col 3 AND Col 4 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
Column Num 6 7 8 9
Description Client Code Unset text Client Output Data
Description Type
Type/Options True(T) / text True(T) / ASCII (A) /
False(F) False(F) Numeric (N)
Example true Non-found true Numeric
Optional (O) or Optional Optional Optional Optional
Mandatory (M) Empty = false Empty = --- Empty = false 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
13: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\
Figure 13:2. Extract from MDS-REPORT-HEADINGS
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.
or
2. Select the Settings > MDS AutoNaming menu item and the form in Figure 14:1.: MDS
AutoNaming form is displayed.
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 14: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
MaxIndex\1999
Figure 14:2. Extract from DES-SUPP-NAMES
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.
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.
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.
hole will require a larger pin and a hanger with larger rods. This is handled by adding a one-
letter 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).
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 co-
ordinates. 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'
-- End Section 1
--
-- =============================================
-- Permitted View Scales
-- =============================================
--
-- Section 2
Metric \MET \1/1 \1 1 \1
Metric \MET \1/2 \1 2 \0.5
Metric \MET \1/3 \1 3 \0.333333,0.3333,0.33
Metric \MET \1/5 \1 5 \0.2
Metric \MET \1/10 \1 10 \0.1
Metric \MET \1/20 \1 20 \0.05
Metric \MET \1/25 \1 25 \0.04
Metric \MET \1/33.1/3 \1 33.1/3 \0.0303,0.03
Metric \MET \1/50 \1 50 \0.02
Metric \MET \1/75 \1 75 \0.013333,0.0133,0.013
Metric \MET \1/100 \1 100 \0.01
Metric \MET \1/150 \1 150 \0.006667,0.0067
Metric \MET \1/200 \1 200 \0.005
Metric \MET \1/250 \1 250 \0.004
Metric \MET \1/500 \1 500 \0.002
Metric \MET \1/1000 \1 1000 \0.001
Metric \MET \1/1250 \1 1250 \0.0008
Metric \MET \1/2500 \1 2500 \0.0004
Architectural \ARC \3" = 1'-0" \3Inch 1' \0.25
Architectural \ARC \1 1/2" = 1'-0" \1.1/2Inch 1' \0.125
Architectural \ARC \1" = 1'-0" \1Inch 1' \0.083333,0.0833
Architectural \ARC \3/4" = 1'-0" \0.3/4Inch 1' \0.0625
Architectural \ARC \1/2" = 1'-0" \0.1/2Inch 1' \0.041667,0.0417
Architectural \ARC \3/8" = 1'-0" \0.3/8Inch 1' \0.03125 ,0.0313
Architectural \ARC \1/4" = 1'-0" \0.1/4Inch 1' \0.020833,0.0208
Architectural \ARC \3/16" = 1'-0" \0.3/16Inch 1' \0.015625,0.0156
Architectural \ARC \1/8" = 1'-0" \0.1/8Inch 1' \0.010417,0.0104
Architectural \ARC \1/16" = 1'-0" \0.1/16Inch 1' \0.005208,0.0052
Engineering \ENG \1" = 10'-0" \1Inch 10' \0.008333,0.0083
Engineering \ENG \1" = 20'-0" \1Inch 20' \0.004167,0.0042
Engineering \ENG \1" = 30'-0" \1Inch 30' \0.002778,0.0028
Engineering \ENG \1" = 40'-0" \1Inch 40' \0.002083,0.002
Engineering \ENG \1" = 50'-0" \1Inch 50' \0.001667,0.0017
Engineering \ENG \1" = 60'-0" \1Inch 60' \0.001389,0.0014
Engineering \ENG \1" = 75'-0" \1Inch 75' \0.001111,0.0011
Engineering \ENG \1" = 100'-0" \1Inch 100' \0.000833,0.0008
-- End Section 2
--
-- =============================================
-- 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
/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
:MDSABAOption This controls the Projection angle of the View: 1 = 1st angle
projection and 3 = 3rd angle projection. The uda defaults to 3rd
angle projection if unset.
SheetLayout
Task name: MDS_aba_sheet_task
SheetLayout
Function name: Mdsabasheettask.pmlfnc
Description: This task is mandatory for all MDS Template sheets as it sets up
the sheet environment to be able to run all the other Tasks for a
particular Template. It defines the Views, sets the scales,
switches off the View Frames, and sets the View Type. It also
gets the name of the required MDS Support.
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:
Support code
Task name: MDS_aba_suppcode
Function name: MDSabasuppcode.pmlfnc
Description:
MainView
Task name: MDS_aba_view_task
Function name: MDSabaviewtask.pmlfnc
Description: This task is mandatory as it processes other View tasks
although the majority of the main detail VIEWS attributes are
modified in this function (task). The View Scales and the
update of each detail view is carried out in the sheet function
(task), i.e. !!mdsabasheettask.pmlfnc to avoid updating these
Views more than necessary.
Support data
Task name: MDS_aba_supp_data
Function name: MDSabasuppdata.pmlfnc
Description:
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:
From To
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.
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 earlier.
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.
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.
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.
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
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.
GT500 to GT569
Guide for Shoes
Simple Guide 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 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.
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.
3 Clearance CLR
4 Length LEN
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
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.
1 Height HEI
2 Width WID
3 Clearance CLR
4 Length LEN
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
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.
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
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.
AN640 to AN700
Anchor for Trunnions
Simple Anchor Representation
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, i.e.
to -1. All other design parameters are set to 0 (zero) as shown in the form displayed above.
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
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.
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
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.
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.
P-Point Description
1 Arrive Point
2 Leave Point
3 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.
Note: The MDS default p-points provided cannot be deleted or modified, but additional p-
points can be created if required.
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:
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.
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. Change the search path on the MDSPLOTS environment
variable, within the mdsevars.bat batch file from set mdsplots=%1\pdmsui\des\mds\plot to
set mdsplots= S:\AVEVA\MDS12.0.0\user_plots %1\pdmsui\des\mds\plot.
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).
A.3 Anchors
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.
Refer to Modifying User Defined Ancillary Geometry for information on User Defined Anchor
Standards.
A.4 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.
Refer to Modifying User Defined Ancillary Geometry for information on User Defined
Ancillary Standards.
.
A.6 U bolts
The following standards are available in the MDS application. Refer to Modifying User
Defined Ancillary Geometry for information on User Defined U Bolt Standards.
A.11 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. Refer to Modifying User
Defined Ancillary Geometry for information on User Defined Guide Standards.
.
A.14 Lugs
The following standards are available in the MDS application. Refer to Modifying User
Defined Ancillary Geometry for information on User Defined Lug Standards.
A.16 Stops
The following standards are available in the MDS application. Refer to Modifying User
Defined Ancillary Geometry for information of User Defined Stop Standards.
A.18 Trunnions
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.
Index
A C
Active Cable Clips
allowed pipe bores for trunnion . . . . 8:5 standards . . . . . . . . . . . . . . . . . . . . A:13
available ancillaries . . . . . . . . . . . . . 5:3 Cable Tray Framework Supports
available framework standards . . . . . 7:3 standards . . . . . . . . . . . . . . . . . . . . A:14
available hanger configurations . . . . 6:3 Closed End Clearance . . . . . . . . . . . . . . 5:5
available pipe bores . . . . . . . . . . . . . 5:7 Create . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9
available trunnion types . . . . . . . . . . 8:2
Active Icons . . . . . . . . . . . . . . . . . . . . . . 3:16 D
Administrators Role . . . . . . . . . . . . . . . . 1:1
Aliases Data Sets . . . . . . . . . . . . . . . . . . . . . . 18:18
hanger configuration . . . . . . . . . . . . . 6:4 Dataset Code Conversion Factor . . . . . 3:14
Allowed rod sizes Default forms . . . . . . . . . . . . . . . . . . . . . 1:1
hangers . . . . . . . . . . . . . . . . . . . . . . 6:6 Default text files . . . . . . . . . . . . . . . . . . . 1:1
Alternate Representation Level . . . . . . . 3:12 Description
Alternative Expression . . . . . . . . . . . . . 5:11 ancillary support standard . . . . . . . . 5:3
Anchors framework standard . . . . . . . . . . . . . 7:2
standards . . . . . . . . . . . . . . . . . . . . . A:3 hanger configuration standard . . . . . 6:3
Ancillaries trunnion standard . . . . . . . . . . . . . . . 8:2
standards . . . . . . . . . . . . . . . . . . . . . A:4 Design parameter definitions . . . . . . . . . 5:1
Ancillary support standards . . . . . . . . . . . 5:2 Design Parameters
Associated Ancillaries user editable . . . . . . . . . . . . . . . . . 5:12
standards . . . . . . . . . . . . . . . . . . . . . A:2 Design parameters . . . . . . . . . 5:8, 5:9, 5:10
Auto Naming default files . . . . . . . . . . . 14:1 Determine if Notes Appear on Isometric Drawing
3:15
B Display Orientation in Support Tag on Isometric
3:14
Bore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Drawing production
Bore size . . . . . . . . . . . . . . . . . 5:7, 5:9, 5:10 MDS specific sheet template libraries 17:3
Bottom associated support standards MDS specific tasks . . . . . . . . . . . . 17:4
hangers . . . . . . . . . . . . . . . . . . . . . . 6:5 sheet tasks . . . . . . . . . . . . . . . . . . . 17:4
Branch Reinforcements view tasks . . . . . . . . . . . . . . . . . . . 17:6
standards . . . . . . . . . . . . . . . . . . . . A:12 Drawing Production Defaults . . . . . . . . 17:1
O
J
Open End Clearance . . . . . . . . . . . . . . . 5:5
Joint Offset . . . . . . . . . . . . . . . . . . . . . . . 3:9
Overview of the MDS Application . . . . . . 1:1
L P
Lugs
PARAGON database . . . . . . . . . . . . . . . 1:1
standards . . . . . . . . . . . . . . . . . . . . A:24
Parameter Tab . . . . . . . . . . . . . . . . . . . 5:10
Parameters
M design . . . . . . . . . . . . . . . 5:8, 5:9, 5:10
user editable . . . . . . . . . . . . . . . . . 5:12
Max. Horizontal Angle . . . . . . . . . . . . . . . 3:6
Pipe Clearance . . . . . . . . . . . . . . . . . . . . 3:5
T
Transport Prefix . . . . . . . . . . . . . . . . . . 3:12