1 / 22

Crash Upgrade: Lessons Learned

This article discusses the lessons learned from crash data management and the necessary upgrades for a more efficient and accurate traffic safety system. It highlights the challenges faced by law enforcement, outdated crash report forms, and the importance of modernizing data management systems. The article also explores the impacts of data integration and improved reporting on various stakeholders.

ssalas
Download Presentation

Crash Upgrade: Lessons Learned

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Crash Upgrade: Lessons Learned Chokkalingam Muthumari CRU Supervisor WisDOT BOTS Steven T. Parker, Ph.D. IT Program Manager UW-Madison TOPS Lab Andrea R. Bill Safety Program Manager UW-Madison TOPS Lab

  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-10-454)

  3. 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.

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

  5. 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.

  6. National Perspective: Crash Data Improvement Program (CDIP) • The Performance “Six Pack” • Timeliness • Accuracy • Completeness • Consistency • Accessibility • Integration Traffic Safety Information Systems

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

  8. 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.

  9. 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).

  10. 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:

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

  12. Rollout • Training across the state • 100% Electronic • Communications • Email • Newsletters • Stakeholder Groups • Conferences • Being Available • On Time Under Budget • High Profile Success Story

  13. 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

  14. System Modernization • Data Dictionary • System Architecture • Server Infrastructure

  15. Web Services • TraCS - DT4000, DT3480 • Driver Report - DT4002 • Driver Record, WIN, TIME • FMCSA- Safety Net • Future: National FARS TraCS Driver Report DMV TIME WIN TOPS Lab WisDOT

  16. Resolve System • Web Based • Multiple Roles • CRU • FARS • DMV • FMCSA • Risk Management • Version History • Enhanced Editing & Validation • Enhanced Reporting

  17. Data Integration

  18. 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 • Easily describe what happened (i.e., cell phone usage, roundabouts, cross median crashes)

  19. Impacts to Others • Subscription Emails • General Crashes • Police Departments • Maintenance Supervisors • FMCSA • Others? • Automation in Customer Create • Timeliness - nightly • Accuracy • Completeness

  20. Lessons Learned • Communication • Documentation • Streamlining processes • Continued Training • There’s a solution (immediate and future)

  21. 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

  22. Thank You! crash.database@dot.wi.gov http://www.topslab.wisc.edu/programs/safety/ projects/Crash_Database_Improvement/

More Related