SCOHTS Meeting Robert Pollack - FHWA April 28, 2010

MIRE Concept Model Inventory of Roadway Elements Dictionary of critical roadway and traffic data variables that will enable us to make more effective and efficient safety improvement decisions – Similar to Model Minimum Uniform Crash Codes (MMUCC), – MIRE will be a guideline, not a requirement

Purpose Define “good inventory data” and move toward the use of performance measures Develop a roadway inventory to benefit multiple users Make it easier to collect, store, and use inventory safety data Increase the use of safety analysis tools Integrate inventory data to other safety data

Revision Process Initial MIRE report released August 2007 Current effort to revise MIRE elements, MIRE Version 1.0 (Soon to be released) Reviewed several sources: – Comments/polling results from Webconferences – Inputs from Executive Steering Committee – Final HPMS Specifications (May 2009) – Updates to other tools (SafetyAnalyst, HSM) – Safety Focus Areas

MIRE Elements MIRE elements broken down into three main categories – Roadway Segments – Roadway Alignment – Roadway Junctions 202 elements in proposed MIRE Version 1.0

Supplemental Databases Roadside fixed objects Signs Speed data Automated enforcement devices Land use elements related to safety Bridge descriptors Railroad grade-crossing descriptors Safety improvements

Format For each element – Definition – Attributes – Priority – HPMS/Tool Requirements – Illustrations if needed

Example - #182 Interchange Type Definition: Type of interchange. Attributes: Diamond, Full cloverleaf, Partial cloverleaf, Trumpet, Three-leg directional, Four-leg all-directional, Four-leg directional with loop ramps, Single entrances and/or exits (partial interchange), Single point interchange (SPI), Other (e.g., double crossover diamond, displaced left turn, diverging diamond). Priority: Critical HPMS/Tool Requirements: SafetyAnalyst(Required)

#182 Interchange Type

Highway Safety Manual Facilitates explicit consideration of safety throughout the project development process Provides a synthesis of validated highway safety research Provides analytic tools for predicting the impact of decisions on road safety

What MIRE Could Help You Do Use the New Safety Tools – Interactive Highway Safety Design Model (IHSDM) Tools for designers, planners and safety engineers to compare alternative roadway designs and safety treatments – SafetyAnalyst Advanced tools to identify most promising locations for treatment and choose the best treatment

What MIRE Could Help You Do Enhanced Problem Identification – These examples require inventory files containing full population of roadway elements (e.g., segments, intersections, curves, ramps) -- cannot be done with just crash data as done today. – E.g., better selection of high-priority intersections by comparison of crash rate within intersection categories (e.g., within all signalized intersections with entering volumes between X and Y)

What MIRE Could Help You Do Enhanced Problem Identification (cont) – Selection of high-priority horizontal curves by crash rate within roadway class (e.g., most hazardous curves on two-lane rural roads)

What MIRE Could Help You Do Enhanced Targeting of Specific Treatments – Selection of all horizontal curves on two-lane rural roads with speed limit of 55 and degree of curve greater than 10 degrees for low cost treatment (e.g., chevrons or advanced pavement markings)

Next Steps Finalize MIRE Report Develop MIRE Management Information System (MIRE MIS) – Prototype data management system Process for data handling and storage Linkage among files Performance metrics Mechanisms for data collection Select Lead Agencies and provide support as needed

Lead Agency Effort Select agencies willing to collect MIRE data elements Choose one area to focus on – Curves, intersections, pedestrian, etc Application process VHB project team provide support

Discussion Forum Webconference Presentations FAQs Resources

Questions Contact: FHWA: Carol Tan, Robert Pollack,