Transportation workers face critical safety risks when drivers fail to comply with traffic control instructions in work zones. These intrusions threaten not only the flaggers who are directing traffic, but all workers on the job site and the drivers themselves. Knowing the nature and frequency of intrusions is necessary to develop effective prevention strategies. A new mobile phone app enables workers to quickly and easily report incidents, allowing MnDOT to analyze risks and improve worker safety.
In previous research, a process was developed for workers to report work zone intrusions. Both an online system and paper forms were created to allow workers to report intrusion information, which was then used to develop a database of work zone incidents. This process, however, was not used consistently, and there was insufficient data to identify commonalities or trends.
“The work zone intrusion app gives workers a way to report how, when and where incidents are happening, and gives MnDOT the capability to analyze the data, identify trends and, ultimately, keep incidents from happening,” said Brian Davis, research fellow, University of Minnesota Department of Mechanical Engineering.
MnDOT wanted to improve the reporting system to inform the development and implementation of strategies that would reduce or mitigate work zone incidents. In addition to enabling workers to provide timely and accurate reporting from the field immediately after events occurred, the improved system needed to be simple enough to minimize worker distraction and also needed to interface with the existing database.
What Was Our Goal?
The goal of this project was to create a user-friendly tool that would allow highway workers to report intrusions in the field in real time. This data could then be used to inform the development of effective strategies that would optimize safety in road work zones.
What Did We Do?
Two smartphone app prototypes were designed for reporting incidents. One design used a drop-down menu for gathering incident information, which was similar to the design of the online reporting system. The second design used a radio button style for gathering information, similar to the paper form. After an initial round of testing, end users provided feedback and identified process issues to refine the design of the final app.
In response to user feedback, researchers added a progress bar to the app.
In a second round of testing, investigators explored different layouts, toggle switches instead of radio buttons and other features used in Apple-owned iOS apps. Testing was conducted in a videoconference with 10 MnDOT maintenance employees who were asked to enter data based on a previous motorist intrusion. While entering the information, employees were encouraged to provide feedback about the usability of the prototype as they navigated through the app and its features.
Training and a communications plan for the final app design selected were developed to raise awareness of the app and its purpose, educate users on its contents and functions, and increase their buy-in. Lastly, a framework for data analysis and an example report analyzing the existing data were also developed.
What Did We Learn?
By working iteratively with MnDOT maintenance workers and supervisors in developing the work zone intrusion mobile app, investigators were responsive to end user needs. In the initial round of testing, for example, users indicated a preference for radio buttons and improved “Back” or “Continue” buttons to accommodate smaller screens. Subsequent testing refined features and resulted in the removal of redundant questions.
“This reporting mechanism, when broadly adopted across MnDOT districts, will be invaluable to devising strategies to keep workers safe. We haven’t even come close to seeing the full value of this tool,” said Todd Haglin, emergency management and safety manager, MnDOT Office of Administration.
The final mobile phone app design includes the capacity to enter a short report for less severe intrusions, providing the date, time and location of the incident, and information about the incident severity, including whether it involved a risk to a flagger or crew member and if a crash or injury occurred. An affirmative answer to any of those questions prompts the user to complete the longer report, which requests information about:
- Driver behavior and vehicle actions that constituted the intrusion, type of vehicle(s) involved and the location of the intrusion in the work zone.
- Work zone, including its purpose, layout and on-site traffic control devices.
- Grade, alignment and condition of the road.
- Weather and lighting conditions at the time of the intrusion.
A narrative about the incident is required in the long report and optional in the short version. Phone location data is also collected with the user’s permission.
A communications plan includes six individual products such as infographics, training workshops and videos, each with objectives, message content and delivery methods or venues.
Finally, in addition to the initial analysis of existing data, a sample infographic and an analysis framework provide the basis for future reports. Suggested topics for data analysis reports include when intrusions occur and their consequences, safety equipment used in mitigating risks and work zone layout.
What’s Next?
MnDOT’s Office of Maintenance Operations will assume oversight of the work zone intrusion app’s implementation, including facilitating its use across the agency. The Office of Traffic Engineering will analyze and report the data, communicating its value to MnDOT staff.
Crossroads 