How to identify critical functions, failure domains and practical fallback paths without mistaking duplicate equipment for a resilient production.
Editorial principle
Redundancy is useful only when the backup survives the same failure, can be activated in time and has been rehearsed.
The PROVANTAGE Handbook / Production resilience
Redundancy begins by naming the live function that must continue and the maximum acceptable interruption—not by purchasing a second copy of everything.
A backup is credible only if it avoids relevant shared failures, is current and ready, can be selected in time and has an operator who recognises when to act.
Identify the speech, content, playback, display, audio or communication functions whose interruption matters.
02
Set recovery objective
Define acceptable audience impact and how quickly service must return.
03
Map failure domains
Find shared power, processors, networks, switches, routes, configuration and people.
04
Choose response
Prevent the failure, monitor it, add an independent path or prepare a simpler fallback.
05
Assign the action
Specify who detects, decides, switches, communicates and restores.
06
Prove the plan
Simulate representative failures safely and record actual recovery behaviour.
The duplicate-laptop trap
TWO DEVICES.
ONE SWITCHER.
ONE FAILURE.
Two playback computers feeding one unprotected switcher, one output path or one power circuit do not protect the complete presentation function. Follow the signal to the audience and inspect every shared dependency.
The practical output
BACKUP IS
A REHEARSED
ACTION.
Create a critical-function map showing primary path, fallback path, shared dependencies, monitoring, recovery owner and tested recovery time.
By PROVANTAGE · Published 2026-08-24 · Updated 2026-08-24
Production redundancy questions
USEFUL ANSWERS.
Short answers to common event-technical-production questions.
01Does having two laptops create presentation redundancy?+
Only if the second system has the correct current content, an independent usable signal path and a tested switching method that operators can activate within the acceptable recovery time.
02What is a failure domain?+
It is a component or condition whose failure can affect multiple supposedly separate paths—for example one switch, power circuit, processor, cable route or operator action.
03Should every event system be duplicated?+
No. Prioritise functions according to consequence, likelihood, detection and recovery time. Some risks need prevention or a simpler fallback rather than full duplication.
04How is redundancy tested?+
Simulate representative failures safely before show day, observe alarms and audience impact, execute the fallback and record recovery time and ownership.