Wayfinding and exits
Platforms, gates, taxi ranks and step-free routes.
Transportation
The concourse board
and everything around it.
A station runs two kinds of screen: the ones that carry live service information, and the many more that carry everything else — wayfinding, safety, retail, notices. ScreenQube runs the second kind across every site you operate, from one browser.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
You work in a browser.
They see the wall.
The screen above is what you publish. This is where it ends up — a display a customer stands in front of, driven by a player that fetched it on its own.
What goes on the screens
Six things worth putting up.
Every one of these is ordinary media, arranged in Composition and sent out by Publish. Nothing here needs a separate system.
Safety and security notices
Line-of-sight notices that have to be current across every site.
Service notices and disruption messaging
Published as media to the screens and sites you choose.
Retail and concession promotion
The commercial screens beside the information ones.
Timetable posters and seasonal changes
The printed timetable, replaced without a print run.
Staff and depot notices
Back-of-house screens on the same platform.
Where the screens go
Four walls that earn it.
-
Concourse and ticket hall
Wayfinding, notices and commercial content in the busiest space you have.
-
Platform and gate approaches
Short, legible, and read at a glance.
-
Interchange and taxi ranks
Where people are deciding where to go next.
-
Depots and staff areas
Rotas, safety and operational notices.
How it is run
Four steps, then it runs itself.
The same four steps whether you have four screens or four hundred. This is the real console, not an illustration.
-
Add facilities, pair screens
One facility per site, branch or building. A screen joins by showing a registration code, which you type in once. Switch between facilities from the header.
-
Upload and compose
Media goes into the library, in folders, with tags. Composition arranges it into zones — your own files, plus App Store apps like weather, news or a ticker.
-
Publish three ways
On a schedule, with day sequences. Or QuickPlay, which the console describes as displaying content instantly for a flash sale or an emergency. Or as the default composition a screen falls back to.
-
Check it, without going there
Live Monitoring reports each screen's state. Take Screenshot shows what one is really displaying. Reload, clear the cache or reboot it remotely.
What it fixes
The three complaints we actually hear.
- Notices are printed per station and nobody knows which are current.
- One library, one publish, and Audits recording each change.
- A screen at a small station has been dark for weeks.
- Total Disconnected Screens is a headline tile, per facility.
- Every station is a separate estate to manage.
- Each station is a facility. Publish targets one, several, or all of them.
Set it up as
The solutions this usually becomes.
Nearby
Other industries with the same problem.
Questions
What transportation teams ask first.
Can it drive live arrivals and departures from our feed?
No live transport-data integration has been observed in the console. See the passenger information page for exactly what is and is not confirmed today.
Can we manage each station separately?
Yes. Each station is a facility with its own screens and a facility switcher in the header.
What happens if a site loses connectivity?
The screen is counted in Total Disconnected Screens. Whether a player continues to play its last content offline has not been confirmed.
What hardware is supported?
Android players, on displays you own.
Put it on every screen.
Talk to us about becoming the partner who sells it.
We will introduce you to the partner who covers your region.