Fleet operations

The fuel linethat does not add up.

An operator checks each fuel-card line against the tank and the trip, flags what does not fit and drafts the follow-up. Your fleet manager approves before anything goes out.

  • ISO 27001
  • GDPR
  • Every run auditable
From the trip exportIllustrative fleet
Ring Road28 kmDepot NorthVN-114 parked from 17:30Station 2217
Flagged · Fuel

112 L bought for an 80 L tank

Fuel card, 9 Oct 18:52

112 L diesel at Station 2217, Ring Road · €181.44

Telematics, 9 Oct

Parked at Depot North from 17:30, 28 km from the station

More fuel than the tank holds, bought while the van was 28 km away.

Draft for A. Novak, fleet manager

Message to the Depot North manager: ask the driver for the receipt and the vehicle filled. Card dispute drafted for the provider.

Enterprises running operators on Alomana

  • up to 60%less time on fleet admin
  • up to 15%lower fuel and maintenance cost
  • 20+ hoursback each week from paperwork and calls

Fuel is the first of six checks.

Telematics knows where the van went, the fuel card what was bought, dispatch what was booked, the invoice what was billed. The operator puts them side by side.

  • 01

    Fuel against the tank and the trip

    Flags fuel beyond the tank, or bought away from the van

  • 02

    Jobs against trips

    Finds jobs marked done with no stop at the address

  • 03

    Invoices against service history

    Catches repeat repairs and parts billed twice

  • 04

    Idle and out-of-hours use

    Lists engine-on hours at depots and use outside shifts

  • 05

    Mileage against the service plan

    Lists the vans due a service and drafts the bookings

  • 06

    Fines and tolls against the driver

    Matches each charge to the van and driver at that time

How the operator works the week

  1. 1

    Connect

    Telematics and fuel-card exports, dispatch sheets and invoices, from SharePoint, Drive, Sheets or your database.

  2. 2

    Check

    It compares every record with what the vans did, in code, and keeps the rows behind each flag.

  3. 3

    Approve

    You say yes. It sends the follow-up and logs it.

Week 41, 6–12 OctIllustrative week

  • Telematics tripstrip export (CSV)1,912 trips
  • Fuel cardscard statement (CSV)386 transactions
  • Dispatchjobs sheet (Google Sheets)1,204 jobs
  • Maintenancegarage invoices (PDF)27 invoices

Found4 exceptions

Nothing goes to a driver or a vendor without a yes.

  • Messages, disputes and bookings wait for a person's yes
  • A declined action is not retried
  • Every run logged: input, output, tools, user

Run recordIllustrative fleet

Input
Card statement and trip export, Week 41, 6–12 Oct
Tools
Compared in code, in an isolated sandbox
Output
VN-114 flagged: 112 L bought for an 80 L tank. Draft for A. Novak, fleet manager
User
A. Novak, fleet manager

Sent by A. Novak, fleet manager · logged

Measured on

  • Fuel spend per van
  • Exceptions closed each week
  • Repeat repairs caught
  • Hours spent reconciling

Works with

  • Snowflake
  • PostgreSQL
  • Google Sheets
  • Google Drive
  • SharePoint
  • Slack
  • Telematics and fuel-card exports
  • Other systems via a remote MCP server

Trusted for

  • ISO 27001
  • GDPR
  • Never trains on your data
  • Single-tenant for enterprise

A custom operator typically goes live in up to 4 weeks.

Questions

What is an AI fleet operations operator?

An autonomous agent that checks your fleet's records against each other. It compares telematics trips, fuel-card transactions, dispatch jobs and maintenance invoices, flags each mismatch with the rows behind it, and drafts the follow-up for your fleet manager to approve.

Does it replace our telematics or fuel cards?

No. Your telematics, fuel cards and dispatch system keep running. The operator works on what they export or store: CSV and Excel files, PDFs, Google Sheets or your data warehouse.

Does it track our vans in real time?

No. It works on the records you give it, when you run it, and a workflow can run it every morning on the previous day's exports. Live tracking and alerts stay with your telematics.

Does it contact drivers or vendors on its own?

No. Messages, disputes and bookings sent through Alomana's connectors wait for a person's yes. A declined action is not retried, and every run is logged with its input, output, tools and user.

Which systems does it connect to?

Alomana has 20+ connectors, including Snowflake, PostgreSQL, Google Sheets and Drive, SharePoint and Slack, activated per deployment. Telematics and fuel-card platforms connect through their exports or a remote MCP server.

Is our fleet data private?

Alomana is ISO 27001 certified and GDPR-compliant, and your data is never used to train AI models. Enterprise deployments run single-tenant, in a dedicated instance.

Bring one week of exports.

Talk it over with sales: what the operator needs from your systems, and how it goes live.

Alomana is a secure enterprise AI platform where autonomous agents, called operators, run business processes end to end. Every run is fully auditable.