/
Water/
Specialized fields/
Wastewater and sewer networksWastewater, measured before it overflows.
Sewers overflow in storms, pumping stations fail at night and treatment plants must meet their discharge permits. Level sensors in the network, overflow monitors, pumping station data and effluent and river quality give operators the view they need to prevent spills, report the ones that happen and show regulators and the public what reaches their rivers and coasts.
Plan a deploymentHow it worksStation Builder- Industry
- Water
- Measurements
- 5
- Sources cited
- 5
Water · Wastewater and sewer networks
What reaches the river
Sewers and treatment plants protect public health, but in storms combined sewers overflow, and pumping stations or plants can fail. Regulators and the public increasingly expect every overflow to be measured and reported. Observation lets utilities prevent what they can and prove what happened.
What is measured
Levels, pumps, effluent and rivers
Level sensors over weirs and in manholes detect overflows and surcharge; pumping stations report wet well level, flow and status; effluent stations measure plant discharge; river and bathing water stations measure what reaches them; rain gauges explain why. Each reading carries its asset.
- Instruments
- Sewer levels · Pumping stations · Effluent quality · River quality · Rain gauges
The base node
Endpoints under the covers
Battery endpoints under manhole covers read level sensors and send short messages. The edge node signs every value, detects overflow start and end from levels and rainfall, and publishes event records without waiting for manual review. Every event keeps its raw levels.
Radio and links
LoRaWAN under the street
LoRaWAN reaches endpoints under covers from gateways on buildings and poles. Pumping and river stations use cellular, and treatment plants use the utility’s fibre. Each path is measured in the survey. Weak sites get an extra gateway nearby. Links are rechecked after street works.
- Links
- LoRaWAN · Public cellular · Fibre
How it works
From a weir to a public notice
A level rise above a weir is read under the cover, sent over LoRaWAN to a gateway and to the edge node. The node records the overflow start, checks rainfall, signs the event and sends notices to operations, the regulator and, where agreed, a public page.
From order to operation · Order
Scope overflows and permits
The scope reads the overflow inventory, the permits and the reporting duties. Nexus Observatory Inc. returns a sensor plan per overflow, pumping station and outfall, the radio design, the event and reporting workflow and a price per site. Priority goes to overflows near bathing waters.
Plan a deploymentFrom order to operation · Survey
Survey chambers and outfalls
Crews survey overflow chambers, critical manholes, pumping stations and outfalls with network staff, under confined-space procedures. They check geometry, weir levels, radio reach under covers and access, and record each site against the utility’s assets. Sites where signal under the cover is weak get a gateway placed nearer or a different antenna before installation.
From order to operation · Permits
Confined spaces and street works
Chamber work follows confined-space entry procedures and street works permits. Reporting arrangements are agreed with the environmental regulator, including what is published to the public and when. Every agreement and permit is kept with the site it covers, so the next crew knows the conditions before lifting a cover.
From order to operation · Build
Build for sewers
Level sensors, endpoints, pumping station gateways and river stations are built for corrosive, wet environments, configured with weir levels and enrolled with their identities and asset numbers. Each sensor is set for its chamber’s geometry and weir level, so an overflow is detected at the level where spilling actually begins.
Open the Station BuilderFrom order to operation · Install
Install under the covers
Gateways go up first, then sensors over weirs and in manholes, endpoints under covers, gateways at pumping stations and stations at outfalls and receiving waters. Each installation is checked and photographed. Covers are refitted securely and traffic management removed promptly, so streets are disturbed as little as possible.
From order to operation · Commission
Commission events end to end
Each device proves its identity, then levels are checked against manual measurements and weir levels, and event detection runs against rainfall. Notices are tested to the operator, the regulator and the public page. Results are signed into each site’s record before reporting begins.
From order to operation · Operate
Prevent, then report
Operators see levels rising with rainfall, pumping stations at risk and overflows as they start. Events are recorded with start, end and duration, and notices go to the regulator and public as agreed. Pumping station alerts reach the on-call crew with the station’s data, so a failure is handled before it becomes a spill.
From order to operation · Maintain
Clean, check and improve
Sensors are cleaned of fouling, checked against manual levels and moved as the network changes. Overflow records guide investment, and every change is recorded. Sensors that drift or foul are visible in the record, and their readings are flagged until they are cleaned and checked again. Records feed the annual return to the regulator.
Book field servicesData products
For operators, regulators and the public
Operators receive pumping alerts and overflow events; treatment managers see effluent compliance; regulators receive event records; environmental agencies and bathing water managers see receiving water quality; the public can see overflow notices. All from the same signed readings. Each carries its quality flags.
See the data productsEvidence
Overflow records that stand scrutiny
Weir levels, sensor checks, every event with start, end and duration, and every change are signed and kept. Monitoring follows the wastewater and bathing water rules that apply, so regulators and the public can trust the overflow record. Every published event links to its readings.
- Drawn against
- Directive (EU) 2024/3019 · Directive 2006/7/EC · EPA combined sewer overflow programme
What you get
Environmental and permit monitoring
Emissions, water quality, noise and dust monitoring for permit conditions, with traceable calibration and evidence bundles. Delivered as managed service and data licence, for industrial operators, municipalities, regulators. Scale: Site to portfolio. Service levels are written as numbers you can measure on your own dashboard.
Talk to salesNext step
Plan wastewater and sewer networks with us
Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for wastewater and sewer networks. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace.
Plan a deploymentOpen the Station BuilderOpen the Studio
01The place and its hazards
Where it runs, and what can go wrong.
Operating contextWastewater systems collect sewage and, in combined systems, rainwater through sewers and pumping stations to treatment plants that discharge to rivers and seas under permits. In heavy rain, combined sewers overflow by design at outfalls, and regulators increasingly require overflows to be monitored and reported. Treatment performance and receiving water quality are monitored under discharge rules.
Hazards
- Combined sewer overflows in storms
- Pumping station failures and spills
- Blockages and flooding from sewers
- Treatment failures and permit breaches
- Harm to bathing waters and ecosystems downstream
02What must be measured
What, where, how often, and under which rules.
Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below.
| Measurement | Where | Cadence | Sources |
|---|---|---|---|
| Sewer level and overflow events | Overflow chambers and critical manholes | Continuous, with event start, end and duration | 12 |
| Pumping station status, flow and wet well level | Every pumping station | Continuous | 2 |
| Effluent quality and flow | Treatment plant outfalls | Continuous, with permit sampling | 2 |
| Receiving water quality | Rivers, estuaries and bathing waters downstream | Continuous at key points | 34 |
| Rainfall | Rain gauges over the catchment | Continuous | 5 |
03The observation stack
From one base unit to a network.
The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol.
- 01
Base unit
A chamber endpoint: a level sensor read by a battery LPWAN device under a manhole cover.
Build a station → - 02
Site
A sewer catchment: overflow and manhole sensors, pumping stations, rain gauges and the receiving water stations.
Plan a site → - 03
Fleet
Every catchment, pumping station and plant run as one fleet, with one overflow and compliance record.
Managed offers → - 04
Network
Utilities, environmental regulators and bathing water managers share federated records and public overflow notices.
The open protocol →
- 01Water level gauge
- 02Flow meter
- 03Water quality sonde
- 04LPWAN endpoint
- 05LoRaWAN gateway
- 06Edge node (Wedge)
- 07Cellular modem/router
- 08Battery case
- 09Pole
Radio and links
LoRaWAN
Sensors under manhole covers have no power and weak signal; LoRaWAN reaches them from gateways on buildings and poles.
Radio and links
Public cellular
Pumping stations and river stations report over cellular.
Radio and links
Fibre
Treatment plants join the utility’s network over fibre.
Edge computeAn edge node detects overflow start and end from chamber levels, checks them against rainfall and publishes event notices without waiting for manual review.
PowerChamber endpoints run on batteries; pumping and river stations use site power or solar with battery backup.
04How it works
From the instrument to the product.
One observation’s path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks.
Wastewater and sewer networks: data path
– of 08
01 Instruments Measurement with sensor identity andcalibration 02 Field radio 03 Gateway 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products OGC SensorThings APIOPC UA (IEC 62541)LoRaWAN 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment 01 Water level gauge SDI-12 · RS-485 · Ethernet 02 Flow meter SDI-12 · RS-485 · Ethernet 03 Water quality sonde SDI-12 · RS-485 · Ethernet 04 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 05 LoRaWAN gateway Ethernet · RF · GNSS antenna 06 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 07 Cellular modem/router Ethernet · USB · RS-232 Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Overflow events with start, end andduration Pumping station alerts Effluent compliance records Receiving water quality 08 Battery case USB 09 Pole SDI-12 SDI-12 Ethernet LoRaWAN Ethernet Ethernet LTE/NR| Item | Equipment | Data ports | Protocols | Power in |
|---|---|---|---|---|
| 01 | Water level gaugeRadar, pressure or float gauge for river, lake, reservoir or tide level. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 02 | Flow meterOpen-channel or pipe flow meter (Doppler, ultrasonic, electromagnetic). | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 03 | Water quality sondeMulti-parameter sonde for temperature, conductivity, pH, dissolved oxygen and turbidity. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 04 | LPWAN endpointBattery-powered endpoint on LoRaWAN, NB-IoT or LTE-M that carries one or more sensors. | Analogue I/OSDI-12RS-485 | LoRaWAN, OMA LwM2M, CoAP | Internal battery, Energy harvesting |
| 05 | LoRaWAN gatewayMulti-channel LoRaWAN gateway that forwards uplinks to a network server and schedules downlinks within duty limits. | EthernetRFGNSS antenna | LoRaWAN, MQTT 5 | PoE, 12 V DC |
| 06 | Edge node (Wedge)Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains |
| 07 | Cellular modem/routerLTE or NR modem or router that uses a public carrier or private network as backhaul. | EthernetUSBRS-232 | 3GPP E-UTRA air interface, 3GPP NR air interface, OMA LwM2M | 12 V DC, PoE |
| 08 | Battery casePortable battery pack with DC outputs for field kits. | USB | Modbus | AC mains, HV DC, USB PD |
| 09 | PoleUtility, street or dedicated pole with clamp positions. | — | — | — |
How it scales
01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces.SITE
Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality.CLUSTER
×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites.FLEET
Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts.TRUST DOMAIN
TRUST DOMAIN
TRUST DOMAIN
×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange- Data in the field
- MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
- Telemetry
- OpenTelemetry OTLP.
- Control
- TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
- Data upstream
- At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
- Evidence
- DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
- Events
- Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
- Exchange
- OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.
05From order to operation
Every step, from the first call to a running site.
The same crew and the same record carry the work from scope to maintenance.
- 01 Order
Scope overflows and permits
The scope reads the overflow inventory, the permits and the reporting duties. Nexus Observatory Inc. returns a sensor plan per overflow, pumping station and outfall, the radio design, the event and reporting workflow and a price per site. Priority goes to overflows near bathing waters. 21
- 02 Survey
Survey chambers and outfalls
Crews survey overflow chambers, critical manholes, pumping stations and outfalls with network staff, under confined-space procedures. They check geometry, weir levels, radio reach under covers and access, and record each site against the utility’s assets. Sites where signal under the cover is weak get a gateway placed nearer or a different antenna before installation.
- 03 Permits
Confined spaces and street works
Chamber work follows confined-space entry procedures and street works permits. Reporting arrangements are agreed with the environmental regulator, including what is published to the public and when. Every agreement and permit is kept with the site it covers, so the next crew knows the conditions before lifting a cover.
- 04 Build
Build for sewers
Level sensors, endpoints, pumping station gateways and river stations are built for corrosive, wet environments, configured with weir levels and enrolled with their identities and asset numbers. Each sensor is set for its chamber’s geometry and weir level, so an overflow is detected at the level where spilling actually begins.
- 05 Install
Install under the covers
Gateways go up first, then sensors over weirs and in manholes, endpoints under covers, gateways at pumping stations and stations at outfalls and receiving waters. Each installation is checked and photographed. Covers are refitted securely and traffic management removed promptly, so streets are disturbed as little as possible.
- 06 Commission
Commission events end to end
Each device proves its identity, then levels are checked against manual measurements and weir levels, and event detection runs against rainfall. Notices are tested to the operator, the regulator and the public page. Results are signed into each site’s record before reporting begins.
- 07 Operate
Prevent, then report
Operators see levels rising with rainfall, pumping stations at risk and overflows as they start. Events are recorded with start, end and duration, and notices go to the regulator and public as agreed. Pumping station alerts reach the on-call crew with the station’s data, so a failure is handled before it becomes a spill.
- 08 Maintain
Clean, check and improve
Sensors are cleaned of fouling, checked against manual levels and moved as the network changes. Overflow records guide investment, and every change is recorded. Sensors that drift or foul are visible in the record, and their readings are flagged until they are cleaned and checked again. Records feed the annual return to the regulator.
06Data products and integration
What it delivers, to whom, and into which systems.
Data products
- Overflow events with start, end and durationOperators, regulators and the public
- Pumping station alertsNetwork operations
- Effluent compliance recordsTreatment managers and regulators
- Receiving water qualityEnvironmental agencies and bathing water managers
Integration
- Control system and historianPumping and plant data reach the historian over OPC UA.
- Regulatory reportingEvent records export in the formats the regulator requires.
- Public noticesAn agreed public page shows recent overflow events.
Exchanged through OGC SensorThings API, OPC UA (IEC 62541), LoRaWAN.
07Questions buyers ask
Before you scope it.
Can you monitor every overflow?
The plan covers the overflows your permits and regulator require, prioritised by impact.
Do sensors work under manhole covers?
Yes. LoRaWAN is chosen because it reaches under covers; the survey measures each location.
Can the public see overflows?
If you choose to publish, an agreed public page shows events as they are recorded.
Does this help reduce overflows?
Seeing levels rise with rainfall lets operators act earlier and shows where investment has the most effect.
08Resources
The sources behind this page.
Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does.
- 1Combined Sewer Overflows (CSOs)US Environmental Protection Agency
- 2Directive (EU) 2024/3019 concerning urban wastewater treatmentEuropean Union · 2024
- 3Directive 2006/7/EC concerning the management of bathing water qualityEuropean Union · 2006
- 4Directive 2000/60/EC establishing a framework for Community action in the field of water policyEuropean Union · 2000
- 5Guide to Instruments and Methods of Observation (WMO-No. 8)World Meteorological Organization
09Related
Use cases and solutions.
Use caseStreet flood observatory
Ultrasonic depth sensors on poles report street-level water depth as open data and alerts.The full use case →SolutionEnvironmental and permit monitoring
Emissions, water quality, noise and dust monitoring for permit conditions, with traceable calibration and evidence bundles.Solutions for water →SolutionMunicipal sensing and connectivity layers
City-wide LPWAN or private 5G as a shared layer for public sensors and services.Solutions for water →10Water: specialized fields
Other fields of this industry.
Specialized fieldRivers and flood warning
River level and flow, rainfall and cameras at gauging stations, flood forecasts and warnings issued by the authority, on links that keep working when the river rises.The full field →Specialized fieldGroundwater and aquifers
Water levels, salinity and abstraction in monitoring and production wells, on battery endpoints and LoRaWAN, for aquifer management, licensing and drought planning.The full field →Specialized fieldDrinking water treatment and networks
Water quality from source to tap, pressure and flow by district, acoustic leak detection and treatment plant monitoring, on secure networks kept apart from plant control.The full field →Specialized fieldLakes and reservoirs
Buoys and profilers for temperature, oxygen and algae, inflow and level, satellite views of blooms, so water suppliers and lake managers act before a bloom closes a source or a beach.The full field →Bring us the site.
Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details.
Plan a deploymentStation BuilderOpen the StudioTalk to salesRequest a quote