Pete’s Note: We’re pleased to have Gary Netherton provide a guest post for us today. In this post, he shares a dialogue between operators around how to balance a line, which inevitably leads to an educational lesson on the Theory of Constraints, and methods for line balancing such as reducing cycle time, doubling, and moving work elements. He shares a line balancing example with application in the theory of constraints.
Enjoy his post and learn more about Gary after the article.
Ever have processes that need fixed but the team seems to have their own ideas about which processes need fixed first?Â As a result, you end up â€œfixingâ€ problems that seem to create problems elsewhere.Â It seems that you end up right where you started.
â€œHow did you manage to do that?â€
It is actually pretty simple.Â You donâ€™t choose your best target for improvement.Â Or, as Eliyahu Goldratt would say, you donâ€™t identify and attack your constraint.
â€œHow do you do that?â€
Well, that is actually pretty simple, too . . . Â if you take the time to do it correctly.Â This often means more than walking the floor and looking for a buildup of inventory between operations (though that is a very good start).Â One of the best ways to start is by mapping the process.Â Some might suggest a value stream map while others may say a process flow diagram will suffice.Â Either is a good option, but I recommend choosing the one that works for you.
After you have a picture of what your process looks like, pull out the old stopwatch.Â Take about 10 cycle time measurements for each operation that youâ€™ve identified on your flow diagram.Â When you are done, average them out and create a Pareto diagram of the operations.
The first, tallest bar on your diagram is your constraint.
Complete a detailed review of that operation.Â Look for opportunities to speed it up or pass off some of its activities to another operation (thatâ€™s called â€œline balancingâ€ . . . an important part of eliminating constraints).Â The idea is to either speed up that operation (if possible) or to â€œshareâ€ part of that operations activities with other operations.Â In the end, the goal is for all of the operations to take about the same amount of time (except the last one . . . it should be your fastest).
But what if I canâ€™t speed it up OR share with other operations?
Well, there is one more option, but this is a last resort.Â In the event that an all-encompassing operation cannot be split up or sped up â€“ like, for example, some kind of functional test â€“ you might need to consider doubling that operation.
Yes, doubling the operation is the equivalent of putting a fork in the river.Â Operation â€œCâ€ can either feed station â€œD-1â€ or â€œD-2â€, whichever is free.Â By having two â€œDâ€ stations, you essentially reduce the overall cycle time of that operation.Â Then either of the â€œDâ€ stations can feed the next operation.Â Granted, this operation may be a bit capital-intensive, but it can pay for itself in increased productivity if done correctly.
Using the Theory of Constraints â€“ the equivalent of a chain is as strong as its weakest link â€“ the team can attack items in a sensible order.Â And once that is complete, the cycle can start all over again (like PDCA).Â Restudy, re-graph, and research the weakest link (slowest operation).Â Attack that constraint and watch as the team starts to see improvements.
Gary Netherton is a multi-certified quality professional with project management experience in leading quality and manufacturing efforts from product and product launch to problem-solving using Six Sigma, PDCA, and other quality tools. His expertise is advanced product quality planning as well as data collection and analysis. He currently reside and work near the Seattle area of Washington.