ACCESS, PEOPLE & OPERATIONS
People and activity monitoring
Understand how spaces are used so you can plan cleaning, facilities and capacity around observed demand.
Offices, campuses, libraries, leisure facilities and public buildings often rely on bookings or assumptions to judge utilisation. Aggregate occupancy and footfall information can reveal differences between intended and actual use, helping teams make better operational decisions.
ON THIS PAGE
What we monitor
Real-world example: A historic theatre in Rome
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
The right device depends on the question. Presence sensors indicate whether activity is detected; doorway counters estimate entries and exits; suitable occupancy sensors estimate numbers within defined areas. These are different measurements and should not be treated as interchangeable.
We favour aggregate, non-identifying information where it meets the purpose. Sensor technology, mounting, field of view and any data retained are agreed during design.
02
Illustrative application scenario
For example, a campus facilities team compares use of meeting rooms and shared areas across the week. It adjusts cleaning visits to activity patterns and investigates rooms that are regularly booked but little used. Combining utilisation with utilities data can also help identify opportunities to review operating schedules.
REAL-WORLD EXAMPLE
A historic theatre in Rome
Milesight describes a project with iComfort combining LoRaWAN occupancy and environmental sensing with people counters at a historic theatre. The deployment includes 175 presence sensors, 48 air-quality sensors and 17 people counters. Bringing occupancy, footfall and indoor conditions together supports decisions about how the building is used and operated, while addressing the practical constraints of a heritage setting.
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
Review trends by room, zone and time period, compare peak and quieter periods and assess changes after an operational adjustment. Scoped integrations can combine aggregate data with booking, facilities or building-management systems, where those interfaces are available.
04
What a pilot should establish
Test representative spaces against observed counts, including groups, multiple entrances and people remaining still. Agree the accuracy needed for the decision and assess counting drift, reporting intervals and maintenance. Measure whether the information improves scheduling and space decisions.
People should understand the purpose of monitoring. We agree access, retention and appropriate privacy assessment before deployment. The application is intended for space and service planning, not individual productivity scoring. Estimated occupancy is not an evacuation roll call or a substitute for a safety-critical capacity-control system.
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.
-
The right device depends on the question. Presence sensors indicate whether activity is detected; doorway counters estimate entries and exits; suitable occupancy sensors estimate numbers within defined areas. These are different measurements and should not be treated as interchangeable. We favour aggregate, non-identifying information where it meets the purpose. Sensor technology, mounting, field of view and any data retained are agreed during design.
-
Review trends by room, zone and time period, compare peak and quieter periods and assess changes after an operational adjustment. Scoped integrations can combine aggregate data with booking, facilities or building-management systems, where those interfaces are available.
-
Test representative spaces against observed counts, including groups, multiple entrances and people remaining still. Agree the accuracy needed for the decision and assess counting drift, reporting intervals and maintenance. Measure whether the information improves scheduling and space decisions. People should understand the purpose of monitoring. We agree access, retention and appropriate privacy assessment before deployment.
-
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.