Technology & Innovation
Topics

Automated Vehicles

Overview

Automated vehicle safety technologies signal the next revolution in roadway safety. We see great potential in these technologies to save lives—more than 30,000 people die on our roads every year and we can tie 94 percent of crashes to human choice—transform personal mobility and open doors to communities that today have limited mobility options.

The DOT Federal Automated Vehicles Policy sets the voluntary framework for the safe and rapid deployment of these advanced technologies.

Press Release

NHTSA Data Shows Traffic Deaths up 7.7 Percent in 2015

Read More
Press Release

U.S. DOT to Host Public Meetings on Safe Operation of Automated Vehicles

Read More
Federal Policy

Overview

Components and Development

Policy Fact Sheet Federal Automated Vehicles Policy Overview PDF, 296.58 KB

The Federal Automated Vehicles Policy sets out a proactive safety approach that will bring lifesaving technologies to the roads safely while providing innovators the space they need to develop new solutions. The Policy is rooted in DOT’s view that automated vehicles hold enormous potential benefits for safety, mobility and sustainability.
The primary focus of the policy is on highly automated vehicles (HAVs), or those in which the vehicle can take full control of the driving task in at least some circumstances. Portions of the policy also apply to lower levels of automation, including some of the driver-assistance systems already being deployed by automakers today.

Components of the Policy

Official Notices
  • Vehicle Performance Guidance for Automated Vehicles: The guidance for manufacturers, developers and other organizations outlines a 15 point “Safety Assessment” for the safe design, development, testing and deployment of automated vehicles.
  • Model State Policy: This section presents a clear distinction between Federal and State responsibilities for regulation of HAVs, and suggests recommended policy areas for states to consider with a goal of generating a consistent national framework for the testing and deployment of highly automated vehicles.
  • Current Regulatory Tools: This discussion outlines DOT’s current regulatory tools that can be used to accelerate the safe development of HAVs, such as interpreting current rules to allow for greater flexibility in design and providing limited exemptions to allow for testing of nontraditional vehicle designs in a more timely fashion.
  • Modern Regulatory Tools: This discussion identifies potential new regulatory tools and statutory authorities that may aid the safe and efficient deployment of new lifesaving technologies.
Federal Policy

Performance

For Manufacturers

Vehicle Performance Vehicle Performance Guidance Fact Sheet PDF, 300.95 KB

The Vehicle Performance Guidance for Automated Vehicles (“Guidance”) outlines best practices for the safe design, development and testing of automated vehicles prior to commercial sale or operation on public roads. The Guidance includes a 15-Point Safety Assessment to set clear expectations for manufacturers developing and deploying automated vehicle technologies. For companies, the Guidance describes internal processes and strategies, organizational awareness, record-keeping, testing and validation, engagement with DOT and NHTSA, and improved transparency to support the safe deployment of HAV technology. The industry’s adoption and use of the Guidance, which DOT and NHTSA will review annually and update as necessary, will build public confidence and maintain the U.S. lead on these emerging automotive safety technologies.

Federal Policy

State Policy

Roles

Model Policy Model State Policy Fact Sheet PDF, 297.65 KB

State governments play an important role in facilitating automated vehicles, ensuring they are safely deployed and promoting their life-saving benefits. The Model State Policy confirms that States retain their traditional responsibilities for vehicle licensing and registration, traffic laws and enforcement, and motor vehicle insurance and liability regimes while outlining the Federal role for automated vehicles. The Model State Policy supports the establishment of a consistent national framework of laws and policy to govern automated vehicles.

State responsibilities:

  • Licensing (human) drivers and registering motor vehicles in their jurisdictions;
  • Enacting and enforcing traffic laws and regulations;
  • Conducting safety inspections, when States choose to do so; and
  • Regulating motor vehicle insurance and liability.the next revolution in roadway safety.
Federal Policy

Regulation

Current tools

Current Regulatory Tools

Learn about existing regulatory tools that NHTSA will use to promote the safe development and deployment of automated vehicles, including interpretations, exemptions, notice-and-comment rulemaking, and defects and enforcement authority. NHTSA has streamlined its review process and is committing to expediting simple automated vehicle-related interpretations and exemption requests.

Modern Tools

Modern Regulatory Tools Modern Regulatory Tools Fact Sheet PDF, 300.82 KB

We’ve identified potential new tools, authorities and resources that could aid the safe deployment of automated technologies by enabling DOT to be more nimble and flexible. Some of the identified tools could be created under current law while others would require Congressional action. Today’s governing statutes and regulations were developed before automated vehicle technologies were even a remote notion. Current authorities and tools alone may be insufficient to ensure the safe introduction and full safety promise of new technologies. This challenge requires DOT and NHTSA to examine whether the ways in which the Agency has addressed safety for the last several decades should be expanded to realize the safety potential of automated vehicles over the decades to come.

Frequently Asked Questions

FAQ: Federal Automated Vehicles Policy

This Addendum provides responses to frequently asked questions from stakeholders following the release of the Federal Automated Vehicles Policy (the Policy) on September 20, 2016. No changes in the Policy are presented; rather this Addendum provides only clarifying information. Some comments submitted to the Agency referenced “clarification” for particular points within the Policy but were effectively requesting changes to the Policy and therefore were not included in this Addendum.  If necessary, NHTSA may issue additional FAQs in response to feedback and to support implementation of the Policy.   

Codification of Policy Components

Page 11, Section I: Vehicle Performance Guidance for Automated Vehicles section explicitly states, “This guidance is not intended for States to codify as legal requirements for the development, design, manufacture, testing, and operation of automated vehicles.”  Thus, the Policy is clear that States should not codify (i.e., incorporate into State statutes) the Vehicle Performance Guidance or any of the specific elements of the Safety Assessment Letter. However, as part of State oversight of HAV deployment and testing within that State, it may wish to request a copy of any Safety Assessment Letter an entity has submitted to NHTSA. It should be noted that NHTSA is taking steps to make publicly available the safety assessment letters received by the Agency, which would obviate the need for a State to request an additional copy.

The Model State Policy (Section II of the FAVP) is designed to accomplish two aims: first, to clarify and delineate the Federal and State roles for the regulation of highly automated vehicles; and second, to lay out a framework that the States may use as they write their laws and regulations so that we build a consistent, national framework for the testing and operation of highly automated vehicles.

As stated in the Model State Policy, NHTSA strongly encourages States to allow NHTSA alone to regulate the safety and performance aspects of HAV technology and vehicles. NHTSA encourages those States that wish to regulate HAV testing to incorporate relevant components of the Model State Policy into their regulations, in order to promote a more cohesive body of authorities and avoid a patchwork of inconsistent State laws and regulations. During the development and after the subsequent release of the Model State Policy, many State government officials expressed their views that while they were generally comfortable with the Federal Government having the responsibility for the regulation of vehicle and equipment safety, they would need confidence that vehicle manufacturers, testers and other entities were conforming to the safety approach envisioned in the Federal Automated Vehicles Policy. Therefore the Model State Policy suggests to States that they may request submission of confirmation that an automaker, tester or other entity has followed the principles set forth in the Vehicle Performance Guidance. The Model State Policy recommends that a copy of the Safety Assessment Letter could serve that purpose, but as the letter is presently voluntary, a State could request alternative documentation in the event an entity does not submit a Safety Assessment Letter.

Absent this assurance, and absent the implementation of a new Federal Motor Vehicle Safety Standard that would preempt State action, States have the legal right and power to develop their own vehicle safety and performance criteria. Such actions would create the undesired patchwork of State laws and regulations that would inhibit innovation by presenting developers of these technologies multiple sets of potentially conflicting standards.
 

The Policy is a framework to foster the safe testing and deployment of automated vehicles, delineate State versus Federal roles, clarify current regulatory tools, and begin discussions and considerations of potential additional regulatory tools. The Safety Assessment Letter discussed in the Vehicle Performance Guidance section is a voluntary submission by any entity testing or deploying HAV. Entities are not required to submit a Safety Assessment Letter; there is no enforceable requirement to comply with the Policy as it relates to the Safety Assessment Letter. The Policy does contemplate that in the future, the Agency may engage in a rulemaking to require the submission of the Safety Assessment Letter (p. 15).

To facilitate voluntary submissions, NHTSA has developed an illustrative template as an example of the type and amount of information the Agency is requesting. The Agency is developing additional templates for receipt notifications and supplemental information requests, to be used in the event that further dialogue is needed on one or more of the 15-point safety assessment areas. These do not involve a burden-hour increase from the original estimate provided.
 
Lastly, the Safety Assessment Letter is not intended to be used as an enforcement tool. If automated safety technology or equipment pose an unreasonable risk to safety, the Agency, in accordance with NHTSA Enforcement Guidance Bulletin 2016-02: Safety-Related Defects and Automated Safety Technologies, published concurrently in the Federal Register with the Policy on September 23, 2016, will use all tools at its disposal to protect against unreasonable risk of harm that may occur because of the design, construction or performance of a motor vehicle or motor vehicle equipment. NHTSA’s existing authority and responsibility covers defects that create unreasonable risks to safety that may arise in connection with automated vehicles.

Four-Month Waiting Period Post Safety Assessment Letter Submission

Page 16, under Section I:  Vehicle Performance Guidance for Automated Vehicles, states, “…NHTSA would expect manufacturers and other entities to provide a safety assessment letter at least four months before active public road testing begins on a new automated feature.”

The four-month reference is intended to be the maximum amount of time NHTSA expects to take for review of the Safety Assessment Letter and any dialogue with an entity to begin, if necessary. However, we do not expect that each exchange will take four months, rather up to four months. While NHTSA strongly encourages submission of a Safety Assessment Letter prior to testing and deployment, entities are neither required to submit a letter nor to delay testing or deployment based on the submission and evaluation of a letter. There is no mandatory waiting period.

Signatures for Safety Assessment Letter

Page 16, under Section I: Vehicle Performance Guidance for Automated Vehicles, states, “For each area, the Safety Assessment should include an acknowledgment that indicates one of three options… Next to the checked line item, the submitter should include the name, title, and signature of an authorized company official and the date.

NHTSA has not stipulated who within an organization should be the signatory of the Safety Assessment Letter or the 15 points to be included in such a letter. NHTSA envisions that the signatory for each of the 15 points should be an individual with expert knowledge in that area and authority to speak for the entity. Depending on the entity, this could be one person for all safety assessment points or different individuals for different areas. 

Submission of a Revised Safety Assessment Letter

Page 17 of the Policy discusses changes to software that would constitute submission of a revised Safety Assessment Letter. In general, a revised letter is appropriate whenever a manufacturer or entity makes software or hardware updates that constitute a significant change to any of the 15 elements in the Safety Assessment. It is not necessary, however, to submit a revised letter that contains all of the 15 points. Rather the revised letter need only address those elements that have changed significantly. 

Specific examples from the Policy include: 

“If these software or hardware updates materially change the way in which the vehicle complies with any of the 15 elements of the Guidance, the agency would deem the update to be one that would necessitate provision of a Safety Assessment to the agency summarizing that particular change.” (p. 17)

“For the HAV OEDR capability, if there is a change to the set of normal driving scenarios or pre-crash scenarios that the HAV system has the capability to address as a result of a software or hardware update, then this should also be summarized in revised Safety Assessment.” (p. 17)

With respect to fall back strategy, “If the fall back strategy and the resulting implementation for achieving a minimum risk condition is changed by a software or hardware change, this change should be addressed in a new or revised Safety Assessment.” (p. 17)

Confidential Business Information

On page 15, the Policy states that the Safety Assessment Letter should be sent to NHTSA’s Office of the Chief Counsel. Further, entities should follow NHTSA’s CBI regulation (49 CFR Part 512) to handle such information. CBI may be submitted separately from a Safety Assessment Letter, and should be cross-referenced in the Letter. 

Data Collection and Sharing

On Page 18, Section I: Vehicle Performance Guidance for Automated Vehicles, E. Cross-Cutting Areas of Guidance, 1. Data Recording and Sharing requests that “manufacturers and other entities should collect, store and analyze data regarding positive outcomes.” The Policy defines positive outcomes as, “events in which the HAV system correctly detects a safety relevant situation, and successfully avoids an incident (e.g., “near misses”….).” 

NHTSA intends for manufacturers and other entities to collect information involving positive outcomes. Near misses, as a subset of positive outcomes, are those incidents in which the “automated function correctly detects and identifies an unsafe maneuver initiated by another road user and executes an appropriate response that successfully avoids an event, incident, or crash” as stated on page 18 of the Policy. Thus a successful maneuver through such a situation constitutes a near miss, but the circumstances around the event may be important to share with other entities as systems are developed. 

NHTSA expects that each entity will develop an appropriate definition according to its testing and deployment plans. Based on the input of those entities, NHTSA will consider whether further clarification is necessary with respect to what constitutes a near miss incident.

The Policy states, “each entity should develop a plan for sharing its event reconstruction and other relevant data with other entities. Shared data will help to accelerate knowledge and understanding of HAV performance, and could be used to enhance the safety of HAV systems and establish consumer confidence in HAV technologies.” The Policy does not require entities to share data, rather it recommends development of a plan for sharing data to increase the broad knowledge base. NHTSA recognizes that additional coordination with industry is needed to determine what data can be shared. 

Creation of an Automated Safety Technology Committee

NHTSA does not expect States to create any entity in order to have a fully functioning automated safety technology committee; however, States may decide to create some of these entities. On page 40, under Section II:  Model State Policy, C.1. Administrative, NHTSA included recommendations to assist in the safe and knowledgeable introduction of automated vehicles onto the States’ roadways. Recommendation b. stated: 

Each State should create a jurisdictional automated safety technology committee that is launched by the designated lead agency and which includes representatives from the governor’s office, the motor vehicle administration, the State department of transportation, the State law enforcement agency, the State Highway Safety Office, office of information technology, State insurance regulator, the State office(s) representing the aging and disabled communities, toll authorities, and transit authorities.

The references to these specific entities were intended as examples of those that may be appropriate for participation in an automated safety technology committee. They are not requirements. NHTSA recognizes that some of the listed entities may not exist in all States. The committee structure may vary from State to State.

Application to Test and Jurisdictional Permission to Test

Page 41, Section II: Model State Policy, C.2.g. Application for Manufacturers or Other Entities to Test HAVs on Public Roadways states, “The application should identify each test operator, their driver’s license number, and the jurisdiction or country in which the operator is licensed.” Page 43, Section II.C.3.g. Jurisdictional Permission to Test states, “Each test vehicle should be properly registered and titled in accordance with the State’s laws.” Under both referenced sections, the intent was for authority to reside with the State jurisdiction. 

Driver Background Check

Page 43, Section II. Model State Policy, C.4.Testing by the Manufacturer or Other Entity, Recommendation d. states, “Before being allowed to operate a test vehicle, the persons designated by the manufacturer or other entity as operators of the test vehicles may be subjected to a background check including, but not limited to, a driver history review and a criminal history check.”

The Policy does not require such testing but rather suggests that States consider developing authority to test drivers. The choice of whether or not to conduct background checks is at the discretion of the State.  

Scope of the Vehicle Performance Guidance

The intent of the policy is to address the entire spectrum of partially to fully automated systems. The SAE Levels of Automation refer to the capabilities and functions of automated systems. The entire policy includes all levels of automation (L2-L5) because a manufacturer or supplier can alter the classification of its automation by adding or omitting capabilities and functions.
    
Table 1 on page 34 of the Policy details each of the 15 safety points and whether each applies to Level 2 systems/vehicles as well as compared to Levels 3 to 5 systems/vehicles.

Entities submitting a letter for Level 2 automated systems should pay particular attention to Section I:  Vehicle Performance Guidance for Automated Vehicles, G. Guidance for Lower Levels of Automated Vehicle Systems starting on page 31. Table 1 on page 34 of the Policy details each of the 15 safety points and whether each applies to Level 2 systems/vehicles.  

Page 12, Section I: Vehicle Performance Guidance for Automated Vehicles, B. Scope, states, “This Guidance is intended for vehicles that are tested and deployed for use on public roadways. This includes light-, medium-, and heavy-duty vehicles.”  The Guidance is intended to be applied to any motor vehicle under the jurisdiction of NHTSA operated on public roadways including, but not limited to low-speed vehicles, motorcycles, passenger vehicles, medium-duty vehicles, and heavy-duty vehicles. 

Search for more resources

7 Results
Title Type Audience Date
 
HS 812 222 Evaluation of Light Vehicle V2V Communication Safety Applications PDF, 4.31 MB
Document Researchers 04/13/2017
Federal Automated Vehicles Policy Public Meeting PDF, 125.79 KB
Document Trade Groups, Vehicle Manufacturers 11/10/2016
U.S. DOT announces public meeting on Federal Automated Vehicles Policy
Press Release 11/01/2016
Workshop on Governance of the Safety of Automated Vehicles PDF, 664.29 KB
Document Trade Groups, Vehicle Manufacturers 10/20/2016
U.S. DOT issues Federal Policy for safe testing and deployment of automated vehicles
Press Release 09/20/2016
Related resources for this topic
B-Roll of Automated Vehicles

Public Comments

DOT wants to hear from you about the Federal Automated Vehicles Policy. NHTSA accepted comments through November 22, 2016, on our public docket. You can submit as many attachments as you like, but we appreciate if your main comments are in English and limited to 15 pages. Regulations.gov does not edit comments, so if you would like to submit confidential information for the Agency to consider, please follow the instructions found in the Federal Register Notice. If you have any questions about how to submit comments, please call NHTSA's Office of the Chief Counsel at 202-366-2992.