1 / 35

IGG Agenda – February 1st 2007

Minutes from last IGG meeting 10.00 – 10.10 Review of Action Items 10.10 – 10.20 CER Update 10.20 – 10.30 Gemserv Update 10.30 – 10.40 Market Operations Update 10.40 – 11.00 Networks SEM Update 11.00 – 12.30 Retail Market Design Service Update 12.30 – 12.40

yoshi-mcfarland
Download Presentation

IGG Agenda – February 1st 2007

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.00 – 10.10 Review of Action Items 10.10 – 10.20 CER Update 10.20 – 10.30 Gemserv Update 10.30 – 10.40 Market Operations Update 10.40 – 11.00 Networks SEM Update11.00 – 12.30 Retail Market Design Service Update 12.30 – 12.40 Market Design Update 12.40– 12.50 Discussion Requests & Market Change Requests Next Steps 12.50 - 13.00 IGG Agenda – February 1st 2007 1

  2. Minutes • Minutes from IGG meeting – December 14th 2006 2

  3. Action Items • Actions Addressed in Advance of Meeting • Update on Action Items • Actions to be covered during remainder of presentation • Actions to be carried forward • Other Action Items 3

  4. Update on Action Items • Action Item 4– Review possibility of creating and providing dedicated MPRN data for use in all IPT tests • ESB Networks ISC have agreed to this in principle • Draft proposal to issue from RMDS to ESB Networks ISC 4

  5. Update on Action Items • Action Item 8 – Provide update on date for data provision • MCR 0083 refers • Customer Data DG 3 and higher will be available online in CSV format to download. • 2 separate files: MPRN (File 1) and Meter details (file 2) • Expected to go live week beginning 19th February 5

  6. Update on Action Items • Action Item 9 – RMDS to investigate the procedural issue whereby a duplicate MPRN is generated when a quotation is ‘rolled back’ • In the early months post go-live, a bug was discovered in the New Connections process whereby a duplicate MPRN was generated when a new quotation superceded an old quotation (‘rolled back’) for the same physical site • The defect was fixed and no further duplicate MPRNs were detected from the New Connections process • The broader issue of Working Practice 13 will be covered later in the presentation 6

  7. Update on Action Items • Action Item 20– RMDS Draft Business Plan 2007 • Issued to MPs on the 5th January • To be discussed later in presentation 7

  8. Actions to be covered during remainder of presentation • Action Item 3– Review Objections and Cancellations process • Numbers with CER for Review • CER Update 8

  9. Actions to be covered during remainder of presentation • Action Item 5 – Review note detailing the difficulties surrounding suppression of withdrawal of CoS reads • E-mail issued 3rd October • No feedback received • Request from one MP that this item should be left open until a decision has been reached by CER • CER Update 9

  10. Actions to be covered during remainder of presentation • Action Item 10 –Update DR 0123 – Versioning of 341 message to include a table indicating how versioning will work • DR 0123 has been updated, not yet circulated to MPs • Proposed versioning table covered later in the presentation 10

  11. Action Items to be carried forward • Action Item 6 – Investigate whether new 131 message could be issued for Special Read Request • DR 0117 has been updated and will issue to MPs in the next week 11

  12. Action Items to be carried forward • Action Item 7– Update MCC Guidance document • Document in Final Review Stage 12

  13. Action Items to be carried forward • Action Item 13– Prepare proposals on addresses in the Retail Market • Document in Final Review Stage 13

  14. Action Items to be carried forward • Action Item 11– Issue revised DR103- Vulnerable Customers • Version 6.0 to issue following feedback 14

  15. Actions to be covered during remainder of presentation • Action Item 18 – Request Market Participants to review alternative proposal for MCR 0063 as outlined in the SEM slide presentation at the last IGG • Covered in SEM presentation 15

  16. CER Update 16

  17. Gemserv Update 17

  18. Market Operations Update 18

  19. Retail Electricity Market Issues Update Susan Morrissey, RMDS 19

  20. Retail Electricity Market Issues Log • Log continuing to issue on a weekly basis • Summary Statistics (as per last release –31-01-2007) • Total Number of Issues Logged 138 • Total ‘Closed’ 126 • Total ‘In Progress’ 8 • Total ‘Being Monitored’ 1 • Total ‘Logged’ 3 • Issues Resulting in DRRs 9 • Total Raised Since Last Issue 0 • Total Closed Since Last Issue 0 20

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

  22. Retail Market Design Service Update • ESB Working days 2007/2008 issued on 5th January 2007 • Draft Business Plan issued on 5th January 2007 • Supplier Support Arrangements for 2007 issued on the 17th January 2007 22

  23. Retail Market Design Service Update • Working Practice 13 – Termination of Duplicate MPRNs • Issues raised by one supplier: • ESB Networks Users are allowed to create duplicate mprns • So far no case of duplicate MPRNs has been detected for MPRNs created after go-live of the central market system in January 2005. • The cases of duplicate MPRNs so far detected and analysed relate to MPRNs created in the legacy systems prior to this. ESB Networks previously had a number of legacy systems linked by multiple interfaces allowing the creation of duplicate MPRNs due to poor cross-validation. • It is important to note that the New Connections process as designed and implemented for SAP blocks the generation of a second MPRN for any connection point within the quotation accepted by the customer. 23

  24. Retail Market Design Service Update • Working Practice 13 – Termination of Duplicate MPRNs (contd) • Issues raised by one supplier: 2. ESB Networks Users are allowed create duplicate quotations for one site address at New Connection • The current New Connections process allows creation of multiple quotations for any site address. This facilitates customers changing their minds or this facilitates different parties applying for a new connection at the same one-off site. However once one of the offers is accepted, this changes the status of the MPRN in this offer to 'Assigned' , making only this MPRN available for registration for suppliers on the MP Extranet. • While almost unheard of, it is theoretically possible for two offers be accepted and paid for through a customer error, this will be detected by the ESBN engineering officer long before the connection is built when s/he visits the site to design the connection. 24

  25. Retail Market Design Service Update • Working Practice 13 – Termination of Duplicate MPRNs (contd) • Issues raised by one supplier: 3. Market systems allow mprn specific meter reads be allocated to multiple mprns • Analysis of the duplicate MPRNs contradicts this perception. Reading validations apply to all meter readings received in ESB Networks systems. The meter reader must input either a valid meter reading or trigger the generation of an estimate for each MPRN via the handheld device. Analysis of duplicate MPRNs thus far indicates that actual readings are obtained for the first MPRN and estimate readings have been generated for the second MPRN. 25

  26. Retail Market Design Service Update • Working Practice 13 – Termination of Duplicate MPRNs (contd) • Issues raised by one supplier: 4.Meter Readers do not recognise that there is an issue with duplicate mprns when entering reads • Meter Readers will normally report duplicate MPRNs to the back office 26

  27. Retail Market Design Service Update • Working Practice 13 – Termination of Duplicate MPRNs (contd) • Issues raised by one supplier: 5.A simple validation would be to prevent the Meter Serial Number & Meter Category Code existing at multiple mprns - this should prevent mprn specific meter reads being allocated to multiple mprns Each meter has a unique serial number. The central market system does not permit a single meter to be present at more than one installation. MPRN specific reads are covered by point no. 3 27

  28. Discussion Requests & Market Change Requests Susan Morrissey, RMDS 28

  29. New Market Change Request • MCR 0127 - Decouple Connection Agreement • requirement from Change of Supplier where • MIC >= 100kVA and there is no Change of Legal • Entity • Version 1 issued 31st January • Feedback requested by 15th February 29

  30. Discussion Request DR 0113 – Supplier of Last Resort Current Position • 2nd Clarifications Document issued to CER • SEM Team have highlighted a passage in the Trading and Settlement Code which contradicts the assumption of a dedicated supplier unit per SoLR event – “In the event that there are multiple defaults occurring at the same time, all retail customers affected by these default events will be managed under the one SoLR Supplier Unit unless the defaulting Supplier Unit is responsible for providing metered demand quantities that relate to a Trading Site with Non-Firm Access. “ Next Steps • Clarify issue relating to Trading and Settlement Code • On receipt of clarifications from CER the DR will be re-issued 30

  31. Discussion Request DR 0118 – Avoidance of Erroneous De-Registrations • Feedback Received 31

  32. Discussion Request • DR 0123 – Versioning of 341 Messages 32

  33. DR 0123 – New Table Versioning Scenarios • The following table explains how the “Version Number” will work. • Column 1 one identifies five possible Scenarios. • Column 2 identifies the Aggregation cycle. • Column 3 identifies the time period associated with the aggregation cycle (D = day, M = month). Column 4 indicates whether or not a reading is an estimate or an actual reading. • Column 5 indicates the sending of a message. • Column 6 shows the version number. • NOTE The version number acts as a flag to indicate a change from an estimate reading to an actual reading. The flag changes from 01 to 02. The flags themselves do not represent actual readings or estimate readings. • Scenario 1 indicates actual readings from D+1. The version number does not to change as there are actual readings to work with from day 1 • Scenario 2 where estimates are only available at D+1, but between D+1 and D+4 an actual reading is sent. This matches the current process and no Version number change is required • Scenario 3 where estimates are only available at D+4, but between D+4 and M+4 an actual reading is sent. The version number during this period, increments from 01 to 02 indicating the receipt of an actual reading that will replace an estimate reading. • Scenario 4 where estimates are only available at M+4, but between M+4 and M+13 an actual reading is sent. The version number during this period, increments from 01 to 02 indicating the receipt of an actual reading that will replace in estimate reading. • Scenario 5 where no actual reading has been received in 13 months. This may not be possible but it is important to cover all eventualities. In this case flag remains at 01. 33

  34. Proposed Diary dates for subsequent meetings • 08.03.07 • 19.04.07 • 07.06.07 (proposed change from 31.05.07 – near bank holiday) Next Steps 34

  35. Propose to continue with conference call every two weeks – proposed dates • Suggest cancelling Conference Call scheduled for 8th February • 22.02.07 • 22.03.07 • 04.04.07 • 03.05.07 • 17.05.07 • Call details will remain the same: • Number: 01-6647602 PIN : 77640 • Contingency number remains: 01-6647777 PIN: 60236 Next Steps 35

More Related