Project Nexus Workgroup Extension of Modification 0434 to permit retrospective updates pre-dating Project Nexus Go Live Date 9 th September 2014

Mod 0434 development At the time the target system was unknown so 0434 drafted to be effective from Nexus Go Live Date only provides for read replacement where the read to be replaced has a date of Project Nexus Go Live Date or later only provides for an asset update where the asset event date is Project Nexus Go Live Date or later However, functionality in the target system provides for read replacement and asset updates where the event pre-dates Project Nexus Go Live Date to be submitted and accepted (validations permitting).

Proposal for Proposal to allow both read replacement and asset updates (only asset have been discussed previously) to use target system functionality and be submitted up to an event date which is the Code Cut Off Date (often referred to as “line in the sand”). Create a rolling read replacement and asset update window in line with Code Cut Off Date Financial adjustments will be processed as per 0434 with the exception of smaller supply points where any adjustment will only apply from Project Nexus Go Live Date (adjustments pre- dating Project Nexus Go Live Date will be managed through Reconciliation by Difference process)

Key Factors Inclusion of read replacements pre Project Nexus Go Live Date Creates a single methodology approach to retrospective adjustments arising from asset updates or read replacements whether the event concerned occurred pre or post Nexus Go Live Date. No financial impact (all financial adjustments are limited to Code Cut Off Date irrespective of Nexus) Target system will support single methodology Removes requirement to maintain pre Nexus adjustment methodology and tools. Application of post Nexus validation

Example Scenario: Erroneous Read Identified 1 st April 2012 (Code Cut Off ) Check Read Nexus Go Live Date Erroneous Read Process as per Shipper calculates consumption adjustment -CMS query submitted -Query validated -Consumption adjustment processed and invoiced Process as per Shipper submits replacement read -Target system validates read and updates Supply Point Register -Adjustment automatically calculated and invoiced Erroneous Read identified