1 / 35

IGG Agenda – 18 th September 2008

Minutes from last IGG meeting 10.30 - 10.40 Review of Action Items 10.40 - 10.50 CER Update 10.50 – 11.05 Gemserv update 11.05 – 11.15 Market Operations Update 11.15 – 11.25 Address Data Standards Update 11.25 - 11.40

yagil
Télécharger la présentation

IGG Agenda – 18 th September 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Minutes Minutes from IGG meeting – 14th August 2008 2

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

  4. CER Update 4

  5. Gemserv Update 5

  6. Market Operations Update 6

  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 email 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 Engineering Officer Management Company Planning Authority ESB Networks Developer Developers Agreement Supply Agreement Connection Agreement Wiring Cert Management Agreement Customer Supplier Electricity Bill Address Setup Legal Documents 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 DR 0157 - Addition of Vulnerable Customer data deletion flag on 102V.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 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 Completing Design Completing Design For TUoS New market rule Irish Language Act Reduce residual CA on CoS issue Completing Design Better mkt function Speed up response Automation Better mkt function Better mkt function Better mkt function 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 Number MCR Description MCR Number MCR Description 32

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

  34. Next Steps • Propose to continue with conference call every two weeks: 02.10.08 16.10.08 • Call details have new contingency PIN No: • Number: 01-6647602 PIN : 77640 • Contingency number remains: 01-6647777 New PIN: 80490 34

  35. Thank You 35

More Related