IF YOU COULD GIVE ONE DON'T AND ONE MUST-DO FOR AN EVENT OF THIS SCALE, WHAT WOULD THEY BE?
At the server level, an N+1 approach is often adopted, with a limited number of spare channels relative to the number of inputs. Even when handling hundreds of inputs, only a small number of backup channels may be provisioned. This reflects the level of reliability expected from such systems. The likelihood of failure is considered low enough that extensive redundancy is not always required. With distribution, resilience depends on the delivery method, whether SRT, JPEG XS or file- and non-file-based workflows. Diverse paths remain key. More broadly, resilience varies by layer: hardware resilience is well established and consistently demonstrated, particularly in video servers, while software resilience still raises questions. Cloud infrastructure hails in a different model of resilience. While generally expected to be robust and scalable, failures, when they do occur, can be more absolute in nature. Systems can be designed with redundancy and scalability in mind, but they are dependent on underlying infrastructure, so outages may have widespread impact.
OPHIR ZARDOK: Don’t deploy new technology for the first time at the event itself. The Games is not the place for a proof of concept. Every novel workflow – whether it’s a new compression format, a cloud- based routing architecture or an AI-driven transmission system – needs to have been proven in live broadcast conditions before the Opening Ceremony. Our LIQ technology went
ARE THERE ANY COMMON COORDINATION ISSUES BETWEEN BROADCASTERS AND VENDORS – AND HOW CAN THEY BE AVOIDED?
ALEX REDFERN: A stronger focus on outcomes can help reduce coordination issues. When all stakeholders are aligned on the end goal, the specific method of achieving it becomes less critical. However, established working practices can present challenges, particularly when individuals or teams are accustomed to operating in a certain way based on previous events. As a result, misalignment tends to arise more frequently around processes than outcomes, which are typically well defined – for example, delivering a file to a specific destination or transmitting a stream to a defined endpoint. Version misalignment is another common issue. Broadcasters often operate across multiple software versions within ecosystems. While this may function effectively at an individual level, it introduces complexity from a vendor perspective, particularly in
terms of support and integration. Supporting multiple versions simultaneously increases operational overhead and can create challenges when integrating systems between different broadcasters, host broadcasters and rightsholders. In some cases, differences in software versions can hinder interoperability. Coordination is further complicated by the global nature of major events. Teams are often distributed across multiple locations, including the International Broadcast Centre, regional hubs and broadcaster headquarters. So, ensuring consistent communication and information sharing across time zones presents an additional challenge. Vendors frequently act as a central point of coordination, facilitating communication between these groups. However, managing alignment across geographically dispersed teams remains a complex task, especially when operating at scale.
Powered by FlippingBook