Why Not Chase the Rabbit?By Jon Miller | Post Date: January 17, 2007 11:27 PM | Comments: 7 This is a question I have most often heard from European engineers, or from people in other countries who are working with extremely high volume light assembly operations, usually following some teaching about just in time production or Standard Work: "What do you think about the rabbit chase system?" I don't like the rabbit chase system at all. I would rather have people try the rabbit system, as well as Standard Work in u-cells or straight lines, whichever made sense, and compare the results. But if asked, I will explain that the rabbit chase does not seem Lean to me at all. The rabbit chase system, first of all, involves each worker doing all operations in a cell from beginning to end, "chasing" each other around and around as they work in the same cell. I don't know where the "rabbit" piece comes from. The advantages stated for the rabbit chase are that it is easy to add or subtract people from the line to increase output, and that you do not need to balance the line because people self-balance as they develop a pace. In addition, each person could gain a sense of satisfaction from learning how to operate each process. One of the main reasons that I have seen the rabbit chase performed is that the line speed or takt time for that cell is much too fast to do anything other than race to keep up. In some cases there would be more time waste in hand-offs and than in actual value added work done. But in these cases the design of the equipment and the pacing of work itself needs to be reconsidered, and slowed down through duplication of cells and low cost equipment. The hand-off approach that is the typical flow line or u-cell involves balancing cycle time between workers, and a clear definition of work sequence. Some raise the issue of timing of the hand-off but this is a non-issue if you allow one piece of Standard WIP. In the rabbit chase full training needs to be done for entire process for each person, which is a good thing if you can do it, but more practically the u-cell allows you to cross train step by step. In the rabbit chase each person must check their own quality, or perhaps rely on an end-of-line inspection, while in Standard Work the quality is built-in through in-process checks by the person doing the work as well as verification and feedback by the downstream person upon hand-off. In the case of the rabbit chase it would seem like there is the possibility of interference between one person and the next, if the speed difference between workers stacked up over time. Standard Work forces you to document a repeatable work sequence for each person that is based on takt time and while this is not always easy, it is an important discipline and the foundation of kaizen through the removal of variations in cycle time, making the work easier, low cost automation, etc. No doubt I am understating the benefits of the rabbit chase system, since I have undone far more of them than I have implemented. Feel free to comment in defense of the rabbit chase, as I could use the education. Whichever way you prefer, do an experiment to try it the other way. If you don't like the results keep trying until you get the results you need. Just don't say "I told you it wouldn't work" and revert back to today's proven method, which you need to think of as the "worst ever". That's kaizen way. Jon, I don't see the two approaches as opposed to each other, quite the contrary actually. I have implemented various "rabbit" lines when working for a (yes, european...) automotive supplier, all with a 45-60s takt. Here is how we overcame most of the issues you mention, except maybe cycle time variation which was not always easy to spot: First example: A 5 or 6 station U-shape of low cost machinery (spot welding, rivetting, manual assembly and functional check), manned with 2 or 3 workers according to takt--this ratio is crucial to avoid interference. All stations included extensive poka-yoke, SMED, manual load and automatic unload. When the workers arrived at a given station, they'd find the previous operator's part unloaded (when OK) or blocked (NOK) and would either load the station with fresh parts, start the process and carry the previous OK part with them to the next station--or pull the cord. Standard WIP = 1. Changeover was performed by a team leader who entered the cell between two workers and followed them from station to station while changing the fixtures in less than historic minimum takt, so the line didn't even have to stop. Second example: Low cost O-shaped moving lines with 5 to 7 pallets with some 7ft between workers, extensive integrated poka-yokes and one off-line functional check station, and flow racks from the outside. One lap corresponds to one assembly cycle, line speed and/or number of workers vary according to takt. Every worker assembles one complete process. Standard WIP = 0. Both systems used standard work (although it went by a different name), enforced a repeatable work sequence, were based on takt--and worked best when each worker performed a full cycle. We tried both ways. Poster: Thomas | Post Date: January 18, 2007 12:41 PM Thanks Thomas. You tried both ways. That's great. Why did you find one method better than the other? Poster: Jon Miller | Post Date: January 18, 2007 10:52 PM Jon, In the first example we encountered a serious balancing problem when operating the line with the number of operators necessary most of the time (product specific issue). In the second example we planned like this from the start, the operators (some of them came from the first example line) initially were reluctant because of "the endless miles we'll have to walk". They wanted to try it the other way and finally liked "full circle" better, mainly for ergonomic reasons. HTH. Poster: Thomas | Post Date: January 22, 2007 11:36 AM Jon, I've been working with "Rabbit Chase" System (Cell in Motion) for 8 years, and I'm absolutely convinced that is a powerful system. Here you are some benefits that I found: >
Better Ergonomics (reducing repeatability) Poster: Jorge Luis Angeles | Post Date: November 20, 2008 3:33 PM Dear Jorge, Your words are expressing good results, but at the same time if we are going for RC, the following problems are facing: 1.If we take a manual assembly cell with 5 manpower (4 operators &1 final inspector), if we engage all the 5 in RC, they have to undergo all the stations. If the assembly is having 25 parts to be assembled, 1. Difficult to train all the operators in all the stations Thanks & regards, Poster: Mariappan | Post Date: June 30, 2009 2:29 AM Mr. M.Mariappan I have recently successfully implemented RC in high volume production system at Hero Honda Motors Ltd in Welding line.I faced the similiar issue which you are talking about. In my views 1. We can break complete line (15 to 20 Station ) into 3/4 Cells based on the component. This is little difficult but once done can solve major training issue. In my case i breaked the complete line into three cells without compromising the overall flow of line. I guess you may find some answers. Thanks Ashish Gupta Poster: Ashish | Post Date: December 20, 2010 7:45 AM |



Hi Jon, to me the biggest advantage to properly designed u shaped cells is the pacing factor. One operator is able to work the entrance and exit of the cell which is an excellent pacing mechanism. Rabbit chasing is great for designing the cell though since a cell should be created such that one person can easily do all steps sequentially. But then once this is done the rabbits must leave! Just my two cents.