1. IGG Agenda – 18th September 2008
Minutes from last IGG meeting
Review of Action Items
CER Update – 11.05
Gemserv update – 11.15
Market Operations Update – 11.25
Address Data Standards Update
Retail Market Design Service Update
Market Design Update
Next Steps – 1

2. Minutes from IGG meeting – 14th August 2008

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

4. CER Update 4

5. Gemserv Update 5

6. Market Operations Update6

7. Retail Market Design Service Update
C. Madden, RMDS 7

8. RMDS Update Agenda Recalculation of Estimates
Updating of Site Addresses 8

9. RMDS Update Recalculation of Estimates
The changes to SAP to provide for Change Request CR221 were released to Production on September 16th.
An was released outlining the details of the functionality delivered and/or deferred items 9

10. ESB Networks – Amending Site Address
Historically (June 2008) all address changes were accepted. This has led to:
Duplicate addresses
The Meter Reader unable to find a meter at a site address
Acceptance of amended site addresses is now strictly controlled by the Bureau
The following are some of the procedures used for verifying the site address:
Find out if the site address already exists
Is the site a one off or part of a development
Research the address (New Connections)
Determine if outside verification is required (Planning Authority)
Carry out a site visit
Access to main switching Board (Management Company)
Access to the Customers premises (Customers Electrician)
Is the address Commercial or Domestic 10

11. Supplier Impacts
As a result of the new procedures the following has happened:
Rejection rates have increased considerably
Suppliers don’t know why their addresses are being rejected as there are not enough Reject Reason codes
Multiple requests to amend the same site have been received
Multi metering sites and Housing Estates are most problematic 11

12. Address Amendment Examples
This example reflects no address change, but still accepted and entered by the supplier. 12

13. Address Amendment Examples
This address was rejected as there is already a unit six existing at the same address 13

14. Address Amendment Examples
This example illustrates the varying spelling differences between supplier requests and what is in the Regional Structure. 14

15. Address Amendment Examples
This was rejected as there is already a no 1 in the system 15

16. Address Amendment Examples
This example shows a second request to alter addresses as the original change was made on the 7/7/08. How often do we change the same address. 16

17. Site Address Interactions / Dependencies
Management Company
Engineering Officer
Developer
Address
Setup
Legal
Documents
Management Agreement
Supplier
Wiring Cert
Planning Authority
Developers Agreement
Supply Agreement
Customer
Connection Agreement
ESB
Networks
Electricity Bill
Wiring Cert address has to match exactly the Connection Agreement address
Bank 17

18. Address Bureau Concerns
Developers are looking to change addresses after they have been agreed with the Planning Authority and after customers have moved in.
There is nothing to stop the Developer from making address change requests.
Huge cost in readdressing a whole development.
Planning authorities are not being consulted about the Developer address changes.
ESB Networks now have concerns over the legality of documentation. 18

19. Discussion Requests & Market Change Requests
Cormac Madden, RMDS 19

20. Discussion Request Discussed at the August 28th Conference call.
DR Addition of Vulnerable Customer data deletion flag on 102 V.2
Discussed at the August 28th Conference call.
All were in favour of the flag being included on the 102 message
All agreed that medical institution could be added.
It was agreed that there was no need to display the delete flag on the 102P.
Approval to progress to MCR 20

21. Market Change Request
MCR 0080 – Remove Meter Point Status Field from 017 Message
Dates back to early 2006
Approved but not Implemented
Not on Current Outstanding List
Should this MCR be included on the MCR prioritisation list? 21

22. Market Change Request MCR 0165 – Recalculation of Estimates
Released Tuesday 16th September at 14h00.
Release note issued
Design is somewhat different to MCR
Amendments to MCR will be proposed
Recalculation due to meter removal readings is not yet operational. A supplementary release is planned. 22

23. Discussion Request MCR 0167 - Delivery of 106d message to EirGrid
Approval requested 23

24. Discussion Request Circulated to the market Approval Requested
MCR 0168 – Addition of 331MM to notify of QH meter removal during QH de-energisation with meter removal process
Circulated to the market
Approval Requested 24

25. SoLR Working Practice 17 Purpose of Working Practice 17
Provide Alternate Suppliers with an opportunity to acquire the Defaulting Supplier’s Customers
Provide a clear mechanism by which ESB Networks MRSO and MO can hand over clean data to the SoLR at the end of day 19 (5 day communication period + 14 day CoS period).
Provide guidelines on how to handle the following scenarios:
Present Reading < Previous Reading
Large Debits 25

26. SoLR Working Practice 17 26

27. SoLR Working Practice 17 27

28. SoLR Working Practice 17 28

29. SoLR Working Practice 17 Issues
How does the SoLR and Alternate Suppliers recover SoLR costs
A customer cannot query an SoLR reading 10 months after the SoLR Direction date
How does the SoLR / Alternate Supplier identify SoLR readings 29

30. Action 367: MPRN/Name & Address Web Service
Investigated using existing web service for this purpose.
Finding: a new web service is required. Reasons:
Existing web service is not designed for CoS volume
Modification to information content required
RMDS will develop a DR for a new web service 30

31. 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 0081
Suppliers Extranet shows Non billable devices where installed
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
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
Completing Design
For TUoS
New market rule
Irish Language Act
Reduce residual CA on CoS issue
Better mkt function
Speed up response
Automation
Automation + better function
(Impose 20 day time limit on replacement of CoS reads) 31

32. Release Planning - Outstanding MCRs
MCR Number MCR Description
MCR Number
MCR Description
MCR 0161
Increasing the threshold for connection agreements in CoS process
MCR 0162
SoLR process
MCR 0163
Increase in tolerance levels for NQH Meter Reading Validation 32

33. Next Steps Proposed Diary dates for IGG meetings in 2008: 30.10.2008
Proposed dates are on Calendar of Events on RMDS website 33

34. Next Steps Propose to continue with conference call every two weeks:
Call details have new contingency PIN No:
Number: PIN :
Contingency number remains: New PIN: 80490 34

35. Thank You 35