Broadcast equipment has a long lifespan. Many studios still run MOS-enabled devices purchased a decade ago. Graphics engines, playout servers, teleprompters, and automation equipment often rely heavily on MOS compatibility. But editorial workflows are rapidly moving to the cloud.
This creates a key challenge:
How can modern cloud-based rundown systems integrate seamlessly with older MOS-based devices?
MOS was originally designed for on-prem NRCS systems like iNews and ENPS. These systems communicated with devices over local networks. Cloud systems, however, operate over the internet, lacking direct access to local equipment.
This is solved with MOS gateways. A MOS gateway sits inside the studio network and communicates with cloud-based rundown software through secure APIs or WebSocket tunnels. It then relays MOS messages locally to equipment like graphics engines or playout servers.
This hybrid model works extremely well. Producers work in a cloud-native rundown system like Falcon Rundown. When they update the rundown, the cloud system sends a message to the gateway. The gateway translates this into MOS messages that devices can understand.
This allows studios to retain existing equipment while modernizing editorial workflows.
MOS also supports bidirectional communication. If a graphics operator updates a template or associate a new media object, the MOS gateway can send updates back to the cloud. This keeps everything in sync.
Another important concept is rundown locking. During a show, the gateway ensures MOS devices do not fall out of sync if a producer updates a running story. MOS uses “rundown story IDs” to tie updates to specific elements.
As cloud systems grow, MOS remains essential. Even newer tools that do not strictly require MOS often provide it as an optional integration, because the broadcast world still depends heavily on MOS-compatible hardware.
Falcon Rundown’s architecture is designed to support MOS integration through lightweight gateways, making it ideal for hybrid setups.