Editing Protocols/Shell H2S
From PCSAR
Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Current revision | Your text | ||
Line 1: | Line 1: | ||
== Background == | == Background == | ||
- | As a result of their exercise | + | As a result of their recent mock exercise, Shell is looking for ways of |
- | Shell | + | working better with Pincher SAR. During an H2S incident, if they |
- | + | ||
don't immediately locate a resident and have reason to believe 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. | are still in the area, they would want a search to be initiated. | ||
- | Shell | + | Shell wants to have a protocol in place by the end of August, 2011 to meet |
- | + | their drilling schedule. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
== Profile == | == Profile == | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
H2S incidents originating from commercial oil or gas field facilities, where | H2S incidents originating from commercial oil or gas field facilities, where | ||
search and rescue groups may be involved, would generally fall into three | search and rescue groups may be involved, would generally fall into three | ||
possibly scenarios: | possibly scenarios: | ||
- | + | 1) an instantaneous release due to equipment failure followed by | |
- | + | isolation of the failed equipment and a diminishing gas cloud | |
- | the | + | |
- | + | 2) an instantaneous release due to equipment failure followed by | |
- | + | complications in isolating the release or weather conditions that do not | |
- | + | disperse the gas cloud quickly | |
- | + | ||
- | + | 3) a drilling operation were the incident may develop over several hours | |
- | + | or days allowing for a standby situation prior to any searches | |
+ | |||
- | + | H2S events evolve relatively slowly, so that there would typically be | |
time to conduct the search before searchers may have to be withdrawn. | time to conduct the search before searchers may have to be withdrawn. | ||
They expect hours or days in this phase. Typically 6 hours, | They expect hours or days in this phase. Typically 6 hours, | ||
occasionally as low as 2 hours. | occasionally as low as 2 hours. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
There would typically be only one individual or party being searched | There would typically be only one individual or party being searched | ||
for. The search areas might be up to 3 quarter sections of open | for. The search areas might be up to 3 quarter sections of open | ||
agricultural, forested, or mountainous terrain. The subjects would be | agricultural, forested, or mountainous terrain. The subjects would be | ||
- | responsive (no expectation of simultaneous injury). | + | responsive (no expectation of simultaneous injury). Helicopter, |
- | Helicopter, | + | |
vehicle, quad and foot teams would be used. | vehicle, quad and foot teams would be used. | ||
- | |||
- | + | During an evolving event, Shell would has 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. A search conducted for public that are suspected to still be in the area. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | Shell typically co-locates the Incident Command Post with the Emergency Operations Centre at the Shell Waterton Plant. | |
- | + | ||
== Protocol == | == Protocol == | ||
Line 120: | Line 46: | ||
'''Policies:''' | '''Policies:''' | ||
# SAR responders will only be working in H2S environments where it is possible to work safely without masks. | # SAR responders will only be working in H2S environments where it is possible to work safely without masks. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
# An experienced industry safety person will accompany all SAR teams and be constantly monitoring the environment. | # An experienced industry safety person will 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. | # As in any incident, SAR workers will not be encouraged to work in an environment where they don't feel comfortable. | ||
- | # | + | # When participating in 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 will be paid for by Shell. | # Costs of the SAR response will be paid for by Shell. | ||
- | |||
'''Procedure:''' | '''Procedure:''' | ||
Line 138: | Line 56: | ||
#* ''Rationale: Go big fast. Don't know whether SAR will be required but better to get involved early.'' | #* ''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) | #* Contact: 403-627-2262 (Dispatch through STARS Link Centre) or 403-627-5804 (On-call Manager) | ||
- | #* ''Note: Shell might | + | #* ''Note: Shell might chose to add 403-627-5804 to their automated notification system and call 403-627-2262 only if there is no answer on the first number'' |
# The Pincher SAR Manager will evaluate the situation and determine whether it is appropriate for Pincher SAR to be involved. | # 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 | #* 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. | + | # 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'' | #* ''Note: Shell will already have notified the RCMP at a Level 1'' | ||
#* ''Rationale: This will provide liability and WCB coverage.'' | #* ''Rationale: This will provide liability and WCB coverage.'' | ||
# The RCMP member tasks Pincher SAR to respond. | # The RCMP member tasks Pincher SAR to respond. | ||
- | # The PCSAR Manager puts a PCSAR Call-Out Person on stand-by | + | # 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 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 | + | # The PCSAR Manager maintains an awareness of the efforts to notify the public at Level 1 (rovers) and if appropriate to the evolving situation has PCSAR members put on stand-by. |
- | + | # If the incident goes to Level 2, Shell Incident Commander appoints the PCSAR Manager to the additional ICS role of "Evacuation/Search Leader". From that role, The PCSAR Manager directs the search effort. | |
- | + | ||
- | # If the incident goes to Level 2 | + | |
# A full activation of PCSAR members is undertaken | # A full activation of PCSAR members is undertaken | ||
- | #* | + | #* Members arrive typically in 45 minutes + travel time. |
- | # When the subjects are found and evacuated or it is unsafe to be in the area, | + | # When the subjects are found and evacuated or it is unsafe to be in the area, PCSAR members are withdrawn. |
# The PCSAR Manager remains in the role of Technical Advisor until the incident drops below Level 1. | # The PCSAR Manager remains in the role of Technical Advisor until the incident drops below Level 1. | ||
#* ''Rationale: additional searches may evolve'' | #* ''Rationale: additional searches may evolve'' | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
== Support == | == Support == | ||
=== Training === | === Training === | ||
- | Training | + | Training would be provided to SAR volunteers on working safely in an |
- | on | + | H2S environment. This would be to raise the confidence of SAR |
- | + | ||
- | This | + | |
volunteers that they can be safe in such environments. | volunteers that they can be safe in such environments. | ||
- | |||
- | |||
- | |||
- | |||
Shell Incident Commanders will receive an orientation on the basics of what SAR | Shell Incident Commanders will receive an orientation on the basics of what SAR | ||
Line 226: | Line 84: | ||
Shell rovers will receive training on | Shell rovers will receive training on | ||
* the do's and don't's of search prior to trained SAR workers showing up | * the do's and don't's of search prior to trained SAR workers showing up | ||
- | * e.g. how to avoid | + | * e.g. how to avoid damage tracking information at vehicles |
The industry safety personnel that will accompany SAR teams will receive | The industry safety personnel that will accompany SAR teams will receive | ||
Line 235: | Line 93: | ||
- | A mock | + | A mock incident will be set up to validate this protocol. |
- | + | === Notification System === | |
+ | To further reduce our time to scene, Shell is offering the | ||
+ | use of their automated call out system to notify our members. | ||
+ | Use #1: to notify the on-call manager when a Level 1 is reached. | ||
+ | |||
+ | Use #2: to notify all SAR responders for a standby or call-out | ||
=== Radio Channel === | === Radio Channel === | ||
- | Shell's | + | Shell's radio channel(s) will be programmed into PCSAR's radios to aid intercommunications. |
== To do == | == To do == | ||
- | + | {{rbw}} | |
- | * | + | * Involve RCMP in protocol development |
- | + | * Get copy of report from Shell's mock | |
- | * | + | * Add Shell's channels to PCSAR radios |
- | * | + | * review Shell's automated calling system with Shell or their provider |
- | * | + | * Notify SARA / BC that may be model for other areas (after approved) |
- | + | 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. | |
- | + | ||
- | + | ||
- | + | ||
== Protocol development == | == Protocol development == | ||
Line 265: | Line 125: | ||
Pincher SAR | Pincher SAR | ||
- | * | + | * Brett Wuth |
- | + | * Brian Balak | |
- | + | Shell | |
- | + | * Jim Little | |
- | * | + | * Brandy Kilkenny |
- | * | + | |
Log | Log | ||
- | * | + | * 2011-06-16 Shell Waterton 68 ERP - exercise |
* 2011-07-21 PCSAR exercise review | * 2011-07-21 PCSAR exercise review | ||
* 2011-07-30 Shell requests discussions | * 2011-07-30 Shell requests discussions | ||
Line 279: | Line 138: | ||
* 2011-08-11 PCSAR/Shell meeting | * 2011-08-11 PCSAR/Shell meeting | ||
* 2011-08-16 discussed at PCSAR preplan mtg | * 2011-08-16 discussed at PCSAR preplan mtg | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- |