<?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: Overburdened with Andon Calls</title>
	<atom:link href="http://theleanthinker.com/2010/01/20/overburdened-with-andon-calls/feed/" rel="self" type="application/rss+xml" />
	<link>http://theleanthinker.com/2010/01/20/overburdened-with-andon-calls/</link>
	<description>Thoughts and insights from the shop floor.</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:11:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Bryan Zeigler</title>
		<link>http://theleanthinker.com/2010/01/20/overburdened-with-andon-calls/comment-page-1/#comment-34593</link>
		<dc:creator>Bryan Zeigler</dc:creator>
		<pubDate>Sat, 30 Jan 2010 22:30:47 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1082#comment-34593</guid>
		<description>Great insights guys.  Sometimes in striving for perfection I get lost from what is normal for the current state.

Thanks again, Bryan</description>
		<content:encoded><![CDATA[<p>Great insights guys.  Sometimes in striving for perfection I get lost from what is normal for the current state.</p>
<p>Thanks again, Bryan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Hallan</title>
		<link>http://theleanthinker.com/2010/01/20/overburdened-with-andon-calls/comment-page-1/#comment-34582</link>
		<dc:creator>Kris Hallan</dc:creator>
		<pubDate>Fri, 29 Jan 2010 07:44:15 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1082#comment-34582</guid>
		<description>By setting up your rules for andon pulling, you are basically setting up a continuous pareto.  The problem with using a pareto to solve problems is that it is a batch and queue operation.  You have to build up a batch of information before you can start solving the problems.  This means all of the problems are old.  By setting up standard rules for your andon that basically say, &quot;when the problem is this big, do this&quot;, you get to work on the biggest problems.

You CAN respond to every problem without causing muri because you get to define what a problem is.  Even Toyota does not respond to EVERY problem.  They just happen to be responding to problems that seem a lot smaller then the ones that we are resonding to.  My factories andon will go off when someone is 30 minutes behind while Toyota&#039;s will go off when they are 30 seconds behind.  They are not choosing to respond to the problem that made them 3 seconds behind however...

I have found this to be a very effective way of setting inventory levels.  Ask the team that will respond to problems how many andon calls they can physically respond to and solve to root cause in a week.  Then set your abnormal inventory levels to hit that number of times based upon historic fluctuations.  Then keep lowering waters as fluctuation decreases.</description>
		<content:encoded><![CDATA[<p>By setting up your rules for andon pulling, you are basically setting up a continuous pareto.  The problem with using a pareto to solve problems is that it is a batch and queue operation.  You have to build up a batch of information before you can start solving the problems.  This means all of the problems are old.  By setting up standard rules for your andon that basically say, &#8220;when the problem is this big, do this&#8221;, you get to work on the biggest problems.</p>
<p>You CAN respond to every problem without causing muri because you get to define what a problem is.  Even Toyota does not respond to EVERY problem.  They just happen to be responding to problems that seem a lot smaller then the ones that we are resonding to.  My factories andon will go off when someone is 30 minutes behind while Toyota&#8217;s will go off when they are 30 seconds behind.  They are not choosing to respond to the problem that made them 3 seconds behind however&#8230;</p>
<p>I have found this to be a very effective way of setting inventory levels.  Ask the team that will respond to problems how many andon calls they can physically respond to and solve to root cause in a week.  Then set your abnormal inventory levels to hit that number of times based upon historic fluctuations.  Then keep lowering waters as fluctuation decreases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Il meglio della blogosfera lean #22 — Encob Blog</title>
		<link>http://theleanthinker.com/2010/01/20/overburdened-with-andon-calls/comment-page-1/#comment-34564</link>
		<dc:creator>Il meglio della blogosfera lean #22 — Encob Blog</dc:creator>
		<pubDate>Sat, 23 Jan 2010 07:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/?p=1082#comment-34564</guid>
		<description>[...] Overburdened with Andon Calls dal blog The Lean Thinker di Mark Rosenthal: Una bella riflessione su andon, lavoro standard e rispetto delle persone (traduzione automatica) [...]</description>
		<content:encoded><![CDATA[<p>[...] Overburdened with Andon Calls dal blog The Lean Thinker di Mark Rosenthal: Una bella riflessione su andon, lavoro standard e rispetto delle persone (traduzione automatica) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

