ADES CORE ADES MANAGEMENT SYSTEM PDF

DOCUMENT NO: REV: PAGE:...

DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 1 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 DOCUMENT TYPE: PREPARED BY: REVIEWED BY: APPROVED BY: Directive Tariq Kabalan Islam Saleh Mehdi Hamel TITLE: EVENT REPORTING AND INVESTIGATION 1.0 PURPOSE 1.1 This directive defines the process for QHSSE and the relevant Operational and Maintenance Events reporting, classification, and investigation to continuously improve ADES performance and management system. 1.2 Process shall ensure the following: 1.2.1 Adequate and timely recovery measures are deployed to respond to stabilize the situation raised from any QHSSE and the relevant Operational and Maintenance events. 1.2.2 Recording events accurately, consistently and in compliance with applicable obligations. 1.2.3 Events are communicated/ reported by ADES to the appropriate stakeholders as required. 1.2.4 Consistent determination of root causes analysis to ensure the necessary corrective, and preventive actions are taken to avoid occurrence/ recurrence. 2.0 SCOPE 2.1 This directive is applicable to all ADES locations and all subsidiaries and affiliate companies. 3.0 DEFINITIONS AND ACRONYMS 3.1 ADES Reporting Platform – It is the Company’s platform for reporting ADES related events and beyond, ADES uses “SYNERGI LIFE” as a reporting platform. 3.2 QHSSE and Operational and Maintenance Events - Any event occurring during the service provision resulting in a deviation that may or have the potential to negatively impact ADES personnel, processes, assets as well as ADES stakeholders. 3.3 Process Safety – The management of barrier for major accidents hazards as defined by ADES Process Safety Severity Matrix to prevent catastrophic accidents. 3.4 Person in Charge (PIC) - Is the most senior person and have control over work location and or process (i.e.: OIM, STP, Project Manager, etc.) 3.5 Injured Person (IP) – Is the person who sustained the injury. 3.6 Hazardous Situation (HAZS)- An unplanned or undesired situation in which the risks created by an activity’s exposure to a hazard(s) are inadequately controlled leading to potentially cause an accident. 3.7 Near Miss (NM) - An event where no property was damaged, and/ or no personnel injury was sustained; but, where given a slight shift in time or position, property damage, and/ or personal injury or any other loss could have occurred. 3.8 Accident (ACC) - An event resulting in harm/loss for ADES personnel, processes, and assets, as well as ADES stakeholders. 3.9 Fatality (FTL) - A fatality is a work-related injury or illness that results in death. Fatalities are included when calculating the Lost Time Incident (LTI) incidence rate and frequency rate. 3.10 Lost Time Injury (LTI) - A work-related accident (injury or illness) to an employee in which a physician or licensed health care professional recommends days away from work due to the accident. 3.11 Restricted work Case (RWC) - A Restricted Work Case (RWC) occurs when an employee cannot perform all of the routine job functions but does not result in days away from work. 3.12 Medical Treatment Case (MTC) - Any work-related injury or occupational illness requiring medical care or treatment beyond first aid (regardless of the provider of such treatment) that does not result in a Restricted Work Case (RWC) or Lost Time Incident (LTI). 3.13 First Aid Case (FAC) - Any treatment of minor scratches, cuts, burns, splinters and so forth, and any follow-up visit for the purpose of observation. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 2 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 3.14 Occupational Illness - A work related occupational illness is one that is determined by a physician or licensed health care professional to have resulted from exposure to factors related to the employee’s occupation and meets general recording criteria. 3.15 Report Only (RO) - Minor on-job events consultation with the Medic but not requiring any treatment or medication. 3.16 Work Related Injury (WRI) – An injury is work-related anytime an event or exposure in the work environment is the discernible cause or contributes to an injury or illness or significantly aggravates a pre-existing injury or illness. 3.17 Non-work-related Injury (NWRI) - A non-work-related injury is one that has been suffered or sustained outside of working hours and/or outside of any functions relating to the workplace. 3.18 Recordable Injury (RI) - Regardless of where signs or symptoms surface, a case is recordable only if a work event or exposure is a discernible cause of the injury or illness or of a significant aggravation to a pre-existing condition. 3.19 Days Since Last LTI or Recordable Injury (DSLLTI or DSLRI) - Days to be counted since last Lost Time Injury (LTI) or last Recordable Injury are days that the rig was reporting man-hours and no LTI or Recordable Injury occurred. 3.20 Immediate Correction (IC) - The intervention that must take place immediately to respond to an emergency and lead to stabilization (recovery measures). 3.21 Corrective Action (CA) - The action taken to eliminate the causes of an existing nonconformity, defect, or other undesirable situation to prevent recurrence. 3.22 Preventative Action (PA) - The action taken to eliminate the cause of a potential nonconformity, defect, or other undesirable situation to prevent occurrence. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 3 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 4.0 WORKFLOW © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 4 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 5.0 RESPONSIBILITY 5.1 All Employees shall: 5.1.1 Report all detected events to their direct Supervisor/Manager or directly to the PIC if the Supervisor/Manager isn’t available, who by his turn shall report to the PIC. 5.1.2 Cooperate during the events investigations, and as requested/ required. 5.2 PIC shall: 5.2.1 Report the event using ADES Reporting Platform and via other applicable means of reporting. 5.3 Investigation Owner shall: (6.6.4, Investigation Levels, Owners, and Approvers) 5.3.1 Lead the event investigation (Investigation Team Leader). 5.3.2 During the investigation, communicates investigation updates to relevant stakeholders, as necessary. 5.3.3 Ensure completion of the investigation report, and action creation in ADES Reporting Platform. 5.3.4 Follow-up on timely closure of actions. 5.3.5 Review the effective closure of actions in ADES Reporting Platform and approves or requests rework. 5.4 Investigation Approver shall: (6.6.4, Investigation Levels, Owners, and Approvers) 5.4.1 Review the investigation report in ADES Reporting Platform and approves or requests rework. 5.4.2 Close the investigation report after verifying all actions are effectively closed and closures were supported by detailed evidence. 6.0 Directive 6.1 Event Recovery Measures: Once notified, the PIC shall ensure correct recovery measures are immediately deployed, as necessary, the following recovery measures shall be deployed in relation to applicable events: 6.1.1 Medical recovery: Ensure the event scene is secured, made safe, and evidence are collected. Ensure activation of location specific Emergency Response Plan (ERP), as applicable. IP(s) shall always be treated with their best interests in mind. PIC shall regularly ensure that the Medic is monitoring the IP’s condition, as necessary. Shore-based medical support will be used, if deemed necessary; and instructions shall be followed. All treatment shall be recorded in the Medic’s logbook. Upon recovery, PIC shall verify with P&O department that IP have been checked and declared fit to work through the approved medical service providers before returning to work. 6.1.2 Crane accident: All Crane Operators shall be suspended from crane duties until the investigation Owner determines they can resume their duties. Saudi National Crane operators shall immediately handover his Saudi Aramco Heavy Equipment License to the Company Representative until the investigation is completed and shall not operate any heavy equipment for which he may be certified unless his Heavy Equipment License is returned. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 5 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.1.3 Environmental pollution: Ensure activation of location specific Emergency Response Plan (ERP), as applicable. Contain the pollution with onboard facilities to limit the scale of spill. Request external support as per scale of spill evaluation. 6.1.4 Non-productive Time (NPT): PIC shall assess the condition and evaluates the required resources and time to return to operations mode. PIC shall submit a flash report detailing the reason and expected duration of NPT in addition to required shore-based support. 6.1.5 Automotive Accident: Secure the personnel and follow local regulations requirements. Request external support as needed. 6.1.6 Process Safety Accident: Ensure activation of location specific Emergency Response Plan (ERP), as applicable. Contain the event with onboard facilities to limit its scale. Request external support as per situation evaluation. 6.1.7 Material Claim/ Service Rejection (Risk Rating= Moderately high or more): Notify Supply Chain department to suspend upcoming orders from same vendor. till the event is closed (Report/ investigation). Notify Finance department to suspend vendor entitlements till the event is closed (Report/ investigation). 6.1.8 Client Satisfaction: Communicate with the Client Representative to have in-depth understanding of the situation. Apply immediate corrections as required to rectify the Client’s concern(s). 6.1.9 Workplace Violence: Isolate involved personnel to avoid escalation of conflict. Report to P&O as an administrative case. 6.1.10 Bomb Threat/ Attack: Ensure activation of location specific Emergency Response Plan (ERP), as applicable. 6.1.11 Kidnapping/ Hostage Ensure activation of location specific Emergency Response Plan (ERP), as applicable. Follow local regulations requirements after consulting with Corporate Security Manager. 6.1.12 Information Technology Cyber Attack Notify IT department. 6.2 Event Notification: 6.2.1 All events shall be immediately reported to the PIC. 6.2.2 When the event site is under shared supervision with the Client, PIC shall notify the onboard Client Representative after deploying necessary recovery measures. 6.2.3 PIC shall contact and or send an email notification to his direct Supervisor/ Manager. 6.2.4 PIC shall notify QHSSE department, other departments shall be notified when deemed necessary. 6.2.5 All marine related events shall be notified to the Marine Department, who in turn shall report it to the respective Flag State only after liaising with respective Operations Managers. 6.2.6 Local authorities shall be notified with specific events in accordance with the local regulations’ requirements. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 6 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.3 Safety stand-down meeting: 6.3.1 Following any Health and Safety accident, a safety stand-down meeting shall be held at the event location by PIC, as necessary, and logged on the “Daily Report”. 6.3.2 Site PIC shall invite the Client Representative to attend the safety stand-down. 6.4 Drug screening/ testing 6.4.1 Official drug screening/ testing may be initiated after an event. PIC shall obtain Country Management approval before screening or testing. 6.5 Event Reporting: 6.5.1 General requirements PIC shall create and submit the event report on ADES Reporting Platform addressing the below facts as minimum: a. Brief description of the event (type and severity) b. Country and name of the location, rig, facility, yard etc. c. Date and time of occurrence. d. Indication of any injured person(s), including third parties. e. Job title of the injured. f. Initial injuries and treatment given. g. Situation of any injured people at time of report. h. Brief description of asset, environmental, information, or reputation loss, if any. Refer to Synergi User Guide “Event reporting” for Event report creation and submission. Event Report shall be reviewed and approved by the PIC’s direct Supervisor/ Manager. Event Reports shall be automatically distributed internally; with reference to email router setting. 6.5.2 Event brief: When writing event brief in ADES Reporting Platform, the brief shall follow the minimum requirements below: In the event’s title, differentiate between the 3rd Party involved (ADES or Client). Should note the person’s position (e.g., Roustabout / Engineer, etc.) and not the person’s name. Titles should use accurate wording to reflect real facts. LOPC events should first list the liquid/gas (H2S / SBM / OBM / Hydraulic Oil), followed by the (quantity), followed by the leak’s location, followed by a description. If dropped objects are the cause of the event, include the following: a. Dropped object equipment description. b. Weight of dropped object in pounds (lbs.). c. The dropped object height in feet (ft.). d. The location object landed. e. Red Zone or outside Red Zone. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 7 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION f. The cause of the dropped object. g. The Dropped Object Calculator potential severity should be listed. Examples of events briefing: o Engine oil (5 gals.) leaked from dislodged Engine #5 fill hose during 1000hr oil change. o RSB struck on top of the left foot after control line spool rack is mishandled during manual handling operation. o Stop Drop Hammer (3.60lbs) dropped (3.66ft) from FLM in man-rider to rig floor red zone (DROPS calculator indicates FATALITY). 6.5.3 Event Categorization: Any QHSSE event shall be categorized by one of the following categories: Quality Events: A Quality Event is any event occurring during the service provision resulting in a deviation that materially impacts or have the potential to impacts the quality of the service provided. Quality Events include the following sub-categories: a. Client Satisfaction. b. Quality Performance. c. Non-productive Time. d. Vendor Quality. Report all the following events as a “Quality Event” in ADES Reporting Platform: a. Client complaints/ Evaluation comments. b. Client concerns risking a contract continuity. c. public concerns risking ADES Reputation. d. Operation non-productive time. e. Asset damages. f. Revenue losses. g. Rejected vendors’ services. h. Rejected vendors’ supplies. i. Vendor performance deficiencies. Safety Events: A Safety Event is any event occurring during the service provision resulting in a deviation that may or may not impacts the safety and Health of personnel. Safety events include the following sub-categories: a. People injury/ illness. (Including Dropped object) b. Automotive. c. Process Safety. All safety events sub-categories shall be reported as one of the following: a. Hazardous Situation. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 8 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION b. Near Miss. c. Accident. Report all work-related people injury/ illness as “Safety Events” in ADES REPORTING PLATFORM. IP completes their statement regarding the work-related injury/illness. Attach medical documents to the ADES Reporting Platform case. Capture all known information on ADES Reporting Platform Personal Injury form. Do not share personal medical information with external parties unless authorized by Legal Department. Medical reports from work-related injuries required by ADES Customer for classification purposes only should be shared via the official channels. Report a non-work-related people injury/ illness as “Safety Events” in ADES Reporting Platform if: a. The condition is severe enough to require evaluation/treatment at an onshore medical facility. b. The Medic onboard the Rig provides a prescription-strength medication or treatment beyond first aid. c. A medical professional has diagnosed a contagious disease with a high probability of infecting others. NOTE: All other minor non-work-related illnesses can be captured in the medic logbook. The Medic logbook should be reviewed and signed daily by the OIM/STP/PIC. Report all Automotive Events as a “Safety Events” in ADES Reporting Platform: a. Report all events involving an automotive supplied or owned for Company business in ADES Reporting Platform. b. If an injury occurs, report injury consequence in the same case. c. Do not report a stolen automotive or theft from a car as an “Automotive Event”, report these events as a “Security Events”. Report all Process Safety related events as a “Safety Events” in ADES Reporting Platform, Process Safety includes the following: Fire, Explosion or Gas release, Loss of power, Land Rig Move, Marine collision, Stability/ Watertight integrity, Station Keeping, Safety critical asset impairment/ failure, Well control, and Loss of primary containment. Environmental Events: Environmental event is any unintended actual or potential release of substances/ pollutants into the surrounding media (water, land, or air). Environmental Events include the following sub-categories: a. Marine pollution b. Land pollution c. Air pollution Report all Environmental Events in ADES Reporting Platform. Spills on the deck or secondary contained that do not reach the environment shall be reported as Environmental Event but may not be reported to marine authorities. Security Events: Security event is any threat or attack that impacts ADES personnel, and assets. Security Events include the following sub-categories: © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 9 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION a. Perimeter Breach b. Suspicious Package c. Workplace Violence d. Theft e. Sabotage (including Arson) f. Assault (including Piracy) g. Threat/ Ransom h. Kidnapping/ Hostage i. Information Technology Cyber Attack (including Credentials attack, Data breach, Denial of service attacks) Report all Security Events in ADES Reporting Platform. 6.5.4 People Injury Classification: All accidents involving people injury illness shall be classified as follows: On job Fatality (FTL) An on-job injury or occupational illness that results in death. Lost Time Injury/Illness (LTI) An on-job injury or occupational illness that involves one or more days away from work as determined by the company medical provider. Time away from work on the day of the QHSSE Events is not considered in determining Lost Time injury/ illness (LTI). Time spent traveling, undergoing evaluation, awaiting medical evaluation results, or otherwise seeking medical treatment should not be counted as a Lost Time QHSSE Events (LTI) when considering LTI classification. Illness includes diseases or rashes that may be caused by inhalation, absorption, ingestion, or direct contact. The exposure may have taken place over a period of time or resulted from a single QHSSE Events. Some examples include noise induced hearing loss, dust-disease of the lung, respiratory conditions due to toxic agents, poisoning (such as H2S and other gases), disorders due to physical agents (other than toxic materials) such as heatstroke, heat-exhaustion, dehydration, or other environmental factors, and illnesses to medical professionals because of exposure to patients. Restricted Work Case (RWC) An on-job injury or occupational illness that results in restricted work. The employee cannot perform an activity he/she regularly performs at least once a week. (Example: A sprained ankle resulting in a reassignment from a field to a desk job for 5 days.) Does not include restricted work activity limited to the day of injury or illness. Examples of how to determine a restricted work case are: a. Employee is kept from performing one or more of the routine functions (work activities the employee regularly performs at least once a week) of his/her job, or from working the full workday that he/she would otherwise have been scheduled to work. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 10 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION b. A physician or other licensed health care professional recommended that the employee not perform one or more of the routine functions of his/her job, or not work the full workday that he/she would otherwise have been scheduled to work. Medical Treatment Injury/Illness Event (MTC) An on-job injury or occupational illness that is more serious than on-job first aid case (FAC) or occupational illness requiring medical treatment. (Examples: Treatment requiring sutures, prescription medicines, vaccines (hepatitis B, rabies); use of tweezers to remove splinters from eye; rigid means to immobilize part of body.) MTCs include all cases involving: a. Given a one or more doses of prescription medicine. b. Given an “over the counter” medicine at prescription strength. c. Other immunizations that are administered to manage a job-related injury or illness such as Hepatitis B or rabies vaccine. d. Using wound closing devices such as sutures, staples, etc. e. Physical therapy or chiropractic treatment. f. Using devices with rigid stays or other systems designed to immobilize parts of the body (does not include any non-rigid means of support). g. Removing splinters from the eye with tweezers and other complex means. First Aid Injury Event (FAC) Minor on-job injury requiring one-time treatment and subsequent observations. The treatment, even if administered by a physician, doesn’t require medical or surgical follow-up intervention. (Examples: Diagnostic procedures such as x-rays and blood tests. Treatments such as tetanus shots, bandaging, using eye patches, hot or cold compression therapy). Below is the complete list of all treatments considered as first aid. Any minor treatment that is not on the list should be considered as a Medical Treatment Case: a. Using a nonprescription medication at nonprescription strength. b. Administering tetanus immunizations. c. Cleaning, flushing or soaking wounds on the surface of the skin. d. Using wound coverings such as bandages, Band-Aids, gauze pads, etc.; or using butterfly bandages or Steri-Strips. e. Using hot or cold therapy or treatments. f. Using any non-rigid means of support, such as elastic bandages, wraps, non-rigid back belts, etc. g. Using temporary immobilization devices while transporting an accident victim (e.g., splints, slings, neck collars, back boards, etc.) h. Drilling of a fingernail or toenail to relieve pressure or draining fluid from a blister. i. Using eye patches. j. Removing foreign bodies from the eye using only irrigation or a cotton swab. k. Removing splinters or foreign material from areas other than the eye by irrigation, tweezers, cotton swabs or other simple means. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 11 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION l. Using finger guards. m. Using massages (Physical therapy or chiropractic treatment are considered medical treatment.) n. Drinking fluids for relief of heat stress. Report Only/No Treatment (RO) Minor on-job events consultation with the Medic but not requiring any treatment or medication. Non-Work-Related Injury/illness (NWRI) The following types of injury/ illness are NOT considered to be work-related: a. Off-duty injuries occurring in crew accommodations, camp, galley, or away from the work site. b. Symptoms arising on premises totally due to outside factors such as injuries, illnesses, or fatalities due to a naturally occurring factor (hurricane, earthquake, lightning) that is otherwise not related to Rig operations. injury/ illness of this type should not be reported. c. Member of the public, visitors, regulatory agents, employee(s) off duty waiting for transportation to shore or off of the location. d. An injury or illness that results solely from voluntary participation in a wellness program or in a medical, fitness, or recreational activity such as blood donation, physical examination, flu shot, exercise class, racquetball, or other sports activity. e. The injury or illness is the result of the employee eating, drinking, or preparing food or drink for personal consumption. f. An injury to a person assigned by the company to prepare food for company personnel is work- related. g. The injury or illness is the result of an employee doing personal tasks, unrelated to their employment, at the establishment. h. The injury or illness is the result of personal grooming, self-medication for a non-work-related condition, or is intentionally self-inflicted. i. The injury or illness is caused by a motor vehicle accident while the injured is commuting to or from work even if the accident occurs on company property. j. Cold or flu. k. Following an investigation, the injury or illness is determined to have resulted solely from a pre- existing condition, which resulted in signs or symptoms surfacing at work, but were not caused by, exacerbated by, or cannot be linked back to a work activity. l. An injury that results from a natural bodily action or reaction such as walking or bending, coughing, or sneezing, that is unrelated to work. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 12 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.6 Level of investigation: Level of investigation is determined based on Risk Rating, use Appendix A or Appendix B Matrix to rate the risk generated from an event. 6.6.1 Severity Actual and Potential severity shall be identified in accordance with the following: People injury/ illness: Severity is found in the “People” section of the matrix. Automotive accidents: Severity is found in the “Automotive” section of the matrix. Environmental accidents: Severity is found in the “Environment” section of the matrix. For offshore discharge of oil/hydrocarbons can be estimated based on sheen size. The below table may be used in consultation with the Marine Department. Process Safety accidents: Severity is found in the “PSE” section o of the matrix. Non-Productive Time/ Asset damage/ Revenue loss accidents: Severity is found in the “NPT/ Asset Damage/ Revenue Loss” section of the matrix. Client/ Contract/ Reputation accidents: Severity is found in the “Client/ Contract/ Reputation” section of the matrix. Security Events: Use the matrix. to assess severity levels. Assess against People, Automotive, Environment, PSE, NPT/ Asset Damage/ Revenue Loss, and Client/ Contractual/ Reputation. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 13 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.6.2 Likelihood Actual likelihood (Event based) shall be classified based on the rate of event recurrence, while Potential likelihood (Activity based) shall be classified based on the rate of activity recurrence. 6.6.3 Risk Rating Calculation Actual risk rating is the evaluation of actual risk generated due to the event. Actual Risk Rating = Actual Severity * Likelihood (Event Based) Potential risk rating is the evaluation of risk that could have potentially generated due to the event. Potential Risk Rating = Potential Severity * Potential Likelihood (Activity Based) *Red Zone Management - Potential Risk Rating Escalation If Red zone management in place, the potential risk rating regarding People Category shall be calculated as follows: Potential Risk Rating= Potential Severity * Red Zone Compliance Score In the case of red zone was clear of personnel, then Red Zone Compliance Score equals 0, and in the case of red zone was no clear of personnel, then Red Zone Compliance Score equals 5. Red zone management includes DROPS, moving equipment, lifting operations. 6.6.4 Determine Level of Investigation, Investigation Owner, and Investigation Approver: The investigation Levels, Owners, and Approvers shall be automatically determined based on the potential risk rating as detailed in below table. Investigation Levels, Owners, and Approvers Risk Level No Risk Low Medium High Potential Risk 0 1-4 5 - 12 13 - 25 Rating Investigation Event Report Only 1-pager TapRooT® RCA TapRooT® RCA Type PIC’s direct Case Owner PIC Function Manager Supervisor Country Manager/ Case Approver PIC’s Supervisor Function Manager Function Director There are two types of investigation: a. 1-Pager - Local investigation led by PIC using the 1-pager Template (ADES 1-Pager Template). b. TapRooT® RCA - Root Cause Analysis led by Investigation Owner using TapRooT® RCA Template (ADES Root Cause Analysis Template). TapRooT® RCA shall be performed when requested by the Client and or ADES Management even if the request is not as per the investigation level requirement. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 14 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.7 Event investigation: 6.7.1 Investigation Team Selection Investigation owner (Team Leader) shall initiate the investigation by assigning investigation team members. Investigation team members shall consist of qualified Subject Matter Experts (SME) related the event category, such as site supervisors, QHSSE supervisors, Maintenance Supervisor, P&O Specialist, etc. Team members must not be directly involved in the event. All investigation team leaders shall be trained in the TapRooT® investigation methodology. In case an investigation team leader is not trained, a dispensation request shall be submitted to the corporate HSSE Manager for approval. 6.7.2 Investigation Execution: Investigation team shall use the ADES approved investigation methodology for root cause analysis. Investigation team shall attend to the event scene according to the event type. Photographs, sketches, and other supporting documents should be collected as evidence. Interviews shall be held with all personnel involved whether they witnessed the event or not, all witness statements must be in English or translated to English and recorded on the Interview/ Witness statement Form (Witness Statement Form). Interview/witness statement record shall be signed for acknowledgment to confirm accuracy. 6.7.3 Investigation Reporting and Actions Creation: Investigation owner shall ensure completion of the investigation report, and action creation in ADES Reporting Platform. Witness statements, photographs, sketches, and other supporting documents should be attached within ADES Reporting Platform. Investigation report shall be prepared based on the type of investigation. Actions shall be created by Investigation Owner in ADES Reporting Platform “Actions” Tab, in 2 types: a. Corrective action. b. Preventative action. Fleet wide actions shall be assigned as applicable. Additional actions shall be assigned for additional findings which are not classified as a causal factor or root cause. Actions can only be assigned to ADES Reporting Platform users. If the employee is not an ADES Reporting Platform user, actions shall be assigned to their direct Supervisor or Manager. Actions shall be SMARTER. Specific - Who will do precisely what by when? Measurable - Can the action be measured (quantitatively) to see when the action was implemented and see if it fixed the root cause? © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 15 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION Accountable - Is the person responsible for implementing the action assigned? Reasonable - Is this corrective action practical? Timely - Is the due date for the action soon enough, given the consequences of another failure? Effective - Will the action prevent or significantly reduce the odds of this problem happening again? Reviewed – Will this action cause any problems? Has the action been reviewed for unintended negative impacts on the process or the people? Actions closure dates are prioritized based on the criticality of actions: Criticality Priority Due date (Closure) Urgent (UR) P1 Immediate High priority (HP) P2 Within 14 days. Medium priority (MP) P3 Within 45 days. Low priority (LP) P4 Within negotiated date Request for extension is not applicable for P1 actions. 6.7.4 Investigation Peer Review:. Investigation owner shall lead peer review of the draft investigation report with the Country Management (Operations and other applicable Functions) and perform required rework in ADES Reporting Platform according to review results. Investigation approver shall lead peer review of the final investigation report with the Corporate Management (Operations, QHSSE and other applicable Functions) and approve or requests rework in ADES Reporting Platform. 6.7.5 Investigation Report Follow-up, and Closure: Investigation owner shall follow-up on timely closure of actions. Investigation owner shall review the closed actions in ADES Reporting Platform and approves or requests rework. Investigation approver shall close the investigation report after verifying all actions are effectively and timely closed. 6.7.6 Communication of Investigation Results: Investigation reports shall be automatically distributed internally, with reference to email router settings. Investigation reports may be distributed to Client after being reviewed and approved by respective Operations Manager. All relevant lessons learned whether internal or external shall be shared using the approved Safety Alert template (QHSSE Alert Template) through the designated platform for material knowledge sharing (ADES Library, Skills VX, etc.) Each Quarter selected High Potential events shall be reviewed in an Executive Events Review meeting. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 16 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.8 Reporting & Investigation Timeline: Time from Event Action Accountable Immediately Report Event to I direct Supervisor/ Manager All Employees Immediately Secure the scene and take recovery measures as per event type PIC Within 15-30 min. Notify the onboard Client representative PIC Within 2 hrs. Notify his supervisor and the concerned QHSSE supervisor of the event PIC occurred. Start to gather evidence. Within 8 hrs. Submit event report on ADES Reporting Platform, determine the risk PIC rating of the event Within 12 hrs. PIC’s supervisor shall review and approve the report on ADES PIC’s Reporting Platform Supervisor/ (After approval, the event report shall be distributed internally) Manager Within 24 hrs. Submit report on Client Reporting platform when applicable. Country Local authorities shall be notified with specific events in accordance QHSSE with local regulations’ requirements. Manager Within 24 hrs. Confirm event risk rating (including classification when the event Corporate includes people injury/ illness). QM/HSSE Within 24 hrs. In consultation with concerned Operations Manager, ensure completion Marine of any appropriate external notification forms required by local Flag Department regulations. Within +/- 12 hrs. Assign Investigation Team members. Investigation (from report Investigation team to be dispatched to event location. Owner approval) Within 7 Days. Peer review shall be completed for the draft investigation report with the Investigation Country Management (Operations and other applicable Functions) Owner Within 10 Days. Peer review shall be completed for the final investigation report with the Investigation Corporate (Operations, QHSSE and other applicable Functions) Approver Within 14 Days. Approve investigation Report on ADES Reporting Platform. Investigation Approver Within 14 Days. Communicate investigation report with Client (when required). Operations Manager 6.9 Reporting Work Hours: 6.9.1 The Operations Manager shall designate the office administrator, or other individual, to report monthly administrative hours for the relevant cost center. 6.9.2 PIC shall ensure: Monthly work hours are reported to the designated office administrator. Monitor the Days Since Last Lost Time Incident (DSLLTI) and Days Since Last Recordable Incident (DSLRI) monthly from ADES Reporting Platform. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 17 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.9.3 Project Manager shall ensure during project period that work hours are reported to the designated office administrator. 6.9.4 The QHSSE Department shall report information to relevant industry organizations as applicable. 6.9.5 Operational work hours shall be used to measure safety performance of operation under a specific contract and are calculated using the following criteria: On-tour hours worked by ADES personnel and labor contractor personnel who occupy positions usually filled by ADES employees. Hours should also be included for any labor contractor personnel “Third- Party” who work under ADES direct supervision in any of the company units/facilities (i.e., any non-ADES employee occupying a regular crew position and any extra labor contractor-supplied personnel requested by the client and supervised by ADES supervisors). 6.9.6 Total unit Operational hours from the personnel on board (POB) are calculated using the criteria defined in 6.1.1 above. 6.9.7 Administrative personnel hours are calculated using actual hours worked by administrative staff. 6.9.8 Operational man-hours are reported internally by the end of the 5th day of each month. 6.9.9 Monthly information is reported to relevant industry organization, such as the International Association of Drilling Contractors (IADC) as required by membership. 6.9.10 Project work hours are calculated separately from operational work hours and shall be used to measure the safety performance of a specific project where the unit/ facility is handed over to project management and are calculated using the following criteria: Hours worked by project personnel and other department personnel temporarily assigned to project (i.e. operations, maintenance, etc.). Hours should also be included for any labor contractor personnel “Third- Party” who work under project direct supervision in relation to project scope. 6.9.11 Project man-hours are reported internally on weekly basis during project period. 6.10 Injury Rate Calculation: 6.10.1 To calculate the total recordable injury rate (TRIR), use recordable injury data: [(MTO+RWTC+LTI+FTL) multiplied by 200,000 then divided by Total Hours Worked = Recordable Injury Rate]. 6.11 Calculation of DSLLTI and DSLRI: 6.11.1 DSLLTI and DSLRI are accrued for each day when man-hours are being charged to the operation whether the unit/facility is drilling, moving, or undergoing repair or modification. 6.11.2 DSLLTI and DSLRI are continued when an operation moves to a different geo- graphic location. 6.11.3 DSLLTI and DSLRI are continued when unit/facility operations are reassigned to different operating groups. 6.11.4 When the unit/ facility is handed over to project management DSLLTI and DSLRI shall be suspended until the unit/ facility is handed over back to operations management. 6.12 Reporting DSLLTI and DSLRI 6.12.1 PIC shall ensure that DSLLTI and DSLRI status is posted for the unit/facility and updated daily for all personnel to review. 6.12.2 DSLLTI and DSLRI status shall be reported daily to the unit/facility Manager via the morning report or call. 6.12.3 DSLLTI and DSLRI status is obtained on ADES Reporting Platform. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 18 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 6.13 KEY INDICATORS 6.13.1 On-time submission of Event Report on ADES Reporting Platform (Time from event). 6.13.2 On-time completion of Event Investigation Report (Days from Event). 6.13.3 On-time completion of actions by priority (Due date). 6.13.4 On-time submission of man-Hours. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies.  DOCUMENT NO: REV: PAGE: CAMS 01-11-DIR 01-00 19 of 19 CORE ADES MANAGEMENT SYSTEM ORIGINAL ISSUE DATE: REVISON DATE: 13 May 2024 13 May 2024 TITLE: EVENT REPORTING AND INVESTIGATION 7.0 FORMS AND RECORDS 7.1 Event Reports - ADES Reporting Platform - permanently retained. 7.2 Medical reports – original - permanently retained. 7.3 Authority reports – original - permanently retained. 7.4 1-Pager investigation Report. (SAF-40 ADES 1-Pager Template) - ADES Reporting Platform - permanently retained. 7.5 TapRooT® Root Cause Analysis Report. (SAF-39 ADES Root Cause Analysis Template) - ADES Reporting Platform - permanently retained. 7.6 Witness Statements (SAF-17 Witness Statement Form) - permanently retained. 7.7 Safety Alert (SAF-41 QHSSE Alert Template) - ADES Reporting Platform - 2 years. 7.8 Quarterly Executive Events Review MOM - ADES Reporting Platform - 2 years. 7.9 Man-Hours – ADES Reporting Platform - permanently retained. 7.10 Reports to industry organizations – electronic – 3 years. 8.0 REFERENCES 8.1 Appendix A - ADES General Risk Matrix. 8.2 Appendix B- ADES Process Safety Severity Matrix. 8.3 SYNERGI User Guide “Event reporting”. 8.4 IADC – 2018 – ISP – Reporting - Guidelines. 8.5 OSHA – 1904 – Recording and Reporting Occupational Injuries and Illness. © ADES This document is copyrighted, and the content of this document is confidential and intended solely for the recipient. All printed or downloaded versions of this document are uncontrolled copies. Appendix A – ADES General Risk Matrix Rev:01-00 Actual Likelihood (Event based) Severity Level Severity 1 2 3 4 5 People Has happened in Has happened at Has happened NPT/ Client/ (For potential PSE Severity Level Never Heard of in Heard of in ADES or once per the location or more than once Automotive Environment Asset damage/ Contract/ DROPS events use (See PSE Severity the industry industry year in the more than once per year at the Revenue loss Reputation DROPS calculator) Matrix) industry per year in ADES location NPT Increasing Country > 3.0% Multiple fatalities Massive effect (Regional complaints >50% or scale, permanent Medium Medium High High High Asset damage 5 Multiple fatalities Damage cost damage) Level 5 (catastrophic) > $ 1M Termination of Contract > $ 1M > 5000 bbl. (5) (10) (15) (20) (25) Massive (Global concern Revenue loss and media coverage) > $5 M Increasing Country NPT complaints 2.5% - 3.0% 25-50% Fatality, or permanent Major effect (Local scale, High total disability Low Medium Medium High Fatality, or permanent long-term damage, Asset damage Written notice threatening 4 total disability or decades) Level 4 $ 500k- $ 1M termination if not rectified. Damage cost (4) (8) (12) (16) $100k - $ 1M 500 bbl.=>5000 bbl. (20) Revenue loss Major (regional or $500 k - $5 M persistent national concern) Major injury or health Increasing Country effect (LTI or Partial NPT complaints disability) 2.0% - 2.5% 10-25% or Moderate effect (Local Major injury or health Low Medium Medium Medium High Damage cost scale, medium-term Asset damage Verbal advice if breach 3 effect (LTI or Partial $10k - $100k damage, years) Level 3 $ 50k - $ 500k continues, termination disability) (3) (6) (9) (12) (15) or 50 bbl.500 bbl. notice shall be issued. Rollover at speed > 20 Revenue loss kmph $50 k - $500 k Moderate (Medium term national concern) Minor injury or health Increasing Country effect (MTC or RWC) NPT complaints or 1.0% - 2.0% 20 kmph/ Towing $5 k - $50 k concern) required Slight injury or health effect (FAC) NPT Low Country client or < 1.0% satisfaction score 80% BOP operating pressure. Stability incident resulting requiring a rig-wide equipment resulting in an - Kick with pit gain significantly above kick tolerance