Project Nexus

1
Project Nexus Requirements DefinitionPhase
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.

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

4
Topics In-Scope of xoserves 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

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 IC supply points
• Demand Allocation data
• Inclusion of Unique Sites within Nexus
• New EUC for SSPs
• WAR calculation review
• Review SOQ process for DM NDM

6
Topics Currently Out-of-Scope of xoserves
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

7
Resources Available

• Requirements Register
• xoserves 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

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)

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 IC 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

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

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

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

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
• Workstream
• Modification Panel
• If consensus cannot be reached the status quo
  remains

14
.
Project Nexus Requirements DefinitionPhase
Strawman Plan Assumptions 30th April 2009
Shirley Wheeler
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 !
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

17
UNC Project Nexus Proposed High-level Plan
18
UNC Project Nexus Proposed Workgroup
Preparation Plan
19
UNC Project Nexus Proposed Workgroup Plan
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