Click below to access the document:

What is Health Campaign Microplanning?

Health campaign microplanning is a detailed planning approach used to ensure that health interventions, such as immunisations or disease prevention campaigns, are effectively delivered to target populations.

Microplanning helps to know:

1. Who needs the intervention?

2. Where is the intervention needed?

3. How many resources (medical supply, people, commodities, etc.) are needed for the intervention?

4. How will we reach the intervention site?

Challenges With Current Microplanning Process?

1. Prone to Errors: The process relies heavily on Excel, requiring meticulous care for resource estimation calculations, making it highly susceptible to errors.

2. Fragmented Management: Each district manages its microplan individually, leading to a back-and-forth process for collaboration. Incomplete data from any district results in faulty resource estimation for the entire campaign.

3. Complex Data Collection: Gathering and validating population data for microplan estimation is a tedious and poorly defined process. Incorrect population estimates can lead to inaccurate resource estimations for the campaign.

4. Time-Consuming Collaboration: Microplanning involves multiple people from various administrative levels to administer and validate resource estimations. Offline collaboration is time-consuming and increases the risk of errors if not managed carefully.

5. Lack of Reusability: Microplan estimations are created from scratch for each new campaign, making the process lengthy and time-consuming without the benefit of reusing previous plans.

Why Digitise the Microplanning Process?

Build capabilities that help maximise campaign coverage, enhance access for health campaigns and fairly estimate resources for microplaning. These can be achieved by the following:

1. Improve population denominator: Leverage data triangulation from multiple sources and validation from community leaders at village/settlement level to identify and improve population denominator.

2. Targeted Interventions: Leverage data to pinpoint high-risk and unsettled areas and tailor campaign strategies to specific geographic populations.

3. Optimized Resource Allocation: Analyze population distribution and resource needs to ensure efficient deployment of personnel, vaccines, and supplies.

4. Improved Outreach & Accessibility: Identify underserved communities and map optimal routes for campaign teams, maximizing outreach and access.

5. Increased Transparency & Accountability: Provide a clear picture of campaign coverage and resource distribution, promoting accountability to stakeholders and communities.

Goals for Building Microplanning 0.1

1. Enable countries to be able to collect and validate accurate population data for better & accurate microplan estimation.

2. Enable countries to have better accountability mechanisms and controlled access to ensure transparency and authorised access for microplan execution.

3. Enable countries to more accurately estimate and distribute resources, ensuring targeted regions are reached and health campaigns are executed smoothly.

4. To reduce the time to set up and finalise a microplan from an average of 3 months to 1 month.

Key Features

Set up & manage microplan

• Capture campaign details & administrative boundary

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

• Configure microplan assumptions & estimation formula

• Create microplan users & manage their access

• Re-use existing microplan

Validate & finalise population data for microplanning

• Validate top-down ingested population data of the villages

• Edit & 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

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

• View the 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

Validate & finalise the microplan estimation

• Validate microplan estimation

• Approve or reject 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

Geospatial view of microplan estimation

• View the microplan estimation for catchment boundaries on the geospatial map

• View the resource estimation for facilities on the geospatial map

• View the geospatial map with multiple base map layers

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.

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.

Census Service

The Census Service provides core functionalities for managing census data and integrating with Plan Service to support advanced microplanning and resource allocation:

• Census Record Creation:

  • Enables creation of census records for specific boundaries.

  • Supports categorization of records by population type (e.g., people, animals, plants, or others).

• Demographic Data Handling:

  • Facilitates storage of population data categorized by demographic variables (e.g., age, gender, ethnicity).

  • Allows detailed population distribution to be stored, enabling advanced analysis and planning (e.g., if categorizing by age : {"0-14": 10000, "15-24": 8000}).

• Boundary and User Validation:

  • Validates boundaries for census operations via the Boundary Service.

  • Verifies user roles for census actions, ensuring compliance with campaign and boundary rules.

  • Automatically manages census record validity periods, updating timeframes for new campaigns.

• Integration with Plan Service:

  • Works with the Plan Facility API to map facilities to boundaries, ensuring targeted resource allocation and seamless integration between Census and Plan Services.

  This service ensures precise demographic analysis, maintains data integrity, and integrates effectively with resource planning processes.

API List (New)

Introduction

This user manual is designed to guide system admins, population data approvers, facility boundary assigners, and microplan estimation approvers to use Microplanning for health campaigns.

User Roles

1. System administrator - This user is responsible for setting up the microplanning platform, such as selecting campaign boundaries, setting up the data, configuring the microplan assumptions, etc. This user will belong to the national/country-level administrative hierarchy.

2. Population data approver - This user will have access to the microplan module to view, validate, and approve the population of the assigned jurisdiction such as province, district, etc. The approved population will be used for the estimation of resources of the microplan.

3. National population data approver - This is a national/central level population data approver who will have access to approve and finalise the population data for the villages/settlements within the campaign boundary.

4. Facility boundary assigner - This user will have access to the microplan module to assign the facilities to their catchment boundaries concerning the user’s assigned jurisdiction such as province, district, etc.

5. National facility boundary assigner - This is a national/central level user, who will have access to the microplan module to assign the facilities to their catchment boundaries and finalize the facility to catchment area assignment for the villages/settlements within the campaign boundary.

6. Microplan estimation approver - This user will have access to the microplan module to view, edit, and approve the microplanning estimation concerning the user’s assigned jurisdiction such as province, district, etc.

7. National Microplan estimation approver - This is a national/central level user, who will have access to the microplan module to view, edit, and approve the microplanning estimation and finalize the microplan estimation for the villages/settlements within the campaign boundary.

Steps to Use Microplanning

Step 1 - How will the system administrator set up the microplan?

System role involved: System Administrator

1. First, select the language before you can log in. Currently, three languages are supported:

• English

• Portuguese

• French

Select the preferred language and click on 'Continue' to go to the login page.

(Note: Getting an account on HCM Microplanning: The implementation team will create the account for the system admin and the admin will be provided with a username and password to log into the account).

1. On the login page, enter the 'Username', 'Password', and the 'City' you are working in to log in to HCM Microplanning.

Once you log in, you will be landing on the homepage to take the next action.

1. Once you land on the homepage, you will see 3 different actions to choose from:

• Set Up Microplan: This is the capability that you will use to set up the microplan for a health campaign.

• Open Microplans: This is the capability that you will use to view the drafted and already created microplans.

• User management: You will use this capability to register the users with different roles that are part of the microplanning process.

1. If this is the first time a microplan is being set up, you must create the users who will be primarily working on the different microplanning activities.

As a system administrator:

1. You must click on the "User Management" module to start with.

2. Once you click on the "User Management" module, you can see the list of users who are already registered for different microplanning roles. The user details that you will be able to see are:

• Name: Name of the microplanning user

• Email: Email ID of the microplanning user

• Contact Number: Contact number of the microplanning user

• Role: The role that is assigned to the microplanning user

This is the dashboard view that you will get once you land on the user management module. If this is a first-time setup, there will be no user details available in the dashboard.

1. You can search users using the ‘Name’ or ‘Contact Number’ search fields.

2. You can filter out some users belonging to a role using the role filter available in the dashboard.

3. If you need to add new users to the microplanning module, then click on the "Bulk Upload Users" feature.

1. In the bulk upload user page, you can see a button called "Download Template", which will be used to register new users to the microplanning module.

2. Once you click on the ‘Download Template’ button, you will be able to download an Excel sheet that you will use to enter the new user details that are part of the Microplanning module.

The content of the template are:

• Read me: This sheet will have the details of how to fill the user template Excel and upload it for user registration.

• User roles: This sheet will have the list of roles available for user registration and the description of each role.

• Role mapping for each sheet: There will be a sheet defined in the template for each role available. Inside each of the role sheets, the system admin can fill in user details with -

- Name: Name of the user who will use the microplanning platform.

- Contact number: Contact number of the person who will use the microplanning platform.

- Email ID: Email ID of the person who uses the microplanning platform.

This is the template structure for adding the new user details.

1. Once the template is filled, you can upload the data and see a success message that the file has been uploaded successfully.

This is the screen that you will see when the template file is successfully uploaded.

This is the screen that you will see when the uploaded template file is successfully submitted.

1. Once the file is uploaded, you will be able to download the user credentials of the new users who are registered.

This is the capability that you will be able to download the user credentials of the registered users.

Content of the screen:

• File name and attachment: This will have the name of the file with a hyperlink to view and download the file.

• The downloaded file will have all the details of the file that was uploaded, along with the user login credentials for each of the users in the file.

• The downloaded file will have the login credentials that were generated by the system itself for the first time when the file was uploaded and submitted successfully.

• File uploaded by: This will show the name of the system administrator who uploaded and submitted the file.

• File uploaded time: This will show the timestamp of the file uploaded by the system administrator.

1. Once the user creation step is completed, you can start with the microplan setup process.

As a system administrator:

1. Using this screen, you can capture the campaign details for which the microplanning needs to be done. The components of this screen are -

• Disease identified for the campaign - By default ‘Malaria’ will be chosen as we are creating the microplanning for the assumptions of malaria. As and when new diseases come into the picture, we will add those diseases in the dropdown.

• Type of campaign - Upon choosing the disease, you will be asked to choose the campaign type, which is either ‘Bednet’ or ‘SMC’. As and when new campaign types come into the picture, we will add those campaign types in the dropdown.

• Resource distribution strategy - Upon choosing the campaign type, you will be asked to choose the distribution strategy, which is either ‘Fixed post’ or ‘House-to-House’ or ‘Fixed post & House-to-House’. Depending on the strategy chosen, the assumptions and resource estimation formula will be auto-configured in the platform.

Once you have chosen the required details, you can click on the "Save and Proceed" button to move to the next screen.

This is the screen that you will use to fill in the campaign details.

1. Using this screen, you can view the details of the campaign for which the microplanning needs to be done, and the user will be able to name the microplan accordingly for further use. The components of this screen are -

• Campaign details - The campaign basic details chosen in the previous screen such as campaign disease, campaign type, and resource distribution strategy will be shown here.

• Naming of microplan - The microplan name will be auto-suggested by the system. The structure of the microplan name is "Disease-CampaignType-Resource distribution strategy-MonthLast2digitsOfYear". The name is a suggested name and you can edit the microplan name if required. It’s a mandatory field.

• Microplan naming format - This segment talks about the criteria for creating a microplan name if you want to self-create a microplan name. The naming conventions are:

- The name should be a minimum of 3 characters in length

- Only numeric values are not allowed

- Special characters -, _, (, ),& are only allowed

Once you have finalised the microplan name, you will have to click on the "Save and Proceed" button to move to the next screen.

This is the screen that you will use to edit and finalise the microplan name.

1. Once you have finalized the microplan name and campaign details, you will not be allowed to edit the campaign details if you save the details and move to the next screen.

You will see a warning pop-up to confirm if you want to save and move to the next screen:

This is the warning pop-up that you will see before you move to the next screen.

1. This step will let you select the existing boundary data in the system. (This is a mandatory field for moving to the next screen). The boundary data will have to be set up in the system beforehand at the time of instance creation and the same boundary data should be reused by the user for all campaigns in a given instance.

(Note: If you have not selected boundaries, you will not be allowed to move on to the next steps. For example: If the boundary data is set up for Mozambique, the user will see the whole boundary mapping for Mozambique that is available on the system. If there is a need for change, we will provide the contact information for the support team to update the boundary and the support team will update the boundary data).

The boundary selection for a campaign will happen through a mapped checkbox field as shown below. There is a drop-down-based selection for each level of the hierarchy:

This is the boundary selection screen that you will need to configure.

If a given boundary is selected in one level of the hierarchy, the next level will show boundaries mapped to only the ones selected in the previous level. You will not be able to make any selection at a given level without selecting the boundaries in the level above.

After you have selected the boundaries, click on the "Save and Proceed" button.

1. Here, you will set target and total population data for the microplan by default at the lowest level of the administrative hierarchy boundaries. This will be achieved by an Excel upload as explained below:

To set target and total population data, click on “Download Template” on this screen. You will download the template having all the boundaries in Excel with an empty column for setting population data.

Note: Each campaign will have its target-setting template: For example, the bednet campaign will have its template, and the SMC campaign will have its template.

The first tab/sheet will be the “Read Me” tab and will have the information on how you can set the targets for each village selected in the boundary selection screen.

The district-wise sheets will have the following structure:

Note: All the villages in the Excel will be listed based on the district they belong to, with one tab for each district having a list of the villages under them. For example, if you have selected 20 districts, you will see 20 tabs (one for each district) having all the villages belonging to that particular district.

You must adhere to the guidelines while entering the population data and uploading it for the microplanning estimation. The guidelines are below for population data upload -

• The mandatory fields such as total population and target population data must be a whole number (For example, population can be 1234 and not 123.5)

• The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds (Value should be 12.3455 & not 12° 20' 43.7994")

Some of the validation you need to take care of while uploading the population Excel file:

• You can’t upload a file with empty population data for one or more villages in the sheet

• The population data for a village must be a whole number, else the file will not be uploaded

• You can’t delete any of the columns in the file before uploading it

• You can’t change the column structure in the file before uploading it

• You can’t delete any of the sheets in the Excel before uploading it

• You can’t upload a file with negative population data for a village in the sheet

• You must adhere to the standard structure of the latitude & longitude before you upload the file with the latitude and longitude of the villages

Once you have uploaded the population data, click on "Save and Proceed" to move to the facility upload page.

This screen will be used for uploading the population data.

This screen shows the validation when the population file is uploaded successfully.

1. Once the population file is uploaded, you need to upload the facility sheet to configure the facilities that will be used in the microplanning process.

To configure the facility data for the microplan, you will have to download the facility upload sheet using the ‘Download Template’ button.

If you already have a facility registry set up in the instance where the microplan is getting configured, those facilities will be pre-populated in the downloaded template. You can also add new facilities in the template, which will be considered for the current microplan.

The facility template structure is below:

The facility template will have 3 different Excel sheets:

- Read me: This will help you know the steps to configure the facilities required for microplanning.-

- List of available facilities:

• Facility Name: If the instance already has facilities defined, then you will be able to see the names of the facilities that are existing.

• Facility Type: If the instance already has facilities defined, then you will be able to see the type of facilities that are linked to each facility. The facility type for an instance will be defined in the MDMS during instance creation.

• Facility Status: If the instance already has facilities defined, then you will be able to see the status of the facilities that are existing. The facility status for an instance will be defined in the MDMS during instance creation.

• Capacity: If the instance already has facilities defined, then you will be able to see the capacity of the facilities that are existing. The definition of capacity of the facility is defined in the MDMS during instance creation.

• Facility usage: If the instance already has facilities defined, then you will be able to see the usage status of the facilities that are existing. ‘Active’ usage status means the facility is operational for the campaign and ‘Inactive’ usage status means the facility is non-operational for the campaign. The usage status is defined in the MDMS during instance creation.

• Serving population per campaign: This will define the total population that can be served by the facility in a campaign.

• Is fixed post?: If the instance already has facilities defined, then you will be able to see if the facilities will be catered as a fixed post. The fixed post tag will only be functional when the resource distribution strategy is either Fixed post or House-to-House & Fixed post (Mixed). For instance, the fixed post tag will be defined for a facility unless it is manually changed by the user.

• Residing boundary code: The residing boundary code defines where exactly the facility resides. The user can tag the boundary where the facility resides using the residing boundary sheet. The residing boundary of the facilities will be saved for the instance and it can be changed as per the user’s requirement during the facility configuration. This will be a dropdown option.

• Latitude & Longitude: Here the user will be asked to enter the latitude & longitude of the facility to be shown on the map. This is optional data.

- Boundary data: This sheet will give you the administrative boundary where the microplan is being set up. This will also give the boundary codes for each administrative boundary, which can be used for tagging the facilities to their respective boundaries.

You must adhere to the guidelines while entering the facility data and uploading it for the microplanning estimation. The guidelines are below for population data upload -

• All the fields are mandatory and can't be empty, except the Latitude and Longitude fields

• The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds (Value should be 12.3455 & not 12° 20' 43.7994")

Some of the validation you need to take care of while uploading the population Excel file:

• You must fill in all the mandatory fields before uploading the facility Excel file

• For all the values of each column of data, you must choose the value from the dropdown to upload the Excel file

• You can’t delete any of the columns in the file before uploading it

• You can’t change the column structure in the file before uploading it

• You can’t delete any of the sheets in the Excel before uploading it

• You can’t upload a file with negative facility capacity for a facility in the Excel sheet

• You must adhere to the standard structure of the latitude & longitude before you upload the file with the latitude and longitude of the villages

• You must choose the correct facility residing code, from the Boundary code sheet, for tagging the facility to its boundary

Once you have uploaded the facility template, click on "Save and Proceed" to move to the facility upload page.

This screen will be used for uploading the facility data.

This screen shows the validation when the facility file is uploaded successfully.

1. Once the data management step is completed, you will be directed to the microplan assumption module.

Here, you will be asked some preliminary questions, the answers to which will provide an ideal estimate assumption form for you.

This is the screen for answering the preliminary questions.

Since you have chosen the resource distribution strategy as "House-to-House & Fixed post", you will have to answer the following questions:

• How is the campaign registration process happening?

• How is the campaign distribution process happening?

You can choose either House-to-House or Fixed post and depending on what you have selected, the microplan assumptions will be configured on the next page accordingly.

Here, once the previous questions are answered, you will move to the microplan assumption page to enter the microplan assumptions as per the campaign requirements.

This is the screen for entering the general assumptions for the microplan.

This is the screen for entering the registration assumptions for the microplan.

This is the screen for entering the distribution assumptions for the microplan.

This is the screen for entering the commodities assumptions for the microplan.

This is the screen for entering the vehicle assumptions for the microplan.

Here is the sheet containing the information for all the assumptions as per the campaign type and the distribution strategy:

All the assumptions shown above are configured as per the campaign type and distribution strategy chosen.

You can add a new assumption, if required, using the "Add assumption" button.

You can delete the already configured assumptions, if required, using the ‘Delete’ button beside the assumption.

Once all the assumptions are configured, click on "Save and Proceed" to move to the next section of the microplan formula configuration.

1. Once the assumptions are configured, you will be moved to the microplan formula configuration.

Here, you will be able to see the formulas that are pre-configured for the campaign type and distribution strategy chosen.

And you must configure the microplan assumptions properly as the formulas will be dependent on the assumptions you have configured.

This is the screen for viewing the general estimations formula.

This is the screen for viewing the registration estimations formula.

This is the screen for viewing the distribution estimations formula.

This is the screen for viewing the commodities estimations formula.

This is the screen for viewing the vehicle estimations formula.

Here is the sheet containing the information for all the estimation formulas as per the campaign type and the distribution strategy:

All the estimation formulas shown above are configured as per the campaign type and distribution strategy chosen.

You can add a new estimation formula, if required, using the "Add formula" button.

You can delete the already configured estimation formula, if required, using the ‘Delete’ button beside the pre-configured formula.

Once all the estimation formulas are configured, click on "Save and Proceed" to move to the next section of user access management.

1. Once the formula configuration has been completed, you will be moved to the user access management for configuring the users who will be performing the microplanning activities.

Here, you can choose and attach the selected users to the microplan.

This screen is for adding the users belonging to the ‘National Microplan estimation approver’ to the microplan using the "Assign National Microplan Estimation Approver" button.

This is the pop-up that you will use to search for the user to whom you want to assign the microplan.

This screen shows the users with the "National microplan estimation approver" role you added to this microplan. You can also un-assign the assigned users from the microplan using the ‘Unassign’ button.

This screen is for adding the users belonging to the "National facility boundary assigner" to the microplan using the "Assign National Facility Boundary Assigner" button.

This is the pop-up that you will use to search for the user to whom you want to assign the microplan.

This screen shows the users with the "National facility boundary assigner" role you added to this microplan. You can also un-assign the assigned users from the microplan using the ‘Unassign’ button.

-------------------------------------------------------------------------------------------------------------------

This screen is for adding the users belonging to the "National population data approver" to the microplan using the "Assign National Population Data Approver" button.

This is the pop-up that you will use to search for the user to whom you want to assign the microplan.

This is the screen that shows the users with the "National population data approver" role that you have added to this microplan. You can also un-assign the assigned users from the microplan using the ‘Unassign’ button.

This screen is for adding the users belonging to the "Microplan estimation approver" to the microplan using the ‘Assign Microplan Estimation Approver’ button.

This is the pop-up that you will use to search for the user to whom you want to assign the microplan.

This is the screen that shows the users with the "Microplan estimation approver" role that you have added to this microplan. You can also un-assign the assigned users from the microplan using the ‘Unassign’ button.

This screen is for adding the users belonging to the "Facility boundary assigner" to the microplan using the "Assign Facility Boundary Assigner" button.

This is the pop-up that you will use to search for the user to whom you want to assign the microplan.

This screen shows the users with the "Facility boundary assigner" role you added to this microplan. You can also unassign the assigned users from the microplan using the ‘Unassign’ button.

This screen is for adding the users belonging to "Population data approver" to the microplan using the "Assign Population Data Approver" button.

This is the pop-up that you will use to search for the user to whom you want to assign the microplan.

This is the screen that shows the users with the "Population data approver" role that you have added to this microplan. You can also un-assign the assigned users from the microplan using the ‘Unassign’ button.

Now that you have assigned the required users to the microplan, you can click on "Save and Proceed" to go to the next and final phase of the microplan setup.

1. You are now at the last leg of setting up the microplan.

In the summary screen, you can view all the tabs and make edits before finalising the microplan setup.

This summary screen shows you all the tabs of microplan configuration.

This is the finalised microplan setup screen. Once the microplan setup is done, you cannot make any changes in the microplan. Now the microplan is ready for the next set of activities to be executed.

1. Here, you will click on "Open Microplan" to view the list of the microplans that are either in created or in drafted status.

The microplan can be in any of the following statuses at a time:

• Drafted: This status indicates that the microplan is partially configured and the setup isn’t completed yet.

• Completed setup: This status indicates that the microplan setup has been completed and now the microplanning activities can be started.

• Validation in progress: This status indicates that the microplan validation process has started.

• Microplan finalised: This status indicates that the microplan estimation has been finalised and completed.

The dashboard has a total of 6 columns:

• Name of the microplan: It indicates the name of the microplan

• Status of microplan: It indicates the current status of the microplan

• Campaign disease: It indicates the campaign disease for the microplan

• Campaign type: It indicates the type of the campaign for the microplan

• Distribution strategy: It indicates the distribution strategy of the campaign for the microplan

• Action: It indicates the action that can be taken in the microplan.

Available actions are -

1. Edit microplan: If the microplan status is drafted, you can edit the microplan before finalizing it.

2. View summary: If the microplan setup is completed, you can only view the summary of the microplan. You will not be able to edit the microplan.

3. Download: If the microplan estimation is finalised, you can download the microplan estimation in Excel format.

This is the view of the ‘Open microplan’ dashboard.

Step 2 - How will the population data be validated and approved for microplan estimation?

System role involved: National population data approver, Population data approver

1. You must first select the language before you can log in. Currently, 3 languages are supported for the HCM Microplanning platform. They are:

• English

• Portuguese

• French

Select the preferred language and click on 'Continue' to go to the login page.

(Note: Getting an account on the HCM Microplanning platform: The microplanning users with different roles will have their account created by the system admin and will be provided with a username and password to log in to the account).

1. On the login page, enter the 'Username', 'Password', and the 'City' you are working in to log in to the HCM Microplanning platform. You need to use the login credentials belonging to the ‘Population data approver’ or ‘National population data approver’ roles.

Once you log in, you will be landing on the homepage to take the next action.

1. Once you are on the home page, you will be able to see the "My Microplan" segment.

This is the view of the "My Microplans" segment.

By clicking the "My Microplan" segment, you will be able to see the list of Microplans that you are part of.

This is the dashboard that will show you the list of microplans assigned to you.

The data points that are available on this dashboard are:

• Name of Microplan: This field will show you the name of the microplan assigned to you.

• Status: This field will show the status of the microplans assigned to you. A microplan can be in either of the following statuses:

- Completed setup: This status means that the assigned microplan setup is completed and it’s ready for validation activities.

- Validation in progress: This status means that the assigned microplan is being validated by the assigned microplanning users.

- Microplan finalised: This status means that the assigned microplan’s estimation has been reviewed and finalized by the validation team.

• Campaign Disease: This field will show you the campaign disease for which the microplan was set up.

• Campaign Type: This field will show you the type of campaign for which the microplan was set up.

• Distribution Strategy: This field will show you the distribution strategy that is considered for the campaign assigned to the microplan.

• Action: This button will let you take the set of actions you want to perform in the selected microplan.

You can also search a microplan using the ‘Microplan Name’ search on top.

1. Once you choose the microplan on which you want to act, you will be redirected to an activity selection screen.

This is the view for the activity selection screen.

Once here, if you are logged in as a "Population data approver" role, you will have to click on the "Validate & Approve Population Data" tab. The population data will refer to the top-down uploaded population data by the system administrator while setting up the microplan.

This is the first and the critical step, without the validation and finalization of the population data, you will not be able to move ahead with other activities.

1. You will click on the "Validate & Approve Population Data" tab, and you will be redirected to the population validation page where you need to validate the population for each village or settlement under your jurisdiction.

This is the view for the population validation screen.

In this dashboard you will be able to see:

- List of villages that are assigned to you and others for validation. You can filter out the villages that are assigned to you and others by using the tabs "Assigned to me" and "Assigned to all".

- List of villages as per their validation status. You can filter out the villages with different statuses such as:

• Pending for validation: This status shows the list of villages under your jurisdiction and has not been validated yet.

• Pending for approval: This status shows the list of villages under your jurisdiction and has not been approved yet. You will only see villages in this status if any of your subordinates have updated the target or total population data for the villages under their jurisdiction and they have sent the villages to you for approving the changes made.

• Validated: This status shows the list of villages under your jurisdiction and has been validated either by you or your subordinates or your supervisors.

- You can also filter out the villages concerning their administrative hierarchy and administrative area using the filters available at the top.

- In the village details, you will be able to see:

• Village name: This indicates the name of the villages assigned.

• Assignee: This indicates the name of the person responsible for validating the village population data.

• Uploaded total population: This indicates the total population data that was uploaded by the central team or system administrator while setting up the microplan.

• Confirmed total population: This indicates the total population data for the village, which will be used for microplan estimation. Here, the uploaded total population will be the same as the confirmed total population.

• Uploaded target population: This indicates the target population data that was uploaded by the central team or system administrator while setting up the microplan.

• Confirmed target population: This indicates the target population data for the village, which will be used for microplan estimation. Here, the uploaded target population will be the same as the confirmed target population.

• Status logs: This indicates the status of each village (Validated, Sent for correction, or Approved), who changed the status, at what time the status was changed and what was the reason for the change.

Note: There will be a couple more columns such as confirmed and uploaded target population as per age groups for the SMC campaign.

This is the view of the status logs.

Now, if you agree to the confirmed population data in this dashboard, you will have to choose the villages and click on the ‘Validate’ button to validate the village population data.

Once you click on the ‘Validate’ button, you will be asked to enter a comment/reason for validation. This is non-mandatory and can be made mandatory depending on the microplan requirement.

This is the screen for validating the village population data.

This is the pop-up for adding a reason/comment of validation. Adding a reason/comment is non-mandatory.

In case you aren’t aligned with the confirmed population data of the village, you can click on the ‘edit’ button beside the confirmed population data to update it.

Once you update the confirmed population data, that particular village will move to the "Pending for approval" status of your supervisors to validate & approve the data.

This is the pop-up screen for editing/updating the village population data.

This is the pop-up for adding a reason/comment for sending the data for approval. Adding a reason/comment is non-mandatory.

Now, if you log in with a superior role such as "National population data approver", you will be able to see the villages that are assigned to you for approval.

As a supervisor with a "National population data approver" role, you will be able to take either of the following actions on the villages assigned to you:

• You can send back the data for correction: If you are not aligned with the population data update done by your subordinate, you can choose to send back the village data to your subordinate with a valid reason for rejection.

• You can approve the changes made in the village population data: If you are aligned with the population data update done by your subordinate, you can choose to approve the data with a reason for approval. Again, adding reason is a non-mandatory step.

This is the screen showing the list of villages that are pending for approval.

This is the pop-up you will get if you choose to send back any village data for correction. Adding the comment/reason is non-mandatory.

This is the pop-up you will get if you choose to approve the village data. Adding the comment/reason is non-mandatory.

Once the villages are validated, you should be able to see them in the ‘Validated’ bucket. Here, if you are not aligned with any of the village data that is validated, you will have the ability to send back the data for correction to the subordinate, who had earlier validated the data.

This is the dashboard showing the villages that are already validated. You get an option to send back any of the villages for correction if you are not aligned with the validated population data.

This is the pop-up you will get if you choose to send back any village data for correction. Adding the comment/reason is non-mandatory.

Once all the villages under your jurisdiction are validated, you should be able to see the villages in the ‘Validated’ bucket. You can go back to the home screen since your activity is completed.

This is the dashboard view when all the villages, under your jurisdiction, are validated.

Here, if all the users assigned to the "Population data approver" role have validated all the villages under their jurisdiction, the user with the "National population data approver" role will get a button called "Proceed To Finalise Population Data" to finalise the population data for the campaign boundaries. Once the population data is finalized, the same population data will be used for the microplan estimations.

This is the view that the "National population data approver" gets once all the villages in his jurisdiction are validated.

This is the pop-up that the "National population data approver" gets once he clicks on the "Proceed To Finalise Population Data" button.

This screen shows that the population data has been finalised for microplan estimation.

You can now click on the ‘Go back to home’ button to go back to the "My Microplans" dashboard, as your assigned activity has been completed.

Step 3 - How will the facility to catchment area mapping be done?

System role involved: National facility boundary assigner, Facility boundary assigner

1. You must first select the language before you can log in. Currently, 3 languages are supported:

• English

• Portuguese

• French

Select the preferred language and click on 'Continue' to go to the login page.

(Note: Getting an account on the HCM Microplanning platform: The microplanning users with different roles will have their account created by the system admin and will be provided with a username and password to log in to the account).

1. On the login page, enter the 'Username', 'Password', and the 'City' you are working in to log in to the HCM Microplanning platform. You need to use the login credentials belonging to the "Facility boundary assigner" or "National facility boundary assigner" roles.

Once you log in, you will be landing on the homepage to take the next action.

1. Once you are on the home page, you will be able to see the "My Microplan" segment.

This is the view of the "My Microplans" segment.

By clicking on the "My Microplan" segment, you can see the list of Microplans that you are part of.

This is the dashboard that will show you the list of microplans assigned to you.

1. Once you choose the microplan on which you want to act, you will be redirected to an activity selection screen.

This is the view for the activity selection screen.

Once here, if you are logged in as a "Facility boundary assigner" role, you will have to click on the "Assign Facilities To Villages" tab.

This is the second step, without finalizing the facility-boundary assignment mapping, you will not be able to move ahead with the next activity.

1. You will click on the "Assign Facilities To Villages" tab, which will redirect you to the facility assignment screen where you will need to assign the facilities under your jurisdiction to their respective catchment boundaries (Example: villages).

This is the dashboard view you will see when you log in as either the "Facility boundary assigner" or "National facility boundary assigner" role.

In this dashboard, you will be able to:

• Search and filter facilities as per the "Facility name", "Facility type", "Facility status", and "Administrative area".

• Tabular view of data having below points:

• Facility Name: This indicates the name of the facility assigned to you.

• Facility Type: This indicates the type of facility assigned to you.

• Facility Status: This indicates the status of the facility assigned to you.

• Capacity: This indicates the storage capacity of the facility. It can be either ‘Bales’ for the LLIN campaign or ‘SPAQs’ for the SMC campaign.

• Assigned Villages: This indicates the count of villages that are assigned to the chosen facility.

• Serving Population: This indicates the sum of the target population of the villages that will be served by the chosen facility.

• Fixed Post: This indicates if the facility is fixed post or not.

• Administrative Area: This indicates the administrative boundary to which the facility is mapped.

• Assign: Assign indicates that you can either assign some villages or administrative boundaries to the facility for defining the catchment area or you can de-assign the some villages or administrative boundaries that are already assigned to the chosen facility.

1. You will click on the ‘Assign’ button, which will redirect you to the boundary assignment/assignment dashboard.

Here, you can see 2 different tabs, one that shows the list of villages, that are not assigned to any facility called the ‘Unassigned Villages’ tab, and the other that shows the list of villages, that are already assigned to the chosen facility called "Assigned Villages" tab.

This is the view for de-assigning or assigning the villages to the chosen facility.

1. In the "Unassigned Villages" tab, you will see the list of villages that are yet to be assigned to a facility for defining their service boundary.

On this page, you can filter out the villages as per their administrative hierarchy and administrative areas from the filter segment above.

You can select one or more villages that can be considered as the catchment boundaries for the chosen facility and then click on "Add to facility" to add the selected villages to the chosen facility.

This is the view that you will get once you choose the villages for the facility assignment.

1. Once the villages are assigned to the facility, you will be able to see the assigned villages in the "Assigned Villages" tab. The assigned villages define the catchment boundary for the chosen facility.

On this page, you can filter out the villages as per their administrative hierarchy and administrative areas from the filter segment above.

You can select one or more villages that can be de-assigned from the chosen facility. Once de-assigned, the village will not be part of the catchment boundary of the facility anymore. The de-assigned villages can be reassigned to the chosen facility from the "Unassigned Villages" tab.

This is the view that you will get once the villages are assigned to the chosen facility. You can choose to de-assign the villages from this dashboard.

1. Once all the villages under the campaign boundary are assigned to their catchment or service facilities, then, if you are logged in as a ‘National facility boundary assigner’, you can see a button called "Proceed To Finalise Facility Assignment".

This is the button you will see as a "National facility boundary assigner" once all the villages under the campaign boundary have been assigned to their catchment facility.

1. If you are logged in as a "National facility boundary assigner", you can see and click on "Proceed To Finalise Facility Assignment" to finalise the facility assignment for the campaign boundary.

Here, once you click on this button, you will be shown a pop-up asking you to verify the facility assignment and then finalize the assignment. Once finalized, you can make any changes to the facility assignment.

This is the warning pop-up you will see when you try to click on the "Proceed To Finalise Facility Assignment"’ button.

1. Once you click on the button shown in the pop-up called "I Want To Finalise", you will see the activity completion screen showing the facility assignment is completed successfully.

This is the screen you will see when the facility assignment is completed.

You can now click on the "Go back to home" button to go back to the "My Microplans" dashboard, as your assigned activity has been completed.

Step 4 - How will the microplan estimations be validated and approved?

System role involved: Microplan estimation approver, National microplan estimation approver

1. You must first select the language before you can log in. Currently, 3 languages are supported for the HCM Microplanning platform. They are:

• English

• Portuguese

• French

Select the preferred language and click on 'Continue' to go to the login page.

(Note: Getting an account on the HCM Microplanning platform: The microplanning users with different roles will have their account created by the system admin and will be provided with a username and password to log in to the account).

1. On the login page, enter the 'Username', 'Password', and the 'City' you are working in to log in to the HCM Microplanning platform. Use the login credentials belonging to the "Microplan estimation approver" or "National microplan estimation approver" roles.

Once you log in, you will be landing on the homepage to take the next action.

1. Once you are on the home page, you will be able to see the "My Microplan" segment.

This is the view of the ‘My Microplans’ segment.

By clicking on the ‘My Microplan’ segment, you can see the list of Microplans that you are part of.

This is the dashboard that will show you the list of microplans assigned to you.

1. Once you choose the microplan on which you want to act, you will be redirected to an activity selection screen.

This is the view for the activity selection screen.

Once here, if you are logged in as a ‘Microplan estimation approver’ role, click on the "Validate & Approve Microplan Estimations" tab.

This is the third and final step where the microplan estimation for all the villages under your jurisdiction needs to be validated and finalized for executing the microplan.

1. Once you click on "Validate & Approve Microplan Estimations", you will be redirected to the dashboard to validate the microplan estimations for the administrative areas under your jurisdiction.

This is the dashboard for validating & approving the microplan estimation for the administrative areas under your jurisdiction.

In this dashboard you will be able to see:

• Administrative hierarchy and administrative are filters to filter out administrative areas under a specific administrative hierarchy.

• ‘Assign to me’ or ‘Assign to all’ filters will show you the list of villages that are yet to be validated by either you, or your subordinates, or your supervisors.

• Status filter to filter out the administrative areas or villages as per their status. The filters are:

• Pending for validation: This status shows the list of villages under your jurisdiction and has not been validated yet.

• Validated: This status shows the list of villages under your jurisdiction and has been validated either by you or your subordinates or by your supervisors.

• In the tabular view of the data, you will be able to see the microplan estimation data for all the villages under your jurisdiction. The columns shown in the dashboard will change depending on the campaign type and distribution strategy chosen.

The tabular data will have the list of microplan estimations, for the villages, that need to be validated by either you, or your supervisor, or your subordinate.

1. Once you have checked the microplan estimations for all the villages under your jurisdiction and if you are fine with the estimation numbers, you can click on the villages that you want to validate and then click on the ‘Validate’ button.

Once you click on the ‘Validate’ button, the selected villages will move away from the ‘Pending for validation’ bucket to the ‘Validated’ bucket.

Any action that you take in the dashboard for a village will be recorded and can be seen by anyone using the "Status logs" button.

This is the view of the dashboard to validate the microplan estimation for the concerned villages.

This pop-up will be shown to you when you click on the ‘Validate’ button. You, as a microplan estimation approver, can enter any comment or reason for validating the microplan estimation for the villages chosen. Entering any comment or reason is non-mandatory.

This is the status logs pop-up showing the status of the village, who made the status change and when was the change recorded.

1. Once the villages are validated, you can see the list of villages in the ‘Validated’ bucket.

If you log in as a superior administrative hierarchy "Microplan estimation approver" or "National microplan estimation approver" role, you can validate if the villages validated by your subordinates are correct.

If you are not aligned with the validation done by your subordinates, you can always send back the village data for correction to the person who had validated the villages. This can be done using the button called ‘Send back for correction’.

Any action that you take in the dashboard for a village will be recorded and can be seen by anyone using the ‘Status logs’ button.

This is the view of the dashboard for checking the data and sending back the data for correction.

This pop-up will be shown to you when you click on the "Send back for correction" button. You, as a microplan estimation approver, can enter any comment or reason for sending back the village data for correction for the villages chosen. Entering any comment or reason is non-mandatory.

1. Once all the villages under the approver’s jurisdiction are validated, then, if you are logged in as a "National microplan estimation approver", you will be able to see a button called ‘Proceed To Finalise Microplan Estimation’.

This is the button you will see as a ‘National microplan estimation approver’ once all the villages under the campaign boundary are validated.

1. If you are logged in as a "National microplan estimation approver", you will be able to see and click on the "Proceed To Finalise Microplan Estimation" to finalise the microplan estimation for all the villages under the campaign boundary.

Here, once you click on this button, you will be shown a pop-up asking you to validate the estimation before you finalise the microplan estimations.

This is the warning pop-up you will see when you try to click on the "Proceed To Finalise Facility Assignment" button.

1. Once you click on the button shown in the pop-up called "I Want To Finalise", you will see the activity completion screen showing the microplan estimation is completed successfully.

This is the screen you will see when the microplan estimation is finalised.

You can now click on the "Go back to home" button to go back to the "My Microplans" dashboard, as your assigned activity has been completed.

1. Once the microplan is finalised, you will be able to download the microplan estimations in an Excel spreadsheet.

This is the view where you will see the microplans that are finalised and you will be able to download the microplan estimations using the "Download Estimation" button.

System SOP(s) for Programme Teams

1. Data upload are to be followed and adhered to

a. Input formats supported:

- Pre-defined Excel template

- Geosjon (pre-defined schema)

- Shapefile

b. Configure data starting from admin 0

c. A naming convention needs to be followed for data upload (training to be provided)

d. 1 file per boundary to be uploaded

- 1 file for all admin 0

- 1 file for admin 1

Input File Validation

GeoJSON

• The GeoJSON file should meet the specification

• The top-level element should be of type “FeatureCollection”

• All the Features within the FeatureCollection should have geometries of the same type (i.e. All should be points, or all should be MultiPolygons, and so on).

• The coordinates should be in the valid range of Latitude & Longitude. (Valid range for Latitude is -90 to +90; Valid range of Longitude is -180 to +180)

• If the third coordinate (i.e. the height value) is present, then it will be ignored.

• All the features should have properties with the same set of keys.

• In the Properties object, the values for fields that represent a Numeric Value, should not be quoted with double quotes, (i.e. population of 10,000 should be represented as “population” : 10000 and not “population” : “10,0000”

Shapefile

• A shapefile consists of multiple files with the same name and different extensions. Mandatory ones are .shp, .shx & .dbf. You could also have .prj, .sbx & .sbn.

• The shapefile should be in the WGS 84 lat-long coordinate system. (i.e. EPSG:4326). If the .prj file is missing, then the data is assumed to be in the WGS 84 lat-long coordinate system.

• Data in any other coordinate system, even if indicated so in the .prj file will not be considered valid.

• The coordinates should be in the valid range of Latitude & Longitude. (Valid range for Latitude is -90 to +90; Valid range for Longitude is -180 to +180).

• Field Names are limited to 10 Characters as per the Shapefile Specification.

• The Various fields in the attribute table should have the appropriate data types. (i.e. Numeric Values should be in fields of the type Short Integer, Long Integer, Float, or Double)

• The User should zip up all the files in Zip format, and upload them into the system. At a minimum, the system needs .shp, .shx & .dbf files

• The total size of all files together should not exceed 2GB

Excel

• The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds ( Value should be 12.3455 & not 12° 20' 43.7994")

• Any leading & trailing whitespace characters (Spaces, Tabs, Carriage Return, new line etc) will be stripped out from all fields

This section provides a detailed and comprehensive view of the micro planning system's internal mechanics. The LLD focuses on providing API specifications, sequence diagrams and database schema. This section serves as a blueprint for developers and engineers to implement the system accurately.

The Microplanning system is designed to allow users to generate, validate, and approve micro plans across various geographic boundaries. The system's architecture includes services for handling population data, plan estimates, employee assignments and facility linkages. The system is scalable, secure, and optimised for local and national-level campaigns.

High Level Design

Low Level Design

Configuration Details

For MDMS-V2 changes, refer to the files below for MDMS schema and data that needs to be added for Microplanning:

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "id"
            ],
            "x-unique": [
                "id"
            ],
            "properties": {
                "id": {
                    "type": "number"
                },
                "data": {
                    "type": "array",
                    "items": {
                        "type": "string"
                    }
                },
                "isActive": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "id"
            ],
            "x-unique": [
                "id"
            ],
            "properties": {
                "id": {
                    "type": "number"
                },
                "data": {
                    "type": "string"
                },
                "isActive": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "resourceDistributionStrategyCode",
                "resourceDistributionStrategyName"
            ],
            "x-unique": [
                "resourceDistributionStrategyCode"
            ],
            "properties": {
                "resourceDistributionStrategyCode": {
                    "type": "string"
                },
                "resourceDistributionStrategyName": {
                    "type": "string"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "role",
                "roleCode",
                "orderNumber"
            ],
            "x-unique": [
                "roleCode"
            ],
            "properties": {
                "role": {
                    "type": "string"
                },
                "roleCode": {
                    "type": "string"
                },
                "orderNumber": {
                    "type": "number"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "x-unique": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "properties": {
                "campaignType": {
                    "type": "string"
                },
                "DistributionProcess": {
                    "type": "string"
                },
                "RegistrationProcess": {
                    "type": "string"
                },
                "assumptionCategories": {
                    "type": "array",
                    "items": {
                        "type": "object",
                        "required": [
                            "category",
                            "order",
                            "assumptions"
                        ],
                        "properties": {
                            "order": {
                                "type": "number"
                            },
                            "category": {
                                "type": "string"
                            },
                            "assumptions": {
                                "type": "array",
                                "items": {
                                    "type": "string"
                                }
                            }
                        }
                    }
                },
                "resourceDistributionStrategyCode": {
                    "type": "string"
                },
                "isRegistrationAndDistributionHappeningTogetherOrSeparately": {
                    "type": "string"
                }
            },
            "x-ref-schema": [
                {
                    "fieldPath": "resourceDistributionStrategyCode",
                    "schemaCode": "hcm-microplanning.ResourceDistributionStrategy"
                },
                {
                    "fieldPath": "resourceDistributionStrategyCode",
                    "schemaCode": "hcm-microplanning.ResourceDistributionStrategy"
                }
            ]
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "x-unique": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "properties": {
                "campaignType": {
                    "type": "string"
                },
                "outputCategories": {
                    "type": "array",
                    "items": {
                        "type": "object",
                        "required": [
                            "category",
                            "order",
                            "outputs"
                        ],
                        "properties": {
                            "order": {
                                "type": "number"
                            },
                            "outputs": {
                                "type": "array",
                                "items": {
                                    "type": "string"
                                }
                            },
                            "category": {
                                "type": "string"
                            }
                        }
                    }
                },
                "DistributionProcess": {
                    "type": "string"
                },
                "RegistrationProcess": {
                    "type": "string"
                },
                "resourceDistributionStrategyCode": {
                    "type": "string"
                },
                "isRegistrationAndDistributionHappeningTogetherOrSeparately": {
                    "type": "string"
                }
            },
            "x-ref-schema": [
                {
                    "fieldPath": "resourceDistributionStrategyCode",
                    "schemaCode": "hcm-microplanning.ResourceDistributionStrategy"
                }
            ]
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "x-unique": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "properties": {
                "campaignType": {
                    "type": "string"
                },
                "inputCategories": {
                    "type": "array",
                    "items": {
                        "type": "object",
                        "required": [
                            "category",
                            "order",
                            "inputs"
                        ],
                        "properties": {
                            "order": {
                                "type": "number"
                            },
                            "inputs": {
                                "type": "array",
                                "items": {
                                    "type": "string"
                                }
                            },
                            "category": {
                                "type": "string"
                            }
                        }
                    }
                },
                "DistributionProcess": {
                    "type": "string"
                },
                "RegistrationProcess": {
                    "type": "string"
                },
                "resourceDistributionStrategyCode": {
                    "type": "string"
                },
                "isRegistrationAndDistributionHappeningTogetherOrSeparately": {
                    "type": "string"
                }
            },
            "x-ref-schema": [
                {
                    "fieldPath": "resourceDistributionStrategyCode",
                    "schemaCode": "hcm-microplanning.ResourceDistributionStrategy"
                }
            ]
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "x-unique": [
                "campaignType",
                "resourceDistributionStrategyCode",
                "isRegistrationAndDistributionHappeningTogetherOrSeparately",
                "RegistrationProcess",
                "DistributionProcess"
            ],
            "properties": {
                "campaignType": {
                    "type": "string"
                },
                "DistributionProcess": {
                    "type": "string"
                },
                "RegistrationProcess": {
                    "type": "string"
                },
                "ruleConfigurationCategories": {
                    "type": "array",
                    "items": {
                        "type": "object",
                        "required": [
                            "category",
                            "order",
                            "ruleConfigurations"
                        ],
                        "properties": {
                            "order": {
                                "type": "number"
                            },
                            "category": {
                                "type": "string"
                            },
                            "ruleConfigurations": {
                                "type": "array",
                                "items": {
                                    "type": "object",
                                    "required": [
                                        "output",
                                        "input",
                                        "operatorName",
                                        "assumptionValue"
                                    ],
                                    "properties": {
                                        "input": {
                                            "type": "string"
                                        },
                                        "output": {
                                            "type": "string"
                                        },
                                        "operatorName": {
                                            "type": "string"
                                        },
                                        "assumptionValue": {
                                            "type": "string"
                                        }
                                    }
                                }
                            }
                        }
                    }
                },
                "resourceDistributionStrategyCode": {
                    "type": "string"
                },
                "isRegistrationAndDistributionHappeningTogetherOrSeparately": {
                    "type": "string"
                }
            },
            "x-ref-schema": [
                {
                    "fieldPath": "resourceDistributionStrategyCode",
                    "schemaCode": "hcm-microplanning.ResourceDistributionStrategy"
                }
            ]
        }

{
                "type": "object",
                "title": "Generated schema for Root",
                "$schema": "http://json-schema.org/draft-07/schema#",
                "required": [
                    "operatorName",
                    "operatorCode"
                ],
                "x-unique": [
                    "operatorName"
                ],
                "properties": {
                    "operatorCode": {
                        "type": "string"
                    },
                    "operatorName": {
                        "type": "string"
                    }
                }
            }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "registrationAndDistributionHappeningTogetherOrSeparatelyName",
                "registrationAndDistributionHappeningTogetherOrSeparatelyCode"
            ],
            "x-unique": [
                "registrationAndDistributionHappeningTogetherOrSeparatelyCode"
            ],
            "properties": {
                "registrationAndDistributionHappeningTogetherOrSeparatelyCode": {
                    "type": "string"
                },
                "registrationAndDistributionHappeningTogetherOrSeparatelyName": {
                    "type": "string"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "code"
            ],
            "x-unique": [
                "code"
            ],
            "properties": {
                "code": {
                    "type": "string"
                },
                "name": {
                    "type": "string"
                },
                "active": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "code"
            ],
            "x-unique": [
                "code"
            ],
            "properties": {
                "code": {
                    "type": "string"
                },
                "name": {
                    "type": "string"
                },
                "active": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "id"
            ],
            "x-unique": [
                "id"
            ],
            "properties": {
                "id": {
                    "type": "number"
                },
                "values": {
                    "type": "array",
                    "items": {
                        "type": "string"
                    }
                },
                "question": {
                    "type": "string"
                },
                "required": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "code"
            ],
            "x-unique": [
                "code"
            ],
            "properties": {
                "code": {
                    "type": "string"
                },
                "name": {
                    "type": "string"
                },
                "active": {
                    "type": "boolean"
                }
            }
        }

 {
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "code"
            ],
            "x-unique": [
                "code"
            ],
            "properties": {
                "code": {
                    "type": "string"
                },
                "name": {
                    "type": "string"
                },
                "active": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "type",
                "manufacturer",
                "model",
                "capacity"
            ],
            "x-unique": [
                "manufacturer",
                "model",
                "capacity"
            ],
            "properties": {
                "type": {
                    "type": "string"
                },
                "model": {
                    "type": "string"
                },
                "uomCode": {
                    "type": "string"
                },
                "capacity": {
                    "type": "number"
                },
                "manufacturer": {
                    "type": "string"
                }
            },
            "x-ref-schema": [
                {
                    "fieldPath": "type",
                    "schemaCode": "hcm-microplanning.VehicleType"
                },
                {
                    "fieldPath": "uomCode",
                    "schemaCode": "hcm-microplanning.Uom"
                }
            ]
        }

{
                "type": "object",
                "title": "Schema for vehicle type",
                "$schema": "http://json-schema.org/draft-07/schema#",
                "required": [
                    "type"
                ],
                "x-unique": [
                    "type"
                ],
                "properties": {
                    "type": {
                        "type": "string"
                    }
                }
            }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "contextPathConfig",
                "id"
            ],
            "x-unique": [
                "contextPathConfig",
                "id"
            ],
            "properties": {
                "id": {
                    "type": "string"
                },
                "contextPathConfig": {
                    "type": "string"
                }
            }
        }

{
                "type": "object",
                "title": "DssKpiConfigs",
                "$schema": "http://json-schema.org/draft-07/schema#",
                "required": [
                    "module",
                    "kpiConfig"
                ],
                "x-unique": [
                    "module"
                ],
                "properties": {
                    "module": {
                        "type": "string"
                    },
                    "kpiConfig": {
                        "type": "array",
                        "items": {
                            "type": "object",
                            "required": [
                                "campaignType",
                                "charts"
                            ],
                            "properties": {
                                "charts": {
                                    "type": "array",
                                    "items": {
                                        "type": "object",
                                        "required": [
                                            "visualizationType",
                                            "localeKey",
                                            "visualizationCode",
                                            "order",
                                            "moduleLevel"
                                        ],
                                        "properties": {
                                            "order": {
                                                "type": "number"
                                            },
                                            "localeKey": {
                                                "type": "string"
                                            },
                                            "moduleLevel": {
                                                "type": "string"
                                            },
                                            "concateChars": {
                                                "type": "string"
                                            },
                                            "concatenateKey": {
                                                "type": "string"
                                            },
                                            "visualizationCode": {
                                                "type": "string"
                                            },
                                            "visualizationType": {
                                                "type": "string"
                                            }
                                        }
                                    }
                                },
                                "campaignType": {
                                    "type": "string"
                                }
                            }
                        }
                    }
                }
            }

{
                "type": "object",
                "title": "Generated schema for Root",
                "$schema": "http://json-schema.org/draft-07/schema#",
                "required": [
                    "hierarchy",
                    "lowestHierarchy"
                ],
                "x-unique": [
                    "hierarchy"
                ],
                "properties": {
                    "hierarchy": {
                        "type": "string"
                    },
                    "lowestHierarchy": {
                        "type": "string"
                    }
                }
            }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "uomCode",
                "name"
            ],
            "x-unique": [
                "uomCode"
            ],
            "properties": {
                "name": {
                    "type": "string"
                },
                "uomCode": {
                    "type": "string"
                }
            }
        }

{
            "$schema": "http://json-schema.org/draft-07/schema#",
            "title": "Generated schema for Root",
            "type": "object",
            "properties": {
                "id": {
                    "type": "string"
                },
                "code": {
                    "type": "string"
                },
                "iconName": {
                    "type": "string"
                },
                "required": {
                    "type": "boolean"
                },
                "UploadFileTypes": {
                    "type": "array",
                    "items": {
                        "type": "object",
                        "properties": {
                            "id": {
                                "type": "string"
                            },
                            "code": {
                                "type": "string"
                            },
                            "fileExtension": {
                                "type": "array",
                                "items": {
                                    "type": "string"
                                }
                            },
                            "iconName": {
                                "type": "string"
                            },
                            "namingConvention": {
                                "type": "string"
                            }
                        },
                        "required": [
                            "id",
                            "code",
                            "fileExtension",
                            "iconName",
                            "namingConvention"
                        ]
                    }
                }
            },
            "x-unique": [
                "code"
            ],
            "required": [
                "id",
                "code",
                "iconName",
                "required",
                "UploadFileTypes"
            ]
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "code",
                "name",
                "active"
            ],
            "x-unique": [
                "code"
            ],
            "properties": {
                "code": {
                    "type": "string"
                },
                "name": {
                    "type": "string"
                },
                "active": {
                    "type": "boolean"
                }
            }
        }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "type",
                "section",
                "doHierarchyCheckInUploadedData",
                "showResourcesInMappingSection",
                "template",
                "schema"
            ],
            "x-unique": [
                "type",
                "campaignType",
                "section"
            ],
            "properties": {
                "type": {
                    "type": "string"
                },
                "schema": {
                    "type": "object",
                    "required": [
                        "Properties"
                    ],
                    "properties": {
                        "Properties": {
                            "type": "object",
                            "required": [
                                "boundaryCode"
                            ],
                            "properties": {
                                "lat": {
                                    "$ref": "#/definitions/latLongProperties"
                                },
                                "long": {
                                    "$ref": "#/definitions/latLongProperties"
                                },
                                "capacity": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "boundaryCode": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "facilityCode": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "facilityName": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "facilityType": {
                                    "$ref": "#/definitions/facilityProperties"
                                },
                                "facilityStatus": {
                                    "$ref": "#/definitions/facilityProperties"
                                },
                                "targetPopulation": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "totalTargetPopulation": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "targetPopulationAge3To11": {
                                    "$ref": "#/definitions/commonProperties"
                                },
                                "targetpopulationAge12To59": {
                                    "$ref": "#/definitions/commonProperties"
                                }
                            }
                        }
                    }
                },
                "section": {
                    "type": "string"
                },
                "template": {
                    "type": "object",
                    "required": [
                        "showTemplateDownload",
                        "includeFacilityData",
                        "hierarchyLevelWiseSheets",
                        "propertiesToHide"
                    ],
                    "properties": {
                        "propertiesToHide": {
                            "type": "array",
                            "items": {
                                "type": "string"
                            }
                        },
                        "includeFacilityData": {
                            "type": "boolean"
                        },
                        "showTemplateDownload": {
                            "type": "boolean"
                        },
                        "facilitySchemaApiMapping": {
                            "type": "object",
                            "properties": {
                                "capacity": {
                                    "type": "string"
                                },
                                "facilityCode": {
                                    "type": "string"
                                },
                                "facilityName": {
                                    "type": "string"
                                },
                                "facilityType": {
                                    "type": "string"
                                },
                                "facilityStatus": {
                                    "type": "string"
                                }
                            }
                        },
                        "hierarchyLevelWiseSheets": {
                            "type": "boolean"
                        }
                    }
                },
                "campaignType": {
                    "type": "string"
                },
                "showResourcesInMappingSection": {
                    "type": "boolean"
                },
                "doHierarchyCheckInUploadedData": {
                    "type": "boolean"
                }
            },
            "definitions": {
                "commonProperties": {
                    "type": "object",
                    "required": [
                        "type",
                        "isRequired",
                        "isLocationDataColumns",
                        "isRuleConfigureInputs",
                        "isFilterPropertyOfMapSection",
                        "isVisualizationPropertyOfMapSection",
                        "toShowInMicroplanPreview"
                    ],
                    "properties": {
                        "type": {
                            "type": "string"
                        },
                        "isRequired": {
                            "type": "boolean"
                        },
                        "isLocationDataColumns": {
                            "type": "boolean"
                        },
                        "isRuleConfigureInputs": {
                            "type": "boolean"
                        },
                        "toShowInMicroplanPreview": {
                            "type": "boolean"
                        },
                        "isFilterPropertyOfMapSection": {
                            "type": "boolean"
                        },
                        "isVisualizationPropertyOfMapSection": {
                            "type": "boolean"
                        }
                    }
                },
                "latLongProperties": {
                    "type": "object",
                    "required": [
                        "type",
                        "minimum",
                        "maximum",
                        "isRequired",
                        "isLocationDataColumns",
                        "isRuleConfigureInputs",
                        "isFilterPropertyOfMapSection",
                        "isVisualizationPropertyOfMapSection",
                        "toShowInMicroplanPreview"
                    ],
                    "properties": {
                        "type": {
                            "type": "string"
                        },
                        "maximum": {
                            "type": "number"
                        },
                        "minimum": {
                            "type": "number"
                        },
                        "isRequired": {
                            "type": "boolean"
                        },
                        "isLocationDataColumns": {
                            "type": "boolean"
                        },
                        "isRuleConfigureInputs": {
                            "type": "boolean"
                        },
                        "toShowInMicroplanPreview": {
                            "type": "boolean"
                        },
                        "isFilterPropertyOfMapSection": {
                            "type": "boolean"
                        },
                        "isVisualizationPropertyOfMapSection": {
                            "type": "boolean"
                        }
                    }
                },
                "facilityProperties": {
                    "type": "object",
                    "required": [
                        "type",
                        "isRequired",
                        "enum",
                        "isLocationDataColumns",
                        "isRuleConfigureInputs",
                        "isFilterPropertyOfMapSection",
                        "isVisualizationPropertyOfMapSection",
                        "toShowInMicroplanPreview"
                    ],
                    "properties": {
                        "enum": {
                            "type": "array",
                            "items": {
                                "type": "string"
                            }
                        },
                        "type": {
                            "type": "string"
                        },
                        "isRequired": {
                            "type": "boolean"
                        },
                        "isLocationDataColumns": {
                            "type": "boolean"
                        },
                        "isRuleConfigureInputs": {
                            "type": "boolean"
                        },
                        "toShowInMicroplanPreview": {
                            "type": "boolean"
                        },
                        "isFilterPropertyOfMapSection": {
                            "type": "boolean"
                        },
                        "isVisualizationPropertyOfMapSection": {
                            "type": "boolean"
                        }
                    }
                }
            }
        }

{
                "type": "object",
                "title": "Generated schema for Root",
                "$schema": "http://json-schema.org/draft-07/schema#",
                "required": [
                    "name",
                    "value"
                ],
                "x-unique": [
                    "name"
                ],
                "properties": {
                    "name": {
                        "type": "string"
                    },
                    "value": {
                        "type": "string"
                    }
                }
            }

{
                "type": "object",
                "title": "Hierarchy Configuration Schema",
                "$schema": "http://json-schema.org/draft-09/schema#",
                "required": [
                    "hierarchy",
                    "type"
                ],
                "x-unique": [
                    "type"
                ],
                "properties": {
                    "type": {
                        "enum": [
                            "default",
                            "microplan",
                            "campaign",
                            "console"
                        ],
                        "type": "string",
                        "description": "Specifies the type of hierarchy configuration."
                    },
                    "group": {
                        "type": "array",
                        "items": {
                            "type": "string"
                        },
                        "description": "An array of disease groups from the project type master."
                    },
                    "hierarchy": {
                        "type": "string",
                        "unique": true,
                        "description": "The type of hierarchy, must be a unique string."
                    },
                    "department": {
                        "type": "array",
                        "items": {
                            "type": "string"
                        },
                        "description": "An array of departments from the department master."
                    },
                    "lowestHierarchy": {
                        "type": "string",
                        "description": "The lowest administrative level in the hierarchy."
                    },
                    "highestHierarchy": {
                        "type": "string",
                        "description": "The highest administrative level in the hierarchy."
                    },
                    "splitBoundariesOn": {
                        "type": "string",
                        "description": "The level on which boundaries are split."
                    }
                }
            }

{
            "type": "object",
            "title": "Generated schema for Root",
            "$schema": "http://json-schema.org/draft-07/schema#",
            "required": [
                "title",
                "type",
                "data"
            ],
            "x-unique": [
                "title",
                "type"
            ],
            "properties": {
                "data": {
                    "type": "array",
                    "items": {
                        "type": "array",
                        "items": {
                            "type": "object",
                            "required": [
                                "column",
                                "value"
                            ],
                            "properties": {
                                "value": {
                                    "type": "string"
                                },
                                "column": {
                                    "type": "string"
                                }
                            }
                        }
                    }
                },
                "type": {
                    "type": "string"
                },
                "title": {
                    "type": "string"
                }
            }
        }

For the addition of Indexer Mappings, refer to the file below and add the mappings for Microplanning:

PUT census-index-v1
{
  "mappings": {
    "properties": {
      "Data": {
        "properties": {
          "@timestamp": {
            "type": "date"
          },
          "additionalDetails": {
            "type": "object"
          },
          "additionalFields": {
            "type": "nested",
            "properties": {
              "editable": {
                "type": "boolean"
              },
              "id": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "key": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "order": {
                "type": "long"
              },
              "showOnUi": {
                "type": "boolean"
              },
              "value": {
                "type": "long"
              }
            }
          },
          "assignee": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "auditDetails": {
            "properties": {
              "createdBy": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "createdTime": {
                "type": "long"
              },
              "lastModifiedBy": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "lastModifiedTime": {
                "type": "long"
              }
            }
          },
          "boundaryAncestralPath": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "boundaryCode": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "effectiveFrom": {
            "type": "long"
          },
          "effectiveTo": {
            "type": "long"
          },
          "facilityAssigned": {
            "type": "boolean"
          },
          "hierarchyType": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "id": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "jurisdictionMapping": {
            "type": "object"
          },
          "populationByDemographics": {
            "type": "nested",
            "properties": {
              "demographicVariable": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "id": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "populationDistribution": {
                "properties": {
                  "0-14": {
                    "type": "long"
                  },
                  "15-24": {
                    "type": "long"
                  },
                  "25-64": {
                    "type": "long"
                  },
                  "65+": {
                    "type": "long"
                  }
                }
              }
            }
          },
          "source": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "status": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "tenantId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "totalPopulation": {
            "type": "long"
          },
          "type": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "workflow": {
            "properties": {
              "action": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "assignes": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "comments": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

PUT plan-facility-index-v1
{
  "mappings": {
    "properties": {
      "Data": {
        "properties": {
          "@timestamp": {
            "type": "date"
          },
          "active": {
            "type": "boolean"
          },
          "additionalDetails": {
            "type" : "object"
          },
          "auditDetails": {
            "properties": {
              "createdBy": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "createdTime": {
                "type": "long"
              },
              "lastModifiedBy": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "lastModifiedTime": {
                "type": "long"
              }
            }
          },
          "facilityId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "facilityName": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "planConfigurationId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "planConfigurationName": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "residingBoundary": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "serviceBoundaries": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "tenantId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          }
        }
      }
    }
  }
}

PUT plan-index-v1
{
  "mappings": {
    "properties": {
      "Data": {
        "properties": {
          "@timestamp": {
            "type": "date"
          },
          "additionalDetails": {
            "type": "object"
          },
          "assignee": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "auditDetails": {
            "properties": {
              "createdBy": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "createdTime": {
                "type": "long"
              },
              "lastModifiedBy": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "lastModifiedTime": {
                "type": "long"
              }
            }
          },
          "boundaryAncestralPath": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "campaignId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "id": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "jurisdictionMapping": {
            "type" : "object"
          },
          "locality": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "planConfigurationId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "resources": {
            "type": "nested",
            "properties": {
              "estimatedNumber": {
                "type": "float"
              },
              "id": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "resourceType": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              }
            }
          },
          "status": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "tenantId": {
            "type": "text",
            "fields": {
              "keyword": {
                "type": "keyword",
                "ignore_above": 256
              }
            }
          },
          "workflow": {
            "properties": {
              "action": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "assignes": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              },
              "comments": {
                "type": "text",
                "fields": {
                  "keyword": {
                    "type": "keyword",
                    "ignore_above": 256
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}