Agsdm SRS

AGDSM- Unified Scheme
AgDSM
Scheme
Software Requirement Specification
Version 0.1 | 09th May 2019
1
AgDSM-Agriculture Demand Side management
Project Description
1. Project Code
RISL_EESL (Design, Development, Implementation & FMS of Unified

2. Project Name
Portal of EESL)
3. Account
5. Location Rajasthan
6. Customer Name EESL
7. Project Manager/ Email Debasis Sarangi
8. Customer Contact Details EESL
Review History
Prepared Prepared Reviewed Reviewed Approve Approve Change Description

#
By Date By Date d By d Date
1 Sanjay 09th May

. Singh 2019
2
.
3
.
Affected Group
1. RISL (Raj Comp)
2. EESL (Energy Efficiency Services Ltd)
3. CSDC India Pvt. Ltd.
2
Content
1. Introduction ............................................................................................................................................... 9
2. Project Summary ...................................................................................................................................... 9
3. Objective of the Project ........................................................................................................................... 9
4. Scope of Document ................................................................................................................................ 10
5. Function Overview ................................................................................................................................. 11

5.1. Overview of Scheme Process Flow ......................................................................................................................... 11
6. System Requirement in Detail ............................................................................................................... 12

6.1. Public Interface .................................................................................................................................................... 12
6.2. Website Details.................................................................................................................................................... 12
7. EESL Scheme Module Overview (login, Forget Password, edit) ....................................................... 13

7.1. EESL Login.......................................................................................................................................................... 13
7.1.1. Introduction............................................................................................................................................... 13
7.1.2. Functionality Flow Chart ........................................................................................................................... 13
7.1.3. User Login UI Wireframe .......................................................................................................................... 13
7.1.4. Use Case.................................................................................................................................................. 14
7.1.5. UI Validation Details ................................................................................................................................. 14
7.2. Change Password ................................................................................................................................................... 16
7.2.1. Introduction............................................................................................................................................... 16
7.2.2. Functionality Flow Details ......................................................................................................................... 16
7.2.3. Change Password UI................................................................................................................................ 17
7.2.4. Use Case.................................................................................................................................................. 17
7.2.5. User Validation Details ............................................................................................................................. 18
7.3. Forget Password ................................................................................................................................................. 19
7.3.1. Introduction............................................................................................................................................... 19
7.3.2. Forgot Password UI Wireframe ................................................................................................................ 19
7.3.4. Use Case.................................................................................................................................................. 21
7.3.5. UI Validation Details ................................................................................................................................. 21
8. Scheme Master Transaction .................................................................................................................. 22

8.1. EESL Scheme Registration ................................................................................................................................. 22
8.1.1. Introduction............................................................................................................................................... 22
8.1.3. Use Case.................................................................................................................................................. 24
8.1.4. UI Wireframe ............................................................................................................................................ 25
8.1.5. UI Validation ............................................................................................................................................. 25
8.2. Dashboard ........................................................................................................................................................... 27
8.2.1. Introduction............................................................................................................................................... 27
8.2.2. UI wireframe ............................................................................................................................................. 27
8.2.2. Use case .................................................................................................................................................. 28
9. Scheme Admin Transaction .................................................................................................................. 29

9.1. Scheme Admin .................................................................................................................................................... 29
9.1.1. Introduction............................................................................................................................................... 29
9.1.2. UI Wireframe ............................................................................................................................................ 29
3
9.1.4. Use Case.................................................................................................................................................. 31

9.2. Awareness Proposal............................................................................................................................................ 33
9.2.1. Search Awareness Proposal .................................................................................................................... 33
9.2.1.1. Introduction ......................................................................................................................................... 33
9.2.1.2. UI wireframe ....................................................................................................................................... 33
9.2.1.2. Functionality Flow Chart ..................................................................................................................... 35
9.2.1.3. Use Case ............................................................................................................................................ 35
9.2.1.4. UI Validation Details............................................................................................................................ 36
9.2.2. Create Awareness Proposal ..................................................................................................................... 37
9.2.2.1. Introduction ......................................................................................................................................... 37
9.2.2.2. UI Wireframe ....................................................................................................................................... 37
9.2.2.4. Use Case ............................................................................................................................................ 41
9.2.3. Approve / Reject Awareness Proposal ..................................................................................................... 45
9.2.3.1. Introduction ......................................................................................................................................... 45
9.2.3.2. UI Wireframe ....................................................................................................................................... 45
9.2.3.4. Use Case ............................................................................................................................................ 48
9.2.3.5. UI Validations details .......................................................................................................................... 49
9.3. Awareness Outcome ........................................................................................................................................... 51
9.3.1. Search outcome ....................................................................................................................................... 51
9.3.1.1. Introduction ........................................................................................................................................ 51
9.2.1.2. UI wireframe ....................................................................................................................................... 51
9.3.1.3. Use Case ............................................................................................................................................ 53
9.3.2. Create Outcome ....................................................................................................................................... 55
9.3.2.1. Introduction ......................................................................................................................................... 55
9.3.2.2. UI Wireframe ....................................................................................................................................... 55
9.3.2.4. Use Case ............................................................................................................................................ 59
9.3.3. Approve / Reject Awareness Outcome ..................................................................................................... 63
9.3.3.1. Introduction ......................................................................................................................................... 63
9.3.3.2. UI Wireframe ....................................................................................................................................... 63
9.3.3.4. Use Case ............................................................................................................................................ 67
9.3.3.5. UI Validations details .......................................................................................................................... 68
9.4. Survey ................................................................................................................................................................. 69

9.4.1. Search Survey .......................................................................................................................................... 69
9.4.1.1. Introduction ......................................................................................................................................... 69
9.4.1.3. Use Case ............................................................................................................................................ 71
9.4.2. Create Survey .......................................................................................................................................... 73
9.4.2.1. Introduction ......................................................................................................................................... 73
9.4.2.2. UI Wireframe ....................................................................................................................................... 73
9.4.2.4. Use Case ............................................................................................................................................ 76
9.5. Farmer Willing ..................................................................................................................................................... 80
9.5.1. Search farmer Willingness ........................................................................................................................ 80
9.5.1.1. Introduction ......................................................................................................................................... 80
9.5.1.3. Use Case ............................................................................................................................................ 82
9.5.2. Create willing ness form ........................................................................................................................... 84
4
9.5.2.1. Introduction ......................................................................................................................................... 84

9.5.2.2. UI Wireframe ....................................................................................................................................... 84
9.5.2.4. Use Case ............................................................................................................................................ 87
9.6. Proposal .............................................................................................................................................................. 91
9.6.1. Search Proposal ....................................................................................................................................... 91
9.6.1.1. Introduction ........................................................................................................................................ 91
9.6.1.3. Use Case ............................................................................................................................................ 93
9.6.2. Create Proposal ....................................................................................................................................... 95
9.6.2.1. Introduction ......................................................................................................................................... 95
9.6.2.2. UI wireframe ....................................................................................................................................... 95
9.6.2.4. Use Case ............................................................................................................................................ 97
9.7. Agreement ......................................................................................................................................................... 101

9.7.1. Search Agreement.................................................................................................................................. 101
9.7.1.1. Introduction ....................................................................................................................................... 101
9.7.1.2. Functionality Flow Chart ................................................................................................................... 103
9.7.1.3. Use Case .......................................................................................................................................... 103
9.7.1.4. UI Validation Details.......................................................................................................................... 104
9.7.2. Create Agreement .................................................................................................................................. 106
9.7.2.1. Introduction ....................................................................................................................................... 106
9.7.2.2. UI Wireframe ..................................................................................................................................... 106
9.7.2.4. Use Case .......................................................................................................................................... 110
9.8. LOA .............................................................................................................................................................. 112
9.8.1. Search LOA ............................................................................................................................................ 112
9.8.1.1. Introduction ...................................................................................................................................... 112
9.8.1.3. Use Case .......................................................................................................................................... 114
9.8.2. Create LOA ............................................................................................................................................ 116
9.8.2.1. Introduction ....................................................................................................................................... 116
9.8.2.2. UI Wireframe ..................................................................................................................................... 116
9.8.2.4. Use Case .......................................................................................................................................... 121
9.9 PO ..................................................................................................................................................................... 124
9.9.1. Search PO..................................................................................................................................................... 124
9.9.1.1. Introduction ....................................................................................................................................... 124
9.9.1.3. Use Case .......................................................................................................................................... 126
9.9.2. Create PO .............................................................................................................................................. 128
9.9.2.1. Introduction ....................................................................................................................................... 128
9.9.2.2. UI Wireframe ..................................................................................................................................... 128
9.9.2.4. Use Case .......................................................................................................................................... 131
9.10. Indent................................................................................................................................................................... 134
9.10.1. Search Indent ......................................................................................................................................... 134
9.10.1.1. Introduction ................................................................................................................................. 134
9.10.1.2. Functionality Flow Chart .............................................................................................................. 135
9.10.1.3. Use Case .................................................................................................................................... 136
5
9.10.1.4. UI Validation Details .................................................................................................................... 136

9.10.2. Create Indent.......................................................................................................................................... 138
9.10.2.1. Introduction ................................................................................................................................. 138
9.10.2.2. UI Wireframe ............................................................................................................................... 138
9.10.2.4. Use Case .................................................................................................................................... 141
10. DISCOM Transaction ................................................................................................................................ 144

10.1. Awareness Proposal ............................................................................................................................................ 144
10.1.1. Search Awareness Proposal ....................................................................................................................... 144
10.1.1.1. Introduction ................................................................................................................................. 144
10.1.1.2. UI Wireframe ............................................................................................................................... 144
10.1.1.4. Use Case .................................................................................................................................... 146
10.1.2. Create Awareness Proposal ................................................................................................................... 149
10.1.2.1. Introduction ................................................................................................................................. 149
10.1.2.2. UI Wireframe ............................................................................................................................... 149
10.1.2.4. Use Case .................................................................................................................................... 153
10.1.3. Approve / Reject Awareness Proposal ................................................................................................... 157
10.1.3.1. Introduction ................................................................................................................................. 157
10.1.3.2. UI Wireframe ............................................................................................................................... 157
10.1.3.4. Use Case .................................................................................................................................... 160
10.1.3.5. UI Validations details ................................................................................................................... 161
10.2. Awareness Outcome ........................................................................................................................................... 162
10.2.1. Search outcome .......................................................................................................................................... 162
10.2.1.1. Introduction ................................................................................................................................. 162
10.2.1.3. Use Case .................................................................................................................................... 164
10.2.2. Create Outcome .......................................................................................................................................... 167
10.2.2.1. Introduction ................................................................................................................................. 167
10.2.2.2. UI Wireframe ............................................................................................................................... 167
10.2.2.4. Use Case .................................................................................................................................... 171
10.2.3. Approve / Reject Awareness Outcome ................................................................................................... 174
10.2.3.1. Introduction ................................................................................................................................. 174
10.2.3.2. UI Wireframe ............................................................................................................................... 174
10.2.3.4. Use Case .................................................................................................................................... 178
10.2.3.5. UI Validations details ................................................................................................................... 179
10.3. Survey ................................................................................................................................................................. 180
10.3.1. Search Survey............................................................................................................................................. 180
10.3.1.1. Introduction ................................................................................................................................ 180
10.3.1.3. Use Case .................................................................................................................................... 182
10.3.2. Create Survey ........................................................................................................................................ 184
10.3.2.1. Introduction ................................................................................................................................. 184
10.3.2.2. UI Wireframe ............................................................................................................................... 184
10.3.2.4. Use Case .................................................................................................................................... 187
6
10.4. Farmer Willing...................................................................................................................................................... 191

10.4.1. Search farmer Willingness .......................................................................................................................... 191
10.4.1.1. Introduction ................................................................................................................................. 191
10.4.1.3. Use Case .................................................................................................................................... 193
10.4.2. Create willing ness form ......................................................................................................................... 195
10.4.2.1. Introduction ................................................................................................................................. 195
10.4.2.2. UI Wireframe ............................................................................................................................... 195
10.4.2.4. Use Case .................................................................................................................................... 197
10.5. Indent................................................................................................................................................................... 201
10.5.1. Search Indent ......................................................................................................................................... 201
10.5.1.1. Introduction ................................................................................................................................. 201
10.5.1.2. Functionality Flow Chart ............................................................................................................. 202
10.5.1.3. Use Case .................................................................................................................................... 202
10.5.2. Create Indent.......................................................................................................................................... 204
10.5.2.1. Introduction ................................................................................................................................. 204
10.5.2.2. UI Wireframe ............................................................................................................................... 204
10.5.2.4. Use Case .................................................................................................................................... 206
10.6. Bulk Upload ......................................................................................................................................................... 209
10.6.1. Bulk upload ................................................................................................................................................. 209
10.6.1.1. Introduction ................................................................................................................................. 209
10.6.1.2. UI Wireframe ............................................................................................................................... 209
10.6.1.4. Use Case .................................................................................................................................... 212
11. ADA Admin Transaction ...................................................................................................................... 213

11.1. Old Pump set Handover ............................................................................................................................... 213
11.1.1. Search Old Pump Set Handover ............................................................................................................ 213
11.1.1.1. Introduction ................................................................................................................................. 213
11.1.1.3. Use Case .................................................................................................................................... 214
11.1.2. Create Old Pump Set Handover .................................................................................................................. 216
11.1.2.1. Introduction ................................................................................................................................. 216
11.1.2.2. UI Wireframe ............................................................................................................................... 216
11.1.2.4. Use Case .................................................................................................................................... 219
11.2.1. Search Installation ....................................................................................................................................... 222
11.2.1.1. Introduction ................................................................................................................................ 222
11.2.1.2. UI Wireframe ............................................................................................................................... 222
11.2.1.4. Use Case .................................................................................................................................... 224
11.2.2. Create Installation ....................................................................................................................................... 226
11.2.2.1. Introduction ................................................................................................................................. 226
11.2.2.2. UI Wireframe ............................................................................................................................... 226
11.2.2.3. Use Case .................................................................................................................................... 227
11.3. Verification ........................................................................................................................................................... 230

11.3.1. Search Verification ...................................................................................................................................... 230
7
11.3.1.1. Introduction ................................................................................................................................. 230

11.3.1.3. Use Case .................................................................................................................................... 231
11.3.2. Create Verification ....................................................................................................................................... 234
11.3.2.1. Introduction ................................................................................................................................. 234
11.3.2.2. UI Wireframe ............................................................................................................................... 234
11.3.2.4. Use Case .................................................................................................................................... 236
11.4. Assign Pump to Farmers ..................................................................................................................................... 238
11.4.1. Search Verification ...................................................................................................................................... 238
11.4.1.1. Introduction ................................................................................................................................. 238
11.4.1.3. Use Case .................................................................................................................................... 239
11.4.2. Create Assign Pump to farmer .................................................................................................................... 241
11.4.2.1. Introduction ................................................................................................................................. 241
11.4.2.2. UI Wireframe ............................................................................................................................... 241
11.4.2.4. Use Case .................................................................................................................................... 242
12. Supplier Transaction ............................................................................................................................ 244

12.1. Dispatch ....................................................................................................................................................... 244
12.1.1. Search Dispatch ..................................................................................................................................... 244
12.1.1.1. Introduction ................................................................................................................................. 244
12.4.1.3. Use Case .................................................................................................................................... 245
12.1.2. Create Dispatch .......................................................................................................................................... 248
12.1.2.1. Introduction ................................................................................................................................. 248
12.1.2.2. UI wireframe ................................................................................................................................ 248
12.1.2.4. Use Case .................................................................................................................................... 250
12.2. Trip ............................................................................................................................................................... 253
12.2.1. Search Trip.................................................................................................................................................. 253
12.2.1.1. Introduction ................................................................................................................................. 253
12.2.1.3. Use Case .................................................................................................................................... 255
13. Common Messages .............................................................................................................................. 257

13.1. Annexure - 1 ................................................................................................................................................ 257
13.2. Annexure –2................................................................................................................................................. 259
8
1. Introduction
Scheme System will act as the electronic face of the DISCOM, ADA, Supplier as well as Scheme
Departmental users. It will be single source of the information for all ADA and Supplier for Pump
dispatch and installation. EESL, ADA and Supplier can track their Pump status on software. On the other
hand, department users also can monitor the Scheme Pump installation and verification by PMC (ADA)
and their status online.
2. Project Summary
Scheme is part of unified portal which is intended to provide access for the entire Scheme Schemes
user, ADA, DISCOM and supplier vendor.
Scheme admin can create, update and view Awareness proposal as per DISCOM, Proposal, Agreement,
Survey, Willingness form, and old pump handover, Create Indent, LOA, and PO against LOA, Installation,
and Assign Pump to Farmer and Bulk upload for offline.
 DISCOM user can create, update and view awareness proposal, Proposal outcome, Survey and
farmer willingness form.
 ADA user can create, edit and view Old Pump set handover, PMC verification, Installation and
Dispatch.
 Supplier user can view Indent, Old hand Pump Handover and Dispatch activity through login.
 System gives user wise role and responsibility to access Unified system as per requirement.
3. Objective of the Project
Objective of this System is to facilitate Scheme stakeholders in order to create awareness, outcome,
survey, willingness form, Letter of award with vendor, PO against LOA, indent creation, dispatch pump
to ADA location, installation new pump to farmer location with reference of assign pump to farmer
transaction. After installation PMC/ADA agency will go framer location.
9
4. Scope of Document
The scope of this SRS covers the functionality of end to end flow of Scheme like online Awareness
Proposal, Outcome, Survey, Agreement, LOA, PO creation, Old pump handover from framer and
assign new pump to farmer. After installation verification agency verifies pump installation.
10
5. Function Overview
5.1. Overview of Scheme Process Flow
11
6. System Requirement in Detail
6.1. Public Interface
6.2. Website Details

For Scheme Portal access user must go to http://ebs.eeslindia.org URL and login with Employee id, DISCOM
id, ADA Id and Supplier Id with password. And System will redirect to Dashboard and show as per role and
rights wise transaction.
12
7. EESL Scheme Module Overview (login, Forget Password, edit)
7.1. EESL Login
7.1.1. Introduction
Through this functionality, Scheme user will be login into the system with SAP ID (Employee id). User will
need to provide a user name, password in order to log in into the system to perform their activity.
Notes:
 The SAP ID will be treated as User ID
7.1.2. Functionality Flow Chart
Start
Is User Registered Get Registration

with EESL& have SAP Code No done by EESL
Admin
Yes
Enter User Id
and Password
Show Message Invalid

Is User ID & Password Correct No User Id and Password
Yes
Logged in System
End
7.1.3. User Login UI Wireframe
13
7.1.4. Use Case
Use case id UC_ User_ Login

Use Case name User login
Actors User Department User
Description It details about the login process for registered user on the Scheme
Preconditions The user should be registered in any Scheme with EESL and have valid SAP
Code, password
Post conditions User will be logged in into the system and will be redirected to respective
Dashboard page.
Normal Flow . User shall visit Login Page of unified portal
. User shall fill the Login Credentials and click Sign In
. The system shall validate the login credentials and if successfully verified,
shall display the Dashboard page of the logged in User and maintain the
session.
. On Successful – login Successfully
. On Failure – Invalid username/Password
Alternative Flows User do not remember the password and clicks on ’Forgot Password’.
Exceptions In case the Vendor enters incorrect credentials, system shall display error on
submission.
Includes NA
Priority High as it is the first step for accessing the services available to the registered
User.
Frequency of Use High
Business rules SAP Code of respective User will be treated as User Name
The User Name shall be unique and there shall be password policy for the
same
Assumptions User should know its login credentials.

Note and issues NA
7.1.5. UI Validation Details
Field Name Length Field Type Mandatory Populated By Field Specification /Validations
User Name 15 Text Box M User input Enter SAP ID of the registered user
Password 15 Text Box M User input Enter Password of the User
Forget Password NA Link NM NA Generate new password if user
have forgot current password
14
Sign In NA Button M NA Clicking on this will validate the

User id and password of the user
15
7.2. Change Password
7.2.1. Introduction
After the Login, If User wants to change the password from the Profile, and then he/she needs to provide the
new password and Confirm password.
7.2.2. Functionality Flow Details
EESL visit AgDSM portal
Login into the System with login details
After login, click on Change Password
EESL will provide old password and new password and confirm
new password
Is old password
Yes
correct?
No
Is confirm password and

new password same? No
Yes
System will show
New password will be saved in an Error message
to provide correct
the system database
password
close
16
7.2.3. Change Password UI
Menu Icon -> Profile
7.2.4. Use Case
Use case id UC_ Change Password
Use Case name Change Password
Actors Scheme user
Description It details about the change Password for registered users on the Scheme Portal for
online filing of the application.
Preconditions . The scheme user should be logged into the system
. Scheme should enter the old password
Post-conditions . Scheme user Password will get changed
Normal Flow . Scheme user need to visit Scheme PORTAL
. He will be logged in into the system
. Click on “Change Password”
. Enter Old Password
. Enter New Password and confirm the same
. On Success – Password Change Successfully
. On Failure – “Warning! Password not change “
Exceptions In case the Scheme user enters incorrect old Password or new password and confirm
new password does not match, the system shall display error on submission.
Includes NA
17
Priority Low as EESL will change his Password rarely.
Frequency of Use Low
Business rules The old Password shall be correct and new Password& confirm Password should be
same
Assumptions Scheme user should know the current Password
Note and issues NA
7.2.5. User Validation Details
Field Name Length Field Mandatory Populated By Field Specification /Validations

Type
Old Password 15 Text Box M User input Should not blank
New Password 15 Text Box M User input Should not blank
Confirm 15 Text Box M User input Should not blank

Password
18
7.3. Forget Password
7.3.1. Introduction
If registered user forgot the current password, user can generate new password by clicking on the ‘Forgot
Password’ link, whereas User need to enter User Id i.e. SAP Id of the User.
7.3.2. Forgot Password UI Wireframe
19
20
7.3.4. Use Case
Use case id UC_ Forgot_ Password

Use Case name Forgot Password
Actors User (Department User)
Description If user forgot the current password, user can generate new password by
clicking on the ‘Forgot Password’ link, whereas User need to enter User
Id i.e. SAP Id of the User.
Preconditions The user should be registered in any Scheme with EESL and have valid
SAP Code as well as password
Post conditions . User should be able to generate new password
Normal Flow . User shall open Login Page of unified portal
. User shall click ‘Forgot Password’ link
. User shall enter the User Id i.e. SAP Id of that user and click ‘Proceed’
button
. On incorrect User ID
. On Success – System should populate message ‘Do you want reset
password’
. Clicking on Yes button will send auto generated link at the User’s email
provided during registration, and Clicking on ‘No’ button will close the
popup window
. If Yes, User will go to the email Id and click on the received link which
will take the user to the reset password window
. At Reset password window, User will enter New Password and Confirm
new password as per Password policy
. On Success – Password changed successfully
Alternative Flows NA
Exceptions In case the EESL scheme user enters incorrect credentials, system shall
display error
Includes NA
Priority Medium
Frequency of Use Medium
Business rules System will allow user to reset password if user have forgot the current
password
Assumptions User should know its login User ID.
Note and issues NA
7.3.5. UI Validation Details
Password 8-15 Text Box M User input Enter New Password
Retype 8-15 Text Box M User Input Same as Password
Password
Reset NA Button M Na Clicking on this button will save the
Password password in database
21
8. Scheme Master Transaction
8.1. EESL Scheme Registration

Through this functionality, Department Users, DISCOM, ADA and Supplier will be logged into the
system. User will need to enter their SAP Code and password in order to log in into the system to
perform their activity.
8.1.1. Introduction
Registration is the process by which Scheme system records specific details of EESL super admin
panel and issues a unique Login ID and Password which is SAP Id, System generate Employee id or
vendor id at the time of joining and Vendor agreement. After login, EESL Scheme admin user can
view their profile; Dashboard, Awareness proposal, Awareness outcome, Survey, Willingness form,
Proposal, Agreement, Old pump handover, PMC verification, create indent, installation, LOA, PO,
Dispatch, Bulk upload, and Assign pump to framer transaction.
22
Start
Yes
Scheme admin clicks on Customer/vendor

Tab
Yes
Super admin Clicks on Customer/vendor for

registration
Yes
Admin should enter valid Mobile number And

Email id
Yes
User name,
address, district,
birth date
,Corporate
Details
Yes
Get Mail from System
Yes
Customer
receives the
mail As given
mail per given
mail id
Yes
Redirect to EESL
Login Page
Yes
Customer/vendor need to enter valid Credential
Yes
Correct
credential No
entered?
Yes
Enter password and confirm

Yes Error
password,
message is
displayed
Yes
submit Yes
Customer/Vendor
need to user SAP Yes
ID
Unsuccessful
Clos e Registration
23
8.1.3. Use Case
EESL Registration
Use Case ID UC_EESL user Registration

Use Case Name Registration of user
Actors Scheme user
Description This functionality allows Single Window user for registration
Preconditions User logged in into the system
Post-conditions User’s unique Login ID and Password is generated
Normal flow / . Login in unified portal

Basic Flow
. Login as Super admin
. Click on Create user
. Click on user create
. Select create Customer
. Single Window User click “Create Customer” option/link from Master
. A user enters personal details such as first name, address, district, birth date,
Dependencies mobile number,
User should corporate
enter details
valid mobile and password
number and email(which
id. will be further used for
login)
Includes NA
 User click on the "Submit” button
Priority High
 The system validates all inputs
Frequency of Use High Mail confirmation and OTP (One Time Password) is generated and sent
on the user's mobile number and mail id.
Business Rules/ Customer mobile number and Email id should be valid for successful registration
 A user needs to click on URL and system redirect to Login page
Validation
Special Valid Mobile
On success,
number,a user
Emailregisters
id successfully and can proceed with further
Requirements actions such as view profile and transaction details.
Assumptions The system should be up and running
24
8.1.4. UI Wireframe
8.1.5. UI Validation
Initial Name 50 Text box M User input Special character not allows.
Customer First Name 50 Text box M User input Allow char with whitespace
Customer Middle 50 Text box M User input Special character not allows.
Name
Customer Last Name 50 Text Box M User input Special character not allows.
Address 250 Text box M User input Special character allows.
State NA Dropdown M User input The system will populate State

name from State master
District NA Dropdown M User Input The system will populate District
25
name from District master
City NA Dropdown M User Input The system will populate City

name from City master
Pin code 06 Text Box M User Input Only Numeric allow
Phone no 10 Text box M User input Only Numeric allow
Company Name 50 Text box M User input Alphanumeric allows.
Years of 30 Calendar M User input Calendar picker

establishment picker
Company Address 250 Text box M User input Should not blank
GST No 15 Text box M User input Alphanumeric allow
TIN No 11 Text Box M District Alphanumeric allow

Master
Industry Type NA Dropdown M User input Should not blank
Industry sector NA Dropdown M User input Should not blank
User Name 50 Text box M User input Alphanumeric allow
Password 15 Text box M User Input Alphanumeric allow
Confirm Password 15 Text box M User input Alphanumeric allow
Clicking on this button will take

Update NA Button NA NA
the user on update
Clicking on this button will Clean

Reset NA Button NA NA
data
Clicking on this button system

Cancel NA Button NA NA
will redirect to home page
26
8.2. Dashboard
8.2.1. Introduction
Scheme user can check Dashboard by a first appeal by logging as Scheme user.
8.2.2. UI wireframe
27
8.2.2. Use case
Dashboard
Use Case ID UC_ Dashboard
Use Case Name Dashboard
ACTORS Scheme user
Description This page describes Dashboard
Preconditions Scheme user is logged in to the system
Post conditions Dashboard can visible after successful login
Normal flow / Basic Flow . Scheme User logins Unified portal

. User will see Main transaction screen
. Click Transactions -> Dashboard
Dependencies System should be up
Includes NA
Priority Low
Business Rules/ Validation Dashboard visible after login
Special Requirements None

Assumptions System should be up and running
28
9. Scheme Admin Transaction
9.1. Scheme Admin
9.1.1. Introduction
Scheme user can login through SAP Id (Employee id) and password. After login user can see Unified Scheme,
Related Scheme and Another portal. User need to choose Unified Scheme, in Unified Scheme user will get
transaction page.
9.1.2. UI Wireframe
This screen appears after successful log-in of the User which is the home screen of the User that shows
three sections on the page.
 Unified Scheme
 Other Scheme
 Related Portal
Section 1: Unified Scheme: This section shows the Name of Schemes of logged-In user which is assigned
to that user.
Section 2: Other Scheme: This section shows the Name of those Schemes which are kept out of Unified
section of logged-In user.
Section 3: Related Portal: This section shows the Name of that Portal which are kept out of Unified
section of logged-In user.
After selecting unified Scheme user will get Scheme Transaction window.
29
30
9.1.4. Use Case
EESL Admin transaction

Use Case ID UC_ Admin_ Transaction
Use Case Name Admin Transaction
ACTORS Scheme User
31
Description This functionality allows Scheme user to show application as per role
Preconditions EESL user is logged in to the system
Post-conditions System show role wise transaction
Normal flow / Basic Flow . User logins Unified portal

. User will see Main Scheme Icon
. Click Transactions
. User can see transaction as per admin role.
Includes NA
Priority Low
Business Rules/ Validation User will see admin transaction.
Special Requirements None
Assumptions NA
32
9.2. Awareness Proposal
9.2.1. Search Awareness Proposal
9.2.1.1. Introduction
Scheme Team can search the Awareness Proposal status and awareness details by entering the search
parameters on the search page for respective tabs like for awareness ID, Awareness name, created from,
created to and status.
9.2.1.2. UI wireframe
After Login  Click on Unified Scheme
Click on Awareness Tab
33
Click on Search Button
Awareness Search List
34
9.2.1.2. Functionality Flow Chart
9.2.1.3. Use Case
Use case id UC_ Awareness_ Search Page

Use Case name Scheme Awareness Proposal Search Page
Actors Scheme user
Description Scheme user can search the details by entering search parameters
Preconditions The scheme User should logged-in into the system
Post conditions Search Details will be Displayed in the list
Normal Flow . User will visit Login page of unified portal
. User will log-in into the system
. Click Unified Portal Links section-> Scheme> Awareness Proposal ->
. Enter search parameter
E.g. Awareness ID, Awareness name, created from, Created to and
status.
. Click Search button
Exceptions NA
Includes NA
35
Priority NA
Business Scheme user can search the details by entering search parameter
rules/Validation
Assumptions NA
Note and issues NA
9.2.1.4. UI Validation Details
Awareness ID 5 Dropdown No User input Awareness id allow only
numeric value
Awareness Name 50 Dropdown No User input Agency name should exist in
data base
Created From NA Input Box No Calendar Picker Must accept only past and
current date
Created to NA Input Box No Calendar Picker Must accept only past and
current date
Status NA Input box No Dropdown Must be only 3 status;
Approved, Pending and Draft
Search NA Button Yes NA Clicking on this button will
show details
Reset NA Button No NA Clicking on this button will
remove the search parameter
if entered any
Add New NA Button No NA Clicking on this button will
Awareness take the user at the page from
Proposal where Awareness Proposal
can be created
Back to Clicking on this will take the
NA Button NA NA
Transaction user to the Search page
Clicking on this button will
Sign-out NA Button NA NA
logout the user
Back to SSO NA Button NA NA take user on Transaction link
page
Clicking on this link will take
EESL Logo NA Button NA NA user to the Transaction
creation page
Clicking on this icon will take
user on the Profile Edit,
Navigation Icon NA Icon NA NA
Transactions as well as Task
List
Copy NA Button No NA Clicking on this button will
copy the content displayed on
the page which can be paste
on word page
Excel NA Button No NA Clicking on this button will
fetch the displayed rows into
the excel sheet
Print NA Button No NA Clicking on this button will
print the displayed rows
36
9.2.2. Create Awareness Proposal
Scheme user can create Awareness proposal from the Transaction link after Login.
9.2.2.2. UI Wireframe
Click on Awareness Proposal Tab
Click on Create Awareness Proposal Button
37
38
After click on Submit  Select User for Approval from Dropdown and Click on Submit
39
After Click on Submit Button Confirmation Message popup with Awareness Id
40
Start
Login with
Scheme Admin
Click Transaction
Icon -> Click
Transaction
Click Awareness
Proposal
-> Click Add New
Awareness
Fill Mandatory
Details - Submit
Select Desired User to

send for Approval ->
Submit button
Confirmation
Message will be
displayed
End
9.2.2.4. Use Case
Awareness Proposal
Use Case ID UC_ Awareness _ Proposal
Use Case Name Add Awareness Proposal
ACTORS Scheme user
Description This page describes about the Add new Awareness
41
Preconditions User should successful login into the system
Post conditions New Awareness will be created successfully
Normal flow / Basic . User logins Unified portal

Flow . User will see Main Navigation Icon on the left-hand side
. Click Transactions -> Awareness Proposal -> Create Awareness Proposal
. Fill Mandatory details and send for approval
Includes NA
Priority High
Business Rules/ Awareness Proposal will be created successfully

Validation
Special NA
Requirements
Assumptions NA
Field Name Length Field Mandatory Populated Field Specification

Name By /Validations
Awareness Type NA Dropdown M User Input Should be Present data in

System
Language NA Dropdown M User Input Should be Present data in

System
Awareness Name 50 Text Box M User Input Should accept Varchar with
special char
Awareness Objective 50 Text Box M User Input Should accept Varchar with
special char
State NA Dropdown M User Input Should be Present data in

System
District NA Dropdown M User Input Should be Present data in

System
Division NA Dropdown M User Input Should be Present data in
42
System
DISCOM NA Dropdown M User Input Should be Present data in

System
Address 50 Text area M User Input Should accept Varchar with

special char
Pin Code 06 Text Box M User Input Accept Numeric Value
Start Date NA Calendar M User Input Calendar Picker

Picker
End Date NA Calendar M User Input Calendar Picker

Picker
Invitees Detail 50 Text Box M User Input Should accept Varchar with
Organisation Name special char
Name 20 Text Box M User Input Accept Char value
Phone 10 Text Box M User Input Accept Numeric Value
Email 50 Text Box M User Input Accept Alpha Numeric Value
EESL Employee List NA Dropdown M User Input Should be Present data in

System
Name
Designation NA Text Box M Auto Auto Populate

populate
Phone NA Text Box M Auto Auto Populate

populate
Email NA Text Box M Auto Auto Populate

populate
External Party List NA Dropdown M Auto Should be Present data in

populate System
Type
Name 50 Text box M User input Accept Char value
Phone 10 Text box M User Input Accept Numeric value
Email 50 Text box M User Input Accept whitespace with

Varchar
Additional Details 5 Text Box M User Input Accept Numeric Value
43
Expected No. Of Enquiry
Expected Budget Cost 8 Text Box M User Input Accept Numeric Value
(in Rs.)
Expense Name 50 Text Box M User Input Accept Alpha Numeric Value
Expense Cost (in Rs.) 5 Text Box M User Input Accept Numeric Value
Remaining Allocated NA Text Box M Auto Auto populate

Budget populate
Total Estimated Cost (in NA Text Box Auto Auto populate

Rs.) populate
Remark 50 Text Area M User Input Accept Varchar with special

char
+ Add Row NA Button NA NA Clicking on this button will

add new row where user can
fill related information
-Delete Row NA Button NA NA Clicking on this button will

delete row where user can
delete chose related
information
Previous NA Button NA User Input System redirect to previous

page
Preview NA Button NA NA Clicking on this button will

show EESL project page
details which submitted by
EESL user
Save As Draft NA Button NA NA Clicking on this button will

save data in editable form
Submit NA Button NA NA Clicking on this button

system will create unique
Project ID with constituency
44
9.2.3. Approve / Reject Awareness Proposal
Scheme user or Approver can Approve/Reject the received Awareness Proposal from the Transaction link
after login.
45
Click on Accept Button for Approval
46
If Accepted -> Accepted confirmation -> OK
If Rejected -> Enter Rejection Remarks and click Reject Button
Rejection confirmation -> Ok
After click on OK button
47
Start
Login with
Scheme Admin
Credentials
Click on Transaction
Icon -> Click
Transactions ->
Click Awareness
Proposal -> Search
Click View Details

Icon
Rejected
Enter Rejection
Remarks and click
Accept or Reject Reject button ->
Status will be
changed as Draft
Accepted
Acceptance
confirmation will
show and Status will
be changed as
Approved
End
9.2.3.4. Use Case
Approve / Reject Awareness Outcome

Use Case ID UC_ Approve/Reject Awareness Proposal
Use Case Name Approve /Reject Awareness Proposal
ACTORS Scheme user
Description This page describes about the Approve /Reject Awareness proposal
48

Post conditions Awareness will be Approved or Rejected successfully
. User will see Main Navigation Icon on the left-hand side
. Click Transactions -> Awareness Proposal -> Search button
. Click View Detail icon -> click Approve or Reject button
. Awareness Proposal will be Approved or Rejected

Exceptions/Alerts NA
Includes NA
Priority High
Business Rules/ Validation Awareness proposal will be Approved or Rejected successfully
Special Requirements NA
Assumptions NA
9.2.3.5. UI Validations details
Populated Field Specification

Field Name Length Field Type Mandatory
By /Validations
Clicking on this icon will open
the page from where
View detail NA Icon M NA
Outcome can be approved or
Rejected
Approve the Outcome and
Accept NA Button NA NA
status will be changed as
Approved
Reject the Outcome and
Reject NA Button NA NA
Draft
NA Button NA NA
logout the user
page
creation page
Navigation Icon NA Icon NA NA user on the Profile Edit,
49
List
50
9.3. Awareness Outcome
9.3.1. Search outcome
Scheme user can search the Awareness Outcome status and awareness outcome details by entering the
search parameters on the search page for respective tabs like for awareness outcome ID, Awareness
outcome name and status.
51
Awareness Outcome Search List
52
9.3.1.3. Use Case
Use case id UC_ Awareness_ Outcome_ Search Page

Use Case name Awareness Outcome Search Page
Actors Scheme user
Description Scheme User can search the details by entering search parameters
Preconditions The User should logged-in into the system
. Click Unified Portal Links section-> Scheme> Awareness Outcome ->
E.g. Outcome ID, Awareness outcome name and status.
Exceptions NA
Includes NA
Priority NA
53
Business rules/Validation Scheme Admin user can search the details by entering search parameter
Assumptions NA
Note and issues NA
Outcome ID 5 Dropdown No User input Awareness outcome id allow
only numeric value
Outcome Name 05 Dropdown No User input Agency name should exist in
data base
show details
if entered any
Create New NA Button No NA Clicking on this button will
Outcome take the user at the page from
where Outcome can be
creating as per Awareness
Proposal
NA Button NA NA
logout the user
Back to SSO NA Button NA NA take user on Master /
Transaction link page
EESL Logo NA Button NA NA user to the Master and
Transaction creation page
Masters, Transactions as well
as Task List
on word page
the excel sheet
54
9.3.2. Create Outcome
Scheme admin can create Awareness Outcome from the Transaction link after Login; however, awareness
outcome can be created from two ways. One by clicking on + (Add Outcome) from the Awareness search list,
secondly clicking on Awareness Outcome tab -> Add Outcome button
First way to create Awareness Outcome ->Click Transactions -> Awareness Outcome
55
Click Search
Awareness Search List Page -> Click + icon (Add Outcome)
Second Way to create Awareness Outcome: Click Main EESL LOGO -> Click Transactions -> Awareness
Outcome -> Select Awareness Id
56
Select Awareness ID And click on Next Button
Fill All Details and Click on Next Button
57
Fill Details and Click on Submit Button
Select desired user whom Awareness Outcome to be sent for Approval
Submission confirmation message
58
Start
Login with
Scheme Admin
Credentials
Icon -> Click
Transactions ->
1- Click Awareness
2- Awareness Outcome
Proposal -> Search ->
-> Add Outcome->
Click + Icon (Add
Select Awareness Id
Outcome)
Awareness Outcome Creation

page -> Fill Mandatory Details
and submit for Approval
End
9.3.2.4. Use Case
Awareness Outcome
Use Case ID UC_ Awareness _ Outcome
Use Case Name Awareness outcome
ACTORS Scheme user
Description This page describes about the create awareness Outcome
Post conditions Awareness Outcome will be created successfully

. Click Transactions -> Awareness Proposal
59
. Enter Search Parameters -> Search button

. Search list will be displayed -> Click + Icon (Add Outcome)
. Awareness Outcome page will be opened
Includes NA
Priority High
Business Rules/ Awareness Outcome should be created successfully

Validation
Special None
Requirements
Assumptions NA

Awareness ID NA Dropdown M User Input Should be Present data in

System
Awareness Name NA Text Box M Auto Should accept Varchar with

Populate special char
Total Enquiry Received 08 Text Box M Auto Should accept Varchar with
EESL Employee List 50 Text Box M Auto Should accept Varchar

Populate
Name
Designation 50 Text Box M Auto Should accept Varchar

populate
Phone 10 Text Box M Auto Should accept Varchar

populate
Email NA Text Box M Auto Should accept Varchar with

populate special char
External Party List NA Text Box M Auto Should be Present data in

populate System
Type
60
Name 50 Text box M Auto Should be Present data in

populate System
Phone 10 Text box M Auto Should be Present data in

populate System
Email 50 Text box M User Input Should be Present data in

System
Participants Details 50 Text box M User Input Should be allow Varchar
Department Name
Person Name 50 Text box M User Input Should allow char
Designation 50 Text box M User Input Should allow Varchar
Mobile 10 Text box M User Input Should allow only numeric
Email id 50 Text box M User Input Should allow Varchar and

special char
Attachment details 50 Text box M User Input Should allow Varchar and
special char
Browse File NA Upload M User Input Only allow PDF, JPEG, JEP
Button and all image format
Additional Details NA Text Box M Auto Should be Present data in

populate System
Estimated cost (In Rs.)
Actual Cost involved (in 8 Text box M Auto Should be Present data in
Rs.) populate System
Remaining Allocated NA Text box M Auto Auto populate

Budget populate
Remark 250 Text box M User Input Should allow Varchar and
special char
Expense Name 50 Text box M User Input Should allow Varchar and
special char
Estimated Cost 8 Text box M User Input Allow only Numeric
Actual cost 8 Text box M User Input Allow only Numeric
61
Attach Invoice NA Upload M User Input Only allow PDF, JPEG, JEP
62
9.3.3. Approve / Reject Awareness Outcome
Scheme user or Approver can Approve/Reject the received Awareness Outcome from the Transaction link
after login.
create Awareness Outcome ->Click Transactions -> Awareness Outcome
63
Click Search
Outcome Search List Page ->View Detail
Click Accept or Reject button
64
65
Recetion Confirmation Message
66
Start
Login with
Scheme Admin
Credentials
icon
Click Awareness
Outcome -> Search
Click View Details

Icon
Enter Rejection
Remarks and click
Accept or Reject Rejected Reject button ->
Status will be
changed as Draft
Accepted
Acceptance
confirmation will
be changed as
Approved
End
9.3.3.4. Use Case

Use Case ID UC_ Approve/Reject Awareness Outcome
Use Case Name Approve /Reject Awareness Outcome
ACTORS Scheme Admin
Description This page describes about the Approve /Reject Awareness Outcome
. User will see Main Navigation Icon on the Transaction
. Click Transactions -> Awareness Outcome -> Search button
. Awareness Outcome will be Approved or Rejected
67

Includes NA
Priority High
Business Rules/ Validation Awareness Outcome will be Approved or Rejected successfully
Assumptions NA

By /Validations
the page from where
Rejected
Approved
Draft
NA Button NA NA
logout the user
List
68
9.4. Survey
9.4.1. Search Survey
Scheme Team can search the Survey status and Survey details by entering the search parameters on the
search page for respective tabs like for Survey ID, consumer name and Mobile no.
Click Transactions ->Click on Survey Tab
69
Search List
70
9.4.1.3. Use Case
Use case id UC_ Survey_ Search Page

Use Case name Survey Search Page
Actors Scheme user
Description Scheme Admin User can search survey details by entering search
parameters
. Click Unified Portal Links section-> Scheme> Survey ->
E.g. Survey ID, consumer name and Mobile no
Exceptions NA
Includes NA
Priority NA
Business Scheme Admin user can search the details by entering search parameter
71
rules/Validation and survey details will use in farmer willingness for creating indent
Assumptions NA
Note and issues NA
Survey ID 5 Text Box No User input Survey id allow only numeric
value
Farmer Name 50 Dropdown No User input Agency name should exist in
data base
Mobile no 10 Input box No User Input Accept Numeric Value starting
with 6,7,8,9
show details
if entered any
Survey take the user at the page from
where Survey can be created
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
72
9.4.2. Create Survey
This section will allow creating survey as per DISCOM requirement. Survey will manage all details about
farmer and pump. It shows primary information about farmer. Survey basically takes care by PMC and
DISCOM stakeholder.
Click Transactions -> Survey
Click on Create New Survey Button and click on Submit button
73
Fill all the Details
74
Confirmation Message with Survey id
75
9.4.2.4. Use Case
Survey
Use Case ID UC_ Survey
Use Case Name Survey
ACTORS Scheme user
Description This page describes about to create new Survey
Post conditions Proposal will be created successfully
76
Flow . Click Transactions -> Survey -> Create New Survey

. Enter Mandatory details and submit
. Survey will be created
Includes NA
Priority High
Business Rules/ Survey should be created successfully

Validation
Special None
Requirements
Assumptions NA

General Information 50 Text box M User Input System allow char
Farmer Name
Father Name 50 Text box M User Input System allow char
Transformer Location 20 Text box M User Input Accept Alpha Numeric Value
and special Char
Transformer Name code 10 Text box M User Input Accept Alpha Numeric Value
and special Char
Service Connection 20 Text box M User Input Accept Alpha Numeric Value
Number and special Char
Mobile Number 10 Text box M User Input Accept Numeric Value
Sanction Load 10 Text box M User Input Accept Alpha Numeric Value
Date NA Text box M Calendar Calendar Picker

Picker
State NA Text box M Dropdown Should be Present data in

System
77
District NA Text box M Dropdown Should be Present data in

System
ID Type NA Text box M Dropdown Should be Present data in

System
ID Number NA Text box M User Input Accept Numeric Value
DIVISION NA Text box M Dropdown Should be Present data in

System
DISCOM NA Text box M Dropdown Should be Present data in

System
Village Name 50 Text box M User Input Accept Alpha Numeric Value
Address 250 Text Area M User Input Accept Alpha Numeric Value
Document Attachment NA Browse M User Input Accept Pdf, Doc, JPEG

Button
Pump Set Details NA Text box M User Input Should be Present data in
System
Pump Set Rating
(HP/KW)
Age of Pump Set 5 Text box M User Input Accept Alpha Numeric Value
Pump Manufacturing NA Text box M Calendar Should be Present data in

Date Picker System
No. of Stage in Case 5 Text box NM User Input Accept Numeric Value
Submersible
Performance of Pump 5 Text box NM User Input Accept Alpha Numeric Value
Parameter Voltage(v)
Current (I) 5 Text box M User Input Should be Present data in

System
Input Power (KW) 5 Text box M User Input Accept Numeric Value
Power factor 5 Text box NM User Input Accept Numeric Value
Time Taken to fill Time 5 Text box NM User Input Accept Numeric Value
Flow (LPS) 5 Text box NM User Input Accept Numeric Value
Iteration I, II, III 5 Text box M User Input Accept Numeric with
decimal Value
Average / Total NA Text box M Auto Auto Populate
78
Populate
Total Bore depth (FT) 10 Text box M User Input Accept Alpha Numeric Value
Pump Installation Depth 10 Text box M User Input Accept Alpha Numeric Value
(FT)
Water Level from 10 Text box NM User Input Accept Alpha Numeric Value
Ground (FT) Min/Max
Elevation of Discharge 10 Text box NM User Input Accept Alpha Numeric Value
Point (FT)
Bore Size (inch) 10 Text box NM User Input Accept Alpha Numeric Value
Pump Size (inch) 10 Text box M User Input Accept Alpha Numeric Value
Delivery Pipe Type 10 Text box M User Input Accept Alpha Numeric Value
Delivery Pipe Length 10 Text box NM User Input Accept Alpha Numeric Value
Delivery Pipe Diameter 10 Text box NM User Input Accept Alpha Numeric Value
(inch)
Pressure (kg/sq. cm if 10 Text box NM User Input Accept Alpha Numeric Value
required)
Corp Cultivated 10 Text box NM User Input Accept Alpha Numeric Value
Method of 10 Text box NM User Input Accept Alpha Numeric Value

Irrigation/required Area
Other Observation: 50 Text Area NM User Input Accept Alpha Numeric Value
79
9.5. Farmer Willing
9.5.1. Search farmer Willingness
Scheme Team can search the Willingness status and willingness details by entering the search parameters on
the search page for respective tabs like for state, District, DISCOM, from date and to date.
Click Transactions -> Farmer Willingness
80
Search List-->Click on View icon to see details
81
9.5.1.3. Use Case
Use case id UC_ Willingness_ Search Page

Use Case name Willingness form
Actors Scheme user
Description Scheme User can search the details by entering search parameters
. Click Unified Portal Links section-> Scheme> Farmer Willingness->
E.g. State, District, DISCOM, from date and to date.
Exceptions NA
Includes NA
Priority NA
82
rules/Validation
Assumptions NA
Note and issues NA
State NA Dropdown No User input Should be in System
District NA Dropdown No User input Should be in System
DISCOM NA Dropdown No User input Should be in System
From date NA Calendar No User input Accept Present and Past date
Picker only
To date NA Calendar No User input Accept Present and Past date
Picker only
show details
if entered any
New willingness NA Button No NA Clicking on this button will
form take the user at the page from
where Willing can be create
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
83
9.5.2. Create willing ness form
This section will allow to Scheme user can create willingness form against survey. Willingness form is full
details of farmer and pump.
Click Transactions -> Farmer willingness
Click on Add Willingness Form
84
Fill all the Required Fields and Click on Submit Button
85
After Clicking Submit Button
86
9.5.2.4. Use Case
Farmer Willing Form
Use Case ID UC_ Farmer_ Willingness_ Form
Use Case Name Farmer Willing Form
ACTORS Scheme User
Description This page describes about the create Willingness form against framer
Post conditions Farmer willing Form will be created successfully

. Click Transactions -> Farmer willingness-> Create New willingness
. Farmer willingness id will be created
87
Includes NA
Priority High
Business Rules/ Farmer Willingness Form should be created successfully

Validation
Special None
Requirements
Assumptions NA
Field Name Length Field Type Mandatory Populated Field Specification /Validations
By
Consumer Name 50 Text box M Auto Should be Present data in System

populate
Father Name 50 Text box M Auto Should be Present data in System

populate
Mobile Number 10 Text box M User Input Should be Present data in System
Date of NA Text box M Calendar Should select current or future date

Installation Picker only
Agency Code 20 Text box M User Input Should Accept whitespace,

Alphanumeric value
Service NA Text box M Dropdown Should be Present data in System

Connection
Number
State NA Text box M Auto Should be Present data in System

populate
District NA Text box M Auto Should be Present data in System

populate
Circle Name NA Text box M Auto Should be Present data in System
88
populate
Division Name NA Text box M Auto Should be Present data in System

populate
DISCOM NA Text box M Auto Should be Present data in System

populate
Village Name 50 Text box M User Input Should Accept whitespace,

& Auto Alphanumeric value
populate
Address 250 Text Area M User Input Should Accept whitespace,

populate
Section Office 50 Text box NM User Input Should Accept whitespace,

populate
DTR 20 Text box M User Input Should Accept whitespace,

Location/Number Alphanumeric value
Feeder Name 20 Text box M User Input Should Accept whitespace,

Alphanumeric value
Attachment NA Browse M User Input Accept Pdf, Doc, JPEG

Detail button
Pump Set Rating 10 Text box NM User Input Should Accept whitespace,
populate
Total Bore Depth 10 Text box M User Input Should Accept whitespace,
(FT.) & Auto Alphanumeric value
populate
Pump Installation 10 Text box M User Input Should Accept whitespace,

Depth (FT.) Alphanumeric value
Water Level from 10 Text box NM User Input Should Accept whitespace,
Ground (FT.) Alphanumeric value
min/max
Bore Size (Inch) 10 Text box M User Input Should Accept whitespace,
Alphanumeric value
Site Location 50 Text box M User Input Should Accept whitespace,

Alphanumeric value
89
Age of Pump Set 30 Text box M User Input Should Accept whitespace,
Alphanumeric value
Delivery Pipe 20 Text box M User Input Should Accept whitespace, Should
Length (FT.) Accept whitespace, Alphanumeric value
Delivery Pipe Size 10 Text box M User Input Should Accept whitespace,
(inch) Alphanumeric value
10 Text box NM User Input Should Accept whitespace,

Elevation of Alphanumeric value
Discharge Point
Height (ft.)
Pump Size 10 Text box M User Input Should Accept whitespace,

Alphanumeric value
Preview NA Button NA NA Clicking on this button will show EESL

project page details which submitted by
EESL user
Attachment NA Browse M Browse Only <Pdf, JPEG> should be allowed

Attach Attach
Save As Draft NA Button NA NA Clicking on this button will save data in

editable form
Submit NA Button NA NA Clicking on this button system will

create Farmer willing with id
90
9.6. Proposal
9.6.1. Search Proposal
Scheme Team can search the Proposal status and Proposal details by entering the search parameters on the
search page for respective tabs like for Proposal id, DISCOM and Phone.
Click Transactions -> Proposal
91
Search List Click on View icon to see Details and Click on Edit for update
92
9.6.1.3. Use Case
Use case id UC_ Proposal_ Search Page

Use Case name Proposal
Actors Scheme user
Description This page describes Proposal details as per submitted Proposals
Post conditions Proposal Search List will be displayed
93
Normal Flow . User logins Unified portal

. Click Transactions -> Proposal
. Search list will be displayed
Exceptions NA
Includes NA
Priority NA
Business Enquiry Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Proposal Id 5 Text Box No User input Should be in System
Phone 10 Text Box No User input Accept numeric value
show details
if entered any
New Proposal NA Button No NA Clicking on this button will
take the user at the page from
where Proposal can be created
NA Button NA NA
logout the user
page
creation page
List
on word page
the excel sheet
94
9.6.2. Create Proposal
Scheme admin can create Proposal from the Transaction link after Login.
Click Transactions -> Proposal
95
Click on Create New Proposal
Fill all Details and Click on Submit Button
96
Start
Login with
Scheme Admin
Click on
Transaction
Click Proposal
-> Click Add Proposal
Enter / Update details

and click submit button
Proposal Id will be
created
End
9.6.2.4. Use Case
Create Proposal
Use Case ID UC_ Add Proposal
Use Case Name Add Proposal
ACTORS Scheme user
Description This page describes about the Add Proposal
97

. Click Transactions -> Proposal -> Create New Proposal button
. Proposal will be created

Includes NA
Priority High
Business Rules/ Validation Proposal should be created successfully
Assumptions NA


System
DISCOM/Department NA Text box M Dropdown Should be Present data in

System
Scope of Project 3000 Text Area M User Input Whitespace and Accept
Alpha Numeric Value
Duties Responsibilities 3000 Text Area NM User Input Whitespace and Accept
Alpha Numeric Value
Payment Terms 3000 Text Area M User Input Whitespace and Accept
Alpha Numeric Value
Project Phase
Percentage of Project 10 Text box M User Input Whitespace and Accept

Cost Alpha Numeric Value
Agency 3000 Text box M User Input Whitespace and Accept

Alpha Numeric Value
Terms of Payment 3000 Text box M User Input Whitespace and Accept
Alpha Numeric Value
98
Signing Authority of 50 Text box M User Input Whitespace and Accept

DISCOM Alpha Numeric Value
Name
Designation 50 Text box M User Input Whitespace and Accept

Alpha Numeric Value
In Presence of 50 Text box M User Input Whitespace and Accept Char

Value
Name
Designation 50 Text box M User Input Whitespace and Accept Char

Value
Signing Authority of EESL 50 Text box M User Input Whitespace and Accept Char
Value
Name
Designation 50 Text box M User Input Whitespace and Accept Char

Value
In Presence of 50 Text box M User Input Whitespace and Accept Char

Value
Name
Designation 50 Text box M User input Whitespace and Accept Char

Value
Remark 250 Text Area M User Input Accept Alpha Numeric Value
Document Attachment NA Upload M User Input Allow only pdf. Images

Detail format (JPEG)


information

EESL user

99

system will create unique ID
100
9.7. Agreement
9.7.1. Search Agreement
Scheme Team can search the Agreement status and agreement details by entering the search parameters on
the search page for respective tabs like for Proposal id, Agreement id and DISCOM.
Click Transactions -> Click on Agreement
101
Agreement Search List-->Click on view and edit
102
9.7.1.3. Use Case
Use case id UC_ Agreement_ Search Page

Use Case name Agreement
Actors Scheme Admin
Description This page describes agreement search details
Post conditions Agreement Search List will be displayed
103
Normal Flow  User login-- > Unified portal

 Click Transactions -> Agreement
 Enter Search Parameters -> Search button
 Search list will be displayed
Exceptions NA
Includes NA
Priority NA
Business Agreement Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Proposal Id 5 Text Box No User input Should be in System
Agreement Id 5 Text Box No User input Should be in System
show details
if entered any
Agreement take the user at the page from
where Agreement can be
created as per Proposal
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
104
105
9.7.2. Create Agreement
This section will allow creating agreement against Proposal document. In Agreement section user and vendor
will agree on scope of project, Duties and responsibility, Payment Terms and proposal timeline.
Click Transactions -> Agreement Tab
106
Click on Create New Agreement
Fill Required Fields and Click on Submit Button
107
108
109
9.7.2.4. Use Case
Agreement
Use Case ID UC_ Agreement
Use Case Name Agreement
ACTORS Scheme Admin
Description This page describes about to create Agreement
Post conditions Agreement will be Created successfully
Normal flow / Basic Flow . User login into system
. User will click on Unified Scheme
. Click Transactions -> Agreement -> Create New Agreement
. Fill all mandatory filled
. System generate unique Agreement id.
Includes NA
Priority High
Business Rules/ Validation Agreement should be Accepted successfully
Assumptions NA
Field Name Length Field Name Mandatory Populated Field Specification

By /Validations
Agreement No. 5 Text Box M User Input Accept Numeric Value
Proposal ID 5 Dropdown M User Input Should be Present data in

System

System
110
DISCOM/Department NA Dropdown M User Input Should be Present data in

System
Scope of Project 3000 Text Area M User Input Accept Alpha Numeric
Value
Duties Responsibilities 3000 Text Area M User Input Accept Alpha Numeric
Value
Payment Terms 30 Text Area M User Input Accept Alpha Numeric

Value
Project Phase
Percentage of Project 10 Text Box M User Input Accept Numeric Value

Cost
Agency 50 Text Area M User Input Accept Alpha Numeric

Value
Terms of Payment 30 Text Area M User Input Accept Alpha Numeric

Value
Signing Authority of 50 Text Box M User Input Accept Varchar Value

DISCOM
Name
Designation 50 Text Box M User Input Accept Varchar Value
In Presence of 50 Text Box M User Input Accept Varchar Value
Name
Signing Authority of 50 Text Box M User Input Accept Varchar Value

EESL
Name
In Presence of 50 Text Box M User Input Accept Varchar Value
Name
Remark 250 Text Area M User Input Accept Varchar Value
Document Attachment NA Button M User Input Upload Document (JPEG,

Detail PDF)
111
9.8. LOA
9.8.1. Search LOA
Scheme Team can search the LOA status and LOA details by entering the search parameters on the search
page for respective tabs like for LOA id and Agency name.
Click Transactions -> LOA
112
Search List
113
9.8.1.3. Use Case
Use case id UC_ LOA_ Search Page

Use Case name LOA
Actors Scheme user
Description Scheme User can search LOA details by entering search parameters
114
Normal Flow . User will log-in into the system

. Click Unified Portal Links section-> Scheme> LOA ->
E.g. LOA id and Agency name
Exceptions NA
Includes NA
Priority NA
Business Scheme Admin user can search the details by entering search parameter
rules/Validation
Assumptions NA
Note and issues NA
LOA Id 5 Text Box No User input Should be in System
Agency Name 50 Text Box No User input Should be in System
show details
if entered any
Add New LOA NA Button No NA Clicking on this button will
where LOA can be created0
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
115
9.8.2. Create LOA
This section will allow creating Letter of agreement with vendor as per requirement.
Click Transactions -> LOA
116
Click on Create New LOA
117
118
Confirmation Message with LOA ID
119
120
9.8.2.4. Use Case
LOA
Use Case ID UC_LOA
Use Case Name LOA
ACTORS Scheme Admin
Description This page describes about the Create New LOA
Post conditions LOA Id will be created

Flow . Click Transactions -> LOA
. Click Transactions -> Create LOA --> Fill all the required field
. Click on submit Button
. Clicking on submit button Confirmation message popup with LOA ID
Includes NA
Priority High
Business Rules/ LOA should be created successfully

Validation
Special None
Requirements
Assumptions NA
By
Agency Name NA Dropdown M User Input Should be Present in system
Agency Type NA Dropdown M User Input Should be Present in system
Customer NA Dropdown M User Input Should be Present in system

Name
Nodal Officer NA Dropdown M User Input Should be Present in system

EESL
121
Nodal Officer 50 Input Box M User Input Alpha Numeric value

DISCOM
Start Date NA Calendar M User Input Accept till date only

Picker
END Date NA Calendar M User Input Accept till date only

Picker
Duration NA Dropdown M User Input Should be Present in system
Remark 250 Text Area M User Input Accept Alpha Numeric value
Project Scope 3000 Text Area M User Input Accept Alpha Numeric value
& Work
Activity 50 Text Box M User Input Accept Alpha Numeric value
Timeline 250 Text Box M User Input Accept Alpha Numeric value
Status NA Dropdown M User Input Should be Present in system
Item 15 Dropdown M User Input Should be Present in system
Description 15 Dropdown M User Input Should be Present in system
Stage 300 Text Area M User Input Alpha Numeric Value
Year NA Text Box M Calendar Alpha Numeric Value

Picker
Quantity 15 Text Box M User input Numeric Value
UOM NA Dropdown M User Input Must be in master data
Base Price 10 Text Box M User Input Numeric Value
TAX 10 Text Box M User Input Numeric Value
Total 10 Text Box M User Input Numeric Value

Calculation
Terms of 3000 Text box M User Input Alpha Numeric Value

Payment
Attachment 30 Text Box M User Input Attachment must be in Pdf and Jpg
Details format
+ Add Row NA Button NA NA Clicking on this button will add new row
where user can fill related information
122
-Delete Row NA Button NA NA Clicking on this button will delete row

where user can delete chose related
information

EESL user

editable form
Submit NA Button NA NA Clicking on this button system will create

unique Project ID
123
9.9 PO
9.9.1. Search PO
Scheme Team can search the PO status and PO details by entering the search parameters on the search page
for respective tabs like for LOA id, PO id and Contact Person Name.
Click Transactions -> PO
124
PO Search List
125
9.9.1.3. Use Case
Use case id UC_ PO_ Search Page

Use Case name PO
Actors Scheme user
Description This page describes to search PO list which saved in system
Post conditions PO Search List will be displayed
126
Normal Flow . User login->Click on Unified portal

. Click Transactions ->PO
Exceptions NA
Includes NA
Priority NA
Business PO Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
LOA Id 5 Text Box No User input Should be in System
PO Id 5 Text Box No User input Should be in System
Contact Person 15 Text Box No User input Should be in System
Name
show details
if entered any
Add New PO NA Button No NA Clicking on this button will
where PO can be creating
against per LOA
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
127
9.9.2. Create PO
This section will allow creating PO against Letter of agreement with vendor as per requirement. PO is sub
quantity of LOA which every time deducts from LOA quantity.
Click Transactions -> PO
Select LOA Number from Dropdown
128
129
According to LOA, PO will Show -->Click on Create PO Button
130
9.9.2.4. Use Case
PO
Use Case ID UC_PO_ Creation
Use Case Name PO
131
ACTORS Scheme user
Description This page describes about the create PO against LOA
Post conditions PO will be created successfully
Normal flow / Basic . User login -->Click on Unified portal

Flow . Click Transactions -> Click on Create PO
. Enter Create PO
. Fill all mandatory parameter
. System generate unique PO id
Includes NA
Priority High
Business Rules/ PO should be created successfully

Validation
Special None
Requirements
Assumptions NA
By
LOA No / NA Dropdown M User Input Should be Present in system

Name
LOA Date NA Calendar M User Input It must take future date more than 5
Picker years
PO Date NA Calendar M User Input It must take future date more than 5
Picker years
Vender Code NA Dropdown M User Input Should be Present in system
City 50 Text Box M User Input Alpha Numeric value
Pin code 6 Text Box M User Input Numeric value
132
Address 250 Text Box M User Input Alpha Numeric value
Contact Person 50 Text Box M User Input Alpha Numeric Value only
Mobile 10 Text Box M User Input Numeric Value only

Number
Shipping 30 Text Box M User Input Accept Alpha Numeric value

Method
Item Details 5 Text Box M Auto Accept Alpha Numeric value

populate
Payment 3000 Text Area M User Input Accept Alpha Numeric value
Terms
Delivery Terms 3000 Text Area M User Input Accept Alpha Numeric value
+ Add Row NA Button NA NA Clicking on this button will add new row
where user can fill related information
-Delete Row NA Button NA NA Clicking on this button will delete row

where user can delete chose related
information
Preview NA Button NA NA Clicking on this button will show EESL PO

details which submitted by EESL user

editable form
Submit NA Button NA NA Clicking on this button system will create

PO id
133
9.10. Indent
9.10.1. Search Indent
Scheme Team can search the indent status and indent details by entering the search parameters on the
search page for respective tabs like for indent id and DISCOM.
Click Transactions -> Indent
134
**Click on Search Button
135
9.10.1.3. Use Case
Use case id UC_ Indent_ Search Page

Use Case name Indent
Actors Scheme user
Description This page describes about the Search Indent
Post conditions Indent Search List will be displayed
Normal Flow . User login-- >Click Unified portal
. Click Transactions ->indent
Exceptions NA
Includes NA
Priority NA
Business Indent Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Indent Id 5 Text Box No User input Should be in System
DISCOM 5 Text Box No Dropdown Should be in System
show details
if entered any
Add New Indent NA Button No NA Clicking on this button will
where Indent can be created
NA Button NA NA
logout the user
as Task List
136
on word page
the excel sheet
137
9.10.2. Create Indent
Scheme admin can create indent from the Transaction link after login.
Click Transactions -> Click on Indent
138
Click on Add New Indent Button
Fill all the Required Field ->Click on Submit Button
139
140
9.10.2.4. Use Case
Use Case ID UC_ Indent creation
Use Case Name Indent
ACTORS Scheme user
Description This page describes create new indent as per farmer willingness
Post conditions Indent will be created successfully
Normal flow / . User login- >Click on Unified portal

Basic Flow . Click Transactions -> Indent-> Create new Indent
. Fill Mandatory details
. Click on Submit Button
. System generate unique id.
Includes NA
Priority High
Business Rules/ Indent will be created successfully

Validation
Special None
Requirements
Assumptions NA
By
DISCOM NA Dropdown M User Input Should be Present in system
Agreement NA Dropdown M User Input Should be Present in system

Number
Circle NA Dropdown M User Input Should be Present in system
Manufacturer 15 Text Box M User Input Accept Alphanumeric Value with

whitespace
141
Warehouse 50 Text Box M User Input Accept Alphanumeric Value with

whitespace
Nodal Officer & 15 Text Box M User Input Accept Alphanumeric Value with
Number whitespace
Panel Pump 15 Input Box M User Input Numeric Value only and more than
Count Total Sanction Quantity
PO Number NA Dropdown M User Input Should be Present in system
Manufacturing NA Calendar M User Input Pick only current and previous date
Completed On Picker not future date
Proposed PDI NA Calendar M User Input Pick only current and previous date
Picker not future date
Actual PDI NA Calendar M User Input Pick only current and previous date
Created On NA Calendar M User Input Pick only current and previous date
Created By 50 Text Box M User Input Accept Alphanumeric Value with

whitespace
No. of Former 15 Text Box M User Input Accept Alphanumeric Value with
Submitted whitespace
PO Number 15 Text Box M User Input Accept Alphanumeric Value with

whitespace
Barcode 20 Text Box M User Input Accept Alphanumeric Value with

whitespace
New Pump 15 Text Box M User Input Accept Alphanumeric Value with
Model whitespace
Size 15 Text Box M User Input Accept Alphanumeric Value with

whitespace
Make 15 Text Box M User Input Accept Alphanumeric Value with

whitespace
Add Control 15 Text Box M User Input Accept Alphanumeric Value with
Panel Detail whitespace
Barcode
+ Add Row NA Button NA NA Clicking on this button will add new

row where user can fill related
information
142
-Delete Row NA Button NA NA Clicking on this button will delete

row where user can delete chose
related information
Preview NA Button NA NA Clicking on this button will show

EESL indent details which
submitted by EESL user
Save As Draft NA Button NA NA Clicking on this button will save

data in editable form

create Indent id
143
10. DISCOM Transaction
10.1. Awareness Proposal
10.1.1. Search Awareness Proposal
DISCOM Team can search the Awareness Proposal status and awareness details by entering the search
parameters on the search page for respective tabs like for awareness ID, Awareness name, created from,
created to and status.
Click on Transaction --> Click on Awareness Proposal
144
145
10.1.1.4. Use Case
Use case id UC_ Awareness_ Search Page

Use Case name Awareness Proposal Search Page
Actors DISCOM user
Description DISCOM User can search the details by entering search parameters
146
Normal Flow . User will visit Login pageClick on unified portal

. Click Unified Portal Links section-> Scheme> Awareness Proposal ->
E.g. Awareness ID, Awareness name, created from, created to and
status.
Exceptions NA
Includes NA
Priority NA
Business DISCOM user can search the details by entering search parameter
rules/Validation
Assumptions NA
Note and issues NA
Awareness ID 5 Dropdown No User input Awareness id, allow only
numeric value
Awareness Name 50 Dropdown No User input Agency name should exist in
data base
Created From NA Input Box No Calendar Picker Must accept only past and
current date
Created to NA Input Box No Calendar Picker Must accept only past and
current date
show details
if entered any
Awareness take the user at the page from
where Awareness Proposal
will be created
NA Button NA NA
logout the user
as Task List
147

on word page
the excel sheet
148
10.1.2. Create Awareness Proposal
DISCOM user can create Awareness from the Transaction link after Login.
Click on Transaction--- >Awareness Proposal
149
Fill all the Required Field-->Next --> Click on Submit Button
150
After click on Submit  Select User for Approval from Dropdown and Click on Submit
151
After Click on Submit Button Confirmation Message popup with Awareness Id
152
Start
Login with
Scheme Admin
Click Main
Navigation Icon ->
Click Transaction
Click Awareness
Proposal
-> Click Add New
Awareness
Fill Mandatory
details -> Submit
button
Select Desired
User to send for
Approval ->
Submit button
Confirmation
Message will be
displayed
End
10.1.2.4. Use Case
Awareness Proposal
Use Case ID UC_ Awareness _ Proposal
Use Case Name Add Awareness Proposal
ACTORS DISCOM user
Description This page describes about the create new Awareness proposal
Post conditions New Awareness will be created successfully
153
Normal flow / Basic . User login-- > Unified portal

Flow . Click Transactions -> Awareness Proposal -> Create Awareness
. Fill Mandatory details and send for approval
. After click on Submit Button Confirmation Message will pop up with id
Includes NA
Priority High
Business Rules/ Awareness Proposal will be created successfully

Validation
Special NA
Requirements
Assumptions NA

Awareness Type NA Dropdown M User Input Should be Present data in

System
Language NA Dropdown M User Input Should be Present data in

System
Awareness Name 50 Text Box M User Input Should accept Varchar with
special char
Awareness Objective 50 Text Box M User Input Should accept Varchar with
special char

System

System
Division NA Dropdown M User Input Should be Present data in

System

System
154
Address 250 Text area M User Input Should accept Varchar with
special char
Pin Code 06 Text Box M User Input Accept Numeric Value
Start Date NA Calendar M User Input Calendar Picker

Picker
End Date NA Calendar M User Input Calendar Picker

Picker
Invitees Detail 50 Text Box M User Input Should accept Varchar with
Organisation Name special char
Name 50 Text Box M User Input Accept Char value
Phone 10 Text Box M User Input Accept Numeric Value
Email 50 Text Box M User Input Accept Alpha Numeric Value
EESL Employee List NA Dropdown M User Input Should be Present data in

System
Name
Designation NA Text Box M Auto Auto Populate

populate
Phone NA Text Box M Auto Auto Populate

populate
Email NA Text Box M Auto Auto Populate

populate
External Party List NA Dropdown M Auto Should be Present data in

populate System
Type
Name 50 Text box M User input Accept Char value
Phone 10 Text box M User Input Accept Numeric value
Email 50 Text box M User Input Accept whitespace with

Varchar
Additional Details 5 Text Box M User Input Accept Numeric Value
Expected No. Of Enquiry
Expected Budget Cost 8 Text Box M User Input Accept Numeric Value
(in Rs.)
155
Expense Name 50 Text Box M User Input Accept Alpha Numeric Value
Expense Cost (in Rs.) 10 Text Box M User Input Accept Numeric Value
Remaining Allocated NA Text Box M Auto Auto populate

Budget populate
Total Estimated Cost (in NA Text Box NM Auto Auto populate

Rs.) populate
Remark 250 Text Area M User Input Accept Varchar with special
char


information
Previous NA Button NA User Input System redirect to previous

page

EESL user


system will create unique
Project ID with constituency
156
10.1.3. Approve / Reject Awareness Proposal
Scheme admin or Approver can Approve/Reject the received Awareness Proposal from the Transaction link
after login.
157
Click on Accept Button for Approval
158
After click on OK button
159
Start
Login with
Scheme Admin
Credentials
Click Main Navigation

Icon -> Click
Transactions ->
Click Awareness
Proposal -> Search
Click View Details

Icon
Enter Rejection
Remarks and click
Status will be
changed as Draft
Accepted
Acceptance
confirmation will
be changed as
Approved
End
10.1.3.4. Use Case
Approve / Reject Awareness Proposal

Use Case ID UC_ Approve/Reject Awareness Proposal
Use Case Name Approve /Reject Awareness Proposal
ACTORS Scheme user
Description This page describes about the Approve /Reject Awareness Proposal
160
Includes NA
Priority High
Assumptions NA

By /Validations
the page from where
Awareness Proposal can be
approved or Rejected
Approve the Awareness
proposal and status will be
changed as Approved
Reject the Awareness
proposal and status will be
changed as Draft
NA Button NA NA
logout the user
page
creation page
Navigation Icon NA Icon NA NA user on the Profile Edit, App
as well as Task List
161
10.2. Awareness Outcome
10.2.1. Search outcome
DISCOM user can search the Awareness Outcome status and awareness outcome details by entering the
search parameters on the search page for respective tabs like for awareness outcome ID, Awareness
outcome name and status.
Click on Unified Scheme
162
Click Search
163
10.2.1.3. Use Case
Use case id UC_ Awareness_ Outcome_ Search Page

Use Case name Awareness Outcome Search Page
Actors DISCOM user
Description DISCOM User can search the details by entering search parameters
164

. Click Unified Portal Links section-> Scheme> Awareness Outcome ->
E.g. Outcome ID, Awareness outcome name and status.
Exceptions NA
Includes NA
Priority NA
rules/Validation
Assumptions NA
Note and issues NA
Outcome ID 5 Dropdown No User input Awareness outcome id allow
only numeric value
Outcome Name 50 Dropdown No User input Agency name should exist in
data base
show details
if entered any
Outcome take the user at the page from
where Outcome.
NA Button NA NA
logout the user
as Task List
on word page
165
the excel sheet

166
10.2.2. Create Outcome
DISCOM user can create Awareness Outcome from the Transaction link after Login; however, awareness
outcome can be created from two ways. One by clicking on + (Add Outcome) from the Awareness search list,
secondly clicking on Awareness Outcome tab -> Add Outcome button
First way to create Awareness Outcome ->Click Transactions -> Awareness Proposal
Click Search
167
Second Way to create Awareness Outcome: Click Main EESL LOGO -> Click Transactions -> Awareness
Outcome -> Select Awareness Id
Select Awareness ID And click on Next Button
168
Fill All Details and Click on Next Button
169
Select desired user whom Awareness Outcome to be sent for Approval
Submission confirmation message
170
Start
Login with
Scheme Admin
Credentials

Icon -> Click
Transactions ->
1- Click Awareness
2- Awareness Outcome
Proposal -> Search ->
-> Add Outcome->
Click + Icon (Add
Select Awareness Id
Outcome)
Awareness Outcome Creation

page -> Fill Mandatory Details
and submit for Approval
End
10.2.2.4. Use Case
Awareness Outcome
Use Case ID UC_ Awareness _ Outcome
Use Case Name Awareness outcome
ACTORS DISCOM user
Description This page describes about the Add Awareness Outcome
Post conditions Awareness Outcome will be created successfully

171
Flow . Click Transactions -> Awareness Outcome

. Search list will be displayed -> Click + Icon (Add Outcome)
. Awareness Outcome page will be opened
. Fill all mandatory filled
. System generate unique id
Includes NA
Priority High
Business Rules/ Awareness Outcome should be created successfully

Validation
Special None
Requirements
Assumptions NA

Awareness ID NA Dropdown M User Input Should be Present data in

System
Awareness Name NA Text Box M Auto Should accept Varchar with

Total Enquiry Received 08 Text Box M Auto Should accept Varchar with
EESL Employee List 50 Text Box M Auto Should accept Varchar

Populate
Name
Designation 50 Text box M Auto Should accept Varchar

populate
Phone 10 Text Box M Auto Should accept Numeric

populate
Email NA Text Box M Auto Should accept Varchar with

populate special char
172
External Party List NA Text Box M Auto Should be Present data in

populate System
Type
Name 50 Text box M Auto Should be Present data in

populate System
Phone 10 Text box M Auto Should be Present data in

populate System
Email 50 Text box M User Input Should be Present data in

System
Participants Details 50 Text box M User Input Should be allow Varchar
Department Name
Person Name 50 Text box M User Input Should allow char
Designation 50 Text box M User Input Should allow Varchar
Mobile 10 Text box M User Input Should allow only numeric
Email id 50 Text box M User Input Should allow Varchar and

special char
Attachment details 20 Text box M User Input Should allow Varchar and
special char
Browse File NA Upload M User Input Only allow PDF, JPEG, JEP
Additional Details NA Text box M Auto Should be Present data in

populate System
Estimated cost (In Rs.)
Actual Cost involved (in 8 Text box M Auto Should be Present data in
Rs.) populate System
Remaining Allocated NA Text box M Auto Auto populate

Budget populate
Remark 250 Text box M User Input Should allow Varchar and
special char
Expense Name 50 Text box M User Input Should allow Varchar and
173
special char
Estimated Cost 8 Text box M User Input Allow only Numeric
Actual cost 8 Text box M User Input Allow only Numeric
Attach Invoice NA Upload M User Input Only allow PDF, JPEG, JEP
10.2.3. Approve / Reject Awareness Outcome
Scheme admin or Approver can Approve/Reject the received Awareness Outcome from the Transaction link
after login.
Click Transactions -> Awareness Outcome
174
Click on Search
Outcome Search List Page ->View Detail
175
Click Accept or Reject button
176
Recetion Confirmation Message
177
Start
Login with
Scheme Admin
Credentials

Icon -> Click
Transactions ->
Click Awareness
Outcome -> Search
Click View Details

Icon
Enter Rejection
Remarks and click
Status will be
changed as Draft
Accepted
Acceptance
confirmation will
be changed as
Approved
End
10.2.3.4. Use Case

Use Case ID UC_ Approve/Reject Awareness Outcome
Use Case Name Approve /Reject Awareness Outcome
ACTORS Scheme user
Description This page describes about the Approve /Reject Awareness Outcome
. User will see Main Navigation Icon on the Transaction
178

Includes NA
Priority High
Assumptions NA

By /Validations
the page from where
Rejected
Approved
Draft
NA Button NA NA
logout the user
page
creation page
Navigation Icon NA Icon NA NA user on the Profile Edit, App
as well as Task List
179
10.3. Survey
10.3.1. Search Survey
DISCOM user can search the Survey status and Survey details by entering the search parameters on the
search page for respective tabs like for Survey ID, consumer name and Mobile no.
Click on Survey
180
Search List
181
10.3.1.3. Use Case
Use case id UC_ Survey_ Search Page

Use Case name Survey Search Page
Actors DISCOM user
Description DISCOM user can search survey details by entering search parameters
. Click Unified Portal Links section-> Scheme> Survey ->
E.g. Survey ID, consumer name and Mobile no
Exceptions NA
182
Includes NA
Priority NA
rules/Validation
Assumptions NA
Note and issues NA
Survey ID 5 Text Box No User input Awareness outcome id allow
only numeric value
Consumer Name 50 Dropdown No User input Agency name should exist in
data base
Mobile no 10 Input box No Dropdown Must be only 3 status;
show details
if entered any
Survey take the user at the page from
where Survey can be created
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
183
10.3.2. Create Survey
This section will allow creating survey as per DISCOM requirement after approval of awareness outcome.
Survey will manage all details about farmer and pump. It shows primary information about farmer while
awareness proposal and outcome manage at farmer location. Survey basically takes care by PMC and
DISCOM stakeholder.
184
185
Confirmation Message with Survey id
186
10.3.2.4. Use Case
Survey
Use Case ID UC_ Survey
Use Case Name Survey
ACTORS DISCOM user
Description This page describes about the Create Survey

187
Flow . Click Transactions -> Survey -> Create New Survey

. Survey will be created
Includes NA
Priority High
Business Rules/ Survey should be created successfully

Validation
Special None
Requirements
Assumptions NA

General Information 50 Text box M User Input System allow char
Consumer Name
Father Name 50 Text box M User Input System allow char
Transformer Location 20 Text box M User Input Accept Alpha Numeric Value
and special Char
Transformer Name code 10 Text box M User Input Accept Alpha Numeric Value
and special Char
Service Connection 20 Text box M User Input Accept Alpha Numeric Value
Number and special Char
Mobile Number 10 Text box M User Input Accept Numeric Value
Sanction Load 8 Text box M User Input Accept Alpha Numeric Value
Date NA Text box M Calendar Calendar Picker

Picker

System
188
District NA Text box M Dropdown Should be Present data in

System
ID Type NA Text box M Dropdown Should be Present data in

System
ID Number NA Text box M User Input Accept Numeric Value
DIVISION NA Text box M Dropdown Should be Present data in

System
DISCOM NA Text box M Dropdown Should be Present data in

System
Village Name 50 Text box M User Input Accept Alpha Numeric Value
Document Attachment NA Browse M User Input Accept Pdf, Doc, JPEG

Button
Pump Set Details NA Text box M User Input Should be Present data in
System
Pump Set Rating
(HP/KW)
Age of Pump Set 5 Text box M User Input Accept Alpha Numeric Value
Pump Manufacturing NA Text box M Calendar Should be Present data in

Date Picker System
No. of Stage in Case 5 Text box NM User Input Accept Numeric Value
Submersible
Performance of Pump 5 Text box NM User Input Accept Alpha Numeric Value
Parameter Voltage(v)
Current (I) 5 Text box M User Input Should be Present data in

System
Input Power (KW) 5 Text box M User Input Accept Numeric Value
Power factor 5 Text box NM User Input Accept Numeric Value
Time Taken to fill Time 5 Text box NM User Input Accept Numeric Value
Flow (LPS) 5 Text box NM User Input Accept Numeric Value
Iteration I, II, III 5 Text box M User Input Accept Numeric with
decimal Value
Average / Total NA Text box M Auto Auto Populate
189
Populate
Total Bore depth (FT) 5 Text box M User Input Accept Alpha Numeric Value
Pump Installation Depth 5 Text box M User Input Accept Alpha Numeric Value
(FT)
Water Level from 5 Text box NM User Input Accept Alpha Numeric Value
Ground (FT) Min/Max
Elevation of Discharge 5 Text box NM User Input Accept Alpha Numeric Value
Point (FT)
Bore Size (inch) 5 Text box NM User Input Accept Alpha Numeric Value
Pump Size (inch) 5 Text box M User Input Accept Alpha Numeric Value
Delivery Pipe Type 5 Text box M User Input Accept Alpha Numeric Value
Delivery Pipe Length 5 Text box NM User Input Accept Alpha Numeric Value
Delivery Pipe Diameter 5 Text box NM User Input Accept Alpha Numeric Value
(inch)
Pressure (kg/sq. cm if 5 Text box NM User Input Accept Alpha Numeric Value
required)
Corp Cultivated 5 Text box NM User Input Accept Alpha Numeric Value
Method of 5 Text box NM User Input Accept Alpha Numeric Value

Irrigation/required Area
Other Observation: 250 Text Area NM User Input Accept Alpha Numeric Value
190
10.4. Farmer Willing
10.4.1. Search farmer Willingness
DISCOM user can search the Willingness status and willingness details by entering the search parameters on
the search page for respective tabs like for state, District, DISCOM, from date and to date.
Click on Farmer Willing Form
191
Search List-->Click on View icon to see details
192
10.4.1.3. Use Case
Use case id UC_ Willingness_ Search Page

Use Case name Willingness form
Actors DISCOM user
Description DISCOM user can search the details by entering search parameters
. Click Unified Portal Links section-> Scheme> Willingness form ->
E.g. State, District, DISCOM, from date and to date.
Exceptions NA
Includes NA
Priority NA
193
rules/Validation
Assumptions NA
Note and issues NA
State NA Dropdown No User input Should be in System
District NA Dropdown No User input Should be in System
From date NA Calendar No User input Accept Present and Past date
Picker only
To date NA Calendar No User input Accept Present and Past date
Picker only
show details
if entered any
New willingness NA Button No NA Clicking on this button will
form take the user at the page from
where Willing Created can be
NA Button NA NA
logout the user
page
creation page
List
on word page
the excel sheet
194
10.4.2. Create willing ness form
This section will allow to DISCOM user can create farmer willingness form against survey. Willingness form is
full of details about farmer and pump.
Click on Willingness Form
195
196
After Clicking Submit Button
10.4.2.4. Use Case
Farmer Willing Form
Use Case ID UC_ Farmer_ Willingness_ Form
197
Use Case Name Farmer Willing Form
ACTORS DISCOM user
Description This page describes about to create Willingness form against survey or bulk upload
Post conditions Willingness form will be created successfully
Normal flow / Basic . User login -> Unified portal

Flow . Click Transactions -> Farmer Willingness form -> Create Willingness
. Farmer Willingness will be created
Includes NA
Priority High
Business Rules/ Farmer Willing Form should be created successfully

Validation
Special None
Requirements
Assumptions NA
By
Consumer Name 50 Text box M Auto Should be Present data in System

populate
Father Name 50 Text box M Auto Should be Present data in System

populate
Mobile Number 10 Text box M User Input Should be Present data in System
Date of NA Text box M Calendar Should select current or future date

Installation Picker only
198
Agency Code 20 Text box M User Input Should Accept whitespace,

Alphanumeric value
Service NA Text box M Dropdown Should be Present data in System

Connection
Number
State NA Text box M Auto Should be Present data in System

populate
District NA Text box M Auto Should be Present data in System

populate
Circle Name NA Text box M Auto Should be Present data in System

populate
Division Name NA Text box M Auto Should be Present data in System

populate
DISCOM NA Text box M Auto Should be Present data in System

populate
Village Name 50 Text box M User Input Should Accept whitespace,

populate
Address 250 Text Area M User Input Should Accept whitespace,

populate
Section Office 50 Text box NM User Input Should Accept whitespace,

populate
DTR 20 Text box M User Input Should Accept whitespace,

Location/Number Alphanumeric value
Feeder Name 50 Text box M User Input Should Accept whitespace,

Alphanumeric value
Attachment NA Browse M User Input Accept Pdf, Doc, JPEG

Detail button
Pump Set Rating 10 Text box NM User Input Should Accept whitespace,
populate
Total Bore Depth 6 Text box M User Input Should Accept whitespace,
(FT.) & Auto Alphanumeric value
populate
199
Pump Installation 6 Text box M User Input Should Accept whitespace,

Depth (FT.) Alphanumeric value
Water Level from 6 Text box NM User Input Should Accept whitespace,
Ground (FT.) Alphanumeric value
min/max
Bore Size (Inch) 6 Text box M User Input Should Accept whitespace,
Alphanumeric value
Site Location 30 Text box M User Input Should Accept whitespace,

Alphanumeric value
Age of Pump Set 30 Text box M User Input Should Accept whitespace,
Alphanumeric value
Delivery Pipe 20 Text box M User Input Should Accept whitespace, Should
Length (FT.) Accept whitespace, Alphanumeric value
Delivery Pipe Size 6 Text box M User Input Should Accept whitespace,
(inch) Alphanumeric value
10 Text box NM User Input Should Accept whitespace,

Elevation of Alphanumeric value
Discharge Point
Height (ft.)
Pump Size 6 Text box M User Input Should Accept whitespace,

Alphanumeric value

EESL user
Attachment NA Browse M Browse Only <Pdf, JPEG> should be allowed

Attach Attach

editable form

create Farmer willing Form with unique
Project ID
200
10.5. Indent
10.5.1. Search Indent
DISCOM user can search the indent status and indent details by entering the search parameters on the
search page for respective tabs like for indent id and DISCOM.
Click on Indent
201
10.5.1.3. Use Case
Use case id UC_ Indent_ Search Page

Use Case name Indent
Actors Scheme user
Description This page describes about the Search Enquiry
202

Normal Flow . User logins-- >Click on Unified portal
. Click Transactions ->indent
Exceptions NA
Includes NA
Priority NA
Business Indent Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Indent Id 5 Text Box No User input Should be in System
show details
if entered any
Add New Indent NA Button No NA Clicking on this button will
where Indent can be created
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
203
10.5.2. Create Indent
DISCOM user can create indent from the Transaction link after login.
Click on Indent Tab
204
205
10.5.2.4. Use Case
Use Case ID UC_ Indent creation
Use Case Name Indent
ACTORS DISCOM user
206
Description This page describes about the Add new indent
Post conditions New Indent will be created successfully
Normal flow / . User login-- >Unified portal

Basic Flow . Click Transactions -> Indent-> Create new Indent
Includes NA
Priority High
Business Rules/ Indent will be created successfully

Validation
Special None
Requirements
Assumptions NA
By
DISCOM NA Dropdown M User Input Should be Present in system
Agreement NA Dropdown M User Input Should be Present in system

Number
Circle NA Dropdown M User Input Should be Present in system
Manufacturer 15 Text box M User Input Accept Alphanumeric Value
Warehouse NA Dropdown M User Input Should be Present in system
Nodal Officer & 50 Text Box M User Input Accept Numeric Value
Number
Panel Pump 15 Input Box M User Input Numeric Value only and more than
Count Total Sanction Quantity
PO Number NA Dropdown M User Input Should be Present in system
Manufacturing NA Calendar M User Input Pick only current and previous date
Completed On Picker not future date
207
Proposed PDI NA Calendar M User Input Should be Present in system

Picker
Actual PDI NA Calendar M User Input Should be Present in system

Picker
Created On NA Calendar M User Input Should be Present in system

Picker
Created By 50 Text Box M User Input Should be Present in system
No. of Former 15 Text Box M User Input Accept Numeric Value

Submitted
PO Number 15 Text Box M User Input Accept Numeric Value
Barcode 15 Text Box M User Input Accept Alphanumeric Value
New Pump 15 Text box M User Input Accept Alpha Numeric Value
Model
Size 15 Text Box M User Input Accept Numeric Value
Make 15 Text Box M User Input Accept Alpha Numeric Value
Add Control 15 Browse M User Input Accept Numeric Value

Panel Detail
Barcode
+ Add Row NA Button NA NA Clicking on this button will add new

row where user can fill related
information
-Delete Row NA Button NA NA Clicking on this button will delete

row where user can delete chose
related information

EESL indent details which
submitted by EESL user


create Indent id
208
10.6. Bulk Upload
10.6.1. Bulk upload
DISCOM user can upload farmer details from the Transaction link after login.
Click on Bulk Upload
209
210
211
10.6.1.4. Use Case
Use Case ID UC_ Bulk Upload
Use Case Name Bulk upload
ACTORS DISCOM user
Description This page describes about the upload farmer willingness details
Post conditions New Indent will be created successfully
Normal flow / . User logins Unified portal

Basic Flow . User will see Main Navigation Icon on the left-hand side
. Click Transactions -> Bulk upload-> Bulk Upload
Includes NA
Priority High
Business Rules/ Bulk upload will be created successfully

Validation
Special None
Requirements
Assumptions NA
By
Download NA Download NM User Input Excel format

Excel Data
Choose Bulk NA Upload M User Input Should be in PDF and Jpg format
Upload File Button
Upload Chosen NA Upload M User Input Should be in PDF and Jpg format
File Button
212
11. ADA Admin Transaction
11.1. Old Pump set Handover
11.1.1. Search Old Pump Set Handover
ADA Team can search the indent status and indent details by entering the search parameters on the search
page for respective tabs like for Old Handover id and DISCOM.
Click on Transaction--> Old Pump set Handover
213
11.1.1.3. Use Case
Use case id UC_ Old Pump_ Handover_ Search Page

Use Case name Old pump set handover
Actors ADA user
Description This page describes about the Search Old Pump set handover
Post conditions Old Pump set handover Search List will be displayed
. Click Transactions ->Old Pump Handover
Exceptions NA
Includes NA
214
Priority NA
Business Old hand pump handover Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Old hand pump 5 Text Box No User input Should be in System
handover Id
show details
if entered any
Add New Old NA Button No NA Clicking on this button will
Pump set take the user at the page from
handover where Old Pump set handover
can be created
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
215
11.1.2. Create Old Pump Set Handover
This section will allow verifying vendor installation as per consent letter. He can select or reject an
installation detail which is posted by Vendor. Verification processes take complete details about pole
installation as per Constituency, district, Block, Village, Beneficiary name, Mobile no, Remark and live latitude
and longitude which capture by mobile application.
Click on Transaction--> Old Pump set Handover
216
Click on Add New Old Pump set
Fill Required Field
217
218
11.1.2.4. Use Case
Old Pump Handover
Use Case ID UC_ Old pump_ Handover
Use Case Name Old Pump Handover
ACTORS ADA user
Description This page describes about the Add old pump handover
Post conditions New Old Pump set handover will be created successfully
Normal flow / Basic . User login-- >Click Unified portal

Flow . Click Transactions -> Old Pump handover -> Add New handover Pump
Includes NA
Priority High
Business Rules/ Old hand pump handover id will be created successfully

Validation
Special None
Requirements
Assumptions NA
By

System

System
Division Name NA Dropdown M User Input Should be Present data in

System
219

System
Village Name 50 Text Box M User Input Accept Alpha Numeric Value
Serial No. 15 Text Box M User Input Accept Numeric Value
Sl. No. should match with EEPS

receipt Note

System
Date NA Calendar M User Input Accept past and present date

Picker
Service Connection No. 15 Text Box M User Input Should be Present data in
System
Item 15 Text Box M User Input Select from system Data
Serial No. 15 Text Box M User Input Accept Numeric Value
UPPCL/PVVNL 15 Text Box M User Input Accept Alpha Numeric Value

Representative
Name
Mobile No. 10 Text Box M User Input Accept Numeric Value
EESL Representative 50 Text box M User Input Accept Alpha Numeric Value
Name
Installation Representative 50 Text Box M Accept Alpha Numeric Value
Name
+ Add Row NA Button NA NA Clicking on this button will add

new row where user can fill
related information

information
220

Old Hand pump handover
details which submitted by ADA
user
Attachment NA Browse M Browse Only <Pdf, JPEG> should be

Attach Attach allowed

Submit NA Button NA NA Clicking on this button system

will create unique Hand pump
handover id
221
11.2.1. Search Installation
ADA team can search the indent status and indent details by entering the search parameters on the search
page for respective tabs like for Installation id and farmer.
222
Click on Transaction--> Installation Tab
Installation Search List
223
11.2.1.4. Use Case
Use case id UC_ Installation_ Search Page

Use Case name Installation
Actors ADA user
Description This page describes about the Search Installation
Post conditions Installation Search List will be displayed
224

. Click Transactions ->Installation
Exceptions NA
Includes NA
Priority NA
Business Installation Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Installation Id 5 Text Box No User input Should be in System
Farmer Name 50 Text Box No User input Should be in System
show details
if entered any
Add Installation NA Button No NA Clicking on this button will
where Installation can be
created.
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
225
11.2.2. Create Installation
ADA user can create installation from the Transaction link after login.
Click on Installation Tab
Click on Add New Installation
226
11.2.2.3. Use Case
Use Case ID UC_ Installation
Use Case Name Installation
ACTORS ADA user
Description This page describes about the Add new installation
Post conditions Installation will be created successfully
Normal flow / . User logins Unified portal

227
Basic Flow . Click Transactions -> installation -> New installation

Includes NA
Priority High
Business Rules/ Installation id will be created successfully

Validation
Special None
Requirements
Assumptions NA
By
Service NA Dropdown M User Input Should be Present in system

Connection No.
Token No. NA Dropdown M User Input Accept Numeric Value
Farmer Name NA auto M User Input System Generated

populate
Father Name NA auto M User Input System Generated

populate
Mobile Number NA auto M User Input System Generated

populate
Address NA auto M User Input System Generated

populate
Pump Detail 15 Input Box M User Input Numeric Value only and more than
Total Sanction Quantity
Pump Type NA Dropdown M User Input Should be Present in system
Sim Card Serial 20 Text Box M User Input Pick only current and previous date
No. not future date
Sim Card Mobile 10 Text Box M User Input Accept Numeric Value
228
No.
Distributed on NA Calendar M User Input Should be Present in system

Picker
Distributed by 50 Text Box M User Input Accept Alpha Numeric Value
Consumer Type NA Dropdown M User Input Should be Present in system
Installed on NA Calendar M User Input Should be Present in system

Picker
Installed by 50 Text Box M User Input Accept Alpha Numeric Value
Status NA Dropdown M User Input Accept Alpha Numeric Value
Latitude 4 Text Box M User Input Accept Numeric Value
Longitude 4 Text b0x M User Input Accept Numeric Value
Installation NA Dropdown M User Input Accept Alpha Numeric Value

Source
Attachment of NA Browse M User Input Accept JPEG and pdf

Farmer Close up
Photo File
Farmer with Old NA Browse M User Input Accept JPEG and pdf
Pump Photo
Farmer NA Browse M User Input Accept JPEG and pdf

Electricity Bill
Photo
Farmer NA Browse M User Input Accept JPEG and pdf

Signature Photo
File
Farmer with NA Browse M User Input Accept JPEG and pdf

Installed Pump
Photo
229
11.3. Verification
11.3.1. Search Verification
ADA user can search the verification status and verification details by entering the search parameters on the
search page for respective tabs like verification id, Name and Phone.
Click on Transaction--> Verification
230
Search List
11.3.1.3. Use Case
Use case id UC_ Verification_ Search Page

Use Case name Verification
Actors ADA user
231
Description This page describes about the details about search Verification
. Click Transactions ->verification
Exceptions NA
Includes NA
Priority NA
Business Verification Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Verification Id 5 Text Box No User input Should be in System
Name 50 Text Box No User input Should be in System
Phone 10 Text box No User input Should be in System
show details
if entered any
Add Verification NA Button No NA Clicking on this button will
where Verification can be
created
NA Button NA NA
logout the user
as Task List
on word page
232

the excel sheet
233
11.3.2. Create Verification
Scheme user can create new verification from the Transaction link after login.
Click on Transaction--> Verification
234
235
11.3.2.4. Use Case
Create Verification
Use Case ID UC_ Verification
Use Case Name Verification
ACTORS ADA user
Description This page describes to create verification about installation pump details against
236
farmer details
Post conditions New verification will be created successfully
. Click Transactions ->Verification

. Click on-> New verification
. Fill all mandatory fields
. System create unique verification id.
Includes NA
Priority High
Business Rules/ Verification will be created successfully

Validation
Special None
Requirements
Assumptions NA
By
Service No. NA Dropdown M User Input Should be Present data in System
Farmer Name 50 Input Text M User Input Auto populate
Install Agency NA Dropdown M User Input Should present in System

Name
Date of NA Calendar M User Input Select Date Present and Past

Installation Picker
Remark 250 Text Area M User Input Accept Alpha Numeric Value
Action NA Dropdown M User Input Should present in System
237
11.4. Assign Pump to Farmers
11.4.1. Search Verification
ADA user can search the Assign Pump to farmer status and Assign Pump details by entering the search
parameters on the search page for respective tabs like for indent id.
Click on Assign Pump to Farmers
Select Indent ID and Click on Search Button
238
11.4.1.3. Use Case
Use case id UC_ Assign pump_ Search Page
239
Use Case name Assign Pump to farmer

Actors ADA user
Description This page describes search Assign Pump details
Post conditions Assign Pump Search List will be displayed
. Click Transactions ->Assign Pump to farmer
Exceptions NA
Includes NA
Priority NA
Business Assign Pump Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Indent Id 5 Text Box No Dropdown Should be in System
show details
if entered any
NA Button NA NA
logout the user
as Task List
240
11.4.2. Create Assign Pump to farmer
ADA user can create Assign Pump to Farmer from the Transaction link after login.
241
11.4.2.4. Use Case
Assign Pump to Farmer

Use Case ID UC_ Assign Pump
Use Case Name Assign Pump to farmer
ACTORS ADA user
Description This page describes about the Assign Pump to Farmer
Post conditions Assign pump to farmer will be created successfully
242

. Click Transactions -> Assign Pump to farmer -> Assign pump
. System generate unique Pump assignment id.
Includes NA
Priority High
Business Rules/ Assign Pump to farmer will be created successfully
Validation
Special None
Requirements
Assumptions NA
243
12. Supplier Transaction
12.1. Dispatch
12.1.1. Search Dispatch
Supplier team can search the Dispatch status and Dispatch details by entering the search parameters on the
search page for respective tabs like for Dispatch id and agency name.
Click on Dispatch
Click on Search
244
Search List
12.4.1.3. Use Case
Use case id UC_ Dispatch Search Page

Use Case name Dispatch
Actors Supplier user
Description This page describes about the Search Dispatch transaction
245
Post conditions Dispatch Search List will be displayed

. Click Transactions ->Dispatch
Exceptions NA
Includes NA
Priority NA
Business Dispatch Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Dispatch Id 5 Text Box No Dropdown Should be in System
Agency Name 50 Text Box No User Input Accept Varchar with white
space
show details
if entered any
Dispatch take the user at the page from
where Dispatch can be created
NA Button NA NA
logout the user
as Task List
on word page
the excel sheet
246

247
12.1.2. Create Dispatch
Supplier user can create Dispatch from the Transaction link after login.
Click on Dispatch
Click on Create Dispatch
248
249
12.1.2.4. Use Case
Dispatch
Use Case ID UC_ Dispatch
Use Case Name Add Dispatch
ACTORS Supplier user
Description This page describes about the Add new Dispatch
250

Post conditions Dispatch will be created successfully
. Click Transactions -> Dispatch -> Create Dispatch
. System generate unique dispatch id
Includes NA
Priority High
Business Rules/ Validation Dispatch will be created successfully
Assumptions NA
By
LOA No. NA Dropdown M User Input Should be Present data in System
Warehouse 50 Text Box M User Input Accept Varchar

Name
Agency Name 50 Text Box M User Input Accept Varchar
Delivery 15 Text Box M User Input Accept Varchar

Challan
Number
Customer 250 Text Area M User Input Accept Varchar

Address
Challan Date NA Calendar M User Input Accept till date only

Picker
Customer 15 Text Box M User Input Accept Alpha Numeric Value

GSTIN Number
Transportation 15 Text Box M User Input Accept Varchar

Mode
Transport 50 Text Box M User Input Accept Varchar
251
Company
Vehicle Name 50 Text Box M User Input Accept Alpha Numeric Value
&Number
Dispatch Date NA Calendar M User Input Accept till date only

picker
Item Name 50 Text Box M User Input Accept Varchar
Item 50 Text Box M User Input Accept Varchar

Description
Quantity 10 Text box M User Input Accept Numeric Value
Attachment Button M User Input Accept JPEG and PDF

Detail
252
12.2. Trip
12.2.1. Search Trip
Supplier user can search the Trip status and trip details by entering the search parameters on the search
page for respective tabs like for Agency, from date and to date.
Click on Trip Tab
253
Click on View icon
254
12.2.1.3. Use Case
Use case id UC_ Trip Search Page

Use Case name Trip
Actors Supplier admin
Description This page describes about the Search Trip
Post conditions Trip Search List will be displayed
. Click Transactions ->Trip
Exceptions NA
Includes NA
Priority NA
Business Trip Search List will be displayed
rules/Validation
Assumptions NA
Note and issues NA
Agency Name 50 Text Box No User Input Accept Varchar with white
space
Start Date NA Text Box No Calendar picker Accept current and previous
date
End Date NA Text Box No Calendar picker Accept current and previous
date
show details
if entered any
NA Button NA NA
logout the user
as Task List
255

on word page
the excel sheet
256
13. Common Messages
13.1. Annexure - 1
S. No. Messages
5.1.1 Invalid User Id and Password!
5.1.2 The following fields xxxxx are mandatory.
5.1.3 Please select <field name>.
5.1.4 Please fill all mandatory fields.
5.1.5 Please select <field name> from the dropdown menu.
5.1.6 Please enter e-mail id in the following format user_name@domain_name.
5.1.7 Content cannot exceed xxx characters.
5.1.8 Selected Date cannot be a future date.
5.1.9 Password is mandatory.
5.1.10 Confirm Password is mandatory.
5.1.11 Old Password is not valid
5.1.12 Acceptance is mandatory.
5.1.13 From date is mandatory.
5.1.14 To Date must be greater than or equals to From Date.
5.1.15 Please enter a numeric value.
5.1.16 Please enter data in proper format. Only alphabets a-z, numbers 0-9 are allowed.
5.1.17 Only alphabets a-z, numbers 0-9, and special characters ‘- ‘, ‘/’ are allowed.
5.1.18 The new password cannot be same as old password.
5.1.19 Password shall be as per password policy.
5.1.20 Please enter Application number.
5.1.21 Date of birth shall not be future date.
5.1.22 No data available in table.
5.1.23 The Application number doesn’t exist.
5.1.24 Password shall be at least 8 & maximum to 15 characters.
5.1.25 Your Password is changed successfully.
257
5.1.26 Password shall be the combination of a-z, 0-9 & Special characters.
5.1.27 Password and Retype password shall be same.
5.1.28 Application submitted successfully.
5.1.29 Please upload the <filetype (.jpg, .pdf,)> file.
5.1.30 Your profile has been updated successfully.
5.1.31 Your session will expire in 30 minutes.
5.1.32 Your session has expired.
5.1.33 You have made five failed login attempts. Please try again after 30 minutes <date, time> or contact your
administrator for the correct username and/or password.
258
13.2. Annexure –2
Sub field / Maximum From

Permissible data / data Mandatory
S. No Field Name List of Sub Strength Master
format
Fields Table
1. Email id NA User_name@domain_name 50 Yes
Alphanumeric, Special
Characters. Only at the rate
(@), full stop (.)and
underscore (_) allowed
2. New NA combination of a-z, 0-9 & 8 to 20 Yes
Password Special characters or more
3. Change NA combination of a-z, 0-9 & 8 to 20 Yes
Password Special characters or more
Forget
Password
4. Mobile Numeric 10 Yes
number Number should be start with
6 or 7 or 8 or 9
5. FAX Numeric 11
6. Remark NA Alphanumeric, special 250

character allowed
7. Date of NA DD-MM-YYYY 10
Birth
8. Name NA Whitespace and alphabet 50
9. Address NA Alphanumeric and special 250

characters. only hyphen (–),
slash (/) and comma (,)
should be allowed
10. Pin code NA Numeric 6
11. District NA District Master NA Yes
259

Agsdm SRS

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Agsdm SRS

Загружено:

Авторское право:

Доступные форматы

AGDSM- Unified Scheme

Software Requirement Specification

Version 0.1 | 09th May 2019

RISL_EESL (Design, Development, Implementation & FMS of Unified

6. Customer Name EESL

7. Project Manager/ Email Debasis Sarangi

8. Customer Contact Details EESL

Prepared Prepared Reviewed Reviewed Approve Approve Change Description

1 Sanjay 09th May

1. RISL (Raj Comp)

2. EESL (Energy Efficiency Services Ltd)

3. CSDC India Pvt. Ltd.

2. Project Summary ...................................................................................................................................... 9

3. Objective of the Project ........................................................................................................................... 9

4. Scope of Document ................................................................................................................................ 10

5. Function Overview ................................................................................................................................. 11

6. System Requirement in Detail ............................................................................................................... 12

7. EESL Scheme Module Overview (login, Forget Password, edit) ....................................................... 13

8. Scheme Master Transaction .................................................................................................................. 22

9. Scheme Admin Transaction .................................................................................................................. 29

9.1.4. Use Case.................................................................................................................................................. 31

9.4. Survey ................................................................................................................................................................. 69

9.5.2.1. Introduction ......................................................................................................................................... 84

9.7. Agreement ......................................................................................................................................................... 101

9.10.1.4. UI Validation Details .................................................................................................................... 136

10. DISCOM Transaction ................................................................................................................................ 144

10.4. Farmer Willing...................................................................................................................................................... 191

11. ADA Admin Transaction ...................................................................................................................... 213

11.3. Verification ........................................................................................................................................................... 230

11.3.1.1. Introduction ................................................................................................................................. 230

12. Supplier Transaction ............................................................................................................................ 244

13. Common Messages .............................................................................................................................. 257

3. Objective of the Project

5.1. Overview of Scheme Process Flow

6. System Requirement in Detail

6.1. Public Interface

6.2. Website Details

7. EESL Scheme Module Overview (login, Forget Password, edit)

7.1. EESL Login

 The SAP ID will be treated as User ID

7.1.2. Functionality Flow Chart

Is User Registered Get Registration

Show Message Invalid

7.1.3. User Login UI Wireframe

7.1.4. Use Case

Use case id UC_ User_ Login

Assumptions User should know its login credentials.

7.1.5. UI Validation Details

Sign In NA Button M NA Clicking on this will validate the

7.2. Change Password

7.2.2. Functionality Flow Details

EESL visit AgDSM portal

Login into the System with login details

After login, click on Change Password

Is confirm password and

7.2.3. Change Password UI

Menu Icon -> Profile

7.2.4. Use Case

Use case id UC_ Change Password

Use Case name Change Password

Actors Scheme user

Preconditions . The scheme user should be logged into the system

. Scheme should enter the old password