> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.0/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/setup-microplan/assumptions-and-formulae-data.md).

# Assumptions & Formulae Data

## Overview

The **Assumptions and Formulae** step helps the system automatically load campaign-specific logic based on the choices you make earlier. These configurations define how resources are calculated and distributed during the campaign.

The data shown in this step is **pre-configured and auto-loaded** from MDMS, based on your selections.

## Steps

### Step 1: Select the Campaign Type

* Choose a **Campaign Type** (for example, *Bednet Campaign*).
* Campaign types are loaded from [**MDMS**](https://unified-dev.digit.org/workbench-ui/employee/workbench/mdms-search-v2?moduleName=HCM-PROJECT-TYPES\&masterName=projectTypes).
* This selection acts as the primary driver for which assumptions and formulae are applicable.

<figure><img src="https://3976166735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmb5VUHEnO0msarLMPz6q%2Fuploads%2FMQ0RmHz0pieNsyzOPtoq%2Fimage.png?alt=media&amp;token=339a6610-f45f-4065-8587-b3aa12ca6b17" alt=""><figcaption></figcaption></figure>

### Step 2: Select the Resource Distribution Strategy

Choose how resources will be distributed during the campaign:

* **House to House**
* **Fixed Post**
* **Mixed**

Your selection here determines what additional details the system asks for and how assumptions and formulae are pre-configured.

<figure><img src="https://3976166735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmb5VUHEnO0msarLMPz6q%2Fuploads%2FygBSxyaIE3VbJoSoWbk5%2Fimage.png?alt=media&amp;token=3568e216-cf29-424b-ab57-e4f29dcd92c2" alt=""><figcaption></figcaption></figure>

### Step 3: Define Registration and Distribution Flow

If the Resource Distribution Strategy is **Mixed**

* You must configure **both**:
  * Registration process
  * Distribution process
* For each process, choose one of the following:
  * Mixed
  * House to House
  * Fixed Post
* Rules:
  * Both registration and distribution can be **mixed**.
  * **House-to-House** and **Fixed Post** cannot be selected together for registration and distribution.

{% hint style="info" %}
If the Resource Distribution Strategy is **House-to-House** or **Fixed Post**

* Specify whether:
  * Registration and distribution happen **together**, or
  * Registration and distribution happen **separately**.
* This choice controls how the campaign workflow is structured.
  {% endhint %}

<figure><img src="https://3976166735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmb5VUHEnO0msarLMPz6q%2Fuploads%2FKXLMODvicU9FeNzyHafG%2Fimage.png?alt=media&amp;token=a52226d8-3d12-4976-a828-6ad4a3f1e9a1" alt=""><figcaption></figcaption></figure>

### Step 4: System Loads Assumptions Automatically

* Based on:
  * Campaign type
  * Resource distribution strategy
  * Registration and distribution flow
* The system auto-loads the relevant assumptions from [**`HypothesisAssumptions`**](https://unified-dev.digit.org/workbench-ui/employee/workbench/mdms-search-v2?moduleName=hcm-microplanning\&masterName=HypothesisAssumptions) **(MDMS)**.
* These assumptions define campaign hypotheses such as coverage, effort, and operational constraints.

<figure><img src="https://3976166735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmb5VUHEnO0msarLMPz6q%2Fuploads%2FWRwxLuRSL8SjbVdUulGx%2Fimage.png?alt=media&amp;token=f20732ae-67e8-49d8-9c79-7e10a8619825" alt=""><figcaption></figcaption></figure>

### Step 5: System Loads Formulae Automatically

* Using the same selections, the system loads calculation rules from [**`AutoFilledRuleConfigurations`**](https://unified-dev.digit.org/workbench-ui/employee/workbench/mdms-view?moduleName=hcm-microplanning\&masterName=AutoFilledRuleConfigurations\&uniqueIdentifier=LLIN-mz.MIXED.SEPARATELY.MIXED.MIXED) **(MDMS)**.
* These formulae control how:
  * Resource quantities
  * Workforce requirements
  * Operational timelines are calculated in the microplan.

<figure><img src="https://3976166735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmb5VUHEnO0msarLMPz6q%2Fuploads%2FOEwdUvjW0Yg31uELo2rM%2Fimage.png?alt=media&amp;token=04c6b649-52d8-4a87-95ce-07f09553bd74" alt=""><figcaption></figcaption></figure>

### Example Flow

1. Campaign Type: **Bednet Campaign**
2. Resource Distribution Strategy: **Mixed**
3. Registration Process: **House to House**
4. Distribution Process: **Fixed Post**

Based on these selections:

* **Assumptions** are loaded from [`HypothesisAssumptions`](https://unified-dev.digit.org/workbench-ui/employee/workbench/mdms-view?moduleName=hcm-microplanning\&masterName=HypothesisAssumptions\&uniqueIdentifier=LLIN-mz.MIXED.SEPARATELY.MIXED.MIXED)
* **Formulae** are loaded from [`AutoFilledRuleConfigurations`](https://unified-dev.digit.org/workbench-ui/employee/workbench/mdms-view?moduleName=hcm-microplanning\&masterName=AutoFilledRuleConfigurations\&uniqueIdentifier=LLIN-mz.MIXED.SEPARATELY.MIXED.MIXED)

No manual configuration is required—the system selects the correct data automatically.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/health/v2.0/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/setup-microplan/assumptions-and-formulae-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.