Project Database Set up in AVEVA Administration

In terms of setup, it is strongly recommended to share a single, writable, configuration database between multiple MDBs rather than having a different one for each MDB. For a given project, the configuration for all MDBs can then be modified in any one of the MDBs, which can be viewed using the System Defaults window. Refer to Maintenance for further information.

The administrator is responsible for ensuring that the (writable) configuration database is added to each MDB, unless this is already the case. If the database is not present in the MDB, only the AVEVA default values are available. If the database is not writable, it is not possible to modify the configuration at any level.

If the user level configuration is to be supported, the access status for the database must allow it to be writable by ordinary users. This is possible without compromising access because configuration below the user level can only be edited by users with administrator or team administrator access rights, even if the database is defined as writable by all in AVEVA Administration . However, if a configuration database with administrator write privileges only is already available, for other purposes, a second configuration database must be added to support individual, writable, user configurations.

If the administrator wishes to share configurations between projects, it is possible to create corporate project and discipline level configurations in a master project (for example, ACP), by opening Draw in the primary project and using the System Defaults window. In order to make these available as the default configurations in a local project (for example, APS), the administrator must add the master configuration database to the local project MDBs. As a foreign database, this is read-only and is additional to the writable config db that must be added to local project MDBs.