INDUSTRY FIELD GUIDE
Railroad interchange records for AI custody checks
A railcar can appear in both the sending and receiving system before a confirmed interchange.
NAICS 482111 · Line-Haul Railroads
NAICS 482112 · Short Line Railroads
A railcar can appear in both the sending and receiving system before a confirmed interchange. A useful dataset shows which record expresses intent and which proves custody changed. Public freight data initiatives describe the value of joining records across organizations. A carrier can build a narrow, simulated interchange case before offering its own operational data. U.S. DOT freight visibility data overview · Scale AI Data Partnerships
Use two invented car IDs and a transfer list. Record a planned interchange, a verified receiving event, and a later correction from the sending carrier. Add a similar car on a different track in the exercise. Ask the assistant which train or operator can be linked to each car at a given time and which record closes the handoff. Include the roles and evidence source as structured fields.
Remove real car numbers, railroad customer records, sensitive route information, waybill terms, and yard layouts. Check both operators’ permission for real interchange files.
Describe a railroad custody sample
Original Fiund exercise
A transfer list expresses intent until an exact receiving event confirms custody
Two invalid training car aliases and fictional operator roles form a custody exercise. There is no actual railroad, track layout, waybill, customer or route.
| Record | Source | What it records |
|---|---|---|
| RIC1 | Planned interchange | Sending operator A lists cars DEMO-C1 and DEMO-C2 for receiving operator B at practice time T. |
| RIC2 | Verified receipt | B explicitly acknowledges DEMO-C1 at T1. Later sender correction changes C1's administrative description, not identity or receiving role. |
| RIC3 | Second car evidence | C2 has planned transfer only. Similar car C2X has a B receipt in another exercise; no C2 receipt or equivalence record. |
Question for the model
Which car has a confirmed custody change, and do the sender correction or near-match close C2's handoff?
Show the reference answer and checks
RIC2 explicitly confirms B's receipt of DEMO-C1, closing that fictional handoff from RIC1's plan. Its description correction preserves the same car and does not create another custody event. RIC3 leaves C2's receiving evidence absent; C2X belongs to another identity and exercise. Report C1's confirmed change and C2's planned-only state rather than treat presence in both systems or a transfer list as proof of completed interchange.
- Treating a planned transfer list as a receiving acknowledgment.
- Using another car's near-match receipt or counting a description correction as a second handoff.
Fields to preserve
- Car and sending/receiving role
- Defines the custody scope.
- Planned versus received event
- Separates stages.
- Correction target and unmatched receipt
- Preserves identity.
Test another case
Add a C2 receipt from operator C rather than B. Require the documented recipient to be reported and the intended-B mismatch flagged.
Use original fictional events. Exclude real car numbers, customers and yard details; both operators' rights govern real interchange data.
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.