Interpreting ARI file types and states

The ARI receiver service has received the incoming reading file. It is waiting to be further processed by ARI.

The inbound XML file and all of its channel elements are recognized by the ARI receiver service as well-formed and valid files. The receiver is processing valid channel elements in the order that they are listed in the file.

The ARI receiver service has completely processed the file, and all readings data has passed all steps of the parsing process. All readings are written to their defined work bin files for subsequent processing by validation and estimation (VE) services.

The inbound file contains invalid channel elements. The ARI receiver service has set the file to a read-only state. The receiver does not process the file again unless the file properties are manipulated manually or by an external process.

When the file is corrected and resubmitted for processing, IEE re-imports the previously processed channels as new, unchanged versions of the readings.

The XML file that corresponds to this work bin file now has a file state of Processed, and it has been written to a work bin file. The newly created work bin file is waiting to be further processed by ARI.

The work bin file is assigned to a validation and estimation (VE) process. Initial validation has taken place. The VE runner is holding readings that require estimation in memory until the data collection window (DCW) ends. When the DCW ends, the VE runner performs estimation and secondary validation. The VE service has generated clean reading files and a number of other binary files that contain supporting information to be imported into the IEE database as part of the AMI Readings Import Job.

All clean reading files within the work bin file are imported into the IEE database, as are all other binary files that contain supporting information.

If the ARI Dashboard shows a Work bin file type in an Error file state, contact your system administrator.

The validation and estimation (VE) service has generated clean reading files for import into the IEE database.

The AMI Readings Import Job is transporting clean reading data and supporting binary files into the IEE database.

All readings for the associated clean reading file are successfully imported into the IEE database.

If the ARI Dashboard shows a clean reading file type in an Error file state, contact your IEE database administrator.

The resubmit file in a state of Resubmit indicates that the resubmit file has been created.

There is a one-to-one relationship between the source XML reading file and the resubmit file. The ARI receiver writes all unrecognized channels from a single source XML reading file to one resubmit file. The ARI process attempts to reprocess resubmit files once a day, in case the meter configuration has arrived. Typically, XML files are written to resubmit files for the following reasons:

• Reading data from a new meter arrives at IEE before the meter installation service order has been completed and the configuration data pushed to IEE.
• The receiver recognizes the channel ID but the readings are of a different interval length.

The resubmit file is waiting to be reprocessed and the time on the IEE application server is two minutes before the start of the data collection window (DCW).

The resubmit file is being processed.

The data that originally caused the file to be resubmitted has been obtained. The file has been reprocessed by ARI.

The data that caused the file to be resubmitted has not been obtained by ARI for a period of time longer than that defined in the Banked XML Maximum Retry Count system setting.

ARI bypass files are routed to the Workbin0 file to be processed by the standard readings import (SRI) process instead of by the ARI process. All ARI bypass files maintain a file state of Processed. Files can be routed to Workbin0 for several reasons and at many stages of the ARI process. Typically, files are routed to Workbin0 because:

• The ARI receiver recognized channels as invalid or malformed or a service point configuration has changed.
• The meter or service point configuration has changed during the current day.
• The AMI Readings Import service point attribute is set to Exclude.
• An ARI VE runner is processing small amounts of older data and the threshold in the Route Historic Data to WB0 in Days system setting is reached.

The total number of channels that were not imported, likely, due to missing configurations in IEE.

Channels banked can be distributed across one or more XML files.