Fleet.
Explore vehicles and fleet operations.

Fleet models a single government's vehicle pool: Driver (a government employee assigned to drive), Vehicle , FuelConsumption and Maintenance — real government fleet vehicle models, real license-class regimes, real fuel-price calibration, per city.

It does not model commercial operators, multiple fleets, or trips. If that's what you're looking for, that's Transport → Nairobi's Operator/Route/Vehicle/Trip model — see the boundary below before you read further.

Nairobi City Twin™ · 1940–2026

Every public claim below is grounded in the certified Fleet release. Fleet is deliberately narrow: it represents government operational vehicles, drivers, maintenance and utilization without publishing the physical generation model.

A government workforce identity assigned as a fleet driver, with license and eligibility context represented longitudinally.

One row per government fleet vehicle — vehicle code, registration number, type, capacity and status. No owner concept: every row belongs to the same one fleet.

A refuelling event — vehicle, driver, litres, odometer reading, cost, fuel type. The largest table in the domain by far.

A scheduled and completed maintenance event per vehicle, drawn from a curated maintenance-component catalog.

A curated catalog of government-fleet vehicle profiles, duty contexts and maintenance categories appropriate to the city release.

Driver records use Kenya-appropriate license classes aligned to the public NTSA categories represented by the release, with class and expiry context attached to the synthetic driver.

Synthetic by design: every driver, vehicle, fuel event and maintenance record is a plausible, generated representation of a government fleet operation. None represents an actual government employee, an actual registered vehicle, or an actual expenditure.

If your mental model is "an operator runs a group of vehicles that make trips" — that's Transport , not Fleet. Fleet answers a narrower, different question: how does one government track and maintain the vehicles it already owns?

• Driver, Vehicle, FuelConsumption, Maintenance
• One institution, no Operator concept
• Individual trip histories are not included

• Operator, Route, Vehicle (Transport's own table), Trip
• Many real operators — SACCOs and other commercial operators
• 22 certification checks, Nairobi

• PrivateVehicle
• Citizen / Business / ForeignNational / Institution owner
• No operational activity modeled

Representative public fields: driver/licensing context, vehicle identity and class, fuel events, odometer context and maintenance timing. The full physical field dictionary is not published.

No live record is shown here. This public catalog does not publish live identifiers, driver assignments or fuel amounts. Licensed release access provides current queryable data.

Explore the City Twin →

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

A representative public record shape — illustrative rather than a captured live-row identity.

This is the real chain Fleet actually models: Employee → Driver → Vehicle → Fuel / Maintenance. There is no "Fleet" node in this chain, because there's only ever the one fleet — the government's own — and no "Trip" node, because vehicle movement itself isn't tracked here, only its fuel and maintenance consequences.

The Nairobi release runs the shared generation model against the same shared vehicle and maintenance catalogs. What differs is each country's real driver-licensing taxonomy and each country's real fuel price level.

A single shared catalog now serves Nairobi consistently, replacing two different earlier approaches that didn't match each other.

Fleet's own audit registration names it "Government Vehicle Fleet" — there is exactly one institution, no Operator entity, and no concept of a business running its own fleet. Commercial, logistics and corporate vehicle operations are not modeled anywhere in this engine under the name "Fleet." Real multi-operator commercial vehicle activity — SACCOs and other commercial operators — is modeled separately, under Transport Nairobi's Operator/Route/Vehicle/Trip tables.

Fleet tracks that a vehicle was refuelled and maintained, not where or why it travelled. A trip, route, or utilization concept for government fleet vehicles does not exist in this domain — the closest available proxy is fuel-consumption frequency, not a real trip log.

The field stays NULL in Nairobi today, a genuine cross-domain gap tracked separately, not fixed by this page.

Nairobi has an Asset registry that can resolve the guarded asset reference relationship, but Fleet generation does not require every government vehicle to be linked to a mapped asset. asset reference is therefore optional enrichment, not a guaranteed spatial record for every vehicle.

Driver and fuel-consumption records were unavailable in both City Twins on 2026-08-07, although vehicle and maintenance records were present. Updated driver and fuel coverage is pending.

Fleet records discrete fuel and maintenance events after the fact. It does not model live GPS position, dynamic dispatch, route optimization, or any real-time operational state for a vehicle.

License expiry is automatically kept consistent with the underlying citizen's birth and death dates, but no realism check yet measures whether the license-class mix or expiry-renewal pattern resembles real driver-licensing behavior.

View All Fleet Limitations →

Earlier Fleet findings were resolved in the reviewed Nairobi data. Current driver and fuel coverage is reported separately from those dated results.

Structural certification runs 11 separate checks — catalog population, relationship integrity, value-range consistency, temporal ordering and historical-context consistency. Revalidated live 2026-08-06: 7 PASS, 0 FAIL, 4 N/A Nairobi (the 4 N/A are checks that depend on driver/fuel-consumption data — see above). A supporting license-class catalogue gap was corrected during revalidation and is now populated again.

Unlike newer catalog pages in this documentation, Fleet has a real certification battery, a real realism battery, and a real release history documenting the issues found while building both — including a data gap where an entire domain marked "graduated" turned out to have never actually generated its driver or fuel-consumption records on Nairobi until 2026-07-26/27, and a second data gap (disclosed above) where that same data is empty again as of 2026-08-06.

Lesson from Fleet's release history: a domain marked "graduated" in prior documentation can still have generation steps that were never actually executed against live data — graduation certifies the design, not that every downstream table has been populated, and (per this pass) not that it stays populated across every future deploy.

The 2026-07-27 odometer-monotonicity fix is still correct in the underlying model — see the original 0-of-74,499/0-of-72,001 verification → — but there is currently no live fuel-consumption data on Nairobi to re-verify it against.

A real fleet Vehicle row — one of 500 published on Nairobi.

A real, completed Maintenance record on this vehicle, scheduled 2026-03-18, cost KES 110,490.00 — one of 2,250 real maintenance rows.

confirmed in the published source: Driver and FuelConsumption both have 0 rows. Vehicle and Maintenance are real; driver assignment and fuel tracking are designed but not yet generated.

What a commercial operator's vehicle does day-to-day — the trips, the routes, the fares — is told on Transport → , not here.

Employee → Driver → Vehicle → Fuel & Maintenance — one government's own vehicle operation, honestly scoped.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™