Category Archives: Traffic and Safety

Traffic and Safety

Using Smartphones to Deliver Effective In-Vehicle Work Zone Messages

Leave a comment

Under simulated conditions, drivers were not distracted by controlled work zone-related messages delivered through smartphones. In fact, driving performance improved. Researchers also learned that the location of the smartphone did not affect the driver if the message included an auditory component.

“The main goal was to determine whether in-vehicle warnings conveyed through smartphones would be distracting to the driver. We found that wasn’t the case,” said Ken Johnson, Work Zone, Pavement Marking and Traffic Devices Engineer, MnDOT Office of Traffic, Safety and Technology.

“We learned that drivers had a lower mental workload when they experienced the in-vehicle messages. It really didn’t matter what modality we used. Half the messages were auditory only, and half were auditory paired with visual,” said Nichole Morris, Director, University of Minnesota HumanFIRST Laboratory.

What Was the Need?

Highway work zones require drivers to reduce speed and be aware of work crews, lane closures, traffic backups, construction equipment and other potential hazards on the roadway.

Transportation departments have long employed stationary warning signs, sometimes supplemented by portable changeable message signs (PCMSs), to alert drivers to upcoming construction projects. However, some previous studies have indicated that stationary warning signs are not always effective. In addition, PCMSs are costly and may be difficult to deploy in the field.

Smartphone technology offers an opportunity to deliver accurate and early in-vehicle warnings about road construction miles ahead. Digital messages could alert drivers about upcoming work zone conditions and improve safety for drivers and workers in the field.

But receiving in-vehicle messages about work zone conditions could distract drivers from safely operating their vehicles. MnDOT needed to study the advantages and disadvantages of using smart-phones to deliver in-vehicle work zone messages.

What Was Our Goal?

The primary goal of this project was to determine whether smartphones have the potential to safely deliver effective and accurate messages to drivers about upcoming road construction on Minnesota highways.

What Did We Do?

A 7-inch LCD screen
A smartphone was replicated through installation of an LCD screen positioned inside the driving simulator.

The research team developed and conducted an online survey that focused on Minnesota drivers’ perceptions of work zone safety and on their attitudes toward using smartphones and potentially receiving in-vehicle messages regarding work zone conditions.

Data from the surveys was used by the HumanFIRST Laboratory at the University of Minnesota to develop a driving simulation study designed to determine whether in-vehicle messages sent by smartphones could promote safe driving in work zones. The study analyzed 48 drivers operating a driving simulator within two work zones to test reactions to in-vehicle messages as compared to messages displayed on an external PCMS system. Researchers collected data about each participant’s visual attention, driving performance, mental workload and opinions on smartphone technology.

Researchers also reviewed previous national studies and published works to identify environmental and driver behavior risk factors related to work zones.

What Did We Learn?

An analysis of the simulation results showed drivers were very responsive to receiving in-vehicle messages regarding work zones and roadway hazards. Messages presented through smartphones did not cause driver distractions. In fact, some drivers’ performance actually improved following delivery of audiovisual messages.

Drivers preferred to receive audio messages, and researchers learned that a synthesized female voice (like Apple’s Siri) resulted in greater awareness and acceptance from the driver than a more natural or prerecorded voice.

Survey findings showed that only 5 percent of participants use a dashboard mount for their smartphones, while the vast majority keep their phone in the cup holder, on the console, in a backpack or purse, or on the passenger seat. A few participants said they hold their smartphone while driving. Investigating the safety impact of this behavior paired with an in-vehicle messaging system, researchers found that the location of the smartphone within the simulator (on the dash or passenger seat) did not negatively impact driver safety or performance, providing the work zone message contained the auditory component.

In-vehicle messages required less cognitive effort from drivers, and drivers had greater recall of the hazard warning message versus stationary PCMS signage.

A significant number of survey participants, nearly 20 percent, provided unprompted feedback that it was the state’s responsibility to provide factual work zone messaging information and to ensure in-vehicle technology employed does not pose a distraction.

What’s Next?

MnDOT will need to continue research into the viability of smartphones as the way to deliver in-vehicle work zone messages. The simulation study provided the findings needed to advance the project to field testing, where drivers would respond to in-vehicle messages from smartphones on a test track or under real roadway conditions. Another potential topic to explore through further research is the viability of messages delivered through electronic interface or dashboard features offered on some newer vehicles.

MnDOT should identify the medium needed to deliver in-vehicle messages and use the prescribed syntax outlined by the study for communicating messages. Researchers noted the existing 511 service provided by MnDOT currently provides road, traffic, weather and other information. A study should be undertaken to determine whether the 511 or a third-party app would be most appropriate for a future statewide in-vehicle messaging program.

This post pertains to Report 2017-19, “In-Vehicle Work Zone Messages,” published June 2017.

Traffic and Safety

Do Lower Cost Improvements to Address Congestion Lead to More Crashes?

Leave a comment

An analysis of crash data revealed that congestion-related improvements implemented on I-35W in the Twin Cities did not introduce additional safety risks. When installed strategically, improvements like priced dynamic shoulder lanes can alleviate congestion and improve safety for motorists.

“Rather than just conducting a before-and-after analysis of crashes, we also wanted to compare the expected crash rate based on changes in traffic conditions,” said Brian Kary, Freeway Operations Engineer, MnDOT Metro District.

“Probably the most significant finding was that rear-end crash risk shows an inverted U-shaped relation to lane occupancy,” Gary Davis, Professor, University of Minnesota Department of Civil, Environmental and Geo-Engineering.

Davis served as the study’s principal investigator, and Kary was the technical liaison.

What Was the Need?

A left lane on I-35W marked as a PDSL. The variable message sign shows a diamond shape (signifying a high-occupancy-only lane) and a price of 25 cents.
A PDSL automatically changes status based on traffic conditions. The diamond indicates that it is open as a high-occupancy-only lane.

The Urban Partnership Agreement (UPA) is a federally funded program managed by the Federal Highway Administration to explore ways to reduce congestion on urban freeways. The Twin Cities area was one of four urban areas selected to test several innovative technologies through the UPA. These included high-occupancy toll (HOT) lanes, engineered revisions to ramps and auxiliary lanes, and a priced dynamic shoulder lane (PDSL) system on segments of the Interstate 35 West (I-35W) corridor. Work on implementing these innovations in the Twin Cities ran from spring 2009 through fall 2010.

MnDOT may decide to incorporate selected innovations, including the conversion of bus-only shoulder lanes to PDSLs, in other corridors. Decision-makers needed to better understand the safety-related benefits associated with the UPA improvements.

What Was Our Goal?

The goal of this project was to compare the incidence of crashes occurring on I-35W before and after implementation of the UPA improvements. Researchers wanted to determine whether any increase in crashes was due to the installation of the PDSLs or to other changes in the transportation network.

What Did We Do?

Researchers started by compiling data files on variables such as traffic volume and lane occupancy, weather conditions, and the presence or absence of UPA improvements for the relevant portions of I-35W. A second set of data was prepared using the Minnesota Crash Mapping Analysis Tool (MnCMAT) to identify crashes that took place on I-35W from 2006 to 2008 and from 2011 to 2013, the three years before and after the UPA project.

Investigators established three regions — HOT, Crosstown and PDSL — and divided each region into sections so that traffic demand and lane geometry would be constant within a section.

The data files were analyzed to determine the likelihood of a rear-end crash based upon the time of day, traffic volume, weather and other conditions.

What Did We Learn?

The analysis indicated that the increase in crashes on the most analyzed sections of I-35W was not likely the result of installation of PDSLs and other UPA improvements. A noted increase in crash rates was instead tied to reconstruction work that removed a bottleneck in the Crosstown Commons area, where I-35W shared right of way with Trunk Highway 62 (TH 62). There were some exceptions, however. Fewer crashes occurred on a section of the freeway south of I-494 during both study periods. An increase in rear-end crash risk north of the Minnesota River was due to weather and traffic conditions. In addition, researchers identified an inverted U-shaped relationship between lane occupancy and crash risk along several sections of the I-35W study area.

The findings supported the contention that PDSLs, when installed strategically, are safe and can provide transportation departments with an additional resource for managing congestion and improving traffic conditions along the Twin Cities freeway network.

Installation of PDSLs in the corridor did decrease the bottleneck at TH 62, but the improvement literally moved the problem down the road by creating a new bottleneck close to downtown Minneapolis.

From the MnCMAT database, the research team found 5,545 records of various types of crashes that took place from the beginning of I-35W to the I-35W/I-94 junction during the two three-year study periods. Rear-end crashes were by far the most prevalent type of crash, with 1,513 recorded before the UPA improvements and 1,657 during the three subsequent years.

Researchers encountered some challenges in preparing the data files for analysis. Careful screening of loop detector data was needed to identify questionable statistics and required a review of individual crash reports to verify crash locations.

What’s Next?

Through this research, MnDOT gained valuable insights into the impact of the UPA improvements on crash incidents along areas studied on the I-35W corridor. The methodology employed supports using PDSLs on other sections of the freeway network.

This post pertains to Report 2017-22, “Safety Impacts of the I-35W Improvements Done Under Minnesota’s Urban Partnership Agreement (UPA) Project,” published in June 2017.

Traffic and Safety

Building More Accurate Traffic Modeling for Twin Cities Construction Projects

Leave a comment

MnDOT is exploring different software options for developing a “mesoscopic dynamic traffic model” that can more accurately predict road construction impacts than current macroscopic models like the Twin Cities Regional Travel Demand Forecasting Model.

“Dynamic traffic assignment is an emerging model type, and there are a lot of software platforms with different methodologies. MnDOT was interested in reviewing their pros
and cons,” said Jim Henricksen, Traffic Forecaster, MnDOT Metro District, who helped lead a recent research project that analyzed different software packages.

“A team maintains the Twin Cities Regional Travel Demand Forecasting Model. Any mesoscopic model would require a similar maintenance effort to keep the model from becoming obsolete as construction adds new lanes,” said John Hourdos, Director, Minnesota Traffic Observatory, University of Minnesota, and principal investigator for the study.

What Was the Need?

Traffic modeling is a valuable tool used in transportation planning to predict the impacts of new construction or maintenance projects. MnDOT currently has modeling tools available in two scales: macroscopic and microscopic. Macroscopic-scale planning level tools such as the Twin Cities Regional Travel Demand Forecasting Model predict driver route choice and the number of drivers that will travel on a given road at a given time. Microscopic-scale traffic simulation, on the other hand, models driver behaviors such as gap acceptance or acceleration rates. MnDOT uses microscopic-scale simulation to plan capacity-increasing projects, but the tool is only feasible on the corridor level because generating the simulation requires a large amount of data and computing power.

To bridge these two scales, MnDOT is developing a mesoscopic-scale dynamic traffic assignment (DTA) model for the Twin Cities. This model falls between microscopic- and macroscopic-scale modeling in scope and complexity. It simulates the movement of individual vehicles based on traffic flow equations rather than driving rules, which requires less detail and computing time than a microscopic simulation and can be used over a wider area. MnDOT will use this model for applications such as staging construction seasons to minimize the disruption caused by multiple large projects, or coordinating traffic modeling across the road networks operated by MnDOT, counties and cities.

To assist in developing this system, MnDOT needed information about the capabilities of available modeling software packages in addition to the needs, desires and restrictions of the agencies and consultants who will be using the model.

What Was Our Goal?

The goal of this project was to better understand the capabilities of commercially avail-able modeling software packages to address MnDOT’s modeling and simulation needs.

What Did We Do?

Investigators interviewed stakeholders about their understanding of and need for mesoscopic traffic simulation and DTA. Stakeholders included individuals who have used or requested data from the Twin Cities Regional Travel Demand Forecasting Model maintained by the Metropolitan Council. Investigators also reviewed four case studies of mesoscopic DTA models used in Manhattan; San Francisco; Detroit; and Jacksonville, Florida.

To supplement the findings from the interviews and case studies, investigators conducted a comprehensive review of the claimed capabilities of six commercially avail-able traffic simulation software packages: TransModeler, Aimsun, DynusT/DynuStudio, Dynameq, Cube Avenue and Vissim. Investigators didn’t test the software, but instead reviewed manufacturers’ documentation and literature to identify limitations of their methods and whether those methods are applicable to MnDOT’s needs.

Traffic in a highway work zone.
DTA can aid in staging multiple major construction projects in the Twin Cities to minimize the disruption they cause to travelers.

What Did We Learn?

To compare the capabilities of the various simulation software packages, investigators created a matrix that included comprehensive notations about a software package’s claimed features that may not fully meet MnDOT’s simulation needs. For example, some software packages claim to model actuated signals, but they create models based on Highway Capacity Manual assumptions rather than real-world conditions.

DynusT is the most commonly used simulation program, possibly because it is open-source and the easiest software to use, although it requires DynuStudio, a commercial graphical user interface and data management system. DynusT also has some limitations, such as not considering the individual lanes in each roadway segment, which would limit its effectiveness in modeling roads where individual lanes have imbalanced densities.

Most interviewees had only limited experience with mesoscopic modeling. Incorporating traffic signals in a simulation network is a significant challenge, according to interviewees, because currently a database of signal timings isn’t available.

While all four of the DTA case studies reviewed required more data, calibration and validation than older models, each of the developers reported that these challenges had been mitigated, and the models created could answer complex questions that previous models couldn’t.

What’s Next?

Traffic simulation and modeling is a fast-developing field, particularly mesoscopic-scale modeling. Each of the software packages reviewed in this project has had at least two new versions in the past 18 months, and while their modeling approaches are fundamental to the software in some cases, in other cases capabilities will be added or improved as software develops.

The foundation of a mesoscopic model for the Twin Cities has been built and tested in Transmodeler (with significant pro bono work from the software developer). However, MnDOT has also used its existing DynusT model for several projects beyond its initial purpose, and the agency will use the information gathered in this project to determine which approach is more practical for MnDOT and its consultants based on cost, capabilities and data availability. Transmodeler is generally more powerful, but it will also incur greater costs, particularly since every consultant would need to acquire its own copy of the software.

This Technical Summary pertains to Report 2017-10, “Framework and Guidelines for the Development of a Twin Cities Mesoscopic DTA Model,” published April 2017.

Traffic and Safety

Using SMART-Signal Data to Predict Red Light Running at Intersections

Leave a comment

This project developed a methodology using traffic data collected by the SMART-Signal system to identify intersections prone to red light running and, therefore, serious crashes. This methodology could help MnDOT prioritize intersections for safety improvements.

“The essence of this project was to develop a toolbox that traffic engineers can use to determine an intersection’s safety performance,” said Henry Liu, Research Professor, University of Michigan Transportation Research Institute.

Liu served as the study’s principal investigator.

“This research provides a way to classify intersections that have a higher potential for red light running,” Mick Rakauskas, Former Research Fellow, HumanFIRST Program, University of Minnesota

What Was the Need?

Engineers traditionally measure an intersection’s safety using the number of crashes that actually occur there. However, collisions are rare and somewhat random events, and it can take a long time to collect enough data to accurately assess a single location’s safety.

Traffic conflicts—“close calls” in which one or both drivers must brake, swerve or take some other evasive action to avoid a crash—happen much more often than collisions do. As a result, many research projects use traffic conflicts as an alternative measure of safety.

Red light running (RLR) is one of the most common and dangerous causes of traffic conflicts at signalized intersections. While not every RLR event leads to a collision, it is often the first step in a process that ends in one.

Additionally, crashes caused when drivers run red lights are typically right-angle crashes, which are frequently severe. About 45 percent of right-angle collisions result in injury compared to about 25 percent of other crash types. Reducing right-angle-crash frequency can therefore significantly improve overall road safety and reduce costs related to traffic collisions.

MnDOT’s Safety Group wanted to determine whether it was possible to objectively and automatically identify intersections where RLR events are most likely to occur. Developing a methodology to identify the most dangerous intersections would help MnDOT prioritize locations for safety improvements.

What Was Our Goal?

Several previous MnDOT research projects had developed the SMART-Signal system, an automatic system that collects data from traffic signal controllers at signalized intersections. MnDOT has installed the system at more than 100 intersections in the Twin Cities. This project sought to develop tools that use SMART-Signal data to evaluate safety performance at intersections.

What Did We Do?

flowchart
This flowchart shows the methodology for determining whether an RLR event will result in a crossing conflict.

Researchers analyzed SMART-Signal data collected at the intersection of Boone Avenue and Trunk Highway 55 (TH 55) in Golden Valley between December 2008 and September 2009. This intersection is equipped with both stop-bar detectors and advance detectors located about 400 feet upstream of the intersection. Researchers used stop-bar-actuation data and details about traffic signal phases to identify RLR events at the intersection.

However, since most intersections are equipped only with advance detectors, this method cannot be used to measure RLR events at all intersections. As an alternative, re-searchers used vehicle-speed and traffic-volume data from the advance detectors, along with recorded traffic-signal-phase information from SMART-Signal, to identify potential RLR events. They compared these potential events to actual RLR events identified using stop-bar data and developed a formula to predict whether an RLR event would occur. This formula can be applied at intersections of major and minor roads that are not equipped with stop-bar detectors.

Researchers then used data from a minor road to develop a method that identified whether an RLR event would lead to a traffic conflict. In this method, an intersection is first divided into four conflict zones (two in each direction). When a vehicle from the main road enters the intersection, the method enables researchers to calculate when the vehicle enters and leaves each of the conflict zones it passes through. Then they determine whether a vehicle from the minor road is in the same conflict zone. Using this methodology, researchers estimated the number of daily traffic conflicts at other inter-sections on TH 55. These estimates were based on data collected in 2009 and between 2012 and 2015.

Finally, researchers developed a regression model to evaluate whether adding the number of predicted traffic conflicts to a more standard model that used average annual daily traffic (AADT) would correlate with the number of actual collisions at that site. They evaluated the model using data from seven four-legged intersections and two T-intersections on TH 13 and TH 55.

What Did We Learn?

The formula for predicting RLR events matched observations 83.12% of the time, based on more than 2,000 data points.

The number of daily crossing conflicts at TH 55 intersections ranged from 7.9 (at Glenwood Avenue in 2009) to 51.2 (at Winnetka Avenue in 2013).

While limited data were available for the regression model (as no site had more than four years of SMART-Signal data available, and there were only 11 crashes in total), the model suggests that estimated average traffic conflicts and minor-road AADT both contribute to accurate prediction of right-angle-crash frequency, while major-road AADT does not. Due to the limited data available, however, these conclusions should be considered preliminary.

What’s Next?

While there are currently no plans for follow-up studies, additional research efforts could include continuing to evaluate and improve the prediction model as more data are collected, and installing video cameras at intersections to validate the proposed methodologies.

This Technical Summary pertains to Report 2017-08, “Estimation of Crossing Conflict at Signalized Intersection Using High-Resolution Traffic Data,” published March 2017. 

Traffic and Safety

Choosing Effective Speed Reduction Strategies for Roundabouts

Leave a comment

Using survey results and prior research, this project developed a new resource to enable Minnesota local road engineers to select appropriate speed reduction measures for roundabouts. Further research is needed to determine the relative effectiveness of different measures alone and in combination.

“Although roundabouts are becoming common, single-vehicle crashes from drowsy, inattentive or unfamiliar drivers are still a concern, particularly in rural areas,” said Joe Gustafson, Traffic Engineer for Washington County. “This project provides an overview of existing speed reduction treatments that have been used in both roundabout and nonroundabout contexts, and a framework to properly evaluate the effectiveness of new treatments.”

“Rather than try to identify the right combination of treatments, the research was designed to give engineers a variety of options to consider for a given location,” said Susan Chrysler, Senior Research Scientist, Texas A&M Transportation Institute.

Gustafson served as the technical liaison for the study, and Chrysler was the principal investigator.

What Was the Need?

2017-14-p1-image

Roundabouts can provide a safer alternative to traditional intersection control devices like traffic signals and stop signs. Roundabouts have been proven to reduce crash severity by requiring drivers to decrease speed during the approach to the intersection. But failure to slow down sufficiently could result in a crash.

Signs and markings are key treatments used to communicate to drivers that they must slow down as they approach the roundabout. When navigated appropriately, roundabouts can eliminate or reduce the severity of crashes, reduce delays and reduce fuel consumption.

What Was Our Goal?

This project had two goals: to analyze existing research and conduct a survey of roundabout design and installation practitioners to determine best practices; and to develop a resource that engineers can use to identify appropriate speed reduction treatments for high-speed approaches to roundabouts.

What Did We Do?

Investigators surveyed transportation engineers from Minnesota and other states, along with technical consultants, to learn their experiences managing roundabouts with high-speed approaches. The survey addressed geometric design parameters and traffic control methods, changes in maintenance practices, crash history and speed reduction measures that were considered or eventually enacted.

Previous research on the subject was studied, including the Federal Highway Administration report Roundabouts: An Informational Guide and National Cooperative Highway Research Program Report 672: Roundabouts: An Informational Guide, Second Edition. Design manuals from four states were reviewed to provide a sample of the material avail-able to practitioners seeking guidance on design of high-speed roundabout approaches.

Based on their research, investigators provided information on the effectiveness of various treatments and on their installation and maintenance costs. They also developed a methodology for conducting a speed study to assist engineers in determining the most effective treatment for a given intersection. Treatments for alerting drivers that a round-about is ahead include traditional signs, pavement markings, illumination and other indicators, plus advanced devices like speed-activated, LED-enhanced warning signs.

What Did We Learn?

Each roundabout presents unique challenges. Local road engineers need to evaluate the characteristics of the intersection being considered (such as geometric design and adjoining land use) and the costs of installation and maintenance before recommending a specific treatment or combination of treatments.

Other findings include the following:

  • Speed reduction techniques found effective for horizontal curves, urban-rural transition zones and isolated rural intersections should be effective for rural roundabouts with high-speed approaches.
  • In rural locations, speed reduction treatments that have been used at railroad crossings, T-intersections and work zones may also be applicable to roundabouts.
  • Some unique treatments used internationally hold promise, but further study is needed before these treatments can be recommended for use in the United States.

What’s Next?

This study was the first phase of research. The findings provide the methodology to select, install and evaluate treatments at different locations. Further research is needed to accomplish the following:

  • Analyze the effectiveness of speed reduction treatments at different locations
  • Determine the impact of different combinations of treatments
  • Establish the comparative benefits of two or more treatments that fall within the same general cost and maintenance grouping
  • Analyze the impact of roundabout infrastructure (such as gateway treatments and illumination), various pavement markings and the long-term effects of specific signing treatments.

This Technical Summary pertains to the LRRB-produced Report 2017-14, “Strategies for Effective Roundabout Approach Speed Reduction,” published May 2017. 

Traffic and Safety

Self-propelled auto-flagger keeps workers out of traffic

Leave a comment

Working with a Minnesota manufacturer, researchers developed a moving automated flagger assistance device (AFAD) that signals traffic at work zones. The AFAD is operated remotely by a worker who can stand off the roadway out of traffic.

“Everybody who has used the mobile AFAD has liked it. We love our stationary AFAD unit. These units have really big stop-slow signs—they’re so visible,” said Jeremy Gjovik, Transportation Operations Supervisor, MnDOT District 3.

“The AFAD is a one-of-a-kind device. We were able to basically start from scratch and come up with a device that meets all the needs it was designed for,” said Edward Terhaar, Principal, Traffic Engineering, Wenck Associates, Inc.

Terhaar served as the principal investigator for the study.

What Was the Need?

According to data from the U.S. Bureau of Labor Statistics, 149 roadway workers were killed nationwide from 2003 to 2015 while flagging or directing traffic, and many near misses have been reported with the increase in distracted driving that has come with mobile device use.

In 2014, MnDOT trained over 60 state and district maintenance workers in the use of an automated flagger assistance device (AFAD). The AFAD has been embraced in Minnesota as a highly visible device that effectively directs traffic in stationary maintenance and construction projects while keeping flagging personnel off the road during operation.

The AFAD does not, however, suit moving operations (like pavement crack sealing) because the device requires towing. Engineers at MnDOT wanted to determine if the AFAD could be made into a mobile device that could be operated by a road crew near, but not on, the roadway.

What Was Our Goal?

MnDOT funded this research to develop a self-contained, self-propelled mobile AFAD for use on moving work zone roadway projects.

What Did We Do?

2017-09-p2-imageResearchers met with MnDOT engineers to identify the features that would be required in a moving AFAD. They determined that the device would have to be towable to a construction site with standard towing gear, operable remotely through wired or wireless controls, movable forward and in reverse, and able to use rechargeable onboard batteries.

The research team investigated existing self-propelled devices from the United States, Canada and Australia for moving wheeled objects, large and small, to see if they could be adapted to these needs. No suitable device was found.

After further consultation with the Technical Advisory Panel, researchers approached DJ Products of Little Falls, Minnesota, a company that designs and manufactures devices (including battery-operated devices) for moving trailers, dumpsters, shopping carts and aircraft.

Researchers met with DJ Products in February 2015, reviewed its products and agreed that DJ Products would develop a prototype vehicle on which the AFAD could be mounted. In August 2015, after evaluating and modifying designs, DJ Products hosted a demonstration of the prototype vehicle without the AFAD attached. The research team requested modifications, and in April 2016, the company presented a new self-propelled device with the AFAD attached.

What Did We Learn?

Initial field testing was delayed due to seasonal weather issues and device operating problems that required the replacement of components. In February 2017, a MnDOT operator tested the mobile AFAD on a crack-sealing project on State Highway 71 south of Sauk Centre.

The moving AFAD can be operated with a wired or wireless controller, as well as with controls on a handlebar mounted on the vehicle. Operators must use one remote for moving the wheeled unit, and the remote from the original AFAD for sign messaging. The new device moves forward and backward, can be towed with a standard hitch, and employs onboard batteries and a charger.

Setup and takedown require more effort than conventional flagging, but this effort is not considered cumbersome. The moving AFAD can be operated by one person standing 400 feet or more off the roadway, and the device is large enough to be easily seen and understood by road users.

The new device was used for only one hour initially. The sealing crew was outpacing the moving AFAD because the crack-sealing project entailed few repairs with greater distance between repair locations than is typical of such projects.

What’s Next?

The moving AFAD device can be used as is, and is still being tested by MnDOT. Further modifications will be requested, including enhancement of the battery-powered unit, as it currently requires a battery change to operate through an entire work shift.

Steering and controller design will likely be modified. Currently, the moving AFAD operates like a rear-wheel-drive vehicle and must be steered from its rear-wheel, traffic-facing axle, forcing the remote operator to guide it up the road as if backing up a boat trailer. MnDOT operators may ask that the device be redesigned to be steerable from the traffic-leading end of the vehicle, as if it were pulling the signage up the road, allowing for more intuitive control.

MnDOT personnel would also like to see the device’s controller integrated with the sign controller, eliminating the need for two controllers—one for moving, the other for operating the sign. Nevertheless, the device appears to be a promising option for mobile AFAD use by an operator who need not stand on the road to direct traffic.

This Technical Summary pertains to Report 2017-09, “Development of a Moving Automatic Flagger Assistance Device (AFAD) for Moving Work Zone Operations,” published March 2017. 

Previous research:

Traffic and Safety

ATM Queue Warning Systems Can Reduce Freeway Crashes

Leave a comment

ATM queue warning systems were developed and deployed on two freeways to alert motorists to queuing conditions ahead that could lead to rear-end crashes. At one test site, the prototype system substantially reduced crashes and near-crashes. At the other site, it reduced speed variances.

“The big lesson learned was that the detection method had to function quickly and display a message that was timely and accurate. This gains the trust and confidence of the motoring public,” said Brian Kary, Freeway Operations Engineer, MnDOT Metro District.

“Deploying the product of this research was not difficult. The challenge came in closing the gap to alert the drivers to slow down,” said John Hourdos, Director, Minnesota Traffic Observatory, University of Minnesota.

Kary served as the technical liaison for the study, and Hourdos was the principal investigator.

What Was the Need?

To reduce congestion and improve safety, MnDOT has deployed active traffic management (ATM) technology on two highways in the Twin Cities freeway network. The ATM system incorporates intelligent lane control signals (ILCS) placed over selected lanes at half-mile increments to warn motorists of incidents or hazards ahead. With advance warning, drivers can slow down and possibly avoid crashes.

The deployed system, however, does not specifically target the prevention of rear-end collisions, which are the most frequent type of crashes on freeways. Research has shown that rear-end collisions tend to occur during extended lines of stop-and-go traffic and at end-of-queue locations. Overhead, real-time electronic messages that warn of queuing conditions ahead can prepare motorists to reduce speed and avoid potential rear-end collisions. Such messages have the added benefit of improving mobil-ity since fewer crashes will improve traffic flow.

What Was Our Goal?

This project sought to develop and field-test two different prototypes for ATM queue warning systems. One prototype would address stop-and-go traffic and end-of-queue situations. The other would address shock waves, a crash-facilitating condition where there is a sudden change in traffic movement that causes a cascade of braking. The long-range goal of the project is to develop a unified ATM queue warning system that can be deployed at other locations within the freeway network.

What Did We Do?

Development of two prototype high-resolution ILCS warning systems began in 2014. The systems were then deployed on two high-traffic freeways in the Twin Cities: one on Interstate 35 West (I-35W) and the other on I-94. Both were still in operation in mid-2017.

The two locations have significantly different traffic conditions. On I-35W, congestion creates expanding queues that extend from the Trunk Highway 62 (TH 62) interchange to the 50th Street overpass. At the I-94 location, crashes are most likely to occur due to shock waves that can often quickly develop near the Portland Avenue overpass.

2017-20-p2-imageTo capture traffic data, researchers used either live video from closed-circuit-camera detector stations or data from existing in-pavement loop detectors. The ILCS units dis-played the message Slow Traffic Ahead, which would direct drivers to reduce speed due to the congested lanes ahead. Other messages, such as Prepare to Stop or Traffic Ahead 10 MPH, were considered but not tested during this initial study.

A server installed at the Minnesota Traffic Observatory at the University of Minnesota archived the time and location of each queue on I-94 and measured its duration and length. This provided the data needed to develop two algorithms that can be used to develop a rear-end-collision warning system that can be installed at freeway locations where similar queuing conditions exist.

What Did We Learn?

The data collected show that warning messages delivered by the ATM system can be effective in alerting drivers to queuing conditions. The ultimate benefit is a reduction in rear-end collisions in downstream locations on the freeway.

Data recorded at the I-35W location revealed that:

  • Messages delivered by the ILCS system helped drivers maintain a steady speed and eliminate stop-and-go travel.
  • The contents of warning messages should be crafted to have an impact on all motorists. Drivers responded differently to specific messages.
  • Queue warning systems can be made more effective through deployment of a real-time, lane-specific ILCS system and collection of high-resolution data.
  • Some drivers did not always heed the first queue warning message to decrease speed, but they did slow down further along the roadway.
  • There was no significant difference in impact between warning messages issued during the morning peak travel period and those issued during the evening peak.

In the first three months of queue warning system operation, the crash frequency re-corded at the I-94 test site was 9.34 crashes per vehicle miles traveled (VMT) and 51.8 near-crashes. This was a 22 percent decrease from the 11.9 crashes per VMT recorded at the site in 2013 monitoring data, and a 54 percent decrease from the 111.8 near-crashes recorded there in 2013.

The research showed that to prevent potential collisions, the ATM system had to deliver messages quickly and accurately to give drivers enough time to adjust their speeds. Also, the control algorithms developed in this project can provide the queue-estimation projections needed by MnDOT and other transportation departments to enhance the effectiveness of their ATM systems.

What’s Next?

While the deployment of the two queue warning system prototypes was a relatively cost-effective option, a longer trial period of two to three years is needed to ensure that the ATM system delivers sustainable benefits.

This Technical Summary pertains to Report 2017-20, “Development of a Queue Warning System Utilizing ATM Infrastructure System Development and Field Testing,” published June 2017. 

Traffic and Safety

Gauging safety of heavy vehicles on older concrete bridges

Leave a comment

Bridges built using prestressed concrete girders are among the most common in Minnesota and throughout the U.S. because of their good performance, lower initial material costs, and relatively low ongoing maintenance costs. However, the federal requirements for these bridges have changed considerably over the years. As a result, bridges built to older specifications may score poorly when subjected to new bridge rating standards even though they are actually in good condition.

“One area in which this discrepancy between ratings and reality can cause problems is determining safe legal load limits for bridges, which are used to decide whether larger trucks may cross the bridge with an overload permit,” says Catherine French, CSE Distinguished Professor in the Department of Civil, Environmental, and Geo- Engineering and the study’s principal investigator.

“Our goal was to evaluate whether the current guidelines regarding shear forces (which transfer the loads to the supports) may be overly conservative for these older concrete bridges that are in good condition.”

Sponsored by MnDOT, the study was conducted by a team of U of M researchers including Carol Shield (co-investigator) and Benjamin Dymond.

Researchers used a multipronged approach consisting of numerical modeling and tests in both the laboratory and the field. The numerical modeling was used to apply the results of the laboratory and field tests to a study examining the effects of key parameters on the distribution of shear in a bridge system. Parameters included span length, girder spacing and depth, deck thickness, and load position.

Results showed that the shear forces for some bridges are not as high as those predicted by distribution factors in the current specifications—at least partially explaining why some MnDOT bridges with low shear ratings show no signs of distress, French says. The researchers provided recommendations for more refined methods of evaluating prestressed concrete girder bridges that rate low for shear and developed a screening tool to identify which bridges that rate low for shear should be further analyzed.

“The results of this project will help us re-evaluate aging bridges in our inventory, to distinguish those that really do have shear problems from those that don’t, and make decisions about whether they need to be replaced or rehabilitated for extra capacity,” says Yihong Gao, bridge designer with MnDOT’s Office of Bridges and Structures.

Resources:

Maintenance Operations, Research, Traffic and Safety

Reducing speeds to improve safety for work-zone flaggers

Leave a comment

When drivers approach a roadway work zone at high speeds, they put the lives of work-zone flaggers at risk. To keep flaggers safe on the job, U of M researchers are looking for better ways to capture drivers’ attention—and compel them to slow down—as they approach flagger-controlled work zones.

Kathleen Harder, director of the Center for Design in Health, and John Hourdos, director of the Minnesota Traffic Observatory, identified and tested new work-zone warning elements to more effectively capture and sustain driver attention. The project was funded by MnDOT and the Minnesota Local Road Research Board.

The project began with a simulator study in which participants completed three drives, each featuring a work zone with different warning treatments. One condition was a traditional four-sign configuration currently used to warn drivers approaching work zones. The other two conditions featured a variety of new elements, including signage with new messaging such as  a “one-lane road ahead” sign with flashing LED lights, a dynamic speed warning sign equipped with a loud warning horn that sounded if drivers exceeded the speed limit, and portable rumble strips.

“Overall, we found that the new set of elements is more effective than the elements currently used to reduce driving speeds on the approach to a flagger-controlled work zone,” Harder says.

Although adding LED lights to the one-lane road sign had no significant effect on drivers’ speeds, findings indicated that the dynamic speed sign coupled with the horn was more effective than the dynamic sign alone.

To test these new elements under real-world conditions, the researchers conducted field tests evaluating two configurations in Minnesota work zones. The first configuration followed the minimum standards outlined in the Minnesota Manual on Uniform Traffic Control Devices. The second deployed signs employing new messaging and attention-getting devices, including a dynamic speed warning sign, horn, and rumble strips.

Findings showed that the combination of the dynamic speed warning sign and the horn successfully reduced the overall speed of vehicles approaching the work zone. The portable rumble strips did not cause any significant speed reduction, but this may have been related to their location downstream from the dynamic speed sign and horn.

“Our findings reveal that the new set of elements designed to capture driver attention—including new messaging, a dynamic speed trailer, and horn—had a significant influence on reducing driver speed,” Harder says. “The experimental layout practically eliminated high-speed outliers and successfully reduced the approach speed to the flag operator.”

Research, Traffic and Safety

New work-zone warning app featured on KARE 11

1 Comment

A new app that sends warning messages to drivers as they approach work zones was featured on KARE 11 News on Thursday. The app was developed by U of M researchers in a project sponsored by MnDOT.

The story aired as part of KARE 11’s #eyesUP campaign to end distracted driving.

The app works by pairing with Bluetooth low-energy tags placed in work zones, triggering audio warnings in smartphones that are within their range. This allows drivers to get a warning message without having to look down at their phones—or at warning devices such as changeable message signs outside their vehicles. And if a driver is being distracted by their phone, the app will interrupt whatever they are doing to provide a warning that a work zone is up ahead.

U of M researchers Chen-Fu Liao and Nichole Morris, who worked on the project, are interviewed in the story, along with Ken Johnson, work-zone, pavement marking, and traffic devices engineer at MnDOT.