UTILITIES & EQUIPMENT
Fuel tank monitoring
Know what fuel is available, plan replenishment and investigate unexpected changes before they disrupt operations.
Connected tank monitoring gives estate and facilities teams visibility of fuel stored at generators, heating systems, depots and remote sites. It can support hotels, ports, public buildings, sports facilities and golf-course maintenance operations. For island estates, better stock information helps teams plan around delivery lead times and coordinate site visits.
ON THIS PAGE
What we monitor
Illustrative application scenario
Industry example: remote oil-field tank monitoring
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
Suitable level sensors or interfaces to existing tank gauges provide regular readings. With validated tank dimensions or a calibration table, these can be converted into estimated volume and percentage full. Trends can highlight refill events, consumption patterns and unexpected drops. Flow-meter or generator-runtime data can add context where available.
Device selection depends on the fuel, tank construction, mounting arrangement, measurement range and site conditions. Any equipment used in a hazardous area must be suitable for that location and installed by appropriately qualified personnel.
02
Illustrative application scenario
A hotel monitors its heating-fuel tank and a separate standby-generator tank. A low-level notification prompts the facilities team to check stock and arrange a delivery. After replenishment, the recorded level rise helps confirm the event. An unusually rapid fall triggers investigation of consumption, authorised withdrawals, sensor readings and possible leakage or theft; the reading alone does not establish the cause.
INDUSTRY EXAMPLE
remote oil-field tank monitoring
The LoRa Alliance publishes a MultiTech case study about Chevron oil-field tank monitoring using LoRaWAN. It provides an industrial example of remote tank visibility. Oil-field operations differ from estate fuel storage, so the sensing method and operating requirements must be assessed for each application.
Read the MultiTech / Chevron case study →
This is a third-party example published by the LoRa Alliance, not a Nesos IoT deployment.
03
What your team sees in NesosIQ
View tanks by island, site or asset, compare current readings and follow level history. Agreed thresholds can flag low stock or unusual changes, alongside device-health information where supported. Estimated remaining supply can be calculated where consumption data is sufficiently reliable; intermittent generator use requires particular care. Combine fuel information with utilities and plant monitoring to support operational decisions.
04
What a pilot should establish
Validate readings against the existing gauge or a suitable reference, confirm tank geometry and usable capacity, and test coverage and reporting intervals. Agree replenishment thresholds, delivery lead times and who responds. Review alert usefulness, data gaps and sensor-maintenance needs before extending to further tanks.
Routine telemetry complements inspections and the tank’s dedicated safety arrangements. It does not replace overfill protection, certified leak-detection systems or emergency procedures. Stock estimates are not assumed suitable for billing or custody transfer.
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 level sensors or interfaces to existing tank gauges provide regular readings. With validated tank dimensions or a calibration table, these can be converted into estimated volume and percentage full. Trends can highlight refill events, consumption patterns and unexpected drops. Flow-meter or generator-runtime data can add context where available. Device selection depends on the fuel, tank construction, mounting arrangement, measurement range and site conditions.
-
View tanks by island, site or asset, compare current readings and follow level history. Agreed thresholds can flag low stock or unusual changes, alongside device-health information where supported. Estimated remaining supply can be calculated where consumption data is sufficiently reliable; intermittent generator use requires particular care. Combine fuel information with utilities and plant monitoring to support operational decisions.
-
Validate readings against the existing gauge or a suitable reference, confirm tank geometry and usable capacity, and test coverage and reporting intervals. Agree replenishment thresholds, delivery lead times and who responds. Review alert usefulness, data gaps and sensor-maintenance needs before extending to further tanks. Routine telemetry complements inspections and the tank’s dedicated safety arrangements.
-
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.