Normalisation of deviance

IChemE Safety Centre
3 Feb 202053:25

Summary

TLDRThis webinar, hosted by Trish Caron, Director of the IME Safety Center, delves into the concept of 'normalization of deviance', a phenomenon where warning signs are ignored due to complacency. Using the Columbia space shuttle disaster as a case study, the presentation explores how repeated deviations from safety protocols can become normalized, leading to catastrophic outcomes. It also examines historical incidents across various industries to highlight the dangers of this phenomenon and emphasizes the importance of recognizing and addressing deviance to prevent future tragedies.

Takeaways

  • 🚀 The concept of 'normalization of deviance' was introduced by sociologist Diane Vaughan, highlighting the dangers of ignoring warning signs due to complacency or false assumptions of safety.
  • 🔍 The Columbia Space Shuttle disaster serves as a case study for normalization of deviance, where foam insulation damage during launch was initially a concern but later became an accepted risk, leading to catastrophic failure.
  • 📈 NASA's history of debris strikes on shuttles shows a pattern of increasing acceptance of risk, with incidents like the Atlantis shuttle's near burn-through event and the Columbia disaster illustrating the dangers of complacency.
  • 🛠️ The Challenger disaster in 1986 also exemplifies normalization of deviance, where known design flaws in the O-rings were deemed acceptable risks, leading to the explosion and loss of the crew.
  • 🔥 The BP Texas City refinery explosion and the Deepwater Horizon disaster both demonstrate how deviations from standard procedures and confirmation bias can lead to major accidents.
  • 🌋 The Pike River coal mine disaster in New Zealand shows how normalization of high methane levels led to a fatal explosion, despite clear warning signs being ignored.
  • 🛳️ The Costa Concordia cruise ship disaster highlights how routine deviations from safety protocols, such as performing salutes too close to shore, can become normalized and lead to tragedy.
  • 🔍 The importance of monitoring and maintaining safety instruments was emphasized, as failed or ignored instruments can lead to critical information being overlooked, as seen in the Columbia disaster.
  • 🤔 The webinar discusses the need for organizations to focus on proving systems and actions are safe, rather than assuming they are safe until proven otherwise, to prevent complacency and normalization of deviance.
  • 📊 The discussion on measuring safety performance by the absence of incidents can embed normalization of deviance, as the lack of reported incidents is not necessarily evidence of a safe workplace, but could indicate ignored warning signs.

Q & A

  • What is the main topic of the IME Safety Center webinar presented by Trish Caron?

    -The main topic of the webinar is the concept of 'normalization of deviance,' which refers to the phenomenon where warning signs are ignored or become unnoticed over time, leading to potential safety risks.

  • Who introduced the term 'normalization of deviance' and in what context?

    -Sociologist Diane Warren introduced the term 'normalization of deviance' in her 1996 book 'The Challenger Launch Decision,' which was about the Challenger space shuttle disaster.

  • What is the significance of the Columbia space shuttle case study in the webinar?

    -The Columbia space shuttle case study is used to highlight the factors around normalization of deviance, as it is a well-documented incident where such behavior led to the tragic loss of the shuttle and its crew.

  • What was the role of foam insulation in the Columbia space shuttle disaster?

    -The foam insulation from the external tank broke away during launch and struck the left wing of the orbiter, damaging the thermal protection system, which ultimately led to the shuttle's disintegration upon re-entry.

  • How did NASA's response to debris strikes evolve over time, as illustrated by the case studies?

    -Initially, debris strikes were considered a safety of flight issue, but over time they became an accepted risk and were normalized within the organization, leading to a shift in focus from addressing the issue to merely analyzing the probability of damage.

  • What was the initial design specification for the Space Shuttle program and how did it differ from the reality?

    -The initial design specification for the Space Shuttle was to provide routine access to space with around 50 flights per year. However, by 1989, it was only conducting 24 flights a year due to budget overruns and capability issues.

  • What cultural factors within NASA contributed to the normalization of deviance?

    -Cultural factors included a hubris associated with past successes, a rejection of criticism and externally imposed changes, and a focus on proving systems and actions were safe rather than proving they were unsafe.

  • How did the Challenger and Columbia investigations reveal similar cultural issues within NASA?

    -Both investigations found a failure to learn from past incidents, inadequate concerns over deviation from expected performance, and a silent safety program within the human spaceflight area of NASA.

  • What is the importance of leading versus lagging safety performance metrics in identifying normalization of deviance?

    -Leading metrics focus on proactive measures and can help identify potential issues before they become normalized, whereas lagging metrics like incident counts can embed normalization of deviance by focusing on the absence of incidents as a measure of safety.

  • What are some strategies organizations can use to prevent the normalization of deviance, as suggested by the webinar?

    -Strategies include multi-tiered risk assessments, sign-off by competent technical authorities, rewarding the identification of deficiencies, and focusing on leading safety performance metrics.

  • How can the concept of confirmation bias contribute to the normalization of deviance?

    -Confirmation bias can lead individuals to seek out and interpret information in a way that confirms their pre-existing beliefs, potentially normalizing deviance by overlooking or dismissing warning signs that contradict the belief in a safe and successful operation.

Outlines

00:00

🚀 Introduction to IME Safety Center Webinar

Trish Caron, the director of the IME Safety Center, introduces the second member webinar on the topic of 'normalization of deviance.' She outlines the webinar's structure, including the opportunity for audience interaction through chat, and promises to address questions throughout and at the end. The concept of normalization of deviance is introduced, with a historical reference to Diane Warren's work and its significance in the Columbia and Challenger space shuttle disasters. The Columbia case study is highlighted to discuss the consequences of ignoring warning signs, such as equipment malfunctions that are dismissed as false alarms.

05:01

🔍 The Columbia Shuttle Disaster: A Case Study

This section delves into the Columbia shuttle disaster, detailing the mission's history, the launch delay, and the incident involving foam insulation from the external tank damaging the orbiter's thermal protection system. The report from the Columbia Accident Investigation Board is referenced, showing a pattern of foam debris strikes on space shuttles and how they were normalized over time. The narrative describes how NASA's response to these incidents evolved from active concern to acceptance, culminating in the Columbia disaster where the foam strike was not considered an anomaly due to its normalized status.

10:03

🛠️ The Challenger Incident and NASA's Cultural Acceptance of Deviance

The discussion shifts to the Challenger incident, examining the cultural acceptance of deviance within NASA that led to the tragedy. The focus is on the Challenger's o-ring failure, which was a known issue that had been normalized due to previous successful launches despite the risks. The presentation critiques NASA's safety management system, highlighting the lack of problem reporting, trend analysis, and the involvement of experts in critical decisions. It emphasizes the importance of proving safety rather than the absence of danger and reflects on the cultural hubris that contributed to the failure to learn from past incidents.

15:10

📈 Normalization of Deviance in Various Industries

This part of the script broadens the discussion to include normalization of deviance across different industries, citing examples such as the Pike River coal mine explosion, the BP Texas City refinery incident, the Deepwater Horizon disaster, and the grounding of the Costa Concordia. It emphasizes the common thread of accepting deviations from safety standards as normal operating procedures, leading to catastrophic outcomes. The summary serves as a cautionary note on the dangers of complacency and the importance of learning from warning signs.

20:10

🔧 The Dangers of Measuring Safety by Incident Absence

The script addresses the flawed approach of gauging safety performance solely by the absence of incidents, which can mask underlying issues and embed normalization of deviance. It challenges the audience to consider their own organization's methods of monitoring safety, whether they focus on the absence of failure or the presence of success. The section ends with a poll question to engage the audience in reflecting on their safety monitoring systems and their effectiveness.

25:13

🤔 Audience Engagement and Future Webinars

The script concludes with an interactive segment inviting audience questions and comments, acknowledging the earlier audio loss and reviewing some of the questions that were submitted. It also provides information on upcoming webinars, including one on the BP Texas City refinery incident with Dr. Paul Tebow and sessions on lead process safety metrics and the Pike River Mine explosion anniversary. The section encourages sharing of ideas and suggestions for improving webinars and for topics of interest.

30:20

🔄 Balancing Reward and Accountability in Safety Management

The final part of the script explores the challenging balance between rewarding success and identifying safety deficiencies. It discusses the potential unintended consequences of reward systems based on safety outputs like incident rates, which may not accurately reflect the underlying safety culture or the presence of potential risks. The conversation touches on the need to move away from lagging indicators to leading indicators, emphasizing the importance of proactive safety management.

Mindmap

Keywords

💡Normalization of Deviance

Normalization of deviance refers to the phenomenon where unconventional or risky practices become accepted as normal due to repeated exposure, leading to a reduced sensitivity to potential dangers. In the context of the video, this concept is central to understanding the cultural and systemic failures that led to disasters like the Columbia space shuttle incident. The script discusses how repeated foam debris strikes on the shuttles were initially a concern but over time became 'normalized', leading to a disregard for the associated risks.

💡Columbia Accident Investigation Board

The Columbia Accident Investigation Board is a committee that was formed to investigate the Space Shuttle Columbia disaster. The video script mentions this board in relation to the report published in 2003, which detailed the findings on the causes of the Columbia disaster, highlighting the role of normalization of deviance in the incident.

💡Thermal Protection System

The Thermal Protection System (TPS) on a space shuttle is designed to protect the vehicle from the intense heat experienced during re-entry into Earth's atmosphere. In the script, it is mentioned that foam insulation broke away from the external tank and damaged the TPS on the Columbia shuttle, leading to catastrophic consequences. This system's importance and the failure to address repeated foam strikes underscore the normalization of deviance.

💡STS-107

STS-107 refers to the Space Shuttle mission编号, which was the mission during which the Columbia disaster occurred. The script uses this term to discuss the specific events and decisions that led to the tragedy, emphasizing the mission's long duration and the various delays that occurred before its launch.

💡Foam Debris Strikes

Foam debris strikes are incidents where foam insulation from the external tank of the space shuttle breaks off and hits the shuttle during launch. The script provides a history of these strikes, noting that they were initially considered a safety issue but eventually became normalized as an acceptable risk, contributing to the disaster in the case of Columbia's STS-107 mission.

💡Safety Culture

Safety culture encompasses the values, attitudes, and practices that determine the effectiveness of an organization's approach to safety. The video script discusses the safety culture at NASA, highlighting how a lack of proper safety culture and failure to learn from previous incidents contributed to the normalization of deviance and subsequent disasters.

💡Risk Analysis

Risk analysis is the process of evaluating the likelihood and consequences of potential hazards. In the script, it is mentioned that NASA conducted risk analysis on the debris strikes but failed to take appropriate action, instead normalizing the risk as acceptable, which is a key aspect of the normalization of deviance.

💡Confirmation Bias

Confirmation bias is the tendency to favor information that confirms one's existing beliefs or hypotheses. The script discusses this concept in the context of the Macondo well blowout, where test results were misinterpreted to confirm the belief that the cement job was secure, illustrating the danger of confirmation bias in safety-critical decisions.

💡Lead and Lag Metrics

Lead metrics are indicators that suggest future performance, while lag metrics reflect past performance. The script emphasizes the importance of lead metrics in safety management, cautioning against the reliance on the absence of incidents (lag metrics) as proof of safety, which can mask underlying issues that normalization of deviance might have caused.

💡High-Reliability Organizations

High-reliability organizations are those that consistently operate in complex, hazardous environments with a strong focus on safety and reliability. The script implies that NASA and other organizations involved in the incidents discussed should strive to be high-reliability organizations by addressing and learning from the normalization of deviance.

💡Morton Thiokol

Morton Thiokol is the manufacturer of the o-rings that were implicated in the Challenger Space Shuttle disaster. The script refers to Morton Thiokol engineers' concerns about the o-rings' performance in cold temperatures, which were initially considered a deviance but eventually became normalized, leading to the tragic explosion of the Challenger.

Highlights

Introduction of Trish Caron, Director of the IME Safety Center, and her background in engineering and process safety.

Definition of 'normalization of deviance' as a concept introduced by sociologist Diane Vaughan, relating to ignoring warning signs due to desensitization.

The role of normalization of deviance in the Columbia Space Shuttle disaster, with a detailed case study of the incident.

Historical data on foam debris strikes on space shuttles, indicating a pattern of accepted risk over safety.

Challenger incident's influence on the understanding of normalization of deviance within NASA's culture.

Cultural analysis of NASA showing a pattern of ignoring safety warnings and a failure to learn from past incidents.

The impact of budget pressures and staff reductions on safety protocols and the normalization of deviance.

Discussion on the importance of distinguishing between proving systems and actions are unsafe versus proving they are safe.

Examples of normalization of deviance from various industries, including the BP Texas City refinery and the Deepwater Horizon rig.

The concept of confirmation bias in safety management and its role in misinterpreting warning signs.

The Pike River coal mine disaster and the normalization of methane levels as a production issue rather than a safety one.

The challenge of balancing rewarding success with identifying and addressing safety deficiencies within organizations.

The idea of celebrating 'red' on the scorecard, which refers to acknowledging and addressing deficiencies in safety systems.

Importance of leading indicators in safety performance measurement over lagging indicators to prevent normalization of deviance.

Strategies for identifying when deviance may become normalized within an organization and the effectiveness of these systems.

Upcoming webinars on safety topics, including the BP Texas City refinery incident and the Pike River Mine explosion.

Transcripts

play00:02

hello and welcome to the IME Safety

play00:05

Center webinar this is the second member

play00:08

webinar we have hosted and we plan to

play00:10

host many more in the future

play00:12

my name is Trish Caron and on the

play00:14

director of the ikm Safety Center

play00:16

I joined IQ me to lead development of

play00:19

the IQ in January 2014 prior to that I

play00:22

had a career working in engineering

play00:23

operations and Process Safety in the oil

play00:26

and gas and chemical industries the

play00:33

topic for this webinar is normalization

play00:35

of deviance

play00:36

as we progress through the webinar

play00:38

you'll be able to ask questions or make

play00:40

comments by typing in the chat box on

play00:42

the right hand side of your screen

play00:43

please make sure you select entire

play00:45

audience so everyone can see your

play00:47

comments we will endeavor to answer your

play00:50

questions both during and at the

play00:52

conclusion of the presentation so what

play01:01

is normalization of deviance the concept

play01:04

of normalization of deviance was raised

play01:06

by sociologist Diane Warren in her 1996

play01:10

book the Challenger launch decision

play01:13

following this and the Columbia incident

play01:16

she was then invited to join the

play01:17

Columbia accident investigation board

play01:20

the concept of normalization of deviance

play01:23

is basically not taking heed of warning

play01:25

signs because you just don't notice them

play01:27

this warning signs anymore for example

play01:29

you may have a piece of equipment that's

play01:31

constantly in an alarm state you either

play01:33

stop noticing the alarm or justify that

play01:36

it's okay because it's a false alarm

play01:38

rather than address what's causing it

play01:41

you may miss the real alarm by always

play01:44

assuming it's false we're going to talk

play01:50

a little bit about the columbia space

play01:51

shuttle as a case study here and this

play01:54

case study has been chosen to highlight

play01:56

the factors around normalization of

play01:58

deviance as it's a very clearly

play02:00

documented incident in the Columbia

play02:02

accident investigation board report

play02:04

which was published in 2003 Columbia was

play02:10

on its 28th flight and

play02:12

113 space shuttle mission it was

play02:15

designated space transportation system

play02:18

sts-107 it was a long mission of 16 days

play02:22

in orbit sts-107 was initially scheduled

play02:27

for launch in May 2000 but this was

play02:30

delayed until January 2003 for various

play02:34

reasons shuttle launches can be delayed

play02:36

over time and they basically maintain

play02:41

that original designation so in this

play02:43

instance for example sts-112 flew before

play02:47

sts-107 during the launch when the

play02:52

external tank disconnected from the

play02:54

orbiter foam insulation broke away from

play02:56

what's called the bipod ramp and struck

play02:59

the left wing of the orbiter during the

play03:02

investigation into the incident it was

play03:04

determined this foam damaged the thermal

play03:06

protection on the orbiter the thermal

play03:09

protection is designed to protect the

play03:11

orbiter during the extreme heat build-up

play03:14

that occurs on re-entry into the Earth's

play03:16

atmosphere this table taken from the

play03:25

Columbia accident investigation board

play03:27

report volume 1 shows a history of major

play03:30

foam debris strikes on space shuttles

play03:32

there were 14 instances in all when

play03:35

significant damage occurred or there was

play03:37

a large foam loss looking at mission

play03:41

sts-27 are with Atlantis the Atlantis

play03:45

orbiter suffered a near burn through

play03:47

event when it lost a thermal tiles due

play03:50

to excessive foam debris strikes on

play03:54

mission STS 35 this appears to be when

play03:57

NASA started to define debris hits as a

play04:00

reuse or turnaround issue rather than

play04:03

just a safety of flight issue mission

play04:08

STS 50 appears to be when debris strikes

play04:10

become an accepted risk in the

play04:12

organization STS 56 is when strikes are

play04:17

now considered commonplace and

play04:18

acceptable mission sts-112 also suffered

play04:23

a significant debris strike

play04:25

in this instance it was not even

play04:26

considered to be an anomaly because

play04:28

there are now the situation where phone

play04:30

strikes are expected on launch when

play04:34

finally mission sts-107 in January of

play04:40

2003 with the Columbia launch occurred

play04:43

the Columbia broke up on re-entry after

play04:46

suffering tile damage from the foam

play04:48

debris impact and to burn through events

play04:51

which led to the orbiter becoming

play04:53

unstable the shuttle program was delayed

play05:00

in its early phases due to issues with

play05:02

the thermal tiles in fact as they were

play05:05

developing the design of the orbiter

play05:07

that took a very long time to install

play05:09

the tiles and they would often fall off

play05:12

after installation and have to be

play05:13

reinstalled this led to new adhesives

play05:16

being developed to ensure that the tiles

play05:19

actually stayed in place damage to the

play05:23

thermal tiles was initially a concern to

play05:25

NASA and they started to develop a

play05:27

method for repairing the tiles in orbit

play05:29

but this was unsuccessful and eventually

play05:32

they cancelled these efforts they were

play05:35

also unable to stop the throne shedding

play05:37

issue so interestingly rather than

play05:39

focusing on making the orbiter more

play05:43

resistant to impact strikes they

play05:45

actually put a lot of effort into

play05:47

analyzing the probability of damage they

play05:50

then didn't do anything with this risk

play05:52

analysis they basically just analyzed it

play05:56

the repair program as well as a visual

play05:59

inspection of the orbiter after launch

play06:00

was reinitiated following the Columbia

play06:03

loss the visual inspections are or were

play06:08

achieved in the last launches of the

play06:10

shuttle system either via satellite

play06:13

ground-based imagery or if the orbiter

play06:16

was docking at the International Space

play06:18

Station it was observed by the space

play06:21

station crews visually before docking to

play06:23

see whether there was any damage to be

play06:25

concerned about and therefore

play06:27

potentially repair whilst in orbit this

play06:34

image here

play06:35

shows you the space shuttle in its

play06:38

entirety so the Space Shuttle term

play06:40

refers to the orbiter the external tank

play06:42

and the solid rocket boosters the orange

play06:46

tank in the middle is the external tank

play06:48

and the small red circle at the top is

play06:51

where the bipod ramp is this is where

play06:53

the phone breaks off when the shuttle

play06:56

actually launches and the external tank

play06:59

separates the red circle down towards

play07:03

the bottom is the debris strike region

play07:05

where the Columbia was actually struck

play07:07

with the foam that had broken away and

play07:11

this is actually Columbia on its launch

play07:14

pad prior to launch

play07:15

in 2003 the Space Shuttle design project

play07:21

started in earnest in 1972 it was

play07:24

initially designed to be a routine form

play07:26

of transport to orbit with around 50

play07:28

flights per year and commercial

play07:30

contracts to launch satellites to assist

play07:32

with its funding however by 1989 it was

play07:35

only conducting 24 flights a year the

play07:38

budgeting for the system was overrun and

play07:40

it was not generating the expected

play07:42

revenue due to capability issues the

play07:46

shuttle however was declared operational

play07:48

in 1982 and ready to provide economic

play07:51

and routine access to space this was

play07:54

more for political purposes because the

play07:56

system was proving difficult to operate

play07:57

with more maintenance required between

play07:59

flights than had been expected rather

play08:02

than leading the 10 working days

play08:03

projected in 1975 to process a return to

play08:07

orbiter for its next flight by the end

play08:10

of 1985 an average of 67 days had

play08:15

elapsed before a shuttle was ready for

play08:17

launch the original design specification

play08:23

also did not include protection from

play08:25

debris strikes

play08:26

therefore the occurrence of a debris

play08:28

strike was a violation or deviance from

play08:31

the specification in fact even as the

play08:33

shuttle orbits earth whilst in orbit it

play08:39

actually orbits in a reverse and

play08:41

upside-down direction to protect its

play08:43

sensitive areas so that it doesn't

play08:45

suffer debris impacts from anything

play08:48

in the Earth's orbit as well

play08:54

normalization of deviance in NASA

play08:56

predated the Columbia incident there are

play08:59

striking similarities with the cultural

play09:01

acceptance of deviation but extended

play09:04

back to the challenger incident

play09:06

Challenger or mission STS 51 L had been

play09:10

delayed several times and pressure was

play09:12

mounting for launch there was also a lot

play09:16

of media focus and the space shuttle

play09:18

program was striving to become more

play09:20

relevant so some of you may remember

play09:22

that space shuttle Challenger actually

play09:25

had a middle school teacher on board

play09:27

because they were going to try and raise

play09:30

the profile of the space program by

play09:34

engaging with students and schools all

play09:35

over America the schedule was put a head

play09:39

of engineering considerations that the

play09:41

ambient temperature was outside previous

play09:42

experience and the o-rings became

play09:45

brittle in lower temperatures the chief

play09:48

engineer was actually told to take his

play09:49

engineering had often put his management

play09:51

on to make a launch decision when the

play09:53

engineers from the o-ring manufacturer

play09:55

raised concerns about the temperature of

play09:59

launch the NASA safety program was

play10:03

infective and remained silent the onus

play10:05

was on the contract engineers to prove

play10:08

that it was unsafe rather than a focus

play10:10

on proving it was safe

play10:12

prior to STS 51 L when the o-ring began

play10:16

behaving in unexpected ways rather than

play10:19

testing the joint NASA and Morton

play10:21

Thiokol the manufacturer came to see the

play10:24

deviation as an acceptable flight risk a

play10:26

violation of design that could be

play10:28

tolerated

play10:29

the Challenger investigation also found

play10:32

that the safety management system in

play10:33

particular elements involving problem

play10:35

reporting trend analysis interpretation

play10:38

of criticality and involvement of

play10:40

experts in critical decisions were all

play10:42

severely lacking thinking about your own

play10:45

organizations do you focus on proving

play10:48

systems and actions are unsafe or

play10:50

proving they are safe and it's a very

play10:53

important distinction between those two

play10:59

while there were recommendations to

play11:01

address the cultural issues following

play11:02

Challenger the human spaceflight area of

play11:06

NASA remained largely unaffected human

play11:09

spaceflight was the area responsible for

play11:12

managing the shuttle program this led to

play11:15

inadequate concerns over deviation from

play11:17

expected performance silent safety

play11:19

program and schedule pressure being

play11:23

entrenched in the organization this was

play11:27

compounded by budget pressure and a

play11:29

reduction in staffing that had occurred

play11:30

during all of this culturally there's a

play11:34

hubris associated with success

play11:37

regardless of the Challenger incident

play11:39

itself this was the organization that

play11:41

had put a man on the moon and developed

play11:43

the space shuttle program miss then it

play11:46

was not possible for them to believe

play11:47

failure could occur in their culture the

play11:50

culture rejected criticism

play11:51

recommendations and externally imposed

play11:54

changes the findings of both Challenger

play11:57

and Columbia investigations are similar

play12:00

from a cultural perspective very clearly

play12:03

a failure to learn there some thermal

play12:11

protection areas are so fragile file

play12:13

they can be damaged with a fingernail

play12:16

engineers were quoted as saying that if

play12:18

they had known the external tank was

play12:20

going to produce the debris shower that

play12:21

occurred on launch they would have had a

play12:23

very difficult time clearing Columbia

play12:25

for launch over the life of the program

play12:29

up to sts-107 orbiters landed with an

play12:33

average of 143 divots on upper and lower

play12:36

surfaces with 31 of these everything

play12:39

over one inch in one dimension efforts

play12:43

were made to modify the foam and bipod

play12:45

connectors but when this proved too

play12:47

difficult the word ik c s-- eventually

play12:50

the damage was seen as merely a delay in

play12:53

preparation for the next flight rather

play12:55

than a safety of slight issue for the

play12:57

current flight because after all the

play12:59

previous orbiters had all returned

play13:01

safely

play13:07

sts-112 which flew a few months before

play13:10

sts-107 suffered a bipod ramp foam

play13:14

shedding incident which resulted in a

play13:17

three inch by 4 inch dodge in the foam

play13:19

on one of the solid rocket boosters this

play13:21

was a very big warning signal that was

play13:24

normalized it was not even recognized as

play13:26

an in-flight and long link with each

play13:30

successful landing engineers and

play13:32

managers regard the phone shedding and

play13:34

inevitable and unlikely to impact on

play13:36

safety that is it had become an

play13:38

acceptable risk as the acceptance of

play13:47

debris strikes increased the one in

play13:49

which they were handled changed

play13:50

significantly after the discovery of a

play13:53

debris strike on flight day two of

play13:55

sts-27 are with Atlantis in 1988 the

play14:00

crew was immediately directed to inspect

play14:02

the orbiter using its space arm while so

play14:05

able to view some of the damage they

play14:07

weren't actually able to see that there

play14:09

was a missing tile the location of where

play14:12

the tile was lost was fortunately a much

play14:14

thicker aluminum plate which prevented a

play14:17

total burn through though the orbiter

play14:19

skin that was damaged on return to the

play14:21

atmosphere the engineers were surprised

play14:25

at the extent of the damage when that

play14:27

shuttle actually landed 707 impacts with

play14:31

298 of them greater than 1 inch and a

play14:34

missing tile as the commander had said

play14:37

it looked like she'd been lasted with a

play14:38

shotgun 14 years later when a debris

play14:43

strike was discovered on flight day 2 of

play14:45

sts-107 with Columbia shuttle program

play14:48

management declined to inform the crew

play14:50

or have them inspect the orbiter for

play14:52

damage they declined multiple requests

play14:55

for on-orbit imaging to inspect the

play14:57

tiles on the orbiter and ultimately they

play15:01

discounted the possibility of a burn

play15:03

through interestingly debris strikes

play15:09

continued to be an issue for the shell

play15:11

program up until its final mission this

play15:14

photo shows some thermal tile damage

play15:16

from the final shuttle mission STS

play15:18

one three five with Atlantis the orbiter

play15:21

Atlantis is on display at Kennedy Space

play15:23

Center in the condition she landed in

play15:25

and this sort of damage is very evidence

play15:27

if you ever have the opportunity to see

play15:30

one of the shuttles on display it was

play15:39

standard protocol for high-resolution

play15:41

footage of launches to be examined for

play15:43

anomalies the team reviewing the footage

play15:46

were concerned there may have been

play15:47

damage to the thermal tiles due to the

play15:49

debris strike multiple requests were

play15:52

made to inspect the orbiter during the

play15:54

mission the first was a request for the

play15:57

crew to do a visual inspection that

play15:59

request to the engineering Directorate

play16:00

was never answered three separate

play16:04

requests were made over several days to

play16:06

obtain high-resolution footage of the

play16:07

orbiter in orbit to determine if there's

play16:10

any damages concern each of these

play16:12

requests was eventually rejected as

play16:14

being unnecessary without images the

play16:18

debris assessment team could only

play16:20

estimate using mathematical models which

play16:22

were actually not designed for that

play16:24

purpose to postulate potential damage it

play16:27

was estimated that there may be

play16:28

localized heat damage but they could not

play16:31

definitively say structural damage would

play16:33

occur more batters are monitored with an

play16:38

exclusion zone while in orbit on

play16:40

slightly two of the mission an

play16:42

additional object appeared in orbit with

play16:44

the orbiter for almost an hour this was

play16:46

detected via the exclusion zone

play16:48

monitoring it was not possible to

play16:50

conclusively determine what it was that

play16:52

the size and shape was consistent with a

play16:54

reinforced carbon-carbon panel fragment

play16:57

it was possible that this was when the

play16:59

damaged tile fell off the orbiter the

play17:02

crew were informed of the debris strike

play17:04

on flight day 8 and they were told it

play17:06

was not a concern and they had nothing

play17:08

to worry about the only reason they were

play17:10

actually informed is because they were

play17:13

about to do media interviews on flight

play17:15

down May 10 and it had become public

play17:17

knowledge throughout the u.s. that there

play17:20

was some concern about a debris strike

play17:22

so they were informed so that they

play17:24

weren't surprised in an interview when

play17:25

they were asked about it

play17:29

foam impacts have been normalized there

play17:31

are maintenance turnaround issue rather

play17:32

than a threat to safety was an

play17:35

identified and acceptable risk not a

play17:37

flight safety issue we can consider that

play17:40

this is actually similar to the Pike

play17:41

River coal mine explosion where

play17:43

excessive methane levels were seen to be

play17:46

a production related issue rather than a

play17:48

safety one high levels had been accepted

play17:56

the Columbia Auditor was unique she was

play17:59

the first orbiter to be launched and she

play18:02

had additional instrumentation to

play18:04

validate performance and design over her

play18:07

life of 28 missions the additional

play18:09

instrumentation began to fail as it was

play18:11

installed for design validation it was

play18:13

not maintained or repaired on failure

play18:16

failed instrumentation meant results

play18:18

could not be relied upon even though the

play18:21

results were logged unexpected results

play18:24

from the sensors in her left wing were

play18:26

assumed to experience though they may

play18:29

have been an indication of the impending

play18:30

breakup it's worth considering how your

play18:34

facilities are instrumented what are

play18:36

your instruments telling you are you

play18:38

measuring the right things what are you

play18:41

doing with the data how are your

play18:43

instruments being maintained is data

play18:47

being ignored because it might be

play18:48

spurious or from instruments that are

play18:50

considered no longer necessary there

play18:58

have been several incidents where

play19:00

evidence of normalization of deviance

play19:02

have contributed to the outcome a

play19:05

selection across different industries

play19:07

have been chosen here the Challenger

play19:10

Space Shuttle in 1986 when the Space

play19:13

Shuttle exploded 73 seconds after launch

play19:15

with the loss of all seven crew the

play19:19

greatly coal mine flood in 1996 when an

play19:21

underground mines flooded when they

play19:23

broke through to some disused and

play19:25

flooded mine tunnels there were four

play19:27

fatalities in 2005 the BP Texas City

play19:32

refinery with the overfilling if the

play19:34

raffinate splitter tower resulting in a

play19:36

loss of containment and subsequent

play19:37

explosion and 15 felonies

play19:41

in Macondo in 2010 with the well blowout

play19:44

resulting in 11 fatalities significant

play19:46

oil filler on the sinking of the reed

play19:48

the Pike River coal mine in 2010 29

play19:53

miners died when they were trapped in

play19:54

the underground mine after a series of

play19:56

explosions due to methane buildup DuPont

play20:00

toxic chemical releases in 2010

play20:02

resulting in one fatality at the Bell

play20:05

West Virginia site and something a

play20:09

little war left field the Costa

play20:11

Concordia in 2012 the grounding and

play20:13

sinking of the passenger ship with the

play20:15

loss of 32 lives let's go into these in

play20:19

a bit more detail to highlight the

play20:20

normalization of deviance that occurred

play20:24

so a little bit more on the Challenger

play20:26

Space Shuttle the o-rings in the socket

play20:30

rock solid rocket boosters were designed

play20:32

to create a pressure seal to contain the

play20:34

solid rocket motors over a series of

play20:36

previous flights it was noted that the

play20:38

o-rings were being eroded during the

play20:40

launch process this became a known

play20:42

design flaw it was also known that the

play20:45

o-rings performed worse when it became

play20:47

brittle under colder ambient conditions

play20:50

this design flaw became acceptable to

play20:52

NASA as there had been no negative

play20:54

consequences of the known issue at the

play20:57

time of launching challenger the ambient

play21:00

temperature was lower than previous

play21:01

launches the Morton Thiokol engineers

play21:04

who designed the o-rings were concerned

play21:06

that this was outside of their known

play21:08

experience where actually recommended

play21:11

against launch in the predicted weather

play21:13

conditions however the deviance of

play21:16

earrings being eroded had been so

play21:18

normalized in the organization that the

play21:21

decision to launch was made the risk was

play21:23

deemed acceptable because nothing bad

play21:25

had happened to previously the results

play21:27

as we know was the destruction of the

play21:28

orbiter and the loss of the entire crew

play21:31

shortly after launch the greatly mine

play21:39

near Newcastle in New South Wales was

play21:42

located in an area rich with black coal

play21:45

calories had been present in the region

play21:47

since the eighteen hundreds

play21:49

initially the mine it greatly was quite

play21:52

some distance away from old abandoned

play21:53

tunnels which

play21:54

over the years had flooded 1994 the

play21:58

decision was made to expand the greatly

play22:00

mind and drawings of the old tunnels are

play22:02

obtained these were unfortunately

play22:05

incorrect and as a result the abandoned

play22:07

tunnels were 100 meters closer than

play22:09

thought in the weeks leading up to the

play22:13

incident warning signs began to appear

play22:15

that the miners were getting closer to

play22:17

the abandoned tunnels

play22:18

however these warnings were ultimately

play22:20

dismissed the district was typically a

play22:24

wet one

play22:25

however Gretna 9 was always considered

play22:27

to be a drier mine in fact it did not

play22:30

have pumps installed when the miners

play22:33

started to report seepage and

play22:34

accumulation of water it should have

play22:36

been a warning that they may have been

play22:38

getting closer to flooded tunnel forced

play22:41

over the two weeks leading up to the

play22:43

flood there were reports of nuisance

play22:45

water in one report the question was

play22:48

actually asked were not close to the old

play22:50

mine are we the increased presence of

play22:54

water was normalized as the coal seam

play22:56

just giving out a considerable amount of

play22:58

water the presence of water in this

play23:01

increasing quantity was deviant but was

play23:03

normalized as nothing to be concerned

play23:05

about BP Texas City refinery the AH

play23:12

summarization unit was being restarted

play23:15

after a shutdown the procedure required

play23:18

pumping of raffinate through the

play23:20

splitter tower however it was common

play23:22

practice to deviate from the procedure

play23:23

and block flow out of the tower this was

play23:26

done to avoid losing liquid level in the

play23:28

tower during startup which may have

play23:30

damaged equipped equipment the previous

play23:33

experience by the operators was that

play23:35

they could get sudden drops from the

play23:36

level in the tower so they adapted the

play23:38

way they started it to compensate

play23:41

compounding this issue was the

play23:43

acceptability to start the tower even

play23:46

though there were reported malfunctions

play23:47

with the level gauges and pressure

play23:49

control valve on the tower another

play23:52

deviation from procedures was the lack

play23:55

of additional staff during startup of

play23:57

the isomerization unit as required by BP

play24:01

safety guidelines

play24:04

the tower overflowed to a blowdown drum

play24:06

rather than to a flair system this was

play24:09

despite numerous recommendations to

play24:11

install the flare system the blowdown

play24:13

zone was a deviation from current

play24:14

accepted engineering design and had

play24:16

resulted in numerous releases to

play24:18

atmosphere of flammable liquids in the

play24:20

past the Deepwater Horizon drill rig had

play24:30

just completed drilling the Macondo well

play24:32

and was preparing to leave the area this

play24:36

process included completing the cement

play24:37

ceiling of the well and removal of heavy

play24:40

drilling mud from the riser provided the

play24:43

cement ceiling was successful removing

play24:45

the mud would not result in any safety

play24:47

issues once the cement ceiling had been

play24:50

completed it was declared a success by

play24:52

the engineers undertaking it this

play24:54

declaration set up the expectation that

play24:57

all subsequent tests which showed had

play24:59

been a success the focus of well

play25:01

integrity tests then shifted to confirm

play25:04

that it was sealed rather than to

play25:05

investigate whether it was sealed yet

play25:08

again a very subtle difference in

play25:09

thought however in this instance the

play25:13

cement ceiling had been unsuccessful and

play25:14

the well was not sealed this highlight

play25:17

of the concept of confirmation bias as

play25:19

well where people have the subconscious

play25:21

preference to look for information that

play25:23

confirms their beliefs rather than

play25:24

refutes them normalization of deviance

play25:28

came into play during the confirmation

play25:30

bias that occurred with the Lovell

play25:32

integrity testing warning signs showing

play25:35

that cement ceiling was unsuccessful

play25:36

were justified away the explanations

play25:39

that did not call into doubt the

play25:41

integrity with the nations that did not

play25:44

call into doubt the integrity of the

play25:45

cement ceiling this can be a challenge

play25:49

in interpreting the warning signs some

play25:51

explanations of them may be benign but

play25:54

if a confirmation bias has already

play25:56

established that there is success the

play25:58

deviation may be normalized

play26:11

the Pike River coal mine was an

play26:14

underground mine and it shipped its

play26:16

first coal in February 2010 so there's a

play26:19

time of the explosion in November 2010

play26:21

it was still a very new mine it did

play26:24

however have some very unusual design

play26:25

features the main ventilation fan was

play26:29

located underground rather than above

play26:30

which is the conventional design this

play26:34

difference contributed to the

play26:36

ventilation system deficiencies which

play26:38

meant it was not able to handle the

play26:39

level of methane being liberated by the

play26:41

mining process employed this was

play26:44

exacerbated by the hydro mining which

play26:47

was liberating higher levels of methane

play26:49

in this particular mine the performance

play26:53

of the ventilation system seen as an

play26:55

Operations issue that impacted

play26:58

production and not safety this was

play27:00

because the accumulation of methane

play27:02

triggered production stoppages because

play27:05

of the focus on production some methane

play27:06

detectives were actually bypassed to

play27:08

prevent these stoppages although the

play27:11

levels of methane were manually recorded

play27:14

on a shift or shift basis but no action

play27:17

was taken when these readings

play27:19

consistently showed excessive levels the

play27:22

deviance of high methane levels was

play27:24

normalized and mining continued it's not

play27:28

known what the ignition source was for

play27:30

the initial explosion and after many

play27:33

years despite the attempts to recover

play27:35

the remains of the miners their bodies

play27:37

remain in the mine the decision to cease

play27:40

attempting to extract them was made in

play27:42

December 2014

play27:48

in 2010 the Daponte

play27:51

Bell West Virginia facilities suffered a

play27:54

series of significant incidents the CSB

play27:58

chose to investigate them over the

play28:01

concern that three very significant

play28:04

incidents could occur over a two day

play28:05

period the first release was of methyl

play28:10

chloride by a ruptured bursting disc

play28:12

this then allow the substance to leak

play28:14

back into the building for five days

play28:16

through a poorly designed vent before it

play28:18

was discovered

play28:19

the bursting disc had sensors connected

play28:22

to it

play28:22

however from experience they were

play28:25

unreliable so the alarms were just

play28:27

assumed to be false or a nuisance prior

play28:30

to this incident though new more

play28:32

reliable sensors had been installed this

play28:35

hadn't been communicated to the

play28:36

operators and they hadn't been trained

play28:38

on the new sensors so the alarms were

play28:40

still assumed to be false the alarms

play28:44

were normalized the second release was

play28:47

of oleum from the sample line through

play28:51

corroded pipe work though they had

play28:54

identified corrosion a year earlier

play28:56

after a different leak and made

play28:58

recommendations for thickness monitoring

play29:00

program it had not been implemented at

play29:03

the time of this incident the third

play29:07

release was when a hose containing

play29:09

phosgene burst spraying an operator

play29:12

phosgene is a highly toxic substance

play29:15

that attacks the mucous membranes of the

play29:17

body and though the worker initially

play29:19

seemed okay he did go to hospital for

play29:21

observation and later died in hospital

play29:24

the phosgene was extracted from a

play29:26

canister into the process via a

play29:28

stainless steel braided teflon lined

play29:31

hose given the permeability of teflon to

play29:34

fourth gene the hoses were to be

play29:36

replaced every thirty days however at

play29:39

the time of the incident they had not

play29:41

been changed for approximately seven

play29:43

months this was because the maintenance

play29:45

system which prompted the change out had

play29:47

been changed and the new system was not

play29:49

sending reminders the normalization of

play29:53

deviance however occurred when earlier

play29:55

that day and now the phosgene hose had

play29:57

failed in service this provided a

play30:00

warning signal to the operators but no

play30:03

checks were done on the other

play30:05

phosgene hoses it was assumed that

play30:08

everything was still okay so there was

play30:11

no checks and no reply estimate other

play30:12

hoses prior to this incident occurring

play30:20

the Costa Concordia cruise ship this

play30:23

ship struck rocks and eventually sank

play30:25

when it sailed at high speed too close

play30:28

to an island in a maneuver called a

play30:30

salute the reason for a salute is

play30:32

usually to give passengers MP I believe

play30:38

we're now back online apologies for that

play30:41

interruption I'm not sure what happened

play30:44

with the audio what I might do is just

play30:55

go back a couple of incidents I'm not

play30:57

sure at which point we actually dropped

play30:59

out I believe it was the DuPont facility

play31:03

so I'm going to go back to the start of

play31:04

the DuPont incident again and my

play31:07

apologies for that technical glitch the

play31:11

CSB chose to investigate the Bell

play31:13

facility I have a concern that three

play31:15

significant incidents could occur over a

play31:17

two day period the first release was of

play31:21

methyl chloride via a ruptured bursting

play31:23

disk this then followed the substance

play31:25

allowed the substance to leak back into

play31:29

the building for approximately five days

play31:30

to a poorly designed vent prior to it

play31:33

being discovered the bursting disc had

play31:36

sensors connected to it whoever it is

play31:38

they were unreliable so alarms were

play31:41

assumed to be false or nuisance prior to

play31:45

the incident though new more reliable

play31:47

sensors had been installed but the

play31:50

alarms were still assumed to be false

play31:52

these alarms were normalized the second

play31:56

release was of oleum from a sample line

play31:58

through through corroded pipe work

play32:02

better had identified the corrosion a

play32:04

year earlier after a different league

play32:06

and made recommendations for thickness

play32:08

monitoring program this had not been

play32:10

implemented at the time the incident

play32:12

occurred the third release was when a

play32:17

hose containing phosgene burst spraying

play32:19

an operator phosgene attacks and mucous

play32:22

membranes for the body and it is a

play32:24

highly toxic substance

play32:25

although the worker initially seemed

play32:28

okay he later died in hospital the

play32:31

she was extracted from a canister into

play32:33

the process via stainless steel braided

play32:35

Teflon lined hoses given the

play32:39

permeability of teflon to phosgene the

play32:42

hoses were to be replaced every 30 days

play32:44

however at the time of the incident they

play32:47

had not been changed for approximately

play32:48

seven months this was because the

play32:51

maintenance system which prompted their

play32:53

change out had been changed and the new

play32:56

system was not providing reminders the

play32:59

normalization of deviance however

play33:01

occurred when earlier that day another

play33:03

phosgene hose failed in service this

play33:06

warning sign did not trigger checking

play33:08

and replacing of the other hoses onto

play33:15

the Costa Concordia the Costa Concordia

play33:19

cruise ship struck rocks and eventually

play33:21

sank when it failed at high speed to

play33:23

close to an island in a maneuver called

play33:25

a salute the reason for their salute is

play33:29

usually to thrill passengers and people

play33:30

on shore and how close the ship is

play33:34

according to the prosecution of the

play33:37

captain of the Costa Concordia over the

play33:39

previous few months in Italy there does

play33:42

appear to have been a history of Costas

play33:44

ship performing salutes

play33:46

over many many years this deviant

play33:50

activity may have been normalized in the

play33:52

company culture the captain was charged

play33:56

with a range of offences including

play33:58

manslaughter and deserting his post

play33:59

after he left the ship while the

play34:01

evacuation was still underway in

play34:04

February 2012 he was found guilty and

play34:06

sentenced to 16 years however in Italy

play34:10

the verdict is not considered final

play34:11

until after all his appeals are over

play34:13

these appeals are still ongoing

play34:21

measuring safety performance and success

play34:24

by recording the number of incidents

play34:26

that occur can embed normalization of

play34:29

deviance logically the absence of one

play34:33

thing is not proof of the presence of

play34:35

another a lack of incidence is not

play34:37

evidence that the workplace is safe

play34:39

there may be a situation where the lack

play34:41

of reported incidents is evidence of

play34:43

normalization of deviance

play34:45

and nothing has gone wrong yet it does

play34:48

not mean that nothing will go wrong in

play34:49

the future consider how you monitor

play34:52

safety performance in your own

play34:53

organization are you measuring success

play34:56

by the absence of failure or actually by

play34:59

the presence of success this is where

play35:02

the lead metrics are so important we're

play35:07

about to do a poll question now so

play35:09

shortly a window will pop up on your

play35:11

screen and you'll be able to select a

play35:16

response to the question do you have

play35:24

systems in place to identify when

play35:27

deviants may become normalized you'll be

play35:32

able to select yes no or don't know and

play35:36

we cannot tell who is submitted each

play35:37

answer as you answer the poll some

play35:40

questions for you to consider do your

play35:44

engineers make clear requests of what

play35:45

they thereafter

play35:47

how do people making the decisions

play35:50

ensure they understand the consequences

play35:51

of those decisions how a dissenting

play35:55

views handled do you assume previous

play35:59

successes are a justification to keep

play36:00

going or do you prove it a safe is the

play36:05

absence of failure seen as proof of

play36:07

success so it looks like we have a few

play36:13

people still coming in with that poll so

play36:16

give it a couple more seconds

play36:27

okay so let's take a look at these

play36:35

results so we actually seen 25% of you

play36:54

saying that yes you do have systems in

play36:56

place to identify when deviance may have

play37:02

become normalized and seventy-five

play37:03

percent saying no so thank you for that

play37:10

feedback so those of you that answered

play37:14

the 25% that answered that you do have

play37:17

systems in place to identify when

play37:20

deviance has become normalized I've got

play37:23

another question for you then and that

play37:26

is how effective have these systems been

play37:36

so I'll give you a chance to answer

play37:38

those questions again so questions to

play37:44

consider as you answer this time does a

play37:47

system address confirmation bias

play37:49

for example now images of the shuttle

play37:52

were requested because they were

play37:53

convinced they did not need them they

play37:56

looked for data to justify their opinion

play37:58

rather than challenging him this was

play38:01

also seen in Macondo the results of the

play38:03

well integrity testing were

play38:04

misinterpreted in justifying that the

play38:06

cement job was secure because it thought

play38:08

it had to be a good cement job

play38:16

so so far as that Paul comes in we're

play38:20

seeing a lot of people saying that where

play38:25

they did have processes in place they're

play38:28

mostly effective though some don't quite

play38:34

know at this stage so I'll just give

play38:42

this poll another few seconds okay well

play38:51

close that off there so what we're

play38:56

seeing here is that for those of you

play38:58

that said you did have systems in place

play39:00

to identify aliens about 75% of you are

play39:06

saying that you believe those systems

play39:08

are effective at about 25 percent I'm

play39:11

sure so I think that's an interesting

play39:12

picture to see how well we think some of

play39:16

our systems are are working in fact so

play39:21

this now actually concludes the

play39:24

technical aspect of the presentation so

play39:30

I'd like to now move to any questions or

play39:32

comments that you may have so

play39:34

understanding that we did have a period

play39:36

of time there where we lost audio

play39:38

apparently and so I'm just going to go

play39:44

back through a couple of the questions

play39:46

and comments that were put in was there

play39:49

a document documented link between tiles

play39:51

disengaging or falling off and a major

play39:53

accident there was certainly the

play39:56

documented link from the perspective

play39:58

that the Atlantis shuttle had had an ear

play40:02

burn through event and it was purely by

play40:05

chance that the tile that fell off came

play40:07

from a region where the whole of the

play40:10

aircraft was actually much thicker so it

play40:12

suffered significant heat damage but it

play40:14

didn't have a total burn through and

play40:15

loss of structural integrity

play40:34

what those systems are for the 25% that

play40:37

had system so that's actually a really

play40:40

good question for those of you that did

play40:42

have those systems in place now you're

play40:44

able to actually just jot down in that

play40:46

chat box for us exactly what the what

play40:51

sort of systems you're using so that we

play40:53

can try and understand what others are

play40:57

using and share that learning so you

play40:59

know what are your learnings about how

play41:02

to share and guard against normalization

play41:03

of deviance in your organization's and

play41:05

how well is that working for you so do

play41:09

we have any suggestions from people

play41:11

around that sort of information or any

play41:22

other questions at all or comments

play41:39

so what I might do then is move on to

play41:44

talk about some of the upcoming webinars

play41:46

that we have and if you have any

play41:49

questions or comments or suggestions

play41:51

around how the how people's areas work

play41:59

you can then put them through so I've

play42:10

just seen we've had some comments come

play42:12

through and I've just lost them on my

play42:20

screen somehow so I'll get to that's get

play42:26

those back in a second on the 23rd of

play42:29

March this year we have a webinar coming

play42:31

up talking about the BP Texas City

play42:33

refinery that actually marks its 10th

play42:35

anniversary we've been fortunate enough

play42:38

to secure dr. Paul Tebow to discuss that

play42:43

particular incident Paul was actually a

play42:46

member of the Baker panel which was the

play42:48

panel that was developed to review the

play42:54

cultural aspects of the US refineries

play42:57

following that particular incident

play43:03

following that Wilbur have another one

play43:05

in June where we're actually going to be

play43:06

talking about the lead process safety

play43:08

metrics project that we've been working

play43:10

on in the Safety Center and where we've

play43:12

got to and then in November on the

play43:16

anniversary of the Pike River Mine

play43:17

explosion the fifth anniversary we'll

play43:19

have a session talking about that as

play43:21

well in terms of the ideas and comments

play43:27

that people have come through with

play43:28

things such as multi-tiered risk

play43:30

assessments of deviations is one area

play43:33

that a one model that people are using

play43:36

and sign off by competent technical

play43:38

authorities to ensure that they're

play43:41

getting broad input into particular

play43:42

topics

play43:46

and other questions come through would

play43:48

it be correct to say that people may not

play43:50

have been able to construct the Columbia

play43:53

disaster before the incident in any

play43:55

hazard study that's an interesting

play43:58

question and I would perhaps suggest

play44:01

that they would have been able to given

play44:04

the previous history that they had and

play44:06

given certainly Columbia was by no means

play44:08

the first major debris strike that that

play44:12

had and also as I said with the Atlantis

play44:16

shuttle that had launched several years

play44:19

earlier there were certainly great

play44:21

concern at that launch that they could

play44:23

have an issue where they had thermal

play44:26

damage sufficient that that shuttle may

play44:28

not have been able to return and that's

play44:31

certainly very clearly seen by the fact

play44:34

that as soon as they immediately

play44:35

discovered that they had some foam

play44:38

shedding issues that they straightaway

play44:40

had the crew inspect the shuttle which

play44:43

as I mentioned is quite different to the

play44:45

response to Columbia they had got to the

play44:49

point in Columbia where they just

play44:50

believed it was not possible to have the

play44:52

issue as opposed to looking back into

play44:55

their own history and seeing that they

play44:56

had very clear warning signs that had

play44:58

occurred and even the previous launch

play45:01

where a significant chunk was taken out

play45:05

of one over the solid rocket boosters by

play45:08

the debris shower that occurred I'd

play45:11

certainly recommend people read or take

play45:14

a quick look at least through some of

play45:15

the executive summary of the Columbia

play45:17

report it's a very very interesting

play45:19

report and it's not purely technical

play45:22

based on the idea of a flight and how

play45:25

those flight structures work it is

play45:27

really more around the cultural

play45:31

deficiencies that occurred within that

play45:33

organization and how it has subsequently

play45:36

changed it's a very interesting study of

play45:40

a culture where there is no concept of

play45:46

failure occurring and they had that in a

play45:50

series of different different incidents

play45:52

because they they could not conceive

play45:54

failure given some of the six

play45:57

that they had had in the past I'd also

play46:02

recommend if anyone gets the chance to

play46:04

visit a place like Kennedy Space Center

play46:05

it is a very very interesting place to

play46:07

visit to see the development of their

play46:09

engineering over many many years but

play46:11

also there are still elements of that

play46:14

same culture around not being able to

play46:16

conceive that something could go wrong

play46:19

given the history that they had no we

play46:30

don't appear to have any more questions

play46:32

or comments coming through so apologies

play46:40

once again for that loss of audio during

play46:43

the presentation and I hope I managed to

play46:45

go back to the right point so you could

play46:48

hear the rest of it this webinar is

play46:52

being recorded so it will be available

play46:55

for viewing in your organization's after

play46:57

this event and that will be available

play47:00

through the Safety Center website at WWE

play47:05

Safety Center org and in the supporters

play47:08

area on the menu you can click straight

play47:11

through to the webinars and you'll be

play47:12

able to see it there and view it also if

play47:16

you have any future comments around

play47:20

webinars please contact us at Safety

play47:23

Center and IQ me org if you have any

play47:25

ideas of how to improve these obviously

play47:28

with technology this is an important one

play47:31

but also for the benefit or particular

play47:33

topics that you'd like looked at or if

play47:35

you'd like to be added to our e-mail

play47:36

notification list so you get notified

play47:38

directly I just had one last question

play47:41

come through asking what time will the

play47:43

BP Texas City session be off the top of

play47:46

my head from memory at the moment I

play47:48

believe it's about 10:00 a.m. Melbourne

play47:50

time which is 7:00 a.m. earth time and

play47:53

part of that is to be able to match in

play47:57

the time zone so that Paul can join us

play47:59

for that discussion I have

play48:07

just seeing one more question come

play48:10

through sorry that I have missed how

play48:14

does the industry find that balance

play48:15

between rewarding success versus

play48:18

rewarding identification of deficiencies

play48:20

in safety systems and deviation on the

play48:23

basis of design that is a very very good

play48:26

question does anyone have any thoughts

play48:30

that would like to actually send through

play48:31

to to assist with that that question I

play48:35

think it is a very challenging balance

play48:38

to go through and I think it's all part

play48:40

of ensuring that you've established an

play48:43

appropriate culture in an organization

play48:45

to make sure that you do have people

play48:48

accountable for what occurs you do need

play48:51

to reward and celebrate success to a

play48:53

certain degree in my experience but you

play48:57

also need to make sure that there's a

play48:59

real focus on where issues are occurring

play49:04

that we're not hiding them or failing to

play49:08

see them more to the point as we

play49:11

endeavor to improve what's going on does

play49:15

anyone else have any other thoughts

play49:16

about how to balance that rewarding

play49:18

success versus deficiencies another very

play49:24

interesting way I've seen it referred to

play49:26

is a comment around celebrating the red

play49:33

on the scorecard and challenging the

play49:35

green so really sending the message out

play49:38

there that you're interested in

play49:39

understanding and you want to see what

play49:42

the deficiencies are and challenge when

play49:44

no deficiencies are found because no

play49:46

system that a human is involved with is

play49:49

free of deficiencies

play50:01

okay we haven't got any more comments

play50:04

come through at this point in time on

play50:05

questions ruff just another one Hopkins

play50:17

has a good theory reward frontline

play50:19

people for reporting incidents and

play50:20

senior managers for safety outputs EDG

play50:25

incident rates is that from Hopkins new

play50:28

book that's just come out in his

play50:32

discussions around reward systems for

play50:39

bonus structures etc and how they

play50:41

potentially drive unintended behaviors

play50:46

and consequences in an organization okay

play50:51

now I've got that answer through know he

play50:52

believes that was out of the disastrous

play50:53

decisions book which was the Macondo

play50:57

review that Hopkins did thank you for

play51:00

that so there's there is certainly some

play51:03

some interesting areas I think I I have

play51:07

some concerns around the idea of the

play51:11

rewarding of management for the safety

play51:13

outputs being the injury rates because

play51:15

that comes back to that very topic of

play51:17

looking at whether we are measuring the

play51:20

success of something by the absence of

play51:24

something else so the absence of

play51:28

injuries or leaks does not mean that

play51:31

we're not about to have one or that

play51:32

we're not about to see something go

play51:38

wrong quite significantly so I think we

play51:43

need to to be very careful and and start

play51:46

to move away from the idea of rewarding

play51:48

people for lagging indicator results I

play51:53

think we need to be moving far more

play51:55

towards the leading space to ensure that

play51:57

we actually see what's going on at that

play52:01

point

play52:11

okay thank you all very much for your

play52:15

attendance I certainly hope that you

play52:18

fall on this webinar both interesting

play52:20

and thought-provoking just got another

play52:25

comment come through sorry I think

play52:26

you're right in rewarding the red

play52:28

warning signs and completing RCA on the

play52:31

warning signs before things go wrong and

play52:33

I think that's a very very good good

play52:36

comment it's around how do we then

play52:37

strike that balance from the busyness

play52:40

that we all exists in to make sure that

play52:43

we give those areas the appropriate

play52:45

attention and understand that the

play52:48

warning sign has existed and appeared

play52:50

and also that we review it to understand

play52:52

how we can address it because there is

play52:55

definitely a balance that does have to

play52:57

come through around how we can actually

play52:59

manage our day to day business because

play53:04

we all still have jobs to do we all

play53:07

still need to understand these things

play53:08

and work through them so thank you very

play53:10

much for that comment as I mentioned

play53:13

this recording will be on the I kms

play53:15

Safety Center website so I would like to

play53:19

sign off there and thank you all very

play53:21

much for your participation today thank

play53:23

you

Rate This

5.0 / 5 (0 votes)

Etiquetas Relacionadas
Safety CultureDeviance NormalizationCase StudiesRisk ManagementSpace ShuttleColumbia DisasterBP Texas CityPike River MineProcess SafetyWebinar Insights
¿Necesitas un resumen en inglés?