For a rollout of 44 screens at 32 to 43 inches, pick a commercial display family with a built-in SoC player that one cloud CMS supports. Provisioning then runs about 5 minutes per screen; adding an external player to every wall adds 15 to 20 minutes per screen and leaves a box to maintain. Order one screen, prove binding and remote reboot, then order the rest.
A fleet changes the answer. For one screen, a display with a built-in SoC player and a screen with an external player box sit close together, and the single-screen comparison covers that call. For 44 screens at 32 to 43 inches the routes separate: a built-in SoC player deletes a box, two cables and a registration step from every wall, worth 10 to 15 minutes of hands-on work per screen. Across this fleet that is one to two installer-days. So the rule for a rollout this size: choose displays with a built-in SoC player only when one cloud CMS supports that display family, and prove the pairing on one screen before you order the other 43. This page is the fleet-scale decision; the digital signage player guide holds the player basics.
One CMS across the fleet decides
Every major commercial display family carries a built-in SoC (System on Chip) player with its own app platform, and cloud CMS vendors write a player app for the families with large fleets. Each CMS publishes the display families it supports, usually down to model generation. That supported list is the decision.
If the family you planned to buy is on your CMS list, every screen installs the player from the display's own app platform and binds to the dashboard in minutes. If it is off the list, your options are a different display family, a different CMS, or an external box on every wall. At 44 screens, changing the family or the CMS now almost always costs less than fitting and maintaining 44 boxes.
Confirm the dashboard features you will actually use before you commit: content push to every screen, status reporting, a remote screenshot, a remote reboot, and firmware updates. A fleet you cannot reboot from the dashboard means a site visit for every hung screen.
Your options at fleet scale
| Route | Hands-on per screen | Fleet control | Fits when |
|---|---|---|---|
| Commercial SoC display your CMS lists | about 5 minutes | full: content push, status, screenshot, remote reboot | 20 screens or more, one family across the fleet |
| Commercial SoC display your CMS doesn't list | varies; usually means a second CMS or a family swap | split across dashboards | not at this scale |
| Commercial display plus external player | 15 to 20 minutes | full, and a failed box swaps out in the field | mixed sizes, odd inputs, screens the CMS app can't reach |
| Consumer TV running the CMS in its browser | minutes to set up, then a manual login per screen | little: no supported app, no commercial duty rating, no remote reboot | a screen or two |
The consumer-TV browser route is tempting because setup takes minutes. It trades away everything a fleet needs: after a power cut someone reopens the browser and logs in on every screen, one at a time.
Worked example: provisioning 44 screens at 32 to 43 inches
Inputs. 44 screens, each 32 to 43 inches, from the rollout in question; screen size barely moves provisioning time, the player's location drives it. SoC route: 5 minutes hands-on per screen, a planning figure that assumes the CMS account, screen groups and playlists are built in advance, each wall has a live network connection, and the installer only mounts the screen, opens the built-in CMS app and binds it to its group. External route: 15 to 20 minutes per screen, adding the player box mount, an HDMI cable and power to it, and a second device registered in the CMS. Scheduling basis: one 8-hour installer-day.
Rule. Installer time = screens x hands-on minutes per screen ÷ 60, then ÷ 8 for installer-days.
Arithmetic. SoC route: 44 screens x 5 min per screen = 220 min; 220 ÷ 60 = 3.7 hours, about half a day. External route: 44 x 15 min = 660 min = 11.0 hours; 44 x 20 min = 880 min = 14.7 hours; in days, 11.0 ÷ 8 = 1.4 and 14.7 ÷ 8 = 1.8 installer-days. Difference: 11.0 - 3.7 = 7.3 hours, and 14.7 - 3.7 = 11.0 hours across the fleet.
Result. The external route adds 7.3 to 11.0 hours of hands-on fit-out work, or 1.4 to 1.8 installer-days.
Threshold and decision. The extra 10 to 15 minutes per screen costs one full installer-day for every 32 to 48 screens: 32 x 15 min = 480 min = 8 hours, and 48 x 10 min = 480 min = 8 hours. At 44 screens, take the SoC route the moment one CMS supports the family. If no CMS you would choose supports it, change the display family or the CMS before ordering; carrying the external route costs up to 1.8 extra installer-days at fit-out and leaves a box behind every screen for the life of the fleet.
Duty rating and dashboard control to confirm
Two specs separate a commercial signage panel from a consumer TV. The first is the hours-per-day duty rating: commercial panels publish one on the spec sheet, consumer TVs publish none for commercial use, and a fleet that runs through all opening hours needs that rating written into the quote. The second is remote control: status, screenshot and reboot from the dashboard. At one screen a power-cycle is a walk down the corridor; at 44 screens it is a site visit per incident, so remote reboot is a requirement.
Each wall also needs a live network connection. A screen that drops off the dashboard is a network-path problem first, and the checks that fix one signage player losing its CMS connection are the same checks at fleet scale: link, address, path out, then the screen.
When to pick something else
Mixed hardware. Screens you already own, odd sizes, or a family the CMS app can't reach: fit external players to those screens and keep one dashboard, provided the CMS supports both player types. The per-screen trade-offs live in the SoC vs external player vs mini PC comparison.
No network at some walls. The cloud plan stops where the connection stops. The offline or cloud guide covers when to run a player from local storage instead.
Under about 10 screens. The provisioning delta shrinks to 1.7 to 2.5 hours (10 screens x 10 to 15 min), and a swappable external box starts to look reasonable again.
Small-format signs. Shelf-edge, counter and panel-mount signs are a different question: our panel-mount series plays straight from microSD or USB with no subscription, and larger wall screens in the current range, up to 75 inches, are quoted per project with software and rating confirmed in the quote. See the display range.
What to send with the order
- The CMS supported-list entry for the exact display model, size and generation, with the features you require confirmed: content push, status, screenshot, remote reboot, firmware updates.
- The hours-per-day duty rating, printed in the quote.
- One pilot screen as the first line of the order, with an acceptance test: bind it to a group, push a playlist, pull a screenshot, reboot it from the dashboard. Order the remaining 43 only after that passes.
- A network plan: one live connection per wall, and the CMS addresses allowed through the firewall.
- Mounting and power per wall: a mount rated for the panel and the wall type, an outlet within reach of the screen, and the power drops left to the electrician.
The decision
Recommendation: for a 44-screen rollout at 32 to 43 inches, shortlist commercial SoC display families your chosen cloud CMS lists as supported, order one screen, and prove binding, content push, screenshot and remote reboot on it before ordering the other 43. If your CMS doesn't support a family you were going to buy, change the family or the CMS now: fitting an external player to each wall adds 10 to 15 minutes per screen, one to two installer-days across this fleet, and a box behind every screen for years.
Questions
Does a built-in SoC player remove the CMS subscription?
No. Most cloud CMS platforms charge per screen, so the screen count drives the software cost whichever way the player is built. The built-in player removes the external box, its HDMI and power cabling, and the mounting and registration work per screen; it leaves the software line on the invoice unchanged. Ask the CMS vendor to price the full fleet before you compare panels, because over a few years the software line usually outweighs the hardware difference.
Can one cloud CMS manage SoC screens and external players together?
Usually, yes. Most CMS vendors publish supported players for several display families and for external player hardware, and screen groups work the same way for both. Check both entries on the supported list before you order anything. If the CMS supports one and not the other, you end up with two dashboards, two update routines and two sets of credentials, which is exactly what the family choice was meant to avoid at 44 screens.
What happens to a screen that loses its network connection?
It stops taking content pushes and stops reporting status, so it drops off the fleet dashboard until the network path is back. Whether it keeps playing its last synced playlist depends on the player's offline behaviour, which the CMS documentation states for the player you pick. Plan one live network connection per screen and test it during the pilot: a fleet-wide outage on the dashboard is nearly always the network, not 44 dead screens.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.