TM-2256 AVEVA Marine (12.1) Outfitting Supports Administration Rev 1.0
TM-2256 AVEVA Marine (12.1) Outfitting Supports Administration Rev 1.0
(12.1)
TRAINING GUIDE
Outfitting Supports
Administration
TM-2256
www.aveva.com
AVEVA Marine (12.1)
Outfitting Supports – TM-2256
www.aveva.com
2
AVEVA Marine (12.1)
Outfitting Supports – TM-2256
Revision Log
Date Page(s) Revision Description of Revision Author Reviewed Approved
DH,
29/11/2013 All 0.1 Issued for Review
Elva L
DH,
05/12/2013 All 0.2 Reviewed Wayne R
Elva L
DH,
24/01/2014 All 1.0 Approved for Training 12.1.SP4 Wayne R
Elva L
Updates
All headings containing updated or new material will be highlighted.
Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers please report it to the AVEVA
EDS - Training & Product Support at [email protected]
This manual provides documentation relating to products to which you may not have access or which may
not be licensed to you. For further information on which products are licensed to you please refer to your
licence conditions.
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.
1 Introduction .............................................................................................................................................. 6
1.1 Aim..................................................................................................................................................... 6
1.2 Objectives ......................................................................................................................................... 6
1.3 Prerequisites .................................................................................................................................... 6
1.4 Course Structure .............................................................................................................................. 6
1.5 Using this Guide ............................................................................................................................... 7
2 Overview ................................................................................................................................................... 9
2.1 Work Flow and Data Composition.................................................................................................. 9
2.2 Major Features................................................................................................................................ 11
3 Database of AOS Project ...................................................................................................................... 13
3.1 Supplied Projects ........................................................................................................................... 13
3.2 Variables of AVEVA Outfitting Supports ..................................................................................... 13
3.3 Database Requirements ................................................................................................................ 13
3.4 Configure AOS Profile Catalogue and Specification Database ................................................ 15
3.5 Configure Working Project MDBs for AOS ................................................................................. 18
3.6 How to Reuse PSM 12.1 Data ........................................................................................................ 24
Exercise 1 – Project Setup ............................................................................................................................ 24
4 Application Access Control .................................................................................................................. 25
4.1 Define AOS Team and User .......................................................................................................... 25
4.2 Design Rule Access Control ......................................................................................................... 33
5 Design Rule Configuration ................................................................................................................... 37
5.1 Define Support Type and Name .................................................................................................... 38
5.2 Define Support Area ...................................................................................................................... 41
5.3 Ancillary Selection ......................................................................................................................... 43
5.4 Define Sliding Pad & Ancillary Type ............................................................................................ 45
5.4.1 Updating New Size ................................................................................................................... 46
5.4.2 Define Sliding Pad Material ...................................................................................................... 49
5.4.3 Define Ancillary Element Type (ATTA/FIXING) ....................................................................... 49
5.5 Define Span Length ....................................................................................................................... 51
5.6 Define Snip Size & Available Profile ............................................................................................ 56
5.7 Define Profile Material ................................................................................................................... 59
5.8 Define Support Type & Size .......................................................................................................... 61
Exercise 2 – Design Rule Setting for Specific Rule ................................................................................... 64
6 Catalogue and Specification Creation ................................................................................................. 67
6.1 Create Ancillary Catalogue ........................................................................................................... 68
6.2 Create Ancillary Specification ...................................................................................................... 72
6.3 Add New Size of Sliding Pad Catalogue & Specification ........................................................... 76
6.4 Create Material ............................................................................................................................... 78
6.5 Invalid Specification Control ........................................................................................................ 81
Exercise 3 – Set Design Rule with New Subtype Support & Ancillary ..................................................... 83
7 Drawing Configuration .......................................................................................................................... 87
7.1 Hierarchy of AOS Support Sketch Drawing Template ............................................................... 87
7.2 Configure Drawing Functions ....................................................................................................... 88
7.2.1 Define Function for View .......................................................................................................... 90
7.2.2 Define View Function Parameter ............................................................................................. 91
7.2.3 View Function Management ..................................................................................................... 93
7.2.4 Parameter Management .......................................................................................................... 97
7.2.5 Define Function for Sheet ...................................................................................................... 100
Exercise 4 – Configure View Function and Parameter ............................................................................ 102
7.3 Create New Drawing Template Library with Backing Sheet .................................................... 104
Exercise 5 – Create New Support Sketch Template ................................................................................. 110
1 Introduction
The AVEVA Outfitting Supports (AOS) application is used to create, modify and delete the various types of
support for Pipe, Cable way and HVAC. AOS based on the user defined rule allows the user to easily create
support models and drawings.
1.1 Aim
The participants will learn the basic functions required to configure AOS Design Rule, Settings and Sketch
Drawings using AVEVA Outfitting Supports (hereinafter AOS) application. At the end of this training course,
the support Designer will have enough knowledge and understanding of AOS to be able to manage supports
on the Marine Training Project (MTP).
1.2 Objectives
1.3 Prerequisites
AVEVA Marine 12.1 has been installed with valid licenses and the basic configurations have been
setup correctly.
The user has a valid AVEVA Outfitting Supports license and the software has been installed.
The user knows how to launch Admin, Outfitting module and Paragon of AVEVA Marine.
The user should have already completed AOS Basic Training and have an understanding of it.
Training will consist of demonstrations and set exercises. Each workstation will have a training project,
populated with model objects. This will be used by the trainees to practice their methods, and complete the
set exercises.
AVEVA Outfitting Supports provides various functions to create Pipe supports, Cable Tray supports and
HVAC supports. In this guide Pipe Supports, Cable Tray Supports and HVAC Supports are called [PSM],
[CSM] and [HSM] respectively.
It is assumed that:
• [PSM]: Only available for Pipe Supports
• [CSM]: Only available for Cable Tray Supports
• [HSM]: Only available for HVAC Supports
• No mark: Available for all disciplines as a general function
When creating Pipe support, Cable Tray support and HVAC support, the functions of Modify and Utility are
the same so the guide is based on Pipe Support. If necessary, an additional explanation for each discipline
will be added.
© Copyright 1974 to current year. 6
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Marine (12.1)
Outfitting Supports – TM-2256
Certain text styles are used to indicate special situations throughout this document, here is a summary;
Menu pull downs and button click actions are indicated by bold dark turquoise text
Information the user has to key-in will be in bold red text
Annotation for trainees benefit
Additional information
System prompts should be bold and italic in inverted commas i.e. 'Choose function'
Example files or inputs will be in the Courier New font.
2 Overview
This chapter explains major features, data composition and how to store model data within MDB.
The AOS project contains design rules, catalogues & specifications, UDA, materials, etc. in each database
to run the application. To operate the application properly, the administrator must include such AOS
databases into necessary MDB as a foreign database. These data in each database should be defined by a
certain naming convention and standards by the administrator or the user with the access right. The data is
commonly used by all users.
The administrator should configure the catalogues and specifications for support work in the Catalogue
database and support templates for support type reference in the Design database. Also, many different
materials to be used for support components are created and managed in the PROPCON database.
Templates, drawing library, symbol, etc. for drawing creation are also managed in the Drawing database.
Support design rules should be located below APPLDW in the Design database. The design rules can be
set and stored by design part in each design area.
Refer to the appendices of the AVEVA Outfitting Supports – Administrator and User Guide.
DesignDatabase
Various support design rules defined by the administrator are maintained here. Data added, deleted
and modified by the administrator are managed in the DABACON according to each element type
and attributes.
CatalogueDatabase
DictionaryDatabase
PropertyDatabase
DraftDatabase
Key Benefits
AOS offers functions to easily add support components, for example ancillary, sliding pad, support
fittings, etc. The administrator can configure such design rules as catalogues and this can be
managed via the AOS Ancillary Spec Controller form.
The application allows the user to create supports for Piping, Cable Tray, and HVAC. It is highly
interactive, enabling the user to design supports with the minimum of effort. AOS is also highly
configurable, allowing the administrator to define project-related defaults, in order to control the
design of supports and determine the range and types of ancillary components that can be used on
a project.
The standard framework supports in the application are designed using structural sections and are
template driven. A default set of structural templates based on Japanese Profiles is supplied with
the AOS application. Any relevant national standard for steelwork sections can be used by
configuring the supplied templates.
If the templates supplied do not meet the project or company requirements, the system
administrator can easily create new support templates or reuse supplied templates.
Ancillaries are elements which are generally used in shipbuilding (for example u-bolt, strap, loose
type, etc.). They are attached to Pipe, Cable Tray or HVAC.
The Support Sketch Admin function of AOS helps the administrator to manage the Tasks applied to
Drawing Template and Task Parameter through UI.
Various Drawing Templates can be provided to customers based on the Support Sketch Drawing
Templates basically provided. Customers can use (add) various Drawing Templates based on the
Support Sketch Drawing Templates basically provided according to their own circumstances. The
Tasks can be applied to new Drawing Templates.
The AVEVA Marine product is supplied with a training project, MTP. To operate AOS properly, MTP as well
as the AOS project should be configured in advance by the administrator.
If MTP and AOS are properly installed then the user can use MDB (AOSFWD, AOSMID, AOSAFT) in the
MTP. Please refer to MDB basically provided from AOS to understand this training.
This chapter explains how databases provided from AOS is included into the Marine Training Project (MTP)
to be customised. This is useful when adding the AOS project to other projects.
The AOS application is supplied to all the users of AOS with several projects.
When AOS are loaded AVEVA Marine Macros variables PDMSUI, PMLLIB and PDMSUSER are modified
to have multi-paths and are typically:
These variables can be checked using q evar, for example q evar pmllib.
The user does not need to add variables to evars.bat. They are automatically loaded through window
batch fiile (OutfittingSupport.bat).
To operate the AOS application, the following databases should be made up in AOSMDB:
MASTER/PSM-CATALOGUE
MASTER/PSM-DESIGN
MASTER/PSM-DICTIONARY
MASTER/PSM-DRAFTING
MASTER/PSM-PROPERTY
MASTER/CSM-HSM-CATALOGUE
MASTER/CSM-HSM-DESIGN
MASTER/CSM-HSM-DICTIONARY
MASTER/CSM-HSM-DRAFTING
MASTER/CSM-HSM-PROPERTY
The following Databases included within the AOS Project do not need to be added to MDB because
they are empty databases and only created for new functions.
MASTER/OFFSHORE-DESIGN
MASTER/OFFSHORE-CATALOGUE
MASTER/OFFSHORE-DRAFTING
MASTER/OFFSHORE-PROPERTY
MASTER/OFFSHORE-DICTIONARY
MASTER/ASLCATA
MASTER/CABLEPROP
MASTER/DICT
MASTER/HVACCATA
MASTER/MARSTLCATA
MASTER/MDSDICT
MASTER/PADD
MASTER/PIPECATA
MASTER/PROP
MASTER/STLCATA
MASTER/SUPPCATA
MDS/CATA
MDS/DESITMPL-PSL
MDS/DESI-SPECIAL-TMPL-DIN
MDS/DESITMPL-DIN
MDS/DRAFT
MDS/MDSAPPDEFAULTS
MDS/PROP
MDS/WELDS
MDS/DRAFTSTDS
If the user does not operate AOS in the MDS module then MDS Database does not need to be added
to MDB.
MPROJECT/CATA
If the user does not use Catalogues of MTP (MPROJECT/CATA) then Catalogue Database of MTP
Project does not need to be added to MDB for AOS operation.
The user should first define Profile Catalogue and Specification to use AOS. But Profiles used in the Steel
work can be reused in the AOS by setting profile specifications of MAS project suitable for the AOS project.
To start the AVEVA Outfitting Supports application, select All Programs > AVEVA Marine > Design >
Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project mas
Username SYSTEM
Password XXXXXX
Module Admin
Accroding to circumstances the user can use Profile Catalogue and Specificaiton defined in other
projects.
In the Admin elements area, select Elements Databases & Extracts > Include Foreign Database. Select
AOS in the Foreign Projects.
The following is the process of adding AOS Dictionary Database to the MAS project.
Username SYSTEM
Password XXXXXX
MASTER/PSM-DICTIONARY
MASTER/CSM-HSM-DICTIONARY
Profile information which will be used in AOS is recorded in the above database through UDA of Profile
Specification.
In the Admin elements, select Elements : MDBs > Create Multiple Database. Enter the following data.
Name AOSP
Description MDB for AOS Profile Selection
MASTER/PSM-DICTIONARY
MASTER/CSM-HSM-DICTIONARY
MASTER/STLCATA
If additional Profile Catalogue and Specification are needed then add the Database including the relevant
Catalogue and Specification.
Change the information of Profile Specification in the PARAGON module via MDB added.
Select All Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project mas
Username SYSTEM
Password XXXXXX
MDB AOSP
Module Paragon
The newly added UDA is represented in the Profile Specification by accessing the Paragon module. Set the
value of UDA :AOSProfile to TRUE.
/BS-SPEC
/JIS-SPEC
/NON-STANDARD-SPEC
These Profile Specs can be used as Profile for Support Model in the AOS application. How to apply Profile
Specification to the Support Model is covered in Chapter 5. Design Rule Configuration.
This section explains the composition of Database and MDB for Working Project (Local Project) which refers
to Master Project provided from AOS as Foreign Database.
The AOS Project (Master Project) contains Catalogue, Specification and Template information which is the
basis of Support Model. It is recommended that AOS database is used in the Working Project as foreigen
project to protect direct access from Working Project.Therefore the information of Design Rule and Support
Library is defined on the AOS Project and can be referred or regenerated in the Working Project.
To set MDB for MTP Project and add AOS Project as Foreign Database to Working Project, select All
Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports.
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username SYSTEM
Password XXXXXX
Module Admin
MDB(AOSFWD, AOSMID, AOSAFT) is already included in the MTP Project, which means AOS
Database is already added as Foreign Database.
In the Admin elements select Elements Databases & Extracts > Include Foreign Database. Select AOS
in the Forgin Projects.
MASTER/PSM-CATALOGUE
MASTER/PSM-DESIGN
MASTER/PSM-DICTIONARY
MASTER/PSM-DRAFTING
MASTER/PSM-PROPERTY
MASTER/CSM-HSM-CATALOGUE
MASTER/CSM-HSM-DESIGN
MASTER/CSM-HSM-DICTIONARY
MASTER/CSM-HSM-DRAFTING
MASTER/CSM-HSM-PROPERTY
Username SYSTEM
Password XXXXXX
MASTER/PSM-CATALOGUE
MASTER/PSM-DESIGN
MASTER/PSM-DICTIONARY
MASTER/PSM-DRAFTING
MASTER/PSM-PROPERTY
MASTER/CSM-HSM-CATALOGUE
MASTER/CSM-HSM-DESIGN
MASTER/CSM-HSM-DICTIONARY
MASTER/CSM-HSM-DRAFTING
MASTER/CSM-HSM-PROPERTY
The above databases are essential AOS Databases to use AOS in the working project. In order to create
supports, more than one writable Design(DESI) Database should be included and Drawing(PADD)
Database for Drawing is also needed. In addition Catalogue & Specification Database and Hull Database as
well as Pipe or Cable Tray or HVAC Model are added for the standard of support.
Database Purpose
PSM/EDK_FWD
PSM/DDK_FWD
Support Design Database, AOS Support and Support information will
PSM/CDK_FWD
be stored in this Database.
Etc...
MDS/EDK_FWD
MDS/DDK_FWD
MDS/CDK_FWD Referred Design Database for MDS.
Etc...
EQUIP/EDK_FWD
EQUIP/DDK_FWD
EQUIP/CDK_FWD Referred Design Database for Equipments.
Etc...
ELECT/EDK_FWD
ELECT/DDK_FWD
ELECT/CDK_FWD Referred Design Database for Cable Way.
Etc...
HVAC/EDK_FWD
HVAC/DDK_FWD
HVAC/CDK_FWD Referred Design Database for HVAC.
Etc...
PIPE/EDK_FWD
PIPE/DDK_FWD
PIPE/CDK_FWD Referred Design Database for Pipe.
Etc...
MPROJECT/DICT
MPROJECT/PROP
MPROJECT/CATA Referred Database for Catalogue and Spcification.
Etc..
PHULLFWD/P_F101
PHULLFWD/P_F102
PHULLFWD/P_F103 Referred Database for Hull.
Etc...
MASTER/PIPECATA
MASTER/STLCATA
MASTER/HVACCATA Referred Foreign Database for Catalogue and Spcification in MAS.
Etc...
MASTER/PSM-CATALOGUE
MASTER/PSM-DESIGN
MASTER/PSM-DICTIONARY Referred Foreign Database for AOS Master Database.
Etc...
Please refer to AOSFWD MDB for the database not mentioned in the List.
To configure MDB, select the Elemetns MDBs in the Admin elements area. Select <MDB>AOSFWD in
MDB list and click Copy... button.
To MDB AOSW
Description MDB for AOS Working
MDB(ASOW) copied from MDB ASOFWD includes all the essential Databases of AOS.
Database Configuration for creating supports is over in the Working Project. Select the MDB(AOSW) added
as shown.
Select All Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username SYSTEM
Password XXXXXX
MDB AOSW
Module Outfitting
To start the application, select the Outfitting Supports – Pipe or Cable Tray or HVAC button in the toolbar
or Utilities > Outfitting Supports – Pipe or Cable Tray or HVAC. The main form of each application is
open.
Check that the AOS application is run normally via Outfitting Support toolbar or Utilities menu.
AOS 12.1 can be accessible in the Equipment, Pipework, Cable Tray, HVAC Designer, Cabling System
and Multi Discipline Supports of the Outfitting module through the toolbar and pull-down menu.
The user can identify that Databases of AOS Mater Project are added in the Design Explore after accessing
the Outfitting module.
Adding Support Area Rule or working on Support Library must be done after accessing via AOS MDB of
AOS Project. Note that it can affect all Working Projects referring to the AOS Project.
Support Area Rule and Support Template have been modified through the Outfitting module. Work on
Support Library is done through the Paragon module.
AOS allows Design and Drawing Data of PSM 12.1 to be used. Refer to Chapter 3.4 How to reuse PSM
Databases in AOS12.1.SP4 Administration and User Guide.
As shown below, Material, Catalogue, UAD and Drawing databases are to be used as foreign databases
and Design as a project database.
Define the Design database by areas; AFT AREA, MID AREA and FWD AREA.
AOS creates a Support Model based on the Rule Based Design way and this model will be the standard of a
Sketch Drawing. Therefore access right to Design Rule(Support Area) differ from the user to the user. The
only user with access right can modify the information of Design Rule (Support Area) and decide the range
of access right of the general user.
This chapter explains the way to assign and manage access right within the AOS application.
User access rights defined in the AOS are categorised into three. The range of access right depends on the
User Level. The administrator can impose an access limit on the general user.
Administrator
Key Man
General User
TEAM and User are already created for AOS Access Control in the MTP Project. Please note that the
relevant Team and User should be deleted for this training.
There are three users in the MTP Project. The first is the Administrator who is a free user in the AVEVA
Marine. Although the administrator is not assigned to a specific team and his Security Level is set to Free,
his Access Right is maintained.
Select All Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username SYSTEM
Password XXXXXX
Module Admin
In the Admin elements area, select Elements : Users > Create User. Enter the following data:
Username AADIMN
Password AADIMN
Description Administrator for AOS
Security Free
Save Work.
Log into the Outfitting module as ADMIN to check if the Administrator right is assigned.
To start the AVEVA Outfitting Supports application, select All Programs > AVEVA Marine > Design >
Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username AADMIN
Password AADMIN
MDB AOSW
Module Outfitting
Click the Outfitting Supports – Pipe button or Utilities > Outfitting Supports – Pipe to start the
application.
When the new project is performed for the first time in the
Outfitting module, this message will be displayed because local
design rule (Application Data Wold) is not created per MDB.
The functions of the AOS main form are deactivated before Application Data World for Support Design Rule
is created.
Create the Design Rule Hierarchy for the working project in the AOS/EDK_FWD database. Click the Create
Design Rule Hierarchy button in the Utilities tab after selecting /* (world) as follows.
Only administrators can create the Application Data World for Design
Rule.
Template Site is also created for the local project and can be used
to add Support type to the local project.
As Application Data World for saving Design Rule in the local project is completed, the functions of the AOS
main form are active.Check that all functions of Set Design Rules are activated.
As the administrator has all rights to Design Rule, all the buttons are active.
Click the Support Rule Options link label and Set values as following.
The second user is the Key Man who is a newly defined user type in the AOS application and assigned to
specific team for distinguishing from General User. First, create a team for Key Man.
In the Admin elements area, select Elements : Team > Create Team. Enter the following data:
Name AOSADMIN
Description Team for AOS Admin
To create a Key Man, select Elements: Users > Create User. Enter the following data:
Username KEYMAN
Password KEYMAN
Description Key Man User for AOS
Security General
Select AOSADMIN in the Project Teams list, add it to the Team Membership as shown below. If
necessary, the user can assign right to additional Databases.
Add AOS, DRAFT, ELECT, EQUIP, HVAC, OUTSTEEL and PIPE to Team Membership.
KEYMAN User, a member of AOSADMIN Team, has the right of Key Man. KEYMAN User has the right of
Key Man as he is included into AOSADMIN Team.
If the Key Man User account is already created then just add AOSADMIN to Team Membership.
In the Admin elements area, select Elements : Users and select OUTADMIN in the User list.
Click Modify...
Add AOS Team to Team Membership for access right to AOS Design Database.
Access the MTP Outfitting module as Key Man (KEYMAN, OUTADMIN). Check that five functions of Set
Design Rules are active.
Refer to Chapter 3. Start Application of TM 2241-AVEVA Outfitting Supports Designer Guide for more
information on how to check Design Rule in the Outfitting module.
Third, the General User is a typical user type of Designer who generally access working projects. So there is
no need to set a specific team for the General User within AOS.
Username GENUSER
Password GENUSER
Description General User for AOS
Security General
Add AOS, DRAFT, ELECT, EQUIP, HVAC, OUTSTEEL and PIPE to Team Membership.
Save Work.
The General User means all the users who are not included into AOSADMIN Team when Security is set to
General.
Access the Outfitting module as General User (GENUSER, SUPP, PIPE etc ). Check that three functions of
Set Design Rules are active.
The values of Support Information of Dimension can be modifided in the Settings tab.
If design rule is properly defined then the user does not need to consider specific values of Profile Size /
Ancillary and the administrator can restrict the general user’s access right to Design Rule.
This section explains how the administrator directly defines access right via Support Rule Option within the
AOS application.
Select All Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username AADMIN
Password AADMIN
MDB AOSW
Module Outffitng
Select Pipework... application in the Design menu, run the Outfit Supports – Pipe and click the Utilities
tab.
As for Rule Access, if AOS Administrator is selected then the General User (Designer) can not access all
of the Design Rules. As for Support Dimension, if Design Rule is selected then the General user can not
access Dimension items of the Settings tab.
Select AOS Administrator in the Rule Access and Design Rule in the Support Dimension as shown.
Then Login into as the General User (Designer).
Select All Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username GENUSER
Password GENUSER
MDB AOSW
Module Outfitting
Select Pipework... application in the Design menu, run the Outfitting Supports – Pipe and click the
Utilities tab. The Set Design Rules button is deactivated.
Rule Access and Support Dimension are set by each discipline respectively.
This chapter explains how to use the Set Design Rules function. This function is for the administrator to set
and manage unified support design rules for support creation and modification. There are eight design rules
definable by the administrator.
The functions of Set Design Rules for Pipe, Cable Tray and HVAC are almost the same so the
explanation is based on Outfitting Supports – Pipe. If needed, an additional explanation will be provided
by the trainer.
If Master Rule has to be changed, the user must access the AOS Project.
To start the AVEVA Outfitting Supports application, select All Programs > AVEVA Marine > Design >
Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project Training
Username AADMIN
Password AADMIN
MDB AOSW
Module Outfitting
Change to the Beams & Columes application and run the AOS application in the Utilities menu. Or use the
Outfitting Supports toolbar.
Design > Structures > Beams & Columes... or Utilities > Outfitting Supports – Pipe...
Select Set Design Rules from Utilities tab of the AOS application.
Support Types are managed in two ways (Std. Code, Support Name). Std. Code is for operating AOS
system and Support Name is for the user which means the user can change it.
The administrator can define naming rules of supports with suitable support name and description of
subtype support framework for a company or a project. It can be exported to or imported from Excel.
The Support Name information is stored in Application Data Area element /<project code>-NAME-
RULE/APPDAR and these names are brought from the subtype framework provided in site /<project
code>-TEMPLATE/SITE. The administrator should keep the naming rule of STRU when a subtype
framework is added.
For example, MTP is a project code, A is the main type and 01 is the subtype framework sequence.
Therefore the next number will be the last sequence + 1 such as A14.
Input the command (NEW STRU COPY /PSM-TEMPLATE-A01/STRU) in the command window.
Restart the AOS application and run the Support Name function.
An error form will be displayed, which means the icon file doesn’t exist in
the added Subtype Support Template.
Icons should also be synchronised with naming rules. The file format png is recommended and located in
the following directions.
Pipe “%pmllib%”\aosaddin\icons\psmsubtype\
Cable Tray “%pmllib%”\aosaddin\icons\csmsubtype\
HVAC “%pmllib%”\aosaddin\icons\hsmsubtype\
Name marsuppframemtp-a14.png
If the icon file is not found out when restarting the Support Name function, enter the
following command in the command window.
Rerun the Support Name function and check the Subtype Support for A14 in the List.
The items highlighted in yellow can be modified in the Support Name List. Change the name of Subtype
Support MTP-A14 into the following and save it.
When logging into AOS Project, the Subtype Supports basically provided can be modified.
Std. Code is the fixed Naming Structure in the Support Template so supports are created in the system
based on it. But the Support Name the user wish to use is PSM-A15 which can be modified and used
regardless the Naming Structure.
Let’s check that the name of Subtype Support added is the Support Name changed in the Support Creation
form.
According to support installation area, design rules for ancillary, subtype support framework, the profile size,
etc. can be different. The user should configure an area to apply the design rules considering pipe
specifications, pipe system, bore size, installation area, etc. This Support Area affects Ancillary Selection,
Set Ancillary Type and Support Type & Size.
Related design rules are loaded by selecting a support area. Machinery area (MACH) is provided as default.
The information of support area is stored and managed in /<project code> -SUPPORT-AREA/APPDAR
and can be exported or imported.
Right click on the Support Area MACH and select Copy Support Area to copy and create a new area for
403_ZONE.
Name 403_ZONE
Description 403 Zone For Training
Support Area 403_ZONE has the same information as MACH saved in the AOS Project. But the user can
directly modify 403_ZONE because its information is saved in the MTP (Local Project).
Click the Update Support Design Rules ( ) button in the Utilities tab to reload the area data.
Click the Settings tab and select 403_ZONE in the Support Area of Supprot Information.
There are so many ancillaries provided from the application according to different material types. The
administrator or the key man can classify ancillaries for use. They can be selected based on a support area
and multi-selection is available.
The Unused Ancillaries list shows all types of ancillaries registered. The user has to move them into the
Used Ancillaries list to use
Move Ancillary Type from the Unused Ancillaries List to the Used Ancillaries List. Set an ancillary type in
the Ancillary Selection form.
Move five ancillaries of FRMOA1 type into the Used Ancillaries list. Click the Apply link label to save.
The user can prevent from unnecessary ancillaries being used in each Support Area.
The user can directly use FRMOA1 Type ancillaries added as shown below.
The adminstrator can predefine design rules of type, material, etc. for ancillary and sliding pad by support
area.
Select the Support Area 403_ZONE which is created in section 5.3. Modify rules by specification against
403_ZONE.
Move /A150 from the Not Used for Common Rule to the Used for Common Rule in the Set Common
Spec. tab as shown below.
As for the supports installed in the Pipe model using Pipe Specification /A150, their Ancillary Type and
Sliding Pad Material are decided based on the information (Design Rule) of the Common Rules tab.
AVEVA Outfitting Supports – Designer Guide explains the Ancillary Types defined. This section only
contains the role of Administrator.
When first creating Support Area, the user should define the range of size for applying Design Rule.
Ancillary Type can also be defined within the range of Support Area. This subsection explains how to update
Size when a new TUBI (New size) is defined in the Pipe Specification.
Select 403_ZONE and check the size range of the Common Rules tab (15mm ~ 600 mm).
The Ancillary Type form shows Ancillary Type and Sliding Pad Material information which are applied
according to Support Rule during support creation. Ancillary type is applied based on Size.
Thirty ranges of Pipe Bore Size from 10mm to 1000mm are registered in the MTP. Twenty ranges of the size
from 15mm to 600mm are registered in the Support Area 403_ZONE so only twenty ranges are shown in the
Ancillary Type form. The nominal sizes are Bore Sizes of all Specification defined in the Catalogue and are
searched when running the AOS application.
Let’s look at what’s happening in the AOS system after adding new Pipe Bore Size.
Search /A150 Specification in the MAS Project and add a TUBE (new bore size).
To add new Pipe Bore Size, select All Programs > AVEVA Marine > Design > Outfitting Supports
12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project mas
Username SYSTEM
Password XXXXXX
Module ALLMAS
Module Paragon
Navigate to /A150.
Reload the AOS main form, click the Ancillary Type link label in Design Rules form.
If a new Specification (new bore size) is added, it can be identified when running the Ancillary Type
function. The window for entering an Imperial value for Size is displayed.
60mm 2.3
The new size (60mm) is added as shown below. Ancillary and Sliding Pad suitable for the new size (60mm)
should be added.
All values of 60mm Size are set to Unset because Catalogue and Specification suitable for 60mm Size are
not prepared.
© Copyright 1974 to current year. 48
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Marine (12.1)
Outfitting Supports – TM-2256
Selecting a Sliding Pad Material is available only when Ancillary Type has a Sliding Pad. Sliding Pad
Material is only applicable to the Pipe Support.
Size 100mm
Ancillar Type UBLTA4-MG
Pad Material TEFRON
Click Apply link label and close the Ancillary Type form.
The administrator can predefine which element type (ATTA or FIXING) is to be used as default for ancillary
creation. The ancillary type ATTA will exist as a PIPE component, and Fixing as a component of
STRUCTURE. Refer to section 2.2. Major Features of this guide.
It is recommended that the administrator sets only one element type to be used for all the supports in a
single project.
The ancillary element Type created can be changed by using the Ancillary Type Converter of the Utilities
tab.
It is recommended that Ancillary is set to FIXING type. As for ATTA type, the referred Model is modified by
the user so it can cause problems.
Basic shapes of Support are defined in the Support Template. But the lengths of Leg Profile and Span
Profile are defined according to circumstances of support creation. The values of Span Length are fixed so
the administrator should check and define them.
The administrator can set span length rules for a distance value between the centre of an ancillary and the
end of a span profile. If the administrator selects catalogues, the Span Length function is not activated as
shown and the length is decided by the parameter of ancillary catalogues.
When selecting Catalogue from the Span Length, the Span Length link label is deactivated.
Select Length Table from the Span Length, click the Apply link label.
Create an Ancillary Group in the Ancillary Group tab. Enter the Group Name and Description:
Select UBOLTA in the Span Length tab and enter the values of L1 and L2 as follows.
Size 80mm
Length for End (L1) 130mm
Length for Bend (L2) 150mm
The support rule for Pipe Size 80mm using Ancillary Type UBLTA1 and the Span Length (130mm and
150mm) are defined. If Span Length is not defined for specific size then the relevant supports can’t be used
as follows.
When creating a support by using the ancillary selected in the Ancillary Group, the result is as follows.
Ancillaries provided from the AOS Project basically have the following Data Set. PDFE and PDFB of Dkey
value correspond to L1 and L2 respectively.
The value of Span Length is defined by changing the value of Ancillary Catalogue so in most cases the
value should be modified in the AOS Project (Master) which contains Ancillary Catalogue.
The value of Span Length is generally defined in the Catalogue during the Ancillary Catalogue creation,
which is common to the Local Project. If values of Span Length need to be changed in the Local Project,
use the Span Length Table.
To modify Span Length in the new Catalogue, select All Programs > AVEVA Marine > Design > Outfitting
Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project AOS
Username SYSTEM
Password XXXXXX
DMB AOS
Module Paragon
Type UBLTA1
Size 100mm
Name /PSM-ANCIL/UBLT/A1/100
PA20 110
PA21 120
Return to the Outfitting module and do Get Work. Create a support using the Ancillary modified. The result
is as follows.
There are many specifications of profiles provided from AVEVA Marine, such as Japanese Standard (JIS),
British Standard (BS), etc. The standard depends on the types of companies and the user can select and
manage supports in the proper specification in use for their projects.
This section explains how to manage Profiles which are needed to create supports.
Profile Specifications included in the Used Profiles can be used when creating supports. All Profiles
selected in the Ancillary Type & Size should be preselected in the Profile Selection.
Move Profile Specifications of /JIS-SPEC, /BS-SPEC, /NON-STANDARD-SPEC from the Unused Profiles
to the Used Profiles.
Now let’s define the Snip Size of selected profiles, which is different from setting Snip Size in the Settings
tab. Snip Size for each Profile is defined and its application method is different from Min. Snip Size or Min
Snip Offset of Default Setting.
The material reference of profile can be decided from the Settings tab or specifications (SPCO) of a
selected profile.
Material information of Profile (SCTN) used in the support follows Matref of Specification (SPCO). But when
Support Profile (SCTN) is created keeping the attribute of Profile Specification through AOS, its Material
information can be easily defined if needed.
When Specification is selected, only Material information (MATREF) set in the Profile Specification is used.
When User Selections is selected, Material information of SCTN Element set by the user during support
creation is used.
When creating Supports, the Material information is input in the Matref of SCTN Element as shown. But
Material reference of original Profile Specification is not changed.
Information of Support Type and Size are covered in TM 2241 AVEVA Outfitting Supports - Designer Guide.
This section explains how values of Design Rule affect support models.
The information defined in the Support Type & Size Table is related to the previous step as follows.
Main Type Main Type is defined based on the value of the Support Template defined in the
MTP (Local Project) with AOS Project (Master Project).
Profile Spec. The Specification selected in the Profile Selection is only available.
Pad Material The Pad Material defined in the AOS Project (Master Project) can be selected.
Sub Type Sub Type is defined based on the value of the Support Template defined in the
MTP (Local Project) with AOS Proejct (Master Project).
Span Profile Specification applicable to Profile Spec. must be selected. Specification must be
selected in the Profile Spec.
Leg Pad Pad specification is saved in the AOS Project and is directly selected by the user
according to Leg Profile.
As shown above, all values of Size 60mm are Unset because this size is newly added.
Size 60mm
Subtype PSM-A01
Span Profile /BS-SPEC/45x45x6.0
Leg Profile /BS-SPEC/45x45x6.0
Leg Pad /PSM-PAD-01/TRIANGLE-80x80x8
However the following error message will be displayed when trying to create a support for a Pipe (Size
60mm)
This case is that Ancillary Type is not defined although Support Type and Profile Size are decieded.
All values of 60mm Size are set to Unset as shown because Catalogue and Specification suitable for 60mm
Size are not prepared.
There is a correlation between Design Rule and Support Library and according to circumstances Catalogue
and Specification should be managed together.
Rename the existing support frame and ancillary as follows. Refer to the previous chapter.
The exisiting Support frame PSM-A01 is not modified in the Local Project (MTP). Log into the AOS
Project.
Name EXE02_AREA
Description Exercise02 For Training
Type UBLTD4-MHG
Set the Pipe specification (for the Training project) /SP_DRN as a specific rule, define the above ancillary
against 80mm bore.
Change the Support Area into 403_ZONE. Set Pipe Specification /SP_DRN as a Common rule.
Using the Support area 403_ZONE and EXE02_AREA, check if the defined design rules are applied to
design models.
The AOS Project basically provides Ancillary Catalogue, Material, Sliding Pad Catalogue, etc. But the user
wants to frequently modify and add them and they should follows the specific rule such as Data Set (DTSE)
and Point Set (PTSE) to properly work within the AOS system. So this section explains how to easily add or
modify AOS Catalogue following the rule.
To add or modify Ancillary Catalogue / Specification, log into the Paragon module in the AOS project.
Select All Programs > AVEVA Marine > Design > Outfitting Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project AOS
Username SYSTEM
Password XXXXXX
MDB AOS
Module Paragon
For catalogue data about PSM, CSM and HSM, refer to the AVEVA
Outfitting Supports 12.1.SP4 Support Libraries.
P-Points have been created with the minimum points required, which are:
P-Point Description
1 Arrive Point
2 Leave Point
3 Bottom of Pipe (BOP)
9 BOP (Including geometry if required), i.e. bottom of the ancillary geometry
10 Left of Pipe
11 Right of Pipe
12 BOP
P1 and P2 are the arrive and leave points along the centre line of the pipe.
C:\PSM_ANCIL_UBLT_A1.txt.
Save as PSM_ANCIL_UBLT_A5.txt.
Navigate to /PSM-ANCIL/UBLY/A4, drag and drop the PSM_ANCIL_UBLT_A5.txt datal file into the
Command window and change the Function into UBLTA5.
For the next step, modify the created CATE by Modify > Category... As mentioned above, this example is
to create Type A5 which modify the U-bolt length. Therefore only PARA8 should be changed as shown
below.
Add the Ancillary Catalogue for Size 60mm which are created in Chapter 5.4.1.
Copying and modifying the basic Catalogue informaion is the easy way to create new Catalogue without the
loss of information.
To use CATE members SCOMs updated in the catalogue data, it should be registered as specification
component (SPCOs). Using the AOS Ancillary Spec Controller, the administrator can easily generate the
ancillary specification database. Once specification data is defined in the Paragon module, the ancillary
categories are usable in the Outfitting module. The user can set icon images for each CATE element and
they were stored in CATE’s ICON attribute.
The following example shows how to create new SPCOs with /PSM-ANCIL/UBLT/A5 (SCOMs) previsouly
created.
Select PIPE.
The administrator can identify Materials (for Ancillary), Catalogues and Specifications in each tab.
Icon files for ancillary are decided according to Naming Structure as follows.
Please refer to the attached file for ICON file marsuppattastrpa5.png. The general paths of Ancillary
ICON file are as follows.
Pipe %pmllib%'\aosaddin\icons\psmsubtype\
Cable Tray %pmllib%'\aosaddin\icons\csmsubtype\
HVAC %pmllib%'\aosaddin\icons\hsmsubtype\
To apply the new icon, enter the PML REHASH ALL in the Command Window.
If the information of Ancillary Catalogue (CATA) added is correct, AOS system automatically updates
Ancillary Specification via the function of Update Specification.
Save Work.
SPCOs added should follow the rule of AOS, which means SELEs are classified in the following order; 1.
Size 2. Materilal 3. Profile Thickness. Note that SPCO exists for Material and Profile Thickness respectively.
Therefore if Material or Profile Thickness is added, Update Specification must be operated in the same
way.
If a new Profile Thickness is added, run the Get Profile Thickness of AOS Ancillary Spec Controller,
which allows checking the added Thickness automatically. Please refer to AVEVA Outfitting Supports –
Administrator and User Guide for more information.
The user can define the Ancillary Type for Size 60mm added in
Chapter 5.4.1.
Move UBLTA5 types into the Used Ancillaries list as shown below.
The user can define Ancillary Type for Size 60mm in the Ancillary Type form as shown below.
Sliding Pad Catalogue and Specification are also created in the same way as Ancillary. But the function of
Update Specification is separated.
Here is a way to add new Size to the Sliding Pad Catalogue, which is different from Ancillary Catalogue.
For catalogue data about PSM, CSM and HSM, refer to the AVEVA Outfitting Supports 12.1.SP4 Support
Libraries located in <installed dir>\Marine\Design\OutfittingSupports12.1.SP4\PMLLIB\aosaddin\aosdata.
The administrator can identify Materials (for Ancillary), Catalogues and Specifications in each tab.
Informaion can be modified by right click on the Sliding PadSpec Controller which is same as
Ancillary Spec. Controller.
Save Work.
SPCOs added should follow the rule of AOS, which means SELEs are classified in the following order; 1.
Size 2. Materilal 3. Pad Thickness. Note that SPCO exists for Material and Profile Thickness repectively.
Therefore if Material or Profile Thickness is added, Update Specification must be operated in the same
way.
Material information of Ancillary and Sliding Pad is managed as a form of SDTE Element within the AOS
system. As mentioned previously, Ancillary and Sliding Pad Specification are dramatically changed
according to Material. This section explains the process of adding Material information and updating
Specification.
This section explains Material information within AOS system, not Component Reference (CMPD) of
SPCO. Please refer to Chapter D. PROPCON Data of AVEVA Outfitting Supports – Administrator and
User Guide for Component Reference (CMPD).
Ancillary UBOLT
Material MG
Description SS400GALV
Code UBLT
CE is moved to SDTE element applicable to the selected Material.To create a new Material copy the existing
Material information.
To modify the information of the newly created /PSM/UBLT-S5, change RTEXT Attribute into SS540 GALV
as follows.
Save Work.
Ancillary Specifications (SPCO) for S5 are newly added. Idenfity the added Specification in the following
Hierarchy and check if the Hierarchy is well-organised.
The Update Specification function allows identifying the changes to Material & Catalogue and updating
Specification.
© Copyright 1974 to current year. 80
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Marine (12.1)
Outfitting Supports – TM-2256
This section explains the way to delete Catalogue and Specification. The user deletes Catalogue and its
relevant Specifications are deleted by the AOS system. The function of automatically deleting Catalogue and
Specification is not provided. But when deleting Material in the AOS Sliding Pad Spec Controllor, the AOS
system automatically deletes relevant Specifications.
Note that deleting Catalogue and Specification can have a critical effect on the relevant Suppport model.
Especially modifying AOS Project (Master Project) affects all relevant Local Projects.
Althogh the Catalogue is deleted the Specification created based on /PSM-ANCIL/SPAD/SPRO/A1/60 still
remains as follows.
Running Update Specification in the Specification tab results in deleting Specification (SPCO) related to
/PSM-ANCIL/SPAD/SPRO/A1/60.
As for Ancillary Specifications, Specification (SPCO) is made up based on Profile Thickness which is
explained in Chapter 6.2. When deleting Profile Thickness relevant SPCO are searched and deleted as
follows.
All SPCOs related to Thickness 12.0mm are searched by running Collect Invalid Specification.
When modifying Profile Thickness changes are automatically applied to via the function of Get Profile
Thickness. The standard of identifying Thickness is as follows.
Get Profile Thickness (link label): Bring thickness of used profiles which are defined in Profile Selection.
Get Profile Thickness (text box): Enter thickness if there is no thickness in use for profile.
SPCOs searched in the Invalid Ancillaries can be directly deleted by clicking Delete SPCO. Those SPCOs
should not be deleted for this training.
Exercise 3 – Set Design Rule with New Subtype Support & Ancillary
This exercise is aimed at adding a new Subtype Support by copying and modifying the existing one.
Navigate to /MTP-TEMPLATE-J/ZONE.
Referring to the previous chapter, copy the existing support frame as follows
Specification /Std/FB/50.0x5-Flat-Bar
ROTATE BY -90
Description SPAN-J04
Function SPAN-J04
Delete the FITT Element (Endcut) below SCTN Element. The result is as follows.
Set J-type Subtype in the Support Type & Size table as follows.
7 Drawing Configuration
This chapter explains the template of AOS Support Sketch Drawing Production with the Template
Hierarchy and how to modify AOS Support Sketch Drawing Template using a task.
AOS Support Sketch Drawing is created via the Marine Drafting module but the information of Sketch
Drawing Template is defined in the Outfitting Draft module. AOS Project provides various Templates for
Support Sketch Drawing and various types of Templates can be regenerated based on the templates
provided from AOS.
The following shows the structure of Support Sketch Drawing Template provided from AOS Project.
To start the AVEVA Marine application, select All Programs > AVEVA Marine > Design > Outfitting
Supports 12.1.SP4 > Outfitting Supports
The AVEVA Marine – Outfitting Supports Login form appears, enter the following data:
Project AOS
Username SYSTEM
Password XXXXXX
MDB AOS
Module Outfitting Draft
Select Draft >Drawing Function Admin… and then Configure > Support Sketch Admin…
Information can be displayed on a drawing based on configurations for a project or customers. Also the
Drawing Function Manager with many functions required for the drawing will help the user to generate high
quality drawings.
Sketch Drawing Template (DRTMPL) the user wants to modify will be displayed in
Template(DRTMPL) the Selection List. Function Attribute of Drawing Template must be PSM,
CSM or HSM. Selected Sketch Template is displayed in the Main View and
the Frame of the selected View is highlighted.
View List Select one of the views that exist in the selected template.
Database Mode Confirmable: If the user changes any of views or sheet function parameter,
system displays the confirm window before applying the changes.
Writeable: Promptly apply the changes without confirm message.
Select the templates of Sketch Template in sequence and check if the relevant Template Drawing is open in
the Main View. Check if the relevant view is highlighted by selecting views of View List.
The values applied to Sketch Drawing Template are categorised in the following order; 1.Template 2.Sheet.
Check the Functions of the selected View and change their values.
Function on Current View Display the functions (TASK) applied to the selected View in the View List.
View Function on Library Display the functions (TASK) included in the selected Sketch Department
(DEPT).
View Function Parameters Display the parameters included in the selected Function (TASK).
Functions displayed in the Functions on Current View can be identified in the TASK layer of the selected
View. Move the Add View Title from View Function on Library to Function on Current View. Check the
Add View Title added in the TASK layer.
The order of TASK is the same as Function List’s and TASK is performed according to this order.
This order can be modified by using the option list (Up, Down),
which is promptly applied to the Hierarchy.
A new TASK Add View Title is applied to the selected View (/PSM-ABA-A4-B/S1/V3). The result is as
shown below.
This section explains the way to modify details of Functions added. First, select Add View Title in the View
Function on Library and identify a modifiable Parameter List of the Function in the View Function
Parameters.
Text Height 8
Text Colour RED
The result is as shown below. Check the Text Height and Text Colour changed.
Select Define View Option from the Function on Current View and change a Parameter as follows.
Show Ancillary ON
Functions applied to the Drawing Template can be modified in the same way.
If additional information needs to be input or modified then the user can add a new Task. The new task is
executed (carried out) by the AOS system during Sketch Drawing creation.
Run the View Function Management by right clicking on the View Function on Library or Function on
Current View as shown below.
Default values of all Tasks of the Function Library can be modified in the View Function Management. New
Functions (Task) can also be added to the Function Library.
The value modified via the View Function Management is directly saved as Default in the Function Library.
Select /PSM_Project_Libraries in the Sketch Department and Add View Title in the Function on Library.
Text Height 3
Text Colour BLUE
Move Add View Title from View Function on Library to Functions on Current View.
Move Add View Title again into View Function on Library.
Check that the Default parameter value is changed according to Function Library data.
Here is a way to add a Function (Task). Prior to adding a Function, pmlfnc file should be prepared. Please
use the attached PML function file aosTraining.pmlfnc.
Select the Add Function button from the right mouse button list.
The PML Code Name is the name of pmlfnc file (aosTraining.pmlfnc) which should be saved in the
path of %PMLLIB%.
As you can see, the new Function is added. Let’s add necessary Parameters for the function.
Select the Add Parameter option from the right mouse button menu.
The input value of added Parameter is limited. For example, when Type is set to BOOLEAN, the user
can select ON/OFF regardless of value. If the definition of Value Type is needed, the user can modify
and add the parameter using Management Parameter. Please refer to AVEVA Outfitting Supports –
Administrator and User Guide for more information.
Message Print Function and Function Parameters are saved and managed as shown below.
The values of Parameter used in the Function can be categorised by Parameter Type. Parameter
Management allows the range of the categorised Type to be predefined. Therefore the parameter value of
the categorised type should be selected within the range defined.
Select the Parameter Management option from the right mouse button menu.
There are two types of Parameter (BOOL, DIR) which are predefined in the AOS system.
If the relevant type is predefined in the Management Parameter then the user can select and input one
among the predefined parameters. The value of Boolean (BOOL) / Direction (DIR) is predefined as
Default. The value of Colour (COLO) / Real (REAL) is defined in the system but this value is not
represented in the Parameter Types list.
Here is a way to register the parameter of the TEXT Type. The Parameter of TEXT Type was previously
added to Message Print Function.
The AOS system searches all parameter values of TEXT Type and the Parameter Values are displayed as
shown.
If the Parameter Type is TEXT then the Parameter Value should be selected between TEXT Type Message
01 and TEXT Type Message 02.
To add a new value of Parameter Type select the Add Parameter Value option from the right click mouse
menu.
The user can select one among the values defined in the Parameter Management by clicking on the TEXT
Type Parameter of Message Print Function.
Function or Parameter not provided from AOS can be applied by creating PML Function script and can be
easily managed through the View function management.
The definition of Function for Sheet is the same as View Function’s. But Sheet Function allows the values
set in the Backing Sheet (Text) to be defined via Parameter.
The subsections explain the way to modify the MTO Table of Sketch Drawing Template Sheet and the value
of Title Block by changing the Sheet Function.
Select Add MTO Table in the Function on Current Sheet. Modify the Profile Grouping Method into 2 in the
Sheet Function Parameter.
The result of Sketch Drawing is as shown below. Compare Profile Grouping Method 1 and 2.
The user selects Fill Title Block in the Function on Current Sheet. The configuration is almost the same
as explained previously, but the values of LINE and TEXT defined within the Sheet can be directly modified,
which is different from the View Function.
The Sheet contains the information of MTO Table and Title Block.
The values in the Title Block are similar to the Intelligent Text. So ?stage? entered as Stage value is
changed into a proper value during Support Sketch Drawing creation.
Add a new Function to the view of Sketch Drawing Template and change the Parameter values of the added
function.
The function of Message Print Function was added in the previous course.
Apply the changes to the View Function and Sheet Function and check the result. The user can directly
identify the result of the Message Print Function in the Command window.
This section explains the way to create a new Template by copying and modifying the Template basically
provided from the AOS Project.
Select Draft > General Admin…to copy the template provided from AOS.
Paste it.
The Element names below Template and Backing Sheet can be easily modified via the function of
Modify > Name…
The result is as shown below.
The new Template /PSM-ABA-A4-E is available. Check the Template /PSM-ABA-A4-E in the Support
Sketch Admin and Pipe Support Sketches as shown. The contents of this template are the same as
Template /PSM-ABA-A4-A.
To modify the MTO Table of Backing Sheet, the Intelligent Text provided from the AVEVA Marine Outfitting
Draft is used and Backing Sheet is modified via the Outfitting Draft.
Note that it’s better to change into Draft > Sheet Library… (Sheet Administrator) Mode for
convenience.
Please use the SNIP to Grid function and the Grid function.
STRA /PSM-Drawing-BackingSheet/A4-E
/MtoTable/ColumnLine4
TEXP /PSM-Drawing-BackingSheet/A4-E
/MtoTable/Weight
Check the changes to the Backing Sheet by opening the Drawing Template (/PSM-ABA-A4-E).
?pos?, ?mtrl_no?, ?desc?, etc. marked in the MTO List of the Template are the marking rule like the
Intelligent Text of the Outfitting Draft. They can be modified via Sheet Function.
Please refer to AVEVA Outfitting Supports – Administrator and User Guide for more information.
Align ?qty? with the Column, enter Specified String (?weight?) for Weight.
Other Texts such as ?connectname?, ?desc?,etc. exist. If a new Specified String is added to the
backing sheet, the relevant Sheet Function should be prepared in advance. Refer to
aosCreateMto.pmlfnc.
STRA /PSM-ABA-A4-E/S1/MtoEntries/ColumnLine4
TEXP /PSM-ABA-A4-E/S1/MtoEntries/Weight
Etext WEIGHT
The following shows the result of creating a Sketch Drawing by using the newly added Support Sketch
Template /PSM-ABA-A4-E. Compare it with Support Sketch Template /PSM-ABA-A4-A and confirm
differences.
Btext Etext
?pos? POSNO
?mtrl_no? MTRLNO
?desc? DESC
?qty? QTY
?weight? WEIGHT
?pos? CONNECT
Modify the names of Drawing Template and Backing Sheet as follows. Change the Element name.
Add Pipe Name Column to the MTO Table of Backing Sheet (/PSM-Drawing-BackingSheet/A4-EX04).
Change the Logo placed in the Title Block of Backing Sheet (/PSM-Drawing-BackingSheet/A4-EX04) by
using the following Symbol Template.
Change the Backing Sheet Reference (BSRF) of Drawing Template (/PSM-ABA-A4-EX04) into newly
added /PSM-Drawing-BackingSheet/A4-EX04. Modify the attributes if necessary.
Enter the Specified String (?connectname?) to input the proper information in the Pipe Name column.
Create a drawing using the Support Sketch Template added. The result is as shown below.