Campus mobility serves diverse populations with distinct access requirements: students, faculty, staff, visitors, and departmental operations. Universities need federation-level control with per-program autonomy, budget isolation, and centralized oversight—not separate systems for each mobility initiative.
Student services, facilities, and academic departments all run independent mobility programs requiring separate budgets and policies
Students vs. faculty vs. staff require different vehicle access, booking restrictions, and subscription eligibility
Each department needs transparent cost reporting without visibility into other programs' operations
Academic calendars create predictable usage spikes requiring fleet size adjustments without platform reconfiguration
A multi-tenant federation allows each department to operate as an independent entity with isolated fleets, clients, and budgets—centralized IT oversight, decentralized operations. Driver groups enforce access restrictions: student groups limited to weekday bookings and economy vehicles, faculty groups unrestricted access to all categories. Per-group subscription plans with configurable billing cycles align to semester schedules. Dashboard widgets provide department-level KPIs without cross-program data exposure. Fleet size adjusts via slot enable/disable—no platform reconfiguration for summer vs. fall semester capacity.
Federation model: independent departmental programs under university IT control
Driver groups: per-population booking policies and vehicle access restrictions
Subscription plans: semester-aligned billing cycles with auto-renewal
Configurable dashboards: department-level KPIs with data isolation
Slot management: seasonal fleet capacity adjustments without reconfiguration
