- Common Alerting Protocol
- EAS Participant Requirements
- Encoder/Decoder CAP Conformity
- Monitoring IPAWS-OPEN
- Testing with IPAWS-OPEN
- Additional References
The Emergency Alert System (EAS) is a public alert and warning system that is supported by EAS participants, including terrestrial broadcasters, cable television systems, wireless cable systems, satellite digital audio radio service (SDARS) providers, direct broadcast satellite (DBS) services and wireline video service providers.
Common Alerting Protocol
The IPAWS Open Platforms for Emergency Networks (IPAWS-OPEN) collects Common Alerting Protocol (CAP) alerts issued by authorized public officials and distributes them to (EAS participants via an EAS CAP feed. The EAS CAP feed is available on the internet and EAS participants require an internet connection to poll IPAWS-OPEN. In addition, EAS participants may poll state CAP servers or other CAP-based networks via the internet where appropriate.
FEMA announced the adoption of Common Alerting Protocol Version 1.2 on September 30, 2010. The CAP 1.2 standard is further customized by the Common Alerting Protocol, v. 1.2 USA Integrated Public Alert and Warning System Profile Version 1.0, an Organization for the Advancement of Structured Information Standards (OASIS) Technical Committee Specification. The IPAWS Profile ensures that CAP data will be compatible with U.S. channels for alert distribution, including the EAS.
Common Alert Protocol-based networks do not replace traditional, over-the-air methods of monitoring EAS tones; instead, they supplement those sources and provide additional redundancy. Likewise, CAP does not replace the existing EAS protocol, compatible with the National Weather Service’s Weather Radio Specific Area Message Encoding (SAME). EAS participants will use CAP-based equipment to translate CAP messages to the EAS protocol and message format. CAP-based equipment consists of stand-alone converters, firmware upgrades to existing encoders/decoders, or newer encoder/decoder models with CAP fully integrated.
CAP-based equipment converts CAP to EAS/SAME protocol using a set of recommendations developed by the EAS CAP Industry Group (ECIG). See the ECIG Recommendations for a CAP EAS Implementation Guide for specific details.
Benefits of CAP
- CAP alerts are transmitted in digital format; therefore, there is no degradation of quality of the content that may be experienced with analog methods such as radio.
- CAP alerts can be directly available to encoder/decoder equipment within seconds of their creation; therefore, delays or disruptions relating to station-to-station, over-the-air relay are reduced.
- The internet infrastructure has a high level of redundancy and reliability, and may survive when other channels of communication do not.
- In addition to EAS-required data, CAP alerts may carry rich information such as audio, video, geographical-location data, etc., that EAS participants may opt to use for supplemental information to provide to their audiences.
EAS Participant Requirements
The Federal Communications Commission’s (FCC) Second Report and Order requires EAS participants to “accept CAP-based alerts” within 180 days of CAP adoption by FEMA. A subsequent FCC waiver extended the deadline an additional 180 days, to September 30, 2011. The Fourth Report and Order further extended the deadline to June 30, 2012.
During January 2012, the FCC announced its Fifth Report and Order to clarify FCC rules relating to CAP implementation. Among the provisions is a new requirement for EAS participants’ EAS equipment to interface with IPAWS to enable the distribution of CAP-formatted alert messages from the IPAWS system. As EAS rules and the CAP standard evolve over time, IPAWS will be updated to accommodate new requirements.
Encoder/Decoder CAP Conformity
To support EAS participants in their selection of CAP-capable encoder/decoder equipment, the IPAWS Conformity Assessment Program tested voluntarily submitted equipment for conformance to CAP 1.2, the IPAWS CAP Profile, and the Emergency Alert System Common Alerting Protocol Industry Group (ECIG). Manufacturers whose equipment successfully passed conformity testing may reference this fact through a Supplier’s Declaration of Conformity (SDoC) posted on the Responder Knowledge Base Website (select “IPAWS SDoCs”).
FEMA published the Integrated Public Alert and Warning System (IPAWS) Guide for Independent Testing of Emergency Alert System Equipment to describe testing requirements for any Independent Testing Authority (ITA) who wishes to provide testing services for the manufacturers of EAS decoder equipment for purposes of meeting FCC equipment certification requirements.
Private sector manufacturers and system developers may continue to submit their products to the Supporting Technology Evaluation Program (STEP) for conformance testing. See the Preparedness-Technology, Analysis, and Coordination (P-TAC) Center Website for additional information.
The IPAWS Program Management Office (PMO) released the information necessary to allow CAP compatible EAS equipment to poll the IPAWS-OPEN system. Once equipment manufacturers update and release their firmware for this new system, EAS participants will be able to enter the following URL, https://apps.fema.gov/ into encoder/decoder devices. However, please note that CAP-compatible EAS equipment manufacturers must first provide firmware updates before message polling will work. EAS participants should check their equipment manufacturer’s web sites for information on when these software updates will be available.
Testing with IPAWS-OPEN
Beginning December 12, 2011, FEMA began generating, processing and serving one CAP message per week per each of nine local U.S. time zones. This CAP message consists of a Required Weekly Test (RWT) message directed to all states and is issued at 11:00 AM local time each Monday. (For purposes of these exercises, states divided into two time zones are assigned to the time zone that includes the largest area within the state.) These log-only RWT messages will serve as non-disruptive internal test messages to provide EAS participants with the opportunity to verify configuration and message connections.