Digital Signage

How It Works & Technology Overview

A signage system is three subsystems with different labor profiles: infrastructure (displays, mounts, media players, power, network), CMS (the content-management platform that schedules and distributes content to players), and content operations (who builds and updates content after go-live). Players are dedicated devices (BrightSign-class), system-on-chip inside commercial displays (Samsung Tizen, LG webOS), or PC/Android boxes. Players cache content locally and phone home to a cloud or on-prem CMS — so network design is about reliable outbound connectivity and content-download windows, not streaming bandwidth. Display selection is driven by environment: ambient light (standard commercial panels are ~350–700 nits; storefront/direct-sun placements need high-brightness 1,500–3,500+ nit units), orientation (landscape/portrait), duty cycle (16/7 vs 24/7 rated), and heat/ventilation at the mounting location. Video walls add a compounding layer: structural backing, micro-adjustable mounts, bezel alignment, and color calibration across tiles.

Common Deployment Scenarios

• Corporate lobby/communications displays: a handful of screens, cloud CMS, marketing-owned content; the content plan matters more than the hardware.
• Menu boards (QSR/retail): portrait/landscape arrays above counters, dayparting schedules, price-sync integrations; uptime and heat are the field issues.
• Video walls: 2×2 up to monument builds; per-tile alignment and calibration labor compounds, and structural review is non-negotiable.
• Wayfinding/interactive kiosks: touch overlays, ADA height/reach compliance, enclosure ventilation; software integration (directories, maps) is its own scope.
• Outdoor/drive-thru: high-brightness, sealed enclosures (IP/NEMA-rated), dedicated circuits, wind load and sometimes municipal signage permits/zoning.

Products, Vendors & Characteristics

• Players: BrightSign (dedicated, reliable, provisioning via USB/network bootstrap — they don't auto-configure), SoC displays (fewer boxes, tied to panel brand), Android/PC players (flexible, more support surface).
• CMS platforms: Appspace, Scala, Navori, ScreenCloud, Yodeck, BrightSign's own network, Samsung MagicINFO/VXT, LG SuperSign — subscription per screen; the operating client (marketing vs IT vs ops) should choose, not procurement alone. On-prem CMS behind a corporate firewall shifts deployment from minutes to an IT coordination project.
• Displays: Samsung, LG, NEC/Sharp, PPDS (Philips) commercial lines; high-brightness/outdoor from the same families plus Peerless/SunBrite-class enclosures; dvLED (Samsung/LG/Absen/Planar) for large-format walls.
• Mounts: Chief, Peerless-AV, Premier — pop-out/micro-adjust mounts for video walls; wall type (drywall/concrete/glass) drives mount selection and labor.

What Makes It Hard (Gotchas & Failure Modes)

• Content operations get priced backwards. The project is ~20% hardware and ~80% content pipeline; proposals that omit template design and an ownership plan produce logo-loop lobbies and unhappy clients. Content creation is a separate line item — clients always assume it's included.
• Sunlight and heat kill displays. Standard panels wash out and suffer permanent damage in direct sun; recessed millwork placements without ventilation cook players and panels — pull-out mounts and airflow are design items.
• Finished walls lie. Assume light-gauge studs and no blocking until a drawing or test proves otherwise; video walls need verified structural backing with real safety factor.
• Corporate networks resist players: VLAN isolation, 802.1X, firewall whitelisting for the CMS cloud — player enrollment becomes an IT-coordination task; get the network requirements sheet approved before install day.
• Screen counts grow after rough-in ("while you're here" additions needing new runs), and every added screen re-opens cabling scope.
• Commissioning with placeholder content hides failures — soak-test 24–48 hours with the real production files at real bitrates before sign-off.
• Day-two CMS reality: dayparting logic, approval workflows, localized pricing feeds — the "software install" assumption misses where CMS labor actually lives.
• Live-data screens: a dashboard or production-numbers screen is an integration with another system's owner — the data often lives on a separate or controlled network (plant floor, POS, finance) whose owner must approve access, and that approval sets the schedule.

Effort & Estimation Patterns

• Standard interior display + player, wall-mount: 2–3 hours per screen fully installed and enrolled.
• Outdoor display (enclosure, dedicated circuit): 4–6 hours plus electrician coordination; permits add calendar time.
• Video wall: 4–6 hours per tile (mount, multi-axis alignment, bezel calibration) plus a half-day for wall configuration and color matching; structural backing verification precedes everything.
• CMS platform setup (tenant configuration, player enrollment, playlist structure): 1–2 days initial.
• Content templates: 4–8 hours per template depending on complexity; data-driven templates (menus, dashboards) at the high end plus integration time.
• Kiosks/interactive: hardware install 3–5 hours per unit; software/content integration scoped separately.
• Multipliers: concrete/glass mounting, ceiling-suspended arrays, occupied retail hours (night work), and restricted networks (add 2–4 hours per project of IT coordination, more with 802.1X).
• Recurring: CMS subscription resale, content-update retainers, and monitoring (player-offline alerts) price per screen per month; lamp-free panels have pushed maintenance toward monitoring + content rather than parts.