Gas Meter Type Code - Thermal Mass Measurement
Date of latest update
Type
Issue
ID
I0184
Urgent
No
Latest Update
16/10/2024 - This Change Issue has been withdrawn at the request of the proposer.
Summary
Empty
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
Stages Selection
I0184 - Change Proposal Form (PDF)
Company Name
Octopus Energy Ltd
Review status
Review required
Improvements to CSS Business Process Logic
Date of latest update
Type
Change
ID
R0178
Change Category
Change Path
Priority
Urgent
No
Latest Update
17/06/2026 - The Code Manager has published an Update to Plan. This will be presented to the REC Technical Expert Panel at their meeting on 24 June 2026.
Summary
This change proposal is aimed towards rectifying a collection of issues that were identified with the CSS Business Process Logic. These have been identified as follows: 1. Deactivation of an active reg. whilst in-flight switch in progress 2. Deactivation of a prior cancelled registration 3. OFAF switch containing multiple MPxN
Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
25 June 2027
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- Deactivation of an active reg. whilst in-flight switch in progress As mentioned previously, the ‘Deactivation of an active reg. whilst in-flight switch in progress’ issue did have an existing REC CP raised and therefore is further along the discussion process compared to the other two issues identified. Initial discussion outlined that the most appropriate solution for this change proposal should consider the business needs and the desired outcomes. It was noted that from a business perspective, if the switch has already been accepted, then it should still go through and not be cancelled. Therefore, the following points were raised: • It was acknowledged that there are multiple solution options/approaches that could potentially be employed to resolve this issue. As such, and to avoid being overly prescriptive, it is requested that CSS provider investigate all possible options and outline their recommendation for the most suitable approach, which would be developed/progressed further through the subsequent Impact Assessments. • However, the aim is for an effective solution to be developed which would ensure that the consumer is switched with the original effective date being used and that CSS systems could cater for such registration events whilst following the normal Gate Closure processes. • Where possible, the solution should also look to proactively mitigate the impact of this scenario, as opposed to working on a retrospective basis which can lead to the issue persisting over an extended period of time. It was also noted that consideration would need to be given to state of the meters as this would also have an impact on whether switches are able to progress: Therefore, the following points were raised: • The solution would need to consider how the incumbent supplier has deactivated the meter and whether it has been moved to a ‘terminated’ state or a ‘dormant’ state. o Dormant – The meter is inactive. Note that this is a temporary state and therefore the meter could be put back into service. o Terminated – The meter has reached end of life and cannot be reinstated. Note that this is a permanent state. • If the incumbent supplier has moved the meter into a ‘terminated’ state, the in-flight switch would then need to be cancelled. • However, for the ‘dormant’ state, the following two options would be available in terms of what could happen to the status of the meter and thus the in-flight switch: o Moves from ‘inactive’ to ‘active’ (continue with the switch) o Moves from ‘inactive’ to ‘cancelled’ (cannot continue with the switch)
- Deactivation of a prior cancelled registration and OFAF switch contains multiple of the same MPxN It is noted that the initial approach discussed was to add new Business Data Validation Rules (BDVR) to stop these issues from occurring. However, this was only discussed at high-level and therefore we request that the CSS provider confirm this approach and provide further details as this change proposal progresses.
Problem Statement
1) Deactivation of an active reg. whilst in-flight switch in progress: There are instances where the incumbent supplier is withdrawing prior to the ‘Supply Effective from Date’, causing the accepted switch to fail at Gate Closure which occurs at 17:00hrs. This creates the scenario in which there is no longer a losing supplier for the consumer to switch from, and therefore the switch process stalls and cannot be progressed. Therefore, this has a direct impact on consumers who have a switch request which has already been accepted but CSS is not able to progress further as the switch process stops. Indeed, there have been a total of 82 missing messages observed since 1st January 2023, of which 66 messages have been related to switches where there was no registered Supplier recorded at Gate Closure. The 30th September 2023 Gate Closure was particularly impacted by this scenario and resulted in 45 registrations which did not become effective on 14th October 2023 as planned. It should also be noted that the 1st October is one of the key contracting dates for large Industrial and Commercial (I&C) consumers, consequently increasing the impact to consumers in this instance. 2) Deactivation of a prior cancelled registration: This scenario occurs when the registered supplier of a MPxN (via the active registration) is the same supplier that cancelled a previous switch for the same MPxN. In this case there is the possibility that the supplier could attempt to deactivate the active registration by accidentally providing the cancelled registration identifier. Currently, CSS still accepts the deactivation request and erroneously changes the cancelled registration state from cancelled to inactive, sending out securedInactive messages. Currently, after an MPxN is disconnected, the Supplier is required to submit a deregistration request to CSS. Therefore, there is a possibility that the suppliers could submit this request for a cancelled registration not active registration. CSS would still accept this request as the Business Data Validation Rules (BDVR) lack coverage of this case; in such cases the Supplier may incorrectly believe that they have deregistered the MPANs. 3) OFAF switch containing multiple MPxN: This is the instance where the end user sends through a One Fail All Fail (OFAF) switch with the same MPxN contained within the payload 2 or more times. Multiple registration IDs are created for the same MPxN, and the registration is left in an incorrect state given a lack of appropriate BDVRs. Indeed, there has been a further reported incident regarding an OFAF transaction of the same MPxN. The primary MPxN was associated with a secondary MPxN and therefore two registrations were created for the primary and secondary MPxN, equating to four registrations in total. There was then an objection raised but this only cancelled 1 of the 2 registrations for each MPxN. The remaining 2 registrations proceeded through gate closure.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
maxime.van-eyseren@capgemini.com
R0178 - Change Proposal Form
R0178 - Change Report (Proposal Plan) V2.0 (18.02.2025)
R0178 - Update to Proposal Plan V1.0 (Approved) 18.02.2025
R0178 - Consolidated Impact Assessment Responses (Non-Confidential) 18.03.2026
R0178 - Change Report (For Consultation) V1.0
R0178 - Update to Plan (17.06.2026) Pre-Approval
Company Name
REC Technical Services
Review status
Review required
Clarify & Strengthen CRS Providers Requirements
Date of latest update
Type
Change
ID
R0168
Change Category
Change Path
Priority
Urgent
No
Latest Update
This Change Proposal was implemented on 28 February 2025.
Summary
The RECCo MSI review focused on the analysis and assessment of; Code compliance, performance, impacts and insights from lessons learned feedback from impacted stakeholders. These assessments thematically articulated changes and improvements identified to assure industry market participants that clear and appropriate action is, and will be, taken to prevent, detect and mitigate the risks and impacts of another event, and prepare for the right response to any future incidents. This Issue has been raised to address learnings from the P1 switching incident in July 2023.
Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
28 February 2025
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- Root Cause Communication: That the DCC, in its role as Switching Operator, delivers, clear, accurate, timely information on the incident root cause, as soon as possible, once it has obtained a reasonable understanding. Both to offset the risks of uncertainty and limited information introduce, ensuring Switching parties (like Supplier, TPIs and Networks) have the right information to enable meaningful engagement, assist their end-consumers, and all impacted Market Participants can more proactively manage the incident impacts, including making appropriate plans in response to the incident and its resolution. Switching Operator's End-Consumer Communication: Introduce a requirement for the DCC, in its role as the Switching Operator, to provide end-consumer appropriate information for REC Parties and Non-REC Parties use to determine communication and action for their Consumers.
- Switching Operator, Switching Incident Impact Assessment: This change should clarify the existing Switching Operator’s broader obligation to assess an incidents impact on the wider Switching Arrangements (set out in REC Schedule 26, Switching Service Management Schedule (SSMS), section 1.7, or Major Switching Incidents starting at section 2.9), to ensure the Switching Operator facilitates the most effective, efficient (time, cost, resource) overall Switching industry solution is promoted and implemented. Incident Wider Switching Impact Assessment: Clarify that if a Major Switching Incident is not going to be resolved within defined Service levels (4 hours), then the DCC in its role as Switching Operator should determine the impact on compliance with the REC end-to-end Switching Arrangements, and work with Ofgem, and the Code Administrators for BSC, UNC and DCUSA, and RECCo, to identify the cross code impacts/impacts on other Codes when managing an incident and developing an appropriate solution for industry, with least negative impact to end-consumers.
- Refresh and testing of Switching Operator’s (SO) incident related policies, processes, and procedures, to ensure they remain fit for purpose.
- Refresh and testing of Switching Operator’s (SO) incident related policies, processes, and procedures, to ensure they remain fit for purpose.
Proposed Solution Document
Document title
I0168 Switching Operator MSI Best Practice Document - for RFI and Industry Comments (02.08.2024)
Archive
Off
Document title
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 05.12.2024
Archive
Off
Document title
Switching Operator (SO) Service Definition (R0168 - Red-lining) 05.12.2024
Archive
Off
Document title
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 05.12.2024
Archive
Off
Document title
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024 (Word Version)
Archive
Off
Document title
R0168 Draft Switching Operator Best Practice Document (V1.0 for Industry Consultation) 05.12.2024 (PDF Version)
Archive
Off
Document title
R0168 - Change Report (for Consultation) 12.12.2024
Archive
Off
Document title
Schedule 26 - Switching Service Management Schedule (R0168 - Red-lining) 28.01.2025
Archive
Off
Document title
Central Switching Service (CSS) Service Definition (R0168 - Red-lining) 28.01.2025
Archive
Off
Document title
Switching Operator (SO) Service Definition (R0168 - Red-lining) 28.01.2025
Archive
Off
Document title
Major Switching Incident: Switching Operator Best Practice Document V0.2
Archive
Off
Document title
Major Switching Incident: Switching Operator Best Practice Evaluation Form V1.0
Archive
Off
Problem Statement
On 6th July 2023, a Major Switching Incident occurred with the Central Switching Service ((CSS) operated by the Switching Operator and CSS Service Provider, the Smart Data Communication Company (DCC)). It prevented the successful completion of that day’s planned electricity and gas, supply switches and new registrations. The CSS was stabilised post-incident and any new requests submitted after 9 a.m., 6th July were processed successfully. Through the collective action of the Switching Operator and industry parties, the CSS sent the missing industry messages to give effect to the intended switches and new registrations during the period of the 2nd to the 8th of August 2023. Priority 1 (P1) Major Switching Incidents of this nature are required to be resolved within 4 hours; however, DCC reported it took 1,605.6 hours in this instance. This incident had significant impacts on multiple industry parties and end consumers, demonstrating a clear need for improvement in the arrangements managing switching services and response to major incidents. The Retail Energy Code Company ((RECCo) with the assistance of its Code Manager) completed an end-to-end incident review; to identify the root cause, consider the efficiency and effectiveness of the incident management response, assess the improvements required, and identify appropriate actions for risk mitigation. With the overarching objective that by delivering the identified review recommendations, these actions should limit the possibility, or minimise the impact of, any future major switch incidents.
Stages Selection
SME
SME Role
Lead Assurance Analyst
SME User
vaishnsharma@deloitte.co.uk
I0168 - Issue Form
I0168 Switching Operator MSI Best Practice Document - for RFI and Industry Comments (02.08.2024)
I0168 - Change Report (Change Plan) (Approved) 17.09.2024
I0168 - Update to Proposal Plan (Approved 30.10.2024)
R0168 - Consolidated Consultation Responses (Non-Confidential) 20.01.2025
R0168 - Change Report (Final Reccomendation) 04.02.2025 (Approved) V2.0
Company Name
-
Review status
Review required
Alignment of Market Message D0225 ‘consent to share flag’ to support PSR data sharing
Date of latest update
Type
Change
ID
R0139
Change Category
Change Path
Priority
Urgent
Yes
Latest Update
This change was implemented on the 12th April 2024.
Summary
Ofgem have been in with discussion with Energy Suppliers this year, requesting them to voluntarily change how they use the consent option within the Priority Services Register (PSR) flow. This Change Proposal (CP) has been raised to make sure the Market Message mirrors the process agreed between Ofgem and Energy Suppliers by re-naming the Priority Services Register (PSR) Data Item DI51497 (J2208) as “Lawful basis for sharing” and to amend the relevant clauses in REC Schedule 13 if needed.
Change Plan
Party Impact Assessment
Completed
Start:
11 Aug 2023Due:
05 Jan 2024Completion:
05 Jan 2024Preliminary Change Report Issued
Completed
Start:
05 Jan 2024Due:
26 Jan 2024Completion:
26 Jan 2024Consultation
Completed
Start:
26 Jan 2024Due:
09 Feb 2024Completion:
09 Feb 2024Final Change Report Issued
Completed
Start:
09 Feb 2024Due:
16 Feb 2024Completion:
16 Feb 2024Responsible Committee Decision
Not Started
Start:
16 Feb 2024Due:
28 Feb 2024Completion:
Appeal Window Closure
Not Started
Start:
28 Feb 2024Due:
13 Mar 2024Completion:
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Date
12 April 2024
| Included changes | Affected REC Items | |
|---|---|---|
| R0105 | Review of ONAGE SLAs |
|
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed Solution Document
Document title
Redlining - DI51497 - J2208 - Consent to share data obtained
Archive
Off
Problem Statement
The current PSR Data Item DI51497(J2208) ‘Consent to share data obtained’ does not mirror the legal basis for sharing data that DNOs rely on, or the process that Suppliers have planned to have in place by early 2024.
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
beth.brown@capgemini.com
R0139 - Change Proposal Form
Consolidated Impact Assessment Responses
Consolidated Consultation Responses R0139
R0139 Change Proposal Plan v1.0 Approved
R0139 Initial Assessment Report v1.1 Approved
R0139 - Extension to Change Plan v1.0
R0139 Preliminary Change Report v1.0
R0139 Final Change Report v1.0 approved
ICO letter to Ofgem
R0139 redlining - DI51497 - J2208 - Consent to share data obtained
Company Name
Energy Networks Association
Review status
Review required
Updates to the Data Access Matrix
Date of latest update
Type
Change
ID
R0130
Change Category
Change Path
Priority
Urgent
No
Latest Update
21/05/2024 - This change proposal has been withdrawn and the adoption window is closed. There is no longer the requirement for the requester to have Enquiry Services Data.
Summary
There are organisations that are named in Schedule 12 - Data Access that are not recorded in the gas and/or electricity Data Access Matrix (DAM). This means it is not possible for the Code Manager to provision them access. All organisations listed in Schedule 12 to access data in the REC should have an entry in the Data Access Matrices. This Change Proposal has been raised to review the Schedule and DAMs and take forward the necessary changes.
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Fuel
Date of Update to Priority
Solution Development
Stages Selection
R0130 - Change Proposal form (downloadable version) 16.06.2023
Company Name
REC Code Manager
Review status
Review required
Clarifying Event of Default requirements
Date of latest update
Type
Change
ID
R0129
Priority
Urgent
No
Latest Update
04/10/2023 - Following the approval of R0138, this change has been withdrawn.
Summary
Following several recent events of non-payment for services and REC defaults it is clear that the event of default provisions in the Code are unclear. This change seeks to introduce clarity to the REC Main Body.
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
R0129 - Change Proposal form (downloadable version) 16.06.2023
Company Name
REC Code Manager
Review status
Review required
Supplier compensation for Network Party driven MPXN or GSP Group changes
Date of latest update
Type
Change
ID
R0112
Priority
Urgent
No
Latest Update
28/07/2023 - The Proposer has withdrawn R0112. This Change Proposal is open for adoption for 10 Working Days, after which time it will be fully withdrawn on the REC Portal. If you wish to adopt the Change Proposal, you can do this via the ‘Adopt Proposal’ button by 23:59 on 12 August 2023.
Summary
Empty
Impacted Consumers
Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
R0112 - CP Form (Downloadable Version)
Company Name
ScottishPower Energy Retail Ltd
Review status
Review required
CSS Message Time Stamping
Date of latest update
Type
Change
ID
R0107
Urgent
No
Latest Update
11/08/2023 - This Change Proposal has been withdrawn. During the progression of the Preliminary Impact Assessment work, it was found that an existing data item ‘EventDate’ could be leveraged to address the issue stated in the Change Proposal. R107 will be open for adoption until 25/08/2023.
Summary
Empty
Change Plan
Test
In Progress
Start:
14 Apr 2023Due:
19 Mar 2026Completion:
19 Mar 2026Impacted Consumers
Impacted REC Documents
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Status
Date Raised
Date of Update to Priority
Solution Development
Stages Selection
SME
SME Role
Lead Technical Analyst
SME User
caroline.milner@capgemini.com
R0107 - Change Proposal Form
Company Name
DCC
Review status
Review required
Clarifications to the Theft Detection Incentive Scheme
Date of latest update
Type
Change
ID
R0091
Change Category
Change Path
Priority
Urgent
No
Latest Update
02/04/2023 - Change Proposal implemented on 01 April 2023
Summary
The Energy Theft Detection Incentive Scheme (TDIS) seeks to encourage Suppliers to undertake theft investigations. Following the completion of the first scheme year operated wholly under the REC, there have been several areas of the Code identified where additional clarity would benefit the administration of the TDIS.
Change Plan
Initial Assessment Report Issued
Completed
Start:
23 Jan 2023Due:
27 Jan 2023Completion:
27 Jan 2023Change Proposal Plan Issued
Completed
Start:
27 Jan 2023Due:
27 Jan 2023Completion:
27 Jan 2023Preliminary Change Report Issued
Completed
Start:
07 Feb 2023Due:
17 Feb 2023Completion:
17 Feb 2023Consultation Issued
Completed
Start:
17 Feb 2023Due:
17 Feb 2023Completion:
17 Feb 2023Responsible Committee Decision
Completed
Start:
17 Feb 2023Due:
24 Mar 2023Completion:
24 Mar 2023IAR and CPP Approval
Completed
Start:
27 Jan 2023Due:
07 Feb 2023Completion:
07 Feb 2023Impacted REC Documents
Impacted REC Parties and Market Participants
Status
Implementation Date
01 April 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0100 | Update to Error Handling Documents |
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As an Energy Supplier, I need my TDIS obligations to be clear to ensure I can meet the requirements appropriately.
- As the Code Manager, I want all Suppliers to be clear on the required Energy Theft reporting so that the scheme can be effectively administered.
- As RECCo, I want to ensure that all Suppliers have clear obligations to ensure the effective administration of TDIS to support the Theft Reduction Strategy.
Proposed Solution Document
Document title
R0091 - Legal Text (as at IAR/CPP)
Archive
Off
Document title
R0091 - Legal Text at FCR 21.03.2023
Archive
Off
Document title
R0091 - Legal Text FINAL
Archive
Off
Document title
EMAR Link
Archive
Off
Problem Statement
To enable REC Parties and their agents to successfully meet the obligations of the TDIS, the REC needs to accurately reflect the intention of the requirements and current processes.
Stages Selection
R0091 - Change Proposal Form
R0091 - Change Proposal Plan (Approved) 07.02.2023
R0091 - Initial Assessment Report v1.0 (Approved) 07.02.2023
R0091 - Preliminary Change Report v1.0 17.02.2023
R0091 - Consolidated Consultation Responses
R0091 - Final Change Report v1.0 (Pre-Vote) 21.03.2023
R0091 - Final Change Report v2.0 (Post-Vote) 24.03.2023
Company Name
-
Review status
Review required
Make Shipper NExA values available on the GES portal
Date of latest update
Type
Change
ID
R0088
Other Industry Codes impacted
Change Path
Priority
Urgent
No
Latest Update
03/11/23 - This change was implemented on 03 November 2023 as part of the November 2023 REC Release
Summary
This Change Proposal seeks to deliver the consequential REC changes for Uniform Network Code (UNC) Modification 0701 Aligning Capacity Booking under the UNC and arrangements set out in relevant NExAs. Modification (MOD) 0701 will ensure that the daily capacity allowed by the Network Exit Agreement (NExA) and that permitted by the UNC are aligned.
Change Plan
Initial Assessment and Change Proposal Plan issued
Completed
Start:
16 Jan 2023Due:
24 Mar 2023Completion:
24 Mar 2023Initial Assessment Report and Change Plan approved
Completed
Start:
24 Mar 2023Due:
04 Apr 2023Completion:
04 Apr 2023Service Provider Impact Assessment
Completed
Start:
04 Apr 2023Due:
25 Apr 2023Completion:
24 Apr 2023Party Impact Assessment
Completed
Start:
25 Apr 2023Due:
31 May 2023Completion:
31 May 2023Preliminary Change Report published
Completed
Start:
31 May 2023Due:
16 Jun 2023Completion:
16 Jun 2023Consultation
Completed
Start:
16 Jun 2023Due:
21 Jul 2023Completion:
21 Jul 2023Final Change Report published
Completed
Start:
21 Jul 2023Due:
18 Aug 2023Completion:
18 Aug 2023Responsible Committee decision
Completed
Start:
18 Aug 2023Due:
30 Aug 2023Completion:
30 Aug 2023Impacted Consumers
Impacted REC Services
Impacted REC Parties and Market Participants
Status
Implementation Date
03 November 2023
| Included changes | Affected REC Items | |
|---|---|---|
| R0104 | Clarifying requirement for continuous billing following an Erroneous Switch |
Documents
| Name | Version | Last updated | Actions |
|---|---|---|---|
| 1.0 | 08 Jun 2026 |
|
|
| 1.0 | 08 Jun 2026 |
|
Download
Copy link
Implementation Status
Date Raised
Fuel
REC Decision Maker
Date of Update to Priority
Solution Development
Proposed solution summary
- As a Consumer, where I have entered a bi-lateral NExA with the relevant Transporter, I want my Shipper and Transporter to have access to all the data they need when capacity referrals to the Gas Transporters are required.
- As a Gas Transporter, I want the details of the NExA to be held in GES, to increase visibility of the existence of the NExA and to provide details of the offtake parameters.
- As a Gas Shipper, I need to understand both that a NExA exists, and that I have visibility of the offtake parameters relative to the site, so that I can ensure that I take the necessary actions to ensure the Consumer has the appropriate booked Supply Point Capacity.
Proposed Solution Document
Document title
R0088 Gas DAM v3.1 at FCR (18.08.2023)
Archive
Off
Problem Statement
XRN 5186 will make updates to the GES to implement the solution for UNC MOD 701. Following Ofgem’s decision to approve MOD 701, a REC Change Proposal is required to make changes to the REC DAM to enable the delivery of the full cross code solution.
Stages Selection
SME
SME Role
Lead Technical Analyst
R0088 - Initial Assessment Report v1.0 (Approved) 04.04.2023
R0088 - Preliminary Change Report (Post-Vote) 28.06.2023
R0088 - Change Proposal Plan v1.0 (Approved) 04.04.2023
R0088 - Final Change Report v2.0 (Approved) 30.08.2023
R0088 - Final Change Report v1.0 (Pre-Vote) 18.08.2023
Company Name
Xoserve
Review status
Review required