Federal Highway Administration National Dialogue on Highway Automation: August 1-2, 2018 Digital Infrastructure and Data Workshop Summary

Collaboration Corner

Format

The Collaboration Corner consisted of a career-fair-style setup with seven stations for collecting different types of information from stakeholders. This setup encouraged a highly interactive session, with participants on their feet and moving from station to station. USDOT staff members were located at each station to encourage participation, clarify the exercise, engage in discussion, and ask follow-up questions. Participants were allowed to move at their own pace but were provided with informal prompts to move to a new station every 15 minutes. Information was collected at each station through two methods:

• Post-it exercise—Attendees used post-it notes to respond to a specific prompt, which was presented on posters at each station. This was a public form of communication that allowed attendees to view and engage with their colleagues' suggestions.
• Suggestion box—Participants wrote their questions, suggestions, or other input on an index card and placed it into a suggestion box. This was a more private form of communication that allowed attendees to provide information that they may not have been comfortable sharing in a public forum.

Stakeholders provided input on the following topics:

• Identifying Data Needs: Data for collecting, sharing, and standardizing
• Digital Infrastructure and Connectivity: Needs and challenges
• Preparing for an Automated Future: Focus areas and use cases
• State and Local Issues: Building capacity and providing guidance
• Research Needs: Collecting research needs statements
• Terminology: Developing a lexicon around highway automation
• Parking Lot: Gathering important questions and comments that didn't fit cleanly in any of the other categories

This section summarizes key themes and takeaways for each topic.

Identifying Data Needs

This topic focused on identifying which data are necessary for enabling safe and efficient AV operations and which entities should be involved. Input was solicited in three categories, each of which was represented on a separate flip chart at the station: (1) data to collect, (2) data to share, and (3) data to standardize. Participant inputs are summarized below.

Table 1 Participant Inputs: Data Needs

Data to Collect
Public Sector	Road conditions and potential hazards Work zone information Location and path of emergency vehicles Operating conditions that an AV experiences
Private Sector	Infrastructure status and quality Information regarding near-misses and crashes with and without injuries Pedestrian and bicyclist information
Data to Share
Public Sector	SPaT data Road conditions and potential hazards Location and path of emergency vehicles Work zone information Event, incident, and road closure information
Private Sector	Non-sensitive data that would not raise anti-trust or anti-business concerns Cyber threats and vulnerabilities Collision and near-miss data Consumer adoption metrics Business models Routing information
Data to Standardize
Public Sector	Vehicle-to-vehicle and vehicle-to-infrastructure communications message sets Geo-mapping information Work zone location and timing Traveler information Information collected by electronic data recorders in vehicles
Private Sector	Probe vehicle data Connected vehicle datasets and applications Linear referencing

Digital Infrastructure and Connectivity

This topic focused on different aspects of digital infrastructure considered to be most critical to enabling automation, such as specific elements that support vehicle interoperability and automated vehicles operating in a mixed-fleet environment. Input was solicited in three categories: (1) needs, (2) challenges, and (3) roles.

Table 2 Participant Inputs: Digital Infrastructure and Connectivity

Needs
Education for drivers, consumers, and road users Dedicated spectrum for connected vehicle communications Incremental deployment that supports both current and future vehicles and leverages existing infrastructure without being locked into one technology Unambiguous standards for data transmission, connectivity, and interoperability Connectivity along major travel routes (e.g., fiber-optic cable) Proofs-of-concept and demonstrations
Challenges
Developing consensus standards for connected vehicles Obsolescence of infrastructure and technology Data privacy and security Funding and maintenance of digital infrastructure assets Consistency of road signs and marking Data storage and transmission efficiency
Roles
Federal: Regulating aspects of AVs critical to safety of the transportation system. State: Permitting of right-of-way for digital infrastructure field deployments Original equipment manufacturers (OEMs), start-ups, etc.: information technology solutions Public-private partnerships: No role identified

Preparing for an Automated Future

This topic focused on opportunities in data and digital infrastructure to support an automated future. Input was solicited in five categories: (1) policy and planning; (2) operations; (3) freight; (4) infrastructure design; and (5) safety.

Table 3 Participant Input: Preparing for an Automated Future

Policy and Planning
Data	Jurisdiction-specific regulatory information needs to be consistent and exchanged (e.g., traffic and privacy regulations). A value proposition is needed for collecting, sharing, and validating information. Data on vehicle operations can inform safety and long-range planning.
Digital Infrastructure	Need to recognize potential impacts on the electric grid.
Operations
Data	SPaT information could potentially support transportation system efficiency. Public agencies would like data to assist with asset management and integrated corridor management.
Digital Infrastructure	Shared weather and hazard information could be useful.
Freight
Data	Freight operations would benefit from data to support real-time weight assessments and dynamic hazardous materials information.
Digital Infrastructure	Updated rest area information could be useful.
Infrastructure Design
Data	Data can help prioritize infrastructure investments. Important to determine minimum data elements and standards for infrastructure design. Need to develop processes for data aggregation and transmission to IOOs. Need to update intersection and railroad crossing information.
Digital Infrastructure	Secure collection and storage architecture are important issues. Real-time reporting of work zone information is needed.
Safety
Data	Data can inform system security, performance requirements, and modeling of safety-related factors. Sharing of collision and near-miss information is needed.
Digital Infrastructure	Need to develop standards for connected vehicles and infrastructure. There should be different policies for companies at different levels of maturity (e.g., experienced OEMs vs. start-ups).

State and Local Issues

This topic focused on what State and local organization need to do to prepare for an automated future. Input was solicited in five categories: (1) information and tools, (2) technical assistance, (3) guidance, (4) workforce training and skills, and (5) other.

Table 4 Participant Input: State and Local Issues

Information and Tools
Near-Term	Information exchange from pilots to avoid duplication of efforts Understanding of who needs what data for which purposes Tools for automatic digital mapping
Long-Term	Understanding the availability and types of AV data Real-time work zone reporting Traveler information reporting standards
Technical Assistance
Near-Term	Communications technology investment decisions Network capacity and availability Model data sharing agreements
Long-Term	Digital mapping
Guidance
Near-Term	Infrastructure investments needed to accommodate AVs Federal and State leadership and consistency Data validation policies Availability and protection of 5.9-GHz spectrum Clarification of the State regulatory role
Long-Term	Data governance Inclusion of AV components in Federal grant criteria Best practices for data exchange
Workforce Training and Skills
Near-Term	Professional capacity-building and training Agile and open-source development Funding for workforce development Updated job descriptions and classifications to include technology skills
Long-Term	Data scientists and other new skill sets
Other
Near-Term	Standards development and adoption Clarification on whether connectivity will be required Consideration of bicyclist/pedestrian needs
Long-Term	Rural considerations Elimination/reduction of barriers to entry Impacts on "car culture"

Research Needs

This topic focused on identifying research that needs to be conducted and suggested responsible sectors and timeframes. Research needs were solicited in three categories: (1) urgent (by 2020), (2) medium-term (by 2025), and (3) long-term (by 2030 or later).

Table 5 Participant Input: Research Needs

Urgent (by 2020)
Public Sector	Collision and near-miss data related to pedestrians Low-risk pilot studies Impact on travel demand and patterns Consumer education
Industry	Electric grid impacts Security risks Sensor technology Dynamic emission control Collision prevention
Medium-Term (by 2025)
Public Sector	Infrastructure investments needed to accommodate AVs Cross-sector/jurisdiction collaboration Rural impacts Mixed-fleet considerations Changing role of traffic management centers Traffic and curb use implications
Industry	Conformance testing Consumer adoption
Long-Term (by 2030 or later)
Public Sector	Interactions between AVs and all road users Human-factors-style testing for automated systems Modifications to the traffic control system
Industry	Impacts on urban planning

Terminology

Participants shared the most common terminology that they hear when discussing AVs and indicated which terms are helpful and which are confusing. They placed these terms along two axes to show how these terms are used. The vertical axis represented the frequency with which these terms are used, and the horizontal axis represented the level of confusion surrounding the use of these terms. Table 6 illustrates the terms placed into each quadrant.

Some of the most confusing and frequently encountered terms include the various descriptions of connected and/or automated vehicles, as well as the specific meanings of broadly defined words such as data, digital infrastructure, and standards.

Table 6 Participant Input: Terminology

	Confusing	Clear
Frequency	Data: What data? Why is it needed? Who will use it? How will it be protected? Standards: We talk about them, but what are they? Enabling legislation AV vs. connected vehicle (CV) Road weather and real-time update Data governance Open data Digital infrastructure Connected vehicle Automated driving system vs. AV vs. highly automated vehicle vs. connected and automated vehicle SAE levels and full automation timeframes Autonomous Dedicated short-range communications Uniformity Cybersecurity and data privacy	OEM Anonymous vehicle sensor information needed Probe data Automated/Self-driving SAE J3016 (taxonomy and definitions, internationally adopted)
	Digital infrastructure Data Blockchain Equity (automation helps access e.g., disabled, aging)	Drive-by-wire Subrogation

Parking Lot

Any remaining questions and comments that did not cleanly fit into the other topic areas were included in this topic area. Topics included:

• The need for the healthcare community to be involved in discussions regarding data
• Implications of AV use on urban planning
• Ensuring equal access and benefits
• Managing parking and unoccupied AVs
• Policies for children riding in AVs
• Potential impacts of personal aerial vehicles