Simulate Kanban control loops
Set up the control loops – demand, product store (kanban count), and lot size – then press Play. The simulation runs the pull process column by column: each column triggers one or more box withdrawals. A yellow transport kanban replaces the pink production kanban, which collects at the lot post to form a lot (with a separate lot size for each variant). The lot passes through the chute and the 4 stations (with changeover station by station), and the Loading cart returns the finished lot to the product store. At the end, you can see how well your plan worked – and where bottlenecks occurred.
Simulation results
Updates live while the simulation runs.
Set up control loops
Set demand, product store (kanban count), and lot size for each variant – plus the withdrawal pattern (leveled / in blocks).
Withdrawal control loop (yellow transport kanban)
Each column of the Heijunka schedule releases the yellow transport kanban – a column can contain multiple withdrawals (A+C, A+B …). It retrieves the box from the product store; if it is empty → shortage.
Production control loop (pink production kanban)
The detached pink card collects at the lot post to form a lot (lot size) → full lot into the Chute → through the 4 stations (changeover station by station) → Loading cart returns the finished lot to the product store.
Global parameters
Variants
Simulation
Press Play – the pull process unfolds card by card. The columns are numbered; the blue marker ▼ shows the current column, and the yellow outline marks the card currently being withdrawn. Use Step ⏭ / ⏮ Back to move forward or back one step at a time. Red marks shortages (“View Point for problems”).
for problems
Understand control loops (guided)
From the pull principle and the two control loops to sizing – technical terms are underlined.
Video companion · Questions & answers
The video is an animation without narration. This companion explains what it shows and the underlying concepts from the course materials in plain language. Click a question to open its answer. Technical terms are underlined (hover over them).
Terms explained simply +
A control loop in a pull system links consumption to replenishment: production starts only after something is withdrawn. Here are the key terms in plain language:
How saving works +
This HTML file is your document. Everything you enter is saved in this very file, just like a Word document. If you share the file, it includes all your simulations.
Save (green button or Ctrl+S) saves the current state without prompting. Until you create your own working file, the state is stored in the browser and is available the next time you open it.
Save as (under “Simulations”) creates a file on your drive. This is the only time you are asked where to save. After that, each Save writes silently to the same file.
The first time: Open the file, click “Simulations”, then Save as. From then on, just use the green button.
Autosave: Once a simulation has been saved, the tool automatically saves subsequent changes after a few seconds.
If something goes wrong: The tool continually stores a recovery copy in the browser. If the browser crashes or you accidentally close the window, your work is available the next time you open it.
Browser support: Chrome and Edge currently support writing directly to the file. In Firefox and Safari, everything stays saved in the browser, and the file itself remains unchanged.