WEA and IPAWS are two of the most frequently used acronyms in emergency management; and although most emergency managers have a good idea about what the acronyms stand for, not all understand the relationship between the two systems or how they can be integrated with other mass emergency notification systems.
Mass emergency communications started more than two thousand years ago when Chinese soldiers lit fires and sent smoke signals along the Great Wall of China to warn soldiers in neighboring towers of invaders. Methods of communication have evolved over the centuries and now most people receive mass emergency communications on their mobile devices via Wireless Emergency Alerts.
The Wireless Emergency Alert (WEA) service went live in 2012 – enabling alerting authorities to send geo-targeted text alerts to the public via commercial wireless carriers (AT&T, Verizon, etc.). Geo-targeted messages can be used to warn the public in specific geographic areas of national emergencies, imminent natural or human-made threats, public safety issues, or missing children.
Unlike SMS text messages which need to locate each recipient individually, wireless emergency text alerts reach all cellphone/smartphone users who are receiving a signal from a targeted cell tower. Because wireless emergency text alerts don’t have to go through so many processes, the service works when cellphone networks are overloaded.
The Integrated Public Alert and Warning System (IPAWS)
Although WEA can be used as a standalone mass emergency communication service, its coverage is limited to members of the public with a WEA-compatible cellphone/smartphone, who have their phone with them at the time of an alert, and who haven’t disabled the emergency alert feature. The risk therefore exists some people may be unaware that a threat or public safety issue exists.
To mitigate this risk, the Federal Emergency Management Agent (FEMA) developed the Integrated Public Alert and Warning System (IPAWS) – a system through which alerting authorities can send alerts via the WEA service, the Emergency Alert System (EAS) for radio and TV stations, the National Oceanic and Atmospheric Administration (NOAA) weather radio service, Internet-based services, and unique state and local alert systems.
The effectiveness of the IPAWS system is dependent on alerting authorities using software compatible with the Common Alerting Protocol (CAP) to push alerts through the IPAWS Gateway. Receiving Internet-based services (i.e., desktop alerts, IoT devices, etc.), and unique state and local alert systems (i.e., PA systems, roadside digital signage, etc.) must also be CAP compatible, while EAS disseminators must convert CAP messages into a Specific Area Message Encoding (SAME) format to ensure a backup communication channel exists if the Internet is unavailable.
Shortcomings of the WEA and IPAWS Systems – and How to Overcome Them
While the WEA and IPAWS systems look good on paper, both have shortcomings. As already explained, in order for the IPAWS system to be fully effective, messages must be sent and received via CAP compatible software. Further shortcomings include that neither system supports two-way communication, while the only supported languages are English and Spanish. In many jurisdictions there are large communities that speak neither language.
The best way to overcome these shortcomings is by adding a messaging platform to the IPAWS infrastructure after the IPAWS gateway. The platform would ideally be CAP compatible in order to receive and disseminate messages from IPAWS alerting authorities, but would also have the capabilities to disseminate messages to mobile devices and Internet-based services beyond the normal IPAWS channels. So, for example, alerts could be sent via social media channels.
With regards to supporting two-way communication, mass notification platforms such as Rave Alert do not require additional configuration to receive replies from recipients of alert notifications. For alerting authorities, this means situational awareness in emergency situations can be substantially improved, enabling a more effective response. Additionally, the auto-translate capabilities of the Rave Alert platform ensure ethnic communities are equally well informed of an emergency or threat.
Rave Alert is Not Just for FEMA Alerting Authorities
According to the latest list of alerting authorities, around half the country’s emergency management agencies are authorized by FEMA to send messages through the IPAWS system. In the remaining areas, there is an increased likelihood the public may not receive timely warnings of imminent threats or public safety issues. It will largely depend on what alternatives each emergency management agency has in place to warn communities of imminent danger.
While implementing the Rave Alert platform will not qualify a non-authorized emergency management agency as a FEMA alerting authority, it will enable the non-authorized agency to send geo-targeted alerts via SMS text, email, RSS, desktop alerts, social media, Alertus-compatible devices, and CAP-compatible services to citizens of all ethnicities, and with the capability to receive replies and engage in two-way conversations.
It should be noted that Rave Alert is IPAWS-OPEN in as much as the platform receives, authenticates, and disseminates messages transmitted by alerting authorities. This means that if Area A is protected by a non-authorized emergency management agency, and the adjacent Area B is protected by a FEMA alerting authority, citizens of both Areas A and B will be able to receive timely warnings of imminent threats and public safety issues relevant to their area via the Rave platform.
In addition, non-governmental organizations can also take advantage of the Rave platform to disseminate government alerts in order to enhance their existing emergency communications. Therefore, irrespective of whether your public safety role is in a FEMA alerting authority, a non-authorized agency, a business, a school, or a healthcare facility, we invite you to get in touch and request a demo.
Comments are closed here.