The FINA World Swimming Championship at Etihad Arena Abu Dhabi in 2021 was the first time the championship had been held in the Middle East. The venue itself had been built for events of this calibre, but the build-out for a FINA short-course championship required a specific layer of integration that no event in the UAE had previously needed: FINA-standard timing and results integration alongside aquatic-venue networking in an environment where the standard arena assumptions about RF behaviour and equipment placement do not all hold.
IP Care delivered the IT operation for the championship. This case study walks through what is technically different about aquatic-venue event IT, how the FINA standards layer was integrated, and what worked.
— The brief —
The brief had three primary elements. The first was the FINA-standard timing and results integration: the venue network had to support the official FINA timing system, which feeds the scoreboard, the broadcast graphics, the official results, the FINA technical jury and the international rights holders simultaneously, with the kind of timing discipline that competitive swimming demands. The second was the broadcast LAN — international rights-holder coverage in a venue configured for aquatic sport, with multiple production positions around a competition pool plus the standard arena positions for the medal ceremonies and ancillary events. The third was attendee WiFi, hospitality connectivity, press centre LAN and the venue CCTV layer integrated with venue command and ADMCC standards.
Layered on top was the championship-week schedule itself: a six-day competition window with multiple sessions per day, race blocks running on tight schedules, and FINA technical-jury and athletics-federation stakeholder co-ordination running continuously through the championship.
— What is technically different about aquatic-venue IT —
Three things separate aquatic-venue IT from standard arena IT.
The first is the RF environment. A competition pool is approximately 50 metres long, surrounded by spectator seating, with substantial water surface acting as a partial RF absorber and the surrounding pool deck creating reflection paths that do not exist in a dry arena. The pool itself shifts the RF picture relative to the arena baseline — the WiFi coverage plan around the pool deck requires more attention to cell sizing, directional antenna placement and propagation modelling than a dry-floor arena event of comparable attendee density.
The second is the environmental envelope. Aquatic venues carry persistent high humidity, residual chlorine in the air around the pool deck, and a wash-down regime for surfaces near the water that is different from the corresponding maintenance regime in a dry arena. Network equipment placed in or near the pool deck has to be rated for the environment; cable routing has to avoid the wash-down zones; equipment enclosures have to accept persistent humidity without degraded reliability. None of this is unusual for purpose-built aquatic facilities. It is unusual for a multi-purpose arena temporarily configured for aquatic championship use.
The third is the timing system integration. FINA timing is a specific stack — touchpads at the wall, integrated start signal, integrated lane judging, integrated results processing — and the venue network has to carry the timing-system traffic with the appropriate latency budget and integration into the broadcast graphics and the official results. The FINA technical jury sees the same authoritative timing source as the broadcast graphics, the scoreboard and the official record. Getting that operating to FINA standard inside a venue configured for the championship is a workstream comparable in effort to the NBA timing-system integration.
— Architecture —
The build at Etihad Arena for the championship was layered on top of the existing arena network. Per-championship additions included: aquatic-venue WiFi 6 coverage around the pool deck with environmental-rated APs and conservative cell sizing relative to standard arena event coverage; a FINA-spec timing and results network connecting touchpad systems, lane judging, start signal, scoreboard control and the broadcast graphics integration; a press centre LAN with broadcast-grade uplinks for the international press contingent; a broadcast LAN feeding international rights holders covering the championship; integration with the FINA technical jury and event-management workflows; and a CCTV layer integrated with venue command and ADMCC retention standards.
— The kit —
Approximately 100 HPE Aruba WiFi 6 access points across the bowl, pool deck, concourses and hospitality, with the pool-deck installations using environmental-rated enclosures and conservative cell sizing. A redundant Aruba CX 8325 switching core. An active-passive Palo Alto firewall pair. A Cisco Catalyst 9500-class broadcast LAN physically segmented from every other network. A dedicated FINA timing-system integration network with the timing-system vendor’s equipment running across our managed switching plant. Press centre LAN with broadcast-grade uplinks. Event CCTV layer with venue command integration. The NOC ran continuous for the six-day competition window with the SOC co-located on the standard model.
— The numbers —
A six-day competition window. Multiple sessions per day with tight inter-race timing. Approximately 100 fan-facing access points across the venue. A FINA-spec timing and results network operating continuously through the competition. Zero broadcast-impacting or timing-impacting incidents during competition sessions. A handful of low-severity findings across the championship window, every one of them inside the SLA window for resolution. The first FINA World Swimming Championship in the Middle East delivered on schedule against the FINA technical envelope.
— Operational rhythm —
Aquatic championship rhythm follows the competition schedule. Race blocks run in tight sequence — multiple races per session, sessions running morning and evening across the six days, with finals stacked across the back end of the competition window. The IT operation has to be in full monitoring posture for every race block, with no flex window for in-session technical recovery on the timing or broadcast networks.
Pre-championship validation was four days. Day minus four: full integration test across all networks. Day minus three: FINA technical-jury walkthrough with sign-off on timing-system integration. Day minus two: international rights-holder broadcast handshake. Day minus one: dress rehearsal of every category of incident response with the on-site team and remote NOC running drills end-to-end. Competition day one through six: continuous monitoring with bridge cadence calibrated to the race-block schedule.
— The hardest moments —
The hardest moment was a transient finding on the pool-deck WiFi during the second day of competition — sustained throughput in one section of the pool deck briefly dropped below design tolerance during a peak press-attendance session. The root cause was a propagation deviation around a temporary press position that had been added overnight in a slightly different layout than rehearsed. The on-site engineering team adjusted antenna placement during the inter-session window between morning and evening sessions, restored the design throughput, and the issue did not recur. The lesson — temporary changes to press-position layouts during the championship need same-day RF re-validation — is now standard practice.
The timing-system integration ran cleanly through every race block of the championship. The broadcast LAN held for every international rights-holder feed. The press centre LAN absorbed the international press contingent without finding. By the operational measures that matter, the championship was an uneventful IT delivery against a demanding standards envelope.
— What works —
Environmental rating from day one of the build. Network equipment placed in or near the pool deck for aquatic events has to be rated for the humidity and chlorine environment from the outset, not retrofitted. The cost premium is modest; the avoided reliability cost is significant over a six-day championship window.
Conservative cell sizing around the pool. Standard arena RF coverage plans do not transfer directly to aquatic-venue coverage. Pool-deck cells should be smaller, antenna placement more deliberate, and the predictive model validated more carefully on site than for a comparable arena event. The 2021 build did this and the only RF finding of the championship was traceable to a temporary press-position change, not to the design coverage plan.
Continuous FINA technical-jury integration. The timing-system integration is not a one-shot pre-championship sign-off — it is a continuous integration that the FINA technical jury observes through the competition. Treating the timing-system integration as a continuous engagement with the jury, not a transactional pre-event handshake, is what produces a clean competition.
— What we would change for a future aquatic championship —
Pre-stage a full additional pool-deck WiFi coverage pod for the highest-attendance press positions, rather than relying on adjusting existing cells to absorb late-stage position changes. The cost is modest; the avoided inter-session adjustment is meaningful.
Move the press centre LAN to a slightly higher capacity baseline. The press contingent for an international aquatic championship sustains higher per-position bandwidth than the equivalent contingent at an arena sporting event, and the current build was adequate but not generous.
— Why this matters —
Aquatic-venue event IT is a niche capability inside the broader event-IT discipline. Most arena-IT specialists do not have the environmental-rated equipment pipeline, the pool-deck RF coverage experience or the FINA timing-system integration history. The 2021 championship was the first FINA event of this calibre in the Middle East, and the operational lessons compounded into the runbook for any future aquatic championship work in the region.
For federations and event organisers planning aquatic championship work, the lesson is that aquatic-venue IT is materially different from arena IT and should be treated as a distinct technical envelope. The right partner has aquatic-environment experience in the equipment specification, the RF coverage plan and the timing-system integration. The standard arena-IT operator can deliver attendee WiFi and broadcast LAN to championship standard; the aquatic-venue specifics are where the engagement either runs cleanly or finds the gaps.