LIGHTING & SAFETY
Emergency lighting monitoring
Bring compatible test results and fault information into a clearer estate-wide view, so maintenance teams can target follow-up work.
Across housing blocks, workplaces and public buildings, emergency-lighting records can be spread across contractors, logbooks and local systems. Connected reporting can reduce manual collection and make missing results or recurring faults easier to investigate.
ON THIS PAGE
What we monitor
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
Where luminaires or controllers support it, integrations can provide function-test results, duration-test results and reported battery, lamp or communications faults. We survey the installed equipment and interfaces first. Compatible self-test or DALI emergency systems may support automated testing and reporting; capability is confirmed for the actual installation.
02
Illustrative application scenario
For example, a scheduled test reports a failure at a labelled luminaire in a communal corridor. The maintenance team reviews the result, arranges an inspection or repair and checks the follow-up test. A missing report is flagged separately from a confirmed test failure, so teams do not mistake a communications issue for a proven lighting fault.
03
What your team sees in NesosIQ
Review available test outcomes and exceptions by building and asset, with links to the agreed asset register or maintenance workflow where integrated. Portfolio reporting can support oversight of outstanding issues and help contractors arrive with better information.
04
What a pilot should establish
Reconcile asset labels, verify interface compatibility and compare reported results with the source system and on-site checks. Agree test schedules, outage behaviour, record retention and ownership of remedial work with the responsible team and competent specialists. Measure reporting completeness, time spent gathering records and time to investigate failures.
Remote reporting supports an emergency-lighting maintenance programme. It does not establish the adequacy of the lighting design, replace required inspections or automatically certify compliance. Test arrangements and applicable requirements remain part of the competent-person assessment.
Technical background: DALI Alliance: emergency lighting.
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.
-
Where luminaires or controllers support it, integrations can provide function-test results, duration-test results and reported battery, lamp or communications faults. We survey the installed equipment and interfaces first. Compatible self-test or DALI emergency systems may support automated testing and reporting; capability is confirmed for the actual installation.
-
Review available test outcomes and exceptions by building and asset, with links to the agreed asset register or maintenance workflow where integrated. Portfolio reporting can support oversight of outstanding issues and help contractors arrive with better information.
-
Reconcile asset labels, verify interface compatibility and compare reported results with the source system and on-site checks. Agree test schedules, outage behaviour, record retention and ownership of remedial work with the responsible team and competent specialists. Measure reporting completeness, time spent gathering records and time to investigate failures. Remote reporting supports an emergency-lighting maintenance programme.
-
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.