170 likes | 185 Views
Development of the 2005 Crash Report Lessons Learned. Helmut Schneider, LSU – Project Director Jonathan Stevenson, LSU - Developer Laurene Hutchinson, LSU-Data Base Administrator. Acknowledgements. Sgt. Darrin Naquin & Chuck Miller - LA Traffic Records Committee
E N D
Development of the 2005 Crash ReportLessons Learned Helmut Schneider, LSU – Project Director Jonathan Stevenson, LSU - Developer Laurene Hutchinson, LSU-Data Base Administrator
Acknowledgements • Sgt. Darrin Naquin & Chuck Miller - LA Traffic Records Committee • Jim Champagne - Louisiana Highway Safety Commission • Dan Magri - LADOTD • Dr. Sonja Wiley-Patton: Research – Understanding of Perception and Intentions to Use Electronic Crash report • http://cvoc.bus.lsu.edu/ss/wsb.dll/swpatton/LSU_Crash_Report.htm
Lessons Learned • From Paper Form to Laptop Computer • Get wide Range of Input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Paper form Put as much as possible on as few as possible pages Often no logical order Template use Computer Use layout convenient for police officers to enter Fast and easy data entry Logical order Crash Vehicle Written Report Drawing Paper versus Computers Use of layout of “well designed” paper crash report allows easy transition from paper to laptop!
Lessons Learned • Acknowledgements and Research Questions • Paper form – Computer • Get wide range of input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Get wide range of input! • Police officers • Traffic Engineers • Data entry personnel • State, City and small agencies • Safety professionals • IT personnel
Lessons Learned • Acknowledgements and Research Questions • Paper form – Computer • Get wide range of input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Process Issues • Analyze business process at agencies and Reengineering • Filling out crash form • Supervisor checks • Data transmission • Filing of Report • Backup
Overview Lessons Learned • Acknowledgements and Research Questions • Paper form – Computer • Get wide range of input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Technical Issues: Microsoft. NET Smart Client Software Built to take advantage of new XML technologies, smart client software delivers the best of both worlds, combining the reach of the internet and the power and functionality of local computing hardware.
Back-End – Databases and WWW servers • Databases for data collection and production • Assure well-designed database interfacing with Front-End • Web-Servers • Development server for designing queries • Production for public access
Lessons Learned • Acknowledgements and Research Questions • Paper form – Computer • Get wide range of input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Technology Solutions to Increase Quality of Data • Auto-population of data elements • Location information – GPS • Personal information – swiping licenses • Use VIN Number check • CVARS- display reminder to fill out commercial vehicle information when vehicle type is truck/bus
Overview Lessons Learned • Acknowledgements and Research Questions • Paper form – Computer • Get wide range of input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Data collection for safety improvements Allow for edits Data should not be locked Data collection for Public & Court use “Official” crash report Report needs to be signed and locked Legal Issues Pdf file Database
Overview Lessons Learned • Acknowledgements and Research Questions • Paper form – Computer • Get wide range of input • Business Process • Technology • Quality of Data • Legal Issues • Data Analysis & Problem Identification
Data Analysis & Problem Identification • Crash Reports • Commercial Crashes • By Parish • By Month • Graph Lhsc.lsu.edu