ACCESS, PEOPLE & OPERATIONS
Asset tracking and utilisation
Spend less time searching for shared equipment and make better decisions about where assets are needed.
Maintenance tools, mobile equipment, cages and other shared assets can move between buildings and teams. Connected tracking can provide a recent location or zone, improving visibility without relying entirely on manual updates.
ON THIS PAGE
What we monitor
Real-world example: Asset visibility for a US utility
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
Suitable tags can report location, proximity to a defined zone, movement or selected condition data. Outdoor GNSS, indoor proximity and other positioning methods have different strengths. We agree the accuracy, update frequency and battery-life trade-off before selecting devices and connectivity.
02
Illustrative application scenario
For example, a facilities team needs to find equipment used across several buildings. A recent zone report narrows the search, while movement history helps identify assets that repeatedly sit unused in one area. The team can compare this information with its booking or inventory records before moving or buying equipment.
A reported location is only as current as its timestamp. Movement alone does not prove productive use, and a tracker is not a guarantee that lost or stolen equipment can be recovered.
REAL-WORLD EXAMPLE
Asset visibility for a US utility
TEKTELIC describes work with N-Smart for an unnamed major utility on the US East Coast. The solution combines Bluetooth asset tags with LoRaWAN infrastructure to improve visibility across warehouses, yards and field operations. TEKTELIC reports a 20% reduction in material loss and write-offs. The example shows how different technologies can work together around the practical task of finding and managing equipment.
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
Associate tag data with a meaningful asset name and review recent reported location or zone, movement events and device status where supported. Scoped integration with an existing inventory or maintenance system can avoid creating a second, disconnected asset register.
04
What a pilot should establish
Choose representative assets and movement routes, including storage areas and difficult radio environments. Compare reported locations with known positions and test attachment, durability and maintenance needs. Measure search time, data freshness and whether the information improves allocation.
The project defines what happens outside coverage and how offline or stale data is shown. This use case concerns equipment. Any proposal to track people requires a separate, clearly justified design with appropriate privacy arrangements.
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.
-
Suitable tags can report location, proximity to a defined zone, movement or selected condition data. Outdoor GNSS, indoor proximity and other positioning methods have different strengths. We agree the accuracy, update frequency and battery-life trade-off before selecting devices and connectivity.
-
Associate tag data with a meaningful asset name and review recent reported location or zone, movement events and device status where supported. Scoped integration with an existing inventory or maintenance system can avoid creating a second, disconnected asset register.
-
Choose representative assets and movement routes, including storage areas and difficult radio environments. Compare reported locations with known positions and test attachment, durability and maintenance needs. Measure search time, data freshness and whether the information improves allocation. The project defines what happens outside coverage and how offline or stale data is shown. This use case concerns equipment.
-
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.