Transit Departure Boards

Departure boards people can trust

A departure board has one job: be right, and be on. Passengers plan around it, staff get blamed when it's wrong, and a black screen above a platform erodes trust in the whole system. Yet many transit displays still run on unmanaged players nobody can see into — discovered down only when a passenger complains.

TelemetryOS runs departure boards as managed applications. A board app built with the React SDK reads live data from your AVL system or GTFS-realtime feed — TelemetryOS enables applications to connect to any REST API — and renders departures, delays, and platform changes the moment the data moves. The same screens carry service alerts and safety messaging, scheduled by station or taken over immediately when something urgent happens.

Resilience is built in at the device. TelemetryOS devices cache content and execute applications locally, so an overhead bank of departures stays live even if a screen drops the network; it keeps playing from the device and resyncs when the connection returns. No black screens mid-rush because a switch rebooted.

Monitored like the infrastructure it is

Departure boards are infrastructure, and infrastructure needs monitoring. The TelemetryOS console gives operations teams one view of every device across every station: health, playback status, app version, and proof-of-play. A screen that fails at the end of a far platform is an alert with remote diagnostics behind it, not a discovery made on a walk-through three days later.

That one console scales from a single station to a whole network. Content and schedules are managed per station, per platform, or system-wide; new stations join the fleet as deployments, not projects. For agencies and the integrators who serve them, the result is a display network that behaves predictably — which, for a departure board, is the entire point.