Andrea R Bill Safety Program Manager UWMadison TOPS Lab billwiscedu Past Paper crash report backlogs in Texas GAO10454 According to the CDIPG one refrain commonly heard from police is that crash forms are being completed just for insurance companies ID: 794579
Download The PPT/PDF document "The Continuous Pursuit of Quality Crash..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
The Continuous Pursuit of Quality Crash Data
Andrea R. BillSafety Program ManagerUW-Madison TOPS Labbill@wisc.edu
Slide2Past
Paper crash report backlogs in Texas.
(GAO-10-454)
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
Slide3Past
Crash Elements and Attributes2012Brown County Sheriff,La Crosse County Sheriff, City of Madison, City of Milwaukee,
Wisconsin State PatrolOneida Tribal Police, and
Analysts.
Slide4Present
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.
Slide5National Perspective: Crash Data Improvement Program (CDIP)
The Performance “Six Pack”TimelinessAccuracyCompletenessConsistencyAccessibility
Integration
Traffic Safety Information Systems
Slide6Crash Database - Objectives
Implement the Revised Crash Form and Driver Report Form January 1, 2017Streamline Crash Data ProcessingModernize the Data Management SystemImprove Crash Data Quality – MMUCC / MIRETake Full Advantage of the TraCS Location Dialogue Box (TLT)Enhance Crash Data Access and Interoperability
Support More Frequent Updates to the Crash Form
Oracle Database 12c Enterprise Edition
TraCS Web Services
Web Based Resolve System
Slide7Slide8Rollout
Training across the state100% ElectronicCommunicationsEmailNewslettersStakeholder GroupsConferencesBeing AvailableOn Time Under BudgetHigh Profile Success Story
Slide9WisDOT Crash Database and Resolve System
DT4000, DT4002, DT3480Crash Database (Oracle)Crash Report Image FilesTraCS Web ServicesWeb Based Resolve SystemLinkages to WisDOT DMV Systems
Data Extracts and External InterfacesLinkages to Other Datasets
Slide10Slide11Crash Data Tools
Resolve SystemWeb ServicesEmail SubscriptionsCommunity MapsPredictive Analytics
Analysis
Crash Database
Timeliness
Accuracy
Completeness
Consistency
Accessibility
Integration
Slide12Resolve System
Web BasedMultiple RolesCRUFARSDMVFMCSARisk ManagementVersion HistoryEnhanced Editing & ValidationEnhanced Reporting
Slide13Web Services
TraCS - DT4000, DT3480Driver Report - DT4002Driver Record, WIN, TIMEFMCSA - Safety NetNHTSA FARS EDTTraCSDriver Report
TOPS Lab
WisDOT
DMV
TIME
WIN
Slide14NHTSA FARS EDT
Nightly transmissionIncludes records for all reportable crashesEDT based on defined rules and data typesStreamlines processing of FARS cases
Slide15Email
Subscriptions Fatal SupplementGovernment Property CrashesWork Zone CrashesDaily Fatality ReportFMCSAPolice Agencies
Slide16Work Zone Crash Report
Slide17Community Maps
Major upgrade rolled out in January 2018Crash data imported on a nightly basisIncludes all reportable crashesMap locations taken directly from crash report (TraCS / TLT)Public facing interface with basic crash informationPassword protected interface with additional detail and access to DT4000 crash reportsUsed extensively across Wisconsin at the county Traffic Safety Commissions
Slide18Impacts to Law Enforcement
TraCS Form Transmission ProcessAutomate Up Front Validation StepsRequirement for Electronic ReportingMaintain Communication & Feedback During Resolve ProcessingTIME, Wisconsin.Gov Access UnchangedChanges 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
Tools back in their hands
Slide19Timeliness—Why It Matters
A key NHTSA Crash Data Quality MeasureWI Stat 346.70(2) requires that a written report be made within 10 days of the crashTimely Data is important and critical to certain applications, particularly incident response, roadway repair, predictive analyticsCrash Reports are available to the public immediately after transmission. Motorists call the CRU if their report is unavailable shortly after a crash
Slide20Timeliness-Days to Transmission
Parameter
2015
2016
2017
2018 (
Mean10.810.88.77.21st Quartile3322
Mode6644
3rd Quartile
11
11
9
8
Slide21Timeliness—Factors/Opportunities
Ease of Form CompletionComplexity of Crash ScenarioAgency PoliciesEase of AmendmentCompliance with StatutesPublic and Peer Influence
Slide22Timeliness—Strategies
Improve the form to shorten completion time—simplicity, clarity, flow. Validations are particularly ripe for improvementA 5 minute reduction in completion time will save about 12,000 officer hoursStrategically offer short forms—currently "Car-Deer", perhaps Parking Lot/Private PropertyWork with Agencies to streamline reporting; Kenosha PD shows that mostly same shift transmission is feasible.
Slide23Timeliness—More Strategies
Provide completion aids for difficult but common crash and unit scenarios. Hit and Run unit completion is a notable success of this sort.Default or replace fields via linkages—Roadway information (requires consistent, reliable TLT location), Drug & Alcohol test results.Institute process monitoring to identify and solve issues before they become problemsOther Ideas? Please tell us!
Slide24CRU and Data Quality—1
Develop and refine the crash data model, ensuring that it is consistent with statutes, standards and the department’s business needs. Work with TraCS and TOPS, the implementers of the crash data model, to ensure that this model is properly represented in the crash forms and the crash database.Work with Law Enforcement Officers to improve data clarity and form completion efficiency.
Slide25CRU and Data Quality—2
Monitor for completeness and consistency.Collaborating with BOTS, develop crash data extracts and reports to meet the data needs of Agencies, the DOT, researchers, regulators and the public.Identify and develop data linkages that will improve and supplement crash dataBe alert for questions that signal data issues, responding quickly to minimize their impact.
Slide26Slide27Slide28KABCO
MAIS
O
C
B
A
K
1 (minor)
20,886 (91.5)
56,548 (87.9)
47,706 (75.7)
7,514 (35.2)
0 (0)
2 (moderate)
1,778 (7.8)
6,538 (10.2)
11,466 (18.2)
6,142 (28.8)
0 (0)
3 (serious)
92 (<1)
844 (1.3)
2,759 (4.4)
4,567 (21.4)
0 (0)
4 (severe)
52 (<1)
339 (<1)
1,042 (1.7)
2,683 (12.6)
0 (0)
5 (critical)
6 (<1)
31 (<1)
76 (<1)
406 (1.9)
0 (0)
6 (maximum-fatal)
1 (<1)
5 (<1)
3 (<1)
16 (<1)
1,184 (100)
Total
22,815
64,305
63,052
21,328
1,184
KABCO
MAIS
O
C
B
A
K
1 (minor)
3,445 (95.6)
5,488 (90.1)
6,408 (79.6)
683 (26.2)
0 (0)
2 (moderate)
138 (3.8)
507 (8.3)
1318 (16.4)
948 (36.3)
0 (0)
3 (serious)
18 (<1)
85 (1.4)
281 (3.5)
821 (31.5)
0 (0)
4 (severe)
0 (0)
5 (<1)
25 (<1)
98 (3.8)
0 (0)
5 (critical)
1 (<1)
7 (<1)
17 (<1)
60 (2.3)
0 (0)
6 (maximum-fatal)
0 (0)
0 (0)
0 (0)
0 (0)
127 (100)
Total
3,602
6,092
8,049
2,610
127
Slide29check
2017
2018
2019
BAC Result Suspiciously High
113
151
59
BAC Done But Result Unavailable
3081
2999
1715
Check Autocycles
0
0
47
Pedalcycle Crash Type Without Cyclist
2
0
0
Citations: Unit vs. Person Counts Disagree
0
0
0
Citations: Irregular Person Numbering
462
419
246
Citations: Issued to Passenger
159
100
55
Citations: Unit Totals, DB/PDF Mismatch
291
121
20
Date vs. Month or Day of Week Contradiction
2
0
0
Crash Type not Reflected in Vehicle Events
24940
25075
11399
Slide30Modernization
How do you keep champions interested?How often do you update?Communication of changes?Continuous feedback?Coordination between agencies (i.e., TRU)
Slide31Lessons LearnedCommunication
DocumentationStreamlining processesContinued TrainingThere’s a solution (immediate and future)
Slide32Crash Database - Future
Improve Crash Mapping and Analysis CapabilitiesInclude Photos & Attachments to the Crash ReportLinkages to External Data (EMS, Roadway)Include Additional TraCS FormsResearch and InnovationTo enable analysis and decision making through downstream applications