Just-In-Time (JIT) Explained
By Mahasys Multi Zenith · Manufacturing software for Indonesian plants · Last updated June 2026
Just-In-Time (JIT) is a production philosophy developed at Toyota: produce and deliver only what is needed, when it is needed, in the amount needed. It is one of the two pillars of the Toyota Production System (the other is jidoka — built-in quality). JIT replaces inventory buffers with fast, accurate signals — and kanban is the mechanism that carries those signals.
The idea: inventory hides problems
Taiichi Ohno's famous metaphor describes inventory as water in a river. When the water level is high, the rocks at the bottom — machine breakdowns, long changeovers, quality defects, unreliable suppliers — are invisible. The boat sails smoothly, but the rocks are still there and the water is expensive.
Lower the water and the rocks appear. That is uncomfortable by design: JIT deliberately reduces inventory so problems surface and must be fixed at the root, instead of being absorbed by buffer stock. This is why JIT is inseparable from continuous improvement — every reduction in inventory exposes the next problem to solve.
The three elements of JIT
- Takt time. The rate of customer demand — total available production time divided by required output. Every process is paced to takt, not to machine capacity.
- Continuous flow. Parts move one piece (or one small lot) at a time through the value stream, instead of sitting in batches between processes.
- Pull system. Downstream processes pull from upstream only what they consume. Nothing is produced "just in case." Kanban cards are the pull signal.
JIT and the supplier: what it actually demands
Inside a single plant, JIT is a scheduling discipline. Across a supply chain, it becomes a contract: the OEM's assembly line depends on every supplier delivering the right part, in the right quantity, inside a tight time window — often multiple deliveries per day.
For a Tier 1 or Tier 2 supplier serving Japanese OEMs in Indonesia, the practical daily reality of JIT looks like this:
- The OEM publishes the day's kanban requirement electronically (e-Kanban).
- The supplier prints kanban cards and attaches them to containers as parts are produced.
- Deliveries run on fixed milk-run routes and dock windows — a truck arriving 30 minutes late is a reportable event.
- Consumed kanban return as the signal to produce the next cycle.
Every manual step in this loop — retyping data, cutting printed cards by hand, sorting by lane — adds delay and error risk to a system designed around speed and precision. This is why kanban-process automation is usually the first digitalization project with provable ROI at supplier plants.
JIT vs traditional batch production
| Aspect | Batch / push production | Just-In-Time (pull) |
|---|---|---|
| Production trigger | Forecast / monthly plan | Actual consumption (kanban signal) |
| Inventory | Large buffers between processes | Minimal, capped by kanban count |
| Lot size | Large (amortize changeovers) | Small (requires fast changeover / SMED) |
| Problem visibility | Hidden by inventory | Exposed immediately |
| Cash tied in WIP | High | Low |
| Demand on data | Monthly reports suffice | Real-time signals required |
What JIT requires to work (and where it fails)
- Heijunka (leveled production). Pull systems break under demand spikes. The OEM levels its build schedule so supplier demand is stable enough to pull against.
- Fast changeovers. Small lots are only economical when changeover time is minutes, not hours (SMED).
- Built-in quality (jidoka). With no buffer stock, one defective lot stops the chain. Defects must be caught at the source.
- Reliable, fast information flow. The signal is the system. Late, wrong, or manually re-keyed data breaks JIT faster than a machine breakdown does.
- Supplier discipline across tiers. JIT at the OEM only works if Tier 1 delivers JIT — which increasingly means Tier 1 asks the same of Tier 2.
The well-known failure mode is supply disruption: the 2011 Tōhoku earthquake and the 2020–2022 semiconductor shortage both stopped JIT assembly lines worldwide. Toyota's response was not to abandon JIT but to add strategic buffers for long-lead critical components while keeping pull discipline everywhere else. The lesson for suppliers: JIT is not "zero inventory" — it is right-sized inventory with fast signals and exposed problems.
Frequently asked questions
What does Just-In-Time (JIT) mean? +
Just-In-Time is a production philosophy developed at Toyota: produce and deliver only what is needed, when it is needed, in the amount needed. Instead of building inventory as a safety buffer, JIT synchronizes every process to actual demand — exposing waste that inventory would otherwise hide.
What is the relationship between JIT and kanban? +
JIT is the philosophy; kanban is the operating mechanism that makes it work. Kanban cards are the physical signal that tells each process exactly what to produce and when. Full kanban guide here.
Apa itu Just-In-Time dalam industri otomotif Indonesia? +
Dalam ekosistem otomotif Indonesia, JIT berarti supplier Tier 1 dan Tier 2 mengirim part ke OEM sesuai jadwal kanban harian — bukan forecast bulanan. Supplier menerima sinyal e-Kanban setiap hari, memproduksi sesuai jumlah yang diminta, dan mengirim dalam window waktu ketat ke plant OEM di Karawang, Cikarang, atau Sunter.
What are the risks of JIT? +
Supply disruption, demand spikes beyond leveled capacity, and logistics failures. Toyota mitigates these with supplier development, heijunka, and selective strategic buffers for critical components. JIT is not zero inventory; it is right-sized inventory with fast signals.
Further reading
- Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production (1988) — the primary source on JIT and kanban.
- The Toyota kanban system explained — the pull mechanism that executes JIT.
- What is e-Kanban? — the modern electronic implementation.
- Jishuken explained — Toyota's supplier improvement workshops that spread JIT capability.
- What is MES? — the real-time data layer JIT-era plants run on.