1. Project Nexus (AMR) Workgroup – 7 th July 2010 Response to Transporter action

2. Transporter action response – 22 nd June meeting  From minutes of 22 nd June meeting. The group identified a requirement to determine:  ……who needs the data, and for what purpose, as a necessary starting point.  The Transporters were asked to specify their meter read data requirements going forward, which CW believed would be well worth looking at and he would be happy to provide thoughts for the next meeting.  Action AMR0014: Transporters (CW) to specify the Transporter meter read data requirements going forward

3. Core Transporter Meter Reading data requirements  Primary obligations set out in UNC Principal Document.  Consumption data is used to calculate/derive AQs and undertake NDM Reconciliation (Individual). We currently determine consumptions by using:  Validated Meter Readings:  Required to calculate Metered Volumes and by applying CV to calculate Metered Quantities (kWh values)  Meter Information:  Required to derive Metered Volumes by applying relevant ‘asset’ data to ‘cyclical’ read sequences  Transporters use Meter Information for some other purposes such as helping to validate ‘M’ numbers.

4. Core Transporter Meter Reading data requirements  Ultimately Transporters require access to accurate energy values to meet our UNC obligations.  Going forward we need to be absolutely certain that we can derive or obtain these accurately and in a timely way to maximise the efficiency of our key UNC related processes  We know that the receipt of Meter Readings and Meter Information are a tried and tested way in which this can be achieved but are there alternatives?  We believe that the administratively burdensome and inefficient activities of dealing with erroneous and poor quality data need to be dealt with. How can this be achieved?  We would welcome the views of Shippers regarding how this key requirement can be safeguarded in the most efficient manner