| 1 | [[TOC]] |
| 2 | = Grameen Development Services = |
| 3 | == Requirements for Information Management of DRR Portal for Maharajganj == |
| 4 | |
| 5 | === Deployment Scenario === |
| 6 | * Online, publically accessible instance. Subdomain of gdsindia.org |
| 7 | * Offline, on one of the PCs at project location. At a point this will be the main point of data entry and data will need to be synced up to online install of Eden. |
| 8 | * Offline install will, ideally, also have: GSM Modem setup to make calls/send SMS alerts. |
| 9 | * using !FreeSwitch/OpenGSM/FreedomFone to manage SMS menus? |
| 10 | |
| 11 | === Users of the System === |
| 12 | * GDS Humanitarian Response Team |
| 13 | * Write access to all data |
| 14 | * GDS Head Office |
| 15 | * Write access to all data |
| 16 | * Partners/Donors. Oxfam (India/Novib) |
| 17 | * Read access to all data - I think they should just have read access to a comprehensive/daily situation reports, and any other "read" only resource that we want them to see. Primarily I think we want the system to be able to send reports to them, in a particular format daily. In future, if need be we can give read/write access to required data as and when needed? |
| 18 | * Public |
| 19 | * Read access to just some data |
| 20 | |
| 21 | === Priority === |
| 22 | Contact List of: |
| 23 | * Field Volunteers and CBOs (Community based organisations) |
| 24 | * Team Members |
| 25 | * GDS Humanitarian Team |
| 26 | * Government Departments |
| 27 | * Transport |
| 28 | * Pharmacists |
| 29 | * Food-material Suppliers |
| 30 | * Non-Food material Suppliers |
| 31 | * CSOs (Civil Society Organisation) |
| 32 | |
| 33 | === Reporting Needs === |
| 34 | (with proper GDS Branding) |
| 35 | |
| 36 | ==== Daily ==== |
| 37 | * River-water Levels (Twice: 8am, 3pm) |
| 38 | * Rainfall (Once) |
| 39 | |
| 40 | ==== Incident based ==== |
| 41 | Any R&R work or distribution work done. |
| 42 | |
| 43 | (This goes on to the Situation Map?) |
| 44 | 2. Recipients through automated emails upon data entry: GDS HO, Oxfam, Local NGOs, NIDM, NDMA, Sahyog, IAG-UP |
| 45 | 3. Current Format for recipients: The pdf file of water-levels and rainfall sent twice daily. |
| 46 | 4. All the above reports should be available for public view as well on dashboard. |
| 47 | |
| 48 | === Features Required === |
| 49 | * Volunteer Management - Volunteers are selected/trained members from the village. They won't be accessing the system. - Need to record their profile info with skills/training they have received. (PR+Creating a Group named "Volunteer" can do?" |
| 50 | * Person Registry (to manage villager's profile) |
| 51 | * Employee Information/GDS Response Team |
| 52 | * Warehouse/Inventory Data |
| 53 | * How many warehouses? What workflow for adding/transferring/removing items? Procurement happens outside? |
| 54 | * Messaging - Alerts via SMS/Email. |
| 55 | * Using online SMS gateway: http://mvaayoo.com |
| 56 | * Dashboard for Internal Team and a Public Dashboard with feeds. (like news room feed from http://www.gdsindia.org/maharajganj/category/news-room/feed/) |
| 57 | |
| 58 | === Type of Data === |
| 59 | * Most of the existing data is in Excel/Word documents with non-UTF/non-standard Hindi fonts. |
| 60 | * Flood related alerts/Water Level information and Rainfall data of forecast sites is recieved in Hindi as well |
| 61 | * Locations Hierarchy needs to have names in multiple languages (Hindi, English & Local language) |
| 62 | * Location Hierarchy --> State --> District--> Block --> Nyaya Panchayat -->Gram Sabha/Panchayat-->Village |
| 63 | * Dealing with "India" and "Uttar Pradesh" state data only for now for this deployment. |