INDUSTRY FIELD GUIDE
Shuttle transfer and vehicle assignment records for AI
A shuttle can change vehicles without changing the public run number.
NAICS 485999 · All Other Transit and Ground Passenger Transportation
A shuttle can change vehicles without changing the public run number. A status report needs to distinguish the planned assignment from the vehicle that actually arrived. Census lists shuttle and vanpool operators in this industry, and FTA’s glossary provides transit reporting terminology. Census NAICS manual · FTA National Transit Database glossary
Prepare two fictional shuttle runs with the same name on different dates. Add a corrected vehicle assignment, an observed transfer, and a proposed alternative that was never dispatched. Ask the model which evidence applies to each run and whether the transfer can be confirmed. In a vanpool version, record an operator-confirmed replacement rather than individual trip details.
Protect hotel guest, employer and rider records, private stop locations, and real vehicle and staff assignments. Use scenario aliases and keep official service decisions outside the test.
Describe a shuttle handoff dataset
Original Fiund exercise
A vehicle substitution stays within its dated shuttle run
Two invented shuttle runs share a display name but use abstract dates and vehicles. There are no guests, employees, riders, private stops or actual assignments.
| Record | Source | What it records |
|---|---|---|
| SHU1 | Run map | Run NAME on D1 initially assigned vehicle V1; same NAME on D2 assigned V3. Distinct full run IDs R1 and R2. |
| SHU2 | R1 substitution | Reviewed correction changes D1/R1 from V1 to V2. Original observed transfer event explicitly confirms R1/V2 arrival and handoff. |
| SHU3 | Unactivated alternative | Proposal would replace R2/V3 with V4, never dispatched or confirmed. No D2 transfer observation supplied. |
Question for the model
Which vehicle and handoff are supported for each dated run, and does the proposal or repeated name extend R1's evidence to D2?
Show the reference answer and checks
SHU2 supports D1/R1's corrected V2 assignment and observed handoff. SHU1 retains D2/R2's V3 planned assignment, while SHU3's V4 remains an unactivated proposal with no observed transfer. The repeated display name does not transfer D1's confirmation to D2. Report planned assignment, correction and observed event separately rather than claim a future run occurred or an alternate vehicle was dispatched.
- Joining runs by display name while ignoring the service date.
- Treating a proposed replacement as dispatched or a corrected assignment as observed arrival without its event.
Fields to preserve
- Full run ID and date
- Defines the instance.
- Planned/corrected vehicle
- Preserves assignment history.
- Observed transfer and proposal state
- Supports the handoff.
Test another case
Add a D2 V4 arrival observation but no approved substitution. Require the actual observation and unresolved assignment conflict both to remain visible.
Use original aliases and records. Exclude private stops and actual vehicle or staff data; official service decisions stay outside the test.
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.