UnitProcedureTemplate: fd-cip-cycle¶

A through-plate CIP cleaning cycle for a filter-dryer: pre-rinse, hot chemical wash, post-rinse. Use this UnitProcedureTemplate at the top of a filter-dryer-specific CIP master recipe. Unlike the mix-tank and reactor CIP unit procedure templates, this one does not include drying or vent steps. Those remain at the master-recipe level because whether drying is needed (and to what target moisture) depends on the campaign following the CIP.

Referenced directly by the sim-fd-cip-m1 master recipe. That recipe wraps this unit procedure template with a pre-CIP vacuum-decay integrity test, a post-CIP vacuum-dry phase, and a vent step.

Where to find it¶

System endpoint → Equipment Library → Unit Procedures → select fd-cip-cycle.

graph TD
    Start([initial]) --> PR[pre-rinse]
    PR --> HW[hot-wash]
    HW --> PoR[post-rinse]
    PoR --> Done([done])

Strict linear sequence with no conditional branches. If you need to skip the hot wash, extend the chart to expose skip_if_zero as a cycle-level parameter.

What you see when it runs¶

Element	Meaning
Unit procedure node	The top-level node for `filter-dryer-1`'s procedural tree
Operation children	`pre-rinse`, `hot-wash`, `post-rinse`
Active operation	Highlighted on the tree; click in to see its child phase

HMI screenshot pending

An annotated capture of a running fd-cip-cycle procedural tree will be added here.

Why filter-dryer-specific¶

The filter-dryer cleans by pulling WFI (or chemical solution) through the filter plate under vacuum, where vessel-style CIP fills the vessel and agitates. This requires a fundamentally different valve and control topology:

Resource	Mix tank (vessel CIP)	Filter-dryer (through-plate CIP)
Water inlet	`inlet_valve` (fills vessel)	`wash_valve` (admits water above plate)
Drain	`outlet_valve` (drains bottom)	`filtrate_valve` (under plate, pulled by vacuum)
Driving force	gravity drain + agitation	vacuum pump under plate
Vacuum	n/a	`vacuum_controller` (continuous)
Heating	`temp_controller`	`jacket_controller`

Because the filter-dryer has no "fill and agitate" step, the generic cip-rinse-op and cip-hot-wash-op operations don't apply. The filter-dryer has its own fd-cip-rinse-op and fd-cip-hot-wash-op operations wrapping the through-plate phases.

Operations¶

Three steps, each calling one filter-dryer-specific operation template. Each operation wraps exactly one phase. The operations exist so the UnitProcedureTemplate can call OperationTemplate resources per ISA-88 layering.

#	Step	Operation	Phase	Description
1	`pre-rinse`	`fd-cip-rinse-op`	`fd-cip-rinse`	Through-plate WFI pre-rinse — open filtrate, start vacuum, open wash valve, hold for rinse duration, drain residual
2	`hot-wash`	`fd-cip-hot-wash-op`	`fd-cip-hot-wash`	Through-plate hot chemical wash — heated chemical under vacuum with `skip_if_zero` gate (always `1` at this level — the operation exists for parity, but gating is available if you extend the recipe)
3	`post-rinse`	`fd-cip-rinse-op`	`fd-cip-rinse`	Through-plate WFI post-rinse — removes chemical residue

Capability: filtration.

Parameters¶

Parameters follow the {stepPrefix}{Field} naming convention of the other CIP unit procedure templates. All are optional with defaults, and the master recipe binds each one to a same-named recipe parameter. TIME parameters take duration strings ("45s", "1m30s", "5m"). A bare number is not a duration.

Parameter	Type	Unit	Default
`preRinseDuration`	TIME	—	`10m`
`preRinseVacuum`	REAL	%	`60`
`hotWashTemp`	REAL	degC	`65`
`hotWashJacketOutput`	REAL	%	`70`
`hotWashContactTime`	TIME	—	`20m`
`hotWashVacuum`	REAL	%	`50`
`postRinseDuration`	TIME	—	`10m`
`postRinseVacuum`	REAL	%	`60`

How it works¶

The batch controller expands this template into a three-operation SFC when the batch starts. Each operation wraps exactly one through-plate phase, and the unit procedure advances when the current operation completes.

pre-rinse pulls WFI through the plate under vacuum.
hot-wash pulls heated chemical solution through the plate and holds for the contact time (with an internal skip_if_zero gate that's bound to 1 at this level).
post-rinse pulls WFI through again to remove chemical residue.

What this template does NOT include¶

The filter-dryer CIP master recipe has two post-CIP steps that live outside this unit procedure template:

vacuum-dry phase — removes residual wash water by heating the jacket under vacuum until the moisture sensor reaches the target. Whether drying is needed (and to what target moisture) depends on the campaign following the CIP, so this stays at the master-recipe level.
filter-discharge phase used as a vent — breaks the vacuum by opening the vent valve to atmosphere. Used here with agitator_speed: 0 because there's no cake to discharge. It's just the final pressure equalization.

Keeping these at the master-recipe level means you can reuse this fd-cip-cycle unit procedure template unchanged for recipes with different post-cleaning requirements (immediate re-use, long-term storage, handoff to next campaign, etc.).

Used in recipes¶

sim-fd-cip-m1 — filter-dryer CIP master recipe. Calls this template between the vacuum-decay integrity test and the post-CIP drying / venting steps.

Try it¶

HMI endpoint → Batch Execution → + New → sim-fd-cip-m1 → Start
The first step on filter-dryer-1 is the standalone fd-vacuum-decay-test phase. This unit procedure activates after the test passes
Expand the procedural tree to see this template at the top with three operation children
Click into each operation to watch its single through-plate phase run