U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000


Skip to content
Facebook iconYouTube iconTwitter iconFlickr iconLinkedInInstagram

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
Back to Publication List        
Publication Number:  FHWA-HRT-17-047    Date:  September 2017
Publication Number: FHWA-HRT-17-047
Date: September 2017

 

Appendix E. Example Projects and Associated Technology Readiness Levels

Table 8. Example 1. Innovative bridge design and rapid renewal: design tool kit.

Research Product to be Assessed: A “guidebook” for designing, constructing, and reusing bridge systems that address rapid renewal needs. Includes detailed plans for light, simple bridges that are easier to design, fabricate, transport, and erect than traditional bridges. Features concepts for innovative foundation systems, sub- and super-structure systems, subsystems, and components.

Technology “As Implemented” (TRL 9): A printed or software guidebook that describes recommended best practices for accelerated bridge construction and installation.

Level

Operating Environment

Technology to be Assessed

TRL
2–5

Laboratory Environment: A simulation or small-scale project. The user likely would be a member of the guidebook development team.

Components: The translation of the case studies into the guidance provided by the guidebook.

TRL
6

Relevant Environment: A single full-scale construction project on a controlled site, with project managers familiar with the guidebook and in contact with the development team.

Prototype: Case studies of bridge designs or aspects of design technique, and the logical organization and presentation of that knowledge base.

TRL
7–9

Operational Environment: The application of the guidebook to a physical project: a span of 100 to 400 ft, in nonwinter weather, in rural and urbanized areas throughout the United States, regardless of development density or traffic density. The user might be a state Department of Transportation engineer with bridge design experience overseeing the construction and installation of a bridge.

Technology: The complete guidebook and any ancillary material needed for its use.

Project Web site:

http://www.trb.org/Main/Blurbs/168046.aspx.

Table 9. Example 2. Increased understanding of driver visibility requirements.

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
2–5

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
6

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
7–9

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.

Table 10. Example 3. Anonymous traffic probes for travel time and origin-destination using Bluetooth IDs.

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
2–5

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
6

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
7–9

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.

 

 

 

Federal Highway Administration | 1200 New Jersey Avenue, SE | Washington, DC 20590 | 202-366-4000
Turner-Fairbank Highway Research Center | 6300 Georgetown Pike | McLean, VA | 22101