TRB Workshop on the Future of Road Vehicle Automation

Transcription

1 TRB Workshop on the Future of Road Vehicle Automation Steven E. Shladover University of California PATH Program ITFVHA Meeting, Vienna October 21,

2 Outline TRB background Workshop organization Automation taxonomy Breakout discussions on research needs: Driver-vehicle interaction and human factors Technology needs and constraints Safety and security Public policy Legal liability and risk System architectures Transition and deployment scenarios 2

3 Transportation Research Board (TRB) Operating element within National Research Council, under National Academies of Science and Engineering (private, non profit) Professional society, research coordinator, and public policy advisor 200+ standing committees on all aspects of transportation Organizing conferences, reviewing research papers for publication in TRR Defining research needs statements for use by researchers anywhere Committees on ITS and Vehicle-Highway Automation directly focused in this area 3

4 Workshop Organization Summer meeting organized by ITS and Vehicle- Highway Automation Committees, with cosponsorships by committees on: Vehicle user characteristics (human factors) Managed-use lanes Emerging technology law Major activity center circulation systems (PRT) Emerging and innovative public transport and technologies (other new systems) Planning committee of 36 people July at Beckman Center, U.C. Irvine 125 participants from U.S., Europe and Japan 4

5 Workshop Outline July 24 Pre-workshop on early automation deployment opportunities in managed lane operations July 25 Presentation sessions to explain current international state of the art and knowledge on: Automation taxonomy and benefits (4) Private personal vehicles (~autonomous) (6) Trucks and transit vehicles (~cooperative) (6) Cross-cutting activities (5) July 26 Breakout discussions on 7 cross-cutting topic areas Specifics to follow July 27 Organizers work on synthesizing results 5

6 Definitions (per Oxford English Dictionary) autonomy: 1. (of a state, institution, etc.) the right of self-government, of making its own laws and administering its own affairs 2. (biological) (a) the condition of being controlled only by its own laws, and not subject to any higher one; (b) organic independence 3. a self-governing community. autonomous: 1. of or pertaining to an autonomy 2. possessed of autonomy, self governing, independent 3. (biological) (a) conforming to its own laws only, and not subject to higher ones; (b) independent, i.e., not a mere form or state of some other organism. automate: to apply automation to; to convert to largely automatic operation automation: automatic control of the manufacture of a product through a number of successive stages; the application of automatic control to any branch of industry or science; by extension, the use of electronic or mechanical devices to replace human labour 6

7 Autonomous Unmanned Vehicles Google s Cars Automated Highway Systems (AHS) Commercially Available Automotive Collision Warnings and ACC DOT s Safety Pilot Program 7

8 Additional Classifications based on Divisions of responsibility between driver and the system, building on BASt structure Distributions of functions among the vehicle, other vehicles and infrastructure Driving functions that could potentially be automated Roadway and traffic environments Weather and environmental conditions Special operational challenges 8

9 Breakout Discussion Topic Groups Half-day discussions in groups of people, identifying research needs in: Driver-vehicle interaction and human factors Technology needs and constraints Safety and security Public policy Legal liability and risk System architectures Transition and deployment scenarios 9

10 Driver-Vehicle Interaction and Human Factors - Research Needs Human-centered definitions of levels of automation Definition of hand-off processes between driver and system and how to test them Can disengaged driver be brought back to attention, and how soon? Matching driver mental model to actual system concept of operations What level and kind of driver status display is needed? Is an external display of automated status needed for other drivers? What are long-term unintended consequences of increased reliance on automation? How to reconcile individual driver desire for convenience with societal need for safety? 10

11 Technology Needs and Constraints Research Needs Issues of cost, functionality, reliability Sensors, actuators, controllers, processors, communication, positioning Hardware and software across all categories How to verify performance? What evaluation metrics? User needs and system requirements How to define and test safety? Cyber security Defining operational limits (weather, traffic ) Data to archive for problem diagnosis Platoon protocols 11

12 Safety and Security Research Needs Define resiliency to include safety, reliability and security Address simultaneously or in sequence? Topic areas: Privacy and security requirements compared to current V2V and I2V needs? Data logging requirements Balancing privacy, safety and security Educating users about privacy, safety and convenience trade-offs Public vs. private investments and B/C ratios How to do trusted software updates? Find possible lessons from other industries Estimate likelihood of attack and how to defend Adapt ISO for software and automation 12

13 Public Policy Research Needs Need good data to feed policy discussions (but who owns and controls access to it?) Division of responsibilities among different levels of government (federal, state, local) Risk allocation among public and private sector actors Vehicle industry impacts Fewer vehicles, but more complicated Ownership vs. usage (car sharing) models Early infrastructure planning for long-lead-time investments Environmental trade-off between more, but cleaner, VMT Need for systemwide mobility thinking (analogous to utilities, not separated between vehicle and infrastructure) 13

14 Legal Liability and Risk Research Needs Concerns about meaning of control who was operating, or who was responsible? Especially for platoon leaders Seek analogies from other automated systems (medical, financial, other transport modes) Define roles and responsibilities of public and private sectors Societal acceptance of automated crashes? Political feasibility of limitations on liability? Who owns data, and who has access to it? Vehicle owner? System developer? 14

15 System Architecture Research Needs Basic issues: Role of infrastructure and roadway operator Role of communications (cooperative or autonomous?) All scenarios: Freeway, urban, transit, trucks, parking Topic areas: Business models (premium toll service, truck platoons, automated urban parking ) Standards and tools to facilitate deployment on infrastructure (signage, road markings, SPaT) Logical path to deployment (information clearinghouse, local infrastructure incentives, future proofing vs. rapid changes in technology or public perceptions) 15

16 Transition and Deployment Scenario Research Needs Considered implications of different dimensions of automation concepts: Driver in the loop vs. driver not engaged Operating only in dedicated lanes or in all road environments Urban vs. rural applications Shared vs. owned vehicle operations Occupied vs. unoccupied vehicles Low speed vs. high speed operations These were used to identify deployment challenges and the difficulty of the problems to be solved 16

17 Next steps Summary report on workshop Publication of research needs statements on TRB website Presentations of last summer s highlights in high-profile TRB Annual Meeting sessions, January 14-15, 2013 Formation of Joint Subcommittee on Multimodal Road Vehicle Automation First meeting Thursday, Jan. 17 at end of TRB Annual Meeting, Washington DC Second workshop at Stanford, CA July 16-19,