Army Emergency Management Program - Federation of American ...
Army Emergency Management Program - Federation of American ...
Army Emergency Management Program - Federation of American ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
G–5. Functional area annexes<br />
a. Concept. The FAAs shall be developed for each assigned functional area with responsibilities in developing,<br />
fielding, employing, and/or sustaining EM capabilities. FAAs shall consist <strong>of</strong> detailed guidance for each assigned<br />
functional area related to the development and execution <strong>of</strong> target EM capabilities. FAAs assign responsibility to the<br />
organization and individuals for carrying out specific actions at projected times and places in an emergency which<br />
exceeds the routine responsibility or capability <strong>of</strong> the functional area. These actions are not specific to a particular<br />
hazard, but rather focus on core common components supported by the functional area. FAAs also identify unmet<br />
needs <strong>of</strong> each Functional Area necessary for successful execution <strong>of</strong> assigned functions.<br />
b. Functional area model. Services may use the ESF-based organizational model or a functional area-based organizational<br />
model for their installation EM plans. All <strong>Army</strong> installations are directed to use a functional area-based<br />
organizational model as described in this publication. Installation commanders should note that the use <strong>of</strong> functional<br />
areas (instead <strong>of</strong> ESFs) is in compliance with all DOD and <strong>Army</strong> policy.<br />
(1) <strong>Emergency</strong> support function–based model. ESFs were designed by the Federal Government to address a problem<br />
associated with large, multi-departmental governments in that many <strong>of</strong> the same functions were performed by different<br />
departments (for example, Defense, Homeland Security, Interior, State, Commerce, and Treasury all have law enforcement<br />
components) and so one Primary Agency was necessary to coordinate and synchronize the actions <strong>of</strong> multiple<br />
departments towards the goal <strong>of</strong> providing a single function or set <strong>of</strong> similar functions. Many State Governments have<br />
adopted this same model for organizing the provision <strong>of</strong> additional capabilities and capacity to local Governments<br />
requesting assistance. See chapter 18 for a listing <strong>of</strong> ESFs.<br />
(2) Challenge. All installation EOCs need to plan for their interface with Federal, State, and possibly local<br />
operations centers utilizing ESFs in order to request and/or provide support under this model. However, the ESF<br />
concept was not designed to include all local government functions as required <strong>of</strong> an EM program or address continuity<br />
programs. CPG 101 acknowledges this issue and identifies the need for additional “locally defined ESFs” when using<br />
an ESF-based format at the local level.<br />
(3) Functional area model. Installations have the opposite challenge in that most existing functional areas provide<br />
multiple functions (for example, fire and emergency services provides functions associated in part or all <strong>of</strong> ESF #4, #8<br />
(with medical treatment facility), #9, and #10 (with Environmental <strong>Program</strong>)). The <strong>Army</strong> has determined that integrating<br />
existing functional areas is <strong>of</strong> greater importance and value to the EM program than realigning resources to a<br />
Federal structure which was not designed for local execution.<br />
c. Core requirements. All <strong>Army</strong> installations shall develop, at a minimum, one FAA per functional area as defined<br />
in the table G–13.<br />
Table G–13<br />
Functional area annex development assignments<br />
Functional areas Development lead<br />
Command, control, and communications<br />
Installation EOC (one FAA for entire function) Installation emergency manager<br />
Command section Garrison commander with installation EM<br />
Operations section DES<br />
Planning section DPTMS<br />
Logistics section DOL<br />
Finance and administration section DHR<br />
Information section (if established) Installation ATO + <strong>Army</strong> CID liaison<br />
EOC manager Installation EOC manager<br />
IT/IS support NEC<br />
Installation dispatch center DES<br />
<strong>Emergency</strong> communications NEC - IT support services<br />
Mass warning and notification system Installation emergency manager<br />
JIC PAO<br />
Key personnel<br />
Installation emergency manager Installation emergency manager<br />
Installation EOC manager Installation EOC manager<br />
DA PAM 525–27 20 September 2012<br />
249