|
 click
on photo to purchase |
Root Cause
Analysis
Improving Performance for Bottom-Line Results
Second Edition
Robert J. Latino and
Kenneth C. Latino |
|
Review (from Preface) |
|
Because technology is outpacing humanity's ability to keep up
with it, we are faced with a growing amount of losses. Whether losses
are measured in terms of units produced, quality of healthcare, customer
satisfaction, etc., the common denominator of why our numbers do not measure
up to expectation is the human being.
As corporations continue to reengineer or downsize to "trim
the fat," they raise the bar on their production expectations. Now we
are faced with a paradox of having fewer people with more tasks to
accomplish. How can this be done? The answer, and what we
believe corporate America is trying to do, is reinvent the way we do work.
Doing things the way we have always done them will no longer obtain the
goal. Therefore, we must think outside the proverbial box and
question, why we do the things we do and the way that we do them.
As complex as it seems in our respective environments, the
answer is quite simple when we look at the big picture. Corporations
set earnings expectations, plants set production goals, or hospitals set
expected profit margins; whatever the case, they all set the bar at a
certain level. once that bar is set, all plans revolve around it.
The dilemma that we all face is where are we now compared to the bar?
The distance between our actual situation and where the corporation would
like us to be is the "Gap." The gap is composed of various undesirable
outcomes, failures, incidents, events, etc. What they all have in
common is that they are siphoning money out of the corporate engine.
These events are costing organizations a fortune, and most organizations do
not even know what or where these events are located. Consider this
thought, "Why does a maintenance budget exist?" It exists to repair
both expected and unexpected events. For example, in a manufacturing
plant when chronic type failures occur on a daily or weekly basis, we tend
to become very good at repairing them. They happen so often that we do
not see them as a failure any more but as part of the job. When this
occurs, it is retired to the pasture of the maintenance budget and accepted
as "a cost of doing business." In essence, we will attain our goals in
spite of these events. This is a costly paradigm that is generally
worth tens of hundreds of millions of dollars in accepted losses.
What if we decided we were not going to accept these small,
chronic issues any more? What if we set out to identify all the events
in the gap? What if we dedicated ourselves to understanding why error
occurs and how to prevent it? What if we were to eliminate chronic
failure from occurring? It is difficult for most to envision because
it seems like it is such a distant goal. Our people have the knowledge
and the power to move our organizations to heights never imaginable, if we
would just believe in them and let them soar. This text in an effort
for both management and analysts to help them fully understand why things do
not always work out as planned and how to use root cause analysis to make
sure they do not happen again.
|
| Table
of Contents |
|
Chapter 1
Introduction to Root Cause Analysis (RCA) |
|
The Buzzword Syndrome |
|
Focusing on What Is Important |
|
Cost versus Value |
|
Compliance Training |
|
Incident Versus Proactive RCA |
|
The PROACT® Method |
|
PReserving Event Data |
|
Ordering the Analysis Team |
|
Analyzing the Data |
|
The Root Causes |
|
Communicating Findings and Recommendations |
|
Tracking for Results |
|
Automating RCA |
|
RCA Knowledge Management |
|
Case Histories |
|
Chapter
2 Creating the Environment for RCA to Succeed: The Reliability
Performance Process (TRPP)© |
|
The Role of Executive Management in RCA |
|
The Role of an RCA Champion |
|
The Role of the RCA Driver |
|
Setting Financial Expectations:
The Reality of the Return |
|
Chapter 3 Failure Classification |
|
Problems versus Opportunities |
|
Sporadic versus Chronic Events |
|
RCA as an Approach |
|
Chapter
4 Failure Modes and Effects Analysis (FMEA): The Modified
Approach |
|
Traditional FMEA |
|
Modified FMEA |
|
Step 1: Perform Preparatory Work |
|
Step 2: Collect the Data |
|
Step 3: Summarize and Encode the
Data |
|
Step 4: Calculate Loss |
|
Step 5: Determine the Significant
Few |
|
Step 6: Validate Results |
|
Step 7: Issue a Report |
|
Chapter
5 Enterprise Reliability Asset Management Systems (ERMS):
Automating the Modified FMEA Process |
|
Establish Key Performance Indicators (KPIs) |
|
Determining Our Event Data Needs |
|
Establish a Workflow to Collect the Data |
|
Employ a Comprehensive Data Collection System |
|
Analyze the Digital Data |
|
Chapter 6 The PROACT®
RCA Method |
|
Preserving Event Data |
|
The Error-Change Phenomenon |
|
The 5-Ps Concept |
|
Parts |
|
Position |
|
People |
|
Paper |
|
Paradigms |
|
Chapter 7 Ordering the Analysis Team |
|
Team Member Roles and Responsibilities |
|
The Principal Analyst (PA) |
|
The Associate Analyst |
|
The Experts |
|
Vendors |
|
Critics |
|
Principal Analyst Characteristics |
|
The Challenges of RCA Facilitation |
|
Bypassing the RCA Discipline and Going
Straight to Conclusion |
|
Floundering of Team Members |
|
Acceptance of Opinions as Facts |
|
Dominating Team Members |
|
Reluctant Team Members |
|
Going Off on Tangents |
|
Arguing among Team Members |
|
Promote Listening Skills |
|
Team Codes of Conduct |
|
Team Charter |
|
Team Critical Success Factors (CSFs) |
|
Team Meeting Schedules |
|
Chapter 8 Analyze the Data: Introducing the
Logic Tree |
|
Logic Tree Architecture |
|
The Event |
|
The Event Mode(s) |
|
The Top Box |
|
The Hypotheses |
|
Verifications of Hypotheses |
|
The Fact Line |
|
Physical Root Causes |
|
Human Root Causes |
|
Latent Root Causes |
|
Building the Logic Tree |
|
Broad and All Inclusiveness |
|
The Error-Change Phenomenon Applied to the Logic Tree |
|
Order |
|
Determinism |
|
Discoverability |
|
An Academic Example |
|
Verification Techniques |
|
Confidence Factors |
|
The Troubleshooting Flow Diagram |
|
The Logic Tree Applied to Criminology |
|
Chapter 9 Communicating Findings and Recommendations |
|
The Recommendation Acceptance Criteria |
|
Developing the Recommendations |
|
Developing the Report |
|
The Final Presentation |
|
Have the Professionally Prepared Reports
Ready and Accessible |
|
Strategize for the Meeting by Knowing Your
Audience |
|
Have an Agenda for the Meeting |
|
Develop a Clear, Concise, Professional
Presentation |
|
Coordinate the Media to Use in the
Presentation |
|
Conduct Dry Runs of the Final Presentation |
|
Quantify Effectiveness of Meeting |
|
Prioritize Recommendations Based on Impact
and Effort |
|
Determine Next Step Strategy |
|
Chapter 10 Tracking for Results |
|
Getting Proactive Work Orders Accomplished in a
Reactive Backlog |
|
Sliding the Proactive Work Scale |
|
Developing Tracking Metrics |
|
Exploiting Success |
|
Creating a Critical Mass |
|
Recognizing the Life Cycle Effects of RCA on the
Organization |
|
Conclusion |
|
Chapter 11 Automating Root Cause Analysis: The
Utilization of PROACT® Version 2.0 |
|
Customizing Proact® for Our Facility |
|
Setting Up a New Analysis |
|
Automating the Preservation of Event Data |
|
Automating the Analysis Team Structure |
|
Automating the Root Cause Analysis -- Logic Tree
Development |
|
Automating RCA Report Writing |
|
Automating Tracking Metrics |
|
Chapter 12 Case Histories |
|
Case History 1: ISPAT Inland, Inc. (East
Chicago, IN) |
|
Undesirable Event |
|
Undesirable Event Summary |
|
Line Item from Modified FMEA |
|
Identified Root Causes |
|
Implemented Corrective Actions |
|
Effect on Bottom Line |
|
RCA Team Acknowledgments |
|
Additional RCA Team Comments |
|
Logic Tree |
|
Case History 2: Eastman Chemical Company
(Kingsport, TN) |
|
Undesirable Event |
|
Undesirable Event Summary |
|
Line Item from FMEA |
|
Identified Root Causes |
|
Implemented Corrective Actions |
|
Effect on Bottom Line |
|
RCA Team Acknowledgements |
|
Logic Tree |
|
Case History 3: LYONDELL-CITGO Refining
(Houston, TX) |
|
Undesirable Event |
|
Undesirable Event Summary |
|
Line Item from Modified FMEA |
|
Identified Root Causes |
|
Implemented Corrective Actions |
|
Effect on Bottom Line |
|
Corrective Action Time Frames |
|
RCA Team Statistics |
|
RCA Team Acknowledgements |
|
Additional Comments |
|
Logic Tree |
|
Case History 4: Eastman Chemical Company (World
Headquarters: Kingsport, TN) |
|
Undesirable Event |
|
Undesirable Event Summary |
|
Line Item from Modified FMEA |
|
Specific RCA Description |
|
Identified Root Causes |
|
Implemented Corrective Actions |
|
Effect on Company Bottom Line |
|
RCA Acknowledgments |
|
Case History 5: Southern Companies Alabama Power
Company (Parrish, AL) |
|
Undesirable Event |
|
Undesirable Event Summary |
|
Line Item from Modified FMEA |
|
Specific RCA Description |
|
Identified Root Causes |
|
Implemented Corrective Actions |
|
Effect on Company Bottom Line |
|
RCA Acknowledgments |
|
Logic Tree |
|
Case History 6: Weyerhaeuser Company (Valliant,
OK) |
|
Undesirable Event |
|
Undesirable Event Summary |
|
Line Item from Modified FMEA |
|
Identified Root Causes |
|
Implemented Corrective Actions |
|
Effect on Bottom Line |
|
RCA Team Acknowledgments |
|
Additional RCA Team Comments |
|
Index |