| | 55 | Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile |
| | 56 | handhelds. If necessary suggest some GUI tweaks to harmonize the |
| | 57 | desktop version with the mobile screens. |
| | 58 | |
| | 59 | Step 2. Design hazard specific alert authoring and issuing GUIs. For |
| | 60 | example, Alerting Authorities, in a local area (Barangay, |
| | 61 | Gramaniladari, Thaluk, etc) do not need the full CAP message but a few |
| | 62 | attributes like the area and water level. We will target on delivering |
| | 63 | 3-5 mobile GUIs for Landslide, Flood, Accident, |
| | 64 | |
| | 65 | Step 3. Develop the requirements/design for using the concept of |
| | 66 | Pictographs in Alerting and other features such as a wake up function |
| | 67 | to sound an Audible Alarm etc. I think we should do the same with the |
| | 68 | web GUI such that we can set a siren audio to sound for a specific |
| | 69 | warning_priority threshold. |
| | 70 | |
| | 71 | We may have to look for funding outside of the ESCAP project for step 3. |
| | 72 | |