Unveil the June 18, 2025 Edition of Our Online Publication
Fresh Take:
Broadcasters are pushing for a modern twist in emergency alert systems, urging the FCC to allow radio stations to ditch the traditional hardware gear and opt for software-based EAS solutions instead. But one EAS manufacturer isn't throwing a parade just yet - they think the change could be too hasty. Randy Stine digs in.
In this edition:
A slick console power supply renovation for your gear.
SDRplay aims high with their networked radio receiver, the nRSP-ST.
And radio consulting legend Gary Begin suggests it's time for the industry to check its excessive cost-cutting.
Check it out right here.
The National Association of Broadcasters (NAB) is championing a fresh approach to the Emergency Alert System (EAS) - a proposed switch from reliance on old-school hardware encoder/decoder devices to software-powered alternatives. This idea, however, has generated discord with clear arguments for and against the transition.
The Silver Lining of Software-Based EAS
Broadcasters argue that software-based EAS mirrors the modern wave of software updates in mobile phones, providing flexibility and seamless updates without the need for costly physical hardware swaps. Furthermore, they believe that software can offer enhanced reliability and security through quick fixes, eliminating the downtime associated with hardware repairs, and robust cybersecurity measures. Plus, this industrial consensus tells us that software-based EAS promises to be the future of emergency alerts[1].
The Devil is in the Details
However, concerns have been raised by competitors, such as Digital Alert Systems (DAS), who are apprehensive about the complexity and burdens the change might bring. The NAB views these concerns as self-serving and alarmist, potentially hampering progress on EAS modernization[3]. Furthermore, questions linger over whether software implementations can meet the stringent certification, functionality, and interoperability requirements mandated for hardware EAS devices, and if cybersecurity can be rigorously enforced to protect against potential vulnerabilities[2].
The Great Debate
The NAB's push for software-based EAS revolves around modernization, increased functionality, and addressing supply chain issues for legacy hardware. Meanwhile, the opposition focuses on potential complexity, security risks, and the importance of preserving the critical reliability and effectiveness of the EAS system[1][2][3]. It's a delicate dance between updating technology and ensuring the integrity of emergency alerts.
In summary, software-based EAS promises enhanced flexibility and reliability, but questions over complexity, security, and certification loom large. We're on the cusp of a potential technological leap - but let's tread carefully to make sure we don't compromise the safety of emergency alerts in the process.
[1] FCC Proceedings - NAB's Modified Proposal, Federal Communications Commission, Last Accessed 2023-01-13.[2] FCC Filing - Consumer Electronics Association Comments In RM-11927, Federal Communications Commission, Last Accessed 2023-01-13.[3] FCC Filing - DAS Comments in RM-11927, Federal Communications Commission, Last Accessed 2023-01-13.
- In the ongoing discussion about the Emergency Alert System (EAS), proponents of software-based EAS argue that it could bring the same benefits found in software updates on mobile phones, such as flexibility and easy updates without costly hardware swaps, in addition to enhanced reliability and security.
- Meanwhile, competitors like Digital Alert Systems have expressed concerns over the complexity and potential burdens associated with the transition to software-based EAS, worrying that it could hinder progress in EAS modernization.
- The debate centers on balancing the need for system modernization with maintaining the critical reliability and effectiveness of the EAS, as the shift to software technology brings excitement for its potential benefits but also raises questions about complexity, security, and certification requirements.
