Watch This One Piece Flow vs. Mass Production Envelope Stuffing Lean Thinking Simulation

No video

Watch This One Piece Flow vs. Mass Production Envelope Stuffing Lean Thinking Simulation

Рет қаралды 204,908

Күн бұрын

GembaAcademy.com | In this video Ron Pereira puts one piece flow up against mass or lot production in a fun, easy to duplicate, envelope stuffing simulation.
✉️ For more information about our Lean & Six Sigma courses contact us at: www.gembaacade...
Or call ☎️ Toll Free: +1-(888) 439-8880

Пікірлер: 16

@michaelhenry4405 8 жыл бұрын

Over the years I have come to realise how much time is lost due to material handling. I now seperate material handling as a seperate time measure during all tact time measurements. its an "in-hand" vs "out of hand" measure. In this case its 1 touch as opposed to 3 touches. However, the more intricate and more complex the situation the relevance of costing reduces. For instance each touch could then include an inspection point. So you can use the "time loss" as "inspection gain". It just makes for better idea thinking. Remember, Time Matters!

@stuartbudd5026 7 жыл бұрын

The answer is........... Less wait time. The envelopes are "waiting" for a smaller amount of time, or specifically in this case, there is less picking up the paper/envelope and placing it back down again. An example of why it is better to have a small level of work in progress (WIP). Thus, overall the amount of time required to complete the who batch is reduced. Note the "what happens if there is an issue" point in the video. That's an important point.

@memburydays7419 8 жыл бұрын

Saw your 1st video on this & it was brilliant for me Kee up the GREAT Work, love the Gemba Academy

@3moirai 9 жыл бұрын

It's an interesting demonstration, but I'm confused why this works especially as a one man station. Another big thing from Lean and Theory of Constraints thinking is the concept of Bad Multitasking. I would think that in a single man station, you would get an efficiency from performing each single individual task on the batch of 10 papers rather than constantly context switching through each task on one piece flow.

@rodrigo7ber 8 жыл бұрын

+3moirai There won`t be a conflict as long as you keep the station with less than 3 options or choices. As studies have shown, a normal person can deal with no more than 3 choices during one cycle. The key thing here isn`t efficiency. The goal isn´t to keep a worker busy all the time, but make sure material flows smoothly through the process. Even if that means keeping a low efficiency on resources. TOC mentions that efficiency thinking is precisely one of the constraints that avoid getting the best flow in any environment. The Goal explains that in detail.

@jefferan0118 8 жыл бұрын

very easy and educational video, Great!

@jayakumarsubramanian3485 7 жыл бұрын

very good example

@maxpower9672 7 жыл бұрын

"Google video", that was back when VHS was king, right? Jk Good video. Thanks.

@metu6246 7 жыл бұрын

great video, thanks!

@Mahesh_TC 8 жыл бұрын

Fantastic!

@Freevideobacks 8 жыл бұрын

nice video, very soundly video, enjoyed your cool clip

@InCog2020 9 жыл бұрын

Funny and informative.

@bdjuggalo 8 жыл бұрын

i like the demonstration good example compared to what i do for a living. I was wondering though does it make a difference that on the first part you double checked the envelope to make sure it was closed and on the second part you skipped that process. That over time does effect time right?

@maxpower9672 7 жыл бұрын

bdjuggalo, even if he spent an entire second on each double check, that would have only added 10 seconds to the process. As he mentioned, it's really the cumulative time each act of stacking, reaching, picking and repositioning that adds time to the mass produced system.

@ThaylorHarmor 7 жыл бұрын

bdjuggalo he didn't need to do that step because he had the piece in his hand. The piece did not need to be stored and put into inventory and then pull item out of the inventory. An example is software development is the time it takes you to get back into the code (aka context switching).