Zones Event Chronicle and Process History View

The workstations in each DeltaV system collect process and event data in that system. Inter-Zone parameter writes are recorded in both the originating and receiving zones, if the Event Chronicle database is enabled and local areas and Remote Zone Areas are assigned to the appropriate workstation's Alarms and Events subsystems.

System-wide events such as logins, logouts, and downloads are always associated with AREA_A in a DeltaV system. This means that AREA_A must be assigned to the Alarms and Events subsystem for those types of events to be recorded. This is true even if you rename AREA_A. The area that was named AREA_A must be assigned to the Alarms and Events subsystem to record system-wide events. This is true for DeltaV Zones as well.

For example, a DeltaV Zones environment includes two zones, ZONE_A and ZONE_B. For ZONE_B's Event Chronicle to record system-wide events from ZONE_A, its AREA_A must be shared with ZONE_B and the shared area must be assigned to the Alarms and Events subsystem on a node in ZONE_B. For example, if the system is configured as shown in the table below, the Event Chronicle in ZONE_B records system-wide events occurring in ZONE_A and in ZONE_B. In the Event Chronicle in ZONE_A, only system-wide events from ZONE_A are recorded.

How events appear in the Event Chronicle depends on:

• The zone the change is made from

• The zone the change is made in

• Where events are recorded.

In general, Inter-Zone event records include zone information and are recorded in both zones, if the configuration in both zones supports it. The area column displays the Remote Zone Area name of the remote zone in the local zone. Other fields display zone information as appropriate. For example, given the following configuration of two zones:

In addition, local areas in both zones are shared with read/write access.

In ZONE_A user Fred, with configure privileges, is logged into a local Operator Station. Fred launches DeltaV Operate, opens a picture with datalinks configured to write to another zone, for example, DVSYS.ZONE_B%MOD1/PARAM1.F_CV. Fred changes the value of PARAM1, then launches Process History View and connects to OP_STA_A. The Event Chronicle record for his action appears as shown: 

In ZONE_B user Fred, with configure privileges, logs in to local Operator Station OP_STA_B, launches Process History View, and connects to OP_STA_B. The Event Chronicle record appears as shown: