32 | | 1.1. Authorized user chooses to create a new message |
33 | | 1.1. If presented to select a template (e.g. Cyclone template) |
34 | | 1.1. Completes the missing information specific to the event such as event, headline, onset, description, instructions, effective, areaDesc, etc |
35 | | 1.1. Repeat the "info" segment of the message for each language, as specified by the profile |
36 | | 1.1. Saves the message as an "actual" alert with a scope set to "Public" |
37 | | 1.1. Chooses to broadcast the message through the cellular networks, share with all TV/Radio stations |
38 | | * He will then optionally attach files (eg. containing pre-decided evacuation instructions etc) and also add a few more language templates and edit them |
39 | | * He then sends the CAP Alert as a "Public" alert which everyone subscribed or added in the contacts is notified about |
40 | | * Since CAP is an XML standard it can be easily picked up by automated systems and required actions maybe performed (eg. Sirens) |
| 37 | a. Authorized user chooses to create a new message |
| 38 | a. If presented to select a template (e.g. Cyclone template) |
| 39 | a. Completes the missing information specific to the event such as event, headline, onset, description, instructions, effective, areaDesc, etc |
| 40 | a. Repeat the "info" segment of the message for each language, as specified by the profile |
| 41 | a. Attach a "resource" file |
| 42 | a. Saves the message as an "actual" alert with a scope set to "Public" |
| 43 | a. Chooses to broadcast the message through the cellular networks, share with all TV/Radio stations |
| 44 | 1. A warning agency learns of a tsunami warning and wants to activate the siren towers |
| 45 | a. Similar to the previous instance, the authorized user would create a message |
| 46 | a. Set the "parameter" values to trigger the sirens |
| 47 | a. Select the areaDescription to determine the targeted siren towers |
| 48 | a. Choose the delivery method as "siren system" and send the message |