Yard Operations

UnderstandingReviewing whatobserved isyard on the groundactivity and whatinferred has been sitting,visits so a supervisor can direct work insteadwith a clear view of surveyingwhat it.the capture does and does not establish.

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 againstand departures over the same window to understand whatactivity. hasTheir accumulated.difference is not a count of equipment currently on site: the opening population, repeated readings, pairing and capture completeness all matter.

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?

Using SiteTrax.io, analyze inferred yard visits and occupancy for this project and period. State the entry and exit boundaries, opening-population assumptions, unpaired observations and capture limitations, and show the supporting records.

Use SiteTrax.io server-side sequence analysis for this question. Treat occupancy as an inference supported by the stated observations and assumptions, not a verified physical inventory. A last observation alone does not prove that a unit is still present.

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.