Regional lines, like main lines, benefit from the introduction of ATO systems. The introduction of the ATO system can effectively reduce operating costs and can contribute to reduce overall infrastructure costs. The solutions explored in the present document are the introduction of ATO Grade of Automation 2 (GoA2) up to Grade of Automation 4 (GoA4) for regional applications. There are many similarities with what is applied on main lines. Since the same trains can circulate both on main lines and on G1 regional lines, interoperability must be guaranteed. The use of the ATO over ETCS signalling system is a must that has guided the integration of the solutions in the regional context. This report covers use cases for G1 regional lines that allow automation of train operation on low-traffic lines with moderate speeds. The ATO functionality developed is using ERTMS/ETCS as a platform. The report specifies several use cases and technical requirements that ATO must meet to improve performance and overall economic sustainability of regional lines. Subsequently, various grades of automation applicable were analysed. Grade of Automation is studied from GoA2, where a train driver is responsible for starting automatic operation and can intervene and manually drive the train in certain circumstances, to GoA3 which is driverless but with at least one train attendant on board. The on-board staff can handle doors, external and internal communication, facility issues and evacuating passengers if necessary. In GoA4, in which the train operates completely without on-board staff, start, stop, and operation of doors are performed completely without driver and train attendant. However, as a fallback system, the train can be operated by a remote operator (in conformity with GoA3). The use cases identified are particularly useful for regional lines. The present document constitutes the main outcome of FP6 WP3 Task 3.1 (Regional Rail CCS & Operations for G1 Lines Requirements & Specifications), which forms the basis for the demonstration campaigns to be performed by FP6 WP8 Task 8.1 (Development of individual demonstrator ATO GoA2 on G1 regional lines) and Task 8.2 (Development of individual demonstrator ATO GoA3/4 including perception and remote driving on G1 regional lines) during the second half of the project.

Regional railways play a significant role, not only in serving rural areas in Europe, but also acting as feeders for passenger and freight traffic for the main network. Regional railway lines have an essential function as an environmentally friendly mode of transport. In combination with other public transport services, such as bus, micro mobility services, on-demand services, as well as cycling, walking, and driving, regional rail enables passengers to reach remote stations and places in rural areas. To ensure the long-term viability of regional railways, among other factors, a high service quality and high customer satisfaction are required to make rail an attractive and preferred mode of transport. Regional rail services play an important role in achieving a high customer satisfaction. Every day, passengers rely on regional trains and other regional services for transportation. The key, not only to accomplish customer satisfaction, but to also increase service quality, reliability, and efficiency, is a sophisticated information service. The societal significance of a smoothly running rail service stems not only from railways being an important part of the infrastructure in many European countries, but also from the need to live, trade and travel more sustainably. Within FP6-FutuRe WP6, a highly accurate multimodal travel solution is developed. The goal is to deliver transport service information for first and last mile services, while including passenger transportation and partly combining it with freight transportation. The service information shall be supplied both on-board of regional vehicles, e.g. via personal digital devices, and at regional rail stations. In rural areas with mostly low density of rail services, travellers need to be able to proceed with their journey once they have reached their final railway station. To cater to this need, in this deliverable D6.1, a solution is specified that can inform passengers about which mode is suitable to reach the final destinations. It is considered that there might be delays or other incidents that affect a transport services’ operating schedule and that some travellers may have specific mobility restrictions. Interfaces between rail services and other mobility services, such as demand responsive transport, are helpful to adjust to different scenarios and to operate as efficiently as possible. A possible solution is developed in collaboration of several tasks within WP6 as well as in exchange with FP1-MOTIONAL. The present document explains the Alpha Release outline of our solution, as well as the scope of collaboration with Destination 1 (FP1 -MOTIONAL). The initial specification of the Regional Rail Services solution is defined through user stories and use cases, that specify the key elements of the solution as of M6 of the project. Based on the use cases, a list of requirements has been derived, describing the requirements of the planned solution on a high level. This document is describing the first set of specifications for the solution to be developed within FP6-FutuRe WP6/11. The Final Release Specifications (D6.2) will be based on this present deliverable and will describe the solution in a more detailed way, including technical descriptions of all system functionalities and components, an architecture description, UML diagrams, and a final list of use cases and list of functionalities to be developed and subsequently demonstrated in WP11.

Deliverable 6.3 reports on the requirements and design for the interface between Traffic Management Systems (TMS) and Passenger Information Systems (PIS) in WP6 of the EU-Rail FP6 FutuRe project. The interface will be demonstrated using a PIS developed in FP6 WP6 and a TMS developed in the FP1 MOTIONAL project. The aim of the interface is twofold: On the one hand the interface facilitates to provide demand forecast data for train services from a PIS to a TMS so that on TMS side short-term traffic control actions can be taken and long-term replanning decisions can be made; on the other hand, the interface enables the TMS to send information about timetable updates via the interface to the PIS so that travellers can be informed in real time about changes impacting their journeys. The TMS-PIS interface is specified based on four use cases. Three use cases are concerned with transferring demand forecast data for regional train services from a PIS to a TMS. The demand forecast data is calculated within FP6 WP6 by an analytics component of the PIS. The demand forecasts cover (1) the number of passengers between two stations within a defined time window, (2) the number of passengers on a train between subsequent stops, and (3) the number of passenger alighting/boarding at a given station of a train service. On TMS side, the forecast data are processed and used for supporting Traffic Controllers in case of short-term demand forecasts for the next hours and Timetable/Traffic Planners in case of long-term demand forecasts for the next days. A fourth use case describes timetable updates on TMS side, such as delayed departure times or platform changes, that are transferred to the PIS.

This report encapsulates the experiences with data collection for Task 6.3 in Work Package 6 (WP6) of Flagship Project 6 FP6-FutuRe and is referred to as Deliverable 6.4. Task 6.3 involves the mapping of databases needed for various use cases within the broader context of WP6. WP6 involves specification of customer services in the context of regional rail, e.g. a multimodal travel solution including occupancy forecasts. The subsequent task corresponding to T6.3 is T11.3. The data mapping is targeted in T6.3 and the mapped data will be made available for the use case implementations in T11.3. The data on demand and supply related to railway infrastructure is required for proper conduct of operations. For example, one should know the demand and supply statistics before operating new trains or constructing new lines between two locations. The main sources of data for the supply side of railways can be identified as transport operators, infrastructure managers, and ticket vendors. Meanwhile, the demand data can be acquired from the ticket sales and passenger counts. These sources are not limited, as data on demand and supply can be generated by simulation methods, as done by researchers. Additionally, this report discusses the differences between static and dynamic data streams, focusing on their updating frequency, as well as the format and availability of these data streams. The need for data simulations and data validation is also discussed.

The EU-Rail FP6 Future project’s Work Package 6 focuses on Regional Rail Services Requirements & Specifications, with the objective of developing and demonstrating highly accurate multimodal travel solutions for both on-board regional vehicles and at regional rail stations, for passengers and freight. Task 6.4 of WP6 focuses on providing short- and long-term travel demands using machine learning algorithms, enabling a more dynamic response to changing demand and allowing for the adjustment of planned rail services. This deliverable, “Specification of demand analysis algorithms”, is a crucial component of the project, providing specifications for demand analysis algorithms under the specific view of regional lines. This deliverable will include use cases, system actors, capabilities and requirements, high-level architecture, exchange scenarios per use case, interfaces and standards, and algorithm descriptions. The report’s purpose is to provide a comprehensive understanding of the specifications of demand analysis algorithms, ensuring that they meet the project’s objectives and requirements. The report details the scope of the work, including the partner’s developments involved, and the techniques used to develop the demand analysis algorithms. The report was developed considering also FP1 MOTIONAL project specifications on this topic, having a deep alignment on the designed solution. The main findings and conclusions of the deliverable highlight the added value of the work, particularly in overcoming the current limitations of the public transport system, which often leads to costly operations and an inability to react to changing demand. The demand analysis algorithms developed in this deliverable will enable a more dynamic response to changing demand, reducing costs and improving the overall efficiency of regional rail services.

This deliverable is developed as part of Task 6.5 within Work Package 6 (WP6) of the EU-Rail FP6 FutuRe project, a strategic initiative aimed at revitalizing regional railway networks across Europe. WP6 is dedicated to the specification phase, laying the groundwork for the solutions that will later be implemented and demonstrated by WP11. Task 6.5 emphasizes passenger congestion monitoring, providing information that enables operators and authorities to explore different scheduling approaches and adapt them to various transport services. This document specifically focuses on the passenger congestion monitoring specifications necessary to enhance the efficiency and service quality of regional railway lines. The goal of this deliverable is to create a comprehensive specification for a passenger congestion monitoring system and its associated algorithms. This system aims to enhance responsiveness to fluctuating passenger volumes in regional rail services. The structure of this deliverable includes the following key components: 1. Introduction (Section 1): A concise overview of the document’s purpose, objectives, and scope. 2. Objective/Aim (Section 2): Outlines the objectives and scope of this deliverable clearly and concisely. 3. Background (Section 3): Overview of congestion and monitoring, highlighting key challenges and current solutions. 4. Methodology (Section 4): The methodology used for the specification, focusing on the Architecture Analysis & Design Integrated Approach (ARCADIA). 5. Use Cases (Section 5): Detailed scenarios illustrating various passenger flow and congestion situations to provide practical context for system application. 6. System Requirements (Section 6): A thorough outline of both functional and non-functional requirements that the system must meet to be effective and reliable. 7. System Components (Section 7.2): Granular descriptions of each component’s functions and their alignment with system requirements, facilitating modular development and integration. 8. Exchange Scenarios (Section 7.3): Elaborated interactions between system components, depicting data flows during different operational conditions to ensure accurate and efficient data processing. 9. Algorithm Descriptions (Section 8): Specifications of algorithms designed to predict and manage passenger congestion using advanced data analytics and machine learning techniques. 10. Conclusion (Section 9): Summarizes the specifications for the passenger congestion monitoring system and its impact on regional railways. By defining these elements, this deliverable provides a robust framework for developing and implementing a passenger congestion monitoring system. This framework will guide subsequent development phases in WP11, ensuring the practical application of these specifications and thereby supporting the broader mission of the FutuRe project to revitalize regional railway networks across Europe.

Regional railways play a crucial role in Europe, not only by serving rural areas but also by acting as feeders for passenger and freight traffic to the main network. These lines provide an essential, environmentally friendly mode of transport—regional railways enable passengers to reach remote stations and rural destinations effectively.
Given this context, the courier, express, and parcel (CEP) services industry is booming due to shifts in consumer shopping habits and increased retail activity. This growth is putting pressure on road infrastructure and local communities, highlighting the need for more sustainable freight logistics. One innovative solution is to leverage underutilized public transport, such as trams and regional trains, for freight delivery, particularly in smaller towns and rural areas. Task 6.6 within WP6 of FP6 FutuRe aims to enhance freight services to regional and rural areas by leveraging rail transport instead of road. The primary focus is to define and specify innovative solutions for integrating first and last mile transport with passenger trains. Key activities include specifying information, routing, and booking functions for cargo distribution, as well as providing transport offers based on available capacity. Furthermore, the task analyses and defines the necessary framework conditions to effectively implement these freight services.
Deliverable 6.7 outlines how to integrate cargo distribution with passenger trains, reviewing similar initiatives, operational details, and system requirements. The specifications have been described through use cases, requirements, sequence diagrams, components, functions, and interfaces and standards. These specifications are supported by a review of related projects and studies.
Despite a promising start to Task 6.6, we have been unable to secure a demonstration partner. Given this situation, continuing the project to implement and demonstrate the described functionalities to a suitable Technology Readiness Level seems unfeasible, in the subsequent demonstration in WP11.

This deliverable is developed as part of Task 6.7 within Work Package 6 (WP6) of the EU-Rail FP6 FutuRe project, a strategic initiative aimed at revitalizing regional railway networks across Europe. WP6 is dedicated to the specification phase, laying the groundwork for the solutions that will later be implemented and demonstrated by WP11. Task 6.7 aims to foster the standardization processes within the EU. It therefore identifies which data interfaces between components are necessary to provide the information which power the multimodal travel solutions designed in WP6. It analyses if standard interfaces specifications are used and if they already fulfil completely the requirements. If no standard interface specification is available, it is assessed if a standardization process for this interface is advisable. The focus was hereby put on the data exchange between different system components and therefore on data interface specifications. For task 6.7, it was envisaged that it will develop an alpha release of the final deliverable. The final version will be developed by task 11.7. During the work on the alpha release, in total six data interfaces / data formats were identified where it might be advisable to amend existing standard data specifications or create new specifications. For the final release, a more detailed gap analysis will be elaborated.

As of today, the European railways are suffering from several systemic challenges. One of them addresses the cross-border compatibility arising from different standards and expectations from the European infrastructure managers, railway undertakings and partners from the industry. Another problem to tackle involves the competition with other modes of transport such as private car travel, and the profitability of medium route distances. Therefore, within the Flagship Project 6, a key element is to foster the collaboration among all European partners to achieve the overall objective of revitalising regional railways. It is paramount to connect regional railways with other modes of travel that are being used for first and last mile services. This enables a new competitiveness for regional railways and contributes to improved cross-border compatibility in Europe which leads to the reduction of capital expenditures and operating expenses, enhanced productivity (unit costs per train kilometre) and improved customer satisfaction. However, it is important to note that these goals are competing against each other. As a part of the Flagship Project 6, Work Package 6 deals with the conceptualisation of a multimodal travel solution providing requirement specifications. Several advancements should be introduced here, including the usage of demand-related capacity information, congestion monitoring and the utilisation of regional lines for freight transport. An orientation is provided by the technology of a Mobility-as-a-Service (MaaS) solution which aims at consolidating multiple modes of travel into a single platform. In that way, it is possible to plan journeys across all modes of transportation. The goal of Deliverable 6.9 (Task 6.8) is to specify requirements, acceptance criteria and a test strategy. To achieve this, use cases based on relevant personas using the frontend and/or backend services were identified. Important actors within the system are commuters, travellers/tourists, and persons with reduced mobility. The backend services are primarily influenced by administrators. Additionally, an analytics platform establishes a connection between business intelligence analysts and personas from infrastructure management and railway undertakings, such as the traffic manager. The prepared use cases helped with the design of the requirements questionnaire and allowed the expansion of the requirement specification by user requirements from infrastructure managers (IMs) and railway undertakings (RUs). Requirements are ranging from the interface design and user interaction to the querying of reports for insights into passenger behaviour accompanied by addressing data backup, logging of failures and redundancy of the system. Several use cases that have been documented in the deliverable potentially overlap with main line use cases. For the alpha release of the requirement specification, this is considered acceptable. During development of the final release, it will be clarified if a use case has a regional focus or if it applies to main line as well. In the latter case, synergies can be leveraged. To ensure that the implemented solutions comply with the requirement specification defined in Work Package 6, a testing strategy and respective test cases are provided.