Transfer Batch vs. Process Batch

Pattern: A named solution to a recurring problem.

Separate the quantity processed between setups from the quantity moved downstream at one time, so the system can protect scarce setup capacity and still keep flow moving.

Also known as: batch splitting; lot splitting; overlapping batches.

A process batch is the quantity a resource completes before changing setup. A transfer batch is the quantity moved to the next operation. Traditional batch-and-queue practice often treats them as the same number. TOC treats that equality as a policy choice, not a law of production. Once the two are separated, a plant can keep a large process batch where setup time would consume scarce constraint capacity and still move smaller transfer batches downstream as soon as they are ready.

Context

Transfer-batch policy belongs in production control, especially in systems using Drum-Buffer-Rope, Simplified Drum-Buffer-Rope, or a DBR-adjacent release rule. The issue appears whenever work moves through dependent operations in lots: fabrication to welding, machining to heat treat, testing to assembly, or a supplier shipment into a plant. The batch that protects a setup decision at one resource may be too large for the next resource’s flow need.

The distinction depends on knowing where capacity is scarce. At a Capacity-Constrained Resource or true internal constraint, setup time can consume throughput because the resource has little protective capacity. At most non-constraints, the same extra setup may consume idle time the system already has. That is why TOC practitioners don’t ask whether small batches are good or bad in general. They ask where the batch sits relative to the constraint, what the setup consumes, and whether waiting for the full batch delays flow.

The TOCICO Dictionary defines a process batch as the quantity completed at a workstation before switching work or setup, and a transfer batch as the quantity completed before that output moves to the next workstation. Both entries make the same certification-grade point: in batch-and-queue environments, production lead time can fall sharply when the transfer batch is smaller than the process batch.

Problem

A plant has accepted that the constraint sets the pace, but its batching policy still ties downstream flow to local setup economics. A non-constraint finishes a small quantity that the next operation could use immediately, then waits until the whole process batch is complete before moving anything. The next operation sits idle, the buffer burns time, and the plant calls the delay “normal lead time.”

The standard objection is cost. Smaller movements appear to require more handling, more setups, or more paperwork. Cost-world reporting then translates those local activities into a higher unit cost, even when no new labor, machine, or operating expense has been added. The plant protects an accounting number and pays with longer lead time, higher work-in-process, and more risk that the constraint or the customer due date won’t be protected.

Forces

• Setup time matters differently at the constraint and at non-constraints. A setup at the constraint can replace throughput-producing time; a setup at a non-constraint often consumes protective capacity the system owns but doesn’t need at that moment.

• Flow depends on overlap. If each operation waits for a whole process batch before transferring anything, the routing becomes a relay race with long handoffs rather than a flow with overlapping work.

• The next operation needs useful work, not a locally efficient batch. A downstream resource can start protecting the constraint or the shipping buffer as soon as the first transfer batch arrives.

• Material handling is visible while waiting time is often invisible. The extra move shows up on the floor; the hours lost in queue and wait time are absorbed into “lead time” unless the system measures them directly.

• Cost-world measures favor large batches. Economic batch quantity logic spreads setup cost across more units, but it doesn’t ask whether the extra waiting increases inventory or delays throughput.

Solution

Choose the process batch for the setup economics of the resource, and choose the transfer batch for the flow need of the next operation. The two numbers may be equal, but they don’t have to be. Treat equality as a decision that must earn its place.

At the constraint or CCR, protect scarce setup time first. If a furnace, coating line, press, or CNC cell loses a meaningful portion of system throughput every time it changes over, the process batch may need to remain large enough to make the setup worthwhile. That doesn’t mean downstream work must wait for the whole lot. As soon as a usable transfer quantity is complete, move it.

At non-constraints, bias transfer batches smaller. A non-constraint has protective capacity by definition; it can often afford shorter runs, more frequent transfers, or extra handling if those moves protect the constraint’s schedule or the shipping buffer. The question is not whether the non-constraint looks efficient. The question is whether the system ships sooner, carries less work-in-process, and keeps the constraint fed.

The rule is especially clean under DBR. The drum defines what the constraint needs and when. The rope limits release to what the drum and buffers can absorb. Smaller transfer batches let the work already released move through the route without waiting for local batch completion. Buffer Management then tells whether the policy is working: fewer repeated red events, fewer buffer holes caused by waiting behind large lots, and less expediting to recover from avoidable queue time.

How It Plays Out

The Goal’s first batch split. Goldratt and Cox introduce the mechanism before they name the full accounting argument. A hot order must move from fabrication to welding before the end of the day. Under the old policy, material handling would wait for the entire batch. The local move changes: the first usable quantity is transferred on the hour, so welding can start while fabrication keeps working. The operation hasn’t added capacity. It has changed the overlap between dependent steps.

Heat treat at the constraint. Later in the UniCo story, heat treat remains sensitive because setup and loading time at the furnace can consume scarce constraint capacity. The process batch is still shaped by furnace loading, temperature cycles, and setup economics. The transfer batch is smaller: work is sorted, stacked, and moved so the next useful quantity can travel as soon as it protects the priority schedule. That is the distinction in operational form. The furnace doesn’t have to run tiny lots to make downstream flow faster.

A market-constrained make-to-order shop. Schragenheim’s S-DBR treatment makes the same rule less theatrical. In a shop where market demand is the primary constraint, the first implementation move is to choke release to the production buffer horizon and then attack batching policy. The customer order quantity may become the batch, or the process batch may be reduced where setup capacity allows it. Transfer batches are challenged because large manufacturing orders often hide urgent customer quantities inside less urgent stock quantities. Small transfers let the urgent work move without turning the whole plant into a locally optimized batch queue.

Consequences

Benefits:

• Lead time falls without added capacity. Overlap cuts queue and wait time between dependent operations. The plant can ship sooner even when every resource’s net processing time is unchanged.

• Work-in-process falls. Smaller transfers reduce the amount of material waiting for a full lot to finish before the next operation can begin.

• Constraint protection improves. If a buffer is at risk because a needed job is trapped inside a large upstream batch, smaller transfers can move the needed quantity before the full process batch is complete.

• The financial reading becomes cleaner. Throughput Accounting separates the real operating-expense question from the unit-cost calculation. If no new resource is added, the extra setup or movement at a non-constraint may not raise operating expense at all.

• The policy exposes false bottlenecks. The TOCICO Dictionary names equality between process batch and transfer batch as one policy that can make resources look like bottlenecks. Once the policy is removed, the apparent bottleneck may disappear.

Liabilities:

• The constraint can be damaged by indiscriminate batch cutting. If smaller process batches force extra setups at the true constraint, the system can lose throughput. The rule is to split transfer batches first and shrink process batches only where setup capacity can absorb it.

• Material handling and paperwork may need redesign. A plant built around once-per-batch moves may need different carts, travelers, labels, scanning rules, or staging areas before small transfers are practical.

• Large process equipment may impose physical minimums. Molds, furnaces, tanks, kilns, and coating lines sometimes have minimum charge sizes. The process batch may be fixed by physics even while the transfer batch remains flexible.

• The cost-world argument returns quickly. Cost-World Thinking will show higher unit cost if it allocates setup time over fewer units. If the organization still rewards local efficiency, the old batch policy will come back.

• Too many tiny transfers can create noise. One-piece flow is not automatically the TOC answer. The right transfer batch is the smallest useful quantity that protects the next operation without burying the floor in handling work.

Complements: Buffer Management — Buffer Management shows whether smaller transfer batches are protecting flow: fewer red events and smoother buffer penetration mean the batch policy is doing its job.

Complements: Throughput Accounting — Throughput Accounting explains why more setups at non-constraints need not raise operating expense in the short run, while shorter lead time and lower inventory can improve the system's financial result.

Corrupted by: Cost-World Thinking — Cost-world thinking welds transfer batch and process batch together because it reads extra setups and material moves as unit-cost penalties rather than as flow decisions.

Corrupted by: Efficiency Trap — The Efficiency Trap pushes large local batches even when smaller transfers would keep downstream work moving and protect the constraint.

Depends on: Capacity-Constrained Resource (CCR) — The process batch is most sensitive at the constraint or CCR because setup time there consumes scarce capacity; non-constraints can usually afford smaller transfer batches and more movement.

Implements: Drum-Buffer-Rope (DBR) — Transfer-batch policy is one of the operating rules DBR uses to protect the drum: work can move downstream before the whole process batch is complete, so the constraint's output is not trapped behind local batching convenience.

Implements: Subordination — Splitting the transfer batch is a physical form of subordination: non-constraints give the next operation what the system needs now rather than waiting for their own batch economics to finish.

Sources

• Cox, TOCICO Dictionary (2nd ed., 2012), entries “process batch,” “transfer batch,” “bottleneck resource,” “policy constraint,” “make-to-order injections,” and “make-to-availability injections,” provide the certification-grade definitions and connect batch policy to lead time, apparent bottlenecks, and TOC logistics injections. The Dictionary is distributed through TOCICO membership and doesn’t carry an Open Library record.

• Goldratt and Cox, The Goal (1984; revised editions through 2004), Chs. 17, 23, 28, 29, 31, and 37, supply the worked narrative: hourly transfer of a hot order, split-and-overlap heat-treat batches, repeated batch-size cuts, the cost-accounting objection, and the later recognition that optimum batch sizes are one of the cost-world assumptions the plant had to reject.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 7 (Blackstone, “Theory of Constraints: A Status Report”), states the transfer-batch / process-batch distinction in DBR terms, names overlapping operations as a lead-time move, and reports DBR cases where small transfer batches were part of the implementation package.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 8 (Srikanth, “DBR, Buffer Management, and VATI Flow Classification”), connects batch size to bottleneck exploitation, V-plant divergence, process-batch decisions at the constraint, and the rule that small batches are constrained only when the added setups create a capacity problem.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 9 (Schragenheim, “From DBR to Simplified-DBR for Make-to-Order”), treats batching policy as part of S-DBR implementation: choke release to the production-buffer horizon, reduce or abolish inherited batching policies, and use Buffer Management priority rather than local batch economics to drive execution.