NalJalSeva: Empowering Rural Water Management With DIGIT

NalJalSeva, powered by the DIGIT platform, is designed for rural communities to independently manage their water supply infrastructure. The solution allows users to add new consumers, generate demand, collect revenue, and record expenditure transactions. It simplifies record-keeping, maintains a consumer database, monitors user charges, and provides a unified system for benchmarking rural governance and operations.

The NalJalSeva solution design impacts the financial and operational governance outcomes in multiple ways. Some of these include:

• Empowering Local Communities: Villages gain full control over their water systems, promoting long-term sustainability.

• Digital Governance: Built on DIGIT, NalJalSeva streamlines revenue and expense management, ensuring smooth operation.

• Transparent and Accountable: Financial and operational activities are visible to local governments, ensuring transparency and accountability.

Problems Addressed By NalJalSeva

The Finance Department and Water Supply and Sanitation Department have limited visibility over the fiscal sustainability of water schemes and get hit by the sudden demand for large funds to clear electricity bills.

The Department of Water Supply & Sanitation (DWSS) face several problems due to the lack of financial visibility of schemes:

• Unreliable and poor-quality water—Ineffective fiscal resource tracking often results in underfunding of water quality or treatment schemes.

• Inability to collect adequate water charges — Manual methods of revenue collection from households on account of water charges often lead to shortfalls. Pending dues often accumulate and adversely impact financial planning and proposed schemes.

• Lack of visibility of revenue and expenditure information - Inadequate financial transparency offers limited insight into how funds are being managed and spent by the local governing bodies. This creates financial blind spots, leading to misallocation of resources and unplanned expenses.

NalJalSeva helps digitise the revenue and expense records of Gram Panchayat Water Supply Committees. The dashboards and data insights provide DWSS and FD officials with visibility into the GPWSC's financial status.

The app offers capabilities to:

• track and manage the revenue and expenditure records using the digital platform

• share reports over WhatsApp

• access updated insights on consumer satisfaction/quality of services provided by local governing bodies

• view dashboards for a snapshot of collections and expenditures to the Sarpanch/other rural administrative officials

• access detailed collection reports from each household for accurate insights into consumption and demand

Approach

NalJalSeva integrates with the Fiscal Information Exchange (iFIX) platform to promote transparency and accountability in fiscal transactions. The fiscal events are posted on the platform in a standardised format making it easier to track and manage financial performance. The events are aggregated and processed to provide rich insights on key performance metrics which are available to users in the form of fiscal sustainability dashboards.

The illustration below provides a visualisation of how multiple actors interact with the distinctive Gram Panchayat Water Supply & Sanitation system registries to manage and coordinate various fiscal events. The key actors or stakeholders of the system include system administrators, department workers, local governing bodies, citizens and collection agents. Streamlined interaction between these actors is crucial for effective operations and management of fiscal events to facilitate sustainable and equitable access to basic services within the community.

The NalJalSeva app offers multiple benefits that promote the efficiency and transparency of water management services within local governing bodies.

• Digital book-keeping - maintains all receipt and expense records in digital format reducing the reliance on physical documents.

• Account management - simplified consumer and vendor account creation or management

• Low-effort operations - easy to use and environmentally friendly

• Minimise manual work - a simple mobile app that saves the time and effort of managing revenue & expenditure transactions

• Environment friendly - digital operations ensure all accounts are managed digitally thus reducing paper usage

• Accountability and transparency - recorded fiscal events and data-driven insights available through performance dashboards ensure accountability and transparency in operations

• Seamless handover - easy to handover records from one to another Sarpanch

• Dashboard insights - configurable dashboards provide easy and effective visualisation of local governance performance metrics

• Better planning - helps in better planning and efficient fund management, leading to better services

• Builds trust - information sharing about GPWSCs’ performance with citizens helps build trust and confidence

• Online and cash payment - Online payment through multiple options - Netbanking, Credit/Debit Card, Mobile Wallets. Cash payment is also available

• Notifications and alerts - SMS alerts, digital bills and receipts shared on registered mobile numbers, active SMS alerts

• Consumer rating - Citizens can rate the quality of water services in villages/wards. It helps identify problems and improve water services.

• Full or partial payment - users have the option to make partial payment of bills

About NalJalSeva

A digital solution powered by DIGIT that enables the gram panchayat water committee to collect & manage revenue and expenditure.

NalJalSeva meets the objectives of the Jal Jeevan Mission launched by the Department of Drinking Water & Sanitation (DDWS), which aims to "provide safe and adequate drinking water through individual household tap connections by 2024 to all households in rural India." The solution empowers the village communities with the ease of consumer management, billing, collection, expense management and monitoring water supply schemes.

The NalJalSeva mobile app enables rural local bodies to manage revenue and expenditures related to water supply projects. It is designed for water management committee members and collection agents. The collection agents can add consumers (or households) and generate bills and receipt acknowledgements. The app provides an intuitive interface for users at the local governance level along with insightful dashboards for effective decision-making.

Features

NalJalSeva offers multiple features required to manage revenues and expenditures (listed below).

• Create and maintain household registers

• Collect payments

• Download bills & receipts

• Add and update expense records

• Generate demands and bills

• Create and edit consumer details

• Access insights through rich dashboards

Section Overview

This section contains all docs and information required to understand NalJalSeva, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the NalJalSeva app.

• Technology

• Architecture

• Demo Video

• Configuration Docs

• User Manual

Navigation Tips

• Click on the embedded links within the content to browse topic details

• Use the contents links available on the right side of the screen to move to a specific heading

• Find the list of Related Docs links at the bottom of each page to browse through additional product details

Contact Us

Overview

The View Consumer screen allows users to view the consumer details and linked information.

Design & Workflow

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

The View Consumer screen contains all information related to household

The static household 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

Workflow

1. If the bill is not generated (Post rollout until the first month), only the data card is shown, and no action is required.

1. Once the first demand is generated, a new consumer bill/card will be generated, and the following data points and actions will be displayed.

• 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 can 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.

1. 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 - Download the receipt in the Revenue Collector's 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 the receipt PDF

NalJalSeva is an app-based solution designed for rural water governance and financial management. It supports local governance by providing tools to support consumer management, billing and collection added to financial reporting.

The solution enables the governance bodies to maintain financial records following established procedures and practices.

Key Features Of Nal Jal Seva

The solution offers an end-to-end solution for managing rural water supply schemes, focusing on maintaining transparency and simplifying financial transactions. It enhances governance and simplifies tasks for local authorities while ensuring accountability.

Click on the links below to explore the NalJalSeva workflows:

Overview

Users can check the configured Water Charge details in the dashboard for the selected tenant/Scheme.

Design & Workflow

Users can click on the VWSC and Water Charges Info card on the home page to view the tabulated rate information details.

Overview

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

Design & Workflow

The section provides specific screen design and configuration details below.

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 and Assamese are the supported languages with English as the default language. Localization in the screens is displayed based on the language selected.

User ID and Password Entry

On the login screen -

1. Enter the user ID, which is the registered mobile number of the user

2. Enter the system-generated password. Click on the Continue button to log in.

Forgot Password

Click on the Forgot Password link on the login screen. This navigates the user to the password reset screen.

Enter the registered Mobile Number and the OTP received on the mobile number.

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.

Overview

All Gram Panchayats have a monthly billing cycle for water charges. The generate bulk demand feature schedules the system to generate demand and raise bills for non-metered connections.

Design & Workflow

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 based on the roles.

   • Details of Notification -

     • “Demand for dd/MM/YYYY - dd/MM/YYYY has been raised. X bill (s) has been raised and sent to <X/TotalConsumer>households"

   • Details of SMS Notification

     • “Dear, Demand for Billing Cycle 01/10/2024-31/10/2024 has been generated for Testing. Kindly plan for the collection of Water Charges for this period - https://naljalseva.jjm.gov.in/assam/mgramseva/home. DWSS JJM Assam

4. Each non-metered household gets notifications -

   • SMS Notification with Bill PDF

     • 'Dear, a new water bill for Billing Cycle 1/10/2024 - 31/10/2024 has been generated for Consumer ID for Rs.30.0. Click to download the latest bill. DWSS JJM Assam.

   • SMS notification with a payment link -

     • This is disabled as of now we can enable or disable sms in

     • 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. "Generate Bill"

   • 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.

To explore the Demand Generation Logic refer to Bulk Demand Generation for Non-Metered.

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.

Last Bill Month of demand generated - Once the demand is generated for any connection it falls under this category and it shows the number of consumers by month whose demand is generated for that month Last Bill Month of demand not generated - When we create a consumer and we have not generated even one demand that consumer will fall in this category. It will show the number of consumers month-wise for whom demand is not generated. We also provide the option to see the consumer list and edit screen from there for whom not a single demand is generated in the system.

Successful demand generation -

Overview

The Update Consumer screen allows users to edit and update consumer information and details.

Design & Workflow

Users can search for the consumers using -

1. Consumer mobile number

2. Name of the consumer

3. New connection ID

The user details are fetched based on the input search criteria.

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 to the Consumer Edit Screen from the search screen or the search results screen (Case when multiple search results are displayed).

• 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 - A 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.

Overview

The SMS notification feature triggers messages to users for specific events and updates.

Design & Workflow

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

Overview

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

Design & Workflow

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

1. Clicking “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, water bill for 1 - 30 has been generated for consumer ID for Rs. 250. Click attached as PDF”

To find details on Demand Generation Logic refer to the Demand/Bill Generation for metered connection.

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 the user has the option to change it.

Overview

The Add Expense feature enables users to add expense details.

Design & Workflows

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

Expense Types

On selecting the option “Add Expense Record” from the list of tiles/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 digits running seq No>”

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

Overview

The update expense feature allows users to modify and update expense details.

Design & Workflows

Expense modification is allowed based on the status of the payment as highlighted in the scenarios below.

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”.

Overview

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

Design & Workflows

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

The login, reset and forgot password feature enables users to access the HRMS application.

Design & Workflows

On successful User/employee Creation, the users receive a link via SMS. Clicking on this link redirects the users to the login page of the HRMS app. The users can log in from this screen or even reset their password in case they are logging in for the first time.We also Provide Forget password option in 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 and Assamese are the supported languages with English as the default language. Localization in the screens is displayed based on the language selected.

User ID & 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.

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

State Admin

Block Admin

Upon selection of the scheme the user is mapped to -

Forgot Password

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

Overview

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

Design & Workflows

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

Users can -

• Change Language

• Edit profile

• Logout

Changing language changes localization as per standards

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 the 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 confirmed 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

The View Household Register enables users to view household details.

Design & Workflow

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

View Consumer Ledger Report

Once you click on the ledger report of the consumer it opens the below screen -

Select the financial year and click on View to view a report of that financial year or Download to download the report of the selected year.

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

Overview

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

Desgin & Workflow

Users can see the consumer billing information on the screen.

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

1. 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.

1. 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

1. User Actions

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

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

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

1. SMS to Household

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

  • 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 can leave a review for water charges. Refer Feedback - Post Payments

Details on the card

• When an online payment method is selected, the “Collect Payment” option is disabled. Since the household 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 View Tabular Dashboard for expenses provides a view of all expenses incurred during the month.

Design & Workflows

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.

Overview

Employee can be searched by name, employee ID and Number.

Design & Workflows

State User search Employee Search by name, employee ID and Number.

Block-based search is available for state users.

Search based on employee status

Block User Search Employee

Search Employee By name, employee ID and Number.

The search screen will show the below details

1. Employee Id

2. Employee Name

3. Mobile Number

4. Type of user

5. Designation

6. Status

Role-based search is also available for block users -

We have search option for inactive/ active users -

Overview

State/Block employees can search all employees across the state/block.

Design & Workflows

State User

State users have to select the applicable block to search for the employee in that block.

State users can select one role or select all roles to see all users in the selected block.

Further, the drill-down state user can select the concerned panchayat in the block along with the concerned scheme in that block. If nothing is selected it includes all panchayat and scheme within the block.

Block User

Block Users can search all employees under the block he/she is mapped to. To search user click on “Search Department User”.

Once clicked -

The block user can select the Panchayat within the block to which the employee is mapped.

Users can further drill down to the scheme once they select a panchayat. It will display the list of schemes under the selected panchayat.

Block users can select roles in the roles dropdown field. Users can select all or select concerned roles.

The search result can be downloaded/viewed on the screen.

Visible details of Employee

1. EmployeeID

2. Employee Name

3. Type Of user

4. Designation 5.Mobile Number

5. Status

6. Scheme

Overview

Only Block Users can update the rate master of a Scheme.

Design & Workflows

Make sure in the dropdown of the block, the user selects the concerned scheme to modify.

Once clicked on “rate master” it will redirect to the rate master screen.

A list of Rate masters can be seen in different configurations -

1. Residential / non-metered

2. Residential / metered

3. Commercial / non-metered (not used in Naljal yet)

4. Commercial / Metered (not used in Naljal yet)

5. Public Sector / Non-metered (not used in Naljal yet)

6. Public sector/ Metered (not used in Naljal yet)

7. Mixed / Metered (not used in Naljal yet)

8. Mixed / Non-metered (not used in Naljal yet)

Edit Existing Rate Master

Click on the rate master configuration you want to edit/disable.

Click on edit.

Edit Non-metered Residential Rate

Edit Metered Connection

Data Points

“From” is the starting of unit “To” is end of unit “Rate” is rate defined within that slab

For example if from is 0 and to is 5 and rate is 5 . consumer 3unit than the rate Will be 3*5= 15 rs

Add Rate Master

By default, state configuration is shown in the rate master if no rates are defined for a particular tenant. How to know this

If you try to edit the rate master shown it will throw you an error.

Building Type

Connection Type

Calculation Attributes

Overview

Only Block Users can update the Penalty Master of a Scheme.

Design & Workflows

Ensure the user selects the correct scheme to modify from the Scheme dropdown.

Edit Existing Penalty master

Click on the Penalty Master configuration you want to Edit/Disable.

Data Points:

Rate -> In percentage 10 means 10%, 20 Means 20% of the water charge configured Type -> fixed Amount -> Not required From FY -> 2023-24 Subtype -> Current Month Minimum amount -> not required Flat amount -> not required (it is used for a flat amount of Penalty) Starting Date -> From the date the penalty ID is applicable Applicable After days -> days after demand generation the penalty is applicable

Add Penalty Master

Overview

The Create Employee feature in the HRMS application enables users to add employee details.

Design & Workflows

State User Creation

State user is created the very first time with the desired Role as STATE_ADMIN, HRMS_ADMIN, MDMS_ADMIN Using API of create Employee in Egov-hrms.

Create Block Users

Click on “Create Block user” and add the employee details.

Once created the Employee Creation Successful Screen is deployed it generates a unique Employee Code.

The employee gets a message to log in with one-time login credentials.

“Dear, You've been invited to mGramSeva Application of Assam. Please login using https://naljalseva.jjm.gov.in/uat/mgramseva/login. Username: Password:”

Block users can log into HRMS and Create Other field Users, namely Revenue Collector, Chairmen or Secretary.

Create Field Users

Homepage of Block Users - Block users can select the scheme from the dropdown list and add field users to the selected scheme.

Click on Create Employee to create the field Employee.

By default, the selected scheme in the dropdown will be preselected in the jurisdiction details. This is the primary scheme meaning you cannot remove this scheme from the user once it is created Block User can add other schemes to the same Employee by clicking on Add Jurisdiction.

The below screen is displayed upon successful creation of user -

A message will trigger to the employee with a one-time login credentials -

“Dear , You've been invited to mGramSeva Application of Assam. Please login using https://naljalseva.jjm.gov.in/uat/mgramseva/login. Username: Password:”

Overview

Employee details can be updated using the Edit employee details option.

Design & Workflows

State users - can edit block user details

Block users - can edit field user details

Search user by name (Fuzzy search) , Mobile number or Employee ID

Block user can also search user by roles.

Click on the user you want to edit.

Click on take action Button to edit the user.

The options on the action button can be used to Deactivate / Edit the employee.

Deactivate Employee

Fill in the required details and deactivate the user.

Activate User

Activate an deactivated employee.

Edit Active User

Other details can be modified.

Overview

The view and download reports feature enables users to generate and download different types of reports linked to consumers, vendors, expenses, collections and ledgers at various levels.

Design & Workflows

Report Dashboard

Select the Financial year for which you want to see the report.

Billing Cycle - Select the billing cycle month for the applicable financial year.

Select the applicable report option to view or download specific reports.

Bill Report

This report consolidates the details of bills consumer-wise for the selected month.

Details

1. Consumer Id

2. IMIS/OLd Connection Number

3. Name

4. Created date 5.Penalty

5. Advance

6. Total Amount

Collection Report

Details

1. Connection Id

2. IMIS/OLd Connection Number

3. Name

4. Payment Method

5. Amount

Inactive Consumer Report

Details -

1. Connection ID

2. Name

3. Inactivation Date

4. Inactivated by

Expense Report

Details -

1. Connection Id

2. Name Of payee

3. Amount

4. Bill Registered Date

5. Expense From

6. Expense To

7. Application Status

8. Paid Date

9. Has Attachment

10. Canceled time

11. Cancelled By

Monthly Ledger

Details:

1. Connection Id

2. Sr no.

3. Old Connection Id/IMIS no

4. Consumer Name

5. Consumer Entered Date

6. Previous Outstanding last Month (If Any)

7. Advance amount Received (if Any)

8. Bill generated for the month

9. Date of bill generated

10. Total Amount

11. Amount collected against total amount

12. Date of Amount collected

13. Remaining amount to be collected

Vendor Report

Details -

1. Bill Id

2. Name Of payee

3. Mobile Number

4. Type of Expense

Introduction NalJalSeva

NalJalSeva is a standalone app-based module that enables the GPWSC committee to create new consumers, generate demand, collect revenue, record expenditure transactions etc.

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

Follow the step-by-step (links below) guide to use the app:

Overview

The state dashboard option is available to State Users logged in to HRMS.

Design & Workflows

Clicking on the State dashboard option displays the state dashboard in Kibana.

The screen provides options to select the date range for which you want to see the data. Further, there is a drill down where we can select districts, blocks, panchayat and schemes as well.

Overview

State Users logged into HRMS have the option to view the Rate Dashboard.

Design & Workflows

Here we can see the rate dashboard which shows the rate configured for each scheme.

Overview

The Rollout Dashboard option is available to all State Users.

Design & Workflows

This is the dashboard that gives you a view of the total connections across active users and the total demand generated across the whole state.

Here we have options to select the date range within which you want to see the data. Further, there is a drill down where we can select districts, blocks, panchayat and schemes as well.

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

Enter the registered mobile number. Enter the system-generated password. Click on the Continue button to log in.

Forgot Password

Click on the Forgot Password link on the login screen. This navigates the user to the password reset screen.

Enter the registered Mobile Number and the OTP received on the mobile number.

Enter the new password and confirm the new password. Click on the Change Password button to change the password. Follow the Password Hint details given on the screen to structure the password.

This redirects the user to the home page containing the cards to relevant NalJalSeva functionalities available for the mapped user role.

Users can -

Change Language

Click on the user icon on the top section of the screen. Click on the applicable Language option to localise the application. The supported languages are Assamese and English, where English is the default language.

Edit Profile

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.

Click on the Save button to save the changes.

Change Password

Click on the Change Password button to change the password.

Enter the Current Password. Set a new password and confirm the new password. Follow the password hints given on the screen to set the password.

Click on Change Password to save the new password.

Logout

Click on the Logout button to logout from the application.

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, the 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.

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, and Party Bill Date. Select Yes or No to indicate if the bill is paid or not. Click on the 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.

The journey of PFM Mission in Punjab began in January 2021 with signing of a tri party MoU among The Department of Governance Reforms and Public Grievances (DGR & PG), the Department of Finance (FD), Punjab, and eGov Foundation to provide a systemic solution to enhance public finance management in the state.

The pilot was agreed to be carried out in the Department of Water Supply and Sanitation (DWSS).

Multiple learning sessions with the DWSS officials were conducted to gain in-depth knowledge on current processes and systems, pressing challenges, and how the Mission can design potential solution(s) to the identified problem/s. After these discussions, the following problem statement was identified:

Visibility into financial sustainability of GPWSC run schemes:

• The water charges (funds) collected by the GPWSC for their schemes and expenditures made thereof are not visible to the DWSS or the Department of Finance (FD)

• Such transparency is necessary since DWSS funds the asset creation and provides for O&M and electricity charges shortfall of GPWSC, if any

To solve the above problem statement, eGov Foundation in consultation with the DWSS, Government of Punjab, identified Anandpur Sahib (APS) as the pilot division to implement mGramSeva. mGramSeva, a mobile application, envisions to capture all the Revenue and Expenditure details in digitized format which will bring in accountability and transparency of GPWSC funds, as well as enable and empower frontline leaders of the Panchayats.

The mGramSeva solution adoption highlights are given below:

1. In APS division there are more than 76 schemes and 100 villages which are GPWSC run schemes, for which the water bills are generated manually

2. No automated or digital system currently in place to notify the household through SMS for bills generated

3. Manual recording all the receipts and expenses in cash book

4. Sarpanch does not have access to real time information on collection and expenditure

5. Household information records are maintained manually

Install AWS. Follow the subsequent steps to begin the setup of NalJalSeva.

Overview

This page provides step-by-step details on setting up a git repo for code, configs, V1 MDMS, and Infra As Code.

Steps

Fork the following repos that contain the master data and default configurations. Customize the data (master data, ULB, Tenant details, Users, etc) as per specific implementation requirements in the respective GitHub organization accounts.

Follow the steps given below to set the git repository,

• ​Fork both the MDMS, and config repos into your GitHub organization account.

• Create a GitHub user account, and generate an SSH authentication key (generate a new SSH key and add it to the above user account.

• Enable new GitHub users to access the forked repos.

• Add the ssh private key generated in the previous step to the egov-demo-secrets.yaml within the git-sync section.

• Update the services in the git-sync repository by specifying the forked repository and branch in the egov-demo.yaml file.

/DIGIT-DevOps/config-as-code/environments/egov-demo-secrets.yaml

• Update the deployment configuration details for the below as per your specifications:

  1. Number of replicas/scale of each service (depending on whether dev or prod load)

  2. You must update the SMS gateway, email gateway, and payment gateway details for the notification and payment gateway services, etc.

  3. Update the config and MDMS GitHub repos wherever marked.

  4. Update GMap key (In case you are using Google Map services in your PGR, PT, TL, etc)

  5. Create one private S3 bucket for Filestore and one public bucket for logos. Add the bucket details respectively and create an IAM user with the s3 bucket access. Add IAM user details to <env-secrets.yaml>.

  6. URL/DNS on which DIGIT will be exposed.

  7. SSL certificate for the above URL.

  8. Any specific endpoint configurations (Internal/external).

/DIGIT-DevOps/config-as-code/environments/egov-demo.yaml

Overview

This page provides the steps to follow to create a Git account in the client name.

Steps

To create a Git account in the client name, follow the steps below:

1. Register the client on a Git hosting platform such as GitHub, GitLab, or Bitbucket by providing their email address, choosing a username, and setting a secure password.

2. Once the account is set up, they can start using Git to manage their code repositories and collaborate on software development projects with ease.

We currently use the free Let's Encrypt SSL certificate, which is valid for 90 days and must be manually renewed afterwards. There are also several paid SSL certificate options available globally.

Overview

To enable any municipal service in a fresh environment and for the first time, we require a basic idea of what DIGIT does and the generic services required to set it up.

DIGIT is an open-source, customizable platform that lends itself to extensibility. New modules can be built on top of the platform to suit new use-cases or existing modules can be modified or replaced. To enable this, in addition to deploying DIGIT, a CD/CI pipeline has to be set up. CD/CI pipelines enable the end users to automate & simplify the build/deploy process.

Find more details on DIGIT and platform deployment here.

Core Services

DIGIT platform comprises several core services that serve as the platform backbone. Some of the key core services are listed below:

1. Workflow Service

2. Location Service

3. User Service

4. Access Control Service

5. PDF Service

6. Payment Service

7. MDMS Service

8. Indexer Service

9. Persister Service

10. ..among multiple others

Each microservice has a distinct function explained in the provided documentation links.

Developers can activate specific municipal services easily once the platform and its terminologies are well understood.

Overview

This page provides step-by-step instructions for using a Python script to create consumers for NalJalSeva. Follow these guidelines to load consumer data into the system using the Python script provided.

Steps

Step 1: Prepare Excel Sheet

Before running the script, ensure you have a properly formatted Excel sheet. The sheet should include the following columns:

• Consumer Name (Mandatory, use "NA" if not available)

• Gender (Male/Female)

• Father Name (Mandatory, use "NA" if not available)

• Mobile Number (Mandatory)

• Old Connection Number

• Property Type

• Service Type (till now we have Non-metered only for data loading)

• Ward (Always set to "Ward 1")

• Meter Reading (If available, use the provided date; otherwise, default to "12/01/2022")

• GPWSC Name

• Arrears

• Previous Reading ((if arrears and previous reading are not given, write '0')

Ensure the format of the meter reading matches the provided sample format given in the Excel file below, as incorrect formatting may lead to loading failures.

Step 2: Python Script Configuration

Edit the Python script with the following details:

• Set the host URL based on whether it's for production, QA, or UAT.

• Provide the username and password corresponding to your host URL.

• Specify the path where your Excel file is stored. It is recommended to store the Excel file in the same location as your Python script.

Step 3: Running the Script

Execute the Python script after configuring the host URL, username, password, and file path. The script will load data into mGramSeva based on the information provided in the Excel sheet.

Step 4: Post-Execution Steps

Do not open the Excel file until the script completes its task. After completion, open the Excel file to check the status. The status will indicate whether the operation was successful or if there was a failure. If there's a failure, refer to the reason for further investigation and resolution.

6KBConsumers.xlsx

13KBloadConsumer-uat.py

Overview

This page provides a clear and concise guide for automating user creation in NalJalSeva. It allows you to efficiently create users and manage their roles in the system.

Follow the steps provided on this page to create users for NalJalSeva using a Python script. The process involves preparing an Excel sheet with user information, configuring the Python script, and executing it.

Pre-requisites

1. Python script for creating users for NalJalSeva.The sample format of the Python script is attached below.

2. Excel sheet containing user data. The sample format of the Excel sheet is attached below. Make sure to populate the data in the same format.

   • Columns: tenant name, mobile no, father name, gender, date of birth (dd/mm/yyyy), type, and ward (fixed to "ward 1").

   • Types: Sarpanch, Secretory, Revenue Collector, Division User or State User

   • Roles for Sarpanch: COLLECTION_OPERATOR, EXPENSE_PROCESSING, BULK_DEMAND_PROCESSING, DASHBOARD_VIEWER, GP_ADMIN.

   • Roles for Secretory: EXPENSE_PROCESSING, BULK_DEMAND_PROCESSING, DASHBOARD_VIEWER, GP_ADMIN, COLLECTION_OPERATOR.

   • Roles for Revenue Collector: COLLECTION_OPERATOR, DASHBOARD_VIEWER.

   • Roles for Division User: HRMS_ADMIN, DIVISION_ADMIN

   • Roles for State User: HRMS_ADMIN, STATE_ADMIN

Steps

1. Prepare the Excel Sheet:

   Create an Excel sheet with the following columns and data in the given format:

   • Tenant Name (in lowercase)

   For State User tenant name will be pb

   • Mobile Number

   • Father's Name (Mandatory, use "NA" if not available)

   • Gender (M/F - this data is mandatory)

   • Date of Birth (in the format dd/mm/yyyy)

   • Type (Sarpanch, Secretory, Revenue Collector, Division User or State User)

   • Roles - Based on the User Type, set corresponding roles:

     • Sarpanch: COLLECTION_OPERATOR, EXPENSE_PROCESSING, BULK_DEMAND_PROCESSING, DASHBOARD_VIEWER, GP_ADMIN

     • Secretary: EXPENSE_PROCESSING, BULK_DEMAND_PROCESSING, DASHBOARD_VIEWER, GP_ADMIN, COLLECTION_OPERATOR

     • Revenue Collector: COLLECTION_OPERATOR, DASHBOARD_VIEWER

     • Division User: HRMS_ADMIN, DIVISION_ADMIN

     • State User: HRMS_ADMIN, STATE_ADMIN

   • The 'Boundary' should be set to "Ward 1" as per mGramSeva standards.

2. Run the Python Script:

   • Open the Python script.

   • Provide the following information within the script:

     • Host URL: Specify the target environment (prod, qa, or uat).

     • Username and Password: As per your host URL.

     • Path to the Excel file: Ensure the Excel file is in the same location as the script.

   • Execute the script.

3. Post-Execution:

   • Do not open the Excel file until the script has completed its task.

   • After the script finishes, open the Excel file to review the results.

   • The Excel file will contain two columns:

     • User ID: If successful, the ID will be present.

     • Status: Will indicate either "Success" or "Failure." If failed, the reason for failure will be provided.

6KBupdated-user.xlsx

10KBonBoarding.py

This page provides step-by-step instructions for creating a consumer in the mGramSeva system using two API calls. The first API call is to create a property, and the second API call is to make a connection for the consumer.

Pre-requisites

Before proceeding with the given tasks, ensure the following prerequisites are met:

1. Authentication Token (authToken): Obtain a valid authentication token for the desired environment. This token is necessary to authenticate and authorize your requests.

2. API Endpoints: Ensure you have access to both APIs required for creating a property and a consumer. Make sure you have the correct API documentation or information about the endpoints, request payloads, and any required headers.

3. Postman: If you don't have Postman installed, download and install it. Import this collection in Postman. Make sure you change the URL as per your requirements.

Steps

Follow the steps given below to create consumers using either Property Create API or Consumer Create API.

Property Create API

Here's a step-by-step guide:

1. Locate the Property Creation API:

   • Open the Postman collection you imported.

   • Find the request corresponding to the Property Creation API. It might be named something like "Create Property" or similar.

2. Set Request Parameters:

   • Review the request parameters for creating a property.

   • For metered connections, provide values for initialMeterReading, meterReading, meterId, and previousReading. Set them to null if not applicable.

   • Set ConnectionType to "Metered" for metered connections and "Non_Metered" for non-metered connections.

   • Ensure that oldConnectionNo is unique every time you create a property.

3. Execute the Request:

   • Click on the "Send" button to execute the request.

   • Review the response to confirm that the property has been created successfully.

4. Copy Property ID:

   • In the response, you should find the propertyId field. Copy the value of propertyId as this will be needed for subsequent steps.

Now, you have successfully created a property, and you have the propertyId copied for future use. Ensure to follow any additional instructions provided in the Postman collection or the API documentation.

Consumer Create API

Follow the steps below to create a consumer using the Consumer Creation API from the Postman collection:

1. Locate the Consumer Creation API:

   • Open the Postman collection.

   • Find the request corresponding to the Consumer Creation API. It may be named "Create Consumer - Metered" for metered connections or "Create Consumer - Non-Metered" for non-metered connections.

2. Set Request Parameters:

   • Review the request parameters for creating a consumer.

   • For metered connections, provide values for initialMeterReading, meterReading, meterId, and previousReading. Set them to null if not applicable.

   • Set ConnectionType to "Metered" for metered connections and "Non_Metered" for non-metered connections.

   • Ensure that oldConnectionNo is unique every time you create a consumer.

   • Use the propertyId obtained from creating the property as instructed in the previous step.

3. Execute the Request:

   • Click on the "Send" button to execute the request.

   • Review the response to ensure that the consumer has been created successfully.

By following these instructions and providing the necessary details, you should be able to successfully create a consumer with a property and connection in the NalJalSeva system. Ensure that you follow any additional guidelines or instructions provided in the Postman collection or API documentation.

Overview

Follow the steps provided on this page to create and add users on the mGramSeva platform once the installation is complete.

Pre-requisites

Ensure the Postman utility is installed to run the following scripts. If not, Install Postman on the local machine.

Create Users - Steps

There are two methods to create users - either through API or through port-forwarding. To create users through port-forwarding refer here.

Follow the steps given below to create different types of users through the API.

There are primarily three different types of users as listed below:

• Super User

• Anonymous User

• System User

Super User - A superuser is a privileged user account with elevated access rights in a computer system or application. It is typically reserved for administrators or trusted personnel and grants them full control and unrestricted access to all system resources. Superusers are necessary to manage and maintain the system, perform critical tasks, and troubleshoot issues efficiently.

A Superuser is created using the createnovaildate API. Below is the curl given for creating a superuser.

Steps to follow:

1. Import the curl given below in Postman.

2. Refresh the authorisation token.

3. Provide User data as per requirements. This API will create a Super User in production. To add users in any other environment change the URL.

curl --location 'https://mgramseva-dwss.punjab.gov.in/user/users/_createnovalidate' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJQQVlIQWZ1YXpiRFpadlVGdEJSdmFQOWxYaHROXzBUS2FzdUpxZWl3bW04In0.eyJleHAiOjE2NDA0MTM1MjMsImlhdCI6MTYzNzgyMTUyMywianRpIjoiZTZiNmQyNmQtY2EwYS00MDZmLTgxZGYtYTNiOTE0NGEzYTQ3IiwiaXNzIjoiaHR0cHM6Ly9pZml4LXVhdC5wc2Vncy5pbi9hdXRoL3JlYWxtcy9pZml4IiwiYXVkIjoiYWNjb3VudCIsInN1YiI6ImJhMDE1OGFiLWZlYTMtNDc5NC04ZDE3LTRiYjc4MjFhZmM2NyIsInR5cCI6IkJlYXJlciIsImF6cCI6ImlmaXgtdWF0IiwiYWNyIjoiMSIsInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIiwiZmlzY2FsLWV2ZW50LXByb2R1Y2VyIiwiZGVmYXVsdC1yb2xlcy1pZml4Il19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJlbWFpbCBwcm9maWxlIiwiY2xpZW50SG9zdCI6IjE5Mi4xNzIuMzIuODYiLCJjbGllbnRJZCI6ImlmaXgtdWF0IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJ0ZW5hbnRJZCI6InBiIiwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LWlmaXgtdWF0IiwiY2xpZW50QWRkcmVzcyI6IjE5Mi4xNzIuMzIuODYifQ.Wemcw5vLajX77GnHJmLq3-NhoEaBcySUyNQCpzfglBojTfF9-7xTk7ripf-VxlR3H5AsULIOsw1vRjTW255_3v-MwlYgRML4YE-d-Bt54v1SVnZ77NQsGRmmZ2UQ4wTwIhYQi2jaqzfTeAdU0fJAQTqo7POpTUcChTz_L6O7MQbVVpDJ3BRoWa5XX-BE6MYqZR1tBrLimvJEUWneohUEpPNncszmUAKEZkhEaiUhh8AzSJA3KtP18JOFC8KOCi7ErL-Vf-bJ928tpsNOMmFM2Syjxnqwu2rHE1ZPLdPUxGt6PGI9oJR7PEShakne0p9Fx-PLP8NxCPFCErq87U6zag' \
--data-raw '{
    "RequestInfo": {
        "api_id": "1",
        "ver": "1",
        "ts": null,
        "action": "create",
        "did": "",
        "key": "",
        "msg_id": "",
        "requester_id": "",
        "authToken": "7d2b5b4f-6053-4633-941c-d30d67bc52b8",
        "token_type": "bearer"
    },
    "User": {
        "userName": "9399998206",                
        "name": "Test",
        "gender": "male",
        "mobileNumber": "9399998206",
        "active": true,
        "type": "EMPLOYEE",
        "tenantId": "pb",
        "password": "eGov@123",
        "roles": [
            {
                "name": "Super User",
                "code": "SUPERUSER",
                "tenantId": "pb"
            }
        ]
    }
}'

The parameters - userName, name, gender, mobileNumber, tenantId, and password can be changed as per requirements.

Anonymous User -An anonymous user is a generic or unauthenticated user account that does not require login credentials to access certain parts of a system or website. These accounts are essential for providing basic access to public information or services without requiring user registration. They are commonly used to ensure accessibility for a wide audience and encourage user interaction while preserving user privacy. These are used when the system is accessing non-authentication links such as bills and payment receipts.

Creating an anonymous user is the same as creating a superuser. The only difference is to change the name and code in roles. The API below is used to create an Anonymous User in production.

curl --location 'https://mgramseva-dwss.punjab.gov.in/user/users/_createnovalidate' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJQQVlIQWZ1YXpiRFpadlVGdEJSdmFQOWxYaHROXzBUS2FzdUpxZWl3bW04In0.eyJleHAiOjE2NDA0MTM1MjMsImlhdCI6MTYzNzgyMTUyMywianRpIjoiZTZiNmQyNmQtY2EwYS00MDZmLTgxZGYtYTNiOTE0NGEzYTQ3IiwiaXNzIjoiaHR0cHM6Ly9pZml4LXVhdC5wc2Vncy5pbi9hdXRoL3JlYWxtcy9pZml4IiwiYXVkIjoiYWNjb3VudCIsInN1YiI6ImJhMDE1OGFiLWZlYTMtNDc5NC04ZDE3LTRiYjc4MjFhZmM2NyIsInR5cCI6IkJlYXJlciIsImF6cCI6ImlmaXgtdWF0IiwiYWNyIjoiMSIsInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIiwiZmlzY2FsLWV2ZW50LXByb2R1Y2VyIiwiZGVmYXVsdC1yb2xlcy1pZml4Il19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJlbWFpbCBwcm9maWxlIiwiY2xpZW50SG9zdCI6IjE5Mi4xNzIuMzIuODYiLCJjbGllbnRJZCI6ImlmaXgtdWF0IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJ0ZW5hbnRJZCI6InBiIiwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LWlmaXgtdWF0IiwiY2xpZW50QWRkcmVzcyI6IjE5Mi4xNzIuMzIuODYifQ.Wemcw5vLajX77GnHJmLq3-NhoEaBcySUyNQCpzfglBojTfF9-7xTk7ripf-VxlR3H5AsULIOsw1vRjTW255_3v-MwlYgRML4YE-d-Bt54v1SVnZ77NQsGRmmZ2UQ4wTwIhYQi2jaqzfTeAdU0fJAQTqo7POpTUcChTz_L6O7MQbVVpDJ3BRoWa5XX-BE6MYqZR1tBrLimvJEUWneohUEpPNncszmUAKEZkhEaiUhh8AzSJA3KtP18JOFC8KOCi7ErL-Vf-bJ928tpsNOMmFM2Syjxnqwu2rHE1ZPLdPUxGt6PGI9oJR7PEShakne0p9Fx-PLP8NxCPFCErq87U6zag' \
--data-raw '{
    "RequestInfo": {
        "api_id": "1",
        "ver": "1",
        "ts": null,
        "action": "create",
        "did": "",
        "key": "",
        "msg_id": "",
        "requester_id": "",
        "authToken": "7d2b5b4f-6053-4633-941c-d30d67bc52b8",
        "token_type": "bearer"
    },
    "User": {
        "userName": "9399998206",
        "name": "Test",
        "gender": "male",
        "mobileNumber": "9399998206",
        "active": true,
        "type": "EMPLOYEE",
        "tenantId": "pb",
        "password": "eGov@123",
        "roles": [
            {
                "name": "anonymous",
                "code": "ANONYMOUS",
                "tenantId": "pb"
            }
        ]
    }
}'

System User - Creating a system user is the same as creating a superuser and anonymous user. The only difference is to change the name and code in roles.

This page provides a comprehensive guide on using the CreateNovaildate API to create users with specific roles based on their responsibilities within the system. Adjust the parameters and roles as needed for your specific requirements.

Steps

The CreateNovaildate API allows users to create a new user with specified details that include username, name, gender, mobile number, activation status, user type, tenant ID, and password. Refer to the Request Parameters details available below.

Additionally, users can be assigned specific roles based on their responsibilities.

Request Parameters

1. username (string): User's unique username.

2. name (string): Full name of the user.

3. gender (string): Gender of the user.

4. mobileno (string): User's mobile number.

5. active (boolean): User's account status (true for active, false for inactive).

6. type (string): It will be EMPLOYEE only.

7. tenantid (string): User's tenant ID.

8. password (string): User's password.

9. Roles: Roles determine the permissions and responsibilities assigned to a user.

The available roles are as follows:

Roles for Sarpanch

• COLLECTION_OPERATOR

• EXPENSE_PROCESSING

• BULK_DEMAND_PROCESSING

• DASHBOARD_VIEWER

• GP_ADMIN

Roles for Secretary

• EXPENSE_PROCESSING

• BULK_DEMAND_PROCESSING

• DASHBOARD_VIEWER

• GP_ADMIN

• COLLECTION_OPERATOR

Roles for Revenue Collector

• COLLECTION_OPERATOR

• DASHBOARD_VIEWER

Roles for Division User

• HRMS_ADMIN

• DIVISION_ADMIN

Roles for State User

• HRMS_ADMIN

• STATE_ADMIN

To assign roles to a user, include the desired roles in the roles section of the request. PROFILE_UPDATE role is available for every user to update existing roles.

This documentation outlines the process of setting up a new tenant in MDMS (Master Data Management System). To achieve this, it involves cloning the MDMS repository locally and utilizing a Python script that interacts with an Excel file containing essential information for the new tenant setup.

Pre-requisites

1. Clone the MDMS repository to your local machine.

2. Have the Excel file ready for reference. The structure of the Excel file is critical, and any changes must align with the specified columns. The reference to the Excel file is given below.

Steps

Python Script Configuration

1. Locate the Python script for adding a new tenant. The script can either be placed in the "tenants" folder locally or specify the full path where your "tenants.json" folder is present within the script.

2. Open the script and edit the following lines to match your requirements:

   Copy

   dataframe = openpyxl.load_workbook("Book2.xlsx")

   Replace "Book2.xlsx" with the name of your Excel file containing tenant information.

3. Specify the sheet name in your Excel file where the required data is stored.

   Copy

   dataframe1 = dataframe["Sheet1"]

Excel File Preparation

1. Ensure your Excel file adheres to the specified format. The columns must match the template provided, and any deviation may result in script failure.

2. Do not modify the column structure in the Excel sheet, as the script relies on a consistent format.

Running the Script

Execute the Python script after configuring it according to your needs. The script will process the Excel file, and upon completion, a new file named "tenants_new.json" will be generated.

Deploying to MDMS

• Copy the generated tenants_new.json file to the MDMS repository or select and apply the updated data within MDMS as needed.

5KBBook2.xlsx

3KBcreate_tenants_json_Book2.py

After creating a tenant in the tenants.json file we need to make a separate folder in MDMS for each tenant.

This page outlines the step-by-step process for using a Python script to change master rates for NalJalSeva in bulk. The script reads data from an Excel file, updates the master rates, and generates a new CSV file containing the modified information. Once the script is successfully executed, changes can be pushed to the local MDMS repository on GitHub.

Pre-requisites

• Python script

• MDMS repository cloned on the local system

• Excel file with tenant names, old master rates, and new master rates

Steps

1. Prepare Excel File:

• Ensure the Excel file contains three columns: Tenant Name (in lowercase), Old Master Rate, and New Master Rate.

• If the columns are not present, add them to the Excel file.

2. Clone and Create Branch:

• Clone the MDMS repository to your local system.

• Create a new branch from the branch where you intend to make changes.

3. Update Python Script:

• Open the Python script and locate the variables:

  • updatedfile: Provide the path to your Excel sheet.

  • localFilePath: Specify the path where your MDMS repository is cloned.

  • Identify the columns in the Excel file where the Tenant Name, Old Master Rate, and New Master Rate are stored. Update the script accordingly:

uniqueVillageName = row[2].value
oldMasterRate = row[7].value
newMasterRate = row[8].value

• Run the script.

4. Script Execution:

• Do not open the Excel file during script execution.

• The script will generate a new file named new_updated_file4.csv containing information about whether rates were updated or not.

5. Verification:

• Check new_updated_file4.csv to verify if all rates were updated successfully.

6. Push Changes to Git:

• If all rates are updated, the local changes will affect the MDMS repository.

• Raise a pull request and merge changes from the Git repository.

Follow the above steps to update NalJalSeva master rates in bulk, and ensure precise and streamlined changes to the MDMS repository.

9KBMaster Rate Tracking.xlsx

3KBChangeTariffOfVillage.py

Overview

Localization is the process of adapting a software application, website, or content to different languages and regions, making it accessible and user-friendly for diverse audiences. It involves translating text, adapting graphics, and configuring settings to suit a specific locale's cultural and linguistic preferences.

Search API For Localization In NalJalSeva

To retrieve localization messages in NalJalSeva, use the Search API given below. This API allows you to search for messages based on parameters like locale, tenantId, and apiId. Here is an example using cURL:

To search for messages in different languages and environments, you can customize the parameters such as locale (en_IN, hi_IN, pn_IN) and tenantId. Change the URL to search in any other environment. The current API is specific to the UAT environment.

curl --location 'https://mgramseva-uat.psegs.in/localization/messages/v1/_search?locale=en_IN&tenantId=pb' \
--header 'authority: mgramseva-dwss.punjab.gov.in' \
--header 'accept: */*' \
--header 'accept-language: en-GB,en;q=0.9' \
--header 'content-type: application/json; charset=utf-8' \
--header 'cookie: _ga=GA1.1.748766720.1676369982; _ga_DDHVQCKC6W=GS1.1.1676369981.1.0.1676369984.0.0.0' \
--header 'origin: https://mgramseva-dwss.punjab.gov.in' \
--header 'referer: https://mgramseva-dwss.punjab.gov.in/mgramseva/selectLanguage' \
--header 'sec-ch-ua: "Not_A Brand";v="99", "Google Chrome";v="109", "Chromium";v="109"' \
--header 'sec-ch-ua-mobile: ?1' \
--header 'sec-ch-ua-platform: "Android"' \
--header 'sec-fetch-dest: empty' \
--header 'sec-fetch-mode: cors' \
--header 'sec-fetch-site: same-origin' \
--header 'user-agent: Mozilla/5.0 (Linux; Android 10; SM-G981B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Mobile Safari/537.36' \
--data '{
    "apiId": "mgramseva",
    "ver": 1,
    "ts": "",
    "action": "_search",
    "did": 1,
    "key": "",
    "msgId": "20170310130900|en_IN",
    "authToken": "",
    "userInfo": null
}'

Upsert API For Localization In NalJalSeva

The Upsert API allows users to update or insert new localization messages into NalJalSeva. This involves refreshing the authentication token and providing details like code, message, module, and locale. Here is an example using cURL:

In this example, you can customize the "code," "message," "module," and "locale" parameters to specify the localization details you want to upsert. Make sure to update the authentication token for security purposes.

curl --location 'https://mgramseva-uat.psegs.in/localization/messages/v1/_upsert' \
--header 'Content-Type: application/json' \
--data '{
    "RequestInfo": {
        "apiId": "Mihy",
        "ver": "1.0",
        "ts": "",
        "action": "create",
        "did": "1",
        "key": "abcdkey",
        "msgId": "20170310130900",
        "requesterId": "",
        "authToken": "7d569ce1-4b5c-4f4c-be93-4af7265890f3"
    },
    "tenantId": "pb",
    "messages": [
         {
            "code": "CORE_DOWNLOAD",
            "message": "Download",
            "module": "mgramseva-common",
            "locale": "en_IN"
        }
    ]
}'

This page provides the steps to follow to create a workflow in NalJalSeva. Here is the reference to the DIGIT workflow service.

Follow the steps below to create a workflow in NalJalSeva.

Steps

Follow these steps to create a workflow in NalJalSeva:

1. Check Existing Workflow:

   • Utilize the provided Postman collection that includes workflow creation and search APIs.

   • Use the search API to check if the workflow for the specified state already exists.

2. Workflow Creation:

   • If the workflow is not present, proceed to create it using the create API.

   • Ensure to provide the necessary details in the userInfo section and give superuser information.

   • Adjust parameters like tenantId and roles according to your specific requirements.

3. Port Forwarding:

   • Execute port forwarding to the workflow service using the following kubectl command:

     Copy

     kubectl port-forward <pod-name> -n mgramseva

     Replace <pod-name> with the appropriate pod name.

4. Create Workflow:

   • After port forwarding, initiate the workflow creation process.

5. Search Through API:

   • Use the search API to verify that the workflow has been successfully created.

   • Adjust the search parameters as needed.

These steps ensure a smooth workflow creation process inNalJalSeva. Make sure to follow each step in sequence for a seamless experience.

This page provides details on how to register the SMS templates with the specified TEMPLATE ID for each Localization key and append the TEMPLATE ID at the end of the message in the Localization system.

Steps

To register the provided SMS templates with a specific TEMPLATE ID for each Localization key and append the TEMPLATE ID at the end of the message

The sample SMS messages in the table below have to be registered with a specific TEMPLATE ID (Eg.'100700746377980') for each Localization key.

Append the TEMPLATE ID at the end of the message.

Push the SMS templates in Localisation.

NalJalSeva's Master Data Management System (MDMS) is organized into several folders, each containing essential JSON files that define various aspects of the application's configuration. This documentation provides an overview of the key folders and their respective files, along with a description of the data contained within each file.

Steps

1. ACCESSCONTROL-ACTIONS-TEST

This folder contains the actions-test.json file, which defines various API endpoints along with their configurations.

{
  "id": 11,
  "name": "Employee Count",
  "url": "/egov-hrms/employees/_count",
  "parentModule": "egov-hrms",
  "displayName": "Employee Count",
  "orderNumber": 0,
  "enabled": false,
  "serviceCode": "egov-hrms",
  "code": "null",
  "path": ""
}

• id: Unique identifier for the API endpoint. Increase id with respect to id present in action-test.json file.

• name: Name of the endpoint.

• url: URL of the API endpoint.

• Other things : As per your specific requirements.

2. ACCESSCONTROL-ROLEACTIONS

This folder contains the roleactions.json file, which associates roles with action IDs.

{
  "rolecode": "HRMS_ADMIN",
  "actionid": 11,
  "actioncode": "",
  "tenantId": "pb"
}

• rolecode: Code representing the role

• actionid: Action ID associated with the role, linking to entries in actions-test.json

• actioncode: Additional code for the action if needed

• tenantId: Tenant ID associated with the role

3. ACCESSCONTROL-ROLES

This folder contains the roles.json file, defining roles in the system.

{
  "code": "ANONYMOUS",
  "name": "anonymous",
  "description": "anonymous user"
}

• code: Code representing the role

• name: Name of the role

• description: Description of the role

4. BillingService

This folder contains various JSON files related to billing services.

4.1 BusinessService.json

Defines business services, such as expenses like electricity bills and salaries.

{
  "businessService": "EXPENSE.ELECTRICITY_BILL",
  "code": "EXPENSE.ELECTRICITY_BILL",
  "collectionModesNotAllowed": [
    "DD"
  ],
  "partPaymentAllowed": true,
  "isAdvanceAllowed": false,
  "isVoucherCreationEnabled": true,
  "isActive": true,
  "type": "Adhoc"
}

• businessService: Identifier for the business service.

• code: Code representing the business service.

• collectionModesNotAllowed: Collection modes not allowed for the service.

• partPaymentAllowed: Indicates whether part payment is allowed.

• isAdvanceAllowed: Indicates whether advance payment is allowed.

• isVoucherCreationEnabled: Indicates whether voucher creation is enabled.

• isActive: Indicates whether the service is active.

• type: Type of the service.

4.2 PaymentService.json

This file, located in the billingservice folder provides configurations for payment services within the Billing Service module.

{
  "tenantId": "pb",
  "moduleName": "BillingService",
  "PaymentService": [
    {
      "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
    }
  ]
}

• tenantId: The identifier for the tenant associated with the configuration.

• moduleName: The name of the module, in this case, "BillingService."

• PaymentService: An array containing configurations for different payment services.

Payment Service Configuration:

• businessService: Identifier for the business service.

• code: Code representing the payment service.

• collectionModesNotAllowed: Array specifying modes of payment not allowed for this service.

  • "DD": Demand Draft

  • "CHEQUE": Cheque

  • "CARD": Card

  • "OFFLINE_NEFT": Offline NEFT

  • "OFFLINE_RTGS": Offline RTGS

  • "POSTAL_ORDER": Postal Order

  • "ONLINE": Online

• partPaymentAllowed: Indicates whether part payment is allowed for this service.

• isAdvanceAllowed: Indicates whether advance payment is allowed for this service.

• demandUpdateTime: Time interval (in milliseconds) for updating demands.

• isVoucherCreationEnabled: Indicates whether voucher creation is enabled for this service.

• billGineiURL: URL for generating bills using Bill Genie.

• isBillAmendmentEnabled: Indicates whether bill amendment is enabled for this service.

This configuration specifies the payment modes not allowed for the "ws-services-calculation" business service, whether part payment and advance payment are allowed, the demand update time, voucher creation status, Bill Genie URL, and bill amendment status.

4.3 TaxHeadMaster.json

This file is responsible for defining the various charges and taxes which are going to be configured in the application.

4.4 TaxPeriod.json

This file is used to define the number of financial years which are supported in each tax head.

ws-services-masters

This folder contains various JSON files related to ws-services-masters.

ws-services-calculation This folder contains various JSON files related to ws-services-calculations.

PropertyTax

This folder contains various JSON files related to property tax.

ExpenseType

This folder contains expense type in JSON format.

All (1 to 8 points) are state-level changes.

Tenant Folder (City level changes for every city there is one folder in MDMS)

For each tenant, there is a unique folder containing three subfolders, each with its specific configuration files.

1. businessservice.json - Billing Service Configuration

This file, located in the billing service folder, provides tenant-specific configurations for the Billing Service module. It is similar to the global BusinessService.json configuration but is specific to the tenant.

2. boundary-data.json - Location Boundary Data Configuration

This file, located in the egov-location folder contains boundary data specific to the tenant.

Details of the structure and content of this file would be specific to the actual data in the system. Please refer to the specific boundary-data.json file for detailed information.

3. WCBillingSlab.json - Water Connection Billing Slab Configuration

This file, found in the ws-services-calculation folder defines billing slabs for water connection based on building type and connection type.

{
  "id": "1",
  "buildingType": "RESIDENTIAL",
  "connectionType": "Metered",
  "calculationAttribute": "Water consumption",
  "minimumCharge": 100,
  "slabs": [
    {
      "from": 0,
      "to": 1000000,
      "charge": 2,
      "meterCharge": 50
    }
  ]
}

• id: Unique identifier for the billing slab.

• buildingType: Type of the building (e.g., RESIDENTIAL).

• connectionType: Type of connection (e.g., Metered).

• calculationAttribute: Attribute used for calculation (e.g., Water consumption).

• minimumCharge: Minimum charge for the billing slab.

• slabs: Array defining the billing slabs, including from, to, charge, and meterCharge.

This configuration is used to determine rates for water consumption based on the specified billing slab criteria.

There is a tenant folder in the MDMS which contains all tenants in tenants.json file.

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 water connection-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 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

• Calling generateDemand method based on isAdvanceCalculation. If true, create a demand object with consumerType “waterConnection-advance“.

The purpose of the NalJalSeva IFIX adapter service is to push the demand, bill, and payment events to IFIX from the NalJalSeva.

Overview

NalJalSeva IFIX adapter service is a wrapper for pushing data from the NalJalSeva to IFIX. When demand or payment is generated in the NalJalSeva system, the NalJalSeva IFIX adapter service listens to those topics and it calls the IFIX reference adapter service push API to publish the data to IFIX.

Pre-requisites

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

• Java 8

• Kafka

• Spring boot

Key Functionalities

• Pushing demand, bill and payment events to the IFIX adapter

The following topics interact with the NalJalSeva IFIX adapter service - When we create demand for ws-services, then it sends an event as demand for IFIX. If it is expense demand, it sends the event as a bill for IFIX. If it is a ws-services payment, then it sends the event as a receipt for IFIX. If it is an expense payment, it sends the payment as an event for IFIX.

• naljalseva-create-demand

• naljalseva-update-demand

• egov.collection.payment-create

Deployment Details

Deploy the following build.

• ifix-adapter:v1.0.0-4e24064-14

Integration Details

Integration Scope

NalJalSeva IFIX adapter is integrated with the IFIX Reference adaptor service. NalJalSeva IFIX adapter Application internally invokes the IFIX Reference adaptor service to push the data.

Integration Steps

NalJalSeva IFIX adapter application triggers IFIX-reference-adapter/events/v1/_push to push the demand, bill, and payment events from NalJalSeva to IFIX.

Service Architecture

NalJalSeva is built on top of the DIGIT Platform. It consists of distinct layers listed below.​

Back End - Core Services

1. ​User Services (egov-user)

2. ​User OTP (user-otp)

3. ​Access Control (access-control)

4. ​MDMS

5. ​ID Generation Service (id-gen)

6. ​Payment Gateway (pg-service)

7. ​Workflow Service (wf-service)

8. ​Persister

9. ​Indexer

10. ​Encryption Service (data-encryption-service)

11. ​Localization Service (localization-service)

12. ​Boundary Service (boundary-service)

13. Location Service (location-service)

14. ​URL Shortening Service (url-shortening-service)

15. ​PDF Generation Service (pdf-generator)

16. ​SMS Notifications (notification-sms)

17. Email Notifications (notification-email)

18. ​Filestore

19. ​API Gateway​

Business Services

1. ​Billing Service​

2. ​Collection service​

3. ​Apportioning Service​

4. ​Dashboard Ingest​

5. ​Dashboard Analytics (DSS)

Municipal Services

1. ​Property Service (property-services)

2. ​Water Service Calculator (ws-calculator)

3. ​Water Service (ws-service)

4. ​eChallan (echallan)

5. ​User Events (user-event)

6. ​Vendor​

7. ​IFIX Adaptor Integration Service​

NalJalSeva Architecture

The sequence diagram below illustrates a typical interaction between the various services. Sample sequence diagram for a typical flow of DIGIT Microservices.