25.01.2015 Views

SOP Manual - Cleveland Fire Department

SOP Manual - Cleveland Fire Department

SOP Manual - Cleveland Fire Department

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Cleveland</strong> <strong>Fire</strong> <strong>Department</strong><br />

Operations <strong>Manual</strong><br />

Sprinklers and Standpipes<br />

Purpose<br />

To provide a policy for <strong>Fire</strong> Company operations at buildings protected by fire sprinklers and equipped<br />

with standpipes.<br />

Objective<br />

To establish guidelines for supporting <strong>Fire</strong> <strong>Department</strong> Connections and operating from standpipes.<br />

Scope<br />

These procedures apply to all Engine Companies in reference to sprinkler and standpipe connections.<br />

Responsibility<br />

It is the responsibility of the Incident Commander and the Company Officers to comply with this policy.<br />

Policy<br />

A. Upon Arrival<br />

B. Safety:<br />

1. Give conditions report.<br />

2. Continue size-up.<br />

3. Determine exact location of the fire.<br />

a. Check with occupants.<br />

b. Check enunciator panel (if available)<br />

c. Check for alarm bells ringing, which may indicate the involved zone.<br />

d. Check for water flowing from exterior drains, which may indicate the general<br />

area.<br />

4. Request that the second arriving Engine Company standby or hook up and pump to the<br />

<strong>Fire</strong> Sprinkler or Standpipe Connection.<br />

1. Use full protective clothing.<br />

2. Maintain tight control over personnel during interior operations.<br />

3. Use hose lines during interior search operations.<br />

4. No personnel shall use an elevator in any occupancy to gain access to a hose connection.<br />

Effective: June 1, 1997 Revised: 5/14/2009 Page | 242<br />

Approved by: Chief Chuck Atchley

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!