SRS Version 1.17 (22-08-06)

Conceptual System Requirement Specification Ver. 1.
17 (22-08--06)
Contents
1.
INTRODUCTION.................................................................................................................................1
2.
SYSTEM OVERVIEW.........................................................................................................................2
2.1
GEOGRAPHIC INFORMATION SYSTEM (GIS)..........................................................................2
2.2
DDA INFORMATION SYSTEM (DIS)..............................................................................................2
3.
CONCEPTUAL SRS FOR EACH DEPARTMENT.........................................................................4
3.1
PLANNING...........................................................................................................................................4
3.1.1.
3.1.2.
3.1.3.
3.1.4.
3.1.5.
3.1.6.
3.1.7.
3.2
ARCHITECTURE................................................................................................................................8
3.2.1.
3.2.2.
3.2.3.
3.3
EXISTING APPLICATION FUNCTIONALITY.....................................................................................14

RECEIVE PROPOSAL AND CONDUCT PRELIMINARY SURVEY.........................................................14
APPROVAL AND MAINTENANCE OF RECORDS...............................................................................15
LAND ACQUISITION INFORMATION AND PROGRESS.....................................................................15
COMPENSATION............................................................................................................................16
WEB-BASED FUNCTIONALITY......................................................................................................16
MISCELLANEOUS..........................................................................................................................16
ENGINEERING WING.....................................................................................................................17
3.4.1.
3.4.2.
3.4.3.
3.4.4.
3.4.5.
3.4.6.
3.4.7.
3.4.8.
3.4.9.
3.4.10.
3.4.11.
3.4.12.
3.4.13.
3.5
RECEIVE PROJECT SCHEME DETAILS FROM ENGINEERING AND PLANNING................................10

PREPARE ARCHITECTURAL DESIGN.............................................................................................10
PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT................................10
LAND MANAGEMENT....................................................................................................................12
3.3.1.
3.3.2.
3.3.3.
3.3.4.
3.3.5.
3.3.6.
3.3.7.
3.4
PREPARE GIS BASED MASTER PLANS AND ZONAL PLANS (LONG TERM PLANNING)..................6
PREPARE ANNUAL AND MONTHLY PLANS.....................................................................................6
MONITOR/REVISE ANNUAL AND MONTHLY PLANS.......................................................................7
RECEIVE LAND DETAILS FROM LAND MANAGEMENT DEPARTMENT & PREPARE LAYOUT PLANS 7
PREPARE PROJECT SCHEMES AND DEVELOPMENT PLANS FOR THE PROJECT...............................7
BUILDING SECTION........................................................................................................................7
PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT..................................7
RECEIVE CONCEPTUAL / DEVELOPMENT PLANS FROM PLANNING DEPTT..................................19

RECEIVE DETAILS OF LAND ACQUIRED.......................................................................................19
ACTIVITIES OF CRB CELL...........................................................................................................20
MONITORING OF PRE-CONSTRUCTION STAGE..............................................................................20
PREPARE FEASIBILITY REPORTS FOR DETAILED PLANS................................................................20
PRELIMINARY ESTIMATES, ADMINISTRATIVE APPROVAL & EXPENDITURE SANCTION................21
PREPARE DETAILED ESTIMATES AND TECHNICAL SANCTION........................................................22
WORKS EXECUTION AND MONITORING.......................................................................................23
WORKS BUDGETING AND FINANCE RELATED FUNCTIONALITY...................................................24
PROJECT ACCOUNTING............................................................................................................25
ARBITRATION, ENCROACHMENT MONITORING AND DEMOLITION PLANS..............................25
WEB BASED ACCESS................................................................................................................26
PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT............................26
LAND DISPOSAL..............................................................................................................................27
3.5.1.
3.5.2.
3.5.3.
3.5.4.
3.5.5.

INTEGRATION WITH OTHER DEPARTMENTS..................................................................................29
FLOAT SCHEME FOR RESIDENTIAL, COMMERCIAL AND/OR INSTITUTIONAL ALLOTMENT............30
RECEIVE APPLICATION FORM AND REGISTRATION MONEY FROM BANKS..................................30
ALLOTMENT OF LAND/SHOPS BY AUCTION, TENDER, COMPUTERIZED DRAW, RESERVED PRICE.31
Delhi Development Authority
SRS
Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

3.5.6.
3.5.7.
3.5.8.
3.5.9.
3.5.10.
3.5.11.
3.5.12.
3.5.13.
3.5.14.
3.5.15.
3.5.16.
3.5.17.
3.5.17.
3.6
HOUSING............................................................................................................................................36
3.6.1.
3.6.2.
3.6.3.
3.6.4.
3.6.5.
3.6.6.
3.6.7.
3.6.8.
3.6.9.
3.6.10.
3.6.11.
3.6.12.
3.6.13.
3.6.14.
3.6.15.
3.6.16.
3.6.17.
3.6.18.
3.6.19.
3.6.20.
3.6.21.
3.6.22.
3.6.23.
3.7
RECEIVE ZONAL PLANS FROM PLANNING...................................................................................51

CONDUCT PRELIMINARY SURVEY AND IDENTIFY ENCROACHMENT AREAS..................................51
CONDUCT DETAILED SURVEY AND PREPARE LANDSCAPE PLANS.................................................51
MODIFY LANDSCAPE PLANS BASED ON FEASIBILITY STUDY......................................................51
HORTICULTURE..............................................................................................................................52
3.8.1.
3.9

RECEIVE DETAILS OF FLATS AVAILABLE FROM ENGINEERING......................................................43
FLOAT A HOUSING SCHEME.........................................................................................................43
RECEIVE APPLICATION FORM AND REGISTRATION MONEY FROM BANKS..................................44
CONDUCT COMPUTERIZED DRAW................................................................................................44
PREPARE CONSOLIDATED REFUND CHEQUES BANK WISE...........................................................44
CALCULATE HOUSING COST AND DEMAND................................................................................44
ISSUE DEMAND LETTERS TO ALLOTEE........................................................................................45
RECEIVE PAYMENT DETAILS FROM BANKS.................................................................................45
ISSUE POSSESSION LETTER.....................................................................................................45
INTIMATE HAND OVER OF POSSESSION TO HOUSING.............................................................46
EXECUTE CONVEYANCE DEED................................................................................................46
RECEIVE APPLICATION FOR CONVERSION TO FREEHOLD FROM BANKS.................................46
VERIFY OUTSTANDING DUES..................................................................................................46
RECEIVE PAYMENT DETAILS FROM BANKS............................................................................47
APPROVE CONVERSION AND ISSUE CONVEYANCE DEED.......................................................47
RECEIVE COMPLAINTS OF VIOLATIONS FROM PUBLIC............................................................47
CHECK VIOLATION AND ISSUE SHOW CAUSE NOTICE............................................................47
RECEIVE/APPROVE APPLICATION FOR REGULARIZATION........................................................47
ISSUE ORDERS FOR DEMOLITION/CANCELLATION OF LEASE.................................................48
RECEIVE APPLICATION FORM AND DOCUMENTS FROM APPLICANT........................................48
VERIFY DOCUMENTS AND APPROVE/REJECT THE APPLICATION............................................48
LANDSCAPE......................................................................................................................................49
3.7.1.
3.7.2.
3.7.3.
3.7.4.
3.8
ALLOTMENT OF LAND AS COMPENSATION TO ROHINI REGISTRANTS AND GH SOCIETIES.........31

ALLOTMENT OF SHOPS UNDER RESERVED CATEGORIES AND STAFF ORDERS...............................31
MONITORING AND DISPOSAL OF PETROL PUMPS, GAS GODOWNS, CNG STATION SITES.............32
MONITORING AND DISPOSAL OF COMMERCIAL BUILT UP PROPERTIES AND LICENSED UNITS.....32
ISSUE OF DEMAND LETTER......................................................................................................32
RECEIVE PAYMENT DETAILS FROM BANKS............................................................................33
PAYMENT, POSSESSION LETTER, CONVERSION TO FREEHOLD...............................................33
PERFORM TRANSFER OF PROPERTY AND MUTATION RELATED ACTIVITIES..............................34
RELOCATION/REDEVELOPMENT OF COMMERCIAL AREAS......................................................34
MAINTAIN RECORDS OF LEGAL CASES AND APPLICATIONS RECEIVED FROM CITIZENS..........34
WEB-BASED FUNCTIONALITY..................................................................................................35
36
DATABASE DEVELOPMENT AND INFORMATION............................................................................54
LEGAL DEPARTMENT....................................................................................................................55
3.9.1.
3.9.2.
3.9.3.
3.9.4.
3.9.5.
3.9.6.
3.9.7.
LEGAL CASE MONITORING SYSTEM............................................................................................58

LAWYERS FEE BILL PROCESSING SYSTEM..................................................................................58
RECEIVE SUMMONS/NOTICE FROM COURT AND OPEN CASE FILE.................................................59
FORWARD CASE FILE TO HOD FOR OPINION...............................................................................59
MONITOR CASE PROGRESS..........................................................................................................59
RECEIVE JUDGMENT AND OPINION FROM PANEL LAWYER.........................................................59
TAKE DECISION TO APPEAL/CLOSE THE CASE............................................................................60
SRS
ii

3.9.8. RECEIVE LAWYER FEE BILL........................................................................................................60
3.9.9. CALCULATE FEES AS PER POLICY.................................................................................................60
3.9.10.
ISSUE PAYMENT CHEQUE........................................................................................................60
3.9.11.
REPORTS..................................................................................................................................61
3.10 FINANCE DEPARTMENT...............................................................................................................62
3.10.1.
3.10.2.
3.10.3.
3.10.4.
3.10.5.
3.10.6.
3.10.7.
3.10.8.
3.10.9.
3.10.10.
3.10.11.
3.10.12.
3.10.13.
3.10.14.
3.10.15.
3.10.16.
3.10.17.
3.10.18.
3.10.19.
3.10.20.
3.10.21.
3.10.22.
3.10.23.
3.10.24.
3.10.25.
3.10.26.
CHART OF ACCOUNTS.............................................................................................................62
JOURNAL ENTRIES...................................................................................................................63
BUDGETING.............................................................................................................................63
REPORTING..............................................................................................................................63
CUSTOMER INFORMATION.......................................................................................................64
BILLING...................................................................................................................................64
CASH RECEIPTS/PROCESSING/RECONCILIATION.....................................................................65
REPORTING..............................................................................................................................65
INVOICES.................................................................................................................................65
VENDOR/CONTRACTOR INFORMATION....................................................................................66
BANK RECONCILIATION/ERROR CHECKING............................................................................66
REPORTING..............................................................................................................................66
LAND.......................................................................................................................................66
HOUSING.................................................................................................................................67
FIXED ASSETS MAINTENANCE.................................................................................................67
RESIDENTIAL LANDS...............................................................................................................68
COMMERCIAL LANDS..............................................................................................................68
INSTITUTIONAL LANDS...........................................................................................................69
PRE DETERMINED RATES FOR PROJECTS (COST BENEFIT ANALYSIS)....................................69
HOUSING COST.......................................................................................................................70
DEMAND AND COLLECTION REGISTER...................................................................................70
PRELIMINARY COST ESTIMATES..............................................................................................71
COMPILATION OF MONTHLY / ANNUAL ACCOUNTS................................................................71
PAYROLL MAINTENANCE........................................................................................................71
PAYROLL PROCESSING............................................................................................................72
3.11 PERSONNEL DEPARTMENT.........................................................................................................73

3.11.1.
3.11.2.
EXISTING APPLICATION FUNCTIONALITY................................................................................73

INTEGRATION AND FUNCTIONALITY ENHANCEMENT..............................................................74
3.12 WEBSITE FUNCTIONALITY.........................................................................................................75

3.12.1.
3.12.2.
3.12.3.
3.12.4.
3.12.5.
EXISTING INFORMATION ON WEBSITE.....................................................................................75

INTERFACE TO CUSTOMERS.....................................................................................................76
INTERFACE TO GENERAL PUBLIC.............................................................................................77
INTERFACE TO CONTRACTORS................................................................................................77
INTERFACE WITH SERVICE PROVIDERS LIKE BANKS, ONLINE AUCTION SITES........................77
3.13 OTHER SYSTEM REQUIREMENTS.............................................................................................78

3.13.1.
VIGILANCE SYSTEM................................................................................................................78
3.13.2.
PUBLIC RELATIONS.................................................................................................................78
3.13.3.
POSTAL MAIL/CORRESPONDENCE RECEIPT AND DISPATCH AT RECEPTION COUNTER...........79
MONITORING SYSTEM REQUIREMENTS......................................................................................................79
3.13.4.
FILE TRACKING AND RECEIPT AND DISPATCH SYSTEM REQUIREMENTS................................80
3.13.5.
VC OFFICE..............................................................................................................................80
3.13.6.
SYSTEM DEPARTMENT.............................................................................................................81
3.13.7.
OFFICE OF THE PRINCIPAL COMMISSIONER CUM SECRETARY................................................81
SRS
iii
1. Introduction
The Delhi Development Authority (DDA) was created in 1957 with the objective to promote and
secure the development of Delhi as per the provisions of the Delhi Development Act. Thus the
primary objective of DDA is to promote planned development of Delhi.
Delhi has been growing at a rapid pace and the situation will remain the same in the near future.
For DDA, to ensure meeting of its objective and delivery of quality services to its stakeholders, it
becomes imperative that the processes are efficient, and suitably enabled by technology. The
recent strides in Information Technology present new opportunities for process improvement and
efficiency enhancement within an Organization. With this aim in mind, DDA has undertaken a
project for Integrated Management System with the following main objectives:
Re-engineering and Integration of various existing applications/modules
Development of new applications
Development / Implementation of applications like Geographic Information Systems (GIS)
Providing adequate software training, handholding and post-implementation support to

concerned users on the software
This document contains a brief of the conceptual requirements of all the departments of DDA to
be covered under the proposed Integrated Management System and the main processes within
each of the departments. The objective of this document is to ensure that the vendors understand
the functioning of DDA and get a grip of the requirements of each department for the proposed
Integrated Management System to aid in the formulation of their effort and time estimates for
implementing the requirements. Based on the conceptual SRS a detailed SRS document will
have to be prepared by the vendor, which would lead to software development. It is important to
note here that modifications/improvements generated during the preparation of the detailed SRS
will have to be incorporated with the Integrated Management System.
SRS
2. System Overview
At present DDA has various applications running in its departments and these applications are
not fully integrated with each other. A description of these applications has been provided under
the respective department description and conceptual software requirements specification
section. It may be noted that wherever feasible and efficient, the proposed system would
incorporate the current application in the Integrated Management System. In case it is not
feasible, then these applications will have to be suitably modified to integrate into IMS or
redevelop as the case may be.
Also, all users in DDA should be able to use the system over intranet without the need to have
client software loaded on their machines.
The proposed Integrated Management System has 2 components A GIS component and A DDA
Information System (DIS) component. The application has been so designed that there is an
interface between the two components for exchanging information so that user requirements are
met.
3.
Geographic Information System (GIS)

GIS is a tool capable of storing, processing and analyzing geographic information, obtained
through various map surveys of different sources, including remote sensing and topographic data.
The GIS will enable DDA to develop an updated and correct spatial land database and use this
spatial database for better planning and land development activities. Access to updated and
correct land information will lead to efficient management of all activities of the departments.
The core user departments for the GIS application are Planning, Land Management, Architecture,
Landscape and Horticulture. These core departments will be able to use the GIS application for
viewing spatial data, prepare plans and schemes, use spatial data modeling for analysis and also
track project progress.
The other main user departments of GIS application are Engineering, Housing, Land Disposal,
Finance and Legal. These departments will be able to view spatial information and also edit
attribute data relating to a plot of land.
4.
DDA Information System (DIS)

The main objective of the DDA Information System (DIS) is to automate the business processes
within each department and also integrate the processes across departments for seamless
SRS

information exchange between departments. Accordingly, the system has been designed based
on the study of the business processes of each department and information flow across
departments.
In addition to specific modules for each department, a postal mail and file tracking system has
also been envisaged along with website functionality.
Web based functionality has been identified to ensure better manageability and better citizen
service levels and better integration with banks and other utilities.
SRS
5. Conceptual SRS for each Department

3.1
Planning
The Planning department at DDA is headed by Commissioner (Planning) who reports to the Vice
Chairman of DDA. The planning department is responsible for the long term planning and
development plans of DDA. The department is also responsible for the planning of project
schemes. The department also plays a regulatory role relating to planning permissions and
developmental control norms.
The structure of the department is as below:
1. Master Plan & Policy Preview Headed by an Additional Commissioner and performs
activities related to preparation of the Master Plan for Delhi
2. Area Planning Section This section is headed by an Additional Commissioner and
performs activities relating to planning in developed zones of the city.
3. Traffic and Transportation Section An Additional Commissioner looks after this section.
Planning of traffic and transportation networks is handled by this section
4. Projects This section handles planning activities for large projects such as Dwarka,
Rohini and Narela. Each project is headed by a Director who reports to an Additional
Commissioner.
5. Developmental Controls This section handles all regulatory functions of the department.
This section is responsible for ensuring that all development takes place as per the
developmental control norms specified in the Master plan. This section is also the basic
co-ordination unit for the department
The business process map for Planning department is given in the following page. From the
process map it can be observed that the main interaction for planning department is with Land
Management (for obtaining Land Acquisition information), Engineering (which utilizes the layout
plans for land demarcation and development) and Architecture (which utilizes the layout plans
project scheme plans for preparing architecture design)
SRS
SRS
SYSTEM REQUIREMENTS
5.1
Prepare GIS based Master Plans and Zonal Plans (Long Term Planning)
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
5.2
The system should allow the user to prepare master plans and zonal plans for Delhi
The system should be able to show the details of the same area at the master plan level,
zonal plan level and the layout level.
The system should be able to define the various zones and indicate the manner in which
the land in each zone is proposed to be used.
The system should have the provision of classification of various land uses as per the
Master Plan Norms.
The system should be able to show the land use classification zone wise.
The system should be able to integrate the Projects i.e., existing and targeted by Delhi
Development Authority, both in land use plan and policy proposals.
The system should enable the Planning of new road network in such a manner as to
prevent possibilities of future congestion by modifying road sections to accommodate
road side parking, and space for widening, expansion and provision of grade separators,
etc.
The system should enable development of an integrated relationship between the road,
rail and metro-system to provide for seamless multi-modal transport.
The system should enable transportation network analysis to facilitate efficient planning
The system should facilitate the planning of physical and social infrastructure including
sewage and solid waste disposal
The system should incorporate the development control regulations, zoning regulations
for a particular area to facilitate better planning
The system should be able to incorporate the building byelaws so as to keep a tab on
unauthorized developments.
The system should enable planning of drains and waterfront to be landscaped in the form
of interconnected parkways.
Prepare Annual and Monthly Plans

i.
ii.
iii.
iv.
v.
vi.
The system should allow the user to prepare annual and monthly plans
The system should ensure that the plans and programs are in line with the master plan
The system should enable the creation of specific project proposals and categorization of
the proposals into short and long term.
The system should enable the categorization of proposals into mandatory and optional
projects
The system should have the provision for incorporating information such as implementing
agency, development cost and resource usage for each proposal
The system should allow the user to view the planned proposals for each area.
SRS

5.3
Monitor/Revise Annual and Monthly Plans

i.
ii.
iii.
iv.
The system should allow the user to enter the status of each proposal.
The system should allow the user to revise a proposal.
The system should enable the user to view status of each proposal.
The system should generate appropriate reports on project progress etc as defined by
the user.
5.4Receive Land details from Land Management department & prepare Layout Plans
i.
ii.
iii.
iv.
v.
5.5
Prepare Project Schemes and Development Plans for the Project

i.
ii.
iii.
iv.
v.
5.6
The system should allow the user to define specific project proposals for a plot of land.
The system should ensure that the project is in conformance with the master plan/zonal
plan and land use specification
The system should ensure that the project proposal is as per the annual plan
The system should allow the user to develop the development plan for the project. The
system should allow the user to use the layout plan developed for this purpose.
The system should allow the user to view all the related plans for a project. The system
should allow the user to drill down from the master plan to specific project development
plans.
Building Section
i.
ii.
5.7
The system should allow the user to view the map of the land acquired by LM
The system should allow the user to overlay the master plan and zonal plans over the
land acquired for planning purpose
The system should allow the user to link the plot with a particular zonal plan.
The system should allow the user to develop layout plans for the land acquired in
conformance with the zonal plan/master plan.
The system should allow the user to view all the related plans for a plot of land and vice
versa.
The system should allow the user to monitor building construction details
The system should allow maintenance of building construction records as per
requirements
Provide various Reports as per requirements of the department
SRS
6.
Architecture
A Chief Architect heads the Architecture department at DDA. The architecture department is
responsible for
Developing the Urban Design / Architectural Schemes (residential and hierarchical & nonhierarchical commercial projects) and their Development Control Norms.
Heritage and Conservation projects; Sports related projects; Miscellaneous Projects
(community facilities, upgradation, etc.)
Conduct and co-ordinate Screening Committee Meetings for approval of all projects of
Planning, Architecture and Landscape departments
Approval from DUAC for urban design / architecture schemes ; approval from DUHF for
all conservation projects; Approval from SMB of all sports related projects; approval from
other authorities like CFO, Airports Authority, Environmental Clearances, etc.
The department is divided into 5 Zones, each zone handling projects under their area. Work in
the zonal section is monitored by two Additional Chief Architects who report to the Chief Architect.
A co-ordination, directly unit under the Chief Architect, conducts and coordinates Screening
Committee meeting for approval of all projects of Planning, Architecture and Landscape Depts.;
Overall coordination and compilation of projects of all units of HUPW; preparation of annual
administrative report and annual action plan and other administrative activities.
The business process map for Architecture department is given in the following page. From the
process map it can be observed that the interactions for architecture department is with
Engineering (for obtaining project scheme details and physical land survey details), Planning (for
obtaining the layout plans and project development plans), Land Disposal, other bodies like
SMB, DUAC, DUHF, CFO, Airport Authority, Environment Pollution Control, etc.
SRS
SRS
EXISTING APPLICATIONS
The Architecture department currently uses manual drafting and a very limited application of Auto
CAD software for designing purposes, the reason being inadequate training of personnel and
unavailability of adequate infrastructure. The Auto CAD application and other packages like
Architectural desktop, Rewitt etc. will have to be integrated with the Integrated Management
System. Usage of the Auto CAD application is to be increased through proper training.
SYSTEM REQUIREMENTS
6.1
Receive Project Scheme details from Engineering and Planning

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
6.2
Prepare Architectural Design

i.
ii.
iii.
6.3
The system should allow the user to view the layout plans for the area on which the
project is being developed.
The system should be able to view the land map and its information on which the project
is being developed
The system should allow the user to view the project scheme structural and service
details prepared by engineering
The system should allow the user to update the status of the project (during architecture
design phase).
The system should allow the user to link an outsourced agency (to whom the design has
been outsourced fully or partially) to a particular project
The system should allow the user to view the status of the project (including the
architectural drawings).
The system should maintain status of part/full disposal of projects in the Land Disposal
wing
The system should allow the user to drill down to a project from the layout plan.
The system should be able to integrate with a standard CAD package in order to link the
architectural design drawings with a particular project.
The system should have the facility to link the architectural drawings with the layout plans
The system should have the facility to import designs prepared by external agencies into
a project. The system should allow linking of the drawings with the basic drawings
prepared by the department for the project.
SRS
10

Process map of Architecture Department
PROJECT
Feasibility Study
Contextual Features
Survey / Measured Drawing
Preparation of Conceptual Design & Layout

Approval of HOD
Screening Committee Approval
DUAC Approval For Commercial
& Multi-Story Projects
DUHF Approval For All

Heritage Projects
Issue of Drawings for Service & Site

Development
Incorporating Service Details
Issue to Engg. Department for Execution
Preparation of detailed working Drawings
Arch. Controls conditions
2n
d
St
ag
e
D
U
H
F
A
pp
ro
va
l
6.4
SMB Approval For all

Sports Activity Projects
Issue of Drawings for Structure Design
Incorporating Struct. Details Preparation of
Working Drawings
Issue to Engg. Department for Execution
Site Coordination
Issue of Control Drawings to Land
Department & Disposal
Revision as Site
Problem
Preparation of Development Plan
General action format for projects
SRS
11
7.
8.
Land Management
The Land Management department at DDA is headed by Commissioner (Land Management) and
executes activities related to the acquisition of land from the Central Government, protection of
the acquired land from encroachment and taking suitable actions in case of unauthorized
constructions.
The structure of the department is as below:
6. Land Management I: Headed by Director and performs activities related to
encroachment protection and demolition of unauthorized construction
7. Land Management Head Quarters: Headed by Director and performs activities related
to acquisition of land and dealing with Government of India departments for the same
8. Zonal Offices
Dy. Directors for Zones of South East, North, Rohini, South West, East
Dy. Directors for Enforcement, Co-ordination, Nazul Lands I & II
As can be seen from the process map on the next page, the main interactions of the department
are with Planning department within DDA and with the Government of Indias Land and Building
department. The Planning department hands over the approved proposals and layout plans to the
Land Management department for acquisition of land. On these proposals and plans then, the
Sajra maps, showing the original Khasra numbers of each unit piece of land, are superimposed.
On the basis of this, a list is prepared of the Villages and their respective Khasra Numbers, which
need to be acquired and processing for the same is initiated.
After acquisition, the land management department transfers the land to the user department
within DDA for development purposes, which is usually the Engineering Wing.
SRS
12
SRS
13
At present the Land Management department has a Land Management Information system,
which is a GIS and Oracle 8i based application with the following broad level functionality:
8.1
Existing application functionality

i.
ii.
iii.
iv.
Details
Digitized maps
Clearly showing lines and demarcations of khasra no.s / plots
Notification: Display of notifications related to the different stages of acquisition

Award: Details of award of compensation
Comparison:
v.
Intelligent maps wherein users can build and run queries, like area under a
particular stage of acquisition

About: Information on the land management system
The Land Management Information System will have to be enhanced or suitably recoded /
modified as per requirements specified in this section and will have to be integrated with the
Integrated Management System
SYSTEM REQUIREMENTS
8.2
Receive proposal and conduct preliminary survey

i.
ii.
iii.
iv.
v.
vi.
vii.
The system should have the facility to receive data pertaining to proposals for
development like objective, current land use, future land use, benefits, etc. prepared by
the Planning department
The system should be able to display information as per the development / layout plans
made in the Master Plan
The system should provide the facility to overlay other maps (like Khasra maps) on the
Master Plan layouts
The system should have facility to capture information received through preliminary
surveys
The system should have the facility to capture field information for surveys entered by the
users though GPS technology
The system should allow categorizing of physical survey information as per requirements
of DDA
The system should maintain physical survey observations area wise
SRS
14
8.3
Approval and maintenance of records

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
8.4
The system should maintain status of approval of each proposal

The system should generate automatic reminders on approvals, which are due with a
reason for a delay in receipt of approvals
The system should be able to capture comments in the case of approvals not being
granted to certain proposals
The system should maintain a history of unapproved proposals with comments and
reasons for the same
The system should generate custom reports to monitor the details of each proposal along
with relevant fields like date of approval, approving authority, proposed date of land
acquisition, proposed date of works completion, etc.
The system should maintain audit trail of exchanges of information with Land and
Building department
The system should allow maintaining a list of villages and khasra numbers, area of each
coming under the proposed development / layout plan
The system should allow users to attach / link textual information to graphical maps
Land Acquisition information and progress

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
The system should capture information related to land surveys

- Actual area
- Name of personnel performing the survey
- Any other relevant information
The system should maintain records of draft notifications issued for approval
The system should maintain standard formats for issue of notifications
System should capture the status of issue of notifications
System should display maps of land areas with the corresponding status of issue of
notifications for that area
The system should maintain status of approval for each notification
The system should capture unapproved notifications with reasons for the same
The system should allow web based receipt of objections from general public to
notifications issued
The system should maintain detailed records of compensation to be paid
The system should maintain records of unresolved compensation cases along with
reasons for the same
The system should allow categorization of unresolved compensation cases
The system should be able to display maps of areas with the categories of unresolved
cases in each, in different color codes
The system should be able to provide Layout wise and if required Khasra wise status of
acquisition with color codes
SRS
15

8.5
Compensation
i.
ii.
iii.
iv.
8.6
Web-based functionality
i.
ii.
iii.
iv.
v.
vi.
8.7
The system should be able to capture the compensation paid by DDA against each land
area / plot under relevant heads as defined by DDA
The system should allow access to finance department to the compensation paid
The system should have the facility to capture details of acquired area, notifications
issued, perceived roadblocks, legal cases if any etc. during handover of land to DDA
The system should maintain records of transfer of land by Land Management to user
departments
The system should allow web-based access to acquired and non-acquired land
The system should display information on the web for area under DDA for development
purposes
The system should capture information on compensation paid to land owners and display
it on the web
The system should maintain, if required, information on future land acquisition plans
The system should allow display of gazette notifications on the web
The system should allow web-based receipt of objections to notifications issued
Miscellaneous
i.
ii.
iii.
iv.
v.
The system should be able to provide a layout wise and if required khasra wise
regularization status with color codes
The system should display layout wise and if required khasra wise cluster view
The system should be able to capture city survey number, khasra number and sheet
number
The system should be able to generate custom reports based on user defined criteria
SRS
16
9.
Engineering Wing
Engineering Wing is headed by the Engineer Member and has the following structure:
1. Zone Level:
Chief Engineers for each Zones: Rohini, Dwarka, South West, South East, North and
East Zones
Chief Engineers of Electricity, Design and Quality Control
Director (Material Management) and Project Manager (Flyover)
2. Circle Level:
Each Zone is further divided into Circles with a Superintending Engineer in-charge of the
circles. There are around 20 Circles (15 Civil, 3 Electrical, 2 Flyover) and 45
Superintending Engineers, out of which 20 are field engineers.
3. Divisions:
There are around 80 field divisions and 140 Executive Engineers.
The Land, which has been acquired by the Land Management department and is under the
possession of DDA, is handed over to the Engineering Wing for development purposes. The
Engineering conducts physical surveys of the land covered in the plans to identify actual
conditions on the ground like mounds, pits, High Tension lines, etc. and prepares a feasibility
report.
The main activities of the Engineering Wing can be divided into the following categories:
1. Pre-Construction activities: Staring from physical survey of land and fencing to
preparation of Detailed Estimates and Notice Inviting Tender
2. Tender related activities: Preparation of notice Inviting Tender, Evaluation and Award of
Contract
3. Works in Progress activities: Project Execution and Monitoring
4. Post Construction Activities: From calculation of actual costs incurred in the works to
handing over property to the allotee
SRS
17
Planning
Prepare Zonal
Development Plans or
Scheme wise plans and
send to LM for
acquisition
Land
Management
<Engineering Wing>
Hand over to user

department if
already acquired
else start
acquisition
process
Planning to
incorporate the
changes as per
engineers
observations
Engineering
Finance
Observations are whether

there is any natural
obstruction or Hight Tension
Lline or built up area or
encroachment (checked by
LM but Engg does again as
sometimes big time lag
between activities)
Steering Committee
approves the
development or specific
project plan
Mark observations
on the
development plan
and send it back to
Planning
Receive land
acquired from LM
department
Divide work
according to
Circles and then
Divisions, etc.
Architecture
drawing is
prepared
Perform physical survey of

land, physically demarcate
boundaries
Sent to Finance
Wing for
concurrence and
Engineer Member
for admin.
approval
Feasibility report
and preliminary
estimate is
prepared
Approval from
DUAC
Prepare detailed
cost estimates
Receive Technical
Sanction
Prepare Notice
Inviting Tender,
Tender
Evaluation by
Works Advisory
Boarad for > Rs 5
Cr.
Project
Execution
and
Monitoring
Match khasra no.s shown in

planning map with actual on the
ground.
Superimposes Sajra maps on
Planning maps (except for
Nazul A/C II)
Decide on compensation
SRS
EAC accords Admin

Approval and Expenditure
Sanction
18
The Engineering wing currently uses STAAD package in a limited way for structural designing.
The current applications will have to be integrated with Integrated Management System. Usage of
the STAAD application is to be increased through proper training.
SYSTEM REQUIREMENTS
9.1
Receive Conceptual / Development Plans from Planning Deptt.

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
9.2
System should allow access to the proposal details prepared by the planning department
on the basis of which the project has been decided to be executed
System should allow access to development plans / layout plans made by Planning
department
The system should allow marking of observations made by the Engineering Wing during
physical survey of the Land on the development / layout plans
The system should allow Engineering Wing to send the development / layout plan to
Planning along with the physical observations
The system should maintain an audit trail of comments made by Engineering users
The system should enable the observations on the development plan to be viewed by the
Planning
The system should maintain records of exchanges of layout / development plans made
between Engineering Wing and Planning department in terms of dates on which sent,
changes made, etc.
The system should be able to trace the status of approval of the plans at each stage The
system should allow linking of plans wherein a plan may be defined as the parent plan
having multiple plans linked to it
System should allow access to development plans, maps made by Planning department
in the past
Receive details of Land Acquired

i.
ii.
iii.
iv.
The system should have the facility to capture information related to observations made
during the physical survey of land performed during acquisition by Land Management
department
System should capture information like maps, area and location of land handed over to
Engineering Wing in each phase by Land Management department for development
purposes
System should allow select users to view information related to the status of Land
Acquisition under progress on the basis of land acquired, total land in proposal, issues
related to pending acquisitions, etc.
System should be able to capture textual information on the reasons of extensions in
Land Acquisition dates like legal proceedings, likely dates of acquisition, etc.
SRS
19

v.
vi.
vii.
viii.
System should allow need based access to this information on reasons for extensions
The system should have the facility to capture status of Fencing of Land
The system should maintain records of date of handover, officer in-charge from Land
Management department, officer to whom handed over, etc. each time the land acquired
is handed over to the Engineering Wing for development purposes
System should enable Chief Engineer (Zones) to maintain Soil Investigation reports of
the Land acquired
9.3
Activities of CRB Cell

i.
System should maintain status of firm registration, renewal, pending action, etc. as per
details of registers
ii.
System should be able to maintain progress of cases in pipe lines
iii.
System should digitize the diary / movement register
iv.
System should be able to maintain a list of correspondences received
v.
System should be able to maintain list of policies / decisions taken in past
vi.
System should be able to maintain the details of suspended, blacklisted, debarred
contractors
9.4
Monitoring of Pre-construction Stage

i.
System should have the facility to maintain the status of approvals from Chief Fire Officer
ii.
System should have the facility to maintain the status of approvals from Delhi Urban Arts
Commission
iii.
The system should have the facility to maintain the soil investigation report
iv.
System should allow maintenance of agenda items for
a. Water supply
b. Structural arrangements
c. Sanitary services
d. Electrical services
v.
The system should allow CDO to upload the structural details in the specified format
9.5
Prepare Feasibility Reports for detailed plans

i.
The system should be able to maintain maps of the following scales at a minimum and
more depending on the requirements and as defined by the appropriate authority
ii.
iii.
iv.
v.
1:500
1:1000
User defined Scale
The system should be able to capture foundation system reports on the basis of
recommendations in the Soil Investigation report
The system should allow capturing and tracking of requirements for External Consultants
for technical help on preparation of Foundation Systems
The system should generate automatic reminders on approval of Layout plans
The system should have the facility to allow access to the concerned personnel in the
Engineering Wing to access the Layout Plans as and when they get approved
SRS
20

vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
The system should be able to overlay the circle, division distribution on the land to be
developed
The system should allow division of work circle wise and division wise based on decision
made by the Chief Engineer of the concerned Zone
The system should be able to maintain standardized formats of feasibility reports System
should allow preparation of multiple versions of feasibility reports keeping records of
changes made in each version
System should allow marking of observations on the Layout plan
The system should be able to allow users to enter history information for each Layout
Plan based on standard formats
System should capture date of dispatch of layout plan with comments and history sheet
to Planning department
The system should allow access to the altered layout plans made by planning.
The system should maintain a final version of layout plan after all changes have been
incorporated, which is totally locked from editing.
System should maintain the policies and building bye laws like FAR, coverage, etc. as
fixed by DDA from time to time
The system should allow plans to be maintained under separate categories like:
Phase Plan
Sector Plan
Specific Projects like shopping complex
User defined categories
9.6Preliminary Estimates, Administrative Approval & Expenditure Sanction

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
The system should maintain a database of architectural drawings, detailed structural

drawings and related data
The system should allow preparation of preliminary cost estimates by the engineers
based on area use and plinth area rates for each type of land use
The system should maintain a pre-defined list of Plinth Area Rates and Cost Indices as
defined by DDA from time to time
The system should allow simple mathematical calculations and formulas to arrive at the
cost estimates
The system should allow workflow review and approval of preliminary estimates across
more than one location
The system should maintain a checklist of tasks to be done during preparation of
Preliminary Estimates
The system should allow work packages to be exchanged between different locations
and officers during the review process with the packages having both spatial and nonspatial data
The system should have the facility to capture the comments made by reviewers under
each category or specific section of the work package like observations on cost index,
assumptions on area calculations, etc.
Chosen Cost Index
SRS
21
ix.
Assumptions on area calculations
Assumptions in total cost calculations
The system should maintain the following indicative documents in the Work Packages
related to Preliminary Estimate for each project
Conceptual Plan (showing map and location for which estimate is being
prepared)
Salient Features of the project like Title; Location; Owner; Architect; Current Land
Use; Plot 3.4.10 Area; Regulations of area, height, FAR, Proposed area, green,
etc.
Details of the scope of work of the Project along with a brief history
A sample format for Administrative Approval and Expenditure Sanction
Feasibility Report (availability of services, dimensions, structures, telephone

lines, HT lines, 3.4.11 Setback with respect to boundaries, North point,
Encroachment details, etc.
Agenda for structural arrangements, water supply, sanitary services, electrical

services, etc. should be maintained for approval
References to approvals of Screening Committee and Delhi Urban Arts

Commission and Chief Fire Officer, if applicable
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
Layout Plans
Any other documents related to preliminary estimate calculation
The system should maintain a schedule of material quantities required for the project
The system should automatically calculate the final amounts for each quantity based on
Plinth Area Rates and the Cost Indexes as defined and approved for the project
The system should capture schedule of quantities for works not included in the Plinth
Area Rates as a separate from the requirement mentioned in point above
The system should maintain development costs per sq. m. as defined by DDA from time
to time
The system should allow maintenance of an abstract of all costs
System should have the facility to drill down from the abstract of costs to the schedule of
quantities
The system should maintain standard formulas used for area calculations
The system should allow workflow based approval of the Work Packages
The system should maintain approval details and status of each project from Screening
Committee and Delhi Urban Arts Commission and Chief Fire Officer, if applicable
The system should maintain a database of Administrative Approvals and Expenditure
Sanction for reference
9.7Prepare detailed estimates and technical sanction

i.
ii.
iii.
The system should allow preparation of a detailed cost estimate

The system should have the facility to compute quarter wise quantity of stipulated
materials to be issued to contractor
The system should maintain approval hierarchy for technical sanction as per DDA norms
SRS
22

iv.
v.
vi.
vii.
viii.
The system should allow workflow based Technical sanctions based on project value
The system should maintain standard formats for Notice Inviting Tenders, Bid
Comparisons, etc.
The system should capture information for comparison of bids received from various
vendors according to pre-defined formats
The system should allow access to Finance for scrutiny of the comparatives of tenders
System should capture the status of award of work
9.8Floating of Tender
i.
ii.
iii.
The system should provide the functionality of e-tendering and/or e-procurement

The system should be able to seamlessly integrate with third party e-tendering and/or eprocurement engines
The system should be able to generate reports as required from the third party etendering and/or e-procurement engine
9.9Works Execution and Monitoring

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
The system should have the facility to capture the project plans and proposals submitted
by the prospective contractors, if required
The system should be able to capture the details of material (other than stipulated for
issue) required for completion of work
The system should be able to capture the details of labor (other than stipulated for issue)
required for completion of work
The system should be able to capture the services plan with the status of each
The system should monitor progress in specified reporting formats
Works in preconstruction stage
Works in progress
The system should support user defined reporting formats as per DDA requirements
The system should send automatic communication to the Housing / Land Disposal on
completion of Project
The system should be able to display the areas on which development works are being
carried out or have been completed
System should have the facility to maintain financial records such as validity of securities,
Earnest Money Deposits, etc. for contractors / agencies
The system should be able to display the areas on which works have not been completed
within the contract period
The system should be able to display development agency and users for plots in the
layout with color codes
The system should have the provision to capture the change of users for a given land
area and maintain the history of change of users
The system should have a provision to maintain Inventory / Utilization of Lands
The system should have a provision to print the layout plan of an area with index and in
the required format
SRS
23

xv.
xvi.
xvii.
The system should be able to generate the total quantum of work done after completion
such as
Length of road
Length of water pipeline laid, etc.
xxii.
xxiii.
The system should allow preparation of actual works expenditure at the end of the work
System should capture the information on work types in hand under each zone, circle
and division
System should have the facility to display location wise work types in hand
The system should have the facility to display prevalent market rates of various building
materials
System should be able to maintain quality control elements
System should be able to maintain records of instructions issued by EM, CE(QC), CTE
and any other authority as specified
System should have the facility to display Engineers incharge of various works / pockets
System should be able to maintain details of commercial property
9.10
Works Budgeting and Finance related functionality
xviii.
xix.
xx.
xxi.
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
The system should allow budgeting activity to be carried out on an annual basis with a
mid-year review
The system should allow maintenance of scheme wise budget under expenditure and
receipt heads
The system should aggregate budget received from divisions into Circle wise
The system should automatically generate reminders and allow select users at
Headquarters to access Zone wise estimates
The system should allow engineering department to access approval details and status of
budget for each work / scheme
System should allow a mid year review of budget and preparation of a revised estimates
The system should allow re-appropriation of budget based on revised requirements
The system should allow scrutiny of justification of financials / comparative statements,
prepared after opening of tenders submitted by contractors for each scheme
The system should allow access to tender rates for similar works executed in other zones
by DDA
The system should support workflow based approvals of budgets by Head Office
The system should allow recommendations for changes from Head Office to be cascaded
down to zones, circles and divisions
The system should be able to calculate the revenue that has been generated from a
layout
The system should allow aggregation of details of court cases from divisions, circles into
zones
The system should allow sharing of these details with the head office
The system should maintain a list of division wise pending cases, contempt cases and
cases where some action is pending from DDA side
SRS
24

xvi.
xvii.
9.11
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
xx.
xxi.
The system should maintain list of audit paragraphs with comments from external
auditors and status of responses to these comments made by divisions
The system should allow the user to monitor the expenditure against budget allocation for
individual budget schemes
Project Accounting
The system should allow complete monitoring of works costing above Rs. 10 Lakhs up to
finalizing of bill
The system should maintain records of bills approved and paid to contractors
The system should allow preparation of actual and estimated project expenditure for each
scheme / work
The system should allow recording of information on expenditure incurred on
maintenance of colonies
The system should maintain records of handing over of services to Civic agencies
The system should capture the expenditure on salaries of employees for each zone
The system should maintain records of General Provident Fund accounts of all
employees for each zone
The system should automatically calculate the Income Tax liabilities for employees and
include it in the salary calculations
The system should maintain a monthly account of all expenditures incurred within a zone
The system should generate settlement of bills, having the following types:
First and Final settlement (for works, which require one time payment)
Running account bill (for on-going works)
Final bill (final settlement for on-going works)
The system should maintain audit trail of bill approvals granted and the approval authority
for each
The system should allow aggregation of bills paid under a particular work / scheme at any
point in time to arrive at the total cost incurred in that work / scheme
The system should automatically make deductions like Sales Tax from payment being
made to contractors
The system should maintain details of material bills
The system should maintain records of approvals granted to the material bills
The system should generate a list of pending bills with reason for the same
The system should be able to capture the expenditure incurred on each work / scheme
The system should be able to display the progress of works layout plan wise with different
color codes
The system should have the facility to maintain annual theft and losses as per user
defined formats
The system shall maintain the GIS/details of all underground services with complete
particulars of levels, sizes, etc.
Working of justification of rates on the basis of Delhi Analysis of Rates (DAR) of CPWD &
current rates approved in DDA.
SRS
25

xxii.
Working of Estimate cost on the basis of DAR of CPWD & DSR revised from time to
time, not earlier (than One Year).
9.12
Arbitration, Encroachment Monitoring and Demolition Plans
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
9.13
i.
ii.
iii.
iv.
v.
vi.
9.14
The system should monitor court cases relating to arbitration matters, matters of
administration and other issues not directly related to project
The system should support monitoring and disposal of observations of Quality Control
cases
The system should maintain records of replies to Audit Paras of the Internal / External
audit of works in Zones
The system should be able to maintain records of receipt / disposal of Public Grievances
references
The system should capture reports, photographs received from engineers, patwaris, etc.
on land encroachment, misuse of properties, unauthorized construction, etc.
The system should capture the standard formats for preparation of demolition plan
The system should allow automatic communication to concerned officers on receipt of an
encroachment report
The system should maintain standard formats for preparing request letters as preparation
for the demolition plan
The system should maintain a list of third party contractors and the standard equipment
required for the demolition
The system should capture information on status of legal proceedings, main points of
contention, etc. on cases made by owners / encroachers in response to eviction /
demolition orders circulated by DDA
Web based access
The system should allow display of Notice Inviting tenders on the internet
The system should allow prospective vendors to download forms through the internet
The system should display results of award of work on the internet if required
The system should allow web based access to all current schemes / works being carried
out under each division
The system should allow web based access to relevant details of each of the schemes /
works being carried out
All users in DDA should be able to use the system over intranet without the need to have
client software loaded on their machines
SRS
26
10. Land Disposal

The Land disposal department at DDA is headed by a Commissioner (Land Disposal) and
performs activities related to allotment of land and post allotment activities. It receives information
from the engineering wing on availability of land for allotment, both on completion of development
activity and as and when any vacant property comes to their notice.
The structure of the department is as follows:
1. Residential Headed by Director and looks after residential properties
2. Commercial Headed by Director and looks after commercial properties
3. Institutional Headed by Director and looks after Institutional, Industrial and Old Scheme
Branch (Karol Bagh, other old Delhi areas) properties
The Land disposal department based on the information received from the engineering wing from
time to time, acts accordingly to ensure allotment of property as per policy. The department also
performs post allotment activities related to issuance of possession letters and execution of the
lease deed and conveyance deed. Another major responsibility of the department includes works
related to mutation of the property.
The main transactions of the department are related to residential lands, wherein both the
availability of accurate information on plots for allotment and the reduction in cycle time for
possession letter issuance, leasehold to freehold conversion, etc. are paramount. Thus the Land
disposal department is a customer facing department, dealing directly with the public at large for
activities like receipt of applications, resolution of issues, allotment to Co-operative Group
Housing Societies, alternate allotment as compensation, mutation cases and this point has to
born in mind at the time of proposal formulation.
As has been depicted in the process map on the next page, the Land Disposal department
interacts mainly with the Engineering Wing on one side and with the Finance Department on the
other. The interactions with Finance department are mainly related to verification of payment,
calculation of ground rents, composition fee, conversion charges, subletting charges, etc.
SRS
27
SRS
28
SRS
29
EXISTING APPLICATION
10.1
At present the Land Disposal department has a stand-alone application called Bhoomi, which is
a Visual Basic and Oracle 8i based application having the following broad functionality:
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
Allotment, with following steps
Attach program
Attach Scheme
Attach property
After doing the above three, get a Program No.
Define draw parameters
Perform draw
Program Completion
Allotment Rohini
Lease
Lease / Conveyance deed form
Auto capture of data to fill up form
This module is used to a lesser extent
Registration
Cash Management
Demand
File data loading (to import files)
Property
License
Master
Online
Post allotment
Security
The Allotment module of the Bhoomi application has been brought into use and the application
will have to be enhanced or suitably recoded / modified as per requirements specified in this
section and will have to be integrated with the Integrated Management System
SYSTEM REQUIREMENTS
10.2
i.
Integration with other departments

System should ensure receipt of information from engineering wing on availability of plots
and shops for disposal for commercial lands, residential lands and commercial estate
branch
SRS
30

ii.
iii.
iv.
v.
vi.
vii.
viii.
10.3
No encroachment clearance
Results of physical surveys performed
Details of disputed land areas
System should ensure receipt of information from engineering wing on availability of

shops and plots for disposal
System should allow access to calculation of ground rents, misuse charges, etc. made by
Finance department
System should allow access to progress status of calculation of charges made by
Finance department
Standard Cost prepared by Land Costing should be available on the system
Float Scheme for residential, commercial and/or institutional allotment

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
10.4
System should allow access to reports on encroachments/unauthorized construction

made by Engineering Wing or Land Management department from time to time
System should allow access to reports on misuse of properties received from Land
Management department (Enforcement Branch).
System should maintain records and status of clearances received from the Land
Management department for upcoming notifications:
System should maintain standard formats for Scheme Notifications with details like
Scheme Name, Date of Inception, Date of Allotment, Date of closure etc
Provide for associating a plot/commercial property with a particular scheme. Ensure that
a particular plot/commercial property is associated only with one scheme at a time
Provide for reservation of a plot/commercial property for a particular category of
applicants as per government rules for allotment
Provide for associating a priority number for each plot/commercial property in the scheme
based on list of waiting registrants, reservation of the plot/commercial property, etc
System should ensure that records of scheme notifications are maintained
System should be able to maintain list of banks associated with the scheme along with
bank details
System should be able to maintain details of brochures issued for a particular scheme
including brochure cost
System should be able to maintain details of number of brochures issued to various sales
counters/banks for a particular scheme
Receive Application form and Registration Money from Banks

i.
ii.
iii.
iv.
v.
vi.
Maintain standard formats of application forms for housing schemes

Provide for importing soft copy of applicant data received from banks
Maintain check list and status of documents submitted by applicants
Maintain list of documents to be supplied by allottee for issue of possession letter
Generate letter of deficiencies on the basis of check list of documents submitted by
alottee
Provide for verification and correction of applicant data (with physical application forms)
SRS
31

vii.
viii.
10.5
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
10.6
i.
ii.
iii.
iv.
v.
vi.
x.
10.7
Maintain applicant details for each scheme such as Applicant Name, Application Form
No., Scheme Name, Address etc
Maintain details of registration money received applicant wise/bank wise/scheme wise
Allotment of Land/Shops by auction, tender, computerized draw, reserved price
System should have the policy of auctions, allotments, etc. available for access on the
computer to internal users of DDA
System should ensure receipt of information from engineering wing on availability of plots
for disposal
System should generate notifications for inviting applications according to pre-decided
eligibility norms normally and through the website
System should have the facility for automated check printing
System should allow tender/auction of plots and shops based on random location as and
when information is received from Engineering Wing
The system should generate reports of plot wise/applicant wise allotments
The system should maintain details of plots/commercial allotted against each successful
applicant
The system should maintain list of un-allotted plots/commercial properties scheme wise.
These should be available for disposal under a different scheme and method of disposal
The system should allow for generation of a soft copy of successful/unsuccessful
applicant details for hand over to banks
Allotment of Land as compensation to Rohini Registrants and GH Societies

System should allow for registration for allotment under the alternate allotment scheme
System should allow for allotment of land as allotment recommendation from L&B
department and database of all Group Housing Societies registered in Delhi and all
Rohini registrants based on approvals by appropriate authority
System should allow receipt of information from Planning & Engineering department on
availability of plots for alternate allotment under Rohini schemes and Group Housing
Society categories
Perform allotment through computerized draw with priority based on the rules laid down
for the three schemes
System should allow of the alternate allotments only in new upcoming schemes
System should ensure further processing through the usual process
System should allow for payment of Ground rent in case of societies under:
a. By societies
b. By allottees
Allotment of shops under reserved categories and staff orders
SRS
32

i.
ii.
iii.
iv.
10.8
i.
ii.
iii.
iv.
10.9
v.
vi.
vii.
viii.
ix.
x.
xi.
10.10
System should be able to allow allotment of shops based on pre-defined rules as per
reservation policy made for special categories
System should maintain a list of special categories and the amount of reservation allowed
against each category
System should be able to update the reservation policy from time to time
System should maintain the status of allotment made under registration with details of
numbers allotted against numbers available
Monitoring and Disposal of Petrol pumps, gas godowns, CNG station sites
System should be able to maintain records of petrol pumps disposed with names of party
currently operating the petrol pump, date of disposal, demand, etc.
System should be able to maintain records of disposal of CNG station sites and gas
godowns with details of current agency handling the operations, date of disposal, etc.
System should be able to maintain records and details of field visits to ascertain the
actual operation in the disposed land
System should be able to maintain the records of future sites shortlisted for usage as
petrol pumps, gas godowns and/or CNG stations.
Monitoring and Disposal of commercial built up properties and licensed units

System should be able to maintain records of disposal of commercial built up properties
like shops, restaurants, offices, etc.
System should be able to segregate records of commercial built up properties on the
basis of types of usage
System should be able to maintain records of Parking contracts, taxi stand sites and
licensed units in market complexes
System should be able to generate reports on license fee due, received and date of
payment, for licensed units and properties
System should be able to maintain records of agencies handling the operations of
licensed units with details of manager in-charge of the location, his contact numbers, etc.
System should be able to maintain records through user-defined parameters
System should be able to capture relevant details of an entire market area, including
details of shop owners, past records of performance, any encroachments, etc.
Issue of demand letter

i.
ii.
iii.
System should generate demand letters to the successful allottee

System should maintain standard formats for Demand Letters, Possession Letters,
Conveyance Deed, etc.
System should have the facility to enter ground rent payment and lease execution in case
the allotment is made to societies
SRS
33

iv.
10.11
System should have the facility to categorize allotee into One time payees, Installment
Payees, etc.
Receive Payment Details from Banks

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
10.12
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
xx.
xxi.
xxii.
The system should have facility to import soft copy of payment details received from
banks
The system should be able to generate discrepancy report allottee wise against
payments received from banks
The system should allow for manual verification and correction of discrepancy cases with
proper safeguards
The system should track payments received allottee wise and generate exception reports
The system should have facility to generate notifications to appropriate users in case of
late payment or non payments
System should automatically update information for each allotee related to his past
submittals of installments and verification of payments
System should maintain complete history of payments made by allotee at all times
The system should have facility to generate defaulter list and generate e-mail/print
notifications to appropriate users
The system should have facility to generate reminder letters for defaulters.
The system should generate reports on payments received/balance allottee / agency
wise
The system should have provision for cancellation of allotment in case of default.
Payment, Possession Letter, Conversion to Freehold
System should allow entry of data related to receipt of payments according to conditions
in Demand Letter
System should generate alerts on any irregularities (installment missed, wrong amount
paid, etc.) for each allotee
System should ensure issue of possession letters on complete payments made by allotee
System should be able to generate information on missing payments, fines, etc. to be
imposed on the allotee
System should have facility to enter application details for execution of Conveyance deed
System should have the facility to enter application details for conversion from leasehold
to freehold and update the status of each conversion application with reference to
milestones
System should be able to capture the lease administration process for land disposal
System should be able to generate the outstanding dues of allotee
System should have the facility to verify whether the allotee has made all payments
System should allow the user to approve conversion only after receipt of all dues from the
applicant / allotee
System should have inbuilt checks and verifications to ensure all conditions related to
execution of deed have been met
SRS
34
10.13
Perform transfer of property and mutation related activities

i.
ii.
iii.
iv.
v.
vi.
10.14
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
10.15
System should incorporate the mutation process under different categories:
Change of ownership
Sale of Land
Death of the owner
Other categories
System should allow receipt of application for mutation

System should maintain standard formats for notifications, letters, etc. and be able to
print copies of the same
System should allow for maintaining the records of progress of legal proceedings
System should maintain the final record of mutation performed with details of:
Reason for mutation
Resulting Change
System should allow for performing construction related activities, like time extension,
conversion to free hold, etc.
Relocation/Redevelopment of Commercial Areas

System should be able to maintain records of rehabilitated markets / industries, old
location, current location, date of shifting, duration of shifting, agency, etc.
System should be able to capture complaints, grievances received from concerned
parties on the rehabilitation process
System should maintain records of court orders, committee orders passed in relation to
rehabilitation of industries, markets, etc.
System should have facility to enter rehabilitation plans
System should be able to capture details of execution against plan and reasons for delay
in execution if any
System should have facility to enter redevelopment plans and details
System should maintain records for monitoring of consultants appointed for drawing
redevelopment plans with relevant details of past performance, financial data, etc.
System should be able to generate reports on rehabilitations executed within a specific
period as defined by the user
Maintain records of Legal cases and Applications received from citizens

i.
ii.
iii.
iv.
System should maintain records of Legal cases with details of status, last update, subject
of case, relevant dates, etc.
System should be able to classify cases according to user defined subject matters for
easy reference to case decisions
System should be able to generate reports on current cases, cases disposed off, etc.
System should be able to maintain entire case history based on user defined parameters
SRS
35

v.
vi.
vii.
10.16
Web-based functionality
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
xviii.
xix.
xx.
xxi.
xxii.
xxiii.
10.17
System should be able to generate alerts /reminders on case meetings to appropriate

personnel responsible for attending the case hearing
System should be able to maintain records of applications received from citizens
System should be able to display the current status of each application, which officer is
handling the application, reasons for delay based on pre-defined deadlines for disposal
System should allow receipt of complaints from general public on misuse of residential
premises for other purposes
System should allow forwarding of these complaints to appropriate department / authority
within DDA for further action
System should maintain the policies related to auction, allotment of land available to the
general public for download through the Internet
System should display notifications for general public and allow download of notification
from the internet
System design should make adequate arrangements for integration with online auction
sites for auction of plots
System design should make adequate arrangement for integration with bank databases
for online updating of information related to deposit of money (challans) made by allotee
System should allow complete one to one matching with information available with the
Banks on money deposited by Allotee
System should allow creation of new schemes as per requirements of Land Disposal
department
System should maintain the updated records of applicants for all schemes
System should ensure that any changes made in the applicants data are informed
automatically to appropriate authority
System should ensure that periodic alerts are generated to appropriate authority for
maintenance of data
System should allow generation of new schemes as defined by DDA from time to time
System should ensure that a list of applicants is maintained for transfer of unsuccessful
applicant names to upcoming schemes
System should allow generation of alert and automatic cancellation of applicant name
from list on allotment
System should provide appropriate authority with the facility to delete applicant names
from the list
System should maintain audit trail on any changes made in the applicants database
SRS
36

10.18
11. Housing
The Housing department is headed by Commissioner (Housing). The main activity of housing
department is to dispose and provide associated services for houses/flats constructed by DDA.
The Housing department floats schemes for allotment of houses/flats. Other main activities of the
department include enforcement of housing regulations (prevention of unauthorized construction,
misuse of houses etc), conversion of flats from leasehold to freehold and providing housing
related services such as mutation, change of address etc.
The Housing department is divided into the following sections:
Housing Schemes Sections: There are separate sections for each scheme category. These
sections are MIG, LIG, Janta, SFS and EHS. Each section handles the entire scheme
management for the schemes floated by the concerned section.
Lease Administration Branch: This section is responsible for processing applications received for
conversion of leasehold flats to freehold. This section also handles services such as transfer of
property, mutation and inclusion of name.
Housing Finance: This section is responsible for handling all finance related activities of housing
department. These activities include calculation of demand and EMIs, verification of payments
received and calculation of outstanding dues.
Housing Enforcement: The main activity of this section is to ensure that housing regulations are
followed by allottees. The section enforces these regularizations and takes punitive action against
defaulters.
The business process maps for housing are given in the following pages. Four processes have
been defined for the department. These are:
1.
2.
3.
4.
Housing Scheme Management

Lease Administration
Housing Enforcement
Housing Services.
From the process maps it can be observed that the main interaction of housing is with
Engineering department (for obtaining housing project status and possession status) and external
entities such as customers (for all housing scheme and services) and banks (for application
processing and payments) .
SRS
37
Receive
details of
constructed
flats from
Engg
Housing
Finance
Banks
Customer
Housing Mgmnt
Section
Receive
Applications and
Registration
Money
Float a Housing
Scheme
Verify Applications
and enter into
System
Prepare list
of alottees
and
unsuccesful
applicants
Conduct
Computerized
Draw
Purchase Scheme
Brochure
Issue Demand
Letters to allottees
Receive Refund of
Registration
Money
Receive
Application form
and Registration
money
Consolidate All
applications and
payments
Receive
allottee/refund
applicant list
and refund
cheque
Prepare
Consolidated
cheque for refund
amount bank wise
SRS
Prepare Costing of
flats (Land
Premium plus
Housing Cost)
Calculate Demand
and installments(in
case of Hire
Purchase)
38
Customer
Housing Mgmnt
Section
Scrutinise the
supporting
documents
Execute
Conveyance Deed
and hand original
CD to alottee
Prepare Posession
Letter
Docs OK
NO
Receive Demand
Letter from DDA
Apply for Posession

letter after making all
payments (along with
necessary documents
and copy of bank
challan)
Receive letter from

DDA asking for
Documents
Receive Payment
Demand letter
from DDA
Receive Posesion
Letter
Take posession of
flat and intimate
DDA
Yes
Receive Full
Payment for Cash
Down purchases,
First Installment
for HP cases from
Customer
No
Receive Payment
Details and
Challan from
Banks
Verify Challan
Payments made
All Payments
made?
Engineering
Housing
Finance
Banks
Yes
Receive Copy of
Posession Letter
SRS
Hand over
Posession and
inform Housing
39
Lease
Administration
Branch
Housing Lease Administration
Receive
application from
bank
Retreive original
file from
concerned section
Receive
outstanding
dues details
from HF
Dues < 5000
Yes
Approve
Application
1 Copy of CD
retained in Original
File
Receive letter on
outstanding dues
Receive
Application for
conversion to free
hold
Receive approval
letter and CD
Pay Stamp Duty
Receive payment
from customer
Receive original
file and application
from LAB
Check
Outstanding dues
if any
Receive payment
details from Bank
Sub Registrar
Housing
Finance
Banks
Customer
No
Register the CD in
favour of applicant
SRS
40
Housing Enforcement
Receive
complaints on
violations from
public
House Owner
Engineering
Housing
Enforcement
Inform MCD of violation
Notified area of
DDA
Yes
Inform concerned
JE to check the
violation
Issue Show cause

notice under Sec
30/31
Receive reply to
show cause/
application for
regularisation
Violation report
checked by JE
Approve
Regularisation
No
Initiate action for

demolition/Inform
LAB for
cancellation of
lease
Yes
Apply for
regularisation as
per DDA
procedure
Receive Show
cause notice
SRS
41
Aplply to DDA for

a service
(mutation, change
of address etc)
Receive
application form
from Applicant
Housing
DDA Counter
Applicant
Housing Services
Receive letter
regarding
incomplete
documentation
Enter applicant
details in system,
issue
acknowledgement
letter
Receive
application form
and supporting
documents
Receive approval
letter
No
Verify the
documents
Docs OK?
SRS
Yes
Approve
application, update
file
42
At present the Housing department has a Housing Management Information system also known
as AWAAS, which is a Developer 2000 and Oracle 8i based application with the following broad
level functionality:
11.1

1. AWAAS has the following modules:
a. Registration
b. Master Maintenance
c. Payment Maintenance
d. Post Allotment Activities
e. Draw of Lots
f. Demand letter module
g. Compactor module
h. Query module
2. The following activities are handled by Registration module of AWAAS:
a. Data Entry of application received from applicants for allotment
b. Maintenance of application form (addition/deletion of fields, etc)
c. Entry of Amount deposited by applicant
d. Printing of Checklist of application forms for verification and correction of
application forms
3. Payment Maintenance module handles the following activities of Housing Finance:
a. Entry of challans received from banks by Cash section
b. Accounting of the payments received (challans). There is no allottee wise
accounting.
c. Verification of the challans by concerned sections
d. An option for costing of flats is available in this module which is not being used
by Housing Finance
e. 18 reports are available in this module such as Discrepancy report, scheme
wise report, bank wise report etc.
4. The Master maintenance module is used for maintaining all masters of AWAAS. There
are about 400 masters in AWAAS.
5. Draw of lots module of AWAAS is used for allotment of houses through a Lucky Draw
process. The procedure followed for draw of lots is given below:
a. The system appends an 8 digit random number to each flat being allotted.
b. The flats are sorted and reshuffled.
c. A Cross-Reference table of flats is generated. A random serial number is
assigned to each flat. The table is printed. (These flats are also flagged in the
database)
d. The same procedure is followed for applicants and a cross-reference table of
applicants is generated and printed. The preferences of the applicants are also
mentioned against each applicant in the cross-reference table.
SRS
43

e. A lucky number for both flats and applicants is manually drawn and entered in
the system.
f. The Draw program is run and the system allots the flats to applicants. The
allottee trail and the final allotment list is printed.
6. Post Allotment Activities module of AWAAS handles the following activities of housing:
a. Cancellation of allotment
b. Addition/Deletion of names (in case of joint holding etc)
c. Change of mode of payment from Hire Purchase to Cash Down
d. Mutation
e. Updation of refund of money (not used for accounting purpose)
f. Conveyance Deed (CD) execution (not being used currently)
g. CD Execution module for monitoring stage of execution.
h. Printing of CD (not being used currently)
i. Issue of possession letter (not being used)
7. The Query module of AWAAS is used to search using pre-defined queries.
The application will have to be enhanced or suitably recoded / modified as per requirements
specified in this section and will have to be integrated with the Integrated Management System
SYSTEM REQUIREMENTS
11.2
11.3
11.4
Receive details of flats available from Engineering

i.
ii.
iii.
iv.
v.
11.5
The system should maintain complete list of flats which are available/under construction
The system should maintain all details of a flat like zone, address, flat category etc
Interface with engineering module to obtain status of a flat and relevant details
The system should enable the user to estimate the likely available date of a flat (date of
completion of construction of the flat)
Float a Housing Scheme

xi.
xii.
xiii.
xiv.
Scheme Name, Date of inception, Date of Draw, Date of closure etc

Provide for associating a flat with a particular scheme. Ensure that a flat is associated
only with one scheme at a time
Provide for reservation of a flat for a particular category of applicants eg ground floor flats
for physically challenged applicants
Provide for associating a priority number for each flat in the scheme based on list of
waiting registrants, reservation of the flat etc
SRS
44

xv.
xvi.
xvii.
11.6
Receive Application form and Registration Money from Banks

ix.
x.
xi.
xii.
xiii.
11.7
xxi.
xxii.
xxiii.
xxiv.
xxv.
The system should allow conducting of computerized random draw for allotments
The system should allow pre-defined criteria for the draw
The system should allow sorting and random shuffling of flats and applicants and
generation of cross-reference tables prior to conduction of the draw
The system should allow for use of lucky number as the starting number for the draw.
The system should generate reports of flat wise/applicant wise allotments
The system should maintain details of flats allotted against each successful allotee
The system should maintain list of un-allotted flats scheme wise. These should be
available for allotment under a different scheme
The system should allow for generation of a soft copy of successful/unsuccessful
applicant details for hand over to banks
Prepare Consolidated Refund Cheques Bank wise

i.
ii.
iii.
iv.
11.9
Maintain standard formats of application forms for housing schemes

Provide for importing soft copy of applicant data received from banks
Provide for verification and correction of applicant data (with physical application forms)
Maintain applicant details for each scheme such as Applicant Name, Application Form
No., Scheme Name, Address etc
Maintain details of registration money received applicant wise/bank wise/scheme wise
Conduct Computerized Draw

xviii.
xix.
xx.
11.8
Maintain list of banks associated with the scheme along with bank details
Maintain details of brochures issued for a particular scheme including brochure cost
Maintain details of number of brochures issued to various sales counters/banks for a
particular scheme
The system should automatically calculate the refund amount for each scheme bank wise
for all banks associated with the scheme
The system should provide for automated cheques printing facility with proper
authorization
The system should generate reports of refund money bank wise and applicant wise.
The system should allow generation of a soft copy of refund amount bank wise and
applicant wise for hand over to banks
Calculate Housing Cost and Demand

i.
ii.
The system should interface with costing module for obtaining relevant costing data
The system should import land premium and housing construction cost data from costing
module
SRS
45

iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
11.10
Issue Demand Letters to Allotee

i.
ii.
iii.
iv.
v.
11.11
The system should maintain standard formats for demand letters

The system should automatically generate demand letters for each allottee based on the
demand calculated
The system should allow for bulk and individual printing of demand letters for each
scheme
The system should maintain the date of printing of demand letter allottee wise. The
system should not allow duplicate printing of demand letter without authorization.
The system should maintain the date of issue of demand letter.

ix.
x.
xi.
xii.
xiii.
xiv.
xv.
xvi.
xvii.
11.12
The system should be able to calculate plinth area rates on a half yearly basis by using
average housing cost data (standard costing)
The system should maintain plinth area rates for the current year and previous years.
The system should be able to calculate the housing cost using the plinth area rates and
multipliers specified by the user
The system should allow calculation of demand for two types of payments Cash Down
and Hire Purchase
For cash down, the system should be able to calculate the cash down payment for each
flat allottee wise and scheme wise
For Hire Purchase, the system should be able to calculate the first installment and EMIs.
The system should allow the user to specify pre defined criteria such as first installment
amount (% of total cost), interest rate, no of installments etc for calculating the first
installment amount and EMIs for Hire Purchase schemes
The system should maintain the payment terms (demand) for each allottee
banks
The system should be able to generate discrepancy report allottee wise against
payments received from banks
The system should allow for manual verification and correction of discrepancy cases
The system should track payments received allottee wise and generate exception reports
The system should have facility to generate notifications to appropriate users in case of
late payment of first installment
The system should have facility to generate defaulter list and generate e-mail
notifications to appropriate users
The system should have facility to generate reminder letters for defaulters.
The system should generate reports on payments received/balance allottee wise
The system should have provision for cancellation of allotment in case of default.
Issue Possession Letter
SRS
46

i.
ii.
iii.
iv.
v.
vi.
vii.
11.13
Intimate Hand Over of Possession to Housing

i.
ii.
11.14
The system should generate reports of allottees eligible for issue of possession letter (ie
all payments have been made by allottee)
The system should allow issue of a reminder letter asking for the allottee to apply for
possession along with details of documents required
The system should provide a checklist of supporting documents required for allotment
The system should allow generation of possession letter only if all payments are made
and all documents are received
The system should maintain standard formats for possession letter
The system should generate reports on possession letters issued date wise, scheme
wise etc.
The system should maintain date of issue of possession letter for each allottee
The system should allow authorized users in Engineering department to view the
possession letter issued to an allotee
The system should allow engineering users to input date of hand over of possession of
flat
Execute Conveyance Deed

i.
ii.
iii.
iv.
The system should maintain pre defined formats of Conveyance Deed

The system should allow for printing of Conveyance Deed allottee wise
The system should allow printing of CD only if intimation has been received from
engineering on hand over of possession
The system should generate reports on CDs issued allottee wise/scheme wise
Housing Lease Administration

11.15
Receive Application for Conversion to Freehold from Banks

i.
ii.
iii.
iv.
v.
11.16
The system should have facility for entering applicant details such as applicant name,
address, flat address, scheme under which allotment was made etc
The system should provide for status monitoring of each application received
The system should have the facility to update status of each conversion application with
reference to milestones
The system should have facility to retrieve applicant and flat details from the database by
applicant name, flat no etc
The system should have facility to view all matching applicant/flat data and select the
correct applicant/flat manually
Verify Outstanding Dues

i.
The system should allow the user to view all payment details for the selected flat
SRS
47

ii.
iii.
iv.
v.
vi.
11.17

i.
ii.
iii.
11.18
The system should incorporate pre defined rules for calculating outstanding dues for
each scheme, flat category etc
The system should be able to calculate and display the outstanding dues for the selected
flat
The system should generate demand letter for the selected applicant/flat. The system
should have facility to print the demand letter.
The system should maintain date of issue of demand letter
The system should have facility to export demand details to hand over to banks
banks
The system should be able to generate discrepancy report of payments not
received/partial payments received applicant wise against payments received from banks
The system should allow for manual verification and correction of discrepancy cases
Approve Conversion and Issue Conveyance Deed

i.
ii.
iii.
iv.
The system should allow the user to approve conversion only after receipt of all dues
The system should display details of outstanding dues/payments received etc
The system should maintain pre defined formats for CD
The system should allow generation and printing of CD
Housing Enforcement
11.19
Receive Complaints of Violations from Public

i.
ii.
iii.
11.20
The system should have facility to maintain details of complaints received such as
complainant name, flat details, flat owner details
The system should generate an automatic complaint no for each complaint
The system should provide for status monitoring of each complaint
Check Violation and Issue Show Cause Notice

i.
ii.
iii.
iv.
v.
The system should allow the department user to view the complaint details
The system should allow the user to view all the flat details from the database
The system should allow the user to enter the report on the violation
The system allow the user to print show cause notices under section 30/31
The system maintain pre defined formats for show cause notices
SRS
48

11.21
Receive/Approve application for Regularization

i.
ii.
iii.
iv.
v.
11.22
The system should allow inputting of application details

The application should be related to the complaint number
The system should maintain list of supporting documents required for regularization
The system should allow approval of regularization only after all supporting documents
have been confirmed
The system should update regularization details against the concerned flat
Issue Orders for Demolition/Cancellation of Lease

i.
ii.
iii.
iv.
v.
The system should allow users to generate and print demolition/cancellation orders
The system should generate e-mail notification to users in LAB section for cancellation of
lease
The system should allow users to enter action taken report
The action taken and status should be linked to flat no/complaint no
The system should generate reports complain wise/period wise etc
Housing Services
11.23
Receive Application form and documents from applicant

i.
ii.
iii.
iv.
v.
vi.
11.24
Verify Documents and Approve/Reject the Application

i.
ii.
iii.
iv.
v.
vi.
11.25
The system should maintain list of services provided by housing department

The system should generate an automatic application no for each application
The system should allow the user to enter application details such as name, address etc
for each type of service
The system should display a checklist of supporting documents required for each service
The system should allow the user to accept the application only if all supporting
documents are provided
The system provide for status monitoring of each application
The system should allow user to view the application details

The system should allow the user to view all the flat/applicant details from the database
The system should allow the user to accept or reject the application
The system should maintain predefined letter formats for approval/rejection
The system allow user to print approval/rejection letter
The system should update the relevant details in the flat/applicant database
SRS
49
12. Landscape
The Landscape department is headed by Director (Landscape). The main activity of the
landscape department is to prepare the plans for development of the Greens identified in the
Master Plan. The landscape department prepares the landscape plans based on the zonal plans
prepared by Planning. The landscape department also designs the sports complexes developed
by DDA.
The department has 6 Landscape Architects who are responsible for designing and getting the
landscape plans, prepared.
The business process map for Landscape department is given in the following page. From the
process map it can be observed that the Landscape department interacts with Planning (which
gives the zonal plans for the Green to be developed), Land Management (in case of any
encroachment), Engineering (which conducts the feasibility study for development of the Green)
and Horticulture (which develops the Green based on the plans provided by Landscape)
SRS
50
Landscape
<Landscape>
Request from
RWA / Municipal
Councilors
Get the
Preliminary Survey
conducted
Any
encroachment
No
Prepare
Landscape plan
working drawings /
Detailing
Get the detailed

survey conducted
Modify Landscape
Plans
Received Zonal
Plans from
Planning
Horticulture
Engineering
Land
Management
Yes
Yes
Yes
Take steps to clear
encroachment
Conduct Feasibility
Study
Conduct Feasibility
Study
SRS
Modifications
required
Modifications
required
No
No
Receive Plans
for
Development
Receive Plans for

Development
51
SYSTEM REQUIREMENTS
12.1
Receive Zonal Plans from Planning / Requests from RWAs & Municipal Councilors
i.
ii.
iii.
iv.
v.
12.2
Get the preliminary survey conducted and identify encroachment areas

i.
ii.
iii.
iv.
12.3
The system should allow the user to specify the areas of encroachment on the land map.
The system should allow the user to view the status of the land.
The system should allow the user in Land Management department to view the
encroachment details specified by the Landscape department.
The system should allow the user in Land Management department to update the status
of encroachment
Get the detailed survey conducted and prepare landscape plans

i.
ii.
iii.
iv.
v.
vi.
12.4
The system should allow the user to visualize areas identified for landscape development
as per the Master Plan
The system should allow the user to view the Zonal Plans and Layout plans for the area
on which the green is being developed.
The system should be able to view the land map and related land information on which
the green is being developed
The system should allow the user to view the status of the land being developed.
The system should allow the user to view the zonal plan and layout plan for the area
being developed
The system should allow the user to overlay the layout plans over the land map for the
area being developed
The system should allow the user to give suggestions with reference to landscape plans
for the area.
The system should allow the user to drill down from the master plan to the landscape
plan and vice versa
The system should allow the user to view the status of a particular project.
The system should allow the user to view the landscape plan in 3D.
Modify Landscape Plans based on Feasibility study

i.
ii.
iii.
The system should allow the user to view the landscape plan (which is to be modified)
The system should allow the user to suggest modifications in the landscape plan.
The system should maintain earlier versions of the plan (and allow their re-development)
SRS
52
13. Horticulture
The Horticulture department in DDA has Directors (North) and Director (South) at its helm with
both of them reporting to the Engineer Member. There are around 11 Horticulture divisions with a
significant number of Horticulture staff on the field looking after the development and
maintenance of greens.
The activity of Horticulture department usually covers the plots for which development is being
done by DDA and for the green areas mentioned in Master Plan.
SRS
53
SRS
54
SYSTEM REQUIREMENTS
13.1
Database development and Information

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
The system should maintain a database of parks being maintained by DDA

The system should capture the status of Green areas within Delhi for comparison between
two time periods
The system should be able to display location wise status of Green areas within Delhi and
facilitate comparisons
The system should be able to maintain a record of letters exchanged with Municipal
Corporation of Delhi for transfer of parks to them
The system should have the facility to maintain records of transfer of parks like
a) Area transferred,
b) Condition of area at the time of transfer,
c) Any points to be careful on, etc.
The system should have the facility to capture the annual action plan of the department
with Schemes, Budgets, Number of Trees to be planted, etc.
The system should have the provision to monitor the progress of the Action Plan
The system should allow restricted access to users to make changes in the Action Plan
The system should maintain details of land available with Horticulture Division as
a) Land taken from Land Management branch
b) Land taken from Civil Wing
The system should maintain following information on parks
a) District parks to be maintained by DDA
b) Small parks to be transferred to MCD
The system should maintain the details of plantations made during the year
a) Division wise
b) Scheme wise
c) Park wise
The system should maintain necessary records of flower shows
The system should have the provision to maintain revenue raised by the division
The system should allow access to plans prepared by Director Landscape
SRS
55
14. Legal Department

The Chief Legal Advisor (CLA) heads the Legal Department. The main function of the legal
department is to monitor all the court cases involving DDA. The Legal department is responsible
for assigning a panel Lawyer to the case, monitor progress of the case, give opinion on judgment
of a case (whether to appeal or close the case) and monitor compliance of the directions issued
by the court.
The Legal department has posted Law officers in each department of DDA. It is the responsibility
of the law officers to monitor the progress of each case in their respective department. The law
officers report to the Deputy CLA who reports to the CLA.
The business process map for legal department is given in the next page. It can be noted that
legal department interacts with every other department of DDA.
SRS
56
Receive summons
from Court
Administrative
Dept Legal Cell
Dept
Legal Dept
Legal Case Monitoring
Open Legal file

and send to
concerned
department
Prepare duplicate
file and forward to
panel advocate
Receive opinion
and decide to
close case/file
appeal
Send original file

to HoD for
comments
Comments vetted
by law officer and
sent to panel
lawyer
Monitor Case
Progress
Comments on the
case prepared by
nodal officer
Receive copy of
judgement and
opinion from Panel
lawyer
Receive opinion
from law officer
SRS
57
Legal Deptt
Finance
Lawyers Fee - Bill Processing
Receive Fee Bills

and send to
respective Dealing
Clerk
Perform
processing of bills
and payment
Y
Dealing Clerk
check raw bills and
attachments for
completeness
Fill 3 copies of
performa of
payment
Verification of fee bill

for payment through
Jr. Law Officer or
respective authority
Further verification
of entrustment
from records
Send back with

appropriate
comments
Complete?
Sent to accounts
for processing
Advancement of Payment
and Additional payment in
case of objection are also
performed
Following verifications done:

Whether hearing effective or
non-effective,
Whether bill submitted
previously.
Whether charges claimed
are valid as per Fee Bill
policy, etc.
SRS
58
Existing Application Functionality

The legal department currently uses two software applications namely Legal Case Monitoring
System and Lawyer Fee Bill Payment System.
14.1
Legal Case Monitoring System
i.
ii.
iii.
iv.
v.
vi.
vii.
14.2
The application is a legal case monitoring system for tracking the status of all legal cases.
The application has features such as status of the case, next hearing date, lawyer
representing DDA, property details, etc.
The application has separate modules for legal dept and other departments of DDA. Legal
dept can view details of all cases, while departmental users can view only details of cases
of the concerned dept.
The application has options for generating various reports related to a case such as
reminders for next hearing dates, case status reports etc.
The application has a library module for scanning case related documents, which can be
used for reference. Search option is also available.
A Query module is available for searching case details using pre-defined queries. Query
can be done case number wise or case title wise.
Master maintenance module is available for entering/maintaining master data.
Lawyers Fee Bill Processing System
i.
ii.
iii.
iv.
v.
vi.
vii.
The application is a billing system for tracking bills of external lawyers appointed by DDA.
Details for bills presented by lawyers are entered into the application. The bill is verified in
the application (like verification of the lawyer, case no., duplication of bill etc).
After verification, the bill is cleared and payment order details are entered. After the bank
and cheque details are obtained, the same are entered into the application and the bill is
closed.
The application has options for different types of bills such as fees, OPE etc.
Basic data such as lawyer name & address, case details, hearing dates, case status etc
are entered into the master maintenance module.
The application has facilities for managing IT related activities such as TDS reports, Form
16A etc.
Various report options are available for tracking the bills.
These software will have to be enhanced/or suitably modified/recoded as per the requirement to
meet the functionality specified in this section and will have to be integrated with the Integrated
Management System.
SRS
59
SYSTEM REQUIREMENTS
Legal Case Monitoring
14.3
Receive summons/notice from court and open case file

i.
ii.
iii.
iv.
v.
14.4
Forward Case file to HOD for opinion

i.
ii.
iii.
iv.
v.
14.5
The system should allow the law officer/HoD to view the case details
The system should allow the HOD to associate a nodal officer to the case
The system should allow the user to enter para wise comments on the case
The system should allow printing of the comments of the dept in standard formats
The system should allow authorized users to view the comments
Monitor Case Progress

i.
ii.
iii.
iv.
v.
14.6
The system should generate a case number for each case file opened
The system should allow the user to enter the case details such as summons details,
respondent details, standing counsel name, nature of case, administrative department
responsible for the case etc
The system should allow the user to associate a panel lawyer with the case. The system
should maintain list of panel lawyers approved by DDA
The system should be compatible and connected with High Courts database of cases
The system should allow the users to enter and access the property details
The system should allow the user to enter case progress comments
The system should allow the user to enter hearing dates etc for a case
The system should generate alert notification to concerned users regarding hearing dates
etc
The system should allow the user to enter the hearing dates for the case and the names
of attendees
The system should allow the user to view complete history of the case
Receive Judgment and Opinion from Panel Lawyer

i.
ii.
iii.
The system should maintain judgment types such as stay/interim order etc
The system should allow the user to enter the judgment type for a particular case
The system should allow the user to enter the judgment details for a case
SRS
60

iv.
v.
14.7
The system should allow the user to enter the opinion of the panel lawyer on the
judgment
The system should allow authorized users to view the status of the case and its history
Take Decision to Appeal/Close the Case

i.
ii.
iii.
iv.
v.
vi.
vii.
The system should allow authorized users to take decision on the case
The system should allow the user to enter appeal details for the case
The system should allow authorized users to monitor the case
The system should allow authorized users to enter details of directions to be followed by
administrative departments in case of adverse judgments
The concerned HoD should be able to view the details of the directions to be followed.
The system should allow printing of the judgment/directions details
The system should allow the user of administrative department to enter the compliance
report
The system should allow the legal department users to view the status of the
case/compliance report
Lawyer Fee Bill processing
14.8
Receive Lawyer Fee Bill

i.
ii.
iii.
14.9
The system should maintain various rates of fees by Court type, lawyer type, hearing
type etc as per DDA policy
The system should have pre defined formats for entering the bill details
The system should validate the bill with the case details such as lawyer name, hearing
date etc. The system should allow the bill to be processed only if the bill is valid
Calculate fees as per policy

i.
ii.
iii.
iv.
14.10
The system should automatically calculate the fees based on the rates maintained in the
system
The system should allow approval of the bill only if the amount is equal to or less than the
calculated fees
The system should allow exception cases to be approved by authorized users
The system should deduct TDS while calculating the amount to be paid. TDS rates
should be maintained in the system
Issue Payment Cheque

i.
ii.
The system should maintain details of payments made by lawyer and case number
The system should interface with cash module for issue of cheques and printing
SRS
61

iii.
iv.
14.11
The system should have relevant checks and should not allow duplicate payments for the
same case/hearing/lawyer
The system should generate reports of payments made/bills submitted by case/lawyer
etc as per requirements
Reports
i.
ii.
iii.
iv.
v.
vi.
The system should generate reports of pending cases for next hearing date.
The system should generate reports of cases for which hearings are scheduled during a
particular period
The system should generate reports of cases by lawyer/court/department etc.
The system should generate reports on judgments delivered/directions issued
The system should generate compliance report by case number
The system should be able to generate performance reports for each lawyer
SRS
62
15. Finance Department

The Finance Member heads the Finance Department. The Chief Accounts Officer (CAO), Director
(Finance) and Director (Land Costing) report to the Finance member. The finance department
handles all activities relating to financial transactions in DDA.
The Finance Department is broadly divided into the following sections:
Accounts: This section is headed by the CAO. The Central Accounting Unit is the basic
accounting unit of DDA. This section handles all functions related to accounting and budgeting.
Land Costing Section: This section is responsible for the costing of land under various categories,
which are to be sold by DDA. The section is headed by Director (Land Costing)
Finance: This section is responsible for handling all activities related to project cost estimates.
This section is responsible for giving the financial concurrence for preliminary cost estimates
provided by engineering for a project.
The finance department interacts with all departments of DDA. In addition it also interacts with
customers and banks. The department receives and makes all payments on behalf of DDA.
Existing Application Functionality

The Costing section uses a spreadsheet model for conducting the Cost Benefit Analysis for
Projects. In addition Costing and Housing Accounting software has been developed by M/s
S.G.Martin & Co., which is currently not being used. A Payroll software is being used by the
department for processing of each departments payroll.
These existing applications need to be modified/enhanced and integrated with the Integrated
Management System
SYSTEM REQUIREMENTS
General Ledger
SRS
63

15.1
15.2
15.3
Chart of Accounts
i.
ii.
15.4
Journal Entries
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
15.5
The system should follow accrual method of accounting

The system should provide facility to post journal entries on line
The system should have facility to delete and reenter a single journal entry
The system should have option to revise erroneous journal entries on line
The system should have facility to enter description for each journal entry
The system should display control totals after each journal entry
The system should allow printing of control totals before updating general ledger file
The system should have facility to automatically generate standard journals, accruals,
accrual reversals, recurring or repeating journals
The system should have facility to generate detailed listing of transactions by
account/journal.
The system should process year end adjustments as a separate period
The system should be able to post to new period/year before current period/year closes
Budgeting
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
15.6
Codify Chart of Accounts under 3 Heads of Accounts Nazul 1, Nazul 2 and General
Development Account
The system should provide facility to maintain chart of accounts Add/Delete/Modify
The system should have facility to enter receipt and expenditure budgets department
wise
The system should maintain pre-defined formats for entering budget data
The system should have facility for entering budget data scheme wise
The system should compile and generate receipt and expenditure budget reports
The system should support multiple open budget versions
The system should have facility to monitor actual versus budget
The system should have facility to roll forward actual and budget to the next year
The system should have facility to create budget for the next year before the current year
closes
The system should have ability to calculate budget variances
The system should have facility to base new budget versions as %increase/decrease
over previous year
The system should allow quarterly review of Budgetary receipts and payments
Reporting
SRS
64

i.
General Reporting:
a. Trial Balance
b. Profit & Loss (Prior year comparative data)
c. Balance Sheet under double entry system if it is functional in DDA or as per the
current system functional in DDA
d. General Ledger Detail Report
e. Financial Statement Ratio Analysis
f. Chart of Accounts listing
g. Departmental Income/Expenses with Budget Vs Actuals
h. Fund flow requirement
i. Fortnightly / Monthly Cash flow review
j. Review of works over Rs. 5 Crores
k. Review of major activities in the land, housing etc.
l. Review of establishment expenditure over Works expenditure
m. Review of Sundry Creditors
ii.
iii.
iv.
v.
The system should provide for user specified reporting

The system should have facility to run reports while the system is on line
The system should have a financial report writer which utilizes user defined parameters
The system should provide graphics reporting capabilities
Accounts Receivable
15.7
Customer Information
i.
ii.
iii.
iv.
15.8
The system should maintain customer (allottee) information such as Name, Address,
plot/land bought etc
The system should maintain customer history such as payment/default details,
paid/outstanding amount, payment terms and schedule etc
The system should be able to calculate total Accounts Receivable balance by Customer,
period, scheme etc.
The AR module should interface with the budgeting module.
Billing
i.
ii.
iii.
iv.
v.
vi.
The system should generate bills for each customer

The system should be able to calculate interest charges and past due charges
The system should be able to compute late payment charges according to individual
customer payment terms
The system should be able to prepare invoices and statements as per user defined
formats
The system should allow different invoice descriptions based on type of receivable
The system should be able to produce one time invoices
SRS
65

vii.
15.9
The system should interface with Housing/Land Disposal modules for processing
customer payments
Cash Receipts/Processing/Reconciliation
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
15.10
The system should be able to process full and partial payments

The system should record payment types such as cheques/cash/bank etc
The system should maintain customer balances
The system should apply overpayment/underpayment to next invoice
The system should allow receipt of payment through EFT
The system should allow receipt/transmission of bank data electronically
The system should allow the use of a suspense account for correcting errors
The system should use line-by-line method to transfer errors to suspense account and
authorized resubmit.
The system should suspend out of balance batches until corrected
The system should provide interface to General Ledger
Reporting
i.
ii.
iii.
iv.
The system should generate accounts receivable summary and detailed aging report
The system should allow credit management reporting/inquiry listing customer accounts
over a specified number of days past due etc
The system should have ability to forecast accounts receivable cash receipts by
day/week/month based on receivable and past history
The system should have ability to combine Accounts Receivable with Accounts Payable
to show the cash position of the company
Accounts Payable
15.11
Invoices
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
The system should have facility to enter both approved and unapproved invoices on line
The system should have facility to generate invoice only after approval from authorized
person.
The system should allow definition of approval/authorization levels by user.
The system should have facility to modify/delete/cancel an invoice before it is paid by
authorized person only
The system should have facility to enter for matching purposes PO, Invoice Number,
Vendor Number
The system should have ability to process non purchase order payables
The system should have automated cheques printing facility to be used by authorized
user.
The system should allow users to maintain tax details of:
SRS
66

a.
b.
c.
d.
e.
15.12
Vendor/Contractor Information
i.
ii.
iii.
15.13
The system should maintain vendor/contractor information with unique vendor number
The system should generate vendor lists in alphabetic sequence/numeric sequence
The system should have facility to categorize vendors based on user specifications
Bank Reconciliation/Error Checking

i.
ii.
iii.
iv.
v.
vi.
15.14
VAT
Fringe Benefit Tax
Service Tax
Property Tax
Other as required by user
The system should have ability to compare issued cheques with cleared cheques
The system should generate a report of outstanding cheques
The system should support wire transfers/direct deposits to vendors
The system should flag invalid PO numbers
The system should flag Invoice/PO variances > user defined %
The system should allow online validation of data and error correction
Reporting
i.
ii.
iii.
iv.
v.
The system should generate report on outstanding invoices by invoice date/due date
The system should generate a report of open purchase orders
Ability to forecast A/P cash requirements for day/week/month based on vendor invoices
and open/closed POs
Ability to combine A/R system with A/P system to show cash position of the company
The system should maintain details of status of investments made in different Banks /
Institutions / Govt. Securities (Head wise)
Inventory/WIP/FG
15.15
Land
i.
ii.
iii.
iv.
Land is a stock item for DDA. The system should maintain a stock register for land
acquired by DDA
The land stock register should have both area and value
The system should be able to track the expenditure incurred on a plot of land for land
development
The system should have interface with the engineering and accounts payable module for
collecting land development expenditure data
SRS
67

v.
vi.
vii.
viii.
ix.
15.16
The system should be able to update the stock register as required

The stock register should reflect the current valuation of Land at any given point of time
The system should be able to calculate the weighted average cost of land for valuation
purposes
Once the land is split and sold as plots, the system should value the land accordingly to
the stock register
The system should be able to generate reports on Inventory/WIP and FG of land
Housing
i.
ii.
iii.
iv.
v.
vi.
The system should maintain stock register for all flats/housing being constructed by DDA.
The register should be maintained scheme wise.
All expenditure incurred for construction of a house (under general development account)
should be tracked by the system. The system should interface with the engineering and
accounts payable module for this purpose.
The stock register should be updated with cost of construction for valuation of the
housing inventory.
The system should be able to calculate the weighted average cost of the flat scheme
wise for valuation purposes
Once the houses are sold, the system should value the house accordingly.
The system should be able to generate reports on Inventory/Work In Progress and
Finished Goods of land.
Fixed Assets
15.17
Fixed Assets maintenance

i.
ii.
iii.
iv.
v.
The system should maintain the fixed asset register of DDA.

The system should maintain the date of purchase of the asset, cost of purchase, asset
category and depreciation rate for the asset.
The system should be able to calculate the depreciation charges for each asset.
The system should be able to calculate the closing balance asset value as per
accounting policies of DDA
The system should generate the Fixed Asset Register.
Costing and Pricing
SRS
68

i.
15.18
Residential Lands
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
15.19
The system should maintain the details of location of each property based on standard
criteria
The system should maintain the land acquisition cost for land acquired by the Delhi
Administration.
The system should maintain the pool rates fixed by the Delhi Administration (Land and
Building Department) for various zones.
The system should maintain current and historical pool rates.
The system should be able to calculate the land acquisition cost for a particular plot of
land based on the pool rate.
The system should be able to calculate the cost of development of land based on
expenditure incurred for land development by engineering, administrative charges etc.
The system should have adequate interface with engineering and accounts payable
modules for this purpose
The system should allow for use of multipliers for calculation of land disposal rates for
different categories of land.
The system should be able to maintain the multipliers with option to the user to change
them
The system should maintain the pricing data for each plot of residential land sold.
Commercial Lands
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
The system should maintain the auction rate obtained on disposal of commercial land in
Delhi by area, zone etc.
The system should enable the user to calculate the average auction rate for the plot to be
sold by specifying the zone/area of similar plots
On specification of the zone/area etc, the system should be able to calculate the average
auction rate based on the auction rates of the specified plots.
The system should be able to calculate the reserve price for the plot being sold based on
the floor space specified for the plot
The system should maintain the reserve price for each plot of land sold.
The system should allow authorized users to modify (increase/decrease) the reserve
price calculated by the system.
The system should have the facility to display conversion rates for commercial land on an
year to year basis
The system should be able to maintain a list of conversion cases finalized
The system should have the facility to provide global market rate for commercial property
based on auction/tender rates
The system should enable the user to calculate average license fee for the commercial
properties
SRS
69

xi.
xii.
xiii.
xiv.
15.20
Institutional Lands
i.
ii.
iii.
iv.
v.
vi.
15.21
The system should be able to display license fees zone wise / area wise for similar
properties
The system should be able to calculate average license fees based on floor space etc. as
specified
The system should have the facility to maintain a reserve license fee for each property
given on license fee
The system should allow authorized users to modify (increase/decrease) the license fee
calculated
The system should maintain the rates fixed by the government for disposal of institutional
lands.
The system should be able to calculate the disposal price for a specified piece of
institutional land based on the above rates.
The system should allow the user to modify the rate for a particular institutional plot (for
plots sold at concessional rates).
The system should maintain disposal price for each institutional plot sold
The system should be able to display conversion rates of industrial land on zonal basis
The system should maintain the list of conversion cases finalized
Pre Determined Rates for Projects (Cost Benefit Analysis)

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
The system should maintain land acquisition cost for land acquired by Delhi Govt.
The system should have the functionality to conduct cost benefit analysis for concluding
pre determined rates for land premium for Projects
The system should use Discounted Cash Flow (DCF) for estimating the present value of
both revenue and expenditure.
The system should allow the user to specify the discount rate for the DCF analysis
The system should interface with accounts payable and engineering module for obtaining
the project cost data.
The system should allow interface with Land Management department for
a. Total land acquired
b. Total land to be acquired
c. Compensation Paid
d. Additional Compensation
e. Other information as per user
The system should allow interface with Planning Wing for
a. Land use distribution
The system should be able to calculate the Break Even rate on a no profit no loss basis.
The system should maintain the pre-determined rates for previous years.
The system should maintain multipliers for different land use categories.
The system should generate reports on the CB Analysis as required by the users
SRS
70

xii.
xiii.
xiv.
15.22
Housing Cost
i.
ii.
iii.
iv.
v.
15.23
The system should maintain the pre-determined rates for developed areas / colonies by
adopting the break-even rate for developed areas
The system should provide users with details of revenue receipts as per:
a. Receipt from auction of land
b. Receipt from allotment of PDR
c. Receipt from allotment on concessional prices to public, semi-public
organizations
d. Receipt from institutions and organizations to whom land has been allotted at
Zonal variant rates
e. Receipt from institutions and organizations to whom land has been allotted at full
market rates
f. Receipt from Housing Wing on account of land transferred to GDA for
construction of flats
g. Receipt from disposal of built up properties allotted at reserve and full market
rates
h. Any other receipts as per user
The system should be able to generate year wise market rates for:
a. Misuse charges
b. Composition Fee
c. Damage Charges
The system should calculate the Housing cost as equal to Land Premium plus Half Yearly
average of the housing construction cost
The system should calculate the Plinth Area rates based on the average housing
construction cost. The system should maintain the current and past plinth area rates.
The land premium cost is equal to the land cost multiplied by a multiplier for each
category of houses. (eg 0.85 for LIG etc)
The system should interface with housing module for calculation of demand and
installments.
The system should have provision to interface:
a. With Engineering Wing for Cost of construction of each scheme along with flat
details
b. Land Costing wing for land rate
Demand and Collection Register

i.
ii.
iii.
The system should maintain the demand and collection register plot wise.
The system should be able to calculate the ground rent to be collected for each plot of
land sold along with the schedule of payments.
The system should interface with accounts receivable module to update ground rent
payments received for each plot of land.
SRS
71

iv.
v.
vi.
vii.
viii.
ix.
x.
15.24
Preliminary Cost estimates

i.
ii.
iii.
iv.
v.
15.25
The system should be able to calculate interest penalty for late payments. The system
should maintain the rate of interest to be charged.
The system should allow for generation of notices to defaulters on a periodic basis.
The system should be able to maintain records of ground rent received and outstanding
during a year in respect of any colony at any point of time
The system should allow authorized users to delete/modify/add any demand of ground
rent
The system should be able to generate a list of sundry debtors year wise
The system should have the provision to reconcile the total credit given to new properties
with the figures as booked by accounts (main)
The system should be able interface with the third party financial service providers for
demand and collection registers, etc.
The system should maintain the preliminary cost estimates for engineering project cost
estimation.
The system should maintain Delhi Schedule of rates issued by CPWD
The system should interface with engineering module for maintaining of preliminary cost
estimates
The system should allow the authorized users to view the preliminary estimates for a
project prepared by engineering.
The system should allow the authorized users to view the preliminary estimates for a
project prepared after accord of financial concurrence
Compilation of Monthly / Annual Accounts

i.
ii.
iii.
The system should have the facility for compilation of accounts by various accounts
rendering units:
a. Zonal CAUs
b. Housing
c. PAO (EW)
d. Store Division I and II
e. DDA (Main) etc.
The system should have the facility for compilation of monthly and annual accounts by
Head Quarters
The system should be able to generate consolidated registers for maintenance of
scheme wise with sub-head of account wise details
Payroll
15.26
Payroll Maintenance
SRS
72

i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
15.27
Payroll Processing
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
15.28
The system should maintain personnel data of each employee of DDA.

The system should maintain the following details of each employee: Name, Department,
Designation, Pay Scale, Seniority, Cadre etc.
The system should maintain the payroll data of each employee such as Basic, DA, HRA,
Allowances, EPF, GPF, LIC premium etc.
The system should calculate GPF balance of each employee of DDA at the close of each
financial year
The system should maintain the leave records of each employee. The system should
enable authorized users to update leave data on a regular basis.
The system should generate Form 16 of Income Tax in respect of each employee
The system should generate annual tax returns
The system should have facility of e-TDS
The system should generate quarterly Fringe Benefit Tax returns of DDA
Payroll software should be in Hindi
The system should have monthly details of Pension contribution subscribed by each
individual and equal amount deposited by DDA under new Pension Scheme to be
introduced in DDA with effect from 1.1.2004
The system should process the salary of each employee every month.
The system should have automated salary cheques printing facility by authorized users
The system should allow authorized users to access the payroll information.
The system should have the facility to automatically increase the basic pay of an
employee equivalent to the amount of annual increment after every year.
The system should have facility to calculate Income Tax of an employee and prepare
various reports like Form-16 and other related reports
The system should allow the user to edit the payroll data for an employee (in case of
promotions, penalties etc)
The system should be integrated with the Personnel management Information System
and the Accounts Payable module.
The system should be able to calculate the retirement benefits of an employee.
SRS
73
16. Personnel Department

The personnel department at DDA is headed by Commissioner (Personnel & Systems) and has
the following broad work areas:
1. Personnel Branch 1: For employees under gazzeted group A, group B and small cadres
Personnel Branch 2: For Technical Group C employees
Personnel Branch 3: For clerical, Group C, Ministerial employees and stenographers
Personnel Branch 4: For miscellaneous group C and artesian cadres
2. Transfers and Postings
3. Performance appraisals through ACRs, recruitments
4. Policy and Coordination Branch
5. Welfare activities, Retirement Benefits, Disciplinary cases, etc.
DDA has already developed a Personnel Management Information System (PMIS) using Oracle
as the Database and Developer 2000 as the front-end.
16.1
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.

Service Records
Recruitment and Reservations
Employee Service Book Events
Transfers and Postings
Training
Promotions
Confidential Reports
Loans and Advances
Leave Data maintenance
Leave Travel Concession
Employee related Disciplinary and Court cases
Retirement and Death Cases
Personnel File Tracking activity
Policy Matters of Policy and Coordination branch
Staff Grievances
MIS reports
The solution development agency is expected to integrate the existing PMIS application to the
Integrated Management System. Any modifications / improvements generated during preparation
of the detailed Software Requirement Specifications may also need to be incorporated
SRS
74
SYSTEM REQUIREMENTS
16.2
Integration and Functionality enhancement

Following is the functionality, which has not been incorporated in the PMIS and needs to be
incorporated:
i.
ii.
iii.
iv.
v.
The system should be able to maintain training calendars and allow users to access the
calendars for viewing information on available trainings
The system should be able to integrate with the Finance department on the following:
Issue of promotion orders
Allotment of Staff Quarters
Leave eligibility and records
Punishment notices issued
The system should integrate with the Vigilance department for monitoring of legal cases
and their results for an employee
The system should have the facility to capture information like grievance details,
negotiation points, etc. of interaction with unions
The system should be able to generate reports like:
Category wise number of employees with their age profile and qualifications of
each
Search history of transfers and postings of employees on the basis of specific

user defined attributes
User defined reports
SRS
75
17. Website Functionality

At present the DDA website, www.ddadelhi.com is hosted by a third party ISP and primarily
provides information to the general public on the functioning of different departments of DDA
The existing website provides the following information
17.1
Existing Information on website

i.
ii.
iii.
iv.
About DDA
DDA at a glance
Achievements
Charter
Organization Chart
Planning
Master Plans
Zonal Plans
Urban Extension project
Traffic and transport
Other projects
Special projects
Policy modifications
Building guidelines
Housing
Live schemes
Draw Results
Allotment queries
Relief Schemes
Procedures and Permissible alterations
Building Bye Laws
Lands
Residential Properties
Commercial Properties
Industrial Properties
Institutional Properties
Public Notices
Allotment Queries
SRS
76

v.
Urban Heritage
vi.
vii.
viii.
ix.
Description of different urban heritage sites
Sports
Sport Complex locations and descriptions
Multi-Gyms locations
Golf Courses
Greens
Environment
Parks
City Forests
Landscapes
Sports facilties
Landmarks
Play fields
Nurturing Sports
Notices
Public Notice
Tender Notice
Procedures for Housing, Lands and Buildings
Along with this the existing website also provides links to some important websites concerned
with the Development of Delhi.
In addition to the functionalities and features already existing, following functionalities are being
proposed as part of the Integrated Management System
17.2
Interface to Customers
i.
ii.
iii.
iv.
vii.
viii.
The website should allow online submission of applications for registration for allotment
under a particular scheme
The website should maintain and allow access to the updated records of registered
applicants under all schemes
The website should maintain a list of successful applicants based on allotment through
draw and other means
The website should provide information on the payments made by allotee
Initial Payment, EMI schedule
Current status of payments received
Details of fines or penalties imposed
Final Payment date and status
In case of non-payment, the website should allow users to access directly or request over
internet for the dues to be paid by them
The website should flag-off the completion of payments for an allotee and provide
information on way forward for execution of conveyance deed
SRS
77

ix.
17.3
Interface to general public

i.
ii.
iii.
x.
xi.
xii.
xiii.
17.4
The website should allow receipt of complaints from general public on misuse of
residential premises for other purposes
Website should maintain the policies related to auction, allotment of land available to the
general public for download through the Internet
Website should display notifications for general public and allow download of notification
from the internet
The website should maintain, if required, information on future land acquisition plans
The website should allow display of gazette notifications on the web
The website should allow web-based receipt of objections to notifications issued
The website should display information on the web for area under DDA for development
purposes
Interface to Contractors
i.
ii.
iii.
17.5
The system should capture information on compensation paid to land owners and display
it on the web
The website should allow contractors to download tenders on the internet

The website should allow prospective vendors to download forms through the internet
The website should display results of award of work on the internet if required
Interface with Service Providers like Banks, online auction sites

i.
ii.
iii.
The website design should make adequate arrangement for integration with bank
databases for online updating of information related to deposit of money (challans) made
by allotee
The website should have the facility for online capture of information generated by Banks
on money deposited by Allotee
The website should have the facility to integrate with online auction sites for facilitating
the auction process
SRS
78
18. Other System Requirements

All the system mentioned below need to be enhanced or suitably recoded/modified as pre the
requirements mentioned in this section and will have to be integrated with Integrated
Management System.
18.1
Vigilance System
The Vigilance department at DDA is headed by the Chief Vigilance Officer and the main activity is
to monitor any policy breaches by the staff of DDA. Following are the requirements of the
department
SYSTEM REQUIREMENTS
i.
ii.
iii.
iv.
v.
vi.
vii.
18.2
The system should be able to maintain and display records of court case decisions
The system should be able to maintain different categories of Vigilance court cases and
classify the results amongst one of these heads
The system should be able to capture vigilance related data for each officer
The system should interface with the Personnel system to access records of all officials
as required
The system should capture and provide online read access to all for circulars issued by
Vigilance department
The system should be able to maintain a unique id number for each employee
The system should be able to capture all vigilance related complaints and display it in a
pre-defined or user defined format
Public Relations
The Public Relation department within DDA comes under the Principal Commissioner Cum
Secretary and is headed by the Director (Public Relations).
At present DDA has a developed an application Public Grievance Redressal and Monitoring
System (PGRMS), which is browser based application and has SQL as back-end and ASP with
Visual Basic and Java script at front-end. This application at present is partially implemented and
at other places awaiting hardware deployment and will have to be enhanced or suitably recoded /
SRS
79

modified as per requirements specified in this section and will have to be integrated with the
Integrated Management System.
SYSTEM REQUIREMENTS
The following list provides the software requirements for Public Relations:
i.
ii.
iii.
iv.
v.
vi.
vii.
The system should allow advance information to be shared with internal departments for
advertisements released by DDA from time to time
The system should maintain records of updated status of cases
The system should maintain a database of all releases issued by the Public Relations
department with access to internal departments
The system should allow receipt and forwarding of all grievances received by the Public
Relations department
The system should maintain a list of disposals made by departments
The system should maintain a database of all notifications issued by DDA to the general
public
The system should have the provision to allow centralized monitoring of e-mails
responded to by DDA officials
Additionally the system should be able to cater to the following requirements of the
Public Relations department
i.
ii.
iii.
iv.
18.3
The library should be linked so that status of books and also their catalogues are
available to all the officers within the Organization
There should be access of the P.R. Department to the Data Base of other departments so
that dissemination of information without wastage of time can be ensured
The system should also ensure that the letters received at the computerized R & D
System which are being sent to all the HODs under a scroll, are also monitored through
the system instead of being monitored only at the HODs level in their respective
departments. The status of their disposal should also be reflected at the R & D counter
Public Relations should have access to the Data Base of Parliament questions which is
being prepared by the P & C
Postal Mail/Correspondence Receipt and Dispatch at Reception Counter

Monitoring System Requirements
i.
ii.
The system should be able to monitor the following:
Department records
Branch Records
Senders Records
Mark -To Records
The system should be able to track and maintain the status of postal communication
SRS
80

iii.
iv.
18.4
Destination department
Source agency / department
User defined classifications
The system should be able to generate reports like:
Receipt Report
Dispatch Report
User defined reports
File Tracking and Receipt and Dispatch System Requirements
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
18.5
The system should have the facility for classification of postal communication into
categories based on:
The system should have the facility to ensure secure access for entry of file/paper for
single and multiple files/papers
The system should allow users to raise request for a file if it is not available currently
The system should be able to generate notifications to the concerned user as and when
the file becomes available
The system should have the provision to track the current location of any file/paper
whether it is with a being with a particular user, kept at storage or compactor room, etc.
The system should have the facility to transfer the ownership of the file from one user to
another
The system should be able to categorize files/papers under standard and user defined
categories
The system should support user ids and password based access to information
The system should be able to track the movement of files and generate reminders based
on responsibilities and deadlines
The system should be able to generate reports on:
File/Paper activity
Login report
Pending request reports
File inventory report
Inactive file reports
The system should be able to maintain records of list of files worked on by each user and
allow users to see their file usage history
The system should support browser based access
The system should have the capability to integrate with web-based solutions
VC Office
SRS
81

The system should incorporate requirements of VC office like inflow and outflow of letters and
postal mail, case history monitoring and maintenance and file movement details, etc. The system
should be able to generate appropriate reminders and alerts for the same.
18.6
System department
The system should incorporate requirements of Systems department like maintenance of stock
registers of all IT equipment with adequate details of its location and person allotted to. The
proposed system should also allow raising of complaint tickets and monitoring of the same
through various reports and alerts.
18.7
Office of the Principal Commissioner cum Secretary

The system should incorporate requirements of other sections of principal commissioner cum
secretary and the various reports as per the requirements of these sections
SRS
82

SRS Version 1.17 (22-08-06)

Загружено:

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

Исходное описание:

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

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

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

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

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

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

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

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

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

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

SRS Version 1.17 (22-08-06)

Загружено:

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

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

Conceptual System Requirement Specification Ver. 1.

GEOGRAPHIC INFORMATION SYSTEM (GIS)..........................................................................2

DDA INFORMATION SYSTEM (DIS)..............................................................................................2

CONCEPTUAL SRS FOR EACH DEPARTMENT.........................................................................4

EXISTING APPLICATION FUNCTIONALITY.....................................................................................14

RECEIVE PROJECT SCHEME DETAILS FROM ENGINEERING AND PLANNING................................10

RECEIVE CONCEPTUAL / DEVELOPMENT PLANS FROM PLANNING DEPTT..................................19

EXISTING APPLICATION FUNCTIONALITY.....................................................................................29

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

RECEIVE ZONAL PLANS FROM PLANNING...................................................................................51

EXISTING APPLICATION FUNCTIONALITY.....................................................................................42

ALLOTMENT OF LAND AS COMPENSATION TO ROHINI REGISTRANTS AND GH SOCIETIES.........31

DATABASE DEVELOPMENT AND INFORMATION............................................................................54

LEGAL CASE MONITORING SYSTEM............................................................................................58

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

3.11 PERSONNEL DEPARTMENT.........................................................................................................73

EXISTING APPLICATION FUNCTIONALITY................................................................................73

3.12 WEBSITE FUNCTIONALITY.........................................................................................................75

EXISTING INFORMATION ON WEBSITE.....................................................................................75

3.13 OTHER SYSTEM REQUIREMENTS.............................................................................................78

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Re-engineering and Integration of various existing applications/modules

Development of new applications

Development / Implementation of applications like Geographic Information Systems (GIS)

Providing adequate software training, handholding and post-implementation support to

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Geographic Information System (GIS)

DDA Information System (DIS)

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

5. Conceptual SRS for each Department

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Prepare Annual and Monthly Plans

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Monitor/Revise Annual and Monthly Plans

Prepare Project Schemes and Development Plans for the Project

Provide various Reports as per requirements of the department

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Receive Project Scheme details from Engineering and Planning

Prepare Architectural Design

Provide various Reports as per requirements of the department

Delhi Development Authority

Conceptual System Requirement Specification Ver. 1.17 (22-08--06)

Survey / Measured Drawing

Preparation of Conceptual Design & Layout

DUHF Approval For All

Issue of Drawings for Service & Site