Request for Proposal - HSVP

Request for Proposal Selection of System Integrator for the Up-

Gradation / Development and Maintenance

of HUDA Application

RFP Reference no GM(IT)/RP/HUDA/2017/45413

RFP for Selection of System Integrator for the Up-Gradation / Development and Maintenance of HUDA Application

2 | P a g e

CONTENTS

1. INSTRUCTIONS TO BIDDERS ..................................................................................................................................... 13

1.1 USE OF RFP DOCUMENT & OTHER INFORMATION ........................................................... 13

1.2 RIGHT TO REJECT ALL OR ANY PROPOSAL ................................................................... 13

1.3 INTRODUCTION ............................................................................................................. 14

1.4 CLARIFICATIONS/AMENDMENTS & PRE-BID MEETING ..................................................... 15

1.5 PREPARATION OF PROPOSAL ....................................................................................... 16

1.6 SUBMISSION, RECEIPT AND OPENING OF PROPOSALS .................................................... 17

1.7 INSTRUCTIONS TO BIDDERS FOR E-TENDERING ............................................................. 18

2. PROPOSAL EVALUATION ............................................................................................................................................ 21

2.1 PRE-QUALIFICATION CRITERIA ..................................................................................... 21

2.2 TECHNICAL EVALUATION CRITERIA ............................................................................... 24

2.3 EVALUATION OF PRE-QUALIFICATION BIDS ................................................................... 30

2.4 TECHNICAL EVALUATION PROCESS .............................................................................. 30

2.5 FINANCIAL EVALUATION PROCESS ................................................................................ 30

2.6 FINAL EVALUATION ...................................................................................................... 31

2.7 AWARD OF CONTRACT ................................................................................................. 32

2.8 PERFORMANCE BANK GUARANTEE (PBG) .................................................................... 32

3. PROJECT PROFILE ......................................................................................................................................................... 33

3.1 TOTAL NUMBER OF CURRENT HUDA USERS & OFFICES ................................................ 34

3.2 HUDA CITIZEN WEB PORTAL ....................................................................................... 34

3.3 PLOT AND PROPERTY MANAGEMENT SYSTEM (PPM) & FINANCIAL ACCOUNTING SYSTEM

(FAS) 36

3.4 COURT CASE TRACKING SYSTEM (CCTS) ..................................................................... 39

4. SCOPE OF WORK ............................................................................................................................................................ 41

4.1 PROPOSED LOGICAL ARCHITECTURE OF THE HUDA APPLICATIONS ............................... 41

4.2 ARCHITECTURE GUIDELINES ......................................................................................... 47


3 | P a g e

4.3 FUNCTIONAL REQUIREMENTS OF THE MODULES............................................................. 48

4.4 MOBILE APPLICATION DEVELOPMENT ........................................................................... 48

4.5 APPLICATION DEVELOPMENT ........................................................................................ 49

4.6 OPERATIONS AND MAINTENANCE (POST GO-LIVE AMC)- PART B .................................. 57

4.7 TIMELINES & MILESTONES ............................................................................................ 60

4.8 PAYMENT SCHEDULE ................................................................................................... 63

4.9 SERVICE LEVEL AGREEMENT ........................................................................................ 65

5. GENERAL CONDITIONS OF CONTRACT .................................................................................................................. 71

5.1 USE AND ACQUISITION OF ASSETS ................................................................................ 71

5.2 ACCESS TO THE DEPARTMENT’S OR IT’S NOMINATED AGENCIES’ LOCATION ................... 72

5.3 MEASUREMENTS AND ARITHMETIC CONVENTIONS ......................................................... 72

5.4 CONFIDENTIALITY ........................................................................................................ 72

5.5 DATA PROTECTION ...................................................................................................... 73

5.6 CONFLICT OF INTEREST ................................................................................................ 73

5.7 FRAUD & CORRUPTION ................................................................................................ 73

5.8 TAX ............................................................................................................................. 74

5.9 LIQUIDATED DAMAGES ................................................................................................. 75

5.10 PENALTIES .................................................................................................................. 75

5.11 INDEMNITY ................................................................................................................... 75

5.12 LIMITATION OF LIABILITY .............................................................................................. 75

5.13 PERSONNEL ................................................................................................................ 76

5.14 INTELLECTUAL PROPERTY RIGHTS ................................................................................ 77

5.15 TRADEMARKS, PUBLICITY............................................................................................. 79

5.16 FORFEITURE OF EARNEST MONEY ................................................................................ 79

5.17 FORCE MAJEURE ......................................................................................................... 79

5.18 TERMINATION .............................................................................................................. 81


4 | P a g e

5.19 EFFECTS OF TERMINATION ........................................................................................... 82

5.20 DISPUTES RESOLUTION ................................................................................................ 82

5.21 CHANGE CONTROL PROCEDURE ................................................................................... 83

5.22 TRANSITION & EXIT MANAGEMENT................................................................................ 85

5.23 MISCELLANEOUS ......................................................................................................... 89

6. FORMS AND FORMATS ................................................................................................................................................ 90

6.1 ADDITIONAL INFORMATION RELATED TOTHE PROJECT .................................... 90

6.2 FORM 1 - COVERING LETTER – TENDER DOCUMENT (FORMAT) ..................................... 91

6.3 FORM 2 - FORMAT FOR LAST 5 YEARS PROVIDING IT SERVICES .................................... 93

6.4 FORM 3- DECLARATION THAT THE VENDOR HAS NOT BEEN BLACKLISTED ...................... 94

6.5 FORM 4 - FINANCIAL TURNOVER FORMAT .................................................................... 95

6.6 FORM 5 - FORMAT FOR CITATIONS ............................................................................... 96

6.7 FORM 6 - DECLARATION FOR NO CONSORTIUM OR SUB-CONTRACTING.......................... 97

6.8 FORM 7 - (SUGGESTED FORMAT OF CURRICULUM VITAE (CV) FOR PROJECT

STAFF) ................................................................................................................................. 98

6.9 FORM 8 - (FINANCIAL PROPOSAL SUBMISSION FORM) ..................................... 100

6.10 FORM 9 - CHANGE CONTROL NOTE FORMATS ............................................................ 102

6.11 FORM 10 - FORMAT FOR PRE-BID CLARIFICATIONS .................................................... 105

6.12 ABBREVIATIONS .................................................................................................... 106

ANNEXURES ........................................................................................................................................................................... 107

7. ANNEXURE A - FUNCTIONAL REQUIREMENTS FOR FAS MODULE ............................................................ 107

7.1 MAINTAIN BANK MASTER ........................................................................................... 107

7.2 MAINTAIN BANK BRANCH MASTER ............................................................................. 107

7.3 MAINTAIN OFFICE MASTER ......................................................................................... 107

7.4 MAINTAIN FINANCIAL YEAR MASTER ........................................................................... 108

7.5 MAINTAIN CHEQUE CONTROL REGISTER ..................................................................... 108

7.6 MAINTAIN FDR DETAILS ............................................................................................. 109


5 | P a g e

7.7 MAINTAIN VOUCHER DETAILS ..................................................................................... 109

7.8 MAINTAIN GL AND SL HEADS MASTER ....................................................................... 113

7.9 MAINTAIN TAX MASTER .............................................................................................. 114

7.10 MAINTAIN LOANS DETAILS ......................................................................................... 114

7.11 MAINTAIN PARTY/ SUPPLIER/ CONTRACTOR MASTER .................................................. 114

7.12 MAINTAIN ESTIMATES ................................................................................................ 115

7.13 MAINTAIN WORKS CATEGORY MASTER ....................................................................... 115

7.14 MAINTAIN WORKS MASTER ........................................................................................ 116

7.15 MAINTAIN SALE OF TENDER FORM .............................................................................. 116

7.16 MAINTAIN TENDER/ QUOTATION SUBMISSION .............................................................. 116

7.17 OPEN TENDER ........................................................................................................... 117

7.18 AWARD TENDER ........................................................................................................ 117

7.19 MAINTAIN MB REGISTER ............................................................................................ 117

7.20 MAINTAIN CONTACTOR BILL ENTRY ............................................................................ 117

7.21 CLUBBING CONTRACTOR BILLS .................................................................................. 118

7.22 MAINTAIN PPM RECEIPT DETAILS .............................................................................. 118

7.23 CLUB PPM RECEIPT .................................................................................................. 118

7.24 LAC DETAILS ............................................................................................................ 119

7.25 LAC ACQUISITION MASTER ........................................................................................ 119

7.26 LAC PAYMENT DETAILS ............................................................................................. 119

7.27 MAINTAIN ENHANCED COMPENSATION ........................................................................ 120

7.28 MAINTAIN AND REVISE BUDGET .................................................................................. 120

7.29 MAINTAIN FIXED ASSETS CATEGORY MASTER ............................................................. 121

7.30 MAINTAIN FIXED ASSET BLOCK MASTER ..................................................................... 121

7.31 MAINTAIN FIXED ASSET .............................................................................................. 121

7.32 MAINTAIN FIXED ASSET DEPRECIATION RATE MASTER ................................................ 121


6 | P a g e

7.33 DEPRECIATION CALCULATION OF FIXED ASSETS ......................................................... 122

7.34 MAINTAIN FIXED ASSET SALE ..................................................................................... 122

7.35 MAINTAIN FIXED ASSET WRITE OFF ............................................................................ 122

7.36 MAINTAIN TRANSFER OF FIXED ASSETS ...................................................................... 123

7.37 MAINTAIN PARTY BILL ENTRY ..................................................................................... 123

7.38 CLUB PARTY BILLS .................................................................................................... 123

7.39 MAINTAIN PAYROLL DATA .......................................................................................... 124

7.40 GENERATE CREDIT DEBIT NOTE ................................................................................. 124

7.41 VIEW DEBIT NOTE ...................................................................................................... 124

7.42 VIEW CREDIT NOTE .................................................................................................... 124

7.43 UPLOAD BANK STATEMENT DETAILS .......................................................................... 125

7.44 ENTER BANK STATEMENT DETAILS ............................................................................. 125

7.45 PERFORM SYSTEM RECONCILIATION ........................................................................... 125

7.46 PERFORM MANUAL RECONCILIATION .......................................................................... 126

7.47 UPDATE BANK STATEMENT DETAILS .......................................................................... 126

7.48 UPDATE VOUCHER CHEQUE DETAILS .......................................................................... 126

7.49 REFUND OF SECURITY ................................................................................................ 127

7.50 CALCULATION OF SECTOR COSTS ............................................................................... 127

7.51 MAINTAIN TDS DETAILS ............................................................................................. 127

7.52 SCHEDULE MASTER ................................................................................................... 128

7.53 BSPL SCHEDULE DETAILS ......................................................................................... 128

7.54 DE CLUBBING OF BILLS .............................................................................................. 128

7.55 MAINTAIN SYSTEM PARAMETERS ................................................................................ 129

7.56 EXTERNAL INTERFACES .............................................................................................. 129

7.57 USER ACCESS CONTROL AND SECURITY ..................................................................... 130

7.58 FAS REPORTS ........................................................................................................... 130


7 | P a g e

8. ANNEXURE B - FUNCTIONAL REQUIREMENTS PPM MODULE .................................................................... 132

8.1 MAINTAIN ZONE MASTER............................................................................................ 132

8.2 MAINTAIN ESTATE OFFICE MASTER ............................................................................ 132

8.3 MAINTAIN URBAN ESTATE MASTER ............................................................................ 133

8.4 MAINTAIN PROPERTY CATEGORY MASTER .................................................................. 133

8.5 MAINTAIN PROPERTY SUB CATEGORY MASTER ........................................................... 133

8.6 MAINTAIN INTEREST RATES ........................................................................................ 135

8.7 MAINTAIN FEE MASTER .............................................................................................. 135

8.8 MAINTAIN SURCHARGE MASTER ................................................................................. 136

8.9 MAINTAIN ADVOCATE MASTER ................................................................................... 138

8.10 MAINTAIN RESERVATION CATEGORY MASTER ............................................................. 138

8.11 MAINTAIN COMPOUNDABLE VIOLATION MASTER.......................................................... 139

8.12 MAINTAIN PROCEDURE/PROCESS MASTER .................................................................. 139

8.13 MAINTAIN SECTOR MASTER ....................................................................................... 140

8.14 MAINTAIN ACQUISITION DETAILS ................................................................................ 141

8.15 MAINTAIN PROPERTY DETAILS.................................................................................... 142

8.16 MAINTAIN FLOATATION SCHEME ................................................................................. 143

8.17 MAINTAIN APPLICATION REGISTRATIONS .................................................................... 144

8.18 MAINTAIN DRAW RESULTS ......................................................................................... 145

8.19 ALLOTMENT OF PROPERTY ......................................................................................... 145

8.20 GENERATE REFUND ORDER ....................................................................................... 152

8.21 MAINTAIN APPLICATIONS RECEIVED ........................................................................... 153

8.22 TRANSFER OF PROPERTY ........................................................................................... 154

8.23 MORTGAGE PERMISSION APPLICATION APPROVAL ...................................................... 156

8.24 GENERIC APPLICATION APPROVAL ............................................................................. 157

8.25 SURRENDER OF PROPERTY ........................................................................................ 158


8 | P a g e

8.26 RESTORATION OF PROPERTY...................................................................................... 159

8.27 WAIVING OF CHARGES ............................................................................................... 159

8.28 ALLOTMENT OF ALTERNATE PLOT .............................................................................. 160

8.29 GENERAL PROCEDURES INVOLVED IN PLOT AND PROPERTY MANAGEMENT .................. 160

8.30 MONITOR COURT CASES ............................................................................................ 162

8.31 MONITOR APPEALS .................................................................................................... 162

8.32 PUBLIC WEBSITE DATA .............................................................................................. 163

8.33 EXTERNAL INTERFACE SPECIFICATIONS ...................................................................... 163

8.34 USER ACCESS CONTROL AND SECURITY ..................................................................... 165

8.35 REPORTS .................................................................................................................. 165

9. ANNEXURE C - FUNCTIONAL REQUIREMENTS WEB PORTAL MODULE .................................................. 167

9.1 STATIC CONTENT LIST: .............................................................................................. 167

9.2 DYNAMIC CONTENT LIST ............................................................................................ 168

10. ANNEXURE D - FUNCTIONAL REQUIREMENTS OF CCTS MODULE ....................................................... 174

10.1 APPLICATION USER MASTER ...................................................................................... 174

10.2 CASE TYPE MASTER .................................................................................................. 175

10.3 URBAN ESTATE MASTER ............................................................................................ 176

10.4 SECTOR MASTER ....................................................................................................... 177

10.5 PROPERTY CATEGORY MASTER ................................................................................. 177

10.6 COURT CASE NATURE MASTER .................................................................................. 178

10.7 COURTS MASTER ....................................................................................................... 178

10.8 COURTS LOCATION MASTER ...................................................................................... 179

10.9 HUDA OFFICES MASTER ........................................................................................... 180

10.10 ADVOCATE MASTER ................................................................................................... 180

10.11 COURT CASE DETAILS ............................................................................................... 181

10.12 REPORTING ............................................................................................................... 181


9 | P a g e

DISCLAIMER

1. The information contained in this Request for Proposal document (the “RFP”) or subsequently

provided to Bidder(s), whether verbally or in documentary or any other form by or on behalf of the

Haryana Urban Development Authority (HUDA) or any of their employees or advisors, is provided

to Bidder(s) on the terms and conditions set out in this RFP and such other terms and conditions

subject to which such information is provided.

2. This RFP is not an agreement and is neither an offer nor invitation by the HUDA to the prospective

Bidders or any other person. The purpose of this RFP is to provide interested parties with

information that may be useful to them in preparing their technical proposals and financial offers

pursuant to this RFP (the "Proposal").

3. This RFP includes statements, which reflect various assumptions and assessments arrived at by

HUDA in relation to the Assignment. Such assumptions, assessments and statements do not

purport to contain all the information that each Bidder may require. This RFP may not be

appropriate for all persons, and it is not possible for the HUDA, its employees or advisors to

consider the investment objectives, financial situation and particular needs of each party who

reads or uses this RFP. The issue of this RFP does not imply that HUDA is bound to select a Bidder

or to appoint the Selected Bidder for the Assignment and HUDA reserves the right to reject all or

any of the Bidders or Proposals without assigning any reason whatsoever.

4. The Bidder shall bear all its costs associated with or relating to the preparation and submission of

its Proposal including but not limited to preparation, copying, postage, delivery fees, expenses

associated with any demonstrations or presentations which may be required by HUDA or any other

costs incurred in connection with or relating to its Proposal.

5. HUDA shall not be liable in any manner whatsoever for the same or for any other costs or other

expenses incurred by a Bidder in preparation or submission of the Proposal, regardless of the

conduct or outcome of the Bidding Process.


10 | P a g e

A. DEFINITIONS

Unless the context otherwise requires, the following terms whenever used in this RFP and

Contract have the following meanings:

1. “Bidder” means firm/company who submits proposal in response to this Request for Proposal

document.

2. “System Integrator” means the firm/ company, selected through competitive tendering in

pursuance of this RFP, for providing the System Implementation services under the contract.

3. “Contract” means the Contract entered into by the parties for providing System Implementation

services along with the entire documentation specified in the RFP.

4. “CLIENT/DEPARTMENT” means Haryana Urban Development Authority (HUDA).

5. “Personnel” means technical and support staff provided by the System Integrator to perform

services to execute an assignment and any part thereof.

6. “Proposals” means proposal submitted by bidders in response to the RFP issued by the

DEPARTMENT for selection of System Integrator

7. “Go-Live” The date on which the proposed solution becomes operational after successful

conclusion of all acceptance tests to the satisfaction of HUDA or as provided in this RFP.

8. “Implementation Services” means the work to be performed by the System Integrator pursuant

to this RFP and to the contract to be signed by the parties in pursuance of any specific

assignment awarded by the DEPARTMENT.

9. “Working Hours/Day” 9 hours a day, 5 days a week. These times are subject to change as per

changes in the rules and regulations of the department or as per requirements of HUDA

10. “SOW” means Scope of Work for the SI, specified in Section 4 of RFP


11 | P a g e

B. LETTER OF INVITATION Date: __________

To

<Name of System Integrator Firm>

<Address>

Sub: Selection of System Integrator for the Up-Gradation/Development and Maintenance of HUDA

Application

The Haryana Urban Development Authority (HUDA) is a statutory body of Haryana Government

constituted under the Haryana Urban Development Authority Act, 1977. A statutory body of State

Government of Haryana, HUDA’s mandate is to promote and secure development of urban areas, make

available developed land to Haryana Housing Board and to undertake building works. Presently HUDA

is having 34 Urban Estates in the state of Haryana with about three hundred thousand allottees all over

the state and lacs of citizens who use the HUDA infrastructure throughout the state including the

residents of National Capital region.

In the year 2006, HUDA went for a comprehensive computerization of Allottees account,

plots/property files and Financial accounting system aimed to

Bring improved transparency in the functioning of HUDA

Build accountability in the system

Improve the service delivery mechanism of HUDA

To redress the grievances of the allottees and the General Public

To make various online services available including enabling payment gateway

HUDA now intends to initiate a process to revamp the application and launch the next version which is

more stable and easy to use application, which uses all modern infrastructure, is entirely supported by

Cloud platforms, is compliant/viewable on all devices (computers, mobiles and tablets etc.), has bi-

lingual support (Hindi/English) and use latest technology available in market today for development

and databases.

1. To undertake the assignment of revamping the application (by upgrading the existing application or

developing a new application), HUDA intends to appoint a System Integrator for onsite

development of the project.

2. Details of the services required to be provided, terms & conditions and other details, are available

in the RFP document.


12 | P a g e

3. This RFP includes the following:

a. Letter of Invitation

b. Instruction to Bidders

c. Terms of Reference

d. General Terms of Contract

e. Appendix (Submission Forms)

4. The RFP document is available on the HUDA’S web site https://www.huda.org.in and e-tenders

Portal https://etenders.hry.nic.in from 15-03-2017onwards.

5. Any suggestion / questions to the RFP in form of pre-bid queries may be shared to HUDA at the

email id [email protected]. Any suggestions accepted by HUDA will form part of RFP and will

be uploaded in the Organization’s website www.huda.org.in.

6. Last date & time of submission of the Proposal is 19-04-2017 by 15.00 hrs. IST.

7. The bidder may also visit the Huda office on any working day for seeking clarification as per contact

details given below:

Shri. Sanjay Sharma,

General Manager (IT)

Haryana Urban Development Authority

C-3, Sector-6

Panchkula, Haryana

Phone: 0172-2569504

E-mail: [email protected]

Thanking You,

Yours Sincerely

mailto:[email protected]


13 | P a g e

1. INSTRUCTIONS TO BIDDERS

1.1 Use of RFP document & other Information

Successful bidder shall not, without the HUDA’s prior written consent, disclose the contract

agreement, or any provision thereof, or any specification, pattern, sample or information

furnished by or on behalf of Bidder in connection to any person other than a person employed

by the Bidder in the performance of the contract agreement and the scope of work. Disclosure

of document/information to any such employed person shall be made in confidence and shall

extend only as far as may be necessary for such performance.

1.2 Right to Reject All or Any Proposal

Notwithstanding anything contained in this RFP, the HUDA reserves the right to accept or reject

any Proposal and to annul the Selection Process and reject all Proposals, at any time without

any liability or any obligation for such acceptance rejection or annulment, and without

assigning any reasons thereof.

HUDA reserves the right to reject any Proposal if:

1. At any time, a material misrepresentation is made or uncovered.

2. The Bidder does not provide, within the time specified by the DEPARTMENT, the

supplemental information sought by the DEPARTMENT for evaluation of the Proposal.

Such misrepresentation/ improper response may lead to the disqualification of the Bidder. If

such disqualification/rejection occurs after the Proposals have been opened and the highest

ranking Bidder gets disqualified/rejected, then the DEPARTMENT reserves the right to consider

the next best Bidder, or any other measure as may be deemed fit in the sole discretion of the

DEPARTMENT, including annulment of the Selection Process and forfeiting of EMD deposited

by the bidder.


14 | P a g e

1.3 Introduction

The name of the Client, address and telephone number is:


C-3, Sector-6

Panchkula, Haryana

Phone: 0172-2569504


Contact Details:

Shri. Sanjay Sharma

General Manager (IT)

Name of the Assignment: Selection of System Integrator for the Up-Gradation/Development

and Maintenance of HUDA Application

1. The method of selection is : Quality and Cost Based Selection (70:30 – between technical and

financial proposal respectively)

2. The System Integrators (SI) are invited to submit a Technical Proposal and a Financial Proposal

(online only), in the formats specified in this document (section 2.4 and Section 6.9 form -8)

Responses should be in English Language. The Proposal will be the basis for contract negotiations

and for ultimately signing of a contract with the successful bidder. The proposal shall remain

binding and valid for a period of 180 days from the submission of the proposal and can be

extended mutually by both the parties

3. The System Integrators must familiarize themselves with the Departmental focus and HUDA’s

existing applications and take them into account in preparing their Proposals. Refer to Section 3 -

Project Profile for details of applications.

4. Key Events and Dates

S No. Key Event Date

1 Document available on website 15-03-2017

2 Submission of Pre bid queries 27-03-2017 by 2 PM

3 Pre bid Meeting 29-03-2017 at 2 PM

4 Issue of Clarifications to the bidders 05-04-2017



15 | P a g e

S No. Key Event Date

5 Last date for submission of Technical and

Financial Bid 19-04-2017 by 3 PM

6 Address for Submission of Proposal


C-3, Sector-6

Panchkula, Haryana

Phone: 0172-2569504


7 Technical Bid Opening 20-04-2017 at 11 AM

8 Date of Technical Presentation To be informed

9 Commercial Bid Opening To be informed

10 Earnest Money Deposit INR 10 lakh to be returned upon

selection to bidder

11 Performance Bank Guarantee 10% of the Bid Value

12 Tender Fee Cost INR 5,000/-

*The department shall not be responsible for any Postal or other delays.

5. HUDA will provide limited office space with basic furniture and utilities to the engaged System

Integrator. Telephones, office and computing equipment, including servers, computers, printer,

and photocopier shall be provided by HUDA to the successful bidder for this onsite project.

6. Please note that (i) the costs of preparing the proposal and of negotiating the contract, including

a visit to the HUDA, are not reimbursable; and (ii) HUDA is not bound to accept any of the

Proposals submitted.

1.4 Clarifications/Amendments & Pre-bid Meeting

1. Bidders may request a clarification with regard to any part of the RFP document on or before

27-03-2017 by 2 PM. Any request for clarification must be sent in writing through e-mail to the

email id [email protected]. The clarifications would be issued by 05-04-2017and shall be

published on the Websites. The format for pre-bid clarification is at Section 6.11 Form -10.

The address for requesting clarifications is:

Sh. Sanjay Sharma, General Manager (IT)


C-3, Sector-6

Panchkula, Haryana

Phone: 0172-2569504






16 | P a g e

A pre-bid conference will be held in Office of General Manager (IT), HUDA, Plot No – C-3,

Conference hall, Sector – 6, Panchkula on 29-03-2017 at 2 PM. A bidder has to first deposit the

cost of RFP – INR 5000/- by DD in favor of the Chief Administrator, HUDA to get registered.

1.5 Preparation of Proposal

1. System Integrator is requested to submit the Proposals in English language.

2. The bidding comprises of three tier system: Pre-qualification, Technical bid and Financial bid.

3. In preparing the Technical Proposal, bidders are expected to examine the documents comprising

this RFP in detail. The proposal should cover all the aspects of the terms of reference (specified

in section 4). Any bid not found responsive to the terms of reference shall be rejected. Material

deficiencies in providing the information requested may also result in rejection of the Proposal.

4. While preparing the Technical Proposal, bidders must give particular attention to the following:

a. The bidder shall not associate with individual SI(s) and / or other firms or entities in a joint

venture relationship to outsource/sub-contract a part or whole of services desired of the

bidder as a part of this assignment.

b. The detailed resume (inclusive of Professional Qualification and Experience) of key

professional staff proposed to be deployed for the project should be submitted.

c. The key professional staff proposed should be permanent employees of the bidding firm.

d. Except as specifically provided, the Technical Proposal shall not include any information

relating to the Financial bid.

e. In preparing the Financial Proposal, Bidders are expected to take into account the

requirements and conditions of the RFP document.

5. The Financial Proposal should be inclusive of all taxes, duties, fees, levies, and other charges

imposed under the applicable local laws.

6. Bidders should express the price of their services in INR only.

7. The proposals must remain valid for 180 days after the date of opening of the financial

proposals. During this period, the bidder is expected to keep available the professional staff

proposed for the assignment. The Client will make its best effort to complete negotiations

within this period.

8. Earnest money deposit: The proposal must be accompanied by earnest money deposit of Rs. 10

Lacs in the form of Demand Draft, or Bank Guarantee drawn on any nationalized/scheduled

bank payable to ‘The Chief Administrator HUDA’ at Panchkula without which the proposal will

be rejected outright. Earnest money deposit will not be accepted in cash or any other manner.

No interest is payable on the amount of E.M.D.

9. The Earnest money deposit will be returned along with necessary endorsement for payment to

the tenderers whose offers are not accepted by HUDA within two months of the placing of final

order to the successful bidder. However for the successful bidder, the Earnest money deposit so

submitted will be refunded on submission of Bank guarantee against security deposit.


17 | P a g e

1.6 Submission, Receipt and Opening of Proposals

1. Each Bidder shall submit only one Technical Proposal.

2. Each Bidder can submit one Financial Proposal, financial break up as mentioned in Section 6.9

FORM- 8

3. Proposals should be submitted in English Language

4. The proposal submission address is:

Sh. Sanjay Sharma, General Manager (IT)


C-3, Sector-6

Panchkula, Haryana

Phone: 0172-2569504


5. Proposals must be submitted no later than 19-04-2017 by 3 PM. Any Proposal received there

after shall be returned unopened.

6. The original Prequalification Proposal, Technical Proposal and Financial Proposal shall be

prepared in indelible ink. It shall contain no inter-lineation or overwriting, except as necessary to

correct errors made by the firm itself. Any such corrections must be attested by the person or

persons who sign(s) the Proposals.

7. An authorized representative of the firm should sign on all the pages of the Proposal. The

representative’s authorization should be confirmed by a written power of attorney

accompanying the Proposal.

8. Manual Submission of Documents - Online Bidders will also require to physically submit the Bid

Document (prequalification proposal and technical proposal) and EMD costing in original as

uploaded on the website, otherwise the bid shall stand rejected. The documents duly binded,

properly tagged and numbered along with EMD cost of the Tender Request for Proposal shall be

sent either through speed post, courier or personally and should reach in the office of General

Manager(IT), HUDA, C-3, Sector-6, Panchkula by 19-04-2017 till 3 PM.

9. The Financial Proposal should only indicate prices without any condition or qualification

whatsoever and will include all taxes, duties, fees, levies and other charges levied by Central &

State, as may be applicable in relation to activities proposed to be carried out. Any upward or

downward revision in taxes, duties, fees, levies and other charges levied by Central & State

during the period of contract shall be to the client’s account. Bidder will also include in its fees all

Out of Pocket Expenses relating to the deployment of the Team in HUDA HQ office, Panchkula.

The Financial bid should be submitted through online mode only.

10. Bidders should express the price of their services in INR only.

11. The bid proposals for manual submission should be submitted as follows:



18 | P a g e

a. Prequalification Proposal should be placed in one envelope and should be marked as

“Prequalification Proposal for Selection of System Integrator for the Up-

Gradation/Development and Maintenance of HUDA Application‟

b. Technical Proposal in another envelop marked as “Technical Proposal for Selection of

System Integrator for the Up-Gradation/Development and Maintenance of HUDA

Application”.

All above envelopes should be sealed separately and put in one envelope marked “Selection of

System Integrator for the Up-Gradation/Development and Maintenance of HUDA Application”.

This outer envelope shall bear the submission address and other information indicated in the

Data Sheet and clearly marked, “Do not open, except in presence of the Evaluation Committee.”

12. The financial proposal must be submitted through online mode only.

13. After the deadline for submission of proposals the Prequalification Proposal shall be opened

immediately by the evaluation committee.

14. Proposals must remain valid for 180 days after the date of opening of financial proposals.

15. From the time the bids are opened to the time the contract is awarded, if any Bidders wish to

contact the Client on any matter related to its proposal, it should do so in writing at the address

of the client’s office indicated in Para 4 of Section 1.6 above. Any effort by the Bidder to influence

the Client in the Client’s proposal evaluation, proposal comparison or contract award decisions

may result in the rejection of the proposal.

1.7 Instructions to Bidders for E-Tendering

These conditions will over-rule the conditions stated in the tender documents, wherever relevant

and applicable.

1. Registration of bidders on E-tendering Portal: All the Bidders intending to participate in the

tenders processed online, are required to get registered on the Electronic Tendering System on

the Portal https://etenders.hry.nic.in

2. Obtaining a Digital Certificate

a. The Bids submitted online are required to be signed electronically with a Digital Certificate

to establish the identity of the bidder online. These Digital Certificates are issued by an

Approved Certifying Authority, by the Controller of Certifying Authorities, Government of

India.

b. In case of online bidding if the digital certificate issued to the authorized user of a firm is

used for signing and submitting a bid, it will be considered equivalent to a no objection

certificate/power of attorney /lawful authorization to that User. The firm has to authorize a

specific individual through an authorization certificate signed by all partners to use the

https://etenders.hry.nic.in/


19 | P a g e

digital certificate as per Indian Information Technology Act 2000.Unless the certificates are

revoked, it will be assumed to represent adequate authority of the user to bid on behalf of

the firm in HUDA tenders as per Information Technology Act 2000. The digital signature of

this authorized user will be binding on the firm.

c. In case of any change in the authorization, it shall be the responsibility of management /

partners of the firm to inform the certifying authority about the change and to obtain the

digital signatures of the new person / user on behalf of the firm / company. The procedure

for application of a digital certificate however will remain the same for the new user.

d. The same procedure holds true for the authorized users in a private/Public limited

company or L&C Society. In this case, the authorization certificate will have to be signed by

the directors of the company.

3. Set up of machine

In order to operate on the electronic tender management system, the user’s machine is

required to be set up. A help file on setting up of the system can be downloaded from the home

page of the website - https://etenders.hry.nic.in or may contact on following:-

Tel: 0172-2707732, 2700275

Toll Free: 1800 3070 2232

Mobile: +91-7878007972 and +91-7878007973

4. Download of Tender Documents

The tender documents can be downloaded by the registered user from the Electronic

Tendering System through the Portal https://etenders.hry.nic.in

5. Key Dates

The bidders are strictly advised to follow dates and times as indicated in the Introduction

section (Para 4Section 1.3). The date and time will be binding on all bidders. All online activities

are time tracked and the system enforces time locks that ensure that no activity or transaction

can take place outside the start and end dates and the time of the stage as defined in the

Notice Inviting Tenders.

6. Submission of actual online bids

Bidders have to submit their bids online and upload the relevant documents. The process is

required to be completed within the date and time as stated in the Notice Inviting Tenders (Key

Dates). (Para 4Section 1.3) The electronic bids of only those bidders who have submitted their

bid within the stipulated time, as per the tender time schedule (Key Dates), will be accepted by

the system. A bidder who does not submit his bid within the stipulated time will not be allowed

to submit his bid by the E-Tendering System.




20 | P a g e

Note: Bidders participating in e-tendering shall check the validity of his/her Digital Signature

Certificate before bidding in the Tenders floated online at e-tendering website

https://etenders.hry.nic.in



21 | P a g e

2. PROPOSAL EVALUATION

2.1 Pre-Qualification Criteria

At the time of submission of bid response, the Bidder should be able to demonstrate

Organizational, Financial and Experience criteria as specified below.

Please Note: These are the minimum requirements for a bidder to be evaluated for this RFP. Any

bids not meeting the pre-qualification criteria shall be rejected. Bid without adequate EMD will

be liable for rejection without providing any opportunity to the bidder concerned. All Formats

in which information is to be submitted are attached in section 6

S No. Qualification Criteria Documents/ Information

to be provided in the

submitted response

Format /

Template in

which

information

to be

submitted

(section 6)

PQ 1. Covering Letter of submission of response. As per format in Form-1 Form - 1

PQ 2. The bidder must be a company

registered/incorporated under the Indian

Companies Act, 1956 and have been in

existence for a period of at least 5 years as of

31.12.2016

a) Certificate of

Incorporation

b) Memorandum of

Association or Articles of

Association

PQ 3. The Bidder should have been engaged in IT

related activities / services for at least last 5

years as on 31st December 2016. IT related

activities/ services should mean projects

involving development of software applications,

providing operational and maintenance services

for applications.

Work orders confirming

year and Area of activity,

signed and stamped by

authorized signatory of the

Bidder.

Form - 2

PQ 4. Bidder should hold a valid ISO 9001:2008/ISO

9001:2015 and CMMI-5 certificates or higher as

on date of submission of bid

Valid ISO 9001:2008/ISO

9001:2015 and CMMI-5

certificates.

PQ 5. The bidder should not have been blacklisted by

any Government Agency in India or be under a

declaration of ineligibility for fraudulent or

corrupt practices or inefficient/ ineffective

Self-declaration from the

authorized signatory of

the bidder

Form - 3


22 | P a g e

performance as on date of submission of bid.

PQ 6. The bidder should have valid Service Tax

Registration and PAN No as on date of

submission of bid.

Certified copy of service

tax registration and PAN

number.

PQ 7. The Bidder must have on its roll IT staff of at

least 100 professionally qualified personnel

(relevant degree holders B. Tech/B.E/MCA/M.

Tech / MBA) as on date of submission of bid

Self-certificate signed by

the Authorized

Representative of the

Bidder should be

submitted.

PQ 8. The bidder should satisfy following financial

criteria:-

The Bidder should have:

A. Positive net worth

B. An overall annual turnover of not less

than INR 50 Crore during each of the

last three financial years (, FY13-14,

FY14-15 and FY15-16). Out of the total

annual turnover INR 25 Crore should

be from Software/ Application

Development and Integration in each

of the last three financial years from

Indian operations. (F.Y., 2013-14, 2014-

15 and 2015-2016 respectively)

Audited Annual Financial

Statements and Annual

Report and Certified

statement from the

Current Statutory

Auditors of the bidder.

Form - 4

PQ 9. Bidder’s experience credentials must meet one

of the following options:

a. Completed 1 engagement with Government /

PSU in India/ Abroad where value of work

relating to software development,

enhancement and / or maintenance is INR 5

crore or higher in the last 7 years as on date of

submission of bid.

b. Completed 2 engagements with Government

/ PSU in India/ Abroad, value of work relating to

software development, enhancement and / or

maintenance in each of which is at least INR 3

Crore in the last 7 years as on date of

submission of bid.

a) Filled citations

b) Work Order/

Agreement clearly

highlighting the date

of award of work and

value of work from

software

development,

enhancement and / or

maintenance

c) Project Completion

Certificate from client

mentioning start &

end date of the

project and value of

work from software

Form - 5


23 | P a g e

development,

enhancement and / or

maintenance.

d) Self-certificate from

Company CS.

However client is free

to make a reference

checks or

independently

validations.

PQ 10. Consortium of any kind is not allowed.

Self-declaration from

authorized signatory of

bidder that there is no

consortium partner.

Form - 6

PQ 11. Escalation matrix The bidder shall provide

the escalation matrix along

with contact number,

email id and address of the

hierarchy up to the level of

MD/CEO of the Company.


24 | P a g e

2.2 Technical Evaluation Criteria

The technical proposals of only those bidders, who qualify in the evaluation of the

prequalification proposals, shall be considered.

The Technical Bid will be examined by the evaluation committee on the basis of responsiveness

to the scope of work, past experience and profile of people in the firm. The broad evaluation

criteria and points system applied are specified below. The bidder attaining Zero in any of the

Technical Criteria may lead to disqualification of the Bid. The Technical Evaluation Committee, at

its sole discretion, would evolve a further benchmark, scoring pattern within the allocated marks

for each line item indicated below.

S.

No.

Qualification Criteria MARKS Documents/Information to

be provided in the submitted

response

Reference

& Page

Number

TQ 1 - Experience 30 Marks ( Refer section 6.6 form-5 format for Citation)

1. Software development and

maintenance experience for

Indian Government

Ministries / Departments /

PSUs with value of work

relating to software

development, enhancement

and / or maintenance INR 3

crore or higher.

Work order should have

been awarded in the last

five years as on date of

submission of bid

(Only any additional

projects apart from the

ones already mentioned in

the prequalification

proposal to be specified

here)

Project should be

completed or ongoing with

relevant software related

milestone completed.

5 projects: 20 Marks



2 projects: 8 Marks

1 project: 4 Marks

The Bidders shall submit:

a. Filled up citations

b. Work Order/ Agreement

clearly highlighting the date of

award of work and value of

work from software


and / or maintenance

c. Project Completion /partial

completion Certificate from

client mentioning start & end

date of the project and value

of work from software


and / or maintenance.


25 | P a g e

Weight ages (W)

In case relevant software

related milestone is

completed (application

gone live) and client

completion letter available :

100% weight age


related milestone is in

progress (application not

gone live) and work order

more than 6 months old

and client satisfaction letter

available: 50% weight age

2. Experience of application

Development and

implementation with an

Urban development

authority / Urban local

bodies / State Industrial and

Infrastructure Development

Corporation/ Banks / PSUs

or any e-Governance

project in the last 7 years.

Work order should have

been awarded in the last

seven years as on date of

submission of bid

Project should be

completed or ongoing with

relevant software related

milestone completed.

Weight ages (W)


related milestone is

completed (application

gone live) and client

completion letter available :


1 project: 5 Marks

The Bidders shall submit:

a. Filled up citations (Section

6.6 FORM 5)

b. Work Order/ Agreement

clearly highlighting the date of

award of work and value of

work from software


and / or maintenance

c. Project Completion /partial

completion Certificate from

client mentioning start & end

date of the project and value

of work from software


and / or maintenance.


26 | P a g e

100% weight age


related milestone is in

progress (application not

gone live) and work order

more than 6 months old

and client satisfaction letter

available: 50% weight age

TQ- 2 Solution Proposed & Approach and Methodology(20 marks)

1. Solution Architecture

Proposed solution

architecture fulfilling

project requirement and

description of proposed

software components.

10 Marks Solution architecture and

detailing of components used

including aspects of security,

scalability, performance

assurance

2. Approach and

methodology for the

project:

10 Marks Describe the detailed

approach and methodology

for SDLC to be adopted for the

project.

a) Formal approach to PM,

usage of specific tools

b) Formal approach for

training and change

management

c) Approach to Pilot and Go-

live and transition from

existing to new system

d) Assumptions and Key asks

/ support required from

HUDA

TQ 3- Resource Deployment Plan ( 5 Marks)

1. Resource Deployment Plan 5 Marks The bidder is required to

share the Resource

Deployment Plan with

detailed roles and

responsibilities of each

resource with deliverables in

terms of documents and


27 | P a g e

visible outcomes associated

with each resource within the

scope of project Without

Resource Deployment Plan

the technical Evaluation of

resources shall not be

considered

TQ 4 - Resource Profile (30 Marks) It is required that the bidders should submit the CVs (Refer

Section 6.8 FORM- 7 SUGGESTED FORMAT OF CURRICULUM VITAE (CV) FOR PROJECT STAFF) of

all the key personnel proposed for the project.

1. Project Manager (Offsite)

B. Tech/ B.E. and MBA

At least 7 years as project

manager, Past experience

in handling .NET based

application up

gradations/migration a

must.

•More than 10

years of Relevant

Experience = 5

Marks

• 7 to 10 Years of

Relevant Experience

= 3 Marks

• Less 7 Years of

Relevant Experience

= 0 Mark

Applicant CV

Applicant Documents /

Credentials

2. Senior Architect (1,

Onsite)

B.E/B.Tech/MCA

At least 5 years are in

Architect Roles, Past

experience in handling

.NET based application up

gradation/migration

• More than 7 Years

of Relevant

Experience = 5

Marks

• 5 years to 7 Years

of Relevant

Experience = 3

Marks

• Less than 5 Years

of Relevant

Experience = 0

Mark

Applicant CV


Credentials

3. Senior Software Engineer

(Minimum 2, Onsite)

B.E/B.Tech/MCA least 5

year experience as

Application developer.

Working knowledge of

.NET 2.0 required. Prior

• More than 7 years

of Experience in

Application

development based

projects = 5 Marks

• 5 Years to 7 years

of Experience in

Applicant CV


Credentials


28 | P a g e

experience on

finance/Account related

project is must. At least

one resource with

SharePoint Server

experience as well .NET

development experience.

Knowledge of PL/SQL is a

must.

Application

development based

projects = 3 Marks

Less than 5 Years of

Experience in

Application

development based

projects = 0 Mark

4. Software Engineer

(Minimum 4 onsite)

B.E/B.Tech/MCA

At least 3 years of

experience as application

developer. Knowledge of

PL/SQL is a must.

• More than 5 years

of experience in

Application

development based

projects = 5 Marks

• 3 years to 5 years

of Experience in

Application

development based

projects = 3 Marks

Less than 3 years of

experience in

Application

development based

projects = 0 Mark

Applicant CV


Credentials

5. Quality Analyst (Minimum

1 onsite)

B.E/B.Tech/MCA

At least 3 years of testing

experience and

demonstrated experience

in handling quality

assurance tools.

• More than 5 Years

of Experience in

testing and handling

quality assurance

tools = 5 Marks

• 3 years to 5

Years’ Experience in


quality assurance

tools = 3 Marks

•Less than 3 Years

of Experience in


quality assurance

tools = 0 Mark

Applicant CV


Credentials


29 | P a g e

6. Database Administrator,

onsite

B.E/B.Tech/MCA,

Database Certification

At least 5 years of

experience as a database

administrator.

• More than 5

Years of

Experience as

database

administrator = 5

Marks

• 3 years to 5 Years

of Experience as

database

administrator = 3

Marks

• Less than 5 Years

of Experience as

database

administrator = 0

Mark

Applicant CV


Credentials

TQ 5 - Certifications( 5marks)

1. Other relevant certifications

ISO 20000 and ISO 27001

1 Certification =3

marks

Both Certifications =

5 marks

Certified copies of all valid

certifications

TQ 6 - Technical Presentation 10 Marks

1. Technical Presentation

30 minutes

10 Marks Technical presentation to

demonstrate the bidders

proposal to the client

including approach and

methodology,

software/platform/

technology to be used,

Number of software licenses

required etc.


30 | P a g e

2.3 Evaluation of Pre-Qualification Bids

1. For the evaluation of Pre-Qualification Bids, the documentation furnished by the Bidders will be

examined to check if all the eligibility requirements and furnished in accordance with the

formats supplied are met.

2. HUDA may ask the Bidder for additional information whenever HUDA feels that such

information would be required. This may also include reference checks to verify credentials

supplied by the Bidder.

3. Proposals not meeting pre-qualification criteria will not be processed further for technical

evaluation.

2.4 Technical Evaluation Process

1. Technical Proposals would be evaluated only for those Bidders, who qualify the Pre-

qualification evaluation.

2. Depending on the evaluation methodology mentioned above in Section 2.2, each Technical Bid

will be assigned a technical score (TS) out of a maximum of 100 points as per the

aforementioned Technical Evaluation Criteria.

3. A bidder will be considered for opening of Financial Bid if it scores at least 70% marks in the

Technical Evaluation criteria as defined in Section 2.2

4. After the technical evaluation is completed, HUDA shall notify the name of the bidder on

website www.huda.org.in whose proposals were considered non-responsive to the RFP and

Terms of Reference or not qualified for the financial evaluation, indicating that their Financial

Proposals will be returned unopened after completing the selection process. HUDA shall

simultaneously notify the bidders, whose proposals have qualified for further evaluation,

indicating the date and time set for opening the Financial Proposals. The notifications will be

hosted on HUDA website www.huda.org.in.

2.5 Financial Evaluation Process

1. The Financial bid should be submitted through online mode only

2. Only those bidders who qualify the Technical Evaluation shall be considered for financial

evaluation. The Financial Proposals of such bidders shall be opened in the presence of the

bidders’ representatives who choose to attend.

3. The financial evaluation of the financial proposal will be by determining whether the Financial

Proposals are complete and unconditional.

4. The cost indicated in the Financial Proposal shall be deemed as final and reflecting the total

cost of services (“Bid Price”).

http://www.huda.org.in/



31 | P a g e

5. Omissions, if any, in costing any item shall not entitle the bidder to be compensated and the

liability to fulfill its obligations as per the Scope of Work within the total quoted price shall be

that of the bidder.

6. No pre-tender or post-tender negotiation with any bidder including successful bidder shall be

allowed.

7. The currency or currencies in which payments shall be made to the supplier/ selected bidder

under this Contract shall be Indian Rupees (INR) only.

8. Any conditionality included in the financial proposal will lead to disqualification of the entire

bid and forfeiture of the EMD.

9. The Proposal with lowest ‘Total Cost Quote for Project’ will be awarded a Commercial score of

100 (L1).

10. Commercial Scores for other technically qualified bidders will be evaluated using the following

formula- Commercial Score of Bidder (CS) = (Financial Bid of L1 / Financial Bid of the Bidder)

X100 (rounded off to 2 decimal places)

2.5.1 Correction of Arithmetic Errors in Financial Bids

The bid evaluation committee shall correct arithmetical errors in substantially responsive

Bids, on the following basis, namely: -

1. If there is an error in a total corresponding to the addition or subtraction of subtotals, the

subtotals shall prevail and the total shall be corrected

2. If there is a discrepancy between words and figures, the amount in words shall prevail, unless

the amount expressed in words is related to an arithmetic error, in which case the amount in

figures shall prevail subject to clause (1) above.

2.6 Final Evaluation

1. Final evaluation shall be done on “Quality & Cost Based Selection” method (QCBS).

2. A composite score shall be calculated for technically qualified bids only. The weight age for the

composite evaluation shall be awarded as below:-

i. Technical – 70%

ii. Commercial – 30%

3. Bidder with the highest final Score (FS1) (Final Score = TS*0.70 + CS*0.30) will be considered as

successful bidder (rounded off to 2 decimal places).

4. In case of a tie in the final score, the bidder having highest technical score will be considered

eligible for award of contract.

5. No pre-tender or post-tender negotiation with any bidder including successful bidder shall be

allowed.


32 | P a g e

2.7 Award of Contract

1. After evaluation of the proposals, a contract will be awarded to the most responsive bidder(s)

with highest final score as per Final Evaluation (section 2.6).

2. Prior to expiry of the validity period, HUDA will notify in writing that the successful bidder’s

proposal has been accepted and LOI will be issued. Upon the successful bidder’s furnishing of a

Performance Bank Guarantee, the contract signing process will commence. In case the

tendering process has not been completed within the stipulated period, HUDA, may ask the

bidders to extend the validity period of the bid.

3. The notification of award will constitute the formation of the contract. Upon the successful

bidder's furnishing of Performance Bank Guarantee, HUDA will notify each unsuccessful bidder

and return their EMD.

2.8 Performance Bank Guarantee (PBG)

1. The successful bidder shall at its own expense deposit with HUDA, within 15 Working Days of

the date of notice of award of the contract, an unconditional and irrevocable Performance

Bank Guarantee (PBG) from a Scheduled or Nationalized bank acceptable to HUDA, payable on

demand, for the due performance and fulfillment of the contract by the Bidder.

2. The Successful Bidder will submit Performance Bank Guarantee (PBG) of INR 10% of the

contract value valid for tenure of the contract + six (06) months. All incidental charges

whatsoever such as premium, commission etc. with respect to the Performance Bank

Guarantee shall be borne by the bidder.

3. PBG shall remain valid for a period of one hundred and eighty (180) days beyond the date of

completion of all contractual obligations of the successful bidder.

4. In the event of the bidder being unable to service the agreement for reasons solely attributed

to service provider, HUDA would have the right to invoke the PBG, in lieu of all other related

claims for damages under this agreement. HUDA shall notify the bidder in writing of the

exercise of its right to receive such compensation within 14 days, indicating the contractual

obligation(s) for which the bidder is in default.

5. Before invoking the PBG, the bidder will be given an opportunity to represent before HUDA.

The decision of HUDA on the representation given by the Supplier shall be final and binding. If

circumstances so warrant, the matter may be referred to an arbitrator to be appointed by the

HUDA with mutual consent.


33 | P a g e

3. PROJECT PROFILE

The Haryana Urban Development Authority (HUDA) was constituted under the Haryana Urban

Development Authority Act, 1977. A statutory body of State Government of Haryana, HUDA’s

mandate is to promote and secure development of urban areas, make available developed land to

Haryana Housing Board and to undertake building works. Presently HUDA is having 34 Urban

Estates in the state of Haryana with about Three hundred thousand allottees all over the state and

lacs of citizens who use the HUDA infrastructure throughout the state including the residents of

National Capital region.

In the year 2006, HUDA went for a comprehensive computerization of Allottees account,

plots/property files and Financial accounting system aimed to

1. Bring improved transparency in the functioning of HUDA

2. Build accountability in the system

3. Improve the service delivery mechanism of HUDA

4. To redress the grievances of the allottees and the General Public

5. To make various online services available including enabling payment gateway

The applications were launched in 2006 and used then latest available technologies like .Net as

platform and SQL server as the database. Currently the applications are using .Net 2.0 as

development platform and MSSQL server 2008 as the database. The Test System Environment is

hosted at HUDA HQ office while the Live Production system are hosted at SDC State Data Center)

Haryana.

HUDA now intends to initiate a process to revamp the application and launch next version which is

more stable and easy to use application, which uses all modern infrastructure, is entirely

supported by Cloud platforms, is compliant/viewable on all devices (computers, mobiles and

tablets etc.), has bi-lingual support (Hindi/English) and use latest technology available in market

today for development and databases.

Through this RFP HUDA invites interested System Integrators (SI) to /upgrade/modify/ re-develop

the applications onsite to achieve the requirements mentioned under the Scope of work (section

4). The SI is required to study/understand the functionalities of the current applications deployed

in HUDA and modify/upgrade current application or develop newer version of applications on

latest platforms and database technologies.

A brief of current applications deployed in HUDA is given below. Proposed architecture and high

level Functional requirements of the applications is also described in the section-4scope of work.


34 | P a g e

The SI is required to design, develop and deploy the applications as per technology of their choice

to best meet the requirements mentioned in this RFP

3.1 Total Number of current HUDA Users & offices

Application Internal users External Users Concurrent Users

Plot & Property Management and

Financial accounting System

2000 NA 1000

Court Case Tracking System 2000 15000 1000

Web portal 1000 350000 150000

Utility Services – Online Booking System 10 4500 100

The bidder also has to provide web interface for the application already running in HUDA

3.2 HUDA Citizen Web Portal

There are about 3, 15,000 allottees who are already registered into the portal. The application

has a user database which is used for registering and authenticating the users of the portal. The

application also uses the PPM database. The PPM application and the portal application are

deployed in the same environment as detailed below. As a result the portal application has

access to the PPM database. All details related to the plots and the properties are picked from

the PPM database.

The portal Application also has a payment gateway feature through external partners for online

payment of Dues. This application has been implemented in 3 tier architecture.

The application is used for:

a. Publish information about the new schemes of HUDA.

b. Publish tenders and notices.

c. Allow online registration of users for the schemes of HUDA and to facilitate online payment

of dues.

d. Allow banks to upload payment details in the form of excel sheets and flat files.

e. Allow download of different kinds of application forms and challans.

f. Provide information to registered Allottees about their Plots and Payments Due.


35 | P a g e

The users of the application can be categorized into the following categories:

a. Allottees

b. Citizen

c. Admin

d. Banks

The major purpose for which the application is used by the public users is to find information

about the new schemes that have been launched and to facilitate the payment of dues by the

allottees.

The content on the portal is mostly static. Dynamic content is fetched from PPM database, while

the MOSS server takes care of displaying the static content.

3.2.1 Application platform details

Sr. No Detail Software/Platforms

1. Development environment Visual Studio 2005

2. Framework Dot Net 2.0 Service Pack 1

3. Compilation .NET

4. Database MS SQL server 2008 R2

5. Operating system

Windows Server 2008 R2 Enterprise (x64) Service Pack 1

(build 7601

6. Share Point Moss 2007 - 32 bit

3.2.2 Hardware infrastructure for Portal Application (Test & Live Environment)

All Test systems/servers are hosted at HUDA HQ office while all Live Servers are hosted at SDC,

Haryana

Sr. No Server Role Make and

Model

Server

configuration Server Capacity and OS

1.

Application

server (test

portal server)

IBM system X

3550 M2

Dual 2.13GHz Quad

Core Nehalem

Based, 8GB RAM,

146GB X 2

Windows Server 2008 R2

Enterprise (x64) Service Pack 1

(build 7601)

2.

DB server

(portal test

database server)

HP-ProLiant

DL580 G4

Dual Xeon 3.Ghz,16

GB RAM,

146GB x 2



3. Live portal Web

server 1

HP ProLiant BL

420c G8

Intel xenon E5-

2440 2.4GHZ ( 2

200GBx2


36 | P a g e

Sr. No Server Role Make and

Model

Server

configuration Server Capacity and OS

processors) 12

cores ,

32GB RAM



(build 7601)

4. Live portal Web

server 2

HP ProLiant BL

420c G8

Intel xenon E5-

2440 2.4GHZ ( 2

processors) 12

cores ,

32GB RAM

200GBx2



(build 7601)

5.

Portal Live

Database server

1

HP ProLiant BL

420c G8

Intel xenon E5-

2450, 2.1 GHZ ( 2

processors) 16

cores,

64GB RAM

200GBx2



(build 7601)

6.

Portal Live

Database server

2

HP ProLiant BL

420c G8

Intel xenon E5-

2450, 2.1 GHZ ( 2

processors) 16

cores,

64GB RAM

200GBx2



(build 7601)

3.3 Plot and Property Management System (PPM) & Financial Accounting System (FAS)

This is an Intranet based application only accessible to employees of HUDA with all estate offices

throughout the state of Haryana

3.3.1 Plot and Property Management (PPM) Software

Plot and Property Management module takes care of the general working of the Estate Office in

terms of the plot and property management for all types of the property. This application covers

various activities such as allotment of plots, payments/ dues for plots, survey details of the plots,

maintenance of certificates by their issue dates and so on.

The PPM module of the HUDA application enables users to manage all types of plot and

property.

The major functionalities covered by the PPM module are:

1. Allotment of the plots by draw or auction, scrutiny of applications, generation of schedule of

payments, allotment letters, and offer of possession to plot holders.


37 | P a g e

2. Maintenance of date-wise tracking of the payments received; compute possession interest,

delay interest, rebates, extension fee and generate notices to the plot holders for due

payments, extension fee, and enhancement due.

3. Maintenance and tracking of all the certificates (Possession certificate, building plan, DPC

level certificate, full or partial Occupation certificate) by storing their issue dates. Generate

notices for compoundable/ non-compoundable violations.

4. Tracking of cancelled/ vacant plot, Issue Transfer certificate, Mortgage certificate, No-dues

certificate etc.

5. Monitoring of appeals filed by the plot holders.

6. Monitoring of legal cases of HUDA property under litigation.

7. Providing export data file to HUDA which would be replicated by HUDA on their public

website at pre-defined frequency to let the plot holders view their payment and dues details.

3.3.2 Financial Accounting System (FAS)

The Financial Accounting System (FAS) deals with preparation of all account books,

reconciliation of the funds, preparation of budget and monitoring of loans, and entry of bills and

their payment. The FAS module of the HUDA application enables users to manage all the

activities related to financial accounting.

The major functionalities covered by the FAS module are:

1. Preparation of all account books like Cash book, Bank book, Journal, Ledgers

2. Funds transfers between HUDA offices through Credit/Debit Notes

3. Reconciliation of Bank Statements

a. Reconciliation of funds

4. Preparation of Budget

5. Budget estimates of the receipts and expenditures of the current financial year at office level

6. Monitoring of loans to employees

7. Engineering Works Functionality

a. Entry of contractor bills at various divisional offices

b. Payments against work done

8. Preparation of trial balance. Monthly accounts are now easily available through trial balance.

9. Integration with third parties like Banking systems, etc. for updating of payments.


38 | P a g e

3.3.2.1 Application Platform Details

S.No Detail Software/Platforms

1. Development

environment Visual Studio 2005


3. Compilation .NET


5. Operating system Windows Server 2008 R2 Enterprise (x64) Service Pack 1

(build 7601

As described above, the application is divided into the following modules:

1. Administration

2. Plot and Property Management (PPM)

3. Financial Accounting System (FAS)

These applications have been implemented in a two tier architecture. The architecture used for

this application is MVC. All the business logic is implemented in a business layer. All the business

functions of application are built in the database layer using stored procedures. The business

intelligence application used for PPM and FAS Reports in the application is Crystal Reports

The application is built in .NET platform using ASP.NET 2.0. The database used for the application

is Microsoft SQL server 2008. The IDE used for development of application is Microsoft Visual

Studio 2005.

3.3.2.2 Hardware infrastructure for PPM & FAS Application (Test & Live Environment)

All Test systems/servers are hosted at HUDA HQ office while all Live Servers are hosted at SDC,

Haryana.

S.No Server Role Make and Model Server

Configuration Server Capacity and OS

1.

Application

server

(PPM&FAS test

server)

HP- ProLiant DL360

G5

Single Xeon, (2

core) 4GB RAM

72GB X 3

Windows Server 2008 R2 Enterprise

(x64) Service Pack 1

2.

DB server

(PPM&FAS test

database server)

HP-ProLiant DL580

G4

Dual Xeon

3.Ghz,16 GB

RAM,

146GB x 3


(x64) Service Pack 1


39 | P a g e

3.4 Court Case Tracking System (CCTS)

The HUDA court case tracking system is an application that helps the HUDA employees, the

allottees and the advocates to track the cases that they are a party to.

This application has the following functionalities.

1. Facilitate data entry to add/edit the details of the court cases. This is done by employees of

HUDA.

2. Allow access of reports to the users of the websites – external as well as internal. The external

users have limited access to the site and can view a limited set of reports.

3. Internal users can get access to reports in 21 pre-defined formats apart from having the

options to choose fields for a custom report.

4. All the users of the website have access to the calendar using which the user can view the

number of cases listed for hearing on any given day, along with the location details of the

hearing.

5. This application has been implemented in a two-tier architecture.

3.

Live PPM&FAS

Application

server 1

HP ProLiant BL

420c G8

Intel xenon E5-

2440 2.4GHZ ( 2

processors) 12

cores ,

32GB RAM

200GBx2


(x64) Service Pack 1 (build 7601)

4.

Live PPM&FAS l

Application

server 2

HP ProLiant BL

420c G8

Intel xenon E5-

2440 2.4GHZ ( 2

processors) 12

cores ,

32GB RAM

200GBx2



5.

PPM&FAS Live

Database server

1

HP ProLiant BL

420c G8

Intel xenon E5-

2450, 2.1 GHZ (

2 processors)

16 cores,

64GB RAM

200GBx2



6.

PPM&FAS Live

Database server

2

HP ProLiant BL

420c G8

Intel xenon E5-

2450, 2.1 GHZ (

2 processors)

16 cores,

64GB RAM

200GBx2




40 | P a g e

3.4.1 Application Platform Details

S.No Detail Software/Platforms

1. Development environment Visual Studio 2005


3. Compilation .NET


5. Operating system Windows Server 2008 R2 Enterprise (x64) Service

Pack 1 (build 7601

3.4.2 Hardware infrastructure for CCTS Application (Test & Live Environment)

All Test systems/servers are hosted at HUDA HQ office while all Live Servers are hosted at

SDC, Haryana

S. No Server Role Make and

Model Server configuration Server Capacity and OS

1.

Test Application

server (CCTS

urban estate)

IBM System

x3550 M2

Intel(R) Xeon(R) CPU

E5506 @ 2.13GHz (2

processors), 8 cores,

RAM = 8 GB

72GB X 2


Enterprise (x64) Service Pack

1

2. Test DB server

(CCTS)

Dell

PowerEdge

R720

Intel(R) Xeon(R) CPU E5-

2637 0 @ 3.00GHz, 2

Core(s), RAM = 64 GB

5TB



1

3.

Live CCTS

Application

server 1

HP ProLiant

BL 420c G8

Intel xenon E5- 2440

2.4GHZ ( 2 processors)

12 cores ,

32GB RAM

200GBx2



1 (build 7601)

4.

Live CCTS

Application

server 2

HP ProLiant

BL 420c G8

Intel xenon E5- 2440

2.4GHZ ( 2 processors)

12 cores ,

32GB RAM

200GBx2



1 (build 7601)

5. Live Database

server

HP ProLiant

BL 420c G8

Intel xenon E5-2450, 2.1

GHZ ( 2 processors) 16

cores,

64GB RAM

200GBx2



1 (build 7601)


41 | P a g e

4. SCOPE OF WORK

The Project involves two parts as below:

In the Part A, the System Integrator shall be required to upgrade the existing applications to meet

the functional and technical requirements elaborated here or build a new application in accordance

with the functional and technical requirements elaborated here and implement successfully.

In the Part B Operations & Management Post Go-Live, the System Integrator shall be required to

provide support (AMC) for the applications for a period of three years after Go-Live.

PART A – Up gradation of Existing Applications/ Development of New Application

4.1 Proposed Logical Architecture of the HUDA Applications

The applications have to be implemented in a multi-tier architecture. The architecture guidelines

in the section below suggest a possible multi-tier architecture for the applications. The proposed

architecture of the re-engineered applications is logically presented in the form of six layers. This

can be called the logical architecture of the application. The Six layers are:

1. Front End layer

2. Authentication layer

3. Workflow and Workflow Builder Layer

4. Business process Layer

5. Data Layer

6. Integration Layer


42 | P a g e

1. Front end – This consists of the applications and the interfaces which allow a user to access

the application. This may kiosks, the web portal and the mobile applications. The UI

components including the forms that users fill and the validation of these forms will be a part

of this layer. The Front end developed should support Hindi Language also. The Front end has

to be bilingual (English & Hindi) as per Indian government norms.


43 | P a g e

E-Forms- They are the primary instrument to collect information, and lets citizens apply for

various schemes of HUDA. It is also the most common, and popular way of initiating the service

requests. E-form is an electronic version of physical forms, organized in a better way, and have

the ability to collect information more effectively, and can be easily tracked. At HUDA, these E-

Forms serve as the front end or first point for initiation of any scheme delivery. Citizens can

apply for services using these E-Forms, or take a physical print of these E-Forms and then

submit them to HUDA, in case of physical registration.

a. The e-forms will also allow for validation of the data entered into the form fields, like

validation of formats for email address, mobile numbers, Aadhar Card numbers, pan

card numbers and other details

Web Portal- the Web portal is the Front end Webpage of HUDA (www.huda.org.in). It provides

all information regarding various departments of HUDA and their working. It is the portal

where all citizens can view/access services/information/documents provided by HUDA through

Internet.

2. Authentication Layer: There will be one common page which will be the central portal. This

will be the HUDA portal. There will be different login links. Allottees, Applicants/citizens, Banks,

Employees will be the different categories of users. Allottees, applicants and banks will be able

to access the applications through internet. Employees can only login on the intranet. A

separate login page can be provided to them. All user registration and authentication happens

through this layer. User profile management and updating will be a part of this layer.

Registration Component -The registration component is for the citizens of state and will work

in tandem with the e-forms component to ensure smooth registration of applicants for the

various schemes. The registration component will also ensure that the registration rules for

different schemes are followed so that only eligible applicants are registered and ineligible

applicants are filtered out. After successful registration, a unique registration number will be

generated which will be used for all further transactions of the system – like status tracking,

escalations, notifications. For every application processed by the registration component, the

time stamp will be stored in the system. This will be useful for status tracking.

User Management- This component takes care of configuring new users for the system,

registering users in bulk and also assigning roles and responsibilities to the users. It should also



44 | P a g e

be possible to manage the privileges of the users and make changes whenever necessary. It

should also allow for search functionality.

3. Workflow and Workflow builder Layer- This is the layer that controls all the Workflows

involved in the application. It also provides for development of new workflows or modification

of existing workflows.

Workflow component- Workflow component is the main engine of the HUDA portal. All

backend processing is driven and controlled through workflow. Workflow component is a

configurable element, which moves a service across various roles and at the same time

maintains a record of progress. Workflow component has the ability to record an exception,

and truncate a process before completion, besides ensuring completion of process for most

service requests. All approvals at HUDA are managed through the workflow components. This

component will take care of routing the approval for different kinds of applications (ex. building

plans, plot applications, certificates, bills, payments) to the concerned officers within the

department and keeping a track of the current status.

Workflow Builder- This is one of the most important components of this system. The main

purpose of this component is to help Administrators create new forms and new workflows

depending on the requirements. Using workflow builder, forms can be created for new

schemes, workflows can be created for new processes – right from the number of approvers

required, people to be notified, payments to be made, external interfaces that are to be used

and so on. Additionally, the workflow builder will also allow to modify the rules of the existing

processes as and when the need arises. In short, it uses the existing components of the

application to create new work flows according to the process requirements. This is different

from the workflow component because the workflow component takes care of the backend

processing, whereas the workflow builder creates the rules and logic which the workflow

component has to follow.

4. Business Process Layer- This is the layer where the workflow engine would manage flow of

service requests from one stage to another. This should be highly configurable, and should be

able to manage multi-level workflows. All Integrations with external systems like Payment

gateways, Associate Banks and other government systems (CM Dashboard, Aadhar) would

happen here. The Content management services will also be a part of this layer. The different

Business Modules of the application will be a part of this layer. This layer helps information

exchange between all the modules.


45 | P a g e

Content Management System- Content Management system makes it easier to store and

access the information that is available in the system. This includes making downloadable

content like challans, application forms and excel templates on the website. This also includes

provision for maintaining audio files, video files, images and content from third party internet

sources. The department information, notices, tenders, policies, news items, advertisement of

new schemes can be managed using this component. It also includes a Search component to

easily find information in the system using keywords. MIS Reporting is a component, which

would enable reporting for various levels, in both standard and ad-hoc formats. Most of the

reports would be pre-defined, but this component should also be able to help the officials with

new reports, whose need arises in future, or are ad-hoc in nature. MIS reporting component is

expected to interface all database elements, and be able to generate reports in various formats

Business Modules – The four major Business modules of the application are HUDA web portal,

plot and property management, financial accounting system and Court case tracking system.

The High Level core functionalities of all the Modules are defined below in the FRS(Annexure).

Further Modules can be added as per Business needs and similarly large modules can also be

split into smaller modules for ease of operations. All Module mentioned are interrelated and

information exchange takes between all modules.

External service Interface- the modules are linked with external services like payment

gateways, notification components


46 | P a g e

Payments- this component is a generic module /interface by which various services are able to

provide users/citizens to make payments for various services through widely used payment

methods like credit cards, debit cards and net banking.

Notifications- Notification component acts as a messaging component between HUDA and end

users, as this component’s primary function is to notify end users. The end users could be

citizens, complainants, department employees, allottees. Notification components should have

further sub-components consisting of SMS Gateway, SMTP Gateway (email), IVR and should

also have a facility to print individual letters in case of certain specific services

Reconciliation- This Component shall be used to perform System reconciliation of the Bank

statement with that of the ledger of that bank account in HUDA. The Bank statement details

are fed in to the system, either through manual entry or upload of data (reverse files) by the

banks in the system. The Bank statements are reconciled with the voucher details within the

system

5. Data Layer - This layer consists of components that hold the data required by the applications.

The information for the user accounts, employee details, documents and reports, receipts,

certificates come from this layer. Each module is associated with a database and all database

share data between themselves.

6. Integration Layer – SOA (Service oriented architecture) based integration layer facilitate the

integration of external systems such as Banks, Adhaar and other Government applications, SMS

gateways, Email gateways, IVR, payment aggregators, etc.. It is based on Service Oriented

Architecture which allows participating systems to provide and consume functionalities as

services. This layer should provide standard adapters for commonly used enterprise

applications. The integration layer should also support known industry integration mechanisms


47 | P a g e

4.2 Architecture Guidelines The Application is expected to be cloud compliant and multi device friendly.

1. Centralized Architecture – It is proposed that all the applications will make use of a

centralized architecture. All requests from the users (both internal and external) will be

routed to a single system for processing.

2. Web Portal should be upgraded/developed according to the Government of India Guidelines for

Government Websites (GIGW) and W3C guidelines.

3. As mentioned in the logical architecture, the system should support a multi-tier architecture.

4. The Application developed should support Hindi Language also. The application has to be

bilingual (English & Hindi) as per Indian government norms.

5. The integration layer of application should be based on SOA (Service oriented architecture),

should support XML services and all the necessary protocols that need to be supported for

internet applications. The integration layer should also support known industry integration

mechanisms

6. The architecture should support Loose Coupling to the maximum possible extent. Loose

coupling of services reduces dependencies and helps ensure components are treated

individually. Failure, removal or addition of a component should have a minimum impact on

other components.

7. While ensuring loose coupling, it should also be possible to reuse the services of a

component for different processes. This helps in avoiding designing new components to

cater to a new process.

8. The design should include integration with existing IT infrastructure created under SDC, SWAN,

CSC, and State Portal.

9. If there is any requirement of any additional software license or any other component to meet

the functional and technical requirements would be proposed by the bidder in advance,

however HUDA will procure the same licenses from government agency/HARTRON and

ownership for installation, configuration, implementation, commissioning and coordination

required during OEM support will be with the SI.

10. The web/Application server & database server should be in different zones behind the firewall

(Dedicated or common firewall).

11. The solution/ application should function properly across browsers including but not limited to;

Internet Explorer, Safari, Firefox, Chrome.


48 | P a g e

12. The developed solution/application should be able to achieve as minimum, the following

parameters:

a. Average page loading time (time taken between click of the link to the complete loading

of the page) should be less than 2 seconds for all static pages and below7 seconds for

pages with dynamic data intensive pages

b. Average time for Internal User Login on application should be under 3 seconds

c. Average time to throw by results of queries by the internal users of application should

be under 5 seconds

4.3 Functional requirements of the Modules

This Section describes the Functional requirements of all the module i.e. Financial Accounting,

Plot and property management, Web portal and Court case tracking system

These high level functionalities are based on the current application system and processes

involved. These functionalities are elaborated to aid the bidder to understand the scope of work

and to come up with realistic implementation approach and estimates of time and cost. The

bidders is required to study the system requirements themselves during the system study phase

and get knowledge about the workflows and business processes to be automated by the

proposed applications. The Functional Requirements of the modules are described in document

at Annexure A, B, C and D.

4.4 Mobile Application Development The bidder should also develop Mobile application for its portal www.huda.org.in with the

following main objectives:

To ensure compliance with “Guidelines for Indian Government Websites (GIGW)”. To

integrates easy to use content management system for easily managing overall content

of the website.

To make Mobile Apps accessible on all platforms like windows, Android, Blackberry &

Mac iOS etc.

To provide information to citizens with minimum number of clicks.

To get security certificate from TPA.

Citizens can make their payments online through mobile application.

Citizens can receive the alerts and notifications through mobile application.

Development of consistent visual elements and Mobile Apps architecture that is

scalable and expandable and W3 compliant

Enhance the presentation of the content so that they sync with the growth oriented

approach of the Authority.



49 | P a g e

The SI will ensure that the development of the overall mobile application will be as per the FRS&

SRS finalized with the Department.

4.5 Application Development

4.5.1 KICKOFF

The SI will have a project Kickoff meeting with HUDA officials and present a High Level Plan for

development of the Solution.

4.5.2 PROJECT PLAN

The System Integrator (SI) shall develop a Project Plan, in collaboration with HUDA within 4

weeks of the commencement of services describing all the elements of project management

work detailing the scope and schedule.

The Project Plan developed by the SI should specify the schedule of various tasks, deliverables

and deployment of resources. This plan shall be submitted to HUDA for review and approval.

The Project Plan shall address, at the minimum, the following:

1. Description of the SI’s organization with their proposed staffing, roles and

responsibilities.

2. Project Organization and Communication structure.

3. Prepare a detail risk management plan

4. Security and confidentiality practices in accordance with industry best practices to ensure

the security and confidentiality of information, documents, records, software, data,

reports, deliverables etc. handled during the entire project and subsequently.

5. Define an organized set of activities for the project and identify the interdependencies

between them.

6. Project plans and schedules giving details of various tasks, task durations, dependencies,

deliverables, milestones, resource deployment, meetings, reviews and information

required from the HUDA.

7. Resource planning and deployment for each phase/activity. Resource planning must also

indicate where each resource would be based during that phase, i.e., onsite at the HUDA

or offsite at the SI premises.

8. Establish and manage resource assignments and responsibilities.

9. Highlight the milestones and associated risks.

10. Manage project deadlines and performance objectives.


50 | P a g e

11. Communicate the project plan to stakeholders with detailed reports

12. Training plan for user acceptance tests and other related training during rollout for the

department identified user. The plan shall include description of training, man-days of

training etc.

13. The Project Plan should be updated every quarter in consultation with HUDA.

14. Bidder will be help and extend the support to integrate database, application, and mobile

application with Analytics tool deployed at HUDA.

During the project implementation the SI shall report to HUDA, on following items:

1. Results accomplished during the period (fortnightly).

2. Cumulative deviations to date from the schedule as specified in the finalized Project Plan.

3. Corrective actions to be taken to return to planned schedule of progress.

4. Proposed revision to planned schedule provided such revision is necessitated reasons

beyond the control of SI.

5. Other issues and outstanding problems, and actions proposed to be taken.

6. Identify the activities that require the participation of client personnel (including HUDA,

the Program Management Unit etc.) and communicate their time requirements and

schedule early enough to ensure their full participation at the required time.

SI will be required to submit following documents:-

1. Baseline Project Plan

2. Planning Assumptions & Constraints, critical success factors, benchmarks, and performance

measures

3. Risk management plan

4. Reporting framework

5. Communications plan

6. Training plan

4.5.3 REQUIREMENT TRACEABILITY MATRIX

Selected SI shall be responsible for maintenance of a Requirement Traceability Matrix

through-out the project.

Selected SI would ensure that overall solution is fully compliant with the requirements and

specifications as mentioned in the RFP. For ensuring this, SI shall prepare a Requirements

Traceability Matrix on the basis of Functional Requirements and Technical Requirements

provided by HUDA (updated by selected SI as necessary) and the System Requirements

Specifications (SRS) prepared by Selected SI.


51 | P a g e

This matrix would keep track of the requirements and trace their compliance through

different stages of the project including software design, coding, unit testing, integration

testing, user acceptance testing and final acceptance testing. The requirements traceability

matrix would be a live document throughout the project, with the SI team updating the

matrix at every stage to reflect the compliance of each specification at every stage.

Through the duration of the project, HUDA will periodically review the Traceability Matrix.

HUDA would provide the final approval once they are satisfied that all requirements are met.

4.5.4 DESIGN SOFTWARE SOLUTION

4.5.4.1 System Study

1 The SI will undergo a KT phase during which the details of the existing applications will be

explained. The KT by the vendor shall cover the following aspects:

a. A description of the functionality of the module

b. Design and coding aspects of the module – including the names of the files, sequence of

function/procedure calls, names of the methods.

c. The integration of this module with other modules.

d. Importance of the module vis-a-vis the other modules.

e. Database details related to the module if any.

2 Through the information gathered through the KT phase and its own analysis, the SI shall

carry out a detailed systems study to prepare/ refine the functional requirements and

formulate the final System and Software Requirements Specifications documents.

3 HUDA reserves the right to modify the functional requirements in certain cases to the

extent that the overall effort remains the same. HUDA may also change the sequence of

tasks and activities or certain modules to suit the needs of the department or the project.

4 As part of the preparation of SRS, the selected SI shall be responsible for preparing and

submitting detailed requirement specification documents as per IEEE or equivalent

standards which meets all the Business, Functional and Technical requirements of the

departments concerned. The SI shall prepare the SRS documents and have it reviewed and

approved by the Department.

5 The selected SI is required to update the FRS / SRS as and when any enhancements

modifications are made to the overall solution till the duration of the Contract, including

AMC Phase


52 | P a g e

4.5.4.2 Solution design

1. The selected SI shall design an integrated solution architecture & specifications for meeting the

System Requirement Specifications, finalized by the SI and approved by HUDA. The solution

designed should have seamless integration of all the components comprising of the solution

being designed. The solution design shall include, but shall not be limited to, the design of the

application architecture, user interface, database structures, security architecture, network

architecture etc. The principles of Service Oriented Architecture shall be followed while

designing the systems.

2. The architecture should be proven to be scalable (cater to increasing load of internal and

external users and their transactions) and capable of delivering high performance for at-least

three years from the date of deployment. In this context, it is required that the application and

deployment architecture should provide for Scale-Up and Scale out on the Application and Web

Servers, Database Servers and all other solution components.

3. The selected SI would have the overall responsibility for development/customization,

integration, testing and rollout of all components of the project. The SI shall provide the overall

solution as per the defined scope of work and provide the required manpower for the project

and its components.

4. All the applications will be designed using a multi-tier architecture.

5. As part of the solution design phase the SI will prepare Detailed Design documents which shall

include:

a. Business process maps

b. Functional requirement Document

c. High Level Design Document

d. Low Level Design Document

e. Software requirement document

6. SI shall prepare a Requirements Traceability Matrix on the basis of Functional Requirements

and Technical Requirements created/updated by selected SI and the System Requirements

Specifications (SRS) prepared by Selected SI

7. The SI shall also design a testing strategy during design phase. The selected SI shall design the

Testing strategy including traceability matrix, Test cases and conduct testing of various

components of the software developed/customized for Project. The software testing shall

include Unit Testing, System Testing, Performance Testing, Integration Testing etc. following

documents to be submitted

a. Test strategy document

b. Creation of test plan and test cases.

8. The SI shall also prepare the data migration strategy and plan for smooth migration of data

from current environment to new environment.


53 | P a g e

4.5.5 SOLUTION DEVELOPMENT

1. The SI will ensure that the development of the overall solution will be as per the FRS and SRS

finalized with the Department.

2. All Requisite Hardware for Development shall be provided by HUDA as per SRS Finalised with SI

3. SI will set up and configure the development environment.

4. A standard methodology e.g. Agile/scrum shall be adopted for software engineering. Any future

requirements like change in processes or any modification in the application will also need to be

taken into account at the time of developing the Software.

5. If there is any requirement of any additional software license or any other component to meet the

functional and technical requirements would be proposed by the bidder, however HUDA will

procure the same licenses from government agency/HARTRON and ownership for installation,

configuration, implementation, commissioning and coordination required during OEM support will

be with the SI.

6. SSL certificates supporting 256 bit encryption shall procured by the bidder for Web Portal

Application.

7. The selected SI shall be responsible for enabling all the functionalities as defined in the overview of

Functional Requirements. These requirements provide brief on the functional requirements for

various modules of the solution, and the processes that needs to be enabled by the system.

8. The SI will unit test the developed software and do integration testing.

9. SI will provide the rights to developed code after QA to HUDA

10. The selected SI shall set up separate environment at HUDA HQ, Panchkula office for development,

performance testing, and UAT

4.5.6 TESTING

1. The selected SI shall enable all necessary tools and software for enabling various stages of testing.

This would include functional testing as well as stress/ performance/load testing.

2. The selected SI shall make all necessary arrangement for testing including but not limited to

(integration, system, functional, user acceptance, and final acceptance testing) and preparation of

test scripts, test data, etc.

3. The selected SI shall obtain the sign-off from HUDA on testing approach and plan. The SI shall

perform the testing of the solution based on the approved test plan, document the results and shall

fix the bugs found during the testing. Though HUDA is required to provide formal approval for the

test plan, it is the ultimate responsibility of SI to ensure that the end product delivered by the

selected SI meets all the requirements (including functional and technical requirements) of the

Project.

4. As this project involves both the development and hosting of the applications, the following points

related to Acceptance, Certification and Roll out shall be considered:-


54 | P a g e

5. An acceptance test plan along with test cases and expected results traced to the requirements shall

be provided during the development and the same shall be accepted by the Department.

6. Any observations/feedback from the Department related to the test plan and test cases shall be

duly factored in as relevant.

7. Department shall constitute a team of users who will facilitate the test process, butthe bidder’s

personnel shall carry out the tests.

8. The errors identified during testing, shall be duly rectified and resolved. Maximum of three rounds

of testing shall be permitted.

9. The pre-requisite for the software to be accepted is that it should have ZERO Severity Level defects

certified by third party auditor engaged by HUDA.

4.5.6.1 User Acceptance Testing

The selected SI shall perform User Acceptance Testing (UAT) and load testing before

Commissioning of the system. The test cases for UAT shall be prepared by the selected SI and

submitted to HUDA for approval.

1. Bugs/defects detected during acceptance testing in developed custom components

should be rectified by the bidder.

2. On successful completion of the user acceptance testing, User Acceptance Sign off

certificate will be provided by HUDA.

4.5.6.2 Performance Testing

Endurance testing

The applications have to be tested which involves testing a system with a significant load

extended over a significant period of time, to discover how the system behaves under

sustained use. The applications have to be stress tested to ensure that they are able to

perform robustly under below load conditions

S.No Applications Load conditions

1 PPM & FAS Application 2000 concurrent users; 10,000 total users

2 Citizen web portal 5,00,000 total users

3 CCTS application 5000 Concurrent user; total users 10,000

The User Acceptance Testing and the performance testing will be performed in separate

environments.

Following reports are to be submitted during testing phase


55 | P a g e

a. Test Plans

b. Test Results

c. Bug reports

d. Regression test results

e. Updated traceability matrix

f. UAT Signoff

4.5.7 TRAINING

Bidder to conduct training for the following User Groups (approximately 150 individuals) HUDA:

1. Database Administrators (Minimum 2 users) – HUDA will identify Database administrators to

be trained. The bidder will train these resources on the overall and basics of troubleshooting

and coordination. The bidder to bring out clearly the description of training, man-days of

training etc.

2. Application Management (Minimum 15 users) – HUDA will identify a set of resources to be

trained in the application development and maintenance. Bidder to bring out clearly the

description of training, man-days of training etc.

3. End User Training (Minimum 100 Users) - For the pilot phase, bidder shall train all target

employees under the Pilot Phase for the identified pilot locations. Training should be provided

for all the modules. Bidder to bring out clearly the description of training, man-days of training

etc.

4. Train the Trainers (Minimum 30 Users)-Bidder shall be responsible for conducting train the

trainers training for identify user group in HUDA. Bidder to bring out clearly the description of

training, man-days of training etc.

Training should be conducted in batches with a batch of maximum 25 people.

HUDA will arrange the logistics of training room etc. but the bidder will arrange for the travel

and stay of their trainer as per schedule.

4.5.7.1 Testing & Evaluation:

SI shall conduct tests for the evaluation of trainees at the end of training session. This will help

HUDA management team to assess the effectiveness of the training and its intake by the

trainees. The results will be published as an evaluation report.

SI shall also collect a feedback from trainees which will include questions about their self-

assessment to conduct the classes, satisfaction for the training material and faculty,

enhancement suggestions etc.


56 | P a g e

If the 50% or more batches score less than 75% score in the evaluation, SI will re-train the

entire batch.

4.5.8 PILOT GO-LIVE

The project will roll-out in two phases namely Pilot Go-Live and Go-Live. In the first phase

(Pilot Go-Live), HUDA main administrative offices will be covered namely: Panchkula,

Faridabad, Gurgaon, Hisar and Rohtak.

1 All requisite Hardware for production environment will be provided by HUDA. Production

environment will be hosted at SDC, Haryana

2 SI will Set up and configure the Production environment

3 SI will migrate all data from the test environment to production environment

4 HUDA will assign a third party Auditor to conduct application and performance audit before

Go-Live. The SI shall close all gaps/defects/bugs mentioned in the TPA reports.

5 SI shall conduct validation tests on migrated data and obtain signoff for the same from

HUDA

6 Issue of acceptance certificate from all Administrative offices shall be considered as

successful PILOT Implementation

7 The SI will be required submit a go- live Plan to initiate the go live phase.

4.5.9 THIRD PARTY AUDIT

After Development of the solution the SI shall provide assistance to HUDA team in undertaking

Security Audit of the developed application by third party external agency selected by HUDA

and undertake the following activities:

1. Ensure developed application is free from Vulnerability / bugs / defects etc. mandatory

for clearing Security Audit as per the direction of 3rd Party Agency.

2. Share all the relevant documents like FRS / SRS / Test Cases as required by the third

party external agency

3. Incorporate desired changes in the developed application software suggested by the

third party external agency

The basic responsibility of testing the system lies with the SI. The functional testing by a 3rd

Party agency appointed by HUDA is for the purpose of certification. SI shall provide all the

necessary support to the agency in conducting the functional Testing services.

The Selected SI shall ensure the following points are duly addressed for successful completion of

audit certification:

Application audit will include:

1. Functionality audit that will map the functionality delivered to the FRS agreed upon

during development phase.


57 | P a g e

2. Determine systematic measures implemented to control and secure access to the

application programs and data including password controls, user authentications, roles

and responsibilities, audit trails and reporting, configuration and interface controls, etc.

3. Review of database structure including:

a. Classification of data in terms of sensitivity & levels of access

b. Security measures over database installation, password policies and user roles and

privileges

c. Access control on database objects – tables, views, triggers, synonyms, etc.

d. Database restoration and recoverability

e. Audit trails configuration and monitoring process

f. Network connections to database

4.5.10 GO- LIVE

1. Go-Live is the Successful roll out of application in all HUDA estate offices with all

functionalities achieved, zero defects (from the test cases signed off with HUDA) and go-

live signoff received from HUDA.

2. SI will prepare a detailed operations and management plan and resource plan. HUDA will

approve operations and management plan and resource plan. The development team shall

hand over the entire applications to the operation team.

3. SI will perform any new Changes/Modification for a period of 4 months after Go-Live at no

additional cost to HUDA.

4. SI will prepare a three year product evolution plan with future risk and dependencies.

PART B – Operations & Maintenance Phase

4.6 Operations and Maintenance (Post Go-live AMC)- Part B

4.6.1 APPLICATION AND SOFTWARE MANAGEMENT

The selected SI shall be responsible for the day to day maintenance of the applications for the

entire period of Contract of three years after the date of commissioning. During this phase, the

selected System Integrator shall deploy the required resources (at least 3) onsite fulltime at

HUDA premises. For the Up Graded/developed applications as part of this RFP, the selected SI

will be responsible for smooth Operations and Maintenance Services for the period covering

onsite support for 3 years of AMC from the date of Go-Live of the developed/Up-graded

Applications covering the following:

1. Resolve any bugs reported by HUDA IT support team.

2. Resolve usage issues.


58 | P a g e

3. Resolve performance and other related issues, tweaking and tuning on regular basis.

4. Resolve application access related problems.

5. Creation, customization, updating of reports as and when required.

6. Any new Changes/Modification/Updating/Formatting in input and output screens/ forms/

process/ reports because of change in user/functional/legal/business requirements.

7. Optimization of stored procedures.

8. Bug fixing, ensuring smooth access of application from / through relevant mode.

9. Management of database like addition/deletion of tables/columns, uploading of data,

generation and analysis of reports, transaction logs monitoring. However, HUDA will

responsible for administration of database.

10. Bidders are free to provide best solutions/practices to increase the

performance/efficiency/optimization of application.

11. Close Coordination with HUDA IT team for smooth and timely application execution

12. Closure of issues arising out of Security Audit

13. Generation of regular reports in relation to SLA’s and transactions on a daily, weekly, monthly

basis or as agreed with HUDA

14. Application and database backups

15. Updates to all software components with the latest patches/version upgrades, as released by

the concerned OEM players from time to time.

16. Bidder will be help and extend the support to integrate database, application, and mobile

application with Advanced Analytics tool deployed at HUDA.

4.6.2 DATABASE ADMINISTRATION AND TROUBLESHOOTING

Undertake end-to-end management of database on an on-going basis to facilitate smooth

functioning and optimum utilization including regular database backup and periodical testing of

backup data, conducting configuration review to tune database, maintaining the necessary

documentation and managing schemes to database schema, disk space, user roles, and

storage.

4.6.3 SOFTWARE CHANGE & VERSION CONTROL

All planned changes to application systems shall be coordinated within established Change

Control processes to ensure that:

1. Appropriate communication on change required has taken place

2. Proper approvals have been received

3. Schedules have been adjusted to minimize impact on the production environment

SI shall define the Software Change Management & Version control process and obtain

approval for the same from HUDA. For any changes to the software, SI has to prepare detailed


59 | P a g e

documentation including proposed changes, impact to the system in terms of functional

outcomes/additional features added to the system etc. SI shall obtain approval from HUDA for

all the proposed changes before implementation of the same into production environment and

such documentation is subject to review at the end of each quarter of operations &

maintenance support.

4.6.4 MAINTAIN CONFIGURATION INFORMATION

Maintain version control and configuration information for application software and any

system documentation.

4.6.5 MAINTAIN SYSTEM DOCUMENTATION

1. Maintain and update documentation of the software system. SI shall ensure that:

2. Source code is documented

3. Functional specifications are documented

4. Application documentation is updated to reflect on-going maintenance and enhancements

including FRS and SRS.

5. User manuals & training manuals are updated to reflect on-going changes/enhancements.

6. Standard practices are adopted & followed for version control and management.

4.6.6 OTHER RESPONSIBILITIES

1. Undertake preventive maintenance (any maintenance activity that is required before the

occurrence of an incident with an attempt to prevent any incidents) and carry out the

necessary repairs and replacement of parts wherever needed to keep the performance levels

of the hardware and equipment in tune with the requirements of the SLA. Such preventive

maintenance shall not be attended during working hours, unless inevitable and approved by

the HUDA

2. Undertake reactive maintenance (any corrective action, maintenance activity that is required

post the occurrence of an incident) that is intended to troubleshoot the system with sufficient

teams

3. Escalate and co-ordinate with its OEMs for problem resolution wherever required

4. The selected SI will be required to comply with various policies relating to monitoring and

management of infrastructure such as IS Policy, backup and archival policy, system software

update policy etc. of HUDA

5. Application and Database backups and patch management

Following are the minimum deliverables for the entire AMC phase


60 | P a g e

a. Issue tracker reports

b. Monthly Activities and Status Reports

c. Application Availability Reports

d. SLA compliance reports

4.7 Timelines & Milestones

A project phase would be considered successfully completed when all activities and deliverables

pertaining to that phase (as detailed below) have been approved by HUDA.

S.No. Project

Phase

Required Activities Deliverables Timeline

1 Kick off Project kick–off meeting

High level project plan

Deliverable 1

a) High level project plan

T* + 1

Weeks

2 Planning Develop detailed Project Schedule and

Resource Plan

Develop Risk Management Plan

Develop Communication Plan

Develop Training plan

Develop system Change Management

Processes

Work environment, etc.

Deliverable 2

a) Baseline Project Plan

b) Planning Assumptions &

Constraints, critical success

factors, benchmarks, and

performance measures

c) Risk management plan

d) Reporting framework

e) Communications plan

T* + 3

Weeks

3 System

Study/De

sign

Establish environment

System Study

Process mapping

Functional requirement document

High Level Design

Low Level Design

Requirement Traceability Matrix

Software requirement document

Creation of test plan and test cases.

Identification of data migration

requirements

Preparation of data migration, strategy

and plan

Deliverable 3

a) Business process maps

b) Functional requirement

c) High Level Design

d) Low Level Design

e) Requirement Traceability Matrix

f) Software requirement

document

g) Test strategy and test Plan

h) Creation of test plan and test

cases.

i) Data migration, strategy and

plan

T* + 6

Weeks


61 | P a g e

S.No. Project

Phase


4 Develop

ment

Application Development along with

Mobile application

Unit testing

Integration Testing

Updation of traceability matrix

Deliverable 4

Developed code after QA

T* + 15

Weeks

5 Testing/

UAT

Detailed test plan including for Mobile

application

Setup test environment

Preparation of test data setup

Execute test & document results

Report the bugs

Bug fixing

Regression testing

Updation of traceability matrix

Error correction & retesting

Deliverable 5

a) Test Plans

b) Test Results

c) Bug reports

d) Regression test results

e) Updated traceability matrix

f) UAT Signoff

T* + 18

Weeks

6 Pilot Go-

Live

Setup of production Setup

Execution of data migration, strategy and

plan

Validation of migrated data

Preparation of Go-live plan

Training as per training plan

Deliverable 6

a) Production environment

b) Signoff of data migration

c) Training

d) Go-Live Plan

T*+ 22

Weeks

7 Third

party

Audit

Close all the audit findings. Deliverable 7

a) Audit Closure Report

8 Go-Live Go-live signoff from User.

Conduct post-implementation

review/audit

Detailed Operations and management

plan with resource details.

Prepare Lessons Learned Report

Prepare 3-Year product evolution plan

Deliverable 8

a) Operation and Management

Plan

b) Operations and Management

Resource Deployment plan

c) Three Year product evolution &

resource plan

T* + 27

Weeks


62 | P a g e

S.No. Project

Phase


9 Annual

Mainten

ance

Regular Updating of the HUDA web portal

as per directions of HUDA

Software maintenance, including

preventive maintenance and

troubleshooting problems reported

User support to HUDA staff and officers

Making the applications compatible with

all the major browsers, whenever a new

version is introduced

Software support for new features to be

developed or modifications in the Portal

application, Plot and Property

Management and Financial Accounting

System, using dedicated onsite

manpower, as per user’s feedback OR

Policy Changes.

Suggest and implement new features on

the applications keeping user’s

convenience in mind.

Database administration and trouble-

shooting

Maintaining system documentation

Source code

Function specifications document

User manual & Training manuals

Update FRS &SRS

Review meetings with Senior

management of the bidder- at least once

in a month

Closure of issues arising out of Security Audit.

Deliverable 9

a) Issue tracker reports

b) Monthly Activities and Status

Reports

c) Application Availability Reports

d) SLA compliance reports

Monthly

For Next 3

years post

Go live

phase


63 | P a g e

S.No. Project

Phase


10 Exit

Manage

ment

A detailed program of the transfer

process that could be used in

conjunction with a Replacement System

Integrator including details of the means

to be used to ensure continuing

provision of the services throughout the

transfer process or until the cessation of

the services and of the management

structure to be used during the transfer.

Plans for the communication with the

System Integrator's sub-contractors,

staff, suppliers, customers and any

related third party as necessary to avoid

any material detrimental impact on the

HUDA’s operations

The System Integrator shall re-draft the

Exit Management Plan annually

thereafter to ensure that it is kept

relevant and up to date

Deliverable 10

a) Exit Management Plan

T*+ 8

Weeks,

and then

updated

Annually.

*T is Contact Signing Date

N.B. Kindly note that Deliverable 1 – 8 are the deliverable comprising the scope in PART A – Up-

Gradation of Existing HUDA Applications. Deliverable 9&10 are the part of scope in PART B – Post

Go-Live Support (AMC).

The deliverables mentioned above are the minimum required deliverables. HUDA can ask for further

submission of reports and deliverables (except from the one already mentioned above) from the SI

as per need requirements according to the phases mentioned above.

4.8 Payment Schedule The payments shall be released post acceptance of the submitted complete Deliverables for

respective project phases as mentioned in section 4.7 above.

Every attempt will be made to make timely payments post the relevant sign offs and relevant

documentation being submitted for respective project phases as mentioned in section 4.7 above

and calculation of penalty applicable as per Section 4.9


64 | P a g e

Table 1.1

S. No Milestone Payment %

1. Mobilization

Successful completion of Kickoff phase as

defined in Section 4.7above

10 % of Total contract value

2. Study/Design

Successful completion of Planning and

System Study/Design phase as defined in

Section 4.7 above


3. Completion of UAT (testing)

Successful completion of Development

and Testing/UAT phase as defined in

Section 4.7 above


4. Pilot Go-Live*

Successful completion of Pilot Go-Live

phase as defined in Section 4.7 above


5. Closure of TPA gaps

(Implementation)

Successful completion of Third party Audit

phase as defined in Section 4.7 above


6. Go – Live**

Successful completion of Go-Live phase as

defined in Section 4.7 above


7. Operation & Maintenance

Successful Completion of Annual

Maintenance phase as defined in Section

4.7 above

40% of total contract value equated quarterly for

12 quarters

*Pilot Go-Live is a successful roll out of all modules of application in HUDA main administrative offices namely:

Panchkula, Faridabad, Gurgaon, Hisar and Rohtak.

** The date on which the proposed solution becomes operational after successful conclusion of all acceptance tests to

the satisfaction of HUDA


65 | P a g e

4.9 Service Level Agreement

Service Level Agreement (SLA) will form part of the contract between HUDA and the SI. SLA

defines the terms of the SI’s responsibility in ensuring the timely delivery and the compliance to

the Performance Indicators as detailed in this document. The SI has to comply with Service

Levels requirements to ensure adherence to timelines, quality and availability of products /

service. The purpose of this Service Level Agreement to clearly define the performance criteria

that shall be adhered to by the SI for the duration of the project.

Project performance is mapped to the achievement of milestones listed below. The SI is

expected to achieve the milestones as mentioned in the Section 4.7 Timelines & Milestones.

Any deviation to this due to reason attributed to the SI shall be considered as breach of SLA and

penalties shall be applied accordingly.

4.9.1 PART A – IMPLEMENTATION OF ALL APPLICATIONS OF HUDA

S. No Major Area Parameter Requirements Penalty

1 PART A –

Implementation

Phase

Completion of each Phase

Kick off

Planning

System Study/Design

Development

Testing /UAT

Pilot Go-Live

Third party Audit

Go- Live

As per

timelines in the

Section 4.7

Delay of each week

will result in the

recurring penalty of

1 % of the total

contract value. The

maximum penalty to

be capped at 10% of

the total contract

value.

HUDA may carry out

the work at the risk

and cost of SI if they

fail to achieve the

milestone with

reasonable period or

period decided by

the department.

Time extension can

be considered if the

delay is not on the

part of the SI.


66 | P a g e


2 Resource

Deployment

Deployment of on-site resources as

per the RFP - TQ 4

Within 30 days

of issue of

Letter of

Award.

Rs.3000/- per day

per resource will be

levied on the bidder.

3 Resource

availability

Availability of on-site resources as

per the RFP - TQ 4

Non-availability

of resource

without

information/ap

proval of client.

0.1% per working

day per resource of

the total contract

value. The maximum

penalty to be capped

at 20% of the total

contract value.

4.9.2 PART B – OPERATIONS & MAINTENANCE PHASE - AMC POST GO-LIVE

1. This agreement is effective on the Go-Live Date, and is in effect until SLA is terminated by

either party.

2. SI will create/update/track/close requests for Modification/update/change in application

along with timelines.

3. SI will generate of regular reports in relation to SLA’s and transactions on a daily, weekly,

monthly basis or as agreed with HUDA

4. Breach of SLA because of dependency on HUDA or because of Hardware fault/ issues/

non-availability shall not account to the SI

5. SLAs would be monitored on a quarterly basis and penalties would be imposed, in case of

breach of any of the SLAs and the same would be deducted from the Quarterly Payment

(QP).

6. On breach of any of the SLAs in a quarter, a penalty would be levied on the quarterly

payment due to System Integrator/Successful bidder. For each breach a penalty of 3% of

the quarterly payment due would be levied, with a maximum penalty not exceeding 10%

of the quarterly payment.

7. The amount of penalty under this Contract shall not exceed 10% of total contract value in

case of non-compliance with SLAs.

8. In case of more than 10 breaches in a quarter or breach of a particular SLA metric

consecutively in 2 (two) quarters, the System Integrator has to provide the reasons for

such breaches to HUDA in writing. In case of non-satisfactory reasons, HUDA shall have

the right to invoke full Performance Bank Guarantee and/ or call for termination of


67 | P a g e

contract. For calculation of Penalty the total equated quarterly installments as

mentioned in the Payment schedule will be considered.

9. HUDA will arrive at the quantum of breaches and applicable penalties as per the terms &

conditions of tender document before every due payment. The same will be

communicated to the System Integrator, in case of the disagreement the System

Integrator would need to provide the justification in writing within one week to HUDA.

Based on the justification given by System Integrator, HUDA would invoke/relax the

penalty(ies) depending upon the merit of the case. The decision of HUDA will be final and

binding for all such cases.

10. Non-availability of resource without information/approval of client during the AMC

phase shall attract a penalty of 0.1% per working day per resource of the total contract

value.

Service Level Monitoring (SLM)

The Service level monitoring parameters on which the SLA shall be applicable are as under.

The SLM’s will be measured on the basis of MIS reports generated from the monitoring

system, maintained and operated by the System integrator

S. No. Metric Expected Service Level Remarks

SLM1 Solution/ Application

availability at central

location.

>=99.5% Statistics for SLA Monitoring

to be provided by the

System Integrator

Application has to be

available 24x7

“Application& Mobile App

availability" shall mean the

time period for which the

specified application is

Available to the internal and

external users of the

system.

Application and Mobile App

non availability due to

downtime because of

bugs/vulnerability/security

non-compliances/non-

functioning of intended

service/services shall be

accounted to SI

Hardware related

downtime shall not be

accounted to the SI.


68 | P a g e


Slippage

For 0.1- 5% = 1

breach

For 5-10% = 2

breach

For > 10% = 3

breach

SLM2 Average Time taken for

closure of bugs and

configuration changes in

the Solution/ application

Not later than 4 days or

Within mutually agreed

timelines between HUDA

and SI.

1 breach every 8 hours over

4 days after approval or

mutually agreed timeline

SLM3 Time taken to update

the content, press

releases, news, notices

and tenders etc. and

other important items

on web portal.

Not later than 2 days or

within mutually agreed

timelines between HUDA and

SI

HUDA would require certain

updates for circulars /

notifications to be uploaded

on urgent basis the

turnaround time for which

would be less than 2 days. 1

breach if task is not

completed within agreed

timelines

SLM4 For vulnerability attacks

due to which the whole

website is defaced/not

available /content

changed/redirected

Restore website Within 8

hours

Detection of Vulnerability

and information of same to

website administrator and

department officials within

30 minutes

Action must be taken to

restore the website

within 8 hours of

reporting/detection of

such incident, else it

would be considered as a

breach.


69 | P a g e


SLM5 Patch Management (for

application, mobile app,

software and

Database)

Within approved time

window of HUDA’s approval

a) Testing has to start

within 1 working day of

release of patch subject

of approval of HUDA

and availability of

system downtime. In

case of non-availability

of downtime, a

mutually agreed

timeline between

selected SI and HUDA

shall be applicable.

b) Results of testing along

with recommendations

should be submitted to

HUDA for approval

c) 1 breach if patch is not

implemented within 3

days of receiving

approval from HUDA

SLM6 Solution (including

Application, mobile

app and database)

Backup

Service

SI should ensure that the

back-up taken is

complete, consistent and

correct.

The selected SI shall be

required to take daily

backups and implement

replication as per agreed

benchmark. Every instance

of non-replication of

backup is 1 breach

SLM7 Compliance Reports,

SLA monitoring reports

The bidder has to

establish a reporting

framework which

includes various reports

formats as well as their

reporting frequency

along with HUDA.

The reports should be

provided as per agreed

framework timelines.

Delay of every 5 days =

1 breach,


70 | P a g e

Resource Deployment/Availability SLM


1 Resource

Deployment

Deployment of on-site

resources as per Operations &

Maintenance resource

deployment plan

Within 1 days

of Operations

& Maintenance

phase

Rs.3000/- per

day per resource

will be levied on

the bidder.

2 Resource

availability

Availability of on-site resources

Operations & Maintenance

resource deployment plan

Non-availability

of resource

without

information/ap

proval of client.

0.1% per

working day per

resource of the

total contract

value. The

maximum

penalty to be

capped at 20%

of the total

contract value.

4.9.3 UPDATING THE SERVICE LEVEL AGREEMENT

1. Any and all changes to the agreement will be initiated in writing between the HUDA and the SI.

The service levels in this agreement are considered to be standard for the HUDA and will only

be modified if both parties agree to an appended set of terms and conditions. However

decision of GM(IT) HUDA, shall be considered final and binding for both parties

2. This Service Level Agreement is not a fixed document to be produced once and used forever.

Instead, it must be re-evaluated and updated as the work environment changes. As technology

changes, the services and systems covered by this Agreement will change. New areas of

responsibility must be documented.

3. This document will be reviewed and revised annually. Changes to the Service Level Agreement

may be required at other times to include new systems, change in operating hours, etc.


71 | P a g e

5. GENERAL CONDITIONS OF CONTRACT

5.1 Use and Acquisition of Assets

During the Term the System Integrator shall:

1. Take all reasonable and proper care of the entire hardware and software, network or any other

information technology infrastructure components used for the Project and other facilities

leased/owned by the System Integrator exclusively in terms of the delivery of the Services as

per the Agreement (hereinafter the “Assets”).

2. Keep all the tangible Assets in good and serviceable condition (reasonable wear and tear

excepted) and/or the intangible Assets suitably upgraded subject to the relevant standards at

the date the System Integrator takes control of and/ or first uses the Assets and during the

entire term of the Agreement.

3. Provide a well-prepared documentation for users in the form of a user's manual, a clear plan

for training, educating and hand holding the users and shall form part of handholding phase

until bringing up the users to use software solution with speed and efficiency; and

4. Train the team identified by HUDA, which will be in place during hand-holding and will be

responsible for trouble shooting all post-implementation and maintenance activities.

5. To the extent that the Assets are under the control of the System Integrator, keep the Assets

suitably housed and in conformity with any statutory requirements from time to time

applicable to them; and

6. Not, knowingly or negligently use or permit any of the Assets to be used in contravention of

any statutory provisions or regulation or in any way contrary to law; and

7. Use the Assets exclusively for the purpose of providing the Services as appropriate; and

8. Transfer the ownership of the Assets (not already with HUDA which shall include the solution

and Software including the source code and associated documentation which is the work

product of the development efforts involved in the Project.) to HUDA at the appropriate time

(in synchronization with the submission of deliverables thereof) or in accordance with the

terms of the agreement; and

9. Ensure the integration of the software with the existing hardware in order to ensure the

smooth operations of the entire solution architecture to provide efficient services to all the

Stakeholders of this Project in an efficient and speedy manner; and


72 | P a g e

10. Obtain a sign off from HUDA or its nominated agencies at each stage as is essential to close

each of the above considerations.

5.2 Access to the Department’s or it’s Nominated Agencies’ Location

For so long as the System Integrator provides Services from HUDA office location on a non-

permanent basis and to the extent necessary for the System Integrator to provide the Services

and at no cost to the System Integrator, HUDA, shall, subject to compliance by the System

Integrator with any safety and security guidelines which may be provided by HUDA and notified

to the System Integrator in writing, provide the System Integrator with:

1 Reasonable access, to HUDA / Departmental locations for as much time as deemed necessary for

delivery of services; and

2 Access to office equipment as mutually agreed and other related support services in such location

and at such other HUDA location, if any, as may be reasonably necessary for the System Integrator

to perform its obligations hereunder and under the SLAs.

3 Locations and items shall be made available to the System Integrator on an "as is, where is" basis by

HUDA. The System Integrator agrees to ensure that its employees, agents and contractors do not

use the location, services and items:

a. For the transmission of any material which is defamatory, offensive or abusive or of an obscene

or menacing character; or

b. In a manner which constitutes a violation or infringement of the rights of any person, firm or

company (including but not limited to rights of copyright or confidentiality); or

c. In violation of the provisions of any law in force in India.

5.3 Measurements and Arithmetic Conventions

All measurements and calculations shall be in the metric system and calculations done to 2

(two) decimal places, with the third digit of 5 (five) or above being rounded up and below 5

(five) being rounded down except in money calculations where such amounts shall be rounded

off to the nearest INR

5.4 Confidentiality

Subject to the other provisions of this RFP, information relating to evaluation of proposals and

recommendations concerning award of contract shall not be disclosed to the bidders who

submitted the proposals or to other persons not officially concerned with the process.


73 | P a g e

5.5 Data Protection

1. In the course of providing the Services, the System Integrator may be compiling, processing and

storing proprietary HUDA Data relating to the allottees.

2. The System Integrator and each user are responsible for complying with its respective

obligations under the applicable data protection laws and regulations governing HUDA data.

3. The System Integrator shall not transfer any HUDA Data unless otherwise authorized by HUDA

in this regard.

5.6 Conflict of Interest

1. The System Integrator shall hold HUDA’s interests paramount, without any consideration for

future work, and strictly avoid conflict of interest with other assignments or their own

Departmental interests. If during the period of this Agreement, a conflict of interest arises for

any reasons, the System Integrator shall promptly disclose the same to HUDA.

2. The System Integrator shall also cause its personnel and subcontractors not to engage either

directly or indirectly, in any business or professional activities that would conflict with the

activities assigned to them under or pursuant to this Agreement.

5.7 Fraud & Corruption

5.7.1 DEFINITIONS:

It is HUDA’s policy to require that HUDA as well as the System Integrator observe the highest

standard of ethics during the execution of this assignment. In pursuance of this policy, HUDA

defines, for the purpose of this provision, the terms set forth below as follows:

1. “corrupt practice” means the offering, receiving or soliciting directly or indirectly, or anything

of value to influence the action of a public official in the selection process or in the agreement

execution;

2. “fraudulent practice” means a misrepresentation or omission of facts in order to influence a

selection process or the execution of an agreement;

3. “collusive practices” means a scheme or arrangement between two or more bidders, with or

without the knowledge of HUDA, designed to establish prices at artificial, non-competitive

levels;

4. “Coercive practices” means harming or threatening to harm, directly or indirectly, persons or

their property to influence their participation in a selection or procurement process, or affect

the execution of an agreement.


74 | P a g e

5.7.2 MEASURES TO BE TAKEN BY THE HUDA

1. Notwithstanding anything else contained in this document, HUDA may terminate the

agreement if it finds that the representatives of the System Integrator, were engaged in

corrupt, fraudulent, collusive or coercive practices during the selection process or the execution

of the Agreement, and the System Integrator having failed to take timely and appropriate

action satisfactory to HUDA to remedy the situation;

2. HUDA may also impose sanctions against the System Integrator, including declaring the System

Integrator ineligible, either indefinitely or for a stated period of time, to be awarded a contract

if at any time it determines that the System Integrator has directly or through an agent,

engaged in corrupt, fraudulent, collusive or coercive practices in competing for, or in executing,

a HUDA financed contract.

5.7.3 COMMISSIONS AND FEES

At the time of execution of the Agreement, the System Integrator shall disclose any

commission or fees that may have been paid or is agreed to be paid to agents, representatives,

or commission agents with respect to the selection process or execution of the Agreement. The

information disclosed must include at least the name and address of the agent, representative,

or commission agent, the amount and currency, and the purpose of the commission or fee.

5.8 Tax

1 HUDA or its nominated agency shall be responsible for withholding taxes from the amounts due

and payable to the System Integrator wherever applicable. The System Integrator shall pay for all

other taxes, duties or levies in connection with the Agreement, SLAs, and any other Project

Engagement Definition including, but not limited to, property, sales, use, excise duty, value-added,

goods and services, consumption and other applicable taxes, duties or levies.

HUDA or its nominated agency shall provide the System Integrator with the original tax receipt of

any withholding taxes paid by HUDA or its nominated agencies on payments under the Agreement.

The System Integrator agrees to reimburse and hold HUDA or any of its nominated agencies

harmless from any deficiency (including penalties and interest) relating to taxes that are its

responsibility under this paragraph. For purposes of the Agreement, taxes, duties or levies shall

include taxes, duties or levies incurred on transactions between and among HUDA, the System

Integrator and third party subcontractors.

2 In the event of any increase or decrease of the rate of taxes, duties or levies, changes in currency

exchange rates etc. due to any statutory notification/s during the Term of the Agreement the

consequential effect shall be to the account of the HUDA.

3 The Parties shall cooperate to enable each Party to accurately determine its own tax liability and to

minimize such liability to the extent legally permissible.


75 | P a g e

5.9 Liquidated Damages

System Integrator shall commence the work and shall execute the project as per time frame

mutually agreed upon in the contract. If the completion of the project milestones is not

attained within the stated time, it would be dealt under section 4.8 of the RFP.

Further, HUDA shall arrive at the applicable penalties as per the SLA of Tender document

before every due payment. The same will be communicated to the System Integrator, in case

of the disagreement the System Integrator would need to provide the justification in writing

within one week to HUDA. Based on the justification given by System Integrator, HUDA would

invoke/relax the penalty(ies) depending upon the merit of the case. The decision of HUDA will

be final and binding for all such cases.

5.10 Penalties

In the event, the System Integrator fails to meet the project responsibilities including target

service levels as stipulated in the SLAs or any damages caused by System Integrator including

its employees, contractors, sub-contractors to HUDA properties, personnel, data etc., the

System Integrator shall be liable for penalty stipulated in the SLAs in terms of the SLA contained

in SLA Agreement section 4.9 of this RFP and any additional penalty towards the damages as

mentioned above. The total amount of penalty per “milestone or SLA” shall not exceed 10% of

total contract value. However, if the 10% penalty cap is reached by the System Integrator

twice, HUDA can terminate the contract, as per section 5.18.2

5.11 Indemnity

The Selected Bidder shall, subject to the provisions of the Agreement, indemnify the

DEPARTMENT for any third party claims causing direct loss or damage that is caused due to any

deficiency in services arising out of:

1. Breach of confidential information

2. Breach of IPR

3. Breach of applicable Law

4. Damage to property

5. Loss of life.

5.12 Limitation of Liability

Except in cases of criminal negligence or willful misconduct and Intellectual Property Rights

Indemnity claims:

1. Neither Party shall be liable to the other Party, whether in contract, tort, or otherwise, for

any indirect, special, incidental, exemplary, punitive or consequential loss or damage,


76 | P a g e

loss of use, loss of production, or loss of profits or interest costs, which may be suffered

by the other Party in connection with the Contract, other than specifically provided as

any obligation of the Party in the Contract, and the aggregate liability of the Bidder to the

HUDA, whether under the Contract, in tort or otherwise, shall not exceed the fee

received by the Bidder in the last twelve months immediately preceding date such

liability.

2. Contract, in tort or otherwise, shall not exceed the Contract Price, provided that this limitation

shall not apply to any obligation of the System Integrator to indemnify the HUDA with respect

to patent infringement

5.13 Personnel

1. Personnel assigned by System Integrator to perform the Services shall be employees of System

Integrator, and under no circumstances will such personnel be considered employees of HUDA.

System Integrator shall have the sole responsibility for supervision and control of its personnel

and for payment of such personnel's entire compensation, including salary, withholding of

income taxes and social security taxes, worker's compensation, employee and disability

benefits and the like and shall be responsible for all employer obligations under all applicable

laws.

2. System Integrator shall use its best efforts to ensure that sufficient System Integrator

personnel are employed to perform the Services, and that, such personnel have appropriate

qualifications to perform the Services. HUDA or its nominated agencies shall have the right to

require the removal or replacement of any System Integrator personnel performing work

under this Agreement. In the event that HUDA requests that any System Integrator personnel

be replaced, the substitution of such personnel shall be accomplished pursuant to a mutually

agreed upon schedule and upon clearance of the personnel based on profile review and

personal interview by HUDA or its nominated agencies, within not later than 30 working days.

3. The System Integrator shall also be responsible to train identified employees of HUDA with

regard to the Services being provided by the System Integrator as and when required by HUDA

during the Term of this Project. The parameters of the training required for these employees of

HUDA shall be communicated by HUDA to the System Integrator periodically and shall be in

accordance with the latest procedures and processes available in the relevant areas of work.

4. The profiles of resources proposed by System Integrator in the technical proposal, which are

considered for Technical bid evaluation, shall be construed as ‘Key Personnel’ and the System

Integrator shall not remove such personnel without the prior written consent of HUDA. In case

such as resignation, sickness such personnel may be replaced with the prior written consent

and approval of HUDA. For any changes to the proposed resources, System Integrator shall

provide equivalent or more experienced resources in consultation with HUDA.


77 | P a g e

5. Except as stated in this Article, nothing in this RFP will limit the ability of System Integrator

freely to assign or reassign its employees; provided that System Integrator shall be responsible,

at its expense, for transferring all appropriate knowledge from personnel being replaced to

their replacements. HUDA shall have the right to review and approve System Integrator’s plan

for any such knowledge transfer. System Integrator shall maintain the same standards for skills

and professionalism among replacement personnel as in personnel being replaced.

6. Each Party shall be responsible for the performance of all its obligations under the Agreement

and shall be liable for the acts and omissions of its employees and agents in connection

therewith.

Neither Party will solicit for employment or knowingly hire an employee of the other Party with

whom such Party has contact pursuant to project engagements till the end of the contract

period.

5.14 Intellectual Property Rights

1. Products and fixes: All products and related solutions and fixes provided pursuant to this RFP

shall be licensed according to the terms of the license agreement packaged with or otherwise

applicable to such product. Bidder would be responsible for arranging any licenses associated

with products.

a. “Product” means any computer code, web-based services, or materials comprising

commercially released, pre-release or beta products (whether licensed for a fee or no

charge) and any derivatives of the foregoing which are made available to HUDA for

license which is published by product owner or its affiliates, or a third party.

b. “Fixes” means product fixes that are either released generally (such as commercial

product service packs) or that are provided to you when performing services (such as

workarounds, patches, bug fixes, beta fixes and beta builds) and any derivatives of the

foregoing.

2. For an Bespoke development, HUDA shall retain exclusive intellectual property rights to the

software (including source code), forms and the compilations that were developed or

generated during the course of the Project to which HUDA has sovereign rights and nothing

herein shall or will be construed or deemed to grant to the System Integrator any right, title,

license, sub-license, proprietary right or other claim against or interest in, to or under (whether

by estoppels, by implication or otherwise) to the aforesaid rights.

3. All right, title and interest in and to, and ownership in, Proprietary Information of System

Integrator, which is provided to HUDA for the Project including source code of any pre-existing

application of the System Integrator, shall remain solely with the System Integrator. HUDA shall

be entitled to use such System Integrator Proprietary Information only in connection with the


78 | P a g e

Services or to the extent necessary for the Project’s normal operational, repair and

maintenance purposes related to the Services. HUDA shall not have the right to resale or

redistribute such proprietary information of the System Integrator.

a. However, any software that may be acquired from third Parties during the term of the

Agreement and that which may be developed by the System Integrator during the

course of the Agreement specifically for the Project shall not be considered as System

Integrator’s Proprietary Information by HUDA.

b. Accordingly, all right, title and interest in and to, and ownership in, any modifications,

enhancements, customizations of the System Integrator’s pre-existing work that may

have been done by the System Integrator during the course of the Agreement

specifically for the Project or as a result of Services rendered by the System Integrator

hereunder shall remain solely with HUDA.

4. All right, title and interest in and to, and ownership in, proprietary information of the Project

which is provided to System Integrator by HUDA; and all modifications, enhancements and

other derivative works of such Project Proprietary Information ("Proprietary Information"); any

modifications, enhancements, customizations of the System Integrator’s pre-existing work

that may have been done by the System Integrator during the course of the Agreement

specifically for the Project or as a result of Services rendered by the System Integrator

hereunder shall remain solely with HUDA. System Integrator shall be entitled to use such

Proprietary Information only during the Agreement Term and only for the purposes of

providing the Services or to the extent necessary for System Integrator’s normal operational,

repair and maintenance purposes related to the Services. HUDA shall retain ownership of all

Intellectual Property Rights related to “Up-Gradation/Development and Maintenance of

Applications at HUDA” project proprietary information.

5. With respect to ownership of the Deliverables, the Parties agree that the following shall apply:

a. Deliverables provided to HUDA by System Integrator during the course of its

performance under this Agreement, which includes but is not limited to Software as

defined in this Agreement, in which, subject to the foregoing provisions of this Article,

all right, title and interest in and to such Deliverables, shall, as between System

Integrator and HUDA, immediately upon creation, vest in HUDA. To the extent that the

System Integrator Proprietary Information is incorporated within the Deliverables,

System Integrator and its employees engaged hereby grant to HUDA a worldwide,

perpetual, irrevocable, non-exclusive, transferable, paid-up right and license to use,

copy, modify (or have modified), transport to HUDA facilities, and prepare from them,

use and copy derivative works for the benefit of and internal use of HUDA, of such

System Integrator Proprietary Information. HUDA’s rights pursuant to the preceding

sentence include the right to disclose such System Integrator Proprietary Information

to third party contractors solely for use on the Project provided that all such third party


79 | P a g e

contractors execute, deliver and comply with any customary confidentiality and

nondisclosure agreements reasonably required by HUDA.

6. HUDA hereby grants to System Integrator a non-exclusive right and license to access and use

the Department offices and information solely for the purpose of providing Services on this

Project. Such right and license shall terminate upon the expiration or termination of the

Agreement.

7. System Integrator shall not use HUDA Data to provide services for the benefit of any third

party, as a service bureau or in any other manner.

5.15 Trademarks, Publicity

Neither Party may use the trademarks of the other Party without the prior written consent of

the other Party. Except as required by law or the rules and regulations of the stock exchange

upon which the securities of the System Integrator is listed, neither Party shall publish or

permit to be published either along or in conjunction with any other person any press release,

information, article, photograph, illustration or any other material of whatever kind relating to

the Agreement or the business of the Parties without prior reference to and approval in writing

from the other Party, such approval not to be unreasonably withheld or delayed.

5.16 Forfeiture of Earnest Money

1. If the bidder withdraws his bid before the expiry of validity or after the acceptance of the bid,

the earnest money deposited by the bidder will be forfeited.

2. In case of issue of the Letter of Intent, if the bidder fails to:

a. Accept the Letter of Intent by returning a duly signed copy within the time limit

specified; and / or

b. Execute the contract agreement; and / or

c. Furnish the performance bank guarantee as specified in this Document the earnest

money deposit will be forfeited

5.17 Force Majeure

5.17.1 DEFINITION

For the purposes of this assignment, “Force Majeure” means an event which is beyond the

reasonable control of a Party, and which makes a Party’s performance of its obligations

hereunder impossible or so impractical as reasonably to be considered impossible in the

circumstances, and includes, but is not limited to, war, riots, civil disorder, earthquake, fire,

explosion, storm, flood or other adverse weather conditions, strikes, lockouts or other

industrial action (except where such strikes, lockouts or other industrial action are within the


80 | P a g e

power of the Party invoking Force Majeure to prevent), confiscation or any other action by

government agencies.

Force Majeure shall not include

1. any event which is caused by the negligence or intentional action of a Party or agents

employees thereof, nor

2. any event which a diligent Party could reasonably have been expected to both (A) take into

account at the time of the conclusion of the Agreement and (B) avoid or overcome in the

carrying out of its obligations hereunder.

Force Majeure shall not include insufficiency of funds or failure to make any payment

required hereunder.

The DEPARTMENT will decide the eventuality of Force Majeure which will be binding on

both the parties.

5.17.2 NO BREACH OF AGREEMENT

The failure of a Party to fulfill any of its obligations shall not be considered to be a breach of, or

default under, the Agreement insofar as such inability arises from an event of Force Majeure,

provided that the Party affected by such an event has taken all reasonable precautions, due

care and reasonable alternative measures, all with the objective of carrying out the terms and

conditions of the Agreement.

5.17.3 MEASURES TO BE TAKEN

1. A Party affected by an event of Force Majeure shall take all reasonable measures to remove

such Party’s inability to fulfill its obligations hereunder with a minimum of delay.

2. A Party affected by an event of Force Majeure shall notify the other Party of such event as soon

as possible, and in any event not later than fourteen (14) days following the occurrence of such

event, providing evidence of the nature and cause of such event, and shall similarly give notice

of the restoration of normal conditions as soon as possible.

3. The Parties shall take all reasonable measures to minimize the consequences of any event of

Force Majeure.

5.17.4 PAYMENTS

During the period of its inability to perform the Services as a result of an event of Force

Majeure, the System Integrator shall be entitled to be reimbursed for additional costs

reasonably and necessarily incurred by it during such period for the purposes of the Services

and in reactivating the Services after the end of such period. Such expenses will be approved by

the DEPARTMENT. The System Integrator will have to provide proper justification and

certificate from their auditors for such expenses on the format as may be decided by the

DEPARTMENT.


81 | P a g e

5.17.5 CONSULTATION

Not later than thirty (30) days after the System Integrator has, as the result of an event of Force

Majeure, become unable to perform a material portion of the Services, the Parties shall consult

with each other with a view to agreeing on appropriate measures to be taken in the

circumstances.

5.17.6 SUSPENSION OF AGREEMENT

The DEPARTMENT may, by written notice of suspension to the System Integrator, without any

obligation (financial or otherwise) suspends all the payments to the System Integrator

hereunder if the System Integrator shall be in breach of this Agreement or shall fail to perform

any of its obligations under this Agreement, including the carrying out of the Services; provided

that such notice of suspension (i) shall specify the nature of the breach or failure, and (ii) shall

provide an opportunity to the System Integrator to remedy such breach or failure within a

period not exceeding thirty (30) days after receipt by the System Integrator of such notice of

suspension.

5.18 Termination

5.18.1 TERMINATION FOR BANKRUPTCY

1. HUDA may serve written notice on System Integrator at any time to terminate the Agreement

with immediate effect in the event of a reasonable apprehension of bankruptcy of the System

Integrator:

2. System Integrator shall in the event of an apprehension of bankruptcy immediately inform

HUDA, well in advance (at least 4 months) about such a development;

5.18.2 TERMINATION FOR DEFAULT

1. HUDA reserves the right to terminate the contract in case Bidder gets blacklisted by the

Government of Haryana, or any other Ministry of Government of India or any of their

agencies during the course of this project on account of proven corrupt or fraudulent

practice or convicted for any offence by any court of Law

.

2. If at any stage of Tendering process or during the currency of the Contract, any suppression /

falsification of information with respect to any of the conditions in the RFP comes to the

knowledge of HUDA, HUDA shall have the right to reject the bid or terminate the contract, as

the case may be, without any compensation to the Bidder

3. In the event that HUDA or any of its nominated agencies reasonably believes that the SI is in

breach of its obligations under this Agreement or any SLA, HUDA may terminate this

Agreement upon written notice of not less than 30 days to the other. Any notice served


82 | P a g e

pursuant to this Article shall give reasonable details of the breach, which includes but is not

limited to the following:

a. If there is breach which translates into default in providing Services by the SI as per any

SLA and this Agreement, continuously for more than one payment period, then HUDA

or any of its nominated agencies will serve a thirty day’s notice for curing this material

breach. In case the material breach continues after the notice period, HUDA will have

the option to terminate the Agreement. HUDA would further have the right to encash

the Performance Bank Guarantee. A notice of at least 30 days to be given in any case of

termination.

b. Because time is the essence of the contract, in case, for reasons prima facie

attributable to the SI, there is a delay of more than 3 months in the Project ‘Go-Live’,

HUDA may terminate this Agreement after affording a reasonable opportunity to the

Implementation Agency to explain the circumstances leading to such a delay. Further,

HUDA may also invoke the Performance Guarantee of the Implementation Agency.

5.18.3 TERMINATION FOR CONVENIENCE

1. HUDA, by written notice sent to the System Integrator, may terminate the Contract, in whole

or in part, at any time for its convenience. The notice of termination shall specify that

termination is for its convenience and the System Integrator will be given 3 months before

termination of contract takes effect.

2. On termination of the Agreement for any reason, the SLAs shall automatically terminate

forthwith and HUDA will decide the appropriate course of action.

5.19 Effects of Termination

1. In the event of HUDA, terminating the Agreement for its convenience, the System Integrator

will be paid the amount due to it for the services rendered. The compensation will be decided

in accordance with the Terms of Payment Schedule including other aspects such as cost of

selection of alternate service provider, penalties, pro-rata payments etc.

2. Upon termination of the Agreement for any reason, the Parties will comply with the Exit

Management Schedule as contained in Section 5.22.

5.20 Disputes Resolution

5.20.1 AMICABLE SETTLEMENT

The parties shall use their best efforts to settle amicably all disputes arising out of or in

connection with this Agreement or the interpretation thereof. In the event a dispute,

differences or claim arises in connection with the interpretation or implementation of this

agreement, the aggrieved party shall issue a written notice setting out the Dispute/differences

or claim to the other party, parties shall first attempt to resolve such dispute through mutual


83 | P a g e

consultation. If the dispute is not resolved as aforesaid within 15 days from the date of receipt

of written notice, the matter will be referred for Arbitration.

5.20.2 ARBITRATION

1. In the event of any dispute or differences arising under these conditions or any special

conditions of the contract in connection with this contract, the same shall be referred

to arbitration, for final decision and the same shall be binding on all parties.

2. Any other terms and conditions, mutually agreed prior to finalization of the order /

Contract shall be binding on the Bidder.

3. Client and the Bidder shall make every effort to resolve amicably by direct negotiation

any disagreement or dispute arising between them under or in connection with the

purchase order. If any dispute shall arise between parties on aspects not covered by

this Contract, or the construction or operation thereof, or the rights, duties or liabilities

under these except as to any matters the decision of which is specially provided for by

the general or the special conditions, such dispute shall be referred to two arbitrators,

one to be appointed by each party and the said arbitrators shall appoint an umpire in

writing before entering on the reference and the award of the arbitration or umpire, as

the case may be, shall be final and binding on both the parties. The arbitrators or the

umpire as the case may be, with the consent of parties, may modify the timeframe for

making and publishing the award. Such arbitration shall be governed in all respects by

the provision of the Indian Arbitration and Conciliation Act, 1996 or later and the rules

there under and any statutory modification or reenactment, thereof. The arbitration

proceedings shall be held in Panchkula, Haryana, India.

5.21 Change Control Procedure

This Schedule describes the procedure to be followed in the event of any proposed change to

the Service Level Agreement (SLA), or Scope of Work. Such change shall include, but shall not

be limited to, changes in the scope of services provided by the SI and changes to the terms of

payment as stated in the Terms of Payment Schedule.

HUDA and the SI recognize that frequent change is an inevitable part of delivering services and

that a significant element of this change can be accomplished by reorganizing processes and

responsibilities without a material effect on the cost. The SI will endeavor, wherever

reasonably practicable, to effect change without an increase in the terms of payment as stated

in the Terms of Payment Schedule and HUDA will work with the SI to ensure that all changes

are discussed and managed in a constructive manner.

This Change Control Schedule sets out the provisions which will apply to changes to

1. Service Level Agreement

2. Scope of Work


84 | P a g e

5.21.1 CHANGE CONTROL NOTE ("CCN")

The SI and HUDA shall consider a change, so, only when such change is beyond the scope of

Services mentioned in this RFP.

Change requests in respect of the SLA, or Scope of Work will emanate from the Parties'

respective Project Manager who will be responsible for obtaining approval for the change and

who will act as its sponsor throughout the Change Control Process and will complete Part A

(refer section 6.10 form 9 for formats of CCN) of the CCN attached below hereto. CCNs will be

presented to the other Party's Project Manager who will acknowledge receipt by signature of

the CCN.

Any change before accepted and implemented, will have to be approved by HUDA

The following are to be noted:

1. For any items for which the rates are not already sought in the Commercial Bid of the RFP, the

rates will be mutually agreed between HUDA and the SI.

2. If the change arises from increase in scope of work and the change is within 25% of the

contract value, then, additional payment equivalent to value of change will be made to the SI

as per payment schedule agreed with HUDA in CCN

3. If the change arises from increase in scope of work and value of change is beyond 25% of the

contact value, it will be beyond the scope of the change control process and may be

considered as the subject matter for a separate bid process and a separate contract or

alternately be done as part of same contract on mutually agreed terms with the SI subject to

the approval of Governing Council of HUDA.

4. If the change arises from decrease in scope of work, and the change is within 25% of the

contract value, the Contract Value for purpose of this agreement will be revised by deducting

an amount value equivalent to value of change

5. If the change arises from decrease in scope of work and value of change is beyond 25% of the

contact value, the Contract Value for purpose of this agreement, will be revised by deducting

an amount mutually agreed between HUDA and Implementing agency subject to the approval

of Governing Council of HUDA.

5.21.2 QUOTATION

The SI shall assess the CCN and complete Part B of the CCN (refer section 6.10 form-9).

In completing Part B of the CCN the SI shall provide as a minimum:

1. A description of the change;

2. A list of deliverables required for implementing the change;

3. A timetable for implementation;

4. An estimate of any proposed change;

5. Any relevant acceptance criteria;


85 | P a g e

6. An assessment of the value of the proposed change;

7. Material evidence to prove that the proposed change is not already covered within the

scope of Work, SLAs

Prior to submission of the completed CCN to HUDA, the SI will undertake its own internal

review of the proposal and obtain all necessary internal approvals. As a part of this internal

review process, the SI shall consider the materiality of the proposed change in the context of

the Agreement, the Project Implementation, Operation and Management SLA affected by the

change and the total effect that may arise from implementation of the change.

Materiality criteria will be established by HUDA and the SI's Project Manager. Changes

requiring no escalation of authority can be implemented. Discussion and agreement as to

materiality will be held in accordance with the Governance Schedule.

5.21.3 COSTS

Each Party shall be responsible for its own costs incurred in the quotation, preparation of CCNs

and in the completion of its obligations described in this process provided the SI meets the

obligations as set in the CCN. In the event the SI is unable to meet the obligations as defined in

the CCN then the cost of getting it done by third party will be borne by the SI.

5.21.4 REPORTING/REVIEW

The Status on the progress of the Change requests and CCNs will be reported by SI to HUDA on

a fortnightly basis and same shall be reviewed by both the parties on Fortnightly basis. For any

changes in the Project, identified by either party, SI shall prepare a detailed Change Control

Note within ten working days from the date of intimation of such change.

5.21.5 OBLIGATIONS

The SI shall be obliged to implement any proposed changes once approval from HUDA in

accordance with this CCN has been given, with effect from the date agreed for

implementation.

5.22 Transition & Exit Management

5.22.1 PURPOSE

1. This clause sets out the provisions which will apply on expiry or termination of the

“Contract Agreement”, the “Project Implementation, Operation and Management SLA

(Service Level Agreement)” and “SOW (Scope of Work)”.


86 | P a g e

2. In the case of termination of the Project Implementation and/or Operation and

Management SLA or SOWs due to illegality, the Parties (‘HUDA’, ‘Systems Integrator’) shall

agree at that time whether, and if so during what period, the provisions of this clause shall

apply.

3. The Parties shall ensure that their respective associated entities, in case of the HUDA or its

nominated agencies and Systems Integrator, carry out their respective obligations set out

in this Exit Management Clause.

5.22.2 TRANSFER OF ASSETS

1. The System Integrator shall be entitled to use the Facilities for the duration of the exit

management period.

2. HUDA during the Project Implementation Phase and Operation and Management Phase

shall be entitled to serve notice in writing on the System Integrator at any time during the

exit management period requiring the System Integrator to provide the HUDA with a

complete and up to date list of the Assets within 30 days of such notice. All the Assets

detailed in the list shall be transferred to HUDA within the time period as indicated to the

System Integrator by HUDA.

3. That on the expiry of this clause, the System Integrator and any individual assigned for the

performance of the services under this clause shall handover or cause to be handed over all

Confidential Information and all other related materials in its possession, under this clause

to the HUDA.

4. That the products and technology delivered to the HUDA during the contract term or on

expiry of the contract duration should not be sold or re-used or copied or transferred by

System Integrator without prior written notice and approval of the HUDA. All software &

documents etc. used by System Integrator for the HUDA shall be the legal properties of the

HUDA.

5.22.3 COOPERATION AND PROVISION OF INFORMATION

During the exit management period:

1. The System Integrator will allow the HUDA or its nominated agencies access to information

reasonably required to define the then current mode of operation associated with the

provision of the services to enable it to assess the existing services being delivered;

2. Promptly on reasonable request by the HUDA or its nominated agencies, the System

Integrator shall provide access to and copies of all information held or controlled by it, the

Project Implementation, the Operation and Management SLA and SOWs relating to any

material aspect of the services (whether provided by the Systems Integrator). HUDA or its

nominated agencies shall be entitled to copy all such information. Such information shall

include details pertaining to the services rendered and other performance data. The

System Integrator shall permit HUDA or its nominated agencies and/or any Replacement

System Integrator to have reasonable access to its employees and facilities as reasonably


87 | P a g e

required to understand the methods of delivery of the services employed by the System

Integrator and to assist appropriate knowledge transfer.

5.22.4 CONFIDENTIAL INFORMATION, SECURITY AND DATA

1. The System Integrator will promptly on the commencement of the exit management

period supply to the HUDA or its nominated agencies the following:

a. Information relating to the current services rendered and user satisfaction surveys

and performance data relating to the performance in relation to the services;

b. Documentation relating to Intellectual Property Rights of HUDA;

c. HUDA data and confidential information;

d. All current and updated departmental data as is reasonably required for purposes

of HUDA or its nominated agencies transitioning the services to its System

Integrator in a readily available format; and

e. All other information (including but not limited to documents, records and

agreements) relating to the services reasonably necessary to enable HUDA or its

nominated agencies, or its System Integrator to carry out due diligence in order to

transition the provision of the Services to HUDA or its nominated agencies, or its

System Integrator (as the case may be).

2. Before the expiry of the exit management period, the System Integrator shall deliver to

HUDA or its nominated agencies all new or up-dated materials from the categories and

shall not retain any copies thereof, except that the System Integrator shall be

permitted to retain one copy of such materials for archival purposes only.

3. Before the expiry of the exit management period, HUDA or its nominated agencies shall

deliver to the System Integrator all forms of System Integrator confidential information

which is in the Possession or Control of the HUDA or its nominated agencies or its

users.

5.22.5 EMPLOYEES

1. Promptly on reasonable request at any time during the exit management period, the

System Integrator shall, subject to applicable laws, restraints and regulations (including in

particular those relating to privacy) provide to the HUDA or its nominated agencies a list of

all employees (with job titles) of the System Integrator dedicated to providing the services

at the commencement of the exit management period;

2. Where any national, regional law or regulation relating to the mandatory or automatic

transfer of the contracts of employment from the System Integrator to HUDA or its

nominees, or a Replacement System Integrator ("Transfer Regulation") applies to any or all

of the employees of the Systems Integrator, then the Parties shall comply with their

respective obligations under such Transfer Regulations.

3. To the extent that any Transfer Regulation does not apply to any employee of the Systems

Integrator, HUDA or its nominated agencies, or its Replacement System Integrator may

make an offer of employment or contract for services to such employee of the System


88 | P a g e

Integrator and the System Integrator shall not enforce or impose any contractual provision

that would prevent any such employee from being hired by the HUDA or its nominated

agencies or any Replacement Systems Integrator

5.22.6 TRANSFER OF CERTAIN AGREEMENTS

On request by the HUDA or its nominated agencies, the System Integrator shall effect such

assignments, transfers, innovations, licenses and sub-licenses as required in favor of the HUDA

or its nominated agencies, or its Replacement System Integrator in relation to any equipment

lease, maintenance or service provision agreement between System Integrator and third party

lessors, Systems Integrator/Successful Bidders, or Systems Integrator, and which are related to

the services and reasonably necessary for the carrying out of replacement services.

5.22.7 GENERAL OBLIGATIONS OF THE SYSTEM INTEGRATOR

1. The System Integrator shall provide all such information as may reasonably be necessary to

effect handover as practicable in the circumstances to HUDA or its nominated agencies or

its replacement System Integrator and which the System Integrator has in its possession or

control at any time during the exit management period.

2. The System Integrator shall commit adequate resources to comply with its obligations

under this Exit Management Clause.

5.22.8 EXIT MANAGEMENT PLAN

1. The System Integrator shall provide the HUDA or its nominated agencies with a

recommended exit management plan ("Exit Management Plan") which shall deal with at

least the following aspects of exit management as a whole and in relation to the Project

Implementation, the Operation and Management SLA and SOWs.

a. A detailed programme of the transfer process that could be used in conjunction

with a Replacement System Integrator including details of the means to be used to

ensure continuing provision of the services throughout the transfer process or until

the cessation of the services and of the management structure to be used during

the transfer

b. Plans for communication with such of the Systems Integrator's staff, suppliers,

users and any related third party as are necessary to avoid any material

detrimental impact on HUDA’s operations as a result of undertaking the transfer.

2. Exit Management Plan shall be presented by the System Integrator to and approved by the

HUDA or its nominated agencies.

3. During the exit management period, the System Integrator shall use its best efforts to

deliver the services.


89 | P a g e

4. Payments during the Exit Management period shall be made in accordance with the Terms

of Payment Clause for all milestones that have been successfully completed.

5. The Exit Management plan shall be furnished in writing to the HUDA within 60 days.

5.23 Miscellaneous

1. The end product of the work assignment carried out by the Bidder, in any form, will be the

sole property of Client.

2. The Bidder shall perform the services and carry out its obligations under the contract with

due diligence and efficiency, in accordance with generally accepted techniques and

practices used in the industry and with professional engineering and training / consulting

standard recognized by national / international professional bodies and shall observe

sound management practice. It shall employee appropriate advanced technology and safe

and effective methods. The Bidder shall always act, in respect of any matter relating to this

Contract, as faithful advisors to Client and shall at all times, support and safeguard Client

legitimate interests.

3. The Bidder automatically agrees with Client for honoring all aspects of fair trade practices

in executing the work orders placed.

4. In the event the Bidder or the concerned Division of the company is taken over / bought

over by another company, all the obligations under the Contract with Client, should be

passed on the compliance by the new company new Division in the negotiation for their

transfer .

5. This Contract is intended solely for the benefit of the parties hereto. Nothing in this

Contract shall be construed to create any duty or any liability to any person not a party to

this Contract.

6. The Contract shall not be interpreted or construed to create an association, joint venture,

or partnership between the parties or to impose any partnership obligation or liability upon

either party. Neither party shall have any right, power or authority to enter into any

Contract or undertaking, or act on behalf of or to act as an agent or representative of, or to

otherwise bind, the other party.

7. Survival: All provisions of this Contract, which are expressly or by implication come into or

continue in force and effect after the expiration or termination of this Contract shall remain

in effect and be enforceable following such expiration or termination.

8. It will be the primary responsibility of successful bidder to close all the gaps identified by

the security audit team of HUDA.

9. The bidder has to provide the Source Code and AMC of the project.


90 | P a g e

6. FORMS AND FORMATS

6.1 ADDITIONAL INFORMATION RELATED TOTHE PROJECT

6.1.1 FUNCTIONS CARRIED OUT BY THE AUTHORITY

The Authority has taken over work which was being handled by individual departments.

The main functions of Haryana Urban Development Authority are as under:-

1. To promote and secure development of urban areas with the power to acquire, sell

and dispose of property, both movable and immovable

2. To acquire, develop and dispose land for residential, industrial and commercial

purpose

3. To make available developed land to Haryana Housing Board and other bodies for

providing houses to economically weaker sections of the society ; and

4. To undertake building works. Details are available on www.huda.org.in



91 | P a g e

6.2 FORM 1 - Covering Letter – Tender Document (Format)

To be submitted on the Letterhead of the responding firm)

{Place}

{Date}

To,

The General Manager IT


Plot c-3 HUDA HQ

Sector-6 Panchkula 134109

Ref: RFP reference no ___________ dated ________

Subject: Covering Letter for the proposal for “Selection of System Integrator for Up

gradation/development and maintenance of HUDA Application”.

Dear Sir,

1. Having examined the Tender document, we, the undersigned, herewith submit our

proposal in response to your Tender

no._____________________dated____________for “Up gradation/development and

maintenance of HUDA Application”, in full conformity with the said Tender document.

2. We have read the provisions of the Tender document and confirm that these are

acceptable to us. We further declare that additional conditions, variations, deviations, if

any, found in our proposal shall not be given effect to.

3. We agree to abide by this proposal, consisting of this letter, the detailed response to

the Tender and all attachments, for a period of 180 days from the closing date fixed for

submission of proposals as stipulated in the Tender document.

4. The Earnest Money Deposit of INR submitted by us in the form of Bank

Guarantee shall be forfeited and the contract would be liable for termination, if we do

not submit the requisite Performance Bank Guarantee within 15 days of issuance of

Letter of Intent for “Up gradation/development and maintenance of HUDA

Application”.

5. We would like to declare that we are not involved in any major litigation that may have

an impact of affecting or compromising the delivery of services as required under this

assignment and we are not under a declaration of ineligibility for corrupt or fraudulent

practices.

6. We would like to declare that there is no conflict of interest in the services that we will

be providing under the terms and conditions of this Tender.

7. We hereby declare that all the information and statements made in this proposal are

true and accept that any misrepresentation contained in it may lead to our

disqualification.


92 | P a g e

8. We understand HUDA is not bound to shortlist/ accept any proposal received during the

Bid Process.

9. Our correspondence details with regards to this proposal are:

S.No. Information Details

1. Name of responding firm:

2. Address of responding firm:

3. Name, Designation and Address of the

contact person to whom all references

shall be made regarding this Tender:

4. Telephone no. of contact person:

5. Mobile no. of contact person:

6. Fax no. of contact person:

7. E-mail address of contact person:

We hereby declare that our proposal submitted in response to this Tender is made in good faith

and the information contained is true and correct to the best of our knowledge and belief.

Yours sincerely,

(Signature)

Name of the Authorized signatory:

Designation of Signatory:

Seal


93 | P a g e

6.3 FORM 2 - Format for Last 5 years providing IT Services

Assignment Name

Name of the Client along with name and designation of Project

Coordinator from the Organization :

(May be used for referencing)

Address, phone and email ID:

Type of customer & industry: (such as Government, Private, etc.

along with type of industry focus, if applicable)

Nature of Services Provided (by your organization)

Start Date & Duration of Engagement


94 | P a g e

6.4 FORM 3- Declaration that the vendor has not been blacklisted

(To be submitted on the Letterhead of the vendor)

(Place)

(Date)

To,



Plot c-3 HUDA HQ


Subject: “Selection of System Integrator for Up gradation/development and maintenance of

HUDA Applications”.

Dear Sir,

We confirm that our company is not blacklisted in any manner whatsoever by any central

Government department, autonomous organizations, Public Sector Undertakings (PSUs) or any

other Government organizations in India on any ground including but not limited to indulgence

in corrupt practice, fraudulent practice, coercive practice, undesirable practice or restrictive

practice.

It is hereby confirmed that I/We are entitled to act on behalf of our company/ corporation/

firm/ organization and empowered to sign this document as well as such other documents,

which may be required in this connection.

Dated this ___ day of ___201_

Yours sincerely,

On behalf of [Vendor’s Name]

Authorized Signature [In full and initials]:

Name and Title of Signatory:

Name of Firm:

Address:

Seal/Stamp of Vendor:


95 | P a g e

6.5 FORM 4 - Financial Turnover Format

Year 2013-2014 2014-2015 2015-2016

Annual Turnover

Year 2013-2014 2014-2015 2015-2016

Annual Turnover from

Software/ Application

Development and

Integration

Please attach Audited Annual Financial Statements and Annual Report and Certified statement

from the Current Statutory Auditors of the bidder as proofs


96 | P a g e

6.6 FORM 5 - Format for citations

Using the format below, provide information on each reference assignment for which your

organization, either individually or as an association (or consortium), was legally contracted. A

Client completion certificate should support each reference assignment.

Assignment Name

Name of the Client along with name and designation of Project

Coordinator from the Organization :

(May be used for referencing)

Address, phone and email ID:

Type of customer & industry: (such as Government, Private, etc.

along with type of industry focus, if applicable)

Start Date & Duration of Engagement

Current Status

Approx. Value of engagement / services

Whether involved independently or as a consortium (with

details of prime or sub-contracting relationship, partner names,

etc. along with the specific positioning of your organization in

the consortium)

Narrative Description of Project and objectives of the

project/engagement.

Nature of Services Provided (by your organization)

Professional Staff: Team Size and approximate effort provided

by your organization

Description of Actual Services Provided by Your Staff:


97 | P a g e

6.7 FORM 6 - Declaration for No Consortium or sub-contracting

(To be submitted on the Letterhead of the vendor)

(Place)

(Date)

To,



Plot c-3 HUDA HQ


Subject: “Selection of System Integrator for Up gradation/development and maintenance of

HUDA Applications”.

Dear Sir,

We confirm that our company is not bidding for tender no. Selection of System

Integrator for Up gradation/development and maintenance of HUDA Application” under

consortium or sub-contracting with any other company. Our Firm shall alone provide all the

services mentioned in this tender document.

It is hereby confirmed that I/We are entitled to act on behalf of our company/ corporation/ firm/

organization and empowered to sign this document as well as such other documents, which may

be required in this connection.

Dated this ___ day of ___201_

Yours sincerely,

on behalf of [Vendor’s Name]

Authorized Signature [In full and initials]:

Name and Title of Signatory:

Name of Firm:


98 | P a g e

6.8 FORM 7 - (SUGGESTED FORMAT OF CURRICULUM VITAE (CV) FOR PROJECT

STAFF)

IMPORTANT NOTE: Please limit each CV to two pages

Proposed Area of work:

Name of the Firm

Name of the Staff

Designation in the Firm/Entity:

Date of Birth and Nationality:

No. of years with Firm/Entity _________________________

Total Experience ______________________

Relevant Year of Experience_________

Proficiency in English Language: __________________________________

Educational Background:

[College/university and other specialized/management/professional education with

institution/university names, year of completion and name of degree/diploma obtained]

Employment Record:

[Starting with present job, list in reverse chronological order employment data, listing positions

held, dates, and name of employer, job title and locations of work. Provide very briefly the

types of activities performed during the most recent ten year period]

Competencies, Achievements and Relevant Experience

[Give a description of staff member’s in-depth and successful experience in maximum five

assignments most pertinent to tasks on this assignment. Details required are as under:

Name and Objective of Assignment, Role on the assignment, Year and Duration of assignment,

Location, Name of HUDA and a description of the key activities performed by the staff member

and staff member’s contribution to the project.]


99 | P a g e

Roles & Responsibilities in the phase wise scope of Project: List out the roles and

responsibilities assigned to the resource.

Visible/Measurable Deliverables of the resource in the phase wise scope of project: Clearly list

out the project deliverables of the resource.


100 | P a g e

6.9 FORM 8 - (FINANCIAL PROPOSAL SUBMISSION FORM)

(Location, Date)

FROM: (Name of the Firm) To: (Name and address of the Client)

Sir,

Subject: <SUBJECT>

We, the undersigned, offer to provide the services for the above in accordance with your

Request for Proposal dated [Date], and our proposal (technical and Financial Proposals).

Our attached financial proposal as is ‘Part A’ that contains the consolidated Project Cost (for up

gradation/development of Application). The amount is inclusive of all project related expenses

and taxes (computed as per the current rate) payable under the local laws. We understand that

this amount is subject to deduction of tax at source as provided under applicable law. Any

variation in taxes rates during the contract tenure will be to the HUDA’s account supported by

relevant documentation.

‘Part B’ provides the three year maintenance costs for the application. This amount is inclusive

of all project related expenses and taxes (computed as per the current rate) payable under the

local laws.

Our financial proposal shall be binding upon us subject to the modifications resulting from

contract negotiations, up to expiration of the validity period of the Proposal, i.e. [Date]

We solemnly affirm that we will strictly adhere to the laws against fraud, corruption and

unethical practices, including but not limited to “Prevention of Corruption Act, 1988”, during

the bidding process and execution of the contract, in case we are awarded the work.

We understand you are not bound to accept any Proposal you receive.

Yours sincerely,

Authorized Signatory

Name and Title of Signatory,

Name of the Firm


101 | P a g e

Address:

To be submitted online mode (in BOQ) only

Project Cost

Part A: Up-Gradation/ Development of existing applications in HUDA.

S.No. Component Total Cost (INR)

1

One time development cost for the applications including

training etc.(exclusive of service tax)

Total Cost PART A: Project Value (1)

Part B: Post Go-Live Annual Maintenance Cost

S.NO AMC Cost Total Cost (INR)

1 Total AMC cost for 3 years support for

the applications(exclusive of service

tax)

Total Cost PART B

SI will submit a resource plan before AMC starts with details of the type of resources and the

roles and responsibility of each resource.

*Conditional bids will be rejected.


102 | P a g e

6.10 FORM 9 - Change Control Note Formats

Change Control Note CCN Number:

Part A: Initiation

Title:

Originator:

Sponsor:

Date of Initiation:

Details of Proposed Change

(To include reason for change and appropriate details/specifications. Identify any attachments as

A1, A2, and A3 etc.)

Authorized by HUDA Date:

Name:

Signature:

Received by the

Implementation

Agency

Date:

Name:

Signature:


103 | P a g e

Part B : Evaluation

Change Control Note CCN Number:

(Identify any attachments as B1, B2, and B3 etc.)

Changes to Services, charging structure, payment profile, documentation, training, service levels and

component working arrangements and any other contractual issue.

Brief Description of Solution:

Impact:

Deliverables:

Timetable:

Charges for Implementation:

(including a schedule of payments)

Details of Manpower to be provided (Provide CVs of Manpower to be deployed )

Other Relevant Information:

(including value-added and acceptance criteria)

Authorized by the

Private Implementation Partner

Date:


104 | P a g e

Name:

Signature:

Change Control Note CCN Number :

Part C : Authority to Proceed

Implementation of this CCN as submitted in

Part A, in accordance with Part B is:

(tick as appropriate)

Approved

Rejected

Requires Further Information (as follows, or as

Attachment 1 etc.)

For HUDA

For the SI

Signature Signature

Name Name

Title Title

Date Date


105 | P a g e

6.11 FORM 10 - Format for Pre-bid Clarifications

A. Details of bidder

Name of Bidder

submitting

request

Name and Position of

person submitting

request

Full formal address of the bidder including phone,

fax and email points of contact

B. Form for Pre-Bid Clarifications

SNO Section No. in

RFP

Reference/Subject Points of Clarification Reply to clarification

from HUDA


106 | P a g e

6.12 ABBREVIATIONS

Abbreviation Description

PPM Plot and Property Management

FAS Financial Accounting System

CCTS Court Case Tracking System

EMP Exit Management Plan

SI System Integrator

STQC Standardization Testing and Quality Certification

HUDA Haryana Urban Development Authority

SLA Service Level Agreement

IT Information Technology

SPOC Single Point of Contact

Commissioning Go-live of the up graded applications


107 | P a g e

ANNEXURES

7. ANNEXURE A - FUNCTIONAL REQUIREMENTS FOR FAS MODULE

This section briefly describes the overall capability of the functionality to be provided by the proposed

FAS for HUDA. FAS deals with preparation of all account books, reconciliation of the funds, preparation

of budget and monitoring of loans, and entry of bills and their payment. This is an internal application

accessible only in HUDA offices

7.1 Maintain Bank Master

Description

This function is intended to add Banks to the Bank Master. Bank Code shall uniquely identify each Bank.

Existing Bank details can also be edited and deleted using this function.

Business Logic

Details like Bank Code, Bank Name, and Head office address along with the contact person name shall

be captured using this function.

Validations

Bank Code should be unique

7.2 Maintain Bank Branch Master

Description

This function is intended to add a Bank branch to the Branch Master. Branch Code shall uniquely

identify each Bank branch.

Business Logic

Bank branch details like Bank Branch Name, Address along with Magnetic Ink Character Recognition

(MICR) code and BSR code of various banks with which HUDA interacts shall be captured through this

master. HUDA can hold one or more than one account in a Bank Branch. Account information such as

account number, type of account along with GL/ SL code shall also be captured using this function.

Existing Branch and account information shall also be modified using this function.

Validations

Branch Code should be unique

7.3 Maintain Office Master

Description

This function is intended to add Office to the Office Master. Office Code shall uniquely identify each

Office.


108 | P a g e

Business Logic

HUDA has divided Haryana in different zones, where each zone has multiple Offices. There are various

types of offices like Division Office, LAO Office, CA Office. Office Details like Office Type, Office Code,

Name, and Address are captured through this master. ‘Date From’ and ‘Date To’ describes the

existence of Office in particular zone, and shall be captured using this master.

Each sector falls under a Division and Urban Estate, this association is also managed using this function.

Validations

Zone Codes should be valid

Office Code should be unique

Only Office name and address can be modified

‘Date To’ cannot be less than the ‘Date From’

Division office must have associated TAN details

7.4 Maintain Financial Year Master

Description

This function is intended to capture the financial year details like Start date, end date, and the status of

the financial year.

Business Logic

This function shall contain details of the financial year.

The accounting period has been fixed as the calendar month. For a closed period no transactions can

be entered or modified in any of the Finance and Accounting sub-systems. The financial year shall be

from 1st of April of the current year to 31st March of the next year. The accounting period can have the

following status:

Open

Closed

Transaction entries can be entered into the system for an open period. A period once “closed” can be

reverted back to an “open” status for transaction entry.

Validations

None

7.5 Maintain Cheque Control Register

Description

This function is intended to add the cheque details issued to/ by different Banks to/ by HUDA. This

function is also intended to maintain the details and status of the cheque/ drafts that have been issued

to/by HUDA.


109 | P a g e

Business Logic

Details like Account Number Code, Account number, Bank Code, Branch code, Bank Name, Cheque/

Draft Number, Status, Amount, In favor Of, Issue Date of the cheque shall be captured. Cheque

Amount, in favor of and Issue Date of the cheque shall get populated once the cheque is issued to the

party and the payment voucher has been posted. In this case the cheque status shall also be changed

to ‘Used’. For unused and/ or damaged cheques the status shall be updated directly by the user.

Validations

Account Number code should be valid.

The status of the cheque may be used, unused, cancelled, lost or damaged.

7.6 Maintain FDR Details

Description

This function is intended to capture the details of the individual Fixed Deposit Receipt (FDR) issued to

HUDA.

Business Logic

FDR Details like date, principal amount, rate of interest, interest amount, maturity amount, TDS

deducted, bank name, branch name and date of maturity shall be captured. The FDR by default shall be

in favor of Chief Administrator HUDA. A provision for calculating the premature amount on a given date

and given rate shall also be provided. There shall be a provision to select whether the interest is

compounded quarterly/half yearly/annually.

Also, by providing the rate of interest and date, premature amount can be calculated.

Validations

Date of maturity should be valid and should be greater than FDR Date

The FDR by default should be issued in favour of Chief Administrator of HUDA

The premature amount date should be less than the date of maturity.

7.7 Maintain Voucher Details The major functional areas of Financial Accounting are:

Maintenance of different types of vouchers (Journal Vouchers, Bank Vouchers and Cash Vouchers)

Daybooks generation

Posting transactions to respective General Ledger (GL) and Subsidiary Ledger (SL)

Maintenance of GL accounts with flexible SL.

The types of vouchers are:


110 | P a g e

Journal Voucher (JV)

Bank Payment Voucher (BPV)

Cash Payment Voucher (CPV)

Bank Receipt Voucher (BRV)

Cash Receipt Voucher (CRV)

Contra Voucher (CV)

Irrespective of the type, each voucher shall have the following features:

1. The vouchers should always be balanced, that is, the total debit amount entered should always be

equal to the total credit amount entered.

2. Vouchers can only be created for an accounting period with an “open” status.

3. Printed voucher shall have amount in words. The user shall enter the amount in figures only.

4. Future dated transactions shall not be allowed.

5. Back dated transactions (only JVs) shall be allowed, provided the corresponding accounting period

is open.

6. Vouchers shall have a facility of multiple debits and multiple credits.

7. Authorized users shall authorize and post the voucher to the respective GL codes, after which, the

voucher cannot be deleted.

8. The voucher cannot be edited once it has been approved. A JV shall have to be created for this

purpose.

9. User identification of the person creating and the person authorizing the voucher shall be stored in

the system for control purposes.

10. Cashbook/ Bankbook have to be closed the next day. On a Friday, it can be closed on the same day.

11. There shall be an exception in the system for opening and closing the Bankbook on the last day of

the year by the authorized person only that is, March 31. The bankbook shall also remain open on

Sept 30 and Dec 31.

12. Bank daybook for each month shall be closed seven days after month end and for the month of

September, it shall close after a month.

13. An advice note shall be created with each voucher for maintaining a physical record of the

transaction.

14. The narration to have party name to appear by default and the user shall have an option to edit it

15. There shall be the provision in all the vouchers to make the reverse entry for the already posted

voucher. In that case system shall also take the voucher number and voucher date of the voucher

that is to be reversed. If the voucher by which the payments has been made for bill is reversed then

the bill status shall also get changed to unpaid.

The system shall provide location wise a unique ID (system generated sequence number) for each

voucher to be generated at the time of its creation.


111 | P a g e

7.7.1 MAINTAIN BANK PAYMENT VOUCHER

Description

This function shall allow the user to maintain the Bank Payment Voucher (BPV).

Business Logic

Individual voucher numbers shall be assigned to each BPV. The bank payment shall be checked against

the closing balance for the particular bank account and any voucher pending authorization against the

same account. The user shall be able to override and proceed. After every payment, the balance shall

be displayed on the screen.

Validations

Voucher Number should be unique.

The voucher should be balanced.

7.7.2 MAINTAIN BANK RECEIPT VOUCHER

Description

This function shall allow the user to maintain the Bank Receipt Voucher (BRV).

Business Logic

A single Bank Receipt Voucher (BRV) shall always allow receipts into one single bank account only. The

system shall generate a receipt to the party for the amount received.

Validations



7.7.3 MAINTAIN CASH PAYMENT VOUCHER

Description

This function shall allow the user to maintain the Cash Payment Voucher (CPV).

Business Logic

Single Cash Payment Voucher (CPV) shall be one transaction.

It shall alert the user if the payment shall lead to a negative balance in the account. The cash payment

shall be checked against the cashbook balance for the particular transaction and any voucher pending

authorization against the same account. The user shall not be able to proceed.

Validations




112 | P a g e

7.7.4 MAINTAIN CASH RECEIPT VOUCHER

Description

This function shall allow the user to maintain the Cash Receipt Voucher (CRV).

Business Logic

Single Cash Receipt Voucher (CRV) shall be one transaction.

Validations



7.7.5 MAINTAIN JOURNAL VOUCHER

Description

This function shall allow the user to maintain a Journal Voucher (JV) relating to adjustments to be

made.

Business Logic

Details of non-bank and non-cash transaction shall be entered through a JV.

A JV is created whenever an entry has to be posted to GL but the bank and cashbooks are not affected.

Validations



7.7.6 MAINTAIN CONTRA VOUCHER

Description

This function shall allow the user to enter a Contra Voucher.

Business Logic

Transactions that affect cash account on one hand and bank account on the other hand and vice-versa,

or and bank-to-bank transactions are entered through contra vouchers.

Validations


The voucher should be balanced

7.7.7 QUERY AND APPROVE VOUCHER

Description

This function shall allow the user to query for voucher of any status.


113 | P a g e

Business Logic

Records of all the vouchers shall be maintained and the possible status of the voucher: Approved,

Posted, and Cancelled, Hold can be entered. The user shall search for the records of the vouchers based

on the Type of voucher, Status, Date and Office. A list of Vouchers shall be displayed in a grid. All the

vouchers with status other than “Approved” shall have a link” Approve Voucher” to enable the

approval process. For the Approved voucher, this link shall be disabled.

All the vouchers need to be approved. A voucher shall be printed after its authorization and physically

signed by the person authorizing it. The user can Approve, Cancel, Recheck or Hold a voucher.

Validations

A voucher shall be printed after its authorization.

7.8 Maintain GL and SL Heads Master

Description

This function is intended to add a General Ledger Head in GL Heads Master and SL heads in SL head

master under the various head categories and Head Sub Categories that are defined in the system. GL

Head Code and SL Head code shall uniquely identify each GL Head and SL head respectively. Each GL is

associated with the Head Categories (Assets, Liabilities, Income, and Expenditure) and Corresponding

Head Sub Categories like Fixed Assets, Currents Assets etc.

Business Logic

Each GL code corresponds to a particular Sub head category and then in turn corresponding Head

Category. The GL could have subsequent Subsidiary Ledgers (SL’s) associated with it. The GL Code shall

be maintained centrally and shall be used by different offices as per requirement. This is to ensure

uniformity across the different offices of HUDA.

Also, SL Heads are created under GL heads. The SL code cannot exist independently. A single GL may

have multiple SL’s associated with it but a SL shall be associated with only one GL.

Validations

GL Code should be valid and unique

Only GL description can be modified.

SL Code should be unique

Only SL description can be modified.


114 | P a g e

7.9 Maintain Tax Master

Description

This master is related to various types of tax involved namely Labor welfare cess, sales tax and

work contractor cess

Business Logic

It allows HUDA to charge appropriate taxes as per policy. It includes the with effect from date and the

type of tax to be charged. The Tax rate and state can be defined. Surcharge rates and education cess if

applicable can be defined

Validation

With effect from date and tax type and tax rate have to defined

7.10 Maintain Loans Details

Description

The function is intended to add loan details given/ received by individuals by HUDA.

Business Logic

Details of the loan like borrower/ lender, Scheme, Date, Amount, interest rate, Disbursement/

Repayment schedule, duration and penalty interest shall be captured using this function.

Disbursement details like borrower/ lender name, loan amount, disbursement amount, instalment

start/ end dates can be viewed by this function. Also, outstanding amount along with the other loan

details like disbursed amount and sanctioned amount can be viewed using this function. The interest

shall be calculated for the loans given by HUDA.

Validations

Loan date should be valid

Loan amount should be valid

Recovery start date cannot be less than Recovery End date.

7.11 Maintain Party/ Supplier/ Contractor Master

Description

This function is intended to capture the details of the party/ suppliers/ contractors at different

locations.


115 | P a g e

Business Logic

A unique contractor ID identifies each supplier. Details like contractor name, PAN, sales tax

identification number and address of a supplier/ contractor is captured.

Validations

PAN should be valid and unique and Contractor ID should be unique

7.12 Maintain Estimates

Description

This function is intended to add an Estimate to the system.

Business Logic

HUDA has divided the Estimates of work into various types like External development Cost (EDC),

Internal Development Cost (IDC), Govt. Land, Deposit Work. Each estimate type can have Estimate

categories like Road. Water Supply, Sewerage, Storm Water Drainage, Electrification, Horticulture,

Building Work.

Each Estimate category can have various estimates under it. Various details of an Estimate such as

Estimate Type, Estimate Category, Estimate Id, Estimate Description, Amount, and Sanction Date are

captured through this function. System shall provide facility to add estimates with their association

with sector details. System shall also provide for the search facility for estimates which can also be used

to go to a particular estimate to review and approve it against fixation cost of a sector.

Validations

Estimate Id is unique

Only an authorised person shall be able to add/delete/edit the ‘Estimate Categories’

No work can be booked against an estimate unless the estimate is approved

7.13 Maintain Works Category Master

Description

This function is intended to define different work categories at XEN level. At the divisional level there

are six major categories of work like New Work, Deposit Work, Continuous Work, and Annual

Maintenance.

Business Logic

Details like Category Id and category description and remarks shall be captured in this function.

Validations

Category Description should be valid


116 | P a g e

7.14 Maintain Works Master

Description

This function is intended to define the various works within the existing categories at the XEN level and

assign it to a particular division.

Business Logic

Unique work Id is created whenever a new work is to be started under a given XEN office.

The respective category Id and Category of work is selected and the various details like work Id, work

description, type of work, Estimate Id, Estimate Category and the division at which the work is to be

executed are captured.

Validations

Work cannot be created against an estimate if that estimate is not approved

7.15 Maintain Sale of Tender Form

Description

This function shall be used to view, capture, and delete details of the tender form sold to the

contractor / supplier.

Business Logic

HUDA floats tenders for different works. Tenders Forms corresponding to these works are sold to the

suppliers. Tender forms sold to suppliers shall be captured using this function. The system shall

generate receipts for the same.

Validations

None

7.16 Maintain Tender/ Quotation Submission

Description

This function shall be used to view, capture, and delete details of the tender/ quotation given by the

contractor / supplier.

Business Logic

Suppliers submit Tender forms with quotations and Earnest Money. These details are captured using

this function. Earnest Money of unsuccessful applicants shall be refunded to them.

Validations

None


117 | P a g e

7.17 Open Tender

Description

This function shall be used to shortlist contractors who have quoted minimum amount for the tender

and generate refund orders to the rest of the contractors.

Business Logic

Contractors submit Tender forms with quotations and Earnest Money. Out of them, some contractors

are selected using this function and refund order is generated for the rest of the contractors. The

system; by default; shall select three contractors with minimum amount. Though, this can be over-

ridden by FAS user.

Validations

None

7.18 Award Tender

Description

This function shall be used to award tender to a Contractor out of the list of short listed contractors.

Business Logic

Contractors submit Tender forms with quotations and Earnest Money. A contractor is selected from the

previously short listed contractors using this function and refund order is generated for the rest of the

contractors. The system; by default; shall show the contractor with minimum amount as ‘selected’.

Though, this can be over-ridden by FAS user.

Validations

None

7.19 Maintain MB Register

Description

The screen is to be used to capture the details of the Measurement Book (MB) register.

Business Logic

Various details like Measurement Book (MB) Number, Issued to Whom, Work Id, Division Code,

Division Name, Edit and Delete shall be captured.

Validations

MB Number should be unique

7.20 Maintain Contactor Bill Entry


118 | P a g e

Description

The screen is to be used to capture the details of the bill received from the supplier.

Business Logic

Various details like bill number Bill date, bill status, category id, work id, type of work, contractor id,

agreement Id, total amount, amount paid, current payable amount shall be captured. Sales tax (x% of

current amount), Income Tax (y% of current amount), surcharge on IT (z % of income tax), security,

water charges, miscellaneous deposits and others shall be captured. The values for x, y and z shall be

parameterized in the application depending on the financial year.

Validations

Bill Number should be unique

7.21 Clubbing Contractor Bills

Description

The function is intended to club the various bills received from the contractor against various works

and create a single payment voucher for the same.

Business Logic

Based on the contractor Id selected, all the bills corresponding to the given contractor shall be

displayed along with bill details. Provision shall be made for selecting bills from the displayed bills and a

common voucher shall be posted for the sum equal to the total sum of the selected bills.

Validations

None

7.22 Maintain PPM Receipt Details

Description

This screen is used to capture the payment received from the allottees against various heads like

installment+ charges, extension fees, compounding fees and rent.

Business Logic

Various details like Date on which the receipt is generated, Property Category, Property Sub Category,

Estate Office, Urban Estate, Sector, Plot Number, Name of allottees, Draft/cheque number and Draft

/Cheque Date are captured. A voucher shall be generated on approval of these receipts and the

payment shall be posted in the various SL’s.

Validations

Date should be current Date

7.23 Club PPM Receipt


119 | P a g e

Description

This function shall be used to search and club various receipts received by the estate office and

generate a single voucher for the same.

Business Logic

On the Estate level, PPM receipts can be clubbed together to generate a voucher. Also, Total amount of

all the receipts shall be calculated through the system.

Validations

None

7.24 LAC Details

Description

This function allows the user to add an LAC account to an LAO Office. The details of awards related to

the LAC account are also captured.

Business Logic

Each LAO office has multiple LAC accounts related to it. Each LAC Account has multiple awards

associated with it but at one point of the time it operates for only one award. The payments done for

the purchasing of land in an award are made through these LAC Accounts. Each LAC account has an

Authorization Amount which can be modified by a competent authority.

Validations

Combination of LAO Office, Account Number and Award No. is unique.

7.25 LAC Acquisition Master

Description

HUDA has certain Land Acquisition Offices (LAO) Offices which deal with the purchasing of land from

the land owners. Each LAO is related to multiple Land Acquisition Collectors. A Land Acquisition

Collector is a bank account assigned to an LAO. LAO create awards for the acquisition of land. This

function is to allow to the user to create an award and add the details corresponding to that award.

Business Logic

An award consists of the details of the land to be acquired. An award Id identifies an award. Various

details related to an award for example, Award No, Total area, quality of land, payment amount and

date are captured.

Validations

Award No. is unique

7.26 LAC Payment Details


120 | P a g e

Description

This function allows the user to add the payment details related to an award for an acquisition of land.

Business Logic

The payments done for the purchasing of land in an award are made through these LAC Accounts. The

details related to the payments made for an award no. are captured through this function.

Validations

None

7.27 Maintain Enhanced Compensation

Description

This function shall be used to view, add details of the enhanced compensation to be paid to an owner

as and when a court order is passed for the same.

Business Logic

Each sector can have multiple price enhancements for the plots in the given Sector. There can be

multiple price enhancements on the plot cost. As the parts of the sector may be acquired at different

times the price enhancement can come at different times and may be different for different areas of

the sector... Also the court for the same area can order multiple price enhancements. The total

enhancement will be the cumulative sum of all the enhancements ordered. Through this functionality,

liability of HUDA on account of enhanced compensation can be known for a particular party at a given

award date, court order date and rate.

Validations

None

7.28 Maintain and Revise Budget

Description

This function shall be used to capture and edit details of the Budget.

Business Logic

This function is indented to capture the budget details. Budget shall be allocated or revised for head

category, head sub category, GL and SL levels Before approval of budgets any changes required to be

made can be handled through edit link. But once the budget is approved then the same can be revised

only by competent authority through revision link.

Reports like Budget Estimate for Land Acquisition, Budget Estimate of Revenue Expenditure in Total,

Budget Estimate of Receipt from Government Land Scheme Wise, Budget Estimate of New Sale – Area

Wise and Property Wise, Budgeted Cash Flow, Budget Estimate of Enhanced Compensation Sector Wise

in a Division, Budget Estimate of Enhanced Compensation Division Wise, Budget Estimate of Receipts

and Budget Estimate of Payments shall be generated by the system.


121 | P a g e

Validations

Budget date should be a valid date.

7.29 Maintain Fixed Assets Category Master

Description

This function is intended to define the Fixed Asset Categories used by HUDA

Business Logic

Fixed assets are categorized for calculation of depreciation. Every Fixed Asset Category is mapped to a

fixed asset GL code and a Depreciation GL code.

Validations

Fixed Asset Category is valid.

7.30 Maintain Fixed Asset Block Master

Description

This function is intended to create block for Fixed Assets

Business Logic

HUDA has defined certain blocks, which are mapped with the Fixed Asset categories for Income Tax Act

Depreciation Calculation.

Validations

Fixed Asset Block should be valid. Fixed Asset Block should be unique.

7.31 Maintain Fixed Asset

Description

This function is intended to add/ maintain Fixed Asset in the existing lists of Fixed Assets.

Business Logic

Various details like the Fixed Asset Number, HUDA defined Fixed Asset Number, Fixed Asset category,

Category description, Purchase Price, Location, Depreciation Start Date and contractor name shall be

captured.

Validations

Fixed Asset Number should be valid and unique

HUDA defined Fixed Asset Number should be valid and unique

7.32 Maintain Fixed Asset Depreciation Rate Master

Description


122 | P a g e

This function is used to capture the details of the depreciation rates and the dates from which the

depreciation rates come in to effect for different categories of Fixed assets.

Business Logic

Various details like the Fixed Asset Category, Depreciation Rates and Dates from which the mentioned

rates come into effect are captured

Validations

“Dates Applicable From” is a valid date

7.33 Depreciation Calculation of Fixed Assets

Description

This function is used to calculate depreciation on a Fixed Asset Category for the period specified

between “Date From” and “Date To”

Business Logic

Various details like the Fixed Asset Category, Depreciation Rate and Date From and Date to be

captured. Based on the above details provided the depreciation is calculated and accordingly provision

is given to post a voucher from the same.

Validations

‘Date To’ cannot be an earlier date than ‘Date From’

7.34 Maintain Fixed Asset Sale

Description

This function is used to capture the details of the sale of the Fixed Asset.

Business Logic

Various details for the sale of the fixed asset like fixed asset category, fixed asset number, sale date are

captured. Details like Profit and loss on the sale and Written Down value (WDV) shall be calculated

Validations

Fixed Asset number is valid

7.35 Maintain Fixed Asset Write Off

Description

This screen shall be used to capture the details of the written off Fixed Asset.

Business Logic

Various details for the written off fixed asset like fixed asset category, fixed asset number, write-off

date are captured. Details like Profit and loss on the sale and WDV shall be calculated


123 | P a g e

Validations

Fixed Asset number should be valid

7.36 Maintain Transfer of Fixed Assets

Description

This screen shall be used to capture the details of the written off Fixed Asset.

Business Logic

Various details for the transfer of the fixed asset like fixed asset category, fixed asset number, transfer

date; current location and transfer to location are captured. Details like Profit and loss on the sale and

WDV are calculated

Validations

Fixed Asset number should be valid

7.37 Maintain Party Bill Entry

Description

This screen shall be used to capture the details of bills received from parties at the office for which

payment has to be made.

Business Logic

Various details like Office type, Office Code, Office Name, Party Code, Party Name, Party type, Bill

Number, Bill Date, Bill Amount, Bill Particulars, and Payment type, TDS Percentage. TDS Amount,

Payable Amount, Bill Status shall be captured.

Validations

The Bill Number should be valid.

7.38 Club Party Bills

Description

This screen shall be used to club various approved bills of a parties received at an office and generate a

voucher for the same.

Business Logic

Various details like Office type, Office Code, Office Name, Party Code, Party Name, Party type, shall be

captured. Facility shall be provided for searching and selecting the bills of a particular party and posting

a voucher for the total amount of the selected bills.

Validations

At least one bill should be selected for generating a voucher.


124 | P a g e

7.39 Maintain Payroll Data

Description

This function shall be used to enter Details of the Payroll at a Particular Office level

Business Logic

The details of the Earnings and Deductions are entered at the Office level for a particular month of the

financial year and a voucher is generated for the same amount.

Validations

Net payable amount cannot be negative.

7.40 Generate Credit Debit Note

Description

This function shall be used to generate a Credit Debit Note.

Business Logic

A debit/ credit note may be generated at Head Office/Estate Office/Division Office (HO/EO/DO) level.

Corresponding credit/ debit note is generated by acknowledging the debit note and approving credit

note.

Validations

Note Number should be unique

7.41 View Debit Note

Description

This function shall be used to view debit notes and acknowledge.

Business Logic

Various debit notes can be viewed through this function and can be acknowledged to facilitate inter

unit reconciliation

Validations

None

7.42 View Credit Note

Description

This function shall be used to view credit notes and approve.

Business Logic


125 | P a g e

Various credit notes can be viewed through this function and can be approved to facilitate inter unit

reconciliation.

Validations

None

7.43 Upload Bank Statement Details

Description

This function shall be used to upload bank statement details when the details are available in an

electronic file format.

Business Logic

The Bank statement details are available in form of a scroll. If the scroll is in an electronic file format,

the same can be uploaded into the system.

Validations

None

7.44 Enter Bank Statement Details

Description

This function shall be used to enter bank statement details when the details are not available in an

electronic file format.

Business Logic

The Bank statement details are available in the form of a scroll. If the scroll is not in an electronic file

format, the same shall be entered manually.

Validations

None

7.45 Perform System Reconciliation

Description

This function shall be used to perform System reconciliation of the Bank statement with that of the

ledger of that bank account in HUDA.

Business Logic

The Bank statement details are fed in to the system, either through manual entry or upload of data

received from the banks. The Bank statements are reconciled with the voucher details within the

system. The cheque number, cheque date and amount shall be used to reconcile the bank statements

by the system.

Validations


126 | P a g e

None

7.46 Perform Manual Reconciliation

Description

This function shall be used to perform Manual reconciliation of the Bank statement with that of the

ledger of that bank account in HUDA.

Business Logic

The Bank statement details are fed in to the system, either through manual entering or uploading. The

Bank statements are reconciled manually one at a time with the voucher details within the system.

Validations

None

7.47 Update Bank Statement Details

Description

This function shall be used to update the Bank Statement Details if the entries are not correct.

Business Logic

The Bank statement details are fed into the system either manually or by uploading. The function

“Update Bank Statement Details” shall allow the user to make correction in the Bank Statement details

if any mistake has been made when entering.

Validations

None

7.48 Update Voucher Cheque Details

Description

This function shall be used to update the Voucher Cheque Details if the entries are found to be

incorrect.

Business Logic

There is a possibility that the voucher details entered in the system may have some mistakes. The

function “Update Voucher Cheque Details” shall allow the user to rectify the errors in the voucher

details.

Validations

None


127 | P a g e

7.49 Refund of Security

Description

This function shall be used to verify the details of the security deposit from a contractor against a

particular work and generate a voucher for the refund of the same when the work has been completed.

As soon as the final bill is entered for the given work, the work is assumed to be completed. The refund

shall have to be approved before refund voucher can be generated. When the status stands approved

from the approver, refund voucher shall be generated

Business Logic

The Earnest Money, deposited at the time of Tender Quotation, shall be deposited as security. At the

payment of each of the running bills and Final bill, security charges shall be deducted from the Bill

amount and shall be deposited as security.

Once the work is complete and the final bill is generated, the total amount of the security deposited

shall be refunded to the Contractor, after approval.

Validations

The refund can be made only if the status of work is complete

The refund shall have to be approved before refund voucher can be generated.

7.50 Calculation of sector costs

Description

This function shall be used to enter the details of the various costs incurred on a sector.

Business Logic

The project sub costs under a given project cost may differ from time to time. Facility shall be given

here to enter the project sub costs as per the need. HUDA incurs three types of costs on sectors -

Development Cost, Land cost and Indirect Cost. These costs shall be captured to fix the price of sector

cost.

Validations

Total cost cannot be zero.

Project sub cost should be unique for same type of project cost

7.51 Maintain TDS details

Description

HUDA deducts Tax Deducted at Source (TDS) from the payment of the bills which is then paid to the

Income Tax department. This function shall be used to maintain the details of TDS paid to the Income

Tax department.


128 | P a g e

Business Logic

TDS amount deducted by HUDA from the bill payment shall be displayed on the screen. The option

shall be given to the user to select the deducted TDS details which shall be paid to the central

government via a single TDS Challan. The details of the Challan shall be captured on the screen which

shall be used to print the Form16 report for the deductees.

Validations

None

7.52 Schedule Master

Description

This function is indented to new schedule to Balance sheet or profit loss (income and expenditure)

statements and Sector Account.

Business Logic

This function shall maintain the schedules for Balance sheet and profit loss (income and expenditure)

statements and Sector Account.

Schedule Code shall uniquely identify each Schedule.

Validations

Schedule code should be unique.

7.53 BSPL Schedule Details

Description

This function is indented to add Balance sheet or profit loss schedules.

Business Logic

This function shall maintain the schedules for Balance sheet and profit loss statements. Descriptions

can be added to system and shall belong to a GL head, and can be of type Debit or credit.

Validations

None

7.54 De clubbing of bills

Description

As part of revising the clubbed vouchers, de-clubbing may be required by approving authority.

Business Logic


129 | P a g e

While a voucher is being reviewed, an approver shall have the option to de club certain entries as

appropriate. This shall post the voucher without those bill entries. The voucher then can be re-

reviewed and approved. The de clubbed bills status shall be changed to unpaid.

Validations

None

7.55 Maintain System Parameters

Description

This functionality allows entering values of various parameters being used throughout FAS.

Business Logic

By providing screen for maintenance (add/change/delete) of system parameters, the flexibility of

application is increased. These parameters are then used to organize various elements of code,

screens, reports etc.

Validations

The value of system parameters must conform to the usage type i.e. alphanumeric, numeric,

alphabetic etc.

7.56 External interfaces

7.56.1 INTERFACE DESCRIPTIONS

The bank shall provide Application details of the applicants received against scheme floated by HUDA in

text files and shall be uploaded in the system. For successful uploading the text file should adhere to a

predefined supplied format.

7.56.2 MESSAGE/ INTERFACE SPECIFICATIONS

Title: Application Upload

Description: The flat file containing application details of the applicants against a

particular scheme floated by HUDA

Business

Purpose:

The bank shall act as an agent and shall receive the applications. The

applications shall then be converted into electronic format by the

bank. The text files produced by the bank shall then be uploaded

through the interface into the system.

7.56.3 PPM INTERFACE

All the payments made and received by HUDA shall be captured by Plot and Property Management

(PPM), and shall act as the source to the FAS module.


130 | P a g e


Through the PPM, all payments made to external or third party like advocates and payments received

from external sources such as allottees, shall be entered into the system and used for further

calculation and managing accounts.

7.56.5 MESSAGE/INTERFACE SPECIFICATIONS

Title: PPM

Description: Details of payments made and received shall be entered using the

PPM

Business

Purpose:

The PPM module shall act as an agent to capture the payment

details.

7.57 User Access Control and Security

The users of the HUDA system are categorised into the following groups

7.57.1 OPERATING SYSTEM LEVEL

Administrator shall be responsible for system administration and housekeeping of the HUDA servers

7.57.2 APPLICATION USER

Users will be assigned a unique user id and password. User ID and password shall be used to logon to

the system. In case of an invalid combination of these two codes, the system shall display an error

message and prevent further processing. There is a disclaimer stating controls and responsibility of

users and it is to be accepted to login. Without accepting the terms and conditions in disclaimer user

cannot login into the system. The users shall be divided into 2 groups

a. Individual Users – Users will have access to the application software only. Users will have

access to specific screens and functions within them basis on the role. Roles shall be

assigned to the user depending on his area of operation. User rights shall also be

+controlled by the location of the user. Users shall only view or modify data pertaining to

their location.

b. Administrative Users – Users shall have access rights for user creation and assignment of

access rights to the application users. Administrative users shall also have rights to create

program heads for the menu and associate forms to these heads. Administrative users

would also be able to reset the password of the individual users.

7.58 FAS Reports Description

The list of various reports generated through FAS system is given below:-


131 | P a g e

1. Chart Of Accounts

2. General/Subsidiary Ledger

3. Day Book Report

4. Trial Balance

5. Fund Flow Details

6. A/c Mapping With Schedule

7. Final Accounts

8. Works Report

9. Estimate Report

10. MB Issue Register

11. Queue List of Bills

12. Contractor Register

13. Refund Of Security

14. Contractor Bill

15. Maturities Due List

16. Price Fixation

17. Land Acquisition

18. LAC Authorization Report

19. Enhanced Comp. Summary

20. Enhanced Comp. Calc.

21. LAC Cheque Register

22. Budget Estimate

23. Budget Head wise Variance

24. Reconciliation Details

25. Credit Debit Note Register

26. Bank Details

27. Bank Voucher Report

28. Cash Voucher Report

29. Journal Voucher

30. Voucher Status

31. Cash Voucher Range

32. Contra Voucher

33. Journal Voucher Range

34. Voucher Check List

35. Bank Voucher Range

36. Cheque Report

37. Fixed Asset Depreciation


132 | P a g e

8. ANNEXURE B - FUNCTIONAL REQUIREMENTS PPM MODULE

This section briefly describes the overall capability of the functionality to be provided by the proposed

PPM module of HUDA application. This module deals with maintaining the property inventory, current

status of individual property, property registration and allotment details, payment details of plot

holders, generation of various notices and certificates. This is an internal application accessible only in

HUDA offices

8.1 Maintain Zone Master

Description

This function is intended to add a Zone in the Zone Master. Zone Code will identify each Zone uniquely.

Business Logic

HUDA has divided Haryana in various zones. Each zone is further divided into Estate Offices, which in

turn has multiple Urban Estates in it. Date From and Date To shall be captured to capture the validity of

existence of a Zone.

Validations

Zone Code should be unique.

Zone name and Date to can be modified.

Date to can’t be less than the Date From.

Date To will be populated if the Zone ceases to exist. This can happen when one zone gets divided

into multiple new zones or two or more zones merges and forms a new zone.

8.2 Maintain Estate Office Master

Description

This function is intended to add an Estate Office in the Estate Office Master. Estate Office Code shall

identify each Estate Office uniquely. Estate Office address shall be captured to display the same on the

reports.

Business Logic

HUDA has divided Haryana in different zones. Each zone is further divided into multiple Estate Offices.

Date From and Date To shall be captured for the validity of Estate Office in the Zone.

Validations

Zone Code should be valid.

Combination of Estate Office Code and Date From shall be unique.

Estate Office name, address and Date To can be modified.

Date to can’t be less than the Date From.


133 | P a g e

Date To shall be populated if the Estate Office moves from one zone to another.

8.3 Maintain Urban Estate Master

Description

This function is intended to add an Urban Estate in the Urban Estate Master. Urban Estate Code shall

identify each Urban Estate uniquely. Urban Estate address shall be captured displayed on the reports.

Business Logic

Each Estate Office has multiple Urban Estates under it. Date From and Date To shall be captured for the

validity of Urban Estate in the Estate Office. Zone potential, which is divided into High, Medium and low

shall also be captured in order to calculate the different types of fees applicable on property.

Validations

Zone Code should be valid.

Estate Code should be valid.

Combination of Urban Estate Code and Date From shall be unique.

Zone potential should be valid.

Urban Estate name, address and Date To can be modified.

Date To cannot be less than the Date From.

Date To should be populated if the Urban Estate moves from one Estate Office to another.

8.4 Maintain Property Category Master

Description

This function is intended to add property category in the property category master. Each property

category code shall uniquely identify the property category.

Business Logic

HUDA has divided property into various categories like Residential, Commercial, Group Housing

Societies, Industrial, Institutional, and Community Buildings. This function will be used to assign a

unique code to each property category, which shall be used throughout the application.

Validations

Property Category Code should be unique

Only Property Category description can be modified

8.5 Maintain Property Sub Category Master

Description

This function is intended to add property sub category in the property sub category master. Each

property sub category code shall uniquely identify property sub category.


134 | P a g e

Business Logic

Property categories are further divided into property sub categories. Details of few property sub

categories are mentioned in the following table:

Table 1: Property Sub Categories

S.

No.

Property Category Property Sub Category

1. Residential 1 Marla, 2 Marla to 2 Kanal

2. Commercial SCO, SCF, Double Story Shops, Showrooms, Booths, Service

Booths, Small Booths, Kiosks, Hotel, Cinema, Shopping Malls,

Multiplexes, Departmental Stores, Commercial Stores

3. Group Housing

Societies

Government dept., Welfare Housing Societies registered under

companies Act, Group Housing Societies registered under

Societies Act, Group Housing Societies for EWS

4. Industrial Industrial Plots

5. Religious Temple, Gurudwara, Church, Mosque, Charitable & Social

Societies

6. Private Hospitals Nursing Home, Clinic, Hospitals

7. Govt. Hospital Dispensary, Clinic

This function shall be used to assign a unique code to each sub category, which shall be then used

throughout the application. The following information should be captured at the property sub category

level:

Type of property

Default mode of allotment

Default number of instalments

Default instalment type

Additional cost for preferential plots

Additional cost for special preferential plots

Percentage of total cost due at the time of application

Percentage of total cost due on allotment

Permissible constructed floor

Permissible constructed floor area

Validations


135 | P a g e

Property Category Code should be valid

Property sub category Code should be unique

Property Sub Category Code cannot be modified

8.6 Maintain Interest Rates

Description

This function is intended to capture details of the interest rates charged by HUDA.

Business Logic

HUDA charge different interest rates for different interest types. Different interest types are possession

interest, delay interest, etc. HUDA also charges same interest rates for all the allotments during a

particular period of time. Date From and Date To shall be captured for interest rates of various interest

types during a period.

Validations

Interest Type should be valid.

Date To cannot be less than the Date From.

Date To shall be populated if the interest rate changes from one period to another.

8.7 Maintain Fee Master

Description

This function is intended to capture the details of various fees being charged by HUDA.

Business Logic

HUDA charges different fees for different fee types and fee sub type. Different fee types are:

Transfer Fee – Residential

Transfer Fee – Commercial

Extension Fee – Residential

Extension Fee – Residential EWS

Extension Fee – Commercial up to 2 storeys

Extension Fee – Commercial more than 2 storeys

Compounding fee

Map fee (per print)

Plan fee (per sq.m.)

Scrutiny fee (per sq.m.)

Revalidation fee (per sq.m.)

Registration fee


136 | P a g e

Registration renewable fee

Extension-Surcharge fee

Extension-Rebate fee

Administrative fee

Different fee sub types are

Architects, Plumbers for Registration fee

First transfer, second transfer, third transfer and fourth transfer for Transfer Fee – Residential and

Transfer Fee – Commercial

First Block, Second Block, Third Block, Fourth Block, Fifth Block, Sixth Block and Seventh Block for

Extension Fee – Residential, Extension Fee – Commercial up to 2 storeys, Extension Fee –

Commercial more than 2 storeys, Extension Fee – Commercial up to 100 sq. Yards

Family transfer, Sale Deed, Will or In-testate Death for Administrative fee

HUDA charges same fee for all the allotments during a particular period of time. Fixed fee amount or

fee based on percentage is captured for each fee type and fee sub type. Fee charged differs Zone

potential wise and property sub category wise. Validity Start Date and Validity End Date shall be

captured for time period during which the fee amount or fee rate is applicable.

Validations

Fee Type should be valid.

Combination of Fee Type, Fee Sub Type and Validity Start Date shall be unique.

Zone Potential should be valid.

Property Sub Category Code should be valid.

Validity End Date cannot be less than the Validity Start Date.

Validity End Date will be populated if the fee changes from one period to another.

8.8 Maintain Surcharge Master

Description

For most of the categories of plots, 10% of tentative cost of the plot is paid as earnest money at the

time of submission of application. The next 15% of the tentative cost of the plot is paid within the

specified time period from the date of' issuance of letter of allotment. If this 15% of the amount is not

deposited within the stipulated time, then surcharge is levied. This function is intended to facilitate the

parameterization of the surcharge rate and officer level that has the authority to condone the

surcharge.

Business Logic

Facility shall be provided to enter the rate of surcharge and authority to condone the surcharge for the

delay in terms of days. Validity Start Date and Validity End Date shall also be captured to capture the


137 | P a g e

time period for which the rate of surcharge is applicable. The days after which surcharge shall be levied

is maintained at the property category level in the Property Category master. Though the authority can

condone the surcharge but the delayed period interest shall always be levied on the principal amount.

Besides surcharge the penal interest shall also be calculated for the delayed period.

The table below shows the various rates for the surcharge applicable for the delay in days and the

authority to condone surcharge.

Table 2: Surcharge Rates

Property

Category

Days From Days To Authority to Condone Rate of

Surcharge (%)

Residential 0 30 Estate Officer 5

31 45 Administrator 7.5

46 60 Chief Administrator 10

61 Chairman

Commercial 0 15 Estate Officer 2.5

16 30 Administrator 5

Industrial/

Institutional

0 30 Estate Officer 5

31 60 Administrator 7.5

61 90 Chief Administrator 10

Further if surcharge shall not be paid within the extended period then provision shall be made to cancel

the allotment and change the plot status to vacant.

Validations

Property Category should be valid.

Days To, if populated, should not be less than Days From.

Validity End Date should not be less than the Validity Start Date.

Validity End Date should be populated if the rate of surcharge changes from one period to another.


138 | P a g e

8.9 Maintain Advocate Master

Description

This function is intended to add advocate details in the Advocate Master.

Business Logic

HUDA shall capture the details of the advocates associated with HUDA. An advocate shall be engaged

with a court type. Date From and Date To shall be captured to know the time for which an advocate is

associated with HUDA

Validations

Date To can be modified

Date To cannot be less than the Date From

8.10 Maintain Reservation Category Master

Description

This function is intended to capture the percentage of plots being reserved by HUDA for allotting

residential properties to the various reservation categories.

Business Logic

HUDA maintains the same reservation percent for all the residential plot allotments during a particular

period of time. Details like reservation category code, reservation sub category code, and diversion sub

category will also be captured.

Reservation under schedule castes reservation category is further been segregated into two

reservation sub categories that is Group ‘A’ and Group 'B'. Similarly, reservation with regard to

backward class reservation category is further divided into two reservation sub categories that is Group

‘A’ and Group 'B'.

In case of non-availability of sufficient number of applicants in one reservation sub category, the

applicants from other reservation sub category shall be considered for the purpose. This diverted

reservation sub category will be captured as the ‘Diversion Sub-Category’. For example, reservation

with regard to schedule castes reservation category and Group ‘A’ reservation sub category will have

Group 'B' as the ‘Diversion Sub-Category’

Reservation percent differs property sub category wise. Validity Start Date and Validity End Date will be

captured to capture the validity of reservation percent for the given reservation sub category for the

given period.

Validations

Reservation Category should be valid.

Reservation Sub Category should be unique.


139 | P a g e

Diversion Sub Category should be valid.



Validity End Date will be populated if the reservation percent changes from one period to another.

8.11 Maintain Compoundable Violation Master

Description

This function is intended to capture the details of various Compoundable / Non Compoundable

Violations and the related Fees.

Business Logic

HUDA maintains Compoundable / Non Compoundable violation fixed fee and fee rates for all the

residential plots. Details like violation category, violation description, property category, property sub

category, compounding fixed fee, compounding fee rate and remarks shall be captured in this function.

Violation fixed fee and fee rates also differ property sub category wise. Validity Start Date and Validity

End Date for which violation fee is same shall be captured and whenever there is a change in rate, new

Validity Start Date and Validity End Date shall be captured along with new rates.

Validations

Combination of Violation Category, property category, property sub category and Validity Start

Date should be unique.

Property Category should be valid.



Validity End Date will be populated if the compoundable fees change from one period to another.

8.12 Maintain Procedure/Process Master

Description

This function shall be used to capture the various processes like Building Plan Sanction, DPC

Certification, POC Certification, OC Certification, Demarcation Plan, Sanction of Building, No Dues

Certificate, Non-Encumbrance Certificate, Mortgage Permission, Conveyance Deed, Transfer Permission

Letter, Re-Allotment Letter (Final Transfer) and so on along with the ‘Days to Process request’

information. It will also have links to capture:

The list of documents that the applicant is required to submit for various processes

The approval levels required for issue of different certificates


140 | P a g e

Business Logic

The applicant shall submit a request along with the list of documents. This request can be either for

transfer of property, mortgage of property, completion certificate, DPC certificate, POC/OC certificate

or any other request. Facility shall be given here to maintain the list of the mandatory and optional

documents that the applicant is required to submit along with the request form. This list will be used to

generate the checklist for various processes in the Application Received screen. Refer Error! Reference

source not found. for list of documents.

These request forms shall undergo an approval process by HUDA officials. The facility shall be provided

to capture the processing authority hierarchy for various certificate request applications.

Validations

None

8.13 Maintain Sector Master

Description

This function is intended to capture the details of the sector carved out by HUDA.

Business Logic

Urban Estate wise details of sectors shall be maintained by this function. Sector ID shall be unique

within an Urban Estate. Sector details like area of sector, planned area (clear area and encroachment

area), non-planned area (clear area and encroachment area) of the sector, total area acquired,

property sub category wise number of plots along with its plot numbers, zoning plan, demarcation

plan, amendment plan details, price enhancements and offer of possession details shall be captured.

Entire sector may not be demarcated in one go; each sector will be allowed to have multiple

demarcation plans for various parts of the sectors. Demarcation plan will either be total or in parts. The

first demarcation plan approved is called ‘Total’; other is called ‘Part’. For each Demarcation plan,

drawing number, drawing approval date, number of plots under each property sub-category, their

physical plot numbers, length, breadth and dimension of the plot shall be captured. The demarcation

plans can be changed by one or multiple amendment plans. For each amendment plan, amendment

number, amendment date, amendment notes, number of plots added or deleted for each sub-category

shall be captured in the application.

One Sector can have multiple Zoning plans like Residential, Commercial or Institutional zones. Zoning

plan will also be in either total or part. The first Zoning plan approved is called ‘Total’; others are called

‘Part’. For each Zoning plan, drawing number, drawing approval date, number of plots under each

property sub-category and their physical plot numbers shall be captured. The zoning plans can be

changed by one or multiple amendment plans when required during demarcation plan.

The plots within a sector may be ready for possession at different dates therefore the provision shall be

provided to enter multiple entries for the Offer of Possession for a sector. Property sub category wise


141 | P a g e

details like range of the plot numbers for which possession can be offered and possession date shall be

captured by the system.

Provision shall be given to generate ‘Possession List’ and ‘Offer of Possession Letter’ for all the plots in

the given sector of the Urban Estate for which the Possession has been given by the development wing

that is for which Possession Date has been populated.

Also each sector can have multiple price enhancements for the plots in the given Sector. There can be

multiple price enhancements on the plot cost too. As the parts of the sector may be acquired at

different times the price enhancement can come at different times and may be different for different

areas of the sector. The demarcation plan number will allow the enhancement rate to be associated

with the plot number following the particular area of the sector for which the enhancement is being

asked for. Also the court for the same area can order multiple price enhancements. In this case the

Demarcation plan number will be the same. The total enhancement will the cumulative sum of all the

enhancements ordered. The enhancement rates are different for General and EWS categories. The

General Category rates will be applicable to all Property Sub-Categories except the EWS Sub-

Categories. Details like count of the enhancement being effected; enhanced rate of the land per sq.

meter (separate for General and EWS category), and date on which the enhancement is applicable will

be captured.

Provision shall be given to generate ‘Demand Letters’ for each plot falling in the area of the sector for

which enhanced compensation is ordered by the court.

Validations

Urban Estate Code should be valid

Sector ID should be unique within the Urban Estate Code

Property Sub Category Code is valid

8.14 Maintain Acquisition Details

Description

This function is intended to capture the details of the land acquired by HUDA in the given Urban Estate.

Business Logic

Acquisition details like Award number, Urban Estate for which the land is acquired, date on which the

area is acquired and total area acquired in acres shall be captured. Land falling in multiple sectors can

be acquired under one acquisition award number. Facility shall be provided to capture multiple Sector

Ids and area acquired for the sector under each award number.

Multiple properties are acquired along with the award of the land. For example, properties like farms,

orchids, buildings, industrial sheds, unauthorized houses. Details of the properties acquired along with

the land like property type, compensation money paid for the acquisition, property status that is

whether ‘Sold’/’Unsold’, date of sale, amount received as a result of Auction / Lease / Rent, Remarks if

any shall be captured.


142 | P a g e

In each acquisition land may be acquired from multiple Village / Mauja’s. Details like name of the

village / Mauja number, Area of the Village / Mauja number acquired, Khasra Number and area of

Khasra acquired shall also be captured.

Validations


Sector ID should be valid

Sum of the area acquired for sectors cannot be more than the total area acquired under a

particular award number.

On entry of the sector ID and area acquired for the sector record, total area acquired at sector level

will be updated.

8.15 Maintain Property Details

Description

This function is intended to capture the details of the plots as captured during the maintenance of the

sector master.

Business Logic

Property details like number of current owners of the property, reservation category and reservation

sub category of the original allotment, original owner’s name and address, current owner’s name and

address, joint holders name and address, previous owner’s name and address, General Power of

Attorney (GPA) details, details of transfer, survey details, property dimension, property area, incidental

area, cost, increased area cost, enhancement cost, date of enhancement, total cost, payment details,

location status, issue date for various certificates shall be captured.

GPA/SPA details shall include

Name

Father/husband name

Correspondence address

Permanent address

GPA/SPA registering authority

Date on which GPA/SPA is signed

Date till which GPA/SPA is valid.

Provision shall be provided to upload the signature and photograph files for the owner, joint holders

and for GPA. File naming convention for signature file will be ‘Urban Estate Code + Sector ID + Plot

number + owner/joint holder/GPA + First Name + Sign’. File naming convention for photograph file will

be ‘Urban Estate Code + Sector ID + Plot number + owner/joint holder/GPA + First Name + Photo’


143 | P a g e

Transfer details would get populated from the ‘Transfer of Property’ function. Transfer details shall

include reason for change of ownership, date on which previous ownership changed and type of

transfer.

Property is surveyed for multiple activities. For example, when applicant applies for DPC certificate, OC

certificate, Transfer of property, Building Plan approval, Mortgage certificate and so on. There can be

general survey also. Survey details like survey date, nature of survey, area of the property, whether

constructed or not, if constructed then the details about the constructed floor and constructed floor

area, remarks of Junior Engineer, Misuse if any found by JE during Survey, violation category, violation

description, type of finding, area violated, compounding fee, Notice section number, date of issue of

notice, action taken by owner and date on which action taken by owner shall be captured.

Property details data will be used to generate the Urban Estate wise, Sector wise list of Vacant/

Resumed/ Cancelled/ Un-allotted/ Under Court cases plots.

Validations



Property Sub Category Code should be valid

8.16 Maintain Floatation Scheme

Description

This function is used to enter all the scheme-related information into the system.

Business Logic

One scheme can cover plots of different sub categories spanning in multiple sectors across multiple

Urban Estates. Facility shall be given to add available plot numbers in different sub categories in

multiple sectors of various Urban Estates to the scheme. Date of floatation of scheme, associated bank

codes, branch codes and property cost of each sub category of plot shall also be captured. Provision

shall be given to upload the application registration data provided by the bank collecting the

application forms and to automatically generate the registration numbers for all the eligible applicants

for a particular scheme. The registration status of the scheme shall also be maintained in the HUDA

application. The registration number shall be generated in a sequential manner urban estate, property

category, property sub category, reservation category, and reservation sub category wise.

This data will be used to generate the plot cards of all properties being offered for allotment in the

particular scheme for manual lottery.

Validations

Plot number added in the scheme should be valid and available plot.

Application registration data provided by the banks is in the pre-agreed format.

The application user has manually verified application registration data and application status has

been set to ‘Eligible’.


144 | P a g e

8.17 Maintain Application Registrations

Description

The Residential plots in different sectors are offered by HUDA by advertising in the leading newspapers

from time to time. Applications are invited for allotment of different categories of plots through these

advertisements and received by the prescribed Banks. Conducting the open draw from the applications

received against the advertisement makes allotment. All the successful applicants are issued a letter of

allotment by indicating all terms and conditions of allotments with mode and schedule of payment.

This allotment is made as per the provisions of HUDA Act, 1977.

HUDA receives application registration details from banks (authorized by HUDA for registration to the

proposed Scheme) in the electronic format. This data shall be uploaded into the HUDA application. This

uploaded data would then be manually cross verified by HUDA staff against the actual application form

and corrected for any errors. This function shall be used to modify the record either to correct the

errors found in the verification process or to update any requests related to address change etc. from

the applicant.

Business Logic

The banks will send application registration details for one scheme in one file. This file shall be

uploaded in the application and then facility shall be provided to manually update the details as per the

physical application forms. Provision shall also be given to Accept/Reject an application. On accepting

the application, status shall be set to Eligible (‘E’) and if rejected it shall be set to Rejected (‘R’). In case

applicant withdraws the application, facility shall be provided to set the application status to

Withdrawn (‘W’).

This data shall be used to generate reports for applications received, verified list of applications

received, list of rejected applications, list of withdrawn applications, master list of eligible applications

received, registration cards to be send to all eligible applicants, stub cards of all eligible applicants for

manual lottery. It shall also be used to generate the ready reckoned mapping the application number

to the registration number.

If the applicant is successful in the draw, the allotted plot number shall be populated from the ‘Draw

Results’ function and the ‘Eligible’ application status shall be changed to ‘S’ (Successful). If the applicant

is unsuccessful in the draw, the refund order number will be populated from the ‘Generate Refund

Order’ function and the ‘Eligible’ application status shall be changed to ‘U’ (Unsuccessful).

Validations

Scheme number should be valid



Property sub category code should be valid

Reservation category code should be valid

Reservation sub category code should be valid


145 | P a g e

Bank code and branch code should be valid

8.18 Maintain Draw Results

Description

HUDA on its discretion may hold manual lottery. In this case the results need to be entered into the

system.

Business Logic

Facility shall be given to enter registration numbers against the plot numbers in different sub

categories of multiple sectors across various Urban Estates in the scheme. Date of draw of scheme shall

also be captured. The applicant registration details shall be updated with the allotted property number.

This data will be used to generate the list of successful applicants after the draw.

Validations

Registration number should be valid

8.19 Allotment of Property HUDA allots different allotment procedure for allotting plots to the different categories of the plot. The

different allotment procedures are explained in the following section.

8.19.1 COMMERCIAL PROPERTY

Description

The commercial property can be classified into

1. Hotel

2. Cinema

3. Shopping Malls

4. Multiplexes

5. Departmental Stores

6. Commercial Stores

7. Shop Cum Offices

8. Shop cum Flats

9. Double Storey Shops

10. Booths

11. Service Booths

12. Kiosks


146 | P a g e

The property can be a built up structure constructed by HUDA or a site. HUDA always auctions the

commercial property.

Business Logic

The following process shall be followed by the system after allotment of the commercial property.

For allotment of commercial property system shall following process

Successful bidder shall have to pay 10% of bid amount at the time of auction.

Allotment letter shall be issued.

15% of the total cost shall be due within 30 days from the date of issuance of allotment letter.

If successful bidder surrenders before the approval of the bid by Zonal Administrator, full amount

shall be refunded back to the allottee otherwise 10% amount shall be forfeited.

If this 15% amount is not deposited within 30 days of date of issue of allotment letter, the

surcharge shall be levied along with the delay interest from the date of allotment. Further if

surcharge is not paid within a maximum of 30 days, the allotment shall be cancelled.

If the 15% amount is deposited within the stipulated time (or paid along with the surcharge), the

remaining 75% of the cost shall be paid in lump sum within 60 days of the allotment without

interest or shall be divided into fixed number of instalments

If the instalments are not paid as per the schedule, then a delay interest on the due amount shall

be imposed. This interest is calculated for the number of days by which the instalment is overdue.

After HUDA offers the Possession of the site to the plot holders, the reducing simple interest called

possession interest shall be imposed from the date of offer of possession on the remaining amount

due towards the plot holder.

In case allottee desires to deposit full cost of the plot after 60 days of the allotment or in between

the schedule of payment, interest shall be charged up to the date of payment.

The allottee shall be given a fixed time period from the date of offer of possession as Construction

period. Over the completion of construction period if the plot holder do not completes the

construction then extension fee shall be charged.

Facility shall be provided to process the allottees request for mortgage certificate, partial/full

completion certificate, transfer application and so on.

Facility shall be provided to print the show cause notices for the allottee whose instalments are not

regular or who are misusing their property.

The option shall be provided to resume the property.


147 | P a g e

8.19.2 RESIDENTIAL PROPERTY TO GENERAL PUBLIC

Description

HUDA always allots the residential property by floating a scheme to the general public and holding a

draw of allotment. Applicants pay 10% of tentative cost of the plot as earnest money at the time of

submission of application.

Business Logic

The following process shall be followed by the system after allotment of the residential property.

Provision shall be provided to print the refund orders for the unsuccessful applicants.

For the successful applicants allotment letter shall be issued.

The next 15% of the tentative cost of the plot shall be paid within 30 days from the date of issuance

of letter of allotment.

1. If allottee surrenders the plot within 30 days of the allotment, then 100% amount shall be

refunded back to the allottee and the plot status shall be changed to vacant.

2. If this 15% of the amount shall not be deposited, a further grace of 60 days shall be given with

delay interest. Failing which surcharge shall be levied. Further if surcharge shall not be paid

within maximum of 30 days then provision shall be made to cancel the allotment and change

the plot status to vacant.












If the price of plot is enhanced then provision shall be given to charge enhancement fee from

allottee.


completion certificate, transfer application and so on.




8.19.3 RESIDENTIAL PROPERTY TO EWS


148 | P a g e

Description

HUDA allots the residential property to EWS by floating a scheme and holding a draw of allotment.

Applicants pay 10% of tentative cost of the plot as earnest money at the time of submission of

application.

Business Logic

The following process shall be followed by the system after allotment of the residential property to

EWS.



The remaining 90% of the cost shall be paid in lump sum within 60 days of the allotment without











allottee.


completion certificate, and transfer application and so on.




8.19.4 PLOTS TO GOVERNMENT DEPARTMENTS UNDER RENTAL HOUSING SCHEME

Description

HUDA allots plots to government departments for their rental housing. Plots are offered on first cum

first basis. The applicant department pay 10% of tentative cost of the plot to accept the offer.

Business Logic

The following process shall be followed by the system after allotment of the plot to the government

department under Rental Housing Scheme.


149 | P a g e


of letter of intent.

3. If this 15% of the amount shall not be deposited, a further grace of 90 days shall be given.

Failing which surcharge shall be levied. Further if surcharge shall not be paid within maximum

of 30 days then provision shall be made to cancel the allotment and change the plot status to

vacant.


If department surrenders the plot before date of issue of allotment letter, then 100% amount shall

be refunded back to the department and the plot status shall be changed to vacant.









The department shall be given a fixed time period from the date of offer of possession as

Construction period. Over the completion of construction period if the plot holder do not

completes the construction then extension fee shall be charged.

If the department completes the construction within the specified years from the date of

possession, fixed percent rebate on the price of the land shall be given and adjusted towards the

future instalments.


department.

Facility shall be provided to process the department’s request for mortgage certificate, partial/full


Facility shall be provided to print the show cause notices for the department whose instalments are

not regular or who are misusing their property.



150 | P a g e

8.19.5 PROPERTY UNDER GROUP HOUSING SCHEME

Description

HUDA always allots the residential property by floating a scheme for Group Housing Society GHS and

holding a draw of allotment. Applicant society pays 10% of tentative cost of the plot as earnest money

at the time of submission of application. Applicant society also submits the FORM L containing list of

members of the society along with the application.

Business Logic

The following process shall be followed by the system after allotment of the property to GHS.

Provision shall be provided to print the refund orders for the unsuccessful applicant societies.

For the successful applicants letter of Intent shall be issued.


of letter of intent.

4. If this 15% of the amount shall not be deposited, a further grace of 60 days shall be given.

Failing which surcharge shall be levied. Further if surcharge shall not be paid within maximum

of 30 days then provision shall be made to cancel the allotment and change the plot status to

vacant.


If GHS surrenders the plot before date of issue of allotment letter, then 100% amount shall be

refunded back to the GHS and the plot status shall be changed to vacant.








due towards the society.

The society shall be given a fixed time period from the date of offer of possession as Construction



If the society completes the construction within the specified years from the date of possession,

fixed percent rebate on the price of the land shall be given and adjusted towards the future

instalments.


society.


151 | P a g e

Facility shall be provided to process the society’s request for mortgage certificate, partial/full


Facility shall be provided to print the show cause notices for the society whose instalments are not



8.19.6 INDUSTRIAL PROPERTIES

Description

HUDA invites application forms for various industrial plots. The committee constituted at the Zonal

level under the chairmanship of respective administrators rejects or accepts the application. Applicant

pays 10% of tentative cost of the plot as earnest money at the time of submission of application along

with the other necessary documents like project report, partnership deed, and land utilization plan and

so on.

Business Logic

The following process shall be followed by the system after allotment of the industrial property.



The next 15% (to make 25% of the land cost) of the tentative cost of the plot shall be paid within 30

days from the date of issuance of allotment letter.

5. If this 15 %( to make 25% of the land cost) of the amount shall not be deposited, the delay can

be condoned by the appropriate authority on levy of surcharge. Besides the surcharge the

alottee shall have to pay penal interest on the 15% amount for the delayed period, to be

reckoned from the date of allotment. Further if payment in not done within the specified

period then provision shall be made to cancel the allotment and change the plot status to

vacant.

If applicant surrenders the plot within 30 days of issue of allotment letter, then 100% amount shall

be refunded back to the applicant and the plot status shall be changed to vacant.


remaining 75% of the cost shall be either paid in lump sum within 60 days of the allotment without




After HUDA offers the Possession of the site to the plot holders, the simple interest called


due towards the applicant.


152 | P a g e

The plot holder shall be given a fixed time period from the date of offer of possession as

Construction period. Over the completion of construction period if the plot holder do not

completes the construction then resumption proceeding start. Also if the commercial production

do not start within the specified period from the date of offer of possession then extension fee

shall be charged.

If production does not start within one year of the completion of the construction resumption

proceedings starts.


applicant.

Facility shall be provided to process the applicant’s request for mortgage certificate, partial/full


Facility shall be provided to print the show cause notices for the applicant whose instalments are

not regular or who are misusing their property.


8.19.7 INSTITUTIONAL PROPERTIES

Description

The institutional sites can be classified into the following categories:

Religious/Dharamshala/Charitable/Social/Philanthropic/Trust/Societies/Old Age Homes – For

allotment of this category of institutional property, HUDA invites applications, which are accepted

or rejected by the authorized committee. No transfer of land is allowed.

Nursing Homes/Clinics/Schools – The institutional site of this category is allotted through auction.

No transfer of land is allowed.

Hospital - For allotment of this category of institutional property, HUDA invites applications, which

are accepted or rejected by the authorized committee. No transfer of land is allowed.

Petrol Pump - For allotment of this category of institutional property, draw of allotment is done.

8.20 Generate Refund Order

Description

This function is intended to print the Refund Order to unsuccessful applicants in the draw, on pre-

printed stationary provided by the bank. This shall also be used to generate refund order for the

withdrawn or rejected applications.

Business Logic

Refund orders are issued to the unsuccessful applicants in the draw. Refund orders are printed on the

sequenced running pre-printed stationary provided by the bank. The cheque numbers are associated

with the refund order number dynamically at the print time and shall be stored in the system. In case


153 | P a g e

the printing stops in between then the printing of the refund order shall start from the next available

cheque number.

Validations

Scheme number should be valid

Cheque number is a valid cheque as captured in the cheque control register of FAS module with

status as ‘Unused’

After the confirmation by the user that the refund order is printed successfully, cheque control

register would be updated with the date, amount, in favour of and status details. Also, application

status will be set to ‘U’ (Unsuccessful) and the Refund Order number will be populated in the

‘Application Registration’ function.

8.21 Maintain Applications Received

Description

This function is intended to capture the application received for issue of various certificates.

Business Logic

Facility shall be provided to enter the applications received for issue of various certificates like Building

Plan Sanction, DPC Certification, POC Certification, OC Certification, Demarcation Plan, Sanction of

Building, No Dues Certificate, Non-Encumbrance Certificate, Mortgage Permission, Conveyance Deed,

Transfer Permission Letter, Re-Allotment Letter (Final Transfer) and so on.

On entry of the Urban Estate Code, Sector Id, property sub category and plot number, details of the

plot and plot owner shall be displayed on the screen. Details like Property status, present owner’s

name and address, GPA name and address (in case GPA is valid), father/husband name, checklist of the

documents that needs to be attached along with the application form and days required to process the

request shall be displayed.

Status of the property shall also be displayed whether the property is under court case, mortgage,

surrendered, misused, resumed, cancelled or not. Applicant’s remarks and application submission date

(default will be system date) shall be entered in the system. System will calculate the outstanding dues;

process fee as per the rates defined in the fee master; and planned issue date of the certificate as per

the details captured in the process master. On accepting the application, system will generate running

application number to track the application.

Facility shall also be provided to query the property details and/or payments/dues details of the

property. Application Received Receipt will be generated for every accepted application. It will give the

application number, application received date and the date on which the certificate will be issued to

the applicant.

Validations

Plot number should be valid


154 | P a g e

Outstanding dues and process fee will be calculated by the system.

On issue of the certificate, certificate issue date will be updated in the property details screen.

8.22 Transfer of Property

Description

This function is intended to transfer the property from one owner to another owner. For property

transfer, HUDA charges administrative charges if the conveyance deed is done and all dues are clear,

otherwise transfer fee is also charged by HUDA.

Business Logic

Transfer is allowed only for Residential plots, Commercial plots and Nursing Homes (Auction). Transfer

request of the seller shall be captured by the system using ‘Maintain Applications Received’ function

and can be queried using application number. Details like Urban Estate Code, Sector Id, property

category, property sub category, plot number, details of the plot and plot owner will be displayed on

the screen. Details like present owner’s name and address, GPA name and address (in case GPA is

valid), father/husband name, joint holders name and address, reservation category, reservation sub-

category, area of the plot at allotment, area of the plot at possession, any incidental space allotted,

total area of the property, Conveyance Deed status and payment/dues status shall be displayed.

Transfer details like mode of transfer, type of transfer, and relationship with transferee, transferee’s

name and address, father/husband name, joint holders name and address shall be captured by the

system. System shall calculate the transfer fee and administrative charges as per the rates defined in

the fee master. After This application shall be verified by the junior engineer, superintendent and then

the Estate Officer. An option shall be provided in the system to print the Transfer Permission Letter

after Estate officer does the verification of the application.

System generated memo number of Transfer Permission Letter and date of issue of the Transfer

Permission Letter shall be saved in the system. After submission of the documents along with Transfer

Permission Letter by the applicant, an option shall be provided to print the re-allotment letter. Date on

which the applicant submits documents along with Transfer Permission Letter and date on which

Attendance was marked shall be saved in the system. System generated memo number of Re-allotment

Letter and date of issue of the Re-allotment Letter shall be saved in the system. Other processing

official details like designation of the processing official, processing official’s name, processing date,

processing status, processing official’s comments and processing official’s remarks shall also be

captured.

At each stage of processing, system shall provide the facility to print the application containing the

processing official’s comments and remarks along with other details, which the processing official shall

attach in the file before sending to next processing authority.

Transfer of residential/ commercial plots wherein either full payment has already been made or laid

down schedule of payment of instalments is over or Construction is complete (i.e. OC issued),


155 | P a g e

whichever is earlier, shall be allowed only through execution of conveyance deed/ sale deed. However,

in other case, wherein full payment of the plot has not been made so far and the schedule of payment

of instalments is not yet over, a maximum of four transfers are allowed before final payment.

In order to determine the rate of transfer fee, various Urban Estates have been grouped into the

following zones:

1) High Potential Zones (HPZ) - Gurgaon, Faridabad, Panchkula

2) Medium Potential Zone (MPZ) – Karnal, Panipat, Bahadurgarh

3) Low Potential Zone (LPZ) – Rest of the Urban Estates

Transfer Fee rates applicable in various Zones for Residential plots are:

Table 3: Transfer Fee

No. of Transfer Transfer Fee (Rs. per sq. meter)

HPZ MPZ LPZ

Ist Transfer 75 60 40

IInd Transfer 75 60 40

IIIrd Transfer 100 75 50

IVth Transfer 100 75 50

For commercial sites, the rates of transfer fee are three times of the corresponding rates as applicable

to the residential plots.

In cases, where the deed of conveyance of the plot has been executed, transfer shall be permitted on

payment of Rs. 5000/- as administrative charges and on production of a certified copy of sale deed. No

limit of transfer in such cases has been prescribed.

The family transfer includes father, mother, sons, daughters, sisters, brothers, husband, wife, daughter-

in-law and son-in-law. Transfer of plot shall be allowed on payment of Rs. 5000/- as administrative

charges.

No transfer fee shall be charged in case:

4) Wherein the transfer/sale is being affected through execution of conveyance deed/sale deed.

5) Transfer within the family

In both the cases above, only administrative charges shall be charged.

Validations

Application number should be valid

Transfer fee, if applicable, will be automatically populated by the system on the basis of the

following rules:


156 | P a g e

a) Transfer fee rates as per the number of transfer and zone of the plot will be picked up from the

fee master.

b) No transfer fee shall be charged if Mode of Transfer is ‘Family Transfer’

c) No transfer fee shall be charged if Mode of Transfer is ‘Will or In-testate Death’

d) No transfer fee shall be charged if transfer is being effected through execution of Conveyance

Deed or Sale Deed.

e) In case where Mode of Transfer will be ‘Court Decree’ then

i. For constructed plot i.e. OC issued and for all Modes of Transfer excluding ‘Will or In-

testate Death’, transfer will be effected through Conveyance Deed. No transfer fee shall be

charged only administrative charges of Rs.5000/- is charged as in case of transfer through

Conveyance Deed will be charged.

ii. In case Conveyance Deed has been executed or full payment made or schedule of

payments is over and for all Modes of Transfer excluding ‘Court Decree’, ‘Will or In-testate

Death’, transfer is executed through Sale Deed/ Gift Deed. No transfer fee shall be charged

only administrative charges of Rs.5000/- is charged as in case of transfer through Sale Deed

will be charged.

Administrative charges shall be automatically populated by the system on the basis of the following

rules:

a) If Mode of Transfer is ‘Family Transfer’ - Rs. 5000/-.

b) In case Conveyance Deed has been executed (for all Modes of Transfer excluding ‘Family

Transfer’, ‘Sale Deed’ ,‘Will or In-testate Death’(out of family)) – Rs.5000/-

c) If Mode of Transfer is ‘Sale Deed transfer’ – Rs. 5000/-

d) If Mode of Transfer is ‘Court Decree’ – Rs. 5000/-

e) If Mode of Transfer is ‘Death’ (within family) – Rs. 1000/-

Memo Number of Transfer Permission Letter and Memo Number of Re-allotment Letter shall be

generated by the system as and when these will be printed.

8.23 Mortgage Permission Application Approval

Description

This function is intended to facilitate the processing of Mortgage Permission request.

Business Logic

Mortgage permission request of the allottee shall be entered in the application using ‘Maintain

Applications Received’ function. And can be queried basis on application number. Details like Urban

Estate Code, Sector Id, property category, property sub category, plot number, plot owner will be

displayed on the screen. Details like present owner’s name and address, GPA name and address (in

case GPA is valid), father/husband name shall be displayed.


157 | P a g e

Mortgage request details like name of the bank/ financial institute where Mortgage is to be applied

shall be accepted by the system. System shall calculate the fee and administrative charges as per the

rates defined in the fee master. This application has to be verified by the Estate Officer. An option shall

be provided in the system to print the Mortgage Permission Letter after Estate Officer does the

verification of the application. System generated memo number of Mortgage Permission Letter and

date of issue of the Mortgage Permission Letter shall be saved in the system. Other details like

designation of the processing official of the application, processing official’s name, processing date,

processing status, processing official’s comments and processing official’s remarks shall also be

captured.


processing official’s comments and remarks along with other details, which the processing official shall

attach in the file before sending to next processing authority.

Validations


Fee and Administrative charges, if applicable, shall be automatically populated by the system.

Memo Number of Mortgage Permission Letter shall be generated by the system as and when it will

be printed.

8.24 Generic Application Approval

Description

This function is intended to facilitate the processing of the following kind of applications

Building Plan Sanction

DPC

No Dues Certificate

Non-encumbrance Certificate

POC

OC

Business Logic

Application shall be queried from the system basis on application number. Details like Urban Estate

Code, Sector Id, property category, property sub category, plot number, plot owner shall be displayed

on the screen.

Details like present owner’s name and address, GPA name and address (in case GPA is valid),

father/husband name shall be displayed. System shall calculate the fee and administrative charges as

per the rates defined in the fee master. This application has to be verified by the concerned Officer. An

option shall also be provided in the system to print the Approval Letter after the verification of the

application is done. System generated memo number of Approval Letter and date of issue of the


158 | P a g e

Approval Letter will be saved in the system. Other details like designation of the processing official of

the application, processing official’s name, processing date, processing status, processing official’s

comments and processing official’s remarks shall also be captured.


processing official’s comments and remarks along with other details.

Validations


Fee and Administrative charges, if applicable, shall be automatically populated by the system.

Memo Number of Approval Letter shall be generated by the system at the time of printing.

8.25 Surrender of Property

Description

This function is intended to allow the user to surrender of property by the applicant.

Business Logic

Allocated property can be surrendered at any time. For Residential/ Institutional/Industrial properties

1. If property is surrendered before 30 days of the allotment then full earnest money is refunded.

2. If property is surrendered after 30 days of the allotment then 10% of the consideration money

(that is cost of land (including enhancements) + penalty (if any) + interest (if any)) will be

forfeited and the remaining amount deposited by the applicant is refunded.

For Commercial properties, if property is surrendered any time after the allotment then 10% of the

consideration money (that is cost of land + penalty (if any) + interest (if any)) will be forfeited and the

remaining amount deposited by the applicant is refunded.

Facility shall be provided to query the property details of the property that the allottee wants to

surrender. Details like total payment received from allottee, refund amount due to be returned to the

applicant and total amount forfeited as a result of the surrender of the property by the applicant shall

be calculated by the system and displayed. User has a choice to confirm the surrender. On confirmation

of the surrender, current owner details of the property shall be populated in the previous owner details

and current owner details shall be made blank. The status shall also be set to ‘S’ (Surrender) and

property will come under the un-allotted category.

Validations

Plot number should valid

Total payment received from allottee, refund amount due to be returned to the applicant and total

amount forfeited as a result of the surrender of the property by the applicant shall be calculated by

the system.

Change of ownership shall be set to ‘S’ (Surrender)


159 | P a g e

Property Status shall be updated to ‘Un-allotted’

8.26 Restoration of Property

Description

This function is intended to allow the user to restore the resumed property.

Business Logic

Facility will be provided to query the property details of the property that the needs to be restored.

Details like applicant name, father/husband name, permanent address, and correspondence address

date and memo number of the resumption notice issued to the plot owner shall be displayed. Date of

restoration of the property, memo number of restoration letter that shall be sent to the applicant and

remarks regarding the restoration order shall also be captured. User shall be given the choice to

confirm the restoration. On confirmation of the restoration, current owner details of the property shall

be populated from the latest previous owner details. The property will then come under the allotted

category.

Validations

Plot number should be valid

Current owner details of the property shall be populated from the latest previous owner details

Property Status shall be updated to ‘Allotted’

8.27 Waiving of Charges

Description

This function is intended to facilitate the processing of Waiving of charges request.

Business Logic

Waiving of charges request of the allottee shall be entered in the application using ‘Maintain

Applications Received’ function. Waiving of charges shall be queried from the system using application

number. Details like Urban Estate Code, Sector Id, property category, property sub category, plot

number, plot owner will be displayed on the screen. Details like present owner’s name and address,

GPA name and address (in case GPA is valid), father/husband name shall be displayed.

Charges details like fee type, fee amount, and fee amount after waiving charges shall be accepted by

the system. Application for waiving of charges shall be processed by different processing officials.

Option shall be provided in the system to print the Letter after final processing official completes the

application process. System generated memo number of letter and date of issue of the letter shall be

saved. Other details like designation of the processing official of the application, processing official

name, processing date, processing status, processing official comments and processing official remarks

shall also be captured. After each approval by the processing officers, in the hierarchy, system shall

provide a facility to print the application along with the notes and comments, which can be attached in

the file.


160 | P a g e

Validations


Fee type and fee amount shall be automatically populated by the system.

Memo Number of letter will be generated by the system as and when it will be printed.

8.28 Allotment of Alternate Plot

Description

This function is intended to facilitate the allocation of alternate plot to the allottee in case the allotted

property cannot be given to the allottee.

Business Logic

There can be the case where the allotted plot cannot be given to the allottee because of encroachment

or any other reason. For these cases facility shall be provided to allot the alternate plot to the allottee.

Facility will be provided to query the property details of the property that cannot be allotted to the

allottee. Details like applicant name, father/husband name, permanent address, and correspondence

address, GPA name and address (in case GPA is valid) shall be displayed. Alternate plot sector Id,

alternate plot number, rate at which alternate property is being allotted and reason for issue of

alternate plot shall also be captured. User shall be given the choice to confirm the alternate plot

allocation. On confirmation of the allocation, current owner details of the original property will be

made blank. The original property will then come under the originally un-allotted category. The current

owner details of the alternate property will be populated with the applicant’s details and property

status shall be changed to the allotted category. Whenever the new allotment letter shall be printed,

memo number of alternate allotment letter and date of issue of alternate allotment letter shall also be

populated by the application.

Validations

Original and alternate plot number should be valid

Property Status of original plot shall be updated to ‘Un-allotted’ and of alternate plot shall be

updated to ‘Allotted’

8.29 General Procedures Involved in Plot and Property Management The following section describes the general procedures required in PPM.

8.29.1 SURCHARGE PROCEDURE

For most of the categories of plots, 10% of tentative cost of the plot is paid as earnest money at the

time of submission of application. The next 15% of the tentative cost of the plot is paid within the

specified time period from the date of' issuance of letter of allotment. If this 15% of the amount is not

deposited within the stipulated time, then surcharge is levied. However, the officers at different levels

have the authority to condone the delay. But the delayed period interest shall always be levied the

principal amount. Besides surcharge the allottee shall have to pay the penal interest also for the


161 | P a g e

delayed period.

8.29.2 CANCELLATION PROCEDURE

If any allottee fails to deposit the 15% amount and surcharge fee after the allotment, within the

extended period then provision shall be made to cancel the allotment and change the plot status to

vacant.

8.29.3 POSSESSION PROCEDURE

HUDA offers possession of land to its allottees once the area is developed. The offer of possession of

plot is given after completing all the basic amenities in the sector. The basic amenities in the sector

include the facilities like approach road, street lighting, water supply and sewerage facilities. After

HUDA offers the possession of the site to the plot holders, the simple interest called possession interest

shall be imposed from the date of offer of possession on the remaining amount due towards the plot

holder.

8.29.4 EXTENSION PROCEDURE

According to HUDA policy, the allottee is required to complete the construction of Residential/

Commercial plot within 2 years from the date of offer of possession. Further, provision of extension of

time for construction beyond stipulated period of 2 years has also been made. The extension fee needs

to be paid for extension of property. The rate of extension fee depends on the zone potential and the

year in which the plot falls after the expiry of the normal period of construction.

8.29.5 TRANSFER PROCEDURE

HUDA allows transfer the property from one owner to another owner. If the conveyance deed is done

and all dues are clear then HUDA charges administrative charges for transfer of the property otherwise

transfer fee is also charged by HUDA. Transfer is allowed only in case of Residential/ Commercial/

Nursing Homes (Auction). Transfer of residential/ commercial plots wherein either full payment has

already been made or laid down schedule of payment of installments is over or Construction is

complete (i.e. OC issued), whichever is earlier, shall be allowed only through execution of conveyance

deed/ sale deed. However, in other case, wherein full payment of the plot has not so far been made

and the schedule of payment of installments is not yet over, a maximum of four transfers shall be

allowed before final payment. The rate of transfer fee depends on the zone potential of the urban

estate in which the plot lies.

8.29.6 ENHANCEMENT PROCEDURE

Each sector can have multiple price enhancements for the plots in the given Sector. There can be

multiple price enhancements on the plot cost. As the parts of the sector may be acquired at different

times the price enhancement can come at different times and may be different for different areas of

the sector. The demarcation plan number shall allow the enhancement rate to be associated with the

plot number following the particular area of the sector for which the enhancement is being asked for.

Also the court for the same area can order multiple price enhancements. In this case the Demarcation


162 | P a g e

plan number will be the same. The total enhancement will be the cumulative sum of all the

enhancements ordered. The enhancement rates are different for General and EWS categories. The

General Category rates will be applicable to all Property Sub-Categories except the EWS Sub-

Categories. Details like count of the enhancement being effected; enhanced rate of the land per sq.

meter (separate for General and EWS category), and date on which the enhancement is applicable shall

be captured. The installments for enhanced amount shall be calculated separately.

8.29.7 RESUMPTION PROCEDURE

Facility shall be provided to generate show cause notices for the allottee whose instalments are not


8.29.8 SURRENDER PROCEDURE

The allottee has the option to surrender the plot within 30 days of the allotment. In this case, 100%

amount deposited by the allottee (10% of the cost) is refunded back. The plot comes under un-allotted

category.

8.30 Monitor Court Cases

Description

The legal department of HUDA deals with the cases of plot holders and enhancement challenge cases.

A lot of HUDA property is under litigation. Facility shall be provided to enter the court case details and

monitor the legal cases by keeping case wise track of all the proceedings.

Business Logic

Facility shall be provided to query and enter the court cases of plot holders. A unique system generated

case number shall be given to each court case. Details like court in which case is lodged, case type,

details of the property that is under litigation, case filing date, petitioners in the case, respondents in

the case, brief details of the dispute, name of HUDA advocates, name of complainant advocates shall

be captured. The hearing details of the case like date of hearing, proceedings, position of the case, date

of next hearing shall also be maintained. Facility shall be provided to enter the judgment details like

judgment date, judgment status, judgment passed, compliance date; compliance status shall also be

maintained.

Reports like list of pending court cases, abstract of court cases, court case compliance status and

previous hearing details of the pending court case shall also be printed.

Validations

Litigation property details should be valid

8.31 Monitor Appeals


163 | P a g e

Description

The plot holders whose property is resumed can file an appeal with Zonal administrator or the Chief

Administrator. Facility shall be provided to enter the appeal/ revision details and monitor the appeal/

revisions by keeping appeal wise track of all the proceedings.

Business Logic

Facility shall be provided to query and enter the appeal/ revision details of plot holders. A unique

system generated case number shall be given to each appeal and revision. In case of revision, previous

appeal number shall also be captured. Details like court in which case is lodged, case type, details of the

property for which appeal is raised, case filing date shall be captured. The hearing details of the case

like date of hearing, proceedings, position of the case, date of next hearing shall also be maintained.

Facility shall be provided to enter the judgment details like judgment date, judgment status, judgment

passed, compliance date; compliance status shall also be maintained.

Reports like list of pending appeal/ revisions, abstract of appeal/ revisions and appeal/ revisions

compliance status shall also be printed.

Validations

Litigation property details should be valid

8.32 Public Website Data

Description

For public access, the application will be hosted on the existing website of HUDA. Develop query pages

for

Display of payment details

Display of due details of plot holders on the public website.

Display of current status for the various applications received from allottees.

Display of static information regarding various processes at the Estate Office.

Notification of information to allottees through SMS/email gateways

Business Logic

Facility shall be provided to query the payment/ due details of the plot holders. The screen layout shall

be same as that displayed for the property details screen.

Validations

No

8.33 External Interface Specifications


164 | P a g e

This section describes the external interfaces with the PPM (Plot and Property Management).

8.33.1 SYSTEM INTERFACES

Bank shall provide application details of applicants received against scheme floated by HUDA in text

files and shall be uploaded to the system. For successful uploading text file should adhere to predefined

supplied format.


The text file shall be received in electronic format from the banks. These text files shall be uploaded to

the system. These text files will contain details of application received from the applicants against a

particular scheme floated by HUDA.


Title: Application Upload

Description: The flat file containing application details of the applicants against a

particular scheme floated by HUDA

Business Purpose: The banks will act as an agent and will receive the applications. This

will then be converted into electronic format by the banks. The text

file produced by the banks will then be uploaded through the

interface into the system.

8.33.4 FAS INTERFACE

The Banks shall also provide the payment details in electronic format, which shall be uploaded into the

system through the FAS component. The PPM component shall interact with the FAS component to

obtain the payments made or received against each allottee. Payments made can be against various

heads like installments, compounding fees, extension fees. These details shall be supplied to the PPM

through FAS.


Bank shall provide text files in electronic format and same shall be uploaded into the system. The text

files shall contain details of application received from the applicants against a particular scheme floated

by HUDA.


Title: Payment Details

Description: The FAS module using the text file received from the banks will

capture the payments made and received against each allottee. This


165 | P a g e

data will then be shared with the PPM module through this interface

Business Purpose: The FAS module will act as an agent to capture the payment details

which the banks send in electronic format.

8.34 User Access Control and Security

The users of the HUDA system are categorised into the following groups

8.34.1 OPERATING SYSTEM LEVEL

Administrator shall be responsible for system administration and housekeeping of the HUDA servers

8.34.2 APPLICATION USER

Users will be assigned a unique user id and password. User ID and password shall be used to

logon to the system. In case of an invalid combination of these two codes, the system shall

display an error message and prevent further processing. There is a disclaimer stating controls

and responsibility of users and it is to be accepted to login. Without accepting the terms and

conditions in disclaimer user cannot login into the system. The users shall be divided into 2

groups

a. Individual Users – Users will have access to the application software only. Users will have

access to specific screens and functions within them basis on the role. Roles shall be

assigned to the user depending on his area of operation. User rights shall also be

+controlled by the location of the user. Users shall only view or modify data pertaining to

their location.

b. Administrative Users – Users shall have access rights for user creation and assignment of

access rights to the application users. Administrative users shall also have rights to create

program heads for the menu and associate forms to these heads. Administrative users

would also be able to reset the password of the individual users.

8.35 Reports

Description

The various reports are:-

1. Sector Reports

2. Allottee Account Statement

3. Scheme Wise Plot Status

4. Scheme Appl. Reports

5. Cards for Lottery

6. Bidders List


166 | P a g e

7. Plot Status Reports

8. Deposit Dues Reports

9. Defaulters List Report

10. Possession List

11. JE Appointment Details

12. Print Receipt

13. Service Tax Report

14. Generate Allotment Letter

15. Refund Order

16. Print Letters

17. Print Certificate

18. Print Reminders

Business Logic

Facility to be provided to view all reports and certificates in HUDA prescribed formats


167 | P a g e

9. ANNEXURE C - FUNCTIONAL REQUIREMENTS WEB PORTAL MODULE This briefly describes the content on HUDA Public Website www.huda.org.in

9.1 Static Content List:

Static Contents on HUDA Web Portal

S.No Subject Remarks

1 Message from CA Web Content

2 About us

a HUDA at a Glance Web Content

b Vision and Mission Web Content

c Chairman's Message Web Content

3 Wings

a Architecture Wing Web Content

b Enforcement Wing Web Content

c Engineering Wing Web Content

d Establishment Wing Web Content

e Estate Office Web Content

f Finance Wing Web Content

g Information Technology Wing Web Content

h Legal Cell Web Content

i Policy Wing Web Content

j Town Planning Wing Web Content

k Zonal Administration Web Content

l Urban Branch Web Content

m Monitoring Cell Web Content


168 | P a g e

Static Contents on HUDA Web Portal

S.No Subject Remarks

4 Services

a How do I lodge Complaints? Web Content

b Community Facilities Web Content

5 Site Map Web Content

6 Terms of Use Web Content

7 Privacy Policy Web Content

8 Help Web Content

9 FAQs Web Content

9.2 Dynamic Content List

S.No Subject Administration Workflow (Y/N)

1 About US

a Major initiatives (Instead

of Achievements)

Content to be managed

by Administrator Group of

HUDA

N

b Events and Gallery Content to be managed


HUDA

N

c New HUDA Schemes Y

2 Repository

a Articles Content to be managed


HUDA

N

b Forms (Downloadable) Upload/Removal of pdf

documents to be

managed by HUDA

N


169 | P a g e


Administrator

c MapQuest To be managed by

Administrator Group of

HUDA

Y

d Notifications To be managed by


HUDA

N

e Challans

3 Policy

a Commercial Plot Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

b Industrial Plot Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

c IT Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

d Residential Plot Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

e Institutional Plot Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

f Social and Charitable

Plot Policy

Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N


170 | P a g e


g Accounts Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

H Oustees Policy Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

4 Notices

A Public Notice Content to be managed


HUDA

N

B Tender Notice Content to be managed


HUDA

N

5 Services

A Allotee Account

Information

Web Content to be pulled

from PPM Application

Y

B Discussion Board / Blog Standard Functionality N

C Draw Results To be pulled from PPM

Application

Y

D How do I Lodge

Complaints?


documents to be

managed by HUDA

Administrator

N

E Instruction Manual Upload/Removal of pdf

documents to be

managed by HUDA

Administrator

N

F Miscellaneous Services N


171 | P a g e


G News and

Announcements



HUDA

N

H Application Submission

for Allottees

Y

I Apply to online Schemes,

download scheme

brochure, application

forms and challans.

Citizens Y

J Poll / Surveys Standard Functionality N

K Registration Numbers Y

L Status Enquiries Y

M Upcoming events /

Calendar

Standard Functionality N

N Online View of Plot Rates Y

6 Contact Us

A Directory Content to be managed


HUDA

N

B Feedback Y

C Send Thoughts Standard functionality N

7 Online Payments Y

8 Refunds Y

9 External integrations External systems

connected to portal

Y

A Notifications to allottees

via SMS , Email

SMS/Emails to Allotees Y


172 | P a g e


Notification of

request completion

status/ payment status

to allotees

vial SMS/email Gateways

B Bank Payment

Integrators

Payment integrators of

banks to make payments

from various other banks

Y

C Plot Property

Management system

Applications received,

payments received,

display allottee plot

details., Due details of

plot holders

Y

10 Information as per RTI

Act 2005


documents to be

managed by HUDA

Administrator

N

11 Lodge Complaints Y

12 Complaints Status Y

13 Advertisements To be managed by


HUDA

N

14 Search Here Standard Functionality N

15 Image / Slideshow on

Home Page

To be managed by


HUDA

N

16 News Flash on top of all

Pages



HUDA

N

17 Log In Window

A Select User type(Combo

Box)

Values are static (Allotee,

Employee, User group)

Y


173 | P a g e


B Log In Id , Password

(Text Box)

Employees and User

groups to be validated

from HUDA's Active

Directory, Allotees to be

validated from allotees

user name and password

database of HUDA

Y

C New User For Citizens Only N

D Forgot Password For Citizens Only Y

18 Download Tools To be managed by


HUDA

N


174 | P a g e

10. ANNEXURE D - FUNCTIONAL REQUIREMENTS OF CCTS MODULE The HUDA court case tracking system is an application that helps the HUDA employees, the

allottees and the advocates to track the cases that they are a party to.

This application has the following functionalities.

1) Facilitate data entry to add/edit the details of the court cases. This is done by employees of

HUDA.

2) Allow access of reports to the users of the websites – external as well as internal. The external

users have limited access to the site and can view a limited set of reports. Internal users can

get access to reports in 21 pre-defined formats apart from having the options to choose fields

for a custom report.

3) All the users of the website have access to the calendar using which the user can view the

number of cases listed for hearing on any given day, along with the location details of the

hearing.

The users of the application can be classified as:

1) HUDA employees – Employees are essentially from the Legal Cell of HUDA who receive inputs

regarding the court cases and enter these details into the system.

2) Administrator – Administrator can add users to the application, manage the roles of the users

and the components that they can access. Additionally they have the privilege to add

different kinds of details into the application, which are used to define the court cases in

terms of different parameters and categories.

3) Citizens – Citizens can use the application to view the court cases listed for hearing on a

specific date.

4) Advocates – Any advocate can access the website and find out the number of cases of HUDA

pending with him/her.

All the reports in the application can be exported as excel sheets.

The functional requirements of the existing application are tracked below

10.1 Application User Master

Description

This section is used to manage users for this application. It includes adding new users, modifying

details of existing users and deleting existing users.


175 | P a g e

10.2 Case Type Master

Description

This page is used to manage the different types of cases that HUDA is handling. Every case has a case

type code, followed by a description.


176 | P a g e

10.3 Urban Estate Master

Description

The urban estate master is used to keep track of the urban estates in Haryana. Every urban estate

has a specific code


177 | P a g e

10.4 Sector Master

Description

This is used to keep track of the different sectors in each of the urban estates

10.5 Property Category Master

Description

This section lists the various property categories that HUDA offers. Each of these property

categories have a category code


178 | P a g e

10.6 Court Case Nature Master

This section maintains a list of the nature of court cases that HUDA is involved in. Currently, there are

only four types of cases.

10.7 Courts Master

Description

This section maintains a list of all the courts in which there are cases are being fought or had

been for/against HUDA. Every court name has a corresponding code which is used further in the

system.


179 | P a g e

10.8 Courts Location Master

Description

This section maintains a list of all the courts in which there are cases are being fought or had

been for/against HUDA and the locations of each of these codes. This is different from the courts

master, as a court with the same name may be present in different locations.


180 | P a g e

10.9 HUDA Offices Master

Description

This section is to maintain the list of different departments of HUDA and the corresponding office

codes

10.10 Advocate Master

Description

This section maintains the details of all the advocates who are fighting cases on behalf of HUDA. It

contains the name of the advocate, their contact details including email, phone number and address


181 | P a g e

10.11 Court Case Details

Description

This section is the most important functionality of the CCTS application. All the relevant details

corresponding to the court cases are to be entered in this page. This page also provides the user with

the facility to search for information related to court cases.

10.12 Reporting Following reports are generated through CCTS:-

1. Details of Cases Listed on a Date

2. Details of Cases Decided on a Date

3. No. of Cases Entrusted to an Advocate between Dates

4. No. of Cases Pending with an Advocate

5. Summary Report

6. List of cases decided against HUDA

7. List of Cases Decided in Favor of HUDA

8. List of Cases Decided against HUDA/Appeal Filed

9. List Of Cases where Advocate not Engaged

10. List of Cases where written statement not filed.

11. List of Cases Entrusted to a Particular Advocate

12. List of Cases Complied/Not Complied

13. List of Cases where Fee Pending/Not Entered

14. List of Cases where Certified Copy received from Counsel/Directly From court

15. List of Cases for Case Nature Pending/Decided

16. List of cases on basis of Case date and other parameters

17. List of cases listed on the next 7 days where written statement not filed

18. List of LAC cases listed on a date

19. List of New Case Entered On Months Years, Detail Reports Administrator Wise

20. Daily Progress of HUDA User Zone Wise

21. Custom Reports - The application also provides the feature for the user to generate a report

with custom fields. The custom fields are displayed in the screenshot below. Additionally, the

user can select criteria like case nature, urban estate, court name, court location based on which

the report will be generated with the desired fields

Request for Proposal - HSVP

Documents

Transcript of Request for Proposal - HSVP