Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 29

Incident Reporting and

Investigation/
Root Cause Analysis
Incident Reporting and Investigation / Root Cause Analysis
Agenda

• Incident Investigation Overview


• Root Cause Analysis
• Purpose
• Steps
• 5 Whys
• Example

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 3


Incident Investigation

• Phase I: Fact Gathering


• Timeline or Chain of Events
• Phase II: Assessment
– Identify Problem (Problem Statement)
– Identify Contributing Causes (Fishbone Diagram, Brainstorming)
– Work down to Root Causes (5-Why Process)
• Phase III: Corrective Actions & Documentation
• Phase IV: Communication of Lessons-Learned
• Phase V: Follow-up

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 4


JLL Incident Reporting and Investigation Requirements

1. All incidents shall be entered into the JLL incident management system within 24 hours
2. Incidents shall be investigated within 5 days and root cause(s) identified
3. Lessons learned shall be completed within 10 days
4. Days away or restricted duty days shall be updated when the employee returns to work
5. Corrective actions shall be tracked to closure in the JLL incident management system
6. Affected employees shall be trained on how to report accidents
7. Those completing incident investigations shall have appropriate experience or training
8. Enforcement authority correspondence shall be uploaded to the incident management system
9. Outcomes and metrics shall be reported to responsible leadership

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 5


What is Root Cause Analysis?

Root Cause Analysis:


Identification and evaluation of the reason for an undesirable condition
or nonconformance; a methodology that leads to the discovery of the
cause(s) of a problem or root cause(s).

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 6


When Do I Need to Conduct an RCA?

Significant EHS Events Requiring an RCA


Injury or work-related illness resulting in more that first aid (aka, Recordable)
Disabling or other Days Away from Work injuries or illnesses
Fatality and/or hospitalization of one or more days

Spill or Release to the Environment of oil or other hazardous materials of a quantity that
requires immediate reporting to a Government Agency

Fire, explosion or similar incident


Receipt of complaint/citation/notice, or Notice of Violation/other written enforcement
Near misses that are medium or high severity, e.g., Violation of JLL Cardinal Rules

NOTE: Conduct an RCA any time a negative event occurs, and your Team needs to understand how it happened.

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


RCA – Step 1: Identify Problem Statement

Identifying the problem statement


• Take time to clearly develop your "problem statement", as how
the problem is described can influence the development of the causes
• The problem statement(s) should not attempt to identify the root problem.
For example, if a site loses power during a lightening storm the problem
statement is NOT “lightening caused the site to lose power”, rather the
problem statement is “The site lost power”
• Don’t state the causes of the problem, but simply identify the problem.

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 8


RCA – Step 2: Identify Contributing Causes

Cause & Effect/Fishbone diagram: Use a structured brainstorming session with a team to
develop the possible causes
Look for causes or themes that appear repeatedly

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


RCA – Step 3: Identify Root Causes

Identify Root Causes


Apparent Cause vs Root Cause
• An apparent cause is the usually most basic reason that a system fails.
• The root cause is the underlying reason for a failure. This is usually the reason behind the apparent
cause.
• Example: You are driving to work in your new car, and suddenly your car sputters and dies with no
warning or other indications of trouble.
• While waiting for AA to arrive, you determine that your car is out of fuel (apparent cause).
• A mechanic later finds that a defective float on the fuel guage always showed the tank at least one-
quarter full (root cause).

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 10


RCA – Step 3: Identify Root Causes

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 11


RCA – Step 3: Identify Root Causes

Root Cause Analysis Tools


• 5 Why Analysis
• Barrier Analysis
• Causal Factor Tree Analysis
• Cause and Effects Analysis
• Change Analysis
• Failure Mode and Effects Analysis
• Fault Tree Analysis
• Pareto Analysis (80/20)
© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 12
RCA – Step 3: Identify Root Causes

Important Conditions for the ‘Whys’


• “Why" is taken to mean "What were the factors that directly resulted in the effect?"
• The real root cause should point toward a process that is not working well or does not exist.
• A key phrase to keep in mind in any 5-Why exercise is "people do not fail, processes do."
• We may observe that causes seem to point towards classical answers such as not enough time, not
enough investments, or not enough manpower. These answers may sometimes be true but in many
cases, they lead to answers that may be out of our control. Therefore, instead of asking the question
why?, ask why did the process fail?

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


RCA – Step 3: Identify Root Causes

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 14


C
RCA – Step 3: Identify Root Causes

Single-Track vs. Multiple-Track RCAs


• Many RCA “forms” or processes rely on a single-track, or one straight line of single
contributing causes responsible for each why (e.g., Domino Effect)
• Simpler, but rarely captures real-life scenarios
• Run the risk of missing an important root cause
• A better process to use is multi-track, accommodating multiple contributing causes
responsible for each why

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


RCA – Step 3: Identify Root Causes

Single-Track

Problem: Car sputters and dies

Why 1 Why 2 Why 3 Why 4 Why 5 Root Cause Recurrence Prevention

No fuel getting to Car is out of fuel Defective float on the Defective float on Replace (warranty repair)
engine fuel gauge the fuel gauge defective float

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 16


RCA – Step 3: Identify Root Causes

Multiple-Track
Problem: Scaffolding Collapsed

Why 1 Why 2 Why 3 Why 4 Why 5 Root Cause Recurrence Prevention

Gust of wind Scaffold was not It was considered scaffold They would have to drill into façade The design drawings Lack of understanding Training of JLL supplier
blew scaffold mechanically tied off anchors could damage and so width of scaffold base was were not verified by a and verification of CDM Project Manager and JLL
over to a listed building newly refurbished building increased by scaffold company, competent person and roles and Facility manager on CDM
façade although this design modification was shared with the responsibilities regulations. Put a system in
clearly inappropriate principal designer or place to review JLL contractors
client (including principal designer)
training on CDM
An incomplete risk Modification to scaffold design done This change was not Lack of communication Enhance communication
assessment was developed as per verbal instruction between communicated to the and lack of inspection through site orientation /
but not reviewed as part of principal contractor site supervisor & principal designer nor program induction, cross party
management of change their subcontractor scaffolder only identified through spot meetings and introduction of
process checks through client spot check process by client.
(JLL)
Principal contractor supervisor Overstepped Delegation of authority Clear lines of communication
instructed changes to the scaffold boundaries of authority not clearly defined and and defined DOA established
(Contrary to his specialist suppliers checked between all parties at
design). commencement of project
Lack of client Lack of supervision and Enhanced management of
supervision of Principal vendor performance contractors and contractor
contractor management selection
Local permissions to gain Lack of detailed planning by ??? and Poor planning and Lack of planning Improved pre-construction
consent for façade drilling Principal contractor, principal communication safety planning
would take weeks and were designer (it was known that a
not considered early scaffold was needed and that the
enough in project building was listed)

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 17


RCA – Step 3: Identify Root Causes

When should you stop asking why?


• Beyond the control of your organization or the company

• Sufficient safeguards in place to ensure prevention of recurrence

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

A warehouse employee has had


enough and decides to leave early

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

Rather than going the correct


route, he decides to take a short
cut through the warehouse.

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

The forklift driver is under


pressure to get finished before the
end of shift and is driving faster
than permitted because the
limiter has been disabled.

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

The warehouse operative


appears in front of the forklift

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

The forklift driver brakes hard

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

The forklift skids on oil on the floor


which has been leaking from the
forklift during the last few days.

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

The unsecured load is thrown


forward, striking the warehouse
operative. He receives a broken leg
and multiple bruises.

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


Example RCA

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved.


References

• Incident Reporting and Investigation global standard (link)


• 5 Why Root Cause Analysis Template (link)
• Incident Investigation and Reporting courses are available in the JLL
Learning Management System

© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 28


© 2021 Jones Lang LaSalle IP, Inc. All rights reserved. 29

You might also like