Common Alerting Protocol

The Common Alerting Protocol (CAP) is an XML-based data format for exchanging public warnings and emergencies between alerting technologies. CAP allows a warning message to be consistently disseminated simultaneously over many warning systems to many applications. CAP increases warning effectiveness and simplifies the task of activating a warning for responsible officials.

Individuals can receive standardized alerts from many sources and configure their applications to process and respond to the alerts as desired. Alerts from the Department of Homeland Security, the Department of the Interior's United States Geological Survey, and the Department of Commerce's National Oceanic and Atmospheric Administration (NOAA), and state and local government agencies can all be received in the same format, by the same application. That application can, for example, sound different alarms based on the information received.

By normalizing alert data across threats, jurisdictions, and warning systems, CAP also can be used to detect trends and patterns in warning activity, such as trends that might indicate an undetected hazard or hostile act. From a procedural perspective, CAP reinforces a research-based template for effective warning message content and structure.

The CAP data structure is backward-compatible with existing alert formats including the Specific Area Message Encoding (SAME) used in Weatheradio and the broadcast Emergency Alert System as well as new technology such as the Commercial Mobile Alert System (CMAS), while adding capabilities including:

Background

The National Science and Technology Council (NSTC) November 2000 report on “Effective Disaster Warnings” recommended that “a standard method should be developed to collect and relay instantaneously and automatically all types of hazard warnings and reports locally, regionally and nationally for input into a wide variety of dissemination systems”.[1]

In 2001 an international, independent group of over 120 emergency managers convened online by California emergency telecommunications expert Art Botterell began specifying and prototyping the Common Alerting Protocol data structure based on the recommendations of the NSTC report. The project was embraced by the non-profit Partnership for Public Warning and a number of international warning system vendors.[2] A series of field trials and long-term demonstration projects during 2002-03 led to the submission of a draft CAP specification to the OASIS standards process for formalization.

The CAP 1.0 specification was approved by OASIS in April 2004. Based on experience with CAP 1.0, the OASIS Emergency Management Technical Committee adopted an updated CAP 1.1 specification in October 2005.[3][4] At a meeting in Geneva in October 2006 the CAP 1.1 specification was taken under consideration by the International Telecommunications Union for adoption as an ITU recommendation.

The latest CAP specification version 1.2 is available since July 2010 at the OASIS Web site.[5]

Implementations

United States

According to a CAP 1.0 Fact Sheet,[6] CAP implementations have been demonstrated by agencies and companies including: United States Department of Homeland Security; National Weather Service; United States Geological Survey; California Office of Emergency Services;[7] Virginia Department of Transportation; NDS, Ltd.; GeoDecisions, Inc.; Blue292; Warning Systems, Inc.; Comlabs, Inc.; mobileFoundations; Ship Analytics; AlertSense (formerly MyStateUSA); IEM, Inc.; Hormann America, Inc.; Oregon RAINS; Alerting Solutions, Inc. and others.

It is also mentioned by the Internet Society in its 2005 "Public Warning Network Challenge".[8]

In early 2005, the U.S. Department of Homeland Security (DHS), in partnership with the Association of Public Television Stations,[9] demonstrated CAP-based "digital EAS" broadcasts over public television digital TV transmitters and satellite links in the Washington, D.C. area and nationwide.

CAP is the foundation technology for the planned "Integrated Public Alert and Warning System", an all-hazard, all-media national warning architecture being developed by DHS, the National Weather Service within NOAA, and the Federal Communications Commission.[10]

Canada

In Canada, a working group composed of public alerting practitioners and government agencies has developed a CAP Canadian Profile (CAP-CP) based on CAP but specialized to address the needs of Canadian public alerting stakeholders, such as bilingualism, geocoding for Canada, managed lists of locations and events, etc. The Canadian government has adopted CAP-CP for its National Public Alerting System (NPAS) project. The CAP‑CP working group, along with stakeholders and projects such as the Canadian Public Safety Operations Organization (CanOps) and Netalerts' Sarnia Lambton trial, are now working with and refining CAP‑CP for national application in Canada.[11][12]

CAP has been implemented for a small-scale, grassroots hazard information system in Sri Lanka following the 2004 Indian Ocean Tsunami. This implementation was part of the "HazInfo Project", funded by Canada's International Development Research Centre.[13]

Australia

The Australian Government Standard for Common Alerting Protocol (CAP-AU-STD, 2012) was developed by a CAP-AU-STD stakeholder group comprising federal agencies Emergency Management Australia, the Bureau of Meteorology, GeoScience Australia, Department of Agriculture, Fisheries and Forestry and the Department of Health, as well as a number of State Government authorities and emergency services agencies. The project was co-ordinated by the Australian Government Attorney-General's Department (Australian Emergency Management).[14] [15]

Worldwide

In 2007, the International Telecommunication Union, Telecommunication Standardization Sector (ITU-T) adopted the Common Alerting Protocol as Recommendation X.1303.[16][17] The recommendation annex contains an authoritative ASN.1 module translation of the CAP XML schema that may be useful for some implementations. Rec. X.1303 is within the remit of ITU‑T Study Group 17 (Security), Rapporteur Group on Cybersecurity (Q.4/17) for purposes of further evolution of the standard.[18]

References

  1. ↑ http://www.sdr.gov/NDIS_rev_Oct27.pdf
  2. ↑ http://www.ppw.us
  3. ↑ http://www.oasis-open.org/committees/emergency
  4. ↑ http://www.oasis-open.org/committees/download.php/14759/emergency-CAPv1.1.pdf
  5. ↑ http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf
  6. ↑ http://www.incident.com/cookbook/index.php/CAP_Fact_Sheet
  7. ↑ "Emergency Digital Information Service (EDIS)". ca.gov.
  8. ↑ "The Internet Rises to the Challenge of Public Warning". isoc.org.
  9. ↑ "Association of Public Television Stations". apts.org.
  10. ↑ http://www.fema.gov/emergency/ipaws/
  11. ↑ "CanOps". capan.ca.
  12. ↑ "AlertSite Sarnia-Lambton Index". netalerts.ca.
  13. ↑ "Evaluating Last-Mile Hazard Information Dissemination (HazInfo)". lirneasia.net.
  14. ↑ "Pages - Australian Emergency Management". em.gov.au.
  15. ↑ "Common Alerting Protocol – Australia (CAP-AU-STD) - GovShare". govshare.gov.au.
  16. ↑ "ITU Telecommunication Standardization Sector". ITU.
  17. ↑ tsbmail. "X.1303 : Common alerting protocol (CAP 1.1)". itu.int.
  18. ↑ "ITU-T Study Group 17 (Study Period 2013-2016)". itu.int.

External links