2024-09-27, Crash DB Workgroup Meeting
- Michael Satteson
- Steven Parker
- Polly Ebbinger
Intro
Informal Opening Discussion
Arrivals and Departures
Bras Richter is the CRU’s newest member, an IS Business Automation Senior, filling the vacancy created when Soujanya departed.
.
Jacob Clausen has resigned to take a private sector job in Colorado.
Crash DB Systems Review
TraCS Systems and Crash Form development
Dave Malisch / Geri Polster
Fall Pack Release, second pack out for testing.
Get tables and F2 Help documents. By Thursday of next week.
TOPS Database and WisTransPortal
Steven Parker / Andi Bill
Maintenance Updates and System Stability
CRASHDB-1658: Server Maintenance, September 22
Configuration typo for a security path led to a temporary transmission issue in UAT.
CRUBIZ-1655: Purchases of Crash Reports through http://Wisconsin.Gov
Prioritized JIRA Issues and Enhancements
JIRA Completed
CRASHDB-1659: Resolve System Contact Information
JIRA In Progress
CRASHDB-1541: Duplicate Failure Message: Retransmission vs. Reuse
Pending CRASHDB-1570.
CRASHDB-1570: Pipeline work on SOAP and REST
Deployed TST and UAT to new DevOps environment.
CRASHDB-1637 – Resolve – 503 Error
No issues since moving PRD Resolve into the new DevOps environment last month.
JIRA Planning
2023 RP Refinalization
Purge and Archiving Processes
Purge and Archive processes continuing to run smoothly.
1,152,959 total archived crashes of which 542,592 represent purged crashes (the archive adds approximately 13K crashes per month). This includes 2,159,983 total image files.
HWYCLASS Working Group
Working group meeting Tuesday, September 24
Phase 2 Prototype Testing Rollup
Phase 3 Implementation Planning
WisTransPortal / Community Maps
Community Maps citations and warnings data layer in progress.
Working with BTO (AASHTOWare)
City of Madison (Citian)
Crash Records Unit
Brad Richter / Polly Ebbinger / Mike Satteson
Issue Resolution Summary
Issue Type | New since 8/23 | Resolved since 8/23 | Remaining |
|---|---|---|---|
Document # Reuse* | 41 | 44 | 11 |
Retransmissions | 55 | 55 | 0 |
Potential Duplicate | 1 | 0 | 1 |
LE Questions | 6 | 5 | 1 |
Informatica Data Catalog Project
The CRU has just started work with BITS and Informatica to catalog the crash database:
A critical goal of this project is to get our database into compliance with DOA Standards for data security classification. As part of this work, each field in the database will need to be assigned a security classification ranging from public to confidential.
But we intend to get much more out of this project.
Authoritative Field Documentation, which serves as the source for the TraCS F2 help and for the documentation provided to analysts and the public.
A data linage that maps the path and transformations of data fields as they move from TraCS to the Crash Database and Data extracts. Provide the whos, whens and hows of data changes and modifications
Metadata change management, allowing us to to provide the data stability needed for 5-year analyses but also to gracefully adapt the data to new and changing standards.
Fatality Case Management and Reporting
Out sole FARS analyst was on leave for the first half of September. This has put me too much is the weeds to provide a formal analysis and metrics. But I can provide some anecdotal highlights.
The Daily Fatality Report
The old access database is now fully relegated to legacy reporting. It is quite demanding to maintain. But we are keeping it alive to maintain reporting continuity as we develop new reports. We be changing delivery mechanisms. Starting on Monday, 30 September, reports will be distributed using Lyris rather than being manually setup and mailed through Outlook.
Cause of Death Review
We continue to push to obtain a confirmed cause of death for each fatality in our case management system as soon as is practical. We’ve set an internal goal of having confirmed cause of death for 95% of fatalities within 4 months of the death. This goal is structured to allow us to be in an excellent position to align FARS cases to state crash data for a given calendar year prior to state data finalization. This will be a challenging goal to achieve with our current capabilities. Obtaining wider access to DHS Vital Records Death Certificates would make this goal achievable and significantly decrease the time and effort required to confirm cause of death. We plan to track our performance and the resources required for this work to develop a justification for expanded access to these Vital Records data.
A Fort McCoy Fatal Crash, is it reportable?
On 8 September we received a fatal notification from the Fort McCoy PD of a crash that occurred at about 02:12 on the 7th at “GINGER RD\STH 21”. The source of the notification implied that this crash occurred on the fort, so we put the case under review rather than announcing it. Follow-up with the agency indicated that the crash occurred on the Fort McCoy Military Reservation but outside of the the fenced area of the fort. Depending upon how one interprets statutes and guidance, this may or may not have been a motor vehicle traffic crash fatality.
By my interpretation of ANSI D16 this would be A FARS reportable crash, but the state maps strongly imply that this would not be traffic crash by State standards. We are consulting with NHTSA FARS experts to get a ruling from them on whether this was a trafficway or private way crash.
DMV Systems and SR
Ken Matthews
Reference Point Coding
Ben Rouleau / Asadur Rahman
08/22-09/25 period summary
Jacob: 173 (last coded 09/03)
Jack McCaffrie: 2,728
Lukas Wellenstein: 3,848
Tristan: 624
Thresa Majeski: 1,731
Total: 9,101
RP coding needed - 2024: 11,533.
Crash Data Analysis and Reporting
Valerie Payne
Scheduled Topics and Briefing documents