1 project nexus requirements definition phase steve nunnington

20
1 Project Nexus Project Nexus Requirements Definition Requirements Definition Phase Phase Steve Nunnington

Upload: baldric-reynolds

Post on 26-Dec-2015

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1 Project Nexus Requirements Definition Phase Steve Nunnington

1

Project NexusProject Nexus

Requirements DefinitionRequirements DefinitionPhasePhase

Steve Nunnington

Page 2: 1 Project Nexus Requirements Definition Phase Steve Nunnington

2

UNC Project Nexus Workstream Proposals

Project Nexus UNC Workstream formed to debate and develop the UNC Topics which support the delivery of Project Nexus.

21 Topics in scope within the ‘Initial Requirements Register’ 9 major Topics 12 Others

Topics to be raised formally as per normal UNC Workstream governance

Any new Topics to be raised in this way Proposal to employ Topic Workgroups similar in structure to

UNC Development Workgroups Workstream to review Topics and decide which Topics should

be debated within a workgroup.

Page 3: 1 Project Nexus Requirements Definition Phase Steve Nunnington

3

Project Nexus Interactions

Responsibilities of UNC Project Nexus Workstream Prioritisation & grouping of Topics and issues Recommend approval or rejection of proposals Provide guidance to Topic Workgroups Review Topic Workgroup update reports Refer back to the Workgroup where further analysis or information is required Review details of any new topics raised within the Workgroups and carry out

an impact assessment to decide if a new Workgroup is required Ensure adequate publicity is given to proposals, as appropriate Seek views of the Authority or affected bodies (E.G. BERR, IGT UNC, SPAA

etc.) on matters connected to any proposal Define assumptions and principles to support the business rule development Track cross Topic Workgroup inter-dependencies Workstream to initiate legal drafting Manage change control

Page 4: 1 Project Nexus Requirements Definition Phase Steve Nunnington

4

Topics In-Scope of xoserve’s Prevailing Services

Initial Requirements Register – within scope of Workstream

Supplier Switching Market Differentiation Connection and Registration Increased reads for Energy Allocation, Balancing and Transportation

Charging Reconciliation AQ Management Volume Capture Invoicing Rules Treatment of Retrospective Updates

Page 5: 1 Project Nexus Requirements Definition Phase Steve Nunnington

5

‘Other’ In-Scope Topics cont.

Governance of SPA Fuel Poor Incentive and Liability regime review Review Of Reporting Requirements Central Register of Emergency Contacts Multiple shippers per legal entity SSP I&C supply points Demand Allocation data Inclusion of Unique Sites within Nexus New EUC for SSPs WAR calculation review Review SOQ process for DM & NDM

Page 6: 1 Project Nexus Requirements Definition Phase Steve Nunnington

6

Topics Currently Out-of-Scope of xoserve’s Prevailing Services

Initial Requirements Register – currently out of the scope of Workstream Data Management – Data Hub Data Management – Quality Assurance Data Management – Exchange & Flows of Data Data Management – Central Data Store for Smart Metering Data iGT Services

xoserve will look to build on the discussions being facilitated by Ofgem and SPAA in respect of iGT services and DECC in respect of Smart Meters.

xoserve will organise and facilitate separate workgroups for Data Management.

The outputs from the above Workgroups will contribute to the Topic Workgroup discussions

Page 7: 1 Project Nexus Requirements Definition Phase Steve Nunnington

7

Resources Available

Requirements Register xoserve’s Review of Topics List of relevant Mods (Live and closed) Interdependencies of Topic Workgroups Contractual Obligation Impacts Outline Terms Of Reference for Topic Workgroups Industry participant benefit matrix Impacts/Dependencies analysis from Data Management &

iGT Topics xoserve existing BPMs

Page 8: 1 Project Nexus Requirements Definition Phase Steve Nunnington

8

Proposed Topic Grouping and Priorities

1 Market Differentiation Workgroup 2. Market Differentiation

2 Connection & Registration Workgroup 3. Connection & Registration

3 SPA Workgroup 1. Supplier Switching (Dual Fuel & Switching Timescales) 10.1 Governance Of Industry SPA process 10.2 Identification of Fuel Poor 10.5 Register of Emergency Contact Details 10.6 Multiple Suppliers/Shippers per legal entity 10.9 Single database for all supply points (E.G. Unique Sites)

Page 9: 1 Project Nexus Requirements Definition Phase Steve Nunnington

9

Proposed Topic Grouping and Priorities cont.

4 Volume Workgroup 7. Volume Capture

5 Meter Reading Workgroup 4. Increased Reads for Energy

6 Retrospective Update Workgroup 9. Treatment of Retrospective

7 AQ & Allocation Energy Workgroup 6. AQ Management 10.7 I&C status / profile in SSP market sector 10.8 Demand Allocation data split by SSP and LSP market 10.10 Review Winter Annual Ratio calculation and allocation of EUC 10.12 Review treatment of SOQs in DM and NDM arenas

Page 10: 1 Project Nexus Requirements Definition Phase Steve Nunnington

10

Proposed Topic Grouping and Priorities cont.

8 Invoicing Workgroup 8. Invoicing Rules 10.3 Review of Incentives & Liabilities

9 Reconciliation Workgroup Reconciliation

10 Non-Functional Workgroup This workgroup would discuss all non-functional areas, e.g. file

formats and interfaces. The workgroup may require a representative from each of the other workgroups as the method and process for delivery of each topic will have to be considered

Page 11: 1 Project Nexus Requirements Definition Phase Steve Nunnington

11

Proposed Topic Management

Governance TOR for each Workgroup/Topic All documentation available on JO website JO to chair meetings Minutes to be produced within 5 days Agenda available at least 5 days prior to meeting Monthly report to be sent to Workstream charting progress Any new Topics to be approved by Workstream and allocated to a Workgroup

1st Workgroup (per Topic area) Decide on attendees Venue Dates and times of meetings (10AM – 3PM) Sponsor to introduce Topic TOR signed off Creation of Workplan

Page 12: 1 Project Nexus Requirements Definition Phase Steve Nunnington

12

Proposed Topic Management cont.

2nd Meeting xoserve produce ‘As Is’ Process Model Baseline current process and obtain consensus Outside the meeting stakeholders will identify issues This could take more than one meeting dependent on complexity

Subsequent Meetings Further opportunity for consultation respondents to air their views and develop

their ideas into a tangible proposition Other stakeholders to present their issues & Improvement Opportunities Group to examine and discuss these proposals and discuss which ones

should be taken forward Consider impacts of in-flight mods Consider determinations made to closed modifications (Joint Office) Costs & Benefits should be the main driver to take issues forward

Page 13: 1 Project Nexus Requirements Definition Phase Steve Nunnington

13

Proposed Workgroup Outputs

Re-draw Process Models after the discussions have concluded to give ‘To Be’ Maps

xoserve will maintain a register to ensure that all Topic areas are discussed and ensure traceability

Produce a Report for every Topic investigated including a justification for their outcome

Raise any UNC Mod as appropriate & pass to Workstream Capture Requirements in a tool to be defined by xoserve Produce a set of business rules sufficient to aid design Where consensus cannot be reached escalation will be

1. Workstream2. Modification Panel

If consensus cannot be reached the status quo remains

Page 14: 1 Project Nexus Requirements Definition Phase Steve Nunnington

14

.

Project NexusProject Nexus

Requirements DefinitionRequirements DefinitionPhasePhase

‘ ‘Strawman’ Plan & AssumptionsStrawman’ Plan & Assumptions3030thth April 2009 April 2009

Shirley Wheeler

Page 15: 1 Project Nexus Requirements Definition Phase Steve Nunnington

15

UNC Project Nexus Planning Assumptions

Several principles need to be agreed by industry before commencement of workgroup workshops Funding Principles Change Control Mechanism

Approach proposal is accepted by UNC Workstream 10 Workgroups Overarching Workstream

10 Topic areas determined as S, M or L Determines the number of workshops per category

Scene Setting

Current Processes

‘To be’

Processes

Finalisation Sub Total No. of Scenarios

Total

S 1 1 2 2 6 3 18

M 1 3 5 2 11 5 55

L 1 4 12 2 19 2 38

Makes a total of 111 workgroup meetings, excluding Workstream Meetings !

Page 16: 1 Project Nexus Requirements Definition Phase Steve Nunnington

16

UNC Project Nexus Planning Assumptions

Workgroups cannot all be worked concurrently Resources Dependencies

If one workshop planned every three/four weeks timescale of 2010 cannot be achieved, therefore:- 2 day workshops have been planned for ‘Current Process Verification’ 3 day workshops have been planned for ‘To be processes’

Consistency of approach/attendees Less recapping on previous meetings ‘Longer days’ – less travelling Less Administration for all parties

Work content does not include any impact on accepting any iGT, Data Management/Smart Metering requirements

On ‘smaller’ non-related topics Modifications/legal drafting raised as soon as possible, but will still need to be included in final consistency check

Review of Requirements to ensure that they are all still relevant

Page 17: 1 Project Nexus Requirements Definition Phase Steve Nunnington

17

UNC Project Nexus – Proposed High-level Plan

UniqueID

Task Name Duration Start Finish

1 Requirements Capture 410 days Mon 20/04/09 Fri 12/11/10

60 Preparation Phase 183 days Mon 20/04/09 Thu 31/12/09

205 Development of Workstream Plans 47 days Thu 23/04/09 Mon 29/06/09

64 Workstream Preparation 183 days Mon 20/04/09 Thu 31/12/09

61 Development Phase 379 days Tue 02/06/09 Fri 12/11/10

101 UNC Workstream 379 days Tue 02/06/09 Fri 12/11/10

218 Workstream Progress Meetings 306 days Thu 25/06/09 Thu 26/08/10

178 Workstream Workgroups 313 days Tue 02/06/09 Thu 12/08/10

177 Penultimate Workstream Meeting 6 days Fri 13/08/10 Fri 20/08/10

180 Final Workstream Meeting 0 days Fri 20/08/10 Fri 20/08/10

186 Legal Drafting 35 days Mon 23/08/10 Fri 08/10/10

188 UNC Modifications 20 days Fri 15/10/10 Fri 12/11/10

200 Exit Criteria 0 days Fri 12/11/10 Fri 12/11/10

20/08

12/11

Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter

2009 2010 2011

Page 18: 1 Project Nexus Requirements Definition Phase Steve Nunnington

18

UNC Project Nexus – Proposed Workgroup Preparation Plan

UniqueID

Task Name Duration Start Finish

1 Requirements Capture 410 days Mon 20/04/09 Fri 12/11/10

60 Preparation Phase 183 days Mon 20/04/09 Thu 31/12/09

205 Development of Workstream Plans 47 days Thu 23/04/09 Mon 29/06/09

64 Workstream Preparation 183 days Mon 20/04/09 Thu 31/12/09

67 Current Operational Process Maps 22 days Fri 01/05/09 Tue 02/06/09

197 Requirements Register 0 days Thu 30/04/09 Thu 30/04/09

71 Data Management Requirements 0 days Mon 30/11/09 Mon 30/11/09

198 iGT Requirements ? 0 days Fri 19/06/09 Fri 19/06/09

199 Funding 0 days Thu 28/05/09 Thu 28/05/09

94 Requirements Change Control 151 days Fri 01/05/09 Mon 30/11/09

98 Legal Drafting 66 days Wed 30/09/09 Thu 31/12/09

108 UNC Workstream 20 days Thu 30/04/09 Thu 28/05/09

109 Workstream Approach 20 days Thu 30/04/09 Thu 28/05/09

61 Development Phase 379 days Tue 02/06/09 Fri 12/11/10

200 Exit Criteria 0 days Fri 12/11/10 Fri 12/11/10

30/04

30/11

19/06

28/05

12/11

Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter

2009 2010 2011

Page 19: 1 Project Nexus Requirements Definition Phase Steve Nunnington

19

UNC Project Nexus – Proposed Workgroup Plan

UniqueID

Task Name Duration Start Finish

101 UNC Workstream 379 days Tue 02/06/09 Fri 12/11/10

218 Workstream Progress Meetings 306 days Thu 25/06/09 Thu 26/08/10

178 Workstream Workgroups 313 days Tue 02/06/09 Thu 12/08/10

102 Market Diff Workgroup (1) (L) 137 days Tue 02/06/09 Wed 09/12/09

116 Conx and Disconx Workgroup (2) (M)123 days Tue 30/06/09 Thu 17/12/09

122 SPA Workgroup (3) (L) 153 days Wed 28/10/09 Fri 28/05/10

128 Voulume Workgroup (4) (S) 104 days Wed 10/06/09 Mon 02/11/09

134 Meter Reading Workgroup (5) (M) 123 days Thu 02/07/09 Mon 21/12/09

145 Retro Update Workgroup (6) (M) 123 days Fri 18/09/09 Tue 09/03/10

146 AQ & Alloc Energy Workgroup (7) (M)123 days Mon 16/11/09 Wed 05/05/10

157 Invoicing Workgroup (8) (S) 94 days Mon 01/03/10 Thu 08/07/10

163 Reconciliation Workgroup (9) (M) 62 days Wed 19/05/10 Thu 12/08/10

169 Non-functional Workgroup (10) (S) 104 days Thu 12/11/09 Tue 06/04/10

177 Penultimate Workstream Meeting 6 days Fri 13/08/10 Fri 20/08/10

180 Final Workstream Meeting 0 days Fri 20/08/10 Fri 20/08/10

186 Legal Drafting 35 days Mon 23/08/10 Fri 08/10/10

188 UNC Modifications 20 days Fri 15/10/10 Fri 12/11/10

20/08

Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan2nd Quarter 3rd Quarter 4th Quarter 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter 1st Quarter

2009 2010 2011

Page 20: 1 Project Nexus Requirements Definition Phase Steve Nunnington

20

UNC Project Nexus Planning – Next Steps

What Who When

Feedback to approach & plan Workstream 13th May 2009

Update approach, assumptions & plan. xoserve 21st May 2009

Approach, assumptions & plan agreed at Workstream

Workstream 28th May 2009

Actual dates for all workshops,venues published

xoserve 12th June 2009

Plan baselined Workstream 25th June 2009

Progress monitoring commences All Ongoing