| 26 | | <Who will be the users of the solution?> [[br]] |
| 27 | | There are 3 categories of stakeholders who will use the system for different information communication needs. |
| 28 | | 1. EOC Staff!/Units (Operational): |
| 29 | | a. Director!/Commander |
| 30 | | a. Operations (or Dispatch) |
| 31 | | a. Planning |
| 32 | | a. Logistics |
| | 26 | There are 3 categories of stakeholders who will use the system for different information needs; namely those who coordinate from a central unit, field operatives responding on site, and other stakeholders who indirectly respond to the incident. The users described below are from a humanitarian perspective. However, a utilities company may chose to use the system where they may only have EOC staff and field operatives (e.g. engineering and maintenance teams). |
| | 27 | === Who are the users === |
| | 28 | 1. EOC Staff / Units (Operational): |
| | 29 | a. Director / Commander |
| | 30 | a. Operations / Dispatch |
| | 31 | a. Planning & Logistics |
| 42 | | a. Local NGOs, International Organizations (e.g. UN agencies, Red Cross) |
| 43 | | a. Civil Society (e.g. |
| 44 | | [[br]] |
| 45 | | * Emergency management is the theme or suite SAFIRE sits in. It can be any organization who would want to manage their emergencies. |
| 46 | | * In general, Police, Fire, Ambulance, NEOC, DEOC, Telecom, Power, Water. |
| 47 | | <How will stakeholders be affected?>[[br]] |
| 48 | | * Accountability |
| 49 | | * Efficiency gains |
| 50 | | |
| 51 | | Media, Public, Presidents Office, Disaster Management Ministry, and Heads of Departments |
| 52 | | * Homepage - Most recent events with the |
| 53 | | * most recent update summary report (similar to WA-COP homepage), |
| 54 | | * show/hide incident information for each event |
| 55 | | * Button at the top: “I want to report an incident” (i.e. for public, civil societies, and NGOs, to directly use the web form) |
| 56 | | * Table view listing of other ongoing or past events |
| 57 | | * Default - most recent active events and incident report |
| 58 | | * option to search and filter by status, date, event type, and, title |
| 59 | | * Map view of past and present events |
| 60 | | * Select/Deselect event area polygons (remove overlapping polygons) |
| 61 | | * Zoom into see the headline of the incident information |
| | 41 | a. Civil Society, Local NGOs, International Organizations (e.g. Sarvodaya, Red Cross, UN agencies) |
| | 42 | a. Public |
| | 43 | |
| | 44 | === How the users are affected === |
| | 45 | ||= Element =||= Description =|| |
| | 46 | || Coordination ||avoid duplication, everyone sees the same set of information, and can re-use without creating their own information stacks || |
| | 47 | || Consistency || || |
| | 48 | || Control || || |
| | 49 | || Accountability || || |
| | 50 | |
