Data alignment of meter information through MHHS Migration
Summary
This Issue looks to address that when Meter updates are made during a Market Wide Half-Hourly Settlement (MHHS) migration, whilst the Meter Technical Details (MTDs) will be shared between participants, there will be no update sent to the Registration Service as the Gaining Meter Operator Agent (MOA) will not know that they need to send a D0312 (for reverse migration) or IF005 (for forward migration) and the Losing MOA cannot send the message.
Latest update and next planned activity
Date of latest update
Latest Update
30/04/2026 - The Code Manager has now published the I0240 - Scenario Guidance Document V2.0 on the REC Portal. This is available on the I0240 Proposal Page and the Market-wide Half Hourly Settlement Hub.
Impacts Overview
Impacted REC Documents
Schedule 14 - Metering Operations
Priority and rationale
High
Priority last updated on 29 May 2026
Solution development
Problem Statement
During MHHS migration, key Market Messages from the Losing MOA, such as D0312, IF005, D0205, and D0139, are rejected by the Registration Service, preventing updates to meter details and Energisation status. This creates a risk of data misalignment, as the Gaining MOA may not be aware that updates occurred and therefore cannot resend them.
No documents available.
There is currently no Change Plan.
Original submission
Change details
- - -
27 Jan 2025
Change details
Data alignment of meter information through MHHS Migration
• Once a forward migration has been initiated e.g. an MHHS agent request (IF031) issued for a non MHHS Metering Point then any further meter updates by the Losing MOA via the D0312 will be rejected by the Registration Service. • Similarly, once reverse migration has been initiated e.g. a switch request initiated by a Non MHHS Qualified Supplier in relation to an MHHS Metering Point, then any further meter updates by the Losing MOA via the IF005 will be rejected by the Registration Service. • In both of these scenarios there will be a change of agent event and MTDs shared by the Losing MOA to the Gaining MOA. These MTDs may include the updates following meter works or they may not. • If the meter update happens after the MTDs have been shared then the Losing MOA should send the updated MTDs to the Gaining MOA. There is a clear statement to cover this in the migration schedule: o 2.7.15, 2.8.15 and 3.8.7: Where the MTDs change before the Gaining MOA effective from date, the Losing MOA shall send revised MTDs. • We understand the issue is that whilst the MTDs will be shared between participants, there will be no update sent to the Registration Service as the Gaining MOA will not know that they need to send a D0312 (for reverse migration) or IF005 (for forward migration) and the Losing MOA cannot send the message.
There will be a misalignment in the data held with the Registration Service and that held between other industry parties. In addition, the Registration Service could issue an incorrect PUB_036 to parties which would need in updated MTD's being received from the MS and old MTD's from the Registration Service resulting in user intervention to correct the discrepancy.
There needs to be a mechanism in situ to be able to update the Registration Service
-
Impacts
No details provided
Other (please provide details in Additional information box below)
Alignment of industry data and no requirement for industry parties to align the data via manual interaction.
Schedule 14 - Metering Operations
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
-
No details provided
Priority & timing
Yes
This is required for MHHS Reverse Migration and given that this could start impacting industry from M8/M10 currently at Sept 2025, a resolution is required
-
-
No details provided
Other (please provide details in the Additional information box below)
Activity
Status has been changed to Issue Closed.
james.hardy has been allocated as Lead Analyst.
Orphaned SME: Lead Technical Analyst, vaishnsharma have been allocated as SME.