AVEVA™ Operations Management Interface

Runtime behavior of Area objects

Save PDF

Save PDF

The following information describes the runtime behavior of Area objects. Runtime behavior is limited to the state of individual Area objects.

After it has been deployed and is operating, an Area object can assume one of several states, which are described in the following table.

State Change	Behavior
Startup	None.
Going onscan	In this transition state, the data quality of the alarm counters, alarm list, and event list is set to INITIALIZING.
Running onscan	In this state, the Area object: Maintains a list of all the alarm and event messages from the AutomationObjects directly assigned to it. Exceptions are sub-areas, WinPlatforms, AppEngines, and DeviceIntegration Objects (including DeviceIntegration Networks) that are responsible for maintaining their own alarms and events. Updates the alarm and event lists so that subscribed alarm/event clients are notified. Reads the alarm counts from all child areas (or child notification distributors). These values are totaled and included in the alarm total counts. If any of the child areas are offscan, then the data quality of the counter is set to UNCERTAIN. Otherwise, the alarm counter will have quality of GOOD. Sets the data quality for the alarm and event lists to GOOD.
Going offscan	During this transition state, the Area object: Sets the data quality of alarm counters and the alarm list to BAD. Sets the data quality of the event list to GOOD.
Offscan	In this state, the Area object: Maintains only a list of event messages from the assigned AutomationObjects. Updates only the event list in order to notify the subscribed event clients.
Shutdown	The Area object is shut down and performs no role in the system.