UTILITIES & EQUIPMENT
Utilities monitoring
See where electricity, water, gas and heat are used, investigate avoidable consumption and measure the effect of operational changes.
Portfolio bills show the total, but often hide when and where waste occurs. Connected metering and submetering help property, finance and facilities teams build a more useful picture of buildings, tenants, common areas and major equipment.
ON THIS PAGE
What we monitor
Real-world example: CURRENTA at CHEMPARK, Germany
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
We assess existing meters, available data and approved interfaces before recommending new devices. Depending on the installation, readings may come from pulse outputs, compatible digital meters, utility data services or additional submeters. Electrical monitoring is specified and installed by appropriately qualified personnel; the same approach does not suit every supply.
02
Illustrative application scenario
For example, an office estate shows a high overnight electrical baseload and continuous weekend water use. Time-based profiles help the facilities team isolate areas for investigation, check schedules or equipment, and compare consumption after corrective work.
Where tariffs and appropriate emissions factors are supplied, the data can support estimated cost and carbon reporting. These calculations are only as reliable as the inputs and measurement boundaries; billing and financial settlement require an appropriately specified metering arrangement.
REAL-WORLD EXAMPLE
CURRENTA at CHEMPARK, Germany
Conneqtive describes retrofitting energy meters and using LoRaWAN to bring machine-level consumption into dashboards, reports and alerts. Its CHEMPARK case study reports a six-week implementation and a 95% reduction in data-collection effort. The useful lesson is operational: replacing manual readings can make consumption information easier to review and act on. The article’s energy-saving estimates are potential savings, not established results.
Read Conneqtive’s case study →
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
Bring interval readings, trends and agreed exception thresholds together by site, meter or supply. Compare buildings using relevant context such as floor area, occupancy and operating hours. Scoped data exports and integrations can support existing energy-management and reporting workflows.
04
What a pilot should establish
Start with a defined question: out-of-hours demand, unexplained water use or the impact of a plant upgrade. Confirm meter ownership, units, pulse factors, timestamps and data completeness. Compare readings with the source meter and establish a baseline before claiming savings.
Assess the actionable issues found, time spent collecting readings and measured consumption changes after intervention. Any savings depend on the action taken and changing building conditions, not monitoring alone.
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.
-
We assess existing meters, available data and approved interfaces before recommending new devices. Depending on the installation, readings may come from pulse outputs, compatible digital meters, utility data services or additional submeters. Electrical monitoring is specified and installed by appropriately qualified personnel; the same approach does not suit every supply.
-
Bring interval readings, trends and agreed exception thresholds together by site, meter or supply. Compare buildings using relevant context such as floor area, occupancy and operating hours. Scoped data exports and integrations can support existing energy-management and reporting workflows.
-
Start with a defined question: out-of-hours demand, unexplained water use or the impact of a plant upgrade. Confirm meter ownership, units, pulse factors, timestamps and data completeness. Compare readings with the source meter and establish a baseline before claiming savings. Assess the actionable issues found, time spent collecting readings and measured consumption changes after intervention.
-
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.