1. Senior Stakeholder Forum Wednesday 19 th June 2013

2. Welcome Agenda –Purpose of the ForumNick Salter Feedback on Terms of Reference –Overall Industry Change HorizonAndy Miller –Project Nexus UpdateAndy Miller –UK-Link Programme Progress to DateAndy Watson High Level PlansAndy Watson Data CleansingAndy Miller Ongoing Engagement/GovernanceSandra Simpson –Review of MeetingSandra Simpson

3. Overall Industry Change Horizon Andy Miller

4. 2012 2013 2014 2015 2016/17 2020 DCC Evolution Non UKL technology refresh / replace Nexus BRD’s & Mods European Market Development SMIP Foundation DCC day 1 UK Link Programme FGO Review Change programme Release x+1Release x+2 Ofgem Change of Supplier Initiative Ongoing change - mods etc

5. Project Nexus Update Andy Miller

6. 432 Project Nexus – gas settlement reform 434 Project Nexus – Retrospective Adjustment 440 Project Nexus iGT Single Service Provision –Also iGT UNC039 - iGT Agency Services 453 Project Nexus – Demand Estimation Others expected to support implementation Nexus requirements – supporting UNC Modifications

7. UK-Link Programme Progress & Plans Andy Watson Programme Manager

8. Programme Indicative Path 8 Note: assumes a release based approach 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Build & Dev Test Logical Analysis System & User Test Data Cleansing Test Build Design Detailed Design Stakeholder Engagement Cutover and go-live R2 Cutover and go-live DBI SourcingHLD

9. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Indicative Path: Logical Analysis Logical Analysis Note: assumes a release based approach Logical Analysis Key Deliverables Phase started 25 th March 2013 Develop Logical Process & Data Models for the requirements captured in the BRDs during Project Nexus and known future requirements Undertake a detailed review of the Non-Functional Requirements. Define and introduce Competency Centre to support delivery of future changes as an enduring service Output will inform and support all future phases of the Programme

10. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Note: assumes a release based approach Indicative Path: High Level Design High Level Design High Level Design Key Deliverables High Level Architecture Design, details the high level future state business processes and solution design Security Architecture and Policies, details at high level the framework to protect all assets Integration Architecture, details at high level, the integration framework between all systems, both internal to Xoserve and external Test Strategy & Plan, defines the overall test approach and each test phase with corresponding timelines Programme Delivery, definition and timescales of the remaining phases and indicative release plan

11. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Note: assumes a release based approach Indicative Path: Detailed Design Detailed Design Detailed Design Key Deliverables Detailed Architecture Design Detailed Security Architecture and Policies Detailed Integration Architecture Detailed Test Strategy & Plan, defines the overall test approach for each test phase with corresponding timelines Programme Delivery, definition and timescales of the remaining phases and detailed delivery plan Detailed Data Migration plan

12. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Build Note: assumes a release based approach Build Key Deliverables Technical Specification; Batch Job Configuration; Installation Guides Training Content & Materials; Test scripts Cutover plan Service Transition plan Dependencies / Impact on Legacy Systems Indicative Path: Build

13. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 System & User Test R1 Go live Note: assumes a release based approach Test Key Deliverables Under take User and System Test Review test results Dev Test System Test Integration Test Performance Test User Acceptance Test Technical / Operations Test Industry / Regulatory Transition handover document Indicative Path: Test

14. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Note: assumes a release based approach Test R2 Go live Build Design Release 2 Key Deliverables Same deliverables as Release 1, without High Level Design and potentially shorter timelines. Indicative Path: Release 2

15. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Data Cleansing & MIgration Note: assumes a release based approach Data Cleansing Key Deliverables Data Cleansing Strategy & Approach Identification of Data Issues Data Topics Data Profiling Data Issue Analysis & Prioritisation Industry Engagement UK Link Steady State Cleansing Data Cleansing Progress Reporting Indicative Path: Data Cleansing & Migration

16. 2013201420152016 Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q4Q1Q2 Note: assumes a release based approach Stakeholder Engagement Key Deliverables Identify stakeholders Understand Stakeholder Expectations Analyse and Map Stakeholders (Involve / Influence) Develop, maintain an effective communication plan (Review / Modify) Increase Stakeholder cooperation and success in delivering overall objectives (Impact of Change, Testing phases) Reduce the risk of misunderstanding the scope of work Indicative Path: Stakeholder Engagement Stakeholder Engagement

17. Data Cleansing Andy Miller

18. Engagement & Governance Sandra Simpson

19. UK-Link Programme Engagement PN UNC UK-Link Committee  Established by Mod Panel to facilitate discussions on topics and development of mods  Requirement for workgroup will cease once modifications are approved  Still a requirement for, and value in, a business focussed group  Clarifications, data cleansing, testing, transition & migration arrangements  May be the same attendees or may be more operational  Focus on technical matters only  File formats, interface architecture  Need to ensure organisations are represented  UKL Programme launch at UK- Link Committee on 12 th September.