Which Nims Management Characteristic Follows

The Incident Command System (ICS) is based on the post-obit 14 proven NIMS management characteristics, each of which contributes to the strength and efficiency of the overall system:

Mutual Terminology	Integrated Communications
Modular Organization	Establishment and Transfer of Control
Management by Objectives	Unified Command
Incident Activeness Planning	Concatenation of Command & Unity of Command
Manageable Span of Control	Accountability
Incident Facilities and Locations	Dispatch/Deployment
Comprehensive Resources Management	Information and Intelligence Management

Common Terminology

The Incident Control Organization (ICS) establishes Common Terminology that allows diverse incident direction and support organizations to work together across a wide variety of emergency functions and hazard scenarios. This common terminology covers the following:

Organizational Functions: Major functions and functional units with incident direction responsibilities are named and They remain standard and consequent.
Resource Descriptions: Major resources – including personnel, equipment, teams, and facilities – are given mutual names and are "typed" with respect to their capabilities.
Incident Facilities: Common terminology is used to designate the facilities in the vicinity of the incident surface area.

During an incident:

Communications should apply common terms.
Organizations should avoid radio codes, agency-specific codes, acronyms, or jargon. Usage of these types of codes may cause confusion or perchance compromise life safety due to a misunderstanding or

The goal is to promote agreement amidst all parties involved in managing an incident.

Modular System

The Incident Command System (ICS) organizational construction develops in a modular manner based on the incident's size and complication.

The responsibility for the establishment and expansion of the ICS modular organization rests with the Incident Commander.
As the incident grows more than complex, the ICS arrangement may expand as functional responsibilities are delegated.

ICS Organizational Structure

The Operations Section develops and expands from the lesser-upwards in a modular fashion. As resources arrive and are added to the Operations system, span-of control, geography, and/or functional responsibilities are considered in shaping how the Operations organization expands to coincide with increasing complication.

The remaining ICS organizational structure typically develops in a top-downwardly, modular fashion that is based on the size and complexity of the incident, besides as the specifics of the hazard environment created by the incident. Every bit incident complexity increases, the arrangement expands from the top-down as functional responsibilities are delegated.

The ICS organizational construction is flexible. When needed, separate functional elements tin be established and subdivided to heighten internal organizational management and external coordination. Equally the ICS organizational construction expands, the number of direction (or "Overhead") positions besides expands to fairly address the requirements of the incident.

Direction by Objectives

The Incident Commander or Unified Command (which will be discussed later), establishes incident objectives that bulldoze incident response activities.

Management past Objectives includes the following:

Establishing specific, measurable incident objectives.
Identifying strategies, tactics, tasks, and activities to achieve the objectives.
Developing and issuing assignments, plans, procedures, and protocols to accomplish identified tasks.
Documenting results for the incident objectives.

Incident objectives are used to ensure that everyone inside the ICS organization has a clear understanding of what needs to be accomplished.

Guiding the decisions that a team makes in choosing how best to reach their piece of work is typically a fix of Priorities. They are besides provided by Command and must exist numbered in society of importance to have any truthful value for making decisions. A prepare might look like the following:

Life Condom
Incident Stabilization
Property/Environmental Preservation

Incident Action Planning

Incident activity planning guides effective incident management activities. An Incident Action Plan (IAP) is a concise, coherent ways of capturing and communicating overall incident priorities, objectives, strategies, tactics, and assignments in the context of both operational and support activities. The IAP should focus on addressing the needs of future timeframes (called operational periods).

To be effective, an IAP should:

Cover a specified timeframe
Be proactive and address contingencies
Specify the incident objectives
Country the activities to be completed
Assign responsibilities
Identify resources
Specify communication protocols

Even the smallest of incidents are managed by incident objectives and plans. The programme can be as simple equally the next steps the Incident Commander plans to practice. For smaller/less complex incidents, the IAP may be oral or written, except for hazardous materials incidents, which require a written IAP.

Manageable Span of Control

Depending on your role inside the Incident Control Organisation (ICS) structure, y'all may be asked to manage the activities of others.

The span of control refers to the number of individuals or resources that one supervisor can manage effectively during an incident. This concept is particularly important for shaping the Operations Department organizational structure.

The optimal span of command is one supervisor to five subordinates (ane:5).

However, effective incident management particularly outside of the Operations Section may require ratios significantly different from this. This ratio is a guideline–incident personnel should use their best judgment to determine the appropriate ratio for an incident.

If too much responsibleness is given to the supervisor, the span of control may become unmanageable. A manageable span of control on incidents may actually vary depending upon the type of incident, nature of the chore, hazards and prophylactic factors, and distances between personnel and resource.

Maintaining a manageable span of command is particularly of import at incidents where prophylactic and accountability are a height priority.

Incident Facilities and Locations

Depending upon the incident size and complexity, various types of support facilities may be established past Incident Command. These designated facilities typically include:

Incident Control Post(ICP)
Incident bases and camps
Joint Information Centers (JIC)
Staging Areas
Helicopter (Helo) Spots and Helibases (Air and UAV)

Comprehensive Resource Management

At any incident or event, the situation must be assessed and response planned. Resources must be organized, assigned, and directed to accomplish the incident objectives. Every bit they work, resources must be managed to adjust to changing atmospheric condition. Managing resource safely and effectively is the almost of import consideration in an incident. The formalized resource management procedure in ICS ensures that the management principles translate into do at the incident.

Comprehensive Resource Direction describes standard mechanisms to place requirements, order and acquire, mobilize, track and report condition, demobilize, and reimburse and restock resources such as personnel, teams, and equipment.

Primal resource management activities include:

Resource Identification and Typing
Qualification, Certification and Credentialing Personnel
Planning for Resources
Acquiring, Storing and Inventorying Resources

Integrated Communications

Incident communications are facilitated through the development and utilise of a common communications plan and interoperable advice processes and systems that include vox and data links.

Integrated Communications are necessary to:

Maintain connectivity
Accomplish situational awareness
Facilitate information sharing

Establishment and Transfer of Control

The command function should be clearly established at the start of an incident. The jurisdiction or organization with chief 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 control is transferred, the process should include a briefing that captures all essential information for continuing prophylactic and effective operations.

Unified Control

In a Unified Command, there is no single "Commander." Instead, the Unified Command manages the incident through jointly canonical objectives. Unified Control allows entities with unlike legal, geographic, and functional responsibilities to work together finer without adversely affecting private bureau authority, responsibility, or accountability.

Unified Command is typically established when no single jurisdiction, agency, or organisation has the authority and/or resources to manage the incident on its own.

Unified Command tin include incidents involving multiple jurisdictions, a unmarried jurisdiction with multiagency involvement, or multiple jurisdictions with multiagency interest.

Chain of Command

Chain of control is an orderly line that details how potency flows through the hierarchy of the incident direction system. Chain of control:

Allows an Incident Commander to straight and control the actions of all personnel on the incident.
Avoids confusion by requiring that orders flow from

The chain of command does Non prevent personnel from directly communicating with each other to ask for or share information. While formal management and command follow the chain of command, informal information sharing occurs throughout the ICS structure.

Unity of Command

While the concatenation of command relates to the overall bureaucracy 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:

Written report to merely ane Incident Command System (ICS)
Receive piece of work assignments only from your ICS

When yous are assigned to an incident, yous no longer study directly to your day-to-day supervisor. In fact, there is no correlation betwixt the ICS organization and the administrative construction of whatever single bureau or jurisdiction. This is deliberate considering confusion over unlike position titles and organizational structures has been a significant stumbling block to effective incident management in the past.

While the chain of command and unity of control is 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.

Accountability

Effective accountability during incident operations is essential. As part of the Incident Control System (ICS) structure, you will demand to abide past agency policies and guidelines and whatever applicable rules and regulations.

There are several principles you volition need to attach to:

Check-In/Bank check-Out. All responders must study in to receive an consignment. Checking out is just as critical as checking
Incident Action Response operations must be coordinated equally outlined in the Incident Activeness Plan.
Unity of Each private will be assigned to simply one supervisor.
Personal ICS relies on each private taking personal accountability for his or her own actions.
Span of Supervisors must be able to adequately supervise and control their subordinates, every bit well every bit communicate with and manage all resource nether their supervision.
Resources Supervisors must tape and report resource status changes every bit they occur. Accountability starts every bit soon every bit a resource is requested through the time that the resource returns to their home base safely.

In improver to the incident, personal accountability is critical to response success. Each member is responsible for maintaining situational awareness of their surroundings, equally well as reporting safety concerns to the concatenation of command.

Dispatch/Deployment

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

Another cardinal feature of ICS is the importance of managing resource to adjust to changing weather condition.

When an incident occurs, you must exist dispatched or deployed to become part of the incident response. In other words, until you are deployed to the incident organization, you remain in your everyday role.

After existence deployed, your first job is to check-in and receive an assignment. After bank check-in, yous will locate your incident supervisor and obtain your initial briefing. The briefings yous receive and give should include:

Current cess of the
Identification of your specific task
Identification of
Location of the work area.
Identification of interruption areas, as appropriate.
Procedural instructions for obtaining needed resource.
Operational periods/work
Required safety procedures and personal protective equipment (PPE), equally

Information and Intelligence Direction

Information and intelligence are important in the Incident Command Organisation (ICS). Incident management must establish a procedure for gathering, analyzing, assessing, sharing, and managing incident-related data and intelligence. In NIMS, "intelligence" refers exclusively to threat-related information developed by law enforcement, medical surveillance, and other investigative organizations.

To download a pdf version of this information, click here.