<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Troubleshooting:  It does not take an expert to do it correctly</title>
	<atom:link href="http://blog.bulk-online.com/blower-technology/troubleshooting-it-does-not-take-an-expert-to-do-it-correctly.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bulk-online.com/general/troubleshooting-it-does-not-take-an-expert-to-do-it-correctly.html</link>
	<description>A weblog for the worldwide powder and bulk solids handling and processing community.</description>
	<lastBuildDate>Fri, 07 Oct 2011 14:26:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kohout</title>
		<link>http://blog.bulk-online.com/general/troubleshooting-it-does-not-take-an-expert-to-do-it-correctly.html/comment-page-1#comment-33492</link>
		<dc:creator>Kohout</dc:creator>
		<pubDate>Sat, 06 Mar 2010 13:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bulk-online.com/?p=573#comment-33492</guid>
		<description>It could be 
Where?  

Good luck in finding
Vasek</description>
		<content:encoded><![CDATA[<p>It could be<br />
Where?  </p>
<p>Good luck in finding<br />
Vasek</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teus Tuinenburg</title>
		<link>http://blog.bulk-online.com/general/troubleshooting-it-does-not-take-an-expert-to-do-it-correctly.html/comment-page-1#comment-31201</link>
		<dc:creator>Teus Tuinenburg</dc:creator>
		<pubDate>Mon, 19 Oct 2009 15:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bulk-online.com/?p=573#comment-31201</guid>
		<description>Dear Ralf,

Troubleshooting is fun for a real technician but not for a manager.
The naming and blaming starts when after a very short time the cause cannot be found.
Counting to ten helps and after 10, clear and logical thinking is the only way to solve the situation.
The 5 â€œWâ€s, you mention can be a good guideline.
However, I found only 3 â€œWâ€s
What
When
Why

Using the first â€œWâ€
What are the two missing â€œWâ€s?
Who?
?

Have a nice day
Teus</description>
		<content:encoded><![CDATA[<p>Dear Ralf,</p>
<p>Troubleshooting is fun for a real technician but not for a manager.<br />
The naming and blaming starts when after a very short time the cause cannot be found.<br />
Counting to ten helps and after 10, clear and logical thinking is the only way to solve the situation.<br />
The 5 â€œWâ€s, you mention can be a good guideline.<br />
However, I found only 3 â€œWâ€s<br />
What<br />
When<br />
Why</p>
<p>Using the first â€œWâ€<br />
What are the two missing â€œWâ€s?<br />
Who?<br />
?</p>
<p>Have a nice day<br />
Teus</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S.Ganesh</title>
		<link>http://blog.bulk-online.com/general/troubleshooting-it-does-not-take-an-expert-to-do-it-correctly.html/comment-page-1#comment-31192</link>
		<dc:creator>S.Ganesh</dc:creator>
		<pubDate>Mon, 19 Oct 2009 04:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bulk-online.com/?p=573#comment-31192</guid>
		<description>Excellent. I may need to add few words. Trouble free running of an equipment starts at the design stage itself. 
The following are must for trouble free of any equipment.
1. Good Design
2. Good erection &amp; Commissioning
3. Good Operation
4. Good Maintenance.

A good maintenance engineer should have a very basic knowledge about other three fields also, to find out out where the mistake could have happened.

Thanks &amp; regards,</description>
		<content:encoded><![CDATA[<p>Excellent. I may need to add few words. Trouble free running of an equipment starts at the design stage itself.<br />
The following are must for trouble free of any equipment.<br />
1. Good Design<br />
2. Good erection &amp; Commissioning<br />
3. Good Operation<br />
4. Good Maintenance.</p>
<p>A good maintenance engineer should have a very basic knowledge about other three fields also, to find out out where the mistake could have happened.</p>
<p>Thanks &amp; regards,</p>
]]></content:encoded>
	</item>
</channel>
</rss>

