@
meldrewreborn
SMETS1 meters do not correctly record half-hourly data. When these meters were originally 'supplier; specific' and half hourly data was required there was an additional layer of calculation which was performed on the data by each supplier. Now that all the data flows through the DCC, it is their responsibility to massage the numbers into the correct format for processing by the supplier.
Each meter manufacturer provided it's own API for each supplier to be able to work with the data correctly. The problem lies entirely with the DCC, not the supplier or the meter itself.
From the government (BEIS):
It seems that SMETS1 meters record half hourly data as kW per half hour (not per hour) and therefore pre-DCC migration the SMETS1 SMSO was re-calculating this. It sounds like post DCC migration this recalculation step was lost and hence the issue you’re seeing.’
The issue was impacting many SMETS1 meters built by different manufacturers. As Octopus is the only supplier that uses 30 minute data for billing, their t-o-u tariff customers were the ones most affected.
SMSO:
Smart meters need a smart back-end system, which is why Secure has developed the Smart Metering Operator Services (SMSO) system. This system controls all aspects of meter operation, and is the interface between your business systems and your meters, using industry-standard web-service APIs.
We also realise that the day-to-day management of smart meters should not be a burden on your business, so we offer a wide range of services to help you get started in smart metering. These range from a full, web-based, smart metering management system through to consultancy services to help you integrate your business system with our SMSO system. For us, partnerships come first and this is about working together.’
On meter adoption, I believe that the DCC takes over this function.
The reference to Octopus was from a few years ago when they were the only supplier offering ToU tariffs. Now that they are more common across a range of suppliers the issue is becoming more prevalent. It seems that DCC have not properly integrated the SMSO architecture into their systems.
Another reason they are simply not fit for purpose.
Half hourly readings are only necessary for two reasons.
1. Flexible ToU tariffs where the rate changes on half-hourly intervals. I think Octopus Agile is the only system that uses this data explicitly.
2. To allow recording of data into a spreadsheet or graph for statistical puropses.
All that is needed for E7 or Next Drive is to take the readings at the point the rate changes. That is to say, at the end of the peak period, take a single total kWh reading. Take another reading at the end of the off-peak rate. It's as simple as that and does not need to be any more complicated than that!
