Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies., 31296-31297 [2016-11635]

Download as PDF 31296 Federal Register / Vol. 81, No. 96 / Wednesday, May 18, 2016 / Notices Privacy Act Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT’s complete Privacy Act Statement in the Federal Register published on April 11, 2000 (Volume 65, Number 70; Pages 19477–78). FOR FURTHER INFORMATION CONTACT: By Order of the Maritime Administrator. Dated: May 10, 2016. T. Mitchell Hudson, Jr., Secretary, Maritime Administration. Intended Commercial Use of Vessel: ‘‘Crewed Yacht Charter’’ Geographic Region: ‘‘Puerto Rico, Florida’’ [FR Doc. 2016–11725 Filed 5–17–16; 8:45 am] BILLING CODE 4910–81–P DEPARTMENT OF TRANSPORTATION Maritime Administration [Docket No. MARAD–2016 0050] Requested Administrative Waiver of the Coastwise Trade Laws: Vessel FEEL THE MAGIC; Invitation for Public Comments Maritime Administration, Department of Transportation. ACTION: Notice. AGENCY: As authorized by 46 U.S.C. 12121, the Secretary of Transportation, as represented by the Maritime Administration (MARAD), is authorized to grant waivers of the U.S.-build requirement of the coastwise laws under certain circumstances. A request for such a waiver has been received by MARAD. The vessel, and a brief description of the proposed service, is listed below. DATES: Submit comments on or before June 17, 2016. ADDRESSES: Comments should refer to docket number MARAD–2016–0050. Written comments may be submitted by hand or by mail to the Docket Clerk, U.S. Department of Transportation, Docket Operations, M–30, West Building Ground Floor, Room W12–140, 1200 New Jersey Avenue SE., Washington, DC 20590. You may also send comments electronically via the Internet at http://www.regulations.gov. All comments will become part of this docket and will be available for inspection and copying at the above address between 10 a.m. and 5 p.m., E.T., Monday through Friday, except federal holidays. An electronic version of this document and all documents entered into this docket is available on the World Wide Web at http:// www.regulations.gov. sradovich on DSK3TPTVN1PROD with NOTICES SUMMARY: VerDate Sep<11>2014 17:10 May 17, 2016 Jkt 238001 Bianca Carr, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE., Room W23–453, Washington, DC 20590. Telephone 202– 366–9309, Email Bianca.carr@dot.gov. As described by the applicant the intended service of the vessel FEEL THE MAGIC is: SUPPLEMENTARY INFORMATION: The complete application is given in DOT docket MARAD–2016–0050 at http://www.regulations.gov. Interested parties may comment on the effect this action may have on U.S. vessel builders or businesses in the U.S. that use U.S.flag vessels. If MARAD determines, in accordance with 46 U.S.C. 12121 and MARAD’s regulations at 46 CFR part 388, that the issuance of the waiver will have an unduly adverse effect on a U.S.vessel builder or a business that uses U.S.-flag vessels in that business, a waiver will not be granted. Comments should refer to the docket number of this notice and the vessel name in order for MARAD to properly consider the comments. Comments should also state the commenter’s interest in the waiver application, and address the waiver criteria given in § 388.4 of MARAD’s regulations at 46 CFR part 388. Privacy Act Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT’s complete Privacy Act Statement in the Federal Register published on April 11, 2000 (Volume 65, Number 70; Pages 19477–78). By Order of the Maritime Administrator. Dated: May 10, 2016. T. Mitchell Hudson, Jr., Secretary, Maritime Administration. [FR Doc. 2016–11714 Filed 5–17–16; 8:45 am] BILLING CODE 4910–81–P PO 00000 Frm 00073 Fmt 4703 Sfmt 4703 DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration [DOT Docket No. NHTSA –2016–0036] Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies. National Highway Traffic Safety Administration (NHTSA), DOT. ACTION: Extension of comment period for proposed Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies AGENCY: This document extends the comment period on planned guidelines for the safe deployment and operation of automated vehicles. The intent of the operational guidance is to encourage innovative and safe deployment of automated vehicle technologies. Written statements and supporting information submitted during the comment period will be considered with the same weight as oral comments and supporting information presented at the public meetings. The comment due date was May 9, 2016. Comments continue to come in and requests have been made to extend the period to provide comments on this important topic. This document grants that request and extends the comment due date for the planned Guidelines to May 31, 2016. DATES: The due date for comments on DOT Docket No. NHTSA–2016–0036 is extended to May 31, 2016 ADDRESSES: Please submit all written comments no later than May 31, 2016, by any of the following methods: • Federal Rulemaking Portal: Go to http://www.regulations.gov. Follow the online instructions for submitting comments. • Mail: Docket Management Facility: U.S. Department of Transportation, 1200 New Jersey Avenue SE., West Building Ground Floor, Room W12–140, Washington, DC 20590–0001. • Hand Delivery or Courier: 1200 New Jersey Avenue SE., West Building Ground Floor, Room W12–140, Washington, DC 20590–0001, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal Holidays. • Fax: 202–366–1767. Instructions: All submissions must include the agency name and docket number. Note that all comments received will be posted without change to http://www.regulations.gov, including any personal information provided. Please see the Privacy Act discussion below. SUMMARY: E:\FR\FM\18MYN1.SGM 18MYN1 Federal Register / Vol. 81, No. 96 / Wednesday, May 18, 2016 / Notices sradovich on DSK3TPTVN1PROD with NOTICES Docket: For access to the docket go to http://www.regulations.gov at any time or to 1200 New Jersey Avenue SE., West Building, Ground Floor, Room W12– 140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal Holidays. Telephone: 202–366–9826. Privacy Act: Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT’s complete Privacy Act Statement in the Federal Register published on April 11, 2000 (Volume 65, Number 70; Pages 19477–78), or you may visit http://www.regulations.gov/ privacy.html. Confidential Business Information: If you wish to submit any information under a claim of confidentiality, you should submit three copies of your complete submission, including the information you claim to be confidential business information to the Chief Counsel, NHTSA, at the address given under FOR FURTHER INFORMATION CONTACT. In addition, you should submit two copies, from which you have deleted the claimed confidential business information, to Docket Management at the address given above. When you send a comment containing information claimed to be confidential business information, you should submit a cover letter setting forth the information specified in our confidential business information regulation (49 CFR part 512). SUPPLEMENTARY INFORMATION: Background DOT recently announced a series of actions to remove potential roadblocks to the integration of innovative automotive technology. As part of this effort, the Department announced several milestones for 2016, including development of guidance on the safe deployment and operation of automated vehicles. NHTSA held two public meetings where participants could address a panel on the topic of guidance on the safe deployment and operation of automated vehicles. The meetings were held in Washington, DC on April 8, 2016, and in Stanford, CA on April 27, 2016. Public Meeting Topics During the public meetings NHTSA sought input on the following topics: 1. Evaluation and testing of scenarios the AV system should detect and correctly operate in: Within the AV VerDate Sep<11>2014 17:10 May 17, 2016 Jkt 238001 system’s operating envelope, consider how to identify the scenarios that could be encountered by the AV system (e.g., behavioral competencies/normal driving, pre-crash scenarios, etc.) and what design and evaluation (testing) processes and methods are needed to ensure that the vehicle can detect and appropriately react to these scenarios. Consider whether third party testing is appropriate for validating test results. 2. Detection and communication of operational boundaries: If there are limitations on where AV technology will operate—what methods should the AV technology use to sense when it is reaching the operational domain limit and how should that be communicated to the driver? 3. Environmental operation and sensing: Consider what environmental conditions AV systems will likely operate in. For environmental conditions in which AV systems are not designed to operate, discuss methods used to detect these conditions. 4. Driver transitioning to/from AV operating mode: For AV systems that rely on transferring vehicle operation back to the driver, discuss approaches to (a) ensuring safe transitioning back to a fully capable non-impaired driver (e.g., geo-fencing, adverse weather) and (b) how non-optimal driver behavior (e.g., decision errors, erratic behavior, driver impairment) will be addressed by the AV system. 5. AV for persons with disabilities: Consider the unique needs of people with different types of disabilities in the design, development, and policy setting for self-driving cars and related automation. 6. Data: Consider data recording capabilities of system(s) necessary to monitor the correct operation of the AV system, and what are appropriate triggers (crash, near crash, etc.) to determine system operational status or possible malfunction of the system. Also consider how recorded data could be accessed and by whom. During the testing phase, consider what data should be made public for further analysis and understanding. 7. Crash avoidance capability: Consider the capabilities of AV systems with respect to detecting roadway hazards (other vehicles, pedestrians, animals, etc.) such that common crash scenarios involving these hazards (control loss, crossing paths head-on, etc.) can be detected and either avoided or mitigated. 8. Electronics systems safety: Consider methods and potential documentation that could be produced with respect to functional safety and cybersecurity. PO 00000 Frm 00074 Fmt 4703 Sfmt 9990 31297 9. Non-passenger AVs: Consider differences between AVs designed for delivery of goods and products that are not intended to have a human operator or potentially even human passengers. 10. Aspects of AV technology that may not be suitable or ready for guidelines: For these areas, information would be useful on alternative approaches to assure safety. 11. Identification of industry voluntary standards, best practices, etc., related to automated vehicle operation. 12. Information AVs may need to communicate to pedestrians and other vehicles (manual or automated) just as a driver would. Consider situations such as pedestrians crossing a travel lane in a parking lot and how this communication should be accomplished. 13. Conditions in which AVs may need to be able to identify and communicate to a central location or authority that a problem has occurred. Consider situations where passengers may be delivered to their destination but a medical problem or potential incapacitation enroute may potentially suggest considerations for vehicle capabilities that could handle such cases. 14. Operation of an AV with open safety recall: Consider if automated vehicles should be allowed to operate in automated mode in cases when there is an open safety recall on that vehicle or if automated functions should be restrained until recall repairs are completed (perhaps reversion to manual driving when possible). Consider if AVs with open recalls should be allowed to operate on public roads at all, and if so, under what conditions. 15. Other topics needed for operational guidance: Other topics that would be beneficial to address in an operational guidance document to facilitate innovation and safe deployment of these systems on public roadways. Issued in Washington, DC, under authority delegated by 49 CFR 1.95. Nathaniel Beuse, Associate Administrator for Vehicle Safety Research. [FR Doc. 2016–11635 Filed 5–17–16; 8:45 am] BILLING CODE 4910–59–P E:\FR\FM\18MYN1.SGM 18MYN1

Agencies

[Federal Register Volume 81, Number 96 (Wednesday, May 18, 2016)]
[Notices]
[Pages 31296-31297]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2016-11635]


-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

National Highway Traffic Safety Administration

[DOT Docket No. NHTSA -2016-0036]


Guidelines for the Safe Deployment and Operation of Automated 
Vehicle Safety Technologies.

AGENCY: National Highway Traffic Safety Administration (NHTSA), DOT.

ACTION: Extension of comment period for proposed Guidelines for the 
Safe Deployment and Operation of Automated Vehicle Safety Technologies

-----------------------------------------------------------------------

SUMMARY: This document extends the comment period on planned guidelines 
for the safe deployment and operation of automated vehicles. The intent 
of the operational guidance is to encourage innovative and safe 
deployment of automated vehicle technologies. Written statements and 
supporting information submitted during the comment period will be 
considered with the same weight as oral comments and supporting 
information presented at the public meetings. The comment due date was 
May 9, 2016.
    Comments continue to come in and requests have been made to extend 
the period to provide comments on this important topic. This document 
grants that request and extends the comment due date for the planned 
Guidelines to May 31, 2016.

DATES: The due date for comments on DOT Docket No. NHTSA-2016-0036 is 
extended to May 31, 2016

ADDRESSES: Please submit all written comments no later than May 31, 
2016, by any of the following methods:
     Federal Rulemaking Portal: Go to http://www.regulations.gov. Follow the online instructions for submitting 
comments.
     Mail: Docket Management Facility: U.S. Department of 
Transportation, 1200 New Jersey Avenue SE., West Building Ground Floor, 
Room W12-140, Washington, DC 20590-0001.
     Hand Delivery or Courier: 1200 New Jersey Avenue SE., West 
Building Ground Floor, Room W12-140, Washington, DC 20590-0001, between 
9 a.m. and 5 p.m. ET, Monday through Friday, except Federal Holidays.
     Fax: 202-366-1767.
    Instructions: All submissions must include the agency name and 
docket number. Note that all comments received will be posted without 
change to http://www.regulations.gov, including any personal 
information provided. Please see the Privacy Act discussion below.

[[Page 31297]]

    Docket: For access to the docket go to http://www.regulations.gov 
at any time or to 1200 New Jersey Avenue SE., West Building, Ground 
Floor, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., 
Monday through Friday, except Federal Holidays. Telephone: 202-366-
9826.
    Privacy Act: Anyone is able to search the electronic form of all 
comments received into any of our dockets by the name of the individual 
submitting the comment (or signing the comment, if submitted on behalf 
of an association, business, labor union, etc.). You may review DOT's 
complete Privacy Act Statement in the Federal Register published on 
April 11, 2000 (Volume 65, Number 70; Pages 19477-78), or you may visit 
http://www.regulations.gov/privacy.html.
    Confidential Business Information: If you wish to submit any 
information under a claim of confidentiality, you should submit three 
copies of your complete submission, including the information you claim 
to be confidential business information to the Chief Counsel, NHTSA, at 
the address given under FOR FURTHER INFORMATION CONTACT. In addition, 
you should submit two copies, from which you have deleted the claimed 
confidential business information, to Docket Management at the address 
given above. When you send a comment containing information claimed to 
be confidential business information, you should submit a cover letter 
setting forth the information specified in our confidential business 
information regulation (49 CFR part 512).

SUPPLEMENTARY INFORMATION:

Background

    DOT recently announced a series of actions to remove potential 
roadblocks to the integration of innovative automotive technology. As 
part of this effort, the Department announced several milestones for 
2016, including development of guidance on the safe deployment and 
operation of automated vehicles.
    NHTSA held two public meetings where participants could address a 
panel on the topic of guidance on the safe deployment and operation of 
automated vehicles. The meetings were held in Washington, DC on April 
8, 2016, and in Stanford, CA on April 27, 2016.

Public Meeting Topics

    During the public meetings NHTSA sought input on the following 
topics:
    1. Evaluation and testing of scenarios the AV system should detect 
and correctly operate in: Within the AV system's operating envelope, 
consider how to identify the scenarios that could be encountered by the 
AV system (e.g., behavioral competencies/normal driving, pre-crash 
scenarios, etc.) and what design and evaluation (testing) processes and 
methods are needed to ensure that the vehicle can detect and 
appropriately react to these scenarios. Consider whether third party 
testing is appropriate for validating test results.
    2. Detection and communication of operational boundaries: If there 
are limitations on where AV technology will operate--what methods 
should the AV technology use to sense when it is reaching the 
operational domain limit and how should that be communicated to the 
driver?
    3. Environmental operation and sensing: Consider what environmental 
conditions AV systems will likely operate in. For environmental 
conditions in which AV systems are not designed to operate, discuss 
methods used to detect these conditions.
    4. Driver transitioning to/from AV operating mode: For AV systems 
that rely on transferring vehicle operation back to the driver, discuss 
approaches to (a) ensuring safe transitioning back to a fully capable 
non-impaired driver (e.g., geo-fencing, adverse weather) and (b) how 
non-optimal driver behavior (e.g., decision errors, erratic behavior, 
driver impairment) will be addressed by the AV system.
    5. AV for persons with disabilities: Consider the unique needs of 
people with different types of disabilities in the design, development, 
and policy setting for self-driving cars and related automation.
    6. Data: Consider data recording capabilities of system(s) 
necessary to monitor the correct operation of the AV system, and what 
are appropriate triggers (crash, near crash, etc.) to determine system 
operational status or possible malfunction of the system. Also consider 
how recorded data could be accessed and by whom. During the testing 
phase, consider what data should be made public for further analysis 
and understanding.
    7. Crash avoidance capability: Consider the capabilities of AV 
systems with respect to detecting roadway hazards (other vehicles, 
pedestrians, animals, etc.) such that common crash scenarios involving 
these hazards (control loss, crossing paths head-on, etc.) can be 
detected and either avoided or mitigated.
    8. Electronics systems safety: Consider methods and potential 
documentation that could be produced with respect to functional safety 
and cybersecurity.
    9. Non-passenger AVs: Consider differences between AVs designed for 
delivery of goods and products that are not intended to have a human 
operator or potentially even human passengers.
    10. Aspects of AV technology that may not be suitable or ready for 
guidelines: For these areas, information would be useful on alternative 
approaches to assure safety.
    11. Identification of industry voluntary standards, best practices, 
etc., related to automated vehicle operation.
    12. Information AVs may need to communicate to pedestrians and 
other vehicles (manual or automated) just as a driver would. Consider 
situations such as pedestrians crossing a travel lane in a parking lot 
and how this communication should be accomplished.
    13. Conditions in which AVs may need to be able to identify and 
communicate to a central location or authority that a problem has 
occurred. Consider situations where passengers may be delivered to 
their destination but a medical problem or potential incapacitation 
enroute may potentially suggest considerations for vehicle capabilities 
that could handle such cases.
    14. Operation of an AV with open safety recall: Consider if 
automated vehicles should be allowed to operate in automated mode in 
cases when there is an open safety recall on that vehicle or if 
automated functions should be restrained until recall repairs are 
completed (perhaps reversion to manual driving when possible). Consider 
if AVs with open recalls should be allowed to operate on public roads 
at all, and if so, under what conditions.
    15. Other topics needed for operational guidance: Other topics that 
would be beneficial to address in an operational guidance document to 
facilitate innovation and safe deployment of these systems on public 
roadways.

    Issued in Washington, DC, under authority delegated by 49 CFR 
1.95.
Nathaniel Beuse,
Associate Administrator for Vehicle Safety Research.
[FR Doc. 2016-11635 Filed 5-17-16; 8:45 am]
 BILLING CODE 4910-59-P