Transcription

1 operative ITS oordination ployment upport This project has received funding from the European Union s Horizon 2020 research and innovation programme under Grant Agreement No

2 Panel Session C-ITS Deployment - Strategic Issues Moderator Onno Tool [RWS] Panellists Suzanne Hoadley[Polis] Paul Spaanderman[PaulsConsultancy] Tuesday, 9:30-10:30 2

3 Strategic Issues CODECS at a glance CODECS specific focus on: City perspective on C-ITS Hybrid Communication Use Cases framework 3

4 CODECS at a Glance Title: operative ITS ployment oordination upport Acronym: CODECS Number: Call: H2020-MG-2014_SingleStageB Topic: MG-7.2b-2014 Towards seamless mobility addressing fragmentation in ITS deployment in Europe Type: Coordination & Support Action Duration: 1 May April 2018 (36 month) 4

5 CODECS at a Glance Cooperative Intelligent Transport Systems and Services (C-ITS) are mature to enter the European and international market European Automotive Industry and Road Authorities are preparing initial C-ITS deployment as off 2019 Day One implementation provides information and warning services which support foresighted driving, with noticeable effects on traffic safety, efficiency and travel comfort Market acceptance requires coherent end-user experiences, interoperability and a concerted roll-out of systems and services across borders and brands CODECS aims on giving guidance to a concerted C-ITS roll-out across Europe in later innovation phases which might require related research, testing and standardisation 5

6 Objectives Sustaining C-ITS deployment in Europe by Coordinating initial deployment activities Aligning deployment road maps Giving strategy coordination support Raising awareness for the idea of cooperative road traffic Building up and maintaining stakeholder network For information sharing, knowledge transfer, exchange of experiences For consolidating implementation approaches, functional preferences and strategy requirements By organising workshops, webinars, stakeholder meetings, conferences, personnel consultation 6

7 Objectives Serving as nodal point for consolidating stakeholder requirements Horizontal level: aligning functional approaches and open strategy issues between initial deployment initiatives and stakeholders Vertical level: calling attention to consolidated stakeholder views and preferences in discussion of high-level decision makers Supporting The Amsterdam Group The C-ITS Deployment Platform of the European Commission Standards Setting Organisations Other key deployment players in coming to a concerted C-ITS deployment approach. 7

8 Key Activities Coordination of Initial Deployment Road Mapping for C-ITS Deployment Strategy Coordination Support 8

9 Measures & Practices 9

10 Impact Key interposed variable: interoperability of systems and services 10

11 Impact CODECS Stimulates interoperability by Proposals for functional specifications Standards profile for V2I/I2V applications Paves the way for consolidated C-ITS roll-out with Blueprint for deployment Aligned functions road map Recommendations for strategic decision making 11

12 Partners 12

13 Contact To join the CODECS network, contact us! ITS mobility GmbH (Coordinator) Hermann-Blenk-Straße Braunschweig Germany Dr. Karl-Oskar Proskawetz This project has received funding from the European Union s Horizon 2020 research and innovation programme under Grant Agreement No

14 The city perspective on C-ITS Suzanne Hoadley, Polis

15 Urban transport challenges and policies 15

16 ICT/ITS an enabling technology Traffic/network management Traffic light control Public transport priority Real-time information Information services Multimodal info Demand management (enforcement) Payment systems, fleet management & other areas 16

17 Municipal infrastructure spending April to April 2018 CODECS - TRA

18 Determining the C-ITS value proposition Many technologies and tools widely used in cities today What additional value can C-ITS bring over existing systems? Claimed potential benefits include improved flow, safety, emissions etc BUT not much is yet proven at large scale Before implementing a city will need to know: Who receives benefit (e.g. all vehicles, buses only, specific vehicles, cyclists only) How widespread benefit is (e.g. single junction vs city-wide) How benefit is valued (e.g. money, time saved, accident reduction, or just political) 18

19 City views of C-ITS Will C-ITS do the job better than another (cheaper) technology/ measure? Is it sufficiently tested to be safe and to achieve the desired outcomes? How much will it cost to install, operate and maintain? how can C-ITS build on existing investments, ie, how can it integrate with legacy systems? is it future-proofed against obsolescence Is it available and meets the specifications? Isn t C-ITS just for cars and motorways? 19

20 City requirements for C-ITS Start from the problem rather than the technology Understand the benefits/business case Facilitate procurement (procurement guidance, market readiness, future-proofed investment) Enable integration (interfaces, regional UTC standards) Address organisational issues (resources, skills, procedures, role & responsibility) User response (will customers use it?) 20

21 Interesting urban C-ITS use cases Source: 21

22 City outreach and engagement City Pool Scope Promote discussion & awareness raising on city-specific issues Gather input for CIMEC and CODECS activities (requirements, use cases, deployment challenges/enablers) City Pool workshops 3/3/16 London (CIMEC-CODECS) 6/6/16 Glasgow (CODECS) 14/11/16 Barcelona (CIMEC-CODECS) 18/5/17 Brussels (CIMEC) 22/3/18 Dublin (CODECS) 40 local authorities from 15 countries 22

23 Conclusions and recommendations Awareness among cities is growing needs to be sustained through European and especially national programmes Knowledge building and discussion required in relation to: Value proposition of C-ITS for cities Business model (direct or third party approach) Technical approach (merits/constraints of direct and cellular comms) Changing role of traffic manager in view of technology evolution (connectivity and automation) and growing role of private sector Dedicated urban C-ITS support activity is needed (development of use cases and profiles, migration approaches, deployment issues, sharing results of pilots, etc) April to April 2018 CODECS - TRA

24 24

25 25

26 Hybrid Communication Paul Spaanderman

27 Hybrid Communication In General Complementarity, Interoperable and able to Coexist! The Term is used randomly in horizontal and vertical system definitions. No definition for ITS can be found. HC in ITS and Automation (CCAM) European wide the term was introduced in the C-ITS deployment platform phase 1 report (2016).

28 HC Objective Is intended to Improve traffic safety and support traffic Automation (CCAM) Maximize the awareness about the environment we are in. With the intension to maximize the travel safety, efficiency and improve the comfort. Cooperative-ITS contributes to this By sharing relevant information in a time relevant manor!

29 Hybrid Communication C-ITS platform phase 1 report does not provide a clear definition. Complementing communications with initial deployment based on concurrent operation of at least regular cellular and IEEE802.11p/ITS-G5 communication technologies. Based on the limited clarification stakeholders developed their own benefits not necessarily being Interoperable, Backward compatible.

30 HC Workshops EATA To establish a common view The CODECS & EU Commission Initiative CODECS Workshop: sharing the views May 19 th C-ITS Platform meeting: Alignment of the results July 10 th 2017 Publication of the agreements and recommendations: CODECS Workshop ITS Hybrid Communication report T4.2.1* and report D4.5 *)

31 HC = sum requirements for the beyond Day-1 services 3-4G+ ITS-G5 + 5G Key elements: Follow the EU Commission complementing multi-communications approach: Bases 3-4G + ITS-G5 technologies Added new technologies providing Higher Quality of Service (QoS). Introductions of communication dynamic capabilities at the Facilities and application level Introduction of new 5 th generation communications Ensuring Clarity about the quality of the information provided End2End interoperability and backward compatibility at functional and technology layers for an agreed set of European services Higher Geolocation accuracy to support VRU and other services Extended privacy solutions for data aggregation beyond short-range (GDPR) Realize Functional Safety requirements (ISO/TS 26262)

32 Roads Works Warning Extending the Day-1 services (example) DAY-1: Static RWW, Local safety CAMs to traffic centre, DENM RWW warnings via Short-Range communication. Centrally managed or decentralized managed Traffic centers

33 Roads Works Warning Extending the Day-1 services (example) DAY-1: Static RWW, Local safety and preventive routing via Service providers: Static RWW warning DENMs provided via Data warehouse Extended Vehicle model Exchange Node (NordigWay) OEM Provider Service Provider Authority Provider Country Data Warehouse Network Operator Cloud services. e.g. MEC, IoT Traffic centers

34 Roads Works Warning Extending the Day-1 services (example) DAY-1: Dynamic Local RWW, Local safety and maximizing road throughput local speed and lane optimisation via local CAM analyses + IVI messaging. Exchange Node (NordigWay) Extended Vehicle model OEM Provider Service Provider Authority Provider Country Data Warehouse Network Operator Cloud services. e.g. MEC, IoT Traffic centers RSU

35 ITS Services Road Works Warning Service Use Cases: Static Short-Range Safety Routing Assist Dynamic Short-Range Safety and Flow optimisation. Extended services going into: Extended Safety, Integral Safety, Automation, C-ACC, Platooning and VRU

36 The Hybrid ITS stations To ensure QoS requirements Multi-Channel operation Functional Safety ITS Layers Extensions Especially Facility Security Management layers Infotainment, Multi-model Traveling and system maintenance applications and services Geolocation Referencing High Geolocation Accuracy Extended Security and Privacy ITS Security Automation and Safety QoS applications and services Nav-MAP HD-MAP Local-MAP QoS + MCO Management MAC /PFY Spectrum Satelite 17, ,5-51,4 GHz IP ECO DAP+ FM IP ECO FM FM TMC ECO 3G/4G/ 5G Licenced (several) IP ECO Un-Licenced (WiFi) IP ECO 11p/ITS-G5 11px/ITS-G5 Un-Licenced (5.9 GHz) ITS-G5 B-QOS ECO LTE-V2x Un-Licenced (?/5.9 GHz) ITS-G5/LTE ECO G5 Licenced (? GHz 700 MHz) IP H-QoS ECO G5 Un-Licenced (63 GHz) IP B-QoS ECO

37 Hybrid in the Cloud Increase functionality of DATEX II Agree Uniform use VRU and accident management

38 Hybrid Communication + 3-4G+ ITS-G5 5G Hybrid Communication is not a specific architecture nor a system but it s the recognized identifier representing the collection of functional and technical improvements to realize to satisfy the main objective of beyond Day-1 Traffic Safety and CCAM related data exchange. It became a common recognized term and now an European objective.

39 Use Cases Onno Tool

40 Several EU initiatives C-Roads C-The Difference C-Mobile CIMEC TIMON MAVEN More EU projects And many more national initiatives Growing landscape of C-ITS implementation 40

41 Interoperability END Use-Cases Applications Facility Services Prioritization Networking Access sharing Channels Air Fairness Area Covered Spectrum Security at all layers END 41

42 Use Cases Interoperability? Common understanding and language necessary? What is a use case? Scenario, application, scenes, service, functionalities several terms are used 42

43 Use Cases So what is a use case? The term Use Case was introduced as a methodology to support system analysis, with the purpose to identify, clarify and organise system requirements such that systems engineering can realise systems based on System Modeling 43

44 Use Cases Within Intelligent Transportation Systems the term Use Case has a wider value. It is not specifically used for system engineering. It is used by all stakeholder groups for internal alignment between these stakeholders. Alignment focussing on the functional needs to support general social and market business objectives and not just for system engineering. 44

45 Use Cases An ITS Use Case identifies a functional objective (goal) to reach. It clarifies the original situation, the objectives to achieve and the end situation and it recognises the general context in which this objective needs to be realised. 45

46 Cases An ITS Use Case includes a high-level system environment description including high-level functions, their interactions and conditions to realize the use case. No implementation but only high-level functional requirements maybe specified which might include high-level behavioural, conditional and/or situational aspects such that the description is implementation agnostic. For implementation, a single Use Case may be supported by many different scenarios (such as Business, Legal, Privacy, Implementation, Testing/Validation, Environmental, Operational and Life Cycle Scenarios) 46

47 Generic and specific requirements Use case Functiona l R a ng e D e sire d B e ha viour Functiona l Syst e m B ounda rie s S itu atio n D yna m ic E le m e nt s Sc e ne r y Se lf- R e pre - se nta t ion S cen ario A c t ions & E ve nt s G oa ls & Va lue s L e g a l P ro file B u sin e ss P ro file Te le - c om m u nic a t ion P ro file P riva c y & Se c urit y P rofile s P ro files H um a n B e h a viou r P rofile O pe ra t iona l & L if e Cyc le P rofile s E vironm e nta l P rofile Q ua lific a t ion P rofile CODECS developed template for the use cases, used for discussion in other projects and C-Roads Reference: Defining and Substantiating the Terms Scene, Situation, and Scenario for Automated Driving by: Simon Ulbrich, Till Menzel, Andreas Reschka, Fabian Schuldt, and Markus Maurer. ISO/DTR ( ), ETSI TR , CODECS

48 Hierarchy Traffic Functional Scene? Traffic Services Traffic Use Cases Traffic Scenario s Traffic Scenes? Scenario V=10/h 1 10m V=10/h 1 10m Interaction Scene 1 J Scene 1 Scene 48

49 ? V=10km/h 1 10m? V=10km/h 1 V=15km/h 1 49

50 Use Cases Developed template for systematic approach Strong link with C-Roads, applying this framework approach in harmonising functional descriptions, is applied in InterCor as well. Dissemination via workshops and webinars Experience: substantial effort to come to common language and harmonised descriptions 50

51 Recommendations Aligning Use Cases on a EU level is necessary Keep the end users in mind because will in the end determine the value of the use cases by adopting them Develop Use Cases with multiple stakeholders on EU level 51