<?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: TOC Bottleneck versus Lean Pacemaker – Part 2</title>
	<atom:link href="http://lssacademy.com/2007/04/19/toc-bottleneck-versus-lean-pacemaker_19/feed/" rel="self" type="application/rss+xml" />
	<link>http://lssacademy.com/2007/04/19/toc-bottleneck-versus-lean-pacemaker_19/</link>
	<description>Lean Manufacturing, Six Sigma, Lean Six Sigma, and Kaizen</description>
	<lastBuildDate>Sat, 12 May 2012 15:25:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Ron Pereira</title>
		<link>http://lssacademy.com/2007/04/19/toc-bottleneck-versus-lean-pacemaker_19/comment-page-1/#comment-6394</link>
		<dc:creator>Ron Pereira</dc:creator>
		<pubDate>Wed, 13 Apr 2011 13:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/?p=205#comment-6394</guid>
		<description>Hi Vivek, thanks for the great comment.  

The key, from a lean perspective, is to ensure value flows according to what the customer requests.  So while we are always aware of our &quot;constraints&quot; or any process with cycle time greater than takt time, we will NOT allow it to dictate production.  Instead, we break the bottleneck by removing waste or adding resources if needed so it operates below takt time.  

But, again, a lean pacemaker is not necessarily the bottleneck.... instead it is the process furthest downstream whereby everything flows smoothly.  

So with Goldratt&#039;s famous Herbie analogy... we lean folk agree to take the junk from his backback and such.  But, most likely, this won&#039;t be enough to make his cycle time less than takt time so lean proponents would also help the young lad lose weight  -  no pun intended!</description>
		<content:encoded><![CDATA[<p>Hi Vivek, thanks for the great comment.  </p>
<p>The key, from a lean perspective, is to ensure value flows according to what the customer requests.  So while we are always aware of our &#8220;constraints&#8221; or any process with cycle time greater than takt time, we will NOT allow it to dictate production.  Instead, we break the bottleneck by removing waste or adding resources if needed so it operates below takt time.  </p>
<p>But, again, a lean pacemaker is not necessarily the bottleneck&#8230;. instead it is the process furthest downstream whereby everything flows smoothly.  </p>
<p>So with Goldratt&#8217;s famous Herbie analogy&#8230; we lean folk agree to take the junk from his backback and such.  But, most likely, this won&#8217;t be enough to make his cycle time less than takt time so lean proponents would also help the young lad lose weight  &#8211;  no pun intended!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vivek Chopra</title>
		<link>http://lssacademy.com/2007/04/19/toc-bottleneck-versus-lean-pacemaker_19/comment-page-1/#comment-6393</link>
		<dc:creator>Vivek Chopra</dc:creator>
		<pubDate>Wed, 13 Apr 2011 07:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/?p=205#comment-6393</guid>
		<description>Hi,
&quot;Why would I choose to let an operation with such problems determine the way I flow my entire value stream? &quot;
I agree but disagree :). As you rightly pointed out, TOC also says that the constraint, if it exists within the organization, has to be broken (which will, by the way, expose a different constraint, which again we have to manage...so there is always some constraint). Irrespective of whether we are breaking or not, we are always left with a constraint which limits the through-put of the organization. According to TOC there will be no situation where there will be zero constraint because that would mean that the organization can increase throuput without bounds. 
So we are always left with some constraint whether we like it or not -we can&#039;t really avoid that. We would obviously like to be in a happy position where we can choose our constraint but we may not always have that luxury. One can always choose a pacemaker process as separate from a constraint process and schedule it but one will probably realize over time, that it is still the constraint which is threatening the schedule at the pacemaker and so has to be managed separately.
Vivek</description>
		<content:encoded><![CDATA[<p>Hi,<br />
&#8220;Why would I choose to let an operation with such problems determine the way I flow my entire value stream? &#8221;<br />
I agree but disagree <img src='http://lssacademy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . As you rightly pointed out, TOC also says that the constraint, if it exists within the organization, has to be broken (which will, by the way, expose a different constraint, which again we have to manage&#8230;so there is always some constraint). Irrespective of whether we are breaking or not, we are always left with a constraint which limits the through-put of the organization. According to TOC there will be no situation where there will be zero constraint because that would mean that the organization can increase throuput without bounds.<br />
So we are always left with some constraint whether we like it or not -we can&#8217;t really avoid that. We would obviously like to be in a happy position where we can choose our constraint but we may not always have that luxury. One can always choose a pacemaker process as separate from a constraint process and schedule it but one will probably realize over time, that it is still the constraint which is threatening the schedule at the pacemaker and so has to be managed separately.<br />
Vivek</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Let&#8217;s Create a Future State Value Stream Map! &#124; Lean Six Sigma Academy</title>
		<link>http://lssacademy.com/2007/04/19/toc-bottleneck-versus-lean-pacemaker_19/comment-page-1/#comment-1360</link>
		<dc:creator>Let&#8217;s Create a Future State Value Stream Map! &#124; Lean Six Sigma Academy</dc:creator>
		<pubDate>Wed, 27 Feb 2008 02:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/?p=205#comment-1360</guid>
		<description>[...] process “on an island” the lean approach is to schedule one process. We call this process the pacemaker process since it sets the pace for the entire [...]</description>
		<content:encoded><![CDATA[<p>[...] process “on an island” the lean approach is to schedule one process. We call this process the pacemaker process since it sets the pace for the entire [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

