Minutes from last IGG meeting10.00 – 10.10 Review of Action Items10.10 – 10.20 CER Update10.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 - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• 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
– 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
• Working Practice 13 – Termination of Duplicate MPRNs
– Issues raised by one supplier:
1. 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.
• 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.
• 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.
• 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
28
RMDSRMDSRMDSRMDS Retail Market Design Service www.rmdservice.com
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
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.
34
RMDSRMDSRMDSRMDS Retail Market Design Service www.rmdservice.com
Next Steps
• Proposed Diary dates for subsequent meetings
– 08.03.07– 19.04.07– 07.06.07 (proposed change from 31.05.07 – near
bank holiday)
35
RMDSRMDSRMDSRMDS Retail Market Design Service www.rmdservice.com
Next Steps
• Propose to continue with conference call every two weeks – proposed dates
Suggest cancelling Conference Call scheduled for 8th February