<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Conveyors and Accumulation Tables &#187; throughput</title>
	<atom:link href="http://www.garvey.com/tag/throughput/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.garvey.com</link>
	<description>We Handle It</description>
	<lastBuildDate>Thu, 19 Jan 2012 23:18:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Counterpoint:  Is Slower Really Faster?</title>
		<link>http://www.garvey.com/2011/10/counterpoint-is-slower-really-faster/</link>
		<comments>http://www.garvey.com/2011/10/counterpoint-is-slower-really-faster/#comments</comments>
		<pubDate>Mon, 24 Oct 2011 19:20:00 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[counterpoint]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[packaging digest]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=1275</guid>
		<description><![CDATA[Jack Mans, a 45 year packaging industry veteran and contributor to Packaging Digest, wrote a piece laying out the case for slowing packaging lines down to increase output on a consistent basis. The Faster I Go the Behinder I Get &#8211; back when I was a project engineer at Kraft Foods (as it was known [...]]]></description>
			<content:encoded><![CDATA[<p>Jack Mans, a 45 year packaging industry veteran and contributor to <a href="http://www.packagingdigest.com">Packaging Digest</a>, wrote a piece laying out the case for slowing packaging lines down to increase output on a consistent basis.<br />
<blockquote><a href="http://www.packagingdigest.com/blog/Pack_Rat/41325-The_faster_I_go_the_behinder_I_get.php">The Faster I Go the Behinder I Get</a> &#8211; back when I was a project engineer at Kraft Foods (as it was known then), our objective for every packaging line was to increase output. And the obvious way to do that was to run the line faster. Unfortunately, at some point, as you increase operating speed, production actually decreases, because you lose more product to problems than you gain from the increased speed.</p></blockquote>
<p>I agree that this case exists and when a line performing very poorly, slowing things down to get control of the situation is the first and easiest thing you can do.  There is, however, a reason management wants to increase production:  It&#8217;s incredibly profitable to do so and worth the time (and money) to figure out how.  Slowing down is not the only way to increase throughput on a consistent basis.  </p>
<blockquote><p> if the new filler you bought can run 300 bottles/min, but the labeler can only consistently run 280, you will encounter problems.</p></blockquote>
<p>Jack&#8217;s slowdown approach would have us run the filler at a consistent rate of 280/min to match the labeler.  Let&#8217;s assume that &#8220;running consistently&#8221; equates to an efficiency of 98% and this can be achieved at both the filler and the labeler.  At a line speed of 280/min, the overall throughput of our simple line is 0.98 * 0.98 * 280 = 268.9 products per minute (ppm).  </p>
<div id="attachment_1277" class="wp-caption aligncenter" style="width: 439px"><a href="http://www.garvey.com/wp-content/uploads/2011/10/slow-down-or-go-fast.png"><img src="http://www.garvey.com/wp-content/uploads/2011/10/slow-down-or-go-fast.png" alt="Higher efficiency doesn&#039;t always mean more throughput" title="slow-down-or-go-fast" width="429" height="308" class="size-full wp-image-1277" /></a><p class="wp-caption-text">Higher efficiency doesn't always mean more throughput</p></div>
<p>If you raise the line to the rated filler speed (300/min) and raise the labeler to 320/min, you&#8217;re going to take a hit in efficiency on the labeler, right?  If we add a buffer with a capacity of 900 products between the filler and labeler, we can withstand efficiencies on the labeler as low as 84% before dropping the line speed below 268.9ppm.  For reference ow how bad 84% is, that is equal to one hour, sixteen minutes, and forty-eight seconds of downtime in an eight hour shift.  If we can consistently hold an efficiency of 92% (38 minutes of downtime per shift) at the higher speed, our line will run at 294ppm.  This is a 9.3% increase over slowing the line down.</p>
<p>Slow Down:<br />
0.98 * 0.98 * 280 = 268.9ppm</p>
<p>Buffered:<br />
0.98 * 300 = 294ppm<br />
0.92 * 320 = 294.4ppm</p>
<p>294 &#8211; 268.9 = 25.1<br />
25.1/268.9 = 0.093 = 9.3%</p>
<p>Jack ends with three steps:</p>
<blockquote><p>•    Slow the line incrementally until your long-term (daily? weekly?)  throughput peaks and begins to decrease.<br />
•    Continue to slow the line for a short period to make sure that you have really maximized throughput and that the throughput is stabilized across all shifts.<br />
•    Slowly increase speed until output starts to fall off. Then, go back to the sustainable speed.</p></blockquote>
<p>In many cases this may work to improve results, but it will not maximize throughput or get management off your back.  If the line described above runs two eight hour shifts per day, five days per week, fifty weeks out of the year, and has a profit margin of $0.50 per product, a 9.3% improvement translates to $3,012,000 in yearly positive cash flow.  </p>
<p>To maximize throughput:</p>
<blockquote><p>•    Identify the constraint<br />
•    Protect the constraint from all interruptions<br />
•    Increase the speed of the constraint if possible</p></blockquote>
<p>More examples and formulas:<br />
<a href="http://www.garvey.com/2009/11/packaging-throughput-example/">Packaging Throughput Example</a><br />
<a href="http://www.garvey.com/2009/12/what-size-accumulation-table-do-i-need/">How Big Should my Buffer Be?</a><br />
<A href="http://www.garvey.com/2009/12/non-linear-throughput-analysis-of-a-packaging-line/">Non-linear line analysis</a><br />
<a href="http://www.garvey.com/2010/03/accumulation-tables-in-a-puck-line/">Accumulation in a Puck Line</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2011/10/counterpoint-is-slower-really-faster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Garvey Workshop in Princeton, NJ 5/26</title>
		<link>http://www.garvey.com/2011/05/garvey-workshop-in-princeton-nj-526/</link>
		<comments>http://www.garvey.com/2011/05/garvey-workshop-in-princeton-nj-526/#comments</comments>
		<pubDate>Thu, 19 May 2011 19:08:03 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[packaging]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=1263</guid>
		<description><![CDATA[Mike Earling (VP, Sales ) and I will be presenting a workshop on maximizing throughput at the Healthcare Packaging Conference in Princeton, NJ. We&#8217;ll be talking about how to use the theory of constraints to maximize your packaging line&#8217;s throughput and get the most out of your company&#8217;s investment. It&#8217;s on Thursday, May 26th. Click [...]]]></description>
			<content:encoded><![CDATA[<p>Mike Earling (VP, Sales ) and I will be presenting a workshop on maximizing throughput at the <a href="http://www.healthcarepackaging.com/conference/">Healthcare Packaging Conference</a> in Princeton, NJ.  We&#8217;ll be talking about how to use the theory of constraints to maximize your packaging line&#8217;s throughput and get the most out of your company&#8217;s investment.  It&#8217;s on Thursday, May 26th.  Click <a href="http://www.healthcarepackaging.com/conference/">here</a> for more details.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2011/05/garvey-workshop-in-princeton-nj-526/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can Slowing Down Raise Throughput?</title>
		<link>http://www.garvey.com/2010/08/can-slowing-down-create-higher-efficiency/</link>
		<comments>http://www.garvey.com/2010/08/can-slowing-down-create-higher-efficiency/#comments</comments>
		<pubDate>Wed, 25 Aug 2010 13:42:18 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[bottling]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[math]]></category>
		<category><![CDATA[packaging]]></category>
		<category><![CDATA[slow]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=1166</guid>
		<description><![CDATA[Update: I recently made some changes to this article. Most assumed that I was in favor of always slowing down to increase throughput, but it&#8217;s actually only advisable if you can increase efficiency by a significant amount (10-20%). All the changes are in the last paragraph. Can you increase efficiency and throughput by slowing down? [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update:</strong>  I recently made some changes to this article.  Most assumed that I was in favor of always slowing down to increase throughput, but it&#8217;s actually only advisable if you can increase efficiency by a significant amount (10-20%).  All the changes are in the last paragraph.</p>
<p>Can you increase efficiency and throughput by slowing down?</p>
<p>I recently had a discussion with a customer and an engineering firm about increasing throughput by slowing down the rate of a labeler from 400/minute to 380/minute.  They recorded an improvement in efficiency to justify the change.  I questioned the decision from a thruput standpoint and wanted to come up with a good way to determine if an increase in efficiency actually increased the thruput or not.</p>
<div id="attachment_1176" class="wp-caption aligncenter" style="width: 435px"><a href="http://www.garvey.com/wp-content/uploads/2010/08/slowdown.jpg"><img src="http://www.garvey.com/wp-content/uploads/2010/08/slowdown.jpg" alt="" title="slowdown" width="425" height="282" class="size-full wp-image-1176" /></a><p class="wp-caption-text">Is slower better?</p></div>
<p>Efficiency is calculated using the following formula:</p>
<blockquote><p>MTBF / (MTBF + MTR)</p></blockquote>
<p>MTR = Mean Time to Repair<br />
MTBF = Mean Time Between Failure</p>
<p>A properly buffered line should have capacity to handle the longest MTR on the line.  The difference in maximum rates should be such that the table can go from full to empty in less time than the MTBF.   For example, if you have a line like this:</p>
<table>
<tbody>
<tr>
<th>Name</th>
<th>Max Rate</th>
<th>MTR</th>
<th>MTBF</th>
</tr>
<tr>
<td>Filler</td>
<td>330 bpm</td>
<td>3 min</td>
<td>60 min</td>
</tr>
<tr>
<td>Buffer</td>
<td colspan="3">990 bottle capacity</td>
</tr>
<tr>
<td>Labeler</td>
<td>400 bpm</td>
<td>? min</td>
<td>? min</td>
</tr>
</tbody>
</table>
<p>Your labeler must have a MTR of 3 minutes or less and an MTBF of 9.9 minutes or more, giving us a minimum labeler efficiency of 77%.  So what if I decrease my max rate in an effort to improve efficiency?</p>
<table>
<tbody>
<tr>
<th>Name</th>
<th>Max Rate</th>
<th>MTR</th>
<th>MTBF</th>
</tr>
<tr>
<td>Filler</td>
<td>330 bpm</td>
<td>3 min</td>
<td>60 min</td>
</tr>
<tr>
<td>Buffer</td>
<td colspan="3">990 bottle capacity</td>
</tr>
<tr>
<td>Labeler</td>
<td>380 bpm</td>
<td>? min</td>
<td>? min</td>
</tr>
</tbody>
</table>
<p>My minimum required MTR is the same since I&#8217;m still filling the buffer at 330 bpm, but my minimum required MTBF is now 19.8 minutes.  This gives us a way to measure whether the decrease in rate has affected throughput.  My labeler efficiency must now remain above 87% (19.8 / (3+19.8)) to keep the filler running and maintain throughput.<br />
<div id="attachment_1174" class="wp-caption aligncenter" style="width: 414px"><a href="http://www.garvey.com/wp-content/uploads/2010/08/labeler-mtbf-efficiency.png"><img src="http://www.garvey.com/wp-content/uploads/2010/08/labeler-mtbf-efficiency.png" alt="" title="labeler-mtbf-efficiency" width="404" height="261" class="size-full wp-image-1174" /></a><p class="wp-caption-text">As the labeler slows down, its efficiency must go up to maintain throughput for the packaging line.</p></div></p>
<p>The formula can even more simply be expressed like this:</p>
<blockquote><p> e = (Fr / Lr)</p></blockquote>
<p>Where e = the minimum efficiency needed to maintain throughput<br />
Fr = the max rate of the constraint<br />
Lr = the max rate of the machine in question</p>
<p>If I run the labeler at 400 bpm I need to maintain a labeler efficiency of 77%.  If I run it at 380bpm, I must maintain an efficiency of 87%.  So if slowing the max rate of the labeler resulted in improving the efficiency from under 77% to something over 87%, then yes it will have improved throughput.  If they were already running above 77% prior to the rate change, then throughput will be unchanged.  If efficiency is under 87% after the rate change, then throughput will decrease.  </p>
<p>In practice you have to find the right balance between rate and efficiency.  It may be tremendously more difficult to maintain 87% than 77%, due to inconsistent materials or operator error.  </p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2010/08/can-slowing-down-create-higher-efficiency/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Packaging Throughput Example</title>
		<link>http://www.garvey.com/2009/11/packaging-throughput-example/</link>
		<comments>http://www.garvey.com/2009/11/packaging-throughput-example/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 15:44:03 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[accumulation]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[packaging]]></category>
		<category><![CDATA[production]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=729</guid>
		<description><![CDATA[Getting the best performance out of an automated packaging line is a difficult task. It is made up of a series of independent machines that each perform a different function such as filling, labeling, packing, etc. The machines are linked together by an overall control system that records the states of each machine (ie. waiting, [...]]]></description>
			<content:encoded><![CDATA[<p>Getting the best performance out of an automated packaging line is a difficult task.  It is made up of a series of independent machines that each perform a different function such as filling, labeling, packing, etc.  The machines are linked together by an overall control system that records the states of each machine (ie. waiting, functioning or malfunctioning) and sets their speeds.  Being in series, these machines are vulnerable to the &#8220;weakest link&#8221; phenomenom.  If one goes down, they all go down.</p>
<div id="attachment_730" class="wp-caption aligncenter" style="width: 220px"><img class="size-full wp-image-730" title="weakest_link" src="http://www.garvey.com/wp-content/uploads/2009/11/weakest_link.jpg" alt="Remember that game show the Weakest Link?" width="210" height="210" /><p class="wp-caption-text">Remember that game show the Weakest Link?</p></div>
<p>The first step in maximizing your throughput is identifying your constraint, or bottleneck.  Take the efficiency of each machine and multiply it by its maximum rate.  This will give you the net rate of each machine.  The machine with the lowest net rate is your constraint and your goal should to keep it running as fast and as often as possible.</p>
<p><strong>Example:</strong><br />
A simple packaging line: (ppm = products per minute)</p>
<table border="1" cellspacing="0" cellpadding="5" width="100%">
<tbody>
<tr>
<th>Name</th>
<th>Max Rate</th>
<th>Efficiency</th>
<th>Net Rate</th>
<th>Throughput</th>
</tr>
<tr>
<td>Filler</td>
<td>300 ppm</td>
<td>94%</td>
<td>282 ppm</td>
<td rowspan="3">167.7 ppm</td>
</tr>
<tr>
<td>Labeler</td>
<td>200 ppm</td>
<td>97%</td>
<td>194 ppm</td>
</tr>
<tr>
<td>Casepacker</td>
<td>400 ppm</td>
<td>92%</td>
<td>368 ppm</td>
</tr>
<tr bgcolor="#fa9805">
<td><strong>Total</strong></td>
<td><strong>200 ppm</strong></td>
<td><strong>83.9%</strong></td>
<td colspan="2"><strong>167.7 ppm</strong></td>
</tr>
</tbody>
</table>
<p>Some interesting notes:</p>
<ul>
<li>Each machine runs 92% or higher, but the line net efficiency is only 83.9%.  This is because downtime on just one machine shuts down the whole line (ie. if the Casepacker jams, the Filler and the Labeler also shut down).  The net efficiency of the line is calculated by multiplying the efficiencies of each machine in sequence:<br />
<strong>0.94 * 0.97 * 0.92 = 0.839 = 83.9%</strong></li>
<li>To get the overall line speed, multiply the net efficiency by the max rate of the <em>slowest</em> machine:  0.839 * 200 = 167.7 ppm</li>
<li>The machine with the lowest net rate is the labeler (194 ppm), making it the constraint.  194 ppm is the upper limit of what we can achieve on this line.</li>
</ul>
<p>So how do you achieve the upper limit of 194 products per minute?  By making sure downtime on the Filler and Casepacker don&#8217;t ever cause the Labeler to shut down.  By adding an accumulation table in between the Filler and the Labeler, you are segregating the line into two separate systems.  This breaks the compounding effect of the machine efficiencies.</p>
<table border="1" cellspacing="0" cellpadding="5" width="100%">
<tbody>
<tr>
<th>Name</th>
<th>Max Rate</th>
<th>Efficiency</th>
<th>Net Rate</th>
<th>Throughput</th>
</tr>
<tr>
<td>Filler</td>
<td>300 ppm</td>
<td>94%</td>
<td>282 ppm</td>
<td>282 ppm</td>
</tr>
<tr>
<td colspan="5" bgcolor="#006a41"><span style="color: white;">Accumulation Table</span></td>
</tr>
<tr>
<td>Labeler</td>
<td>200 ppm</td>
<td>97%</td>
<td>194 ppm</td>
<td rowspan="2">178.5 ppm</td>
</tr>
<tr>
<td>Casepacker</td>
<td>400 ppm</td>
<td>92%</td>
<td>368 ppm</td>
</tr>
<tr bgcolor="#fa9805">
<td><strong>Total</strong></td>
<td><strong>200 ppm</strong></td>
<td><strong>89.2%</strong></td>
<td colspan="2"><strong>178.5 ppm</strong></td>
</tr>
</tbody>
</table>
<p>Since the line is now in two sections, we have to calculate their throughput separately.  The throughput of the first section is 282ppm (0.94 * 300 ppm = 282 ppm).  The throughput of the second section is 178.5 ppm (0.97 * 0.92 * 200 ppm = 178.5 ppm).  We are still limited by the bottleneck of the second section, so the throughput of this line is 178.5 ppm, a 6.4% increase over our previous line.</p>
<p>Since we haven&#8217;t reach our upper limit of 194 ppm we should add another buffer between the Labeler and the Casepacker.</p>
<table border="1" cellspacing="0" cellpadding="5" width="100%">
<tbody>
<tr>
<th>Name</th>
<th>Max Rate</th>
<th>Efficiency</th>
<th>Net Rate</th>
<th>Throughput</th>
</tr>
<tr>
<td>Filler</td>
<td>300 ppm</td>
<td>94%</td>
<td>282 ppm</td>
<td>282 ppm</td>
</tr>
<tr>
<td colspan="5" bgcolor="#006a41"><span style="color: white;">Accumulation Table</span></td>
</tr>
<tr>
<td>Labeler</td>
<td>200 ppm</td>
<td>97%</td>
<td>194 ppm</td>
<td>194 ppm</td>
</tr>
<tr>
<td colspan="5" bgcolor="#006a41"><span style="color: white;">Accumulation Table</span></td>
</tr>
<tr>
<td>Casepacker</td>
<td>400 ppm</td>
<td>92%</td>
<td>368 ppm</td>
<td>368 ppm</td>
</tr>
<tr bgcolor="#fa9805">
<td><strong>Total</strong></td>
<td><strong>200 ppm</strong></td>
<td><strong>92%</strong></td>
<td colspan="2"><strong>194 ppm</strong></td>
</tr>
</tbody>
</table>
<p>Now we&#8217;ve broken the line into three sections with each machine running independently.  We have no compounding of efficiencies, so all we have to do is pick the lowest net rate of the machines.  In this case, the Labeler&#8217;s net rate is 194 ppm and this is throughput of the line, a 15.7% increase over our original throughput of 167.7 ppm.</p>
<h2>What does 15.7% mean to a company&#8217;s bottom line?</h2>
<p>If you are having trouble meeting market demand for a product it could be huge.<br />
Let&#8217;s say the line is running:<br />
2, 8 hour shifts per day<br />
7 days a week<br />
Profit is a conservative 50 cents per product</p>
<blockquote><p>2 shifts * 8 hours * 60 minutes / hour * $0.50 cents * 26.3 extra products per minute = <strong>$12,624.00 per day in additional revenue</strong></p></blockquote>
<p><strong>Over six months it generates $2,203,880.00</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2009/11/packaging-throughput-example/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

