1. Travel Times on Dynamic Message Signs Brandy Meehan Transportation Information Management Team Federal Highway Administration September 28, 2005

2. 2 Dynamic Message Signs Valuable pieces of “real estate” Nationwide – 4,500 2,805 permanent freeway signs for 97 agencies 759 portable signs for 85 agencies 937 signs on streets/arterials for 84 agencies Approximate investment nationally: Over $330,000,000 in sign hardware alone From the 2002 Deployment Tracking Database

3. 3 A Resource Underutilized Signs are often blank or Provide vague information “Congestion Ahead”

4. 4 FHWA Recommended Practice for DMS July 16, 2004 Memorandum www.ops.fhwa.dot.gov/travelinfo/resources/cms_rept/ travtime.htm “Dark” DMS are not being fully utilized Travel time messages should be the default information

5. 5 FHWA Recommended Practice for DMS (2) Full network coverage not needed in order to begin providing travel times No new DMS should be installed on heavily traveled corridors unless the capability to display travel times exists

6. 6 Workshop Details March 16-17, 2005 Georgia DOT’s NaviGAtor TMC Facilitated by ITS America

7. 7 Participants Virginia DOT Caltrans Utah DOT Los Angeles DOT Wash. State DOT Georgia DOT* TxDOT* Wisconsin DOT* NC DOT MTC Florida DOT NYDOT FHWA Resource Center PBS&J ITSA A total of 21 representatives from: *Speakers

8. 8 Issues to Consider (1/4) Convincing management (or staff) to post messages Overwhelmingly positive response in other cities Travel time accuracy 90% is ideal; no less than 80% accuracy Give a time range of 2 to 3 minutes Message construction Sign dependent No qualifiers Destinations for each sign should remain the same

9. 9 Selecting destinations and segment lengths Data dependent Select popular destinations O&M Costs and TMC staff Maintenance costs folded into other programs Travel time messages automatically posted TMC staff monitors system when there are problems Issues to Consider (2/4)

10. 10 Travel time algorithms Most are very simple Software upgrades Make sure that the DOT owns the software Get software from other states Reaching both commuters and non-locals Posting distances and travel times Issues to Consider (3/4)

11. 11 Prioritizing DMS messages Travel times should be the default Public outreach and public reaction Coordinate with the media Develop and execute and outreach plan Public response very positive  90% favorable in Seattle  85% favorable in Salt Lake City Issues to Consider (4/4)

12. 12 What is FHWA doing? 4 travel time case studies  http://www.ops.fhwa.dot.gov/travelinfo Article in the September ITE Journal Workshop materials on ITSA website  http://www.itsa.org/dms.html

13. 13 Travel Time Status Alaska Hawaii Puerto Rico D.C. = Provide Travel Times = Plans to Provide Travel Times

14. 14 For More Information Brandy Meehan, FHWA 202-366-6598 Brandy.Meehan@fhwa.dot.gov www.itsa.org/dms.html www.ops.fhwa.dot.gov/travelinfo