Last updated: June 2026

Metro Fleet Fueling Case Study: 21,000 Units Under Control

PCG built and deployed a security-hardened fueling management platform for one of the five largest metropolitan fleets in the United States. It carries 21,000 fleet equipment units, 130,000 fuelings per quarter, plus 65 fueling sites across more than 50 departments.

How large a fueling operation can FireFlight run? This platform handles 21,000 fleet equipment units and 130,000 fuelings per quarter across 65 sites. Every vehicle class is covered, from first responders to sanitation plus public works. In June 2026 that means real-time control, ruggedized hardware integration, plus encrypted communications on a mission-critical system.

See it on your own sites and tanks. Not a canned demo.

Book a Demo Talk to Our Team

What was breaking in the old fueling system?

The system was slowing to a crawl. Years of unindexed historical data had piled up, so response times dragged and the delays showed up in daily operations. Software crashes interrupted fueling and pushed more work onto IT.

Tank data had to be pulled by hand. Veeder Root readings were retrieved manually, with no real-time integration across the sites. There was no central dashboard for site activity, tank levels, or system health, so nobody had one view of the operation.

Cellular cost was the quiet drain. Unoptimized protocols retransmitted the full vehicle whitelist and site data unencrypted on every change, whether a vehicle update, a site edit, or a fuel allowance change. The sync was repetitive, redundant, plus insecure. On top of that, transaction logging often failed to reflect the actual dispense, which created billing discrepancies and audit concerns.

How did FireFlight take control of the operation?

PCG engineered the platform for mission-critical uptime, which is the standard when first responders depend on a pump working. Real-time control replaced the manual pulls, so tank levels and site activity arrive without anyone driving out to read a gauge.

Ruggedized hardware integration ties the field equipment to the platform. Communications run fully encrypted end to end. A central dashboard finally shows site activity, tank levels, plus system health in one place.

Data cost dropped sharply once the protocols were rebuilt, and the operational errors went with them. Most deployments run in weeks, not months. Transaction logs now reflect the actual dispense, which closes the billing discrepancies that triggered audit concerns.

What scale does the platform carry?

  • More than 21,000 fleet equipment units.
  • More than 130,000 fuelings per quarter.
  • 65 fueling sites across more than 50 departments.
  • Every vehicle class: first responders, sanitation, transportation, plus public works.
  • Real-time control across sites.
  • Ruggedized hardware integration in the field.
  • Fully encrypted communications.
Mission-critical uptime Encrypted communications Lower cellular data cost

How is a mission-critical fueling system secured?

Communications run fully encrypted across every site, replacing protocols that had been sending vehicle whitelists and site data in the clear on each change. The platform is security-hardened for an operation that first responders depend on.

Transaction logs now match the actual fuel dispensed, so billing lines up and an audit has a record it can trust.

Which FireFlight modules built this system?

Documents HistoryTimestamped storage of photos, reports, plus certificates.
Work OrdersMobile job forms with photo attachments and sign-off fields.
CRM / Contact LogsCentralized crew and client records.
Manual LibraryOn-demand access to service procedures plus repair guides.
Notes HistoryAudit-proof logging of field notes plus issue comments raised on a job.
Inventory ControlReal-time tracking of parts and supplies.
Materials & Parts ListPre-built material lists auto-populated per job type.
CertificationsTechnician credentials and training kept current.
We went from chaos to total control, in less than two weeks.
Operations LeadField services client

Thirty-one years of mission-critical builds

Phoenix Consultants Group has built custom software since 1995, more than 500 applications, on a platform it hosts plus supports itself. Fleet fueling for a top-five metropolitan operation is among that work, alongside physician credentialing and airport ground equipment management.

FireFlight also carries AI reporting. A fleet manager can ask a plain-English question about consumption at one site or which tanks are running low and get an answer from live data, with no canned report and no waiting in a queue. Most deployments still run in weeks, not months.

What changed operationally after deployment?

  • Launched in under 10 days with no disruption.
  • Field technicians reached 100% adoption within 3 days.
  • Dispatch time fell by 75%.
  • Revenue leakage stopped through proof-of-service logs.
Ikhana guide character
On-Screen Guide

Ikhana got the crews on board fast

Field technicians hit full adoption in three days. Ikhana explains each field right on the screen, so a crew picks up a new system without classroom training or a thick manual.

Learn more

Frequently Asked Questions

How large a fueling operation can FireFlight run?
+
This platform handles more than 21,000 fleet equipment units and over 130,000 fuelings per quarter across 65 fueling sites. It serves more than 50 departments, covering first responders, sanitation, transportation, plus public works.
Does it read tank levels automatically?
+
Yes. Veeder Root tank data used to be retrieved by hand with no integration between sites. The platform pulls it in real time, so tank levels appear on the dashboard rather than waiting on someone to check a gauge.
How did it cut cellular data cost?
+
The old protocols retransmitted the entire vehicle whitelist and site data on every change, unencrypted. Rebuilding that communication removed the repetitive, redundant sync traffic, which brought the data cost down sharply and closed the security gap at the same time.
Are the transaction logs reliable for billing?
+
They are now. Logging previously failed to reflect the actual fuel dispensed, which produced billing discrepancies plus audit concerns. Records match the dispense, so a finance team and an auditor see the same number.
What happens when the system slows down under years of data?
+
Accumulated unindexed historical data was causing sluggish response times plus daily delays. Addressing how that history is stored and indexed removed the drag, and the crashes that had been interrupting fueling stopped adding to the IT workload.
How fast did it go live?
+
The system launched in under 10 days with no disruption. Field technicians reached full adoption within 3 days. Most deployments run in weeks, not months.
Allison Woolbert
Allison Woolbert
Principal, Phoenix Consultants Group

Allison has built custom software since before Phoenix Consultants Group opened its doors in 1995. Across 31 years she has delivered more than 500 applications, including fleet fueling systems for large metropolitan operations.

phxconsultants.com fireflightdata.com

Phoenix Consultants Group. Founded 1995. FireFlight Data Systems is PCG's hosted platform. Last updated June 2026.

This system was built using FireFlight for rapid deployment and long-term adaptability.