AASHTOWare Safety Powered by Numetric

Data Requirements

The AASHTOWare Safety platform utilizes data from various data sources, including crash, vehicle, occupant, and roadway data. Data from existing databases maintained by the agency is supplied to AASHTO’s partner, Numetric, Inc. who will conduct Extract, Transform and Load (ETL) processes to cleanse, unify, and manage the data inputs for use in the AASHTOWare Safety platform.

Data varies from agency to agency, and available data will continue to evolve and expand. The data needs for the AASHTOWare Safety platform are divided into three general categories: Configuration data, required data, and supplemental data.

Configuration Data

The purchasing agency will be provided with a number of default data values, which can be customized to meet the specific needs of that agency. These configurable data points can be customized at any point:

• Countermeasure Logic: AASHTOWare Safety Segment Analytics analyzes crash data (manner of collision, road conditions, etc.) and asset data (signage, rumble strips, etc.) to recommend treatments that mitigate crashes based on the countermeasure logic. Countermeasure Logic is required for use of the Safety Analysis application and provides additional value to the Network Screening, and Crash Query applications.
• CMF Values: CMF values are used in conjunction with the various calculations to estimate the effectiveness of a particular safety treatment. CMF Values are required for the use of the Safety Analysis application.
• Calculations: AASHTOWare Safety utilizes various calculations throughout the analytics performed by the applications within the platform. Calculations are utilized in the Crash Query, Network Screening, and Safety Analysis applications.
• Cost Defaults: The cost defaults pertain to each type of crash severity. These cost defaults are critical when calculating the benefit and benefit-cost equations across a segment of road or intersection, as well as various other calculations throughout the AASHTOWare Safety platform. The cost defaults are utilized in the Crash Query, Network Screening, and Safety Analysis applications.
• Discount Rate: The discount rate is applied to the benefit calculation to convert the costs and benefits at different points in time of the crashes into a single time dimension. The discount rate essentially denotes the change in money value across a time period.
• Calibrated SPF Values: Because SPFs are developed using data from specific locations at a specific period in time, it is necessary for each agency to provide state-specific, calibrated SPF values. SPF Values are used to calculate Crash Ratio in Network Screening—In the event that an agency cannot provide their calibrated SPF values, this calculation will not be provided in the Network Screening application.

Required Data

• Crash Data: Crash ID, Crash Date, Severity, Manner of Collision, Route IT, Milepoint, Latitude, Longitude, Number of Vehicles.
• Segment Data: Segment ID, Route ID, Route Direction, BMP, EMP, Segment Geometry. In order to run a segment analysis, AASHTOWare Safety uses a segment dataset provided by the agency.
• AADT Data: AADT, Route ID, BMP, EMP
• Intersection Data: Intersection ID, Route ID, BMP, EMP, Intersection Geometry. In order to run an intersection analysis, AASHTOWare Safety uses an intersection dataset provided by the agency.
• Vehicle Data: Crash ID

Supplemental Data

The AASHTOWare Safety platform is capable of supporting most other Vehicle, Roadway, or Model Inventory of Roadway Elements (MIRE) asset data that can be provided by the purchasing agency. Any additional data provided will provide further depth of analysis and additional filtering capabilities to the AASHTOWare Safety applications.