Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Maintenance Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • RCM Blitz®
      • ReliabilityXperience
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Podcasts
  • Courses
    • Your Courses
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
  • Barringer Process Reliability Introduction Course Landing Page
  • Upcoming Live Events
You are here: Home / Articles / Is All RCA the Same?

by Robert (Bob) J. Latino Leave a Comment

Is All RCA the Same?

Is All RCA the Same?

In order to know if all RCA is the same, we first have to define ‘What is RCA?’ On the surface this seems quite simple, but unfortunately it is quite complex. When I train or present speeches around the world, I often poll my audiences about how they define ‘RCA’. The fact is I will get as many answers, as I have people that I ask. This is unfortunate because there is no universally accepted definition of what ‘RCA’ actually is. Are there definitions out there, absolutely! There are hundreds of them. Various regulatory agencies have their own such definitions, as do corporations and companies. However, when definitions differ between agencies, corporations and industries, it is hard to measure the effectiveness of ‘RCA’ across the board, because everyone considers whatever they are doing, as ‘RCA’.

A few examples of this are when we use RCA as a noun and therefore all different brands and techniques are just adjectives describing the noun. Below we prove this by providing definitions of analytical methodologies that are often grouped into the category of RCA.

I will add another potential form of RCA, used by many in industry, which is ‘trial and error’. I do not list it with the others because I really don’t consider it an analytical process. This approach just supports the paradigm of ‘if it ain’t broke, don’t fix it!’ This is more akin to applying a crisis maintenance strategy, there really is no analytics going on, we just fix things when they break.

Troubleshooting. When something ‘fails’ in our workplaces, do faces come to mind of the people that we immediately turn to, to make everything all right? These are our ‘heroes’ who get us back to normalcy quickly, and they get a fair amount of recognition for doing so. However, these individuals are being provided positive recognition for being great responders. They are rarely doing any analytics to understand root causes, but they are great at implementing temporary solutions. A progressive management team, under these conditions, would be asking, “Why is this guy getting some much practice at responding?” that’s where the meat is. This approach is normally attractive because it is quick, inexpensive and demonstrates immediate action.

Brainstorming. We can all relate to this analytical technique. Something bad happens, we put very smart people in a room who listen to a summary of what we know happened (the bad outcome). Oftentimes this description embeds hearsay as fact, and the group is accepting of this hearsay as they move on to solutions. So many bright people throw out disconnected ideas as to what they think happened, and then they move on to action plans. Usually this approach focuses on speed to demonstrate activity, and as a result is weak on evidence and analysis down to root causes. Chances are this team will be meeting again because the failure will recur. This approach takes a little longer because we are not dealing with an individual, we are dealing with several individuals so this requires more give-and-take in discussions.

Problem Solving. This approach is very common and it essentially is brainstorming plus a structured analytical tool like 5-whys or a fishbone diagram. The ‘tool’ provides a degree of discipline as it has a series of steps and a structure to follow. This is certainly more progressive than troubleshooting and brainstorming. This approach, when applied properly, could be effective. However, in my 30+ years of this business, I find that this approach is not always applied properly. People are usually time constrained to hurry up and therefore the time to collect evidence is expensed. So we run with hearsay and assumption, we treat them as facts, and we develop and implement recommendations accordingly.

Root Cause Analysis. The bedrock of any effective RCA methodology and tool, will be the:

  1. Proper defining of a factual problem statement.
  2. Requirement of collecting hard evidence to back up our hypotheses.
  3. Utilization of a cause-and-effect tool, versus a ‘categorical’ tool. Categorical RCA tools employ the use of broad cause categories (i.e. – Man, Machine, Methodology, Communications, etc.) and they require brainstorming underneath that category for more specifics. Cause-and-effect tools like a Logic Tree require that logic be correlated to each other, while evidence is proving the hypotheses that are true. This essentially is a graphical reconstruction of the failure being analyzed.

 

At a high level, here are a few keys to getting past Shallow Cause Analysis (SCA) to perform a real Root Cause Analysis:

  1. Drilling down past the decision-maker and focusing on flawed management systems that influenced poor decision-making.
  2. Development and implementation of effective corrective actions and the tracking and trending of quantifiable bottom-line metrics, demonstrating improvements on the front lines.  Emphasis on creating an overall, corporate knowledge management system that leverages successful logic and puts it at the fingertips of others that can use it, all around the corporation.

Time pressure has a huge impact on the effectiveness of an RCA. When anyone is time pressured to do anything, they often will take short-cuts. In the RCA world, the short-cuts are likely to take place from the most time-consuming part of an analysis/investigation which is the data collection phase. So when we take short-cuts on gathering our evidence, we increase the risk of recurrence because we are not operating on facts, just hearsay and assumptions. The below illustrates the correlations that time pressure has on analysis effectiveness and accuracy.

The Effects of Time Pressure on RCA Accuracy and Effectiveness

In summary, the faster we do an analysis, the more likely we are to do the same analysis again. This is because we are likely to be weak on evidence and our focus is on solutions and not analysis. On the surface, the advantages of ‘shallow cause analysis’ tools is that they are faster and require less resources to complete the analysis. The disadvantages are that we are likely to repeat the need to do another analysis on the same issue.

When RCA is done properly, it does take more time to conduct an effective analysis. However, we should not have to do it again if we did it right the first time!

Remember, “We NEVER seem to have the time and budget to do things right, but we ALWAYS seem to have the time and budget to do them again!”

Filed Under: Articles, on Maintenance Reliability, The RCA

About Robert (Bob) J. Latino

Robert Latino is currently a Principal at Prelical Solutions, LLC, along with his brother Ken Latino. Bob was a Founder and CEO of Reliability Center, Inc. (RCI), until it was acquired in 2019. RCI is a 50-year-old Reliability Consulting firm specializing in improving Equipment, Process and Human Reliability. Mr. Latino received his Bachelor’s degree in Business Administration and Management from Virginia Commonwealth University. For any questions, please contact Bob at blatino@prelical.com

« Cmk! How could there possibly be another capability index?!
Data, Information, and Wisdom »

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

logo for The RCA article series image of BobArticle by Robert (Bob) J. Latino
Principal at Prelical Solutions, LLC

in the The RCA article series

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Posts

  • Leadership Values in Maintenance and Operations
  • Today’s Gremlin – It’ll never work here
  • How a Mission Statement Drives Behavioral Change in Organizations
  • Gremlins today
  • The Power of Vision in Leadership and Organizational Success

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy