Fuel
Fuel delivered, stored and drawn recorded on delivery notes, tank probes and pump terminals that nobody reconciles until month-end.
AI for mining contractors: fuel, machines, loads and reports
A mining or haulage contractor has to account to its client for every tonne, every litre and every machine hour. Mirage reads the records that prove it, fuel deliveries and pump transactions, trip and load tickets, weighbridge records, machine logs and shift reports, ties each one to a machine, a load or a litre, and sends what does not match to a person. Mirage has not published a deployment at a contract-mining company; the nearest is Transwin, a Moroccan logistics operator that moves mining freight with more than 100 machines, where five systems run in production.
Where a contractor's margin leaks
Every tonne and every litre has to be accounted for to the client, from records kept in separate systems.
Machines
Hours, greasing and oil changes followed machine by machine on paper, so the breakdown arrives before the service.
Loads
Trip tickets, weighbridge records and the dispatch plan that disagree, with no one tying each load to a truck, a driver and a destination.
Reporting
Shift reports and the monthly report to the client assembled by hand from exports, spreadsheets and chat groups.
What Mirage runs for contractors on a mine
One platform, built from the systems already on site. Each workflow is built and put into production before the next.
Fuel
Deliveries, tank levels and pump transactions reconciled per tank, per day and per machine, with missing volumes and abnormal consumption flagged while they can still be explained.
Haulage and loads
Raw GPS turned into trips, loading, hauling, dumping, queuing and idle time per truck and machine, compared with the dispatch plan per shift; each load matched at the weighbridge.
Maintenance
Greasing, oil changes and hours followed machine by machine; the work order drafted with the asset, the symptom and its history, and sent to the planner for approval.
The shift record and the client report
Extraction, hauling, stockpiles, equipment, fuel and maintenance in one record per shift, and the recurring report filled from it, each value traced to its source.
The nearest published deployment: Transwin
Mirage has not published a deployment at a contract-mining company. Transwin moves mining, fertilizer, steel and agri-food freight and runs more than 100 machines; a second control room project covers the mining side of its business.
12%
Lower fleet diesel consumption
5
Systems live across freight, fuel, mining and fleet
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
- Mining machines failed expensively and unpredictably, and operational data lived in separate systems, spreadsheets and teams.
- Deployment
- Per-machine tracking of greasing, oil changes and mileage, with prediction layered on top so maintenance is scheduled before breakdown, and usage data feeding how machines are assigned and routed. Fuel across deliveries, tanks and pumps.
- Now
- Five systems in production across freight, fuel, mining and fleet, with a control room across the business, grown from a single paid document workflow.
What stays with your team
Mirage reconciles and flags. Your site team decides, and a named person signs what goes to the client.
- Fuel gap
- Sent to the person who can act, with the delivery note, the tank readings and the pump transactions attached. Explaining it is theirs.
- Load mismatch
- A load whose ticket, weighbridge record and dispatch plan disagree is held for a person with the records side by side.
- 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.
- Client report
- A missing or inconsistent value is flagged, not guessed. A named person approves the report before it goes out.
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 mining and haulage contractors
It reconciles fuel per machine, turns GPS and telematics into trips and cycles compared with the dispatch plan, follows each machine's maintenance, matches loads at the weighbridge and builds the shift record and the recurring report to the client, each value traced to its source. What does not match goes to a person.
Not at a contract-mining company, and the site says so. The nearest published deployment is Transwin, a Moroccan logistics operator that moves mining freight and runs more than 100 machines: per-machine maintenance tracking, fuel across deliveries, tanks and pumps, and a control room on the mining side of its business.
The ERP (SAP, Oracle, Microsoft Dynamics, Sage or a mining-specific one), GPS and dispatch systems, fuel management, maintenance or CMMS, weighbridges, and the field reports, Excel files and chat groups that still carry real data. Where no documented interface exists, Mirage's engineers build the connector during deployment.
At Transwin: 12% lower fleet diesel consumption and five systems in production, across 550 specialized trucks and more than 100 machines. Mirage publishes no figure on downtime or utilization.
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.