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 17: | Line 17: | ||
'''Announcement''' | '''Announcement''' | ||
- | Pincher Creek | + | Pincher Creek SAR and Shell Canada have negotiated a protocol for the |
involvement of SAR responders in incidents of H2S release in the area | involvement of SAR responders in incidents of H2S release in the area | ||
managed by the Shell Waterton facility. H2S, a gas that is poisonous | managed by the Shell Waterton facility. H2S, a gas that is poisonous | ||
Line 55: | Line 55: | ||
'''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 100: | Line 99: | ||
Helicopter, | Helicopter, | ||
vehicle, quad and foot teams would be used. | vehicle, quad and foot teams would be used. | ||
- | (There is no history in this | + | (There is no history in this area of this type of search being required.) |
'''Role 3 - search - unresponsive''': | '''Role 3 - search - unresponsive''': | ||
Line 108: | Line 107: | ||
there may be individuals who have been "knocked down" | there may be individuals who have been "knocked down" | ||
and are unconscious. | and are unconscious. | ||
- | The subjects | + | The subjects will not be responsive. |
Helicopter, | Helicopter, | ||
vehicle, quad and foot teams would be used. | vehicle, quad and foot teams would be used. | ||
- | (There is no history in this | + | (There is no history in this area of this type of search being required.) |
'''Role 4 - provide mobile command post''': | '''Role 4 - provide mobile command post''': | ||
- | + | Under discussion and not yet decided | |
+ | is whether PCSAR's mobile command post | ||
+ | could be of benefit for general use of in the field during an incident. | ||
== Protocol == | == Protocol == | ||
Line 121: | Line 122: | ||
# 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, whether experienced or inexperienced with H2S, will be deployed when readings are 0 ppm (i.e less than 500 ppb).'' |
#* ''Note: The legal working limit is a maximum of 10 ppm for a maximum of 8 hours.'' | #* ''Note: The legal working limit is a maximum of 10 ppm for a maximum of 8 hours.'' | ||
# SAR dogs will not be used. | # SAR dogs will not be used. | ||
- | #* ''Rationale: dogs are | + | #* ''Rationale: dogs are known to be attracted to H2S odour and could expose themselves to high spot concentration'' |
# 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. | ||
Line 138: | Line 139: | ||
#* ''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 | ||
Line 145: | Line 146: | ||
#* ''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. In incidents that start at Level 2 or higher, the PCSAR Manager requests the entire team and possibly neighboring teams to stage at (e.g.) the Pincher Fire Hall or to be on standby. | + | # The PCSAR Manager puts a PCSAR Call-Out Person on stand-by. In incidents that start at Level 2 or higher, the PCSAR Manager requests the entire team and possibly neighboring teams to stage at (e.g.) the Pincher Fire Hall (or to be on standby). |
# 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 as appropriate to the evolving situation, has PCSAR members put on stand-by. | # The PCSAR Manager maintains an awareness of the efforts to notify the public at Level 1 (rovers) and as appropriate to the evolving situation, has PCSAR members put on stand-by. | ||
Line 152: | Line 153: | ||
# If the incident goes to Level 2 or higher, 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 or higher, 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. | ||
# 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, stand-by and staging can reduce this time.'' |
# When the subjects are found and evacuated or it is unsafe to be in the area, SAR workers are withdrawn. | # When the subjects are found and evacuated or it is unsafe to be in the area, SAR workers 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. | ||
Line 160: | Line 161: | ||
'''Partial ICS organization chart:''' | '''Partial ICS organization chart:''' | ||
- | + | Incident Commander | |
- | + | | | |
- | + | +-----------+--------------+ | |
- | + | Operations Planning | |
- | + | Section Chief Section Chief | |
- | + | | | | |
- | + | Public Safety Search and Rescue | |
- | + | Group Supervisor Technical Advisor | |
- | + | | (PCSAR) | |
- | + | Evacuation/Search | |
- | + | Leader | |
- | + | (PCSAR) | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
== Personnel requirements == | == Personnel requirements == | ||
Line 198: | Line 179: | ||
<br/> | <br/> | ||
Only 3 of the current pool of PCSAR managers may be available. Of the others | Only 3 of the current pool of PCSAR managers may be available. Of the others | ||
- | * | + | * 1 lives too far away (Lethbridge) |
+ | * 3 are likely to be preempted by a simultaneous activation of PCCEMA to deal with the same incident. | ||
'''SAR workers experienced with H2S''': | '''SAR workers experienced with H2S''': | ||
Line 206: | Line 188: | ||
'''SAR workers not experienced with H2S''': | '''SAR workers not experienced with H2S''': | ||
* rest of PCSAR members, members from neighbouring groups | * rest of PCSAR members, members from neighbouring groups | ||
- | |||
- | |||
== Support == | == Support == | ||
Line 235: | Line 215: | ||
- | A mock | + | A mock incident was set up to validate this protocol. |
- | + | === Notification System === | |
+ | To further reduce PCSAR's time to scene, Shell is offering the | ||
+ | use of their automated call out system to notify PCSAR members. | ||
+ | A report of who was notified and what their numeric touch tone response was | ||
+ | can be e-mailed or faxed to the Pincher SAR manager / call-out person. | ||
+ | |||
+ | 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 to an H2S incident | ||
+ | |||
+ | Use #3: | ||
+ | Shell is exploring the possibility of use of their automated call out system | ||
+ | as a general (non-H2S) mechanism to notify PCSAR members of an incident. | ||
+ | * ''Rationale: Shell may be able to undertake this service to PCSAR at little additional cost. Usage for this purpose would serve as verification and on-going practice of the automated system for Shell personnel.'' | ||
=== 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|tasked}} | |
- | + | ||
* confirm protocol with RCMP | * confirm protocol with RCMP | ||
- | * | + | * review Shell's automated calling system with Shell or their provider |
- | + | * monitor H2S training to members | |
- | + | * Notify BC SAR community that may be model for other areas (AB already done) | |
- | + | * Determine whether/how SAR dogs can be used | |
- | + | ** What H2S level is unhealthy for them? | |
- | + | ** What H2S level (if any) impacts their performance? | |
- | + | ** Are they at risk of being attracted to point sources of H2S? | |
- | * | + | * pre-identify which PCSAR members are H2S experienced |
- | * | + | * discuss with PCCEMA where of 3 search managers that are PCCEMA members, whether should plan to release 1 to this protocol |
- | * ( | + | |
- | * | + | |
- | + | ||
- | + | ||
- | + | ||
== Protocol development == | == Protocol development == | ||
Line 265: | Line 252: | ||
Pincher SAR | Pincher SAR | ||
- | * | + | * Brett Wuth |
- | * | + | * Brian Balak |
- | + | * Janet Jones | |
- | + | * Eric Bruder | |
- | * | + | * Ron Hann |
- | * | + | Shell |
+ | * Jim Little | ||
+ | * Brandy Kilkenny | ||
+ | * Cal Piotrowski | ||
Log | Log | ||
- | * [[2011-06-16 Shell Mock|2011-06-16]] Shell Waterton 68 ERP | + | * [[2011-06-16 Shell Mock|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 282: | Line 272: | ||
* 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 | ||
* 2011-10-18 reviewed and updated at PCSAR preplan mtg with Shell | * 2011-10-18 reviewed and updated at PCSAR preplan mtg with Shell | ||
- | * [[2011-11-19 Shell Mock|2011-11-19]] Shell pipeline | + | * [[2011-11-19 Shell Mock|2011-11-19]] Shell pipeline exercise |
* 2012-01-03 Jim Little, Cal Piotrowski attend PCSAR board mtg re phone system; discuss training of Shell personnel with Brett | * 2012-01-03 Jim Little, Cal Piotrowski attend PCSAR board mtg re phone system; discuss training of Shell personnel with Brett | ||
* 2012-01-09 announcement sent to SARA board, Alberta SAR community | * 2012-01-09 announcement sent to SARA board, Alberta SAR community | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- |