81 FR 14934 - Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies
DEPARTMENT OF TRANSPORTATION
National Highway Traffic Safety Administration Federal Register Volume 81, Issue 53 (March 18, 2016)
National Highway Traffic Safety Administration
Federal Register Volume 81, Issue 53 (March 18, 2016)
| Page Range | 14934-14936 | |
| FR Document | 2016-06143 |
[Federal Register Volume 81, Number 53 (Friday, March 18, 2016)] [Notices] [Pages 14934-14936] From the Federal Register Online [www.thefederalregister.org] [FR Doc No: 2016-06143] ----------------------------------------------------------------------- DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration [Docket No. NHTSA-2016-0036] Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies AGENCY: National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT). ACTION: Announcement of public meeting. ----------------------------------------------------------------------- SUMMARY: NHTSA is announcing a public meeting to seek input 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. At this meeting, NHTSA is seeking public input on those aspects of automated vehicle (AV) systems that would benefit from operational guidelines. For example, of high importance to the Agency is information on the roadway scenarios and operational environments highly automated vehicles will need to address and the associated design and evaluation processes and methods needed to ensure that AV systems can detect and appropriately react to these scenarios such that a high level of safety is assured when these systems are deployed on US roadways. Also of interest would be input on aspects of automated vehicle technology that may not be suitable or ready for guidelines. For these areas, information would be useful on alternative approaches to assure safety. DATES: NHTSA will hold the public meeting on April 8, 2016, in [[Page 14935]] Washington, DC. The meeting will start at 9:00 a.m. and continue until 4:00 p.m., local time. Check-in (through security) will begin at 8 a.m. (Note: A second public meeting will be held on the West Coast (California), and details for that meeting will be announced in a separate Federal Register (FR) Notice.) ADDRESSES: The meeting will be held at the U.S. Department of Transportation, West Building, Ground Floor Atrium, 1200 New Jersey Avenue SE., Washington, DC 20590. This facility is accessible to individuals with disabilities. The meeting will also be webcast live, and a link to the actual webcast will be available through http://www.nhtsa.gov/Research/Crash+Avoidance/Automated+Vehicles. FOR FURTHER INFORMATION CONTACT: If you have questions about the public meeting, please contact us at [email protected]. Registration is necessary for all attendees. Attendees should register at http://goo.gl/forms/l8z3HVM6hw by April 1, 2016. Please provide name and affiliation, indicate if you wish to offer technical remarks, and please indicate whether you require accommodations such as a sign language interpreter. Space is limited, so advanced registration is highly encouraged. Although attendees will be given the opportunity to offer technical remarks, there will not be time for attendees to make audio-visual presentations during the meeting. Note: We may not be able to accommodate all attendees who wish to make oral remarks. Should it be necessary to cancel the meeting due to inclement weather or other emergency, NHTSA will take all available measures to notify registered participants. NHTSA will conduct the public meeting informally, and technical rules of evidence will not apply. We will arrange for a written transcript of the meeting and keep the official record open for 30 days after the meeting to allow submission of supplemental information. You may make arrangements for copies of the transcripts directly with the court reporter, and the transcript will also be posted in the docket when it becomes available. Written Comments: 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 meeting. Please submit all written comments no later than May 9, 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. 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, several milestones were announced for 2016, including development of guidance on the safe deployment and operation of automated vehicles. Draft Agenda 08:00-09:00--Arrival/Check-In 09:00-12:00--Morning Public Meeting Session 12:00-13:00--Lunch Break 13:00-16:00--Afternoon Public Meeting Session 16:00-Adjourn Public Meeting Topics NHTSA is seeking input on the following topics during the morning and afternoon sessions of the meeting. 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 will be addressed by the AV system (e.g., decision errors, erratic behavior, driver impairment.) 5. 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 [[Page 14936]] accessed and by whom. During the testing phase, consider what data should be made public for further analysis and understanding. 6. 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. 7. Electronics systems safety: Consider methods and potential documentation that could be produced with respect to functional safety and cybersecurity. 8. 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. 9. 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. 10. Identification of industry voluntary standards, best practices, etc., related to automated vehicle operation. 11. Information AV's 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. 12. 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-06143 Filed 3-17-16; 8:45 am] BILLING CODE 4910-59-P
![14934 Federal Register / Vol. 81, No. 53 / Friday, March 18, 2016 / Notices
Alaska (excluding waters in certain circumstances. A request for Privacy Act
Southeastern Alaska and waters north such a waiver has been received by Anyone is able to search the
of a line between Gore Point to Cape MARAD. The vessel, and a brief electronic form of all comments
Suckling [including the North Gulf description of the proposed service, is received into any of our dockets by the
Coast and Prince William Sound])’’ listed below. name of the individual submitting the
The complete application is given in DATES: Submit comments on or before comment (or signing the comment, if
DOT docket MARAD–2016–0029 at April 18, 2016. submitted on behalf of an association,
http://www.regulations.gov. Interested ADDRESSES: Comments should refer to business, labor union, etc.). You may
parties may comment on the effect this docket number MARAD–2016–0026. review DOT’s complete Privacy Act
action may have on U.S. vessel builders Written comments may be submitted by Statement in the Federal Register
or businesses in the U.S. that use U.S.- hand or by mail to the Docket Clerk, published on April 11, 2000 (Volume
flag vessels. If MARAD determines, in U.S. Department of Transportation, 65, Number 70; Pages 19477–78).
accordance with 46 U.S.C. 12121 and Docket Operations, M–30, West By Order of the Maritime Administrator.
MARAD’s regulations at 46 CFR part Building Ground Floor, Room W12–140, Dated: March 8, 2016.
388, that the issuance of the waiver will 1200 New Jersey Avenue SE.,
have an unduly adverse effect on a U.S.- T. Mitchell Hudson, Jr.,
Washington, DC 20590. You may also
vessel builder or a business that uses Secretary, Maritime Administration.
send comments electronically via the
U.S.-flag vessels in that business, a Internet at http://www.regulations.gov. [FR Doc. 2016–06100 Filed 3–17–16; 8:45 am]
waiver will not be granted. Comments All comments will become part of this BILLING CODE 4910–81–P
should refer to the docket number of docket and will be available for
this notice and the vessel name in order inspection and copying at the above
for MARAD to properly consider the address between 10 a.m. and 5 p.m., DEPARTMENT OF TRANSPORTATION
comments. Comments should also state E.T., Monday through Friday, except National Highway Traffic Safety
the commenter’s interest in the waiver federal holidays. An electronic version Administration
application, and address the waiver of this document and all documents
criteria given in § 388.4 of MARAD’s entered into this docket is available on [Docket No. NHTSA–2016–0036]
regulations at 46 CFR part 388. the World Wide Web at http://
www.regulations.gov. Guidelines for the Safe Deployment
Privacy Act and Operation of Automated Vehicle
FOR FURTHER INFORMATION CONTACT: Safety Technologies
Anyone is able to search the
electronic form of all comments Bianca Carr, U.S. Department of
Transportation, Maritime AGENCY: National Highway Traffic
received into any of our dockets by the Safety Administration (NHTSA),
name of the individual submitting the Administration, 1200 New Jersey
Avenue SE., Room W23–453, Department of Transportation (DOT).
comment (or signing the comment, if
Washington, DC 20590. Telephone 202– ACTION: Announcement of public
submitted on behalf of an association,
366–9309, Email Bianca.carr@dot.gov. meeting.
business, labor union, etc.). You may
review DOT’s complete Privacy Act SUPPLEMENTARY INFORMATION: As
SUMMARY: NHTSA is announcing a
Statement in the Federal Register described by the applicant the intended
public meeting to seek input on planned
published on April 11, 2000 (Volume service of the vessel BLACKBIRD X is:
guidelines for the safe deployment and
65, Number 70; Pages 19477–78). Intended Commercial Use of Vessel: As operation of automated vehicles. The
a hovercraft charter business during intent of the operational guidance is to
By Order of the Maritime Administrator.
Spring and Summer. If chartering encourage innovative and safe
Dated: March 8, 2016.
includes sport fishing, the fish caught deployment of automated vehicle
T. Mitchell Hudson, Jr., would NOT be sold commercially
Secretary, Maritime Administration.
technologies.
Geographic Region: ‘‘New York, At this meeting, NHTSA is seeking
[FR Doc. 2016–06101 Filed 3–17–16; 8:45 am] Connecticut’’ public input on those aspects of
BILLING CODE 4910–81–P automated vehicle (AV) systems that
The complete application is given in
DOT docket MARAD–2016–0026 at would benefit from operational
http://www.regulations.gov. Interested guidelines. For example, of high
DEPARTMENT OF TRANSPORTATION
parties may comment on the effect this importance to the Agency is information
Maritime Administration action may have on U.S. vessel builders on the roadway scenarios and
or businesses in the U.S. that use U.S.- operational environments highly
[Docket No. MARAD–2016–0026] flag vessels. If MARAD determines, in automated vehicles will need to address
accordance with 46 U.S.C. 12121 and and the associated design and
Requested Administrative Waiver of evaluation processes and methods
MARAD’s regulations at 46 CFR part
the Coastwise Trade Laws: Vessel needed to ensure that AV systems can
388, that the issuance of the waiver will
BLACKBIRD X; Invitation for Public detect and appropriately react to these
have an unduly adverse effect on a U.S.-
Comments scenarios such that a high level of safety
vessel builder or a business that uses
AGENCY: Maritime Administration, U.S.-flag vessels in that business, a is assured when these systems are
waiver will not be granted. Comments deployed on US roadways.
asabaliauskas on DSK3SPTVN1PROD with NOTICES
Department of Transportation.
ACTION: Notice. should refer to the docket number of Also of interest would be input on
this notice and the vessel name in order aspects of automated vehicle technology
SUMMARY: As authorized by 46 U.S.C. for MARAD to properly consider the that may not be suitable or ready for
12121, the Secretary of Transportation, comments. Comments should also state guidelines. For these areas, information
as represented by the Maritime the commenter’s interest in the waiver would be useful on alternative
Administration (MARAD), is authorized application, and address the waiver approaches to assure safety.
to grant waivers of the U.S.-build criteria given in § 388.4 of MARAD’s DATES: NHTSA will hold the public
requirement of the coastwise laws under regulations at 46 CFR part 388. meeting on April 8, 2016, in
VerDate Sep<11>2014 19:50 Mar 17, 2016 Jkt 238001 PO 00000 Frm 00113 Fmt 4703 Sfmt 4703 E:\FR\FM\18MRN1.SGM 18MRN1](https://thefederalregister.org/doc/81_FR_14987/page/1.svg)
![14936 Federal Register / Vol. 81, No. 53 / Friday, March 18, 2016 / Notices
accessed and by whom. During the communication should be been in process for 180 days or more.
testing phase, consider what data accomplished. The reason(s) for delay and the expected
should be made public for further 12. Other topics needed for completion date for action on each
analysis and understanding. operational guidance: Other topics that application is provided in association
6. Crash avoidance capability: would be beneficial to address in an with each identified application.
Consider the capabilities of AV systems operational guidance document to
facilitate innovation and safe FOR FURTHER INFORMATION CONTACT:
with respect to detecting roadway
deployment of these systems on public Ryan Paquet, Director, Office of
hazards (other vehicles, pedestrians,
roadways. Hazardous Materials Special Permits
animals, etc.) such that common crash
and Approvals, Pipeline and Hazardous
scenarios involving these hazards Issued in Washington, DC, under authority Materials Safety Administration, U.S.
(control loss, crossing paths head-on, delegated by 49 CFR 1.95.
Department of Transportation, East
etc.) can be detected and either avoided Nathaniel Beuse,
Building, PHH–30, 1200 New Jersey
or mitigated. Associate Administrator for Vehicle Safety
7. Electronics systems safety: Consider Avenue SE., Washington, DC 20590–
Research.
methods and potential documentation 0001, (202) 366–4535.
[FR Doc. 2016–06143 Filed 3–17–16; 8:45 am]
that could be produced with respect to BILLING CODE 4910–59–P Key to ‘‘Reason for Delay’’
functional safety and cybersecurity. 1. Awaiting additional information from
8. Non-passenger AVs: Consider applicant
differences between AVs designed for DEPARTMENT OF TRANSPORTATION 2. Extensive public comment under review
delivery of goods and products that are 3. Application is technically complex and is
not intended to have a human operator Pipeline and Hazardous Materials of significant impact or precedent-setting
or potentially even human passengers. Safety Administration and requires extensive analysis
9. Aspects of AV technology that may 4. Staff review delayed by other priority
not be suitable or ready for guidelines. Hazardous Materials: Delayed issues or volume of special permit
For these areas, information would be Applications applications
useful on alternative approaches to AGENCY: Office of Hazardous Materials Meaning of Application Number
assure safety. Safety, Pipeline and Hazardous Suffixes
10. Identification of industry Materials Safety Administration
voluntary standards, best practices, etc., N—New application
(PHMSA), DOT. M—Modification request
related to automated vehicle operation. ACTION: List of application delayed more R—Renewal Request
11. Information AV’s may need to than 180 days. P—Party To Exemption Request
communicate to pedestrians and other
vehicles (manual or automated) just as SUMMARY: In accordance with the Issued in Washington, DC, on March 10,
a driver would. Consider situations such requirements of 49 U.S.C. 5117(c), 2016.
as pedestrians crossing a travel lane in PHMSA is publishing the following list Donald Burger,
a parking lot and how this of special permit applications that have Chief, General Approvals and Permits.
Reason for Estimated date
Application No. Applicant delay of completion
Modification to Special Permits
16412–M ........... Nantong CMC Tank Equipment Co. Ltd., Jiangsu, Province ................................................... 4 03–31–2016
15628–M ........... Chemours Company FC, LLC, Wilmington, DE ....................................................................... 4 03–31–2016
15610–M ........... TechKnowServ Corp., State College, PA ................................................................................. 4 03–31–2016
15537–M ........... Alaska Pacific Powder Company, Watkins, CO ....................................................................... 4 04–15–2016
7607–M ............. Thermo Fisher Scientific, Franklin, MA .................................................................................... 4 03–31–2016
16035–M ........... LCF Systems, Inc., Scottsdale, AZ .......................................................................................... 4 04–30–2016
14437–M ........... Columbiana Boiler Company (CBCo), LLC, Columbiana, OH ................................................. 4 02–15–2016
New Special Permit Applications
15767–N ........... Union Pacific Railroad Company, Omaha, NE ........................................................................ 3 02–29–2016
16001–N ........... VELTEK ASSOCIATES, INC., Malvern, PA ............................................................................. 3 03–31–2016
16477–N ........... Hydroid, Inc., Pocasset, MA ..................................................................................................... 4 03–15–2016
16495–N ........... TransRail Innovation, Inc., Calgary .......................................................................................... 4 03–31–2016
16524–N ........... Quantum Fuel Systems Technologies Worldwide, Inc., Lake Forest, CA ............................... 4 03–15–2016
16463–N ........... Salco Products, Lemont, IL ...................................................................................................... 3 03–31–2016
16571–N ........... Chevron USA Inc., San Ramon, CA ........................................................................................ 4 04–15–2016
16559–N ........... HTEC Hydrogen Technology & Energy Corporation, North Vancouver, BC; Canada ............ 4 04–30–2016
16560–N ........... LightSail Energy, Inc., Berkeley, CA ........................................................................................ 4 04–30–2016
Party to Special Permits Application
asabaliauskas on DSK3SPTVN1PROD with NOTICES
16279–P ........... AEG Environmental Products & Services, Inc.; Westminster, MD .......................................... 4 03–31–2016
[FR Doc. 2016–06055 Filed 3–17–16; 8:45 am]
BILLING CODE 4910–60–M
VerDate Sep<11>2014 19:50 Mar 17, 2016 Jkt 238001 PO 00000 Frm 00115 Fmt 4703 Sfmt 9990 E:\FR\FM\18MRN1.SGM 18MRN1](https://thefederalregister.org/doc/81_FR_14987/page/3.svg)
Document Created: 2018-02-02 15:14:16
Document Modified: 2018-02-02 15:14:16
| Category | Regulatory Information | |
| Collection | Federal Register | |
| sudoc Class | AE 2.7: GS 4.107: AE 2.106: | |
| Publisher | Office of the Federal Register, National Archives and Records Administration | |
| Section | Notices | |
| Action | Announcement of public meeting. | |
| Dates | NHTSA will hold the public meeting on April 8, 2016, in Washington, DC. The meeting will start at 9:00 a.m. and continue until 4:00 p.m., local time. Check-in (through security) will begin at 8 a.m. (Note: A second public meeting will be held on the West Coast (California), and details for that meeting will be announced in a separate Federal Register (FR) Notice.) | |
| Contact | If you have questions about the public meeting, please contact us at [email protected] | |
| FR Citation | 81 FR 14934 |
2025 Federal Register | Disclaimer | Privacy Policy
USC | CFR | eCFR