DIGIT Docs
Microplanning 0.2
Microplanning 0.1Microplanning 0.2
  • DIGIT Knowledge Base
  • Local Governance
Microplanning 0.2
Microplanning 0.1Microplanning 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. Set Up Microplan

Data for Assumptions and Formulae

PreviousData ManagementNextMicroplan Assumptions

Last updated 3 months ago

Was this helpful?

The Microplan Assumptions and Formulae are designed to streamline the process of defining critical campaign-related hypotheses based on the selected Resource Distribution Strategy and Campaign Type. Assumptions and formulae depend on the selections, such as campaign type, resource distribution strategy, registration, and distribution process happening together or separately, registration process, and the distribution process in the case of mixed resource distribution strategy. The campaign type options are from the MDMS data :

The Resource distribution Strategy can be Mixed, Fixed Post or House To House. If it is chosen as Mixed, then after completing the boundary selection and data management steps, the system prompts users to provide details for both the registration and distribution processes. They can choose from three options: Mixed, House to House, and Fixed Post. Both registration and distribution processes can be Mixed. However, the same method cannot be selected for both in the case of Fixed post and House to House. If the resource distribution strategy is chosen as Fixed Post or House To House, then users are prompted to specify the relationship between registration and distribution processes, whether the registration and distribution process happening together or separately.

The response determines how the system pre-configures subsequent assumptions, which will be from the data: The response determines how the system pre-configures subsequent formulae, which will be from the data:

Example:

The campaign type is selected as Bednet Campaign

The Resource distribution Strategy is selected as Mixed

As the mixed strategy is chosen for resource distribution, we need to provide details for both the registration and distribution processes:

This is how the data for the assumptions and formulae gets loaded based on the selections.

Based on our previous selections, the assumptions data will be chosen from:

Based on our previous selections, the formulae data will be chosen from:

HypothesisAssumptions
AutoFilledRuleConfigurations
MDMS
MDMS
MDMS