Location. Chair / Minutes. Network Rail Attendees Darrell Sikora-Smith (DSS) (Chair)

Transcription

1 Meeting Name: UK TAF Senior User Group (SUG) Time Tuesday 5 th December 2017, 14:00 15:00 Location Chair / Minutes Via Conference Call Darrell Sikora-Smith (Chair) Marcel Potter (Minutes) Attendees Network Rail Attendees Darrell Sikora-Smith (DSS) (Chair) Business Design Authority Status Attended Julia Lawrence (JL) Programme Manager Apologies Will Deakin (WD) Programme Design Authority Attended Peter Beevers (PB) Subject Matter Expert Apologies Andy Ashill (AA) Project Manager Attended Jason D Arcy (JDA) Enterprise Architect Apologies Marcel Potter (MP) (Minutes) PMO Attended External Attendees Mark Wallis (MW) DB Cargo (UK) Ltd (Active) Attended Carl Gager (CG) DB Cargo (UK) Ltd (Active) Attended David Brooke (DB) Freightliner (Active) Norman Egglestone (NE) Direct Rail Services (Active) Apologies Gareth Houghton (GH) Neil Sime (NS) Colas Rail (Active) Victa Railfreight (Active) Alfredo Giangregorio (AG) GB Railfreight (Active) Attended Alex Sprott GB Railfreight (Active) Apologies Eric Aliot (EA) HS1 (Informed) Apologies Richard Thorp (RT) HS1 (Informed) Apologies Page 1 of 6

2 Minutes / Actions / Decisions Item Description Action / Decision 1 Introductions DSS welcomed all attendees to the meeting. The meeting was rescheduled to an hour later from 14:00 15:00 due to the availability of participants. It was noted that with only two FOCs in attendance (DB Cargo & GB Railfreight) that the meeting was not Quorate in accordance with the proposed Terms of Reference. It was agreed to proceed with the meeting and then request that those Members not present agree to the draft Minutes and Decisions via . The meeting will then be declared Quorate on that basis. (See also Agenda Item 3. below). 2 Previous SUG Meeting DSS refereed to p.3 of the Meeting Pack and provided a brief re-cap of the key points and decisions from the last Senior User Group (SUG) meeting held on 26 th September In particular: TrainID and OTN proposals outlined and agreed at the extraordinary SUG held 14 th September were agreed at the meeting on 26 th September, and further endorsed by the UK TAF TAP Steering Committee on 9 th October The NR Train Running project and Train Preparation requirements are merging into a new project called Train Operations Analysis of the Locations data and solution is still ongoing; however an update will be provided under Item 5. below Decisions: o The output of the final RMC meeting on 11 th May 2017 was agreed o The TrainID and OTN proposal endorsed on 26 th September was agreed as being a true reflection of the discussions held and the agreement reached o It was agreed to hold the next SUG meeting on 5 th December The Senior User Group agreed the output from the SUG Meeting on 26 th September Senior User Group Terms of Reference DSS said that the Terms of Reference have been updated to reflect the change from Requirements Management Committee (RMC) to Senior User Group (SUG), and also to reflect the change from requirements gathering and solutionising to delivery. The proposed Terms of Reference will be attached to the meeting Minutes for approval ahead of the next meeting. It was agreed to attach the proposed Terms of Reference along with the meeting Minutes, for approval via ahead of the next meeting Page 2 of 6

3 4 New TAF TAP Programme Scope DSS referred to p. 5 of the Meeting Pack, and outlined the key changes to the NR Programme scope: The TAF TAP Programme is now part of the Route Service IT Digital Rail Portfolio Train Running and Train Preparation requirements have now been merged into a new Train Operations Project Train Consist & Train Ready messages have been moved from the scope of Path Management to the new Train Operations Project The DfT has requested NR continue in its co-ordination and European influencing roles, as it is important that we continue to shape and influence the direction of the TSI s while the UK is still and EU Member State The Programme will continue to support the Wagon Keeper briefing An Operations Data Store will be implemented for certain messages TAF implementation will still act as an enabler for activities such as the TOPS replacement, and also deliver scalable platforms to allow the addition of TAP messages as/when required. The key change in scope is that Path Management activities under the NR TAF TAP Programme have ceased, and the baselined design and requirements artefacts are being handed over to the System Operator to implement in CP6. In addition, two additional Passenger messages adopted by the sector that are not part of the TAF and TAP regulations (Journey Modification & Change of Track) will be delivered by a separate project within the RS IT Digital Rail Portfolio (these messages do not impact freight). These scope changes were provisionally agreed at the UK TAF TAP Steering Committee meeting on 9 th October, with the caveat that the committee wanted additional confidence that the System Operator has accepted the Path Management obligations into its roadmap, and a plan for when these would be implemented. MW agreed that this additional confirmation is required to give confidence that the obligations (which are a legal requirement) will be implemented, if not by the TAF TAP Programme, then by another part of NR. MW requested (in his role as UK TAF NCP) a contact name from the System Operator to act as a named contact point, and asked whether the System Operator will report progress at the UK TAF TAP Steering Committee. DSS confirmed that meetings have taken place with the System Operator and the key design and requirements artefacts are due to be handed over at a further meeting next week. He also noted that the System Operator is very keen to implement Electronic Bid/Offer; however we will not be in a position to strongly influence the System Operator implementation or timescales. NR to confirm a Point of Contact in the System Operator to MW as the UK TAF NCP, and confirm whether the System Operator will report progress to the UK TAF TAP Steering Committee. DSS07 Page 3 of 6

4 MW also requested that the Programme assist in communicating to the other UK IMs, FOCs and Wagon Keepers regarding the JSG reporting requirements. It is now the responsibility of each company to report on its own behalf (to date only NR and DB Cargo UK have reported to the JSG). This will require a list of contact details to be agreed and passed to the JSG to enable them to issue invitations to report, and communications to those companies who might expect to receive them. DSS said that the Programme already has a fairly comprehensive contact database based on publically available information (from sources such as the ORR). We will work with MW to agree the contact list and any communications to be issued, which NR agreed to issue on behalf of MW as the UK TAF NCP. NR to work with MW to agree the contact list for JSG reporting, and any communications to be issued to those companies who would be expecting to receive them DSS08 NR agreed to issue communications around the new JSG reporting requirements from the existing TAF TAP mailbox, on behalf of MW as the UK TAF National Contact Point (NCP) Locations Update WD said that the general points around the proposed Locations approach had not changed since previously agreed (please refer to p.6 of the Meeting Pack). However since then, further analysis has been undertaken and actions taken to move forward. In particular: The Common Interface and CRD feed is now live The CORPUS system CRUD processes have been defined and agreed with the NR Systems and Data Team The updated CORPUS user guide and process document are currently with the Systems and Data Team to formally sign off WD noted that the user guide and process document will be circulate in the New Year once formally signed off, but essentially the existing process will continue. MW said that DB Cargo has since identified that Freight Locations are not the only locations used for example Charter Trains and asked how these gaps would be filled. WD said that the process would be robust and would enable changes to be made to the database for example using the existing update process or via bulk upload. MW agreed to review the process document when received and then analyse the likely scale of any locations gaps. If required, a meeting will then be arranged for early next year to decide on the size of the issue. NR to forward the updated CORPUS user guide and process document to WD09 Page 4 of 6

5 SUG Members in the New Year once signed off by the NR Systems and Data Team. MW to review the updated CORPUS user guide and process document and analyse the likely scale of any locations gaps, and confirm to NR (a meeting will then be arranged as required). MW10 6 European Update WD provided an update on recent European meetings (p.7 of the Meeting Pack). In particular, he noted: RISC approved the rolling up of a number of changes as a formal legal document and issued as Baseline v2.2. This has required Member State approval. The proposed changes roll up all to approved activities to March 2017 including the Common Interface specification and changes to the CI xml interface (approval likely in March 2018) Path Pilot Kick-Off NR will have Observer status ERA TAF Co-operation Group (October) discussions focused on TAP existing systems exemption and the concept of soft compliance the next meeting will review the definition of soft compliance following a working party that is scheduled to meet ERA in January 2018 Common Components Change Control Board (October) At the CCB RNE announced that they will move the hosting of their CI and CRD installation from a datacentre in Sweden to Austria over the Christmas period. The old SSLs will be revoked in June 2018 SMO meetings (November) a number of change requests were discussed alongside TTR (the timetabling re-design project in which the UK is not involved) and VSTP via electronic messages The recent JSG Meeting discussed the Sector Handbook, updates on new Change Requests and TTR. The 7 th EU progress reporting timetable was also agreed. 7 Programme Update DSS highlighted the key update since the last meeting is that the Common Interface went live as planned in October, which meets one of our key target Implementation Dates for the UK. He also highlighted the rationale for the creation of the new Train Operations Project, and confirmed that the baselined Path Management artefacts will be transferred to the System Operator next week. Key progress for the last three Periods, and planned activities for the next three Periods is shown on pp of the Meeting Pack. 8 Next Senior User Group DSS suggested holding the next meeting in March 2018, and this was agreed. Suggested dates will be circulated with the meeting Minutes and invites then issued once the most suitable date is agreed. It was agreed to hold the next Senior User Group meeting in March Page 5 of 6

6 NR to circulate suggested dates for the March 2018 SUG with the December meeting Minutes and issue invites once the most suitable date is agreed. MP11 7 AOB and close The following AOB was raised: MW said that DB Cargo are in discussion with RNE about installing the Common Interface in the next few weeks, and asked whether NR would be willing to assist in their testing, and NR agreed that this would be very beneficial to both parties, and assist in proving compliance. MW to liaise with WD and AA on Common Interface Testing. CG raised a concern that the good progress and engagement on TAF TAP to date may be lost if the NR Programme is part of the wider Digital Railway agenda where he believes that the freight community has seen little tangible benefit to date, and little traction on issues such as ERTMS or corridor management. He also raised a wider concern on how the freight community should engage with NR, now that the Freight Technology Group (FTG) has ceased. AA confirmed that the Digital Rail Portfolio sits within Route Services IT it is not part of Digital Railway (i.e. the programme has just moved from one internal Route Services IT delivery portfolio to another). WD also confirmed that TAF TAP still has assigned core resources in place, and that the SUG will still continue to review progress and delivery of TAF. However it was noted that the programme has no wider remit to reconstitute the FTG. DSS thanked everyone for their attendance and the meeting then closed. Next Meeting: March 2018, tbc Page 6 of 6