Page 1 of 29 NIMS Basic - Command and Management FEMA 501-2 March 27, 2006 Revision 0 I. Purpose: This document describes the systems used to facilitate domestic incident command and management operations, including the ICS, multi-agency coordination systems, and the JIS. II. Scope: Details on incident command and management are contained in NIC Document FEMA 501-8, NIMS Basic - ICS Requirements. A. ICS ICS is a management system designed to enable effective and efficient domestic incident management by coordinating the combination of facilities, equipment, personnel, procedures, and communications operating within a common organizational structure, designed to enable effective and efficient domestic incident management. It is: • Widely applicable. • Used to organize both near term and long term field-level operations for a broad spectrum of emergencies, from small to complex incidents, both natural and manmade. • Used by all levels of government, Federal, State, local, and tribal, as well as many private sector and non-governmental organizations. • Applicable across disciplines. • Normally structured to facilitate activities in five major functional areas. o Command o Operations o Planning o Logistics o Finance/administration B. Challenges Acts of biological, chemical, radiological, and nuclear terrorism represent particular challenges for the traditional ICS structure. • Events that are non-site specific, are geographically dispersed, or evolve over longer time periods, will require extraordinary coordination between Federal, State, local, tribal, private sector, and non-governmental organizations. • An area command may be established to oversee the management of such incidents. Page 2 of 29 C. Extract This document is extracted from FEMA 501, National Incident Management System. Refer to the NIMS in the event of conflicting information. Document text underlined and in teal font is extracted from the NRP and provides information on the interface between the documents. III. Table of Contents: I. Purpose:.................................1 II. Scope:..................................1 A. ICS......................................1 B. Challenges...............................1 C. Extract..................................2 III. Table of Contents: ....................2 IV. Definitions: ...........................3 V. Process:.................................4 A. Concepts and Principles .................4 1. Safety ..................................4 2. Incident Response........................4 3. Modularity and Scalability...............5 4. Interactive Management...................5 5. Measurable Objectives....................5 6. Implementation...........................5 7. Applicability ...........................5 B. Management Characteristics ..............5 1. Common Terminology.......................6 2. Modular Organization.....................6 3. Management by Objectives ................6 4. IAP......................................6 5. Span of Control .........................7 6. Pre-designated Incident Locations and Facilities ..........7 7. Comprehensive Resource Management .......7 8. Integrated Communications................7 9. Establishment and Transfer of Command ...7 10. Unified Command.........................8 11. Accountability .........................8 12. Deployment .............................8 13. Information and Intelligence ...........8 C. Organization and Operations .............9 1. Overview ................................9 2. Command Function .......................10 3. Single Command..........................10 4. UC .....................................10 5. Command Staff ..........................12 6. General Staff ..........................13 7. Operations..............................13 Page 3 of 29 8. Planning ...............................15 9. IAP.....................................16 10. Logistics .............................16 11. Information and Intelligence...........17 12. Area Command ..........................18 D. Multi-agency Coordination Systems.......19 1. Primary Functions ......................19 2. EOC.....................................19 3. Multi-agency Coordination Entities .....21 E. Public Information Systems..............21 1. Principles..............................22 2. Description and Components .............22 VI. Responsibilities: .....................23 VII. References: ..........................28 VIII. Supersedure:.........................28 IX. Attachment 1...........................29 A. IAP Outline.............................29 IV. Definitions: chain of command: The orderly line of authority within the ranks of the incident management organization. command staff: The command staff in an incident management organization consists of the incident commander and the special staff positions of PIO, SO, LNO, their assistants, and other positions as required that report directly to the IC. DOC: Department Operations Center general staff: A group of incident management personnel: • Organized according to function. • Reporting to the incident commander. • Normally consisting of the operations, planning, logistics, and finance/administration section chiefs. IAP: Incident Action Plan ICP: Incident Command Post ICS: Incident Command System JIC: The Joint Information Center is a physical location where public affairs professionals from organizations involved in incident management activities can collocate to perform critical emergency information, crisis communications, and public-affairs functions. Page 4 of 29 JIS: Joint Information System LNO: Liaison Officer NRP: National Response Plan PIO: Public Information Officer resources: The personnel, teams, equipment, supplies, and facilities available, or potentially available, for assignment or allocation in support of incident management and emergency response activities. single resources: Individual personnel and equipment items and the operators associated with them. SO: Safety Officer span of control: The ratio of a supervisor to subordinates. strike teams: A set number of resources of the same kind and type that have an established minimum number of personnel. task forces: Any combination of resources assembled in support of a specific mission or operational need, and having common communications and a designated leader. UC: Unified Command unity of command: Every individual reports to a designated supervisor at the scene of the incident. V. Process: A. Concepts and Principles The NIMS requires that field command and management functions be performed in accordance with a standard set of ICS organizations, doctrine, and procedures. The IC, however, generally has some flexibility to modify procedures or organizational structure. 1. Safety The IC/UC and supervisors at all levels of incident management have the ultimate responsibility for the safe conduct of incident management operations. 2. Incident Response ICS provides a flexible core mechanism for coordinated and collaborative incident management for: • Incidents in which additional resources are required or are provided from different organizations within a single jurisdiction, or outside the jurisdiction. • Complex incidents with national-level implications, such as an emerging infectious disease or a bio-terror attack. Page 5 of 29 • A single incident covering a large geographical area requiring multiple “local” ICS organizations. Note: Effective cross-jurisdictional coordination using processes and systems described in the NIMS is absolutely critical in this instance. 3. Modularity and Scalability ICS is modular, scalable, and is designed to have the following operating characteristics. • Suitable for operations within a single jurisdiction or single agency, a single jurisdiction with multi-agency involvement, or multiple jurisdictions with multi-agency involvement. • Applicable and acceptable to users throughout the country. • Readily adaptable to new technology. • Adaptable to any emergency or incident to which domestic incident management agencies would be expected to respond. • Scalable organizational structure based on the size and complexity of the incident. 4. Interactive Management ICS has interactive management components for effective and efficient incident management and emergency response. • Common terminology, standards, and procedures that enable diverse organizations to work together effectively. • A standard set of pre-designated organizational elements and functions. • Common names for resources used to support incident operations • Common “typing” for resources to reflect specific capability. • Common identifiers for facilities and operational locations used to support incident operations. 5. Measurable Objectives Measurable objectives ensure fulfillment of incident management goals. Objective setting begins at the top and is communicated throughout the entire organization. 6. Implementation\ICS implementation should have the least possible disruption on existing systems and processes to facilitate its acceptance across a nationwide user community, and ensure continuity in the transition process. 7. Applicability ICS should be user friendly and be applicable across a wide spectrum of emergency response and incident management disciplines to enable the communication, coordination, and integration critical to an effective and efficient NIMS. B. Management Characteristics B. Management Characteristics ICS is based on proven management characteristics that contribute to the strength and efficiency of the overall system. Page 6 of 29 1. Common Terminology Common terminology allows diverse incident management and support entities to work together across a wide variety of incident management functions and hazard scenarios. It includes the following items. a) Organizational Functions Name and define major functions, and functional units with domestic incident management responsibilities using standard and consistent terminology for the organizational elements involved. b) Resource Descriptions Use common names and capability “type” to help avoid confusion and enhance interoperability for major resources such as personnel, facilities, major equipment, and supply items used to support incident management activities. NIC Document FEMA 501-4, NIMS Basic - Resource Management, specifies the process for accomplishing this task. c) Incident Facilities Use common terminology to designate those facilities in the vicinity of the incident area that will be used in the course of incident management activities. 2. Modular Organization Develop the incident command organizational structure in a top-down, modular fashion based on the: • Size and complexity of the incident. • Specifics of the hazard environment created by the incident. When needed, establish separate functional elements, each of which may be further subdivided to enhance internal organizational management and external coordination. a) Size The IC has ultimate responsibility for establishing and expanding the ICS modular organization based on the requirements of the situation. 3. Management by Objectives Communicate this approach throughout the entire ICS organization and include the following. • Establish overarching objectives. • Develop and issue assignments, plans, procedures, and protocols. • Establish specific, measurable objectives for various incident management functional activities, and direct efforts to attain them in support of defined strategic objectives. • Document results to measure performance and facilitate corrective action. 4. IAP The IAP provides a coherent means to communicate the overall incident objectives in the context of both operational and support activities. See additional details under Organization and Operations. Page 7 of 29 5. Span of Control A manageable span of control is key to effective and efficient incident management. • The span of control of any individual with incident management supervisory responsibility should range from three to seven subordinates. • The type of incident, nature of the task, hazards and safety factors, and distances between personnel and resources influence span of control considerations. 6. Pre-designated Incident Locations and Facilities FEMA 501-4 provides more details on pre-designated facilities, which typically include: • Incident command posts. • Bases. • Camps. • Staging areas. • Mass casualty triage areas. • Others as required. 7. Comprehensive Resource Management Maintain an accurate and up-to-date picture of resource utilization, a critical component of domestic incident management. Resource management includes processes for: • Categorizing, ordering, dispatching, tracking, and recovering resources. • Reimbursement for resources, as appropriate. 8. Integrated Communications Address the equipment, systems, and protocols necessary to achieve integrated voice and data incident management communications in preparedness planning. Develop and use a common communications plan and interoperable communications processes and architectures to facilitate incident communications. This integrated approach: • Links the operational and support units of the various agencies involved. • Is necessary to maintain communications connectivity and discipline. • Enables common situational awareness and interaction. 9. Establishment and Transfer of Command The agency with primary jurisdictional authority over the incident designates the individual at the scene responsible for establishing command. • Clearly establish the command function at the beginning of incident operations. Page 8 of 29 • When command is transferred, the process must include a briefing that captures all essential information for continuing safe and effective operations. a) Command Principles Chain of command and unity of command clarify reporting relationships and eliminate the confusion caused by multiple, conflicting directives. Incident managers at all levels must be able to control the actions of all personnel under their supervision. 10. Unified Command Unified command allows agencies with different legal, geographic, and functional authorities and responsibilities to work together effectively without affecting individual agency authority, responsibility, or accountability in incidents involving: • Multiple jurisdictions. • A single jurisdiction with multi-agency involvement. • Multiple jurisdictions with multi-agency involvement. 11. Accountability Effective accountability at all jurisdictional levels and within individual functional areas during incident operations is essential, and requires compliance with the following principles. a) Check-In All responders, regardless of agency affiliation, must report in to receive an assignment in accordance with the procedures established by the IC. b) IAP Direct and coordinate response operations as outlined in the IAP. c) Unity of Command Assign each individual involved in incident operations to only one supervisor. d) Span of Control Supervisors must be able to adequately: • Supervise and control their subordinates. • Communicate with and manage all resources under their supervision. e) Resource Tracking Supervisors must record and report resource status changes as they occur. 12. Deployment Personnel and equipment should respond only when requested or when dispatched by an appropriate authority. 13. Information and Intelligence The incident management organization must establish a process for gathering, sharing, and managing incident-related information and intelligence. Page 9 of 29 C. Organization and Operations The IC, command staff, and general staff comprise the ICS organization with five major functions as shown in Figure 1. A potential sixth area covers the intelligence function as described in Information and Intelligence above. FEMA 501-8 provides additional information on ICS requirements. Figure 1: ICS Command and General Staff Under the Command block are: Operations Planning Logistics Finance/Administration Intelligence 1. Overview Command staff and general staff must: • Continually interact. • Share vital information and estimates of the current and future situation. • Develop recommended courses of action for consideration by the IC. a) Command The IC and command staff comprises the command function. b) Command Staff Command staff is responsible for overall management of the incident, which includes command staff assignments required to support the command function. Establish command staff positions to assign responsibility for key activities not specifically identified in the general staff functional elements. These positions may include the: • PIO • SO • LNO •Others as required and assigned by the IC. c) General Staff Incident management personnel who represent the major functional elements of the ICS comprise the general staff. These include section chiefs for: • Operations. • Planning. • Logistics. • Finance/Administration. Page 10 of 29 • Other as appropriate. FEMA 501-4 provides additional information on the specific functions and makeup of the individual units within each of these sections. d) Assigned Representatives Agency and organizational representatives assigned to an incident must have the authority to speak for their parent agencies or organizations on all matters following appropriate consultations with their agency leadership. See the LNO section for point of contact information. 2. Command Function This may be a single command or UC. The primary differences are: • In a single command structure, the IC establishes and ensures accomplishment of incident management objectives and strategies. • In a UC structure, the individuals designated by their jurisdictional authorities, or by departments within a single jurisdiction must jointly: o Determine objectives, strategies, plans, and priorities. o Work together to execute integrated incident operations and maximize the use of assigned resources. 3. Single Command The appropriate jurisdictional authority designates a single IC with overall incident management responsibility when an incident occurs within a single jurisdiction and there is no jurisdictional or functional agency overlap. A single IC may be designated in cases where incident management crosses jurisdictional and/or functional agency boundaries if all parties agree to such an option. Jurisdictions should consider pre-designating ICs in their preparedness plans. 4. UC The UC is an important element in multi-jurisdictional or multi-agency domestic incident management. As a team effort, it overcomes much of the inefficiency and duplication of effort that can occur when agencies from different functional and geographic jurisdictions, or agencies at different levels of government, operate without a common system or organizational framework. All agencies with jurisdictional authority or functional responsibility for any or all aspects of an incident and those able to provide specific resource support participate in and contribute to the UC structure. a) Structure The exact UC composition will depend upon the: • Locations of the incident and which geographical administrative jurisdictions are involved. • Type of incident and which functional agencies of the involved Page 11 of 29 jurisdictions are required. Note: A single IC may be designated to promote greater unity of effort and efficiency in some multi-jurisdictional incidents. b) Designated Agency Officials The designated agency officials participating in the UC: • Represent different legal authorities and areas of responsibility. •Use a collaborative process to establish incident objectives. • Designate priorities that accommodate those objectives. c) Jurisdictional Responsibility Agencies that lack jurisdictional responsibility, but are heavily involved in the incident: • Are defined as supporting agencies. • Are represented in the command structure. • Effect coordination on behalf of their parent agency through the LNO. Jurisdictional responsibilities of multiple incident management officials are consolidated into a single planning process as discussed more fully in FEMA 501-8, and include: • Responsibilities for incident management. • Incident objectives. • Resource availability and capabilities. • Limitations. • Areas of agreement and disagreement between agency officials. d) Collaborative Management Incidents are managed under a single collaborative approach that includes the following. • Common organizational structure. • Single ICP. • Unified planning process. • Unified resource management. e) IAP The planning section chief develops the IAP, which is approved by the UC. The operations section chief: • Directs the tactical implementation of the IAP. • Normally comes from the agency with the greatest jurisdictional involvement. • Is an agreed upon designation by the UC participants. f) Practices UC works best when the participating members of the UC collocate at the ICP and follow the requirements described in the Responsibilities section. Page 12 of 29 5. Command Staff See additional information in the Responsibilities section. a) Positions Command staff positions are: • Specifically designated. • Report directly to the IC. • Assigned responsibility for key activities that are not part of the general staff functional elements. • Typically comprised of PIO, SO, and LNO activities. Designate additional positions: • Depending upon the nature, scope, complexity, and locations of the incidents. • According to specific requirements established by the IC. b) Additional Positions Additional command staff positions may also be necessary depending upon the: • Nature and location of the incident. • Specific requirements established by the IC. Example: A legal counsel may be assigned directly to the command staff to advise the IC on legal matters such as emergency proclamations, legality of evacuation orders, and legal rights and restrictions pertaining to media access. Similarly, a medical advisor may be designated and assigned directly to the command staff to provide advice and recommendations to the IC in the context of incidents involving: • Medical and mental health services. • Mass casualty. • Acute care. • Vector control. • Epidemiology. • Mass prophylaxis considerations, particularly in the response to a bio-terrorism event. c) PIO Designate only one incident PIO, whether the command structure is single or unified. Assistants may be assigned from other agencies or departments involved. Page 13 of 29 d) SO The SO provides the IC with systems and procedures necessary to assess, coordinate, and implement safety measures for incident operations. Designate a single SO in a UC structure in spite of the fact that there may be multiple jurisdictions and/or functional agencies involved. Assistants may be required and may be assigned from other agencies or departments comprising the UC. Note: The agencies, organizations, or jurisdictions that contribute to joint safety management efforts do not lose their individual identities or responsibility for their own programs, policies, and personnel. Rather, each entity contributes to the overall effort to protect all responder personnel involved in incident operations. e) LNO The LNO is the point of contact for representatives of other governmental agencies, non-governmental organizations, and/or private entities. In either a single or UC structure, representatives from assisting or cooperating agencies and organizations coordinate through the LNO. Assistants and personnel from other public or private agencies or organizations involved in incident management activities may be assigned to the LNO to facilitate coordination. f) Members Command staff members: • May need one or more assistants to manage their workloads in the context of large or complex incidents. • Should organize their assistants for maximum efficiency. 6. General Staff The general staff: • Represents and is responsible for the functional aspects of the incident command structure. • Typically consists of the operations, planning, logistics, and finance and administration functions, which are described below. 7. Operations Figure 2 depicts the primary organizational structure for the section. Expand the basic structure according to operational factors and the specific circumstances of the incident at hand. Consider structures based on: • Jurisdictional boundaries. • A strictly functional approach. • A mix of functional and geographical considerations. Page 14 of 29 Figure 2: Operations Section Organizational Elements Operations Section Branch Division or Group Resource a) Operations Section Chief The operations section chief: • Is responsible to the IC/UC for all incident-related operational activities. • Establishes tactical objectives for each operational period with other section chiefs and unit leaders. •May have one or more deputies assigned, with the assignment of deputies from other agencies encouraged in the case of multi-jurisdictional incidents. • Should be designated for each operational period. • Should have direct involvement in the preparation of the IAP for the corresponding period of responsibility. b) Branches Branches serve several purposes, and may be functional or geographic in nature. In general, establish branches when the number of divisions or groups exceeds the recommended span of control of 1:3 to 1:7 for the operations section chief. Note: A ratio of 1 supervisor for 5 subordinates is normally recommended, but may vary from 1:8 to 1:10 in larger-scale law enforcement operations. Page 15 of 29 c) Divisions and Groups Establish divisions and groups when the number of resources exceeds the manageable span of control of the IC/operations section chief. There also may be additional levels of supervision below the division or group level. • Divisions are established to divide an incident into physical or geographical areas of operation. • Groups are established to divide the incident into functional areas of operation. Example: The IC may establish intelligence functions as a functional group in the operations section for certain types of incidents. d) Resources Resources may be organized and managed in three different ways, depending upon the requirements of the incident. • Single Resources. • Task Forces. • Strike Teams. Use strike teams and task forces wherever possible to: • Optimize the use of resources. • Reduce the span of control over a large number of single resources. • Reduce the complexity of incident management coordination and communications. 8. Planning The section in Figure 3 is comprised of four primary units, as well as a number of technical specialists. Figure 3 - Planning Section Organization Planning Section: Resources Unit Situation Unit Demobilization Unit Documentation Unit Technical Specialists Page 16 of 29 9. IAP The IAP includes the overall incident objectives and strategies established by the IC or UC, and is especially important when: • Resources from multiple agencies/jurisdictions are involved. • Multiple jurisdictions are involved. • The incident will effectively span several operational periods. • Changes in shifts of personnel and/or equipment are required. • There is a need to document actions and/or decisions. In the case of UC, the IAP must adequately address the: •Mission and policy needs of each jurisdictional agency, as well as interaction between jurisdictions, functional agencies, and private organizations. • Tactical objectives and support activities required for one operational period, generally 12 to 24 hours. • Continuous incorporation of “lessons learned” as incident management activities progress. The IAP will typically contain a number of components as shown in Attachment 1, Table 1. 10. Logistics The section as shown in Figure 4 supports requirements needed to facilitate effective and efficient incident management. Figure 4: Logistics Section Organization Logistics Section: Supply Unit Food Unit Ground Support Unit Communications Unit Facilities Unit Medical Unit Page 17 of 29 a) Finance and Administration Establish a finance and administration section when the agencies involved in incident management activities require finance and other administrative support services. The basic organizational structure is shown in Figure 5. The depicted units may be created as required. Note: Not all incidents will require a separate finance/administration section. In cases requiring only one specific function (e.g., cost analysis), a technical specialist in the planning section may provide this service. Figure 5: Finance and Administration Section Organization Finance/Administration Section: Compensation/Claims Unit Procurement Unit Cost Unit Time Unit 11. Information and Intelligence The analysis and sharing of information and intelligence are important elements of ICS, and must be appropriately analyzed and shared with personnel designated by the IC, who have proper clearance and a “need to-know” to ensure that they support decision-making. In this context, intelligence includes not only national security or other types of classified information but also other operational information that may come from a variety of different sources, such as: • Risk assessments. • Medical intelligence (i.e. surveillance). • Weather information. • Geospatial data. • Structural designs. • Toxic contaminant levels. • Utilities and public works data. • Etc. Other activities directed by the IC can include information security and operational security. Page 18 of 29 a) Organization Traditionally, information and intelligence functions are located in the planning section. In exceptional situations the IC may need to assign the information and intelligence functions to other parts of the ICS organization. The intelligence and information function may be most appropriately organized in one of the following ways: • Within the command staff for incidents with little need for tactical or classified intelligence, and where incident-related intelligence is provided by supporting agency representatives, through real-time reach-back capabilities. • A branch within the planning section for incidents with some need for tactical intelligence, and where a law enforcement entity is not a member of the UC. • As a branch within the operations section for incidents with a high need for tactical intelligence (particularly classified intelligence), and where law enforcement is a member of the UC. • As a separate general staff section when an incident is heavily influenced by intelligence factors, or where there is a need to manage and/or analyze a large volume of classified or highly sensitive intelligence or information. This option is particularly relevant to a terrorism incident, where intelligence plays a crucial role throughout the incident life-cycle. 12. Area Command An area command is: • Activated only if necessary, depending upon the complexity of the incident and incident management span-of-control considerations. • Usually established by an agency administrator or other public official with jurisdictional responsibility for the incident. • Used when there are a number of incidents in the same area and of the same type, such as two or more hazardous material (HAZMAT) or oil spills, and fires. These incidents may compete for the same resources. • Established either to oversee the management of multiple incidents that are each being handled by a separate ICS organization or to oversee the management of a very large incident that involves multiple ICS organizations, such as would likely be the case for incidents that are non-site specific, geographically dispersed, or evolve over longer periods of time, (e.g. a bio-terror event). In this sense, acts of biological, chemical, radiological, and/or nuclear terrorism represent particular challenges for the traditional ICS structure, and will require extraordinary coordination between Federal, State, tribal, local, private sector, and non-governmental organizations. Page 19 of 29 a) Resource Demands When incidents do not have similar resource demands, they are usually handled separately and are coordinated through an EOC. Area Command should not be confused with the functions performed by an EOC. • Area command oversees management of the incident. • An EOC coordinates support functions and provides resources support. b) Unified Area Command A unified area command should be established to allow each jurisdiction to have representation in the command structure if the incidents under the authority of the area command are multi-jurisdictional. D. Multi-agency Coordination Systems This is a combination of facilities, equipment, personnel, procedures, and communications integrated into a common system with responsibility for coordinating and supporting domestic incident management activities. Multi-agency coordination systems may contain an EOC and, in certain multi-jurisdictional or complex incident management situations, multi-agency coordinating entities. Note: Direct tactical and operational responsibility for the conduct of incident management activities rests with the IC. 1. Primary Functions Refer to the Responsibilities section for additional details. 2. EOC The EOC: • May be a permanent organization, facility, or may be established to meet temporary, short-term needs. • Physical size, staffing, and equipping will depend on the size of the jurisdiction, resources available, and anticipated incident management workload. • May be organized and staffed in a variety of ways. • Should include the following core functions regardless of the specific organizational structure used. o Coordination. o Communications. O Resource dispatch and tracking. o Information collection, analysis, and dissemination. • May also support multi-agency coordination and joint information activities as discussed below. • Represents the physical location where the coordination of information and resources to support incident management activities normally takes place. Note: The ICP located at or in the immediate vicinity of an incident site Page 20 of 29 is primarily focused on the tactical on-scene response, but may perform an EOC like function in smaller-scale incidents, or during the initial phase of the response to larger, more complex events. Note: The ICP should be linked to the DOC and EOC to ensure effective and efficient incident management. a) Facilities A standing EOC, or those activated to support larger, more complex events is typically established in a more central or permanently established facility, at a higher level of organization within a jurisdiction. The DOC facility: • Normally focuses on internal agency incident management and response and is linked to, and in most cases physically represented in a higher level EOC. • Is organized by major functional discipline (fire, law enforcement, medical services, and so on), or by jurisdiction (city, county, region, and so on), or, more likely, some combination thereof. b) Staffing Personnel representing multiple jurisdictions and functional disciplines and a wide variety of resources may staff the EOC for complex incidents. Example: A local EOC established in response to a bio-terrorism incident would likely include a mix of personnel including: • Law enforcement. • Emergency management. • Public health. • Medical personnel, including representatives of: O Health care facilities. O Pre-hospital emergency medical services (EMS/EMT). O Patient transportation systems. o Pharmaceutical repositories. o Laboratories. o Etc. c) Communications and Coordination Upon activation of a local EOC, establish communications and coordination between the: • IC/UC and the EOC when they are not collocated. • ICS field organizations and the activated local EOC, either directly or through their parent organizations. Each EOC, at all levels of government and across functional agencies, must be capable of communicating appropriately with other EOCs during incidents, to include those maintained by private organizations. Communications between EOCs must be reliable and contain built-in Page 21 of 29 redundancies. Efficient EOC functioning most frequently depends on the existence of mutual aid agreements and joint communications protocols among participating agencies. Such agreements are discussed in NIC Document FEMA 501-3, NIMS Basic - Preparedness. 3. Multi-agency Coordination Entities A multi-agency coordination entity, such as an emergency management agency, may be used to facilitate incident management and policy coordination when an incident: • Crosses disciplinary or jurisdictional boundaries. • Involves complex incident management scenarios. a) Operation and Structure The situation at hand and the needs of the jurisdictions involved will dictate how multi-agency coordination entities conduct their business and they are structured. Multi-agency coordination entities typically consist of principals or their designees from organizations and agencies with direct incident management responsibility, or with significant incident management support or resource responsibilities. These entities are sometimes referred to as: • Crisis action teams. • Policy committees. • Incident management groups. • Executive teams. • Other similar terms. Example: The wildland fire community has such an entity called the Multi-Agency Coordination Group (MAC Group). b) Coordination In some instances, the EOC may serve a dual function as a multi-agency coordination entity; in others, preparedness organizations discussed in FEMA 501-3 may fulfill this role. Regardless of the term or organizational structure used, these entities typically provide strategic coordination during domestic incidents. If constituted separately, multi-agency coordination entities, preparedness organizations, and EOCs must coordinate and communicate with one another to provide uniform and consistent guidance to incident management personnel. E. Public Information Systems Systems and protocols for communicating timely and accurate information to the public are critical during crisis or emergency situations. This section describes the principles, system components, and procedures needed to support effective emergency public information operations. Page 22 of 29 1. Principles a) PIO The PIO supports the IC. Specific activities are detailed in the Responsibilities section. b) Public information The JIC coordinates public awareness functions with the information and operational security matters that are the responsibility of the information and intelligence function of the ICS, particularly where public awareness activities may affect information or operations security. c) Participating Organizations Organizations participating in incident management retain their independence. ICs and multi-agency coordination entities establish and oversee the JIC, to include processes for coordinating and clearing public communications. In the case of UC, the departments, agencies, organizations, or jurisdictions that contribute to joint public information management do not lose their individual identities, or responsibility for their own programs or policies. Rather, each entity contributes to the overall unified message. 2. Description and Components a) JIS The JIS integrates public information activities among JICs. Specific actions are detailed in the Responsibilities section. Key elements include: • Interagency coordination and integration. • Developing and delivering coordinated messages. • Support for decision-makers. • Flexibility, modularity, and adaptability. b) JIC JIC actions are detailed in the Responsibilities section. More than one JIC may be needed for a complex incident spanning a wide geographic area or multiple jurisdictions. • A single location is preferable, but the system should be flexible and adaptable enough to accommodate multiple JIC locations when the circumstances of an incident require. • A JIC may be established at various levels of government in large or complex incidents, particularly those involving complex medical and public health information requirements. An example of typical JIC organization is shown in the Figure 6. Page 23 of 30 Figure 6: JIC Organization Joint Information Center: Press Secretary Liaison Research Team Media Operations Logistic Team VI. Responsibilities: Area Command For incidents under its authority: • Sets overall incident-related priorities. • Allocates critical resources based on priorities. • Ensures that incidents are properly managed. • Ensure that incident management objectives are met and do not conflict with each other or with agency policy. • Identifies critical resource needs and reports them to the EOC and multi-agency coordination entities. • Ensures that short-term emergency recovery is coordinated to assist in the transition to full recovery operations. IC • Establishes incident management objectives and strategies. o Develops incident objectives upon which subsequent incident action planning will be based. o Ensures all functional area activities are directed toward accomplishment of the strategy. • Modifies procedures or organizational structure to: o Align as necessary with the operating characteristics of their specific jurisdictions. o Accomplish the mission in the context of a particular hazard scenario. • Approves the IAP. • Directs the identification and location of facilities based upon the requirements of the situation at hand. • Approves all requests pertaining to the ordering and releasing of Page 24 of 29 incident resources. • Expands the organization from the top down as incident complexity increases and functional responsibilities are delegated. • Expands the number of management positions concurrently with structural expansion to adequately address the requirements of the incident. Information and Intelligence Function • Develops, conducts, and manages information-related security plans and operations as directed by the IC. • Coordinates information and operational security matters with public awareness activities that fall under the responsibility of the PIO, particularly where such public awareness activities may affect information or operations security. • Handles and safeguards sensitive information of all types. • Provides sensitive information to those who need access to it in order to effectively and safely conduct their missions. JIC • Provides the organizational structure for coordinating and disseminating official information. • Coordinates and integrates public information functions: o Across jurisdictions and across functional agencies. o Among Federal, State, local, and tribal partners. o With the private sector and non-governmental organizations. • Provides a location for organizations participating in the management of an incident to work together to ensure dissemination of timely, accurate, easy-to-understand, and consistent information to the public. • Includes representatives of each jurisdiction, agency, private sector, and non-governmental organization involved in incident management activities. • Has the most current and accurate information regarding incident management activities at all times. • Is established at each level of incident management as required. • Follows procedures and protocols to communicate and coordinate effectively with other JICs, as well as with other appropriate components of the ICS organization on an ongoing basis. Page 25 of 29 JIS • Provides the plans, protocols, and structures used to establish an organized, integrated, and coordinated mechanism to deliver understandable, timely, accurate, and consistent information to the public in a crisis. • Encompasses all public information operations related to an incident, including: o All Federal, State, local, tribal and private organization PIOs. o Staff. o Each JIC established to support an incident. • Provides the mechanism for integrating public information activities: o Among JIC locations. o Across jurisdictions. o With the private sector and non-governmental organizations. Logistics Section • Orders resources from off-incident locations. • Provides facilities, transportation, supplies, equipment maintenance and fuel, food services, communications and information technology support. • Provides emergency responder medical services, including inoculations as required. Multi-agency Coordination Entities • Ensure each agency involved in incident management activities is providing appropriate situational awareness and resource status information. • Establish priorities between incidents and/or area commands in concert with the IC/UC involved. • Acquire and allocate resources required by incident management personnel in concert with the priorities established by the IC/UC. • Anticipate and identify future resource requirements. • Coordinate and resolve policy issues arising from the incident. • Provide strategic coordination as required. • Following incidents, ensure that improvements in plans, procedures, communications, staffing, and other capabilities necessary for improved incident management are acted upon. • Coordinate the above improvements with appropriate preparedness organizations, if they are constituted separately. Page 26 of 29 Multi-agency Coordination Systems • Support incident management policies and priorities. • Facilitate logistics support and resource tracking. • Make informed resource allocation decisions based on incident management priorities. • Coordinate incident related information. • Coordinate interagency and intergovernmental issues regarding incident management policies, priorities, and strategies. Operations Section •Reduces the immediate hazard. • Saves lives and property. • Establishes situational control. • Restores normal operations. Operations Section Chief • Directly manages all incident-related operational activities. • Establishes tactical objectives for each operational period. • Prepares the IAP for the corresponding period of responsibility. PIO • Supports the IC. o Is a key staff member supporting the incident command structure. o Represents and advises the IC on all public information matters relating to the management of the incident. o Gets IC approval before releasing any incident-related information. • Handles media and public inquiries, emergency public information and warnings; rumor monitoring and response, media monitoring, and other functions required to coordinate, clear with appropriate authorities, and disseminate accurate and timely information related to the incident, particularly regarding information on public health and safety and protection. o Interfaces with the public and media and/or with other agencies with incident-related information requirements. o Develops accurate and complete information on the incident’s cause, size, and current situation; resources committed; and other matters of general interest for both internal and external consumption. o May also perform a key public information-monitoring role. • Coordinates public information at or near the incident site and serves as the on-scene link to the JIS. • On-scene in a large-scale operation, serves as a field PIO with links to the JIC typically collocated with the Federal, regional, State, local, or tribal EOC tasked with primary incident coordination responsibilities. Page 27 of 29 Planning Section • Collects, evaluates, and disseminates incident situation information and intelligence to the IC/UC and incident management personnel, unless the IC places this function elsewhere. •Prepares status reports. •Displays situation information. •Maintains status of resources assigned to the incident. •Develops and documents the IAP based upon guidance from the IC or UC. •Develops planning options. •Forecasts requirements for additional resources. All Responders Report in (check-in) to receive an assignment in accordance with the procedures established by the IC. SO • Provides the set of systems and procedures to the IC that ensures: o On-going assessment of hazardous environments. o Coordination of multi-agency safety efforts. o Implementation of measures to promote emergency responder safety, as well as the general safety of incident operations. • Monitors incident operations. • Advises the IC on all matters relating to operational safety, including the health and safety of emergency responder personnel. • Has emergency authority to stop and/or prevent unsafe acts during incident operations. • Coordinates closely with the operations section chief, and planning section chief regarding operational safety and emergency responder health and safety issues. • Ensures the coordination of safety management functions and issues across jurisdictions, across functional agencies, and with private sector and non-governmental organizations. Supervisors • Supervise and control their subordinates. • Communicate with and manage all resources under their supervision. • Record and report resource status changes as they occur. Page 28 of 29 UC • Provides guidelines to enable agencies with different legal, geographic, and functional responsibilities to coordinate, plan, and interact effectively. o Determines overall incident strategies. o Selects objectives. o Ensures that joint planning for tactical activities is accomplished in accordance with approved incident objectives. o Ensures the integration of tactical operations. o Approves, commits, and makes optimum use of all assigned resources. • Selects an operations section chief for each operational period. • Keeps each other informed of specific requirements. • Establishes consolidated incident objectives, priorities, and strategies. • Coordinates to establish a single system for ordering resources. • Develops a consolidated IAP, written or oral, that is evaluated and updated at regular intervals. •Establishes procedures for joint decision-making and documentation. VII. References: FEMA 501, National Incident Management System FEMA 501-3, NIMS Basic - Preparedness FEMA 501-4, NIMS Basic - Resource Management FEMA 501-8, NIMS Basic - ICS Requirements FEMA 510, National Response Plan VIII. Supersedure: Original Page 29 of 29 IX. Attachment 1 A. IAP Outline Table 1: Sample IAP Outline Table headings are: Components; Normally Prepared By: Common Components Incident Objectives: Incident Commander Organization List/Chart: Resources Unit Assignment List: Resources Unit Communications Plan: Communications Unit Logistics Plan: Logistics Unit Responder Medical Plan: Medical Unit Incident Map: Situation Unit Health and Safety Plan: Safety Officer Other Potential Components (Scenario dependent) Air Operations Summary: Air Operations Traffic Plan: Ground Support Unit Decontamination Plan: Technical Specialist Waste Management or Disposal Plan: Technical Specialist Demobilization Plan Demobilization Unit Operational Medical Plan: Technical Specialist Evacuation Plan: Technical Specialist Site Security Plan: Law Enforcement Specialist Investigative Plan: Law Enforcement Specialist Evidence Recovery Plan: Law Enforcement Specialist Other: As Required