incident reporting & classification module 30 - Brunei Shell ...

incident reporting & classification module 30 - Brunei Shell ... incident reporting & classification module 30 - Brunei Shell ...

20.01.2013 Views

Revision 4.1 Brunei Shell Petroleum Company Sendirian Berhad I NCIDENT R EPORTING & C LASSIFICATION ( INCL. ‘OMNIS AFE’ ) M ODULE 30 T HIS DOCUMENT IS A LEVEL 3 PROCEDURE GUIDING AN ACTIVITY RELATED TO THE HSE M ANAGEMENT S YSTEM Document no. : BSP-02.01.05-Procedure-1621 Document Owner: Document Author: Lee, Wai-Chee, HSE Hairulanuar, HSE/42

Revision<br />

4.1<br />

<strong>Brunei</strong> <strong>Shell</strong> Petroleum Company Sendirian Berhad<br />

I NCIDENT R EPORTING &<br />

C LASSIFICATION<br />

( INCL. ‘OMNIS AFE’ )<br />

M ODULE <strong>30</strong><br />

T HIS DOCUMENT IS A LEVEL 3<br />

PROCEDURE GUIDING AN ACTIVITY<br />

RELATED TO THE HSE<br />

M ANAGEMENT S YSTEM<br />

Document no. : BSP-02.01.05-Procedure-1621<br />

Document Owner:<br />

Document Author:<br />

Lee, Wai-Chee, HSE<br />

Hairulanuar, HSE/42


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Revision Record<br />

REV REVISION DESCRIPTION DATE<br />

1.0 First issue September 1996<br />

2.1 Updated to inc. <strong>reporting</strong> of potentially significant <strong>incident</strong>s November 2000<br />

2.2 Updated to reflect “transition to asset units”, include OmniSafe amendments and<br />

revised investigation & <strong>reporting</strong> changes<br />

April 2002<br />

3.0 Approved May 2002<br />

3.1 Updated to reflect revised early notification of significant <strong>incident</strong>s + reference to<br />

latest group guideline<br />

June 2002<br />

4.0 Definitions updated. Appendix G deleted. Environmental examples added. January 2003<br />

Appendices H and I updated for Occupational Illness - Need for involvement of<br />

LGL for actual consequence rated 3 and above included.<br />

4.1 Corrections made for Actual consequences and potential risk June 2003<br />

Distribution Control<br />

Distribution of this document is via the LIVELINK document management system.<br />

Notice and Warning<br />

Copyright © 2002, <strong>Brunei</strong> <strong>Shell</strong> Petroleum Company Sendirian Berhad<br />

This document is the property of <strong>Brunei</strong> <strong>Shell</strong> Petroleum Sendirian Berhad (BSP), KB3534, Negara <strong>Brunei</strong><br />

Darussalam. Circulation is restricted to BSP and its designated associates, contractors and consultants. It<br />

must not be copied or used for any other purpose other than which it is supplied, without the expressed<br />

written authority of BSP.<br />

Except where provided for purposes of contractual requirements, BSP disclaims any responsibility or liability<br />

for any use or misuse of the document by any person and makes no warranty as to the accuracy or suitability<br />

of the information to any third party. Any misuse of the document is redressable by BSP.<br />

Rev. 4.1 - June 2003 Page 2 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

T ABLE OF C ONTENTS<br />

1 INTRODUCTION 4<br />

2 INCIDENT REPORTING PROCEDURE 9<br />

3 SYSTEM TRAINING & COMPLIANCE MONITORING 13<br />

APPENDIX A - OWNERSHIP OF INCIDENTS & STATISTICS 14<br />

APPENDIX B- EXAMPLES OF ACTUAL RISK ASSESSMENT 15<br />

APPENDIX C – EXAMPLES OF INCIDENT POTENTIAL 16<br />

APPENDIX D – EXAMPLES OF ‘WORK RELATED’ INCIDENTS 18<br />

APPENDIX E – EXAMPLES OF EXPOSURE HOURS 20<br />

APPENDIX F - ENVIRONMENTAL INCIDENTS 21<br />

APPENDIX G - COMPLAINTS FROM THE PUBLIC 23<br />

APPENDIX H - OCCUPATIONAL ILLNESS REPORTING 24<br />

APPENDIX I – OCCUPATIONAL ILLNESS CLASSIFICATION AND EXAMPLES 27<br />

APPENDIX J - MEDICAL TREATMENT AND FIRST AID CASES 28<br />

APPENDIX K – SEVERITY (OR CONSEQUENCE) RATING 29<br />

Rev. 4.1 - June 2003 Page 3 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

1 INTRODUCTION<br />

1.1 Purpose<br />

The BSP HSE Management System requires that company and contractor staff report ALL HSE <strong>incident</strong>s and<br />

near misses related to our activities. This is required so that we can:<br />

- take prompt action to mitigate any residual risks or reduce further exposure;<br />

- communicate the information to others (internally and externally), who may need to take action to<br />

prevent such an <strong>incident</strong> happening<br />

- meet our obligation to notify either government or shareholders about significant <strong>incident</strong>s or injuries<br />

- investigate what happened swiftly and determine appropriate follow up actions to prevent recurrence<br />

1.2 Scope<br />

This procedure applies to ALL company and contractor staff. ALL HSE <strong>incident</strong>s or near misses shall be<br />

reported, classified, and recorded in the corporate HSE Information System, OmniSafe, using this procedure.<br />

The procedure covers:<br />

- initial <strong>incident</strong> <strong>reporting</strong><br />

- <strong>incident</strong> evaluation, which involves actual consequence & potential risk assessment (severity &<br />

likelihood)<br />

- injury <strong>classification</strong><br />

- <strong>incident</strong> ownership & HSE ‘statistic’ ownership<br />

- determining whether <strong>incident</strong>s are ‘work related’ and ‘reportable’<br />

- what constitutes ‘exposure hours’<br />

and explains how OmniSafe is used throughout the process to capture and store ALL relevant information<br />

about each <strong>incident</strong>.<br />

This procedure explicitly excludes the <strong>incident</strong> investigation process, which is addressed separately.<br />

� Module 31 - Incident Investigation & Follow-Up<br />

This procedure applies principally to BSP, but may also be used by BLNG, BST & BSM.<br />

1.3 References<br />

This document is supported by the Group yellow guide, Incident Classification, Investigation & Reporting (see<br />

below)<br />

� http://sww.shell.com/shell-online/group/hse/hse_publications/publications.htm<br />

1.4 Roles and Responsibilities<br />

1.4.1 Incident Reporter<br />

ALL company employees and contractors MUST report ‘work related’ HSE <strong>incident</strong>s and<br />

near misses within 24hrs.<br />

Incidents MUST be reported in OmniSafe, which is available to ALL company web-users. In the event that the<br />

web is unavailable, physically, or temporarily due to break-down or maintenance, then a paper copy of the<br />

<strong>incident</strong> report shall be completed and submitted to the company line supervisor or company contract holder,<br />

which must be entered into OmniSafe as soon as possible.<br />

The company encourages everyone to report any <strong>incident</strong> or near miss, even if it is not considered to be ‘work<br />

related’ - there is learning from every <strong>incident</strong>.<br />

If there is any doubt whether or not the <strong>incident</strong> is work related, REPORT it. The recordability will be resolved<br />

as part of the investigation and follow up.<br />

The <strong>incident</strong> reporter must complete ALL the <strong>incident</strong> report fields, as accurately as possible, including their<br />

own name and reference indicator, or contractor company.<br />

Rev. 4.1 - June 2003 Page 4 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

1.4.2 Incident Owner<br />

Once an <strong>incident</strong> is reported in OmniSafe the reporter must select an ‘owner’, from a drop down menu in<br />

OmniSafe to direct the report to. This person is called the ‘<strong>incident</strong> owner’. Invariably, this will be the most<br />

appropriate asset owner representative (e.g. SOS, AOS, Terminal Superintendent, Drilling Supervisor, etc., or<br />

the company contract holder (see Appendix A - Ownership of Incidents & Statistics).<br />

The <strong>incident</strong> owner is responsible for firstly ‘accepting’ the <strong>incident</strong> (i.e. it is an <strong>incident</strong> related to his/her<br />

asset, or contract, and they are the most appropriate ‘owner’), and secondly ‘evaluating’ the <strong>incident</strong>, which<br />

includes confirming that<br />

• the details of the <strong>incident</strong> are correct<br />

• the actual consequence and potential risk assessments are appropriate, and<br />

• in the case of an injury, the injury <strong>classification</strong> has been recorded.<br />

The <strong>incident</strong> owner is also responsible for ensuring an investigation team leader is appointed appropriate to<br />

the potential risk evaluation. On completion of the <strong>incident</strong> investigation the ‘owner’ is responsible for verifying<br />

that the actions derived from the investigation are closed out properly by the assigned action parties and<br />

approved.<br />

Where medical treatment has been given by anyone other than HML staff, the <strong>incident</strong> owner must draw this<br />

to the attention of HML, and provide them with all the necessary details for any required follow up.<br />

ALL nominated <strong>incident</strong> owners are recorded in the OmniSafe database, and drop down menu, and given<br />

OmniSafe “CLIENT SERVER” access.<br />

1.4.3 Incident Sponsor<br />

The <strong>incident</strong> sponsor is a department head, a manager, or a director, who is most directly associated with the<br />

line <strong>incident</strong> owner. The seniority of the sponsor depends on the potential risk evaluation of the <strong>incident</strong> or<br />

near miss, as follows<br />

- LOW (department head)<br />

- MEDIUM (manager)<br />

- HIGH (director)<br />

The <strong>incident</strong> sponsor is responsible for ensuring that the <strong>incident</strong> is investigated properly with the appropriate<br />

level of seniority and independence and verifying that actions have been fully completed. The sponsor is the<br />

only person able to close an <strong>incident</strong> in OmniSafe, having satisfied him/herself that the <strong>incident</strong> has been<br />

properly followed up.<br />

1.4.4 HSE Adviser<br />

The HSE adviser will provide advice and support to the Incident Owner and Sponsor in clarifying and applying<br />

this procedure. In addition, where required the HSE Advisor will assist in determining, in consultation with<br />

the Medic/Doctor, the injury <strong>classification</strong>, especially regarding the differentiation between a lost workday case<br />

and a restricted workday case. The HSE Adviser will interpret the guidelines and definitions to ensure that<br />

consistency is applied throughout.<br />

1.4.5 Medic/Doctor (HML)<br />

When a company or contractor employee is injured, or reports sick, the medic or doctor MUST record the<br />

treatment. The treating HML staff, if necessary in consultation with HSE Advisers, determine and recommend<br />

the injury ‘<strong>classification</strong> ’. HML will also ascertain whether the treated illness is occupational (refer to<br />

Appendix H - Occupational Illness Reporting).<br />

The medic/doctor will report the injury in the ‘Health Reporting’ <strong>module</strong> of the OmniSafe system and crossreference<br />

the treatment report with the corresponding <strong>incident</strong> report (seeking HSE advice and help where<br />

required). Following injury treatment, the doctor/medic must ensure that the relevant line supervision is<br />

notified about the injury treatment promptly.<br />

In the case of lost time injuries, the doctor/medic will also notify HSE (or the duty HSE Adviser), the relevant<br />

line manager, or the emergency co-ordinator (EC) immediately.<br />

Note: ALL patient treatment reports are confidential. Consequently, access to the Health Reporting<br />

<strong>module</strong> is restricted to the Chief Medical Officer (CMO), and those to whom the CMO expressly grants<br />

access.<br />

In the case of occupational illness, the medic/doctor will ONLY record the instance of a case by<br />

<strong>classification</strong>, type, and the asset/service unit location in OmniSafe. Detailed treatment data will be withheld<br />

from the OmniSafe database, on separate file. This is to protect patient confidentiality. Follow up<br />

investigation, and findings are determined by the CMO, but records of these investigations retained for later<br />

scrutiny or audit purposes.<br />

Rev. 4.1 - June 2003 Page 5 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

In the event that a company or contractor employee obtained treatment from a 3 rd party medical centre or<br />

practitioner, HML will, where required follow up with that party, to understand the nature of the injury/illness<br />

and treatment to help in advising on injury/illness <strong>classification</strong>, or request for referral of the patient to<br />

Panaga Clinic.<br />

Process<br />

Notification<br />

Evaluation<br />

Investigation<br />

Approval<br />

Close-Out<br />

1.5 Definitions<br />

Term Definition<br />

Responsibility<br />

Raise an <strong>incident</strong> report<br />

Determine investigation level<br />

Establish injury class<br />

Produce investigation report<br />

Create SMART action item<br />

Input action item<br />

Approve investigation report<br />

Complete action item<br />

Approve action item<br />

Close-Out <strong>incident</strong> report<br />

Roles<br />

Reporter<br />

Owner<br />

HML/HSE<br />

Team<br />

Leader<br />

Owner<br />

Owner<br />

Action Party<br />

Owner<br />

Sponsor<br />

Table 1-1: Overview of Roles & Responsibilities<br />

Time<br />

Within 24 hours<br />

Within 2<br />

days<br />

Within 20<br />

working days<br />

Within 1 month<br />

As per target<br />

date<br />

Accident The term is normally used to describe an unplanned event, or chain of events, which has<br />

caused fatalities. In all other cases of injury or illness, the term ‘<strong>incident</strong>’ is preferred – see<br />

later.<br />

Asset<br />

Custodian<br />

A person appointed by the Asset Holder to be the custodian of an asset and to have<br />

management responsibilities for all activities carried out on that asset.<br />

Asset Holder The position that is accorded single point accountability by the Managing Director for all<br />

aspects of the management, including budgetary control, of a clearly defined asset or group<br />

of assets, over part or all of its lifecycle, in order to achieve corporate objectives.<br />

The postholder identified in the BSP Asset Holder list as being responsible for a particular<br />

item or area of BSP property.<br />

Contractor All parties working for the <strong>Brunei</strong> <strong>Shell</strong> Companies either as a direct Contractor or as a subcontractor.<br />

Exposure<br />

Hours<br />

The total number of hours of employment including paid overtime and training but<br />

excluding leave, sickness and unpaid overtime hours. The exposure hours should be<br />

calculated separately for Company and Contractor personnel. Time off duty, even if this<br />

time is spent on Company premises, is not included in the calculation of exposure hours,<br />

but <strong>incident</strong>s during this time are included in the statistics if they are the result of failure or<br />

absence of management controls.<br />

Fatality (FAT) A death resulting from a ‘work related’ injury or occupational illness, regardless of the time<br />

intervening between the <strong>incident</strong> causing the injury or exposure or causing illness and<br />

death.<br />

First Aid<br />

Case (FAC)<br />

Any single treatment and subsequent observation of minor scratches, cuts, burns, splinters<br />

etc. that do not normally require medical care by a physician. Such treatment and<br />

observation are considered First Aid even if provided by a physician or registered<br />

Rev. 4.1 - June 2003 Page 6 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

HSE<br />

Management<br />

Control of<br />

Contractors<br />

professional person. Examples are found in Appendix J - Medical Treatment and First Aid<br />

Cases<br />

HSE Management controls (e.g. contracts, standards) verified by the Contract Holder to<br />

ensure effective HSE Management by the Contractor.<br />

Incident An unplanned event or chain of events, that has, or could have, resulted in injury or illness<br />

or damage to assets the environment or company reputation.<br />

Injury Any injury such as a cut, fracture, sprain, amputation etc., that results from a single<br />

instantaneous exposure.<br />

Lost Time<br />

Injuries (LTI)<br />

Lost Time<br />

Injury<br />

Frequency<br />

(LTIF)<br />

Lost Workday<br />

Case (LWC)<br />

Medical<br />

Treatment<br />

Case (MTC)<br />

Near Miss<br />

(NM)<br />

Occupational<br />

Illness<br />

Permanent<br />

Total<br />

Disability<br />

(PTD)<br />

Reporting<br />

Period<br />

Restricted<br />

Work Case<br />

(RWC)<br />

Road Traffic<br />

Incident<br />

Total<br />

Reportable<br />

Case<br />

Frequency<br />

(TRCF)<br />

Loosely used expression to describe an injury which results in lost work – but more<br />

precisely is the sum of injuries resulting in fatalities, permanent total disabilities and lost<br />

workday cases, but excluding restricted work cases and medical treatment cases. This<br />

parameter is used to generate the lost time injury frequency indicator (LTIF)<br />

A safety performance indicator that gives the frequency of lost time injuries per million<br />

exposure man hours. It is calculated by dividing the total number of lost time injuries (see<br />

above) by the number of exposure hours in millions.<br />

Any work-related injury, which renders the injured person temporarily unable to perform<br />

their normal work or restricted work on any day after the day on which the injury occurred.<br />

Any day includes rest day, weekend day, scheduled holiday, public holiday or subsequent<br />

day after ceasing employment.<br />

This definition deviates from OSHA guidance, which considers restricted work as a lost<br />

workday case.<br />

A single <strong>incident</strong> can give rise to several lost workday cases, depending on the number of<br />

people injured as a result of that <strong>incident</strong>.<br />

Any work-related injury that involves neither lost workdays nor restricted workdays but<br />

which requires treatment by a physician or other medical specialist.<br />

Medical Treatment does not include first aid even if a physician or registered professional<br />

person provides this.<br />

Examples are to be found in Appendix J - Medical Treatment and First Aid Cases<br />

An Incident that could have caused illness, injury or damage to assets, the environment or<br />

company reputation, or consequential business loss but did not.<br />

Any work-related abnormal condition or disorder, other than one resulting from an injury<br />

that is caused by or mainly caused by exposures at work. (50% or more probability that the<br />

illness was caused by exposures at work) Occupational illnesses include acute and chronic<br />

illness or diseases that may be caused by inhalation, adsorption, ingestion or direct contact.<br />

The procedure to determine whether an illness is occupational can be found in Appendix H -<br />

Occupational Illness Reporting<br />

Any work-related Injury that permanently incapacitates an employee and results in<br />

termination of employment.<br />

The period of time covered by the report. Within BSP the LTIF and TRCF statistics are<br />

always presented on a ‘rolling 12 month’ <strong>reporting</strong> period, e.g. all relevant <strong>incident</strong>s and/or<br />

all relevant man hours within the 12 months immediately prior to the report date are<br />

included.<br />

Any work-related injury which renders the injured person temporarily unable to perform all,<br />

but still some, of their normal work on any day after the day on which the injury occurred.<br />

An <strong>incident</strong> involving a vehicle driven by a company or contractor employee, whether on or<br />

off road, that has resulted in injury, illness or damage to assets, the environment or the<br />

Company’s reputation, irrespective of the cost of repair or responsibility for cause.<br />

A safety performance indicator giving the frequency of reportable injuries per million<br />

exposure man hours.<br />

It is calculated by dividing the sum of reportable injury cases by the number of millions of<br />

exposure man hours over a given period (normally 12 months).<br />

Rev. 4.1 - June 2003 Page 7 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Third Parties Persons or organisations, which are not employed by, or contracted to, the Company or<br />

contractor.<br />

Work Related Those activities for which management controls are in place, or should have been in place.<br />

Incidents occurring during such activities must be reported and will be included in<br />

performance statistics.<br />

For consistency in the <strong>reporting</strong> practices of Group Companies, the following activities are<br />

considered to be work related, as they are susceptible to <strong>incident</strong>s with significant impact,<br />

for which company controls should be in place:<br />

• All work by company personnel,<br />

• All work by contractor personnel on company premises, and<br />

• All work by contractor personnel on non-Company premises for which it is concluded<br />

on the basis of risk considerations that company and contractor management controls are<br />

required<br />

For Company personnel, work includes overtime, attending courses, conferences and<br />

Company organised events, business travel, field visits, or any other activity where the<br />

employee’s presence is expected by the employer.<br />

Where it is impossible or inappropriate for the Company to seek to impose management<br />

control on a contractor, exceptions may be justifiable. Examples may be found in areas<br />

where contractor services are not dedicated to the company e.g.<br />

• Manufacturing of components in a factory together with the manufacture of components<br />

for other customers;<br />

• Construction at a contractor’s fabrication site shared by other customers<br />

• Delivery of goods or products to company locations by a contractor who is also employed<br />

to deliver goods or products to other companies during the same journey.<br />

• customer collection of company products, where the vehicle and drivers are under the<br />

control of the customer.<br />

Advice should be sought from the Contract Holder if the reportability of a particular<br />

contractor is in doubt.<br />

Please refer to Appendix D – Examples of ‘Work related’ Incidents<br />

Rev. 4.1 - June 2003 Page 8 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

2 INCIDENT R EPORTING P ROCEDURE<br />

2.1 Overview of the Process<br />

Table 2-1 illustrates the whole <strong>incident</strong> <strong>reporting</strong> process, starting with initial notification, by the reporter,<br />

through to closeout by the sponsor.<br />

NOTIFICATION<br />

Reporter<br />

2.2 Internal Notification<br />

2.2.1 Initiating an Incident Report.<br />

Table 2-1<br />

The reporter needs to complete the Incident Report Form, which is available in the OmniSafe Incident<br />

Reporting System, http://swwbond.bsp.shell.bn/cgi-bin/omniweb.exe/index<br />

Contractors, who do not have access to the company Intra-Web, must use the paper based <strong>incident</strong> report<br />

form, and send it to their Contract Holder. The contract holder must then upload the information into<br />

OmniSafe.<br />

The initial report must capture:<br />

• Where and When the <strong>incident</strong> happened;<br />

• For any injury related <strong>incident</strong>, the number of people injured;<br />

• What happened, i.e. brief description of the <strong>incident</strong>;<br />

• Severity of the <strong>incident</strong> - Actual Consequence & Potential Risk;<br />

• When the <strong>incident</strong> was reported and by whom (for reference purposes only)<br />

2.2.2 Alerting Others in the Company<br />

Incident Reporting Process<br />

EVALUATION<br />

Owner<br />

HEALTH REPORT<br />

HML MEDIC OR DOCTOR<br />

INVESTIGATION<br />

Investigation<br />

Team Leader<br />

Creating<br />

Owner<br />

APPROVAL<br />

Owner<br />

ACTION ITEM<br />

Completion<br />

Action Party<br />

All <strong>incident</strong>s must be reported within 24 hours<br />

CLOSE-OUT<br />

Approval<br />

Owner<br />

‘Investigation’ is addressed in Module 31<br />

Sponsor<br />

Once reported in OmniSafe, the system automatically assigns an Incident Owner, based primarily on the<br />

location, or the contract, and will generate an automatic ‘e-mail’ notifying him/her. All HSE advisors are<br />

notified, and line staff appropriate to the <strong>incident</strong> owner.<br />

In the case of a fatality, lost workday case (LWC), or serious <strong>incident</strong> with damage, or harm to the<br />

environment, the <strong>incident</strong> owner must prepare a ‘newsflash’ indicating:<br />

- Brief description (with an illustrative photograph if possible) of the <strong>incident</strong>, incl.<br />

severity of the injury/damage<br />

- Where the <strong>incident</strong> happened<br />

- Whether the injured person is a contractor or company employee, and how the person<br />

is recovering<br />

- Immediate actions taken, if applicable<br />

- Immediate causes, and any early lessons to be shared<br />

This “newsflash” should be reviewed by an HSE Advisor, and submitted to the company MD for signature.<br />

Then published via HSE/0 in English and Bahasa Melayu, in hard copy, and on the “bulletins” page of the<br />

intraweb.<br />

Rev. 4.1 - June 2003 Page 9 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

An emerging issue has been identified concerning the potential legal implications for BSP and our contractors<br />

as a result of <strong>incident</strong>s involving BSP activities. In particular, any findings attributing causes of <strong>incident</strong>s to<br />

certain implicit shortcomings or negligence of one party can potentially be used in legal court against a<br />

unsuspecting employer ( BSP or contractors)<br />

What precaution should we/contractors be taking in developing, <strong>reporting</strong> and releasing <strong>incident</strong> reports?<br />

In the light of this, all staff need to be cautioned that any communication of an <strong>incident</strong> outside of BSP or in a<br />

wider forum must be done with care (see below note 1). A responsible and acceptable approach is to include<br />

involving contractor or sub contractor key representatives to participate in the investigation into any <strong>incident</strong>s<br />

that are associated with BSP activities. The final investigation report must be jointly signed off by the involving<br />

contractor to confirm their acceptance of the findings and the subsequent recommendations. A positive spinoff<br />

from this is the opportunity for learning from each other between BSP & our contractors.<br />

NOTE 1:<br />

For an <strong>incident</strong> with an ‘actual’ consequence of 3 or above, the <strong>incident</strong> owner must inform LGL<br />

within 48 hours of the <strong>incident</strong>. LGL will assess the need for special precautions related to the<br />

investigation (e.g. document control etc.) and advice the <strong>incident</strong> owner accordingly.<br />

NOTE 2:<br />

For an <strong>incident</strong> with an ‘actual’ consequence 4 or 5, HSE must submit a notification to SIEP-EPA<br />

within 24 hours (see ’Incident, Classification, Investigation and Reporting Feb 2002’ Yellow guide).<br />

For <strong>incident</strong>s with 'potential' consequence 4 or 5, HSE must submit a similar notification format, BUT<br />

it is NOT required to do so within 24hrs, this is to allow for proper determination of the <strong>incident</strong><br />

potential.<br />

2.3 Evaluation (Incident Owner)<br />

The <strong>incident</strong> evaluation must be completed by the Incident Owner within 24hrs<br />

after receiving the <strong>incident</strong> report.<br />

2.3.1 Confirming the Accuracy of the Initial Incident Report<br />

The <strong>incident</strong> owner must confirm the accuracy of the information given in the initial notification, checking<br />

when, where, what, and who was involved. Where a person is hurt, the injury <strong>classification</strong> is determined by<br />

HML, and the <strong>incident</strong> owner must confirm this with the medical department, if the data has not been posted<br />

in OmniSafe.<br />

2.3.2 Evaluate Potential Risk<br />

It is imperative that the <strong>incident</strong> owner assesses the <strong>incident</strong> potential risk carefully as this determines the<br />

seniority of the subsequent <strong>incident</strong> investigation.<br />

The <strong>incident</strong> owner must use the Risk Assessment Matrix, available in OmniSafe, and determine FIRST the<br />

potential consequence of the <strong>incident</strong>, THEN the realistic likelihood of this consequence, based on historical<br />

knowledge (refer to examples in Appendix B- Examples of .) These two combine to reveal the potential risk. If<br />

required, the <strong>incident</strong> owner may involve his HSE Advisor in assisting with this review.<br />

The <strong>incident</strong> owner must:<br />

• edit the report only after careful review<br />

• THEN ‘accept’ the <strong>incident</strong> report in OmniSafe.<br />

The <strong>incident</strong> owner must report all lost workday cases (LWC’s), and <strong>incident</strong>s, including near misses, with a<br />

potential consequence of 3, or higher, to the Line Manager within the 24 hours of the <strong>incident</strong>.<br />

The Line Manager should report all <strong>incident</strong>s with actual consequences rated 4 or 5, to the Company<br />

Managing Director & HSE within 24 hours of the <strong>incident</strong> occurring.<br />

Once the report is accepted, it will be published in the public OmniSafe web server.<br />

Incident investigation leadership is driven by the potential ‘risk’ (refer to Appendix C – Examples of Incident<br />

Potential). A typical level of investigation leader, and sponsor are shown in Table 2-2.<br />

Rev. 4.1 - June 2003 Page 10 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Investigation Level Investigation Team Composition Team Leader Sponsor<br />

Low First line of supervision Sec / Div Head Div / Dept Head<br />

Medium Dept Head + other line staff as required +<br />

HSE advisor<br />

High Manager + Dept Head + HSE Advisor +<br />

Independent person or specialist required.<br />

Table 2-2<br />

2.4 Injury Classification (Medic/Doctor & HSE)<br />

In the event of an ‘<strong>incident</strong> with injury’ report, HML will automatically be informed.<br />

Dept Head Manager<br />

Manager Director<br />

Following a medical examination, and treatment, the treating HML representative must complete a medical<br />

treatment report, and recommend in consultation, where necessary, with an HSE Adviser the injury<br />

<strong>classification</strong> (fatality, lost workday case, restricted workday case, medical treatment case, or first aid case),<br />

(refer to Appendix J - Medical Treatment and First Aid Cases).<br />

The treating doctor/medic will confer with the<br />

• relevant Asset/Service Unit HSE Adviser during normal working hours, and<br />

• the duty HSE Adviser outside normal working hours<br />

The medical treatment report will subsequently be recorded in the Health Reporting <strong>module</strong> of OmniSafe.<br />

This ‘Health Reporting’ <strong>module</strong> report carries a ‘field’ requiring the corresponding <strong>incident</strong> reference number to<br />

be inserted. This ties together the treatment, with the <strong>incident</strong>, and the injury <strong>classification</strong>.<br />

The OmniSafe Health Reporting <strong>module</strong> report can only be raised by the location medic(s), or other staff<br />

appointed by the CMO. Where direct access to OmniSafe is not available or possible, the medic/doctor must<br />

complete a paper hard copy treatment report and send it to HML/3 for uploading into the OmniSafe Health<br />

Reporting Module.<br />

Contractors or sub-contractors must submit their medical treatment report to their Company contract holder<br />

who in turn will advise HML/3.<br />

For any treatment of a work related injury or an occupational illness carried out in a private clinic or<br />

Government hospital, the <strong>incident</strong> owner must inform the HML duty doctor, who will follow up with the<br />

external medical practitioner.<br />

2.5 Incident Investigation<br />

For details of <strong>incident</strong> investigation please refer to BSP-02-procedure-1620 (Module 31 - Incident Investigation)<br />

An investigation report must be submitted for review to the <strong>incident</strong> owner and sponsor<br />

within 20 working days from the date of <strong>incident</strong> notification<br />

The final electronic version of <strong>incident</strong> report must be archived in the OmniSafe system. The Incident Owner<br />

must hold a hard copy.<br />

NOTE: ALL lost workday cases require a ‘formal’ investigation<br />

Rev. 4.1 - June 2003 Page 11 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

2.6 Incident Report ‘Approval’<br />

Once an <strong>incident</strong> report has been fully investigated, the investigation report approved, and the follow up<br />

actions defined and recorded in OmniSafe, the <strong>incident</strong> can be “approved” as either, ‘work related’ or ‘nonwork<br />

related’.<br />

Note: after “approval” the OmniSafe System Administrator can no longer edit the report, WITHOUT<br />

intervention.<br />

2.7 Incident Report ‘Close-Out’<br />

The OmniSafe system automatically notifies the <strong>incident</strong> sponsor via e-mail when all action items in the<br />

<strong>incident</strong> report have been closed.<br />

The Incident Sponsor can only close the approved <strong>incident</strong> report, when ALL the action items recommended out<br />

of the <strong>incident</strong> investigation have been closed. The <strong>incident</strong> sponsor must verify that actions have been done<br />

fully (this will probably be on a selective sampling basis), and then he/she can close the <strong>incident</strong>.<br />

The sponsor must select the <strong>incident</strong> report in OmniSafe, then change the status from ‘Approved (Recordable<br />

or Non-Recordable)’ to ‘Closed’.<br />

2.8 Third Party Notification<br />

2.8.1 Government<br />

For all work related <strong>incident</strong>s involving staff earning B$750 per month or less as described below<br />

Category 1 - fatalities.<br />

Category 2 - injuries or occupational illness where the injured person is totally disabled from earning full<br />

wages at the work at which he/or she was employed for more than 3 consecutive days. This<br />

includes all Lost Workday Cases (LWC) or Restricted Work Cases (RWC) where the injury or<br />

illness occurred as a result.<br />

the <strong>incident</strong> owner must report it within 10 days of the <strong>incident</strong> to the Employment Commissioner of the<br />

<strong>Brunei</strong> Government using the ‘Laws of <strong>Brunei</strong> - Worker’s Compensation Act 1957 - Schedule Form A’<br />

Any oil spill of more than 5m 3 at sea must be reported to the Government Marine Department as per the Oil<br />

Spill Emergency Response Procedure � BSP-02-Procedure-0660<br />

2.8.2 Police<br />

In all cases of a death whether or not work related occurring on Company premises, the <strong>incident</strong> owner must<br />

notify the Royal <strong>Brunei</strong> Police immediately (this may be done in consultation with HRS).<br />

In the event of a motor vehicle, or aircraft, <strong>incident</strong> or accident, which involves injuries to any person or<br />

animal, or damage to any vehicle, aircraft, or property, whether or not these are owned by the Company, or a<br />

third party, it must be reported by the driver to the nearest police station within 24 hours.<br />

� HSE Standard Module 17 – Land Transport BSP-02-standard-1651 and TMS0439 Land Transport Manual<br />

BSP-14.02-standard-003<br />

2.8.3 Department of Civil Aviation (DCA)<br />

All accidents involving aircraft must be reported by BSP SAV Dept. (Aviation Service Department) to the DCA,<br />

with further notification to<br />

• Advisory service for <strong>Shell</strong> Aircraft in London,<br />

• Safety Design Dept. for Aircraft Manufacturer - Relevant information only at Company discretion.<br />

2.8.4 Petroleum Unit<br />

The Company is not obliged to report safety <strong>incident</strong>s to the PU, but will provide information if requested.<br />

The <strong>incident</strong> owner is obliged to report an excursion on produced water effluent quality > 100-mg/l oil in<br />

water, by sending a signed copy of the ‘Variance Control’ via HSE/5.<br />

Rev. 4.1 - June 2003 Page 12 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

3 SYSTEM T RAINING & COMPLIANCE M ONITORING<br />

3.1 OmniSafe Training<br />

Basic OmniSafe Training is provided for:<br />

• Incident Reporters (i.e. every company employee)<br />

• Action Parties<br />

• Incident Sponsors<br />

Advanced OmniSafe training is provided for:<br />

• Incident Owners<br />

• HSE focal points<br />

• HSE Advisors<br />

3.2 Monitoring Compliance with Reporting Procedure<br />

Incident <strong>reporting</strong> procedure compliance is monitored through ‘OmniSafe’ performance indicators as follows:<br />

• Late <strong>reporting</strong><br />

The <strong>incident</strong> is reported more than 1 working day after the date of <strong>incident</strong>.<br />

• Overdue ‘evaluation’<br />

Incident report is accepted more than 2 working days after the report is raised.<br />

• Overdue ‘approval’<br />

Incident report is approved more than 1 month after the <strong>incident</strong> date.<br />

• Overdue follow up action items<br />

Action items still open after the target date.<br />

The System Custodian (HSE/41) extracts statistics related to compliance with the <strong>reporting</strong> procedure from<br />

OmniSafe. The OmniSafe Performance Indicators are used in the Functional/Dept HSE Meeting.<br />

Rev. 4.1 - June 2003 Page 13 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX A - OWNERSHIP OF I NCIDENTS & STATISTICS<br />

Incident Ownership<br />

The “ownership” of <strong>incident</strong>s rests predominantly with the Asset Owner of the facility on which the <strong>incident</strong><br />

occurred, or, where the <strong>incident</strong> occurs outside of Company premises, with the Contract Holder.<br />

The role of the <strong>incident</strong> owner is to ensure that there is the proper level of follow up as judged by the <strong>incident</strong><br />

evaluation, and that the investigation identifies underlying causes and remedial actions.<br />

Example1: A contractor employee working for SCO is carrying out a task under cover of a PTW on CP-7<br />

complex and hurts himself. The ‘<strong>incident</strong> owner’ would be the asset owner for CP-7 (EOP/1), and is<br />

responsible for making sure the <strong>incident</strong> is evaluated, and an appropriate investigation is established.<br />

Example 2: In the above example, the same contractor employee working for SCO is carrying out a task on<br />

the workboat, anchored adjacent to Ampa-9, and injures himself. In this case the ‘<strong>incident</strong> owner’ is the<br />

Contract Holder, who holds influence over the workboat itself.<br />

Example 3: A contractor employee is working in a workshop belonging to the contractor and injures himself.<br />

The ‘<strong>incident</strong> owner’ is the Contract Holder.<br />

HSE Statistic Ownership<br />

The Company party who is adjudged to have the “most” direct HSE management influence or control over the<br />

outcome of the <strong>incident</strong> owns the statistic. In most cases this will be the same as the ‘<strong>incident</strong> owner’. In<br />

some cases it may be another party who has a relation with the <strong>incident</strong> owner but who has more direct HSE<br />

management control and influence.<br />

Example 1: An STL pool car is involved in an accident and is being driven by another user department. The<br />

vehicle is in technically good condition. STL does not have the “most” direct HSE management control over<br />

the driver. The respective user department takes statistic ownership.<br />

Example 2: A visitor to an offshore facility falls and injures himself. The facility owner will be the <strong>incident</strong><br />

owner, and will determine the underlying causes and sponsor the investigation. The investigation will<br />

determine whether the facility or the visitor’s line department had the most direct control or influence over<br />

the <strong>incident</strong>.<br />

Example 3: A contractor employee injures himself in his workshop. The workshop belongs to the contractor<br />

and is used to do work on behalf of the Company under contract. The activity was part of the contract scope.<br />

The Company Contract Holder will own this and the statistic will be assigned to the contract holder’s<br />

department.<br />

Rev. 4.1 - June 2003 Page 14 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX B- EXAMPLES OF ACTUAL CONSEQUENCES<br />

The assessment of an <strong>incident</strong> is divided into two elements:<br />

1. What actually happened and the actual consequences. (If this is level 4 or 5 <strong>reporting</strong> to SIEP is required)<br />

and<br />

2. The potential risk. This requires the assessment od what the potential consequences might have been<br />

and the likelihood of these consequences based on historical data. Together the potential consequence<br />

and likelihood give the potential risk.<br />

Example 1<br />

As part of a HSE Management System development for a Terminal, the following scenario was identified. All<br />

the tanks in a terminal are within bunds. One of the tanks is receiving gasoline from a tanker. The operation<br />

is started at night. The storage tank is overfilled and a large vapour cloud is formed by vaporising gasoline. A<br />

passing vehicle ignites the vapour cloud. A major explosion and fire develop which destroy 10 of the 15 tanks<br />

at the terminal, cause extensive damage, and result in multiple fatalities. Such an accident has occurred<br />

previously in this business sector, and has caused international impact.<br />

The following actual consequence levels were identified: P5, A5, E3, R5<br />

Example 2<br />

The following scenario actually occurs in an operation. All staff of a 24-hour operation use the site/facility<br />

canteen for meals. Poor food hygiene practices leads to contamination of food. Limitations in the<br />

temperature control both in the preparation and storage pending serving fail to kill harmful bacteria and lead<br />

to their multiplication. Significant proportions of staff on all shifts suffer food poisoning and are unable to<br />

carry out their duties causing extensive loss of production.<br />

The following actual consequence <strong>classification</strong> is proposed: P2, A5 due to lost production R4 national<br />

reputation damage due to food poisoning in other business sectors.<br />

Example 3<br />

The following scenario actually occurs in an operation. A manufacturing facility discharges an effluent<br />

containing a harmful substance, which is moderately toxic, very persistent and has a moderate potential to<br />

bioaccumulate. To avoid damage, a concentration of 15 mg/l should not be exceeded in the effluent to the<br />

local environment. Due to increased production levels, the concentration of the substance in the effluent<br />

increases to about 200 mg/l for extended periods of time. As a result the maximum allowable concentration<br />

of the substance in the receiving aquatic environment is exceeded. During routine investigations by the<br />

authorities, the substance is detected in low concentrations in tissues of commercial fish. The fish are<br />

deemed unsuitable for consumption. An investigation points to the effluent from the facility.<br />

As the discharge occurs for extended time periods, it is deemed to have resulted in continual environmental<br />

damage. Massive damage claims and international reputation damage due to similar environmental impacts<br />

have previously occurred in similar companies in our business sector. The following consequence<br />

<strong>classification</strong> is proposed: A5, E4, R5.<br />

Rev. 4.1 - June 2003 Page 15 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX C – EXAMPLES OF I NCIDENT P OTENTIAL<br />

Example 1: During a weekly off loading operation from a supply vessel, a roof section of a container became<br />

detached and fell into the sea striking the vessel on the portside. Containers containing chemicals are<br />

delivered once a month. The potential consequence to people from this <strong>incident</strong> is a single fatality. This<br />

corresponds to a consequence level of 4. A similar <strong>incident</strong> with fatal consequences occurred 3 years ago.<br />

Several times per year local damage occurs as a result of loose items falling during off loading. The Incident<br />

Potentials determined are:<br />

C4(P) - fatality if a person was below falling roof.<br />

D3(A) - equipment damage causes partial shutdown.<br />

C1(E) - slight environmental effect<br />

Example 2: Bus carrying contract cleaning staff fails to stop at security check and hits the security gate.<br />

There were no injuries. There have been previous occasions in company when sudden stops from hitting<br />

obstacles resulted in fractures or bruises. The following <strong>classification</strong>s re appropriate:<br />

D3(P) - injuries from sudden stop: D2(A) - damage to vehicle or obstacles.<br />

Example 3: Mechanical digger severed a live 415 Volt underground cable to a laboratory while excavating to<br />

lay water pipes. There were no injuries.<br />

B4(P) - possible electrocution of driver (one person): C2(A) - loss of ongoing experiment and equipment.<br />

Example 4: Radioactive contamination is found on workbench during routine monitoring. The <strong>incident</strong><br />

would be classified:<br />

B4(P) - internal contamination can lead to cancer, cases are known in industry<br />

E3(E) - repeated breach of statutory rules<br />

Example 5: While trying to jump start a car (12V) with a crane battery (24V) the car battery exploded,<br />

spraying acid on operator. Actual consequences: damage to clothing and car – level 1.<br />

C4(P) –possible permanent eye injury: C2(A) – damage to the car<br />

Example 6: Filing cabinet drawers are opened adjacent to a busy access route in an office. The cabinet<br />

overbalances and falls over, nobody is hurt but people could have been passing.<br />

It has occurred once before in the Operating Unit that someone was seriously hurt by such an accident.<br />

C3(P) - major injury to person passing<br />

Example 7: During 'start-up' an exchanger joint fails releasing an estimated 5-tonne cloud of propane. The<br />

operator jumped away and sprained his ankle.<br />

B5(P) - possible multiple fatalities if the gas cloud had been ignited: B3(A) - damage in case of gas cloud<br />

explosion.<br />

Example 8: During the loading of diesel from a tank, the ship’s hose sprung a leak and the river was<br />

contaminated. The contamination was noted within minutes by an outsider who warned the loading master.<br />

The damage could have been much worse if it had not been spotted so quickly. Small leaks have occurred<br />

earlier in the company, but not a major one.<br />

B3(E) or D2(E) - spills with minor effects have occurred, more serious local effect has not occurred previously<br />

in this company.<br />

D2(R) - local population gets worried about frequent minor spills.<br />

Demonstration of Risk Management: Management of this risk should be demonstrated in a HSE Case.<br />

Example 9<br />

A manufacturing site built pre-1970 contains significant quantities of brown and blue asbestos as fire<br />

retardant and pipe insulation material. No survey has been carried out to identify and label all sources of<br />

asbestos. The insulation may need to be disturbed for maintenance purposes and it is not uncommon for<br />

minor work to be carried out by company maintenance staff without adequate precautions to prevent the<br />

release of dust.<br />

Rev. 4.1 - June 2003 Page 16 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Chronic exposure to asbestos fibres may result in mesothelioma, asbestosis or lung cancer. Cases known in<br />

industry, and may also have occurred in our company (uncertain). Lacking other information, frequency is<br />

classed as C rather than B.<br />

The following risk <strong>classification</strong> is proposed: C4(P) C4(A) due to monetary liabilities to meet claims and<br />

insurance premiums C4(R) resulting from potential negative publicity.<br />

Risk Management: Appropriate risk reduction measures should be incorporated to reduce the risk to ALARP.<br />

Demonstration of Risk Management: Management of this risk should be demonstrated in the HSE Management<br />

System or in a HSE Case.<br />

Example 10<br />

It is decided to drill a number of oil wells in a remote and rather arid area and some 200 employees and<br />

contractors move in and set up a camp. The local population uses ground water for various purposes e.g.<br />

drinking water consumption, watering cattle and small irrigation projects. The company plans to extract<br />

water for drinking water and for various drilling related purposes. The capacity of the aquifer is unknown but<br />

it is possible that demand for ground water might exceed the capacity of the aquifer to recharge and water<br />

levels may decrease below the level to support the usage by the local population. The population have<br />

already voiced their concerns about potential loss of cattle and diminished crop yields to the local mayor. If<br />

the concerns materialise it would result in a major environmental effect (reflecting social impact<br />

considerations), significant reputation damage and moderate compensation claims. This has happened in<br />

our industry sector, although not in this company.<br />

The following risk <strong>classification</strong> is proposed: B4(E) C4(R) B3(A).<br />

Risk Management - Appropriate risk reduction measures should be incorporated to reduce the risk to ALARP<br />

(e.g. aquifer testing, control of water usage).<br />

Demonstration of Risk Management: - Management of this risk should be demonstrated in a HSE Case or in the<br />

HSE Management System, which should include controls identified from a Social Impact Assessment.<br />

Severity<br />

People<br />

0 No health<br />

effect/injury<br />

1 Slight health<br />

effect/injury<br />

2 Minor health<br />

effect/injury<br />

3 Major health<br />

effect/injury<br />

4 PTD or 1 to 3<br />

fatalities<br />

5 Multiple<br />

fatalities<br />

CONSEQUENCES INCREASING LIKELIHOOD<br />

A B C D E<br />

Never Heard of Incident Happens Happens<br />

heard of in has several several<br />

in industry occurred times per times per<br />

industry<br />

in our year in year in a<br />

Company our<br />

Company<br />

location<br />

Assets<br />

Environment<br />

Reputation<br />

No damage No effect No impact<br />

Slight<br />

damage<br />

Minor<br />

damage<br />

Localised<br />

damage<br />

Major<br />

damage<br />

Extensive<br />

damage<br />

Slight effect Slight impact<br />

Minor effect Limited<br />

impact<br />

Localised<br />

effect<br />

Considerable<br />

impact<br />

Major effect National<br />

impact<br />

Massive<br />

effect<br />

International<br />

impact<br />

Rev. 4.1 - June 2003 Page 17 of <strong>30</strong><br />

A<br />

E R


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX D – EXAMPLES OF ‘WORK RELATED’ INCIDENTS<br />

Transportation of Personnel<br />

Work-Related<br />

- Personnel travelling exclusively on Company business using public or private transport from their normal<br />

place of residence or regular place of work to a temporary place of work.<br />

- Personnel travelling in Company-owned or arranged transport.<br />

- Personnel travelling from temporary accommodation e.g. base camp, hotel, guesthouse etc. to a place of<br />

work.<br />

Non Work-Related<br />

- Company and Contractor personnel commuting between home and normal work place on other than<br />

arranged transport.<br />

- Non business-related travel in vehicles which are allocated to employees or Contractor personnel for their<br />

unrestricted personal use.<br />

- Company and Contractor personnel travelling (even at irregular hours) from their home to a regular<br />

assembly point where they are collected in transport specially furnished by their employer.<br />

- Personnel deviating from a business trip for personal reasons provided this does not breach Company<br />

procedures.<br />

Example 1: An employee has a Company vehicle for which he/she has unrestricted personal use. The<br />

employee is due to attend a business meeting at Bandar Seri Begawan on a Tuesday morning. The employee<br />

decides to leave on the Monday evening and break his journey by visiting friends. An <strong>incident</strong> occurs at that<br />

time. It is not work-related.<br />

Example 2: Another employee has to use a pool car for a similar business meeting but persuades the pool<br />

supervisor to breach Company procedures and release the car on the Monday so he/she can visit friends. If<br />

an <strong>incident</strong> occurs at that time it is work-related.<br />

Notes<br />

Where an <strong>incident</strong> occurs during travel in non-Company arranged transport, but the subsequent<br />

investigation shows that Company transport should have been provided (because, for example <strong>incident</strong>s<br />

during this activity could create a negative impact on the Company) then the <strong>incident</strong> should be considered<br />

work-related.<br />

Example 3: A ship’s crew member is travelling ashore by launch for an authorised recreational trip. The<br />

employer is expected to arrange safe transport. Therefore, if an <strong>incident</strong> occurs, e.g. from a collision of the<br />

launch with another vessel, any injuries sustained by the crew member would be considered<br />

work-related.<br />

Transportation of goods and equipment<br />

Work-Related<br />

- Transportation of goods and equipment within Company managed locations.<br />

- Transportation of goods and equipment on Company owned or contracted transport (e.g. trailers, boats,<br />

etc.)<br />

- Transportation of goods and equipment readily identifiable as related to the Company operations. (E.g.<br />

seismic vehicles, land drilling rigs etc.)<br />

Non Work-Related<br />

- Those transport activities which are not primarily dedicated to the supply of goods and equipment for the<br />

Company or its Contractors and which are not readily identifiable as related to Company or its<br />

Contractors and do not present a high risk to the Company (e.g. delivery of mail, use of road, air and sea<br />

freight, Contractors engaged on multi deliveries.)<br />

Transportation of Product<br />

Work-Related<br />

- All <strong>incident</strong>s, which occur to Company employees, and to, Contractors on Company premises or working<br />

under the Company’s management control.<br />

Rev. 4.1 - June 2003 Page 18 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Example: A road haulier is working under a long term contract to deliver a product on the Company’s<br />

behalf. The haulier operates its own HSE-MS, has ISO 9000 and ISO 14001 accreditation and does not work<br />

exclusively for the Company. An <strong>incident</strong>, which occurs during the time the haulier was delivering the<br />

product for the Company, would normally be included in the Company statistics as would the exposure<br />

hours.<br />

- Transportation within Company-managed locations/by Company-managed pipelines.<br />

- Transportation in Company branded road cars.<br />

Non Work-Related<br />

- Any <strong>incident</strong>s to Contractors not working under the Company’s management control.<br />

Rev. 4.1 - June 2003 Page 19 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX E – EXAMPLES OF E XPOSURE H OURS<br />

The following examples are intended to clarify the definition of Exposure Hours, and to give examples where<br />

injuries are considered to be work related even though exposure hours are not being accumulated at the<br />

time of the <strong>incident</strong>.<br />

Example 1: A Company or Contractor employee being on board a manned platform, rig, standby boat,<br />

supply vessel, construction or maintenance barge etc., but not on duty. The person is not engaged in work<br />

tasks and the Company has no management controls in place other than housekeeping risks, hence, this<br />

off-duty time is not counted as Exposure Hours. Nevertheless, an injury occurring during off-duty periods<br />

would be considered a work-related injury if it is the result of failure of Company Controls.<br />

Example 2: An employee sustains an injury in an offshore gymnasium in his off duty time. Management<br />

controls had not been breached. The Injury is not work-related. If the controls had been breached, the<br />

injury would be reportable but the Exposure Hours would not be accumulated.<br />

Example 3: An office worker living in a suburban area who travels to work by public transport. This<br />

person’s Exposure Hours would be the time spent at the office.<br />

Example 4: An office worker living in a suburban area who travels to work in transport arranged by the<br />

Company. This person’s Exposure Hours would be the time spent at the office. However, an injury occurring<br />

to the employee in transport arranged by the Company would be considered a work-related injury.<br />

Example 5: An employee is travelling on Company business but in the employee’s own time, i.e. outside the<br />

employee’s normal working hours. This person’s Exposure Hours would be calculated on the basis of the<br />

normal working week. Nevertheless, an injury occurring to the employee during such transportation would<br />

be considered a work related injury.<br />

Example 6: An employee working scheduled overtime. This person’s Exposure Hours would include all<br />

overtime periods.<br />

Example 7: An office employee working unscheduled extra hours. Whilst in theory such working time<br />

should be treated as in Example 6, it is generally impracticable to keep records of such working time and,<br />

hence, this person’s Exposure Hours should be calculated on the basis of the normal working week.<br />

However, an injury occurring to the employee during such overtime working would be considered a workrelated<br />

injury.<br />

Rev. 4.1 - June 2003 Page 20 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX F - ENVIRONMENTAL I NCIDENTS<br />

The purpose of this section is to illustrate with examples types of Environmental Incidents, and in particular<br />

to clarify what constitutes an environmental <strong>incident</strong>.<br />

Definition and <strong>reporting</strong> of a spill<br />

A spill has been defined as any unexpected loss to water or land of crude oil, condensate, feed stocks,<br />

intermediates, products, or non-aqueous phase process materials irrespective of the amount recovered.<br />

Definition does not include produced water spills.<br />

Spills which are wholly contained by an impervious surface e.g. non-cracked concrete and good condition<br />

bitumen bunds should be excluded. Clay and earth bunds are not considered impervious.<br />

All spills irrespective of quantity should be reported to the line supervisor. Spills greater than 10 litres must<br />

be reported in Omnisafe. Reporting of spills smaller than 10 litres in Omnisafe is discretionary and may be<br />

limited to those where lessons can be learned from the <strong>incident</strong>. Spills less than 10 litres are typically<br />

considered to have a minor effect on the environment. Spills of less than 10 litres are not at this time included<br />

in the oil spill statistics.<br />

Example 1: Crude oil spill during work on pipeline<br />

A large diameter crude oil pipeline in the Terminal was being opened up for maintenance. Because the line<br />

had not been adequately cleared beforehand, around 10m³ of crude oil spilled into the pipe track which was<br />

impervious. The majority ran off into the site drains and was collected in the interceptor system and<br />

recovered. None of the oil passed through the interceptor outfall to the stream or river.<br />

As the spill had caused no environmental damage to the soil or water because it was effectively contained in<br />

the imperbious pipe track and drains, it should still be investigated to prevent recurrence. However it would<br />

not be considered as an environmental <strong>incident</strong> but must be captured in Omnisafe as an <strong>incident</strong>.<br />

If the same spill had occurred under conditions of high rainfall and some of the oil had been discharged<br />

through the outfall and recovered from the stream, the spill should then be counted as an environmental<br />

<strong>incident</strong>.<br />

Example 2: Diesel oil spill from ship<br />

A vessel was berthed in port. Diesel oil was being transferred internally from shore to fuel settling tanks. The<br />

settling tank overflowed spilling diesel onto the deck of the vessel and subsequently approximately 100 litters<br />

went into the harbour. The Oil Spill Response Team was put into operation and the oil was dispersed within<br />

an hour. The Authorities were notified.<br />

This was clearly an environmental <strong>incident</strong>. The fact that the Authorities were involved, and the <strong>incident</strong><br />

attracted local media attention, means that it should also be considered as a reputation <strong>incident</strong>. To avoid<br />

duplication, the <strong>incident</strong> should be classified and reported on basis of the highest rating.<br />

Example 3: Waste paint tins<br />

Three 5 litre tins of liquid paint all partly full were found in a general waste skip, which had been returned<br />

from an offshore installation to a landfill site. The waste was detected by the landfill operator and constituted a<br />

“waste non-compliance”. If it had gone into the landfill this would have breached statutory criteria and could<br />

have led to further investigation.<br />

Although it was spotted before it went in to the landfill, this <strong>incident</strong> should be considered as a minor breach<br />

of statutory criteria, and therefore an environmental <strong>incident</strong>. As there had been previous non-compliances on<br />

that landfill location which had come to the attention of the local press, the impact on reputation should also<br />

be considered.<br />

Example 4<br />

A drum of chemicals is taken to a site ashore where drilling activities are being carried out. During the<br />

process of moving this drum to a suitable storage place using a forklift, it is punctured and the chemicals leak<br />

out into the ground.<br />

In this <strong>incident</strong> the ground has been contaminated as a result of the loss of containment of the chemical and it<br />

should therefore be considered an environmental <strong>incident</strong>.<br />

Example 5.<br />

During operations offshore a valve is inadvertently opened resulting in the unintentional release of<br />

hydrocarbons to the atmosphere via the vent system.<br />

Rev. 4.1 - June 2003 Page 21 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

As it is now our policy not to vent this unintentional release should be considered an environmental <strong>incident</strong>.<br />

Example 6.<br />

A well is being drilled on land near a running stream. In order to manage the drilling mud a pit is correctly<br />

constructed with a plastic lining and sandbags around the perimeter. However, during the night there is<br />

extensive rain and the pit overflows into the stream.<br />

This overflow of the pit into the stream must be considered an environmental <strong>incident</strong> as it has resulted in the<br />

contamination of the stream.<br />

Example 7.<br />

During the removal of some redundant equipment and old batteries from an off shore facility the container<br />

with its contents inadvertently falls into the sea.<br />

This <strong>incident</strong> has two aspects, one is safety and the second is environmental. Both aspects should be<br />

considered during the follow-up. From an environmental perspective consideration needs to be given to any<br />

damage that may have been done to any underlying corals as well as the potential for any chemicals from the<br />

batteries to harm the environment.<br />

Example 8.<br />

Land wells are provided with cellar to collect spills and grease contaminated liquid from the well assembly.<br />

Liquid contained in the cellar is not an environmental <strong>incident</strong> as the cellar is designed for this purpose.<br />

However, during heavy rainfall, well cellar can overflow to the surrounding area and could contaminate the<br />

soil. This is a recordable environmental <strong>incident</strong>.<br />

Example 9.<br />

During the removal of a well cellar for de-commissioning and abandonment, the well cellar was backfilled with<br />

ground water due to the high water table. The water was subsequently pumped out to the nearby river.<br />

In this scenario if it is only groundwater that is being discharged to the nearby river then it does not constitute<br />

an environmental <strong>incident</strong>. However, if there were any contamination of the groundwater from the cellar, then<br />

the discharge of untested and contaminated water into the river would constitute an environmental <strong>incident</strong><br />

breaching our HSE Policy.<br />

Example 10.<br />

During the process of adding mercaptans to LPG some is vented into the atmosphere resulting in a pungent<br />

odour being detected by a member of the public who phones in and complains about the smell. This should<br />

be logged as an environmental <strong>incident</strong> as the emission of chemicals to the atmosphere that create a nuisance<br />

to the public must be considered as ‘pollution’ of the environment.<br />

Example 11.<br />

Where a flare emits dark black smoke for an extended period (say 1 hour or more) this should be logged as an<br />

environmental <strong>incident</strong>. Smoke is a pollutant and although a small puff may still be acceptable extended<br />

periods of black smoke should not be accepted and should therefore be logged as an environmental <strong>incident</strong>.<br />

Example 12.<br />

Emissions from flares if unburnt can have a pungent odour, often of H2S. As a result if the pilots of a flare are<br />

left unlighted this should be considered as an <strong>incident</strong>. Initially it should be seen as a safety <strong>incident</strong> but if<br />

there are any complaints regarding odours it should also be logged as an environmental <strong>incident</strong>.<br />

Rev. 4.1 - June 2003 Page 22 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX G - COMPLAINTS FROM THE P UBLIC<br />

Example 1: Smoking flare stack<br />

A call received from a member of the public had complained that a vent flare at the Refinery Plant was<br />

exceptionally smoky over the weekend. The public living near the Plant has always taken an interest in HSE<br />

issues at the Plant, and the <strong>incident</strong> was discussed at the local community meeting. If on investigation this<br />

proved to be a justified complaint, it should be included as an environmental <strong>incident</strong>. Because of the local<br />

interest it would certainly count as a Reputation <strong>incident</strong>.<br />

Public complaints can be entered into OmniSafe, via the web, as a separate <strong>incident</strong> category.<br />

Rev. 4.1 - June 2003 Page 23 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX H - OCCUPATIONAL I LLNESS R EPORTING<br />

The <strong>Shell</strong> Group and <strong>Brunei</strong> <strong>Shell</strong> want all cases of occupational illness to be reported. The reason for this is<br />

to determine whether illnesses are occurring because of work, and if so, to take measures to try and prevent<br />

them.<br />

What is an occupational illness?<br />

An occupational illness is defined as any abnormal condition or disorder, other than one resulting from an<br />

injury, which is caused or mainly caused by work.<br />

Illnesses and injuries can include the same conditions (e.g. back pain), however the nature of the causative<br />

event or exposure is different. An injury results from a single instantaneous event or exposure, while an<br />

illness results from repeated events or exposures or exposure over a period of time.<br />

Occupational illness categories and examples are listed in Appendix I – Occupational Illness Classification and<br />

ExamplesAppendix I – Occupational Illness Classification and Examples.<br />

Why are we asking you to report possible occupational illnesses?<br />

Health, like safety, is a line management responsibility. It is impossible to manage a problem unless we have<br />

data that give us an idea of the extent of the problem, it’s relative importance, and the resources required to<br />

manage it successfully. Reliable illness data will enable us to learn about health problems among our staff and<br />

to manage them better.<br />

Data from illness reports will not be used as a basis for comparing performance between departments or<br />

companies, or to penalise them in any way. The data is intended to be used by managers to help improve<br />

health performance over time.<br />

In order to have meaningful data on which to base decision making we need to ensure that as many<br />

occupational illnesses as possible that occur are recognised and reported. Employees, supervisors and<br />

managers should all have a strong index of suspicion and not hesitate to refer if they feel that an illness may<br />

be work related. They do not have to be sure that an illness is work related but simply have to have a<br />

suspicion.<br />

Who is responsible for deciding whether an illness is occupational?<br />

The final decision on whether an illness is occupational is made by a <strong>Brunei</strong> <strong>Shell</strong> company doctor with<br />

adequate training or experience in identifying occupational illness.<br />

What is the <strong>reporting</strong> process?<br />

The Minimum Health Management Standards require that <strong>Brunei</strong> <strong>Shell</strong> companies have a reliable system in<br />

place for recognising and identifying occupational illness.<br />

Usually, if an employee or their supervisor or manager suspect an occupational illness, they will arrange an<br />

appointment with a company doctor or medic (offshore). If the doctor or medic feels that there is a likelihood<br />

of occupational illness then they will fill out the <strong>reporting</strong> form, titled “Occupational Health Illness Report”<br />

(which can be found on the HML/8 website) and forward this to the Chief Medical Officer (CMO) at HML.<br />

Guidance on determining whether or not a condition is an occupational illness can be found in Appendix 4 of<br />

the <strong>Shell</strong> Group document “Incident Classification, Investigation and Reporting, Issue 2.0, Feb 2002”. If there<br />

is any doubt, however, doctors or medics should report the case to HML.<br />

Company medics and doctors need to be vigilant when treating workers for the possibility that an illness may<br />

be work related. If they feel that an occupational illness is likely then they should report it to HML.<br />

Some workers will consult a non company doctor for treatment, such as in a private clinic or government<br />

hospital. If the doctor feels that the illness is occupational then ideally they should report directly to HML<br />

(local clinics have received copies of the <strong>reporting</strong> form). Many will not, however, and if the worker or their<br />

supervisor or manager is aware that the illness may be work related then they should arrange a further<br />

appointment with a company doctor to assess this.<br />

On receiving the <strong>reporting</strong> form the CMO at HML will arrange for a review by a <strong>Brunei</strong> <strong>Shell</strong> company doctor<br />

with adequate training or experience in identifying occupational illness to verify whether or not the illness is<br />

indeed occupational. The reviewing doctor may request more information from the referring person and may<br />

arrange to see the worker for a further examination, and occasionally investigations.<br />

Do contractors need to report occupational illnesses?<br />

Companies contracting to <strong>Brunei</strong> <strong>Shell</strong> companies should have a similar system in place to ensure that<br />

occupational illnesses that occur in contracting workers while working for <strong>Brunei</strong> <strong>Shell</strong> companies are<br />

reported to HML.<br />

Rev. 4.1 - June 2003 Page 24 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Contracting companies may choose to use the <strong>Brunei</strong> <strong>Shell</strong> company medics and doctors or they may use their<br />

own medical staff. It is important however that they remain vigilant and ensure that as many occupational<br />

illnesses that occur as possible are captured and reported to HML.<br />

What happens after occupational illnesses are confirmed by HML?<br />

Confirmed occupational illnesses are added to the occupational illness database, commonly referred to as<br />

Total Reportable Occupational Illness, or TROI. All occupational illnesses are reported as part of the HSE<br />

<strong>reporting</strong> process. They are reported in the categories listed in Appendix I – Occupational Illness Classification<br />

and ExamplesAppendix I – Occupational Illness Classification and Examples. The cases are reported in a nonidentifiable<br />

way. The total occupational illness cases per million exposure hours (work hours) is reported as<br />

the Total Reportable Occupational Illness Frequency, or TROIF. The data are used to identify problems and<br />

plan the management of these.<br />

Confirmed cases are only investigated if the worker with the occupational illness gives their consent. The level<br />

and type of investigation depends on the details of the particular case. The worker’s management will be<br />

informed and involved in the investigation, hence the need to obtain the worker’s consent prior to the<br />

investigation. Significant illness cases (defined as those resulting in permanent total disability or death) will<br />

be notified to the business director within 24 hours and the investigation will include a tripod analysis.<br />

Non-accidental deaths.<br />

Non-accidental deaths involving company or contractor employees while at work will be notified to the<br />

business by the CMO within 24 hours and investigated. The same applies to non-accidental deaths outside<br />

normal working hours where there is a reason to suspect a relationship between the death and events or<br />

exposures at work.<br />

Examples of non-accidental deaths that are work related include:<br />

• Where an individual died as the result of exposure to toxic chemicals while at work.<br />

• Where an individual with a major heart problem was not fit to perform the work he was doing,<br />

resulting in his death.<br />

• Where an individual committed suicide and his depression was found to be due to work related<br />

stress factors.<br />

The investigation will follow the guidance included in section 4.2 of the <strong>Shell</strong> Group guide “Incident<br />

Classification, Investigation and Reporting, Issue 2.0, Feb 2002”. The investigation will aim to establish<br />

whether the death was caused by work (in which case it will be recorded in the statistics as work related) and<br />

whether there are any contributing factors which can be remedied.<br />

Communication of lessons learned.<br />

Where an investigation of an illness reveals a significant learning potential, the lessons should be<br />

communicated within the business unit and where applicable to the business. “Significant learning<br />

potential” is defined in section 3.7 of the <strong>Shell</strong> Group guide “Incident Classification, Investigation and<br />

Reporting, Issue 2.0, Feb 2002”.<br />

Rev. 4.1 - June 2003 Page 25 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Assessment of<br />

contractor by<br />

contracting company<br />

doctor (if not using<br />

<strong>Brunei</strong> <strong>Shell</strong> medic or<br />

doctor)<br />

SUMMARY OF REPORTING PROCESS<br />

Case added to<br />

occupational illness<br />

database for<br />

<strong>reporting</strong><br />

Worker/ supervisor/ manager suspects<br />

occupational illness<br />

and/or<br />

Assessment by<br />

<strong>Brunei</strong> <strong>Shell</strong><br />

company medic or<br />

doctor<br />

Medic or doctor feels<br />

that occupational<br />

illness likely<br />

Reporting form<br />

“Occupational Health Illness<br />

Report” completed and<br />

forwarded to CMO at HML<br />

Occupational<br />

illness confirmed<br />

Case<br />

investigated<br />

Assessment by<br />

non-company<br />

doctor (e.g. govt.<br />

hospital or private<br />

clinic)<br />

Rev. 4.1 - June 2003 Page 26 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX I – OCCUPATIONAL I LLNESS C LASSIFICATION AND<br />

E XAMPLES<br />

Note: The list of examples below is not all inclusive.<br />

• Infectious and parasitic diseases:<br />

Food poisoning, legionnaire’s disease, malaria, dengue fever, hepatitis.<br />

• Skin diseases and disorders:<br />

Dermatitis, chrome ulcers, oil acne.<br />

• Respiratory conditions due to dust or toxic agents:<br />

Asthma, rhinitis, bronchitis, asbestosis, silicosis, allergic alveolitis.<br />

• Poisoning (systemic effects of toxic materials):<br />

Poisoning by lead, mercury, arsenic, cadmium, carbon monoxide, hydrogen sulphide, solvents,<br />

pesticides (and many others).<br />

• Upper limb and neck disorders:<br />

Tendonitis, bursitis, repetitive strain injury, raynaud’s phenomenon.<br />

• Back problems and lower limb disorders:<br />

Chronic back pain, sciatica, tendonitis, bursitis.<br />

• Cancers and malignant blood diseases:<br />

Lung cancer, mesothelioma, bladder cancer, leukaemia, lymphoma, skin cancers.<br />

• Disorders due to mental stress:<br />

Depression, anxiety disorders, stress, recurrent tension headaches, irritable bowel syndrome.<br />

• Noise induced hearing loss:<br />

As defined in the SHC Noise Guide.<br />

• Other illnesses and disorders:<br />

Heatstroke, heat exhaustion, sunburn, hypothermia, seasickness, welding flash and other eye<br />

conditions, vibration white finger, caisson disease, benign tumours, non-cancerous blood disorders.<br />

Rev. 4.1 - June 2003 Page 27 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX J - MEDICAL T REATMENT AND F IRST A ID C ASES<br />

Medical Treatment Case (MTC)<br />

The following examples are generally considered medical treatment:<br />

• Treatment of infection<br />

• Application of antiseptics during second or subsequent visit to medical personnel<br />

• Treatment of second or third degree burns<br />

• Application of sutures (stitches)<br />

• Application of butterfly adhesive dressings or steri strips in lieu of sutures<br />

• Removal of foreign bodies embedded in the eye<br />

• Removal of foreign bodies from wounds, if the procedure is complicated because of depth of embedment,<br />

size, or location<br />

• Use of prescription medications, except a single dose administered on the first visit for minor injury or<br />

discomfort.<br />

• Use of hot or cold soaking therapy during the second or subsequent visit to medical personnel<br />

• Application of hot or cold compresses during the second or subsequent visit to medical personnel<br />

• Cutting away dead skin (surgical debridement)<br />

• Application of heat therapy during the second or subsequent visit to medical personnel<br />

• Use of whirlpool bath therapy during the second or subsequent visit to medical personnel<br />

• Positive X-ray diagnosis of fractures, broken bones, etc.<br />

• Admission to a hospital or equivalent medical facility for treatment or observation.<br />

Loss of consciousness<br />

If an employee loses consciousness as the result of a work-related injury, the case must be reported as least as<br />

a MTC, no matter what type of treatment was provided. The rationale behind this is that loss of consciousness<br />

is generally associated with the more serious injuries.<br />

First Aid Cases (FAC)<br />

The following examples are generally considered first aid treatment, i.e. one-off treatment and subsequent<br />

observation of minor injuries:<br />

• Application of antiseptics during the first visit to medical personnel<br />

• Treatment of first degree burns<br />

• Application of bandages during any visit to medical personnel<br />

• Use of elastic bandages during the first visit to medical personnel<br />

• Removal of foreign bodies not embedded in eye if only irrigation is required<br />

• Removal of foreign bodies from wound; if the procedure is uncomplicated, and is, for example by tweezers<br />

or other simple technique<br />

• Use of non-prescription medications and administration of a single dose of prescription medication on the<br />

first visit for a minor injury or discomfort<br />

• Soaking therapy on the initial visit to medical personnel or removal of bandages by soaking<br />

• Application of hot or cold compresses during the first visit to medical personnel<br />

• Application of ointments to abrasions to prevent drying or cracking<br />

• Application of heat therapy during the first visit to medical personnel<br />

• Use of whirlpool bath therapy during the first visit to medical personnel<br />

• Administration of tetanus shots or boosters. However, these shots are often given in conjunction with<br />

more serious injuries. Consequently, injuries requiring these shots may be included in the statistics for<br />

other reasons.<br />

• Negative X-ray diagnosis or laboratory analysis, unless they lead to further treatment.<br />

• Observation of injury during a visit to medical personnel<br />

Rev. 4.1 - June 2003 Page 28 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

A PPENDIX K – SEVERITY (OR CONSEQUENCE) RATING<br />

Severity rating for People<br />

No Description<br />

0 No injury or damage to health<br />

1 Slight injury or health effects (including first aid case and medical treatment case) – Not<br />

affecting work performance or causing disability.<br />

2 Minor injury or health effects (Lost Time Injury) – Affecting work performance, such as<br />

restriction to activities (Restricted Workday case) or a need to take a few days to fully recover<br />

(Lost Workday case). Limited health effects which are reversible, e.g., skin irritation, and food<br />

poisoning.<br />

3 Major injury or health effects (including Permanent Partial Disability and Occupational<br />

Illness) – Affecting work performance in the longer term, such as a prolonged absence from<br />

work. Irreversible health damage without loss of life, e.g. noise induced hearing loss, chronic<br />

back injuries, sensitisation, hand/arm vibration syndrome, repetitive strain injury.<br />

4 Permanent Total Disability or one to three fatalities – From an accident or Occupational<br />

Illness. Irreversible health damage with serious disability or death, e.g., corrosive burns, heat<br />

stroke, cancer (small exposed population).<br />

5 Multiple fatalities – From an accident or Occupational Illness e.g., chemical asphyxiation or<br />

cancer (large exposed population).<br />

Severity rating for Asset Damage<br />

No Description<br />

0 Zero Damage<br />

1 Slight Damage – No disruption to operation (cost less than $10,000)<br />

2 Minor Damage – Brief disruption (cost less than $100,000)<br />

3 Local Damage – partial shutdown (can be restarted but cost up to $500,000)<br />

4 Major Damage – Partial operation loss (2 weeks shutdown costs up to $10,000,000)<br />

5 Extensive damage – Substantial or total loss of operation (cost in excess of $10,000,000)<br />

The total cost (in US$) = consequential (downtime or deferment) cost + repair cost<br />

Severity Rating for Impact on Reputation<br />

No Description<br />

1 Slight Impact – Public awareness may exist, but there is no public concern.<br />

2 Limited Impact – Some local public concern. Some local media and/or local political attention<br />

with potentially adverse aspects for company operations.<br />

3 Considerable Impact – Regional public concern. Extensive adverse attention in local media.<br />

Regional/national policies with political attention. Adverse stance of local government and/or<br />

action groups.<br />

4 National Impact – National public concern. Extensive adverse attention in the national media.<br />

Regional/national policies with potentially restrictive measures and/or impact on grant of<br />

licenses. Mobilisation of action groups.<br />

5 International Impact – International public attention. Extensive adverse attention in<br />

international media. National/International policies with potentially severe impact on access to<br />

new areas, grants or licences and/or tax legislation.<br />

Rev. 4.1 - June 2003 Page 29 of <strong>30</strong>


Module <strong>30</strong> - Incident Classification and Reporting BSP-02.01.05-procedure-1621<br />

Severity Rating for Environment<br />

It is important to stress that the size of environmental release is not always comparable with environmental<br />

impact (e.g. 10 m3 of oil spilt in the ocean could have a different effect to 10m3 spilt in a small river). Also, the<br />

significance of a release varies between local and global effects (e.g. an air emission <strong>incident</strong> might have<br />

negligible environmental impact, but might be a clear breach of prescribed internal standards). A degree of<br />

judgement is thus required.<br />

If in doubt interpreting the severity of environmental consequence, please contact HSE/5 for advice.<br />

No. Description Spills Prod<br />

Water<br />

0 Zero effect - No environmental damage. No<br />

change in the environment. No financial<br />

consequences.<br />

1 Slight effect - Local environmental damage.<br />

Within fence and within systems. Negligible<br />

financial consequences. Compliant with<br />

statutory limits or prescribed internal<br />

standards.<br />

2 Minor effect - Contamination. Damage<br />

sufficiently large to attack the environment.<br />

No permanent effect on the environment.<br />

Minor breach of statutory limits or prescribed<br />

internal standards.<br />

3 Local effect - Limited loss of discharges of<br />

known toxicity. Affecting neighbourhood.<br />

Clear breach of statutory limits or prescribed<br />

internal standards.<br />

4 Major effect - Severe environmental<br />

damage. The company is required to take<br />

extensive measures to restore the<br />

contaminated environment to its original<br />

state. Extended breach of statutory limits or<br />

prescribed internal standards.<br />

5 Massive effect - Severe environmental<br />

damage or severe nuisance extending over a<br />

large area. In terms of commercial or<br />

recreational use or nature conservancy, a<br />

major economic loss for the company. Major<br />

breach of statutory limits or prescribed<br />

internal standards.<br />

Venting / Flaring<br />

Rev. 4.1 - June 2003 Page <strong>30</strong> of <strong>30</strong><br />

-<br />

Very small<br />

spill<br />

1 m 3<br />

Moderate<br />

spill<br />

>10 m 3<br />

Large spill<br />

>100 m 3<br />

Very large<br />

spill<br />

>1000 m 3<br />

Oil in<br />

water<br />

> 40 ppm<br />

Oil in<br />

water<br />

> 100 ppm<br />

Oil in<br />

water<br />

> 1000 ppm<br />

Uncontrolled<br />

event<br />

e.g. vent pipe leak,<br />

maintenance<br />

release<br />

Smoky flare<br />

Continuous for over<br />

one (1) hour<br />

Operational<br />

excursion<br />

without<br />

permission/covered<br />

by variation<br />

Notes:<br />

Guidance on quantification and fate of oil spill for offshore spill is given in<br />

� BSP Emergency Oil Spill Procedure BSP-02-procedure-0660<br />

Guidance on interpreting operational excursions for air emission <strong>incident</strong>s (e.g. compressor trips) is given in<br />

� BSP Venting & Flaring Policy & Guidelines BSP-02-policy-1428<br />

� BSP Venting & Flaring Guidelines (Operations) BSP-71-guidleine-02<br />

Any excursions from operating guidance is a variation and must authorised by line supervision in accordance<br />

with<br />

� Variance Procedure BSP-71-procedure.01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!