Expected
Identify the route, stop, vehicle, schedule and responsible team.
Connected Campus · Transport operations
A moving dot cannot answer a worried parent.
A late bus needs more than a position on a map. Your team needs a reason, a responsible person and a clear next update. Connect route context to the people who own that response.
Your separately ordered BCO transport integration brings the selected vehicle-location (GPS) or staff status updates, delay review, backup responsibility and approved communication into one operating plan—configured, tested and accepted before your agreed launch.
- Bring
- One route and the questions families ask when it runs late.
- Check
- Location updates, staff confirmation and approved family communication.
- Agree
- Provider connections, response ownership and tests before launch.
Your commissioned workflow
From a route update to a responsible staff response.
Give the team a shared sequence: what was expected, what happened, who is checking and what was communicated.
Observed
Receive the agreed vehicle-location updates or an authorised staff status update.
Exception
Distinguish a vehicle delay or route change from missing or out-of-date location data.
Response
Assign an owner, capture the reason and prepare the next update.
Closure
Record the outcome and any delivery confirmation available from the selected messaging channel.
The moments that matter
A missing signal should not become a missing response.
Problem
Location updates stop during the trip.
A blank map may mean a power, network or device failure—not a confirmed vehicle incident.
Your commissioned BCO response
Check whether location updates have stopped separately from whether the bus is delayed. Assign a staff member to confirm the vehicle’s position through an agreed backup method.
Problem
A delay alert creates more questions.
Families receive a warning without a reason, a next update time or someone to contact.
Your commissioned BCO response
After a staff member checks the situation, approve an update explaining what happened, who should receive it and the next step.
Problem
No one closes the loop.
The vehicle arrives, but the unresolved status leaves another shift unsure what happened.
Your commissioned BCO response
Record how the trip ended, who handled the issue and which messages were sent, using the agreed completion process.
Acceptance before launch
Rehearse the response—not only the map.
The checks agreed for acceptance cover routine trips and difficult moments: out-of-date location updates, delayed vehicles, unavailable contacts and the next message.
- Location updatesDistinguish missing or out-of-date data from an actual vehicle delay.
- Delay ownershipName who checks a delay or uncertain update and decides what happens next.
- EscalationAgree who takes over when the first contact cannot respond.
- CommunicationCheck approved message content and what the selected channel can report about delivery.
- ClosureKeep the result for the next shift and for management review.
Commissioned for your routes
One agreed operating plan, from provider to response.
Transport integration is commissioned separately from the base ERP subscription. Your proposal names the vehicle-location or staff update sources, supplier connections, messaging channels and included processes, with delivery stages and acceptance before the agreed launch.
Your response model
- Routes, stops, vehicles, schedules and responsible teams.
- Rules for delays, missing location updates and who takes over if needed.
- Who may receive updates, which messages are approved and how completed trips or issues are recorded.
- Staff handover and the checks agreed for acceptance.
Your delivery scope
- Named vehicle-location devices or staff update sources, with agreed supplier connections.
- How often location is updated, which route functions are included and how long data is kept.
- Installation, connectivity, warranty and support roles.
- Messaging permissions, available delivery reports, usage costs and launch dates.
Route alerts support institutional response; they do not replace driver, attendant or emergency responsibilities. Read the Connected Campus buyer questions.
Continue the Smart Campus story