Scope of Work for the MIS Development The system should work offline more specifically; the MIS should have the following functionality capacities: The MIS name, roles, MIS identity, MIS password, the fields/parameters, parameter descriptions, how & where to get it, data entry, how to edit old dataset-quarterly data for each cycle, how to manage data set and analysis tools. It should have the following additional functionality. 1. Planning – data entry and notifications system. 2. Monitoring – data entry, and export in various formats. 3. Reporting – reports, graphs, and ad-hoc custom reporting capability. 4. Role-based user dashboards that cumulate data, for easy-to-use data visualization and highlight projects and tasks that require attention.
In detail, the Excel-based MIS should be able to: 1. Have Excel fields that accept front-end data entry tools using appropriate and efficient querying tools for data retrieval. 2. Ensure data retrieval/exchange capability with other systems and databases as agreed in the first part of the assignment. 3. Have relevant import/export capabilities to pre-designed templates or databases. 4. Display summary pages showing data from all available sources, aggregate statistics, and summary visuals which illuminate what is and is not working. 5. Present summary dashboards showing progress. 6. Allow a user to overlay and/or compare data. 7. Provide administrators with intuitive tools for reconciling discrepancies between different data sources, and a clear indication in the event that the link between systems becomes inoperable or offline. 8. Provide a database administration module, allowing for advanced user management, with a staggered set of privileges for different users as well as user authorization, tracking/authorizing changes to results hierarchy, database download, online backup, and other necessary features; and 10. Integration with a Knowledge Management platform. 9. Propose a security standard for the system. This may include a login ID, password, security administration, and security access and security certificates (This is a must to ensure secure connections to the system). 10. During the development of the software, the Consultant will be required to implement unit testing, acceptance, and performance testing so as to ensure that the MIS developed delivers the proposed value. 11. Document and share the source code, database schemas, and user manuals. 12. Offer a short virtual recorded training on how to use the system. 13. Be available for a period of 14 days to ensure the system is stable after the development period.