AMI contingency read monitor

Use the AMI Contingency Read Monitor to perform the following tasks:

• Request a read of a meter or multiple meters, for a specified period of time.

• Track the progress of contingency read requests.

• Ensure that all meter data has been collected before reprogramming or changing the meter.

  Note: The user must have security role permissions for AMI > Contingency Read, AMI > Contingency Read Monitor, and Communications > Remote Interrogation to enable AMI Contingency Read from the AMI workbench.

Contingency reads are issued to ensure that all meter data is collected before any critical change is made to the service point or meter. For example, a meter reprogram performed over the network or in the field can erase all existing readings and event data on the meter. A contingency read collects the meter data before the meter memory is lost.

The IEE contingency read process includes notification to the user or to an external system that the data has been collected and imported successfully into the IEE database. After the utility receives this confirmation, the reprogram or meter change can proceed without critical loss of data.

Contingency reads also provide data to support same-day billing. For example, if a customer is moving out, the contingency read collects the data from the meter and notifies the customer information system (CIS) so the utility can generate a final bill.

Note: Contingency read data is routed to Work Bin 0 to be imported through SRI-E. If the service point instance is associated with a data routing program, IDM routes the data based on the data routing program that is assigned to the service point instance.

IEE imports contingency reads immediately upon receiving the request, even if the reads fall within the normal AMI readings import window. IEE does not wait to import the contingency read with other reads.

Note: When IEE receives multiple register reads that map to the same IEE channel, IEE saves only the first one. Succeeding reads are ignored.