KING COUNTY FIRE RESOURCE PLAN Section 9 King County Radio Interoperability

Save this PDF as:

Size: px
Start display at page:

Download "KING COUNTY FIRE RESOURCE PLAN Section 9 King County Radio Interoperability"


1 KING COUNTY FIRE RESOURCE PLAN Section 9 King County Radio Interoperability Adopted 11/16/16 Revised 7/27/ PURPOSE 1.1 This procedure is adopted by the King County Fire Chiefs as a standard for all fire departments within King County as a countywide standard. 2.0 REFERENCES 2.1 The region s Tactical Interoperability Communications Plan (TICP) details the interoperability channel banks and their use Radio systems participating in this model include: Snohomish Emergency Radio System (SERS) King County (KC) Radio System Port of Seattle (PoS) Radio System Pierce County/Tacoma/Puyallup radio systems 3.0 POLICY STATEMENT 3.1 In an effort to improve regional communications interoperability during significant incidents, emergency responders, dispatch centers (PSAPs), and public safety radio system managers throughout the Central Puget Sound region, have agreed to implement a system of shared channels to enhance radio interoperability. 3.2 The system consists of policies, procedures and operating guides governing a collection of radio channel banks to be programmed into all capable public safety radios. 4.0 DEFINITIONS 4.1 Authority - Authority for the implementation and use of these interoperability channel banks comes under the authority of those agencies/departments listed as signatories to the Central Area Puget Sound Tactical Interoperable Communications Plan (TICP). 4.2 Permitted users - Only public safety users shall have access to all radio channel banks. Non-public safety radios should include non-trunked interoperability channel banks for general access. If non-public safety users require access to the interoperability channel banks, they will be patched in at the PSAP level. Section 9 Radio Interoperability Procedure Page 1 Revised: 7/27/16

2 4.3 Zone channel configuration(s) - While the five (5) interoperability channel banks can be located anywhere in a regional radio s template, the channel banks shall be a contiguous grouping and identical in all radios. 5.0 MODEL PROCEDURE 5.1 Where an agency/jurisdiction is unable, through physical radio limitations, to include all of the regional interoperability channel banks, they shall still attempt to adhere to the following format, as best they are able. 5.2 The interoperability channel banks shall be listed in the following order (south-tonorth), with the conventional channel banks being last. PC/Tacoma/Puyallup, Port of Seattle, King County, Snohomish County, State/Nationwide Interoperability. Pierce C/Tac/Puy Port of Seattle King County Snohomish Co GENERAL LAW FIRE NATIONAL STATE INTER OP INTER OP INTER OP INTER OP 700 INTEROP 700 INTEROP 700 INTEROP 800 INTEROP INTEROP 1 MA PC1 POS CALL KC CALL SNO CALL 7CALL50 7CALL50 7CALL50 8CALL90 ST OPS1 2 MA PC2 POS IO 02 KC IO 02 SNO IO 02 7CALL70 7CALL70 7CALL70 8CALL90D ST OPS1D 3 PSOPS3 POS IO 03 KC IO 03 SNO IO 03 7TAC71 7TAC71 7TAC71 8TAC91 ST OPS2 4 PSOPS4 POS IO 04 KC IO 04 SNO IO 04 7TAC71D 7TAC71D 7TAC71D 8TAC91 D ST OPS2D 5 PCLERN POS IO 05 KC IO 05 SNO IO 05 7TAC72 7TAC72 7TAC72 8TAC92 ST OPS3 6 ST OPS1D POS IO 06 KC IO 06 SNO IO 06 7TAC72D 7TAC72D 7TAC72D 8TAC92 D ST OPS3D 7 ST OPS2D POS IO 07 KC IO 07 SNO IO 07 7GTAC57 LAW61 7FIRE63 8TAC93 ST OPS4 8 7CALL70* POS IO 08 KC IO 08 SNO IO 08 7GTAC57D LAW61D 7FIRE63D 8TAC93 D ST OPS4D 9 7TAC71* POS IO 09 KC IO 09 SNO IO 09 7MOB59 LAW62 7FIRE84 8TAC94 ST OPS5 10 7TAC72* POS IO 10 KC IO 10 SNO IO 10 7MOB59D LAW62D 7FIRE84D 8TAC94 D ST OPS5D 11 7TAC75* POS IO 11 KC IO 11 SNO IO 11 7TAC75 7TAC75 7MED LAW81* POS IO 12 KC IO 12 SNO IO 12 7TAC75D 7TAC75D 7MED65D 13 7FIRE84* POS IO 13 KC IO 13 SNO IO 13 7GTAC77 LAW81 7MED FIRE84* POS IO 14 KC IO 14 SNO IO 14 7GTAC77D LAW81D 7MED66D 13 7FIRE84* POS IO 15 KC IO 15 SNO IO 15 7MOB79 LAW 82 7TAC75 16 TP EMERP POS EM P KC EM P SNO EM P 7MOB79D LAW 82D 7TAC75D or or or or TP EMERF POS EM F KC EM F SNO EM F *These Pierce County Interoperable conventional channels require P25-Phase I (FDMA) enabled radios. 5.3 Include conventional channel banks - the last channel banks will include the Statewide and Nationwide 700 MHz and 800 MHz interoperability channels, in both their direct and repeated configurations All radios (police, fire, general government, etc.) will have all conventional channels, regardless of general-use classifications for specific channels (e.g., Law priority, Fire/EMS priority, General government priority, etc.). Section 9 Radio Interoperability Procedure Page 2 Revised: 7/27/16

3 While they are not currently governed by this section of the TICP, regional public safety users should consider inclusion of additional nationwide 700 MHz interoperable channels in their radio templates, as capabilities permit. 5.4 Interoperability Channel Assignments Assignment guidelines for the interoperable talk groups contained within the trunked radio system zones are identified as: IO 01 - (Hailing/Announcement/Calling) IO 02 through IO 15 - (Operations - Law Enforcement and Fire/EMS) IO 16 - (Dedicated emergency channel) IO 01 - Calling Channel: This talk group is not to be used as a command/tactical channel. The calling channel shall be used for: Hailing/Announcing When responders come into a radio system area, apart from their home system, and have not already been told which interoperability channel to switch to, they should utilize the calling channel to identify themselves and their mission/destination. The PSAP will acknowledge per the section on Requests below. (Example - This is the Seattle Fire Department medical strike team on the Port of Seattle radio interop zone, coming to assist with a plane crash at SeaTac. We are requesting a channel assignment. Port of Seattle dispatchers would then tell the SFD strike team the appropriate PoS interoperability channel to switch to.) Periodic Announcements When multiple responders are expected to come into a radio system area, a PSAP may make periodic, preemptive announcements (Example - Units responding to the land slide in Snohomish County, please switch to Snohomish County Interop Channel 7 and talk to incident staging ) Monitoring - All PSAPs shall monitor the Interoperability Calling Channel for their respective radio system. While PSAPs may not have requested outside aid, and hence not be expecting anyone to call them specifically, they should remain aware of which regional interoperability channels are being utilized, should they have a future need for their own jurisdictions, or should they also send units to assist in an on-going incident Requests - Units requesting a channel assignment will be primarily acknowledged by the PSAP supporting the incident(s) for which those units are coming to assist. If, after multiple attempts at hailing by a unit are unanswered, an adjacent PSAP shall acknowledge the hailing unit and advise the unit to stand by while contact with the primary PSAP is attempted by other means (phone, PSAP-Net, TRIS Intercom, etc.) IO 02 IO 15 - Coordinating and Assigning: While all channels may be utilized by any/all public safety agencies, for the sake of convenience and efficiency, PSAPs will assign interoperability channels using the following guidelines. For those incidents/events that are multi-discipline in nature, discretion will be left Section 9 Radio Interoperability Procedure Page 3 Revised: 7/27/16

4 up to the assigning PSAP. Consideration should be given the primary focus of the incident at the time Law enforcement agencies requesting use of an interoperability talk group from a channel bank should first be assigned channels in the top half portion of the bank. When possible LE PSAPS should assign top down (e.g., KC IO2, then KC IO3, etc.) Fire/EMS agencies requesting use of an interoperability talk group from a channel bank should first be assigned channels in the bottom portion (bottom up), of the channel bank. (e.g., KC IOP 15, KC IOP 14, etc.) Types of interoperability channel use: Impromptu use - Impromptu use is defined as that use which is unplanned and related to public safety emergencies. A notification to all PSAPs should occur as soon as possible after assignment. This will likely be on a system s PSAP talk group or other talk group/intercom resource. For this reason, it is imperative that all PSAPs continuously monitor their respective PSAP Intercom, TRIS Intercom, Interoperability Calling channels or other assigned system wide communication resource Patching During impromptu use, and when possible, interoperability channels should be console-patched to the relevant agency/system talk groups to minimize system overloading. Having initial units switch talk groups in the middle of an incident presents safety concerns and potentially consumes additional system resources Pre-planned Use - Pre-planned use of the regional interoperability trunked talk groups differs from the previously mentioned Impromptu use in that a formal communications plan (F-205) needs to be developed by the COML/PSAP working for the Incident Commander. The F-205 should include the interoperable talk group(s) to be used, talk groups that will be patched into the interoperable talk groups (if applicable), contact information of the lead COML/PSAP, and (either attached or in the notes section) a listing of participating agencies. The Communications Plan (F-205) - Should be disseminated to the other PSAPs that are primary users of the specific radio system with as much lead time as possible to allow for review by all PSAP shifts. Coordination - done over PSAP net, TRIS Intercom and/or Interoperability Calling channel), 8CALL90, or other, if needed - Immediately prior to the planned event, radio system PSAPs should again be alerted by the hosting PSAP as appropriate. Notification should include affected talk groups, anticipated time/duration of use, changes to the previously distributed communications plan (F-205), participating agencies, etc. Interoperability Channels - For pre-planned events, COMLs/PSAPs should be cognizant of the potential need for emergency/unplanned events that might also need specific interoperability channels. (Recalling that default assignment(s) for the interoperability talk groups start from the top (Law Enforcement on 2, 3, 4) and/or bottom Section 9 Radio Interoperability Procedure Page 4 Revised: 7/27/16

5 (Fire/EMS on 15, 14, 13), of a radio systems interoperability channel bank). Even though 14 or more interoperability talk groups will be available throughout each of the regional radio systems, not all interoperability talk groups should be utilized at a given location, at the same time. Site capacity planning - Users, PSAPs, and system managers are to remain cognizant that some physical tower sites (mostly in the Eastern portions of our counties) are unable to operate at the full capacity of the respective radio systems. While busier, more populated locations may be able to support 20+ simultaneous conversations (on different talk groups), remote locations may only be able to support 5 conversations (different talk groups). It is ESSENTIAL to note that this includes users that are only listening and not talking as they still consume an available resource IO 16 - Emergency Button Use: Because of the very specific nature in how emergencies by public safety officers are handled, only police, fire, and EMS radios are authorized to have the public-safety emergency buttons, and associated functionality, enabled for these talk groups For radios on IO talk groups, Emergency button activation will cause the radio to REVERT to a discipline-specific Emergency talk group on channel 16 (KC EM F, KC EM P) It is important to note, that while law enforcement radios and fire/ems radios appear to be the same (specifically, with Channel 16 being displayed as the Emergency talk group), THEY ARE NOT THE SAME TALK GROUP. For example: a law enforcement user on the King County interoperability channel bank Channel 16 (KC EM P), would NOT be able to talk to a fire/ems user on the same channel bank Channel 16 (KC EM F)! The different emergency talk groups are a result of the varied nature in how law enforcement and fire/ems emergencies are handled. If needed, the two emergency talk groups can be patched at the PSAP level. Monitoring: For each of the radio systems in the region, a designated PSAP (and a secondary for King County), is assigned as the primary monitoring agent for interoperability talk group emergency activations. In Snohomish County (SERS), Fire/EMS user emergencies will revert to SNOCOM In Snohomish County (SERS), Law Enforcement users will revert to SNOPAC In King County, Fire/EMS user emergencies will revert to Seattle Fire FAC. NORCOM is secondary for Fire/EMS. Section 9 Radio Interoperability Procedure Page 5 Revised: 7/27/16

6 In King County, Law Enforcement users will revert to Seattle Police Radio. Valley Communications is secondary for Law Enforcement. Port of Seattle Fire/EMS user emergencies will revert to Port of Seattle Dispatch Port of Seattle Law Enforcement users will revert to Port of Seattle Dispatch In Pierce County, Fire/EMS users emergencies will revert to Tacoma Fire Dispatch In Pierce County, Law Enforcement users will revert to South Sound Dispatch While these PSAPs are identified as the primary recipients of Emergency button activations on the interoperability talk groups, all PSAPs have the ability to monitor their respective EMER talk groups. When a particular PSAP is hosting a regional activity, they will also monitor the regional EMER talk group Unless arrangements have previously been made to transfer Interop- EMER monitoring responsibilities, the primary assigned monitoring PSAP will be the first to respond to EMER activations. This priority accounts for the possibility that an EMER may be coming from users on any other interoperability talk groups. Processing: Because Emergency Button activations on the interoperability channel banks can be received at all PSAPs on a given radio system, and may be initiated from any public safety radio throughout the entire region, it is critical that such activations be received and processed in a consistent manner. This will foster an increased comfort level in all system users, allowing public safety users and dispatchers to focus on assisting with the emergency itself instead of the actual processing Because of the nature of the regional interoperability talk group channels/zones, there is a strong likelihood that units declaring an emergency may not be from the default monitoring PSAPs listed previously. As a result, units may not be registered in the monitoring agency s CAD system and, as a result, the Emergency Button activation may only display a radio system ID number (no unit/user information). At a minimum, if an Emergency Button activation for one of the interoperability channel banks is received at a PSAP, any available/presented information should be immediately recorded (e.g. user s name, radio number, unit name, what agency the radio is assigned to per the master assignment list, etc.) Even if the user does not answer, the accountability system(s) will help find/identify them by their name and unit number. Consideration must also be given for the possibility of multiple Emergency Button activations. Section 9 Radio Interoperability Procedure Page 6 Revised: 7/27/16

7 The radio system Acknowledge step can be completed at any dispatch console Following an Emergency Button activation, the monitoring PSAP shall immediately attempt to contact the user on the interoperability channel bank EMER talk group and confirm if they have an emergency to report. RADIO #3126, (ENGINE 16 or 2B3) CONFIRM YOUR STATUS? RADIO WITH AN EMERGENCY ACTIVATION ON RADIO #123456, CONFIRM YOUR STATUS? At a minimum, and using plain language, the PSAP will try to determine: Who is reporting the emergency? What is/was the last known location of the emergency? What incident is the unit assigned to or part of? What is the nature of the emergency? If an actual emergency has been declared, and the location is known, the default PSAP will broadcast the emergency on the most applicable talk group (known event IO or owner agency s talk group), in an effort to get assistance to that unit as quickly as possible. Include radio # and any other identifiable and/or pertinent information when broadcasting. The applicable owner PSAP will then take ownership for handling the duration of the emergency and will immediately contact the Incident Commander (IC), if applicable If there is no response after repeated attempts, the hosting PSAP for an event the unit is likely to be involved in, or the radio s owner agency, should be notified via a PSAP talk group, phone, etc. All information should be passed on to the event agency or radio owner agency for handling of the activation from that point forward, but then will remain on the EMER talk group until the responsible PSAP can be heard (on the EMER talk group) assuming responsibilities for mitigating the situation The monitoring PSAP for a hosted event shall notify the Incident Commander (IC), on the event IO talk group that an Emergency Button Activation has been received and contact has been unsuccessful. Provide the IC with all available information and restrict traffic on the IO event talk group. Remind the IC that the affected unit is reverted on the IO EMER talk group It is important to note that, depending on the discipline of the user and the discipline of the IC, the IC may not be able to switch their radio to the same EMER talk group as the individual declaring the emergency. (Example: A fire/ems IC will have a different EMER talk group in their radio than an assigned Law Enforcement member who might declare an emergency). They would need a PSAP to patch the two EMER talk groups together If it is determined that no emergency exists, or it was an accidental activation, inform the user to reset their portable radio by turning their radio off and then back on. Section 9 Radio Interoperability Procedure Page 7 Revised: 7/27/16

8 As a reminder, because EMER activations consume trunked radio system resources and because there is only a single EMER talk group available for all channels in a given radio system s interoperability bank, emergency button activations should be cleared as soon as officer/fire fighter safety is assured. 6.0 KING COUNTY CHIEF S DIRECTIVE 6.1 This procedure was adopted by the King County Fire Chiefs as a standard for all fire departments within King County as a countywide standard. Other than numbering this procedure to match the local system, it shall be placed in the located departments SOG/SOP verbatim, to ensure countywide standardization. Changes to this procedure must be with the concurrence of the King County Fire Chiefs Association. Section 9 Radio Interoperability Procedure Page 8 Revised: 7/27/16