When a location dot is not the whole picture

What sits behind the dot

A location appears on a tracking screen. Before acting on it, the person watching needs to know when the position was measured, when the system received it and how reliable it is. A displayed position may be useful, but its meaning depends on the information behind it.

The device first needs a way to establish its position. It then needs a communication path to report that position, a platform to display it and people who know how to respond. Each stage has its own dependencies. Understanding them helps a business distinguish a routine communication gap from a problem that needs urgent attention.

This article explains those dependencies and the questions they raise. The assessment steps below are proposals. No installed device, named supplier or proprietary recovery system has been audited for this article.

1. Finding a vehicle and reporting its position are separate jobs

Several technologies can contribute to a tracking service. Their roles differ, so the first useful question is which job each part of the actual product performs.

These descriptions explain the technologies in general. Proprietary radio recovery networks, satellite messaging and other combinations require evidence from the relevant supplier before their capabilities can be assessed.

2. What an interruption can mean

A device can have a valid local position while being unable to report it. It can also communicate while its position is unavailable or unreliable. A monitoring platform needs to make those distinctions clear.

Jamming disrupts reception of genuine satellite-navigation signals. Spoofing supplies counterfeit signals that can mislead a receiver. The European Union Aviation Safety Agency documents both mechanisms in aviation. That evidence explains how interference works; it does not establish how often it occurs in South African vehicle tracking. ^[5]

These are scenarios to assess. Coverage gaps, equipment faults and maintenance can also explain a missing report. An unusual position or a silent device alone cannot establish criminal interference.

South African police have reported recovering a signal-jamming device and linked such devices to hijacking activity. That makes interference a locally relevant question for suppliers. The report provides no national prevalence estimate and does not demonstrate that a particular tracking product can be defeated. ^[6]

3. Ask for evidence that the whole service works

The US National Institute of Standards and Technology’s connected-device baseline offers a starting point for procurement: devices should be identifiable, their configuration controlled, data protected, interfaces restricted, updates secured and their security state visible. A supplier should be able to explain how these capabilities apply to its product. ^[7]

1. Map the service. Record device models, firmware, connectivity, platform, data flows and support contacts. Identify responsibility for each stage, including subcontractors and end-of-support dates.
2. Agree what “working” means. Set acceptable reporting delays, alert-delivery times and escalation times. Distinguish the time a position was measured from the time its message arrived.
3. Test interruptions safely. Use supplier-approved simulations, controlled loss-of-connectivity scenarios and tabletop exercises. Do not transmit interference or attempt unauthorised radio tests.
4. Control access and changes. Use strong authentication for sensitive accounts, separate operational roles, limit privileged access and review relevant activity records. Where remote commands exist, match their controls to their consequences.
5. Check how support will continue. Ask about secure updates, vulnerability reporting, patch commitments and the plan for devices or networks reaching the end of their useful life.
6. Rehearse the response. Confirm that an alert reaches someone accountable, that supplier handovers work and that staff know how to handle uncertain data. Receiving a notification and taking action are separate events.

These are proposed assessment actions, with the appropriate tests determined by the product and its operational use. Two devices that depend on the same network or other point of failure may provide less resilience than their number suggests. Ask suppliers to demonstrate the independence and performance of any fallback arrangements.

4. Plan for network changes and responsible use of location data

Get the current transition plan

South Africa’s May 2024 spectrum policy included a preliminary roadmap with 31 December 2027 as the date for total 2G/3G shutdown, with dates and sequencing subject to assessment. That historical policy does not establish a current shutdown commitment for every operator. Before buying, renewing or replacing equipment, obtain the relevant operator’s and device supplier’s latest written transition plan. ^[8]

Give location information clear rules

Tracking records that identify a person need deliberate decisions about purpose, access, retention and supplier responsibilities. Establish who can use the information and how a suspected compromise will be escalated. The Information Regulator’s guidance describes security-compromise notification duties and the involvement of the Information Officer; reporting need not wait for an investigation to finish. The applicable duties require assessment when an incident arises. ^[9]

Keep operational decisions accountable

Changes to production systems, recovery actions and safety-relevant commands need defined approval, testing and rollback arrangements. Improvements to monitoring rules should be reviewed and measured. Supplier answers, clear responsibility and rehearsed procedures can improve readiness.

Six questions to take into the supplier meeting

1. Which parts of the service remain usable when positioning, mobile connectivity or external power fails?
2. How do you detect and communicate unreliable or old data, and what are the known limitations?
3. Which tests demonstrate the performance and independence of your fallback arrangements?
4. What are the device, firmware and network support dates, and who pays for and performs migration?
5. What evidence supports your account protection, update security, activity records and incident handling?
6. Who takes responsibility when contact is lost, and when was that handover last rehearsed?

A useful tracking service connects observations to an effective response. Understanding how that connection works is a practical foundation for procurement, daily operation and recovery planning.