This driver has been developed and tested against Akuacom servers only.

The event XML format used by this driver for communication is specific to Akuacom DRAS servers.

If the driver is placed in a JACE running within a network firewall, the driver cannot establish communication with the DRAS server. An alternative is to place the JACE in a public network or to open appropriate firewall ports in the WAN.

Caching op mode and event info schedule will help when there is a temporary loss of connectivity to the server. If the ADR client connection to the server is unavailable for a long time, updating active event might not make sense. Because there is no way for the client to come to know any intermediate changes done in the server during the network failure.

Updating Active Event with the schedule - will be done only for the currently active event. The driver will not pick the next event automatically from the list of events. For example, for the following events:

If the network connection gets the last signal at 8:30 p.m., then the driver updates Active Event with the information for “Event1”. The driver would not make “Event2” since the next active event will not occur until 9:00 p.m. This is implemented this way because event order is decided by the server’s internal priority mechanism. During network failure, if the event priority is changed in the server, the client operating with old event order will be misleading.

When the station is restarted during network failure, "Active Event" and all events under Programs node will get cleared. This is for the same reason explained in point 2 above.

Manual configuration is not fully implemented in DRAS server. As of now only opmode value can be configured in the server. Driver has been developed and tested only against the current functionalities supported by the server

Akuacom DRAS server does not support configuring all 7 event info types. Driver is developed and tested with 3 event info types -PRICE_ABSOLUTE, PRICE_RELATIVE and LOAD_AMOUNT

Akuacom DRAS server does not support configuring event info schedule for PRICE_RELATIVE in CPP program

Driver communicates to DRAS server through REST2 interface. But event cannot be acknowledged using this interface. Currently using REST interface to send acknowledgement back. This can be edited by using Acknowledgement URL in Adr Device.

The top-node of event xml received by the client is considered to be the event with the most priority. Two different client accounts associated to the same programs-events can receive the events in different order of priority. But the driver sticks to same thumb-rule of keeping top event info - as the high priority event. This means client C1 will display E1 as active where as client C2 will display E2 as active.