Simulation for Pharmaceutical Manufacturing
Where Batch Rules Limit Capacity as Much as Line Rates
A pharmaceutical line is a manufacturing system with a regulatory system wrapped around it. Batches can't be interrupted, and changeovers carry validated cleaning. Material waits on quality release rather than on a conveyor. The constraint is often a step where nothing physical is happening at all.
Who has used it
Eli Lilly · Genentech · Glaxo Wellcome · Pfizer · Teleflex · BioPharm Services
Why the usual throughput analysis misses here
Most capacity arithmetic assumes the constraint is a machine running too slowly. In pharma the binding step is often a wait, such as a hold for quality release, a validated clean between products, or a stability or sterility check that takes as long as it takes. None of those go faster when you buy more equipment, and none of them show up as downtime on a machine report.
So the plant is a coupled system whose couplings are procedural rather than mechanical, and averages mislead badly here. A step that's idle 80% of the time can still be the constraint, because what matters is when it's available relative to when the batch needs it.
What tends to be binding
Quality hold and release
Material that's physically finished but not yet releasable takes up space, ages, and blocks the step behind it. Release time is variable and mostly outside operations’ control. That kind of variability has to be modeled rather than averaged.
Validated changeover and cleaning
Changeovers aren't a setup time to squeeze. They're a validated procedure, which makes campaign length a real commercial lever. Longer campaigns amortize the clean but build inventory and reduce responsiveness, and the best length moves with product mix.
Batch integrity
A batch that can't be split or interrupted couples upstream and downstream far more tightly than a continuous flow does. Buffering between them is limited by hold times and stability, so the usual answer of adding storage is bounded by chemistry and by the filing.
Shared suites and utilities
Suites, vessels and clean utilities shared across products couple lines that look independent on a flowsheet. The interaction only appears over time, under a real campaign schedule.
It's the same pattern as everywhere else on this site, in a stricter setting. The loss report ranks by minutes lost, but what you want ranked is recoverable throughput, meaning what the line actually returns when a constraint is relieved. In a regulated plant, several of the biggest entries on that report can't be relieved at all, so ranking by recovery matters even more.
Related work on this site
The same mechanisms show up on these other lines.
Buying time instead of buying a line
Two stages that had to run in lockstep were separated by stabilizing the intermediate. It's the direct analog of a hold-time constraint, where a buffer's worth depends on how long material may legally sit in it.
Run the simulator → Campaign SchedulingThe Shifty Bottleneck
Changing the product format moved the constraint and defeated a planning system built on a fixed bottleneck. It's the campaign-scheduling problem in another industry.
Read the example →A free line assessment, this fall
Bring one question about your line. We model it on your own data and send back a two-page readout in about five business days.
Apply for a free line assessment →Or explore the Sandbox first, with no sign-up.