<?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: Batch vs continuous flow processing</title>
	<atom:link href="http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/feed/" rel="self" type="application/rss+xml" />
	<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/</link>
	<description>Share Learn And Grow</description>
	<pubDate>Wed, 20 Aug 2008 21:55:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: I Was Just so Wrong &#124; The Hot Aisle</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-127</link>
		<dc:creator>I Was Just so Wrong &#124; The Hot Aisle</dc:creator>
		<pubDate>Wed, 23 Jul 2008 20:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-127</guid>
		<description>[...] impress me? Both Toyota and the businesses I have been serving for the last decade specialize in Continuous Batch Flow Processing. Toyota make cars in batch, Investment Banks like Lehman Brothers and Deutsche Bank process [...]</description>
		<content:encoded><![CDATA[<p>[...] impress me? Both Toyota and the businesses I have been serving for the last decade specialize in Continuous Batch Flow Processing. Toyota make cars in batch, Investment Banks like Lehman Brothers and Deutsche Bank process [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-77</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Thu, 17 Apr 2008 02:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-77</guid>
		<description>Thank you for the comment Greg and for sharing your experience in this area. Sounds like you have seen this type of thing before.

I will look for you at the next party ;)

All the best - JR</description>
		<content:encoded><![CDATA[<p>Thank you for the comment Greg and for sharing your experience in this area. Sounds like you have seen this type of thing before.</p>
<p>I will look for you at the next party <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>All the best - JR</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Lins</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-76</link>
		<dc:creator>Greg Lins</dc:creator>
		<pubDate>Wed, 16 Apr 2008 22:27:18 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-76</guid>
		<description>Hey JR,

I totally agree with you.  Every time I discuss batch vs. continuous flow at a party (with or without cocktails) it engages the interest, fascination, and admiration of all attending. And it is much better if you can draw it on a napkin.  Sometimes you can even tear up some napkins, label them, and move them around to show the differences.  Awe-inspiring stuff....

Anyway, I'll toss in 2 more cents.  Pretty much every implementation of continuous flow I've been engaged in results in inventory reductions of 50-90%, and floor space reductions of 30-70%.  Defects drop off 90% or more, and labor efficiency increases 20-50%.  

What never ceases to amaze me is why so many businesses continue to manufacture the "old way."  My first work in this area was in the early 80's, and you would think by now every production manager and engineer would understand the concepts.  Go figure. 

Take care,

Greg</description>
		<content:encoded><![CDATA[<p>Hey JR,</p>
<p>I totally agree with you.  Every time I discuss batch vs. continuous flow at a party (with or without cocktails) it engages the interest, fascination, and admiration of all attending. And it is much better if you can draw it on a napkin.  Sometimes you can even tear up some napkins, label them, and move them around to show the differences.  Awe-inspiring stuff&#8230;.</p>
<p>Anyway, I&#8217;ll toss in 2 more cents.  Pretty much every implementation of continuous flow I&#8217;ve been engaged in results in inventory reductions of 50-90%, and floor space reductions of 30-70%.  Defects drop off 90% or more, and labor efficiency increases 20-50%.  </p>
<p>What never ceases to amaze me is why so many businesses continue to manufacture the &#8220;old way.&#8221;  My first work in this area was in the early 80&#8217;s, and you would think by now every production manager and engineer would understand the concepts.  Go figure. </p>
<p>Take care,</p>
<p>Greg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-75</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Wed, 16 Apr 2008 20:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-75</guid>
		<description>Hi Crux,

Yes you are correct. The throughput between the two system will be the same (all things being equal). The example was designed to compare and contrast the two systems as you said.

We can agree to disagree on it being academic ;)</description>
		<content:encoded><![CDATA[<p>Hi Crux,</p>
<p>Yes you are correct. The throughput between the two system will be the same (all things being equal). The example was designed to compare and contrast the two systems as you said.</p>
<p>We can agree to disagree on it being academic <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crux_ from news.ycombinator.com</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-74</link>
		<dc:creator>crux_ from news.ycombinator.com</dc:creator>
		<pubDate>Wed, 16 Apr 2008 19:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-74</guid>
		<description>I think there is a difference in assumptions here that needs to be made explicit: 

Chris mentioned that the "Full teams to work paint and wheels sit idle". But I was assuming a resource (people) that could be moved between processes. Either imagine just one team who can build, put wheels on, and paint; or imagine that the teams "sitting idle" are not invited in that day and thus don't draw down resources.

In either case for a given amount of resources (people), and with the ability to allocate those resources between steps as you see fit, then the throughput will be the same.

The example was designed to demonstrate that the "same" process is done more efficiently. But if you measure efficiency by person-hours, or dollars, in this type of thought experiment, you will find that they are identical. And if you have flexibility in where you put your resources, they are pretty much identical in terms of throughput, too. So touting the difference as one between processes is quite misleading, misleading enough that I would call it wrong.

This is all academic, really. Nobody doing real manufacturing has "batch" and "continuous" bandwagons they cheer for: they use gigantic models, simulated annealing and genetic algorithms, actuarial accounting, economic modeling, and reams and reams of PhD-level research to carefully tweak everything to manage the complex interactions of throughput, risk, and demand.</description>
		<content:encoded><![CDATA[<p>I think there is a difference in assumptions here that needs to be made explicit: </p>
<p>Chris mentioned that the &#8220;Full teams to work paint and wheels sit idle&#8221;. But I was assuming a resource (people) that could be moved between processes. Either imagine just one team who can build, put wheels on, and paint; or imagine that the teams &#8220;sitting idle&#8221; are not invited in that day and thus don&#8217;t draw down resources.</p>
<p>In either case for a given amount of resources (people), and with the ability to allocate those resources between steps as you see fit, then the throughput will be the same.</p>
<p>The example was designed to demonstrate that the &#8220;same&#8221; process is done more efficiently. But if you measure efficiency by person-hours, or dollars, in this type of thought experiment, you will find that they are identical. And if you have flexibility in where you put your resources, they are pretty much identical in terms of throughput, too. So touting the difference as one between processes is quite misleading, misleading enough that I would call it wrong.</p>
<p>This is all academic, really. Nobody doing real manufacturing has &#8220;batch&#8221; and &#8220;continuous&#8221; bandwagons they cheer for: they use gigantic models, simulated annealing and genetic algorithms, actuarial accounting, economic modeling, and reams and reams of PhD-level research to carefully tweak everything to manage the complex interactions of throughput, risk, and demand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-73</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 16 Apr 2008 19:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-73</guid>
		<description>@Crux

He is not wrong. In the example, the full teams to work paint and wheels sit idle until it is there turn to produce.</description>
		<content:encoded><![CDATA[<p>@Crux</p>
<p>He is not wrong. In the example, the full teams to work paint and wheels sit idle until it is there turn to produce.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-72</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Wed, 16 Apr 2008 18:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-72</guid>
		<description>Hi Crux,

That is an astute observation.

In the batch processing example you have a lot of waiting (or waste).
As machines are working, you have idle inventory sitting there, doing nothing. 

As you correctly pointed out, the continuous process doesn't have that idle time. As soon as one product is finished, it is immediate sent to the next stage for processing.

Regarding the other example you describe. It is not a similar comparison. In the example I use above, the assumption I use in both cases is that the machine can only work on one car at a time. Obviously if you bought x3 machine your would triple output.</description>
		<content:encoded><![CDATA[<p>Hi Crux,</p>
<p>That is an astute observation.</p>
<p>In the batch processing example you have a lot of waiting (or waste).<br />
As machines are working, you have idle inventory sitting there, doing nothing. </p>
<p>As you correctly pointed out, the continuous process doesn&#8217;t have that idle time. As soon as one product is finished, it is immediate sent to the next stage for processing.</p>
<p>Regarding the other example you describe. It is not a similar comparison. In the example I use above, the assumption I use in both cases is that the machine can only work on one car at a time. Obviously if you bought x3 machine your would triple output.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crux_ from news.ycombinator.com</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-71</link>
		<dc:creator>crux_ from news.ycombinator.com</dc:creator>
		<pubDate>Wed, 16 Apr 2008 17:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-71</guid>
		<description>This is wrong.

In your batch example, the cars are finished with 30 person-minutes of labor.

In your 'continuous' example... the cars are finished with 30 person-minutes of labor. The only reason that the time is shorter is because you have two more people working!!!

Consider if you had three people working at each step of the batch process: It would only take 3 1/3 minutes to build 10 car bodies; 3 1/3 minutes to put on wheels, and 3 1/3 minutes to paint them. For a grand total of: 10 minutes! Batch processing for the win!</description>
		<content:encoded><![CDATA[<p>This is wrong.</p>
<p>In your batch example, the cars are finished with 30 person-minutes of labor.</p>
<p>In your &#8216;continuous&#8217; example&#8230; the cars are finished with 30 person-minutes of labor. The only reason that the time is shorter is because you have two more people working!!!</p>
<p>Consider if you had three people working at each step of the batch process: It would only take 3 1/3 minutes to build 10 car bodies; 3 1/3 minutes to put on wheels, and 3 1/3 minutes to paint them. For a grand total of: 10 minutes! Batch processing for the win!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-70</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Wed, 16 Apr 2008 16:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-70</guid>
		<description>thanks to  kingkongrevenge for highlighting another advantage of continuous flow:

* is more robust - because continuous flow is so disruptive due to equipment failures, workers are forced to fix root cause problems fast

This is another fascinating aspect of the Toyota Production System (TPS).
I hope to write more about this later.</description>
		<content:encoded><![CDATA[<p>thanks to  kingkongrevenge for highlighting another advantage of continuous flow:</p>
<p>* is more robust - because continuous flow is so disruptive due to equipment failures, workers are forced to fix root cause problems fast</p>
<p>This is another fascinating aspect of the Toyota Production System (TPS).<br />
I hope to write more about this later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://rasmusson.wordpress.com/2008/04/16/batch-vs-continuous-flow-processing/#comment-69</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Wed, 16 Apr 2008 16:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://rasmusson.wordpress.com/?p=56#comment-69</guid>
		<description>Hi biff,

In this context continuous flow refers to the continuous movement of cars from one stage to the next many cross functional teams working together on one car at a time.

One of the many differences between batch processing and continuous flow is the amount of WIP (work in process). Batch process have a lot of WIP. Lean manufacturing tries to minimize WIP.

Cheers</description>
		<content:encoded><![CDATA[<p>Hi biff,</p>
<p>In this context continuous flow refers to the continuous movement of cars from one stage to the next many cross functional teams working together on one car at a time.</p>
<p>One of the many differences between batch processing and continuous flow is the amount of WIP (work in process). Batch process have a lot of WIP. Lean manufacturing tries to minimize WIP.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
