CAP Interoperability

From its inception, the Alertus System was designed with a focus on interoperability and compatability with web standards.  Alertus was one of the first companies to support version 1.1 of the Common Alert Protocol (CAP) specification and we are committed to supporting all future CAP releases.

The Alertus system can be activated by a CAP messages accessed in one of the following ways:

• Pulled from a URL
• Pushed via a HTTP post
• Pushed via the Alertus Middleware SOAP API
• Pasted and submitted into a secure web form
• Pulled from an ATOM CAP syndication feed (such as NOAA)
• Retrieved from a DMIS-OPEN COG

When the Alertus System processes a CAP file it constructs and disseminates a detailed Alertus alert notification using the core CAP fields (i.e., identifier, duration, headline, description, msgType, etc.).  However, Alertus’s adoption of CAP goes above and beyond typical vendors’ CAP support.  Users can setup and configure multiple alert profiles that are activated when CAP alerts meeting the urgency/severity/certainty criteria are received.  If the CAP alert specifies a geographic area, only devices located within the contained boundary will be activated.  Moreover, the geographic location of these alert devices can be easily managed by creating user definable rules that use flexible regular expression syntax.

The Alertus system is also compatible with FEMA's Disaster Management Interoperability Services, commonly referred to as DMIS-OPEN.  Alertus endpoints can be automatically or manually activated from CAP alerts posted to DMIS-OPEN Cogs.  For more information see FEMA's Disaster Management Website.

The latest CAP news is posted on the OASIS Emergency Management TC Website.