Task Force on Autonomous Vehicles 2019 Final Report to the Oregon State Legislature
Total Page:16
File Type:pdf, Size:1020Kb
AV Task Force Report Cover.pdf 1 9/6/2019 2:50:35 PM 2019 STATE OF OREGON TASK FORCE ON AUTONOMOUS VEHCILES C M Y CM MY CY CMY K TASK FORCE ON AUTONOMOUS VEHICLES 2019 FINAL REPORT TO THE OREGON STATE LEGISLATURE Sept. 6, 2019 STATE OF OREGON TASK FORCE ON AUTONOMOUS VEHICLES 2019 FINAL REPORT To the Oregon State Legislature House Bill 4063 Task Force Sept. 6, 2019 PAGE i TASK FORCE ON AUTONOMOUS VEHICLES Task Force Membership Chair Lt. Tim Tannenbaum, Sen. Sara Gelser, Sen. Fred Girod, Rep. Lynn Findley, Rep. Susan McLain, Richard Blackwell, Marie Dodds, Steve Entler, Daniel Fernandez, Chris Hagerbaumer, Eric Hesse, Cheryl Hiemstra, Capt. Stephanie Ingraham, Neil Jackson, Jana Jarvis, Mark MacPherson, Evan Manvel, Galen McGill, David McMorries, Robert Nash, Todd Nell, Jeff Owen, Carly Riter, Eliot Rose, Jeremiah Ross, Paul Savas, Becky Steckler, Graham Trainor, Sean Waters, Caleb Weaver Designated Alternates Hanan Alnizami, Mike Bezner, Waylon Buchan, Miriam Chaum, Carlos Contreras, Kristine Cornett, Kate Denison, Jeb Doran, Amanda Howell, Ritchie Huang, Gail Krumenauer, Tom McClellan, Chris Muhs, John Powell, Michael Rose, Jacob Sherman, Aeron Teverbaugh, Young Walgenkim, Caleb Winter, Sara Wright Oregon Department of Transportation Staff Jenna Adams-Kalloch (Emerging Technology Policy Lead), Adam Argo (Principal Planner), Maureen Bock (Chief Innovation Officer), Roberto Coto (Innovative Programs Coordinator), Andrew Dick (Connected, Automated and Electric Vehicle Advisor), Paul Duncan (Policy Advisor), Michelle Godfrey (Education and Outreach Coordinator), Kevin Haas (Traffic Standards Engineer), Amy Joyce (Legislative Liaison), Sarah Kelber (Public Information Representative), Ali Lohman (Automated Vehicle Policy Analyst) Disclaimer This final report is submitted to the Oregon State Legislature as allowed by House Bill 4063 (2018). The contents of this report reflect the view of the Task Force on Autonomous Vehicles, which is solely responsible for the facts and accuracy of the materials presented. House Bill 4063 (2018) The Task Force on Autonomous Vehicles was established by House Bill 4063 in Oregon’s 2018 legislative session. The bill directs the task force to develop recommendations for automated vehicle legislation. In accordance with the bill, the task force submitted a report to the Interim Joint Committee on Transportation on Sept. 11, 2018. The 2018 report included recommendations for legislation to address the following issues: licensing and registration, law enforcement and crash reporting, cybersecurity, and insurance and liability. HB 4063 also allowed the task force to develop a second report due to the Legislature on Sept. 15, 2019, which may address topics including land use, road and infrastructure design, public transit, workforce changes, and state responsibilities relating to cybersecurity and privacy. On Sept. 10, 2018, the task force voted to pursue the second report. This report fulfills those requirements. PAGE ii Structure of Report The report begins with a brief overview of automated vehicle technology and the considerations that prompted the creation of the task force. The next section outlines the task force membership, structure, and process. Then, the report includes materials and recommendations on six topics: 1) vehicle code amendments and public safety; 2) cybersecurity, privacy and data; 3) road and infrastructure design; 4) land use; 5) public transit; and 6) workforce changes. The appendices of the report include the text of HB 4063 (2018), additional comments issued by task force members, and comments from non-members. PAGE iii Abbreviations and Acronyms Definitions ADS Automated driving system Automated driving system (ADS): The hardware and software that are collectively capable of performing AV Automated vehicle the entire driving task on a sustained basis. This term is CAV Connected and automated vehicle used to describe vehicles with SAE automation levels of 3, 4 or 5. (See “Levels of Automation” on page 5.) CV Connected vehicle A vehicle designed to be DSRC Dedicated short range communications ADS-dedicated vehicle: operated exclusively by a level 4 or 5 automated DUII Driving under the influence of intoxicants driving system for all trips within its given operational design domain limitations (if any). (See “Types of EV Electric vehicle Vehicles” on page 6.) FHWA Federal Highway Administration Connected vehicle: A vehicle equipped with FMVSS Federal Motor Vehicle Safety Standards communications technology that allows it to exchange HAV Highly automated vehicle messages with other vehicles, infrastructure, or even cell phones. The messages may convey a vehicle’s HB 4063 House Bill 4063 of 2018 speed and bearing, warning about upcoming ITE Institute of Transportation Engineers construction zones or crashes on the route, weather alerts, or other information critical to safety and system MUTCD Manual on Uniform Traffic Control Devices management. NACTO National Association of City Transportation Conventional vehicle: A vehicle designed to be Officials operated by a conventional driver during part or all NCHRP National Cooperative Highway Research of every trip. A conventional vehicle may be equipped Program with automated features, but requires a conventional driver to operate the vehicle during portions of each NHTSA National Highway Traffic Safety trip. (See “Types of Vehicles” on page 6.) Administration Deployment: The operation of an automated vehicle OBU On-board unit on public roads by members of the public who ODOT Oregon Department of Transportation are not employees, contractors, or designees of a manufacturer or for purposes of sale, lease, providing PKI Public key infrastructure transportation services for a fee, or otherwise making RSU Road-side unit commercially available outside of a testing program. SAE International Society of Automotive Driver assistance technology: A general term for Engineers level 1 and level 2 automation features, which are capable of performing only part of the dynamic driving SCMS Security Credential Management System task and thus require a human driver. Examples of US DOT United States Department of Transportation driver assistance technology include lane keeping assistance, lane centering, and adaptive cruise control. V2I Vehicle-to-infrastructure V2V Vehicle-to-vehicle Dual-mode vehicle: A type of ADS-equipped vehicle designed for both driverless operation and operation V2X Vehicle-to-everything by a conventional driver for complete trips. (See “Types of Vehicles” on page 6.) PAGE iv Fallback-ready user: The user of a vehicle equipped Operational design domain: The environment and with a Level 3 automated driving system who is able to specific conditions for which an automated vehicle is operate the vehicle and is prepared to respond if the engineered and in which it can safely operate. vehicle requests that the user intervene. (See “Levels of Automation” on page 5.) Testing: The operation of an automated vehicle on public roads by employees, contractors, or designees Federal Motor Carrier Safety Regulations: The rules of a manufacturer for the purpose of assessing, and regulations establishing requirements for the safe demonstrating, and validating the autonomous operation of commercial motor vehicles, applicable technology’s capabilities. to all employers, employees, and commercial motor vehicles that transport property or passengers in Vehicle-to-everything communications: Exchange of interstate commerce. Federal Motor Carrier Safety messages between a connected vehicle and any or all Regulations are issued by the Federal Motor Carrier elements of the driving environment, including other Safety Administration. vehicles, roadside infrastructure, or even cellphones. This is sometimes referred to a V2X communication. Federal Motor Vehicle Safety Standards (FMVSS): The standards and regulations establishing the Vehicle-to-infrastructure communications: minimum safety performance requirements to Exchange of messages between a connected which manufacturers of motor vehicles and items of vehicle and connected infrastructure, often through motor vehicle equipment must conform and certify roadside units. This is sometimes referred to as V2I compliance. FMVSS are issued by the National Highway communication. Traffic Safety Administration. Vehicle-to-vehicle communications: Exchange of Highly automated vehicle (HAV): A vehicle equipped messages between two or more connected vehicles, with automated technology capable of performing which is sometimes referred to as V2V communication. the entire driving task, including operating the vehicle and monitoring the driving environment, for at least part of a trip. This term is used to describe vehicles with SAE automation levels of 3, 4 or 5. (See “Levels of Automation” on page 5.) PAGE v TABLE OF CONTENTS Executive Summary ............................................................................................................................................2 Introduction to Automated Vehicles ...........................................................................................................5 Levels of Automation ................................................................................................................................5 Types of Vehicles ........................................................................................................................................6 Federal, State and Local Roles in Regulating Automated Vehicles ........................................7