30.01.2013 Views

Army Emergency Management Program - Federation of American ...

Army Emergency Management Program - Federation of American ...

Army Emergency Management Program - Federation of American ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

training (Ready <strong>Army</strong>), to include evacuating, sheltering-in-place, treating the wounded, and providing critical information<br />

to first and emergency responders. These residents will take these actions well before the mass warning and<br />

notification system is activated or the first unit is on the scene. Once the mass warning and notification system is<br />

activated, past engagement through the Ready <strong>Army</strong> Campaign will have helped build the level <strong>of</strong> trust, knowledge,<br />

confidence, and aptitude to follow the protective action recommendations quickly and effectively. This consistent,<br />

positive messaging prior to an emergency extends to building the trust base required for effective EPI throughout the<br />

response and recovery phases.<br />

c. Continuity at all levels. As stated in chapter 2, successful response operations require continuity at all levels from<br />

the highest levels <strong>of</strong> government (continuity <strong>of</strong> government) to all critical or essential operations (continuity <strong>of</strong><br />

operations (COOP)) to essential services, headquarters and staff functions, tenant organizations, and commercial<br />

businesses (business continuity). The reason for the installation’s existence is to enable mission execution in support <strong>of</strong><br />

the national military strategy. The MEFs necessary to perform these missions reside in all manner <strong>of</strong> information,<br />

expertise, capabilities, and facilities. It is not operationally or financially possible to sustain all MEFs all <strong>of</strong> the time in<br />

an all-hazards environment. However, it is possible to mitigate the potential effects <strong>of</strong> these hazards to these MEFs<br />

through a comprehensive, integrated continuity program. The same applies to all <strong>of</strong> the headquarters, staff, and<br />

business functions that organize and maintain all <strong>of</strong> the necessary elements <strong>of</strong> operational readiness and community life<br />

on the installation. All <strong>of</strong> these supporting functions make up the “normalcy” that the installation is striving to achieve<br />

during the recovery phase. The sooner these functions are restored to normal operations, then the sooner the protected<br />

populace can return to a semblance <strong>of</strong> normal, daily life after an emergency. This speed to recovery is enabled first and<br />

foremost by an aggressive continuity program at every level.<br />

d. Capabilities-based planning. As stated in chapter 6, the EM program employs a capabilities-based emergency<br />

planning process as shown in figure 6–2 in order to effectively develop, employ, and sustain EM capabilities applicable<br />

across all identified hazards. These EM capabilities must be flexible enough for use in all emergencies, including<br />

unforeseen incidents, yet detailed enough to provide a course <strong>of</strong> action for installation commanders to proceed with<br />

preplanned responses to any incident.<br />

e. Core components. As stated in chapter 6, these EM capabilities shall consist <strong>of</strong> 6 core components common to the<br />

Response to all emergencies, regardless <strong>of</strong> cause. These core EM capabilities include: (1) C3, (2) mass warning and<br />

notification, (3) community preparedness, (4) first and emergency responders, (5) Public Health and Medical Services,<br />

and (6) mass care. A capability is not deemed to exist until it is properly organized, manned, trained, equipped,<br />

exercised, evaluated, maintained, and sustained. See table 2–2 for additional information.<br />

18–2. Operational environment<br />

a. Defining the operational environment. As identified in chapter 1, the operational environment in which the EM<br />

program is employed is diverse and cannot effectively be condensed into a single description. The operational<br />

environment includes a wide array <strong>of</strong> political and geographic environments, each having a unique mix <strong>of</strong> natural,<br />

technological, and terrorism hazards. In order to ensure a common reference point within incident management<br />

discussions, it is important to define the operational environment as best as possible so that the concepts described<br />

below may be put in an agreed-upon scope and context understood by all parties.<br />

b. Shared capabilities. Each jurisdiction maintains some or all <strong>of</strong> the EM Capabilities required to successfully<br />

execute the jurisdiction’s EM plan. Many <strong>of</strong> these resources may be unique to only 1 or 2 jurisdictions (such as<br />

Hospitals, HAZMAT Response capabilities, or EOD/bomb squad capabilities) yet may be required by neighboring<br />

jurisdictions should an emergency occur. Response capabilities may be organic, external, or shared resources.<br />

c. Compatibility and interoperability. The goal <strong>of</strong> the <strong>Army</strong> EM <strong>Program</strong> is to develop common standards, common<br />

terminology, and common processes for meeting the compatible priorities <strong>of</strong> the <strong>Army</strong> and the surrounding jurisdictions<br />

through the established and commonly understood processes <strong>of</strong> EM. At its core, this compatibility is achieved<br />

through mutual adoption and integration <strong>of</strong> the principles and procedures identified in NIMS. Each <strong>of</strong> these jurisdictions<br />

have their own distinct incident management requirements, but they must be able to effectively communicate and<br />

operate together at the local level, including the ability to use common terminology, exchange data across disparate<br />

information systems, and mutually support the efforts <strong>of</strong> other jurisdictions while maintaining necessary services and<br />

capabilities for their own jurisdiction. The ability to plan individually for every eventuality in an all-hazards environment<br />

does not exist within <strong>Army</strong> installations or local civil jurisdictions and both communities have therefore adopted<br />

the concept <strong>of</strong> comprehensive, integrated EM in order to develop, exercise, and maintain those common NIMS<br />

principles.<br />

d. Response timeline. As Category 5 first responders initially assess the incident and make a determination that the<br />

magnitude will overwhelm installation and local resources, the installation commander may deem it necessary to<br />

request assistance from higher levels. Type I and II installation commanders must be prepared to address response<br />

operations for Type 1–5 Incidents for a minimum <strong>of</strong> 4–6 hour while waiting for additional local, <strong>Army</strong>, State, tribal,<br />

Joint, DOD, and/or Federal (or Host Nation) assistance. Type III and IV installations shall be reliant upon Federal,<br />

State, and local (or Host Nation) assistance immediately.<br />

Note. As defined within chapter 1, there are two basic geographical groups <strong>of</strong> installations; foreign locations (overseas) and domestic<br />

locations. Installations may be further defined by their location relative to local civil jurisdictions and supporting resource providers.<br />

158 DA PAM 525–27 20 September 2012

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!