Pacemaker Process
The one process that gets scheduled. Everything else pulls from it.
What is a Pacemaker Process?
The pacemaker process is the single point in a value stream that gets scheduled, setting the pace for everything upstream and downstream. Upstream operations pull material to the pacemaker; downstream operations flow continuously after it. The pacemaker is usually placed at the most downstream continuous-flow process, and its rate is set to takt time so the whole stream stays aligned with customer demand.
The pacemaker process is one of the more subtle pieces of value-stream design and one of the most consequential. The idea: in a well-designed value stream, only one process gets a production schedule, and that one process sets the pace for everything else. Most shops have a schedule at every operation, which is part of why they run push and feel chaotic. Picking one pacemaker and pulling around it is what gives lean value streams their characteristic steady rhythm.
"One process gets the schedule. Everything else pulls or flows. That is the whole architecture."
How a pacemaker process works
The architecture has three pieces. The pacemaker itself is the single scheduled process. Upstream of the pacemaker, operations are linked by pull signals. Downstream of the pacemaker, operations flow continuously. The schedule lives only at the pacemaker, paced to takt time so the pacemaker produces exactly at customer demand rate.
The pacemaker gets placed at the most downstream point in the value stream where continuous flow ends. That is usually final assembly, packout, or finishing. Putting it further upstream means a lot of inventory sits between the pacemaker and the customer, which the pull mechanism cannot reach. Putting it further downstream is impossible if downstream is flowing continuously; the pacemaker has to be at the boundary between the pulled (upstream) and flowed (downstream) sections of the stream.
The mechanism at the pacemaker is usually a heijunka box, a slotted board with cards organized by pitch interval. Each card tells the pacemaker what to build at each interval. The operator pulls the next card, the pacemaker produces that part, and the consumption pulls material upstream through the value stream. The cards in the heijunka box are the only schedule on the floor. Everything else runs from signals.
The other piece is the order release pattern. New customer orders arrive at the front office and get translated into kanban cards or production instructions that enter the pacemaker's box in the pattern that fits the leveling plan. Sales does not push individual orders to the floor. The orders feed the box, the box paces the pacemaker, and the pacemaker paces the stream. The shop floor never sees the order book directly. It sees only the cards.
Where a pacemaker process fits on the shop floor
Picture a small fab shop running steel parts that go through laser cutting, brake forming, welding, and final assembly. Without a pacemaker, every operation runs from its own slice of the MRP schedule, which the shop reruns weekly. The result is constant rescheduling and inconsistent WIP between operations.
The shop designates final assembly as the pacemaker. A heijunka box gets installed next to final assembly, sized to a 30-minute pitch. Cards for each customer order enter the box in a leveled pattern. The final assembly cell runs from the box. The weld station now pulls from a small supermarket of welded parts, refilling whatever final assembly consumed. The brake pulls from a supermarket of cut parts, refilling whatever weld consumed. The laser pulls from raw stock, refilling whatever brake consumed.
Within a quarter, the schedule no longer gets rerun. The pacemaker holds steady, the upstream operations pull at the same steady rhythm, and the shop's WIP drops by roughly half. The owner stops spending time on rescheduling because the schedule lives only at one place and is set monthly, not weekly. The rest of the shop runs on the rhythm the pacemaker is keeping.
Common mistakes with pacemaker processes
- Picking the wrong location. The pacemaker belongs at the most downstream point of continuous flow. Too far upstream and the downstream cannot pull from it.
- Scheduling more than one process. Multiple schedules drift. The whole point of a pacemaker is that the schedule lives in one place.
- Setting pace to capacity, not demand. The pacemaker runs at takt, not at what the equipment could do. Running faster than takt creates overproduction.
- No heijunka box at the pacemaker. Without a physical sequencing tool, the pacemaker reverts to whatever the next loud order is. The box is what makes the schedule visible.
- Treating the pacemaker as a bottleneck. They can be the same, but the choice of pacemaker is about flow architecture, not capacity. Picking based on bottleneck logic leads to a pacemaker too far upstream.
Pacemaker process and related Lean tools
The pacemaker is paced to takt time and sequenced by heijunka at a pitch interval that fits the production mix. Upstream of the pacemaker, the stream runs as a pull system with kanban signals refilling supermarkets. Downstream of the pacemaker, the stream uses continuous flow to move work from the pacemaker through final operations without a separate schedule.
Related terms
One-Piece Flow
One part, one process, one move at a time. The extreme end of flow.
Read termProduction Leveling
A steady shop instead of a heroic one. Wobbles stay in the order book.
Read termPush System
Make to a schedule. Hope the next station can absorb it. Usually it cannot.
Read termSupermarket
A sized store. The customer pulls. The supplier refills what got taken.
Read term