National Academies Press: OpenBook
« Previous: Chapter 4 - Case Examples
Page 67
Suggested Citation:"Chapter 5 - Conclusion." National Academies of Sciences, Engineering, and Medicine. 2020. Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events. Washington, DC: The National Academies Press. doi: 10.17226/25825.
×
Page 67
Page 68
Suggested Citation:"Chapter 5 - Conclusion." National Academies of Sciences, Engineering, and Medicine. 2020. Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events. Washington, DC: The National Academies Press. doi: 10.17226/25825.
×
Page 68
Page 69
Suggested Citation:"Chapter 5 - Conclusion." National Academies of Sciences, Engineering, and Medicine. 2020. Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events. Washington, DC: The National Academies Press. doi: 10.17226/25825.
×
Page 69

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

67 Conclusion State DOTs are progressing toward or have attained compliance with the requirements of 23 CFR § 667. However, agencies have taken different approaches to interpreting the requirements and incorporating the results of their efforts into broader asset management and infrastructure investment decisions and actions. This study sought to document the actions taken to date and planned by state DOTs in this regard. Conclusions About Different Agency Approaches These conclusions draw from the information gathered in this effort to identify differences between agencies’ approaches and results and determine the factors that have led to these differences. • FHWA opted to include the requirements for identifying and evaluating sites damaged by multiple emergency events in a section of the Code of Federal Regulations (23 CFR § 667) separate from the requirements for the Emergency Relief Program (23 CFR § 668). They issued those requirements in coordination with the asset management regulations (23 CFR 515) because the agency identified a connection between the management of these facilities and an agency’s ability to address risks related to achieving its asset management objectives (FHWA 2016d). • The synthesis found most agencies have not developed processes that integrate the results of identifying and evaluating sites damaged by multiple emergency events into their asset management practices other than providing summaries in their TAMPs and making the findings available to staff and FHWA. • Agencies that identified the greatest number of sites damaged by multiple emergency events either took a broad view to interpreting the requirements of 23 CFR § 667, often going beyond those requirements in their definitions of qualifying events or locations impacted by multiple events, or had practices in place to retain detailed historical records. • Nearly half of the agencies that responded (19 of 39, 45%) reported having no records of damage due to emergencies prior to 2001. • Lack of data was selected as the greatest challenge to compliance with the requirements of 23 CFR § 667 by the most agencies in the survey (16 out of 42, 38%). • Just over half of the agencies (14 of 27, 52%) that reported identifying at least one site damaged by multiple emergency events provided no response regarding the status of their evaluations to determine alternative strategies for sites damaged by multiple events. • State DOTs most commonly worked with state emergency management offices to identify and evaluate sites damaged by multiple events. • Most states (31 of 42, 74%) were able to comply with 23 CFR § 667 without requiring addi- tional permanent staff. States that did augment staff most commonly did so with consultants (10 of 11, 91%). C H A P T E R 5

68 Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events • Agencies adopted a variety of criteria for defining damage from multiple events having occurred at a common location. • Half of responding agencies (21 of 42) indicated that the results of their analyses were made available to one or more external stakeholder groups. • Most agencies (31 of 42, 74%) had not yet developed written procedures related to compliance with 23 CFR § 667. • Most responding agencies (15 of 18, 83%) incorporated the results of the analysis only into the risk management section of their TAMPs. Only seven agencies reported incorporating the results into other sections of their TAMPs. • Most agencies have not yet used the alternative strategies developed in compliance with 23 CFR § 667 in support of project development. Opportunities for Future Research The following bulleted items highlight knowledge gaps that could be supported by future research efforts. Those opportunities are summarized as follows. • Additional research could seek to build on prior efforts regarding the consideration of resilience in project design to incorporate resiliency into programmatic and strategic practices and processes, such as LCP and developing asset management investment strategies. • Research would enable state DOTs to identify the potential benefits of identifying alternative strategies for sites damaged by multiple events to support decisions regarding the extent to which it is cost effective to expand the definition of “event” and “same location” beyond the requirements of 23 CFR § 667. • Research could determine the types and formats of data elements that can be efficiently collected to support the identification of sites and evaluation of alternative strategies for loca- tions damaged by multiple emergency events. Agencies would benefit from the documentation of best or recommended practices for recording, storing, and sharing data about the location, type, and root cause of damage and repairs related to emergency events. Standardization of such data and processes would support coordination between different business units within agencies, such as the responsibility for response and recovery and the units responsible for collecting reimbursements from federal and other agencies. • Changes in maturity would be evident if the survey were repeated following the November 23, 2020, deadline for states to identify and evaluate sites damaged by multiple emergency events on all public roads. Particular areas of focus that could address knowledge gaps remaining after this synthesis include – Documentation and comparison of how different agencies define emergencies and permanent repairs, – Examples of agencies’ use of evaluation results, particularly to justify the funding of betterments through the FHWA’s ER program, and – Additional documented practices for locating and evaluating sites damaged by multiple events. • To comply with 23 CFR § 667, agencies must develop alternative strategies for addressing the root cause of damage at sites damaged by multiple emergency events (23 CFR § 667.1). Additional research could provide support to agencies identifying and executing appropriate alternative strategies and applying those alternative strategies – To repair damaged assets during recovery from emergency events, – For incorporation into the environmental review process during project development, – To inform the planning and project selection processes, and – To support LCP and other TAMP practices.

Conclusion 69 • Research could help identify the connection, if any, between damage caused by emergency events and disruption of service caused by the events. • Agencies other than state DOTs (e.g., county, municipal, or toll authorities) could benefit from additional research regarding best practices for the collection and retention of data on damage and related repairs resulting from emergency events. Note that the results of FHWA pilot projects on incorporating resiliency into LCP were not available in time for inclusion in this report. • Several agencies have developed software for collecting and storing data on damage from emergency events. The documentation of best or recommended practices for the design and use of such software would support agencies of all types in selecting or developing tools that address their needs and facilitate the sharing of information with other stakeholders.

Next: Abbreviations, Acronyms, and Initialisms »
Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events Get This Book
×
 Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events
MyNAP members save 10% online.
Login or Register to save!
Download Free PDF

Current legislation and subsequent asset management rules require state departments of transportation (DOTs) to conduct statewide evaluations of roads, highways, and bridges that have required repair and reconstruction activities two or more times since 1997 due to emergency events as declared by the president of the United States or by a state’s governor.

The TRB National Cooperative Highway Research Program's NCHRP Synthesis 556: Asset Management Approaches to Identifying and Evaluating Assets Damaged Due to Emergency Events furnishes documentary evidence of the approaches that state DOTs have taken to identify and evaluate locations where highway assets have been repeatedly damaged and to identify considerations that have been made for mitigating the risk of recurring damage to assets in those areas.

The report is intended to help transportation agencies with building data sets and tools that support the evaluation of damage to assets associated with emergency events and to illustrate methodologies that are being used to integrate these risks into asset investment decisions.

READ FREE ONLINE

  1. ×

    Welcome to OpenBook!

    You're looking at OpenBook, NAP.edu's online reading room since 1999. Based on feedback from you, our users, we've made some improvements that make it easier than ever to read thousands of publications on our website.

    Do you want to take a quick tour of the OpenBook's features?

    No Thanks Take a Tour »
  2. ×

    Show this book's table of contents, where you can jump to any chapter by name.

    « Back Next »
  3. ×

    ...or use these buttons to go back to the previous chapter or skip to the next one.

    « Back Next »
  4. ×

    Jump up to the previous page or down to the next one. Also, you can type in a page number and press Enter to go directly to that page in the book.

    « Back Next »
  5. ×

    To search the entire text of this book, type in your search term here and press Enter.

    « Back Next »
  6. ×

    Share a link to this book page on your preferred social network or via email.

    « Back Next »
  7. ×

    View our suggested citation for this chapter.

    « Back Next »
  8. ×

    Ready to take your reading offline? Click here to buy this book in print or download it as a free PDF, if available.

    « Back Next »
Stay Connected!