Cooperative ITS Corridor Joint Deployment Amsterdam Group CODECS Workshop Roskilde, 15 September 2015
The official start On 10 June 2013, the Ministers of Transport of the Netherlands, Germany and Austria signed the Memorandum of Understanding on the setting up of the C-ITS Corridor. 2
3 The main partners
The first services The first applications in the corridor Rotterdam Frankfurt/M. Vienna 4
Strategic Goals The C-ITS corridor provides an international basis for standardized and forward-looking cooperative ITS services Coordinated implementation of first cooperative applications in the C-ITS Corridor Safe and efficient mobility through cooperative services Joint approach pursued by road operators, the automotive industry and mobility service providers Basis for the gradual introduction of cooperative systems in Europe 5
Three main phases 1. Preliminary development and "proof-of-concept" with roadworks warning trailers in Hesse around Frankfurt/Main, by extending the Dutch test environment DITCM, and within the Austrian project ECO-AT The corridor is the basis for the further development of cooperative services. 2. Introduction of the two first applications in the Cooperative ITS Corridor (NL DE AT) Road Works Warning Improved traffic management by cooperative vehicle data 3. Rollout on a national level 6
Time schedule of the German C-ITS Corridor part today Spring 2016 End 2016 2014 2015 2016 2016 2017 System Architecture IT-Security and Privacy Iterative Specification, Development and Testing of ITS Central Station (IRS) and ITS Roadside Station (IRS) Trial operation Rollout Participation of the automotive industry in each test cycle Operation and Evaluation Status: 31.08.15 7
C-ITS Corridor organization Supervisory Board Steering Group (NL) Coordination Committee (DE) Steering group National Coordination (AT) International Strategic Coordination Team (ISCT) International Operational Coordination Team (IOCT) Yellow Group National Project Groups (NL) National Project Groups (DE) National Project Groups (AT) 8
National project groups in Germany PG 0 Project Management PG 1 System Architecture Ideal timeline PG 2 ICS cooperative central station PG 6 Privacy and IT Security PG 3 Interlinking ICS PG 4 IRS cooperative roadside infrastructure PG 5 IVS cooperative vehicle systems Horizontal Core Elements PG 7 Testing and Compliance Horizontal PG 8 Operation and Evaluation 9
Issues mapped to German project groups PG 0 Project Management PG1 System Architecture PG 1 System Architecture Still work in progress PG 6 Privacy and IT Security Several feedback loops with most PGs PG2 ICS (Central Station) PG 2 ICS PG 3 Interlinking ICS PG 4 IRS PG 7 Test and Compliance PG 5 IVS Legacy systems & interfaces in general Requirements that are partially not yet defined PG 8 Operation and Evaluation PG3 Network of Central Stations Legacy systems & interfaces in individual states Federal structure and overlapping competences PG4 IRS (Roadside Unit) Different interfaces to IVS and ICS, no independent specification Requirements that are partially not yet defined PG8 Operation and Evaluation Create detailed operational manuals, set up change management What to evaluate and how? 10
General Implementation Issues PG 0 Project Management PG4 / PG5 common interface PG 1 System Architecture Standards freeze at certain point in time PG 6 Privacy and IT Security Common release management PG6.1 Security PG 2 ICS PG 3 Interlinking ICS PG 4 IRS PG 7 Test and Compliance PG 5 IVS Find a suitable PKI solution WG5 Common solution for different stakeholders PG 8 Operation and Evaluation PG6.2 Privacy Various issues: data ownership, data usage, user consent WG4 Different approaches: top-down framework vs. bottom-up recommendations PG7 Testing & Compliance Depending on various PGs and overall system design Requirements and test cases have to be developed for each level Exchange of specifications to create common requirements Cooperative task for industry and road authorities 11
Lessons learned SELECTION OF LESSONS LEARNED Legacy systems have to be taken into account Interoperability of new equipment cannot be taken for granted Conformance testing and interoperability testing are important Standards alone do not guarantee interoperability Stakeholders can benefit from common interfaces (Coordinated) profiling and standardization is required Coordination between stakeholders requires extra effort Cooperation across jurisdictions poses new challenges C-ITS is a truly cooperative task WHAT IS NEEDED FOR C-ITS TO BECOME A SUCCESS STORY? Information exchange and knowledge transfer Joint European deployment strategy (Profiled) standards 12
Thank you for your kind attention Suggestions orquestions? www.c-its-corridor.de Bild: Hessen Mobil Road and Traffic Management