Upgrade Overview

A number of the enhancements made at AVEVA Hull and Outfitting 12.1 require an upgrade to the database. Each of these individual changes is referred to as a Part Upgrade. In general each of these has been designed to be ‘optional’ from a customer perspective, in that the 12.1 software can work with a database that has not been upgraded and the software will degrade gracefully – that is, the software will continue to work, although some new functions may not be available.

This means that it is possible for customers to continue to work with Foreign DBs, which may be shared with 12.0 or earlier projects and which have not been upgraded, included in their projects. An example would be a Corporate Catalogue DB used for 12.0 and multiple projects.

Databases which have not been upgraded will however be read-only. The following warning will appear when opening an MDB from a project that has not been upgraded:

This warning (or similar) indicates that the project needs to be upgraded to the latest version in order to allow write access.

All the Part Upgrades will be run by a new Upgrade Framework, which converts a AVEVA Hull and Outfitting 12.0 project to 12.1. This is initiated from Admin using the following commands in the Command Pane (or TTY mode):

lock

dbupgrade project to latest

unlock

This procedure may also be used with Global projects if some additional precautions are taken. A brief summary is given below – further details are given in the 12.0 to 12.1 Upgrade manual.

Earlier projects should first be upgraded to AVEVA Hull and Outfitting 12.0.

Schematic Model Manager has its own units handling at AVEVA Hull and Outfitting 12.0. It also has its own upgrade mechanism, which is separately documented; the software will advise if it is necessary to run this: