WP1

D1.1 State-of-the-Art Document (submitted: December 2016, M03) -- [DOWNLOAD PDF]
D1.1 describes state-of-the art in integrated system development and Ethernet networking technology in aerospace and automotive industry, and provides a general high-level technology baseline required for design of advanced integrated architectures.

D1.2 Initial System Integration Requirements Document for Next-Gen TCMS (submitted: March 2017 – M06) -- [DOWNLOAD PDF]
D1.2 collects all initial system functional, safety and performance requirements related to system integration, required for the design of next-gen TCMS. It also includes the rationale for use cases and configuration scenarios for integrated TCMS architectures.

D1.3 Initial Drive-by-Data Draft Concept (submitted: March 2017 – M06) -- [DOWNLOAD PDF]
D1.3 describes the draft concept of design and methodology for next generation TCMS.

D1.9 Final Drive-by-Data Concept Design (due date: September 2018 – M24)
D1.9 describes the concept of design and methodology for next generation TCMS including all relevant technologies and open issue/gap analysis.

WP2

D2.1 Report on state-of-the-art of 'functional distribution architecture' frameworks and solutions (submitted: December 2016, M03) -- [DOWNLOAD PDF]
Describes the state-of-the-art of representative functional distribution architectures, including existing solutions from other domains (automotive, avionics).

D2.2 Report on analysis of 'functional distribution architecture' frameworks and solutions (submitted: April 2017, M07) -- [DOWNLOAD PDF]
Contains the results of analysing the feasibility of COTS frameworks and solutions for the deployment of next generation TCMS systems and the gaps to overcome.

D2.3 Report on 'TCMS framework concept' design, security concepts, and assessment (due date: December 2017, M15) -- [DOWNLOAD PDF]
Provides the proposed 'Safety concept' and 'Security concept' for the 'TCMS framework'. Describes the proposed 'Design concept' for the 'TCMS framework', considering both 'safety and security' concepts. Summarizes the conclusions obtained from the reviewing and assessment activities of the 'TCMS framework concept'.

D2.4 Report on TCMS framework instantiation (due date: March 2018, M18) -- [DOWNLOAD PDF]
Describes the design instantiation in AUTOSAR of the 'TCMS framework' design concept. Characterizes the design instantiation in mixed-criticality hypervisor / multicore of the 'TCMS framework' design concept, taking into account ARINC653 capabilities. Describes the design instantiation in RTOS of the 'TCMS framework' design concept.

D2.5 Report on requirements of next generation TCMS framework (due date: September 2018, M24)
Elucidates the set of requirements for next generation TCMS frameworks, considering safety and security aspects.

WP3

D3.1 Report on state-of-the-art analysis and initial requirements for distributed simulation framework (submitted: December 2017, M03) -- [DOWNLOAD PDF]
Describes the state-of-the-art of distributed simulation frameworks including existing solutions from other domains (e.g., automotive, avionics). In addition, the deliverable will contain the initial requirements for the concept and proof-of-concept implementation of the S4R simulation and validation framework.

D3.2 Report on design of TCMS distributed simulation framework concept (submitted: July 2017, M10) -- [DOWNLOAD PDF]
Elucidates the high-level distributed simulation framework concept supporting efficient co-simulation at different sites, SIL/HIL testing, mechanisms for observation of messages, remote testing and fault injection.

D3.3 Report on design of T2G Test Environment (submitted: July 2017, M10) -- [DOWNLOAD PDF]
Delivers a concept of a simulation environment for the validation of TCMS interfaces to ground systems including testing of compliance to relevant railway standards.

D3.7 Evaluation results, conclusions and further recommendations, including derived requirement recommendations for drive-by-data and embedded platform (due date: September 2018, M24)
Contains the evaluation results and conclusions, which are established using test-cases in the simulation and validation environment including TCMS and the train-to-ground interfaces.

WP4

D4.1 Requirements definition for Brake by Wire (submitted: December 2016, M03) -- [DOWNLOAD PDF]
This deliverable contains the collection of information necessary for the definition of requirements. A first iteration of brake system and electronic control and communication requirements will be provided. Standard and technologies applied in other transport sector and suitable for use (or as reference) for railway “brake by wire” systems will be likewise addressed.

D4.2 Final requirements definition for Brake by Wire and safety concept (submitted: October 2017, M13) -- [DOWNLOAD PDF]
Gathers the final requirements for brake system and for electronic control and communication, as well as a thoughtful risk analysis and verification plan. Last but not least, a technical and safety concept for brake systems will be presented. D4.2 will connect with the communication requirements specification for the safety Ethernet infrastructure (TCMS) from WP1.

WP5

D5.2 Initial report and updates on dissemination, exploitation and standardisation activities (submitted: September 2017 – M12) -- [DOWNLOAD PDF]
This deliverable will include a record of activities related to dissemination and exploitation that have been undertaken and those still planned as well as a report of completed and planned communication activities.

D5.3 Final report and updates on dissemination, exploitation and standardisation activities (due date: September 2018 – M24)
This deliverable will include a record of activities related to dissemination and exploitation that have been undertaken and some going beyond the project lifetime as well as a report of completed communication activities.

WP6

D6.2 Risk Assessment Plan (submitted: September 2017 – M12) -- [DOWNLOAD PDF]
The risk assessment plan shows how potential risks are assessed and mitigated in order to avoid any negative influence on the SAFE4RAIL project objectives. The interrelated risk assessment plan – risk identification, handling and monitoring – will be established.