INDUSTRY FIELD GUIDE
Inland barge lock-event data for AI evaluation
A tow can arrive in a queue without starting passage.
NAICS 483211 · Inland Water Freight Transportation
A tow can arrive in a queue without starting passage. The U.S. Army Corps of Engineers collects lock data and has described an AI-camera trial for lock operations. A barge operator can propose a separate simulated benchmark for matching events that occur at different stages. USACE lock data program · USACE lock AI-camera trial
Create two fictional tow arrivals and one verified passage. Give the tows similar names and different training identifiers. Add an intermediate status update that is compatible with waiting. Ask the model which event marks a completed passage and what is unknown about the other tow. Label planned, observed, and operator-confirmed times independently.
Use no actual lock schedules, operational systems, shipper accounts, or exact infrastructure coordinates. An authorized photograph or schematic can be used when it helps explain the mock records. The task stays offline.
Describe an inland freight event sample
Original Fiund exercise
Queue arrival and waiting updates do not establish completed passage
Two invented tow aliases and abstract lock events form an offline fixture. No schedule, shipper, operating system, infrastructure coordinate or navigation instruction is included.
| Record | Source | What it records |
|---|---|---|
| IL1 | Tow A | Full ID DEMO-A, arrival observed 08:00. Operator-confirmed passage complete 08:40, exact A event reference. |
| IL2 | Tow A2 | Distinct full ID DEMO-A2, arrival observed 08:20. Planned passage 09:00; update at 08:50 says waiting. |
| IL3 | Similar-name summary | A and A2 share a short display name in the original mock interface. No completion for A2 or approved identity merge supplied. |
Question for the model
Which tow has a completed-passage record, and what can be stated about A2's plan and last observation?
Show the reference answer and checks
IL1 explicitly confirms A's passage completed at 08:40. IL2 supports A2's observed arrival and latest waiting update; its 09:00 planned passage is not execution evidence. IL3's shared short name does not transfer A's completion to A2. Report planned, observed and confirmed times distinctly, leaving A2's completed passage unresolved even after the planned time would have passed. The fixture makes no navigation or operational decision.
- Treating a planned passage time as a completed event.
- Matching similar tow names instead of the full training identifier.
Fields to preserve
- Tow ID and display-name scope
- Disambiguates records.
- Arrival, waiting and passage event
- Separates stages.
- Planned versus confirmed timestamp
- Supports the state summary.
Test another case
Supply A2's passage-start event without completion. Require a state advance without calling passage complete.
Use synthetic logs and original schematics. Exclude actual schedules and infrastructure details; all evaluation stays offline.
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.