Slugs, and the limits of feedback

A slug is a body of liquid that arrives all at once, from the pipeline rather than from the well's average rate. Total feed jumps and the water fraction jumps with it.

Feedback control cannot anticipate. A PID only acts on error that has already appeared, so by the time the level has risen enough to command the valve open, the slug is already inside the vessel. A reactive controller is always late to a slug, not because it is badly tuned, but because of what feedback is.

What decides the outcome is whether the vessel has the surge volume (the spare capacity between the operating level and the trip) to absorb what arrived, and whether the valve has the capacity to pass it before the level reaches its trip. Tuning changes how gracefully you use that room. It does not create more of it.

There is a genuine choice here. Holding the level tightly passes the slug straight downstream; letting the level move absorbs it and protects whatever is next in the train. Field practice often prefers the second: the vessel is used as a buffer rather than a setpoint. It is called averaging level control, and it is the right answer more often than trainees expect.