Protocols/Shell H2S

From PCSAR

Contents 1 Background 2 Profile 3 Protocol 4 Support 4.1 Training 4.2 Notification System 4.3 Radio Channel 5 To do 6 Protocol development

Background

As a result of their exercise in June 2011, Shell identified a need to work 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 and Pincher SAR subsequently negotiated a protocol where Pincher SAR will provide search management and operations. Pincher SAR will provide a SAR manager as an advisor early on in their incidents. When the need for a search is identified, Pincher SAR will be in charge of that activity. Industry personnel will accompany search teams for safety.

Profile

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 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.

H2S incidents originating from commercial oil or gas field facilities, where search and rescue groups may be involved, would generally fall into three possibly scenarios:

Scenario 1: a drilling operation. Because of the known risk the company will have additional resources on standby. Problems typically develop over several hours or days before there is an effect on surrounding public. If a incident occurs, the source is known. Potentially a larger amount of H2S can be released over a longer period of time than in other scenarios.

In this scenario 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.

Scenario 2: an instantaneous release due to equipment failure at a facility or pipeline. The failed equipment is quickly isolated resulting in a smaller amount released than in a well scenario. In pipelines, the isolated segment may be up to 1 km in length, so the exact source is not known initially. The gas cloud disperses quickly.

Scenario 3: The same as scenario 2 but complications in isolation or weather conditions (no wind) result in the gas cloud not dispersing rapidly.

Role 1 - door knocking: When industry personnel are in short supply, SAR workers may accompany them (typically in paired teams of 2) to provide notification through door knocking. The industry person will be the team leader. The SAR worker will assist and provide advise in e.g. preserving tracks should the situation escalate to a search.

Role 2 - search: 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.

Protocol

Policies:

1. 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: As guidelines, SAR workers who are inexperienced with H2S and SAR dogs 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 limit is a maximum of 10 ppm for a maximum of 8 hours.
2. An experienced industry safety person will accompany all SAR teams and be constantly monitoring the environment.
3. As in any incident, SAR workers will not be encouraged to work in an environment where they don't feel comfortable.
4. At all times, Shell will be responsible for the safety of the field teams.
5. Shell will be responsible for directing and performing the notification operations, with possible assistance from SAR workers.
6. Pincher SAR will be responsible for directing and performing the search operations should they be required.
7. Costs of the SAR response will be paid for by Shell.

Procedure:

1. Upon reaching Level 1 or higher, Shell's Logistics Section will contact 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)
   • 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.
2. 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
3. The Pincher SAR Manager contacts the tasking agency (Pincher Creek RCMP) and recommends that Pincher SAR be tasked to respond.
   • Note: Shell will already have notified the RCMP at a Level 1
   • Rationale: This will provide liability and WCB coverage.
4. The RCMP member tasks Pincher SAR to respond.
5. The PCSAR Manager puts a PCSAR Call-Out Person on stand-by. In incidents that start at Level 2, the PCSAR Manager may put the entire team and possibly neighboring teams on stand-by, or request that they stage at (e.g.) the Pincher Fire Hall.
6. The PCSAR Manager attends the Incident Command Post and assumes the ICS role of Technical Advisor on SAR.
7. 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.
8. 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.
9. A full activation of PCSAR members is undertaken
   • Note: Members arrive typically in 45 minutes + travel time. Possible use of Shell's automated call-out system can reduce this time.
10. When the subjects are found and evacuated or it is unsafe to be in the area, SAR workers are withdrawn.
11. The PCSAR Manager remains in the role of Technical Advisor until the incident drops below Level 1.
    • Rationale: additional searches may evolve

Support

Training

Training would be provided to SAR volunteers from PCSAR and neighbouring groups 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.

PCSAR SAR managers are expected to take H2S training to support their managing of responses to these incidents.

Shell Incident Commanders will receive an orientation on the basics of what SAR can provide, what SAR needs, and how to work with SAR.

Shell rovers will receive training on

• the do's and don't's of search prior to trained SAR workers showing up
• e.g. how to avoid damaging tracking information at vehicles

The industry safety personnel that will accompany SAR teams will receive training on

• how to work with trained SAR personnel.
  • roles and responsibilities
• purposeful wandering

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 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.

Radio Channel

Shell's 2 field radio channels have been added to PCSAR's radios to aid intercommunications.

To do

(review: Brett Wuth)

• 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

Participants:

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
• 2011-08-16 discussed at PCSAR preplan mtg
• 2011-09-06 approved by PCSAR board
• 2011-10-14 Nov 19 exercise planning meeting sets objective of verifying protocol