• Federal Highway Administration >
• Publications >
• Research Publications >
• 07046 >
• Chap2.Cfm >
• Model Minimum Inventory of Roadway Elements—MMIRE

Model Minimum Inventory of Roadway Elements—MMIRE

PDF files can be viewed with the Acrobat® Reader®

DEVELOPMENT OF MMIRE

MMIRE has been developed through a multistage process involving identification of potential elements, review and comment by data collection and data use experts, modification of MMIRE element listing based on that review, and developing of proposed coding schemes for each element. The following narrative describes that process.

IDENTIFICATION OF POTENTIAL MMIRE ELEMENTS

As noted above, the goal of MMIRE is to define critical safety data inventory elements—those elements needed by State and local agencies to conduct their internal analyses, and those elements required by existing safety analysis tools and resources. However, this effort was not limited to existing data element needs. Thought also was given to critical elements that will be needed for use in future analysis tools and program decisions. For example, pedestrian and bicycle safety are both high-priority areas for both State and local jurisdictions. As in program decisions and knowledge developed for other road users, both crash and exposure data are needed by the analyst. While pedestrian and bicycle exposure data currently are not collected, these counts may be possible by using digital-image-based methods now under development. Such critical, but nonexistent, elements are included in the proposed MMIRE structure. The research team based their choice of proposed elements on five specific existing tools and resources:

• HPMS—the Highway Performance Monitoring System. As noted above, HPMS is very likely the reason why current inventory systems exist in State DOTs. Even given the fact that HPMS was not developed as a safety data base, it was a high-priority source of potential elements, with elements from both the "universe" and the "sample" datasets of HPMS being considered in terms of possible use in safety analyses. Conversations were held with HPMS staff to ensure that the proposed MMIRE would be compatible with current HPMS revision efforts, and HPMS staff provided inputs on elements before initial review by outside experts.
• IHSDM—FHWA’s Interactive Highway Safety Design Model. This is a CAD-based system composed of multiple modules that allow the user to predict the expected safety performance of roadway design and redesign alternatives. Currently, only the rural two-lane version has been developed. However, similar tools are being developed for both suburban and urban arterials and rural multilane roadways. These tools will be included in the first edition of the Highway Safety Manual. Elements related to these road types have been added to the MMIRE matrix based on IHSDM user documents.⁽⁴⁾
• SafetyAnalyst. FHWA is currently developing this package of safety management tools that will assist the user in efforts ranging from screening the roadway network to identify sites for improvement, analyzing the sites and choosing the most appropriate treatments, and evaluating the effects of the treatment. Variables required by SafetyAnalyst as noted in the user documentation are considered to be very critical MMIRE elements. "Optional" or "recommended" SafetyAnalyst variables also were included and considered.⁽⁵⁾
• TSIMS—AASHTO’s Traffic Safety Information Management System. The overall goal of the TSIMS project is to develop an enterprise safety data warehouse, software that will assist the State and local agency in the collection, storage and linkage of the many types of safety data. A component of the current TSIMS package is a "Data Dictionary" that includes listings of "minimum," "basic," and "extended" roadway inventory variables. Since this is very similar to what MMIRE is attempting to do, many of these elements were reviewed and included in the MMIRE matrix.
• MMUCC—The Model Minimum Uniform Crash Criteria. While MMUCC is a crash data element system, it contains reference to 18 roadway inventory variables that should exist in a roadway inventory file and thus be linked to for analyses. Based on inputs from MMUCC specialists at the review workshop, these variables were checked against the listing of draft MMIRE variables, and all were found to be included.

These four original inventory element listings were reviewed in detail by the project team staff, and potential MMIRE elements were identified. In addition to elements in these four listings, the project team also included additional elements that are felt to be critical MMIRE variables. These additions were based primarily on four other sources:

1. Project team knowledge of State inventory databases that arose from their work with the nine States and two local agencies that are or have participated in FHWA’s Highway Safety Information System (HSIS).^{9
   9} For more information, refer to http://www.hsisinfo.org/.
   
   
2. Project team knowledge of roadway safety research efforts, and the data needed to conduct that research (including data that are not available in most or all State and local data files).
3. Project team knowledge of efforts related to the development of the Highway Safety Manual, and the data elements needed in the research and tools supporting that effort.
4. Project team knowledge of data needed in other "nontraditional" safety data analyses—primarily those related to pedestrian, bicycle, and roundabout safety.

This element identification effort produced a listing of over 150 potential MMIRE elements. The listing was converted to a matrix for use in the review workshop described in the section below. For each data element, the project team provided a proposed priority—1^st, 2^nd, and not recommended. This priority was based on a combination of factors including the requirements of the four major data sources and tools noted above (i.e., MMUCC was added later) and the team’s knowledge of current and expected future analysis and tool needs. In some cases, the difficulty of data collection was considered in this prioritization.

In addition to the draft priority, the matrix also provided information on the presence of or requirement for each data element in the four basic data sources and the "level of priority" provided by each source (e.g., HPMS has both Sample Section and Universe elements; SafetyAnalyst has "mandatory," "optional," and "supplemental" elements).

Finally, the project team searched for each potential data element in inventory files for 20 States that were available to them—the eight current HSIS States and 12 other States. Each State file was examined to determine which of the MMIRE elements being considered were collected by that State. For example, information on "county" is captured in 18 of the 20 State systems examined (i.e., 90 percent). This information was also provided to the reviewers in the workshop to give them some sense of the current presence of each variable in the sample State data systems.

THE MMIRE REVIEW WORKSHOP

A one-day MMIRE review workshop was held August 3, 2006, in conjunction with the International Traffic Records Forum (ITRF). As indicated above, the purpose of the workshop was to have State and local agency data collectors and data users review and provide feedback on the potential data elements in the draft MMIRE matrix described above. To ensure input from State and local DOT data collection managers, State and local data users, roadway safety researchers, and other roadway data experts, the workshop participants include both an invited group of attendees whose travel expenses were funded by FHWA and other ITRF attendees who signed up for the workshop. The workshop included 34 attendees—18 from State DOTs, 2 from local DOTs, 6 from the USDOT, 6 roadway safety researchers, one data-product vendor, and one representative from AASHTO. A full list of attendees is provided in Appendix A.

The above-described MMIRE draft matrix was presented to the attendees, who were asked to:

1. Provide feedback including their thoughts on the adequacy of the proposed MMIRE and the proposed priority of the elements.
2. Provide suggestions concerning additional/fewer elements and difficulties and solutions to collection of each element.
3. Provide suggestion on how best to proceed toward the development of a MMIRE implementation plan.

MODIFICATION OF DRAFT MMIRE ELEMENT LISTING

Following the workshop, the project team incorporated the feedback from the workshop participants into the final proposed MMIRE elements. Changes incorporated included addition of a small number of new variables and deletion of a smaller number of proposed variables, minor variable name changes, and changes in the priorities for some variables. The most significant changes involved (1) reorganization of sections of the matrix, (2) changing what were originally "intersection" descriptors to include additional "junctions" such as mid-block pedestrian and bicycle crossings, and (3) a change in how the "priority" of each element is defined. With respect to the latter, while the draft priorities discussed at the workshop could be affected by the anticipated difficulty in data collection, the discussion there resulted in the final priority being only based on the importance of the element in safety analyses, and a new variable was added estimating the level of difficulty of data collection.

DEVELOPMENT OF PROPOSED CODING SCHEME FOR EACH MMIRE ELEMENT

Following finalization of the proposed listing of MMIRE elements, the project team defined a proposed coding scheme for each element. For existing elements found in any of the five data sources noted above, the team reviewed the proposed coding from each. As would be expected, the coding for a given variable differed to some degree across the sources. The final decision was made based on the expected use in future analyses. Thus, additional weight was given to the schemes now used in both the IHSDM and SafetyAnalyst and anticipated for use in future tools. However, an attempt was made to ensure that the proposed scheme also was compatible with HPMS codes, on the assumption that States may have used that coding when developing their inventory files, thus reducing the amount of recoding that might be necessary in a conversion to the MMIRE formats.

Previous | Table of Contents | Next