ESB Networks AIP Programme Meeting of the IGG

ESB Networks AIP Programme Meeting of the IGG, February 1 st, 2007

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 1

ESB Networks AIP Programme : 1. Review of where we are Before the Special IGG of 7 th June 2006, a first draft document ‘Impact of AIP on ROI Retail Market’ issued from ESB Networks AIP programme. This set out the impacts for the Irish Retail Market that had at that time been identified by ESB Networks as a result of the AIP, in so far as the requirements were known. Before the IGG of the 22 nd June 2006, all key design issues were included in Appendix 8 in the second draft of the discussion document. At the IGG on the 22 nd June there was a walk through of each of the issues in that document. Before the IGG of the 13 th July , updated Appendix 8 issued on 7 th July , ver 0. 3, containing feedback from Market Participants, SIMDRACS Co-Ordinator, new requirements that were received from Regulatory Authority, and review of Design Issues by ESB Networks. Following the IGG of the 13 th July, four Market Participants responded to specific queries raised at that IGG. At the IGG of August 10, the responses were debated. In early August , CER/SIMDRACS gave approval to proceed with the detailed design based on what had been discussed to date with the IGG. At the IGG of 21 st September there was a recap of the high level design for AIP and an update on issues. On 7 th October draft ver 0. 4 issued, followed on 13 th October by version 0. 41 which had the marked-up changes of ver 0. 4 removed. This document was reviewed at the Special IGG on 16 th October. Option 3 of the Message Model was presented and all Market participants were asked to respond by 19 th Oct. MCRs issued in 3 batches over 24 th, 25 th and 26 th October. All Market participants responded by 26 th October to Option 3 : 4 in favour, 3 not. Option 3 of the Message Model was incorporated into these MCRs. 2

ESB Networks AIP Programme : 1. Review of where we are At the IGG of 1 st November, draft ver 1. 0 MCRs and issues were discussed. Retail Market Participant Comments were fed back and baselined ver 1. 1 MCRs were issued on 15 th November. On 6 th December draft ver 0. 5 issued having been updated with the outcome of the discussions from the Special IGG on the 16 th October and the IGG on the 1 st November. It summarises the contents of the ver 1. 1 MCRs. At the IGG of 14 th December, alternative proposals for MCR 063 were presented and comments were requested. Two Market Partcipants have responded On 21 st December ver 1. 2 of MCR 123 issued for comments. Two comments have been received. On 8 th January 2007 ver 1. 0 ‘Impact of AIP on ROI Retail Market’ issued , which was a cleaned-up copy of draft ver 0. 5 without the marked-up changes. 3

ESB Networks AIP Programme : 1. Review of where we are……. contd ü 18 th May - Introduction ü 1 st June - Draft ver 0. 1 ‘Impact of AIP on ROI Retail Market’ issued to IGG ü 7 th June - Special IGG ü 21 st June - Draft ver 0. 2 ‘Impact of AIP on ROI Retail Market’ issued to IGG ü 22 nd June - IGG discussion on Appendix 8 – Key Issues - TAG discussion on Key Issues ü 29 th June - Responses from Market Participants ü 4 th July - SIMDRACS Co-Ordinator clarifications/decisions ü 7 th July - Draft ver 0. 3 [Appendix 8] ‘Impact of AIP on ROI Retail Market’ issued ü 13 th July - Special IGG ü 10 th Aug - Update to IGG ü 21 st Sept - Update to IGG ü 6 th October - Draft ver 0. 4 ‘Impact of AIP on ROI Retail Market’ issued ü 13 th October- Draft ver 0. 41 ‘Impact of AIP on ROI Retail Market’ issued 4

ESB Networks AIP Programme : 1. Review of where we are……. contd ü 16 th October - Special IGG - Draft ver 0. 41 ‘Impact of AIP on ROI Retail Market’ ü 24 th, 25 th, 26 th October - MCRs issued in 3 batches ü 1 st November - IGG review of MCRs, ver 1. 0 ü 14 th November - Comments/Queries on MCRs ver 1. 0 issued ü 16 th November - ver 1. 1 of MCRs issued ü 6 th December - Draft ver 0. 5 ‘Impact of AIP on ROI Retail Market’ issued ü 14 th December - Update to IGG, including alternative proposals for MCR 063 and for which two Market Partcipants have commented. ü 21 st December - ver 1. 2 of MCR 123 issued for comments ü 8 th January 07 - Ver 1. 0 ‘Impact of AIP on ROI Retail Market’ issued 5

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 6

A. B ESB Networks AIP Programme : 2 Upate on Issues SIMDRACS items There remain a number of key outstanding items and we will formally bring proposals to the IGG when the detailed requirements are known, viz. § Data Queries and AD Hoc Aggregations § Material Differences Issue 20 Issue 18 § Consumption Adjustments inside or outside the 13 months • Update - CER Consultation planned during 2007 Issue 19 In addition, the following issues are outstanding • Definition of Working days Issue 1 • Future Use of SSAC Issue 2/A 1 • Calendar for Aggregation Issue 7 • Metering Responsibilities - placeholders in MCRs • Non Participant Generators and SOLR event - with SIMDRACS Co-Ordinator • Eir. Grid method of validation, estimation, substitution - this item has been moved to the main IGG forum 7 Issue 23

ESB Networks AIP Programme : 2 Upate on Issues ……. contd SIMDRACS C RA 324 As stated at the IGG of 14 December: • RA 324 will not be implemented by SMO prior to go-live • impacts on a Small number of Trading sites with firm/non firm access calculations • Unique ASU will be needed where not a TSSU • Import data is Price-Effecting and is needed by SMO on 7 day week, calendar day basis • RA 324 Mitigations strategy was developed by SIMDRACS co-ordinator and work continues within the SIMDRACS forum - date for final resolution is set at 6 th March 8

ESB Networks AIP Programme : 2 Upate on Issues ………………. . contd D Cutover/Transition • Transitional Arrangements for Non-Participant Generators Issue 22 • Update - have requested a formal meeting with the CER on this and will give an update at the next IGG • Eirgrid requirements in respect of data after cutover Issue A 3 • Update - we expect to be able to provide the data in the required formats, will be confirmed after testing • Investigate if any Trans sites with MEC < 10 MW Issue A 6 • Update - There are no Trans sites with MEC < 10 MW - propose to close this 9

ESB Networks AIP Programme : 2 Upate on Issues ………………. . contd New Item E. Estimations for Indicative aggregations for QH sites We are currently considering estimates for indicative aggregations for QH sites We propose to calculate basic estimates during Data Aggregation for QH sites with no reads [and as agreed already, these will not be issuing] And on D+4 if there are no reads, then PDS will provide MRSO with estimates for Initial Data Aggregation in accordance with the QH Estimation, Substitution and Validation rules. At the next IGG we will present proposals for the calculation of the estimates for QH sites for use in Indicative Data Aggregation 10

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 11

ESB Networks AIP Programme : 3. MCRs MCR 123 ver 1. 2 and proposed sundry changes A. MCR 0123 ver 1. 2 : WPO 012 : To nominate / denominate a Supplier as a recipient of Participant Generator messages 341, and 504, 504 s, 594 and 597 B. Proposed Sundry changes , Clarifications on the following MCRs MCR 0112 : Data Aggregation MCR 0117 : Aggregation Briefing paper MCR 0120 : Data Items and Definitions MCR 0125 : WP 14 Distribution Connected Non Participant Generator Export Arrangements MCR 0115 : MPD 3 - Objections and Cancellations MCR 094 : MPD 2 - Change of Supplier - QH Metered MCR 095 : MPD 6 - New QH Metered Connections MCR 068 : Amendments to 591 Market Message C. ‘Impact of AIP on ROI Retail Market’ document - propose to hold off on making changes to this document till later 12

ESB Networks AIP Programme : 3. A Ver 1. 2 of MCR 0123/WP 012 WPO 012 : To nominate / denominate a Supplier as a recipient of Participant Generator messages 341, and 504, 504 s, 594 and 597 : [MCR 123] - Ver 1. 2 issued 21 st December • if a generator nominates a supplier to receive their messages then it must be for all GUIDs that fall under that Generator ID and not just selective GUIDs The reason for this proposal is to simplify processing requirements. 2 queries were received • clarification on scope issued on 11 th January that MCR 0123 only concerns Participant Generators, the design for Non-Participant Generator data is not affected by MCR 0123 / Working Practice 12 i. e. Non-Participant generator data will be sent to the appropriate Supplier that is registered for each export arrangement. • The second query was ‘If the system can be set up to send NP Generator data to more than one supplier then can it not also be configured to send PGenerator to more than one supplier if the generator requests it? • Would like to understand today if there is a real Business need for this 13

ESB Networks AIP Programme : 3. B Proposed Sundry changes to MCRs MCR 0112, MCR 0117 § The SIMDRACS forum has agreed to send an email to the SMO where the measured quantity of an interval has been set to zero in the netting calculations for non-participant generator data. This will be a copy of the email that is being sent to the Supplier. • MCR 0112: Data Aggregation • MCR 0117 : Aggregation Briefing paper 14

ESB Networks AIP Programme : 3. B Reading Data Status Field § Proposed Sundry changes to MCRs MCR 0120, MCR 0117 § The SMO have clarified the values to be used in the Reading Data Status Field Proposed Clarification to be added to MCR 0120: Data Items and Definitions ‘ A code of 0 denotes estimated readings while a code of 1 denotes Actual readings’ In addition, the following was discussed in the SIMDRACS forum The SIMDRACS rules for determining whether an aggregation of meter readings was estimated or actual was based on the concept where there was only one meter reading to be considered per MPRN. This may not be the case where there is Generation on the site, particularly where there is splitting of the generation between several suppliers outside of the market. • Therefore, it is proposed that when calculating the value of this flag that the actual/estimated value will be determined only from import meters • Also proposed is that where two 15 minute intervals are amalgamated together to a 30 minute trading period, if either or both of the 15 -minute meter reading is an estimate then the 30 minute trading period metered volume will be considered as an estimate. MCR 0117 : Aggregation Briefing paper 15

ESB Networks AIP Programme : 3. B Proposed Sundry changes to MCRs MCR 0125 Non-Participant Generators: § The SIMDRACS forum agreed that the factor of 20 can be changed to 1. 5 § Therefore, am proposing amend MCR 0125: WP 14 Distribution Connected Non Participant Generator Export Arrangements to read : It is a Regulatory requirement that in the new manual registration process for Non-Participant Generation, a Supplier must show that they have historic demand that has been (in all Trading Periods) 1. 5 times greater than the maximum contracted output of all out-of-market generation contracted to that Supplier Unit. 16

ESB Networks AIP Programme : 3. B Proposed Sundry changes to MCRs MCR 094, MCR 095, MCR 115, MCR 0120 Meter Point Registrations - sundry changes proposed , for alignment of Wholesale & Retail Market Registrations for Trading sites MCR 0115/MPD 3 Objections and Cancellations § that the title of MCR 115 should be changed from ‘COS Objections and Cancellations’ to ‘Objections and Cancellations’ § that will validate the incoming 011 Cancellation Message so that Cancellation requests will be automatically rejected for New Registrations for Trading Site [currently only COS] and that for these rejections, the new Reject Reason/Code ‘TSR’ will apply on Market Message 111 R § that New Connections and COS will not automatically time out for Trading Sites and instead that MRSO would contact the Supplier/SMO as appropriate § MCR 095 MPD 6 - New QH Metered Connections § MCR 094 MPD 2 - Change of Supplier - QH Metered § MCR 0115 MPD 3 - Objections and Cancellations § Description of the reject reason for the Reject Code ‘SSS’ to be changed from ‘SSAC invalid for the Supplier’ to ‘SSAC invalid for the Supplier Unit’ § MCR 0120 Data Items and Definitions 17

ESB Networks AIP Programme : 3. B Proposed Sundry changes to MCRs MCR 068 : Amendments to 591 Market Message The details of this Change request currently read : The 591 market message to be amended to only allow valid combinations of DLF & Load profile Proposed Clarification to be added to the MCR - The 591 will be sent for each Supplier Unit/SSAC combination. - The 591 market message will be checked for each standard profile/DLF combination and if there are no MPRNs registered for that settlement day then this DLF and standard profile combination segment will not be populated on the message. 18

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 19

ESB Networks AIP Programme : 4. Market Trials Scripted Phase Mid July to Mid September Unscripted Phase Mid September to end October To support SMO requirements, MRSO are to send the SMO 8 prefabricated 590 messages MRSO - daily send SMO 590 messages as per the Settlement Calendar • SMO have stated that Market Trials will not be a preview of Market Behaviour • Market Trials are primarly geared towards the wholesale market • Retail Market Processes eg COS are not included in SMO plans 20

ESB Networks AIP Programme : 4. Market Trials…………………. . contd Exact details to be worked out with the SMO in their Market Trial Preparation phase, which SMO have advised that they have scheduled to run from 5 th March to 6 th July. This is our current understanding In the first Phase, • MRSO will be sending 8 ‘prefabricated’ 590 messages to SMO for every Unit , one message each week In the second Phase • SMO are looking for aggregations based on realistic data • we are planning to take a copy of the live database beforehand cutting over with the new Data Model including Supplier and Generator Units • This will be in a Market Trials test environment • we will follow the aggregation calendar set out by the SMO, aggregating daily and sending 590 messages to SMO • Our Market Trials test environment will not be updated with customer or meter movements, or NQH reads, but will have daily QH reads uploaded. The QH upload from Eir. Grid is to be confirmed with them. 21

ESB Networks AIP Programme : 4. Market Trials…………………. . contd Registration Information • Suppliers and Generators will be engaged in a registration process with the SMO • We will be looking to get Registration information as early as it is available from the SMO for Supplier Units, Participant Generator Units, Trading Sites etc. • We would like to get all the Non-Participant Generator Registration before the start of Market Trials • and that the Market Trials would be a test of the Retail cutover using real registration data. Also • Would appreciate if Suppliers could share with us now on a confidential basis how many Supplier Units they are planning to register , if more than one. 22

ESB Networks AIP Programme : 4. Market Trials…………………. . contd Key Question for Market Participants • For the second phase of Market Trials, Do any Retail Market Participants plan to send or receive Retail Market Messages • If yes, which messages • Can Retail Market Participants let us know by 15 th February - this is to allow us to plan for delivery and the technical environment 23

ESB Networks AIP Programme : 4. IPT - Timing - Initial Proposals Scripted Phase Mid July to Mid September Unscripted Phase PREP IPT Mid September to end October IPT has to end here Mid August 1 st week Sept Timing • IPT to be scheduled as late as possible to allow everyone to be ready - starts Mid August • IPT will be completed before the start of the second phase of Market Trials - ends First week in September Freeze on changes after IPT 24

ESB Networks AIP Programme : 4. Market Assurance/IPT - Initial Proposals The asssumptions are that • an IPT is needed • that IPT will be in accordance with the Assurance Strategy • the content of IPT will be relatively standard IPT tests • We are looking to confirm these assumptions and timings and asking Retail Market Participants for your comments , by February 15 th • and based on feedback, • will discuss with Gemserv and RMDS • and report back to the next IGG 25

ESB Networks AIP Programme : 4. Cutover • SEM go-live date is Thursday November 1 st • The SMO approach to cut-over is in the planning stages - no details available yet • The following is a provisional approach for Retail Market cutover, pending details from SMO and will confirm over later IGGs Would like to agree the high level proposals with the IGG so that we can plan on the basis proposed and proceed to document the proposals in greater detail We are asking Retail Market Participants for your comments , by February 15 th and in particular if you could let us know if you have any independent issues with the timing of cutover. 26

ESB Networks AIP Programme : 4. Cutover - Provisional Proposals Retail Market Assumption is that the IGG agree to a Retail Market Cutover the weekend before go-live Weekend before ie Sat 27 October , Sun 28 October: ESBN Cutover activities • we set-up Supplier Units, Trading Sites, Participant Generator Units, Export Arrangements for Non-Participant Generators, New Suppliers, New Generators • our conversion of SSACs to ‘A’ , effective from 1/11/2007, exception are PES MPRNs • we assign MPRNs to a default Supplier Unit - see later slide • we apply Schema changes and once all are happy that the schema changes have been successful, all* subsequent market messages can be used and will have the new formats - and including the 501 [Total count of Usage Factor field size change] and 504/504 s[Generator Unit field size changing from 4 to 9] Market Messages for settlement dates after the cutover weekend and up to and including 31/10/2007 - including the 341 message which will have Generator Unit field size changing from 4 to 9 * exception is 010 - see later slides Note A detailed hour by hour plan of the tasks over the cutover phase will be set out and documented at a later stage 27

ESB Networks AIP Programme : 4. Cutover - Provisional Proposals Monday 29 October [Bank Holiday] • ESBN issue a list of MPRNs with changes to Retail Market Participants for confirmation Thursday 1 November • New Aggregation messages will apply for Settlement days effective from now onwards • and 591, 595 messages will be sent to TSO [not SSA] 28

ESB Networks AIP Programme : 4. Cutover - Provisional Proposals Approach for Supplier Unit Values • Proposal is that we will agree with each Supplier a ‘default’ Supplier Unit into which we will move MPRNs and all WIP COS and New Registrations during the Cutover Weekend assign an effective from date of 1/11/2007 for the Supplier Unit. - exception is Trading Site Supplier Units which we will handle on an individual basis • Suppliers would then need to submit 015 for Change of Supplier Units before 1/11/2007, with an effective from date of 1/11/2007 if do not want the default Supplier Unit to apply at 1/11/2007. Note that from 1/11/2007 normal date dependant validations will resume which means that Supplier Units can only be changed in accordance with the timing and frequency set out in MPD 20 [Change of Supplier SSAC and/or Supplier Unit] Market Message Restrictions: In order to ensure a smooth transition from the old SSAC values to the new values ESB Networks request that the IGG agree to: • • Note: Not allow any 010 Market Messages between the Cutover Weekend and 1/11/2007 Not allow any 010 Market Message on or after 1/11/2007 with a Reading and a Required Date prior to 1/11/2007 In the exceptional circumstance when a Scheduled Read is taken early and this enacts the Change of Supplier , we want to agree with each Supplier a default SSAC which will be used for Settlement Days prior to 29 1/11/2007.

ESB Networks AIP Programme : 4. Cutover - Provisional Proposals COS, New Registration Scenarios: 1. A 1. 2. B 010 received prior to the Cutover Weekend and completes between the Cutover Weekend and 1/11/2007 • Any WIP COS or New Registrations that complete after the cutover and prior to 1/11/2007 with an effective date prior to 1/11/2007 may need manual intervention by MRSO, so can expect small delays for confirmation messages • to keep numbers low, we are asking Suppliers to submit a reading with COS in the days prior to the Cutover Weekend where possible • Once completed, WIP COS, New Registrations will default to an agreed Supplier Unit and if you want the Supplier Unit to change, Suppliers will need to send in an 015 before 1/11/2007, with an effective from date of 1/11/2007 if do not want the default Supplier Unit to apply at 1/11/2007. C 010 received prior to the Cutover Weekend and completes after 1/11/2007 • This will be processed as standard and Cutover programs will convert the data into the new industry data model with appropriate Supplier Unit and SSAC 010 received prior to and completes prior to the Cutover Weekend No issue with this: this will be processed as normal and Cutover programs will convert the data into the new industry data model with appropriate Supplier Unit and SSAC 30

ESB Networks AIP Programme : 4. Cutover - Provisional Proposals COS, New Registration Scenarios cont’d: 1. D • 010 received between the Cutover Weekend and 1/11/2007 request that the IGG agrees that 010 will not be submitted in this scenario 2. E • 010 received after Go-Live with a Requested Date prior to 1/11/2007 request that the IGG agrees that 010 will not be submitted in this scenario F 010 received after Go-Live with a Requested Date of 1/11/2007 but an ‘early’ Scheduled Read causes the Co. S to complete prior to 1/11/2007 • ESB Networks will agree a default SSAC per Supplier Unit with the Supplier and will update the data with the old SSAC for Settlement Days prior to 1/11/2007 and the new SSAC after 1/11/2007 31

ESB Networks AIP Programme : 4. Cutover - Provisional Proposals MPA Market Messages • All relevant outbound MPA (e. g. 101 P, 105, etc) Market Messages from ESB Networks issued after the Cutover Weekend will only ever contain the SSAC which was requested on the original 010, even if this is ‘out of date’. Note: All SSACs for an MPRN will have been defaulted to A, or remain at F, within the system, with an effective from date of 1/11/2007 The following table represents the data that should be supplied on an 010 Market Message and that which will be issued by ESB Networks: Inbound from Suppliers Scenario Supplier Unit SSAC Outbound from ESB Networks Supplier Unit SSAC A Old N/A Old B Old N/A Old Default Old C Old N/A Old Default Old* F Old New New* * This value is the value on the 010 Market Message and not the SSAC in place on the effective date of the COS 32

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 33

ESB Networks AIP Programme : 5 MCR 063 At the last IGG on December 14 th, we presented alternative proposals and asked for your responses. • Two Retail Market Participants responded • Both Respondents rejected the alternative proposal. The main points from the responses include: • In order to validate settlement liabilities calculated by MRSO and carry out shadow settlement for SEM, Suppliers must be able to replicate the aggregation calculation and must therefore have access to the basic data used by the MRSO for each aggregation run. • Since this request [MCR 063] was raised it has become apparent that with the introduction of the SEM this data is more necessary. • the number of daily aggregations for SEM increases the need for a rigorous audit trail to underpin the calculation of Suppliers' liabilities • What is required is a report of the input data used to deliver the aggregation output that is sent to the SMO. • Suppliers need this information so that they can; • replicate MRSO aggregation, • compare MPRN numbers and consumption (EUF/AUF) settlement configuration parameters against their own internal records • apply any adjustments they choose to the data, in order to estimate the gap between initial and final settlement values and hence their likely ultimate settlement liabilities for each Settlement day • monitor the level of estimated data used in calculation of their final settlement. 34

ESB Networks AIP Programme : 5 Validation of Aggregation - QH Export Response to Requirement of Suppliers to Validate Aggregations: QH Export - the view is that there are no specific issues with validation and aggregation for QH Export because data is available by individual Generator Unit / Export Arrangement 35

ESB Networks AIP Programme : 5 Validation of Aggregation - QH Import Response to Requirement of Suppliers to Validate Aggregations - QH Import Every change that is made to the MRSO database is advised to Suppliers • There are individual market messages for all changes to master data eg. DUo. S Group, MCC , DLF • 341 QH Read messages are sent daily Therefore Suppliers have the information to validate data and carry out an independent aggregation if they choose to do so. Note if Suppliers want to do their own indicative aggregation then this would need to be discussed as the IGG has already decided that the 341 messages for estimates for indicative are not required 36

ESB Networks AIP Programme : 5 Validation of Aggregation - QH Import Response to Requirement of Suppliers to Validate Aggregations - QH Import In addition, to Support Suppliers requirements the following are proposed for discussion 1. Amend the daily 595 message to include the following • count of MPRN by DLF • % count of all MPRNs that have been estimated , per Supplier Unit/SSAC • % of consumption that is actual , per Supplier Unit/SSAC This supports Suppliers who choose to carry out their own independent checks for QH sites with • a daily verification of the count of MPRNs • visibility of the count of MPRNs that are actual/estimated • visibility of the consumption that is actual/estimated 2. MRSO to provide on request an extract of all of the QH MPRNs that have been included in a specific aggregation run, along with the Supplier Unit, SSAC, DLF that was used in the aggregation • This supports an independent verification by Suppliers of a particular aggregation 3. MRSO to provide on request an extract of all of the QH MPRNs that were included in a specific aggregation and our records at that point in time of the DG, MCC for each MPRN. This report should ideally be timed to run after the specific aggregation. • This supports an independent verification by Suppliers of the database for aggregation and other billing records 37

ESB Networks AIP Programme : 5 Validation of Aggregation - NQH Import Response to Requirement of Suppliers to Validate Aggregations - NQH Import Every change that is made to the MRSO database is advised to Suppliers • There are individual market messages for all changes to master data eg. DUo. S Group, MCC , Load Factors for MDs, Standard Load Profile, DLF • Every change to Usage factors is sent to Suppliers, including effective date, and by time of use, and whether actual or estimated • Profile co-efficients are made available annually • The relationship between the Duos Group, Meter Configuration Code, Load Factors for MDs, and data aggregation profiles is set out in the document ‘Meter Configuration Code Guidance Notes’ Therefore Suppliers have the information to validate data and carry out an independent aggregation if they choose to do so. 38

ESB Networks AIP Programme : 5 Validation of Aggregation - NQH Import Response to Requirement of Suppliers to Validate Aggregations - NQH Import In addition the new 591 messages will have, for each aggregation, For each DLF/Standard Load profile combination • Count of MPRNs • Total Usage Factor by Time of Use This supports Suppliers who choose to carry out their own independent checks on • a daily verification of the count of MPRNs • verification of the total usage factors used in that aggregation In addition, • by applying the total usage factors to the profile coefficients , Suppliers can if they choose to, verify the consumption that has been calculated in that aggregation 39

ESB Networks AIP Programme : 5 Validation of Aggregation - NQH Import Response to Requirement of Suppliers to Validate Aggregations - NQH Import In addition, to support Suppliers requirements, the following are proposed for discussion 1. MRSO to provide on request an extract of all of the NQH MPRNs that have been included in a specific aggregation run, along with the Supplier Unit, SSAC, DLF, Usage Factor by Time of Use, Load Profile that was used in the aggregation • This supports an independent verification by Suppliers of a particular aggregation 2. MRSO to provide on request an extract of all of the NQH MPRNs that were included in a specific aggregation and our records at that point in time of the DG, MCC, Load factor [if MD] , Usage factor and Load profile applying per time of use and whether actual or estimated, for each MPRN that was included in a specific aggregation. This report should ideally be timed to run after the specific aggregation. • This supports an independent verification by Suppliers of the database for aggregation and other billing records Note : Regarding monitoring the level of estimated data used in calculation of final settlement - these requirements will be considered as part of the overall debate on Consumption Adjustments and we will revert later with proposals 40

ESB Networks AIP Programme : 5 Validation of Aggregation Notes on Ad-Hoc requests for Extracts • these would need to be scheduled to run at a time that is not in conflict with the live production schedule • Output format will not be new messages • Because of the costs involved, the frequency and costs of producing the reports would need to be discussed as an MRSO item at future IGGs 41

ESB Networks AIP Programme : 5 Validation of Aggregation • We are looking for comments on these proposals • In the short term, we propose that next week we will issue a new MCR for the changes to the 595 message • and asking Retail Market Participants for your comments , by February 15 th 42

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 43

ESB Networks AIP Programme : 6. Next Steps § We are continuing with the build based on the MCRs. § Looking from responses from Market Participants to items raised today by Thursday 15 th February § outstanding items will be reviewed at the next IGG • At the next IGG , we will be updating you on • Market Trials • Market Assurance / IPT • Cut-over 44

ESB Networks AIP Programme : Agenda 1. Review of where we are 2. Issues - Update 3. MCRs - MCR 123 ver 1. 2 and proposed sundry changes 4. Market Trials, Market Assurance, Cutover 5. MCR 063 / Validation of Aggregation 6. Next Steps 7. TAG Implications 45

ESB Networks AIP Programme : 7. • TAG Implications Version 6. 0 of the XML schema is currently in Unit Test. This is baselined in line with the agreed MCRs proposed for SEM, with one additional code being added for Vulnerable Customer Delivery. · Provisional dates for the release of the XML Schema to Retail Market Participants: A A provisional XML schema is planned to be available in mid-February · This will consist of individual message structures with associated documentation · In particular, any changes to 595 market messages arising from todays earlier discussion will not be incorporated. · Sample xml can be provided if requested. B A formal release of the XML schema will be released April 16 th · This will be subject to change control and further testing. 46

ESB Networks AIP Programme : 7. TAG Implications……………. . contd • The IPT phase is proposed for August/September • Assuming no change to the schema release on the 16 th April this version will be used for IPT • If further changes are approved a further release will be issued before IPT commences. 47

ESB Networks AIP Programme : Thank You 48