TwinEdge Water OS
Water OS for connected water treatment plant operations.
TwinEdge Water OS connects source water, treatment process, chemical dosing, lab and LIMS evidence, distribution, water quality, regulatory deadlines, maintenance, field work, CMMS/EAM, and governed AI into one operating layer for water utilities.
Treatment operations
Chemical dosing
Water quality
Distribution network
CMMS and field
Compliance evidence
Water OS is the operating system for water treatment, quality, distribution, and field action.
Platform in action
Water OS across command, treatment, quality, chemicals, distribution, and action
Use the operating map, command center, treatment plant operations, chemical operations, and semantic board views to show how plant and utility workflows operate from one connected Water OS layer.
Water OS connected system map
The operating map shows source systems, treatment process, storage, distribution, quality, chemicals, CMMS, evidence, validation, and AI context working together.
Water OS command center
Operators see incidents, alarms, backlog, recommendations, actions, domain state, assets, and work links from one command surface.
Water treatment plant operations
Plant process context makes intake, treatment, storage, distribution, chemical dosing, quality forecast risk, and engineering audit paths visible together.
Chemical dosing operations
Chemical operations connect dose controls, residual targets, pump parameters, safety context, inventory, and operator response.
Semantic board
Shared water KPIs, source coverage, confidence, and board packs give operators and leaders the same governed view of performance.
Workflow
How the water operating system works
Connect industrial sources, build trusted context, govern recommendations, and turn approved decisions into operational work.
Connect plant and utility systems
Bring SCADA, PLCs, sensors, historian tags, GIS, LIMS, lab results, permits, CMMS/EAM, maintenance records, field evidence, and regulatory deadlines into one water operating context.
Build one operating spine
Map source intake, process units, chemical systems, reservoirs, pressure zones, service areas, sampling locations, work, and compliance objects to semantic KPIs, validation gates, and evidence trails.
Turn context into governed action
Use command-center workflows, AI copilots, treatment recommendations, sampling routes, work orders, chemical reorder paths, water-loss investigations, and compliance packs with approval and replay.
Capabilities
Water OS capabilities
Water OS is the operating package that connects water treatment plant operations with quality, compliance, distribution, maintenance, and field execution.
Treatment command center
Operator views for source protection, intake, coagulation, filtration, disinfection, clearwell storage, distribution pump stations, incidents, alarms, shift handoff, and priority actions.
Chemical and process optimization
Dose targets, residuals, jar tests, SDS context, chemical inventory, reorder workflows, process envelopes, engineering audit paths, and operator-approved optimization runs.
Quality, lab, and regulatory evidence
Sampling plans, batches, results, QA/QC, chain of custody, MCLs, exceedances, regulatory calendar, obligations, PFAS, LCR, TCR, CCR, DMR, correspondence, and report evidence.
Distribution and water loss operations
Storage, pressure zones, PRVs, DMAs, NRW scorecards, minimum night flow, bursts, leaks, acoustic logger and satellite review, pressure management, and service-impact context.
Maintenance and field execution
AssetOps EAM, work orders, PMs, route sequencing, mobile field work, hydrant inspections, backflow tests, instrument maintenance, photos, measurements, closeout, and audit-ready field evidence.
Spine, readiness, and governed AI
Canonical water objects, identity resolution, source readiness, semantic KPIs, object 360 profiles, validation gates, operations health, evidence lineage, AI copilot, approvals, and replay.
Operating spine
One water context for the plant and the utility
Water OS connects plant process context with quality, distribution, maintenance, field, and compliance workflows so recommendations can become traceable action.
Source-to-distribution model
Source protection, intake, treatment units, chemical dosing, storage, pressure zones, customer taps, hydrants, backflow devices, and sampling points are represented as connected operating objects.
Semantic KPIs and validation
Energy intensity, chemical cost, water quality confidence, PM compliance, sample lifecycle, source coverage, readiness, and route gaps are validated before operational action.
Evidence that follows the work
Telemetry, lab evidence, operator notes, field photos, CMMS activity, regulatory obligations, and AI recommendations remain connected for audit, replay, and reporting.
Workflows
Water treatment workflows that move from signal to action
These are the operating loops a treatment plant team runs every day.
Quality exception to corrective action
An exceedance or forecast risk links to affected process units, samples, limits, operator review, field task, corrective action, and report evidence.
Chemical stockout to purchase and dose plan
Chemical demand, residual trends, tank inventory, SDS, vendors, reorder rules, purchase path, and dose changes are visible before operators approve a change.
Network issue to field response
Pressure, DMA, water-loss, hydrant, backflow, and customer-impact context routes investigation, work orders, sampling routes, and public notice workflows.
Water OS scope
Water treatment plant operating system coverage
The scope stays focused on source-to-tap treatment, quality, distribution, maintenance, field execution, and compliance workflows.
Engineering controls
Engineering controls for industrial AI.
TwinEdge can show real telemetry, local inference, protocol flows, and agent traces without claiming uncontrolled autonomy or SCADA replacement.
Read-only first
Physical writeback is disabled by default and recommendations pass through approval gates.
Replayable evidence
Plans, diffs, source context, and approval history remain available for review.
Deployment choice
Cloud-connected, local, and offline paths support evaluation without forcing one architecture.
Source system respect
TwinEdge works above SCADA, historians, CMMS, GIS, LIMS, ERP, and data lakes rather than pretending to replace them all.
Outcomes
Why water utilities use it
The benefit is operational coordination: fewer disconnected screens, faster action from evidence, and compliance context that stays attached to the work.
Operators and supervisors
See plant state, quality risk, chemical status, distribution impacts, incidents, recommendations, and work links without switching across SCADA, LIMS, GIS, CMMS, and spreadsheets.
Water quality and compliance teams
Trace every result, exceedance, obligation, deadline, corrective action, and report package back to source evidence and approved operational context.
Utility leadership
Understand risk, backlog, chemical cost, water-loss exposure, compliance readiness, and response performance from one operating picture.
Connected platform
How Water OS works with existing utility systems
Water OS does not replace every operational system. It gives treatment plant teams one governed operating layer across data, decisions, work, and evidence.
SCADA, PLC, historian, sensor, GIS, LIMS, lab, CMMS/EAM, permit, and customer systems keep their role.
Water OS maps those systems into source, treatment, chemical, quality, distribution, asset, work, and compliance objects.
Command center, sampling routes, maintenance work, field closeout, chemical reorder, and compliance packs use the same evidence.
AI recommendations stay governed with validation gates, approvals, audit history, and replay.
ERP, procurement, SAP, Oracle, Microsoft Dynamics, REST, and MCP integrations move approved context into enterprise workflows.
Edge and cloud deployment options support plant, utility, and offline operating needs.
Evaluate TwinEdge
Reduce utility fragmentation with one operating layer.
Start with a treatment plant and its connected quality, chemical, distribution, maintenance, and compliance workflows, then expand across the utility using the same governed Water OS spine.