When a DR event xml is sent from the DRAS server, in addition to the current state of the event, a schedule of event values are also sent, as shown in the example below:

A list of various op mode value changes/ pricing and load shed changes over the event's active window can also be configured in the DRAS server. The DR event xml received from the DRAS server contains the complete information. The schedule of event information that is valid at different time offsets will help when there is a temporary network connection issue between DRAS client and server.

The Adr Device configuration determines whether or not schedule information is stored in the station bog file. This determination is made using the "Enable Cache" slot under the device. The default value for this slot is "false" (schedule is not cached). If a schedule needs to be stored, the Boolean slot must be set to "true".

The “Work On Cache Enabled” slot under AdrNetwork determines whether cached data will be used to update the “Active Event” component in the case of a network failure. This slot is defaulted to “false”. When set to “true”, a network level monitoring thread updates the “Active Event” component for devices that are currently “down” if the “Enable Cache” slot for those devices is set to “true”.

If both the “Work On Cache Enabled” component under the AdrNetwork and the “Enable Cache” component under the AdrDevice are set to “true”, then the “Active Event” component under the AdrDevice will be updated with cached event schedules as shown below. However, the status of the points is still marked down to indicate that the client connection to the DRAS server is unhealthy, as shown in Figure 17.