Project Nexus - Meeting Scenarios and Review

Transcription

1 Monday 18 th May 2009 Attendees: Name Nick Salter (NS) Helen Bennett (HB) (Secretary) Shirley Wheeler (SW) (Chair) Andrew Campbell (AC) Simon Harrison (SH) Simon Trivella (ST) Graham Wood (GW) Ashley Collins (ACo) Hazel Ward (HW) Alan Raper (AR) Brian Durber (BD) Martin Brandt (MB) Jemma Woolston (JW) Sean McGoldrick (SM) Joel Martin (JM) David Rodger (DR) Wayne Mills (WM) Richard Street (RS) Joanna Fergusson Organisation Engage Consulting Wales & West Utilities British Gas EDF Energy npower National Grid Distribution E.ON UK Scottish and Southern Shell Gas Direct National Grid Transmission Scotia Gas Networks Scottish Power Scottish Power Corona Northern Gas Apologies: Name Jacqui Hall Organisation CNG 1. Introduction & Project Nexus Background SW opened the workshop and introduced the attendees before handing over to NS who presented a brief background to Project Nexus, the Consultation, its outcomes and Data Management. 2. Scene Setting AC explained that the main purpose of the workshop is to agree the Data Management objectives, define the scope of what we are trying to achieve and the approach to be adopted. He further explained that the subsequent 3 workshops will focus on the various options and concepts and add detail. 3. Review Data Management Definition document Publication of DM documents The workshop enquired as to whether the Definition document is published anywhere on the website. AC confirmed that it wasn t at this point but would be once it was finalised. The workshop further explained that this does not help small suppliers as it is not easy for them to attend every meeting; because the document is not published it s difficult for them to comment or contribute without attending the meeting. NS agreed that the Definition document can be put on the website; however, will need to ensure that all interested parties are aware of its status as this is not the final version of the Definition document. 1

2 Summary The workshop was concerned about the use of the word preferred regarding Data Management options and concepts. This is largely due to the levels of uncertainty within the industry and predominantly related to the Smart Metering Market Model and its implications. The workshop suggested the use of the word potential instead of preferred. AC confirmed that s proposed approach is to attempt to identify preferred options and that the timing may be right in relation to the DECC Smart Metering consultation. The workshop agreed that it is not unreasonable to come up with some high level principles and options for Data Management. However, it concluded that preferred options and concepts may prove difficult to agree. It was agreed that the use of preferred would be reconsidered. There were similar concerns raised regarding the use of the word Conclusions to describe the report resulting / outcomes from the s. After some debate it was agreed that the use of conclusions would be reconsidered; some alternatives suggested were framework or potential. It was agreed that the aim / scope of the Data Management s should look to determine the likely direction in which DECC s work on the Smart Metering Market Model will drive the industry. Data Management Milestones There was some concern about the timing of the s in relation to the PNUNC work stream and DECC s Smart Metering Market Model consultation. It was agreed that there should be a checkpoint in the plan to get back together after the DECC consultation process to ensure that there s consistency between the Data Management work, the stakeholders responses to DECC s Smart Metering Market Model Consultation and the PNUNC work stream and to confirm that the planned with senior stakeholder representatives should commence. The was also concerned about timeframes suggesting the subsequent s are too close together. AC explained the proposed approach but the requested that the time between s be extended. It was agreed that the timings should enable a full 10 working day review of notes and outcomes before subsequent s are run. It was further agreed that Mondays would be the most preferable day of the week to hold the workshops. Approach The asked if is intending to produce a Logical Data Model as part of this project. SW confirmed that it is intended to produce a LDM but that this would be though the auspices of the PNUNC work stream and not through the Data Management s. The asked about the intended input to the s. AC confirmed that the intention is to produce appropriate Strawmen as input that will be considered by attendees and amended / enhanced as agreed and in line with the agreed Scope. The then asked what subject matter was to be considered at each of the s. AC explained that it depended to some extent on the outcome of today and the number of Scenarios and Options agreed to be further developed (see section 6). 2

3 The asked if would be able to say anything about the cost of implementing options. AC stated that the Data Management s would not result in providing cost estimates for the scenario / option combinations taken forward. RS Suggested using high level options/preferences/principles and how to apply them costs will come with this (NOT SURE ABOUT THIS MAYBE SW CAN REMEMBER HOW WE REACTED?) The asked whether benefit assessments would be qualitative or quantitative. AC confirmed that they would largely be assessed on a qualitative basis and explicitly that there d be no quantification of cost benefits but that some quantitative assessment would be desirable for operational benefits (e.g. attempt to quantify the extent existing problems and the likely improvement realised by changing the Data Management arrangements). Statement of Scope The identified that: points (a) and (b) under The consideration should include (section 6.4 on page 21) are the same; the second list of points in section 6.5 duplicates the references used for the first list; under section 6.5, Shipper Emergency Contact Details data is already collected and centralised with. It was agreed that this is more to do with providing a value added service; There should be a catch-all point for capturing additional data identified during the s (examples cited included Special Needs, Wet Gas and Shipper to Transporter communication). s Terms of Reference AC asked the which additional industry role should be invited to the subsequent workshops. It was agreed that until there was a better understanding of the options that were being further considered the parties invited should continue to be Transporters and Shippers/Suppliers, Ofgem and DECC. It was further agreed that extending the attendance should be left to s judgement / discretion. The requested that SMART metering roll out and its impacts should be included in section 7.1. (Post meeting note: The intention is that the objectives be applied in conjunction with the Scope detailed in Section 6 which includes references to Smart Metering impacts). There was concern that until there s more clarity around the Smart Metering Market Model and its implications that it might be difficult to determine the degree of support for a given Data Management requirement or concept. It was agreed that the wording should address this possibility. 4. Review Project Nexus Initial Requirements Register AC advised that each entry in the Initial Requirements Register (IR) had been assessed to identify the following: Outside DM requirements scope but inside data scope (in UNC scope) In UNC scope on a process by process basis not a specific topic group (outside DM scope) Design / Solution and not Requirements phase (outside DM scope) 3

4 In DM scope (outside UNC scope) In UNC scope (outside DM scope) Notes and Actions from the Project Nexus In DM scope from a principles perspective but not at the detai8l (in UNC scope) In DM scope from a principles perspective but not at the detail (in UNC scope on a process by process basis but not a topic) In DM scope from a principles perspective but not at the detail (outside UNC scope) Outside UNC and DM scope It was agreed that a revised version of the IRR, highlighting the above, should be published. AC took the through each entry in the document, stating which category each entry fell under. Discussions around the document were as follows:- Supplier Switching AC stated that this topic will get addressed at the PNUNC work stream with Dual Fuel being included within the Data Scope but outside the Requirements Scope for Data Management. There was some debate about recent EU requirements regarding Supplier Switching and that they may impact SPA and system requirements and that it may fall within the Data management remit. AC reiterated that the Data Management s will investigate high level requirements / principles and responsibilities around where and how data is held, validated, and shared. SW confirmed that the detailed changed to SPA processes will be addressed in the PNUNC work stream using the output from the Data Management s as guidance in relation to how the data is managed. Market Differentiation Connection & Registration Increased Reads for Energy Allocation, Balancing and Transportation Charging Reconciliation AQ Management Volume Capture Invoicing Rules Treatment of Retrospective Updates AC commented there are a lot of data implications here, but all at the detail level to be addressed in the PNUNC work stream. Other The requested that an additional sub-topic of Vulnerable Customers to be added to the IRR. The requested that the entry under 10.2 from Shell Gas Direct needs to be included within a further sub-topic of Bad Debt Risk 4

5 There was some debate about whether 10.9 should be included in Data Management scope. It was agreed that it will be picked up by the PNUNC work stream but would be outside the scope of the Data Management s. Data Management - Data Hub The asked whether be tracking items that are within the scope of the DM s. AC confirmed this to be correct. It was agreed that extra columns would be added to the IRR to aid traceability. The workshop asked whether a process been recently undertaken to identify the differences between what s defined in Market Domain Data (MDD) and what holds. AC agreed to determine if such an exercise had been undertaken. It was agreed that 11.7 should be amended to be In DM scope from a principles perspective but not at the detail (in UNC scope on a process by process basis but not a topic).. Data Management Quality Assurance Data Management Exchange and Flows of Data It was agreed that 13.13, 13.18, and should be amended to be In DM scope from a principles perspective but not at the detail (in UNC scope on a process by process basis but not a topic). It was agreed that should be amended to be In DM scope from a principles perspective but not at the detail (outside UNC scope). It was agreed that it is inappropriate for this to be included in the IRR. (Having read the detail I m not convined that this is correct) Data Management Central Data Store for Smart Metering Data AC asked BD to provide some clarity regarding 14.3 before deciding how this should be categorised. It was agreed that 14.5 should be amended to be In DM scope from a principles perspective but not at the detail (in UNC scope on a process by process basis but not a topic). igt AC advised that the entries listed under the igt topic are currently not in scope and awaiting further clarification and guidance from the SPAA work group. 5. Smart Metering Market Models / Implications of DECC s announcements of 11th May 2009 There was some discussion about the DECC announcement with the opinion being that while it and the next 3 months will give some background and confirm stakeholder views, it s unclear how much more detail and clarity can or will be provided although there was a view that DECC will issue policy guidelines showing what can/cannot be done with regard to Data privacy and Data access. There was further debate about what Data Management can / cannot do with regard to Smart Metering implications. It was agreed that the Data Management s will be looking to establish high level principles for a solution and that the principles should remain consistent regardless of is the parties involved. The pointed out that the Smart Metering roll-out will be ongoing until the year The impacts on Nexus could be significant depending on how both Smart Metering and Project Nexus are delivered. 5

6 It was agreed that, for the purposes of the Data Management workshops, the Smart Metering Market Model proposed in DECC s latest announcement should be used as the basis for assessing the potential impacts of Smart Metering. 6. Review Data Management Scenarios & Options document AC advised that all Scenarios and Options had been reviewed internally and assessed against the Data Management themes listed on pages 9 and 10 of the Scenarios and Options document. This assessment formed the basis of options to be further progressed. The felt that there was insufficient clarity regarding the various Scenarios and Options and that more work needed to be undertaken before the options to be further developed could be determined. It was therefore agreed that for each of the options within the document, should create a diagrammatic and verbal description for the following processes:- Meter Asset Detail maintenance; Meter Reading; Supply Point Transfer (Change of Supplier). It was further agreed that each should also highlight the potential implications of DECC s proposed Smart Metering Market Model. The revised descriptions will then be used to run the first workshop at which attendees would identify those that should be further investigated. The requested that the revised Scenarios and Options document should be made available 10 working days before the first. 7. Next Steps Revise the Data Management Definition document as agreed during the and issue as a final draft on 27 th May 2009; Issue notes and actions from this on 27 th May 2009; Publish a revised version of the IRR; Amend the plan to reflect the revised approach agreed during the, including: o the additional work required to describe all the scenarios and options as agreed; o a 10 working day review period for the revised Scenarios and Options document the review period to have concluded before running the first ; o a 10 working day review period for documents detailing the outcomes the review period to have concluded before the subsequent ; Revise the Scenarios and Options document as agreed It was also agreed that invitations to subsequent s should be issued to the attendees of this (for the organisations represented). 6

7 Summary of actions arising Discussion Action Advocator Owner Status update Definition Document Publish Data Management Definition document on the website. Definition Document Definition Document Initial Requirements Register Initial Requirements Register Initial Requirements Register Amend the document as agreed during the and detailed in the notes above. Revise the planned dates for the s based on the outcome of the. Amend the document as agreed during the and detailed in the notes below. Publish a revised version of the Initial Requirements Register showing the scope categorisation. Provide some clarity regarding IRR entry AC BD Scenarios and Options Re-draft the Scenarios and Options document as described in the notes above. 7