DIGIT Docs
Microplanning 0.2
  • DIGIT Knowledge Base
  • Local Governance
Microplanning 0.2
  • Introducing Microplanning
    • Release Notes
      • v0.2 Release Notes
        • Release Checklist
        • Technical Release Summary
        • Master Data Management Service (MDMS) and Configuration updates
        • Service Builds
        • UI/UX Audit
  • PRODUCT SPECIFICATION
    • User Manual
    • Product Requirement Document
      • SOPs
        • Guidelines
  • TECHNOLOGY
    • Architecture
      • High Level Design
      • Low Level Design
        • Plan Management
        • Census Management
        • Microplanning UI
          • System Admin Flow
          • Population Data Approval
          • Facility Catchment Mapping
          • Microplan Estimation Approval
      • Services
        • HCM Microplan Web
          • User Interface Design
          • Set Up Microplan
            • Microplan Details
            • Boundary Selection
            • Data Management
            • Data for Assumptions and Formulae
            • Microplan Assumptions
            • Formula Configuration
            • User Tagging
            • Summary Screen
          • User Management
            • Bulk User Create
            • Download Users Credentials
          • Supervisor Flows
            • User Interface Design
            • My Microplan
            • Select Activity
            • Validate And Approve Population Data
              • Village Details
            • Assign Facility To Villages
              • Village Assignment And Unassignment to Facility
            • Validate And Approve Microplan Estimation
          • Open Microplans: System Admin
            • Draft Flow
    • Specification
      • Plan Service
      • Resource Generator Service
      • Census Service
  • SETUP
    • Installation
    • Configuration
      • Advanced Configurations
    • QA Test Cases
    • Performance Testing
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page

Was this helpful?

Export as PDF
  1. TECHNOLOGY
  2. Architecture
  3. Services
  4. HCM Microplan Web
  5. Supervisor Flows

Assign Facility To Villages

PreviousVillage DetailsNextVillage Assignment And Unassignment to Facility

Was this helpful?

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

Role

Description

Role Code

Facility Catchment Mapper

Responsible for assingning facility to villages

FACILITY_CATCHMENT_MAPPER

Root Facility Catchment Mapper

Has additional permissions, including the ability to finalize catchment mapping

ROOT_FACILITY_CATCHMENT_MAPPER


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.


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:

Facility Detail

Description

Facility Name

Displays the name of the facility.

Facility Type

Displays the type of facility (e.g., Warehouse, Health Post).

Facility Status

Displays whether the facility is permanent or temporary.

Capacity

Shows the facility's capacity (e.g., Bales for bednets or Blisters for SMC campaigns).

Assigned Villages

Shows the number of villages assigned to the facility.

Serving Population

Displays the total population being served by the facility.

Fixed Post

Indicates if the facility is a fixed post.

Residing Village

Shows the name of the village where the facility resides.


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

Purpose

Endpoint

Method

Payload

Search for facilities

/plan-service/plan/facility/_search

POST

{ "PlanFacilitySearchCriteria": { "limit": 10, "offset": 0, "tenantId": "mz", "planConfigurationId": "297699ef-0041-4421-a4ae-acdd89c78e80", "jurisdiction": ["MICROPLAN_MO"], "facilityName": "", "residingBoundaries": [] } }

Search for project types

/project-factory/v1/project-type/search

POST

{ "CampaignDetails": { "tenantId": "mz", "ids": ["395adc89-6030-4347-ae5c-32a059f5aae5"] } }

Fetch chart data

/dashboard-analytics/dashboard/getChartV2?_=1733293436271

POST

{ "aggregationRequestDto": { "visualizationType": "METRIC", "visualizationCode": "totalFacilitiesWithMappedVillages", "filters": { "COUNTRY": ["MICROPLAN_MO"], "planConfigurationId": ["297699ef-0041-4421-a4ae-acdd89c78e80"], "tenantId": ["mz"] }, "moduleLevel": "MICROPLAN-FACILITY" }, "headers": { "tenantId": "mz" } }

Search census data

/census-service/_search

POST

{ "CensusSearchCriteria": { "tenantId": "mz", "facilityAssigned": false, "source": "297699ef-0041-4421-a4ae-acdd89c78e80", "jurisdiction": ["MICROPLAN_MO"] } }

Search for employees assigned to a plan

/plan-service/employee/_search?_=1733293435767

POST

{ "PlanEmployeeAssignmentSearchCriteria": { "tenantId": "mz", "active": true, "planConfigurationId": "297699ef-0041-4421-a4ae-acdd89c78e80", "employeeId": ["55392d76-9d87-4d4f-9ae9-2f44ff6968f2"], "limit": 5, "offset": 0 } }

MDMS Data is fetched from:

https://github.com/egovernments/egov-mdms-data/tree/UNIFIED-QA/data/mz/health/hcm-microplanning