<?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; Sigma</title>
	<atom:link href="http://www.resourcesystemsconsulting.com/blog/archives/category/sigma/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>z-Table</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/2264</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/2264#comments</comments>
		<pubDate>Thu, 20 May 2010 16:24:04 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Safety Stock]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=2264</guid>
		<description><![CDATA[<p id="top" /></p> ]]></description>
			<content:encoded><![CDATA[<p id="top" /><img title="z Normal Distribution" src="http://business.statistics.sweb.cz/normal01.jpg" alt="z Normal" width="725" height="999" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/2264/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lean Six Sigma Certification Game</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/1357</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/1357#comments</comments>
		<pubDate>Sat, 01 Aug 2009 21:26:06 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Certification]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=1357</guid>
		<description><![CDATA[<p id="top" />A friend and colleague, Bill Bentley, writes about the use of professional certifications in the recruiting industry.</p> <p>I had a long talk with a senior IT professional in Chicago last week expressing his deep frustration that despite his long and distinguished professional career, he could not get interviews without certain certifications despite being able to teach the topics himself.</p> <p>Many of you looking for jobs are facing the same problem whether you know it or not. Certifications are being used to screen out candidates because of the huge numbers of applicants. An $8/hr person or worse, a computer program, is being used to scan resumes into the little pile that the hiring manager will look at and the big pile that gets thrown away.</p> <p>Certifications which are being used A LOT for this purpose are Six Sigma, Lean, PMP and increasingly in the IT field, ITIL. In some cases the companies truly [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />A friend and colleague, <a href="http://www.value-train.com/">Bill Bentley</a>, writes about the use of professional certifications in the recruiting industry.</p>
<blockquote><p>I had a long talk with a senior IT professional in Chicago last week expressing his deep frustration that despite his long and distinguished professional career, he could not get interviews without certain certifications despite being able to teach the topics himself.</p>
<p>Many of you looking for jobs are facing the same problem whether you know it or not. Certifications are being used to screen out candidates because of the huge numbers of applicants. An $8/hr person or worse, a computer program, is being used to scan resumes into the little pile that the hiring manager will look at and the big pile that gets thrown away.</p>
<p>Certifications which are being used A LOT for this purpose are Six Sigma, Lean, PMP and increasingly in the IT field, ITIL. In some cases the companies truly want these skills but in many cases they are nothing more than `wish list&#8217; skills and objective facts that can be easily used by the resume screener for sorting.</p>
<p>If the jobs that you look at have these topics listed in the job descriptions you can be quite sure that without them, your resume is much more likely to end up in the big pile than the little pile. &#8230;</p></blockquote>
<p><a href="http://www.amazon.com/Certified-Sigma-Black-Secrets-Study/dp/B0017VSZJO%3FSubscriptionId%3D02E5W5871AJF7PMMMS82%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3DB0017VSZJO"><img class="alignright" style="margin-left: 10px;" src="http://ecx.images-amazon.com/images/I/51WHuf0TrcL._SL500_.jpg" alt="" width="148" height="191" /></a>So do you really need that certification just to get the job?  Often an organization is trying to upgrade its bench strength by requiring certification, but how do you know it&#8217;s not just a charade and a meaningless recruiting filter.  Maybe you want to be sure your prospective employer is serious, and that might take some digging and fortitude to be able to walk away from a company that&#8217;s just pretending.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/1357/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Forget the 80/20 Rule</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/1362</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/1362#comments</comments>
		<pubDate>Sat, 01 Aug 2009 13:51:37 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Pareto]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=1362</guid>
		<description><![CDATA[<p id="top" />In the late 1800s, economist and avid gardener Vilfredo Pareto established that 80% of the land in Italy was owned by 20% of the population. While gardening he later observed that 20% of the pea pods in his garden yielded 80% of the peas that were harvested. And thus was born a theory that has stood the test of time and scrutiny. The Pareto Principle or the 80:20 Rule has proven its validity in a number of other areas:</p> 80% of sales come from 20% of your customers (definitely true in our case) 20% of your products account for 80% of your sales A small percentage of the population generate the largest health care costs Earnings come from 20% of your investments 80% of this blog&#8217;s traffic is to 20% of the postings (actually 33 pages of 180, or 18.3%) <p>We&#8217;ve learned to categorize and sort our defects, problems, expenses by this [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><a href="http://www.amazon.com/Rise-Fall-Elites-Application-Theoretical/dp/0887388728%3FSubscriptionId%3D02E5W5871AJF7PMMMS82%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0887388728"><img class="alignright" src="http://ecx.images-amazon.com/images/I/41cH277fmIL._SL500_.jpg" alt="" width="166" height="250" /></a>In the late 1800s, economist and avid gardener Vilfredo Pareto established that 80% of the land in Italy was owned by 20% of the population. While gardening he later observed that 20% of the pea pods in his garden yielded 80% of the peas that were harvested. And thus was born a theory that has stood the test of time and scrutiny. The Pareto Principle or the 80:20 Rule has proven its validity in a number of other areas:</p>
<ul>
<li>80% of sales come from 20% of your customers (definitely true in our case)</li>
<li>20% of your products account for 80% of your sales</li>
<li>A small percentage of the population generate the largest health care costs</li>
<li>Earnings come from 20% of your investments</li>
<li>80% of this blog&#8217;s traffic is to 20% of the postings (actually 33 pages of 180, or 18.3%)</li>
</ul>
<p>We&#8217;ve learned to categorize and sort our defects, problems, expenses by this 80/20 rule so that we can focus or limited resources, attention, brain power on the &#8216;vital few&#8217;.</p>
<p>But in my experience you can&#8217;t let this thinking allow you to forget about the tail.  Often the greatest opportunities or insights are found are out there in the mix.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/1362/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>EVOP &#8211; Evolutionary Operations</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/309</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/309#comments</comments>
		<pubDate>Sun, 22 Mar 2009 15:13:54 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[EVOP]]></category>
		<category><![CDATA[Evolutionary Operations]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=309</guid>
		<description><![CDATA[<p id="top" /> <p></p> <p>&#160;</p> <p>Evolutionary Operations, first described by George E. P. Box and Norman R. Draper in in their book Evolutionary Operations &#8211; A statistical method for process improvement, New York: John Wiley and Sons, 1969.</p> <p>EVOP is Continuous Improvement + Design of Experiments.</p> <p>Basic idea is to replace the routine&#160; operation of a process by continuous and systematic plan of slight adjustments of the control variables.&#160; The effects of the adjustments are then evaluated just as with DOE.&#160; The process is then shifted in the desired direction of improvement.&#160; In many product and service processes it is impossible or very expensive to do DOE, especially where trials can be disruptive or the process owner would let you have the necessary time, materials, labor to run your experiments.&#160; So rather than running experimental production runs you use actual production by shifting off the base point left, right, up, down all within &#34;spec&#34;.</p> [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />
<p><a title="Evolutionary Operation" href="http://www.amazon.com/Evolutionary-Operation-Statistical-Improvement-Classics/dp/0471255513%3FSubscriptionId%3D1N9AHEAQ2F6SVD97BE02%26tag%3Dleansigmasupp-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0471255513" linkindex="53" set="yes"><img hspace="10" height="250" align="left" width="161" alt="Evolutionary Operation: A Statistical Method for Process Improvement (Wiley Classics Library)" src="http://ecx.images-amazon.com/images/I/41BF6H9W2WL._SL500_.jpg" /></a></p>
<p>&nbsp;</p>
<p>Evolutionary Operations, first described by George E. P. Box and Norman R. Draper in in their book <em>Evolutionary Operations &#8211; A statistical method for process improvement</em>, New York: John Wiley and Sons, 1969.</p>
<p>EVOP is Continuous Improvement + Design of Experiments.</p>
<p>Basic idea is to replace the routine&nbsp; operation of a process by continuous and systematic plan of slight adjustments of the control variables.&nbsp; The effects of the adjustments are then evaluated just as with DOE.&nbsp; The process is then shifted in the desired direction of improvement.&nbsp; In many product and service processes it is impossible or very expensive to do DOE, especially where trials can be disruptive or the process owner would let you have the necessary time, materials, labor to run your experiments.&nbsp; So rather than running experimental production runs you use actual production by shifting off the base point left, right, up, down all within &quot;spec&quot;.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;<span id="more-309"></span></p>
<p>The procedure goes like this:</p>
<ol>
<li>Choose a base point, a place to start, typically the center of the control variables specification ranges.</li>
<li>Evaluate the objective function at the base point and determine a set of regularly spaced points around the base point.&nbsp; For 2 variables, form a square with the base point at the center.&nbsp; For 3 variables, form a cube, etc..&nbsp; That is, conduct a DOE or Taguchi using the live process.</li>
<li>Then, shift the process center to the point that has the largest value of the objective function.</li>
<li>Use this point as the new base point.</li>
<li>Repeat steps (2) and (3) until no further improvement occurs.</li>
</ol>
<p>EVOP can be slow, months instead of weeks, so you need some patience and structure.&nbsp; For organizations that embrace the method it becomes a basic part of the continuous improvement scientific management culture.</p>
<input type="image" height="300" width="421" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/EVOP1%282%29.png" alt="Evolutionary Operations" longdesc="undefined" />
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/309/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fixed Repeating Schedule &#8211; Product Family Turnover Rate</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/281</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/281#comments</comments>
		<pubDate>Wed, 11 Mar 2009 17:08:17 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Logistics]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Fixed Repeating Schedule]]></category>
		<category><![CDATA[Product Family Turnover Rate]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=281</guid>
		<description><![CDATA[<p id="top" />Here&#8217;s another example for &#8220;sizing the wheel&#8221; for a mixed model fixed repeating schedule.</p> <p>Given:</p> Changeover Time = 100 minutes Available Production Time = 2 shifts * 7 hrs/shift * 60 min/hr = 840 min/day <p>and</p> Product Daily Demand (pcs) Cycle Time (min.) Load (min.) A 80 5 400 B 40 4 160 C 20 4 80 D 10 6 60 700 <p>Now some math:</p> Total Load = 700 min. Time Available for Changeovers = 840 min/day &#8211; 700 min/day = 140 min/day Changeover Time for group = 100 min * 4 products = 400 min/family Changeovers per day = 140 min/day / 400 min/family = 0.35 group/day or a Replenishment Time of 2.85 days/family <p>So the fixed repeating wheel will turn once in 2.86 days.  Production run sizes as follows:</p> Product Daily Demand * Replen Time Cycle Time (min) Load (min) A 229 5 1145 B 114 4 456 C 57 [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />Here&#8217;s another example for &#8220;sizing the wheel&#8221; for a mixed model <a href="http://www.resourcesystemsconsulting.com/blog/archives/115">fixed repeating schedule</a>.</p>
<p>Given:</p>
<ol>
<li>Changeover Time = 100 minutes</li>
<li>Available Production Time = 2 shifts * 7 hrs/shift * 60 min/hr = 840 min/day</li>
</ol>
<p>and</p>
<table style="width: 331px; height: 124px;" border="1">
<tbody>
<tr align="center" valign="middle">
<td>Product</td>
<td>Daily Demand (pcs)</td>
<td>Cycle Time (min.)</td>
<td>Load (min.)</td>
</tr>
<tr align="center" valign="middle">
<td>A</td>
<td>80</td>
<td>5</td>
<td>400</td>
</tr>
<tr align="center" valign="middle">
<td>B</td>
<td>40</td>
<td>4</td>
<td>160</td>
</tr>
<tr align="center" valign="middle">
<td>C</td>
<td>20</td>
<td>4</td>
<td>80</td>
</tr>
<tr align="center" valign="middle">
<td>D</td>
<td>10</td>
<td>6</td>
<td>60</td>
</tr>
<tr align="center" valign="middle">
<td></td>
<td></td>
<td></td>
<td>700</td>
</tr>
</tbody>
</table>
<p>Now some math:</p>
<ol>
<li>Total Load = 700 min.</li>
<li>Time Available for Changeovers = 840 min/day &#8211; 700 min/day = 140 min/day</li>
<li>Changeover Time for group = 100 min * 4 products = 400 min/family</li>
<li>Changeovers per day = 140 min/day / 400 min/family = 0.35 group/day or a Replenishment Time of 2.85 days/family</li>
</ol>
<p>So the fixed repeating wheel will turn once in 2.86 days.  Production run sizes as follows:</p>
<table style="width: 279px; height: 159px;" border="1" cellspacing="1" cellpadding="1">
<tbody>
<tr align="center" valign="middle">
<td>Product</td>
<td>Daily Demand * Replen Time</td>
<td>Cycle Time (min)</td>
<td>Load (min)</td>
</tr>
<tr align="center" valign="middle">
<td style="text-align: center;">A</td>
<td>229</td>
<td>5</td>
<td>1145</td>
</tr>
<tr align="center" valign="middle">
<td style="text-align: center;">B</td>
<td>114</td>
<td>4</td>
<td>456</td>
</tr>
<tr align="center" valign="middle">
<td style="text-align: center;">C</td>
<td>57</td>
<td>4</td>
<td>228</td>
</tr>
<tr align="center" valign="middle">
<td style="text-align: center;">D</td>
<td>29</td>
<td>6</td>
<td>174</td>
</tr>
<tr align="center" valign="middle">
<td></td>
<td></td>
<td></td>
<td>2003</td>
</tr>
</tbody>
</table>
<p>Plus 4 changeovers of 100 min each = 2403 min = 2.86 days.</p>
<p>When it comes time to run product A, run 2.86 days worth. Got it?</p>
<p>Would be nice if we could run just one piece.  But until we can make the 100 minute changeover go away we&#8217;re stuck running a batch of some size.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/281/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Process Improvement in a Down Economy</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/199</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/199#comments</comments>
		<pubDate>Sat, 31 Jan 2009 22:16:44 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Economy]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Process Improvement]]></category>
		<category><![CDATA[Profitability]]></category>
		<category><![CDATA[Six Sigma]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=199</guid>
		<description><![CDATA[<p id="top" /></p> <p>Many business leaders fail to see the opportunities that an economic downturn provides.  To take advantage of opportunities you first need to make a rapid assessment of your vulnerabilities and then move quickly to minimize them.  Advantage can be gained by using process improvement tools to increase profitability and competitiveness:</p> Drive out waste through Lean Sigma operations Tools: value stream mapping, line balancing, kaizen to reduce direct and overhead labor Customer Collaboration Tools: customer segmentation, goal alignment, cycle time reduction, product line rationalization Supplier Optimization Tools: supplier &#38; material consolidation, lead time reduction, product design-to-cost Accelerate cash flow and aggressively manage working capital Tools: inventory reduction, excess/slow moving/obsolete inventory analysis, safety stock tuning, cycle time reduction to reduce WIP, receivables and payables management Increase Capacity Tools: overall equipment effectiveness, theory of constraints, quick changeover, product family turnover analysis Product Redesign Tools: component substitution, design for six sigma, design for manufacturability, value engineering [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><img src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/ready-set-go.jpg" alt="" width="300" height="213" /></p>
<p>Many business leaders fail to see the opportunities that an economic downturn provides.  To take advantage of opportunities you first need to make a rapid assessment of your vulnerabilities and then move quickly to minimize them.  Advantage can be gained by using process improvement tools to increase profitability and competitiveness:</p>
<ol>
<li>Drive out waste through Lean Sigma operations<br />
Tools: value stream mapping, line balancing, kaizen to reduce direct and overhead labor</li>
<li>Customer Collaboration<br />
Tools: customer segmentation, goal alignment, cycle time reduction, product line rationalization</li>
<li>Supplier Optimization<br />
Tools: supplier &amp; material consolidation, lead time reduction, product design-to-cost</li>
<li>Accelerate cash flow and aggressively manage working capital<br />
Tools: inventory reduction, excess/slow moving/obsolete inventory analysis, safety stock tuning, cycle time reduction to reduce WIP, receivables and payables management</li>
<li>Increase Capacity<br />
Tools: overall equipment effectiveness, theory of constraints, quick changeover, product family turnover analysis</li>
<li>Product Redesign<br />
Tools: component substitution, design for six sigma, design for manufacturability, value engineering</li>
</ol>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/199/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Gauss</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/172</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/172#comments</comments>
		<pubDate>Tue, 30 Dec 2008 21:12:13 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Gauss]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=172</guid>
		<description><![CDATA[<p id="top" /> <p>&#160;</p> <p> Johann Carl Friedrich Gauss (1777-1855)&#160; seen here on a German 10 Deutsche Mark banknote was a mathematician, astronomer, scientist noted for least squares, the normal distribution, and number theory.&#160; Also known as the Gaussian distribution, the normal distribution is defined by the mean (&#34;average&#34;, &#956;) and variance (standard deviation squared, &#963;2). The standard normal distribution is the normal distribution with a mean of zero and a variance of one.&#160; Common applications include process modeling, queuing theory, safety stock and service level calculations, as was as statistical process control.</p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> <p>&#160;</p> ]]></description>
			<content:encoded><![CDATA[<p id="top" />
<p>&nbsp;</p>
<p><img hspace="10" height="267" align="left" width="400" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/DSCF0668.JPG" alt="" /> Johann Carl Friedrich Gauss (1777-1855)&nbsp; seen here on a German 10 Deutsche Mark banknote was a mathematician, astronomer, scientist noted for least squares, the <a href="http://en.wikipedia.org/wiki/Normal_distribution">normal distribution</a>, and number theory.&nbsp; Also known as the Gaussian distribution, the normal distribution is defined by the mean (&quot;average&quot;, <i>&mu;</i>) and variance (standard deviation squared, <i>&sigma;</i><sup>2</sup>). The <b>standard normal distribution</b> is the normal distribution with a mean of zero and a variance of one.&nbsp; Common applications include process modeling, queuing theory, safety stock and service level calculations, as was as statistical process control.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/172/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Rules of On-error Training</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/121</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/121#comments</comments>
		<pubDate>Sun, 06 Jul 2008 20:08:46 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Logistics]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Training]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=121</guid>
		<description><![CDATA[<p id="top" />&#160;</p> <p>1. Ownership Rule &#8211; the person who first detects the problem is responsible for finding the root cause of the problem.</p> <p>2. Quickly Rule &#8211; the problem must be dealt with and solved within 30 minutes, not put on a list or in a report for action at another time.</p> <p>3. Actually Rule &#8211; if possible play back or recreate the process that occurred before the defect.</p> <p>4. Support Rule &#8211; the person who detects the problem has primary responsibility for solving it, but supervisor and fellow workers can stop working and lend problem solving support.</p> <p>5. Shut Up Rule &#8211; the discoverer is expected to solve the problem and be allowed time to discuss the problem and attempt to solve it.  Others can help but the supervisor or manager must keep quiet and give the person a chance to solve the problem.</p> <p>From Dr Ryuji Fukuda</p> <p>&#160;</p> [...]]]></description>
			<content:encoded><![CDATA[<p id="top" />&nbsp;</p>
<p><img src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/oops.jpg" alt="" width="250" height="207" align="left" hspace="10" />1. <strong>Ownership</strong> Rule &#8211; the person who first detects the problem is responsible for finding the root cause of the problem.</p>
<p>2. <strong>Quickly</strong> Rule &#8211; the problem must be dealt with and solved within 30 minutes, not put on a list or in a report for action at another time.</p>
<p>3. <strong>Actually</strong> Rule &#8211; if possible play back or recreate the process that occurred before the defect.</p>
<p>4. <strong>Support</strong> Rule &#8211; the person who detects the problem has primary responsibility for solving it, but supervisor and fellow workers can stop working and lend problem solving support.</p>
<p>5. <strong>Shut Up</strong> Rule &#8211; the discoverer is expected to solve the problem and be allowed time to discuss the problem and attempt to solve it.  Others can help but the supervisor or manager must keep quiet and give the person a chance to solve the problem.</p>
<p>From <a href="http://daviesconsultinginc.com/ryuji-fukuda.php" target="_blank">Dr Ryuji Fukuda</a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/121/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PowerPoint and other miscommunications</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/106</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/106#comments</comments>
		<pubDate>Sun, 05 Aug 2007 22:52:04 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Consulting]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Sigma]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/archives/106</guid>
		<description><![CDATA[<p id="top" />Recently read Edward R. Tufte&#8217;s The Cognitive Style of PowerPoint: Pitching Out Corrupts Within and initially dismissed his thesis as troglodyte.  Now sensitized, I&#8217;ve been watching for evidence of PowerPoint Abuse.  Found an unfortunate example with two parallel teams during a strategic capital equipment review.  Both teams were given the same mission and access to data: scrutinize the new capital equipment plans, challenge assumptions, collect new data and define cost reduction and risk mitigation plans.  Both teams were staffed with bright industrial, process, manufacturing, quality engineers who pulled on other subject matter experts in their data gathering.  Leadership effectively facilitated and guided both teams through the current state to future state diagnostic journey.  Significant productivity, utilization, overall equipment effectiveness opportunities were identified and tested over the two week full-time exercise.</p> <p>One team plastered their &#8220;war room&#8221; with all of their data, continuously rearranging their wall, retelling their story.  The other team began [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><img style="float: left; margin-left: 10px; margin-right: 10px;" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/CognitivePowerPoint.gif" alt="" width="484" height="597" />Recently read Edward R. Tufte&#8217;s <a href="https://www.edwardtufte.com/tufte/powerpoint"><em>The Cognitive Style of PowerPoint: Pitching Out Corrupts Within</em> </a>and initially dismissed his thesis as troglodyte.  Now sensitized, I&#8217;ve been watching for evidence of PowerPoint Abuse.  Found an unfortunate example with two parallel teams during a strategic capital equipment review.  Both teams were given the same mission and access to data: scrutinize the new capital equipment plans, challenge assumptions, collect new data and define cost reduction and risk mitigation plans.  Both teams were staffed with bright industrial, process, manufacturing, quality engineers who pulled on other subject matter experts in their data gathering.  Leadership effectively facilitated and guided both teams through the current state to future state diagnostic journey.  Significant productivity, utilization, overall equipment effectiveness opportunities were identified and tested over the two week full-time exercise.</p>
<p>One team plastered their &#8220;war room&#8221; with all of their data, continuously rearranging their wall, retelling their story.  The other team began typing their findings and abandoned their wall after a couple of days.  Individual leaders would visit with the teams randomly throughout the study period but never &#8220;walked the wall&#8221;, instead expected PowerPoint slides for the daily out briefs.  Attempts were made to reconcile the two teams leading up to a joint presentation to senior management.</p>
<p>Bottom line &#8211; what&#8217;s the new equipment price tag to support the new 5 year strategic operating plan?</p>
<p>One team argued for showing both the prior and new estimates as side by side stacked bar charts, the other team just a table listing the $9.6 million delta.</p>
<p>Despite coaching challenges the delta display won out.  Too bad because the Executive VP had remembered &#8220;the number&#8221; and misinterpreted the table.  Had the first team taken the EVP on a tour of their wall the message would have been clearer.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/106/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Safety Stock Calculations</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/90</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/90#comments</comments>
		<pubDate>Mon, 29 Jan 2007 15:58:19 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lean Sigma]]></category>
		<category><![CDATA[Logistics]]></category>
		<category><![CDATA[Sigma]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Safety Stock]]></category>
		<category><![CDATA[Safety Stock Calculation]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/archives/90</guid>
		<description><![CDATA[<p id="top" />When I first learned inventory planning the math was rather simple.  On top of the cycle stock (expected demand during lead time) I would add a percentage or a number of days (or more likely weeks).  If the lead time was 2 weeks I  might carry 3 or 4 weeks.  I soon learned that demand for some inventory items is more volatile than for others, and some suppliers less reliable than others.  I&#8217;d rather have too much then not enough, and I&#8217;d never gotten in trouble for having a little too much.</p> <p>So since all items and situations are different I started using some statistics; (average demand * lead time) + (one sided Z factor * demand standard deviation) for the target inventory level; a little better approach.</p> <p>Here&#8217;s another formula from Inventory Management Review;</p> <p>Safety Stock: {Z * SQRT (Avg. Lead Time * Standard Deviation of Demand ^2 + Avg. Demand [...]]]></description>
			<content:encoded><![CDATA[<p id="top" /><img src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/SS.png" alt="" hspace="10" width="518" height="232" align="left" />When I first learned inventory planning the math was rather simple.  On top of the cycle stock (expected demand during lead time) I would add a percentage or a number of days (or more likely weeks).  If the lead time was 2 weeks I  might carry 3 or 4 weeks.  I soon learned that demand for some inventory items is more volatile than for others, and some suppliers less reliable than others.  I&#8217;d rather have too much then not enough, and I&#8217;d never gotten in trouble for having a little too much.</p>
<p>So since all items and situations are different I started using some statistics; <strong><span style="color: #339966;">(average demand * lead time) + (<a href="http://www.sjsu.edu/faculty/gerstman/EpiInfo/z-table.htm"><strong><span style="color: #339966;">one sided Z factor</span></strong></a> * demand standard deviation) </span></strong>for the target inventory level; a little better approach.</p>
<p>Here&#8217;s another formula from <a href="http://www.inventorymanagementreview.org/2005/06/safety_stock.html">Inventory Management Review</a>;</p>
<p>Safety Stock:<br />
<strong><span style="color: #339966;">{Z * SQRT (Avg. Lead Time * Standard Deviation of Demand ^2 + Avg. Demand ^2 * Standard Deviation of Lead Time ^2}</span></strong>.<br />
(note ^2 means &#8216;square&#8217;)<br />
Reorder Point:<br />
<strong><span style="color: #339966;">Average Lead Time*Average Demand + <em>Z*SQRT(Avg. Lead Time * Standard Deviation of Demand^2 + Avg. Demand^2 * Standard Deviation of Lead Time^2)</em></span><em> </em></strong><em>.</em></p>
<p>&nbsp;</p>
<p>Over at <a href="http://www.quickmba.com/ops/inventory-management/">QuickMBA</a> ; To calculate the safety stock, first calculate the standard loss function, designated as L(z). This function is dependent on the values of the desired fill rate  <em>f</em>,  the demand  μ  and its standard deviation  σ ,  the time between orders  <em>p</em>,  and the replenishment lead time <em>l</em> : L(z)  =  ( 1 &#8211; <em>f</em> ) <em>µ p</em> / <em>σ</em> ( <em>p </em>+ <em>l</em> )<sup>1/2</sup>.  Once L(z) is known, z can be found in a look-up table and the safety stock can be calculated by:</p>
<p><strong><span style="color: #339966;">Safety Stock  =  <em>z σ</em> ( <em>p</em> + <em>l </em>)<sup>1/2</sup></span></strong></p>
<p>Here&#8217;s a new one recently published by <a href="mailto:kent.linford@moen.com">Kent Linford</a> in the <a href="http://www.apics.org/Resources/Magazine" class="broken_link">APICS Magazine</a> Nov/Dec 2006.  <span id="body"><strong><span class="subhome" style="color: #009966;"><br />
SS = √ [( σFE)<sup>2</sup> x (LTI/FI)<sup>beta</sup> + ( σLT)<sup>2</sup> x D<sup>2</sup>] x Z x (FI/OCI)<sup>beta</sup></span></strong></span></p>
<p>Where:<br />
SS = safety stock<br />
FE = forecast error<br />
LT = lead time interval<br />
FI = forecast interval (pick a beta between 0.5 and 0.7)<br />
D = average demand during lead time<br />
Z = normal distribution service factor based on desired service level<br />
OCI = order cycle interval</p>
<p>Dave Piasecki at <a href="http://www.inventoryops.com/safety_stock.htm">InventoryOps.com</a> uses;<br />
<strong><span style="color: #339966;">safety stock = <em>(standard deviation)*(service factor)*(lead-time factor)*(order cycle factor)*(forecast-to-mean-demand factor)</em></span></strong></p>
<p><a href="http://www.effectiveinventory.com/article29.html">Jon Schreibfeder</a> has another approach.</p>
<p>And so too does <a title="Calculate safety stock" href="http://www.lokad.com/calculate-safety-stocks-with-sales-forecasting.ashx">Joannès Vermorel</a>.</p>
<p>&nbsp;</p>
<p>Any questions? Got any other versions?  What formula do you use?</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/90/feed</wfw:commentRss>
		<slash:comments>110</slash:comments>
		</item>
	</channel>
</rss>

