Batch Manufacturing
Batch manufacturing is the traditional form of manufacturing where production is completed in lots of various size, and the lots are passed along en masse to the next step. Typically, layouts in batch manufacturing are done by function—a weld shop, a paint shop, a fabrication shop, etc.
Another name for batch manufacturing is “batch and queue”. It gets this name for obvious reasons. Products are produced, and then are shipped to the next process, where they sit in line waiting to be worked on.
Lean Manufacturing Overview: Lean vs. Batch Manufacturing
I’ve got to warn you. This video on batch manufacturing is one of my first. It is a little slow, but it really does a great job of showing the flow of a batch system and a pull system operating side by side, building the same product. Focus on the content, please, and not the delivery.
On the surface, batch manufacturing has a lot of logic behind it.
- Big, efficient machines tend to have long setup times, so you have to spread out the changeover across a lot of parts to make it worthwhile. For example, consider this situation: a 10 minute setup time and a 1 minute cycle time for a part. It takes 11 minutes to do a setup and produce one part in single piece flow, for an average time per part of 11 minutes. When you batch 10 parts, it takes 20 minutes, for an average time of two minutes per part. Seems like a no-brainer about which option to choose.
- Batching deals with long processes (i.e. curing paint) by using big equipment that can handle large batches.
- When different functions are far from each other, batching helps lower the impact of transportation time. The effect is the same as setup—the more parts on a cart, the less time moving parts around takes per part.
- When assembly people do many parts at one time (like hose assembly or cutting wire for electrical harnesses), they can get into a rhythm that makes them really fly.
- When a machine is hard to adjust, it saves time to just run a whole bunch of pieces once the settings are dialed in.
- The night crew might not make as much as, or even all the same products that the day crew does. Perhaps the night shift only needs to add 15 or 20 percent to production and runs a slimmed down crew. In addition, in many cases, night shifts are used for processes that have trouble keeping up with the rest of the operation. In those situations, there might not be a downstream process present, so there is no way to create flow. The midnight crew would likely batch to cover any demand needs for the next day.
It sounds like there is a rather compelling case for batching. It is no wonder that it is so prevalent. So, what is the problem with each of these above arguments?
Each assumes that the underlying problem is not solvable. In the first example, the problem is that the team feels that they can’t reduce the setup time. Lean says to take the setup time down to single digit minutes (SMED), or eliminate it altogether.
In the long process example, the rationale is that there is no way to reduce the time the process takes or no way to avoid using large “monument” machines instead of small, right-sized ones.
Basically, in each of these cases, there is some underlying assumption that precludes flowing product smoothly. Lean breaks down these assumptions.
The Problem with Batching
So, why is batch manufacturing bad? Well, first of all, there is lots of inventory, and inventory costs money. It also takes up space. It requires heavy equipment to move it. It takes a long time to cycle through all of the product groups to meet customer needs. The list can continue, but the point is made. And these are all best cases.
In the worst case situation, batching can have a huge impact on quality. Imagine that a punch breaks on the first fabrication machine in a value stream, and a large batch is produced with every part missing a hole. The problem might not be noticed until the products snake their way all the way through to the last station of the assembly line, right before an important client’s shipment is scheduled to go out the door. Then people end up scrambling to try to track down all the bad parts, which have to be scrapped. In Lean, with less inventory, the problem would be noticed much sooner, minimizing the problem.
The reason that batch manufacturing is still around is that it is intuitive. When I got married, I had been in Lean manufacturing for a few years.
My wife to be and I assembled our wedding invitations. I thought I was being efficient. I figured out how to get the computer configured to print all of our envelopes, so I got them all done at once. Then we put all the stamps on at once. Then we got ready to put together all of the invitations at once. Things were going great until my then-fiancé told me that I had printed the addresses on the inside envelope instead of the outside envelope. I didn’t even know there was a difference! OK, that didn’t really happen, but it could have. We were batching.
Well, you get the point. After all my Lean training, I immediately reverted to a batch process at home. It just makes sense when looked at with the knowledge that most of us accumulate in a lifetime. It is one of the reasons that Costco and Sam’s Clubs are so popular. We think we are getting a deal when we buy 300 rolls of toilet paper all at once. We forget that we needed to buy the Super-Size SUV to transport it into our oversized house with enough closet space to hold it. We forget that the extra money we spent on it could have been earning interest in our account, instead of sitting in a hall closet in the form of paper goods.
I once had a team member tell me, “We are doing one-piece flow—we just do it 5 at a time.” There is just something ingrained in people along the way that batching is good business. Getting Lean, and really striving for continuous improvement requires developing an ability to take these paradigms and throw them out the window. Look at the process with an eye on how it should be set up if no problems existed, and then figure out how to get rid of the problems.
Take a look around your facility or office. See where work is done in a batch and consider why it is done that way. Focus on the underlying assumption. Target your improvement efforts at removing those paradigms.
0 Comments