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.
installation EOC. Functional areas are responsible for resource and financial management related to life cycle management<br />
<strong>of</strong> assigned resources and this responsibility shall not be transferred to EM programs without written approval<br />
from higher headquarters.<br />
Note. The Tier One and Tier Two assets discussed below are terms established by DHS and FEMA for resource typing. There is no<br />
correlation or linkage between these asset and/or resource descriptions and the installation Tier designations 2, 1, and 0 established<br />
by JPM–IPP for the purposes <strong>of</strong> equipment fielding. NIMS resources will be listed throughout this publication with spelling <strong>of</strong> Tier<br />
One and Tier Two for delineation.<br />
b. National Incident <strong>Management</strong> System Tier One assets. To allow resources to be deployed and used on a National<br />
basis, the NIC is responsible for defining National Resource Typing standards for NIMS Tier One assets (National<br />
level resources) as defined by NIMS Guide 0001 and shown in table 9–1. NIMS Tier One assets have strict<br />
requirements regarding organization, manning, training, certification, credentialing, equipment, and - most relevant to<br />
the <strong>Army</strong> EM <strong>Program</strong> - past experience with Federal and/or State disaster declarations. Past CS operations do not<br />
count for previous experience. As all <strong>Army</strong> installation capabilities are retained under DOD control and are not<br />
Nationally deployed by FEMA independent <strong>of</strong> civil support mission assignments, DAMO–ODP has determined that<br />
none <strong>of</strong> the available NIMS Tier One typed resource definitions are applicable at the time <strong>of</strong> this publication.<br />
DAMO–ODP will remain engaged in the ongoing resource typing Initiative and update this guidance, as necessary.<br />
Table 9–1<br />
National Incident <strong>Management</strong> System Tier One Typed Resource Definitions by Guide Number<br />
Resource FEMA Guide # Resource FEMA Guide #<br />
Animal Health 508–1 Law enforcement 508–6<br />
Incident management 508–2 Bomb squad 508–6<br />
EMS 508–3 Special weapons and tactics teams 08–6<br />
Fire and emergency services 508–4 Public works resources 508–7<br />
HAZMAT response 508–4 Search and rescue (SAR) 508–8<br />
Medical response 508–5 To be determined 508–9<br />
Public health 508–5 - -<br />
c. State and local NIMS Tier Two Assets. As identified in NIMS Guide 0001, NIMS Tier Two assets are those<br />
resources defined and inventoried by local jurisdictions, including the <strong>Army</strong> EM <strong>Program</strong>, that are: (1) not Tier One<br />
resources, (2) are not assigned to interstate mutual aid deployment under EMAC. This definition includes all identified<br />
<strong>Army</strong> EM <strong>Program</strong> resources. NIMS Tier Two resource typing definitions are not distributed by the NIC to other users,<br />
including the <strong>Army</strong> EM <strong>Program</strong>. Therefore, the <strong>Army</strong> EM <strong>Program</strong> shall comply with NIMS requirements to develop<br />
standardized resource typing definitions for local EM programs to the extent possible. All installations shall implement<br />
a resource typing process based on the <strong>Army</strong> resource typing definitions provided in this publication. Installations shall<br />
type all resources identified within their jurisdiction or with which they have an approved support agreement or<br />
contract. Installations may develop local typing criteria for additional NIMS Tier Two assets identified in the planning<br />
process. Installations shall submit local typing criteria to DAMO–ODP via their supported installation-owning command<br />
for consolidation and inclusion in future updates to this publication.<br />
9–5. Financial management<br />
a. Requirements. <strong>Emergency</strong> cost accounting is a key function <strong>of</strong> the installation EOC during an emergency. The<br />
installation EOC’s finance and administration section shall develop and standardize procedures to rapidly develop and<br />
manage emergency cost accounting codes to track all emergency-related expenses, including those incurred under<br />
support agreements and support contracts, per DFAS–IN 37–100. The installation EOC’s finance and administration<br />
section shall also consolidate and forward cost estimates identified during the damage assessment process to the<br />
appropriate installation-owning command (IMCOM, AMC, USARC, ARNG) and to ASCCs as directed. It is the<br />
responsibility <strong>of</strong> installation-owning commands to develop the overarching emergency funding lines necessary to<br />
consolidate multiple emergency CACs in use by multiple installations at the same time.<br />
b. Process. The installation business <strong>of</strong>fice and/or comptroller shall develop and approve procedures for expediting<br />
fiscal decisions during emergencies consistent with established authorization levels and fiscal policy. This framework<br />
should provide for maximum flexibility to expeditiously request, receive, manage, and apply funds in a non-emergency<br />
environment and in emergency situations to ensure the timely delivery <strong>of</strong> assistance. The administrative process shall<br />
be documented through written procedures. The program should also be capable <strong>of</strong> capturing financial data for future<br />
cost recovery, as well as identifying and accessing alternative funding sources and managing budgeted and specially<br />
appropriated funds. These financial procedures shall include the following:<br />
DA PAM 525–27 20 September 2012<br />
57