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 13: | Line 13: | ||
charge of that activity. Industry personnel will accompany search | charge of that activity. Industry personnel will accompany search | ||
teams for safety. | teams for safety. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
== Profile == | == Profile == | ||
- | During an evolving event, Shell has different levels of activation: | + | 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. | * '''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 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 | + | * '''Level 2''': Non-workers in the area will be required to evacuate. A search is 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. | Shell typically co-locates the Incident Command Post with the Emergency Operations Centre at the Shell Waterton Plant. | ||
Line 55: | Line 28: | ||
'''Scenario 1''': a drilling operation. | '''Scenario 1''': a drilling operation. | ||
- | Because of the known risk | + | Because of the known risk the company |
- | the company | + | |
will have additional resources on standby. | will have additional resources on standby. | ||
Problems typically develop over several hours or days | Problems typically develop over several hours or days | ||
before there is an effect on surrounding public. | before there is an effect on surrounding public. | ||
- | If | + | If a incident occurs, the source is known. |
Potentially a larger amount of H2S can be released | Potentially a larger amount of H2S can be released | ||
over a longer period of time than in other scenarios. | over a longer period of time than in other scenarios. | ||
Line 83: | Line 55: | ||
'''Role 1 - door knocking''': | '''Role 1 - door knocking''': | ||
- | When industry personnel are in short supply | + | When industry personnel are in short supply, |
SAR workers may accompany them (typically in paired teams of 2) | SAR workers may accompany them (typically in paired teams of 2) | ||
to provide notification through door knocking. | to provide notification through door knocking. | ||
Line 90: | Line 62: | ||
should the situation escalate to a search. | should the situation escalate to a search. | ||
- | '''Role 2 - search | + | '''Role 2 - search''': |
- | + | ||
- | + | ||
- | + | ||
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. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
== Protocol == | == Protocol == | ||
Line 121: | Line 74: | ||
# 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. | ||
#* ''Note: The Incident Management Team will continuously make this evaluation based on for example, readings in the field, computer modelling of gas cloud, and access to egress routes.'' | #* ''Note: The Incident Management Team will continuously make this evaluation based on for example, readings in the field, computer modelling of gas cloud, and access to egress routes.'' | ||
- | #* ''Note: As | + | #* ''Note: As guidelines, SAR workers who are inexperienced with H2S will be deployed when readings are 0 ppm (i.e less than 500 ppb); SAR workers who are experienced with H2S typically may be deployed when readings are up to 2 ppm.'' |
- | #* ''Note: The legal | + | #* ''Note: The legal limit is a maximum of 10 ppm for a maximum of 8 hours.'' |
- | + | ||
- | + | ||
# 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 86: | ||
#* ''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 STARS Link Centre is not a suitable number to receive an automated call.'' |
# 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 in 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 | ||
- | #* ''Note: Members arrive typically in 45 minutes + travel time. Possible use of | + | #* ''Note: Members arrive typically in 45 minutes + travel time. Possible use of Shell's automated call-out system can reduce this 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 114: | ||
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 123: | ||
- | 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 2 field radio channels have been added to PCSAR's radios to aid intercommunications. |
== To do == | == To do == | ||
- | + | {{rbw}} | |
- | + | ||
* confirm protocol with RCMP | * confirm protocol with RCMP | ||
- | * | + | * Label Shell's channels on PCSAR radios |
- | + | * review Shell's automated calling system with Shell or their provider | |
- | * | + | * provide H2S training to members |
- | + | * Notify SARA / BC that may be model for other areas (after approved) | |
- | + | ||
- | + | ||
- | * | + | |
- | + | ||
- | * | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
== Protocol development == | == Protocol development == | ||
Line 265: | Line 147: | ||
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 281: | Line 162: | ||
* 2011-09-06 approved by PCSAR board | * 2011-09-06 approved by PCSAR board | ||
* 2011-10-14 Nov 19 exercise planning meeting sets objective of verifying protocol | * 2011-10-14 Nov 19 exercise planning meeting sets objective of verifying protocol | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- |