<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Just in Time Just Isn’t</title>
	<atom:link href="http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/</link>
	<description>Resources and Commentary for Lean Manufacturers</description>
	<lastBuildDate>Wed, 23 Nov 2011 13:23:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: The fastest way to reduce on-hand inventory balances is to ship it &#124; Tim Lovelock</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-728</link>
		<dc:creator>The fastest way to reduce on-hand inventory balances is to ship it &#124; Tim Lovelock</dc:creator>
		<pubDate>Sun, 22 Aug 2010 16:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-728</guid>
		<description>[...] @chrischip: Just in Time Just Isn’t &#8230;But don’t pull your hair out over inventory. Your customers won’t wait for you to ramp [...]</description>
		<content:encoded><![CDATA[<p>[...] @chrischip: Just in Time Just Isn’t &#8230;But don’t pull your hair out over inventory. Your customers won’t wait for you to ramp [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Earley</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-721</link>
		<dc:creator>Tony Earley</dc:creator>
		<pubDate>Sun, 31 Jan 2010 15:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-721</guid>
		<description>Wow, talk about going against some of the major principles!!!! I am new to this blogging lark and have just started my own blog, &lt;a href=&quot;http://howtoimplementleanmanufacturing.blogspot.com/&quot; rel=&quot;nofollow&quot;&gt; how to implement lean manufacturing &lt;/a&gt;. I hope I can come up with a post like this to get a reaction like this deserves!
Inventory hides all the other problems in your system - GET RID OF INVENTORY!!!
I have been into so many companies that have managed to implement JIT even with masses of variants.. I worked in a company with some 15,000 finished part numbers, all produced and supplied JIT.
If you can&#039;t reduce your inventory you just are not thinking hard enough!!!!
You are just giving up!!!!!!!!!</description>
		<content:encoded><![CDATA[<p>Wow, talk about going against some of the major principles!!!! I am new to this blogging lark and have just started my own blog, <a href="http://howtoimplementleanmanufacturing.blogspot.com/" rel="nofollow"> how to implement lean manufacturing </a>. I hope I can come up with a post like this to get a reaction like this deserves!<br />
Inventory hides all the other problems in your system &#8211; GET RID OF INVENTORY!!!<br />
I have been into so many companies that have managed to implement JIT even with masses of variants.. I worked in a company with some 15,000 finished part numbers, all produced and supplied JIT.<br />
If you can&#8217;t reduce your inventory you just are not thinking hard enough!!!!<br />
You are just giving up!!!!!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Tovšak</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-720</link>
		<dc:creator>Peter Tovšak</dc:creator>
		<pubDate>Fri, 15 Jan 2010 10:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-720</guid>
		<description>JIT is just one amongst many priciples/guidance of LEAN MANUFACTURING. There are noultimate rule,  how deep to implement it (JIT). It depends from case to case of production environment.  In case of interactive MES, why not to implement it, especially, if we have production of different subassembly in floors under the same corporate umbrella. We have to balanced the material flow to the pace of main assembly lines to achieve steady moving of material, taking into account efficient use of logistic and transport resources. The inventory needed is only for buffering the sequence of dependent processes with different pace. For each item of final produst we have to achieve the during its production and its usage. 
Peter Tovšak, GORENJE d.d.</description>
		<content:encoded><![CDATA[<p>JIT is just one amongst many priciples/guidance of LEAN MANUFACTURING. There are noultimate rule,  how deep to implement it (JIT). It depends from case to case of production environment.  In case of interactive MES, why not to implement it, especially, if we have production of different subassembly in floors under the same corporate umbrella. We have to balanced the material flow to the pace of main assembly lines to achieve steady moving of material, taking into account efficient use of logistic and transport resources. The inventory needed is only for buffering the sequence of dependent processes with different pace. For each item of final produst we have to achieve the during its production and its usage.<br />
Peter Tovšak, GORENJE d.d.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Walker</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-719</link>
		<dc:creator>Ken Walker</dc:creator>
		<pubDate>Tue, 12 Jan 2010 18:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-719</guid>
		<description>I agree with the concept of stocking parts.  The problem we have had and continue to have is customer commitment to parts made beyond &quot;firm orders&quot;.   We have a claim now for obsolete parts that was determined as invalid even though the manufacturing process was weeks longer than the &quot;firm order&quot; lead time allowed.  Cost us several thousands in processing costs.  Often cannot meet deliveries if wait to begin making parts (let alone buy raw material) for repeat items until release becomes firm.</description>
		<content:encoded><![CDATA[<p>I agree with the concept of stocking parts.  The problem we have had and continue to have is customer commitment to parts made beyond &#8220;firm orders&#8221;.   We have a claim now for obsolete parts that was determined as invalid even though the manufacturing process was weeks longer than the &#8220;firm order&#8221; lead time allowed.  Cost us several thousands in processing costs.  Often cannot meet deliveries if wait to begin making parts (let alone buy raw material) for repeat items until release becomes firm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Benedix</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-717</link>
		<dc:creator>Gary Benedix</dc:creator>
		<pubDate>Tue, 05 Jan 2010 16:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-717</guid>
		<description>Lean manufacturing driven by real-time MES and tight integration to corporate ERP is the better way to go in our marketplace.  JIT may work in Japan or China where the suppliers are located close to each other and oftentimes sister companies under the same corporate umbrella.  I know of one application here in the US utilizing real-time MES, sequencing and tight integration with the customer order processing and manufacturing systems that comes as close to JIT as I&#039;ve seen.</description>
		<content:encoded><![CDATA[<p>Lean manufacturing driven by real-time MES and tight integration to corporate ERP is the better way to go in our marketplace.  JIT may work in Japan or China where the suppliers are located close to each other and oftentimes sister companies under the same corporate umbrella.  I know of one application here in the US utilizing real-time MES, sequencing and tight integration with the customer order processing and manufacturing systems that comes as close to JIT as I&#8217;ve seen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-716</link>
		<dc:creator>Blake</dc:creator>
		<pubDate>Mon, 04 Jan 2010 18:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-716</guid>
		<description>I wholeheartedly agree and have been saying such for years.  We need to use all our advantages; one key one is space.  It is something Japan has very little of per capita, but we have a lot of space and very low commercial real estate costs because of the economic crash.  It is time to banish warehouse taxes and encourage people to use the space we have.  An empty warehouse is like an empty hotel--the resource is perishable.  It should not cost an arm and a leg to the Gov&#039;t to have buffer inventory.  We have a chance to set some things right, let&#039;s make this change too.</description>
		<content:encoded><![CDATA[<p>I wholeheartedly agree and have been saying such for years.  We need to use all our advantages; one key one is space.  It is something Japan has very little of per capita, but we have a lot of space and very low commercial real estate costs because of the economic crash.  It is time to banish warehouse taxes and encourage people to use the space we have.  An empty warehouse is like an empty hotel&#8211;the resource is perishable.  It should not cost an arm and a leg to the Gov&#8217;t to have buffer inventory.  We have a chance to set some things right, let&#8217;s make this change too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PC</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-713</link>
		<dc:creator>PC</dc:creator>
		<pubDate>Mon, 28 Dec 2009 15:56:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-713</guid>
		<description>I&#039;ve seen that the amount of inventory buffer that many organizations maintain is far too high - often based on entirely spurious thinking like a knee-jerk reaction to a stock problem that happened a long time that somehow has become policy imbedded in stone.  I think that lean pushes you to question just why you have the amount of invested working capital you do and then pushes you to try to reduce it.  Obviously working within the 4-wall is easiest but there are certainly ways to reduce inventory buffers through the extended supply chain.  The buffering however needs to reflect the realities of changing demand patterns and the stability of the process.  It&#039;s a balancing act.  I would not however say that a make-to-stock model is the only model possible and that high inventory is just the cost of doing business.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen that the amount of inventory buffer that many organizations maintain is far too high &#8211; often based on entirely spurious thinking like a knee-jerk reaction to a stock problem that happened a long time that somehow has become policy imbedded in stone.  I think that lean pushes you to question just why you have the amount of invested working capital you do and then pushes you to try to reduce it.  Obviously working within the 4-wall is easiest but there are certainly ways to reduce inventory buffers through the extended supply chain.  The buffering however needs to reflect the realities of changing demand patterns and the stability of the process.  It&#8217;s a balancing act.  I would not however say that a make-to-stock model is the only model possible and that high inventory is just the cost of doing business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Gavoor</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-704</link>
		<dc:creator>Mark Gavoor</dc:creator>
		<pubDate>Fri, 18 Dec 2009 17:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-704</guid>
		<description>I think the de-coupling has already happened, de facto.  JIT implies supplier factories being near customer factories.  Materials, parts or assemblies, are supplied daily or hourly to the customer factory.  For this to happen, the supplier factory or DC needs to be within 24 hour delivery time from the customer factory.

With the massive off-shoring of production, JIT has been replaced by Lean which, to me, is minimization of inventories when the lead times are way too long to even think about JIT.  To add to Gary&#039;s point, when the lead times are long... forecasting errors will increase and dominate.  Thus, JIT becomes passe.</description>
		<content:encoded><![CDATA[<p>I think the de-coupling has already happened, de facto.  JIT implies supplier factories being near customer factories.  Materials, parts or assemblies, are supplied daily or hourly to the customer factory.  For this to happen, the supplier factory or DC needs to be within 24 hour delivery time from the customer factory.</p>
<p>With the massive off-shoring of production, JIT has been replaced by Lean which, to me, is minimization of inventories when the lead times are way too long to even think about JIT.  To add to Gary&#8217;s point, when the lead times are long&#8230; forecasting errors will increase and dominate.  Thus, JIT becomes passe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Chiappinelli</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-703</link>
		<dc:creator>Chris Chiappinelli</dc:creator>
		<pubDate>Fri, 18 Dec 2009 13:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-703</guid>
		<description>Gary makes a good point. Just-in-time encompasses many different activities, many of them beneficial to production activities. Basically what I tried to get across in my post was that beyond the four walls of the factory, my faith in Just-in-Time breaks down. I don&#039;t believe the same system that makes work cells and workers more efficient (delivering materials and components just in time) can be mapped to the customer delivery chain. I don&#039;t believe Toyota can truly deliver a finished product to the end customer just in time. It&#039;s an admirable goal, but one that too many good lean practitioners have failed to deliver on adequately.</description>
		<content:encoded><![CDATA[<p>Gary makes a good point. Just-in-time encompasses many different activities, many of them beneficial to production activities. Basically what I tried to get across in my post was that beyond the four walls of the factory, my faith in Just-in-Time breaks down. I don&#8217;t believe the same system that makes work cells and workers more efficient (delivering materials and components just in time) can be mapped to the customer delivery chain. I don&#8217;t believe Toyota can truly deliver a finished product to the end customer just in time. It&#8217;s an admirable goal, but one that too many good lean practitioners have failed to deliver on adequately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Foster</title>
		<link>http://blog.managingautomation.com/lean/2009/12/just-in-time-just-isn%e2%80%99t/comment-page-1/#comment-700</link>
		<dc:creator>Gary Foster</dc:creator>
		<pubDate>Wed, 16 Dec 2009 19:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.managingautomation.com/lean/?p=291#comment-700</guid>
		<description>Do you understand the purpose of J-I-T?
Not just reducing inventory, but reducing time until errors are discovered,  making problems apparent,  engaging and aligning people so they see that their effort is important.

Inventory or Batched product is a risk in many ways.
It does isolate processes.  sometimes good,  oftentimes bad.

GF</description>
		<content:encoded><![CDATA[<p>Do you understand the purpose of J-I-T?<br />
Not just reducing inventory, but reducing time until errors are discovered,  making problems apparent,  engaging and aligning people so they see that their effort is important.</p>
<p>Inventory or Batched product is a risk in many ways.<br />
It does isolate processes.  sometimes good,  oftentimes bad.</p>
<p>GF</p>
]]></content:encoded>
	</item>
</channel>
</rss>

