DANE COUNTY FIRE/EMS SERVICES RADIO COMMUNICATIONS PROTOCOLS. Edition 8

Similar documents
Title- RADIO PROTOCOL FOR EMERGENCY INCIDENTS CLASSIFICATION POLICY STATEMENT

Lincoln County Fire and Rescue Association Standard Operating Guideline (SOG)

VOLUSIA COUNTY SHERIFF S OFFICE FIRE/EMS COMMUNICATIONS CENTER

STANDARD OPERATING PROCEDURES COMMUNICATIONS SYSTEM b RADIO DISCIPLINE AND TERMINOLOGY EFFECTIVE: JULY 2011

11. INCIDENT COMMUNICATIONS/GENERAL OPERATING GUIDELINES

KING COUNTY FIRE MODEL PROCEDURE Section 15 Abandon / Withdraw

800 System Procedures

EFFECTIVE DATE: 01/01/2002 REFERENCES: RELATED DIRECTIVES: RESCINDS:

Mosier Fire & Emergency Services Standard Operating Procedure Communications

Rulemaking Hearing Rules of the Tennessee Department of Health Bureau of Health Licensure and Regulation Division of Emergency Medical Services

Standard Operating Procedure Ottawa Fire Services. Radio Communications Procedures- Revised

25 Rapid Intervention Team

II. Description of UHF Fire and EMS Radio System

DELAWARE COUNTY PUBLIC WARNING SYSTEM

BUTLER COUNTY FIRE CHIEF S ASSOCIATION Standard Operation Guideline

RESPONSE TAPE 2 SIDE A, 10:22-11:10 a.m.

STANDARD OPERATING GUIDELINES FOR MAYDAY OPERATIONS

Best Operating Practice

R E V I S E D 1. CALL TO ORDER 2. ACTION ITEMS. 2a. Approval of Minutes February 25, 2016* 2b. Draft Fire Communications Plan*

San Mateo County Fire Service POLICIES AND STANDARDS MANUAL

RESPONSE TAPE 1 SIDE B, 9:31-10:22 a.m.

REGIONAL MCI COMMUNICATIONS AND EXERCISE (DRILL) PLAN

Policies, Procedures and Guidelines. Section: Operations Page: 1 of 10 Section No: 2.8 Date: November 1, 2014

Regional MCI Communications and Exercise (Drill) Plan

Example: COUNTY: Engine 225, County, are you requesting to 2nd alarm? UNIT: Engine 225, Affirmative.

SULLIVAN COUNTY. Mayday Policy & Procedure Emergency Evacuation Policy & Procedure

1. STANDARD OPERATING PROCEDURES 1.1 MISSION STATEMENT

Communications Committee Meeting

SAN FRANCISCO EMERGENCY MEDICAL SERVICES AGENCY EMS COMMUNICATIONS EQUIPMENT AND PROCEDURES

BUTLER COUNTY FIRE CHIEF S ASSOCIATION Standard Operation Guideline

State Plan for Mutual Aid Communications Frequencies. Annex K Version 4.4

SAN DIEGO COUNTY MUTUAL AID RADIO PLAN

COMMUNICATIONS MANUAL CHANGE LOG

LOUDON COUNTY ARES EMERGENCY OPERATIONS PLAN

Appendix D Warning System Guidelines. Draft

KING COUNTY FIRE RESOURCE PLAN Section 9 King County Radio Interoperability

Writing Guide for Standard Operating Procedures

Allied Radio Matrix for Emergency Response (ARMER) Standards, Protocols, Procedures

References December 11 th, 2013 revised to reflect orange emergency activation button on the UHF Digital Trunked Radio System

ESF 2. Communications

AMATEUR RADIO EMERGENCY SERVICES

OhioHealth Emergency Medical Services Event Medicine

Amateur Radio Emergency Service Standard Operating Guidelines. For Grayson County, Texas

Sullivan County. for use of the Emergency Communications System. Fire Service Policy & Procedures 1 of 6

IFERN / IFERN 2 Radio Base Stations for all Wisconsin MABAS Divisions/Counties

Radio Procedure Manual 2018

EMERGENCY HEALTH SERVICES FEDERATION REGIONAL COMMUNICATIONS MANUAL

MIAMI VALLEY FIRE/EMS ALLIANCE STANDARD OPERATING GUIDELINES. 800 MHz Radio System Operations in Montgomery County

Emergency Support Function 2. Communications. Iowa County Emergency Management Agency

Buchanan County Communications. Public Safety Radio System Radio Regulations and Etiquette

System Overview 10/25/2010

Radio Procedure Manual 2013

COMMUNICATIONS MANUAL CHAPTER 9, ADDENDUM 1 September 30, 2008 BATTALION RECORDER SYSTEM 1. INTRODUCTION

Command Talk Group functions are managed on the Dispatch Talk Group when not assigned.

Chapter 3 Test. Directions: Write the correct letter on the blank before each question.

Presurvey Information Request for Communication/Dispatch Centers

USE OF THE NYC TRANSIT SUBWAY REPEATER SYSTEM

STANDARD RADIO TERMINOLOGY

CENTRAL CALIFORNIA EMERGENCY MEDICAL SERVICES

Chautauqua County Office of Emergency Services. Chautauqua County Interoperable Communications System DISPATCH/RADIO PROTOCOL FIRE - EMS

STANDARD OPERATING GUIDELINE. Rapid Intervention Team

WOOD COUNTY ARES EMERGENCY COMMUNICATIONS PLAN Effective June 3, 2008

Basic IMS A R E S. Amateur Radio Emergency Communications. IMS For Amateur Radio. Self Study Training Course. Amateur Radio Emergency Service

LETTER OF PROMULGATION

2 ESF 2 Communications

COMMUNICATIONS MANUAL CHAPTER 12 January 4, 2011 POST RADIO / CROSS BAND REPEATER TABLE OF CONTENTS 1. INTRODUCTION...1

Doug Joinson de joinson & associates

PALM BEACH COUNTY DEPARTMENT OF PUBLIC SAFETY DIVISION OF EMERGENCY MANAGEMENT STANDARD OPERATING GUIDE COMMUNITY EMERGENCY RESPONSE TEAM

Wyoming s Statewide Public-Safety Interoperable Radio Communications System WyoLink Frequently Asked Questions (FAQ)

The Highland Lakes ARES Amateur Radio Emergency Service Emergency Communications Plan

Law Enforcement Dispatch Summary

Firefighter Awareness. and. Survival Techniques

9/10/2012. Chapter 18. Learning Objectives. Learning Objectives (Cont d) Communication

Marin Emergency Radio Authority Mutual Aid and Communications Plan. Table of Contents Date: 04/03/2013 Version: E.B. 5/8/13 Item C-1a Chapters:

The Medical Examiner s Process

WELLINGTON RADIO CLUB

Emergency Alert System

GREENE COUNTY DEPARTMENT OF EMERGENCY SERVICES. Standard Fire Radio Procedures. Director John P. Farrell Jr. Deputy Director Randy Ormerod

EMERGENCY SUPPORT FUNCTION #2 COMMUNICATIONS

Fire Service Radio Communications: The Use of Dispatch & Working Channel Communications

A legacy of regional cooperation, a commitment to a vibrant future. National Capital Region Communications Interoperability Group Procedures

RECOMMENDATION ITU-R M.541-8*

Sample Slip and Fall Prevention Program

Louisiana ARES Simulated Emergency Test (Revision 1) Cold Front With Tornado Activity 2018 Plan October 20, 2018, 9 AM to 12 Noon CDT.

RADI & PROG POLICY. Page 1 of 7

GAMA Emergency Alerting System Activation Procedures. Ascension Parish, Louisiana February 8, 2008

Emergency Response/Recovery Plan

CONOPS Interoperability. Maine Emergency Management Agency & Maine Department of Public Safety State of Maine 7/6/2015

Use of Tactical Callsigns in ARES. W5UHQ Assistant EC Licking County March 31, 2010 Updated 1 April, 2010

CUMBERLAND COUNTYAMATEUR RADIO EMERGENCY SERVICE/RADIO AMATEUR CIVIL EMERGENCY SERVICE

Technical Services Talk

ASTRO 25 MISSION CRITICAL DATA YOUR LIFELINE FOR SUCCESSFUL MISSIONS

Course Firefighter II. Unit IX Emergency Communications

Training that is standardized and supports the effective operations of NIIMS.

General Communications Rules of Use. VHF and UHF Conventional Interoperable Channels

Procedure Mining Two Way Radio Usage (Surface)

TOOLBOX TALKS. Active Shooter Awareness. A Quality Service Contractors Publication for Members July What is an Active Shooter?

ESF 2. Communications

ANNEX B COMMUNICATIONS

HABITAT FOR HUMANITY OF EVANSVILLE SWEAT EQUITY POLICY

Transcription:

DANE COUNTY FIRE/EMS SERVICES RADIO COMMUNICATIONS PROTOCOLS Edition 8 Dane County Fire Chief's Association Dane County EMS Association Dane County Public Safety Communications Center Board Approved: August, 1993 Revised: April, 1996 June, 1997 March, 1998 June, 2003 April, 2006 February, 2009 July, 2012

DANE COUNTY FIRE/EMS SERVICES RADIO COMMUNICATIONS PROTOCOLS 1. Introduction 2. Fire / EMS Radio Communications Protocols 3. Radio Channels A. Radio Channel Names and Descriptions B. Channel Use Guide C. Channel Assignment Guide - Communicator's Reference APPENDICES I. Plain Language Guide II. Apparatus Identifiers III. First-In Reports IV. Command Messages V. Communications Techniques VI. Communications Center Phone Numbers

DANE COUNTY FIRE/EMS SERVICES RADIO COMMUNICATIONS PROTOCOLS 1. INTRODUCTION These radio communications protocols were originally developed under the direction and guidance of the Dane County Fire Chief's Association and the Dane County Public Safety Communications Center with the following goals in mind: Establish a guide to facilitate uniform countywide fire service radio communications, Facilitate effective and safe emergency operations by establishing standards for radio channel utilization, Improve fireground safety. Due to the close working relationship between the fire and emergency medical services within Dane County, it was recognized that everyone involved would be better served by having a consolidated and coordinated radio communications protocol. A quality improvement (QI) team made up of representatives from City of Madison and Dane County fire and EMS services and the Dane County Public Safety Communications Center worked throughout 1997 to bring about these consolidated protocols. 1

EFFECTIVE / REVISION DATES Upon recommendation of the Dane County Fire Chief's Association and approval of the Dane County Public Safety Communications Center Board, this plan is implemented on August 1, 1993. Following a comprehensive review by a Quality Improvement Team made up of fire service and Communications Center representatives, and upon recommendation of the Dane County Fire Chief's Association and approval of the Dane County Public Safety Communications Center Board of proposed modifications, this plan is revised April 1, 1996. Through a biannual feedback and review process put in place as part of the Quality Improvement process, and upon recommendation of the Dane County Fire Chief's Association and approval of the Dane County Public Safety Communications Center Board, this plan is revised as of June, 1997. As a result of a quality improvement (QI) initiative of the Dane County Fire Chief s Association, Dane County EMS Association, and the Dane County Public Safety Communications Center to consolidate the Dane County EMS Association Radio Communications Manual into one combined Fire/EMS protocol, and upon recommendation to and approval of the Dane County Public Safety Communications Center Board, this plan is revised as of March, 1998. Through a feedback and review process put in place as part of the Quality Improvement process, and upon recommendation of the Dane County Fire Chief's Association and the Dane County EMS Association, and upon approval of the Dane County Public Safety Communications Center Board, this plan is revised as of June, 2003. Through a feedback and review process put in place as part of the Quality Improvement process, and upon recommendation of the Dane County Fire Chief's Association and the Dane County EMS Association, and upon approval of the Dane County Public Safety Communications Center Board, this plan is revised as of April, 2006. Through a feedback and review process put in place as part of the Quality Improvement process, and upon recommendation of the Dane County Fire Chief's Association and the Dane County EMS Association, and upon approval of the Dane County Public Safety Communications Center Board, this plan is revised as of January, 2009. Through a feedback and review process put in place as part of the Quality Improvement process, and upon recommendation of the Dane County Fire Chief's Association and the Dane County EMS Association, and upon approval of the Dane County Public Safety Communications Center Board, this plan is revised as of July, 2012 2

2. FIRE / EMS COMMUNICATIONS PROTOCOLS 2A-1 DISPATCH DESIGNATION LOCAL ALARMS The term COMM CENTER will be used when referring to the dispatch center operated by the Dane County Public Safety Communications Department. 2A-2 DISPATCH DESIGNATION MABAS ALARM LEVELS The term MABAS DIVISION 115 will be used when referring to the dispatch center (Dane County Public Safety Communications Department) whenever an incident escalates to a MABAS alarm level (Box Alarm or greater). 2B MAKING RADIO CONTACT BETWEEN UNITS When initiating a radio transmission to another unit or base, the following three guidelines are recommended: 1. Transmit the name of the unit/base being called FIRST, and then give your unit designation. (This is intended to capture the attention of the unit being called first) 2. When you call a unit/base, WAIT FOR THEM TO ACKNOWLEDGE YOU before you transmit your message. (This will ensure they are ready to listen to you before you give your information). 3. When receiving a message, always REPEAT a summary of the key points within the message to confirm you have interpreted the intent correctly. 2C-1 LOCAL BASE STATIONS - FIRE / EMS STATIONS Base stations operated by a fire department and/or EMS district will be designated by the COMMUNITY NAME, followed by STATION. The use of a number following the word STATION is optional based on community need. Examples: "Blooming Grove Fire Station" "Fitchburg Fire Station 2" Middleton EMS Station 3

2C-2 LOCAL BASE STATIONS - LAW ENFORCEMENT OR OTHER Base stations operated by local entities other than at a fire or EMS station will be designated by stating the COMMUNITY NAME followed by the TYPE OF AGENCY. Examples: "Sun Prairie Police" "Dane County Emergency Management" 2C-3-A GENERIC CALL - EMS Sometimes there is a need for a generic way to call for any unit from a specific EMS Service. To raise any unit from a specific service, use the designation SERVICE NAME followed by the word EMS. Examples: "Waunakee EMS" "Belleville EMS" When someone is attempting to call a service using the generic call message, the following guidelines should be used by the called EMS service to determine who should answer: If responding to an emergency incident, the crew chief should answer. If there is no emergency incident in progress: * The EMS service STATION if staffed, * The on-duty CREW CHIEF, * A SERVICE MEMBER if a radio is available. 4

2C-3-B GENERIC CALL - FIRE Sometimes there is a need for a generic way to call for any unit from a specific department. To raise any unit from a specific department, use the designation COMMUNITY NAME followed by the word FIRE. Examples: "Waunakee Fire" "Belleville Fire" When someone is attempting to call a department using the generic call message, the following guidelines should be used by the called department to determine who should answer: If responding to an emergency incident, the "lead" unit, or the unit who will establish command once on the scene. If command has been established, COMMAND should answer. If there is no emergency incident in progress: * The community FIRE STATION if staffed, * A DEPARTMENT OFFICER, * A DEPARTMENT MEMBER if a radio is available. 5

2D UNIT IDENTIFICATION Units will use plain language identification when conducting radio communications. Plain language identification will include: Community Name* - Unit Type - Unit Number Examples: "Belleville Rescue 48 "Town of Madison Ladder 9" "Maple Bluff Engine 2" "Verona Tender 7" APPENDIX II contains a complete list of approved "unit type" identifiers. * NOTE: Units operated by the City of Madison Fire Department are not required to use the community name when: - Operating on their assigned 800 MHz TRS TALK GROUP, and - On incidents involving response solely by City of Madison units, and - And when no radio channel patch is active with County (VHF/high-band) channels. Should an incident involve both City of Madison and non-city of Madison units operating on a single or patched radio channel(s), City of Madison units shall be identified using the community name "Madison. In cases where one vehicle such as a pick-up or Suburban is used to pull a trailer such as a Decon trailer (CAD designation D ), HIT trailer (CAD designation H ), Mass Casualty trailer (CAD designation MC ), or Utility trailer (CAD designation U ), the pull vehicle shall identify itself on the radio by the designation of the trailer (i.e. - if DeForest Car 1 is used to pull a Dane County Mass Casualty trailer, its radio designation for the period of time it is pulling the trailer is DeForest Mass Casualty 1, not Deforest Car 1 ). The operator of the pulling vehicle should notify the COMM CENTER to place the pulling vehicle OUT OF SERVICE or to add the pulling vehicle designation (i.e. - DeForest Car 1) to the assignment. 6

2E Index: ALERT MESSAGES 2E-1A Dispatch Script - Information Messages 2E-1B Dispatch Script - Initial (Still/Full Still) Alarm Pre-Alerting Message (Future) 2E-1C Dispatch Script - Initial (Still/Full Still) Alarm Alert Message 2E-1D Dispatch Script - Special Call Alert Message 2E-1E Dispatch Script - Subsequent/MABAS Alarm Alert Message 2E-1F Alerting Mutual Aid Fire/EMS Units on an Initial Alarm Event 2E-1-A DISPATCH SCRIPT INFORMATION MESSAGES INFORMATION messages for fire and/or EMS units will follow a standard sequence, including the following information: - Start the dispatch message with: INFORMATION ONLY FOR (insert the Department/District/Entity/Group name that will be receiving the message) - Insert Informational Message - End with: Time of information message, xx:xx The INFORMATION message will automatically be re-transmitted a second time by the paging system, so dispatchers do not need to repeat information when they transmit the initial INFORMATION message. Examples: - INFORMATION ONLY for Belleville Fire, Belleville Brush 1 will be out of service for maintenance until further notice; time of information message 14:21 - INFORMATION ONLY for all Dane County Fire and EMS Units, Dane County Channel E-Edward is out of service, and all EMS calls will be assigned to C- Charlie until further notice; time of information message 23:16 2E-1-B DISPATCH SCRIPT INITIAL (STILL/FULL STILL) ALARM PRE- ALERTING MESSAGE (Future enhancement to the protocols) 7

2E-1-C DISPATCH SCRIPT INITIAL (STILL/FULL STILL) ALARM ALERT MESSAGE FIRST (STILL/FULL STILL) ALARM ALERT messages directed to fire and/or EMS units will follow a standard sequence, including all of the following information: - Start the dispatch message with the word ATTENTION - Identification of responding units (Department/District name if specific units are not recommended by CAD), including those fire/ems units that are dispatched by other dispatch centers or on other paging channels. - Location of incident (municipality, common place name (if available), address, apartment number or floor, etc.) - Both cross streets (if available) - Nature of the incident (EMD/EFD alpha acuity designator only, and a brief description of incident type, including the priority dispatch protocol chief complaint and determinant descriptor) - Channel assignment - Time of dispatch The FIRST (STILL/FULL STILL) ALARM ALERT message will automatically be re-transmitted a second time by the paging system, so dispatchers do not need to repeat information such as the address or nature of the incident when they transmit the original FIRST (STILL/FULL STILL) ALARM ALERT message. Examples: - Attention Brooklyn Rescue 42; in the Village of Brooklyn at the intersection of Highway 92 and Highway 14; an alpha response, for a traumatic injury, a leg injury; a channel E-EDWARD assignment; time 13:42 - Attention Shorewood Hills Engine 1, Engine 2, Squad 5, Car 1 and Rescue 58; in the Village of Shorewood Hills at 1008 Shorewood Boulevard, cross street Harvard Road; a delta response, for a reported structure fire in a commercial structure; a channel B-BAKER assignment; time 22:41 - Attention Stoughton Fire; in the Town of Dunn at Hwy 51 and Quam Drive; a bravo response; for a vehicle fire; a channel D-DAVID assignment; time 03:51 - Attention Engine 6; 835 W Badger Road, cross streets Perry and Cypress; a Charlie response, for a fire alarm in a commercial structure; an ADMIN channel assignment; time 09:31** ** NOTE: Units operated by the City of Madison Fire Department are not required to use the community name under certain conditions per protocol section 2D. CONTINUED 8

Specifics concerning the FIRST (STILL/FULL STILL) ALARM ALERT MESSAGE include: - Identification of responding department or units >> For departments/units that are selectively dispatched, do not repeat the "community name" before every unit when all units being alerted are from the same department. The "community name" is only required before each unit if units from multiple departments are being alerted at the same time. When units from multiple agencies are being sent to an incident and are dispatched on separate frequencies or by other dispatch centers, all units assigned should be identified in the ALERT MESSAGE. - Location of incident (municipality, address, common place name, apartment, floor, etc.) >> All pertinent information should be given on the ALERT MESSAGE to assist departments where members respond directly to the scene. Pertinent information includes the municipality, a common place name, address, floor or apartment if available. - Cross street >> Only the cross street name (James Street, Adams Court, Smith Road) should be given. Hundred block information should not be included unless asked for by a responding unit. In cases where the CAD provides both cross streets, both should be given. - Nature of the incident >> Information provided should be as short but descriptive as possible. The EMD/EFD alpha acuity level designator, chief complaint, and determinant descriptor will be given for EMD/EFD coded incidents. - Radio channel to operate on >> It is critical the channel assignment be given during the ALERT MESSAGE. If a channel assignment is not given during the ALERT MESSAGE, or if the channel assignment is changed after the ALERT MESSAGE has already been given, the department/unit must be re-alerted. Most County department members will ONLY hear information put out over their alert pagers. - Time of dispatch >> Stated as "time, ##:##" 9

2E-1-D DISPATCH SCRIPT SPECIAL CALL ALERT MESSAGE SPECIAL CALL ALERT messages for fire and/or EMS units will follow a standard sequence, including all of the following information: - Start the dispatch message with the word: ATTENTION - Identification of responding units (or Department/District name if specific units are not recommended by CAD), including those fire/ems units that are dispatched by other dispatch centers or on other paging channels. - A special call from the (requesting Agency) for... - Location of incident (municipality, common place name (if available), address, apartment number or floor, etc.) - Both cross streets (if available) - Nature of the incident (EMD/EFD alpha acuity designator only, and a brief description of incident type, including the priority dispatch protocol chief complaint and determinant descriptor) - Channel assignment - Time of dispatch The SPECIAL CALL ALERT message will automatically be re-transmitted a second time by the paging system, so dispatchers do not need to repeat information such as the address or nature of the incident when they transmit the initial SPECIAL CALL ALERT message. Examples: - ATTENTION Cambridge Rescue 92; a SPECIAL CALL from Cambridge Rescue 94 in the Town of Oakland at the intersection of Highway 12 and Ehrke Road; a request for a second Rescue at the scene of a vehicle crash, a channel B- BAKER assignment; time 14:32 - ATTENTION Mount Horeb Engine 1; a SPECIAL CALL from Verona Fire in the Town of Verona at 2842 Timber Lane, cross street of County Highway PB; a request for a single engine at the scene of a structure fire; acknowledge on A- ADAM; time 18:31 - ATTENTION Fitchburg Fire; a SPECIAL CALL from Fitchburg Car 1; a request for Battalions 1 and 2 to respond to your respective stations to staff reserve apparatus; acknowledge on A-ADAM; time 07:29 10

2E-1-E DISPATCH SCRIPT - SUBSEQUENT/MABAS BOX ALARM ALERT MESSAGE (ONLY FOR USE ON IFERN BROADCASTS) Dane County shall use the MABAS-Wisconsin Dispatch Script as defined in MABAS Wisconsin Policies, Procedures and Guidelines Index Number B-01-01: The MABAS Box Alarm ALERT MESSAGE will include the following information: THIS IS MABAS DIVISION 115 TO ALL LOCALS. THE (insert the name of the stricken Department/District/Entity) IS REQUESTING MABAS BOX NUMBER XX-XX TO THE LEVEL, (MABAS Box, MABAS 2nd, etc.) FOR A, (Incident Type e.g. Structure Fire, Mass Casualty, etc.) AT, (Incident Location) (REPEAT ONCE) THE FOLLOWING DEPARTMENTS ARE DUE TO RESPOND TO THE SCENE: (Read list of Departments/Equipment/Personnel/Destinations from Box Alarm Card) THE FOLLOWING DEPARTMENTS ARE DUE FOR CHANGE OF QUARTERS: (Read list of Departments/Equipment/Personnel/Destinations from Box Alarm Card) STAGING WILL BE AT, (Staging Area Location) OPERATING ON FREQUENCY, (MABAS FG Red, White, or Blue, etc.) ALL RESPONDING UNITS SWITCH TO AND ACKNOWLEDGE ON IFERN Example: This is MABAS Division 115 to all locals, the City of Fitchburg Fire Department is requesting MABAS Box Number 20-17 to the MABAS 2 nd Alarm level for a structure fire at 5040 Caddis Bend in the City of Fitchburg. The following units are due to respond to the scene: Blooming Grove Engine 1, McFarland Engine 3, Maple Bluff Engine 1, City of Madison Ladder 8, Middleton Ladder 2, Waunakee Squad 5, and Cottage Grove Car 1. The following units are due for a change of quarters: Deerfield Engine 1 to Blooming Grove and Mount Horeb Engine 4 to Verona. Staging will be at the Nevin State Fish Hatchery at 3911 Fish Hatchery Road operating on the MABAS Fireground Blue channel. All responding units will switch to and acknowledge on IFERN 1; time 21:14 11

2E-1-F ALERTING MUTUAL AID FIRE/EMS UNITS ON AN INITIAL ALARM EVENT The jurisdictional fire department shall be notified of all fire incidents occurring or having occurred in its area of responsibility (fire incidents are those which have been determined as such after being categorized by the Emergency Fire Dispatch protocol). Whenever a mutual aid Fire or EMS unit is alerted to respond into another jurisdiction because the primary (1 st due) Fire/EMS unit is not available (i.e. - the 1 st due Fire department or EMS unit is already assigned to another incident, etc.), the COMM CENTER will ALERT both the responding and the jurisdictional Fire or EMS units. This ensures that any first responder or other available personnel that might be in the jurisdiction are aware of the incident and may respond per their local department or service protocols. Requests from an EMS unit to have a Fire department paged in place of, or in addition to the EMS agency having jurisdiction shall be honored, which is considered to be compliant with this section of the protocol. It shall be the responsibility of the alerted agency to notify the COMM CENTER if they are unable to respond due to certification levels or other limitations. 2E-2-A ALERT MESSAGES DAILY TESTS The COMM CENTER will conduct daily tests of all fire and EMS agency alerting systems per the following schedule: City of Madison Fire/EMS agencies at 7:00 a.m. and 5:00 p.m. daily County Fire/EMS agencies at 6:00 p.m. daily The test will be conducted in accordance with COMM CENTER procedures. This test is designed will allow departments/stations to determine if their alerting systems are working properly. If a department/station alerting system does not receive a TEST ALERT PAGE, that member/station is to contact their department chief/director, or designee. The department chief/director, or designee, will evaluate any missed page reports, and determine if a TEST ALERT PAGE was done or not. If it is determined that there was no TEST ALERT PAGE, or there is evidence of a larger problem, that person shall contact the on-duty COMM CENTER supervisor directly (not the fire/ems dispatch position), in order to determine if there is a radio system problem. When a HEAVY TRAFFIC condition exists during the time period that TESTS are to be done, the COMM CENTER may elect to not conduct the designated tests. 12

2E-2-B ALERT MESSAGES MONTHLY MABAS WISCONSIN IFERN TESTS The COMM CENTER will conduct a monthly IFERN Alert test in accordance with MABAS-Wisconsin Policies, Procedures and Guidelines - Index Number C-01-04.02 (located at http://www.mabaswisconsin.org/pdf-files/051409-policies-procedures- Guidelines-Indexed.pdf) 2E-2-C ALERT MESSAGES MONTHLY ALL-COUNTY ALERT TONE TESTS The COMM CENTER will conduct the monthly ALL-COUNTY ALERT TONE test in conjunction with the monthly outdoor warning siren test on the first Wednesday of each month at 12 noon. The test will be conducted in accordance with COMM CENTER procedures. This test is designed will allow departments/stations to determine if their ALL-COUNTY alerting systems are working properly. 2F ACKNOWLEDGMENTS 2F-1 ACKNOWLEDGMENT BY RESPONDING DEPARTMENTS, STATIONS OR UNITS The department(s), station(s) or unit(s) which has been alerted shall acknowledge the ALERT message on the assigned radio channel within two minutes. This acknowledgment will include the following: - Identification of unit or department - Restatement of incident location - Restatement of incident type It is recommended that a representative from the alerted agency carry out their acknowledgement via radio, but in rare cases, if radio communication is not possible, it is acceptable for the representative to acknowledge the call by calling 9-1-1. The time in which the ALERT message was acknowledged will be recorded by the COMM CENTER. EMS units that acknowledge the ALERT message, but are not at the EMS station are encouraged to advise the COMM CENTER of the circumstances (i.e. - an EMT responding to the station from work). CONTINUED 13

NOTE: Acknowledgment of the alert message by a department, station or unit other than the City of Madison does not necessarily indicate that a "response" has begun. 2F-2 FAILURE OF A DEPARTMENT, STATION, OR UNIT TO ACKNOWLEDGE THE ALERT MESSAGE WITHIN TWO MINUTES In the event a department, station or unit does not acknowledge the ALERT MESSAGE within two minutes, the COMM CENTER will re-broadcast the ALERT MESSAGE. The communicator will begin the second alert message with "Attention (Department/Station/ Unit) second page"; and continue on with the balance of the ALERT MESSAGE. The communicator will end the ALERT MESSAGE with; "time of second page, ##:##. In the event a department, station or unit does not acknowledge the ALERT MESSAGE within two additional minutes (four minutes total from original ALERT MESSAGE), the COMM CENTER will alert an appropriate mutual aid response. Once mutual aid has been alerted, the COMM CENTER will: 1. Re-broadcast a third ALERT MESSAGE to the original department, station or unit, and 2. Notify the on-duty COMM CENTER supervisor who will attempt to make telephone contact with a representative of the original department, station or unit (utilizing the County Resource Manual, starting with a duty or chief officer, or EMS District Director). 14

2F-3 FAILURE OF A DEPARTMENT, STATION OR UNIT TO BEGIN A RESPONSE WITHIN SIX MINUTES In the event a department, station or unit fails to begin a response within six minutes, the COMM CENTER will: 1. Make radio contact with the unit that acknowledged the ALERT MESSAGE. 2. Make a notification to the agency advising them that it has been six minutes since the initial page, and if the unit is not enroute/responding within eight minutes, mutual aid will be sent. 3. If the primary response unit (EMS unit or first fire unit) is not responding at the eight minute mark, the communicator will then proceed with alerting appropriate mutual aid resources after eight minutes from the time of the original ALERT MESSAGE has elapsed. In cases where multiple units from the same department or station have been alerted, the communicator shall make a best effort attempt to monitor the progress of all units assigned to the incident. The communicator shall notify the Incident Commander/first responding unit whenever any subsequent units have not started a response within the eight minute time frame. 15

2G RESPONSE MESSAGE (Not required for City of Madison Units) When units assigned to an incident begin their response, each unit shall make contact with the COMM CENTER, wait for acknowledgment, and then broadcast the following message: - Identification of unit - Indication unit is RESPONDING/ENROUTE (if a unit is responding or enroute in non-emergency mode, include that status information in the message) - Restatement of incident location Example: (FIELD UNIT) "COMM CENTER from Dane Engine 1" (COMM CENTER) "Dane Engine 1" (FIELD UNIT) "Dane Engine 1, responding to 401 Main Street for a possible car fire. (COMM CENTER) "Dane Engine 1 responding. Anytime a unit is responding as the only fire or EMS unit to an incident, and that unit is equipped with an MDC, that unit may change its status using the MDC. A radio message to the COMM CENTER is not required when the MDC is used. When more than one fire or EMS unit is responding to an incident, a radio message is still required for the benefit of other field units. The MDC may still be used to change the unit s status. Units changing their status by MDC should be aware that the COMM CENTER communicator is not automatically made aware of the status change and that there is always a possibility that the COMM CENTER CAD may not accept the update. Each unit shall be acknowledged by the COMM CENTER, and the CAD shall be updated by the COMM CENTER unless the unit is utilizing a MDC and has updated their own status. Once the first unit from a fire department or EMS service begins their response, the COMM CENTER shall provide any further information pertinent to the situation that was not transmitted with the ALERT message. In addition, it is important to caution responding units about other activity in the area of their incident such as law enforcement action, imminent hazards, or any other situation where other emergency vehicles may also be responding in the same area. 16

2H COMM CENTER ACKNOWLEDGMENT The COMM CENTER will acknowledge responding units by BRIEFLY RESTATING THEIR TRANSMISSION. Examples: (FIELD UNIT) "COMM CENTER from Mazo Engine 3" (COMM CENTER) "Mazo Engine 3" (FIELD UNIT) "Mazo Engine 3 is responding, County Y at Hendel Street for a grass fire" (COMM CENTER) "Mazo Engine 3 responding" (FIELD UNIT) COMM CENTER from Shorewood Rescue 58 (COMM CENTER) Shorewood Rescue 58 (FIELD UNIT) Shorewood Rescue 58 is responding to Marshall Court for reported chest pains (COMM CENTER) Shorewood Rescue 58 responding The COMM CENTER will use this same protocol when acknowledging all response, on-location, returning, and in-quarters transmissions, except for rebroadcasts of the FIRST-IN REPORT which is described in protocol section 2I. 17

2I FIRST IN REPORTS 2I-1-A FIRST UNIT TO ARRIVE ON SCENE - EMS INCIDENTS First-in reports are not required on EMS responses involving a single ill or injured person. This does not apply to any type of traffic or transportation related incidents. If the situation is found to be greater than a single patient incident, a FIRST IN REPORT as described in protocol section 2I-1-B shall be given. Anytime a unit is responding as the only fire or EMS unit to an incident, and that unit is equipped with an MDC, that unit may change its status using the MDC. A radio message to the COMM CENTER is not required when the MDC is used. When more than one fire or EMS unit is responding to an incident, a radio message is still required for the benefit of other field units. The MDC may still be used to change the unit s status. Units changing their status by MDC should be aware that the COMM CENTER communicator is not automatically made aware of the status change and that there is always a possibility that the COMM CENTER CAD may not accept the update. 18

2I-1-B FIRST UNIT TO ARRIVE ON SCENE - FIRE / JOINT FIRE AND EMS INCIDENTS The first arriving unit shall report ON LOCATION along with a brief description of the situation found (FIRST IN REPORT). The time at which the first assigned unit reports "ON LOCATION" will be acknowledged and recorded by the COMM CENTER. The COMM CENTER will rebroadcast the FIRST IN REPORT on the assigned radio channel, and note the designation of the unit in command in the CAD. The FIRST IN REPORT will include the following: - Identification of unit providing the FIRST IN REPORT - Indication of ON LOCATION Status - Description of the scene - Description of conditions observed - Designation of unit that will establish Incident COMMAND (NOTE: The first arriving unit may indicate that they will provide the rest of the FIRST IN REPORT after completing additional investigation or a 360 size-up) - The initial action being taken by that unit - Action(s) to be taken by subsequent arriving unit(s) Refer to APPENDIX III for examples of FIRST IN REPORT elements. If the first unit to arrive on the scene does not broadcast a FIRST IN REPORT, or leaves out important information like identification of the unit that will be in COMMAND, the COMM CENTER should request a FIRST IN REPORT or the appropriate missing information. Examples: "Fitchburg Engine 2 from COMM CENTER" "Fitchburg Engine 2" "Fitchburg Engine 2, can you provide a FIRST IN REPORT" Command and subsequent responding units should expect the COMM CENTER to rebroadcast the FIRST IN REPORT immediately after it is provided by the first in unit, so units should hold any further transmissions to provide the COMM CENTER enough time to complete the rebroadcast of the FIRST IN REPORT. 19

2I-2 SECOND, THIRD, ETC. UNITS TO ARRIVE ON SCENE Units which arrive after the first-arriving unit should transmit an ON LOCATION report which will include the following: - Unit Identification, followed by "ON LOCATION" - If staged, announce staged location. - If assigned to carry out a task, repeat the task. Examples: "Maple Bluff Engine 1 on location, staged at Oxford and Sherman" "(Madison) Ladder 8 on location, Level one staging in front of Walgreens" "Stoughton Ladder 1 on location, taking the front of the building and laddering the roof" Town of Madison Medic 66 on location, staged north NOTE: It is strongly recommended that units resist such additional comments as, awaiting assignment, or Command, where would you like us, etc. It should be assumed that COMMAND will provide you an assignment or specific directions where to position when appropriate. The COMM CENTER shall acknowledge the arrival of 2nd, 3rd, etc. arriving units; and the CAD shall be updated by the COMM CENTER unless the unit is utilizing an MDC and has updated their own status. The acknowledgment shall follow the format outlined in protocol section 2H. If after a reasonable amount of time the unit believes COMMAND may have missed their ON LOCATION report, the unit should contact COMMAND to confirm that the Incident Commander is aware that they are on the scene. 20

2J-1 UNIT STATUS UPDATES In accordance with other applicable protocol sections, departments/units are responsible for updating the COMM CENTER with the following status changes: - Acknowledgement of ALERT MESSAGE (only one acknowledgement message per station or agency is necessary, instead of each separate assigned unit) - Each unit responding/en route - Each subsequent responding unit that is cancelled while responding - Each unit arriving on scene - EMS Incidents Patient contact made (by Rescue or Medic unit personnel) - EMS Incidents CPR/CCR initiated (by any responder) - EMS Incidents first shock delivered (by any responder) - Each Rescue or Medic unit transporting a patient - Each Rescue or Medic unit arriving at a transport destination - Each unit leaving the incident scene, and whether that unit is in service or out of service - Each unit arriving back in quarters - Changes in manner of notifications (unit cannot be reached by pager, but by radio or phone instead; or unit is no longer on the radio and available by phone or pager) - Units out of territory or district - Units in training, or performing some other task, that may delay their response - Units going on duty or off duty - Rescue or Medic units changing from one level of service to another (i.e. - BLS to ALS) - Units out of service for some other reason not listed above 21

2J-2 INCIDENT TIMING BENCHMARKS The Communicator shall provide INCIDENT TIMING BENCHMARKS in accordance with MABAS Wisconsin Communications Protocol B-03-01 on both MABAS and non- MABAS incidents, such as structure fires, brush fires, hazardous materials, transportation (crash), and entrapment incidents (i.e. - any incident assigned to a dedicated TACTICAL channel). 1. The COMM CENTER should give the Incident Commander Incident Timing Benchmarks at 10, 20, and 30 minutes after the arrival of the first emergency vehicle on scene. Timing benchmarks shall continue every 30 minutes thereafter, until the Incident Commander states that the incident is under control, or at such time that the Incident Commander deems that the benchmarks are no longer needed 2. The Incident Commander should provide the COMM CENTER with a progress report at each of the Incident Timing Benchmarks 3. When an incident progresses to a MABAS Box Alarm level, the status of the Incident Timing Benchmarks shall be relayed to the appropriate MABAS Division Dispatch Center that will be handling the Box Alarm communications. 22

2K PRINCIPLES FOR USE AND ASSIGNMENT OF RADIO CHANNELS 2K-1 "THE GOLDEN RULE" FOR FIREGROUND COMMUNICATIONS If you remember one thing and one thing only, it is this... THE FIREGROUND CHANNEL BELONGS TO INCIDENT COMMAND AND THE ON-SCENE CREWS (Fire and EMS) THEIR COMMUNICATIONS MUST HAVE ABSOLUTE PRIORITY! All other communications must be limited, or managed on another radio channel. 2K-2 ADMINISTRATIVE CHANNELS Each radio system (City of Madison and Dane County) has one radio channel designated as the "Admin Channel", meaning its primary use will be for routine, day-to-day communications. This channel will be available to all Fire / EMS services and allied users. This is the only channel that will be monitored by the COMM CENTER when no active incident is in progress. This channel will be used for all communications with the COMM CENTER when a unit is not currently assigned to an active incident; and such communications may include: - Transmissions from field units to advise the COMM CENTER of their status when the unit is not assigned to a particular incident. Examples include: - Inspecting - Parades or other community relations activities - Training - EMS units on the air and going to a hospital to pick up supplies - Calls to the COMM CENTER for assistance while a unit is in the field - Calls from base stations to the COMM CENTER reporting walk-in or call-in reports of an incident - Units returning from a previous incident CONTINUED 23

The "Admin Channel" will also be used for specific purposes during the following conditions: - During an active incident, when an assigned unit needs assistance with directions, requires assistance with issues not related to active on-scene firefighting or hazard zone activities, or for any reason to prevent interfering with on-scene firefighting or hazard zone communications. This is consistent with the Golden Rule for fireground communications, section 2K-1. - HEAVY TRAFFIC conditions: The "Admin Channel will be used for all Station-to-Station and Stationto-COMM CENTER communications as outlined in protocol section 2R-1 (4). - Subsequent Response Levels to non-mabas Mutual Aid requests: The "Admin Channel" will be used to manage all communications of units on any mutual aid response to a non-mabas incident. - CHANGE OF QUARTERS: Units ALERTED to perform a CHANGE OF QUARTERS to another station or department's territory as part of a non-mabas incident (refer to protocol section 2K-7). Designated "Admin Channels": City of Madison System CITY OF MADISON FIRE ADMIN (TRS TG 56048) County System Channel A-ADAM (158.745) 24

2K-3 INITIAL ALARM ASSIGNMENT COMMUNICATIONS Each radio system (City of Madison and Dane County) has designated radio channels for use during an incident. Active incidents dispatched by the COMM CENTER will be managed on these designated channels. The COMM CENTER will assign initial FIRST (STILL OR FULL STILL) ALARM responding units to a specific channel based on the guidelines contained in protocol section 3B. All communications by initial alarm departments, stations and/or units will be conducted on the assigned radio channel. For incidents in Dane County, where the geographic territory is protected by a department, station and/or unit located outside Dane County (i.e. - Blanchardville or New Glarus in SW Dane County, Edgerton in SE Dane County, Columbus in NE Dane County, or Sauk City in NW Dane County), the responding department may choose to manage the incident on their own county radio channel(s). If they wish to contact the Dane County COMM CENTER, the contact should be made on the Admin Channel (A-ADAM); and if they request a Dane County radio channel for operations, the communicator may assign an available Dane County operations channel for their use. Departments, stations or units must check with the COMM CENTER first (via phone or the designated "Admin Channel") before utilizing any operations channel for any other purpose. All transmissions initiated by field units or stations not currently assigned to a designated operations channel will utilize the designated "Admin Channel" per protocol section 2K-2. Designated operations channels: CITY OF MADISON UNITS COUNTY UNITS 1st Choice City Fireground 3 1 st choice from County Matrix 2nd Choice City Fireground 2 2 nd choice from County Matrix 3rd Choice City CMED 4 3 rd choice from County Matrix 4th Choice City CMED 5 4 th choice from County Matrix 5th Choice City Admin Any available MABAS FG channel 6th Choice MARC-1 Use of TALKAROUND on repeatered operations channels: Operations units may use TALKAROUND on a repeatered operations channel at the Incident Commander's (IC's) discretion. The Incident Commander must remain on the repeater channel (unless conditions or circumstances otherwise dictate). 25

2K-4 JOINT RESPONSE SITUATIONS This protocol section establishes guidelines to be used in situations involving joint EMS-Fire and joint City of Madison and County responses. Basic operating principle: If units responding are part of the initial "intervention group" to a common incident, they must all be communicating on a common (or patched) radio channel(s). Operating scenarios: A. JOINT FIRE/EMS RESPONSES: The following guidelines will be used: Incidents that are primarily fire/hazardous materials related will be managed on a fire operations channel; County: B-BAKER, C-CHARLIE, D-DAVID, or F-FRANK City: FIREGROUND 3 or FIREGROUND 2 Incidents that are primarily EMS related will be managed on the EMS operations channel; County: E-EDWARD City of Madison: CMED 5 or CMED 4 Injury crashes (when a fire department or "pin response" is responding along with EMS) will be managed on a fire operations channel; County: B-BAKER, C-CHARLIE, D-DAVID, or F-FRANK City of Madison: FIREGROUND 3 or FIREGROUND 2 If fire units clear from the scene, leaving just one (1) or two (2) EMS units remaining on scene, the EMS units shall be moved to their normally assigned EMS channel (E- Edward or CMED 5) until the EMS unit(s) transport or return to quarters. CONTINUED 26

B. JOINT (MULTIPLE DEPARTMENT) RESPONSES ON INITIAL ALARM In situations where units from multiple departments respond to the same incident on the initial alarm, all units dispatched as part of the initial response will be assigned to the same operations channel. If during their response a unit needs assistance not related to active on-scene firefighting or hazard zone activities, they should switch to their Admin Channel for such assistance to prevent interfering with on-scene firefighting or hazard zone communications. This is consistent with the Golden Rule for fireground communications outlined in protocol section 2K-1. If the initial response involves units from the City of Madison and County units, other than ALS ambulances, the communicator will automatically establish a patch between the assigned City of Madison channel and the assigned County channel. All ALS ambulances are assumed to have the capability of communicating on both the County and City of Madison radio systems. Therefore, when responding out of their area, they shall be assigned to the radio system of the jurisdiction the call is occurring in (i.e. - Middleton Medic 34 responding into the City of Madison should be assigned to the same MFD TRS TALK GROUP that the responding MFD fire apparatus is assigned to, normally CMED 5). CITY OF MADISON UNITS COUNTY UNITS 1st Choice City Fireground 3 1st Choice from County Matrix 2nd Choice City Fireground 2 2nd Choice from County Matrix 3rd Choice City CMED 4 3rd Choice from County Matrix Last Choice City CMED 5 4th Choice from County Matrix 27

2K-5-A MABAS / SUBSEQUENT ALARM COMMUNICATIONS - FIRE INCIDENTS The initial FIRST (STILL OR FULL STILL) ALARM responding units will be assigned to an appropriate operation channel per protocol section 2K-3. Basic operating principle: The fire operations channel belongs to the Incident Commander and the units already on the fireground. EVERY ATTEMPT must be made to eliminate interference with fireground communications by units not on the scene. Operating scenarios: Initial FIRST (STILL OR FULL STILL) ALARM response units Assigned operations channel A simple request for one (1) or two (2) additional Special Call Rescue or Medic units to the same incident that may need to communicate with EMS units already on scene for patient information and updates while they are responding: Assigned operations channel Any other Special Call units prior to a MABAS Box Alarm: Admin Channel until the units arrive on scene or leave Level II staging. Units assigned from a MABAS Box Alarm or subsequent MABAS alarm levels: IFERN 1 Channel until the units arrive on scene or leave Level II staging. When a MABAS Box Alarm is requested by the Incident Commander, MABAS DIVISION 115 will remind him/her to have the Level II staging officer switch to the IFERN 1 Channel to coordinate incoming units. MABAS alarm (mutual aid) units will be assigned by MABAS DIVISION 115 on the ALERT MESSAGE, and will conduct all communications on the IFERN 1 Channel until they leave Level II staging (if used), or arrive "ON SCENE" if Level II staging is not used. This will include all of the following types of communications: - Acknowledgment of the ALERT MESSAGE. - Requests for clarification of address, directions, types of apparatus needed, number of people needed, etc. - Units RESPONDING to the scene. - Units responding that need directions to the scene. CONTINUED 28

If clarifications are needed from COMMAND, MABAS DIVISION 115 will communicate with the Incident Commander on the operations channel, and relay the information to the MABAS (mutual aid) department on the IFERN 1 Channel. Units, stations or departments alerted on MABAS alarms should direct all communications while responding to MABAS DIVISION 115 or to the LEVEL II STAGING Officer and should not switch to the operations channel prior to arriving in Staging unless specifically requested to do so. This is critical to prevent interference with fireground activities. In cases where a Dane County Department is requested to respond on MABAS Box Alarm or provide mutual aid to a department outside Dane County, during the ALERT MESSAGE the department, station or unit(s) will be assigned to the IFERN 1 Channel if the incident is a MABAS incident; or to their Admin Channel if it is a non-mabas request. All subsequent communications with the appropriate MABAS DIVISION Dispatch Center will continue to be conducted on the IFERN 1 Channel, or with the COMM CENTER on channel A-ADAM ("Admin Channel") if it is a non-mabas incident. In cases where a department, station or unit(s) from outside Dane County is requested to respond on a non-mabas alarm (mutual aid) into Dane County, the COMM CENTER will advise the respective alerting agency to direct the department, station or unit(s) to communicate with the Dane County COMM CENTER on channel A-ADAM ("Admin Channel") while responding and prior to arriving on the scene. At the point the units(s) arrive in Level II staging: IF A STAGING OFFICER EXISTS: The units will remain on the IFERN 1 Channel or the "Admin Channel" (CITY OF MADISON FIRE ADMIN or County A-ADAM) and communicate with the staging officer. The STAGING OFFICER must have two radios available. One radio is to be kept on the assigned operations channel for communications with COMMAND. The other radio is to be kept on the IFERN 1 Channel or the "Admin Channel" (CITY OF MADISON FIRE ADMIN or A-ADAM) to manage units in staging. IF NO STAGING OFFICER EXISTS: The officer on the first unit to arrive in STAGING is expected to assume the role of the STAGING OFFICER; and continue in that role unless relieved by another officer assigned by COMMAND. The unit will switch to the assigned operations channel, WAIT UNTIL THEY ARE NOT INTERFERING WITH UNITS ON THE FIREGROUND, and advise COMMAND that they are "ON LOCATION, and establishing Level II staging, with (unit designation) as STAGING OFFICER" per protocol section 2I-2. CONTINUED 29

No specific radio message regarding establishment of Level II staging needs to be transmitted to the COMM CENTER per protocol section 2I-2. NOTE: In any of the scenarios above, it is possible that the response could involve a mix of City of Madison and County units. In such cases, the COMM CENTER Communicator will automatically establish a patch between the appropriate City of Madison and County radio channels per protocol section 2K-4, and will notify all units when the patch is up. The following guidelines should be used when establishing radio channel patches for joint City of Madison and County units: IF A UNIT IS RESPONDING TO LEVEL II STAGING: A patch will be set up between the IFERN 1 channel and the City of Madison "Admin Channel. IF THE UNIT IS MOVING FROM STAGING TO THE FIREGROUND: A separate patch will be automatically set up between the assigned operations channel for the incident and an available incoming unit s operations channel. COMMAND should always be notified by the COMM CENTER that a patch has been established. 2K-5-B MULTIPLE / SUBSEQUENT ALARM COMMUNICATIONS - EMS INCIDENTS The initial FIRST (STILL OR FULL STILL) ALARM responding Rescue/Medic unit(s) will be assigned to an appropriate operations channel per protocol section 2K-3. For a simple request for one (1) or two (2) additional Rescue/Medic units to the same incident, all Rescue/Medic units should be assigned to the same operations channel as the initially dispatched unit(s). For any other incident involving a MABAS Box Alarm or subsequent MABAS alarms, where additional Rescue/Medic units beyond the initial FIRST (STILL OR FULL STILL) ALARM level assignment are responding, the channel assignment for those Rescue/Medic units will follow the procedures outlined in protocol section 2K-5-A. 30

2K-6 COORDINATION OF SUPPORT ACTIVITIES / UNIQUE RESOURCES The primary objective of this section is to establish a protocol that addresses coordinating response(s) and on-scene activities of support, specialty, or unique resources such as a large number of Tenders, an Air Ambulance (Med Flight), Hazardous Materials, Collapse Rescue, or SCUBA teams that may be requested to respond to an incident already in progress. Basic operating principle: To manage units responding as unique or specialized resources, or functioning in a support role once the incident is already in progress (but do not necessarily represent a MABAS alarm resource) in such a way that it does not interfere with units functioning on the fireground. A. SUPPORT ACTIVITIES (Water Supply/Tender Shuttle): At the direction or concurrence of COMMAND, it is recommended support activities like water supply or tender shuttles be conducted on the MABAS FIREGROUND BLUE channel. If MABAS FIREGROUND BLUE is being utilized, it is recommended that the Group officer responsible for the support activity have two radios. One radio is to be kept on the assigned operations channel for communications with COMMAND. The other radio is to be kept on MABAS FIREGROUND BLUE. B. AIR AMBULANCE (HELICOPTER) RESPONSES: Air ambulances will always be assigned to the MARC-2 channel. At different points during the incident, the COMM CENTER may patch the air ambulance to other appropriate radio channel(s). If MARC-2 is not available the EMS-C channel (after DaneCom is implemented/operational) may be used as a secondary channel. FOR PATIENT INFORMATION: The COMM CENTER Communicator will patch MARC-2 to whatever radio channel is being used as MEDICAL CONTROL FOR LANDING ZONE INSTRUCTIONS (where COMMAND wants the LZ GROUP to manage landing on a stand-alone channel): In this case, no patch* is required. The LZ GROUP should be instructed to communicate with the air ambulance directly on MARC-2, or be patched with any available City of Madison TRS Talk Group. CONTINUED 31

FOR LANDING ZONE INSTRUCTIONS (where COMMAND wants the LZ GROUP to manage landing on the OPERATIONS channel): The COMM CENTER Communicator will patch** MARC-2 to whatever radio channel is being used as the operations channel (CITY OF MADISON Fireground 3, CITY OF MADISON Fireground 2, CITY OF MADISON CMED 5, CITY OF MADISON CMED 4, B-BAKER, C-CHARLIE, D-DAVID, E-EDWARD, F-FRANK, etc.) FOR LANDING ZONE INSTRUCTIONS (where LANDING ZONE is being managed by law enforcement): - The COMM CENTER communicator should first ask the law enforcement unit to switch to MARC-2 or be patched with any available City of Madison TRS Talk Group. - If the law enforcement unit does not have MARC-2 or cannot be patched with any available City of Madison TRS Talk Group, the COMM CENTER communicator should attempt to have the law enforcement unit switch to some radio channel managed by the "fire desk", and patch** MARC-2 to the selected channel. - If the law enforcement unit cannot switch to such a channel, the "fire desk" communicator shall speak with the sheriff or City of Madison PD communicator and together agree upon a law enforcement channel to be used; and the "fire desk" communicator will patch** MARC-2 to the selected law enforcement channel. ** NOTE: In all cases where a patch is used for landing zone activities, the patch should remain up until the air ambulance has lifted off, or until COMMAND requests the patch to be taken down. C. SPECIALTY TEAM RESPONSES: Specialty Team responses include: - City of Madison Level A or Level B Haz-Mat Team - City of Madison SCUBA / Water Rescue Team - City of Madison HURT (Heavy Urban Rescue Team) - State of Wisconsin HURT (Heavy Urban Rescue Team) CONTINUED 32