Preparations for Customization

The following main activities are preferably done before starting the customization work:

Set up of the organization for the implementation

The contact between AVEVA and a customer is technically managed by a system manager from the customer organization. The system manager should preferably be involved very early in the implementation of AVEVA Marine at the customer’s site, and will be the point of contact for all technical matters between the customer and AVEVA.

Installation of the hardware and basic software

The customer is normally responsible for installing all hardware and operating system software before AVEVA Marine can be implemented.

Training of users

To successfully install and customize AVEVA Marine, the users should be adequately trained in the use of the various applications. AVEVA offer a full range of standard courses as well as customer specific training programs.

AVEVA further offers on-site supervision, follow-up activities and other types of consulting, aiming at the maximum performance and best use of the software.

The actual installation

The first time installation of the software is often done by AVEVA, while the installation of new releases and updates usually are handled by the customer’s system manager.

The first time installation does normally not include any customization work, but includes all default settings and a sample test project. This installation typically ends up in an acceptance test, and after a successful test the customer is required to sign an acceptance report.

Establishment of system management routines

It is necessary to decide upon management routines at the customer site. Such decisions are very much depending on the intended use of the software, the organization of the customer company, the type of hardware in use and the type of projects to run.

One important concern is to decide on access control, that means, which users have access to which tools, directories and projects. A standard environment is delivered and can be modified. Connected to the access control, built into the operating system, the access to AVEVA Marine products must be set up, using the License management tools, supplied by AVEVA. Further, possible links to other types of software may have to be considered.

A first projects must be initiated. (Refer to Projects for further information.)

Last but not least, proper disk management and backup routines must be established in order not to loose data because of for example, power failure or hardware failure.

Analysis and definition of work-flow and development of working methods

Some basic conventions related to the shipyard facilities and working methods in use should be decided. These include the naming conventions and rules for position numbers and the symmetry conventions. (Refer to Control on Application Level for further information).

The production information for workshops can be tailor-made to a great extent and the use of teams-zones-sections-modules should be established.

If subcontractors are to be used, the planning of the information flow to/from subcontractors is necessary.

Finally, reuse of data - sister ship handling - may be planned.