24/7 means 24 hours a day and 168 hours a week. Confirm that the named model supports that duty cycle, then test restart, offline content and fault recovery.
Check the exact product and conditions
A commercial category name does not establish identical duty-cycle support across every model. Ask for a dated data sheet and warranty wording for the offered model, together with its supported orientation. If a proposal states uninterrupted operation, identify what that statement covers: display electronics, player, CMS, internet connection or service response. Keep unsupported performance assumptions out of the requirement schedule and ask suppliers to mark exceptions explicitly.
Plan planned interruption as well as failure
A network may need maintenance even when visitors expect content at all times. Define a publishing window, an update window and a rollback method. Ask which changes can be made without interrupting playback and verify the answer on the offered configuration. A recovery plan should explain how a device returns after power loss, what content appears first and which person notices if it does not return. Treat an automatic reboot as a behavior to test, not a promise to assume.
Define a measurable service expectation
Agree how incidents are logged, who receives them and which operating hours the response covers. Separate response time from restoration time and ask where spare equipment is held. For critical information, define an alternate communication method when the screen is unavailable. The requirement should describe a business consequence and an accountable response rather than an unqualified percentage that no party has a measurement method to substantiate.
Compare requirements
| Project condition | Focus | Evidence to request |
|---|---|---|
| Panel duty cycle | Exact model documentation | Permitted hours and conditions |
| Playback continuity | Installed player and content | Recovery and cached fallback |
| Service continuity | Operating agreement | Response, restoration and spares |
Procurement checklist
- Attach the offered model’s operating limits.
- Define update and rollback windows.
- Assign incident ownership outside office hours.
- Test the agreed restart sequence.
A practical acceptance task
In a controlled maintenance window, simulate loss of the player’s connection and a safe power restart under the installer’s procedure. Record content recovery, alert delivery and any required manual action. Do not interrupt a live safety-critical system for this exercise.
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.
