Data Center Fuel Monitoring: Telemetry, Alarms, Reorder Points and Burn Reconciliation
The number on the tank gauge is your runtime claim. Measure it reliably, alarm on it in hours, and check it every month against what the generators actually burned.
Data center fuel monitoring puts a live, temperature-compensated level on every generator tank and sends it to the BMS or DCIM and to your fuel supplier. Set alarms and reorder points in hours of runtime, not percent full. Each month, reconcile the gallons the tanks lost against generator run hours and load.
Why the tank level is the number that matters
Every runtime promise a data center makes, to a tenant, an auditor or its own operations team, comes down to how many usable gallons are in the tanks right now. Uptime Institute's Tier Standard sets a floor of 12 hours of fuel at N load for every Tier, and its guidance is blunt about what counts: the fuel that is always available after a failure, "not the best-case scenario of raw fuel storage." How much you should hold is covered in our data center diesel sizing guide. This page is about knowing what you actually have.
Standby tanks make that harder than it sounds. They sit for months, lose a few hundred gallons to each test, gain fuel from deliveries nobody watched, and move fuel between main and day tanks on their own. A sight glass or a monthly stick reading tells you where the level was when someone looked. Monitoring tells you where it is, how fast it's moving, and whether that matches what the generators did.
SensorsTank level sensors for generator fuel tanks
Most generator plants end up with more than one kind of sensor: a continuous level sensor on each tank, float switches at fixed alarm points as a backup, and the generator controller's own fuel sender on sub-base tanks. What each one is good at:
| Sensor | How it reads | Good at | Watch for |
|---|---|---|---|
| Magnetostrictive probe | Floats on a probe inside the tank; the gauge times a pulse to each float | Product level and water level from one probe, temperature at several points, and temperature-compensated volume (Gilbarco Veeder-Root) | A contact probe that needs a tank opening to install |
| Radar | Non-contact; microwave echo off the fuel surface | Holds up through vapor, temperature swings, internal obstructions and stratified fuel (ICON) | The beam has to clear ladders, fill pipes and internal piping |
| Hydrostatic (pressure) | Pressure of the fuel column at the bottom of the tank | No moving parts; tolerates suspended particles and light sludge | Diesel expands and contracts with temperature; ICON advises recalibrating after big seasonal shifts |
| Ultrasonic | Non-contact; sound echo off the fuel surface | Lower cost for small, clean, non-pressurized tanks | Diesel vapor, baffles and fill pipes can distort readings |
| Float switch | Opens or closes a contact at one fixed level | Dependable high, low and overfill alarm points, often as a failsafe behind a continuous sensor | No level reading between the switch points |
Accuracy figures on sensor pages are manufacturer claims for a specific model. Read the datasheet for the unit you are buying, and check how it reports water and temperature.
Gallons, not inches. A sensor measures height. Turning that into gallons takes the tank's capacity chart, and an error in that chart shows up in every reading. Net, not gross. Because diesel changes volume with temperature, the same tank reads differently at dawn and in the afternoon. Gauges that report temperature-compensated volume remove most of that noise, which matters when you reconcile. Water is a reading too. A probe that reports a water level turns a sampling chore into an alarm; what to do when it trips is in our fuel quality program.
BMS and DCIMGetting fuel levels into the BMS, DCIM and your supplier's hands
The fuel level usually needs to reach three places: the BMS that runs building alarms, the DCIM that the operations team watches, and the supplier who refills the tanks. The protocols are well established:
- Modbus. Published by Modicon in 1979, openly published and royalty-free. Modbus RTU runs over serial lines such as RS485; Modbus TCP runs over Ethernet. Many generator control panels, including ComAp and DeepSea models, offer a Modbus RS485 option (AKCP).
- BACnet. The building automation data protocol, published as ANSI/ASHRAE 135 and internationally as ISO 16484-5. It was written for building automation and control systems.
- SNMP. The network management protocol used by IT monitoring tools. Generator panels with an Ethernet port can often be read over SNMP (AKCP).
- Analog and relay outputs. Standalone tank gauges commonly offer 4–20 mA, Modbus RTU and dry-contact relay alarms (ICON).
| Path | What you get | Watch for |
|---|---|---|
| Generator controller over Modbus or SNMP | Fuel level from the controller's sender, run hours, load and engine alarms in one feed | It only sees the tanks wired to that controller |
| Dry contacts from the controller | A low-fuel alarm and other alarm states | Alarm outputs only: no actual fuel level reading (AKCP) |
| Standalone tank gauge into the BMS | A continuous level per tank, with trends and alarm points you set | If the gauge and the BMS speak different protocols, you need a gateway |
| Gateway or protocol converter | Translates between systems, for example Modbus generator data into an SNMP manager (DPS Telecom) | Another device to power, map and maintain |
| Supplier telemetry | The supplier sees the level too and schedules refills off it | Agree which reading is the system of record if it differs from the BMS |
Pick one system of record per tank. When the controller, the BMS gauge and the supplier's sensor disagree by a few hundred gallons, someone has to know which number drives orders and which drives audits. Write it down, and compare the two against a manual reading at each delivery.
AlarmsData center fuel alarms: set them in hours, not percent
"Tank at 60%" means nothing at 3 a.m. "Tank 4 has 36 hours left at full load" does. Convert every level to hours of runtime at the current burn rate, after subtracting the fuel below the pickup that the engine can't draw. A 2,000 kW set burns about 134 to 140 gallons an hour at full load and 75 to 82 at half load (our consumption chart), so 5,000 usable gallons is about 36 hours at full load and 61 to 67 hours at half load.
| Alarm | Trigger | Action |
|---|---|---|
| Refill due | Level drops below your keep-full trigger, usually after a test run or load bank test | Schedule a top-off; the supplier should see it too |
| Outage reorder point | Hours remaining fall to your runtime floor plus the delivery arrival window plus margin | Order the next load now (see reorder points) |
| Low fuel (code) | NFPA 110 section 5.5.2 requires a low-fuel switch on the main tank that trips when less than the minimum fuel for the system's class remains | Escalate. If this is the first alarm anyone acts on, you ordered late |
| Day tank low / high | The transfer system isn't keeping up, or is overfilling | Check transfer pumps, controls and their power source |
| High level / overfill | Level nears full during a delivery. Pump-filled tanks need a high-level alarm and automatic shutoff (HCAI) | Stop the fill |
| Water detected | Water float or probe reading above zero | Drain and sample; polish if it keeps coming back |
| Leak or unexplained drop | Containment or interstitial sensor, or a level falling with every engine off | Isolate and investigate. Uptime Institute calls leak detection crucial to fault tolerance |
| Sensor offline or stale | No new reading within the expected interval | Treat the level as unknown and take a manual reading |
The NFPA 110 low-fuel switch is set at the minimum fuel for the system's class, the amount the plant is supposed to hold at all times. When it trips, the tank is already below its design reserve. Set your reorder alarms well above it, and give every alarm an owner: a named person or role who responds, day and night.
How to set a fuel reorder point for a data center
Between outages, generator tanks barely move, so the routine refill is driven by tests: top off after each test window and load bank test. Our fuel supply agreement guide covers how to write that keep-full trigger into the contract. The reorder point that matters most is the one for an outage, when the tank is draining by the hour. Build it from four parts:
| Part | What it covers | Example: one 2,000 kW set |
|---|---|---|
| Runtime floor | The hours you have committed to keep in the tank at all times | 24 h × ~140 gph = 3,360 gal |
| Arrival window | What the set burns while the next delivery is on its way | 12 h × ~140 gph = 1,680 gal |
| Margin | Late trucks, higher load than planned, a slow fill | Your call; size it to how much a late truck would hurt |
| Unusable fuel | Fuel below the pickup that the engine can't draw | From the tank drawings |
| Outage reorder point | Order the next load when usable fuel falls to this level | 5,040 gal + margin + unusable fuel |
Full-load burn for a 2,000 kW set is 133.6–139.6 gph in our consumption chart; the example rounds up. The 24-hour floor and 12-hour window are illustrations, not recommendations.
Three adjustments make the number honest. Use the real burn rate once an outage starts, since actual load is often well below design (see actual load). Use the regional arrival window, not the normal one, once the event is widespread. And set it per tank, not per site. How the order cadence runs once the outage is long is in our extended outage planning guide.
ReconciliationReconciling generator runtime with fuel burn
Monitoring earns its keep in the monthly reconciliation. Fuel the tanks lost should match fuel the generators burned. When it doesn't, you have a leak, theft, a bad sensor, a short delivery or a generator running differently than you think, and you want to find out on a quiet Tuesday.
- Draw the boundary around the whole system. Count every tank that feeds the generator: main, day and sub-base. Fuel pumped from the main tank to a day tank isn't burn.
- Use comparable readings. Temperature-compensated volume if the gauge reports it; otherwise read at the same time of day.
- Work out fuel used. Opening level + gallons delivered (from the tickets) − closing level.
- Work out expected burn. From the controller log: run hours × load in kW × gallons per hour per kW. Our rule of thumb is 0.022 at 25% load, 0.042 at 50%, 0.059 at 75% and 0.074 at full load, or use your set's spec sheet.
- Compare and chase patterns. One odd month can be a timing issue. The same gap two months running is a problem.
A 2-hour test at 75% load
A 2,000 kW set should burn 104–120 gph at 75%, so 208–241 gallons for the test. Opening 9,800 gallons, no deliveries, closing 9,565: 235 used. In range.
Same test, 500 gallons gone
Twice the expected burn. Check the controller's load log first, then whether fuel moved to a day tank, then for an overnight drop with the engine off, then the sensor against a manual reading.
| Gap | Likely causes | Check |
|---|---|---|
| Tanks lost more than the engines burned | Leak, theft, transfer between tanks counted as burn, sensor drift | Containment alarms, level trend with engines off, manual reading. Our fuel theft guide covers the theft side. |
| Tanks lost less than expected | Generator ran at lower load than assumed, or the burn rate used is wrong for this set | Controller kW log; the spec sheet for that model and rating |
| Level rose with no delivery | Temperature, fuel moved back from a day tank, sensor fault | Compensated vs. gross volume; transfer system logs |
| Delivery doesn't match the ticket | Short delivery, gauge error, fill split across tanks | Gauge before and after each fill, against the ticket and the truck meter |
The same records answer a second question: what testing actually costs you. Monthly test burn by set, logged over a year, is the evidence behind a runtime claim and a fuel budget. The generator fuel calculator gives a quick estimate to check against.
FuelGoMonitored tanks and refills that follow the data
FuelGo runs data center generator fuel as one program on one account. On monitored tanks you see the level on your phone, and so do we: threshold alerts at the level you set, test-run consumption history that shows what exercising costs you in gallons, and refills that trigger on actual consumption instead of a calendar. Monitoring tracks levels across every generator and schedules deliveries, and every delivery is itemized by gallons, date and tank, which is the delivered side of your reconciliation. More on how the program fits a campus: data center fuel delivery.
We deliver generator fuel at 20 to 4,400 gallons per drop and transport loads up to 7,500, with fuel polishing and lab fuel testing when the water alarm or a sample says so (polishing vs. tank cleaning). Need temporary storage? Our rental tanks come with monitoring available or standard, depending on the model. Dispatch runs 24/7/365. Get a delivered quote or call 800-720-4546; a dispatcher replies within the hour.
Common questionsData center fuel monitoring FAQ
What is data center fuel monitoring?
Which tank level sensor is best for generator fuel tanks?
Can generator fuel levels go into our BMS or DCIM?
What fuel alarms should a data center set?
How do you set a fuel reorder point for a data center?
How do you reconcile generator run hours with fuel burn?
Why does the tank level change when the generator has not run?
Does FuelGo offer tank monitoring for data center generators?
Sources: Uptime Institute Journal, Fuel System Design and Reliability, June 2014 (12 hours at N for all Tiers; usable fuel as the baseline; sight glasses; leak detection and isolation) · California HCAI, 2025 Above Ground Fuel Storage reminder list (NFPA 110 5.5.2 low-fuel switch at the class minimum; 133%/100% tank sizing; high-level alarm and automatic shutoff on pump-filled tanks) · ICON Process Controls, Level sensors for fuel storage (ultrasonic, radar, hydrostatic and float switch behavior; 4–20 mA, Modbus RTU and relay outputs; temperature effects) · Gilbarco Veeder-Root, magnetostrictive probes (water detection, multipoint temperature, temperature-compensated volume, in-tank leak testing) · AKCP, Remote generator monitoring and alerts (Modbus RS485 on ComAp and DeepSea panels; SNMP over Ethernet; dry contacts are alarm outputs only) · DPS Telecom, Modbus to SNMP mediation for generators (gateway between protocols; fuel level low and engine hours as monitored points) · Modbus (Modicon 1979; openly published and royalty-free; RTU and TCP) · BACnet International, the BACnet standard (ANSI/ASHRAE 135, ISO 16484-5). Generator burn rates (gallons per hour by size and load, and gallons per hour per kW) are from our generator fuel consumption chart, built from manufacturer spec sheets. Code references are context only; check the edition your authority having jurisdiction has adopted.