Protocols/Shell H2S
From PCSAR
(→Support) |
(→Protocol history) |
||
| Line 103: | Line 103: | ||
* 2011-07-21 PCSAR exercise review | * 2011-07-21 PCSAR exercise review | ||
* 2011-07-30 Shell requests discussions | * 2011-07-30 Shell requests discussions | ||
| - | * 2011-08-09 phone discussions | + | * 2011-08-09 PCSAR/Shell phone discussions |
| - | * 2011-08-11 meeting | + | * 2011-08-11 PCSAR/Shell meeting |
Revision as of 23:59, 16 August 2011
Contents |
Background
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.
Shell wants to have a protocol in place by the end of August, 2011 to meet their drilling schedule.
Profile
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.
During an evolving event, Shell would go through different levels of activation:
- Alert: Shell has received information about a possible incident but has not confirmed it.
- Level 1: An incident has been confirmed, but is not at the level to require evacuations. Public in the area will be notified. Any person suspected to be in the area, but not found for notification, would potentially be a search subject at Level 2.
- Level 2: Non-workers in the area will be required to evacuate. Search conducted for public that are suspected to still be in the area.
Protocol
Principles:
- 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 SAR teams and be constantly monitoring the environment.
- As in any incident, SAR workers will not be encouraged to work in an environment where they don't feel comfortable.
- When participating a search, Pincher SAR will be responsible for directing and performing the search operations; Shell will be responsible for the safety of the field teams.
- Costs of the SAR response would be paid for by Shell.
Procedure:
- Upon reaching Level 1, Shell's Logistics Section will contact a Pincher SAR and request a Search Manager attend the Incident Command Post.
- Rationale: Go big fast. Don't know whether SAR will be required but better to get involved early.
- Contact: 403-627-2262 (Dispatch through STARS Link Centre) or 403-627-5804 (On-call Manager)
- The Pincher SAR Manager will evaluate the situation and determine whether it is appropriate for Pincher SAR to be involved.
- If the situation matches the above profile, it normally would be appropriate
- The Pincher SAR Manager contacts the tasking agency (Pincher Creek RCMP) and recommends that Pincher SAR be tasked to respond at the level of a SAR Manager involvement.
- Note: Shell will already have notified the RCMP at a Level 1
- Rationale: This will provide liability and WCB coverage.
- The RCMP member tasks Pincher SAR to respond.
- The PCSAR Manager puts a PCSAR Call-Out Person on stand-by.
- The PCSAR Manager attends the Incident Command Post and assumes the ICS role of technical advisor on SAR.
- The PCSAR Manager maintains an awareness of the efforts to notify the public at Level 1 (rovers) and if necessary has PCSAR members put on stand-by.
- If the incident goes to Level 2, Shell appoints the PCSAR Manager to the additional ICS role of "Evacuation/Search Leader" and directs the search effort.
- A full activation of PCSAR members is undertaken
- Members arrive typically in 45 minutes + travel time.
Support
Training
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.
The need to orient their Incident Commander in the basics of what SAR can provide, what SAR needs, and how to work with SAR.
Notification System
To further reduce our time to scene, Shell is 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.
To do
(review: Brett Wuth)
- Involve RCMP in protocol development
- Get copy of report from Shell's mock
- Add Shell's channels to PCSAR radios
- Notify SARA / BC that may be model for other areas
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.
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.
Protocol history
Pincher SAR:
- Brett Wuth
- Brian Balak
Shell
- Jim Little
- Brandy Kilkenny
Log
- 2011-06-16 Shell Waterton 68 ERP - exercise
- 2011-07-21 PCSAR exercise review
- 2011-07-30 Shell requests discussions
- 2011-08-09 PCSAR/Shell phone discussions
- 2011-08-11 PCSAR/Shell meeting
