<?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; line analysis</title>
	<atom:link href="http://www.garvey.com/tag/line-analysis/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>Accumulation and Traceability of Packaged Goods</title>
		<link>http://www.garvey.com/2010/12/accumulation-and-traceability-of-packaged-goods/</link>
		<comments>http://www.garvey.com/2010/12/accumulation-and-traceability-of-packaged-goods/#comments</comments>
		<pubDate>Tue, 28 Dec 2010 22:19:52 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[accumulation]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[traceability]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=1236</guid>
		<description><![CDATA[I got an email the other day from Suzi Kennefick about accumulation&#8217;s impact on traceability. I&#8217;m a controls systems validation engineer who is doing a part-time degree in mechatronics. My project is on exploring the replacing of the FIRO (First In / Random Out) buffers we have at work on our filling/packaging line (Bottles) for [...]]]></description>
			<content:encoded><![CDATA[<p>I got an email the other day from Suzi Kennefick about accumulation&#8217;s impact on traceability.</p>
<blockquote><p>I&#8217;m a controls systems validation engineer who is doing a part-time degree in<br />
mechatronics. My project is on exploring the replacing of the FIRO (First In  / Random Out) buffers we have at work on our filling/packaging line (Bottles) for FIFO (First In / First Out) buffers and then looking at how that helps us with maintaining traceability etc.</p></blockquote>
<p>This is a fantastic question and one I thought I understood until I started thinking about it.  I also like the term FIRO, which I have to admit I never heard before.  Most accumulation systems I&#8217;ve used are generally either FILO or FIFO with some randomness thrown in.  A few are near perfect FIFO.</p>
<p>The answer to her question starts with a definition of traceability.  Traceability in packaging is the power to locate when a particular product was packaged in order to isolate a problem.  In the event of a recall, packagers want to minimize losses and the more traceability they have the less product gets scrapped and the more confident they are that the public is protected from sickness (or worse).  Raising the precision of your traceability has significant operational and efficiency costs, so companies must select the level that makes sense for them.</p>
<div id="attachment_1239" class="wp-caption aligncenter" style="width: 279px"><a href="http://www.garvey.com/wp-content/uploads/2010/12/photo1.jpg"><img class="size-thumbnail wp-image-1239" title="photo" src="http://www.garvey.com/wp-content/uploads/2010/12/photo1-269x230.jpg" alt="" width="269" height="230" /></a><p class="wp-caption-text">What type of accumulation system you needdepends on the level of traceability you&#39;re looking for.</p></div>
<p>Here are acceptable ways to use accumulation under various levels of traceability:</p>
<p><strong>Traceability by Day</strong><br />
If you need a product to be traceable back to a specific day, then any accumulation style will work (FIFO, FILO, FIRO, etc.).  All you have to do is make sure all buffers, hoppers, and reject collectors  are cleared out between shifts.  Have an inspector walk the line and make sure no product has been taken off the line and set aside during production.  When stacked in pallets, make sure each pallet is wrapped and marked in a way that no products can easily be removed or have their documentation tampered with.  Pallets should be stored so they are not mixed with other days&#8217; pallets.</p>
<p><strong>Traceability by Hour</strong><br />
Keeping track of a specific hour&#8217;s production requires more rigorous procedures.  All buffers should have a maximum dwell time that when added to the total production time, is no more than 30 minutes (ie. 2 buffers with 10 minutes of maximum dwell time, plus 10 minutes of total production time makes the maximum amount of time on the line 30 minutes).  If the OEM cannot provide a maximum dwell time that is low enough to achieve this, then periodically you will have to artificially introduce down time to empty the buffer if it has not emptied on its own before the alloted time.  This has a significant impact on efficiency.</p>
<p><strong>Traceability by Case or Product</strong><br />
The highest level of traceability goes down to an individual product or small group (ie. case).  In this scenario, no product should ever be able to pass each other on the conveyor system or in buffers, which requires tamper proof conveyors with overhead covers.  Constant monitoring is required to make sure no products are removed from the packaging line unless recorded by an automatic rejector.  Rejected products should be dropped into a locked box that can&#8217;t be opened in the packaging area.  At that point all these extra measures begins to make <a href="http://en.wikipedia.org/wiki/Radio-frequency_identification">RFID</a> tracking an economical solution, which would allow you to once again use any accumulation system, even FILO ones.</p>
<p>Check out our selection of <a href="http://www.garvey.com/category/accumulators/">accumulation tables</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2010/12/accumulation-and-traceability-of-packaged-goods/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What does MTR Stand For?</title>
		<link>http://www.garvey.com/2010/09/what-does-mtr-stand-for/</link>
		<comments>http://www.garvey.com/2010/09/what-does-mtr-stand-for/#comments</comments>
		<pubDate>Wed, 08 Sep 2010 14:43:49 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[accumulation table]]></category>
		<category><![CDATA[buffer]]></category>
		<category><![CDATA[conveyor]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[mtr]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=1186</guid>
		<description><![CDATA[MTR stands for Mean Time to Repair. In automated processing and packaging lines, Mean Time to Repair is the average time it takes to repair a machine once it malfunctions. It&#8217;s used to calculate how much buffering is required upstream or downstream. If your line&#8217;s longest MTR is 3 minutes, then you need at 3 [...]]]></description>
			<content:encoded><![CDATA[<p>MTR stands for <strong>Mean Time to Repair</strong>.</p>
<p>In automated processing and packaging lines, Mean Time to Repair is the average time it takes to repair a machine once it malfunctions.  It&#8217;s used to calculate how much buffering is required upstream or downstream.  If your line&#8217;s longest MTR is 3 minutes, then you need at 3 minutes of accumulation.</p>
<p>Wait, but doesn&#8217;t that mean I will only be able to buffer against half the downtimes?  If you have an even distribution of downtime durations, then yes, you&#8217;d only buffer against half the downtimes.  What we see in reality is that most packaging machinery has a high number of very short downtimes (under 3 minutes) and a small number of very long downtimes (10-60 minutes).  Here&#8217;s some representative (but fabricated) sample data to illustrate this point.</p>
<div id="attachment_1187" class="wp-caption aligncenter" style="width: 488px"><a href="http://www.garvey.com/wp-content/uploads/2010/09/downtime-durations.png"><img class="size-full wp-image-1187 " title="downtime-durations" src="http://www.garvey.com/wp-content/uploads/2010/09/downtime-durations.png" alt="downtime-durations" width="478" height="238" /></a><p class="wp-caption-text">The MTR on this machine is 3.76 minutes.  A 3 minute buffer would cover 92% of all downtimes on this machine.  What would be the machine and facilities cost of capturing that last 8%?</p></div>
<p><strong>How do I reduce MTR?</strong><br />
MTR is made up of three components:  Knowing, Finding, and Fixing.  You must reduce one of these three to reduce MTR.</p>
<p><a href="http://www.garvey.com/wp-content/uploads/2010/09/light-stack.jpg"><img class="size-full wp-image-1188 alignleft" title="light-stack" src="http://www.garvey.com/wp-content/uploads/2010/09/light-stack.jpg" alt="" width="115" height="115" /></a><strong>Knowing:</strong> The time it takes for anyone to realize the machine has malfunctioned and requires human intervention.  The ways to reduce this component are by adding alerts (light stacks, alarms) or operators to continually watch the equipment.</p>
<p><strong>Finding:</strong> The time it takes for someone to find out what the problem is.  This step can be reduced by programming helpful error messages into the machine&#8217;s HMI that tell you exactly where the problem is.  Modern photocopiers do this by telling you where the likely jam points are.  When training operators, make sure they know what the most common malfunction reasons are so they can check those areas first.</p>
<p><strong>Fixing:</strong>:  The time it takes to actually fix this problem.  Reducing this step is the hardest and most difficult to change once a machine is installed.  Hopefully this has been thought about and discussed during the design phase of the equipment.  Machines that are easy to repair must start and stop gracefully, have disconnects easily within reach, accessible doors and guarding, and easily explained repair instructions.</p>
<p>In many cases, the first two steps take far longer than the third so there is a lot of room for improvement.  Reducing MTR helps keep your line running efficiently and allow you to tolerate more frequent hiccups in production.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2010/09/what-does-mtr-stand-for/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>Accumulation Tables in a Puck Line</title>
		<link>http://www.garvey.com/2010/03/accumulation-tables-in-a-puck-line/</link>
		<comments>http://www.garvey.com/2010/03/accumulation-tables-in-a-puck-line/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 20:46:07 +0000</pubDate>
		<dc:creator>Ben Garvey</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[line analysis]]></category>
		<category><![CDATA[machines]]></category>
		<category><![CDATA[packaging]]></category>
		<category><![CDATA[pucks]]></category>

		<guid isPermaLink="false">http://www.garvey.com/?p=1056</guid>
		<description><![CDATA[In our previous line analysis examples we looked at a linear packaging line and another with multiple paths. Today we&#8217;re looking at a puck system. A puck system is used to move unstable products through a packaging line. They&#8217;re popular in the cosmetics and personal care industries and can be purchased from a number of [...]]]></description>
			<content:encoded><![CDATA[<p>In our previous line analysis examples we looked at a <a href="http://www.garvey.com/2009/11/packaging-throughput-example/">linear packaging line</a> and <a href="http://www.garvey.com/2009/12/non-linear-throughput-analysis-of-a-packaging-line/">another with multiple paths</a>.  Today we&#8217;re looking at a puck system.</p>
<p><a href="http://www.adv-puck.com"><img src="http://www.garvey.com/wp-content/uploads/2010/03/labeling-puck_cropped.jpg" alt="" title="labeling-puck_cropped" width="165" height="211" class="aligncenter size-full wp-image-1070" /></a></p>
<p>A puck system is used to move unstable products through a packaging line.  They&#8217;re popular in the cosmetics and personal care industries and can be purchased from a number of vendors such as <a href="http://www.adv-puck.com">Advantage Puck</a>.   The pucks and the products are separated at the end of the line and the pucks must be conveyed and reintroduced back to the beginning.  A puck system provides a unique challenge for our line analysis calculation because stoppages in the line affect the flow of pucks upstream and downstream simultaneously.</p>
<p>Let&#8217;s look at a simple example of three machines.</p>
<div id="attachment_1058" class="wp-caption aligncenter" style="width: 581px"><a href="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-1.png"><img class="size-full wp-image-1058" title="puck-packaging-line-1" src="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-1.png" alt="Three machines in a packaging line using pucks " width="571" height="151" /></a><p class="wp-caption-text">Three machines in a packaging line with a puck return system.</p></div>
<p>Like any normal packaging line, this line has a constraint.  Machine A runs at 300 products per minute (ppm) and the line can&#8217;t go any faster than that.  Machine B accepts products from Machine A and sends them to Machine C.  Machine C performs some sort of operation on the product, removes the product from the puck, and returns the empty back back to Machine A.  If any machine malfunctions, all other machines must also shut down.  Normally we can add an accumulation to help protect the constraint from the downtimes on other machines like this:</p>
<div id="attachment_1059" class="wp-caption aligncenter" style="width: 581px"><a href="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-2.png"><img class="size-full wp-image-1059" title="puck-packaging-line-2" src="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-2.png" alt="We added an accumulation table between Machines A and B." width="571" height="151" /></a><p class="wp-caption-text">We added an accumulation table between Machines A and B to improve throughput, but does it help?</p></div>
<p>Unfortunately, Machine A requires a steady stream of empty pucks from Machine C to run.  Downtimes on Machines B and C interrupt this stream, so despite having an accumulator downstream to allow A to keep running, line production shuts down anyway.</p>
<div id="attachment_1061" class="wp-caption aligncenter" style="width: 571px"><a href="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-4.png"><img class="size-full wp-image-1061" title="puck-packaging-line-4" src="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-4.png" alt="Downtime on Machine C cuts off the flow of empty pucks to Machine A, shutting down the whole line." width="561" height="152" /></a><p class="wp-caption-text">Downtime on Machine C cuts off the flow of empty pucks to Machine A, shutting down the whole line.</p></div>
<div id="attachment_1062" class="wp-caption aligncenter" style="width: 556px"><a href="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-5.png"><img class="size-full wp-image-1062" title="puck-packaging-line-5" src="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-5.png" alt="The same thing happens for downtime on Machine B." width="546" height="156" /></a><p class="wp-caption-text">The same thing happens for downtime on Machine B.</p></div>
<p>We solve this problem by placing a second buffer upstream from the constraint in the empty puck return conveyor.</p>
<div id="attachment_1063" class="wp-caption aligncenter" style="width: 563px"><a href="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-6.png"><img class="size-full wp-image-1063" title="puck-packaging-line-6" src="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-6.png" alt="A second accumulator primed with empty pucks will allow the constraint to keep running. " width="553" height="155" /></a><p class="wp-caption-text">A second accumulator primed with empty pucks will allow the constraint to keep running.</p></div>
<p>If we have downtime on B or C, the second accumulator that was pre-primed with empty pucks will start emptying out and the original accumulation table will start to fill up at a rate of 300ppm.  If the malfunctions on B or C are corrected before these tables empty out or fill up, then no production has been lost and throughput has been increased.</p>
<div id="attachment_1065" class="wp-caption aligncenter" style="width: 563px"><a href="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-71.png"><img class="size-full wp-image-1065" title="puck-packaging-line-7" src="http://www.garvey.com/wp-content/uploads/2010/03/puck-packaging-line-71.png" alt="if B or C malfunctions, the first accumulator starts to fill up and the second starts to empty out, but the important thing is that Machine A keeps going." width="553" height="155" /></a><p class="wp-caption-text">If B or C malfunctions, the first accumulator starts to fill up and the second starts to empty out, but the important thing is that Machine A keeps going.</p></div>
<p>Some important notes and questions:</p>
<p><strong>How big should the accumulation tables be?</strong><br />
Both tables should hold enough products to handle the longest average repair time of any non-constraint machine, plus the number of pucks in transit.</p>
<p><strong>Do the tables have to be the same size?</strong><br />
If you have two tables, they must be the same size because they are emptying out and filling up at the same time.</p>
<p><strong>Does the second accumulator have to be in the empty puck return section?</strong><br />
No, but for the majority of cases it is the best place.  Otherwise you will have to remove all the empty pucks from the system at the end of a shift or allow empty pucks to pass through machines without products in them.  It makes sense from throughput standpoint and an operations perspective to accumulate all the empty pucks on accumulator 2 at the end of the shift.</p>
<p><strong>How many pucks should I put on the system?</strong><br />
Fill the accumulation table prior to Machine A with empty pucks and don&#8217;t put any more on.  Adding more pucks will decrease the line&#8217;s throughput.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.garvey.com/2010/03/accumulation-tables-in-a-puck-line/feed/</wfw:commentRss>
		<slash:comments>0</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>

