Changes between Version 11 and Version 12 of BluePrint/CAPBroker


Ignore:
Timestamp:
03/21/14 02:48:39 (7 years ago)
Author:
Nuwan Waidyanatha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/CAPBroker

    v11 v12  
    66
    77== Introduction ==
    8 [http://en.wikipedia.org/wiki/Common_Alerting_Protocol Common Alerting Protocol] defines a data format for sharing alerts (and re-relaying) over various media channels. This project aims to implement core CAP features into Eden and provide usable UI elements for managing CAP alerts.The module will facilitate the publishing and relaying of alerts and warning as well as offer subscribers means to receive warnings and alerts of their choice. Moreover, the module will provide a common operating picture of the published alerts for improving situational-awareness. The tools are mainly for National Disaster Management Organizations for managing [http://lirneasia.net/2012/05/masas-iscram-2012/ Multi-agency Situational-awareness] with capabilities for all-hazard all-media warning/alerting.
     8[http://en.wikipedia.org/wiki/Common_Alerting_Protocol Common Alerting Protocol] defines a data format for sharing alerts (and re-relaying) over various media channels. This project aims to implement core CAP features into Eden and provide usable UI elements for managing CAP alerts.The module will facilitate the publishing and relaying of alerts and warning as well as offer subscribers means to receive warnings and alerts of their choice. Moreover, the module will provide a common operating picture of the published alerts for improving situational-awareness (e.g. [http://gdacs.org/alerts/ GDACS common operating picture with message filtering]). The tools are mainly for National Disaster Management Organizations for managing [http://lirneasia.net/2012/05/masas-iscram-2012/ Multi-agency Situational-awareness] with capabilities for all-hazard all-media warning/alerting.
    99
    10 The self-contained product, coming out of the developments, will be coined as the CAP-enabled Sahana Alerting and Messaging Broker (abbreviated as "SAMBRO"). One aspect of SAMBRO is for implementers to subscribe to available CAP feeds such as USGS or GDACS, then work in the capacity of an aggregator to present those CAP messages in the common operating picture based on spatial and temporal dimensions. Authorized SAMBRO user can choose to amend those CAP messages, received through the feeds, to relay them to the subscribers registered in the SAMBRO.  content and relay that message to recipients registered in the Sahana Eden instance. They could be human subscribers or other systems linked to Sahana Eden, thus alerting them of an imminent tsunami, for example.
     10The self-contained product, coming out of the developments, will be coined as the CAP-enabled Sahana Alerting and Messaging Broker (abbreviated as "SAMBRO"). One aspect of SAMBRO is give implementers the option to subscribe to available CAP feeds such as the [http://wcatwc.arh.noaa.gov/ National Oceanic and Atmospheric Administration's National Tsunami Warning Centre] CAPXML feeds [https://inatews.bmkg.go.id/rss/capatomlast40event.xml International Tsunami Warning System in Indonesia] with their CAP-Atom feeds, or the [http://gdacs.org/resources.aspx?eventid=122640&episodeid=122656&eventtype=EQ Global Disaster Alert and Coordination System] (GDACS) individual alert CAP files. Thereby, serving in capacity of an aggregator to present those CAP messages in the common operating picture based on spatial and temporal dimensions. Authorized SAMBRO user can choose to amend those CAP messages, received through the feeds, to relay them to the subscribers registered in the SAMBRO.
    1111
    12 Similarly, a manually recorded landslide can be broadcast by an Eden server which will be sent out to the traffic control system, for example, which will allow it to automatically determine a custom traffic routing.
    13 
     12SAMBRO subscribers could be human or other systems (e.g [http://alert-hub.appspot.com Google's Alerthub]). SAMRBO message publishers would be provided with functionality to manage reusable CAP message template and issue CAP messages over multiple channels such as HTTP posts, RSS/Atom feeds, SMS, Email, Twitter, Facebook, so on and so forth. The CAP standard also requires that implementers define a CAP-Profile. These are typically considered as CAP Country Profiles. Therefore, the module will feature those components for managing those implementation specific profiles.
    1413== Description ==
    1514User story: