All Gram Panchayats have a monthly billing cycle for water charges. The Scheduler automatically triggers on the “X” date of every month to generate demand and raise bills for non-metered connections.

• Metered connections do not fall under bulk demand generation

1. For the first month of go-live, it is only the arrears and no demand that is generated hence there is no bill to collect payments.

2. From the second month (X date of Month 2) onwards, demand is generated.

3. Once the demand is generated, a notification is triggered to all mGramSeva users.

   • Details of Notification

     • “Demand for water charges has been raised for <GP>. New Bill Amount is Rs. Xyz. Overall pending amount is Rs.AbcD”

4. Each non-metered household also gets notifications

   • SMS Notification with Bill PDF

     • Dear “username”, A new water bill has been generated against <connection ID>. Please download the bill using <link>

   • SMS notification with a payment link

     • Dear “username”, A new water bill has been generated against <connection ID>. Please pay the bill online to avoid late payment charges<link>

5. Revenue collectors can see a new card (Updated card from month 2 onwards) with information related to demand and payment collection on the HH Details screen.

6. There is also a demand collection tile/card on the home screen.

   • This is used in cases when the scheduler is not run (due to technical errors) and the Gram Panchayat wants to run it manually.

7. The system does nothing if the manual demand generation is done in the middle of the billing cycle for which demand has already been generated.

   • Manual demand generation helps only when the scheduler has not generated a demand for a billing cycle.

In the Bulk Demand screen -

Service Category: Defaulted to Water Charges (Module)

Service Type: Defaulted to “Non-Metered”

Billing Year: Dropdown with the list of the financial years from the master

Billing Cycle: Dropdown with the list of billing cycles for the selected financial year

Clicking on Generate Demand triggers the demand for the given billing cycle based on the logic defined above.

The documents in this section provide the complete details of the

Overview

The household masters have to be created in the system to initiate the demand generation and collection process. These are consumers also referred to as the household that avails the water connection and supply on regular basis.

Select the Create Consumer option from the list of tile/cards on the home page. This redirects the user to the Create Consumer page.

Data element details for the consumer are listed in the table below -

Additional Notes and Validation

• Clicking on the Submit button creates the consumer master and a new consumer ID is assigned to the master. The consumer ID generated is based on logic defined as - “WS-<GP id>-<4 digit running seq No>”

• If the connection ID already exists, the system displays an error message.

• On first-time/new-load, all data entry fields and dropdowns are empty (since there are no records prefilled except for the default fields).

• SMS is not sent to any user upon consumer (HH) creation.

• Submit is disabled until all mandatory fields are entered. Once all inputs are made, the button is enabled.

• Arrears demand:

  • Metered - The arrear demand for the period is created, where the From date is counted as the start of the Financial year and the To date as the period mentioned on the screen.

  • Non-metered - The arrear demand is created for the selected billing cycle.

Successful Actions

1. Successful creation of consumer records displays the toast message “ Registration successful”.

2. Closing this toast message, using the close icon, refreshes the page and the user sees an empty consumer creation screen.

Based on the user role the following functionalities are available and displayed on the home screen:

Overview

Consumer information can be edited under certain conditions -

1. Before the first demand is generated in the system

2. After the first demand is generated in the system

Edit Screen

• Users with permission to edit consumer records can click on the Edit Consumer info tile on the home screen. This navigates them to the consumer search screen.

• Users can navigate from the search screen or the search results screen (Case when multiple search results are displayed) to the Consumer Edit Screen.

• On the successful load of the consumer edit screen, all data parameters of the consumer are shown (with editable and non-editable fields).

• By Default - New consumer ID is shown on the top of the screen and is non-editable.

The table below lists the editable field details -

Edit Options

1. In case there are arrears, demand is generated. If there are no arrears, demand is not generated.

2. Users can modify the arrear value. In such a case, demand is generated with the updated value.

3. Users can add arrear to the connection, for which arrear was zero at the time of creating the connection. In such a case, new demand is generated.

Clicking on the Submit button shows a nudge saying Details Submitted Successfully. Closing the nudge navigates the user back to the home screen.

The CTA is activated only when any field is changed or updated. Else, it is in an inactive state.

Once the demand is generated for metered and non-metered connections, revenue collectors come to this screen to collect payments.

1. Users can see the consumer billing information on the screen

2. Clicking on View Details expands the card and shows more details. Clicking on the Hide Details collapses the card to show only connection ID, Consumer Name & Total Due Amount.

3. Payment amount - can either pay

   • The full amount, or

   • Custom amount - Users can enter the custom amount in the input field - this cannot be zero or greater than the total due amount.

4. Payment methods

   • Cash - select cash and proceed to payment takes the user to the successful collection screen

   • Online - The online payment option displays a Q/R code on the user screen that can be scanned by another phone to pay the due.

   • Post payment via any mode - payment success screen is shown

   • Receipt ID format - RB-dd/mm/yyyy-yy/running_sequence_number

5. User Actions

   • Download receipt - download PDF version of receipt with receipt ID as the name of PDF while downloading

   • Share receipt via WhatsApp - opens the Phone OS sharing options

   • back to home - takes the user back to the home screen

6. SMS to HH

   • As soon as the amount is paid and the Revenue collector reaches the Payment success screen SMS is sent to HH.

     • SMS 1 - Dear ‘Username’, Paid Rs.X for water charges for bill period <Cycle>. Download receipt <link>

     • SMS 2 - Dear ‘Username’, Please leave a review on water supply at <GP> at <Link>

     • HH is able to leave a review for water charges. Refer

Details on the card

• When an online payment method is selected, the “Collect Payment” option is disabled. Since HH scans the QR, the Revenue collector does not have control over the online process.

• The partial amount cannot be greater than the full amount.

Overview

The search screen is used to filter the list of consumers based on selected criteria. This is the common search screen for all the transactions such as -

1. Collect payments

2. Download bills and receipts

3. Update consumer information

Search Parameters

The consumer can be searched on the following parameters -

1. Owner Mobile Number - Allows search of consumer records that match the entered mobile number.

   • OLD Mobile Number

   • NEW Mobile Number

   • The user is able to search only when he/she enters the full mobile number. A partial mobile number search is not allowed.

2. Name of Consumer - Allows search of consumer records that match consumer names with the input text.

   • OLD Name

   • New Name

   • Name search can be done with a partial name also.

3. Old Connection id - Allows search of consumer records that matches the old Connection id entered in the search bar.

4. New Connection id - Allows search of consumer records that matches the New Connection id entered in the search bar.

Search Result

The search result set contains the below information -

1. Sub-Heading - Subheading text changes dynamically with the type of search carried out.

   • Following consumers match search criteria with

     • Phone Number as +91 - 7731045306

     • Name as ABCxyZ

2. New Connection ID

3. Old Connection ID

4. Consumer’s Name

5. Phone Number

6. Address - Combination of Door Number, street number, Ward (if applicable)

7. Clicking on the View Consumer Details button redirects the user to the HH Details screen.

The expense entry for the O&M on regular basis is captured on this screen.

On selecting the option “Add Expense Record” from the list of tile/cards on the home page, the user is navigated to the expense entry screen. The screen displays the following fields.

On Submitting, the Expense entry gets created with a Bill number assigned. The Bill number generated would be based on logic defined as - “EB-<FY>-<4 digit running seq No>”

On Successful creation of expense entry, an acknowledgement screen is shown “Expense Entry successful” along with the Bill Number.

Overview

1. Users are redirected to the View Consumer screen from the home screen via

   • Collect payments → Search Screen → Consumer Details Screen

   • Download bills & receipts → Search screen → Consumer Details Screen

   • Dashboard → Collections → Click on Consumer ID

   • Household Register → Click on Consumer ID

2. This screen contains all information related to HH

Static HH card displays the following details

1. New Connection ID (also displayed as a heading)

2. Consumer name

3. Father's name

4. Phone number

5. Old connection ID

6. Address - Door Number, Street number, Ward (attached)

7. Property type

8. Service type

   • for metered connections - the meter number is displayed

For Non-Metered Connection

1. If the bill is not generated (Post rollout until the first month)

   • Only the data Card is shown - No action is required

2. Once the first demand is generated - A new consumer bill/card gets generated and displays the following data points and actions -

   • Billing cycle – the latest billing cycle

     • Amount -

       • Current Amount - fixed charges applicable to the billing cycle

       • Arrears - Arrears from the first month (From next month onwards this field displays any unpaid dues)

       • Total Amount - Sum of current amount and arrears

     • Action Items

       • Download or Share Bill

         • Clicking on download bill prompts users to download the bill (Bill details are given in a separate user story)

         • Share bill (WhatsApp icon) opens sharing options to the phone OS and the user is able to share bills via WhatsApp

         • Message to go in WhatsApp “Please find Bill for water charges with Connection ID WS-83121-8312 generated on dd/mm/yyyy” along with bill PDF

         • Name of the PDF - “Bill ID”

       • Collect Payment

         • The Collect payment button takes the revenue collector to the payment collection screen

3. After the First payment collection is done

   • A receipt history block is visible only after the first payment transaction is completed through mGramSeva

     • A list of all the receipts is shown under this section as cards, with different data points as actions. Order of receipts is newest → oldest from top to bottom

     • Each receipt card contains

       • Receipt ID

       • Amount Paid

       • Paid Date

     • Actions

       • Download Receipt - downloads the receipt in the Revenue collectors phone as a PDF

         • Name of PDF - “Receipt ID”

       • Share (WhatsApp)

         • Message to go in WhatsApp “Please find the receipt for water charges with Connection ID WS-83121-8312 paid on dd/mm/yyyy” along with receipt PDF

New Connection Before First Bill Generation

First bill is generated - Payment Collection is pending

2 payments made

For Metered Connection

1. If a bill is not generated (Post rollout until the first month)

   • A data card is displayed on the screen

   • Below the data card - the Card to generate a new bill is also displayed

   • This card contains

     • Last bill generation date - For the first time this is picked up from data entry. Next time onwards the system captures the last bill generation date

     • Days from last bill generation date - indicates to the revenue collector the number of days passed since the last time a bill is generated

     • Previous Meter reading - Displays the last read meter units

     • Pending Amount

       • Before the first bill is generated, the arrears are captured during data entry

       • After the first bill is generated, the pending amount includes the entire amount due for the specific user

     • Generate a new bill

       • Clicking on Generate a New Bill initiates bill generation flow for metered connection

     • Note - Users have to generate a bill to start collecting payments. Arrear amount collection also is not possible till the first bill is generated.

2. After the first bill is generated

   • A new consumer bill/card gets generated with the following data points and actions

     • Last bill generation date - date of bill generation

       • Amount -

         • Current Amount - Volumetric charges between 2 latest meter readings according to rate master

         • Arrears - All previously unpaid dues

       • Total Amount - Sum of current amount and arrears

     • Action Items

       • Download, Share Bill

         • Clicking on the download bill prompts users to download the bill for the respective amount (Bill details are given in a separate user story)

         • Share bill (WhatsApp icon) opens the sharing options of the phone OS and the users can share bill via WhatsApp

         • Message to go in WhatsApp “ Please find Bill for water charges with Connection ID WS-83121-8312 generated on dd/mm/yyyy” along with bill PDF

         • Name of the PDF - “Bill ID”

       • Collect Payment

         • Collect payment takes the revenue collector to the payment collection screen

3. After the first payment collection is done

   • A receipt history block is visible only after the first payment happens through mGramSeva

   • A list of all the receipts is shown under this section as cards, with different data points as actions. Order of receipts is newest → oldest from top to bottom

   • Each receipt card contains

     • Receipt ID

     • Amount Paid

     • Paid Date

   • Actions

     • Download Receipt - downloads the receipt to the revenue collectors phone as a PDF

       • Name of PDF - “Receipt ID”

     • Share(WhatsApp)

       • Message to go in WhatsApp “ Please find receipt for water charges with Connection ID WS-83121-8312 paid on dd/mm/yyyy” along with receipt PDF

4. If a new bill is generated again by clicking on ‘Generate a new bill’ - the revenue collector goes through the bill generation flow and a single new card appears between ‘Generate bill’ and ‘Consumer receipts block’

There are 2 methods to generate Bulk Demand -

1. Auto (scheduler based)

2. Manual

Auto: The demand is generated at end of the month or the first day of next month or as scheduled for the recently completed billing cycle. Use cases are as below -

1. First demand generated in the system: The demand is generated for the recently completed billing cycle considering the arrears in the master data. The arrears are tagged to the previous billing cycle of the current demand.

2. Consecutive demands: The demand is generated for all the months pending from the most recent to the last billing cycle completed.

3. The demand is generated for the recently completed billing cycle.

Manual: The demand is generated for the billing cycle selected by the user. The demand is generated only for those consumers for whom demand does not exist for the selected month.

1. First demand generated in the system: The demand is generated for the selected billing cycle considering the arrears in the master data. The arrears are tagged to the previous billing cycle of the current demand.

2. Consecutive demand: The demand for the selected month is generated only if the previous billing cycle demand exists. If the demand for the previous cycle does not exist, it gives an error message “Demand generation is pending from billing cycle - <Name of cycle>. please generate demand from this cycle in sequence”. The validation considers the most recent billing cycle that exists in the system.

Charges/Heads & Calculation Logic

As part of V1, only the water charges head is applicable. Rate Master is defined at the GPWSC level.

Water Charges - Charges are applicable as defined in the Rate Masters based on - Validity, Property Type, and Service Type where the calculation type is “Per Bill Cycle” for the given billing period.

Bill Period - The billing periods are monthly as per the standards followed across GPWSCs. In future, GPWSC may switch to bi-monthly to reduce the processing effort. The sample billing period data is given in the MDMS data.

Exclusion

• Reversion of demand is not allowed. This has to be done in the backend.

• Exception reporting for every batch processing can be accessed from the backend only.

The user of the GP system is onboarded by loading user records in bulk as a backend activity. The system enables the loading of user records in bulk and creates the profiles with a mobile number as login id and with a random password.

On loading user profiles - The GP users are sent a link and login credentials over SMS required to login to the mGramSeva application. The link navigates to this screen and takes the user through the flow of logging in and resetting the password in case of first-time login.

The web link, too, initiates from the same screen.

​All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Overview

The users receive a link via SMS. Clicking on this link redirects the users to the login page of the mGramSeva app. The users can log in from this screen or even reset their password in case they are logging in for the first time. The mGramSeva application link initiates from this screen.

Language Selection

The link in the SMS redirects users to this screen which is the first screen which is the language selection screen. The user selects the preferred language and clicks on Continue. English, Hindi, and Punjabi are the supported languages with Punjabi as the default language. Localization in the screens is displayed based on the language selected.

User ID and Password Entry

The user enters the User ID, which is the registered mobile number of the user, and the system-generated password. Clicking on the Continue button logs in the user.

Forgot Password

The Forgot Password link navigates the user to the password reset screen.

On Successful Login or on Validations of User ID and Password

First Time Login

The user is redirected to the password reset screen where they enter the OTP received on the registered mobile number. The next screen prompts the user to enter a new password and then confirm the same. This is similar to the first-time login screen. Clicking on Submit displays the acknowledgement screen. Clicking on the Continue to Login button on the acknowledgement screen takes the user to the login page.

Subsequent Login

The user is redirected to the home page of the application which displays the menu options based on the mapped user role.

Users can walk through the application for a better understanding of different user actions available on key screens.

Home Screen

Consumer creation screen

Expense Entry Screen

Dashboard

Unlike non-metered connections that have a billing cycle for demand & bills generated automatically, a metered connection needs more inputs, which helps in volumetric billing.

A revenue collector can see a CTA to “Generate a new Bill” on the HH details screen.

1. Clicking on “Generate a new Bill” takes users to the bill generation screen where new meter reading details are entered.

2. The field on the bill generation screen for metered connections is displayed in the table below.

3. Clicking on “Generate bill” takes the user to the bill generation successful screen.

4. Logic for Bill ID number - “RB - dd/mm/yyyy-yy/running_sequence_number”.

5. There are 3 user actions on the success screen

   • Download bill - Download bill as PDF (name of PDF is always the Bill ID by default)

   • Share bill on WhatsApp - Share bill as PDF on WhatsApp

   • Collect Payment - navigates the revenue collector to the payment collection screen

6. Share on WhatsApp opens the WhatsApp share popup with the option to choose contacts/groups. The bill is shared with the below text and attached PDF details -

   Text “ Dear <ConsumerName>, Please find water bill for billing cycle <Cycle> attached as PDF”

For Demand Generation Logic refer to

1. All 5 digits in the meter reading must be entered. Show error message “ Old Meter Reading entered is Invalid” or “ New Meter Reading entered is invalid” respectively.

2. The New Meter reading should be greater than the Old Meter Reading.

3. The meter reading date is by default set to <today's date> but gives the option to change to the user.

For mGramSeva users, different notifications are displayed on the home screen based on various system triggers.

1. A new card is used for each notification displayed below.

2. Cards have a countdown timer - today, 1 day ago, 2 days ago, 3 days ago, and so on.

3. Cards have a close icon on the right top corner. Upon closing, the card view is removed from the screen. Cards, by default, do not have an expiry date.

4. A “New” text is shown to the user whenever there is a new notification after the user's last login.

5. The notification header shows the number of notifications in brackets.

All content on this page by is licensed under a .

Bill and Receipt PDFs can be sent to consumers at multiple touchpoints.

1. When bulk demand is generated through SMS

2. When meter reading is done for metered connections, via SMS

3. When revenue collector goes to HH screen and clicks on download PDF (into his mobile)

4. When revenue collector goes to HH screen and clicks on WhatsApp share PDF (Share PDF’s on WhatsApp)

Bill PDF

Receipt PDF

Various SMS notifications are sent to different users on different actions. Below is a consolidated list of all SMS notifications required.

All content on this page by is licensed under a .

Expense modification is allowed based on the status of the payment as given in below scenarios -

Scenario 1: When the status is “Unpaid”

Allows users to modify all the details except the Bill id. But the user has the option to mark the Bill as “Cancelled”.

Scenario 2: When the status is “Paid”

Does not allow users to modify any details. But the user has the option to mark the Bill as “Cancelled”.

All content on this page by is licensed under a .

As soon as the revenue collector marks the bill as paid by the consumer, they receive one SMS with the link to receipt in PDF format and another SMS with a link to collect feedback.

All content on this page by is licensed under a .

The demand is generated for metered connections for the billing period (defined based on the meter reading date) selected by the user at the time of recording the meter reading.

The 2 use cases to be handled are -

1. First demand generated in the system: The demand is generated for the selected billing period. The demand period would be from “Previous meter reading date” from the consumer master or the demand created as part of the master TO the date entered in the billing screen. The arrears are tagged to the previous billing period of the current demand, and the period is from the start of FY to the “Previous meter reading date” from the consumer master.

2. Consecutive demand: The demand is generated for the period defined based on

   • From Date: Meter reading date from last demand generated for the consumer

   • To Date: Is the selected meter reading date in the bill generation screen

Charges/Heads & Calculation Logic

As part of V1, only the water charges head is applicable. Rate Master is defined at the GPWSC level.

Water Charges - Charges are applicable as defined in the Rate Masters based on - Validity, Property Type, and Service Type where the calculation type is “Unit Rate” for the given number of units.

Bill Period - Is as per the date range selected for the bill generation.

Exclusion

• Reversion of demand is not allowed. This has to be taken up in the backend.

All content on this page by is licensed under a .

mGramSeva users can edit their basic information like name, add gender, email and change password using the hamburger menu on any screen.

1. Users can click on the hamburger menu from any screen. A slider from the left opens up.

2. Users are able to

   • Change Language

   • Edit profile

   • Logout

3. Changing language changes localization as per standards

4. Edit profile takes users to the next screen where changes can be made to the user profile

   • Name - Can be changed

   • Phone number - Cannot be changed

   • Gender - This field is not present by default. Whatever user enters is stored and saved

   • Email ID - It is an empty field. User input is stored as the user’s email id

   • Change Password - This takes users to the password changing screen where the old password, new password and confirm new password have to be entered as per given standards.

     • Dynamic password validation happens the same as in the registration flow.

     • Until all fields are entered, the primary CTA is disabled.

     • Changing the password shows a nudge to the user “Password updated successfully” and closing this nudge takes the user to the user profile screen.

   • Clicking on save shows a nudge to the user” Details saved successfully”. Upon closing, this user remains on the screen but the fields show as edited.

Overview

Users can click on the Household Register on the home screen and navigate to this screen. This provides a single-view snapshot of all pending collections by consumers to date.

Data Points

Clicking on the Back button takes the user back to the home screen.

All content on this page by is licensed under a .

Overview

Clicking on the Dashboard on the home screen navigates the user directly to the revenue dashboard of the current month. From here, the user can switch to the expenditure tab to get a view of expenses. This provides a tabular view of all expenses incurred in that month.

Data Points

Following are the data points/actions needed on the screen:

The table on the screen is a horizontal scrollable one with the leftmost column fixed.

All content on this page by is licensed under a .

On selection of “Modify Expense” option, the below search screen is shown for the users to search the Bill/s -

Search Criteria -

• Vendor Name

• Expense Type

• Bill D

Search Result - Lists all the Expense bills matching the above search criteria

• Bill ID

• Type of Expense

• Vendor Name

• Amount

• Bill Date

• Status

Clicking on Bill id displays the Expense Bill in edit mode based on the validations.

Overview

Water Connection advance changes are added to allow the customer to pay the advance amount. This amount is adjusted when a new demand is generated. We can enable or disable advance based on the configuration.

Pre-requisites

Before you proceed with the documentation, make sure the following pre-requisites are met -

• Java 8

• Kafka server is up and running

• egov-persister service is running and has the water service persister configs path added to it

• PSQL server is running and a database is created to store water connection/application data

• The following services should be up and running:

  • egov-persister

  • egov-mdms

  • ws-services

  • billing-service

  • ws-calculator

  • egov-apportion-service

Key Functionalities

• Accepts advance amount during water connection creation and while collecting payment

• Creates demand for consumer type waterConnection-advance

• Adjusts the new demand with existing advance with apportion service

Deployment Details

Deploy the latest version of ws-service, ws-calculator, billing-service, egov-apportion-service

MDMS Configuration

Billing Service tax head configuration

{
      "businessService": "ws-services-calculation",
      "code": "WS",
      "collectionModesNotAllowed": [
        "DD",
        "CHEQUE",
        "CARD",
        "OFFLINE_NEFT",
        "OFFLINE_RTGS",
        "POSTAL_ORDER",
        "ONLINE"
      ],
      "partPaymentAllowed": true,
      "isAdvanceAllowed": true,
      "demandUpdateTime": 86400000,
      "isVoucherCreationEnabled": false,
      "billGineiURL" : "egov-searcher/bill-genie/waterbills/_get",
      "isBillAmendmentEnabled":true
    }

Tax head master service configuration

{
      "category": "ADVANCE_COLLECTION",
      "service": "WS",
      "name": "Ws advance carry forward",
      "code": "WS_ADVANCE_CARRYFORWARD",
      "isDebit": true,
      "isActualDemand": false,
      "order": "0",
      "isRequired": true,
      "IsBillamend": false
    },

Existing Service Code Changes Billing service changes:

• Creating a new bill for the advance amount in BillServiceV2. Removing the following line while adding the bill objects to the list if (billAmount.compareTo(BigDecimal.ZERO) >= 0)

• Passing Active status filter for demand search during apportioning in DemandService. DemandCriteria searchCriteria = DemandCriteria.builder().tenantId(tenantId) .status(Demand.StatusEnum.ACTIVE.toString()).consumerCode(Collections.singleton(consumerCode)). businessService(businessService).build();

• New Demand audit history API in Demandcontroller. An API that returns the audit history of demandDetails. demand/_history

Water service changes:

• Create water connection API : Adding a check for payment type advance. If advance, passing a boolean isAdvanceCollection to calculationRequest to water calculator service.

• Update water connection API: Adding a check for payment type advance. If advance, passing a boolean isAdvanceCollection to calculationRequest to water calculator service. Adding a check for advance in the validateUpdate method to set the current demand to CANCELLED.

Water calculator service changes:

• Calling estimation service getEstimationMap based on isAdvanceCalculation boolean. If true, reading taxAmount from criteria.getWaterConnection().getAdvance();

• Changes in getEstimatesForTax for a new taxHeadCode ADVANCE_COLLECTION with value WS_ADVANCE_CARRYFORWARD

• Getting the advance amount in getCalculation with taxHeadCode ADVANCE_COLLECTION 4.Calling generateDemand method based on isAdvanceCalculation. If true, create a demand object with consumerType “waterConnection-advance“.

Introduction mGramSeva

mGramSeva is a standalone app-based module that enables the GPWSC committee to create new consumers, generates demand, revenue collection and records the expenditure transaction etc.

mGramSeva enables GPWSCs to maintain financial records of GPWSCs following established procedures and practices.

Key sections:

• Login to App

• Edit profile and change password

• Create consumer & edit consumer details

• Search consumer, generate payment - metered connection

• Search consumer, generate payment - non-metered connection

• Record expense bills & modify expense bills

• Dashboards

Sarpanch, Treasurer, Secretary and Revenue Collector Login

Sarpanch, Treasurer, Secretary and Revenue Collector as first-time users can log in to the mGramSeva app following the steps given in the Login to App section.

Login to App

Click on the preferred language button. The app functions and screens will be available in the selected language.

Enter the registered mobile number and the Password received via SMS.

The user receives an OTP on the registered mobile number. Enter the OTP. Enter a New Password and retype the password to confirm in the Confirm New Password field. Follow the Password Hint on the screen while setting up the password.

Click on the Confirm button. The user password is now updated. Click on the Continue to Login button to log in with the new password.

Click on the relevant village tenant assigned to the user from the screen.

This redirects the user to the relevant mGramSeva functionalities available for the selected tenant.

Edit Profile and Change Password

Users can edit their profiles and change passwords as and when required. Click on the User icon on the top section of the screen. Click on Edit Profile to make profile changes.

Update Name, Gender, or Email ID as required. Make note that the registered Mobile Number cannot be changed. Save the changes.

Click on the Change Password button to change the password.

Create Consumer and Edit Consumer

Click on the Create Consumer icon on the screen to create a new consumer.

This opens the Consumer Details screen. Enter the requested consumer details.

1. Name

2. Gender

3. Father Name

4. Phone Number

5. Old Connection ID

6. Door Number

7. Street Name/Number

8. Ward Name/Number

9. Type of Connection

10. Type of Water Supply

11. If the Type is non-metered

    • Previous Billing year and cycle

12. If Type is metered

    • Previous meter reading date

    • Meter number

    • Previous meter reading

13. Radio Button

    • Arrears: Enter the Arrear amount and penalty as of the billing cycle.

    • Advance: Enter the advance amount as of the billing cycle.

Users can also edit the consumer details if any changes need to be made in the consumer record. Click on the Edit Consumer Details icon on the home screen to make the necessary changes.

Check the option Mark this connection as Inactive to indicate that the given consumer connection is inactive.

Click on the Submit button to save these changes.

Search Consumer and Generate Payment - Metered & Non-Metered Connection

Metered Connection

Click on the Generate Demand icon on the home page to search for a consumer record once the consumer is created. The application enables the users to search a consumer record by Consumer’s Phone Number or Name of the Consumer or Old Connection ID or New Connection ID.

Click on the Search button to view the consumer records. Click on the View Consumer Details button to perform the necessary action.

Users can see the relevant information of a particular consumer. Click on Generate a New Bill button to create a fresh bill. Enter the Previous Meter Reading, New Meter Reading and Meter Reading Date. Click on Generate Bill. A fresh bill is generated for the consumer.

Once the bill is generated, the user can collect payment for the particular bill. Click on the Collect Payment button to collect the payment via cash or online payment.

Click on the phone icon in green to share the bill with the consumer via SMS.

Enter/Update the Payment Amount or Partial Payment to indicate whether the consumer is paying the bill amount in full or making a partial payment. Enter the Amount that is being paid by the consumer in case it is a Partial Payment.

Select the applicable Payment Method as either Cash or Online. Users can also provide consumers with a scannable QR code to make the payment online.

Click on the Download button to download the payment receipt.

Click on the Share icon to send the receipt to the consumer via SMS.

Non–Metered Connection

Click on the Collect Payment icon on the home page to search for a consumer record by Consumer’s Phone Number or Name of the Consumer or Old Connection ID or New Connection ID.

Click on the Search button to view the consumer records. Click on the View Consumer Details button to perform the necessary action.

Click on the Collect Payment button to collect the payment via cash or online payment. Click on the Share Bill button to send the bill to the consumer on the registered mobile number via SMS.

Select Full Payment or Partial Payment to indicate whether the consumer is paying the bill amount in full or making a partial payment. Enter the Amount that is being paid by the consumer in case it is a Partial Payment.

Select the applicable Payment Method as either Cash or Online. Users can also provide consumers with a scannable QR code to make the payment online.

Click on the Download button to download the payment receipt. Click on the Share icon to send the receipt to the consumer via SMS.

Once the payment is completed an SMS is sent to the consumer to take the survey on the water service.

Record Expense Bill and Modify Expense Bill

Expenses Bill Recording

Users can enter the expense details as and when incurred. Click on the Add Expense icon on the home page.

Enter expense information like Type of Expense from the drop-down list available. The type of expenses can be Electricity, O&M, Salary & MISC etc.

Enter Vendor Name, Amount, Bill Date, Party Bill Date. Select Yes or No to indicate if the bill is paid or not. Click on Choose File button to attach a supporting document.

Enter the Payment Date if the bill is already paid before recording it into the system. Click on Submit to register the expense details.

The expenditure entry is saved successfully.

Modify Expense Bill

Click on the Modify Expenses icon on the home page to modify expense details. Enter the Vendor Name, Type of Expense or Bill ID details to search for the specific expense record which needs to be modified.

The system shows the expense records filtered by the search parameter. Click on the Update Expenditure button to modify a particular bill.

Make the necessary modifications to the bill. Update the expense type, or vendor name, amount, or bill date details as required.

Click on Submit to save the changes. Check the Mark this Bill as Cancelled box to indicate that the bill is cancelled.

Dashboard

Main Dashboard

The Dashboard provides the stakeholders at the department level with a consolidated view of the information on Revenue and Expenditure trends month-wise.

Revenue Dashboard

The Sarpanch, Treasurer and Secretary at the GPWSC level can view the collection details like Demand, Pending Collection, Actual Collection, Collection from Residential, Collection from Commercial and Collection from Others. The consumer-wise collection details view is also available.

The Sarpanch, Treasurer and Secretary at the GPWSC level can view the expenditure details like total expenditure, amount unpaid, the amount paid, total bills, pending bills, bills paid, Electricity bills, O&M and salary. The individual expense-wise details view is also available.

Backend Code Git Repo https://github.com/egovernments/punjab-mgramseva/tree/master/business-services/egov-hrms

Connect to your GitHub account and navigate to the config /persister repo: https://github.com/misdwss/config-mgramseva/blob/UAT/egov-persister/hrms-employee-persister.yml DevOps repo: https://github.com/misdwss/iFix-DevOps/tree/mgramseva/deploy-as-code/helm/charts/business-services/egov-hrmsConnect your Github account

There is the concept of hierarchy in mGramSeva : 1. State-level user → one who can create a Division user 2. Div level user → one who can create the employees like Sarpanch for mgramseva List of changes done in the user service and HRMS service to adapt HRMS in mGramSeva: Pfm 1419 user search by debasishchakraborty-egovt · Pull Request #610 · egovernments/punjab-mgramseva

1. Modified the search API of user service to do role based search of users based on the tenants it is mapped to and show the list in all cities where it is mapped to. State-level users can search for division users. Division users are created and mapped to pb as the base tenants and roles HRMS_ADMIN, and DIV_ADMIN to the concerned cities. Division users can search users based on roles like - SYSTEM,+GP_ADMIN,+COLLECTION_OPERATOR,+PROFILE_UPDATE,+DASHBOAD_VIEWER within the GPWSC it is currently logged into.

2. Modified the count API to search for users based on the role and the mapped tenant.

3. MDMS changes: PFM-1419 : HRMS mdms Changes by debasishchakraborty-egovt · Pull Request #312 · misdwss/mdms-mgramseva Update master-config.json by debasishchakraborty-egovt · Pull Request #314 · misdwss/mdms-mgramseva

APIs

Count API 1. Count Normal Employee API

curl --location 'http://localhost:8080/egov-hrms/employees/v1/_count?tenantId=pb.baruwal&_=1697534837504&roles=SYSTEM%2C%20GP_ADMIN%2C%20COLLECTION_OPERATOR%2C%20PROFILE_UPDATE%2C%20DASHBOAD_VIEWER&isStateLevelSearch=true' \
--header 'Accept: application/json, text/plain, */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json;charset=UTF-8' \
--header 'Origin: http://localhost:3000' \
--header 'Referer: http://localhost:3000/mgramseva-web/employee' \
--header 'Sec-Fetch-Dest: empty' \
--header 'Sec-Fetch-Mode: cors' \
--header 'Sec-Fetch-Site: same-origin' \
--header 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36' \
--header 'sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"' \
--header 'sec-ch-ua-mobile: ?0' \
--header 'sec-ch-ua-platform: "Windows"' \
--data '{
    "RequestInfo": {
        "apiId": "Rainmaker",
        "authToken": "28ee5e63-8150-48cf-a0b2-26212a450d18",
        "userInfo": {
            "id": 878469,
            "uuid": "b5bcbe8d-5410-4548-8b94-ee638d409f63",
            "userName": "9502410535",
            "name": "Rakesh",
            "mobileNumber": "9502410535",
            "emailId": null,
            "locale": null,
            "type": "EMPLOYEE",
            "roles": [
                {
                    "name": "HRMS_ADMIN",
                    "code": "HRMS_ADMIN",
                    "tenantId": "pb.baruwal"
                },
                {
                    "name": "DIVISION ADMIN",
                    "code": "DIV_ADMIN",
                    "tenantId": "pb.baruwal"
                },
                {
                    "name": "Employee",
                    "code": "EMPLOYEE",
                    "tenantId": "pb.baruwal"
                }
            ],
            "active": true,
            "tenantId": "pb.baruwal",
            "permanentCity": null
        },
        "msgId": "1697534837504|en_IN",
        "plainAccessRequest": {}
    }
}'

1. Count Division User

curl --location 'http://localhost:8080/egov-hrms/employees/v1/_count?tenantId=pb&_=1697534837504&roles=DIV_ADMIN%2CHRMS_ADMIN&isStateLevelSearch=true' \
--header 'Accept: application/json, text/plain, */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json;charset=UTF-8' \
--header 'Origin: http://localhost:3000' \
--header 'Referer: http://localhost:3000/mgramseva-web/employee' \
--header 'Sec-Fetch-Dest: empty' \
--header 'Sec-Fetch-Mode: cors' \
--header 'Sec-Fetch-Site: same-origin' \
--header 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36' \
--header 'sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"' \
--header 'sec-ch-ua-mobile: ?0' \
--header 'sec-ch-ua-platform: "Windows"' \
--data '{
    "RequestInfo": {
        "apiId": "Rainmaker",
        "authToken": "28ee5e63-8150-48cf-a0b2-26212a450d18",
        "userInfo": {
            "id": 878469,
            "uuid": "b5bcbe8d-5410-4548-8b94-ee638d409f63",
            "userName": "9502410535",
            "name": "Rakesh",
            "mobileNumber": "9502410535",
            "emailId": null,
            "locale": null,
            "type": "EMPLOYEE",
            "roles": [
                {
                    "name": "HRMS_ADMIN",
                    "code": "HRMS_ADMIN",
                    "tenantId": "pb.baruwal"
                },
                {
                    "name": "DIVISION ADMIN",
                    "code": "DIV_ADMIN",
                    "tenantId": "pb.baruwal"
                },
                {
                    "name": "Employee",
                    "code": "EMPLOYEE",
                    "tenantId": "pb.baruwal"
                }
            ],
            "active": true,
            "tenantId": "pb.baruwal",
            "permanentCity": null
        },
        "msgId": "1697534837504|en_IN",
        "plainAccessRequest": {}
    }
}'

Search APIs

1. Search Normal Employee

curl --location 'http://mgramseva-uat.psegs.in/egov-hrms/employees/_search?tenantId=pb.baruwal&isStateLevelSearch=false&limit=200&offset=0&sortOrder=ASC&roles=SYSTEM%2C%2BGP_ADMIN%2C%2BCOLLECTION_OPERATOR%2C%2BPROFILE_UPDATE%2C%2BDASHBOAD_VIEWER&_=1697180313780' \
--header 'Accept: application/json, text/plain, */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json;charset=UTF-8' \
--header 'Origin: http://localhost:3000' \
--header 'Referer: http://localhost:3000/mgramseva-web/employee/hrms/inbox' \
--header 'Sec-Fetch-Dest: empty' \
--header 'Sec-Fetch-Mode: cors' \
--header 'Sec-Fetch-Site: same-origin' \
--header 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36' \
--header 'sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"' \
--header 'sec-ch-ua-mobile: ?0' \
--header 'sec-ch-ua-platform: "Windows"' \
--data '{
    "RequestInfo": {
        "apiId": "Rainmaker",
        "authToken": "ab731e06-b758-47fb-8642-a598daf51d72",
        "userInfo": {
            "id": 4659,
            "uuid": "6736c66c-3091-45d4-9aa0-43dcffa914fc",
            "userName": "5000000001",
            "name": "DIVSION-ADMIN-TESTING",
            "mobileNumber": "5000000001",
            "emailId": null,
            "locale": null,
            "type": "EMPLOYEE",
            "roles": [
                {
                    "name": "HRMS_ADMIN",
                    "code": "HRMS_ADMIN",
                    "tenantId": "pb.lodhipur"
                },
                {
                    "name": "DIVISION ADMIN",
                    "code": "DIV_ADMIN",
                    "tenantId": "pb.lodhipur"
                }
            ],
            "active": true,
            "tenantId": "pb.massewal",
            "permanentCity": null
        },
        "msgId": "1697180313780|en_IN",
        "plainAccessRequest": {}
    }
}'

1. Search Division User

curl --location 'http://mgramseva-uat.psegs.in/egov-hrms/employees/_search?tenantId=pb&isStateLevelSearch=true&limit=200&offset=0&sortOrder=ASC&roles=DIV_ADMIN%2CHRMS_ADMIN&_=1697180313780' \
--header 'Accept: application/json, text/plain, */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json;charset=UTF-8' \
--header 'Origin: http://localhost:3000' \
--header 'Referer: http://localhost:3000/mgramseva-web/employee/hrms/inbox' \
--header 'Sec-Fetch-Dest: empty' \
--header 'Sec-Fetch-Mode: cors' \
--header 'Sec-Fetch-Site: same-origin' \
--header 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36' \
--header 'sec-ch-ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"' \
--header 'sec-ch-ua-mobile: ?0' \
--header 'sec-ch-ua-platform: "Windows"' \
--data '{
    "RequestInfo": {
        "apiId": "Rainmaker",
        "authToken": "ab731e06-b758-47fb-8642-a598daf51d72",
        "userInfo": {
            "id": 4659,
            "uuid": "6736c66c-3091-45d4-9aa0-43dcffa914fc",
            "userName": "5000000001",
            "name": "DIVSION-ADMIN-TESTING",
            "mobileNumber": "5000000001",
            "emailId": null,
            "locale": null,
            "type": "EMPLOYEE",
            "roles": [
                {
                    "name": "HRMS_ADMIN",
                    "code": "HRMS_ADMIN",
                    "tenantId": "pb.lodhipur"
                },
                {
                    "name": "DIVISION ADMIN",
                    "code": "DIV_ADMIN",
                    "tenantId": "pb.lodhipur"
                }
            ],
            "active": true,
            "tenantId": "pb.massewal",
            "permanentCity": null
        },
        "msgId": "1697180313780|en_IN",
        "plainAccessRequest": {}
    }
}'

Overview

Show Update App popup to end users in case there is a new release in the Google Play Store or IOS App Store.

MDMS Configuration

Add the file (link below) in the common-masters MDMS -

mdms-mgramseva/AppVersion.json at UAT · misdwss/mdms-mgramseva

Update the version in the above-mentioned file whenever a new release is deployed to the Play Store or App Store.

{  "tenantId": "pb", 
 "moduleName": "common-masters",  
"AppVersion": [    
{      
"latestAppVersion": "1.2.0",      
"packageName": "com.dwss.mgramseva"    
} ]  
}{  "tenantId": "pb", 
 "moduleName": "common-masters",  
"AppVersion": [    
{      
"latestAppVersion": "1.2.0",      
"packageName": "com.dwss.mgramseva"    
} ]  
}

Version Check Logic

commonProvider.getAppVersionDetails();

The MDMS call is made every time a user opens the app.

Once the ViewBuild() displays a pop-up on the landing page widget, it validates if the package version matches the version in MDMS.

await commonProvider.getAppVersionDetails();
CommonMethods()
    .checkVersion(context, commonProvider.appVersion!.latestAppVersion);

CommonMethods()
    .checkVersion(context, commonProvider.appVersion!.latestAppVersion);

Primary Files

Overview

This is an option to download bills without clicking on collect payment.

Steps

1. Bills and Receipts can be downloaded by clicking on the card/tile named Download Bills & Receipts on the home page.

2. Clicking on this card takes the user to the consumer search page. Searching by a phone number/ connection ID redirects to the Household Detail page.

Overview

Clicking on the Dashboard on the home screen navigates the user to the revenue dashboard view for the current month. This provides a tabular view of the list of consumer records.

Data Points

The following data points/actions are needed on the screen -

All content on this page by is licensed under a .