Sr. No
Sequence number for the list.
Boundary hierarchy type
The meaningful name to define one group of boundaries tasked to perform one function.
Mandatory
MDMS
String
Yes
Code
Code is used to identify a certain classification of the type of boundary hierarchy.
Mandatory
MDMS
String
Yes
Description
A brief description of the boundary hierarchy.
Mandatory
MDMS
String
Yes
Here are the articles in this section:
Product type
Type of product being used. Example: Drug, spray, vaccine, bed net, IEC material.
Yes
String
2
64
Product name
Name of the product being used. Example: Ivermectic, Paracetamol, etc.
Yes
String
2
64
Product manufacturer
Name of the manufacturer. Example: Merck, Johnson & Johnson, etc.
Yes
String
Product variant
Capture the variant of the products. Products can vary based on shape, size, colour or other characteristics. Example: Para 200 mg- pack of 5 tables, Para 250 mg- pack of 10 tables.
Yes
String
2
64
SKU
Stock keeping unit code for the product. Example: Para 200 mg and Para 250 mg.
Yes
String
2
64
Base unit variant
Capture details if variant is the base unit used for record keeping of the product's inventory. Useful to filter variants applicable for tasks within a project. Example: The base unit for bed net is an individual bed net or a bale of 50 nets.
Yes
String
Product Type
Product Name
Product Manufacturer
Product Variant
SKU
Base Unit Variant
Bed nets
Rectangular polyester mosquito net/bed net
Tana Netting FZ-LLC
Rectangular polyester mosquito net/bed net, 75-100 denier, treated with WHOPES recommended insecticide, colour: white/blue/green, dimensions 180x160x150cm (length x width x height) +/-5%
S0000981
Yes
Password
Password to log in to the system.
Yes
Password is encrypted and not retrievable from the system. Password format to be decided.
Name
The name of the user who wants to access the system.
Yes
Mobile number
Mobile number of the user.
No
Gender
Gender of the user being registered.
Yes
Date of birth
Date of birth of the user being registered.
Yes
Email ID of the user being registered.
Yes
Email used for password recovery using OTP-based authentication.
Correspondence address
Address of the user being registered.
No
Role
Role assigned to the user to enable him/her to carry out the tasks, as well as access the required data and services.
Yes
Supports multiple role assignments.
Employment type
The employment type indicates the type of contract which he/she holds within the organisation. This indicates whether he/she is a permanent employee, or a contract employee for a short period. Either one in the employment type - “Permanent”, “Temporary”, “DailyWages” and “Contract” - should be selected
Yes
Date of appointment
Date the user is hired.
No
Facility name
Identifier of the facility.
Yes
Is permanent
Is the facility permanent or temporary.
Yes
Facility type
What is the facility used for? Example: Warehouse, community, health centre.
Yes
Address
Yes
Administrative area
Administrative boundary of the facility.
Yes
Address line 1
No
Address line 2
No
Landmark
No
City
No
Pincode
No
Building name
No
Street
No
Storage
Storage capacity of the facility.
No
Facility Name
Is permanent
Facility type
Administrative area
Address line 1
Address line 2
Landmark
City
Pincode
Building Name
Street
Storage
Solimbo District Warehouse
Yes
Warehouse
Solimbo
Sr. No.
Boundary Code*
This is a code for the sub-classification of a particular boundary. It should be unique across all boundaries defined.
Mandatory
MDMS
String
Yes
Boundary Name* (In English)
The name of the boundary that is being defined in English language.
Mandatory
MDMS
String
Yes
Boundary Name* (In Local Language)
The name of the boundary that is being defined in the local language of the state, such as Portuguese, Hindi, etc.
Mandatory
MDMS
String
Yes
Parent Boundary Code*
This is the boundary code of the parent which identifies to which parent the child belongs to.
Mandatory
MDMS
String
Yes
Boundary Type*
The name of the boundary type, that is, ward, zone, etc.
Mandatory
MDMS
String
Yes
Hierarchy Type Code*
The code of the boundary hierarchies for which this particular boundary is defined.
Mandatory
MDMS
String
Yes
Campaign Start Date
Date when the campaign starts in the respective boundary in dd/mm/yyyy format.
Mandatory
MDMS
Date
Yes
Campaign End Date
Date when the campaign is supposed to end in the respective boundary in dd/mm/yyyy format.
Mandatory
MDMS
Date
Yes
Total Households
Total households present in the boundary (as per the micro-plan).
Mandatory
MDMS
Numeric
Yes
Targeted Households
Total households targeted for the respective boundary (as per the micro-plan).
Mandatory
MDMS
Numeric
For bed net, the total and the targeted is likely to be the same
Yes
Total Individuals
Total individuals present in the boundary (as per the micro-plan).
Mandatory
MDMS
Numeric
Yes
Targeted Individuals
Total individuals targeted in the boundary (as per the micro-plan).
Mandatory
MDMS
Numeric
For bed net, the total and the targeted is likely to be the same
Yes
Bed nets estimated to be delivered
Total bed nets estimated to be delivered in the boundary (as per the micro-plan).
Mandatory
MDMS
Numeric
Yes