Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Health campaign microplanning is a detailed planning approach used to ensure that health interventions, such as immunisations or disease prevention campaigns, are effectively delivered to target populations.
Microplanning helps to know:
Who needs the intervention?
Where is the intervention needed?
How many resources (medical supply, people, commodities, etc.) are needed for the intervention?
How will we reach the intervention site?
Prone to Errors: The process relies heavily on Excel, requiring meticulous care for resource estimation calculations, making it highly susceptible to errors.
Fragmented Management: Each district manages its microplan individually, leading to a back-and-forth process for collaboration. Incomplete data from any district results in faulty resource estimation for the entire campaign.
Complex Data Collection: Gathering and validating population data for microplan estimation is a tedious and poorly defined process. Incorrect population estimates can lead to inaccurate resource estimations for the campaign.
Time-Consuming Collaboration: Microplanning involves multiple people from various administrative levels to administer and validate resource estimations. Offline collaboration is time-consuming and increases the risk of errors if not managed carefully.
Lack of Reusability: Microplan estimations are created from scratch for each new campaign, making the process lengthy and time-consuming without the benefit of reusing previous plans.
Build capabilities that help maximise campaign coverage, enhance access for health campaigns and fairly estimate resources for microplaning. These can be achieved by the following:
Improve population denominator: Leverage data triangulation from multiple sources and validation from community leaders at village/settlement level to identify and improve population denominator.
Targeted Interventions: Leverage data to pinpoint high-risk and unsettled areas and tailor campaign strategies to specific geographic populations.
Optimized Resource Allocation: Analyze population distribution and resource needs to ensure efficient deployment of personnel, vaccines, and supplies.
Improved Outreach & Accessibility: Identify underserved communities and map optimal routes for campaign teams, maximizing outreach and access.
Increased Transparency & Accountability: Provide a clear picture of campaign coverage and resource distribution, promoting accountability to stakeholders and communities.
Enable countries to be able to collect and validate accurate population data for better & accurate microplan estimation.
Enable countries to have better accountability mechanisms and controlled access to ensure transparency and authorised access for microplan execution.
Enable countries to more accurately estimate and distribute resources, ensuring targeted regions are reached and health campaigns are executed smoothly.
This section provides a detailed and comprehensive view of the micro planning system's internal mechanics. The LLD focuses on providing API specifications, sequence diagrams and database schema. This section serves as a blueprint for developers and engineers to implement the system accurately.
The Microplanning system is designed to allow users to generate, validate, and approve micro plans across various geographic boundaries. The system's architecture includes services for handling population data, plan estimates, employee assignments and facility linkages. The system is scalable, secure, and optimised for local and national-level campaigns.
Plan Management - Handles micro plan setup, micro plan employee assignments, micro plan facility linkage, micro plan estimations and its validation/approval.
Census Management - Handles population data and its validation/approval.
Resource Generator - Utility service which reads population and facility excel files uploaded by the user to generate population records and plan facility linkages in the system.
Project Factory - Utility service which exposes APIs to generate population data upload template and facility data upload template.
Plan management service handles micro plan setup, micro plan employee assignments, micro plan facility linkage, micro plan estimations and its validation/approval.
Plan Management API Specification
Census management service handles population data and its validation/approval.
Census Management API Specification
Create/Update Microplan
The System Administrator is responsible for setting up the entire microplanning platform, which includes defining campaign boundaries, configuring facilities, and assigning roles. This user operates at the national or country level and ensures all configurations align with campaign objectives.
Capture Campaign Details:
Actor: System Administrator/Program Manager
Objective: Configure campaign information.
Process:
Select Disease: Choose the disease for the campaign (e.g., malaria).
Campaign Type: Select from options like Bednets or SMC (Seasonal Malaria Chemoprevention).
Resource Distribution Strategy: Choose between Fixed post, House-to-House, or a combination of both.
Next/Back: Proceed to the next screen or return to the previous step.
Validation:
All fields are mandatory before proceeding.
Naming the Microplan:
Actor: System Administrator/Program Manager
Objective: Assign a unique name to the microplan.
Process:
Auto-Suggested Name: The system provides a default name based on the format: Country-Disease-CampaignType-MonthLast2DigitsOfYear.
User Input: Option to modify the name while following a strict naming convention.
Validation:
The name must be unique and follow specific guidelines (e.g., minimum 3 characters, no special characters except _() ).
Select Campaign Boundaries:
Actor: System Administrator/Program Manager
Objective: Choose the geographic administrative boundaries (country, province, district, village, etc.).
Process:
Multi-Select Dropdowns: Select from a multi-select list of administrative divisions.
Validation: All fields are mandatory.
Upload Population Data:
Actor: System Administrator/Program Manager
Objective: Upload population data required for resource estimation.
Process:
Download Template: Download a pre-configured Excel template.
Input Data: Enter total and target population, village coordinates, etc.
Upload: After filling in the template, upload it back to the system.
Validation:
Ensure data integrity (e.g., total population must be greater than zero, population data must be whole numbers).
Upload Facility Data:
Actor: System Administrator/Program Manager
Objective: Set up facilities to be used during the campaign.
Process:
Download Facility Template: Fill out the downloaded template with facility details (e.g., facility type, capacity, geographic coordinates).
Upload and Validate: Once filled, upload the template.
Validation:
Mandatory fields such as facility name, type, and capacity must be filled in.
Manage Microplan Assumptions:
Actor: System Administrator/Program Manager
Objective: Configure assumptions for calculating required resources.
Process:
Set parameters like population density and distribution strategy.
Validation:
Input values must be numerical.
Access Control and Role Configuration:
Actor: System Administrator
Objective: Define and assign roles and permissions (e.g., Data Collectors, Microplan Approvers).
Process:
Configure roles and assign them to specific users.
Define user boundaries and access hierarchies.
The Facility Catchment Mapper is responsible for mapping health facilities to their respective geographic catchment areas (e.g., villages, districts) using data provided via an API. This mapping ensures that each facility is associated with a specific community, enabling efficient distribution of resources during health campaigns.
Assign health facilities to geographic catchment areas (e.g., villages, localities).
Ensure each village or locality is mapped to an appropriate facility.
Review and update facility assignments when necessary based on campaign requirements.
Below are the detailed steps for the facility catchment mapping process.
Step 1: Log in to the Platform
Actor: Facility Catchment Mapper
Objective: Access the facility catchment management dashboard.
Process: The Facility Catchment Mapper logs into the microplanning platform using their credentials and navigates to the facility catchment module.
Outcome: The system displays a list of available campaigns and their linked facilities retrieved from the API.
Step 2: View Facility Data via Plan Facility
Actor: Facility Catchment Mapper
Objective: Access the list of facilities linked to the microplan, pulled from the Plan Facility.
Process:
The system retrieves the list of facilities linked to the current campaign and displays them in the catchment mapping dashboard.
The data from the Plan Facility includes key attributes such as:
Facility Name
Facility Type (e.g., clinic, hospital)
Capacity (e.g., beds, vaccine storage)
Facility Status (active/inactive)
Facility Location (latitude and longitude)
Outcome: The Facility Catchment Mapper can view all the facilities available for mapping in real time.
Step 3: Assign Facilities to Catchment Areas
Actor: Facility Catchment Mapper
Objective: Map each facility to a corresponding catchment area (e.g., village, district).
Process:
Catchment Area Mapping:
Each facility is mapped to a specific administrative boundary (village, district, etc.).
Facility location (latitude and longitude) is used to cross-reference and ensure the correct geographic catchment area is assigned.
Mapping Considerations:
Ensure each catchment area is assigned to the most appropriate or nearest facility based on geographic proximity.
Avoid conflicts where multiple facilities are mapped to the same geographic area, unless required by the campaign.
Outcome: Each facility is successfully assigned to its respective catchment area, ensuring proper resource allocation during campaign execution.
Step 4: Validate Catchment Area Assignments
Actor: Facility Catchment Mapper
Objective: Ensure the accuracy and validity of facility assignments to catchment areas.
Process:
The system highlights any potential mapping errors or overlaps, such as:
Unmapped villages or localities.
Facilities assigned to incorrect or multiple areas.
The Facility Catchment Mapper reviews and resolves these issues before finalizing the assignments.
Validation checks include:
Ensure each village or locality is mapped to exactly one facility.
Verify that all mandatory fields (facility name, type, status, location) are populated.
Outcome: The mapping is validated, and all errors are corrected before approval.
Step 5: Approve and Save Facility Catchment Mapping
Actor: Facility Catchment Mapper
Objective: Finalize and approve the facility catchment mapping.
Process:
Once all assignments are validated, the mapper approves the mappings.
The system saves the approved mappings, and the data is made available for use in microplan resource estimation and campaign execution.
Outcome: Facility catchment mapping is finalized and stored in the system, ensuring proper facility allocation for the upcoming health campaign.
Geographical Accuracy:
Facilities must be assigned to the correct administrative boundaries based on their geographic coordinates.
Avoiding Overlap:
Each catchment area (village, locality, etc.) should be mapped to only one facility unless otherwise required by the campaign's objectives.
Handling Missing Facilities:
If a catchment area does not have a mapped facility, it must be flagged for review and resolution before the campaign begins.
The Data Approver is responsible for validating population data collected by data collectors. The role primarily ensures that population data used for microplan resource estimation is accurate and consistent with predefined rules. Data approvers play a crucial role in identifying discrepancies and ensuring the validity of population numbers before final approval.
Validate population data collected from the field.
Identify discrepancies in population estimates.
Approve or flag data for further review and corrections.
Note : In the current version we are not including data collectors. Population data uploaded in the system admin flow will be sent for approval
The following describes the step-by-step workflow for the Data Approver:
Step 1: Log in to the Platform
Actor: Data Approver
Objective: Access the data review dashboard.
Process: The Data Approver logs into the microplanning platform with their credentials.
Outcome: The system displays all pending data that needs to be validated.
Step 2: Review Submitted Population Data
Actor: Data Approver
Objective: View population data collected by Data Collectors.
Process:
The Data Approver navigates to the population data review section.
The system presents the population data per administrative level (village, district, etc.).
Data is compared against previously uploaded data or other authoritative sources for discrepancies.
Outcome: The Data Approver views all population-related information for selected regions, including:
Total Population
Target Population (e.g., children aged 3-11 months and 12-59 months for SMC campaigns)
Latitude and Longitude (if available)
Step 3: Identify Discrepancies
Actor: Data Approver
Objective: Identify and highlight any discrepancies in the population data.
Process:
The Data Approver can manually review records to ensure the accuracy of the data.
Outcome: The system flags any discrepancies for further review, such as:
Significant deviations from earlier data (e.g., a village's population is reported as 5,000 when the previous figure was 2,000).
Step 4: Modify and Correct Data (If necessary)
Actor: Data Approver
Objective: Make necessary corrections to flagged data before approval.
Process:
If the Data Approver identifies errors or discrepancies, they may either:
Request corrections from the Data Collector.
Manually correct the data in the system, if they have the necessary authority and information.
Corrections may involve:
Adjusting total population numbers.
Updating target population estimates.
Correcting missing or incorrect geographic data (e.g., coordinates).
Outcome: The flagged data is corrected and updated in the system, ready for re-validation.
Step 5: Approve Population Data
Actor: Data Approver
Objective: Final approval of population data for use in resource estimation.
Process:
Once all discrepancies are resolved, the Data Approver selects the data records for final approval.
The system allows bulk approval or individual record validation based on user preferences.
Outcome: Approved population data is locked and made available for further processes, such as microplan resource estimation.
Step 6: Monitor Data Changes
Actor: Data Approver
Objective: Continuously monitor any changes to population data during the campaign.
Process:
The system provides alerts if any new data is submitted or if there are significant changes to previously approved data.
Data Approvers can review and re-approve any updates or revisions during the campaign.
Outcome: All data changes are tracked, ensuring continuous data integrity throughout the microplanning process.
Health campaign microplanning is a detailed planning approach used to ensure that health interventions, such as immunisations or disease prevention campaigns, are effectively delivered to target populations.
Updated registry: Assume that the registry data required for microplanning is accurate and up-to-date. This includes boundary data for countries, provinces, districts, and villages, as well as the location of health facilities and other points of interest. The user can update the registry while setting up the microplan.
User Roles and Access: Assume that users will be assigned specific roles (e.g., system administrator, data collector, reviewer) with corresponding access levels and permissions to ensure data integrity and security.
Data Collection Methodology: Assume that data collection methods are standardized and that data collectors are trained to ensure the consistency and accuracy of the data entered into the system.
Connectivity: Assume that users will have access to the internet or a mobile network to use the platform, although there should be provisions for offline data collection and synchronization when connectivity is limited for certain use cases.
Localization: Assume that the platform will be localized to support multiple languages and adapt to the cultural and linguistic diversity of the target communities. For the first release, the platform will be localised for English, French, and Portuguese languages.
Scalability: Assume that the platform will be scalable to accommodate additional users, data, and campaigns without significant performance degradation.
User Training and Support: Assume that users will receive adequate training on how to use the platform and that support will be available to address any issues or questions that arise.
Sustainability: Assume that the platform will be designed with sustainability in mind, considering the long-term maintenance and updates required to keep the system operational and relevant.
No registry changes: Assume that no new boundary registry or facility registry will be created or updated once the microplan setup is completed.
Below are the users involved in the microplanning process -
a. System administrator - This user is responsible for setting up the microplanning platform such as selecting campaign boundaries, setting up the data, configuring the microplan assumptions, etc. This user will belong to the national/country-level administrative hierarchy.
b. Data collector - This user is responsible for collecting and validating the population data from every village assigned to him/her. He will also capture the geographical features of the assigned villages such as the accessibility level of the village, the security level of the village, etc.
c. Supervisors - This is a user role that can be defined for multiple users across different administrative hierarchies. Every supervisor will have its action mapping such as supervisors with only data approver access, supervisors with microplan approval access, etc. The different type of supervisors involved are
Population data approver - This user will have access to the microplan module to view, validate, and approve the population of the assigned boundaries. The approved population will be used for the estimation of resources of the microplan.
Facility catchment mapper - This user will have access to the microplan module to map the facilities to their catchment boundaries w.r.t the user’s assigned boundaries.
Microplan approver - This user will have access to the microplan module to view, edit, and approve the microplanning estimation concerning the user’s assigned boundaries.
Microplan viewer - This user will have access to the microplan module to only view the microplanning estimation concerning the user’s assigned boundaries.
Click here to view the actor-noun-verb mapping.
The boundary registry is configured and updated during the instance creation for the country.
For defining the campaign facilities, the ‘Facility type’ should be configured in the MDMS during the instance creation for the country.
The facility or point of service capacity must be defined for the campaign type during instance creation. For the bednets campaign, the capacity should be ‘Bales’ ideally, for the SMC campaign, the capacity should be ‘Blisters’ ideally. It may change depending on the user’s requirements.
While managing the facility registry, the ‘Facility status’ needs to be configured in the MDMS during the instance creation of the country.
In the facility upload template, the column ‘Is fixed post?’ column options as ‘Yes’ or ‘No’ need to be configured in the MDMS
In the facility upload template, the column ‘Facility usage’ column options as ‘Active’ or ‘Inactive’ need to be configured in the MDMS
The capacity of the vehicle needs to be configured in the MDMS during instance setup. For the bednets campaign, the capacity should be ‘Bales’ ideally, for the SMC campaign, the capacity should be ‘Blisters’ ideally. It may change depending on the user’s requirements.
There will be 3 different registry data that will be used in this version of the microplan:
Boundary registry - The boundary registry is defined in the MDMS and the same registry can be used in the microplanning module. The boundary registry will later be created & managed by the admin console in the next version of the admin console.
Facility registry - The facility registry is defined in the MDMS and the same registry can be used in the microplanning module. The facility registry will later be created & managed by the admin console in the next version of the admin console.
Vehicle registry - The vehicle registry is defined in the MDMS and the same registry can be used in the microplanning module. The vehicle registry will later be created & managed by the admin console in the next version of the admin console.
Click here to view the detailed roadmap and value bundle
Click here to view in Miro board
Capturing campaign details -
Actor: System administrator/Program manager
Administrative boundary: National/Country
Using this screen, the user will be able to capture the campaign details for which the microplanning needs to be done. The components of this screen are -
a. Disease identified for the campaign - By default ‘Malaria’ will be chosen as we are creating the microplanning for the assumptions of malaria. As and when new diseases come into picture and we will have a better understanding of the assumptions and estimation, we will add those diseases in the dropdown.
b. Type of campaign - Upon choosing the disease, the user will be asked to choose the campaign type, which is either ‘Bednet’ or ‘SMC’. New campaign types can be included as and when understanding of the assumptions and estimation for them can be captured.
c. Resource distribution strategy - Upon choosing the campaign type, the user will be asked to choose the distribution strategy, which is either ‘Fixed post’ or ‘House-to-House’ or ‘Fixed post & House-to-House’. Depending on the strategy chosen, the assumptions and resource calculations will be configured by the platform.
d. Next - On click of ‘Next’, the campaign details will be saved and the user will be redirected to the next screen for naming the microplan.
e. Back - On click of ‘Back’, the user will be redirected to the homepage to either create a new microplan or to open a saved microplan.
Capture microplan name -
Actor: System administrator/Program manager
Administrative boundary: National/Country
Using this screen, the user can view the details of the campaign for which the microplanning needs to be done, and the user will be able to name the microplan accordingly for further use. The components of this screen are -
a. Campaign details - The campaign basic details chosen in the previous screen such as campaign disease, campaign type and resource distribution strategy will be shown here.
b. Naming of microplan - The microplan name will be auto suggested by the system. The structure of microplan name is ‘Country-Disease-CampaignType-MonthLast2digitsOfYear’. The name is a suggested name and the user can edit the microplan name if required. It’s a mandatory field.
Validation: The microplan name must be unique and can’t be the same as any previous created microplan name. If the user tries to enter a name that has been used already, show the error message ‘The name you have entered, has already been used. Please try a different name.’
c. Microplan naming format - This segment talks about the criteria for creating a microplan name, if the user wants to self create a microplan name. The naming convention are:
i. The name should be a minimum of 3 characters in length
ii. Only numeric values are not allowed
iii. Special characters -, _, (, ) are only allowed
Validation: If a user tries to enter a name that doesn’t match with the naming convention, show an error message ‘The name you have entered doesn’t match with the naming convention. Please try a different name.’
The max length of the microplan name is 100 characters.
d. Next - On click of ‘Next’, the microplan name will be saved and unedited. At this stage, the microplan will move to ‘Drafted setup’ status for being re-used or worked upon later.
e. Back - On click of ‘Back’, the user will be redirected to the previous step of capturing campaign details, but the microplan status will not change.
Selection of campaign boundary -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This screen will be used for choosing the campaign boundary where the microplanning estimation needs to be done. The below administrative hierarchy is configured for Mozambique, and the same administrative hierarchies will be different for different countries. The administrative hierarchy is defined during the instance setup of a country. The components of this screen are -
a. Selected boundaries count label - There will be a label on top of the screen where user will be able to see count of boundaries chosen as:
# of country chosen
# of province chosen
# of district chosen
# of admin post chosen
# of locality chosen
# of the village chosen.
b. Country - Here the user will choose the country where the campaign needs to be executed. It’s a mandatory field.
c. Province - Here the user will choose the province where the campaign needs to be executed. There can be multiple provinces to choose from depending on the country chosen. It will be a multi-select search-enabled dropdown for the user to choose the province(s). It’s a mandatory field.
d. District - Here the user will choose the district(s) where the campaign needs to be executed. There can be multiple districts to choose from depending on the provinces chosen. It will be a multi-select search-enabled dropdown for the user to choose the district(s). It’s a mandatory field.
e. Administrative post - Here the user will choose the admin post(s) where the campaign needs to be executed. There can be multiple admin post(s) to choose from depending on the districts chosen. It will be a multi-select search-enabled dropdown for the user to choose the admin post(s). It’s a mandatory field.
f. Locality - Here the user will choose the locality(s) where the campaign needs to be executed. There can be multiple locality(s) to choose from depending on the admin posts chosen. It will be a multi-select search-enabled dropdown for the user to choose the locality(s). It’s a mandatory field.
g. Village - Here the user will choose the village(s) where the campaign needs to be executed. There can be multiple village(s) to choose from depending on the localities chosen. It will be a multi-select search-enabled dropdown for the user to choose the village(s). It’s a mandatory field.
h. Next - On click of ‘Next’, the campaign boundaries will be chosen for microplanning. The same set of boundaries will be further used for data upload in the next part. All the fields are mandatory for moving to the next screen.
i. Back - On click of ‘Back’, the user will be redirected to the previous screen for naming microplan.
Validation: Once the microplan name is chosen and the user moves to the next screen, the microplan name can’t be changed.
Users can view all the selected boundaries as an array of lists and clear the selected boundaries if required. The user will be able to see the list of chosen boundaries for the parent boundary in the content box. For example, if the user chooses to see the list of districts chosen, then it will show in the content box with the province name and the list of districts attached to the province, if there are multiple provinces, there will be multiple content boxes.
Data management process (Population upload) -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This screen will be used for uploading the population data for the boundaries chosen for microplanning. When the user chooses the campaign boundaries in the previous step, the user in this step will have to upload the total and target population of the villages chosen in the campaign boundaries. The components of this screen are -
a. Download population template - This component will be used when the user has to download the boundary template to enter the population details for microplan estimation. The template will be separately downloaded & maintained for both bednets and SMC (As of now).
This screen will appear for the user to download the population template to be filled and upload
The user may skip it if he/she wants to move ahead without downloading the population template
The template for bednets is here.
The content of the downloadable bednet template is as follows -
Country: This shows the country where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Province: This shows the province(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
District: This shows the district(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Administrative post: This shows the admin post(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Locality: This shows the locality(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Village: This shows the village(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Total population: Here the user will be asked to enter the total village population.
Target population: Here the user will be asked to enter the target population who will be benefiting from the campaign.
Latitude & longitude: Here the user will be asked to enter the latitude & longitude of the village to be shown on the map.
For every campaign district, there will be a sheet in the downloadable report that the user needs to fill out and upload.
Note: The template should be configurable depending on the program. For Mozambique, the population template Excel has each sheet for the district. If the program wants to configure and collect data for each administrative post or locality level, the Excel sheets should be configured accordingly to collect population information in the administrative post or locality level.
Validation check:
The columns from ‘Country’ or highest administrative boundary to ‘Village’ or lowest administrative boundary should be fixed in the Excel and non-editable
The target population column is mandatory & can’t be empty
The total population column is mandatory & can’t be empty
The population data must only accept a whole number (Eg: 1234 and not 123.4)
The population data must be greater than 0
The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds
The template for SMC is here.
The content of downloadable SMC template is as follows -
Country: This shows the country where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Province: This shows the province(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
District: This shows the district(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Administrative post: This shows the admin post(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Locality: This shows the locality(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Village: This shows the village(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Total population: Here the user will be asked to enter the total village population.
Target population (Age 3 - 11 months): Here the user will be asked to enter the target population count of the children between 3 - 11 months in the village.
Target population (Age 12 - 59 months): Here the user will be asked to enter the target population count of the children between 12 - 59 months in the village.
Latitude & longitude: Here the user will be asked to enter the latitude & longitude of the village to be shown on the map.
For every campaign district, there will be a sheet in the downloadable report that the user needs to fill out and upload.
Note: The template should be configurable depending on the program. For Mozambique, the population template Excel has each sheet for the district. If the program wants to configure and collect data for each administrative post or locality level, the Excel sheets should be configured accordingly to collect population information at the administrative post or locality level.
Validation check:
The columns from ‘Country’ or highest administrative boundary to ‘Village’ or lowest administrative boundary should be fixed in the Excel and non-editable
The target population columns (Age 3-11 months and age 12-59 months) are mandatory & can’t be empty
The total population column is mandatory & can’t be empty
The population data must only accept a whole number (Eg: 1234 and not 123.4)
The population data must be greater than 0
The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds
b. Upload population template - This component will be used when the downloaded population excel file is filled and needs to be uploaded for estimating the campaign resource estimation.
The user can preview the uploaded file by clicking on the file name and it will open up the Excel preview
The user can re-upload the file using the ‘Re-upload’ button
The user can download the already uploaded file using the ‘Download’ button
The user can delete the uploaded file using the ‘X’ button, and once deleted, the user will be moved back to the Excel upload screen
The user will be able to view the number of errors captured in the uploaded file
The ‘View errors’ button will let the user view the list of errors in a tabular format
Error validation:
For bednet and SMC template upload - If the total population data uploaded is empty for any village, then show the error message ‘Total population data can’t be empty, please update the data and re-upload’.
For bednet and SMC template upload - If the total population data uploaded is not a whole number, then show the error message ‘Total population data must be a whole number, please update the data and re-upload’.
For bednet template upload - If the target population data uploaded is empty for any village, then show the error message ‘Target population data can’t be empty, please update the data and re-upload’.
For bednet template upload - If the target population data uploaded is not a whole number, then show the error message ‘Target population data must be a whole number, please update the data and re-upload’.
For SMC template upload - If the target population data (Age 3-11 months or Age 12-59 months) uploaded is empty for any village, then show the error message ‘Target population data can’t be empty, please update the data and re-upload’.
For SMC template upload - If the target population data (Age 3-11 months or Age 12-59 months) uploaded is not a whole number, then show the error message ‘Target population data must be a whole number, please update the data and re-upload’.
For bednet and SMC template upload - if the lat & long data uploaded does not adhere to the guideline, then show the error message ‘The latitude and longitude data does not comply with the guideline structure, please update the data and re-upload’.
The uploaded Excel file must have ‘Readme’ and ‘District sheets chosen in the boundary selection’, or the microplanning system will not validate and approve the file. Error message to be shown ‘One or more data sheets is absent, please update the data and re-upload the file’.
c. Error list view - This component will be shown when the upload file has one or more errors. The user can view the list of errors on the screen as well as download the errors as an Excel to view the error details in each row of Excel sheet.
The user will be able to navigate through the different errors using the ‘Previous’ or ‘Next’ buttons highlighted during data upload on the error view screen
All the errors will be highlighted in red color
On top of the preview screen, the user will be able to view the error details, for example, here the error mentioned that ‘Row 24 is empty!’
The user can download the Excel file with the detailed error mentioned. There should be an added column called ‘Error details’ that should show the errors in comma-separated format in case a single row has multiple errors
On click of ‘Back’ the user should be exited from the error preview screen
d. Excel upload guideline - The guideline directs the user on what to keep in mind while entering the population data and uploading it for the microplanning estimation. The guidelines are below for population data upload -
The mandatory fields such as total population and target population data must be a whole number (For example, population can be 1234 and not 123.5)
The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds ( Value should be 12.3455 & not 12° 20' 43.7994")
e. Data management process (Facility upload) -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This screen will be used to set up the facilities that are required for the campaign execution and microplanning estimation. Every facility to be used in the campaign needs to be added using this screen. The competent of this screen are -
a. Download facility template - This component will be used when the user needs to see the list of facilities available for the instance. The user can download the facility template and check out the facility list accordingly for campaign execution.
This screen will appear for the user to download the facility template to be updated and upload
The user may skip it if he/she wants to move ahead without downloading the facility template
The template for the facility is here
The facility template will have 2 different Excel sheets:
Facility sheet content:
Facility Name: If the instance already has facilities defined, then the user will be able to see the name of the facilities that are existing.
Facility Type: If the instance already has facilities defined, then the user will be able to see the type of facilities that are linked to each facility. The facility type for an instance will be defined in the MDMS during instance creation. This will be a dropdown option.
Facility Status: If the instance already has facilities defined, then the user will be able to see the status of the facilities that are existing. The facility status for an instance will be defined in the MDMS during instance creation. This will be a dropdown option.
Capacity: If the instance already has facilities defined, then the user will be able to see the capacity of the facilities that are existing. The definition of capacity of the facility is defined in the MDMS during instance creation.
Facility usage: If the instance already has facilities defined, then the user will be able to see the usage status of the facilities that are existing. ‘Active’ usage status means the facility is operational for the campaign and ‘Inactive’ usage status means the facility is non-operational for the campaign. The usage status is defined in the MDMS during instance creation. This will be a dropdown option.
Is fixed post?: If the instance already has facilities defined, then the user will be able to see if the facilities will be catered as a fixed post. The fixed post tag will only be functional when the resource distribution strategy is either Fixed post or House-to-House & Fixed post (Both). For instance, the fixed post tag will be defined for a facility unless it is manually changed by the user. This will be a dropdown option.
Residing boundary code: The residing boundary code defines where (Which village) exactly the facility resides. The user will be able to tag the boundary where the facility resides using the residing boundary sheet. The residing boundary of the facilities will be saved for the instance and it can be changed as per the user’s requirement during the facility configuration. This will be a dropdown option.
Latitude & Longitude: Here the user will be asked to enter the latitude & longitude of the village to be shown on the map.
Residing boundary sheet content:
Country: This shows the country where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Province: This shows the province(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
District: This shows the district(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Administrative post: This shows the admin post(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Locality: This shows the locality(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Village: This shows the village(s) where the campaign needs to run. This will be pre-defined in the downloaded template as per boundary selection in the previous step.
Boundary code: This shows the boundary code of the village where the campaign needs to run. The boundary code will be pre-defined for every village during the boundary registry configuration at the instance creation.
b. Upload facility template - This component will be used to upload the facility template to configure the facilities to be used in the campaign. The user can fill the template with the required details and upload the file accordingly. The user can add a new facility as well as deactivate the existing facilities to be used in the campaign.
The user can preview the uploaded file by clicking on the file name and it will open up the excel preview
The user can re-upload the file using the ‘Re-upload’ button
The user can download the already uploaded file using the ‘Download’ button
The user can delete the uploaded file using the ‘X’ button, and once deleted, the user will be moved back to the Excel upload screen
The user will be able to view the number of errors captured in the uploaded file
The ‘View errors’ button will let the user view the list of errors in a tabular format
Error validation:
In the facility sheet, the ‘Facility Name’ is a mandatory field. The user needs to enter the facility name before uploading the file into the system. Error message when there is no facility name defined ‘The facility name doesn’t exist in the uploaded file, please update and re-upload’.
In the facility sheet, the ‘Facility Type is a mandatory field. The user needs to enter the facility type before uploading the file into the system. Error message when there is no facility type defined ‘The facility type doesn’t exist for the facility in the uploaded file, please update and re-upload’.
In the facility sheet, the ‘Facility Status’ is a mandatory field. The user needs to enter the facility status before uploading the file into the system. Error message when there is no facility status defined ‘The facility status doesn’t exist for the facility in the uploaded file, please update and re-upload’.
In the facility sheet, the ‘Capacity’ is a mandatory field. The user needs to enter the facility capacity before uploading the file into the system. The unit of facility capacity needs to be defined in the MDMS during instance creation. Error message when there is no facility capacity defined ‘The facility capacity doesn’t exist for the facility in the uploaded file, please update and re-upload’.
In the facility sheet, the ‘Facility usage’ is a mandatory field. The user needs to enter the facility usage before uploading the file into the system. Error message when there is no facility usage defined ‘The facility usage information doesn’t exist for the facility in the uploaded file, please update and re-upload’.
In the facility sheet, the ‘Is fixed post?’ is a mandatory field. The user needs to enter the facility-fixed post tag before uploading the file into the system. Error message when there is no fixed post tag defined ‘The facility doesn’t have a fixed post tag defined in the uploaded file, please update and re-upload’.
Validation: This validation will be available only when the resource distribution strategy is either Fixed post or Fixed post & H2H.
In the facility sheet, the ‘Residing boundary code’ is a mandatory field. The user needs to enter the facility’s residing boundary code before uploading the file into the system. Error message when there is no facility’s residing boundary code defined ‘The facility’ residing boundary code doesn’t exist for the facility in the uploaded file, please update and re-upload’.
If the lat & long data uploaded do not adhere to the guideline, then show the error message ‘The latitude and longitude data does not comply with the guideline structure, please update the data and re-upload’.
The uploaded Excel file must have ‘Readme’, ‘Facility’, and ‘Residing boundary’ sheets. The residing boundary sheet will have boundaries chosen for the campaign, else the file will not be validated and approved by the microplanning system. Error message to be shown ‘One or more data sheets are absent in the uploaded file, please update the data and re-upload the file’.
c. Error list view - This component will be shown when the upload file has one or more errors. The user can view the list of errors on the screen as well as download the errors as an Excel to view the error details in each row of the Excel sheet.
The user will be able to navigate through the different errors using the ‘Previous’ or ‘Next’ buttons highlighted during data upload on the error view screen
All the errors will be highlighted in red color
On top of the preview screen, the user will be able to view the error details, for example, here the error mentioned that ‘Row 24 is empty!’
The user will be able to download the Excel file with the detailed error mentioned. There should be an added column called ‘Error details’ that should show the errors in comma-separated format in case a single row has multiple errors
On click of ‘Back’ the user should be exited from the error preview screen
d. Excel upload guideline - The guideline directs the user on what to keep in mind while entering the facility data and uploading it for the microplanning estimation. The guidelines are below for population data upload -
All the fields are mandatory and can't be empty, except the Latitude and Longitude fields
The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds ( Value should be 12.3455 & not 12° 20' 43.7994")
Data management process (Vehicle management) -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This screen will be used to set up the vehicles that are required for the campaign execution and microplanning estimation. Every vehicle to be used in the campaign needs to be added or chosen using this screen. The competent of this screen are -
a. Choosing vehicle type - The user will be asked to select the vehicle type to show the list of vehicles that belong to the vehicle type. Choosing of vehicle type is a multi-select dropdown and upon showing the vehicle list for the chosen vehicle type, the user can choose different vehicles that will be used for campaign execution. The user can choose multiple vehicles at a time.
Validation: It is mandatory to choose at least 1 vehicle for the campaign
b. Showing vehicle details - Once the vehicle lists is shown to the user, the user can check-out the vehicle details and then choose which vehicles to be used for the campaign. The basic vehicle details that will be shown to the users per vehicle are:
Vehicle type
Manufacture
Model
Vehicle capacity - ‘Bales’ for bednets/ ‘Blisters’ for SMC
c. Adding new vehicle details - If the user doesn’t find the vehicle details, he will be asked to add new vehicle details for the campaign. All the fields are mandatory here for adding a new vehicle.
The fields that the user can configure while adding new vehicle information are -
a. Vehicle type - If there is no vehicle type registered for the instance, then the user will get only one option to choose ‘Others’ to add the vehicle type.
b. Enter vehicle type - If the vehicle type is chosen as ‘Others’, the user will be asked to enter the vehicle type. It’s a mandatory field.
c. Enter vehicle manufacturer - The user will be asked to enter the vehicle manufacturer details. It’s a mandatory field.
d. Enter vehicle model - The user will be asked to enter the vehicle model details here. It’s a mandatory field.
e. Enter vehicle capacity (Bales/Blisters) - The vehicle capacity will be defined as ‘Bales’ for bednets and ‘Blisters’ for SPAQ/SMC. It’s a mandatory field.
Validation: The capacity input value must be numerical. Error message if the capacity is invalid ‘The value must be numerical’.
f. Submit - Once the vehicle details are entered here, the user will be directed to submit the details and the vehicle details will be saved in the MDMS for the instance.
Microplan hypothesis and formula configuration -
Actor: System administrator/Program manager
Administrative boundary: National/Country
Case A: When the resource distribution strategy is ‘House-to-House’ and the campaign type is either ‘Bednets’ or ‘SMC’
Sub-Case 1:
Figma sample for choosing preliminary questions (Resource distribution strategy = House-to-House):
Q1. How is the campaign registration process happening?
The user will have only one option to choose from the dropdown ‘House-to-House’
Q2. How is the campaign distribution process happening?
The user will have only one option to choose from the dropdown ‘House-to-House’
Q3. Is the registration and distribution process happening together or separately?
The user will have one of the two options to choose from the dropdown either ‘Together’ or ‘Separately’. Here, the user will choose ‘Together’.
Figma sample for assumption config 1 (Bednets):
Figma sample for assumption config 2 (Bednets):
Figma sample for assumption config 3 (Bednets):
Figma sample for assumption config 4 (Bednets):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
Figma sample for assumption config 1 (SMC):
Figma sample for assumption config 2 (SMC):
Figma sample for assumption config 3 (SMC):
Figma sample for assumption config 4 (SMC):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
In the above images, all the microplan hypotheses are pre-configured in the MDMS.
The user can add new microplan assumptions or delete an old assumption according to the campaign needs. All the microplan assumptions are configured for the village or lowest boundary level.
Upon adding a new microplan assumption, the user will be asked to enter the assumption and attach a value to it. The same assumption will be used in the microplan resource estimation formula.
If an assumption is deleted, upon adding a new assumption the user will be asked choose to either the deleted assumption or create a new assumption.
Depending on the microplan hypothesis configured, the user will be able to check-out the resource estimation formula and then make changes in the formula configuration accordingly.
Figma sample for formula config 1 (Bednets):
Figma sample for formula config 2 (Bednets):
Figma sample for formula config 3 (Bednets):
Figma sample for formula config 4 (Bednets):
Figma sample for formula config 1 (SMC):
Figma sample for formula config 2 (SMC):
Figma sample for formula config 3 (SMC):
Figma sample for formula config 4 (SMC):
In the above images, all the microplan resource estimation formulas are pre-configured in the MDMS.
The user can add a new estimation formula or delete an old formula according to the campaign needs. All the microplan estimation formulas are configured on the village or lowest boundary level. All the values shown will be auto reflected in the microplan estimation dashboard, unless the user wants to disable the ‘Show on estimation dashboard’ checkbox.
If a pre-defined formula is deleted, upon adding a new formula, the user should get an option either to add the deleted formula or add a completely new formula.
Upon adding a completely new estimation formula, the user will be asked to -
Enter the parameter of the resource estimation
Formula inputs
Operator (*,-,+,/)
Eg: Number of bednets (Resource estimation parameter) = Target population (Input) / Number of people per bednet (Input)
Sub-Case 2:
Figma sample for choosing preliminary questions (Resource distribution strategy = House-to-House):
Q1. How is the campaign registration process happening?
The user will have only one option to choose from the dropdown ‘House-to-House’
Q2. How is the campaign distribution process happening?
The user will have only one option to choose from the dropdown ‘House-to-House’
Q3. Is the registration and distribution process happening together or separately?
The user will have one of the two options to choose from the dropdown either ‘Together’ or ‘Separately’. Here, the user will choose ‘Separately’.
Figma sample for assumption config 1 (Bednets):
Figma sample for assumption config 2 (Bednets):
Figma sample for assumption config 3 (Bednets):
Figma sample for assumption config 4 (Bednets):
Figma sample for assumption config 5 (Bednets):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
Figma sample for assumption config 1 (SMC):
Figma sample for assumption config 2 (SMC):
Figma sample for assumption config 3 (SMC):
Figma sample for assumption config 4 (SMC):
Figma sample for assumption config 5 (SMC):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
In the above images, all the microplan hypotheses are pre-configured in the MDMS.
The user can add new microplan assumptions or delete an old assumption according to the campaign needs. All the microplan assumptions are configured on the village or lowest boundary level.
Upon adding a new microplan assumption, the user will be asked to enter the assumption and attach a value to it. The same assumption will be used in the microplan resource estimation formula. If an assumption is deleted, upon adding a new assumption the user will be asked to choose to either the deleted assumption or create a new assumption.
Depending on the microplan hypothesis configured, the user will be able to check-out the resource estimation formula and then make changes in the formula configuration accordingly.
Figma sample for formula config 1 (Bednets):
Figma sample for formula config 2 (Bednets):
Figma sample for formula config 3 (Bednets):
Figma sample for formula config 4 (Bednets):
Figma sample for formula config 5 (Bednets):
Figma sample for formula config 1 (SMC):
Figma sample for formula config 2 (SMC):
Figma sample for formula config 3 (SMC):
Figma sample for formula config 4 (SMC):
Figma sample for formula config 5 (SMC):
In the above images, all the microplan resource estimation formulas are pre-configured in the MDMS.
The user can add a new estimation formula or delete an old formula according to the campaign's needs. All the microplan estimation formulas are configured on the village or lowest boundary level. All the values shown will be auto-reflected in the microplan estimation dashboard unless the user wants to disable the "Show on estimation dashboard" checkbox.
If a pre-defined formula is deleted, upon adding a new formula, the user should get an option either to add the deleted formula or add a completely new formula.
Upon adding a new estimation formula, the user will be asked to -
Enter the parameter of the resource estimation
Formula inputs
Operator (*,-,+,/)
Example: Number of bednets (Resource estimation parameter) = Target population (Input) / Number of people per bednet (Input)
Case B: When the resource distribution strategy is ‘Fixed post’ and the campaign type is either ‘Bednets’ or ‘SMC’
Sub-case 1:
Figma sample for choosing preliminary questions (Resource distribution strategy = Fixed post):
Q1. How is the campaign registration process happening?
The user will have only one option to choose from the dropdown ‘Fixed post’
Q2. How is the campaign distribution process happening?
The user will have only one option to choose from the dropdown ‘Fixed post’
Q3. Is the registration and distribution process happening together or separately?
The user will have one of the two options to choose from the dropdown either ‘Together’ or ‘Separately’. Here, the user will choose ‘Together’.
Figma sample for assumption config 1 (Bednets):
Figma sample for assumption config 2 (Bednets):
Figma sample for assumption config 3 (Bednets):
Figma sample for assumption config 4 (Bednets):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
Figma sample for assumption config 1 (SMC):
Figma sample for assumption config 2 (SMC):
Figma sample for assumption config 3 (SMC):
Figma sample for assumption config 4 (SMC):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
In the above images, all the microplan hypotheses are pre-configured in the MDMS.
The user can add new microplan assumptions or delete an old assumption according to the campaign needs. All the microplan assumptions are configured on the village or lowest boundary level.
Upon adding a new microplan assumption, the user will be asked to enter the assumption and attach a value to it. The same assumption will be used in the microplan resource estimation formula.
If an assumption is deleted, upon adding a new assumption the user will be asked to choose to either delete the assumption or create a new assumption.
Depending on the microplan hypothesis configured, the user will be able to check the resource estimation formula and then make changes in the formula configuration accordingly.
Figma sample for formula config 1 (Bednets):
Figma sample for formula config 2 (Bednets):
Figma sample for formula config 3 (Bednets):
Figma sample for formula config 4 (Bednets):
Figma sample for formula config 1 (SMC):
Figma sample for formula config 2 (SMC):
Figma sample for formula config 3 (SMC):
Figma sample for formula config 4 (SMC):
In the above images, all the microplan resource estimation formula are pre-configured in the MDMS.
The user can add a new estimation formula or delete an old formula according to the campaign's needs. All the microplan estimation formulas are configured on the village or lowest boundary level. All the values shown will be auto-reflected in the microplan estimation dashboard unless the user wants to disable the "Show on estimation dashboard" checkbox.
If a pre-defined formula is deleted, upon adding a new formula, the user should get an option either to add the deleted formula or add a completely new formula.
Upon adding a new estimation formula, the user will be asked to -
Enter the parameter of the resource estimation
Formula inputs
Operator (*,-,+,/)
Example: Number of bednets (Resource estimation parameter) = Target population (Input) / Number of people per bednet (Input)
Sub-case 2:
Figma sample for choosing preliminary questions (Resource distribution strategy = Fixed post):
Q1. How is the campaign registration process happening?
The user will have only one option to choose from the dropdown ‘Fixed post’
Q2. How is the campaign distribution process happening?
The user will have only one option to choose from the dropdown ‘Fixed post’
Q3. Is the registration and distribution process happening together or separately?
The user will have one of the two options to choose from the dropdown either ‘Together’ or ‘Separately’. Here, the user will choose ‘Separately’.
Figma sample for assumption config 1 (Bednet):
Figma sample for assumption config 2 (Bednet):
Figma sample for assumption config 3 (Bednet):
Figma sample for assumption config 4 (Bednet):
Figma sample for assumption config 5 (Bednet):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
Figma sample for assumption config 1 (SMC):
Figma sample for assumption config 2 (SMC):
Figma sample for assumption config 3 (SMC):
Figma sample for assumption config 4 (SMC):
Figma sample for assumption config 5 (SMC):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
In the above images, all the microplan hypotheses are pre-configured in the MDMS.
The user can add new microplan assumptions or delete an old assumption according to the campaign needs. All the microplan assumptions are configured on the village or lowest boundary level.
Upon adding a new microplan assumption, the user will be asked to enter the assumption and attach a value to it. The same assumption will be used in the microplan resource estimation formula.
If an assumption is deleted, upon adding a new assumption the user will be asked to choose to either the deleted assumption or create a new assumption.
Depending on the microplan hypothesis configured, the user will be able to check the resource estimation formula and then make changes in the formula configuration accordingly.
Figma sample for formula config 1 (Bednets):
Figma sample for formula config 2 (Bednets):
Figma sample for formula config 3 (Bednets):
Figma sample for formula config 4 (Bednets):
Figma sample for formula config 5 (Bednets):
Figma sample for formula config 1 (SMC):
Figma sample for formula config 2 (SMC):
Figma sample for formula config 3 (SMC):
Figma sample for formula config 4 (SMC):
Figma sample for formula config 5 (SMC):
In the above images, all the microplan resource estimation formulas are pre-configured in the MDMS.
The user can add a new estimation formula or delete an old formula according to the campaign's needs. All the microplan estimation formulas are configured on the village or lowest boundary level. All the values shown will be auto-reflected in the microplan estimation dashboard unless the user wants to disable the "Show on estimation dashboard" checkbox.
If a pre-defined formula is deleted, upon adding a new formula, the user should get an option either to add the deleted formula or add a completely new formula.
Upon adding a new estimation formula, the user will be asked to -
Enter the parameters of the resource estimation
Formula inputs
Operator (*,-,+,/)
Example: Number of bednets (Resource estimation parameter) = Target population (Input) / Number of people per bednet (Input)
Case C: When the resource distribution strategy is ‘Fixed post & House-to-House’ and the campaign type is either ‘Bednets’ or ‘SMC’
Figma sample for choosing preliminary questions (Resource distribution strategy = House-to-House & Fixed post):
Q1. How is the campaign registration process happening?
The user can choose either ‘Fixed post’ or ‘House-to-House’ or both
Q2. How is the campaign distribution process happening?
The user can choose either ‘Fixed post’ or ‘House-to-House’ or both
Depending on the registration and distribution process chosen, the microplan assumption will be shown to the user for configuration.
Figma sample for assumption config 1 (Bednets):
Figma sample for assumption config 2 (Bednets):
Figma sample for assumption config 3 (Bednets):
Figma sample for assumption config 4 (Bednets):
Figma sample for assumption config 5 (Bednets):
Figma sample for assumption config 6 (Bednets):
Figma sample for assumption config 7 (Bednets):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
Figma sample for assumption config 1 (SMC):
Figma sample for assumption config 2 (SMC):
Figma sample for assumption config 3 (SMC):
Figma sample for assumption config 4 (SMC):
Figma sample for assumption config 5 (SMC):
Figma sample for assumption config 6 (SMC):
Figma sample for assumption config 7 (SMC):
Validation: The input value of an assumption must be numerical and mandatory
Error message in case of invalid input “Please enter a numeric value”
In the above images, all the microplan hypotheses are pre-configured in the MDMS.
The user can add new microplan assumptions or delete an old assumption according to the campaign needs. All the microplan assumptions are configured on the village or lowest boundary level.
Upon adding a new microplan assumption, the user will be asked to enter the assumption and attach a value to it. The same assumption will be used in the microplan resource estimation formula.
If an assumption is deleted, upon adding a new assumption the user will be asked choose to either the deleted assumption or create a new assumption.
Depending on the microplan hypothesis configured, the user will be able to check the resource estimation formula and then make changes in the formula configuration accordingly.
In the above images, all the microplan resource estimation formulas are pre-configured in the MDMS.
The user can add a new estimation formula or delete an old formula according to the campaign's needs. All the microplan estimation formulas are configured on the village or lowest boundary level. All the values shown will be auto-reflected in the microplan estimation dashboard unless the user wants to disable the ‘Show on estimation dashboard’ checkbox.
If a pre-defined formula is deleted, upon adding a new formula, the user should get an option either to add the deleted formula or add a completely new formula.
Upon adding a new estimation formula, the user will be asked to -
Enter the parameter of the resource estimation
Formula inputs
Operator (+,-,*,/)
Example: Number of bednets (Resource estimation parameter) = Target population (Input 1) / Number of people per bednet (Input 2)
Manage data validation -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This screen will be used to set up the data validation rule to highlight the population data discrepancies submitted by the ‘Data collector’ from the ground.
This process will help specifically in identifying if the population data collected and validated by the data collector for certain villages is correct or not. For example, the central team called out that a village has a total population of 2,000. However, while validating the data, the data collector at the village level mentioned that the total population of the village is 5000, which is more than 100% of what was earlier uploaded by the central team. With such cases, it becomes important for the data approver to have a second look at the data and make necessary adjustments in the village population data that can be used for microplan resource estimation.
The content of this screen are -
a. Minimum population of a village in Mozambique: In this field, the user needs to enter the minimum possible population of a village within the campaign region. This ensures that if the ‘Data collector’ validates and collects the total and target population for a village, which is less than the minimum village population configured, it should right away be highlighted to the assigned ‘Population data approver’ role. Here, the country name can be different for different countries, so it has to be configurable depending on the instance created for the country.
Validation: The field must accept a whole number value. Throw the error “Please enter a whole number” if an invalid value is entered.
b. The maximum population of a village in Mozambique: In this field, the user needs to enter the maximum possible population of a village within the campaign region. This ensures that if the ‘Data collector’ validates and collects the total and target population for a village, which is more than the maximum village population configured, it should right away be highlighted to the assigned ‘Population data approver’ role. Here, the country name can be different for different countries, so it has to be configurable depending on the instance created for the country.
Validation: The field must accept a whole number value. Throw the error “Please enter a whole number” if an invalid value is entered.
c. Acceptable change percentage (%) concerning population data uploaded for the villages: In this field, the user needs to enter the acceptable buffer % w.r.t to which the system will not highlight the data discrepancies. For example, if the acceptable change percentage is 10%, and the central team uploaded the total village population of Village-1 as 1000, then the acceptable population range is between 900 to 1100. So, if the ‘Data collector’ validates and collects the village-1 population as 1050, the system will not highlight the data discrepancies to the ‘Population data approver’ user, but if the ‘Data collector’ validates and collects the village-1 population as 1200, the system will highlight the data discrepancies to the ‘Population data approver’ user.
Validation: The field must accept a numeric value. Throw error “Please enter a numeric value” if invalid value entered.
d. Next: The user can move to the next screen to configure the role-action mapping
e. Back: The user can choose to go back to the previous screen of the estimation formula configuration by clicking ‘Back’
Note: The data validation rule configuration isn’t mandatory and the user can move to the next screen without configuration by clicking the ‘Next’ button
Configure access control -
Actor: System administrator/Program manager
Administrative boundary: National/Country
Role configuration - National microplan approver
This role will have access to edit microplan assumptions and approve and finalise microplan estimation for the country.
This screen will be used to configure the ‘National Microplan Estimation Approver’ user role. The assigned user will be able to validate and approve the population data from each village uploaded by the system administrator. The user will only be able to act on the population data of the villages that are assigned to his administrative boundary, i.e., country.
During the configuration of the microplan, there will be no users belonging to the ‘National microplan estimation approver’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign National Microplan Estimation Approvers’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign National Microplan Estimation Approvers’ button, he/she will be prompted a pop-up to assign the users with ‘National Microplan Estimation Approver’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin can search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be auto chosen as ‘Country’ as this user role belongs to the national level. The system administrator shouldn’t get any other administrative hierarchies to choose from.
Administrative area - This will be automatically chosen as the country where the microplan is being configured. The system administrator shouldn’t get any other administrative area to choose from.
Action - This capability will let the system administrator to assign/deassign users of the chosen role to the ongoing microplan. The system administrator can add at least one or more ‘National microplan estimation approver’ users to the ongoing microplan.
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user belonging to the role chosen.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. Content of the screen are -
Search assigned users - The system admin will be able to search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator to assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Note: It’s mandatory to assign at least 1 ‘National microplan estimation approver’ user to the microplan.
Role configuration - National facility catchment assigner
This role will have access to assign & finalize the facility to the catchment areas of the assigned administrative boundary.
This screen will be used to configure the ‘National facility catchment assigner’ user role. The assigned facility catchment assigner will be allowed to map the campaign facilities or point of services to the catchment areas and to finalize the facility-to-catchment area mapping (Eg: Villages) of the assigned boundaries.
During the configuration of the microplan, there will be no users belonging to the ‘National facility catchment assigner’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign National Facility Catchment Assigner’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign National Facility Catchment Assigner’ button, he/she will be prompted a pop-up to assign the users with the ‘National Facility Catchment Assigner’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin can search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be auto chosen as ‘Country’ as this user role belongs to the national level. The system administrator shouldn’t get any other administrative hierarchies to choose from.
Administrative area - This will be automatically chosen as the country where the microplan is being configured. The system administrator shouldn’t get any other administrative area to choose from.
Action - This capability will let the system administrator assign/deassign users of the chosen role to the ongoing microplan. The system administrator can add at least one or more ‘National facility catchment assigner’ users to the ongoing microplan.
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user belonging to the role chosen.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. The content of the screen are -
Search assigned users - The system admin can search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Note: It’s mandatory to assign at least 1 ‘National facility catchment assigner’ user to the microplan.
Role configuration - National population data approver
This role will have access to validate, approve, and finalise the population data for the villages of the assigned administrative boundary.
This screen will be used to configure the ‘National population data approver’ user role. The assigned user will be able to validate, update, and approve the population data of each village uploaded by the system administrator. The user will only be able to act on the population data of the villages that are assigned to his administrative boundary.
During the configuration of the microplan, there will be no users belonging to the ‘National population data approver’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign National Population Data Approver’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign National Population Data Approver’ button, he/she will be prompted a pop-up to assign the users with the ‘National Population Data Approver’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin can search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
The contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be auto-chosen as ‘Country’ as this user role belongs to the national level. The system administrator shouldn’t get any other administrative hierarchies to choose from.
Administrative area - This will be automatically chosen as the country where the microplan is being configured. The system administrator shouldn’t get any other administrative area to choose from.
Action - This capability will let the system administrator assign/deassign users of the chosen role to the ongoing microplan. The system administrator can add at least one or more ‘National population data approver’ users to the ongoing microplan.\
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user belonging to the role chosen.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. The content of the screen are -
Search assigned users - The system admin can search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Note: It’s mandatory to assign at least 1 ‘National population data approver’ user to the microplan.
Role configuration - Microplan estimation approver
This role will have access to edit microplan assumptions and approve microplan estimation of assigned administrative boundaries.
This screen will be used to configure the ‘Microplan estimation approver’ user role. The assigned Microplan estimation approver will be allowed to edit the microplan hypothesis, and validate and approve the microplan for the assigned administrative boundaries.
During the configuration of the microplan, there will be no users belonging to the ‘Microplan estimation approver’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign Microplan Estimation Approvers’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign Microplan Estimation Approvers’ button, he/she will be prompted a pop-up to assign the users with ‘Microplan Estimation Approvers’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin can search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
The contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - The system administrator will be able to choose the administrative hierarchy from the dropdown. The system admin can choose one administrative hierarchy at a time. The system admin can’t choose the highest administrative hierarchy (Eg: Country) and the lowest administrative hierarchy (Eg: Village/Settlement) from the dropdown.
Administrative area - Upon choosing the administrative hierarchy, the system administrator will be able to choose the administrative areas for the chosen administrative hierarchy. The system administrator will be able to choose one or multiple administrative areas at a time. The list of administrative areas should be shown along with their respective parent boundaries.
Action - This capability will let the system administrator assign/deassign users of the chosen role to the ongoing microplan.
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user in the selected role.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. The content of the screen are -
Search assigned users - The system admin can search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
The contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Validations for the ‘Microplan estimation approver’ role:
(Validation criteria for warning messages (Microplan estimation approver)
Role configuration - Microplan estimation viewer
This role will have access to view microplan estimations of assigned administrative boundaries.
This screen will be used to configure the ‘Microplan estimation viewer’ user role. The assigned microplan estimation viewer will be allowed to view the microplan estimation for the assigned administrative boundaries.
During the configuration of the microplan, there will be no users belonging to the ‘Microplan estimation viewer’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign Microplan Estimation Viewers’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign Microplan Estimation Viewers’ button, he/she will be prompted a pop-up to assign the users with the ‘Microplan Estimation Viewers’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin will be able to search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - The system administrator will be able to choose the administrative hierarchy from the dropdown. The system admin can choose one administrative hierarchy at a time. The system admin can’t choose the highest administrative hierarchy (Eg: Country) and the lowest administrative hierarchy (Eg: Village/Settlement) from the dropdown.
Administrative area - Upon choosing the administrative hierarchy, the system administrator will be able to choose the administrative areas for the chosen administrative hierarchy. The system administrator will be able to choose one or multiple administrative areas at a time. The list of administrative areas should be shown along with their respective parent boundaries.
Action - This capability will let the system administrator to assign/deassign users of the chosen role to the ongoing microplan.
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user belonging to the role chosen.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. Content of the screen are -
Search assigned users - The system admin will be able to search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator to assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Validations for the ‘Microplan estimation viewer’ role:
(Validation criteria for warning messages (Microplan estimation viewer)
Note: It’s not mandatory to assign the Microplan estimation viewer to a microplan. The system administrator can skip and go to the next role management screen without assigning the users with Microplan estimation viewer role.
Role configuration - Facility catchment assigner
This role will have access to assign the facility to the catchment areas of the assigned administrative boundary.
This screen will be used to configure the ‘Facility catchment assigner’ user role. The assigned facility catchment assigner will be allowed to map the campaign facilities or point of services to the catchment areas (Eg: Villages/Settlements) of the assigned boundaries.
During the configuration of the microplan, there will be no users belonging to the ‘Facility catchment assigner’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign Facility Catchment Assigner’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign Facility Catchment Assigner’ button, he/she will be prompted a pop-up to assign the users with ‘Facility Catchment Assigner’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin will be able to search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - The system administrator will be able to choose the administrative hierarchy from the dropdown. The system admin can choose one administrative hierarchy at a time. The system admin can’t choose the highest administrative hierarchy (Eg: Country) and the lowest administrative hierarchy (Eg: Village/Settlement) from the dropdown.
Administrative area - Upon choosing the administrative hierarchy, the system administrator will be able to choose the administrative areas for the chosen administrative hierarchy. The system administrator will be able to choose one or multiple administrative areas at a time. The list of administrative areas should be shown along with their respective parent boundaries.
Action - This capability will let the system administrator to assign/deassign users of the chosen role to the ongoing microplan.
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user belonging to the role chosen.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. Content of the screen are -
Search assigned users - The system admin will be able to search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator to assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Validations for ‘Facility catchment assigner’ role:
(Validation criteria for warning messages (Facility catchment assigner)
Note: It’s not mandatory to assign Facility catchment assigner to a microplan. The system administrator can skip and go to the next role management screen without assigning the users with Facility catchment assigner role.
Role configuration - Population data approver
This role will have access to validate & approve the population data for the villages of the assigned administrative boundary.
This screen will be used to configure the ‘Population data approver’ user role. The assigned user will be able to validate and approve the population data uploaded by the system administrator while setting up the microplan. The user will only be able to act on the population data of the villages that are assigned to his administrative boundaries.
During the configuration of the microplan, there will be no users belonging to the ‘Population data approver’ role assigned to the ongoing microplan at first. The system administrator will have to click on the button ‘Assign Population Data Approver’ to start assigning the required users to the ongoing microplan.
Once the system administrator clicks on the ‘Assign Population Data Approver’ button, he/she will be prompted a pop-up to assign the users with ‘Population Data Approver’ role to the ongoing microplan.
Here, the system admin will be able to assign/deassign a user to the ongoing microplan. The content of the pop-up are -
Search filters - The system admin will be able to search a user using the ‘User’s name’ and ‘User’s contact number’.
Validation: Partial string search should be allowed
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - The system administrator will be able to choose the administrative hierarchy from the dropdown. The system admin can choose one administrative hierarchy at a time. The system admin can’t choose the highest administrative hierarchy (Eg: Country) and the lowest administrative hierarchy (Eg: Village/Settlement) from the dropdown.
Administrative area - Upon choosing the administrative hierarchy, the system administrator will be able to choose the administrative areas for the chosen administrative hierarchy. The system administrator will be able to choose one or multiple administrative areas at a time. The list of administrative areas should be shown along with their respective parent boundaries.
Action - This capability will let the system administrator to assign/deassign users of the chosen role to the ongoing microplan.
This pop-up shows the actions that the user can take. The ‘Assign’ button should only be enabled if the system administrator has chosen the administrative hierarchy and the administrative area for a particular user belonging to the role chosen.
Once the system administrator has assigned all the required users to the microplan, the list of assigned users and their details will be displayed on the screen. Content of the screen are -
Search assigned users - The system admin will be able to search a user using the ‘User’s name’.
Validation: Partial string search should be allowed
Assign users - This action will let the system administrator to assign/deassign users to the microplan.
Name of the user - This will be fetched from the user management module for the chosen role.
Contact number of the user - This will be fetched from the user management module for the chosen role.
Email ID of the user - This will be fetched from the user management module for the chosen role.
Administrative hierarchy - This will be fetched from the user data that will be used while assigning the user to the microplan.
Administrative area - This will be fetched from the user data that will be used while assigning the user to the microplan.
Once all the required users are added to the microplan, the system administrator will click on the ‘Save And Proceed’ button to go to the next role assignment screen.
Validations for ‘Population data approver’ role:
(Validation criteria for warning messages (Population data approver
Note: It’s not mandatory to assign Population data approver to a microplan. The system administrator can skip and go to the next role management screen without assigning the users with Population data approver role.
View summary page -
Actor: System administrator/Program manager
Administrative boundary: National/Country
Once the microplan setup is completed, the user can review all the data configured before finalizing the microplan setup. The summary page will give the user the ability to review the configured data for each module. The summary page will let users edit the configured data if required.
The user will be allowed to edit each section of the summary screen as required.
The user will be allowed to download the uploaded file wherever there is file uploaded.
Once clicked on the ‘Edit’ button, the user will be redirected to the section of the microplan setup that needs to be edited.
Upon finalisation, the user will click on the ‘Complete setup’ button to complete the microplan setup for the supervisors to use further.
Sending email notifications to Microplan users -
Actor: System administrator/Program manager
Administrative boundary: National/Country
Once the microplan setup is completed, the users whose roles are configured by the system administrator will get an email notification mentioning their user login credentials and URL to the microplan platform or the data collection app. The email will be sent to the users who have valid email IDs registered during the role mapping. The email will also be sent to a common email address that is accessible by the supervisors.
Note: This should be configurable. If the implementation partner wants to enable email notification, then we should enable this.
Email for the microplan platform users
Content of the email of microplanning users:
From: Email of the implementation partner
To: Registered microplan user’s email ID and the common email ID of the implementation partner
Subject: Login credentials for microplanning platform
Body:
Hi {User’s name},
Below are the login credentials to access the microplanning platform -
URL: {website URL}
Username: {Username}
Password: {Password}
Thank you,
{Implementation partner}
Validation: If a new user is created post-microplan setup, the email will be sent to the new user only.
Email for the data collectors
Content of the email of data collector users:
From: Email of the implementation partner
To: Registered data collector email ID and the common email ID of the implementation partner
Subject: Login credentials for data collection app
Body:
Hi {User’s name},
Below are the login credentials to access the data collection app -
App link: {App download link}
Username: {Username}
Password: {Password}
Thank you,
{Implementation partner}
Landing page for system administrators -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This is the landing page for the system administrator where the user can perform 3 actions:
Setup Microplan: The system administrator will be able to set up the microplan from scratch for a campaign
Open microplans: The system administrator will be able to see the list of campaign microplans in this page and perform certain actions on each microplan, if required
User management: The system administrator will be able to manage microplanning users using the user management module
Logout: The system administrator will be able to log out from the dashboard if he is not required to perform any action
‘Open saved microplans’ module:
This is the screen for the system administrator to check out the list of microplans and perform certain actions if required
Content of the screen:
Search microplan: The user can search microplan using the microplan name. The search can be a partial string match to show the list of microplans that have partially matching string that is typed
Tab filter based on microplan status: The user will be able to filter out and see the list of microplans concerning the microplan status. The microplan status are -
- All - This is default tab that will be chosen where the user can see the list of all microplans irrespective of their status
- Drafted setup - This is the status of the microplan when the system admin has partially configured the microplan and hasn’t completed the setup yet
- Completed setup - This is the status of the microplan when the system admin has created the microplan setup and the microplanning users haven’t yet opened the microplan to perform the activities (approve population data, facility catchment mapping, edit/approve microplan estimation, etc.) defined as per the role. This status will be fetched from the Microplan dashboard of the supervisors.
- Validation in progress - This is the status of the microplan when the user has started working on the microplan. This status will be fetched from the Microplan dashboard of the microplanning users.
- Microplan finalised - This is the status of the microplan when the user has performed all the activities on the microplan and finalised the microplan estimation. This status will be fetched from the Microplan dashboard of the microplanning users.
Microplan name: This shows the name of the microplan that the user has set while setting up the microplan
Microplan status: This shows the different status of a microplan while the microplan goes through a series of operational changes.
Campaign disease: This shows the campaign disease for which the microplan is being configured
Campaign type: This shows the type of campaign for which the microplan is being configured
Distribution strategy: This shows the distribution strategy to be used for the campaign execution
Action: The user will be able to perform certain actions on the microplan. The actions are -
- Edit setup - The user will be able to edit any or all of the segments of the microplan (Except campaign details segment) when the status of the microplan is ‘Drafted setup’. Once the status of the microplan changes to ‘Validation in progress’ or ‘Completed setup’, then the system administrator will be able to edit only the ‘User access management’ segment for edit, add or remove microplanning users.
- View summary - The user will be able to view a summary of the microplan that is setup successfully. The status of the microplan should be ‘Completed setup’, ‘Validation in progress’ and ‘Finalised microplan’. If microplan status is ‘Drafted setup’, the ‘View summary’ option should be hidden for the microplan from action dropdown.
- Duplicate setup - The user will be able to copy the setup configuration of the microplan and create a new microplan with a new name and copied microplan data. On click of ‘Copy’, the user will be re-directed to the first screen of the microplan setup with details already filled. The status of the microplan should be ‘Completed setup’, ‘Validation in progress’ and ‘Finalized microplan’. If microplan status is ‘Drafted setup’, the ‘Duplicate setup’ option should be hidden for the microplan from action dropdown.
‘User management’ module:
This is the screen for managing the users for the microplanning platform by the system administrator.
Content of the screen -
Name search - The system administrator should be able to search for the registered user using his/her name.
Contact number search - The system administrator should be able to search for the registered user using his/her mobile number.
Role filters - The system administrator should be able to filter the users registered in the microplanning platform using the role filters.
User details - This will have the required details of the registered users such as:
Name
Contact number
Role
Edit user details - Each user row should be clickable and on click of that, health HRMS edit user screen will open up. The user can edit below fields -
Name of the user
Email ID of the user
Add/remove user’s role
Activate/Deactivate the user
Bulk upload users - This is the capability that the system admin will have to add new users to the microplanning platform.
The template for bulk upload users is here
Here, the system admin can upload the user details by filling up the template attached above. All uploaded users will be part of the microplanning platform. The uploaded users will be able to access the microplans that they will be assigned to using the access control configuration.
The content of the template are -
Read me - This sheet will have the details of how to fill the user template excel and upload it for user registration.
User roles - This sheet will have the list of roles available for user registration and the description of each role.
Role mapping for each sheet - There will be a sheet defined in the template for each role available. Inside each of the role sheet, the system admin can fill user details with -
- Name - Name of the user who will be using the microplanning platform.
Validation: This is a mandatory field in the template.
- Contact number - Contact number of the person who will be using the microplanning platform.
Validation: This is a mandatory field in the template.
- Email ID - Email ID of the person who will be using the microplanning platform.
Validation of the template uploaded -
The name is the mandatory column to be filled by the system admin in the upload template. If the name is missing for the microplanning users while uploading the template, then show error ‘The ‘name’ is a mandatory field in the file, please update and re-upload’.
The contact number is the mandatory column to be filled by the system admin in the upload template. If the contact number is missing for the microplanning users while uploading the template, then show error ‘The ‘contact number’ is a mandatory field in the file, please update and re-upload’.
There should be a validation on contact number w.r.t the countries. If the contact number isn’t matching with the country’s standard structure, then show the error message ‘The ‘contact number’ entered is invalid, please update and re-upload’.
There should be proper regex validation on the emila ID entered. The system should only accept the email ID that matches with the email format such as ‘abc@abc.abc’. If the entered email ID doesn’t match the proper email structure, then show error message ‘The ‘email ID’ entered is invalid, please update and re-upload’.
There can’t be duplicate users uploaded in the system. If a contact number of a microplanning user is already registered, then show an error message ‘An user with duplicate contact details already exists in the system’.
While uploading the template, if a user with the same contact number exists in a different role sheet with different name or email ID, show an error message ‘User details for the same contact number isn’t matching. Please check the user’s name or email ID.’
A user with ‘Microplan approver’ role can’t be assigned to ‘National microplan approver’ role. If this is the case, show an error message ‘An user with Microplan approver role can’t be assigned to National microplan approver role.’
A user with the ‘Facility catchment assigner’ role can’t be assigned to the ‘National facility catchment assigner’ role. If this is the case, show an error message ‘An user with Facility catchment assigner role can’t be assigned to National facility catchment assigner’.
A user with the ‘Population data approver’ role can’t be assigned to ‘National population data approver’ role. If this is the case, show an error message ‘An user with Population data approver role can’t be assigned to National population data approver’.
Note: Use the same format of showing errors in the user upload module as the ‘Data management - Population upload’ module.
When the user file is successfully uploaded, below is the UI that shows the file uploaded -
The user can download the file that is already uploaded
The user can re-upload the uploaded file if required
The user can view the content of the uploaded file by clicking on the file name, that is uploaded
Download user data -
This is the capability that will be used by the system administrator to download the user credentials of the registered users.
Content of the screen:
File name and attachment - This will have the name of the file with a hyperlink to view & download the file.
- The downloaded file will have all the details of the file that was uploaded, alongwith the user login credentials for each of the users in the file.
- The downloaded file will have the login credentials that were generated by the system itself for the first time when the file was uploaded and submitted successfully.
File uploaded by - This will show the name of the system administrator who had uploaded and submitted the file.
File uploaded time - This will show the timestamp of the file uploaded by the system administrator.
Validation: The timestamp needs to be in the international format of “DD MMM YYYY, HH:MM AM/PM”.
13. Showing ‘Last updated by’ information -
There is a possibility that multiple system administrators are working on the same microplan, to keep the traceability of who made the last changes, it’s important to show the ‘Last updated by “user’s name” at DD:MM:YYYY HH:MM’ in the dashboard for easy identification and traceability.
Editing of microplan setup -
Actor: System administrator/Program manager
Administrative boundary: National/Country
This will let the user edit the microplan setup as required.
The user will be able to edit any or all of the segments of the microplan (Except campaign details and campaign name segment) when the status of the microplan is ‘Drafted setup’.
Once the status of the microplan changes to ‘Completed setup’, ‘Validation in progress’, then the system administrator will be able to edit only the user access control/role management segment for assign/deassign a user to the microplan.
What are the changes that can be made in the microplan setup and what impact will it have on other modules?
The campaign details segment can’t be changed once the user goes to the next screen. There should be a warning pop-up to be shown to the user once the user clicks on the ‘Save & Next’ button.
Warning message: The campaign details can not be changed once saved, please confirm?
Action: The user can either ‘Cancel’ or ‘Confirm’
The microplan name can’t be changed once the user goes to the next screen. There should be a warning pop-up to be shown to the user once the user clicks on the ‘Save & Next’ button.
Warning message: The campaign name can not be changed once saved, please confirm?
Action: The user can either ‘Cancel’ or ‘Confirm’
The user can come back and make changes or update the boundary data. There should be a one-time pop-up/user consent to be shown to the user once the user tries to select a new boundary or unselect an already selected boundary.
Warning message: The uploaded population and facility data will be affected if you make changes to the boundary.
Action: The user can either click on ‘No, I don’t want to change’ or ‘Yes, I want to change’.
The user can come back and make changes or update the data management content. No warning messages will be displayed.
The user can come back and make changes or update the microplan assumption questionnaire. There should be a one-time pop-up/user consent to be shown to the user once the user tries to change any of the question’s dropdown or radio buttons.
Warning message: The campaign assumptions and formula configurations will be affected if you make changes to the questions.
Action: The user can either click on ‘No, I don’t want to change’ or ‘Yes, I want to change’.
The user can come back and make changes or update the microplan assumptions values, if already saved. No warning messages will be displayed.
The user can come back and make changes or update the microplan formula configurations. No warning messages will be displayed.
The user can come back and make changes or update the user management module such as add/remove users to the microplan. No warning messages will be displayed.
Data collector’s flow:
Data collector app -
Actor: Data collector
Administrative boundary: Village/Lowest boundary hierarchy
This app will be used by the users with the ‘Data collector’ role to collect the village population data, along with other geographical information. The user’s goal is to make sure that the correct population and geographical data have been collected for the villages to make an informed microplan estimation.
Note: The app functionalities should be offline first
Content of the screen -
User ID: The data collector will have to enter the username that he has received for logging in and collecting the village data.
Password: The data collector will have to enter the password that he has received for logging in and collecting the village data. The password will be hidden while typing in.
View password: The user can view the password that he has entered.
Login: This is the action button using which the user will log in and land on the homepage.
Forgot password?: If the user forgets his password, the user can click on the ‘Forgot password’ button and the app should give the message “Please connect with your supervisor or administrator to retrieve the password”
Choose language: The user will be able to choose the language for the app content.
Content of the screen -
Population: Upon logging in, the user will land on the homepage where the ‘Population’ functionality will let the user collect village population data for the respective villages
Data sync: If the data is submitted in the absence of internet connection, the data will not be synced with the server. In such cases, the user can see how many records are being unsynced and needs proper internet connection to sync with the server.
Note: Auto data sync needs to be enabled. So, whenever there is an internet connection, the app should auto sync the unsynced data.
Logout: The user can logout from the application by navigating to the hamburger menu and clicking on the logout button. The user will be redirected to the login page accordingly.
Help: The user can understand the modules present in the screen by clicking on ‘help’ button. Help information for the ‘Population’ module - ‘The user can collect population and related information for every assigned boundaries’
Content of the screen -
Search enabled dropdown: The user will be asked to select the village for which the population data needs to be collected. This will be a search enabled dropdown where the user can search for the specific village assigned to him. All the villages should be listed in the dropdown in alphabetical order.
Submitted village data: The user will be able to see the villages whose data has already been submitted. The ‘tick’ mark shows that the village data for that specific village has been collected already. The user can only view the data for those villages where the data has been collected and submitted.
Back: The user will be able to go back to the homepage using the ‘Back’ button.
Content of the screen for bednet campaign data collection form -
Village name: The user will be able to see which village he/she has chosen on the screen.
Uploaded village population: The user will be able to see the uploaded village population, which is the total village population data that was uploaded by the system admin while setting up the microplan.
Uploaded target population: The user will be able to see the uploaded target population of the village, which is the targeted village population data that was uploaded by the system admin while setting up the microplan.
Confirm the total population of the village: The user will be asked to confirm the total population of the village. It’s a mandatory input field.
Validation: The input value should be a whole number. If it’s an invalid entry, show the error message ‘Please enter a whole number’.
Confirm the target population of the village: The user will be asked to confirm the target population of the village. It’s a mandatory input field.
Validation: The input value should be a whole number. If it’s an invalid entry, show the error message ‘Please enter a whole number’.
Accessibility section - Choose village road condition: The user will be asked to choose the village road condition. It’s a dropdown and the user will be given 4 options to choose from -
a. Concrete
b. Gravel
c. Dirt
d. No road
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Accessibility section - Choose village terrain:The user will be asked to choose the village terrain structure. It’s a dropdown and the user will be given 4 options to choose from -
a. Mountain
b. Forest
c. Desert
d. Plain
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Accessibility section - Choose transportation mode to the village: The user will be asked to choose the transportation access to the village. It’s a checkbox-enabled dropdown and the list will be populated depending on the vehicles configured for the campaign by the system administrator while doing the microplan setup. The data collector can choose multiple transportation options as it’s going to be checkboxes. If the user doesn’t find the option to choose, he will choose ‘Others’.
If the user chooses ‘Others’ as the option, he will be asked to ‘Enter the transportation mode’.
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Security section - Is your village prone to civil unrest like violent protests, riots, etc.?: The user will be asked to choose how prone the village is to civil unrest or protest. Below are the options given to the user to choose from -
a. All the time (Atleast once a month)
b. Often (Atleast once a year)
c. Rarely (Once in 2-3 years)
d. Never
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Security section - How often do the security forces patrol the village?: The user will be asked how often do the security forces patrol the village. It’s a dropdown option for the user to choose from. Below are the options given to the user to choose from -
a. Everyday
b. Often (Atleast once a week)
c. Rarely (Once in a month)
d. Never
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Comment: Before submission of the collected data, the user needs to add a comment. It’s a mandatory input field.
Validation: The maximum length of the comment is 140 characters. If the user tries to submit the data without adding a comment, then show the error message “Please enter comment before submission”.
Submit: Once the data form is filled and submitted, the user will be redirected to the village selection page to select a new village for data collection.
Note: If the programme requires deleting existing content or adding new information with multiple dropdown choices or input values in the screen, that should be done by the impel team.
Once the data is filled, the data collector will submit the data, which will be reviewed and taken action by the ‘Population data approver’ role user.
If the user chooses a village, whose data has already been collected and submitted, then he will be able to review the submitted data.
If the user clicks on ‘Back’, the user will be redirected to the village selection screen to choose a new village for data collection and submission.
Content of the screen for SMC campaign data collection form -
Village name: The user will be able to see which village he/she has chosen on the screen.
Uploaded village population: The user will be able to see the uploaded village population, which is the total village population data that was uploaded by the system admin while setting up the microplan.
Uploaded target population (Age 3-11 months): The user will be able to see the uploaded target population between the age 3-11 months of the village, which is the targeted village population data that was uploaded by the system admin while setting up the microplan.
Uploaded target population (Age 12-59 months): The user will be able to see the uploaded target population between the ages 12-59 months of the village, which is the targeted village population data that was uploaded by the system admin while setting up the microplan.
Confirm the total population of the village: The user will be asked to confirm the total population of the village. It’s a mandatory input field.
Validation: The input value should be a whole number. If it’s an invalid entry, show the error message ‘Please enter a whole number’.
Confirm target population of the village (Age 3-11 months): The user will be asked to confirm the target population of the village between the ages 3-11 months. It’s a mandatory input field.
Validation: The input value should be a whole number. If it’s an invalid entry, show the error message ‘Please enter a whole number’.
Confirm target population of the village (Age 12-59 months): The user will be asked to confirm the target population of the village between the ages 12-59 months. It’s a mandatory input field.
Validation: The input value should be a whole number. If it’s an invalid entry, show the error message ‘Please enter a whole number’.
Accessibility section - Choose village road condition: The user will be asked to choose the village road condition. It’s a dropdown and the user will be given 4 options to choose from -
a. Concrete
b. Gravel
c. Dirt
d. No road
Note: The option can be kept enabled/disabled depending on the program’s requirements.
9. Accessibility section - Choose village terrain: The user will be asked to choose the village terrain structure. It’s a dropdown and the user will be given 4 options to choose from -
a. Mountain
b. Forest
c. Desert
d. Plain
Note: The option can be kept enabled/disabled depending on the program’s requirements.
10. Accessibility section - Choose transportation mode to the village: The user will be asked to choose the transportation access to the village. It’s a checkbox-enabled dropdown and the list will be populated depending on the vehicles configured for the campaign by the system administrator. The data collector can choose multiple transportation options as it’s going to be checkboxes. If the user doesn’t find the option to choose, he will choose ‘Others’.
If the user chooses ‘Others’ as the option, he will be asked to ‘Enter the transportation mode’.
Note: The option can be kept enabled/disabled depending on the program’s requirements.
11. Security section - Is your village prone to civil unrest like violent protests, riots, etc.?: The user will be asked to choose how prone the village is to civil unrest or protest. Below are the options given to the user to choose from -
All the time (Atleast once a month)
Often (Atleast once a year)
Rarely (Once in 2-3 years)
Never
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Security section - How often do the security forces patrol the village?: The user will be asked how often the security forces patrol the village. It’s a dropdown option for the user to choose from. Below are the options given to the user to choose from -
a. Everyday
b. Often (Atleast once a week)
c. Rarely (Once in a month)
d. Never
Note: The option can be kept enabled/disabled depending on the program’s requirements.
Comment: Before submission of the collected data, the user needs to add a comment.
Validation: The maximum length of the comment is 140 characters. If the user tries to submit the data without adding a comment, then show the error message “Please enter comment before submission”.
Submit: Once the data form is filled and submitted, the user will be redirected to the village selection page to select a new village for data collection.
Note: If the program requires deleting existing content or adding new information with multiple dropdown choices or input values in the screen, that should be done by the impel team.
Once the data is filled, the data collector will submit the data, which will be reviewed and taken action by the ‘Population data approver’ role user.
Supervisor’s flow :
Landing page for the supervisors -
Actor: Supervisor (Population data approver, Microplan viewer, Microplan approver, and Facility catchment mapper)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second lowest boundary)
Once the supervisor logs in using the login credentials received via email, the supervisor will be able to perform only 2 actions here -
Open microplans: The user will be able to click on ‘My Microplan’ to get the list of all the microplans that he is part of. If a user is a part of 1 or more campaign microplanning processes, he/she will be able to see the list after he clicks on the ‘My Microplan’ link.
Logout: The supervisor will be able to log out from the dashboard if he is not required to perform any action.
Content of the screen:
Search microplan: The user can search microplan using the microplan name. The search can be a partial string match to show the list of microplans that have a partially matching string that is typed
Tab filter based on microplan status: The user will be able to filter out and see the list of microplans concerning the microplan status. The status are -
- All - By default ‘All’ tab will be chosen and the user will be able to see all the microplans that are assigned to him irrespective of the microplan status.
- Execution to be done - This is the status of the microplan when the user hasn’t yet opened the microplan to perform the activities (approve population data, facility catchment mapping, edit/approve microplan estimation, etc.) defined as per the role.
- Execution in progress - This is the status of the microplan when the user has started working on the microplan by clicking on the ‘Start’ button.
Validation: The user with the ‘Population data approver’ role will be able to click on ‘Start’ as without the population data being approved, the microplan estimation won’t be executed. For other roles, the ‘Start’ button should be disabled.
- Execution done - This is the status of the microplan when the user has performed all the activities on the microplan and finalized the microplan estimation.
Microplan name: This shows the name of the microplans that are assigned to the user.
Microplan status: This shows the different status of a microplan while the microplan goes through a series of operational changes.
Campaign disease: This shows the campaign disease for which the microplan is being configured.
Campaign type: This shows the type of campaign for which the microplan is being configured.
Distribution strategy: This shows the distribution strategy to be used for the campaign execution.
Action: The user will be able to perform certain actions on the microplan. The actions are -
- Start - When the microplan status is ‘Execution to be done’, that means the work on microplan hasn’t yet started by any of the users. And this is when the ‘Start’ button will be reflected corresponding to the microplan. When the user clicks on the ‘Start’ button, the status will change to ‘Execution in progress’.
- Edit - When the microplan status is ‘Execution in progress’, that means the working on microplan has started by any of the users. And this is when the ‘Edit’ button will be reflected corresponding to the microplan.
- Download estimation - When the microplan status is ‘Execution done’, that means the microplan estimation has been finalized by the national level user. And this is when the ‘Download estimation’ button will be reflecting corresponding to the microplan. The user will be able to download the excel file of the microplan estimation.
Multi-role activity view -
Actor: Supervisor (Population data approver, Microplan viewer, Microplan approver and Facility catchment mapper)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second lowest boundary)
This view will give the users the activities they can perform on the platform concerning the role assigned to them. A user can be assigned to multiple roles, and depending on the role assigned the user will be able to see the options on the screen.
Once the user takes an action of ‘Start’ or ‘Edit’ for a microplan, the user will be redirected to this available activity screen where the user will be able to take appropriate actions as per the role defined. The activities that will be listed are -
the Approve population data - A user with ‘Population data approver’ role will be able to see the action tab of ‘Approve population data’.
Assign facilities to villages - A user with the ‘Facility catchment mapper’ role will be able to see the action tab of ‘Assign facilities to villages’.
Geospatial map view - Any microplan user irrespective of role defined will be able to see this action tab.
Approve microplan estimations - A user with ‘Microplan approver’ role will be able to see the action tab of ‘Approve microplan estimations’.
View microplan estimations - A user with ‘Microplan viewer’ role will be able to see the action tab of ‘View microplan estimations’.
To access the ‘Assign facilities to villages’ tab, it’s important that the country level ‘Population data approver’ finalizes the population data for the campaign boundary. If the population data is not finalized, then the ‘Assign facilities to villages’ tab will be disabled and users will be able to see a message “The population data for the microplan hasn’t been approved yet. Please come back later.” on hovering over the ‘Assign facilities to villages’ tab.
To access the ‘Geospatial map view’, ‘Approve microplan estimations’ and ‘View microplan estimations’ tabs, it’s important that the country level ‘Facility catchment mapper’ finalizes the facility-to-catchment mapping for all the villages within the campaign zone. If the facility-catchment mapping is not finalized, then the ‘Geospatial map view’, ‘Approve microplan estimations’ and ‘View microplan estimations’ tabs will be disabled and users will be able to see a message “The facility to catchment area assignment for the microplan hasn’t been finalised yet. Please come back later.” on hovering over the ‘Assign facilities to villages’ tab.
Population data approver flow -
Actor: Supervisor (Population data approver)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second last boundary)
This is the flow for approving the village population data that is either uploaded by the system admin or collected by the data collector. Approving population data is crucial as the microplan estimation will be happening concerning the population of the village that is approved.
Population data approvers can act on different administrative hierarchies and depending on the hierarchy and boundaries assigned, the villages will be assigned to the user for approving the population data. For example, the Population data approver can belong to a country, province, district, administrative post, locality and with respect to the boundaries assigned, he will be able to see the village information.
The final approver for the population data of the country will always be the national level ‘Population data approver’ where all the villages and its population will be added up to show the country level population.
Note: The design is showing ‘District’ level population approver screen but a population data approver can belong to any administrative hierarchy of the country.
This is the landing page for the ‘Population data approver’ user where he/she will see the population and related information of the villages that are part of the administrative boundaries assigned to him. The user can check out the detailed information and make changes in the population and related data and send the changes for approval. If no changes are required in the population data, the user can directly validate the village population.
Content of the landing page -
Dynamic boundary filters on top concerning parent and child administrative hierarchy - This is a dynamic filter that will be given to the user for filtering out specific boundaries. This will be a search-enabled dropdown for every filter content. The filters will be added or removed depending on the parent hierarchy assigned to the user. For example, if the user belongs to district hierarchy (Parent), then all child hierarchies and their boundaries will be part of the filter. The user can clear the selected filter by clicking on the ‘Clear Filter’ button.
Dynamic dashboard metrics - There will be dynamic metrics that will be shown to the user depending on the filters chosen. The important metrics that need to be shown on the dashboard are -
a. Uploaded target population - This metric will show the aggregated target population that is uploaded and it will change as per the filters chosen. This is for a bednet campaign.
b. Confirmed target population - This metric will show the aggregated confirmed target population and it will change as per the filters chosen. This is for a bednet campaign.
c. Uploaded target population (Age 3 - 11 months) - This metric will show the aggregated target population (Age 3 - 11 months) that is uploaded and it will change as per the filters chosen. This is for a SMC campaign.
d. Confirmed target population (Age 3 - 11 months) - This metric will show the aggregated confirmed target population (Age 3 - 11 months) and it will change as per the filters chosen. This is for a SMC campaign.
e. Uploaded target population (Age 12 - 59 months) - This metric will show the aggregated target population (Age 12 - 59 months) that is uploaded and it will change as per the filters chosen. This is for a SMC campaign.
f. Confirmed target population (Age 12 - 59 months) - This metric will show the aggregated confirmed target population (Age 12 - 59 months) and it will change as per the filters chosen. This is for a SMC campaign.
g. Uploaded total population - This metric will show the aggregated total population that is uploaded and it will change as per the filters chosen.
h. Confirmed total population - This metric will show the aggregated confirmed total population and it will change as per the filters chosen.
Filters on the action items on the user - This filter will help the user to filter out the villages that need some action. Below are the filters that will be shown to the user:
a. Villages with pending validation - This filter will show the list of villages that are pending to be validated by the user. The user will be able to see the list of villages whose actions are pending on the user as well as on the users that belong to the child boundaries of the parent district level data approver. This filter will be further segregated as -
i. Pending on me - This will show the list of the villages that needs to be validated by the assigned user of the ‘district’. This will also show a metric - the number of villages that are pending to be validated by the user out of the total number of villages belonging to the user’s assigned boundaries, for example, 5/30 villages to be validated. This should be by default chosen when the user lands on the page.
ii. Pending on subordinates - This will show the list of the villages that need to be validated by the users that belong to the child boundaries of the parent ‘district’. This will also show a metric - the number of villages that are pending to be validated by the subordinates out of the total number of villages belonging to the user’s assigned boundaries, for example, 15/30 villages to be validated.
Note: A data approver belonging to a ‘district’ can validate the village population data of the villages that belong to the child boundaries of the ‘district’, even though those villages may have their own data approver assigned.
b. Validated villages - This filter will show the list of villages that are part of the user’s assigned boundary and those have been validated either by the user himself or his subordinates at the lower administrative hierarchy level. This will also show a metric - the number of villages that are validated out of the total number of villages belonging to the user’s assigned boundaries, for example, 25/30 villages are validated.
c. Villages with pending approval - This filter will show the list of villages whose population data (total population or target population) have been changed by the user’s subordinates at the lower administrative hierarchies. This will also show a metric - the number of villages that are pending for approval by the user, for example, 5 villages data to be approved. The assigned user who can see the pending approval villages here can perform 2 activities -
i. Check and approve the recommended village population data
ii. Send back the village data for correction to the user who sent the village data for approval
Data content of the landing page -
Here the user will be able to see the basic information related to the villages that are part of his administrative hierarchy. The data that will be available are -
a. Village - The list of the villages that are part of the user’s administrative hierarchy. There will be a checkbox beside every village listed.
b. Uploaded total population - This will show the total population of the village whose data has been uploaded by the central team or microplan system administrator.
c. Confirmed total population - This will show the total population of the village whose data has been uploaded by the central team or microplan system administrator. This can later be edited.
d. Uploaded target population - This will show the target population of the village whose data has been uploaded by the central team or microplan system administrator. This is specifically for bednet campaigns.
e. Confirmed target population - This will show the target population of the village whose data has been uploaded by the central team or microplan system administrator. This is specifically for bednet campaigns. This can later be edited.
f. Uploaded target population (Age 3-11 months) - This will show the target population between age 3-11 months of the village whose data has been uploaded by the central team or microplan system administrator. This is specifically for SMC campaigns.
g. Confirmed target population (Age 3-11 months) - This will show the target population between age 3-11 months of the village whose data has been uploaded by the central team or microplan system administrator. This is specifically for SMC campaigns. This can later be edited.
h. Uploaded target population (Age 12-59 months) - This will show the target population between age 12-59 months of the village whose data has been uploaded by the central team or microplan system administrator. This is specifically for SMC campaigns.
i. Confirmed target population (Age 12-59 months) - This will show the target population between age 12-59 months of the village whose data has been uploaded by the central team or microplan system administrator. This is specifically for SMC campaigns. This can later be edited.
j. Comment logs - This will show the status flow of a village and comments made while validating or making corrections to the village data. This comment logs will capture the comment made by the users in a timeline manner. For any action that the user takes such as ‘Validate’, ‘Send for data correction’, ‘Send for approval’ and ‘Approve’ the user has to enter a comment.
k. Edit confirmed population - This is an action that the user can take to update the population data of the village, if the user feels that the uploaded data is incorrect or has discrepancies. Upon editing, the village data will be submitted for approval by the user belonging to the next higher hierarchy. This will update the ‘Confirmed total population’ and ‘Confirmed target population’ of the village for the data approver.
Note: Edit population data option will not be provided to the users if they filter the villages by ‘Villages with pending approval’ and ‘Validated villages’ filter.
Action on the villages - There will be certain actions that the user can take on the villages depending on the filter chosen. The actions are -
a. Validate data - This action will be available for the filters chosen ‘Villages with pending validation’. More details will be provided below.
b. Send for correction - This action will be available for the filters chosen ‘Villages with pending approval’ and ‘Validated villages’. More details will be provided below.
c. Approve data - This action will be available for the filters chosen ‘Villages with pending approval’. More details will be provided below.
This functionality will give access to the assigned user to edit the village population data and submit it for approval to the supervisors belonging to the next higher hierarchy.
Note: The edit population data option will not be provided to the users if they filter the villages by ‘Villages with pending approval’ and ‘Validated villages’ filter.
Content of the screen -
Village name - This shows the name of the village that the user wants to edit the population data for.
Uploaded total village population - This shows the total village population uploaded by the system admin for the village.
Uploaded target village population - This shows the target village population uploaded by the system admin for the village. This is specifically for bednet campaigns.
Uploaded target village population (Age 3 - 11 months) - This shows the target village population (Age 3 - 11 months) uploaded by the system admin for the village. This is specifically for SMC campaigns.
Uploaded target village population (Age 12 - 59 months) - This shows the target village population (Age 12 - 59 months) uploaded by the system admin for the village. This is specifically for SMC campaigns.
Confirm total population of the village - This will have auto filled total population data captured by the data collector or population upload file, in case the village doesn’t have any data collector. The data approver can validate and edit the total population and it will be reflected in the ‘Collected total village population’ data column of the dashboard.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Confirm target population of the village - This will have auto filled target population data captured in the population upload file. This is specifically for bednet campaigns.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Confirm target population of the village (Age 3 - 11 months) - This will have auto filled target population (Age 3 - 11 months) data captured in population upload file. This is specifically for SMC campaigns.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Confirm target population of the village (Age 12 - 59 months) - This will have auto-filled target population (Age 12 - 59 months) data captured in the population upload file. This is specifically for SMC campaigns.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Actions buttons - The user will be able to perform either of the below actions here:
a. Send for approval - Once the user updates the population data, the user can send the changed data of the village for approval to the next higher administrative hierarchy data approver. To send corrected data for approval, the user must enter a comment sharing the reason for the change.
Validation: The max length of a comment is 140 characters.
b. Cancel - The user can cancel the update and return to the landing page.
The user can see the comment logs by clicking on the comment logs link. The user will be able to see the detailed action taken on a village along with the timestamp and comment details. This will help the supervisors to understand what actions have been taken in a village and who took the action. This will help in keeping traceability of the changes happening to a village.
The content of the comment logs are -
Status of the action - The user will be able to see the status of the actions taken by the other users. For every action, the status will be captured w.r.t the village and updated in the comment logs. There will be 4 status on a high level:
a. Data submitted - Once the village population data has been uploaded by the central/system admin, the status will be changed to ‘Data submitted’.
b. Sent for approval - Once the village population data has been changed by a user and forwarded for approval, the status will be changed to ‘Sent for approval’.
c. Approved - Once the user approves the recommended changes in the village population, it moves to ‘Approved’ status.
d. Validated - Once the village population data has been validated by the user or by the highest jurisdiction level data approver, the status will be changed to ‘Validated’ and the village will be moved to ‘Validated villages’ bucket.
e. Sent for correction - Once the village population data has been checked by the supervisor and supervisors decide to send the village data for correction, the status will be changed to ‘Sent for correction’.
User’s name and role - Whenever a user takes an action on the village and puts a comment, for every action, the user’s name and role will be captured and shown in the comment logs.
Timestamp - Whenever a user takes an action on the village and puts a comment, for every action, the timestamp of the action will be captured. It should be in the international timestamp format “YYYY-MM-DD HH:MM”.
Comment - Whenever a user takes an action on the village and puts a comment, it will be captured alongside the other details.
Workflow image for data validation and data approval -
Workflow for pending data validation - Upon landing, the user will be able to see the list of villages that are part of the administrative hierarchy assigned to the user and his subordinates. There will be a filter called ‘Villages with pending validation’, in this filter, the user will be able to see all the villages that need the user or his subordinates to take action. On this page, the user can take 2 important actions upon checking the village population data -
a. Validate the village data -
If the user chooses one or more villages and validates their data using the ‘Validate’ button, then the villages will be moved from the bucket of ‘Villages with pending validation’ to ‘Validated villages’. These validated villages will be seen by the user, his subordinates at the child administrative boundaries, and his/her superiors at the parent administrative boundaries. For example, if a district supervisor validates the village data, then it will be seen by the administrative post and locality-level data approvers that are part of the district, also, the validated villages will be seen by the province and country-level data approvers to which the district is linked. For validating a village, the user has to add a reason for validation as a comment. Below is the UI for the comment section to add the validation reason:
b. Send back for correction -
Once the validated villages start residing in the ‘Validated villages’ bucket, those villages will be shown to every user belonging to the parent and child administrative boundaries. The user at the higher administrative boundaries will have the access to send back the data for correction, in case the higher level supervisors aren’t satisfied with the validated village data. Once the data has been sent back for correction, the village will move from the ‘Validated villages’ bucket to the ‘Villages with pending validation’ bucket of the user who has validated it earlier. For sending back for correction, the user has to add a reason for sending back the data for correction as a comment. Below is the UI for comment section to add the validation reason:
Note: Send back for correction button will only be available to the users who validated the village data and to the users that reside in the higher administrative boundaries.
Workflow for pending data approval - Upon landing, the user will be able to see the list of villages that are part of the administrative hierarchy assigned to the user and his subordinates. There will be a filter called ‘Villages with pending validation’, in this filter, the user will be able to see all the villages that need the user or his subordinates to take action. On this page, the user can take 2 important actions upon checking the village population data -
a. Editing the village data - If the user feels that the uploaded data for a certain village is incorrect or out-dated, the user can recommend data changes for the village by clicking on the ‘Edit population data’ button.
Once the user edits the village population data, it will be sent to his next higher level supervisor for approval. The village will be moved from the ‘Villages with pending validation’ bucket to ‘Villages with pending approval’ bucket of the supervisor belonging to the next higher administrative hierarchy. For sending recommended village population data for approval, the user has to add a reason for sending recommended village population data for approval as a comment. Below is the UI for comment section to add the validation reason:
b. Approving the recommended changes in the village data -
The supervisors will be able to see the list of villages with pending approval in the ‘Villages with pending approval’ bucket. In this bucket, the supervisor can check and compare the village population data that is uploaded and then the recommended population data submitted by the subordinate for approval. Here, upon decision making, the supervisor data approver can take 2 actions:
i. Approve the recommended changes in the village data - If the supervisor data approver feels that the recommended changes in the village population is correct, then the data approver will approve the village population using the ‘Approve’ button (The user can choose multiple villages for approval at once). Upon approving the village population, the village will be moved from the assigned data approver’s ‘Villages with pending approval’ bucket to the next higher administrative hierarchy data approver’s ‘Villages with pending approval’ bucket. This workflow will go on until the national or highest administrative hierarchy level data approver validates the population data of the village. Once the changes reach the highest administrative hierarchy for approval, the village status will be ‘Validated’ and the village will reside in the ‘Validated villages’ bucket once approved by the highest administrative hierarchy. For every approval, the data approver needs to add a reason as a comment and that comment will be seen in the comment logs.
Note: The population data approver will be able to see and take actions on the pending approvals on him as well as the pending approvals on his subordinates.
ii. Sending data for correction - If the supervisor data approver at any higher administrative hierarchy feels that the recommended changes in the village population is incorrect, then the data approver will send the village population data for correction using the button ‘Send for correction’. Once the data is sent for correction, the village will be moved from the ‘Villages with pending approval’ bucket of the user to ‘Villages with pending validation’ bucket of the user who submitted the recommended village data changes. For every action of sending for correction, the data approver needs to add a reason as a comment and that comment will be seen in the comment logs.
Important validation: The village population data can’t be changed if the village resides in the ‘Villages with pending approval’ bucket.
View of detailed village data -
This is the redirected page that shows the detailed information of the village selected. When the user clicks on the village on the landing page, he will be redirected to a new page with the detailed information of the village.
Content of the detailed pop-up screen -
Boundary details - Depending on the boundary assigned, the user will be able see the boundary hierarchy and assigned boundaries, along with the child boundary hierarchy and their boundaries.
Uploaded target village population - This will show the system admin’s uploaded target population of the village. This is specifically for bednet campaigns.
Uploaded target village population (Age 3 - 11 months) - This will show the system admin’s uploaded target population (Age 3 - 11 months) of the village. This is specifically for SMC campaigns.
Uploaded target village population (Age 12 - 59 months) - This will show the system admin’s uploaded target population (Age 12 - 59 months) of the village. This is specifically for SMC campaigns.
Approve target population of the village - This will have auto filled target population data captured in the population upload file. In case the target population of the village is updated by the data approver, then the approved target population will be updated with the new updated target population. This is specifically for bednet campaigns.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Approve target population of the village (Age 3 - 11 months) - This will have auto filled target population (Age 3 - 11 months) data captured in population upload file. In case the target population of the village is updated by the data approver, then the approved target population will be updated with the new updated target population. This is specifically for SMC campaigns.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Approve target population of the village (Age 12 - 59 months) - This will have auto filled target population (Age 12 - 59 months) data captured in the population upload file. In case the target population of the village is updated by the data approver, then the approved target population will be updated with the new updated target population. This is specifically for SMC campaigns.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Uploaded total village population - This will show the uploaded total population of the village by the system admin.
Approve total population of the village - This will have auto filled total population data captured in the population upload file. In case the total population of the village is updated by the data approver, then the approved total population will be updated with the new updated total population.
Validation: The field should accept only numeric values and whole numbers. Error message when invalid entry happens “Population data must be a whole number”.
Assigned data approver - This will show the person who is assigned to approve the population data of the village.
Village accessibility level - This shows the accessibility level to a village. The village accessibility level can be edited by ‘Population data approver’, if required. This is an optional field.
There are 3 data parameters to access the accessibility level to the village -
a. Village road condition - The user will be asked to choose the road condition to the village using the data approver dashboard. There will be 4 options given to the user to choose from -
Concrete
Gravel
Dirt
No road
b. Village terrain - The user will be asked to choose the village terrain using the data approver dashboard. There will be 4 options given to the user to choose from -
Mountain
Forest
Plain
Desert
c. Transportation mode - The user will be asked to choose the transport mode available to reach the village using the data approver dashboard. The transportation mode will be fetched from the vehicle registration page. If the user doesn’t get the option to choose the transport mode, he can choose ‘Others’ as an option to add the transport mode to the vehicle. The new transport mode will be just temporarily created and it will not affect the vehicle registration module.
Village security level - The village security level will be edited by the ‘Population data approver’ user if required. This is an optional field.
There are 2 data parameters to access the security level of the village -
a. Is your village prone to civil unrest like violent protests, riots, etc.? - The user will be asked this question to answer using the data approver dashboard. There will be 4 options to choose from -
All the time (Atleast once a month)
Often (Atleast once a year)
Rarely (Once in 2-3 years)
Never
b. How often do the security forces patrol the village?
Everyday
Often (Atleast once a week)
Rarely (Once in a month)
Never
Comment logs - The data approver can check the comment logs in case a village is validated or sent for correction or sent for approval.
Use-case to cover: What if the country-level data approver changes/edits the village population data?
The country-level data approver can make population data changes for any village under his jurisdiction. Now, since the country-level data approver doesn’t have any superior role assigned above him, the changes will not go through any approval process. The country-level data approver can simply make the changes, add a reason for the changes, and save the changes. The status of the village will remain unchanged but all the changes should be logged in the comment and change logs.
Note - The final approver of the village population will be the national or highest administrative hierarchy data approver. The national level data approver will have a button called ‘Finalize Population Data’, and the button will only be enabled when the ‘Villages with pending validation’ is 0, ‘Villages with pending approval’ is 0, and ‘Validated villages’ is x/x, that is, if there are 500 villages in the campaign zone, then 500 villages should be in the validated status. Once the population data is finalised, there will be no action allowed on the dashboard. The user can just work with the filters to view the data but can’t make any changes. Once finalized, the estimation of bednets required per village and the total SPAQ required per village will be calculated.
The user will be able to see the message screen once the population data has been finalized by the national level Population data approver.
Facility catchment mapper flow -
Actor: Supervisor (Facility catchment mapper)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second last boundary)
This is the flow for mapping the campaign facilities/POS to their catchment boundaries (villages). Mapping the facilities/POS to their catchment boundaries (villages) is crucial as the microplan estimation for the boundary (villages) will be happening w.r.t the facility/POS mapped and its type.
Facility catchment mappers can act on different administrative hierarchies and depending on the hierarchy and boundaries assigned, the facility catchment mapper will be able to see their assigned villages and facilities/POS for mapping. For example, the mapper can belong to a country, province, district, administrative post, or locality, and concerning the boundaries assigned, he/she will be able to see the respective villages and facilities/POS within the boundaries assigned.
This screen is the landing page for the mapper. In this screen, the mapper will be able to view all the facilities/POS and their details that are part of his administrative boundaries.
Validation: For the mapper to work on mapping facility/POS to their catchment areas, the population data for the campaign must be approved by the national level Population data approver.
Content of the screen -
Card showing villages with mapped facilities/POS - This card will show the count of the villages that belong to the mapper’s administrative boundary. It also shows the total number of villages (belonging to the mapper’s admin boundary) that have a catchment facility mapped.
Card showing facilities with mapped villages - This card will show the count of the facilities that belong to the mapper’s administrative boundary. It also shows the total number of facilities (belonging to the mapper’s admin boundary) that have a catchment village mapped.
Facility search - This will give the user the ability to search the specific facility that needs to be mapped to the catchment boundaries. The search needs to accept partial string match as well.
Filters - This will let the users to filter out the specific facilities that he needs to do the facility-catchment area mapping for. The user can filter out the facilities that he wants to map the catchment villages to. Below are the multi-select dropdown filters that the user will get -
a. Facility type - This will have the data of facility type defined during the instance creation
b. Facility status - This will have the facility status defined, which is either permanent or temporary
c. Is fixed post? - This will be an optional field. If the campaign distribution strategy is either ‘fixed post’ or ‘house-to-house and fixed post’, then this filter will be available for the user to choose
d. Residing village - This will have the list of all the villages that the facilities in the dashboard are part of
Facility name - This field shows the name of the facility that belongs to the user’s defined boundary.
Facility type - This field contains the type of the facilities that are listed in the dashboard.
Facility status - This field contains the status (Permanent/Temporary) of the facilities that are listed in the dashboard.
Capacity - This field contains the capacity of the facilities that are listed in the dashboard. The capacity can be either ‘Bales’ for bed nets or ‘Blisters’ for SMC campaigns. This will also show the out of total capacity, how much is consumed - Aggregated bales or blisters required for the villages assigned to the facility.
Assigned villages - This field will show the total number of villages that are assigned to the specific facility.
Serving population - This field will show the total population that is being served by the facility out of the total capacity of serving population of the facility. The total population that is served by the facility is the sum of the approver target population of the villages assigned. So, in case of a bednet campaign, the total serving population will be the sum of the target population of all the villages assigned to the facility, and, in case of a SMC campaign, the total serving population will be sum of the target population belonging to age group of 3 to 11 months and age group of 12 to 59 months.
Fixed post - This field tells which facilities listed in the dashboard are fixed post facilities.
Residing village - This field contains the village name where the facility resides. The user can also view the complete boundary information of the village as a tool-tip by clicking on the ‘i’ icon.
Action - Using this the user can map the facilities to their catchment areas for microplanning.
This screen shows the list of villages that are not mapped to any catchment facility.
Using this screen, the mapper will be able to map the chosen facility to their respective serviceable villages in the list. The mapper will be able to see all the villages that are part of his administrative boundaries and the villages that are not mapped to any facility.
Content of the screen -
Content of the screen -
Card showing villages with mapped facilities/POS - This card will show the count of the villages that belong to the mapper’s administrative boundary. It also shows the total number of villages (belonging to the mapper’s admin boundary) that have a catchment facility mapped.
Card showing facilities with mapped villages - This card will show the count of the facilities that belong to the mapper’s administrative boundary. It also shows the total number of facilities (belonging to the mapper’s admin boundary) that have a catchment village mapped.
Facility search - This will give the user the ability to search the specific facility that needs to be mapped to the catchment boundaries. The search needs to accept partial string match as well.
Filters - This will let the users to filter out the specific facilities that he needs to do the facility-catchment area mapping for. The user can filter out the facilities that he wants to map the catchment villages to. Below are the multi-select dropdown filters that the user will get -
a. Facility type - This will have the data of facility type defined during the instance creation
b. Facility status - This will have the facility status defined, which is either permanent or temporary
c. Is fixed post? - This will be an optional field. If the campaign distribution strategy is either ‘fixed post’ or ‘house-to-house and fixed post’, then this filter will be available for the user to choose
d. Residing village - This will have the list of all the villages that the facilities in the dashboard are part of
Facility name - This field shows the name of the facility that belongs to the user’s defined boundary.
Facility type - This field contains the type of the facilities that are listed in the dashboard.
Facility status - This field contains the status (Permanent/Temporary) of the facilities that are listed in the dashboard.
Capacity - This field contains the capacity of the facilities that are listed in the dashboard. The capacity can be either ‘Bales’ for bed nets or ‘Blisters’ for SMC campaigns.
Assigned villages - This field will show the total number of villages that are assigned to the specific facility.
Serving population - This field will show the total population that is being served by the facility out of the total capacity of serving population of the facility. The total population that is served by the facility is the sum of the approver target population of the villages assigned. So, in case of a bednet campaign, the total serving population will be the sum of the target population of all the villages assigned to the facility, and, in case of a SMC campaign, the total serving population will be sum of the target population belonging to age group of 3 to 11 months and age group of 12 to 59 months.
Fixed post - This field tells which facilities listed in the dashboard are fixed post facilities.
Residing village - This field contains the village name where the facility resides. The user can also view the complete boundary information of the village as a tool tip by clicking on the ‘i’ icon.
Action - Using this the user can map the facilities to their catchment areas for microplanning.
This screen is the landing page for the mapper. In this screen, the mapper will be able to view all the facilities/POS and their details that are part of his administrative boundaries. Important validation: For the mapper to work on mapping facility/POS to their catchment areas, the population data for the campaign must be approved by the national-level population data approver.
Content of the screen -
Card showing villages with mapped facilities/POS - This card will show the count of the villages that belong to the mapper’s administrative boundary. It also shows the total number of villages (belonging to the mapper’s admin boundary) that have a catchment facility mapped.
Card showing facilities with mapped villages - This card will show the count of the facilities that belong to the mapper’s administrative boundary. It also shows the total number of facilities (belonging to the mapper’s admin boundary) that have a catchment village mapped.
Facility search - This will give the user the ability to search the specific facility that needs to be mapped to the catchment boundaries. The search needs to accept partial string match as well.
Filters - This will let the users to filter out the specific facilities that he needs to do the facility-catchment area mapping for. The user can filter out the facilities that he wants to map the catchment villages to. Below are the multi-select dropdown filters that the user will get -
a. Facility type - This will have the data of facility type defined during the instance creation
b. Facility status - This will have the facility status defined, which is either permanent or temporary
c. Is fixed post? - This will be an optional field. If the campaign distribution strategy is either ‘fixed post’ or ‘house-to-house and fixed post’, then this filter will be available for the user to choose
d. Residing village - This will have the list of all the villages that the facilities in the dashboard are part of
Facility name - This field shows the name of the facility that belongs to the user’s defined boundary.
Facility type - This field contains the type of the facilities that are listed in the dashboard.
Facility status - This field contains the status (Permanent/Temporary) of the facilities that are listed in the dashboard.
Capacity - This field contains the capacity of the facilities that are listed in the dashboard. The capacity can be either ‘Bales’ for bed nets or ‘Blisters’ for SMC campaigns.
Assigned villages - This field will show the total number of villages that are assigned to the specific facility.
Serving population - This field will show the total population that is being served by the facility out of the total capacity of serving population of the facility. The total population that is served by the facility is the sum of the approver target population of the villages assigned. So, in case of a bednet campaign, the total serving population will be the sum of the target population of all the villages assigned to the facility, and, in case of a SMC campaign, the total serving population will be sum of the target population belonging to age group of 3 to 11 months and age group of 12 to 59 months.
Fixed post - This field tells which facilities listed in the dashboard are fixed post facilities.
Residing village - This field contains the village name where the facility resides. The user can also view the complete boundary information of the village as a tool-tip by clicking on the ‘i’ icon.
Action - Using this the user can map the facilities to their catchment areas for microplanning.
This screen shows the list of villages that are not mapped to any catchment facility.
Using this screen, the mapper will be able to map the chosen facility to their respective serviceable villages in the list. The mapper will be able to see all the villages that are part of his administrative boundaries and the villages that are not mapped to any facility.
Content of the screen -
Card with chosen facility details - This card will show the details of the facility that is chosen. This will help the mapper to understand which facility is chosen and which all villages can be mapped to it. Below are the details of the facility that will be shown -
a. Facility name
b. Facility type
c. Facility status
d. Facility capacity
e. Population being served out of the total serving population capacity of the facility
f. Is fixed post? (Optional)
g. Residing village
Boundary filter - This user will be able to filter out the boundary that is assigned to him, as well as the child boundaries. For example, if the mapper belongs to a district, then he will be able to see the filters for all the hierarchies and their boundaries at and below the assigned district. The mapper will be able to see the boundaries of the assigned district, their administrative post, their localities and their villages. All the filters will be search enabled multi-select dropdowns.
Boundary data - The user will be able to see the boundary data on his screen. Only those boundaries will be visible that are part of his assigned administrative hierarchy and lower hierarchies.
Village accessibility level button - Here the user will be able to see the village accessibility level if it was updated by the population data approver. If there is no data available for the village accessibility, then the accessibility data will be empty. Below are the details for village accessibility shown -
a. Village road condition
b. Village terrain
c. Village transport mode
Note: The data will be shown as a non-editable popup
Village security level button - Here the user will be able to see the village security level if it was updated by the population data approver. If there is no data available for the village security level, then the security level data will be empty. Below are the details for village security level shown -
a. Is your village prone to civil unrest like violent protests, riots, etc.?
b. How often do the security forces patrol the village?
Note: The data will be shown as a non-editable popup
Approved target population - Here the user will be able to see the approved target population of the village. This is for a bednet campaign.
Approved target population (Age 3 - 11 months) - Here the user will be able to see the approved target population (Age 3 - 11 months) of the village. This is for a SMC campaign.
Approved target population (Age 12 - 59 months) - Here the user will be able to see the approved target population (Age 12 - 59 months) of the village. This is for a SMC campaign.
Distance from the catchment facility (KMs) -
Here the mapper can edit and enter the distance of the facility to the catchment village. This field is optional.
Validation: The field can take only numeric values. Error message when the entered value is invalid “Please enter a numeric value”.
Assigned facility - For the ‘Unassigned villages dashboard’, none of the villages should be mapped to any catchment facility.
‘Assign to “facility name”’ button - The user will be able to see the list of the villages assigned to his administrative boundaries. The user can choose multiple villages at a time to assign them to the chosen facility. There should be a confirmation pop-up before the user approves the assignment of the facility to their catchment villages. Once confirmed, the villages will be tagged to the chosen facility for microplan.
Pop-up message - Are you sure you want to assign the selected villages to “facility name”? - There will be a Yes/No action button.
This screen will show all the villages that are assigned to the chosen facility.
Here, all the content of the dashboard will be the same as the ‘Unassigned village dashboard’, with only a difference -
In place of the ‘Assign’ button, there will be an ‘Remove from “Facility name”’ button and the mapper can choose multiple villages that he wants to unassign from the selected facility. There should be a confirmation pop-up before the user approves the unassignment of the facility to their catchment villages. Once confirmed, the villages will be untagged from the chosen facility and those villages will move to the ‘Unassigned villages dashboard’ of the chosen facility for remapping.
Pop up message - Are you sure you want to remove the selected villages from the mapped “facility name”? - There will be a Yes/No action button.
Note - The final approver of the facility assignment to the villages will be the national or highest administrative hierarchy ‘facility catchment assigner’. The national level ‘facility catchment assigner’ will have a button called ‘Finalize facility to village assignment’, and the button will only be enabled when all the villages under the campaign zone are mapped to their respective facilities/POS. Once the catchment mapping is finalized, there will be no other actions allowed on the dashboard. The user can just work with the filters to view the mapping but can’t make any changes. Once finalised, the microplan estimation should be triggered for the campaign villages.
This screen will be shown to the national level facility catchment mapper once all the campaign villages are assigned to their facilities and the assignment has been finalized by the national level facility catchment mapper.
Geospatial view -
Actor: Supervisor (Population data approver, Microplan viewer, Microplan approver, and Facility catchment mapper)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second lowest boundary)
This is the flow that the user will use to visualise the microplan estimation of each village (lowest boundary) and each facility/POS.
Important validation: For the geospatial estimation view to work, it’s important that the facility-catchment area mapping is finalized for the campaign by the national-level facility catchment mapper.
Content of the screen -
Boundary filter - The user will be able to filter out the boundaries at each hierarchy and visualise the geo-cords of specific villages or facilities/POS at the chosen boundaries.
Map - Here the map can be accessed using the openstreetmap. The integration is already built so that it can be reused.
Layers - The user can view the available layers of the map using the layers capability available. The default layer will be of satellite view.
Filters - The user will be able to see two filter option on map:
a. Village filter: This will be chosen by default. This will show all the geo-coordinates of the villages (lowest boundary) on the map.
b. Facility/POS filter: This filter, if chosen, will show all the geo-coordinates of the facilities/POS on the map.
Validation: The two options will be checkboxes and a user can choose either or the options or both. By default, the village filter will be enabled.
Tool-tip information - This will show the estimate of the resources and other details for each village and facility/POS that the user chooses:
a. Village tool-tip information: The user will be able to view certain important information for the village on click -
Village name: The user will be able to see the name of the village on top.
Target population: This will show the target population of the village that will receive the bednets. This is specifically for bednet campaigns.
Target population (Age 3 - 11 months): This will show the target population of the village within the age group of 3 - 11 months that will receive the SPAQ blisters. This is specifically for the SMC campaign.
Target population (Age 12 - 59 months): This will show the target population of the village within the age group of 12 - 59 months that will receive the SPAQ blisters. This is specifically for the SMC campaign.
Total bednets: This will show the total bednets that will be required in the village for the campaign. This is specifically for bednet campaigns.
Total bales: This will show the total bednets that will be required in the village for the campaign. One bale ideally has 50 bednets in total. This is specifically for bednet campaigns.
Total SPAQ blisters (Age 3 - 11 months): This will show the total SPAQ blisters that will be required for the population within the age 3 - 11 months in the village for the campaign. This is specifically for the SMC campaign.
Total SPAQ blisters (Age 12 - 59 months): This will show the total SPAQ blisters that will be required for the population within the age 12 - 59 months in the village for the campaign. This is specifically for the SMC campaign.
Serving facilities/POS: This will show the total number of facilities/POS that serves the chosen village.
b. Facility/POS tool-tip information: The user will be able to view certain important information for the facility/POS on click -
Facility/POS name: The user will be able to see the name of the facility/POS on top.
Facility type: The user will be able to see the type of facility on the tool-tip.
Facility status: The user will be able to see the status of the facility on the tool-tip.
Capacity (Bales or SPAQ blisters): The user will be able to view the capacity of the facility on the tool-tip. For bednet campaign, the capacity will be bales and for the SMC campaign, the capacity will be SPAQ blisters.
Is fixed post?: The user will be able to see if the facility/POS a fixed post or not. This will only be shown if the resource distribution strategy for the campaign is either fixed post or mixed (fixed post & H2H).
Residing village: The user will be able to see the village at which the facility/POS resides.
Catchment villages: This will be the count of the villages (lowest boundaries) that the facility serves.
Serving population: This will be the total number of target population that the facility will serve. This is basically the sum of the total serving population of the villages that the facility is mapped to.
Serving bednets: This will be the total number of bednets that will be distributed to the villages that are mapped to the chosen facility. This is specifically for the bednet campaign.
Serving SPAQ blisters: This will be the total number of SPAQ blisters that will be distributed to the villages that are mapped to the chosen facility. This is specifically for the SMC campaign.
16. Microplan approver flow -
Actor: Supervisor (Microplan approver)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second last boundary)
This is the flow for approving the microplan estimation for the boundaries that are part of the campaign. It’s an important step to make sure that the microplan estimation done by the system is correct and that the same microplan estimation can be used for campaign setup. So, the microplan estimation must be approved by the designated users at each administrative level.
Microplan approvers can act on different administrative hierarchies and depending on the hierarchy and boundaries assigned, the microplan estimation for those villages will be shown to the user for validation. For example, the Microplan approver can belong to a country, province, district, administrative post, or locality, and concerning the boundaries assigned, he will be able to see the microplan estimation for the assigned villages.
The final approver for the Microplan estimation of the country will always be the national level ‘Microplan approver’ where all the villages of the campaign zone along with their microplan estimation will be shown to the national level microplan approver.
Important validation: For the microplan approver workflow to work, it’s important that the facility-catchment area mapping is finalized for the campaign by the national-level facility catchment mapper.
This is the landing page for the ‘Microplan approver’ user where he will see the microplan estimation of the villages that are part of the administrative boundaries assigned to him. The user can check out the detailed estimation information and make changes in the microplan assumptions for the selected villages and send the changes for approval. If no changes are required in the microplan estimation, the user can directly validate the microplan estimation for the villages that are part of his assigned administrative boundaries.
Content of the landing page -
Filters on the action items on the user - This filter will help the user to filter out the villages that need some action. Below are the filters that will be shown to the user:
a. Villages with pending validation - This filter will show the list of villages whose microplan estimations are pending to be validated by the user. The user will be able to see the list of villages whose actions are pending on the user as well as on the users that belong to the child boundaries of the parent district level data approver. This filter will be further segregated as -
Pending on me - This will show the list of the villages whose microplan estimations need to be validated by the assigned user of the ‘district’. This will also show a metric - the number of villages whose microplan estimations are pending to be validated by the user. This should be by default chosen when the user lands on the page.
Pending on subordinates - This will show the list of the villages whose microplan estimations need to be validated by the users that belong to the child boundaries of the parent ‘district’. This will also show a metric - the number of villages whose microplan estimations are pending to be validated by the subordinates.
Note: A microplan approver belonging to a ‘district’ can validate the microplan estimations of the villages that belong to the child boundaries of the ‘district’, even though those villages may have their own microplan approvers assigned.
The user filtering out the villages with pending validation can perform 2 different activities -
Check and validate the microplan estimations for the villages
Change microplan assumptions for the villages and send the changes for approval to higher authorities
b. Validated villages - This filter will show the list of villages that are part of the user’s assigned boundary and whose microplan estimations have been validated either by the user himself or his subordinates at the lower administrative hierarchy level. This will also show a metric - the number of villages whose microplan estimations are validated.
The user filtering out the validated villages can perform 2 different activities -
Check and send the villages for correction if the microplan estimations are not proper
Change microplan assumptions for the villages and send the changes for approval to higher authorities
c. Villages with pending approval - This filter will show the list of villages whose microplan assumptions have been changed by the user’s subordinates at the lower administrative hierarchies. This will also show a metric - the number of villages that are pending for approval by the user.
The assigned user who can see the pending approval villages here can perform 2 activities -
Check and approve the recommended village population data
Send back the village data for correction to the user who sent the village data for approval
Dynamic boundary filters concerning parent and child administrative hierarchy - This is a dynamic filter that will be given to the user for filtering out specific boundaries. This will be a search-enabled dropdown for every filter content. The filters will be added or removed depending on the parent hierarchy assigned to the user. For example, if the user belongs to district hierarchy (Parent), then all child hierarchies and their boundaries will be part of the filter.
Additional filters - Apart from the above filters, there will be a couple of more filters that will be available to the users. The filters are -
a. Facility or point of service - This will show the list of facilities that are mapped to the villages that are part of the microplan approver’s jurisdiction.
b. Village road condition - This will show the list of road conditions that are configured and users will be able to filter out the villages with the chosen road condition.
c. Village terrain - This will show the list of terrain types that are configured and users will be able to filter out the villages with the chosen terrain types.
d. Village transport mode - This will show the list of transport modes that are configured during vehicle registration and users will be able to filter out the villages with the chosen transport mode.
e. Civil unrest occurrence - This will show the list of civil unrest occurrence frequencies configured and users will be able to filter out the villages with the chosen civil unrest occurrence frequency.
f. Security forces patrolling -This will show the list of security forces patrolling frequencies configured and users will be able to filter out the villages with the chosen security forces patrolling frequency.
Metrics to be shown - On top of the dashboard, the microplan approver will be able to see the overall metrics for the villages under his jurisdiction. The metrics are dynamic and it will change depending on the filter selected. There will be different metrics captured for different campaign types.
Metrics for Bednet campaign -
a. Target population
b. Total household
c. Bednets required
d. Bales required
Metrics for SMC campaign -
a. Target population (Age 3-11 months)
b. Target population (Age 12-59 months)
c. Total SPAQ-1 required (Age 3-11 months)
d. Total SPAQ-2 required (Age 12-59 months)
e. Total SPAQ-1 required with buffer (Age 3-11 months)
f. Total SPAQ-2 required with buffer (Age 12-59 month)
Data content for the microplan approver -
The user will be able to see all the villages that are part of the user’s jurisdiction and the microplan estimations of the villages concerning the configurations chosen by the system administrator while setting up the microplan. The fixed data points in this dashboard are -
Boundary data - The user will be able to see the boundary details of the jurisdiction that is assigned to him. For example, if the user belongs to a district, then he will be able to see the boundary data of the district, its admin posts, its localities, and finally villages along with their estimations.
Serving facility/POS - The facility is mapped to the village. This data can be fetched from the village facility catchment mapping.
Village road condition - This data can be fetched if the population data approver fills in the data for the villages assigned.
Village terrain - This data can be fetched if the population data approver fills the data for the villages assigned.
Civil unrest occurrence - This data can be fetched if the population data approver fills the data for the villages assigned.
Security forces patrolling - This data can be fetched if the population data approver fills the data for the villages assigned.
Assigned microplan approver - This will have the information of who is the assigned microplan approver for the village. This will be helpful for validating the villages that are assigned to the user’s child boundary’s microplan approver (subordinates).
Total population - This is the total population of the village that is approved by the country level population data approver.
Target population - This is the target population of the village that is approved by the country level population data approver. This is for a bednet campaign.
Target population (Age 3-11 months) - This is the target population (Age 3-11 months) of the village that is approved by the country level population data approver. This is for a SMC campaign.
Target population (Age 12-59 months) - This is the target population (Age 12-59 months) of the village that is approved by the country level population data approver. This is for a SMC campaign.
View comment logs - The user will be able to see the comment logs for every action taken on the village using the comment logs button that will be available corresponding to each village.
View change logs - The user will be able to see the changes done in the microplan estimations of the villages once the microplan assumptions are updated.
Rest of the data points will be flexible and depending on the configuration chosen by the system admin, those estimation data points will be shown in this dashboard.
Action on the villages - There will be certain actions that the user can take on the villages depending on the filter chosen. The actions are -
1. Validate - This action will be available for the filters chosen ‘Villages with pending validation’. More details will be provided below.
Send back for correction - This action will be available for the filters chosen ‘Villages with pending approval’ and ‘Validated villages’. More details will be provided below.
Approve - This action will be available for the filters chosen ‘Villages with pending approval’. More details will be provided below.
Customise assumptions - This action will be available for the filters chosen ‘Validated villages’ and ‘Villages with pending validation’. More details will be provided below.
Workflow diagram for microplan approver -
Workflow for validating village microplan estimation -
This workflow will let the user validate the microplan estimations for the villages that are under the user’s jurisdiction. This workflow will be a part of the ‘Villages with pending validation’ bucket where the user can multiple villages at once and then validate the villages in bulk if the village microplan estimations seem correct to the user. Once the selected villages are validated, the validated villages will move from the ‘Villages with pending validation’ bucket of the user to the ‘Validated villages’ bucket of the user. Other users who have access to the same jurisdiction will be able to see the validated villages in the ‘Validated villages’ bucket. It’s important that the user adds a comment/reason for validating the microplan estimation of the assigned villages. Any higher authority user will be able to check out the comment logs from the dashboard. Attaching the comment box UI below:
Workflow for customisation of microplan assumptions -
When the villages are available in the ‘Villages with pending validation’ and ‘Validated villages’ buckets, the microplan approver will be able to choose one or more villages to customize their microplan assumptions as per requirement. The microplan approver will be able to see the list of all villages that are under the microplan approver’s jurisdiction.
Once the user clicks on the ‘Customise assumptions’ button, the microplan approver will be redirected to a screen where the user can play around with the microplan assumptions unless the desired microplan estimation for the chosen villages is achieved.
When the microplan approver chooses the village to customize their microplan assumptions, the user will be able to see the standard or already configured assumption value. The user can change and update the microplan assumption value and see the outcome of the changes in the microplan estimation dashboard by clicking on the ‘Apply’ button.
Once the microplan estimations are updated and finalized, the microplan approver can click on the ‘Confirm customisation’ button to go ahead with the estimation changes for the selected villages.
Upon clicking the ‘Confirm customisation’, the user will be shown a pop-up showing which all assumptions are being changed and what was their old value and what is their updated value. The old value will be the standard assumption value if the user is changing the microplan assumption for the village for the first time, if the user is changing the microplan assumption for a village for second/third/so on times, then the old value of the microplan assumption will be last saved value of the microplan assumption. For example, for a village, one of the assumptions was changed from 10 to 20 and then saved by a user. Then, for the same village, the same assumption is changed from 20 to 40, so upon confirmation, the user should be able to see the old value as 20 and the new value as 40.
For sending the changes for approval, the microplan approver needs to add a comment/reason. Below is the UI for adding comments before sending the changes for approval:
Workflow for approving the village microplan estimation -
If the supervisor microplan approver feels that the recommended changes in the village estimations are correct, then the microplan approver will approve the village’s microplan estimation using the ‘Approve’ button (The user can choose multiple villages for approval at once). Upon approving the updated microplan estimation for the villages, the villages will be moved from the assigned microplan approver’s ‘Villages with pending approval’ bucket to the next higher administrative hierarchy microplan approver’s ‘Villages with pending approval’ bucket. This workflow will go on until the national or highest administrative hierarchy level microplan approver approves the microplan estimation changes for the villages. Once the changes reach the highest administrative hierarchy for approval and the national level microplan approver approves the updated microplan estimation changes, the village status will be ‘Validated’ and the village will reside in the ‘Validated villages’ bucket. For every approval, the microplan approver needs to add a reason as a comment and that comment will be seen in the comment logs.
Note: The microplan approver will be able to see and take actions on the pending approvals on him as well as the pending approvals on his subordinates.
Comment box UI:
Workflow for sending back the village microplan estimation for correction -
This workflow will be available in the ‘Villages with pending approval’ and ‘Validated villages’ bucket of the dashboard.
When the villages are available in the ‘Validated villages’ bucket and the microplan approver feels that the microplan estimation for some of the villages are incorrect or needs correction, the microplan approver can choose those villages and send them back for correction using the ‘Send back for correction’ button. The villages that are sent back for correction by the microplan approver will move from the ‘Validated villages’ bucket to the ‘Villages with pending validation’ bucket of the user, who first validated the microplan estimation of the villages.
When the villages are available in the ‘Villages with pending approval’ bucket and the microplan approver feels that the changed/updated microplan estimation for some of the villages need correction, then the microplan approver chooses those villages and sends them back for correction using the ‘Send back for correction’ button. The villages that are sent back for correction by the microplan approver will move from the ‘Villages with pending approval’ bucket to the ‘Villages with pending validation’ bucket of the user, who first made changes in the microplan assumptions and submitted the data for approval to the higher jurisdiction microplan approver.
It is important that every time the user sends back the data for correction, he needs to add a comment/reason for his action. Attaching the comment box UI below:
View comment logs for villages -
The user can see the comment logs by clicking on the comment logs link. The user will be able to see the detailed action taken on a village along with the timestamp and comment details. This will help the supervisors to understand what actions have been taken in a village and who took the action. This will help in keeping traceability of the changes happening to a village. The button to check the comment logs will be available corresponding to each village in the dashboard.
The content of the comment logs are -
Status of the action - The user will be able to see the status of the actions taken by the other users. For every action, the status will be captured w.r.t the village and updated in the comment logs. There will be 4 status on a high level:
a. Sent for approval - Once the microplan assumptions have been changed for one or more villages by a user and forwarded for approval, the status will be changed to ‘Sent for approval’.
b. Approved - Once the user approves the recommended microplan assumption changes for the villages, it moves to ‘Approved’ status.
c. Validated - Once the microplan estimations for the villages have been validated by the user or by the highest jurisdiction level microplan approver, the status will be changed to ‘Validated’ and the village will be moved to ‘Validated villages’ bucket.
d. Sent for correction - Once the microplan estimations for the villages have been checked by the supervisor and supervisors decide to send the village data for correction, the status will be changed to ‘Sent for correction’.
User’s name and role - Whenever a user takes an action on the village and puts a comment, for every action, the user’s name and role will be captured and shown in the comment logs.
Timestamp - Whenever a user takes an action on the village and puts a comment, for every action, the timestamp of the action will be captured. It should be in the international timestamp format “YYYY-MM-DD HH:MM”.
Comment - Whenever a user takes an action on the village and puts a comment, it will be captured alongside the other details.
View microplan estimation change logs for villages -
If a village goes through multiple changes in the assumptions, and as a result of which the microplan estimations for the village changes multiple times, all these changes in the microplan estimations need to be captured in the change logs for the village. The button to check the change logs will be available corresponding to each village in the dashboard. Below are the information that will be shown on the change logs pop-up -
Which microplan estimation data points changed? The user should be able to see the microplan estimation data points that have been changed after updating the microplan assumptions.
Who updated the microplan assumptions? The user should be able to see who has updated the microplan assumptions as a result of which the microplan estimations got changed for the village.
Timestamp of the changes -The user should be able to see at what time the microplan assumptions were changed. It should be in the international timestamp format “YYYY-MM-DD HH:MM”.
What’s the change in the microplan estimations? The user should be able to see what was the earlier value of the microplan estimation data point vs the updated value of the microplan estimation data point.
Note on microplan estimation for the villages -
It’s crucial that for doing the human resource microplan estimation, every village needs to have the assigned facility mapped. Depending on the type of facility (fixed post or non-fixed post), the system will calculate the human resource estimations accordingly. But, it shouldn’t affect the medical resource estimation for the village, such as, number of bednets or SPAQ required for the village shouldn’t be dependent on the facility mapped to the village.
Use-case to cover: What if the country-level microplan approver customizes the microplan assumptions?
The country-level microplan approver can change microplan assumption for any village under his jurisdiction. Now, since the country-level microplan approver doesn’t have any superior role assigned above him, the changes will not go through any approval process. The country-level microplan approver can simply make the changes, add a reason for the changes, and save the changes. The status of the village will remain unchanged but all the changes should be logged in the comment and change logs.
Note - The final approver of the microplan estimation for the campaign villages will be the national or highest administrative hierarchy ‘Microplan approver’. The national level ‘Microplan approver’ will have a button called ‘Finalize microplan’ (Irrespective of any filters), and the button will only be enabled when the ‘Villages with pending validation’ is 0, ‘Villages with pending approval’ is 0 and ‘Validated villages’ is x/x, that is, if there are 500 villages in the campaign zone, then 500 villages should be in the validated status. Once the microplan estimation data is finalized, there will be no action allowed on the dashboard. The user can just work with the filters to view the data but can’t make any changes. Once the microplan estimates are finalised, the user can download the Excel for the microplan estimates from the home page.
This is the final screen that the country-level microplan approver will be able to see once the microplan is finalised. The user can either download the microplan estimation as an Excel or go to the admin console to set up the campaign for the microplan.
Microplan viewer flow -
Actor: Supervisor (Microplan viewer)
Administrative boundary: Country (Highest boundary), Province, Districts, Admin post, Locality (Second last boundary)
This is the flow for viewing the microplan estimation for the boundaries that are part of the campaign. It’s an important step to make sure that the microplan estimation done by the system is correct and that the same microplan estimation can be used for campaign setup. So, the microplan estimation must be viewed/reviewed by the designated users at each administrative level.
Microplan viewers can act on different administrative hierarchies and depending on the hierarchy and boundaries assigned, the microplan estimation for those villages will be shown to the user. For example, the Microplan viewer can belong to a country, province, district, administrative post, or locality, and concerning the boundaries assigned, he/she can see the microplan estimation for the assigned villages.
Validation: For the microplan viewer workflow to work, it’s important that the facility-catchment area mapping is finalized for the campaign by the national-level facility catchment mapper.
This is the landing page for the ‘Microplan viewer’ user where he will see the microplan estimation of the villages that are part of the administrative boundaries assigned to him. Here, the user will only be able to see the villages that have been validated by the assigned microplan approver.
Content of the landing page -
Dynamic boundary filters with respect to parent and child administrative hierarchy - This is a dynamic filter that will be given to the user for filtering out specific boundaries. This will be a search-enabled dropdown for every filter content. The filters will be added or removed depending on the parent hierarchy assigned to the user. For example, if the user belongs to district hierarchy (Parent), then all child hierarchies and their boundaries will be part of the filter.
Additional filters - Apart from the above filters, there will be a couple of more filters that will be available to the users. The filters are -
- Facility or point of service - This will show the list of facilities that are mapped to the villages that are part of the microplan approver’s jurisdiction.
- Village road condition - This will show the list of road conditions that are configured and users will be able to filter out the villages with the chosen road condition.
- Village terrain - This will show the list of terrain types that are configured and users will be able to filter out the villages with the chosen terrain types.
- Village transport mode - This will show the list of transport modes that are configured during vehicle registration and users will be able to filter out the villages with the chosen transport mode.
- Civil unrest occurrence - This will show the list of civil unrest occurrence frequencies configured and users will be able to filter out the villages with the chosen civil unrest occurrence frequency.
- Security forces patrolling -This will show the list of security forces patrolling frequencies configured and users will be able to filter out the villages with the chosen security forces patrolling frequency.
Metrics to be shown - On top of the dashboard, the micro plan viewer will be able to see the overall metrics for the villages under his jurisdiction. The metrics are dynamic, and they will change depending on the filter selected. Different metrics will be captured for different campaign types.
Metrics for Bednet campaign -
- Target population
- Total household
- Bednets required
- Bales required
Metrics for SMC campaign -
- Target population (Age 3-11 months)
- Target population (Age 12-59 months)
- Total SPAQ-1 required (Age 3-11 months)
- Total SPAQ-2 required (Age 12-59 months)
- Total SPAQ-1 required with buffer (Age 3-11 months)
- Total SPAQ-2 required with buffer (Age 12-59 month)
Data content for the microplan viewer -
The user will be able to see all the villages that are part of the user’s jurisdiction and the microplan estimations of the villages concerning the configurations chosen by the system administrator while setting up the microplan. The fixed data points in this dashboard are -
Boundary data - The user will be able to see the boundary details of the jurisdiction that is assigned to him. For example, if the user belongs to a district, then he will be able to see the boundary data of the district, its admin posts, its localities and finally villages along with their estimations.
Serving facility/POS - The facility is mapped to the village. This data can be fetched from the village facility catchment mapping.
Village road condition - This data can be fetched if the population data approver fills the data for the villages assigned.
Village terrain - This data can be fetched if the population data approver fills the data for the villages assigned.
Civil unrest occurrence - This data can be fetched if the population data approver fills the data for the villages assigned.
Security forces patrolling - This data can be fetched if the population data approver fills the data for the villages assigned.
Assigned microplan approver - This will have the information of who is the assigned microplan approver for the village. This will be helpful for validating the villages that are assigned to the user’s child boundary’s microplan approver (subordinates).
Total population - This is the total population of the village that is approved by the country level population data approver.
Target population - This is the target population of the village that is approved by the country level population data approver. This is for a bednet campaign.
Target population (Age 3-11 months) - This is the target population (Age 3-11 months) of the village that is approved by the country level population data approver. This is for a SMC campaign.
Target population (Age 12-59 months) - This is the target population (Age 12-59 months) of the village that is approved by the country level population data approver. This is for a SMC campaign.
View comment logs - The user will be able to see the comment logs for every action taken on the village using the comment logs button that will be available corresponding to each village.
View change logs - The user will be able to see the changes done in the microplan estimations of the villages once the microplan assumptions are updated.
Rest of the data points will be flexible and depending on the configuration chosen by the system admin, those estimation data points will be shown in this dashboard.
It is critical for the program team to set up the campaign as per the microplan created. And in order to do that, the admin console, which sets up the campaign, needs to map the correct microplan for campaign creation. As part of the integration, the Microplanning platform will share the below details with the admin console for campaign setup:
Microplan name
Campaign details
Facility data
Administrative boundaries and their targets
Number of human resources required as per the campaign distribution strategy chosen
a. Number of fixed post registration members required and boundary
b. Number of fixes post distribution members required and boundary
c. Number of household registration members required and boundary
d. Number of household distribution members required and boundary
e. Number of fixed post registration supervisors required and boundary
f. Number of fixed post distribution supervisors required and boundary
g. Number of household registration supervisors required and boundary
h. Number of household distribution supervisors required and boundary
i. Number of household registration monitors required and boundary
j. Number of household distribution monitors required and boundary
The admin console needs to provide the program team with a screen to choose the microplan for which the campaign needs to be set up.
User adoption and engagement -
- User Registration: The number of microplan users registered on the platform.
- Session Time: The average amount of time users spend on the platform in minutes.
- Population coverage accuracy - The total population considered in the microplan vs the total population captured during the campaign execution.
- Resource utilization accuracy - The total number of resources (bednets, frontline workers, vehicles, etc.) estimated during the microplanning phase versus a total number of resources utilised during campaign execution.
- Operational efficiency - Time required to finalise a microplan from the created time.
- Microplan adoption - The number of microplans created w.r.t countries.
- Reusability of Microplans: The frequency with which previous microplans are reused or adapted for new campaigns.
System specs & validation for Microplan module v0.1 -
Find the system specification here
The Microplan Estimation Approver plays a critical role in ensuring the accuracy and approval of resource estimation for health campaigns. This user is responsible for reviewing the resource estimations generated by the system, validating assumptions, and approving or rejecting the final microplan estimations. The goal is to ensure that the estimated resources (e.g., vaccines, bednets, medical personnel) align with the actual needs of the campaign, based on the validated population and facility data.
Review and validate resource estimation formulas.
Approve or reject microplan resource estimations.
Adjust estimation parameters and assumptions if necessary.
Ensure that the approved resource estimation aligns with the campaign's needs.
This section details the steps in the microplan estimation approval process.
Step 1: Log in to the Platform
Actor: Microplan Estimation Approver
Objective: Access the microplan estimation dashboard.
Process: The microplan Estimation Approver logs into the platform using their credentials, granting access to the estimation review and approval module.
Outcome: The system displays a list of microplans that require review, with detailed estimations ready for approval.
Step 2: Review Resource Estimation
Actor: Microplan Estimation Approver
Objective: Review the resource estimations generated by the system for the current campaign.
Process:
The system presents the resource estimation calculations based on the uploaded population and facility data.
The estimations are divided into key resources such as:
Vaccines: Estimated based on population size and target population.
Bednets: Calculated for campaigns like malaria prevention.
Personnel: Estimated based on the required workforce for each facility and catchment area.
Outcome: The microplan estimation approver has a comprehensive overview of the resources estimated for the campaign, with breakdowns by resource type.
Step 3: Review and Validate Assumptions
Actor: Microplan Estimation Approver
Objective: Ensure that the assumptions used for resource estimations are accurate and reasonable.
Process:
The system displays key assumptions that drive the resource estimation formulas, such as:
Target Population: Number of people eligible for the intervention (e.g., children aged 3-11 months for SMC campaigns).
Resource Allocation: Number of resources (e.g., bednets, vaccines) per person or household.
Distribution Strategy: House-to-house, fixed post, or a combination of both.
The approver cross-checks these assumptions with known data and campaign requirements.
If any assumptions seem inaccurate or unreasonable, the Microplan Estimation Approver can modify assumptions for list of specific boundaries
Outcome: The assumptions used for resource estimation are validated, and any necessary corrections are made.
Step 4: Approve or Reject the Microplan Estimation
Actor: Microplan Estimation Approver
Objective: Make the final decision to approve or reject the resource estimation for the campaign.
Process:
After reviewing the resource estimation, the Microplan Estimation Approver selects Approve or Reject.
Approve: Confirms that the estimation is valid and the required resources are accurately calculated. Once approved, the estimation becomes final and is locked for campaign execution.
Reject: If the estimation is inaccurate, the approver provides feedback and requests a re-evaluation of the data or assumptions.
The system prompts the approver to provide reasons for rejection, which are communicated to the appropriate team for corrections.
Outcome: Once approved, the resource estimation is finalized, and the required resources are allocated for the campaign. If rejected, the estimation returns to the appropriate team for review and modification.
Role
User mapped?
Administrative hierarchy
Administrative areas assigned?
Warning message
Action on warning
Microplan estimation approver
No
-
-
There is no ‘Microplan estimation approver’ assigned to the microplan. Are you sure to continue without assigning ‘Microplan estimation approver’?
Choice A (Highlighted button) - No, I don’t want to continue
Choice B - Yes, I want to continue
Microplan estimation approver
Yes
Province/district/Admin post/Locality
All province/district/Admin post/Locality
Microplan estimation approver
Yes
Province/district/Admin post/Locality
Some province/district/Admin post/Locality
‘Microplan estimation approver' role is assigned to only a few 'province/district/Admin post/Locality', would you like to proceed without assigning 'Microplan estimation approver' role to remaining 'province/district/Admin post/Locality'?
Choice A (Highlighted button) - No, I don’t want to proceed
Choice B - Yes, I want to proceed
Role
User mapped?
Administrative hierarchy
Administrative areas assigned
Warning message
Action on warning
Microplan estimation viewer
No
-
-
There is no ‘Microplan estimation viewer’ assigned to the microplan. Are you sure to continue without assigning ‘Microplan estimation viewer’?
Choice A (Highlighted button) - No, I don’t want to continue
Choice B - Yes, I want to continue
Microplan estimation viewer
Yes
Province/district/Admin post/Locality
All province/district/Admin post/Locality
Microplan estimation viewer
Yes
Province/district/Admin post/Locality
Some province/district/Admin post/Locality
‘Microplan estimation viewer' role is assigned to only a few 'province/district/Admin post/Locality', would you like to proceed without assigning 'Microplan estimation viewer' role to remaining 'province/district/Admin post/Locality'?
Choice A (Highlighted button) - No, I don’t want to proceed
Choice B - Yes, I want to proceed
Role
User mapped?
Administrative hierarchy
Administrative areas assigned
Warning message
Action on warning
Facility catchment assigner
No
-
-
There is no ‘Facility catchment assigner’ assigned to the microplan. Are you sure to continue without assigning ‘Facility catchment assigner’?
Choice A (Highlighted button) - No, I don’t want to continue
Choice B - Yes, I want to continue
Facility catchment assigner
Yes
Province/district/Admin post/Locality
All province/district/Admin post/Locality
Facility catchment assigner
Yes
Province/district/Admin post/Locality
Some province/district/Admin post/Locality
‘Facility catchment assigner' role is assigned to only a few 'province/district/Admin post/Locality', would you like to proceed without assigning 'Facility catchment assigner' role to remaining 'province/district/Admin post/Locality'?
Choice A (Highlighted button) - No, I don’t want to proceed
Choice B - Yes, I want to proceed
Role
User mapped?
Administrative hierarchy
Administrative areas assigned
Warning message
Action on warning
Population data approver
No
-
-
There is no ‘Population data approver’ assigned to the microplan. Are you sure to continue without assigning ‘Population data approver’?
Choice A (Highlighted button) - No, I don’t want to continue
Choice B - Yes, I want to continue
Population data approver
Yes
Province/district/Admin post/Locality
All province/district/Admin post/Locality
Population data approver
Yes
Province/district/Admin post/Locality
Some province/district/Admin post/Locality
‘Population data approver' role is assigned to only a few 'province/district/Admin post/Locality', would you like to proceed without assigning 'Population data approver' role to remaining 'province/district/Admin post/Locality'?
Choice A (Highlighted button) - No, I don’t want to proceed
Choice B - Yes, I want to proceed
Coming soon
Coming soon.
