This deliverable will contain a set of documents including analysis based on first input from SP and related Fas (e.g., regarding demonstrators) and definition for relevant use cases, operational parameters and scenarios in scope of passenger/freight/inspection vehicles and tramway applications.

This deliverable contains all the requirements specified and consolidated in the task 19.1.

This deliverable will contain a report about actual existing and specified automated functions, tasks or related use cases with annotated target component as scope, a draft release for set of documents including analysis based on first input from SP and related Fas (e. regarding demonstrators) and definition for relevant use cases, operational parameters and scenarios in scope of passenger/freight and tramway applications.

Requirements (in collaboration with FA1 WP 8/9 and 15/16) for capacity simulation tooling and methodology (like development of Train Path Envelopes for ATO operations) to measure the potential impact of ATO/TMS C Das technology.

Requirements and use cases for development, engineering, commissioning, maintenance and refurbishment in the context of DevOps and architectural evolution.

Report on the applicability of approaches on evolvability from other domains, e.g. IT systems.

Requirements including existing ones for OSI layer 1-6 on communication functionality of Onboard Communication Network and Basic Services.

Concrete candidates of technologies for OSI layer 3 6 and for assoc. basic services

This deliverable will contain a set of documents defining user freight specific user requirements for all automation process subproject tasks e.g., automatic functions, ATO GoA 3/4 specification, safe perception system and remote driving.

This deliverable will contain a set of documents defining harmonized urban use cases and operational rules for all automation process subproject TE.

Use cases from the perspective of all relevant stakeholders ( sub system suppliers, railway undertakings).

In this report, it will be described how prior and ongoing activities on FRMCS and ACS relate, how a maximum extent of synergies among the concepts can be leveraged in the remainder of this WP, and how ACS concepts going beyond the FRMCS architecture and functionality can prospectively be integrated into the FRMCS system.