150 likes | 309 Views
NCHRP Synthesis 350 Crash Records Systems. Safety Data Analysis Tools Workshop March 27-28, 2006. Synthesis Objectives. Who administers and maintains? How is data quality ensured? How integrated / linked to other sources? How accessible is information to users? What barriers exist?.
E N D
NCHRP Synthesis 350Crash Records Systems Safety Data Analysis Tools Workshop March 27-28, 2006
Synthesis Objectives • Who administers and maintains? • How is data quality ensured? • How integrated / linked to other sources? • How accessible is information to users? • What barriers exist?
Completeness / Quality Eroding • Reduced staff and resources • Increased crash thresholds • Data entry backlogs • More use of GIS but fewer roadway elements • Missing core elements (i.e. # of lanes, lane/shoulder widths, median type/width) • Horizontal curve, vertical grade, intersection/ interchange features virtually nonexistent
Responding States 50% response rate
SurveySummary • Crashes more timely and complete • over 80% within 90 days • almost 85% have all reportable crashes • Average system development cost just over $850,000 • Most popular features of current crash systems: • Analysis and Reporting (majority of votes) • Linkage • Data Collection
SurveySummary • Most frequently desired improvements are: • (1) linkage • (2) collection • (3) access
Institutional Barriers • Poor communication of changes • (e.g., new roadways not identified in crash system) • Lack of access to other data systems • (e.g., files reside in different agencies) • Inadequate training & feedback • Duplicate data collection • Changes in forms & procedures • (without adequate communication and review) • No consistent method of identifying locations
Successful Crash Records Systems “Where you stand on an issue depends on where you sit” Good Practices
Successful Systems Components • data collection • data processing & management • data linkages for reporting & analysis
Successful Crash Data Collection • Have technologies needed to ensure • Accurate data • Uniform data entry • Easy completion of the report • Seamless transfer of the crash data to: • the supervisor • the local crash records system (if desired) • the statewide crash records system
Successful Processing & Management • Accepts electronically transmitted data • Provides document imaging & management • Includes linkages or integration with other • data sources
Successful Crash Reporting / Analysis Ultimately, to be worth the effort and expense of its creation and maintenance, a crash records system must support analyses for highway and traffic safety. Establish a Knowledge Base for Traffic Records Systems
Overcome Institutional Barriers • Sell the value of safety information systems • Coordinate collection, management, and use • Integrate planning of safety programs and IS • Obtain resources to select appropriate technology • Use cadre of analytically trained professionals • Promote technical standards for IS characteristics
Characteristics of Successful Systems -- Not Just Hardware & Software -- • TRCC • Strategic Plan for TR Improvements • Budget for system lifecycle • Data-for-data partnerships / Sharing with others • Knowledge Base for TR systems • Simplified data collection