Shared batch reactors should be sized from the product that requires the largest practical batch volume after campaign timing and whole-batch constraints are applied. Start by defining each product’s target output, batch-cycle time, and reactor volume required per unit of product. Then allocate the available operating time among products, calculate feasible integer batch counts, and select a vessel volume that accommodates the largest resulting batch while meeting cleaning, sterilization, changeover, and scheduling requirements.

A shared reactor is governed by the limiting product condition: the largest actual batch volume required by any product after rounding batch counts to whole batches. The best schedule is the one that satisfies production targets while minimizing idle time, changeovers, bottlenecks, and unnecessary reactor capacity.

Define the Shared-Plant Capacity Problem

Establish the available operating window

Let the total available operating time be (T). For products (A), (B), and (C), allocate campaign times (t_A), (t_B), and (t_C) such that:

[ t_A+t_B+t_C=T ]

The available time should reflect the real operating calendar, including planned maintenance, staffing limits, experiments, and required downtime.

A nominal value such as 500 operating hours is useful for planning, but it should not be treated as fully productive time unless the plant can actually operate during that entire period.

Define the complete batch cycle

For product (x), define the total cycle time as:

[ t_{\text{cycle},x}

t_{\text{fill},x} +t_{\text{process},x} +t_{\text{clean},x} +t_{\text{sterilize},x} +t_{\text{empty},x} ]

Depending on the process, heating, cooling, sampling, maintenance, and inspection may also need to be included.

The critical principle is that turnaround time consumes reactor capacity. A reactor that reacts for six hours but requires four hours for cleaning and recharging has a ten-hour production cycle, not a six-hour cycle.

Calculate Product-Specific Batch Requirements

Determine the number of batches

For product (x), the ideal continuous estimate of batch count is:

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

This value is useful for preliminary sizing, but it is generally not an executable production plan because a fraction of a batch cannot normally be scheduled.

The practical batch count must be an integer:

[ N_x \in {0,1,2,\ldots} ]

Convert campaign targets into batch volumes

Let:

(M_x) be the target mass of product (x),
(v_{\text{react},x}) be the reactor volume required per unit mass of product (x),
(N_x) be the number of completed batches.

The required batch volume is:

[ V_x=\frac{M_x,v_{\text{react},x}}{N_x} ]

This calculation captures an important trade-off. More batches reduce the volume required per batch, but they consume more filling, processing, cleaning, sterilization, and emptying time.

The corresponding campaign duration is:

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

Thus, batch count and campaign duration must be evaluated together.

Include material-balance sizing where appropriate

For a reaction-based process, reactor volume can also be connected directly to the required production rate and conversion:

[ V_R = \frac{\nu_A \Phi_P (t+t')} {\nu_P M_P c_{A0}\zeta_A} ]

Here, (t) is active reaction time and (t') is non-productive operating time, including activities such as charging, heating, cooling, cleaning, and discharge.

This formulation makes the effect of operational efficiency explicit: reducing turnaround time can reduce the reactor volume required for a given production rate, provided the process and production assumptions remain valid.

Size the Common Reactor

Identify the limiting product

For a candidate allocation of campaigns, calculate (V_x) for every product. The shared vessel must satisfy:

[ V_R \geq \max(V_A,V_B,V_C,\ldots) ]

The product associated with the maximum value is the limiting product.

This is the governing vessel-size condition because a reactor sized below that value cannot complete the corresponding product campaign at the required batch count.

Use equal-volume calculations for preliminary allocation

Before enforcing integer batch counts, engineers can explore a balanced allocation by setting the ideal batch-volume requirements equal:

[ \frac{M_Av_{\text{react},A}}{t_A/t_{\text{cycle},A}}

\frac{M_Bv_{\text{react},B}}{t_B/t_{\text{cycle},B}}

\frac{M_Cv_{\text{react},C}}{t_C/t_{\text{cycle},C}} ]

Combined with:

[ t_A+t_B+t_C=T ]

these equations provide candidate campaign durations that use the shared reactor more evenly.

This is a planning technique, not the final design decision. Equal ideal volumes can produce fractional batches, and the resulting rounded schedule may shift the limiting condition to a different product.

Recalculate after rounding

After obtaining preliminary campaign times, round the batch counts to feasible integers and recalculate:

[ V_x=\frac{M_xv_{\text{react},x}}{N_x} ]

Then verify all of the following:

(N_x t_{\text{cycle},x}) fits within the allocated campaign time.
The completed batches meet or exceed the required production target.
The reactor volume accommodates every product batch.
Cleaning, sterilization, and changeover requirements are included.
The selected schedule does not exceed the total available operating time.

The final reactor size should be based on this integer-feasible schedule, not solely on the continuous equal-volume solution.

Schedule Campaigns for Throughput

Choose campaign boundaries deliberately

A campaign is a sequence of batches for one product before the shared equipment is changed over to another product.

Longer campaigns usually reduce the frequency of cleaning and product changeover. However, they can delay other products, increase intermediate inventory, or create delivery problems when demand is time-sensitive.

Campaign duration should therefore be selected from both production requirements and operational constraints.

Compare alternative product sequences

The order of product campaigns affects total elapsed time whenever changeovers, cleaning procedures, or shared upstream and downstream equipment differ.

For example, a sequence such as:

[ A \rightarrow B \rightarrow C \rightarrow A \rightarrow B \rightarrow C ]

may have a shorter repeat-cycle time than:

[ C \rightarrow B \rightarrow A \rightarrow C \rightarrow B \rightarrow A ]

if the first sequence reduces cleaning severity, thermal transitions, or equipment idle periods.

Over a fixed operating window, even a modest difference in sequence cycle time can change the number of completed batches. Sequence selection should therefore be evaluated alongside vessel sizing rather than treated as an administrative detail.

Synchronize interconnected unit operations

A reactor campaign cannot be optimized independently when the pilot plant also includes pretreatment, separation, recovery, or packaging units.

The schedule must account for:

Material availability from upstream operations.
Reactor loading and unloading windows.
Separation and recovery capacity.
Intermediate hold limits.
Cleaning and sterilization dependencies.
Downstream packaging or sampling capacity.

In a serial process, the slowest or most constrained unit becomes the plant bottleneck. Increasing reactor capacity does not improve total throughput if another unit cannot accept the reactor output.

Optimize Batch Cycle Time

Separate productive and non-productive time

The active processing period contributes to conversion or product formation. Turnaround activities enable the next batch but do not directly produce product.

A useful conceptual form for production rate is:

[ \text{Production rate} \propto \frac{\text{product obtained per batch}} {t_{\text{active}}+t_{\text{turnaround}}} ]

This shows why a technically fast reaction may still have poor plant productivity if cleaning, sterilization, cooling, or discharge operations are slow.

Evaluate the best active cycle time

Extending reaction time may improve conversion, but it also delays the next batch. The useful cycle time is the point at which the additional product obtained from longer processing no longer compensates for the time consumed.

Graphically, the optimum occurs where the line from the origin is tangent to the performance curve that relates product formation or conversion to active processing time, after accounting for fixed turnaround time.

This analysis helps determine whether capacity is best improved by increasing reaction time, improving conversion, or reducing turnaround activities.

Treat thermal operations as capacity constraints

Heating and cooling can dominate batch-cycle time in pilot-scale equipment. Reactor jackets, internal coils, coolant flow, heat-transfer coefficients, and temperature-control limits all affect the time before a vessel can be emptied and recharged.

For bioprocesses, sterilization heating and controlled cooling may be essential to product quality. They should be modeled as part of the validated cycle rather than treated as incidental delays.

Understanding the Trade-offs

Equalized volumes may not minimize total time

Balancing ideal batch volumes across products can improve equipment utilization, but it does not automatically produce the highest throughput.

A product with a long cycle time may require substantial campaign time even when its batch volume is moderate. A schedule optimized only for equal vessel volumes can therefore leave insufficient time for other products.

Rounding can change the limiting condition

The continuous estimate (N_x^*=t_x/t_{\text{cycle},x}) is not directly executable. Rounding batch counts can create unused time, increase required volume, or cause a different product to become the largest batch.

For this reason, every candidate schedule requires an integer-batch recalculation.

Larger vessels do not remove operational bottlenecks

Oversizing the shared reactor may allow larger batches, but it can increase capital cost, cleaning requirements, heating and cooling loads, and material losses.

A larger reactor also provides no system-level benefit if separation, recovery, utilities, staffing, or downstream packaging remain limiting.

Product sequencing can increase cross-contamination risk

The shortest theoretical sequence is not always acceptable. Bioprocess and chemical plants may require validated cleaning, segregation, allergen or potent-compound controls, or a specific campaign order.

A schedule must satisfy those quality and safety requirements before throughput benefits are considered.

Pilot-plant assumptions need validation

Basic batch-reactor calculations often assume perfect mixing, no material flow during reaction, and constant liquid volume. These assumptions are useful for analysis, but scale-up work must verify mixing, heat transfer, foaming, gas transfer, viscosity effects, density changes, and actual working-volume limits.

The vessel’s nominal geometric volume is not necessarily its usable batch volume.

Making the Right Choice for Your Goal

Use an iterative calculation that combines campaign allocation, whole-batch counts, reactor volume, sequence-dependent changeovers, and upstream and downstream constraints.

If your primary focus is minimum capital cost: Balance campaign times preliminarily, then size the vessel to the largest actual batch volume after integer batch counts and validated working-volume limits are applied.
If your primary focus is maximum throughput: Compare complete campaign sequences using total cycle time, changeovers, idle periods, and bottleneck utilization rather than reactor volume alone.
If your primary focus is production flexibility: Preserve operating margin for the product with the largest volume or longest cycle time, and verify that cleaning and sterilization procedures support the intended product order.
If your primary focus is scale-up or education: Record each batch step separately, including charging, heating, sterilization, cooling, reaction, discharge, and cleaning, so calculated cycle times can be compared with measured pilot-plant performance.

A defensible shared-reactor design is the smallest validated vessel and schedule that completes all required whole batches within the available operating window while respecting process, quality, safety, and downstream constraints.

Summary Table:

Planning factor	Key calculation or check	Why it matters
Available operating time	Allocate campaign times within total validated operating hours	Prevents unrealistic production plans
Complete batch cycle	Include filling, processing, heating, cooling, cleaning, sterilization, and discharge	Captures true reactor capacity
Batch count	Use feasible whole-batch integers for each product	Ensures the schedule can be executed
Batch volume	Calculate target output × volume per unit ÷ batch count	Determines product-specific vessel demand
Limiting product	Select the largest actual batch volume after rounding	Sets the minimum shared-reactor size
Campaign sequence	Compare changeovers, cleaning, idle time, and product order	Improves throughput and reduces cross-contamination risk
Plant integration	Coordinate upstream supply, separation, recovery, utilities, and packaging	Prevents non-reactor bottlenecks
Final validation	Confirm working volume, mixing, heat transfer, quality, safety, and downstream capacity	Supports reliable scale-up and operation

Plan a More Flexible, Reliable Pilot Plant with LABPARK

Need to size shared reactors or improve multi-product campaign scheduling? Contact LABPARK for practical support in selecting and configuring Educational and Vocational Unit Operations Pilot Plants for chemical engineering, bioprocess and biotechnology, and environmental and water treatment applications.

LABPARK helps universities, research institutes, and enterprises evaluate complete process workflows—not just individual vessels. Our pilot plants support hands-on education, process development, scale-up studies, equipment validation, and operator training, with attention to batch capacity, working volume, heating and cooling, cleaning, sterilization, process integration, and downstream bottlenecks.

Tell us your products, target output, batch-cycle times, operating window, and required unit operations. We can help you develop a practical pilot-plant configuration that improves training value, testing flexibility, process understanding, and production planning.