| | 83 | * Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile |
| | 84 | handhelds. If necessary suggest some GUI tweaks to harmonize the |
| | 85 | desktop version with the mobile screens. |
| | 86 | |
| | 87 | * Step 2. Design hazard specific alert authoring and issuing GUIs. For |
| | 88 | example, Alerting Authorities, in a local area (Barangay, |
| | 89 | Gramaniladari, Thaluk, etc) do not need the full CAP message but a few |
| | 90 | attributes like the area and water level. We will target on delivering |
| | 91 | 3-5 mobile GUIs for Landslide, Flood, Accident, |
| | 92 | |
| | 93 | * Step 3. Develop the requirements/design for using the concept of |
| | 94 | Pictographs in Alerting and other features such as a wake up function |
| | 95 | to sound an Audible Alarm etc. I think we should do the same with the |
| | 96 | web GUI such that we can set a siren audio to sound for a specific |
| | 97 | warning_priority threshold. |
| | 98 | |
| | 99 | We may have to look for funding outside of the ESCAP project for step 3. |