The A2/M2 (London to Dover) Connected Vehicle Corridor

Transcription

1 The A2/M2 (London to Dover) Connected Vehicle Corridor April 16 Presentation Title (edit this in Insert > Header and Footer, then click 'Apply to All') 1

2 Background Derived from the Road Investment Strategy - Incentivise the advancement of in-vehicle, vehicle-to-vehicle, and vehicle-toinfrastructure technologies, through the provision of roadside Wi-Fi: Target M2, M20, M26, M25 A2/M2 (London to Dover) Connected Vehicle Corridor Partnership formed December 2014 Deliver real-world capabilities research to deployment Create a living laboratory for testing and evaluating technologies Budget 2016 establish a 15 million connected corridor from London to Dover to enable vehicles to communicate wirelessly with infrastructure and potentially other vehicles Highways England Innovation Strategy April A2/M2 (London to Dover) Connected Vehicle Corridor

3 The A2/M2 Connected Vehicle Corridor 3 A2/M2 (London to Dover) Connected Vehicle Corridor

4 Progress Preparation for detailed design stage. Defined, procured and managed a series of feasibility studies a) identify services and infrastructure for the pilot b) provide framework for impact assessment c) define data management requirements/new services Track tests being undertaken in May Deployment strategy commissioned (retro-fitting vehicles) Further studies - framework for industry to test equipment - capability and capacity of 5.9GHz - retro-fitting connected vehicles 4 A2/M2 (London to Dover) Connected Vehicle Corridor

5 Day One Services April 16 Defined by partners, supported by feasibility road works information; roadworks warning data; in-vehicle signing; probe vehicle data; signal phasing information (urban C-ITS) freight services Consistent with C-ITS Platform (EU) and interoperable with other Corridors. 5

6 Possible data-led services Unplanned Event within connected area Unplanned Event within Travel Area Roadworks Freight operations Major Traffic Generator within connected area Significant incident within connected area Family travelling through connected area Heavy Goods Vehicle parking adjacent to the connected area 6

7 Use Case 1 Use Cases Assessment of Data Coverage and Gaps Information Services Incident Location and Impact Data Requirements Network Model Data Catalogue Data Gaps Common Network Model Use Case 2 Delay Information Current Link Journey Times MIDAS Data Use Case 3 Alterative route options Future Link Journey Times CITS PVD Incident Clearance Time Service providers Journey Times Return to Normal Time Incident Impact & Duration Model

8 (DRAFT) Potential core C-ITS Data Management System Corridor Dashboard Application Probe Vehicle Application User Trust Management Core System Network Services Transport for London TCC Highways England TCC Roadworks Information Application User Permissions Time Synchronisation Core2Core Kent CC TCC In-vehicle signage Application Misbehaviour Management Service Monitor Data Distribution National Access Point (NAP) SPaT /Map Application Roadside ITS Stations ITS G5 3G/4G In-vehicle ITS Stations 3G/4G Mobile ITS Stations C-ITS Corridors Core Systems PVD App PVD App PVD App Roadworks App Roadworks App Roadworks App Signage App Signage App Signage App SPaT / MAP SPaT / MAP SPaT / MAP 8

9 Challenges High ambition to develop innovative C-ITS applications Harvesting UK industry Data management/hub/iot and data-led services European policy/regulation Security and data privacy Standards Integration UK (C-ITS Deployment Board) and European level 9

10 INTERCOR Study demonstrating a coordinated large-scale interoperable deployment of C-ITS services through Netherlands, Belgium/Flanders, UK and France Cross border interoperability by ensuring interoperability testing, Security and Certification and seamless continuity of service Provide C-ITS services on a larger scale by specifying, using and fostering hybrid communication Strategic cooperation between C-ITS front running countries - to develop and apply a common deployment framework 10

11 Connecting Corridors the Intercor proposal 11 Intelligent Transport Systems

12 Strategic objectives 12

13 Tactical objectives Cross border test and harmonisation of current C-ITS Day One services (FR, NL) Create basis for further C-ITS development (NL, BE, FR, UK) Develop, test and pilot C-ITS platform outputs (security and hybrid communication) Learn by doing and exchange of knowledge/experience (BE, UK) Design, develop and test new freight/logistic C-ITS service 13

14 A2/M2 Programme 14