Fleet utilisation, so you know whether you need 12 vans or 9
One percentage per asset, and what to do about it
Utilisation is arithmetic, so we publish the arithmetic. The rest of this page is what Yipii does with the number once it has it.
The utilisation percentage
Actual distance divided by the target you set, times 100. Calculated daily for every asset, so any two vehicles compare directly.
Windows and date ranges
Rolling 7, 30 and 90-day windows sit on the dashboard. Today, this week, this calendar month or a custom range answer a specific question.
Ranked recommendations
High, medium and low severity, each naming an asset or a group and the action: sell, reassign, review fleet size, or book extra servicing.
Targets per asset type
A weekly distance target with your own under and over thresholds, set by asset subtype, by asset type, or once for the whole fleet.
How fleet utilisation is calculated
Utilisation % = (actual distance ÷ target distance) × 100
Put a 500 km weekly target on a van, let it cover 300 km, and it reads 60%. That is the entire calculation, which means the number is only ever as sensible as the target behind it. Benchmarks are configurable for exactly that reason.
The gauge runs from 0 to 120% and splits into three zones, drawn around the thresholds you set on the benchmark.
Below your under threshold
The asset is not meeting target. Far enough below and this becomes the sell or reassign conversation.
Inside the target band
Where you want most of the fleet to sit. Nothing to act on.
Above your over threshold
The asset is at risk of accelerated wear, so it wants earlier servicing rather than a conversation with the driver.
A bad week is not a bad van
One quiet week means very little on its own. Yipii calculates utilisation daily and keeps rolling 7, 30 and 90-day windows, so a fortnight off the road for a gearbox shows as a dip in the 7-day figure and barely moves the 90-day one. When you need a specific period instead, switch to today, this week, this calendar month, or a custom range.
- Rolling 7, 30 and 90-day windows, recalculated daily
- Today, this week (Monday to Sunday), and this calendar month
- Custom range for a quarter, a season, or a single contract
- Direction of travel per asset, so a climbing figure reads differently from a falling one
Included with Yipii Mobility, the add-on that extends your IoT account. One subscription covers everything in the app, so no feature here is sold on its own. What Yipii Mobility includes
The panel names the asset and the action
Yipii sorts what it finds into four groups: under-utilised assets, over-utilised assets, patterns by asset type, and patterns by group. Each one arrives ranked by severity and written as a sentence, so nobody has to interpret a chart to know what is being suggested.
"Asset BCX-926 significantly under-utilised at 15% of target. Consider selling or reassigning."
One asset a long way below target. This is the line that changes the size of the fleet.
"5 assets in the School Transport group consistently below target. Review fleet size."
A pattern across a group rather than a single bad week. Cheaper to fix once than five times.
"Asset MDC-215 slightly over-utilised. Schedule extra maintenance."
Worth acting on while it is still a service booking rather than a breakdown.
Targets cascade from specific to general
A refrigerated van and a supervisor's car should never share a distance target. Yipii looks for the most specific benchmark it can find and falls back until it lands on one.
Every benchmark holds three numbers: a weekly distance target, an under-utilised threshold (60% is a common starting point) and an over-utilised threshold (110%). Change them once and every gauge tied to that benchmark moves with them.
- 1
Asset subtype
The tightest match Yipii looks for. A 3.5 t box van carries a different weekly distance target from a crew cab.
- 2
Asset type
Used when the subtype has no benchmark of its own. One target for every van, one for every car, one for every trailer.
- 3
Fleet default
The fallback that catches everything else, so no asset ends up without a target to be measured against.
Two places the gauge misleads you
Benchmarks are not time-sliced
A fleet running airport transfers in July and August covers far more ground than the same fleet in January. Yipii holds one weekly distance target per benchmark with no seasonal calendar behind it, so a tourist-season fleet reads over-utilised all summer and under-utilised all winter against a single year-round number.
The correction is manual. Raise the target going into the season, drop it again afterwards, and treat the recommendations from the shoulder months with a bit of suspicion.
An asset with no data reads 0%
Utilisation needs either a tracker reporting trips or regular odometer entries, plus a benchmark on the asset type. Without both, the asset sits at 0% and looks like the worst performer in the fleet when it is only unmonitored.
A vehicle in seasonal storage has the same problem: the arithmetic is right and the advice is wrong. Fitting a tracker that reports trips removes most of this.
Frequently asked
Utilisation % = (actual distance / target distance) x 100. Yipii runs it daily for every asset and keeps rolling 7, 30 and 90-day windows on the dashboard. The actual distance comes from IoT tracker trips where a tracker is fitted and from odometer readings where one is not. The target comes from the benchmark attached to the asset subtype, then the asset type, then the fleet default, in that order.
Whatever you decide, because a courier van and a director's car have nothing in common. Yipii holds thresholds rather than verdicts: 60% for under-utilised and 110% for over-utilised are common starting points, and both are configurable on every benchmark. Run the fleet for a month, look at where the vehicles you are happy with land, and set the weekly distance target around that.
IoT tracker trips are the primary source. Odometer readings act as the backup for assets with no tracker fitted. Fuel logs, engine hours and idle time, meaning stationary time with the ignition on, add to the picture without being required. An asset with neither tracker trips nor odometer entries will not calculate a figure and shows 0%.
Yipii flags it as high severity and suggests selling or reassigning it. Check two things before you act. First, that the asset is reporting properly, because a flat tracker battery and an idle van look identical on a distance chart. Second, that the benchmark on its type is realistic: a van doing short runs around Valletta all day covers very little distance and is not idle at all.
No. Mobility is quoted as one subscription covering the whole app, so utilisation arrives with maintenance, costs, drivers, time tracking and the rest whether you asked for them or not. That is a deliberate contrast with Yipii IoT, where individual capabilities genuinely are add-ons you pick from a list. A Mobility quote starts from the IoT account you already run and puts the app on top of it, so the conversation is about fleet size rather than which features you want switched on.
What sits next to utilisation
Utilisation is one screen inside the Mobility app. The same subscription covers every page below, so none of them is a separate line on a quote.
Fleet size is the argument that decides a quote on two industries in particular, construction and plant and logistics and distribution. The benchmark fields, the recommendation types and the setup steps are written out in the utilisation guide in the Yipii Mobility docs.