<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Lean Sigma Supply Chain</title>
	
	<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>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/resourcesystemsconsulting/ZiAJ" /><feedburner:info uri="resourcesystemsconsulting/ziaj" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://feeds.feedburner.com/resourcesystemsconsulting/ZiAJ" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare href="http://www.wikio.com/subscribe?url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><feedburner:feedFlare href="http://www.flurry.com/pushRssFeed.do?r=fb&amp;url=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.flurry.com/images/flurry_rss_logo2.gif">Subscribe with Flurry</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsalloy.com/?rss=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.newsalloy.com/subrss3.gif">Subscribe with NewsAlloy</feedburner:feedFlare><feedburner:feedFlare href="http://download.attensa.com/app/get_attensa.html?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fresourcesystemsconsulting%2FZiAJ" src="http://www.attensa.com/blogs/attensa/WindowsLiveWriter/BadgeredintoBadges_10C02/attensa_feed_button5.gif">Subscribe with Attensa for Outlook</feedburner:feedFlare><feedburner:browserFriendly>Hope you like the posts.  Drop a comment and add to the knowledge bank!</feedburner:browserFriendly><item>
		<title>Square Root Law – inventory in multiple locations</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/QWOivXq6_MM/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=QWOivXq6_MM:_EwEzkD0oyE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=QWOivXq6_MM:_EwEzkD0oyE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=QWOivXq6_MM:_EwEzkD0oyE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=QWOivXq6_MM:_EwEzkD0oyE:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=QWOivXq6_MM:_EwEzkD0oyE:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=QWOivXq6_MM:_EwEzkD0oyE:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/QWOivXq6_MM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2606/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2606</feedburner:origLink></item>
		<item>
		<title>Visual Office</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/kcXvNupETtU/2588</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2588#comments</comments>
		<pubDate>Fri, 29 Jul 2011 00:30:59 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean]]></category>
		<category><![CDATA[5S]]></category>
		<category><![CDATA[Office 5S]]></category>
		<category><![CDATA[Visual Office]]></category>
		<category><![CDATA[Visual Workplace]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2588</guid>
		<description><![CDATA[<p id="top" />Where do you want to work?  If you&#8217;ve ever been to Disney or Epcot you may remember the experience.  You park your car or get off the tram and you don&#8217;t need to be able to read a map, or the signs, you just follow the walkways and it just seems obvious where to go and how to get there.  A ton of science goes into making the experience at the Magic Kingdom completely different from that of the traveling carnival that shows up at the edge of town in the empty lot next to the volunteer fire house.  At the carnival you can&#8217;t get from here to there, if you even can figure out where there is.  Kids may have a bunch of fun at either, but the parental stress level is completely different between the two amusement parks.</p> <p>Which of the two do you want your office or shop floor [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />Where do you want to work?  If you&#8217;ve ever been to Disney or Epcot you may remember the experience.  You park your car or get off the tram and you don&#8217;t need to be able to read a map, or the signs, you just follow the walkways and it just seems obvious where to go and how to get there.  A ton of science goes into making the experience at the Magic Kingdom completely different from that of the traveling carnival that shows up at the edge of town in the empty lot next to the volunteer fire house.  At the carnival you can&#8217;t get from here to there, if you even can figure out where there is.  Kids may have a bunch of fun at either, but the parental stress level is completely different between the two amusement parks.</p>
<p>Which of the two do you want your office or shop floor to be like, Disney or the carnival?  If Disney is your destination, how do you get from here to there?</p>
<ol>
<li>Information is the output of an office.  Information can take many forms: email, databases, presentations,decisions.</li>
<li>Wastes of Defects, Storage, Motion, Overprocessing, Waiting, Overproduction all occur in much the same ways as on a factory floor.  For example motion can be seen in walking, reaching, searching, questioning, interrupting.  Each of these activities cause delays and stress.  But we adapt and accept and live with the abnormal.  We just get used to it.</li>
<li>Time is the inventory of the office.  Time piles up in our in-boxes and databases.  Time happens when work stops.  We run out of information, need a signature, find a mistake and then set that work aside and pick up some other job, file, task.  We keep busy.  But the thing we were working on sits and waits, the clock ticking away.</li>
</ol>
<p>Making the abnormal viable, finding where the time is piling up isn&#8217;t easy, but that&#8217;s the mission of the visual office; making the piles of time visible, and then once we can see the inventory of time we just might get uncomfortable and creative and go do something to reduce the inventory, and speed up the flow.</p>
<p>&nbsp;</p>
<p>Here are a couple references &#8230;</p>
<p><a href="http://www.amazon.com/Office-Kaizen-Transforming-Operations-Competitive/dp/0873895568%3FSubscriptionId%3DAKIAJCG65A6MXWWI452Q%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0873895568"><img title="Office Kaizen" src="http://ecx.images-amazon.com/images/I/51JdLIvmDWL.jpg" alt="" width="223" height="350" /></a><a href="http://www.amazon.com/5S-Office-Organizing-Workplace-Eliminate/dp/1563273187%3FSubscriptionId%3DAKIAJCG65A6MXWWI452Q%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1563273187"><img title="5S for the Office" src="http://ecx.images-amazon.com/images/I/51rOC8U%2BfmL.jpg" alt="" width="269" height="350" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=kcXvNupETtU:rKt0-Bh6o2c:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=kcXvNupETtU:rKt0-Bh6o2c:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=kcXvNupETtU:rKt0-Bh6o2c:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=kcXvNupETtU:rKt0-Bh6o2c:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=kcXvNupETtU:rKt0-Bh6o2c:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=kcXvNupETtU:rKt0-Bh6o2c:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/kcXvNupETtU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2588/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2588</feedburner:origLink></item>
		<item>
		<title>Table top simulation – dock operations</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/n3mBd9neCcQ/2558</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2558#comments</comments>
		<pubDate>Wed, 22 Jun 2011 17:33:02 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean]]></category>
		<category><![CDATA[Logistics]]></category>
		<category><![CDATA[Simulation]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2558</guid>
		<description><![CDATA[<p id="top" />Simulation is the act of imitating or mimicking the behavior of some situation or some process by means of something suitably analogous.  The imitation of a process can be used for debugging, and validating process design changes or use to communicate or train associates.</p> <p>Simulations can be used for:</p> process design testing new ideas debugging designs testing understanding gaining commitment testing alternatives communicating and training <p>Sometimes the simulation is role playing theater, other times the &#8216;game&#8217; has logic and is reproducible, with known inputs and expected outputs.  The photo here is of a recent workshop where we studied how the warehouse dock floor would look after changing the pick waving rules and packaging.  Here outbound goods will be switching from trailer loose stack to returnable shipping containers.</p> <p>Would we need more floor space?  Do we have enough pickers and loaders?  How do we pick and load multiple deliveries nose-to-tail?</p> <p>While computer modeling [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/IMG_0505.jpg" target="_blank"><img class="size-full wp-image-2559 alignleft" style="margin-left: 10px; margin-right: 20px;" title="Warehouse dock operation simulation" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/IMG_0505.jpg" alt="Table-top simulation" width="400" height="300" /></a>Simulation is the act of imitating or mimicking the behavior of some situation or some process by  means of something suitably analogous.  The imitation of a process can be used for debugging, and validating process design changes or use to communicate or train associates.</p>
<p>Simulations can be used for:</p>
<ul>
<li>process design</li>
<li>testing new ideas</li>
<li>debugging designs</li>
<li>testing understanding</li>
<li>gaining commitment</li>
<li>testing alternatives</li>
<li>communicating and training</li>
</ul>
<p>Sometimes the simulation is role playing theater, other times the &#8216;game&#8217; has logic and is reproducible, with known inputs and expected outputs.  The photo here is of a recent workshop where we studied how the warehouse dock floor would look after changing the pick waving rules and packaging.  Here outbound goods will be switching from trailer loose stack to returnable shipping containers.</p>
<p>Would we need more floor space?  Do we have enough pickers and loaders?  How do we pick and load multiple deliveries nose-to-tail?</p>
<p>While computer modeling is certainly a consideration the use of table-top simulation has many benefits:</p>
<ul>
<li>Many problems are difficult or expensive to test in real life</li>
<li>Many people process information visually</li>
<li>A number of alternatives can be quickly tested as the team uncovers issues and finds solutions</li>
<li>Simulation costs are very low; you don&#8217;t need expensive software or extensive training</li>
</ul>
<p>Here&#8217;s the process we used to build our &#8216;war game&#8217;:</p>
<ol>
<li>Decide what we wanted to test; i.e. the output &#8211; in this case floor loading and labor resources</li>
<li>Gather the input &#8211; shipping orders for a typical busy day, number of pickers by zone, number of packing loaders, shift schedules, picking and loading rates, floor space and equipment dimensions (carts, containers, trailers, etc)</li>
<li>Determine the constraints, rules; e.g. number of loaders per trailer, length of breaks</li>
<li>Document assumptions; e.g any trailer can be at any dock door, break and lunches can be staggered, etc.</li>
<li>Be creative and design the game pieces (entities) and determine their quantities; in this exercise carts, containers, bins, trailers</li>
<li>Scale physically (1inch=5feet), scale time (1 day of 10 hours took an hour of game time)</li>
<li>Collect metrics, such as; line per hour, wave start and end time, trailer load duration, number of floor spaces occupied, number of time floor space turned over, number of workers needed</li>
</ol>
<p>Once the model &#8216;behaved&#8217; like the current process the team began introducing rule changes which uncovered obstacles.  One of the first changes was reducing the wave batch size from 90 minutes to 30.  Next came changes to packaging and trailer loading.  By the end of the workshop new procedures were debugged and ready for full scale dry runs leading to a live implementation next month.  Stay tuned &#8230;</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=n3mBd9neCcQ:yKeZmstS5X0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=n3mBd9neCcQ:yKeZmstS5X0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=n3mBd9neCcQ:yKeZmstS5X0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=n3mBd9neCcQ:yKeZmstS5X0:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=n3mBd9neCcQ:yKeZmstS5X0:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=n3mBd9neCcQ:yKeZmstS5X0:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/n3mBd9neCcQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2558/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2558</feedburner:origLink></item>
		<item>
		<title>Safety Stock to Bridge the Forecast-Accuracy Gap</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/91dfNKEZ1dc/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=91dfNKEZ1dc:zlZJtcrlfyY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=91dfNKEZ1dc:zlZJtcrlfyY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=91dfNKEZ1dc:zlZJtcrlfyY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=91dfNKEZ1dc:zlZJtcrlfyY:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=91dfNKEZ1dc:zlZJtcrlfyY:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=91dfNKEZ1dc:zlZJtcrlfyY:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/91dfNKEZ1dc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2550/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2550</feedburner:origLink></item>
		<item>
		<title>Total Flow Management</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/zSJyqzLstBo/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=zSJyqzLstBo:gF3mF4tGTVA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=zSJyqzLstBo:gF3mF4tGTVA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=zSJyqzLstBo:gF3mF4tGTVA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=zSJyqzLstBo:gF3mF4tGTVA:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=zSJyqzLstBo:gF3mF4tGTVA:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=zSJyqzLstBo:gF3mF4tGTVA:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/zSJyqzLstBo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2510/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2510</feedburner:origLink></item>
		<item>
		<title>Demand Segmentation and Building a Lean Fulfillment Stream</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/sC0wJlM6Fx8/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=sC0wJlM6Fx8:PCIfHkkblTQ:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/sC0wJlM6Fx8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2506/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2506</feedburner:origLink></item>
		<item>
		<title>Replenishment Strategies</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/JaUsU_sHrtE/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=JaUsU_sHrtE:ADOYtlKvxjQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=JaUsU_sHrtE:ADOYtlKvxjQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=JaUsU_sHrtE:ADOYtlKvxjQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=JaUsU_sHrtE:ADOYtlKvxjQ:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=JaUsU_sHrtE:ADOYtlKvxjQ:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=JaUsU_sHrtE:ADOYtlKvxjQ:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/JaUsU_sHrtE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2502/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2502</feedburner:origLink></item>
		<item>
		<title>Demand Profile</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/bszl1GOyTAE/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=bszl1GOyTAE:pZo3yqZxWV0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=bszl1GOyTAE:pZo3yqZxWV0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=bszl1GOyTAE:pZo3yqZxWV0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=bszl1GOyTAE:pZo3yqZxWV0:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=bszl1GOyTAE:pZo3yqZxWV0:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=bszl1GOyTAE:pZo3yqZxWV0:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/bszl1GOyTAE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2484/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2484</feedburner:origLink></item>
		<item>
		<title>21st Century Supply Chains Require Demand Driven Rules and Tools</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/fE8fWHr0pQc/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>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=fE8fWHr0pQc:ZnA0U7-mnSs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=fE8fWHr0pQc:ZnA0U7-mnSs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=fE8fWHr0pQc:ZnA0U7-mnSs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=fE8fWHr0pQc:ZnA0U7-mnSs:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=fE8fWHr0pQc:ZnA0U7-mnSs:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=fE8fWHr0pQc:ZnA0U7-mnSs:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/fE8fWHr0pQc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2474/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2474</feedburner:origLink></item>
		<item>
		<title>Improve Turnaround, Shutdown, and Outage Duration: After Action Review</title>
		<link>http://feedproxy.google.com/~r/resourcesystemsconsulting/ZiAJ/~3/qu5kRdsxEgA/2464</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2464#comments</comments>
		<pubDate>Fri, 22 Apr 2011 13:05:23 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean]]></category>
		<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[Lean Maintenance]]></category>
		<category><![CDATA[Outage]]></category>
		<category><![CDATA[Shutdown]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2464</guid>
		<description><![CDATA[<p id="top" />The practice of AAR comes from the military, as in the US Army&#8217;s TC25-20 &#8220;A Leader&#8217;s Guide to After-Action Reviews&#8221; 9/93.  The approach is a classic example of Plan/Do/Check/Act and after an activity, while events are still fresh we ask five questions as follows:</p> What was the plan? What actually happened? What went well?  So we can be sure to do it again. What went wrong?  So we can figure out how to do better. What are we going to do now? ]]></description>
			<content:encoded><![CDATA[<p id="top" /><img class="alignleft" style="border: 1px solid black; margin-right: 25px;" src="http://www.mccoy.army.mil/readingroom/newspaper/realmccoy/11142008/images/180_EN_CO_MCP_AAR_375x.JPG" alt="" width="375" height="251" />The practice of AAR comes from the military, as in the US Army&#8217;s TC25-20 &#8220;<a href="http://www.au.af.mil/au/awc/awcgate/army/tc_25-20/tc25-20.pdf">A Leader&#8217;s Guide to After-Action Reviews</a>&#8221; 9/93.  The approach is a classic example of Plan/Do/Check/Act and after an activity, while events are still fresh we ask five questions as follows:</p>
<ol>
<li>What was the plan?</li>
<li>What actually happened?</li>
<li>What went well?  So we can be sure to do it again.</li>
<li>What went wrong?  So we can figure out how to do better.</li>
<li>What are we going to do now?</li>
</ol>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=qu5kRdsxEgA:tKKjqFF72JQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=qu5kRdsxEgA:tKKjqFF72JQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=qu5kRdsxEgA:tKKjqFF72JQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=qu5kRdsxEgA:tKKjqFF72JQ:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?i=qu5kRdsxEgA:tKKjqFF72JQ:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?a=qu5kRdsxEgA:tKKjqFF72JQ:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/resourcesystemsconsulting/ZiAJ?d=dnMXMwOfBR0" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/resourcesystemsconsulting/ZiAJ/~4/qu5kRdsxEgA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2464/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.resourcesystemsconsulting.com/blog/archives/2464</feedburner:origLink></item>
	</channel>
</rss>

