An update to BullConverter allows MnDOT’s statewide weigh-in-motion (WIM) system to adopt systems from more manufacturers. The BullReporter upgrade adds new reporting functions, including a View Vehicles function that provides an image of a vehicle along with a graphical representation of WIM data, such as weight and speed.

This upgrade, developed through a research study, expands the commercial traffic information that the Office of Traffic System Management can provide to the MnDOT Office of Bridges and Structures, local and state permitting agencies, the Minnesota State Patrol and other Minnesota authorities.

“With BullReporter, now we can produce daily, weekly and monthly reports of the overweight vehicles that cross over WIM sensors,” Benjamin Timerson, Transportation Data and Analysis Program Manager, MnDOT Office of Transportation System Management.

What Was the Need?

Weigh-in-motion (WIM) systems measure characteristics of individual vehicles on the road, generating records of data that include vehicle type, speed, axle weights and spacing. When a vehicle crosses WIM sensors in the pavement, it triggers electrical signals that are transmitted to a WIM controller, which converts the signals into usable WIM vehicle data. A number of manufacturers produce WIM sensors and controllers, and each vendor employs its own methods of processing signals and producing proprietary WIM data.

In 2009, MnDOT began using BullConverter/BullReporter (BC/BR) software with heterogeneous WIM systems. BC converts incompatible, proprietary data into a uniform comma-separated values (CSV) format. BR generates reports from the converted CSV data, allowing the analysis of WIM data over different systems.

Currently, MnDOT’s Office of Transportation System Management (OTSM) uses WIM systems from International Road Dynamics (IRD), but recently began evaluating systems from Kistler and Intercomp. In a current study, investigators are evaluating the use of Intercomp WIM controllers with Intercomp sensors, IRD controllers with Kistler sensors, and Kistler controllers with Kistler sensors. These new WIM system combinations require new conversion functions in BC.

What Was Our Goal?

The goal of this project was to upgrade the BC/BR software package by improving  existing functions and incorporating new functions that will convert Intercomp and Kistler formats to the Bull-CSV format and refine export functions in BC. MnDOT also wanted to expand data reporting capabilities and analytical options in BR, including a View Vehicles capability for analyzing individual vehicles.

What Did We Implement?

MnDOT funded enhancements to the BC/BR software package to include Kistler and Intercomp formats and develop new data retrieval, statistical assessments and report generation applications, including View Vehicles.

How Did We Do It?

MnDOT provided the original BC/BR developer with a detailed list of enhancements and new conversion and reporting functions. The team developed a new WIM data downloading tool for Kistler controllers that would connect the controllers through the Internet and download and archive the raw data. Developers added two new conversion functions in BC to support conversion from Kistler and Intercomp formatted data to CSV-formatted data. The team also updated the export function in BC.

The software team then added View Vehicles report, a new reporting function, to BR. View Vehicles allows queries of vehicle records under any combination of parameters, including lane numbers, date and hour ranges, class numbers, gross vehicle weight (GVW), speed range, axle weight ranges and warning flags. Retrieved vehicle data are then displayed in web or PDF formats with a digital photo of the vehicle and graphics of selected WIM parameters.

The team added histogram functions for GVW and equivalent single-axle load (ESAL), which would retrieve a set of vehicle data based on user-selected parameters and then plot a graph or produce a spreadsheet. Developers enhanced a few other elements of BC/BR, wrote a manual for editing classification schemes and trained OTSM staff on the editing procedures.

What Was the Impact?

Deploying the updated BC/BR software package has significantly helped MnDOT and other state agencies. OTSM now can produce many different reports with a range of user-selectable data queries that can be customized to share with the MnDOT Office of Bridges and Structures, the Minnesota State Patrol and overweight permitting offices.

Expanded GVW and ESAL data generated with the updated software can be used in evaluating designs for new bridge construction. Permitting offices can draw upon BR reports to request changed axle configurations of overweight vehicles to prevent bridge damage. OTSM can also provide reports and vehicle images for compliance activities to the MnDOT Bridge Office, permitting offices and the State Patrol.

In addition, the updated BC/BR can provide data on traffic volume and vehicle class to the Office of Traffic Safety and Technology, can inform design decisions by the Office of Materials and Road Research, and can offer a wide range of useful information to the Office of Freight and Commercial Vehicle Operations.

“This software allows us to use different WIM systems and generate reports and analysis by integrating incompatible systems. We added more capabilities in BullConverter and increased BullReporter functions from 40 to more than 60,” Taek Kwon, Professor, University of Minnesota Duluth Department of Electrical Engineering.

What’s Next?

BC and BR are now fully updated for current needs and are in use by OTSM. The upgraded software will be used until industry changes or new analytical needs arise at MnDOT.

This posting pertains to Report 2017-34, “Enhanced Capabilities of BullReporter and BullConverter,” published September 2017. The full report can be accessed at mndot.gov/research/reports/2017/201734.pdf.