Product - mGramSeva - iFIX
Introduction
This document contains Product Requirements and specifications of mGramSeva.
mGramSeva app is majorly used to capture revenue and expenditures of GPWSCs. This will also help in brining about financial transparency to DWSS department on handed over schemes.
iFIX is designed and developed in 4 important parts.
mGramSeva
iFIX Adapter
IFIX Core
Reference dashboard
About mGramSeva
Manage Gram Panchayats Master Data
Manage Gram Panchayat Administrator
Scheme handed over to GPWSC - RD
Scheme with WSSD - WSSD
Manage GP Level Settings
Electricity Meters etc..
Manage User Access
Manage Receipts
Manage Expenditure
View Reports
Integrate with iFix Adaptor
Manage Internal Transaction to Head Mappings
Post to iFIX
Save Reference ID
Reconcile Transactions
Fetching data from other systems
Rural development system
Banks
Origami
PFMS/Treasury
PSPCL
Abbreviations
Abbreviations | Description |
GP | Gram Panchayat |
HH | Household |
FY | Financial Year |
PSPCL | Punjab State Power Corporation Limited. |
IFMS | Integrated Financial Management System |
PFMS | Public Financial Management System |
GPWSC | Gram Panchayat Water Supply and Sanitation Committee |
Why mGramSeva
No visibility in the financial information(revenue and expenditure) of the GPWSS run schemes.
Objectives
Digitize the revenue collection process for water charges pertaining to schemes under GPWSC.
Digitize expenditure information of schemes under GPWSC
Pass the digitized fiscal information into the reference dashboard via iFIX.
Success Metrics
70% of GPs from Anandpur Division should start using GPWSS system in month 1
90% GPs should start using GPWSS System by month 3
Potential Risks
Not having adoption at ground
Revenue collector not having a smart phone.
Possible poor-connectivity issues in certain villages?
Users
GPWSC committee
Sarpanch/Secretary
View the dashboards by month/by billing cycle to ensure collections and expenditure rightly collected and spent.
Treasurer
Generate bulk demand for each billing cycle in addition to viewing the dashboards for each billing cycle.
Revenue collector
Revenue collector is responsible for collection of revenue under each billing cycle.
Visiting each HH, raising bills, entering meter details for HH with metered connection, collecting the amount and handling collected revenue back to treasurer/committee will be part of Revenue collectors job.
Types of roles
Collection Operator
GP Admin (Consumer creation)
Revenue (Bulk Demand) Processing
Expense Processing
GP Dashboard
Feature List
Feature Group | Sub - Feature | Remarks |
Login | Select Language | |
Login | ||
Forget Password | ||
Cards listing based on roles (Landing Page) | ||
Tenant Selection | Select Tenant | |
Switch Tenant | ||
Generate Bulk Demand | Generate Bulk Demand | |
Bulk notification | ||
Household information (New/Edit/Search) | New Connection | |
Search Connection | ||
Edit Connection | ||
View Household information | ||
Billing | Raise Water bill (Metered) | |
Generate Bill (Acknowledgment screen) | ||
SMS Notification | ||
Bill PDF | ||
Exception cases ??should this be handled. | ||
Bill sequence number (Config) | ||
Revenue of | Collect Payment | |
Generate Receipt | ||
SMS Notification / eMail | ||
Receipt PDF | ||
Online Payment interface (navigated from SMS) | ||
Payment gateway integration | ||
Expenditure | Add Expense | |
Update expense detail | ||
Dashboard | View collection & Exp dashboard | |
Sort & Filter Revenue table | ||
Sort & Filter Expenditure table | ||
Master | Revenue and Expenditure Heads | State |
Scheme Master | State | |
Electricity Connection | Tenant | |
Boundary (Hierarchy Type, Boundary Type and Boundary) | State | |
Gram Panchayat | State | |
User Role | State | |
User |
| |
Rate | Tenant | |
Billing Cycle |
| |
Integration | PSPCL | NA |
Out of scope :
Penalty Calculation (P2)
Advance Payment (P2)
Application Flow
Registration, Login and tenant selection
Step | Description | Screens |
1 | Registration: Users will be invited to the GP system via SMS. SMS will take the user to a language selection screen followed by a password setup screen. Users will have 3 languages to select English, Hindi and Punjabi. GPs linked to the user's mobile number are shown on this screen. Password Validation Once the password is set, the user can log into the system. | |
2 | Click on ‘Continue to login’ to proceed to the login screen. Enter phone number and password to login. For users associated with single GP, home screen will be shown with NO Dropdown for GP selection IF a GP is added/removed to a user at a later point of time, the same will be added/removed from dropdown. | |
3 | For users associated with multiple GPs, the home screen will be shown with Dropdown for GP selection. Drop down will contain a list of GPs linked to the user's mobile number in alphabetical order. Show GP Code along with GP name | |
4 | Users who want to reset their password or forgot password will come on forgot password screen by clicking on “Forgot Password” Link on login screen. Enter phone number and continue to receive a link to reset password. Phone number should NOT be new. It should already be existing (linked to any GPs) in the system How will users change of phone number be entered? |
New Connection & Modify connection
Step | Description | Screens |
1 | Home Screen: Users will see maximum 9 cards on home screen
Validations: Depending on roles users will be able to take respective actions. | |
2 | Consumer Creation Users can create new HH/Consumer/Connection in the application using this option. UX after submitting the page - Confirm with Antriksh Data Elements:
Validations:
| |
3 | Edit Consumer information Edit contact info (Home Screen) -> Search connection -> Consumer detail Screen Connection ID is not editable. Rest all fields are editable. | |
4 | Closed/Inactive connections |
Generate Bulk Demand
Step | Description | Screens |
1 | This screen will be used by <role> to generate Bulk demand for non-metered consumer types in the GP. Once Demand is generated for a billing cycle all non-metered consumers will get notification that a bill is generated. *Metered connections will get bill generated messages only after meter reading is entered. Data Elements:
Validations If the demand is already generated, it should generate only for those HH for which demand does not exist for the given cycle. |
|
2 | Online Payment An SMS with payment link is sent to HH(Non-metered) as soon as demand is generated. This link will contain payment to current month plus arrears if any. For metered connections,SMS is sent only after revenue collector visits the household enters meter readings and generates the bill. |
Billing
Step | Description | Screens |
1 | <User> Can search for HH by mobile number or connection ID Use Cases
| |
2 | Screen when HH mobile number has more than 1 Connection. Each card will show following details
| |
3 | After searching for HH by phone number or connection ID <user> lands onto this screen. Show below details of the user
Under this Aggregate information of the user is shown by the selected time range Financial year?
Below the aggregate information month wise billing information will be shown to <user> Each card will have
Is this possible? Are we storing month/cycle wise bill information for previous years too in the system?
| |
4 | To generate bill for metered connection <role> will come onto this screen where
Clicking on generate bill will generate bill for HH Notification will be sent to HH <role> will have the option to download the bill on his device. | |
5 | HH information-> Generate Bill->Collect payment HH information-> Collect payment Payment information
|
Expense Record
Step | Description | Screens |
1 | <user> Can record expenses from this screen. Following details are captured while entering expense record
| |
2 | User gets to this screen from two flows Home screen -> Click on Dashboard -> Expenditure Tab Home Screen -> Update Expenses Dashboard will be filtered by date Data fields
|
Dashboard
Step | Description | Screens |
1 | <role> clicks on dashboard on home screen to view GP dashboard Default dashboard shows collections and expenditure table by each billing cycle in selected year(Financial/Calendar?) Each cell represents net collection and expenditure for that billing cycle (Cash/Accrual?) |