Army Emergency Management Program - Federation of American ...
Army Emergency Management Program - Federation of American ...
Army Emergency Management Program - Federation of American ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
e. Process. The basic plan is developed by the installation EMWG. Drafts are usually prepared by a small<br />
subcommittee or development team and then reviewed by the entire membership on a regular basis, either virtually or<br />
during a physical meeting.<br />
(1) Summary content. The community pr<strong>of</strong>ile, personnel categorization, and risk management summary elements are<br />
usually tables or graphics representing the composite information. The results from each <strong>of</strong> these distinct efforts shall<br />
be maintained by the installation emergency manager for a period <strong>of</strong> 3 years for reference and assessment purposes.<br />
(2) Detailed content. Preparedness requirements include all organization, manning, and shift assignments including<br />
required training, certification, credentialing, equipment issue, exercise, evaluation, maintenance, and sustainment<br />
requirements and processes. The organizational requirements must be identified within the basic plan and approved by<br />
the installation commander when approving the installation EM plan. It is recommended that installation EM plans<br />
refer to manning and staffing documents as tabs or external, supporting documents that are not actually signed by the<br />
installation commander to ensure that updating these documents is not constrained by staffing requirements.<br />
(3) Operational concepts. The concepts detailed in chapters 18–19 <strong>of</strong> this publication represent notional response<br />
and recovery operations based upon a series <strong>of</strong> assumptions, which may or may not represent the local conditions at the<br />
Installation. These operational concepts establish the requirements and processes regarding the 6 common core<br />
components applicable to all emergencies regardless <strong>of</strong> cause: C3, mass warning and notification, community preparedness,<br />
first and emergency responders, public health and medical services, and mass care. The concepts should not detail<br />
procedures or processes specific to a particular hazard, as these issues are addressed in the HSAs.<br />
G–4. Support annexes<br />
a. Concept. Support annexes shall be developed by the EMWG to support identified EM capabilities requiring<br />
detailed guidance for execution, especially in the development <strong>of</strong> capabilities not established by existing DOD<br />
programs. As support annexes consist <strong>of</strong> specific guidance on the TTPs necessary for the successful completion <strong>of</strong><br />
complex tasks or functions required by the basic plan, support annexes may refer to established, published, and<br />
approved tactics, techniques, and procedures publications, modify existing TTPs based upon local conditions, or<br />
develop TTPs for tasks or functions not included in existing TTP publications.<br />
b. Development. The SAs are developed by assigned functional areas in support <strong>of</strong> the installation EMWG for final<br />
approval by the installation commander as elements <strong>of</strong> the installation EM plan.<br />
c. Content. Support annexes are developed based upon local conditions and requirements. Specific core Support<br />
Annexes are required for successful execution <strong>of</strong> assigned functions as identified below. DAMO–ODP shall identify<br />
and leverage best practices regarding SA development by providing template examples on the <strong>Army</strong> EM AKO Web<br />
site as they become available. Each SA has a recommended development matrix identifying lead and supporting<br />
functional areas assigned development responsibilities.<br />
(1) Resource management. In support <strong>of</strong> NIMS, DODI 6055.17, and NFPA 1600, all <strong>Army</strong> installations shall<br />
develop a support annex for resource management detailing the local procedures and processes for resource inventories,<br />
resource typing, and resource management across all phases <strong>of</strong> EM. This support annex will identify the procedures<br />
necessary to locate, acquire, store, distribute, maintain, test, and account for personnel, services, resources, materials,<br />
and facilities procured or donated to the EM program. These procedures will establish the following: (a) processes for<br />
describing, requesting, tracking, and taking inventory <strong>of</strong> resources, (b) procedures for activating these processes prior to<br />
and during an incident, (c) procedures to dispatch resources prior to and during an incident, (d) procedures to<br />
demobilize, deactivate, or recall resources during or after an incident, and (e) establish contingency planning process<br />
for resource shortfalls per NFPA 1600. Development will be led by the installation emergency manager in coordination<br />
with the membership <strong>of</strong> the installation EMWG. See chapter 9 for additional information. See table G–2 for development<br />
assignments.<br />
Table G–2<br />
Resource management support annex matrix<br />
Functional area Role Functional area Role Functional area Role<br />
Installation commander Approve DHR Key PAO Support<br />
Installation EMWG Support DFMWR Key RSO —<br />
Installation emergency manager Lead DPTMS Key ILO Support<br />
Installation EOC manager Support DES Key ICO Support<br />
MTF commander Support DOL Key Equal employment<br />
<strong>of</strong>fice (EEO)<br />
Garrison RMO Key DPW Key IRACO —<br />
Garrison PAIO — NEC Key ISO Support<br />
244 DA PAM 525–27 20 September 2012<br />
—
Change language