NOC Runbooks for Cup Finals: A Field Manual from 12 Saudi & GCC Deployments

Every Skyline cup-final deployment ships with a 30-page printed NOC runbook — a literal flip-book that the on-call engineer pulls out when something goes wrong. After 12 cup-final deployments across Saudi Arabia and the GCC we've refined the template. This is what's in it.

Section 1: System map

One A3 page showing every node, every link, every IP, every contact phone number. Printed. Laminated. Hung on the NOC wall.

Section 2: Pre-match checklist

T-minus 4 hours: 47 checkbox items. Power feed verification (dual?). Network uplink failover test (manual switchover passes within 6 seconds?). PTP clock sync across all broadcast gear (offset under 100 microseconds?). Scoring console reachable from NOC dashboard? Mobile-phone signal in the gantry area? Each item has a YES/NO/N-A field and the operator initials.

Section 3: Incident playbooks

One playbook per failure mode. "Broadcast feed lost" → "Camera 7 lost PTP" → "Fan Wi-Fi DDoS suspected" → "Scoring console frozen". Each playbook lists: detection signal, escalation contact, mitigation steps in order, rollback procedure if mitigation fails.

Section 4: Communication tree

Who calls whom, when. The tournament director, the broadcast OB truck, the venue manager, the security chief, the vendor escalation, the federation observer. Phone numbers + radio channels + WhatsApp groups, all printed.

Section 5: Post-event reconciliation

End-of-match: archive all scoring data, snapshot the network state, log any incidents, submit the federation results form within 30 minutes of the final whistle.

Why printed

Because at the moment you need it most — power outage, network down, monitors dark — the digital version is unavailable. The printed runbook is always readable.