Sie sind auf Seite 1von 85

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. PREPARE GIS BASED MASTER PLANS AND ZONAL PLANS (LONG TERM PLANNING)..................6

          • 3.1.2. PREPARE ANNUAL AND MONTHLY PLANS.....................................................................................6

          • 3.1.3. MONITOR/REVISE ANNUAL AND MONTHLY PLANS.......................................................................7

          • 3.1.4. RECEIVE LAND DETAILS FROM LAND MANAGEMENT DEPARTMENT & PREPARE LAYOUT PLANS 7

          • 3.1.5. PREPARE PROJECT SCHEMES AND DEVELOPMENT PLANS FOR THE PROJECT...............................7

          • 3.1.6. BUILDING SECTION........................................................................................................................7

          • 3.1.7. PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT..................................7

  • 3.2 ARCHITECTURE................................................................................................................................8

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

    • 3.2.2. PREPARE ARCHITECTURAL DESIGN.............................................................................................10

    • 3.2.3. PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT................................10

  • 3.3 LAND MANAGEMENT....................................................................................................................12

    • 3.3.1. EXISTING APPLICATION FUNCTIONALITY.....................................................................................14

    • 3.3.2. RECEIVE PROPOSAL AND CONDUCT PRELIMINARY SURVEY.........................................................14

    • 3.3.3. APPROVAL AND MAINTENANCE OF RECORDS...............................................................................15

    • 3.3.4. LAND ACQUISITION INFORMATION AND PROGRESS.....................................................................15

    • 3.3.5. COMPENSATION............................................................................................................................16

    • 3.3.6. WEB-BASED FUNCTIONALITY......................................................................................................16

    • 3.3.7. MISCELLANEOUS..........................................................................................................................16

  • 3.4 ENGINEERING WING.....................................................................................................................17

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

    • 3.4.2. RECEIVE DETAILS OF LAND ACQUIRED.......................................................................................19

    • 3.4.3. ACTIVITIES OF CRB CELL...........................................................................................................20

    • 3.4.4. MONITORING OF PRE-CONSTRUCTION STAGE..............................................................................20

    • 3.4.5. PREPARE FEASIBILITY REPORTS FOR DETAILED PLANS................................................................20

    • 3.4.6. PRELIMINARY ESTIMATES, ADMINISTRATIVE APPROVAL & EXPENDITURE SANCTION................21

    • 3.4.7. PREPARE DETAILED ESTIMATES AND TECHNICAL SANCTION........................................................22

    • 3.4.8. WORKS EXECUTION AND MONITORING.......................................................................................23

    • 3.4.9. WORKS BUDGETING AND FINANCE RELATED FUNCTIONALITY...................................................24

      • 3.4.10. PROJECT ACCOUNTING............................................................................................................25

      • 3.4.11. ARBITRATION, ENCROACHMENT MONITORING AND DEMOLITION PLANS..............................25

      • 3.4.12. WEB BASED ACCESS................................................................................................................26

      • 3.4.13. PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT............................26

  • 3.5 LAND DISPOSAL..............................................................................................................................27

    • 3.5.1. EXISTING APPLICATION FUNCTIONALITY.....................................................................................29

    • 3.5.2. INTEGRATION WITH OTHER DEPARTMENTS..................................................................................29

    • 3.5.3. FLOAT SCHEME FOR RESIDENTIAL, COMMERCIAL AND/OR INSTITUTIONAL ALLOTMENT............30

    • 3.5.4. RECEIVE APPLICATION FORM AND REGISTRATION MONEY FROM BANKS..................................30

    • 3.5.5. ALLOTMENT OF LAND/SHOPS BY AUCTION, TENDER, COMPUTERIZED DRAW, RESERVED PRICE.31

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

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

    • 3.5.7. ALLOTMENT OF SHOPS UNDER RESERVED CATEGORIES AND STAFF ORDERS...............................31

    • 3.5.8. MONITORING AND DISPOSAL OF PETROL PUMPS, GAS GODOWNS, CNG STATION SITES.............32

    • 3.5.9. MONITORING AND DISPOSAL OF COMMERCIAL BUILT UP PROPERTIES AND LICENSED UNITS.....32

      • 3.5.10. ISSUE OF DEMAND LETTER......................................................................................................32

      • 3.5.11. RECEIVE PAYMENT DETAILS FROM BANKS............................................................................33

      • 3.5.12. PAYMENT, POSSESSION LETTER, CONVERSION TO FREEHOLD...............................................33

      • 3.5.13. PERFORM TRANSFER OF PROPERTY AND MUTATION RELATED ACTIVITIES..............................34

      • 3.5.14. RELOCATION/REDEVELOPMENT OF COMMERCIAL AREAS......................................................34

      • 3.5.15. MAINTAIN RECORDS OF LEGAL CASES AND APPLICATIONS RECEIVED FROM CITIZENS..........34

      • 3.5.16. WEB-BASED FUNCTIONALITY..................................................................................................35

      • 3.5.17. PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT............................35

      • 3.5.17. 36

    • 3.6 HOUSING............................................................................................................................................36

      • 3.6.1. EXISTING APPLICATION FUNCTIONALITY.....................................................................................42

      • 3.6.2. RECEIVE DETAILS OF FLATS AVAILABLE FROM ENGINEERING......................................................43

      • 3.6.3. FLOAT A HOUSING SCHEME.........................................................................................................43

      • 3.6.4. RECEIVE APPLICATION FORM AND REGISTRATION MONEY FROM BANKS..................................44

      • 3.6.5. CONDUCT COMPUTERIZED DRAW................................................................................................44

      • 3.6.6. PREPARE CONSOLIDATED REFUND CHEQUES BANK WISE...........................................................44

      • 3.6.7. CALCULATE HOUSING COST AND DEMAND................................................................................44

      • 3.6.8. ISSUE DEMAND LETTERS TO ALLOTEE........................................................................................45

      • 3.6.9. RECEIVE PAYMENT DETAILS FROM BANKS.................................................................................45

        • 3.6.10. ISSUE POSSESSION LETTER.....................................................................................................45

        • 3.6.11. INTIMATE HAND OVER OF POSSESSION TO HOUSING.............................................................46

        • 3.6.12. EXECUTE CONVEYANCE DEED................................................................................................46

        • 3.6.13. RECEIVE APPLICATION FOR CONVERSION TO FREEHOLD FROM BANKS.................................46

        • 3.6.14. VERIFY OUTSTANDING DUES..................................................................................................46

        • 3.6.15. RECEIVE PAYMENT DETAILS FROM BANKS............................................................................47

        • 3.6.16. APPROVE CONVERSION AND ISSUE CONVEYANCE DEED.......................................................47

        • 3.6.17. RECEIVE COMPLAINTS OF VIOLATIONS FROM PUBLIC............................................................47

        • 3.6.18. CHECK VIOLATION AND ISSUE SHOW CAUSE NOTICE............................................................47

        • 3.6.19. RECEIVE/APPROVE APPLICATION FOR REGULARIZATION........................................................47

        • 3.6.20. ISSUE ORDERS FOR DEMOLITION/CANCELLATION OF LEASE.................................................48

        • 3.6.21. RECEIVE APPLICATION FORM AND DOCUMENTS FROM APPLICANT........................................48

        • 3.6.22. VERIFY DOCUMENTS AND APPROVE/REJECT THE APPLICATION............................................48

        • 3.6.23. PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT............................48

  • 3.7 LANDSCAPE......................................................................................................................................49

    • 3.7.1. RECEIVE ZONAL PLANS FROM PLANNING...................................................................................51

    • 3.7.2. CONDUCT PRELIMINARY SURVEY AND IDENTIFY ENCROACHMENT AREAS..................................51

    • 3.7.3. CONDUCT DETAILED SURVEY AND PREPARE LANDSCAPE PLANS.................................................51

    • 3.7.4. MODIFY LANDSCAPE PLANS BASED ON FEASIBILITY STUDY......................................................51

  • 3.8 HORTICULTURE..............................................................................................................................52

    • 3.8.1. DATABASE DEVELOPMENT AND INFORMATION............................................................................54

  • 3.9 LEGAL DEPARTMENT....................................................................................................................55

    • 3.9.1. LEGAL CASE MONITORING SYSTEM............................................................................................58

    • 3.9.2. LAWYERS FEE BILL PROCESSING SYSTEM..................................................................................58

    • 3.9.3. RECEIVE SUMMONS/NOTICE FROM COURT AND OPEN CASE FILE.................................................59

    • 3.9.4. FORWARD CASE FILE TO HOD FOR OPINION...............................................................................59

    • 3.9.5. MONITOR CASE PROGRESS..........................................................................................................59

    • 3.9.6. RECEIVE JUDGMENT AND OPINION FROM PANEL LAWYER.........................................................59

    • 3.9.7. TAKE DECISION TO APPEAL/CLOSE THE CASE............................................................................60

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

    • 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. CHART OF ACCOUNTS.............................................................................................................62

      • 3.10.2. JOURNAL ENTRIES...................................................................................................................63

      • 3.10.3. BUDGETING.............................................................................................................................63

      • 3.10.4. REPORTING..............................................................................................................................63

      • 3.10.5. CUSTOMER INFORMATION.......................................................................................................64

      • 3.10.6. BILLING...................................................................................................................................64

      • 3.10.7. CASH RECEIPTS/PROCESSING/RECONCILIATION.....................................................................65

      • 3.10.8. REPORTING..............................................................................................................................65

      • 3.10.9. INVOICES.................................................................................................................................65

        • 3.10.10. VENDOR/CONTRACTOR INFORMATION....................................................................................66

        • 3.10.11. BANK RECONCILIATION/ERROR CHECKING............................................................................66

        • 3.10.12. REPORTING..............................................................................................................................66

        • 3.10.13. LAND.......................................................................................................................................66

        • 3.10.14. HOUSING.................................................................................................................................67

        • 3.10.15. FIXED ASSETS MAINTENANCE.................................................................................................67

        • 3.10.16. RESIDENTIAL LANDS...............................................................................................................68

        • 3.10.17. COMMERCIAL LANDS..............................................................................................................68

        • 3.10.18. INSTITUTIONAL LANDS...........................................................................................................69

        • 3.10.19. PRE DETERMINED RATES FOR PROJECTS (COST BENEFIT ANALYSIS)....................................69

        • 3.10.20. HOUSING COST.......................................................................................................................70

        • 3.10.21. DEMAND AND COLLECTION REGISTER...................................................................................70

        • 3.10.22. PRELIMINARY COST ESTIMATES..............................................................................................71

        • 3.10.23. COMPILATION OF MONTHLY / ANNUAL ACCOUNTS................................................................71

        • 3.10.24. PAYROLL MAINTENANCE........................................................................................................71

        • 3.10.25. PAYROLL PROCESSING............................................................................................................72

        • 3.10.26. PROVIDE VARIOUS REPORTS AS PER REQUIREMENTS OF THE DEPARTMENT............................72

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

    • 3.11.1. EXISTING APPLICATION FUNCTIONALITY................................................................................73

    • 3.11.2. INTEGRATION AND FUNCTIONALITY ENHANCEMENT..............................................................74

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

    • 3.12.1. EXISTING INFORMATION ON WEBSITE.....................................................................................75

    • 3.12.2. INTERFACE TO CUSTOMERS.....................................................................................................76

    • 3.12.3. INTERFACE TO GENERAL PUBLIC.............................................................................................77

    • 3.12.4. INTERFACE TO CONTRACTORS................................................................................................77

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

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

    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.

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

    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

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

    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.

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

    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)

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

    Conceptual System Requirement Specification Ver. 1.17 (22-08--06) Delhi Development Authority SRS

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

    SYSTEM REQUIREMENTS

    • 5.1 Prepare GIS based Master Plans and Zonal Plans (Long Term Planning)

    i.

    The system should allow the user to prepare master plans and zonal plans for Delhi

    The system should be able to show the land use classification zone wise.

    ii.

    The system should be able to show the details of the same area at the master plan level,

    iii.

    zonal plan level and the layout level. The system should be able to define the various zones and indicate the manner in which

    iv.

    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

    v.

    Master Plan Norms.

    vi.

    The system should be able to integrate the Projects i.e., existing and targeted by Delhi

    vii.

    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

    viii.

    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,

    ix.

    rail and metro-system to provide for seamless multi-modal transport. The system should enable transportation network analysis to facilitate efficient planning

    x.

    The system should facilitate the planning of physical and social infrastructure including

    xi.

    sewage and solid waste disposal The system should incorporate the development control regulations, zoning regulations

    xii.

    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.

    xiii.

    The system should enable planning of drains and waterfront to be landscaped in the form of interconnected parkways.

    • 5.2 Prepare Annual and Monthly Plans

    i.

    The system should allow the user to prepare annual and monthly plans

    The system should have the provision for incorporating information such as implementing

    ii.

    The system should ensure that the plans and programs are in line with the master plan

    iii.

    The system should enable the creation of specific project proposals and categorization of

    iv.

    the proposals into short and long term. The system should enable the categorization of proposals into mandatory and optional

    v.

    projects

    vi.

    agency, development cost and resource usage for each proposal The system should allow the user to view the planned proposals for each area.

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

    • 5.3 Monitor/Revise Annual and Monthly Plans

    i.

    The system should allow the user to enter the status of each proposal.

    ii.

    The system should allow the user to revise a proposal.

    iii.

    The system should enable the user to view status of each proposal.

    iv.

    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.

    The system should allow the user to view the map of the land acquired by LM

    ii.

    The system should allow the user to overlay the master plan and zonal plans over the

    iii.

    land acquired for planning purpose The system should allow the user to link the plot with a particular zonal plan.

    iv.

    The system should allow the user to develop layout plans for the land acquired in conformance with the zonal plan/master plan.

    v.

    The system should allow the user to view all the related plans for a plot of land and vice versa.

    • 5.5 Prepare Project Schemes and Development Plans for the Project

    i.

    The system should allow the user to define specific project proposals for a plot of land.

    ii.

    The system should ensure that the project is in conformance with the master plan/zonal

    iii.

    plan and land use specification The system should ensure that the project proposal is as per the annual plan

    iv.

    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.

    v.

    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.

    • 5.6 Building Section

    i.

    The system should allow the user to monitor building construction details

    ii.

    The system should allow maintenance of building construction records as per requirements

    • 5.7 Provide various Reports as per requirements of the department

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

    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 & non- hierarchical 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.

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

    Conceptual System Requirement Specification Ver. 1.17 (22-08--06) Delhi Development Authority SRS

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

    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.

    The system should allow the user to view the layout plans for the area on which the

    The system should allow the user to link an outsourced agency (to whom the design has

    ii.

    project is being developed. The system should be able to view the land map and its information on which the project

    iii.

    is being developed The system should allow the user to view the project scheme structural and service

    iv.

    details prepared by engineering The system should allow the user to update the status of the project (during architecture

    v.

    design phase).

    vi.

    been outsourced fully or partially) to a particular project The system should allow the user to view the status of the project (including the

    vii.

    architectural drawings). The system should maintain status of part/full disposal of projects in the Land Disposal

    viii.

    wing The system should allow the user to drill down to a project from the layout plan.

    • 6.2 Prepare Architectural Design

    i.

    The system should be able to integrate with a standard CAD package in order to link the

    ii.

    architectural design drawings with a particular project. The system should have the facility to link the architectural drawings with the layout plans

    iii.

    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.

    • 6.3 Provide various Reports as per requirements of the department

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

    • 6.4 Process map of Architecture Department

    PROJECT Feasibility Study Survey / Measured Drawing Contextual Features Preparation of Conceptual Design & Layout Approval
    PROJECT
    Feasibility Study
    Survey / Measured Drawing
    Contextual Features
    Preparation of Conceptual Design & Layout
    Approval of HOD
    Screening Committee Approval
    DUAC Approval For Commercial & Multi-Story Projects DUHF Approval For All Heritage Projects SMB Approval For
    DUAC Approval For Commercial
    & Multi-Story Projects
    DUHF Approval For All
    Heritage Projects
    SMB Approval For all
    Sports Activity Projects
    Issue of Drawings for Structure Design
    Issue of Drawings for Service & Site
    Development
    Incorporating Struct. Details Preparation of
    Incorporating Service Details
    Working Drawings
    Issue to Engg. Department for Execution
    Issue to Engg. Department for Execution
    Preparation of detailed working Drawings
    Arch. Controls conditions
    Site Coordination
    Revision as Site
    Problem
    Issue of Control Drawings to Land
    Department & Disposal
    Preparation of Development Plan
    2n
    d
    St
    ag
    e
    D
    U
    H
    F
    A
    pp
    ro
    va
    l

    General action format for projects

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

    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 India’s 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.

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

    Conceptual System Requirement Specification Ver. 1.17 (22-08--06) Delhi Development Authority SRS

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

    EXISTING APPLICATIONS

    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.

    Details

    Digitized maps

    Clearly showing lines and demarcations of khasra no.s / plots

    ii.

    Notification: Display of notifications related to the different stages of acquisition

    iii.

    Award: Details of award of compensation

    iv.

    Comparison:

    Intelligent maps wherein users can build and run queries, like area under a particular stage of acquisition

    v.

    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.

    The system should have the facility to receive data pertaining to proposals for

    The system should have the facility to capture field information for surveys entered by the

    ii.

    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

    iii.

    made in the Master Plan The system should provide the facility to overlay other maps (like Khasra maps) on the

    iv.

    Master Plan layouts The system should have facility to capture information received through preliminary

    v.

    surveys

    vi.

    users though GPS technology The system should allow categorizing of physical survey information as per requirements

    vii.

    of DDA The system should maintain physical survey observations area wise

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

    • 8.3 Approval and maintenance of records

    i.

    The system should maintain status of approval of each proposal

    The system should generate custom reports to monitor the details of each proposal along

    ii.

    The system should generate automatic reminders on approvals, which are due with a

    iii.

    reason for a delay in receipt of approvals The system should be able to capture comments in the case of approvals not being

    iv.

    granted to certain proposals The system should maintain a history of unapproved proposals with comments and

    v.

    reasons for the same

    vi.

    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

    vii.

    Building department The system should allow maintaining a list of villages and khasra numbers, area of each

    viii.

    coming under the proposed development / layout plan The system should allow users to attach / link textual information to graphical maps

    • 8.4 Land Acquisition information and progress

    i.

    The system should capture information related to land surveys

    • - Actual area

    • - Name of personnel performing the survey

    • - Any other relevant information

    ii.

    The system should maintain records of draft notifications issued for approval

    iii.

    The system should maintain standard formats for issue of notifications

    iv.

    System should capture the status of issue of notifications

    v.

    System should display maps of land areas with the corresponding status of issue of

    vi.

    notifications for that area The system should maintain status of approval for each notification

    vii.

    The system should capture unapproved notifications with reasons for the same

    viii.

    The system should allow web based receipt of objections from general public to

    ix.

    notifications issued The system should maintain detailed records of compensation to be paid

    x.

    The system should maintain records of unresolved compensation cases along with

    xi.

    reasons for the same The system should allow categorization of unresolved compensation cases

    xii.

    The system should be able to display maps of areas with the categories of unresolved

    xiii.

    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

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

    • 8.5 Compensation

    i.

    The system should be able to capture the compensation paid by DDA against each land

    ii.

    area / plot under relevant heads as defined by DDA The system should allow access to finance department to the compensation paid

    iii.

    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

    iv.

    The system should maintain records of transfer of land by Land Management to user departments

    • 8.6 Web-based functionality

    i.

    The system should allow web-based access to acquired and non-acquired land

    ii.

    The system should display information on the web for area under DDA for development

    iii.

    purposes The system should capture information on compensation paid to land owners and display

    iv.

    it on the web The system should maintain, if required, information on future land acquisition plans

    v.

    The system should allow display of gazette notifications on the web

    vi.

    The system should allow web-based receipt of objections to notifications issued

    • 8.7 Miscellaneous

    i.

    The system should be able to provide a layout wise and if required khasra wise

    ii.

    regularization status with color codes The system should display layout wise and if required khasra wise cluster view

    iii.

    The system should be able to capture city survey number, khasra number and sheet

    iv.

    number The system should be able to generate custom reports based on user defined criteria

    v.

    Provide various Reports as per requirements of the department

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

    • 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

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

    <Engineering Wing> Prepare Zonal Development Plans or Scheme wise plans and send to LM for acquisition
    <Engineering Wing>
    Prepare Zonal
    Development Plans or
    Scheme wise plans and
    send to LM for
    acquisition
    Planning to
    incorporate the
    Architecture
    changes as per
    engineer’s
    observations
    drawing is
    prepared
    Observations are whether
    Hand over to user
    department if
    already acquired
    else start
    acquisition
    process
    Steering Committee
    there is any natural
    obstruction or Hight Tension
    Lline or built up area or
    approves the
    development or specific
    project plan
    encroachment (checked by
    LM but Engg does again as
    sometimes big time lag
    between activities)
    Mark observations
    on the
    Feasibility report
    Receive land
    acquired from LM
    department
    Approval from
    and preliminary
    Prepare Notice
    development plan
    and send it back to
    Planning
    DUAC
    estimate is
    Inviting Tender,
    prepared
    Tender
    Divide work
    according to
    Circles and then
    Divisions, etc.
    Perform physical survey of
    land, physically demarcate
    boundaries
    Sent to Finance
    Wing for
    concurrence and
    Engineer Member
    for admin.
    approval
    Prepare detailed
    Receive Technical
    cost estimates
    Sanction
    Evaluation by
    Works Advisory
    Boarad for > Rs 5
    Cr.
    Project
    Execution
    and
    Monitoring
    EAC accords Admin
    Approval and Expenditure
    Sanction
    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
    Land
    Finance
    Engineering
    Planning
    Management

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

    EXISTING APPLICATIONS

    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.

    System should allow access to the proposal details prepared by the planning department

    The system should maintain an audit trail of comments made by Engineering users

    ii.

    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

    iii.

    department The system should allow marking of observations made by the Engineering Wing during

    iv.

    physical survey of the Land on the development / layout plans The system should allow Engineering Wing to send the development / layout plan to

    v.

    Planning along with the physical observations

    vi.

    The system should enable the observations on the development plan to be viewed by the

    vii.

    Planning The system should maintain records of exchanges of layout / development plans made

    viii.

    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

    ix.

    System should allow access to development plans, maps made by Planning department in the past

    • 9.2 Receive details of Land Acquired

    i.

    The system should have the facility to capture information related to observations made

    ii.

    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

    iii.

    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

    iv.

    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.

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

    v.

    System should allow need based access to this information on reasons for extensions

    vi.

    The system should have the facility to capture status of Fencing of Land

    vii.

    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

    viii.

    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

    ii.

    details of registers 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

    iii.

    Commission 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

    1:500

    1:1000

    User defined Scale

    ii.

    The system should be able to capture foundation system reports on the basis of

    iii.

    recommendations in the Soil Investigation report The system should allow capturing and tracking of requirements for External Consultants

    iv.

    for technical help on preparation of Foundation Systems The system should generate automatic reminders on approval of Layout plans

    v.

    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

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

    vi.

    The system should be able to overlay the circle, division distribution on the land to be

    vii.

    developed The system should allow division of work circle wise and division wise based on decision

    viii.

    made by the Chief Engineer of the concerned Zone The system should be able to maintain standardized formats of feasibility reports System

    ix.

    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

    x.

    The system should be able to allow users to enter history information for each Layout

    xi.

    Plan based on standard formats System should capture date of dispatch of layout plan with comments and history sheet

    xii.

    to Planning department The system should allow access to the altered layout plans made by planning.

    xiii.

    The system should maintain a final version of layout plan after all changes have been

    xiv.

    incorporated, which is totally locked from editing. System should maintain the policies and building bye laws like FAR, coverage, etc. as

    xv.

    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.

    The system should maintain a database of architectural drawings, detailed structural

    The system should allow workflow review and approval of preliminary estimates across

    ii.

    drawings and related data The system should allow preparation of preliminary cost estimates by the engineers

    iii.

    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

    iv.

    defined by DDA from time to time The system should allow simple mathematical calculations and formulas to arrive at the

    v.

    cost estimates

    vi.

    more than one location The system should maintain a checklist of tasks to be done during preparation of

    vii.

    Preliminary Estimates The system should allow work packages to be exchanged between different locations

    viii.

    and officers during the review process with the packages having both spatial and non- spatial 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

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

     

    Assumptions on area calculations

    The system should maintain the following indicative documents in the Work Packages

    A sample format for Administrative Approval and Expenditure Sanction

    The system should maintain a schedule of material quantities required for the project

    Assumptions in total cost calculations

    ix.

    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

    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 Layout Plans

    Any other documents related to preliminary estimate calculation

    x.

    xi.

    The system should automatically calculate the final amounts for each quantity based on

    xii.

    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

    xiii.

    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

    xiv.

    to time The system should allow maintenance of an abstract of all costs

    xv.

    System should have the facility to drill down from the abstract of costs to the schedule of

    xvi.

    quantities The system should maintain standard formulas used for area calculations

    xvii.

    The system should allow workflow based approval of the Work Packages

    xviii.

    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

    xix.

    The system should maintain a database of Administrative Approvals and Expenditure Sanction for reference

    9.7Prepare detailed estimates and technical sanction

    i.

    The system should allow preparation of a detailed cost estimate

    ii.

    The system should have the facility to compute quarter wise quantity of stipulated

    iii.

    materials to be issued to contractor The system should maintain approval hierarchy for technical sanction as per DDA norms

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

    iv.

    The system should allow workflow based Technical sanctions based on project value

    v.

    The system should maintain standard formats for Notice Inviting Tenders, Bid

    vi.

    Comparisons, etc. The system should capture information for comparison of bids received from various

    vii.

    vendors according to pre-defined formats The system should allow access to Finance for scrutiny of the comparatives of tenders

    viii.

    System should capture the status of award of work

    9.8Floating of Tender

     

    i.

    The system should provide the functionality of e-tendering and/or e-procurement

    ii.

    The system should be able to seamlessly integrate with third party e-tendering and/or e- procurement engines

    iii.

    The system should be able to generate reports as required from the third party e- tendering and/or e-procurement engine

    9.9Works Execution and Monitoring

    i.

    The system should have the facility to capture the project plans and proposals submitted

    ii.

    by the prospective contractors, if required The system should be able to capture the details of material (other than stipulated for

    iii.

    issue) required for completion of work The system should be able to capture the details of labor (other than stipulated for issue)

    iv.

    required for completion of work The system should be able to capture the services plan with the status of each

    v.

    The system should monitor progress in specified reporting formats

    Works in preconstruction stage

    Works in progress

    vi.

    The system should support user defined reporting formats as per DDA requirements

    The system should be able to display the areas on which works have not been completed

    vii.

    The system should send automatic communication to the Housing / Land Disposal on

    viii.

    completion of Project The system should be able to display the areas on which development works are being

    ix.

    carried out or have been completed System should have the facility to maintain financial records such as validity of securities,

    x.

    Earnest Money Deposits, etc. for contractors / agencies

    xi.

    within the contract period The system should be able to display development agency and users for plots in the

    xii.

    layout with color codes The system should have the provision to capture the change of users for a given land

    xiii.

    area and maintain the history of change of users The system should have a provision to maintain Inventory / Utilization of Lands

    xiv.

    The system should have a provision to print the layout plan of an area with index and in the required format

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

    xv.

    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.

    xvi.

    The system should allow preparation of actual works expenditure at the end of the work

    xvii.

    System should capture the information on work types in hand under each zone, circle

    xviii.

    and division System should have the facility to display location wise work types in hand

    xix.

    The system should have the facility to display prevalent market rates of various building

    xx.

    materials System should be able to maintain quality control elements

    xxi.

    System should be able to maintain records of instructions issued by EM, CE(QC), CTE

    xxii.

    and any other authority as specified System should have the facility to display Engineers incharge of various works / pockets

    xxiii.

    System should be able to maintain details of commercial property

    9.10

    Works Budgeting and Finance related functionality

    i.

    The system should allow budgeting activity to be carried out on an annual basis with a

    The system should allow engineering department to access approval details and status of

    The system should support workflow based approvals of budgets by Head Office

    ii.

    mid-year review The system should allow maintenance of scheme wise budget under expenditure and

    iii.

    receipt heads The system should aggregate budget received from divisions into Circle wise

    iv.

    The system should automatically generate reminders and allow select users at

    v.

    Headquarters to access Zone wise estimates

    vi.

    budget for each work / scheme System should allow a mid year review of budget and preparation of a revised estimates

    vii.

    The system should allow re-appropriation of budget based on revised requirements

    viii.

    The system should allow scrutiny of justification of financials / comparative statements,

    ix.

    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

    x.

    by DDA

    xi.

    The system should allow recommendations for changes from Head Office to be cascaded

    xii.

    down to zones, circles and divisions The system should be able to calculate the revenue that has been generated from a

    xiii.

    layout The system should allow aggregation of details of court cases from divisions, circles into

    xiv.

    zones The system should allow sharing of these details with the head office

    xv.

    The system should maintain a list of division wise pending cases, contempt cases and cases where some action is pending from DDA side

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

    xvi.

    The system should maintain list of audit paragraphs with comments from external

    xvii.

    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

    9.11

    Project Accounting

    i.

    The system should allow complete monitoring of works costing above Rs. 10 Lakhs up to

    The system should maintain records of handing over of services to Civic agencies

    ii.

    finalizing of bill The system should maintain records of bills approved and paid to contractors

    iii.

    The system should allow preparation of actual and estimated project expenditure for each

    iv.

    scheme / work The system should allow recording of information on expenditure incurred on

    v.

    maintenance of colonies

    vi.

    The system should capture the expenditure on salaries of employees for each zone

    vii.

    The system should maintain records of General Provident Fund accounts of all

    viii.

    employees for each zone The system should automatically calculate the Income Tax liabilities for employees and

    ix.

    include it in the salary calculations The system should maintain a monthly account of all expenditures incurred within a zone

    x.

    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)

    xi.

    The system should maintain audit trail of bill approvals granted and the approval authority

    xii.

    for each The system should allow aggregation of bills paid under a particular work / scheme at any

    xiii.

    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

    xiv.

    made to contractors The system should maintain details of material bills

    xv.

    The system should maintain records of approvals granted to the material bills

    xvi.

    The system should generate a list of pending bills with reason for the same

    xvii.

    The system should be able to capture the expenditure incurred on each work / scheme

    xviii.

    The system should be able to display the progress of works layout plan wise with different

    xix.

    color codes The system should have the facility to maintain annual theft and losses as per user

    xx.

    defined formats The system shall maintain the GIS/details of all underground services with complete particulars of levels, sizes, etc.

    xxi.

    Working of justification of rates on the basis of Delhi Analysis of Rates (DAR) of CPWD &

    current rates approved in DDA.

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

    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.

    The system should monitor court cases relating to arbitration matters, matters of

    The system should capture reports, photographs received from engineers, patwaris, etc.

    ii.

    administration and other issues not directly related to project The system should support monitoring and disposal of observations of Quality Control

    iii.

    cases The system should maintain records of replies to Audit Paras of the Internal / External

    iv.

    audit of works in Zones The system should be able to maintain records of receipt / disposal of Public Grievances

    v.

    references

    vi.

    on land encroachment, misuse of properties, unauthorized construction, etc. The system should capture the standard formats for preparation of demolition plan

    vii.

    The system should allow automatic communication to concerned officers on receipt of an

    viii.

    encroachment report The system should maintain standard formats for preparing request letters as preparation

    ix.

    for the demolition plan The system should maintain a list of third party contractors and the standard equipment required for the demolition

    x.

    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

     

    9.13

    Web based access

    i.

    The system should allow display of Notice Inviting tenders on the internet

    The system should allow web based access to relevant details of each of the schemes /

    ii.

    The system should allow prospective vendors to download forms through the internet

    iii.

    The system should display results of award of work on the internet if required

    iv.

    The system should allow web based access to all current schemes / works being carried

    v.

    out under each division

    vi.

    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

    • 9.14 Provide various Reports as per requirements of the department

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

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

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

    Conceptual System Requirement Specification Ver. 1.17 (22-08--06) Delhi Development Authority SRS

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

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

    EXISTING APPLICATION

    • 10.1 Existing application functionality

    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. Allotment, with following steps Attach program Attach Scheme Attach property After doing the above three, get a Program No. Define draw parameters

    ii.

    iii.

    Perform draw Program Completion Allotment Rohini Lease

    iv.

    Lease / Conveyance deed form Auto capture of data to fill up form This module is used to a lesser extent Registration

    • v. Cash Management Demand File data loading (to import files) Property License

    vi.

    vii.

    viii.

    ix.

    • x. Master Online Post allotment Security

    xi.

    xii.

    xiii.

    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 Integration with other departments

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

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

    ii.

    System should allow access to reports on encroachments/unauthorized construction

    iii.

    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

    iv.

    Management department (Enforcement Branch). System should maintain records and status of clearances received from the Land

    Management department for upcoming notifications:

    No encroachment clearance Results of physical surveys performed

    Details of disputed land areas

    v.

    System should ensure receipt of information from engineering wing on availability of

    vi.

    shops and plots for disposal System should allow access to calculation of ground rents, misuse charges, etc. made by

    vii.

    Finance department System should allow access to progress status of calculation of charges made by

    viii.

    Finance department Standard Cost prepared by Land Costing should be available on the system

    • 10.3 Float Scheme for residential, commercial and/or institutional allotment

    i.

    System should maintain standard formats for Scheme Notifications with details like

    System should ensure that records of scheme notifications are maintained

    ii.

    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

    iii.

    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

    iv.

    applicants as per government rules for allotment Provide for associating a priority number for each plot/commercial property in the scheme

    v.

    based on list of waiting registrants, reservation of the plot/commercial property, etc

    vi.

    System should be able to maintain list of banks associated with the scheme along with

    vii.

    bank details System should be able to maintain details of brochures issued for a particular scheme including brochure cost

    viii.

    System should be able to maintain details of number of brochures issued to various sales counters/banks for a particular scheme

    • 10.4 Receive Application form and Registration Money from Banks

    i.

    Maintain standard formats of application forms for housing schemes

    ii.

    Provide for importing soft copy of applicant data received from banks

    iii.

    Maintain check list and status of documents submitted by applicants

    iv.

    Maintain list of documents to be supplied by allottee for issue of possession letter

    v.

    Generate letter of deficiencies on the basis of check list of documents submitted by

    vi.

    alottee Provide for verification and correction of applicant data (with physical application forms)

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

    vii.

    Maintain applicant details for each scheme such as Applicant Name, Application Form

    viii.

    No., Scheme Name, Address etc Maintain details of registration money received applicant wise/bank wise/scheme wise

    10.5

    Allotment of Land/Shops by auction, tender, computerized draw, reserved price

    i.

    System should have the policy of auctions, allotments, etc. available for access on the

    ii.

    computer to internal users of DDA System should ensure receipt of information from engineering wing on availability of plots

    iii.

    for disposal System should generate notifications for inviting applications according to pre-decided

    iv.

    eligibility norms normally and through the website System should have the facility for automated check printing

    v.

    System should allow tender/auction of plots and shops based on random location as and

    vi.

    when information is received from Engineering Wing The system should generate reports of plot wise/applicant wise allotments

    vii.

    The system should maintain details of plots/commercial allotted against each successful

    viii.

    applicant The system should maintain list of un-allotted plots/commercial properties scheme wise.

    ix.

    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

    10.6

    Allotment of Land as compensation to Rohini Registrants and GH Societies

    i.

    System should allow for registration for allotment under the alternate allotment scheme

    ii.

    System should allow for allotment of land as allotment recommendation from L&B

    iii.

    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

    iv.

    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

    v.

    System should allow of the alternate allotments only in new upcoming schemes

    vi.

    System should ensure further processing through the usual process

    x.

    System should allow for payment of Ground rent in case of societies under:

    • a. By societies

    • b. By allottees

    • 10.7 Allotment of shops under reserved categories and staff orders

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

     

    i.

    System should be able to allow allotment of shops based on pre-defined rules as per

    ii.

    reservation policy made for special categories System should maintain a list of special categories and the amount of reservation allowed

    iii.

    against each category System should be able to update the reservation policy from time to time

    iv.

    System should maintain the status of allotment made under registration with details of numbers allotted against numbers available

    10.8

    Monitoring and Disposal of Petrol pumps, gas godowns, CNG station sites

    i.

    System should be able to maintain records of petrol pumps disposed with names of party

    ii.

    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

    iii.

    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

    iv.

    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.

    10.9

    Monitoring and Disposal of commercial built up properties and licensed units

    v.

    System should be able to maintain records of disposal of commercial built up properties

    System should be able to maintain records through user-defined parameters

    vi.

    like shops, restaurants, offices, etc. System should be able to segregate records of commercial built up properties on the

    vii.

    basis of types of usage System should be able to maintain records of Parking contracts, taxi stand sites and

    viii.

    licensed units in market complexes System should be able to generate reports on license fee due, received and date of

    ix.

    payment, for licensed units and properties System should be able to maintain records of agencies handling the operations of

    x.

    licensed units with details of manager in-charge of the location, his contact numbers, etc.

    xi.

    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.

    10.10

    Issue of demand letter

     

    i.

    System should generate demand letters to the successful allottee

    ii.

    System should maintain standard formats for Demand Letters, Possession Letters,

    iii.

    Conveyance Deed, etc. System should have the facility to enter ground rent payment and lease execution in case the allotment is made to societies

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

    iv.

    System should have the facility to categorize allotee into One time payees, Installment Payees, etc.

    • 10.11 Receive Payment Details from Banks

    i.

    The system should have facility to import soft copy of payment details received from

    ii.

    banks The system should be able to generate discrepancy report allottee wise against

    iii.

    payments received from banks The system should allow for manual verification and correction of discrepancy cases with

    iv.

    proper safeguards The system should track payments received allottee wise and generate exception reports

    v.

    The system should have facility to generate notifications to appropriate users in case of

    vi.

    late payment or non payments System should automatically update information for each allotee related to his past

    vii.

    submittals of installments and verification of payments System should maintain complete history of payments made by allotee at all times

    viii.

    The system should have facility to generate defaulter list and generate e-mail/print

    ix.

    notifications to appropriate users The system should have facility to generate reminder letters for defaulters.

    x.

    The system should generate reports on payments received/balance allottee / agency

    xi.

    wise The system should have provision for cancellation of allotment in case of default.

    10.12

    Payment, Possession Letter, Conversion to Freehold

    xii.

    System should allow entry of data related to receipt of payments according to conditions

    xiii.

    in Demand Letter System should generate alerts on any irregularities (installment missed, wrong amount

    xiv.

    paid, etc.) for each allotee System should ensure issue of possession letters on complete payments made by allotee

    xv.

    System should be able to generate information on missing payments, fines, etc. to be

    xvi.

    imposed on the allotee System should have facility to enter application details for execution of Conveyance deed

    xvii.

    System should have the facility to enter application details for conversion from leasehold

    xviii.

    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

    xix.

    System should be able to generate the outstanding dues of allotee

    xx.

    System should have the facility to verify whether the allotee has made all payments

    xxi.

    System should allow the user to approve conversion only after receipt of all dues from the

    xxii.

    applicant / allotee System should have inbuilt checks and verifications to ensure all conditions related to execution of deed have been met

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

    • 10.13 Perform transfer of property and mutation related activities

    i.

    System should incorporate the mutation process under different categories:

    Change of ownership

    Sale of Land

    Death of the owner

    Other categories

    ii.

    System should allow receipt of application for mutation

    iii.

    System should maintain standard formats for notifications, letters, etc. and be able to

    iv.

    print copies of the same System should allow for maintaining the records of progress of legal proceedings

    v.

    System should maintain the final record of mutation performed with details of:

    Reason for mutation

    Resulting Change

    vi.

    System should allow for performing construction related activities, like time extension, conversion to free hold, etc.

    10.14

    Relocation/Redevelopment of Commercial Areas

    i.

    System should be able to maintain records of rehabilitated markets / industries, old

    ii.

    location, current location, date of shifting, duration of shifting, agency, etc. System should be able to capture complaints, grievances received from concerned

    iii.

    parties on the rehabilitation process System should maintain records of court orders, committee orders passed in relation to

    iv.

    rehabilitation of industries, markets, etc. System should have facility to enter rehabilitation plans

    v.

    System should be able to capture details of execution against plan and reasons for delay

    vi.

    in execution if any System should have facility to enter redevelopment plans and details

    vii.

    System should maintain records for monitoring of consultants appointed for drawing redevelopment plans with relevant details of past performance, financial data, etc.

    viii.

    System should be able to generate reports on rehabilitations executed within a specific period as defined by the user

    • 10.15 Maintain records of Legal cases and Applications received from citizens

    i.

    System should maintain records of Legal cases with details of status, last update, subject

    ii.

    of case, relevant dates, etc. System should be able to classify cases according to user defined subject matters for

    iii.

    easy reference to case decisions System should be able to generate reports on current cases, cases disposed off, etc.

    iv.

    System should be able to maintain entire case history based on user defined parameters

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

     

    v.

    System should be able to generate alerts /reminders on case meetings to appropriate

    vi.

    personnel responsible for attending the case hearing System should be able to maintain records of applications received from citizens

    vii.

    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

    10.16

    Web-based functionality

    viii.

    System should allow receipt of complaints from general public on misuse of residential

    System should maintain the policies related to auction, allotment of land available to the

    ix.

    premises for other purposes System should allow forwarding of these complaints to appropriate department / authority

    x.

    within DDA for further action

    xi.

    general public for download through the Internet System should display notifications for general public and allow download of notification

    xii.

    from the internet System design should make adequate arrangements for integration with online auction

    xiii.

    sites for auction of plots System design should make adequate arrangement for integration with bank databases

    xiv.

    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

    xv.

    Banks on money deposited by Allotee System should allow creation of new schemes as per requirements of Land Disposal

    xvi.

    department System should maintain the updated records of applicants for all schemes

    xvii.

    System should ensure that any changes made in the applicants’ data are informed

    xviii.

    automatically to appropriate authority System should ensure that periodic alerts are generated to appropriate authority for

    xix.

    maintenance of data System should allow generation of new schemes as defined by DDA from time to time

    xx.

    System should ensure that a list of applicants is maintained for transfer of unsuccessful

    xxi.

    applicant names to upcoming schemes System should allow generation of alert and automatic cancellation of applicant name

    xxii.

    from list on allotment System should provide appropriate authority with the facility to delete applicant names

    xxiii.

    from the list System should maintain audit trail on any changes made in the applicants’ database

    10.17

    Provide various Reports as per requirements of the department

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

    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. Housing Scheme Management

    • 2. Lease Administration

    • 3. Housing Enforcement

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

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

    Housing Scheme Management Receive Receive Prepare list details of Applications and Conduct of alottees constructed Float
    Housing Scheme Management
    Receive
    Receive
    Prepare list
    details of
    Applications and
    Conduct
    of alottees
    constructed
    Float a Housing
    Scheme
    Registration
    Verify Applications
    and enter into
    System
    Computerized
    and
    Issue Demand
    Letters to allottees
    flats from
    Money
    Draw
    unsuccesful
    Engg
    applicants
    Purchase Scheme
    Brochure
    Receive Refund of
    Registration
    Money
    Receive
    Receive
    Application form
    Consolidate All
    allottee/refund
    and Registration
    applications and
    applicant list
    money
    payments
    and refund
    cheque
    Prepare
    Consolidated
    cheque for refund
    amount bank wise
    Prepare Costing of
    flats (Land
    Premium plus
    Housing Cost)
    Calculate Demand
    and installments(in
    case of Hire
    Purchase)
    Housing
    Housing Mgmnt
    Banks
    Customer
    Finance
    Section

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

    Housing Scheme Management Scrutinise the Prepare Posession supporting Docs OK Letter documents Execute Conveyance Deed and
    Housing Scheme Management
    Scrutinise the
    Prepare Posession
    supporting
    Docs OK
    Letter
    documents
    Execute
    Conveyance Deed
    and hand original
    CD to alottee
    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
    Receive Posesion
    Take posession of
    Demand letter
    Letter
    from DDA
    flat and intimate
    DDA
    Yes
    Yes
    Receive Full
    Payment for Cash
    Down purchases,
    First Installment
    for HP cases from
    Customer
    No
    Receive Payment
    Details and
    Verify Challan
    All Payments
    Challan from
    Payments made
    made?
    Banks
    Receive Copy of
    Posession Letter
    Hand over
    Posession and
    inform Housing
    Housing
    Housing Mgmnt
    Engineering
    Banks
    Customer
    Finance
    Section

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

    Housing Lease Administration Receive Receive 1 Copy of CD Retreive original application from outstanding Approve file
    Housing Lease Administration
    Receive
    Receive
    1 Copy of
    CD
    Retreive original
    application from
    outstanding
    Approve
    file from
    Dues < 5000
    Yes
    bank
    dues details
    Application
    retained in Original
    File
    concerned section
    from HF
    No
    Receive letter on
    outstanding dues
    Receive approval
    letter and CD
    Pay Stamp Duty
    Receive
    Application for
    conversion to free
    hold
    Receive payment
    from customer
    Receive original
    file and application
    from LAB
    Check
    Outstanding dues
    Receive payment
    details from Bank
    if any
    Register the CD in
    favour of applicant
    Lease
    Housing
    Sub Registrar
    Banks
    Customer
    Administration
    Finance
    Branch

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

    Housing Enforcement Inform MCD of violation Receive Issue Show cause complaints on violations from Notified area
    Housing Enforcement
    Inform MCD of violation
    Receive
    Issue Show cause
    complaints on
    violations from
    Notified area of
    DDA
    Yes
    Inform concerned
    JE to check the
    violation
    Approve
    notice under Sec
    No
    Regularisation
    30/31
    public
    Receive reply to
    show cause/
    application for
    regularisation
    Initiate action for
    demolition/Inform
    LAB for
    cancellation of
    lease
    Violation report
    checked by JE
    Yes
    Apply for
    Receive Show
    regularisation as
    cause notice
    per DDA
    procedure
    Housing
    House Owner
    Engineering
    Enforcement

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

    Housing Services Aplply to DDA for a service (mutation, change of address etc) Receive letter regarding
    Housing Services
    Aplply to DDA for
    a service
    (mutation, change
    of address etc)
    Receive letter
    regarding
    Receive approval
    incomplete
    letter
    documentation
    Receive
    application form
    from Applicant
    Enter applicant
    details in system,
    issue
    acknowledgement
    letter
    No
    Receive
    application form
    Approve
    Verify the
    and supporting
    Docs OK?
    Yes
    application, update
    documents
    documents
    file
    Housing
    DDA Counter
    Applicant

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

    EXISTING APPLICATIONS

    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 Existing application functionality

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

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

    • 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 Housing Scheme Management

    11.2

    11.3

    11.4

    Receive details of flats available from Engineering

    i.

    The system should maintain complete list of flats which are available/under construction

    ii.

    The system should maintain all details of a flat like zone, address, flat category etc

    iii.

    Interface with engineering module to obtain status of a flat and relevant details

    iv.

    The system should enable the user to estimate the likely available date of a flat (date of completion of construction of the flat)

    v.

    Provide various Reports as per requirements of the department

    11.5

    Float a Housing Scheme

    xi.

    Scheme Name, Date of inception, Date of Draw, Date of closure etc

    xii.

    Provide for associating a flat with a particular scheme. Ensure that a flat is associated

    xiii.

    only with one scheme at a time Provide for reservation of a flat for a particular category of applicants eg ground floor flats

    xiv.

    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

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

    xv.

    Maintain list of banks associated with the scheme along with bank details

    xvi.

    Maintain details of brochures issued for a particular scheme including brochure cost

    xvii.

    Maintain details of number of brochures issued to various sales counters/banks for a particular scheme

    • 11.6 Receive Application form and Registration Money from Banks

    ix.

    Maintain standard formats of application forms for housing schemes

    x.

    Provide for importing soft copy of applicant data received from banks

    xi.

    Provide for verification and correction of applicant data (with physical application forms)

    xii.

    Maintain applicant details for each scheme such as Applicant Name, Application Form

    xiii.

    No., Scheme Name, Address etc Maintain details of registration money received applicant wise/bank wise/scheme wise

    • 11.7 Conduct Computerized Draw

    xviii.

    The system should allow conducting of computerized random draw for allotments

    xix.

    The system should allow pre-defined criteria for the draw

    xx.

    The system should allow sorting and random shuffling of flats and applicants and

    xxi.

    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.

    xxii.

    The system should generate reports of flat wise/applicant wise allotments

    xxiii.

    The system should maintain details of flats allotted against each successful allotee

    xxiv.

    The system should maintain list of un-allotted flats scheme wise. These should be available for allotment under a different scheme

    xxv.

    The system should allow for generation of a soft copy of successful/unsuccessful applicant details for hand over to banks

    • 11.8 Prepare Consolidated Refund Cheques Bank wise

    i.

    The system should automatically calculate the refund amount for each scheme bank wise

    ii.

    for all banks associated with the scheme The system should provide for automated cheques printing facility with proper

    iii.

    authorization The system should generate reports of refund money bank wise and applicant wise.

    iv.

    The system should allow generation of a soft copy of refund amount bank wise and applicant wise for hand over to banks

    • 11.9 Calculate Housing Cost and Demand

    i.

    The system should interface with costing module for obtaining relevant costing data

    ii.

    The system should import land premium and housing construction cost data from costing module

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

     

    iii.

    The system should be able to calculate plinth area rates on a half yearly basis by using

    iv.