Doas_mode table

Modes are used to establish different operation scenarios. They configure the ownership and privileges between the different points of the system.

Modes are used to establish different operation scenarios. For example, one mode may be set up so that privileges, such as events and alarms, are enabled on a number of systems, and a second mode may be set up so that ownership is enabled on only one system. Modes are used to activate the privileges defined for the datasets and systems.

Modes are defined by records within the doas_mode table. Each privilege record points to a mode record. A mode record may be associated to any number of privilege records. For example, consider the following scenario. In one mode, HUB1 is expected to own (and therefore be responsible for polling) a specific field device. In another scenario PRI is expected to own the field device. The following figure shows two modes and the privileges associated with each.

The top half shows the mode and associated privileges that define the scenario where HUB1 owns the field device. The bottom half defines the scenario where MAS owns the field devices.

Note: For simplicity, the above figure describes the relationship of only two of the unique privilege types contained within the doas_privilege record -- ownership and configuration.

When the top doas_mode record is ACTIVE, then the associated top two privileges are 'turned on'. The bottom privileges are turned off. In this mode, HUB1 'owns' the field devices.

When the bottom doas_mode record is ACTIVE, then the associated bottom two privileges are 'turned on'. The top privileges are turned off. In this mode, PRI 'owns' the field devices.