Posting travel times on dms webinar 042711

649 views

Published on

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…
.


Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
649
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Posting travel times on dms webinar 042711

  1. 1. Posting Travel Times on Dynamic Message Signs & 3rd Party Data… best practices & lessons learned<br />Welcome!<br />Wednesday, April 27, 2011 11:00a.m. – 12:30 p.m. (Eastern Time) <br />
  2. 2. Posting Travel Times on Dynamic Message Signs & 3rd Party Data… best practices & lessons learned<br />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. <br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  3. 3. What prompted this webinar?<br /><ul><li> The Idaho Transportation Department’s interest in </li></ul> posting travel time<br /><ul><li> FHWA facilitated a teleconference for ITD with other </li></ul> state DOTs to learn of their approaches<br /><ul><li> Mutual assessment by the State Transportation </li></ul> agencies involved and FHWA that this topic was of <br /> national interest and so deserved a webinar to share <br /> lessons learned & best practices.<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  4. 4. 2009 MUTCD Reference <br />Changeable Message Signs<br />Section 2L.02 Applications of Changeable Message Signs<br />G. Travel Time<br />We have three poll questions we would like you to respond to:<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  5. 5. Posting Travel Times on Dynamic Message Signs & 3rd Party Data… best practices & lessons learned<br />Moderator & Speaker Bios are available in the “Download Bios & Today’s Presentation Pod”<br />ModeratorBob KoeberleinMobility Services EngineerIdaho Transportation Department<br />We have three speakers today:<br />Special Guest Speakers<br />● Jennifer Portanova<br />State ITS Operations EngineerNorth Carolina Department of Transportation ---● Jeff GalasTraffic Systems Center ManagerIllinois Department of Transportation---● Richard DyeCHART Systems Administrator Maryland State Highway Administration---<br />Wednesday, April 27, 2011 11:00a.m. – 12:30 p.m. (Eastern Time) <br />
  6. 6. Posting Travel Times on Dynamic Message Signs & 3rd Party Data<br />… best practices & lessons learned<br />April 27, 2011<br />Jennifer Portanova, PE<br />North Carolina Department of Transportation<br />State ITS Operations Engineer<br />
  7. 7. POLICY<br /><ul><li>No formal policy
  8. 8. Guidelines
  9. 9. Time of day TT will be posted
  10. 10. How often TT will be updated
  11. 11. Priority level of message
  12. 12. Message Format</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  13. 13. LOCATION<br /><ul><li>Posting TT in urban & rural areas statewide
  14. 14. Pre-determined locations
  15. 15. Reoccurring congestion
  16. 16. Decision Point between two routes
  17. 17. Needs tweaking
  18. 18. Regional input on locations</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  19. 19. POSTING<br />HIGH<br /><ul><li>Automated and Manual Posting
  20. 20. Weekdays Peak Hours
  21. 21. 6 am to 9 am
  22. 22. 4 pm to 7 pm
  23. 23. Or if speeds drop below speed limit (automated)
  24. 24. Updated every:
  25. 25. 10 minutes (manual)
  26. 26. 1 minute (automated)
  27. 27. Low Message Priority</li></ul>LOW<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  28. 28. POSTING FORMAT<br /><ul><li>Short Segments (96 mph)
  29. 29. Range Vs. No Range</li></ul>VS<br />Current format<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  30. 30. EQUIPMENT<br />Not using portable devices<br /><ul><li>Permanent signs (DMS)
  31. 31. Discussed stationary
  32. 32. Challenges with older devices
  33. 33. Number of characters
  34. 34. Communication
  35. 35. Automation Software</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  36. 36. DATA SOURCE: Manual<br /><ul><li>Vehicle probe speed data
  37. 37. Webpage with TT
  38. 38. Capped at Speed Limit
  39. 39. Round up
  40. 40. Message updated by operator</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  41. 41. DATA SOURCE: Automated<br /><ul><li>Microwave speed sensors
  42. 42. Current software limits data source
  43. 43. Working on software for any source</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  44. 44. DATA RELIABILITY<br /><ul><li>3rd Party Microwave Sensor
  45. 45. Sensitivity
  46. 46. Maintenance
  47. 47. 3rd Party Vehicle Probe Data
  48. 48. Missing segments
  49. 49. Mountains
  50. 50. Source of data
  51. 51. Continues to improve</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  52. 52. WORK ZONES & VARIABLE SPEED LIMITS<br /><ul><li>Permanent devices
  53. 53. Have some TT in WZ
  54. 54. Not strategically posting for a WZ, yet…
  55. 55. Working on WZ application
  56. 56. Variable speed limits
  57. 57. Only in WZ
  58. 58. Not in effect during peak hours</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  59. 59. MAINTAINING ASSETS<br /><ul><li>Devices and data already existed
  60. 60. Funded operator positions to post
  61. 61. Webpage to make Manual TT easier
  62. 62. Future Investments
  63. 63. Upgrade DMS for automated TT
  64. 64. Strategic Development
  65. 65. SMARTlink RFP</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  66. 66. LESSONS LEARNED<br /><ul><li>Automated ideal – monitoring still required
  67. 67. Regional perspective important
  68. 68. Avoid ranges on small segments
  69. 69. Expect to make changes
  70. 70. Have a Champion</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  71. 71. Posting Travel Times on Dynamic Message Signs & 3rd Party Data<br />… best practices & lessons learned<br />Jeff Galas, Traffic Systems Center Manger<br />Illinois Department of Transportation<br />
  72. 72. Travel Times in the Chicago Area<br />Illinois Department of Transportation<br />District 1<br />Traffic Systems Center<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  73. 73. Network of over 2400 detectors – <br />168 centerline miles monitored<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  74. 74. Combination of Detection Methods:<br /><ul><li> Induction Loops
  75. 75. RTMS microwave detectors
  76. 76. Microloops (magnetometers)
  77. 77. Bluetooth capture</li></ul>Spaced approximately every 0.5 mile<br />Interfaced to the ATMS as <br />Volume and Occupancy (presence)<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  78. 78. 42 Expressway Dynamic Message Signs<br />14 Arterial DMS<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  79. 79. Combination of DMS Technologies<br /><ul><li> Flip Disk – Fiber optic enhanced</li></ul> 25 to 30 year old<br /><ul><li> LED Full matrix Walk-in NTCIP compliant</li></ul> More recent installations<br /><ul><li> LED Full matrix / Full Color</li></ul> Replacing the oldest of the old<br /> MUTCD Graphics capability<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  80. 80. Near Real Time Congestion and Travel Times<br /><ul><li> Available to the public for over 30 years
  81. 81. Distributed through local television and radio outlets
  82. 82. Broadcast on Highway Advisory Radio
  83. 83. Displayed on the LMIGA website
  84. 84. Displayed on Dynamic Message Signs</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  85. 85. Congestion messages displayed on DMS …. Daytime only<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  86. 86. Challenged to start displaying Travel Times<br /><ul><li> Use existing Travel Time algorithms
  87. 87. Determine and develop new Travel Time zones
  88. 88. Interface to sign controller
  89. 89. Monitor operation for accuracy</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  90. 90. Travel Time Calculation:<br />Each station is sending presence information in real time<br />20 second sample is stored<br />Speed is calculated using Volume and Occupancy:<br />Speed = 3600 (Volume) (average vehicle length)<br /> 52.8 (polling interval) (Occupancy)<br />Average vehicle length varies by lane (17 feet to 22 feet)<br />Data is normalized prior to calculation<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  91. 91. Travel Time Calculation:<br />Speed is used to calculate relative time:<br />Travel Time = Length of segment<br />Speed<br />Each segment is adjusted for actual spacing between detectors<br />Segment times are concatenated for longer zones<br />Zone travel times averaged over 5 minute period<br />before being published or displayed<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  92. 92. ATMS Vehicle Detection Station – Estimated Speed<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  93. 93. ....DMS Travel Times<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  94. 94. Guidelines for DMS Messages<br />Hierarchy of messages displayed:<br />1,2 Priority message (Crash, pavement failure, incident)<br /> ATMS incident<br /> Scheduled message (lane closures, planned events)<br />2 phase Congestion / Travel Times<br /> AMBER alert<br />Travel Times<br />8,9 Stored message (PSA ,seat belt, DUI, etc)<br />10 Previous ATMS travel times<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  95. 95. Messages refer to landmarks and destinations<br />DMS <br />Travel Time zones <br />do not exceed <br />10 miles<br />O’Hare Airport<br />Junction<br />Circle<br />159th street<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  96. 96. Desire (demand) for travel times<br /><ul><li> Public has become accustomed to travel times
  97. 97. Media focus on travel time info
  98. 98. When outages occur, calls come in
  99. 99. Requests for system expansion
  100. 100. Difficulties in construction zones
  101. 101. When the loops are removed
  102. 102. RTMS units
  103. 103. Bluetooth</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  104. 104. Construction Alternatives<br />“Bridge” Detection zones – short distances<br />Probe Vehicles<br /> Travel times manually entered as received<br />RTMS units<br /> conflict with construction staging<br /> re-calibration based on lane configuration<br />Bluetooth<br /> Fairly accurate alternative<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  105. 105. DMS Travel Times during Construction<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  106. 106. Investment in infrastructure<br />Initial installation<br /> Approximately $250,000 per sign <br /> Truss, Sign, power, communication<br />ATMS modification and software<br />Maintenance<br /> Under contract - $26,000 per month for system<br /> Additional cost for battery back-up sign - $1,000 / year<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  107. 107. Using the I-95 Corridor Coalition Vehicle Probe data to put Automated Travel Times on Dynamic Message Signs in Maryland<br />Richard R. Dye<br />CHART Systems Administrator<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  108. 108. <ul><li>As recently as December 2007, Travel Times on DMS was scheduled for FY 2012 due to lack of infrastructure to provide good data and the need to devote a major build entirely to this effort.
  109. 109. In the mean Time CHART was preparing the background logic in smaller builds (System Alerts R3B1, Scheduler and Event-based Notification R3B2) </li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  110. 110. <ul><li>That same month, the I-95 Corridor Coalition awarded a Travel Time contract and software development for automated messages on CHART signs was pushed forward to meet the challenge
  111. 111. Work was also begun on Engineering Guidelines for Implementing Travel Times On DMS in Maryland </li></ul>More Info, download Procedural Guidelines For Implementing Travel Time on DMS In CHART (PDF) at http://traffic.md.gov/readingroom/RR_ChartSWProgDocumenation.asp<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  112. 112. <ul><li>…but… developing software to implement a 3rd party interface that had been neither developed nor tested was risky (to say the least)
  113. 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. 114. … and the FHWA “map” was not going away</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  115. 115. Assumptions!<br /><ul><li>If the 3rd party data is good, we can move automated travel times on DMS up to a non-dedicated build if:
  116. 116. Routes in CHART will be built using links that we choose
  117. 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. 118. Travel Time will run during hours of day that we choose
  119. 119. This will allow us to avoid obvious trouble spots for probe-based systems (e.g. low volume of probes between 2am and 4am)</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  120. 120. Assumptions!<br /><ul><li>Travel times will be displayed in ranges, not exact times
  121. 121. The currently approved quality scores will be used to determine if a message is displayed
  122. 122. A smoothing algorithm will be added to the travel time data received from The 3rd party vendor
  123. 123. This should mitigate the severity of seriously outlying data points</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  124. 124. Assumptions!<br /><ul><li>If a maximum travel time threshold is received, the message will not be displayed and an alert will be set to the controlling Ops Center as well as notification to selected pager/email groups in the system
  125. 125. Travel times below a minimum will display travel time as if the speed limit were traveled</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  126. 126. Timeline<br /><ul><li>CHART Release 3, Build 3 was deployed in December 2009 and was composed of:
  127. 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. 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. 129. External Event Import including External Event Alert
  130. 130. External DMS and TSS import from RITIS.
  131. 131. Capability to manage geographical area definitions
  132. 132. Direct TCP/IP communication for DMS and TSS</li></ul>More Info, download CHART R3B3 Detailed Design.pdf at http://traffic.md.gov/readingroom/RR_ChartSWProgDocumenation.asp<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  133. 133. How Did It Turn Out?<br /><ul><li>Privileged operators can create travel routes</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  134. 134. How Did It Turn Out?<br /><ul><li>For maximum flexibility, DMS Message Templates are used to define the format and layout of messages used to show travel times and/or toll rates on DMSs. Message templates target DMSs of a specific size (rows /columns) to allow layout features such as column data and to ensure messages created with the template match the layout specified by the template designer.
  135. 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.</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  136. 136. How Did It Turn Out?<br /><ul><li>Any Operator can see
  137. 137. The name and length of the route
  138. 138. The current travel time for the route
  139. 139. The current travel time trend
  140. 140. The current average speed on the route
  141. 141. The current toll rate for the route
  142. 142. The devices using the travel route
  143. 143. The roadway route(s) that are included in the travel route.
  144. 144. The roadway direction(s) that are included in the travel route.
  145. 145. The Counties that are included in the travel route </li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  146. 146. <ul><li>Travel Time started on I-95 between the beltways in January 2010
  147. 147. Travel Times run 5am to 9pm weekdays</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  148. 148. <ul><li>Travel Time expanded to both beltways in March 2010</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  149. 149. August 2010 – Senior Management Weighs in <br />- All signs displaying travel time need to also display the distance to the destination(s).<br /> <br />- The distance as displayed on single destination signs to read XX MINUTES on line 3 if there is room. XX MIN otherwise.<br /> <br />- For multiple destination signs, the sign should display XX MI between the destination and the travel time.<br /> <br />- In a few cases, the destination description is too long for XX MI to fit on the same line.  In these cases the message should be revised to report travel time to a single destination. <br /><ul><li>Travel Time expanded westward and to the eastern shore in Late 2010</li></ul>Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  150. 150. What Can the Operators See?<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  151. 151. What Makes up a Route?<br />Links that we receive from the 3rd party vendor and build into a Route<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  152. 152. And general settings (max displayable time, min travel time, who to alert when things go wrong – remember the assumptions?)<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  153. 153. …and a Dynamic Message Sign!<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  154. 154. What Does the Public See?<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  155. 155. What if Travel Time is Exceeded?<br />What Does the Operator See?<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  156. 156. What if Data Quality is too Low?<br />What Does the Operator See?<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  157. 157. What if there is a Conflict?<br />What Does the Operator See?<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  158. 158. Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  159. 159. What Does the Public See?<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  160. 160. Experience So Far<br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />
  161. 161. Any Questions for our Speakers?<br />Thank You!<br />Ray Murphy, ITS Specialist<br />Office of Technical Services<br />ray.murphy@dot.gov, 708-215-1301<br />FHWA Operations<br />http://ops.fhwa.dot.gov/<br />FHWA Real-Time System Management Information Program<br />SAFETEA-LU, Subtitle B, §1201 <br />Provisions of the Rule – 23 CFR Part 511<br />Bob Rupert, FHWA, 202-366-2194, Robert.Rupert@dot.gov <br />http://ops.fhwa.dot.gov/1201/ <br />Posting Travel Times on Dynamic Message Signs & 3rd Party Data Webinar<br />

×