<?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>Lean Sigma Supply Chain &#187; Supply Chain</title>
	<atom:link href="http://www.resourcesystemsconsulting.com/blog/archives/category/supply-chain/feed" rel="self" type="application/rss+xml" />
	<link>http://www.resourcesystemsconsulting.com/blog</link>
	<description>Thoughts on Supply Chain with a Lean and Six Sigma twist.</description>
	<lastBuildDate>Thu, 22 Sep 2011 09:26:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Square Root Law &#8211; inventory in multiple locations</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2606</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2606#comments</comments>
		<pubDate>Tue, 02 Aug 2011 02:13:36 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Logistics]]></category>
		<category><![CDATA[Supply Chain]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2606</guid>
		<description><![CDATA[<p id="top" />Got asked what would happen to inventory when the number of stocking locations change.  I thought for a minute and remembered a quick estimate.  The Square Root Law states that total safety stock can be approximated by multiplying the total inventory by the square root of the number of future warehouse locations divided by the current number.</p> <p>X2 = (X1) * √ (n2/n1)</p> <p>n1 = number of existing facilities</p> <p>n2 = number of future facilities</p> <p>X1 = existing inventory</p> <p>X2 = future inventory</p> <p>&#160;</p> <p>Here&#8217;s an example:</p> <p>Current inventory is 4000 units, 2 facilities grow to 8.  Using the square root law the future inventory = (4000) * √ (8/2) = 8000 units.</p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> ]]></description>
			<content:encoded><![CDATA[<p id="top" />Got asked what would happen to inventory when the number of stocking locations change.  I thought for a minute and remembered a quick estimate.  The Square Root Law states that total safety stock can be approximated by multiplying the total inventory by the square root of the number of future warehouse locations divided by the current number.</p>
<p>X2 = (X1) * √ (n2/n1)</p>
<p>n1 = number of existing facilities</p>
<p>n2 = number of future facilities</p>
<p>X1 = existing inventory</p>
<p>X2 = future inventory</p>
<p>&nbsp;</p>
<p>Here&#8217;s an example:</p>
<p>Current inventory is 4000 units, 2 facilities grow to 8.  Using the square root law the future inventory = (4000) * √ (8/2) = 8000 units.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2606/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Safety Stock to Bridge the Forecast-Accuracy Gap</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2550</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2550#comments</comments>
		<pubDate>Mon, 20 Jun 2011 15:00:55 +0000</pubDate>
		<dc:creator>David McPhetrige</dc:creator>
				<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Inventory Reduction]]></category>
		<category><![CDATA[Supply Chain Modeling]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2550</guid>
		<description><![CDATA[<p id="top" />(From David McPhetrige, founder of TopDown Lean Systems, LLC, providing correct, comprehensive, multi-attribute safety-stock analysis, http://topdownleansystems.com.)</p> <p>Surveys indicate that even world-class companies have average forecast accuracy in only the high 70%’s, especially at the SKU or component level that makes or breaks service levels and financial performance. Contributors to forecast inaccuracy include factors that can be addressed through best practices, and factors that will always be unpredictable:</p> Chronic bias, which can be minimized with effective Sales/Inventory/Operations Planning, or SIOP. (It’s a safe bet that world-class businesses are already doing this, and they are still achieving only high 70%’s.) Unforeseen and unforeseeable special causes, such as natural disasters. <p>The reality is that forecasting can be only so accurate, in part because it predicts the timing and magnitude of only three types of variation:</p> Trend Seasonality Certain foreseeable special causes, such as promotions <p>A forecast can predict the timing and magnitude of these variations [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />(From David McPhetrige, founder of TopDown Lean Systems, LLC, providing correct, comprehensive, multi-attribute safety-stock analysis, <a href="http://topdownleansystems.com/">http://topdownleansystems.com</a>.)</p>
<p>Surveys indicate that even world-class companies have average forecast accuracy in only the high 70%’s, especially at the SKU or component level that makes or breaks service levels and financial performance. Contributors to forecast inaccuracy include factors that can be addressed through best practices, and factors that will always be unpredictable:</p>
<ul>
<li>Chronic bias, which can be minimized with effective Sales/Inventory/Operations Planning, or SIOP. (It’s a safe bet that world-class businesses are already doing this, and they are still achieving only high 70%’s.)</li>
</ul>
<ul>
<li>Unforeseen and unforeseeable special causes, such as natural disasters.</li>
</ul>
<p>The reality is that forecasting can be only so accurate, in part because it predicts the timing and magnitude of only three types of variation:</p>
<ol>
<li>Trend</li>
<li>Seasonality</li>
<li>Certain foreseeable special causes, such as promotions</li>
</ol>
<p>A forecast can predict the timing and magnitude of these variations only so well. Realistically, then, many businesses – and even world-class companies – are left with a significant forecast-accuracy gap that, if not bridged, compromises target fill rates, inventory performance and financial goals.</p>
<p>So first, how do you bridge this gap today? Obviously, you strive continuously to improve your forecasting accuracy, and you always will. That said, though, here are some bridging “techniques” that I’ve observed and even been part of, and likely you can think of some that I’ve missed:</p>
<ul>
<li>Mind-set: Complain about, but begrudgingly resign yourself to, suboptimal inventory and fill-rate performance, and related costs and risks</li>
<li>P&amp;L: Increase the budget for airfreight, expediters or other expediting costs and expenses</li>
<li>Balance Sheet: Increase safety-stock levels</li>
<li>Obsolete/Slow-moving: Increase efforts to return excess materials to suppliers</li>
</ul>
<p>Some of these techniques can and do help achieve service-level targets. But at a minimum, they rarely help, and may in fact hurt, financial performance. Fortunately, a financially-beneficial service-level bridge from forecast to reality is right there in your data! How so?</p>
<p>Well, there is still variation that’s left over after bias, unforeseeable special causes and the three variations with predictable timing: Common-cause random variation in demand (or usage, for components) and replenishment lead time.</p>
<p>The good news is that it is possible to quantify the magnitude of random variation by analyzing historical demand and/or lead-time data. Of course, the timing of random variation is unpredictable (that’s what makes it random), and this means that common-cause random variation must be addressed with properly-determined safety stock.</p>
<p>At this point, you may be saying, “I’m already doing that. I use a statistical technique to determine my safety stock levels.” Forgive the blunt and clichéd reply, but – how’s that working for you? Honestly, is your technique consistently achieving your fill-rate targets on an item-by-item basis? Or does it often seem to put too much inventory in place? And in many cases, does it put too little inventory in place, and you have to subjectively override or increase the calculated safety-stock level?</p>
<p>The fact that your safety-stock calculation is unreliable does not mean that there is no statistical solution. What it does mean, however, is that you must</p>
<ol>
<li>Properly identify and isolate the common-cause random variation from all the other variations, and</li>
<li>Use a correct, comprehensive statistical safety-stock approach that includes not just common-cause random variations in demand and lead time, but all six factors that affect safety stock, service levels, inventory performance and expediting.</li>
</ol>
<p>We aren’t talking about a spreadsheet, or perhaps an unused ERP feature. We’re talking about outside expertise in safety-stock analysis.</p>
<p>A recent CSCO Insights executive brief (from Supply Chain Digest and Cognizant) entitled “Five Strategies for Improving Inventory Management Across Complex Supply Chain Networks” recommends this as the first of five strategies: “Get Much More Granular with Safety Stock Management.” (<a href="http://www.scdigest.com/assets/reps/exec_brief_network_inventories.pdf">http://www.scdigest.com/assets/reps/exec_brief_network_inventories.pdf</a>.)</p>
<p>This brief advises using “many more attributes associated with each SKU.” The result of this expanded effort is compelling: “The greater the [safety-stock] precision a company will have.” The CSCO Insights authors advise that to do this “obviously requires a lot more work,” and that this increased analysis offers “rich dividends.” The brief concludes that pursuing the strategy of a “higher level of safety stock management” may require a “relatively uncommon skill set” that may best be provided by outside expertise.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2550/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Total Flow Management</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2510</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2510#comments</comments>
		<pubDate>Fri, 10 Jun 2011 01:28:57 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean]]></category>
		<category><![CDATA[Reviews]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Flow]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2510</guid>
		<description><![CDATA[<p id="top" /></p> <p>&#160;</p> <p>Euclides A. Coimbra and his associates at the Kaizen Institute have created a wonderful and detailed work on the application of continuous improvement to supply chains.  Here is a full exploration and application of lean from end to end of the extended value stream.  Two thumbs up!</p> <p>Some of the graphics look to once have been powerpoint and when reproduced are to small and grainy to be able to read.  There isn&#8217;t an index so finding topics is limited to the table of contents.  The book is hard bound, and printed on good paper.</p> <p>Some of the vocabulary is odd; &#8220;border of line&#8221; might be better said as&#8221; interface&#8221; or &#8220;borderline&#8221;.</p> <p>Economic Order Quantity, or as referred to in this book, Wilson&#8217;s Formula, is treated in a refreshing way.</p> <p>We can say that Wilson&#8217;s formula still applies today.  The only problem is when people assume that changeover time (or, generally [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><a title="Total Flow Management" href="http://www.amazon.com/Total-Flow-Management-Achieving-Excellence/dp/0473146592%3FSubscriptionId%3DAKIAJCG65A6MXWWI452Q%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0473146592" target="_blank"><img class="alignleft" src="http://ecx.images-amazon.com/images/I/51GgiPUznKL._SL500_.jpg" alt="" width="200" height="200" /></a></p>
<p>&nbsp;</p>
<p>Euclides A. Coimbra and his associates at the Kaizen Institute have created a wonderful and detailed work on the application of continuous improvement to supply chains.  Here is a full exploration and application of lean from end to end of the extended value stream.  Two thumbs up!</p>
<p>Some of the graphics look to once have been powerpoint and when reproduced are to small and grainy to be able to read.  There isn&#8217;t an index so finding topics is limited to the table of contents.  The book is hard bound, and printed on good paper.</p>
<p>Some of the vocabulary is odd; &#8220;border of line&#8221; might be better said as&#8221; interface&#8221; or &#8220;borderline&#8221;.</p>
<p>Economic Order Quantity, or as referred to in this book, Wilson&#8217;s Formula, is treated in a refreshing way.</p>
<blockquote><p>We can say that Wilson&#8217;s formula still applies today.  The only problem is when people assume that changeover time (or, generally speaking, ordering cost) is rigid and cannot be reduced.  Many people don&#8217;t think to do Wilson&#8217;s calculations because they are still misled by two strong paradigms: <em>flow at any cost</em> and <em>efficiency at any cost</em>.</p>
<p>The &#8216;flow at any cost&#8217; paradigm is a rising paradigm that is currently gaining in popularity.  People hear about the wonderful Toyota Production System (TPS) and start to increase the flow by reducing the batch sizes blindly, without looking at Wilson&#8217;s formula.  What happens is that the CAPEX requirements explode, because the small batch sizes together with big changeover times decrease efficiency.  The result is that flow is indeed achieved &#8211; but at the expense of capital expenditure, not by internally reducing the changeover time and increasing equipment flexibility.  You can see this effect in many rich companies that are implementing Lean manufacturing and the TPS.</p></blockquote>
<p>For a more in depth review check out Jon Miller&#8217;s posting on Gemba Panta Rei,<br />
<a href="http://www.gembapantarei.com/2011/04/review_of_total_flow_management_by_euclides_coimbr.html">Review of Total Flow Management by Euclides Coimbra</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2510/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Demand Segmentation and Building a Lean Fulfillment Stream</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2506</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2506#comments</comments>
		<pubDate>Thu, 09 Jun 2011 21:56:55 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean]]></category>
		<category><![CDATA[Reviews]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Demand]]></category>
		<category><![CDATA[Demand Segmentation]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2506</guid>
		<description><![CDATA[<p id="top" /></p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> <p>Hot off the press from the Lean Enterprise Institute &#8230;</p> <p>Page 12 &#38; 13 have a brief description of Coefficient of Variation and a SKU Scatter Diagram (weekly volume vs. SKU stability).  10 weeks usually isn&#8217;t sufficient for meaningful or statistically significant calculation of standard deviation.</p> <p>The guidelines given need to be tempered with the granularity of the data.  While a coefficient of variation of less than 1.0 can be considered stable for weekly data, it would be considered very noisy when using monthly data and quite stable when using daily demand.</p> <p>This small quibble aside the authors Martichenko and von Grabe do a wonderful job describing lean principles for the supply chain, or as they prefer, the fulfillment stream.</p> <p>&#160; &#160;</p> <p>&#160;</p> ]]></description>
			<content:encoded><![CDATA[<p id="top" /><a href="http://www.amazon.com/Building-Fulfillment-Stream-Robert-Martichenko/dp/1934109193%3FSubscriptionId%3DAKIAJCG65A6MXWWI452Q%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1934109193" target="_blank"><img class="alignleft" style="margin-left: 10px; margin-right: 10px;" title="Building a Lean Fulfillment Stream" src="http://ecx.images-amazon.com/images/I/51GySCCqC8L.jpg" alt="" width="244" height="298" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Hot off the press from the <a title="Lean Enterprise Institute" href="http://www.lean.org/" target="_blank">Lean Enterprise Institute</a> &#8230;</p>
<p>Page 12 &amp; 13 have a brief description of <a title="Demand Segmentation" href="http://www.resourcesystemsconsulting.com/blog/archives/tag/demand-segmentation" target="_blank">Coefficient of Variation</a> and a SKU Scatter Diagram (weekly volume vs. SKU stability).  10 weeks usually isn&#8217;t sufficient for meaningful or statistically significant calculation of standard deviation.</p>
<p>The guidelines given need to be tempered with the granularity of the data.  While a coefficient of variation of less than 1.0 can be considered stable for weekly data, it would be considered very noisy when using monthly data and quite stable when using daily demand.</p>
<p>This small quibble aside the authors Martichenko and von Grabe do a wonderful job describing lean principles for the supply chain, or as they prefer, the fulfillment stream.</p>
<p>&nbsp;<br />
&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2506/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Replenishment Strategies</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2502</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2502#comments</comments>
		<pubDate>Thu, 09 Jun 2011 21:09:58 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean]]></category>
		<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Demand Profile]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2502</guid>
		<description><![CDATA[<p id="top" />Determining an appropriate production model starts with Demand Profile and Demand Segmentation.  High volume low variability items, and low volume high variability items behave very differently.  How to decide if a particular product is a candidate for a one piece flow cell or a craftsmen job bench?  Look to the coefficient of variation for a clue.</p> <p></p> <p>&#160;</p> <p>Type 1 &#8211; Rate-base or Just-in-time</p> forecasting of the flow rate or takt time RCCP &#8211; rough  cut capacity planning to monitor impact of mix and volume on pace maker operation produce to rate (or TAKT) vs discrete order or customer pull demand flow vs time-phased requirements planning maintain flow priority and timing no detailed Capacity Requirements Planning required no or minimal shop order launch or inventory transactions highly visual and standardized shop floor control “one-piece” flow, zero inventory, standard WIP &#8211; work-in-process seamless flow/pull of material Dynamic cycle time (Little’s Law) <p>Type 2 [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />Determining an appropriate production model starts with <a title="How to do a Demand Profile" href="http://www.resourcesystemsconsulting.com/blog/archives/2484" target="_blank">Demand Profile</a> and <a title="How to do a Demand Segmentation analysis" href="http://www.resourcesystemsconsulting.com/blog/archives/110" target="_blank">Demand Segmentation</a>.  High volume low variability items, and low volume high variability items behave very differently.  How to decide if a particular product is a candidate for a one piece flow cell or a craftsmen job bench?  Look to the coefficient of variation for a clue.</p>
<p><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/VolVar.png"><img class="aligncenter size-full wp-image-2503" title="VolVar" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/VolVar.png" alt="Demand Segmentation - Volume vs Variability" width="542" height="419" /></a></p>
<p>&nbsp;</p>
<p><strong>Type 1 &#8211; Rate-base or Just-in-time</strong></p>
<div>
<ul>
<li>forecasting of the flow rate or takt time</li>
<li>RCCP &#8211; rough  cut capacity planning to monitor impact of mix and volume on pace maker operation</li>
<li>produce to rate (or TAKT) vs discrete order or customer pull</li>
<li>demand flow vs time-phased requirements planning</li>
<li>maintain flow priority and timing</li>
<li>no detailed Capacity Requirements Planning required</li>
<li>no or minimal shop order launch or inventory transactions</li>
<li>highly visual and standardized shop floor control</li>
<li>“one-piece” flow, zero inventory, standard WIP &#8211; work-in-process</li>
<li>seamless flow/pull of material</li>
<li>Dynamic cycle time (Little’s Law)</li>
</ul>
<p><strong>Type 2 &#8211; Pull</strong></p>
<ul>
<li>combination of discrete forecasting and/or demand rate-based forecasting</li>
<li>MRP planning &#8212; pull Kanban, Heijunka visual shop floor control</li>
<li>RCCP, but no detailed CRP</li>
<li>flat Bills Of Materials</li>
<li>more cellular manufacturing</li>
<li>point-of-use vs. central stores</li>
<li>inventory is strategic: standard inventory, time-based replenishment, pull based on consumption vs. push based on demand</li>
<li>based on statistically balanced rate, build to level-loaded demand with calculated standard inventory buffers</li>
</ul>
<p><strong>Type 3 &#8211; Push or Job Shop Discrete</strong></p>
<div>
<ul>
<li>discrete requirements planning (firm orders and long range forecast)</li>
<li>Rough Cut Capacity Plan</li>
<li>time phasing of requirements</li>
<li>application of order policies: lead time, safety stock &amp; time</li>
<li>Capacity Requirements Planning</li>
<li>MRP shop order launch &amp; order maintenance (message filters and “noise management”)</li>
<li>ability to aggregate disparate requirements across multiple products by work center, supplier, product</li>
<li>central stores of inventory</li>
<li>multi-level inventory: stores, pick, kit, move, queue</li>
<li>batch processing</li>
<li>demand leveling difficult and uneconomical</li>
</ul>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2502/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Demand Profile</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2484</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2484#comments</comments>
		<pubDate>Wed, 01 Jun 2011 16:28:00 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Demand Profile]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2484</guid>
		<description><![CDATA[<p id="top" />Maslow&#8217;s hammer, or a golden hammer is an over-reliance on a familiar tool; as Abraham Maslow said in 1966 in A Psychology of Science, &#8220;It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.&#8221;  So, must every product in every business segment be set up in a one piece flow cell? Or put on kanban with an heijunka to smooth demand? Or run on a rate-based assembly line? Certainly not!  One size rarely fits all.  But how to know which techniques make sense?</p> <p>One place to start is to look at customer demand. All lean practitioners know about Takt Time, or the customer drum beat, and is used to match the pace of an operation with customer demand.  Takt Time is calculated at Available Time/Demand, and is by definition an average.  Customer demand is anything but average, and so we need [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />Maslow&#8217;s hammer, or a golden hammer is an over-reliance on a familiar tool; as Abraham Maslow said in 1966 in <a title="A Psychology of Science by A. Maslow" href="http://books.google.com/books?id=3_40fK8PW6QC&amp;printsec=frontcover#v=onepage&amp;q&amp;f=false" target="_blank"><em>A Psychology of Science</em></a>, &#8220;It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail.&#8221;   So, must every product in every business segment be set up in a one piece flow cell?  Or put on kanban with an heijunka to smooth demand?  Or run on a rate-based assembly line?  Certainly not!  One size rarely fits all.  But how to know which techniques make sense?</p>
<p>One place to start is to look at customer demand.  All lean practitioners know about Takt Time, or the customer drum beat, and is used to match the pace of an operation with customer demand.  Takt Time is calculated at Available Time/Demand, and is by definition an average.  Customer demand is anything but average, and so we need to understand the variation or range of demand placed on our process.</p>
<p>Here&#8217;s an example &#8230;</p>
<p><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/TimeSeries.png"><img class="aligncenter size-full wp-image-2485" title="TimeSeries" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/TimeSeries.png" alt="" width="658" height="371" /></a>To build a demand profile take the following steps:</p>
<ol>
<li>Pick the product or product family or business unit of interest.</li>
<li>Determine an appropriate time unit &#8211; hourly, daily, monthly.</li>
<li>Gather the true customer demand as best you can.  Be careful about using promise dates instead of requested dates, and be doubly cautious of schedules which are often smoothed, filtered, or otherwise manipulated.</li>
<li>Create the graph or time series plot as above.</li>
<li>Now calculate some simple descriptive statistics.  In this example the average is 17 with a range of 49 and a standard deviation of 11.</li>
</ol>
<p>What can we conclude?  Should we design our operations control around a demand rate of 17 a day?  Is the variation in demand something we can deal with?  How?</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2484/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>21st Century Supply Chains Require Demand Driven Rules and Tools</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2474</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2474#comments</comments>
		<pubDate>Tue, 10 May 2011 01:00:27 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Demand]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2474</guid>
		<description><![CDATA[<p id="top" />Here&#8217;s an interesting argument for repackaging MRP for pull by Chad Smith &#38; Carol Ptak 21st Century Supply Chains Require Demand Driven Rules and Tools.</p> <p>Perhaps new technology can address the limitations of classic material requirements planning.</p> <p>Any thoughts?</p> <p>&#160;</p> ]]></description>
			<content:encoded><![CDATA[<p id="top" />Here&#8217;s an interesting argument for repackaging MRP for pull by <strong> </strong><strong><a>Chad Smith &amp; Carol Ptak</a></strong><br />
<a href="http://www.softwareadvice.com/articles/manufacturing/demand-driven-mrp-105062011/">21st Century Supply Chains Require Demand Driven Rules and Tools.</a></p>
<p>Perhaps new technology can address the limitations of classic material requirements planning.</p>
<p>Any thoughts?</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2474/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips for sizing your warehouse</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2357</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2357#comments</comments>
		<pubDate>Thu, 24 Mar 2011 11:55:29 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Logistics]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Warehouse Layout]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2357</guid>
		<description><![CDATA[<p id="top" /></p> Don&#8217;t get fooled by &#8220;averages&#8221; Consider using statistical tools, such as standard deviation, to analyze operational data &#8211; both in and out bound Understand which system components can expand by adding labor, and which can&#8217;t Design expansion capability in from the start; SKU count almost always goes up, not down over time Get executives to sign off on future sales projections that will serve as the basis of the design; if they won&#8217;t or can&#8217;t, then round up Be very leery of unrealized plans to increase inventory turns; easier said then done Consider ability to add overtime and additional shifts to expand initial system capacity Recognize more companies regret having less capacity than those that think systems were over-specified You can usually add labor to increase throughput in pick modules, but if a sorter is maxed out, there is not much you can usually [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/WhseLayout.png"><img class="size-full wp-image-2358 alignleft" style="margin-left: 15px; margin-right: 15px;" title="WhseLayout" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/WhseLayout.png" alt="" width="600" height="421" /></a></p>
<ul type="disc">
<li>Don&#8217;t get fooled by &#8220;averages&#8221;</li>
<li>Consider using statistical tools, such as standard deviation, to analyze operational data &#8211; both in and out bound</li>
<li>Understand which system components can expand by adding labor, and which can&#8217;t</li>
<li>Design expansion capability in from the start; SKU count almost always goes up, not down over time</li>
<li>Get executives to sign off on future sales projections that will serve as the basis of the design; if they won&#8217;t or can&#8217;t, then round up</li>
<li>Be very leery of unrealized plans to increase inventory turns; easier said then done</li>
<li>Consider ability to add overtime and additional shifts to expand initial system capacity</li>
<li>Recognize more companies regret having less capacity than those that think systems were over-specified</li>
<li>You can usually add labor to increase throughput in pick modules, but if a sorter is maxed out, there is not much you can usually do</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2357/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ABC Analysis: how to</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2373</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2373#comments</comments>
		<pubDate>Tue, 22 Mar 2011 13:13:08 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[ABC Analysis]]></category>
		<category><![CDATA[Inventory Analysis]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2373</guid>
		<description><![CDATA[<p id="top" />&#160;</p> Make a list of part numbers Determine total quantity used over some period of time Obtaining the cost for each part Calculate usage $ value for each part by multiplying the quantity and the cost Sort the list from high to low $ Calculate the total usage $ value for all items Calculate each item&#8217;s percent of total usage $ value Select percentage cut offs for each ABC group, for example: <p></p> <p>&#160;</p> <p>Here&#8217;s an example &#8230;</p> <p></p> <p>&#160;</p> <p>Next steps</p> <p>Once you have classified your parts you can use this data to drive key materials management activities. For example, coordinating your perpetual inventory cycle counting program – you might routinely verify your Category A parts on a monthly basis but only review your category C parts twice a year.</p> <p>You might use flow orders, kanban, or VMI for your C parts but require detailed negotiated purchase orders for your A [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />&nbsp;</p>
<ol>
<li>Make a list of part numbers</li>
<li>Determine total quantity used over some period of time</li>
<li>Obtaining the cost for each part</li>
<li>Calculate usage $ value for each part by multiplying the quantity and the cost</li>
<li>Sort the list from high to low $</li>
<li>Calculate the total usage $ value for all items</li>
<li>Calculate each item&#8217;s percent of total usage $ value</li>
<li>Select percentage cut offs for each ABC group, for example:</li>
</ol>
<p><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/ABCCutoffs.png"><img class="alignnone size-full wp-image-2375" title="ABCCutoffs" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/ABCCutoffs.png" alt="" width="280" height="96" /></a></p>
<p>&nbsp;</p>
<p>Here&#8217;s an example &#8230;</p>
<p><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/ABCExample.png"><img class="alignnone size-full wp-image-2374" title="ABCExample" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/ABCExample.png" alt="Example of ABC Analysis" width="323" height="296" /></a></p>
<p>&nbsp;</p>
<p>Next steps</p>
<p>Once you have classified your parts you can use this data to drive key materials  management activities.  For example, coordinating your perpetual inventory  cycle counting program – you might routinely verify your Category A parts on  a monthly basis but only review your category C parts  twice a year.</p>
<p>You might use flow orders, kanban, or VMI for your C parts but require detailed negotiated purchase orders for your A  parts.</p>
<p>In a warehouse you might want to be sure the A items are near the shipping dock and the C items are toward the back.</p>
<p>You might even want to take a close look at the C items and purge a few.</p>
<p>The main point is &#8211; one size doesn&#8217;t fit all parts, choose the materials management approach that best serves each inventory category.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2373/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bullwhip Effect</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2321</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2321#comments</comments>
		<pubDate>Fri, 18 Mar 2011 20:07:00 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Strategy]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Bullwhip]]></category>
		<category><![CDATA[Supply Chain Strategy]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2321</guid>
		<description><![CDATA[<p id="top" />The bullwhip effect is the result of uncertainty caused from distorted information flowing up and down the supply chain.  The bullwhip effect is caused by fluctuations in information supplied to firms further up the supply chain. Distorted information causes firms to forecast demand incorrectly.  Thereby, many unnecessary costs are put upon each of the firms along the supply chain.  Nearly all industries are affected!  Firms that experience large variations in demand are at risk.  Firms that depend on suppliers upstream or distributors and retailers downstream may be at risk.   Most firms are affected by the bullwhip effect.  The bullwhip effect used to be considered a normal phenomenon.  However, recently, many firms have been trying to focus on how to improve communication along the supply chain.  The bullwhip effect can inflict many unnecessary costs on business firms.  Inventory costs from stored inventory, problems with quality caused from rapid production, overtime expenses for increased [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />The bullwhip effect is the result of uncertainty caused from distorted information flowing up and down the supply chain.  The bullwhip effect is caused by fluctuations in information supplied to firms further up the supply chain. Distorted information causes firms to forecast demand incorrectly.  Thereby, many unnecessary costs are put upon each of the firms along the supply chain.  Nearly all industries are affected!  Firms that experience large variations in demand are at risk.  Firms that depend on suppliers upstream or distributors and retailers downstream may be at risk.   Most firms are affected by the bullwhip effect.  The bullwhip effect used to be considered a normal phenomenon.  However, recently, many firms have been trying to focus on how to improve communication along the supply chain.  The bullwhip effect can inflict many unnecessary costs on business firms.  Inventory costs from stored inventory, problems with quality caused from rapid production, overtime expenses for increased employee labor, and increased units being shipped create costs far and beyond normal levels of production.  Customers can also lose faith in a firms ability to deliver products.  This is because firms are having trouble meeting demand.  Likewise, firms often must lengthen lead time for finished goods, which also may discourage customers, which in turn leads to lost sales.  In a worst case, incorrect forecasts may entice a company to adjust capacity which could be detrimental to the overall success of the company.  To reduce stocked product, retailers may offer sales promotions to customers.  If retailers fail to notify firms upstream in the supply chain, these firms may forecast increased sales as legitimate demand.  Thereby producing product that was not wanted by the customer in the first place.  Furthermore, salesforce incentives may entice selling products to firms to meet targets.  This may cause large inventories for the firm, or the firm may cancel the orders, which causes demand fluctuations in the supply chain.   Firms upstream in the supply chain may feel that the increased demand may be legitimate and increase production and inventory levels to produce more.  However, in reality, the product hardly moved and required a drop in price to be moved off of retailer’s shelves.  Each firm upstream in the supply chain will feel the whip effect.</p>
<p>Here&#8217;s the classic illustration from <a title="Bullwhip effect in supply chains" href="http://www70.homepage.villanova.edu/matthew.liberatore/VSB3008/9712170320.pdf" target="_blank">The Bullwhip Effect in Supply Chains</a> by Hau L. Lee • V. Padmanabhan • Seungjin Whang, SLOAN MANAGEMENT REVIEW/SPRING 1997.</p>
<p><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/Bullwhip.png"><img class="aligncenter size-full wp-image-2322" title="Bullwhip" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/Bullwhip.png" alt="" width="600" height="405" /></a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2321/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

