PBMS pages updated.

pjoshi751 · pjoshi751 · commit 8f04e7a151f5 · 2024-01-03T06:26:19.000+05:30
diff --git a/SUMMARY.md b/SUMMARY.md
@@ -7,7 +7,14 @@
 * [Architecture](platform/architecture.md)
 * [Modules](platform/modules/README.md)
   * [Program & Beneficiary Management System](platform/modules/program-and-beneficiary-management-system/README.md)
+    * [Eligibility](platform/modules/program-and-beneficiary-management-system/eligibility.md)
+    * [Proxy Means Test](platform/modules/program-and-beneficiary-management-system/proxy-means-test.md)
+    * [Deduplication](platform/modules/program-and-beneficiary-management-system/deduplication.md)
+    * [Enrolment](platform/modules/program-and-beneficiary-management-system/enrolment.md)
+    * [Entitlement](platform/modules/program-and-beneficiary-management-system/entitlement.md)
+    * [Disbursement](platform/modules/program-and-beneficiary-management-system/disbursement-cycles.md)
     * [Self Service Portal](platform/modules/program-and-beneficiary-management-system/self-service-portal.md)
+    * [Notifications](platform/modules/program-and-beneficiary-management-system/notifications.md)
   * [Social Registry](platform/modules/social-registry.md)
   * [Registration Tool Kit](platform/modules/registration-tool-kit/README.md)
     * [ODK Collection App](platform/modules/registration-tool-kit/odk-collection-app.md)
diff --git a/platform/modules/program-and-beneficiary-management-system/deduplication.md b/platform/modules/program-and-beneficiary-management-system/deduplication.md
@@ -0,0 +1,61 @@
+# Deduplication
+
+## Introduction
+
+Deduplication refers to the process of removing duplicate entries in the program, thus avoiding double-dipping, and merging all the demographic fields associated with an individual or a group into a single record.
+
+Each program in the OpenG2P program should have at least one Deduplication Manager configured. A separate Deduplication Manager must be created and configured for a program.
+
+## Deduplication Manager types
+
+OpenG2P platform supports three types of Deduplication Managers:
+
+#### Default Deduplication Manager
+
+This Deduplication Manager is assigned by default to each program. Since it is mandatory to configure at least one Deduplication Manager, program administrators can use this Deduplication Manager if they are sure of unique registration entries or do not want to run the deduplication.
+
+#### ID Deduplication Manager
+
+This Deduplication Manager will deduplicate the registrants based on the ID of the registrants. The program administrators should configure the ID type that will be used for deduplication. To learn more about ID type configuration, click [here](../guides/user-guides/configure-id-types.md).
+
+#### Phone Number Deduplication Manager
+
+The registrants can be deduplicated based on their phone numbers. This Deduplication Manager is often configured along with the ID Deduplication Manager.
+
+## Deduplication Manager configuration
+
+Configuring a Deduplication Manager in a program is a two-step process.
+
+#### Create a Deduplication Manager type
+
+The program administrator must create at least one Deduplication Manager for each Deduplication Manager type required. To learn more about this step, click [here](../guides/user-guides/create-deduplication-manager-types/).
+
+#### Add the Deduplication Manager to a program
+
+The program administrator needs to add the Deduplication Manager(s) created in the first step to the program. To learn more about this step, click [here](../guides/user-guides/create-deduplication-manager.md).
+
+## Deduplicating registrants
+
+Deduplication of registrants is a one-click operation once Deduplication Managers are added to the program. The Deduplication Manager does not distinguish between original and duplicate records, and all beneficiaries with the same field value - as configured for duplicate detection - are listed as duplicates.
+
+The figure below shows two duplicate entries.&#x20;
+
+<figure><img src="../.gitbook/assets/deduplicate-beneficiaries.png" alt=""><figcaption></figcaption></figure>
+
+## Deduplicating Individuals
+
+The Deduplication Manager also supports deduplication for the scenario in which the program administrator or approving authorities approve the [entitlement ](entitlement.md)of a single individual. The demographics of the individual will be deduplicated against that of every enrolled beneficiary.&#x20;
+
+If the program supports multiple entitlements for the same individual, then this deduplication can be skipped. It is assumed that in such a case, there are other mechanisms to ensure that double-dipping is prevented.
+
+Together, these features provide flexibility for program administrators to implement a wide variety of social protection programs.
+
+## How-To Guides
+
+[Configure ID Types](../guides/user-guides/configure-id-types.md)
+
+[Create Deduplication Manager Types](../guides/user-guides/create-deduplication-manager-types/)
+
+[Create Deduplication Manager under Program](../guides/user-guides/create-deduplication-manager.md)
+
+##
diff --git a/platform/modules/program-and-beneficiary-management-system/disbursement-cycles.md b/platform/modules/program-and-beneficiary-management-system/disbursement-cycles.md
@@ -0,0 +1,23 @@
+# Program Cycles
+
+## Introduction
+
+A program may have disbursements done in multiple cycles with different start and end dates for each cycle. Such cycles may be defined and triggered as per the schedule defined in each cycle. Each program should have at least one Cycle Manager associated with it.&#x20;
+
+<figure><img src="../.gitbook/assets/program-cycles.png" alt=""><figcaption></figcaption></figure>
+
+## Program Manager
+
+The Program Manager is a software module in the OpenG2P platform. It manages the number of cycles in a program and each request to create a cycle is executed through the Program Manager. The program administrators can easily replicate cycles by selecting the option to copy from the previous cycle. The manager also has a configuration option to create a cycle-less program. To learn the steps to configure a Program Manager, click [here](../guides/user-guides/configure-program-manager-in-program.md).
+
+## Cycle Manager
+
+While the Program Manager manages all the cycles, each cycle is managed by a Cycle Manager. Cycle Manager provides many convenient single-click actions to enable program administrators to quickly create new cycles, copy beneficiaries from the program, and prepare and approve entitlements. To learn more about these steps, click [here](../guides/user-guides/create-and-approve-disbursement-cycle.md).
+
+<figure><img src="../.gitbook/assets/program-cycle-prepare-payments.png" alt=""><figcaption></figcaption></figure>
+
+## How-To Guides
+
+[Configure Program Manager in Program](../guides/user-guides/configure-program-manager-in-program.md)
+
+[Create and Approve Program Cycle](../guides/user-guides/create-and-approve-disbursement-cycle.md)
diff --git a/platform/modules/program-and-beneficiary-management-system/eligibility.md b/platform/modules/program-and-beneficiary-management-system/eligibility.md
@@ -0,0 +1,39 @@
+# Eligibility Assessment
+
+## Introduction
+
+For a given program, there are certain criteria by which individuals are eligible for that program. Assuming that eligibility can be expressed unambiguously based on an individual's demographic data, a program administrator can apply the criteria in the registry to create a list of beneficiaries.
+
+## Eligibility Manager
+
+In OpenG2P, Eligibility Manager is a separate software module for configuring eligibility to a program. The module provides both simple filters and more sophisticated filters, such as the [Proxy Means Test](proxy-means-test.md), to define most eligibility requirements. Program administrators can also write their own custom plugins and add them to the Eligibility Manager.
+
+## Configuring eligibility criteria in a program
+
+In the OpenG2P program, configuring eligibility criteria is a two-step process. Program administrators need to first create Eligibility Manager(s) based on type. In the second step, these Eligibility Managers are added to the program.
+
+#### Creating Eligibility Manager type
+
+OpenG2P supports three types of Eligibility Managers.
+
+1. Default Eligibility Manager
+2. ID document Eligibility Manager
+3. Phone number Eligibility Manager
+
+One Eligibility Manager can be associated with only one program. To learn the steps to create an Eligibility Manager, click [here](../guides/user-guides/create-eligibility-manager-1/).
+
+#### Adding an Eligibility Manager to a program
+
+A program can have multiple Eligibility Managers. To learn the steps to add the Eligibility Managers, click [here](../guides/user-guides/create-eligibility-manager.md).
+
+## Eligibility filters
+
+The image here shows eligibility criteria with two filters: first for checking that the registrant is part of exactly one program, and second for checking that the registrant is unemployed.
+
+<figure><img src="../.gitbook/assets/eligibility-criteria-filters (1).PNG" alt=""><figcaption></figcaption></figure>
+
+## How-To Guides:
+
+[Create Eligibility Manager Types](../guides/user-guides/create-eligibility-manager-1/)
+
+[Create an Eligibility Manager Under the Program](../guides/user-guides/create-eligibility-manager-1/)
diff --git a/platform/modules/program-and-beneficiary-management-system/enrolment.md b/platform/modules/program-and-beneficiary-management-system/enrolment.md
@@ -0,0 +1,27 @@
+# Enrolment
+
+## Introduction
+
+Enrolment is the process of creating a beneficiary list of individuals or groups by querying the registry and applying eligibility criteria. OpenG2P provides convenient filters and plugins to make the entire process frictionless, convenient and time-saving.
+
+## Program enrolment
+
+Once the eligibility criterion is configured in the program, the program administrators can enrol the registrants with a single click of a button. Registrants are enrolled in the program upon meeting the eligibility criteria. Once enrolled in the program, the registrants will be designated as beneficiaries. Follow the guide[ Enrol Registrants into Program](../guides/user-guides/enrol-registrants-into-program.md) to learn the enrolment process.
+
+## Registrant status
+
+Upon enrollment, the status of all the eligible beneficiaries changes to enrolled. The status of ineligible beneficiaries changes to not eligible. Program administrators can view the status of both enrolled and non-eligible registrants.
+
+If the registrants have enrolled into the program using the Self-Service Portal, then they can track their enrolment status from the portal. Learn more about the [Self-Service Portal](../secure-registry/registration-methods/self-service-portal.md).
+
+## Eligibility criteria change
+
+OpenG2P allows the program administrators to change the eligibility criteria after enrolling the registrants. In such a case, the program administrators can re-run the eligibility check on the enrolled beneficiaries once again and the beneficiaries not meeting the new eligibility criteria will be listed as not eligible.
+
+## Demo
+
+{% embed url="https://www.youtube.com/watch?v=5NOfSTehmtU" %}
+
+## How-To Guides
+
+[Enrol Registrants into the Program](../guides/user-guides/enrol-registrants-into-program.md)
diff --git a/platform/modules/program-and-beneficiary-management-system/entitlement.md b/platform/modules/program-and-beneficiary-management-system/entitlement.md
@@ -0,0 +1,66 @@
+# Entitlement
+
+## Introduction
+
+Entitlement is the quantity of benefit that a beneficiary is entitled to receive. This is the money that a beneficiary will receive via either direct bank transfer, mobile wallet, cash at the counter, vouchers or other disbursement mechanisms. Entitlement is defined for each [cycle](disbursement-cycles.md).
+
+## Entitlement Manager
+
+Entitlement Manager is a software module provided by the OpenG2P platform. The module provides a human-centric design for configuring the entitlement and approval process. Configuring an Entitlement Manager in a program is a three-step process:
+
+#### Configure the Entitlement Manager role
+
+Each Entitlement Manager has one or more approving authority roles. The approving authority role is played by a group of users who can approve the entitlements. Hence the approving authority role is configured as a group in the OpenG2P platform. To learn the steps to configure an approving authority role, click [here](../guides/user-guides/create-entitlement-manager-role.md).
+
+#### Create an Entitlement Manager type
+
+OpenG2P supports two types of Entitlement Managers: Default Entitlement Managers and Voucher Entitlement Managers. The Voucher Entitlement Manager configures an [entitlement voucher](../eligibility-and-enrolment/payment-types/voucher.md) template in addition to the configurations provided by the Default Entitlement Manager. To learn the steps to create an Entitlement Manager type, click [here](broken-reference).
+
+#### Configure Entitlement Manager in a program
+
+In this step, the program administrators add the Entitlement Managers created in the second step to a program. To learn the steps to configure Entitlement Managers in a program, click [here](broken-reference).
+
+## Entitlement details
+
+OpenG2P entitlement managers allow program administrators to configure entitlement details under these broad categories.&#x20;
+
+#### Entitlement amount
+
+These configurations include entitlement amounts, transfer fees, currency, amount per person for a group, and the maximum number of individuals in a group. These configurations allow program administrators to set rules for entitlement amounts for individuals and groups.
+
+#### Approving authority
+
+The Entitlement Manager can have one or more stages of approval, and the program administrators can assign one of the approving authorities for each stage of approval. [Immediate Individual Assistance On-Demand](../workflows/on-demand-assistance.md) workflow describes an example involving multi-stage approval.
+
+#### Entitlement voucher
+
+OpenG2P provides an easy-to-use UI for creating an [entitlement voucher](../eligibility-and-enrolment/payment-types/voucher.md) template along with a QR code configuration. Once the entitlement is approved, a voucher file is generated according to the voucher template and QR code configuration. To understand the workflow for entitlement vouchers, click [here](../workflows/on-demand-assistance.md).
+
+The Entitlement Manager provides an option to auto-generate the entitlement voucher file upon entitlement approval. By default, these files are stored in the cloud. Program administrators can also configure the storage type - cloud, OpenG2P storage, or external storage - for the entitlement voucher files. To learn the steps to configure an entitlement voucher, click [here](broken-reference).
+
+## Approval process
+
+The approval process can be single-stage or multi-stage based on the approval settings in the Entitlement Manager. The figure below shows the entitlement approval for a program.
+
+<figure><img src="../.gitbook/assets/approval-process.png" alt=""><figcaption></figcaption></figure>
+
+The multi-stage approval typically follows this process:
+
+* The first approving authority inspects and verifies documents, enrols the beneficiary based on eligibility, and adds an assessment.
+* Subsequent approving authorities will skip the process of enrolment. However, they also inspect and verify beneficiary documents, and add their assessments.
+* The last approving authority completes the approval process and generates an entitlement voucher.
+
+To learn the steps for multi-stage approval, click [here](../guides/user-guides/multi-stage-approval.md).
+
+## How-To Guides
+
+[Create a Custom Group](../guides/user-guides/create-entitlement-manager-role.md)
+
+[Create Entitlement Manager Type](broken-reference)&#x20;
+
+[Configure Entitlement Manager in the Program](broken-reference)
+
+[Configure Entitlement Voucher](broken-reference)
+
+[Multi-Stage Approval](../guides/user-guides/multi-stage-approval.md)
+
diff --git a/platform/modules/program-and-beneficiary-management-system/notifications.md b/platform/modules/program-and-beneficiary-management-system/notifications.md
@@ -0,0 +1,48 @@
+# Notifications
+
+## Introduction
+
+Notifications to beneficiaries and administrators are a must, especially when there are multiple stages of a delivery chain, usually with long time intervals between the different stages. Beneficiaries must be notified of their enrollment status, entitlements, payouts, exits, etc. Multiple channels such as SMS, email, and messaging apps can be used for notifications.
+
+OpenG2P provides configuration of email, SMS, and Fast2SMS notifications in a few simple steps. Depending on the implementation needs of a program, notifications can be triggered for specific events in the delivery chain.
+
+The figure below shows example notifications configured for two events - enrolling in the program and sending OTP.
+
+<figure><img src="../.gitbook/assets/notification-events.png" alt=""><figcaption></figcaption></figure>
+
+## Notification Manager
+
+OpenG2P manages notifications via Notification Managers. Each program has at least one Notification Manager configured. The platform defines a different Notification Manager for each type of notification - SMS, email, Fast2SMS. These are the most commonly used Notification Managers:
+
+* SMS Notification Manager
+* Email Notification Manager
+* Fast2SMS&#x20;
+
+OpenG2P uses the in-built [Qweb Templates](https://www.odoo.com/documentation/16.0/developer/reference/frontend/qweb.html) and [Inline Templates](https://apps.odoo.com/apps/modules/10.0/mail\_inline\_css/) for configuring the HTML pages and fragments. Notifications are sent based on the event and application configurations.
+
+<figure><img src="../.gitbook/assets/notification-template.png" alt=""><figcaption></figcaption></figure>
+
+## Configuring notifications
+
+Configuring the notifications requires two steps:
+
+#### Create a Notification Manager type
+
+The program administrator must create at least one Notification Manager for each Notification Manager type required. To learn more about this step, click [here](../guides/user-guides/create-notification-manager-types/).
+
+#### Add the Notification Manager to a program
+
+The program administrator needs to add the Notification Manager(s) created in the first step to the program. To learn more about this step, click [here](../guides/user-guides/configure-notification-manager.md).&#x20;
+
+## Send notifications
+
+Sending the notifications is a one-click operation. Based on the state of the program - enrolment, entitlement, payment, etc. - the corresponding notification is sent by the Notification Manager types configured for the program. To learn more about this step, click [here](../guides/user-guides/send-notifications-to-individual-registrants.md).
+
+## How-To Guides
+
+[Create Notification Manager Types](../guides/user-guides/create-notification-manager-types/)
+
+[Create Notification Manager under Program](../guides/user-guides/configure-notification-manager.md)
+
+[Send Notifications to Individual Registrants](../guides/user-guides/send-notifications-to-individual-registrants.md)
+
diff --git a/platform/modules/program-and-beneficiary-management-system/proxy-means-test.md b/platform/modules/program-and-beneficiary-management-system/proxy-means-test.md
