Improving the Crash Data System in Arizona: Impacts of SAFETEA-LU

Transcription

1 Improving the Crash Data System in Arizona: Impacts of SAFETEA-LU Presented at the 2006 Traffic Records Forum Palm Desert, California July 30, 2006 Kohinoor Kar, Ph.D., P.E. Arizona Department of Transportation () Highway Enhancements for Safety (HES)

2 Arizona Crash Facts ,891 total crashes 1,038 fatal crashes ~ 1,179 persons killed 45,234 injury crashes ~ 70,096 injured Estimated population 6,044,985 Fatality rate 1.97 per 100 MVMT Estimated economic loss over $2.8 billion Source: Motor Vehicle Division Traffic Records Section Using 2004 NSC Injury Cost Data

3 Existing Crash Data System ALISS = Accident Location Identification Surveillance System Structured Query Language (SQL)-based Maintained by the Motor Vehicle Division of Involves mostly manual processes Cannot take electronically collected crash data

4 How does it work? Most of the data collection is done manually on hard copy report form Crash data elements are entered into ALISS manually Reports are microfilmed for further uses and records Several public and private agencies request and use the data Crash reports are generated in various forms based on requests received

5 Crash Report Form A Few Major Issues Does not contain a few data elements recommended by the Model Minimum Uniform Crash Criteria (MMUCC) Hard copy, non-electronic form Some officers do not provide enough information as needed Data Collection Most of the agencies are collecting manually, except a few local agencies using electronic tools Data Transfer (Report to Database) 100% Manual; electronically collected data cannot be imported to ALISS yet Data Storage Report forms are stored in Microfilms only

6 A Few Major Issues (contd.) Data Integration No comprehensive system exists that integrates various data elements, e.g., highway data, traffic data, crash data, GIS Quality Control/Quality Assurance Lot of human errors Problems with location identifications Training Police Officer s s training not sufficient or updated Others Lack of communications between users Deficiencies in resources and organizational set ups

7 Impact of SAFETEA-LU Safe, Accountable, Flexible and Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) Section 408 Program grants administered by the National Highway Traffic Safety Administration (NHTSA) First year grant requires that a State established a highway safety data and Traffic Records Coordinating Committee (TRCC) developed a multiyear highway safety data and traffic records system strategic plan (Strategic Plan) Source: Federal Register, Vol. 71, No. 22, Feb 2, 2006

8 Arizona s s Approach State of Arizona developed the Strategic Planning Process, which will address the following areas: Crash information Roadway information Driver information Vehicle information Enforcement/Adjudication information Injury surveillance information

9 Model Data Processing Vehicles, Titles, Registrations Reports Road Characteristics, Location, Inspections, Carrier Data Titles, Registrations, Inspections Vehicle Information VIN, Tag, Owner Roadway and Traffic Data Roadway Information (GIS) Crash Characteristics Structures, RR Inventory Traffic, Pavement Condition, Inventory, Ratings Crashes, Operator Vital Statistics, Reports Cost Data Crash EMS Response, Information Injury Surveillance BAC, Drug, Death Information, Vital Stats Driver Analysis, Reports Information Crash History Characteristics EMS Run Reports, Driver License History Driver Information Convictions Dispositions Citations, Arrests Trauma Data, Discharge Summaries, Rehabilitation Reports Driver History Enforcement/ Adjudication Information Reports

10 Recent Developments The Governor s s Traffic Safety Advisory Council (GTSAC) established a Traffic Records Subcommittee, which is currently known as the Traffic Records Coordinating Committee (TRCC) performed a research project on Arizona s s crash data collection and analysis system A Crash Data User Group has been formed with key members NHTSA Technical Team performed a Traffic Records Assessment Data Processing in the Traffic Records System has been modeled (flow chart on previous slide) Tasks and responsibilities have been defined, and delegated to various stakeholders NHTSA Section 408 Grants application has been submitted

11 TRCC Strategies & Tasks Create and publish a catalog of available highway safety reports and resources to enable all interests in highway safety to become aware of points of contact, plans for improvements, and information available Clearinghouse of documents located and published on GTSAC website Edu TRCC Staff time and website Produce an interface specification document that identifies a specific data transmission protocol to allow agencies to submit crash data electronically to ALISS Technical documentation defines standards by which data shall be submitted to ALISS MVD and Data Bureau PROJECT (FY 06) - $30,000 Expand the Data Warehouse to include data extracts from the other traffic records system components More data components will be available through the data warehouse Data Warehouse Staff Time

12 TRCC Strategies & Tasks (contd.) Provide a secure web- based access to the data warehouse Pilot test with a limited number of jurisdictions and/or partner agencies (TRCC members) Data Warehouse Staff Time Establish and implement a standard procedure for identifying street names that can be used easily by the data collection personnel, especially for police officer collecting crash data Documented standard for naming roadways (Av vs. Ave) Data Bureau PROJECT (FY 06) - $25,000 Establish a cooperative program with the AOC to track conviction reports which are rejected and assure that they are entered into the file Cooperative agreement between and AOC in place MVD Staff Time

13 TRCC Strategies & Tasks (contd.) Develop a state pre- hospital and trauma patient care data repository(ies) EMS ADHS Potential 408 funding (infrastructure) based on scoping Evaluate and determine the feasibility of a secure portal with defined data access parameters for data owners to access the CODES linked data file EMS ADHS and CODES Potential 408 funding (infrastructure) based on scoping Establish a process to track fatal crashes to insure all fatal reports are documented and submitted to ALISS and FARS Process established for notification (awareness) and tracking of fatal crashes MVD staff time Establish a crash data quality (ALISS) and trend analysis report that identifies baseline data quality issues Benchmarks established MVD PROJECT (FY 06)- $100,000

14 TRCC Strategies & Tasks (contd.) Obtain analytical capabilities on the GOHS staff for researching and developing strategic initiatives for all program areas in highway safety GOHS staff person on-board Edu GOHS GOHS Staff Time Develop a communications plan that solicits input and provides critical information to stakeholder agencies, departments, and organizations Information shared with GTSAC Communication Subcommittees Edu GOHS GOHS Staff Time Develop a "data dictionary" and manual that will be made available to users Dictionary developed and manual available Edu MVD and MAG MAG funds and MVD and MAG staff time

15 TRCC Strategies & Tasks (contd.) Select a standard for electronic imaging Standard protocol developed MVD MVD Staff Time Update the centerline file on a regular (at a minimum as a new road opens) basis so that the location-based maps within the ALISS system can be current with X,Y coordinates to improve the current 20% deficiency in the ALISS database for crashes that lack GPS location information Reduction in 20% deficiency Data Bureau Staff Time SPR Funding for staff

16 TRCC Strategies & Tasks (contd.) Assure that the current migration to the geo- database and the Data Warehouse capture and store roadway attributes needed for the management of the highway infrastructure and safety analysis Geo-database and crash data input interface (new ALISS front-end) with software tools that allow integration of crash data and roadway inventory for state and local roads Data Bureau PROJECT (FY 06) -$50,000 plus $100,000 (est) SPR FY 06 and 07 Upgrade from microfiche storage of traffic records to electronic data imaging format in Traffic Records Section Electronic scanner purchased and in use within Traffic Records Section MVD and GOHS PROJECT (FY 06) - $50,000

17 TRCC Strategies & Tasks (contd.) Determine user community for MVC data and their approved levels of access to ensure appropriate confidentiality Users and access levels defined TRCC PROJECT (FY 07) - $50,000 Record the adverse histories from all drivers' previous states of record in the same manner as is done for commercial drivers Complete driver history of each registered driver in Arizona Enf MVD PROJECT (FY 06 and 07) - $200,000 Modification of ALISS to accept missing MMUCC elements and attributes (i.e. BAC) Report on needed modifications HES PROJECT (FY 06)- $50,000

18 TRCC Strategies & Tasks (contd.) Provide additional training or printed bulletins to correct problem areas of the crash report such as Manner of Collision and correctly identifying the carrier in a CMV crash Training provided to officers regionally Edu MVD and GOHS PROJECT (FY 07)- $50,000 Provide basic data extraction and analysis tools for the entire user community Tools available to user community MVD PROJECT (FY 06) - $100,000 Develop a program and purchase hardware to implement a dual screen system for Traffic Records Section (look at electronic form and enter into ALISS) Traffic records section has capability to use dual screen format MVD PROJECT (FY 07) - $100,000

19 TRCC Strategies & Tasks (contd.) Expand the Data Warehouse to include data extracts from the other traffic records system components Phase 1 will be implemented Data Warehouse Potential 408 funding (infrastructure) based on scoping (FY 06 and 07) Provide a secure web- based access to the data warehouse Pilot test with a limited number of jurisdictions and/or partner agencies (TRCC members) Data Warehouse Potential 408 funding (infrastructure) based on scoping (FY 06 and 07) Program in place to track conviction reports which are rejected and assure that they are entered into the file Program in place to track conviction reports to their completion Enf MVD PROJECT (FY 06 and 07)- $200,000

20 TRCC Strategies & Tasks (contd.) Facilitate discussion with tribal courts about the possibility of submitting conviction documentation to a state database, especially those associated with DUIs Tribal courts submitting conviction data to state database Enf ITCA Potential 408 funding (infrastructure) based on scoping Develop an electronic transfer of fatal crash data from ALISS to FARS Data transfer program to share ALISS data with FARS (elimination of duplication of data entry effort) MVD PROJECT (FY 06 and 07)- $300,000 Support the electronic transfer of data to ALISS Batch uploading capabilities based on established protocols MVD PROJECT (FY 06 and 07)- $100,000

21 TRCC Strategies & Tasks (contd.) Provide for the entry of needed elements and attributes into the crash report form New data elements within Arizona's crash report form to accommodate elements and attributes TRCC PROJECT (FY 06 and 07)- $50,000 Provide for the front end data entry of needed elements and attributes into ALISS New data elements within ALISS to accommodate elements and attributes MVD PROJECT (FY 06 and 07)- $100,000 Develop a tracking system in to insure that reports returned for correction are returned for re-entry entry into ALISS Computerized document tracking system for reports returned to local jurisdictions for additional information MVD PROJECT (FY 06 and 07)- $100,000 Track trends in ALISS's data quality issues Trend tracking program in place MVD PROJECT (FY 07)- $100,000

22 TRCC Strategies & Tasks (contd.) Conduct a pre-hospital and hospital needs inventory that will identify the current status of computer equipment, software products being used, and availability of internet access for pre-hospital providers and trauma facilities throughout EMS ADHS and CODES Potential 408 funding (infrastructure) based on scoping Support the AOC in the migration, development, and implementation of the new court case management system for limited jurisdiction courts (Tempe) with the existing judicial data warehouse ensuring that there are linkages to other components of the traffic records system Needs assessment report prepared for the TRCC Enf AOC Potential 408 funding (infrastructure) based on scoping

23 TRCC Strategies & Tasks (contd.) Support the AOC in the migration, development, and implementation of the new court case management system for general jurisdiction courts (Superior Court in Tucson) with the existing judicial data warehouse ensuring that there are linkages to other components of the traffic records system Needs assessment report prepared for the TRCC Enf AOC Potential 408 funding (infrastructure) based on scoping Work with the courts not reporting local jurisdiction convictions to obtain conviction documentation, especially those associated with DUIs All courts reporting convictions to state database Enf AOC Potential 408 funding (infrastructure) based on scoping

24 TRCC Strategies & Tasks (contd.) Design and implementation of a centralized statewide citation tracking system containing information about a citation's entire life cycle Centralized statewide citation tracking system in place Enf AOC Potential 408 funding (infrastructure) based on scoping Set protocol for the use of electronic citations to insure that the electronic citation contains the state prescribed data elements Protocol established for electronic citations Enf AOC Potential 408 funding (infrastructure) based on scoping

25 TRCC Strategies & Tasks (contd.) Multiple referencing system for facilities with route number, names, and spatial location Database created with look up tables for multiple names of same facility (SR 87 and Arizona Ave) Data Bureau PROJECT (FY 07) - $150,000 Purchase GIS file for Arizona's local roads from a third party vendor File is acquired and a process established for integration into ATIS Roads Data Bureau PROJECT (FY 06 and 07) - $500,000 Assure that the current migration to the geo- database and the Data Warehouse capture and store roadway attributes needed for the management of the highway infrastructure and safety analysis Geo-database and crash data input interface (new ALISS front-end) with software tools that allow integration of crash data and roadway inventory for state and local roads Data Bureau PROJECT (FY 07 and 08) -$150,000

26 TRCC Strategies & Tasks (contd.) Assure that the above undertaking considers the interrelationship of ALISS and road and behavioral information for effective data-driven driven safety improvements Analysis tool for safety project prioritization HES PROJECT(FY 07 and 08) - $300,000 Upgrade, when feasible, the collection of location data using GPS devices and remote data entry of crash data Interested jurisdictions have GPS devices GOHS PROJECT (FY 09)- $500,000

27 Conclusions State of Arizona has developed a few well-defined strategies and tasks to improve the crash data system GTSAC and TRCC have been formed Activities of TRCC have been accelerated by Congressional mandates Tasks and responsibilities to improve the crash data system have been delegated to various stakeholders Section 408 Grants application submitted

28 Big Question

29 Acknowledgements Reed Henry, TRCC Co-Chair, Chair, -HES Jennifer Brown, FHWA Arizona Division Nancy Ann Crandall, Traffic Records Sreelatha Gajula, -HES

30 Thank You! Questions? Comments? Suggestions? Contact: Kohinoor Kar