Skip to content
Use CaseApr 20228 min read

Fuel Level Monitoring for Multi-Site Gas Stations With VX-Olympus

Smart EnergyVX-Olympus
fuel-monitoringsmart-energytank-levelgas-stationmulti-sitevx-olympusreorder-alertdelivery-reconciliationconvenience-store

You ordered a delivery last Tuesday. You think there is enough inventory to get through the weekend. You are not certain.

This is the operating posture of most convenience store and gas station networks that manage fuel levels manually. Not negligence — limitation. Underground tank levels are not visible, not easily measured, and not automatically reported. The standard approach is a combination of ATG (automatic tank gauge) readings downloaded at the site, manual dipstick checks, and scheduled deliveries based on historical consumption averages.

When consumption runs higher than the average — a road closure redirects traffic past one of your locations, a local event drives a weekend spike, a competitor runs out — the scheduled delivery arrives too late, or not at all.

Running dry costs money. Not just the lost revenue from vehicles that drove away. Also the customers who told their colleagues, the reputation damage on map apps that flag “out of fuel”, and the operations scramble to arrange an emergency delivery on short notice.

Continuous, real-time fuel level monitoring eliminates the uncertainty.


The Manual Model and Its Failure Points

Most multi-site fuel operators run one of two models:

ATG-based reading: The site’s automatic tank gauge records level readings, but those readings are pulled manually, viewed at a local display, or accessed through a proprietary ATG vendor portal that is not integrated with operations management. Each site is a separate login. Aggregating across 20 locations requires 20 manual checks.

Dipstick and schedule: Some locations — particularly smaller independent operators — still rely on manual dipstick readings taken once or twice daily and delivery schedules set monthly by a fuel coordinator. When a site runs high-volume, the schedule is already wrong.

Neither model gives an operations manager real-time visibility into aggregate inventory across their network.

The ATG reading is not the problem. The lack of real-time aggregation, alerting, and delivery integration is.


What VX-Olympus Adds to Fuel Level Monitoring

VX-Olympus integrates with both ATG systems and dedicated IoT tank level sensors to create a real-time, multi-site fuel monitoring layer.

Real-Time Level Visibility

Every connected tank reports its current level on a configurable interval — every 15 minutes, every hour, or on threshold events. VX-Olympus normalizes these readings into a standard data model: site, tank ID, product type, current level in gallons and as a percentage of capacity, timestamp.

The operations manager’s dashboard shows every site, every tank, at a glance. Color coding indicates status:

  • Green: Level above reorder threshold, no action required
  • Amber: Level below reorder threshold, delivery should be scheduled
  • Red: Level at critical threshold — immediate action required

No site visits. No manual log compilation. The current state of your entire network visible in one screen.

Configurable Alert Thresholds

Alert thresholds are configured per tank, per product type:

  • Reorder alert — fires when level drops below a configured percentage (e.g., 30% of capacity). Notifies the fuel coordinator that a delivery should be scheduled. Not urgent — planning window.
  • Critical alert — fires when level drops below the emergency threshold (e.g., 15% of capacity). Notifies the site manager and area manager immediately. Delivery required within the day.
  • Runout risk alert — fires when the estimated time-to-empty, based on current consumption rate, falls below a configured window (e.g., less than 18 hours to empty). Escalates to operations leadership.

Delivery Reconciliation

When a delivery arrives, VX-Olympus logs the pre-delivery level and the post-delivery level. The difference is the delivered volume. Compare that against the delivery ticket.

If the delivered volume per the ticket does not match the measured tank gain within a configurable tolerance, a discrepancy alert fires. This does not mean theft occurred — delivery measurement has inherent variance, and temperature affects volume calculations. But it means the discrepancy is flagged for review rather than silently accepted.

Over time, the delivery history for each site creates a consumption curve: average daily consumption, week-over-week trends, seasonal patterns. That data feeds better delivery scheduling — moving from calendar-based to consumption-based ordering.


Multi-Site Dashboard: What Operations Actually Sees

A fuel operations manager covering 15 locations opens VX-Olympus:

  • Network map view: Each site is a pin on a geographic map. Color indicates overall fuel status — green, amber, or red. Sites with active alerts show an alert badge.
  • Table view: Every site listed with current level percentage, estimated hours to reorder threshold, last delivery date, and last reading timestamp. Sortable by any column.
  • Site drill-down: Click any site to see individual tanks, full historical level chart, alert history, and scheduled delivery information.
  • Active alerts panel: Any site currently in amber or red status with time-since-alert and acknowledgment status.

No telephone calls to site managers to get status. No spreadsheet to compile. The operations picture is current, accurate, and available at any point.


Environmental Monitoring: Leak Detection Integration

Fuel operations carry EPA Spill Prevention, Control, and Countermeasure (SPCC) obligations. A leak from an underground storage tank is not just an environmental problem — it is an EPA enforcement event, a remediation liability, and an operational shutdown.

VX-Olympus can integrate with interstitial space sensors and overfill prevention equipment to monitor for:

  • Sudden level drops not correlated with dispensing activity — a tank losing fuel faster than it is being dispensed is a leak signature
  • Interstitial sensor readings — moisture or hydrocarbon detection in the secondary containment space of a double-wall tank
  • Overfill prevention system status — real-time status of mechanical overfill protection

These signals, correlated with the level monitoring data, give environmental compliance teams an early warning layer. A leak caught early is a containment response. A leak caught late is a remediation project.


Hardware Options and Integration Paths

VX-Olympus integrates with fuel level monitoring through several hardware paths depending on the existing site infrastructure:

ATG integration: Most commercial ATG systems (Veeder-Root, OPW, Incon) support data export via RS-232 serial or Modbus. VX-Olympus protocol converters read ATG data and feed it into the monitoring layer without replacing the ATG hardware. Existing investment is preserved.

Standalone IoT level sensors: Ultrasonic or pressure-based level sensors installed in tank openings report directly via LoRaWAN or cellular to VX-Olympus. Used for tanks without an existing ATG, or where the ATG integration is impractical.

Pulse meter integration: Fuel dispenser pulse meters track dispensed volume per transaction. VX-Olympus can receive pulse meter data via Modbus or dedicated IoT interfaces to reconcile dispensed volume against tank level changes in real time.

The combination of ATG readings, IoT level sensors, and dispenser pulse data creates a complete fuel inventory picture: received, stored, and dispensed — with every number sourced from a sensor, not a human estimate.


What the Deployment Looks Like

For a site with an existing ATG system:

  1. Install an IoT gateway at the site (typically in the back office) — one device covers all ATG and sensor data from the facility.
  2. Connect to the ATG via serial interface using a Modbus adapter.
  3. Configure VX-Olympus to receive the ATG data stream, map each tank to the VX-Olympus device model, and set alert thresholds.
  4. Configure notification routing — which users receive which alert tiers.

Typical deployment time per site: 2–4 hours, no disruption to fuel operations.

For a 20-site rollout, a 2-person installation team completes 4–5 sites per day. A full network is live in under two weeks.


The Outcome

Fuel management without real-time visibility is risk management through hope. VX-Olympus replaces the hope with data, and the reactive delivery scramble with proactive logistics.


Managing fuel across multiple sites? Talk to our team about a deployment scoped to your ATG infrastructure and site count.

Ready to see how this applies to your operations?

Every article describes real capabilities you can deploy today.