Deliverables
A white paper on the Business Case for interoperable ABT is published.
SMART System Requirements for embedding privacy measures in local travel scheme systems. Stating acceptable operation parameters and the certification bandwidths and thresholds to be used for service level monitoring. SMART Contract Requirements for: • Data Owners/Subject (Traveller) • Data Processors (Merchant, Service Provider, Travel Scheme) • Data Traders (Third Party opt-in data processors offering value for insight) • Credential Creation & Authorization Processors
A document that describes the franchise structure for the ETC, and will be used for the franchise contracts.
A document that describes the design and full scope of the pilots.
Plan for expansion of the Lab, consisting of the following: a. Infrastructure & Software Plan b. Connectivity Plan c. Connected Solution Testbench d. Pilot Use Cases e. Test Plan Schedule
Document that describes the design elements, interfaces, APIs. core components and common standards necessary for the interoperable provisioning of the following services to Travellers travelling in a foreign travel scheme or between two or more Travel Schemes: - Interoperable Journey Planning - Interoperable Account Based Ticketing - Interoperable Real-Time Travel Information
A document that includes all the up-dates resulting from the Grant Agreement preparation phase.
Functional specifications document which describes: - Interoperable User Account Creation - Travel Scheme SSO Connect - ETC Connect for Services - ETC Onboarding Workflow Interface - Interoperable Payment Method Bundles - ETC Connect for Payment Methods - Interop Hub Fund Transfer Matrix - Interoperable Ticket Pouch - Open Standards & Requirements - Reference Web & Mobile Apps
In this document the overall test plan and test strategy is described with input from all the work packages. Also all relevant pilot use cases will be included in this document.
Statutes of the European Travellers Club, a not-for-profit entity, to be set up.
A detailed document which provides the results of the pilot, based upon the Test and evaluation Plan. This report will be used to draft the overall Final Report.
Report with specifications for cross-border Mobility-Information.
This document specifies the different test cases, used in the interoperable testing.
A document with the results of the whole programme. This will be presented in the final stakeholder meeting.
Report with results of the end-to-end tests.
A detailed document for the execution of the pilots, based on the input from work packages <11>, <12> and <13>.
A document that describes the whole programme with milestones, planning, scope, work packages, relation between work packages, communication, budget, risks etc.
The business plan document for the ETC.
A license agreement which is aligned with the business model requirements as set forth in work package 3.
This is the final test report.
Document that describes the low-cost implementation strategy for existing and greenfield (including the SAM based implementation of the GST terminal).
Design documentation of the central authentication and routing hub including system of hubs and token ID-management.
The franchise contracts for the members of the European Travellers Club.
Based upon the final report and the results of the final stakeholder meeting this report will not only focus on the results of the programme, but also on the recommendations for the (near) future.
This test reports consists of: - 2 test reports of the GST token test suite execution. - 3 test reports of the GST terminal test suite execution. - 3 test reports of GST v2 integration and interoperability.
A white paper that describes the whole eco-system for interoperable account-based ticketing.
A detailed document with results of the pilot, based upon the Test and evaluation Plan.
A detailed document which describes the test entry and exit criteria and the criteria for evaluating the pilot.
Open Standards document that will be published and can be used by other parties to implement a Interoperable Account System and connect it to the central authentication and routing hub of the ETC.
Detailed design incorporating the relevant best practices for security, privacy and single sign on in the context of a Pan European Account Based Ticketing Solution with federated local multifunctional services and payment methods. Designed to function tightly with the ETC Hub interfaces and security & privacy controls but flexible enough framework to allow each country some freedom in how they choose to implement portions thereof in their home country.
Translate Standards and Requirements for Incorporation in the German eTicket standard. Specifications from relevant work packages are translated into the technical environment and the rules and regulations of the German eTicket standard so that the German-pilot can be copied to each other e-ticket implementation in Germany.
Open Standards document that will be published and can be used by other parties to implement a Interoperable Travellers Interface and connect it to the central authentication and routing hub of the ETC.
Audit Procedures for: Data Processors, Data Traders & Credential Processors.
This document describes: - a specification of the GST v2 to be used for the implementation on both NXP platforms and Java Card platforms. - the transaction interfaces between the GST-token and the terminals. - the transaction interfaces between the terminal and the central authentication and routing hub.
The standards, requirements and performance benchmarks for the ETC Hubs will be published to allow Travel Schemes wishing to develop their own local or regional hubs the chance to.
The validators in the Netherlands vehicles must accept the unique identifier which is stored on the German smartcard in public transport. This approach allows the current VDV travelers to use their existing VDV-card and the new (pilot) users to use the OV-chipkaart to pay for the trip and ‘travel on account’.
Reservation- and ticketing platform ready and based on the principles of Account based Ticketing.
The validators in the German vehicles must accept the unique identifier which is stored on the Dutch OV-chipkaart. This approach allows the current VDV travelers to use their existing VDV-card and the new (pilot) users to use the OV-chipkaart to pay for the trip and ‘travel on account’.
Prototyping & Staging Server for the Lab.
A showcase for the pilot teams and stakeholders in the Lab.
Test of the use cases of the Dutch Pilot in the ETC lab in Amersfoort.
End of the Dutch Pilot
Mobile Travel App ready to provide access to all website functionality and including a ticket feed in which transactions are shown, as soon as they are received from the front-end terminals.
ABT-systems connected with pilot region.
In this test suite all tests are described, programmed for: - the testing of transactions between token and terminal. - the testing of transaction between the terminal and the central authentication and routing hub.
Start of the pilot in Luxembourg
Based upon the specifications of the version 2 the token will be implemented on a Java Card based platform (chip).
Equipment ready to be used in the pilot with ABT software integrated.
End of the German Pilot
Demo system ready with Demo Interfaces, Open API, Demo Reference Mobile Apps
Fare Medium for travellers with ETC-token ready.
This portal will be used to communicate with stakeholders and users of the ABT (in the different pilots). During the whole period of the programme this portal will be used to communicate, receive feedback with above mentioned groups.
Demo System ready to select and integrate core back-end components in concert with a reference Mobile App Front end for demonstration purposes. Conduct User Panels to refine User Experience.
