Resolution Logic for Data Gaps or Overdue Data

When resolving Data Gaps or Overdue Data Notifications using the available capability, the following methods are used when calculating the data that should be used to fill the gaps or extend the data.

ConditionApplicable Strategy TypeFill Method Number of Weeks

Interval Data Periodic Channel

The periodic channel is configured as Non Meter Reading and each interval represents the consumption in that time period.

Data Gaps and Overdue Data

Period Average

The system will...

  1. Get the periodic interval data for the X weeks prior to start of the gap (where X is the Weeks to Average that has been specified for the Strategy)
  2. Calculate an average value for each equivalent data interval based on Time of Day and Day of Week using the X weeks of data
  3. Fill the gap/overdue data period using the averaged data for the equivalent period
  4. Update the status of the Notification to 'Resolved', setting the sub-status to 'Manually Actioned' or "Automatically Actioned" (depending on whether the system was configured to automatically fill the data, or resolved manually by a User), and the last action date as the current date

Example

If you specify 4 weeks, Sigma will calculate an averaged value to use based on the data for the equivalent time period in the last 4 weeks. 

Example scenario: if a half hour gap is detected on a Monday morning at 8am, Sigma will look at the previous 4 Mondays at 8am and use an average of those to fill the gap.

When performing the calculation:

  • if there is no data available or the data are zero value for all the applicable preceding number of periods, then the system will raise a notification for the gap with a status of "Resolution Error" so that these are visible and can be managed manually.
  • if there is data available for only some of the applicable preceding number of periods or the values are zero, then the system will exclude these periods from the calculation as to not artificially deflate the value used for filling the gap.


Defaults to 4 Weeks

Meter Reading Periodic Channel

The periodic channel is configured as Meter Reading and each interval represents the advance since the last reading.


Data Gaps 

Interpolation

The system will...

  1. Get the valid meter readings immediately before and after the data gap
  2. Calculate the advance between the two readings
  3. Apportion the the gap advance to each data interval that should exist between the gap
  4. Update the status of the Notification to 'Resolved', setting the sub-status to 'Manually Actioned' or "Automatically Actioned" (depending on whether the system was configured to automatically fill the data, or resolved manually by a User), and the last action date as the current date.

Example

The data should be received every half-hour and there is a gap for two half-hour periods.

  • 06:30 am - 40 kWh
  • 07:00 am - 50 kWh
  • 08:30 am - 110 kWh
  • 09:00 am - 140 kWh

Here, the readings for 07:30 and 08:00 are missing. The system determines that the difference between the pre (07:00) and post (08:30) readings is 60 units (110 - 50). This 60 units is then apportioned to work out what the advance needs to be for the two missing half-hour periods:

  • 07:00 am - 50 kWh (+20 units)
  • 07:30 am - 70 kWh (+20 units)
  • 08:00 am - 90 kWh (+20 units)
  • 08:30 am - 110 kWh

Here, the 20 units is added on from the prior read to fill the first missing half-hour. The 20 units is then added again to fill the second missing half-hour, and then 20 units added so that it will equal the first actual reading after the gap.

N/A
Overdue DataThe system will apply the Period Average logic above, to fill the overdue period with estimated data based on the historical average for the equivalent periods of time.Defaults to 4 Weeks