Skip to main content
Apollo NZ Global
← Broadcast + Replay Architecture

HLJÓÐ · Match-day operations + failover

Know the fallback before the screen goes black.

Define operators, test sequence, content / replay / scoring handoffs, backup signal paths, processor and power response, communications and shutdown procedure before event day.

One technical lead per eventFallback paths documented before doors openUnknown redundancy stays visibly unknownNo invented weather or electrical shutdown thresholds

Operating sequence

Five stages from power-up to handover.

A reliable venue system is not only hardware. It is a repeatable operating sequence with named responsibilities, known fallback paths and a clear record of what changed during the event.

01Pre-open technical check

Confirm screen power-up, processor status, inputs, cabinet health, signal path, scoring / graphics source and communications before spectators enter.

02Pre-match content + data check

Verify score / timing feed, replay sources, sponsor content, programme graphics, clean / dirty outputs and fallback content.

03Live-event operation

Keep operator roles clear. Log faults, confirm handoffs and use the agreed fallback path rather than improvising a new signal chain during play.

04Incident + failover

Identify whether the fault is source, production, transport, processor, screen, power or network. Move only to the documented backup path for that fault domain.

05Post-event shutdown + handover

Return the system to the agreed state, capture incidents / changes, preserve logs where required and flag unresolved faults before the next event.

Event operations brief

Assign the people and the backup paths.

Use actual named roles where possible. If a backup path does not exist, record that clearly and define the acceptable degraded operating state instead of pretending redundancy is available.

Operational review

Operational actions identified

These prompts identify missing operating decisions. They do not replace venue emergency procedures.

  • Operator communications are not yet defined. Match-day failover depends on a reliable communication path between scoring, production, screen and venue teams.

Failover matrix

Identify the fault domain before changing the system.

A production-source failure, transport failure, processor failure and screen-power failure need different responses. The matrix keeps the first response aligned with the actual fault domain.

Failure / incidentFirst operating responseLead role
Primary programme feed lostSwitch to agreed backup source / switcher output or approved fallback contentProduction / screen operator
Scoring / timing feed lostKeep the display running without unverified score data; use approved non-scoring content until the upstream feed is restoredScoring operator + production lead
Replay source lostContinue live programme / score presentation without replay unless a documented backup replay source existsReplay / production operator
Signal transport faultUse the pre-defined backup transport or alternate processor input where availableAV / production technical lead
Screen processor faultUse the project-specific processor replacement / bypass plan; do not assume an instant switchoverScreen / AV technical lead
Cabinet / module faultAssess whether operation can continue safely with the affected area isolated; service only under the approved access and electrical procedureScreen technician
Control-room power lossFollow the venue power-loss and safe-restart procedure; backup power is not established by this briefElectrical / AV lead
Full screen power lossFollow the project electrical fault / safe-restart procedure and confirm cause before re-energisingElectrical lead + screen technician

Final safe-isolation, electrical, structural, weather and restart procedures must come from the actual project documentation and responsible venue professionals.

Match-day handoff

Turn the technical system into a repeatable operating routine.

Use the brief at pre-event technical meetings and retain the final approved version with the venue operations pack.

HLJÓÐ MATCH-DAY OPERATIONS + FAILOVER BRIEF
OPERATIONS FLAGS
- Operator communications are not yet defined. Match-day failover depends on a reliable communication path between scoring, production, screen and venue teams.
FAILOVER MATRIX
- Primary programme feed lost → Switch to agreed backup source / switcher output or approved fallback content · Lead: Production / screen operator
- Scoring / timing feed lost → Keep the display running without unverified score data; use approved non-scoring content until the upstream feed is restored · Lead: Scoring operator + production lead
- Replay source lost → Continue live programme / score presentation without replay unless a documented backup replay source exists · Lead: Replay / production operator
- Signal transport fault → Use the pre-defined backup transport or alternate processor input where available · Lead: AV / production technical lead
- Screen processor fault → Use the project-specific processor replacement / bypass plan; do not assume an instant switchover · Lead: Screen / AV technical lead
- Cabinet / module fault → Assess whether operation can continue safely with the affected area isolated; service only under the approved access and electrical procedure · Lead: Screen technician
- Control-room power loss → Follow the venue power-loss and safe-restart procedure; backup power is not established by this brief · Lead: Electrical / AV lead
- Full screen power loss → Follow the project electrical fault / safe-restart procedure and confirm cause before re-energising · Lead: Electrical lead + screen technician
This is an operations-planning framework, not an emergency response plan or manufacturer service manual. Final procedures must use the actual venue systems, project documentation, electrical rules, structural / weather limits and nominated responsible people.

Complete the venue workflow

Operations sits on top of the technical design.

Broadcast + ReplayScoring IntegrationLighting + LEDSpecifier & Tender Centre
Project