Wayfinding, concessions, employee areas and the advertising estate usually run on four contracts, and none of them tells you when a screen goes dark.
Concourse wayfinding on one system, the concessions estate on another, employee screens on a third, and the advertising network on a fourth. Between them they are most of the glass in the building, and the thing they all have in common is that a screen goes black and nobody finds out until a passenger says so. One platform runs all of it, every screen reports whether it is actually rendering rather than whether a command was sent, and anything the airport already publishes as a feed can be on any of them.
Flight information is operationally critical and usually runs on a dedicated system wired into the operational database, with redundant data paths and automatic failover. Most airports want that left exactly where it is, and we run alongside it happily: if the operational database publishes a feed, we render arrivals, departures and gate changes on the concourse, concession, lounge and employee screens that sit outside that certified path, so a passenger in the food hall sees the same gate change as the passenger standing under a flight board.
And if you want the critical path itself, that is a build and we will quote it. It comes with a specification rather than a feature list: failover time, redundant players, accessibility, language handling and an acceptance test written down and engineered to. We have always built to what a customer runs rather than to a supported list, and this is the same answer in a harder room.
What an airport asks first, before cost. Whether it opens a port, whether it touches the operational network, and whether a screen failing at three in the morning is something anybody finds out about. Outbound connections only, no inbound rules, and every screen reporting its own storage, temperature and render state continuously.
The advertising creative is video, and that is where the rate goes up. Full-motion spots on the concourse network and the spectaculars, in the daypart they were sold for, cached on each screen ahead of the slot so a busy morning never turns a paid spot into a still frame. The same path carries a terminal-wide announcement when it is needed.
Runs alongside your flight information system today, and can be built to the critical path if you want it there.
Any feed the airport already publishes can reach a screen, including operational data on non-critical displays.
Priority messaging takes every screen at once, in order, and each one confirms it rendered.
24 hour operation with per screen temperature, storage and render reporting, because a hot enclosure is what kills a player.
Outbound only. No inbound rules and no change to the operational network.
Adapters owned outright at $50 each, so a terminal refit does not become a hardware negotiation.
None of the above is a playlist somebody maintains. Each screen is a surface for Ava, which holds one understanding of the place and knows which room it is in, so what belongs there at that hour is composed rather than authored. A concession list and a daypart are enough for her to keep a concourse honest while the operational systems keep doing their own job.
At $40 per screen per year with the hardware owned outright, the interesting number is not ours. It is the sum of what the concourse, the concessions estate, the employee screens and the advertising network cost today under four separate contracts.