Yard Operations
Understanding what is on the ground and what has been sitting, so a supervisor can direct work instead of surveying it.
In the application
- Open Dashboard, set the project and period, and read the asset and scan totals for the shape of the day.
- Open Assets to see individual readings, most recent first.
- Compare arrivals against departures over the same window to understand what has accumulated.
From an assistant
Using SiteTrax.io, summarize activity at my sites for the last seven days and break it down by asset type and direction.
Using SiteTrax.io, were there any unusual volume gaps at my sites this week?
Coverage is the limiting factor
Yard visibility is only as complete as the capture behind it. The Intelligence hub states this directly: if you chose yard visibility in your profile, it will tell you that which working zones are covered is not yet confirmed, and prompt you to map what is already visible and close only the gaps that remain.
Do that exercise before treating a yard count as complete. A zone with no camera contributes nothing to the record, and no amount of analysis recovers it.
Watch out for
- Absence of a reading is not absence of a unit. It is absence of an observation.
- Dwell needs boundaries. Time on the yard can be measured where entry and exit observations pair reliably. Where they do not, SiteTrax.io reports the limitation rather than estimating.
- Combined processing adds rows. Where container and chassis are processed together, a synthetic row can be stored for the paired side.