1 / 16

TR1-1051-301: Web Based Crash Reporting and IDOT Data Integration Project

TR1-1051-301: Web Based Crash Reporting and IDOT Data Integration Project. Abraham Emmanuel Chicago Department of Transportation. Project Goals. Improve timeliness, completeness and accuracy of traffic crash data thru: Electronic reporting of crash data

river
Download Presentation

TR1-1051-301: Web Based Crash Reporting and IDOT Data Integration Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TR1-1051-301: Web Based Crash Reporting and IDOT Data Integration Project AbrahamEmmanuel Chicago Department of Transportation

  2. Project Goals Improve timeliness, completeness and accuracy of traffic crash data thru: • Electronic reporting of crash data • Integration of Chicago crash data with IDOT • Real-time validation of crash reports

  3. Source of All Crash Statistics • Over 90% of Chicago crashes are currently reported on paper forms (SR1050)

  4. Paper Based Reporting has Lead to Significant Data Quality Issues Study conducted by CDOT in 2008 showed that 99% of the Chicago traffic crash data contained significant quality issues

  5. Three Categories of Errors Contribute to Poor Crash Data Quality Incomplete and Inaccurate information on the crash report Keying in errors. Not all records keyed in Inconsistent standards used in developing stats Collection Recording Reporting The goal of this project is to eliminate the errors in data collection and recording

  6. Chicago Crash Data Life Cycle By a Police Officer at the Scene or at the Police Station Collection Recording Reporting By a Data Entry Operator at the CPD Headquarters By a Statistician or Data Analyst

  7. Paper Based Reporting Issues • Has no means to validate codes or cross check with related information • Cannot prevent blank fields • Up to 6 months lag in keying-in to a database • Duplication of data entry efforts at IDOT and City • Errors and omissions when keying-in the data on paper to a database

  8. Paper Based Reporting Issues • Some crash reports lost before it is keyed in • IDOT reviews crash reports and make corrections before data is keyed whereas the Chicago crash data is never validated or corrected • Many fatal crashes not available in the Chicago database. Crashes which are also criminal incidents cannot be keyed in as both an auto incident and a criminal incident

  9. For Safety Improvement Decisions Engineers need to know: • Where the crash occurred • What type of crashes are occurring and why • Are there locations that need immediate attention • Are there traffic crashes at a location that can be prevented • What is the result of a crash mitigation effort • What is the general trend in traffic crashes

  10. Crash Data Quality Improvement Efforts Electronic reporting. Validate data at the time of data entry. Eliminate the separate data entry process Standardize Reporting practices Collection Recording Reporting Database

  11. Electronic Reporting • Data collection and recording combined into a Web based crash reporting system • Eliminate data entry at the CPD Headquarters • Data entry and validation at the same time • Electronic crash diagramming tool • Incorporate workflow • Real-time data entry avoid delay in recording • Reduced time for clearing the crash scene

  12. Integration with External Systems • Integrate with external systems for faster and accurate data collection • SOS / LEADS • Drivers License Reader • GPS Based Location Identification • City and State can exchange data easily • Integrated single data source vs. two separate data sources • Open for use by all Illinois Police agencies

  13. Implementation Plan • Make crash reporting a component of the R-Case comprehensive case management system being developed at the Chicago Police. • R-case is capable of collecting people, vehicle and property specific information. Adding crash specific fields to the R-Case system provide most straight forward implementation and at the same time we can leverage existing systems and technology.

  14. Progress to Date • Initial system design and concepts Developed • Engaged a vendor (Oracle) • 60% of the work completed for the diagramming tool • R-Case development and phased implementation continuing at CPD

  15. Action Plan for Next Year • Interface with IDOT crash database. • Establish systems for synchronizing the databases at Chicago and Springfield. • Integrate legacy data. • Testing & Training • Go Live (fall of 2012)

  16. Questions? Contact Info: Abraham Emmanuel Chicago Department of Transportation aemmanuel@cityofchicago.org (312) 742-1362 Jacqueline Frausto Chicago Police Jacquelyn.Frausto@chicagopolice.org

More Related