Once the system administrator completes the microplanning setup, including defining campaign boundaries, configuring facilities, and assigning roles, the Supervisor Flow begins.

The Supervisor Flow for managing microplans enables supervisors to track, edit, validate, and finalise microplans associated with public health campaigns. Each microplan provides specific details about campaigns, statuses, and associated actions, ensuring effective campaign execution.

The table below outlines roles, their corresponding role codes, and descriptions of responsibilities for supervisors:

Overview

This page displays a tailored list of microplans that the logged-in supervisor is tagged to. Supervisors can manage these microplans within their jurisdiction, ensuring campaign activities are effectively tracked and validated.

Key Features:

• Microplans Access: Supervisors will see a list of microplans they are tagged to. This ensures that supervisors can only view and manage the microplans relevant to their role and responsibilities.

• filterUniqueByPlanConfig Parameter: The filterUniqueByPlanConfig parameter is used here to return all the microplans associated with the logged-in supervisor. This guarantees that only relevant data is displayed.

• Jurisdiction-Based Access: Supervisors have jurisdiction based on the hierarchy they belong to. For example, a district-level supervisor can access microplans for their district, while a province-level supervisor can access microplans specific to their province.

Sample Hierarchy

Interface Elements

Header Section

• Title: My Microplans represents the section for managing microplans.

• Tabs:

  1. All: Displays all microplans.

  2. Completed Setup: Lists microplans with finalized setup.

  3. Validation in Progress: Microplans undergoing validation.

  4. Microplan Finalised: Displays finalized microplans.

Search Functionality

• Search Bar: Allows filtering microplans by name.

• Clear Button: Resets the name search to display all microplans.

Microplan Table

The table lists the microplans in a tabular format. Each row represents a microplan, and the columns provide detailed information:

Actions for Each Microplan

Process Steps

Step 1: Access My Microplans

• Objective: View and manage microplans.

• Process: Navigate to the My Microplans section.

• Outcome: A list of all microplans is displayed, with tabs for status-based filtering.

Step 2: Search for a Microplan

• Objective: Locate a specific microplan.

• Process: Use the search bar to input the microplan name. Click Clear to reset the search.

• Outcome: Filtered results display matching microplans.

Step 3: Perform Actions

• Based on the status, perform the following actions:

  • Completed Setup: Click Start Validation to begin validating the microplan.

  • Validation in Progress: Click Edit to modify the microplan details.

  • Microplan Finalised: Click Download Estimations to save related data.

Endpoints

1. Overview

The Population Data Validation and Approval screen is designed for population data approvers to ensure the accuracy and consistency of population data submitted for villages. This screen allows approvers to validate, correct, and approve data, ensuring the integrity of the data used for resource planning.

2. User Roles

3.Interface Elements

Header Section

• Microplan Name: Displays the name of the current microplan being reviewed.

• Logged-in User: Indicates the user role and account.

Population Data Summary (KPIs)

• All values are dynamically updated based on the real-time census data.

• These values are sourced directly from microplan-specific KPIs, which reflect any actions taken by data approvers.

• As census data is reviewed, corrected, or approved, the values will change accordingly.

Filters and Search

• Administrative Hierarchy and Area Selection: Dropdown menus for selecting specific administrative areas (e.g., district and village).

• Search and Filter Options:

  • Workflow Status Filters:

    • Pending for validation

    • Pending for approval

    • Validated

  • Assigned to Filters:

    • Assigned to me

    • Assigned to all

  • Buttons: Apply Filter, Clear

Population Data Table

Action Buttons

• View Logs: Displays historical changes and logs related to a specific village's data

4. Workflow for Population Data Validation

4.1. Role-Based Permissions and Actions

Population Data Approver (PDA)

The Population Data Approver is responsible for validating population and editing data. Their responsibilities include:

Validating Data:

• Cross-check the uploaded data with the confirmed population to ensure accuracy.

Editing Data:

• Modify the village population data if discrepancies are found, with a reason logged for each change and the data is sent back for approval.

When No Data Is Assigned:

• If no data is assigned to the PDA, a "Back" button is shown, allowing them to return to the previous screen.

Root Population Data Approver (RPDA)

The Root Population Data Approver has all the functionalities of a PDA and additional capabilities, to finalize population data. Their responsibilities include:

Editing Data:

• Modify the village population data if discrepancies are found, with a reason logged for each change.

Approving or Sending Data for Correction:

• Once the population data is validated, the RPDA can either approve it or send it back for correction if further issues are identified.

Approval Workflow:

• If someone from the below hierarchy modifies and sends the data for approval, the RPDA can approve it. For example, if a province-level user sends the data back for approval, the RPDA will receive the application for approval and validation.

Finalizing Actions:

• If all the villages within the selected microplan have been validated and no further changes are required, the RPDA will see a "Finalize Actions" button at the footer of the page.

• The "Finalize Actions" button will lock the data and prevent further modifications once clicked, marking the end of the validation process for the selected microplan population data.

• After finalizing the population data a success screen will be shown, indicating that population data is finalized.

Additional Notes

• Once the population data reaches the national-level data approver and the validation is finalized, the system will disable all action buttons. The status will be set to "CENSUS_APPROVED" and no further changes can be made. At this point, users can only view the details of the data but will not be able to perform any additional actions, such as editing or approving the data.

• Population supervisors will only see the boundaries in their inbox that fall under their jurisdiction.

End Points

Overview

The document provides an interactive interface for supervisors to manage and track microplans. It displays role-based activity cards that guide users through tasks such as validating population data, assigning facilities, and approving microplan estimations. The available activities are dynamically presented based on the user’s role (Root or Normal) and the current workflow status of the microplan, ensuring that supervisors only see the actions relevant to their responsibilities at each stage of the microplan.

Interface Elements

Microplan Name Display:

A prominently displayed label at the top of the interface that shows the name of the selected microplan.

Activity Options:

Displays a list of activities as clickable items. Selecting an activity navigates the user to the corresponding detailed workflow.

Available Activities

1. Validate & Approve Population Data

• Purpose: Ensures the population data associated with the microplan is accurate and approved for further processing.

• Steps:

  1. Review uploaded population data for completeness and correctness.

  2. Approve or flag data for revision as needed.

• Roles Involved:

  • ROOT_POPULATION_DATA_APPROVER: Can review, approve, or send back population data, as well as finalised population data.

  • POPULATION_DATA_APPROVER: Can review, approve, or send back population data.

• Role-Based Access:

  • This card is visible based on the user role and the wfStatus that aligns with the data validation stage.

2. Assign Facilities to Villages

• Purpose: Assign healthcare or distribution facilities to specific villages or areas within the campaign's scope.

• Steps:

  1. Map villages to designated facilities.

  2. Confirm assignments to ensure logistical accuracy.

• Roles Involved:

  • ROOT_FACILITY_CATCHMENT_MAPPER: Assign and unassign facilities to villages, and finalise facility assignments.

  • FACILITY_CATCHMENT_MAPPER: Assign and unassign facility to villages.

• Role-Based Access:

  • This card appears only when the wfStatus indicates that facility assignment is the next step.

3. Validate & Approve Microplan Estimations

• Purpose: Review and finalise the estimated resources, population coverage, and other metrics calculated for the microplan.

• Steps:

  1. Check estimations for accuracy and alignment with campaign objectives.

  2. Approve or request adjustments as necessary.

• Roles Involved:

  • ROOT_PLAN_ESTIMATION_APPROVER: Can approve or request adjustments for microplan estimations, also finalized microplan estimation.

  • PLAN_ESTIMATION_APPROVER: Can approve or request adjustments for microplan estimations.

• Role-Based Access:

  • The card is displayed based on wfStatus of the plan configuration, indicating readiness for estimation validation.

User Actions Flow

1. Select an Activity: Choose one of the available activities depending on the current stage of the microplan.

2. Proceed to the Next Screen: Click the activity to access its detailed workflow interface.

Notes

• Role-based Permissions: Certain activities might be restricted based on user roles and permissions.

• Sequential Workflow: Activities must be completed in sequence for effective campaign execution:

  1. Validate Population Data

  2. Assign Facilities

  3. Approve Microplan Estimations

• Progress Tracking: Ensure tasks are not repeated and assignments remain aligned with campaign objectives.

API Endpoints

1.Overview

The Facility Catchment Assigner role is responsible for mapping campaign facilities/points of service (POS) to their respective catchment villages. This mapping ensures that estimation of resources for campaign can be done accurately based on the facilities/POS and the villages assigned to them.

2.User Roles

3.Key Responsibilities of the Facility Catchment Assigner

1. Assign Facilities to Villages:

   • Map facilities/POS to the villages within their assigned administrative boundaries.

2. Monitor Facility and Village Mappings:

   • Ensure that all villages and facilities are appropriately mapped for the campaign.

4.Interface Elements

Header Section

• Microplan Name:

  • Displays the name of the current microplan being worked on.

• Logged-in User:

  • Displays the role and account of the logged-in user (Facility Catchment Assigner).

Facility Assign Summary (KPIs)

The dashboard provides a summary of the facilities and villages that are part of the user's administrative boundaries.

Cards

1. Villages with Mapped Facilities/POS:

   • Displays the count of villages assigned to mapped facilities/POS within the administrative boundary.

2. Facilities with Mapped Villages:

   • Displays the count of facilities that have assigned villages in the administrative boundary.

Master Details For Search Filter Dropdowns

The following master details are part of the Facility Catchement Mapping:

• Facility Type: The type of facility (e.g., Warehouse, Health Post).

• Facility Status: Status of the facility (e.g., Permanent, Temporary).

• Residing Village: The villages where the facilities are located.

• MDMS Data is fetched from: https://github.com/egovernments/egov-mdms-data/tree/UNIFIED-QA/data/mz/health/hcm-microplanning

Search and Filter Options

1. Facility Search:

   • Allows the user to search for specific facilities based on partial string matches.

2. Filters:

   • Facility Type: Filters by the type of facility (e.g., Warehouse, Health Post).

   • Facility Status: Filters by the facility's status (e.g., Permanent, Temporary).

   • Is Fixed Post?: Filters by whether the facility is a fixed post or not.

   • Residing Village: Filters by the villages where the facilities are located.

Facility Details

The following details are available for each facility in the dashboard:

Assigning and Unassigning Villages to a Facility:

When the user clicks on a facility or assign button in facility row, a popup window opens displaying essential details about the selected facility, as well as options for managing unassigned and assigned villages for this facility.

5.Finalizing the Facility to Village Mapping

Once all villages are assigned to their respective facilities and the mappings are complete, the national level facility catchment assigner can finalize the assignment.

Finalization Process

1. Finalize Mapping:

   • A “Finalize facility to village assignment” button will be available to finalize the facility-to-village mapping.

   • After finalizing the facility catchment mapping a success screen will be shown, indicating that facility assignment is done.

   • Once finalized, no further changes can be made, and the microplan estimation for the campaign will be triggered.

2. Finalized Mapping View:

   • After finalization, the mapping cannot be modified, and the dashboard will display the finalized assignments for reference.

6.End Points

1.Overview

When the user clicks on a facility, this popup window opens displaying essential details about the selected facility, as well as options for managing unassigned and assigned villages for this facility.

2.Interface Elements

Facility Details Card

Upon selecting a facility, a Facility Details popup will display the following:

• Facility Name: Name of the selected facility.

• Facility Type: Type of facility, such as "Warehouse" or "Health Post."

• Facility Status: Indicates whether the facility is temporary or permanent.

• Capacity: Displays the capacity of the facility (e.g., the number of bales for bednet distribution or blisters for SMC campaigns).

• Serving Population: The serving population currently being served by the facility.

• Fixed Post: Indicates if the facility is a fixed post, which is typically a permanent, stationary facility.

• Residing Village: The village where the facility is located or based.

Filter Options:

• Select Administrative Hierarchy: Dropdown menu for selecting an administrative level (e.g., Country, Province, District).

• Select Administrative Area: Dropdown menu for selecting a specific area within the hierarchy (e.g., Locality, Village).

• Search: Search for villages by name or code.

• Clear: Clears all selected filters and resets the search options.

3.Unassigned Villages and Assigned Villages

3.1.Unassigned Villages

This section allows the user to manage villages that have not yet been assigned to any facility. Users can select villages from this list and assign them to a facility.

3.2.Assigned Villages

This section displays the villages that have already been assigned to a facility. Users can manage these assignments, including unassigning a village if necessary.

Actions:

• Assign: To assign a facility to a village, select the village from the unassigned list and click the "Assign" button.

• Unassign: If a village is already assigned to a facility, users can unassign it by selecting the village and clicking the "UnAssign" button.

4.Notes:

• Unassign: Clicking on unassign button will show a alert message that you want to unassign this village from the current selected facility.

• Close: Clicking "Close" will exit the page without making any changes.

5.EndPoints:

1. Overview

The Microplan Estimation Approver screen is designed for supervisors to validate and approve microplan estimations within their assigned administrative boundaries. This screen allows approvers to validate, correct, and approve data, ensuring the integrity of the data used for resource planning.

2. User Roles

3.Interface Elements

Header Section

• Microplan Name: Displays the name of the current microplan being reviewed.

• Logged-in User: Indicates the user role and account.

Plan Estimation Data Summary (KPIs)

• All values are dynamically updated based on the real-time plan data.

• These values are sourced directly from microplan-specific KPIs, which reflect any actions taken by data approvers.

• As plan estimation data is reviewed, corrected, or approved, the values will change accordingly.

Filters and Search

• Administrative Hierarchy and Area Selection: Dropdown menus for selecting specific administrative areas (e.g., district and village).

• Search and Filter Options:

  • Workflow Status Filters:

    • Pending for validation

    • Validated

  • Assigned to Filters:

    • Assigned to me

    • Assigned to all

  • Buttons: Apply Filter, Clear

Plan Estimation Data Table

The table on the Microplan Estimation Validation Page displays key data for each village involved in the campaign, including the village name, status logs, assignee details, and facility name. It also includes important information such as road conditions, terrain, and security factors, which help assess the village’s readiness for plan activities. Additionally, the table presents validated population data, the number of households(based on selected campaign), and other critical metrics related to the plan data, ensuring that approvers have a comprehensive view of the plan estimation details before approval.

Action Buttons

• View Logs: Displays historical changes and logs related to a specific plan estimation's data.

4. Workflow for Plan Estimation Data Validation

4.1. Role-Based Permissions and Actions

Plan Estimation Approver

The Estimation Data Approver is responsible for validating plan data. Their responsibilities include:

Validating Data:

• Cross-check the uploaded data with the confirmed population to ensure accuracy.

Identifying Discrepancies:

• If discrepancies are found, the PEA can flag the data for revision.

Approval Workflow:

• The PDA at the appropriate level will see the application as pending for approval. In such cases, the PDA can validate and approve the data.

When No Data Is Assigned:

• If no data is assigned to the PEA or all data assigned to him is validated, a "Back" button is shown, allowing them to return to the previous screen.

Root Plan Estimation Approver (RPEA)

The Root plan Estimation Approver has all the functionalities of a Plan Estimation Approver and additional capabilities, such as finalizing the microplan. Their responsibilities include:

Approving or Sending Data for Correction:

• Once the plan data is validated, the RPEA can either approve it or send it back for correction if further issues are identified.

Approval Workflow:

• If someone from the below hierarchy modifies and sends the data for approval, the RPEA can approve it. For example, if a province-level user sends the data back to a district-level user, who updates and sends it back for approval, the province-level RPEA will receive the application for approval.

Finalizing Actions:

• If all the villages within the selected microplan have been validated and no further changes are required, the RPDA will see a "Finalize Actions" button at the footer of the page.

• After finalizing the plan data a success screen will be shown, indicating that microplan is finalized.

• The "Finalize Actions" button will lock the data and prevent further modifications once clicked, marking the end of the validation process for the selected microplan or district.

5.Additional Notes

• Once the plan estimation data reaches the national-level data approver and the validation is finalized, the system will disable all action buttons. The status will be set to "ESTIMATION_APPROVED" and no further changes can be made. At this point, you can download microplan estimation.

• Estimation supervisors will only see the boundaries in their inbox that fall under their jurisdiction.

6.End Points:

1.Overview

When a user clicks on a village name in the Population Data Table, they are directed to the Village Details Page, which provides detailed information about the selected village.

2.Header Information

• Microplan Name: Displays the name of the microplan associated with the village.

• Displays the Hierarchy of the village.

3.Security & Accessibility

• Village Security: Provides an input field for entering security details about the village.

• Master Details :

  • Security Questions

    1. Is your village prone to civil unrest like violent protests, riots, etc.? Captures the frequency of civil unrest occurrences using the following options:

       • All the time (At least once a month): Frequent civil unrest.

       • Often (At least once a year): Civil unrest occurs occasionally but is a notable concern.

       • Rarely (Once in 2–3 years): Rare civil unrest.

       • Never: No recorded instances of civil unrest.

    2. How often do the security forces patrol the village? Measures the frequency of security patrols to ensure safety, with the following options:

       • Every day: Daily security patrols.

       • Often (At least once a week): Regular but less frequent patrols.

       • Rarely (Once in a month): Infrequent security patrols.

       • Never: No security patrols.

• Village Accessibility: Allows entering accessibility details for the village.

• Master Details :

  • Village Road Condition: Captures the type of road infrastructure present in the village. The options include:

    • Concrete: Indicates the presence of a well-paved concrete road.

    • Gravel: Represents roads made of gravel.

    • Dirt: Denotes unpaved roads made of dirt or soil.

    • No Road: Indicates the absence of any road infrastructure.

  • Village Terrain: Specifies the geographical terrain of the village. The available options are:

    • Mountain: Villages located in mountainous areas.

    • Forest: Villages surrounded by dense forest areas.

    • Plain: Villages situated in flat, open landscapes.

    • Desert: Villages located in arid, desert regions.

4.Population Data

The data displayed here can be reviewed, modified, and validated by the appropriate users, depending on their role.

Data Table:

Note : The data inside table will change based on selected campaign.

Steps

Note : the data inside table will change based on selected campaign.

Actions:

• Edit Population Data: If needed, the confirmed population data can be modified.

• Cancel: Discards any changes made to the population data.

• Submit and Validate:

  • If the Root Population Data Approver (RPDA) is logged in, they can directly validate the data.

  • If the Population Data Approver (PDA) is logged in, the data will move to the "Pending for Approval" status and will need further validation by higher-level approvers.

5.Comment Logs

• View Comment Logs: This feature displays the history of changes and comments made about the village's population data, enabling transparency and tracking.