Kanban

Kanban (in kanji 看板 also in katakana カンバン, where kan, 看 / カン, means "visual," and ban, 板 / バン, means "card" or "board") is a concept related to lean and just-in-time (JIT) production. According to Taiichi Ohno, the man credited with developing JIT, kanban is a means through which JIT is achieved. The Japanese word kanban (IPA: [kanbaɴ]) is a common term meaning "signboard" or "billboard".

Kanban is a signaling system to trigger action. As its name suggests, kanban historically uses cards to signal the need for an item. However, other devices such as plastic markers (kanban squares) or balls (often golf balls) or an empty part-transport trolley or floor location can also be used to trigger the movement, production, or supply of a unit in a factory.

The need to maintain a high rate of improvements lead Toyota to devise the kanban system. Kanban became an effective tool to support the running of the production system as a whole. In addition, it proved to be an excellent way for promoting improvements because reducing the number of kanban in circulation highlighted problem areas.

Origins

The term kanban describes an embellished wooden or metal sign which has often been reduced to become a trade mark or seal. Since the 17th century, this expression in the Japanese mercantile system has been as important to the merchants of Japan as military banners have been to the samurai. Visual puns, calligraphy and ingenious shapes — or kanban — define the trade and class of a business or tradesman. Kanban signify a store where customers can purchase goods.

In the late 1940s, Toyota was studying supermarkets with a view to applying some of their management techniques to their work. This interest came about because in a supermarket the customer can get what is needed at the time needed in the amount needed. The supermarket only stocks what it believes it will sell and the customers only take what they need because future supply is assured. This led Toyota to view a process as a customer of preceding processes, and the preceding processes as a kind of store. The customer process goes to this store to get its needed components, and the store then replenishes the stock of those components. Kanban uses the rate of demand to control the rate of production, passing demand from the end customer up through the chain of customer/store processes. In 1953, Toyota applied this logic in their main plant machine shop.

Operation

An important determinant of the success of production scheduling based on "pushing" the demand is the quality of the demand forecast which can receive such "push". Kanban, by contrast, is part of an approach of receiving the "pull" from the demand. Therefore the supply, or production is determined according to the actual demand of the customers. In contexts where supply time is lengthy and demand is difficult to forecast, the best one can do is to respond quickly to observed demand. This is exactly what a kanban system can help: it is used as a demand signal which immediately propagates through the supply chain. This can be used to ensure that intermediate stocks held in the supply chain are better managed, usually smaller. Where the supply response cannot be quick enough to meet actual demand fluctuations, causing significant lost sales, then stock building may be deemed as appropriate which can be achieved by issuing more kanban. Taiichi Ohno states that in order to be effective kanban must follow strict rules of use (Toyota, for example, has six simple rules, below) and that close monitoring of these rules is a never-ending problem to ensure that kanban does what is required. Toyota's Six Rules are:

• Do not send defective products to the subsequent process
• The subsequent process comes to withdraw only what is needed
• Produce only the exact quantity withdrawn by the subsequent process
• Equalize production
• Kanban is a means to fine tuning
• Stabilize and rationalize the process

A simple example of the kanban system implementation might be a "three-bin system" for the supplied parts (where there is no in-house manufacturing) — one bin on the factory floor (demand point), one bin in the factory store and one bin at the suppliers' store. The bins usually have a removable card that contains the product details and other relevant information — the kanban card. When the bin on the factory floor becomes empty, i.e, there is demand for parts, the empty bin and kanban cards are returned to the factory store. The factory store then replaces the bin on the factory floor with a full bin, which also contains a kanban card. The factory store then contacts the supplier’s store and returns the now empty bin with its kanban card. The supplier's inbound product bin with its kanban card is then delivered into the factory store completing the final step to the system. Thus the process will never run out of product and could be described as a loop, providing the exact amount required, with only one spare so there will never be an issue of over-supply. This 'spare' bin allows for the uncertainty in supply, use and transport that are inherent in the system. The secret to a good kanban system is to calculate how many kanban cards are required for each product. Most factories using kanban use the coloured board system (Heijunka Box). This consists of a board created especially for holding the kanban cards.

E-kanban systems

Many manufacturers have implemented electronic kanban systems. Electronic kanban systems, or E-Kanban systems, help to eliminate common problems such as manual entry errors and lost cards. E-Kanban systems can be integrated into enterprise resource planning (ERP) systems. Integrating E-Kanban systems into ERP systems allows for real-time demand signaling across the supply chain and improved visibility. Data pulled from E-Kanban systems can be used to optimize inventory levels by better tracking supplier lead and replenishment times.

See also

• CONWIP
• C-VARWIP
• Enterprise resource planning (ERP)
• Just In Time (JIT)
• Manufacturing
• Material requirements planning (MRP)
• Manufacturing resource planning (MRP II)
• Scheduling (production processes)
• Supply chain management
• Drum-Buffer-Rope
• List of software development philosophies
• Lean software development

Further reading

• Ohno, Taiichi (1988). Toyota Production System: Beyond Large-Scale Production. Productivity Press. ISBN 978-0-915299-14-0. {{cite book}}: Unknown parameter |month= ignored (help)
• Waldner, Jean-Baptiste (1992). Principles of Computer-Integrated Manufacturing. John Wiley & Sons. ISBN 047193450X. {{cite book}}: Unknown parameter |month= ignored (help)
• Louis, Raymond (2006). Custom Kanban: Designing the System to Meet the Needs of Your Environment. University Park, IL: Productivity Press. ISBN 978-1-56327-345-2.

External links

• Kniberg, Henrik (June 29, 2009). "Kanban vs Scrum: A practical guide" (PDF). Retrieved June 29, 2009.
• Peterson, David (October 20, 2009). "Kanban for Software Engineering: An introductory guide for managers". Retrieved October 20, 2009.