TD 4.1 - Interoperability Framework
The aim of the ‘Interoperability Framework’ (TD4.1) is to facilitate multimodal travel in a highly diverse environment and with many transport modes. The world of transportation service providers needs to be open-ended; it evolves at its own pace, and uses multiple data formats and interfaces. Interoperability at the semantic level defines formal and explicit models of the transportation domain in an open, standard, machine-readable language that is exchanged automatically by computers.
Implementation within IP4 projects
Currently available deliverables:
D2.1 Analysis of the demand of travellers for the TC
D2.2 Analysis of the demand of market actors for the IF
D2.3 Analysis of impacts on the governance solution
D3.1 Regulatory Environment (interim)
D3.2 Regulatory Environment (final)
D4.1 Initial Semantic Interoperability Technology Market Watch
D4.2 Synthesis of the Semantic Interoperability Technology Market Analysis
D5.2 Toolkit of recommendations and KPI Scoreboard
D3.1 Annotations for mapping from legacy data models to ontologies
D3.2 Extension to the S2R reference ontology
D3.3 Mapping between standard and reference ontology
D4.1 Analysis of state of the art ontology conversion tools
D4.2 Software release of archetypal implementation of converters
D4.3 Mapping between standard and reference ontology
D4.4 Adaptation of Archetypal implementation
D5.1 Requirements for the Demo
D5.2 KPI and Metrics for Evaluation
D5.3 Demonstration Platform ready for test
D5.4 Report on the Results of the Pilot
D5.5 Report on the results of IT2Rail semantic broker demonstration scenario
D1.1 -Architectural Principles and Design_ C-REL - v4
D1.2 -Architectural Principles and Design_ A-REL
D1.5 - Interoperability Framework Components A-REL
D2.1 Initial analysis of requirements of S2R IP4 projects and other EU initiatives
D2.2 Requirements for an IF architectural design (C-REL)
D2.3 Requirements for an IF architectural design (F-REL)
D2.4 Recommendation to IP4 – intermediate version
D2.5 Recommendation to IP4 – final version
D3.1 State-of-the-art and best practices in architecting systems processing semantic data
D3.2 Performance and scalability requirements for the IF (C-REL)
D3.3 Design of Architecture_ Testing Infrastructure_ Test Cases and Benchmarks of the IF (C-R
D3.4 Requirements Analysis and Design of Architecture, Testing Infrastructure, Test Cases and Bench
D4.1 Analysis of the state-of-the-art
D4.2 A lightweight solution to automate the generation of ontologies_ mappings and annotation
D4.3 A lightweight solution to automate the generation of ontologies, mappings and annotations (F-R
D5.1 Requirements_ scenarios and use cases for the proof-of-concept (C-REL)
D5.3 Validation of pilot implementation (C-REL)
D5.4 Requirements, scenarios and use cases for the proof-of-concept (F-REL)
D5.6 Final report on the results of the validation of pilot implementation
D3.2. Source code of Algorithms for optimal synchronisation of shared-mobility and mass transit
D3.3 Crowd-based Travel Expert Service
D3.4 Travel Companion enhancements
D3.5 Ride-Sharing Agreements Ledger Module
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.
TD 4.2 - Travel Shopping
The ‘Travel Shopping’ (TD4.2) aims to provide a comprehensive shopping application enabler which combines all modes of transport, all operators and all geographies, and provides a list of customer-relevant trip offers which are guaranteed available for booking, purchase and ticketing. The IP4 approach will promote the integration of distributed travel operators’ data and the orchestration of services such as expert journey planning. It will be facilitated by the Interoperability Framework by enabling applications based upon different standards or coding lists, to communicate meaningfully but without costly application adaptations.
Implementation within IP4 projects
Currently available deliverables:
D1.1 – WP1 Travel Shopping CREL Ontology
D1.2 – WP1 Specifications CREL
D1.3 – CREL (Core Release) Implementation Report WP1
D1.4_S2R-IP4_Ontology_TS_final
D2.2 - TD4.2 Travel Shopping FREL Implementation Report
D2.1 First conceptualization of choice criteria and incentives
D2.2 State-of-the-art of ride-sharing in target EU countries
D2.3 First set of requirements and specification for complementary travel expert services
D2.4 Final conceptualization of choice criteria and incentives
D2.5 Recommendations and criteria for a successful ride-sharing in the IP4 ecosystem
D2.6 Final set of requirements and specification for complementary travel expert services
D3.1 Evolutions of IP4 Components Specifications Report
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.
TD 4.3 - Booking & Ticketing
The ‘Booking & Ticketing’ (TD4.3) will orchestrate multiple but parallel interactions with several booking, payment and ticketing engines, including the all-important roll-back activities, should any single transaction fail, in order to eliminate risk. Thanks to the concept of a unique traveller identifier and wallet, the traveller will have easy access to the complete and integral components of his/her journey, including easy production of the entitlement tokens required for all ticket validation controls encountered en route. It will radically simplify the traveller’s life, by abolishing uncertainties associated with ‘behind-the-scenes’ multiple booking, payment and ticket processes.
Implementation within IP4 projects
Currently available deliverables:
D2.1 – WP2 Booking & Ticketing – CREL Ontology
D2.2 – WP2 Booking & Ticketing – CREL Specification
D2.3 – WP2 Booking & Ticketing – CREL Implementation Report - PDF
D2.4 - TD4.3 FREL Ontology (PDF)
D2.5 - TD4.3 FREL Specification (PDF)
D2.6 - WP2 Implementation Report - FREL - PDF
D4.2 - TD4.3 Booking and Ticketing Implementation Report
D10.1 - Contractual Management FREL Specifications
D10.2 - Contractual Management FREL Implementation Report
D2.1 First conceptualization of choice criteria and incentives
D2.2 State-of-the-art of ride-sharing in target EU countries
D2.3 First set of requirements and specification for complementary travel expert services
D2.4 Final conceptualization of choice criteria and incentives
D2.5 Recommendations and criteria for a successful ride-sharing in the IP4 ecosystem
D2.6 Final set of requirements and specification for complementary travel expert services
D3.1 Evolutions of IP4 Components Specifications Report
ExtenSive_D5.1_SaaS Solutions Specification Report
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.
TD 4.4 - Trip Tracker
The ‘Trip-tracker’ (TD4.4) will give travellers in-trip assistance when navigating transport nodes, while also providing personalised information (related to predefined preferences) and up-to-date status reports on subsequent legs of the journey; it will support them in case of disruption, by proposing updated booking possibilities together with updated rights to travel.
Implementation within IP4 projects
Currently available deliverables:
D1.5 FREL Implementation Report
D3.2 CREL Synchronisation Report
D2.2 Model for analysing a user_s trip purpose (activities)
D2.3 Modelling framework for analysing user_s choices
D2.5 Continued assessment and improvement of the modelling framework
D4.2 Affective and Persuasive HMI concepts and models
D4.3 Lifelong training schemes for My-TRAC users
D4.4 Continued assessment and improvement of the Human-Machine Interface
D5.1 Elicitation of requirements document for My-TRAC
D5.4 Final version of My-TRAC application
D6.3 Roadmap for application improvements and extension
D6.2 - TD4.4 Trip Tracking - FREL Implementation Report
D10.1 - Contractual Management FREL Specifications
D10.2 - Contractual Management FREL Implementation Report
D5.2. MaaS Assessment Tool
D3.1 Evolutions of IP4 Components Specifications Report
ExtenSive_D5.1_SaaS Solutions Specification Report
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.
TD 4.5 - Travel Companion
The traveller will have full control of the journey, thanks to their own personal and secured ‘Travel Companion’ (TD4.5), which stores and shares their personal preferences in a wallet. It will give access to all travel services needed for the journey, shopping and booking, and allow storage of the rights to travel. At the same time, retailers and operators will be able to identify and authorise the Travel Companion to access their own systems and networks.
Implementation within IP4 projects
Currently available deliverables:
D2.2 CREL Implementation Report
D2.5 FREL Implementation Report
D3.2 CREL Synchronisation Report
D2.2 Model for analysing a user_s trip purpose (activities)
D2.3 Modelling framework for analysing user_s choices
D2.5 Continued assessment and improvement of the modelling framework
D3.4 Analytics Framework algorithms calibration
D3.5 Continued assessment and improvement of the user-service algorithm
D8.2 - TD4.5 Travel Companion FREL Implementation Report
D4.2 Monitoring indicators and targets
D1.1-Travel Concerns components specification report
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.
TD 4.6 - Business Analytics Platform
All the services related to individual travels and to additional sensors will generate a great deal of data which have great value for both operators and end users. It will be the role of the ‘Business Analytics’ (TD4.6) to manage those data. Novel ‘big data’ technologies such as ‘intentional’ semantic information (denoting objects by properties rather than by values) will improve the capabilities to analyse distributed and heterogeneous linked data, creating numerous possibilities to generate unprecedented insights for all the actors of the ecosystem, and new intelligence for the benefit of operators and travellers.
Implementation within IP4 projects
Currently available deliverables:
D2.1 Analysis of the demand of travellers for the TC
D2.2 Analysis of the demand of market actors for the IF
D2.3 Analysis of impacts on the governance solution
D3.1 Regulatory Environment (interim)
D3.2 Regulatory Environment (final)
D4.1 Initial Semantic Interoperability Technology Market Watch
D4.2 Synthesis of the Semantic Interoperability Technology Market Analysis
D5.1 Requirements for the Demo
D5.2 KPI and Metrics for Evaluation
D5.3 Demonstration Platform ready for test
D5.4 Report on the Results of the Pilot
D5.5 Report on the results of IT2Rail semantic broker demonstration scenario
D2.1 Big Data Architecture
D2.2-Big Data Architecture AREL
* D2.3 - Big Data Architecture F-REL
D2.4 Needs and related features
D2.5-Needs and related features AREL
D2.7 - Data Management Analytics Visual Analytics C-REL
D2.8-Data Management Analytics Visual Analytics AREL
D7.2 IP4_CDM data integration use case demonstrator definition
EXTENSIVE-S2R-D7.1_DSS algorithm specifications and data collection
* Please note that this/these deliverable(s) is/are undergoing S2R JU review and acceptance processes.
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.
TD 4.7 - Overall IP4 Coordination and Demonstrations
Although IP4 is organised around six Technology Demonstrators (TDs) with clear and non-overlapping objectives, all input will contribute to a specific IP4-integrated Technical Demonstrator (iTD4.7), which will act as the orchestrator of other TDs’ developments, and which will ensure the systems approach to integrate the different TDs’ results.
Implementation within IP4 projects
Currently available deliverables:
D3.1 – WP3 Business and Contractual Management – CREL Ontology
D3.2 – WP3 Business and Contractual Management – CREL Specification
D3.3 – WP3 Business and Contractual Management – FREL Ontology - PDF
D3.4 – WP3 Business and Contractual Management – FREL Specification - PDF
D4.1 - CREL Synchronisation Report (PDF Version)
D4.2 Implementation Report - CREL - Pdf
D4.3 - WP4 Synchronisation Report - FREL - PDF
D4.4 Implementation Report - FREL - PDF
D1.1 Technical Principles Description
D1.2 Data management Plan
D3.1 Report on major “needs” to address
D3.2 Report on major needs to address (Final version)
D3.3 User profiles and use case definition and description (initial version)
D3.4 User profiles and use case definition and description (final version)
D5.1 Definition of the demonstration for the Alfa Release
D5.2 Definition of the demonstration for the Beta release
D5.3 Definition of the demonstration for Final release
D5.1 Requirements_ scenarios and use cases for the proof-of-concept (C-REL)
D5.3 Validation of pilot implementation (C-REL)
D5.4 Requirements, scenarios and use cases for the proof-of-concept (F-REL)
D5.6 Final report on the results of the validation of pilot implementation
D.4.2. Impact assessment: Demand, costings, business models and regulation
D5.1 Project logo and website
D5.5 Interim Stakeholders consultation report
D5.6 Final Stakeholders consultation report and additional use-cases
D2.1 Technology survey, C-REL
D2.2. Demonstration requirements and scenarios, C-REL
D2.3 Demonstration requirements and scenarios, F-REL
D3.1 List of operational KPIs, analysis of the users’ satisfaction and methodology, C-REL
D3.2 List of operational KPIs, analysis of the users' satisfaction and methodology as a whole, F-REL
D4.4. User engagement strategy per each demonstrator
All deliverables, results and publications herewith provided reflects only the author's view and the S2R JU is not responsible for any use that may be made of the information it contains.