Skip to Content
ID
23-508-1289
Name
Emergency Operations Center Management Support Team
Status
Published
Version
1.1
Updated
11/10/2022 1:45:54 PM
Original Release
08/30/2022
Last Major Release
 
Description
The Emergency Operations Center (EOC) Management Support Team (MST) supports the Authority Having Jurisdiction (AHJ) and the Incident Commander (IC) with key functions relating to EOC management, including subject-matter expertise and technical support
Resource Category
Emergency Operations Center (EOC)
Primary Core Capability
Operational Communications
Secondary Core Capability
 
Resource Kind
Team
Overall Function
The EOC MST supports the AHJ to: 1. Set functional objectives to meet IC and Multiagency Coordination (MAC) Group priorities 2. Integrate stakeholders into EOC operations 3. Work with senior officials to facilitate the development of policy direction for incident support 4. Ensure timely, accurate, and accessible information dissemination to internal and external stakeholders 5. Establish an operational tempo in support of the IC 6. Facilitate routine and ongoing coordination with both public and private sector entities 7. Provide a range of current and future planning services 8. Coordinate resource management 9. Coordinate incident related projects, cascading needs, or other consequences that may fall outside of Area Command, Incident Command, Unified Command, or Department Operation Center authorities, responsibilities, objectives, or capabilities 10. Transition operations into short-term or long-term recovery through the effective transition of EOC responsibilities, functions, and projects to Incident Command, Unified Command, or the AHJ
Composition and Ordering Specifications
1. Discuss logistics for deploying this team, such as working conditions, length of deployment, security, lodging, transportation, and meals, prior to deployment 2. The requestor should specify if the personnel should have training and experience with specific software applications, hardware, and equipment 3. Requestor and provider should discuss the complexities of the incident to identify the necessary team member and their qualifications 4. Requestor should specify if the team should deploy with the identified equipment below 5. Requestor should specify what authorities the team will be delegated upon arrival
Supporting Core Capabilities
None
Components
Component Notes  
Minimum Personnel Per TeamThe AHJ may refer to the EOC Skillset Codes when specifying a required level of experience as part of a request: • Code C: Task performed in training or classroom setting, including seminars and workshops • Code E: Task performed during a full-scale exercise with equipment • Code F: Task performed during a functional exercise • Code I: Task performed during a real-world incident or event • Code J: Task performed as part of day-to-day job duties • Code T: Task performed during a tabletop exercise
Component Types
Type Attribute
Type 1All Type 1 personnel are required to meet, at a minimum, Codes I and J in all applicable EOC Skillset task reviews as applicable to the affiliated EOC position(s) and structure being requested to be filled Minimum Personnel Per Team for organization structure: Incident Support Model (ISM): 5 OR Incident Command System (ICS) 5 OR Departmental/Emergency Support Function (ESF) Structure 5
Type 2All Type 2 personnel are required to meet, at a minimum, Codes E, F, I, and J in all applicable EOC Skillset task reviews as applicable to the affiliated EOC position(s) and structure being requested to be filled Minimum Personnel Per Team for organization structure: ISM: 5 OR ICS 5 OR Departmental/ESF Structure 5
Type 3All Type 3 personnel are required to meet, at a minimum, Codes F, I, and T in all applicable EOC Skillset task reviews as applicable to the affiliated EOC position(s) and structure being requested to be filled Minimum Personnel Per Team for organization structure: ISM: 5 OR ICS 5 OR Departmental/ESF Structure 5
Management And Oversight Personnel Per Team1. The EOC MST can be deployed without the EOC Director position if augmenting an existing EOC Leadership structure 2. EOC Director refers to the individual who leads the EOC MST when it is activated. This position may use another title, including EOC Manager and EOC Coordinator, depending on the plans and procedures of the AHJ
Component Types
Type Attribute
Type 1Same As Type 2
Type 2Same As Type 3
Type 3Management and Oversight Personnel Per Team for organization structure: ISM 1 – EOC Director OR ICS 1 – EOC Director OR Departmental /ESF Model 1 – Emergency Manager
SUPPORT PERSONNEL PER TEAM1. Departments may be added or removed from the EOC MST Departmental/ESF Structure based on incident-specific requirements 2. The AHJ may request and/or authorize personnel with different levels of experience or types to create a blended EOC MST based on incident-specific requirements or staffing needs
Component Types
Type Attribute
Type 1Same As Type 2
Type 2Same As Type 3
Type 3Support Personnel Per Team for organization structure: ISM 1. 1 – Situational Awareness Section Coordinator 2. 1 – Planning Support Section Coordinator 3. 1 – Resource Support Section Coordinator 4. 1 – Center Support Section Coordinator 5. 1 – Public Information Officer OR ICS 1. 1 – Operations Section Coordinator 2. 1 – Planning Section Coordinator 3. 1 – Logistics Section Coordinator 4. 1 – Finance/Administration Section Coordinator 5. 1 – Public Information Officer OR Departmental/ESF Structure 1. Department of Natural Resources 2. Department of Health and Human Services 3. Department of Public Works 4. Department of Public Safety 5. Department of Administration
DeploymentNot Specified
Component Types
Type Attribute
Type 1Personnel are expected to support 14-day assignments with 24-hours staffing from a deployed cache
Type 2Personnel are expected to support 7-day assignments with up to 24-hours staffing in an established EOC facility or a deployed cache
Type 3Personnel are expected to support 3-day assignments with 12-hour staffing in a dedicated EOC facility
Equipment1. The Type 2 EOC MST is required to provide enough equipment to support each team member unless the equipment is provided by the requestor 2. Type 1 EOC MST is required to provide enough equipment to support each team member and other partners at the EOC unless the equipment is provided by the requestor 3. The EOC MST may be required to obtain any additional equipment based on incident-specific conditions
Component Types
Type Attribute
Type 1Same As Type 2
Type 2Same as Type 3, PLUS: 1. 1 – Printer 2. Office supplies
Type 35 – Laptop computers
Personal Protective Equipment (PPE) Per Team MemberAdditional PPE may be required based on the facility the EOC MST deployed to and other incident-specific conditions
Component Types
Type Attribute
Type 1Same As Type 2
Type 2Same As Type 3
Type 3Not Applicable
Communications Equipment Per Team1. The Type 2 EOC MST is required to provide enough communications equipment to support each team member unless the equipment is provided by the requestor 2. Type 1 EOC MST is required to provide enough communications equipment to support each team member and other partners at the EOC unless the equipment is provided by the requestor 3. The EOC MST may be required to obtain any additional communications equipment based on incident-specific conditions
Component Types
Type Attribute
Type 1Same as Type 2, PLUS: 1. 1 – Satellite phone 2. 1 – Mobile internet cradle capable of supporting multiple connections or alternate capability of each team member to access the internet, such as individual cell phone hot spots
Type 2Same as Type 3, PLUS: 1 – MiFi capable of supporting five connections
Type 35 – Cell phones
940940
Notes
References
Reference
FEMA, National Incident Management System (NIMS), October 2017
FEMA, NIMS Guideline for the National Qualification System, November 2017
FEMA, National Response Framework, June 2019
FEMA, National Preparedness Goal, September 2015
NIMS How-To Quick Reference Guide, August 2021
NIMS Emergency Operations Center Skillsets User Guide, September 2018
Published Versions
Version Publish Date Document Type
1.1 11/10/2022 1:45:54 PM PDF
1.0 8/30/2022 10:16:27 AM PDF