Register gap check

The Register Gap Check looks for register reads that should exist based on the register channel configuration in IEE, but that do not exist (missing register reads) or that have a value of zero (invalid register reads). This check always results in a FAIL if a register read is not present for the time of day that is specified in the rule.

Use this rule to find gaps in data, particularly if there are no interval channels configured for the meter. If estimation is enabled and a register estimation routine is enabled in the service point's estimation set, IEE attempts to create accurate estimated register reads to replace reads that failed the Register Gap Check.

For example, the following scenarios typically result in gaps:

A system that sends the data may lose a file.
A changed telephone number for which the paperwork has not yet been completed.
An intermittent communication issue may exist within a fixed network or AMI network.

Because data gaps prevent billing accuracy and can lead to revenue lost or disputes with customers, the causes for repeated occurrences in the same service point register channel should be pinpointed and resolved as quickly as possible. Gaps in register data can also affect the accuracy of scaling and use of the data set with other estimations.

The Register Gap Check can detect register gaps regardless of how data is imported: ARI, SRI/SRI-E, manual edit, or pick-up reads via MDUS. For both ARI importers and non-ARI importers such as SRIE or Manual Validation, the register gap check validation rule creates a MISSING register at the “Expected Time” specified in the validation rule. The main criterion is that it will only run against register channels that are linked to an interval channel via MeterRead ChannelSet. During import of intervals through SRIE, if the register gap check validation determines that there are missing registers in the “Expected Time” covered by the date range specified in the interval reads, it creates a MISSING register on the “Expected Time,” which is then marked as failed validation.

The Register Gap Check can be configured against an interval/register channel set. It cannot be configured against an interval channel. It can run in line with readings import, on schedule or manually triggered, via UI or API, or triggered by Validation Detection Processor (VDP).

It uses the Expected Time parameter and the time period to look for register reads that should exist, either in the reading payload or in the database. Only look for the end read (similar to what ARI does today).

For example, if Expected Time is set to 00:00,

For timespan Apr 25th 00:01 to Apr 26th 00:00, it will look for the Apr 26th 00:00 register.
- Scenarios: In line validation for ARI import, or Daily recurring validation for SRI/SRI-E import.
For timespan Apr 25th 16:01 to Apr 26th 00:00, it will look for the Apr 26th 00:00 register.
- Scenarios: In line validation for SRI/SRI-E import of 8 hours chunk of data.
For timespan Apr 25th 08:01 to Apr 25th 16:00, it will SKIP because the expected register is in the future.
- Scenarios: In line validation for SRI/SRI-E import of 8 hours chunk of data.
For timespan Apr 25th 00:01 to Apr 30th 00:00, it will look for Apr 26th 00:00, Apr 27th 00:00, Apr 28th 00:00, Apr 29th 00:00, and Apr 30th 00:00 registers.
- Scenarios: In line validation for Contingency Read or Gap Fill import of 5 days worth of data.
For timespan Apr 1st 00:01 to May 1st 00:00, it will look for all midnight registers between Apr 2nd 00:00 & May 1st 00:00, inclusive.
- Scenarios: Manual validation for a month billing period, following an ABE exception.

Register reads that are timestamped outside of the Expected Time parameter are not considered; for example, actual pick-up reads timestamped 14:35 (obtained when the field engineer goes on site) are left untouched. When register gaps are identified, validation fails.