Skip to content

OperationTemplate: cip-rinse-op

A generic CIP rinse operation: fill the vessel with WFI, agitate to dissolve residue, and drain. Use this operation for any non-final rinse step in a mix-tank-style CIP cycle (pre-rinse or intermediate rinse between chemical washes). For the final rinse, use cip-conductivity-rinse-op, which adds a conductivity endpoint check.

In ISA-88 terms this is an OperationTemplate that groups three phases into a reusable unit a UnitProcedureTemplate can call repeatedly.

Where to find it

System endpoint → Equipment Library → Operations → select cip-rinse-op.

What you see when it runs

Inside the procedural tree (HMI endpoint → Batch Execution → click into the active batch), this operation appears as a three-step node with the active phase highlighted:

Element Meaning
Operation node pre-rinse or intermediate-rinse depending on which UnitProcedureTemplate call you're inside
Phase children fill → agitate → drain, executed in order
Active phase Highlighted — click into it for the phase-level detail (active SFC step, parameters)

HMI screenshot pending

An annotated capture of a running cip-rinse-op operation will be added here.

Phases

# Step Phase template Description
1 fill cip-fill Fill vessel with WFI
2 agitate cip-agitate Agitate to dissolve residue
3 drain cip-drain Drain rinse water

Capability: mixing.

Parameters

Parameter Type Unit Range Default Required
fill_level REAL L 50-450 300 yes
agitate_speed REAL % 20-100 40 yes
agitate_duration TIME — 10s-10m 5m yes
drain_level REAL L 0-50 5 no

TIME parameters take duration strings ("45s", "1m30s", "5m"), not bare numbers.

How it works

The operation's spec.chart is a linear three-step SFC, and the batch controller advances one child phase at a time:

  1. fill runs to completion (level reaches the operation's fill_level parameter via cip-fill's level guard).
  2. agitate runs next — the agitator ramps to agitate_speed and holds for agitate_duration.
  3. drain opens the outlet and waits until level drops to the drain target.
  4. The operation completes and the parent unit-procedure step advances.

Each phase retains its own failure-mode semantics. See the linked phase pages for alarm pairings and timeoutSeconds guidance.

Used in

Try it

  1. HMI endpoint → Batch Execution → + New → sim-cip-cycle-m1 → Start
  2. Expand the procedural tree — the first node is this operation (pre-rinse), then caustic-wash, then another call as intermediate-rinse
  3. Click into pre-rinse to see the three child phases advance in turn