1. Transport Implementation of ITS Directive 2010/40/EU Priority Action "A" The Provision of EU-wide Multimodal Travel Information Services UK PTIC, Nottingham, 16 February 2016

2. ITS Directive 2010 | 2 Objectives Establish a framework for coordinated and effective deployment and use of ITS within MS and across borders Develop specifications necessary to ensure the compatibility, interoperability and continuity for the deployment and operational use of ITS for priority actions Framework for the Coordinated and Effective Deployment and Use of Intelligent Transport Systems

3. ITS Directive: two-step approach Step 1: specifications according to Article 5 developed with MS experts Step 2: Mandated deployment (if deemed necessary, eCall etc.)

4. ITS Directive: Priority Actions a)the provision of EU-wide multimodal travel information services b)the provision of EU-wide real-time traffic information services; c)data and procedures for the provision, where possible, of road safety related minimum universal traffic information free of charge to users; d)the harmonised provision for an interoperable EU-wide eCall e)the provision of information services for safe and secure parking places for trucks and commercial vehicles; f)the provision of reservation services for safe and secure parking places for trucks and commercial vehicles.

5. Why is the provision of EU-wide multimodal travel information included in the ITS Directive? 1/2 Support the promotion of sustainable modes of transport and modal integration relieving congestion and reducing pollution provide travellers with an overview of all possible travel options available to them tailored to their individual travelling needs provide travellers with pre-trip and on-trip information so they are better prepared during disruptions Improve accessibility and support travellers with reduced mobility

6. Why is the provision of EU-wide multimodal travel information included in the ITS Directive? 2/2 In 2013 300 million cross-border trips were made in the EU [EUROSTAT] – not including single day return trips. Travellers need door-to-door travel info not just point-to- point info. ModePercentage Air53% Rail5% Bus/coach6% Motor vehicle30% Waterway5% Other1%

7. UK-EU Travel Information Demand Total number of visits to UK from EU 2010 - 2014 – 23m Total number of visits to other EU countries from UK 2010 - 2014 – 43m

8. Multimodal Travel Information Services in the EU Type of service provider: both public and private transport operators, public authorities and private service providers Geographical coverage: limited EU-wide coverage, mainly MS/regional focused. No 'door-to-door' coverage. Travel option/modal coverage: limited 'multimodal focus' – only one or two modes Type of information provided: mainly static information, insufficient real-time information

9. Scope of priority action "a" | 9 "The definition of the necessary requirements to make EU-wide multimodal travel information services accurate and available across borders based on one or more of the following types of provisions: functional provisions describing the roles of various stakeholders and the information flow between them technical provisions providing for the technical means to fulfil functional provisions organisational provisions describing procedural obligations of the various stakeholders service provisions describing the levels of services and their content Information and Planning, NOT ticketing

10. ACCESS/EXCHANGE DATA ACCESS/EXCHANGE DATA OR LINK SERVICES 1. Monolithic / “Centralised” De-centralised True Distributed De-centralised Hybrid / Chained Different approaches to support EU-wide Multimodal Travel Information Services Data – must be easy to access and easy to exchange Services – must be interoperable

11. National Access Point MS are already required through the real-time traffic information specifications (priority action 'b' and 'c') to set up a NAP Type of NAP - Minimal level: national data register - Comprehensive level: national database MS to select most suitable type of NAP not EU

12. Type of data - Pre-existing data within MS, no requirements to collect or digitize information (Article 5 ITS Directive) - Requirements for at least static data, dynamic data at the discretion of the MS - Identified data prioritized into 3 groups – phased approach to complete NAP

13. Group 1 static data Address identifiers, points of interests, access nodes, geometry of access nodes, network topology, timetables, accessibility information, road/cycle/pedestrian network etc. Group 2 static data Car-sharing, bike-sharing stations, refuelling points, bike parking, basic ticket information etc. Group 3 data static data Detailed cycle network attributes and estimated travel times by day type and time-band etc.

14. Group 1 dynamic data Disruptions, real-time status information - delays, cancellations, guaranteed connections monitoring, status of access nodes (platform information, operational lifts/escalators, closed entrances and exit locations) Group 2 dynamic data Car-sharing availability, bike sharing availability etc. Group 3 data dynamic data Car parking spaces (on-street) etc.

15. Geographical scope Static Data groupComprehensive TEN-T incl. Urban Nodes Other parts of network Level of service 12019 2023 Level of service 22020 Level of service 32021 Dynamic data – if MS choose to include dynamic data in the NAP, they are encouraged to follow the above timeframe but no obligation to do so

16. UK Urban Nodes COMP TEN-T Birmingham Bristol Edinburgh Glasgow Leeds London Manchester Portsmouth Sheffield

17. Data exchange standards at NAP Relevant legislation/activities to be 'grandfathered' into specifications: Rail – TAP TSI Road – Priority action 'b' (DATEX II) Air – IATA SSIM New: Other scheduled modes – use of CEN NeTEx and CEN SIRI in NAP

18. Transport Data exchange standards and NAP National formats across all modes NAP NeTEx/SIRI DATEX II TAP-TSI IATA Translation Data Mapping

19. European Context

20. Linking services WHAT - Demand-based obligation to link public travel information services at local, regional and national level HOW - Recommendation of CEN OPEN API standard for distributed journey planning (Roger Slevin coordinator of CEN WP)

21. Data updates - When changes occur, data should be updated via the NAP in a timely manner - Responsible stakeholders shall in a timely manner correct any inaccuracies detected by them in their data or signalled to them by any user and end users.

22. Service Quality Provisions Service providers shall be transparent in the way travel options are ranked i.e. what criteria has been used

23. Common T&C When 3rd parties use travel and traffic data from NAP they must indicate the original source of the data and date of last update

24. Next steps Two MS Expert Meetings Further Stakeholder Consultation Inter-Service Consultation ITS Advisory Group // ITS Committee Translation (2 months) Right of scrutiny EP/Council (4 months) Adoption European Commission Expected agreed adoption – 4Q 2016

25. stephanie.leonard@ec.europa.eu