Protocols/Shell H2S

From PCSAR

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
-
.
+
Hi All,
 +
 
 +
I just had a phone conversation with Jim Little and Brandy Kilkenny from
 +
Shell.
 +
 
 +
As a result of their recent mock exercise, they're looking for ways of
 +
working better with Pincher SAR. During an H2S incident, if they
 +
don't immediately locate a resident and have reason to believe they
 +
are still in the area, they would want a search to be initiated.
 +
 
 +
We are meeting Thursday at 11:00 to create a draft protocol. I'm
 +
e-mailing you to get your input.
 +
 
 +
In our preliminary discussion the following points were raised:
 +
 
 +
Training would be provided to SAR volunteers on working safely in an
 +
H2S environment. This would be to raise the confidence of SAR
 +
volunteers that they can be safe in such environments.
 +
 
 +
SAR responders would only be working in H2S environments where it
 +
is possible to work safely without masks.
 +
 
 +
A higher trained H2S worker would accompany all teams and be
 +
constantly monitoring the environment.
 +
 
 +
H2S events evolve relatively slowly, so that there would typically be
 +
time to conduct the search before searchers may have to be withdrawn.
 +
They expect hours or days in this phase. Typically 6 hours,
 +
occasionally as low as 2 hours.
 +
 
 +
There would typically be only one individual or party being searched
 +
for. The search areas might be up to 3 quarter sections of open
 +
agricultural, forested, or mountainous terrain. The subjects would be
 +
responsive (no expectation of simultaneous injury). Helicopter,
 +
vehicle, quad and foot teams would be used.
 +
 
 +
In order to reduce our time to scene, we would be prealerted prior to
 +
a decision to advise evacuating residents.
 +
 
 +
Our search manager would make a decision of whether to respond,
 +
establish contact with the tasking agency (RCMP) and make a
 +
recommendation to be tasked.
 +
 
 +
To further reduce our time to scene, Shell is considering offering the
 +
use of their automated call out system to notify our members. I know
 +
the board was looking at purchasing such a service. Was Eric taking
 +
the lead on that? I'd like to get the requirements you've developed
 +
and the recommendations of the call-out people to see how Shell's
 +
offer could best fit.
 +
 
 +
Shell wants to have a protocol in place by the end of August to meet
 +
their drilling schedule.
 +
 
 +
Subsequent to the protocol, Shell would like to have some training
 +
related to SAR for their field personnel. They are targeting only 8
 +
hours, not the full 40 hour SAR Fundamentals. This shorter training
 +
might be about how to work with trained SAR personnel, and what to
 +
do/not do before SAR workers show up.
 +
 
 +
I haven't mentioned yet, but I intend to bring up:
 +
 
 +
The need to have a Search Manager as part of the incident overhead
 +
team.
 +
 
 +
The need to orient their Incident Commander in the basics of what SAR
 +
can provide, what SAR needs, and how to work with SAR.
 +
 
 +
It should be noted that we, a volunteer organization, through the
 +
proposed protocol would be providing an emergency service to Shell, a
 +
business. Shell is currently offering:
 +
 
 +
* training
 +
* use of their call out system
 +
 
 +
It may be appropriate to ask for additional support. On the other
 +
hand, Shell has been a long time supporter of Pincher SAR and has
 +
contributed in many ways. I'd like to hear from the board if they
 +
want me to bring up any other ways we hope they could reciprocate.
 +
 
 +
At the last board meeting, the board asked me to take the lead in
 +
these discussions. If the board has any other direction, please
 +
provide it, or if you wish someone to attend Thursday's meeting in
 +
addition to me, that would work to.
 +
 
 +
Any other input from anyone with thoughts, ideas or concerns would be
 +
appreciated. Please e-mail or call me.
 +
 
 +
Coming out of Thursday's meeting will be a draft protocol. I'll
 +
distribute it as soon as it's written up. I'll ask for your feedback
 +
and comments. We will discuss it at the August 16 Preplan meeting.
 +
Assuming their are no major hiccups, the board can endorse it at the
 +
September 6 meeting. If there are concerns, we should resolve them
 +
quickly so that by Shell's goal of August 31, I'll be able to indicate
 +
whether Pincher SAR is likely or not to adopt the protocol.
 +
 
 +
I look forward to your comments on the above work.

Revision as of 23:06, 16 August 2011

Hi All,

I just had a phone conversation with Jim Little and Brandy Kilkenny from Shell.

As a result of their recent mock exercise, they're looking for ways of working better with Pincher SAR. During an H2S incident, if they don't immediately locate a resident and have reason to believe they are still in the area, they would want a search to be initiated.

We are meeting Thursday at 11:00 to create a draft protocol. I'm e-mailing you to get your input.

In our preliminary discussion the following points were raised:

Training would be provided to SAR volunteers on working safely in an H2S environment. This would be to raise the confidence of SAR volunteers that they can be safe in such environments.

SAR responders would only be working in H2S environments where it is possible to work safely without masks.

A higher trained H2S worker would accompany all teams and be constantly monitoring the environment.

H2S events evolve relatively slowly, so that there would typically be time to conduct the search before searchers may have to be withdrawn. They expect hours or days in this phase. Typically 6 hours, occasionally as low as 2 hours.

There would typically be only one individual or party being searched for. The search areas might be up to 3 quarter sections of open agricultural, forested, or mountainous terrain. The subjects would be responsive (no expectation of simultaneous injury). Helicopter, vehicle, quad and foot teams would be used.

In order to reduce our time to scene, we would be prealerted prior to a decision to advise evacuating residents.

Our search manager would make a decision of whether to respond, establish contact with the tasking agency (RCMP) and make a recommendation to be tasked.

To further reduce our time to scene, Shell is considering offering the use of their automated call out system to notify our members. I know the board was looking at purchasing such a service. Was Eric taking the lead on that? I'd like to get the requirements you've developed and the recommendations of the call-out people to see how Shell's offer could best fit.

Shell wants to have a protocol in place by the end of August to meet their drilling schedule.

Subsequent to the protocol, Shell would like to have some training related to SAR for their field personnel. They are targeting only 8 hours, not the full 40 hour SAR Fundamentals. This shorter training might be about how to work with trained SAR personnel, and what to do/not do before SAR workers show up.

I haven't mentioned yet, but I intend to bring up:

The need to have a Search Manager as part of the incident overhead team.

The need to orient their Incident Commander in the basics of what SAR can provide, what SAR needs, and how to work with SAR.

It should be noted that we, a volunteer organization, through the proposed protocol would be providing an emergency service to Shell, a business. Shell is currently offering:

  • training
  • use of their call out system

It may be appropriate to ask for additional support. On the other hand, Shell has been a long time supporter of Pincher SAR and has contributed in many ways. I'd like to hear from the board if they want me to bring up any other ways we hope they could reciprocate.

At the last board meeting, the board asked me to take the lead in these discussions. If the board has any other direction, please provide it, or if you wish someone to attend Thursday's meeting in addition to me, that would work to.

Any other input from anyone with thoughts, ideas or concerns would be appreciated. Please e-mail or call me.

Coming out of Thursday's meeting will be a draft protocol. I'll distribute it as soon as it's written up. I'll ask for your feedback and comments. We will discuss it at the August 16 Preplan meeting. Assuming their are no major hiccups, the board can endorse it at the September 6 meeting. If there are concerns, we should resolve them quickly so that by Shell's goal of August 31, I'll be able to indicate whether Pincher SAR is likely or not to adopt the protocol.

I look forward to your comments on the above work.

Retrieved from "http://pcsar.dyndns.org:8080/mediawiki/index.php/Protocols/Shell_H2S"
Personal tools