# Dispatch NOC puts 20,000+ active fuel tanks in one view

> A mid-market fuel carrier had tank-level inventory in Gravitate but no single operations view for finding low tanks across its customer base. We built a dispatch NOC dashboard that puts 20,000+ active tanks in priority order, so operators can spot inventory risk and turn it into the next delivery.

Client: Mid-Market Fuel Carrier
Published: 2026-10-01
Services: software-development, software-development/operations-tooling, software-development/systems-integration
Results: 20,000+ Active tanks visible; 7,000+ Open stores covered; 3,000+ Integration-monitored tanks
Stack: Gravitate, Go, React, WebSockets

## The problem

A mid-market fuel carrier manages inventory across thousands of customer sites. Gravitate held the tank readings, demand signals, planned drops, and projected runout dates, but dispatch did not have a wallboard built for scanning that whole operation at once.

That matters because a low tank is both a service risk and a revenue opportunity. When a tank needs fuel, the team needs to see it early enough to assemble the order and get a truck moving. Buried in individual records, those opportunities are easy to miss. On a dispatch-center TV, the team needed an immediate answer to a simple question: which customer tanks need attention now?

## What we built

We built a network operations center (NOC) dashboard around the way dispatch triages work. It pulls the carrier's store and tank data from Gravitate, normalizes it into one operational view, and sorts tanks by urgency.

The dashboard gives each tank a clear state: critical, low, healthy, or unknown. It distinguishes a tank that needs a delivery from one whose reading is stale or missing, so an unreliable signal does not masquerade as an empty tank. For inventory-managed sites, it also surfaces projected runout, accounting for planned deliveries where that is the right operational assumption.

Dispatch can filter the fleet by customer, market, product, monitoring method, signal quality, compliance status, and tank strategy. A first load comes from the dashboard API; live changes then reach every open screen over WebSocket. That makes the display useful both as a glanceable NOC board and as a working queue for an operator at a desk.

*A full-fleet view makes exceptions visible without hiding the healthy tanks that provide context.*

The Gravitate integration keeps Gravitate as the source of truth. The dashboard does not create another inventory system for dispatch to reconcile. It gives the team the view Gravitate's underlying data made possible.

*The compact board is designed to be readable at a glance on a dispatch-center display.*

## Results

At the time of the production data review, the dashboard covered 7,000+ open stores and 20,000+ active tanks, including 3,000+ tanks with integration-based monitoring. Instead of looking for exceptions one customer or store at a time, dispatch has one shared view of inventory that needs attention.

The operational result is a clearer path from signal to action: a low tank appears in priority order, the team can confirm the context, and dispatch can put together the delivery before the opportunity gets lost. Revenue impact has not yet been measured, so this case study reports coverage and system behavior rather than an estimated dollar return.