A gravity media filter is the polishing step in a drinking-water plant where water, having already been coagulated and settled, passes down through a bed of sand or layered media to remove the last fine particles and floc. Gravity pulls the water through the bed; the media catches the small particles that clarification could not settle out, producing the clear, low-turbidity water that a plant sends on to disinfection and distribution. As the bed captures particles it slowly clogs, so filtration runs in cycles - filter until the bed is loaded up, then backwash it clean and start again. Managing that cycle well is the heart of running a filter.
Gravity Media Filter in one line: A gravity media filter is a bed of sand or dual media in a drinking-water plant that removes fine particles and floc as water flows down through it under gravity. The bed gradually clogs during a filter run and is periodically cleaned by reversing flow in a backwash cycle, restoring capacity so filtration can continue.
Rapid gravity filtration follows clarification. By the time water reaches the filters, coagulant has already bound fine particles into floc and a settling process has removed the bulk of it, but a residue of small particles and floc remains, and that is what the filter takes out. The water sits above the media bed and flows down through it under gravity, and the particles are captured not merely at the surface but throughout the depth of the media by a mix of straining, adhesion, and settling within the pores. The filtered water is collected by an underdrain system at the bottom of the bed.
The media itself is chosen to filter in depth rather than just at the surface. A classic rapid sand filter is a bed of graded sand; a dual-media filter puts a layer of coarser, lighter anthracite coal on top of finer, denser sand. That arrangement matters because after a backwash the layers resettle in order - coarse on top, fine on bottom - so incoming water hits the coarse layer first and works down into progressively finer media. This lets particles penetrate and be captured throughout the bed's depth instead of clogging only the top, which lengthens the run and uses the whole bed. Some plants add a third, still coarser layer for even more depth capacity.
The output that matters is turbidity, the cloudiness of the filtered water, which is the plant's continuous proxy for how well the filter is removing particles. Low, stable filtered turbidity means the bed is doing its job; a rising turbidity means particles are starting to slip through. Filtered water turbidity is monitored continuously on each filter because it is both a treatment performance measure and, indirectly, a barrier against the microorganisms that ride on particles - so a filter's turbidity trend is watched closely throughout every run.
A filter run is the span of time between backwashes, and it ends when one of two things happens. The first is headloss. As the bed captures particles, the pores clog and it becomes harder to push water through, so the resistance across the bed - the headloss - climbs steadily through the run. When headloss reaches a terminal value, the filter can no longer pass its rated flow effectively, and the bed must be cleaned. Headloss rising smoothly through a run is normal and expected; it is the clock counting down to the next backwash.
The second thing that can end a run is turbidity breakthrough. Even before the bed is fully clogged, it can start letting particles pass - the captured floc can shear loose or the bed can simply run out of depth capacity - and the filtered turbidity begins to rise. If turbidity climbs past a set limit, the run has to end regardless of headloss, because passing higher-turbidity water defeats the purpose of the filter and weakens the treatment barrier. A well-run filter is balanced so that headloss and breakthrough arrive at roughly the same time, using the full clean water the bed can produce without letting quality slip.
Both signals are trended continuously so an operator, or the control system, knows exactly where each filter is in its run. A run that ends much sooner than usual on headloss suggests a heavier particle load or a coagulation problem upstream; early turbidity breakthrough can signal media loss, a poor backwash, or coagulation that is off. Reading headloss and turbidity together across all the filters lets an operator schedule backwashes sensibly rather than reactively, and it flags the developing problems - a fouling bed, lost media, an upstream chemistry issue - that show up first in the filter runs.
Backwash is where the filter's automation earns its keep, because it is a multi-step sequence that has to run in the right order every time. When a filter reaches terminal headloss, hits a turbidity limit, or times out on a maximum run length, the SCADA system triggers the backwash. It takes the filter out of service, drains down to the media surface, and then runs the cleaning steps: many plants start with an air scour that agitates and loosens the packed bed, follow with a rising backwash flow that fluidizes the media and lifts the captured dirt out to the washwater troughs, and finish with a rinse before the filter returns to service. Each step has its own valve line-up, flow rate, and duration.
Sequencing this correctly is exactly the kind of deterministic, safety-relevant task PLC and SCADA control handles well. The controller opens and closes the influent, effluent, backwash supply, air, and waste valves in the proper order, confirms each valve reached position before proceeding, ramps the backwash flow to fluidize the bed without washing media over the troughs, and holds each step for its set time. It also manages the return to service, often filtering to waste briefly so the first, slightly turbid water after a backwash does not reach the clearwell. Interlocks prevent illegal states, such as running backwash flow before the effluent valve is closed.
Because a plant typically has several filters and often serves a system with remote tanks and pump stations, a cloud SCADA platform such as Merobix helps by presenting every filter's headloss, filtered turbidity, run time, and backwash status together, and by historizing them for the operational and regulatory record. Turbidity is a reported compliance parameter, so a system that logs each filter's turbidity continuously and records every backwash provides the documentation a utility needs. Operators can see which filter is nearing the end of its run, confirm a backwash completed cleanly, and get an alarm callout if turbidity breaks through or a backwash valve fails to seat - the kind of remote visibility that keeps a battery of filters producing consistent water without someone standing at every gallery.
A sand filter uses a single graded bed of sand, while a dual media filter adds a layer of coarser, lighter anthracite coal on top of finer, denser sand. Because the layers resettle in order after a backwash, dual media filters water from coarse to fine through the depth of the bed, letting particles penetrate deeper instead of clogging only the surface. That gives a dual media filter more dirt-holding capacity and a longer run for the same conditions.
A filter run ends when the bed reaches terminal headloss, meaning it has clogged enough that it can no longer pass its rated flow, or when filtered turbidity rises past a set limit as particles begin to break through. A maximum run-time limit can also end a run even if neither of those is reached. Whichever comes first triggers the backwash, which cleans the media and restores capacity for the next run.
A backwash typically takes the filter offline, drains it down, and then runs a cleaning sequence - often an air scour to loosen the packed media, followed by a rising backwash flow that fluidizes the bed and carries the captured dirt out to washwater troughs, and finally a rinse. The filter is then returned to service, sometimes filtering to waste briefly so the first slightly turbid water is not sent to the clearwell. A control system sequences each valve and flow step in the correct order.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.