I see that for lean manufacturing one very good way to identify waste is to map out the process using spaghetti chart. Can someone help in developing the spaghetti chart. Where can I find more info on spaghetti chart?

Hmmm. I wonder if you are referring to the type of chart I locally call a "bubble chart". This listed the various stages in a process (bubble) and the number of items and how long they took to move from stage to stage. I've attached a particularly nasty one from years ago, and that process is considerably smoother now.

Actually, I think johnnybegood is referring to a chart that looks like an aerial long-exposure photo of someone moving through all the processes with a bright light attached to him so the resulting photo looks like a plate of spaghetti as the person crosses and recrosses paths in accomplishing all the processes.

Take a look at this link for a more clear idea of the concept
http://www.isa.org/PrinterTemplate.cfm?Section=InTech&template=/ContentManagement/ContentDisplay.cfm&ContentID=38982

The last thing you want is a spaghetti chart as an end product. (And hopefully, not as a starting product.)

A computer program is often described by the type of "pasta" it resembles. A "spaghetti" program has code running everywhere. In the process mapping/VSM world this is a depiction with things running everywhere. Thus, if you map the product flow, it looks like a bowl of spaghetti!
A "lasagne" (or lasagna) program is layered. Program main routines, applicable sub-routines, and output, are located in the same strata.
"Ravioli" programming uses packets. Instructions are routed into areas for computation.

Capisce?
A "spaghetti" production process is a mess!
A "lasagne" operation is rare.
A "ravioli" production system is a goal of lean; the cellular methodology. Lessen waste by putting all steps close; less hand-over, inventory, etc.

Madfox
(AS, computer science...non Italian)

The link Wes put up is a good one.

Typically I do not use a spaghetti diagram for product flow, I use it for process flow. (typically 1 cell at a time).

Often, there are so many lines, it looks like spaghetti.

For what ever its worth, I use the Std. Work Combination table, then when mapping the flow, I first number from a starting point, to each point in the cell where work is done, cell to cell. Then, just as I did in 1st grade, I follow the numbers, dot to dot to see what my picture looks like.

No need to add complexity to this subject. Take an overhead of your plant or process layout and pencil in the traffic associated with the individual performing the work, or better yet, the product traveling through the plant. Running with the assumption that WIP inventory is very impatient (it should be) and needs to get to a finished state, look at the amount of travel it takes for your product to make it to the finished stage. Since travel is non-value added work, eliminate as much as possible. The speed of any process, or plant, is inversely proportionate to it's level of complexity. Excess travel does not add value and creates complexity.

Spaghetti diagrams (vs charts) are one of the best tools to visualize one of the 7 deadly wastes - excess travel. Start with the raw material cage or receiving doc and follow a major material throught its actual travel to get to either the finished goods cage or shipping doc.

If you can do this while there is also WIP of the same part, it is also very valuable to note the date on the part in the various locations. You then get not only the spaghetti diagram but also a rough idea of the flow time.

From there go and find the actual labor hours in your cost accounting system to make the part. If you are not doing lean work yet I'll bet you will find the actual value adding time is 5% or less of the time the part is in process.

This information is the basic building block for value stream mapping and can have incredible results when implemented correctly.

If you would like additional information, let me know. Send me a PM.

Gregg

a small example from one of my friends

thanks

pls refer attached

http://en.wikipedia.org/wiki/Spaghetti_chart


A spaghetti chart is a graphical aid used in lean manufacturing (http://elsmar.com/wiki/Lean_manufacturing) activities. It is used to detail the actual physical flow and distances involved in a work process. Processes that have not been streamlined (http://elsmar.com/wiki/Streamlined) frequently are poorly laid out with work/product taking a path through the work area that looks like a mass of cooked spaghetti (http://elsmar.com/wiki/Spaghetti).
To create a spaghetti chart you first create a scale map of a work station or work process. The next step is to draw a line from the initial point of work to the next step, then the third step, and so on until the work/product exits the work area. Examination of this resulting chart will show where improvements are to be made.
Using the information provided by the process chart is to be used to physically relocate work steps so that work/product does not backtrack at any point and proceeds in a linear fashion. A common end layout resulting from using a spaghetti chart is a "U" - shaped workstation where material enters on one end and exits in parallel fashion with all work steps completed.

mmmm spaghetti