Pull System Architecture: Demand-Driven Production

Design pull systems that make only what is used: pull signal types, kanban sizing, supermarket design, FIFO lanes and how pull works with MRP.

18 min read 5 sections Guide 7 of 20, Lean Master Practitioner Updated

USEREFILL
KanbanNothing is made until a card asks for it

New to this topic?

Read these first to get the most out of this guide:

3
Pull Signal Types
K=DL(1+S)/C
Kanban Formula
FIFO
Simplest Pull Lane
≤WIP Cap
CONWIP Rule

Push vs. Pull: The Fundamental Choice

In a push system, production is driven by a forecast. MRP calculates what should be produced when, and releases work orders to the floor. The problem: forecasts are always wrong. When demand is lower than forecast, inventory accumulates. When demand is higher, you are short. And because work is released on schedule rather than on signal, WIP builds throughout the factory with no mechanism to limit it.

WIP 7LEAD TIME
Little's lawWIP = throughput × lead timeThe Little's law guide

In a pull system, production is driven by actual consumption. When the downstream process uses a part, a signal goes upstream: “I consumed one. Make another.” Nothing is produced without this signal. This creates a natural WIP limit: the total number of pull signals in the system equals the maximum WIP. Little’s Law guarantees that limiting WIP reduces lead time.

Three Types of Pull Signals

LINE
CONWIPA fixed number of cards: a job starts only when one leavesThe CONWIP guide
Signal TypeHow It WorksBest For
Kanban CardA physical or electronic card that authorizes production of a specific part in a specific quantity. When the downstream process consumes a container, the card returns upstream as a production signal.Repetitive parts with stable demand. Standard fasteners, brackets, common machined components.
FIFO LaneA physical lane (rack, conveyor, or marked floor area) with a fixed capacity. Upstream produces until the lane is full, then stops. Downstream consumes from the lane.Custom or variable parts flowing between two specific operations. No need to specify part number: just “next in sequence.”
CONWIPA system-wide WIP limit. When one unit exits the entire system, one unit is authorized to enter. See CONWIP guide.Job shops with high mix, make-to-order, or long-cycle assembly. Where part-level kanban is impractical due to variety.

Kanban Sizing

LISTEN · LEARN · LEADWEEK 1 → 13
First 90 daysA calendar of thirteen weeks fills in: listen, learn, then leadThe First 90 days guide
Kanban Calculation Worked Example

Part: Aluminum bracket, used at 20/day on the assembly line.

Replenishment lead time: Machine shop takes 2 days to produce a batch after receiving the kanban signal.

Safety factor: 30% (machine shop has some variability).

Container size: 10 parts per bin.

Kanban formula: K = D × L × (1 + S) ÷ C

K = 20 × 2 × (1 + 0.30) ÷ 10 = 52 ÷ 10 = 5.2 → 6 kanban cards

Total inventory in system: 6 bins × 10 parts = 60 parts maximum.

How it works: The supermarket holds 6 bins. When the assembly line takes a bin, the kanban card goes back to the machine shop. The machine shop produces one bin of 10 and sends it to the supermarket. The system self-regulates: if demand drops, cards circulate slower; if demand rises, cards circulate faster.

Start with More Kanban, Then Reduce

When first implementing kanban, err on the side of too many cards (more inventory). This provides a safety buffer while you learn the system. Then systematically remove cards one at a time. Each card you remove lowers inventory and tightens the system. When removing a card causes a stockout, you have found a problem: solve it (reduce lead time, improve reliability), then remove another card.

Supermarket Design

A kanban supermarket is the physical location where pull inventory is stored. It is not a warehouse. It is a designed, visual, managed buffer with specific rules:

FIFO
SupermarketSloped roller lanes feed parts first in, first out, and the water spider pulls from the front
RuleWhy
Every part has a labeled, fixed locationNo searching: anyone can find any part
Maximum quantity marked visuallyOverproduction is immediately visible (bins overflowing their marked area)
FIFO within each laneOldest parts are consumed first: prevents shelf-life and revision issues
Located between the producing and consuming processesMinimizes transport; the consuming process is the “customer”
Replenishment triggered only by kanban card/signalPrevents push-driven overstock

Integrating Pull with MRP

Pull systems and MRP are not mutually exclusive. In most aerospace factories, both coexist:

ABC
HeijunkaLevel the mix and the volume, so every day looks like the averageThe Heijunka guide
MRP DoesPull Does
Long-range capacity planning (months out)Daily execution on the floor
Material procurement (supplier lead times)Production release timing
Determines WHAT and HOW MANY to produceDetermines WHEN to release to the floor
Runs weekly or daily batchesSignals in real-time based on consumption

MRP plans. Pull executes. MRP says “we need 200 brackets this month.” Pull says “don’t release more until the supermarket signals need.” The combination prevents the overproduction that pure MRP-push creates while maintaining the planning visibility that pure pull cannot provide for long-lead procurement.

The Bottom Line

Pull systems prevent overproduction by linking production directly to consumption. Kanban cards work for repetitive parts, FIFO lanes for sequential flow, and CONWIP for high-mix environments. Size kanban conservatively at first, then systematically tighten. Integrate pull with MRP: let MRP plan, let pull execute. The result is lower WIP, shorter lead time, and a self-regulating production system. Next: Heijunka, leveling the demand signal so pull systems do not get overwhelmed by volume and mix variation.

Frequently asked questions

What is a pull system?

A pull system is a production control method where work is produced only when the downstream process signals a need. Nothing is made until the customer (internal or external) consumes the previous unit. This is the opposite of push production, where work is released based on a schedule or forecast regardless of actual downstream demand.

How do you size a kanban system?

Kanban quantity = (Daily demand × Lead time × (1 + Safety factor)) ÷ Container quantity. For example: 20 parts/day demand, 3-day replenishment lead time, 20% safety factor, container holds 5 parts: K = (20 × 3 × 1.2) ÷ 5 = 14.4 → 15 kanban cards. Each card authorizes production of one container of 5 parts.

Can pull work in aerospace with long cycle times?

Yes, but the pull signal operates at the appropriate level. For long-cycle assembly (days or weeks per position), pull means a CONWIP system: one aircraft exits the line, one enters. For short-cycle components (hours per batch), pull means kanban supermarkets. The principle is the same: produce only when the downstream customer signals need.

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn

Take this to a room

The running order

For anyone designing a pull system. They should leave able to pick between kanban, FIFO and CONWIP, and to size a kanban loop.

7 beats · 13 min
  1. 1

    Three signal types, three situations

    Choosing the wrong one is why pull systems fail in high-mix plants.

    • Kanban: repetitive parts with steady demand.
    • FIFO lane: sequential flow where you just need order and a cap.
    • CONWIP: high mix, low volume; cap the stream rather than the part number.

    Ask the room What is our mix, and which of the three fits it?

  2. 2

    Size the kanban

    One formula: demand times lead time times a safety factor, divided by container size.

    • Lead time is everything: production, transport and waiting.
    • Safety factor typically 1.1 to 1.5 depending on reliability.
    • Every input is measurable. None of them is a preference.
  3. 3

    Start with too many cards

    Deliberately over-size it at first. This is counterintuitive and it is right.

    • More cards means more inventory, which is a buffer while you learn the system.
    • Then remove them one at a time, systematically.
    • It is far easier to remove a card than to recover from a stockout.
  4. 4

    Removing a card is an experiment

    This is the improvement engine, and most kanban systems never run it.

    • Each card removed lowers inventory and tightens the system.
    • When a removal causes a stockout, you have found a real problem.
    • Fix it (lead time or reliability), then remove another.

    Ask the room When did we last remove a card?

  5. 5

    Supermarket design

    A controlled buffer, not a staging area. The difference is the limits.

    • Min and max per item, visible at a glance.
    • Located near the consuming process, not in the warehouse.
    • One container equals one signal, which is why container standardisation matters.
  6. 6

    MRP plans, pull executes

    The integration question always comes up, and this sentence resolves it.

    • MRP decides what is needed and when: the demand signal.
    • Pull decides when it is actually released and made.
    • They are not competing systems, and framing it as a fight is how pull gets rejected.
  7. 7

    The result

    Lower WIP, shorter lead time, and a system that regulates itself.

    • Overproduction becomes structurally impossible: no signal, no production.
    • Problems surface instead of hiding behind inventory.
    • Then heijunka levels the demand signal so the pull system is not overwhelmed by mix.

    Ask the room Which single loop do we build first?