Incident Management / Analysis

Transcription

1 Tom Dyson Incident Management / Analysis

2 Black & Gus-It may not be the way it seems

3 Rapid Improve Event Steps to a complete Incident Management and Analysis Program Gather Data Evaluate CA Event Entry Incident Analysis Implement CA Conduct Analysis Communicate

4 Incident Management / Analysis The Problem Gathering and Inputting Data Perform RCA or ACA to identify Corrective Actions that will eliminate future events Communication Developing an Analytic Model that can: identify areas of opportunities and/or correlate trends

5 Data Gathering/Entry What type of events are capture Injury/Illness Vehicle/Equipment Near Miss Initial event details entered into Safety Management Enterprise Who When Why What Where

6 Gathering and Inputting Data The Golden Hour Action Timeframe Incident Occurs - Identify nature of Incident Ensure Work Area is Safe As soon as reasonable but must be completed within 1 hour after notification of incident (Golden Hour). As soon as reasonable but must be completed within 1 hour after notification of incident (Golden Hour). Perform Notification of Incident As soon as reasonable but must be completed within 1 hour after notification of incident (Golden Hour). Supervisor or Representative Reports to Scene Perform Internal Updates Gather Data As soon as reasonable but must be completed within 1 hour after notification of incident (Golden Hour). As soon as reasonable but must be completed within 1 hour after notification of incident (Golden Hour). As soon as reasonable but must be completed within 1 hour after notification of incident (Golden Hour).

7 Scene Responder Make the area safe Care for employee Communicate Preserve

8 Safety Management Enterprise System Safety1Source Event Entry OSHA/WC/DOT BBP Information SIF/PSIF Citations/Regulatory Actions Corrective Actions Tracking Communication Statistics/Analytics

9 Data Analysis/Analytics All information is uploaded and updated in real time, no delay. Events have a minimum of 184 data points to analyze. Safety Observations (C2C) can have significantly more. Allows any user to easily analyze data through simple built in graphs, reports, charts and export functions. Communicates with other systems allowing data to be analyzed by business segments and shares information with HR, W.C., and Cyber Security Systems (to name a few).

10 Conduct Analysis

11 Type and Level of Analysis Utilize an Incident Analysis Process Root Cause Sologic Tap Root Apparent Cause 5 Why s 5M The analysis level for all safety events shall be determined as follows: Safety Event Fatality Recordabl e First Aid PSIF Minimum Level of Analysis Root Cause Apparent Cause (or equivalent) Business Segment Discretion Apparent Cause (or

12 Measuring Improvements of I.A. Program Metric Current Goal % of Recordable events verified within 10 days of event being reported % of Recordable events where analysis is complete (investigation sign-off) within 45 days of event being reported % of Recordable events that include non-blank corrective action(s) after investigation is signed off % of Recordable events that include "no information" or "other than listed choices" as cause A root cause analysis will be completed for any PSIF event that results in a LWA. This level of event will be communicated at the ALT level within 10 days of the investigation being signed off in Safety1Source. 54% 41% 26% 90% or higher 90% or higher 80% or higher 62% 10% or lower 100%

13 Analytic Measurements

14 Communication When an event initially occurs Safety Event Notification Status Messages are sent Relays new information discovered Injury Class Change After the incident analysis is completed that outlines corrective actions Red Recordable/LWA Injury Yellow Near Miss/First Aid/PMV Green Good Catch/Informational

15 Corrective Actions In developing Corrective Actions at least one of the top three should be included Elimination Substitution Engineering Controls 15

16 Evaluate Corrective Actions Communicated to all business segments Tracked for completion/implementation Corrective actions shall be evaluated periodically to insure effectiveness. This can be done in a variety of ways. As an example: if the CA involves training, Insight can be used to determine training has been attended by all affected. C2C s can be utilized to evaluate if the training has improved the behaviors or the skills that lead to the event occurring. Evaluated months later to determine if effective