Release Summary

Microplanning v0.1 has a total of 4 modules with multiple features that will let the microplanning teams or participants perform different activities for the microplan execution.

To learn more about the Health Campaign Management (HCM) product, click here.

Release Highlights

Module 1: Set up & manage

Set up and manage microplan

• Capture campaign details and administrative boundary

• Manage microplan data: Top-down population and facility data ingestion

• Configure microplan assumptions and estimation formula

• Create microplan users and manage their access

• Re-use existing microplan

Module 2: Validation

Validate and finalise population data for microplanning

• Validate top-down ingested population data of the villages

• Edit and update ingested population data of the villages

• Approve or reject updated/edited population data of the villages

• View status logs and user comments whenever population data is updated

• Finalise the microplan population data for the campaign region

Module 3: Map & assign

Assign facilities or point-of-services to their catchment areas

• View list of facilities belonging to the user’s jurisdiction

• Assign the catchment areas under the user’s jurisdiction to the facilities for service delivery

• De-assign the already assigned catchment areas under the user’s jurisdiction

• Finalise the facility-to-boundary mapping for the campaign region

Module 4: Estimation

Validate and finalise microplan estimation

• Validate microplan estimation created by the system

• Update microplan assumptions based on area accessibility and security levels

• Approve or reject updated/edited microplan estimation

• View status logs, change logs, and user comments whenever microplan estimation gets updated

• Finalise the microplan estimation for the campaign region

• Download and view the finalised microplan as an Excel

Known Limitations

There are some known limitations in the current release of the product and the required change requests have been raised to cater to the limitations. Some of the limitations are:

• Configuration of microplan assumptions as per the village’s/settlement’s accessibility or security in the estimation dashboard will not be available.

• The facility upload sheet will not accept the capacity of a facility as 0.

• Configuration of mixed distribution strategy (Fixed post + House-to-House) will not be available.

Click below to access the document:

Plan Service

Plan configuration

• Upload Data: Upload population and facility data required for census data approval, facility catchment and resource estimates. This data can be provided in the format of .xlsx (Excel)

  Note: While uploading data, it is important to note that location coordinates (latitude and longitude) are not mandatory for microplanning.

• Assumptions Configuration:

  Assumptions Configuration: Configure assumptions essential for the microplanning estimation processes. These assumptions might include demographic factors, resource availability, and operational constraints.

• Formula Configuration:

  Set up the formulae to calculate estimated resources, such as human resources, commodities, and budgets. This includes human resources, commodities, and budgets.

Plan estimates

• Activity Management: Define and manage the sequence and dependencies of activities required for a campaign.

• Resource Estimation: Saves the necessary resources for each activity, ensuring that all required materials and personnel are planned.

• Condition Monitoring: Set and monitor conditions that must be satisfied for activities to commence, ensuring the right prerequisites are met.

• Target Setting and Tracking: Define performance targets against these metrics to ensure campaign goals are met.

• Output Generation:

  Generate and save microplans.

Plan employee assignment features

• Hierarchical Assignment: Assign employees to roles based on different hierarchy levels (e.g., Province, District, or Village).

• Role Definition: Specify roles for employees, such as PLAN_ESTIMATION_APPROVER, to clearly define their responsibilities within the microplanning process.

• Jurisdiction Mapping: Link employees to one or more jurisdictions, ensuring operational clarity for each role and its geographical coverage.

Plan facility assignment feature

• Plan Configuration Association

  • The planConfigurationId links the facility mapping to a specific plan, allowing resources and operations to align with the corresponding microplanning requirements.

• Facility Details

  • The facilityId uniquely identifies a facility (e.g., health center, warehouse), providing precise mappings for service delivery or logistical purposes.

• Residing and Service Boundaries

  • Residing Boundary: Defines the geographical location or administrative boundary where the facility resides.

  • Service Boundaries: Specifies the areas serviced by the facility, supporting multi-boundary coverage.

• Custom Metadata (Extensibility)

  • The additionalDetails field allows for capturing detailed metadata about the facility, such as:

    • Facility type (e.g., "Warehouse").

    • Operational status (e.g., "Permanent").

    • Resource capacities (e.g., "Capacity: 500").

    • Fixed post status and population served.

Resource Estimation Service

• File Parsing and Resource Estimation:

  • The service processes multiple file formats (Excel, Shapefiles, GeoJSON) to estimate the resources required for a microplanning campaign.

  • It reads the input data, applies predefined assumptions and formulas, and calculates the necessary resources.

• Triggers for Plan-Facility Creation, Census Data Creation, and Plan Generation:

  • Plan-Facility Creation Trigger: When a facility file is uploaded, the service triggers the Plan-Facility Creation API from the project-factory. This ensures that the facilities are created based on the file contents.

  • Census Data Creation Trigger: When a population file is uploaded, the service triggers the Census Data Creation process. This involves reading the population file, processing the data, and updating the system with the relevant census information.

  • Plan Generation Trigger: After the census data is approved, the service reads the updated population file, updates the census data, and triggers the resource estimation and microplan generation based on the latest data detailing the necessary resources and their distribution for the campaign.

• Resource Mapping:

  • The service enriches the mapping of resource columns from the data upload to a predefined set of attributes required for each campaign. This ensures the resources are aligned with the necessary specifications.

• Upload Updated Result Sheet:

  • After the microplan is created and have gone through the estimation approval process, the updated approved resource estimations sheet is uploaded to the filestore and updated back into the plan configuration ensuring the latest version of the resource data is securely stored and accessible.

• HCM Console Integration:

  • The service integrates with the HCM Console, updating the project factory with the estimated resources. This ensures that the project factory always has the most accurate and up-to-date resource requirements for effective campaign planning and execution.

API List (New)