Support to development of demonstrator platform for Traffic Management - S2R-OC-IP2-02-2019

Deadline: Jun 18, 2019  
CALL EXPIRED

SPECIFIC CHALLENGE

Innovation Programme 2 includes, as a key innovation, the specification and design of a communication platform (Integration Layer) using standardized data structures and processes to manage the Communication/Data exchange between different services/clients and supporting TMS applications connected to other multimodal operational systems.

This Integration Layer links in a first step, Traffic Management, Traffic Control, Asset and Energy Management systems and signaling field infrastructure. It also provides a gateway for the communication with external clients such as traffic status update and management of traffic demands from external services.

Public documents describing the proposed architecture, interfaces and the data model are available as deliverables from the project IN2RAIL50. X2RAIL-2 is continuing to enhance the specifications and will supply updated drafts for the action.

It is required that consortia applying for this call include an Infrastructure Manager (IM) to host the installation and provide real data from trackside assets and trains to be integrated into the communication network allowing the test and validation of business service application for Traffic Management and Traffic Control developed from different partners of the S2R program. It is preferable that the involved IM is actively performing Traffic management and traffic Control in dedicated Control centers.

SCOPE

The proposals should address all work streams described below, in line with the public deliverables from the project “IN2RAIL” (Grant agreement number 635900).

•   D7.3 Specifications of the standard operator workstation

•   D8.1 Requirements of the Integration Layer

•   D8.2 Requirements for Interfaces

•   D8.3 Description of the Integration Layer and constituents

•   D8.4 Interface Control Document for Integration Layer Interfaces, external/Web interfaces and Dynamic Demand Service

•   D8.5 Requirements of an Application framework

•   D8.6 Description of the Application Framework

•   D8.7 Interface Control Document (ICD) for Application-specific Interfaces

•   D9.1 Appendix 1 “Canonical Data Model”

The proposals shall include activities covering the following scope:

•   Delivery of HW and System SW (RHE Linux) needed for Integration Layer, Application Framework and Operators Workstation both connected to the Integration Layer;

•   Configuration of the middleware of the Integration Layer to support the Conceptual Data Model, and all specified communication and data management processes for Integration Layer, Application Framework, Operators Workstation and WEB-IF.

•   Integration (Interface to Integration Layer, function and data mapping of specific formats to Conceptual Data Model, all necessary administrative processes to manage the clients/services) of the following clients/services:

2. Preferably 2 Radio Block Centers (RBCs) for ETCS Level 2 operations (if not available, a simulation tool for the RBC is required);

3. Web-IF to exchange data with external clients for weather forecast and passenger information systems;

4. Three operator workstations linked with Integration Layer and being able to manage and display Traffic Management Traffic Control functionalities, Energy (Grid) and Asset (infrastructure) status. It shall also be able to present data coming from external clients/services via WEB-IF to the operator;

5. Application Framework to host applications for Traffic Management and Traffic Control;

6. Maintenance Service Management System to the level to subscribe to traffic status and to publish asset fore and now cast information;

7. Preferable Energy (Grid) Management Control System.

•   Configuration of 3 Databases attached to the Integration Layer:

1. Geographical Database:

   •   supporting position representation in LRBG (Balise based), GNSS and

     Kilometer format;

   •   providing the “translation” of the different data formats;

   •   carrying all necessary infrastructure elements needed for Traffic Control,

     Automated Train Operation, Moving Block Operation, Maintenance services,

     and Traffic Management ;

   •   Data structure shall be according the Conceptual Data Model.

2. Time Table Database:

   •   Supporting now – and forecast traffic status;

   •   Supporting Sandbox operations;

   •   Data structure shall be according the Conceptual Data Model.

3. Vehicle Database:

   •   Supporting all relevant data for single vehicles e. g. Locomotive and Train

     consist needed for Traffic Control, Traffic Management, Automated Train

     Operation, Moving Block, Fleet Management services including Maintenance;

   •   Data structure shall be according the Conceptual Data Model.

4. Implemented Data:

   •   Infrastructure Data related to the network operated from the IM of the

     consortia shall be implemented into the Geographical Database in the

     required Data structure;

   •   Data representing the vehicles operation on the network shall be

     implemented into the Vehicle Database in the required Data structure

   •   Data representing the operational Timetable (now-and fore-cast status) for the train services carried out on the network of the IM of the consortia shall be implemented into the Time Table Database in the required Data structure.

•   First level support for 12 months during installation, commissioning and testing phase of the prototypes of the S2R X2RAIL2/4 prototypes.

•   Project Plan to be agreed with TD2.9 activities to be included in the action to be funded under the topic S2R-CFM-IP2-01-2019 and with CCA WA4.2 activities to be included in the action to be funded under topic S2R-CFM-CCA-01-2019, to integrate the activities carried out under these topics;

•   Project Management tools/structure to link closely linked with TD2.9 and CCA WA4.2;
  108

•  Validation of the system including Modules from TD2.9 activities/work package of S2R-CFM- IP2-01-2019 and CCA WA4.2 activities work package of S2R-CFM-CCA-01-2019 as agreed in the Project Plan.

An indicative scheduling of the deliverables is suggested below51:

•   Deliverables of work stream 1 are expected to be available by M6;

•   Deliverables of work stream 2 are expected to be available by M9;

•   Deliverables of work stream 3 expected to be available by M15;

•   Deliverables of work stream 4 expected to be available by M21;

•   Deliverables of work stream 5 to start by month M21 and end in month 33;

•   Deliverable of work stream 6 is expected to be available by M3;

•   Deliverable of work stream 7 is expected to start in Month 2 and end in month 30;

•   Deliverable of work stream 8 is expected to be available by M30.

The activities are expected to reach TRL 6/7.

COMPLEMENTARITY

As specified in section 2.3.1 of AWP 2019, in order to facilitate the contribution to the achievement of S2R objectives, the options regarding 'complementary grants' of the S2R Model Grant Agreement and the provisions therein, including with regard to additional access rights to background and results for the purposes of the complementary grant(s), will be enabled in the corresponding S2R Grant Agreements.

The action that is expected to be funded under this topic will be complementary to the actions that are expected to be funded under the following topics:

 S2R-CFM-IP2-01-2019: Completion of activities for enhanced automation systems (including Freight ATO GoA4), train integrity, object controller.

 S2R-CFM-CCA-01-2019: Integrated mobility management (I2M), Energy and Noise & Vibration.

EXPECTED IMPACT

The activities are expected to contribute to:

•   Achieving the basic knowledge and experience of the best system architecture for the targeted communication platform. Application such as automated Train Operation and automated Traffic regulation processes will be one of the main key element to improve European industries competitiveness also in markets currently dominated by other systems;

•   Defining and validating the basic architecture able to power the deployment of this new communication structure. The new structure will have impact reducing OPEX and CAPEX of Rail operations for mainline and regional;

•   Reducing time to market for such a system, the test & commissioning phase under life operations integrating the activities of TD2.9 and CCA WA4.2 is a key success factor. It will also have significant impact on the signaling system at a enabling different and simplified operational procedures;

•   Specific metrics and methods to measure and achieve impacts should be included in the proposals, with the objective to achieve by the end of the S2R Program the quantitative and qualitative targets defined in the S2R MAAP related to TD2.9 and CCA WA4.2, in line with the relative planning and budget.

  Type of Action: Innovation Action (IA)