Board design and publishing
Composed once, published to the sites that need it.
Passenger information boards
Arrivals, departures and gate boards are the most recognisable screens in the category, and the most often oversold. Here is the part ScreenQube evidences, and the part it does not.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
The screen above is what you publish. This is where it ends up.

How it is made
Named against the product's own modules rather than invented for a marketing page.
Composed in Composition and published to the screens and sites you choose.
Every station, terminal or depot is a facility holding its own screens.
Seasonal timetables and planned works, with a start and an end.
Live Monitoring counts active and disconnected screens, per facility.
What you get
Composed once, published to the sites that need it.
Set once, with an end that arrives on its own.
Published as media to the sites affected.
The operational question at 05:00, as a headline tile.
Reports run in three kinds: a Media Report, an Uptime Report and Audit Logs.
Audits, with a name against each action.
Who runs this
Nearby
Questions
No. No transport data connector exists in the console. The nearest thing is the web-URL app: a board your own systems publish as a web page can be displayed and scheduled. That is display, not integration.
Every screen that is not the live board — wayfinding, notices, safety, retail and staff information — plus publishing, scheduling, monitoring, reporting and auditing across every site.
Yes. Weather, news, currency, YouTube and tickers are all App Store apps.
An Android player app on displays you own.