Campaign scheduling and operation sequencing can materially change total throughput in a multi-product batch pilot plant. When shared mixers, reactors, separators, or cleaning systems are used in different sequences, the timing of changeovers and handoffs determines equipment idle time and total cycle duration. For example, a sequence with a 12.5-hour cycle can produce approximately 40 batches in 500 hours, while a 13.5-hour sequence produces only about 37 batches.

The best sequence is not simply the one that processes each product fastest in isolation; it is the one that minimizes waiting, changeover losses, and bottleneck delays across the entire plant.

Why Sequence Determines Throughput

Shared equipment creates scheduling dependencies

In a multi-product plant, several products compete for the same equipment. A reactor may be waiting for a mixer, while a separator is waiting for reactor output, and a cleaning system may be required before the next product can begin.

The sequence determines whether these units operate continuously or spend time waiting for one another.

Changeovers add non-productive time

Switching between products often requires cleaning, sterilization, reagent loading, sensor calibration, and equipment preparation. These activities do not directly create product, but they extend the campaign make-span.

A sequence that causes frequent or difficult changeovers can therefore reduce throughput even when the individual processing times are unchanged.

Sequence affects plant cycle time

If a complete product pattern takes (t_{\text{cycle}}) hours, the approximate number of completed cycles over an operating period (T) is:

[ N \approx \frac{T}{t_{\text{cycle}}} ]

For a 500-hour operating period:

A 12.5-hour sequence supports approximately 40 cycles.
A 13.5-hour sequence supports approximately 37 cycles.

The difference comes from only one hour per sequence, but that loss accumulates across the full operating horizon.

How Operation Order Creates or Removes Idle Time

Synchronization between serial operations

Pilot plants commonly use serial steps such as pretreatment, reaction or fermentation, separation, and packaging. The effective plant throughput is constrained by how well the cycle times of these operations are synchronized.

If an upstream reactor finishes before the separator is available, the reactor may remain idle or the product may require intermediate storage. If the separator finishes first, it may wait for the next reactor batch.

Product-specific processing times matter

Products A, B, and C may require different reaction, separation, cleaning, or loading times. Consequently, the same equipment sequence may not perform equally well for every campaign arrangement.

A sequence such as ABCABC may align the different operation times more effectively than CBACBA, producing a shorter overall cycle and less equipment waiting.

Bottlenecks propagate through the plant

A delay at one shared unit can affect all downstream operations. For example, if a separator is the limiting unit, increasing reactor utilization alone will not increase total output unless the separation schedule is also improved.

This is why throughput analysis must consider the complete route rather than optimizing each unit independently.

The Role of Batch Size and Campaign Structure

Longer campaigns can reduce changeover frequency

Running several batches of the same product consecutively may reduce the number of product-to-product cleanings. This can improve equipment availability and shorten the total campaign duration.

However, long campaigns may require more intermediate or finished-product storage and can reduce flexibility if demand changes.

Splitting campaigns increases turnaround burden

Dividing a campaign into many short runs may reduce storage requirements, but it introduces more cleaning and preparation events. The added turnaround time can outweigh the apparent scheduling benefit.

This is particularly important in multipurpose pilot plants where cross-contamination prevention requires thorough cleaning between products.

Batch cycle time includes more than processing

A practical batch cycle should include filling, active processing, emptying, cleaning or sterilization, and recharging. A useful planning relationship is:

[ \text{Activity Time}

\frac{\text{Unit Processing Time}\times\text{Batch Size}+\text{Setup Time}} {\text{Efficiency}} ]

Here, setup time includes preparation activities, while efficiency reflects how closely operators achieve the standard execution time.

Storage and Equipment Coupling

No intermediate storage requires tight sequencing

When no storage exists between a reactor and separator, the two units must be closely synchronized. A fixed alternating pattern such as A-B-A-B may be necessary, even if it is not the theoretically fastest sequence.

This constraint can reduce capacity because one unit may be forced to wait for the other.

Buffers can decouple operations

Intermediate storage allows an upstream unit to continue operating while a downstream unit completes another task. This can reduce idle time and improve utilization of the reactor or mixer.

The benefit is not unlimited: storage adds space, handling requirements, residence-time considerations, and potentially additional quality-control demands.

Storage changes the optimization problem

Without storage, the priority is synchronization. With storage, the schedule can prioritize utilization of the most constrained equipment while using the buffer to absorb timing differences.

Therefore, the best sequence depends not only on processing times but also on available storage capacity and allowable inventory.

Planning the Campaign and Equipment Capacity

Allocate time by product

A campaign plan should define the available operating period and allocate time among products:

[ t_A+t_B+t_C=T ]

For each product, the expected number of batches can be estimated from its campaign time and batch cycle:

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

In practice, batch counts must be converted to whole batches, which can change the required equipment volume and the final schedule.

Size equipment for the limiting batch condition

The required batch volume for each product depends on its target production, process-specific volume requirement, and number of batches. After rounding batch counts to practical whole numbers, the largest required batch volume governs the shared vessel size.

This step matters because an apparently efficient schedule may be infeasible if one product requires more reactor or separator capacity than the equipment provides.

Include auxiliary resources

The schedule should include not only primary equipment but also cleaning systems, operators, utilities, and maintenance windows. A reactor may be available in theory but unusable in practice if the cleaning-in-place system or trained operator is unavailable.

Process modeling combined with scheduling simulation is useful for exposing these resource conflicts before operating the pilot plant.

Understanding the Trade-offs

Maximum throughput versus flexibility

A sequence optimized for throughput may favor long product campaigns and few changeovers. That can reduce flexibility when product targets, priorities, or operating conditions change.

A more flexible schedule may accept some idle time or additional cleaning to support smaller campaigns and faster response.

Fewer changeovers versus higher inventory

Reducing changeovers often means producing larger lots of one product before switching. This can increase intermediate or finished-product inventory and may exceed available storage.

The correct choice depends on whether the dominant constraint is equipment time, storage, contamination control, or demand responsiveness.

Shorter batch time versus more batches

Some process changes can shorten the cycle time of each batch but reduce the amount processed per charge. In batch distillation, for example, an added solvent or entrainer may reduce the cycle duration while requiring more individual batches because less feed fits into the reboiler.

The relevant measure is total campaign completion time, not the number of batches or the duration of one batch considered separately.

Local optimization versus system throughput

Improving the apparent utilization of one unit can worsen the overall schedule if it creates downstream congestion. The plant objective should be total completed production over the planning horizon, not maximum activity at any single vessel.

How to Apply This to Your Pilot Plant

A reliable analysis should compare candidate sequences using the same operating horizon, product targets, cleaning requirements, storage limits, and resource availability.

If your primary focus is maximum throughput: Compare complete campaign sequences by total cycle time and equipment idle time, then select the sequence that produces the most completed batches over the planning period.
If your primary focus is contamination control: Include product-specific cleaning and sterilization requirements explicitly, even when they make a sequence longer.
If your primary focus is equipment utilization: Identify the bottleneck unit and synchronize upstream and downstream operations around its cycle time.
If your primary focus is flexibility: Balance fewer changeovers against storage capacity, batch-size constraints, and the ability to respond to changing product priorities.
If your primary focus is pilot-plant training: Use scheduling simulations and physical runs to measure waiting, setup, operator efficiency, and the practical effect of alternative sequences.

The central planning principle is to optimize the entire batch network—equipment, changeovers, storage, labor, and bottlenecks—rather than any single operation in isolation.

Summary Table:

Factor	Throughput impact	Planning focus
Campaign sequence	Determines waiting time and total cycle duration	Compare complete product sequences
Changeovers	Cleaning, sterilization, and setup reduce productive time	Group compatible batches where practical
Bottlenecks	Delays at shared units propagate downstream	Schedule around the limiting equipment
Batch size	Affects batch count, vessel capacity, and campaign duration	Size equipment for the largest practical batch
Intermediate storage	Buffers timing differences between operations	Balance flexibility, inventory, and storage limits
Auxiliary resources	Operators, utilities, maintenance, and cleaning systems constrain availability	Include every shared resource in the schedule
Operating priority	Throughput, flexibility, contamination control, and inventory can conflict	Select the objective before optimizing the sequence

Planning a multi-product batch pilot plant? Contact LABPARK to discuss a pilot-scale solution tailored to your process and production goals. LABPARK provides Educational and Vocational Unit Operations Pilot Plants for chemical engineering, bioprocess and biotechnology, and environmental and water treatment applications. Our systems help universities, research institutes, and enterprises evaluate equipment capacity, simulate campaign schedules, train operators, identify bottlenecks, and improve throughput before full-scale implementation. Work with LABPARK to configure shared mixers, reactors, separators, cleaning systems, storage, and supporting utilities around your products, batch sizes, and operating constraints.