Deliverable D1.7 Report on collaboration activities and guidelines for  TSPs joining the IP4 ecosystem
Creators: name: Rizzi, Giuseppe
name: Petrakou, Zoe
name: Stroumpou, Ismini
name: Trzaskowska, Marta
name: Kortsari, Annie
name: Mitropoulos, Lambros
name: Altobelli, Emiliano
name: Mariorenzi, Luca
name: Topolevec, Gordan
name: Jurankova, Petra
name: Rossi, Matteo
name: Bassi, Nicola
name: Cartolano, Fabio
Publisher: name: Zenodo
Year: 2023

description: D1.7 presents an overview of S2R ecosystem, with a specific focus on Innovation Pillar 4: its main features, its challenges, its technical demonstrators, the research and innovation activities performed and the main objectives and outcomes. A calendar of IP4MaaS and CFM (Call For Members) meetings and interactions was presented, in order to showcase all the different occasions in which, formally and informally, the projects had the opportunity to exchange. Official Collaboration meetings have been organized regularly in order to coordinate the collaboration between consortia. Additional meetings have been organized around a specific topic every time it was needed. The interaction facilitated the exchange of material (in particular accesses, documentation, GTFS files, APIs, credentials) needed for the integration of TSPs in the S2R ecosystem, it allowed the preparation and execution of demos. In some case, it helped the project actors to get familiar with the IP4 ecosystem. To facilitate this, as a joint exercise carried out by IP4MaaS and RIDE2RAIL projects with the support of CFMs partners, an “IP4 Terminology and Glossary” Excel file was kept constantly updated by OC partners (in particular UITP, CEFRIEL, AITEC, POLIMI). The aim of the glossary is to help OC and CFM projects to use in their activities the same glossary, harmonizing as much as possible the terminology used not only in the official documentsbut also in the day-to-day project activities. A comprehensive list of functionalities utilized and tested within IP4MaaS is presented in this document, highlighting its main features and nature (passive/active according to CFMs nomenclature). An overview of all the requirements to integrate each of the functionalities selected by each demo team is also provided. This facilitates each potential TSP willing to be integrated in the ecosystem to understand the requirements (APIs, web services, GTFS, GeoJson coordinates, among the most relevant) needed for the integration. To facilitate the understanding of the process to be followed for being integrated, the description of the integration process per each TSP in each demo site is presented, with the support of public deliverables issued by CFMs projects and the support of demo actors involved in IP4MaaS.Finally, recommendations for a smooth integration of TSPs and involvement of users are provided, with some lessons learnt coming from the demo preparation and execution process. As supporting tools, the overall IP4 glossary, developed jointly by Open Calls (RIDE2RAIL-IP4MAAS) and CFMs project partners and kept updated throughout the project by all these partners coordinated by UITP, is provided as Annex.The list of technical requirements for each of the IP4 functionalities has been provided as Annex II. This would help the reader to understand the requirements that each TSP/mobility service provider should provide for being part of the IP4 ecosystem.