Retail Energy Code - Data Access Schedule June 2019 CoMC

Agenda Direction of Data Access Schedule (DES) Contracting Model Data Access Agreements Release of Data under REC

Direction of Data Access Schedule Expected to lean on Energy Data Taskforce – data ‘presumed open’ References ‘Data Access Principles’ – which are tbc Access to data will be defined by: Role for ‘Market Participant Enquiry Service Users’ – i.e. where there is a recognised MP Role Type e.g. Supplier / Transporter / MAM / MAP Individual justification for ‘Other Enquiry Service Users’ Data Access Matrix (DPM mk2!) Defines principles for assessment of adding / removing data items from the DAM led by REC Code Manager Defines principles for adding new User Types Will define audit rules Some threads to extract for early consideration Data Access Schedule drafted and expected to be issued in May Consultation

Current Contracting Model UNC DSC CDSP Third Party Services Service Definition UKLM DPM Data Access Agreement Shipper Transporter Supplier MAM Major Energy User Other

Data Access Agreements Currently DAAs are executed between the CDSP and any third party accessing data in accordance with the Third Party & Additional Services Policy under the DSC DSC Core Customers don’t need a DAA (covered under DSC provisions) REC Data Access Schedule (DAS) assumes that there will be a standard DAA (this may just be a front end and schedules with ability to add separate schedules) REC Data Access Schedule expects that all parties will require DAA Potential that REC will meet DAA requirement for REC parties All other Enquiry Service Users will require DAA (i.e. Shippers) REC Data Access Schedule is proposing to introduce a ‘Data Enquiry Services Administrator’ – DAA executed between Admin and Enquiry Service User This allows potential for electricity and gas models to be different - MRASCo understood to execute DAA – so Admin could be Code Manager / Other

Data Access Agreements REC proposes Data Enquiry Services Administrator could be the Code Manager, Enquiry Service Provider or other party (not a REC party) As Enquiry Service Provider it makes sense for CDSP to be the Data Enquiry Service Administrator who enters into the DAA with a third party Data Items will be made available in accordance with DAM/DPM but DAA will set out terms for receiving Data Items and the purpose for which the Data Items are shared, as well as data protection provisions and audit rights which will be standard requirements for the DAA As Service Provider CDSP should have the relationship with the party receiving Data to ensure control over the Data Items that are shared Under one of the Future Contracting Models, Shippers could continue to access Data Items under the DSC rather than entering into a separate DAA

REC Contracting Model UNC REC DSC CDSP / GRDA CDSP / GRDA Potential remains to provide direct services – e.g. specific APIs to DSC Core (+ Third parties) CDSP / GRDA DSC CDSP / GRDA Enquiry Service Administrator Instruction under DAA to provide Service REC Service Definition REC Data Access Matrix REC Data Access Agreement Shipper Transporter* Supplier* MAM Major Energy User Other

REC / DSC Hybrid Contracting Model UNC REC DSC CDSP / GRDA CDSP / GRDA Enquiry Service Administrator DSC Service Definition REC Service Definition UKLM DPM / REC Data Access Matrix REC Data Access Agreement Shipper Transporter Supplier MAM Major Energy User Other

Some Discussion Points … These aren’t intended to be exhaustive or leading!!!! REC Contracting Model + Provides a single model for control of Data Release + Reduces risk of dual governance - Relies on interface with UNC being effective REC / DSC Hybrid Contracting Model + Existing DSC Parties don’t need to execute DAAs + Retains [some] DSC Service Lines As Is / Control - Adds data governance (at odds with ‘Open data’ messaging?)

Release of Data Under REC Data within the gas Enquiry Service will be obtained from two routes CSS Provider – Registration Data Existing UNC provision Data from CSS Provider is limited As UNC parties, we need to understand treatment of the data items that we receive via the UNC currently following implementation of REC Transporter data Shipper data Supplier data (received via Shipper) The REC will categorise all data with the Owner / Master of the data item Owner will be the Market Participant responsible Master will be the Code responsible – so permission to release expected to be sourced from that Code prior to inserting into the REC DAM

Release of Data Under UNC CDSP Shipper Supplier Transporter Physical Data Flow ‘Regulatory’ (i.e. notional) Data Flow

Release of Data Under REC – Is this correct? Presumed this would be “Shipper Only” data items – i.e. those that don’t originate from Suppliers UNC Which Code is this flow governed under? UNC / REC? Future of UNC V5? Notional flow under REC of data originating from Supplier or their Agents Shipper CDSP / GRDA REC Supplier CSS Transporter Physical Data Flow ‘Regulatory’ (i.e. notional) Data Flow

Release of Data Under REC What data items are classed as Shipper Only? Expected that this is as specified in UNC Annex G-1 (CSS UNC Drafting) - ‘Group D - Settlement Details: User Specified’ Class of Supply Meter Point Meter Read Batch Period Meter Read Frequency Supply Point Capacity Supply Point Offtake Rate NTS Optional Commodity Detail LDZ Optional Capacity Detail Others? Seasonal Detail Interruptible Detail Any outbound data items to Shippers?

Questions / Follow Up Data Access Schedule will be within the REC Consultation – issued mid June- when contemplating your consultation responses we request that…. Consider the DAA Approach – which parties the DAA should be between (our proposal would be between the Enquiry Service User and the GRDA (Xoserve as CDSP), OR that the GRDA should also be the Data Enquiry Service Administrator Consider the data items and the treatment of these under the Codes Consider (and feedback to Xoserve) the impacts to the DSC Propose a further discussion at DSC Contract Managers during the consultation once parties have seen the Data Access Schedule