Tread pulls live paver telemetry from your paving machines to drive paving stats and moving geofences (a geofence — a virtual fence around a site — that follows the paver as it works). Use this for linear paving jobs where a static geofence does not cover the work.Documentation Index
Fetch the complete documentation index at: https://docs.tread.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A paver fitted with a supported tracker that exposes a position feed.
- A Tread admin user with the Integrations permission.
- An equipment record in Tread for the paver.
- A paving project in Tread with moving geofences enabled.
How it works
- Connect the tracker — Tread reads paver position from the tracker’s API.
- Match paver to equipment — The tracker’s vehicle ID maps to a Tread paver equipment record.
- Stream position — Tread receives the paver’s GPS position on a recurring poll.
- Move the geofence — The job’s geofence follows the paver as the paving line advances.
- Calculate paving stats — Tons placed, lane-miles covered, and idle time roll up into project reporting.
What flows where
| Data | Direction | Frequency |
|---|---|---|
| Paver GPS position | Paver Tracker → Tread | Recurring poll |
| Paver active/idle state | Paver Tracker → Tread | Real time |
| Tons placed (where supported) | Paver Tracker → Tread | TODO: confirm with engineering |
| Vehicle metadata | Paver Tracker → Tread | On connect |
Setup
Match paver to equipment
Tread lists pavers from the tracker feed. Map each to a Tread equipment record.
Enable moving geofences on the project
Open the paving project, turn on moving geofences, and pick the paver to follow.
Limitations
- One paver tracker provider per Tread company.
- Moving geofences need a clean GPS signal. Tunnels and overpasses can pause updates.
- Tons-placed data depends on what the paver tracker exposes — not every tracker reports volume.
- Pavers swapped mid-project must be re-mapped before the geofence follows the new machine.
- Long-term historical position lives in the tracker provider, not Tread.
Troubleshooting
Geofence not moving with the paver- Confirm moving geofences are enabled on the project.
- Confirm the right paver equipment is mapped.
- Check the tracker for a recent position fix on the paver.
- Confirm the paver is active in the tracker provider.
- Refresh the vehicle list in Settings → Integrations → Paver Tracker.
- If still missing, confirm the tracker credentials are valid.
- Confirm the tracker actually reports the field Tread is reading. Some trackers only report position, not tons.
- For projects without volume telemetry, capture tons through standard tickets instead.