E - Municipality SRS

SOFTWARE
REQUIREMENT
Specification
Table of Contents
1.0 Introduction .
1.1 Purpose of this Document .
1.2 Scope of the Development Project
1.3 Definitions, Acronyms, and Abbreviations
1.4 References .
1.5 Overview of Document ..
2.0 General Description ..
2.1 Product Perspective .
2.2 Overview of Functional Requirements ..
2.3 Overview of Data Requirements ..
2.4 General Constraints, Assumptions, Dependencies, Guidelines .
2.5 Approval System
3.0 Specific Requirements .
3.1 Detailed Description of Functional Requirements
3.2 Performance Requirements .
3.3 Quality Attributes .
3.4 Common Functions and procedures used in ERP
4.0 Documentation Requirements (Module Wise)
4.1 Financial Accounts
4.1.1 Brief Description
4.1.2 User Requirements
4.1.3 Flow Chart
4.1.4 Algorithms
4.1.5 Data Flow Diagram
4.1.6 Entity Relationship Diagram
4.1.7 Activity Diagram
4.1.8 MIS Reports
4.2
Payroll
4.2.3 Flow Chart
4.2.4 Algorithms
4.2.8 MIS Reports
4.3
Pension
Page -
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
User Requirements
Flow Chart
Algorithm
Data Flow Diagram
Entity Relationship Diagram
Activity Diagram
MIS Reports
4.4
Property Tax
4.4.3 Flow Chart
4.4.4 Algorithms
4.4.8 MIS Reports
4.5
PHE
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.5.7
4.5.8
Brief Description
User Requirements
Flow Chart
Data Flow Diagram
Activity Diagram
MIS Reports
Algorithms
4.6
Birth & Death

4.6.3 Flow Chart
4.6.4 Algorithms
4.6.8 MIS Reports
4.7
Revenue
4.7.3 Flow Chart
4.7.4 Algorithms
4.7.8 MIS Reports
Page -
4.8
Central Purchase
4.8.3 Flow Chart
4.8.4 Algorithms
4.8.8 MIS Reports
4.9
Jankarya
4.9.3 Flow Chart
4.9.4 Algorithms
4.9.8 MIS Reports
4.10 Workshop
4.10.1
4.10.2
4.10.3
4.10.4
4.10.5
4.10.6
4.10.7
4.10.8
Brief Description
User Requirements
Flow Chart
Algorithms
Data Flow Diagram
Activity Diagram
MIS Reports
4.11 Fire Brigade

4.11.1
Brief Description
4.11.2
User Requirements
4.11.3
Flow Chart
4.11.4
Algorithms
4.11.5
Data Flow Diagram
4.11.6
4.11.7
Activity Diagram
4.11.8
MIS Reports
4.12 Legal Section

4.12.1
Brief Description
4.12.2
User Requirements
4.12.3
Flow Chart
4.12.4
Algorithms
4.12.5
Data Flow Diagram
Page -
4.12.6
4.12.7
4.12.8
4.13 Udhyaan
4.13.1
4.13.2
4.13.3
4.13.4
4.13.5
4.13.6
4.13.7
4.13.8
4.14 Zoo
4.14.1
4.14.2
4.14.3
4.14.4
4.14.5
4.14.6
4.14.7
4.14.8

Activity Diagram
MIS Reports
Brief Description
User Requirements
Flow Chart
Algorithms
Data Flow Diagram
Activity Diagram
MIS Reports
Brief Description
User Requirements
Flow Chart
Algorithms
Data Flow Diagram
Activity Diagram
MIS Reports
5.0 Solution Methodology

5.1 Approach
5.2 Development Architecture
1. INTRODUCTION
GMCs ERP is a true enterprise solution that integrates function across an organization and
enables E-Governance in future. It integrates with existing systems, financials, documenting,
cashiering, fields data collection etc. to make the organization a seamless functioning entity. The
software has got an exhaustive number of modules, which take care of each and every operation of
Gwalior Municipal Corporation. The main aim of computerization is to automate and standardize the
Page -
operations of the office of the commissioner, office of all the heads of departments, Zonal offices and
other related entities working under GMC. Further, we have established their connectivity with the
head office and with other with hi-tech Microwave Wireless Radio Networking system. This Software
Requirement Specification provides information of what must the proposed system do, which will help
the designers/developers to design an error free, and user-friendly software.
1.1 Purpose
This document describes the system requirements for the computerization of Gwalior Municipal
Corporation, which will allow users to support reliable and fast work. We have provided specific
requirements, including the data input and output as seen from a users point of view. Throughout this
document all functional and some nonfunctional requirements are formalized while defining the whole
software project scope.
Intended Audience and Reading Suggestions
The documented is intended for GMCs ERP:Computerization Project Of GMC and its functioning
areas.
QP1
QP2
QP3
QP Query Poster (User)

HD Help Desk
T - Team
TM Team Member
GMC
HD1
T1
1
TM11
HD2
T2
TM12
TM21
T1
1
TM22
TM11
T2
TM12
TM21
TM22
1.2 Scope of the Development Project

The Proposed System has to incorporate all feasible requirements of the user. It needs
powerful, user friendly and efficient application software.
Page -
The Proposed System will help the staff of GMC so that there will be minimal human interface in its
future functioning. This would be achieved with a user-friendly approach and designing on less effort
taking lines. It spells need for a high quality, secured user interface and quality MIS Reports. At each
and every step, the module has to be flexible in terms of functionality, yet it has to be rigid in terms of
achieving the overall goal by not violating any rules and regulations of the Gwalior Municipal
Corporation.
a)
b)
c)
d)
e)
f)
g)
h)
The Proposed system must completely automate the existing manual system.
The system should be error free & user friendly.
It must be easy to understand, so that a new user can also use it easily.
It must eliminate the manual record keeping practice.
Proper maintenance of all input details
MIS Report generation in a well-organized form.
It should provide facility of updating the records.
Search and display the records.
Benefits to Municipal Corporation

Builds a solid IT backbone by integrating the entire operations of the Municipal
Corporation.
Creates an intelligent Complaint-Redress System.
Provides a Controlling Tool to the Municipal Commissioner.
Better staff motivation, greater political control and better public image.
1.3 Definition, Acronyms, and Abbreviations

GMC - refers to Gwalior Municipal Corporation (M.P.)
Existing System - refers to Current Manual System
1.4 References
ZONE 1
Document\Book Name
Software Engineering
Modern Systems Analysis &
Design
SRS Templates
Author
Pressman
Jeffrey A.Hoffer, Joey
F.George
1.5 Overview of Document

This SRS presents the overall description of the proposed system for automation and
empowerment of GMC. What are the requirements of the software? What are expectations of the
Page ZONE 4
ZONE 6
ZONE 8
department from the proposed system? What functions must the software product perform? And what
not?
This SRS describes Scope and Objectives of the proposed system. It also presents the
functional requirements of the proposed system. Specific requirements are described with the following
subsections: Logical Database requirement, Design Constraints and software system attributes.
2. General Description
2.1 Product Perspective
A new system GMCs ERP will be developed to store information and support the information
related to all modules. Also, it would transfer daily money collection into accounts on regular basis.
The use of the new system shall require additional training for the staff due to the differences
between the automated system and the current manual
Existingprocedure.
Departments The current manual procedure shall
be replaced by the proposed system. The manual system shall be utilized periodically to ensure that
the backup process remains viable when called upon. The proposed system shall also have on-site and
off-site backups of the database and infrastructure.
Department
User Perspective Ideally wants quick answers or solutions. The user is only interested in the solution
of his/her grievances posted. The user would like to get answer of their queries quickly without so
Data
many of obstacles.
Migrati
on
Perspective
utility
Existing Information
on Registers
sophisticated facilities
to search/view
Role Holder
Wants
the queries/grievances posted
by the user. If an answer does not exist in the knowledge pool, the role-holder resolves the
queries/grievances and if requires escalate it to a second-tier person in the case Approval System.
Super Administrator Perspective needs
a system
that accommodates real-time access. Since the help
PROPOSED
GMC SYSTEM
desk is a business critical operation, the super administrator is responsible for the consequences of
any delays caused by the overhead of system configuration; the super administrator needs a reliable,
Users
Global Help Desk
scalable system to support a broad range of support inquiries.
Level N
Department Head Perspective needs top-quality service for users coupled with reasonable cost; a
Help Desk 1
is quickly deployed and easily used by all of the parties above, as well as the tools to
Level 3
access current and historical activities, trends and results. The DH (Department
Head) also wants
triggers, such as escalation and advanced notification, so that emergency and high-level problems
Help Desk 2
get immediate attention.
The above mentioned are some of the perceptions from diversified areas.
Level 2
GMC
Database
system
that
SOFTWARE
Need for common system - Sometimes managing separate helpdesks becomes a tedious task and
costly one. ERP will be common platform for each and every helpdesk from where query posting,
Level 1
query searching, resolving query to sort out.
Help Desk n
Other
Modules
Page -
Page -
User interfaces
This software will provide a electronic-centric approach to the user interface. Traditional manual
works forces the employee to focus his/her attention on cryptic data file formats or verbose problem
oriented languages and third party text format.
The electronic-centric approach employs principles of visualization and direct manipulation, resulting
in software that enables employees to concentrate on modeling a electronic file and studying its
behavior.
Communication interfaces
Wireless Radio Frequency Microwave Network
Central Server Architecture
Page -
10
2.2 Overview of Functional Requirements

This section provides a high level description of the major requirements of ERP. Our software will
respond to hot keys and provide input form for entry and actions. Furthermore, it will parse the
meaningful information and read back the details and allow users to take print efficiently. The
Proposed System will help the staff of the Department in the way that there will be minimal human
interface with high user friendly and less effort taking. It needs a high quality and secured of user
interfaces and a very professional quality generated MIS Reports. At each and every step the module
has to be flexible in terms of functionality, yet it has to be rigid in terms of achieving the overall goal
by not violating any rules and regulations of the Nagar Nigam, Gwalior.
2.3 Overview of Data Requirements
The data input from the user will be in the form of keystrokes. Its output to the user will be in the form
of screen and MIS report.
2.4 General Constraints, Assumptions, Dependencies, Guidelines
The product will only work with a computer that is capable of running ERP. The code must be
compliant with the computer.
Audit process requires that validation and verification occur at each processing point.
The standard requirement is as following:
Operating Systems
Windows 98
Windows 98SE
Windows ME
Windows NT 4.0
Windows 2000(Recommended)
Windows XP (Recommended)
Minimum Hardware
Pentium 233 MHz (Recommended: Pentium 500MHz or greater)
64 MB RAM (Recommended: 128 MB RAM or greater)
64 MB hard drive space
Communication Interfaces
Wireless Networking
Peripherals
The target computer for this program should be equipped with networking facility for usage and
storage of the records.
Networking Peripherals
Microwave Access Radio
High Gain Antennae
Wire rope Mast

Page -
11
RF Cables
Wireless Network Cards
End Connector
Hub
CAT 5 Cables
Switch Port
Connectors
Router
RAID Cards
Clustering Storage Box
Additional Software
Microsoft SQL Server (Desktop Edition)
Baraha SDK 5.0: The main objective of the Baraha 5.0 SDK is to help developer
community develop various types of applications in Kannada/Devanagari scripts.
Assumptions and Dependencies
Various departments of GMC have existing personnel, familiar with usage of automation
process technology and they can maintain the system once installed.
Daily money collections of Demand Bill Receiving of the up state of the system, paperwork will
replace the temporary malfunction of the system assuming orders will be entered upon system
recovery.
At least one authorized person shall be available all times to approve what employees can't
approve.
2.5 Approval Systems

Functions
Functional requirements define the fundamental actions that must take place in the software in accepting
and processing the inputs and in processing and generating the outputs.
Following are the functional requirements of the proposed systems:
a) System shall save data with no duplaicte enteries that means each and every case must have unique
ID.
b) It shall not insert a invalid entry. The user must be resticted to enter any wrong entry or data.
c) Each form operate on a singlt toolbar.
d) It shall be fully operatable through keyboard.
e) It shall have the facility of updating the records. In case user makes mistake in entering data then it
provide updating facility.
f) Data must be flow in proper way. Hot keys must be provided with proper tips for operating the
product.
g) Reports must be produced in a well format manner.
Page -
12
h) Contempt cases shall refer to existing cases that have been closed.
i) A facility of deleting records must also be provided in the proposed system.
j) A separate report shall be designed to search a particular department on which case has been filled or
by which cases has been filled on GMC.
Approval System (with diagram and cases)
Some Queries must get the approval in order to be processed any further. To deal with this, the system
first sends the query to the approval hierarchy. If the Approval is not done, the Query wont proceed
further. The following interaction diagram depicts the importance of approval in the current system.
From the above diagram it is clear that if a query needs to be approved, it must goes to the approval
p0rocess, and then only itll be submitted to the Role Holder for the Resolution. Otherwise, it wont
be allowed to proceed further and will be closed.
Page -
13
The Hierarchy of Approval system has been depicted in the following picture. There can be a no of
levels in this hierarchy.
Execution Authority
(Role Holder)
Approval Authority
(Approver)
User
(Normal User)
A n1
A 11
A 01
A 12
A 02
A 03
Approval Hierarchy
A
04
Level
s
There may be cases that if any one among the approval hierarchy approves the Query, it can be
further submitted to the role holder for Resolution. In some cases, however the Query must get
approved from a set of approvers in order to proceed further. The following diagram depicts the
Approval Process, in which a Query comes in for the approval and once it get approved from the
Immediate Boss of the User (who posted this Query). Once the Query is approved, it further
submitted to the Role Holder for Resolution. If it is getting disapproved, itll be closed.
Page -
14
Approval Flow in the Approval Hierarchy

Based on the Approval Process, the Query will be submitted to the lowest level approver, if it is being
approved, then the system will test if any further approval required, if Yes then itll be submitted to the
upper level Approver for further approval else Submitted to the Query Resolution Process. In this way
it can go up to n level for the approval.
Approved?
IfIfApproved?
Y
Further Approval
Required
?
Approved?
IfIfApproved?
Y
Further Approval
Required
?
Approved?
IfIfApproved?
Query
Closed
Approved
IfIfApproved
from
from
ImmediateBoss
Boss
Immediate
??
Query
Resolution
New Query
Levels
Page -
15
3. SPECIFIC REQUIREMENTS
3.1 Detailed Description of Functional Requirements
These requirements are listed in order of importance, with the most important first.
1. Hot keys for ERP
2. Purpose: To allow user to control hot keys
Inputs: Keystroke combination
Processing: Action happens after user inputs the command.
Command Name
Software Hot key
Save Record
Ctrl + S
Update
Ctrl + U
Delete
Ctrl + D
Cancel
Ctrl + C
Close Window
Ctrl + Q
Copy
Ctrl + C
Cut
Ctrl + X
Search
Ctrl + F
Paste
Ctrl + V
Print
Ctrl + P
The Proposed
software
checks for
duplicate
value, Check
for financial
year before
any
transactions,
Check for
numbers and
strings value
according to
the needs.
3.2 Performance Requirements

Static numerical requirements are:
The software can support more than one terminal.
The number of simultaneous users can be more than one at the same time.
Dynamic numerical requirements are:
All of these requirements should be stated in measurable terms.
Most of the transactions shall be processed within few seconds.
An operator shall not have to wait for the transaction to complete.
3.3 Quality Attributes
Security
All Hindi font data should be encrypted during transmission using a devapi.convert dll.
All users shall be authenticated and verified before any access to the system.
Page -
16
Firewalls shall be in place to protect desktop application PTMS and database server(s).
Network monitoring software shall be employed to monitor network traffic at all times.
A user shall only authenticate and validate once per session (single log-in).
By grouping the SQL statement together in a single transaction, we shall control whether and how
changes are made to the database. Since all insert statements must succeed for the transaction to be
committed, a failure of any of the statements will cause the entire transaction to be rolled back.
However, that once we will commit the transaction, we cant roll it back. Likewise, once we will roll a
transaction back, we cant commit it.
Maintainability
The Server system shall provide for incremental backups of all data.
The Server system shall systematically backup data during the workday.
The system shall comprehensively backup all data in a batch-like process once per day.
All maintenance activities shall be logged by the system and shall include the time, date, and
individual responsible.
3.4 Common Functions and procedures used in ERP

These are the following common functions and procedures which are used in the ERP module:
1. Procedure opendata() : This procedure is used to connect to the Sql Server 2000 database to a
respective database.
2. Procedure extend (frmname As Form) : To place a SDI(Single Document Interface) form
centrally over a MDI(Multiple Document Interface) form.
3. Procedure tool() : Toolbars visibility becomes true. Save, Search, Edit and Quit Mode common
for all the forms in toolbar.
4. Procedure tool1() : Save, Search, Edit and Quit Mode common for all the forms in toolbar.
5. Procedure tool2() : Edit mode of the toolbar is enabled
6. Procedure tool3() : Save mode of the toolbar is enabled.
7. Procedure tool4() : Only Quit button is enabled.
8. Procedure tool5() : All buttons enabled false of the toolbar.
9. Procedure tool6() : Undo, Update and Quit buttons of the toolbar are enabled true.
10. Procedure Makefal() : All menus enabled false.
11. Procedure MakeTrue() : All menus enabled true.
12. Procedure GoDate() : Retrieval of financial year dates from the database.
Page -
17
13. Procedure ClsRecset() : Makes all recordsets close and sets them to nothing.
14. Procedure Convertmonth(dm1 As String) : Shows a month from its first date to last date. e.g. :
if JAN then 01/01/2005 to 31/01/2005 as per financial year.
15. Function KeyUpper(KeyAscii As Integer) As Integer : Enables uppercase typing.

16. Function KeyNumber(KeyAscii As Integer) As Integer : Enables numeric typing.
17. Function KeyQuotes(KeyAscii As Integer) As Integer : Disables quotes and concat button of
the keyboard Meant for lower case typing.
18. Sub ClearallText(frm As Form) : Clears Textboxes, Combos, checkboxes and maskedit boxes of
a form.
19. Function CatchDec(KeyAscii As Integer) As Integer : Restrict decimal places after two digits.
20. Sub Main() : Shows first form of any module after executing an .EXE.
21. Sub balancing() : Used in accounting software. Calculates closing balances of all the ledgers.
22. Function ConvertLanguage(strVal As String, Optional blnDate As Boolean) As String :
Converts BRH Devanagari font to English font before inserting a field into a database.
23. Sub fontFalse() : Disables Hindi typing.
24. Sub fontTrue() : Enables Hindi typing.
25. Function ChkDate(dat As Control) As Boolean : Date check according to financial year, i.e. a
date lies between the present financial year or not.
26. Sub SetNegativeOp() : Used in accounting package. Opening balances setting if the amount is
negative.
27. Sub SetNegativeNg() : Used in accounting package. Closing balances setting if the amount is
negative.
28. Function DtFr(cntl As Variant) As String : Date setting according to system dates setting.
29. Sub CboSel(Ctl1 As Control, KeyAscii As Integer) : Enables SENDMESSAGE for a combo
box.
30. Function cboRt(Ctl1 As Control) As String : Used in accounting package. Conversion of
Hindi Font into English Font using combo boxes.
31. Function ComboORListValueCheck(cnt As Control) As Boolean 'checking value in List :
Checks whether a item is available in the list or not.
Page -
18
32. Sub Cancel() : Cancels or Undo a current operation using toolbar.

33. Sub ClearAll() : Clears a form.
34. Sub Delete() : Deletes a record using toolbar.
35. Sub Edit() : Edits a current record using toolbar.
36. Sub Update() : Updates a record after edition using toolbar.
37. Sub save() : Saves/Inserts a record into the database using toolbar.
38. Sub Exit1() : Exits current form opened above the MDI form.
39. Sub fill() : Fills a record into a form from the database after proper selection criteria.
40. Sub inc1() : Increment of a value of a particular format which may be a string or a number.
41. Function ChkDup() As Boolean : Check for a duplicate item in a flex grid which is already
selected on the above rows.
42. Sub calculate() : Summation of a particular column in a grid.
43. Sub CalRest() : Summation of a particular column in a text at the last row.
44. Function CheckForEmpty() As Boolean : Check for a particular field in a grid whether empty
or not.
45. Function CheckForNegative() As Boolean : Checks whether the summation of a column is
negative or not. If negative it restricts further functions.
46. Sub ClearGrid() : Clears a grid.
47. Sub DelAll() : Used in accounting package. Used to delete a particular record before making
updations
4. Documentation Requirements (Module Wise)

4.1 Financial Accounting
This module looks after all financial aspects of GMC including incomes, expenses, revenue
generation, cash and bank related transactions. This module is linked to all those modules, which are
related to revenue generation through which all transactions take place automatically without any
hazard after the approval of authorized officer. This software is fully privileged based and password
protected. Users are defined as per the Accounts Officer authorization.
Page -
19
It looks after all type of financial aspects through different departments periodically and reports are
generated according to the person concerned as per the requirement. As financial accounts is the
backbone of any establishment like GMC, it is developed by the highly qualified professionals with a
huge knowledge of all if and buts of Accounts.
1. Budget heads to be incorporated as per the GMC.
2. Voucher Entries as per financial accounting rules.
3. Cheque writer form.
4. Approval of cheques by an authorized officer.
Startthe verification of officer concerned.
5. Income heads get posted automatically after
6. Budgets monthly status.
7. Cash Book.
8. Bank Book.
Department And Ledger Opening
9. Bank Reconciliation
10. Periodic status of revenue generated from various departments.
11. Periodic ledger status.
Opening Balances And
Budget Entry
12. Trial balance.
13. Balance sheet.
Voucher Entry
No
Revenue Collection
(Departments)
Voucher
Verificatio
n
No
Yes
Voucher
Verificatio
n
Voucher Creation
Yes
Ledger Balance Updating
Voucher Creation
4.1.3 Flow Chart
Ledger Posting And Balancing
Accounts
Data
Store
Final Accounts
Reports &
Statements
Page End
No
20
4.1.4 Algorithm
Step 1 : Start
Step 2 : Enter department information.
Step 3 : ledger creation under departments and group.
Step 4 : Fill opening balance and budget entry.
Step 5 : enter voucher entry.
Step 6 : voucher verification process.
Step 7 : ledger balance checking.
Step 8 : if voucher verified then voucher creation else go to step 5 or step 16.
Step 9 : Ledger Posting and go to step 14.
Step 10 : revenue entry from various department.
Step 11 : ledger selection and voucher verification.
Step 12 : if voucher verified then voucher creation else go to step 10 or step 16.
Step 13 : Ledger Posting.
Step 14 : Ledger Balancing and store in database.
Step 15 : MIS Report Generation Process.
Step 16 : End.
Page -
21
Vouchers
Other Departments
MIS Reports
Administration
Cash & Cheque Deposits

Application for Budget
Cash / Cheque Deposit

Cash & Cheque Receive
0-Level
MIS Reports
Approval of Budget
Input Data (Voucher Enter)
Accounting
System
Banks
Cash / Cheque receive

Ledger Posting
Users
Reports
MIS Reports
Account Department
0-LEVEL DIAGRAM
Page -
22
1.0
Budget
Entry
Budgetary
Budgetary Master
Master
Budget Master Updation

Budget check for a
particular voucher
Voucher Detail
Voucher Entry
2.0
Departments
Cash/Cheque
Cash/Cheque
Voucher
Entry
System
Voucher Entry
Voucher Master
3.0
Update
Ledger Amt.
Ledger
Ledger Updation
System
4.0
Ledger Detail
Voucher info
Produce
MIS
Reports
MIS Reports
Voucher info
Administration of GMC
1st-LEVEL DIAGRAM
Page -
23
Departments
Cash
Received
Cash
Payment
2.1
Budget check for a

particular voucher
Cash
Voucher
Entry
Voucher Master
Cash
Voucher
Budgetary
Master
Cash Voucher
Entry
Voucher Detail
2.2
Cheque Voucher Entry
Cheque
Voucher
Cash
Payment
Cheque Voucher Entry
Cash
Received
Departments
2nd-LEVEL DIAGRAM
Page -
24
Departments
Bank
Cash
Deposit
Cash Receiving
Cash
Receiving
2.1.3
2.1.1
Cash Voucher Entry
Receipt
Voucher
Contra
Voucher Master
Voucher Detail
2.1.4
2.1.2
Journal
Entry
Payment
Voucher
Cheque Payment
Departments
Budget check for a particular voucher
Budgetary Master
3rd-LEVEL DIAGRAM
Page -
25
2.1
Opening
Balances
Budget
Entry
System
Estimated
Budget
2.0
New Ledger Entry
Update
Ledger
Amount
Amount
Amount
Ledger
2-LEVEL DIAGRAM
3.1
3.0
3.7
Produce MIS
Report
Revenue
From Depts.
report
Misc.
Report
1.6.1
Revenue
From
PHE
3.2
3.3
3.4
3.5
3.6
Cash Book
Bank Book
Trial
Balance
Balance
Sheet
1.6.2
Periodic
Revenue
Ledger
From
Property Tax
Voucher
1.6.3
Revenue
From
Fire Brigade
Voucher
Voucher
Voucher
Voucher
1.6
Voucher Info
Update
Ledger
Balances
Ledger
Accounts Department
1.6.4
Revenue
From Zoo
2-LEVEL DIAGRAM
1.6.5
Revenue
From
Rajasv
Page -
26
3-LEVEL DIAGRAM
Page -
27
Deptid
deptnam
e
remark
s
gno
nature
gname
Dept_Master
group_master
H
as
H
as
subdept_master
Subgroup_master
sdeptid
remark
s
subdep
tname
HA
S
HA
S
nature
sgnam
e
gno
sgno
accid
budget
Iname
sdeptid
Ledger
opdr
sgno
gno
opcr
cldr
clcr
HA
S
accid
HA
S
Date2
Iname
PreBudget
recordLed
Date1
deptid
opdr
sdeptid
opcr
budget
Date1
Date2
vno
accid
vdate
sgno
vno
vtype
gno
sn
crdr
vtotal
narratio
n
remark
s
Lid
1
v_master
H
as
v_details
dr_am
t
cr_amt
Page -
28
chqno
sd
rem
H
as
dno
Date
1
zno
Lid2
cdate
Ledger
H
as
cqid
tn
vdate
Chq_writer
remark
s
accid1
accid2
chqno
amount
chqdat
e
Add/Edit/Dele
te
Group
SubGroup
Voucher Detail
Departmen
ts
Page -
29
Sub
Departmen
t
Accounts Officer
Ledger
Master
Voucher
Entry
Revenue From
Department
Cheque
Writer
Reporting
Budget
Budget Monthly
Periodic Ledger Status
Cash Book
Bank Book
Debit Note Register
Journal Register
Consolidated Report
Trail Balance
Balance Sheet
Revenue Generation From

various Department
Cheque
Approval
Revenue
Voucher
Entry
4.1.8
MIS Reports
1. Department wise budget status.

2. Monthly budget status.
3. Periodic Ledger Status.
4. Cash Book.
5. Bank Book.
6. Debit Note Register.
7. Journal Register.
8. Reconciliation of bank (Pending Cheques).
9. Reconciliation of bank (Approved Cheques).
10. Consolidated Report (Ledger Wise).
11. Consolidated Report (Credit Only).
12. Consolidated Report (Debit Only).
13. Trial Balance.
14. Balance Sheet.
15. Revenue generation from various departments.
Page -
30
4.2 Payroll
This module looks after the details of salaries of GMC employees, which includes demographic details
also. It takes care of their attendance, leaves taken, insurance, LIC policies, loans & advances,
arrears, yearly salary increment.
1.
2.
3.
4.
5.
6.
Payslip generation.
Salary Register.
Salary Deduction Register.
Bank List Department wise.
Bank wise listing.
Employees Annual salary details.
Page -
31
7. Employees increment details.

8. Loans & Advances Details.
9. LIC details.
Start
Insurance
Details
Loan
details
Employee Detail
Processing
Is
Insura
nce
avail
No
Is
Loan
avail
No
Yes
Yes
Employee Insurance information is

stored and an id is generated
4.2.3 Flow Chart
Arrear
Ledger detail Processing

(Emp. Detail,Insurance,Loans)
Attendance
No
Yes
Arrear
Processing
Employee Loan information is stored

and an id is generated
Increment
No
Yes
Holiday
Working
Yes
Yes
No
No. of Absent
Increment
Detail
Special day
salary
Processing
Monthly salary ledger

Data Store
Accounts
transfer
Reports &
Salary Slip
End
Page -
32
4.2.4 Algorithms
Step1:
Start.
Step2:
Enter Employee detail.
Step3:
Enter Loan Detail of Employee.
Step4:
Enter Insurance detail of Employee.
Step5:
If Loan is avail then Loan is Processed goto step7
Step6:
If Insurance is avail then Insurance is processed goto step7.
Step7:
Salary Ledgerdetail is processed
Page -
33
Step8:
If Employee have an arrear then Arrear Processed goto step12
Step9:
If Employee have an absent then input no. of absent goto step12
Step10: If Employee have an Increment then input Increment detail goto step12
Step 11: If Employee works on holiday then special day salary Processed goto step 12
Step12: Process the salary transaction and stored into the Database.
Step13: MIS Report Generation Process.
Step14: End.
Users
Data Entry
Account Department
Consolidated
Amount
0-Level
Salary & Arrear Transfer into

employees Bank account

Bank
PayRoll
System
Payment
Payroll System
MIS Reports
Employee Detail
Salary/Loan/GPF/
Insurance/ Leave /
Increments Detail
Employee
Salary Slip
Advance Cheque
MIS Reports
Departments/ Administration
Page -
0-LEVEL DIAGRAM
34
Fetching Information
from
Employee
Master Database
Register New Employee
1.0
Employee
Master
Payroll Book
Keeping
Entered new records
or updating existing
records
Fetching Record for Correction
Register Allowance & Deductions
Zonal
Office
/Department
Receiving Allowances
(Operator)
Fetching
Records
&
Deductions
Fetching Information from

Employee Transaction
Database
Employee Transaction
from Employee Salary
Receiving Database
Salary Details
3.0
MIS Reports &
Salary Slip
Generation
Providing MIS
Reports or
Administration /
Department
Employees
Page -
35
Date Wise Collection

Transfer to Account
Department
2.0
4.0
Salary & Arrear

Generation
Payment of
Loan &
Advance
Installment
Receive
money
against
sanction
Loan
and
Advance
Employees
Payment
Detail
Allowances
Salary &
Arrear
Transfer
into
employees
Bank
account
Corporation Deduction
Other Deduction
Store in
Ledgers
Fund Transfer

Transfer to Account
Department
Accounts
Department
Bank
1-LEVEL DIAGRAM
Page -
36
Zonal Office
(Operator)
Entered new records or updating existing records
1.1
Fetching Master
Information for
Transaction
Register New Employee
Employee
Master
Payroll Book
Keeping
Employee
Transaction
Adding
Record for
Advance
Loans/Isuranc
e
Fetching
Record for
Correction
Adding New
Transaction
Advance
Loans/Insurance
Fetching Record for
Correction
Adding New
Transaction
1.2
Payroll
Transaction Book
Keeping
2-LEVEL DIAGRAM
Page -
37
Receive money against

sanction Loan and Advance
Employees
Payment of Loan
& Advance
Installment
Payment Detail
Bank
Fetching Records for

Payslip Generation
Search Record
2.1
Employee
Master
Salary & Arrear

Generation
Salary & Arrear Transfer into

employees Bank account
Search Record for

Transaction
Employee
Transaction
Fetching
Records for
Payslip
Generation
Update Salary
Receiving
Salary and Arrear

Receiving
Employees &
Department
2.2
Report
MIS/Receipt
/salary slip
Generation
2-LEVEL DIAGRAM
Page -
38
Fetching Records for MIS

Reports Generation
3.1
Employee
Master
Payroll MIS
Reports
Generation
Reports Generation
Fetching Records for Pay

Slip Generation
Employee
Transaction
Salary Details
Reports Generation
Advance
Loans/Insurance
3.2
Print or
Display
Records
Salary Slip
Generation
3.3
Display or Print
(MIS Reports)
2-LEVEL DIAGRAM
Page -
39
DP
enid
dedid
bp
EType
ETID
remarks
Desig_Master
Remarks
Remarks
Has
bp
C
F
Leave_Master
Deduction_Master
Earning_Master
ET_master
Dept_Master
Head
Heasd
Designame
desigid
Deptname
Deptid
Type
Leaveid
Remarks
alias
alias
Has
Has
Has
BName
Has
Ecode
Eid
Bank_Master
Bid
TZSet
Emp_Master
Has
Nam
e
BID
Has
Addres
s
Remarks
Fname
IDate
Doc
Desigid
Remarks
ID
Remarks
Dor
Eid
Type
ZSet
DeptID
PFNo
Basic
Has
Emp_Details
Total
Basic
Gid
doj
empid
Insid
empid
date
d
ded
Iid
aid
Att_details
Has
Has
amoun
t
Ins_master
Salid
intime
outtime
dtid
dated
Sal_M
dated
Att_master
Sal_master
Has
dt2
head
Sal_details
Has
dtid
absent
dt1
Month1
remarks
Loanid
tot
Year1
month
eid
Remarks
year
Has
Loan Master
Advance Master
aid
Remarks
Type
words
Recamt
tp
Loanid
type
twdays
Has
aid
salid
leaves
loanid
Ded
advid
dated
empid
amount
Page -
40

Add/Edit/Delete
Dept./Zone
Designation
Allowances
Deductions
Salary Details
Grade
Leave
Salary Ledger Provider
Employee
Reporting
Salary List
Deduction List
Bank List Department wise
Increment List department
Emp. Loans
wise
Insurance Detail
Emp.
Insurance
User
Insurance Ledger Provider
Loans Detail
Department wise
Emp.
Increment
User
Auto.Salary
Manual
Salary
Loans Ledger Provider
Attendance List
Employees detail List
Employees loans status

List
Annual salary List
Bank wise Bank salary List
Pay slip
Salary Check
MIC
Members
Salary Cheque
MIC Salary
Salary Details
Salary Check
Salary Cheque
Salary Cheque
Salary Ledger Provider
Salary Generated
Account
Accounts
4.4.8 MIS Reports

Reports for any application play an important role. This application will support reporting to help the
management in knowing the status and to view graphs based on the figures. This application will support
generation of report within a specified period and also for a particular Department. The different reports
that would be there in the application are as follows:
1. Monthly salary List
This report gives a list of Employee monthly salary department wise with all allowances, deductions and
their Leave of Employee. This report also shows Head wise amount. It helps in clarity of amount.
2. Monthly salary deduction List
This report gives a list of Employee monthly salary deduction amount department wise with all deduction
heads.
3. Pay slip
This report shows the monthly pay slip of Employee with their salary details for that month.
4. Monthly Bank list Department wise
This report shows the list of Employee with their bank name, account no. And amount for particular
month of salary. The purpose of this list is to shown total amount of particular bank department wise with
employees detail.
5. Monthly Bank List Bank wise
This report generates the bank list that is send to bank by GMC.
6. Employee detail List
This report generates the list of Employee with their details like Name, Father Name, Department name,
designation, Address, Joining date, Retirement date, Current Basic.
7. Attendance List
This report shows the monthly attendance of Employees department wise Even an Employee is working in
other department but attendance shows in their department. For generating this report the Bank name,
month, year has to be entered.
8. Salary increment list
This report shows the Employees name their current basic, increment amount and basic after increment
for an increment date of Employee comes on that month .It helps to check Employees name, Increment
amount before making salary of month
Page -
42
9. Loans detail of Employee

This report shows the loans detail of Employee like Loan amount, deposit amount, remaining amount, and
monthly deduction amount. For generating this report the Time period has to be entered.
10. Annual Salary List
Using this report the user will be able to generate the listing of Annual salary getting by Employee with
monthly payment details Department wise. For generating this report Transactions Year and department
name has to be entered.
Page -
43
4.3 Pension
Pension is a part of accounts module, which takes care after the retirement or Death of GMC Employee.
In Existing system Pension Record maintained manually. Pension Ledger is prepared with all details of
Pensioner Like Pensioner Name, their Last Basic, Last DA and Job Duration, which is helpful in
calculation of Gratuity and Pension Calculation. In Existing system Gratuity and Pension is calculated
manually. There are three types of Pension Final Pension, Provisional Pension, and Family Pension.
Monthly Ledger is prepared for Pensioner and Bank list is prepared monthly.
4.3.2 User Requirement

1.
2.
3.
4.
5.
6.
Gratuity Calculation
Pension Calculation
Bank List
Pension Register
Pensioner detail
Consolidated Report.
4.3.3 Flow Chart

Start
Pension Detail
Is
Job duration>Min.
Years for Gratuity
No
Is
Death
Yes
Yes
Gratuity Processed
No
Is Job duration>Min.
Years for Pension
Yes
Is
Retired
No
No
Is
Pension Finalized
Family
Pension
processin
g
No
Provisional Processing
Yes
Final Pension Processing
DatatStore
Pension Ledger Processed
Reports
End
Page -
46
4.3.4 Algorithms
Step1: Start.
Step2: Enter Pensioner detail .
Step3: If Job duration >Min. years for Gratuity then Gratuity Processed goto step 5.
Step4: If Death then goto step 9.
Step5: If not Job duration>Min. years for Pension goto step11.
Step6: If not Retired then goto step10.
Step7: If Pension is not Finalized then goto step 9.
Step8: Final Pension is Processed goto step 11.
Step9: Provisional Pension is Processed goto step 11.
Step10: Family Pension is Processed goto step 11.
Step11: Process the transaction and stored into the Database.
Step12: Issue the Receipt and print the Receipt against Pension.
Step13: End
Page -
47
Data Entry
Consolidated
Amount
Users
Fund Transfer
Payment
Bank
Pension Cheque
Pension System
MIS Report
Pensioner
Account Department
Zonal Office
(Operator)
Gratuity/Pension/
Allowance/Deduction
Payment
Advance Cheque
MIS Reports
Departments/ Administration
0-LEVEL DIAGRAM
Page -
48
from Employee Master
Database
Register New Pensioner
1.0
Pensioner
Master
Pension Book
Keeping
Entered new records

or updating existing
records
2.0
MIS Reports

Pension Transaction Database
Pension Transaction
Providing MIS
Reports
Register Allowance & Deductions
Department
(Operator)
Administration /
Department
Fetching
Records
Transfer to Account
Department
3.0
4.0
Pension & Arrear

Generation
Pension
Store in
Ledgers
Fund Transfer

Transfer to Account
Department
Bank
1-LEVEL DIAGRAM
Accounts
Department
Page -
49
Zonal Office
(Operator)
1.1
Fetching Master
Information for
Transaction
Pension Master
Pension Master
Book Keeping
Pension Transaction
Adding New
Transaction
Fetching Record
for Correction
1.2
Pension
Transaction Book
Keeping
2-LEVEL DIAGRAM
Page -
50

Reports Generation
2.1
Pension Master
Pension MIS
Reports
Generation
Pension Transaction
Reports Generation
2.2
Print or Display Records
Display or Print
(MIS Reports or
Bank List)
2-LEVEL DIAGRAM
Page -
51
address
Nam
e
FName
Pn
o
PPDate
Bi
d
Remarks
Bank_Master
dob
PPNo
BName
JDate
Pi
d
H
as
Pen_Master
RDate
Bi
d
ddar
Pstatus
Ptyp
e
hrent
Bname
medical
gamt
Basic
DA
accno
LDa
Pid
Has
monpid
Pension
MonD
A
Parrear
Year1
Basic
DA
HRA
Ptyp
e
ma
Page -
52
4.3.7Activity Diagram
Add/Edit/Delete
Bank
Pension
Detail
Gratuity
Calculation
Pension Details
User
AutoCalculat
e Pension
Reporting
Pensioner Detail Report
Monthly Pension Report
Schedule Report
User
Pension Check
Auto.Pensio
n
Pension Cheque
Manual
Pension
Pension Details
Accounts
Pension Check
Pension Cheque
Account
Pension Ledger Provider
Pension Generated
Page -
53
4.3.8 MIS Reports

Reports for any application play an important role. This application will support reporting to help the
management in knowing the status and to view data. This application will support generation of report
within a specified period. The different reports that would be there in the application are as follows:
1. Monthly Pension List
This report gives a list of monthly Pension Bankwise with all allowances, deductions. This report also
shows Head wise amount. It helps in clarity of amount.
2. Monthly Bank List
This report generates the bank list that is send to bank by GMC.
3. Pensioner detail List
This report generates the list of Pensioner with their details like Name, Father Name, Address, Joining
date, Retirement date, Last Basic, Last DA, Gratuity, Pension Type etc.
4. Schedule report
This report generates the list of Bank Name and their corresponding Total amount monthly based.
Page -
54
4.4 Property Tax Management System

The Property Tax is one of the department of Gwalior Municipal Corporations (G.M.C.). The
functionality of the department incorporates to taxation of all properties, which comes in GMC domain.
The procedure of Property Tax to collect the taxes on the basis of Self-assessment form in which all
kind of properties that includes kind of Construction (RCC, RBS etc.), Type of usage (Self use or rented)
and residential or non-residential. The property holders fill the self-assessment form of their property and
pay the tax. If a property holder doesnt pay the tax within a financial year then Property Tax Department
raises the Demand Bill and sends the same to the property holder.
The Property Tax Management System is based on the concept of Taxation of Property. The
module has to incorporate all feasible requirements of the user. It needs powerful, user friendly
and efficient application software.
The module will help the staff of Property Tax Department in the way that there will be minimal human
interference with high user friendly and less effort taking. It needs a high quality and secured of user
interfaces and a very professional quality generated Demand Bill and MIS Reports. At each and every
step the module has to be flexible in terms of functionality, yet it has to be rigid in terms of achieving the
overall goal by not violating any rules and regulations of the Nagar Palik Nigam, Gwalior. The interface
provides the ability to:
1. Input information in details.
2. Generate Demand Bill with previous dues.
3. Search and display the records.
4. Print MIS reports.
These functions include saying the command of the hot key as it is invoked, providing shortcuts for
operations.
Benefits to Municipal Corporations
1. Builds a solid IT backbone by integrating the entire operations of the Municipal Corporation.
2. Creates an intelligent Complaint-Redress System.
Page -
55

As per the user a requirement that states to fulfill the requirements of department, which handles all the
transactions through computer system, and generate the MIS reports. The all requirements are given
below:
1. To maintain the master data separate from the daily transactions.
2. Register the new properties.
3. Required auto Tax Calculation (without/ with minimal human interferences).
4. To save the time for transactions processing.
5. To provide the transparent and accurate data to the department.
6. To provide the accurate Tax Calculation as per norms.
7. To issue the Property Bill/ Demand Bill.
8. To issue the Property Bill/ Demand Bill Receipts.
9. To keep the data and details in proper format.
10. Maintain the different heads of the property Tax (Property Tax, Samekit Tax, Citizen Development Tax
and Education Tax) .
11. Required to have computerized search to find quick details as per different parameters.
12. To Provide help to the Management/ Administration to take their Decisions based on the following
MIS reports:
Property Tax Bill

Property Tax Demand Bill
Defaulters List
Paid Tax List
Top Defaulters List
Periodic Collection Report
Property Description Report
Over all Billing Detail
Tax Collection Report Zone Wise
Tax Collection Report Ward Wise
Page -
56
Start
4.4.3 Flow Chart
Enter Ward Number
Verified
Ward
Number
No
Reject Ward
Number
Yes
Picked the first Property
ID for Calculation within
ward Number
Get the Annual Rate from

the Database for current
financial year
Bill
Generate
Transaction
Data
Store
ERROR
Demand Bill Issue Press
Demand Bill &

MIS Reports
Stop
Page -
57
Bill Generation Process Flowchart 1.1
Page -
58
Start
Enter Property ID
Verified
Property ID
No
Reject Property
ID
Yes
Display Bill Detail for
receiving
Enter the amount paid by

Property Holder
Bill
Generate
Transaction
Data
Store
ERROR
Receipt Issue Press
Receipt against
Demand Bill
Stop
Bill Receiving Process Flowchart 1.2
Page -
59
4.4.4 Algorithms
Algorithms of Flowchart 1.1 (Bill Generation Process):
Step1: Start.
Step2: Input Ward Number.
Step3: If Ward Number does not exist then goto Step8.
Step4: Pick the First Property ID for Calculation within a Ward Number.
Step5: Get the annual rates from the Database for current financial year.
Step6: Generate the bill for a particular financial year and stored in the database.
Step7: Issue the Demand Bill and print the Demand Bill.
Step8: Stop
Algorithms of Flowchart 1.2 (Bill Receiving Process):

Step1: Start.
Step2: Input Property ID.
Step3: If Property ID does not exist then goto Step8.
Step4: Display the Bill Detail for receiving.
Step5: Input the amount paid by Property Holder.
Step7: Issue the Receipt and print the Receipt against Demand Bill.
Step8: Stop
Page -
60
Self-Assessment Form
Property Holders
MIS Reports
Bill Payment
Register New Property
Demand Bill
Property Tax
Department (Admin)
0-Level
Bill Receipt
Property Tax
Management
System
Input Data
Zonal Office
MIS Reports
Date Wise Collection Transfer to

Account Department
Account Department
0 LEVEL DIAGRAM
Page -
61
from Property Tax
Master Database
1.0
Property Tax
Master
Property Tax Book
Keeping

Property Tax Transaction
Database
MIS Reports &

Demand Bill
Generation
Property Tax
Transaction
Providing MIS
Reports
or
Demand Bill
from Property Tax
Receiving Database
Zonal Office
(Operator)
Receiving Property Tax
2.0
Property Tax
Receiving
Property Tax
Department
Property
Holders
Fetching
Records
Transfer to Account
Department
3.0
4.0
Demand
Bill Receiving or SelfAssessment form
receiving
Store in Ledgers
Fund Transfer
Property Tax
Ledger
Providing
Receipt against
Property Tax
Demand Bill
Receive money
against Property
Tax Demand Bill
Property
Holders

Transfer to Account
Department
Accounts
Department
Page -
62
1-LEVEL DIAGRAM
Zonal Office
(Operator)
Fetching Master
Information for
Transaction
1.1
Property Tax Master
Book Keeping
Property Tax
Master
Property Tax
Transaction
Fetching
Record for
Correction
1.2
Adding New
Transaction
Property Tax
Receiving
Fetching Record for
Correction
Adding New
Transaction
Property Tax
Transaction Book
Keeping
2-LEVEL DIAGRAM
Page -
63
2.1
Property Tax MIS
Reports Generation

Reports Generation
Fetching
Records for
Demand Bill
Generation

Demand Bill Generation

Reports Generation
Property Tax
Master
Property Tax
Transaction
Fetching
Records for
Demand Bill
Generation
Property Tax
Receiving
2.2
Property Tax Demand
Bill Generation
Print or
Display
Records
Print or
Display
Records
2.3
Display or Print (MIS
Reports or Demand
Bill)
Page -
64
2-LEVEL DIAGRAM
Page -
65
3.1

Receipts Generation
Search Record for

Bill Receiving
Property Tax
Master
Bill Receiving
Search Record for

Bill Receiving
Property Tax
Transaction
Fetching
Records for
Receipts
Generation
Update Bill
Receiving
Property Tax
Receiving
3.3
3.2
Receipt Generation
Print Receipt
Print Receipt
2-LEVEL DIAGRAM
Page -
66
4.1
Search
Records
Transfer to Account
Search Records for Transfer

to Account
for
Current/Previous Bill
Receiving by Cash
Property Tax
Receiving
Update Property
Tax Ledger
Property Tax
Ledger
4.2
Update Property
Tax Ledger
Current/Previous Bill
Receiving by Cheque
2-LEVEL DIAGRAM
Page -
67
LocalityID
DivisionName
Remarks
ZoneNo
FinYear
PropRDMkt
CLID
Remarks
s
Description
WardNo
ClDetail
Locality
WardName
Description
ZoneName
ASID
Rate
DivisionID
DivisionMaster
Has
ZoneMaster
WardMaster
Has
Locality
Has
ClassLocality
Kind
s
Used In
AnnualSlabRate
LDetail
CTID
LName
FHName
Has
Kabiz
Date1
DtID
FName
CDetail
BuildingNo
TypeOfLiving
uction
Used In
RationCard
LTID
Has
PropertyMaster
Kind
s
PropertyHolder
Date_Master
TypeOfConstructio
n
PropID
Used In
PropDetID
Address
PropRDMkt
PropUse
Used In
PropertyDetail
NoOfFamilies
TotConsArea
TotalArea
Used In
WaterConn
PlotSize
OpenLand
EduTax
Date1
BalEduTax
SamekitTax
Has
Surcharge
PropTax
Dated
CitizenDevTax
Amount
mRec
FinYear
RecNo
BalPropTax
TrMasID
RecID
SewaSulk
TotalARV
PropTrMas
ETax
BalSewaSul
k
BalCitizenDevTax
BalSamekitTax
R1
Advance
PaymentMode
BalSurcharge
BalTotalTax
TotalTax
BalTotalPayble
Rebate
BalRebat
e
Dated
FinYear
S2
Remarks
NetTaxableARV
Receipt_Details
Has
TotalPayble
STax
PTax
PTax
S1
Receiving_Master
Has
TotalMaintenance
Date1
R2
CTax
Software Requirements Specification for GMC
Add/Edit/Delete
Zone
Ward
Locality
Property Tax Department
Annual Rate
Slab
Slabs
Type of Living
Operator
Type of
Construction
Other Rates
Property Holders
Property Master
Reporting
Property Description
Over All Bill Status
Unpaid Bill
Paid Bill
Top Defaulters List
Tax Collection Reports Zone
Wise
Tax Collection Reports Ward
Wise
Locality List
Number of Records Date Wise
Number of Records Ward Wise
Water Connection Reports
Ration Card Reports
Calculated Tax
Bill Generation
Bill Receipt
Bill
Adjustment
Account
Transfer
Copyright GMC
Page -
70
4.4.8 MIS Reports
Bills
1. Property Tax Bill
Contains Name, Father Name, Address, Locality, Ward and Zone
Provides the information of previous and current year dues.
Terms and conditions.
2. Property Tax Demand Bill
Contains Name, Father Name, Address, Locality, Ward and Zone
Provides the information of previous and current year dues.
Terms and conditions.
MIS Reports
1. Defaulters List
Users have different-2 criterion for the searching (First Name, Last Name, Father/Husband Name,
Building No., Address, Ward No. and Locality is mandatory).
Contains Name, Father Name, Address, Locality, Ward and Zone.
Provides the information of itemized dues financial year wise.
2. Paid Tax List
Users have different-2 criterion for the searching (Date range, First Name, Last Name,
Father/Husband Name, Building No., Address, Ward No. and Locality is mandatory).
3. Top Defaulters List
Users enter the Numbers of top defaulter and Zone or Ward or All.
4. Periodic Collection Report
Provides the information of receiving between a date ranges.
Copyright GMC
Page -
71
5. Property Description Report

Users have the searching Ward No. and Match or Unmatched property .
6. Over all Billing Detail
Provides the information of itemized dues and receive tax financial year wise.
7. Tax Collection Report Zone Wise
Users have option for selection of all zones and any one zone.
Estimated Tax, Tax Received and percentage of Estimated Tax.
8.
Tax Collection Report Ward Wise

Users have option for selection of all zones and any one zone.
Estimated Tax, Tax Received and percentage of Estimated Tax.
9. Locality List
Users have option for selection of Zone and Ward.
Locality, Ward, New Class of Location and Old Class of Location.
10. Number of property record prepared on the basis of Comprehensive ERP Survey Date Wise
Users have option for Date range.
Provides the information of Date and number of records entered on the same date.
11. Number of property record prepared on the basis of Comprehensive ERP Survey Ward Wise
Users have option for Date range.
Provides the information of Ward and number of records entered on the date range in a particular
Ward.
Copyright GMC
Page -
72
4.5 PHE
This module looks after all aspects of PHE which includes Water supply, Bill generation, Revenue
Collection, Issue new connection and Disconnection of existing connection. This software is fully
privileged based and password protected. Users are defined as per the PHE Officer authorization.
It looks after all type of financial aspects of PHE and reports are generated according to the person
concerned as per the requirement. As PHE is one of the main department of any establishment like GMC,
it is developed by the highly qualified professionals with a huge knowledge of all if and buts of PHE.
The PHE module is based on the concept of Water Billing. The module has to incorporate all feasible
requirements of the user. It needs powerful, user friendly and efficient application software.
The module will help the staff of PHE Department in the way that there will be minimal human
interference with high user friendly and less effort taking. It needs a high quality and secured of user
interfaces and a very professional quality generated Bill and MIS Reports. At each and every step the
module has to be flexible in terms of functionality, yet it has to be rigid in terms of achieving the overall
goal by not violating any rules and regulations of the Nagar Palik Nigam, Gwalior. The interface provides
the ability to:
2. Generate Bill with previous dues.
operations.
3.
Copyright GMC
Page -
73
below:
2. Register the new connections.
3. Required auto bill generation (without/ with minimal human interferences).
6. To issue the Bill.
9. To Provide help to the Management/ Administration to take their Decisions based on the following MIS
reports:
Dues List.
Advance List.
Over all Billing Detail
Collection Report Zone Wise.
Collection Report Ward Wise
Copyright GMC
Page -
74
Start
4.5.3 Flow Chart
Enter Ward Number
Verified
Ward
Number
No
Reject Ward
Number
Yes
Picked the first
Connection ID for
Calculation within ward
Number
Get the Bill Amount from
the Database
Bill
Generate
Transaction
Data
Store
ERROR
Bill Issue Press
Bill & MIS

Reports
Stop
Copyright GMC
Page -
75
Bill Generation Process Flowchart 1.1
Copyright GMC
Page -
76
Start
Enter BillNo.
/Connection No.
Verified
Reject
No
Yes
Display Bill Detail for
receiving
Enter the amount paid by

Connection Holder
Bill
Generate
Transaction
Data
Store
ERROR
Receipt Issue Press
Receipt against
Bill
Stop
Bill Receiving Process Flowchart 1.2
Copyright GMC
Page -
77
4.5.4 Algorithms
Algorithms of Flowchart 1.1 (Bill Generation Process):

Step1: Start.
Step2: Input Ward Number.
Step3: If Ward Number does not exist then goto Step8.
Step4: Pick the First Connection Number for Calculation within a Ward Number.
Step5: Get the Bill amount from the Database.
Step6: Generate the bill for a particular month and stored in the database.
Step7: Issue the Bill and print the Bill.
Step8: Stop
Algorithms of Flowchart 1.2 (Bill Receiving Process):

Step1: Start.
Step2: Input Connection Number.
Step3: If Connection No. does not exist then goto Step8.
Step4: Display the Bill Detail for receiving.
Step5: Input the amount paid by Connection Holder.
Step7: Issue the Receipt and print the Receipt against Bill.
Step8: Stop
Copyright GMC
Page -
78
Application for Connection
Water Connection
Holders
MIS Reports
PHE Department
Bill Payment
Water Bill
Bill Receipt
PHE
Input Data
Division
MIS Reports

Account Department
Account Department
0-LEVEL DIAGRAM
Copyright GMC
Page -
79
Fetching
Information from
PHE
Master
Database
Register New
Connection
1.0
2.0
PHE
Master
PHE Book
Keeping
from PHE Transaction
Database
Fetching Record for

Correction
Register New
Connection
Entered new records or updating existing
records
PHE
Transaction
Fetching
Records
Providing
MIS Reports
or Water Bill
Fetching
Information from
PHE
Receiving
Database
Division
(Operator)
Receiving Property Tax
MIS Reports &

Generation
Bill &
Advance
Receiving
PHE
Department
Water Connection
Holders

Transfer to Account
Department
3.0
4.0
Bill Receiving
And
Advance
Receiving
Providing
Receipt against
Water Bill
Store in Ledgers
Fund Transfer
PHE Ledger
Transfer to Account
Department
Receive money
against Water Bill
Accounts
Department
Water Connection
Holders
1- LEVEL DIAGRAM
Copyright GMC
Page -
80
Division Office
(Operator)
records
1.1
PHE Master Book
Keeping
Fetching
Master
Information
Register New
PHE Master
Fetching Record for
Correction
PHE Transaction
Register New
Connection
Fetching
Record
for
Adding New
Transaction
1.2
Adding New
Transaction
Connection Book
Keeping
Bill Receiving
Fetching Record
for Correction
2- LEVEL DIAGRAM
Copyright GMC
Page -
81

Bill Generation

MIS Reports
Generation
2.1
PHE Master
PHE MIS Reports
Generation
PHE Transaction
MIS Reports
Generation
Fetching
Records for
Bill
Generation
Fetching
Records for
Demand
Bill
Generation
Bill Receiving
2.2
Bill Generation
Print or
Display
Record
s
Print or
Display
Record
s
2.3
Display or Print
(MIS Reports or
Bill)
2- LEVEL DIAGRAM
Copyright GMC
Page -
82
3.1

Receipts Generation
Search Record
for
Bill
Receiving
PHE Master
Bill Receiving
Search Record
for
Bill
Receiving
PHE
Transaction
Fetching
Records for
Receipts
Generation
Update Bill
Receiving
PHE
Receiving
3.3
3.2
Print
Receipt
Receipt
Generation
Print Receipt
2- LEVEL DIAGRAM
Copyright GMC
Page -
83
4.1
Search Records for
Transfer to Account
Search Records for

Transfer to Account
Bill Receiving by
Cash
Bill Receiving
Update PHE
Ledger
PHE Ledger
4.2
Update PHE
Ledger
Bill Receiving by
Cheque
2- LEVEL DIAGRAM
Copyright GMC
Page -
84

LocalityID
Remarks
DivisionName
Locality
WardName
Description
ZoneName
ZoneNo
WardNo
Remarks
s
Description
DisAmt
Desc
CTypeId
DivisionID
DisDate
DisConId
Remarks
s
Amount
Has
DivisionMaster
Has
ZoneMaster
WardMaster
Has
Locality
Disconnection
ConnStatus
ConnStatus
Date1
DtID
ConnMode
Amount
CxnMode
CxnNo
Used In
Date_Master
BCID
BcCode
ConnType
Has
CxnModeId
Connection
Master
Old_Cxnno
BCName
BC_Master
Used In
Anyamtdue
Used In
FtName
Cxn_active
Address
ConnDate
Used In
Dated
Lname
Connection Trans
Dated
FName
OldFtName
Advance Receiving
Dated
Has
NewFtName
CTID
AdvRecNo
Amount
CTDate
Amount
ChqDate
Remarks
ChqNo.
Bank
Name
Bill_Master
Rebate
Dated
Payment Mode
Dated
Remarks
RecDate
Bill Receiving
Used In
Has
Last Bill Date
Bill From
Bill To
RecNo
Amount
Remarks
ChqDate
ChqNo.
Status
BillDate
1
Amount
Bill Due
Date
BillNo
Bank
Name
Rebate
Payment Mode
Dated
RecDate
Copyright GMC
85 Page -
Old Name
New Name
Remarks

Add/Edit/Delete
PHE Department
Zone
Ward
Locality
Operator
Connection
Type
Connection
Mode
Consumer
BC Master
Reporting
General Search.
Bill Receiving.
Other Receiving.
Disconnection Report.
New Connection Report.
Consolidate Connection Report.
Name Transfer Report.
Advance Report.
Due List.
Connection
Detail
Bill Generation
Bill Printing
Bill Receipt
Disconnection
Name Transfer
Account Transfer
Copyright GMC
Page -
86
4.5.8 MIS Reports
1. Water Bill
2. Advance List.
3. Due List
4. General Search.
5. Periodic Collection Report.
6. New Connection Report.
7. Periodic Disconnection Report.
8. Periodic Name transfer Report.
Copyright GMC
Page -
87
4.6 Birth & Death

4.6.1. Brief Description
This document is intended for Birth and Death software specification, which is the module of Project
ERP. GMCs ERP is a true enterprise solution that integrates function across an organization and
enables E-Governance in future. It integrates with existing systems, financials, documenting, cashiering,
fields data collection etc. to make the organization a seamless functioning entity. The software has got an
exhaustive number of modules, which take care of each and every operation of Gwalior Municipal
Corporation. The main aim of computerization is to automate and standardize the operations of the
office of the commissioner, office of all the heads of departments, Zonal offices and other related entities
working under GMC. Further, we have established their connectivity with the head office and with other
with hi-tech Microwave Wireless Radio Networking system
According to the existing system Birth and Death module is totally manually. All work related to that
is depend on the manual file handling. Certificates also generated manually. Due to manual work we
are not able to search the records quickly. Ledgers are also available in bad conditions. Not such
records are maintained due to which we able to know how many certificates generated daily. We all
know that manual work is not so much reliable and fast thats why the whole procedure of generating
a certificate becomes a very tedious job.
The use of new system shall require additional training for staff due to the differences between the
automated system and the current manual procedure. The current manual procedure shall remain in
place in case of critical failure of the proposed system. The manual system shall be utilized
periodically to ensure the backup process remain viable when called upon. The proposed system shall
also have on-site and off-site backups of the database and infrastructure. Daily backup of Database is
maintained in case of any Disaster. According to the current computerized system we are able to
complete the process in few minutes i.e. the reduction of time in cost of increment of work. The
purpose of Birth and Death software is to reduce the number of point of failure and inaccuracies
associated with the existing manual procedure, and reduces the turnaround time for processing i.e.
Reduction of Manpower.
4.6.2. User Requirements
1. Birth Records
2. Death Records
3. Generated Birth Certificate
4. Generated Death Certificate
5. MIS Reports
a) Periodic Reports for Birth and Death
b) Number of printed certificate reports
Copyright GMC
Page -
88
4.6.3 Flow Charts

Fig 4.6.3.1
Start
New Birth Information
Registratio
n exist
Information Verification Process
Datastore
Registration No. Issued
Birth
Certificate
& Reports
Stop
Copyright GMC
Page -
89
Fig 4.6.3.2
Start
New Death Information
Registratio
n exist
Information Verification Process
Datastore
Registration No. Issued
Death
Certificate
& Reports
Stop
Copyright GMC
Page -
90
4.6.4 Algorithm
Algorithm of Fig 4.6.3.1
Step 1: Start
Step 2: Input the Information of Birth i.e. the Registration Process
Step 3: If Registration Info. Not exists then go to Step 2 Else Continue
Step 4: Information Verification Process
Step 5: Issued of Registration Number
Step 6: Generate MIS Reports and Birth certificate
Step 7: Storage of data in Database
Step 8: Stop
Algorithm of Fig 4.6.3.2
Step 1: Start
Step 2: Input the Information of Death i.e. the Registration Process
Step 3: If Registration Info. Not exists then go to Step 2 Else Continue
Step 4: Information Verification Process
Step 5: Issued of Registration Number
Step 6: Generate MIS Reports and Death certificate
Step 7: Storage of data in Database
Step 8: Stop
Copyright GMC
Page -
91
Citizens
Provide Information of Citizens
Input Data
Users
Payment against Death/Birth

Certificates
0
Birth or Death Certificate
Birth &
Death
Input Data
Health Office
MIS Reports
0 LEVEL DIAGRAM
Copyright GMC
Page -
92
Fetching
Information from
Birth/Death
Master Database
Register New Entry
1.0
2.0
Birth/Deat
h Master
Birth/Death Book
Keeping
from
Birth/Death
Transaction Database
Fetching Record for

Correction
MIS Reports &

Certificate
Generation
Birth/Death
Transaction
Register New Entry
Providing
MIS Reports

records
Health Office
(Operator)
Health
Department
Citizens
1 LEVEL DIAGRAM
Health Office
(Operator)
Fetching
Master
Information
for
Transaction

records
Register New Entry
1.1
Birth/Death
Master Book
Keeping
Birth/Death
Master
Fetching Record for
Correction
Register New Entry
Birth/Death
Transaction
Fetching
Record
for
Correctio
n
Adding New
Transaction
1.2
Registered Book
Keeping
2 LEVEL DIAGRAM
Copyright GMC
Page -
93

Certificate Generation

MIS Reports
Generation
2.1
Birth Master
Birth/Death MIS
Reports
Generation
MIS Reports
Generation
Fetching
Records for
Demand
Bill
Generation
2.2
Certificate
Generation
Print or
Display
Record
s
Print or
Display
Record
s
2.3
Display or Print
(MIS Reports or
Certificate)
2 LEVEL DIAGRAM
Copyright GMC
Page -
94
4.6.6 Entity Relation Diagram

Penalt
y
Remar
k
Mother State
DtI
D
Bth_
id
Reg_d
te
Name of Child
dob
Sex
Addre
ss
Mother
Place
Info.
Add
Mother loc.
Diff
Birth Master
No of Child
Child
Wt
Mother
Ntn.
Mother
ocp.
Mother
Age
Father
Occ
Used
In
Father
National
Father
Educatio
n
Father
Religio
n
Nurse
Father
Name
Del.
Time
Has
NoofCopies
DTI
D
Date_Master
Date
1
PrintDat
e
Flag
PrintedCertificate_B
Fees
Dth_reg
Dth_id
DtID
Dth_d
te
Sex
Name of
dead
Age
Father
Address
Remark
s
Plac
e
Pen1alt
y
Place
Name
Death Master
Drink
Info. Add.
Tobacc
o
Info. Date
Sthan
Smoking
Period
Lady
Treatmen
t
Religio
n
Occupati
on
State
District
Type
Place
Dis.
Has
Used In
NoofCopie
s
DTID
PrintDa
te
Date
1
Date_Master
Flag
Fees
PrintedCertificate_D
Copyright GMC
91 Page -

Admin
Birth
Entry
Death
Entry
Operator
Birth
Certificat
e
Death
Certificat
e
User
Reporting
Only Gwalior Nagar Nigam Cases detail.

Periodical Cases detail.
Date wise Case Detail.
Name wise Cases detail.
Sex wise Cases detail.
Final Cases detail.
Consolidated details
B/D
Records
Daily
Case
Updation
Daily
Report
Copyright Amity IT Solutions Pvt. Ltd.
Page -
92

4.6.8. MIS Reports
1. Yearly Registration Details
Yearly Registration details give the total number of birth and death in a particular year.
2. Monthly Registration Details
Monthly Registration details give the total number of birth and death in a particular month.
3. Consolidated Reports
Consolidated Reports gives the description of the particular citizen.
4. General Reports
General Report gives total number of birth and death in current year, previous year and current month.
5. Printed Certificates
It gives total number of printed birth and death certificates in particular period.
Page -
93

4.7 Revenue
The Revenue Collection System that provide us the ability to handle all the department transactions
(which are operating manually so far) through system by which it is easy to maintain and store the data
centrally.
The Revenue Collection System software is the only software through which the Gwalior Municipal
Corporation collects their revenue under the different heads like shop and establishment registration,
entertainment tax, registration charges on sale of animals etc.
In the software description of Revenue Collection System the system itself means that it accept the revenue
entries under the different heads and issue the different types of receipts against the payment received by
the department as per the specific head. It also issues the certificates as per requirement like certification
of registration for shop and establishment registration department. Once the revenue is collected can be
transfer to the accounts department.
The different revenue collection heads are given below:
1. Income from Abkari (Beer Bar) as tax
2. Income from Entrainment as tax
3. Income from Advertisement
4. Income from Awara pashu
5. Income from Tanga Fee Registration
6. Income from Building Permission
7. Income from Prati-Lipi
8. Income from Vividh
9. Income from Asthai Madakhalat and Fine
10. Income from Pashu-vadha Home
11. Income from GMC Market Shops, Buildings etc.
12. Income from GMC Shopping Complexes.
13. Income from Shop Name Transfer.
14. Income from New Permission of Pidio.
15. Income from GMC Land Lease Premium.
16. Income from Nazul Department.
17. Income from Galaw Vishrantigrah.
18. Income from Lease Rent Land and Bhatak Patte.
19. Income from Lease for Khuli Bhumi Awas and Vavsaye.
20. Income from Shop and Establishment Registration.
21. Income from Bhumi Muawza Fee.
22. Income from Community Halls.
23. Income from Bazar Haat, Parking Stand Contract.
24. Income from Registration Fee on sale of Achal Pari-sampatti.
Page -
94

The module will help the staff of Revenue Collection Department in the way that there will be minimal
human interface with high user friendly and less effort taking. It needs a high quality and secured of user
interfaces and a very professional quality generated Different Registration Certificate, Receipts and MIS
Reports. At each and every step the module has to be flexible in terms of functionality, yet it has to be rigid
in terms of achieving the overall goal by not violating any rules and regulations of the Nagar Palik Nigam,
Gwalior. The interface provides the ability to:
1. Input detail information to maintain the centralized data.
2. Generate Receipts and certificate as per requirements
3. Search and display the details.
4. Print MIS reports as per requirements
1.Builds a solid IT backbone by integrating the entire operations of the Municipal Corporation.
2.A Transparent System for the department and the public.
3.Creates an intelligent Complaint-Redress System.
4.A accurate details in form of reporting.
5.The Centralized data with security.
Page -
95

below:
2. System must save the time for transactions processing.
3. System must provide the transparent and accurate data to the department.
4. Keep the data and details in proper format.
5. Issue the computerized Fee /Registration Receipts.
6. Certify by issuing certification as per requirements.
7. To renew the transactions on due date as if required.
8. Required different MIS reports as par department requirements.
9. Required auto transfer of revenue to the accounts department.
10. Required to print different ledgers as per under the different heads.
11. Required to have computerized search to find quick details as per different heads.
Page -
96
4.7.3 Flow Chart

Start
Revenue Forms
Details
Data Verification
Document
Collection
Revenue Collection Details

Process
Verified
Document
Status
Data
Store
Cancellation
Process
No
Receipt
Yes/Certificate Issue
Process
MIS Reports
Revenue
Transfer
to
Accounts
Stop
Page -
97
4.7.4 Algorithm
4.7.4.1 Module Algorithm
Step 1: [Data Feeding] Read: Filling Revenue Collection Form Details.
Step 2: [Document Collection] Revenue Other Information Collection.
Step 3: [Predefined Process] Documents and Data Collection.
Step 4: Procedure: Revenue Collection Detail Processing.
Step 5: [Condition Check] Verification of Document Status.
Step 6: If found un-authenticated details
Procedure: Cancellation Process and Exit or Go To Step 11.
Step 7: If found authenticated details
Procedure: Issue Receipts and Certification.
Step 8: [Data Store] Write: To Database.
Step 9: Procedure: Revenue Transfer To Accounts.
Step 10: [Printing] Print MIS Reports.
Step 11: Exit
Page -
98
4.7.4.2 Receipt Generation Algorithm

Example Dukaan Sansthan New Registration / Renewal Receipt Issue
Step 1: [Initialize] Payment Type
Step 2: Read: Registration No.
Step 3: [Condition check]
If invalid Registration No
Exit or Step 8
Else
Continue
Read: Receipt Date
End If
Step 4: Procedure: Find Registration Details on basis of Reg. No.
Step 5: [Condition Check] Read: Payment Type
If Payment Type = Cheque
Read: Bank Name, Cheque No, Cheque Date
Read: Registration / Renewal Fee
Continue
Else if Payment Type =Cash
Read: Registration / Renewal Fee
Continue
End if
Step 6: Write: To Database
Step 7: Procedure: Issue Receipt with new receipt no.
Step 8: Exit
Page -
99

In context level diagram we are representing the basic functionality and working of the department as a
whole process by using the common required inputs and their possible outputs.
As per the basic functionality of the revenue collection system software we receiving the specific revenue
details as input for the system and provides the receipts, certificates and MIS reports as the output of the
system.
Application for Registration
Shop Keepers /
Picture Halls /
Hawkers Zone/
GMC Market
MIS Reports
Fee/ Rent
Registration Certificate/
Permissions
Revenue
Department (Admin)
0-Level
Receipts
Revenue
Collection
System
Input Data
Zonal Office/
Departments (Users)
MIS Reports
Date Wise and Head wise

Collection Transfer to
Account Department
Account Department
0 LEVEL DIAGRAM
Page -
100
from Revenue Master
Database
New Registration
1.0
2.0
Revenue
Master
Revenue Book
Keeping

Revenue Transaction
Database
Fetching Record for Registration
New Registration
Revenue
Transaction
Fetching
Re
cor
ds
Providing MIS
Reports or
Permission Letter
Certificates
from Revenue
Receiving Database
Zonal Office/
Departments (Users)
Receiving Fee/ Rent
from concerning
bodies
MIS Reports,
Permission Letter &
Certificate Generation
Revenue
Receiving
Revenue
Department
Shop Keepers /
Picture Halls /
Hawkers Zone/
GMC Market
Date & Head Wise

Collection Transfer to
Account Department
3.0
4.0
Fee / Rent Receiving

Store in Ledgers
Fund Transfer
Revenue
Ledgers
Providing
Receipt
against
Property
Tax
Demand
Shop
Bill
Date & Head Wise

Collection
Transfer to
Account
Department
Receive money
against Property
Tax Demand Bill
Accounts
Department
Keepers /
Picture Halls /
Hawkers Zone/
GMC Market
1 LEVEL DIAGRAM
Page -
101
Zonal Office/
Departments (Users)
1.1
Revenue Master Book
Keeping
Fetching Master Information for

Transaction
New Registration
Revenue
Master
Fetching Record for Registration
New Registration
Revenue
Transaction
Fetching
Record for
Registration
Adding New
Transaction
Revenue
Receiving
Adding New
Transaction
1.2
Revenue Transaction
Book Keeping
Fetching Record for

Correction
1 LEVEL DIAGRAM
Page -
102
2.1
Revenue
Master
Revenue MIS Reports

Generation

Reports Generation
Fetching
Records for
Certificates/
Permission

Certificates/ Permission

Reports Generation
Revenue
Transaction
Fetching
Records for
Certificates/
Permission
Revenue
Receiving
2.2
Issue Certificates/
Permission latter
Print or
Display
Records
Print or
Display
Records
2.3
Reports/ Certificates/
Permission latter)
2 LEVEL DIAGRAM
Page -
103

Receipts Generation
Search Record for Fee/ Rent

Receiving
3.1
Revenue
Master
Fee /Rent Receiving
Search Record for Fee/

Rent Receiving
Revenue
Transaction
Fetching
Records for
Receipts
Generation
Update Fee/ Rent

Receiving
Revenue
Receiving
3.2
Receipt Generation
3.3
Print Receipt
Print Receipt
2 LEVEL DIAGRAM
Page -
104
4.1
Search Records for Transfer
to Account
Search Records for

Transfer to Account
Fee/ Rent Receiving
by Cash
Revenue
Receiving
Update Revenue
Ledger
Revenue
Ledger
4.2
Update Revenue
Ledger
Fee/ Rent Receiving

by Cheque
2 LEVEL DIAGRAM
Page -
105

Div. ID
IDiv. ID
Div Name
Division Master
Remarks
H
as
Zone No
Zone Name
Zone Master
Revenue Master
Description
Division ID
Date ID
H
as
Ward ID
Date Master
o
Zone No
Ward Master
Date
Descriptio
n
iption ID
Locality
H
as
Loc. Name
Ward No
Locality Master
Used In
Loc. Class
A
Remarks
Page -
106
Financial
Year Date
A
Rw ID
Locality
ID
Rw. Issue
Date
Head ID
Revenue Master
Contact
Ending
Date
Fee ID
Date ID
Contact
Issue Date
Party Name
Party Address
Party Phone No
Fee ID
Head ID
Remarks
Remarks
Fee Amt
Head Name
Fee Master
Head Master
Has
Rept. No.
B
Fin. Year
Remarks
Reg. ID
Receipt Master
Rept.
Type
Has
Date ID
Rept. Date
Penalty
Amt
Bank Name
Cheque
No
Cheque
Dt.
License
Amt
Fee Amt
Page -
107
Date ID
Rew. ID
Bank Name
Rev. ID
Cheque No
Rew. Dt
License
Amt
Fin. Year
Date
New Renewals
Period
From
Penalty
Amt
Period To
H
as
Used
In
Remarks
Date
From
Financial Year
Date
From
User
Name
Password
Password
Page -
108
4.7.7. Activity Diagram
Add/Edit/Delete
Registration, Renewal,
Certificate,
Permissions.
Zone Detail
New Revenue Details
Ward Detail
New Revenue Information

Provider
Due Renewal Listing

Code wise and Date
wise for shopkeepers.
Locality Info
General Search.
Category
Info
Single Registration
Renewal Information.
Renewal Details
Fee Detail
Renewal Information
Provider
Revenue Ledger Print.

Rev. Info.
User
Renewal Ledger Print.

Revenue Collection
Details.
New Fee
Rcpt
Rew &
Rcpt.
Other Information
Provider
Other
Receipt
Details
Certificate
User
Revenue Details
Verified documents
Certification / Receipts
Information Provider
Authenticated details
User
Authenticator
Page -
109
4.7.8.MIS Reports
1 Revenue Detail List
This report helps to find the revenue details including all information like ward no and locality from which
the revenue is collected, head name under which the revenue collected, fee details if there is any kind of
charges on basis of some head criteria, Party name and address etc.
2 Receipts
This format is related to the receipt of new renewal with the payment details (like payment through cash
or cheque) against the amount received from new revenue, renewal or any other way.
3 Revenue Ledger
This format will print the ledger that shows the complete details of the revenue details collected on that
specific date with probable details like ward number.
4 Renewal Ledger
This format shows the details of that revenue information whose renewals are done and print as a renewal
ledger. The ledger will print all the details. Note that the renewal is done with the specific requirement.
5 Revenue Collection Details
This report format displays the revenue collected by the department against the payment received either
through new revenue, renewals or duplicate certificate issue either by cash or cheque.
Page -
110
4.8 Central Purchase

This module looks after all aspects of Central Purchase including Item Details, Supplier Details, Unit
Details, Purchase of material from Supplier, Direct Purchase, Material issue to various department and
In/Out of rejected vehicle parts. This software is fully privileged based and password protected. Users
are defined as per the Workshop Officer authorization.
It looks after all type of financial aspects of Central Purchase and reports are generated according to the
person concerned as per the requirement. As Central Purchase is one of the main department of any
establishment like GMC, it is developed by the highly qualified professionals with a huge knowledge of
all if and buts of Workshop.
The interface provides the ability to:
Input information in details.
Search and display the records.
Print MIS reports.
operations.
Builds a solid IT backbone by integrating the entire operations of the Municipal Corporation.
Creates an intelligent Complaint-Redress System.
Page -
111

transactions through computer system, and generate the MIS reports. The all requirements are Shown
below:
To maintain the master data separate from the daily transactions.
To save the time for transactions processing.
To provide the transparent and accurate data to the department.
To keep the data and details in proper format.
Required to have computerized search to find quick details as per different parameters.
To Provide help to the Management/ Administration to take their Decisions based on the following MIS
reports:
Stock Status.
Periodic In/out OF Material.
Periodic Status Of Item to various Department.
Periodic Purchase Status.
Periodic Status Of Material Issue.
Periodic Direct Purchase Status
Page -
112
4.8.3 Flowchart
Start
Enter Items Detail
Enter Item Issue Name and

N Qty.
No
Generate PO For N Qty
If Qty >=
N
Yes
Yes
Qty. Received No
M=N-Rec. Qty
Issue Item
If M
>0
No
Error
Update Stock
Data
Store
Stop
Page -
113
4.8.4 Algorithms
Step 1: Start
Step 2: Input Item Details
Step 3: Input Item Issued Name and Quantity.
Step 4: If Quantity < Number then go to Step 5
Else go to Step 8
Step 5: Issued Item
Step 6: Update the Stock
Step 7: Storage of Data
Step 8: Generate PO
Step 9: Stop
Page -
114
Departments/Zonal
Offices
Indents for Items
0-Level
Item Received/ Item Issued
Central
Purchase
Input Data
Zonal Offices
MIS Reports
0-LEVEL DIAGRAM
Page -
115
Fetching
Information from
CP
Master
Database
Register New Indents
1.0
from CP Transaction
Database
CP Book Keeping
Fetching Record for
Correction
2.0
MIS Reports &
Generation
CP
Transaction

records
Providing
MIS Reports
Fetching
Information from
CP
Receiving
Database
Zonal
(Operator)
CP
Department
Fetching
Records
Zonal office
Indents
3.0
Item Receiving
1-LEVEL DIAGRAM
Zonal Office
(Operator)
1.1
CP Master
CP Master Book
Keeping
Fetching
Master
Information
for
Transaction
Fetching Record for

Correction
CP Transaction
1-LEVEL DIAGRAM
Page -
116

Bill Generation

MIS Reports
Generation
2.1
CP Master
CP MIS Reports
Generation
CP Transaction
MIS Reports
Generation
Fetching
Records for
Bill
Generation
Fetching
Records for
Bill
Generation
Bill Receiving
2.2
Bill Generation
Print or
Display
Record
s
Print or
Display
Record
s
2.3
Display or Print
(MIS Reports or
Bill)
3-LEVEL DIAGRAM
Page -
117

Unit
Rate
OpStock
ItemNa
me
TypeName
SubTyName
SubTypeID
Remarks
Remark
Remar
ks
ItemId
SubTypeMaster
Has
TypeMaster
ItemMaster
Has
Rate
Rate
Qty
Has
BalQty
Qty
TypeId
ClStoc
k
ItemCo
de
BalQty
POItem
POGiItem
DisDesc
Has
Podate
DisDesc
TotalAmt
DisPer
DisPer
Has
ChId
TaxDesc
TotalAmt
Tax Desc
DelDate
POMaster
POId
POGiMaster
Has
Remarks
DisAmt
TaxPer
TotalAmt
TotalAmt
DisAmt
SuppMaster
Used In
TaxAmt
TaxPer
PhNo
SuppId
TotalAmt
Remarks
ContPer
GIItem
Has
GIMaster
GiId
Address
CompName
Terms
GiDate
Has
DisDesc
Terms
Qty
Rate
DisAmt
TaxDesc
TaxPer
TaxDesc
TaxAmt
Dpd_Details
GiId
Remarks
TotalAmt
Terms
GiDate
Qty
Has
Qty
Remarks
TotalAmt
Terms
TaxPer
RejIn_Master
TaxDesc
TaxDesc
TaxAmt
RejInId
RejInDate
Deptt
Rate
DisDesc
DisAmt
Rate
Dpd_Master
Has
RejIn_Details
BillNo
DisDesc
Deptt
DisAmt
TaxPer
TaxDesc
TaxAmt
TaxDesc
RejOutiId
BillNo
Remarks
TotalAmt
Terms
RejOutDate
RejOut_Master
RejOut_Details
Has
DisDesc
Rate
Deptt
Qty
DisAmt
TaxPer
TaxDesc
TaxDesc
TaxAmt
BillNo
Page -
118

Central Purchase
Type
SubType
Supplier
TCBC
Operator
Units
Department
Item
Zonal Offices
Purchase Order
Reporting
Current Stock.
Item Periodic Status.
Periodic PO Status.
Periodic Status of Inward Challan against PO
Periodic Status of PO Cancellation.
Periodic Status of Direct Purchase.
Material In From various Dept.
Periodic Status of Material Issue.
Periodic Status of Vehicle Maintenance.
Periodic Status of Rejected In/Out Material.
Periodic Status of Katta In/Out
Inward Challan
PO Cancellation
Direct
Purchase
Material/In
From Dept.
Material Issue
Katta Out/In
Rejection In/Out
Page -
119

4.8.8 MIS Reports
1. Stock Status
This report Shows the status of the items related to there opening stock, closing stock, rejection stock, unit and
there total.
2. Periodic Item Wise Status
This report shows periodic in and out status of the Item.
3. Periodic Status of PO
This report shows the periodic status of Purchase Order
4. Periodic Status of Inward Challan against PO
This report shows the periodic status of Inward Challan against Purchase Order.
5. Periodic Status of PO Cancellation
This report shows the periodic status of PO Cancellation.
6. Periodic Status of Direct Purchase
This report shows the periodic status of Direct Purchase.
7. Periodic Status of Issued Items
This report shows the periodic status of Item issued to different departments.
8. Vehicle Under Maintenance
This report shows periodic status of Vehicle maintenance.
9. Material In From Various Department
This report shows periodic status of material in from various departments.
10. Rejection In Status
This report shows periodic status of rejected material in from various departments.
11. Rejected Out Status
This report shows periodic status of rejected material out from various departments.
Page -
120

4.9 Jankarya
This document is intended for Jankarya software specification, which is one of the most important parts of the
Project titled ERP.
According to the existing system Jankarya module is totally manually. All work related to that is depend on
the manual file handling. Due to manual work we are not able to search the records quickly. We all know that
manual work is not so much reliable and fast thats why the whole procedure of generating a certificate
becomes a very tedious job.
Jankarya module is divided into two parts:
1. Construction Permission done by Gwalior Nagar Nigam
2. For Building Permission.
Application Filling
Dayara Filling
Final Building Permission
1. Construction detail registers

2. Application detail registers
3. Dayara detail registers
4. Registers of Permitted Files for detail entry
Page -
121
4.9.3 Flow Chart

Start
New Application Filed for

Building Permission
Information
New Dayara Entry against

Application No.
No
Application/
Dayara
Exists
YES
Information
Verification
Process
No
YES
A
Page -
122
Granted Permission (File)

Information
Data
Store
File Number Issued
Reports
Stop
Page -
123

4.9.4 ALGORITHM
Step1: Start.
Step2: Enter new application filed for building permission.
Step3: Enter new dayara entry against application number.
Step4: Check for application or dayra.
Step5: If not exist then go to Step1 else continue.
Step6: Processing information verification.
Step7: Granted Permission (File) Information.
Step8: File number Issued.
Step9. Stop.
4.9.5
Data Flow Diagram

Page -
124
Provide information of
jankarya
Users
Jankarya Department
Reports
0 Level
MIS Reports
Input Data
Application Registration
For Building Permission
0- LEVEL DIAGRAM
Page -
125
Fetching Information For MIS Report
1.0
Building Application
Master Entry
Jankarya
Book Keeping
2.0
MIS Report
Generation
Dayara Master Entry

records

Providing
MIS Reports
Jankarya
Office
(Operator)
Jankarya
Department
Nagar
Nigam
1 LEVEL DIAGRAM
Page -
126

4.9.6 E-R Diagram
SNo.
Prakaran
No.
Ward No.
Work
Name
Workplace
Zone No.
Estimated
Amount
Remarks
Book
No.
Estimation
Date
Payble
Amount
Construction Master
Tender Date
Complitio
n Time
Tender Rate
Senctioned
Date
Contractor
Name
Senctioned
Amount
Senctioned
SNo.
Used
In
Dat
e1
Dtid
Date_Master
Page -
127
App. No.
App.
date
Applicant
Name
Zone No.
F/H Name
Malba
Masala Fees
Address
Application Master
Measuremen
t
Const. Fees
Receivers
Name
Cancellation
Date
Building
Type
Used
In
Result
Dtid
Date
1
Date_Master
Page -
128
File
Number
Applicatio
n Number
Applica
nt Name
F/H Name
Remarks
Building
Number
Certificate
date
Dayara Master
Address
Certificat
e Number
Zone No
Used
In
Date
1
Dtid
Date_Master
Page -
129
Applica
nt Name
File Number
Zone No
Application
Number
F/H Name
Remarks
Address
Certificate date
Permission Master
Building
Number
Certificate
Number
Used
In
Date1
Dtid
Date_Master
Page -
130
Add/Edit/Delete
Application
Master
Dayara and Permission
Register
Reports:
Dayara
Master
Operator
MIS report for construction work details

MIS Report for Year wise construction work
MIS Reports for Application details
MIS Report for Dayara Details
MIS Report for Permitted File Details
Permission
Application Register
Master
Constructio
n
Work
Master
4.9.8 MIS Reports

1. Full detail of Construction work with record finding and Reports
2. MIS Reports of Construction works in a particular year
3. MIS Reports of Construction works on selected parameters
Page -
131

4. Full detail of Application Filing and record Finding of selected parameters
5. Full detail of Dayara Filing and record Finding of selected parameters
6. Full detail of permitted Files for Building construction.
4.10 Workshop
Page -
132

This module looks after all aspects of Workshop including Vehicle Details, Vehicles Insurance Due dates,
Vehicle parts, Purchase of material from Supplier, Direct Purchase, Material issue to various department
and In/Out of rejected vehicle parts. This software is fully privileged based and password protected. Users
are defined as per the Workshop Officer authorization.
It looks after all type of financial aspects of Workshop and reports are generated according to the person
concerned as per the requirement. As Workshop is one of the main department of any establishment like
GMC, it is developed by the highly qualified professionals with a huge knowledge of all if and buts of
Workshop.
The interface provides the ability to:
operations.
3. Provides a Controlling Tool to the Municipal Commissioner.
Page -
133

transactions through computer system, and generate the MIS reports. The all requirements are Shows
below:
6. To Provide help to the Management/ Administration to take their Decisions based on the following MIS
reports:
Stock Status.
Periodic In/out OF Material.
Periodic Status Of Vehicle Maintenance.
Vehicle Insurance Reminder.
Periodic Purchase Status.
Periodic Status Of Material Issue.
4.10.3 Flow Chart

Page -
134

Start
Enter Items Detail
Enter Item Issue Name and

N Qty.
No
If QOH >=
IQ
Generate PO For N Qty

Yes
Yes
Qty. Received
M=N-Rec. Qty
Issue Item
If M
>0
No
Error
Update Stock
Data Store
Stop
Flowchart 1.1
Page -
135

4.10.4 Algorithms
Algorithms of Flowchart 1.1:
Step1: Start.
Step2: Input Items Detail.
Step3: Input Item Name and N Qty.
Step4: If Quantity On Hand less then N quantity then go to Step 7.
Step5: Issue Items to department.
Step6: Update Stock.
Step7: Generate Purchase order.
Step8: Received Item against Purchase Order, calculate balance qty (M= N- Qty. Rec.) and Update stock.
Step9: If M greater then 0 then go to step 8
Step10: Stop
Page -
136

MIS Reports
Users
Department/Admin.
0-Level
Enter Records
Work Shop
Receive Material
Vehicle For
Maintenance
Bill Received
Supplier
Maintenance
Center
Purchase Order
0 LEVEL DIAGRAM
Page -
137
Fetching
Information from
Work Shop Master
Database
Register New Items
1.0
2.0
Work Shop
Master
Work Shop Book
Keeping
from
Work
Shop
Transaction Database
Fetching Record for

Correction
Enter New Transactions
Work Shop
Transaction

records
Items
Receiving
Fetching
Records
Receive PO
Fetching
Records
4.0
Vehicle
Maintenance
Item Receiving
Against PO
Item Receive
Work Shop
Department
from
Work
Shop
Vehicle Database
Vehicle
Maintenance
3.0
Providing
MIS Reports
from
Work
Shop
Items
Receiving
Database
Work Shop
(Operator)
Receiving Items
MIS Reports &

PO Generation
Vehicle For
Maintenance
Maintenance
Bill
Maintenance
Center
Suppliers
1- LEVEL DIAGRAM
Page -
138
Work Shop
(User)
1.1
Fetching Master
Information for
Transaction
Register New Items
Work Shop
Master
Work Shop Master

Book Keeping
Work Shop
Transaction
Fetching
Record for
Correction
Adding New
Transaction
Item Receiving
Fetching Record for
Correction
Adding New
Transaction
1.2
Work Shop
Transaction Book
Keeping
2- LEVEL DIAGRAM
Page -
139
Fetching Records for PO

Generation

Reports Generation
2.1
Work Shop
Master
Work Shop MIS

Reports Generation

Reports Generation
Fetching
Records for
Demand Bill
Generation
Work Shop
Transaction
Fetching
Records for
PO Generation
Item Receiving
2.2
PO Generation
Print or
Display
Records
Print or
Display
Records
2.3
Reports)
2- LEVEL DIAGRAM
Page -
140
3.1
Fetching Records for PO

Updation
Search Record for

Item Receiving
Work Shop
Master
Item Receiving
Search Record for

Item Receiving
Update Item
Receiving
Work Shop
Transaction
Fetching
Records for
Stock
updation
Item Receiving
3.2
Update Stock& PO
Status
2- LEVEL DIAGRAM
Page -
141

Unit
Rate
OpStock
VType
ItemNam
e
TypeName
SubTyName
Remarks
TypeId
ItemCo
de
SubTypeID
Remark
Remar
ks
ItemId
Remarks
VTypeId
ClStoc
k
VehicleTypeMaster
SubTypeMaster
ItemMaster
Has
WSBillNo
DisDesc
POMaster
POId
EngNo.
Remarks
DisAmt
TaxPer
TotalAmt
UMDetails
TotalAmt
DisAmt
SuppMaster
Used In
Insdate
VehicleId
TaxAmt
POGiMaster
Has
ItemName
FTppe
VehicleNo.
DisPer
Has
ChId
Tax Desc
DelDate
Has
Rate
DisDesc
TotalAmt
DisPer
Has
Podate
Qty
Model
POGiItem
TotalAmt
UMMaster
Has
RegDate
POItem
Remarks
UMid
TaxDesc
Fax
MantMaster
BalQty
TotalAmt
Date
MantId
Has
UmDate
Terms
PhNo
CompName
BillDate
Qty
Address
Qty
Contper
Rate
WSFileno
Remarks
Used In
Rate
Has
BalQty
TypeMaster
TaxPer
PhNo
VehicleMast
SuppId
Used In
TotalAmt
ContPer
GiDate
GIMaster
GiId
Has
GIItem
Has
DisDesc
Address
CompName
Terms
Terms
Qty
TaxDesc
TaxPer
Rate
DisAmt
BillNo
TaxDesc
TaxAmt
GiId
Remarks
TotalAmt
Terms
GiDate
Used In
Dpd_Master
Dpd_Details
Has
DisDesc
Deptt
Qty
Rate
DisAmt
TaxPer
Qty
TaxDesc
RejInId
BillNo
Rate
TaxDesc
TaxAmt
Remarks
TotalAmt
Terms
RejInDate
RejIn_Master
RejIn_Details
Has
DisDesc
Deptt
TotalAmt
TaxPer
TaxDesc
Terms
RejOutDate
BillNo
RejOut_Master
RejOut_Details
Has
DisDesc
Deptt
DisAmt
Qty
TaxPer
TaxDesc
TaxAmt
TaxDesc
TaxDesc
TaxAmt
RejOutiId
Remarks
DisAmt
Rate
Remarks
Remarks
Dept.
BillNo
Page -
142

Add/Edit/Delete
Work Shop
Type
SubType
Supplier
Vehicle
Operator
Vehicle Type
Maintenance
Item
Purchase Order
Inward Challan
Reporting
Current Stock.
Item Periodic Status.
Periodic PO Status.
Periodic Status of Inward Challan
against PO
Periodic Status of PO Cancellation.
Periodic Status of Direct Purchase.
Material In From various Dept.
Periodic Status of Material Issue.
Periodic Status of Vehicle Maintenance.

Periodic Status of Rejected In/Out Material.
Vehicle Insurance Reminder.
PO Cancellation
Direct
Purchase
Material/In
From Dept.
Material Issue
Vehicle Under
Maintenance
Rejection In/Out
Page -
143
4.10.8 MIS Reports
1 Stock Status
This report Shows the status of the items related to there opening stock, closing stock, rejection stock, unit and there
total.
2 Periodic Item Wise Status

This report shows periodic in and out status of the Item.
3 Periodic Status of PO
This report shows the periodic status of Purchase Order
4 Periodic Status of Inward Challan against PO
This report shows the periodic status of Inward Challan against Purchase Order.
5 Periodic Status of PO Cancellation
This report shows the periodic status of PO Cancellation.
6 Periodic Status of Direct Purchase
This report shows the periodic status of Direct Purchase.
7 Periodic Status of Issued Items
This report shows the periodic status of Item issued to different departments.
8 Vehicle Under Maintenance
This report shows periodic status of Vehicle maintenance.
9 Material In From Various Department
This report shows periodic status of material in from various departments.
10 Rejection In Status
This report shows periodic status of rejected material in from various departments.
11 Rejected Out Status
This report shows periodic status of rejected material out from various departments.
4.11 Fire Brigade
Page -
144
4.11.1. Brief Description

This document is intended for Fire Brigade software specification, which is the module of Project
ERP. GMCs ERP is a true enterprise solution that integrates function across an organization and
enables E-Governance in future. It integrates with existing systems, financials, documenting, cashiering,
fields data collection etc. to make the organization a seamless functioning entity. The software has got
an exhaustive number of modules, which take care of each and every operation of Gwalior Municipal
Corporation. The main aim of computerization is to automate and standardize the operations of the
office of the commissioner, office of all the heads of departments, Zonal offices and other related entities
working under GMC. Further, we have established their connectivity with the head office and with other
with hi-tech Microwave Wireless Radio Networking system
This module deals all work related to the Fire Brigade Department. Panchnama, NOC and all such type
of certificates generated through automated system due to which we are able to track the records. This
Module is related to the Accounts one for Revenue collection. For Security point of view the Module is
totally password protected. All periodically reports can be generated easily as per the requirements of
Department. Module provides the features of financial year due to which we are able to track the
records which comes under that Financial Year.
Start
1.
2.
3.
4.
5.
6.
7.
8.
Enter Fire Call Details

Fire Call Records
Panchnama Records
Agni Report Records
Generation of Printed Receipt
Generation of Printed Fire Certificate
Fire Call
Generation of Printed NOC
Exist
MIS Reports
Transfer Revenue in Accounts
Enter Panchnama
Enter Agni Report

4.11.3 Flowchart
Request for
Fire
Certificate
Page -
145
Issued Fire
Certificate
Issued Fire
Certificate
Stop
Page -
146
4.11.4 Algorithms
Step 1: Start
Step 2: Enter Fire call Details
Step 3: If Fire Call Not Exit then go to step2
Else continue
Step 4: Enter Panchnama Report
Step 5: Enter Agni Report
Step 6: If not request for Fire Certificate then go to step7
Else Issue of Fire Certificate
Step 7: Stop
Page -
147
Application for NOC, Fire Certificate
Citizens
MIS Reports
Fire Department
Bill Payment
NOC,Fire Certificate
Bill Receipt
Fire Brigade
Input Data
Department
MIS Reports

Account Department
Account Department
0 LEVEL DIAGRAM
Page -
148
Fetching
Information from
Fire
Master
Register New Call
1.0
Fire
Master
Fire Call Book

Keeping

records
Fire Brigade
(Operator)
from Fire Transaction
Database
Fetching Record for

Correction
Register New Call
2.0
MIS Reports &
Generation
Fire
Transaction
Providing
MIS Reports
Fetching
Information from
Fire
Receiving
Bill Receiving
Fire
Department
NOC, Fire
Certificate Holders

Transfer to Account
Department
4.0
Store in Ledgers
Fund Transfer
Fire Ledger
1st Level DFD
1 LEVEL DIAGRAM
Page -
149
Fire Office
(Operator)
records
Fetching
Master
Information
Register New Call
1.1
Fire Master
Fire Master Book

Keeping
Fetching Record for
Correction
Fire Transaction
Register New Call
Fetching
Record
for
Adding New
Transaction
Adding New
Transaction
1.2
Connection Book
Keeping
Bill Receiving
Fetching Record
for Correction
2 LEVEL DIAGRAM
Page -
150

Bill Generation

MIS Reports
Generation
2.1
Fire Master
PHE MIS Reports

Generation
Fire Transaction
MIS Reports
Generation
Bill Receiving
2.2
Fire Certificate &

NOC Generation
Print or
Display
Record
s
Print or
Display
Record
s
2.3
Display or Print
(MIS Reports)
2 LEVEL DIAGRAM
Page -
151
4.11.6 Entity Relation Diagram

Batch No.
Name
Employee Master
FC
ID
Emp ID
Agni ID
Date
Remarks
Date
Has
Has
Remarks
Batch No.
Type
EmpID
Desg
Address
Name
Name
NOC
NID
Bank Name
Fire Certificate
Amount
Type
Type
Job ID
Daily
Job
Used In
Emp ID
Staff
Model
Reg
Date
NO.
DtId
Caller Add
Owner
Date1
Date
Owner Add
Amount
No.
Date Master
Used In
Daily Job
Used In
Remarks
Type
Vehicle
Master
Job ID
Vech ID
Job ID
Remarks
No.
Has
Has
Daily
Job
Tr
an
sa
ID
cti
on
Engine
No.
Caller
Time
Vech ID
Incharge.
Caller Nam
Fire Date
Hozi
Number
Telephone
Pumping
Water Qty
Rec No.
Vehicle
Trans.
Distance
Mobile oil
Labour
Station
Owner
Extra
Agni
Address
Party Name
Agni Durghtana
Date
Prop
Fire
De
sc
Reason
152
Page -
Other
Receipt
Admin
Add/Edit/Delete
Employe
e
Remar
ks
Vehicle
Fire call
Operator
Panchnam
a
Agni
Report
Hearing File
Reporting
Only Gwalior Nagar Nigam Cases

detail.
Fire Call detail.
Receipt Detail.
Fire Certificate detail.
NOC detail.
Receipt
Generation
Fire
Certificat
e
NOC
4.11.8 MIS Reports
Page -
153
1. Fire Call Status

Status of Fire Call in between particular time period, employees wise or vehicle wise.
2 Receipt Status
Status of Receipt in between particular time period, employees wise or vehicle wise.
3 Fire Certificate Status
Status of Fire Certificate in between particular time period, employees wise or vehicle wise.
4 NOC Status
Status of NOC in between particular time period, employees wise or vehicle wise.
Page -
154
4.12 Legal Section

Legal section is a department of Nagar Nigam, which handles Nagar Nigam Cases filed on or
by Nagar Nigam. These Cases are filed on any department of Nagar Nigam or by any employee on its
department. Cases type like Promotion, Atikraman, and Jankarya etc.. Some times it also acts as Third
Party. There are some advocates hired by Nagar Nigam for handling these cases. Existing System
maintain these advocates detail. It also maintain Dayra Registers, which contain Detail of Cases, like
department name, court name, party name and Advocate name. Advocates maintain a file which contains
information about cases hearing, court decisions and periodically update these files. Finally it produces
MIS reports for case details that specifies party names, advocate names, court names, case hearing
dates, court decisions and status of cases through typewriter.
4.12.2 User Requirement
Automate Legal Section department.

Eliminate bookkeeping records.
Daily updation of case as per hearing.
Generate report as per Performa with advance search option.
Eliminates MS-office software that is using for prepare report.
Page -
155
4.12.3 Flow Chart
Start
Enter Case Detail for

Registration
Check
Contempt
Cases
NO
YES
Input
File Reference No.& Case No.
Case Registration
Input Case Status Per

Hearing
Data
Store
Case Status Update
MIS
Reports
End
4.12.4 Algorithms
Step 1 : Start
Page -
156
Step 2:Entry case information like case registration date in court, court, department name, concerning
person of department, dispute place, advocate name, whom are favour of case and whom are against the
case.
Step 3 : If case is contempt then it should be existing that has been closed.
Step 4 : Yes, enter file order no and reference of existing case then case registered.
Step 5 : No, case registered.
Step 6 : Daily Update case status as on hearing of the case.
Step 7 : Generate MIS report with advance search option.
Step 8 : END
Page -
157
0
User
Case Entry
Legal Section
System
Case Status Detail
Court
MIS Reports
Legal Section
Department
And Admin
0 LEVEL DIAGRAM
1.0
User
Case Entry
Case
Registration
Copyright Amity IT Solutions
Pvt. Ltd.
Process
Case File Detail
Court
.
Page -
158
2.0
Update Case
Process
New Case
Detail
Case Registration
Update Case
Detail
3.0
Case Detail
Formatted
Case Detail
Case Detail
Produce MIS
Reports
Case Status Detail

MIS Reports
Legal Section
Department
And Admin
1 LEVEL DIAGRAM

Citizen
Name
Department
DeptI
D
HOD
Father
Name
Caseno
Resn
o
Addres
s
Advocate
Name
Advocate
Type
ADVOCATE
Page -
159
VADI PRATIVADI
DEPARTMENT
Casen
o
Resn
o
ADVOCATE CASES
APPLICATION
REGISTER
COURT
APPLICATION DETAIL
Casen
o
CourtID
Case
Favo
ur
Casedate
CourtI
D
Court
Nam
e
Remarks
Casen
o
Case
Statu
s
DeptId
Case date
Subject
Court
Decision
Next
Date
Dispute
place

Add/Edit/Delete
Case Register
Departme
nt
Employee
Advocate
Type
Reporting
Only
Gwalior Nagar Nigam Cases
detail.
Periodi
cal Cases detail.
Depart
ment. wise Case Detail.Page
Court
wise Cases detail.
Lawyer
160
Operator
Advocate
Court
Case Registration
Hearing File
Daily Case
Updation
4.12.8 MIS Report

Pending Cases
This generates report of pending cases status. Searching criteria for generate report are periodical,
department, caseno and name wise.
Solved Case
This generates report of solved cases status. Searching criteria for generate report are periodical,
department, caseno and name wise.
All Case Status.
This report generate by options like periodically, court wise, Final/Order/reject case, advocates wise
and solved case.
Only Gwalior Nagar Nigam Cases detail.
This is advance feature of the proposed system. It only generates case status report in which
Gwalior Nagar Nigam is involved. Searching option are court wise, favour side cases, against side
case and final cases.
Page -
161
Contempt cases report

This is other facility of the software that generates contempt cases report. Searching option are court
wise, periodic wise and solved / order / reject cases.
Page -
162
4.1 Udyan
4.13.1
Brief Description
The module Udhyaan of ERP will be developed to store information to support the Garden, Park and
Rotary maintenance on regular basis. This module looks after all plants, fountains, tube-well, statue, and
play-equipments of Garden including plant-distribution, complaints details. As long as the hardware and
software environment is capable of working with project ERP, it will work for Udhyaan.
The use of the new system shall require additional training for the staff due to the differences
between the automated system and the current manual procedure. The current manual procedure shall
remain in place in case of critical failure of the proposed system. The manual system shall be utilized
periodically to ensure that the backup process remains viable when called upon. The proposed system
shall also have on-site and off-site backups of the database and infrastructure.
4.13.2
1.
2.
3.
4.
5.
User Requirements
Garden, Park and Rotary details.

Plants details.
Vehicles information.
Plant distribution details.
Garden Maintenance information on regular basis.
Page -
163
4.13.3
Flow Chart
Start
Garden,Park,Rotary
, Plant,Vehicle
Master Information
New Plant
Distributio
n
No
Yes
Check Exist
Plant
No
Plant
Found
Yes
Plant Distribution Master
Update
Reports
Final Garden,
Plant Information
Stop
Page -
164
4.13.4
Algorithm
Step1: Start
Step2: Enter the Garden, park, rotary, plant, and vehicle master information.
Step3: If new plant required then check for availability.
Step4: If new plants not available then go to Step 2 else continue.
Step5: Garden and plant master information adds or updates.
Step14: Stop.
Page -
165

Users
Provide information
of Udhyaan
Reports
0 Level
Udhyaan Department
MIS Reports
Input Data
Udhyaan
0 LEVEL DIAGRAM
Page -
166
1.0
2.0
Udhyaan Master Entry

Udhyaan
Book
Keeping
MIS Report
Generation
Udhyaan Transaction Entry
Providing MIS
Reports

records
Udhyaan Office
(Operator)
Udhyaan
Department
Nagar
Nigam
0 LEVEL DIAGRAM
Page -
167
Udhyaan Office
(Operator)
1.1
Udhyaan Master
Book Keeping
Fetching Master Information

for Transaction
Input Plant details
Plant Distribution
Master
Input Plant details
Plant Distribution
Transaction
Fetching
Record for
Correction
Adding New
Transaction
1.2
Udhyaan
Transaction Book
Keeping
2 LEVEL DIAGRAM
Page -
168

Reports Generation
2.1
Udhyaan Master
Udhyaan MIS Reports

Generation
Udhyaan Transaction
Reports Generation
2.2

Reports)
2 LEVEL DIAGRAM
Page -
169
MotorName
Area
MotorCapacity
Locatio
n
GardenType
Sitting
NoOfPlan
ts
GardenName
ElectricPoles
Remark
s
Gid
NoStatu
e
Garden_Master
Garden_Details
Has
TubeWellCapacity
TubeWell
Has
Has
Remark
s
PlantMaster
Fountain Type
FountainName
Dtid
Remarks
Remark
s
Remarks
Pid
PlantsDist_Master
Plantname
Seaso
n
Date
NoOfPlant
s
Pdid
Has
Plantsdist_Details
Remarks

Page -
170
Add/Edit/Delete
Garden Register
Plant
Garden
Reporting
Garden Details
Vehicle
Plant Details
Vehicle Details
Operator
Plant Distribution Details

Garden
Details
Certific
Complaints Details
Maintenance Details
Plant
Plant Register
Distribution
Sheet
4.13.8
MIS Reports
Page -
171
1. Garden Details Report: Garden detail contains all the information like garden name, location, area,
sitting arrangement description, number of statue and their description etc.
2. Plant Details Report: This contains plant name, season name and their description.
3. Vehicle Report: Vehicle details contain vehicle no., model, registration date, insurance date, amount,
engine no., fuel type, and department.
4. Plant Distribution Details: This contains garden name, plant name, date of distribution, number of
plants, plant remarks and other remarks.
5. Complaints Details: This contains garden name, date of complaint, complaint details, remarks.
6. Maintenance Details Report: A Maintenance detail contains garden name, date and other remarks.
4.1 Zoo
Page -
172
A new system Zoo (Animal Classifications) of ERP will be developed to store information to support
the Zoo maintenance on regular basis, transfer daily money collection in accounts. This module looks
after all Animals aspects of Zoo including species type, block distribution, identity chart, acquisiondisposal, birth-death, diet chart and daily collections. As long as the hardware and software environment
is capable of working with project ERP, it will work for Zoo.
The use of the new system shall require additional training for the staff due to the differences between
the automated system and the current manual procedure. The current manual procedure shall remain in
place in case of critical failure of the proposed system. The manual system shall be utilized periodically
to ensure that the backup process remains viable when called upon. The proposed system shall also have
on-site and off-site backups of the database and infrastructure.
4.14.2
User Requirements
1. Animal Inventory details.

2. Animal Diet Chart details.
3. Identity chart information.
4. History Sheet Information of Endangered and other animals.
5. Animal in-out information on regular basis.
6. Income heads from visitors and parking get posted automatically after the verification of officer
concerned.
4.14.3 Flow Chart
Page -
173
Start
Zoo Parking /
Visitors
Animal Master
Information
Animal
Birth
/Death /
Disposal
/Check
Yes
Check Exist
Animal
Data
Store
Preparation
for Accounts
No
Exist
Animal
Found
Animal Diet
Information
No
Yes
Periodic Animal Status
A
Update
Reports
Animal
Birth
/Death /
Disposal
/Check
Yes
No
Final Animal
Information
Stop
Diet Information Updates

B
Page -
174
4.14.4 Algorithm
Page -
175
Step1: Start
Step2: Enter the Animal Master Information and go to Step 9.
Step3: If Animal birth or acquision then continue.
Step4: Periodic animal information adds or updates.
Step5: If Animal death or disposal then checks for exist.
Step6: If not exist then go to Step1 else continue.
Step7: If number of death animal greater than number of animal exist then go to step5
Else continue.
Step8: Periodic animal information adds or updates.
Step9: Enter the diet information with their quantity go to step3.
Step10: If Animal birth or acquision or death or disposal then continue.
Step11: Corresponding animal diet information updates.
Step12: Enter the zoo parking and visitors information.
Step13: Revenue transfer in accounts.
Step14: Stop.
Page -
176
Users
Provide information
of Zoo
Reports
Input Data
Zoo Department
0
Zoo
(Animal Classification)
MIS Reports
Consolidated
amount transfer
to accounts
Accounts Department
0 LEVEL DIAGRAM
Page -
177

Add/Update Data
2.0
1.0
Zoo Master Entry
Zoo Book
Keeping
Fetching
Information For
Correction
MIS Report
Generation
Zoo Transaction Entry
Add/Update Data

Providing
MIS Reports
Zoo Office
(Operator)
Nagar Nigam
3.0
Zoo Department
Fund Transfer

Transfer to Amount
Department
Accounts
Department
1 LEVEL DIAGRAM
Page -
178
Zoo Office
(Operator)
1.1
Zoo Master Book
Keeping
Input Animal details
Fetching Master Information for Transaction
Zoo Master
Zoo Transaction
Input animal details
Adding New Transaction
1.2
Zoo Transaction Book
Keeping
2 LEVEL DIAGRAM
Page -
179
Fetching Records for MIS Reports Generation
2.1
Zoo Master
Zoo MIS Reports

Generation
Zoo Transaction
Fetching Records for MIS Reports Generation
2.2

Reports)
2 LEVEL DIAGRAM
Page -
180

Sciname
Descripti
on
Aniname
Photo
Extinct
Unsexed
Tot. Male
Qty
AniId
Tot Female
Tot. Child
AniMaster
Contai
ns
AnimalDetails
Has
Kinds
Block Type
Has
AniFoodMaster
Animal Type
AniTid
Remarks
AniTyp
e
AniTid
AniTyp
e
SymNam
e
Remark
s
Ftype
Fid
ItemName
Unit
Remark
s
Animal Identity
Animal History
ISISn
o
Sex
House
name
BreadingSeason
DOB
PDam
Distributio
n
CName
PSire
Famil
y
Hindiname
Photo
AniName
Page -
181
Add/Edit/Delete
Animal
Darsak/Cycle Stand Register
Type
Block
Animal
Keeper
Identity
Operator
Chart
Certific
History
Sheet
Reporting
History Sheet Report
Identity Chart Report
Block wise Report
Animal Keeper Report
Dirt Chart Details
Animal Inventory Report
Date/Month Wise Visitors Collection Detail
Date/Month Wise Parking Collection Detail
Animal Birth Details
Animal Death Details
Animal
Stock Register
Master
Animal In/Out
Daily
Collection
Block
Distribution
4.14.8
MIS Reports
Page -
182
1. History Sheet Report: History sheet contains all the information like species name, common name, house
name, parents history, diet details and other biological information like order, family, genus and habitat
etc.
2. Identity Chart Report: This report contains all information of particular species like name, scientific
name, habitat place, breading season, nature, and other description with photograph of animal.
3. Block wise Report: The whole block is divided into six blocks (A, B, C, D, E, F) for best care of
animals. One animal keeper is assigned one block for feeding, nurturing and care of animals. One can see
the details of block by selecting the block name.
4. Animal Keeper Report: This report contains the information of animal keeper name, block name,
animal name and their schedule.
5. Diet Chart Details: It contains daily diet details of animals. Animal diet is divided in two parts. A)
Vegetarian B) Non-vegetarian. Daily, monthly and yearly diet schedule can be generated.
6. Animal Inventory Report: This report contains details of animal stock of current financial year with
species name and details of total male, female, unsexed and also total births, acquision, disposal and
deaths. Animals are also divided into two other categories as per norms of wildlife protection as
7. Extinct (Schedule-1)
8. Non extinct (Schedule-2)
9.Date/Month Wise Visitors Amounts Collection Detail:
10. Date/Month Wise Parking Amounts Collection Detail:
11. Animal Birth Details: This report contains date of birth, species name, animal name and remarks.
12. Animal Death Details: This report contains date of death, species name, animal name and remarks.
Page -
183

E - Municipality SRS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E - Municipality SRS

Uploaded by

Copyright:

Available Formats

SOFTWARE

Birth & Death

4.11 Fire Brigade

4.12 Legal Section

Entity Relationship Diagram

5.0 Solution Methodology

QP Query Poster (User)

1.2 Scope of the Development Project

Benefits to Municipal Corporation

1.3 Definition, Acronyms, and Abbreviations

1.5 Overview of Document

Wireless Radio Frequency Microwave Network

Central Server Architecture

2.2 Overview of Functional Requirements

Microwave Access Radio

High Gain Antennae

Wire rope Mast

Microsoft SQL Server (Desktop Edition)

Assumptions and Dependencies

2.5 Approval Systems

Approval Flow in the Approval Hierarchy

Software Hot key

3.2 Performance Requirements

3.4 Common Functions and procedures used in ERP

15. Function KeyUpper(KeyAscii As Integer) As Integer : Enables uppercase typing.

32. Sub Cancel() : Cancels or Undo a current operation using toolbar.

4. Documentation Requirements (Module Wise)

Ledger Balance Updating

4.1.3 Flow Chart

Ledger Posting And Balancing

4.1.5 Data Flow Diagram

Cash & Cheque Deposits

Cash / Cheque Deposit

Input Data (Voucher Enter)

Cash / Cheque receive

Budget Master Updation

Budget check for a

Budget Master Updation

Cheque Voucher Entry

Cheque Voucher Entry

Budget Master Updation

New Ledger Entry

4.1.6 Entity Relationship Diagram

4.1.7 Activity Diagram

Periodic Ledger Status

Debit Note Register

Revenue Generation From

1. Department wise budget status.

7. Employees increment details.

Employee Insurance information is

4.2.3 Flow Chart

Ledger detail Processing

Employee Loan information is stored

Monthly salary ledger

Enter Employee detail.

Enter Loan Detail of Employee.

Enter Insurance detail of Employee.

If Loan is avail then Loan is Processed goto step7

If Insurance is avail then Insurance is processed goto step7.

Salary Ledgerdetail is processed

If Employee have an arrear then Arrear Processed goto step12

If Employee have an absent then input no. of absent goto step12

Salary & Arrear Transfer into

4.2.4 Data Flow Diagram