Ask what the audience will see during a fault
“Backup included” is incomplete. Ask the supplier to describe a failure, the expected audience-visible effect and the recovery method. A spare component in a case may shorten a repair, while an already configured alternative path may maintain or restore the image differently. Both can be useful, but they should not be sold as the same outcome.
Start with the programme. A welcome loop that can pause has different needs from a live awards cue or a broadcast backdrop. Specify the moments that matter most, then compare the equipment and staffing needed to protect them.
Use a failure matrix in the quotation
| Possible fault | Question about the proposed response | What remains to check |
|---|---|---|
| Playback computer stops | Is a second source connected, loaded and ready for the correct cue? | How the operator switches and whether the same failure affects both sources. |
| Signal connection fails | Is there a supported, configured alternative route? | Which exact connections are covered and how the fault is detected. |
| LED processor fails | Is a compatible backup processor configured for this wall? | The changeover behaviour and consistency of the backup image. |
| A panel or module fails | Are compatible spares and authorised technicians available? | Access, replacement procedure and the effect of stopping work around the screen. |
| Supply interruption | Which loads, if any, have an agreed power backup? | Whether the screen itself or only control equipment is protected. |
Brompton's redundancy documentation distinguishes closed-loop data redundancy from processor redundancy and describes different changeover behaviour. Redundant operation also affects system capacity. Ask for the actual design and test result, rather than treating all redundancy as an invisible, instantaneous switch.
Look for dependencies shared by both options
Two playback computers still depend on how their signals reach the screen. Two saved copies can still contain the same incorrect export. A replacement processor is not ready if its mapping belongs to another screen. Trace the programme from content to display and ask where the primary and backup converge.
This does not mean every component needs a duplicate. It means the quotation should identify the uncovered failures so the organiser can make an informed choice. Keep operational continuity separate from equipment quantity.
Worked example: a product-launch film
Assume a hypothetical launch with a 90-second film that starts on the presenter's cue. The organiser asks for backup playback. Option A includes another laptop in a case. Option B includes a connected second player with the approved film loaded, an agreed switching method and a rehearsed recovery cue.
Compare what happens if the first player stops halfway through. With A, someone must prepare and connect the replacement before deciding where playback resumes. With B, the team can test its proposed switching and continuation method before the show. Neither description establishes uninterrupted playback; the supplier must demonstrate the actual audience-visible result.
Agree an editorial fallback too: restart the film, move to a holding slide or let the presenter continue. Put that decision in the cue sheet. An operator should not have to invent the programme response while also diagnosing the fault.
Spare parts need access and people
Ask which spares match the proposed panels and who can use them during the booked hours. A spare module is useful only with a suitable repair opportunity and an authorised procedure. ROE Visual's Ruby specification lists service access as a product property; the actual installation must preserve the access the chosen system needs.
Include the site's restrictions in the plan. If guests stand immediately around the display, a repair may require the organiser to clear a work area. Ask whether the event should continue elsewhere or pause. Do not plan for staff to improvise physical access during a live programme.
Rehearse recovery under an agreed test plan
List the failures the system is designed to cover and the ones it does not cover.
Have the qualified technical team define controlled tests before audience admission; event staff should not unplug equipment to experiment.
Check the backup content, mapping, picture appearance and cue position.
Record the observed interruption and the actions each role takes.
Confirm how the system returns to its normal state and who approves doing so.
Ask for the backup scope, test time and operator coverage as explicit quotation items. Reducing the scope can be a valid budget decision when the remaining exposure is understood; an undefined promise of “full backup” cannot support that decision.
Discuss critical programme moments with technical support when specifying LED equipment and LED rental. Request a plain-language failure matrix alongside the equipment list.
Further reading
Brompton: redundancy configuration; ROE Visual: panel serviceability example. Product features require the correct configuration and do not establish the resilience of an entire event system.