Draft UK Link Implementation Summary - Modifications & Distribution Workstream

1. Distribution WorkstreamUNC Modification 0224Draft UKLink Implementation SummaryResponses26th February 2009

2. …Draft UKLink Implementation Summary • DM Elective Change is a Tactical change • DM Elective seeks to reuse existing Daily Metered functionality • Majority of existing DM Interfaces are currently xoserve to / from DMSP • Solution seeking to minimise impacts on Non Participant Shippers • Initial Views sought on principles of the files/records

3. …Draft UKLink Implementation Summary • Comments invited on: • Input Reading File - DME file / O10 record. • Start and End readings are mandatory • Note: with current arrangement transfer reading cannot be provided on ‘D’ (where D is the confirmation effective date) • ‘Reading Date’ must reflect that it is the End Reading for a Gas Flow Day • i.e. date ‘R-1’ (where R is the actual reading date) – e.g. reading taken at 6am on 01/01/09 will be End Reading for GFD 31/12/08. • Reading fields protocol is that these fields are NOT necessarily populated with actual index • e.g. where a meter reads in cubic feet this typically might have a read unit of 100. On a 5 dial meter the NDM read register would show 01234, the equivalent DM reading expected within the DME file would be 0123400. • ‘Consumption’ field is expected to be populated with Metered Volume required to be calculated by Shipper

4. Draft UKLink Implementation Summary • Comments invited on: • RPA file / O02 and M01/S72 records. • Standard application level rejections will be embedded on the O02 • Standard UKL Rejection Record S72 record will not be provided • Maximum file breaches rejections shall use the M01 record, with a subordinate S72 record, providing the relevant rejection reason. • DMO file / Various 'O' prefixed records. • This is a new file for the additional level service. • Embedded within this response record is the outcome code to indicate whether the record was accepted or rejected. • The outcome is not indicated by an alternative record type.

5. Responses Received • SPA Changes: • Approach for new code in Gas Nomination Type seems sensible to reduce impact rather than introducing a new field, we support the approach. • DM Reading Files: • Input: • Acceptance that the DME is new format and there is nothing currently out there with this detail that can be utilised. Development of new file acknowledged as required. • Output: • Question whether differentiation of MDE from existing MDR is necessary, albeit minor development, suggest that MDR is used for DME purposes • Respondee does not support creation of the MDE file. Respondee requested other views. • DM Activities • ‘Maintain Datalogger Asset Data’ – “creation of a dummy datalogger into UK Link is essential and underpins the whole process without this action none of it works “ i.e. circumventing validation is a mandatory change.

6. Next Steps… • Appropriate to take Non Response as Acceptance??? • Comments received give indication of general acceptance of approach? • Detailed comments may provide changes later… • Need to account for this in Development Costs…