In my previous posts I explained what “Just in Time” is, and started with different actions on how to make “Just in Time” work. As it turns out, there are a lot of things you can do, and one blog post was not enough. So here’s part two on how to make “Just in Time” work! As before, be warned that most of these methods or actions are not easy!
Level Your Production
In addition to a reliable signal, it is also important to give the supplier a steady and stable demand. This means leveling your production (which is again easier said than done). I wrote a whole series of posts on the different ways to do leveling (heijunka). The more stable your orders are for the customer, the easier it is for your suppliers to deliver the products just on time. Lean tools like small lot sizes, SMED, and a good product mix help.
Hence, avoid changes in your product mix if you can. The less you change your mix, the better. If you frequently increase or decrease quantities – even if you tell the supplier a day before shipping – the supplier will need additional inventory again to cover these fluctuations.
Internal Milk Run
Previously I talked about the benefit of an external milk run, or delivery routes with multiple stops at multiple suppliers. The same can be done within the plant. A milk run that delivers parts at a higher frequency than a conventional delivery will require less material at the production processes. And remember, the space there is the most valuable in your plant! Hence, if you have not done it already, consider implementing a milk run to achieve a Just in Time delivery at least between your warehouse and your manufacturing location (although, traditionally, this may not be considered Just in Time, as JIT usually involves the supplier. But the effect is the same).
Pull Production and Pull Deliveries
One major source of fluctuations is humans, especially when planning delivery or production quantities. They may over- or underestimate demand, pool orders, or have other quirks that makes their plan less stable than it could be. If I were in their shoes, I would probably do the same, since I am merely human too 😉 .
However, if I could, I would implement a pull production, both for my own production system and for the deliveries of goods to me. I have written a lot about pull before (e.g., Why Pull Is So Great! and The (True) Difference Between Push and Pull). So, without going into too much detail, pull production will help you a lot when you try to do JIT.
Ship to Line
A related approach is Ship to Line. The idea is to deliver arriving shipments not into the warehouse, but directly to the line (or, in general, the processes) where they are needed. This, of course, works only with small shipments, as otherwise the space around your processes would be overloaded.
Just in Sequence
Yet another related approach is Just in Sequence. The idea is to deliver the parts not only in time, but also in the sequence they are needed. This way there is less effort in sorting out the sequence after unloading, which reduces another source of fluctuation.
This is commonly done in the automotive industry with seats. Due to the many different seat variants, it is usually not possible to keep them in stock. Instead, the supplier is very close to the plant, has a direct line to the production plan, and delivers the seats for the car just in the right sequence (and naturally also just on time) as they are needed.
Focus on Your High Runners
All of the previous actions are not easy. If you are just starting with JIT, then you should focus on your high runners and your expensive or large parts. High runners are frequently purchased goods, and hence have much less fluctuation than low runners. Through its larger quantity alone, the fluctuation is already reduced, making it easier for you to do JIT.
Also, the benefit will be larger for expensive or large-sized parts. The expensive parts have a bigger benefit in terms of tied-up capital, whereas the larger parts have a bigger benefit when it comes to the space around your production processes.
Convince Your Suppliers
To implement JIT, you need to work together with your suppliers – and your supplier with you. Quite a bit of the effort is usually on the supplier’s side. Hence, you need to convince them to join the efforts. There are usually two strategies common in industry.
First, if you are a large or even the largest customer of your supplier, you have a lot of market power over them. Hence, the supplier has an interest to keep its biggest customer (you) happy. For the supplier, it is also an economy of scale, as it is easier to deliver JIT if you have larger quantities of goods to deliver. A common example is the automotive industry and their suppliers, although even then a brute-force approach rarely works.
Second, if you are only a small customer of your supplier, you have to give them other incentives. This is usually a bit more difficult, as “incentive” usually means “money.” You need to share the benefits of JIT with the supplier. Even then, there is a risk that this may not be worth it for a supplier for whom you are only a small customer.
What usually does not work is a small customer trying to force a supplier to do JIT. Of course, the supplier will not tell you so, but it will use lots of sweet words that sound like cooperation. In reality, however, the supplier will try to get away with minimal effort, which usually is not good enough.
What Is Not Necessary (but may be good anyway)
After all these different things you could do, I would like to mention a few things that may not be necessary, even though other literature mentions them sometimes (e.g. a book I highly appreciate, Factory Physics by Hopp and Spearman). Here, it seems like a lot of different topics of lean manufacturing are pooled under the header of JIT. While the topics are good, some may be less necessary than others for a good JIT.
Some authors mention that single source is necessary for Just in Time (i.e., there should be only one supplier). I think this is not really necessary. While there is a small additional effort in coordinating two suppliers, I think this effort is not prohibitive. Simply schedule the deliveries as you need them, sometimes from one, sometimes from the other supplier.
The disadvantage would be smaller quantities from each supplier, and hence a tad more fluctuations for each. You also would have to make sure to alternate the delivery sources as much as possible. If you do one month from one supplier and then a month from the other supplier, then you make it more difficult for both of them.
On the other hand, dual source or even multi-source have the advantage of a more stable supply in case of disruption, strike, technical problems, bankruptcy, and so on. For this reason, many companies try to source important parts from two suppliers.
Many other things have been mentioned as a necessity for JIT, like preventive maintenance, visual management, cellular manufacturing , and so on. While they surely do not hurt, I personally think they are not a key factor for a successful JIT implementation. In any case, I hope this three-part series will help you in understanding and implementing Just in Time. So, go out, get your parts exactly when you need them (but not earlier or later), and organize your industry!
Nice learning. Thank you.
Thanks for sharing your thoughts. Although might not be strictly necessary (what part of lean is?) when thinking about JIT I also think in the connection to single piece flow and SMED.
Hi Miguel, one piece flow (and the SMED needed to reach it) can help, thanks for pointing that out. I added “Please note that there is no point to have deliveries smaller than your lot size in production. Hence, JIT benefits also from small lot sizes and one piece flow in production.” to my previous post on this topic. Thanks, Chris.
Really appreciate. After 15yrs Lean practice I still try to figure out what, how much, how this is ideally applied to multi-channel commerce and distribution (logistics). Any insights? Steffen
Hi Steffen, Interesting question. I usually associated JIT with pull, hence it would be mostly inbound logistic. But, I guess similar things can also be applied to distribution – if you have control over distribution. Small lot sizes probably work, too, and are beneficial ,too. For a delivery just in time, however, you would need to know when exactly what is needed, and usually the supplier does not have enough detail on that, but rather fulfills the orders of the customer. I have heard cases, however, where the supplier successfully suggested smaller lot sizes to the customer.
Hope this helps,
Chris
Excellent post Chtistoph.
A/ Focus on High runners
In Project or Engineering activity, high runners are not stable whatever the level of levelling implemented.
Indeed, we have 3 groups of parts: 1/3 stable high runners, 1/3 low runners and specific to order parts and 1/3 all parts falling between the 2 previous categories. When they are cheap and small they can be considered as high runners as benefits of kanban are expected to be far higher than side effects (cost, space, effort to review frequently the kanban rules).
The % of such parts will be usually far higher in western countries than in emerging countries as manpower is considered expensive …and robust supply chain needed for external kanban is already available.
B/ kanban and double source
When part consumption is not stable, the company wants to get cost benefit of low cost import or secure its supply chain. Then double source is not a blocking point for kanban. Domestic source can be managed by kanban and second source by a MRP replenishing a local distribution center managed by EDI or call off. It requires to implement a process to systematically re-calculate (through SIOP/MPS/ERP) an optimized quota for each source (specific ERP functionality or double MRP calculaton). I suggest both sources should be used in parallel with defined rules. Then double source eases tasks of SCM practitionners and prevents shortages.
Note that Kanban could also address in parralel the 2 sources.
Congrats for your book and your very practical posts I often circulate to colleagues.
Patrick