DSC Governance Sub Group Recommendations

Slides:



Advertisements
Similar presentations
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
Advertisements

DSC Change Governance Review Group
XRN4361 – UK Link Release 2 - Delivery
Project Roles and Responsibilities
Market Trials ChMC 8th August 2018.
DSC Change Committee Summary – 12th December
DSC Change Committee Summary – 13th June
Change Management Committee – June 2019 Update
DSC ChMC CSS update 7th November 2018
Amendment Invoice Task Force Progress Report
Overall Project RAG Status
UIG Task Force Progress Report
Change Management Committee – June 2019 Update
2019 Release Planning Options inc Modification 0621 / GB Charging Project DSC Change Management Committee update July 2018.
Change Management Committee – November 2019 Release Update
CSS Update for CoMC 19th September 2018
DSC ChMC CSS update 6th July 2018
DSC Change Committee Summary – 11th July
COR1360 NTS Exit Reform (Mod 0195AV) UK-Link Committee 11th June 2009
Background MDD is currently managed within SPAA
Release 3 Plan Options Analysis
Overall Project RAG Status
DSC Change Committee Summary – 10th October
DSC Change Committee Summary – 9th May
XRN4361 – UK Link Release 2 - Delivery
UIG Task Force Progress Report
Change Proposals Capture to Delivery
Smart Metering Portfolio DCC Day 1 UK Link Committee DCC Day 1 Shipper File Format Representation Thursday 08th August 2013.
UIG Task Force Progress Report
DSC Change Committee Summary – 9th January ‘19
KVI Change Management Survey Feedback
UKL Committee - DN Interruption Update
DSC Change Committee Summary – 13th March ‘19
Release 3 Update 07th March 2018.
Release 3 Scope & Proposed Plan
Change Management Committee – Retail & Networks Update
DSC Change Committee Summary – 13th February ‘19
UIG Task Force Progress Report
CDSP Service Document amendment - high-level activity description*
UK Link Future Release 3: Track 1 Implementation Approach for Approval at ChMC 2nd October 2018.
Change Management Committee – November 2019 Release Update
DSC ChMC CSS update 12th September 2018
XRN4658 – OTR UNCVR Amendment
Implementation Approach Distribution Workgroup – June 2014
UIG Task Force Progress Report
DSC Change Committee Summary – 7th March
DSC Governance Review Group
UK Link Future Release 3: Track 1 Implementation Approach for Approval at ChMC 2nd October 2018.
UIG Task Force Progress Report
UIG Task Force Progress Report
DSC Change Committee Update
UIG Task Force Progress Report
DSC Change Committee Update
DSC Governance Review Group
DSC ChMC Switching Programme Update 10th July 2019
UIG Task Force Progress Report
DSG Governance Group Recommendations.
UIG Task Force Progress Report
DSC ChMC Switching Programme Update 10th July 2019
Process for Updates to the DSC Service Description Table
DSC Change Committee Update
UIG Task Force Progress Report
DSC ChMC Switching Programme Update 11th September 2019
DSC ChMC Switching Programme Update 10th July 2019
DSC Change Committee Update
DSC CoMC Switching Programme Update September 2019
UIG Task Force Progress Report
UIG Task Force Progress Report
UIG Task Force Progress Report
UIG Task Force Progress Report
Presentation transcript:

DSC Governance Sub Group Recommendations July 2018

Agenda Scope of change to Change Committee Change Proposal process map Change Proposal templates EQR/BER/CCR templates Rom Form and Process Change Pack High level Design documentation Change register Publication of Change Proposal’s DSG terms of reference review

Scope of Changes to be tabled at Change Committee meetings All Change Proposals raised by Shipper/DN/NTS/IGT Any change raised by Xoserve, that has an external consequential impact, for information Pass to DSG to work up suitable solution Changes to Service lines (information and to approve no requirement for EQR/BER, CoMC approve the service line change)

Change proposal process map Maps the process through the capture phase up to approval of the CP into delivery (could be data, minor or major release)

Change Proposal Templates Templates simplified The change proposal template will build as it progresses through the change cycle i.e. will append review outcomes to the CP and EQR/BER/CCR as they are produced Version control on the CP with a history of updates provided in the document Change proposal EQR BER CCR The Change proposal document shows all appendices that will be added to change proposal (dependant on the process on the CP follows) as it progresses through capture phase. Appendix 1 is completed internally by Xoserve with the output reviewed and ratified with DSG – this provides the priority score

EQR, BER and CCR Forms In most cases would only expect an EQR for major releases not required for change delivered: Via minor release Via data office Documentation changes In all instances a BER and CCR will be provided and require approval at Change Committee

Change proposal publications When a new Change Proposal is raised this will be issued out via Joint Office with a covering email confirming it a new Change Proposal to be reviewed at next Change Committee All Change Proposals will continue to be published on Joint Office website, new version will be published each time it is amended (the previous versions will also be available)

Review/Consultation phases Change Proposal Review process/consultation will be sought at 3 stages of the change process (not every change will require all) Initial review Solution review Detailed Design The process allows parties to provide a representation through the change process on the principle of the change, the solution and the detailed impacts of the change. The representations received will be included in the Change Proposal documentation and will aid Change Managers when requested to vote to proceed at each stage If a User requests their comments to remain private (not to be published) the information will not be shared but we will note the rep (not info supplied) and if the rep was in support or not. All will be issued via the change pack process.

Review/Consultation phases Review/Consultation type Description Aim/expectation Project phase Change Proposal Review (period defined by proposer) Change Managers send a CP for initial review following submission to Change Management committee Reviewer to make initial assessment of the change and if the change should progress Capture Solution Review 10 business day process Issue out high level design documents for each solution options, providing high level design impact and costs per change, and time to deliver (cost and time lines are best estimate) Reviewer to review solution options and give a view of the preferred solution (Xoserve will state to DSG preferred option where appropriate the Xoserve preferred solution option) Design Consultation standard change pack process issued out at detailed design phase providing detailed impacts including interface and documentation Reviewer to review and comment on the final solution including all amended interface documents; these form the basis of system build and design externally for all Users (once approved) Delivery (detailed design)

High level Design Documentation For each solution option the high level design impacts document will be completed, this will give a view of: The systems impacts and complexity level The high level cost of the change Estimated delivery time scales The information will supplied out during solution review for reps

Change Packs Issued each Friday following Change Management Committee Can issue extraordinary packs if required; normally this will be requested at ChMC Xoserve will only be required to respond to design consultation. Review comments will be supplied to Change Managers (if confirmed can be published) to provide a wider view and aid in voting matters on if a change should progress

Release Circular Each Release will have a Change reference number and a release circular document to support the release (rather than a CP template as per current process.

ROM process A standalone process (will not be raising a CP to get a ROM) Following receipt of request for a ROM The request will be logged The ROM produced On delivery of the ROM the request will be closed on the Change Register A CP will be required to be raised at the appropriate time if the ‘idea’ is required to be progressed

Change Register New status aligned to CP form All change information supplied will be an extract of the change register i.e. for future release purposes June 19 release button added

What change is delivered in Minor release? Xoserve Internal impacting change Non systems impacting change for any Customers Documentation only changes i.e. descriptions New reporting / reporting changes that are not delivered through automated processes i.e. IX API based solutions The proposer or DSG can recommend the change is delivered via a minor release but the final decision would be with ChMC (section on the CP to state major (and mm/yyyy) or Minor release)

What change is delivered in Major release? Changes to interfaces to customers Requires installation or modification of hardware of software for any customer Changes to format of any UK Link Communications File Format changes including addition of allowable values Anything ChMC determines as requiring delivery via major release rather than minor release

Work in Progress Extract of change register to provide high level view of Change Proposals, status of the proposal and next stage Xoserve to publish Change Proposals on Xoserve.com so all change information in one single place (a link to the information will be published on Joint Office website). Create a guidance document on raising a change proposal and the process for change Ongoing review of forms to ensure fit for purpose Full review of DSC Change Management Procedures assess against new processes and assess if changes are required.