National Academy of Sciences | 150 Year Anniversary

Questions? Call 800-624-6242

| Items in cart [0]

The National Academies Press

Rights & Permissions

topleft topright

NCHRP Report 525 Volume 16: A Guide to Emergency Response Planning at State Transportation Agencies (2011)
National Cooperative Highway Research Program (NCHRP)

Citation Manager

Lockwood, Stephen, Singleton, Anne, Wallace, Charles E, Sergent, Jason, Boyd, Annabelle, Transportation Research Board. "Emergency Incident Characteristics and Terminology." NCHRP Report 525 Volume 16: A Guide to Emergency Response Planning at State Transportation Agencies. Washington, DC: The National Academies Press, 2011.

Please select a format:

BibTeX EndNote RefMan


Page
19
bottomleft bottomright
Page
19
Front Matter (R1-R11)
Summary (1-4)
Background (5-5)
Guide Scope (6-6)
Guide Audience (7-7)
Guide Development Process (8-9)
Homeland Security Presidential Directives (10-10)
National Emergency Management Policies and Guidelines (11-12)
Institutional Authority Context (13-14)
Guiding Principles (15-18)
Emergency Incident Characteristics and Terminology (19-21)
Section 3 - Assess Agency Status in Emergency Response Training (22-22)
Emergency Planning Phase (23-23)
Step 1 - Form a Collaborative Planning Team (24-27)
Step 2 - Conduct Research to Identify Hazards and Threats and Analyze Gathered Data (28-33)
Step 3 - Determine Goals and Objectives of Emergency Planning and Response Activities (34-34)
Step 4 - Develop and Analyze Courses of Action and Identify Resources (35-37)
Step 5 - Write the Plan (38-40)
Step 6 - Approve and Implement the Plan (41-41)
Step 7 - Exercise the Plan and Evaluate Its Effectiveness (42-43)
Prepare for the Emergency (44-45)
Step 1 - Develop Approaches to Implement State Transportation Agency Roles and Responsibilities During Emergencies (46-50)
Step 2 - Establish Communication Protocols and Mechanisms for Public Outreach (51-56)
Step 3 - Emergency Evacuation/Shelter-in-Place/Quarantine Plans and Traffic Control and Management Protocols and Procedures (57-61)
Step 4 - Develop Mobilization Plans for State Transportation Agency Personnel and Resources (62-65)
Step 5 - Ensure Cost Tracking and Accountability (66-66)
Respond to the Emergency (67-68)
Step 1 - Initiate Emergency Response (69-70)
Step 2 - Address Emergency Needs and Requests for Support (71-73)
Step 3 - Manage Evacuations, Shelter-in-Place, or Quarantine (74-76)
Step 4 - Implement Emergency Response Actions (77-79)
Step 5 - Continue Response Requirements (80-81)
Step 6 - Conclude Response Actions (82-82)
Step 1 - Restore Traffic to Affected Areas (83-85)
Step 2 - Identify and Implement Lessons Learned (86-88)
Impact on and of the Transportation System (89-90)
Example: Escalation of Incidents and Response (91-94)
List of Acronyms (95-97)
References (98-99)
Other Resources (100-100)
Planning-Level Organizational Principles (101-101)
PREPARE for Emergencies (102-102)
Decision-Making Sequences (103-103)
Full Emergency Response Matrix (104-125)
Purpose and Supporting Resources for Action Reference Matrix (126-136)
Appendix A - Guide to Using Portions of the 2002 Guide (137-138)
Appendix B - Emergency Response Legal Authorities (139-139)
Appendix C - Emergency Response Stakeholder Responsibilities (140-145)
Appendix D - Key Emergency Response Definitions (146-149)
Appendix E - Key Traffic Incident Definitions (150-152)
Appendix F - Intelligence Fusion Centers (153-154)
Appendix G - Transportation Emergency Response Effects Tracking (TERET) (155-155)
Appendix H - Model Emergency Operations Plans (156-156)
Appendix I - Policy and Procedural Memoranda and Memoranda of Understanding (157-157)
Appendix J - Training/Exercise Plans (158-158)
Abbreviations used without definitions in TRB publications (159-159)

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 19
Institutional Context for Emergency Response 19 · Similarly, are the respective roles and responsibilities of the state/territorial/ tribal transportation agency vis-ŕ-vis local agencies clearly defined and The importance of Unified Com- accounted for in state and agency EOCs? mand is not to have a single Inci- · Is a transportation agency's public information program adequate for dent Commander, but rather to appropriate response? operate under a single Incident · Is the state and transportation agency level of communications interoper- Action Plan (IAP). ability adequate? · How does the response program relate to a broader emergency transporta- (Paraphrased from NIMS) tion operations program or a traffic incident management program? · Is evacuation/shelter-in-place/quarantine planning adequate? · Is the response program properly correlated with the need to protect the agency's critical assets? How can a solid response program be part of the protection of critical assets? · Where is the funding for emergency response? Is the funding adequate? · Is the state agency internally aware, and are other agencies aware, of how transportation agen- cies can contribute to emergency response? Are assets inventoried? · How can ITS, transportation management centers, and other functional equivalents be used for response? · How can Traffic Incident Management Teams be effectively used for ER? Key Definitions The various documents identified in Section 1, Introduction, generally contain glossaries. As these are mostly DHS or FEMA emergency management documents, they define terminology used in the Homeland Security (HS)/EM community. The terminology is not always consistent among the documents. See Appendix D for an annotated glossary of general HS/EM terminol- ogy. Key emergency management terms included in the Appendix D glossary follow: · Catastrophic incident · Incident, traffic · Emergency · First responder · Emergency management · Fusion Center · Emergency Management Assistance Compact · Incident Command System (ICS) (EMAC) · Major disaster · Emergency management/response personnel · Security countermeasures · Emergency response · Traffic incident · Emergency Transportation Operations (ETO) · Traffic incident management · Incident (see below) · Unified Command (UC) Additionally, Appendix E contains a discussion of traffic incident terminology, including MUTCD definitions of minor, moderate, and major incidents. Emergency Incident Characteristics and Terminology The more severe categories of incidents are those more commonly associated with emergen- cies caused by nature or persons acting as terrorists. As the degree of complexity of an incident increases, so does the typical response. Figure 6 illustrates this point. Table 2 summarizes the characteristics of these incident levels. The final category, catastrophic, was not included in Figure 6, but is added Table 2 because in EM, it is considered the highest level of incident, generally garnering the greatest response. Examples are 9/11, Hurricane Katrina, and the Asian tsunami.

OCR for page 20
20 A Guide to Emergency Response Planning at State Transportation Agencies Source: Adapted from NCHRP Report 525, Volume 6, 2005. Figure 6. The complexity of emergencies and response. Section 5, Nature and Degree of Hazards/Threats, details these incidents and the responses to them. The comments above also point out the scalability of the NIMS ICS. At a minor traf- fic incident, the Incident Commander could be a single police officer working the scene alone, but the principles of NIMS should be followed as appropriate. As the severity of incidents increases, the response in terms of ICS grows, including application of Unified Command and ultimately Multiagency Coordination (MAC). The key point is to use the ICS structure for all incidents. This is why all responders--including transportation personnel--are trained in NIMS/ICS.

OCR for page 21
Institutional Context for Emergency Response 21 Table 2. General incident characteristics. Level Definition Typical Cause Typical Comment Duration Planned Planned special Entertainment, Hours to Generally a controlled Activities events, recurring or sports, social, weeks event, serious nonrecurring political incidents may be a by- product becoming one of the next levels Minor An incident generally Minor-moderate Minutes to ICS should be Incident resolved by local traffic, minor several followed, albeit in agencies flooding or fires hours these cases generally on a small-scale basis. This would include traffic incidents at the 1­2 levels. Major An incident requiring Major traffic, Hours to This would likely Incident multiple jurisdictions/ suicide attempt, days warrant a scaled-up agencies major non- response, including HAZMAT spill the formal creation of a command post and strict ICS/UC. This would include traffic incidents at levels 2­3 HAZMAT Any incident involving a HAZMAT spill Hours to This is a special Incident HAZMAT-qualified days category and may response have long-term effects if contamination is involved Natural Any naturally occurring Weather, Days to These will generally Disaster major emergency agricultural, months require the full earthquake, implementation of ICS pandemic, with activation of wildfires EOC(s), perhaps even State EOC(s) Terrorist A human-perpetrated CBRNE Days to Same as above. Incident major emergency months Catastrophic Extraordinary levels of Any of the Months to These may have any mass casualties, foregoing on a years of the previous levels damage, or disruption massively as the genesis. severely affecting the destructive or Multiple state EOC population, threatening activations are infrastructure, scale probable as well as a environment, economy, highly populated ICS national morale, and/or government functions