LIGHTING & SAFETY
Street and external lighting
Identify lighting faults sooner, plan maintenance with better information and assess energy use across outdoor assets.
Local authorities, campuses, housing estates and commercial sites often manage lighting spread across roads, paths, car parks and open spaces. Connected monitoring can reduce reliance on routine patrols or public reports as the only indication of a problem.
ON THIS PAGE
What we monitor
Real-world example: Hafnarfjörður, Iceland
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
Compatible controllers can report operating status, faults, energy use and other electrical information supported by the equipment. We assess luminaires, drivers, controller interfaces, electrical supplies and the existing management system before proposing a retrofit or integration.
02
Illustrative application scenario
For example, several lights on an estate report unexpected operating conditions. The maintenance team groups the affected assets, checks whether the issue is local or shared and plans a targeted visit. After repair, reported status and subsequent checks help confirm the outcome.
Where compatible controls are included, authorised teams may manage schedules or dimming profiles. These changes must follow an agreed lighting design and operational policy; energy savings must be balanced with the required illumination for the location.
REAL-WORLD EXAMPLE
Hafnarfjörður, Iceland
LORIOT describes a connected-lighting deployment with Flashnet and Rafal covering 6,000 streetlights. Controllers and a central management system support remote monitoring, control and lighting schedules that respond to daylight. LORIOT reports energy reductions of up to 35% for this deployment. It also shows how municipal network infrastructure can provide a foundation for additional applications.
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 asset-labelled status, energy trends and exceptions together with other estate applications. Data can be integrated from suitable controllers or an existing central-management system. The project defines which platform owns control commands, schedules and maintenance records to avoid conflicting instructions.
04
What a pilot should establish
Select representative lighting types and locations. Validate coverage, installation access, event reporting and energy measurements. Test local schedules and agreed fallback behaviour during communications loss before enabling remote control. Compare fault-discovery time, maintenance visits and energy use against the baseline.
A device showing offline does not by itself prove that a lamp is off. Device-agnostic design means we select connectivity and interfaces for the lighting estate; not every luminaire is suitable for the same retrofit.
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.
-
Compatible controllers can report operating status, faults, energy use and other electrical information supported by the equipment. We assess luminaires, drivers, controller interfaces, electrical supplies and the existing management system before proposing a retrofit or integration.
-
Bring asset-labelled status, energy trends and exceptions together with other estate applications. Data can be integrated from suitable controllers or an existing central-management system. The project defines which platform owns control commands, schedules and maintenance records to avoid conflicting instructions.
-
Select representative lighting types and locations. Validate coverage, installation access, event reporting and energy measurements. Test local schedules and agreed fallback behaviour during communications loss before enabling remote control. Compare fault-discovery time, maintenance visits and energy use against the baseline. A device showing offline does not by itself prove that a lamp is off.
-
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.