INDUSTRY FIELD GUIDE
Transportation program service units and reporting data for AI
A transportation program can receive reports using different service units or operating modes.
NAICS 926120 · Regulation and Administration of Transportation Programs
A transportation program can receive reports using different service units or operating modes. FTA’s National Transit Database glossary defines measures such as vehicle revenue hours. An agency can create an original exercise that tests whether a model reconciles comparable reporting fields. FTA National Transit Database glossary
Make two fictional operators report service hours. Give one total vehicle hours and the other revenue hours, then add an amended export that supplies a matching basis. Ask which records can support a combined figure and cite the correct version. Score unit, mode and period.
Use fictitious routes and records or cleared published reports. Exclude private operator feeds, driver information, live location details and infrastructure vulnerabilities.
Describe a synthetic transport reporting sample
Original Fiund exercise
Combine revenue hours only after the amended export supplies the same basis
Two fictional transit operators report abstract vehicle-service hours for the same period and mode. There are no actual routes, drivers, vehicles or live locations.
| Record | Source | What it records |
|---|---|---|
| TPR1 | Operator A period P/mode M | Total vehicle hours 120, including 20 nonrevenue hours; definition supplied. |
| TPR2 | Operator B period P/mode M | Revenue vehicle hours 80; no total-hours figure supplied. |
| TPR3 | Authorized A amended export | Explicit revenue vehicle hours 100, same P/M; original total 120 retained as a different metric. |
Question for the model
Which common-basis combined figure is supported, and why should the original 120 and 80 not be added as a revenue-hours total?
Show the reference answer and checks
TPR3 and TPR2 supply compatible revenue vehicle hours of 100 and 80 for the same period and mode, supporting 180 combined revenue hours. TPR1's 120 includes nonrevenue time, so adding it directly to B's 80 would mix bases and overstate that metric. Preserve A's total-hours record separately, and do not infer B's total hours without its missing nonrevenue component.
- Combining total vehicle hours and revenue vehicle hours under one label.
- Overwriting the original total with the amended revenue field as if it corrected the same metric.
Fields to preserve
- Operator, mode and period
- Defines compatible reporting scope.
- Total versus revenue hour definition
- Prevents unlike units from being summed.
- Amended field and retained original
- Keeps different measures rather than inventing supersession.
Test another case
Change B's mode or period in a new export while keeping its 80 value. Require scope checks before repeating the 180 combined figure.
Use fictitious records and routes. Exclude private feeds, drivers, live positions and infrastructure vulnerabilities.
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.