Fuel doesn't disappear in big spills.
It disappears in thousands of unverified transfers.
The variance is real. The record to explain it doesn't exist.
Tank variance found during monthly reconciliation. 800 gallons missing.
You discover the gap weeks after it happened. No digital trail of when the loss occurred, whether it was a slow leak or an unrecorded dispense. The investigation starts from zero.
Driver dispensed 400 gallons. No digital record of who authorized it.
The fuel left the system. The paper log says one thing. The tank level says another. Without digital chain-of-custody per transaction, accountability is a conversation — not a record.
Emergency delivery dispatched. Tank wasn’t actually low — sensor was wrong.
A single bad reading triggered a $2,800 emergency dispatch. Without continuous digital verification against multiple data points, one faulty sensor costs more than the fuel itself.
SPCC plan says inspections are current. Auditor says otherwise.
Your compliance binder looks complete — until the auditor asks for timestamped evidence of the last three inspections. The gap between what you documented and what actually happened is the gap that triggers penalties.
The gap is not more tank gauges or another reconciliation spreadsheet. It is that your tanks, pumps, and dispensers were never digitally alive — they cannot verify their own levels, enforce dispense authorization, or hand themselves to an AI that prevents the variance.
HOW WE DO IT
One Operating System. Built for the complexity of fuel and fluid operations across every site you actually manage.
Not another sensor layer feeding another dashboard. A complete operational foundation — hardware, connectivity, identity, workflows, and AI — that makes every asset digitally alive and every transfer, dispense, and maintenance event a governed, automatically recorded transaction.
Locate & Sense
Every bulk tank, skid tank, frac tank, day tank, and generator tank — tracked by level, condition, and quality state. Every IBC tote, drum, cylinder, and returnable container — tracked by location and assignment status across every site and yard. Every fuel truck, lube truck, cart, hose, dispenser, transfer pump, and meter — tracked by location, operational state, and calibration status. Environmental and quality signals captured continuously: tank level, flow rate, pressure, temperature, water-in-fuel detection, filter differential pressure.
4 sites monitored | 2 assets flagged
Normalize
Viaanix trackers, partner devices, RTUs, PLCs, flow meters, SCADA outputs, telematics feeds, and data from existing ERP and fuel management systems — we ingest it all into one consistent operational model. No vendor lock-in. No rip-and-replace.
Vendor protocols: 11 | Unified: ✅
Digitalize
Once connected, every asset gains a digital identity — a governed record of what it is, where it has been, every level reading, every transfer event, every dispense record with operator and cost-centre association, every inspection, every maintenance event, every calibration cycle, and every exception.
Rules: 5 active | Alerts: 1 open
Run Operations on ArgusIQ™
ArgusIQ™ is the hub. Built-in CMMS and work orders manage equipment maintenance end-to-end. Ticketing and workflows orchestrate reorder approvals, transfer verifications, dispense accountability, variance investigations, spill response, inspection scheduling, calibration enforcement, and compliance closure. SOPs, inspection procedures, compliance checklists live inside as a searchable knowledge base, grounded for AI.
Teams online: Ops (6) Maint (4) HSE (2)
Automate With AI and Orchestration
Ask Argus queries live operational data in plain language. ArgusOps provides multi-site command dashboards. ArgusForge extends to new workflows without new silos. ArgusAI brings full AI on-premises and air-gapped for regulated environments.
REAL OUTCOMES
You’ll recognise your operation in these.
These are not hypothetical scenarios. They are the exact accountability failures, variance mysteries, and compliance exposures your teams navigate every day.
“Tank T-08 hit 18% at 14:23 on Wednesday. A delivery was scheduled before anyone checked the gauge on Thursday morning.”
The Scene
It’s Wednesday afternoon. Tank T-08 at Site B is at 18%. The site supervisor won’t check until Thursday morning’s walkthrough. The lead time on a delivery is four days. By the time the order goes in Thursday, the site will run dry before the truck arrives. Emergency delivery: $4,200 premium.
With Viaanix
ArgusIQ™ detected T-08 at 18% at 14:23. Reorder workflow triggered automatically. Delivery scheduled for Monday — two days before the tank would have run dry. No emergency. No premium. No walkthrough required.
What Does Not Happen
The Thursday morning surprise. The emergency delivery call. The $4,200 premium. The production disruption while the site waits for fuel.
Reorder triggered automatically at threshold. Emergency delivery eliminated. Lead time managed by system, not by memory.
Days to empty: 7.2 | Delivery margin: +2 days
“IBC-19 was supposed to be at Site B. It was at Yard Zone C. The query found it in six seconds.”
The Scene
IBC-19 was dispatched to Site B last Tuesday. It’s now Friday and the receiving team says it never arrived. Three phone calls later, someone drives to Yard Zone C and finds it sitting next to two other totes that were also supposed to be somewhere else. Container “losses” are not losses — they are location truth failures.
With Viaanix
RTLS tracks every IBC, drum, and cylinder across every site and yard zone. “Where is IBC-19?” — answer in six seconds: Yard Zone C, Site A. Overdue for return since Tuesday. Alert sent to logistics lead.
What Does Not Happen
The three phone calls. The drive to check. The Friday afternoon discovery. The week of uncertainty about where the container actually was.
Container located in seconds. Overdue returns flagged automatically. Location truth replaces phone calls.
Overdue: 3 days | Return initiated
“Delivery truck connected at 09:11. Tank T-04 was at 87%. The workflow blocked the transfer before a single litre was pumped.”
The Scene
A delivery truck arrives at Site C. The driver connects to Tank T-04 and starts the transfer. T-04 is at 87% — the delivery is 5,000 gallons. The tank holds 6,000. Nobody checked the level before authorising the delivery. The overfill triggers a spill, an environmental incident, and a reportable event.
With Viaanix
ArgusIQ™ checks tank level before every inbound transfer. T-04 at 87% with a 5,000-gallon delivery = overfill risk. Transfer blocked at 09:11. Dispatcher notified. Delivery redirected to T-07 (at 22%). No overfill. No spill. No incident.
What Does Not Happen
The overfill. The spill. The environmental incident. The reportable event. The cleanup cost. The regulatory penalty.
Overfill prevented by automated pre-transfer level check. Zero manual intervention required.
Overfill prevented | Dispatcher notified 09:11
“Water detected in Tank T-11 at 06:44. The quarantine hold was placed at 06:45.”
The Scene
Tank T-11 receives a delivery on Monday. By Wednesday, the fluid being dispensed from T-11 is causing equipment issues downstream. A manual sample reveals water contamination. Three days of dispenses from a contaminated tank — affecting every vehicle and piece of equipment that was fuelled from it.
With Viaanix
Water-in-fuel sensor detected contamination at 06:44 on Monday — one hour after delivery. ArgusIQ™ placed an automatic quarantine hold at 06:45. Dispense blocked. Quality investigation workflow opened. Supplier notified. Zero contaminated dispenses.
What Does Not Happen
The three days of contaminated dispensing. The equipment issues downstream. The investigation to determine which assets were affected. The supplier dispute without evidence.
Contamination detected within one hour. Quarantine placed in under 60 seconds. Zero contaminated dispenses.
Contaminated dispenses: ZERO
“Vehicle V-22 fuelled at 07:34. 74.3 gallons. Operator badge confirmed. Cost centre assigned. Record closed. No manual entry required.”
The Scene
Fleet operations dispense fuel to 40+ vehicles per day across three sites. At month-end, 20% of dispense events have incomplete records — missing operator, missing vehicle, missing cost centre. The reconciliation cannot close because the data that would close it was never captured at the point of dispense.
With Viaanix
Every dispense event is a five-element transaction: asset (V-22), operator (badge confirmed), location (Dispenser D-3), volume (74.3 gal), and purpose (cost centre 4420). All five captured automatically at point of dispense. Record closed. No manual assembly required.
What Does Not Happen
The 20% incomplete records. The month-end reconciliation scramble. The manual assembly of dispense data hours or days after the event.
100% five-element dispense accountability. Zero manual entry at point of dispense. Month-end reconciliation closes automatically.
5/5 elements captured | No manual entry
“Pump P-7, Shift 3, four consecutive Tuesdays. Dispense volumes 34% above fleet average. Exception ticket raised automatically on week two.”
The Scene
Fuel theft in industrial and fleet operations is rarely dramatic. It is a pattern — consistent, small, and invisible in aggregate data. Pump P-7, third shift, Tuesday nights. Dispense volumes 34% above fleet average. Nobody notices because the variance is spread across the month-end reconciliation along with meter drift, short-fills, and project misallocations.
With Viaanix
ArgusIQ™ flags statistical anomalies at the dispense-event level. After week two, an exception ticket was raised automatically: Pump P-7, Shift 3, Tuesdays, 34% above average. Investigation initiated with full event data. Pattern confirmed by week three.
What Does Not Happen
The months of undetected losses. The reconciliation that writes it off as acceptable variance. The pattern that continues because nobody had the data to see it.
Anomaly detected at week two. Exception ticket auto-raised. Investigation initiated with full event-level data.
Exception detected automatically
“Delivered: 12,400 gallons. Dispensed: 12,288 gallons. Variance: 112 gallons. Three contributing factors identified before the CFO asked.”
The Scene
Month-end reconciliation. Delivered: 12,400 gallons. Metered dispenses: 12,288 gallons. Variance: 112 gallons. The CFO asks where it went. Nobody can answer. Fuel theft, meter drift, short-fills, unauthorised dispensing, and project misallocation all look identical in a reconciliation with no event-level data.
With Viaanix
ArgusOps showed the variance breakdown before the reconciliation closed: 48 gal meter drift (Meter M-04, flagged for calibration), 37 gal evaporative loss (within tolerance), 27 gal timing gap between delivery acceptance and first dispense record. Three contributing factors. All documented. All explainable.
What Does Not Happen
The unexplained variance. The CFO question nobody can answer. The write-off that masks a real problem. The investigation that starts from zero.
Variance decomposed to contributing factors automatically. All factors documented with source data. Reconciliation closes with explanation, not write-off.
Meter drift: 48 | Evap: 37 | Timing: 27
“Transfer #4412: Pump P-3 to IBC-19. 850 litres. Zone B. 11:34am. Operator verified. Destination confirmed. Record closed. No manual log entry made.”
The Scene
Inter-site transfers are the most documentation-intensive and least documented events in fuel and fluid operations. A transfer involves a source, a destination, a volume, an operator, a timestamp, and a verification. Most operations capture one or two of those elements. The transfer log is assembled from memory hours or days later.
With Viaanix
Transfer #4412 recorded automatically: Pump P-3 to IBC-19, 850 litres, Zone B, 11:34am. Operator badge verified. Destination IBC confirmed via RTLS. Record closed at point of transfer. Audit trail complete. No manual log entry.
What Does Not Happen
The manual log entry. The memory-based record. The transfer that disappears from documentation. The audit that finds a gap in the chain of custody.
Transfer recorded with all six elements automatically. Zero manual documentation. Complete audit trail at point of event.
Record closed | No manual entry
“Spill event logged at 14:07. Response steps opened at 14:07. Evidence captured at 14:22. Regulatory notification drafted at 14:45. Supervisor arrived at 15:00 to a closed record.”
The Scene
A spill occurs at 14:07. The site supervisor is notified by phone. They arrive at 15:00. The incident report starts from scratch — finding the right form, interviewing witnesses, assembling a timeline from memory. The EPA inspector asks for the contemporaneous record two weeks later. It was written from memory two days after the event.
With Viaanix
Spill event logged at 14:07. ArgusIQ™ opened the response workflow at 14:07 — checklist of required steps, evidence capture prompts, notifications to HSE and site supervisor. Photos and measurements captured at 14:22. Regulatory notification drafted at 14:45 with auto-populated event data. Supervisor arrived at 15:00 to a complete, contemporaneous incident record.
What Does Not Happen
The record assembled from memory. The form search. The witness interviews two days later. The documentation violation on top of the environmental event. The penalty for the absence of a record.
Incident record complete before supervisor arrival. Evidence captured within 15 minutes. Regulatory notification drafted within 38 minutes. Contemporaneous record for inspector.
Record complete before supervisor arrival
“Delivery order: 8,000 gallons. Meter reading at acceptance: 7,940 gallons. Short-measure exception raised automatically. Supplier claim initiated before the truck left.”
The Scene
Delivery acceptance in most operations is a signature on a bill of lading. The delivery order says 8,000 gallons. The receiving team signs. Nobody verifies the actual volume against the meter reading until the month-end reconciliation finds a variance that nobody can explain.
With Viaanix
Delivery acceptance workflow compares the ordered volume against the meter reading at point of receipt. Order: 8,000 gallons. Meter: 7,940 gallons. Variance: 60 gallons (0.75%). Short-measure exception raised automatically. Supplier claim initiated with timestamped evidence before the truck left the site.
What Does Not Happen
The unverified acceptance. The month-end discovery. The supplier dispute without evidence. The 60 gallons absorbed as unexplained variance.
Short-measure detected at acceptance. Supplier claim initiated with evidence. Variance resolved before truck departed.
Resolved before truck departure
“Filter differential pressure on Unit P-3 crossed threshold at 22:14 on Tuesday. WO-22091 was created at 22:14. The pump had not yet failed.”
The Scene
Transfer Pump P-3 has been running for six months. The filter is on a six-month replacement schedule — but conditions vary. Differential pressure has been creeping for two weeks. On Tuesday night at 22:14, it crosses the threshold. By Wednesday morning, the filter is partially blocked. By Thursday, the pump is down. Emergency replacement: $4,000 plus downtime.
With Viaanix
Differential pressure sensor on P-3 reports continuously to ArgusIQ™. At 22:14 Tuesday, ΔP crossed 28 psi (threshold: 22 psi). WO-22091 auto-created for filter replacement. Parts verified in stock. Scheduled for Wednesday morning planned window. Pump never failed.
What Does Not Happen
The Thursday failure. The emergency replacement. The $4,000 cost. The downtime. The transfers that backed up while P-3 was down.
Condition-triggered work order created 36 hours before predicted failure. Replacement scheduled in planned window. Zero unplanned downtime.
Pump status: RUNNING | Intervention: preemptive
“"Show me the top ten dispense variances this week across all sites and their likely causes." Live answer. Grounded in actual data. Available before the 08:00 operations call.”
The Scene
The operations manager needs a cross-site variance summary for the 08:00 call. Assembling it means calling three site supervisors, pulling four spreadsheets, and reconciling numbers that were already a day old when they were entered. The summary takes 90 minutes. It’s incomplete. It’s late.
With Viaanix
"Ask Argus: show me the top ten dispense variances this week across all sites and their likely causes." Answer in seconds. Ten variances ranked by magnitude. Contributing factors identified for each. Compliance gaps flagged on two events. Available at 07:45 — fifteen minutes before the call.
What Does Not Happen
The 90-minute assembly. The three phone calls. The incomplete summary. The meeting that starts without the data it needs.
Cross-site variance summary in seconds. Contributing factors auto-identified. Available before the operations call, not after.
Query time: 3.2s | Grounded in live data
THE PLATFORM IN ACTION
This is what your operation looks like when every tank, pump, and dispenser is digitally alive.
Live telemetry, governed dispense workflows, and AI — running across terminals, tank farms, and fleet yards. One Operating System.
AST-01
88min
AST-05
72min
AST-08
45min
AST-12
58min
AST-15
22min
AST-19
91min
3 of 4 dispenses verified | 1 flagged for review
BUILT FOR WHAT COMES NEXT
Autonomous inspection systems, remote operation platforms, and AI-driven maintenance are entering fuel and fluid infrastructure at scale. Is your Operating System the foundation they need to run?
Every autonomous capability entering fuel and fluid operations needs the same thing: a system that knows what every asset is, where it is, and what state it’s in. That system is ArgusIQ™.
Autonomous Inventory Management
AI-driven burn rate prediction, automatic reorder triggering, and delivery scheduling across every site. Replenishment decisions made by the system — verified by humans, not initiated by them.
Robotic Inspection Integration
Autonomous inspection platforms for tank integrity, valve condition, and environmental monitoring. ArgusIQ™ routes inspection paths, captures evidence, and generates compliance records automatically.
AI-Driven Variance Detection
Pattern recognition across dispense events, transfer records, and inventory movements. Anomalies surfaced before they compound. Contributing factors identified without manual investigation.
Remote and Offline Operation (ArgusAI)
Full AI stack running on-premises and air-gapped for remote terminals, pipeline stations, and regulated environments. Zero cloud dependency. Full operational intelligence where there is no network.
Every autonomous system entering fuel and fluid operations needs the infrastructure you can build with Viaanix today. Digital identity is the foundation. ArgusIQ™ is the brain. The rest follows.
WHAT THIS COSTS NOT TO HAVE
Fuel and fluid losses are not catastrophic events. They are relentless small failures that compound across every site, every shift, every transfer, every month.
Fuel Variance
Dispense Accountability
Emergency Dispatches
SPCC Compliance
WHY VIAANIX
Not another vendor. A different foundation.
RTLS-First Truth Across Every Asset
Every tank, tote, drum, dispenser, pump, and meter has a known location and a governed lifecycle. Not a sensor reading in isolation — a complete operational truth layer that connects location, condition, event, and workflow.
One OS — Not Five Point Solutions
Tank monitors, dispense loggers, CMMS, ticketing, compliance checklists, and AI — all in one platform. Viaanix replaces five separate software purchases with one operating system your entire team runs on.
AI Grounded in Your Operation
Ask Argus answers questions about your tanks, your transfers, your variances — grounded in your live operational data. Not a generic model. An intelligence layer that knows your operation specifically.
Deploy Anywhere — Even Off-Grid
Cloud, private cloud, on-prem, or fully air-gapped with ArgusAI. Remote terminals, pipeline stations, and regulated environments get full operational intelligence without cloud dependency.
Deployment Options
Cloud
Fully managed SaaS. Fastest path to value.
Private Cloud
Your cloud, your network, our platform.
On-Prem
Inside your firewall, full control.
Air-Gapped (ArgusAI)
Zero internet. Full intelligence. For remote terminals and regulated environments.
You don’t have a measurement problem. You have an execution problem. And it has a solution.
Every outcome on this page — automatic reorder workflows, verified dispense accountability, condition-triggered maintenance, contemporaneous compliance records, AI that answers your questions against your live data — is running at operations like yours right now. The difference is not technology. It is a decision to stop managing operations with the same fragmented stack that created the variances in the first place.