1. Beyond MMUCC – Updating Wisconsin’s Crash Report Form
Traffic Records Forum 2016
August 9, 2016
Steven Parker
IT Program Manager
Andrea R. Bill
Safety Program Manager
David A. Noyce
Director

2. Past
According to the CDIPG, one refrain commonly heard from police is that “crash forms are being completed just for insurance companies”
WisDOT MV4000 Instruction Manual
Primary training resource for WI officers
Last updated in 1998
Brief and vague concerning engineering fields
No baseline definition of when to flag hills or curves
Poor definition of traffic barrier
No discussion of roundabouts
Paper crash report backlogs in Texas. (GAO )
Paper Forms
Scantrons

3. Engineering Elements Data Quality Audit
Low accuracy for access control at partially controlled facilities indicates a lack of understanding for what qualifies as partial control
When hills or curves are present on at least one approach, when should they be marked?
Low traffic-way accuracy is a result of misunderstanding what constitute divided roadways and barriers
Roundabout-specific inaccuracies were especially noteworthy in the horizontal curve and traffic-way fields

4. Near Past Crash Elements and Attributes 2012 Brown County Sheriff,
La Crosse County Sheriff,
City of Madison,
City of Milwaukee,
Wisconsin State Patrol
Oneida Tribal Police, and
Analysts.

5. Crash Data Work Group
DMV
DSP
DTIM
DTSD
DBM
TOPS Lab

6. Present
Help Screens
TraCS has built-in help screens that can be accessed for a data field by pressing the <F2> key. Help is available for each of the forms in the suite.
The Help button on the toolbar brings up information about the TraCS software, in general.

7. National Perspective: Model Minimum Uniform Crash Criteria (MMUCC) FAST Act
110 Crash Data Elements
77 Collected From Scene
10 Derived
23 Linked
4 Categories
Crash Data Elements
Vehicle Data Elements
Person Data Elements
Roadway Elements
FAST Act
Safety Performance Measures
Over $60 million in funding

8. National Perspective: Crash Data Improvement Program (CDIP)
The Performance “Six Pack”
Timeliness
Accuracy
Completeness
Consistency
Accessibility
Integration
Personal Experience and following up
Traffic Safety Information Systems

9. Crash Database - Objectives
Implement the Revised Crash Form by January 1, 2017
Streamline Crash Data Processing
Modernize the Data Management System
Improve Crash Data Quality – MMUCC / MIRE
Take Full Advantage of the TraCS Location Dialogue Box (TLT)
Enhance Crash Data Access and Interoperability
Support More Frequent Updates to the Crash Form
Oracle Database 12c Enterprise Edition
TraCS Web Services
Web Based Resolve System

10. MMUCC Mapping process
NHTSA and the GHSA have put out literature on how to map MMUCC compatibility, as well as an excel spreadsheet tool to make the process easier.
This tool is divided into each of the 4 element types, and lists each MMUCC element with its corresponding attributes.
Next to each attribute is a box to input a 1 if the attribute maps, or a 0 if it does not.

11. MMUCC Mapping process
To get the final compatibility, each element is weighted the same for a category (crash, vehicle, etc.).
For example, C1-Case Identifier is weighed just as much as C2-Crash Classification, even though C1 only has 1 attribute in it and C2 has 5.
If an element attribute does map, next to that box is a field to put the corresponding attribute that maps from the state’s crash report. This process is repeated for each of the 110 data elements in MMUCC (collected, linked, and derived).

12. Mapping process
The tool has a sheet that displays the results, breaking them into 3 categories:
ALL 110 elements
Elements collected at the scene
Linked or Derived elements
The updated WI MMUCC compatibility:

13. Went Beyond MMUCC 4… Secondary Crashes Incident Management Motorcycle
Non Motorists
Citations for all persons
Truck/Bus/Hazmat

14. WisDOT Crash Database and Resolve System
DT4000, DT4002, DT3480
Crash Database (Oracle)
Crash Report Image Files
TraCS Web Services
Web Based Resolve System
Linkages to WisDOT DMV Systems
Data Extracts and External Interfaces
Linkages to Other Datasets

15. Impacts to Law Enforcement
TraCS Form Transmission Process
Automate Up Front Validation Steps
Requirement for Electronic Reporting
Maintain Communication & Feedback During Resolve Processing
TIME, Wisconsin.Gov Access Unchanged
Changes to Data Extracts, WisTransPortal
Weed out fields that had become obsolete and identify others that were not being collected (i.e. roundabouts or cell phone use)
Form is more intuitive and that there is a great savings at both the state and local level by gathering correct and accurate data
Easily describe what happened (i.e., cell phone usage, roundabouts, cross median crashes)

16. Broader Look Tried to simplify when possible
Working towards a change in PDO threshold
Parking Lot
Non-Domesticated Animal PDO crash
Unit Status
Hit and Run
Amendments
Fatal Supplement
Fatal Notifications
On Emergency
Driver Report Form – DT4002
No paper forms

17. Crash Database - Future
Improve Crash Mapping and Analysis Capabilities
Include Photos & Attachments to the Crash Report
Linkages to Federal Systems (FARS, FMCSA)
Linkages to External Data (EMS, Roadway)
Include Additional TraCS Forms
Research and Innovation
To enable analysis and decision making through downstream applications

18. Questions