CONNECTED TECHNOLOGY. CLEARLY EXPLAINED.
Fleet trackers
Choose fleet-tracking hardware through vehicle fit, positioning and delivery needs, power behaviour, regional network support and controlled access to trip records.
A fleet tracker is one component of a tracking service. Useful operation depends on the installation, position estimate, communication path, configuration and platform that receives the record. Review those parts together before treating a moving marker as a current or complete vehicle record.
Specify the hardware in its operating context
Identify the vehicle and installation
Record the exact vehicle, permitted power/interface connection, mounting location and installer responsibility. Distinguish a removable diagnostic-port unit, a wired tracker and an independently powered asset device. Use the vehicle and tracker instructions for the actual installation rather than transferring one format’s assumptions to another.
Define useful record age
Decide how recent a record needs to be for the task. Keep position capture, record creation, attempted transmission and platform receipt distinct. A display’s refresh rate alone does not establish the age or accuracy of the position being shown.
Confirm the whole service
Match the regional hardware variant, radio support, operator plan, platform and firmware. Ask who manages configuration, subscriptions, updates and support. Include network changes and service exit in the decision; the same product family can have variants that do not suit the same deployment.
Follow power, position and records through the service
Positioning and delivery are different
Ask the provider to explain how the chosen device estimates position and how it delivers records. Review the intended mounting and representative operating environments. Mark stale or unavailable positions clearly; a satellite-positioning capability does not establish continuous communication, indoor accuracy or a recovery service.
Capture settings and sending settings
The FMC920 documentation separates acquiring records from attempting to send them, with time, distance, angle or speed-change acquisition options. Use this as a model-specific example of configuration choices. Request the actual fleet configuration and distinguish expected record intervals from a guaranteed delivery time.
Parked operation and wake-up
Check the documented power source, sleep modes and wake-up behaviour for the exact firmware. Teltonika’s FMC920 sleep guide describes modes that change GNSS and communication behaviour. A parked vehicle’s latest visible position must not automatically be described as a newly measured location. Include authorised power-use and recovery observations in a pilot.
Inputs, accessories and platform interpretation
List the required vehicle signals and accessories, then confirm their physical interface, configuration, units and platform support. Keep a directly received measurement distinct from a platform estimate or classification. Record which functions are unsupported rather than filling a dashboard with assumed values.
Driver privacy and restricted records
Agree the purpose, access, private-use handling and retention before deployment. Geotab’s Restricted Data Mode documentation distinguishes its MyGeotab database from separate, time-limited Gateway storage and notes that some non-GPS features continue. A privacy setting’s name alone does not prove that all collection has stopped or every copy has been erased.
Support, export and retirement
Assign responsibility for installation faults, missing records, firmware changes and account access. Check export fields, device ownership, recurring fees and the process for replacing a unit or moving a vehicle. Remove unnecessary access and follow the documented process when equipment or subscriptions are retired.
A bounded demonstration to request
Choose an authorised representative vehicle and a defined operational question. Compare capture and receipt timestamps, review a documented parked state and examine how unavailable data appears. Use demonstration identifiers in public examples. This is a proposed evaluation record, not an IoTPapa road test, installed fleet or achieved saving.
Primary technical references
Teltonika: FMC920 acquisition settings and FMC920 sleep modes describe one tracker’s configuration. Geotab: Restricted Data Mode explains a platform-specific privacy boundary. None is a certification of a different product or service.
From hardware to operations
Fleet and telematics covers exception handling, operator responsibilities and the wider service. OBD adapters covers occasional diagnostic access. Keep those workflows distinct when preparing a shortlist.
By Admin · Reviewed 18 October 2026. Documentation-based product-type guide; no vehicle installation, tracking trial, driver assessment, power measurement or network-coverage result claimed. Return to Automotive IoT.
Develop the vehicle and operational brief
EXPLORE FURTHER
Fleet and telematics
Build a service around records and operator decisions.
EXPLORE FURTHER
OBD adapters
Review diagnostic information and exact vehicle coverage.