INDUSTRY FIELD GUIDE
Independent trucking terminal queue data for AI review
A truck may enter the terminal more than once in a day.
NAICS 488490 · Other Support Activities for Road Transportation
A truck may enter the terminal more than once in a day. A queue status tied only to the truck cannot tell a dispatcher which visit is still active. Census places independent trucking terminal operations in road transportation support. DOT’s FLOW program illustrates why organizations benefit from well-defined freight events. Census NAICS manual · U.S. DOT FLOW program
Give one invented tractor two distinct visits with different appointment IDs. Record a queue entry, a door assignment, and a verified exit for the first. Give the second a later gate scan without a door assignment. Ask the model to reconstruct both histories and avoid applying the earlier exit to the later visit. Include a duplicate event at one scan point.
Remove facility layouts, access tokens, security procedures, and real vehicle or customer identifiers. Use fictitious terminal labels and get permission if a partner controls source records.
Describe a terminal queue benchmark
Original Fiund exercise
One tractor's earlier exit cannot close its later terminal visit
A fictional terminal log uses invalid tractor and appointment aliases. It contains no real facility layout, driver, customer, access token or live queue state.
| Record | Source | What it records |
|---|---|---|
| TQ1 | Visit A | Tractor DEMO-T, appointment A: queue entry 08:00, door assignment 08:10, verified exit 09:00. |
| TQ2 | Visit B | Same tractor, appointment B: new gate entry 11:00. Duplicate scan repeats identical event key B-IN; no door assignment or exit for B. |
| TQ3 | Summary draft | Draft joins by tractor only and calls B exited at 09:00. Original event references distinguish A and B. |
Question for the model
What stage is documented for each visit, and should the repeated B-IN scan create another visit?
Show the reference answer and checks
TQ1 documents A's queue, door assignment and exit. TQ2 documents B's later gate entry only; its repeated B-IN key is one event rather than another visit. TQ3 incorrectly carries A's earlier exit to B, creating an impossible sequence and ignoring appointment identity. Keep two visit histories under the same tractor alias and leave B's door and exit states unresolved without inferring an actual terminal condition.
- Joining all events by vehicle while ignoring visit or appointment.
- Counting an identical scan key twice or applying an earlier exit to a later arrival.
Fields to preserve
- Tractor and appointment/visit ID
- Defines the event scope.
- Queue, door and exit type
- Separates stages.
- Timestamp and unique scan key
- Supports ordering and deduplication.
Test another case
Add B's exit with no door event. Require exit to become documented while the missing door history remains explicit.
Use original synthetic events. Exclude security procedures, facilities and customer identifiers; partner-controlled records need authorization.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.