Bus Safety
Know the moment your child boards - and where they get off
AI at the bus door records every boarding and drop, parents get an alert in seconds, and the system warns about missed buses, wrong stops and any child still on board when the trip ends.
- Works offline
- 10 parent alert events
- Live map only during trips
Thursday, 8 October
08:06
- EduPresence07:18
Bus R-12 has left the depot
Track live in the app.
- EduPresence07:37
Bus approaching
Bus R-12 will reach Sector 21 stop in ~5 minutes.
- EduPresence07:42
Boarded
Aarav boarded bus R-12 at 07:42 at Sector 21 stop.
- EduPresence08:05
Reached school
Aarav reached school at 08:05.
The goal
GPS shows where the bus is. We show who is on it.
Parents must know when their child boards, where and when the child gets off, and must be warned when something is wrong.
Boarding confirmed
A BOARD event with time, stop and location for every child, matched against the route roster.
Drop verified
ALIGHT near the assigned stop is confirmed; anywhere else triggers a wrong-stop alert.
Nobody left behind
At trip end, anyone boarded but not alighted triggers a loud on-bus alarm and an urgent alert.
Challenges on a moving bus
Designed for weak 4G, vibration, glare and power cuts
A bus is a hostile place for computers. Every challenge has a specific design answer.
Intermittent 4G (tunnels, rural roads)
All AI runs on the bus. Events are stored on the device and sent when the network returns - never lost.
No GPU, limited power (12 / 24 V)
Low-power device; AI active only when the door opens or motion is detected.
Vibration, heat, dust
Rugged, fanless device, IP-rated camera, wide temperature range and proper mounting.
Changing light (sun through windows, night)
WDR + IR camera facing the steps (not the windscreen); IR LEDs for early mornings.
Kids crowding / small children
Camera at child face height on the step rail; several frames per track; RFID card tap as backup.
Power cuts when ignition is off
Small backup power for a safe shutdown; data is protected and the trip resumes on boot.
Clock drift
GPS time as the reference; events stamped with both device time and GPS time.
Hardware options
Three ways to equip a bus
Start with option A on most fleets; move to B where you need better cameras or cabin recording; use C if your buses already carry an AI-capable MDVR.
Tablet kiosk
Rugged 8-10" tablet with 4G + GPS built in, fixed mount at the door, optional external camera and NFC reader
Pros
- Cheapest
- One device does camera + GPS + 4G + screen + battery
- Attendant UI on the same screen
Cons
- Built-in front camera angle is limited
- Consumer tablets overheat in summer - choose rugged
In-bus AI unit
Compact in-bus AI unit with IP camera(s), 4G router with GPS and a small attendant screen
Pros
- Better cameras
- Can add cabin CCTV / recording
- Same software as the campus device
Cons
- More parts
- Installation and power design needed
Integrate existing MDVR
Commercial bus MDVR with AI features, integrated with EduPresence
Pros
- Reuse existing hardware
Cons
- Vendor lock-in
- Capabilities vary by vendor
On-bus flow
From ignition to the last drop
Matching against the route roster (30-60 students) is extremely fast and more accurate than whole-school matching.
Step 1
Boot
Loads today's route and roster from cache (refreshed whenever online). Resumes an open trip after a power cut.
Step 2
Start trip
Attendant taps START TRIP, or the trip auto-starts on geofence exit from the school or depot.
Step 3
GPS every 5-10 s
Points are batched into the outbox and drive the live map for parents and admins.
Step 4
Door opens / motion
Camera wakes: detect -> track -> liveness -> embed -> match against the ROUTE ROSTER first.
Step 5
BOARD or ALIGHT
Direction of movement across a virtual line + trip context. 2+ agreeing frames create the event with time, lat/long and nearest stop.
Step 6
Attendant confirms
Screen shows name, photo and a green tick. Unknown / low confidence beeps: pick the child from the list or tap the RFID card.
Step 7
Synced to cloud
Event saved on the bus device and sent securely - kept until the cloud confirms receipt.
Step 8
Parent notified
'Aarav boarded bus R-12 at 07:42 at Sector 21 stop.' - push plus WhatsApp / SMS.
Step 9
End trip check
Anyone BOARDED but not ALIGHTED? Loud local alarm on the bus and an urgent alert to the cloud.
Parent notification events
Ten events, each with the right urgency
Routine updates go by push; safety-critical alerts escalate to SMS, WhatsApp and phone calls to the transport desk.
Thursday, 8 October
14:53
- EduPresence14:10
Boarded school bus
Aarav boarded bus R-12 for home at 14:10.
- EduPresence14:46
Bus approaching
Bus R-12 will reach Sector 21 stop in ~5 minutes.
- EduPresence14:52
Dropped
Aarav got off at Sector 21 stop at 14:52.
Afternoon return trip as the parent sees it
Notification pipeline
Each boarding or drop is matched to the right guardians, written in the parent's language and sent by app notification, WhatsApp or SMS - with delivery tracking and automatic retries.
De-duplicated
One BOARD notification per child per trip - even if the device re-sends events after a network drop.
Fast
Board / drop alerts reach parents in under 30-60 seconds when online, and 100% are eventually delivered after offline sync.
Offline-safe sync
Events are never lost - only delayed
The bus device is offline-first. The cloud is used for notifications and the live map, never as a dependency for recognition.
- Every event is saved on the bus device first, before anything else
- Events are sent securely and kept until the cloud confirms receipt
- Re-sent events are recognised, so nothing is ever counted twice
- Parents always see the real event time ('Boarded at 07:42'), even if it synced later
- If 4G is down for long, the device sends critical alerts (child left on bus) by SMS from its own SIM
Recognition never depends on the network. The cloud is only used to notify parents and update the live map.
Integration with school attendance
Bus, gate and classroom tell one story
Bus events feed the same attendance record as the gate and classroom cameras - and catch gaps between them.
Bus to classroom
BUS ALIGHT at school + GATE IN confirm ‘present’. If a child boarded but has no gate or classroom detection within 15 minutes, the class teacher is alerted - a possible missing child on campus.
Gate to bus
GATE OUT + BUS BOARD. Children who neither board their mapped bus nor are picked up by an authorised guardian are flagged before the bus leaves.
Leave-aware
Approved leave suppresses ‘missed bus’ alerts, so parents who already told the school aren't alarmed.
Privacy on the bus
Tracking that respects children
Built for India's DPDP Act: purpose-limited, consent-based and minimal.
Own child only
The parent live map shows only their child's bus, and only during trip windows.
No video upload
Recognition runs on the bus device; only small events and GPS points are sent.
Consent first
Children without biometric consent use RFID or the attendant list - same alerts, no face data.
FAQ
Bus safety questions
Works better together
Explore related modules
Attendance, leave, transport and alerts share one data model - so an approved leave quietly suppresses the absent and missed-bus alerts.
Put one bus on EduPresence this month
Start with a single route: we install the kit, map the stops and roster, and your parents start getting board and drop alerts the same week.
- Free campus survey
- Live in days without hardware
- Hosted in India