IGG Agenda 4 th April 2012

1. IGG Agenda 4th April 2012

2. Minutes Minutes from IGG meeting 22nd February 2012 For approval today.

3. IGG Action Items Updated IGG Action List issued in advance of meeting • Actions closed since last IGG meeting: 5 • IGG Actions carried forward: 8

4. IGG Actions Carried Forward

5. LTNA Sites and supplier liability for DUoS charges • Option of reducing MIC proposed as means of reducing liability • Changes to Connection Agreement require written agreement of both parties • Provision for using Variations Clause subject to direction from CER • ESBN process will include • Writing to customer advising of reduced nominal MIC • MIC can be restored on request at no cost to customer • On restoration, customer liable for full DUoS arrears as ESBN reserved capacity at connection point

6. LTNA Sites and supplier liability for DUoS charges Other issues • DG5 customers don’t incur DUoS capacity charges and unaffected by MIC changes • Option only available at DG6 and higher • Option limited to cases where disconnection is not practical or cost of disconnection exceeds a threshold level • Rule set required for situations where the process applies since any costs are ultimately carried by UoS customer Next step is to discuss with Gaslink and develop proposals for consideration by CER

7. CER Update Industry Governance Group 4th April 2012

8. PrePayPower presentation to IGG CoS Loss process

9. Scope Change of Supplier Loss where PrePayPower has gained a customer under standard market processes Does not cover ‘Hardship’ meters where ESBN have installed the prepayment meter This is governed by WP19

10. Principles PrePayPower processes based upon facilitating seamless transfer for the customer within the standard market processes The meter is put into credit mode to ensure that the customer supply is not impacted. A reconciliation is done with for each customer Credit on the meter can be refunded Any charges outstanding can be billed

11. Detail MM110 received from MRSO Customer is contacted to confirm that they wish to transfer Customer is given a code to put the meter into credit mode – ‘ZZCode’

12. Confirmation of Loss MM105L arrives to confirm loss MM310 arrives confirming the read A reconciliation is carried out of the customer usage versus top ups

13. Issues with CoS Loss The major issue that we have experienced is where our customer has contacted a new supplier to be told that they cannot move onto their supply as there is a prepayment meter in place As you can see from previous slides CoS can proceed under normal market processes Our customer services is available at 0818 233 331 to deal with specific customer queries

15. Retail Market Assurance Services for the Irish Electricity Market Peter Varley IGG 4th April 2012 peter.varley@gemserv.com

16. Assurance Activity Update Business As Usual (RMDS) Assurance Process Document Final Review comments received and updates applied Document recently sent to RMDS for second review Enquiry from one organisation that may wish to become a Self-Supplier

17. Assurance Activity Update Harmonisation (HRDS) Workshop held with HRDS and ESBN (13/03/2012) Early draft Assurance Approach circulated (13/03/2012) Feedback received from one party and changes made First cut analysis of IPTs completed and included High and medium impact only Some low impact will be included in detail of IPTs e.g. longer e-mail Grouping will be used to reduce the number of scenarios each organisation will be expected to carry out Small suppliers expected to participate Approach for discussion and approval today

18. Questions & Discussion

19. MRSO UpdateGerry Halligan 04 April 2012

20. 105L Market Messages

22. COS In Progress 02/04/2012 – 8,225 • Reviewed Monthly • Suppliers notified of individual switches outstanding and reason • Switch outstanding for Energisation or Token Meter Removal will not time-out • Contact Customer or submit cancellation • 58 Switches held due to an existing Open Service Order

23. COS and CoLE

25. Debt Flagging

28. Objections – Erroneous Transfers

29. Objections

30. COS & Installation of a Prepayment Meter IGG 04/04/12

31. Purpose • Purpose of these slides is to clarify the process for how concurrent requests for prepayment installation and COS are handled

32. COS & Installation • It is possible for a COS request to complete while a prepayment meter installation request is underway. • Very rare • Impact of Debt flagging • Timing of Requests • Supplier requesting prepayment installation would be aware of existence of a 110MM • End result could be discrepancy between market systems and Liberty Client. • Customer with old supplier in Liberty Client but new supplier in market systems.

33. Process • If a COS is underway when Request for Install received: • Request for Install will be not be processed • Requesting Supplier will be advised • COS proceeds as normal

34. Process • If COS commences subsequent to a Request for Installation: • Prepayment installation will proceed • COS will proceed • Given the customer category, highly likely to be debt flagged and result in cancellation • Gaining Supplier will be notified by KMS of prepayment installation • Gaining Supplier can then either: • Retain customer (instruct KMS to initiate COS in Liberty Client), or • Cancel COS

35. Process • What happens is no action is taken? • Customer will continue to top up using their previous Supplier’s account/card • Customer will be registered to gaining Supplier in market systems • Resolution? • Cancellation of COS at this point by gaining Supplier will result in reconciliation in market systems • Gaining Supplier can then re-request COS (including KMS request)

36. ROI HSP Project Update Conor Garrigan

37. HSP Agenda Items • Project Plan Update • Design Clarifications • MP Planning Workshop (17th April)

38. High Level Schedule

39. ROI HSP Design Clarification Recipient ID in Message must match the physical Message recipient

40. Recipient ID in Message must match the physical Message recipient Background Message routing in the new Tibco-based environment will require that the message contains information to identify the final physical recipient of the message. There are two scenarios in the current Market design where the RecipientID in the message header is not the final physical recipient viz 341/342 Messages that are sent to TSO and 342/594/597 Participant Generator Messages that are sent to a nominated Supplier under WP12. Impact • 341/342 Messages that are sent to TSO: these will now carry a RecipientID of TSO (this used to contain the Registered Supplier / Generator’s identifier) • 342/594/597 Participant Generator Messages that are sent to a Supplier under WP12: these will now carry a RecipientID of the nominated Supplier (this used to contain the Generator’s identifier). These changes are illustrated overleaf Note: No other scenarios or messages are impacted.

41. Recipient ID in Message must match the physical Message recipient

42. MP Planning Workshop 17th April (Merrion Square Offices) • Objective • Allow MPs to assess the business and technical impact of the HSP rollout, and • Kick-start the planning for their own implementation project • Scope / Agenda • HBL overview and review of new summary impact quick reference • Overview of EMMA technical architecture, minimum server spec and configuration options • ROI WebForms demo • Harmonised schema release • Overview of MPs support and communications plans • Next Steps for MPs • Nominate management and technical contacts to attend. Note: this is the only scheduled MP planning workshop by the HSP Project

43. RMDS Update Retail Market Design Update Aileen O’Connor, RMDS 4th April 2012

44. Post-Harmonisation MDU Planning • Active List Validation • Phased validation of the Active List in preparation for the 1st Harmonised Market Release in June 2013 has now commenced • The Active List was circulated on 14th February 2012 for consideration • List contents now need to be validated by the Market, and subset of 7 MCRs from the Active List was presented at HWG today of which : • All MCRs were previously approved at IGG • Five MCRs have been re-versioned. • Today’s IGG Workload • Approval Requested for updated version of MCRs 87 & 1033 • Feedback from MPs Requested – MCR 130

45. Previously Approved MCR for Approval • Classified as ROI Specific at HWG meeting today • Requested at Today’s IGG Meeting: Feedback/Approval for V2.0 • IMPORTANT NOTE: • The 331/332 messages that include the Exchange Meter Reference Number were always intended to have a dual role, that is, to carry details of both physical (actual meter swops) and logical (metering reconfiguration) changes at the metered site • To change this arrangement as proposed in this MCR would be a fundamental change to this part of the market design and possibly was not the intent of the original MCR • If suppliers are interested in isolating physical meter exchanges (which appears to have been the main driver behind the MCR), then they can do so by examining a combination of “Meter Cat + Meter Serial No” on old and new meters which will identify this type of change.

46. Previously Approved MCR for Approval • V2.0 approved on 26/10/2010 • V3.0 created to amalgamate two requests for population of the Market Participant Business Reference as follows: • MCR 1033 – on MM300 with CoLE read & on any associated MM300W • DR 1076 – on MM 300S with special read requested on incoming MM252 • At today’s Meeting • Approval requested for V3.0

47. Previously Approved MCR for Feedback • Classified as ROI Specific at HWG today • Background: • Approved at IGG on 18/10/2007 • ESB Networks has confirmed that incidences of this are very rare. • Only occurs if NT removes meter from a site on an incorrect order type e.g. O/H Service Alteration. This will issue MM332 with Meter Point Status E. • Requested at Today’s Meeting: • Information from Suppliers regarding the scale of this issue to determine if MCR is still required by Market to be retained on Active List for future implementation.

48. Notification of Removal of Previously Approved MCR from Active List • Background: • MCR was developed to agree a new (initially automated but then manual) solution to enable a Supplier who is registering the export arrangement for a particular non participant generator to request the receipt of the meter details relating to the MPRN via a 331 message, either by: • Completing Form 2, to be included in Working Practice 14, at the initial registration of the Supplier to the non-participant Generator • Requesting via email • MCR 173, with updated WP 14, was approved at Conference Call of 01.04.2010 and implemented by MRSO. However, it remained on the Active List of MCRs. • MCR has now been removed from the Active List

49. MCR 1085 - Change to MPD 29 - Grouped CoS • Market Change Request • Approved as DR at IGG meeting of 22.02.2012 • Now presented as MCR with no changes • At today’s Meeting • For Approval

50. Market System Outages • Changes have occurred in Customer/Supplier behaviour, particularly over last 3 yrs. • Increased Volume of messages • Pattern of message flow – more batches • More change on Supplier Systems • Currently process in place for Market System Outage Notification only. • Requirement for Procedure to be documented for both Supplier & ESBN Scheduled & Unscheduled Outages. • Review has been initiated with IT/ESBN to document procedures to incorporate Tibco arrangements. • Supplier suggestions/feedback is requested to aid development of appropriate process.