<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><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" 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>
	<pubDate>Thu, 27 Nov 2008 03:54:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/resourcesystemsconsulting/ZiAJ" type="application/rss+xml" /><item>
		<title>Leader’s Job</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/160</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/160#comments</comments>
		<pubDate>Thu, 27 Nov 2008 03:49:59 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Consulting]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=160</guid>
		<description><![CDATA[&#160;

The leader&#8217;s job is to drive the bus;


Get the right people on the bus
Get the wrong people off the bus
Make sure the right people are in the right seats
Know where the bus is going
Know when to look in the mirror
Be committed to getting the bus to its destination
Provide resources to ensure trip&#8217;s success

]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p><img height="150" width="323" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/Bus.jpg" alt="" /></p>
<p><span>The leader&rsquo;s job is to drive the bus;<br />
</span></p>
<ul>
<li>Get the right people on the bus</li>
<li>Get the wrong people off the bus</li>
<li>Make sure the right people are in the right seats</li>
<li>Know where the bus is going</li>
<li>Know when to look in the mirror</li>
<li>Be committed to getting the bus to its destination</li>
<li>Provide resources to ensure trip&rsquo;s success</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/160/feed</wfw:commentRss>
		</item>
		<item>
		<title>Inventory Drivers</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/124</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/124#comments</comments>
		<pubDate>Sat, 30 Aug 2008 17:06:44 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Supply Chain]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=124</guid>
		<description><![CDATA[&#160;
&#8226; Supply Chain Organization: Is there an integrated approach to the supply chain and inventory decisions, or functional silos? The less integrated, the more inventory problems (shortages or overages) are likely to occur.
&#8226; Supply Chain Network Design: The greater the number of stocking points, all things being equal, the higher the level of inventory. The [...]]]></description>
			<content:encoded><![CDATA[<p>&nbsp;<img height="225" width="300" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/warehouse 4.jpg" class="i_left" alt="" /></p>
<p>&bull; <strong>Supply Chain Organization</strong>: Is there an integrated approach to the supply chain and inventory decisions, or functional silos? The less integrated, the more inventory problems (shortages or overages) are likely to occur.<br />
&bull; <strong>Supply Chain Network Design</strong>: The greater the number of stocking points, all things being equal, the higher the level of inventory. The longer the supply chain (e.g., goods produced offshore), the higher the level of inventory.<br />
&bull; <strong>Customer Service Policies</strong>: A company&rsquo;s strategies and goals related to customer service, both generally and at an A, B, C category level, will greatly impact inventories.<br />
&bull; <strong>Safety Stock Policies</strong>: Relatedly, how aggressive or not a company wants to be with safety levels, and how frequently a company revisits safety stock assumptions and SKU-level targets, are key variables.<br />
&bull; <strong>Degrees of Freedom for Inventory Decisions</strong>: The more individuals that have the ability to add inventory into the supply chain, the higher the levels are likely to be.<br />
&bull; <strong>Management of Trade-Offs</strong>: Company specific decisions about the traditional inventory, transportation, and unit cost trade-offs. The lowest total cost will usually have higher inventories than the lowest inventory cost option.<br />
&bull; <strong>Forecast Accuracy</strong>: The greater the level of forecast inaccuracy, generally the lower levels of total inventory.<br />
&bull; <strong>Demand Variability</strong>: Highly dynamic demand in general leads to greater inventory levels to maintain customer service targets.<br />
&bull; <strong>Supply Variability</strong>: The more variable the supply, the more buffer inventory that needs to be held. Obviously, this is a potential issue with offshoring. In general, variability of supply is worse than a long supply chain in terms of the impact on inventory.<br />
&bull; <strong>SKU Counts</strong>: The higher the number of SKUs, the higher the level of inventory will generally be for the same dollars in sales.<br />
&bull; <strong>Total Cycle Times</strong>: The faster the cycle times, the lower levels of inventory required. Procter &amp; Gamble, for instance, is trying to make its factory more flexible, with much quicker set-up times, in part to reduce inventory levels.<br />
&bull; <strong>Level of Supply Chain Collaboration</strong>: The more integrated a company is with suppliers and customers to jointly manage inventories, the lower inventories are likely to be.<br />
&bull; <strong>Vendor Relationships</strong>: Companies that have supplier-owned inventory programs, or just-in-time supplier logistics centers, will have lower total inventories on the raw materials/components side.<br />
&bull; <strong>Level of Supply Chain Visibility</strong>: The better visibility a company has to its network-wide inventory, the lower its total inventory should be. This is part of the promised potential of RFID.<br />
&bull; <strong>Inventory Accuracy</strong>: The more accurate a company maintains its levels of raw materials and finished goods inventories, the lower the level of inventory, as planners have better trust in the numbers upon which they are planning.<br />
&bull;<strong> Order Patterns (Seasonality)</strong>: Less consistent demand patterns can lead to higher inventory levels. As an extreme example, some wrapping paper manufacturers build inventory all year to ship only in the couple of months before Christmas.<br />
&bull; <strong>Metrics</strong>: What gets rewarded? Metrics drive behavior, and it is no different with inventory. Have a plant that is driven primarily by yield and cost per unit metrics? Expect more inventory, for example.</p>
<p>* from <em>Supply Chain Digest Letter</em> July 2008</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/124/feed</wfw:commentRss>
		</item>
		<item>
		<title>Gemba Walk</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/122</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/122#comments</comments>
		<pubDate>Sun, 06 Jul 2008 21:20:08 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Definitions]]></category>

		<category><![CDATA[Lean]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=122</guid>
		<description><![CDATA[&#160;
1. Select a theme for each walk
2. Question the supervisors
3. Listen (and learn) attentively
4. Share what you learn as you walk
5. Write a short memo on what you learned and post it for all to see
6. Follow up to see that progress is being made
]]></description>
			<content:encoded><![CDATA[<p>&nbsp;<img height="194" width="125" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/Walk.jpg" class="i_right" alt="" /></p>
<p>1. Select a theme for each walk</p>
<p>2. Question the supervisors</p>
<p>3. Listen (and learn) attentively</p>
<p>4. Share what you learn as you walk</p>
<p>5. Write a short memo on what you learned and post it for all to see</p>
<p>6. Follow up to see that progress is being made</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/122/feed</wfw:commentRss>
		</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 21: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>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=121</guid>
		<description><![CDATA[&#160;
1. Ownership Rule - the person who first detects the problem is responsible for finding the root cause of the problem.
2. Quickly Rule - 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.
3. Actually Rule - if possible play [...]]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p><img height="207" width="250" alt="" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/oops.jpg" class="i_right" />1. Ownership Rule - the person who first detects the problem is responsible for finding the root cause of the problem.</p>
<p>2. Quickly Rule - 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 - if possible play back or recreate the process that occurred before the defect.</p>
<p>4. Support Rule - 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 - the discoverer is expected to solve the problem and be allowed time to dicsuss the problem and attempt to solve it.&nbsp; Others can help but the supervisor or manager must keep quiet and give the person a chance to solve the problem.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/121/feed</wfw:commentRss>
		</item>
		<item>
		<title>Gemba</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/120</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/120#comments</comments>
		<pubDate>Sat, 05 Jul 2008 13:14:45 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Definitions]]></category>

		<category><![CDATA[Lean]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=120</guid>
		<description><![CDATA[&#160;
The King
Looking out
Onto the Land
In the Hot Sun
Where the Pigs are
&#160;
&#160;
&#160;
&#160;
Gemba - where to go to understand: not in the office or a conference room, but in the real place.
]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p><img width="455" height="207" align="left" alt="Gemba" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/Gemba.jpg" />The King</p>
<p>Looking out</p>
<p>Onto the Land</p>
<p>In the Hot Sun</p>
<p>Where the Pigs are</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Gemba - where to go to understand: not in the office or a conference room, but in the real place.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/120/feed</wfw:commentRss>
		</item>
		<item>
		<title>Toyota Vocabulary</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/119</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/119#comments</comments>
		<pubDate>Thu, 03 Jul 2008 22:51:35 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Definitions]]></category>

		<category><![CDATA[Lean]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=119</guid>
		<description><![CDATA[Everyone working together in a large room without partitions: Obeya.
Posting project team information on the wall of a dedicated &#8217;situation room&#8217;: Mieruka: visualization
Personal Magnetism: Jinbo.&#160; When Toyota evaluates their supervisors and managers they emphasize process performance, learning, and teaching over results, goals, and objectives.
Adhesive Strength: Nebari Tsuyosa.&#160; Persistence and resilience are Toyota&#8217;s measure of manager [...]]]></description>
			<content:encoded><![CDATA[<p><img align="left" style="width: 302px; height: 300px;" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/Toyota.png" alt="" />Everyone working together in a large room without partitions: <span style="font-family: Tahoma;"><em>Obeya</em></span>.</p>
<p>Posting project team information on the wall of a dedicated &#8217;situation room&#8217;: <span style="font-family: Tahoma;"><em>Mieruka</em></span>: visualization</p>
<p>Personal Magnetism: <span style="font-family: Tahoma;"><em>Jinbo</em></span>.&nbsp; When Toyota evaluates their supervisors and managers they emphasize process performance, learning, and teaching over results, goals, and objectives.</p>
<p>Adhesive Strength: <span style="font-family: Tahoma;"><em>Nebari Tsuyosa</em></span>.&nbsp; Persistence and resilience are Toyota&#8217;s measure of manager performance.</p>
<p>Drinks with fellow workers: <span style="font-family: Tahoma;"><em>Nomikai</em></span><em>.</em> Sharing information, learning by visiting.</p>
<p>&quot;Let&#8217;s<em> </em><span style="font-family: Tahoma;"><em>Yokoten</em></span>&quot;: communication is viral, literally: unfold or open out sideways.</p>
<p>Committees: <span style="font-family: Tahoma;"><em>Iinkai</em></span>; every Toyota employee belongs to several.</p>
<p>Self organized study groups: <span style="font-family: Tahoma;"><em>Jishuken</em></span>.</p>
<p>Consensus building; shopping an idea around: <em>Nemawashi</em>.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/119/feed</wfw:commentRss>
		</item>
		<item>
		<title>Five Frogs</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/118</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/118#comments</comments>
		<pubDate>Wed, 05 Mar 2008 13:39:36 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Consulting]]></category>

		<category><![CDATA[Reviews]]></category>

		<category><![CDATA[Supply Chain]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/archives/118</guid>
		<description><![CDATA[
Five Frogs are sitting on a log.&#160; Four decide to hop off.&#160; How many frogs are left?*
It doesn&#8217;t take much for good intentions to end up in disaster.&#160; It&#8217;s been my recent fate to be involved in two failed mergers, one a postmortem, the next a trainwreck-in-progress.&#160; Integrating distribution, logistics, information, management and financial systems; [...]]]></description>
			<content:encoded><![CDATA[<p><img align="left" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/image/FiveFrog.gif" style="margin-right: 10px;" alt="" /></p>
<h3>Five Frogs are sitting on a log.&nbsp; Four decide to hop off.&nbsp; How many frogs are left?*</h3>
<p>It doesn&#8217;t take much for good intentions to end up in disaster.&nbsp; It&#8217;s been my recent fate to be involved in two failed mergers, one a postmortem, the next a trainwreck-in-progress.&nbsp; Integrating distribution, logistics, information, management and financial systems; oh, and the people is a tough tough thing.&nbsp; The deal makers fall in love with the potential synergies and then all too often with out a plan or a process hope that magic will happen once the deal is done.</p>
<p>&quot;Five Frogs on a Log: A CEO&#8217;s Field Guide to Accelerating the Transition in Mergers, Acquisitions, and Gut Wrenching Change&rdquo; by Mark Feldman and Michael Spratt is a great guide, and not just for mergers and CEO&#8217;s but for any organizational change event and those who are caught up in the maelstrom of clashing cultures.&nbsp; A little light on methodology, this book will let you know what to expect from the merger/acquisition, encourage focusing on execution, the importance of communicating even when in the fog, it&#8217;s a virtual project plan for you and your leadership team.&nbsp;</p>
<p>&nbsp;</p>
<p>Read it!&nbsp; Hopefully before, not after the chaos starts.</p>
<p>&nbsp;</p>
<p>&nbsp;&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>*Five. Because there&#8217;s a difference between deciding and doing. &quot;Execution,&quot; the authors tell us, &quot;is always more difficult than it seems.&quot;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/118/feed</wfw:commentRss>
		</item>
		<item>
		<title>Refine, Simplify, and Strengthen</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/117</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/117#comments</comments>
		<pubDate>Thu, 10 Jan 2008 18:29:14 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Lean]]></category>

		<category><![CDATA[improvement process]]></category>

		<category><![CDATA[transformation]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/archives/117</guid>
		<description><![CDATA[
Why is it that most lean and six sigma transformations are so complicated?&#160; All too often organizational transformations are loaded with tons of non value-added waste: status reports and senior management presentations that serve little or no purpose,&#160; training provided on tools that can&#8217;t or won&#8217;t be applied, unsustained and unsustainable changes made, flying people [...]]]></description>
			<content:encoded><![CDATA[<p><img width="207" height="200" class="i_left" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/image/ABC Blocks.png" alt="ABC's" /></p>
<p>Why is it that most lean and six sigma transformations are so complicated?&nbsp; All too often organizational transformations are loaded with tons of non value-added waste: status reports and senior management presentations that serve little or no purpose,&nbsp; training provided on tools that can&#8217;t or won&#8217;t be applied, unsustained and unsustainable changes made, flying people around the country or world, waiting for the right time or resources, long lists of assignments, window dressing.&nbsp; Applying seven wastes thinking to lean might make transformations a little easier.</p>
<p>Resource + Creativity + Freedom and a Process = Lean Sigma Success</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/117/feed</wfw:commentRss>
		</item>
		<item>
		<title>oops!</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/116</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/116#comments</comments>
		<pubDate>Wed, 02 Jan 2008 20:35:53 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Supply Chain]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/archives/116</guid>
		<description><![CDATA[


]]></description>
			<content:encoded><![CDATA[<p>
<a href="http://xmb.stuffucanuse.com/xmb/viewthread.php?action=attachment&amp;tid=4175&amp;pid=12213"><img width="690" height="473" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/image/container-ship.jpg" alt="" /><br />
</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/116/feed</wfw:commentRss>
		</item>
		<item>
		<title>Fixed Repeating Schedule</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/114</link>
		<comments>http://www.resourcesystemsconsulting.com/blog/archives/114#comments</comments>
		<pubDate>Thu, 27 Dec 2007 18:27:03 +0000</pubDate>
		<dc:creator>Lawrence Loucka</dc:creator>
		
		<category><![CDATA[Definitions]]></category>

		<category><![CDATA[Lean]]></category>

		<category><![CDATA[Fixed Repeating Schedule]]></category>

		<category><![CDATA[FRS]]></category>

		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/archives/114</guid>
		<description><![CDATA[Fixed Repeating Schedule (FRS) also known as Every product Every Interval (EPE) is a production schedule which is &#8216;unchanging&#8217; and repeated perhaps daily or over a period of a few weeks or months before being reset.&#160; If it can be implemented then economies of repetition start to become evident and suppliers and customers can be [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/image/Carousel at Six Flags Atlanta.jpg"><img height="250" width="333" alt="Carousel at Six Flags Atlanta" class="i_left" src="http://www.resourcesystemsconsulting.com/blog/wp-content/uploads/image/Carousel at Six Flags Atlanta.jpg" /></a>Fixed Repeating Schedule (FRS) also known as Every product Every Interval (EPE) is a production schedule which is &#8216;unchanging&#8217; and repeated perhaps daily or over a period of a few weeks or months before being reset.&nbsp; If it can be implemented then economies of repetition start to become evident and suppliers and customers can be assured in their own activity scheduling. What impedes FRS implementation is the uncertainty of demand and supply. Therefore while the scheduling becomes simpler; the activities necessary to make the FRS possible become more complex. Thus the planning to move to FRS raises issues which if managed correctly will reduce complexity overall and improve customer service.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<ol>
<li>
<p>Map the process and determine feasibility by evaluating <a href="http://www.resourcesystemsconsulting.com/blog/archives/110">demand linearity</a></p>
</li>
<li>
<p>Select work group, line, or cell and determine available time, cycle time, change over time</p>
</li>
<li>
<p>Calculate the <a href="http://www.resourcesystemsconsulting.com/blog/archives/115">Product Family Turnover Rate</a> (PFTR) or otherwise known as the EPE Interval</p>
</li>
<li>
<p>Use the PFTR to determine production run sizes for each product</p>
</li>
<li>
<p>Determine input and output buffer sizes</p>
</li>
<li>
<p>Simulate either with desktop role modeling, spreadsheet, or simulation software</p>
</li>
<li>
<p>Establish Kanban controls</p>
</li>
<li>
<p>Setup the Heijunka</p>
</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.resourcesystemsconsulting.com/blog/archives/114/feed</wfw:commentRss>
		</item>
	</channel>
</rss>
