Deployment scenarios
Every educational institution has its own transportation policies, routes, fleet size and operational requirements, so a solution is scoped rather than selected from a list. These are worked examples of that scoping for four common shapes of institution.
Illustrative configuration
Single campus · small fleet · parent visibility the priority
The most common starting point. The institution wants live bus tracking, parent visibility and an end to telephone enquiries, with student-level tracking added once the basics are running.
Illustrative configuration
Single campus · GPS plus RFID · student safety the priority
An institution that wants to know not only where the bus is but which students are on it, with boarding and drop-off recorded rather than remembered.
Illustrative configuration
Safety-led · full integration · optional components included
An institution building the fullest configuration the platform supports, combining tracking and student identification with surveillance, emergency alerting and voice.
Illustrative configuration
Multi-campus · larger fleet · utilisation and reporting the priority
A larger transportation operation where the questions are as much about service utilisation and reporting as about individual journeys.
These are illustrative configurations showing how the solution components are assembled, not descriptions of specific customers. They make no claim about outcomes achieved at any institution.
Customer case studies are published here once an institution has approved being named. Until then, these worked examples show how the documented solution components are assembled for institutions of different shapes.
Bring your fleet size, routes and reporting requirements to a requirement analysis and we will scope a solution against them.
We use a small number of cookies
Strictly necessary cookies keep your theme choice and sign-in working. Analytics cookies tell us which pages are read, in aggregate. No advertising, no cross-site tracking. Read the cookie policy.
