How Do Multi-Product Batch Pilot Plants Show Equipment And Storage Impacts On Production Scheduling?

Multi-product batch unit operations pilot plants demonstrate that equipment constraints and intermediate storage directly determine production schedules, throughput, and profitability. Shared reactors, separators, mixers, and downstream units cannot always operate independently; their cycle times, capacities, cleaning requirements, and transfer rules determine when each batch can start. Pilot plants make these relationships visible by allowing operators to compare synchronized schedules with schedules that use unlimited, finite, or no intermediate storage.

The central lesson is that storage decouples process stages. Without sufficient intermediate storage, upstream and downstream equipment must remain tightly synchronized, often creating idle time and limiting throughput; with appropriate storage, equipment can operate closer to full capacity, although storage costs, vessel limits, product stability, and extra handling introduce new constraints.

How Pilot Plants Expose Scheduling Constraints

Shared equipment creates competing demands

In a multi-product pilot plant, several products may require the same reactor, separator, mixer, filter, or distillation column. Only one operation can use that shared asset at a time, so each product campaign competes for the same processing capacity.

A schedule must therefore account for batch duration, equipment availability, product sequence, transfer time, cleaning, and changeover requirements. The resulting plan is more restrictive than simply adding the processing times for each product.

Cycle sequencing affects total throughput

The order in which products are processed determines how much equipment remains idle between operations. A sequence such as A-B-A-B may be required when an intermediate must move immediately from a reactor to a separator, but that sequence can prevent either unit from operating at its most efficient rhythm.

Alternative campaign sequences can reduce waiting and changeover losses. In an illustrative pilot-plant comparison, an ABCABC sequence produced a shorter cycle per batch set than a CBACBA sequence, allowing more batches within a fixed operating period.

Gantt charts make idle time visible

Pilot systems allow students and engineers to map each recipe onto a Gantt chart. The chart shows when reactors, separators, storage vessels, and operators are occupied or waiting.

This distinguishes productive processing time from non-productive periods such as discharge, cleaning, sterilization, catalyst regeneration, and transfer. It also shows whether the plant is limited by a single bottleneck stage or by poor coordination between stages.

How Intermediate Storage Changes the Schedule

No Intermediate Storage forces synchronization

Under a No Intermediate Storage (NIS) policy, an intermediate must be processed as soon as it leaves the upstream operation. The reactor and separator therefore behave almost like one combined operation.

If the separator is unavailable when the reactor finishes, the reactor must wait. If the reactor has not completed the next batch when the separator is ready, the separator becomes idle. These forced handoffs reduce utilization and can require fixed alternating sequences such as A-B-A-B.

NIS is appropriate when intermediates are unstable, hazardous, highly perishable, or otherwise unsuitable for storage. Its scheduling cost is reduced flexibility.

Unlimited storage decouples process stages

Under Unlimited Intermediate Storage (UIS), intermediates can remain available until the downstream unit is ready. The reactor can start another batch instead of waiting for the separator, and the separator can process stored material according to the most efficient sequence.

This increases scheduling flexibility and can allow the reactor to operate near full capacity. The benefit is greatest when the upstream and downstream cycle times differ substantially or when product campaigns require different processing sequences.

UIS is primarily a modeling case because real facilities rarely have unlimited tank capacity. It establishes the maximum scheduling flexibility against which more realistic policies can be compared.

Finite storage reflects the practical operating case

Finite Intermediate Storage (FIS) limits the volume, number, or availability of storage vessels. It provides some decoupling while preserving the physical constraints found in an actual pilot or production facility.

When all storage vessels are full, the upstream operation must stop or wait. When storage is empty, the downstream operation may become idle. The schedule must therefore control both equipment timing and inventory levels.

FIS experiments show that adding one storage vessel may remove a major bottleneck, while additional vessels may provide little further benefit if another unit has become the limiting resource.

How Equipment Limits Shape Production Plans

Vessel capacity limits batch size

A shared reactor must be large enough to accommodate the largest governing batch volume among the products it processes. Batch volume depends on the product target, the reactor-volume requirement per unit mass, and the number of batches assigned to that product.

For product (x), the approximate number of batches during its campaign is:

[ N_x = \frac{t_x}{t_{\text{cycle},x}} ]

The required batch volume can then be estimated from the production target and the product-specific reactor-volume requirement. After batch counts are rounded to whole numbers, the largest resulting batch volume becomes the limiting vessel-size condition.

Integer batches create real scheduling effects

Campaign durations may be calculated as continuous values during planning, but production requires whole batches. Rounding the batch count can create unused capacity, additional campaign time, or a larger required vessel.

Pilot plants demonstrate this difference clearly. A mathematically balanced plan may not be operationally feasible once batch counts, vessel capacities, transfer limits, and setup times are converted into discrete activities.

The bottleneck determines overlapping cycle time

When reaction, separation, and drying operations overlap, the overall repeating cycle is generally governed by the slowest required stage or the most constrained shared resource.

For example, a reactor may finish a batch quickly but remain blocked if the separator is full. Conversely, a fast separator cannot improve total output if the reactor or dryer supplies material more slowly. Storage can reduce these dependencies, but it cannot eliminate a true capacity bottleneck.

How Campaign Sequence Influences Output

Product order changes equipment utilization

In a multi-product plant, changing product order changes the timing of both processing and cleaning. A sequence that appears efficient for the reactor may create excessive waiting at the separator or require more frequent product changeovers.

Pilot-scale trials allow users to compare candidate sequences under identical operating conditions. They can measure total makespan, equipment idle time, number of changeovers, intermediate inventory, and completed batches.

Shorter repeating cycles increase production capacity

If one campaign sequence completes a set of batches in 12.5 hours while another requires 13.5 hours, the difference compounds over a long operating period. Over 500 hours, the shorter sequence could support approximately 40 batch sets compared with approximately 37 for the slower sequence, subject to rounding and the exact operating assumptions.

The value of sequence optimization is therefore not limited to saving a few minutes in one cycle. It can determine whether the facility completes an additional batch campaign within the available production horizon.

Storage allows more flexible campaign patterns

With sufficient intermediate storage, the plant does not need to force every upstream batch to follow the downstream product order immediately. Reactors can produce campaigns in a sequence that minimizes their own changeovers, while separators or distillation units process available intermediates in a different sequence.

This flexibility can increase throughput, but the schedule must still respect intermediate stability, storage capacity, vessel compatibility, and product-priority requirements.

How Pilot Plants Teach the Scheduling Trade-Off

Physical experiments connect models to operations

Unit operations pilot plants convert abstract scheduling variables into observable events. Operators can see a reactor waiting for a vessel, a separator running below capacity, or a storage tank preventing the next upstream batch from starting.

This makes linear programming constraints and batch scheduling concepts easier to validate. The physical system also exposes practical delays that are often omitted from simplified calculations.

Measurements support quantitative comparison

A pilot exercise can compare schedules using measurable criteria such as:

Total campaign makespan
Number of completed batches
Reactor and separator utilization
Intermediate inventory levels
Storage-vessel occupancy
Cleaning and transfer time
Product yield and off-cut generation
Unit production cost

These measurements show whether a schedule improves actual plant performance or merely shifts the bottleneck elsewhere.

Multi-pass operations reveal storage limitations

In batch distillation or other multi-pass processes, material that does not meet final purity may be collected as an intermediate off-cut and reprocessed later. The campaign then depends on column capacity, reflux profiles, task sequencing, and the number and volume of available storage vessels.

A larger storage capacity may improve recovery and scheduling flexibility, but it cannot compensate for insufficient column capacity. Conversely, a high-capacity column may still be underused if off-cuts have nowhere to go.

Understanding the Trade-offs

More storage improves flexibility but adds cost

Intermediate storage can reduce equipment waiting and increase reactor utilization. It also requires additional tanks, floor space, transfer equipment, controls, cleaning, and inventory management.

Storage may therefore improve throughput without improving overall economics if its capital and operating costs exceed the value of the additional production.

No storage reduces inventory but increases downtime

NIS avoids intermediate inventory and can be necessary for unstable materials. However, it couples equipment tightly and makes every upstream or downstream delay propagate through the schedule.

A small interruption in one unit can therefore create idle time across the connected process.

Splitting campaigns can reduce storage demand

Shorter campaigns may prevent storage vessels from filling and can make material flow easier to manage. The disadvantage is that each campaign split may introduce another cleaning and changeover cycle.

The resulting trade-off is between inventory capacity and changeover downtime. The best schedule balances both rather than minimizing only one.

High purity can increase scheduling complexity

If a single pass cannot meet purity specifications, multiple passes may be required. Reprocessing creates additional tasks, intermediate streams, and storage requirements.

The schedule must balance purity, yield, reflux operation, vessel capacity, and campaign duration. Maximizing purity in every pass is not automatically the same as maximizing total production or profit.

The fastest schedule may not be the lowest-cost schedule

Reducing cycle time can increase output, but it may also require more cleaning, higher storage capacity, additional labor, or less efficient operating conditions. Unit production cost depends on both productive processing and non-productive time.

Pilot plants help identify the operating point where yield gains justify the added processing or cleaning time.

Making the Right Choice for Your Goal

The appropriate storage policy and campaign sequence depend on the material properties, equipment configuration, and business objective.

If your primary focus is maximum throughput: Use pilot-plant trials to compare campaign sequences and introduce enough intermediate storage to keep shared equipment operating near its capacity.
If your primary focus is material stability or safety: Model a no-storage policy and design the schedule around immediate transfers, tightly matched cycle times, and rapid response to delays.
If your primary focus is realistic facility planning: Evaluate finite storage with actual vessel volumes, transfer times, cleaning requirements, and whole-batch constraints.
If your primary focus is minimum capital investment: Compare the value of added storage against the throughput lost through equipment synchronization and idle time.
If your primary focus is lowest unit production cost: Include reaction, separation, transfer, cleaning, regeneration, changeover, and storage costs in the schedule evaluation.
If your primary focus is reactor or pilot-plant sizing: Calculate integer batch volumes for every product and size the shared vessel against the largest governing batch requirement.

A multi-product batch pilot plant turns scheduling theory into direct operational evidence, showing exactly how equipment constraints and intermediate storage determine what the facility can produce.

Summary Table:

Scheduling factor	Operational impact	Key trade-off
Shared equipment	Creates competition between products and limits simultaneous operations	Higher utilization may increase waiting and changeovers
No intermediate storage	Forces immediate transfers and tight synchronization	Lower inventory, but more downtime and schedule disruption
Unlimited storage	Decouples upstream and downstream equipment	Maximum flexibility, but mainly a theoretical case
Finite storage	Provides practical buffering between process stages	Flexibility is limited by tank volume and vessel availability
Batch and vessel capacity	Determines feasible batch size and required equipment volume	Whole-batch constraints can create unused capacity
Campaign sequence	Changes makespan, cleaning time, and equipment utilization	A faster sequence may require more changeovers
Multi-pass processing	Adds reprocessing tasks, off-cuts, and storage requirements	Higher purity may reduce throughput or increase cost
Schedule evaluation	Compares makespan, batches, utilization, inventory, yield, and cost	The fastest schedule may not be the most economical

Optimize Your Pilot-Plant Schedule with LABPARK

Need to evaluate equipment bottlenecks, batch sequencing, or intermediate-storage capacity before scaling up? Contact LABPARK to discuss your requirements.

LABPARK provides Educational and Vocational Unit Operations Pilot Plants for universities, research institutes, and enterprises. Our modular solutions support practical studies in chemical engineering, bioprocess and biotechnology, and environmental and water treatment. Use realistic pilot-scale equipment to compare no-storage, finite-storage, and unlimited-storage scenarios, measure utilization and throughput, test campaign sequences, and identify the most cost-effective configuration for your process.