Ridership, on-time performance, fare revenue, and fleet upkeep
Industry
Public transit
Company size
Mid-size metro transit authority, about 49 million annual boardings, roughly $300M annual operating budget
Operating scale represented
6 operating divisions, 80 bus and rail routes, 320 revenue vehicles, 600 operators and mechanics, 12 fare products, 349,326 daily route-service records, 698,652 daily fare-revenue records, 150,000 operator shifts, 24,000 maintenance records, and 40,000 service incidents
Planning note
Professional-tier BI kit focused on ridership, on-time performance, fare revenue, operator productivity, fleet upkeep, and service reliability
Corravia Transit Authority is a fictional mid-size metro public-transit agency built for BI teams that want a believable ridership, service-performance, fare, operator, and fleet dataset without exposing any real riders, operators, vehicles, or routes. The agency runs local and express buses, bus rapid transit, light rail, and a commuter rail line across several divisions. Everything in the kit is invented so analysts can model on-time performance, ridership by route and time of day, fare revenue by product, operator productivity, and fleet maintenance in one coherent transit story.
These are the operating questions this kit is optimized to answer first.
Follow daily route service by daypart into trips operated, on-time trips, and boardings to show on-time performance and ridership together.
Compare boardings and fare revenue across routes, modes, fare products, and rider classes.
Track operator shifts, service hours, trips operated, and on-time share by division and role.
Connect vehicle age and condition bands to maintenance cost, downtime, and replacement pressure on the oldest fleet.
Use service incidents to show how mechanical, operational, external, and weather causes drive delay minutes and severity by route and mode.