Kanban and similar pull systems like CONWIP or POLCA are basic parts of lean production. They limit the maximum number of parts by attaching a sort of token (i.e., the kanban card) to the part, and return to the beginning when the part leaves the system.
While Toyota did not invent the pull system, they did invent kanban, the genius idea of using cards of paper (and later other forms of information) to create a pull system for mass-produced goods. I recently was able to take pictures of Toyota kanbans, and would like to show and explain them to you. Continue reading Anatomy of the Toyota Kanban→
In my last post I described how to prepare for the implementation of a kanban system. This post goes into more detail on the actual change to the new kanban system. You surely know that every part should have a kanban. But what do you do if you have more kanban than parts? What do you do if you have more parts than kanbans? Find the answers below. Continue reading How to Ramp Up a Kanban System – Part 2: The Switch→
Designing a kanban system on paper is much easier than implementing it on the shop floor. In many of my previous posts I discussed the design of a kanban system in detail. In these two posts I will discuss the steps needed to actually put the system on the ground. This first post is the preparation, and my next post will be the actual switch to the new kanban system. Continue reading How to Ramp Up a Kanban System – Part 1: Preparation→
A kanban is, in its basics, information to reproduce or reorder parts. Hence, in its most basic form it has to say “make me this part” or “bring me this part.” While such very simple kanban systems are possible, usually it helps to include other information on the kanban card. In this post I want to talk about the design details of a kanban card, especially what kind of information we should include on the card. Please note that the items on the list below are suggestions. Which ones you actually include depend on the system you want to establish. Continue reading Kanban Card Design→
To create pull production between two processes, you can add either a FiFo lane or a supermarket. In one case you will have the FiFo as part of a bigger kanban or CONWIP loop, and in the other case you split the value stream into two different kanban or CONWIP loops.
Some questions that I have been pondering are: Which one has less inventory for the same delivery performance? Is it better to use a big loop or two smaller loops for the WIP and delivery performance trade off?