1. UK Link Programme Update to PNUNC August 13th, 2013

2. Introduction
The aim of this session is to provide an overview of the anticipated programme activity for the replacement of UK Link
It should be noted that at present these timescales are indicative and as more information becomes available as the programme progresses formal updates will be provided. 2

3. Programme Indicative Path
2013
2014
2015
2016 Q1 Q2 Q3 Q4
Logical Analysis
DBI Sourcing
HLD
Detailed Design
Cutover and go-live
Build & Dev Test
System & User Test
Design
R2 Cutover and go-live
Build
Test
Data Cleansing
Stakeholder Engagement
Note: assumes a release based approach 3

4. Indicative Path: Logical Analysis Logical Analysis Key Deliverables
2013
2014
2015
2016 Q1 Q2 Q3 Q4
Logical Analysis
Logical Analysis Key Deliverables
Phase started 25th 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
Note: assumes a release based approach

5. Indicative Path: High Level Design High Level Design Key Deliverables
2013
2014
2015
2016 Q1 Q2 Q3 Q4
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
High Level Design
Note: assumes a release based approach

6. Indicative Path: Detailed Design Detailed Design Key Deliverables
2013
2014
2015
2016 Q1 Q2 Q3 Q4
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
Detailed Design
Note: assumes a release based approach

7. Indicative Path: Build Build Key Deliverables
2013
2014
2015
2016 Q1 Q2 Q3 Q4
Build
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
Note: assumes a release based approach

8. Note: assumes a release based approach
Indicative Path: Test
2013
2014
2015
2016 Q1 Q2 Q3 Q4
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
System & User Test R1
Go live
Note: assumes a release based approach

9. Indicative Path: Release 2 Release 2 Key Deliverables
2013
2014
2015
2016 Q1 Q2 Q3 Q4
Release 2 Key Deliverables
Same deliverables as Release 1, without High Level Design and potentially shorter timelines.
Build
Design
Test R2
Go live
Note: assumes a release based approach

10. Indicative Path: Data Cleansing & Migration
2013
2014
2015
2016 Q1 Q2 Q3 Q4
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
Data Cleansing & MIgration
Note: assumes a release based approach

11. Indicative Path: Stakeholder Engagement
2013
2014
2015
2016 Q1 Q2 Q3 Q4
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
Stakeholder Engagement
Note: assumes a release based approach