AIPS event name Date PIM #XXXXXXX (20XX Tier X #XX)

Slides:



Advertisements
Similar presentations
Accident Investigation vs. First Report of Injury.
Advertisements

Accident and Incident Investigation
A Joint Code of Practice Objectives and Summary Presentation
Accident Investigation Root Cause Analysis
Determining the True Root Cause(s) of Accidents and Safety Incidents Incident Investigation and Analysis.
Learning Objectives  Recognize the need for an investigation  Investigate the scene of the accident  Interview victims & witnesses  Distinguish.
ACCIDENT INVESTIGATION
Bureau of Workers’ Comp PA Training for Health & Safety (PATHS)
ACCIDENT INVESTIGATION
Accident Investigation.
HSE Management System - TRIPOD Presented By: Naman Shah Pakistan Refinery Limited Incident Investigation and Analysis.
Incident Reporting Procedure
Main contractor name – LTI# - Date of incident Incident details Contractor name/number: (subcontractor-contractor- PDO)/CXXXXXX Incident owner: Name /
Basics of OHSAS Occupational Health & Safety Management System
Guidance Notes on the Investigation of Marine Incidents
Discipline Flow Chart Verbal Counseling (Site Directors is responsible for this step) PERFORMANCE IMPROVED YESNO WRITTEN WARNING & ACTION PLAN CELEBRATE.
1. Objectives  Describe the responsibilities and procedures for reporting and investigating ◦ incidents / near-miss incidents ◦ spills, releases, ◦ injuries,
Worker Focused Safety Program Violence in the Workplace Worker Training Module 5.
Accident Investigation Association Members Workers’ Compensation Trust S afety A wareness F or E veryone from Cove Risk Services.
Accident Investigation S afety A wareness F or E veryone from Cove Risk Services.
Main contractor name – LTI# - Date of incident Incident details PDO directorate/dept: (e.g. OSD _OSO_OSO4) Contractor name/number : (subcontractor-contractor-PDO)/CXXXXXX.
Main contractor name – LTI# - Date of incident Incident details PDO directorate/dept: (e.g. OSD _OSO_OSO4) Contractor name/number : (subcontractor-contractor-PDO)/CXXXXXX.
Erman Taşkın. Information security aspects of business continuity management Objective: To counteract interruptions to business activities and to protect.
MSE4 Technical Safety Engineering Framework. Technical Safety Function – Core Activities CFDH Skill pool management Skill-pool health – Job Descriptions,
Main contractor name – LTI# - Date of incident 1 HSE Investigation template and guidance Lost Time and HiPo Incident HSE Incident Investigation guidance.
Risks and Hazards to Consider Unit 3. Visual 3.1 Unit 3 Overview This unit describes:  The importance of identifying and analyzing possible hazards that.
Issues that Matter Notification and Escalation

We always have time to work safely
Incident Reporting And Investigation Program
People and Culture Office Safety, Health and Wellbeing
Civil Contractors Federation ‘2017 Earth Awards’ Submission Template CATEGORIES 1 and 2 ONLY Company Name (NOTE: if an Alliance then the name of the.
Risk Assessment Meeting
Incident Investigations
IAEA E-learning Program
Location, Asset, Date of incident
Incident Management: Recording New Incidents User Guide
Quarry Operator and Contractor Code of Conduct
Practicum: Root Cause Analysis
PDCA Problem Solving Guide
ACCIDENT INVESTIGATION PRESENTATION
Environmental Health and Safety (EH&S) Supplier Awareness Training
HSE Incident Investigation guidance notes
HSE Incident Investigation guidance notes
Incident Investigations
Location, Asset, Date of incident
Incident Reporting And Investigation Program
HSE Investigation template and guidance Lost Time and HiPo Incident
Root Cause Analysis for Effective Incident Investigation
Incident details Contractor name/number : (subcontractor-contractor-PDO)/CXXXXXX Incident owner : Name / Ref Ind Location : Area / unit - (road/yard/station/rig/hoist/plant.
People and Culture Office Safety, Health and Wellbeing
PDO Second Alert Date: Incident: LTI What happened?
HSE Investigation template and guidance Non Accidental Death (NAD)
PDO Second Alert Date: Incident title: Fatality What happened?
Accident Investigation
DMAIC STANDARD WORK TEMPLATE
How to conduct Effective Stage-1 Audit
<project> Governance Meeting
DMAIC STANDARD WORK TEMPLATE
County Wide Safety Program
Civil Contractors Federation ‘2014 Earth Awards’ Submission Template CATEGORIES 1 and 2 ONLY Company Name (NOTE: if an Alliance then the name of the.
EVALUATION OF COUNTERMEASURES PDCA
National Health and Safety Conference October 2018
EVALUATION OF COUNTERMEASURES PDCA
Quality Assurance in Clinical Trials
Accident Investigation.
Radiopharmaceutical Production
CR-GR-HSE-302 Management of change
Management of Change GROUP HSE RULE (CR-GR-HSE-302)
HSE Requirements for Pipeline Operations GROUP HSE GROUPE (CR-GR-HSE-414) EXECUTIVE SUMMARY This rule defines the minimum HSE requirements related to the.
Presentation transcript:

AIPS event name Date PIM #XXXXXXX (20XX Tier X #XX) PHOTO OF FACILITY OR EVENT Investigation Team A B C D E Peer Review A

AIPS Event Summary PDO directorate/asset Directorate/Asset Event owner Name director or other event (incident) owner Location Name location Event date & time Date, time Event type AIPS Tier 1/Tier 2/LOPC/HiPo/HVL Actual risk rating RAM (only for applicable categories and only consequence, not likelihood) Potential risk rating RAM (rating for ALL 4 PEAR categories) Description of Event One liner of the event Injury/Damage/Loss List injury type List quantity of product lost List all direct associated cost and damage (including clean-up cost) List indirect cost (e.g. deferment) PIM ID XXXXXXX Immediate cause Description (to be taken from “Causation”sheet) Key latent mgmt failures List no more than 4 failures (to be taken from “Causation” sheet)

Description of the Event Short to the point description of the event (incident) Include picture if/where relevant This should be free text writing and include the relevant facts explaining what happened to all the relevant parties in a short sharp factual paragraph that describes the incident The description should be in sufficient detail to allow a person who does not know anything about the incident to imagine it. It should only be about what happened and not why it happened. Do not include investigation findings here, simply describe the incident as the investigation has shown it happened. Overview photo/drawing of EVENT

Overview of Damage/Impact ADD PHOTOS/DRAWINGS or FLOWCHARTS (include any further photos in back-up) Only include photos or sketches if they add value explaining the incident or causes. Each photo/sketch must be labeled to explain what it is and why it has been shown. Ensure photos are labeled to explain context (e.g. road looking in direction of; historical photo of plant before fire etc). Ensure all photos are evidenced to the investigation. (have formed part of the investigation) Ensure all photos are of suitable clarity. Include a maximum of four photographs/sketches per page. Do not exceed three pages of photographs, diagrams and sketches

Sequence of Events Date & Time Events INCLUDE summary sequence of events Detailed descriptions to be captured in BACK-UP

Loss of Barrier Assessment Which control/recovery barriers failed or were missing? Include barrier picture if/where relevant Include a bowtie representation if relevant

Key Findings ANY KEY findings relevant to the event (divide these over design/operational/technical, emergency response and supplemental findings) Design Integrity ANY finding Technical Integrity Operating integrity Emergency response Supplemental Findings (any finding that is not directly related to the event, but was encountered during the event)

Causation Immediate Cause Loss of containment ....... Underlying Causes Max 4 to 5 underlying causes Latent Management Failures Max 4 to 5 Latent MGT failures

AIPS Pattern Check (Populate below matrix with the key findings where applicable) Pattern DESIGN INTEGRITY TECHNICAL INTEGRITY OPERATIONAL INTEGRITY #1 Drive for production #2 Training and Development #3 Learning from Incidents #4 Creating Error conditions

Recommendations (Verify that: Action Party Target Date Status 1 2 3 (Verify that: - Recommendations address root causes and a clear action to do - Recommendations are agreed by the action party as well as target date)

Recommendations (from MDIRC/IRC) Action Party Target Date Status 1 2 3 (Verify that: - Recommendations address root causes and a clear action to do - Recommendations are agreed by the action party as well as target date)

Add relevant photos/drawings of EVENT PDO-LFI AIPS-20XX0X PROCESS SAFETY EVENT: Title of the event (Date of event) KEY WORDS: Add relevant key words, e.g. Design Integrity, Tier 1, Materials Corrosion & Inspection, Pipelines WHAT HAPPENED: Description of the event ACTUAL CONSEQUENCE(S): Description of the actual consequence and RAM rating [A3] POTENTIAL CONSEQUENCE(S): Description of potential consequence and RAM rating for all categories if applicable [A3C, P4B] KEY LEARNING(S): List and number all individual learnings and add integrity category (e.g. [DI]) and ensure learnings are endorsed by appropriate CFDH, e.g. 1. Formation water with low resistivity (<100 ohm.cm) can conduct CP (stray) currents. If in any doubt about the potential for water production assume it will occur at some time in the operational life and design for it [DI] 2. Cross-bond of existing Isolation Joints can only be a temporary measure, and needs to be followed by replacement or installation of SSD for earthing [TI] Add relevant photos/drawings of EVENT KEY DISCIPLINES: Add relevant key disciplines, e.g. Process Engineering (UEP1P), Material Corrosion & Inspection (UEC) KEY STANDARDS: Add relevant standards, e.g. PR-1418 Incident Notification and Investigation DEP 80.45.10.10 Design of Pressure Relief, Flare and Vent 20XX-Tier X #XX, PIM XXXXXXX

Back Up

20XX-Tier 1 #XX Process Safety Event MDIRC Initial Update Status on DD MM YYYY PROCESS SAFETY EVENT: Directorate – Title of event (DD MM YYYY) WHAT HAPPENED: Provide short description of the event IMMEDIATE CAUSE: Description of immediate cause PRELIMINARY UNDERLYING ROOT CAUSES: List and describe potential underlying causes of the event, e.g. Stopping the incoming feed by third party supplier happened too late PRELIMINARY LATENT MANAGEMENT FAILURES: List and describe potential management failures of the event, e.g. Inappropriate quality control systems for maintenance and inspection PRELIMINARY LEARNINGS (not CFDH approved yet): List all immediate learnings (note that these learnings are not necessarily complete nor will be approved at this stage), and add integrity category (DI, OI, TI), e.g. Enforce third party communication protocol in the event of an emergency [OI] Monitor the flare KOD level at all times and treat the HH level trip/alarm with the highest priority, even if the unit or plant is down and closed in [OI] INVESTIGATION TEAM: List all investigation team members NEXT MDIRC SCHEDULED UPDATE: DD MM YYYY (within 60 days date of event) Add relevant photos/drawings of EVENT (Provide a copy of the MDIRC Initial Update (Tier 1 only), required within 10 days after notification) 20XX-Tier 1 #XX, PIM XXXXXXX

Recommendations – Asset specific Action Party Target Date Status 1 Add any immediate and/or further asset specific actions 2 3

Overview of Damage (More pictures and description if applicable) Only include photos or sketches if they add value explaining the incident or causes. Each photo/sketch must be labeled to explain what it is and why it has been shown. Ensure photos are labeled to explain context (e.g. road looking in direction of; historical photo of plant before fire etc). Ensure all photos are evidenced to the investigation. (have formed part of the investigation) Ensure all photos are of suitable clarity. Include a maximum of four photographs/sketches per page. Do not exceed three pages of photographs, diagrams and sketches

Witness Statements (Refer to witness statements where applicable)

(Provide Tripod diagram if Tripod has been used in the investigation) (If other method has been used, provide any representation that may come with it)

ICAM Causation description Findings: Immediate Causes   Unsafe Actions IC Ref # ICAM Causation description Justification Acts or conditions precipitating the incident. They usually involve the front-line staff, the consequences are immediate and can often be prevented by design, training or operating systems. See listing in GU612 for immediate causes and their Ref No codes which must be used. No free text allowed under descriptions, to be taken from ICAM document (Provide ICAM tables if ICAM has been used in the investigation)

ICAM Causation description Findings: Immediate Causes   Unsafe Conditions IC Ref # ICAM Causation description Justification Acts or conditions precipitating the incident. They usually involve the front-line staff, the consequences are immediate and can often be prevented by design, training or operating systems. See listing in GU612 for immediate causes and their Ref No codes which must be used. No free text allowed under descriptions, to be taken from ICAM document (Provide ICAM tables if ICAM has been used in the investigation)

ICAM Causation description Findings: Underlying Causes (Human and Workplace) IC Ref # UC Ref # ICAM Causation Description Justification Underlying causes can be classified into two classes. Human factors & Workplace factors. They lead to the immediate causes i.e. they are the catalyst or pathway through which the immediate causes materialise. No free text allowed under descriptions, to be taken from ICAM document (Provide ICAM tables if ICAM has been used in the investigation)

ICAM Causation description Findings: Management System failures (MSF) UC Ref # MSF Ref # ICAM MSF Description Justification for management system failure cited What changes to the management system are needed to prevent a reoccurrence in the future across all sites. They are identified by asking what led to the underlying causes being allowed to exist. No free text allowed under descriptions, to be taken from ICAM document Life Saving Rules - Were LSR breached related to the event? Yes/No (Provide: description which rule was breached, did the breach caused the event, was it a violation or negligent error)