Euro-Interlocking Handover Workshop

Transcription

1 Euro-Interlocking Handover Workshop Handover To INESS Emmanuel Buseyne, PM INESS Paris 30. May 2008 Euro-Interlocking 30. May Content 1- Summary of the current situation 2- INESS objectives 4- Implementation of El outputs into INESS 5- Role of Umbrella Railways Euro-Interlocking 30. May

2 1- Summary of the current situation European Context - Different signalling systems in Europe (about 20) - Different ETCS levels (1, 2 or 3) - No European harmonised interlocking functional requirements and design - Different interlockings and ERTMS migration plans and strategy - No harmonised signalling rules Euro-Interlocking 30. May INESS objectives Main objectives - define a common kernel of validated standardised functionalities for future interlockings, including functionalities specially required by ERTMS Level 2 and Level 3 ). - propose one or more standardised system architecture(s) and the relevant functional interfaces between the interlocking and the adjacent subsystems optimised for ERTMS Level 2 and Level 3. -develop a common business model and the associated business cases and cooperation models to support intelligent migration strategies for ERTMS -define standardised and optimised methods and tools for requirements management and for verification and validation. Euro-Interlocking 30. May

3 2- INESS objectives Workstreams zoom in Euro-Interlocking 30. May INESS objectives ERTMS into the general process developpement Functional requirements capturing ERTMS Simulation & modelling System design Functional architecture Testing & Commissioning Safety case process Euro-Interlocking 30. May

4 European Context INESS the forthcoming challenge for the signalling industry UIC and UNIFE have jointly prepared an application for a project Integrated European Signalling System INESS to be supported with about 10 M by the EU in the 7th Framework Programme for Research & Development. About 30 parties from railways, industry, universities and others are participating under co-ordination of UIC. Euro-Interlocking 30. May EC Legal Framework General flowchart Third Parties Impact Budget Contrat EC P.O. Ressources Project Objectives Deliverables Use Time External Audit Euro-Interlocking 30. May

5 EC Legal Framework From the negotiation to the end of the contract Negociation EC decision Contract signature Contract execution End of the contract Euro-Interlocking 30. May EC Legal Framework Roles European Commission TAB Consortium GA SB Manage ment team (plateforme) Management activities Les rôles dans le projet Background ressources Coordinator WS WS WS WS WS WS Results - deliverables impact Foreground- Dissemination Beneficiaries WS Leader Subcontractors Third Contractors (WP) New contractors Euro-Interlocking 30. May

6 EC Legal Framework Contract structure Contract Annex 1 = DOW Annex 2 = General conditions Annex 3 = Specific conditions of the financial scheme Annexes 4, 5 and 6 = Accessions and financial statement Annex 7 = Audit and methodology certificates + Consortium Agreement = based on DESCA model Euro-Interlocking 30. May EC Legal Framework Project Reporting 0 Y 1 Y 2 Y 3 Time Milestones and deliverable lists R1 R2 R3 R4 R5 R6 Every 6 months -Progress of the work -Use of resources -Financial statement At the end -Final publishable summary report -Plan for the use and dissemination of foreground Euro-Interlocking 30. May

7 Management structure and procedures STRATEGIC L LEVEL OPERATIONAL LEVEL Assistance PROJECT MANAGMENT OFFICE (PM, UIC, ALMA) Day-to-day management Support, Quality plan, templates, Guidelines EUROPEAN COMMISSION Intermediation INESS COORDINATOR UIC STEERING BOARD (UIC, NR, DB, BV, ADIF, UNIFE(6 Representatives), PRORAIL, RFI + invited : PM and 1 University ) Strategic orientations and Assistance methodologies with regard to INESS PROJECT MANAGEMENT COMMITTEE (Leader/responsible: INESS Project Manager + WS Leaders) Bottom-up: Project progress information Intermediation WS LEADERS Top-down : Directions To check the compliance of the technical content of project s deliverables with th e defined Quality policy and Quality Plan TECHNICAL ADVISORY BOARD Project Manager+Experts from partners for review WS PARTNERS Euro-Interlocking 30. May Management structure and procedures Management bodies responsibilities Organisation & direction of the consortium,strategic decision making & resolution of conflicts Administration, contractual and financial matters Technical coordination & monitoring Dissemination, Exploitation, Training and communications strategies implementation Project impact and performances measurements, active quality check policy and outcome endorsement Management of knowledge Euro-Interlocking 30. May

8 Day to day management - Constraints SCOPE QUALITY COST TIME Euro-Interlocking 30. May Day to day management - Tasks Managing the delivery and the follow-up of administrative and financial documents Being a permanent contact point for the Coordinator and all the partners regarding their participation in the project, responding to any relevant requests Easing the Coordinator of administrative tasks/notifying the consortium of due dates Preparing the official meetings Following up of actions and decisions Managing the possible changes in the Consortium Agreement Set a common working and reporting tools Following and updating the project indicators (Gantt chart, man power matrix, deliverables list) Euro-Interlocking 30. May

9 Deliverables Actual * Intermediate Month Planned Year 1 Year 2 Year 3 * Final Start End WPs / Tasks WS A - PROJECT MANAGEMENT 1 36 WP.A.1 - Project management 1 36 WS B - BUSINESS MODEL 1 36 WP.B.1 - Value Chain and Life Cycle Model 1 12 WP.B.2 - Target costs for interlocking devices 1 15 WP.B.3 - LCC reduction WP.B.4 - Business model WP.B.5 - Business case and Cooperation Plan WS C - SYSTEM DESIGN WP.C.1 - File Format Definition WP.C.2 - Design Tool Definition WP.C.3 - User to Supplier Linkage Definition and Asset Management WP.C.4 - Data Flow Requirements WS D - GENERIC REQUIREMENTS 2 36 WP.D.1 - Generic requirements guidelines 2 6 WP.D.2 - Common kernel functional requirements 2 20 WP.D.3 - Elaboration of ERTMS requirements WP.D.4- Validation and verification of functional requirements 3 36 WS E - FUNCTIONAL ARCHITECTURE WP.E.1 - Collect information from relevant state of the art projects WP.E.2 - Identification of the typical functional structure of interlockings and their adjacent WP.E.3 - Apportionment of function and production of interface specification WP.E.4 - Trackside Migration and feedback issues WS F - TESTING AND COMMISSIONING 1 24 WP.F.1 - System structure Testing and commissioning model (based on EN 50129) 1 5 WP.F.2 - SoA Railways T&C (including cross-acceptance) 3 12 WP.F.3 - SoA T&C Tools used 4 12 WP.F.4 - CBA (as request and then input for WS B) WP.F.5 - Test scenarios for generic products (link with WS D) WS G - SAFETY CASE PROCESS 1 36 WP.G.1 - Safety Case Process Appraisal 1 5 WP.G.2 - Safety Case Process Strategy Development 5 12 WP.G.3 - Methods and Tools for Modelling 1 13 WP.G.4 - System and Software Specification For Tool Support 7 19 WP.G.5 - Tool Implementation, Verification and Validation WP.G.6 - Safety Case Support Tool Evaluation WS H - DISSEMINATION /TRAINING 1 36 WP.H.1 - Dissemination of knowledge 1 36 WP.H..2 - Exploitation of Results WP.H.3. - INESS Training & Coaching Day to day management - Objectives Guaranty the delivering of the outputs Facilitate the communication and work between partners Ensure a practical and further (after the project) use of the outputs Establish a good financial and technical follow-up of the project through judicious use of indicators Establish a quality control system Disseminate and demonstrate the quality of the project inside and outside the consortium Euro-Interlocking 30. May Day to day management - Tools Project quality plan (to do M1 and M2) Internal consortium organization Decision mechanisms Communication plan Workplan consortium budget Risk management Preliminary scope statement GANNT to follow the production of Deliverables and milestones Jan Feb Mar Apr May Jun CALENDAR - GANTT (36 MONTHS) Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Euro-Interlocking 30. May

10 Day to day management - Objectives Guaranty the delivering of the outputs Facilitate the communication and work between partners Ensure a practical and further (after the project) use of the outputs Establish and ensure a good financial and technical follow-up of the project through judicious use of indicators Establish a quality control system Disseminate and demonstrate the quality of the project outside the consortium Euro-Interlocking 30. May Implementation of EL outputs to INESS Brainstorming items regarding to El processes How many railways should be tagged in order to guaranty a relevant study? How can we estimate the appropriate size of the common core considering ERTMS? Should the FR be considered regarding to National or European Safety rules? Can the simulation process be implemented with or in an ETCS simulator? Do we have a mean to evaluate the accuracy of the actual (and latter) data capturing and validation technology? Is there no other available fitting simulation platforms? Most of the answer are I do not know. There is thus an unexplored field, INESS will have to investigate. Euro-Interlocking 30. May

11 4- Implementation of El to INESS Key elements to analyse these items Consensus between the railways, and between the railways and industries to accept or reject new functionalities in their signaling systems or principles. Ensure coherence with the business model. The Safety Case should consider an ERTMS environment. Build the model (system design and functional architecture) considering. Follow the guidelines of the CENELEC (EN50126 and 50129) norms and the TSI CCS. Euro-Interlocking 30. May Implementation of El to INESS Proposed methodology PM with WS leaders (PMC) meet in (1 or several) workshops to define relevant El outputs and an extended list of questions like the one before PMC actors establish a list of relevant EL items for WS D and determine the methodology plan to fulfill it WS leaders analyze the possible impact on their work program (WS and WP) WS leaders possibly reevaluate the scope of their WS regarding to these new inputs and readjust their WS and work program Individual (/WS) and general GANNT will be redesigned Euro-Interlocking 30. May

12 4- Implementation of El to INESS Relevant item example : how to capture and simulate ERTMS function in WS D 1. Determine the ERTMS functions which are or could be linked to Il s functions like for example : overlaps, end-section timeouts, LOA, border functionalities 2. Identify the FR bound to these functions 3. Extend the CC 4. Simulate theses functions on Cassandra platform choosing a relevant infrastructure configuration 5. Simulate on ERTMS simulator the same functions considering the same infrastructure configuration Euro-Interlocking 30. May Role of the Umbrella railways Definition Railways participating under the Umbrella of the UIC. These railways are: JBV (Norway Railways), PKP (Polish Railways), REFER (Portuguese railways), BD (Danish railways), RHK (Finnish railways), ÖBB (Austrian railways) and SBB (Swiss railways). They have been selected for their world class expertise in CENELEC processes, and in their compatibility of skills regarding to every WS. They have an real interest in developing common FR for implementing their networks. Euro-Interlocking 30. May

13 5- Role of the Umbrella railways Role Contribute to the Interoperability of the European railways Represent all the railway value chain Help to define common functional requirements, architecture and interfaces for the future signalling systems considering the framework of their operational principles Others Estimated total MM is 11 Not involved as direct partners in the project Euro-Interlocking 30. May Thank you for your attention Euro-Interlocking 30. May