Evaluate a digital-signage CMS with actual publishing and recovery tasks. Test approval roles, screen grouping, scheduling, local time, cached playback and monitoring on the proposed player. Content management and device management are separate capabilities. Ask which licenses, integrations and support terms are required for each feature before comparing the total operating cost.
Use a representative publishing week
Build a test playlist with a routine campaign, an urgent update and content that expires. Include Arabic, English, portrait and landscape samples where the project uses them. Ask a local editor to propose a change and a central approver to release it. Verify which screens receive the change and when it becomes visible. Document the CMS, player and content versions so a successful demonstration is tied to the offered combination.
Test the difference between publishing and health
A scheduled item in the CMS is not evidence that the display is lit and visible. Ask what a health signal measures: an online player, a running process, an active display connection or a stronger device report. Define who can change device settings and who can publish content. Restrict each role to its work. Verify sign-in and account recovery using the organization’s IT policy rather than relying on a shared administrator account.
Write the offline and exit requirements
Disconnect the test player from the internet and observe which content continues, which updates wait and how expired material behaves. After reconnecting, verify synchronization and alerts. Ask how the team exports its content, device inventory and playback records if it changes provider. Record subscription limits, storage, player licensing and optional support separately. A migration path and a working fallback can matter more than a long list of unused widgets.
Compare requirements
| Project condition | Focus | Evidence to request |
|---|---|---|
| Publish content | CMS | Roles, approval, schedules |
| Keep devices healthy | Device management | Inventory, alerts, remote actions |
| Prove a playback event | Playback reporting | Event definition and export |
Procurement checklist
- Test the proposed player, not a substitute.
- Verify time zone and schedule behavior.
- Record license boundaries.
- Agree an export and migration path.
A practical acceptance task
Run the sample week in a small test group. Include one rejected edit, one timed expiry, a connection outage and a recovery. Have the intended operator perform the work and export a report that explains what happened.
Build a project briefTechnical references & installation scope
Confirm the offered model’s limits and applicable local requirements with the responsible project team.
- AVIXA · AV Systems Performance Verification
Public overview of performance-verification planning, timing and reporting.
Manufacturer & integration resources
Display product pages and AV integration service information. Obtain exact-model installation instructions separately. External links open in the same tab.
LG
Browse LG commercial-display product families for comparison. A product page is an introduction to equipment; request the exact model’s installation instructions and operating limits for your proposed assembly.
