BUILDING CONDITIONS
Water leak detection
Find unexpected water sooner, direct the right response and reduce the time a leak can go unnoticed.
Leaks in risers, plant rooms, kitchens and unoccupied spaces can affect several properties before someone sees the damage. Connected detection gives housing, commercial-property and facilities teams a clearer starting point for investigation.
ON THIS PAGE
What we monitor
Real-world example: University of Lethbridge, Canada
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
Point sensors detect water at selected locations; sensing cable can cover a wider vulnerable area. Where suitable metering is available, flow and consumption trends can highlight continuous or unusual water use. These approaches complement each other: a floor sensor detects water where it is installed, while a meter may indicate a problem elsewhere on the supply.
02
Illustrative application scenario
For example, water reaches a sensor beneath a communal plant-room connection. A location-labelled event is routed to the agreed team, who check the area, isolate the source where appropriate and arrange repair. Meter trends can then help assess whether abnormal consumption has stopped.
Optional valve control requires a separate plumbing and control design, with permissions, local operation and failure behaviour agreed. It is not assumed to be part of a monitoring-only deployment.
REAL-WORLD EXAMPLE
University of Lethbridge, Canada
TEKTELIC describes a phased deployment with KB Innovations across university residences, expanding to more than 600 leak sensors in four buildings. The system combines location-based detection with dashboard, email and SMS notifications. TEKTELIC reports that alerts helped avert three major flooding incidents during 2022–23, illustrating the importance of connecting detection to a team able to respond.
Third-party project featured in the LoRa Alliance success-story directory. This is not a Nesos IoT deployment; reported results relate to this project.
03
What your team sees in NesosIQ
Organise locations by building, floor or asset, review wet/dry events and see device-health information where supported. Dashboards can combine leak events with utilities data, helping teams distinguish a local incident from a persistent consumption issue. Notification routes and any work-order integration are scoped around your response process.
04
What a pilot should establish
Survey likely leak paths and high-consequence locations. Test detection, radio coverage, notification delivery and the handover to the responding team. Measure time to acknowledge and investigate, event usefulness and sensor-maintenance requirements before extending the system.
Coverage depends on where devices are placed. Monitoring does not find every concealed leak or prevent damage on its own; the value comes from a tested detection-and-response process.
FAQS
Frequently asked questions
Quick answers about how this works, what your team sees and how a deployment starts. For anything else, talk to us.
-
Point sensors detect water at selected locations; sensing cable can cover a wider vulnerable area. Where suitable metering is available, flow and consumption trends can highlight continuous or unusual water use. These approaches complement each other: a floor sensor detects water where it is installed, while a meter may indicate a problem elsewhere on the supply.
-
Organise locations by building, floor or asset, review wet/dry events and see device-health information where supported. Dashboards can combine leak events with utilities data, helping teams distinguish a local incident from a persistent consumption issue. Notification routes and any work-order integration are scoped around your response process.
-
Survey likely leak paths and high-consequence locations. Test detection, radio coverage, notification delivery and the handover to the responding team. Measure time to acknowledge and investigate, event usefulness and sensor-maintenance requirements before extending the system. Coverage depends on where devices are placed. Monitoring does not find every concealed leak or prevent damage on its own; the value comes from a tested detection-and-response process. FAQS
-
No. Nesos IoT deployments use LoRaWAN, a low-power wireless standard designed for monitoring across buildings and estates, so devices do not rely on building Wi-Fi. Network design, gateway connectivity and a site survey are confirmed for each project so coverage fits the environment.
-
Your organisation does. Nesos IoT does not manage alerts or operational responses: your team defines the thresholds, notification routes and response procedures, and NesosIQ can connect to your existing systems through APIs and agreed integrations.
-
Yes. Suitable applications can share the same estate network and NesosIQ platform, so you can start with one challenge and add further monitoring as your needs grow. Our device-agnostic approach selects compatible equipment for each task.
-
We follow Discover, Survey, Pilot, Deploy, Integrate and Scale, starting with a focused pilot that validates measurements, coverage and the operational response. Nesos IoT is based in St Helier, Jersey, and works across the Channel Islands and beyond. Call +44 (0) 1534 753225 or email info@nesos.co.uk.
NEXT STEPS
From pilot to portfolio
We follow Discover, Survey, Pilot, Deploy, Integrate and Scale: agree the operational need, validate devices and coverage, commission the solution and connect it to the people who will act. Device choice, reporting intervals and integrations are confirmed for each project. Suitable applications can share the estate network and NesosIQ platform.