OEE & Downtime in Pharmaceutical Manufacturing
Key takeaways
- In pharma, compliance work eats availability that other sectors never see.
- The big losses: cleaning and changeover validation, documentation, and serialization stops.
- Quality is non-negotiable, so a defect or deviation is unusually expensive.
- Accurate, traceable stop data supports audit-readiness as well as improvement.
Pharmaceutical manufacturing optimises for compliance and patient safety first, throughput second, and rightly so. The result is an OEE profile unlike any other sector: large, necessary availability losses around cleaning, validation and documentation, plus packaging lines that share every micro-stop problem of high-speed filling.
What's a good OEE in pharma?
We found no published OEE range for pharmaceutical lines as a whole with a stated method. The usual reference is 85 percent world-class (traced to Nakajima, Introduction to TPM, 1988), and published plant studies found average OEE of about 55 to 65 percent (sources: Ljungberg, 1998; Hedman et al., 2016); the more useful target is your own line's trend. The gap is not all waste: validated cleaning, changeover and in-process checks are required. The opportunity is to shrink the avoidable part (long changeovers, unlogged micro-stops) without touching what compliance requires. Calculate your OEE.
The biggest losses in pharma
| Loss | Why it's big in pharma | OEE factor |
|---|---|---|
| Cleaning & changeover validation | Validated cleaning and verification between products and batches is long and mandatory | Availability |
| Documentation & in-process checks | Batch records, line clearance and in-process testing pause production | Availability |
| Serialization & aggregation stops | Track-and-trace coding, vision checks and rejects on packaging lines | Performance / Quality |
| Filler / blister / capper micro-stops | High-speed packaging shares the hidden factory problem | Performance |
| Quality holds & reduced yield | Deviations and rejects are costly and trigger investigation | Quality |
Separate the validated, required downtime from the recoverable micro-stops and changeover drift.
One blister line shift, worked through
Illustrative numbers for a blister packaging line, so you can check the math against your own shift. Planned production time is 450 minutes. The log records a 45-minute line clearance and a 45-minute format changeover: 90 minutes of downtime, all of it required. The blister machine is rated at 300 blisters a minute but runs at 270 to hold seal quality, and it stops about 60 times for 20 seconds each (a missing tablet, a feeder jam, a foil splice), which nobody logs.
| Step | Calculation | Result |
|---|---|---|
| Availability | run time 360 min (450 - 90) / 450 | 80.0% |
| Blisters made | 340 running min (360 - 20 of micro-stops) x 270 a minute | 91,800 |
| Performance | 91,800 / 300 a minute / 360 | 85.0% |
| Quality | 89,964 good of 91,800 (1,836 inspection and startup rejects) | 98.0% |
| OEE | 80.0% x 85.0% x 98.0% | 66.6% |
The line lost 150 minutes. 90 of them are line clearance and changeover that the process requires, so the honest target is the other 60: 20 of micro-stops, 34 of reduced speed and 6 of rejects. Only the required part reached the log; the avoidable part never did.
Reason codes for a blister and cartoning line
A short list everyone uses beats a long one nobody does. A starting set:
- Required: line clearance, format changeover, in-process check
- Blister machine: forming film break, seal temperature, feeder jam, missing tablet
- Cartoner and serialization: carton jam, code read failure, aggregation error
- Material: foil or film roll end, leaflet feed
- Starved or blocked: upstream bulk, downstream case packing
- Quality: inspection reject, deviation hold
Log them in the free OEE tracker and the downtime Pareto ranks them for you; the downtime log template does the same on paper.
What a camera shows on a blister line
A stop code tells you the blister line stopped, not what happened at the feeder in the seconds before. Where cameras are fitted, Fabrico's camera-based OEE software can stream, on request, video of the minute the line stopped, next to its machine data (it is not stored). Machine signals also catch short stops and a line that is switched on but not producing, the losses nobody writes down: in the shift above, that is the 20 minutes the log never saw.
What downtime costs in pharma
High product value, batch-based production and strict release testing mean a stoppage can put an entire batch at risk, not just a few minutes of output. Add the cost of investigations and the picture is clear: even modest, recoverable losses are worth chasing. Estimate your downtime cost.
How leading pharma plants improve
- Separate required from avoidable downtime so improvement targets the recoverable part only.
- Attack changeover and cleaning time with SMED-style standard work, within validation.
- Capture every stop accurately for both improvement and a traceable record.
Fabrico reads OEE and stops straight from the line and shows video of a stop streamed on request next to its machine data, where cameras are fitted, giving an accurate, time-stamped record that supports audit-readiness and targets the recoverable losses. It is EU-built, with EU customers hosted on AWS in Frankfurt and holds ISO 27001 / 20000-1 / 9001. We recommend Fabrico; the tools here are free regardless.
What world-class looks like on pharmaceutical lines
Overall Equipment Effectiveness (R. C. Hansen, 2001) sets the world-class bar by type of process, building on Nakajima's TPM figures: 85% or more for batch and discrete processes, 90% or more for dedicated discrete and non-dedicated continuous processes, and 95% or more for dedicated continuous processes. Granulation, compression, coating and packaging run in batches, so the 85% bar applies. Cleaning and line clearance between batches are planned stops that count against availability; only time planned ahead as not for production is left out. Compare a line with its own trend first; published OEE figures by industry are scarce.
Should validated cleaning count against OEE?
It is required downtime during planned production time, so it does reduce OEE. The point is not to cut what compliance requires, but to reduce the avoidable losses around it and to keep cleaning efficient.
How does this help with audits?
Automatic, time-stamped capture of every stop and its cause gives a complete, accurate line history, which supports audit-readiness. It does not by itself make a site compliant; it provides better evidence and control.
Where is the fastest gain?
Usually the unlogged micro-stops on packaging and serialization lines, plus tightening changeover time within the validated procedure.
Common equipment to troubleshoot: Tablet presses · Labellers · full directory
Related guides: OEE & Downtime in Aerospace & Defense Manufacturing · OEE & Downtime in CPG / Consumer Goods Manufacturing · OEE & Downtime in Medical Device Manufacturing · MES for Pharma: Part 11, Annex 11, Validation · MES for Pharma: Part 11, Annex 11, Validation