TM-2120 AVEVA Marine (12.1) System Administration (Basic) Rev 3.0

149  Download (0)

Full text


AVEVA Marine


System Administration



Revision Log

Date Revision Description of Revision Author Reviewed Approved

27/09/2011 0.1 Issued for Review SK / WR

09/10/2011 0.2 Reviewed SK / WR FP / MZ

25/10/2011 1.0 Issued for Training 12.1 SK / WR FP / MZ SH

02/12/2011 2.0 Issued with latest copyright footer CF CF

30/10/2012 2.1

Cache Manager and Optional Upgrade added. Design Reuse exercise revised to use AMT

SK / WR / MZ

02/11/2012 3.0 Issued for Training 12.1.SP3 SK / WR / MZ SK/WR WR


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

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.

Visit our website at


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.


AVEVA Marine (12.1) System Administration (Basic) TM-2120


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 ... 9 1.1 Aim... 9 1.2 Objectives ... 9 1.3 Prerequisites ... 9 1.4 Course Structure ... 9

1.5 Using this guide ... 9

2 Installation and Setup... 11

2.1 Installation of FlexMan 5.2 ... 11

2.2 Installation of the AVEVA Marine (12.1) Application Product Software ... 16

2.2.1 Automatic Install of the Cache Service ... 16

3 Project Access Verifying Installation... 21

3.1 Installation Projects ... 21

3.2 Adding Project Environment Variables to the Batch File ... 22

3.3 Starting the AVEVA Marine (12.1) Application ... 23

3.4 Optional Upgrade ... 24

4 Creating a New Project ... 25

4.1 Project Creation Wizard ... 25

4.1.1 Project Variables ... 25

4.1.2 Adding Project Details ... 27

4.2 Existing Projects ... 27

Exercise 1 - Project Creation ... 28

5 Database Administration ... 29

5.1 Teams and Users ... 30

5.2 Creating Teams ... 31

5.3 Creating Users ... 32

5.3.1 Create User as a Copy of the Existing User ... 34

5.3.2 Creating Users using the Access Control Assistant ... 34

Exercise 2 - Teams and Users ... 35

6 Creating Databases ... 37

6.1 Data Base Types ... 37

6.1.1 Administration Databases ... 37

6.1.2 Model Databases ... 38

6.2 Creating a Design Database ... 38

6.2.1 Create SITE ... 39

6.2.2 Database Access Mode ... 40

6.2.3 Database Access Restrictions ... 41

6.2.4 Controlled Databases ... 41

6.2.5 Protection ... 41

6.2.6 Reference Only Databases ... 42

6.2.7 Area Number, DB Number and File Number ... 42

6.3 Creating a Catalogue Database ... 43

6.3.1 Creating Namesequence Database ... 44

6.4 Copied Databases ... 44

Exercise 3 - Database Creation ... 45

7 Foreign Databases ... 47

7.1 Including and Copying Foreign Databases ... 47

7.1.1 Including Databases from the MAS Project ... 47

7.2 Copying a Foreign Database from the MTP Project ... 48

7.3 Excluding Foreign Databases ... 48

7.4 Deleting Databases ... 48

7.5 Modifying the setup of the Admin Elements Form ... 49

Exercise 4 - Copying and Including Foreign Databases ... 50

8 Multiple Databases (MDBs) ... 51

8.1 Creating MDBs ... 52

8.2 Database Order in the MDB ... 53

Exercise 5 - Creating MDBs ... 54


9.2.1 Project Setup Excel Spreadsheet - Teams ... 56

9.2.2 Project Setup Excel Spreadsheet - Users ... 57

9.2.3 Project Setup Excel Spreadsheet NT Authenticated Users ... 57

9.2.4 Project Setup Excel Spreadsheet Databases ... 58

9.2.5 Project Setup Excel Spreadsheet Included Foreign Databases ... 58

9.2.6 Project Setup Excel Spreadsheet Multiple Databases... 59

9.3 Starting the Excel Import Form ... 59

9.4 Admin Database Rollback ... 61

Exercise 6 Project Setup Excel Import ... 62

10 Project Replication ... 63

10.1.1 Replicate Project Data ... 63

10.1.2 Replicate Project Structure ... 64

Exercise 7 Project Replication ... 65

11 Hull Top Level Elements ... 67

Exercise 8 - Creating Hull Top Level Elements ... 68

12 Testing the AVEVA Hull and Outfitting 12.1 Access ... 69

12.1 Testing the Access ... 69

Exercise 9 - Testing AVEVA Marine (12.1) Access ... 73

13 References between Databases ... 75

13.1 Checking Inter-DB Macros ... 75

13.1.1 Finding the Names of the Inter-DB Macros ... 76

13.1.2 Checking that the Nozzle CREF is not Set ... 76

13.2 Running the Inter-DB Macros ... 76

13.3 Deleting Inter-DB Macros ... 77

Exercise 10 - Running Inter-DB Macros ... 77

14 NT Authentication ... 79

14.1 Setting up NT Authentication ... 79

14.2 Testing the NT Authentication ... 80

Exercise 11 - NT Authentication ... 80

15 Sharing AVEVA Hull and Outfitting 12.1.SPx Projects and Files ... 81

15.1 Sharing Files ... 81

15.2 Cache Manager ... 83

15.3 Creating Shortcuts ... 84

15.4 Change Start in Directory ... 84

15.5 Shortcut Arguments ... 85

Exercise 12 - Creating Desktop Shortcut ... 85

16 Project Administration ... 87

16.1 Locking the Project Database ... 87

16.2 Options under the Admin Menu ... 87

16.3 Abnormal Exits ... 88

16.4 Display Menu ... 88

16.5 The Query Options ... 88

16.5.1 User Status Form ... 88

16.5.2 User List Form ... 89

16.6 Team List Form ... 89

16.7 Database List Form ... 89

16.7.1 DB Session Form ... 90

16.7.2 MDB List Form ... 90

16.7.3 Stamp List Form ... 90

16.7.4 Data Access Control Audit Form ... 91

16.7.5 Database Sets Report Form ... 91

16.8 The Settings Options ... 92

16.9 The Utilities Options ... 92

16.9.1 Integrity Checker Option ... 92

16.9.2 Sending Message... 93

16.10 The Project Options ... 93

16.10.1 Project Information ... 93

16.10.2 Font Families ... 94

16.10.3 True Type Fonts ... 95

Exercise 13 - True Type Fonts ... 97

16.10.4 Module Definition ... 97


AVEVA Marine (12.1) System Administration (Basic) TM-2120

16.11 Deleting Phantom Users / Claim Lists ... 99

16.12 The Data Options ... 100

16.12.1 Change Management ... 100

16.12.2 Backtracking the Databases (Command Window) ... 103

16.12.3 Inter-DB Macros ... 103

16.12.4 Inter-DB Macros ... 104

Exercise 14 - Database Sessions ... 104

17 AVEVA Hull and Outfitting 12.1.1 Environment Variables ... 105

17.1 Environment Variable PDMSWK ... 105

17.2 Environment Variable PDMSUSER... 105

17.3 Serialisation Files... 105

17.4 Environment Variable PDMSUI ... 106

17.5 Environment Variable PMLLIB ... 106

18 Data Integrity Checker ... 107

18.1 Main Checks ... 107

18.2 Causes of database corruption ... 107

18.3 Database Storage Statistics ... 107

18.4 Preparatory Steps before Checking Starts ... 108

18.5 Using DICE ... 108

18.5.1 Check options ... 108

18.5.2 Settings options ... 109

18.6 Macros ... 110

18.7 DICE Output ... 111

18.8 The Error Report ... 112

18.9 The Report Summary ... 112

18.9.1 Fatal Errors ... 112 18.9.2 No Structural Errors... 112 Exercise 15 - Dice ... 112 19 Lexicon ... 113 19.1 Lexicon GUI ... 113 19.2 Lexicon Hierarchy ... 114 19.2.1 Dictionary Database ... 114 19.3 Lexicon Options ... 116 19.4 Display Options ... 116 19.5 Edit Options ... 116

19.6 Schematic Model Manager Options ... 117

19.7 Dictionary Explorer ... 117

19.8 Current Element Editor ... 118

19.9 Creating a UDA (Worked Example) ... 118

19.9.1 ... 119

19.10 Creating a USDA (Worked Example) ... 120

19.11 Creating UDET (Worked Example) ... 121

20 Assembly Planning Properties Creation ... 123

20.1 Creating an Assembly Working Location ... 123

Exercise 16 - ... 125

21 Status Management Configuration ... 127

21.1 Creating a Status World (Worked Example) ... 128

21.2 Creating a New Status Definition ... 129

21.3 Creating a New Status Value ... 130

21.4 Setting the Transitions ... 131

21.5 Testing the Status Management Configuration. ... 132

22 Appendix A - Backing up Data... 133

22.1 Daily Backups ... 133

22.2 Typical Backup ... 133

22.3 Project Backups ... 133

23 Appendix B Design Resuse - Settings ... 135

23.1 Defaults ... 135

23.2 Renaming options ... 135

24 Appendix B1 - Export from source project ... 137


24.2.2 Drag and Drop from Explorers ... 139

24.3 Transfer set ... 140

Exercise 17 Design Reuse ... 140

25 Appendix B2 - Import into the target project ... 141

25.1 Import and release surface file into target project ... 141

25.2 Hull block reference objects import ... 142

25.3 Hull reference objects ... 142

25.4 Project catalogue and steel quality ... 142

25.5 Manufacturing packages ... 142

25.6 Create a new RSO envelope ... 142

25.7 Model import from transfer set ... 144

25.8 Nesting import ... 145

25.9 Outfitting model import ... 146

25.10 Target model check after import ... 146

Exercise 18 Design Reuse ... 146

26 Appendix B3 Hull Model + Outfitting (Working Example)... 147

26.1 Export to transfer set ... 147





AVEVA Marine (12.1) System Administration (Basic) Training Course will enable the Trainee to create and maintain AVEVA Marine (12.1) projects.



Over the duration of the course the Trainee will be given a basic understanding of how to administer an AVEVA Marine (12.1) Project.



Set up a new AVEVA Marine (12.1) project, controlling which users have access to which databases.

Set Hull top level elements using DBPrompt utility. General system configuration.

Administer projects, including change management and setting AVEVA Marine (12.1) fonts. Control user access to AVEVA Marine (12.1) modules.

Check data integrity.

Create DB Listings and understand change highlighting. Create UDAs (User Defined Attributes)

Create UDETs (User Defined Element Types)



Trainees should be familiar with AVEVA Marine (12.1) and Microsoft Windows


Course Structure

Training will consist of oral and visual presentations, 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.


Using this guide

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 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 bold courier new font.




Installation and Setup

This chapter covers the installation of license software and application software and the configuration of the Flexman license utility.


Installation of FlexMan 5.2

Insert the AVEVA Marine (12.1) software products disk into the computer. The disk will autostart and display a welcome page. Click the Click for contents link.

The screenshots displayed in this chapter of the manual are indicative only and may vary depending on the installation version being installed.

The contents of the disk are listed, showing the Application Products and the Utility Products. From the Utility Products section select the current version of AVEVA Flexman.

Then select the option to suit your operating system platform.

The Release Documents screen appears. Firstly, read the release notes. Once this has been read and understood select the INSTALL link.


The Microsoft Internet Explorer form appears asking for confirmation for running active content from CD on your computer. Click the OK (or YES) button. A File Download Security Warning form now appears, Click the Run button

A further Internet Explorer Security Warning form appears as the publisher could not be verified, click the Run button. The FlexMan Setup form appears, click the Next button.

The FlexMan Setup form now changes to allow Custom Setup. To modify selection of features to be installed, click the right mouse button on the selected feature and select the desired installation option from the menu available. By default all the required features are pre-selected to be installed. Click the Next button. The form now changes to Ready to install FlexMan, click the Install button.

Browse may also be used to change the installation path.

The installation starts and is shown in the Status bar.


AVEVA Marine (12.1) System Administration (Basic) TM-2120 When the installation is complete, the FlexMan setup form asks the user to click the Finish button to exit and setup.

Now using Windows Explorer, select your Flexman installation folder e.g. C:\AVEVA_X64\FlexMan5.2 or C\:AVEVA\FlexMan5.2 and place your AVEVA Marine (12.1) license file supplied by AVEVA here.

There are some limits for the license file, the host name can only have 64 characters and the licence file lines

\ continuation character.

Now from the Start menu select All Programs > AVEVA_X64 > FlexMan5.2 > lmtools.exe (LMTOOLS)

The LMTOOLS form appears. On the Service/License File tab, select Configure using Services. Then, select the Config Services tab.

Key in the Service Name AVEVA Marine

Use the Browse button to browse for the Path to the lmgrd.exe file, the Path to the license file and the Path to the debug log file. These are all located in the FlexMan5.2 folder.

Tick the two boxes Start Server at Power Up and Use Services

Then click the Save Service button.


Before running any AVEVA product, the path to the AVEVA license server needs to be set. From the Start menu select All Programs > AVEVA > FlexMan 5.2 > FlexMan Configuration Tool. In the Select

Application Vendor pull-down menu select AVEVA(CADCENTRE). In the System registry (32 bit) and or (64 bit) field key in 744@<Computername> i.e. 744@ukcaml4039. Then click the Set button.

Click the Save and Exit button when finished to close the form.

Generally 744 tcp-port number is used in AVEVA Marine (12.1). This tcp-port number can be changed by the system manager. See your license file.

Only in extreme circumstances edit the registry to clear out any duplicate license path entries. From the Run command in the Open field key in regedit., click OK. Under the HKEY_LOCAL_MACHINE

> SOFTWARE > FLEXlm License Manager select the LM_LICENSE_FILE that is incorrect, then click the right mouse button and select from Modify, Delete or Rename


AVEVA Marine (12.1) System Administration (Basic) TM-2120

The License Server has not yet been started. To start the license server the user can either, Stop and restart your computer, which will start the AVEVA Marine license service or Start the license server manually by opening the Start/Stop/Reread tab and click the Start Server button.

To check that your license server has started correctly the user can view the contents of the license server debug log file by opening the Config Services tab and then select the View Log button.

For some common faults and workarounds see LicenseAdministration.pdf in the Flexman installation folder, or visit:



Installation of the AVEVA Marine (12.1) Application Product Software

If a previous version of the AVEVA Marine (12.1) software has been removed from the machine prior to installing the new software version, the serialization files located in C:\Documents and Settings\<user name>\Local Settings\Application Data\Aveva and the installation folder AVEVA\Marine are to be deleted.

Remember to move any project you would like to keep which is located in the AVEVA\Marine folder before removing the software.

2.2.1 Automatic Install of the Cache Service

The database caching service stores Dabacon database pages on the local disk to improve performance where there is repeated reading of project data across a computer network. The cache must be active on the machine running the application, but the cache is shared by all applications and users running on that machine. If the cache service is not active then database access is via the network file system, as usual. The cache service will be automatically installed if

Message Queuing (also known as MSMQ) is activated on your machine. This is done using the

Start > Control Panel > Add or Remove

Programs facility.

Where MSMQ is not active the cache service will not be installed.

The Cache Manager is covered later in this course.

Now that the FlexMan has been set up and MSMQ enabled (if required), select from the Application Products section AVEVA Hull & Outfitting


AVEVA Marine (12.1) System Administration (Basic) TM-2120

The Release Documents for the AVEVA Marine Hull & Outfitting form is displayed click the INSTALL button.

The Microsoft Internet Explorer form appears asking for confirmation for running active content from CD on your computer. Click the OK or YES button. A File Download Security Warning form now appears, Click the Run button.

A further Internet Explorer Security Warning form appears as the publisher could not be verified, click the Run button.

Windows Installer initiates the AVEVA Marine (12.1) setup form. On the AVEVA Marine (12.1) Setup form click the Next button.


The Custom Setup selection form is displayed for the user to select the features to be installed. By default the AVEVA Marine Suite and Initial Design are pre-selected for installation. To install Hull and Outfitting Marine Sample Projects, place mouse cursor on the icon next to Marine Sample Projects, from the right mouse button context sensitive menu chose Entire feature will be installed on local hard drive from the options. The AVEVA Marine (12.1) Setup form now allows the administrator to change the destination folder by selecting the Browse button if required. When the destination folder has been set, click the Next button.

For the purpose of the Training please make sure that the Area Based ADP, Multi Discipline

Supports and the Schematic 3D Integrator are installed

The Marine setup form now requests Advanced Configuration settings for customers with existing projects and

infrastructure. By default .bat files will be installed with StartMenu Shortcuts and Desktop Shortcuts, these can be selected as required.

The Install Configuration form allows the configuration of folder paths for the pdmsuser, pdmswk and the DFLTS. The form now informs the administrator that the software is ready for installation. If no modification of destination folder is necessary, click the Install button. Otherwise, click Back button to go back through the steps and change the necessary information. The form changes to show the Setup status.


AVEVA Marine (12.1) System Administration (Basic) TM-2120

Once the Installation is complete, the form will change to inform the administrator that the installation is completed. Click the Finish button to exist form.




Project Access Verifying Installation

AVEVA Hull and Outfitting 12.1.SPx makes extensive use of Environment Variables; they are used to define the location of the AVEVA Marine (12.1) software and Projects. In this chapter we are going to investigate the setting and the location of AVEVA Marine (12.1) Projects with the use of the Project Environment Variables for this we will be using the installed Marine sample project (MAR).


Installation Projects

AVEVA Marine (12.1) requires several a number of directories;

these are set for each project. Project names are made up using 3 Characters. i.e., for a Project e.g. MAR MAR000 Project database directory.

MARDFLTS Project defaults directory. MARDIA Project Visio diagram directory.

MARDRG Project Marine Drafting drawings directory. MARDWG Project Final Designer drawings directory. MARISO Project Isodraft Options directory.

MARMAC Project Inter-DB connection macro directory. MARMAR Project Hull directory.

MARPIC Project Draft Picture File directory. MARSTE Project Visio Stencil directory. MARTPL Project Visio template directory. MARINFO Project Information directory. MARREPORTS Project reports directory

MARPSI Project Pipe Stress Interface directory.

AVEVA Hull and Outfitting 12.1.SPx installs several sample projects from the AVEVA Marine (12.1) installation CD.

CPL MDS Catalogue Project

LIS MDS Catalogue Project

MAR Marine Sample Project (Metric)

MAS Marine Master Catalogue

MDS MDS Project

MDU MDS User Defined joints Project

PSL MDS Catalogue Project

We are going to test our AVEVA Hull and Outfitting 12.1 installation using the installation sample project MAR. The environment variables for the MAR project have been set up in the project batch file called

evarsMarine.bat project directory MAR. The evars.bat file held in the

AVEVA\Marine\OH12.1.SPx directory calls for the project batch file, setting all the project variables. The evars.bat file is called from the marine.bat file which is executed when AVEVA Hull and Outfitting 12.1.SPx is started from the start menu All Programs > AVEVA Marine > Design > Marine 12.1.SPx > <Required Application>

All Catalogue information for the MAR project is held in the MAS project so the environment variables for MAS have also been set. The Administrator will check the settings of MAR000, MARPIC, MARISO, MARMAC, MAS000 and MASPIC.

Normally the MASMAC and MASISO will never be required as no Design or Isometrics will be produced in the master catalogue project.


By default the supplied AVEVA Marine (12.1) projects are held in a project directory under the AVEVA

Marine (12.1) executables directory.

Navigate using the Windows Explorer or My Computer to the Project directory, in this example C:\AVEVA\Marine\Projects12.1.SPx\ The user can now see the installed AVEVA Marine (12.1) Projects


Adding Project Environment Variables to the Batch File

If desired to locate the project to another location on your network it will be necessary to change the project environment variables.

Modifications or additions to the Project Environment Variables should be made in the project s batch file e.g. evarsMarine.bat. This file is normally in the project folder.

Using the Windows Explorer navigate to the project batch file e.g. evarsMarine.bat file and open it for editing. The following is an example of how these project variables might be set:

A project loaded onto a machines hard disk

A Project loaded onto a server machine

The IP address \\\ points to the server. This could have also been the server name or another machine name that holds the project i.e. \\ukcaml3459\

Always make modifications to environment variables in the batch file, do not include them as system variables as this may create conflicts between different AVEVA Marine (12.1) versions.

If all projects are located on a server, it is appropriate to have the evars.bat on that server otherwise it would be necessary to edit the evars.bat file at each workstation. To ensure that only one evars.bat file needs to be updated (the one on the server) when a project is added, the marine.bat file should be set to point at the server evars.bat file.


AVEVA Marine (12.1) System Administration (Basic) TM-2120


Starting the AVEVA Marine (12.1) Application

To start AVEVA Marine (12.1), select the application to be started from within the AVEVA Marine menu options: Click Start > All Programs > AVEVA Marine > then follow the path to the program you wish to start or alternatively use the shortcut icons on the desktop to take you to the folder containing shortcuts to the Marine executables. Expanded Start menu options for Design show opposite:

The AVEVA MARINE application login box appears the Project, Username and MDB are chosen by using the option arrows adjacent to each entry (except for SYSTEM which is a free user

and does not appear in the drop down list) whilst the Password must be entered using the keyboard. The Options: Integrate Engineering and Schematics setting is relevant when Outfitting is being used alongside Engineer and/or Diagrams, and it affects the visibility of Engineering and Schematic data in the 3D Outfitting modules. Engineering and Schematic data will be visible, read-only, when this option is checked. The options are determined by the project set- AVEVA Hull and Outfitting 12.1.SPx is initialised.

Select the Project mar, key in Username SYSTEM, key in the Password XXXXXX, then select the MDB ALL_NO_MDS, click Login.

The first time Hull Design module is started a warning be displayed.

Click OK.

When module has started, click the File menu and select the application to be used.

A default screen layout will be displayed comprising the general menu bar for the application and a Design Explorer window showing all the objects from the current design project database.

To exit the AVEVA Hull and Outfitting 12.1 application select Design > Exit from the



Optional Upgrade

The database upgrade framework is extended with a concept of optional upgrades. The software requires a database to be upgraded to a certain level to be granted write access to the database. But beyond that mandatory upgrade level it is now possible to apply further optional upgrade levels to acquire new enhanced features.

The benefit of optional upgrades is that 12.1.SP3 software operates with databases even though this upgrade has not been applied, i.e. the upgrade is optional. Through this you can deploy and install 12.1.SP3 and share project data with previous software versions.

The upgrade level denoted 12010301 is an optional upgrade provided by release of 12.1 SP3 and contains the following upgrade items.

Storing of a space arrangement definition.

Storing of coordinate system entities under a GENPRI element.

Introduce marine drawing type as table attribute. Applicable for PADD databases.

Marine Drawing Object applied with new Layers and IDs for outfitting models. Applicable for PADD databases.

New Marine Drawing Types. Applicable for PADD databases.

The DBUP command is extended with an additional qualifier OPTIONAL to apply an optional upgrade version e.g. DBUP PROJECT TO LATEST OPTIONAL.

The upgrade number may also be given directly e.g. DBUP PRO TO 12010301

The Q UPGRADE LIST is extended to give a short notice for upgrade versions that are optional.

Db upgrade: 12010301, Upgrades the database to 12.1.SP3, version 1. Optional upgrade version.

As soon as a database is upgraded it is no longer compatible with 12.1.SP2 or earlier versions. If backtracking sessions on an upgraded project, if the backtrack takes you to a session before the upgrade was performed, then that database will need to be upgraded once again.




Creating a New Project


Project Creation Wizard

A Project Creation Wizard enables the administrator to create the project structure and an environment variable batch file without the need to use manual techniques.

Activate the Project Creation Wizard by selecting All Programs > AVEVA Marine > Design > Marine12.1.SPx > Project Creation Wizard.

The AVEVA Marine (12.1) Project Creation Wizard form appears, key in the Project ShipAMA, the CODE AMA and key in the Address

C:\AVEVA\Marine\OH12.1.SPx\project\ShipAMA where the project will reside.

The project Address may be changed by typing or browsing but by default it will be automatically populated with the default project path. The

address folder has to be created or should already exist before selecting the Project Variables, Create, buttons etc.

The Project Creation Wizard only allows changes before the Project is created. Once the Project is created changes can be done manually using the available utilities.

4.1.1 Project Variables

The Project variables Button primarily is used to display the location where the project will be created, but can be used to create extra project areas for splitting the project across disks.

From the Project Creation Wizard form click the Project Variables button, the Project Variable form appears.

If variables DWG, INFO, REPORTS and PSI and appropriate folders assigned to each variable are to be included in the new project, check appropriate checkboxes in the Project Variables form shown above.

(26) Extra Project Areas

Using the Extra Project Areas Button Project, additional areas can be created, these were used in the past when disk space was at a premium and are used by some customers to split projects so that they can provide windows file protection.

To add Extra Project Areas use the scrollable menu to select the number of extra project areas to create. The additional Areas and Values are automatically added to the Project Areas and are created when the OK button is clicked.

For the training we will only use the main area so the Extra Project Areas should be set to 0 Marine Variables

The Marine environment setup form is displayed the administrator can make changes to the variables in the project definition file.

From the Project Variables form click the Marine Variables button, The Template path form now appears, change the path as required and then click the OK button.

The Marine environment setup form is displayed showing all the Variables and Values, then select File > Save. The Project Variables form is displayed once again now select File > Close.

This file can be launched through the Admin module. Select Project > Marine environment setup .


AVEVA Marine (12.1) System Administration (Basic) TM-2120

4.1.2 Adding Project Details

The Details button is used to set the project details; this is used to populate the information forms in Outfitting Design and Admin modules.

In Marine projects, the Number value must be the same as the Project value.

From the Project Creation Wizard form click the Details button, the Project Details form appears. Key in the Name System Administration Training Project, the Description System Administration Training and, if required, a Message. Then click the OK button.

Once the details and project variables have been configured, click on the Create button to create the new project.


Existing Projects

From the Project Creation Wizard form Click the Existing Projects button. The Existing Projects form is displayed with the newly created project shown.

The Existing Projects form lists information about existing projects. This form is intended only for browsing the list of existing projects, and cannot be used to change existing projects. It can however be filtered by Project or Code in the drop down box, and then search the list for a string by entering a value in the textbox. Click the Cancel button to close the form.


When the project has been created a ProjectInfo.xml file is written / updated in the PDMS folder, this file can be opened by using the windows explorer and navigating to C:\AVEVA\Marine\OH12.1.SPx\PDMS\

If for any reason the project creation fails, the references to that project should be removed from this file to allow the user to re-use the project name.

The evars.bat file is also updated to include the path to the new project.

Exercise 1 - Project Creation

1. Create a new project AMA using the Project Creation Wizard.


Chapter 5


Database Administration

To start AVEVA Marine (12.1) Admin utility select All Programs > AVEVA Marine > Design> Marine 12.1.SPx > Admin

After initialising the application the AVEVA Marine (12.1) Login box appears. The Project, Username and MDB are chosen by using the option arrows adjacent to each entry (except for SYSTEM which is a free user and does not appear in the drop down list) whilst the Password must be entered using the keyboard. The options are determined by the project

set-AVEVA Marine (12.1) is initialised.

Enter the Project ShipAMA, Username SYSTEM, Password XXXXXX, and then click OK

No MDB needs to be set to go into Admin module

The Admin default screen layout will be displayed comprising of the main pull down menus, the Admin Explorer, the Admin elements form, and the Access Control Assistant form, also available from the Display pull down are the Attributes form and the Search utility.

Most of the admin elements will be created using the Admin elements form. Currently the Access Control Assistant form can only be used for creating users and for Data Access Control (DAC).

It would be normal practice for the system administrator at this point to change the system administrator password (Username = SYSTEM and Password = XXXXXX) to a new one for security reasons. However for the purposes of this System administrator training we will not change it.



Teams and Users

In AVEVA Marine (12.1) each database belongs to one Team only. Ownership of a database is established by the naming convention and has the format i.e. TeamName / DatabaseName. Users are defined by name and password, which they enter when starting the AVEVA Marine (12.1) application.

Users are normally members of Teams. Any user belonging to a Team will have write access to the databases owned by the Team.

Example of Teams and Users:

Team Description User / Password Owning the database(s) Type

CATA Project Catalogue Team CATA / CATA CATA/PIPE CATA







ISO Isometric Team ISO / ISO



SCHEMATICS Schematics Team SCHEM / SCHEM SCHEMATICS/DIAGRAMSS SCHE In addition, the following Teams and Users will be needed for the administrative functions:

Team Description User / Password

PARAGONADMIN Paragon Administration Team PARADM / PARADM DESIGNADMIN Design Administration Team DESADM / DESADM

DRAFTADMIN Draft Administration Team DRAADM / DRAADM

ISOADMIN Isometric Administration Team ISOADM / ISOADM CATADMIN Catalogue Administration Team CATADM / CATADM


AVEVA Marine (12.1) System Administration (Basic) TM-2120


Creating Teams

To create a team, select from the Elements section of the Admin elements form the pull down list, choose Teams, now from the form click the Create button.

The Create Team form appears, key in the Name CATA, the Description Project Catalogue Team and click the Apply button.

Type the Team Name CATA

This process is repeated until all the necessary teams are created. If modifications are required, select from the Admin elements form the team to modify and click the Modify button. Once the Modify Team form appears make the necessary changes and then click the Apply button and then click the Dismiss button to close the form. The Attributes form may also be used to edit fields which are not greyed out.

If the Lock box is ticked all attributes will be greyed out (to refresh the view select a different node in the Explorer then reselect the previous node).


The Teams are now all shown.


Creating Users

To create a user, select from the Elements section of the Admin elements form the pull down list, choose Users, now from the form click the Create button.

The Create User form appears. Key in the Name CATA and the Description Project Catalogue User. On the form, from the Project Teams section select Project Team CATA and use the arrow to add it to the Team Membership section.

To set password, click on the Set Password button. Change Password form will appear.

Key in the password CATA into the New Password field and


AVEVA Marine (12.1) System Administration (Basic) TM-2120

Password length can b

The User Security has two levels:

Free May enter all modules and may update any databases.

General May not enter the restricted modules, which are usually the administration modules of ADMIN and LEXICON.

Now click the Apply button.

This process is repeated until all the necessary users are created.

The Users are now all shown.

If modifications are required, select the user from the Admin elements form and click the Modify button.

Once the Modify User form appears make the necessary changes and then click the Apply button and then click the Dismiss button to close the form.

Modify User form, click the Reset Password button. The Change Password form will appear.

Key in the new password into the New Password field and confirm it by re-typing it into the Confirm New Password field. Click the OK button

password and exit from the form.


5.3.1 Create User as a Copy of the Existing User

To create a new user by copying an existing user, click the Copy button and on the Copy User form key in the name, password, security and description for the new user. Confirm copying and exit the form by clicking OK button.

When creating a new user by Copy User functionality, the new inherits the same team membership as the user being copied.

It is not possible to execute the copy user function without setting the password for the new user. Entry and confirmation of a password for the new user are compulsory.

5.3.2 Creating Users using the Access Control Assistant

It is possible to create users using the Access Control Assistant, from the Access Control Assistant form, select the Users tree and click the right mouse button and from the pop up select New user. Key in the User name ANOTHER (refresh the list if necessary). Using the TAB button on the keyboard, switch to the User description field. Key in the description Windows User. To set the password, use option for modifying user from the Users Admin element form.

The AVEVA Marine (12.1) User name should always be in upper case

New user, windows user, can now be dragged to the required Team / Teams using the left hand mouse button.


AVEVA Marine (12.1) System Administration (Basic) TM-2120

Exercise 2 - Teams and Users

1. Create the Following Teams and Users for the AMA project. The users should be members of their respective teams.

2. The Associations team will have a number of members, ASSEMBLY, HULLF, HULLA, HULLDES, PIPEA, and PIPEF. It will also be necessary to add other users to teams to give required access.


Chapter 6


Creating Databases


Data Base Types

An AVEVA Marine (12.1) project can contain different types of databases described as follows further.

6.1.1 Administration Databases

The SYSTEM database holds the access control data for the model data and modules.

There is only one, SYSTEM database in the Project Directory. It holds administrative information about the composition and use of the project, including the following:

A list of all the databases which are available in the project.

A list of all Users who can access the databases, and the Teams to which they belong. A list of modules available in the project.

The SYSTEM database is a multiwrite database, which means that there may be more than one user in ADMIN at any time but these users cannot modify the same part of the database at the same time.

In the COMMS database the information are stored about who is using which module and which model databases are available.

Each user has a separate area of the COMMS database, which can be accessed in write mode, and so can other users in the project.

The COMMS database is a single-access database. Users queue for the COMMS database on entry into the module.

The MISC database stores inter-user messages, and inter-database macros.

This database can only be opened in write mode by one user at a time, but many users can read from it. All users need to be able to write to this database, but only when they are sending messages or writing inter-database macros, or deleting messages and macros. All users can read from the inter-database at any time

The MISC database is a single-access queued database, that is if a user wants to write to the MISC database must wait until any other users writing to it have finished


6.1.2 Model Databases

DESIGN (DESI) databases contain all the design information for the project. DRAFT (PADD) databases contain data about drawings produced by Outfitting Draft and Marine Drafting.

CATALOGUE (CATA) databases contain the project catalogue and specifications.

PROPERTIES (PROP) databases can contain material properties, and be referenced to by the catalogue.

DICTIONARY (DICT) databases contain the definitions of User-Defined Attributes (UDAs), User Default Element Types (UDETs) and User System Defined Attributes (USDAs) as set up in LEXICON.

ISODRAFT (ISOD) databases contain spool drawings produced by Spooler. SCHEMATIC (SCHE) databases contain P&ID (Schematic) information. MANUFACTURING (MANU) databases contain detailed manufacturing data. NAMESEQUENCE (NSEQ) databases store name sequences.

ENGINEERING (ENGI) databases for engineering tags.

Each project can have only one of each type of administration databases and one Namesequence database (one per location if Global is used with predefined sequences), but it can have any number of other types of model database.


Creating a Design Database

To create a new database, select Databases & Extracts from the Elements section of the Admin elements form pull down list, then click the Create button.


AVEVA Marine (12.1) System Administration (Basic) TM-2120

The Database & Extracts form appears. Select the radio button for Master DB and click the OK button.

The Extract of a DB is covered in the System Administration (Advanced) training manual.

From the Owning Team section select the PIPEF team, now key in the database name DESIGN, the description Forward Area Pipes, and the site name PIPEF, then from the pull down list for Database Type select Design and set the Access Mode to Multiwrite, Implicit Claim

This is repeated until the required number of databases are created.

For databases created to be used by hull design

applications, specific rules are defined and site is not to be set. Hull application functionalities require creating certain database types and, instead of sites, hull top level

elements are defined at a later stage. Creating hull top level elements is covered later in this manual, in the chapter entitled Hull Top Level Elements .

For a full list of the hull modelling requirements see Users Guides AVEVA Marine, Hull in Dabacon, Marine

Databases and World Elements.

6.2.1 Create SITE

It is very useful when creating AVEVA Hull and Outfitting 12.1.SPx projects databases to have at least one top level element created. This gives the administrator the ability to navigate to the correct database when creating items in the design session.

Typical top level element types are: Design, SITE Draft, DEPT Catalogue, CATA etc.

For the creation of hull specific top level elements, in hull databases, DBPrompt utility is used. See chapter entitled Hull Top Level Elements .


6.2.2 Database Access Mode

The access mode for databases can be:

Update Allow one writer and multiple readers.

Multiwrite Allow multiple writers and multiple readers. Elements in databases with multiwrite access must be claimed when they are modified so that no other user can change them at the same time.

Claim mode can be:

Explicit Users must explicitly claim any element they wish to change before the modification can start.

Implicit An element will automatically be claimed when it is activated

DESIGN, DRAFT, CATALOGUE, ISODRAFT, SCHEMATIC, MANUFACTURING and ENGINEERING databases can be multiwrite. The SYSTEM database is always multiwrite.

It is normal practice to use multiwrite databases with implicit claim mode. The following are guidelines for multiwrite databases:

Keep interactive usage levels to 10 or fewer Designers per database.

In Outfitting Design, Outfitting Draft and Paragon, keep data collected on a discipline basis where possible e.g. have a Pipe database, a Steel database, Nested Plate Database etc.

Maintain the concept of a graphical split where possible Use one Team with Multiple Users

Do NOT enter AVEVA Marine (12.1) more that once with the same name from different workstations For multiwrite databases, it may be more appropriate to add several databases to the same team, and allow several users to belong to that team.

If a project becomes Global, the administration becomes much easier if there are more databases i.e. for outfitting only project, if Area 22 Piping is being modelled at another location, then Area 22 Piping database can be allocated to the satellite for updating.

Remember the first level of access control is Team membership e.g. piping designers would not normally have write access to Steelwork databases.

Database access mode can be changed from update to multiwrite at any time. Database access mode can be changed from update to multiwrite only if no database extracts have been created.


AVEVA Marine (12.1) System Administration (Basic) TM-2120

6.2.3 Database Access Restrictions

Access restrictions apply to certain modules and database types as listed below:

Only Schematics modules (Diagrams and Schematic Model Manager) will be able to modify databases with type Schematics.

Only Engineering module will be able to modify databases with type Engineering.

Only Hull and Outfitting modules (all others except Admin, Monitor and Lexicon) will be able to modify databases with types Design, Draft, Isodraft, Manufacturing, Catalogue and Properties. One exception to this exists: Schematics and Engineering modules can write to Design databases Database read restrictions have also been introduced based on the Integrate Engineering and Schematics mode selected when entering certain modules. If this is not selected on entry to a Hull and Outfitting module, any databases in an MDB that have Schematics or Engineering database type will be omitted without any warning being shown.

6.2.4 Controlled Databases

By selecting the Controlled checkbox user can specify that the database will be controlled, by an external system.

If a database is defined as a CONTROLLED database, then all updates are controlled externally to Outfitting. Both UPDATE and MULTIWRITE databases can be CONTROLLED.

The external system is accessed via an EDMSlink program, which must be supplied by the user. Users must claim elements in order to change them on CONTROLLED databases. The EDMSlink program is activated by Outfitting when a CLAIM or release is made. It is totally up to the user as to what the EDMSlink does. Normally it will link into a user's central control system.

Both UPDATE and MULTIWRITE DESIGN databases can also be CONTROLLED.

6.2.5 Protection

By selecting the Protected checkbox the databases are marked as uniquely belonging to the project from which it was protected such that restricted users cannot copy data from that database into another project, even through a physical copy of the database file. The following functionality will be unavailable when Protected is checked:

OUTPUT command

COPY command, when copying across databases EXPORT command

Data Access Routines (DARs)

In addition, read access to certain attributes is restricted to obstruct an unauthorised user from writing their own output using functionality in PML. When Protected has been checked it is possible to set an expiry date. Enabling the Expires checkbox highlights the date pull downs based on date.


6.2.6 Reference Only Databases

Systems and Areas can only be created in DESI DBs. Thus if product checks are made before opening a DESI DB it appears that a 3D-product license will be required to access them, preventing 2D only users from using Systems and Areas.

The Reference Only check box is only

ability of non-3D applications to create and modify reference data in the Design database.

The toggle is inactive when the form is in Modify mode to prevent modification; even when inactive the value of the toggle accurately reflects the setting that applied on database creation. The toggle also informs the top-level element type that is available for immediate creation when the database is


rence command clause is available that is only available when DESI is given as the database type: CREATE DB <database name> DESI [ REF/ONLY ]

It will not be possible to create certain top-level element types in Design databases that have this -level types that will be available are listed in the following table:

6.2.7 Area Number, DB Number and File Number

The Area Number, DB Number and File Number are normally set by the system, as shown by the word System entered in the input boxes. It may sometimes be necessary to set them manually.

The Area Number is used if the user needs to store databases in a different directory. The user can reset this attribute by clicking the System button to the right of the input box.

The DB number is used internally to identify the database. When a database is copied or an extract is made, the copy or extract keeps the same DB number as its parent. There cannot be more than one database with the same DB number in the same MDB (unless the database is a Working Extract). The DB numbers for user defined databases must be in the range 1 255,000, numbers 7,001 to 8,000 and 250,000 to 255,000 are reserved for AVEVA Solutions use. The user can reset this attribute by clicking the System button to the right of the input box.

The Unique button can be used to allow the system to automatically use the next available number in a predefined range. This range is set from the Admin menu Settings > DB Number Range the following form is displayed:

Key in the unique number range to be allocated to your project and click Apply.then Dismiss the form.


AVEVA Marine (12.1) System Administration (Basic) TM-2120

The File number is used in generating the filename of the database, i.e. a database in project ABC with file number 12 will be stored in the file named abc012. The File Number input box will only accept values in the range of 1-8188. This value entered must be unique within the project. If the value is set to System (using the button System next to the input box) then the file number will be reset to 0 and the database file will be created with the name abc<database number>_0001 allowing for the 8188 limit to be ignored. It is

recommended to reset the file number to 0, particularly if a user is going to use extracts, as it will ensure that file names are consistent within an extract family. In modify mode, the input box is inactive.

Click the Apply button and the database will created.


Creating a Catalogue Database

If the database is to be shared across many projects as may be the case with the Piping Catalogue, it will be necessary to specify the AVEVA Marine (12.1) DB Number. Database numbers must be unique within AVEVA Marine (12.1). Remember the Catalogue supplied by AVEVA has the AVEVA Marine (12.1) DB Number in the 7000 range.

From the Settings menu set the DB Number Range to be from 10000 to 20000.

On the Admin elements section of the form Select Databases & Extracts from the Elements pull down list. Then click the Create Button.

The Create Database form appears, key in the Name PIPE, the description Project Pipe

Catalogue, DB Element Name CATA/PIPE, then from the Database Type pull down lists select Catalogue, and from the Access Mode pull down select Multiwrite. Select Unique for the DB Number field, this will be set the catalogue DB Number as 10000.

This would be repeated until all the DBs are created.

If there is a conflict in DB numbers it would need to be resolved using Reconfigure The administrator can use the Modify button to change the database names if this should be required.

Database access is controlled by the Team, so by changing the team the database belongs to will also change user access rights to that database.


6.3.1 Creating Namesequence Database

The Namesequence database (NSEQ) is used by Curved Hull and Assembly Planning. Creating of this type of database is similar to previously described procedures, for creating design and catalogue database. The difference is in access mode settings. There is no possibility to set access mode for this database. Also, Controlled and Protection cannot be set.

For information of name sequences for global set up see TM-2262 AVEVA Marine (12.1) Global training guide


Copied Databases

Copied databases can be used for: Copying a template project

Merging projects

Copying included databases before archiving

If several users are to work on copies of the same data, it may be more appropriate to use Extracts

Databases can be copied by selecting Database from the Elements option list on the Admin elements form, selecting the element desired to copy from the scrolling list, and then clicking the Copy button. The Copy Database form will be displayed.

On the form, the administrator can specify the Owning Team by selecting one from the list of all the teams in the project. The administrator can give the copy a Name, Description and Area Number.

The database number of the copied database cannot be changed. This will be same as the original. Users cannot have more than one database with the same database number in the same MDB To avoid the risk of database corruption, all copying of databases (i.e. the files inside the Project directory) must be done from the ADMIN module and not by using operating system utilities or commands.


AVEVA Marine (12.1) System Administration (Basic) TM-2120

Exercise 3 - Database Creation

1. Create the databases as describe below.

level elements to be defined at a later stage. For a full list of the hull requirements see User Guide > Hull in Dabacon > Marine Databases and World Elements


View showing databases defined in Admin module.

2. Install the Training project MTP, follow the installation wizard delivered by the trainer. This will be referenced in future exercises throughout the training. Please start the MTP project in Hull or Outfitting to verify that the installation has been successful

The training will provide the folder containing the exe file for the installation of the MTP


Chapter 7


Foreign Databases

The administrator can copy databases from other projects. Databases can also be shared between projects; which saves disk space and eliminates errors that could be caused by copying. Catalogue databases are often shared in this way.

Databases included from a second project are also known as foreign databases. The second project must be available, that is, the administrator must be able to read from the second project directory, and have the environment variables for the second project set.

When the administrator creates a project that is going to share databases from other projects Teams must exist for all databases that are to be shared.

Databases in the source project that will be shared must NOT be given a database number that will clash with a database number that already exists in the destination project.

The Foreign Databases are marked with * in the database list.


Including and Copying Foreign Databases

To complete the database additions to our AMA project, we are going to include all the databases for the MAS project and also copy a database from the MAR project.

7.1.1 Including Databases from the MAS Project

To include databases from MAS project, select Databases & Extract from the Admin elements form and then click the button.

Include Foreign Database form appears; select the MAS Project from the Foreign Projects section, Key in the Username SYSTEM and the Password XXXXXX. Then select all the foreign databases except the databases starting with U and then click the Apply button.

All the databases starting with U are Imperial example databases



Copying a Foreign Database from the MTP Project

From the Admin elements form, click the Copy Foreign button. Copy Foreign Database form appears.

From the Foreign Project section, select the MTP project and key in the Username SYSTEM and the Password XXXXXX. Then select from the Foreign Database section the database to copy i.e. MPROJECT/PADD. Now from the Target Database Name section select the Target Database i.e. ADMIN and finally click the Apply button.

Copy all databases belonging to MPROJECT team into the new project to enable project libraries to be

available when executing different functions i.e. Automatic Drawing Production.


Excluding Foreign Databases

The administrator can exclude foreign Databases by clicking the Exclude button on the Admin Element form. The Exclude Foreign Database form will be displayed. Select the foreign databases to be excluded and click Exclude .


Deleting Databases

Databases can be deleted by selecting the element from the list on the Admin elements form and then clicking the Delete button.

To avoid the risk of database corruption, all deletion of databases (i.e. the files inside the project directory) must be done from ADMIN and not by using operating system utilities or commands


AVEVA Marine (12.1) System Administration (Basic) TM-2120


Modifying the setup of the Admin Elements Form

The display on the Admin elements form can be changed to display additional information i.e. the Database Filename, Database Access mode, etc.

From the Settings pull down menu select Display Mode > Setup Admin Elements form .

The Level of Detail on the Admin Elements form appears, select the two boxes for Filename and Access so they are ticked and click the Apply and then the Dismiss button.


Exercise 4 - Copying and Including Foreign Databases

1. Include all the Foreign Databases from the MAS project that are not imperial and not MDS or MDU team own into the AMA project. The list of Foreign databases should appear as below.

2. Copy the MPROJECT/PADD, MPROJECT/CATA from the MTP project into the ADMIN team.

3. Change the display of the Admin Elements Form for Databases to include Access and Filename to be displayed.