The SPRINT project will deliver results that are an integral part of the Shift2Rail IP4 work programme, in close continuity with previous and complementary projects in this domain.
Some of these IP4 projects have been funded through Open Calls (OC) – i.e. ST4RT, GoF4R, My-TRAC, and some others through Calls For Members (CFM) – i.e., Co-Active, ATTRACkTIVE, COHESIVE and CONNECTIVE.
Prior to these OC and CFM projects, the IT2Rail project, which is one of the four “lighthouse” projects that started before the Shift2Rail JU was set up, is the project that kick-started the IP4 activities, addressing all of the Technology Demonstrators in this particular Innovation Program.
As shown in the figure, SPRINT will start its activities with the assessment of the results produced by the related IP4 TD4.1 projects IT2Rail, GoF4R and ST4RT. Moreover, SPRINT will assess the first outcomes from CONNECTIVE, expected in December 2018. SPRINT will remain compatible with the approach currently developed within IP4, to allow the adaptation of the IF mechanisms developed in the parallel complementary project CONNECTIVE. The project will also collect requirements concerning the usage of the IF from ATTRACkTIVE, Co-Active, My-TRAC, COHESIVE and from future TD4.2-TD4.7 CFM/OC projects, even if not directly involved in TD4.1 development. Since these projects make use of the IF to offer to the customer more intuitive and engaging services for door-to-door intermodal journeys, the solutions proposed by SPRINT will also empower these services in terms of performance and scalability. Furthermore, since SPRINT aims to define and use realistic target KPIs to evaluate its solutions, past and ongoing Shift2Rail Cross-Cutting Activities (CCA), such as the results of the projects IMPACT-1 and IMPACT-2 on enabling the monitoring and assessment of the Shift2Rail overall target achievements, will be investigated and a close cooperation with these CCA is expected. The implementation will be validated according to defined functional and non-functional KPIs in relevant use case scenarios with the objective to define recommendations for IP4 to support the market uptake by simplifying / automating all the necessary steps which are needed to integrate new services and sub-systems in the multi-modal transport ecosystem.
