Professional Documents
Culture Documents
Response Risk Assessment Process For Chemical Incidents
Response Risk Assessment Process For Chemical Incidents
This document was prepared as an account of work sponsored by an agency of the United States
government. Neither the United States government nor Lawrence Livermore National Security, LLC,
nor any of their employees makes any warranty, expressed or implied, or assumes any legal liability or
responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or
process disclosed, or represents that its use would not infringe privately owned rights. Reference herein
to any specific commercial product, process, or service by trade name, trademark, manufacturer, or
otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the
United States government or Lawrence Livermore National Security, LLC. The views and opinions of
authors expressed herein do not necessarily state or reflect those of the United States government or
Lawrence Livermore National Security, LLC, and shall not be used for advertising or product
endorsement purposes.
This work performed under the auspices of the U.S. Department of Energy by Lawrence Livermore
National Laboratory under Contract DE-AC52-07NA27344.
LLNL-TR-758734
LLNL-TR-758734
LLNL-TR-758734
Disclaimer
This document was prepared as an account of work sponsored by an agency of the United
States government. Neither the United States government nor Lawrence Livermore National
Security, LLC, nor any of their employees makes any warranty, expressed or implied, or assumes
any legal liability or responsibility for the accuracy, completeness, or usefulness of any
information, apparatus, product, or process disclosed, or represents that its use would not
infringe privately owned rights. Reference herein to any specific commercial product, process,
or service by trade name, trademark, manufacturer, or otherwise does not necessarily
constitute or imply its endorsement, recommendation, or favoring by the United States
government or Lawrence Livermore National Security, LLC. The views and opinions of authors
expressed herein do not necessarily state or reflect those of the United States government or
Lawrence Livermore National Security, LLC, and shall not be used for advertising or product
endorsement purposes.
i
LLNL-TR-758734
Dev Jani
Puneet Khan
Bobby Baker
Robert Greenwalt
Ellen Raber
Sav Mancieri
Michael Dillon
Heather Byrnes
Steve Harris
Kelly Heidecker
ii
LLNL-TR-758734
TABLE OF CONTENTS
iii
LLNL-TR-758734
iv
LLNL-TR-758734
TABLE OF FIGURES
Figure ES-1. RRA Operational Framework and Overarching Critical Tasks ................................................... 1
Figure 1-1. Components of the Nationals Preparedness System diagram from the DHS Threat and Hazard
Identification and Risk Assessment (THIRA) and Stakeholder Preparedness Review (SPR) Guide -
Comprehensive Preparedness Guide (CPG) 201, illustrating the emergency response planning cycle
(2012). ........................................................................................................................................................... 2
Figure 1-2. The three steps of the THIRA process (CPG 201, 2018).............................................................. 3
Figure 2-1. Timeline/Flow of RRA Meetings Related to Seven Key RRA Process Actions ............................. 6
Figure 2-2. The Response Risk Assessment process is comprised of seven key actions .............................. 7
Figure 5-1. RRA information needs illustrated as the intersection of time, resources, and conditions in
the area. ...................................................................................................................................................... 19
Figure 6-1. RRA Dashboard concept of gathering inputs to produce standardized outputs for discussion.
.................................................................................................................................................................... 27
Figure 6-2. RRA Dashboard initial startup worksheet page ........................................................................ 28
Figure 6-3. RRA Dashboard Specific Scenario data entry page for internal scenario ................................. 29
Figure 6-4. RRA Dashboard Specific Scenario data entry page for external scenario ................................ 30
Figure 6-5. RRA Dashboard Community Capabilities data entry page ....................................................... 31
Figure 6-6. RRA Dashboard Community Capabilities data entry page (continued) .................................... 32
Figure 6-7. RRA Dashboard Emergency Warning data entry page for internal scenarios .......................... 33
Figure 6-8. RRA Dashboard Emergency Warning data entry page for external scenarios ......................... 33
Figure 6-9. RRA Dashboard Fire Assignments data entry page .................................................................. 34
Figure 6-10. RRA Dashboard HAZMAT Capabilities data entry page .......................................................... 35
Figure 6-11. RRA Dashboard Medical Assignments data entry page.......................................................... 35
Figure 6-12. RRA Dashboard Transportation Assignments data entry page .............................................. 36
Figure 6-13. RRA Dashboard Output - Critical Task Timing/Resource Summary ........................................ 37
Figure 6-14. RRA Dashboard Output - Summary Plots ............................................................................... 38
v
LLNL-TR-758734
TABLE OF TABLES
Table 3-1. Summary of Select Modeling Systems ....................................................................................... 13
Table 4-1. Facilitator Team Roles and Responsibilities ............................................................................... 15
Table 5-1. Timing of Critical Actions and Decisions .................................................................................... 21
Table 5-2. Information to be Gathered During Primary, Secondary, and Tertiary Response Periods........ 22
Table 5-3. Example Planning and Response Agencies ................................................................................ 24
Table 5-4. Potential Resources for Background Research and Information Gathering .............................. 25
Table 8-1: Possible Meeting Attendees ...................................................................................................... 42
Table 8-2: Facilitator Teams for Tabletop Exercise ..................................................................................... 43
vi
LLNL-TR-758734
EXECUTIVE SUMMARY
The Department of Homeland Security (DHS) has invested significant effort to assess whether cities and
communities across the nation have the capabilities to respond effectively in the event of a potential
chemical hazard release, terrorist attack, or natural disaster. The DHS strategy per Presidential Policy
Directive 8: National Preparedness (PPD-8) is articulated in the National Preparedness Goal (2015) and
efforts to achieve that goal require a capabilities-based planning approach.
In an effort to assess these capabilities, Lawrence Livermore National Lab (LLNL) received funding from
DHS to develop a Response Risk Assessment (RRA) process for potential chemical hazard events. The
objective of the RRA process is to gather the essential information and data to evaluate limitations in
overall response capabilities using rigorous quantitative analyses that focus on minimizing casualties. At
the end of the process, a city or venue should be equipped with the actions it needs to take to meet
capability standards articulated under the DHS national preparedness strategy.
The RRA process uses the operational framework displayed in Figure ES-1 as a model to examine the
emergency response system in detail, from initiation of an incident through definitive medical care. This
operational framework is consistent with DHS/Federal Emergency Management Agency’s (FEMA)
National Response Frameworks, particularly the core capabilities, Emergency Support Functions (ESF)
(DHS, 2016) and National Incident Management System (NIMS)/Incident Command System (ICS) (DHS,
2017). The process framework is also consistent with the mission of the Department of Homeland
Security Countering Weapons of Mass Destruction (CWMD) Office (DHS, 2018).
Five municipalities across the nation worked with LLNL and DHS to implement demonstration projects
that took place in partnership with local agencies, organizations, and other key stakeholders at the state
and federal levels. Following the conclusion of the demonstration projects, LLNL prepared this
document as a manual to guide users in implementing a Response Risk Assessment (RRA) for potential
chemical hazard events.
1
LLNL-TR-758734
In addition to providing the background and foundation of the RRA approach, this document takes the
reader through each part of the entire RRA process. Key timelines, meetings, and analysis actions are
discussed and summarized in tables and figures.
Critical information requirements to establish response timelines, assess population exposure, and
consider capacity limitations that could increase casualties are presented in a manner that the RRA
facilitator may employ to guide discussions with partners. Community partners may then establish
actions for continual improvement in emergency response planning.
To get facilitators off to a running start, examples of materials, tools, questionnaires, presentations, and
templates used in an RRA are provided in the Attachments. They are encouraged to freely use and
duplicate these materials.
Finally, the document includes a summary of RRA enhancement areas and improvement opportunities
identified by individuals, agencies, municipalities, and organizations involved in the demonstration
projects. These nine enhancements are highlighted in Section 9.
2
LLNL-TR-758734
1.0 INTRODUCTION
To ensure that the United States is prepared to respond effectively to a potential chemical hazard
release, terrorist attack, or natural disaster, the Department of Homeland Security (DHS) established a
set of National Preparedness Priorities that focuses on a capabilities-based planning approach (DHS,
2006). Capabilities-based planning focuses on planning under uncertainty, since the next danger or
disaster can never be forecast with complete accuracy. As a result, the nation has been engaged in
planning and preparing for the full spectrum of existing hazards—a process which builds capabilities that
can be applied to a wide variety of incidents.
Capabilities-based planning is used to identify a baseline assessment of homeland security efforts by
comparing current capabilities against the Core Capabilities List defined in the DHS National Response
Framework (DHS, 2013) and the critical tasks associated with those Core Capabilities. This approach
identifies gaps in current capabilities and focuses efforts on identifying and developing priority
capabilities and tasks. These priority capabilities are articulated in a homeland security strategy and
Multi-year Training and Exercise Plan outlined in the Homeland Security Exercise and Evaluation
Program (HSEEP) (DHS, 2013). The 2013 HSEEP report defines the Core Capabilities as “distinct critical
elements necessary to achieve the specific mission areas of prevention, protection, mitigation,
response, and recovery.”
In 2012, Congress appropriated DHS funding to conduct demonstration projects (as part of HSEEP) to
analyze community-level response capabilities during an emergency chemical hazard release. Lawrence
Livermore National Lab (LLNL) was tasked with developing a DHS Response Risk Assessment (RRA)
process (with objectives linked to the Core Capabilities), develop a Chemical Defense Framework, and
team up with local jurisdictions to carry out these projects in the field. As a result, LLNL and DHS
established partnerships with five cities chosen from a competitive field of municipal applicants as the
demonstration project locations.
Each of these projects had a slightly different focus. Three out of the five (Baltimore, Houston, and
Boise) included a comprehensive risk assessment, which included a threat, vulnerability, and
consequence analysis. Each demonstration project concluded the project by implementing a Tabletop
Exercise (TTX). These exercises, designed to test community response capabilities based on a chemical
hazard release scenario, provided the nation’s community emergency managers and first responders
with additional knowledge, skills, and tools to act swiftly and competently, protect lives, and restore
peace of mind in response to a large-scale chemical incident. This document has been developed as a
follow-up effort to those demonstration projects. It summarizes the necessary steps to analyze response
capabilities in a user-friendly format that includes templates and guidance tools.
The RRA process is also consistent with the mission of the DHS Countering Weapons of Mass Destruction
(CWMD) Office, which it describes as “to counter attempts by terrorists or other threat actors to carry
out an attack against the United States or its interests using a weapon of mass destruction.” In
particular, the RRA process meets the CWMD strategic goals to enhance national capabilities, support
partnerships and close capability gaps, and to develop innovative technologies to meet partner
requirement and improve operations (DHS, Countering Weapons of Mass Destruction, 2018).
1.1 BACKGROUND
The strategic foundation for the RRA was established through the National Preparedness Goal (DHS,
2015), an initiative that established the National Preparedness System aimed at achieving community-
wide preparedness throughout the country.
LLNL-TR-758734
Response planning in the National Preparedness System must be viewed as a continuous cycle as
illustrated in Figure 1-1. Identifying potential
risk and hazards in combination with
scenario-based analysis leads to estimating
capacity requirements. Estimating those
requirements is followed by building and
planning for the resources required to
implement an effective response. Then, the
capabilities must be tested and validated.
That involves not only assessing current
needs and capabilities, but also challenging
and continuously improving upon core
capacities. The improvement opportunities
may then be incorporated into risk
identification and capability planning to
strengthen emergency response.
The RRA process is most closely associated
with the Identifying & Assessing Risk,
Estimating Capability Requirements, and
Validating Capabilities components of the Figure 1-1. Components of the National Preparedness System
National Preparedness System (Figure 1-1). diagram from the DHS Threat and Hazard Identification and Risk
Its focus is to examine response capabilities Assessment (THIRA) and Stakeholder Preparedness Review (SPR)
and perform a detailed review to generate Guide - Comprehensive Preparedness Guide (CPG) 201,
illustrating the emergency response planning cycle (2012).
requirements, thereby informing the
development of solutions throughout all five mission areas of the DHS National Preparedness Goal (DHS,
2015), but particularly in prevention, protection, and response.
The specific approach of the RRA process evolved from the DHS Threat and Hazard Identification and
Risk Assessment (THIRA) process (Figure 1-2), a guidance that was developed to implement the
Identifying & Assessing Risk section of the National Prevention System. [THIRA is fully outlined in the
agency’s third edition of the THIRA and Stakeholder Preparedness Review (SPR) Guide, Comprehensive
Preparedness Guide (CPG) 201 (DHS, 2018)].
Consequently, the approach driving the RRA process is most easily described using the THIRA flow
diagram in Figure 1-2 below. It has three major steps:
2
LLNL-TR-758734
Figure 1-2. The three steps of the THIRA process (CPG 201, 2018)
Step 1 is a data gathering step focused on the unique factors of the community. It is broken into three
subcategories identifying sources, possible agents, and possible community areas of concern (“targets”).
Step 2 combines the data into a set of realistic scenarios.
Step 3 examines the community’s response system and compares against the scenarios to select those
that will challenge critical parts of the system to allow analysis and gap identification. For this reason,
the scenarios selected may not be those considered the most likely, but instead are those possible
scenarios that pose the most difficulty.
Pre-incident planning is critical for an effective RRA and must be based upon credible scenarios and
information that has the appropriate level of confidence, such as quantities of deployable resources
associated with an implementable emergency response plan. Exercising response plans help to identify
opportunities for continual improvements that enhance the plan’s effectiveness. As established in the
Threat and Hazard Identification and Risk Assessment Guide Comprehensive Preparedness Guide (CPG)
201 (2018), response planning must be viewed as a continuous cycle as illustrated in Figure 1-1.
3
LLNL-TR-758734
Planning. Instructions on implementing the tabletop exercise—the last event in the RRA process—is not
covered in full, as it is beyond the scope of this document’s focus.
Because the RRA process involves several key actions taking place concurrently, the document includes
cross-references in order to provide facilitators with a “big picture” look at what needs to take place
during each stage of the process.
4
LLNL-TR-758734
5
LLNL-TR-758734
Meet with project Establish rapport and Meet in focused Validate gathered Test response
sponsor and initially project acceptance groups of decision information by capabilities using a
identified partners/ with community/ makers and boots-on- discussing inputs and predefined scenario.
stakeholders to focus venue leaders and the-ground type results of a prepared Scenario is given to
the RRA process and decision makers. professionals initial RRA. Analyze attendees at
identify additional Agree on RRA project organized by ESF or resource beginning of meeting
partners/ needs and scope. type of contribution to interdependencies and RRA is
Objective(s) stakeholders. response efforts. and identify conducted through
Gather information on opportunities to discussion of
response capabilities. expand capabilities. response actions.
Identify response
limitations and
establish
improvement actions.
• Core RRA Team • Core RRA Team • Larger RRA • Larger RRA • Larger RRA
Team Team Team
• Project Sponsor • Expanded
Partners & • Decision makers • Expanded • Expanded
• Initially Identified
Stakeholders Partners/ Partners/
Partners / • Boots-on-the-
Stakeholders Stakeholders
Attendees Stakeholders • Community/ ground
Venue Leaders professionals • Community/ • Community/
Venue Leaders Venue Leaders
• Decision Makers
• Decision Makers • Decision Makers
Initial Research
Partner Engagement
Problem Definition
Seven Key Information Gathering
Actions
Information Vetting
Capabilities Analysis
Capabilities Testing
Figure 2-1. Timeline/Flow of RRA Meetings Related to Seven Key RRA Process Actions
The process depicted in Figure 2-1 supports gathering the information required for the outputs
summarized in the seven key actions of the RRA process. Figure 2-2 below illustrates the structure of the
process through the seven key actions, which are listed in blue boxes across the top of the figure. The
main activities that must be accomplished for each key action are listed in the underlying columns.
6
LLNL-TR-758734
Identify Key Invite Decision Define Potential Identify ID Critical Vet & Refine Identify Response Test Response
Aspects of Makers & Chemical Infrastructure, Potential Scenarios With Limitations Capacity/
City/Venue Stakeholders Incident(s) Targets, Supporting Stakeholders Capability
Infrastructure, & Vulnerable Limitations
Identify Engage Partners Initial Populations Establish Analyze
Scenario for Project Assessment of Response Resources Establish
Options Acceptance Available Plans, Collect Capacity/Capability Capacities/ Interdependencies Improvement
Capacities/ Targets & Estimates Capabilities Actions
Prepare Initial Agree on Project capabilities, & Challenge
Questionnaire Needs and Resources Review Regulatory & Explore Response Prioritize
Scope Emergency Management Response Capacities/ Improvement
Identify Local Identify Key Jurisdiction Limitations Capabilities Actions
Chemical Decision Makers (choke points)
Inventories & Stakeholders Assess proximity to Identify Capacity/ Agreements &
potentially hazardous Capability Improvement
exposure Limitations Plans
Establish Scenario(s)
Figure 2-2. The Response Risk Assessment process is comprised of seven key actions
Specifically, RRA is a process that examines the emergency response systems in a community that are
called upon when responding to a mass casualty chemical incident. It assumes an incident has occurred
and identifies those functions which will be overwhelmed, a dynamic that causes additional risk to the
impacted population. The RRA procedure addresses the four overarching leverage areas highlighted in
Figure ES-1 (Prime the Pump, Early Recognition, Stop the Exposure, and Treat the Wounded) through an
operational framework (also featured in Figure ES-1) that assists in defining agency roles, critical actions,
and associated tasks.
The Operational Framework is a model to examine the emergency response system in detail, from
initiation of an incident through definitive medical care. This framework is consistent with DHS/Federal
Emergency Management Agency (FEMA)’s National Response Frameworks, particularly the core
capabilities, Emergency Support Functions (ESF) (National Response Frameworks, 2013) and National
Incident Management System (NIMS)/Incident Command System (ICS) (NIMS, 2017). (See Attachment B
for a cross-reference between critical actions of the RRA Operational Framework, FEMA Core
Capabilities, and primary ESF).
This manual presents the RRA process in the following sections: Planning and Preparation, Focus Group
Implementation, Collecting Information, Entering Data Into the RRA Dashboard, Informational
Workshop, and Tabletop Exercise Planning. Instructions on how to implement the tabletop exercise—
the last event in the process—is not covered as it is beyond the scope of this manual’s focus.
7
LLNL-TR-758734
8
LLNL-TR-758734
available, identify point of contacts (POCs) for the kick-off meeting.
4. Establish a project schedule
5. Develop the format for the kick-off meeting (including when, where, length, presentation style,
possible presenters, etc.)
3.3.2 Format/Participants
The kick-off meeting is typically a short (1-2 hour) meeting between the project sponsor, the core team
[e.g., facilitator, technical specialist(s), logistics team lead, and any additional support personnel deemed
necessary], the project coordinators, and key partners/stakeholders identified during or subsequent to
the scoping meeting. At the conclusion of the kick-off meeting, the project team will have a more
complete list of partners/stakeholders (agencies and/or POCs) to contact for follow-up facilitated focus
group meetings. Presentations for the kick-off meeting should include, at a minimum, a welcome
presentation (which would include at least one slide on the meeting objectives), and a presentation by
the project sponsor. A list of the typical meeting participants is provided in Attachment A.
9
LLNL-TR-758734
The facilitator guides the agenda and flow of the meeting,
following the format for the kick-off meeting established
during the scoping meeting. (A kick-off meeting agenda
template and example presentation template are included
in Attachments C and D. The presentation can be modified
to meet the needs of the specific RRA and kick-off meeting).
At a minimum, the presentation should include project
goals and objectives, local/venue maps and pictures, and
current demographic information.
3.3.4 Agenda
Kick-off meetings should include the following topics:
1. Welcome and introductions (project sponsor, RRA
project team, project coordinators,
partners/stakeholders)
2. Operational security [classification of project
materials, how to handle Federal For Official Use Only
(FOUO) information, protecting shared information]
3. Meeting objectives
4. Project introduction and objectives (presented by
project sponsor)
5. Review of roles, responsibilities, and resource
capabilities of relevant agencies
6. Discussion of key concerns from participants, as well
as what they hope to gain from participation in the
project
7. Identification of a wider selection of key participants
and agency POC
Based on input (given from partners/stakeholders) during
the kick-off meeting regarding roles, responsibilities, and
resources, the project team develops an initial R&R matrix
for the partners/ stakeholders. This matrix will be vetted
during facilitiated focus groups that are held prior to the
informational workshop.
10
LLNL-TR-758734
DHS facility that may be able to provide relevant Chemical Terrorism Risk Assessment (CTRA) materials.
While specific CTRA results are classified, a Subject Matter Expert (SME) may review the material and
assist in determining if initial generalized scenarios could be credible.
The facilitator gathers the information required for the RRA based on the initial draft scenario. For
example, required information will be different depending on whether the exercise is planned for an
incident occurring at an outdoor venue versus inside a building or facility. The necessary data and
information will also depend on the chemical(s) of concern and exposure pathway(s). This document has
been prepared to facilitate the collection of information required to complete a rigorous RRA.
Prior to the facilitated focus groups, simple scenario modeling is required to display a contamination
plume and assess population exposure. ALOHA (Areal Locations of Hazardous Atmospheres), an EPA
hazard modeling program commonly used to plan for and respond to chemical emergencies, can be
used for this purpose. This document discusses model selection and compares some of the more
common approaches used to generate plots, as well as the information required for the selected
scenario. Model inputs will include the release location, chemical hazard(s), wind speed and direction,
weather conditions, and other pertinent details associated with the release. Output plots, overlaid on
maps, should show an example of the extent of potentially impacted population(s) and exposure levels.
This information will help facilitate discussion with partners and stakeholders (USEPA, 2017).
◼ plots that show the chemical exposure (in the form of a plume) on a map (commonly used)
◼ videos showing how the chemical plume evolves over time
◼ maps of casualty risks (the likelihood that an injury or fatality will occur at a given location)
◼ casualty maps (expected number of people injured or killed at various locations)
It can be helpful to integrate these aids into a geographic display system (such as Esri [Earth Science
Research Institute] Geographic Information Mapping system software or the Google Earth online tool)
so focus group participants can examine the potential impacts in particular areas. Other modeling
analyses (in the form of data/information/presentations) that may be of interest include the total
number of people potentially affected, locations in which sensors are expected to be triggered, the
expected number of casualties, and the response and medical system loads (e.g., 911 calls, hospital
beds, emergency room visits). Finally, it can be helpful to develop aids that show the potential outcomes
for various critical decisions (e.g., sheltering).
11
LLNL-TR-758734
Develop the visual aids using one or more modeling systems and modelers. As there is no single
modeling system that is best for all scenarios and product types, care should be taken to select the most
appropriate resources to use based on the nature of the draft scenarios and desired products. The next
few paragraphs briefly summarize some important considerations when selecting the modeling
system/modeler. Table 3-1 below provides a brief summary of select modeling systems and tools. This
summary is not comprehensive; other modeling systems can also be used.
Physics-based modeling uses mathematical relationships to predict the consequences of a given
scenario. These systems commonly contain the following:
◼ Source term submodel (predicts how much, how fast, and in what form the chemical is released
into the environment)
◼ Fate and transport submodel (predicts where the released chemical goes, how it is transformed
and diluted)
◼ Human exposure submodel (predicts how many people are expected to receive a chemical
exposure)
◼ Health effect submodel (predicts the consequences of a chemical exposure)
Even within a given modeling system, these submodels can vary greatly in complexity and realism. As a
general rule, the more complex and/or realistic a submodel is, the more closely its results will reflect the
scenario being modeled. However, these systems require more input information and user expertise to
run and correctly interpret the results. To reduce the user/modeler burden, these systems commonly
rely on default information and in-house databases.
Since no model can predict the consequences of an event with complete accuracy, trade-offs are
inherently built into every system. Therefore, the model’s intended purpose should be considered when
evaluating the modeling system output. One important distinction is the difference between modeling
“at risk” areas where consequences might occur vs. “affected” areas where consequences are likely to
occur. Due to the challenge of obtaining reliable information during an emergency, many submodels
intended for response are designed to predict the areas and populations that are “at risk” so that
protective actions can be applied to as many potentially affected people as possible. Consequently,
systems using such submodels often overpredict the size of the geographical areas and number of
people who would potentially be affected.
12
LLNL-TR-758734
Developer U.S. Department of U.S. Environmental U.S. Department of Defense Lawrence Livermore
Transportation (DOT) Protection Agency (EPA) / Defense Threat Reductions National Laboratory (LLNL)
and Agency
Description The widely used Orange The ALOHA model provides The HPAC model can The Aeolus model can
Book provides guidance scenario-specific estimates provide scenario-specific provide scenario-specific
on potential (at risk) of potential (at risk) impact estimates of population at estimates of populations at
impact areas and initial areas. When combined with risk (common) or affected risk (common) or affected
response actions. a separate exposure (unusual). (unusual).
submodel, ALOHA can
Orange Book guidance is estimate the number of HPAC has a large variety of Aeolus uses an advanced
based on detailed people at risk. submodels that range in fate and transport submodel
modeling of transportation capability, realism, and to provide highly detailed
accidents, historical ALOHA has moderately complexity. estimates in complex urban
weather, chemical realistic (a) source term and areas.
transportation patterns, (b) fate and transport HPAC typically requires a
and predictions of submodels. significant amount of To provide high-fidelity
impacted areas for scenario information results, Aeolus requires
thousands of scenarios. ALOHA requires a moderate (depends on the submodels highly detailed input
amount of scenario used). information.
The Orange Book requires information and user
minimal scenario expertise. To reduce input To reduce input
information and user requirements, HPAC requirements, Aeolus
expertise. commonly uses previously commonly uses previously
developed default developed default
information (e.g., urban information (e.g., urban
terrain) and in-house terrain) and in-house
databases (e.g., weather). databases (e.g., weather).
13
LLNL-TR-758734
◼ law enforcement
◼ public health
14
LLNL-TR-758734
2. Developing lines of inquiry and key questions to define responder roles, responsibilities, and
resources
3. Coordinating additional information-gathering teleconferences and meetings with project
partners
Partner/stakeholder representatives will come to this meeting prepared to answer questions based on
the pre-questionnaires they have reviewed ahead of time.
Project Sponsor The Federal Department of Homeland Security (DHS) POC provides funding and direction for the
(optional) overall project. During meetings, the project sponsor presents the project background and context
within a national framework.
Facilitator The facilitator plans and manages the progress of meetings. They moderate the flow of discussions
and provide additional information and clarification when needed by being knowledgeable of the project
and familiar with the pre-defined questions. The facilitator must be prepared to keep the meeting
moving forward when discussions stall.
Moderator/Subject The moderator/SME assists the facilitator by presenting and discussing material at a more detailed
Matter Expert level. They support the facilitator in ensuring that the meeting objectives are addressed and that the
(SME) meetings stay on schedule.
Notetaker The notetaker records participant meeting responses and information documenting roles,
responsibilities, resources, and capabilities as they are provided by the various agencies. They record
the response and other pertinent information (e.g., questions, concerns, notes on path forward) on a
form where the pre-identified questions have been listed with space for notes. Following the meetings,
the notetaker compiles the notes along with those provided by planning team members and
participants (if available). The compiled information is distributed to key individuals and used to further
develop the project documents, scenario, and other related materials.
15
LLNL-TR-758734
16
LLNL-TR-758734
4.8 DOCUMENTATION
During each of the facilitated focus group meetings, notes should be taken on the various topics
discussed. Notes from each meeting should be compiled into a single document that can be checked by
each of the facilitator team members for accuracy. It should be verified that all of the information
required in Table 5-2 has been gathered and confirmed during the focus group meetings. Notes and
completed worksheets will be used to prepare for the Informational Workshop, the next meeting in the
RRA process. An explanation of the data input requirements for the RRA is provided in Attachment F.
17
LLNL-TR-758734
◼ Information for transportation nodes: If not classified, most of this information is typically
Sensitive Security Information (SSI) or Chemical-terrorism Vulnerability Information (CVI). Any
information which reveals a potential vulnerability may be classified and requires further review by
an ADC. SSI is information obtained or developed which, if released publicly, would be detrimental
to transportation security (e.g., railcars, ships, etc.) containing toxic industrial material. More
18
LLNL-TR-758734
information regarding this caveat is available through an appropriate ADC.
◼ Specific site, facility, or location characteristics: Such information incorporated into a model
directly or in the form of a database for private, public, state, or local facilities is considered FOUO
unless also designated Protected Critical Infrastructure Information (PCII). Information is FOUO
when the information, or compilation of information, is not well-known or available from open
sources. The information is unclassified when derived totally from open sources. (For all federal
sites or facilities, classification is determined by the providing federal department/agency).
Therefore, the information used for RRAs has typically been classified as FOUO. Similarly,
information derived directly from the Chemical Security Analysis Center (CSAC) retains the FOUO
designation.
As project information has been collected and needs to be released for review and use, specific
markings with appropriate caveats have been utilized upon review by the appropriate ADC. If designated
FOUO, the information has been password protected when sent over email and identified as FOUO
category with the appropriate caveats and handling requirements. A separate email containing the
password is then supplied. LLNL has used the required Department of Energy Classification box
guidelines for marking documents which has the guidance identified, review date, and name of the
appropriate ADC. The Laboratory also holds a record of the topics used for the classification review. If
this information is initially collected, reviewed, and sent out from DHS/Office of Health Affairs (OHA)
directly, different procedures/types of markings may be required.
It is imperative to discuss how the information will be handled/protected at the start of each
informational meeting and discussion-based workshop. This is important to the facility, local, and state
level organizations/agencies, and is especially of concern if other federal agencies (in addition to DHS)
are involved. LLNL has typically communicated details about information protocol with an introductory
slide when presentations are being given. Otherwise, it has verbally discussed these matters up front.
There have also been times when specific facilities have requested that LLNL sign a nondisclosure
agreement regarding all collected information. Another option used has been to employ memorandums
of understanding (MOUs) for specific geographical areas and/or venues. This will be up to the
participants to decide at that time. Using MOUs has enabled more open communication with regards to
the geographical area/venue’s potential vulnerabilities, gaps, and overall preparedness.
19
20
LLNL-TR-758734
Table 5-1. Timing of Critical Actions and Decisions
First Response
Warning Systems
Fire Response
HAZMAT
Medical
Transportation
In combination with the timing and exposure information mentioned, data that needs to be gathered
include available transportation, hospital beds, emergency triage capacity, or similar limitations as listed
in Table 5-2 below. This table specifies the critical information on timeline and resources related to
those decisions.
The first step in collecting this information is requesting documents from partners/stakeholders. The
facilitator will need to continue to gather and validate that information during the facilitated focus
groups. (A bank of possible questions to include in the information-gathering documents is provided in
Attachment E and F. The selected questions will vary depending on the initial draft scenario).
The specific information required will depend upon the scenarios being discussed. The questions in
Attachment E have been developed to be inclusive for most potential scenarios. The questions need to
be reviewed by the facilitator in advance to select the appropriate questions for the scenarios to be
discussed with the specific facilitated focus group (e.g., fire department, medical community,
transportation department). Attachment F outlines the specific information required by the RRA
Dashboard and clarifies the terms used. Facilitators should refer to Attachment F to understand the
information required to be collected during the facilitated focus group discussions.
21
LLNL-TR-758734
Table 5-2. Information to be Gathered During Primary, Secondary, and Tertiary Response Periods
The next level of information gathering will take place during the facilitated focus groups. During these
discussions, specific information required to run the tool must be collected. (For more information on
this topic, see Section 4). Table 5-2 may be used when gathering information to ensure all required
22
LLNL-TR-758734
information is collected. The discussion facilitator will enter information into Microsoft Word
documents. The information from these documents will then be pulled into the RRA tool automatically
when the analysis is run.
5.4.1 People
Using initial contacts provided by the project coordinators, the planning team conducts internet
research, cold calls, and emails, focusing on key staff from federal, state, and local regulatory response
and recovery agencies based on the initial scenario parameters. Discussions are preferably via phone
calls, but email is acceptable, particularly when the contact is difficult to reach. The following questions
are usually covered:
1. Briefly describe the project as it relates to the geographical area/venue.
2. Is the agency contact the appropriate person to participate? If not, which person should receive
authorization to participate in this project? Confirm the contact person’s information.
3. What project-related issues, questions, or concerns does the agency have that can assist the
planning team to prepare and prioritize content for subsequent meetings?
4. Is the agency contact aware of peers in related agencies that should be contacted for the same
purpose?
This process continues until the planning team and project coordinators feel that the database of
potential participants includes sufficient staff from key response and recovery agencies appropriate to
participate in planning and informational meetings. Examples of relevant response and recovery
agencies are presented in Table 5-3 below.
23
LLNL-TR-758734
Table 5-3. Example Planning and Response Agencies
Health Department Regional Railroads Health Department Centers for Disease Control
and Prevention (CDC)
Police Department/ Homeland Urban Area Security Initiative Environmental Protection Federal Bureau of
Security Office (UASI) Dept. Investigation (FBI)
Local Transportation Authority National Guard/Civil Support Agency for Toxic Substances
Team (CST) and Disease Registry
City/County Management (ATSDR)
5.4.2 Data
Data collected for the project includes both documentation and demographics. For the specific
information required in the RRA dashboard, see Table 5-2.
Documentation should include:
24
LLNL-TR-758734
─ Ports
─ Airports
─ Mass transportation terminals
─ Schools
─ Large indoor and/or outdoor venues
─ Hospitals
The collected data is used by the planning team to further develop the scenario and guidance
documents. The project team uses a data request form (refer to Attachment G) as a means of gathering
input from the agency contacts. This form is sent to the contacts along with a blank R&R matrix prior to
the facilitated focus groups. The agency contacts are requested to come to the facilitated focus groups
prepared to discuss the information. Discussions of the gathered data during these meetings will ensure
that information (roles, responsibilities, resources, and capabilities) is shared between participants,
interagency communication is improved, planning for preparation and response is coordinated, and key
or “hot topics” (that can be resolved through partnerships, training, or other efforts) is identified by
participants.
25
LLNL-TR-758734
26
LLNL-TR-758734
INFORMATION
6.1 OVERVIEW
The RRA Dashboard is a spreadsheet-based tool
that allows the user to input information gathered
from the focus groups (as described in Section 4)
and the geographical area/venue (as described in
Section 5) in combination with a specific scenario
or a general community scenario. Once the data
has been entered, the dashboard can analyze
different types of data (i.e., timelines, conditions,
and resources) and provide output (in a dashboard
format) that helps the facilitator identify where the
timelines or resources available may increase or
reduce casualties (see Figure 6-1). The facilitator
can run analyses on the dashboard based on
capabilities of organizations/agencies. Ranging
from basic to advanced, the analyses can give
insight on particular outcomes, such as an
estimated number of casualties that would result
from the scenario over time. Figure 6-1. RRA Dashboard concept of gathering inputs to produce
standardized outputs for discussion.
Conceptually, the dashboard may be thought of as
an information filter that analyzes timeline, condition, and resource data, summarizing key results that
assist the facilitator in framing a discussion on response capabilities. Key concepts to understand for the
RRA Dashboard include:
• The objective is to learn and understand, as a self-assessment.
• The output provides insight and is not meant to be absolute or model predictions.
• The tool is illustrative to compare results and allow participants to analyze and compare
scenarios.
• The range of capabilities and timing to include “likely” as well as a “least” favorable and “best”
(most favorable) inputs that may be analyzed for further improvement.
• The overall goal is to identify those actions that would have the greatest impact for optimization.
27
LLNL-TR-758734
with a defined chemical threat and release location. The “General_Community_Scenarios” tab should be
used for scenarios involving larger areas (including locations that could be impacted by a potential
chemical), with known population groups. Since these areas are larger and exposure of the population
depends on specific conditions (chemical type, weather, time of day, etc.), the tool may be employed to
focus the scenario on the areas of greatest risk/threat.
For example, when “Start a Specific Scenario” is selected, the user will be directed to the
“Specific_Scenario_Definition” tab in the “AnalysisPrePlans” workbook to identify if the incident is
internal or external. Figure 6-3 shows the worksheet for an internal release. The user needs to enter the
following information:
28
LLNL-TR-758734
◼ Building diameter: For internal scenarios, the longest linear diameter of the room in which the
release scenario would occur in meters
◼ Clothing type: Select either “hot” or “temperate” from drop down menu. This is used as a proxy of
amount of skin exposure for individuals with a chemical plume, where “hot” assumes clothing as
shorts and T-shirt and “temperate” assumes long pants and long sleeve shirt.
◼ Population: Total population in the geographical area/venue potentially exposed
◼ Security level: Whether a venue has basic security like metal detectors or backpack searches (as
opposed to uncontrolled entry).
If the scenario is external instead of internal, additional information is required for areas of potential
population exposure, the estimated population, and the percent of that population likely to be outside
at the time of the scenario (Figure 6-4). As data entry continues, separate information for each scenario
may be entered as appropriate. The output for each scenario will then be provided in a separate
“Analysis” worksheet.
Figure 6-3. RRA Dashboard Specific Scenario data entry page for internal scenario
29
LLNL-TR-758734
Figure 6-4. RRA Dashboard Specific Scenario data entry page for external scenario
Once the scenario information is filled out, continue adding gathered information to the remaining
worksheet tabs. Figures 6-5 & 6-6 show the “Community_Capabilities” tab where the information
gathered as described in Section 5 may be entered. These inputs relate to key timelines and resources
that impact overall response timing and effectiveness. They have been grouped by topic areas which
include firefighting capabilities, site operations, suppression operations, rescue and extraction,
decontamination, and community hospital data. The hospital data is required to determine available
patient capacities, travel times to and from the nearest hospital, and available medical
countermeasures.
The RRA Facilitator will input the “likely” or “initial” inputs in the white cells. This input should be
considered the planned or typical community or venue capabilities. The next two cells (blue and green)
may be used to demonstrate a range in response timing or resources as a “least” favorable or “best”
(most favorable) range of capabilities. These cells may also be used to illustrate alternative options to
compare different outcomes. The following figures include mock example data in the cells, to illustrate
implementation.
30
LLNL-TR-758734
31
LLNL-TR-758734
Figure 6-6. RRA Dashboard Community Capabilities data entry page (continued)
The “Emergency_Warning” worksheet is different for internal versus external incidents. Figure 6-7
shows the entry page for internal and Figure 6-8 for external scenarios. The data required for internal or
external scenarios are similar, including the typical times in minutes required for the specific task listed
to occur. If external areas have been identified, for example, they can each be given a different average
time to shelter-in-place.
32
LLNL-TR-758734
Figure 6-7. RRA Dashboard Emergency Warning data entry page for internal scenarios
Figure 6-8. RRA Dashboard Emergency Warning data entry page for external scenarios
33
LLNL-TR-758734
Then, the user can enter how the firefighters will be deployed in the “Fire_Assignments” worksheet.
Figure 6-9 displays an example where the number of firefighters are assigned to specific roles such as:
command, rescue, hasty decontamination, technical decontamination, non-ambulatory
decontamination, and medical support for each specific area. The total firefighters available and the
total assignment in this worksheet are listed at the top of the page.
Figure 6-10 displays the “HAZMAT_Capabilities” worksheet to enter time estimates and resources
available related to HAZMAT activities during the scenario. Similar spreadsheets for medical assignments
and transportation assignments are shown in Figures 6-11 and 6-12, respectively.
34
LLNL-TR-758734
35
LLNL-TR-758734
Once all the data entry has been completed, the RRA Dashboard may be reviewed in the “Analysis”
workbook.
In the “Analysis” workbook in the “Outcomes” worksheet, the dashboard has two main components: a
critical task timing/resource summary and summary plots. The critical task timing/resource summary
lists response actions/decisions along with the time required to make those decisions (Figure 6-13). If
any of the columns are highlighted in red with the word “critical” above it, the actions/decisions are
identified as important to the overall response capability in the specific scenario. Below each column is a
36
LLNL-TR-758734
list of those tasks that were critical in producing the result summarized. For example, the “Evacuation
(Execute)” column is red with a total of 4 minutes for the action and 10.25 minutes cumulatively since
the start of the incident. Beneath that column, the box “Evacuated” is listed as critical, meaning this
decision time was the most critical contributor to the total time required to complete this
action/decision.
The summary plots are further down on the “Outcomes” worksheet and include population exposure
(over time and total), onsite conditions (which details the number of deceased, individuals transported,
and casualties), and hospital conditions (including available beds and countermeasures) (Figure 6-14).
These plots add information to help clarify the consequences of the scenario with the timelines and
resources summarized in the critical task summary in Figure 6-13. The cumulative time for each action
(e.g., detection, warning, evacuation) is plotted. The on-site conditions display the number of individuals
that are deceased, have been transported, or remain as casualties onsite over time. Finally, the available
hospital beds over time are shown along with emergency medical countermeasures including
ventilators, bag valve masks (BVM), and oxygen used for casualties.
37
LLNL-TR-758734
The RRA Dashboard is designed to provide summary information to stimulate discussions regarding
opportunities to improve overall response capabilities. By thoroughly identifying the critical tasks that
may limit the effectiveness of response actions, the dashboard output may prompt a group to re-
examine a scenario and develop alternative assumptions for timing and actions.
Additional resources are available describing the technical details related to the RRA tool (Greenwalt
and Hibbard, 2017).
38
LLNL-TR-758734
39
LLNL-TR-758734
─ To be reviewed and completed during meeting
The workshop presentation is used to guide the meeting. (An example is attached in Attachment H). It
should have the following components:
40
LLNL-TR-758734
PATH FORWARD
The Improvement Plan will include specific actions for optimization that the local partners have
committed to track and implement. Following the Workshop and prior to a formal Table-Top Exercise,
there should be sufficient time allowed for the local partners to address opportunities and implement
action plans.
41
LLNL-TR-758734
8.2.1 Participants
In addition to the project sponsor and planning team (including the facilitator, any SMEs, and
notetakers). TTX attendees will include the partner/stakeholder representatives from the informational
workshop, plus any additional individuals that were identified as being necessary participants, or others
who would benefit from observation of the proceedings. TTX attendees can range from 50 to 70
individuals. The possible attendees are shown in Table 8-1.
Organization Organization
Fire department Federal, state, and local emergency response
organizations
Hazmat (if different than fire department) Public transportation representative(s)
Law enforcement Hospital(s) representative(s)
Facility personnel (if applicable) Coroner
The facilitator/moderator team (moderators are typically pulled from the pool of SMEs) exercises the
RRA scenario(s) by engaging the participants in a discussion of the response process using one or more
of these scenarios (covered one at a time). The participants discuss the response actions that will be
take place as the scenario unfolds. These actions will be entered into the RRA tool to produce an
assessment of the response network based on information given during the exercise.
8.2.2 Documentation
The format of the TTX is provided to the facilitators and project team in a TTX Exercise Plan (ExPlan)
following HSEEP guidance (DHS, April 2013). The ExPlan consists of the following sections:
◼ Exercise Overview
◼ Handling of Sensitive Program Information
◼ Purpose
42
LLNL-TR-758734
Project sponsor (optional) The federal DHS point of contact provides funding and direction for
the overall project. During meetings, the project sponsor presents
project background and context within a national framework.
Facilitator The facilitator plans and manages the progress of meetings and acts
in the role of response individuals and agencies not participating in
the meetings. They moderate the flow of discussions and provide
additional information and clarification when needed by being
knowledgeable of the project and familiar with the pre-defined
questions. The facilitator must be prepared with leading questions
when discussions stall.
Moderator/Subject Matter Expert (SME) The moderator/SME assists the facilitator by presenting and
43
LLNL-TR-758734
discussing material at a more detailed level. They support the
facilitator to ensure that the meeting objectives are addressed and
that the meetings stay on schedule.
44
LLNL-TR-758734
9.0 ENHANCEMENTS
This document has discussed the current RRA process as developed and applied by LLNL and DHS during
previous projects and tabletop exercises. As this process is piloted, tested, and refined new
enhancements will be documented. For example, an additional focus of this document was to
summarize the RRA process in a manner that enables new facilitators to train others in implementing
the process. Various enhancements beyond the originally developed RRA process were therefore
included in this document to meet the goal of establishing a “train the trainers” approach. It is expected
that more enhancements will be added over time (with future implementation at more geographical
areas/venues) based on the experience gained by facilitators. The RRA process may then be revised and
improved with new lessons learned. The enhancements added to the RRA process in this document
include the following:
Enhancement 1 – Enhanced process diagrams and explanatory figures
The RRA process includes many key steps and components, so diagrams and figures have been prepared
to assist facilitators in implementing the necessary actions to ensure a defendable analysis. Many of the
key concepts may now be reviewed with an illustration as well as discussion in the document text.
Enhancement 2 – Clarification of critical information needs
Information gathering is the most critical component of an effective RRA, as scenarios, local response
capabilities, specific location conditions, and available resources will be different in every analysis. This
document was designed to provide background for new RRA facilitators, so it provides a more explicit
summary of critical information requirements.
Enhancement 3 – RRA Dashboard improvements
The RRA Dashboard was modified and simplified for this document to allow the facilitator to easily
visualize results once the critical information gathered has been input into the tool. The dashboard
summarizes curves for subtasks versus casualties (RRA Dashboard) to understand outcomes in a manner
that encourages participants to discuss limitations to response capabilities.
Enhancement 4 – Clarification of alignment with National Response Framework (NRF)
In order to better communicate the RRA process to emergency response communities, it is necessary to
clearly identify how the process is consistent with and fits within the structure of the NRF. Specifically,
the interconnections have been clarified between the RRA process and Emergency Support Functions
(ESFs), as well as the Comprehensive Preparedness Guides (CPGs)—specifically CGP 201, Threat and
Hazard Identification and Risk Assessment (THIRA).
Enhancement 5 – Elaboration of potential information resources
As information gathering is critical, a summary of available resources that may potentially be used by a
new facilitator is included in this document. The goal is to ensure the best available information is
identified and used, as the quality of the RRA output is only as good as the input.
Enhancement 6 – Summary of available plume modeling systems
Chemical plume modeling is critical to assessing population exposures. However, a detailed discussion
on how to implement that modeling is beyond the scope of this document. At the same time, an RRA
facilitator needs to understand available modeling resources and where to get that assistance. A
discussion on this topic has been included in this document.
Enhancement 7 – Sample questions for use during facilitated focus group meetings
The RRA process has used a list of key questions designed to promote discussions that help gather the
necessary information to complete the RRA analysis. These questions have been organized as a resource
in the document attachments.
45
LLNL-TR-758734
Enhancement 8 – Template materials to assist with RRA implementation
Various templates have been added in the attachments to assist new facilitators with implementing the
meetings used to gather information. These templates aid the facilitators and improve consistency in
the application of the RRA process. Such consistency is critical, so that lessons from different
geographical areas/venues can be compared (and ultimately used to develop a process that will make
improvements).
Enhancement 9 – Enhanced glossary to clarify terms employed
The terms used in the RRA process must be clear to the facilitators. They must also be standardized to
allow comparison of results. A glossary has been included in this document along with an attachment
addressing terms used in the RRA Dashboard.
46
LLNL-TR-758734
10.0 REFERENCES
Department of Homeland Security (DHS) (May 2018). Countering Weapons of Mass Destruction. Link:
https://www.dhs.gov/countering-weapons-mass-destruction-office
DHS (May 2018). Threat and Hazard Identification and Risk Assessment (THIRA) and Stakeholder
Preparedness Review (SPR) Guide. Comprehensive Preparedness Guide (CPG) 201.
Link: https://www.fema.gov/media-library/assets/documents/165308
DHS (May 2016). National Response Framework, Third Edition. Link: https://www.fema.gov/media-
library-data/1466014682982-
9bcf8245ba4c60c120aa915abe74e15d/National_Response_Framework3rd.pdf
DHS (April 2013). Homeland Security Exercise and Evaluation Program (HSEEP). Link:
https://www.fema.gov/media-library-data/20130726-1914-25045-8890/hseep_apr13_.pdf
DHS (April 2012). Threat and Hazard Identification and Risk Assessment Guide: Comprehensive
Preparedness Guide (CPG) 201.
DHS (April 2012). Threat and Hazard Identification and Risk Assessment Guide: Comprehensive
Preparedness Guide (CPG) 201 – Supplement 1: Toolkit. Link: https://www.fema.gov/media-
library/assets/documents/26338
47
LLNL-TR-758734
Greenwalt, R., and Hibbard, W. (2016). Mass Casualty Chemical Incident Operational Framework,
Assessment and Best Practices: How to Assess a Community’s Response Risk along with
Recommendations and Best Practices. Livermore, CA: Lawrence Livermore National Laboratory, LLNL-
TR-701202. Link: https://e-reports-ext.llnl.gov/pdf/832745.pdf
U.S. Department of Transportation (2016). Emergency Response Guidebook (The Orange Book). Link:
https://www.phmsa.dot.gov/sites/phmsa.dot.gov/files/docs/ERG2016.pdf
48
LLNL-TR-758734
After Action Report (AAR): Summarizes key exercise-related evaluation information, including the
exercise overview and analysis of objectives and core capabilities.
Capability: Qualitative measure of the available response type for an emergency (e.g., the ability to
extract non-ambulatory casualties from a hot zone while wearing Level A personal protective
equipment)
Capacity: Quantitative measure of the available response for an emergency (e.g., the number of
personnel equipped with Level A personal protective equipment).
Crowdsourcing: Gathering information from or communicating with members of the public who are
either on scene or in contact with those on scene via social media, SMS messaging, email, and/or other
electronic media.
Chemical Stockpile Emergency Preparedness Program (CSEPP): A partnership program between FEMA
and the U.S. Department of the Army (Army) that provides emergency preparedness assistance and
resources to communities surrounding the Army’s chemical warfare agent stockpiles.
Chemical Security Analysis Center (CSAC): DHS center supporting the homeland security community by
providing a repository of crucial knowledge comprised of chemical threat information, the design and
execution of laboratory and field tests, and a science-based threat and risk analysis capability, among
other services.
Chemical Terrorism Risk Assessment (CTRA): Assessments implemented by CSAC to help the federal
government manage its resources and priorities to the appropriate level of risk. CTRA ranks chemicals by
risk based on impact of exposure, intelligence information, and modeling techniques.
Chemical Stockpile: Refers to Army chemical warfare agent stockpiles previously stored in 10 states, 40
counties, and one tribal nation.
Clinical Recognition: Identifying potentially affected individuals by a medical expert by various means
including, but not limited to education, experience, and analytical testing.
Cold Zone: The area of the site that is free from contamination. It may be safely used as a planning and
staging area. Often referred to as the support zone.
49
LLNL-TR-758734
Concept of Operations (CONOPS): A representation, usually in broad outline, of key assumptions or
intent in performing emergency management operations. A CONOPS typically includes a series of
related operations to be carried out simultaneously or in succession and is designed to give an overall
picture of the operation. It is included primarily for additional clarity of purpose.
Countermeasures: Actions taken to mitigate the damage or harm during emergency response
Critical Resources: Personnel, equipment, and supplies which allow for the ability to save lives, prevent
harm, or provide response to an emergency.
Cross-cutting: The potential for a particular emergency response to be applicable for multiple chemicals
and/or venues, locations, or geographical areas
Department of Transportation (DOT): The U.S. Department of Transportation regulates and tracks the
transport of hazardous materials on roadways, railways, and other shipping methods. DOT shipping
papers and manifests can be used by emergency responders to identify the source (sender), hazards,
and emergency actions to address an unplanned release of hazardous materials.
Discussion-Based Meetings: Methodology employed to solicit and develop realistic emergency exercise
and response scenarios based on input and feedback from emergency management personnel, first-
responders, and other key stakeholders.
Diverse (communities): Concept that various geographical areas (including but not limited to regions,
states, counties, cities, and towns) will likely have different levels of emergency response capabilities
and capacities, as will partners/stakeholders.
Emergency Support Function (ESF): The grouping of governmental and certain private sector capabilities
into an organizational structure to provide support, resources, program implementation, and services
that are most likely needed to save lives, protect property and the environment, restore essential
services and critical infrastructure, and help victims and communities return to normal following
domestic incidents.
Emergency Warning: Communication for potential harm, steps to take, and additional information
services due to a given scenario
Facilitator Team: A subset of a planning team that is comprised of the following individuals:
Facilitator – Liaison that guides partners/stakeholders through various discussions and exercises
during the RRA process
Technical Specialists – SMEs that will provide additional information as needed during the RRA
process
Logistics Team Lead – Person responsible for ensuring non-technical related details/needs for
various meetings, events, discussions, exercises, etc. are addressed. These details/needs
include, but are not limited to booking venues, food, lodging, supplies, notetaking, etc.
50
LLNL-TR-758734
First Due (firefighters): The first firefighter(s) arriving on scene. Generally, they are the first to assess the
scenario and make initial recommendations about the response.
Homeland Security Exercise and Evaluation Program (HSEEP): A FEMA document providing a set of
guiding principles for exercise programs, as well as a common approach to exercise program
management, design and development, conduct, evaluation, and improvement planning.
Hot Wash: Debrief of an agency’s performance immediately following an exercise, training, or major
real-life event.
Hot Zone: The area with actual or potential contamination and the highest potential for exposure to
hazardous substances. Often referred to as the exclusion zone.
Key Decisions: Choice points along the emergency response that can directly influence the ability to
save lives, prevent harm, or damage
National Special Security Event (NSSE): Event that the U.S. Department of Homeland Security has
classified as being particularly vulnerable to or a target of various criminal or terroristic activities.
Pre-Incident Planning: Critical details that are gathered from partners/stakeholders on all aspects of
emergency response, potential threats, and other scenario specific details for use in during the RRA
process.
Pre-scripted Messages: Prepared communications from information gathered during the risk
assessment that provides information to address specific needs for each partner/stakeholder.
Protective Actions: Actions taken to reduce or eliminate human exposure to radiation, biological,
chemical, or other hazards following an unplanned incident. Initial protective actions may be undertaken
based on models rather than actual measurements and may change over the course of an incident.
Response Risk Assessment (RRA): A process to identify where shortfalls in emergency and recovery
response capacity may increase consequences of a hazardous material incident.
Second Due (firefighters): The second firefighter(s) arriving on scene. Generally, they offer support to
the first due by providing additional man power, equipment, and/or related emergency response
capabilities.
Shelter-in-Place: Typically refers to selecting a small, interior room or other location with no or few
windows for refuge; ventilation may be limited or shut-down to reduce danger of exposure to hazardous
conditions. Actions include: closing all doors, windows, and vents (if applicable) of the currently
occupied location and remaining in a readily accessible location that puts as much
indoor/uncontaminated air between the individual and the hazardous air, such as a basement or
centrally located medium to small room; and trying to make it as airtight as possible by shutting off all
51
LLNL-TR-758734
ventilation/HVAC systems and extensively sealing the shelter's doors and windows from all outside air
contaminants with damp towels, or if available, plastic sheeting and adhesive tape.
Threat vs. Hazard vs. Risk: For this document these terms will be employed as follows:
Threat – an agent or means by which damage, harm, or adverse effect may be obtained
Risk – the chance or probability, high or low, that any hazard will cause damage, harm, or
adverse effect
Toxic Release Inventory (TRI): A federal environmental protection program and related database
detailing select hazardous material inventory and release reporting data for regulated industrial facilities
(based on Standard Industrial Classification codes) that use listed hazardous materials above specified
threshold quantities.
Warm Zone: The transition area between the hot and cold zones. This area is where responders enter
and exit the exclusion zone and where decontamination activities take place. Often referred to the
contamination reduction zone.
Whole Community: Involving people in the development of national preparedness documents and
ensuring their roles and responsibilities are reflected in the content of the materials. Whole community
includes individuals and families (including those with access and functional needs), business, faith-
based and community organizations, nonprofit groups, schools and academia, media outlets, and all
levels of government, including state, local, tribal, territorial, and federal partners.
52
LLNL-TR-758734
ATTACHMENT A:
EXAMPLE PARTNERS/STAKEHOLDERS LIST
POTENTIAL STAKEHOLDERS TO ENGAGE:
◼ Venue
─ Venue management
─ Venue public interaction staff (ushers, etc.)
─ Venue security
─ Venue first aid office
─ Facility engineer
◼ Community/County/State
─ Dispatch/911
─ Fire/HAZMAT
─ Law Enforcement
─ Public Health
─ Area Emergency Medical System
─ Community/County/State Emergency Management Staff
─ Trauma Center/Hospitals
─ Coroner
─ Local Emergency Planning Committee
─ State Bureau of Homeland Security
─ State Emergency Management Department
─ National Guard Civil Support Team (CST)
─ Regional Poison Control Center
53
LLNL-TR-758734
ATTACHMENT B:
LEVERAGE AREAS AND CRITICAL ACTIONS
LEVERAGE AREAS AND CRITICAL ACTIONS
Updated 06 February 2018
54
LLNL-TR-758734
55
LLNL-TR-758734
etc.) Enforcement
Model the Release (if Environmental Response, ESF-4; EFS-5
applicable) Health and Safety
56
LLNL-TR-758734
ATTACHMENT C:
KICK-OFF MEETING AGENDA
57
LLNL-TR-758734
ATTACHMENT D:
KICK-OFF MEETING EXAMPLE PRESENTATION
58
LLNL-TR-758734
59
LLNL-TR-758734
60
LLNL-TR-758734
61
LLNL-TR-758734
ATTACHMENT E:
QUESTIONNAIRE LIBRARY
A. Venue
1. How many air changes/hour, what is fan normal flow rate?
2. What is the average airflow rate in the populated areas?
3. How is the heating, ventilation, air conditioning (HVAC) system controlled? How long does it
take to shut it down?
4. Can the smoke extraction system be manually controlled?
5. Can the fire sprinkler system be manually controlled?
6. What are the major populated areas of the venue and what are their capacities?
7. What is the security camera coverage? How are they monitored?
8. Are pan-tilt-zoom (PTZ) cameras available?
9. What are the venue emergency services? How large and where are they?
10. How many community law enforcement and medical service units are normally staged at
this venue?
11. For what types of venue events does the CST pre-deploy?
12. Do you have chemical detection/identification means?
13. How would a warning of a chemical release be disseminated? Who would get the warning?
14. How much training do ushers and security staff have to recognize unusual situations?
15. What would happen if the detection came from: usher, first aid office, 911 dispatch, etc.?
16. How would you verify a chemical incident is occurring?
17. What decision process/system is used to initiate actions? How do you make the decision to
evacuate or shelter in place?
18. Who makes the decision to evacuate?
19. How do you evacuate people?
20. How do you handle special populations, panic, blockages during evacuation?
21. How long would evacuation take?
22. How would evacuation be controlled?
23. Do you have a shelter-in-place plan?
24. How long does it take to close off your facility (doors, etc.)?
25. How do you communicate with your staff?
26. Do you have coded announcements that alert staff to a problem?
27. How do you communicate with venue visitors?
28. Do you have prewritten announcements for the general public?
29. How do you identify visitor problems during evacuation?
30. How do you communicate with first responders?
31. Chemical hazard/threat?
32. Release characteristics? (mechanism/dispersal) (from Table 5-2)
33. Exposure pathway? (inhalation, dermal, ingestion, etc.) (from Table 5-2)
B. City
1. What population density would you have during significant events?
62
LLNL-TR-758734
2. Does the arena have big events during times that are large numbers outside on campus?
3. What type of chemical detection/identification means do you have currently?
4. What hazardous chemicals are on campus and how are they controlled?
5. How would a warning of a chemical release be disseminated? Who would get the warning?
6. What is the campus notification system?
7. What are your procedures for handling emergency situations such as fire, earthquake, bomb
threat?
8. What would you do if there were a threatening chemical release?
9. How do you implement a shelter-in-place response? With students outside?
10. What kind of emergency notification system do you have?
11. What are the City’s emergency support capabilities (medical, law enforcement, fire)?
12. What are the linkages to the local community for emergency support (fire, HAZMAT, Law
Enforcement, medical)?
C. Fire/HAZMAT
1. Describe the Fire/HAZMAT structure.
2. Who would be the initial incident commander? How would this position change as the
incident progresses?
3. Who would respond first to a reported chemical incident at the venue? (Venue &
Community)
4. What is the response time for the first fire team? The HAZMAT team?
5. Do you have the ability to generate a plume model? What do you use?
6. How would you establish and mark zones?
7. What kind of chemical detection equipment do responders have? How much?
8. How many responders have appropriate personal protective equipment (PPE) to enter the
hot zone?
9. What means do you have to decontaminate people? How much capacity? How fast can it be
setup and put into operation?
10. What toxic chemicals are shipped through the community? Are there any time restrictions?
11. Do you have a linkage to the railroad?
12. What toxic chemicals cause the most concern?
13. Number of available emergency response units on scene following dispatch? (from Table 5-
2)
14. Number of firefighters initially responding? (from Table 5-2)
15. Number of firefighters available for callup? (from Table 5-2)
16. Time for additional resources to arrive? (from Table 5-2)
17. Number of firefighters conducting source suppression? (from Table 5-2)
18. Time until first firefighter on scene following dispatch? (from Table 5-2)
19. Time for Fire Chief to assess situation? (from Table 5-2)
20. Time for firefighters to develop a plan? (from Table 5-2)
21. Time for fire fighters to implement a plan? (from Table 5-2)
22. Time for HAZMAT to arrive on scene? (from Table 5-2)
23. Time to identify hot/warm zones? (from Table 5-2)
24. Time to identify chemical released? (from Table 5-2)
63
LLNL-TR-758734
25. Time to determine PPE requirements? (from Table 5-2)
26. Time for unit to don Level A PPE? (if needed) (from Table 5-2)
27. Number of Operational teams in CPC? (from Table 5-2)
28. Time to develop a ground survey plan? (from Table 5-2)
29. Time to implement a ground survey plan? (from Table 5-2)
D. Law Enforcement
1. How would evacuation be controlled in a panic situation?
2. How would population after evacuation be controlled?
3. How is the affected area isolated to prevent additional casualties?
4. Do law enforcement officers have PPE?
5. Does law enforcement do search and rescue?
6. Is law enforcement involved in providing warning, shelter-in-place information?
7. Time to establish perimeter control/site security? (from Table 5-2)
E. Emergency Management
1. What chemical detection/identification resources do you have currently?
2. What are your procedures for standing up an Emergency Operations Center (EOC) in an
emergency – how long does it take?
3. How would a warning of a chemical release be disseminated to the emergency management
agencies? Who would get the warning?
4. How do you communicate shelter-in-place or evacuation warnings to the local area? How
long does it take?
5. How do you determine who to warn? Who makes the decision?
6. How do you communicate from the incident site with the hospitals in the area?
7. What chemicals are located in your jurisdiction and how do you keep track of their
locations?
8. Do you have the ability to generate a plume model? What do you use?
9. Who would be the initial incident commander? How would this position change as the
incident progresses?
10. Do you have access to antidotes (atropine)? How much? Where? Who can administer?
11. What mutual aid agreements are in place and what additional resources do they cover?
12. What special resources are available in the area [Civil Support Team, U.S. Environmental
Protection Agency (EPA) On-Scene Coordinator (OSC), state emergency response forces,
etc.]?
13. How do the City/County emergency plans connect to the other plans?
14. How would an affected area be searched and possible victims found and treated?
15. Time for IC to assess the situation? (from Table 5-2)
16. Time for IC to develop initial plan (Evacuation/SIP)? (from Table 5-2)
17. Time for IC to implement initial plan? (from Table 5-2)
18. Time to plan (rescue/extraction)? (from Table 5-2)
19. Time to prepare for rescue/extraction? (from Table 5-2)
20. Rescue/extraction throughput? (from Table 5-2)
21. Time to develop decontamination plan (hasty and technical decon)? (from Table 5-2)
64
LLNL-TR-758734
22. Hasty decon throughput rate? (from Table 5-2)
23. Technical decon throughput rate? (from Table 5-2)
24. Time to initiate emergency warning system? (from Table 5-2)
25. Time to identify critical resources/ sensitive targets? (from Table 5-2)
26. Time to adapt pre-scripted messages? (from Table 5-2)
27. Time to distribute emergency warning? (from Table 5-2)
28. Time to distribute ER directions (Evac/SIP, hasty decon, etc.)? (from Table 5-2)
65
LLNL-TR-758734
32. Time to deploy medical countermeasures? (from Table 5-2)
33. Number of regional medical facilities? (from Table 5-2)
34. Medical facility available capacities? (from Table 5-2)
35. Number of available ambulances? (from Table 5-2)
36. Time until additional ambulances are available? (from Table 5-2)
37. Number of additional ambulances? (from Table 5-2)
38. Number of available buses? (from Table 5-2)
39. Typical bus capacities? (from Table 5-2)
40. Time to deploy buses? (from Table 5-2)
41. Time to load and mobilize ambulances/buses for transport? (from Table 5-2)
42. Average transport speed (mph)? (from Table 5-2)
43. Time to unload and initiate return with transportation? (from Table 5-2)
66
LLNL-TR-758734
ATTACHMENT F:
RRA DASHBOARD INFORMATION REQUIREMENTS
- Wind direction – dominant direction of the wind (N, S, E, etc.), typically indicated by windows
- Typical clothes (dropdown menu) – used to determine skin exposure to chemicals, limited to a
pull-down menu of “temperate” (indicating typical clothing of pants and long-sleeved shirt) or
“hot” (indicating shorts and a t-shirt)
Emergency Management Identification and Warning (complete this section or Venue Management
Recognition and Immediate Actions)
- Time for observer report to reach 911 dispatch – time in minutes from initial recognition to initial
emergency report phone call
- Time for 911 dispatch to recognize major problem – time in minutes for dispatch to acknowledge
an emergency and verify the appropriate callout to emergency responders
- Time to dispatch responders – time in minutes from the call to first responders to arrival on scene
- Time to develop warning area [from Emergency Response Guidebook (ERG)] – time in minutes to
identify potentially impacted populations/areas requiring emergency warnings
- Time to develop warning message – time in minutes to prepare and approve required warning
message(s)
- Time to get warning message out –time in minutes required to distribute warning messages
- SIP Response Time by Population Group/Venue – time required in minutes to actually implement
SIP actions
o Complete table of Time to SIP by population group
67
LLNL-TR-758734
Venue Management Recognition and Immediate Actions (complete this section or Emergency
Management Identification and Warning)
- Typical Clothes (see above)
- Time until Security Office notified – minutes between 911 dispatch notification and security
organization notification
- Time until Security Office recognizes problem – time in minutes for security organization to
recognize an actual chemical incident is occurring
- Time to decide to EVAC – time in minutes required for Incident Commander to assess the situation
and make a decision to evacuate populations in the area
- Time to decide to shut down HVAC fans – minute required to make the decision to shut down
HVAC systems following notification and recognition of a chemical incident by the Security
Office
- Time for fans to spin down – time required in minutes for the facility HVAC system to spin down
and stop external air draw and internal distribution
- Firefighter assignments to population group locations – assign the number of firefighters that
68
LLNL-TR-758734
would be assigned to each population area identified in the scenario
- HAZMAT response estimates – list the time in minutes for the following HAZMAT activities:
o Time to size-up medical requirements – time to determine first aide actions and needs
o Time to develop EMS site plan – time to decide how to stage, segregate, and manage
casualties based on situation
o Time to initiate EMS plan – time to implement that EMS site plan
o Triage throughput/15 minutes – time required to transition a patient in and out of triage
- EMS Response Capacity – list the number and timing of resources/assets related to EMS response
including:
o EMS personnel after augmentation – number of EMTs that can be called up and added
to response as needed
o Emergency Medical Personnel Assignments to Population Group Locations – assign the
available EMS/EMT staff to the various medical assignments in this section
o Exposure Chemical – time required to confirm chemical release and identify appropriate
medical countermeasures
▪ Release Stockpile: Decision Time – time required to decide to use and deploy
medical countermeasures
▪ Medical Countermeasures Available – number of devices or doses (total
quantity and dose requirements) that may be used either at the hospital or on
site, including:
• Ventilator – number of ventilators available, with clarified:
o Application time
o Treatments/medic
• BVM – number of bag valve masks available, with clarified:
o Application time
o Treatments/medic
• Oxygen – number of oxygen tanks/masks summarized to the number of
patients that may be served, with clarified:
o Application time
o Treatments/medic
69
LLNL-TR-758734
o Time until initial ambulances available – time in minutes to initial arrival on scene
o Initial number of ambulances available – number of ambulances in the first dispatch
o Time until augmented ambulances arrive – time in minutes required for additionally
dispatched ambulances to arrive on scene
o Number of additional augmented ambulances – number of additional ambulances in the
later ambulance dispatch(es)
o Number of alternative modes of transportation – number of other transport vehicles
(buses, cars, etc.) that may be deployed to transport patients to hospitals
o Patient capacity in alternative modes of transportation – number of patients that may
be transported in the alternative modes of transportation (or seats available)
o Time until alternative modes of transportation available – time in minutes from request
to arrival of alternative modes of transportation on scene
o Time to load ambulance and begin travel – time in minutes to load and mobilize a
typical ambulance
o Average ambulance speed (mph) – typical speed achievable in the route to the hospital
in miles per hour
o Time to offload ambulance and start return – time in minutes required to remove
patient from ambulance and prepare the ambulance to return depart again to return to
the site
o Transportation assignments to Population Group Locations – assign the number of each
different transportation option in the tables provided as discussed below:
▪ Complete table, each of the following by population group
• Initial ambulance numbers
• Augmented ambulance numbers
• Alternative modes of transport options
70
LLNL-TR-758734
ATTACHMENT G:
SAMPLE STAKEHOLDER R&R DATA REQUEST FORM
Sample Stakeholder Roles & Responsibilities Data Request Form
(Option 1 – Response Capabilities)
Participant Questionnaire
Name
Name of Agency
Phone/E-Mail
Try to keep your responses brief. You may use additional pages if necessary. This information will be
made available to other participants during subsequent meetings.
What role does your organization play? Check all that apply.
Preplanning
Detection/Notification
Emergency Dispatch
71
LLNL-TR-758734
First Responder
Medical Countermeasures
Hospital Operations
Law Enforcement
Other
72
ATTACHMENT H:
SAMPLE INFORMATIONAL WORKSHOP PRESENTATION
73
74
75
76
77
78
79
80
81
82
[document classification, ex. FOR OFFICIAL USE ONLY (FOUO)]
ATTACHMENT I:
TEMPLATE FOR INFORMATIONAL WORKSHOP
AFTER-ACTION REPORT
[image]
[Community/Venue/Threat]
Response Risk Assessment
Workshop
After-Action Report (AAR)
[date]
83
[document classification, ex. FOR OFFICIAL USE ONLY (FOUO)]
This document was prepared as an account of work sponsored by an agency of the United States
government. Neither the United States government nor Lawrence Livermore National Security, LLC, nor
any of their employees makes any warranty, expressed or implied, or assumes any legal liability or
responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or
process disclosed, or represents that its use would not infringe privately owned rights. Reference herein
to any specific commercial product, process, or service by trade name, trademark, manufacturer, or
otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by
the United States government or Lawrence Livermore National Security, LLC. The views and opinions of
authors expressed herein do not necessarily state or reflect those of the United States government or
Lawrence Livermore National Security, LLC, and shall not be used for advertising or product
endorsement purposes.]
[auspices, ex. This work was performed under the auspices of the U.S. Department of Energy by
Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344.]
84
RRA Workshop After-Action Report (AAR)
TABLE OF CONTENTS
Handling Instructions............................................................................................................. 1
Confidentiality ................................................................................................................................. 1
Executive Summary ............................................................................................................... 2
Workshop Planning Team ............................................................................................................... 2
Brief Scenario .................................................................................................................................. 2
Core Capabilities Tested .................................................................................................................. 2
Overview ......................................................................................................................................... 3
Major Strengths Demonstrated ...................................................................................................... 3
Primary Areas for Improvement Identified ..................................................................................... 4
Conclusion ....................................................................................................................................... 4
Workshop Overview .............................................................................................................. 4
Workshop Design Summary and Analysis of Capabilities ........................................................ 6
Workshop Background, Purpose, and Design ................................................................................. 6
Scenario Summary .......................................................................................................................... 6
Workshop Capabilities, Objectives, Activities, and Analysis ........................................................... 7
Conclusion ……………………………………… .................................................................................... 8
Appendix A: Agenda ........................................................................................................... 1
Appendix B: Improvement Plan (IP)................................................................................... 1
Appendix C: Participating Agencies and Organizations ..................................................... 1
Appendix D: Acronyms ....................................................................................................... 2
HANDLING INSTRUCTIONS
The title of this document is the [Community/Venue/Threat] Response Risk Assessment
Workshop After-Action Report (AAR). The information gathered in this report is classified as
[document classification, ex. For Official Use Only (FOUO)] and should be handled as sensitive
information not to be disclosed. This document should be safeguarded, handled, transmitted, and
stored in accordance with appropriate security directives. Reproduction of this document, in
whole or in part, without prior approval is prohibited.
CONFIDENTIALITY
The [Community/Venue/Threat] Response Risk Assessment is an Unclassified workshop. The
control of information is based more on public sensitivity regarding the nature of the workshop
rather than the actual workshop content. Some workshop material is intended for the exclusive
use of the Planning Team, Facilitators, and Moderators, while other content is intended for
workshop participants. The AAR may be viewed by all participants.
All workshop participants should use appropriate guidelines to ensure the proper control of
information within their areas and protect this material in accordance with current United States
(US) Department of Homeland Security (DHS) or their own organization’s directives.
Workshop Detail
EXECUTIVE SUMMARY
The purpose of the Response Risk Assessment Workshop was to workshop and validate the
[Community/Venue/Threat] Response Risk Assessment (RRA) Approach to analyze, assess, and
identify improvements opportunities in response capabilities developed in accordance with the
National-level Framework for application to other cities across the country. The workshop
allowed participants to identify and examine best practices, issues, and gaps likely to be
encountered in responding to a large-scale chemical incident by testing the emergency response
capabilities.
Name Organization
BRIEF SCENARIO
THE SCENARIO INVOLVED [COMMUNITY/VENUE/THREAT]. THE SCENARIO
BEGAN WITH RELEASE OF A TOXIC CHEMICAL AND EXTENDED THROUGH ALL
OF THE RESPONSE TASKS, ENDING WITH HOSPITAL CARE.
OVERVIEW
The [Community/Venue/Threat] Response Risk Assessment Workshop held [date], at the
[location]. A copy of the Agenda is included as Appendix A. The workshop was a one-scenario,
multimedia-based workshop held during a one-day event. The moderated, discussion-based
workshop format allowed participants to interact in accordance with their respective
responsibilities and expertise to coordinate the response to, and recovery from, a large-scale
chemical incident.
The workshop began with introductions by the DHS Sponsor and [Community/Venue/Threat]
Emergency Management, followed by a presentation on the chemical properties and health
effects of the chemical to be discussed during the workshop. Prior to beginning the scenario,
review and training on the [Community/Venue/Threat] RRA processes was provided to the
participants. The remainder of the day was devoted to the scenario that involved [scenario
description] at [scenario location] and validating response capacity information gathered during
facilitated focus group meetings. Questions were asked of the participants that focused on the
actions each agency would take in response to this incident related to alert, notification, initial
response, containment, and consequence mitigation. The workshop ended with all attendees
participating in the development of a consolidated best practices and gaps table which included
assigning action owners to actions (i.e., next steps). The consolidated table is included in this
AAR as an Improvement Plan (IP) (Appendix B). The Planning Team closed the day by
conducting an internal hot wash to share their thoughts regarding the progress of the workshop.
Prior to being released for the day, participants were invited to complete a Participant Feedback
form designed to give each person an opportunity to suggest recommendations and identify
action steps for addressing areas needing improvement.
CONCLUSION
The [Community/Venue/Threat] RRA Workshop provided participants the opportunity to interact
with each other in accordance with their respective responsibilities and expertise under
controlled conditions. The workshop addressed RRA objectives and provided participants with
the opportunity to discuss information gathered during facilitated focus group meetings, best
practices, gaps, and issues related to responding to a large-scale chemical incident at
[Community/Venue/Threat]. The workshop also highlighted areas where further refinements are
needed. By addressing the recommendations contained within this report,
[Community/Venue/Threat] will be better prepared to respond to a large-scale chemical incident
occurs.
WORKSHOP OVERVIEW
The [Community/Venue/Threat] RRA Workshop focused on facility/organizational response and
coordination between the involved organizations following a large-scale chemical incident. It
was not a test of detailed response and recovery procedures, but rather a validation of the
[Community/Venue/Threat] RRA process and identification of best practices and improvement
opportunities.
[document number] 4 [Community/Venue/Threat] RRA Workshop
Location [location]
Sponsor [sponsor]
Program
Requirements [program requirements addressed]
Addressed
The workshop involved a wide-range of participants from Federal, State, and
Participating
local jurisdictional levels as well as private sector partners. The full list of
Organizations
participating agencies can be found in Appendix C.
• Prevention
• Protection
Mission Area(s) • Mitigation
• Response
• Recovery
• Operational Coordination
• Public Information and Warning
• Risk Management for Protection Programs and Activities
• Community Resilience
Core Capabilities • Operational Communications
• Environmental Response/Health and Safety
• Public Health and Medical Services
• Mass Care Services
• Fatality Management Services
The scenario involves a chemical release that results in a surge of patients and
Scenario
fatalities.
The purpose of the [Community/Venue/Threat] RRA Workshop was to test and validate
information gathered and results presented in the [Community/Venue/Threat] RRA Dashboard.
The goals were to:
• Validate RRA results based on information and analyses prepared following facilitated focus
group discussions.
• Define best practices to prepare and respond to high consequence chemical events – whether
caused by accident or terrorism.
• Use a system viewpoint to examine the problem, beginning with incident initiation and
continuing through definitive hospital care.
• Examine overlapping areas of information flow and communication, decision-making,
actions, and resources.
• Summarize improvement opportunities in critical areas, with a focus on saving lives.
SCENARIO SUMMARY
The scenario for the [Community/Venue/Threat] RRA Workshop was selected based on two basic
criteria: it had to be plausible in the [Community/Venue/Threat] environment, and it had to
challenge the different emergency response processes. Issues included:
• It had to be an [indoor/outdoor] release at the [Community/Venue/Threat].
• It had to potentially affect a large portion of the population inside the [Community/Venue/Threat].
• The chemical released had to provide early observable symptoms.
• The chemical released had to potentially result in challenges to many portions of the response system,
including decontamination processes.
Below are key observations from workshop play as they relate to the main objective: “Review
and workshop the draft Response Risk Assessment work as a means of transitioning the
information into application.” Observations are labeled as a strength (S) and/or as an area for
improvement (AFI).
Objective 1: Discuss internal incident management communication processes.
1.1 Observation (S): [example: Participants demonstrated a good understanding of
primary and supporting agencies roles and responsibilities in internal incident
management communication processes.]
Analysis: [example: During the workshop, participants demonstrated a good
understanding of the role of the Fire Department, as the primary agency with overall
Incident Command responsibilities, and those of supporting organizations (e.g. venue,
particularly the Command Post) and agencies (e.g. Emergency Management, Police
Department, and the HazMat Unit of the Fire Department) in operational areas such as
alert, notification, initial response, containment and consequence mitigation, including
means of chemical identification, suppression, rescue and recovery, decontamination,
transport, and medical services.]
1.1.1 Recommendation: [example: None.]
Objective 2: Assess information-sharing capabilities with the public, private sector partners,
and Federal, State, and local government departments and agencies.
2.1 Observation (AFI): [example: The venue Command Post can be in immediate
radio communication with Central (911) Dispatch simply by changing to a different
radio channel. Additionally, StateComm and the Bridge Call are means by which the
Participants share information with, and request additional support from, other
agencies. However, having clear, pre-scripted messages to inform the public was
identified as a gap.]
Analysis: [example: During the workshop, participants discussed several methods for
informing the public, particularly those in attendance at the venue at the time of the
incident, that a large-scale chemical incident had occurred and what to do, (e.g.
assembling outside, disrobing, rinsing with water).]
• 2.1.1 Recommendation: [example: The venue should develop customized messages for
quicker evacuation response.]
CONCLUSION
The [Community/Venue/Threat] RRA Workshop provided the [Community/Venue], stakeholder
agencies, and local jurisdictions the opportunity to review and apply the RRA process in
[Community/Venue/Threat] as a means of identifying opportunities in critical areas that focus on
saving lives in a chemical release emergency.
[document number] 8 [Community/Venue/Threat] RRA Workshop
APPENDIX A: AGENDA
RRA Validation
Note: Facilitators, Moderators, and Note-takers will also meet for about one hour after the
workshop for a debriefing.
1. Early Recognition Early identification of mass Evaluate the linkage between Emergency Management
casualty incident (MCI) event the two plans: MCI and
and initiation of MCI/HazMat HazMat (functional checklist/
protocols. training). Clarification of
threshold.
Immediate Actions
Emergency Response
Medical Treatment
Agency
Civil Support Team
Coroner’s Office
Emergency Management
Paramedics
Sheriff’s Office
Fire Department
Fire Department/Hazardous Materials Team
Police Department
State University
State University Emergency Operations Center
Central District Health Department
Bureau of Homeland Security
State Emergency Medical Services Communications Center
State Police
Regional Medical Center
Emergency Operations Center
US Department of Homeland Security/Office of Health Affairs/Chemical Defense Program
US Department of Veterans Affairs, Medical Center
Veterans’ Health Administration Office of Emergency Management
APPENDIX D: ACRONYMS
Acronym Term
AAR After-Action Report
AFI Area for Improvement
CDHD Central District Health Department
CDP Chemical Defense Project
CONOPS Concept of Operations
DHS United States Department of Homeland Security
ESF Emergency Support Function
FOUO For Official Use Only
HSEEP Homeland Security Exercise and Evaluation Program
HSPD Homeland Security Presidential Directive
HVAC Heating, ventilation, and air conditioning
ICU Intensive Care Unit
IP Improvement Plan
MCI Mass Casualty Incident
NIMS National Incident Management System
NIFC National Interagency Fire Center
OHA Office of Health Affairs
PPE Personal Protective Equipment
RRA Response Risk Assessment
S Strength
US United States
ATTACHMENT J:
TEMPLATE FOR TABLETOP EXERCISE
AFTER-ACTION REPORT
[image]
[Community/Venue/Threat]
Chemical Defense
Demonstration Project
Tabletop Exercise (TTX)
After-Action Report (AAR)
[date]
103
[document classification, ex. FOR OFFICIAL USE ONLY (FOUO)]
This document was prepared as an account of work sponsored by an agency of the United States
government. Neither the United States government nor Lawrence Livermore National Security, LLC, nor
any of their employees makes any warranty, expressed or implied, or assumes any legal liability or
responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or
process disclosed, or represents that its use would not infringe privately owned rights. Reference herein
to any specific commercial product, process, or service by trade name, trademark, manufacturer, or
otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by
the United States government or Lawrence Livermore National Security, LLC. The views and opinions of
authors expressed herein do not necessarily state or reflect those of the United States government or
Lawrence Livermore National Security, LLC, and shall not be used for advertising or product
endorsement purposes.]
[auspices, ex. This work was performed under the auspices of the U.S. Department of Energy by
Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344.]
104
TABLE OF CONTENTS
Handling Instructions............................................................................................................. 1
Confidentiality ................................................................................................................................. 1
Executive Summary ............................................................................................................... 2
Exercise Planning Team .................................................................................................................. 2
Missions Tested ............................................................................................................................... 2
Core Capabilities Tested .................................................................................................................. 3
Overview ......................................................................................................................................... 3
Major Strengths Demonstrated ...................................................................................................... 3
Primary Areas for Improvement Identified ..................................................................................... 4
Conclusion ....................................................................................................................................... 4
Exercise Overview ................................................................................................................. 4
Exercise Design Summary and Analysis of Capabilities ........................................................... 6
TTX Background, Purpose, and Design ........................................................................................... 6
Scenario Summary .......................................................................................................................... 6
Exercise Capabilities, Objectives, Activities, and Analysis .............................................................. 7
Conclusion ……………… ............................................................................................................ 8
Appendix A: Agenda ........................................................................................................ A-1
Appendix B: Improvement Plan (IP)................................................................................ B-1
Appendix C: Participating Agencies and Organizations .................................................. C-1
Appendix D: Acronyms .................................................................................................... D-2
CONFIDENTIALITY
The [Community/Venue/Threat] Chemical Defense Demonstration Project TTX is an
Unclassified exercise. The control of information is based more on public sensitivity regarding
the nature of the exercise rather than the actual exercise content. Some exercise material is
intended for the exclusive use of the Planning Team, Facilitators, and Moderators, while other
content is intended for exercise participants. The AAR may be viewed by all participants.
All exercise participants should use appropriate guidelines to ensure the proper control of
information within their areas and protect this material in accordance with current United States
(US) Department of Homeland Security (DHS) or their own organization’s directives.
EXECUTIVE SUMMARY
The purpose of the Chemical Defense Project TTX was to exercise and validate the
[Community/Venue/Threat] Operational Framework for Chemical Defense (the “Chemical
Defense Framework”) for developing a National-level Framework for application to other cities
across the country. The TTX allowed participants to identify and examine best practices, issues,
and gaps likely to be encountered in responding to a large-scale chemical incident by testing the
emergency response capabilities. The scenario involved [Community/Venue/Threat]. The
scenario began with release of a toxic chemical and extended through all of the response tasks,
ending with hospital care.
Name Organization
MISSIONS TESTED
• Prevention
• Protection
• Mitigation
• Response
• Recovery
OVERVIEW
The [Community/Venue/Threat] Chemical Defense Demonstration Project TTX was held [date],
at the [TTX location]. A copy of the Agenda is included as Appendix A. The TTX was a one-
scenario, multimedia-based exercise held during a one-day event. The moderated, discussion-
based TTX allowed participants to interact in accordance with their respective responsibilities
and expertise to coordinate the response to, and recovery from, a large-scale chemical incident.
This report adheres to Homeland Security Exercise and Evaluation Program (HSEEP) guidelines.
The TTX began with introductions by the DHS Sponsor and [Community/Venue/Threat]
Emergency Management, followed by a presentation on the chemical properties and health
effects of the chemical to be discussed during the TTX. Prior to beginning the scenario, review
and training on the [Community/Venue/Threat] Response Risk Assessment processes was
provided to the participants. The remainder of the day was devoted to the scenario that involved
[scenario description] at [scenario location]. Questions were asked of the participants that
focused on the actions each agency would take in response to this incident related to alert,
notification, initial response, containment, and consequence mitigation. The TTX ended with all
attendees participating in the development of a consolidated best practices and gaps table which
included assigning action owners to actions (i.e., next steps). The consolidated table is included
in this AAR as an Improvement Plan (IP) (Appendix B). The Planning Team closed the day by
conducting an internal hot wash to share their thoughts regarding the progress of the TTX.
Prior to being released for the day, participants were invited to complete a Participant Feedback
form designed to give each person an opportunity to suggest recommendations and identify
action steps for addressing areas needing improvement.
• Observation 2.1(AFI): [example: Participants indicated that accurate recognition of a chemical agent
and its properties may take hours, slowing the alert and assessment process, and thus potentially
increasing casualties. Participants also indicated that the threshold for a Mass Casualty Incident
(MCI) event and decontamination decision processes were not clear.]
o Recommendation 2.1.2(AFI): [example: The Fire Department and Venue should identify the
resources available for decontamination.]
CONCLUSION
The [Community/Venue/Threat] Chemical Defense Demonstration Project TTX provided
participants the opportunity to interact with each other in accordance with their respective
responsibilities and expertise under controlled conditions. The TTX addressed exercise
objectives and provided participants with the opportunity to discuss regional response best
practices, gaps, and issues related to responding to a large-scale chemical incident at
[Community/Venue/Threat]. The exercise also highlighted areas where further refinements are
needed. By addressing the recommendations contained within this report,
[Community/Venue/Threat] will be better prepared to respond to a large-scale chemical incident
occurs.
EXERCISE OVERVIEW
The [Community/Venue/Threat] Chemical Defense Demonstration Project TTX focused on
facility/organizational response and coordination between the involved organizations following a
large-scale chemical incident. It was not a test of detailed response and recovery procedures, but
rather a validation of the [Community/Venue/Threat] Chemical Defense Framework and
identification of best practices and gaps.
Location [location]
Sponsor [sponsor]
Program
Requirements [program requirements addressed]
Addressed
The TTX involved a wide-range of participants from Federal, State, and local
Participating
jurisdictional levels as well as private sector partners. The full list of
Organizations
participating agencies can be found in Appendix C.
• Prevention
• Protection
Mission Area(s) • Mitigation
• Response
• Recovery
• Operational Coordination
• Public Information and Warning
• Risk Management for Protection Programs and Activities
• Community Resilience
Core Capabilities • Operational Communications
• Environmental Response/Health and Safety
• Public Health and Medical Services
• Mass Care Services
• Fatality Management Services
The scenario involves a chemical release that results in a surge of patients and
Scenario
fatalities.
SCENARIO SUMMARY
The scenario for the [Community/Venue/Threat] Chemical Defense Project TTX was selected
based on two basic criteria: it had to be plausible in the [Community/Venue/Threat]
environment, and it had to challenge the different emergency response processes. Issues
included:
• It had to be an [indoor/outdoor] release at the [Community/Venue/Threat].
• It had to potentially affect a large portion of the population inside the [Community/Venue/Threat].
• The chemical released had to provide early observable symptoms.
• The chemical released had to potentially result in challenges to many portions of the response system,
including decontamination processes.
Below are key observations from exercise play as they relate to the main objective: “Review and
exercise the draft Chemical Defense Framework as a means of transitioning the information into
application.” Observations are labeled as a strength (S) and/or as an area for improvement (AFI).
Objective 1: Discuss internal incident management communication processes.
1.1 Observation (S): [example: Participants demonstrated a good understanding of primary
and supporting agencies roles and responsibilities in internal incident management
communication processes.]
[document number] 7[Community/Venue/Threat] Chem Defense Project TTX
Objective 2: Assess information-sharing capabilities with the public, private sector partners, and
Federal, State, and local government departments and agencies.
2.1 Observation (AFI): [example: The venue Command Post can be in immediate radio
communication with Central (911) Dispatch simply by changing to a different radio channel.
Additionally, StateComm and the Bridge Call are means by which the Participants share
information with, and request additional support from, other agencies. However, having clear,
pre-scripted messages to inform the public was identified as a gap.]
Analysis: [example: During the TTX, participants discussed several methods for
informing the public, particularly those in attendance at the venue at the time of the
incident, that a large-scale chemical incident had occurred and what to do, (e.g.
assembling outside, disrobing, rinsing with water).]
• 2.1.1 Recommendation: [example: The venue should develop customized messages for
quicker evacuation response.]
CONCLUSION
The [Community/Venue/Threat] Chemical Defense Demonstration Project TTX provided the
[Community/Venue], stakeholder agencies, and local jurisdictions the opportunity to review and
exercise the draft [Community/Venue/Threat] Chemical Defense Framework as a means of
transitioning the information into application.
Participants in the TTX included several City of [Community/Venue] departments, including
Emergency Management, the Coroner’s Office, and the Police and Fire departments, including
the Hazardous Materials Team. Also in attendance were local and Federal (Veteran’s
Administration) hospitals and private-sector partners (see Appendix C for a full list of
participating agencies and organizations).
The TTX addressed the objectives and provided an opportunity for the participating agencies and
organizations with a role in alert, notification, initial response, containment and consequence
mitigation, suppression, rescue and recovery, decontamination, transport, and medical services
processes to identify potential pitfalls and examine ways to improve collaboration. Strengths and
areas for improvement identified during the TTX have been used to develop the IP presented in
Appendix B.
Scenario Discussion
Note: Facilitators, Moderators, and Note-takers will also meet for about one hour after the
exercise for a debriefing.
6. Early Recognition Early identification of mass Evaluate the linkage between Emergency Management
casualty incident (MCI) event the two plans: MCI and
and initiation of MCI/HazMat HazMat (functional checklist/
protocols. training). Clarification of
threshold.
Emergency Response
Agency
Civil Support Team
Coroner’s Office
Emergency Management
Paramedics
Sheriff’s Office
Fire Department
Fire Department/Hazardous Materials Team
Police Department
State University
State University Emergency Operations Center
Central District Health Department
Bureau of Homeland Security
State Emergency Medical Services Communications Center
State Police
Regional Medical Center
Emergency Operations Center
US Department of Homeland Security/Office of Health Affairs/Chemical Defense Program
US Department of Veterans Affairs, Medical Center
Veterans’ Health Administration Office of Emergency Management
APPENDIX D: ACRONYMS
Acronym Term
AAR After-Action Report
AFI Area for Improvement
CDHD Central District Health Department
CDP Chemical Defense Project
CONOPS Concept of Operations
DHS United States Department of Homeland Security
ESF Emergency Support Function
FOUO For Official Use Only
HSEEP Homeland Security Exercise and Evaluation Program
HSPD Homeland Security Presidential Directive
HVAC Heating, ventilation, and air conditioning
ICU Intensive Care Unit
IP Improvement Plan
MCI Mass Casualty Incident
NIMS National Incident Management System
NIFC National Interagency Fire Center
OHA Office of Health Affairs
PPE Personal Protective Equipment
S Strength
TTX Tabletop Exercise
US United States