Every trip is
a measurement.
Live tracking, driver scores & maintenance. A compact tracker in the diagnostic port reports position every ten seconds and reads the engine continuously. Fleetza turns that into three things you can act on: a driver score built from the events that cause accidents, a predicted failure point for every wearing component, and a true cost per kilometre for each vehicle.
GPS trackingDriver scoringPredictive maintenance
Live GPS tracking
Ten seconds between
one position and
the next.
A trip is not a line on a map. It is a sequence of position reports, and how far apart they are decides what you can prove afterwards — which zone the vehicle was in, for how long, and at what speed it left.
Ten-second refresh
Every vehicle on a live map, updating every ten seconds. Close enough to answer where a vehicle is now rather than where it was when someone last asked.
Replay any route
Any trip can be replayed from its own reports, which is what settles a disputed delivery time or an accident account without relying on recollection.
Zones, entry and exit
Define operational zones and get an alert the moment a vehicle crosses in or out. Depots, customer sites, restricted areas and the boundary of your operating region are all the same mechanism.
Time on site, counted
Entry and exit produce a duration on their own, so customer-visit and job-site compliance stops depending on anyone writing a time down.
Live estimates, shared out
Dispatchers and clients can be given a live arrival estimate for a specific vehicle rather than a phone number to call.
Driver behaviour scoring
A score is only useful if
you can see what
it is made of.
The AI reads every trip for four events: harsh braking, rapid acceleration, speeding and phone use. Each is counted against distance driven and each carries a deduction from a hundred, so a composite score takes apart into the behaviour that produced it — and points at the one coaching conversation worth having. Select a driver to see the decomposition.
Ranked on the last 30 days. Scores are published to the driver as well as to the manager, and every event behind one is dated and reviewable.
DRIVER FILE · FZ-1147
Daniel Okonkwo
86 / 100
Harsh braking and rapid acceleration together carry nine of the fourteen points lost, and on a fixed multi-drop round they usually have one cause: leaving too late. Look at the plan before you look at the driver.
Worked example, with illustrative drivers and event rates. What is not illustrative is the arithmetic: the composite is the four deductions subtracted from a hundred and nothing else, which is what makes it possible to argue with. Coaching against these four events is where the published 41 per cent reduction in accident-related incidents comes from.
Predictive maintenance
The part gets replaced
on a Tuesday, not
on a hard shoulder.
Engine diagnostics, mileage and the way the vehicle is actually driven put a predicted failure point in front of every wearing component. The work is then booked ahead of that point, in a slot you choose. The bar below shows wear already observed as a solid block and the predicted remainder as a dashed one — the gap between the marker and the end of the dashes is the whole product.
The battery is the binding item: 2,500 km of predicted life against a service already booked 1,400 km from now. Bringing the brake pads forward from 98,600 km into that same slot puts the vehicle in the workshop once instead of twice.
Worked example on three vehicles; the window is clipped to the last 12,000 kilometres of history so that the prediction ahead of today is readable. Predicted points move as the vehicle is driven — a van worked hard on short urban runs eats brake pads faster than the odometer alone suggests, and that is precisely the difference between a predicted interval and a fixed one.
Fuel analytics
Fuel leaks in three places
and only one of them
is the engine.
Consumption per vehicle against its own class, the share of engine hours spent stationary, and the distance driven off the planned route. Each points at a different fix: a workshop booking, a policy, or a plan.
| Vehicle | Class | L / 100 km | Class median | Idling | Off plan |
|---|---|---|---|---|---|
| FZ-2208 | Panel van | 9.8 | 9.6 | 6% | 2% |
| FZ-3390 | Rigid 7.5t | 16.5 | 16.9 | 8% | 3% |
| FZ-4415 | Tractor unit | 31.6 | 30.2 | 12% | 4% |
| FZ-1147 | Rigid 7.5t | 18.4 | 16.9 | 21% | 9% |
| FZ-2871 | Panel van | 12.7 | 9.6 | 27% | 14% |
Illustrative figures. FZ-2871 burns roughly a third more than the median for its class, and most of the gap sits in idling and off-plan distance rather than in the vehicle — which makes it a driver and dispatch conversation before it is a workshop booking.
Consumption per vehicle
Measured against other vehicles of the same class doing comparable work, because an absolute litres-per-hundred figure tells you nothing on a mixed fleet.
Idling
Engine hours with the vehicle stationary, attributed to the trip and the driver. This is usually the largest single recoverable line and the cheapest to change.
Inefficient routes and fuel fraud
Distance driven off the planned route, and fuel transactions that do not reconcile against the vehicle’s position and tank capacity at that moment.
Across Fleetza deployments, customers typically cut fuel spend by 18–25%. That is a reported range rather than a guarantee, and how much of it you see depends on how much of your consumption is behaviour and dispatch rather than payload.
Cost intelligence
Cost per kilometre,
with all five
components in it
Acquisition finance, maintenance, fuel, insurance and depreciation for each vehicle, divided by the kilometres it actually ran. That number decides when to replace a vehicle. A purchase price does not.
Every cost lands on the vehicle
A workshop invoice, an insurance premium and a fuel transaction all attach to the registration they belong to, so whole-life cost accumulates as it is incurred rather than being allocated at year end.
Replace on the curve
Cost per kilometre rises as maintenance climbs and residual value falls. The crossing point is a date you can see coming, which is a different decision from replacing on a fixed age.
Illustrative. The shape is yours: Fleetza builds it from your own finance charges, workshop invoices, fuel transactions, premiums and depreciation policy rather than from an industry assumption, and the weekly report ranks vehicles by it.
How it works
Plugged in before lunch
- 01
Install and connect
The compact tracker goes into the vehicle’s diagnostic port in seconds — no wiring, no downtime, nothing removed from service. Live data reaches the dashboard within minutes.
- 02
Monitor and alert
Watch the fleet live while the AI reads for safety events, maintenance needs and policy violations. Alerts arrive while the issue is still small enough to be a conversation.
- 03
Cut cost, lift safety
Weekly AI reports rank your highest-cost vehicles, your riskiest drivers and your maintenance priorities, each with a recommended action attached rather than a chart to interpret.
“FlowZa Fleetza gave us visibility we never had before. Within two months, our accident rate dropped significantly, our fuel costs fell by nearly 20%, and our maintenance spend is now completely predictable. It pays for itself every month.”
Fleetza and LogisPro
Two systems, because
they answer two
questions.
They sit next to each other and people reasonably ask why there are two. The division is simple enough to state in a sentence each.
LogisPro
Plans and tracks the work
Routes, shipments and warehouses. Which drops go on which vehicle in which order, where the shipment is against its window, and whether the goods behind it were picked and packed correctly. The unit of work is a delivery.
Fleetza
Watches the vehicle and the driver
Condition, behaviour and cost. How the vehicle is being driven, what is about to wear out, what it costs per kilometre to keep running. The unit of work is a vehicle and the person in it.
You are here
They are separate systems on separate app subdomains, and they share the vehicle and driver records. A driver’s hours in LogisPro and their safety score in Fleetza belong to the same person, and a service hold recorded in Fleetza is visible to the planner in LogisPro without anyone entering it twice. Run either on its own; run both and neither needs an integration project to see what the other knows.
Questions fleet managers ask
What hardware is involved, and who fits it?
A compact tracker that plugs into the vehicle’s OBD-II diagnostic port. No wiring, no workshop visit and no vehicle out of service; anyone can fit one in seconds, and the vehicle starts reporting within minutes. Vehicles without a usable diagnostic port are the exception and are handled case by case.
Is driver scoring going to be used against our drivers?
That is a policy choice, and the product is built for the coaching version of it. The score decomposes into four named event types, every event behind it is dated and reviewable, and the driver sees the same board the manager does. A number a driver cannot take apart is a number they will dispute; a number they can is the basis of a two-minute conversation.
Does predictive maintenance replace the manufacturer’s service schedule?
No. Treat the schedule as a floor. Prediction moves work earlier when diagnostics and usage say a component will not reach the next interval, and it groups items so that one workshop visit covers several. It does not extend a manufacturer interval on its own.
Do we need LogisPro as well?
Only if you need the work planned. Fleetza is complete on its own for an operator who wants to know what their vehicles and drivers are doing and what they cost. If you are also sequencing drops, tracking shipments against delivery windows or running a warehouse, that is LogisPro — a separate application, bought separately, which you may or may not need.
Where does the cost per kilometre come from?
From recorded costs rather than an assumed rate. Acquisition finance, workshop invoices, fuel transactions, insurance premiums and depreciation attach to the registration they belong to and are divided by the distance that vehicle actually ran. Every component of the figure is traceable to the entry it came from, so an operational number and the one your accountant produces can be reconciled line by line.