PBMS (Odoo)

Static definitions / configurations

Benefit Codes

Configure a list of benefit codes (products) that are disbursed by the various programs. Benefit Codes are broadly classified into the following types

• CASH_DIGITAL — Cash benefits, distributed digitally using direct credits into beneficiary bank accounts or mobile wallets. It is mandatory for Beneficiary financial addresses to be maintained in SPAR (ID-Account Mapper) in case of CASH_DIGITAL. The Measurement unit for CASH_DIGITAL will be restricted to ISO Currency codes.

• CASH_PHYSICAL - Cash benefits, distributed physically. The platform assumes that there will be an agency (service provider) involved in this chain. The Agency will have agents on the ground (field agents) who will physically distribute cash. The department will transfer the required funds to the Agencies by directly transfers into the Agencies' bank accounts. The Measurement unit for CASH_DIGITAL will be restricted to ISO Currency codes.

• COMMODITY - All physical goods such as staples, books, grains and fuel will come under this category.

• SERVICE - Applicable when the department provides services such as health screenings to the public.

• COMBINATION - Applicable when a benefit includes both a commodity plus a service bundled. E.g. a vaccine will involve a physical vaccine vial plus the service of administering the vaccine.

Screens

Tables involved

1. g2p_benefit_codes

Program Definition

You configure the benefit programs which govern the benefit distribution. The key attributes that you define in a benefit program are as follows

1. Target Registry - This attribute indicates the registry from where the beneficiaries' list will be drawn. Mapping a target registry to a program will allow you to define eligibility, priority and entitlement rules using the attributes of the registry. For this, you have to ensure that the target registry is made available as an "ABSTRACT CLASS" in your PBMS Odoo instance. Detailed instructions on how to make this Abstract class available to the PBMS Odoo, can be found in here.

2. Enrolment Frequency - This specifies how frequently will you refresh the Beneficiary List under the program. New enrolments are done by creating a new enrolment cycle. New enrolments typically involve field agents verifying existing beneficiaries, striking out beneficiaries who no longer qualify and adding new beneficiaries. You can also have changes administered through self service portals or integration with Civil Registry APIs or a combination of all of these methods.

3. Disbursement Frequency - This specifies how frequently will you make disbursements under this program. Typically you will Disburse far more frequently than you Enrol. For e.g. you might have an annual enrolment frequency with a monthly disbursement frequency.

4. Benefit Codes - You need to associate a list of Benefit codes with a Program. A program can disburse one or more Benefit codes (products / services) to its beneficiaries. You also need to create entitlement rules for every benefit code associated with the Program.

5. Eligibility Rules - You need to define a set of rules that make a registrant eligible to qualify as a beneficiary under this program. You can use the Target Registry - attributes to define these eligibility rules.

6. Entitlement Rules - You need to define a set of rules that will compute an entitlement (of a benefit code) for a given beneficiary. You need distinct entitlement rules for every benefit code associated with the Program.

Screens

Tables involved

1. g2p_program_definition (primary table that stores the program definition)

2. g2p_benefit_codes_g2p_program_definition_rel (benefit codes for a program)

3. g2p_eligibility_rule_definition (eligibility rules for a program)

4. g2p_entitlement_rule_definition (entitlement rules for a program)

Geographic Administrative Zones

When a benefit program involves physical distribution of goods and services, geography assumes significance. To enable the necessary configurations, the PBMS platform provides you two types of Geographic Administrative Zones

Geographic Administrative Zone - Large

This is a large zone (examples include - States or Districts). Depending on your situation, you can configure any of your relevant Geographic Administrative Zone as a GAZ-Large.

Geographic Administrative Zone - Small

This is a small zone within a Large Zone. A typical Large Zone will consider a number of small zones. Examples of small zones will include - Post Codes, Localities and Streets.

A beneficiary address should necessarily consist of a Large Zone and a Small Zone.

Screens

Tables involved

Warehouses

When a program involves physical distribution of goods and services, the program administering department needs to liaise with a warehouse, where the goods are stored. Depending on the geographical spread of the beneficiaries, the department will likely appoint agencies who then procure the goods from these warehouses and do the actual distribution.

You need to maintain Warehouses and also associate these warehouses to the Geography (large) and the Benefit Codes. Because you might use specific warehouses for certain geographical zones (driven by proximity and ease of transport). Similarly, they might be specific warehouses for specific goods.

Based on these constraints, you have to map Warehouses to Geographic Administrative Zones (Large) and to one or more Benefit. Codes.

During disbursement, the PBMS platform will automatically allocate Warehouses depending on these configurations.

Screens

Tables involved

Agencies

1. Geographic Administrative Zones - Large

2. Geographic Administrative Zones - Small

3. Agenciesive

4. Warehouses