|
 |
| |
| |
| |
Web-based activation of EAS from any network-connected workstation within the Emergency Operations Center or from a remote location |
| |
Authenticated and secure Web-based access to multiple operators. The system includes permission management that defines which specific system operators have EAS activation rights |
| |
Preprogrammed selection of EAS scenarios and audio messages that can be distributed as-is or quickly tailored |
| |
Integrated text-to-speech capability which converts text messages to broadcast audio |
| |
Ability to target broadcasters by geographical regions |
| |
Audit trail of all activations with details including operator, time stamp, scenario activated and more |
| |
Delivery of EAS messages over the IP network, including the public Internet, to the EAS ENDEC (Encoder-Decoder) interface |
| |
Delivery of alerts to broadcasters, online and via print media using additional, non-EAS channels including multi-media desktop alerting that can provide audio, video and more in-depth text information to complement short EAS messages |
|
| EAS integration is achieved through the Common Alerting Protocol (CAP). IWSAlerts generates a CAP-compliant alert, and this message is then processed by CAP-compliant EAS devices that convert the CAP messages to signals that can feed into the EAS system via their standard interface – the ENDEC. With this approach, EAS messages can be communicated over IP networks to any ENDEC – whether located at the headquarters of the emergency management agency or directly to broadcasters over the public Internet. This achieves a high level of redundancy and more reliable broadcast delivery of each activated EAS message. |
| |
 |
| |
|
 |
|