Vehicle Tracking & Fleet Telematics · Technical White Paper
Vehicle Tracking & Fleet Telematics
A technical method for separating the requirement from the subscription, making an exit liability negotiable, folding switching costs into the business case, and governing the data the platform produces.
1 · Category definition
Vehicle tracking is not one product
Industry practice distinguishes stolen-vehicle-recovery systems, fleet-management systems, and systems combining both. The Motor Vehicle Security Association of South Africa also encourages buyers to test recovery performance, product approval, fitment standards and device health-check capability rather than relying on price alone.
The practical implication is straightforward: define the function before comparing the subscription. A recovery-oriented requirement is fundamentally different from a requirement to manage a distributed fleet operationally.
If the organisation uses geofences, trip reports, driver-behaviour data, productivity reports or exception alerts, those belong in the specification. If it does not use them, it should not keep paying for them because they were bundled historically.
10 · Switching economics
Where supplier comparisons usually fail
A comparison that shows the new quotation on one side and the current invoice on the other, while ignoring termination fees, settlement, removal, refitment, downtime and internal effort, produces an attractive and incomplete saving.
Here the exit settlement was material enough to require explicit integration. KuTh negotiated the settlement down first, then deducted the switching cost from the period-based saving calculations in the options paper. The business case remained positive in the preferred scenarios after the exit cost was recognised.
That sequence also helps governance. Decision-makers can see whether value comes from a sustainably lower recurring cost or merely from excluding one-off transition costs — and the approved business case then becomes the baseline for verifying savings after implementation.
11 · Procurement design
Ten variables to specify instead of price per tracker
Scroll table sideways →
| Variable | What to define |
|---|---|
| Functional scope | Recovery, fleet management or both. List required features and mark optional ones separately, so they do not become embedded cost by default. |
| Recovery assurance | Product approval, installer standards, recovery-process capability, health checks, and the evidence the organisation or its insurer expects. |
| Fitment model | Mobile, on-site or workshop installation; who carries travel or call-out cost; expected downtime; de-installation; damage responsibility. |
| Warranty architecture | What the device warranty covers, whether it is embedded, whether extended cover is necessary, and how it interacts with manufacturer warranty. Avoid paying twice for one risk. |
| Escalation | Basis, cap or index; when it applies; whether it touches all components; and any right to renegotiate or exit if the commercial basis changes materially. |
| Commencement and expiry | A vehicle-level schedule of activation, product, price, contract status and expiry — so the fleet does not become a collection of unmanaged legacy contracts. |
| Additions and disposals | Rules for vehicles entering or leaving, so a contract does not keep billing against a disposed asset because a process failed to close. |
| Reporting | Active units, failed units, exceptions, usage, recovery incidents, open fitments, contract status, credits, escalations and billing changes. |
| Price architecture | Separate hardware, installation, connectivity, software, recovery, warranty and value-added services, so later rightsizing is possible. |
| Exit and migration | Pre-agree removal, data extraction, settlement mechanics, device ownership and handover — switching should be a managed event, not an emergency negotiation. |
12 · Data governance
Telematics creates an obligation as well as an opportunity
Vehicle location, trip history, driving behaviour, identifiers and alert data may constitute personal information where it relates to, or can be linked to, an identifiable driver or employee. POPIA then applies its conditions for lawful processing: accountability, processing limitation, purpose specification, openness, security safeguards and data-subject participation.
Procurement should not leave privacy and information security to a supplier's generic terms. The organisation needs to establish why the data is collected, who may access it, how long it is retained, when it may be used for driver management, how credentials are controlled, what security obligations bind the provider, and what happens to the data when a vehicle or supplier leaves the fleet.
The responsible-party and operator roles should also be understood. Commonly the organisation determines the purpose while the provider processes data to deliver the service, but the legal roles depend on the arrangement. The contract should address processing instructions, confidentiality, security measures, incident notification, sub-processing, retention and deletion, rather than assuming the technology provider owns the compliance problem.
Governance checkpoint
The more detailed the tracking and driver analytics, the stronger the need for purpose, access and retention discipline.
Buying more data than the organisation uses is both a cost issue and a governance issue — and the two have the same remedy.
13 · Post-award control
Where value is lost after the decision
The sourcing decision is the midpoint. Value disappears if old services stay active, vehicles are missed, fitments disrupt operations, or the new billing does not match the approved model.
- A master vehicle register carrying registration, VIN where appropriate, assigned product, incumbent status, new supplier status and fitment state.
- A cutover plan identifying which vehicles can move immediately and which require settlement, release, removal or substitution.
- Verification that deactivated services actually stop billing, rather than continuing against vehicles that have already moved.
- Reconciliation of the first invoices under the new arrangement against the approved commercial model.
Conclusion
Three questions, asked in the right order
What does the organisation actually need? What is the contract position on each vehicle? What does switching really cost once settlement, removal and refitment are counted?
Answering those before comparing subscriptions is what produced the useful findings here: an exit liability reduced by 81.7% and therefore no longer a barrier, a like-for-like market reduction of 43.6%, and a recovery-only specification that models at 73.9% — not because it is a better deal, but because it is a different service answering a different requirement.