Area of Responsibility (AOR) Area

The Area of Responsiblity (AOR) Areas are used to define the different views of the system and assign your permissions for those views. An AOR Area contains a collection of AOR Groups, which can be assigned to more than one area. AOR Areas can also be assigned to other AOR Areas creating a hierarchy.

The creation of different types and sizes of the AOR Areas is enabled by fact they can collect each other and the AOR Groups. AOR Areas can range from system overview areas that cover large portions of the system, to station level areas that focus on individual telemetry locations.

Each AOR Area is assigned a set of DNA Permissions. This means that the Controller may be able to view and control devices within one AOR, but may only be able to view the devices in another. This is important when configuring supervisory areas, where you may be able to see alarms but not acknowledge them. It is also necessary so that a Controller may be allowed to see alarms from devices that are adjacent to his/her AOR, while preventing him/her from acknowledging or controlling those devices.

The same AOR Group can be assigned to several AOR Areas, and AOR Areas containing the same AOR group may be assigned to you. If the AOR Group appears in multiple AOR areas that are assigned to you, then the security permissions shall be treated as cumulative. For example, if you are associated with one Area, which contains "DNA Permission – Control_SCADA" and AOR Group1, and you are associated with another Area, which contains "DNA Permission – Modify_XIS_Data" and AOR Group1, then you will be granted both "DNA Permission – Control_SCADA" and "DNA Permission – Modify_XIS_Data" to the points within the AOR Group1.

When an AOR area contains a mix of AOR groups and AOR areas, then the permissions assigned at the top level AOR area will only apply to its member AOR groups, thus maintaining the security assignments made at the lower level AOR areas.

If a computer is configured as having the easy eXtended Operator Station (ezXOS) installed and has control disabled, then all of your assigned AOR areas will be limited to read-only permissions regardless of the AOR areas' configured permissions.

The Layered Products can add additional properties to the AOR Area. For instance, RealTime adds the option of disabling an AOR Area when the Controller first logs into ezXOS, so that it is only active at the Controller's request.