Asset Tracking

Following a single piece of equipment across time and sites using the observations SiteTrax.io has captured.

What tracking means here

SiteTrax.io is an observation-based record, not a telematics feed. It tells you where and when a unit was seen by capture you control. Between observations there is no position, and that is a property of the method rather than a gap to be filled in.

These observations help answer when a unit was seen at an entry or exit and where it was last observed. Whether it is still present requires adequate entry/exit coverage and reliable pairing; the latest observation alone does not establish current presence.

In the application

Open Assets and search the complete identifier.
Widen the date range until the history you need is covered.
Read the sequence of records: check the recorded time and project, then the available heading, direction interpretation and media. A direction or image may be unavailable.

Supported identifiers

Depending on your configuration, SiteTrax.io can read intermodal container IDs, chassis IDs, trailer IDs, USDOT numbers, and license plate information where the configured solution supports it, along with other configured outputs.

From an assistant

Using SiteTrax.io, give me the observation history for chassis identifier ABCZ123456 across all my sites this quarter.

Ask for the detection links and the applied project, date and equipment-type filters. Histories are paginated, so check whether more records remain when you need a complete listing. Use server-side sequence analysis for visit durations instead of treating the first and last displayed rows as a visit.

Watch out for

Search first, then confirm the complete identifier. MCP query search supports partial text and prefixes to find candidate identifiers. Confirm the full identifier before following one unit or requesting an exact latest-observation or identifier-based image/video lookup.
A USDOT number identifies a carrier, not a specific tractor, so it will not behave like a unique asset ID.
Two records can describe one pass. Vertical and horizontal reads of the same unit, or paired container and chassis processing, can both produce more than one row.
Cross-site history needs shared projects. Sites not shared with your account will not appear.