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.

16–4. Public works<br />

a. Requirement. Each installation emergency manager shall meet on no less than a semi-annual basis with the<br />

supporting DPW representatives to ensure that public works projects, to include new building construction (military<br />

construction (MILCON)) and refurbishment or repairs <strong>of</strong> existing facilities, support the construction standards established<br />

in references UFC 4–010–01 and UFC 4–021–01, and applicable DHS, FEMA, and ARC guidance. Construction,<br />

refurbishment, and repair efforts will support the mitigation strategy for reducing the risk <strong>of</strong> facility damage due<br />

to flooding, destructive weather, seismic events, and other identified hazards.<br />

b. Issues. Key areas <strong>of</strong> concern regarding mitigation activities should be identified through the processes identified<br />

in chapters 4 and 5. These areas include the following:<br />

Utility systems, especially power distribution and water treatment/distribution.<br />

Dams and levees.<br />

Lightning and power surge protection.<br />

Landslide and mudslide containment structures.<br />

Earthquake retr<strong>of</strong>it requirements, especially in light <strong>of</strong> EO 12699 (take FEMA online course IS–8A for additional<br />

information).<br />

Note. Protection and consolidated operation <strong>of</strong> HVAC systems is identified throughout this publication as a key concern with regards<br />

to Shelter-in-Place operations. HVAC protection should also address hazard-specific temporary measures, to include screen and filter<br />

additions for volcanic ashfall incidents and for restoration <strong>of</strong> HVAC systems post-flooding incidents.<br />

16–5. Information management<br />

Each installation emergency manager shall meet on no less than a semi-annual basis with the supporting NEC<br />

representatives to ensure that information technology requirements necessary to include support mass warning and<br />

notification systems, continuity plans, installation dispatch center, installation EOC, predesignated mass care locations,<br />

and other pre-identified locations applicable to the execution <strong>of</strong> the installation EM plan are being addressed. These<br />

issues require careful, consistent, and constant coordination with the mission owners (for continuity issues), facility<br />

owners, and the applicable installation EMWG representatives to ensure that capabilities exist instead <strong>of</strong> solely wiring<br />

and hardware, to include training and exercising <strong>of</strong> personnel on new systems. These systems include failover, failback,<br />

and remote storage and access capabilities for designated continuity programs, as well as, the installation EOC and<br />

secondary EOC location.<br />

16–6. Tenant organizations and commercial businesses<br />

Each installation emergency manager shall meet on no less than a semiannual basis with the supporting tenant<br />

organization and commercial business representatives <strong>of</strong> the installation EMWG to ensure that these tenants are<br />

addressing mitigation needs in their facilities and structures. Proper business mitigation efforts support the overall<br />

mitigation strategy by reducing the risk <strong>of</strong> facility damage due to fire, flooding, destructive weather, seismic events,<br />

and other identified hazards. A best practice for this process is the use <strong>of</strong> a pre-coordinated mitigation committee<br />

session focused on this issue.<br />

16–7. Infrastructure coordination<br />

a. Critical infrastructure. Each critical infrastructure risk manager should meet on no less than a semiannual basis<br />

with the owners <strong>of</strong> critical infrastructure, such as specific utility, transportation, or other related providers or responsible<br />

agencies, to identify mitigation efforts being taken by these responsible agencies, including a review <strong>of</strong> applicable<br />

mitigation plans, if permitted by these responsible agencies. A best practice for this process is to coordinate this effort<br />

with existing regionally-based government and/or sector coordinating councils established under NIPP, when available.<br />

Critical infrastructure risk managers shall ensure that their efforts are coordinated with the installation emergency<br />

managers.<br />

b. Utility coordination. Each installation emergency manager shall meet on an as-needed basis with owners <strong>of</strong><br />

external utilities, such as power, communications, water, waste management, and sewer/wastewater companies, to<br />

identify mitigation efforts being taken by these utility owners, including a review <strong>of</strong> applicable mitigation plans, if<br />

permitted by these providers. A best practice for this process is the use <strong>of</strong> a precoordinated Mitigation Committee<br />

session focused on this issue.<br />

c. Technological hazards coordination. The same requirements exist for owners <strong>of</strong> specific technological hazards,<br />

such as dams, levees, airfields, rail transportation, mass transit systems, ferry systems, (petro) chemical facilities and<br />

related manufacturing, storage, or transportation systems, with the potential or historical impact to the <strong>Army</strong> installation.<br />

A best practice for this process is to coordinate these activities with the emergency managers <strong>of</strong> local civil<br />

jurisdictions as well as attend the LEPC meetings, where many <strong>of</strong> these agencies are represented.<br />

DA PAM 525–27 20 September 2012<br />

155

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

Saved successfully!

Ooh no, something went wrong!