Fleet data ownership and export: questions before signing
Owning your fleet data and being able to leave with it are two different contract terms. Confirm the rights, who can request an export, the records, format, metadata, cost and retrieval window, then test whether a recipient can read a sample export.
Where ReWheel stands
ReWheel can offer a deployment in a Canadian region, and in other countries' regions on request; storage, processing and access locations and subprocessors are confirmed in a reviewed deployment proposal.
Ask for rights and retrieval separately
Portable-data checklist
- Which raw records, corrections and derived reports fall within the agreement's rights and export scope?
- Who can authorize an export, and what access checks apply?
- Which file formats, field definitions, units, identifiers and time context accompany it?
- Is a file export, API or other interface included, and what limits or charges apply?
- Can the recipient distinguish missing, corrected, estimated and historical values?
- What retrieval period applies after service ends, and who verifies completion or any requested deletion?
An API description does not establish a contractual right or a retention period, and a CSV filename does not show that all required records are present. Ask for an authorized test export.
Run a recipient test before relying on portability
Acceptance steps
- Authorize the requester and agree on a bounded record scope.
- Export representative records and compare their count and field definitions with the agreed scope.
- Have the recipient identify units, source, observation time and any corrections without help from the file author.
- Check stable identities, duplicate handling and a missing or qualified value.
- Record unresolved fields, applicable charges and who accepts the result.
Keep deletion separate from retrieval: ask for the process, coverage and written confirmation, including backups and holds.
Portable fleet-data CSV schema
Use the two sample records to plan a recipient test.
On a small screen, scroll this table horizontally. Keyboard users can focus the table region and use arrow keys.
| Field | Example value | Meaning |
|---|---|---|
| record_id | R-001 | Stable record identity within the stated export scope |
| asset_id | TRUCK-01 | Stable local asset identity, with a separate mapping if needed |
| observed_at_utc | 2026-10-28T14:00Z | Observation instant in UTC, not file creation time |
| time_zone | America/Edmonton | Named zone for local display/report boundaries |
| signal | trip_distance | Field definition, distinct from an odometer reading |
| value and unit | 12.5 km | Typed value with its explicit unit |
| source | gps | Origin of the value |
| quality_status | example | Qualification kept with the value |
What ReWheel provides
ReWheel FMS connects supported vehicle information with equipment and operational records for field and institutional operations. Vehicle compatibility, data-access requirements, connectivity and installation are assessed per deployment, never assumed.
Continue with ReWheel: Operational fleet records for Canadian buyers
Discuss your workflow