Utilisation by asset, site and contract
Ignition, engine hours, PTO and movement are combined into productive, idle and parked time. Results roll up by depot, contract and asset class, so the weekly number is calculated, not argued.
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 operate — regardless of who supplied the hardware.
- Built for
- Fleet, operations and finance teams
- Connects
- Any tracker brand, any carrier
- Deploys
- Sovereign cloud, private cloud or on-site
/ The shift /
What is actually happening today — and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01Location is not utilisation.
A map tells you where an asset is. It does not tell you whether it did anything useful this week, and that is the number the finance director is asking for.
- 02Every supplier brought a portal.
Three device brands, three logins, three exports, and a spreadsheet somebody rebuilds every Sunday night to make them agree.
- 03Problems are discovered late.
The deviation, the idle asset, the unauthorised movement — all visible in the data, none visible to a person, until it is a 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. No rip-and-replace.
- 2
Tie position to the asset
Each device is linked to an asset, depot, contract and cost centre, so a location becomes a record someone is accountable for.
- 3
Decide on utilisation
Engine hours, movement and idle time are turned into 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 reports go to clients on schedule.
/ What you get /
Capability, not just visibility.
One map across mixed hardware
Device protocols from different tracker brands are normalised into one position stream. Live and historical tracks sit on the same map, with playback per trip.
Geofence and unauthorised-use alerts
Sites, routes and curfew windows are drawn once. Movement outside a permitted zone or time raises an alert with the asset, driver and location attached.
Maintenance triggered by real usage
Service intervals are set in engine hours or kilometres from CAN and odometer data. When a threshold approaches, a work order opens in the workshop system.
Fuel matched to the work done
Fuel-card transactions and fuel-level sensors are matched to position and engine hours. Fills away from the asset’s location, or consumption out of pattern, are flagged.
Reporting that runs itself
Utilisation, trips and exceptions are packaged per client or contract and sent on a schedule, or exported on demand, from the same record operations uses.
/ Use cases /
Where teams put it to work first.
Right-size the fleet
Use productive hours per asset and depot to decide whether to buy, hire, reallocate or retire vehicles before the next capital request.
Reconcile fuel against movement
Match every fuel-card transaction to the asset’s position and engine hours, and send mismatches to finance with the track attached.
Service on real usage
Open workshop jobs from engine hours and kilometres rather than dates, 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 same record operations works from.
/ Benefits by team /
Every team gets a different answer from the same record.
01
Operations
Idle, misused and overdue assets surface as exceptions, so dispatch acts on the problem instead of searching for it.
02
Finance
Cost per productive hour and fuel exceptions come from one record, not a spreadsheet rebuilt every week.
03
Maintenance
Service is triggered by usage from the vehicle, and work orders open with the asset and readings attached.
04
IT
Mixed tracker brands and carriers feed one registry through open APIs, without another supplier portal to support.
/ In practice /
What it looks like on an ordinary Tuesday.
Three moments where the platform earns its place. 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 stopped being an argument and became a weekly number — which changed the fleet-size decision they were about to make.
Story pending customer confirmation/ What you measure /
Numbers that replace arguments.
The indicators this solution produces 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 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 you need answered — usually utilisation or fleet size.
- Phase 2
Connect a pilot depot
One depot’s existing trackers and fuel data are connected to the platform. Assets are linked to contracts and cost centres.
- Phase 3
Prove the utilisation number
Operations and finance review weekly utilisation and exceptions from the pilot, and tune the rules until the number is trusted.
- Phase 4
Scale across depots
Remaining depots, device brands and client reports are added on the same model. Weeks, not quarters, per wave.
/ Security & sovereignty /
Sovereign is a place, not a promise.
In-Kingdom residency
Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.
Built to national controls
Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.
Isolated by tenant
Tenant isolation, role-based access and a full audit trail across users, actions and devices.
Your cloud or site
Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.
/ Built on IoT Cube /
Runs on the platform, not beside it.
Products already running this solution on the shared foundation.
Built on IoT Cube
tracking.me
Saudi AI and IoT fleet tracking, telematics, RFID, tyre management and connected mobility solutions.
Built on IoT Cube
TEFCO
Saudi IoT and telematics hardware — GPS tracking, RFID, AI cameras, sensors and RTLS, installed and supported.
Built on IoT Cube
Raceed
Saudi fleet expense management with NFC fleet cards, real-time spend controls, analytics and fraud detection.
Built on IoT Cube
Gorex
On-demand car care — convenient vehicle maintenance and automotive services, booked in a few taps.
/ Industries /
Where this solution shows up.
/ Questions /
Frequently asked.
Will it work with the trackers we already have?
Almost certainly. Device neutrality is the design principle, and proving it with your specific hardware is usually the first thing we do in a demo.
Can we keep our current supplier?
Yes. Most customers do. We connect their data rather than replace their contract.
How is this different from the tracking platform we already pay for?
Tracking answers where. This answers whether it is worth it, what is about to break, and who needs to act.
Can it support our TGA tracking obligations?
Where your vehicles fall under TGA tracking requirements, position data can be forwarded through a WASL integration. Tell us your licence activity and we will confirm the scope before we build it.
Does it connect to our ERP and fuel cards?
Yes. Open APIs and webhooks carry utilisation, trips and exceptions into ERP, TMS and workshop systems, and fuel-card transactions come back in to be matched against the asset.
Who owns the data, and can we take it out?
You do. Data stays resident in the Kingdom, and full history can be exported or pulled through the API at any time. Nothing is held hostage to the contract.
/ Explore more /
Other solutions on the same foundation.
Cold Chain & Compliance
Monitor conditions continuously and create the operational record while products move.
Driver Safety & Journey Management
Connect journeys, behaviour, safety events and operational response.
Predictive Maintenance
Use condition and usage data to move from failure response to planned work.
Bring us the decision that takes too long today.
Start with the problem. IoT Cube provides the foundation underneath.