<?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"
	>
<channel>
	<title>Comments on: The use of equipment checklists - an emotion-packed discussion</title>
	<atom:link href="http://blogs.reliableplant.com/490/equipment-checklists/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.reliableplant.com/490/equipment-checklists/</link>
	<description>Blogs from ReliablePlant.com</description>
	<pubDate>Thu, 18 Mar 2010 01:29:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Carl</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-5379</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Thu, 20 Aug 2009 06:39:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-5379</guid>
		<description>Very interesting discussion here, tackling exactly one of the issues im dealing with right now. Im freshly graduated from university and have taken the role of maintenance engineer in a rapidly growing company. We comlpeted our third factory last year and by the end of the year we should have our 4th up and running. 
I am all for the checklist mentality because even in my little experience (3 years) I have seen several hours wasted a week from incorrect settings, incomplete assemblies etc. However my dilemma is how to implement these checklists and what to do with them. I will have to resort to the more experienced operators to be able to get a complete list for each machine and obviously add my own input with regards to good practice. I've won the management over with this idea just by showing them the figures of down time but now im at the critical stage of kick starting this new procedure. I like the laminated checklist and grease pencil idea, ive used it in other places and it works. However are the operators simply expected to tick off what they have done? Will this then hold them responsible? The feeling I have gotten from the operators is that these checklists will be simply a measure for management to "cover their asses" and be able to pin the blame on the "poor operator" in the event of an oversight.
Another dilemma is whether i should believe the system i develop is good and implement it throughout the facilities or should i test run it on a couple of production lines? Both have their pros and cons...
I'd like to draw on your years of experience to help me out here! We do learn from our mistakes but im a firm believer of learning from others' mistakes too!
Thanks</description>
		<content:encoded><![CDATA[<p>Very interesting discussion here, tackling exactly one of the issues im dealing with right now. Im freshly graduated from university and have taken the role of maintenance engineer in a rapidly growing company. We comlpeted our third factory last year and by the end of the year we should have our 4th up and running.<br />
I am all for the checklist mentality because even in my little experience (3 years) I have seen several hours wasted a week from incorrect settings, incomplete assemblies etc. However my dilemma is how to implement these checklists and what to do with them. I will have to resort to the more experienced operators to be able to get a complete list for each machine and obviously add my own input with regards to good practice. I&#8217;ve won the management over with this idea just by showing them the figures of down time but now im at the critical stage of kick starting this new procedure. I like the laminated checklist and grease pencil idea, ive used it in other places and it works. However are the operators simply expected to tick off what they have done? Will this then hold them responsible? The feeling I have gotten from the operators is that these checklists will be simply a measure for management to &#8220;cover their asses&#8221; and be able to pin the blame on the &#8220;poor operator&#8221; in the event of an oversight.<br />
Another dilemma is whether i should believe the system i develop is good and implement it throughout the facilities or should i test run it on a couple of production lines? Both have their pros and cons&#8230;<br />
I&#8217;d like to draw on your years of experience to help me out here! We do learn from our mistakes but im a firm believer of learning from others&#8217; mistakes too!<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TimT</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-4569</link>
		<dc:creator>TimT</dc:creator>
		<pubDate>Fri, 24 Jul 2009 15:50:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-4569</guid>
		<description>Very good discussion. Coming from a military background working on fighter jet engines, we always used checklist then had a inspector go over our work. I'm trying to push checklist now and it is hard for most because they never had it. Biggest response is "I've been doing this for over 30 years" Managment and Supervisors need not just a buy in, but actually be trained thereselves to understand the importance so that it's not just a "temporary fix" but something that has to stay, has to be continuously monitored and improved, just like reliability and training.(which is another story) I've been doing this kind of work for over 35+ years and it's really sad to see how our "craftmenship" is steadilty declining. So many people just come to work, do their time and go home.(kinda like prisoners) Our craft Pride is dying so it up to people like you to keep these blogs going. Maybe through this we can keep our jobs at home.</description>
		<content:encoded><![CDATA[<p>Very good discussion. Coming from a military background working on fighter jet engines, we always used checklist then had a inspector go over our work. I&#8217;m trying to push checklist now and it is hard for most because they never had it. Biggest response is &#8220;I&#8217;ve been doing this for over 30 years&#8221; Managment and Supervisors need not just a buy in, but actually be trained thereselves to understand the importance so that it&#8217;s not just a &#8220;temporary fix&#8221; but something that has to stay, has to be continuously monitored and improved, just like reliability and training.(which is another story) I&#8217;ve been doing this kind of work for over 35+ years and it&#8217;s really sad to see how our &#8220;craftmenship&#8221; is steadilty declining. So many people just come to work, do their time and go home.(kinda like prisoners) Our craft Pride is dying so it up to people like you to keep these blogs going. Maybe through this we can keep our jobs at home.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dibyendu Mukherjee</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-3404</link>
		<dc:creator>Dibyendu Mukherjee</dc:creator>
		<pubDate>Wed, 03 Jun 2009 15:21:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-3404</guid>
		<description>Most important thing about check list is that it enables condition based maitenance( and avoid time based maitenance), also reduce cost of maitenance. It also enable one to know his/her equipment very well.</description>
		<content:encoded><![CDATA[<p>Most important thing about check list is that it enables condition based maitenance( and avoid time based maitenance), also reduce cost of maitenance. It also enable one to know his/her equipment very well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B D PAWAR</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-3085</link>
		<dc:creator>B D PAWAR</dc:creator>
		<pubDate>Mon, 25 May 2009 08:49:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-3085</guid>
		<description>Error in operation or maint. ultimetly results in to loss or waste. It is necessary to have a system that could result in to min. efforts to get maximum output with maximum accurecy. The "Check List" with practicaly important parameters will result in to good outcomes.
              Most of us fail in preparing correct check list and unable to traind subordinate about importance and use of check list.

Needs to prepare interesting check list which shall be usable to improve reliability of equipment in long run.</description>
		<content:encoded><![CDATA[<p>Error in operation or maint. ultimetly results in to loss or waste. It is necessary to have a system that could result in to min. efforts to get maximum output with maximum accurecy. The &#8220;Check List&#8221; with practicaly important parameters will result in to good outcomes.<br />
              Most of us fail in preparing correct check list and unable to traind subordinate about importance and use of check list.</p>
<p>Needs to prepare interesting check list which shall be usable to improve reliability of equipment in long run.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john crossan</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-1068</link>
		<dc:creator>john crossan</dc:creator>
		<pubDate>Fri, 10 Apr 2009 03:17:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-1068</guid>
		<description>Absolutely. Not an option, and managers and supervisors need to make that clear and actually have to be out there making sure checklists are being used. That's really the only way to do mandatory. It's really just another aspect of safety. But there's always selling. Have to change the attitude that "Real men (and women) don't use checklists".</description>
		<content:encoded><![CDATA[<p>Absolutely. Not an option, and managers and supervisors need to make that clear and actually have to be out there making sure checklists are being used. That&#8217;s really the only way to do mandatory. It&#8217;s really just another aspect of safety. But there&#8217;s always selling. Have to change the attitude that &#8220;Real men (and women) don&#8217;t use checklists&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Buscarello</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-1051</link>
		<dc:creator>Greg Buscarello</dc:creator>
		<pubDate>Thu, 09 Apr 2009 15:58:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-1051</guid>
		<description>I have been teaching alignment (among other subjects) for over 20 years and one of the most important concepts is the pre-alignment checklist.  While every student would agree (at least by the end of the class) that such a procedure is a good idea, the percentage of those who will be using it on a regular basis a year later is very small.  The difference comes from the expectations of management and supervision.  Once they agree that the procedure makes sense and ideally have an input on the details of the list, they need to be told that to skip it is not an option.  The buy in from the mechanic must happen first through training and involvement in the process, but after that a clear message must be given that "we're serious about this!"</description>
		<content:encoded><![CDATA[<p>I have been teaching alignment (among other subjects) for over 20 years and one of the most important concepts is the pre-alignment checklist.  While every student would agree (at least by the end of the class) that such a procedure is a good idea, the percentage of those who will be using it on a regular basis a year later is very small.  The difference comes from the expectations of management and supervision.  Once they agree that the procedure makes sense and ideally have an input on the details of the list, they need to be told that to skip it is not an option.  The buy in from the mechanic must happen first through training and involvement in the process, but after that a clear message must be given that &#8220;we&#8217;re serious about this!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie Price</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-566</link>
		<dc:creator>Bernie Price</dc:creator>
		<pubDate>Thu, 12 Mar 2009 13:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-566</guid>
		<description>I have my clients use hand held data collectors while they are doing field inspections. The DMSI company who makes them, have software which will point to "The Pencil Whippers". It produces reports which condense the results allowing a maintenance or operating manager to see exactly what is happening. The resulting transparancy is the only stick needed.</description>
		<content:encoded><![CDATA[<p>I have my clients use hand held data collectors while they are doing field inspections. The DMSI company who makes them, have software which will point to &#8220;The Pencil Whippers&#8221;. It produces reports which condense the results allowing a maintenance or operating manager to see exactly what is happening. The resulting transparancy is the only stick needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron B</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-565</link>
		<dc:creator>Ron B</dc:creator>
		<pubDate>Thu, 12 Mar 2009 13:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-565</guid>
		<description>The routes should have equipment with "I -Buttons" to verify compliance. 
Data collectors to have ID for route only.
Random checks are essential by team leaders.
Any variance to normal trends must be checked by another.
Publish findings that have "saved" production and cost savings announced.
All w.o. follow up to be published and tracked.</description>
		<content:encoded><![CDATA[<p>The routes should have equipment with &#8220;I -Buttons&#8221; to verify compliance.<br />
Data collectors to have ID for route only.<br />
Random checks are essential by team leaders.<br />
Any variance to normal trends must be checked by another.<br />
Publish findings that have &#8220;saved&#8221; production and cost savings announced.<br />
All w.o. follow up to be published and tracked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john crossan</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-536</link>
		<dc:creator>john crossan</dc:creator>
		<pubDate>Mon, 09 Mar 2009 16:12:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-536</guid>
		<description>Bernie
Thanks for bringing up mistake proofing.  It's a key part of the ongoing continuous improvement of changeovers and startups. Eliminating adjustments, centerlining to identify repeatable settings that are made simply to fixed stop positions. Visual indicators and color coding to easily determine if things are in the right place. People really get into this and own it.

Also just found recently published investigation into the crash of a Marine F18 in San Diego some months back 
http://www.latimes.com/news/local/la-me-miramar-jet-crash4-2009mar04,0,1947853.story
found among other failings (including maintenance) that the pilot and his advisors failed to follow steps in a safety checklist that would have prevented flying a crippled plane over densely populated areas. This has ended the military careers of a number of those responsible and their superiors. (and four people were killed).</description>
		<content:encoded><![CDATA[<p>Bernie<br />
Thanks for bringing up mistake proofing.  It&#8217;s a key part of the ongoing continuous improvement of changeovers and startups. Eliminating adjustments, centerlining to identify repeatable settings that are made simply to fixed stop positions. Visual indicators and color coding to easily determine if things are in the right place. People really get into this and own it.</p>
<p>Also just found recently published investigation into the crash of a Marine F18 in San Diego some months back<br />
<a href="http://www.latimes.com/news/local/la-me-miramar-jet-crash4-2009mar04,0,1947853.story" rel="nofollow">http://www.latimes.com/news/local/la-me-miramar-jet-crash4-2009mar04,0,1947853.story</a><br />
found among other failings (including maintenance) that the pilot and his advisors failed to follow steps in a safety checklist that would have prevented flying a crippled plane over densely populated areas. This has ended the military careers of a number of those responsible and their superiors. (and four people were killed).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie price</title>
		<link>http://blogs.reliableplant.com/490/equipment-checklists/#comment-494</link>
		<dc:creator>Bernie price</dc:creator>
		<pubDate>Fri, 06 Mar 2009 05:13:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.reliableplant.com/?p=490#comment-494</guid>
		<description>John

There is a comprehensive science / methodology called "error proofing" and several companies who are proponents of it.

The current if not accepted GURU is professor James Reason of Manchester university but there are many others in the field. You and I arrived at the same point from similar directions......We know that a lack of "Operational Accuracy" is the main road block to achieving "World Class" performance. It is not all the other maintenance related issues we have worked on for so long.

regards

Bernie Price - Polaris Veritas Inc</description>
		<content:encoded><![CDATA[<p>John</p>
<p>There is a comprehensive science / methodology called &#8220;error proofing&#8221; and several companies who are proponents of it.</p>
<p>The current if not accepted GURU is professor James Reason of Manchester university but there are many others in the field. You and I arrived at the same point from similar directions&#8230;&#8230;We know that a lack of &#8220;Operational Accuracy&#8221; is the main road block to achieving &#8220;World Class&#8221; performance. It is not all the other maintenance related issues we have worked on for so long.</p>
<p>regards</p>
<p>Bernie Price - Polaris Veritas Inc</p>
]]></content:encoded>
	</item>
</channel>
</rss>
