Every part of a standby generator gets attention except the one it cannot run without. Shops check batteries, change oil, exercise the engine, and test the transfer switch, while the diesel in the tank sits for months or years, quietly changing. Then the outage comes, the engine runs hard on whatever is actually down there, and a machine with a spotless PM history shuts down with clogged filters hours into the event it existed to cover.
This guide is about the tank: why stored diesel degrades, why the failure shows up during the real outage instead of the weekly exercise, and what a fuel program that actually protects the asset contains.
Three ways stored diesel goes bad
Oxidation and sediment
Diesel is not chemically inert. In storage it reacts with oxygen, and the reactions form gums and dark sediment that settle toward the tank bottom, and varnish that clings to wetted components. Heat and temperature swings accelerate the process. Aged fuel darkens, hazes, and carries more particulate than the day it was delivered.
Water
Water gets into storage tanks through condensation as temperatures cycle, through compromised fills and vents, and occasionally with a bad delivery. Water is denser than diesel, so it settles into a layer on the tank bottom, out of sight of anyone who only ever looks at the gauge. On its own it corrodes steel, degrades combustion, and damages injection components. And it enables the third problem.
Microbial growth
Microbes live at the interface between the water layer and the fuel above it, feeding on the hydrocarbons. The colony sheds biomass that operators recognize as dark slime on filter elements, and its byproducts are acidic, which accelerates tank corrosion from the inside. Once established, growth does not stay put: it spreads with the fuel through the supply system. Modern ultra-low-sulfur diesel and biodiesel blends are commonly described as more hospitable to water and microbial problems than the fuels older tanks were designed around, which is part of why a tank that was trouble-free for a decade can foul now.
Why the failure picks the outage, not the exercise
The cruelest property of a fuel problem is its timing. A routine exercise runs briefly and gently on a still tank: the water layer and the sludge sit undisturbed below the pickup, and a short, light run proves very little about what is down there. The tank passes the only test it is ever given.
A real outage is a different event. The engine runs for hours at load and pulls the tank level down toward the sediment. Vibration and flow stir the water layer and the accumulated sludge into suspension, and the pickup starts feeding the engine what the tank was hiding. Filters do their job and clog doing it, mid-event, with the building dark. The machine did not fail; the fuel did, and it failed on exactly the day it mattered.
The operator's read
What a fouling tank looks like before it fails
- Fuel samples that come up dark, hazy, or layered instead of bright and clear.
- Dark slime or paste on filter elements at changeout.
- Filter change intervals that keep shortening on the same unit.
- Water accumulating in the separator or found at the tank bottom.
- Corrosion staining around fittings, fills, and the tank floor.
Any one of these is a reason to sample and inspect rather than wait for the calendar. All of them together mean the tank is already telling you how the next extended run ends.
What a working fuel program contains
A fuel program is scheduled work, on the PM calendar, with a record for every visit, and it runs on a handful of recurring tasks:
- Sampling. Pull fuel from the tank bottom, where water and sediment live, not just the supply line. Look at it, and send it out for laboratory analysis when condition or the governing requirements call for it.
- Water checks and removal. Check for a water bottom on a recurring cadence and pump it off when found. Controlling water is the single most leveraged move in the whole program, because it starves the microbial problem of its habitat.
- Treatment decisions. Stabilizers and biocides exist, and whether and when to use them is a judgment call made with the OEM's guidance, the fuel supplier, and the product labeling. A treatment poured on top of an unmanaged water problem is a receipt, not a fix.
- Polishing. Circulate the tank through staged filtration and water separation when sampling says the fuel is carrying contamination. Heavily fouled tanks may also need physical cleaning.
- Housekeeping. Keep tanks reasonably full to shrink the air space where condensation forms, keep fills and vents sealed and intact, and keep the engine-side filters on their own schedule.
What polishing is, and what it is not
Fuel polishing draws from the tank, ideally from the low point where the contamination sits, passes the fuel through staged particulate filtration and water separation, and returns it. Done properly it removes water, sediment, and biological material, and the difference is visible in the sample jar.
What polishing does not do is turn old fuel into new fuel. Oxidized, chemically aged diesel is generally not restored by filtration, and a polished tank with an uncorrected water source will re-foul. Polishing is the cleanup step inside a program of sampling, water control, and treatment. Sold and scheduled that way, it keeps tanks honest for years. Sold as a one-time miracle, it disappoints on schedule.
Where the standards fit
Standards for emergency and standby power systems treat the fuel supply as part of the system: stored fuel is expected to be maintained, and periodic testing of stored fuel is a common expectation. The specific intervals, test methods, and acceptance criteria come from the governing standard, the adopted edition, the OEM, and the authority having jurisdiction, and healthcare and other life-safety occupancies sit at the strict end of that range. As with everything else in this trade, the requirement travels with the site, so confirm it there rather than assuming one cadence fits every tank.
For the service shop there is a second implication: fuel work is billable, recurring scope. Sampling, water checks, and polishing belong in the service agreement as their own line items, priced deliberately, the same way load bank testing does. The agreement guide covers where those lines go, and the PM contract pricing guide covers how to price them.
The record makes the program real
A fuel program that lives in a technician's memory is a fuel program that dies with a resignation letter. Each visit should leave a record: which tank, what was found, what was pulled, what was treated, who did it, and when. For compliance accounts that record is part of the evidence package the facility shows its surveyor; for everyone else it is how you prove the tank that failed was not one of yours.
Where PowerOps fits
In PowerOps, fuel work runs as scheduled PM: sampling, water checks, and polishing visits are recurring tasks on the PM calendar that generate work orders, so the cadence you sold is the cadence that reaches the dispatch board. A person still assigns and completes every job; nothing advances on a timer. Each completed visit becomes an attributed record: the named technician, the server timestamp, the readings and observations, and the photos of the sample jar and the filter element, captured in the field on the mobile app.
The equipment registry carries each unit's fuel type alongside make, model, serial, and kW rating, and the full service history stays on the unit. When a facility manager asks what has been done about their fuel over the last two years, the answer is a scrollable history with names and dates on it, produced in seconds.