IT that keeps trucks loading, cardlocks taking cards, tanks from running dry.IT that keeps trucksloadingcardlockstakingcardstanksfromrunningdry
From rack price to delivered gallon to settled card, every step depends on systems we keep patched and watched.
Fuel distributor IT
Every gallon moves through a system first
Before a load leaves the rack, someone checked a price, a tank reading and a credit limit. After it's delivered, a ticket, an invoice and maybe a card transaction follow. That chain runs on IT at the plant, in the trucks and at sites you don't staff. Here's where it's under pressure, how it fails, what we change and what you get back.
01 · The pressure
Rack prices, tank readings and dispatch, all before dawn
Pricing staff pull rack and contract prices early, dispatchers build routes from tank monitor readings and customer orders, and drivers start loading before most offices open. Cardlock sites take fleet cards around the clock without anyone on site. Billing reconciles bills of lading against deliveries and card settlements. If dispatch software loses its tank feed or the cardlock network drops, customers run dry, fleets drive elsewhere and you hear about it from the customer first.
- Dispatch depends on live tank monitor readings
- Unattended cardlocks run around the clock
- Billing ties BOLs, deliveries and card settlements
PDI TechnologiesOPIS rack pricingVeeder-Root tank gaugesWEXComdataSamsara
02 · How it breaks
Flat site networks and borrowed vendor logins
The common failures are unglamorous. A cardlock controller, a tank gauge console and a security camera DVR sit on the same flat network behind a consumer router. A payment or maintenance vendor's remote login is shared across every technician they employ. An accounting clerk gets a convincing email from a supplier asking to send this month's fuel payment to a new account. A dispatch server under someone's desk has never been backed up offsite.
- Card terminals, gauges and DVRs on one network
- Shared vendor credentials for remote support
- Supplier payment fraud aimed at accounts payable
PDI TechnologiesOPIS rack pricingVeeder-Root tank gaugesWEXComdataSamsara
03 · What we change
Segmented sites and a defined payment environment
At each cardlock and bulk plant we install a managed firewall that puts payment devices, tank gauges, cameras and office PCs on separate segments, which also narrows what falls inside your PCI DSS scope. Vendor remote access moves to named accounts with MFA and session logs. Office staff get MFA, endpoint detection and email filtering. Dispatch, ERP and accounting data get immutable offsite backups, and accounts payable adopts a callback rule for any change to supplier banking details.
- Payment devices isolated on their own segment
- Named, logged vendor access with MFA
- Callback verification before paying a new account
PDI TechnologiesOPIS rack pricingVeeder-Root tank gaugesWEXComdataSamsara
04 · The after
Smaller PCI scope and fewer surprises at the pump
Once sites are segmented and monitored, you know when a cardlock goes offline before a fleet manager calls. Your PCI DSS self-assessment covers a defined set of devices instead of every network you own, and you can show your acquirer how card data is isolated. A failed dispatch server becomes a restore, not a lost week. Your controller pays suppliers knowing a fake banking change won't slip through on a busy Friday.
- Site outages flagged before customers call
- A cardholder data environment you can describe
- Dispatch and ERP recoverable from tested backups
PDI TechnologiesOPIS rack pricingVeeder-Root tank gaugesWEXComdataSamsara