Columbus Division Of Fire Standard Operating Procedures Driving PDF

Standard Operating Procedures Subject: Driving S.O.P. Number 01-01-01 Vol-CH-Cat.Sub Approved Fire Chief Issued: 08/15/1995 Reviewed: 03/25/2019 Revised: 04/24/2019 Section 1 Administration 1.1 Purpose: The purpose of this procedure is to identify safe driving procedures for apparatus and veh...

Standard Operating Procedures Subject: Driving S.O.P. Number 01-01-01 Vol-CH-Cat.Sub Approved Fire Chief Issued: 08/15/1995 Reviewed: 03/25/2019 Revised: 04/24/2019 Section 1 Administration 1.1 Purpose: The purpose of this procedure is to identify safe driving procedures for apparatus and vehicles. Section 2 General 2.1 This SOP is established in conjunction with MOU #2017-1 regarding the cities implementation of Global Position System (GPS) / Telematics and the collective Bargaining Agreement between the City of Columbus and Local 67. 2.2 Parameters have been placed into the GPS system that triggers “Alerts” to system users. Vehicles are “Pinged” every two minutes; at every “Ping” the system gathers the vehicle data. The alert generating criteria are: The vehicle has exceeded the posted speed limit by 30 or more miles per hour (MPH) for two consecutive pings. The vehicle has exceeded 90 MPH at any time. The vehicle has idled for 4 hours or more. The vehicle is located outside of Franklin and its contiguous counties. 2.3 Members are reminded that current driving procedures and limits have not changed, the criteria above only produces an alert in the GPS system. 2.4 Drivers of all Fire Division vehicles shall have a valid Ohio driver’s license. 2.5 Drivers of all Fire Division vehicles shall be directly responsible for the safe and prudent operation of the vehicles under all conditions. When the driver is under the direct supervision of an officer, that officer shall be responsible for the actions of the driver. 2.6 All persons shall be dressed, seated and have seat belts fastened before the vehicle is moved for any reason. All persons must remain seated and belted at all times when the vehicle is in motion. Riding on tailsteps, sidesteps, running boards, or in any other exposed position is specifically prohibited. Standing while riding is specifically prohibited. 2.7 Members actively performing necessary emergency medical care while the vehicle is in motion shall be secured to the vehicle by a seat belt, or by a safety harness designed for occupant restraint, to the extent consistent with the effective provision of such emergency care. All other persons in the vehicle shall be seated and belted while the vehicle is in motion. Columbus Division Of Fire S.O.P. 01-01-01 Rev. 4/24/2019 1 of 2 2.8 Ordinarily, the speed limit will be obeyed during emergency response. The speed limit may be exceeded when traffic, road and weather conditions are favorable. All emergency responses shall be made with due regard for the safety of all persons using the street or highway. All emergency responses will have emergency lights and sirens operating concurrently. 2.9 When making an emergency response on the freeway, emergency lights and siren should not normally be used. Vehicles shall travel with the flow of traffic, and shall not exceed the posted speed limit. 2.10 Proceed with extreme caution when necessary to travel in the oncoming lane of traffic. Other drivers may not expect you to be in this position and may turn into your path. Fire Division personnel shall be responsible for anticipating the movement of other vehicles and shall pass other vehicles only if reasonably certain the other driver is aware of your presence and location. 2.11 When traveling in the oncoming lane of traffic, all vehicles should come to a complete stop and assure safe passage before proceeding through any intersection. 2.12 Drivers of Division Vehicles shall not proceed through any intersection against a red light or stop sign unless they are reasonably certain it can be accomplished safely. Do not assume that other drivers see or hear you. Make sure all other drivers are aware of your presence and have their vehicles under control before proceeding through the intersection. 2.13 During an emergency response, drivers of all Fire Division vehicles shall bring the vehicle to a complete stop for any of the following: - When directed by a law enforcement officer; - Blind intersections; - When the driver cannot account for all lanes of traffic in an intersection; - When other intersection hazards are present; - When encountering a stopped school bus with flashing warning lights; and - All unguarded railroad crossings. 2.14 During non-emergency travel, drivers shall obey all traffic control signals and signs and all laws and rules of the road for the State of Ohio and the City of Columbus. 2.15 Whenever a FIRE apparatus is stopped and the driver is not in his/her seat, the wheels shall be chocked, front and back. Columbus Division Of Fire S.O.P. 01-01-01 Rev. 04/24/2019 2 of 2 Standard Operating Procedures Subject: Backing of Division Vehicles Approved S.O.P. Number 01-01-02 Vol-CH-Cat.Sub Page: 1 of 1 Fire Chief Effective Date: 04/03/2000 Revised Date: I. PURPOSE: The purpose of this procedure is to more clearly define the proper techniques employed, and responsibilities assigned, when the backing of Division vehicles is required. II. RESPONSIBILITY: It shall be the responsibility of each member to know, understand, and utilize these procedures as they apply to the situation at hand. It shall further be the responsibility of all Division Officers to train their subordinates in the proper application of these procedures and to implement and enforce the use of these procedures. III. IMPLEMENTATION: Because the Division experiences a large percentage of its vehicular accidents when backing, the following procedures are mandatory for use by any Division vehicle permanently staffed with two or more members. Vehicles assigned to individuals, vehicles in-transit while out of service, or vehicles forced to relocate at the scene of an emergency without the benefit of personnel to assist with backing, for example, should exercise extreme caution when backing, if indeed it is necessary at all. IV. ACCOUNTABILITY: Because backing a vehicle is an inherently risky operation, and Division policy clearly calls for assistance with this procedure, both the driver/operator AND the officer or partner(s) will be held equally accountable for violations of this SOP. V. PROCEDURE: A. Driver and/or officer or partner(s) shall ensure at least one, if not more, member(s) is (are) off the vehicle assisting and directing the driver to assure a safe maneuver is completed. B. Driver and backer(s) must remain in both visual and voice contact at ALL times during the backing process. 1. Driver must stop vehicle immediately if backer is not visible. 2. Backer must have portable radio (if available), on the same frequency as driver, during the procedure in order to assure voice communication. 3. Driver must monitor radio transmissions of backer (when portable radio is available) during backing operations. DO NOT DEPEND ON YELLING TO BE HEARD! Standard Operating Procedures Subject: Rescue Support Units S.O.P. Number 01-01-06 Vol-CH-Cat.Sub Page: 1 of 1 Approved Acting Fire Chief Effective Date: 03/01/2007 Revised Date: I. PURPOSE: The purpose of this procedure is to identify the response and utilization of the rescue support units (RSUs). II. RESPONSIBILITY: It shall be the responsibility of each member to know, understand, and utilize these procedures as they apply to the situation at hand. It shall further be the responsibility of all Division Officers to train their subordinates in the proper application of these procedures and to implement and enforce the use of these procedures. III. RESPONSE: The RSU’s may be called for by an officer, acting officer, or incharge rescue person at anytime that they foresee the need to use some of the equipment or absorbent at an incident. The personnel from Station 5 and 19 shall be the primary personnel responsible to take the vehicle to an incident. The FAO will dispatch the next nearest available company to take the vehicle to an incident if personnel from Station 5 and 19 are not available. IV. UTILIZATION: The tools, equipment, lumber, and cribbing carried on the vehicles shall be used to assist rescue personnel at a technical rescue incident. Any company may use the absorbent when the need arises. V. RETURN TO SERVICE: The rescue companies on the incident shall see that the tools and equipment are returned to the vehicle after use. If the absorbent is used, the company that called for the vehicle shall have the responsibility to ensure that the absorbent is replaced as soon as possible from Logistics or Station 4. VI. The RSU’s shall be checked by the assigned rescue companies on each Wednesday. Standard Operating Procedures Subject: Radio Procedures Approved S.O.P. Number 01-02-01 Vol-CH-Cat.Sub Fire Chief Issued: 03/28/2003 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this SOP is to identify the proper procedure for communicating over the radio and the initial radio procedure after being dispatched on an emergency run. Section 2 General 2.1 Do not transmit if the channel is in use. 2.2 Depress the press to talk button. Wait for the carrier to open before speaking. 2.3 Speak slowly and distinctly in a normal conversational tone. 2.4 Know what you are going to say before you transmit. 2.5 When initiating radio contact: (1) Say who you are calling. (2) Say who you are. (3) Give your message. 2.5.1 Short Message Example (Engine 13 reporting a Signal “O”): E-13: “Columbus Fire, Engine 13 has a Signal O” FAO: “Engine 13, Signal O” 2.5.2 Long Message Example (Engine 13 has a long message): E-13: “Columbus Fire, from Engine 13” FAO: “Engine 13, Go” E-13: “Notify Battalion 3 that we need his assistance at Hudson Elementary. A student pulled the fire alarm”. Section 3 Status 3.1 Companies shall accurately maintain their status with the Fire Alarm Office (FAO). Columbus Division of Fire | SOP 01-02-01 Rev. 04/04/2016 1 of 2 3.2 Members shall notify the FAO whenever apparatus leaves the station for any reason other than response to emergency or service runs originating from the FAO via MDC, telephone or radio. 3.3 Members shall notify the FAO when apparatus returns to quarters or is temporarily located at other division locations via MDC, telephone or radio. 3.4 All companies dispatched and responding to emergency runs shall verify their response over the vehicle’s Mobile Data Computer (MDC). 3.5 When directed to respond on a non-Columbus Fire talkgroup, mark “Enroute” by voice on the specified non-Columbus talkgroup. This will be in addition to pressing the MDC’s ‘Enroute’ button for notification of the Columbus FAO. 3.5.1 Example (Engine 13 dispatched on UA-1) (1) Go to the radio Fireground Talkgroup UA-1 (2) E-13: “Upper Arlington Fire, Engine 13 responding to Kenny Road” (3) UA Dispatcher: “Engine 13 responding” 3.6 Members shall be guided by all orders and directions received from Columbus FAO and/or other jurisdiction’s dispatch center. No member shall ignore or disregard such orders or directions, or attempt to issue orders to the Columbus FAO or other jurisdiction’s dispatch centers. 3.7 Refer to SOP 01-02-02 for responding and fireground radio procedures when assigned to a fireground talkgroup. Section 4 Request to be added to an Incident 4.1 As a general guide, a company should not request to be added to an incident unless they are likely to be the first arriving of that type resource. 4.2 Requests to be added to a run shall be made on the assigned talkgroup only. 4.2.1 If the incident is assigned a fireground talkgroup, the request shall be made on the B# IC talkgroup. Columbus Division of Fire |SOP 01-02-01 Rev. 04/04/2016 2 of 2 Standard Operating Procedures Subject: Fireground Communications S.O.P. Number 01-02-02 Vol-CH-Cat.Sub Approved: Acting Fire Chief Issued: 07/01/2015 Reviewed: 12/01/2018 Revised: 01/01/2019 Section 1 Purpose 1.1 The purpose of this procedure is to provide for the effective management of incident operations by establishing common practices for radio communications utilized at incidents involving multiple companies. Section 2 Fireground Radio Talkgoup Assignment 2.1 Multi-company incidents including fire and/or rescue incidents will initially be assigned two talkgroups: (1) B# IC (2) B# FG 2.1.2 All companies should monitor both talkgroups while responding. 2.1.3 Chiefs and Safety Officers should monitor both talkgroups throughout the incident. 2.2 The B# IC talkgroup will be utilized by assigned companies for the purpose of: (1) Verbally marking “responding” when an MDC is not available. (2) Adding/replacing companies assigned to the incident. (3) Verbally marking “on scene”, unless otherwise addressed in Section 2.3 (4) Non-critical communication between the Fire Alarm Office and the Command Post. The level at which this talkgoup is utilized for this purpose will be at the discretion of the incident commander (5) Necessary communications between the Incident Commander and responding companies or the other Chief and Safety Officers operating on the fireground. The level at which this talkgroup is utilized for this purpose will be at the discretion of the incident commander. Columbus Division of Fire | S.O.P. 01-02-02 Rev. 01/01/2019 1 of 4 (6) Communication channel between the Incident Command Post and the Fire Alarm Office, Division/Group Supervisors, Branch Directors, and Staging Area Manager during a multi-alarm or complex incident. 2.3 The B# FG talkgroup will be utilized by assigned companies for the purpose of: (1) First arriving company to transmit the initial radio report. (2) First two Engines and the first Ladder to call “on scene”. (3) First arriving Battalion Chief to call “on scene” and receive a “C-A-N Report” and transmit a status report. (4) Fireground communications for first alarm otherwise assigned to a tactical talkgroup. companies, unless (5) The “STAY” talkgroup for companies involved in the firefighter rescue when a “MAYDAY” has been declared (SOP 02-01-06). 2.4 The designated battalion tactical talkgroup (B# TAC 1-8) will be utilized by assigned companies for the purpose of: (1) First alarm fire companies when assigned to Divisions and/or Groups. (2) Multi-alarm fire companies assigned within the expanded incident command system. 2.4.1 If an EMS Group or Branch is established, the (BN# EMS) talkgroup should be utilized. 2.5 The designated battalion staging talkgroup (BN# STG) will be utilized by multi-alarm companies for the purpose of: (1) Communications by multi-alarm companies assigned, responding, and arriving at Level II Staging Area. (2) Communications between the Fire Alarm Office and the Staging Area Manager. 2.6 When crews are operating below grade, in large commercial buildings, high-rise occupancies, or in areas known to have communication issues the Incident Commander should monitor the designated non-repeated talkgroup (B# Direct Alpha, Bravo, Charlie) or DVRS Digital Vehicle Repeater System, if utilized. Section 3 Fireground Benchmarks 3.1 Fireground benchmarks are used to indicate the accomplishments of fireground objectives. Columbus Division of Fire | S.O.P. 01-02-02 Rev. 01/01/2019 2 of 4 3.2 Fireground benchmarks should be announced on the B# FG talkgroup. 3.3 The following fireground benchmarks shall be reported via radio: (1) “Working Fire”. Indicates an incident that requires multiple resources to control the situation. A “working fire” triggers the Fire Alarm Office to send the appropriate working fire assignment. (2) “360 Complete”. Announced after the initial 360 is completed. (3) “All Clear” (primary & secondary). Indicates completion of primary and secondary searches (SOP 01-03-21). (4) “RIT Established”. This benchmark should include the companies assigned as the Rapid Intervention Team and their location (SOP 0201-03). (5) “Water on the Fire”. Indicates first water on the fire from an interior position and that ventilation may soon be initiated safely. (6) “Situation Contained”. Indicates the incident has been stabilized and the incident can be effectively handled with companies on the scene. (7) Personnel Accountability Report (PAR). When announced by the incident commander, a PAR indicates that all personnel assigned to the incident are accounted for. A completed PAR should be announced on the B# FG talkgroup (SOP 02-02-01). Section 4 Fireground Reports 4.1 Status Report. An announcement made via the radio after each change of command, or as deemed necessary, by the assuming officer. A status report will include the current fireground strategy and the Incident Action Plan. 4.1.1 Status Report Example: “Columbus Fire from Battalion 2, Chief Smith will be assuming command of the Polaris Parkway incident, we are currently in the offensive strategy with interior operations working to contain the fire and obtain an ‘All Clear’ on both the fire building and the Bravo 1 exposure”. 4.1.2 When a status report is used following a transfer of command, it should include the name and rank of the new Incident Commander (SOP 01-0308). 4.2 Progress Report. Progress information between incident incident. Periodic progress Incident Command, which is reporting on the fireground relays critical command and companies assigned to an reports provide important information to essential to developing as sound Incident Columbus Division of Fire | S.O.P. 01-02-02 Rev. 01/01/2019 3 of 4 Action Plan, establishing tactical objectives, maintaining personnel accountability, and efficiently managing incident resources. 4.2.1 Company officers and Division/Group Supervisors shall, on a regular basis report progress or lack of progress in completing their assignment as well as any deviation from established plans. 4.2.2 Company officers and Division/Group Supervisors should initiate a Progress Report at a time that is most conducive to operations. 4.2.2.1 Supervisors who do not receive periodic progress reports from assigned personnel shall request a report at intervals deemed appropriate based on conditions. 4.2.3 An effective method to request and receive a progress report is the C-A-N Report format. 4.2.3.1 The C-A-N Report stands for: C-Conditions, A-Actions, and NNeeds. (1) Conditions: What do you have? a. Current location b. Smoke, fire and heat conditions c. Obstacles encountered and other pertinent information (2) Actions: What are you doing? a. Current actions b. Progress or inability to complete assigned objectives (3) Needs: What do you need? a. Resources or support needed to complete assigned objectives Columbus Division of Fire | S.O.P. 01-02-02 Rev. 01/01/2019 4 of 4 Standard Operating Procedures Subject: On-Scene Radio Report Approved S.O.P. Number 01-02-03 Vol-CH-Cat.Sub Fire Chief Issued: 09/28/2015 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this SOP is to identify the procedure to be used when giving an Initial Radio Report. Section 2 Overview 2.1 The initial radio report is given in two parts: (1) The first report is the brief initial radio report that includes scene size up and establishing command. (2) The second report is the Initial Action Plan. Section 3 Initial Radio Report 3.1 It shall be mandatory that the first arriving division officer or member on the scene of any fire, rescue, or motor vehicle incident give a brief initial radio report and establish command. 3.1.1 If several apparatus arrive simultaneously, the member giving the Initial Radio Report shall designate the highest ranking officer as the incident commander. 3.2 The Initial Radio Report shall consist of: (1) Company Designation (2) Building/Incident Description and Construction i. Building heights over two stories, but having heights within reach of the aerial ladder, may be designated multistory. ii. If the building or structure is well known, the name of the building will suffice. (Kroger, Days Inn, McDonalds, etc.) iii. Occupancy: residence, apartment, hospital, hotel, business, vacant, etc. iv. Type of Construction: ordinary, frame, lightweight, etc. (3) Problem Description Columbus Division of Fire | SOP 01-0 Rev. 04/04/2016 1 of 3 i. The apparent extent of emergency, e.g. situation contained, smoke showing, working fire, 2nd alarm, etc. (4) Name of Incident Commander and command mode (SOP 01-03-04). (5) Location of Accountability i. If the Command Post is not located on the 'Alpha side’ of the structure, its location should be given. 3.2.1 Example “Columbus Fire Engine 16 on-scene of a two-story frame single family residence; light smoke showing from the second story, Delta side; Lt. Smith will have Mobile Command; Engine 16 will have Accountability”. 3.2.2 The Initial Radio Report may also include any initial actions being taken to begin to mitigate the situation. Section 4 Initial Action Plan (IAP) Report 4.1 Prior to initiating offensive operations, and after a more thorough assessment of the situation that includes the completion of the 360 , the Incident Commander shall announce the Incident Action Plan on the B# FG talkgroup. 4.2 In the event that a 360 is unable to be completed prior to initiating offensive operations, the Incident Commander shall announce this fact on the B# FG. 4.3 The IAP Report shall include the following: (1) Findings from the 360 i. “Smoke and Fire Venting from Charley Side second floor, make this a working fire” or “Nothing Significant from Charley Side” or ii. “360 Unremarkable” or “360 NOT achieved”. (2) Immediate Life Safety Issues/Hazards Identified i. “We have a victim in the 2nd floor window on charley side needing rescue” or “Wires down on the Charley side”. (3) Location of the Fire i. “We have a basement fire on the Charley-Delta corner”. (4) Incident Action Plan and Strategy i. “Engine 16 will be doing a transitional attack through the basement window on the bravo side then entering for an offensive strategy, Ladder-13 search 2nd floor, Engine-13 prepare to enter the alpha side with a 2nd line to support the search, etc.” or “Investigating further”. Columbus Division of Fire | SOP 01-0 Rev. 04/04/2016 2 of 3 (5) Additional Resources i. Determine if there is a need to call for additional resources (e.g. extra companies, second alarm, Police, etc.). ii. Additional Resources should be standing by at the scene, prepared to go into action if there is a possibility the incident may expand beyond the capabilities of the companies working on the incident. Do not hesitate to call for additional resources early. iii. The number one reason to call for additional resources is to address life safety issues, both firefighter and civilian. 4.4 During the Investigation Mode, the IAP report may be limited to one or more of the following: (1) 360 Report (2) Announcement of a Situation Contained Section 5 Single Company Responses 5.1 When only one company responds to an emergency such as an auto fire or trash fire, the company officer shall transmit a brief initial radio report upon arrival. As soon as it has been determined that no additional help will be required, a Situation Contained will be transmitted to the FAO. 5.1.1 Single Company Example “Columbus Fire Engine 14 on the scene, we have a trash fire at the rear of a frame garage, Situation Contained, tie up Engine 14”. Columbus Division of Fire | SOP 01-0 Rev. 04/04/2016 3 of 3 Standard Operating Procedures Subject: Urgent / Mayday Communications S.O.P. Number 01-02-04 Vol-CH-Cat.Sub Approved: Acting Fire Chief Issued: 07/01/1998 Reviewed: 12/01/2018 Revised: 01/01/2019 Section 1 Purpose 1.1 The purpose of this document is to provide a consistent policy for Urgent or Mayday communications on the fireground. Section 2 Urgent Communication 2.1 The Urgent message allows members who notice a warning sign of a pending hazardous situation to transmit that information to other members working in the area. 2.2 Examples of reasons to use the Urgent message are, but not limited to: 1) 2) 3) 4) 2.3 Early sign of potential collapse. Signs of possible backdraft or flashover. Loss of water on attack lines. Change from Offensive to Defensive Mode. When the hazard is noted the member will call “Urgent” on the fireground or tactical channel in which they are operating. The member will then give the situation status and an appropriate recommendation to protect members from the danger. 2.3.1 If necessary, the incident commander will then contact the member making the urgent transmission to find out more information. 2.4 Urgent Message Example Ladder 8 talkie #3 transmits Urgent message on FG: “Command from Ladder 8 talkie 3, Urgent, Alpha side wall is showing signs of collapse. All personnel evacuate the Alpha side Collapse Zone.” Columbus Division of Fire | S.O.P. 01-02-04 Rev. 01/01/2019 1 of 3 2 Command (or Div. /Grp. Supervisor) repeats Urgent message on affected talkgroup or All Call All companies Urgent, we have a potential collapse of the Alpha side wall, all personnel evacuate the Alpha side Collapse Zone. Section 3 Mayday Communications 3.1 Mayday message is reserved for situations of imminent danger of personnel. 3.2 Mayday messages can be used for, but not limited to: 1) Member is trapped by collapse. 2) Member becomes lost, disoriented, or entangled. 3) Member becomes ill or injured inside the hazard zone and this injury may inhibit his safe exit. 3.3 Member(s) in imminent danger should transmit the message, “MaydayMayday-Mayday” followed by a L-U-N-A-R Report”. 3.3.1 “L-U-N-A-R”. An acronym for Location, Unit, Name, Air, Resources. This is critical information that should be obtained during a call of MAYDAY. 3.4 Command will declare “Radio Restriction” and repeat the “Mayday” message. 3.4.1 “Radio Restriction”. Prompts all listeners to stop talking over the radio unless a life safety message must be relayed. 3.5 Radio Restriction Tone. The Radio Restriction Tone will be activated by the FAO once a Mayday is declared. This is a tone that marks the channel every 10 seconds. It prompts listeners to stop talking and only the assigned companies will remain on this talkgroup. The audible tone does not affect communications. 3.6 After a Mayday Message is received, the affected talkgroup should only be used by the Incident Commander, Division or Group Supervisor or the Rapid Intervention Crew, in addition to the member who initiated the Mayday (SOP 01-02-02). 3.7 Once the Mayday is received and the IC determines that a “change to” talkgroup is necessary, TAC 1 will be pre-designated for fire ground operations. If TAC 1 is already in use then the IC will determine and announce the “change to” talkgroup. 3.8 Example Firefighter Smith becomes trapped and transmits Mayday: Columbus Division of Fire | S.O.P. 01-02-04 Rev. 01/01/2019 2 of 3 2 “Mayday-Mayday-Mayday! This is FF Smith from Engine 25, I am trapped under a collapsed ceiling on the second floor Bravo side bedroom, send help, I have 500 psi of air remaining, need air and help removing debris. Command repeats message and activates RIC on effected talkgroup and/or All Call Talkgroup: Command to all companies Radio Restriction; we have a Mayday on the fireground. FF Smith from E25 is trapped under a ceiling collapse in a bedroom on the Bravo side second floor. He has 500 psi of air and needs the RIC for air, extrication, and removal. All fire ground operations move to TAC 1. I repeat all fire ground operations mover over to TAC 1. BN 1 will take over the RIC group on BN 3 FG with E16, R16, and L1 3.9 After the Mayday is resolved the IC should announce the return to normal operations and may move companies back to the FG channel. Columbus Division of Fire | S.O.P. 01-02-04 Rev. 01/01/2019 3 of 3 2 Standard Operating Procedures Subject: Emergency Assistance S.O.P. Number 01-02-05 Vol-CH-Cat.Sub Approved: Acting Fire Chief Issued: 07/01/1998 Reviewed: 12/01/2018 Revised: 01/01/2019 Section 1 Purpose 1.1 The purpose of this procedure is to identify methods of requesting assistance for personal safety. Section 2 General 2.1 The term “Emergency” should be used whenever requesting assistance for reason of personal safety from potentially violent situations. 2.1.1 For Urgent or Mayday communications on the fireground refer to SOP 0102-04. 2.2 Emergency assistance requests will be in one of two modes. 1) 10-57- A deteriorating situation that may cause personal harm. 2) 10-3- An imminent danger situation. 2.3 Members will transmit the message “Emergency” or push the Emergency button on the radio or MDC. 2.3.1 If using the Emergency Banner button on the radio. It should be depressed for at least 1.5 seconds to notify the Fire Alarm Office that emergency assistance is needed. 2.3.2 The Fire Alarm Office will request you to “check your display”. If possible, you should respond with the appropriate code, either 10-57 or 10-3. 2.3.3 If no answer to the dispatcher’s request, they will repeat once and then initiate a 10-3 response to your location. 2.4 2.5 Following a request for “Emergency” assistance, you should give your company designation and location. The FAO will then initiate the appropriate response. Columbus Division of Fire | S.O.P. 01-02-05 Rev. 01/01/2019 1 of 2 Section 3 10-57 Response 3.1 When a 10-57 response is requested, the Fire Alarm Office will initiate the following actions: 1) Ask the company for a nature. 2) Notify the Police Dispatcher of the request for a 10-57 response, and request an ETA for police response. 3) The Dispatcher will notify the on-duty Fire Alarm Office Lieutenant. 4) The Dispatcher will check on the Units status every 2 minutes until the incident is deemed “under control”. 5) The Fire Alarm Office Lieutenant may send fire apparatus to the scene depending on the situation and the ETA given by Police. Section 4 10-3 Response 4.1 When a 10-3 response is requested, the Fire Alarm Office will initiate the following actions: 1) Immediately notify the Police Dispatcher of the request for 10-3 assistance, and request an ETA for police response. 2) Activate the channel marker on the channel the 10-3 was requested on. “Radio Restriction Tone”- Will be activated by the FAO once a 10-3 is announced and is a tone that repeats every 10 seconds. This prompts listeners to stop talking and only assigned companies will remain on this channel. The channel marker does not affect communications. 3) The Dispatcher will notify the on-duty Fire Alarm Office Lieutenant. 4) All other radio traffic should be directed to 9 EMS 2 until situation contained, unless otherwise notified by FAO. 5) The Fire Alarm Office will send the closest two fire apparatus (Engines, Ladders or Rescue), a transport vehicle, EMS Supervisor, Battalion Chief and SO2 to the location. This response will stage away from the scene and will be guided by the first in officer’s decisions. Responding companies will wear proper PPE for incident nature. 6) ES-2 will also be notified by the Fire Alarm Office. Section 5 Other Requests 5.1 Non-Emergency requests for police (i.e. complaints, reports, traffic, etc.) other than 10-3 will require a reason for request. Columbus Division of Fire | S.O.P. 01-02-05 Rev. 01/01/2019 2 of 2 Standard Operating Procedures Subject: ICS Purpose and Background Approved S.O.P. Number 01-03-01 Vol-CH-Cat.Sub Fire Chief Issued: 07/01/1998 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this procedure is to explain the background and purpose of the Incident Command System and the National Incident Management System. Section 2 Overview 2.1 The Incident Command System (ICS) was developed as a consequence of fires that consumed large portions of wild land, including structures, in Southern California in 1970. As a result of those fires, ICS was implemented to allow agencies to work together toward a common goal in an effective and efficient manner. 2.2 This system consists of procedures for controlling personnel, facilities, equipment, and communications. 2.3 ICS is designed to begin developing from the arrival of the first resource until the requirement for management and operations no longer exists. The Incident Commander (IC) is a title that can apply equally to an engine company officer, or to the chief of the department, depending upon the situation. The structure of ICS can be established and expanded depending upon the changing conditions of the incident. It is intended to be staffed and operated by qualified personnel from any emergency services agency and may involve personnel from a variety of agencies. 2.4 The system can be utilized for any type or size of emergency, ranging from a minor incident involving a single unit, to a major emergency involving several agencies. The ICS allows agencies to communicate using common terminology and operating procedures. It also allows for the timely combining of resources during an emergency. Section 3 National Incident Management System 3.1 ICS in the fire service is a portion of a broader system of management called the National Incident Management System (NIMS). 3.2 The goal of the NIMS is to develop and maintain a credible emergency management capability nationwide by integrating activities along functional lines at all levels of government, and, to the fullest extent possible, across all hazards. It should be kept in mind that the NIMS process is a means of improving capability and is not an end itself. The various steps in the NIMS process are intended to serve management at each level of government by providing basic Columbus Division of Fire | SOP 01-03-01 Rev. 04/04/2016 1 of 2 2 information upon which reasonable and justifiable plans can be made and effective action taken to increase emergency management capability nationwide. 3.3 The NIMS is used by the Federal Emergency Management Agency (FEMA) in preparing all government agencies to coordinate activities at incidents and disasters. 3.4 Incident Command procedures are designed to accomplish the following 3.4.1 Fix responsibility of command with a designated division member through a standardized identification system, based on arrival sequence and other variables. 3.4.2 Insure that visible, direct, effective command be established as early as possible upon arrival at the incident scene. 3.4.3 Establish an effective framework within which the activities and responsibilities assigned to the Incident Commander can be properly addressed. 3.4.4 Provide a system for accomplishing the orderly transfer of command from the initial Incident Commander to later arriving division officers. 3.4.5 The one function that will always be filled at every emergency incident, regardless of size, is the Incident Commander’s (IC) position. The IC has the responsibility for overall management of the incident. Columbus Division of Fire | SOP 01-03-01 Rev. 04/04/2016 2 of 2 2 Standard Operating Procedures Subject: Chain of Command Approved S.O.P. Number 01-03-02 Vol-CH-Cat.Sub Fire Chief Issued: 07/01/1998 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this procedure is to identify the Chain of Command at emergency incidents. Section 2 General 2.1 The chain of command establishes a framework of responsibility and an effective command system for emergency operations. The chain of command in the Incident Command structure may not follow the established chain of command of the Columbus Division of Fire. In the Incident Command System, a member of any rank can be assigned a command position. For example; a firefighter paramedic could be the Medical Branch Director with officers of any rank working under their command. 2.2 Orders are normally to be given to subordinates only by their immediate supervisor. 2.3 The incident Safety Officer can bypass the chain of command and issue orders when personnel are in imminent danger. 2.4 Orders are to be given in a clear and precise manner. It is the responsibility of the officer to assure that subordinates understand the orders given 2.5 A company shall work as a unit and stay together as much as possible. 2.6 When a company member is separated from his/her company to complete a task, that member shall, upon completion of that task, shall be under automatic orders to return and report to his/her immediate supervisor. 2.7 When a member receives an order from an officer other than his/her immediate supervisor, that member shall be guided by the following procedure: (1) (2) (3) State any previous orders and the officer that issued that order. Follow the judgment of the officer superseding the previous order. After completing the superseded order, report the fact to your officer. Columbus Division of Fire | SOP 01-03-02 Rev. 04/04/2016 1 of 2 2.8 Giving orders to other than your immediate subordinate should be done only for the purpose of life safety. 2.9 Any uniformed personnel arriving first on the scene shall establish Command, give the necessary size-up and direct operations. 2.10 The first arriving officer or member shall assume Incident Command and remain in charge until formally relieved by a superior officer. 2.11 To formally assume command, the superior officer shall follow the Transfer of Command procedure (SOP 01-03-05). This procedure shall be followed any time a transfer of command takes place. 2.12 The ranking officer, other than Deputy Chief and above, shall assume command at all emergency incidents unless it is under control and a Situation Contained is ready to be announced. 2.13 The responsibility for effective incident operations shall be placed with the highest ranking officer at the scene regardless of whether or not that officer formally assumes command. Columbus Division of Fire | SOP 01-03-02 Rev. 04/04/2016 2 of 2 Standard Operating Procedures Subject: Command Responsibilities S.O.P. Number 01-03-03 Approved Vol-CH-Cat.Sub Fire Chief Issued: 07/01/1998 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this procedure is to assist member in determining the responsibilities of the Incident Commander. Section 2 General 2.1 The Incident Commander is responsible for the following: (1) Assumes an effective command location. (2) Calls on the scene and transmits the initial radio report and size-up. a. If it is a “working incident”, assigns a name to the incident. i. For example a working incident at 300 N. High St. could be called “North High Command” or “Hyatt Regency Command” for the occupancy. (3) A “working incident” is defined as any emergency situation that requires multiple resources to achieve a Situation Contained. (4) Assesses the incident priorities. (5) Determines the incident’s strategic goals and tactical objectives. (6) Develops and implements the Incident Action Plan. (7) Develops an incident command structure appropriate for the incident. (8) Assesses resource needs and orders, deploys, needed resources. (9) Coordinates all emergency activities. (10) Serves as Incident Safety Officer until these duties are assumed or reassigned. (11) Coordinates activities of outside agencies. (12) Authorizes information release to the media. (13) Returns companies to service. Columbus Division of Fire | SOP 01-03-03 Rev. 04/04/2016 1 of 1 Standard Operating Procedures Subject: Fire, Bomb, and Hazmat Investigations S.O.P. Number 01-03-03.01 Vol-CH-Cat.Sub Approved: Fire Chief Issued: 10/28/2019 Reviewed: 09/01/2019 Revised: 10/28/2019 Section 1 Administration 1.1 Purpose: The purpose of this procedure is establish guidelines for identifying and reporting the origin and cause of fires, as well as establishing guidelines for requesting a Fire Investigator. 1.2 Responsibility: It shall be the responsibility of each member to know, understand, and utilize these procedures as they apply to the situation at hand. It shall further be the responsibility of all Division Officers to train their subordinates in the proper application of these procedures and to implement and enforce the use of these procedures. Section 2 Policy 2.1 The fire marshal and the chief of the fire department of each municipal corporation…shall investigate the cause, origin, and circumstances of each major fire, as determined by the rules of the fire marshal, occurring in such municipal corporation…which property has been destroyed or damaged, and shall make an investigation to determine whether the fire was the result of carelessness or design (ORC 3737.24 Investigation of fire). 2.2 An officer making an investigation of a fire occurring in a municipal corporation…shall forthwith notify the marshal, and within one week of the occurrence of the fire shall furnish him a written statement of all facts relating to its cause and origin and such other information as is required by forms provided by the marshal (ORC 3737.24 Investigation of fire). Section 3 Incident Commander Responsibilities 3.1 It is the Division of Fire's policy that anytime that a Fire Investigator is NOT called to the scene, the Incident Commander has a duty to: Columbus Division of Fire | S.O.P 01-03-03.01 REV 10/28/2019 1 of 3 2 Investigate the origin and cause of every fire and/or HazMat incident, and then report completed findings with a detailed narrative to the State of Ohio utilizing the NFIRS report Properly gather and/or preserve any evidence (including photographs) that can establish the origin and cause of the fire All photographs are considered to be evidence and shall be immediately forwarded to the Fire & Explosives Investigations Unit (FEIU) by either email ([email protected]) or by secure delivery using other approved electronic media Establish and maintain a chain of custody for any evidence gathered from time of obtainment to time of proper delivery (FEIU) Obtain names of occupants, owners, potential witnesses and contact information so that they can be located/contacted at a later date Section 4 Investigator Required 4.1 If the Incident Commander is unsure if an incident requires the response of a FEIU Investigator, a FEIU Investigator should be contacted by phone to obtain proper guidance. 4.2 The on-scene Incident Commander shall request the assistance of a FEIU Investigator whenever the following circumstances exists: Any fire where the I/C is unable to determine the cause and origin Any suspicious and/or incendiary fires that require further investigation Any fire, whether accidental or malicious, where juveniles are believed to be involved in the ignition of the fire Any injury or death of any person as a result of a fire Any smoke inhalation, burn, or scalding injuries, regardless of how the burns were obtained Any fire on the property of an educational facility (school), nursing home, or place of worship Any structure fire with damage estimated to be in excess of $100,000 Any suspicious package and/or bomb incident within City limits, regardless of whether or not a device detonated Any HazMat incident that may have a nexus to a criminal act. (e.g. white powder / threat / intentional release / drug lab) Any incident requiring an immediate arrest for Arson and/or related crimes Any fire involving City owned property Columbus Division of Fire | S.O.P. 01-03-03.01 REV 10/28/2019 2 of 3 22 Section 5 Run Card Change and Duties of Engine Company 5.1 The run cards for “Person Burned” runs have been changed to include an Engine company with the Medic. 5.2 Duties of the Engine company include the following: Assist with patient care as needed Secure the scene Investigate as outline above in Section 3 Incident Commander Responsibilities Call for a FEIU Investigator when required as outlined in Section 4 Investigator Required. (Note: Prevention 18 personnel are not qualified as a FEIU Investigator). Section 6 Legal Considerations 6.1 All information regarding fires that are suspicious, incendiary, or still under investigation, are considered possible crime scenes and are confidential in nature. In these cases, no sensitive information should be shared with the media or anyone outside one’s chain of command. 6.2 Any device used to obtain photographs and/or videos of fires that are considered suspicious or incendiary may result in the seizure of said device for investigatory and/or legal purposes until such time the investigation and/or trial is completed. Columbus Division of Fire | S.O.P. 01-03-03.01 REV 10/28/2019 3 of 3 22 Standard Operating Procedures Subject: Establishing Command S.O.P. Number 01-03-04 Vol-CH-Cat.Sub Approved Fire Chief Issued: 07/01/1998 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this procedure is to assist members in Establishing Command. Section 2 General 2.1 It shall be mandatory for the first arriving division officer or member on the scene of an emergency incident initiate the basic incident command function, establish a Command Post, and assume all related command responsibilities. 2.2 The first arriving division officer or member must decide on an appropriate commitment for each assigned company. This decision should result in command being exercised according to the provisions of one of three (3) options: (1) Fixed Command (2) Mobile Command (3) Pass Command Section 3 Fixed Command 3.1 Fixed command is defined as a command structure where the incident commander maintains a fixed command location, usually outside of a structure, and devotes all of his/her energies to command. Fixed command is desirable and should be used unless conditions dictate otherwise. 3.2 Fixed Command Example: “Columbus Fire Engine and Ladder 12 on the scene of a multi-story multi-family, wood frame apartment building. We have heavy fire showing on the Alpha-Delta corner 1st floor, make this a working fire; Capt. Smith will be in-charge of fixed command. Engine 12 will be attacking with a 2 1/2; Ladder 12 will be conducting a primary search. Accountability will be at the command post on the Alpha Side”. Section 4 Mobile Command 4.1 Mobile Command is utilized in situations when the division officer or member assuming command accompanies his/her crew in order to investigate the situation. Columbus Division of Fire | SOP 01-03-04 Rev. 04/04/2016 1 of 3 4.2 Mobile command should be reserved for one of the following situations: (1) Situations where there is ‘nothing showing’ and the division officer or member assuming command accompanies his/her crew in order to investigate the situation. (2) Situations that are likely to be quickly contained with few resources committed. (3) While awaiting the arrival of the next arriving officer after PASSING command. 4.3 Whenever the Mobile Command is chosen, it should be concluded rapidly, with one of the following outcomes: (1) The situation is quickly stabilized during the initial investigation. (2) The preliminary investigation reveals no need for additional companies. (3) The situation is contained. (4) Command is transferred. 4.4 If the situation is not likely to be quickly stabilized or initial investigations indicate possible long-term involvement, the company officer should consider one of the following actions: (1) Pass command to another company not operating in the hazard zone. (2) Assign command of his/her immediate company to a company member or another company officer and establish a Fixed Command. 4.5 Mobile Command Example: “Columbus Fire, Engine 30 is on the scene of a large commercial building. Nothing showing. Lt. Smith has mobile command. Engine 30 will be investigating. Engine 34 complete a 360 upon arrival”. Section 5 Passing Command 5.1 Passing command should be considered at incidents requiring immediate action of the first arriving officer in order to stabilize the situation, and where, due to staffing and/or experience factors, the company officer feels that it is necessary for him/her to initially utilize a mobile command operation and accompany his/her crew in their initial efforts. 5.1.1 Passing command should be considered for situations where the actions of the initial officer or member are likely to improve the outcomes of the incident priorities of life safety or incident stabilization. Columbus Division of Fire | SOP 01-03-04 Rev. 04/04/2016 2 of 3 5.1.2 When an Engine and Ladder arrive at the same time and the initial incident commander feels that passing command is appropriate, command may be passed to the next arriving officer or member. 5.2 Passing command should not to be confused with TRANSFERRING command (SOP 01-03-05). Command is PASSED only when the situation requires the immediate active participation of the first member or officer on the scene which prohibits them from establishing a fixed command post. 5.3 When command is passed, the FAO shall notify the next arriving company that command has been passed to them. 5.4 Command can be passed only once. 5.5 The first arriving officer or member retains responsibility for all of the duties of incident command until the next arriving officer or member formally assumes command. 5.5.1 The next arriving officer will obtain a C.A.N. Report from the initial arriving company, establish a fixed command, and give a Progress Report. 5.6 Passing Command Example: “Columbus Fire, Engine 30 is on the scene of a two story, single family, wood frame with fire showing on the Alpha side, second story. Make this a working fire. We will be attacking with 1 3/4”. I am passing command to the next arriving company”. 5.6.1 The dispatcher will repeat this message and notify the next arriving company that command has been passed to them. Columbus Division of Fire | SOP 01-03-04 Rev. 04/04/2016 3 of 3 Standard Operating Procedures Subject: Transfer of Command S.O.P. Number 01-03-05 Approved: Vol-CH-Cat.Sub Fire Chief Issued: 07/07/1998 Reviewed: 03/21/2016 Revised: 04/04/2016 Section 1 Purpose 1.1 The purpose of this procedure is to describe the transfer of command procedure at any incident. Section 2 General 2.1 Should any higher ranking officer decide to officially assume command of the incident, the officer shall locate the Command Post and follow the transfer of command procedure. 2.2 When the first Captain arrives on the scene and it is apparent that it will be some time before the arrival of the Battalion Chief, the Captain should assume a Fixed Command, obtain available information, and inform the fire alarm dispatcher. 2.2.1 It may be advisable for the Captain to check via radio with the responding Battalion Chief. If the Battalion Chief expects to arrive within a reasonable period of time, the Captain may choose not to assume command. Section 3 Transfer of Command Procedure 3.1 When a transfer of command takes place at the Command Post or via radio, the officer being relieved will brief the officer assuming command. 3.1.1 The transfer of command brief will include the following: 1) Incident priorities and strategic goals. 2) Tactical objectives that have been assigned and that need to be assigned. 3) Tactical objectives that have been achieved. 3.2 After the transfer of command procedure has taken place, the officer assuming command shall transmit a ‘Status Report’ via the radio on the primary fireground talkgroup or the ‘ALL-CALL’ (ATG) talkgroup if more than one talkgroup is being used. 3.2.1 A status report shall include the current fireground strategy, the incident action plan, and the name and rank of the new Incident Commander. Columbus Division of Fire | SOP 01-03-05 Rev. 04/04/2016 1 of 2 3.2.1.1 Status Report Example: “Columbus Fire from Battalion 2, Chief Smith will be assuming command of the Polaris Parkway incident, we are currently in the offensive strategy with interior operations working to contain the fire and obtain an ‘All Clear’ on both the fire building and the Bravo 1 exposure”. 3.3 Following the transfer of command, the officer assuming command will reassign the former incident commander to a new role. Section 4 Responding with Suburban Fire Departments 4.1 The intent of this section is to clarify command expectations on mutual aid incidents. 4.2 When suburban departments respond into the City of Columbus, Columbus fire officers below the rank of battalion chief, have the option to take or maintain command of all incidents. 4.3 A Columbus Fire Battalion Chief shall take command of all working incidents within the city limits. 4.4 Initial Command by a Columbus Fire Officer 4.4.1 If Command is Mobile, the Columbus Officer should transfer command to the Suburban Battalion Officer. 4.4.2 A Columbus Fire Officer choosing to not transfer command to a Suburban Battalion Officer shall establish and maintain a Fixed Command. 4.5 Initial Command by a Suburban Fire Officer 4.5.1 If Command is Mobile, the Columbus officer should consider establishing a Fixed Command Post. 4.5.2 When a Columbus officer chooses to take command he/she shall establish a Fixed Command. Columbus Division of Fire | SOP 01-03-05 Rev. 04/04/2016 2 of 2 Standard Operating Procedures Subject: Scene Designations Approved: S.O.P. Number 01-03-06 Vol-CH-Cat.Sub Acting Fire Chief Issued: 07/01/1998 Reviewed: 12/01/2018 Revised: 01/01/2019 Section 1 Purpose 1.1 The purpose of this procedure is to assist members in dividing the incident scene into manageable parts and to assign the designations for those areas. Section 2 General 2.1 To insure uniformity there needs to be a standard means of dividing an incident. The following designation system will be used whenever it is necessary to divide an incident. Section 3 Dividing the Incident 3.1 Sides and Exposures 3.1.1 Each side of the fire building or incident area shall be designated as either Alpha, Bravo, Charlie, or Delta. 3.1.2 Unless otherwise designated, the address side of the building shall be referred to as Alpha side, with the designation moving clockwise around the structure. 3.1.3 Building exposures should be identified with a similar system. For example, an exposure to the right of the Alpha side of the incident would be designated as the “Delta Exposure”. 3.1.4 Exposure Designations Charlie Side Delta Side Bravo Side Bravo 2 Exposure Bravo 1 Exposure Alpha Side Fire Incident Delta 1 Exposure IC Columbus Division of Fire | S.O.P. 01-03-06 Rev. 01/01/2019 1 of 2 3.2 Floors 3.2.1 When operating in a multistory structure, it may be necessary to designate geographic locations by floor. This system of geographic designation uses the floor number to identify a Division. For Example, the first floor would be designated as Division 1, the second floor Division 2 etc. (see figure 1 on page 2). 3.3 Scene Designations Division 4 Division 3 Division 2 Division 1 Columbus Division of Fire | S.O.P. 01-03-06 Rev. 01/01/2019 2 of 2