Recently I became aware that a local jurisdiction, which my department works closely, has no SOPs. I know at one point they had SOGs, that were very similar to my departments. I found this out during a training exercise. The exercise was a building fire and the first engine on location laid out from the hydrant. The second arriving piece was a supervisor (from my department), he took command and started running the fire ground. The next piece was the truck, followed closely by the final 2 engines. The fire was extinguished and the dummies were found and removed and the scenario was over. I thought there were minimal problems with the scenario, however I found out that neither of the engines that arrived after the initial engine picked up the line. While discussing the scenario I found out the their department has no SOPs and if you want them to do something, you must tell them. Does anyone have solid reasoning for not having SOP/SOG? I am really trying to understand the thinking behind this idea.
Tags:
Aaron,
I can think of absolutely no good reason why the department would not have a thorough and comprehensive set of SOP's. It makes absolutely no sense in an industry as complicated and as intricate as ours to not have a well-written set of guidelines or procedures that one can follow when under extreme stress, limited resources and limited information. That is exactly what a standard operating procedure does best, it takes a little bit of that pressure off you so you have at least a framework of a game plan that you can manage your resources around. Having a set of standard operating procedures also allows companies to work together synergistically to achieve tactical objectives. It provides everyone standard game plan to fall back on. Occasionally we meet a fire that we have to step back from and assume a defensive posture or devise a unique approach to but generally standard operating procedures provide us the framework we need to get our work done. Lacking fire ground SOP's is negligent in my opinion.
While having a good set of SOPs/SOGs is essential, some of those who write them make them far too complex. Some "adapt" exsiting versions without really reading them, some have no correlation to a Department's operations.
My version of SOPs/SOGs would be clear and concise and in bullet point fashion... one does not need the equivalent of Tolstoy's "War and Peace" to sum up on what could be stated on a single page or two.
The login above DOES NOT provide access to Fire Engineering magazine archives. Please go here for our archives.
Our contributors' posts are not vetted by the Fire Engineering technical board, and reflect the views and opinions of the individual authors. Anyone is welcome to participate.
For vetted content, please go to www.fireengineering.com/issues.
We are excited to have you participate in our discussions and interactive forums. Before you begin posting, please take a moment to read our community policy page.
Be Alert for Spam
We actively monitor the community for spam, however some does slip through. Please use common sense and caution when clicking links. If you suspect you've been hit by spam, e-mail peter.prochilo@clarionevents.com.
Check out the most recent episode and schedule of UPCOMING PODCASTS
45 members
116 members
62 members
73 members
166 members
65 members
277 members
510 members
10 members
106 members
© 2024 Created by fireeng. Powered by
FE Home | Product Center | Training | Zones | Fire-EMS | Firefighting | Apparatus | Health/Safety | Leadership | Prevention | Rescue |