Ya Salam is the annual concert series that runs on Yas Island in the days immediately following the Abu Dhabi Grand Prix. The format is distinctive in two ways: A-list global artists rotated year-over-year, and a scheduling envelope that begins the day the Formula 1 paddock starts breaking down. The concert venue and the post-race venue are not always the same site, but they sit inside the same operating perimeter on the same island, and the IT infrastructure has to land cleanly inside a venue that, hours earlier, was running at full Formula 1 race-week tempo.
IP Care has delivered the IT operation for the Ya Salam series for six consecutive years from 2019 through 2024. It is the longest-running concert engagement in our portfolio. This case study walks through how the operation has matured across the run, what has changed as the Yas Island event infrastructure itself has evolved, and what the F1-adjacent operating context adds that no other concert engagement in the region carries.
— What is distinctive about Ya Salam IT —
Three things separate the Ya Salam engagement from other large-scale outdoor concert work in the region.
The first is the F1-adjacent operating window. The Abu Dhabi Grand Prix occupies Yas Island at maximum operating intensity in the days leading up to and including race weekend. The Ya Salam concerts follow within a tight window — sometimes the same evening, sometimes the following days. The venue infrastructure available for the concert build cannot be assumed to be in its quiet-week state. Power feeds, RF spectrum, vehicular access, security perimeter co-ordination — all of these are operating against the F1 footprint until the moment the concert build needs them. The operational sequencing between the F1 teardown and the concert build is the single biggest difference between Ya Salam and any other concert we deliver.
The second is the A-list artist rotation. Each Ya Salam year brings a different headline artist with a different production rig, different technical rider, different stage configuration and different requirements layered on top of the venue baseline. The architecture has to be flexible enough to absorb the year-on-year variation in artist-side requirements without rebuilding the venue-side infrastructure each year. The maturity of that flexible-baseline-plus-artist-overlay model is one of the things the six-year run has produced.
The third is the venue evolution. Across 2019–2024 the Yas Island event infrastructure itself has changed substantially. The Yas Bay precinct opened. Etihad Arena went live. The outdoor concert venue infrastructure around Etihad Park has matured. The Ya Salam build has therefore adapted year-over-year not only to artist-side variation but also to a venue baseline that has itself been evolving. The engagement has been a useful window into how venue infrastructure changes get absorbed into recurring event operations.
— Evolution across the years —
The 2019 edition set the architectural template — outdoor concert WiFi for an audience in the tens of thousands, broadcast LAN for the regional rights-holder coverage, CCTV integrated with venue command and the standard concert-night security operations centre. The 2020 and 2021 editions adapted that template to the pandemic operating context, with substantially reduced in-person attendance, expanded broadcast and digital reach, and the additional layer of pandemic-era access control and health-screening integration that ran through every UAE event during those years.
The 2022 edition was the first back-to-normal scale after the pandemic, with the additional dimension that the Yas Bay precinct had opened in the intervening period and the venue baseline itself was richer. The 2023 and 2024 editions consolidated this — the artist productions were larger, the broadcast presence was richer, and the venue-side infrastructure available for the concert build was meaningfully better than at any earlier edition.
Across the six years, the architectural pattern has been: a stable venue-side baseline carried forward and refined year-over-year, plus an artist-specific overlay rebuilt each edition to match the headline artist’s production rig. The venue-side baseline benefits from continuity; the artist-side overlay benefits from a flexible template that can absorb wide variation in production rider requirements.
— Architecture —
The current build at Etihad Park / Yas Bay for a Ya Salam edition includes: outdoor concert-grade WiFi 6 coverage across the audience field, hospitality, back-of-house, broadcast positions and the front-of-house mix area; a Cisco Catalyst 9500-class production LAN feeding the artist’s production rig and the regional broadcast partners; multiple Cambium and Ubiquiti point-to-point microwave links for uplink redundancy and back-of-field production positions; RFID wristband entry backhaul; outdoor-rated CCTV layer integrated with venue command and ADMCC standards; and the standard concert-night SOC running for the event window.
The artist-side overlay is rebuilt per edition against the visiting artist’s technical rider — production-LAN segments for mix, monitor, lighting, video and stage control, additional connectivity for guest-artist or supporting-act positions, and any artist-specific integration layered on top of the venue-side baseline.
— The kit —
A typical Ya Salam edition build at the current scale includes approximately 130 outdoor-rated HPE Aruba WiFi 6 access points; a redundant Aruba CX 8325 switching core; an active-passive Palo Alto firewall pair; a Cisco Catalyst 9500-class production LAN; multiple PtP microwave links for redundant backhaul; RFID wristband backhaul; outdoor CCTV layer; and a portable broadcast rack feeding the regional broadcast partners.
— The numbers —
Six consecutive editions across 2019 through 2024. Peak attendance approximately 30,000-plus per concert night at the post-pandemic editions. A peak concurrent device count north of 40,000 once production crew, broadcast, security and back-of-house are factored in. Zero show-impacting incidents across the six-year run on the production LAN. A small number of low-severity findings across the six editions, every one of them inside the SLA window for resolution.
— The operational rhythm —
Ya Salam operational rhythm is shaped by the F1-adjacent window. The venue handover from the F1 footprint to the concert build is the critical sequencing decision of every edition. Where the F1 weekend ends Sunday evening, the Ya Salam build may need to begin Monday morning, with the concert running Wednesday or Thursday. The build window is therefore typically 48 to 72 hours — compressed even by event-IT standards.
Pre-event sequence: F1 venue teardown coordination → concert build kick-off → 24 hours of physical infrastructure deployment → 12 to 18 hours of network commissioning → final integration test → dress rehearsal → hard validation freeze before doors. The compressed window leaves little slack for incident remediation, which is why the operating model leans heavily on continuity — pre-tested kit, pre-tested PtP paths, documented runbooks and a team that has run this exact engagement five times before.
Show-night cadence follows the standard outdoor-concert model: hard validation freeze at T-2 hours, monitoring posture through doors, continuous monitoring through the run-of-show, no-change exception-only after doors open.
— What the six-year continuity has produced —
The architectural pattern is now mature. The venue-side baseline is documented, validated and reproducible. The PtP backhaul paths around the Yas Bay precinct are surveyed and have been tested multiple times in production conditions. The RFID wristband backhaul integration is template-driven against the typical entry-system vendor stack. The broadcast LAN handshake with the regional rights holders has institutional history. The relationship with the venue management team, the F1 operations team, ADMCC and TDRA has six years of operating history rather than starting from scratch.
The artist-side overlay is the variable component, and the operating discipline around the overlay has also matured. The pre-edition cycle now begins with the artist’s technical rider mapped against the venue-side baseline, with the gaps identified explicitly and the overlay build scoped against those gaps. By the time the visiting artist’s production team arrives on site, the venue-side infrastructure is operating and the artist-side integration drops into a known-clean foundation.
— The hardest moments across the years —
The hardest single moment was in one of the earlier editions, when an F1-side teardown delay compressed the concert build window beyond what the build plan had assumed. The team absorbed the compression by running the network commissioning in parallel with parts of the physical build that traditionally come first — a sequencing departure that worked but raised the operational tension materially. The lesson — every edition should explicitly model a worst-case F1-teardown delay and have a pre-validated compressed-window build sequence ready — went into the runbook and has informed every subsequent edition.
The second hardest pattern across the years has been the artist-side variation. Some visiting productions arrive with rider requirements that exceed the typical Ya Salam baseline by a substantial margin, and the artist-side overlay build window has occasionally been tighter than ideal. The current operating model handles this by maintaining a contingency pack of artist-side overlay equipment — additional production-LAN segments, additional networking, additional uplink capacity — pre-staged at the venue rather than ordered in for the specific rider.
— What works —
Continuity. Six years of the same team running the same engagement against an evolving venue baseline and a rotating artist lineup is the single biggest contributor to the engagement’s operational profile. Engineers who have run the F1-to-concert teardown sequence multiple times handle the compressed window differently from engineers seeing it for the first time.
A flexible venue-side baseline plus a rebuildable artist-side overlay. The architectural pattern is the model. The venue-side baseline benefits from continuity and refinement; the artist-side overlay benefits from a template-driven flexibility that can absorb wide variation without redesign.
Pre-staged contingency for both the F1-teardown compression scenario and the artist-side rider expansion scenario. Both have happened across the six years; both are now planned for explicitly rather than treated as risks.
Co-located NOC and SOC. The standard concert-night security model, brought into Ya Salam in its inaugural edition and refined across the six years.
— What we would change for the seventh edition —
Move parts of the venue-side baseline to a continuously operated footprint between editions. The Yas Bay precinct now hosts enough year-round events that the venue-side infrastructure does not need to be torn down and rebuilt each Ya Salam edition; the cumulative readiness for the next edition would be materially better with a sustained baseline.
Pre-engineer a worst-case-compressed-window build sequence explicitly into the runbook rather than as contingency. The F1-teardown variability is a recurring feature, not an edge case.
Extend the artist-side overlay template to cover a wider range of contemporary touring production riders, particularly the newer wave of integrated wearable / RFID / interactive show elements that have become more common since the Coldplay residency.
— Why this matters —
Recurring concert series at this duration and scale are unusual in the region. Most concert engagements are single-tour-stop or short-series events. Ya Salam at six years is the most operationally mature concert engagement in our portfolio and demonstrates what the recurring-engagement model produces in the concert category — much like the UFC engagement demonstrates the same pattern in combat sports and the NBA engagement demonstrates it in league-standards sports.
For promoters and venue operators planning long-running concert series, the lesson is consistent with what every other long-running engagement in our portfolio has produced: vendor continuity is a strategic decision, the venue-side baseline matures across editions, and the operational tempo gets calmer with each successive year of continuity. The seventh Ya Salam will be operationally calmer than the first, for the same reasons.