ABCDEF
1
RequirementAdressed (Yes/No)Should be done in MVP?What wasn't done?CommentsWB feedback
2
Should have an ETL integration layer to pull data from existing systems into the MIS and Should have real-time validation for ETL serviceYesYes
3
ETL service should support Database, API, Excel and CSV extraction from sourceYesYesThis one is theoretically addressed. We currently have workflows that allow upload from the csv file, however new workflows for databases, APIs etc. can be added through openFN.Sufficient for MVP
4
Allows to see all beneficiaries on the system. Grouped by four statuses which act as a submodule. These are POTENTIAL, ACTIVE, GRADUATED, and SUSPENDEDYesYesBeneficiaries are kept in Individuals and Goups modules. Status of each beneficiary referes to given Benefit Plan
5
Allows the grouping of beneficiaries by a program during the ETL process.NoYesI wouldn't say this one is addressed. Theoretically we could add workflow that would store additional information about the benefit plan and use it to assign individual for a particular program, however our intention is to upload beneficiaries per program from the beginning.We have to allow grouping of beneficiaries once uploading the CSV. We need a field with some ID to indicate if individual is a part of the group and create such group. It essential its in the. MVP so we can allow grouping of members into households et al.
6
Allows filtering and downloading of beneficiaries by using geographical data or other characteristics, as per program needs (there can be sensible defaults, but authorised users should be able to configure them). For example, download, a file of beneficiaries who are FEMALE and have a DISABILITY in particular locationsYesYesAdvanced fiters funcionality allows fitering the data and those can be downloaded later on.
7
Allows a search on each submodule for beneficiariesYesYesSearch criteria
8
Allows to export the beneficiary list as CSVYesYes
9
Allows integration into other modules, like Payments, Kind Disbursement Training, Savings Groups and Grievances to view all recorded data for beneficiaries.YesNoModules weren't developed yet
10
Allows recording of grievances for beneficiariesNoNo
11
Allows creation of data update requests for beneficiariesNoYesCurrently available only for benefit plan updates

To be asked: Shall the data updates be added to the scope of current MVP or not? At this stage we have a proof of concept that data updates works in CORE-MIS but only for benefit plans		To be confirmed with Andrea and WB Team if we need to develop it in the scope of MVp. Just to indicate some events i.e beneficiary turned 18 y.o. This is essential to data management so it should be included
12
Allows configuration of alerts to flag beneficiary details when events are triggered. For example, an alert to flag when beneficiaries turn age nineteen. Which will be executed daily to flag beneficiaries that meet the criteria.NoNoWasn't addressed yetTo be confirmed with Andrea and WB Team if we need to develop it in the scope of MVP. Just to indicate some events i.e beneficiary turned 18 y.o.
13
Allows the transition of beneficiaries through the various status or cycles. For example, POTENTIAL beneficiaries can be made ACTIVE, ACTIVE beneficiaries can be GRADUATED or SUSPENDED.YesYes
14
Depending on the SP program design, change of status at the individual level may or may not reflect at the household level.NoYesNot developed yet

From our perspective it is for MVP2		To be confirmed with Andrea and WB Team if we need to develop it in the scope of MVp
15
Allows undoing a transition of beneficiaries to another status group.YesYes
16
All status changes, benefits and services, etc. should be loggedNoYesFor the time being it's not possible for user to check particular status in the particular time in the past from the UI

Shall it be for MVP2?		To be confirmed with Andrea and WB Team if we need to develop it in the scope of MVp