Gate Operations

Keeping the lane moving, and having a record of what came in and what went out.

In the application

1. Open Dashboard for the gate project and set the period to the shift or day in question.
2. Scroll to recent scans, which lists each reading with its time, identifier, capture type and direction.
3. Open Assets and use Filter Exceptions to select records for inspection. Read the type and status together before deciding whether action is needed.

Both directions matter

Dwell analysis needs observations at both the entry and exit boundaries. One camera can support both directions when its placement and configuration capture them reliably. If you selected gate visibility in your profile, the Intelligence hub asks you to confirm whether ingate and outgate traffic each have active capture, and to add a camera where one side is missing.

This is worth settling early. Detention analysis, dwell measurement and dispute evidence all depend on having both boundaries.

Distinguish the gate's designated role from the observed movement. A dedicated inbound project or camera can classify that operational scope; a camera observing both directions requires the record's heading and stored direction mapping. Vertical or missing headings do not establish heading-derived entry or exit. Preserve any conflict between a lane designation and observed reverse movement.

Where projects form an authoritative pair, they must share a non-empty gate group and contain exactly one ingate and one outgate project in your accessible scope. Otherwise, define the stage projects or cameras explicitly. A generic name such as "North Gate" does not establish the role. For duration analysis, use one equipment family and confirm a maximum valid visit duration.

From an assistant

Using SiteTrax.io, break down today's detections at the gate by status code and asset type. State the timezone and resolved time window.

Using SiteTrax.io, what was the observed time between gate-in and gate-out for trailers this week?

Watch out for

• A status code describes a processing outcome. An unreadable identifier does not prove damage; a synthetic missing pair side does not represent another truck. Inspect the type, status and available evidence before drawing an operational conclusion.
• Peak hours are worth recording in your profile. The interview can save your busiest gate hours as customer-supplied context. Include the hours and timezone directly in an assistant question when the calculation depends on them; saved profile context is not guaranteed to be retrieved or applied.
• Identifier text can be a placeholder. Blank values and single-dash entries are not equipment identifiers.