...
Soujanya Jarabana and Mike Satteson
Questions from Law Enforcement Agencies
...
CRU business unit provided email and remote support to law enforcement agencies to resolve Validation errors in the DT4000 crash form.
Received 9 LEA questions in the last 4 weeks with 2 Hit and Run Crashes and 1 about Crash Diagram Tool.
Transmission failures:
We addressed 17 transmission failures between Feb 24th until now after providing solution to the agencies.
7 are transmitted
6 are transmitted as other Document (Duplicate Document Number)
3 are pending with agencies
1, CRUBIZ-11, was abandoned (. This was an Invalid EMS Agency ID )failure of a 2021-09-23 , having an initial failure date of 2021-09-30.
About half of our transmission failures are caused by document number reuse, a failure mode that we began tracking at the strt of this year. Of these about half are from one machine at one agency. We are working with Badger TraCS to try to get that machine reconfigured to avoid the document number reuse.
DT4000 Fatal Crashes
...
Quality Check process for DT4000 fatal crashes is performed which comes in Resolve. The process starts with creating a Jira issue for DT4000 basic check and then and assigned to the FARS team,
FARS team performs quality check for
All Fatal Injuries Shown
DT3480 Available
Diagram Good
Narrative Good
Sequence of Events Good
Based on the results of the quality check process the agency is contacted to amend the crash report.
Since the start of this process 239 Fatal Crashes have been reviewed, 9 fatal crashes are under agency review.
Tracking is done for missing DT4000 fatal crashes, and the agency is contacted when a 3-week due date is met from the crash date.
Currently, we are missing 1 crash from Racine PD
Enhancements to Crash Database & Resolve System
Currently in development phase is search by Agency in Resolve System and bug fixes to the System Stability tool.
Jira Legacy server System JIRA serverId 27e84956-8aca-34a6-b686-31eab275489e key CRASHDB-1185 In the last four weeks, 2 change requests were submitted which includes:
1 change request for monthly server maintenance
1 change request for adding new features to System Stability
Partial DROC Outage, 2023-03-22/23 (problems submitting multi-unit crashes)
On Wednesday, the BITS DROC team deployed a new version of this application to address address issues with the state of issuance field that occur in some cases when Apple devices are used to complete the form. On Thursday morning the CRU began receiving calls from the public complaining about difficulties completing DROC crashes involving 2 or more units. On Thursday afternoon, the BITS DROC team made an emergency change to revert to the previous DROC version. The CRU was able to reproducer the issue in production when it was live, but could not do so in the test environment. Failure analysis from the BITS DROC team is pending.
DMV Systems and SR
Ken Matthews
Reference Point Coding
Ben RouleauAsadur Rahman
Erickson coded: 556
Jacob coded: 1,409
Total: 1,965
Erickson, our LTE RP coder had to cut back on his hour over the past 2 weeks because he had nearly exhausted the hours under his initial appointment. Renewal of his appointment proved difficult and had to be resolved at the Bureau Director level. But we did get renewal, effective 2023-03-27.
Crash Data Analysis and Reporting
...
Scheduled Topics and Briefing documents
Informal discussion of hosting our annual crash data on WisDOT GIS Open Data as mapped data with a selection of fields and as tabulated dataset in the format that had been provided as a piad subscription service. The subscription service has been discontinued, and the data sets are now available on Box.
Interim Data package, WI_Annual_Crash_Data_Flyer.pdf
Identify the attributes to be associated with the mapped data when hosted, Jacci