Use approved cleaning constraints in campaign planning

Changeover time depends on what came before

A planner adds another batch to a high-demand campaign. The line remains available, material is ready and the extra run appears to avoid a costly changeover. But the proposed campaign now crosses the approved equipment-use boundary. The schedule has improved utilisation by assuming a condition the site has not authorised.

Campaign planning needs more than a block of downtime labelled “cleaning”. It must represent which product ran, on which equipment, for how long, how many batches were included and what must happen before the next use. The correct transition can depend on that history.

The planning application should consume approved constraints and reveal conflicts. It should not create new cleaning limits, select a toxicological threshold or decide that a longer hold time is acceptable. Those are scientific and quality decisions managed through the site's established processes.

Separate production, cleaning and hold-time clocks

Production duration describes how long the batch occupies a resource. Cleaning duration describes the activities required to prepare that resource for its next approved use. Dirty hold time concerns the interval before cleaning, while clean hold time concerns the interval before subsequent use. Campaign duration or batch count can impose another boundary.

These clocks may start and stop at different defined events. A system cannot enforce them reliably if “batch complete” sometimes means processing finished and sometimes means documentation closed. Agree the operational event behind each timestamp and identify the system or person responsible for recording it.

EU GMP Annex 15 addresses clean and dirty hold times and the maximum campaign length considered in cleaning validation. Its applicability depends on the site's regulatory context; the approved site evidence supplies the actual limits used in scheduling. EU GMP Annex 15, sections 10.8–10.9.

Build a transition model people can inspect

Represent the current product, proposed next product, equipment train, applicable cleaning procedure and effective version. Include the required activities and dependencies, such as equipment availability, cleaning personnel, utilities, sampling or review where the approved process requires them.

Avoid treating a blank transition as zero time. It may mean that the route is not approved, the evidence has not been entered or the product combination is genuinely inapplicable. These states need different handling. A planner should receive a clear unresolved-constraint message instead of an apparently efficient sequence.

Version the transition data. When an approved cleaning procedure changes, identify which future schedules used the old version and whether they require reassessment. Preserve historical plans against their original basis so an investigation can reconstruct what the planner knew at the time.

Worked example of an additional campaign batch

Consider an illustrative equipment train with a site-approved campaign boundary of four batches for a particular product and route. This number is an assumption for the example, not a recommended validation limit. Four batches are already scheduled, and commercial demand prompts a request for a fifth.

The scheduler should flag the fifth batch before it is accepted. It can propose feasible alternatives, such as an approved cleaning and readiness sequence before further manufacture, another qualified route if available, or a later campaign. It cannot change the boundary from four to five because the order is urgent.

Suppose the four planned batches each occupy eight hours and the complete approved transition requires a further six hours in this example. The original campaign plus transition occupies 38 hours: 4 × 8 + 6. A fifth batch adds at least eight production hours, but the actual new plan depends on where the required cleaning and readiness activities fall. It is not simply a 46-hour uninterrupted campaign.

Now introduce a breakdown after the third batch. The equipment remains unavailable for an uncertain period. The planning model should evaluate the relevant elapsed-time conditions and proposed recovery sequence using actual event times. A batch-count check alone may miss a time-based campaign or hold constraint.

The production and quality teams decide the permissible recovery path under approved procedures. Planning then reflects that path and recalculates affected customer commitments. The decision record should connect the breakdown, equipment status and revised sequence, so later reviewers do not mistake a rescheduled date for evidence that the original conditions remained valid.

Keep equipment state separate from planned time

A calendar can reserve six hours for cleaning without proving the cleaning occurred. Maintain actual states such as awaiting cleaning, cleaning in progress, awaiting required review and ready for intended use, using the site's approved terminology. The precise workflow will vary; the important point is that elapsed planned time does not automatically establish readiness.

If a required check fails or cleaning is interrupted, retain the event and route the exception. Do not restart the display as though the first attempt never happened. The responsible team needs the history to decide what work is required and how the schedule changes.

Equipment trains complicate readiness. One vessel may be ready while a connected transfer line is unavailable. Define the resources required for the intended route and prevent an aggregate green status from hiding a blocked component. The maintenance-readiness guide covers the related handback decision after engineering work.

Optimise within the approved operating space

Grouping similar products may reduce transitions, but a proposed sequence must first be feasible. After applying the hard constraints, compare alternatives on service, labour, material timing and inventory exposure. The cheapest sequence can still create excess stock or delay a higher-priority commitment.

Show the planner why a sequence was rejected. A message that names the affected equipment, transition version and boundary is actionable. A generic “no solution found” encourages users to move work outside the system, where the constraint may be lost entirely.

Where a novel product or route lacks approved coverage, create a readiness dependency rather than a guessed duration. The cleaning-validation workflow addresses the evidence process; the scheduler should reference its outcome. The broader production-scheduling guide shows how these constraints interact with materials and customer dates.

Test timestamps and disruption paths

Use boundary tests based on the site's approved values. Check a campaign just within the permitted conditions, one exactly at the relevant boundary and one beyond it. Confirm how the approved procedure defines equality and the relevant timing precision; software defaults should not decide those interpretations.

Include late data entry, corrected event times and a temporarily disconnected device. A corrected manufacturing-end time may change a hold-time calculation, so the application should retain the correction history and identify affected decisions. It should not silently recalculate the past without informing the responsible reviewer.

Test whether a planner can bypass a blocked route through manual drag-and-drop, bulk upload or an integration. Controls that work only in one screen leave an inconsistent planning process. Permission to edit a schedule should not imply permission to edit approved cleaning constraints.

Make the pilot useful to both planning and quality

Start with one shared equipment train and a manageable set of product transitions. Ask planners to explain proposed sequences and ask quality reviewers to trace each critical constraint to its approved basis. Both views need to work for the same schedule.

Measure avoidable replanning caused by missing cleaning dependencies and the time taken to resolve unknown transitions. Do not claim that a shorter changeover proves cleaning effectiveness. Operational efficiency and scientific assurance need their own evidence.

NextEdge Labs can help integrate the constraint register, equipment events and planning interface. A valuable first release makes an invalid campaign visibly impossible to approve through the ordinary planning path and gives users a clear route to resolve the underlying issue.

Summary and next actions

Cleaning-aware campaign planning makes approved operating boundaries visible before commitments are made. It connects sequence, elapsed time and actual equipment readiness while leaving scientific limits and recovery decisions with the responsible specialists.

• Select one equipment train and identify the approved product transitions and campaign boundaries.
• Define the start and stop events for each relevant hold-time clock.
• Replay an additional-batch request and a breakdown to check the resulting schedule decisions.
• Test manual edits, corrected timestamps and integration paths against the same constraints.