Allow-list
An agent can only write to tags declared for it.
Hydrira is designed around three facts: treatment plants are critical infrastructure, their output is public health, and the plant's existing automation must keep running if Hydrira stops. This page is the design posture; certifications are on the roadmap and not claimed.
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.
An agent can only write to tags declared for it.
Per-tag rate and magnitude limits, declared and versioned, inside documented process, permit, equipment and rollback bounds.
Shadow, assist or bounded, set per loop; nothing writes in shadow.
Interlock state, permit margin, excursion forecast, shift and operator presence evaluated before every write; a move that would thin a permit margin, a disinfection residual minimum or an integrity limit is blocked.
Anything above the threshold, every permit-adjacent move and every discharge release waits for a named person.
If Hydrira stops, the plant runs on its existing SCADA, PLC and DCS control and interlocks.
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.
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.
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 |
Stated plainly. Items on the roadmap are roadmap items.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Roadmap, first 6 months |
| Critical-infrastructure cybersecurity review | Edge and connectors | QUEUED Roadmap, first 6 months |
| SOC 2 Type II | Cloud control plane | QUEUED Roadmap, 6 to 12 months |
| Compliance and cyber assurance packages | Design partners | QUEUED Roadmap, 6 to 12 months |
| Safe Drinking Water Act, discharge permits, EU Water Framework, nutrient and PFAS rules | Grounding and records | RUNNING Design basis; not a certification of Hydrira |
| IP-safe and edge-only deployment | Plant data, permits, SOPs | RUNNING Design rule; on-prem option |
| Data | Where it stays |
|---|---|
| SCADA tags, analyzer streams, images | Tenant-scoped; on-prem or edge-only option |
| Permits, SOPs, process models | Tenant-scoped |
| Audit log and shift record | The plant's own storage, exportable |
| Surge, fouling and upset patterns | Federated, IP-isolated transfer across similar plant archetypes (planned, opt-in) |
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.
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.
The design posture, the data flows and the roadmap dates, written for a compliance lead and an IT/OT security lead.
↑↓ navigate↵ openesc close