Track A Student & staff bus service
- Fixed routes, stops & timetables per campus
- Monthly seat allotment (a "pass") per rider on a route
- Live "where's my bus" page + arrival alerts
- Fares posted straight to the accounts
Institutional Fleet · University Transport · Autonemo VMS Pro
Running a university's fleet on VMS
Student & staff buses, official cars and vans, drivers, workshop and fuel — one back office.
How a university transport department can run its entire day-to-day operation on Autonemo VMS Pro. A campus runs two kinds of transport at once: scheduled bus routes bringing students and staff in every day, and an on-demand vehicle pool — cars, microbuses, vans and ambulances — that departments book. This is a grounded capability read: what fits out of the box, what needs a workaround, and the two investments worth planning for up front.
2Transport tracks · bus service + vehicle pool
13+Operational areas covered by existing modules
1Platform · per-campus scoping & roles
LiveFollow-the-bus page for students & parents
The shape of the problem
A university runs two kinds of transport.
VMS handles both from one back office. The key insight: there is no single "university" product — it is assembled from proven modules the transport office turns on and configures, then the commercial ones (ticketing storefronts, waste, rental) get switched off.
On one side, a daily bus service: fixed routes, stops and timetables per campus, a monthly seat allotment per rider (the "pass"), a live "where's my bus" page students and parents can open, and fares posted straight to accounts. On the other, an institutional vehicle pool: departments request a car or van, an approval chain signs off, a dispatch board assigns vehicle and driver, and the trip's cost is charged back to the department. Everything below sits on the same drivers, fuel, workshop, compliance and accounting spine.
Think of it as two tracks, one spine: daily scheduled buses for riders, and on-demand official vehicles for departments — sharing drivers, fuel, workshop, compliance and accounting underneath.
Two tracks
The bus service and the vehicle pool.
Track B Institutional vehicle pool
- Departments request a vehicle; multi-level approval
- Dispatch board assigns vehicle + driver with clash check
- Trip logs, odometer, GPS playback & per-trip cost
- Cost charged back to the department / cost centre
The fit matrix
University need → what runs it in VMS.
Every core need of a transport office, mapped to the module that handles it and how ready it is.
Ready out of the box
Works with a workaround
Plan around / add-on
| University need | Handled by (VMS module) | Fit |
|---|---|---|
| Daily bus routes, stops & seat allotment | Pick & Drop roster + Vehicle Routes (monthly seat, route, fare) | Ready |
| Per-trip / event / shuttle ticketing | Bus Ticketing — counter POS + online storefront + seat map | Ready |
| Live "where's my bus" for students / parents | Live Bus Tracking — public QR page, ETA, arrival board & alerts | Needs GPS unit |
| Department vehicle booking (car / van / ambulance) | Staff Transport Request + Requisition + Dispatch, multi-level approval | Ready |
| Drivers — licence, duty, discipline, mobile | Drivers + Fleet Workforce panel + Flutter driver app | Ready |
| Fuel tracking / own diesel pump | Fuel logs + Fuel Station / Pump module + reconciliation | Ready |
| Maintenance & workshop | Garage job cards, mechanics, vendor billing, service-due reminders | Ready |
| Document compliance (fitness / tax / insurance) | Vehicle document-expiry tracking + auto-reminders + dispatch block | Ready |
| Accidents & rider feedback / lost items | Accident register + Vehicle QR public report inbox | Ready |
| Cost per vehicle & per department | Double-entry accounting + cost-centre + profitability reports | Ready |
| Utilisation, idle & distance reporting | Reports Hub (utilisation, idle-vehicle, distance, executive summary) | Ready |
| Multi-campus operation | Branches — one branch per campus, a manager each | Ready |
| Access control per office / role | Staff roles + granular permissions + per-module on/off | Ready |
| Auto-renew pass & auto-invoice each month | Pick & Drop billing desk — monthly roster is manual | Partial |
| Forward budget vs actual | Actuals & profitability reporting only — no budgeting screen | Add-on |
What each area does
The operational toolkit.
A Bus routes & passes
- Routes, stops & timetables per campus
- Pick & Drop monthly roster — a fixed seat on a route for a date range
- Riders (or parents) request a seat online; waitlist handling
- Chargeable fares billed from the billing desk
B Live bus tracking
- Public QR page — scan the sticker on a bus to see it live
- Learned-time ETA + a stop-by-stop arrival board (TV mode)
- Arrival alerts to students / parents by SMS or browser
- Passenger traffic never calls the paid GPS API — reads our own data
C Vehicle pool & dispatch
- Staff / department self-service vehicle request
- Manager + transport-office multi-level approval
- Dispatch board assigns vehicle + driver with clash check
- Trip start / return, odometer, GPS playback, per-trip cost
D Drivers
- Records, licence & expiry, duty roster & attendance
- Driver mobile app — duty clock, trips, fuel, expenses, documents
- Advances, allowances, disciplinary log
- Live driver map for the control room
E Fuel & workshop
- Fuel logs per vehicle + efficiency / mileage trend
- Own diesel pump/tank: issue-to-fleet vs external, shift & dip readings
- Garage job cards, parts, mechanics, vendor bills
- Service-due reminders per vehicle
F Compliance, cost & reports
- Tax-token / fitness / insurance / route-permit expiry — auto-flagged, can block dispatch
- Double-entry accounting; cost charged to a department / cost centre
- Per-vehicle cost & profitability; utilisation & idle reports
- Executive daily summary + per-campus profit summary
Honest considerations
What to plan around.
VMS is a general fleet platform, not a purpose-built campus product — a few things need a decision or a small addition up front.
GPS
Live tracking needs a hardware GPS unit per bus.
The public "follow the bus" page reads position from an on-board GPS device, not the driver's phone. Budget for a tracker on each bus that should appear live.
Passes
Monthly passes are a roster, not an auto-billing subscription.
A seat-on-a-route for a month is fully modelled, but renewal & monthly invoicing are run from the billing desk each cycle — there is no auto-renew engine yet (a candidate add-on).
Budget
Reporting is actuals, not forward budgets.
You get rich cost, profitability & utilisation reporting, but no "budget vs actual" planning screen — track budgets alongside, or add it later.
Setup
It is assembled, then configured.
The transport office turns on the right modules — fleet, drivers, fuel, garage, pick-and-drop, tracking, reports — and turns off commercial ones. A guided setup, not install-and-go.
A sensible rollout
How to bring it live.
1
Set up campuses & people
One branch per campus with a transport manager; staff roles & permissions for each office.
2
Load vehicles, drivers & documents
Full registry with tax / fitness / insurance dates so compliance reminders start working day one.
3
Turn on the vehicle pool
Department requests, approval chain, dispatch board — the everyday car / van workflow.
4
Stand up the bus service
Routes, stops, timetables and Pick & Drop monthly rosters with fares.
5
Add fuel & workshop
Fuel logs / own pump and garage job cards with service-due reminders.
6
Fit GPS & go live for riders
Trackers on buses, QR stickers, the public follow-the-bus page & arrival alerts; then reports & dashboards for the office.
A university can run its whole transport operation on VMS today.
The vehicle pool, drivers, fuel, workshop, compliance, cost accounting, per-campus scoping and reporting are production-grade and ready. The student bus service runs on Pick & Drop plus live tracking — with two clear investments to plan for: a GPS unit on each bus, and (optionally) an auto-renew engine for monthly passes.
Related work
