Like many snow- and ice-control professionals, Carver County Public Works maintenance operations staff are searching for new options to reduce the amount of chloride that reaches our waters from road salt operations. Using food production byproducts such as pickle brine are among the alternatives maintenance staff have been exploring.
Carver County regularly uses salt brine as part of their winter maintenance operations, which has become a widely accepted practice for controlling snow and ice. In the right situation, salt brine can be a more effective alternative to traditional road salt. An opportunity to obtain a free supply of sodium-rich pickle juice from a nearby canning facility seemed like a natural candidate worthy of consideration as a source of brine for county anti-icing and de-icing operations. In addition, recycling the pickle brine could reduce the amount of the waste byproduct.
The Carver County Public Works Department began testing samples of the pickle juice in 2016 with some encouraging results. But further testing showed the brine from the pickle cannery had variable salinity and pH levels that could damage maintenance equipment. Given the variables involved, staff determined it would be difficult to manually control the manufacture of the brine into a usable liquid. VariTech Industries recommended purchase of the Brine Boss, an automated brine blending system to manufacture the 23.3 percent brine solution needed for effective ice control operations. In addition, staff found adding potassium hydroxide to pickle brine neutralizes the pH level.
Carver County staff received a grant through the Local OPERA Program to help purchase the brine making system and support further research into the viability of using pickle brine in winter maintenance operations. Staff also restored an old VariTech 600 brine maker obtained from MnDOT for the project.
After extensive testing and analysis, VariTech engineers and Carver County staff concluded that pickle brine acquired from the cannery had to be exactly the same (salinity, vinegar content, and sugar content) for each and every batch or the system sensors would fail. But it turned out that the pickle brine supplier could not provide chemically consistent batches, and the VariTech system was unable to produce a consistent blend of 23.3 percent brine solution using pickle brine. As a result, Carver County staff determined they were unable to continue using pickle brine for snow and ice control.
Nevertheless, this project benefits other agencies considering the use of food production byproducts. The Carver County project demonstrates that there can be an alternative anti-icing product. As technology continues to advance, Carver County may revisit the use of pickle brine as a viable snow- and ice-control option.
For additional information about the project, check out these resources:
Data from a new system for tracking work zone intrusions may be used to change work zone design and policies, reducing the risk of injury and death from intrusion crashes.
MnDOT and the Local Road Research Board engaged researchers to develop a user-friendly system that allows highway crews to quickly record instances of motorists’ intrusion into work zones, using a laptop, tablet or paper.
“This collaboration resulted in a fast, efficient and easy-to-use system because crews and supervisors let us know throughout the process exactly what they needed to consistently report work zone intrusions,” said Nichole Morris, Director, University of Minnesota HumanFIRST Laboratory.
What Was Our Goal?
The goal of this research project was to develop and test an efficient, comprehensive and user-friendly reporting system for intrusions into work zones. It was essential for the system to be accepted by highway workers. The information collected from the system, which was modeled after the existing MNCrash report, would then be used to examine risk factors to reduce intrusions and danger to workers. Safety data would be relayed back to workers and to MnDOT managers, providing an empirical basis for design changes to work zones, as well as future policy recommendations to the state government.
“To reduce work zone intrusions and make work zones safer, we need to track and analyze the intrusions. This reporting system will generate the data we need to make smart changes and possibly to influence legislative policy,” said Todd Haglin, Emergency Management and Safety Manager, MnDOT Office of Administration.
What Did We Do?
To design a usable system for reporting work zone intrusions, research designers had to:
Understand the characteristics of the typical system user (in this case, the work zone supervisors and crew).
Develop common or typical intrusion scenarios to realistically test the system.
Conduct iterative testing with typical users (supervisors and crew members) and incorporate revisions based on test results.
The research team interviewed work zone supervisors from rural and urban truck station locations across the state: in Baxter, St. Cloud and Duluth and at Cedar Avenue near Minneapolis-St. Paul. Researchers sought to learn what crews and supervisors considered an intrusion and what they thought should be reportable elements of the intrusion, such as the work zone layout, weather, location, time, visibility, road conditions and maneuvers of the intruding vehicle.
In a common type of close call, the dark car shown here fails to merge until it is too close to the work zone, forcing the silver car out of its lane.
Researchers used information gathered from the interviews to develop four typical intrusion scenarios—which were reviewed and revised by MnDOT supervisors—and used these scenarios to test the prototype reporting interface. Then they conducted usability tests with these scenarios and with actual intrusions that crews had experienced. Users suggested changes to the report format throughout the process.
Crews and supervisors collaborated with researchers during three rounds of testing, revising the reporting interface after each round. An online beta version had been supplemented with a paper version. Both versions were revised through this iterative design process.
What Did We Learn?
This design approach allowed the research team to produce a report interface incorporating the very specific needs of the work zone crews and supervisors:
The third major revision split the report decision flow into two options—a shorter report and a comprehensive report—based on whether the intrusion presented a risk to the crew. Without this revision, intrusions that workers considered minor were not likely to be reported.
Researchers surveyed users of the system with each revision. Supervisors liked the drop-down menus, the comprehensiveness of the system and its ease of use. They rated the final revision as good in terms of usability, ease of use and time to completion (five to six minutes on average).
The final design version was tested using a laptop, tablet and paper. Multiple reporting options made it more likely that workers and supervisors would quickly report data about a work zone intrusion before details were forgotten.
What’s Next?
Supervisors and workers involved in the design process gave high marks to the final version of the reporting system. The design is considered complete. Researchers had created the interface as a free-standing program, using the University of Minnesota’s digital resources to build and evaluate their design. For this reporting system to be made vailable for use by MnDOT and other agency workers, MnDOT must engage MNIT, the state’s information technology professionals, to determine where the system will reside and to integrate it into the state’s existing computer platform.
Truck traffic significantly improves deicer performance, deicers perform poorly below 10 degrees Fahrenheit, and brine is spread more by traffic spray and snowplow throw than by storm runoff. This is the outcome of multi-year tests performed in the snow-covered parking lots of two Twin Cities entertainment destinations.
“There is notable airborne removal of deicers from road spray by vehicles and under high wind conditions. For the deicing materials MnDOT uses, little melt is observed below 10 degrees Fahrenheit,” said Tom Peters, Maintenance Research and Training Engineer, MnDOT Office of Maintenance.
MnDOT has conducted several research projects to better understand the performance of both deicing and anti-icing materials (applied to the roadway before a storm to prevent or mitigate ice buildup). Two previous studies evaluated solid materials and liquid brine. In Phase I researchers examined over 50 deicer and anti-icing compounds and blends. They determined that ice melt capacity correlates closely with application temperature, which is the principal factor in effectiveness. Rock salt offers greater ice melt capability, but liquid deicers adhere better to roadways and cause less corrosion and environmental damage to road and bridge environments.
In Phase II, researchers studied deicer performance in the field and considered how traffic levels, truck volumes, weather, pavement type and other factors affect performance. Research showed that deicers work better at warmer temperatures, with little effectiveness below about 10 degrees Fahrenheit. Truck traffic significantly improved deicer performance, contributing to wider and quicker melts. Chlorides were swept off bridge decks by snowplowing, and deicing effectiveness diminished as truck speed rose.
However, severe weather hampered research in Phase II; the winter of 2013-2014 was the coldest experienced in Minnesota in over 30 years. The severity of winter conditions impeded the temperature study of deicer performance and snowplow performance, leaving the research team and MnDOT interested in further study.
What Was Our Goal?
This study aimed to continue the work of Phase II in more representative winter conditions. Researchers evaluated deicer effectiveness, plowing effectiveness, anti-icer persistence in traffic and drains, and pavement shedding of deicers.
What Did We Do?
During the winters of 2015-2016 and 2016-2017, both of which were mild with below-average snow accumulations, the research team followed closely the methods used in Phase II.
Deicers were studied at two facilities in Shakopee, Minnesota. One facility included nine 900-foot lanes on which plow trucks spread deicers at highway speeds. The other facility featured four 500-foot lanes, where deicers were spread by hand in 100-foot segments. Investigators monitored weather and evaluated deicer performance with photography and infrared thermography.
Snowplowing by MnDOT Metro District plow operators was conducted at the two Shakopee facilities as well, at operating speeds of up to 30 mph. Researchers documented performance of various plow configurations in various truck combinations with on-site observation, handheld photography and time-lapse photography.
Anti-icing, in which deicer brines are applied to dry pavement to prevent ice formation, was conducted on an elevated section of U.S. Highway 169 near Mankato that experienced actual traffic. Investigators recorded application rate, time, temperature, precipitation and traffic, as well as deicer flow and concentration in storm drainage runoff over time.
A researcher mixes deicers in bags before spreading by hand at the test site.
Researchers studied pavement shedding of deicers in a lab in terms of storm runoff flow and anti-icer concentration in drainage from artificially induced precipitation. Deicers were applied in brine form, dried, chilled and held at temperatures below the freezing point of water and within the range of effective ice melt temperatures.
What Did We Learn?
Research confirmed that deicer performance varies with temperature, with little benefit from rock salt at 10 degrees Fahrenheit or colder unless the pavement is exposed to sunlight. Deicer accumulated in drains at substantially lower levels than roadway applications suggest regardless of traffic conditions, confirming observations that the majority of deicer loss occurs from displacement by traffic and snowplows.
Plow results were fairly uniform across all lanes and along lane lengths for a given plow type, suggesting truck, plow and driver combinations performed uniformly at each track. At higher speeds, snow rises higher in the curvature of the plow, and snow casts more broadly off plow ends and distributes to greater distances.
“Truck traffic makes a huge difference on deicer performance. If two or three dump trucks that aren’t spreading but have weight in them follow a salt truck, salt use might be cut by two-thirds,” said Stephen Druschel, Professor, Minnesota State University, Mankato, Department of Civil Engineering.
Deicers and anti-icers showed wider and quicker melting capability with traffic, especially by trucks, than without. Prewetting offered no significant observable benefit under most conditions, contrary to reports from snowplow drivers in field operations, unless snow was dry; then significant benefits were observed.
Asphalt and concrete pavements shed salinity at high levels initially and at declining levels at about 0.3 inch precipitation. The type of pavement involved had no apparent effect on deicer runoff.
What’s Next?
The impact of truck traffic on deicer performance is significant and needs to be widely communicated. Reports that prewetting improves deicer adhesion in windy conditions and speeds the initiation of ice melt may warrant further review. Evaluation of atmospheric and off-roadway drainage may help quantify traffic-induced brine spray and plow throw.
The longest winter in recent memory might have ended, but MnDOT’s traffic and maintenance staff are already planning how to make future winters easier on Minnesota drivers.
Recently, the Regional Transportation Management Center was awarded funding to deliver real-time winter weather warnings via its roadside and overhead highway message signs. The RTMC displayed blizzard warnings for the first time during six storms last winter, but the alerts had to be manually entered.
“This is similar information that you receive on your cell phone or the evening news,” said Brian Kary, RTMC Traffic Operations director. “But for somebody who’s traveling down I-90 and just passing through, they might not realize that they’re entering an area with a blizzard.”
Another initiative aims to expand the road condition data that’s available during winter storms by piloting the use of mobile sensors on maintenance supervisor trucks and above-ground sensors at select Road and Weather Information System sites.
Both projects are among eight research implementation projects recently selected for funding by the governing board for MnDOT’s transportation research program.
Weather Alerts
Minnesota has nearly 300 Dynamic Message Signs, which currently issue real-time warnings about traffic incidents, road work and congestion. Around 200 are in the Twin Cities metro; the rest are in Greater Minnesota.
Kary’s two-year project will develop a system that can automatically relay critical weather alerts, which change frequently, are labor-intensive and error-prone when physically entered. Only blizzard warnings from the National Weather Service are initially planned, but the system will be capable of broadcasting all types of weather alerts.
A number of other states already issue weather alerts via their Dynamic Message Signs, so MnDOT has case studies to look at.
Over the next two years, the Maintenance Office will test the use of mobile and above-ground sensors to expand the geographic coverage of RWIS sites, which feed valuable weather and road surface information to highway operations managers and advanced traveler information systems. This might lead to the elimination of in-road sensors, which require lane closures to maintain and must be replaced during road construction projects.
The mobile sensors will collect road condition information, such as temperature, humidity, due point, and friction, from five maintenance supervisor trucks. The other non-invasive sensors will be attached to an RWIS tower or a pole near the roadway and use laser technology to read road surface temperature and condition (water ice, slush and snow).
Potholes are one of the biggest and most costly ongoing maintenance challenges faced by highway agencies. Despite considerable progress in pavement materials and mechanics, pothole repair has remained an area in which little progress has been made.
To make headway in this area, Minnesota transportation researchers studied critical factors in pothole formation and repair in order to identify solutions that would reduce the occurrence of potholes and increase the durability of repairs. They also investigated the potential of newer materials, such as taconite and graphite nanoplatelets (GNP), in repair mixes. Researchers looked at how to make winter patches more durable and also different shapes of patches.
“Our goal was to provide a scientific assessment of pothole repair materials and practices,” said University of Minnesota professor Mihai Marasteanu, the lead researcher. Project sponsors were the Minnesota Department of Transportation (MnDOT) and the Minnesota Local Road Research Board.
What Did We Do?
Researchers began by reviewing national and international literature about pothole causes and repair activities. They also surveyed MnDOT maintenance superintendents and local engineers on current repair practices.
Next, the research team conducted simulations of square, diamond, and round pothole repair shapes to determine if some shapes were more conducive to reducing stress in repair materials. This stress analysis included the use of different common pothole filling mixes and their interface with existing pavement materials.
In the next stage of research, the team evaluated six asphalt mixes for relevant mechanical properties: four winter mixes, a polymer-modified hot-mastic asphalt mix suitable for winter and summer use, and a summer mix in two forms modified with GNP. Mixes were evaluated for compaction and bonding, tensile strength, and water penetration.
Pothole repair samples performed poorly in water penetration tests, which suggested that most mixes will perform poorly under seasonal freeze-thaw stresses.
Finally, researchers studied national and international pavement preservation and pothole prevention practices and the cost-effectiveness of pothole repair.
What Did We Learn?
Through this work, researchers learned that pothole prevention requires repairing pavement cracks as they develop—and sometimes, even timely repairs only slow pothole development.
Laboratory analysis showed that cold mixes compact and bond poorly. To be more effective, these materials require significant curing not possible in the field unless heating is provided. The polymer-modified mastic patching material that was heated was stronger than the winter mixes even at very cold temperatures. Most mastics are used in warm weather, but this material may be effective for winter uses.
Durable winter repairs require expensive patching materials and on-site heating technologies such as truck-mounted microwaves. “To make winter repairs last longer, you need to provide an external source of heat to cure winter patching materials,” Marasteanu says.
Taconite-based materials activated chemically or by heating potholes before and after filling offer promise for more durable repairs. GNP modifiers improved compaction, tensile strength, fracture energy, and fracture resistance in the summer mix.
Pothole repair samples performed poorly in water penetration tests, which suggests that most mixes will perform poorly under seasonal freeze-thaw stresses.
Also of note, the study’s exploration of pothole repair shapes found that circular repairs offer the best filling and compacting performance; repair materials cannot fill corners, even with significant compaction.
“We had been squaring off potholes, making sure patches were all at right angles. But in this study, we found that square patches increase stresses at the boundaries. The ideal is a circular patch,” said Todd Howard, Assistant County Engineer, Dakota County.
What’s Next?
The most common pothole repair in Minnesota is throw-and-roll with HMA (using a truck’s tires to compact shoveled-in asphalt). Newer, more durable repairs include taconite-based materials activated chemically or by heating potholes with a truck-
mounted microwave unit before and after filling. While promising and, in the case of the microwave method, potentially effective in extreme cold, these approaches require further research before becoming widely used in winter and spring repairs.
GNP-modified mixes also warrant further study, especially in winter mixes. If MnDOT can encourage cost tracking, analysis of the cost-effectiveness of various pothole repair methods, including the mastic tested in this research, may become possible.
This research is part of a larger effort by MnDOT to improve pothole repair approaches and develop pothole repair guidance for crews throughout the state, including a recently released asphalt patching best practices guide with decision trees.
The accumulation of chloride in our waters has become a widespread concern. In a recent study sponsored by MnDOT and the Local Road Research Board, researchers measured the transport and accumulation of chloride from road deicers in a metro-area watershed. The findings revealed a greater infiltration of chlorides into soil and subsurface waters than previously assumed.
“The results of this research provide us with knowledge we did not
have before,” says William Herb,a research associate with the University of Minnesota’s St. Anthony Falls Laboratory and the study’s principal investigator. “It will help investigators and policymakers explore ways to capture chlorides and mitigate their damaging environmental effects.”
Road salt (sodium chloride) is used in most states that experience snow and ice, with growing impact. For example, chloride levels in some lakes and streams in the Minneapolis–Saint Paul metro area exceed state and federal water quality
standards, and a recent study showed that levels in more than one-quarter of shallow groundwater wells in the metro were above drinking-water taste standards.
“This is a real concern because even in low concentrations, chloride can be lethal to sensitive plants and some aquatic species, and many of our lakes, wetlands, and streams show acute or chronic levels of chloride,” Herb says.
To learn how chlorides from road salt deicers are transported in urban watersheds, researchers installed field instruments at eight sites in a Roseville watershed. They monitored water and chloride levels nearly continuously over three winter seasons; this included runoff directly from sources (roads and parking lots), transport in ditches and sewer networks, and retention in and release from detention ponds and wetlands. Computer modeling was used to generalize results.
This drain along State Highway 36 was one of the roadway runoff discharge sources used in the study.
Overall, the team observed substantial chloride retention via infiltration to soils and groundwater. For example, monitoring the runoff from a vegetated highway ditch showed that more than 95 percent of the chloride applied to the highway infiltrated
from the ditch into the soil, and less than 5 percent was exported from the site in surface runoff. “Interestingly, substantial chloride export from the ditch was observed in November rainfall runoff prior to application of any new road salt for the upcoming winter, suggesting long-term storage in soils and groundwater in and near the ditch,” Herb says.
Researchers also found that winter rain-on-snow events and the first major
prolonged thaw each season moved surface chlorides most effectively into the watershed.
The research team then used the data and modeling to examine potential strategies for reducing or mitigating the spread of chloride, including capturing low flows, seasonal runoff capture, and capture based on salinity.
Wayne Sandberg, deputy director of the Washington County Department of Public Works, chaired the study’s technical advisory panel. “Based on this research, we now know that deicer chemicals are staying in the soil and moving in the watersheds, and this should change how we manage ice and snow control,” he says. “The next questions are what can we do with that knowledge and what changes can we make.”
MnDOT installed network dash cameras and ceiling-mounted cameras on 226 snowplows, approximately one-quarter of MnDOT’s snowplow fleet. The cameras, integrated with the onboard mobile data computer and automated vehicle location equipment, automatically captured snapshots of road conditions during plowing. The snapshots were incorporated into several facets of MnDOT’s 511 traveler information system: the desktop and mobile versions of the website and the 511 app. Motorists and MnDOT alike found the project to be valuable, with the up-to-the-minute imagery helping members of the public and MnDOT’s maintenance staff make well-informed decisions during winter storm events.
“The largest barrier to implementation involved the development of the software package for integrating snowplow cameras into the current AVL system. It required a great deal of back-and-forth to get things right,” said oe Huneke, Maintenance Decision Support Systems (MDSS)/AVL Section Manager, MnDOT Office of Maintenance.
“We did research to make sure the cameras did not block drivers’ views, taking state and federal regulations into consideration, and we tested the cameras to make sure they were capturing images at the right resolution,” said Jon Bjorkquist, Maintenance Technology Development/ Implementation Coordinator, MnDOT Office of Maintenance.
What Was the Need?
Reliable information about road conditions during winter weather allows motorists to make informed travel decisions and helps MnDOT responders maintain roads. While meteorological updates on a winter storm and automated status reports on Minnesota’s snowplow fleet are important sources of data, they do not provide visual information about road conditions.
In 2015, a pilot project allowed MnDOT to take road condition pictures from cameras mounted on selected snowplows during winter storms. The system was limited, however. Few snowplows were outfitted with these cam-eras, images were not available to the public, and network infrastructure did not allow for easy scaling. A larger scale program was needed to capture road imagery taken from snowplows across Minnesota and to share the pictures with Minnesota motorists.
What Was Our Goal?
MnDOT sought to install cameras on a sizable portion of MnDOT’s snowplow fleet. In addition to making hardware and network enhancements to collect and compile the image data, MnDOT also set out to make the photos avail-able in near-real-time to its internal maintenance staff and the traveling public.
To capture images of road conditions, MnDOT mounted cameras in the cabs of one-quarter of MnDOT’s snowplow fleet.
What Did We Do?
In 2015 and 2016, MnDOT installed network dash cameras and ceiling-mounted cameras on 226 snowplows, approximately one-quarter of the agency’s total snowplow fleet. The cameras, integrated with the onboard mobile data computer and automated vehicle location (AVL) equipment, automatically captured snapshots of road conditions during plowing. This system included the following key operational features:
The dash cameras automatically recorded images whenever the computer-AVL system was on.
The cameras recorded an image of the road ahead of the plow.
Images were taken once every five minutes and were only retained if the plow was moving at least 10 mph.
The cameras were capable of taking operator-initiated snapshots and video clips.
Video clips could be classified into three categories: accident, general interest or work zone.
The system sent the plow camera images and metadata (geolocation, plow, camera and conditions) to a MnDOT server upgraded to accommodate the data. MnDOT set a data retention schedule for mobile snapshots and video segments as well as the data server.
Plow images were incorporated into several facets of MnDOT’s 511 traveler information system, including the desktop and mobile versions of the website and the 511 app. Plow images plotted at 10-minute intervals on the 511 maps provided motorists with up-to-the-minute, easily accessible information on road conditions. The images were also incorporated into MnDOT’s internal website called Condition Acquisition and Reporting System.
What Did We Learn?
The project demonstrated the successful integration of various hardware, software and network systems, carrying the road weather imagery step by step from the cameras to the public 511 interface. The project also succeeded in scaling up an earlier, modest effort to furnish snowplows with cameras.
In addition, MnDOT collected input on the value of the cameras from a range of interested parties: the public, snowplow operators and supervisors, and MnDOT management staff.
The public response was overwhelmingly positive, with 319 Facebook users responding to a MnDOT post about the cameras. All the respondents used positive emote icons (“heart” or “thumbs up”). Several members of the public provided responses through Facebook and MnDOT’s “Contact Us” Web page about the value of being able to view actual road conditions, though others expressed concern about the cost of the system.
Surveys of MnDOT snowplow drivers and supervisors and interviews of MnDOT managers revealed that supervisors and managers had a largely positive view of the program as well. Drivers provided mixed reviews. Comments from these groups yielded the following recommendations about implementing a program of this nature:
Perform outreach efforts that clearly communicate benefits to achieve broad buy-in from snowplow drivers. Provide training and follow-up instruction on use of the cam-era’s features to encourage drivers to use the manual snapshot and video features.
Address drivers’ concerns about privacy (such as “Big Brother is watching”) directly, and understand that these concerns have lessened over time. Supervisors should be advised not to react too quickly to privacy concerns.
Address concerns about in-cab distraction by adjusting the system configuration or hardware. This might include making dash camera screens dimmable at the driver’s option, or placing screens and cameras out of critical sightlines.
What’s Next?
This project was a success, with snowplow camera images providing significant benefits to MnDOT staff and the traveling public. Based on this work, MnDOT plans to install camera systems on additional snowplows in the state fleet—as deemed necessary by district management—and to continue displaying snowplow images on MnDOT’s 511 system.
For most road crews, repairing potholes is an essential and highly visible duty. Choosing the best or most cost-effective pothole repair method, however, has remained a complicated puzzle.
Researchers identified four pothole repair methods suitable for Minnesota: cold mix, hot recycled asphalt, mastic material and mill-and-fill with hot-mix asphalt. They tracked the performance of each method at five sites in northern Minnesota for two years. Using the results from this monitoring period, researchers developed decision trees for selecting an appropriate repair method and best practices for using each method. The decision trees were developed in two formats: as a flowchart that can be used in a maintenance guide and as flash cards that can be laminated and used by maintenance crews for quick reference in the field.
“We wanted to develop a decision tree for choosing the right pothole repair method that could be laminated for use in the field,” said Susan Lodahl, Assistant State Maintenance Engineer, MnDOT Office of Maintenance.
“This project offers help deciding what kind of pothole patch is appropriate for the conditions, including the pothole dimensions, location in the roadway and the season,” said Manik Barman, Assistant Professor, University of Minnesota Duluth Department of Civil Engineering.
What Was the Need?
Repairing potholes is one of the most public of road crews’ duties. Drivers notice cracks and holes, and feel the effects of short-term repairs that kick up gravel as wheels roll over patched holes.
Selecting the appropriate patching method and materials varies depending on several factors, including the size of the pothole and its location on the roadway. Patching methods and materials face seasonal challenges too. In northern Minnesota, asphalt plants shut down for the winter and don’t reopen before March, if then. Potholes that are repaired in cold weather aim for short-term fixes with patches that can be replaced when warm weather returns or when the pavement can be milled and overlaid with hot-mix asphalt (HMA). Road crews have tried applying HMA in winter using various heating systems and in-place recycling methods, but even warm weather patches only offer semipermanent repair.
Whether it’s spring, summer, fall or winter, choosing the best, most cost-effective or durable pothole repair method has remained a complicated puzzle, one that MnDOT would like to help road crews solve.
What Was Our Goal?
MnDOT funded this research to help road crews choose patching methods that match specific repair conditions. Researchers explored patching tools, materials and methods to identify those most appropriate to specific pothole conditions, road locations and time of year. They also evaluated the effectiveness of different methods based on durability, road safety, ride quality, driver satisfaction and other factors.
A researcher conducts an on-site permeability test to determine how well a pothole repair seals and resists water penetration.
What Did We Do?
Research began with a comprehensive literature search of pothole repair methods in Minnesota and other states. From this search, investigators identified four repair methods that best suit Minnesota: cold mix, hot recycled asphalt, mastic material and mill-and-fill with HMA.
With help from the study’s Technical Advisory Panel, researchers identified five sites in MnDOT District 1 near Duluth, Minnesota, where they oversaw 20 pothole repairs. Investigators monitored these repairs for about two years before assessing the methods and their best applications. Researchers then developed decision trees to help road crews choose the most suitable method for each repair and compiled best practices to provide further guidance.
What Did We Learn?
The best practices describe the best uses of each of the four pothole repair methods along with guidelines for preparing the pothole for repair and placing the patching materials.
Cold-mix patches should be placed only in shallow potholes with depths of 2 inches or less. Deeper potholes should be repaired in two lifts, each compacted with a handheld compactor to prevent dishing or denting when the cold mix settles.
Hot mixes using recycled materials should be avoided. The aged binder slows the heating process, and its fines inhibit the bonding of the new binder and aggregate. The new binder also doesn’t seem to rejuvenate the old, and the patches age more rapidly. When hot mix is used for pothole repair, a handheld compactor is required. Recycling mixers such as the Stepp SRM 10-120 should be used to create virgin hot patch material using asphalt oil and sand or small aggregate.
Mastic material provides a smooth driving surface but appears to dish in potholes along longitudinal cracks because the material lacks the strength to support loads. Mastic should only be used on centerline joints and longitudinal joints along shoulders, where it stays in place. It should not be used in wheel paths.
Mill-and-fill with virgin HMA, when constructed with care, can be effective in eliminating dishing and raveling at the patch-pavement interface. Sufficient tack material must be used, and trucks should not be allowed to drive on the tack. The pothole should be filled with the proper amount of HMA, and the patch must be compacted sufficiently. Failure to carefully apply mill-and-fill can lead to significant deterioration at the patch-pavement interface after about 100 days, which can contribute to additional damage in the distressed area.
Using the findings from this study, researchers developed guidelines for patching method selection, placement, compaction practices and moisture control. They also developed decision trees for selecting the appropriate repair method for conditions. The decision trees are available in two formats: as a flowchart for use in maintenance guides and as flash cards for quick reference by maintenance crews in the field. The final report includes best practices and a step-by-step pictorial guide to patching.
What’s Next?
The decision trees and best practices developed in this study can be easily combined into a patching guide that, with laminated flash cards, can be distributed to MnDOT road crews around the state. This research could be amplified by repeating the process with more pothole repairs in other areas of Minnesota to increase data for performance evaluation and analysis of best practices.
Keeping Minnesota’s roadsides green is about more than just aesthetics—healthy turfgrass can improve water quality, reduce erosion and road noise, and provide animal habitat. However, harsh conditions such as heat, drought, and salt use can make it difficult for roadside turfgrass to thrive.
In 2014, as part of a study funded by the Minnesota Local Road Research Board (LRRB), researchers in the University of Minnesota’s Department of Horticultural Science identified a new salt-tolerant turfgrass mixture that could be used on Minnesota roadsides. But, when MnDOT began using the mixture, called MNST-12, the agency experienced a series of installation failures.
Now, led by Professor Eric Watkins, the research team has identified new best management practices for installing and establishing this type of salt-tolerant turfgrass. The study, funded by the LRRB, specifically focused on watering practices, soil amendments, and planting date for both seed and sod.
“Newer improved seed or sod mixes like MNST-12 may have differing requirements for successful establishment compared to other species or cultivars that contractors and other turf professionals are more familiar with,” Watkins says. “Since all of these management practices are prescribed—or not prescribed—in the MnDOT specifications, generating data that can inform future specifications is a valuable outcome of this work.”
The study, which was conducted over several years, included experiments on how water should be applied to new MNST-12 turfgrass installations, the use of soil amendments at the time of establishment, and the effect of the seeding or sodding date on the success of a new planting.
Researchers tested turfgrass watering requirements using an automated rain-out shelter. Photo: Matt Cavanaugh
Based on their findings, the researchers recommend these changes to MnDOT specifications:
No soil amendments are necessary, but adequate seedbed preparation is important.
Seeding is preferred to sodding between August 15 and September 15.
Sodding can be permitted throughout the year, but only if the installer is able to supply frequent irrigation.
When watering in sod, attention should be given to the species being used and local rates of evapotranspiration (evaporation from both the soil and plant leaves). Sod installers can anticipate using between 100,000 and 170,000 gallons of water per acre to ensure a successful establishment.
Sod can be mowed as soon as sufficient root growth prevents an operator from manually pulling up pieces by hand, but it should not be mowed if wilting from heat or drought.
Currently, the researchers are using the results of this project to develop methods for educating and training stakeholders, including turfgrass installers, on these best management practices. They are also developing systems that could be used by installers in the field to help maximize the success rate of turfgrass installations.
“These best management practices can help limit installation failures and reduce maintenance inputs for future installations, providing both an economic and environmental benefit,” Watkins says.
“The knowledge and improved specifications we gained through this research will allow us to make our contractors more successful, which makes MnDOT successful,” says Dwayne Stenlund, MnDOT erosion control specialist. Because local agencies often rely on these MnDOT specifications as a guide for their projects, they will also benefit from the improved practices.
Stenlund also says the new specifications—especially those related to watering requirements—could allow for a clearer understanding of the true cost and value of turfgrass installation and maintenance work, which could ultimately improve the accuracy of the project bidding process.
In another project, the research team is exploring other turfgrass stresses, such as ice cover and heat. They are also testing additional turfgrass species and mixtures in an effort to continue improving MnDOT specifications for roadside turfgrass installations.
A pilot project was begun to study the use of AVL technology in mowing operations. Potential benefits include improved mowing efficiency, improved reporting and ease of supervision, reduced paperwork and reduced spread of noxious weeds.
“Using the data we get from the AVL project, we can estimate how long it will take to mow the entire system,” said Douglas Maki, Asset Management Engineer, MnDOT Metro District. “That way, we can plan far in advance of major holidays, when the most traffic comes through our system.”
“The AVL technology can be used to mark newly disruptive weed locations and anything else a mower operator might see, like potholes, damaged signs or guardrails, and excessive or dangerous debris in the field,” said Adrian Potter, Senior Associate, SRF Consulting Group, Inc.
Potter served as the project’s principal investigator.
What Was the Need?
MnDOT is responsible for mowing roadsides along 14,000 centerline miles of highways for environmental and safety reasons. This is an enormous and critical task, requiring efficient use of employee time and mowing equipment, and efforts to avoid the spreading of noxious weeds, which will lead to increased use of herbicides.
A promising technology that many departments of transportation (DOTs) have installed is automated vehicle location (AVL). AVL systems provide a precise geographic location for DOT-owned vehicles so that real-time data can be obtained on field operations. This technology has been used for snowplowing and other fleet vehicle operations. However, only a few DOTs have used it for mowing operations.
To determine if AVL technology should be used in its
mowing operations, MnDOT undertook a pilot project involving 30 of its mowers. The locations chosen were Metro District roadsides, as MnDOT had previously invested in creating a geographic information system map of noxious weeds on those roadsides.
What Was Our Goal?
The goals of the pilot project were to:
Generate protocols for hardware installation and software training.
Set up the system for communicating data from the mowers to internal MnDOT servers.
Develop accomplishment reports based on data collected by the AVL units.
Develop and provide initial training to operators and supervisors.
Optimize the mower routes used.
What Did We Do?
For the 2015 and 2016 mowing seasons, researchers fitted 30 Metro District tractors with AVL technology, sensors and communication equipment.
The first stage of the project focused on developing the software interface required for the AVL system. The application had to provide a view of the mower’s exact location so that the mower operator could avoid noxious weeds. Data would be collected through an in-vehicle controller unit and transferred to MnDOT for analysis via a Verizon AirCard system installed on each mower.
Mechanics installed metal racks within each of the 30 mowers to protect the Ameritrak AT-500 AVL hardware unit. A video screen was mounted on the top of the rack. A reporting system was developed for use by operators, supervisors and managers. Training sessions were scheduled at the start of each season and when new operators were hired.
What Did We Learn?
The project achieved its initial goals of developing protocols for hardware and software, creating electronic reporting and capturing real-time data.
The research team gained the following insights during the planning and field-testing stages of the project:
Substantial time is needed to adequately develop and test the AVL software and hardware.
Implementing the system also requires considerable time due to resource limitations, and after implementation, it takes multiple mowing seasons to quantify weed and herbicide reductions.
MnDOT mower operators and supervisors recognized the value of the AVL system in improving the efficient use of their time, eliminating the drafting of written reports, and giving MnDOT a more accurate record of acreage mowed.
Since the tractors operated at such slow speeds, the initial data captured were too imprecise to analyze. But with software adjustments, this issue was resolved.
Installation of the AVL unit could have an impact on the operation of the tractor because the additional electrical burden that the unit places on the tractor battery may require the tractor to be sent to the manufacturer for inspection.
What’s Next?
The initial success of the pilot project provided the basis for continued use of AVL technology in Metro District mowing operations during the 2017 season and possibly beyond. MnDOT is currently evaluating whether this project has provided enough data to expand AVL to other districts in the state. The investigators estimate that after full implementation, MnDOT could save $100,000 per year.
MnDOT may consider installing AVL technology in other agency equipment to optimize and monitor maintenance activities.
