U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000
Federal Highway Administration Research and Technology
Coordinating, Developing, and Delivering Highway Transportation Innovations
EAR REPORT |
This report is an archived publication and may contain dated technical, contact, and link information |
|
![]() |
Publication Number: FHWA-HRT-17-047 Date: September 2017 |
Publication Number: FHWA-HRT-17-047 Date: September 2017 |
Research Product to be Assessed: A software program to predict driver and autonomous vehicle response to different combinations of visual guidance—such as centerlines, edge lines, delineators, and raised pavement markers—to navigate curves in the roadway. |
||
Technology “As Implemented” (TRL 9): An advisory software-based tool that helps designers specify the parameters of a new roadway. |
||
Level |
Operating Environment |
Technology to be Assessed |
TRL |
Laboratory Environment: The PC on which the software was developed, operated by one of the developers. |
Components: Algorithms describing the visibility of certain marking types under design conditions, software-based implementation of those algorithms, subroutines for the presentation of the material and acceptance of user input, installation packages, and any instructions. |
TRL |
Relevant Environment: A PC used by a staff member not on the development team. |
Prototype: The software absent some functionality and without adequate documentation; the “alpha” or “beta” version. |
TRL |
Operational Environment: A PC usable by any roadway engineer with no experience in roadway design software. |
Technology: The software, including installation packages and user manual. |
Project Web site: |
http://www.fhwa.dot.gov/advancedresearch/pubs/seedarkear.cfm. |
Research Product to be Assessed: A Bluetooth-based tool that accurately measures travel time and arterial or freeway traffic. |
||
Technology “As Implemented” (TRL 9): A hardware or software system that provides travel-time estimates to travelers and traffic management centers. |
||
Level |
Operating Environment |
Technology to be Assessed |
TRL |
Laboratory Environment: A bench test for individual Bluetooth sensors or a small network of sensors. The software developer or someone else knowledgeable about its operation conducts the software testing. |
Components: Bluetooth sensors, installation hardware, data transmission, analysis, storage hardware or software, and user interface software. |
TRL |
Relevant Environment: A pilot test of a small network of Bluetooth traffic sensors in a parking lot generating data that, when processed, produces travel-time estimates. The software might be poorly documented and usable only by knowledgeable staff. |
Prototype: A complete system—with all necessary parts in place—but with nonweather-resistant sensor housing and functional, but flawed, software. |
TRL |
Operational Environment: The physical environment in which the fully functional Bluetooth sensors will operate (e.g., 2- to 6-lane roads in any U.S. metropolitan area). The software environment in which sensor data is processed and transmitted (e.g., wireless transmission to PCs for data processing and distribution) to the user (i.e., Metropolitan Planning Organization staff or the traveling public). |
Technology: A system composed of Bluetooth sensors, data transmission and storage equipment, software to convert the data into travel-time estimates and present them to users, and any necessary users’ guides. |
Project Web site: |
http://www.sbir.gov/content/anonymous-traffic-probes-travel-time-and-o-d-using-bluetooth-ids-0. |