A conventional aeration control loop holds a fixed dissolved oxygen setpoint, but that setpoint is usually chosen conservatively high to guarantee the plant always nitrifies, which means the plant often aerates more than the day's load actually requires. Ammonia-based aeration control asks a smarter question: instead of holding a fixed oxygen level, hold the outcome that actually matters, which is low effluent ammonia. By letting the measured ammonia decide how much oxygen to demand, it aerates just enough to meet the limit and no more. This guide explains how ABAC works, how it saves energy, and how it is implemented in SCADA.
Ammonia-Based Aeration Control in one line: Ammonia-based aeration control, or ABAC, is a strategy that uses the measured ammonia concentration in the process to set the dissolved oxygen target, rather than holding a fixed DO setpoint. When ammonia is low the controller lowers the DO setpoint to save aeration energy, and when ammonia rises toward the limit it raises the DO setpoint to nitrify harder, so the plant aerates only as much as the actual nitrogen load requires while still meeting its ammonia limit.
In a plant that must nitrify, the real objective is not a particular oxygen level but a low ammonia concentration leaving the process. A fixed dissolved oxygen setpoint is only a proxy for that objective, and to be safe it is normally set high enough to keep nitrifying even under the heaviest expected load. That safety margin is exactly the problem: for most of the day, when the nitrogen load is lighter, holding that high oxygen level delivers more oxygen than the bacteria actually need, and the extra aeration is energy spent for no benefit.
Ammonia-based control replaces the fixed target with one that moves in response to the measured ammonia. An outer controller watches the ammonia concentration and compares it to an ammonia setpoint chosen to stay safely under the permit limit. When ammonia is comfortably low, the controller concludes the plant is nitrifying easily and lowers the dissolved oxygen setpoint, reducing aeration. When ammonia climbs toward its setpoint, the controller raises the dissolved oxygen setpoint to push nitrification harder and bring ammonia back down. The oxygen target thus tracks the true load rather than sitting fixed at a worst-case value.
This is naturally a cascade, or feedforward-trim, arrangement. The slow ammonia loop does not touch the blowers directly; it only adjusts the setpoint handed to the existing dissolved oxygen loop, which continues to do the fast work of holding whatever oxygen level it is told to. Some schemes add a feedforward element that anticipates a rising load from influent measurements and nudges the oxygen up before ammonia has climbed, so the plant reacts to load changes rather than only chasing them after the fact.
The energy saving comes from removing the standing over-aeration that a fixed conservative setpoint bakes in. Nitrifying bacteria need oxygen, but beyond the level required to process the current ammonia load, adding more oxygen does little to speed them up, so the surplus mostly wastes blower power. By pulling the oxygen setpoint down whenever ammonia shows the plant has headroom, ABAC spends that saved power only when the nitrogen load genuinely demands it. Because so much of a plant's electricity goes into aeration, trimming the routine surplus can meaningfully lower energy use.
The reason this can be done safely is that the controller is watching the very thing the permit cares about. A plant on a fixed oxygen setpoint has no direct feedback on whether it is comfortably meeting its ammonia limit; it just trusts that the chosen oxygen level is enough. ABAC closes that gap by measuring ammonia and only relaxing aeration while the measurement confirms there is margin, then tightening aeration the moment the margin shrinks. The strategy is therefore not about accepting worse effluent to save power but about not paying for oxygen that is doing nothing.
Tuning matters because the process is slow and the stakes are real. The ammonia loop is usually made gentle so it does not swing the oxygen setpoint wildly, and limits are placed on how low the oxygen setpoint may fall so the plant never starves the biology or lets floc conditions deteriorate. The aim is a controller that saves energy steadily during light loads while responding promptly and with adequate reserve when the load rises, keeping the plant safely within its limit throughout the daily and seasonal swings in nitrogen load.
Implementing ABAC in SCADA means adding the ammonia loop on top of an existing dissolved oxygen loop and letting it write the DO setpoint. The ammonia analyzer's reading, the ammonia setpoint, the resulting DO setpoint, the measured DO, and the blower or valve output all become tags that operators can see and trend together, which is important because the value of the strategy is only realized if operators can confirm it is behaving. Seeing the DO setpoint ride up and down through the day in step with ammonia is the visible proof that the plant is aerating to demand rather than to a fixed number.
The strategy leans heavily on the ammonia measurement, so sensor health is central. An ammonia analyzer that drifts low would make the plant think it has more margin than it does and could push aeration too far down, risking a limit exceedance, so drift compensation and regular verification against laboratory samples are important safeguards. Some implementations blend or cross-check the online reading, apply an offset from periodic grab-sample comparisons, and flag the reading as suspect if it stalls or diverges, so a drifting sensor is caught before it misleads the controller.
Interlocks and limits protect the plant when things go wrong. A minimum dissolved oxygen setpoint stops the ammonia loop from ever starving the basin, and a fallback is defined for when the ammonia analyzer fails or is flagged bad, typically reverting to a safe fixed DO setpoint so the plant continues to nitrify conservatively rather than trusting a dead sensor. In a cloud SCADA platform such as Merobix, these interlocks, the sensor quality flags, and the whole ABAC control chain are visible and alarmable in one place, so an operator overseeing several plants can trust that each one is either saving energy under valid ammonia data or safely reverted, and can be alerted the moment a sensor drifts or a plant falls back.
Ordinary DO control holds a fixed dissolved oxygen setpoint chosen conservatively to always nitrify. ABAC instead measures effluent ammonia and uses it to move the DO setpoint up and down, aerating harder only when ammonia rises and relaxing when it falls. It controls the outcome the permit actually cares about, low ammonia, rather than a fixed oxygen proxy for it.
A fixed DO setpoint must be set high enough for the worst-case load, so for most of the day the plant over-aerates and wastes blower power. ABAC lowers the oxygen target whenever the ammonia reading shows the plant has margin, spending aeration energy only when the nitrogen load genuinely needs it. Since aeration is a plant's largest electricity use, trimming that routine surplus can meaningfully cut energy.
A drifting or failed ammonia sensor could mislead the controller, so ABAC implementations guard against it. Drift is managed with regular verification against lab samples and offset correction, and the reading is flagged as suspect if it stalls or diverges. If the sensor fails or is flagged bad, an interlock reverts the plant to a safe fixed DO setpoint so it keeps nitrifying conservatively rather than trusting a dead measurement.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.