Utilisation by asset, site and contract
Ignition, engine hours, PTO and movement combine into productive, idle and parked time, rolled up by depot, contract and asset class.
Fleet & Asset Operations
You know where the trucks are. You still cannot say which ones are earning.
Live location, utilisation and condition across every vehicle, trailer and mobile asset you run, whatever hardware is fitted.
- Built for
- Fleet, operations and finance teams
- Connects
- Any tracker brand, any carrier
- Deploys
- Sovereign cloud, private cloud or on-site
/ The shift /
What happens today, and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01A map shows where an asset is, not whether it did anything useful this week.
Finance asks for the second number.
- 02Three device brands mean three portals, three exports and a spreadsheet somebody rebuilds every Sunday to reconcile them.
- 03The route deviation, the idle trailer and the unauthorised trip are already in the data.
Nobody sees them until they arrive as cost.
/ How it works /
From signal to decision in four moves.
Each step runs on the shared IoT Cube foundation, so nothing here is a separate system to maintain.
- 1
Connect every tracker
Existing telematics, trailer trackers and CAN interfaces report into one registry, whatever the brand or carrier.
- 2
Tie position to the asset
Each device is linked to an asset, depot, contract and cost centre, so someone is accountable for the location.
- 3
Decide on utilisation
Engine hours, movement and idle time become productive hours per asset. Rules flag what is idle, misused or due for service.
- 4
Act on the exception
Alerts reach the named dispatcher or workshop lead, work orders open in your maintenance system, and client reports go out on schedule.
/ What you get /
What fleet & asset operations gives you.
One map across mixed hardware
Protocols from different tracker brands normalise into one position stream, with live and historical tracks on the same map and playback per trip.
Geofence and unauthorised-use alerts
Sites, routes and curfew windows are drawn once. Movement outside a permitted zone or time alerts with the asset, driver and location.
Maintenance triggered by real usage
Service intervals are set in engine hours or kilometres from CAN and odometer data. A work order opens in the workshop system as a threshold approaches.
Fuel matched to the work done
Fuel-card transactions and tank-level sensors are matched to position and engine hours. Fills away from the asset, or consumption out of pattern, flag.
Reporting that runs itself
Utilisation, trips and exceptions are packaged per client or contract and sent on a schedule, or exported on demand.
/ Use cases /
Where teams put it to work first.
Right-size the fleet
Use productive hours per asset and depot to buy, hire, reallocate or retire before the next capital request.
Reconcile fuel against movement
Match each fuel-card transaction to the asset’s position and engine hours, and send mismatches to finance with the track.
Service on real usage
Open workshop jobs from engine hours and kilometres, so vehicles come off the road when they need to.
Report utilisation to clients
Send each contract its trips, utilisation and exceptions on a schedule, from the operational record.
/ Benefits by team /
Every team gets a different answer from the same record.
01
Operations
Idle, misused and overdue assets arrive as exceptions for dispatch to act on.
02
Finance
Cost per productive hour and fuel exceptions come from one record.
03
Maintenance
Service triggers on usage read from the vehicle, and work orders open with the asset and readings.
04
IT
Mixed tracker brands and carriers feed one registry through open APIs, with no supplier portal to support.
/ In practice /
Three moments from a working week.
Each one starts with a signal and ends with someone acting on it. The scenarios are illustrative.
The signal
Fourteen trailers at the Jubail yard have not moved in three days while the Riyadh depot is hiring in capacity.
- 1
The platform flags the idle pool against the utilisation rule for that depot.
- 2
The fleet manager sees both depots side by side and reallocates the trailers.
- 3
Dispatch books the repositioning run before the next hire is confirmed.
The outcome
Existing assets are used before new capacity is paid for.
/ Technology /
Four layers. One record underneath.
Device-neutral at the bottom, open at the top, and sovereign all the way through.
01
Devices in the field
Keep the hardware you already have
- GPS and telematics units
- Trailer and container trackers
- OBD and CAN interfaces
- Fuel sensors
- Temperature probes
- Dashcams
02
Connectivity & protocols
Any carrier, any protocol
- MQTT
- Tracker-native TCP/UDP protocols
- CAN / J1939
- OBD-II
- BLE
- NB-IoT / LTE-M
- 4G/5G via any Saudi carrier
- Satellite for remote routes
03
IoT Cube platform
Sovereign, multi-tenant, AI-neutral
- Device registry & OTA
- Asset & identity record
- Geospatial engine
- Rules & alerting engine
- Reporting & exports
- Open APIs & webhooks
04
Your systems of record
Data lands where decisions are made
- ERP
- Maintenance and workshop systems
- Fuel cards
- TMS
- Finance
A regional transport operator brought location, maintenance and fuel data into one view. Utilisation became a weekly number, and the fleet-size decision they were about to make changed.
Story pending customer confirmation/ What you measure /
The numbers this produces.
Measured continuously, per asset, per site and per contract.
Asset utilisation
Productive hours as a share of available hours, per asset, depot and contract.
Idle time
Time with the engine running and no movement or work recorded.
Cost per productive hour
Fuel, maintenance and ownership cost divided by the hours an asset actually worked.
Unauthorised use events
Movements outside approved zones, hours or assignments, and how quickly each was closed.
Maintenance compliance
Services completed on the usage-based schedule versus overdue, by asset class.
Fuel exceptions
Fuel transactions or consumption that do not match the asset’s position or engine hours.
/ Rollout /
Start with one decision. Scale what works.
- Phase 1
Map the fleet and the question
We list your assets, device brands, carriers and systems, and agree the decision to answer, usually utilisation or fleet size.
- Phase 2
Connect a pilot depot
One depot’s existing trackers and fuel data are connected, and assets are linked to contracts and cost centres.
- Phase 3
Prove the utilisation number
Operations and finance review weekly utilisation and exceptions, and the rules are tuned until the number is trusted.
- Phase 4
Scale across depots
Remaining depots, device brands and client reports are added on the same model, one depot wave at a time.
/ Security & sovereignty /
Where your data lives, and who can reach it.
- In-Kingdom residency
- Built to national controls
- Isolated by tenant
- Your cloud or site
/ Built on IoT Cube /
Products already doing this.
Each one runs this solution on the shared foundation.
Built on IoT Cube
tracking.me
AI and IoT fleet management for Saudi Arabia: routing, driver safety, predictive maintenance, RFID and tyre management.
Built on IoT Cube
TEFCO
Saudi distributor of IoT and telematics hardware: trackers, dashcams, sensors, RFID, routers and EV chargers, fitted and supported.
Built on IoT Cube
Raceed
Fleet expense management with NFC fleet cards, spend controls, analytics and fraud detection.
Built on IoT Cube
Gorex
On-demand car care and vehicle maintenance, booked in a few taps at a chosen time and place.
/ Industries /
Where this solution shows up.
/ Questions /
Frequently asked.
Almost certainly. Device neutrality is the design principle, and we test your tracker brands before anything is committed.
/ Explore more /
Other solutions on the same foundation.
See fleet & asset operations on your own assets.
Bring the hardware you already run. We will connect a sample of it and show you the operating picture it produces.