1. Legal issues addressed in the EU funded AdaptIVe project
Andreas Knapp
Daimler AG, Germany
AVS 2015
Ann Arbor, USA
21 July 2015

2. Agenda Project facts Motivation Challenges, objectives, and concept
// July 21, 2015
AVS 2015, Ann Arbor

3. Facts
Duration: 42 months (January 2014 – June 2017) Budget: EUR 25 Million European Commission: EUR 14,3 Million Coordinator: Aria Etemad, Volkswagen Group Research 8 Countries: France, Germany, Greece, Italy, Spain, Sweden, The Netherlands, United Kingdom
// July 21, 2015
AVS 2015, Ann Arbor

4. 29 partners Almost all major OEMs Also OEMs from the US
// July 21, 2015
AVS 2015, Ann Arbor

5. The integrated project AdaptIVe
Integrated project: Provides framework for research on automated driving.
Work is done in what we call “subprojects”. 6 of them
3 working on functions
3 working on general topics
// July 21, 2015
AVS 2015, Ann Arbor

6. Agenda Project facts Motivation Challenges, objectives, and concept
Lets talk about the motivation and the benefits
// July 21, 2015
AVS 2015, Ann Arbor

7. Potentials for automated driving
Drivers are supported in demanding or repetitive tasks. Travel comfort increases.
Vehicles dynamically adapt the level of automation according to the current situation.
Vehicles react more effectively to external threats.
Vehicles are resilient to different types of system and human failure.
Don’t go into details, We like to talk about potentials
About a better world
and the benefits of automated driving
// July 21, 2015
AVS 2015, Ann Arbor

8. Motivation for automated driving functions
Reduction of fuel consumption & CO2 emission
Optimization of traffic flow
Zero emission
Support unconfident drivers Enhance mobility for elderly people
Demographic change
Potential for more driver support by avoiding human driving errors
Vision zero
And on a larger scale on the benefits for
environment and the society
// July 21, 2015
AVS 2015, Ann Arbor

9. Demonstrators
Of course AdaptIVe will provide several demonstrators to showcase possibilities of automated driving:
There are 3 projects that showcase functionality.
Focus is on close distance at low speeds,
city driving and
highway.
All of these projects have research questions and challenges of their own.
Actuators, key fob, ultrasonic and radar sensors,  cameras, on-spot mapping
Actuators for vehicle control, laser scanner and radar sensors, cameras
Actuators, ECUs, on-board sensors, radar, map-based electronic horizon, V2X
// July 21, 2015
AVS 2015, Ann Arbor

10. Challenges and project objectives
Widespread application of automated driving to improve
traffic safety, efficiency and comfort
Strategies for human-vehicle integration
New evaluation methods, impact assessment
Legal issues,
terminology
And then there are other more general topics that will also be addressed
Legal issues
Human vehicle interaction
Evaluation of the demonstrator functions (talk given in the afternoon)
So lets talk about legal issues today
// July 21, 2015
AVS 2015, Ann Arbor

11. Legal issues - Response 4
Called Response – series of European projects
At that time focused on ADAS, now higher automation
So I said that we like to talk about potentials and benefits, but what about difficulties currently opposing the market introduction / research questions
Current legislation does not allow automated driving.
But what are the hurdles?
And the risks? And with risks I do not mean technically now, but for the OEMs?
Legal issues - Response 4
// July 21, 2015
AVS 2015, Ann Arbor

12. Levels of driving automation
LKA
ACC
Parking
Assistance
Traffic Jam
Chauffeur
Garage Pilot
Assisted
High auto-mation
Partial auto-
mation
Condi-
tional auto-mation
level 1
level 4
level 2
level 3 No
auto-
level 0
Full
level 5
Driver in the loop
No significant change with respect to existing driver assistance systems
Driver out of the loop
Not in accordance with regulatory law (Vienna Convention of 1968, national road law)
Shared responsibility for control between driver and system
 need for action
You all know the SAE J3016 automation levels. And we have adopted them for the project.
One of the obvious differences from ADAS to higher levels of automation is that the driver is giving up control or is sharing control with the vehicle.
Focus for work is on level 3 and 4
Source: SAE document J3016, “Taxonomy and Definitions for Terms Related to On-Road Automated Motor Vehicles”, issued , see also
// July 21, 2015
AVS 2015, Ann Arbor

13. Challenges Discuss need for action from an industry perspective
Pave road to market introduction of automated vehicles
Current legal situation does not allow automated vehicles on public roads.
Assess law and identify
needed adaption
National laws can be different with respect to automated driving
Analyze main markets - project partners will contribute for their countries
When can a vehicle be considered safe?
Interpretation of existing law. Liability risks?
Some of the key challenges to be discussed in the project
Note: For series introduction, not developing and testing
2 Restrictions: Cannot do all, cannot propose precise changes
Contribute the needs for action
// July 21, 2015
AVS 2015, Ann Arbor

14. System classification: Group categories of automated driving functions
Research tasks
System classification: Group categories of automated driving functions
Legal difficulties for market introduction of automated driving functions:
What are the new risks for the manufacturer from product liability
Usage and protection of data collected by automated driving functions
Protection against corruption and fraud of vehicle data and V2X data
Problem is to big to be solved in general
Group into bins (or equivalence classes): 2 benefits
Can have a more abstract look
Can be extended to future functionnality
Liability
Data privacy and
data security issues
EU project is ideal
// July 21, 2015
AVS 2015, Ann Arbor

15. System classification
Systematic derivation of relevant system parameters for:
Vehicle
Driver
Environment
Available to public as Deliverable 2.1
on the AdaptIVe website.
Classification tree
Condensed into 10 determining parameters
Can be used
Legal
Functional safety
// July 21, 2015
AVS 2015, Ann Arbor

16. Scenarios
Representative scenarios for assessment on a case by case basis, needed e.g. for product liability. Based on system classification.
Examples showing:
Different levels of automation
Situations that can be handled by the system. And others not
Use of information (on / off board) and allow me just some statements for this situation to show the complexity:
There are at least 4 stakeholders in that situation:
The driver/owner
The content provider (data).
The infrastructure operator (link)
And the manufacturer
Can you imagine what that means in terms of data privacy, security and liability?
// July 21, 2015
AVS 2015, Ann Arbor

17. AdaptIVe Workshop on Legal Aspects
September 17th, 2015
Paris, France
Hosted at the French Car Manufacturers Assocciation (Comité des Constructeurs Français d’Automobile)
Discuss legal topics with external stakeholders and expert public
Promote activities of AdaptIVe
Get insight in current activities, approaches and status of other projects and working groups
Registration is open and agenda online at
For me it is difficult to present legal work, as it is almost exclusively paperwork.
Those further interested in the topic: Invite to workshop
// July 21, 2015
AVS 2015, Ann Arbor

18. Andreas Knapp Daimler AG +49 7031 4389 862 andreas.knapp@daimler.com
Thanks

19. Response 4 partners
// July 21, 2015
AVS 2015, Ann Arbor