|
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
a.
Most Incidents Are Managed Locally. The initial response to most domestic incidents is typically handled
by local “911” dispatch centers, emergency responders within
a single jurisdiction, and direct supporters of emergency
responders. Most responses need go no further. In other instances, incidents that begin
with a single response discipline within a single jurisdiction
may rapidly expand to multidiscipline, multijurisdictional
incidents requiring significant additional resources and
operational support. Whether for incidents in which additional
resources are required or are provided from different organizations
within a single jurisdiction or outside the jurisdiction,
or for complex incidents with national-level implications
(such as an emerging infectious disease or a bioterror attack),
the ICS provides a flexible core mechanism for coordinated
and collaborative incident management. When a single incident
covers a large geographical area, multiple local ICS organizations
may be required. Effective cross-jurisdictional coordination
using processes and systems described in the NIMS is absolutely
critical in this instance. |
II-A-1-a (Page 7) |
|
|
NIMS-Derived Compliance
Statement(s) |
|
|
1. |
The
jurisdiction has implemented and institutionalized processes,
systems, procedures, and/or plans to ensure effective cross-jurisdictional
coordination between multiple local ICS organizations responding
to an incident covering a large geographical area. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
b. The NIMS Requires That
Field Command and Management Functions Be Performed in
Accordance with a Standard Set of ICS Organizations, Doctrine,
and Procedures. However,
Incident Commanders generally retain the flexibility to modify
procedures or organizational structure to align as necessary
with the operating characteristics of their specific jurisdictions
or to accomplish the mission in the context of a particular
hazard scenario. |
II-A-1-b (Page 8) |
|
|
NIMS-Derived Compliance Statement(s) |
|
|
|
The
jurisdiction has implemented and institutionalized processes
and/or plans to ensure: |
|
|
1. |
field
command and management functions are performed in accordance
with a standard set of ICS organizations,
doctrine, and procedures. |
Yes No |
|
2. |
Incident
Commanders have the authority and flexibility to modify
procedures and organizational structure as necessary
to align with the operating characteristics of their specific
jurisdiction or to accomplish the mission in the context of
a particular hazard scenario. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
c. ICS Is Modular and Scalable. ICS
is designed to have the following operating characteristics;
it should be
·
suitable for operations
within a single jurisdiction or single agency, a single jurisdiction
with multiagency involvement, or multiple jurisdictions with
multiagency 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; and
·
have a scalable organizational structure that is based on the size
and complexity of the incident. |
II-A-1-c (Page 8) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
|
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its ICS is modular
and scalable through the following operating characteristics: |
|
|
1. |
suitable
for operations within a single jurisdiction or agency. |
Yes No |
|
2. |
suitable
for operations within a single jurisdiction with multiagency
involvement. |
Yes No |
|
3. |
suitable
for operations within multiple jurisdictions with multiagency
involvement. |
Yes No |
|
4. |
readily
adaptable to new technology. |
Yes No |
|
5. |
adaptable
to any emergency or incident to which domestic incident management agencies
would be expected to respond. |
Yes No |
|
6. |
scalable
in organizational structure based on the size and
complexity of the incident. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
d. ICS Has Interactive Management
Components. These
set the stage for effective and efficient incident management
and emergency response. |
II-A-1-d (Page 8) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
1. |
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its ICS has interactive
management components. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
f. ICS Incorporates Measurable
Objectives. Measurable
objectives ensure fulfillment of incident management goals. Objective-setting begins at the top and
is communicated throughout the entire organization. |
II-A-1-f (Page 9) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
|
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its: |
|
|
1. |
ICS incorporates
measurable objectives to ensure fulfillment of incident
management goals. |
Yes No |
|
2. |
incident
management objective-setting begins at the top and is communicated
throughout the entire organization. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
g. The Implementation of
ICS Should Have the Least Possible Disruption On Existing
Systems and Processes. This will facilitate its
acceptance across a nationwide user community and to insure
continuity in the transition process from normal operations. |
II-A-1-g (Page 9) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
1. |
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its ICS has
the least possible disruption on existing systems and processes. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
1.
Concepts and Principles |
||
NIMS |
h. ICS Should Be User Friendly
and Be Applicable Across a Wide Spectrum of Emergency Response
and Incident Management Disciplines. This will enable the communication,
coordination, and integration critical to an effective and
efficient NIMS. |
II-A-1-h (Page 9) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
1. |
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its ICS is user
friendly and applicable across a wide spectrum of emergency
response and incident management disciplines. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
2.
Management Characteristics |
||
NIMS |
a. Common Terminology. ICS establishes common terminology that allows diverse incident management and support entities to work together across a wide variety of incident management functions and hazard scenarios. This common terminology covers the following: (1) Organizational
Functions. Major functions and functional units with
domestic incident management responsibilities are named and
defined. Terminology for the organizational elements involved
is standard and consistent. (2) Resource Descriptions. Major
resources—including personnel, facilities, and major equipment
and supply items—used to support incident management activities
are given common names and are “typed” with respect to their
capabilities, to help avoid confusion and to enhance interoperability. The process for accomplishing this task is specified
in Chapter IV. (3) Incident Facilities. Common
terminology is used to designate the facilities in the vicinity
of the incident area that will be used in the course of incident
management activities. |
II-A-2-a (Page 9) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
1. |
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its ICS uses common
terminology for organizational functions, resource descriptions,
and incident facilities. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
2.
Management Characteristics |
||
NIMS |
b. Modular Organization. The incident command organizational structure
develops in a top-down, modular fashion that is based on
the size and complexity of the incident, as well as the specifics
of the hazard environment created by the incident. When needed,
separate functional elements can be established, each of
which may be further subdivided to enhance internal organizational
management and external coordination. Responsibility for
the establishment and expansion of the ICS modular organization
ultimately rests with the Incident Commander (IC), who bases
these on the requirements of the situation. As incident complexity
increases, the organization expands from the top down as
functional responsibilities are delegated. Concurrently with
structural expansion, the number of management positions
expands to adequately address the requirements of the incident. |
II-A-2-b (Page 10) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
|
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its ICS: |
|
|
1. |
places responsibility for the establishment and expansion of the ICS
modular organization on the IC. |
Yes No |
|
2. |
expands
from the top down as incident complexity increases and functional responsibilities are
delegated. |
Yes No |
|
3. |
expands
the number of management positions concurrently with structural
expansion to adequately address the
requirements of the incident. |
Yes No |
|
|
Chapter
II – Command and Management |
|
|
A.
Incident Command System |
||
|
2.
Management Characteristics |
||
NIMS |
c. Management by Objectives. Management by objectives represents an
approach that is communicated throughout the entire ICS organization. This approach includes the following:
·
establishing overarching objectives;
·
developing and issuing assignments, plans, procedures, and protocols;
·
establishing specific, measurable objectives for various incident management
functional activities, and directing efforts to attain them,
in support of defined strategic objectives; and
·
documenting results to measure performance and facilitate corrective
action. |
II-A-2-c (Page 10) |
|
|
NIMS-Derived
Compliance Statement(s) |
|
|
|
The
jurisdiction has implemented and institutionalized processes,
procedures, and/or plans to ensure that its approach to management
by objectives includes: |
|