Production Leveling: A Steadier Mix, a Workable Plan

Home » Resources » Production Leveling: A Steadier Mix, a Workable Plan

Estimated reading time: 9 minutes

Monday’s large order fills the line. By Wednesday, another product is running short, so the team interrupts the batch, changes tools and rearranges everything behind it. The factory is working hard, but each department receives a different surge of work.

Production leveling, also called heijunka, means smoothing the volume and product mix made over a chosen period. Instead of passing every fluctuation in incoming orders straight to the shop floor, you build a more regular pattern that still meets customer needs.

The opportunity is a steadier production day: fewer abrupt changes in workload, more frequent replenishment of the products customers need, and less reliance on enormous batches. But an even number of pieces is not necessarily an even amount of work. The pattern also has to fit your machines, setup times and delivery commitments.

That is where SkyPlanner APS helps. You decide the production priorities; its scheduling AI, Arcturus, calculates the sequence against the resources and constraints you have configured. A leveling goal becomes something you can assess against a real production schedule, rather than an attractive pattern that the factory cannot follow.

What production leveling changes

There are two connected decisions in heijunka:

• Volume leveling: spreading the quantity to be made more evenly across time, rather than copying each day’s order intake.
• Mix leveling: making the required product types more regularly in smaller batches, rather than completing one enormous run before starting the next product.

A factory can level volume without leveling mix. Producing the same total every day will not help a customer waiting for Product B if the entire week is devoted to Product A.

Mix leveling shortens that wait by bringing B back into the pattern more often. It also gives upstream processes a steadier requirement for B’s components. The trade-off is more frequent changeovers, which must fit within the available production time.

Leveling does not mean refusing to change when demand changes. It absorbs short-term variation within an agreed planning period; sustained changes in demand require a revised production rate or mix.

A production leveling example: count minutes as well as pieces

Imagine a product family with weekly requirements of 300 units of A, 150 of B and 150 of C. Over five production days, that is 600 units, or 120 units per day.

One possible daily mix is 60 A, 30 B and 30 C. This brings each product back into production daily instead of leaving B and C until the end of the week.

Now check the time required at the shared resource:

• A takes two minutes per unit: 60 units need 120 minutes.
• B takes three minutes per unit: 30 units need 90 minutes.
• C takes five minutes per unit: 30 units need 150 minutes.
• Assume three setups of 15 minutes each: another 45 minutes.

The daily requirement is 405 minutes, including setups. With 420 available production minutes, it fits on this simplified resource calculation, leaving 15 minutes of headroom.

The same daily total can tell a very different story. A day with 30 A, 30 B and 60 C still contains 120 units, but needs 495 minutes, including the same setup allowance. Equal unit counts have hidden an overload.

Use the leveled mix as a starting point, then check the workload at the resources that actually constrain production. Include setup requirements and the timing of preceding operations. The first mix fits the example’s time budget; it is not proof that materials, people and every other operation will be ready.

This distinction matters especially in high-mix production. Leveling a repeatable family can be useful even when individual products have different run times. Treating unlike units as interchangeable capacity cannot.

Where does the variation go?

If customers order unevenly but production runs steadily, something must absorb the difference. Decide what that is before committing to the pattern.

For make-to-stock products, it may be finished inventory. A controlled buffer serves short-term peaks while production replenishes at a steadier rate. Check the required service level, shelf life, stock cost and obsolescence risk. Leveling is not permission to build unwanted products just to keep the line busy.

For configurable products, it may be common semi-finished stock. You can replenish a standard base regularly and complete the customer-specific work later, provided the remaining operations fit the promised response time.

For make-to-order work, it may be time within the customer’s delivery window. If manufacturing can finish comfortably before the promise date, orders can sometimes wait for a planned production slot. If every order is already urgent, that room does not exist.

A permanent rise in demand cannot be absorbed indefinitely by running down stock or extending a queue. Revisit the production rate and capacity. The useful question is not simply “Can we smooth this week?” but “Can we keep this pattern and still deliver what we have promised?”

How to introduce heijunka without creating more disruption

Start with a product family that shares a meaningful production route and has enough recurring demand to support a pattern. Trying to put every one-off job into the same repeating cycle usually obscures the decisions you need to make.

Choose a realistic repetition interval

Decide how often the family and its major products should return to production. Daily replenishment may be attractive, but the time needed for changeovers determines whether it is feasible. A longer cycle may be the right starting point while you reduce setups.

Check the proposed interval against customer delivery requirements and the buffer you are willing to hold. A convenient factory rhythm is of little use if it repeatedly leaves the customer waiting.

Make the time budget honest

Allow for processing, setups and known unavailable time. Use the actual product mix, not a single average cycle time that hides the slower items. Check the resources the family shares with other work, too.

If more frequent product changes consume the capacity you need for output, reduce setup time, adjust the batch pattern or add justified capacity. Do not assume that leveling itself makes changeovers faster.

Agree how exceptions enter the plan

Decide who can change priorities and what qualifies as an exception. Keep some practical room for the variability your process experiences. Filling every available minute on paper makes even a small interruption difficult to recover from.

After a change, review its effect on the rest of the schedule rather than simply inserting another urgent job at the front. This is where manual queue maintenance becomes expensive: the consequence rarely stops at one workstation.

Review delivery, stock and stability together

Watch whether products are available when needed, whether inventory is growing, whether the intended mix is being completed, and how often production has to abandon the pattern. A smoother release pattern is useful only if it supports customer service without moving the problem into excess stock or late orders.

What a heijunka box does, and what it does not

A heijunka box is a visual tool for distributing production signals over time. Typically, product types occupy rows and time intervals occupy columns. Kanban cards show the work to release in those intervals. In paced systems, the release interval is often expressed as pitch: takt time multiplied by the pack-out quantity.

The box makes a chosen pattern visible. It does not establish that the required machines, materials and people will be available. Nor is production leveling the same as line balancing: line balancing distributes work among stations or operators, while leveling smooths volume and mix over time.

When routes, durations and priorities vary, the leveling pattern needs the support of detailed scheduling. SkyPlanner’s role here is to calculate and maintain that schedule, not to replace your production policy with an automatic heijunka-box rule.

Use SkyPlanner to make the pattern workable

A useful leveling policy says what you want production to achieve. SkyPlanner helps you see how the work fits into the time and resources available to achieve it.

Arcturus schedules operations using workstation capacity, shifts, operation dependencies and the priorities you set. Processing and setup durations define the time required. With material-aware scheduling enabled, material availability also affects the calculation. The Gantt view shows the resulting work queues and timing across workstations.

That gives you a practical way to manage the changes that disrupt a leveled plan:

• A priority order arrives: set its priority and review the effect on the remaining work.
• A resource loses available time: record the change and let Arcturus recalculate around the updated capacity.
• A near-term sequence needs stability: use scheduling locks to protect decisions while other work is replanned.

The benefit is not merely a cleaner chart. You spend less of the day moving individual jobs between queues, and more of it deciding whether the production mix, delivery commitments and available capacity still agree. SkyPlanner integrates with any ERP or MES through its open REST API, so better scheduling can build on your existing order and production data.

A customer example: predictable production with room for change

Opes Corporation makes specialty products to stock, generally against predictable three-month customer commitments. That is a useful setting for a regular production rhythm, yet product-development runs and urgent small orders still have to fit.

In its SkyPlanner customer story, Opes describes how the capacity view and updated production plan show the effect of those additions on completion and delivery times. The team can see when jobs will finish and make schedule changes faster than before.

That is the flexibility a regular production rhythm needs: keep the predictable base of work visible, and understand what an exception will change before it disrupts the rest of the queue.

Build a steadier production day around a schedule you can use

Production leveling works when the recurring mix, changeovers and demand buffer make sense together. In a variable factory, use it where repetition helps, then schedule the actual work against actual constraints.

Choose SkyPlanner when maintaining that schedule is consuming the time you need for production decisions. Arcturus handles the scheduling calculation while you retain control of priorities and protected work.

Book a SkyPlanner demo to discuss one recurring product family, its setup requirements and a recent disruption. See how your production priorities translate into a schedule, and what changes when an urgent order or lost shift enters the picture. If you want to explore first, try SkyPlanner with demo data.