TRANSPORTATION RESEARCH BOARD
Accelerating Automated Vehicle Acceptance
July 14, 2020
@NASEMTRB #TRBwebinar PDH Certification The Transportation Research Board has met the standards and Information: requirements of the Registered Continuing Education Providers •2.0 Professional Development Program. Credit earned on completion Hours (PDH) – see follow-up of this program will be reported to email for instructions RCEP. A certificate of completion will •You must attend the entire be issued to participants that have registered and attended the entire webinar to be eligible to receive session. As such, it does not include PDH credits content that may be deemed or •Questions? Contact Reggie construed to be an approval or Gillum at [email protected] endorsement by RCEP.
#TRBwebinar Learning Objectives
1.Identify current AV practices
2.Discuss how data, policies, and trust impact the pace of automated system technologies
#TRBwebinar Are We There Yet? Building on TRB Advancing Automated Vehicle Adoption Workshop
Valerie Shuman Principal, SCG, LLC
https://connectedautomateddriving.eu/event/computers-wheels-whos-going-keep-track-driverless-vehicles/ Overview
• Key Questions • Roundtable Insights Are We There Yet?
• What is an AV anyway & who sets that definition? • Who consistently captures & reports this data for this population (the same way that NHTSA does for the driving public as a whole)? • How do they do this?
• Roundtable Question: What AV metrics can we implement within 12 months (or sooner)?
https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812826 Tracking AV Capability/Performance Trends
• What are the key tasks and metrics (top 10? Top 20)? • How do we regularly review these metrics as an industry to ensure we’re trending in the right direction and report progress?
• Roundtable Question: Propose a set of key driving tasks and metrics that we should be monitoring, and a national level solution for monitoring them What Did We Learn?
• What is an AV? • AV is L3 or 4 and above • Initial focus should be metrics for ADAS and HAV systems (L1/L2)
• What types of metrics? • Focus on efficiency, safety, equity metrics • Look at scenario-based data and outcome metrics to understand status of overall fleet • Develop metrics for each mode • Consider regional requirements like different levels of AV functionality (e.g., rural) • Need to look at crashes and near misses; collect data on what’s working and what’s failing Specific Metrics (1)
• Performance along a “familiar” route • Route performance and adjustments • Takeover time controls in various road conditions and situations • Interaction with local traffic “culture” – is the AV a good citizen? • Consider overtaking distance (especially for bikes) • Organizational Design Domains (ODDs) • How much driving is done in and outside of the ODD? • At L4, testing on all intended ODDs for a given road must be “green” before can use that road • Moving object detection (including speed at which detection is made) • Develop third party testing standards Specific Metrics (2)
• Signal detection analysis for certain crash types in various scenarios • Functional testing • Secondary crashes • Consider contributing factors/context • Develop a list of factors, design scenarios and test to understand crashes/mile • Environmental data • Takeover requests (planned/unplanned) • Post crash what L1/L2 features were turned on (or not)? • Was the driver aware of the feature? • Biometrics of person in the car. Is the person in a good state and can reengage? • Vehicle kinematics How Do We Implement?
• Partner with insurance industry, OEMs, hospitals and public & private sector tracking • Carefully consider model to encourage private sector sharing – anything too “regulatory” will be a challenge • Develop nationally consistent/standardized metrics to allow data- sharing and confidence • Beware of unintended consequences from metrics (incentivize proper design targets) In Summary
• There is a lot of nuance to consider • Making choices is going to be tough • Trust is less important than trustworthiness https://www.automatedvehiclessymposium.org/register Trusting Increasingly Autonomous Vehicle Technology
John D. Lee University of Wisconsin—Madison [email protected]
Lee, J. D., & See, K. A. (2004). Trust in automation: Designing for appropriate reliance. Human Factors, 46(1), 50–80. Lee, J. D., & Kolodge, K. (2019). Exploring trust in self-driving vehicles with text analysis. Human Factors. doi:10.1177/0018720819872672 Lee, J. D. (2020). Trust in automated, intelligent, and connected vehicles. In D. L. Fisher, W. J. Horrey, J. D. Lee, & M. A. Regan (Eds.), Handbook of Human Factors for Automated, Connected, and Intelligent Vehicles. CRC Press. Chiou, E. K. & Lee, J. D. (in review). Trusting automated agents: Designing for appropriate cooperation. Human Factors.
Policy, Standards, and Societal Infrastructure Transportation as multi-echelon network with many trust relationships Remote Infrastructure and Tra c
Remote operator trust in AV • Driver-Automated vehicle trust Negotiated Road Situations
Pedestrian trust in AV • Person-Policymaker trust Engineers trust in sensors
Driving functions and activities
Driver trust in sensor system
Vehicle Sensors and Controls NTSB Highway Accident Report trim from the car was found entangled within the forward-most area of contact damage on the semitrailer. Figure 6 shows a postcrash photograph of the semitrailer, and figure 7 focuses on the damageNTSB to the semitrailer Finds. Overreliance in Tesla Crash
NTSB Highway Accident Report
Figure 6. Damaged right side of the Utility semitrailer.
Figure 11. Chart showing how much time during the 41-minute crash trip that, while Autopilot was active, the driver had his hands on the steering wheel. Visual and auditory warnings are also Figure 7. Closeup view of impact damage to the right side of the Utility semitrailer. The arrow indicates a segment of frontindicated. windshield (Timing trim from theprovided Tesla entrapped is based in the forwardon vehicle-most area data of and is approximate and relative.) damage. System Performance Data. The vehicle performance data revealed the following: