Configuration Levels

Draw provides a five-level configuration hierarchy of (in the order of precedence shown):

• User

• Group

• MDB

• Project

• AVEVA default

Any changes persist between application sessions (after a save work), including the individual user configuration level.

For example, an individual user can change a default value (if the administrator has allowed that default to be changed by the user). This affects only the individual User level configuration, as the User level is the highest one (the one the system looks at first). Otherwise the application looks for the default value at the group level (if the user has a group selected), and if there isn’t one defined, then at the current MDB level, and finally at the project level.

Because the application looks down through the levels for a default value until it finds one that is defined, it follows that higher levels only need to override values that are different from the level below. For example, if the project level configuration provides the defaults for all its MDBs. The MDB level only needs to be modified if a default value different from the project value is required for that MDB. A group level configuration automatically reflects the values for the current MDB, but may override certain values itself.

None of the configuration levels are mandatory. However, if there are no customer-provided values at all, the defaults will fall back to the hard-coded AVEVA level, matching the settings in the APS Sample project. It is expected that the customer will at least have a project level configuration defined.

The Group level is likely to be used for disciplines (for example, one configuration for Piping, one for Structures). However, the groups do not have to map to a discipline, it can be any defined group of users (or the group level may remain unused). If groups are defined, the user can choose a group that the administrator has created from the Configuration drop-down menu at the top left of the Draw Fluent UI.

Note:
A primary project (for example, ACP) can be used to provide default project and discipline configurations to local projects that reference it (for example, APS). The local project and discipline configurations can override the primary project configurations if the administrator modifies them.