280 likes | 297 Vues
Explore the transition from manual crash reporting to TraCS for efficient data collection and improved accuracy in Wisconsin's transportation processes. Learn about benefits, system development phases, and the shift towards automation with TraCS forms.
E N D
Badger TraCS – A Coordinated Effort Patricia McCallum Wisconsin Department of Transportation Traffic Records Forum July 16, 2003
Wisconsin At A Glance • State Animal: Badger • State Beverage: Milk • State Motto: “Forward”
Wisconsin At A Glance • Population: 5.364 million • Counties: 72 • Total miles of Roadway: 110,150 • Federal and State Trunk: 11,752 miles • County: 19,668 miles • Local: 78,730 miles • Crashes per Year: 140,000 • Citations per Year: 850,776 • Law Enforcement Agencies: 620
Crash Reports Submitted by Enforcement Type • 620 Law Enforcement Agencies • State Patrol 4.4% • County Sheriff 39.5% • City Police 47.7% • Village Police 5.1% • Town Police 3.1% • Other .2%
State-of-Practice in Wisconsin • MV4002 Driver Report of Accident • 1-page paperform • Completed by drivers involved in the crash • Manually entered by DMV staff • Data not used for statistical reporting
State-of-Practice in Wisconsin • MV4000 Wisconsin Motor Vehicle Accident Report • 4-page scannable paper form • Non-scannable information entered manually by DMV staff • Contains 147 standard informational fields • Incorporates previously separate form for large truck and bus crashes • On/At location methodology • No standard for GIS maps or for automating incident location • Statistical reports prepared by DMV
State-of-Practice in Wisconsin • Uniform Traffic Citation (UTC) • 2 forms – paper and electronic • 1-page, 3 ply paper form • Information keyed by 3rd party vendor • 12% sent from courts electronically to DMV • No standard software for Field Data Collection, for Mobile Data Browsers or Records Management Systems
State-of-Practice in Wisconsin • Uniform Crime Report (UCR) • Paper form • Manual entry by Office of Justice Assistance • Summary crime statistics • Not compliant with National Incident-Based Reporting System (NIBRS)
State-of-Practice in Wisconsin • CMV Inspection Forms • Motor Carrier Safety Inspection Report • 42,000 reports annually • Federal reporting system • Paper form • Manual entry by State Patrol Inspectors • Motor Carrier Incident Reports • 50,296 reports annually • State reporting system • Paper form • Manual entry by State Patrol Inspectors • Only CMV Inspections at this time
Time to Change the Current Reporting System in Wisconsin “Bridging the gap between the state-of-practice and state-of-the-art”
Looking At Options • Need to replace OS/2 Operating System • Limited funding available – federal funds only • Lack of IT resources for development • Desire to automate crash data reporting • Need to improve location data
Reasons to Adopt TraCS-Administrative Benefits • Cost effective means to streamline data collection • Flexible and expandable architecture • Opportunity to enhance location data • One system for internal data entry and law enforcement automation
Reasons to Adopt TraCS-Law Enforcement Benefits • Modular design to meet majority of data collection needs • Common data shared among forms • Options for reporting crashes • Reduction in administrative duties and paperwork • Driving records updated sooner
Reasons to Adopt TraCS-Law Enforcement Benefits • Immediate access to their own data • Printed copies easier to read • Fewer keying errors • No more filling in bubbles • Data collection made easier, faster and more accurate
TraCS Forms Development CRASH FORMS • Phase I – Driver Report of Accident (MV4002) Internal Entry System • Phase II – Police Accident Report (MV4000) Internal Entry System • Phase III – Automation of MV4000 for Law Enforcement
TraCS Forms Development Phase I – Driver Report of Accident • Project began September 2001 • Created a focus group of processors • Added ODBC connectivity enhancement to TraCS (External Search) • 200+ edits in form • Implemented July 2002
TraCS Forms Development Phase II – Police Accident Report • Project began August 2002 • Project about 95% complete • Involved a focus group of processors • Adopted most of the edits from MV4002 plus added several more • Entry of Truck/Bus fields • Will include data entry of latitude and longitude coordinates if filled out by officer • Plan to implement summer 2003
TraCS Forms Development Phase III – Automation • Project planned to start fall 2003 • Create Outreach group of law enforcement officers • Adopt the majority of edits from internal MV4000 plus modifications • Develop abbreviated deer, fatal supplement, and driver information exchange forms • Establish an image system for storing electronic data • Establish a way to print the electronic reports • Pilot early 2004
TraCS Forms Development Location • Work group formed to provide recommendations on location data capture • Comprised of DOT, Law Enforcement and other agency personnel • Latitude and longitude coordinates can currently be captured using GPS • Will be entered starting in Phase II • Considering an automated map tool such as CTRE tool
TraCS Forms Development E-Citation • Project began January 2003 • Outreach group formed • Single entry screen • 100+ validations • Data sent to Circuit Court Automation Program and Municipal Courts • Field testing fall 2003 • Statewide roll-out 2004
Future TraCS Forms Development • WARNING CITATION • MOTOR CARRIER INSPECTION • INCIDENT REPORT
Coordination and Dissemination of TraCS • TraCS Sub-license and Application • Wisconsin TraCS Steering Committee • Agency representatives • Mission and goals • Coordination Subcommittee • Technical/programming experts • Reviews forms development to ensure statewide consistency
Wisconsin Contacts TraCS Project Manager: patricia.mccallum@dot.state.wi.us Crash IT Developer: jennifer.schmidt@dot.state.wi.us TraCS Citation Manager: anna.biermeier@dot.state.wi.us Citation IT Developer: jeffrey.murkve@dot.state.wi.us
Wisconsin Contacts Questions?