Intro

Informal Opening Discussion

Crash DB Systems Review

TraCS Systems and Crash Form development

Dave Malisch / Geri Polster

TOPS Database and WisTransPortal

Steven Parker / Andi Bill

Maintenance Updates and System Stability

• Completed Maintenance Windows:

  • March 24 – Monthly server maintenance window.

  • April 21 – Monthly server maintenance window.

Prioritized JIRA Issues and Enhancements

• In Progress

  • 2022 RP Re-Finalization

    • https://wi-state-patrol.atlassian.net/browse/CRASHDB-1559

    • Re-Finalization Completed on April 24

      • RP Records merged into final 2022 dataset

      • Final extracts provided to the CRU

    • Next Steps:

      • RP Crash File for GIS RP Crash Map

      • Update WisTransPortal Crash Data

      • Generate Public Extracts

  • 2023 Finalization

    • https://wi-state-patrol.atlassian.net/browse/CRASHDB-1558

    • Reviewing Process Documentation, Edit Checks

  • CRASHDB-989 - RP Coding - Implement Omit List Functionality in the Crash DB

    • https://wi-state-patrol.atlassian.net/browse/CRASHDB-989   

Purge and Archiving Processes

• Purge and Archive processes continuing to run smoothly.

• 1,092,921 total archived crashes of which 498,269 represent purged crashes (the archive adds approximately 13K crashes per month).  This includes 2,045,165 total image files.

HWYCLASS Working Group

• Continuing analysis of the LINK-LINK method for highway crash roadway attribute assignments in comparison to a route-milepoint method based on spatial analysis.

WisTransPortal / Community Maps

• CRASHDB-1607 – WisTransPortal - Crash Reports Retrieval - Customer Number Search:

• https://wi-state-patrol.atlassian.net/browse/CRASHDB-1607

Crash Records Unit

Polly Ebbinger / Mike Satteson

*NOTE: The Document Reuse issues are trending up over last year.

LEA Questions since last workgroup meeting:

• Hit & Run - LE requested clarification as to why LE can submit a H&R report with very little information but a DROC requires at least some identifying information about the H&R unit.

• Amendments - LE wanted to know how to change information on a crash report. They were provided with basic instructions for creating the amended report.

• Reporting Threshold - LE wanted to know how to change the Reporting Threshold (FMCSA) field. They were given the information that this field is calculated based on whether the crash report meets the threshold criteria so there is no way to manually change it.

• Snowplow – LE asked how to get a report involving a snow plow and a parked car to validate. They were given the direction to submit as non-reportable.

Miscellaneous:

We received several requests from Citations & Withdrawals for purged crash reports. We worked with the TOPS Lab to add the Customer Number to the existing WisTransPortal Data Retrieval feature in an effort to provide more efficient self-service for these types of requests.

Data Finalization

2022 Re-Finalization

https://wi-state-patrol.atlassian.net/browse/CRASHDB-1559

2022 RP Coding has been completed and RP Data incorporated into the 2022 data that had been finalized in May 2023. Comparisons of these datasets show no differences other than newly provided RP data and some record timestamps. These re-finalized data are ready to be deployed.

2023 Finalization

As we did last year we are scheduling 2 finalizations, a primary on 2024-05-15 and a secondary on 2024-05-22. (Last year we successfully finalized on the primary date.) We expect to extract, package and test during the remainder of the week following finalization and expect to deploy extracts in time for analysts to begin their work with them at the start of the following week.

We have begun to create the Finalization of 2023 Crash Data (Draft) report. So far is has preliminary 2023 crash statistics akin to those provided in Final year-end crash statistics.

Fatalities and Finalization

In recent years, getting to the final fatality numbers has been a concern for the scheduling of finalization as the FARS team has been working on the analysis and coding of that years crash data. This remains a concern for this year. It has been typical for some crash fatalities to be found not to count as reportable once they come under greater scrutiny by the FARS team. That remains a problem for this year. I believe that we can improve this situation by adopting systematic review of cause of death information of crash fatalities. The current process is essentially manual and historically has not been especially systematic. We have begun to develop more systematic work practices for both cause of death and crash related factors that affect fatal crash reportability. Automation of checks between monthly death certificate data and FARS cases is yet to be done but should be achievable. Even more could be achieved with data and process improvements to death certificate data we receive from Wisconsin DHS Vital Records. But past experience indicates that there are considerable bureaucratic barriers to changes in these data.

Edit Checks and Finalization

With possibly one exception, we expect to be able to clear all of the critical edit checks prior to finalization. The exception is that we may not have death dates for all fatalities. Some of the missing dates of death are for individuals who survived the crash and were transported out of state for medical treatment.

We have not had the resourced to pursue non-critical but important edit checks as we have in the past. I expect our performance on those checks to be poorer than it has been over the past several years.

FARS Systems Status

Cases Without Crash Reports

There are currently 11 2023 fatal DOT crashes in our case management system that we have not yet received a crash report for:

About half of these are recent enough to not be of particular concern. But the Milwaukee PD backlog is something that we would like to clear up. The CRU has made repeated contacts with the Milwaukee PD to try to get these report transmitted.

The Daily Fatality Report

Currently the Daily Fatality Report depends upon an old Access database that had been used for case management. It is prone to failure, and it is not uncommon to need to put several hour of work into addressing failures so that we can get the daily fatality report out. We’d like to retire this tool from case management duties and use it for reporting only as we develop replacement means of creating reports.

DMV Systems and SR

Ken Matthews

Reference Point Coding

Ben Rouleau / Asadur Rahman

Crash Data Analysis and Reporting

Valerie Payne

Analysts to review data requests with a SharePoint tool

Scheduled Topics and Briefing documents

Close

Informal Closing Discussion