Skip to main content
Firedog
Super User
Super User
January 30, 2024
Solved

Lets understand usage data and meter reading precision

  • January 30, 2024
  • 12 replies
  • 2131 views

It is vitally important that electricity meters record accurately; meter readings form the basis for billing, so inaccurate readings will have financial consequences for both buyer and seller - customer and supplier. Meters have to be certified by the manufacturer to achieve a certain minimum degree of accuracy, and customers can usually assume that their meters are recording their usage with an accuracy of better than ±1%.

Customers with multi-rate tariffs like Economy 7 or Economy 10 have also to be confident that the readings on which their peak/offpeak usage is based are also accurate. There has been some doubt about this, so I checked my own experience.

Many OVO customers have been partaking in the Power Move scheme, encouraging us to shift consumption out of the period of highest demand into periods of lower demand. For the more pedantic of us, this has meant keeping a close eye on the half-hourly usage data smart meters provide. Modern smart meters record the usage in each half hour to the nearest Wh (0.001kWh); older ones may only record to the nearest 5 Wh. So we should be able to add up the usage for all 48 half-hours in a day to see the figure that should be added to last night's  meter reading (also to the nearest Wh) to get tonight's reading.

More than that, though, for multi-rate meters: the total of half-hourly usage in a day's offpeak period(s) should be equal to the difference between yesterday's offpeak reading and today's, and similarly for peak periods.

This was the result on one day for my Economy 7 meter, 120 days after its installation:  
  

 

The meter total has remained within (to me) acceptable limits throughout the meter's active life; the 0.001 figure may well be -0.001 tomorrow. And it's remarkable that the sum of 5760 numbers is more or less identical in my computer and OVO's. However, the peak period register has consistently recorded a higher figure than the half-hourly data would suggest, while the off-peak register's reading is correspondingly lower.

It has taken 120 days for this discrepancy to reach 1.0kWh, so it is of course insignificant (1.0 kW charged at the wrong rate costs me 1.0 x 10p, being the difference between peak and offpeak rates. 10p in 120 days amounts to 30p a year). However, for big consumers, not to mention industrial ones, it could be a substantial figure, and of course it's a considerable amount of money in the bank for OVO.

How does this discrepancy arise? My guess is that it's just a question of timing. At midnight each day, the meter has to transmit both the half-hourly data to DCC for the period 23:30-23:59 and the meter readings to OVO. These two transmissions can't take place simultaneously, so there is bound to be a brief delay in one of them. It looks like it's the readings that are sent a little bit later. I haven't been able to find any correlation between the size of the discrepancy on any particular day with the power draw at the time, so I suspect it's completely random. It varies from 3Wh to 30Wh, with an average of (1.003/120=) 8.4Wh. It's interesting that - in this one-instance sample - the discrepancy is always in OVO's favour. I wonder if that's always the case.

Given this apparent fact of life - that offpeak usage will always be under-reported by a tiny amount - we have to consider how to minimize its effect. The easy way is to ensure that any equipment designed to take advantage of cheaper rates isn't activated until some time after the cheap period starts and is deactivated some time before it ends. This may well happen automatically if it's the meter that controls the timings, by virtue of the 'random offset' introduced to ensure that not all power-hungry appliances (e.g. storage heaters) switch on at precisely the same time. I don't know whether this offset is also applied at the end of the cheaper period; this may not be so important, because this type of equipment will usually not be active for the whole period, having achieved saturation some time earlier.

 

Bottom line:

  • Half-hour usage data for a day match exactly to meter readings, at least those recorded and transmitted with three decimal digit precision. Adding one day's usage to the meter reading at its start will produce the reading at its end ± 0.001kWh.
  • Readings taken from more than one register do not match exactly to their expected values arrived at by summing the half-hourly data for the periods covered by each register. In this one sample, offpeak usage is under-reported by about 2%.

 

Best answer by Emmanuelle_OVO

Updated on 05/12/25 by Ben_OVO

 

I received a very detailed response by one of our smart meter experts:

 

Bottom line:

  • Half-hour usage data for a day match exactly to meter readings, at least those recorded and transmitted with three decimal digit precision. Adding one day's usage to the meter reading at its start will produce the reading at its end ± 0.001kWh.
  • Readings taken from more than one register do not match exactly to their expected values arrived at by summing the half-hourly data for the periods covered by each register. In this one sample, offpeak usage is under-reported by about 2%.

 


This bit isn’t quite right as Half Hourly profile data does not 'exactly' match to meter readings, due to 2 specific reasons, UTC vs GMT and Randomised Offset.

No customer on a Smart meter is billed against their Half Hourly Profile data readings, they’re billed on the readings taken from the configurable Billing Registers for the periods in question. This then has a randomised offset applied to them that can make the offset anything up to 10 minutes variation. So the 2 are out of line but are explicitly based on the energy recorded through the metering. All of which must meet the tolerances set out to record energy in the UK.

So the key issue here is attempting to align the Half Hourly data to the meter reading (Billing) data, as they will not explicitly align, but we're not using them for billing purposes. They're for display purposes, so what Firedog is doing won't provide him the answer he wants or the outputs.

 

Please note this is nothing to do with accuracy of the device and all to do with confusion as to how the device operates. The data is accurate, the way it is calculated is accurate, but taking 2 separate data points, with different variables applied, and expecting them to match explicitly is what is creating this confusion.

 

So adding up the Half Hourly profile data to establish a value, and then trying to match that to the meter reading, will only work if you know the offset and how to apply it. But being the Half Hourly profile is not being used for billing, it's not needing to be done, it just gives how much energy was recorded in that Half Hour.

12 replies

Emmanuelle_OVO
Retired Moderator
Retired Moderator
January 30, 2024

This is really thorough and insightful @Firedog! You theory about the cause of the discrepancy seems like a solid one to me. I’ll share your topic with one of our smart meter experts, see if they can shed any light. 

Renewable Energy? Big Fan.
Jeffus
Rank 20
Rank 20
January 30, 2024

Just FYI for anyone interested in this subject.

Attached is someone's submission to the House of Commons Committee on Energy Security and Net Zero. Obviously I can't vouch for detail so do your own research.

it contains some thoughts on the random offset and it's implications 

https://committees.parliament.uk/writtenevidence/123426/pdf/

Emmanuelle_OVO
Retired Moderator
Retired Moderator
January 30, 2024

Updated on 05/12/25 by Ben_OVO

 

I received a very detailed response by one of our smart meter experts:

 

Bottom line:

  • Half-hour usage data for a day match exactly to meter readings, at least those recorded and transmitted with three decimal digit precision. Adding one day's usage to the meter reading at its start will produce the reading at its end ± 0.001kWh.
  • Readings taken from more than one register do not match exactly to their expected values arrived at by summing the half-hourly data for the periods covered by each register. In this one sample, offpeak usage is under-reported by about 2%.

 


This bit isn’t quite right as Half Hourly profile data does not 'exactly' match to meter readings, due to 2 specific reasons, UTC vs GMT and Randomised Offset.

No customer on a Smart meter is billed against their Half Hourly Profile data readings, they’re billed on the readings taken from the configurable Billing Registers for the periods in question. This then has a randomised offset applied to them that can make the offset anything up to 10 minutes variation. So the 2 are out of line but are explicitly based on the energy recorded through the metering. All of which must meet the tolerances set out to record energy in the UK.

So the key issue here is attempting to align the Half Hourly data to the meter reading (Billing) data, as they will not explicitly align, but we're not using them for billing purposes. They're for display purposes, so what Firedog is doing won't provide him the answer he wants or the outputs.

 

Please note this is nothing to do with accuracy of the device and all to do with confusion as to how the device operates. The data is accurate, the way it is calculated is accurate, but taking 2 separate data points, with different variables applied, and expecting them to match explicitly is what is creating this confusion.

 

So adding up the Half Hourly profile data to establish a value, and then trying to match that to the meter reading, will only work if you know the offset and how to apply it. But being the Half Hourly profile is not being used for billing, it's not needing to be done, it just gives how much energy was recorded in that Half Hour.

Renewable Energy? Big Fan.
Firedog
Super User
FiredogSuper UserAuthor
Super User
January 30, 2024

Attached is someone's submission to the House of Commons Committee on Energy Security and Net Zero.

 

 

I knew your filing system would turn up trumps! Thanks for (re-) posting this 🙇‍♂️

Noel | I have no official status; I'm just a volunteer who comes here to help other customers. My gear: Aclara SGM 1416-B Electricity-only E7 meter; Chameleon IHD3-PPMID-AAA | It may look as if I know what I’m talking about, but don’t let that fool you. |
Emmanuelle_OVO
Retired Moderator
Retired Moderator
January 31, 2024

Hey @Jeffus,

 

Our smart meter expert has shared some information regarding the ‘written evidence’ you’ve posted. They advise although it is well meaning, there are inaccuracies which can be misleading. 

 

I’ll private message you a full breakdown of what they’ve advised as it’s rather lengthily. 

 

 

Renewable Energy? Big Fan.
Jeffus
Rank 20
Rank 20
January 31, 2024

Hey @Jeffus,

 

Our smart meter expert has shared some information regarding the ‘written evidence’ you’ve posted. They advise although it is well meaning, there are inaccuracies which can be misleading. 

 

I’ll private message you a full breakdown of what they’ve advised as it’s rather lengthily. 

 

 

I don't need it @Emmanuelle_OVO

I won't read it to be honest.

I haven’t even read everything in the paper. Too detailed for me.

It was an edited paper published by a Westminster select Committee 

OVO are better off sending the commentary to the select committee rather than me.

That would be much more useful

Can you ask them if they will do that?

Else can I send their comments to the select committee and say they are from ovo?

The paper is nothing to do with me 

Emmanuelle_OVO
Retired Moderator
Retired Moderator
January 31, 2024

I’ve already sent you it! Apologies @Jeffus, you can just ignore my (very long) message! 🙈

 

We've reviewed the document posted and would like to highlight it has many inconsistencies and inaccuracies so we would not recommend taking it as being something that fully describes some of the issues or as being fully factual. 

 

It’s worth highlighting that the paper is a view from an individual who has misunderstood some elements of Smart and has called out items that have either been misinterpreted or, unfortunately, not correct.

 

We’re happy to answer any queries or elaborate 😊

Renewable Energy? Big Fan.
Firedog
Super User
FiredogSuper UserAuthor
Super User
January 31, 2024

Sorry to have gone dark on you, but my slide rule overheated and I’ve had to give it a rest. I’ll be back 😊

Noel | I have no official status; I'm just a volunteer who comes here to help other customers. My gear: Aclara SGM 1416-B Electricity-only E7 meter; Chameleon IHD3-PPMID-AAA | It may look as if I know what I’m talking about, but don’t let that fool you. |
Firedog
Super User
FiredogSuper UserAuthor
Super User
February 1, 2024

 Right, now we have all of January’s data in hand, I can try and debunk what the expert says 😉

We know that billing depends solely on the meter readings, regardless of what the usage data may show, especially when viewed with reduced precision at account.ovoenergy.com or in the app.  

However, the expert writes “… the key issue here is attempting to align the HH data to the meter reading (Billing) data... as they will not explicitly align...” Well, in my case, they do align as regards the total usage recorded by the meter. Here is a comparison for the past 92 days, conveniently 1 November 2023 - 31 January 2024:
  

 

Here we see that the reading after three months can be predicted exactly by aggregating the half-hourly figures for the period - the difference between 390.130 and 390.131 is of course insignificant. This is just what I would expect from a precision instrument like a modern smart meter, and I don’t understand why the expert says that usage data and register readings won’t align.

What I can’t find a rationale for is the variance in the peak/offpeak usage figures. The expert gave two reasons: the BST/GMT dichotomy, and the ‘random offset’ that varies the peak/offpeak switching time to protect the electricity network from intolerable surges. 

  • BST/GMT - that’s why I’ve chosen a quarter starting on 1 November, because it’s wholly within the GMT period. So we can rule that out as a factor for now.
  • Random offset. I rather thought that this was meter-specific, built-in from the factory, in which case it should be a constant number n of seconds for any individual meter. If this were skewing the peak usage/readings, I’d expect to see a constant difference, of n seconds’-worth of use at the 00:00-00:30 draw rate in my case. I don’t: the difference appears to be completely random, varying between 3Wh and 35Wh, but usually less than 15Wh and averaging 11Wh, always over-reporting peak usage. I can’t see any reason for it other than perhaps a minor variable delay in submitting the reading. 
     

Bottom line: it’s quite possible to construct a missing meter reading by summing the half-hourly usage figures since the last known reading and adding them on.
  

 

 

PS In case anyone wonders, there are 9 missing half-hourly usage figures, from one day in December where there were two power cuts. I was pleasantly surprised to see that the meter register and the Hh data still matched precisely that day. 48 Hh x 92 days = 4416 - 9 = 4407.

 

Noel | I have no official status; I'm just a volunteer who comes here to help other customers. My gear: Aclara SGM 1416-B Electricity-only E7 meter; Chameleon IHD3-PPMID-AAA | It may look as if I know what I’m talking about, but don’t let that fool you. |
Emmanuelle_OVO
Retired Moderator
Retired Moderator
February 2, 2024

Hey @Firedog,

 

I’ve managed to get a response from our smart meter expert: 

 

Randomised offset is applied to all configurable registers. The registers used for Billing. It is a singular thing. A random number is generated by the meter at the point of it being energised and configured. That value (which is between 0 and 1) is then multiplied by the parameter set by the Installing Supplier, which cannot be less that 600 seconds and more than 1799 seconds... This function must be done as it's a National Grid requirement and set out as an explicit obligation upon us. Also, it cannot be changed once set. The same value will be applied to every configurable register.. it was decided it would not only apply to load switching but any instance where a tariff changes whether load is linked or not.

 

So to answer the query stated, the offset of 5 minutes would apply to the start and finish of the period... so a 7 hour off peak, would commence at 00:05 to 07:05.. but, as it's in seconds, it may not be exactly 5 minutes.. it may be 4 minutes 43 seconds.. or whatever the random value generated made it to be.. hence the fact that attempting to align the HH Profile data to the Billing data generated from the configurable registers is always 'out'. It's not incorrect or inaccurate though.

Renewable Energy? Big Fan.