1. IGG Agenda – 30th October 2008
Minutes from last IGG meeting
Review of Action Items
CER Update
Gemserv update
Market Operations Update
Retail Market Design Service Update
Market Design Update
Next Steps 1

2. Minutes from IGG meeting – 18th September 2008

3. IGG Action Items Closed IGG Actions IGG Actions carried forward:
Updated IGG Action List issued in advance of meeting
11 Actions closed since last IGG meeting:
IGG Actions carried forward:
Owner
Sept 18th
Oct 30th
Suppliers 2 4
RMDS 15 19
MRSO 1 3
ESBN
CER 5
Total 23 34 3

4. CER Update 4

5. Gemserv Update 5

6. Market Operations Update6

7. Market Issues Log New Issue No. 157
Where there is a change of DUoS group on an 013 message and if the last billed date for the site is the current date, the 114 message reflects the old DG.
Defect will be fixed post software freeze 7

8. Retail Market Design Service Update
Conor Garrigan, RMDS 8

9. RMDS Update
Agenda
Conference Calls
Eligible Customer List 9

10. RMDS Update Conference Calls
No supplier input for the past two Conference Calls
Propose to have one Conference Call – mid IGG cycle 10

11. RMDS Update Eligible Customer List (MP Extranet)
Updated on a monthly basis since implementation in February 2007
Some recent monthly updates have been delayed due to outages of the Central Market Systems
Can monthly update be extended to two-monthly update? 11

12. Discussion Requests & Market Change Requests
Conor Garrigan, RMDS 12

13. Market Change Request MCR 0169 – Additional of Vulnerable
Customer data deletion flag on 102mm
Circulated to the market in early October
No Feedback
Approval requested 13

14. Market Change Request
MCR Recalculation of Consumption Estimates
Version 3.0 circulated
Approval Requested 14

15. Code Change Request
CCR new code values to join the existing Meter Category codes.
Previously approved
Error on the Default Register Group for RM103 and RM105
Now Corrected
Approval requested for amended CCR 15

16. Discussion Request DR 0161 – New MP Extranet Web Service
Circulated to the market early October
Any feedback
Approval to progress to MCR 16

17. Discussion Request
DR 0117 – Proposal to add acceptance, completion and cancellation message to the Market Design
Present overview of DR at IGG
DR will be released for review after IGG 17

18. Purpose of DR
Provide codified works detail and statuses on message to supplier where possible
Reduce the number of s being sent by clerical officers to suppliers
Streamline the works business process for notification between Networks and Market Participants.
Provide works status on revenue protection orders. 18

19. Proposed Design
Create a new market message to be known as the 131 message
Change to Networks works completion process
Change to Works Cancellation process
The 131 message within the Revenue Protection Process. 19

20. 131 Message The 131 will be sent:
At various points in the NPA and Non NPA de-energisations, re-energisations, meter works and revenue protection processes
Only supplier requested works (the exception to this being revenue protection where 131 is sent for both supplier requested and networks requested works)
When work requested was not completed but call is FINId
When a call is cancelled by supplier request
The 131 will not be sent:
To acknowledge receipt of supplier works requests
When supplier works completes successfully (the exception to this being revenue protection where the 131 will always be sent for FINId status)
The 131 could be sent
For rescheduled calls. 20

21. Works completion process
Calls which will have a subsequent visit made are set at RESCHEDULED
All calls which are completed and do not require rescheduling, will be FINISHED. There are 2 outcomes to a call being FINISHED:
Successfully completed as requested and
Not completed as requested.
Each of the FINISHED, RESCHEDULED or CANCELLED statuses will be supplemented with a reason code to provide more detail on the reason for the status 21

22. Cancellation process Existing Process
If works can not be completed at a site and no subsequent visit is to be made, the call is set to RESCHEDULED.
The NT then contacts the ESB Networks clerical officer to request contact be made with the supplier to request cancellation of the order.
The clerical officer s a supplier representative
The supplier sends a withdrawal message to cancel the call
The message is received by ESB Networks and processed by workflow
The workflow outsorts the request and the clerical officer manually cancels the call and completes the workflow.
Proposed Process
All calls which were previously set as RESCHEDULED and required supplier cancellations will be FINISHED and supplier will be notified on 131 message. An outcome reason will also be displayed on the 131 message explaining why the call was finished. 22

23. Revenue Protection Process
The 131 message will be used to notify suppliers of revenue protection call completion.
Overcomes issue of no supplier notification for RP calls which are created by circumstances other than the 260 message.
The 131 message will not supply all supplementary information currently sent to supplier for a RP call. The existing processes for supplying this information will remain. 23

24. Main Changes to DR Message Title change
The 131 is not used in special read process as significant value for inclusion could not be identified. If there is a business case from any MP to include, it can be discussed and proposed for inclusion.
The 131 will not issue to notify of successful completion of a works order. The standard confirmation message will serve to indicate of works completion. The implementation of the mobile solution has made this feasible due to same day completion.
The 131 is going to be used to notify of all revenue protection completions, cancellations and possibly rescheduling. Previously revenue protection was not included.
A change to the ESB Networks order completion process has been proposed. This would involve all calls which are not rescheduled or cancelled being finished. Additional reason codes will be added to the system to explain the detail of a finished call (success or non success etc)
The completion process change results in the current cancellation process becoming redundant. 24

25. SoLR Working Practice 17
How long should a customer be allowed to query the SoLR changeover reading, 6 months, 10 months?
How are the SoLR costs to be recovered for both the SoLR and Alternate Suppliers?
Can WP 17 be approved? 25

26. Release Planning - Outstanding MCRs
MCR Number
MCR Description
MCR 0033
Sending 306 for all NQH De-energisations
MCR 0034
Sending 307 for all NQH Re-energisations
MCR 0060
New Message to contain customer details on conversion from NQH to QH 1.1
MCR 0062
New rules for MPD 1 - CoS
MCR 0069
Irish language character set
MCR 0078
Add Validation to use of Registered Company Number
MCR 0080
Remove Meter Point Status Field from 017Message
MCR 0081
Suppliers Extranet shows Non billable devices where installed
MCR 0086
Text To be added to MPD14 to cater for Standard Profile Changes
MCR 0087
Exchanged Meter Ref amendment to provide only for like for like exchanges
MCR 0126
Rejection of change of usage requests DG5 to 1 or 2 where MIC is greater than 30 v1.0
MCR 0127
Decouple Connection Agreement and CoS where no COLE (refer to MCR 0161)
MCR 0130
Extra validation check required at creation of 306 and 307 messages v2.0
MCR 0152
Vulnerable Customers - Phase 3
MCR 0154
Versioning of 341 message
MCR 0157
Proposal to add Acceptance / Completion / Cancellation message to Meter Works Design
(Impose 20 day time limit on replacement of CoS reads) 26

27. Release Planning - Outstanding MCRs
MCR Number
MCR Description
MCR 0161
Increasing the threshold for connection agreements in CoS process (more comprehensive solution than MCR 0127)
MCR 0162
SoLR process
MCR 0164
Including the Meter Multiplier on the Extranet
MCR 0166
Addition of generator ID and export arrangement ID to Extranet
MCR 0168
Addition of 331MM to notify of QH meter removal during QH de-energisation with meter removal process
MCR 0169
Addition of Vulnerable Customer data deletion flag on 102
MCR Number MCR Description 27

28. Next Steps Proposed Diary dates for IGG meetings in 2008/2009:
Proposed dates are on Calendar of Events on RMDS website 28

29. Next Steps Propose to continue with conference call every three weeks:
(subject to agreement)
Call details have new contingency PIN No:
Number: PIN :
Contingency number remains: New PIN: 80490 29

30. Thank You 30