FHWA and NJDOT held a series of three Local Safety Peer Exchanges for municipal and county representatives to discuss local initiatives that demonstrate best practice in addressing traffic safety. The third of these peer exchanges was held on March 26, 2019. Topics discussed included NJ safety performance targets, use of Safety Voyager, substantive vs. nominal approaches to design, systemic vs. hot spot approaches to safety, and discussion of FHWA safety countermeasures, among others.
NJDOT is investigating a powerful set of tools to more effectively manage New Jersey’s roads and highways. The agency has been piloting a study of Safety Analyst, a software package used by state and local highway agencies to identify highway safety improvement needs and projects for funding. The New Jersey State Transportation Innovation Council (STIC) applied Federal Highway Administration’s STIC Incentive Program funding to purchase the Safety Analyst license and service units from AASHTOWare. Following the kickoff and first year, NJDOT has continued to fund the project through FHWA’s Highway Safety Improvement Program (HSIP).
According to AASHTOWare, Safety Analyst helps agencies “proactively determine which sites have the highest potential for safety improvement, as opposed to reactive safety assessment done conventionally” (SafetyAnalyst.org). The software automates procedures and assists agencies to implement the six main steps of the highway safety management (HSM) process—network screening, diagnosis, countermeasure selection, economic appraisal, priority ranking, and countermeasure evaluation. Safety Analyst features four tool modules to perform the six HSM steps:
- Module one utilizes the network screening tool and identifies sites with potential for safety improvement
- Module two provides the diagnosis and countermeasure selection tool, which establishes the nature of accident patterns at specific sites
- Module three includes the economic appraisal and priority ranking tool, which evaluates cost considerations of countermeasures for a specific site
- Module four provides the countermeasure evaluation tool, which allows users to conduct before and after evaluations of implemented safety improvements
A detailed explanation of the benefits and capabilities of these four modules can be found in a series of white papers available from AASHTOWare.
NJDOT’s plans for using Safety Analyst
After receiving funds for Safety Analyst, NJDOT began a pilot study in Burlington County using the software. The objective of this study is to determine a methodology for meeting statewide goals. Items under review include implementation methodology (i.e., the manner and locations of data collection) and the resource requirements (i.e., the time, effort, and cost of implementing the software). NJDOT plans to use the software to more efficiently allocate its resources, time, and funds to improve the state’s roadways. Previously, NJDOT screened roads by identifying equivalent property damage, based on average frequency and severity of crashes and, depending on the project list, other factors such as annual average daily traffic and bicycle/pedestrian generators. Using Safety Analyst, NJDOT anticipates identifying needed road improvement more comprehensively using additional variables, such as roadway volume and characteristics, driveway density, and lane widths.
According to NJDOT Bureau of Transportation Data and Support’s Peter Brzostowski, who is working with the Bureau of Data and Safety, the agency is exploring other innovative ways to gather data for Safety Analyst. Leading ideas include:
- Encouraging collaboration among several NJDOT Bureaus for data collection, including Traffic Engineering, Mobility and Systems Engineering, and Access Management
- Employing monitoring systems to capture data, e.g., using existing/new cameras and radar monitoring
- Utilizing Model Inventory of Roadway Elements (MIRE) (i.e., the FHWA Roadway Safety Data Program’s recommended list of roadway and traffic elements critical to safety management)
- Developing official NJDOT policy for data collection standards
Who’s using Safety Analyst?
State transportation departments and partner educational institutions can use Safety Analyst. At least eleven U.S. states have Safety Analyst licenses—Arizona, Illinois, Kansas, Kentucky, Michigan, Missouri, Nevada, New Hampshire, Ohio, Pennsylvania, and Washington, as well as Ontario, Canada. Some examples of its use include:
- Ohio DOT employed their Safety Analyst model to develop the Access Ohio 2040 Long-Range Transportation Plan, which utilized crash data from the statewide AASHTOWare Safety Analyst model to predict the future safety impacts of alternative networks.
- Michigan DOT is using Safety Analyst and GIS tools to develop a work-order-based maintenance management system and is exploring how to integrate new data collection tools, such as Light Detection and Ranging, or LIDAR, into its use of the software. See this MDOT case study for more information.
- At least eight universities, including United Arab Emirates University, have educational licenses to use Safety Analyst.
The Safety Analyst software tool requires access to a minimum set of data elements including roadway segment characteristics, intersection characteristics, ramp characteristics, and crash data. Agencies or institutions that do not have the ability to collect the minimum data will not be able to utilize Safety Analyst.
According to AASTHOWare’s project manager, Vicki Schofield, the states that have been part of the Highway Safety Improvement System, a multi-state database that contains crash, roadway inventory, and traffic volume, typically have sufficient data resources to utilize the Safety Analyst software. She noted, however, that “all states should be using Safety Analyst or something as robust and researched.” She offered that Safety Analyst is an ideal tool to begin to evaluate the data, even if a state has not completely collected the system data.
How states can begin implementing SafetyAnalyst
Ms. Schofield explained that to implement Safety Analyst effectively, states should work in partnership with other state and federal agencies to assign roles and responsibilities and leverage expertise and capacity. For example, the state transportation planning office can be used to collect roadway and attribute data; the state enforcement office (i.e., Division of Highway Traffic Safety in New Jersey) to compile crash data; the state IT office to manage secure access to databases; and the FHWA division office to connect the state agencies with other resources.
With the Safety Analyst tool, a state will be able to efficiently perform highway safety management—a data-intensive and statistically complex process—to better predict long-term levels of safety at various locations. The tool supports more effective decision-making and provides justification for expenditures of Highway Safety Improvement Program funds, resulting in greater benefits for New Jersey residents and drivers from every dollar invested.
According to Ms. Schofield, the cost for purchasing the software is relatively minor and the primary barrier to implementing Safety Analyst is the time it takes to ready the data-intensive tool for use. Regional or local universities may be able to help expedite implementation by performing tasks that a transportation agency cannot and to help ensure integrity of the tool.
The NJDOT Bureau of Transportation and Support reports that work on the Safety Analyst Pilot Study is almost complete. The Pilot Study is expected to provide information on areas that need to be addressed when developing a full scale contract for the implementation and development of Safety Analyst on a statewide level. The goal will be to maximize the benefit of Safety Analyst to NJDOT and to provide the necessary structure for a sustainable future for the program.
AASHTOWare. 2010. SafetyAnalyst: Software Tools for Safety Management of Specific Highway Sites:
- White Paper for Module 1—Network Screening
- White Paper for Module 2—Diagnosis and Countermeasure Selection
- White Paper for Module 3—Economic Appraisal and Priority Ranking
- White Paper for Module 4—Countermeasure Evaluation
Brzostowski, P. 2017. AASHTOWare Safety Analyst. Presentation to the New Jersey State Transportation Innovation Council. Winter Meeting.
Harwood, D. W., Torbic, D. J., Richard, K. R., & Meyer, M. M. 2010. SafetyAnalystTM: Software Tools for Safety Management of Specific Highway Sites. FHWA-HRT-10-063. Turner-Fairbank Highway Research Center.
LiSanti, D., and C. Trueman. 2018. CIA Safety Team. Presentation to New Jersey State Transportation Innovation Council. Summer Meeting.
LiSanti, D., and K. Skilton. 2018. CIA Safety Team. Presentation to New Jersey State Transportation Innovation Council. Fall Meeting.
FHWA and NJDOT are holding a series of three Local Safety Peer Exchanges for municipal and county representatives to discuss local initiatives that demonstrate best practice in addressing traffic safety. The second of these peer exchanges was held on June 13, 2018. Topics discussed included NJ safety performance targets, use of Safety Voyager, substantive vs. nominal approaches to design, systemic vs. hot spot approaches to safety, and discussion of FHWA safety countermeasures, among others. The third event will be held in Fall 2018.
FHWA and NJDOT are holding a series of three Local Safety Peer Exchanges for municipal and county representatives to discuss local initiatives that demonstrate best practice in addressing traffic safety. The first peer exchange was held on December 6, 2017. Topics discussed included NJ safety performance targets, use of Safety Voyager, substantive vs. nominal approaches to design, systemic vs. hot spot approaches to safety, and discussion of FHWA safety countermeasures, among others. Two more events will be held in 2018.