Skip to content

Read the Overview

Overview is the first page in Studio. It starts with one plain-language sentence about your fleet right now, such as “Most of your fleet is online, but 4 screens need attention.” Below it, the detailed cards answer five questions in order: is the fleet up, what is wrong, what is on air, what happens next, and did playback go as expected while you were away. Each card links to the page with the records behind it.

Studio Overview with Needs attention, On air now, Coming up, and fleet status sections.

The sentence is built from the same figures as the Fleet status card, so it never disagrees with them. It says how much of the fleet is online and how many screens need attention. It doesn’t mention schedules.

It says When
All 10 screens are online. Every screen is connected and nothing needs attention.
Most of your fleet is online… At least two thirds of the screens are online.
6 of 10 screens are online… Between a third and two thirds are online.
Only 3 of 10 screens are online… Fewer than a third are online.
No screens are online… None is online.
…reporting healthy playback Every screen is online and the Player confirms all of them are playing.
…but none is reporting healthy playback. Every screen is online, but the Players report problems and none is playing.

Playback is added only when it changes the meaning, that is, when every screen is online and nothing else needs attention. If playback can’t be measured, the sentence leaves it out. If the incident list is still loading, the sentence doesn’t say whether anything needs attention. If it can’t be loaded, the sentence says “at least” and counts only the problems Studio can already see. A fleet with no screens shows no sentence, only the pairing prompt.

Part What it tells you Where it opens
Fleet status Three figures: how many screens are online, how many the Player confirms are playing, and how many need attention. Screens or Activity
Needs attention The screens with a problem, most urgent first, and the reason for each. It appears only when something is wrong. The screen
On air now The content assigned to online screens, one row per playlist or presentation, with the screens set to show it. Screens
Coming up The next schedules to start or end, with the time until each one. The schedule
Last 24 hours Playback compliance, playback failures, and interrupted plays for the last 24 hours. The matching Activity report
Player updates The latest update deployment. It is highlighted only when a screen failed or is waiting for someone to act. Settings > Player updates
Content health Data Sources that stopped refreshing, playlists with nothing to play, expiring media, and screens with no content. Activity > Content Health
Fleet health The share of time screens were connected and playing, over 24 hours, 7 days, or 30 days. Per-screen rows on the page

If every screen is online and nothing is wrong, Needs attention doesn’t appear, and its figure in Fleet status is 0.

A screen is listed when Tilecast has a reason to think a person should look at it:

  • It is Offline, Stale, or its pairing was revoked. Understand a screen’s status explains these.
  • Its last Player update failed.
  • It has an open incident, such as a playback problem, low storage, or safe mode.

A Disabled screen isn’t listed. An Owner or Administrator turned it off on purpose, so it counts only in the fleet total. A screen that is Recently online isn’t listed either. It lost its connection a moment ago and is inside the two-minute grace period.

These two say different things, and Overview keeps them apart.

On air now lists what online screens are set to show: their assigned playlists and presentations, each with the screens that show it. An assignment says what Tilecast expects. It doesn’t prove the Player is showing it.

Playing in Fleet status counts the screens the Player reports as showing their content with no current fault. It is measured across the screens that are in service, so a disabled screen is not in the total.

Each figure names what it measures and links to the records it counted.

  • Playback compliance compares Player-confirmed screen time with the time Tilecast expected content to play.
  • Playback failures counts plays that failed.
  • Interrupted plays counts plays that ended unexpectedly. A schedule changing over isn’t counted.

If Players confirmed no playback and none was expected, Overview says there is nothing to measure. A figure without data shows No data, never 0. A zero means playback was measured and nothing went wrong.

  • Coming up reads each schedule’s own start, end, days, date range, and time zone. It doesn’t decide which schedule wins when two overlap. Display-control schedules aren’t listed because they send a command instead of changing what plays.
  • Overview reads the screen list. Studio lists up to 500 screens.
  • If one part can’t load, that part shows an error and the rest of the page keeps working.

Only an Owner or Administrator sees Pair screen on an installation with no screens.