MnDOT TSMO Implementation Planning TSMO Objective Profiles 8/15/18 DRAFT

Transcription

1 MnDOT TSMO Implementation Planning TSMO Objective Profiles 8/15/18 DRAFT The MnDOT TSMO Program Planning Support Project has developed an overall MnDOT TSMO Strategic Plan outlining key goals and identifying 15 TSMO s to support these goals. Each of the 15 TSMO s are directly related to one or more of MnDOT s strategic operating goals, as defined in the MnDOT 5-Year Strategic Operating Plan (SOP) for In the next phase of the project, a TSMO Implementation Plan will be developed describing a prioritized list of TSMO strategies to be considered in each MnDOT District, along key corridors, and through statewide functional areas (e.g. road weather management, traveler information, and safety). This document provides a compilation of profiles describing all 15 TMSO s. These Objective Profiles include conditions best addressed by each, examples of key TSMO strategies to accomplish each, examples of current MnDOT related to each, likely impacts of accomplishing these s, and data and information resources to support consideration of each. This document is intended to help TSMO stakeholders (e.g. Districts and functional areas) identify those TSMO s that are most appropriate for their area as a first step towards eventually identifying the specific strategy ideas that they would like to propose for inclusion in the TSMO Implementation Plan. Below is a summary of the TSMO goals and s, per the MnDOT TSMO Strategic Plan. Following the list of goals and s are the 15 Objective Profiles. TSMO Goal: Improve Reliability, Mobility, and Efficiency Maximize existing capacity and reduce recurring (bottlenecks) and non-recurring (work zones, weather, incidents, special events) congestion. Objectives to support this goal: 1. Reduce the frequency of congestion or slowed traffic on the freeways and arterials in urbanized areas throughout Minnesota 2. Increase availability of information about travel times to drivers 3. Reduce the impacts of snow and ice on mobility 4. Reduce incident response and clearance times in the Twin Cities and Greater Minnesota 5. Increase pre-trip and en-route traveler awareness of incidents and alternate options in both the Twin Cities and Greater Minnesota 6. Reduce delays associated with construction 7. Reduce the period of time traffic is congested or delayed due to maintenance and reactive work zone TSMO Goal: Increase Safety Reduce the frequency, severity (fatalities and injuries) and clearance times of crashes. Objectives to support this goal: 8. Reduce the crashes related to congestion in Minnesota urbanized areas 9. Reduce the frequency of secondary crashes and crashes related to work zones 10. Reduce responder crash exposure 11. Reduce the frequency of single vehicle roadway departures Page 1 of 30

2 12. Reduce the frequency of crashes at signalized and unsignalized intersections 13. Reduce the frequency of crashes related to road weather conditions (e.g. snow, ice, fog, etc.) TSMO Goal: Carefully and Responsibly Manage Transportation Operations Assets Proactively and cost-effectively operate, maintain, upgrade, and manage the assets required for effective operations (staff, data, equipment). Objectives to support this goal: 14. Understand and appropriately fund the life-cycle costs of operations, managing, and maintaining the assets needed for operations 15. Acquire, secure, and retain the data needed for MnDOT to effectively perform operations, performance management and planning Page 2 of 30

3 Improve Reliability, Mobility, and Efficiency Objective 1: Reduce the frequency of congestion or slowed traffic on the freeways and arterials in urbanized areas throughout Minnesota Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT The frequency of recurring congestion in Minnesota s urbanized areas can be reduced through continued and expanded use of TSMO strategies that are already being utilized by MnDOT. As new and improved technologies to measure and manage congestion become available, these technologies will help MnDOT better understand congestion trends and apply targeted approaches to reduce congestion and slowed traffic. This TSMO is most appropriate to locations with the following conditions: Locations that experience recurring congestion that slows traffic for approximately 30 minutes or longer at least three days per week; or Travel patterns such that non-recurring events (e.g. incidents, special events) in and around Minnesota urbanized areas create extensive delays that disrupt normal traffic flows an average of two or more times per month. Freeway Management Arterial Management Centrally monitored traffic signal systems Automated Traffic Signal Performance Measures (ATSPM) Integrated Corridor Management Connected and Autonomous Vehicles Statewide: Traveler Information On-road DMS, 511 website, 511 mobile app, 511 phone system Twin Cities: RTMC (Twin Cities) and Supporting infrastructure: traffic cameras, traffic detectors Over 400 Ramp Meters in the Twin Cities Congestion Pricing / MnPASS - Twin Cities (I-394, I-35W, I35-E) Managed Lanes and Congestion Pricing (MnPASS) along several Twin Cities freeways; Centrally monitored traffic signal systems allow real-time signal adjustment to maximize throughput and minimize delays. Cameras in the Twin Cities allow remote monitoring of delays to support the implementation of signal timing changes. Greater Minnesota: Page 3 of 30

4 The frequency of recurring congestion in Minnesota s urbanized areas can be reduced through continued and expanded use of TSMO strategies that are already being utilized by MnDOT. As new and improved technologies to measure and manage congestion become available, these technologies will help MnDOT better understand congestion trends and apply targeted approaches to reduce congestion and slowed traffic. Centrally monitored traffic signal systems in Rochester, Duluth, Mankato, Moorhead, and St. Cloud allow real-time signal adjustment to maximize throughput and minimize delays. Cameras in Duluth, Rochester, and Moorhead allow remote monitoring of delays to support the implementation of signal timing changes. Freeway management in some urbanized areas (e.g. Duluth, Rochester) Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Increased reliability of travel times (reduced variations of travel times) Reduced travel times Reduced miles of directional congestion Reduced number of hours of daily congestion MnDOT 2017 Congestion Report (Twin Cities) Miles of congestion Duration of congestion MnDOT Data Tools (Twin Cities) MnDOT PeMS (Twin Cities) National Performance Management Research Data Set (NPMRDS) - NHS MnDOT Probe Data - Statewide, NHS and many local roads Page 4 of 30

5 Improve Reliability, Mobility, and Efficiency Objective 2: Increase availability of information about travel times to drivers Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Travelers that are informed of the current or predicted travel times along their planned route (and ideally alternate routes) are more likely to adjust their trips to maintain reliable travel times by altering departure times, travel routes, or modes. Within this, TSMO strategies will be implemented to increase travelers knowledge of travel times to enable informed trip planning, both pre-trip and en-route. This TSMO is most appropriate to locations with the following conditions: Urbanized areas where recurring or non-recurring events typically impact traffic on at least a somewhat regular basis (i.e. at least a minute increases in local drive times as compared to normal conditions occurs on average two or more times per week) and where alternate routes are available; and Rural areas where locally occurring events or seasonal traffic (e.g. weekend tourism, commercial vehicle, special events) regularly impact travel times causing delays to locals and/or visitors. These may not be every day, but still may be regularly occurring (e.g. weekly, seasonal, or holiday based). Traveler Information with specific reports of travel times along primary and alternate routes Data Management Integrated Corridor Management Statewide: MnDOT s traveler information website (511mn.org) contains colored road indications of speeds for most highways within Minnesota (excluding local roads). Twin Cities: MnDOT calculates travel times using permanent detection in the Twin Cities and disseminates travel times on roadside DMS and on the 511mn.org website during peak periods. Information is also shared with 3 rd party data providers; and MnDOT has tested temporary travel time measurements (either using temporary roadside readers or 3 rd party data) coupled with local disseminations with success. These have typically accompanied long-term road work with viable alternatives. Increased reliability of travel times (reduced variations of travel times) Page 5 of 30

6 Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Travelers that are informed of the current or predicted travel times along their planned route (and ideally alternate routes) are more likely to adjust their trips to maintain reliable travel times by altering departure times, travel routes, or modes. Within this, TSMO strategies will be implemented to increase travelers knowledge of travel times to enable informed trip planning, both pre-trip and en-route. MnDOT 2017 Congestion Report (Twin Cities) Miles of congestion Duration of congestion MnDOT Data Tools (Twin Cities) MnDOT PeMS (Twin Cities) National Performance Management Research Data Set (NPMRDS) - NHS MnDOT Probe Data - Statewide, NHS and many local roads Incident Reports Local knowledge of locations of recurring congestion Local knowledge of special events that cause congestion Page 6 of 30

7 Improve Reliability, Mobility, and Efficiency Objective 3: Reduce the impacts of snow and ice on mobility Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas The impacts of winter weather events (i.e. snow and ice) on traveler mobility in Minnesota are widespread, extending to commuters in urbanized areas, as well as to commercial and recreational travelers in rural areas. Within this, TSMO strategies will be implemented to help maintain reliable travel times during snow and ice events. This TSMO is appropriate statewide as winter weather has potential to impact reliability in all areas of the state. Specific approaches to accomplish this are most appropriate to urbanized areas, where winter weather events create substantial delays, especially for peak traffic periods or rural corridors where alternate routes are minimal. Road Weather Management Traveler Information Connected an Automated Vehicles Statewide: RWIS sites that provide weather and pavement data to assist with maintenance decisions Use of MDSS to assess road weather conditions and recommend surface treatments MnDOT s traveler information website (511mn.org) contains driving condition reports and indications of speeds for most highways within Minnesota (excluding local roads). New features on 511 website and mobile app, such plow-mounted camera images showing real-time pavement conditions Implementation of Pathfinder, whereby MnDOT coordinates with partners (e.g. National Weather Service) to plan for weather events and apply consistent traveler information messaging, primarily focused on automated blizzard messaging. Twin Cities: Travel time displays on DMS Increased reliability of travel times (reduced variations of travel times) during winter weather events, compared to typical daily travel times Local knowledge of weather and related impacts Maintenance Decision Support System (MDSS) MnDOT PeMS (Twin Cities) National Performance Management Research Data Set (NPMRDS) - NHS Page 7 of 30

8 Page 8 of 30

9 Improve Reliability, Mobility, and Efficiency Objective 4: Reduce incident response and clearance times in the Twin Cities and Greater Minnesota Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT MnDOT works closely with its incident management partners (e.g. law enforcement, tow operator services, etc.) to plan and coordinate multidisciplinary processes to detect, respond to, and clear traffic incidents so that traffic flow may be restored as safely and quickly as possible. Within this, TSMO strategies will be implemented to continue to reduce and maintain lower clearance times for incidents. These reductions in clearance times will help to reduce secondary crashes, further providing mobility and safety benefits. This TSMO is most appropriate to locations with the following conditions: The Twin Cities metro area where incidents such as crashes or debris in the traveled roadway, create traveler delays; Greater Minnesota s urbanized areas (e.g. Duluth, Rochester, Mankato, St. Cloud, Moorehead, etc.) where incidents create traveler delays; and Greater Minnesota s rural areas where significant crashes, including those that involve freight and/or hazardous materials, result in significant delays or temporary road closures. Traffic Incident Management Traveler Information and Alerts Dynamic Lane Control Expanded Quick Clearance Policies for Incidents Statewide: National Traffic Incident Management (TIM) Responder Training provided to MnDOT and partner agencies incident response staff Alternate Route Plans, including alternate route signage on many miles of rural Interstate corridors. CCTV Cameras for incident monitoring and detection on selected rural interstates (including I-35 and I-94). Twin Cities: Freeway Incident Response Safety Team (FIRST) trucks cover 220 miles of freeway Intelligent lane control signals (ILCS) - Twin Cities Extensive camera network to pinpoint incident locations and subsequent traffic impacts - Twin Cities and Greater Minnesota Extensive DMS messages upstream of incidents Greater Minnesota: Page 9 of 30

10 MnDOT works closely with its incident management partners (e.g. law enforcement, tow operator services, etc.) to plan and coordinate multidisciplinary processes to detect, respond to, and clear traffic incidents so that traffic flow may be restored as safely and quickly as possible. Within this, TSMO strategies will be implemented to continue to reduce and maintain lower clearance times for incidents. These reductions in clearance times will help to reduce secondary crashes, further providing mobility and safety benefits. Selected cameras deployed to monitor conditions Selected DMS signs with messages posted upstream of incidents Positive working relationships between MnDOT and State Patrol MnDOT Maintenance responsiveness and assistance at incidents (e.g. deployment of portable DMS, traffic control devices, etc. when called out by State Patrol for assistance). Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Reduced average time to clear lanes (calculated from the start of the incident to when all lanes are reopened) Reduced time for incident detection, notification to traffic operators, and posting of messages to DMS Statewide: MN State Patrol incident reports (if accessible by MnDOT) Twin Cities: RTMC Incident Reports (by request) Rochester: Southern Regional Communications Center Incident Reports (by request) Page 10 of 30

11 Improve Reliability, Mobility, and Efficiency Objective 5: Increase pre-trip and en-route traveler awareness of incidents and alternate options in both the Twin Cities and Greater Minnesota Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Unlike the delays caused by recurring congestion, incidents present more uncertainty to travelers. Through this, strategies and technologies would continue to be deployed to either inform travelers of more incidents or to provide increased information to describe the impacts of incidents (as well as options for alternate routes or modes to avoid the congested areas). By increasing travelers awareness and knowledge of incidents, the travelers can make informed decisions. If presented pre-trip, travelers may elect to delay or alter their trip plans. While en-route, travelers may still alter trip plans. Finally, often just awareness of the incidents can reduce driver stress. This TSMO is most appropriate to locations with the following conditions: Areas or corridors that typically experience non-recurring incidents at least twice per month that restrict traffic flow; and Areas outside the urbanized areas where incidents may be infrequent but cause substantial delays and impacts and advanced information can enable commercial and passenger travelers to alter routes to avoid serious delays and/or hazardous conditions. Traveler Information Traffic Incident Management Integrated Corridor Management Statewide: Incidents that are reported by travelers calling 911 from cellular phones are answered by MSP and conveyed to RTMC operators Incident reports are entered into CARS, triggering dissemination on 511 phone, 511 web, and mobile applications MnDOT publishes a feed of incidents to enable 3 rd party providers (e.g. Google Traffic, HERE) to download incident reports and disseminate using their existing data feeds Timely public notices and news releases released by MNDOT Information and Public Affairs Twin Cities: Incidents occurring in the urbanized areas monitored by the RTMC can be verified using CCTV cameras, and the extent of the impact can be estimated RTMC operators post messages on any of more than 600 DMS upstream of incidents Page 11 of 30

12 Unlike the delays caused by recurring congestion, incidents present more uncertainty to travelers. Through this, strategies and technologies would continue to be deployed to either inform travelers of more incidents or to provide increased information to describe the impacts of incidents (as well as options for alternate routes or modes to avoid the congested areas). By increasing travelers awareness and knowledge of incidents, the travelers can make informed decisions. If presented pre-trip, travelers may elect to delay or alter their trip plans. While en-route, travelers may still alter trip plans. Finally, often just awareness of the incidents can reduce driver stress. KBEM radio broadcasts announce impacts of major incidents in the Twin Cities Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Increased reliability of travel times during non-recurring incident events Better informed traveling public minimizing the likelihood of drivers coming upon unexpected events or delays, therefore allowing time to reroute. Local knowledge of areas with high occurrences of incidents that create delay Minnesota Crash Mapping Analysis Tool (MnCMAT) Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen Page 12 of 30

13 Improve Reliability, Mobility, and Efficiency Objective 6: Reduce delays associated with construction Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Construction can cause delays and impact travel reliability. Within this, TSMO strategies will be implemented to reduce delays and minimize impacts to travelers. All MnDOT highways have the potential to experience delays during construction, depending upon the type of work performed and the capacity restrictions that result. Work Zone Traffic Management and Maintenance of Traffic Strategies Freeway Management Integrated Corridor Management Traveler Information Connected and Automated vehicles Statewide: Intelligent Work Zone (IWZ) Toolbox for selecting and deploying IWZ strategies Coordinated work zone planning via Transportation Management Plans (TMPs) Dynamic merge systems Use of Maintenance of Traffic (MOT) details in plans and specifications Use of strategies such as Lane Closure Timetables and Lane Rentals to maintain mobility in work zones Twin Cities: Travel time information (trip time or estimated delay) Zipper merge Congestion advisories Temporary ramp metering Increased reliability of travel times (reduced variations of travel times) through work zones Reduced travel times along routes with active construction Increased accuracy of traveler information (e.g. travel times, congestion ahead) N/A Page 13 of 30

14 Construction can cause delays and impact travel reliability. Within this, TSMO strategies will be implemented to reduce delays and minimize impacts to travelers. Corridors, Functional Areas and Page 14 of 30

15 Improve Reliability, Mobility, and Efficiency Objective 7: Reduce the period of time traffic is congested or delayed due to maintenance and reactive work zone Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Unlike construction, maintenance and reactive work zone are generally shorter in duration, include less planning, and often are mobile in nature, presenting unique challenges when attempting to minimize congestion impacts. Through TSMO strategies related to this, specific approaches and technologies will reduce negative impacts of these work zone. All MnDOT highways have the potential to experience congestion or delays as a result of maintenance or reactive work zone, depending upon the type or intensity of work performed. Locations that are most likely to benefit from TSMO strategies include: Work zone locations where alternate routes offer diversion options; Work zones involving lane merges; Locations where significant queuing or slowing occurs on the approach to the work zone. Work Zone Traffic Management and Maintenance of Traffic Strategies Freeway Management Traveler Information Connected and Automated vehicles Lane closure manuals Statewide: DMS messaging upstream of maintenance and reactive work zone Portable DMS and arrow boards Press releases to inform travelers of potential delays and back-ups Twin Cities: Pilot deployment integrating lane closure information from arrow boards to traveler information (511 and alerts to TMC operators) for mobile maintenance N/A Increased reliability of travel times (reduced variations of travel times) through work zones Reduced travel times along routes with maintenance or reactive work zone Increased accuracy of traveler information (e.g. lane closure information, travel times, congestion ahead) Page 15 of 30

16 Unlike construction, maintenance and reactive work zone are generally shorter in duration, include less planning, and often are mobile in nature, presenting unique challenges when attempting to minimize congestion impacts. Through TSMO strategies related to this, specific approaches and technologies will reduce negative impacts of these work zone. Consideration of this Objective Page 16 of 30

17 Improve Safety Objective 8: Reduce the crashes related to congestion in Minnesota urbanized areas Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by When urbanized area freeways and arterials are congested, there is an increased likelihood of: rear-end collisions at the back of queues, merge related incidents at on-ramps or merge points, arterial intersection incidents, and generally other conditions that become more dangerous as demand approaches capacity. Through TSMO strategies related to this, specific approaches and technologies would attempt to either reduce congestion in urbanized areas or minimize the safety risks associated with congestion. This TSMO is most appropriate to locations with the following conditions: Freeway and arterial stretches and intersections that encounter regular congestion (e.g. congestion that lasts 20 minutes or longer at least 3 days per week on average); and Areas identified by local engineers as having a higher crash rate than other locations (either through crash reporting analyses compared to typical crash rates for the area or through informal assessments or understanding of local conditions). Freeway Management Arterial Management Traveler Information Increased emphasis on traffic signal operations Statewide: RTMC operators use DMS to warn drivers of downstream congestion or queues, when possible Twin Cities: Temporary queue detection and reporting have been deployed at selected work zones. Reduced frequency of crashes caused by congestion MnDOT PeMS Minnesota Crash Mapping Analysis Tool (MnCMAT) Page 17 of 30

18 Districts, Corridors, and Functional Areas When urbanized area freeways and arterials are congested, there is an increased likelihood of: rear-end collisions at the back of queues, merge related incidents at on-ramps or merge points, arterial intersection incidents, and generally other conditions that become more dangerous as demand approaches capacity. Through TSMO strategies related to this, specific approaches and technologies would attempt to either reduce congestion in urbanized areas or minimize the safety risks associated with congestion. Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen Page 18 of 30

19 Improve Safety Objective 9: Reduce the frequency of secondary crashes and crashes related to work zones Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Drivers approaching work zones or locations where a crash has occurred are at risk of not slowing or stopping in time and crashing into the rear of a queue that has formed. Through TSMO strategies related to this, specific approaches and technologies would help to further reduce initial work zone crashes and help address the root causes of secondary crashes by providing information and alerts to drivers as they approach and proceed through these areas. All MnDOT highways have the potential to experience crashes related to stopped traffic, either approaching work zones or existing crashes. Locations that are most likely to benefit from TSMO strategies include: Locations with a history of previous traffic queuing in advance of the work zone; or Locations with specific characteristics that increase the probability of unexpected conditions in the work zone (e.g. material hauling or delivery, ramp entry points to single-lane (head-to-head) freeway traffic, and hazardous roadway conditions such as flooding, ice, fog, etc.). Locations with limited sight distance or geometric alignments that may limit the warning time drivers have to respond to stopped traffic. Work Zone Management and Maintenance of Traffic Strategies Incident Management Traveler Information Statewide: Intelligent Work Zone (IWZ) Toolbox for selecting and deploying IWZ strategies Coordinated work zone planning via Transportation Management Plans (TMPs) Use of temporary ramp meters in congested work zones Work space/haul road intrusion warning, construction vehicle warnings Hazardous condition warning systems (e.g. flooding, ice, fog, etc.) Research on work zone intrusion detection and alert systems Twin Cities: Queue detection systems Speed advisory and stopped traffic advisories Excessive speed warnings, including dynamic speed displays Page 19 of 30

20 Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Drivers approaching work zones or locations where a crash has occurred are at risk of not slowing or stopping in time and crashing into the rear of a queue that has formed. Through TSMO strategies related to this, specific approaches and technologies would help to further reduce initial work zone crashes and help address the root causes of secondary crashes by providing information and alerts to drivers as they approach and proceed through these areas. Reduced crash rates in and around work zones Reduced secondary crashes Minnesota Crash Mapping Analysis Tool (MnCMAT) Frequency and locations of work zone crashes Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen (Bradley.Estochen@state.mn.us). Page 20 of 30

21 Improve Safety Objective 10: Reduce responder crash exposure Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT As crashes and other types of traffic incidents occur, responders often operate in unsafe conditions as they perform critical services to assist travelers from emergency medical services to vehicle and debris clearance, to traffic control. MnDOT maintains close partnerships with law enforcement and other incident response partners and has worked collaboratively with these partners to develop standard operating procedures to maximize onroad safety for responders. TSMO strategies can reduce this exposure by reducing incident clearance times, alerting travelers to the presence of responders, and equipping responders with the technologies and training they need to minimize crash exposure. This TSMO is most appropriate to locations statewide (urbanized areas and rural areas) where incident responders, including those providing traffic control during incident clearance, are on the scene assisting with and clearing incidents such as crashes, disabled vehicles, debris on the roadway, etc. Responders that perform fatal crash reconstructions are especially vulnerable due to extended time on-scene. Therefore, locations with higher than average fatal crashes might be target pilot locations for TSMO deployments. Incident Management Traveler Information and Alerts Statewide: Camera deployments, extensive in some urbanized areas, to pinpoint incident locations and subsequent traffic impacts National Traffic Incident Management (TIM) Responder Training provided to MnDOT and partner agencies incident response staff Selected DMS messages deployments with messages displayed upstream of incidents Use of pre-warning techniques including advance placement of law enforcement vehicles or maintenance vehicles with arrow boards. Minnesota Move Over law Twin Cities: Freeway Incident Response Safety Team (FIRST) trucks cover 220 miles of freeway Intelligent lane control signals (ILCS) Extensive DMS deployments with messages upstream of incidents Page 21 of 30

22 As crashes and other types of traffic incidents occur, responders often operate in unsafe conditions as they perform critical services to assist travelers from emergency medical services to vehicle and debris clearance, to traffic control. MnDOT maintains close partnerships with law enforcement and other incident response partners and has worked collaboratively with these partners to develop standard operating procedures to maximize onroad safety for responders. TSMO strategies can reduce this exposure by reducing incident clearance times, alerting travelers to the presence of responders, and equipping responders with the technologies and training they need to minimize crash exposure. Research on intrusion alert systems in temporary traffic control settings Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Reduced crashes involving on-scene incident responders Minnesota Crash Mapping Analysis Tool (MnCMAT) - Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen (Bradley.Estochen@state.mn.us). Page 22 of 30

23 Improve Safety Objective 11: Reduce the frequency of single vehicle roadway departures Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Single vehicle roadway departures can be attributed to various human factors and driver behaviors such as fatigued and drowsy driving, distracted driving, inexperienced drivers, and speeding. Inclement weather conditions can also be a factor in vehicle roadway departures. Through TSMO strategies related to this, technology and non-technology based approaches would implement initiatives to help reduce these crashes. This TSMO is most appropriate to locations with the following conditions: High volume freeways or arterials where traffic volumes and posted speeds create a higher probability that single vehicle lane departures result in head-on crashes; Roadway segments that are found to be associated with higher than average single vehicle crashes; Roadway segments with conditions that may be consistent with increased risk of single vehicle departures (e.g. horizontal or vertical curves; areas prone to early freezing, flooding, or fog; visual traps, etc.) Connected/Autonomous Vehicles Road Weather Management Encouraging Safe Driver Behavior Statewide: Selected deployments of hazardous condition detection/warning/treatment systems (e.g. flooding, ice, fog, snow, etc.) Various traveler information mechanisms (DMS, 511) that provide motorists with information to help improve driver behavior in inclement road/weather conditions Twin Cities: Cable median barrier has been installed in high-speed, high volume urban freeway settings High-accuracy GPS mapped road network that includes lane locations for in-vehicle technologies to detect roadway departures and provide alerts to drivers; and related research Greater Minnesota: In rural areas, rumble strips, signing, delineation, and high friction surface treatments have been implemented Page 23 of 30

24 Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas Single vehicle roadway departures can be attributed to various human factors and driver behaviors such as fatigued and drowsy driving, distracted driving, inexperienced drivers, and speeding. Inclement weather conditions can also be a factor in vehicle roadway departures. Through TSMO strategies related to this, technology and non-technology based approaches would implement initiatives to help reduce these crashes. Reduced frequency of single vehicle roadway departures Minnesota Crash Mapping Analysis Tool (MnCMAT) Frequency and location of single vehicle lane departure crashes Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen (Bradley.Estochen@state.mn.us). Page 24 of 30

25 Improve Safety Objective 12: Reduce the frequency of crashes at signalized and unsignalized intersections Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT The hazards associated with intersections occur in both rural and urbanized areas. In rural areas, at intersections where major and minor arterials intersect, drivers may be inattentive or distracted or the gap times between mainline vehicles may present challenges to vehicles approaching from the minor road. In urbanized areas, such as red light running or turning movement violations can result in dangerous right-angle crashes. This TSMO is to increase the safety at both signalized and non-signalized intersections by either alerting travelers to hazards or implementing operational control strategies to lower the speeds through the intersection while maintaining the capacity. This TSMO is most appropriate to locations with the following conditions: Intersections in which the average 5-year crash rate (per million vehicles entering the intersection) exceeds the MnDOT average crash rate or the intersection crash rate is observed by local engineers to exceed typical rates; or Intersections with characteristics that are found to be associated with increased crashes, including: increased skew angles, horizontal or vertical curve at or near the intersection, railroad crossing at or near the intersection, and the minor road does not have a stop sign within 5 miles of the intersection Intersection safety solutions Encouraging safe driving Increased emphasis on traffic signal operations Statewide: MnDOT has deployed several rural intersection conflict warning systems (RICWS) throughout the state. Twin Cities: Centrally monitored traffic signal systems in the Twin Cities allow real-time signal adjustment to maximize throughput and minimize delays. Greater Minnesota: Centrally monitored traffic signal systems in Rochester, Duluth, Mankato, Moorhead, and St. Cloud allow real-time signal adjustment to maximize throughput and minimize delays. Page 25 of 30

26 Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas The hazards associated with intersections occur in both rural and urbanized areas. In rural areas, at intersections where major and minor arterials intersect, drivers may be inattentive or distracted or the gap times between mainline vehicles may present challenges to vehicles approaching from the minor road. In urbanized areas, such as red light running or turning movement violations can result in dangerous right-angle crashes. This TSMO is to increase the safety at both signalized and non-signalized intersections by either alerting travelers to hazards or implementing operational control strategies to lower the speeds through the intersection while maintaining the capacity. Reduced crash rates at signalized intersections; Reduced crash rates at un-signalized intersections; Reduced crash severities related to intersection related crashes. Minnesota Crash Mapping Analysis Tool (MnCMAT) Frequency and locations of crashes at intersections Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen Page 26 of 30

27 Improve Safety Objective 13: Reduce the frequency of crashes related to road weather conditions (e.g. snow, ice, fog, etc.) Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Weather events in Minnesota, ranging from snow and ice, to flooding, fog, or wind can create unsafe conditions resulting in higher crash rates. This TSMO is to implement (and to maintain existing) initiatives to reduce the likelihood that crashes will occur during these inclement weather events. This TSMO is appropriate to all highways in Minnesota. Specific TSMO strategies would apply to a specific set of roadways most prone to localized weather conditions (e.g. flooding, snow drifts, ice buildup, fog in low areas, etc.). Road Weather Management Traveler Information and Alerts Connected an Automated Vehicles Statewide: MDSS to assess road weather conditions and recommend surface treatments Use of Press Releases to warn travelers of adverse conditions and periods when No Travel is Advised RWIS sites that provide weather and pavement data to assist with maintenance decisions Selected locations of hazardous condition detection/warning systems (e.g. flooding, ice, fog, etc.) Selected locations with remotely operated road closure systems (gates, signs) New features on 511 website and mobile app, such as plowmounted camera images showing real-time pavement conditions Implementation of Pathfinder, whereby MnDOT coordinates with partners (e.g. National Weather Service) to plan for weather events and apply consistent traveler information messaging Measures used to reduce vehicle crashes with snow plows, including driver education and news articles Reduced frequency of crashes in locations of inclement weather or visibility Maintenance Decision Support System (MDSS) MnDOT s Transportation Asset Management System (TAMS) MnDOT s Transportation Asset Management Plan Page 27 of 30

28 Corridors, Functional Areas and Weather events in Minnesota, ranging from snow and ice, to flooding, fog, or wind can create unsafe conditions resulting in higher crash rates. This TSMO is to implement (and to maintain existing) initiatives to reduce the likelihood that crashes will occur during these inclement weather events. Crash data reports as requested from the MnDOT Office of Traffic, Safety, and Technology. Contact Brad Estochen Carefully and Responsibly Manage Transportation Operations Assets Objective 14: Understand and appropriately fund the life-cycle costs of operations, managing, and maintaining the assets needed for operations Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, As TSMO strategies become institutionalized within MnDOT, there will be increased reliance on the consistent availability and use of these strategies and supporting technologies. While TSMO strategies are not adding roadway capacity or infrastructure, there are assets associated with the operations (e.g. cameras, DMS, on-board vehicle equipment, etc.). One of MnDOT s TSMO program is to understand the financial and staffing needs associated with managing and maintaining these assets in a way that does not impede on staff time dedicated to other non-operations. This TSMO is an overarching for the entire MnDOT TSMO program. Some assets that support TSMO will require more formal management than others, but it is critical that the assets supporting operations be recognized as critical to MnDOT. N/A Life-cycle analyses of TSMO related assets; Planning for phasing in / phasing out technology solutions (e.g. when to upgrade devices, when to sunset devices, etc.) MnDOT Transportation Asset Management Program (TAMP) is addressing ITS related assets. Managed life-cycles of assets Planned budgets for asset maintenance vs. actual Page 28 of 30

29 As TSMO strategies become institutionalized within MnDOT, there will be increased reliance on the consistent availability and use of these strategies and supporting technologies. While TSMO strategies are not adding roadway capacity or infrastructure, there are assets associated with the operations (e.g. cameras, DMS, on-board vehicle equipment, etc.). One of MnDOT s TSMO program is to understand the financial and staffing needs associated with managing and maintaining these assets in a way that does not impede on staff time dedicated to other non-operations. Corridors, Functional Areas and Page 29 of 30

30 Carefully and Responsibly Manage Transportation Operations Assets Objective 15: Acquire, secure, and retain the data needed for MnDOT to effectively perform operations, performance management and planning Conditions best addressed by this Examples of TSMO strategies or initiatives to accomplish this Current MnDOT Anticipated impacts of this Resources of Data and Information to Support Consideration of this Objective by Districts, Corridors, and Functional Areas As the sources of data continue to increase, so does the volume of data, the value of data, and the reliance of operations on data. Data is now critical to operations, performance management, and planning for operations. MnDOT recognizes this critical role of data, and this relates to MnDOT acquiring, securing, and retaining the data that will be used throughout all operations. This TSMO is an overarching for the entire MnDOT TSMO program. Some TSMO strategies and projects will require different levels of data management (e.g. road weather management may require increased data for MDSS, connected automated vehicles may generate extensive data, etc.). Data appears to be transitioning into more of a service that supports a wide variety of users and projects and is likely to continue this way. Throughout the TSMO program, efficient data procurement/collection, combined with effective management and security measures will facilitate open use by as many MnDOT areas as possible. N/A Data acquisition Data management Data security Data accessibility Data integration Extensive data gathering using the IRIS System on systems statewide TBD Overall data management Page 30 of 30