Logo (Optional)
State of Rhode Island
Tactical
Interoperable Communications Plan (TICP)
October 2009
Logo (Optional)
Tactical Interoperable Communications Plan
Signature Page
Approved
by:
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
Concurrence:
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
_________________________________ __________________
Name/Title/Agency Date
![]()
Record of
Change
|
Description |
Change Date |
Approved By |
|
|
001 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
Table of Contents
1 [Rhode Island /Providence UASI] Information
1.1 Participating Jurisdictions/Agencies/Disciplines
1.1.1 Nongovernmental Agencies Represented in the TICP
1.1.2 Tribal Entities Represented in the TICP
1.1.3 Other TICP(s) in the State
2.4 Responsibilities of the [Governing Body]
2.6 TICP Maintenance and Update
2.7 Agency Responsibilities and Rights
2.8 Prioritization and Shared Use of Regional
Interoperability Assets
3 Interoperability Equipment, Policies, and Procedures
Region-wide
Shared System Technology Overview
Region-wide
Shared System Policies and Procedures
Region-wide
Shared System Rules of Use
Region-wide
Shared System Problem ID and Resolution
[Name]
Shared System Technology Overview
[Name]
Shared System Policies and Procedures
[Name]
Shared System Rules of Use
[Name]
Shared System Problem ID and Resolution
3.1.1 Intra-System Shared Interoperability Channel(s)
Definition
of an Intra-System Shared Channel
Intra-System
Shared Channel Technology Overview
Designated
Intra-System Interoperability Channel(s)
[Name]
Intra-System Shared Channel Policies and Procedures
[Name]
Intra-System Shared Channel Rules of Use
[Name]
Intra-System Shared Channel Problem ID and Resolution
[Name]
Intra-System Shared Channel
[Name]
Intra-System Shared Channel Technology Overview
Designated
Intra-System Interoperability Channel(s)
[Name]
Intra-System Shared Channel Policies and Procedures
[Name]
Intra-System Shared Channel Rules of Use
[Name]
Intra-System Shared Channel Problem ID and Resolution
3.2 Inter-System Shared Channel(s) Policies and Procedures
Definition
of a Region-wide Inter-System Shared Channel
Region-wide
Inter-System Shared Channel Technology Overview
Region-wide
Inter-System Interoperability Channel(s)
Region-wide
Inter-System Shared Channel Policies and Procedures
Region-wide
Inter-System Shared Channel Rules of Use
Region-wide
Inter-System Shared Channel Problem ID and Resolution
[Name/Jurisdiction]
Inter-System Shared Channel
[Name]
Inter-System Shared Channel Technology Overview
Designated
Inter-System Interoperability Channel(s)
[Name]
Inter-System Shared Channel Policies and Procedures
[Name]
Inter-System Shared Channel Rules of Use
[Name]
Inter-System Shared Channel Problem ID and Resolution
3.2.1 ICALL/ITAC Shared Channel(s)
[Name]
ICALL/ITAC Shared Channel Technology Overview
[Name]
ICALL/ITAC Shared Channel Policies and Procedures
[Name]
ICALL/ITAC Shared Channel Rules of Use
[Name]
ICALL/ITAC Shared Channel Problem ID and Resolution
3.2.2 [Name/Jurisdiction] ICALL/ITAC Shared Channel
[Name]
ICALL/ITAC Shared Channel Technology Overview
[Name]
ICALL/ITAC Shared Channel Policies and Procedures
[Name]
ICALL/ITAC Shared Channel Rules of Use
[Name]
ICALL/ITAC Shared Channel Problem ID and Resolution
3.3.1 Region-wide Gateway Policies and Procedures
Region-wide
Gateway Rules of Use
Region-wide
Gateway Communications Request
Region-wide
Gateway Deployment Procedures
Region-wide
Gateway Activation Procedures
Region-wide
Gateway Deactivation Procedures.
Region-wide
Gateway Problem ID and Resolution
Region-wide
Gateway Limitations
Region-wide
Gateway Test Procedures
[Name]
Mobile Gateway Deployment Procedures
[Name]
Fixed Gateway Activation Procedures
[Name]
Gateway Deactivation Procedures.
[Name]
Gateway Problem ID and Resolution
[Name]
Gateway Test Procedures
[Name]
Mobile Gateway Deployment Procedures
[Name]
Fixed Gateway Activation Procedures
[Name]
Gateway Deactivation Procedures.
[Name]
Gateway Problem ID and Resolution
[Name]
Gateway Test Procedures
3.4.1 Region-wide Cache Radio Policies and Procedures
Region-wide
Radio Cache Rules of Use
Region-wide
Radio Cache Request
Region-wide
Radio Cache Equipment Activation
Region-wide
Radio Cache Equipment Deactivation
Region-wide
Radio Cache Problem ID and Resolution
[Name]
Radio Cache Rules of Use
[Name]
Radio Cache Interoperable Communications Request
[Name]
Radio Cache Equipment Activation Procedures
[Name]
Radio Cache Equipment Deactivation Procedures
[Name]
Radio Cache Equipment Problem ID and Resolution
[Name]
Radio Cache Rules of Use
[Name]
Radio Cache Interoperable Communications Request
[Name]
Radio Cache Equipment Activation Procedures
[Name]
Radio Cache Equipment Deactivation Procedures
[Name]
Radio Cache Equipment Problem ID and Resolution
3.5 Mobile Communications Units
3.5.1 Mobile Communications Unit Policies and Procedures
Mobile
Communications Unit Technology Overview
Mobile
Communications Unit Rules of Use
Mobile
Communications Unit Interoperable Communication Request
Mobile
Communications Unit Activation Method
Mobile
Communications Unit Deactivation Method
Mobile
Communications Unit Problem ID and Resolution
4 Regional Emergency Resource Staffing
Appendix
C Inter-system Shared Channels
Appendix
F Mobile Communications Units
Appendix
G Policy Documents, Governing Documents, MOUs, and
Agreements
Appendix
H Incident Command System Planning
Appendix
I Reference Materials
List of Tables
Table 1 Jurisdictions, Agencies, and
Disciplines Represented in the TICP
Table 2
[State/Region/Urban Area] Shared System(s)
Table 3
Intra-System Shared Channel(s)
Table 4
Intra-System Shared Channel(s)
Table 5
Inter-System Shared Channel(s)
Table 6
Inter-System Shared Channel(s)
Table 7
ICALL/ITAC Shared Channel(s)
Table 8
[State/Region/Urban Area] Gateway Systems
Table 9
[State/Region/Urban Area] Radio Cache(s)
Table 10
Required Channels for [State/Region/Urban Area] 700 MHz Cache Radio(s)
Table 11
Optional Channels for [State/Region/Urban Area] 700 MHz Cache Radio(s)
Table 12
Required Channel for [State/Region/Urban Area] 800 MHz Cache Radio(s)
Table 13
Optional Channels for [State/Region/Urban Area] 800 MHz Cache Radio(s)
Table 14
Required Channels for [State/Region/Urban Area] UHF Cache Radio(s)
Table 15
Optional Channels for [State/Region/Urban Area] UHF Cache Radio(s)
Table 16
Required Channels for [State/Region/Urban Area] VHF Cache Radio(s)
Table 17
Optional Channels for [State/Region/Urban Area] VHF Cache Radio(s)
Table 18
[State/Region/Urban Area] Mobile Communications Unit(s)
Table 19
Regional Emergency Resource Personnel
Table 20
CASM AM POC Information.
Table A - 1
Dispatch Center Points of Contact
Table A - 2
Nongovernmental Agency Contact Information
Table A - 3
[Governing Body] Contact Information
Table A - 4
Subcommittee Working Group Member Information
Table B - 1
[State/Region/Urban Area] Shared System(s)
Table B - 2
[Name] Shared Channel Information
Table B - 3
[Name] Shared Talkgroup Information
Table C - 1
[State/Region/Urban Area] 700 MHz Inter-system Shared Channel(s)
Table C - 2
[State/Region/Urban Area] 800 MHz Inter-system Shared Channel(s)
Table C - 3
[State/Region/Urban Area] UHF Inter-system Shared Channel(s)
Table C - 4
[State/Region/Urban Area] VHF Inter-system Shared Channel(s)
Table D - 1
[State/Region/Urban Area] Gateway System(s)
Table E - 1
[State/Region/Urban Area] Radio Cache(s)
Table F - 1
[State/Region/Urban Area] Mobile Communications Unit(s)
List of Figures
Figure 1
[State/Region/Urban Area] Governance Organization Chart
Figure F - 1
[Mobile Communications Unit [Equipment Name]
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 1 Jurisdictions, Agencies, and Disciplines Represented in the TICP
|
Jurisdiction |
Agency |
Discipline |
|
See
Appendix A-1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The primary and alternate points of contact (POC) for copies of or questions regarding this Plan are:
Primary:
Agency Name: RIEMA
POC Name: Michael Walsh
Title: SWIC
Address: 645 New London Ave Cranston RI 02920
Office Phone: 462 7188
Cell Phone: 641 7772
24/7 Phone:
E-Mail: Michael.walsh14@us.army.mil
Alternate:
Agency Name: RIEMA
POC Name: David Smith
Title: Director
Address: 645 New London Ave
Office Phone: 996 9996
Cell Phone:
24/7 Phone:
E-Mail: james.d.smith18@us.army.mil
2nd
Alternate:
Agency Name:
POC Name:
Title:
Address:
Office Phone:
Cell Phone:
24/7 Phone:
E-Mail:
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:

Figure 1 [State/Region/Urban Area] Governance Organization Chart
Appendix A provides POC information for members of the governing body and its subcommittees.
The ICC will:
The ICC meets regularly at RIEMA on the first Tuesday and second Thursday of each month at 0900 am].
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:
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):
When the same resources are requested for two or more incidents, resource assignments should be based on the priority levels listed below:
In the event of multiple simultaneous incidents within the same priority level, the resources should be allocated with the following priorities in mind:
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.
Table 2 [State/Region/Urban Area] Shared System(s)
|
Radio System Name |
Make / Model |
Type |
Frequency Band |
Owning Agency |
Service Area |
|
RISCON |
Mot.
Digital |
Trunk
7.5 |
NA |
RI/Prov |
RI |
|
|
|
|
|
|
|
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:
o The lead agency dispatcher notifies the [Communications Coordinator (COMC)/Communications Unit Leader (COML)/designee] that interoperability channels/talkgroups are in use.
o Each agency’s dispatch center tells additional en-route responders what interoperability channels are in use for the incident.
o The 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 an incident:
Following an incident, the following general problem ID and resolution processes apply to all shared systems:
(Note: Policies and procedures specific to a single shared system
are listed subsequent to that specific shared system below)
The RISCON system consists of The Motorola Trunk 7.5 digital system
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.
Table 3 Intra-System Shared Channel(s)
|
System |
Channel Name |
Primary Use |
Agencies Supported |
Frequency/Band |
|
|
|
|
|
|
|
|
|
|
|
|
The policies and procedures in this section apply to the local, regional, State, and Federal channels shared across multiple systems.
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:
During an incident:
Following an incident, the following general problem ID and resolution processes apply to all shared channels:
(Note: Policies and procedures specific to a
single intra-system shared channel are listed subsequent to specific intra-system
shared channels below.)
Table 4 Intra-System Shared Channel(s)
|
System |
Channel Name |
Primary Use |
Agencies Supported |
Frequency/Band |
|
|
|
|
|
|
|
|
|
|
|
|
[Add text]
[Add text]
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.
Table 5 Inter-System Shared Channel(s)
|
Channel Name |
Primary Use |
Agencies Supported |
Frequency/Band |
|
|
|
|
|
The policies and procedures in this section apply to the local, regional, State, and Federal channels shared across multiple systems.
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:
During an incident:
Following an incident, the following general problem ID and resolution processes apply to all shared channels:
(Note:
Policies and procedures specific to a single shared channel are listed
subsequent to that specific shared channel below)
[Add text]
Table 6 Inter-System Shared Channel(s)
|
Channel Name |
Primary Use |
Agencies Supported |
Frequency/Band |
|
|
|
|
|
[Add text]
[Add text]
3.2.1 ICALL/ITAC Shared Channel(s)
(Note: Although this is titled ICALL/ITAC, use
nomenclature specific to the site, i.e. UCALL/UTAC, VCALL/VTAC, etc.)
Table 7 ICALL/ITAC Shared Channel(s)
|
Channel Name |
Primary Use |
Agencies Supported |
Frequency/Band |
|
|
|
|
|
|
|
|
|
|
[Add text]
[Add text]
[Add text]
[Add text]
3.2.2 [Name/Jurisdiction] ICALL/ITAC Shared Channel
[Add text]
[Add text]
[Add text]
[Add text]
“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.
Table 8 [State/Region/Urban Area] Gateway Systems
|
Gateway Name |
Owning Agency |
Day-to-Day or Incident / Event |
Make / Model |
Fixed / Mobile |
No. of Simultaneous Nets |
No. of Ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3.3.1 Region-wide Gateway Policies and Procedures
The following rules of use shall govern interoperable communications between agencies via gateways:
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:
Upon receiving a request for the deployment of a mobile gateway, the owning agency dispatcher should follow these deployment procedures:
The mobile gateway operator should follow these deployment procedures:
Once the owning agency grants authorization to use their fixed gateway, the region-wide procedures for establishing communications connectivity are:
When the gateway connection(s) is (are) no longer required, agencies should follow these deactivation procedures:
Following an incident, the following general problem ID and resolution processes apply to all regional gateways:
To ensure that equipment components of the gateway operate properly, each agency will participate in the following testing procedure:
(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.
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
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.
Table 9 [State/Region/Urban Area] Radio Cache(s)
|
Radio Cache Name |
Make / Model |
Owning / Managing Agency |
Frequency Band |
Quantity |
|
|
|
|
|
|
|
|
|
|
|
|
3.4.1 Region-wide Cache Radio Policies and Procedures
[State/Region/Urban Area] radio caches have the following characteristics:
All [State/Region/Urban Area] 700 MHz radio caches are required to have the following channels/talkgroups programmed:
Table 10 Required Channels for [State/Region/Urban Area] 700 MHz Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
If possible, the following channels/talkgroups should also be programmed into [State/Region/Urban Area] 700 MHz cached radios:
Table 11 Optional Channels for [State/Region/Urban Area] 700 MHz Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
All [State/Region/Urban Area] 800 MHz radio caches are required to have the following channels/talkgroups programmed:
Table 12 Required Channel for [State/Region/Urban Area] 800 MHz Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
If possible, the following channels/talkgroups should also be programmed into [State/Region/Urban Area] 800 MHz cached radios:
Table 13 Optional Channels for [State/Region/Urban Area] 800 MHz Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
All [State/Region/Urban Area] UHF radio caches are required to have the following channels programmed:
Table 14 Required Channels for [State/Region/Urban Area] UHF Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
If possible, the following channels should also be programmed into [State/Region/Urban Area] UHF cached radios:
Table 15 Optional Channels for [State/Region/Urban Area] UHF Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
All [State/Region/Urban Area] VHF radio caches are required to have the following channels programmed:
Table 16 Required Channels for [State/Region/Urban Area] VHF Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
If possible, the following channels should also be programmed into [State/Region/Urban Area] VHF cached radios:
Table 17 Optional Channels for [State/Region/Urban Area] VHF Cache Radio(s)
|
Channel Name |
Primary Use |
|
|
|
The following are general rules of use and apply to all [State/Region/Urban Area] radio caches:
● Unit Identification – Announce your home agency prior to announcing your unit identifier during interoperable communication situations. (i.e., [Local Example Here])
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:
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.
The radio cache technician (or designee) should follow these deployment procedures:
o Each 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.
o The 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
When the radio cache is no longer required, agencies should follow these deactivation procedures:
During an incident:
Following an incident, the following general problem ID and resolution processes apply to all regional radio caches:
(Note:
Policies and procedures specific to a single radio cache are listed subsequent to
that specific cache below)
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
3.4.3 [Name] Radio Cache
[Add text]
[Add text]
[Add text]
[Add text]
[Add text]
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)
|
Unit ID / Designator |
FEMA Type |
Owning Agency |
Deployment Area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3.5.1 Mobile Communications Unit Policies and Procedures
[Add text]
[Add text]
[Add text]
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:
The MCU Agency determines if the MCU is available for use and coordinates the deployment with the requesting agency Incident Commander or their designee.
[Add text]
[Add text]
Emergency Resource
Directory
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.
Table 19 Regional Emergency Resource Personnel
|
|
Name |
Agency |
Address |
Phone |
Email |
|
COMC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
COML |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INCM |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RADO |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cache THSP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Gateway THSP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other THSP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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:
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.
The CASM AM POC is listed in the following table:
Table 20 CASM AM POC Information
|
Name |
Phone |
Email |
Area
of Responsibility |
|
|
|
|
|
|
|
|
|
|
A.1 Dispatch Centers
Table A - 1 Dispatch Center Points of Contact
|
Name |
24/7 Contact |
Organizations / Agencies Served |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A.2 Nongovernmental Agency Contact Information
Table A - 2 Nongovernmental Agency Contact Information
|
Agency |
Name |
Position |
Phone |
Email |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A.3 [Governing Body] Member Information
Table A - 3 [Governing Body] Contact Information
|
Agency |
Name |
Position |
Phone |
Email |
Governing
Body(s) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A.4 Subcommittee Working Group Member Information
Table A - 4 Subcommittee Working Group Member Information
|
Agency
|
Name |
Position |
Phone |
Email |
Subcommittee(s) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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)
|
Make / Model |
Type |
Frequency Band |
Owning Agency |
Service Area |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
B.1 [Shared System Name]
Responsible Agency
This radio system is owned or managed by: [Agency/Jurisdiction]
Name:
Title:
Phone:
24/7 Phone:
Email:
Number of Radios
|
No. of Mobile Radios on this System: |
|
|
No. of Portable Radios on this System: |
|
System Type
|
Radio System Make: |
|
|
Trunked / Conventional/Both: |
|
|
Radio System Model: |
|
|
Radio System Frequency Band: |
|
|
P25 Compliancy: |
|
|
Number of Channels: |
|
|
Encryption Protocol: |
|
|
Year Installed: |
|
|
Repeated/Simplex/Both: |
|
|
Analog / Digital / Both: |
|
|
Wideband / Narrowband / Both: |
|
|
Voted: |
|
|
Simulcast: |
|
Service area
[Add service area information]
Participating Agencies
Shared Channels
Table B - 2 [Name] Shared Channel Information
|
Channel Name |
Analog / Digital |
Wide / Narrow |
Tx and Tone |
Rx and Tone |
Primary Use |
Agencies Supported |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Shared Talk Groups
Table B - 3 [Name] Shared Talkgroup Information
|
Talkgroup Name |
Talkgroup ID |
Primary Use |
Agencies Supported |
|
|
|
|
|
|
|
|
|
|
Other Shared Channel/Talkgroup Notes:
[Add notes]
Appendix C Inter-system Shared Channels
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)
|
Channel Name |
Analog / Digital |
Wide / Narrow |
Tx and Tone |
Rx and Tone |
Talkgroup ID |
Primary Use |
Agencies Supported |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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]
Name:
Title:
Address:
Phone:
24/7 Phone:
Email:
Service Area
[Add service area information]
Participating Agencies
Other Gateway Notes:
[Add notes]
Appendix E Radio Caches
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)
|
Radio Cache Name |
Make / Model |
Owning / Managing Agency |
Frequency Band |
Quantity |
|
|
|
|
|
|
|
|
|
|
|
|
E.1 [Radio Cache Name]
This radio cache is stored [in or at] [address], [City/County], [State], [zip code]
This radio cache is owned or managed by: [Agency/Jurisdiction]
Title:
Phone:
24/7 Phone:
Email:
Service Area
[Add service area information]
Cache Description:
|
Make / Model: |
|
|
Frequency Band: |
|
|
No. of Radios in Cache: |
|
|
No. of Available Channels: |
|
|
No. of Spare Batteries: |
|
Channels Programmed on Cache
[Add text]
|
Radio
System Name |
Channel
Identification |
|
|
|
|
|
|
|
|
|
Talk Groups Programmed on Cache
[Add text]
Other Cache Notes:
[Add text]
Appendix F Mobile Communications Units
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])
System Type and Capacity
|
Unit ID / Designator: |
[Unique
Name] |
|
Owning Agency |
[Owner
of the MCU] |
|
Type/Make/Model: |
[Enter
Information] |
|
Quantity: |
[#] |
|
Primary Deployment Method
(Other) |
[Vehicle
Chassis Mount, Trailer, Airlift Container, Other] |
|
Deployment Method |
[Describe
Method if Above is Other] |
|
MCU Storage Address |
[Add
Address] |
|
Latitude |
[Optional/Add
Lat where MCU is stored] |
|
Longitude |
[Optional/Add
Long where MCU is stored] |
|
Year Activated |
[Year] |
|
FEMA Type |
[Type
1, Type 2, Type 3, Type 4, Other] |
|
Activation Method |
[Describe] |
|
General Comments |
[Comments] |
|
Time to Setup |
[# of
Minutes Expected to setup the Unit] |
|
Chassis Size |
[Chassis
Size in Feet] |
|
Capability to Extend a Regional
LMR System |
[Yes/No] |
|
Dispatch Capability |
[Yes/No] |
|
Number of Dispatch Consoles |
[#] |
|
SATCOM Capability |
[Yes/No] |
|
SATCOM Type |
[INMARSAT,
AMSC, etc.] |
|
Number of Phone/Data Lines |
[#] |
|
Microwave Connectivity
Capability |
[Yes/No] |
|
PBX Capability |
[Yes/No] |
|
Cellular PBX |
[Yes/No] |
|
Capability FAX Capability |
[Yes/No] |
|
Computer Server Capability |
[Yes/No] |
|
LAN Capability |
[Yes/No] |
|
Number of Workstations |
[#] |
|
Conference |
[Yes/No] |
|
Internet Access |
[Yes/No] |
|
Network Access Speed in KBPS |
[#] |
|
Video Teleconference Capability |
[Yes/No] |
|
On Scene Video Monitoring Capability |
[Yes/No] |
|
Self-contained Power Supply
Capacity (Watts) |
[#] |
|
TV Reception Capability |
[Yes/No] |
|
Expandable Mast |
[Yes/No] |
Other Mobile Communications Unit Equipment Notes:
[Add notes]

Figure F - 1 [Mobile Communications Unit [Equipment Name]
Appendix G Policy Documents, Governing Documents, MOUs, and Agreements
G.1 [Name of Policy, Governing, MOU, and/or Agreement]
[Add a reference and/or link to the above named document]
G.2 [Name of Policy, Governing, MOU, and/or Agreement]
[Add a reference and/or link to the above named document]
G.3 [Name of Policy, Governing, MOU, and/or Agreement]
[Add a reference and/or link to the above named document]
G.4 [Name of Policy, Governing, MOU, and/or Agreement]
[Add a reference and/or link to the above named document]
Appendix H Incident Command System Planning
This appendix contains forms for incident command system (ICS) planning.
ICS Forms can also be found at the following website: http://training.fema.gov/EMIWeb/IS/ICSResource/ICSResCntr_Forms.htm
Note: A copy of completed ICS Forms should also be distributed to the COML.
|
INCIDENT
BRIEFING |
1. INCIDENT NAME |
2. DATE |
3. TIME PREPARED |
||||||||
|
4. MAP SKETCH (NTS) |
|
|||||||||||
|
Function |
Frequency or Talkgroup
Name |
Assignment |
Function |
Frequency or Talkgroup
Name |
Assignment |
|
||||||
|
Command |
|
|
Tactical |
|
|
|
||||||
|
|
|
|
Tactical |
|
|
|
||||||
|
Tactical |
|
|
Tactical |
|
|
|
||||||
|
Tactical |
|
|
|
|
|
|
||||||
|
Tactical |
|
|
Staging |
|
|
|
||||||
|
|
|
|||||||||||
|
5. PREPARED BY (NAME AND POSITION) |
|
|||||||||||
|
201 ICS (7/2006) PAGE
1 of 4 NFES
1325 |
|
|||||||||||
|
6. SUMMARY OF CURRENT ACTIONS |
|||||||||||
|
Time |
Summary of Action |
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
|
|
||||||||||
|
|
Continue
on NIMS/ICS Form 214 Unit Log |
|
||||||||||
|
201 ICS (7/2006) PAGE
2 of 4 NFES
1325 |
|
|||||||||||
|
7. CURRENT ORGANIZATION – Place name and contact
information (talkgroup/channel name, numbers, etc.) below the dividing line. |
|
|
|
|
|
|
201 ICS (7/2006) PAGE
3 of 4 NFES
1325 |
|
|
|
8. RESOURCES SUMMARY |
|||||
|
RESOURCES
ORDERED |
RESOURCES
IDENTIFICATION |
ETA |
ON
SCENE ü |
LOCATION/ASSIGNMENT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
201 ICS (7/2006) PAGE
4 of 4 NFES
1325 |
|
|||||
Instructions for Completing the Incident Briefing (ICS 201 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. |
Map Sketch |
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.2 ICS 205 (New)
|
INCIDENT
RADIO COMMUNICATIONS PLAN |
Incident
Name |
Date/Time
Prepared |
Date/Time
Prepared |
|||||||
|
|
|
|||||||||
|
Ch # |
Function |
Channel Name/Trunked Radio System Talkgroup |
Assignment |
RX Freq N or W |
RX Tone/NAC |
TX
Freq
N 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 (Communications Unit) |
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.3 ICS 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.4 ICS Form 210 (Status Change Card)
|
DESIGNATOR NAME / ID.NO._____________________________________ _________________________________________________ |
||||||||
|
STATUS |
|
|||||||
|
____________ETR (O/S=Out of Service) |
||||||||
|
FROM |
LOCATION |
TO |
||||||
|
|
DIVISION / GROUP |
|
||||||
|
|
STAGING AREA |
|
||||||
|
|
BASE / ICP |
|
||||||
|
|
CAMP |
|
||||||
|
|
ENROUTE |
ETA |
||||||
|
|
HOME AGENCY |
|
||||||
|
MESSAGES |
||||||||
|
TIME___________ |
RESTAT |
|||||||
|
ICS FORM 210 6/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.5 ICS 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.
|
UNIT
LOG |
1. Incident Name |
2. Date Prepared |
3. Time Prepared |
|
|
4. Unit Name/Designators |
5. Unit Leader (Name and
Position) |
6. Operational Period |
||
|
7. Personnel
Roster Assigned |
||||
|
Name |
ICS
Position |
Home
Base |
||
|
|
||||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
8. Activity
Log |
||||
|
Time |
Major
Events |
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
9. Prepared by (Name and
Position) |
||||
|
Time |
Major
Events |
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
214 ICS 5-80 |
9. Prepared by (Name and
Position) |
|||
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.
H.7 ICS Form 216
|
RADIO REQUIREMENTS WORKSHEET |
1. Incident Name |
2. Date |
3. Time |
||||||||||||||
|
4. Branch |
5. Agency | ||||||||||||||||