FHWA Hardware Identification Methods Project Update
FHWA Hardware Identification Methods Project Update Charles Stevens, P.E., PTOE
Idaho Department of Transportation February 16, 2017
Project Overview • FAST Act Requirement – Section 1429: Techniques to identify and document roadside safety hardware devices.
• Project Goals – Determine available hardware ID methods. – Provide analysis of available methods. – Evaluate for ability to convey information, withstand roadside conditions, and connect to existing systems.
Project Overview • Primary Tasks – Create and utilize a Technical Working Group (TWG) – Hardware ID Study • • • • •
Literature Review Technology Owners & Manufacturers Review Department of Transportation (DOT) Use DOT Case Studies (3) Evaluation of ID methods
– Report to Congress
Identification Methods • Barcodes • Radio Frequency ID (RFID) • Serial Numbers
Technical Working Group • Expectations from TWG – Confirmation of appropriate search methods. – Additional sources of information. – Comments/suggestion on discovered hardware ID methods. – Comments/suggestions on evaluation methodology and outcomes.
Literature Review • Hardware ID Methods • Cross Cutting Industry Uses • Connectivity – Data Origin and Creation – Speed and Connection – Software Requirements
• Durability – Weather – Environment – Maintenance
Hardware Manufacturers and Technology Owners • Technology Providers – Interviews – Demonstrations
• Manufacturer Specifications – Data Dictionary
Connectivity Data Origin and Creation Speed and Connection Software Requirements Durability Weather Environment Maintenance
Departments of Transportation • Documenting Examples – Using Methods – What were the applications?
• Case Studies – Michigan (QR Codes) – Idaho – Utah
Evaluating the Methods • Evaluation Protocol – Convey Information – Withstand Conditions – Connect to Existing Systems – Additional Considerations
Where are we now?
Next Steps • Finalize Summary Report (March/April 2017) • Prepare Report to Congress (December 2017)
Contact Information Charles R. Stevens Jr., P.E., PTOE Texas A&M Transportation Institute e‐mail: c‐[email protected] Phone: (713) 613‐9230 Tomás E. Lindheimer, Ph.D. Texas A&M Transportation Institute e‐mail: t‐[email protected] Phone: (979) 458‐2587
Brian J. Fouch, P.E. Federal Highway Administration Office of Safety e‐mail: [email protected] Phone: (202) 366‐9469 Cathy Satterfield, P.E. Federal Highway Administration Office of Safety e‐mail: [email protected] Phone: (708) 283‐3552
Things to Think About • Deployment – System vs. Component – Information Security – Placement and Vandalism
• How to use for ISPE
Idaho Department of Transportation February 16, 2017
Project Overview • FAST Act Requirement – Section 1429: Techniques to identify and document roadside safety hardware devices.
• Project Goals – Determine available hardware ID methods. – Provide analysis of available methods. – Evaluate for ability to convey information, withstand roadside conditions, and connect to existing systems.
Project Overview • Primary Tasks – Create and utilize a Technical Working Group (TWG) – Hardware ID Study • • • • •
Literature Review Technology Owners & Manufacturers Review Department of Transportation (DOT) Use DOT Case Studies (3) Evaluation of ID methods
– Report to Congress
Identification Methods • Barcodes • Radio Frequency ID (RFID) • Serial Numbers
Technical Working Group • Expectations from TWG – Confirmation of appropriate search methods. – Additional sources of information. – Comments/suggestion on discovered hardware ID methods. – Comments/suggestions on evaluation methodology and outcomes.
Literature Review • Hardware ID Methods • Cross Cutting Industry Uses • Connectivity – Data Origin and Creation – Speed and Connection – Software Requirements
• Durability – Weather – Environment – Maintenance
Hardware Manufacturers and Technology Owners • Technology Providers – Interviews – Demonstrations
• Manufacturer Specifications – Data Dictionary
Connectivity Data Origin and Creation Speed and Connection Software Requirements Durability Weather Environment Maintenance
Departments of Transportation • Documenting Examples – Using Methods – What were the applications?
• Case Studies – Michigan (QR Codes) – Idaho – Utah
Evaluating the Methods • Evaluation Protocol – Convey Information – Withstand Conditions – Connect to Existing Systems – Additional Considerations
Where are we now?
Next Steps • Finalize Summary Report (March/April 2017) • Prepare Report to Congress (December 2017)
Contact Information Charles R. Stevens Jr., P.E., PTOE Texas A&M Transportation Institute e‐mail: c‐[email protected] Phone: (713) 613‐9230 Tomás E. Lindheimer, Ph.D. Texas A&M Transportation Institute e‐mail: t‐[email protected] Phone: (979) 458‐2587
Brian J. Fouch, P.E. Federal Highway Administration Office of Safety e‐mail: [email protected] Phone: (202) 366‐9469 Cathy Satterfield, P.E. Federal Highway Administration Office of Safety e‐mail: [email protected] Phone: (708) 283‐3552
Things to Think About • Deployment – System vs. Component – Information Security – Placement and Vandalism
• How to use for ISPE
