Fuel

Fuel delivery, tank-telemetry-triggered.

Per-customer, per-tank, per-product thresholds. Degree-day forecasting for expected-empty date planning. Compartmented loading with product-incompatibility rules.

Tank telemetry · auto-dispatch

Each tank has its own product, threshold, and forecast. Crossing a threshold fires an order. Loading respects compartment incompatibility and hazmat-routing rules.

TANKS · LIVE TELEMETRY
T-018
92%
DIESEL
T-047
34%
GASOLINE
T-129
18%
DIESEL
ORDER FIRED
T-231
10%
GASOLINE
ORDER FIRED
T-304
56%
HEATING
DISPATCHER
Compartment loading + hazmat routing
  • ✓ Product incompatibility rules
  • ✓ Compartment sizing (1400 / 2100 / 1800 gal)
  • ✓ Truck dimension · bridge restriction
  • ✓ Degree-day demand forecast · next 3 days
ROUTE · TRUCK-42
TRUCK-42 · HAZMAT CL-2 180 GAL / 2 STOPS
01
T-129 · DIESEL · 900 gal
Compartment A · window 09:00–11:00
02
T-231 · GASOLINE · 900 gal
Compartment B · window 10:30–12:30
HAZMAT-AVOIDING ROUTE · 42 KM · 68 MIN

Operators in fuel come to Mycelium when their spreadsheets stop scaling — when every morning starts with an exception, when three branches or three airports have three different rule books, when a 45-minute customer window needs to become 30.

01

Dispatch when the tank says so.

Live tank-level readings trigger deliveries against thresholds per customer, per tank, per product. Degree-day forecasting adds the expected-empty date for planning runs, not just reactive ones.

  • Per-customer, per-tank, per-product thresholds
  • Degree-day forecasting for expected-empty date planning
  • Will-call and automatic delivery in the same optimization pass
02

Compartments, hazmat, corridors as constraints.

Compartmented loading respects product incompatibility and compartment size. Hazmat corridors — truck dimensions, placards, tunnel and bridge restrictions, time-of-day windows — ride with each route. Compliance exports for DOT, EPA, and state regulators.

  • Product-incompatibility rules across compartments
  • Hazmat routing with placard, tunnel, and bridge awareness
  • Compliance exports with no spreadsheet hand-off
The paradigm shift

The calendar stops dispatching. The tank does.

WEEKLY TEMPLATE · every customer, every Thursday
5trucks out today regardless of actual need
TANK-TRIGGERED · threshold crossing fires dispatch
2trucks out today, right-timed
Same customers. Same day. 3 unnecessary trips avoided by reading the tank instead of the calendar.
Capital deferral

Fewer trucks needed means deferred fleet capex. Optimization exposes unused capacity that was hiding inside the weekly template.

Labor alignment

When demand drops, the optimizer right-sizes fleet automatically. No off-season bench time you'd pay for while trucks park themselves.

Dispatcher time back

Manual routing goes away. Dispatchers review a machine-generated plan instead of building routes ticket by ticket. Hours daily back to the operations team.

Fewer exception calls

Tank-telemetry-triggered dispatch hits customers before the tank hits empty. Missed deliveries become rare, not routine.

Observed

What the numbers look like in production.

~30 %
Fewer miles · operational-run on a real operator's tickets
~50 %
Fewer driver hours · same operational-run
~70 %
Fewer trucks needed · low-season window
Minutes
Review replaces hours of manual routing

Send a week of delivery tickets and tank readings. We'll model the telemetry trigger.

A real week of tickets and readings beats any demo. Thirty-minute call, honest deltas.