Configuration Database

The Configuration Database (DB) has been introduced to move external reference data into project(s).

In the installation folder of any AVEVA Dabacon based product, is a folder named ‘databases’ which contains two DB files, 9100 and 9101, these are Dictionary (DICT) and Configuration (CONF) DBs respectively.

These DBs are automatically included in any new project you create, and they are referenced by AVEVA products in any module without the need to add them to the Multiüle Databases (MDBs) within the project.

These AVEVA supplied DICT and CONF DB files cannot be accessed or edited by customers.

The DICT DB contains a set of KEYs, each Key represents a specific data type and the CONF DB contains a value applied to the key. For example, a UNITs key with the value set to mm.

Customers Preferred Values

Many customers have common data. For example, a Piping Catalogue (CATA) DB or Production of Annotated and Dimensioned Drawings (PADD) DB with corporate backing sheets and preferred symbols, these DBs are usually stored in a primary or corporate project and become foreign reference DBs in many design projects. Within each design project we then add specific piping CATA DBs and PADD DBs so that the project has the specific design requirements.

It is expected that customers will similarly create a primary or corporate CONF DB in which they set their preferred values to overwrite one or more of the AVEVA default values and this CONF DB is referenced by any design project.

The design project may also have its own CONF DB to accommodate the project requirements and this will be used to overwrite any AVEVA default values or any of your corporate CONF DB default values.

Customers who create CONF DBs must add these to the MDBs within the project.

Element Hierarchies

The Configuration Keys within the DICT DB have elements:

• CFGGPW - Configuration Group World. A top-level element than owns:

• CFGGRP - Configuration Group. A grouping element to allow grouping of related items. A GFGGRP may also own CFGGRP or:

• CFGKEY - Configuration Key. The defined key value.

The Configuration Values in the CONF DB have these elements:

• CFGSTW - Configuration Set World. A top-level element that owns:

• CFGSET - Configuration Set. Will own:

• CFGVAL - The value set against a chosen CFGKEY.

The example graphic is taken from the AVEVA APS project and displays two CONF DB hierarchies.

The first is a project CONF DB with a CFGSTW /CONFIGWORLD and CFGSET with no members.

The second is the 9101 DB with CFGSTW and a CFGSET with many CFGVAL members.

The value that is used is controlled by a Precedence attribute on the CFGSET.

The CONF DB has a CFGSET with the Precedence value of 1.

A CONF DB with a CFGSET with a precedence value greater than 1 will overwrite any modified key value.

The example graphic displays the APS project CONF DB with a CFGSET with a Precedence value of 200.

Overwriting a Key Value

Add your CONF DB to an MDB and enter Lexicon.

To overwrite one or more default CONF DB values, on the Home tab in the Configure group, click Standards to display the Configure window.

The example graphic is achieved by navigating down the CONF DB explorer to any Config Group (CFGGRP).

The grid(s) are exposed, and the columns represent the AVEVA and APS project CONF DB settings.

In the example the cable sizes CFGGRP is the Current Elment (CE) and this has three CFGKEY entries as listed.

In the APS project we have applied values to the first key of 2.5 and 4 mm2 sizes, thus eliminating the 1 and 1.5 mm2 sizes from the 4 values AVEVA defaults.