Oregon Task Force on Autonomous Vehicles Kick-Off Meeting April 18, 2018 4/18/2018 1
Welcome to the Task Force on Autonomous Vehicles 4/18/2018 2
Purpose of the Task Force Framing the Future for Autonomous Vehicles in Oregon • Problem: Oregon law currently assumes a human driver is operating each vehicle on our roadways. The vehicle code doesn’t address a scenario of a partially or completely autonomous vehicle. • First Steps: The Task Force will begin the process of reviewing Oregon’s driver and vehicle laws and proposing any necessary revisions to the Legislature. 4/18/2018 3
House Bill 4063: Why we are here today 4/18/2018 4
Charge from the Legislature Framing the Future for Autonomous Vehicles in Oregon • Develop recommendations on four urgent policy areas relating to automated vehicles • Submit a report, including recommendations for legislation, to the Legislature • Deadline: September 15, 2018 4/18/2018 5
Automated Vehicle Task Force HB 4063 directs the Task Force to address the following issues: Law Enforcement Licensing and and Crash Registration Reporting Cybersecurity Insurance and and Long-Term Liability Policy 4/18/2018 6
Second Report on Long-Term Effects of Automated Vehicles Framing the Future for Autonomous Vehicles in Oregon • Task Force may also develop Road and Land Use Infrastructure recommendations on long-term Design effects Workforce • May submit a second report Public Transit Changes and recommendations to the legislature Cybersecurity and Privacy • Deadline: September 15, 2019 4/18/2018 7
Task Force on Autonomous Vehicles Membership Rep. Susan McLain Daniel Fernández (Jaguar Neil Jackson (OTLA) , Steve Entler (Radio Cab) , Land Rover), Trial lawyers Taxicab industry Rep. Denyc Boles Automotive Industry Graham Trainor (AFL) , Eliot Rose (Metro) , Two Oregon State Senators David McMorries (Office of Workers’ union Metropolitan planning Tom McClellan , the Chief Information Officer), organization Mark MacPherson (Teamsters) , Department of Transportation Cybersecurity industry Transportation union Jebediah Doran (TriMet), Jim Pfarrer, Lt. Timothy Tannenbaum Oregon Transit Association Jared Franz (ATU) , Employment Department (Wash. County Sherriff’s Transportation union Chris Hagerbaumer (Oregon Office) , Cheryl Hiemstra, Environmental Council), Law enforcement Sid Leiken (Lane County) , Department of Justice Nonprofit organization Association of Oregon Counties Jon Isaacs (Uber) , Richard Blackwell, Sean Waters (Daimler) , Transportation network Eric Hesse (City of Portland) , Department of Consumer and Commercial truck manufacturing company League of Oregon Cities Business Services industry Carly Riter (Intel Corp.) , Marie Dodds , Capt. Teresa Bloom, Jeremiah Ross (Ross Law LLC) , AV technology industry American Automobile Oregon State Police Consumer protection advocates Association Robert Nash (State Farm) , Carrie MacLaren, Becky Steckler (University of Automotive insurance industry Jana Jarvis , Department of Land Oregon) , Oregon Trucking Association Conservation and Development Public University 4/18/2018 8
Selection of a Chairperson 4/18/2018 9
Operational Protocol 4/18/2018 10
National Overview: State Automated Vehicle Laws 4/18/2018 11
National Highway Traffic Safety Administration (NHTSA): Federal and State Regulatory Roles for Vehicles Federal State Regulating motor vehicles and motor Regulating human drivers and other vehicle equipment aspects of motor vehicle operation • License drivers • Set Federal Motor Vehicle Safety Standards (FMVSS) for motor • Register motor vehicles vehicles and equipment • Regulate insurance and liability • Enforce compliance with FMVSS • Enact and enforce traffic laws • Manage safety recalls • Conduct safety inspections • Educate public about safety 4/18/2018 12
T e sting De ployme nt 4/18/2018 13
States with Laws or Executive Orders on Autonomous Vehicles 4/18/2018 14
States with AV Task Forces or Work Groups 4/18/2018 15
States That Allow AV Testing and/or Deployment 4/18/2018 16
States Where Testing Has Occurred on Public Roads 4/18/2018 17
California’s Autonomous Vehicle Regulations • Allows testing of AVs with human drivers or remote operators in the vehicle through a permit process. – Manufacturers or testing entities must meet safety, insurance, operator training, and reporting requirements. The manufacturer must also have a plan for law enforcement interaction. • Allows deployment of completely driverless AVs through a permit process. – Manufacturers must certify that AVs meet safety requirements, including the presence of an autonomous technology data recorder and periodic updates to software and mapping information. 4/18/2018 18
Nevada’s Autonomous Vehicle Regulations • Allows testing of AVs on public roads through a self- certification process. – Testing entity must meet insurance, registration, and federal and state safety requirements. • Allows deployment of AVs on public roads through a self-certification process. – Testing entity must meet insurance, registration, and federal safety requirements. • Allows transportation network companies (TNCs) to operate autonomous vehicles through a permit process. – The permit includes requirement for insurance, disclosing fares, reporting crashes, annual reports, and providing service to passengers with disabilities. 4/18/2018 19
Arizona’s Autonomous Vehicle Regulations • Allows testing and operation of AVs with human backup drivers on public roads. • Allows testing and operation of AVs with no backup drivers if tester provides written statement acknowledging that the AV meets basic safety, registration, and licensing requirements. • In the process of establishing mandatory law enforcement interaction plans. 4/18/2018 20
DMV and AAMVA: Automated Vehicles and Considerations for the Vehicle Code Tom McClellan, Oregon Department of Transportation DMV Administrator April 18, 2018 4/18/2018 21
Oregon DMV has identified sections of the vehicle code that may be impacted by automated vehicle deployment • Definitions • Crash Reporting – “Driver” or “Operator” – Process and responsibility for exchanging insurance information and • Driver Licensing alerting DMV – Licensing requirements may depend – How to keep records of incidents and on the capabilities of the automated traffic violations involving highly vehicle automated vehicles • Vehicle Registration • Vehicle Design – Identification of vehicle as an AV – Lack of federal safety standards for automated vehicles • Financial Responsibility – Insurance coverage requirements – What party assumes liability 4/18/2018 22
About AAMVA • Represents Motor Vehicle Administrators of all 69 states, provinces and territories of the United States and Canada • Supports uniformity and reciprocity among jurisdictions • Focuses on safety • Contributed to federal guidance on American Association model state policy for automated of Motor Vehicle vehicles Administrators 4/18/2018 23
AAMVA Guidelines for the Regulation of Highly Automated Vehicles • Provides voluntary recommended guidelines for safe testing and deployment • Complements the federal guidance on model state policy • AAMVA has shared outline and is finalizing the draft • Final version will be published next month, May 2018 4/18/2018 24
AAMVA guidelines will focus on five key areas: 1. Administration 4. Law Enforcement Considerations – Lead agency – Crash reporting – Automated vehicle committee – Distracted driving – Establishing regulatory authority – First responder safety – Law enforcement interaction 2. Vehicle Credentialing Considerations – Adherence to traffic laws – Application for testing permit 5. Topics for Future Versions – Vehicle registration – Insurance – Commercial motor vehicles – Cybersecurity and data privacy 3. Driver Licensing Considerations – Infrastructure – Define driver and passenger roles – Economic considerations – Driver license requirements – Environmental impacts – Driver training requirements – Examiner training requirements 4/18/2018 25
Task Force Member Visioning 4/18/2018 26
4/18/2018 27
Vision for Safety • Safety is a high priority • Testing before deployment • Backup safety drivers • Safety for vulnerable road users • Quantitative goals for safety 4/18/2018 28
Vision for Regulatory Approach • Consistency with federal standards and preemption authority • Unified requirements for interstate commerce • Maintaining local governments’ ability to manage AV use • Clearly defined federal, state, and local roles 4/18/2018 29
Vision for Licensing and Registration • Licensing and registration is a high-priority • Testing phase prior to deployment • Licenses/permits should be revoked if AVs prove unsafe • Special endorsements for vehicles that go in and out of automation • Federal regulation of commercial licensing 4/18/2018 30
Vision for Insurance and Liability • Insurance and liability is a high priority • Clearly assign liability for harms and losses • Establish a chain of accountability • Require adequate insurance coverage • Ensure fair insurance products for Oregonians 4/18/2018 31
Recommend
More recommend
