Download the eKanban Whitepaper

learn-about-ekanban-now

Subscribe for Email Updates

Your email:

Follow Ultriva

Ultriva Blog

Current Articles | RSS Feed RSS Feed

Why kanban is better than min/max replenishment

  
  
  

We all understand how difficult it is to change the wheels on a moving bus. If you've heard that analogy applied before, it was probably to justify why business transformation or a change in process is so difficult.

We've certainly heard the metaphor used to explain the entrenchment of Min/Max Replenishment systems. It's about the only excuse left because reality suggests it just doesn't make sense when compared to Lean manufacturing. Min/Max leads to higher inventory levels and higher inventory levels lead to higher costs. Higher costs are tough to swallow in the highly competitive global manufacturing world.

min-max inventory vs kanban

Why does min/max drive higher costs? The min/max approach promotes large and infrequent orders. These large orders result in significantly higher than needed inventory levels for several days or weeks during each replenishment cycle.

Min/max drives larger orders for several reasons. First, fear of stock-outs. Second, it's typically calculated on inventory levels that come from historical ERP functions. These ERP calculations are highly dependent on accurate bills of material and detailed tracking of scrap and defective material. Missing or inaccurate data in any of these areas leads to inaccurate data and inaccurate data makes for poor forecasting. If you fear stock-outs and you tend to have unreliable forecasts, how do you compensate to avoid stock-outs? You overshoot. When you overshoot, you carry higher inventory levels than you should carry.

In contrast, Kanban is based on more frequent, smaller orders and therefore lower inventory levels. With Kanban (or Electronic Kanban), you order upon or near depletion, replenishing what you need as you need it. Because Kanban cards or bar coded labels are tracked where the material is consumed, inventory data can be tracked very reliably, driving a demand-driven system that promotes lower inventory levels and lower costs.

It is hard to change the wheels on a moving bus, but case study after case study is proving a Lean business is a better business. Eventually, the wheels must be changed.

Comments

There is no real difference.  
 
 
 
You’ve decided through Kanban to make what you sell daily. Good choice. You’ve reduced your batch size. Again, good choice. 
 
 
 
You could accomplish the same by using min/max and reducing you batch size to 1 day (or 1 hr.) or whatever period desired.  
 
 
 
Either method, you accomplish the same result. Get as close to one piece flow as possible. 
 
 
 
Your example shows a very static demand pattern. Kanban works well in that environment. Change that to a very erratic pattern, with limited capacity, and Kanbans fail miserably. 
 
People who argue this live unlimited capacity/resource environments. But it’s not Wonderland like your example. 
 
 
 
Inventory, at the right level, adds value in overcoming variation and abnormalities, either in process, or in flow. If your upstream process consumes faster than 
 
your Kanban can fill, or your replenishment system fails, you don’t service your customers. Any you know what, they don’t really care how much extra inventory you carry,  
 
as long as you support them when they want material, in whatever quantity they desire. If you can’t, and you don’t have any other “hooks” , they move on to someone  
 
who can.  
 
 
 
You got to drive the bus, but don’t paint the windshield black and use the rear view mirror for direction.  
 
 
 
The real key is to remove all abnormality from you systems to minimize inventory, and learn how to respond quickly to those abnormalities.  
 
 
 
Once that occurs, move to Kanban because the foundation is now in place for success. 
 
Posted @ Friday, April 20, 2012 2:15 PM by Onejux
I agree, Kanban is based on actual usage rather than an estimated projection. You still need to maintain the Kanban properly to adjust the Kanban size every time usage changes (Dk). Thanks for sharing! 
 
Gabriel- 
 
Posted @ Wednesday, April 25, 2012 9:40 PM by Gabriel Solano
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics