<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" xml:lang="en-us">
    <title type="text">Resources for root cause analysis</title>
    <subtitle type="text">All articles for root cause analysis</subtitle>
    <id>http://reliableplant.com/Meta/Tags/root%20cause%20analysis</id>
    <rights type="text">Copyright 0000-2013 Noria Corporation - All Rights Reserved</rights>
    <updated>2012-06-20T08:33:42-05:00</updated>
    <generator>Noria Core</generator>
    <link rel="alternate" type="text/html" title="Resources for root cause analysis" href="http://reliableplant.com/Meta/Tags/root%20cause%20analysis" />
    
    <link rel="search" type="application/opensearchdescription+xml" title="Content Search" href="http://reliableplant.com/osd.xml" />
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/noria/reliableplant/tags/root_cause_analysis" /><feedburner:info uri="noria/reliableplant/tags/root_cause_analysis" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:4fd58ff1-3040-46e6-b542-a076008d1a0d</id>
        <title type="text">Standard Work Drives Continuous Improvement</title>
        <summary type="html">&lt;p&gt;
	If you were to ask an operator or even some leaders what standard work meant to them, you might get responses such as &amp;ldquo;standard operating procedures,&amp;rdquo; &amp;ldquo;work instructions&amp;rdquo; or &amp;ldquo;check sheets.&amp;rdquo; These are all legitimately correct answers. What you might not get is that standard work is the basis for driving all continuous improvement actions.&lt;/p&gt;
&lt;p&gt;
	&lt;em&gt;&amp;ldquo;Where there is no standard, there can be no kaizen.&amp;rdquo; &lt;/em&gt;&amp;mdash; Taiichi Ohno&lt;/p&gt;
&lt;p&gt;
	This statement is often ignored as companies work to improve their performance. The initial attempt to quickly resolve issues so that the team can see action being taken may result in the essential element of continuous improvement &amp;ndash; root cause analysis&amp;mdash;being overlooked.&lt;/p&gt;
&lt;p&gt;
	An important part of truly understanding the relationship of variables on a process comes from stabilizing the effects of changes made to improve it. Traditionally, one may view the lack of this understanding in Figure</summary>
        <updated>2012-06-20T08:33:42-05:00</updated>
        <author>
            <name>Mark Steward</name>
        </author>
        <link rel="alternate" type="text/html" title="Standard Work Drives Continuous Improvement" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/mmyotgJZJRE/standard-work-improvement" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28949/standard-work-improvement">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/mmyotgJZJRE" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28949/standard-work-improvement</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:7ea427c7-70aa-49fe-acd9-a0620098bcab</id>
        <title type="text">How to Start a Reliability Program</title>
        <summary type="html">&lt;p&gt;
	&lt;img alt="" src="http://media.noria.com/sites/Uploads/2012/5/31/00ddc08f-b76c-4bb7-ae57-61378a417af4_start reliability program-2.jpeg" style="margin: 7px; width: 253px; height: 199px; float: left;" /&gt;Where do I start? I have heard this question many times, and there is no easy answer other than &amp;ldquo;pick a spot.&amp;rdquo; What I mean is that normally when a company decides to start a reliability program, there are a lot of improvements to be made in other areas as well. I have never heard of a facility in which everything is perfect and the only thing they need to do is start a reliability program to become world class.&lt;/p&gt;
&lt;p&gt;
	Reliability is tied to almost every other area in a facility, and so when one area is at a low point, other areas are also suffering. I would call on all of the experienced reliability veterans to offer their suggestions to help those who want to start a reliability program.&lt;/p&gt;
&lt;h2&gt;
	Pick a Spot&lt;/h2&gt;
&lt;p&gt;
	Gather all of your best people, including the top people </summary>
        <updated>2012-05-31T09:16:03-05:00</updated>
        <author>
            <name>Robert Apelgren</name>
        </author>
        <link rel="alternate" type="text/html" title="How to Start a Reliability Program" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/7_GZ81tbmPw/start-reliability-program" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28919/start-reliability-program">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/7_GZ81tbmPw" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28919/start-reliability-program</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:82b1ea17-5443-4d55-930b-a060008feb76</id>
        <title type="text">Reduce Waste to Improve Reliability</title>
        <summary type="html">&lt;p&gt;
	It seems as if new weight-loss programs and products come out every week. One of the latest is a plastic wrap you place around your stomach. If you strap it around your stomach, you will sweat and lose weight. Brilliant! Of course, you&amp;rsquo;ll probably sweat if you wrap anything air-tight around your stomach.&lt;/p&gt;
&lt;p&gt;
	Perhaps the more interesting thought is to wonder why we fall for this stuff over and over when we all know the basic concepts in weight loss, such as:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
		Less energy intake will reduce fat&lt;/li&gt;
	&lt;li&gt;
		More exercise will burn fat&lt;/li&gt;
	&lt;li&gt;
		More muscle mass will increase metabolism&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	If you know and understand these basic principles of weight loss, you can apply them and become very successful in losing weight. You will learn that it takes hard work to improve your metabolism and that it is a long-term lifestyle commitment, not a short-term project. This sounds awfully similar to reliability improvements, doesn&amp;rsquo;t it? Perhaps that</summary>
        <updated>2012-05-29T08:43:57-05:00</updated>
        <author>
            <name>Tor Idhammar</name>
        </author>
        <link rel="alternate" type="text/html" title="Reduce Waste to Improve Reliability" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/1GrkucLhNqU/reduce-waste-reliability" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28915/reduce-waste-reliability">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/1GrkucLhNqU" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28915/reduce-waste-reliability</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:14e01a64-e9bc-4209-a7e1-a0550099ac9c</id>
        <title type="text">Saving Time and Money with Condition Monitoring </title>
        <summary type="html">&lt;p&gt;
	A recent acoustic emission (AE) study identified a potential critical bearing failure that became a planned preventive action for a leading food manufacturer. This also avoided considerable cost and unplanned downtime.&lt;/p&gt;
&lt;p&gt;
	The acoustic emission equipment and the main tool used during the planned inspection routes were manufactured by Holroyd Instruments. This example will show the value of this type of equipment in avoiding a major unplanned event that could have had massive cost consequences for the business. Collateral damage to the associated equipment would have proved very costly, and the lead time to rebuild could have caused extensive downtime that would have meant disgruntled customers not being able to rely on stock availability.&lt;/p&gt;
&lt;p&gt;
	The story began in April 2010 when some initial elevated readings were noted at two node points on a large step-down transfer gearbox that were sampled on a seven-day routine. The distress readings were elevated and triggered the alarm leve</summary>
        <updated>2012-05-18T09:19:28-05:00</updated>
        <author>
            <name>Andy Gailey</name>
        </author>
        <link rel="alternate" type="text/html" title="Saving Time and Money with Condition Monitoring " href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/6wwOpN2qqnY/condition-monitoring-saving" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28900/condition-monitoring-saving">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/6wwOpN2qqnY" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28900/condition-monitoring-saving</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:5e64a223-acbf-4e38-b84d-a00b00ac5940</id>
        <title type="text">People Make the Difference in Maintenance and Reliability Improvement</title>
        <summary type="html">&lt;p&gt;
	Many people may have gravitated to the maintenance and reliability industry because of the desire to work with machinery. I was trained in engineering and understand how machines operate and work. Machines behave in logical ways. They all follow the mechanical and electrical laws of nature. Engineers are immersed in those laws in their years of schooling. People in the maintenance field thrive on knowing that machinery works and behaves in logical ways.&lt;/p&gt;
&lt;p&gt;
	In a previous article for &lt;em&gt;Reliable Plant&lt;/em&gt;, I pointed out the thought similarities between an organization&amp;rsquo;s safety improvement effort and a maintenance and reliability improvement effort. The idea that zero injuries are possible is a key concept for any safety effort to gain momentum, but how does a plant or an organization really improve safety results?&lt;/p&gt;
&lt;p&gt;
	What I have experienced over the past 30 years is a continual and steady safety improvement effort. In the early years, much of the emphasis was on identifi</summary>
        <updated>2012-03-05T10:27:27-06:00</updated>
        <author>
            <name>Tim Goshert</name>
        </author>
        <link rel="alternate" type="text/html" title="People Make the Difference in Maintenance and Reliability Improvement" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/UGYixQBxbT8/people-reliability-improvement" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28787/people-reliability-improvement">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/UGYixQBxbT8" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28787/people-reliability-improvement</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:537600c5-88a5-49f3-be72-9fdc008fff4f</id>
        <title type="text">Know Where You Are Going for Successful Change</title>
        <summary type="html">&lt;p&gt;
	Early in his change-management career, Yogi Berra was advising a professional sports organization in New York on some of the finer points of managing change. At the executive briefing, Berra delivered his change-management theory overview, which he summed up in this single statement: &amp;ldquo;You&amp;#39;ve got to be very careful if you don&amp;#39;t know where you&amp;#39;re going, because you might end up someplace else.&amp;quot;&lt;br /&gt;
	&lt;br /&gt;
	Apparently, the executive board was impressed because they extended his engagement an additional 14 years. Although his actual change consulting career was short lived, Berra did highlight one of the most critical aspects of successful change &amp;ndash; knowing where you&amp;rsquo;re going. In organizational change, where you&amp;rsquo;re going is usually summed up in business terms: lower cost, higher quality, greater customer satisfaction, etc. These objectives, however, are the results of specific, repeated behaviors. How change truly occurs is by getting people in the org</summary>
        <updated>2012-01-18T08:44:14-06:00</updated>
        <author>
            <name>Scott Franklin</name>
        </author>
        <link rel="alternate" type="text/html" title="Know Where You Are Going for Successful Change" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/ICY4T8JxUnc/going-where-for-successful-change" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28710/going-where-for-successful-change">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/ICY4T8JxUnc" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28710/going-where-for-successful-change</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:0cd6fe94-e75e-4ebe-9c21-9fcf0089278c</id>
        <title type="text">5 Time Wasters for Reliability Engineers to Avoid</title>
        <summary type="html">&lt;p&gt;
	You&amp;rsquo;ve heard the catch phrases. You&amp;rsquo;ve read the success stories. You&amp;rsquo;ve seen the return on investment (ROI) calculations and the positive trending that reliability engineers bring. You&amp;rsquo;ve even lobbied upper management. Your argument has been so convincing that you&amp;rsquo;ve secured approval in this year&amp;rsquo;s budget to hire a reliability engineer. The hiring process has begun, and you can&amp;rsquo;t wait for the results: more reliable equipment, fewer failures and increased availability and production.&lt;br /&gt;
	&lt;br /&gt;
	If only it were that easy. Building a reliability program led by competent professionals takes work. It requires setting expectations properly. Most of all, it requires time. How do you accelerate the process to ensure the maximum benefit in the shortest time? Avoiding these top five time wasters could help.&lt;/p&gt;
&lt;h2&gt;
	Lack of Vision&lt;/h2&gt;
&lt;p&gt;
	No, we aren&amp;rsquo;t talking about whether your reliability engineer could have been a fighter pilot or whether </summary>
        <updated>2012-01-05T08:19:19-06:00</updated>
        <author>
            <name>Josh Rothenberg</name>
        </author>
        <link rel="alternate" type="text/html" title="5 Time Wasters for Reliability Engineers to Avoid" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/9YRWVNf_B68/5-time-wasters" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28692/5-time-wasters">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/9YRWVNf_B68" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28692/5-time-wasters</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:d1628e32-79d2-49d4-859c-9fb7009d0993</id>
        <title type="text">Discipline and Diligence Are Key for Root Cause Analysis</title>
        <summary type="html">&lt;p&gt;
	OK, so now you have put up these fancy (or so you think fancy) check sheets and charts for standard work, expecting the improvements to happen. Things go well for the first couple of days or weeks &amp;ndash; if you are lucky. Everyone is abuzz with this focus of action, but then it begins to degrade. What is happening?&lt;/p&gt;
&lt;p&gt;
	Diligence and discipline of execution are important underlying details of root cause analysis. The new methods are oftentimes person dependent rather than process dependent. So, we find that the owner maintaining this new system goes on vacation, and the team finds itself quickly back where they started &amp;ndash; frustrated and not knowing where to head next. These new methods fall to the side and are sometimes even removed in shame.&lt;/p&gt;
&lt;p&gt;
	The important aspect of this improvement process is applying consistent performance through discipline. The team members must be able to apply the techniques in order to achieve the performance levels and results expected.&lt;/p&gt;
&lt;p&gt;</summary>
        <updated>2011-12-12T09:31:43-06:00</updated>
        <author>
            <name>Mark Steward</name>
        </author>
        <link rel="alternate" type="text/html" title="Discipline and Diligence Are Key for Root Cause Analysis" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/ILy_PlGJ36A/discipline-diligence-key" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28651/discipline-diligence-key">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/ILy_PlGJ36A" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28651/discipline-diligence-key</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:7314d321-4ae3-4aac-84da-9fb300de2e00</id>
        <title type="text">Corporate Culture Cited as Root Cause of Mine Disaster</title>
        <summary type="html">&lt;p&gt;
	The U.S. Department of Labor&amp;#39;s Mine Safety and Health Administration (MSHA) recently announced that it has imposed a fine of more than $10 million following its investigation into the April 2010 explosion at the Upper Big Branch-South Mine, which was operated by Performance Coal Co., a subsidiary of Massey Energy Co.&lt;/p&gt;
&lt;p&gt;
	The explosion killed 29 miners and injured two, making it the worst U.S. coal mining disaster in 40 years. A report concluded that Massey&amp;#39;s corporate culture was the root cause of the tragedy. MSHA has issued Massey and PCC 369 citations and orders.&lt;/p&gt;
&lt;p&gt;
	&amp;quot;The tragic explosion at Upper Big Branch left dozens of families without husbands, fathers, brothers and sons,&amp;quot; said Secretary of Labor Hilda L. Solis. &amp;quot;I made a pledge to the families of those we lost and the entire mining community to conduct the most complete and thorough investigation possible in order to find the cause of this disaster. The results of the investigation lead to the con</summary>
        <updated>2011-12-08T13:28:53-06:00</updated>
        <author>
            <name>Noria news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Corporate Culture Cited as Root Cause of Mine Disaster" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/sXY697iVzmQ/corporate-culture-cause" />
        <category term="Industry News" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28648/corporate-culture-cause">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/sXY697iVzmQ" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28648/corporate-culture-cause</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:c8d274f9-7da5-4aed-9f06-9fb00093289a</id>
        <title type="text">5 Keys to Maintain Equipment Reliability</title>
        <summary type="html">&lt;p&gt;
	There is so much similarity in all that we do within the maintenance planning and scheduling world that compares to other separate and distinct functions. Let me explain. Borrowing from root cause analysis process methods, I trust you are familiar with Ishikawa diagrams (also called fishbone diagrams or cause-and-effect diagrams). These diagrams are one method that is used for product design, quality defect avoidance or variation, or to identify factors that lead to some event, hence the use in root cause analysis.&lt;/p&gt;
&lt;p&gt;
	The categories typically include:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
		Man (people)&lt;/li&gt;
	&lt;li&gt;
		Methods: How the process is performed and the specific requirements to perform the tasks, including time estimates&lt;/li&gt;
	&lt;li&gt;
		Machines: Any equipment, tools, etc., needed to do the job&lt;/li&gt;
	&lt;li&gt;
		Materials: Consumables, parts required&lt;/li&gt;
	&lt;li&gt;
		Measurements: Data generated from the process&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
	All of these items combine together to create some output or event. In</summary>
        <updated>2011-12-05T08:55:44-06:00</updated>
        <author>
            <name>Jeff Shiver</name>
        </author>
        <link rel="alternate" type="text/html" title="5 Keys to Maintain Equipment Reliability" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/f6HEKIkcHbw/5-keys-reliability" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28641/5-keys-reliability">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/f6HEKIkcHbw" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28641/5-keys-reliability</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:dd8a2d54-03bd-4fe5-b768-9fa900927a61</id>
        <title type="text">Implementing Solutions to Root Causes</title>
        <summary type="html">&lt;p&gt;
	Root cause analysis and root cause failure analysis are commonly used terms, but I have always felt that they are somewhat misguided.&lt;/p&gt;
&lt;p&gt;
	First, there is not really such a thing as a &amp;ldquo;root cause&amp;rdquo; to a problem. If you try to find a definition for &amp;ldquo;root cause,&amp;rdquo; you will discover a mix of homegrown attempts, but all of them are general or unclear in nature. Here is an example: &amp;ldquo;A root cause is an initiating cause of a causal chain which leads to an outcome or effect of interest.&amp;rdquo; Aside from being wrong, it is quite a bunch of incomprehensive verbiage.&lt;/p&gt;
&lt;p&gt;
	The problem with definitions such as these is that in the real world it is never possible to prove a single event that solely initiates a whole chain of other events. That is because there are always other events before the so-called &amp;ldquo;root cause event.&amp;rdquo; This may seem like semantics, but for problem-solvers, it is important to keep in mind that there never is a silver-bullet answer.&lt;/p&gt;</summary>
        <updated>2011-11-28T08:53:16-06:00</updated>
        <author>
            <name>Tor Idhammar</name>
        </author>
        <link rel="alternate" type="text/html" title="Implementing Solutions to Root Causes" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/lsjRTRxsvyg/solutions-root-causes" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28634/solutions-root-causes">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/lsjRTRxsvyg" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28634/solutions-root-causes</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:86ecc44b-c0dd-44f6-9257-9fa200ba4548</id>
        <title type="text">3 Common Excuses for Not Performing Root Cause Analysis</title>
        <summary type="html">&lt;p&gt;
	Most people know what is good for them. We know it is better to eat vegetables than cookies and chips. We know it is healthier to exercise than watch TV. How come the cookies and chips are flying off shelves while the veggies whither? How come the average person spends 20-some hours in front of the TV while we struggle to get one single hour of exercise in a week? The answer is that we don&amp;rsquo;t do what is best for us. We more often do what we feel like and what is easy.&lt;/p&gt;
&lt;p&gt;
	The same logic applies to plants and mills. For example, most everyone agrees that we should fix the root causes of problems rather than the symptoms. However, most of us don&amp;rsquo;t fix the root causes of problems. We keep repairing breakdowns and patching problems with temporary solutions year in and year out. How come? There are a million excuses, but none of those make any sense if we look at what is best for a company over time. Let&amp;rsquo;s look at the most common excuses.&lt;/p&gt;
&lt;h2&gt;
	1. &amp;ldquo;There is no t</summary>
        <updated>2011-11-21T11:18:09-06:00</updated>
        <author>
            <name>Tor Idhammar</name>
        </author>
        <link rel="alternate" type="text/html" title="3 Common Excuses for Not Performing Root Cause Analysis" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/43Hbj_i1p8Y/3-common-excuses" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28627/3-common-excuses">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/43Hbj_i1p8Y" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28627/3-common-excuses</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:cc0d8e20-3d2d-4c76-b7b0-9f9b00b3b5d4</id>
        <title type="text">Why Execution is Key for Business Strategies</title>
        <summary type="html">&lt;p&gt;
	Business strategies developed by companies are often useless. A business strategy is basically a plan for what the company should focus on in the future. It is a promise and guideline to steer a company in the right direction. It&amp;rsquo;s not too different from your personal New Year&amp;rsquo;s resolution.&lt;/p&gt;
&lt;p&gt;
	Most people&amp;rsquo;s New Year&amp;rsquo;s resolutions include things such as losing weight, exercising more, drinking less and improving their marriage in some form. The universal formula for change in any personal-improvement book or business book is to:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;
		Understand what to do&lt;/li&gt;
	&lt;li&gt;
		Understand how to do it&lt;/li&gt;
	&lt;li&gt;
		Execute&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;
	Let us compare a business strategy with our beloved New Year&amp;rsquo;s resolution. We know what the problem is, right? We are fat, unhappy, stressed, whatever. We usually know how to improve (drink less, exercise, spend time with the wife), but we fail to execute.&lt;/p&gt;
&lt;p&gt;
	The hard truth is that we try a little. We s</summary>
        <updated>2011-11-14T10:54:15-06:00</updated>
        <author>
            <name>Tor Idhammar</name>
        </author>
        <link rel="alternate" type="text/html" title="Why Execution is Key for Business Strategies" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/PRRlzYV_0k4/execution-key-strategies" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28619/execution-key-strategies">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/PRRlzYV_0k4" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28619/execution-key-strategies</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:74bc6f0e-7987-445f-ab9f-9f9700941318</id>
        <title type="text">6 Techniques to Error-proof Your Plant</title>
        <summary type="html">&lt;p&gt;
	When faced with the task of improving plant efficiency, the average plant manager breaks the task down by the five or six existing &amp;quot;departmental silos.&amp;quot; Each silo leader subdivides responsibility, repeating the mistake, and passes it on to individuals. As a result, we see young, intelligent engineers overwhelmed by the task handed to them of &amp;quot;get out there and improve maintenance.&amp;quot; The situation is not so bad for the less intelligent or those who have become automatons; they just keep repeating what has gone on forever and collect another paycheck.&lt;br /&gt;
	&amp;nbsp;&lt;br /&gt;
	What the plant manager needs is a better way to visualize his situation, a method that will allow him to develop a new strategy. The following insights are based on work done at MIT and by many other professors in &amp;quot;human error&amp;quot; at international centers of learning. The &amp;quot;Error Pyramid&amp;quot; is unique, but the remaining techniques and technologies have been established for 15 years or more.&lt;br /&gt;</summary>
        <updated>2011-11-10T08:59:05-06:00</updated>
        <author>
            <name>Bernie Price</name>
        </author>
        <link rel="alternate" type="text/html" title="6 Techniques to Error-proof Your Plant" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/OoYrl8ccTiI/error-proof-techniques" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28615/error-proof-techniques">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/OoYrl8ccTiI" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28615/error-proof-techniques</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:cb1a81ab-6704-4ba9-a287-9ebe00f05f0c</id>
        <title type="text">ALS Tribology opens new facility</title>
        <summary type="text">Tribology</summary>
        <updated>2011-04-07T14:35:07-05:00</updated>
        <author>
            <name>Noria Corporation</name>
        </author>
        <link rel="alternate" type="text/html" title="ALS Tribology opens new facility" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/cf9sFNT8c1g/ALS%20Tribology%20opens%20new%20facility" />
        <category term="Industry News" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28418/ALS%20Tribology%20opens%20new%20facility">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/cf9sFNT8c1g" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28418/ALS%20Tribology%20opens%20new%20facility</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:a31168ac-1ad1-4406-a425-9e69008f2d4e</id>
        <title type="text">An introduction to mistake-proofing</title>
        <summary type="html">&lt;p&gt;
	This video clip was taken from a Lean Six Sigma green belt class taught by ProgressivEdge. It opens with a discussion on reactive vs. proactive tools and&amp;nbsp;then describes the&amp;nbsp;three levels of mistake-proofing.&lt;/p&gt;
&lt;br /&gt;






</summary>
        <updated>2011-01-12T08:41:15-06:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="An introduction to mistake-proofing" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/X_og3rZ7Xjo/An-introduction-mistake-proofing" />
        <category term="Videos" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/28234/An-introduction-mistake-proofing">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/X_og3rZ7Xjo" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/28234/An-introduction-mistake-proofing</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:2b631cd5-d409-4513-bd68-9e6700d53eda</id>
        <title type="text">Bearing protection rings help cement plant boost uptime</title>
        <summary type="html">&lt;p&gt;
	It seemed as though nothing could stop the squealing. Not that the Monarch Cement Company&amp;rsquo;s huge ball mill wasn&amp;rsquo;t already loud. Powered by a 5,000-horsepower motor, it pulverizes 100 tons of clinker per hour. But the squealing was not what Randy Riebel wanted to hear. As electrical supervisor at Monarch&amp;rsquo;s plant in Humboldt, Kan., he knew the noise meant the motor&amp;rsquo;s bearings were going &amp;ndash; again. What was the solution? Read this case study to find out.&lt;/p&gt;
</summary>
        <updated>2011-01-10T12:56:21-06:00</updated>
        <author>
            <name>Electro Static Technology</name>
        </author>
        <link rel="alternate" type="text/html" title="Bearing protection rings help cement plant boost uptime" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/PfOnwIbmd1A/Cement-plant-protection-rings" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/28192/Cement-plant-protection-rings">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/PfOnwIbmd1A" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/28192/Cement-plant-protection-rings</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:8364aa19-acdf-412a-9ff3-9e3e0091851a</id>
        <title type="text">3M's successful application of Six Sigma</title>
        <summary type="html">&lt;p&gt;
	This video outlines how 3M has applied the Six Sigma methodology in its business and management processes.&lt;/p&gt;
&lt;br /&gt;






</summary>
        <updated>2010-11-30T08:49:47-06:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="3M's successful application of Six Sigma" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/wTGVyzrc9Ro/3M-application-Six-Sigma" />
        <category term="Videos" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/27631/3M-application-Six-Sigma">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/wTGVyzrc9Ro" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/27631/3M-application-Six-Sigma</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:0e486059-1c4b-4816-99ac-9e2c008f8503</id>
        <title type="text">Using root cause analysis to investigate haul truck incident</title>
        <summary type="html">&lt;p&gt;
	Follow Ron Hughes of Reliability Center Inc. as he examines a haul truck accident and uses PROACT RCA to facilitate this root cause analysis.&lt;/p&gt;
&lt;br /&gt;






</summary>
        <updated>2010-11-12T08:42:30-06:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Using root cause analysis to investigate haul truck incident" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/t1DUAIUL_II/Root-cause-analysis-truck" />
        <category term="Videos" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/27442/Root-cause-analysis-truck">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/t1DUAIUL_II" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/27442/Root-cause-analysis-truck</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:5504d4b2-8df7-4d03-9ef8-9e2800e8a641</id>
        <title type="text">How to trend chronic failures through root cause analysis</title>
        <summary type="html">&lt;p&gt;
	Bob Latino from Reliability Center Inc. provides this video on how to trend chronic failures through root cause analysis. Learn why you should trend chronic failures for the bottom-line results.&lt;/p&gt;
&lt;br /&gt;






</summary>
        <updated>2010-11-08T14:07:01-06:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="How to trend chronic failures through root cause analysis" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/gPcG0dxo3uU/Failures-root-cause-analysis" />
        <category term="Videos" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/27375/Failures-root-cause-analysis">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/gPcG0dxo3uU" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/27375/Failures-root-cause-analysis</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:de701b99-3c79-4fbe-b2a1-9e2800e824ac</id>
        <title type="text">Primer on root cause analysis and cause-and-effect diagrams</title>
        <summary type="html">&lt;p&gt;
	This video provides background on root cause analysis and cause-and-effect diagrams.&lt;/p&gt;
&lt;br /&gt;






</summary>
        <updated>2010-11-08T14:05:10-06:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Primer on root cause analysis and cause-and-effect diagrams" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/cYfIr-QddLs/Primer-root-cause-analysis" />
        <category term="Videos" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/27374/Primer-root-cause-analysis">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/cYfIr-QddLs" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/27374/Primer-root-cause-analysis</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:5fa29571-9826-4ed2-91c1-9e210106a45b</id>
        <title type="text">What root cause analysis tool is best for operators</title>
        <summary type="html">&lt;p id="eow-description"&gt;
	Carl March, reliability subject matter expert with Life Cycle Engineering, presents a novel approach to an age-old root cause analysis tool for operators - &amp;quot;Should-Actual-5 Whys&amp;quot; This installment is a part of a series of informative video lessons called &amp;quot;Reliability Made Simple.&amp;quot;&lt;/p&gt;
&lt;br /&gt;






</summary>
        <updated>2010-11-01T15:56:12-05:00</updated>
        <author>
            <name>Life Cycle Engineering</name>
        </author>
        <link rel="alternate" type="text/html" title="What root cause analysis tool is best for operators" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/lxlX6CXTlPo/Root-cause-analysis-operators" />
        <category term="Videos" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/27256/Root-cause-analysis-operators">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/lxlX6CXTlPo" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/27256/Root-cause-analysis-operators</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:bcbc1019-b214-4889-b7e4-9df70094e2e1</id>
        <title type="text">Wind power company gets to the root of icy issue</title>
        <summary type="html">&lt;p&gt;
	With a steady breeze, a wind turbine &amp;ndash; stretching 262 feet high &amp;ndash; majestically turns its three powerful blades, generating enough clean, renewable electricity to power 750 homes for a 24-hour period. When the breeze turns into a driving wind combined with ice, freezing rain, snow and even freezing fog, the turbine&amp;#39;s anemometer, which measures wind speed and force, can freeze up and result in costly downtime for wind power companies such as Clipper Windpower.&lt;/p&gt;
</summary>
        <updated>2010-09-20T09:02:02-05:00</updated>
        <author>
            <name>Janet Jacobsen</name>
        </author>
        <link rel="alternate" type="text/html" title="Wind power company gets to the root of icy issue" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/bBdjk2BDq0k/wind-power-icy-issue" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/26627/wind-power-icy-issue">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/bBdjk2BDq0k" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/26627/wind-power-icy-issue</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:ab109b33-bedd-4859-8767-9db9008523b7</id>
        <title type="text">Machinists cite China link in Gulf equipment failure</title>
        <summary type="html">&lt;p&gt;
	The International Association of Machinists and Aerospace Workers (IAM) on July 19 faulted British Petroleum (BP) for ordering the use of low-cost repair facilities in China to modify critical safety equipment on the Deepwater Horizon rig in the Gulf of Mexico.&lt;/p&gt;
</summary>
        <updated>2010-07-20T08:04:43-05:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Machinists cite China link in Gulf equipment failure" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/-waNMAsjfnE/Machinists-Gulf-equipment-failure" />
        <category term="Industry News" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/25632/Machinists-Gulf-equipment-failure">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/-waNMAsjfnE" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/25632/Machinists-Gulf-equipment-failure</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:69c07afb-9149-4f7c-9ebd-9d9d00e3470e</id>
        <title type="text">Former Intel engineer shares learnings on root cause analysis</title>
        <summary type="html">&lt;p&gt;
	Menachem Horev&amp;#39;s experience and insights are detailed in a new book, &lt;em&gt;Root Cause Analysis in Process-Based Industries&lt;/em&gt;, published by Trafford Publishing. The book describes how anomalies get introduced into highly controlled and automated process in the first place, then provides methods for moving from an initial symptom to a sharply defined problem with a known cause.&lt;/p&gt;
</summary>
        <updated>2010-06-22T13:47:27-05:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Former Intel engineer shares learnings on root cause analysis" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/wEa5lLtJYSs/Intel-root-cause-analysis" />
        <category term="Industry News" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/25205/Intel-root-cause-analysis">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/wEa5lLtJYSs" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/25205/Intel-root-cause-analysis</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:98fc1df5-adb8-46ae-8641-9d6000b72fe6</id>
        <title type="text">How to improve product quality ... through social networks</title>
        <summary type="html">&lt;p&gt;
	A University of Michigan professor found that a&amp;nbsp;lack of coordination causes defects, but network methods can help predict and prevent them.&lt;/p&gt;
</summary>
        <updated>2010-04-22T11:06:56-05:00</updated>
        <author>
            <name>Terry Kosdrosky</name>
        </author>
        <link rel="alternate" type="text/html" title="How to improve product quality ... through social networks" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/lDCPbyeX2Ls/Product-quality-social-networks" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/24195/Product-quality-social-networks">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/lDCPbyeX2Ls" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/24195/Product-quality-social-networks</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:9d761073-2699-49c9-a844-9d1700947abd</id>
        <title type="text">Survey seeks respondents on how to sustain reliability</title>
        <summary type="html">&lt;p&gt;
	ARC Advisory Group is undertaking a survey to better understand manufacturers&amp;rsquo; approach to reliability for the management of physical assets.&lt;/p&gt;
</summary>
        <updated>2010-02-08T09:00:34-06:00</updated>
        <author>
            <name>ARC Advisory Group</name>
        </author>
        <link rel="alternate" type="text/html" title="Survey seeks respondents on how to sustain reliability" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/uTTId7kiKvU/Survey-respondents-sustain-reliability" />
        <category term="Industry News" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/22721/Survey-respondents-sustain-reliability">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/uTTId7kiKvU" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/22721/Survey-respondents-sustain-reliability</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:a34f2f0c-f4d4-46fb-9ff4-9cf800da2405</id>
        <title type="text">What root cause analysis tool is best for operators?</title>
        <summary type="html">&lt;p&gt;
	Whenever you are asked to specify the best tool for an application, you must first consider a few things before settling on an answer. You have to consider who is going to use it, what this tool would be used for (its application), and what the outcome is intended to accomplish. We know the answer to the first consideration to be operators. With this in mind, let us step through the remaining areas of concern to arrive at an answer.&lt;/p&gt;
&lt;p&gt;
	&lt;strong&gt;&lt;u&gt;1) What will the tool be used for?&lt;/u&gt;&lt;/strong&gt;&lt;br /&gt;
	Operators in the manufacturing and process industry environment play key roles in the overall reliability of equipment. First, they should be the most familiar with how their equipment should function under normal conditions. The difference between what that equipment should be doing and what it actually is able to do at a given moment in time is the definition of a problem.&lt;/p&gt;
&lt;p&gt;
	PROBLEM = SHOULD &amp;ndash; ACTUAL&lt;/p&gt;
&lt;p&gt;
	Early indications of the onset of a problem can frequently b</summary>
        <updated>2009-09-08T00:00:00-05:00</updated>
        <author>
            <name>Carl March</name>
        </author>
        <link rel="alternate" type="text/html" title="What root cause analysis tool is best for operators?" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/uvgpNN7h3Qw/root-cause-analysis" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/19880/root-cause-analysis">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/uvgpNN7h3Qw" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/19880/root-cause-analysis</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:05630356-1f0b-48e7-bae9-9cf800da70bd</id>
        <title type="text">Vodcast: 5 Whys root cause analysis problem-solving tool</title>
        <summary type="html">&lt;IMG src="http://media.noria.com/sites/archive_images/images_spacer.gif" width=1 height=1&gt; 
&lt;P&gt;&lt;SPAN&gt;The 5 Whys is one of the simplest problem-solving tools used in lean manufacturing and lean offices. This presentation shows how to use the 5 Whys and what to watch out for. It was created and presented by Jeff Hajek of Velaction Continuous Improvement.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Access this 5-minute, 51-second vodcast by clicking on the link below.&lt;/SPAN&gt;&lt;/P&gt;

</summary>
        <updated>2009-07-24T00:00:00-05:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Vodcast: 5 Whys root cause analysis problem-solving tool" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/AeGjYGPZYkw/5-whys-root-cause-analysis" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/19011/5-whys-root-cause-analysis">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/AeGjYGPZYkw" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/19011/5-whys-root-cause-analysis</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:edf35059-874a-4777-a881-9cf800da6c33</id>
        <title type="text">Vodcast: Root cause analysis and preventing problems</title>
        <summary type="html">&lt;IMG src="http://media.noria.com/sites/archive_images/images_spacer.gif" width=1 height=1&gt; 
&lt;P&gt;&lt;SPAN&gt;Highly reliable organizations result from highly reliable work processes. Thoroughly dissecting a problem reveals specific solutions to improve work process. The Cause Mapping method of root cause analysis connects problems with work processes to reduce risk and improve organizational reliability. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Access this 7-minute, 49-second video by clicking on the link below.&lt;/SPAN&gt;&lt;/P&gt;

</summary>
        <updated>2009-06-30T00:00:00-05:00</updated>
        <author>
            <name>RP news wires</name>
        </author>
        <link rel="alternate" type="text/html" title="Vodcast: Root cause analysis and preventing problems" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/lwBIfu9erZ4/root-cause-analysis-video" />
        <category term="Media Entries" />
        <content type="html" src="http://reliableplant.com/View/18521/root-cause-analysis-video">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/lwBIfu9erZ4" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/View/18521/root-cause-analysis-video</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:a1186008-b1df-44ac-adb5-9cf800d9fbcf</id>
        <title type="text">Is your RCA effort trigger happy?</title>
        <summary type="html">&lt;P&gt;Most work environments are reactive in nature. There is always more work to be done in a day then there is time to perform work. This is because of unexpected changes in the work environment that cause the workforce to respond immediately and without preparation to return their environment back to the status quo. &lt;/P&gt;
&lt;P&gt;Because of this, some companies have elected to do root cause analysis on these unexpected events. When dealing from a reactive point of view, the management will initiate a trigger that will execute the performance of a root cause analysis based on vibration level, hours of downtime, financial impact, etc. Trigger placement is a GOOD and necessary first step. &lt;/P&gt;
&lt;P&gt;The reason it is a good first step is because the natural progression is to first realize the facility is reactive to an excessive level. This discovery is usually through daily or weekly downtime reporting. Once it is determined there is a problem, measures to control the situation are implemented. Triggers are </summary>
        <updated>2007-05-22T10:03:05-05:00</updated>
        <author>
            <name>Mark A. Latino</name>
        </author>
        <link rel="alternate" type="text/html" title="Is your RCA effort trigger happy?" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/cUWpxDonXVk/rca" />
        <category term="Magazine Articles" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/6407/rca">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/cUWpxDonXVk" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/6407/rca</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:6de48a45-d151-4cfc-a326-9cf800d9fad2</id>
        <title type="text">The perils and pitfalls of RCA</title>
        <summary type="html">&lt;P&gt;My "best practices" column series has discussed aspects of failure prevention (Part 1), life cycle cost and engineering (Part 2), and practical condition monitoring (Part 3). This article will discuss what is traditionally called root cause analysis (RCA) and spell out common pitfalls that I've observed in this area. &lt;/P&gt;
&lt;P&gt;&lt;B&gt;Pointing to the obvious:&lt;/B&gt; Many reactive organizations conclude that RCA is the first agenda item for improving reliability. But after completing a few root cause activities, it's obvious that the results will point to already-known problem areas, such as inferior preventive maintenance (PM) and planning and scheduling. The initial reasoning to start an RCA initiative often follows this train of thought: We have a lot of equipment breakdowns, so . . . step one should be to analyze those breakdowns in order to . . . identify the root cause of the breakdowns in order to . . . eliminate the root causes. &lt;/P&gt;
&lt;P&gt;It sounds logical and reasonable when presented this way, bu</summary>
        <updated>2007-02-12T00:00:00-06:00</updated>
        <author>
            <name>Tor Idhammar</name>
        </author>
        <link rel="alternate" type="text/html" title="The perils and pitfalls of RCA" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/jR9UQ6oTLcw/perils-pitfalls-rca" />
        <category term="Magazine Articles" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/4721/perils-pitfalls-rca">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/jR9UQ6oTLcw" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/4721/perils-pitfalls-rca</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:75bef46d-73d3-4bce-952f-9cf800d9fa58</id>
        <title type="text">Rooting for reliability</title>
        <summary type="html">&lt;p&gt;
	It&amp;#39;s fall. The leaves are or will soon be turning colors and then falling to the ground. Football season is in full swing, and I&amp;#39;m sure you&amp;#39;re rooting on your favorite pro, college and/or high school team to victory. It&amp;#39;s a good time to start thinking about rooting your plant&amp;#39;s reliability on to victory, too - but in this case, I&amp;#39;m not referring to cheering; I&amp;#39;m talking about root cause analysis (RCA).&lt;/p&gt;
&lt;p&gt;
	&lt;i&gt;Reliable Plant&lt;/i&gt; magazine recently conducted an extensive survey about the application of root cause analysis in industrial plants. Some of the results were predictable, but others were very surprising. For example, safety was not identified as the leading motivation to trigger an RCA event. Of almost 600 respondents, we found that 77.5 percent perform some root cause analysis in their organization. Granted, the readers of &lt;i&gt;Reliable Plant&lt;/i&gt; are probably among the upper echelon of reliability practitioners, but the results suggest that this importa</summary>
        <updated>2006-11-02T00:00:00-05:00</updated>
        <author>
            <name>Drew Troyer</name>
        </author>
        <link rel="alternate" type="text/html" title="Rooting for reliability" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/0-S4aEJFdPY/reliability" />
        <category term="Magazine Articles" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/3237/reliability">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/0-S4aEJFdPY" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/3237/reliability</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:8cdebfa0-37d8-46c7-b03f-9cf800da0c24</id>
        <title type="text">A 50/50 approach to finding a root cause</title>
        <summary type="html">&lt;p&gt;
	Recently, I volunteered to go to the gemba as an inspector on the weld assembly line for a metal casket manufacturer. After some training, I was left on my own to inspect the welded casket shell for the rest of the shift. It did not take long to find problems in the process.&lt;/p&gt;
&lt;p&gt;
	One non-conformance that caught my attention was a scratch in the same spot on nearly 50 percent of the metal units. Following the established standard work method, I sanded out the scratch and pushed the unit on to the paint department.&lt;/p&gt;
&lt;p&gt;
	The next day, I met with the regular inspector and shared what I observed. He confirmed that this scratch was a pretty common occurrence. Since it was an easy five-second fix, nobody paid much attention to it. Does this sound familiar?&lt;/p&gt;
&lt;p&gt;
	The elimination of this scratch became my new quality mission. I knew I could locate the root cause because it was consistent and easy to see.&lt;/p&gt;
&lt;p&gt;
	To track down the scratch&amp;#39;s root cause, I decided to use the 50/50</summary>
        <updated>2006-08-08T00:00:00-05:00</updated>
        <author>
            <name>Mike Wroblewski</name>
        </author>
        <link rel="alternate" type="text/html" title="A 50/50 approach to finding a root cause" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/xjFaYFUCZSI/root-cause" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/2249/root-cause">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/xjFaYFUCZSI" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/2249/root-cause</feedburner:origLink></entry>
    <entry>
        <id>tag:noria.com,2010-06-10:publishing:magazines:rp:c1a27bb6-aa3e-44b3-841d-9cf800da097c</id>
        <title type="text">What constitutes world-class maintenance and reliability?</title>
        <summary type="html">
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT class=bodytextspaced&gt;I have 
received many calls asking, "How can you tell if you are a world-class 
maintenance and reliability organization, or not?" &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;o:p&gt;&lt;FONT 
class=bodytextspaced&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT class=bodytextspaced&gt;How 
well the systems and practices discussed in this column are being used indicate 
to me how far a plant has to go to become world class in the areas of 
maintenance and reliability. I would suggest reading this column with a group of 
operations and maintenance employees that includes both management and 
craftspeople. &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;o:p&gt;&lt;FONT 
class=bodytextspaced&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT class=bodytextspaced&gt;On a 
scale of zero to 10, rate your plant's use of the following systems and 
practic</summary>
        <updated>2005-09-02T00:00:00-05:00</updated>
        <author>
            <name>Christer Idhammar</name>
        </author>
        <link rel="alternate" type="text/html" title="What constitutes world-class maintenance and reliability?" href="http://feedproxy.google.com/~r/noria/reliableplant/tags/root_cause_analysis/~3/Qs4ckIlJxU8/world-class-maintenance" />
        <category term="Web Exclusives" />
        <category term="Articles" />
        <content type="html" src="http://reliableplant.com/Read/212/world-class-maintenance">&lt;img src="http://feeds.feedburner.com/~r/noria/reliableplant/tags/root_cause_analysis/~4/Qs4ckIlJxU8" height="1" width="1"/&gt;</content>
    <feedburner:origLink>http://reliableplant.com/Read/212/world-class-maintenance</feedburner:origLink></entry>
</feed>
