Core records
Keep a stable vehicle identifier separate from registration, which may change. Link devices through time-bounded assignments. Keep drivers, depots and fleets distinct, with explicit relationships and access scope.
Telemetry and event records
Retain device identity, source timestamp, received timestamp and units. Events should have stable identifiers so retries can be handled without duplicates. Location quality and missing values should be explicit.
Time and audit
Store an unambiguous timestamp and display the intended timezone. Preserve effective time separately from the time a correction was recorded. Record actor, reason and previous values for changes that affect operational interpretation.
Integration discovery
Agree supported entities, read and write permissions, update frequency, failure handling and data retention with Fleetly. This is a conceptual reference, not an executable API specification; obtain the account-specific API contract before building.
Your action checklist
- Stable identifiers
- Explicit units and timezones
- Duplicate handling
- Access and retention agreement
Product availability depends on your devices, integrations, permissions and enabled modules. Confirm your organisation’s configuration before implementation.