When the NBA chose Abu Dhabi for its first preseason games outside North America, the operational expectations followed the league with them. The IT operation around an NBA preseason matchup is not improvised; it is the same league-mandated stack of broadcast, analytics, statistics, scoreboard, IPTV and venue connectivity that runs in every NBA arena, deployed temporarily into a non-NBA venue for the event window.
For the host venue — Etihad Arena — that meant an IT engagement layered on top of the standard arena operation that had to satisfy NBA technical operations, ESPN and the international broadcast partners, the Abu Dhabi Sports Council, the venue management team and the regulators concurrently. IP Care has been the IT partner across every edition from 2022 through 2025, and this case study walks through how that engagement has evolved.
— The brief, year one —
The 2022 edition was the first NBA preseason games outside North America. The brief was straightforward in scope and exacting in standards: deliver the IT infrastructure to host two NBA-grade preseason games to NBA technical-operations standards, in an arena that had hosted basketball before but not at this regulatory and broadcast level.
The NBA technical operations team arrives with a detailed standards document covering everything from network segmentation and broadcast LAN topology through to specific IP plan requirements, NTP source priorities, latency budgets between scoreboard control and the live broadcast feed, and the way statistics traffic and timing system traffic must be carried separately from general venue networking. The host IT operation has to build the infrastructure that meets every line of that standards document in a venue that is not natively NBA-configured.
— What was different about year one —
Three things drove the operational complexity in 2022 above what a typical international basketball event would have demanded. The first was the broadcast scale: ESPN deployed a full North American broadcast crew with the same equipment stack they would deploy for any NBA preseason game in the United States, which meant the production LAN had to accept and pass traffic types we had not previously run for any other event in the UAE.
The second was the timing-system integration. NBA games run on a precise integrated timing stack feeding the scoreboard, the game clock, the shot clock, the foul indicators, the broadcast crew, the statistical operators and the league office in real time. Every one of those clients has to see the same authoritative time source within tight tolerances. Getting that operating to NBA standard inside a venue that was not natively wired for it was the single longest workstream of the year-one build.
The third was the league office integration. NBA games run with continuous, two-way data exchange between the venue and the league office in New York — for statistics, video review, replay, officiating support and post-game data ingestion. The venue network has to provide reliable, low-latency, secure transit for that traffic for the full event window, and the integration is tested and signed off well in advance.
— Architecture —
The build at Etihad Arena for an NBA Abu Dhabi event is layered on top of the existing arena network footprint. Per-event additions include: an NBA-spec broadcast LAN built around Cisco Catalyst 9500-series switches and physically separate from the venue’s permanent broadcast plant; an integrated timing-system network connecting scoreboard control, game-clock, shot-clock, statistics positions and the league-office uplink; high-density WiFi 6E coverage across the bowl, sidelines, media positions and hospitality; a dedicated press centre LAN with broadcast-grade uplinks for North American and international rights-holder crews; and a CCTV layer integrated with venue command and ADMCC standards.
Underneath it all, the venue NOC for the event window is staffed by IP Care engineers running a unified dashboard across the arena network, the NBA-spec broadcast LAN and the security operations centre. The NBA technical operations team has read-access into the dashboard from their on-site position and from their league-office NOC, which has been a recurring requirement and is now a standard part of the build.
— The numbers —
Four consecutive editions (2022, 2023, 2024, 2025). 15,000-plus spectators per game in the Etihad Arena bowl. Two games per edition over two consecutive nights, plus rehearsal day. A peak concurrent device count north of 22,000 across an event night with the broadcast crew, statistics positions and back-of-house factored in. Zero broadcast-impacting incidents across the four-year run. Zero timing-system or statistics-feed failures during live game time across the four editions. A handful of low-severity findings across the years, every one of them inside the SLA window.
— Operational rhythm —
NBA events run on a tighter pre-event cycle than tournament or concert work because the league standards demand it. Day minus three: NBA technical operations team arrives, walkthroughs begin. Day minus two: full broadcast LAN handshake with ESPN production, timing-system integration testing, statistics dry run. Day minus one: open practice with the production stack live, dress rehearsal of every game-night workflow, league-office data exchange validation. Game day one: standard arena operations from doors to final buzzer, with the NOC and SOC running the unified bridge cadence. Game day two: same model, with overnight remediation of any minor findings from game one.
Post-event: 90-minute hot wash with the NBA technical operations lead on site, formal report within five working days into the league-office documentation set, action items into the runbook for the following year.
— Year-on-year evolution —
The 2022 build was substantially heavier on initial design and validation effort than every subsequent year. By 2023 we had a documented runbook covering every workstream from spectrum coordination through timing-system test plans, and the team running the build was largely the same as 2022 — which materially shortened the design phase.
The 2024 edition introduced an upgraded broadcast LAN core to support higher-resolution broadcast feeds and improved redundancy on the league-office uplink. The 2025 edition added a more sophisticated SOC posture with continuous monitoring across the broader Etihad Arena footprint outside the immediate event window.
The shape of the engagement has changed each year. The operating model has not. Same team, same runbook structure, same venue relationships, same regulators — same predictability, which is what the NBA technical operations side has consistently asked for and what continuity has delivered.
— The hardest moments —
Year one had three. The first was the timing-system integration, which took longer than the build plan allowed because the venue was not natively wired for the level of clock-source coordination NBA standards required. We closed the gap with additional cabling and a hardened time-source design over two long days during the build window, and it has been a standard part of the build template ever since.
The second was a brief broadcast-LAN segmentation issue 36 hours before game one, caught by the pre-event drift scan and remediated before ESPN production needed the network. Same lesson as the FIFA broadcast LAN finding — version-controlled configurations and twice-run drift scans now standard.
The third was a press-centre WiFi capacity issue in the year-one event window that we did not anticipate at the density NBA-international broadcast crews actually produce. The 2023 build doubled the press-centre AP density and the issue has not recurred.
Years two through four have been operationally calmer, which is the trajectory the continuity model is designed to produce.
— What works —
The same continuity points as the UFC engagement apply, with some NBA-specific additions.
A documented integration with NBA technical operations standards. The first year required interpreting the standards document and translating it into a venue-specific build. Every year since has executed against a documented template that has already passed an NBA technical operations sign-off, which is a substantial accelerator.
A near-permanent timing-system integration. The hardest part of year one is now standing infrastructure that gets re-validated rather than rebuilt. The cost savings to the host accrue from year two onwards.
League-office integration as a routine. The data exchange between the venue and the New York league office is now a tested, signed-off interface that drops into place without bespoke engineering each year.
Two consecutive game nights instead of one. NBA Abu Dhabi runs as a two-game series, which means the operation has to deliver the full game-day stack twice in 48 hours. The model is engineered for it and the second night runs more smoothly than the first because the team has data from the first night to refine on.
— What we would change for the next edition —
Extend the SOC monitoring further upstream into the venue’s carrier connectivity, so that brief carrier-side anomalies — the kind that have not affected gameplay but have appeared on our edge dashboards — are observable in advance rather than at the edge.
Move to a fully sustained timing-system footprint between editions, so that the timing-system network is continuously validated rather than reawakened each year. The current design is more than adequate; the upgrade buys verification rather than capability.
Pre-stage spare kit for the press centre at the density needed for the most demanding broadcast cohort, rather than the mean. The cost is modest. The risk reduction is meaningful.
— Why this matters —
The NBA Abu Dhabi engagement has been an unusual demonstration of what continuity produces in event IT. Four consecutive editions, zero broadcast-impacting incidents, zero timing-system failures, an operating model that is now mature enough to execute against a documented template rather than design from scratch. The NBA technical operations team has signed off on each edition and continued to engage the same team for the next.
For host venues and event organisers planning recurring international sporting series, the value of continuity in the IT partner is the most consistent finding from this engagement. The right vendor relationship in year four is materially different from the right vendor relationship in year one, and changing it mid-programme has a measurable operational cost.