CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Review Group 272 28 April 2010 CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Recap of Previous Meetings (covered 11 March 2010) Never, ever touch the Mod 640 invoice Timelines for Mod 640 Invoices already tight Any correction could be through ad hoc invoice issued at same time as Mod 640 invoice Split view on Governance Could be under UNC – aids billing, transparency and compliance/interpretation Could be outside of UNC similar to ISD process – facilitate Shipper to Shipper settlement, simpler? Need to address materiality of issue CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Recap of Previous Meetings – 11 March 2010 No time limit for raising an inter-Shipper query – cut off for informing xoserve should facilitate this. There should be a cut off for informing xoserve – e.g.: 5th business day in February Mixed views as to whether cut-off date should support issuing of ad-hoc invoice at the same time as Mod 640 invoice or wash up after the invoice. EDF Energy initial view is cut off date should be 5-6 weeks after Mod 640 invoice is issued by xoserve to provide “wash up” period. CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Recap of Previous Meetings – 11 March 2010 (cont). Notification of any re-apportionment of Mod 640 invoice to xoserve should come from registered Shipper who warrants that all impacted Shippers agree Re-apportionment should be in percentage and must add to 100% E.g. 0% Shipper A, 20% Shipper B, 80% Shipper C CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Actions Shippers to consider the materiality of the number of 640 queries likely to be raised: Information from xoserve shows worst case scenario is 11% (2,527 supply points) of mod 640 would be queried. EDF Energy believes actual number of queries likely to be percentage of this – but unable to quantify without backing data Develop a definition of valid and invalid queries: Covered in slides CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Actions Cont. Review Group to consider any data protection issues with the information required within the report to be provided to Shipper: Supplier information and date of registration is available through ECOES – therefore no data protection issues with releasing this information. CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Valid Queries Valid Queries Any query where it is clear that the change from SSP to LSP occurred in a subsequent Shipper’s ownership. E.g. Meter Readings demonstrate that AQ change occurred in next Shippers’ ownership Threshold crossing occurred due to errors caused by subsequent Shipper – including meter reading errors and asset detail errors Threshold crossing occurred due to lack of action by registered Shipper in AQ Amendment window (i.e. should remain an SSP) CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
Invalid Queries Invalid Queries Any query where it is clear that the change from SSP to LSP occurred in Shipper who is raising the query’s ownership. Or Any query where it is unclear when the change from SSP to LSP occurred. Some examples: Meter Readings demonstrate that AQ change occurred in Shippers’ ownership who is raising the query Threshold crossing occurred due to errors caused by Shipper who is raising query and compounded by subsequent Shippers – including meter reading errors and asset detail errors Threshold crossing occurred at, or around change of supplier No evidence to demonstrate when change in AQ occurred CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.
CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc CONFIDENTIAL - Review Group 272 © 24 November 2009 EDF Energy plc. All rights Reserved.