Tracking ten vehicles is a software problem. Tracking two thousand vehicles across departments, regions and contractors is an organisational one. The map is the easy part; the hard parts are who is allowed to see what, how reports reach the right manager, how every vehicle stays compliant, and how a rollout reaches the last depot without stalling. This page covers enterprise fleet GPS tracking, and those problems in particular, for government-linked bodies and large multi-site companies in Saudi Arabia, and how HHET configures a vehicle tracking system with fleet management software around them. For other sectors, see the wider list of industries we serve.
Multi-site, multi-department fleets
A large fleet is rarely one fleet. A ministry directorate, a utility or a retail group typically runs separate pools: staff transport, maintenance vans, heavy trucks, pool cars and executive vehicles, often split across Riyadh, Jeddah, Dammam and smaller regional offices. Each pool has its own budget holder, its own rules and its own idea of what a normal day looks like.
The usual failure is a single flat list of vehicles with a single administrator. Nobody trusts it, so each department keeps its own spreadsheet. The platform should instead mirror the organisation:
- A hierarchy of groups matching region, department and cost centre, so every vehicle sits in the place a manager would expect to find it.
- Consistent naming and asset records (plate, chassis, driver, assigned department) loaded once at the start, not typed by hand at each depot.
- Different device sets by pool. Staff buses and pool cars need position and speed; heavy trucks add fuel and door inputs; special vehicles may add temperature or panic inputs. One platform, several hardware kits.
Getting this structure right in week one saves months of reorganising later, and it is the part we plan with you before a single tracker is fitted.
Roles, permissions and reporting lines
With many users, access control stops being a setting and becomes the design. A regional manager should see her region and nothing else. An auditor needs to read every report but never change a geofence. A contractor's supervisor needs a live view of the trucks he supplies and no view of the rest of the pool.
| Role | Typical scope | Can do | Cannot do |
|---|---|---|---|
| Platform administrator | Whole organisation | Create users, groups, alert rules, integrations | Nothing is hidden, so keep the number of admins small |
| Regional or department manager | Their own group tree | Live map, reports, alert acknowledgement, driver assignment | See other regions, edit organisation-wide rules |
| Dispatcher or control room | Assigned vehicles or shifts | Live tracking, geofence alerts, trip history | Change users or export the full database |
| Auditor or compliance officer | Read access across groups | Run and export scheduled reports | Edit settings or vehicles |
| Contractor supervisor | Contracted vehicles only | Live view and trip reports | See any other vehicles or history |
Reporting lines work the same way. Scheduled reports go to the person responsible for the vehicles, with a summary rolling up to the director, so exceptions reach the manager who can act on them rather than being buried in a monthly pack that no one opens. Every login and every settings change should be recorded, because in a large organisation the question is not only what the vehicle did, but who changed the alert rule last Thursday.
Compliance at scale
Compliance is simple on one vehicle and slippery on a thousand. The risk is not the headline requirement; it is the forty vehicles where the SIM lapsed, the plate was updated but not the platform, or the tracker was removed during a workshop visit and never refitted.
Vehicles operating under a Transport General Authority (TGA) licence may need to be linked to the WASL platform, and requirements vary by activity and vehicle class. Government entities may also follow their own procurement and data-handling rules, including hosting and access policies. Confirm what applies to your organisation with the relevant authority and your internal compliance team before specifying a solution.
What we can do at the platform level is make compliance visible. A fleet-wide health report lists vehicles that have not reported in 24 hours, units with a disconnected main power feed, and tracker identifiers that do not match the asset record. Our TGA and WASL tracking guide explains how the linking process works and what we confirm with you first.
Data handling needs its own thought. Position history is personal data when it can be tied to a named driver. Decide up front who may export it, how long it is kept and how drivers are informed. Our privacy policy describes how HHET treats platform data, and your own HR and legal teams should set the rules for staff.
Rollout and training
Large rollouts fail on logistics, not technology. A sound plan in Saudi conditions has four stages.
- Audit and structure. Reconcile the vehicle list with the actual fleet. Agree the group hierarchy, naming, device kits and who owns each vehicle record.
- Pilot at one or two sites. Fit a representative sample, such as a depot in Jeddah and one in Riyadh, in a mix of vehicle types. Use the pilot to test alert rules, report schedules and installation times in real heat and dust.
- Waves by region. Move through the fleet in scheduled waves, with installers working at your depots where vehicles are parked, so vehicles lose hours rather than days. Each vehicle is tested on the platform before the installer leaves, using the same sequence described in our GPS installation service.
- Train by role. Administrators learn structure and alerts, managers learn reports, dispatchers learn the live view, and drivers are told plainly what is recorded and why. Short role-based sessions work better than one long demonstration.
Plan for the first ninety days of operation as well as the rollout. Alert volumes are always too high at first, and tuning them with the managers who receive them is what turns a map into a working tool. Add a named contact for the support escalation path, so a failed unit in a remote region does not wait in a general queue.
The result to aim for is a platform that the finance, operations and audit teams all use for their own reasons, because each of them sees the same trusted record. To start scoping a large deployment, send the vehicle counts by region and pool through our quote request form.

Last reviewed .

