Shenzhen Qunmao Display Technology Co., Ltd.Shenzhen Qunmao Display Technology Co., Ltd.Shenzhen Qunmao Display Technology Co., Ltd.Shenzhen Qunmao Display Technology Co., Ltd.Shenzhen Qunmao Display Technology Co., Ltd.Shenzhen Qunmao Display Technology Co., Ltd.
Shenzhen Qunmao Display Technology Co., Ltd.
Home  >  News  >   Product Knowledge

Elevator Advertising Screen System Features: Media-Grade CMS, Bulk Publishing & Remote Control

Elevator Advertising Screen System Features: Media-Grade CMS, Bulk Publishing & Remote Control Guide

Elevator Advertising Screens · Hardware + CMS Selection Guide

Elevator Advertising Screen System Features: How a Media-Grade CMS and Paired Displays Deliver Bulk Publishing and Remote Control at Scale

When you move from a few dozen screens to hundreds or thousands, the deciding factor is no longer panel brightness or bezel width. It is whether your media-grade CMS and your elevator advertising displays are designed to work together. The CMS plans, schedules, reports and sends commands. The terminal decodes, caches, reports back and keeps running. When those two layers are sold separately, scale breaks down at exactly the points that matter: missed slots, unverifiable playback and slow fault detection.

Inside: media-grade CMS · multi-device grouping · bulk publishing and scheduled rotation · playback data · stable operations


01The Media-Grade CMS: The Operating Hub Behind Every Display

Most buyers evaluate the screen and the software as two separate purchases. They compare panels on brightness and bezels, then compare CMS platforms on how many buttons the dashboard has. In day-to-day operations, those decisions cannot be separated. Every instruction from a media-grade CMS has to be executed by the display terminal, and the terminal's decoding power, storage headroom and network module determine how much of the CMS you can actually use.

A CMS Is Not an Upload Tool. It Is Three Linked Layers.

A workable platform has three parts. The cloud layer holds the asset library, playlist creation, scheduling engine, permissions and reporting. The player runs inside the elevator advertising display and handles content download, local caching, decoding and log upload. The management layer gives headquarters, regional managers, content staff and field technicians role-based access from web and mobile.

The layer most often under-specified is the terminal. A perfectly built schedule fails at the last metre if the display has too little storage, a weak decoder or a network module that cannot hold a signal inside a metal elevator shaft. That is the difference between a hardware supplier writing about software and a pure software vendor writing a feature list: every CMS capability has to answer the question, what hardware actually executes this?

Three Requirements Overseas Buyers Always Test

  • Multi-time-zone scheduling. Campaigns go live and come down on local time, not on a spreadsheet conversion. Get the time zone wrong and the ad runs outside the contracted dates, which makes the invoice impossible to defend.

  • Tiered permissions. Headquarters approves everything. Regional managers publish only to their cities. Content staff upload assets but cannot touch device settings. Technicians reboot and diagnose but cannot edit a schedule. Permissions are not a policy document; they are an engineering control that stops a sales rep from overwriting a live campaign.

  • White-label delivery. The interface, domain and reports can carry the agency's brand, so the agency hands advertisers its own playback reports without exposing the upstream platform. Real white-label means configurable report fields and export formats, not just a swapped logo.

Hardware sideQunmao dual-screen elevator advertising displays (QM-1910FZ, QM-2112FZ, QM-2724FZ) provide Wi-Fi, LAN and optional 3G/4G modules at the terminal layer, with 2×USB 2.0, 1×RJ45 and a TF card slot for local expansion and maintenance. Every unit completes a 48-hour burn-in before shipping. The CMS multi-time-zone schedule and bulk push depend on a stable network path and local storage inside the display, not on a dashboard alone.

02Multi-Device Group Management: Organizing Hundreds of Screens by Terminal Identity

Grouping is often described as tagging devices. That undersells it. Across a network that spans countries and cities, groups are the permission structure, the scheduling logic and the billing boundary all at once. Which group a screen belongs to determines who can operate it, what content it receives and which advertiser's report its playback data lands in.

A Four-Level Structure That Holds Up

In practice, the most durable hierarchy is country or city → building or venue → floor or elevator → individual device. Geography handles time zones and market-specific creative. Venue type separates residential, office, retail and healthcare playout rules. Client and agency groups enforce access isolation so each advertiser or channel partner sees only its own screens. Screen type handles single versus dual display, landscape versus portrait, and resolution differences in scheduling.

Grouping Depends on Clean Terminal Identity

A CMS can only group devices it can identify. Serial numbers, installation addresses, building ownership and screen type tags all need to be standardized before a bulk import. If serial number formats vary between production batches, or if the installed location no longer matches the record, your groups become a structure that looks organized but cannot find the device.

Qunmao ships each batch with a serial number and hardware configuration list, so the CMS import maps cleanly. On the dual-screen series, the top and bottom display combinations (18.5"+10.1", 21.5"+12.1", 27"+24") are registered as distinct screen type tags. Mixed deployments still roll up under the same grouping logic instead of being treated as unrelated hardware.

Grouping Only Pays Off When Actions Run at Group Level

Once groups exist, group-level power cycling, rebooting, screenshots, and brightness or volume adjustment become practical. An agency running 800 screens across five cities can push a city-specific promotion to a single city group without touching neighbouring markets. When several displays in one building go offline together, the technician jumps straight to the floor or elevator group instead of scrolling through a flat device list.

03Bulk Content Publishing and Scheduled Rotation: The CMS Plans, the Display Executes

Bulk publishing and scheduled rotation are the easiest features to demo and the easiest to break in production. The problem is rarely the dashboard. It is whether the elevator advertising display can reliably execute what the CMS plans.

Five Steps, Each With a Hardware Constraint

  1. Asset upload and transcodingThe CMS adapts creative to terminal resolution. Dual-screen units have different top and bottom resolutions and aspect ratios, so transcoding rules must be configured per screen position rather than applied as one template.

  2. Playlist or template creationRetail, property management and wayfinding layouts can reuse split-screen templates to cut launch time. Template reuse depends on player firmware compatibility.

  3. Target selectionPublish by device group, tag or individual screen, using the hierarchy from section 02 to avoid pushing to unauthorized markets.

  4. Scheduling and priorityDates, dayparts, loop rules and emergency override priority. Automatic start and end dates are driven by CMS rules but executed against the local schedule on the player.

  5. Bulk push and status confirmationThe CMS reports success, failure or pending sync. Pushing large video files to every screen at once saturates building networks; staged delivery and early scheduling beat a single all-at-once push.

Offline Playback Is a Set of Cache Parameters, Not a Slogan

Elevator environments are hostile to connectivity: metal shafts, basements, active construction and carrier handoffs all interrupt live networks. Saying "it keeps playing offline" is not enough. What you need to confirm is how long it caches, what it caches, what happens when storage runs low, and whether it can roll back to the last known-good playlist if a file corrupts.

After a push, the terminal should hold the full playlist and schedule locally. The network then carries only new assets, status reports and remote commands. During an outage the display keeps playing to its local schedule; on reconnect it syncs logs and status incrementally. Storage must reserve headroom for logs, firmware packages, emergency inserts and rollback versions, rather than filling every gigabyte with promotional video. Large downloads should support chunking and resume, scheduled outside peak elevator traffic.

A testable requirementDo not leave offline playback on a feature list. During sample testing, confirm that under a simulated outage the display completes a full scheduled loop, that logs are backfilled after reconnect, and that falling below the storage threshold raises a CMS alert. If those three actions work, the deployment model is repeatable.

04Playback Data and Device Monitoring: Proof of Play From the CMS, Raw Data From the Display

In elevator media, "the screen is on" and "the ad ran as contracted" are two different facts. Advertisers pay for delivered impressions within a flight, not for electricity. Proof of play matters because it converts a planned schedule into actual, exportable, billable playback records.

Device Monitoring Answers "Can It Play?"

Online status, last sync time, signal strength, storage headroom and playback state are the baseline telemetry a display reports back. Alerts cover offline events, low storage and playback failures, delivered through the dashboard, email or mobile push. A well-built CMS does not flag a fault the moment a heartbeat is briefly lost; it waits for the threshold and backfills missing status and logs once the network recovers.

Playback Data Answers "How Much Ran, and How Do We Bill It?"

Playback logs record the asset, the device, the timestamp and the duration. Proof-of-play reports export by device, building, city or campaign flight. For an ad operator, that report is the underlying evidence for advertiser reconciliation and post-campaign review. If a contract calls for a 15-second spot and the screen actually ran five seconds, manual spot checks will rarely catch it, and the invoice has nothing to stand on.

Log retention and offline backfill on the terminal decide whether proof of play is complete. Playback records generated during an outage must persist locally and upload on reconnect, rather than leaving a blank segment in the data. An hour offline or a failed asset load should appear as an identifiable gap in the playback record, not be masked by the schedule table.

Case 01 · From Manual Site Checks to Proof-of-Play Reconciliation

Background

A regional elevator media operator managed building sites across several cities, with advertisers billed monthly. Proof of play was collected by sending staff to photograph screens on site. Covering several hundred locations took a week, and by the time the report was ready the flight was already half over. Missed slots could only be logged, rarely corrected within the same cycle.

What Changed

During bulk rollout, playback log upload and offline backfill were added to the sample acceptance checklist. The CMS generated proof-of-play reports by campaign flight, building and city. Operations configured storage-threshold and offline alerts so displays never stopped logging because the disk was full. Sales and finance reconciled against terminal logs instead of site photographs.

Outcome

Missed playback moved from "discovered after the flight" to "identified during the flight and made up or credited." Billing disputes shifted from verbal negotiation to record comparison. What the operator delivered to advertisers was no longer a site list but a playback record with device, timestamp and duration, which shortened the reconciliation cycle.

05Stable Operations: Remote Control Only Works When the Display Is Reliable

If remote control means "click reboot in the dashboard," it does not solve the real cost of scale. Overseas operations face two pressures: terminals are geographically dispersed, so site visits are expensive, and elevator shafts steadily wear down hardware through heat, humidity, dust and vibration. A remote management system earns its keep by diagnosing, fixing and reconfiguring without sending anyone on site, reserving physical intervention for the cases that truly need it.

Know What Remote Control Can and Cannot Do

Reboot, screenshot, brightness and volume adjustment, and live view of the current playback frame cover a surprising share of soft faults: a hung player, a failed asset load, a mis-set volume. Group-level execution avoids logging into screens one by one, but only if the terminal acknowledges commands and the CMS can confirm the action actually took effect rather than just showing "sent."

OTA and Staged Rollouts Reduce Upgrade Risk

Player firmware, application and configuration updates should ship in batches and staged rollouts. Validate playback stability, network compatibility and log upload on a small set first, then widen. A failed bulk upgrade on elevator displays costs far more to recover from than the upgrade delivers, which makes staged rollout a requirement rather than an option.

Hardware Reliability Is the Physical Precondition

Remote diagnosis and reboots solve software problems. They cannot substitute for industrial-grade terminal design. Elevator shafts demand 24/7 operation across temperature swings, humidity, dust and vibration; power specifications, network bands and mounting accessories must match the destination market. Qunmao dual-screen elevator displays complete a 48-hour burn-in before shipping and carry CE, FCC, UL and RoHS certification, which reduces the on-site rework that comes from mismatched power and certification requirements.

Permissions and Audit Trails Are Part of Remote Capability

Remote reboot, screenshot and OTA are high-privilege operations and need role isolation plus an action log. Technicians diagnose and reboot but cannot edit a campaign. Content staff publish to authorized groups but cannot touch device configuration. Every remote command produces a traceable record, and the control channel is encrypted so it does not become the weakest link.

Case 02 · Turning a City-Wide Outage Into a Tiered Response

Background

A multi-city operator hit a rainy season event where displays across several buildings in one city went offline together. Problems were previously discovered through property manager calls or advertiser complaints, and technicians worked building by building with little control over recovery time.

What Changed

The CMS was configured with tiered offline alerts. Regional technicians received a mobile push first and checked last heartbeat, storage headroom and playback state remotely. When multiple displays in one building dropped at once, the system grouped them into a building-level event so the team could determine whether the cause was building network or individual hardware. Issues solvable by remote reboot were closed without a site visit; site visits carried parts and a diagnosis rather than a guess.

Outcome

Operations shifted from waiting for complaints to responding by alert tier. Most soft faults closed remotely, and site visits concentrated on terminals that genuinely needed physical work. Recovery time dropped, and the team built a reusable record of which buildings had weak networks and which hardware batches needed closer attention.

Three things to verify with a sample unitFirst, offline playback and log backfill under a simulated outage. Second, success rate and duration when pushing large assets in bulk. Third, command acknowledgement for remote reboot, screenshot and OTA on the target network. Once these pass, the operational model for bulk deployment has a foundation.

06Hardware and CMS Selection Checklist

Pulling the five sections into a buying decision, the test is not how long the feature list is. It is whether each CMS capability has matching hardware behind it, and whether the terminal has been validated on a sample unit before bulk delivery.

Selection areaWhat to confirm on the CMSWhat to confirm on the elevator display
Media-grade CMSMulti-time-zone scheduling, tiered permissions, white-label reports and domainWhether the display ships as a paired package with the CMS; network module options (Wi-Fi / LAN / 3G/4G) matched to building conditions
Device groupingCountry/city/venue/client hierarchy with access isolationConsistent serial number format; installation address and screen type bindable in the CMS
Bulk publishingBulk push, automatic campaign start and end, emergency override priorityDecoder capability, storage headroom, offline playback policy and file rollback
Data and proof of playPlayback log export, reports by flight/building/city, alert deliveryLocal log retention and offline backfill; configurable storage alert threshold
Stable operationsStaged OTA, remote reboot and screenshot, action audit logIndustrial design for shaft temperature, humidity, dust and vibration; power and interface specs
Overseas deliveryMultilingual interface, multi-currency reports, time-zone rulesDestination market certification (CE/FCC/UL/RoHS), power specification, mounting accessories and spare parts

The real dividing line in elevator advertising screen system features is not how many buttons the dashboard offers. It is whether the media-grade CMS and the display terminal are paired tightly enough to turn grouping, publishing, scheduling, data and operations into a repeatable delivery loop. The CMS sets the ceiling on operating efficiency; the terminal decides whether that ceiling holds inside an elevator shaft. Evaluating both on the same sheet gets you much closer to real operating conditions than comparing panel specs or watching a dashboard demo in isolation.


Get a CMS Demo and Request a Sample Unit

Share your target countries, planned screen count and building network conditions, and we will come back with a paired hardware and CMS proposal plus bulk pricing. Sample testing covers group binding, bulk push, offline playback, playback log upload and remote operations on your network.

Request a Sample and Proposal   View the Product   Chat on WhatsApp

Phone / WhatsApp: +86 131 4872 6043 | www.szqunmao.com

This article covers elevator advertising screen system features, media-grade CMS, bulk publishing and remote management. Capabilities described depend on paired CMS and terminal delivery and on results verified during sample testing.

Related news
Copyright © 2015-2026 Qunmao Display Technology Co., Ltd. All Rights Reserved.
  • Shenzhen Qunmao Display Technology Co., Ltd.
  • Shenzhen Qunmao Display Technology Co., Ltd.
  • Shenzhen Qunmao Display Technology Co., Ltd.
  • Shenzhen Qunmao Display Technology Co., Ltd.
  • Shenzhen Qunmao Display Technology Co., Ltd.
Shenzhen Qunmao Display Technology Co., Ltd.
Shenzhen Qunmao Display Technology Co., Ltd.
Shenzhen Qunmao Display Technology Co., Ltd.
Shenzhen Qunmao Display Technology Co., Ltd.
Shenzhen Qunmao Display Technology Co., Ltd.