Displays, announcements, video and the panic button — driven from the same feed as the control room.
Passenger information, voice announcement, video management, video analytics and emergency response, configured per route and per vehicle from the platform rather than device by device.
Five things on the vehicle, configured from one place.
Passenger information & destination boards
Front, rear, side and in-cabin boards: a route and destination library, automatic switching by GPS position, multi-language rendering, next-stop and scrolling messages, with content pushed and scheduled remotely.
Automatic voice announcement
GPS-triggered stop announcements, multi-language text-to-speech, driver PA override, emergency broadcast and scheduled audio slots.
Video management (MDVR)
Live view, timeline playback, event-triggered clip retrieval, per-channel health, edge-versus-cloud retention policy, and evidence export with a chain-of-custody log. Two to eight channels.
Video AI
Automatic passenger counting — boarding, alighting and occupancy — ADAS for forward collision and lane departure, driver monitoring for drowsiness, distraction and phone use, and door-zone safety detection.
SOS and emergency response
Alert routing to the control room and to 112 / ERSS, automatic camera snapshot and audio capture on trigger, a defined escalation ladder, and an acknowledgement and closure audit trail.
It works with the devices already fitted.
The same position as the rest of the vehicle layer: the platform sits above the hardware, so the hardware is a procurement decision rather than a lock-in.
Existing displays and cameras
Boards, recorders and cameras already on the fleet are driven where their interface is documented, or mapped at onboarding where the vendor supplies the specification.
Configured centrally
Route content, announcement libraries, retention policy and event classes are set on the platform and applied per vehicle — not walked around the depot on a laptop.
Device partnerships
Where a deployment specifies new hardware, we work with device partners including MikroElektronika. The rest of that picture is on Integrations.
What we validate rather than claim.
The rest of the vehicle layer.
OBU to Cloud
How every event on this page reaches the platform, and what happens to it once it does.
OBU Software Stack
The local application services that render the boards and play the announcements without a network.
ADAS Configuration
Thresholds, calibration and deployment for the driver-assistance and driver-monitoring functions.
Intelligence
Where the computer-vision models sit, whose they are, and what we will and will not claim for them.
Integrations
The standards and devices RouteSync speaks to, including the Indian statutory set.
See it driven from the control room, not the device.
The point of this layer is that the board, the announcement and the camera event all come from the same feed. It is easier to judge on a route you know.