Fuel
Deliveries, tank levels and pump transactions recorded in three places, so a missing volume is found weeks later, if at all.
AI for carriers and fleet operators: fuel, trips and paperwork
For a carrier, the work Mirage takes on sits between the trucks and the office: fuel delivered, stored and drawn reconciled per vehicle, every trip compared with the plan, machines serviced before they break, and the freight documents behind each load read once and written into the TMS. What does not match goes to the person who can act on it while it can still be explained. In production at Transwin, a Moroccan logistics operator with 550 specialized trucks: 12% lower fleet diesel consumption and 70% less manual data entry on freight documents.
Where a fleet loses money without anyone seeing it
Trucks, fuel and telematics live in separate systems, and the losses are found at month-end.
Trips
GPS positions for every truck, but nobody comparing each trip, load and waiting time with the dispatch plan.
Machines
Greasing, oil changes and mileage followed on paper, so a machine fails expensively and unpredictably before anyone schedules the service.
Paperwork
Freight documents, delivery proofs and inbound tenders read and keyed into the TMS by hand, and more of them with every truck added.
What Mirage runs for carriers and fleet operators
Transwin started with one paid document workflow. Five systems now run in production across its freight, fuel, mining and fleet operations.
Fuel
Deliveries, tank gauges and pump transactions reconciled per tank, per day and per vehicle, with missing volumes and suspicious transactions flagged as they happen.
Trips and the control room
Raw GPS and telematics turned into trips, loading, queuing and idle time per vehicle, compared with the plan, and every shipment, truck and exception in one live view.
Maintenance
Greasing, oil changes and mileage followed machine by machine, with maintenance scheduled before a breakdown and the work order sent to the planner for approval.
Freight documents and delivery proofs
Freight documents, proofs of delivery and inbound tenders read from email and scans, matched to the shipment and the invoice, and written into the TMS.
In production at Transwin
Transwin is a Moroccan logistics operator built around port flows, operating from El Jadida, Jorf Lasfar and Casablanca. It moves agri-food, fertilizer, steel and mining freight.
12%
Lower fleet diesel consumption
70%
Less manual data entry on freight documents
550
Specialized trucks and 100+ machines
“We started with one workflow, and Mirage has been alongside us at every step since. Every process we brought them, they built and put into production. Today they are not a supplier we buy software from. They are our AI partner.”
- Before
- Operational data lived in separate systems, spreadsheets and teams. Adding trucks and contracts meant adding manual work, and no one had a single view of the business.
- Deployment
- Transport documents first, wired into the TMS, then invoicing and financial documents and inbound tenders. Then fuel across deliveries, tanks and pumps, per-machine maintenance tracking, live fleet tracking and a control room across the business.
- Now
- Five systems in production across freight, fuel, mining and fleet, grown from a single paid document workflow.
What stays with your team
Mirage reconciles, compares and flags. The people who run the fleet decide what to do about it.
- Fuel gap
- Sent to the person who can act, with the delivery note, the tank readings and the pump transactions attached. Whether it is a leak, a theft or a recording error is theirs to establish.
- Trip off plan
- Flagged against the dispatch record as it happens. Calling the driver or changing the plan stays with dispatch.
- Service due
- The machine is flagged with its history and a suggested priority. The planner approves the work order and decides when the machine stops.
- TMS entry
- Written when the document agrees with the shipment. A field read without confidence goes to an operator on its own.
From the first meeting to production
Mirage's engineers work on site with your team, on your own documents and systems. Every request gets an answer within two business hours, and the pilot is fixed-price: you can stop after it.
How a deployment runs
- Observe
- Map
- Build
- Run
- Expand
A proof of concept on your own documents one week after the first meeting, then the first workflow in production in 4 to 6 weeks.
See how we deploySecurity and governance
- Deploy anywhere
- Control every action
- Prove what happened
Access permissions, validation workflows and audit logs remain fully controlled by your organization. Signed NDA on request.
See security and data handlingQuestions from carriers and fleet operators
It reconciles fuel deliveries, tank levels and pump transactions per vehicle, turns GPS and telematics into trips compared with the plan, follows each machine's maintenance intervals, and reads the freight documents behind each load into the TMS. What does not match goes to the person who can act on it.
Mirage starts from what is already on site: GPS and telematics units, tank sensors and pump terminals, the TMS, the maintenance system and the ERP. Where a system has no documented interface, Mirage's engineers build the connector during deployment.
At Transwin, with 550 specialized trucks and more than 100 machines: 12% lower fleet diesel consumption, 70% less manual data entry on freight documents, and five systems in production. Mirage publishes no other fuel or fleet figure, and no figure on downtime or utilization.
Yes, and most do. Transwin started with one document workflow; fuel, maintenance, fleet tracking and the control room followed one at a time, each built and put into production before the next.
A fixed-price pilot on one workflow, which you can stop after, then an annual subscription priced by volume, not per user: from $10,000 to launch, then from $1,000 a month. The exact amount is set once we have seen your documents.
A proof of concept on your own documents one week after the first meeting, then the first workflow in production in 4 to 6 weeks. The pilot is fixed-price and you can stop after it.
Bring us the operation you need to improve.
Mirage will map the workflow, identify what can be automated and define the fastest path to production.
Start with a written plan
Tell us where your team loses time. We send back which workflows are worth automating, what a deployment involves on your systems and the shortest path to production. No commitment.