Campaign Run

A campaign run is a planned, contiguous sequence of batches of the same product on the same equipment train. The defining property is reduced changeover between consecutive batches — the equipment stays configured for the product, cleaning is minimal or risk-based, and changeover-driven setup losses are amortised across the campaign.

• Campaign ID — groups the batches with shared planning, cleaning regime and disposition context.
• Sequence — ordered batches with continuity (Batch 1, 2, 3...) and inter-batch hold times tracked.
• Equipment lock — equipment train is reserved for the campaign; arbitration policies prefer campaign continuity.
• Cleaning regime — minor cleans between batches, major cleans at campaign boundaries.
• Disposition — typically batch-by-batch within the campaign with rolling release; sometimes campaign-wide release for very tight processes.

• Changeover amortisation — full clean and recipe swap might take 8 hours; running 10 batches between changeovers turns 80h overhead into 8h overhead per campaign.
• Throughput uplift — campaign-mode utilisation can be 30–60% higher than single-batch mode in shared plants.
• Process stabilisation — campaigns often start with a 'first batch' that runs slightly differently as the train warms up; subsequent batches are tighter.
• Material flow — bulk procurement and inbound logistics align with campaign duration, reducing inventory volatility.
• Resource focus — operators and engineers concentrate on one product, reducing context-switching errors.

• Campaign length — number of batches per campaign, bounded by hold-time, cleaning risk and demand cadence.
• Maximum hold time between batches — beyond which a minor clean or full clean is required.
• First-batch protocol — often includes additional sampling, parametric checks or even is intentionally identified as 'training-out' material.
• Last-batch protocol — sometimes additional sampling at campaign end to confirm no drift.
• Cleaning regime — minor clean (rinse, wipe) between batches, major CIP/SIP at campaign end.
• Quality drift monitoring — IPC trending across the campaign with thresholds for early termination.

The same property that delivers throughput — minimal cleaning between batches — is also the source of campaign-specific risks:

• Carryover accumulation — minor product residues build batch over batch; eventually breach acceptance criteria.
• Equipment fouling — heat exchangers, filters, agitator shafts accumulate deposits affecting performance.
• Microbial load — aqueous processes especially see micro counts creep upward; minor cleans may not suffice.
• Calibration drift — extended runs without recalibration risk silent measurement bias.
• Process drift — small parameter shifts (jacket fouling, valve wear) accumulate over the campaign.
• Hold-time exceedances — gaps between batches sometimes exceed allowed limits without triggering full clean.

Campaign duration limits exist to bound these risks. Pushing past them for short-term throughput often costs a quality investigation worth more than the gain.

• Campaign blocks reserve the equipment train for their full duration.
• Changeover windows between campaigns are scheduled with the same rigour as production blocks.
• Demand-driven planning balances campaign size (longer = better utilisation) against responsiveness (shorter = faster response to mix shifts).
• Multi-product plants typically run a campaign 'cycle' covering all products on a rotation; the cycle length is the plant's planning horizon.

• API — campaigns of 10–30 batches of the same intermediate before changing chemistry.
• OSD pharma — granulation campaigns of 5–15 batches per SKU before product changeover.
• Biopharma — multi-product facilities running 4–10 batches per product per campaign with extensive changeover validation.
• Cosmetics — fragrance-family campaigns to manage allergen and aroma changeover requirements.
• Food — flavour campaigns where minor cleans between flavours within a family precede major cleans between families.
• Chemicals — colour-family campaigns (light shades before dark) to minimise cleaning between batches.

• Campaign length set by management preference rather than by validated cleaning and hold-time limits.
• IPC drift not monitored across the campaign — last-batch failure is a surprise rather than a predicted event.
• First-batch and last-batch differential not analysed — process opportunities missed.
• Hold-time between batches not tracked per equipment — exceedances slip through.
• Campaign-end cleaning postponed when 'just one more batch' is requested — accumulated risk.
• Campaign ID not propagated through downstream records — analytics groups individual batches randomly rather than by campaign context.
• Cleaning-verification testing waived at campaign end based on 'visual clean' — quality risk for changeover.