On December 7th of 2017 the USDOT convened an interesting group of stakeholders to discuss automated vehicle data needs. The goal was simply to better understand what will be needed, so we can all work in that same direction. Attendees included automakers, regulators, local agencies, privacy advocates, data aggregators including Waze and HERE, universities, and industry.
They have published a short document detailing their findings. Download “roundtable-data-automated-vehicle-safety-report” here.
A set of four principles was discussed and supported by the group. Those included
- Promote best practices for data security and privacy.
- Act as a facilitator to promote voluntary data exchanges.
- Start out small to find what works and then build on that.
- Coordinate across modes to save time and money.
Number 2 is perhaps the most problematic. Vehicle and component manufacturers are still playing their cards very close to their vests. They will continue to protect whatever competitive advantage they feel they have. They don’t mind sharing what everyone else is sharing but don’t want to go beyond that point for obvious reasons. So, what will be shared will start with basics such as crash data, AV hours driven, etc. and will grow from there.
The good news, for our purposes here, is the discussion of high priority use cases. #1 on the list is “Monitoring Planned and Unplanned Work Zones”. The data they felt was of the highest value included, “Work zone locations, planned duration of project, updates, planned lane closures, changes in signing, directions, or parking.”
Other encouraging use cases include #2 “Providing Real-Time Road Conditions”. There they discuss the need for data on detours and missing or deficient signs and pavement markings.
Under testing discussions, there was an emphasis on safety-critical scenarios which would have to include work zones. Clearly manufacturers must test not just in ideal conditions, but in all conditions including bad weather, poorly delineated work zones, and in and around major and minor incidents.
They coined the term “Edge Cases” which refer to a “problem or situation that occurs only at the extreme operating parameter.” Certainly, most testing today will continue at or below 35 MPH on a sunny day and under controlled conditions. But once we are all satisfied that AVs can drive safety in ideal conditions, it will be time for the worst-case scenarios. Again, work zones will surely be a part of that.
The last use case of interest was improving roadway inventories. The group felt high-value data for this effort included,””edge-to-edge”, high-definition map elements (e.g., signs and signals, curbs, pavement markings, tolls, express lanes, bridge heights and weight capacities, highway dividers, overpasses, pedestrian areas, bicycle lanes, taxi drop-off zones, (and) quality metrics.”
Under “proposed federal roles” they talk about the USDOT acting as a facilitator of sharing and discussions between the various stakeholders. It’s good to know work zones are now a part of that discussion. Thank you to USDOT for helping make that happen. Our greatest fear just a few short years ago was that the automotive industry would get too far down the road with their development to accommodate special circumstances including work zones, special events and incident response. It’s great to see that won’t be the case.