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.
21 C H A P T E R 3 This chapter presents the general framework for the response process. Details of the key phases within the scope of this manual will be presented in subsequent chapters. To place these phases in context, Table 3-1 provides an overview of the timeline for a general emergency response. In this approach, planning (âFirst You Planâ) and proactive efforts are stressed and will be covered in more detail in Chapter 4. To be deployable by a wide variety of organizations in emergency situations, this meth- odology was developed to be efficient, comprehensive, and inclusive. Implementation is not a trivial matter given the number of variables that must be considered, many of which are beyond the control of the emergency response planners. The methodology covers a diverse range of structure types, ranges of traffic levels, as well as the type of event in order to deter- mine priorities, particularly for the critical period immediately after an event. The method- ology also considers coordination among multiple organizations that may have an interest in assessing these structures so as to avoid overlap and maximize the effectiveness of the response effort. The process is multi-tiered in order to accommodate and recognize the skill of the âinspec- tor,â the available technology and resources, the agencies involved in the response, the type of structure, the type of event, and the ranges of traffic levels. This applies to the coding and mark- ing procedures as well. Of the four assessment stages proposed (and described in detail in Section 5.1), this manual concentrates on the FR and PDA stages that need to be completed rapidly after an emergency event. Response levels are also defined to help determine the quantities of personnel required based on the size of the event. The first stage, FR, is important to obtain an overview and determine the overall extent of damage. Results from FR help prioritize the on-site assessments in the PDA, DDA, and EI stages. PDARs then need a simplified, rapid procedure for identifying basic damage states. The assess- ment process can minimize subjectivity from the inspection process through the use of fail-safe automation based on consistency of data collected in this systematic workflow. However, this procedure is different (and should never replace) the procedure used by a trained structural engineer or inspector who can afford to spend more time on each site during a routine inspec- tion (e.g., NBIS), resulting in greater detail. Those inspections also can utilize more advanced technologies. To help with the PDA process and reporting of results, Volume 3: Coding and Marking Guide- lines was developed to assist the PDARs through a number of possible damage scenarios and Response Process Framework
22 Assessing, Coding, and Marking of Highway Structures in Emergency Situations: Assessment Process Manual Phase Timeline Components Planning and Preparation (â) Now to Day 0 ⢠Identify vulnerable structures and categorize ⢠Prioritize and perform maintenance and upgrades on structures, following a prioritized list, if available and based on availability of funds ⢠Acquire baseline data and analyze potential impacts to key structures ⢠Instrument structures, if possible ⢠Develop response plans and procedures for a number of scenarios ⢠Perform what-if analyses and update plans and procedures as needed ⢠Assign inspection ownership for each structure and highway segment, if possible ⢠Identify safe zones and centralized reporting locations ⢠Research and review best practices and lessons learned ⢠Perform training and drills ⢠Coordinate with other agencies ⢠Publish communication protocols and procedures ⢠Perform regional analysis to develop priority inspection list ⢠Assemble list of potential first responders and PDARs for emergency task force ⢠Develop guidelines for repairing damaged structures Advance Notification for some emergencies (e.g., hurricanes) but not with others (e.g., earthquakes) (â) Few days/ hours prior to Day 0 ⢠Review emergency procedures ⢠Review communication procedures ⢠Implement evacuation plans ⢠Alert response teams ⢠Close traffic near most vulnerable structures ⢠Identify special needs and begin coordination with other agencies ⢠Collect and update emergency task force ⢠Report for duty (physically or through conference call) ⢠Perform initial regional analysis to develop/update priority inspection list Emergency Event / Initial Response* Day 0 ⢠Complete tasks listed in Advance Notification if not already done ⢠Perform FR, when deemed necessary ⢠Initialize PDA starting with critical and essential structures, including coding and marking of structures, as needed ⢠Close impacted routes and set up detours in coordination with other agencies ⢠Communicate with public as appropriate Site Inspections Days to weeks ⢠Continue PDAâassess, code, and mark, as needed ⢠Build temporary structures/bracing ⢠Optimize DDA through regional assessment and coordination ⢠Perform load rating / load analysis when required ⢠Coordinate with other agencies and close/open routes Regional Assessment Weeks ⢠Document areas of impact and damage ⢠Document which highway structures experienced damage ⢠Perform EI on required structures ⢠Develop damage cost estimates to support requests for federal relief funds ⢠Build temporary structures/bracing Initial Recovery Weeks to months ⢠Prioritize and begin repairs ⢠Document procedures ⢠Open routes ⢠Build temporary structures Economic Recovery Months to years ⢠Repair or re-build structures Continued Recovery Years ⢠Review lessons learned ⢠Prioritize upgrades ⢠Continued maintenance ⢠Update strategic plans and emergency response procedures ⢠Go back to Planning and Preparation phase *Additional events may occur such as earthquake aftershocks or a tsunami following an earthquake that need to be accounted for as well. Table 3-1. Key phases in emergency response and events life cycle.
Response Process Framework 23 emergency events. It also provides additional details and examples to help PDARs perform a rapid assessment. Suitable technologies are recommended for each type of inspection and at each stage in the response timeline. Any emergency response plan must have built-in redundancy in terms of alternative inspec- tion methods that take into account individual agenciesâ constraints. It must be recognized that telecommunications links, access to information, and access to the actual structures may or may not be available. Consequently, a two-part, fail-safe approach is recommended that can utilize smart devices via a smart app (see NCHRP Web-Only Document 223: Guidelines for Developing Smart Apps for Assessing, Coding, and Marking Highway Structures in Emergency Situations) when communication infrastructure is available and falls back on manual and paper-based forms as a last resort when digital devices cannot be used.
