Overview of the Incident Command System (ICS) Part 2

The command function should be clearly established at the beginning of an incident. The jurisdiction or organization with primary responsibility for the incident designates the Incident Commander and the process for transferring command.
Transfer of command may occur during the course of an incident. When command is transferred, the process should include a briefing that captures all essential information for continuing safe and effective operations.

In a Unified Command there is no single "Commander." Instead the Unified Command manages the incident through jointly approved objectives. Unified Command allows agencies with different legal, geographic, and functional responsibilities to work together effectively without affecting individual agency authority, responsibility, or accountability.
Unified Command is typically established when no single jurisdiction, agency or organization has the authority and/or resources to manage the incident on its own. This can include incidents involving multiple jurisdictions, a single jurisdiction with multiagency involvement, or multiple jurisdictions with multiagency involvement.

Chain of command is an orderly line that details how authority flows through the hierarchy of the incident management organization. Chain of command:
Allows an Incident Commander to direct and control the actions of all personnel on the incident.
Avoids confusion by requiring that orders flow from supervisors.
Chain of command does NOT prevent personnel from directly communicating with each other to ask for or share information. While formal direction and control follows the chain of command, informal information sharing occurs throughout the ICS structure.

While chain of command relates to the overall hierarchy of the organization, unity of command deals with the fact that all individuals have a single designated supervisor they report to.
Based on the principle of unity of command, you will:
Report to only one Incident Command System (ICS) supervisor.
Receive work assignments only from your ICS supervisor.
When you are assigned to an incident, you no longer report directly to your day-to-day supervisor. In fact, there is no correlation between the ICS organization and the administrative structure of any single agency or jurisdiction. This is deliberate, because confusion over different position titles and organizational structures has been a significant stumbling block to effective incident management in the past.
While chain of command and unity of command are applied in all incidents, the actual command structure itself and the responsibilities of those involved change based on the type of incident and your specific role.

False

True

False

Effective accountability during incident operations is essential. As part of the Incident Command System (ICS) structure, you will need to abide by agency policies and guidelines and any applicable local, tribal, state, or Federal rules and regulations.
There are several principles you will need to adhere to:
Check-In/Check-Out. All responders must report in to receive an assignment. Checking out is just as critical as checking in.
Incident Action Planning. Response operations must be coordinated as outlined in the Incident Action Plan.
Unity of Command. Each individual will be assigned to only one supervisor.
Personal Responsibility. ICS relies on each individual taking personal accountability for their own actions.
Span of Control. Supervisors must be able to adequately supervise and control their subordinates, as well as communicate with and manage all resources under their supervision.
Resource Tracking. Supervisors must record and report resource status changes as they occur. Accountability starts as soon as a resource is requested through the time that the resource returns to their home base safely.

Resources should be deployed only when requested or when dispatched by an appropriate authority through established resource management systems.
Resources not requested should refrain from self-dispatching to avoid overburdening the incident command

Information and intelligence are important in the Incident Command System (ICS).
Incident management must establish a process for gathering, analyzing, assessing, sharing, and managing incident-related information and intelligence. In NIMS, "intelligence" refers exclusively to threat-related information developed by law enforcement, medical surveillance, and other investigative organizations.
Information and intelligence may be gathered from a variety of sources, including:
911 calls
Radio, video and data communications among responders
Situation Reports (SITREPS)
Technical specialists from organizations such as the National Weather Service
Reports from field observers
Geospatial products, such as GIS, etc.
Print, online, broadcast, and social media
Risk assessments
Terroristic or violent threats
Surveillance of disease outbreaks
Structural plans and vulnerabilities

Incident Action Plan

You have completed the National Incident Management System (NIMS) Management Characteristics lesson.
This lesson introduced:
Common Terminology
Modular Organization
Management by Objectives
Incident Action Planning
Manageable Span of Control
Incident Facilities and Locations
Comprehensive Resource Management
Integrated Communications
Establishment and Transfer of Command
Unified Command
Chain of Command and Unity of Command
Accountability
Dispatch/Deployment
Information and Intelligence Management
The next lesson will provide an overview of the ICS Functional Areas and introduce the roles of the Incident Commander and Command Staff.

This lesson introduces you to the Incident Command System (ICS) Functional Areas and roles of the Incident Commander and Command Staff. By the end of this lesson, you should be able to:
Identify the five major ICS functional areas.
Describe the role of the Incident Commander.
Describe the selection of and transfer of command between Incident Commanders.
Identify the position titles associated with the Command Staff.
Describe the roles of the Command Staff.
Differentiate between incident command and incident coordination.

Every incident requires that certain functional areas be implemented. The problem must be identified and assessed, a plan to deal with it must be developed and implemented, and the necessary resources must be procured and paid for.
Regardless of the size of the incident, these functional areas are all required.
In case you ever need to assist with an incident, you should understand how the management structure is constructed using the Incident Command System (ICS). This will help you understand your role in the structure and how you may receive information and assignments.
This lesson focuses on the five major functional areas and the Command Staff roles. The General Staff roles will be discussed in the next lesson.

Command, Operations, Planning, Logistics, Finance/Administration

There are five major Incident Command System (ICS) functional areas that are the foundation on which an incident management organization develops.
These functions apply to incidents of all sizes and types, including both planned events and ones that occur without warning.
If you are in an incident and hear these terms, it's important for you to know what they mean. For instance, you may be directed to provide documents to the Planning Section or receipts to the Finance/Administration Section.

Incident Command: Sets the incident objectives, strategies, and priorities, and has overall responsibility for the incident.

Operations: Conducts operations to reach the incident objectives. Establishes tactics and directs all operational resources.

Planning:
Supports the incident action planning process by tracking resources, collecting/analyzing information, and maintaining documentation.

Logistics: Arranges for resources and needed services to support achievement of the incident objectives (resources can include personnel, equipment, teams, supplies, and facilities).

Finance/Administration: Monitors costs related to the incident. Provides accounting, procurement, time recording, and cost analyses.

Intelligence/Investigations (I/I) is a sixth ICS function identified in NIMS. The Intelligence / Investigations function can be established to collect, analyze, and disseminate incident-related information and intelligence for incidents involving intensive intelligence gathering and investigative activity (such as a criminal or terrorist act, or epidemiological, accident or mass fatality investigation).
When I/I is required, the Incident Command/Unified Command can place the I/I function in multiple locations within the incident command structure based on factors such as the nature of the incident, the level of I/I activity, and the relationship of I/I to other incident activities.

The standard Incident Command System (ICS) organizational structure is shown here. Incident Command, which could be a single Incident Commander or a Unified Command, will lead the effort and, as needed, assign Command Staff and General Staff. For the remainder of this lesson, we will discuss the Incident Command function and the members of the Command Staff.

The National Incident Management System (NIMS) defines command as the act of directing, ordering, or controlling by virtue of explicit statutory, regulatory, or delegated authority.
When you are using the Incident Command System (ICS) to manage an incident, an Incident Commander is assigned. The Incident Commander has the authority to establish objectives, make assignments, and order resources. To achieve these ends, the Incident Commander works closely with staff and technical experts to analyze the situation and consider alternative strategies.
The Incident Commander should have the training, experience, and expertise to serve in this capacity. Qualifications to serve as an Incident Commander should not be based solely on rank, grade, or technical knowledge.

Let's begin by taking a closer look at the Incident Commander. The Incident Commander is responsible for the overall management of the incident. Overall management includes Command Staff assignments required to support the incident command function. The Incident Commander is the only position that is always staffed in ICS applications. On small incidents and events, one person—the Incident Commander—may accomplish all management functions.

In addition to having the overall responsibility for managing the entire incident, the Incident Commander is specifically responsible for:
Ensuring overall incident safety
Providing information services to internal and external stakeholders, such as disaster survivors, agency executives, and senior officials
Establishing and maintaining liaisons with other agencies participating in the incident
The Incident Commander may appoint one or more Deputies. If a Deputy is assigned, he or she should be fully qualified to assume the Incident Commander's position.

The command function should be clearly established at the beginning of an incident. The jurisdiction or organization with primary responsibility for an incident designates the individual at the scene who is responsible for establishing command and the protocol for transferring command. As an incident becomes more or less complex, command may change to meet the needs of the incident.
When command is transferred, the process should include a briefing that captures all essential information for continuing safe and effective operations.

Provide a transfer-of-command briefing to the new Commander

The Incident Commander is responsible for all Incident Command System (ICS) functional areas until the Incident Commander delegates a function. Since the ICS organization is modular, it has the ability to expand or contract to meet the needs of the incident. During a larger incident, the Incident Commander may create sections and delegate the Operations, Planning, Logistics, and Finance/Administration responsibilities. For very small, routine, or short-duration incidents, it is possible that the Incident Commander will not establish any of the Staff positions. In this case, the Incident Commander will personally manage all ICS functions.

Depending upon the size and type of incident or event, the Incident Commander may designate personnel to provide information, safety, and liaison services. In the Incident Command System (ICS), the Command Staff may include:

Public Information Officer, who interfaces with the public and media and/or with other agencies with incident-related information requirements.

Safety Officer, who monitors incident operations and advises the Incident Commander on all matters relating to safety, including the health and safety of incident management personnel.

Liaison Officer, who serves as the Incident Commander's point of contact for representatives of governmental agencies, non-governmental organizations (NGOs), and private-sector organizations.
Incident Commanders may also choose to appoint technical specialists (such as legal, medical, science and technology, or access and functional needs) to act as command advisors.
The Command Staff reports directly to the Incident Commander. In a complex incident, Assistant Officers may be assigned to each of the Command Staff functions.