Skip to main content

Aethr Industrial Intelligence / Water

Aethr Water Intelligence

Intelligence for how industry understands, uses, recovers, and reuses water.

Aethr Water Intelligence is AETHR's long-term programme for building the intelligence layer through which industrial organizations understand, use, recover, reuse, and manage water. We are developing systems that combine model reasoning, plant context, operational data, validated engineering tools, and human expertise to help organizations understand water across the full lifecycle — from intake and treatment to process use, wastewater, recovery, reuse, and discharge.

Programme
Aethr Water Intelligence
First R&D project
Project-Indofin
Status
Active development / R&D

Why water

We begin with water because it touches everything.

Industrial water is not one isolated utility. It passes through production, cooling, boilers, treatment systems, cleaning, heat exchange, chemistry, wastewater, recovery, reuse, and environmental discharge. A single water decision can affect energy consumption, equipment reliability, product quality, chemical use, operating cost, compliance, and production continuity.

That makes water an unusually demanding environment for industrial intelligence. To reason about it well, a system must combine incomplete measurements, physical constraints, engineering calculations, historical context, economics, and human operational knowledge — exactly the kind of problem Aethr Industrial Intelligence is being built to solve. Not a market slide: a technical proving ground.

Water thesis

Use the right quantity of water, at the right quality, in the right process — with the highest practical reuse and the lowest avoidable waste, while preserving safety, economics, reliability, and compliance.

Water is a system of trade-offs, not a single KPI. Reducing intake can raise treatment complexity; higher concentration cycles alter scaling and corrosion risk; a reuse stream may need treatment before a given process; recovery can cost energy and chemistry; the cheapest operating point can carry reliability risk. AWI never optimizes one metric in isolation — it helps operators see system-level consequences across quantity, quality, energy, chemistry, reliability, equipment life, production, treatment cost, reuse potential, discharge, and compliance.

System

The industrial water lifecycle.

SOURCE / INTAKERAW WATER TREATMENTDISTRIBUTIONPROCESS / UTILITIESWASTEWATER COLLECTIONTREATMENTRECOVERYREUSEREUSEDISCHARGE · CONTROLLEDOVERLAY · QUANTITY / QUALITY / ENERGY / CHEMISTRY / COST / RELIABILITY / COMPLIANCE
An industrial systems diagram: source to reuse with a controlled discharge branch, overlaid with quantity, quality, energy, chemistry, cost, reliability, and compliance flows.

Operations

What AWI is intended to do.

01

System state

Understand what the water system is actually doing.

Build the most credible operational picture from imperfect evidence — reconciling sensor telemetry, flow meters, lab measurements, mass balances, equipment state, historian data, and operating context into a coherent representation of plant water behaviour: where water comes from, where it goes, what quality it has, how much is consumed, where losses occur, and what evidence supports the picture. The goal is not another dashboard.

02

Cause & anomaly

Investigate why the system changed.

Identify abnormal behaviour — unexpected consumption, mass-balance gaps, quality drift, treatment-performance changes, sensor disagreement, membrane degradation, cooling-water anomalies, unexplained discharge, recovery loss — and construct competing explanations: process change, instrument error, sampling error, data gap, or equipment behaviour, rather than forcing every anomaly into one explanation.

03

Use & performance

Find better operating choices within real constraints.

Evaluate alternatives across water quantity, required quality, energy, chemistry, equipment limits, production needs, operating cost, reliability, and compliance. The goal is not minimum water at any cost but the best practical operating point under explicit constraints.

04

Circularity

Find technically credible reuse opportunities.

Identify where water can be recovered, treated, cascaded, or reused without transferring unacceptable risk elsewhere — weighing source quality, destination requirement, contaminant thresholds, treatment options, membrane constraints, energy, chemical demand, recovery yield, equipment compatibility, and economics. This is where the circularity mission becomes concrete.

05

Operational trade-offs

Turn analysis into a decision an engineer can evaluate.

Compare alternatives with expected benefit, engineering constraints, evidence used, assumptions, uncertainty, trade-offs, and required verification shown. The system supports decisions; it never hides uncertainty behind one optimization score.

Operating principle

The model reasons. The system verifies. The engineer decides.

Generative models are useful for interpretation, synthesis, hypothesis generation, contextual reasoning, and natural-language interaction. But industrial water contains questions with deterministic answers — mass balance, unit conversion, hydraulic calculation, water-quality limits, membrane constraints, chemical relationships, equipment operating envelopes. Where correctness matters, AWI uses validated engineering tools rather than asking a language model to invent the answer.

PLANT DATA + DOCUMENTSSITE CONTEXTSPECIALIST MODELinterpret / reason / proposeVALIDATED TOOLScalculate / retrieve / verifyPOLICY + CONSTRAINTSEVIDENCE-BACKED RECOMMENDATIONENGINEER / OPERATORMODEL REASONS · SYSTEM VERIFIES · ENGINEER DECIDES
No direct model-to-actuator arrow exists. Every recommendation terminates at the engineer.

System architecture & maturity

The intelligence stack.

OMN is the research architecture. Darwin is the foundation-model family. Specialization adapts Darwin toward water and industry. The site intelligence system — model plus data, tools, memory, and policies — is what an engineer actually meets. AWI is that full programme and system layer, not one model.

1

Research

OMN research foundation

Architecture and training research from AETHR informs how future models are built and evaluated.

2

In development

Darwin foundation-model family

AETHR's emerging model family built from OMN research. Darwin does not power AWI in production today.

3

In development

Industrial / water specialization

Domain adaptation, engineering vocabulary, tool use, physical reasoning, industrial workflows, water-specific evaluation. Darwin-derived specialist models are intended to form the model layer of future AWI systems.

4

Active R&D

Project-Indofin

The first major R&D/product project through which AWI is being developed and validated — connecting plant context, engineering models, operational data, evidence, validated tools, and human workflows.

5

Pilot / planned

Site intelligence

Integration with real facilities under controlled, read-oriented, human-supervised conditions. No production deployments are implied.

OMNarchitecture researchDARWINfoundation-model familyINDUSTRIAL SPECIALIZATIONdomain adaptationWATER SPECIALIZATIONDarwin-derived specialistsSITE CONTEXT + TOOLS + MEMORYsystem layerAETHR WATER INTELLIGENCEprogrammeENGINEER DECISIONhuman authorityPROJECT-INDOFINfirst R&D vehicle ·builds + validates
Project-Indofin spans water specialization, the site-context system layer, and validation — the first R&D vehicle building and validating AWI.

First R&D project

Project-Indofin is where AWI becomes a system.

Aethr Water Intelligence is the long-term programme. Project-Indofin is its first major R&D and product project — designed to develop and validate the architecture that connects specialist AI with industrial water data, engineering calculations, plant context, evidence, and human decision workflows. It sits above SCADA, DCS, BMS, PLC control, safety systems, historians, and laboratory systems, connecting their information into an intelligence layer without replacing any of them.

PHYSICAL PLANT · equipment / pipes / treatment / utilitiesCONTROL SYSTEMS · PLC / DCS / SCADADATA SYSTEMS · historian / lab / CMMS / ERP / documentsPROJECT-INDOFIN / AWI INTELLIGENCE LAYER — CONNECTS, NEVER REPLACESSITE CONTEXTMODEL REASONINGVALIDATED ENGINEERING TOOLSPLANT MEMORYEVIDENCE + POLICY↓ ENGINEER / OPERATOR
The intelligence layer connects existing systems upward into recommendations. No replacement arrows.

Site architecture

A general model does not know your plant.

Around the model, AWI needs a site model (equipment, streams, water network, process topology, operating limits), live and recent context (flows, quality, temperatures, pressures, equipment state, lab measurements), document knowledge (P&IDs where permitted, manuals, SOPs, maintenance history, engineering limits), and plant memory (reviewed incidents, decisions, investigations, validated cases). This context normally remains external to model weights — and the architecture is vendor-neutral by intent, consuming approved information from SCADA, DCS, BMS, historians, LIMS, CMMS, ERP, documentation, and operating records through a future connector layer, without requiring infrastructure replacement.

SITE CONTEXTTELEMETRY · LAB · HISTORIANDOCUMENTS · PROCEDURESEQUIPMENT · LIMITSSPECIALIST MODELone componentRETRIEVALENGINEERING TOOLSPLANT MEMORYVERIFIED / TRACEABLERECOMMENDATIONENGINEERcontext stays external to weights · memory accumulates by review
The model is one component among retrieval, tools, and memory — converging on a verified recommendation the engineer owns.

Correctness

The plant can reject a plausible answer.

Industrial water obeys mass balances, flow continuity, water-quality limits, equipment envelopes, thermodynamics, chemical compatibility, membrane constraints, recovery ratios, and energy use. A fluent answer that violates them is not operational intelligence. Operational knowledge should accumulate — what happened, what evidence existed, what was concluded, what action followed — without uncontrolled learning: live plant data never silently retrains the model, and reviewed cases become future training or evaluation data only through a controlled process. Context first; training only when justified. Customer data stays customer-owned by default, and cross-customer learning happens only where explicit rights and governance permit.

Deployment philosophy

Begin with intelligence, not autonomous control.

Initial deployments are read-oriented, human-supervised, recommendation-oriented, and evidence-backed. The system may retrieve, explain, analyze, calculate, investigate, and recommend — it does not autonomously rewrite control logic, replace safety functions, or execute unrestricted process changes. Missing evidence stays visible: known, calculated, inferred, assumed, missing, and conflicting are distinct states, and when critical information is absent the correct response may be another measurement, a stated uncertainty, a deferred recommendation, or an escalation. Authority expands only with evidence: observe, explain, investigate, recommend today; supervised preparation later; bounded execution only when highly qualified; autonomous control is not a current AWI objective.

Success criteria

Measure outcomes that matter to the plant.

Eventually, AWI should be judged on operational outcome categories — stated without numbers until real pilot evidence exists:

  • water intake avoided
  • water recovered / reused
  • reduction in unexplained losses
  • treatment efficiency
  • energy impact
  • chemical consumption
  • wastewater and discharge burden
  • investigation time
  • operator decision time
  • equipment and reliability impact
  • compliance risk
  • economic value

Positioning

The goal is not another water dashboard.

Dashboards show measurements; AWI reasons over them — what is happening, why, what can change, what that change affects, and what evidence supports the decision. One cubic metre of water is not interchangeable with another: chemistry, contaminants, temperature, pressure, source, treatment history, and destination requirements decide usefulness. AWI reasons about quantity plus quality plus destination, never volume alone.

Relevant environments include power generation, chemicals, refining, manufacturing, metals and minerals, food and process industries, large cooling and utility systems, and other water-intensive operations — listed as relevant environments, not customers.

Programme status

Where the programme is today.

Aethr Water Intelligence is in active development, focused on the model, engineering, evaluation, and system architecture required to connect AI reasoning with real industrial water environments — with Project-Indofin as the first major R&D and product project validating the approach. No multi-plant deployments, production proofs, autonomous control, or commercial-scale savings are claimed.

Longer term, water is both a permanent programme and a proving ground: physical reasoning, time-series context, engineering tools, uncertainty handling, site integration, security, human workflows, auditability, and enterprise deployment learned here transfer to energy, operations, and broader Industrial Intelligence. The Darwin connection follows the decided hierarchy — OMN architecture, Darwin family, Darwin-derived industrial and water specialization, AWI system — with future AWI systems intended to use specialized Darwin-derived models where appropriate, never as a fragmented separate family.

Boundaries

What AWI is not.

  • a replacement for SCADA or DCS
  • a replacement for PLC or safety logic
  • a generic chatbot attached to plant data
  • another dashboard
  • an autonomous operator by default
  • a system that continuously retrains itself on live plant data
  • one water-specific foundation model disconnected from Darwin

Build water intelligence with us.

We are looking to work with industrial operators on real water systems where historical data, engineering context, and operational expertise can be used to develop and validate the next layer of industrial intelligence.