WP01 - Project Management

9Task 1.1 - Project Coordination (Leader: ALS)
Project coordination activities will follow a professional overall project management process. The Coordinator shall:
- Monitor that the action is implemented properly and in accordance with the Grant Agreement.
- Act as the intermediary for all communications, unless the Grant Agreement specifies otherwise.
- Manage interaction with the European Commission and the Shift2Rail Joint Undertaking.
- Ensure quality of documents and deliverables submitted to the European Commission / Shift2Rail Joint Undertaking including financial statements.
- Submit the deliverables and reports to the Commission in accordance with the timing, conditions, forms and templates set out in Annex 1 and Grant Agreement.
Task 1.2 – Consortium and Contract Management (Leader: ALS)
Consortium Management activities will include the following tasks:
- Establishment and maintenance of the Consortium Agreement and collaboration agreement(s) with complementary grant(s).
- Management of change requests to the Grant Agreement including communication with the S2R JU.
- Implementation of competitive calls or tenders by the consortium in order to choose a new beneficiary where required and handling of beneficiaries’ withdrawals.
- Implementation of standard processes for collecting input to the financial, periodic and final reports and deliverables as required by the Grant Agreement and its Annex 1.
- Preparing and managing official project meetings as set out in the Consortium Agreement, as well as of review meetings with the EC/S2R JU, including settings agendas, participant invitations, minutes, meeting location and other associated tasks.
- Arranging the Organization of a kick-off event.
Task 1.3 - Financial Management (Leader: ALS)
The Administrative and Financial Management activities will include:
- Maintain an overview of the overall project budget and its distributions amongst Beneficiaries.
- Receive the EU funding for the project on behalf of the beneficiaries from the Commission / Shift2Rail JU.
- Forward payments to Beneficiaries according to the Grant Agreement and calculations provided by the European Commission / Shift2Rail JU.
- Organise support for Beneficiaries requiring help in preparing the financial statements to be included in the periodic and final reports of the project.
Task 1.4: Quality Assurance (Leader: ALS)
Quality management and adequate risk management will foster the success of the project. The activities are:
- Establish and maintain a project quality plan document. This quality plan will include a template for the assessment of completion of “demonstrator activities” that will be used in all the X2Rail-4 WPs including demonstrator activities
- Apply and monitor the JU Project Management and Collaboration Tool.
- Supervision and monitoring of technical progress and deliverables. Development and maintaining of a risk management plan.



WP02 - Technical Coordination and System Coherence

WP2 is based on a project management, technical co-ordination and system integration methodology. A common platform will be established to enable technical collaboration between the work packages and facilitate data exchange, alignment and consensus during project lifetime. The key tasks of WP2 are:
-    Implement the Technical Management Team;
-    Technical Coordination between the work packages and with other Shift2Rail activities (including the action to be funded under topic S2R-CFM-IPX-CCA-2019)
-    System Coherence.
The WP will be composed by members that are leading the IP2 TDs or that are core members inside one or several TDs and WPs. Each company will nominate a “rail system expert” who is or will also be a TD Leader, WP leader or a “rail system expert” in a TD or WP.
The work on the definition of the reference architecture will take place in the action to be funded under topic S2R-CFM-IPX-CCA-2019 (this work is somehow transferred from IP2 to the action to be funded under topic S2R-CFM-IPX-CCA-2019). WP2 will however ensure the consistency of the technical work done in X2Rail-4.
In order to align X2RAIL-4 with the S2R common railway System Architecture, WP2 will act as the interface to the action funded under S2R-CFM-IPX-CCA-01-2019 regarding the technical assessment of specification requests and regarding the integration of these into X2RAIL-4, following the Programme Governance and Change Management Process agreed by the Shift2Rail Programme Board.
Based on S2R ED Programme Board approval, S2R-CFM-IPX-CCA-01-2019 will submit to WP2 proposals for changes in functional architecture and interfaces of the solution developed within the Project and request a technical assessment. This assessment will include technical feasibility for implementing the change, the impact the change might have within the project, impact on other tasks, milestones and deliverables within the project and eventual changes in timing, effort and budget. S2R-CFM-IPX-CCA-01-2019 will present to the ED Programme Board the results of the technical assessment. In case the Programme Board approves the change, X2RAIL-4 will, if needed, submit a request for an amendment to the Grant Agreement and proceed with the integration.
The “Technical assessment of S2R-CFM-IPX-CCA-01-2019 specification requests” will be performed involving the appropriate experts. These experts could be the experts from the respective IP TDs and project WPs or any experts from the partners that would present the requested skills to conduct the task. WP2 will coordinate the integration of the change and provide S2R-CFM-IPX-CCA-01-2019 with feedback during and at the completion of the integration.

Task 2.1 – Technical coordination, System Integration and Coherence (Leader: ALS; Participants: STS, AZD, BTSE, CAFS, DLR, INDRA, MERMEC, SMO, TD, TRV, DB, HC, SNCF-R, NR)
This task is dedicated to coordinate the ten technical work packages of the project:
-    Coordinate the integration (in the X2Rail-4 project) of the decisions taken by Programme Board
-    Organise and lead quarterly TMT meetings to discuss issues from a system coherence perspective, involve relevant experts and reach consensus between involved parties.
-    Conduct review of the specific technical and system-level related work being carried out by the technical work packages, review the progress, results and capture changes to the work plan, milestones and status indicators.
-    Identify common areas of work, eliminate duplication of effort, between technical work packages, share best practice, monitor performance of partners.
-    Agree and manage work scope allocation between technical activity areas.
-    Co-ordinate and facilitate the data exchange among members and work package tasks.
-    Facilitate the exchange of information between IP2 technical work packages in X2Rail-4
-    
-    Monitor scientific project progress.
-    Support compliance with and monitor impact on International and European standards and TSI specifications.
-    Identification, assessment and joint resolution of technical issues on system level.
-    
-    Ensure use of coherent and unambiguous terminology.
-    Guide and support systems engineering processes.

This task will also implement a technical system integration and coherence among and between all 11 TDs of IP2, together with the other WP2 of X2Rail-1, X2Rail-2 and X2Rail-3. To guarantee X2Rail-4 is delivered as an integrated project, covering all railway market segments and allowing a link to S2R Open Call projects and the transition from past and to future S2R projects, the following activities are to be carried out, within the Technical Management Team:

- Ensure alignment of Functional Requirements Specifications and Interface Specification between the technical work packages WP3 to WP12. Part of WP3, WP4 and WP5 on ATO is at the border between IP2 and IP5 activities for ATO. This will deserve a special attention as far as technical coherence is concerned, IP2 being clearly responsible and involving the expertise in ATO matters and around.
- Assess and verify system interfaces between technical work packages WP3 to WP12.
- Monitor testing and demonstration activities and identify and prevent overlaps and conflicts to ensure successful Technical Demonstrators and prototypes
- Ensure that the output from work packages is consistent with reference architecture developed in the action to be funded under topic S2R-CFM-IPX-CCA-2019 and meets the goals of the project and the instructions from the Programme Board.
- Interaction and synchronisation with complementary S2R Open Call Projects.
- Provide a set of requirements to be used for dissemination by WP13.
  Task 2.2 – Regulations, Standards and KPIs (Leader: ALS; Participants STS, AZD, BTSE, CAFS, DLR, INDRA, MERMEC, SMO, TD, TRV, DB, HC, SNCF-R, NR)
-    
Sub-task 2.2.1 CCA
This sub-task will provide upon request (and at least on semi-annual basis) input in the most appropriate format to the S2R CCA members to quantify the impacts for developing the KPI at S2R programme level (e.g. IMPACT-2 project “improvement table”). Project KPIs will also be reported in the Public Summary section during the yearly reporting period.

Furthermore, this sub-task will provide upon request input (in the most appropriate format) to the S2R CCA members on standardisation (e.g. completing and enhancing the S2R standardisation rolling development plan content, contributing to topic meetings).

Sub-task 2.2.2 ERA/Preparation of CCS TSI
This sub-task consists in initiating CR’s to regulation.
This sub-task also consists in the coordination with European Union Agency for Railways (ERA) in the frame of the preparation of inputs for the foreseen update of the CCS TSI (planned in 2022). This sub-task will include the organization of joint meetings with ERA to present them the technical directions decided/followed in X2Rail-4 specification work and the technical results achieved in the demonstrator/prototyping activities of X2Rail-4.
ERA will be invited to WP2 meetings for that purpose. The relevant WP leaders will also be invited according to the topics to be addressed during these meetings.
In addition, WP2 will be responsible for tracking the deliveries from the relevant TDs/WPs, which will contribute to the update of the CCS TSI. WP2 will liaise with the project coordinator and the S2R IP2 Programme Manager to ensure adequate and smooth communication with the relevant ERA bodies in charge of ETMS/ETCS Change Control Management process.
Task 2.3 – Coordination and Interaction with Shift2Rail IPs (Leader: ALS; Participants: STS, AZD, BTSE, CAFS, DLR, INDRA, MERMEC, SMO, TD, TRV, DB, HC, SNCF-R, NR)
This task implements the support from the Technical Management Team to the Steering Committee if and when required by the Steering Committee.
The activities include coordination and interaction between the X2Rail-4 project, past and future IP2 projects and the concurrent S2R Member and Open Call projects among all five S2R Innovation Programmes and cross-cutting activities, as well as with the action to be funded under topic S2R-CFM-IPX-CCA-2019. To guarantee X2Rail-4 research and development actions are persistently aligned via an up-to-date Multi Annual Action Plan (MAAP) and with all S2R projects, the following activities are to be carried out:
-    Facilitate the exchange of information between IP2 technical work packages in X2Rail-4 and work packages in past and future IP2 projects, other IPs (including the action to be funded under topic S2R-CFM-IPX-CCA-2019) and open calls as defined in the related collaboration agreements.
-    Coordination of collaboration with complementary S2R Open Call Projects.
-    Coordination of collaboration with the action to be funded under topic S2R-CFM-IPX-CCA-2019 for the technical assessment of specification requests coming from the action to be funded under topic S2R-CFM-IPX-CCA-2019.
-    Aligning research and development activities of the X2Rail-4 project with past and future concurrent IP2 projects.
-    Monitor the overall development of X2Rail-4 with respect to the MAAP.

This task will prepare, develop, organise and assign follow-up actions for knowledge transfer (including meetings) between the X2Rail-4 project and concurrent IP2 projects. Amount and frequency of meetings to be organised depend on the number of S2R Member and Open Call project interfaces with IP2.
Part of WP3, WP4 and WP5 is at the border between IP2 and IP5 activities for ATO. It will deserve a special attention as far as technical coherence is concerned, IP2 being clearly responsible and involving the expertise in ATO matters and around.
Task 2.4 - Technical assessment (impact on X2Rail-4 project) of specification requests from the action to be funded under topic S2R-CFM-IPX-CCA-2019 (Leader: ALS, Participants: STS, AZD, BTSE, CAFS, DLR, INDRA, MERMEC, SMO, TD, TRV, DB, HC, SNCF-R, NR)
This task aims to identify and analyse the impact that the requirements specification requests coming from the action to be funded under topic S2R-CFM-IPX-CCA-2019 may have on the process evolution of the technical WPs. In particular the action has to:
1.    Provide the functional analysis and apportionment/possibilities for change with regards to the current functional architecture, including whenever possible a preliminary safety analysis at functional level.
2.    Detailed technical and planning impact: Provide detailed indications on what/how/when the selected requirements impact the development. With respect to the technical WPs, the action should define the complete planning able to identify the impact on specification and development. Specifically the planning should address:
a)    what is impacted (e.g. TD/WP, process, function, architecture, HW, SW …) and the expected change. The analysis has also to identify what change implies (e.g. development already done or planned that might be rationalized/diverted/harmonised/lost because of the change)
b)    how the change can be carried out (e.g. effort requested, workload, task force, interaction with IPX …)
c)    when the change can be foreseen (e.g. Gantt chart, harmonisation with the planned activities, recovery actions to reduce undesirable side effects…)
3.    Evaluate the risk with the lumpsum approach

This task will be performed involving the appropriate experts. These experts could be the experts from the X2Rail-4 TDs and WPs or any experts from the partners that would present the requested skills to conduct the task.
It is important that from the beginning of the project, each partner foresees a budget, timing and availability of the appropriate experts to execute this task. Any foreseen budget that would finally not be needed to execute this task (e.g. because less specification requests than initially expected would have to be analysed) could be later on transferred to other WPs that would require more budget than initially foreseen to complete their tasks.
The results of the tasks will be consolidated at WP2 level. The related deliverables will be submitted to TMT and SC for approval.
If a tool is needed to perform this task (e.g. to write down the requirements), this tool will be jointly decided by the contributors to this task.

WP03 - “ATO up to GoA4” Specification

This is done in two steps associated to two separate activities:
GoA2 specification (quick win)
GoA3/4 specification (preliminary and built upon GoA2)
These specifications will be submitted to ERA  
Task 3.1 – Technical Coordination and System Integration (Leader: ALS, Participants: SMO, STS, AZD, BTSE, CAFS, DB, SBB, MERMEC, NR, TD, TRV, SNCF-R)
ALS as technical leader will carry out the overall WP coordination supported by the task leaders.
Task 3.2 – GoA2 Specification (Leader: ALS, Participants: SMO, STS, AZD, BTSE, CAFS, DB, SBB, MERMEC, NR, TD, TRV, SNCF-R)
In the context of X2Rail-1, the majority of GoA2 functions have been specified in order to perform interoperability tests on two Reference Tests Benches. In addition, the System Requirement Specification and Interface Specification have been submitted as draft to and accepted by ERA.
The purpose of this activity is to update GoA2 specification in order to take into account:
- the results from interoperability tests performed in X2Rail-1 (Return on Experience);
- Safety assessment performed on the current specification;
- Possible new operational requirements primarily related to freight.
A Traceability Matrix between the Operational Concept and Specifications will be produced.
Updated GoA2 specification will be submitted to ERA
GoA2 specification contain:
- The Operation Concepts (Passenger and Freight) specified by the Users team members
- The System Requirement Specification
- And the interface specifications compliant with the architecture defined in the Operation Concept documents
The required FFFIS specifications shall specify the interchangeability and interoperability (Plug&Play).
Fully finalised FFFIS (Plug&Play) specifications will be delivered on the condition that underlying critical technology, relevant for that function/interface implementation, has reached the necessary level of maturity and is ready for product integration.
Task 3.3 – GoA3/4 Specification (Leader: ALS, Participants: SMO, STS, AZD, BTSE, CAFS, DB, SBB, MERMEC, NR, TD, SNCF-R)
In the context of X2Rail-1, preliminary specification for GoA3/4 solution will have been delivered.
It includes:
- Operational Concept including, Needs and Missions, Operational Context Definition, Actors definition, Uses Cases definition, Operational scenarios, Logical Architecture;
- System Requirement Specification including Functional Break down Structure, Functional Requirements, allocation to Logical Blocks, Interfaces Specifications (FIS level).
- Fully functional and vendor independent reference model.
The purpose of this activity is to complete GoA3/4 specification. This includes:
- Completion of Operational Concept (includes GoA1/2);
- Completion of System Requirement Specification;
- Physical Architecture Specification including allocation of Logical Blocks to Physical Blocks and interfaces specification (agreed FFFIS level to ensure agreed Plug&Play);
- Safety analysis of GoA3/GoA4 system in order to identify safety and non-safety relevant building blocks.
- Security analysis.
The required FFFIS specifications shall specify the interchangeability and interoperability (Plug&Play).
Fully finalised FFFIS (Plug&Play) specifications will be delivered on the condition that underlying critical technology, relevant for that function/interface implementation, has reached the necessary level of maturity and is ready for product integration.
This activity will ensure alignment with the GoA1/2 System Requirement Specification" to ensure a separate independent system is not developed. This activity includes the specification of obstacle Detection system which will also be delivered to and used by IP5 (ARCC project) and SMART-2 project. Joint meetings are foreseen.
This activity includes the interface specification with the Rolling Stock. This will be done jointly with IP1 (CONNECTA project). Joint meetings are foreseen.
For localisation principles, we will refer to the results of TD2.4 (Positioning).
This activity includes specific review and update of the GoA3/4 specification considering Freight application.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4

WP04 - “ATO up to GoA4” Development

The following companies will develop ATO prototypes:
ALS    STS    BT    CAFS    TD    AZD
These companies will:
- develop an ATO on-board prototype (TRL 6-7) considering different type of trains (electric or diesel/electric) and different type of operation (High Speed Line, Low Traffic/Regional Lines, Urban/Suburban);
- develop an ATO trackside prototype (TRL 6-7);
- develop or integrate obstacle detection and environment sensors
The ATO prototypes will include:
- Passenger Exchange, door opening/closing, safe departure
- Incident & Emergency detection and management
- Localisation.
- Remote Control supporting degraded modes
These prototypes need to be compliant with the functional and vendor independent reference specification and will be used to demonstrate agreed interoperability and agreed interchangeability of the prototypes provided by different suppliers.
Task 4.1 – Technical Coordination and System Integration (Leader: ALS, Participants: SMO, STS, AZD, BTSE, CAFS,  TD, TRV)
ALS as technical leader will carry out the overall WP coordination supported by the task leaders.
Task 4.2 – GoA3/4 Protype Development (Leader: ALS, Participants: STS, AZD, BTSE, CAFS,TD)
The companies mentioned above will develop their prototypes in compliance with the functional and vendor independent reference specification
All of them envisage to develop trackside and on-board part of the GoA3/4 ATO. The hardware platform will be partner specific; but all of them will comply with the functional and performance requirement delivered by WP3.
Task 4.3 – “Obstacle detection” and “environment sensors” development (Leader: ALS, Participants: STS, AZD, BTSE, CAFS, DB, TD)
The companies mentioned before will develop prototypes for obstacle detection and environment sensors .
Based on the specifications developed in Task 3.3, obstacle detection prototypes will include FFFIS (Plug & Play) Interface to ATO-OB.
The use of this “plug&play” interface is making the “obstacle detection” solution independent from the used technologies. At the present stage, the technologies considered by the different partners mentioned above are not declared. But, as much as possible, they envisage to use diverse technologies achieving the same functional requirement and compliant with the FFFIS interface.
Obstacle detectors developed in the context of WP4 will be used for “factory IOP tests” and “Pilot tests” as well. They will also be proposed to IP5 TD5.1.3. members in order to be tested in a specific freight environment.
Task 4.4 – GoA3/4 Reference Tests Bench (Leader: ALS, Participants: STS)
It is required to perform fully functional tests in order to demonstrate that the interoperability rules, interfaces specification and conformity with the functional and vendor independent reference specification are respected;
This task includes:
- development of upgraded Reference Test Bench;
- validation of the modified interoperability and interchangeability platform test bench;
- specification of the operational scenarios to be tested (including high speed, passenger and freight specific scenarios).
ALS and STS will develop Reference Test Benches.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4

WP05 - “ATO up to GoA4” Tests

It includes:
- The development or upgrade of Reference Test Benches required to perform interoperability tests in factory;
- Factory interoperability tests involving the prototypes developed by the different suppliers;
- On-site tests on Pilot Line and Pilot train involving the prototypes developed by the different suppliers in compliance with the functional and vendor independent reference Specification delivered in D3.2.
Task 5.1 – Technical Coordination and System Integration (Leader: ALS, Participants: SMO, STS, AZD, BTSE, CAFS, DB, SBB, MERMEC, NR, TD, SNCF-R, DB, TRV)
ALS as technical leader will carry out the overall WP coordination supported by the task leaders.
Task 5.2 – GoA3/4 Factory IOP tests (Leader: ALS, Participants: STS, AZD, BTSE, CAFS, DB, SBB, NR, TD, SNCF-R)
The aim of this activity is to perform interoperability and interchangeability tests as specified in operational scenarios defined in WP4. It includes the validation of AoE requirements (up to GoA3/4) using different ATO-OB  and ATO-TS prototypes;
The prototypes will include ATO-OB and ATO-TS. Common implementation with other TD functionalities (e.g. Satellite Positioning) will be analysed and performed in case feasible.
It is required to perform fully functional tests in order to demonstrate that the interoperability rules, interfaces (FFFIS (Plug & Play)) and conformity with the fully functional and vendor independent reference Specification are respected.
Task 5.3 – GoA3/4 Pilot tests (Leader: ALS, Participants: STS, AZD, BTSE, DB, SBB, NR, TD, SNCF-R, SZ)
The aim of this task is to validate AoE using pilot train and pilot line.
The S2R members will:
- host AoE prototypes on a pilot line and manage full functional pilot tests in order to demonstrate the overall functionality, interchangeability and interoperability of “ATO up to GoA4” solution.
- upgrade of 1 pilot train with AoE.
- upgrade of 1 pilot line with AoE.
- perform interoperability tests in accordance with operational scenarios.
- provide a remote driving pilot line demonstration.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4

WP06 - On-Board Train Integrity: laboratory and validation activities completion

Task 6.1 - WP Technical Coordination (Leader: STS)
This task includes general coordination activities.
Task 6.2 – Laboratory and validation activities (Leader: CEIT; Partners: ALS, STS, AZD, BTSE, CAFS, DB, DLR, INDRA, MERMEC, NR, OBB, RAILENIUM, SNCF-R , SMO)
This task includes the following activities:
•    Complete laboratory testing activities with mock-ups and related validation tools for freight and regional lines, with the support of new technologies developed in X2Rail-2;
•     Complete laboratory testing activities related to adaptation of existing technologies for wireless communication suitable to NLOS situations, energy harvesting solutions and related energy storage;
•    Review of the FSM formal models with the partners responsible for the implementation to determine the relevant parameters to target for performance analysis;
•    Update the formal models developed to the different architectures/technologies investigated;
•    Perform the comparative study of the various investigated solutions using simulation and formal verification techniques (statistical model-checking);
•     Complete the RAMS analysis my means of conducting reliability, availability, maintainability, and safety (RAMS) studies in conformity with RAC (Risk Acceptance Criteria) guideline by ERA and CENELEC 50126 standard.
•     Complete the analysis of cost and benefit for the OTI from the X2Rail-2 project, considering further scenarios with regards to a) economic advantages when removing infrastructure elements for train integrity monitoring and b) capacity effects which are enabled based on OTI.
Sub-Task 6.2.1 – OTI demonstrator 1 (Leader: AZD)
This activity includes development of OTI demonstrator TRL4.
Sub-Task 6.2.2 – OTI demonstrator 2 (Leader: INDRA)
This activity includes development of OTI demonstrator TRL4.
Sub-Task 6.2.3 – OTI demonstrator 3 (Leader: MERMEC)
This activity includes development of OTI demonstrator TRL4.
Sub-Task 6.2.4 – OTI demonstrator 4 (Leader: STS)
This activity includes development of OTI demonstrator TRL4.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.

WP07 - On-Board Train Integrity: Demonstration, assessment and standardization proposal

Task 7.1 - WP Technical Coordination (Leader: STS)
This task includes general coordination activities.
Task 7.2 – Demonstration and Assessment (Leader: RAILENIUM; Participants: STS, ALS, AZD, BTSE, CEIT, DB, DLR, INDRA, MERMEC, NR, OBB , SNCF-R , SMO, SZ )
This task includes the following activities:
•    Contribute to the integration and demonstration activities of the OTI prototype for freight & low traffic lines scenarios, starting from the laboratory simulations and tests, to the final test trial in a real environment;
•    Contribute to the development of a demonstration unit suitable for both regional and freight lines; Carry out laboratory tests and pilot line tests on a regional line, using the defined test scenarios and test cases;
•    Perform the preliminary safety assessments of candidate new solution and review test scenarios, test cases and procedures defined in X2R2 WP4;
•    Ensure that OTI solutions comply with the requirements a validation environment will be defined and implemented in a suitable laboratory. The simulation-based ETCS/ERTMS laboratory RailSiTe® as well as the mobile validation environment RailDriVE® will be prepared accordingly to be ready to test OTI solutions. Processes and tools for generic validation and verification are to be set up. The rules for the assessment of the train integrity simulation prototype (on-board locator, based on GNSS and the wireless communication) will be proposed for standardisation;
•    Perform dependability study for the candidate solution, developing the safety integrity level (SIL) allocation methodology to the new train integrity solution on different rail segments, assessing (performance and security evaluation included) innovative wireless communication technologies for train integrity, integrating dependability and safety requirements (e.g. SIL 4 requirements) and contributing to the safety case for certification and authorization;
•    Develop a set of assessment criteria for the process and the product derived by performing an independent safety analysis of OTI demonstrators of sub-tasks 7.2.1, 7.2.2 and 7.2.3.
•    Conduct the safety assessment for certification and authorization activity using audit and review techniques

In order to accompany the development of the on-board train integrity solutions up to TRL7, an outlook on the technology migration of the OTI shall be taken into account. The conditions for the rollout of the new technology will be different for the different market segments. Special attention shall be drawn on the freight sector since these trains are composed individually. It must be ensured that track access is guaranteed when conventional train integrity technology (e.g. axle counters) from the infrastructure will be removed. Based on the technology specifications from the X2Rail-2 project, one or more representative scenarios will be defined, the conditions analysed and possible scenarios for the technology migration developed and described.
Sub-Task 7.2.1 – OTI demonstrator 1 (Leader: AZD)
This activity includes development of OTI demonstrator up to TRL6-7.
Sub-Task 7.2.2 – OTI demonstrator 2 (Leader: INDRA)
This activity includes development of OTI demonstrator up to TRL6-7.
Sub-Task 7.2.3 – OTI demonstrator 4 (Leader: STS)
This activity includes development of OTI demonstrator up to TRL6-7.
Task 7.3 – Standardization Proposal (Leader: STS; Participants: ALS, AZD, BTSE, CEIT, DB, INDRA, MERMEC, NR, RAILENIUM, SNCF, SMO)
This task includes the following activities:
•    Providing an analysis of the impacts on the signalling system, by defining a preliminary proposal for standardization in relation to OTI interfaces (e.g. in the context of CCS and rolling stock. Since today the train integrity functionality is performed by track side equipment influencing the interlocking, the new architecture, interfaces and processes have to be rearranged taking into account the new solution developed (on-board detection).
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.

WP08 - TMS services

The works carried out under this workstream are jointly undertaken from the involved partners.
Task 8.1 - Technical Coordination (Leader: DB, Participants: NR, TRV, SNCF-R, CAFS, INDRA, HC, SMO, STS)
Periodic meetings led by the WP Leader and the Task Leaders/partners to secure and monitor the progress of the activities. This task shall also align the different activities of the work package with other related work streams of S2R and coordinate interoperability of the different solutions developed.
Task 8.2 - Use cases for advanced TMS principles (Leader: NR, Participants: DB, TRV, SNCF-R, CAFS, INDRA, HC, TD, AZD)
Finalise the activities of task 6.4 (deliverable D6.3) of X2Rail-2 work package 6. The task will decide on a specific presentation format for the use cases building on from D6.3. This will include:
- Review and update of uses cases from D6.3
- Updated relevant use cases for degraded mode considerations
- Development of functional specification for TMS for the selected use cases, this will include considering any relevant lessons learnt from for example prototypes as they develop, other relevant tasks
Task 8.3 - Automated conflict handling solution (Leader: DB, Participants: NR, TRV, SNCF-R, CAF, INDRA, HC, SBB , RAILENIUM, TD, ALS, SMO, STS, AZD, SZ)
The conflict resolution solution shall be able to automatically calculate a re-plan after a complex disruption like the closure of a railway line in a dense network.
The solution shall be able to take multiple criteria into account
- Current positions of trains
- Re-routing options, incl. train characteristics
- Unit cycles or upcoming maintenance show-ups for units
- Crew cycles or passenger flows
The solution shall be able to provide several solutions with clear indicators (KPIs) attached to them and all information necessary to allow the operator to decide the most appropriate solution.
Task 8.4 - Large scale optimisation methods (Leader: DB, Participants: NR, TRV, SNCF-R, RAILENIUM, CAFS, INDRA, HC, ALS, STS, AZD)
The task shall identify most promising mathematical methods that will allow in future to use automation and optimisation on a much larger scale. The currently available methods for optimisation of train movements, especially for disruption management, have limits in the number of trains and complexity of the network and considered criteria (KPIs) they are able to take into consideration. This is to an extent that makes usage in large networks still impractical and impacts negatively network capacity and service quality, especially when trying to recover from serious disruptions.
This research task shall test and evaluate new approaches from Operations Research as well as Artificial Intelligence – or the combination of both – for their potential to scale up automation and optimisation of train movements for larger networks and more KPIs, e.g. for network capacity, service quality, cost and/or energy consumption.
The new approaches will aim to coordinate conflict resolution in different areas. They will be independent of the conflict resolution method used in each area, so to make possible to use different methods for areas with different characteristics.
Task 8.5 – Methods and measures for assessment of workload and situation awareness (Leader TRV, Participants: NR, DB, SNCF-R, CAFS, TD, AZD)
This task shall assess and validate the most promising methods and measures developed during X2R-2 for evaluating human performance on new TMS products and prototypes, as an integral part of system performance.
- Evaluate the methods for assessing workload and situation awareness in a simulated environment, using the different operation modes (from normal to emergency)
- Describe and develop a toolbox of methods for mapping and evaluating operator preconditions related with sub-optimal performance, for different stages of the product development process.
- If methods are effective, they could be used to support a proof of concept.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.

WP09 - TMS Demonstrators TRL4

The works carried out under this workstream are based on the results from X2R2 WP6 project. Updates of specifications and the design of a new architecture are done jointly amongst the partners. The proposed non-collaborative demonstrators will be developed to reach TRL4. The design of the demonstrators are managed directly from the Partners. If required, Partners can agree for a joint or partially combined development of demonstrators.
Task 9.1 – Technical Coordination for the design of the demonstrators TRL4 (Leader: BTSE, Participants: STS, NR, SMO, TD, TRV, AZD, HC, DB, INDRA)
Periodic meetings led by the WP Leader and all partners of the work package will be held to secure and monitor the progress of the specification and development activities, the implementation strategy of the works performed under the OC S2R-OC-IP2-02-2019: “Support of the development of demonstrator platform for Traffic Management” and to align the cooperation with other S2R projects and Work Packages (e.g. ATO GOA3/4).
The work package leader will prepare all necessary reports, plans for the S2R IP2 coordinator and S2R JU and will attend TMT meetings of X2R4 to represent the work package.
Task 9.2 – Integration Layer and System Architecture (Leader: BTSE, Participants: STS, NR, SMO, TD, TRV, AZD, DB, HC, INDRA)
The development of the demonstrators related to the TMS workstream is based on specifications delivered from X2R2 project. The activities of this task represent the platform to flag required changes/amendments/enhancements of the SRS of the Integration Layer to the WP. The Partners involved in this activity monitor the change requests, specify necessary enhancements/amendments and deliver the changes to the Canonical Data Model (CDM) work package to be implemented in the design of the S2R CDM.
The works include further the specification/description of a comprehensive functional system architecture for TMS, Traffic and ATO Control. A close cooperation with the work packages specifying the generic ATO GOA3/4 and Moving Block/fixed virtual Block basic operational procedures will secure interoperability, standardization and flexibility of the architecture.
Task 9.3 - Development and Verification of demonstrators TRL4 (Leader BTSE; Participants: STS, NR, SMO, TD, TRV, AZD, HC, INDRA)
The objective of this task is to develop prototypes TRL4. Demonstrators are allocated to partners and shall follow the basic requirements defined in the deliverables of X2R4 WP6. Each demonstrator proposed will be designed and delivered by one partner.
Regular status updates demonstrating the progress of the design activities will be part of Task 1 of this work package.
All necessary activities related to the design of the prototypes shall follow the guidelines described in D6.4 of X2R2 WP6.
At the end of the design phase, the partners will provide reports for each demonstrator. These reports will be verified for completeness as required from the data management plan created in WP1 and will be consolidated into a summary report.
Sub-task - 9.3.1 Demonstrator TRL4 for Connected Driver Advisory System (Partner: STS)
The scope of work of this task is the development of a prototype that implements the computation of speed profile and driving modalities to feed a Connected Driver Advisory System (C-DAS); the development includes the definition of interfaces between the TMS and modules that provides the DAS functionalities. The work is based on the outcome of task 5.6.2 of .X2Rail-2 WP6.
Sub-task - 9.3.2 Demonstrator TRL4 for Conflict Prediction System (Partner: AZD)
This task focusses on the design of a prototype demonstrating complex Conflict Prediction System. The application will be realized by specifying and developing specific tools for handling regular and irregular traffic issues.
Sub-task - 9.3.3 Demonstrator TRL4 for Wayside ATO constituents (Partner: BTSE)
The demonstrator developed under this task addresses the design of constituents needed for ATO GOA2 operation based on data management based on the integration Layer. The works comprise the subsystems and Interfaces needed to read data from the Integration Layer to create a JP and SP, the business function to create these profiles in CDM and the necessary processes to make these messages available at the API linking the ATO -TS to the Integration Layer.
Sub-task - 9.3.4 Demonstrator TRL4 for Integration of field status information (Partner: HC)
This task aims at the development of a Demonstrator (TRL4) for modules for integrating field status information from trains, asset and train control into one single, consistent data source; train forecast calculation; possession management module for (re-)planning of maintenance activities and impacted trains; interfaces for data exchange with external resource management, train request and information services.
Sub-task - 9.3.5 Demonstrator TRL4 for TMS Business Applications (Partner: INDRA)
This task covers the provision of a TRL4 demonstrator based on TMS Business Applications focused on the mitigation of the impact that traffic disturbances and unexpected infrastructure restrictions generate into the traffic evolution. Under these circumstances, for instance, the evolution of the scheduled maintenance works on the facilities are considered, as well as additional required actions arisen during the traffic operation based on the modification of the scheduled trains behaviour.
The implemented prototypes will be based on the Proofs of Concept performed in the X2RAIL-2 and they will expose a modular architecture complying with the specified Integration Layer and its Application Programme Interface in a laboratory environment and using a common data model.
Sub-task - 9.3.6 Demonstrator TRL4 for Conflict Detection and Resolution (Partner: SMO)
This task addresses the specification and development of business service applications for the detection of future conflicts, the presentation of the results to the operator and conflict resolution measures and integration them into operator's workflow. The SW application modules will be hosted in an Application Framework.
Sub-task - 9.3.7 Demonstrator TRL4 for Application Modules (Partner: TD)
The works proposed for this task address the demonstration of use cases identified in Task 6.6 of X2R2 WP6. The prototypes describes the scenario for interaction between an Asset Management System (AMS) and TMS with the goal to perform TMS re-planning services based on early indication of an actual failure or a predicted failure of a railway asset, for example a set of points affecting the capacity of a station. As the proposals are assessed the Plans may be communicated with Rolling Stock and/or Crew systems to ensure they can be resourced. The prototype will include transfer of data between the Integration Layer and selected features of the Standard Operator Workstation (from X2RAIL2 D6.5) including third party application HMI integration and external interface to weather data.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.

WP10 - TMS Demonstrators TRL6

The works carried out under this workstream shall boost the demonstrators started in WP9 from TRL 4 to reach TRL6 at the end the project.
Task 10.1 - Technical Coordination for the design of the demonstrators TRL6 (Leader: BTSE, Participants: STS, NR, SMO, TD, TRV, AZD, DB, HC, INDRA)
Periodic meetings led by the WP Leader and all partners of the work package will be held to secure and monitor the progress of the specification and development activities, the implementation strategy of the works performed under the OC S2R-OC-IP2-02-2019: “Support of the development of demonstrator platform for Traffic Management” and to align the cooperation with other S2R projects and Work Packages (e.g. ATO GOA3/4).
The work package leader will prepare all necessary reports, plans for the S2R IP2 coordinator and S2R JU and will attend TMT meetings of X2R4 to represent the work package.
Task 10.2 Development and Verification of demonstrators TRL6 (Leader BTSE; Participants: STS, NR, SMO, TD, TRV, AZD, HC, INDRA)
The objective of this task is to process the design of the prototypes TRL4 started in WP8 to TRL6 at the end of the project. Each demonstrator proposed will be designed and delivered by one partner.
Regular status updates demonstrating the progress of the design activities will be part of Task 1 of this work package.
All necessary activities related to the design of the prototypes shall follow the guidelines described in D6.4 of X2R2 WP6.
At the end of the design phase, the partners will provide reports for each demonstrator. These reports will be verified for completeness as required from the data management plan created in WP1 and will be consolidated into a summary report.
Sub-task Task - 10.2.1 Demonstrator TRL6 for Connected Driver Advisory System (Partner: STS)
The scope of work of this task is the development of a prototype that implements the computation of speed profile and driving modalities to feed a Connected Driver Advisory System (C-DAS); the development includes the definition of interfaces between the TMS and modules that provides the DAS functionalities. The work is based on the outcome of task 5.6.2 of .X2Rail-2 WP6.
Sub-task - 10.2.2 Demonstrator TRL6 for Conflict Prediction System (Partner: AZD)
This task focusses on the to design a prototype demonstrating complex Conflict Prediction System. The application will be realized by specifying and developing specific tools for handling regular and irregular traffic issues.
Sub-task - 10.2.3 Demonstrator TRL6 for Wayside ATO constituents (Partner:  BTSE)
The demonstrator developed under this task addresses the design of constituents needed for ATO GOA2 operation based on data management based on the integration Layer. The works comprise the subsystems and Interfaces needed to read data from the Integration Layer to create a JP and SP, the business function to create these profiles in CDM and the necessary processes to make these messages available at the API linking the ATO -TS to the Integration Layer.
Sub-task - 10.2.4 Demonstrator TRL6 for Integration of field status information (Partner: HC)
This task aims at the development of a Demonstrator  for modules for integrating field status information from trains, asset and train control into one single, consistent data source; train forecast calculation; possession management module for (re-)planning of maintenance activities and impacted trains; interfaces for data exchange with external resource management, train request and information services."
Sub-task - 10.2.5 Demonstrator TRL6 for TMS Business Applications (Partner: INDRA)
This task covers the provision of a demonstrator based on TMS Business Applications focused on the mitigation of the impact that traffic disturbances and unexpected infrastructure restrictions generate into the traffic evolution. Under these circumstances, for instance, the evolution of the scheduled maintenance works on the facilities are considered, as well as additional required actions arisen during the traffic operation based on the modification of the scheduled trains behaviour.
The implemented prototypes will be based on the Proofs of Concept performed in the X2RAIL-2 and they will expose a modular architecture complying with the specified Integration Layer and its Application Programme Interface in a laboratory environment and using a common data model.
Sub-task - 10.2.6 Demonstrator TRL6 for Conflict Detection and Resolution (Partner: SMO)
This task addresses the specification and development of business service applications for the detection of future conflicts, the presentation of the results to the operator and conflict resolution measures and integration them into operator's workflow. The SW application modules will be hosted in an Application Framework.
Sub-task - 10.2.7 Demonstrator TRL6 for Application Modules (Partner: Thales)
The task will continue the development of a number of the Thales prototypes developed in WP9 Task 9.3.7 to TRL6. This will include the deployment of environments for the Integration Layer, Core Operation Workstation and TMS and Asset Management applications. In particular the interaction between the TMS providing early indication of asset failure on the Integration Layer and selected features of the Standard Operator Workstation (from X2RAIL2 D6.5) including third party application HMI integration.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.
Each partner developing a prototype in the frame of this WP10 will provide to WP13 a “confidential information free” presentation/technical description of its prototype to be used during X2Rail-4 final event.

WP11 - Smart Wayside Object Controller. Demonstrators TRL 4

The goal is to take the activities started in X2Rail-1 WP7 project a stage further by developing demonstrators with TRL 4 to best support the concepts formulated during X2R-1.
Task 11.1 – Technical Coordination and System Integration (Leader: TD)
The leader will prepare reports, annual plans and call needs for the S2R IP2 coordinator and S2R JU and will attend IP2 SC meetings. Attendance to other Shift2Rail committees and dissemination events are expected too. The WP leader will also ensure technical coordination with other TDs in that IP or in others when relevant based on the dependency between TDs. And also, it is important to supervise the schedule of the demonstrations, in order to ensure the correct development and finalization of the demonstrators and manage the risks and mitigation actions. Overall project coordination will be supported by the task leaders.   
Task 11.2 – Definition of demonstrator specifications and test strategy (Leader: INDRA Participants: CAFS, SMO, BTSE, STS, AZD, TRV, TD, DB, RAILENIUM, MERMEC)
The objectives of that task are:
1. Definition of the specifications of System Requirements and System Architecture that will be covered in the demonstrators.
2. Definition of tests strategy and common principles to analyse test results to be applied for the demonstrators.
Task 11.3 – Development and Verification of selected demonstrators (Leader: SMO, Participants: CAFS, SMO, BTSE, STS, INDRA, AZD, TD, RAILENIUM)
The objectives of this task are to develop the laboratory functional models or prototypes following the specifications of System Requirements and System Architecture, to define and apply the tests to be done and to provide the laboratory test report:
1. Development of the prototypes following the specifications
2. Verification of the prototypes will take into account the environment for testing to reach a TRL 4.
As result of these tasks, every partner will provide the individual work with:
-    The description of the demonstrator
-    The results of the verification tests of the demonstrator
In this task the integration of the description and test results of the demonstrators generated as results of Sub-tasks 11.3.1 to 11.3.8 is completed.
Sub-task 11.3.1 – Development and Verification of WiLPOC (Wireless Low Power Object Controller) demonstrator (Partner: CAFS)
The development and verification of CAFS demonstrator will be performed in this sub-task.
The definition of the demonstrator is:
An autonomous object controller prototype to interface with ERTMS balises, signals and track circuits on areas far from stations. The object controller will be focused on Maintenance and Data Logging to allow a high availability of the system minimizing the onsite maintenance task. The object controller will also take into account minimizing the power consumption to allow a remote autonomous operation.. The autonomous power subsystem will be 100% renewable-based (solar+storage) and will be remotely monitorized to ensure its proper operation. The prototype will use secured IP based communications.
Sub-task 11.3.2 – Development and Verification of Track vacancy detection SWOC demonstrator (Partner: SMO)
The development and verification of SMO demonstrator will be performed in this sub-task.
The definition of the demonstrator is:
An object controller prototype, enabling track element management focused on Track Vacancy Detection (axle counters) with optional signal management and with safe and secured communication over wireless networks.
Specifically addressing:
-    The issues of scalability of the object controller networks
-    Communication between object controller and other systems using wireless technology
-    Reduction of power consumption and integration with a locally produced energy system.
Sub-task 11.3.3 – Development and Verification of Cable less Railway Embankment demonstrator (Partner: BTSE, TRV)
The development and verification of BTSE demonstrator will be performed in this sub-task.
The definition of the demonstrator is:
A basic meeting station consisting of two point-machines, an adjacent level crossing and necessary supporting field elements for train detection.
The prototype will contain features for easy installation, energy conservation, and predictive maintenance and for exchange of information with external systems.
Applicable standards and specifications from TD2.1 and TD 2.11 are planned to be integrated.
Based on the prototype, a model for the life cycle costs will be developed.
Sub-task 11.3.4 – Development and Verification of MuNeSS (Multiple Networks Scalable SWOC) demonstrator (Partner: STS)
The development and verification of STS demonstrator will be performed in this sub-task.
The definition of the demonstrator is:
A prototype of wayside object controller that will be able to communicate using the available heterogeneous wireless public networks (e.g. 2G/3G/4G, satellite, ..), instead of dedicated ones, in order to obtain target performances and to guarantee continuous connectivity, which will allow to improve service quality, offering advanced remote diagnostic and maintenance features of the smart object controller and controlled wayside object(s) with no impact on safe communications. SWOC demonstrator will be scalable and decentralized to permit minimization of required cabling.
Sub-task 11.3.5 – Development and Verification of SWOC network for managing WOs demonstrator (Partner: INDRA)
The development and verification of INDRA demonstrator will be performed in this task.
The definition of the demonstrator is:
Design and develop a SWOC for connecting a single-track element and the development of a Wireless Sensor Network for creating a network mesh (access nodes, transport nodes and gateways nodes). The integration of both developments will allow managing a single-track element from an IXL via wireless, through a closed network mesh that will facilitate the safe and secure communication as well as transparent routing for the IXL to the object to be controlled.
Sub-task 11.3.6 – Development and Verification of a LX Smart wayside objects demonstrator (Partner: AZD)
The development and verification of AZD demonstrator will be performed in this sub- task.
The definition of the demonstrator is:
The demonstrator will comprise a simple SWOC connected via radio connection to the IXL or, alternatively, to the level crossing (LX) controller. This SWOC will be able to control wayside objects commonly used at an LX – axle counter, gate signal, warning light, light signal or barrier drive. One or two wayside object types will be part of the demonstrator. It will be connected by a wireless link to the master IXL or LX controller and to a diagnostic and maintenance system. The power is provided either locally by an energy harvesting system or remotely over a cable.
Sub-task 11.3.7 – Development and Verification of WADILP (Wireless, Advanced Diagnosis, Intelligence distribution and Low Power consumption) SWOC for points machines demonstrator (Partner: TD)
The development and verification of TD demonstrator will be performed in this sub-task.
The definition of the demonstrator is:
A high efficient controlling of point machines as prototype with:
-    wireless communication for control entity connection
-    advanced diagnostic features of the smart object controller and the point machine;
-    specifically addressing the issue of optimized distribution of intelligence;
-    very low power consumption of the smart object controller (and requirements on the point machine) supplemented by autonomous power supply and storage
Sub-task 11.3.8 – Development and Verification of NEWNECTAR (New gEneration of adaptable Wireless sensor NEtwork for way side objeCTs in rAilway enviRonments) demonstrator (Partner: RAILENIUM)
The development and verification of RAILENIUM demonstrator will be performed in this sub-task.
The definition of the demonstrator is:
Development of a new generation of low-power and resource-constrained wireless sensor networks (WSN) for adaptive data collection and forwarding for railway environment. RAILENIUM will develop software define approaches. RAILENIUM will address the challenges both at physical layer and at higher layer. At Physical layer,  RAILENIUM will consider reconfigurability capabilities based on cognitive radio features such as spectrum detection and adaptable radio access technologies taking into account low energy consumption with algorithms implemented in Software Defined Radio (SDR) devices. The question of  antenna integration and solutions for energy harvesting will be also considered as well as radio propagation aspects for deployments. At higher level, RAILENIUM will consider Software Defined Networks (SDN) and Network Functions Visualization (NFV) techniques to demonstrate reconfigurability and adaptability when needed for example in case of flooding or other dangerous event in some part of the network.
Task 11.4 –Analysis and Evaluation of the demonstrators (Leader: SMO, Participants: CAFS, BTSE, STS, INDRA, AZD, TD, TRV, DB, RAILENIUM, MERMEC)
The analysis and evaluation of the demonstrator at TRL 4 phase will be used:
-    As an input for WP12 demonstrators
-    For updating of deliverables of X2Rail-1 project, if needed
-    As preliminary conclusions
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.

WP12 - Smart Wayside Object Controller. Demonstrators TRL 6

The goal is to take the technical demonstrators developed in WP11 a stage further in order to reach TRL 6.
Task 12.1 – Technical Coordination and System Integration (Leader: TD)
The leader will prepare reports, annual plans and call needs for the S2R IP2 coordinator and S2R JU and will attend IP2 SC meetings. Attendance to other Shift2Rail committees and dissemination events are expected too. The WP leader will also ensure technical coordination with other TDs in that IP or in others when relevant based on the dependency between TDs. And also, it is important to supervise the schedule of the prototypes, in order to ensure the correct development and finalization of the demonstrators and manage the risks and mitigation actions. Overall project coordination supported by the task leaders.   
Task 12.2 – Implementation and Validation of selected demonstrators (Leader: BTSE, Participants: CAFS, SMO, STS, INDRA, AZD, TD, RAILENIUM)
The objective of this task is the implementation, installation and validation of the prototypes in a representative environment.
Validation will be executed according to test and validation plans.
After implementation and installation of each demonstrator the expected results for each demonstration prototype will be:
-    First stage, the adaptation of validation plans and test description, including environment selection
-    Second stage, the preparation and the test execution.
At the end of this task it will be reached, in correspondence with the achievement of the following results:
-    Prototypes validation tests executed in operationally representative environment (simulation or field tests site) to reach a TRL 6.
-    Validation Test results
In this task the integration of the description and test results of the demonstrators generated as results of Sub-tasks 12.2.1 to 12.2.8 is completed.
Sub-task 12.2.1 – Implementation and Validation of WiLPOC (Wireless Low Power Object Controller) demonstrator (Partner: CAFS)
The implementation and validation of CAFS demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.1.
Sub-task 12.2.2 – Implementation and Validation of Track vacancy detection SWOC demonstrator (Partner: SMO)
The implementation and validation of SMO demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.2.
Sub-task 12.2.3 – Implementation and Validation of Cable less Railway Embankment demonstrator (Partner: BTSE, TRV)
The implementation and validation of BTSE demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.3.
Sub-task 12.2.4 – Implementation and Validation of MuNeSS (Multiple Networks Scalable SWOC) demonstrator (Partner: STS)
The implementation and validation of STS demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.4.
Sub-task 12.2.5 – Implementation and Validation of SWOC network for managing WOs demonstrator (Partner: INDRA)
The implementation and validation of INDRA demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.5.
Sub-task 12.2.6 – Implementation and Validation of a LX Smart wayside objects demonstrator (Partner: AZD)
The implementation and validation of AZD demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.6.
Sub-task 12.2.7 – Implementation and Validation of WADILP (Wireless, Advanced Diagnosis, Intelligence distribution and Low Power consumption) SWOC for points machines demonstrator (Partner: TD)
The implementation and validation of TD demonstrator will be performed in this sub-task.
The definition of the demonstrator is already included in Sub-Task 11.3.7.
Sub-task 12.2.8 – Implementation and Validation of NEWNECTAR (New gEneration of adaptable Wireless sensor NEtwork for way side objeCTs in rAilway enviRonments) demonstrator (Partner: RAILENIUM)
The implementation and validation of RAILENIUM demonstrator will be performed in this sub-task. The solutions designed and developed will be implemented. A demonstration in the field will be developed.  RAILENIUM will consider the possibility to implement in the Sense-City equipex in which flooding could be reproduced.
The definition of the demonstrator is already included in Sub-Task 11.3.8.
Task 12.3 – Analysis and Conclusion of demonstrators (Leader: BTSE, Participants: CAFS, SMO, STS, INDRA, AZD, TD, TRV, DB, RAILENIUM, MERMEC)
The analysis and evaluation of the demonstrator at TRL 6 phase will serve as an input for possible improvements on prototypes, specifications review and conclusions.
This WP will provide when needed the required expertise to support WP2 in the execution of its task 2.4.

WP13 - Exploitation, Dissemination & Communication

Task 13.1 – External Communication (Leader: DB, Participants: ALS, AZD, BTSE, CAFS, CEIT, DLR, HC, INDRA, MERMEC, NR, RAILENIUM, SMO, SNCF-R, STS, TFV, TD)
This task comprises of the following activities in alignment with the Shift2Rail JU communication strategy and activities:
As initial activity, the overall dissemination strategy for X2Rail-4 will be aligned with the S2R JU and other S2R projects, especially already ongoing IP2 projects (X2Rail-1, X2Rail-2 and X2Rail-3), in order to identify the most efficient ways to guarantee the maximum visibility for the X2Rail-4 project and an optimal deployment of the project results (deliverable D13.1). The task shall identify the participants in the Networks of End Users, the means of communication and collaboration and the content of the dissemination tools. The deliverable shall also include an overview about all the planned demonstrators of all X2Rail-4 WPs.
A project identity set will be created, containing elements such as a project logo, templates for presentations and reports, as well as a brochure presenting the project. These tools will follow the Shift2Rail design identity and will be harmonized with the design of the tools of the other IP2 projects. On the already existing public website of the JU another sub-section will be set up to represent X2Rail-4. This will make use of the existing solutions for the X2Rail-1, X2Rail-2 and X2Rail-3 projects and help connect the projects with each other. It will provide up-to-date, easy and quick access to shared requirements and further information in the project all along the project period.
Two Project Leaflets will be produced during the project life, one towards the mid-point and one towards the end. These will provide up-to-date information on the status and achievements of the project. An electronic version will be made available on the website. Dissemination of the leaflet will be done according to the dissemination plan.
In IP2 a common glossary for all WPs will be created. The work has been started in X2Rail-1, X2Rail-2 and X2Rail-3 will be continued also in X2Rail-4. For an easier external usage of this glossary, the content will be made public. Comments and feedbacks will be collected, in order to update the IP2 glossary, if necessary.
The final event conference of X2Rail-3 will additionally be used to discuss the progress of the X2Rail-4 project in M24. This conference will present the work undertaken until that point of the project and any results achieved. It will also look ahead to the future of the project.
A Final Event meeting will be held to present the results of the project, targeting a European audience and possibly open to selected non-European stakeholders. It could be envisaged to organise this event jointly with the consortia of other successful S2R projects. One session could be for all projects, with a second session being dedicated to the X2Rail-4 consortium. The content of the final event and the documents presented will be available within the Report on Communication and Dissemination activities (deliverable D13.3). This report will also be the official final document of the X2Rail-4 project.
X2Rail-4 will be presented at a number of European and international railway conferences and congresses such as UITP world congress, TRA, UIC ERTMS World conference, WCRR, Railway Forum, trade fairs and significant technical conferences. X2Rail-4 members will attend these external events as part of the dissemination activities.
Special attention will be given on the presentation of the project and its progress and results during the InnoTrans2022. This includes the presentation of demonstrators in the Shift2Rail stand.
RAILENIUM plans to disseminate and prepare some publications during the project. Furthermore, they plan to organize a scientific seminar with their partners of the SmartRaCon consortium and with the partners of X2Rail-4.
Task 13.2 – Management of networks of Advisory Groups (Leader: DB, Participants: ALS, STS, BTSE, TD)
This task will set up and manage an Advisory Group, to ensure that the work and results of the project can be disseminated directly to key target groups and feedback can be obtained immediately. By involving key stakeholders, and considering their feedback, this task can increase the chance of the acceptance of the results by the railway sector.
- A first step will be to identify the members of the Advisory Group to be included in such activities, and to create the group accordingly. This may include, but not be limited to, the European regulation and standards bodies (i.e. institutions and groups such as ERA, ISO/CEN/CENELEC/ETSI, UNISIG, EUG, ENISA, UIC, UITP, etc.) Basis for the creation of the group will be the work already foreseen in the ongoing IP2 projects X2Rail-1, X2Rail-2 and X2Rail-3. UR-ID will also be contacted when defining the composition of the Advisory Group.
- Furthermore, terms of reference for the group will be produced, in order to establish composition, working methods and frequency of meetings for the group. Opportunities for synergies with corresponding groups within the Shift2Rail initiative and especially within IP2 will also be taken advantage of.
Task 13.3 – Production and maintenance of Data Management Plan (Leader: DB, Participants: ALS, STS, BTSE, TD)
The Data Management Plan (deliverable D13.2) is to provide a description of the data management that will be used by the X2Rail-4 partners internally under leadership of WP2 and with external stakeholders with regard to all the datasets that will be generated by X2Rail-4. The Data Management Plan (DMP) will evolve during the lifespan of the project and will be based on the foreseen DMP to be created in the already ongoing IP2 projects X2Rail-1, X2Rail-2 and X2Rail-3. Presumably it will be taken up by the future Shift2Rail and especially IP2 activities. It will be developed accordingly to the Horizon 2020 guidelines and will reflect the agreed requirement for protection of the different data being shared. It will in particular set the data reference and name and description, it will provide the reference to relevant definitions and requirements in existing standards and/or regulations and provide also amendment proposals to them. It will generally describe how data will be shared and preserved.