Passenger Mobility & Transit
Routes, schedules, trips, fares, public transport
Bundle → Layer → Finding → Questions Incomplete
4 bundles · 8 layers · 0 findings · 0 questions
network The fixed structure of transit
stopsAndStations
stop places, platforms and interchange facilities
routesAndLines
ordered sequences of stops served by lines
service What is planned and what runs
timetables
published scheduled services and calendars
realtimeOperations
actual vehicle journeys, positions, delays and cancellations
journey How people use the system
tripsAndLegs
passenger trips composed of legs on services
ridershipAggregates
anonymized usage volumes per route, stop and period
fare Pricing access
fareProducts
tickets, passes and their validity rules
tariffZonesAndRules
zonal structures and transfer rules
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- standalone-mm
- Navigation path
- NAV.PHY.FLW.MOB
- Domain
- PHY.FLW.MOB
- Industry
- Cross-industry
- Tags
- passengermobilityphy.flw.mob
- Also called
- F7
What it is Derived, awaiting review
This meta-model describes how people move through shared transport: networks of stops and routes, published timetables, the vehicle journeys that actually run, the trips passengers take across them, and the fare products and zones that price access.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Routes, schedules, trips, fares, public transport
Distinguishing features Derived, awaiting review
- It is its own model because passenger service semantics (headways, punctuality, accessibility, fares, privacy of individual movement) are distinct from goods logistics, even where the two share corridors and terminals.
What robots and AI may and may not do Derived, awaiting review
Must not
- ridershipStatisticsAccess: planners receive anonymized ridership aggregates, never individual trips.
Moral aspects Derived, awaiting review
- It is its own model because passenger service semantics (headways, punctuality, accessibility, fares, privacy of individual movement) are distinct from goods logistics, even where the two share corridors and terminals.
Owners Filled
Steward
Transit operators steward network, schedule, operations and fare records for their own services; ridership aggregates are stewarded by the operator or a statistics office archetype.
Links to other meta-models Filled
composes
- world.money - fare prices embed the money value object.
references
- world.person - a trip may be linked to a passenger identity only under an explicit contract; the default recording is anonymous.
- world.emission - service activity recorded here provides activity data for transit emission estimates.
- world.goodsMovement - passenger and freight services share corridors, terminals and multimodal interchange.
imports
- GTFS - ALIGN: field equivalences for timetable and network publication.
- Transmodel - ALIGN: conceptual public transport reference semantics.
- NeTEx - ALIGN: network, timetable and fare exchange structure equivalences.
requires
- vr.wm-eco-014
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- timetablePublished: a new schedule version for a route or network became effective.
- serviceDeparted: a vehicle journey began at its origin stop.
- serviceArrived: a vehicle journey completed at its destination stop.
- serviceCancelled: a planned service did not run.
- disruptionDeclared: a network or route level disturbance was announced with its scope.
- fareValidated: a fare product was used to access a service (recorded without personal linkage by default).
- tripCompleted: a passenger trip closed, contributing to ridership aggregates.
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- openTimetableFeed: public access to network, stop and schedule data.
- realtimeOperationsFeed: subscribed consumers receive positions, delays and disruptions.
- ridershipStatisticsAccess: planners receive anonymized ridership aggregates, never individual trips.
- journeyPlannerView: stops, routes, timetables and realtime status merged for trip planning; omits ridership and fare revenue data.
- operatorPerformanceView: an operator's own punctuality, cancellations and occupancy; omits other operators.
- cityRidershipAggregate: usage volumes per corridor and period for planning; omits all personal and vehicle-level detail.
Context of use required Filled
- Trip records belong to the passenger where personal linkage exists, and all access is granted by the respective steward through the catalogue's S1/S2 ownership and access models, with audit via S4.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-f7-passenger-mobility-and-transit/spec.yaml, models/docs/flows-resources/F7-passenger-mobility-and-transit.md