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:

  • May 19 – Monthly server maintenance window.

  • May 15 – 2023 Finalization Window

Prioritized JIRA Issues and Enhancements

• 2023 Finalization

  • CRASHDB-1558 - Getting issue details... STATUS

  • Completed:

    • Edit checks, record updates completed

    • May 15 – Finalization Window, Extracts Generated

  • In Progress:

    • [CRASHDB-1623] 2023 Finalization - Crashes Having Late Fatality Withdrawals - Jira (atlassian.net)

    • May 19 – Processed two late withdrawals of 2023 fatalities

    • May 23 – Processed three late withdrawals of 2023 fatalities

  • Pending:

    • CRU Review and sign-off

    • Update WisTransPortal Crash Data

    • Generate Public Annual Extracts

• 2022 RP Re-Finalization

  • CRASHDB-1559 - Getting issue details... STATUS

  • Completed:

    • RP Records merged into final 2022 dataset

    • Final extracts provided to the CRU

    • RP Crash File for GIS RP Crash Map

  • Pending:

    • Update WisTransPortal Crash Data

    • Generate Public Annual Extracts

• JIRA In Progress

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

    • CRASHDB-989 - Getting issue details... STATUS   

    • Initial version on TST server environment

Purge and Archiving Processes

• Purge and Archive processes continuing to run smoothly.

• 1,103,748 total archived crashes of which 506,184 represent purged crashes (the archive adds approximately 13K crashes per month).  This includes 2,065,756 total image files.

HWYCLASS Working Group

• Next working group meeting Tuesday, May 28

• LINK-LINK vs. Route-Milepoint comparison for highway crashes (STN), preliminary analysis / questions for local road crashes (WISLR).

WisTransPortal / Community Maps

• Community Maps User Spring 2024 Group Meeting:  Wednesday, May 29

• Community Maps Flags Technical Documents: available on CM Help Page since March

Discussion:

• Adding the CM flags to the Extracts (single source of data)

• Crash Database and Resolve System – TRCC Upgrade Project

  • Year 1: 10/2024 – 9/2025

    • Project Planning and Coordination

    • MMUCC 6 Elements and Attributes

  • Year 2: 10/2025 – 9/2026

    • TraCS / Resolve Requirements

    • TraCS / Resolve Development – Phase I

  • Year 3:  10/2026 – 9/2027

    • TraCS / Resolve Development – Phase 2

    • TraCS / Resolve Testing and Acceptance

  • Year 4: 10/2027 – 9/2028

    • Rollout Planning and Outreach

    • TraCS / Resolve Rollout January 1, 2028

    • Post-Rollout Maintenance and Support

Crash Records Unit

Polly Ebbinger / Mike Satteson

Issue Resolution Summary

LEA Question Summary

The following LEA questions were addressed since the last workgroup meeting:

• Greyed out crash type box

  • Issue: LEA was trying to change a crash report from a standard crash to a lesser crash.

  • Resolution: Reiteration that this ability was removed with the recent TraCS update.

• Bus crash

  • Issue: How to enter multiple passengers.

  • Resolution: Pointed the agency to the F2 help regarding adding additional individuals as well as the only requirement being entering the injured passengers.

• Postal carrier van

  • Issue: How to select the correct body style

  • Resolution: Select the one that is most appropriate as there is no validation on this combination.

• Citations

  • Issue: Officer created citations prior to creating the crash report.

  • Resolution: Provided the F2 help document for adding crash number after the citations are created.

• Hit & Run:

  • Issue: Entering the H&R unit without all of the pertinent information.

  • Resolution: Provided direction for the requirements and “gotcha” entries that create issues.

• Non reportable crash

  • Issue: Agency wanted to know how to amend a non reportable crash; no change in reportability.

  • Resolution: While trying to determine why this was needed, the agency indicated that they were able to make the change; since this is non reportable, the issue was closed out.

• Restricted driver info

  • Issue: LEA requested information on restricting access to a juvenile driver’s information because of “threats” from a party related to the other driver.

  • Resolution (pending): The LEA was provided information related to open records requirements and some considerations regarding this situation. As they have not responded, this issue is currently still open.

DMV Systems and SR

Ken Matthews

Reference Point Coding

Ben Rouleau / Asadur Rahman

Crash Data Analysis and Reporting

Valerie Payne

Scheduled Topics and Briefing documents

Close

Informal Closing Discussion