Operator reference
Technical documents for the people who run screen estates, rather than the people who buy them. Each one is written from deployments we have run.
Every figure in them comes from a deployment, a test or the service agreement, and a document is revised when the product changes rather than archived. Topics run from how screens go dark and what uptime means to network requirements, display hardening and data residency.
-
What this is
A finite set of documents, not a blog.
Only what an operations lead, deployment engineer or IT reviewer needs to run Adverro, changed when the product changes.
-
Written from what we ran
Every figure here comes from a deployment, a test or the service agreement: the tested display baselines, how uptime is measured and what a screen needs from the network.
-
Revised, not archived
A document is updated when the product moves, and nothing here is archived. What you read describes the platform as it works now, not as it worked when the page was first written.
-
Written for the operator
The audience is the person who gets the call when a board goes dark in a terminal at six in the morning, not the person approving the budget.
What is in the library.
How screens go dark
A failure taxonomy for screen estates: every way a display stops showing what it should, sorted by whether you can clear it from a platform or need somebody standing in front of the panel.
Read itDisplay compatibility and provisioning
The tested platform baselines, the package format and installation route for each, and the four-step sequence for bringing a screen online.
Read itDeployment models
SaaS, private cloud and hybrid, with the responsibility split for each: who patches, who backs up, who is called when it breaks.
Read itData residency
Where content, telemetry and personal data physically sit under each deployment model, and what is selectable.
Read itWhat uptime means
How availability is measured on an Adverro estate, what the figure catches, and the one important thing it does not.
Read itHardening a display
Which standard endpoint controls apply to a signage panel, which cannot, and what stands in for each one that does not.
Read itNetwork and firewall requirements
The one outbound destination a screen needs, what travels over it, what happens when the connection goes, and a checklist for the change request.
Read itLive data on a screen
How flight, pricing, queue and rate information actually reaches a panel, and how a feed is bounded when its source stops responding.
Read itNeed something that is not here?
If your security team or your operations lead needs a document that is not here, ask a product specialist. A completed vendor security questionnaire is available on request.
