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.

Federal Geographic Data Committee’s Homeland Security Working Group.<br />

ISO 19115 (Metadata standard).<br />

(c) Incident <strong>Management</strong> System. IMS is a system that integrates hardware, s<strong>of</strong>tware, and data for managing,<br />

analyzing, logging, and displaying incident-specific information in multiple views, sharing, and/or exchanging such<br />

information across multiple users. All Type I installations shall develop and manage the capability to employ a<br />

computer-based, GIS-enabled IMS in order to conduct the functions <strong>of</strong> information management, coordination, and<br />

resource management. All other installations shall utilize conventional, manual incident management capabilities, to<br />

include the employment <strong>of</strong> ICS techniques and practices such as the use <strong>of</strong> ICS forms for information management as<br />

detailed in NIMS and supporting ICS training and documentation.<br />

1. Incident <strong>Management</strong> System standards. IMS procured and fielded for use in the installation EOC environment<br />

shall comply with the following standards:<br />

Extensible markup language compliant (SEIWG ICD 0101A).<br />

EDXL common alerting protocol (CAP) v1.2 compliant (OASIS Standard).<br />

EDXL distribution element (DE) v1.0 compliant (OASIS Standard).<br />

EDXL resource messaging (RM) v1.0 compliant (OASIS Standard).<br />

Capable <strong>of</strong> developing and transmitting specific area message encoding-compliant messages.<br />

IEEE 1512, 1512.1, 1512.2, and 1512.3 compliant.<br />

Capable <strong>of</strong> managing, maintaining, accessing, and displaying NIMS resource management information, to include<br />

cost management functions.<br />

2. Domestic locations. IMS procured and fielded for use at domestic locations (as defined in chap 1) shall comply<br />

with the following additional standards:<br />

Integrated Public Alert and Warning System (IPAWS) specification to the CAP Standard (CAP v1.2 IPAWS USA<br />

Pr<strong>of</strong>ile v1.0) compliant.<br />

Integrates with National Oceanic and Atmospheric Administration (NOAA) All-Hazards <strong>Emergency</strong> Message Collection<br />

and Processing System (HAZCOLLECT).<br />

Integrates with DHS Disaster <strong>Management</strong> – Open Platform for <strong>Emergency</strong> Networks.<br />

Integrates with DHS Homeland Security Information Network.<br />

(d) Modeling and simulation systems. All Type I installations shall develop and manage the capability to employ<br />

computer-based, hazard-specific, and GIS-enabled modeling and simulation systems in order to identify current and<br />

anticipated dispersion, effects, and/or consequences <strong>of</strong> specific hazards as identified in their risk management process.<br />

All Type II and Type III installations shall utilize conventional, manual modeling capabilities, to include the employment<br />

<strong>of</strong> the techniques described in the North <strong>American</strong> <strong>Emergency</strong> Response Guide.<br />

1. Joint <strong>Program</strong> Manager–Installation Protection <strong>Program</strong> and/or <strong>Army</strong> <strong>Emergency</strong> First Responder <strong>Program</strong> Tier<br />

2 and Tier 1 Capabilities. For <strong>Army</strong> installations in receipt <strong>of</strong> these packages, predictive modeling consists <strong>of</strong> the<br />

provided hazard prediction and assessment capability, consequence assessment tool set, and Joint assessment <strong>of</strong><br />

catastrophic events suite or the EPA toolsets described below.<br />

2. U.S. Environmental Protection Agency toolsets. For all <strong>Army</strong> installations with organic fire and emergency<br />

services and/or environmental programs, the EPA provides the Area Locations <strong>of</strong> Hazardous Atmospheres, computeraided<br />

management <strong>of</strong> emergency operations, and mapping application for response, planning, and local operational<br />

tasks suite with supporting environmental sensitivity index maps and associated environmental sensitivity index viewer.<br />

See http://response.restoration.noaa.gov/index.php for additional information.<br />

3. Hazard-specific modeling systems. Hazard-specific modeling systems should be employed based upon the installation’s<br />

hazard environment. The following systems are provided by the U.S. Government and should be considered for<br />

use in the installation EOC:<br />

FEMA “Hazards, U.S. – Multi-Hazard” (HAZUS–MH) <strong>Program</strong> (http://www.hazus.org).<br />

Hurricane evacuation (HURREVAC) <strong>Program</strong> (http://www.hurrevac.com).<br />

Sea, Lake, and Overland Surges from Hurricanes <strong>Program</strong> (www.fema.gov/plan/prevent/nhp/slosh_link.shtm).<br />

USGS shake maps (earthquake.usgs.gov/earthquakes/shakemap/).<br />

FEMA Coastal Hazard Analysis Model <strong>Program</strong>.<br />

USGS Natural Hazards Support Center.<br />

Pacific Tsunami Warning Center.<br />

n. Information sharing. Installations shall identify multiple information sources both within and outside DOD (for<br />

example, open sources, general public, and law enforcement agencies) and establish and agree upon the following:<br />

o. Budget and/or resource responsibilities. The EM program and, by direct association, the VIPP MDEP resource<br />

select installation EOC requirements, including training <strong>of</strong> the installation EOC team and fielding and sustainment <strong>of</strong><br />

70 DA PAM 525–27 20 September 2012

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

Saved successfully!

Ooh no, something went wrong!