Senior Stakeholder Forum
description
Transcript of Senior Stakeholder Forum
Senior Stakeholder Forum
Wednesday 19th June 2013
Welcome
• Agenda– Purpose of the Forum Nick Salter
• Feedback on Terms of Reference
– Overall Industry Change Horizon Andy Miller– Project Nexus Update Andy Miller– UK-Link Programme
• Progress to Date Andy Watson• High Level Plans Andy Watson• Data Cleansing Andy Miller• Ongoing Engagement/Governance Sandra Simpson
– Review of Meeting Sandra Simpson
Overall Industry Change Horizon
Andy Miller
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+1 Release x+2
Ofgem Change of Supplier Initiative
Ongoing change - mods etc
Project Nexus Update
Andy Miller
• 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
UK-Link ProgrammeProgress & Plans
Andy Watson
Programme Manager
Programme Indicative Path
8Note: assumes a release based approach
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
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 Sourcing HLD
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
Indicative Path:Logical Analysis
Logical Analysis
Note: assumes a release based approach
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
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
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
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
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
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
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
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
System & User Test
R1Go 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
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
Note: assumes a release based approach
TestR2Go live
Build
Design
Release 2 Key Deliverables
• Same deliverables as Release 1, without High Level Design and potentially shorter timelines.
Indicative Path: Release 2
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
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
2013 2014 2015 2016
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
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
Data Cleansing
Andy Miller
Engagement & Governance
Sandra Simpson
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 12th September.