Plant vision and online analyzers
Clarity, turbidity, foam and bulking, floc and settling, colour, leaks and overflows from cameras; turbidity, pH, chlorine, nutrients, TOC and flow fused from online analyzers, with drift and fault detection.
Autonomy in a treatment plant is a set of features that make action safe: cited reasoning, graduated control, bounded writes, permit gating, an immutable audit log, a shift record and a twin that rehearses the shift first. This page lists them one by one.
Illustrative scenario: one municipal activated-sludge wastewater plant with a membrane train, planning the next 24 hours after a rain forecast. Not a measured run.
Each of these exists because a treatment plant is compliance-critical, load-variable, energy-intensive and continuous.
Clarity, turbidity, foam and bulking, floc and settling, colour, leaks and overflows from cameras; turbidity, pH, chlorine, nutrients, TOC and flow fused from online analyzers, with drift and fault detection.
Influent and load, dose response, DO demand and biological state, membrane fouling trajectory, disinfection residual, excursion risk and energy, predicted early enough to act.
Closed loops on coagulant and polymer dose, DO and blower schedules, flux, backwash and cleaning timing, inside documented limits, at the autonomy stage you set.
Simflo ranks 50 to 500 candidate plans over the next 8 to 24 hours on permit margin, kilowatt-hours and chemical cost, and discards any that thin a margin.
Every recommendation carries a citation to the permit, SOP or regulation it relied on, through tenant-isolated, permission-aware retrieval.
Every reading, prediction, limit, approval and write in an append-only log, assembled into the shift record and drafted into the regulatory report.
Per-plant water-quality and energy history and per-operator corrections, versioned and scoped per tenant, so the next shift starts from what the last one taught.
Permia evaluates every planned move against the permit set and the excursion forecast; a move that thins a margin is blocked before it reaches the connector.
cuOpt schedules blowers and pumps, dosing windows, membrane cleaning and backwash and fleet maintenance routes under tariff, labour, asset and permit constraints.
Every Hydrira run is an ordered, inspectable sequence. This is run_scn_0418, an illustrative scenario: one municipal activated-sludge wastewater plant with a membrane train, planning the next 24 hours after a rain forecast. Ten steps, nine automatic, one human approval on the blower setpoint move, every action written to the shift record.
Intake-and-Screen · Flow, turbidity, ammonia and alkalinity at the headworks, and a 24-hour rain forecast that raises the expected influent by mid-afternoon.
Plant orchestrator · Simflo evaluates candidate dose, DO and flux plans over the 24-hour horizon and keeps the plans that hold permit margin through the surge.
Quality-and-Anomaly · Clarifier blanket, foam and colour from the basin cameras fused with turbidity, pH, nutrient and residual analyzers into one calibrated plant state.
Dose-and-Coagulate · Coagulant and polymer dose ramp for the surge window under turbidity, phosphorus, sludge and chemical-cost constraints, cited to the plant's dosing SOP.
Dose-and-Coagulate · A bounded setpoint move inside the declared rate and magnitude limits for the dosing pump, with the rollback value recorded first.
Aerate-and-Bio · Blower and DO setpoint schedule across the basins that meets the nitrogen and phosphorus targets at the lowest kilowatt-hours the biological state allows.
Plant orchestrator · The DO setpoint change is above the plant's threshold for this loop. The process engineer on shift reviews the predicted nutrient margin and approves.
Membrane-and-Disinfect · Flux held through the surge and the next backwash moved earlier, inside the integrity envelope; the disinfection residual minimum is untouched.
Compliance-and-Energy · Every planned setpoint checked against the discharge permit, the nutrient limits and the residual minimum, with excursion risk forecast for the horizon.
Quality-and-Conformance · Inputs, model versions, predictions, limits, the approval and every write appended to the immutable shift record the plant owns.
Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant. The log below is the scenario run, not a measured one.
Goal, plan, thought, action, observation, exactly as the orchestrator would record it.
Hold effluent turbidity, nutrients and disinfection residual inside the discharge permit for the next 24 hours while taking aeration energy and coagulant use to the minimum the permit margin allows.
Read influent and the forecast; rehearse the horizon on Simflo; fuse the plant state; compute dose and DO schedules; write the dose inside bounds; route the DO move for approval; hold flux and move the backwash; check the permit; commit the record.
Rain arrives mid-afternoon and the influent will rise by about a third. Dosing has to ramp before the surge, not after, and the DO schedule has to keep nutrient margin through it.
cuopt.solve_dose over a 12-hour window under turbidity, phosphorus, sludge and cost constraints; plc.write_setpoint on the coagulant pump inside the declared rate and magnitude limits.
The dose ramp holds predicted effluent turbidity under 2 NTU through the surge. The DO schedule saves energy but is above the threshold set for the aeration loop.
Energy never outranks permit margin. The DO change goes to the engineer with the predicted nutrient margin attached, and nothing is written until it is approved.
approve.request to the process engineer on shift; membrane.schedule_backwash to hold flux and move the next backwash ahead of the surge; permit.evaluate across the horizon.
Ten steps, one human approval, all parameters inside limit on the forecast, and the shift record written. Illustrative scenario; nothing here is a measured plant result.
A foam or breakthrough alert is only useful if it arrives before the lab result, and a dose or DO recommendation is only useful if it lands at the cadence the analyzers run. The design targets are under 100 ms per camera inference and 1 to 10 Hz sensor fusion on plant-edge GPUs, with the cloud used for training and simulation.
| Decision | Design target |
|---|---|
| Camera inference | <100 ms |
| Foam, clarity and anomaly vision | 15–30 FPS |
| Sensor fusion, SCADA and analyzers | 1–10 Hz |
The orchestrator retrieves over permits, process and SOP specifications, water regulations (the Safe Drinking Water Act, discharge permits, the EU Water Framework, nutrient and PFAS rules) and compliance and genealogy procedures. Retrieval is multi-tenant isolated and permission-aware, and every output is traceable to a source.
Simflo simulates the plant as it is today, across hydraulics, clarification and filtration, membrane fouling, oxygen transfer and biological response. Candidates that save energy or chemicals but thin a permit margin never reach the agents.
Two agents will want the same actuator. The orchestrator arbitrates on the run goal, with permit margin above everything, and the handoff is logged like any other step.
Chemical phosphorus removal (more coagulant) and biological phosphorus removal (more aeration) both reach the target; each agent proposes its own route.
Simflo scores both routes on permit margin, kilowatt-hours and chemical cost over the horizon; the permit margin is identical, so cost decides.
The biological route wins for this shift; the dosing agent holds coagulant at the clarity dose and the aeration agent takes the phosphorus target.
Both proposals, the arbitration and the chosen route are written to the shift record so a process engineer can see why.
A plant does not go from manual to bounded control in one step. Hydrira makes the stage explicit per loop, auditable and reversible at any time, and some decisions never leave the person.
| Stage | What the agent does | What the person does | When |
|---|---|---|---|
| Shadow | Predicts water quality, fouling, excursion risk and energy; writes nothing | Runs the plant as today; compares predictions to lab, analyzer and SCADA outcomes | First phase with every design partner |
| Assist | Recommends dose, DO, flux and cleaning moves with predicted quality, energy and permit impact | Approves, corrects or rejects each move; corrections train the models | After accuracy is proven against the plant's own baseline |
| Bounded | Writes to an allow-list of low-risk loops inside declared rate and magnitude limits | Sets the limits, watches the record, pulls the loop back at any time | Per loop, after the assist-mode gate and compliance sign-off |
| Exceptions | Escalates anything above the threshold, every permit-adjacent move and every release | Decides; the operator of record is never removed from compliance decisions | Always |
Nothing about a Hydrira run is implicit. The goal is declared, the plan is rehearsed on the twin, each step is typed, and the outcome is written to the shift record.
A run starts as a goal, becomes a plan, and executes as a graph of typed steps. The active path is always visible, always logged, always reversible.
Shadow, assist, bounded, exceptions. Each plant sets the stage per loop, and anything above the threshold, every permit-adjacent move and every discharge release decision waits for a named person.
The numbers Hydrira is engineered against, from the GPU utilization plan.
Design targets from the GPU utilization plan, all marked aspirational in the architecture. Nothing on this page is a measured plant result.
There is no SDK to download yet. What design partners get is the integration surface: connectors, an autonomy policy declared per loop, and an audit record for every reading, recommendation, write and approval. This is the shape of one record, illustrative.
// one write, as the audit log would hold it
{
"run": "run_scn_0418",
"step": "dose.write",
"agent": "agent.dose_coagulate",
"stage": "bounded",
"action": { "tool": "plc.write_setpoint", "tag": "DOS1.SP" },
"limits": { "max_step": "declared per tag", "per": "declared per tag" },
"evidence": ["analyzer.read_influent", "vision.fuse_state"],
"citation": "sop:DOSE-07 §3 · permit:NPDES-WWTP-A §II.A",
"permit_check": "inside margin",
"models": { "dose_response": "versioned", "policy": "versioned" },
"human": null,
"rollback": "38 mg/L",
"outcome": "42 mg/L · inside declared window"
}
The three people in a treatment plant whose week changes when the process runs itself, and what each of them needs from Hydrira.
Owns compliance, reliability, energy, chemicals and cost. Wants autonomous, compliant, lower-energy, lower-chemical treatment, and a number that justifies the spend.
Owns dosing, aeration, membrane and biological strategy, the process windows and the performance. Needs recommendations they can inspect, correct and trust before any loop is handed over.
Owns permit compliance, water quality, energy and environmental reporting and the licence to operate. Needs every action cited, logged and defensible in front of a regulator.
IT/OT and critical-infrastructure cybersecurity leads approve the deployment. There are no customer quotes on this site yet; design partners will be the first voices.
Hydrira reads and writes through the systems already in the plant. No parallel historian, no new HMI, no rip-and-replace. Connectors are built against each design partner's stack first; long-tail integrations are out of scope for the first release.
Plant SCADA, historians, PLC and DCS interfaces
Tag reads at 1 to 10 Hz, guarded setpoint writes, interlocks untouched
Coagulant, polymer, pH-adjust and disinfectant dosing controllers
Dose reads, bounded setpoint writes inside declared limits
Blower controls, DO and ammonia-based aeration control
DO and blower reads, bounded setpoint writes after approval
Membrane and RO skid PLCs, TMP, flux, conductivity, integrity monitors
Reads; flux and backwash writes inside the integrity envelope
Turbidity, pH, chlorine residual, nutrient, TOC and flow analyzers
Reads; drift and fault flags
Lab information systems, jar-test and grab-sample records
Reads for labels and calibration
Fixed cameras on clarifiers, basins, filters and membrane rooms; inspection robots
Streams fused at the edge; supervised routes
Utility MES, maintenance systems, permit and reporting systems, weather
Reads; shift record and report drafts written back
Hydrira writes to control equipment in a plant that keeps a community's water safe. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I + critical-infrastructure cyber review | Cloud control plane, edge | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| SDWA · discharge permits · EU WFD · nutrient and PFAS rules | Grounding and record-keeping | RUNNING Design basis for retrieval and the audit log |
| Per-tenant isolation | Data, memory, models | RUNNING Design rule |
| On-prem or edge-only deployment | Utilities, critical infrastructure | RUNNING Design option |
Hydrira supports your compliance records. It is not a certification, it does not replace your permit and it never removes the operator of record from a compliance decision.
One policy model, one audit trail and one set of energy, chemical, compliance and water-quality benchmarks across every plant in the fleet, with each site's permits, SOPs and process models kept private to that site.
The questions operations managers, process engineers and compliance leads ask in the first meeting.
Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside documented limits. Every design partner starts in shadow mode, where Hydrira predicts and writes nothing. Assist mode follows, where a process engineer approves each move. Bounded write-back comes last, per loop, after the accuracy gate and compliance sign-off, and can be pulled back at any time.
No. Permit-limit setpoints, disinfection residual minimums, integrity limits and discharge release decisions are read and checked, never written. Permia evaluates every planned move against the permit set and blocks anything that would thin a margin. The operator of record stays the operator of record.
The plant keeps running on its existing SCADA, PLC and DCS control and interlocks. Hydrira is supervisory, not primary. Loss of Hydrira is loss of advice, and the gap is recorded in the shift record.
Shadow mode starts with the SCADA tags, analyzer streams and lab records you already have. Accuracy is measured against your own lab and analyzer baseline, and the first-release plan converts to assist mode only when the number is proven. The design targets assume telemetry you already collect, not new instrumentation.
Telemetry, permits, SOPs and models are tenant-scoped, and an on-prem or edge-only deployment is available for utilities. Cross-plant learning is federated and IP-isolated, planned and opt-in: patterns for similar basins, membranes and influent regimes move, raw data does not.
Not yet, and the site does not claim it. SOC 2 Type I with a critical-infrastructure cyber review is on the roadmap for the first six months, Type II for the six to twelve month window. Safe Drinking Water Act, discharge permit, EU Water Framework and nutrient and PFAS rules are what the retrieval grounds on and what the audit log is aligned to; that is a design basis, not a certification.
The one with the clearest number. Aeration energy on an activated-sludge plant, coagulant cost on a dosing train or membrane run length on an RO or MBR train are the usual wedges, because kilowatt-hours, chemical invoices and cleaning counts are already measured. Turbix is the sensing wedge where visibility is the first problem.
Two to four utilities or industrial sites instrument one wedge process in shadow mode and baseline energy, chemicals and compliance from their own records. Assist mode proves accuracy and ROI with an engineer approving each move. Graduated autonomy follows on low-risk loops. Expansion adds adjacent processes, then fleet sites. Gates, not dates.
Shadow mode shows the perception, prediction and evidence features before any control feature is enabled.
↑↓ navigate↵ openesc close