Columbus Division of Fire SOP Manual PDF

COLUMBUS DIVISION OF FIRE DEPARTMENT OF PUBLIC SAFETY STANDARD OPERATING PROCEDURES MANUAL Adapted Version for the 2025 CSC Fire Promotional Exams Revised 4/5/2024 This page left blank for 2 sided printing ...

COLUMBUS DIVISION OF FIRE DEPARTMENT OF PUBLIC SAFETY STANDARD OPERATING PROCEDURES MANUAL Adapted Version for the 2025 CSC Fire Promotional Exams Revised 4/5/2024 This page left blank for 2 sided printing  Alphabetized SOP Index TITLE SECTION SUBJECT REVISED “B” Assignment Response 02-03-03 RESPONSE TACTICS 3/1/2006 “H” Assignment Response 02-03-04 RESPONSE TACTICS 3/10/2004 360 Size-Up 01-03-17 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Air Scrubber 06-07-01 3/01/2021 Accountability 02-01-01 SCENE SAFETY 3/22/2016 Action-Response to Resistance / Aggression 03-07-05 FIRE INVESTIGATIONS UNIT 8/15/2020 Active Violence Incident (AVI) Response 03-04-05 RESPONSE TACTICS 5/13/2021 Additional Resources 01-03-29 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Air Management for SCBA use 01-04-08 PERSONAL EQUIPMENT PPE 5/23/2016 Air-Purifying Respirator (APR) Use 01-04-05 PERSONAL EQUIPMENT PPE 3/31/2017 All Clear 01-03-21 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 ALS Response 02-03-05 RESPONSE TACTICS 7/1/1998 Area Command 03-06-02 RESPONSE TACTICS 2/26/2017 Apparatus OOS Criteria 06-01-02 MAINTENANCE 4/10/2009 Apparatus Specifications 04-01-02 EQUIPMENT 5/4/1999 Apparatus Tag Out Procedures 06-01-03 MAINTENANCE 8/27/2019 AWOL 04-03-20 PERSONNEL 7/14/2023 Backing of Division Vehicles 01-01-02 APPARATUS 4/3/2000 Basement Fire 02-03-03 RESPONSE TACTICS 5/2/2016 BDS Response at 2323 Citygate Dr. 03-03-06 HAZMAT 1/1/2007 Bed Bug Procedures 04-06-01 ADMINISTRATIVE 3/15/2023 BLS Response 02-03-06 RESPONSE TACTICS 7/1/1998 Bomb Squad Transportation of Explosives 03-01-08 BOMB SQUAD (RESTRICTED) 7/1/1998 Bomb Squad Administration 03-01-02 BOMB SQUAD 4/1/2017 Bomb Squad Disposal Operations 03-01-07 BOMB SQUAD (RESTRICTED) 7/1/1998 Bomb Squad Essential Equipment Use 03-01-05 BOMB SQUAD (RESTRICTED) 7/1/1998 Bomb Squad Operations 03-01-06 BOMB SQUAD (RESTRICTED) 7/1/1998 Bomb Squad Operations – 03-01-01 BOMB SQUAD Bomb Squad Reporting Procedures 03-01-09 BOMB SQUAD (RESTRICTED) 7/1/1998 Bomb Squad Response 02-03-08 RESPONSE TACTICS 7/1/1998 Bomb Squad Response Request 03-01-11 BOMB SQUAD 8/10/2020 Bomb Squad Safety 03-01-03 BOMB SQUAD (RESTRICTED) 7/1/1998 Bomb Threats 03-01-04 BOMB SQUAD (RESTRICTED) 7/1/1998 Branches of ICS 01-03-08 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Carbon Monoxide Alarms 02-03-09 RESPONSE TACTICS 7/1/1998 CFD Bio Watch Responsibilities 03-02-01 HAZMAT 4/1/2011 CFD Rider Policy 04-04-02 ADMINISTRATION 8/28/2014 CFD Threat Level Staging 03-02-02 4/1/2011 Chain of Command 01-03-02 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 City Fire Code Appeal Process 08-03-03 FIRE PREVENTION 2/14/2024 Civil Disturbance/Task Force 03-06-01 TASK FORCE 11/30/2016 Code One 01-03-30 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Command Responsibilities 01-03-03 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Command Staff Positions 01-03-09 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Confined Space Rescue/Special Operations 03-05-04 RESCUE 8/10/2020 CPD/CFD MOU 03-07-08 FIRE INVESTIGATIONS UNIT 8/15/2020 Critical Incident Identification and Management 04-03-03 PERSONNEL 4/3/2000 Critical Incident Stress Management Team 04-03-04 PERSONNEL 1/15/2013 Death or Serious Injury of Employee 04-03-02 PERSONNEL 3/10/2004 Defensive Operations 01-03-24 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Department of Health Notification 01-05-05 ADMINISTRATIVE 2/8/2024 Digital Media 04-05-08 PERSONNEL 2/26/2017  Alphabetized SOP Index TITLE SECTION SUBJECT REVISED Discharged Firearms 03-07-04 FIRE INVESTIGATIONS UNIT 8/15/2020 Discipline Hearing – Serving Papers 04-03-05 PERSONNEL 2/7/2000 Dive and Rescue Team (DART) 03-08-01 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 Dive Gear 03-08-02 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 Dive Responses 03-08-05 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 Dive Safety 03-08-03 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 Dive Supervisor Responsibilities 03-08-04 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 Division Staff Vehicles 06-02-03 APPARATUS 3/1/2009 Divisions and Groups 01-03-07 INCIDENT COMMAND SYSTEM (ICS) 1/1/2019 Driver’s License Suspension 04-03-06 PERSONNEL 11/15/2022 Driving 01-01-01 APPARATUS 11/15/2022 Dumpster Fires 02-03-10 RESPONSE TACTICS 7/1/1998 Electrical Emergencies 02-03-17 RESPONSE TACTICS 1/31/2017 Elevator Rescue Operations 02-03-19 RESPONSE TACTICS 12/7/2022 Elevator Use During Fires 02-03-11 RESPONSE TACTICS 7/1/1998 Emergency Assistance 01-02-05 SCENE SAFETY 3/25/2022 Emergency Evacuation 02-01-04 SCENE SAFETY 5/2/2016 Emergency Services Smoke Alarm Installation 08-05-01 PUBLIC OUTREACH 5/29/2019 EMS Staffing 04-03-19 PERSONNEL 3/6/2017 Establishing Command 01-03-04 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Evidence Room Procedures 03-07-01 FIRE INVESTIGATIONS UNIT 3/1/2007 Exposure Fires 01-06-03 INCIDENT MANAGEMENT REPORTING SYSTEM 10/1/2014 Extrication and Technical Rescue 03-05-02 RESCUE 6/26/2001 False Alarm Reporting and Notification 08-02-01 RESPONSE TACTICS 12/1/2017 Family Crisis Notification 04-03-01 PERSONNEL 3/10/2004 Finance 01-03-14 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Fire "Alarm" Assignment 02-02-04 STAGING 7/31/2013 Fire Alarm Investigation 02-03-23 RESPONSE TACTICS 2/1/2024 Fire Control Strategy Factors 01-03-22 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Fireground Communication 01-02-02 COMMUNICATIONS 1/1/2019 Fire, Bomb, Hazmat Investigations 01-03-03.01 INCIDENT COMMAND SYSTEM (ICS) 10/28/2019 Fire Investigator Law Enforcement Authority 03-07-03 FIRE INVESTIGATIONS UNIT 8/15/2020 Fire Station Emergency Smoke Alarm Box 08-05-01 PUBIC OUTREACH 3/1/2016 Fire Stream Management 01-03-26 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Fire Watch Storm 02-03-22 RESPONSE TACTICS 12/18/2023 Firearms Regulations 03-07-06 FIRE INVESTIGATIONS UNIT 8/15/2020 Firehouse Software Rescue Reporting 01-06-05 INCIDENT MANAGEMENT REPORTING 12/30/2021 Firehouse Software Support 01-06-02 INCIDENT MANAGEMENT REPORTING SYSTEM 10/1/2014 Foam Trailer 06-02-04 APPARATUS 10/1/2015 Forcible Entry 01-03-28 INCIDENT COMMAND SYSTEM (ICS) 12/14/2020 Fuel Spills – Small HazMat Spills 02-03-12 RESPONSE TACTICS 3/8/2021 Funeral Procedures 04-03-12 PERSONNEL 12/15/2022 Gas Leak Response 02-03-13 RESPONSE TACTICS 7/1/1998 General Staff Positions 01-03-10 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 HazMat - EMS at HazMat Incidents 03-03-04 HAZMAT 7/1/1998 HazMat / Bomb Squad Medical Evaluation 03-03-01 HAZMAT 7/6/2005 HazMat Action Plan 03-03-02 HAZMAT 3/1/2007 HazMat Mutual Aid Response 03-03-07 HAZMAT 8/1/2008 HazMat Staffing 03-03-03 HAZMAT 3/1/2007 High Pressure Hose Testing 06-04-04 HOSE AND FITTINGS 5/20/2021 Hose Inventory 06-04-02 HOSE AND FITTINGS 4/28/2021  Alphabetized SOP Index TITLE SECTION SUBJECT REVISED Hose Repair / Replacement 06-04-01 HOSE AND FITTINGS 4/28/2021 Hose Test Procedures 06-04-03 HOSE AND FITTINGS 4/28/2021 Hot / Cold Weather Emergencies 04-03-08 PERSONNEL 1/18/2000 High-Rise Command Functions 02-03-04.01 RESPONSE TACTICS 3/22/2016 High-Rise Fire Attack Group 02-03-04.02 RESPONSE TACTICS 3/22/2016 High-Rise Initial Lobby Control / Systems Group 02-03-04.03 RESPONSE TACTICS 3/22/2016 High-Rise Upper Search & Evacuation (USE) Group 02-03-04.04 RESPONSE TACTICS 3/22/2016 High-Rise Resource Group 02-03-04.05 RESPONSE TACTICS 3/22/2016 High-Rise Response 02-03-04 RESPONSE TACTICS 3/22/2016 High-Rise Stairwell Support Group 02-03-04.06 RESPONSE TACTICS 3/22/2016 High-Rise Rehabilitation Group 02-03-04.08 RESPONSE TACTICS 3/22/2016 High-Rise Medical Group 02-03-04.09 RESPONSE TACTICS 3/22/2016 High-Rise Ventilation Group 02-03-04.07 RESPONSE TACTICS 3/22/2016 Hydrant Flowing Response 01-05-03 RESPONSE TACTICS 4/1/2011 ICS Purpose and Background 01-03-01 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Incident Priorities 01-03-19 RESPONSE TACTICS 5/2/2016 Incidents Reports 01-06-01 INCIDENT MANAGEMENT REPORTING SYSTEM 3/1/2024 Infant Save Haven 04-04-01 PUBLIC 10/30/2002 Installation of the McGard Hydrant Lock 04-01-05 EQUIPMENT 5/1/2006 Lactation Policy 04-03-22 PERSONNEL 8/28/2023 Lockout/Tagout Procedures 02-03-21 RESPONSE TACTICS 12/7/2022 Logistics 01-03-13 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Monthly Mileage Reimbursement 04-03-23 PERSONNEL 2/8/2024 Multi Agency Smoke Alarm Drives 08-05-03 PUBLIC OUTREACH 8/10/2020 Mutual Aid 01-06-04 INCIDENT MANAGEMENT REPORTING SYSTEM 10/1/2014 Offensive Operations 01-03-23 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 On-Scene Radio Report 01-02-03 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Operations 01-03-11 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 P-400 Multi Gas Meter 01-07-03 TECHNOLOGY BASE EQUIPMENT 6/15/2014 Paramedic OPT-In 04-03-15 PERSONNEL 2/26/2017 Personal Alert Safety System (PASS) 01-04-09 SCENE SAFETY 5/23/2016 Personal Protective Equipment 01-04-01 PERSONAL EQUIPMENT PPE 3/25/2022 Personal Protective Equipment at Water Rescues 01-04-06 PERSONAL EQUIPMENT PPE 5/23/2016 Planning 01-03-11 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Police and Fire Joint Operational Incidents 03-04-02 POLICE AND FIRE 5/25/2013 Police and Fire Radio Talkgroup 03-04-04 POLICE AND FIRE 2/1/1999 Police and Fire Ranks 03-04-01 POLICE AND FIRE 2/1/1999 Police and Fire Roles at Disaster Scenes 03-04-03 POLICE AND FIRE 11/30/2001 Police Radio Talkgroups 03-04-04.01 POLICE AND FIRE 1/1/2009 Post Blast Investigation 03-01-10 BOMB SQUAD 7/1/1998 Post Incident Safety Review 01-05-01 SCENE CONTROL 11/8/2000 Product Evaluation and Field Test 04-01-03 EQUIPMENT 5/4/1999 Property Conservation 01-03-25 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Protective Clothing Care and Maintenance 01-04-07 PERSONAL EQUIPMENT PPE 3/25/2022 Radiation Monitor 03-03-05 HAZMAT 4/1/2011 Radio Procedures 01-02-01 COMMUNICATIONS 4/4/2016 Radiological Emergency 03-03-09 HAZMAT 1/15/2009 Rapid Key Entry System 02-03-18 RESPONSE TACTICS 12/2/2019 Red Cross Service Request 01-05-04 SCENE CONTROL 11/1/2009 Rehab Functions 02-01-08 SCENE SAFETY 3/1/2006 Representation by City Attorney 03-07-07 FIRE INVESTIGATIONS UNIT 8/15/2020 Rescue Factors 01-03-20 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Rescue Support Units 01-01-06 APPARATUS 1/22/2022  Alphabetized SOP Index TITLE SECTION SUBJECT REVISED Rescue Technician Status 03-05-01 RESCUE 6/26/2001 Research and Development Committees 04-01-01 EQUIPMENT 4/4/2023 Reserve Apparatus Inventory 06-02-02 APPARATUS 3/1/2009 Residence Fires - Single / Double 02-03-01 RESPONSE TACTICS 3/10/2004 Respiratory Protection Requirements 01-04-02 PERSONAL EQUIPMENT PPE 5/23/2016 RIT - Rapid Intervention Teams 02-01-03 SCENE SAFETY 5/2/2016 Rope Rescue 03-05-05 RESPONSE TACTICS 2/03/2021 SCBA Inspection and Care 01-04-04 PERSONAL EQUIPMENT PPE 5/23/2016 SCBA Removal 01-04-03 PERSONAL EQUIPMENT PPE 5/23/2016 Scene Designations 01-03-06 INCIDENT COMMAND SYSTEM (ICS) 1/1/2019 Scene Security and Transfer to CPD 03-08-06 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 School Fire Drills 08-03-01 FIRE PREVENTION 8/16/2019 Separation from Service 04-03-14 PERSONNEL 4/24/2023 Significant Training 05-02-01 FACILITIES 8/23/2013 Size-Up Factors 01-03-18 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Social Media 04-05-07 PERSONNEL 2/26/2017 SOP - Definition 04-02-01 MANUALS 10/23/2003 SOP - Format 04-02-02 MANUALS 2/09/2021 SOP – Manual Index and Distribution 04-02-03 MANUALS 10/23/2003 SOP - Proposals 04-02-04 MANUALS 10/23/2003 SOP – Revisions and Reviews 04-02-05 MANUALS 10/23/2003 Special Diving Operations 03-08-07 DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 Specialized Training Selection 04-03-18 PERSONNEL 3/1/2017 Staff Cell Phones and Pagers 04-01-04 EQUIPMENT 3/7/2006 Staging Area Manager 02-02-06 STAGING 3/22/2016 Staging Level II 02-02-05 STAGING 3/22/2016 Staging Levels 02-02-01 STAGING 3/22/2016 Station Tasks 04-03-17 PERSONNEL 8/10/2020 Structural Damage 01-05-02 SCENE CONTROL 7/1/2020 Subpoena/Summons Procedures 04-03-16 PERSONNEL 11/1/2015 TeleStaff / Trades 04-05-06 TECHNOLOGIES 4/10/2009 TeleStaff Calendar 04-05-02 TECHNOLOGIES 4/10/2009 TeleStaff Log in 04-05-03 TECHNOLOGIES 4/10/2009 TeleStaff Phone Procedures 04-05-04 TECHNOLOGIES 4/10/2009 TeleStaff Reports 04-05-05 TECHNOLOGIES 4/10/2009 Thermal Image Camera Accountability and Tactics 01-07-02 TECHNOLOGY BASE EQUIPMENT 3/1/2006 TIC Operation and Maintenance 01-07-01 TECHNOLOGY BASE EQUIPMENT 3/13/2003 Tunnel Rescue Procedures 02-03-20 RESPONSE TACTICS 12/7/2022 Transfer of Command 01-03-05 INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 Transitional Fire Attack 02-03-02 RESPONSE TACTICS 5/2/2016 Transport Basic Opt-in 04-03-15.01 PERSONNEL 2/26/2015 Transport Vehicle Equipment Placement 06-02-01 APPARATUS 1/1/2009 Uniforms – All Personnel 04-03-10 PERSONNEL 8/19/2019 Uniforms – Uniform Replacement 04-03-11 PERSONNEL 8/19/2019 Urgent / Mayday Communications 01-02-04 SCENE SAFETY 1/1/2019 Utilization of City E-mail 04-03-13 PERSONNEL 1/1/2008 Vacant Structure Fire Response 02-03-16 RESPONSE TACTICS 5/1/2020 Vacant and Inaccessible Building 08-03-02 FIRE PREVENTION 4/11/2019 Vehicle Accident Response 02-03-14 RESPONSE TACTICS 6/12/2020 Vehicle Fire 02-03-15 RESPONSE TACTICS 7/1/1998  Alphabetized SOP Index TITLE SECTION SUBJECT REVISED Vehicle Maintenance Procedures 06-01-01 MAINTENANCE 2/1/2009 Ventilation Factors 01-03-27 INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 Venue/Event Command 03-06-03 RESPONSE TACTICS 2/26/2017 Water Rescue Incidents 02-03-07 RESPONSE TACTICS 3/12/2021 Water Web Procedures 04-01-06 EQUIPMENT 3/1/2008 WebStaff 04-05-01 TECHNOLOGIES 4/10/2009  Numerical SOP Index SECTION TITLE SUBJECT REVISED 01-01-01 Driving APPARATUS 11/15/2022 01-01-02 Backing of Division Vehicles APPARATUS 4/3/2000 01-01-06 Rescue Support Units APPARATUS 1/22/2023 01-02-01 Radio Procedures COMMUNICATIONS 4/4/2016 01-02-02 Fireground Communication COMMUNICATIONS 1/1/2019 01-02-03 On-Scene Radio Report INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-02-04 Urgent / Mayday Communications SCENE SAFETY 1/1/2019 01-02-05 Emergency Assistance SCENE SAFETY 3/25/2022 01-03-01 ICS Purpose and Background INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-02 Chain of Command INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-03 Command Responsibilities INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-03.01 Fire, Bomb, Hazmat Investigations INCIDENT COMMAND SYSTEM (ICS) 10/28/2019 01-03-04 Establishing Command INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-05 Transfer of Command INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-06 Scene Designations INCIDENT COMMAND SYSTEM (ICS) 1/1/2019 01-03-07 Divisions and Groups INCIDENT COMMAND SYSTEM (ICS) 1/1/2019 01-03-08 Branches of ICS INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-09 Command Staff Positions INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-10 General Staff Positions INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-11 Operations INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-11 Planning INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-13 Logistics INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-14 Finance INCIDENT COMMAND SYSTEM (ICS) 4/4/2016 01-03-17 360 Size-Up INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-18 Size-Up Factors INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-19 Incident Priorities RESPONSE TACTICS 5/2/2016 01-03-20 Rescue Factors INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-21 All Clear INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-22 Fire Control Strategy Factors INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-23 Offensive Operations INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-24 Defensive Operations INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-25 Property Conservation INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-26 Fire Stream Management INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-27 Ventilation Factors INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-28 Forcible Entry INCIDENT COMMAND SYSTEM (ICS) 12/14/2020 01-03-29 Additional Resources INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-03-30 Code One INCIDENT COMMAND SYSTEM (ICS) 5/2/2016 01-04-01 Personal Protective Equipment PERSONAL EQUIPMENT PPE 3/25/2022 01-04-02 Respiratory Protection Requirements PERSONAL EQUIPMENT PPE 5/23/2016 01-04-03 SCBA Removal PERSONAL EQUIPMENT PPE 5/23/2016 01-04-04 SCBA Inspection and Care PERSONAL EQUIPMENT PPE 5/23/2016 01-04-05 Air-Purifying Respirator (APR) Use PERSONAL EQUIPMENT PPE 3/31/2017 01-04-06 Personal Protective Equipment at Water Resc PERSONAL EQUIPMENT PPE 5/23/2016 01-04-07 Protective Clothing Care and Maintenance PERSONAL EQUIPMENT PPE 3/25/2022 01-04-08 Air Management for SCBA use PERSONAL EQUIPMENT PPE 5/23/2016 01-04-09 Personal Alert Safety System (PASS) SCENE SAFETY 5/23/2016 01-05-01 Post Incident Safety Review SCENE CONTROL 11/8/2000 01-05-02 Structural Damage SCENE CONTROL 7/1/2020 01-05-03 Hydrant Flowing Response RESPONSE TACTICS 4/1/2011 01-05-04 Red Cross Service Request SCENE CONTROL 11/1/2009 01-05-05 Department of Health Notification ADMINISTRATION 2/8/2024 01-06-01 Incidents Reports INCIDENT MANAGEMENT REPORTING 3/1/2024 01-06-02 Firehouse Software Support INCIDENT MANAGEMENT REPORTING 10/1/2014 01-06-03 Exposure Fires INCIDENT MANAGEMENT REPORTING 10/1/2014 01-06-04 Mutual Aid INCIDENT MANAGEMENT REPORTING 10/1/2014 01-06-05 Firehouse Software Rescue Reporting INCIDENT MANAGEMENT REPORTING 12/30/2021 01-07-01 TIC Operation and Maintenance TECHNOLOGY BASE EQUIPMENT 3/13/2003 01-07-02 Thermal Image Camera Accountability and T TECHNOLOGY BASE EQUIPMENT 3/1/2006 01-07-03 P-400 Multi Gas Meter TECHNOLOGY BASE EQUIPMENT 6/15/2014  Numerical SOP Index SECTION TITLE SUBJECT REVISED 02-01-01 Accountability SCENE SAFETY 3/22/2016 02-01-03 RIT – Rapid Intervention Teams SCENE SAFETY 5/2/2016 02-01-04 Emergency Evacuation SCENE SAFETY 5/2/2016 02-01-08 Rehab Functions SCENE SAFETY 3/1/2006 02-02-01 Staging Levels STAGING 3/22/2016 02-02-04 Fire “Alarm” Assignment STAGING 7/31/2013 02-02-05 Staging Level II STAGING 3/22/2016 02-02-06 Staging Area Manager STAGING 3/22/2016 02-03-01 Residence Fires – Single / Double RESPONSE TACTICS 3/10/2004 02-03-02 Transitional Fire Attack RESPONSE TACTICS 5/2/2016 02-03-03 “B” Assignment Response RESPONSE TACTICS 3/1/2006 02-03-03 Basement Fire RESPONSE TACTICS 5/2/2016 02-03-04 “H” Assignment Response RESPONSE TACTICS 3/10/2004 02-03-04 High-Rise Response RESPONSE TACTICS 3/22/2016 02-03-04.01 High-Rise Command Functions RESPONSE TACTICS 3/22/2016 02-03-04.02 High-Rise Fire Attack Group RESPONSE TACTICS 3/22/2016 02-03-04.03 High-Rise Initial Lobby Control / Systems Gr RESPONSE TACTICS 3/22/2016 02-03-04.04 High-Rise Upper Search & Evacuation (USE RESPONSE TACTICS 3/22/2016 02-03-04.05 High-Rise Resource Group RESPONSE TACTICS 3/22/2016 02-03-04.06 High-Rise Stairwell Support Group RESPONSE TACTICS 3/22/2016 02-03-04.07 High-Rise Ventilation Group RESPONSE TACTICS 3/22/2016 02-03-04.08 High-Rise Rehabilitation Group RESPONSE TACTICS 3/22/2016 02-03-04.09 High-Rise Medical Group RESPONSE TACTICS 3/22/2016 02-03-05 ALS Response RESPONSE TACTICS 7/1/1998 02-03-06 BLS Response RESPONSE TACTICS 7/1/1998 02-03-07 Water Rescue Incidents RESPONSE TACTICS 3/12/2021 02-03-08 Bomb Squad Response RESPONSE TACTICS 7/1/1998 02-03-09 Carbon Monoxide Alarms RESPONSE TACTICS 7/1/1998 02-03-10 Dumpster Fires RESPONSE TACTICS 7/1/1998 02-03-11 Elevator Use During Fires RESPONSE TACTICS 7/1/1998 02-03-12 Fuel Spills – Small HazMat Spills RESPONSE TACTICS 3/8/2021 02-03-13 Gas Leak Response RESPONSE TACTICS 7/1/1998 02-03-14 Vehicle Accident Response RESPONSE TACTICS 6/12/2020 02-03-15 Vehicle Fire RESPONSE TACTICS 7/1/1998 02-03-16 Vacant Structure Fire Response RESPONSE TACTICS 5/1/2020 02-03-17 Electrical Emergencies RESPONSE TACTICS 1/31/2017 02-03-18 Rapid Key Entry System RESPONSE TACTICS 10/2/2019 02-03-19 Elevator Rescue Operations RESPONSE TACTICS 12/7/2022 02-03-20 Tunnel Rescue Procedures RESPONSE TACTICS 12/7/2022 02-03-21 Lockout/Tagout Procedures RESPONSE TACTICS 12/7/2022 02-03-22 Fire Alarm Storm RESPONSE TACTICS 12/18/2023 02-03-23 Fire Alarm Investigation RESPONSE TACTICS 2/1/2024 03-01-01 Bomb Squad Operations – BOMB SQUAD 03-01-02 Bomb Squad Administration BOMB SQUAD 4/1/2017 03-01-03 Bomb Squad Safety BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-04 Bomb Threats BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-05 Bomb Squad Essential Equipment Use BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-06 Bomb Squad Operations BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-07 Bomb Squad Disposal Operations BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-08 Bomb Squad Transportation of Explosives BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-09 Bomb Squad Reporting Procedures BOMB SQUAD (RESTRICTED) 7/1/1998 03-01-10 Post Blast Investigation BOMB SQUAD 7/1/1998 03-01-11 Bomb Squad Response Request BOMB SQUAD 8/10/2020 03-02-01 CFD Bio Watch Responsibilities 4/1/2011 03-02-02 CFD Threat Level Staging 4/1/2011 03-03-01 HazMat / Bomb Squad Medical Evaluation HAZMAT 7/6/2005  Numerical SOP Index SECTION TITLE SUBJECT REVISED 03-03-02 HazMat Action Plan HAZMAT 3/1/2007 03-03-03 HazMat Staffing HAZMAT 3/1/2007 03-03-04 HazMat - EMS at HazMat Incidents HAZMAT 7/1/1998 03-03-05 Radiation Monitor HAZMAT 4/1/2011 03-03-06 BDS Response at 2323 Citygate Dr. HAZMAT 1/1/2007 03-03-07 HazMat Mutual Aid Response HAZMAT 8/1/2008 03-03-09 Radiological Emergency HAZMAT 1/15/2009 03-04-01 Police and Fire Ranks POLICE AND FIRE 2/1/1999 03-04-02 Police and Fire Joint Operational Incidents POLICE AND FIRE 5/25/2013 03-04-03 Police and Fire Roles at Disaster Scenes POLICE AND FIRE 11/30/2001 03-04-04 Police and Fire Radio Talkgroup POLICE AND FIRE 2/1/1999 03-04-04.01 Police Radio Talkgroups POLICE AND FIRE 1/1/2009 03-04-05 Active Violence Incident (AVI) Response RESPONSE TACTICS 5/13/2021 03-05-01 Rescue Technician Status RESCUE 6/26/2001 03-05-02 Extrication and Technical Rescue RESCUE 6/26/2001 03-05-04 Confined Space Rescue/Special Operations RESCUE 8/10/2020 03-05-05 Rope Rescue RESCUE 2/03/2021 03-06-01 Civil Disturbance/Task Force Operations TASK FORCE 11/30/2016 03-06-02 Area Command RESPONSE TACTICS 2/26/2017 03-06-03 Venvue/Event Command RESPONSE TACTICS 2/26/2017 03-07-01 Evidence Room Procedures FIRE INVESTIGATIONS UNIT 3/1/2007 03-07-03 Fire Investigator Law Enforcement Authority FIRE INVESTIGATIONS UNIT 8/15/2020 03-07-04 Discharged Firearms FIRE INVESTIGATIONS UNIT 8/15/2020 03-07-05 Action-Response to Resistance / Aggression FIRE INVESTIGATIONS UNIT 8/15/2020 03-07-06 Firearms Regulations FIRE INVESTIGATIONS UNIT 8/15/2020 03-06-07 Representation by City Attorney FIRE INVESTIGATIONS UNIT 8/15/2020 03-06-08 CPD/CFD MOU FIRE INVESTIGATIONS UNIT 8/15/2020 03-08-01 Dive and Rescue Team (DART) DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 03-08-02 Dive Gear DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 03-08-03 Dive Safety DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 03-08-04 Dive Supervisor Responsibilities DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 03-08-05 Dive Responses DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 03-08-06 Scene Security and Transfer to CPD DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 03-08-07 Special Diving Operations DIVE AND RESCUE TEAM (D.A.R.T.) 12/1/2009 04-01-01 Research and Development Committees EQUIPMENT 4/4/2023 04-01-02 Apparatus Specifications EQUIPMENT 5/4/1999 04-01-03 Product Evaluation and Field Test EQUIPMENT 5/4/1999 04-01-04 Staff Cell Phones and Pagers EQUIPMENT 3/7/2006 04-01-05 Installation of the McGard Hydrant Lock EQUIPMENT 5/1/2006 04-01-06 Water Web Procedures EQUIPMENT 3/1/2008 04-02-01 SOP - Definition MANUALS 10/23/2003 04-02-02 SOP - Format MANUALS 02/09/2021 04-02-03 SOP – Manual Index and Distribution MANUALS 10/23/2003 04-02-04 SOP - Proposals MANUALS 10/23/2003 04-02-05 SOP – Revisions and Reviews MANUALS 10/23/2003 04-03-01 Family Crisis Notification PERSONNEL 3/10/2004 04-03-02 Death or Serious Injury of Employee PERSONNEL 3/10/2004 04-03-03 Critical Incident Identification and Mgt. PERSONNEL 4/3/2000 04-03-04 Critical Incident Stress Management Team PERSONNEL 1/15/2013 04-03-05 Discipline Hearing – Serving Papers PERSONNEL 2/7/2000 04-03-06 Driver’s License Suspension PERSONNEL 11/15/2022 04-03-07 Honor Guard Travel PERSONNEL 5/12/2000 04-03-08 Hot / Cold Weather Emergencies PERSONNEL 1/18/2000 04-03-10 Uniforms – Platoon Personnel PERSONNEL 8/19/2019 04-03-11 Uniforms - Replacements PERSONNEL 8/19/2019 04-03-12 Funeral Procedures PERSONNEL 12/15/2022  Numerical SOP Index SECTION TITLE SUBJECT REVISED 04-03-13 Utilization of City E-mail PERSONNEL 1/1/2008 04-03-14 Separation from Service PERSONNEL 4/24/2023 04-03-15 Paramedic OPT-In PERSONNEL 2/26/2017 04-03-15.01 Transport Basic Opt-in PERSONNEL 2/26/2015 04-03-16 Subpoena/Summons Procedures PERSONNEL 11/1/2015 04-03-17 Station Tasks PERSONNEL 8/10/2020 04-03-18 Specialized Training Selection PERSONNEL 3/1/2017 04-03-19 EMS Staffing PERSONNEL 3/6/2017 04-03-20 AWOL PERSONNEL 7/14/2023 04-03-22 Lactation Policy PERSONNEL 8/28/2023 04-03-23 Monthly Mileage Reimbursement PERSONNEL 2/8/2024 04-04-01 Infant Save Haven PUBLIC 10/30/2002 04-04-02 CFD Rider Policy ADMINISTRATION 8/28/2014 04-05-01 WebStaff TECHNOLOGIES 4/10/2009 04-05-02 TeleStaff Calendar TECHNOLOGIES 4/10/2009 04-05-03 TeleStaff Log in TECHNOLOGIES 4/10/2009 04-05-04 TeleStaff Phone Procedures TECHNOLOGIES 4/10/2009 04-05-05 TeleStaff Reports TECHNOLOGIES 4/10/2009 04-05-06 TeleStaff / Trades TECHNOLOGIES 4/10/2009 04-05-07 Social Media TECHNOLOGIES 2/26/2017 04-05-08 Digital Media TECHNOLOGIES 2/26/2017 04-06-01 Bed Bug Procedures ADMINISTRATIVE PROTOCOL 3/15/2023 05-01-02 State Certification Renewal for Fire Fighter II CERTIFICATION 1/1/2009 05-01-03 State Certification for Fire Safety Inspector CERTIFICATION 1/1/2009 05-01-04 Audit of Fire and EMS Certifications CERTIFICATION 1/4/2016 05-01-05 Certifications - Change in Status CERTIFICATION 8/15/2016 05-02-01 Significant Training FACILITIES 8/23/2013 06-01-01 Vehicle Maintenance Procedures MAINTENANCE 2/1/2009 06-01-02 Apparatus OOS Criteria MAINTENANCE 4/10/2009 06-01-03 Apparatus Tag Out Procedures MAINTENANCE 8/27/2019 06-02-01 Transport Vehicle Equipment Placement APPARATUS 1/1/2009 06-02-02 Reserve Apparatus Inventory APPARATUS 3/1/2009 06-02-03 Division Staff Vehicles APPARATUS 3/1/2009 06-02-04 Foam Trailer APPARATUS 10/1/2015 06-04-01 Hose Repair / Replacement HOSE AND FITTINGS 4/28/2021 06-04-02 Hose Inventory HOSE AND FITTINGS 4/28/2021 06-04-03 Hose Test Procedures HOSE AND FITTINGS 4/28/2021 06-04-04 High Pressure Hose Testing HOSE AND FITTINGS 5/20/2021 06-07-01 Air Scrubber 3/1/2021 08-02-01 False Alarm Reporting and Notification CODE ENFORCEMENT 12/1/2017 08-03-01 School Fire Drills FIRE PREVENTION 8/16/2019 08-03-02 Vacant and or Inaccessible Structures FIRE PREVENTION 4/11/2019 08-03-03 City Fire Code Appeal Process FIRE PREVENTION 2/14/2024 08-05-01 ES Smoke Alarm Installation PUBLIC OUTREACH 5/29/2019 08-05-03 Multi Agency Smoke Alarm Drives PUBLIC OUTREACH 8/10/2020  COLUMBUS DIVISION OF FIRE STANDARD OPERATION PROCEDURES TABLE OF CONTENTS VOLUME 1 EMERGERGENCY SERVICES - SAFETY AND COMMAND SECTION TITLE REVISED 01-01 APPARATUS 01-01-01 Driving 11/15/2022 01-01-02 Backing of Division Vehicles 4/3/2000 01-01-06 Rescue Support Units 1/22/2022 01-02 COMMUNICATION 01-02-01 Radio Procedures 4/4/2016 01-02-02 Fireground Communication 1/1/2019 01-02-03 On-Scene Radio Report 4/4/2016 01-02-04 Urgent/Mayday Communication 1/1/2019 01-02-05 Emergency Assistance 1/1/2019 01-03 INCIDENT COMMAND SYSTEM (ICS) 01-03-01 ICSPurpose and Background 4/4/2016 01-03-02 Chain of Command 4/4/2016 01-03-03 Command Responsibilities 4/4/2016 01-03-03.01 Fire, Bomb, Hazmat Investigations 10/28/2019 01-03-04 Establishing Command 4/4/2016 01-03-05 Transfer of Command 4/4/2016 01-03-06 Scene Designations 1/1/2019 01-03-07 Divisions and Groups 1/1/2019 01-03-08 Branches of ICS 4/4/2016 01-03-09 Command Staff Positions 4/4/2016 01-03-10 General Staff Positions 4/4/2016 01-03-11 Operations 4/4/2016 01-03-12 Planning 4/4/2016 01-03-13 Logistics 4/4/2016 01-03-14 Finance 4/4/2016 01-03-17 360 Size-Up 5/2/2016 01-03-18 Size-Up Factors 5/2/2016 01-03-19 Incident Priorities 5/2/2016 01-03-20 Rescue Factors 5/2/2016 01-03-21 All Clear 5/2/2016 01-03-22 Fire Control StrategyFactors 5/2/2016 01-03-23 Offensive Operations 5/2/2016 01-03-24 Defensive Operations 5/2/2016 01-03-25 PropertyConservation 5/2/2016 01-03-26 Fire Stream Management 5/2/2016 01-03-27 Ventilation Factors 5/2/2016 01-03-28 Forcible Entry 12/14/2021 01-03-29 Additional Resources 5/2/2016 01-03-30 Code One 5/2/2016 01-04 PERSONAL PROTECTIVE EQUIPMENT (PPE) 01-04-01 PPE Use 5/23/2016 01-04-02 Respiratory Protection Requirements 5/23/2016 01-04-03 SCBA Removal 5/23/2016 01-04-04 SCBA Inspection and Care 5/23/2016 01-04-05 Air-Purifying Respirator (APR) Use 3/31/2017 01-04-06 PPE at Water Rescues 5/23/2016 01-04-07 Protective Clothing Care and Maintenance 4/11/2019 01-04-08 Air Management for SCBA use 5/23/2016 01-04-09 Personal Alert Safety System (PASS) 5/23/2016 01-05 SCENE CONTROL 01-05-01 Post Incident Safety Review 11/8/2000 01-05-02 Structural Damage 7/1/2000 01-05-03 Hydrant Flowing Response 4/1/2011 01-05-04 Red Cross Service Request 11/1/2009 01-05-05 Department of Health Notification 2/8/2024 01-06 INCIDENT MANAGEMENT REPORTING SYSTEM 01-06-01 Incidents Reports 3/1/2024 01-06-02 Firehouse Software Support 10/1/2014 01-06-03 Exposure Fires 10/1/2014 01-06-04 Mutual Aid 10/1/2014 01-06-05 Firehouse Software Rescue Reporting 12/30/2021 01-07 TECHNOLOGY BASED EQUIPMENT 01-07-01 TIC Operation and Maintenance 3/13/2003 01-07-02 Thermal Image Camera Accountability and Tactics 3/1/2006 01-07-03 P-400 Multi Gas Meter 6/15/2014  Standard Operating Procedures Subject: Driving S.O.P. Number Approved 01-01-01 Vol-CH-Cat.Sub Fire Chief Issued: 08/15/1995 Reviewed: 03/25/2019 Revised: 11/15/2022 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 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. 11/15/2022 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 mayturn 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. 11/15/2022 2 of 2  Standard Operating Procedures Subject: Backing of Division Vehicles S.O.P. Number Approved 01-01-02 Vol-CH-Cat.Sub Fire Chief Page: 1 of 1 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! This page left blank for 2 sided printing  Standard Operating Procedures Subject: Rescue Support Units S.O.P. Number Approved 01-01-06 Vol-CH-Cat.Sub Acting Fire Chief Page: 1 of 1 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 in- charge 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. This page left blank for 2 sided printing  Standard Operating Procedures Subject: Radio Procedures S.O.P. Number Approved 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 topressing 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 Approved: 01-02-02 Acting Fire Chief Vol-CH-Cat.Sub 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 Section2.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 companies, unless otherwise assigned to a tactical talkgroup. (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-repeatedtalkgroup (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 multipleresources 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 02- 01-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-03- 08). 4.2 Progress Report. Progress reporting on the fireground relays critical information between incident command and companies assigned to an incident. Periodic progress reports provide important information to Incident Command, which is 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 N- Needs. (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 S.O.P. Number Approved 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-02-03 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-02-03 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-02-03 Rev. 04/04/2016 3 of 3 This page left blank for 2 sided printing  Standard Operating Procedures Subject: Urgent / Mayday Communications S.O.P. Number Approved: 01-02-04 Acting Fire Chief Vol-CH-Cat.Sub 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) Early sign of potential collapse. 2) Signs of possible backdraft or flashover. 3) Loss of water on attack lines. 4) Change from Offensive to Defensive Mode. 2.3 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  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, “Mayday- Mayday-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  “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  Standard Operating Procedures Subject: Emergency Assistance S.O.P. Number Approved: 01-02-05 Vol-CH-Cat.Sub Fire Chief Issued: 07/01/1998 Reviewed: 3-25-2022 Revised: 3-25-2022 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 01- 02-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 Following a request for “Emergency” assistance, you should give your company designation and location. 2.5 The FAO will then initiate the appropriate response. Columbus Division of Fire | S.O.P. 01-02-05 Rev. 03-25-2022 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 Unit's 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. 6) If available, members shall wear ballistic helmets and vests. 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. The tone repeats every 10 seconds. This prompts listeners to stop talking and only assigned companies will remain on the 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 a situation contained is given, 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. R e s p o n d i n g a p p a r a t u s will stage away from the scene and will be guided by the first in officer’s decisions. 6) If available, members shall wear ballistic helmet and vests. 7) 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. 03-25-2022 2 of 2  Standard Operating Procedures Subject: ICS Purpose and Background S.O.P. Number Approved 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  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  Standard Operating Procedures Subject: Chain of Command S.O.P. Number Approved 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) State any previous orders and the officer that issued that order. (2) Follow the judgment of the officer superseding the previous order. (3) 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 Approved 01-03-03 Fire Chief Vol-CH-Cat.Sub 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