<?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: Let&#8217;s Create a Future State Value Stream Map!</title>
	<atom:link href="http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/feed/" rel="self" type="application/rss+xml" />
	<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/</link>
	<description>Lean Manufacturing, Six Sigma, Lean Six Sigma, and Kaizen</description>
	<lastBuildDate>Wed, 01 Feb 2012 21:21:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-2959</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sat, 14 Feb 2009 05:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-2959</guid>
		<description>One things that I note regarding the measurement phase.  What would you advise about confirming measurement? A GR&amp;R or a some sort of test such as t-test? On thing about the Takt time would be better to round down the take time to protect the customer?</description>
		<content:encoded><![CDATA[<p>One things that I note regarding the measurement phase.  What would you advise about confirming measurement? A GR&amp;R or a some sort of test such as t-test? On thing about the Takt time would be better to round down the take time to protect the customer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Let&#8217;s Create a Current State Value Stream Map! &#124; Lean Six Sigma Academy</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-1643</link>
		<dc:creator>Let&#8217;s Create a Current State Value Stream Map! &#124; Lean Six Sigma Academy</dc:creator>
		<pubDate>Tue, 18 Mar 2008 17:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-1643</guid>
		<description>[...] the next article in this series: Let’s Create a Future State Value Stream Map! SHARETHIS.addEntry({ title: &quot;Let&#8217;s Create a Current State Value Stream Map!&quot;, url: [...]</description>
		<content:encoded><![CDATA[<p>[...] the next article in this series: Let’s Create a Future State Value Stream Map! SHARETHIS.addEntry({ title: &#8220;Let&#8217;s Create a Current State Value Stream Map!&#8221;, url: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick ong</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-1443</link>
		<dc:creator>nick ong</dc:creator>
		<pubDate>Tue, 04 Mar 2008 12:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-1443</guid>
		<description>i recently have been asked by my boss to do a future state map for despatch area, but as you know despatch area have no takt time or lead time. so where should i start from? any ideas?</description>
		<content:encoded><![CDATA[<p>i recently have been asked by my boss to do a future state map for despatch area, but as you know despatch area have no takt time or lead time. so where should i start from? any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Introducing the Kaizen Newspaper &#124; Lean Six Sigma Academy</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-1417</link>
		<dc:creator>Introducing the Kaizen Newspaper &#124; Lean Six Sigma Academy</dc:creator>
		<pubDate>Sun, 02 Mar 2008 21:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-1417</guid>
		<description>[...] Let’s Create a Future State Value Stream Map! [...]</description>
		<content:encoded><![CDATA[<p>[...] Let’s Create a Future State Value Stream Map! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Watson</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-1364</link>
		<dc:creator>Charles Watson</dc:creator>
		<pubDate>Wed, 27 Feb 2008 03:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-1364</guid>
		<description>Thank you.  Yes, it helps.  I knew it was probably something easy like that.</description>
		<content:encoded><![CDATA[<p>Thank you.  Yes, it helps.  I knew it was probably something easy like that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Pereira</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-1363</link>
		<dc:creator>Ron Pereira</dc:creator>
		<pubDate>Wed, 27 Feb 2008 03:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-1363</guid>
		<description>Thanks for the great question Charles.  In hindsight, I probably could have been more clear with this section.  Here is the explanation.

The total cycle time to make a sandwich is 97 seconds.  However, when we work in one piece flow (no waiting or delay between steps) while using 3 operators we simply divide 97 by 3 which gets us around 32 seconds.  

Now, this assumes we can balance the work evenly... essentially giving each operator around 32ish seconds of work to do.  

In real life, it may be that operator 1 has 30 seconds of work, operator 2 has 35, and operator 3 has 32 seconds of work.

Does this help?</description>
		<content:encoded><![CDATA[<p>Thanks for the great question Charles.  In hindsight, I probably could have been more clear with this section.  Here is the explanation.</p>
<p>The total cycle time to make a sandwich is 97 seconds.  However, when we work in one piece flow (no waiting or delay between steps) while using 3 operators we simply divide 97 by 3 which gets us around 32 seconds.  </p>
<p>Now, this assumes we can balance the work evenly&#8230; essentially giving each operator around 32ish seconds of work to do.  </p>
<p>In real life, it may be that operator 1 has 30 seconds of work, operator 2 has 35, and operator 3 has 32 seconds of work.</p>
<p>Does this help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Watson</title>
		<link>http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/comment-page-1/#comment-1362</link>
		<dc:creator>Charles Watson</dc:creator>
		<pubDate>Wed, 27 Feb 2008 02:50:38 +0000</pubDate>
		<guid isPermaLink="false">http://lssacademy.com/2008/02/26/lets-create-a-future-state-value-stream-map/#comment-1362</guid>
		<description>Can you clarify what you mean when you say, &quot;Once the work was redistributed the team was able to produce a PB&amp;J sandwich approximately every 32 seconds. The total time for the first sandwich to be complete is still 97 seconds.&quot;

I am not sure I follow this?  Is the cycle time 32 seconds or 97 seconds?  And do the number of operators matter here?

Sorry if this is obvious.  I am new to this and am trying to learn.  Thank you.</description>
		<content:encoded><![CDATA[<p>Can you clarify what you mean when you say, &#8220;Once the work was redistributed the team was able to produce a PB&amp;J sandwich approximately every 32 seconds. The total time for the first sandwich to be complete is still 97 seconds.&#8221;</p>
<p>I am not sure I follow this?  Is the cycle time 32 seconds or 97 seconds?  And do the number of operators matter here?</p>
<p>Sorry if this is obvious.  I am new to this and am trying to learn.  Thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

