FCC software-based EAS proposal targets hardware replacement for broadcast stations

Transitioning to software-based alerting allows broadcasters to move away from legacy hardware that faces increasing supply chain constraints and repair backlogs. By enabling automatic failover to backup software instances, the industry can maintain critical communications even if physical facilities are compromised. This shift aligns with the broader migration toward IP-centric architectures, though it introduces new cybersecurity burdens and requires a complete overhaul of the FCC's current equipment certification framework. The exclusion of cloud-based solutions highlights ongoing regulatory concerns regarding the resilience of commercial IP networks during widespread power outages. Watch for the August 31 comment deadline to see if the NAB or SBE pushes for cloud-based flexibility.

The Emergency Alert System ecosystem is already shifting toward software-defined architectures even before the FCC's formal rulemaking concludes. Digital Alert Systems, one of the two dominant EAS equipment manufacturers alongside Sage Alerting Systems, has been actively positioning its DASDEC platform for IP-centric alerting workflows. The company released v5.2 software for its DASDEC and One-Net emergency messaging devices, adding FCC compliance features and enhanced security capabilities including mandatory Triggered CAP Polling and predefined national alert message generation. The Society of Broadcast Engineers has supported the NAB's push for software-based EAS, arguing that aging hardware encoders create single points of failure that software redundancy can eliminate.

On the regulatory and business side, Digital Alert Systems has taken a notably adversarial stance against the very software-based EAS transition the FCC is now proposing. In a May 2025 FCC filing, DAS opposed the NAB's petition to allow software-based alerting, calling it premature and raising concerns about certification gaps, cybersecurity, and regulatory fragmentation. The company argued that without a standardized certification path, a fragmented EAS environment would undermine reliability and interoperability. The same filing supported the NAB's separate proposal to delete simulcasting rules to accelerate ATSC 3.0 NextGen TV deployment, illustrating how the EAS vendor community is selectively engaging with modernization depending on whether it threatens their hardware business model. Digital Alert Systems also filed a letter with the FCC rebutting Weigel Broadcasting's assertions about ATSC 3.0 EAS limitations, signaling active competition over how alerting integrates with next-generation broadcast standards.

Technical partnerships and cybersecurity mandates are shaping the practical path toward software-based EAS. Digital Alert Systems and Ateme announced a collaboration integrating EAS-Net device networking protocol directly into Ateme's TITAN line of SD, HD, and UHD encoders, eliminating the need for added hardware to provide full EAS text crawl and audio capabilities. This integration model demonstrates how software-based alerting can embed into existing encoder infrastructure without standalone devices. The FCC adopted new cybersecurity rules in FCC 26-38 requiring EAS participants to use passwords of at least 15 characters, with Digital Alert Systems confirming its DASDEC platform already meets the requirement. These cybersecurity mandates will apply equally to any software-based EAS solutions that emerge from the current rulemaking, establishing a baseline security posture before the certification framework is even defined.