The following Transportation agencies, Idaho Transportation Department (ITD), North Carolina Department of Transportation (NCDOT), Illinois Department of Transportation (IDOT) and Maryland State Highway Administration (M-SHA) will share lessons learned and best practices regarding Travel Time (TT) posting on Dynamic Message Signs (DMS) and the use of third party data services. The webinar covered DMS Operations and: • POLICIES… • POSTINGS… • UPDATES… • WORK ZONES… • VARIABLE SPEED LIMITS… • PARTNERSHIPS: with Law Enforcement, TIM, etc… • DATA RELIABILITY: data testing/history/accuracy… • PUBLIC OUTREACH/MEDIA: customer feedback… • MAINTAINING ASSETS: investment, financial aspects… • EQUIPMENT: portable & fixed, characters, placement, detection… .

1. Posting Travel Times on Dynamic Message Signs & 3rd Party Data… best practices & lessons learned Welcome! Wednesday, April 27, 2011 11:00a.m. – 12:30 p.m. (Eastern Time)

2. Posting Travel Times on Dynamic Message Signs & 3rd Party Data… best practices & lessons learned Disclaimer: Today’s webinar is being delivered at the request of several State Transportation agencies. FHWA does not endorse any of the 3rd Party Data Service providers/vendors discussed in the following presentations. Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

4. 2009 MUTCD Reference Changeable Message Signs Section 2L.02 Applications of Changeable Message Signs G. Travel Time We have three poll questions we would like you to respond to: Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

5. Posting Travel Times on Dynamic Message Signs & 3rd Party Data… best practices & lessons learned Moderator & Speaker Bios are available in the “Download Bios & Today’s Presentation Pod” ModeratorBob KoeberleinMobility Services EngineerIdaho Transportation Department We have three speakers today: Special Guest Speakers ● Jennifer Portanova State ITS Operations EngineerNorth Carolina Department of Transportation ---● Jeff GalasTraffic Systems Center ManagerIllinois Department of Transportation---● Richard DyeCHART Systems Administrator Maryland State Highway Administration--- Wednesday, April 27, 2011 11:00a.m. – 12:30 p.m. (Eastern Time)

6. Posting Travel Times on Dynamic Message Signs & 3rd Party Data … best practices & lessons learned April 27, 2011 Jennifer Portanova, PE North Carolina Department of Transportation State ITS Operations Engineer

8. Guidelines

9. Time of day TT will be posted

10. How often TT will be updated

11. Priority level of message

12. Message FormatPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

14. Pre-determined locations

15. Reoccurring congestion

16. Decision Point between two routes

17. Needs tweaking

18. Regional input on locationsPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

20. Weekdays Peak Hours

21. 6 am to 9 am

22. 4 pm to 7 pm

23. Or if speeds drop below speed limit (automated)

24. Updated every:

25. 10 minutes (manual)

26. 1 minute (automated)

27. Low Message PriorityLOW Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

29. Range Vs. No RangeVS Current format Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

31. Discussed stationary

32. Challenges with older devices

33. Number of characters

34. Communication

35. Automation SoftwarePosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

37. Webpage with TT

38. Capped at Speed Limit

39. Round up

40. Message updated by operatorPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

42. Current software limits data source

43. Working on software for any sourcePosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

45. Sensitivity

46. Maintenance

47. 3rd Party Vehicle Probe Data

48. Missing segments

49. Mountains

50. Source of data

51. Continues to improvePosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

53. Have some TT in WZ

54. Not strategically posting for a WZ, yet…

55. Working on WZ application

56. Variable speed limits

57. Only in WZ

58. Not in effect during peak hoursPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

60. Funded operator positions to post

61. Webpage to make Manual TT easier

62. Future Investments

63. Upgrade DMS for automated TT

64. Strategic Development

65. SMARTlink RFPPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

67. Regional perspective important

68. Avoid ranges on small segments

69. Expect to make changes

70. Have a ChampionPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

71. Posting Travel Times on Dynamic Message Signs & 3rd Party Data … best practices & lessons learned Jeff Galas, Traffic Systems Center Manger Illinois Department of Transportation

72. Travel Times in the Chicago Area Illinois Department of Transportation District 1 Traffic Systems Center Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

73. Network of over 2400 detectors – 168 centerline miles monitored Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

75. RTMS microwave detectors

76. Microloops (magnetometers)

77. Bluetooth captureSpaced approximately every 0.5 mile Interfaced to the ATMS as Volume and Occupancy (presence) Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

78. 42 Expressway Dynamic Message Signs 14 Arterial DMS Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

81. Distributed through local television and radio outlets

82. Broadcast on Highway Advisory Radio

83. Displayed on the LMIGA website

84. Displayed on Dynamic Message SignsPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

85. Congestion messages displayed on DMS …. Daytime only Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

87. Determine and develop new Travel Time zones

88. Interface to sign controller

89. Monitor operation for accuracyPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

90. Travel Time Calculation: Each station is sending presence information in real time 20 second sample is stored Speed is calculated using Volume and Occupancy: Speed = 3600 (Volume) (average vehicle length) 52.8 (polling interval) (Occupancy) Average vehicle length varies by lane (17 feet to 22 feet) Data is normalized prior to calculation Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

91. Travel Time Calculation: Speed is used to calculate relative time: Travel Time = Length of segment Speed Each segment is adjusted for actual spacing between detectors Segment times are concatenated for longer zones Zone travel times averaged over 5 minute period before being published or displayed Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

92. ATMS Vehicle Detection Station – Estimated Speed Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

93. ....DMS Travel Times Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

94. Guidelines for DMS Messages Hierarchy of messages displayed: 1,2 Priority message (Crash, pavement failure, incident) ATMS incident Scheduled message (lane closures, planned events) 2 phase Congestion / Travel Times AMBER alert Travel Times 8,9 Stored message (PSA ,seat belt, DUI, etc) 10 Previous ATMS travel times Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

95. Messages refer to landmarks and destinations DMS Travel Time zones do not exceed 10 miles O’Hare Airport Junction Circle 159th street Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

97. Media focus on travel time info

98. When outages occur, calls come in

99. Requests for system expansion

100. Difficulties in construction zones

101. When the loops are removed

102. RTMS units

103. BluetoothPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

104. Construction Alternatives “Bridge” Detection zones – short distances Probe Vehicles Travel times manually entered as received RTMS units conflict with construction staging re-calibration based on lane configuration Bluetooth Fairly accurate alternative Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

105. DMS Travel Times during Construction Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

106. Investment in infrastructure Initial installation Approximately $250,000 per sign Truss, Sign, power, communication ATMS modification and software Maintenance Under contract - $26,000 per month for system Additional cost for battery back-up sign - $1,000 / year Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

107. Using the I-95 Corridor Coalition Vehicle Probe data to put Automated Travel Times on Dynamic Message Signs in Maryland Richard R. Dye CHART Systems Administrator Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

109. In the mean Time CHART was preparing the background logic in smaller builds (System Alerts R3B1, Scheduler and Event-based Notification R3B2) Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

111. Work was also begun on Engineering Guidelines for Implementing Travel Times On DMS in Maryland More Info, download Procedural Guidelines For Implementing Travel Time on DMS In CHART (PDF) at http://traffic.md.gov/readingroom/RR_ChartSWProgDocumenation.asp Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

113. This is the 1st time EVER that messages will be put on a CHART field device without the direct approval or even overt knowledge of an operator. How do we manage our risk?

114. … and the FHWA “map” was not going awayPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

116. Routes in CHART will be built using links that we choose

117. This will allow us to avoid obvious trouble spots for probe-based systems (e.g. welcome station on I-95 where long runs parallel to the highway may confuse the data)

118. Travel Time will run during hours of day that we choose

119. This will allow us to avoid obvious trouble spots for probe-based systems (e.g. low volume of probes between 2am and 4am)Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

121. The currently approved quality scores will be used to determine if a message is displayed

122. A smoothing algorithm will be added to the travel time data received from The 3rd party vendor

123. This should mitigate the severity of seriously outlying data pointsPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

125. Travel times below a minimum will display travel time as if the speed limit were traveledPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

127. Traveler Information Messages, including Travel Times and Toll Rates obtained via an external connection to the two different 3rd party vendors system and Vector system.

128. Device Location fields to CHART devices, including DMS, TSS (Detectors), HAR, SHAZAM, and Cameras allowing the system to show devices close to traffic events to aid in event response.

129. External Event Import including External Event Alert

130. External DMS and TSS import from RITIS.

131. Capability to manage geographical area definitions

132. Direct TCP/IP communication for DMS and TSSMore Info, download CHART R3B3 Detailed Design.pdf at http://traffic.md.gov/readingroom/RR_ChartSWProgDocumenation.asp Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

135. Templates may contain both text and data fields. Data fields will be replaced with actual data from one or more Travel Routes when a template is used for a DMS message.Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

137. The name and length of the route

138. The current travel time for the route

139. The current travel time trend

140. The current average speed on the route

141. The current toll rate for the route

142. The devices using the travel route

143. The roadway route(s) that are included in the travel route.

144. The roadway direction(s) that are included in the travel route.

145. The Counties that are included in the travel route Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

147. Travel Times run 5am to 9pm weekdaysPosting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

150. What Can the Operators See? Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

151. What Makes up a Route? Links that we receive from the 3rd party vendor and build into a Route Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

152. And general settings (max displayable time, min travel time, who to alert when things go wrong – remember the assumptions?) Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

153. …and a Dynamic Message Sign! Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

154. What Does the Public See? Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

155. What if Travel Time is Exceeded? What Does the Operator See? Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

156. What if Data Quality is too Low? What Does the Operator See? Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

157. What if there is a Conflict? What Does the Operator See? Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

158. Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

159. What Does the Public See? Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

160. Experience So Far Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar

161. Any Questions for our Speakers? Thank You! Ray Murphy, ITS Specialist Office of Technical Services ray.murphy@dot.gov, 708-215-1301 FHWA Operations http://ops.fhwa.dot.gov/ FHWA Real-Time System Management Information Program SAFETEA-LU, Subtitle B, §1201 Provisions of the Rule – 23 CFR Part 511 Bob Rupert, FHWA, 202-366-2194, Robert.Rupert@dot.gov http://ops.fhwa.dot.gov/1201/ Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar