| 4 | | |
| 5 | | == Description == |
| 6 | | User story: |
| 7 | | * A an emergency response agency learns of an imminent disaster say a Tsunami, and the following are the steps they take up: |
| 8 | | * In Eden's CAP interface the operator chooses the CAP Profile for their region |
| 9 | | * He then chooses a CAP Template specific for Tsunami |
| 10 | | * He then edits the blanked out fields in the template (for example, area description, severity) and also sets a few flags (these are provided as per the CAP 1.2 specification) |
| 11 | | * He will then optionally attach files (eg. containing pre-decided evacuation instructions etc) and also add a few more language templates and edit them |
| 12 | | * He then sends the CAP Alert as a "Public" alert which everyone subscribed or added in the contacts is notified about |
| 13 | | * Since CAP is an XML standard it can be easily picked up by automated systems and required actions maybe performed (eg. Sirens) |
| 14 | | |
| 15 | | Sahana Agasti has a CAP broker implementation |
