{
  "title": "Transportation program service units and reporting data for AI",
  "source_page": "https://fiund.com/industries/transportation-program-service-unit-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Combine revenue hours only after the amended export supplies the same basis",
    "context": "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.",
    "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": "Which common-basis combined figure is supported, and why should the original 120 and 80 not be added as a revenue-hours total?",
    "answer": "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.",
    "failureModes": [
      "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": [
      [
        "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."
      ]
    ],
    "holdout": "Change B's mode or period in a new export while keeping its 80 value. Require scope checks before repeating the 180 combined figure.",
    "boundary": "Use fictitious records and routes. Exclude private feeds, drivers, live positions and infrastructure vulnerabilities."
  }
}