Bagram Airfield Regional Command East (RC-E) Afghanistan

Transcription

1 FINAL DRAFT EMWG Approved Version 19 Aug 2010 Approved for release to Unit Control Centers and Other C2 Functions Bagram Airfield Regional Command East (RC-E) Afghanistan EMERGENCY INTEROPERABILITY COMMUNICATIONS PLAN (EICP) August 2010 First Edition (Phase I) Ready, Able, Interoperable Developed by the Joint BAF-wide Emergency Management Working Group Subworking Group on the

2 THIS PAGE LEFT BLANK INTENTIONALLY EMWG Approved 19 August 2010 Page 1 of 37

3 INDEX EXECUTIVE SUMMARY... Page 4 SECTION I. CONOP... Pages 6-9 Part I.A. Initial Response Element CONOP... Page 8 Part I.B. Installation Control Center CONOP... Page 9 SECTION II. BAF DEFENSE ELEMENT COMMUNICATION PLANS... Pages Part II.A. TELEPHONE COMMUNICATION PLANS... Pages Part II.A.1. Non-classified Telephone Communications Plans... Page 11 Part II.A.2. SIPR Classified Telephone Communications Plans... Page 12 Part II.A.3. CENTRIXS Classified Telephone Communications Plans. Page 12 Part II.B. ELECTRONIC MAIL COMMUNICATION PLANS... Pages Part II.B.1. NIPR Communications Plans... Page 13 Part II.B.2. SIPR Communications Plans... Page 14 Part II.B.3. CENTRIXS Communications Plans... Page 14 Part II.C. RADIO-BASED COMMUNICATION PLANS... Page 15 SECTION III. EMERGENCY RESPONSE/RECOVERY ELEMENT COMMUNICATION PLANS... Pages Part III.A. TELEPHONE COMMUNICATION PLANS... Pages Part III.A.1. Non-classified Telephone Communications Plans... Pages 17 Part III.A.2. SIPR Classified Telephone Communications Plans... Pages 18 Part III.A.3. CENTRIXS Classified Telephone Communications Plans Pages 18 Part III.B. ELECTRONIC MAIL COMMUNICATION PLANS... Pages Part III.B.1. NIPR Communications Plans... Pages 19 Part III.B.2. SIPR Communications Plans... Pages 20 Part III.B.3. CENTRIXS Classified Telephone Communications Plans Pages 20 Part III.C. RADIO-BASED COMMUNICATION PLANS... Page 21 SECTION IV. INCIDENT SUPPORT ELEMENT COMMUNICATION PLANS... Pages Part IV.A. TELEPHONE COMMUNICATION PLANS... Pages Part IV.A.1. Non-classified Telephone Communications Plans... Pages 23 Part IV.A.2. SIPR Classified Telephone Communications Plans... Pages 24 Part IV.A.3. CENTRIXS Classified Telephone Communications Plans Pages 24 Part IV.B. ELECTRONIC MAIL COMMUNICATION PLANS... Pages Part IV.B.1. NIPR Communications Plans... Pages 25 Part IV.B.2. SIPR Communications Plans... Pages 26 Part IV.B.3. CENTRIXS Communications Plans... Pages 26 Part IV.C. RADIO-BASED COMMUNICATION PLANS... Page 27 SECTION V. WEB-BASED COMMON OPERATING PICTURE (COP)... Pages SECTION VI. EICP PLANNING AND EXECUTION STRATEGIES... Page EMWG Approved 19 August 2010 Page 2 of 37

4 SECTION VII. EICP FIRST EDITION (PHASE I) PRIORITIES... Page Part VII.A. Overall Priorities... Page 33 Part VII.B. BAF Defense Element... Page 33 Part VII.C. Emergency Response/Recovery Element... Page 33 Part VII.D. Incident Support Element... Page 33 SECTION VIII. EICP SECOND EDITION (PHASE II) PRIORITIES... Page Part VIII.A. Overall Priorities... Page 35 Part VIII.B. BAF Defense Element... Page 35 Part VIII.C. Emergency Response/Recovery Element... Page 35 Part VIII.D. Incident Support Element... Page 35 SECTION IX. REFERENCES... Page COLORD SHADING KEY Throughout this plan, key unit control centers will be shaded light red, green, yellow, and white. The interpretation of this shading is as follows: EMWG Approved 19 August 2010 Page 3 of 37

5 EXECUTIVE SUMMARY EMWG Approved 19 August 2010 Page 4 of 37

6 EMWG Approved 19 August 2010 Page 5 of 37

7 SECTION I. CONCEPT OF OPERATIONS (CONOP) EMWG Approved 19 August 2010 Page 6 of 37

8 SECTION I.A. INITIAL RESPONSE ELEMENT CONOP (Normal Comm Ops) The following is executed during initial incident response in any scenario where Bagram Airfield (BAF) first responder assets are required and are on scene prior to activation of installation-level C2 support [i.e., TF Wolverine Brigade Tactical Operations Center (TOC), Crisis Action Team (CAT)/Command Post (CP), Emergency Operations Center (EOC); Unit Control Centers (UCCs), Sector Control Centers (SCCs), etc.]. ROE: First responder on scene assumes incident command and should proceed on primary designated channel. If existing communication traffic is in motion (simultaneous incident) and/or EOC directs movement to another channel, IC should move to secondary/tertiary channels, as required. INCIDENT 911 Call or Other Initial Response Initiation First Responders Arrive on Scene: Fire / Security Forces (SFS) & Provost Marshal Office (PMO) / Medical Responders Incident Command Established ITT Fire SFS/PMO Medical Incident 1 Incident 2 Incident 3 Incident 1 Incident 2 Incident 3 Incident 1 Incident 2 Incident 3 ITT Fire Alarm Dispatch Center (FADC) SFS Law Enforcement Desk (LED) Medical Control Center (MCC), Other M2 Nodes Figure 1. Initial Incident Response Command and Control (C2) Incident 1 Incident 2 Incident 3 = Primary: TX MHz / RX MHz = Secondary: TX MHz / RX MHz = Tertiary: TX MHz / RX MHz EMWG Approved 19 August 2010 Page 7 of 37

9 SECTION I.B. INSTALLATION CONTROL CENTER CONOP (Emerg Comm Ops) Emergency Communications Operations are executed following initial base incident response (Part I.A.) under any of the following scenarios: A. Activation of the Emergency Operations Center (EOC). B. Incident Commander declares execution of Emergency Comm Plan (typically after incident entry control point(s)/cordon(s) have been established). C. TF Wolverine Brigade TOC Commander, Wing Commander (or designee), Emergency Operations Center (EOC) Director, Installation Emergency Manager, and/or Public Health Emergency Officer (PHEO) declare execution of Emergency Comm Plan. D. During exercises and other readiness training whereby Emergency Comm Ops has been directed in, and authorized by, the exercise plan/master Schedule Events List (MSEL). Emergency Communications Operations may also be declared prior to any base incident under the following conditions: A. TF Wolverine Brigade TOC Commander, Wing Commander (or designee), and/or Public Health Emergency Officer (PHEO) declare execution of Emergency Comm Plan to establish a readiness posture in anticipation of/in preparation for an emergency event (i.e., FPCON change, intelligence suggesting an attack/incident is imminent, etc.). B. In the execution of unplanned BAF Battle Drills, and as authorized/directed by the appropriate authority. Figure 2. Installation Control Center Command and Control (C2) Structure EMWG Approved 19 August 2010 Page 8 of 37

10 THIS PAGE LEFT BLANK INTENTIONALLY EMWG Approved 19 August 2010 Page 9 of 37

11 SECTION II. BAF DEFENSE ELEMENT COMMUNICATION PLANS EMWG Approved 19 August 2010 Page 10 of 37

12 SECTION II.A. BAF DEFENSE ELEMENT TELEPHONE COMMUNICATION PLANS ROE: Non-classified telephone shall be the primary means of communications across the installation control center s (ICC s) BAF Defense Element. SIPR and CENTRIXS telephones shall be the secondary and tertiary means, respectively. SECTION II.A.1. BAF DEFENSE ELEMENT NON-CLASSIFIED TELEPHONE Figure 3. BAF Defense Element Non-Classified Phone Communications Plan EMWG Approved 19 August 2010 Page 11 of 37

13 SECTION II.A.2. BAF DEFENSE ELEMENT SIPR (CLASSIFIED) TELEPHONE Figure 4. BAF Defense Element SIPR-Classified Phone Communications Plan SECTION II.A.3. BAF DEFENSE ELEMENT CENTRIXS (CLASSIFIED) TELEPHONE Figure 5. BAF Defense Element CENTRIXS-Classified Phone Communications Plan EMWG Approved 19 August 2010 Page 12 of 37

14 SECTION II.B. BAF DEFENSE ELEMENT ELECTRONIC MAIL COMMUNICATION PLANS ROE: NIPR classified shall be the primary means of communications across the installation control center s (ICC s) BAF Defense Element. CENTRIXS and SIPR shall be the secondary and tertiary means, respectively. Classification requirements of an intended message override these designations (e.g., if a message MUST be classified, then NIPR MUST NOT be used). The EICP Subworking Group recommends that all ICC units maintain organizational accounts and/or organizational distribution lists which are easily located on the respective Global Address Lists (GALs). Organizational accounts and distribution lists allow for enduring access across the ICC in spite of transient personnel. SECTION II.B.1. BAF DEFENSE ELEMENT NON-CLASSIFIED (NIPR) ELECTRONIC MAIL Figure 6. BAF Defense Element NIPR Communications Plan EMWG Approved 19 August 2010 Page 13 of 37

15 SECTION II.B.2. BAF DEFENSE ELEMENT SIPR (CLASSIFIED) ELECTRONIC MAIL Figure 7. BAF Defense Element SIPR Communications Plan SECTION II.B.3. BAF DEFENSE ELEMENT CENTRIXS (CLASSIFIED) ELECTRONIC MAIL Figure 8. BAF Defense Element CENTRIXS Communications Plan EMWG Approved 19 August 2010 Page 14 of 37

16 SECTION II.C. BAF DEFENSE ELEMENT RADIO-BASED COMMUNICATION PLANS ROE: Radio communication shall be the emergency means of communications across the Installation Control Center s (ICC s) BAF Defense Element. REMOVED FOR FOUO STATUS REMOVED FOR FOUO STATUS Figure 9. BAF Defense Element Radio Communications Plan EMWG Approved 19 August 2010 Page 15 of 37

17 SECTION III. EMERGENCY RESPONSE/RECOVERY ELEMENT COMMUNICATION PLANS EMWG Approved 19 August 2010 Page 16 of 37

18 SECTION III.A. EMERGENCY RESPONSE/RECOVERY ELEMENT TELEPHONE COMMUNICATION PLANS ROE: Non-classified telephone shall be the primary means of communications across the installation control center s (ICC s) Emergency Response/Recovery Element. SIPR and CENTRIXS telephones shall be the secondary and tertiary means, respectively. Incident in Base Operating Support Integrator (BOS-I) Area: If an incident occurs within the BOS-I operational area, the 86th BSTB/CO, or designated representative, will fulfill the role as the EOC Director and the 455 AEW will provide a liaison officer for mutual support. Incident in Senior Airfield Authority (SAA) Area: If an incident occurs within the SAA operational area, the 455 EMSG/CD, or designated representative, will fulfill the role as the EOC Director and TF Wolverine will provide a liaison officer for mutual support. BOS-I and SAA Simultaneous Incidents: If simultaneous incidents occur or if one incident affects both operational areas, both the 86 BSTB/CO and the 455 EMSG/CD, or designated representatives, will fulfill the role as the EOC director, responsible for their specific operational areas and providing mutual support to the other s response and recovery efforts. BOS-I is responsible for prioritizing base-wide assets, not organic to TF Wolverine or the 455 AEW, needed to assist in response and recovery efforts. SECTION III.A.1. EMERGENCY RESPONSE/RECOVERY ELEMENT NON-CLASSIFIED TELEPHONE Figure 10. Emergency Response/Recovery Element Non-Classified Phone Comm. Plan EMWG Approved 19 August 2010 Page 17 of 37

19 SECTION III.A.2. EMERGENCY RESPONSE/RECOVERY ELEMENT SIPR (CLASSIFIED) TELEPHONE Figure 11. Emergency Response/Recovery Element SIPR-Classified Phone Comm. Plan SECTION III.A.3. EMERGENCY RESPONSE/RECOVERY ELEMENT CENTRIXS (CLASSIFIED) TELEPHONE Figure 12. Emergency Response/Recovery Element CENTRIXS-Classified Phone Comm. Plan EMWG Approved 19 August 2010 Page 18 of 37

20 SECTION III.B. EMERGENCY RESPONSE/RECOVERY ELEMENT ELECTRONIC MAIL COMMUNICATION PLANS ROE: NIPR-classified shall be the primary means of communications across the installation control center s (ICC s) Emergency Response/Recovery Element. SIPR and CENTRIXS shall be the secondary and tertiary means, respectively. Classification requirements of an intended message override these designations (e.g., if a message MUST be classified, then NIPR MUST NOT be used). The EICP Subworking Group recommends that all ICC units maintain organizational accounts and/or organizational distribution lists which are easily located on the respective Global Address Lists (GALs). Organizational accounts and distribution lists allow for enduring access across the ICC in spite of transient personnel. SECTION III.B.1. EMERGENCY RESPONSE/RECOVERY ELEMENT NON-CLASSIFIED (NIPR) ELECTRONIC MAIL Figure 13. Emergency Response/Recovery Element NIPR Communications Plan EMWG Approved 19 August 2010 Page 19 of 37

21 SECTION III.B.2. EMERGENCY RESPONSE/RECOVERY ELEMENT SIPR (CLASSIFIED) ELECTRONIC MAIL Figure 14. Emergency Response/Recovery Element SIPR Communications Plan SECTION III.B.3. EMERGENCY RESPONSE/RECOVERY ELEMENT CENTRIXS (CLASSIFIED) ELECTRONIC MAIL Figure 15. Emergency Response/Recovery Element CENTRIXS Comm. Plan EMWG Approved 19 August 2010 Page 20 of 37

22 SECTION III.C. EMERGENCY RESPONSE/RECOVERY ELEMENT RADIO-BASED COMMUNICATION PLANS ROE: Radio communication shall be the emergency means of communications across the installation control center s (ICC s) Emergency Response/Recovery Element. Figure 16. Emergency Response/Recovery Element Radio Communications Plan EMWG Approved 19 August 2010 Page 21 of 37

23 SECTION IV. INCIDENT SUPPORT ELEMENT COMMUNICATION PLANS EMWG Approved 19 August 2010 Page 22 of 37

24 SECTION IV.A. INCIDENT SUPPORT ELEMENT TELEPHONE COMMUNICATION PLANS ROE: For Emergency Operations Center to other control center traffic, non-classified telephone shall be the primary means of communications across this aspect of the installation control center s (ICC s) Emergency Response/Recovery Element. SIPR and CENTRIXS telephones shall be the secondary and tertiary means, respectively. [NOTE: For Emergency Operations Center to Incident Commander (IC) traffic, radio communications shall be the primary means of communications across this aspect of the installation control center s (ICC s) Emergency Response/Recovery Element.] SECTION IV.A.1. INCIDENT SUPPORT ELEMENT NON-CLASSIFIED TELEPHONE Figure 17. Incident Support Element Non-Classified Phone Communications Plan EMWG Approved 19 August 2010 Page 23 of 37

25 SECTION IV.A.2. INCIDENT SUPPORT ELEMENT SIPR (CLASSIFIED) TELEPHONE Figure 18. Incident Support Element SIPR Phone Communications Plan SECTION IV.A.3. INCIDENT SUPPORT ELEMENT CENTRIXS (CLASSIFIED) TELEPHONE Figure 19. Incident Support Element CENTRIX Phone Communications Plan EMWG Approved 19 August 2010 Page 24 of 37

26 SECTION IV.B. INCIDENT SUPPORT ELEMENT ELECTRONIC MAIL COMMUNICATION PLANS ROE: Non-classified shall be the primary means of communications across the installation control center s (ICC s) Incident Support Element. SIPR and CENTRIXS shall be the secondary and tertiary means, respectively. Classification requirements of an intended message override these designations (e.g., if a message MUST be classified, than NIPR MUST NOT be used). The EICP Subworking Group recommends that all ICC units maintain organizational accounts and/or organizational distribution lists which are easily located on the respective Global Address Lists (GALs). Organizational accounts and distribution lists allow for enduring access across the ICC in spite of transient personnel. SECTION IV.B.1. INCIDENT SUPPORT ELEMENT NON-CLASSIFIED (NIPR) ELECTRONIC MAIL Figure 20. Incident Support Element NIPR Communications Plan EMWG Approved 19 August 2010 Page 25 of 37

27 SECTION IV.B.2. INCIDENT SUPPORT ELEMENT SIPR (CLASSIFIED) ELECTRONIC MAIL Figure 21. Incident Support Element SIPR Communications Plan SECTION IV.B.3. INCIDENT SUPPORT ELEMENT CENTRIXS (CLASSIFIED) ELECTRONIC MAIL Figure 22. Incident Support Element CENTRIXS Communications Plan EMWG Approved 19 August 2010 Page 26 of 37

28 SECTION IV.C. INCIDENT SUPPORT ELEMENT RADIO-BASED COMMUNICATION PLANS ROE: For Emergency Operations Center to Incident Commander (IC) traffic, radio communications shall be the primary means of communications across this aspect of the installation control center s (ICC s) Emergency Response/Recovery Element. In the event there are simultaneous incidents with multiple ICs, the EOC Director shall direct ICs to respective IC radio channels. Primary channels accessible to all ICs are: Incident 1, Incident 2, and Incident 3. In the event there are more than 3 incidents at once, the EOC Director shall consult with the ESF 14 (Comm Recovery/Mitigation) assigned representatives to designate channels for incidents 4 and beyond, based on the communications capabilities of the ICs at such sites. Figure 23. Incident Support Element Radio Communications Plan EMWG Approved 19 August 2010 Page 27 of 37

29 SECTION V. WEB-BASED COMMON OPERATING PICTURE (COP) EMWG Approved 19 August 2010 Page 28 of 37

30 SECTION V. WEB-BASED COMMON OPERATING PICTURE (COP) BAF Incident Command (BIC) CENTRIXS Address: ROE: Though the BIC currently resides on both the SIPR and CENTRIXS Portals, all Installation Control Center (ICC) Elements are directed to use the CENTRIXS platform as the primary means of maintaining real-time awareness of (and inputs into) a given incident s webbased tracking. Figure 24. Web-Based COP EMWG Approved 19 August 2010 Page 29 of 37

31 SECTION VI. EICP PLANNING AND EXECUTION STRATEGIES EMWG Approved 19 August 2010 Page 30 of 37

32 SECTION VI. EICP PLANNING AND EXECUTION STRATEGIES STRATEGIC DESIGN: The BAF EMWG s Emergency Interoperability Communications Plan (EICP) Subworking Group utilized a deliberate, strategic process to formulate the first edition of this written EICP. The process began with assessment of applicable Federal and DoD guidance for emergency interoperable communications planning. In addition, the U.S. Air Force model for National Incident Management System (NIMS) compliance, known as Air Force Incident Management System (AFIMS), was used as the foundation for the straw man communications model. INSTALLATION CONTROL CENTER (ICC) CONCEPT: The backbone of the EICP assumes that an Installation Control Center (ICC) exists at BAF with three distinct, yet interdependent, elements: (1) the BAF Defense Element, (2) the Emergency Response/Recovery Element, and (3) the Incident Support Element. A basic premise of the plans development was first to identify common operating capabilities across a variety of mediums, and then to use the most common denominator mediums as the primary, secondary, and tertiary forms of communications. FIRST EDITION (PHASE 1 VISION): The EICP Subworking Group agreed at its initial planning sessions agreed that a phased approach to EICP development would be the most ideal course of action. The vision for the first edition was to produce a comprehensive emergency communications plan that captured the existing capabilities and limitations of the various ICC elements. DEVELOPMENTAL STEPS: (1) Solicit Communication Capabilities Assessments from All Key Control Centers/Organizations (2) Identify Communications/Signal Action Officers for each Communication Area (Phone, Radio, Electronic Mail) (3) Await Results of CJTF-101 EM OPT CONOP Development Results (will produce C2 picture) (4) Map Key Organizations and Control Centers Against Formal C2 Structure to Produce an Emergency Communications CONOP (Draft Foundation/Skeleton Plan) (5) Map Existing Comm Capabilities and Assess New Requirements Based on Formal C2 Flow (6) Address Gaps and Bottlenecks; Establish Redundancies (7) Develop Final Draft EICP; Test Plan/Validate Capabilities (8) Modify Plan Based on Testing Results; Recommend EICP to EMWG for approval (9) Review/Update EICP Quarterly EMWG Approved 19 August 2010 Page 31 of 37

33 SECTION VII. EICP FIRST EDITION (PHASE I) PRIORITIES EMWG Approved 19 August 2010 Page 32 of 37

34 SECTION VII. EICP FIRST EDITION (PHASE I) PRIORITIES VII.A. OVERALL PRIORITIES (Ranked by EICP Subworking Group): #1 Ensure all ICC units identified in the EICP have functional UPS backup power sources and backup generator power telephone/computer operations are unaffected by power outages. #2 Ensure all ICC units identified in the EICP have additional phone lines with rollover capability to ensure a single line identified in the respective phone communications plans to prevent busy signals. #3 Work with appropriate LOGCAP officer and ITT Fire Department Sub-contractor (under Fluor Contractor) to obtain classified phone and computer systems access in the Fire Alarm/Dispatch 911 Center. VII.B. BAF DEFENSE ELEMENT PHONE: 1. NIPR: Assess & execute (as needed) additional lines & roll-over capability (all sites) 2. CENTRIXS: Request PMO and JDOC access VII.C. EMERGENCY RESPONSE/RECOVERY ELEMENT 1. NIPR: Establish BAF EM Response Recovery Distribution List (with all unit org accts loaded) 2. NIPR: Request Fire, PMO, JDOC Org accounts (or distribution lists) 3. SIPR: Request Fire, PMO, JDOC Org accounts (or distribution lists) 4. SIPR: Establish BAF EM Response Recovery Distribution List (with all unit org accts loaded) 5. CENTRIXS: Request Fire, Craig Hospital MCC, PMO, JDOC Org accounts (or distribution lists) 6. CENTRIXS: Establish BAF EM Response Recovery Distribution List (with all unit org accts loaded) PHONE: 7. NIPR: Assess & execute (as needed) additional lines & roll-over capability (all sites) VII.D. INCIDENT SUPPORT ELEMENT 1. SIPR: Initiate justification/process for Fire SIPR access in Alarm Center 2. CENTRIXS: Initiate justification/process for Fire CENTRIXS access in Alarm Center PHONE: 3. NIPR: Establish redundancy for Fire 911 (Identify alternate ring location) 4. NIPR: Investigate and execute (if possible) 911 simultaneous ring at Craig Hospital & PMO 5. NIPR: Assess & execute (as needed) additional lines & roll-over capability (all sites) WEB: 6. Bagram Incident Command (BIC) COP: Explore/execute access for Fire Alarm Center/911 Dispatch RADIO: 7. Investigate/execute options for back-up radio capability in Emergency Operations Center EMWG Approved 19 August 2010 Page 33 of 37

35 SECTION VIII. EICP SECOND EDITION (PHASE II) PROPOSED PRIORITIES EMWG Approved 19 August 2010 Page 34 of 37

36 SECTION VIII. EICP SECOND EDITION (PHASE II) PRIORITIES VIII.A. OVERALL PRIORITIES (Ranked by EICP Subworking Group): #1 Assess the requirements for, and procure a radio trunking system. This system will use a repeater but it will have more frequencies loaded into it. By establishing a trunking system, the ICC s Incident Support Element would be able to use a unique channels for multiple incidents. In addition, appropriate radio capability segregation (according to appropriate ICC elements) and enhanced radio options would be realized. VIII.B. BAF DEFENSE ELEMENT /PHONE/WEB/RADIO: Ensure all Sector-based C2 nodes identified in the BAF Defense Plan establish/maintain comprehensive interoperability communications plans reflective of the diverse capabilities (and limitations) unique to their respective geographical area. Utilize the EICP Subworking Group to assess/validate such plans and capture them as appendices for EICP Phase II. VIII.C. EMERGENCY RESPONSE/RECOVERY ELEMENT No recommendations at this time. VIII.D. INCIDENT SUPPORT ELEMENT /PHONE/WEB/RADIO: Ensure all Unit Control Centers (UCCs) and other Emergency Support Function (ESF) nodes are identified. Establish/maintain comprehensive interoperability communications plans reflective of the diverse capabilities (and limitations) unique to these varying military, civilian, and contract agencies. Utilize the EICP Subworking Group to assess/validate such plans and capture them as appendices for EICP Phase II. EMWG Approved 19 August 2010 Page 35 of 37

37 SECTION IX. REFERENCES EMWG Approved 19 August 2010 Page 36 of 37

38 SECTION IX. REFERENCES Homeland Security Presidential Directive (HSPD)-5 (28 Feb 2003) National Incident Management System (NIMS); Chapter V.B.1. Communications Management (1 Mar 2004) Air Force Instruction (AFI) [Chapter 1]: 1.3. Military Support to Civil Authorities (MSCA); 1.4. Crisis Management; and 2.2. Stafford Act AFI : Air Force Emergency Management (EM) Program Planning and Operations (Section ) Air Force Incident Management System (AFIMS) implementation guidance from SECAF (10 Jan 2007; pg 23) AFI (Chapter 1, Paragraph 1.3; Chapter 2, Paragraph 2.2; Chapter 3, Paragraph 3.5 and 3.5.1) TF Wolverine-CO, Memorandum for Record, Emergency Management Working Group (EMWG) Charter, dated 01 Jun 2010 TF Wolverine-CO, Memorandum for Record, Joint Emergency Operations Center Standard Operating Procedures, dated 22 Jul 2010 EMWG Approved 19 August 2010 Page 37 of 37