What you will learn
- What data a station display needs to be trusted
- How departure boards, platform screens and announcements stay consistent
- How disruption and platform changes are published quickly
- What station staff control, and what is automatic
- Why a display system fails when its data feed fails
What this project is
Passengers judge a railway by its displays. A board that says a train is on time when it is not, or a platform screen that still shows the previous train, destroys trust faster than a delay itself. A station information system takes timetable data, live train running data and disruption messages, and turns them into consistent information on every screen in the station and, ideally, in the passenger app too.
The system has two jobs: routine information and disruption information. Routine information is the departure board, platform assignment and calling pattern. Disruption information is the exception: cancellations, platform changes, replacement services and advice to use another route. The second job is where design matters most, because it happens under pressure, with incomplete information, and the message must be clear even when the full picture is not yet known.
Core features
- Departure and arrival boards fed by timetable and live running data, with delays shown honestly
- Platform screens that show the next train, its calling pattern and where to stand for each class or coach
- Disruption messages that can be published station-wide or to a single platform in minutes
- Consistency between screens, announcements and the passenger app, so all three agree
- Staff controls for manual messages, with templates for common disruptions
- Fallback displays for when the live feed drops, so screens show the timetable rather than going blank
How it is built
- Map every screen in the station and what each one should show, because a concourse board and a platform screen have different jobs
- Connect the timetable and live running feeds first, and prove the boards match reality for a week before adding disruption tooling
- Build the staff publishing workflow with approval steps for major disruption messages
- Add app and announcement consistency, then test with a simulated disruption across several stations
- Roll out station by station, keeping the old displays running until the new ones are proven
Technology considerations
The feed is the system. If the live running feed is late, wrong or missing, every screen inherits the error. Design for feed failure from the start: show the last known position with a timestamp, fall back to the timetable, and alert staff rather than silently displaying stale data as if it were live. Screen hardware varies too, from large concourse boards to small platform displays, so content should adapt to screen size rather than being a single layout squeezed onto every display.
Message wording needs care. A platform change announced in one sentence, with the new platform prominent, helps more than a paragraph of explanation. Staff should be able to publish a short, clear message fast, and the system should record who published what and when, so a confusing message can be traced and corrected.
Challenges to plan for
- A live feed that stops updating during a disruption, exactly when passengers need it most
- Platform changes that reach screens after passengers have already walked to the wrong platform
- Different messages on screens, apps and announcements for the same train
- Screens that go blank or show errors instead of falling back to timetable information
Who it is for, and its limits
This suits a station operator, a railway company or an authority managing several stations. It fits stations where passengers need live information to choose platforms and connections. It does not fit a small halt with one train an hour and no live feed, and it is not a train tracking system on its own: it displays running data, it does not create it.
A display system does not make trains punctual, and it cannot invent live data where no feed exists. If the underlying running data is poor, the displays will be poor too, however good the screens look. Costs vary with the number of stations and screens, so confirm with a quote after a station survey.
Frequently asked questions
What happens when the live feed fails?
Screens fall back to timetable information and show that live updates are unavailable, rather than going blank or showing stale times as live. Staff are alerted so the failure is fixed, not discovered by passengers.
Who can publish a disruption message?
Trained station or control staff, using templates for common situations. Major messages can require a second approval, but routine platform changes should not wait for a committee.
Do the app and the screens show the same information?
They should, because they read the same data. If they disagree, passengers trust neither. The design goal is one information source, many displays.
Can displays show more than departures?
Yes: safety messages, station facilities, onward connections and service alerts. But departure information comes first, and extra content should never push it off screen.
How are platform changes handled?
As a distinct, prominent message on the affected platform and the concourse board, with the new platform shown first. A quiet edit to a small line of text is how passengers miss their train.