
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
  <title>Lean</title> 
  <description></description> 
  <link>http://www.lean.org/FuseTalk/forum/index.cfm?forumid=1</link> 
  <generator>FuseTalk Educational Edition</generator> 

	<item>
		<title>How do you VSM for Mixed Production?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1956</link> 
		<pubDate>2006-06-05T08:39:05 -05.00</pubDate> 
		<dc:creator>92921</dc:creator>
   	    <slash:comments>6</slash:comments> 
		<description><![CDATA[ What you can do to define a bottelneck is to measure the valu of making 3 pieces for each operator after that you can make your line balancing again because some times you plan a production on 100% ef.
her you must think about the people ho can not reach the takt time. think about the method also because some times you have 2 lines running with the same style and one line reach the takt time and theothers no in this case you must think about the methode of working must be the same if you have something not the same 
hope that you understand what I mean exactly
best regrds 
said ]]></description>
	</item>

	<item>
		<title>Can mapping find all the problems?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1948</link> 
		<pubDate>2006-06-02T16:39:55 -05.00</pubDate> 
		<dc:creator>86359</dc:creator>
   	    <slash:comments>8</slash:comments> 
		<description><![CDATA[ I use the following tools in this order: Spaghetti Diagram, Flow Process Chart, VSM, Material Handling Planning Chart, Timeline ==> Each tool tells just that extra knowledge than did the previous tools in the overall methodology!  VSM alone is a terribly inadequate tool if one wishes to design a total system. ]]></description>
	</item>

	<item>
		<title>Can mapping find all the problems?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1948</link> 
		<pubDate>2006-06-02T09:45:16 -05.00</pubDate> 
		<dc:creator>86359</dc:creator>
   	    <slash:comments>8</slash:comments> 
		<description><![CDATA[ Can VSM find all the problems?

NO.  The VSM gathers and displays whatever you collected.  

If you only gather information for the data box that concerns inventory and cycle time and batch size, then you will only see problems with inventory, batch size, and cycle time.

I teach that VSM should gather the inportant information.  To know what's important, you have to have some inkling of the problems to start with.

It is pretty safe to map inventory and distance and time but if (for example) I think I have a problem with maintenance, then I should have MTTF and MTBF or OEE on my map.

The VSM can only show the problems that we gather information.

Take care. ]]></description>
	</item>

	<item>
		<title>Anyone want to share their maps?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1862</link> 
		<pubDate>2006-06-02T04:45:43 -05.00</pubDate> 
		<dc:creator>33222</dc:creator>
   	    <slash:comments>44</slash:comments> 
		<description><![CDATA[ Hi

There are many methods of creating a VSM but following them for your process may not yield the results,(to eliminate the waste) since each process is diffenrent.  What is important is we should try to create the information and product flow saperately with the timeline.  I would advise you go through the Publication viz. "Learning to see" by Mike Rother and John Shook along with "Seeing the Whole"by Dan Jones and Jim Womack. You yourself will gain the confidence of building your VSM.

All the Best,

Rajendra Muley
Lean Expert
rajendra.muley@honeywell.com ]]></description>
	</item>

	<item>
		<title>Anyone want to share their maps?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1862</link> 
		<pubDate>2006-05-30T03:55:17 -05.00</pubDate> 
		<dc:creator>33222</dc:creator>
   	    <slash:comments>44</slash:comments> 
		<description><![CDATA[ Hello there,

I work at a printing industry and we are trying to build a VSM. Does anyone want to share some maps? It would be a great help.

Thanks! 


Ricardo Inácio
Grupo Higifarma
e-mail: ricardoinacio@higifarma.pt ]]></description>
	</item>

	<item>
		<title>Are Administrative/Business Processes Really Value Streams?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1943</link> 
		<pubDate>2006-05-25T15:21:50 -05.00</pubDate> 
		<dc:creator>77108</dc:creator>
   	    <slash:comments>7</slash:comments> 
		<description><![CDATA[ When I begin VSMs I always start by identifying the Value Stream Product. It makes mapping much easier especially in either administrative processes or even in the service industry. For example, in recruiting, an HR function, I begin by clarifying that the VS product is the "recruitment of a qualified candidate". For each administrative activity if you look at the "end result", the Value Stream Product you can then map it. And every process whether production, administrative, healthcare, etc has a Value Stream Product even if it is not something you can hold in your hand and look at. 

It makes the mapping much easier. Hope this helps. ]]></description>
	</item>

	<item>
		<title>Can mapping find all the problems?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1948</link> 
		<pubDate>2006-05-24T21:04:33 -05.00</pubDate> 
		<dc:creator>86359</dc:creator>
   	    <slash:comments>8</slash:comments> 
		<description><![CDATA[ I tried posting but my server went down. Hopefully this won't be posted twice. 

I tend to use the old process flow chart forms as well as VSMs. VSMs are great tools but the other form helps in that it can be used to measure time and distance for every step within a process. 

I'll try to attach one of the forms so you can see what I'm refering to. I'm sure you recognize it as they've been around for quite some time. For me they work well with VSMs. And it is an easy tool for employees to use. ]]></description>
	</item>

	<item>
		<title>Can mapping find all the problems?</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1948</link> 
		<pubDate>2006-05-24T20:55:59 -05.00</pubDate> 
		<dc:creator>86359</dc:creator>
   	    <slash:comments>8</slash:comments> 
		<description><![CDATA[ I also use the old process flow charting forms and VSMs. The reason being, the VSMs although great tools don't really take into account travel distance for example. The process flow chart forms measure distance and actual time wasted in a variety of non-value-added items. 

I'll try to attach a form so you can see what I am refering to. But together these tools work very well. ]]></description>
	</item>

	<item>
		<title>Cycle time calculation</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1960</link> 
		<pubDate>2006-05-16T12:52:57 -05.00</pubDate> 
		<dc:creator>99919</dc:creator>
   	    <slash:comments>2</slash:comments> 
		<description><![CDATA[ based on the information that you provided, I will assume that all subsequent operations, after the first machine, are duplicated.  If this is the case, the machine with a cycle time of 37 seconds paces your line.  Since you have two on these machines, the line (in it's entirety) produces a part every 18.5 seconds  (37/2). 

If you takt time is 17.7 seconds, I would susspect that you are running some overtime, even with the second line.

NOTE: you may be able to get by with only one machine #4 (17 second cycle) if the material can flow into and out of it. ]]></description>
	</item>

	<item>
		<title>VSM interactive training</title>
		<link>http://www.lean.org/FuseTalk/forum/messageview.cfm?catid=54&amp;threadid=1966</link> 
		<pubDate>2006-05-16T12:46:23 -05.00</pubDate> 
		<dc:creator>108984</dc:creator>
   	    <slash:comments>2</slash:comments> 
		<description><![CDATA[ Arrange for multiple facilitators and go to the floor (very interactive) and learn by doing.  If the operation is large, have the groups each do a section then bring it all together.  Another option is to have two groups do the same stream.  One starting from recieving, the other starting from shipping.  It is always interesting to see if hte current states are the same. ]]></description>
	</item>

</channel>
</rss>
