Some accidents are just waiting to happen. How can you learn from incidents?
Register, analyze and learn from incidents, then optimize your barriers and controls
How can you learn from incidents to ensure structured improvements?
Some accidents are just waiting to happen. How can you learn from (near) incidents? It might look simple to learn from an incident, but it’s easier said than done. Which incidents should you act upon, what measures should you take? Is it part of a trend? Which safety control or barrier failed?
Integration of incident analysis and risk management
Near misses and high potential incidents are a very useful source of information to learn where your management system has failed and what the underlying structural reasons are. When you register and analyze incidents it allows you to improve your barriers and make structured improvements across the organization.
How does it work?
Registration of incidents
- reduce the workload of registering incidents with smart forms
- only ask the relevant questions (answer-dependent questions)
- get insight in incidents, near-misses, observations, deviations
- send automatic email notifications
- diagnose incident reports and take appropriate action
- select the right analysis tool for the incident
- store all incidents in a single database
- assign individuals to the investigation team (add users to an incident)
- keep the right people notified
Barrier-based incident analysis
Select an incident analysis method with the right level of sophistication for the incident to understand the underlying causes, using a predefined structure: Timeline, BSCAT (DNV GL), Barrier Failure Analysis (BFA), Tripod Beta, Root Cause Analysis (RCA), TOP-SET RCA (Kelvin TOP-SET). From there on:
- portray evidence on the timeline tool to support the investigation process
- link barrier failure analysis back onto your proactive risk assessment
- standardize the analysis process and report
- create automatic reports with customizable templates
- give front line people the tools to record incidents in a barrier based manner, based on common incident scenarios (SIR)
- guide inexperienced analysts with step-by-step Barrier Failure Analysis (BFA)
- jumpstart your incident analysis by using data from your bowtie
Learning from multiple incidents
- identify which controls fail time and time again
- aggregate incident data
- identify trends in incident data: Which incident scenarios occur most often?
- barrier log shows how a barrier has failed in previous incidents
- create action plans for barriers based on multiple incident learnings
- avoid treating incidents as single cases, aggregate multiple incidents on bowties.
- avoid generic recommendations, link them to your well-defined barriers in your bowtie
- prioritize your recommendations from multiple incidents, based on the risk picture of the bowtie.
The software features making it possible
The features used for this solution:
- link incidents to barriers in a bowtie framework
- various incident analysis methods
- create reports