This Tactical Interoperable Communications Plan (TICP) is
subject to information and/or equipment updates and changes. The use of this
Record of Change helps manage TICP modifications throughout the life of this
document. All attempts have been made to ensure the accuracy of the information
within this TICP as of the initial distribution date. Any subsequent
adjustments should be logged and coordinated with user agencies within this Rhode
Island Providence UASI. Preface
This document establishes a Tactical
Interoperable Communications Plan (TICP) for the State of Rhode Island,
inclusive of Rhode Island Homeland Security Region [Region 1].
The TICP is intended to document the
interoperable communications resources available within the designated area,
who controls each resource, and what rules of use or operational procedures
exist for the activation and deactivation of each resource.
See Appendix
I for a list of
resources available to assist in preparing/updating the TICP.
Executive Overview
This document establishes a Tactical Interoperable
Communications Plan (TICP) for the State of Rhode Island and the Providence
UASI, inclusive of Rhode Island Homeland Security Region [Region 1]. The TICP
is intended to document the interoperable communications resources available
within the designated area, who controls each resource, and what rules of use
or operational procedures exist for the activation and deactivation of each
resource.
This Tactical Interoperability Communication Plan (TICP) has
been created for the State of Rhode Island and Providence UASI. The plan is
intended for use by first responders and may be used by governmental or
non-governmental organizations and personnel requiring communications or
coordination during an incident or planned event.
The jurisdictions, agencies, and disciplines represented in
the TICP are listed in Table 1. Additional contact information for each agency
is listed in Appendix
A.
Table 1Jurisdictions, Agencies, and Disciplines Represented in the TICP
The [State of Rhode Island Providence UASI] TICP addresses
interoperable communications equipment and planning for the region. Though each
agency, discipline, and jurisdiction participating in this plan is unique
regarding their own interoperable communication needs and capabilities,
proximity to one another, population, and shared incident/event
responsibilities allow them to develop a single, consolidated regional TICP
rather than several individual, potentially incompatible plans.
The TICP therefore consolidates information across agencies,
disciplines, and jurisdictions by documenting regional communications
capabilities in order to provide a usable and accurate regional tactical
incident response tool.
The TICP was developed under the authority of the Interoperable
Communications Committee]. On [MM/DD/YY] the RIEMA Director David Smith
appointed members to the ICC, designated as an advisory committee to the ICC
Members include representatives from the following public safety and public
service disciplines:
The [Name of Council/Executive Board] is comprised of
[Voting/Non-Voting] agency representatives in addition to the following fixed
committee positions:
The ICC has the responsibility to review
this document at a meeting called annually by the TICP POC. Requests for
modifications or additions to this document should be submitted to the TICP POC
for distribution to the Communications Working Group]. Updates to this document
can be recommended by any of the participating agencies. Agencies participating
in this plan will be formally notified within 30 days] of any approved
modifications or additions to this TICP.
Agencies will retain the following rights and
responsibilities:
Agencies are responsible for considering and, if
agreeing to, complying with MOUs and Agreements developed by the ICC in
coordination with their respective jurisdictions.
Authorized representatives of agencies participating
in this plan have the authority to request the use of equipment, including
systems and mobile assets, in accordance with Standard Operating
Procedures (SOPs).
Where applicable, agencies will be responsible for
consistently maintaining, testing, and exercising connectivity to
interoperable communications.
Agencies retain the right to decide when and where to
participate in interoperable communications. For example, agencies will
retain the right to accept or decline a patch to a gateway system to
provide interoperable communications during an incident.
In response to events or incidents which cross over
political jurisdictions, there will potentially be competing demands and
priorities for interoperable communications assets.
Until such time as Incident Command is established, the lead
agency designee (i.e., communications supervisor/command personnel), in
cooperation with assisting agencies, will have the authority to designate the
use of interoperable assets. Once Incident Command has been established,
Command Staff or Communication Unit Leaders (when designated) direct the
further coordination and delegation of the interoperable communications assets
assigned to the event or incident in question.
Agencies should judiciously activate needed interoperable
assets so as to both effectively respond to the event and/or incident and also
minimize any negative impact on surrounding agencies or jurisdictions.
Specifically, interoperable communications should be attempted with the
following order of operations in mind (subject to variability based on the
agencies involved and the nature of the event/incident):
Leverage
face-to-face communications wherever appropriate. For example, the
co-location of all Command and General Staff at the incident command post
(ICP) provides the best direct communications and reduces the demand on
interoperability resources.
Employ
local communications assets until such time as either those assets become
taxed or inadequate based on the nature and/or scope of the incident.
If
response agencies are users of a shared system, utilize that shared system
to establish interoperable communications.
If
response agencies operate on disparate systems, utilize shared or mutual
aid channels to establish interoperable communications.
If
response agencies do not share systems or channels, utilize a gateway
solution to establish interoperable communications.
Where
interoperable communications cannot otherwise be established between
response agencies, utilize swap or cache radios to establish operable
communications for responders.
If
no other method of interoperability can be established, relay
communications through staff members.
When the same resources are requested for two or more
incidents, resource assignments should be based on the priority levels listed
below:
Disasters,
large scale incidents, or extreme emergencies requiring mutual aid or
interagency communications.
Incidents
where imminent danger exists to life or property.
Incidents
requiring the response of multiple agencies.
Pre-planned
events requiring mutual aid or interagency communications.
Incidents
involving a single agency where supplemental communications are needed for
agency use.
Drills,
tests and exercises.
In the event of multiple simultaneous incidents within the
same priority level, the resources should be allocated with the following
priorities in mind:
Incidents
with the greatest level of exigency (e.g., greater threat to life or
property, more immediate need, etc.) have priority over less exigent
incidents.
Agencies
with single/limited interoperable options have priority use of those
options over agencies with multiple interoperable options.
When
at all possible, agencies already using an interoperable asset during an
event should not be redirected to another resource.
Reference to applicable policy documents, governing
documents, MOUs, and sharing agreements can be found in Appendix G.
This section describes all interoperable communications
equipment and their associated policies and procedures in the State of Rhode
Island and the Providence UASI].
“Shared system” refers to a single radio system used to
provide service to several public safety or public service agencies. The table
below lists all radio systems shared by more than one public safety or service
agency operating in the State of Rhode Island and Providence UASI. Details on
each system are provided in Appendix
B.
Note: that intra-system “shared channels” refer to common
frequencies/talkgroups established and programmed into radios to provide
interoperable communications among agencies using the same shared radio system.
“Channel,” in this context, refers to the name of a common frequency/talkgroup
visually displayed on a user’s radio.
The ICC has
identified 1 (one) shared communication systems that provide service to Rhode
Island /Providence UASI]. General interoperable communications rules of use,
policies, and procedures that apply across these systems are detailed below.
Use the following procedures when requesting, using, or
discontinuing the use of shared communication systems:
When an individual responder needs to interoperate
with other agencies on their same shared system, the responder will notify
their dispatch center. The dispatcher can then identify and designate an
appropriate channel. Note that in cases where no dispatcher intervention
is required, responders still notify dispatch that they are switching to a
shared channel to maintain responder safety.
Notify dispatch when the interoperability
channels/talkgroups are no longer required and announce the return to
normal operations channels.
For extended incidents:
oThe
lead agency dispatcher notifies the [Communications Coordinator
(COMC)/Communications Unit Leader (COML)/designee] that interoperability
channels/talkgroups are in use.
oEach
agency’s dispatch center tells additional en-route responders what
interoperability channels are in use for the incident.
oThe
Incident Commander determines when the interoperability channels are no longer
required and notifies the appropriate dispatch center.
●National Incident Management System
– Use an Incident Command System (ICS) compliant with the National
Incident Management System (NIMS) when using any regional interoperability
resource.
●Plain Language – All
interoperable communications during multi-agency, multi-discipline incidents
will be in plain language. Avoid using radio codes, acronyms, and abbreviations
as they may cause confusion between agencies. Ensure that all verbal requests
for assistance or backup specify the reason for the request.
●Unit Identification – Announce
your home agency prior to announcing your unit identifier during interoperable
communication situations. (i.e., [Local Example Here])
During activation,
report shared system problems to the Communications Technician (COMT) or
COML/designee assigned to the incident/event who will follow established
agency procedures to resolve the problem.
Following an incident, the following general problem ID and
resolution processes apply to all shared systems:
Report any problems
with the shared system to the appropriate POC for the owning agency listed
in Appendix
B. The POC will be responsible for ensuring
effective resolution to problems that exist with the shared system.
Report any unresolved problems with that system
directly to the Rhode Island Providence UASI [Communications
Coordinator/COML/ Michael Walsh]. The Rhode Island Providence UASI [Communications
Coordinator/COML/Michael Walsh] ensures effective resolution to the
reported shared system problems.
(Note: Policies and procedures specific to a single shared system
are listed subsequent to that specific shared system below)
RISCON system
consists of those communication assets belonging to the State of Rhode Island
and the City of Providence. Interoperable communications are achieved through
the use of common channels and patching of channels in the system.
Interoperable communications among first responders in the same political
subdivisions shall first be achieved through common channels. Disciplines in a
common zone shall achieve interoperable communications also through common
channels
The member agencies
both governmental and non governmental will abide by the policies practices and
procedures outlined herein. Common channels will be assigned on the basis of
need and the priorities listed. The first priority will be given to disasters, natural
and man made. The second priority will be given to life threatening incidents.
The third priority will be assigned to large property loss incidents. The
fourth priority for channel assignment will be to maintain public law and order
and the fifth priority will be to maintain common infrastructure and event
management.
The first contact
point for interoperable communications shall be the local dispatch office in
which the incident occurs. The dispatch office shall first ensure that the
channel is available and then notify the regional control dispatcher that the
interoperable channel has been assigned to an incident
The overarching
goal of interoperable communications is to ensure communications for all
incidents that may occur during a given time period. With this in mind, each
zone will attempt to maintain communications for incidents that occur in their
zone. The regional control zone shall be the first decision maker to resolve
communication conflicts between jurisdictions. The State Wide Interoperable
Communications Director (SWIC) shall be the final arbitrator resolving
communication conflicts between jurisdictions
Intra-system “shared channels” refer to common
frequencies/talk groups established and programmed into radios to provide
interoperable communications among agencies using the same shared radio system.
“Channel,” in this context, refers to the name of a common frequency/talkgroup
visually displayed on a user’s radio.
The ICC has identified [number here] shared communication
systems that provide service to the [State/Region/Urban Area]. General
interoperable communications rules of use, policies, and procedures that apply
across these systems are
Specific shared interoperable communication channels
available within the region are listed in the tables below. More detailed
information on each channel is documented in Appendix
C.
Intra-system shared
channels are common frequencies/talkgroups established and programmed into
radios to provide interoperable communications among agencies using the same
shared radio system. The following rules of use apply to these channels:
National Incident Management System
– Use an Incident Command System (ICS) compliant with the National
Incident Management System (NIMS) when using any regional interoperability
resource.
Plain Language – All
interoperable communications during multi-agency, multi-discipline
incidents will be in plain language. Avoid using radio codes, acronyms,
and abbreviations as they may cause confusion between agencies. Ensure
that all verbal requests for assistance or backup specify the reason for
the request.
Unit Identification –
Announce your home agency prior to announcing your unit identifier during
interoperable communication situations. (i.e., [Local Example Here])
During
activation, report shared channels problems to the Communications
Technician (COMT) or COML/designee assigned to the incident/event, who
will follow established agency procedures to resolve the problem.
Following an
incident, the following general problem ID and resolution processes apply to
all shared channels:
Report any problems with the
intra-system shared channel to the appropriate POC for the owning agency
listed in Appendix
B. The POC will be responsible for ensuring
effective resolution to problems that exist with the intra-system shared
channel.
Report any unresolved problems with
that system directly to the [State/Region/Urban Area] [Communications
Coordinator/COML/designee]. The [State/Region/Urban Area] [Communications
Coordinator/COML/designee] ensures effective resolution to the reported
intra-system shared channel problems.
(Note: Policies and procedures specific to a
single intra-system shared channel are listed subsequent to specific intra-system
shared channels below.)
Inter-system “shared channels” refer to common
frequencies/talkgroups established and programmed into radios to provide
interoperable communications among agencies using different radio systems.
“Channel,” in this context, refers to the name of a common frequency/talkgroup
visually displayed on a user’s radio.
Specific inter-system shared interoperable communication
channels available within the region are listed in the tables below. More
detailed information on each channel is documented in Appendix C.
Inter-system shared channels are reserved for situations
that require interoperable communications to coordinate multiple public safety
entities and/or activities across two or more separate radio systems. The
following rules of use apply to these channels:
National
Incident Management System – Use an Incident Command System
(ICS) compliant with the National Incident Management System (NIMS) when
using any regional interoperability resource.
Plain Language
– All interoperable communications during multi-agency,
multi-discipline incidents will be in plain language. Avoid using radio
codes, acronyms, and abbreviations as they may cause confusion between
agencies. Ensure that all verbal requests for assistance or backup specify
the reason for the request.
Unit
Identification – Announce your home agency prior to announcing
your unit identifier during interoperable communication situations. (i.e.,
[Local Example Here])
During activation, report shared
channels problems to the Communications Technician (COMT) or COML/designee
assigned to the incident/event, who will follow established agency procedures
to resolve the problem.
Following an incident, the following general
problem ID and resolution processes apply to all shared channels:
Report
any problems with the inter-system shared channel to the appropriate POC
for the owning agency listed in Appendix
CError! Reference source not found..
The POC will be responsible for ensuring effective resolution to problems
that exist with the inter-system shared channel.
Report
any unresolved problems with that system directly to the Rhode Island/ Providence
UASI [Communications Coordinator/COML/Michael Walsh]. The Rhode Island
Providence UASI [Communications Coordinator/COML/Michael Walsh] ensures
effective resolution to the reported inter-system shared channel problems.
(Note:
Policies and procedures specific to a single shared channel are listed
subsequent to that specific shared channel below)
“Gateway” systems interconnect channels of disparate systems
(whether on different frequency bands or radio operating modes), allowing first
responders using their existing radios and channels to be interconnected with
the channels of other users outside of their agency. Dispatch consoles that are
able to create patches will also be captured as gateways. Gateways are listed in the following
table. More detailed information on each gateway is provided in Appendix D.
The
following rules of use shall govern interoperable communications between
agencies via gateways:
National Incident Management System
– Use an Incident Command System (ICS) compliant with the National
Incident Management System (NIMS) when using any regional interoperability
resource.
Plain Language – All
interoperable communications during multi-agency, multi-discipline
incidents will be in plain language. Avoid using radio codes, acronyms,
and abbreviations as they may cause confusion between agencies. Ensure
that all verbal requests for assistance or backup specify the reason for
the request.
Unit Identification –
Announce your home agency prior to announcing your unit identifier during
interoperable communication situations. (i.e., [Local Example Here])
Encryption – All encrypted
radios users must operate in a “clear” mode when a gateway is used, unless
otherwise arranged in advance. Never
assume encryption carries across the gateway.
Monitoring – The Incident
Commander, or their designee, will ensure that each activated
interoperability channel is monitored consistently while in use.
The COML and/or Incident Commander must be
aware that activating multiple gateways to support an incident can result in
mutual interference. Interference issues are best resolved by the technical
support team assigned to the gateways.
The agency requesting the use of a fixed or
mobile gateway device for incident/event communications support should document
and provide the following information to the owning gateway agency POC, on
request:
Requesting agency
On-scene agencies requiring
interoperability
Incident/event type (e.g., wild land
fire, etc.)
Equipment required
Expected duration of event
Location required/access information
Incident POC
User/requestor and/or servicing
dispatch contact phone number
Additional support services requested
(e.g., gateway operator, generator, etc.)
Report
gateway problems to the owning agency dispatcher (for fixed gateways) or
mobile gateway operator (for mobile gateways), who will follow established
agency procedures to resolve the problem.
Following
an incident, the following general problem ID and resolution processes apply to
all regional gateways:
Report
any problems with the gateway to the appropriate POC for that agency
listed in Appendix
D. The POC will be responsible for ensuring
effective resolution to problems that exist with the gateway.
Report
unresolved gateway problems directly to the [State/Region/Urban Area] [Communications
Coordinator/COML/designee]. The [State/Region/Urban Area] [Communications
Coordinator/COML/designee] ensures effective resolution to reported
gateway problems.
The
number of simultaneous patches that can be supported by the gateway will
be limited by switch capacity and the number of lines connecting control centers
and consoles. As a result, a limited number of patches involving resources
at different control points can be supported simultaneously. Likewise, a
limited number of patches involving resources that are accessed through a
communications center console may be supported simultaneously.
Home
system coverage may limit communications. Gateway users must be within the
footprint of their coverage area.
Agencies
not permanently configured on a given gateway will require additional
planning to establish interoperable communications through that gateway.
To ensure that equipment components of the
gateway operate properly, each agency will participate in the following testing
procedure:
Representatives from multiple agencies
should meet on a regular basis to test each gateway.
Testing should include deployment
(mobile only), setup, operation, and deactivation of each gateway.
If an issue or problem is identified
during the testing procedure, determine who will take corrective action. If
the issue or problem cannot be resolved, contact the appropriate technical
personnel to address the issue or problem.
(Note: Policies and procedures specific
to a single gateway are listed subsequent to that specific gateway below)
This section
provides individualized guidance on how to request, deploy, and use specific [State/Region/Urban
Area] gateways. Further detailed information on all [State/Region/Urban Area]
gateways is listed in Appendix
D.
Cache radios, also known as “swapped radios,” refer to
maintaining a cache of standby radios that can be deployed to support regional
incidents. These radios may be from a regional cache or from a participating
agency. These radios allow all responders to use common, compatible equipment
during an incident. Specific caches within the [State/Region/Urban Area] are
listed in the following table. Detailed information on cache radios can be
found in Appendix
E.
Plain
Language – All interoperable communications during multi-agency,
multi-discipline incidents will be in plain language. Avoid using radio
codes, acronyms, and abbreviations as they may cause confusion between
agencies. Ensure that all verbal requests for assistance or backup specify
the reason for the request.
●Unit Identification – Announce
your home agency prior to announcing your unit identifier during interoperable
communication situations. (i.e., [Local Example Here])
Equipment
Return – The requesting agency is responsible for the return of
any cache radios/equipment in the condition that they were received. OR Responsibilities for lost or
damaged equipment lie with the appropriate agency as dictated by existing
Memoranda of Agreement (MOAs).
The Incident
Commander, or their designee, determines when a situation exists that requires
the use of a regional radio cache and notifies the appropriate dispatch center.
The dispatch center will follow internal agency procedures to contact the COML
or Radio Cache Agency POC and relay pertinent information regarding the event.
The requesting agency documents and provides the following information to the
Radio Cache Agency POC, on request:
Requesting
agency
On-scene
agencies requiring interoperability
Incident/event
type of event (e.g., wild land fire, etc.)
Equipment
requirements
Expected
duration of event
Location
required/access information
Incident POC
User/requestor
and/or servicing dispatch contact phone number
Additional
support services requested (e.g., technician, chargers, etc.)
The Radio Cache
Agency determines what radio caches are available for use, identifies a
specific cache, activates that cache, and coordinates the cache deployment with
the requesting agency Incident Commander or their designee.
Contact the on-call technician
responsible for radio cache deployment.
Dispatch the radio cache technician (or
an approved designee) to the incident scene.
Inform the requesting agency that the
radio cache is en route and provide an estimated time of arrival (ETA), if
available.
The radio
cache technician (or designee) should follow these deployment procedures:
Provide dispatch with an ETA at the
incident.
Retrieve the radio cache from its
storage location and deliver it to the incident scene.
Report to the Incident Commander or
Check-in on arrival.
Once on-scene, sign the cache over to
the requesting agency for incident use or, if assigned to remain on scene,
coordinate radio cache deployment procedures with the Communications Unit.
oEach radio in the radio cache will have a unique
identification number for inventory tracking. Ask the receiving agency to sign
a property transfer form if they take responsibility for managing the radio
cache on scene.
oThe requesting Incident Commander, or their
designee, will be responsible for:
§Supporting
radio deployments on-scene
§Maintaining
a record of each user and agency to whom a radio and associated accessories
have been distributed
§Documenting
the identification number of each radio deployed
§Documenting
the channel(s) in use
Each user and/or agency that receives a
radio from the radio cache will be responsible for returning that radio
and all associated accessories to the cache at the end of the incident.
When the radio cache
is no longer required, agencies should follow these deactivation procedures:
Coordinate
the return of all cache radios to the Communications Unit through the
Incident Commander or their designee.
The
Communications Unit will be responsible for inventorying all radios and
accessories returned to the cache. Before leaving the incident scene, the
Communications Unit will determine if any radios have not been returned to
the radio cache and note the user and agency to which the radio was
distributed. Provide this information to the Incident Commander or their
designee.
If the
missing radios cannot be recovered at the incident scene, the
Communications Unit will provide this information to the Radio Cache
Agency POC for resolution.
Report radio
cache problems to the radio cache technician or their designee who will follow
established agency procedures to resolve the problem.
Following an
incident, the following general problem ID and resolution processes apply to
all regional radio caches:
Report any
problems with the radio cache to the appropriate POC for the owning agency
listed in Appendix E. The POC will be responsible for
ensuring effective resolution to problems that exist with the radio cache.
Report
unresolved radio cache problems directly to the [State/Region/Urban Area] [Communications
Coordinator/COML/designee]. The [State/Region/Urban Area] [Communications
Coordinator/COML/designee] ensures effective resolution to reported radio
cache problems.
(Note:
Policies and procedures specific to a single radio cache are listed subsequent to
that specific cache below)
A mobile
communications Unit (MCU) (also known as a Mobile Communications Center (MCC)
or Mobile EOC) refers to any vehicular asset that can be deployed to provide or
supplement communications capabilities in an incident area. Examples of the
types of communications devices an MCU can house are: subscriber and base
station radios of various frequency bands, gateway devices, satellite phones,
wireless computer networks, video broadcasting/receiving equipment, etc. Typically
these communications devices are permanently [located/stored] in the MCUs when
not used. The MCU should also be able to temporarily provide the electrical
power required to operate the communications devices. More detailed information
on each MCU is provided in Appendix
F.
Table 18[State/Region/Urban Area] Mobile
Communications Unit(s)
The Incident
Commander, or their designee, determines when a situation exists that requires
the use of an MCU and notifies the appropriate dispatch center. The dispatch
center will follow internal agency procedures to contact the COML or MCU POC
and relay pertinent information regarding the event. The requesting agency
documents and provides the following information to the MCU POC, on request:
Requesting
agency
Agencies
requiring interoperability
Incident/event
type (e.g., wild land fire, etc.)
Expected
duration of event
Location
required/access information
Incident POC
User/requestor
and/or servicing dispatch contact phone number
Additional
support services requested
The MCU Agency
determines if the MCU is available for use and coordinates the deployment with
the requesting agency Incident Commander or their designee.
The Emergency Resource Directory establishes a list of
personnel who will respond to fill the Communication Unit positions.
Identified personnel must train and exercise to a
regional response level.
Contact information:
Center Name – Number
Center Name – Number
Center Name – Number
Job descriptions and qualified personnel for each
Communications Unit position are detailed below.
Dispatch
Center
Communications Coordinator (COMC)– The COML will work with the COMC to coordinate communications
with other dispatch centers and the incident communication plan. Locally, the
jurisdictional dispatch center supervisor or dispatcher will act as the
Communications Coordinator. Coordinators may also be located at the
region/county, State, and Federal level.
At an
Incident/Event
Communications Unit Leader (COML) –Manages the technical and operational aspects of the
Communications Function during an incident or event. Develops National Incident
Management System (NIMS)/Incident Command System (ICS) Form 205 Incident Radio
Communications Plan and supervises the communication unit.
Technical Specialist (THSP) – Allows for the
incorporation of personnel who may not be formally certified in any specific
NIMS/ICS position. THSPs may include Local Agency Radio Technicians (as opposed
to the COMT), Telephone Specialists, Gateway Specialists, Data/IT Specialists,
and or Cache Radio Specialists.
Incident Communications Technician (COMT) –
Deploys advanced equipment and keeps it operational throughout the incident/event.
Incident Communications Center Manager (INCM) –
Supervises the operational aspects of the Incident Communications Center (ICC)
(Mobile Unit and/or Fixed Facility). During an incident, the ICC is designed to
absorb incident traffic in order to separate that traffic from the day-to-day
activities of the dispatch center. The ICC is typically located at the Incident
Command Post (ICP) in a fixed site, tent, trailer, mobile communications unit.
Radio Operator
(RADO) - Staffs a radio at the ICC and is responsible for documenting
incoming radio and telephone messages. Incident Dispatchers or Tactical
Dispatchers are used as RADOs.
The following table lists contact information of the
Regional Emergency Resource Personnel for each Communications Unit position.
The Communication Assets Survey and Mapping (CASM) tool
provides the ability for representatives of public safety agencies within an
urban area or State to collect, store, and visualize data about agencies,
communication assets, and how agencies use those assets.
The purpose of CASM is to:
Provide a single repository for information about
land mobile radio systems, other interoperability methods, and how they
are used by public safety agencies within a state or urban area.
Provide a method to display the data.
Provide tools to analyze the data and visualize
interoperability gaps in accordance with the Interoperability Continuum
framework.
The CASM tool is composed of two components: the
Communication Assets Survey (CAS) and the Communication Assets Mapping (CAM)
tool. The CAS component provides a means to enter, edit, and delete information
about agencies, communication assets (such as radio systems, dispatch centers,
mutual aid channels/systems, gateways and radio caches), and agency usage of
those assets. The CAM component provides a means to display this information in
a map-based interface and provides analysis tools for displaying
agency-to-agency interoperability, including interoperability gaps, in various
ways.
The CASM tool is web-based and requires the user to have an
active internet connection in order to access both the CAS and CAM components. CAS
is a website that may be accessed via any internet browser, such as Internet
Explorer, Netscape Navigator, or Mozilla Firefox. CAM is a client application
that must be downloaded, installed, and executed on the user’s computer. A user
must have internet access in order to operate CAM.
Authorization to view data for a particular urban area or
State is controlled by the [State/Region/Urban Area] Administrative Manager
(AM); each user must have a user name and password in order to login.
Detailed
information on shared systems available for use within the region is listed in
subsequent pages of Appendix B. The table below lists the shared system(s).
Table B - 1[State/Region/Urban Area] Shared
System(s)
Detailed
information on shared channels available for use within the region is listed in
the following table to include shared channel name(s) and frequency/talkgroup
details for each shared channel.
Table C - 1[State/Region/Urban
Area] 700 MHz Inter-system
Shared Channel(s)
Channel
Name
Analog
/ Digital
Wide / Narrow
Tx and Tone
Rx and Tone
Talkgroup ID
Primary Use
Agencies Supported
Table C - 2[State/Region/Urban Area] 800 MHz Inter-system Shared Channel(s)
Channel
Name
Analog
/ Digital
Wide / Narrow
Tx and Tone
Rx and Tone
Talkgroup ID
Primary Use
Agencies Supported
Table C - 3[State/Region/Urban Area] UHF Inter-system Shared Channel(s)
Channel
Name
Analog
/ Digital
Wide / Narrow
Tx and Tone
Rx and Tone
Talkgroup ID
Primary Use
Agencies Supported
Table C - 4[State/Region/Urban Area] VHF Inter-system Shared Channel(s)
Detailed
information on gateways available for use within the region is listed in
subsequent pages of Appendix D. The table below lists the owning or managing
agency, gateway name(s), make/model and whether the device is fixed or mobile.
Table D - 1[State/Region/Urban Area] Gateway
System(s)
Gateway Name
Owning Agency
Day-to-Day or
Incident / Event
Make / Model
Fixed / Mobile
No. of Simultaneous Nets
No. of Ports
D.1[Gateway Name]
Equipment
Location
This
gateway is stored [in or at] [address], [City/County], [State], [zip code]
Responsible
Agency
This
gateway is owned or managed by:[Agency/Jurisdiction]
Information on radio caches available for use within the
region is listed in subsequent pages of Appendix E. The table below lists the
owning or managing agency, cache, frequency band and quantity of radios in each
cache.
Table
E - 1[State/Region/Urban Area] Radio Cache(s)
Detailed information on mobile communications units (MCU) (also
known as Mobile Communications Center (MSS) or Mobile EOC) available within the
region is listed in subsequent pages of Appendix F.
Table
F - 1[State/Region/Urban Area] Mobile Communications Unit(s)
Unit ID / Designator
FEMA Type
Owning Agency
Deployment Area
F.1[Mobile Communications Unit Equipment Name]
Equipment Location
This Mobile Communications Unit equipment is stored [in or
at] [address], [City/County], [State], [zip code]
Responsible Agency
This Mobile Communications Unit is owned or managed by:[Agency/Jurisdiction]
Name:
Title:
Phone:
24/7 Phone:
Email:
Deployment Area
This Mobile Communications Unit is available for deployment
throughout [Describe jurisdiction or area where this unit can be used (for
example, City of [Name], County, or all counties in the [State/Region/Urban
Area])
Show perimeter and control lines, resources assignments,
incident facilities, and other special; information on a sketch map or
attached to the topographic or orthophoto map.
5.
Resources Summary
Enter the following information about the resources allocated
to the incident. Enter the number and type of resource ordered.
Resources Ordered
Enter the number and type of resource ordered.
Resource Identification
Enter the agency three letter designator, S/T, Kind/Type and
resource designator.
ETA/On Scene
Enter the estimated arrival time and place the arrival time or
a checkmark in the “on scene” column upon arrival.
Location/Assignment
Enter the assigned location of the resource and/or the actual
assignment.
6.
Current Organization
Enter on the organization chart the names of the individuals
assigned to each position. Modify the chart as necessary.
7.
Summary of Current Actions
Enter the name and position of the person completing the form.
8.
Prepared By
Enter Name and position of the person completing the form.
*Note
Additional pages maybe to ICS Form 201 if needed.
Purpose: The incident
Briefing form provides the Incident Commander (and the Command and General
Staffs assuming command of the incident) with basic information regarding the
incident situation and the resources allocated to the incident. It also serves
as a permanent record of the initial response to the incident.
Preparation: The briefing
form is prepared by the Incident Commander for presentation to the incoming
Incident Commander along with a more detailed oral briefing. Proper symbology
should be used when preparing a map of the incident.
Distribution: After the
initial briefing of the Incident Commander and General Staff members, the
Incident Briefing is duplicated and distributed to the Command Staff, Section
Chiefs, Branch Directors, Division/Group Supervisors, and appropriate Planning
and Logistic Section Unit Leaders. The sketch map and summary of current action
Resources Summary portion are given to the Resources Unit.
H.2ICS 205 (New)
INCIDENT
RADIO COMMUNICATIONS PLAN
Incident
Name
Date/Time
Prepared
Date/Time
Prepared
Ch #
Function
Channel Name/Trunked Radio System Talkgroup
Assignment
RX FreqN or W
RX Tone/NAC
TX
FreqN or W
Tx Tone/NAC
Mode
Remarks
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
5.
Prepared by
(CommunicationsUnit)
Incident
Location
Lat/Long
County/State
The
convention calls for frequency lists to show four digits after the decimal
place, followed by either an “N” or a “W”, depending on whether the frequency
is narrow or wide band.Mode
refers to either “A” or “D” indicating analog or digital (Project 25)
H.3ICS 205 Current Version
INCIDENT RADIO COMMUNICATIONS PLAN
1. Incident Name
2. Date/Time Prepared
3. Operational Period Date/Time
4.
Basic Radio Channel Utilization
Radio
Type/Cache
Channel
Function
Frequency/Tone
Assignment
Remarks
5. Prepared by (Communications Unit)
Instructions for Completing the Incident Radio Communications Plan (ICS
205 Form)
ITEM NUMBER
ITEM TITLE
INSTRUCTIONS
1.
Incident Name
Print the name assigned to the incident.
2.
Date/Time Prepared
Enter date (month, day, year) and time prepared (24-hour
clock).
3.
Operational Period
Date/Time
Enter the date and time. Interval for which the Radio
Communications Plan applies. Record the start time and end time and include
date(s).
4.
Basic Radio Channel Utilization System/Cache
Enter the radio cache system(s) assigned and used on the
incident (e.g., Boise Cache, FIREARMS, Region 5 Emergency Cache, etc).
Channel Number
Enter the radio channel numbers assigned.
Function
Enter the function each channel number is assigned (i.e.,
command, support, division tactical, and ground-to-air).
Frequency
Enter the radio frequency tone number assigned to each
specified function (e.g., 153.400).
Assignment
Enter the ICS organization assigned to each of the designated
frequencies (e.g., Branch I, Division A).
Remarks
This section should include narrative information regarding
special situations
5.
Prepared By
Enter the name of the Communications Unit Leader preparing the
form.
Purpose: The
Incident Radio Communications Plan provides in one location information on all
radio frequencies assignments for each operational period. The plan is a
summary of information obtained from the Radio Requirement Worksheet (ICS Form
216) and the Radio Frequency Assignment Worksheet (ICS Form 217). Information
from the Radio Communications Plan on frequency assignment is normally placed
on the appropriate Assignment List (ICS Form 204).
Preparation: The
Incident Radio Communications Plan is prepared by the Communications Unit
Leader and given to the Planning Section Chief.
Distribution: The Incident Radio
Communications Plan is duplicated and given to all recipients of the Incident
Objectives form including the Incident Communications Center. Information from
the plan is placed on Assignment List.
H.4ICS Form 210 (Status Change Card)
DESIGNATOR
NAME / ID.NO._____________________________________
_________________________________________________
STATUS
ASSIGNED
AVAILABLE
O/S REST
O/S MECHANICAL
O/S MANNING
____________ETR(O/S=Out of Service)
FROM
LOCATION
TO
DIVISION / GROUP
STAGING AREA
BASE / ICP
CAMP
ENROUTE
ETA
HOME AGENCY
MESSAGES
TIME___________
RESTAT
PROCESS
ICS
FORM
2106/83
STATUS CHANGE CARD
NFES 1334
Instructions for Completing the Status Change Card (ICS Form 210)
ITEM NUMBER
INSTRUCTIONS
Designator Name/ID No.
Enter the appropriate designator for the kind of resource. The
resource type code are in ICS 020-1, Resource Listings
Status
Determine the current status of the resource. If
out-of-service status is checked, enter the time when the resource will
return to service.
From/Location/To
Place ad checkmark in the FORM column indicating the current
location of the resource (where it came from). Also place a check in the TO
column indicating the assigned location of the resource. When more than one
Division, Staging Area, or Camp is used, identify the specific location
(e.g., Division A, Redfern, Staging Area, Camp Hood).
Message
Enter any special information provided by the resource or
dispatch center such as individual designator of strike teams and task
forces.
Time
Enter the time of the status change (24-hour clock).
Resources Process
This box is checked by Resources Unit personnel after the Unit
has transferred the information to a Resource Status Card (ICS Form 219).
Purpose: The
Status Change form is used by the Incident Communications Center Message to
record status change information received on resources assigned to the
incident.
Preparation: The
form is completed by radio/telephone operators who receive status change
information from individual resources, Task Forces, Strike Teams, and
Division/Group Supervisors. Status information could also be reported by
Staging Area and Helibase Managers or fixed-wing facilities.
Distribution:The Status Change Card is a two-part
form. The original is given to the Resources Unit, and the Communications Unit
retains a second (pink) copy.
H.5ICS 213
GENERAL MESSAGE
TO:
POSITION:
FROM:
POSITION:
SUBJECT:
DATE:
TIME:
MESSAGE:
SIGNATURE:
POSITION:
REPLY:
DATE:
TIME:
SIGNATURE/POSITION:
Instructions for Completing the General Message (ICS 213 Form)
ITEM NUMBER
INSTRUCTIONS
To
Indicate Unit/Person the General Message is intended for. Be
specific.
Office
Indicate the location where the Unit/Person is located, e.g.,
Ground Support Unit Leader, Simpson Camp, Communications, etc.
From
Indicate appropriate designation and location sender.
Subject
Fill in if applicable.
Date
List the date and time.
Message
Briefly complete. Think through the message before writing it
down. Try to be concise as possible.
Reply
This section is intended to be used by the Unit/Person who receives
the message to reply to your message.
Date
Record the date and time of reply.
Signature
Record signature and title of person who initiates the
message.
White Copy/Pink Copy
Both copies are sent by person who initiates the message.
Yellow Copy
Retained by the person who initiates the message.
Pink Copy
May be returned to the person who initiates the message.
The General Message form in use within the ICS is a
three-part form.
Purpose:The General Message form is used by:
1.Incident dispatchers to records incoming messages which
cannot be orally transmitted to the intended recipients.
2.Command Post and other incident personnel to transit
messages to the Incident Communications Center for transmission via radio or
telephone to the addressee.
3.Incident personnel to send any message or notification
to incident personnel which required a hard-copy delivery.
Initiation of the
Form: The General Message form may be initiated by incident dispatchers and
any other personnel on an incident.
Distribution:
upon completion, the General Message may be:
1.Hand carried to the addressee.
2.Hand carried to the incident Communications Center for
transmission.
Instructions for Completing the Unit Log (ICS 214 Form)
ITEM NUMBER
ITEM TITLE
INSTRUCTIONS
1.
Incident Name
Print the name assigned to the incident.
2.
Date Prepared
Enter date prepared (month, day, year).
3.
Time Prepared
Enter time prepared (24-hour clock).
4.
Unit Name
Enter the title of the organizational unit resource designator
(e.g., Facilities Unit, Safety Officer, and Strike Team).
5.
Unit Leader
Enter the name of the individual in charge of the unit.
6.
Operational Period
Enter the time span covered by the log (e.g., 1800 Oct.12 to
0600 Oct.13).
7.
Personnel Roster
List the name, position, and home based of each member
assigned to the unit during the operational period.
8.
Activity Log
Enter the time and briefly describe each significant
occurrence or event (e.g., task assignments, task completions, injuries,
difficulties encountered, etc.)
9.
Prepared By
Enter Name and title of the person approving the log. Provide
log to immediate supervisor at the end of each operational period.
Purpose: The Unit
Log is used to record details of unit activity strike team activity. The file
of these logs provides a basic reference which to extract information for
inclusion ion any after-action report.
Preparation: A
Unit Log is initiated and maintained by Command Staff members, Division/Group
Supervisors, Air Operations Group/Strike Team/Task Force Leaders, and Unit
Leaders. Completed logs are forwarded to supervisors who provide to the
Documentation Unit.
Distribution: The
Documentation Unit maintains a file of all Unit Logs. It is necessary that one
copy of each log be submitted to the Documentation Unit.
