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
  • Step 1: Registration and Distribution Process Selection
  • Step 2: Assumptions Form

Was this helpful?

Export as PDF
  1. TECHNOLOGY
  2. Architecture
  3. Services
  4. HCM Microplan Web
  5. Set Up Microplan

Microplan Assumptions

PreviousData for Assumptions and FormulaeNextFormula Configuration

Last updated 4 months ago

Was this helpful?

The Microplan Assumptions step is designed to streamline the process of defining critical campaign-related hypotheses based on the selected Resource Distribution Strategy and Campaign Type. This step consists of two substeps:

Step 1: Registration and Distribution Process Selection

This screen adapts based on the Resource Distribution Strategy chosen during the Campaign Details step.

1. Mixed Strategy:

For campaigns following the Mixed Strategy, 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.

Prompts:

  1. How is the campaign registration process happening?

    • Users are required to select from predefined options such as House-to-House, Fixed, Mixed, etc.

  2. How is the campaign distribution process happening?

    • Users must select a different option (when the campaign registration process is not Mixed) from the registration process, tailored to the distribution method (For example: House-to-House, Fixed, Mixed, etc.).

This distinction ensures that the two processes are appropriately differentiated and configured.

2. Fixed or House-to-House Strategy:

For these strategies, users are prompted to specify the relationship between registration and distribution processes:

Question:

  • Is the registration and distribution process happening together or separately?

    • Options:

      • Together

      • Separately

The response determines how the system pre-configures subsequent assumptions.

Step 2: Assumptions Form

Once the registration and distribution process is selected, users proceed to the Assumptions Form, which dynamically adapts based on campaign-specific parameters.

Configurability of Assumptions Data (Categories and Assumptions)

  • The Campaign Type (For example: Bednets, SMC)

  • The Resource Distribution Strategy (For example: House-to-House, Fixed, Mixed)

Examples of some dynamic categories of Assumptions:

  1. General Assumptions:

    • High-level parameters that apply to the overall campaign.

  2. Registration Assumptions:

    • Assumptions are specific to how and where registration activities occur.

  3. Distribution Assumptions:

    • Parameters defining the methodology and logistics for distributing resources.

  4. Commodities Assumptions:

    • Details about distributed items, such as the number of bednets per household.

Features of the Assumptions Form:

  1. Input Values:

    • Users must input specific values for each assumption.

    • Validation Rules:

      • Assumption values must:

        • Be numerical and are mandatory. and fall within the range of 0 to 1000.

        • Contain at most two decimal places (For example, 12.34 is valid, but 12.345 is not).

        • Adhere to a specific format, ensuring they match the pattern of a valid decimal or whole number (For example, 123.45 or 678).

    • Tooltips:

      • Each category includes input parameters with tooltips that provide detailed information when users hover over the respective field.

  2. Manage Assumptions:

    • Users can add new assumptions or delete existing ones based on campaign needs.

    • Initiate Adding an Assumption:

      • Users can click the "Add New Assumption" button from the assumptions management interface.

      • Assumption Details Input:

        • A popup/modal is displayed with the following fields:

          • Choose Assumption: A dropdown or selection box to choose an existing assumption or create a new one.

          • Assumption Name: An input field where users specify the name of the new assumption.

      • Confirmation Options:

        • Cancel: Discards the changes and closes the popup/modal.

        • Add: Saves the new assumption after passing validation checks.

  • Deleting Assumption

    • Users can click the 'Delete' button from the assumptions management interface.

    • Confirmation Options:

      • No: Discards the changes and closes the popup/modal.

      • Yes: Deletes the assumption.

    • Recovering deleted assumption:

      • Users can click the "Add New Assumption" button from the assumptions management interface and select the deleted assumption from the Choose Assumption dropdown.

Customisation and Management:

Each assumption category and its parameters are dynamically tailored based on:

  • The selected Campaign Type

  • The chosen Resource Distribution Strategy

The form fetches data from the and includes categories and assumptions customised according to:

MDMS