Tender Document

ADGP TECHNICAL SERVICES, Punjab, Chandigarh

e-Tender/IT Services/2020-21/

Punjab Police Headquarters, Sector 9A, Chandigarh-160009

Notice Inviting e-Tender

e-Tender Notice No. 2020-21/xxxx

ADGP Technical Services, Punjab, invites online e-Tender for the

“Selection of Implementation Agency for the Development, Implementation

and Maintenance of CCTNS & HRMS mobile and Web app with AI powered

search and quality validation technology”.

For participating in the above e-tendering process, the bidders

should have to get themselves registered with https://eproc.punjab.gov.in and get

a user ID and Password. A class-3 Digital Signature is mandatory to participate

in the e-tendering process. For any clarification/difficulty regarding e-tendering

process, please contact us on Phone No. 0172-2970284/2970263

INDEX

Part-I – General and Commercial terms and conditions

S. No. Contents Page(s)

1. General Information 1-2

2. Contact Details 2

3. Invitation to Bidders 3

4. Instruction to Bidders 3-10

5. Rejection Criteria 10-12

6. Malpractices/ undue influence Rejection of Bid 12

7. Right to cancel or annul Bid 12

8. Definitions of important terms 13-14

9. Warranty 14

10. Annual Maintenance Contract 14-15

11. Tolerance clause 15

12. Penalties 15

13. Exit Management Plan 15-16

14. Application Security Audit 16-17

15. Intellectual Property Rights 17-18

16. Waiver 18

17. Assignability 18-19

18. Severability 19

19. Governing law 19

20. Termination for default 19

21. Resolution of Disputes 19-20

22. Force Majeure 20

Part-II – Bid Process

23. Bid Process 21-25

24. Evaluation of Bids 25-26

25. Technical Evaluation 26-28

26. Opening of Financial Bids 28-29

27. Integrated financial-cum-technical evaluation 29-30

28. Notification of Award 30

29. Performance Bank Guarantee (PBG) 30

30. Signing of Contract 30

Part-III – Scope of Work

31. Scope of Work 31-58

32. Training 58

Part-IV – Payments and Penalties

33. Payment Schedule 59-60

34. Payments on account of Annual Maintenance Contract

60

35. Service Level Agreement 60-61

36. Annexure – 1 (Bidder Particulars) 62

37. Annexure – 2 (Bid Form) 63

38. Annexure – 3 (Guarantee) 64

1

Part-I – General and Commercial terms and conditions.

1. General Information

Name of organization

floating e-tender (client)

Punjab Police

Title of the e-Tender Selection of Agency for Development, Implementation and

Maintenance of CCTNS/HRMS mobile and web app with

AI powered search and quality validation.

Contact Person Dr. Surbhi Marwaha, PPS,

DSP/ IT Technical Services, Punjab, Chandigarh

Contact details Contact no. 0172-2748100-06 Extn 2709,

Mob No.: +91 9464433841,

Email Id:- tender.ts@punjabpolice.gov.in

Tender Fee INR 2,000/-

Earnest Money Deposit INR 1,00,000/-

Performance Bank Guar-

antee (PBG)

5% of the Contract Value (including total annual mainte-

nance charges for three years)

Bid validity 12 (Twelve) calendar months from the date of closing of

the tender

1.2 Timeline for tender: -

S. No. Activity Date Remarks

1 Uploading and sale of

Tender Document

18.11.2020 Uploading and sale on E-Procurement

website of Punjab Government

2 Last date and Time for

Tender closing

04:00 PM of

09.12.2020

Closing of Tender

3 Pre-Qualification

10.12.2020

&

11.12.2020

For Pre-Qualification evaluation of Bids

received

4 Technical Evaluation

(Tentative Date)

14.12.2020

&

15.12.2020

Technical evaluation of Bids

2

5 Financial Bid Opening

(Tentative Date)

18.12.2020 Opening of Financial Bid

6 Letter of Intent

(Tentative Date)

21.12.2020 Issuing Letter of Intent

7 PBG and Signing of

Contract

(Tentative Date)

22.12.2020

To

31.12.2020

Submission of PBG and signing of

Contract by the successful bidder

2. Contact Details

IGP Technical Services, Nodal Officer

Punjab Police Headquarters,

Sector 9-A, Chandigarh-160009.

Ms Surbhi Marwaha, PPS, Contact Person

DSP/ IT Technical Services, Punjab

Punjab Police Headquarters, Sector- 9A, Chandigarh

Contact No. 0172-2748100-06 Extn 2709, Mob:- +91 9464433841

Email Id:- tender.ts@punjabpolice.gov.in

Note: For any queries, please contact on the above mentioned numbers

on any working day between 9:30 A.M to 4:30 P.M.

3

3. Invitation to Bidders

This Tender is addressed to interested bidders for the Selection of

Agency for Development, Implementation and Maintenance of

CCTNS/HRMS mobile and web app with AI powered search and qual-

ity validation.

4. Instructions to Bidders

4.1 General

4.1.1 This e-tender is floated through the e-tendering process

and only e- bids shall be accepted. The process to be

followed is outlined in detail in Part-II (Bid process).

4.1.2 Bidders can download the Tender document from

https://eproc.punjab.gov.in.

4.1.3 Bidders shall deposit a Tender Fee of Rs. 2,000/- (non-

refundable) payable only through online mode as pro-

vided in the website https://eproc.punjab.gov.in.

4.1.4 Bidder must state categorically whether or not his/ her

offer conforms to all the terms and conditions of the ten-

der. If there is a variation in any of the terms and condi-

tions, the extent of variation and the reasons thereof

shall be clearly mentioned in the bid. Punjab Police

may or may not accept the bid with variations.

4.1.5 Bidder must state categorically whether or not his/ her

offer conforms to the requirements given in the scope of

work/ technical standards. Bidder must clearly specify

the deviation in the bid, if any, from the scope of work/

technical standards. Any deviations limiting the scope

of work or lowering the technical standards shall not be

accepted. Enhanced scope of work/ enhanced technical

standards will be given due consideration.

4

4.1.6 It will be incumbent upon each Bidder to fully acquaint

himself/ herself with the local conditions and factors at

all respective locations, sites and offices which would

have any effect on the performance of the contract and/

or the cost. It is clarified that the application will be de-

ployed at State Data Center in S.A.S. Nagar (Mohali) or

any other designated place.

4.1.7 The Bidder is expected to obtain for himself/ herself, on

his own responsibility, all information that may be nec-

essary for preparing the bid and entering into a contract.

Obtaining any such information shall be at Bidder's own

cost.

4.1.8 Failure to obtain the information necessary for prepar-

ing the bid and/ or failure to perform the activities that

may be necessary for the project will in no way relieve

the successful Bidder from performing any work in ac-

cordance with the contract entered into.

4.1.9 It is the responsibility of the Bidder that such factors

have been properly investigated and considered while

submitting the bid response and that no claim whatso-

ever including those for financial adjustment to the con-

tract awarded under the bidding documents will be en-

tertained by Punjab Police and that neither any change

in the time schedule of the contract nor any financial ad-

justments arising thereof shall be permitted by Punjab

Police on account of failure of the Bidder to apprise

themselves of local laws and conditions.

4.1.10 When deemed necessary, during the tendering pro-

cess, Punjab Police may seek clarifications on any as-

pect from any or all of the Bidders. However, that would

not entitle the Bidder to change or cause any change in

the substance of the tender submitted or price quoted.

5

4.2 Consortium of Bidders

4.2.1 Considering the wide variety of skills and resources

needed for the project, a maximum of two Companies or

organizations are allowed to form a Consortium and bid

for this project.

4.2.2 In the case of consortium:

4.2.2.1 The Prime Bidder shall be the single point

of contact for Punjab Police and shall be

primarily responsible for the discharge and

administration of all the obligations for this

project.

4.2.2.2 The other consortium member shall furnish

a Power of Attorney in favour of the Prime

Bidder, authorizing the same to submit and

sign the Tender response

4.2.2.3 The Prime Bidder shall sign the Contract

with Punjab Police on behalf of the consor-

tium in case the bid is successful.

4.2.3 It is to be noted here that Consortium is not a manda-

tory condition. A Bidder meeting all the Pre-Qualification

conditions mentioned in this Tender document may bid

independently for this Tender.

4.3 Original developer of Facial Recognition Software

The Bidder (either prime bidder or its partner in case of Consortium)

must be the original developer of Facial Recognition Software. Any

bid not satisfying this condition shall be summarily rejected.

6

4.4 Cost of Bidding Process

The Bidder shall bear all costs associated with the preparation and

submission of its bid, including cost of presentations etc.

4.5 Schedule of e-Tender

4.5.1 The e-Tender shall be uploaded on https://eproc.pun-

jab.gov.in. For any technical help, please contact on

numbers provided on the website.

4.5.2 The Technical bids will be opened in the office of IGP/

TS cum Chairperson Tender Committee, Room No.

215, Punjab Police Headquarters, Sector-9-A, Chandi-

garh-160009.

4.5.3 Scope of Work/ Technical standards/ specifications are

listed in detail in Part-III of this document.

4.5.4 After evaluation of the Pre-qualification documents and

their verification with hard copies of documents submit-

ted by the bidders, the shortlisted bidders will be inti-

mated through e-mail and invited for a technical presen-

tation.

4.5.5 After evaluation of the technical presentation, financial

bids of only those short-listed Bidders who qualify shall

be opened. The date and time of opening of financial

bids will be conveyed via e-mail to such qualified bid-

ders only.

4.6 Earnest Money

4.6.1 Amount of earnest money is INR 1,00,000/-.

4.6.2 Bidders shall deposit the Earnest Money only through

online mode as provided in the website

https://eproc.punjab.gov.in.

7

4.6.3 Bids submitted without depositing Tender Fee and Ear-

nest Money shall be rejected.

4.6.4 No interest will be payable on the Earnest Money by

Punjab Police.

4.6.5 The Earnest Money may be forfeited:

4.6.5.1 If a Bidder withdraws his bid during the pe-

riod of bid validity; or

4.6.5.2 In the case of the finally selected Bidder:

4.6.5.2.1 If the Bidder fails to sign the

Contract in accordance with

the terms of this tender doc-

ument, or

4.6.5.2.2 If the Bidder fails to furnish

Performance Bank Guaran-

tee in accordance with the

terms of this tender docu-

ment, or

4.6.5.2.3 If at any stage any of the in-

formation/ declaration is

found false.

4.6.6 Earnest Money in respect of the finally selected Bidder

will be discharged upon the Bidder signing the Contract

and furnishing the Performance Bank Guarantee as

specified in this tender document.

4.6.7 E-procurement portal will automatically return the EMD

amount of the unsuccessful bidders.

4.7 Amendment of Tender Document

8

4.7.1 At any time prior to the deadline for submission of Bids,

Punjab Police may, for any reason, whether at its own

initiative or in response to a clarification requested by a

prospective bidder, modify the Tender document by way

of amendment(s). Such amendment(s) shall be up-

loaded on the website, through corrigendum and shall

form an integral part of the Tender document. The rele-

vant clause(s) of the Tender document shall be treated

as amended accordingly.

4.7.2 It shall be the sole responsibility of the prospective bid-

ders to check the website https://eproc.punjab.gov.in

from time to time for any amendment in this Tender doc-

ument. In case of failure on the part of the prospective

bidder(s) to know the amendment(s), if any, Punjab Po-

lice shall not be responsible for any consequences aris-

ing out of it.

4.7.3 In order to allow prospective Bidders a reasonable time

to take the amendment into account in preparing their

Bids, Punjab Police, at its discretion, may extend the

deadline for the submission of Bids. Such extensions

shall also be uploaded on the website https://eproc.pun-

jab.gov.in.

4.8 Language of the bid:

The Bids prepared by the Bidder and all correspondence and docu-

ments relating to the bids exchanged by the Bidder and Punjab Po-

lice, shall be in English language.

4.9 Submission of bids

4.9.1 Bidder should go through the Tender advertisement

and the tender document carefully to understand the

documents required to be submitted as part of the bid.

9

4.9.2 Submission of bid response to this Tender shall be

deemed to have been done after careful study and

examination of the Tender document with full under-

standing of its implications.

4.9.3 Bidders should take into account any corrigendum pub-

lished before submitting their bids.

4.9.4 Only online bids shall be considered. Bidders would be

required to bring the Hard copies of all the documents

submitted online, duly stamped and signed by the Au-

thorised signatory of the Bidder on the day of Pre-Quali-

fication evaluation of the bids.

4.9.5 The last date and time of submission of bids shall be

04:00 PM on 09.12.2020

4.9.6 In the event of the specified date for the receipt of Bids

being declared a holiday for Punjab Police, the Bids will

be received up to the appointed time on the next work-

ing day.

4.9.7 Punjab Police may, at its discretion, extend the last

date for the receipt of bids in which case all rights and

obligations of Punjab Police and Bidder previously sub-

ject to the last date will thereafter be subject to the last

date as extended.

4.9.8 All the pages of the proposal must be sequentially num-

bered and must contain the list of contents with page

numbers. Any deficiency in documentation may result in

the rejection of the Bid.

4.9.9 Bidders are advised not to wait for the last date of the

tender and apply well in time. Punjab Police would not

be responsible for any delay in submission of bids for

any reason whatsoever.

10

4.10 Period of validity of bids

4.10.1 Bids shall remain valid for 12 (Twelve) calendar months

from the date of closing of Tender.

4.10.2 Punjab Police may request the Bidder(s) for an exten-

sion of the period of validity. The request and the re-

sponses thereto shall be made in writing (or by fax or by

e-mail). The validity of EMD shall also be accordingly

extended.

4.11 Modification and Withdrawal of Bids

4.11.1 No bid shall be altered/ modified after submission to

Punjab Police. Unsolicited correspondences in this re-

gard from Bidder will not be considered.

4.11.2 No bid shall be withdrawn in the interval between the

last date for receipt of bids and the expiry of the bid va-

lidity period specified by the Bidder in the Bid. With-

drawal of a bid during this interval shall result in the Bid-

der's forfeiture of its EMD.

4.12 Delivery

4.12.1 The cost of complete delivery of product/ services shall

be borne by the successful bidder.

4.12.2 The bidder shall be responsible to deploy the applica-

tion at the State Data Center in S.A.S. Nagar (Mohali) or

any other designated place.

4.12.3 All deliverables must conform to the applicable rules

and laws of the State Govt. and Govt. of India.

5. Rejection Criteria

Besides other terms and conditions highlighted in the tender document,

bids may be generally rejected under following circumstances:

11

5.1 General Rejection Criteria

5.1.1 Bids submitted without or improper EMD or tender fees.

5.1.2 Bids received through Telex or Telegraph or Fax or e-

Mail.

5.1.3 Bids which do not confirm unconditional validity of the

bid as prescribed in the tender.

5.1.4 If the information provided by the Bidder is found to be

incorrect or misleading at any stage or time during the

Tendering Process.

5.1.5 Any effort on the part of a Bidder to influence Punjab

Police bid evaluation, bid comparison or contract award

decisions.

5.1.6 Bids received after the last date and time for receipt of

bids prescribed by Punjab Police in this tender docu-

ment.

5.1.7 Bids without power of attorney and any other document

consisting of adequate proof of the ability of the signa-

tory to bind the Bidder.

5.2 Technical Rejection Criteria

5.2.1 Technical Bid containing financial details.

5.2.2 Revelation of prices in any form or by any reason be-

fore opening the Financial Bid.

5.2.3 Failure to furnish all information required by the Tender

Document or submission of a bid not substantially re-

sponsive to the Tender Document in every respect.

12

5.2.4 Bidders not responding to the complete scope of work/

technical standards as indicated in the Tender docu-

ments, addendum (if any), and any subsequent infor-

mation given to the Bidder.

5.2.5 If the bid does not conform to the timelines indicated in

the bid.

5.3 Financial Rejection Criteria

5.3.1 Incomplete Price Bid.

5.3.2 Price Bids that do not conform to the tender's price bid

format.

5.3.3 If there is an arithmetic discrepancy in the Financial Bid

calculations Punjab Police shall rectify the same. If the

Bidder does not accept the correction of the errors, bid

may be rejected.

6. Malpractices/ undue influence – Rejection of Bid

6.1 No Bidder shall contact Punjab Police on any matter relating

to its bid from the time of the bid opening to the time the Con-

tract is awarded, that has the effect on having any undue influ-

ence on the award of the contract to any Bidder.

6.2 Any effort by a Bidder to influence Punjab Police bid evalua-

tion, bid comparison or contract award decisions shall result in

the rejection of the Bidder's bid.

7. Right to cancel or annul Bid

Punjab Police reserves the right to cancel or annul the bid process

and reject any or all bids at any time without assigning any reason,

prior to placement of supply order/ signing of contract, without

thereby incurring any liability to the affected Bidder(s) or any obli-

gation to inform the affected Bidder(s) of the grounds for such ac-

tion.

13

8. Definitions of Important Terms

8.1 Acceptance of System: The system shall be deemed to

have been accepted by Punjab Police, subsequent to its in-

stallation, and rollout, when all the activities as defined in

Scope of Work have been successfully executed and com-

pleted to the satisfaction of Punjab Police and the UAT (User

Acceptance Testing) is issued.

8.2 Bidder shall mean organization or consortium submitting the

proposal in response to this Tender.

8.3 Contract means the Contract entered into by the parties with

the entire documentation specified in the Tender.

8.4 Contract Value means the price payable to the Bidder under

this Contract for the full and proper performance of its contrac-

tual obligations including the AMC for three years.

8.5 Go-Live means commissioning of the project after rollout of

all modules of the software/ reports as per scope of work

mentioned in the Tender document, to the satisfaction of the

Department.

8.6 OEM means the Original Equipment Manufacturer of any

equipment or system or software or product providing such

goods to Punjab Police under the scope of this Tender.

8.7 Intellectual Property Rights means any patent, source code,

copyright, trademark, trade name, service marks, brands, pro-

prietary information relating to the development of this soft-

ware whether arising before or after the execution of this Con-

tract and the right to ownership and registration of these

rights.

8.8 Prime Bidder means Agency/ Company part of the consor-

tium and severely responsible for executing the work as men-

tioned in the tender and acts as Single Point of Contact

14

(SPoC) for the Project. The Prime Bidder should be a Com-

pany/ trust/ society/ partnership firm/ organization/ entity,

which is in existence for at least 3 years in India.

9. Warranty

9.1 The successful Bidder/ Implementation Agency shall have to

provide a comprehensive free warranty valid for a period of

one year from the date of User Acceptance Testing (UAT).

9.2 The successful Bidder shall provide necessary upgrades/

patches and such other Technical inputs required for success-

ful deployment and rollout of the above-mentioned mobile and

web application, including fixing of any bugs/ vulnerabilities or

Technical problems faced by the Department/ end users as

per Scope of work.

9.3 The Bidder shall ensure that all bugs reported by the users

are duly logged and assigned a unique ID for reference

purposes. Critical Bugs (which cause the application to be

non-functional) have to be resolved in 48 hours and a

workaround provided in 24 hours. Non-Critical bugs have

to be resolved in 7 calendar days.

9.4 If the successful Bidder fails to address the above issues,

Punjab Police will be at liberty to forfeit, partially or wholly, the

Performance Bank Guarantee.

10. Annual Maintenance Contract (AMC)

The bidder shall provide three-year comprehensive Annual Mainte-

nance Support to Punjab Police commencing from the completion of

the free warranty period. Punjab Police would reserve the right to ex-

tend this Annual Maintenance Support for a further period of three

years at mutually negotiated rates, provided that such mutually negoti-

ated rates must not have an increase (if any) of more than 15% of the

average AMC for the first 3 years.

15

During the AMC period, the Bidder shall provide a basic bug logging

and bug tracking system to ensure that all bugs reported by the users

will be duly logged and assigned a unique ID for reference purposes.

Critical Bugs (which cause the application to be non-functional) have

to be resolved in 48 hours and a workaround provided in 24 hours.

Non-Critical bugs have to be resolved in 7 calendar days

11. Tolerance Clause

The Selected bidder shall agree for the development of additional

modules, if any, the cumulative cost of which will not exceed 25 per-

cent of the Contract value, on mutually negotiated man-hour rates,

which in no case will exceed the prevailing rates of National Informat-

ics Centre Services Inc. (NICSI), India at that time.

12. Penalties

The Bidder shall be liable for imposition of penalties on account of de-

lay in milestones and/ or violation of service level agreement as de-

tailed in Part-IV of the document.

13. Exit Management Plan

13.1 An Exit Management plan shall be furnished by the successful

Bidder in writing to Punjab Police not later than three months

from the issue of UAT, which shall deal with at least the fol-

lowing aspects of Exit Management in relation to the contract

as a whole and in relation to the Project Implementation and

Service Level monitoring.

13.1.1 A detailed program of the transfer process that

could be used in collaboration with a Replacement

Service Provider, including the 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 manage-

ment structure to be used during the transfer.

16

13.1.2 Plans for provision of contingent support to Project

and Replacement Service Provider for a reasona-

ble period after transfer, which in no case shall be

less than 03 (three) months.

13.1.3 Exit Management plan in case of normal termina-

tion of Contract period.

13.1.4 Exit Management plan in case of any eventuality

due to which Project is terminated before the con-

tract period.

13.1.5 Exit Management plan in case of termination of the

Bidder.

13.2 Exit Management plan at the minimum should adhere to the

following:

13.2.1 Three (3) months of the support to Replacement

Service Provider post termination of the Contract,

which will be taken as Exit Management Period.

13.2.2 Complete handover of the Planning documents, bill

of materials, functional requirements specification,

technical specifications of all equipment, change

requests if any, source codes, reports, documents

and other relevant items to the Replacement Ser-

vice Provider/ Punjab Police.

13.2.3 Certificate of Acceptance from authorized repre-

sentative of Replacement Service Provider issued

to the Bidder on successful completion of handover

and knowledge transfer.

13.3 During the exit management period, the Bidder shall use its

best efforts to deliver the requisite services.

14. Application Security Audit

The Bidder shall apply for and procure security audit certificate from

the CERT-In Empaneled Information Security Auditing Organisations

17

and submit the same to Punjab Police not later than 2 months from is-

sue of UAT.

15. Intellectual Property Rights

15.1 The Bidder must ensure that while using any software, hard-

ware, processes, documents or material in the course of de-

velopment, implementation and maintenance of the applica-

tion/ Services, it does not infringe the Intellectual Property

Rights of any person or Company. The Bidder shall keep Pun-

jab Police indemnified against all costs, expenses and liabili-

ties whatsoever, arising out of any illegal or unauthorized use

(piracy) or in connection with any claim or proceedings relat-

ing to any breach or violation of any permission/ license terms

or infringement of any Intellectual Property Rights by the Bid-

der or the Bidder’s Team during the course of performance of

the above contract. The Bidder’s liability is excluded regarding

any claim based on any of the following:

15.1.1 Anything which Punjab Police provides and is in-

corporated into the application;

15.1.2 Punjab Police modification of the application;

15.1.3 The combination, operation, or use of the applica-

tion with other materials, if the third party claim has

been caused by the combination, operation or use

of the application.

15.2 Punjab Police shall own and have a right in perpetuity to use

all newly created Intellectual Property Rights which have been

developed solely during execution of this Contract, including

but not limited to all processes, products, source codes, speci-

fications, reports and other documents which have been

newly created and developed by the Bidder solely during the

development, implementation and maintenance of the applica-

tion and for the purposes of inter-alia use or sub-license of

18

such Services under this Contract. The Bidder undertakes to

disclose all such Intellectual Property Rights arising in perfor-

mance of the Services to Punjab Police, execute all such

agreements or documents and obtain all permits and approv-

als that may be necessary in regard to the Intellectual Prop-

erty Rights of Punjab Police.

15.3 If Punjab Police so desires, the Bidder shall be obliged to en-

sure that all approvals, registrations, licenses, permits and

rights etc. which are inter-alia necessary for use of the goods

supplied/ installed by the Bidder, shall be acquired in the

name of Punjab Police, prior to termination of this Contract

and which may be assigned by Punjab Police to the Prime

Bidder for the purpose of execution of any of its obligations

under the terms of the Bid, Tender or this Contract. However,

subsequent to the term of this Contract, such approvals, regis-

trations, licenses, permits and rights etc. shall endure to the

exclusive benefit of Punjab Police.

15.4 The bidder shall not copy, reproduce, translate, adapt, vary,

modify, disassemble, decompile or reverse engineer or other-

wise deal with or cause to reduce the value of the Materials

except as expressly authorized by Punjab Police in writing.

16. Waiver

Failure or delay on the part of the Successful Bidder or Punjab Police

to exercise right or power hereunder shall not operate as a waiver

thereof.

17. Assignability

Neither this Contract nor any rights under it may be assigned by either

Party without the express prior written consent of the other Party. How-

ever, upon assignment of the assignor's interest in this Contract, the

19

assignor shall be released and discharged from its obligations hereun-

der only to the extent that such obligations are assumed by the as-

signee.

18. Severability

If any portion of this Contract or any of the Contract Documents hereto

is held to be invalid, such provision shall be considered severable, and

the remainder of this Contract hereof shall not be affected.

19. Governing Law

This Contract including the Contract Documents shall be governed by

and construed in accordance with the laws of India and the Courts at

Chandigarh shall have jurisdiction in this regard.

20. Termination for Default

20.1 Punjab Police may without prejudice to any other remedy for

breach of Contract, by Thirty (30) days written notice of de-

fault sent to the Successful Bidder and upon the Successful

Bidder's failure and neglect to propose and/ or execute any

corrective action to cure the default, terminate this contract in

whole or in part, if the Successful Bidder fails to perform any

of his obligation(s) under the Contract.

20.2 On termination of the Contract for default, the security deposit

of the Successful Bidder will be forfeited.

20.3 On termination of the Contract for default, action will be taken

to black list the Successful Bidder.

21. Resolution of Disputes

If any question, difference or objection whatsoever shall arise in any

way connected with or arising out of this instrument or the meaning or

operation of any part thereof or the rights, duties or liabilities of either

20

party than save in so far as the decision of any such matter is herein-

before provided for and has been so decided, every such matter in-

cluding whether its decision has been otherwise provided for and/ or

whether it has finally decided accordingly of whether the contract

should be terminated or has been rightly terminated in whole or part

and as regards the rights and obligations of the parties as the result of

such termination shall be referred for arbitration to any officer ap-

pointed by Punjab Government acting as such at the time of reference

and his decision shall be final and binding and where the matter in-

volves a claim the amount if any awarded in such arbitration shall be

recoverable in respect of the matter so referred.

22. Force Majeure

The Successful Bidder shall not be liable for forfeiture of its perfor-

mance security, liquidated damages or termination for default, if the

delay in performance or other failure to perform its obligations under

the contract is a result of an event of Force Majeure. For purposes of

the clause, "Force Majeure" means an event beyond the control of the

Successful Bidder and not involving the Successful Bidder's fault or

negligence and not foreseeable. Such events may include wars or rev-

olutions, fires, floods, epidemics, quarantine restrictions, freight embar-

goes etc.

21

Part-II – Bid Process

23. Bid Process

Bids are invited in two bid system i.e. Technical Bid and Financial Bid.

23.1 Technical Bid

23.1.1 Technical Bid shall comprise of the following sup-

porting documents that must be uploaded online.

Also, one set of self-attested hard copies of the

same, with the Authorised Seal and Signature of

the Bidder, must be brought along at the time of

opening of Technical Bid. These hard copies shall

not be considered for any process of evaluation

and are being sought only for verification of au-

thenticity. It is clarified that only those documents

that have been uploaded online with the Tender

will be considered for evaluation.

Supporting Documents:

23.1.1.1 Bidders Particulars (Annexure-1).

23.1.1.2 Pre-Qualification Covering letter as

per prescribed format at Annexure-2.

23.1.1.3 Guarantee as per Annexure-3.

23.1.1.4 Prescribed supporting document to

prove fulfillment of criteria of Average

Annual turnover of Bidder (In case of

consortium, relevant document of ei-

ther partner) as specified in Table-1

below.

23.1.1.5 Supporting document to prove fulfill-

ment of criteria of experience of the

Bidder (In case of consortium, rele-

vant document of either member of

22

the consortium) as specified in the

Table-1 below.

23.1.1.6 Copy of receipt of online payment of

Earnest Money Deposit on

https://eproc.punjab.gov.in website by

Bidder (In case of consortium, rele-

vant document of prime bidder).

23.1.1.7 Power of Attorney for Authorization

of Signatory for bid signing by prime

bidder.

23.1.1.8 Consortium Agreement, if applicable.

23.1.1.9 Document to support that the bidder

(the Prime bidder or its consortium

partner in case of consortium) is an

original developer of Facial Recogni-

tion Software as specified in Table-1.

23.1.1.10 Affidavit that the bidder is not black

listed as specified in Table-1. (In

case of consortium, affidavits of both

partners)

23

Table -1

S. No.

Parameter / Criteria Supporting documents re-quired to be uploaded by the bidders along with the tech-nical bid

1. Average Annual Turnover

The company must have an average an-nual turnover arising out of software de-velopment/ Mobile application develop-ment of at least INR 5 Crores during last three financial years (i.e. Year 2017-18, year 2018-19 and year 2019-20)

Audited Balance Sheet, profit

and loss account for the relevant

financial years Or a Certificate by

a Chartered Accountant (regis-

tered with ICAI) regarding the

same.

2. Experience

Prime bidder must have been primarily en-

gaged in the field of Software development

preferably with specialization in develop-

ment of Mobile Application Software from

atleast last three financial years. In case of

consortium, the other member must also

be primarily engaged in the field of Soft-

ware development.

Bidder (at least one of the partners in

the case of consortium) must have de-

veloped and provided facial recognition

software in the last 3 financial years

either to Police/ Paramilitary forces or

some other State/ Central government

organization, in connection with secu-

rity matters.

Bidder must attach copies of rele-

vant supply orders. These must

be accompanied by at least One

(01) Certificate of successful

completion of Project or Certifi-

cate of Satisfactory performance

in case of an ongoing Project.

3. Original developer of Facial Recogni-

tion Software

The bidder (the Prime bidder or its consor-

tium partner in case of consortium) is an

original developer of Facial Recognition

Software.

Documentary evidence/ Certifi-

cate to this effect

4. Blacklisting

Bidder (both members of consortium)

must not be blacklisted by any State/ Cen-

tral Government or PSU.

Affidavit regarding the same

23.2 Financial Bid

24

23.2.1 Financial Bid should be in accordance with the format

provided at https://eproc.punjab.gov.in. The Bidder is re-

quired to provide the break up cost mentioning the cost

of each component, Annual Maintenance Charges of

three years, all other costs, all taxes, duties and any

other incidental costs as detailed below.

S. No. Module Price (INR)

1 Login Module - User Authentication and Login to Ap-plication

2 Record creation module of CCTNS/HRMS

3 Facial Recognition Search

4 Search module (General/ Advanced)

5 Access to Applications

6 Persons of Interest (PoI)

7 Village Information System (VIS)

8 Human Resource Management System (HRMS)

9 Dashboard and Reports

10 Annual Maintenance Cost for 1st year

11 Annual Maintenance Cost for 2nd year

12 Annual Maintenance Cost for 3rd year

13 Training

14 Any cost(s) other than above, (please specify)

15 Taxes/ duties etc.

TOTAL COST

23.2.2 All prices should be quoted in Indian Rupees.

25

23.2.3 In the absence of information on break-up of cost

as requested above, a bid may be considered in-

complete and may be summarily rejected.

23.2.4 Bidder shall carry out all the tasks as stipulated in

the Tender document and it shall be the responsi-

bility of the Bidder to fully meet all the requirements

of the Tender document and the scope of work.

23.2.5 Financial Bid should clearly indicate the price to be

charged without any qualifications whatsoever and

should include all taxes, duties, fees, levies, works,

contract tax and any other charges as may be ap-

plicable in relation to the activities proposed to be

carried out.

23.2.6 A financial bid submitted with a variable price quo-

tation or conditional bid shall be treated as incom-

plete and the bid shall be rejected summarily.

23.3 Discount

Bidders are strongly advised not to indicate any separate dis-

count. Discount, if any, should be an integral part of the quoted

prices. Discount of any type, indicated separately, will not be

taken into account for evaluation and comparison purpose.

24. Evaluation of Bids

24.1 Bids will be evaluated in following three stages:

S. No. Stage Documents/ Technical Proposal that will be examined

1. Pre- Qualification Documents

As specified in clauses 23.1.1.1 to 23.1.1.10

2. Technical Evaluation As specified in Table-2 below.

26

3. Financial Bid Financial Bid should be in accordance with the format provided at https://eproc.punjab.gov.in and includ-ing format details of break-up of costs as detailed in clause 23.2.1.

24.2 Pre-qualification screening:

Documents of each bidder as specified in clauses 23.1.1.1 to

23.1.1.10 would be verified/ evaluated. Only the bidders fulfilling the

minimum criteria as at Table-1 in para 23.1 above shall be invited for

technical evaluation.

25. Technical Evaluation

25.1 Only those bidders who fulfil the minimum pre-qualification cri-

teria will be considered for further Technical Evaluation. The

bids of rest of the bidders who do not qualify shall not be pro-

cessed further.

25.2 Technical evaluation shall be carried out by a committee of

officers/experts who shall make an in-depth assessment of

various aspects including, but not limited to, the nature and

volume of experience of the bidder in related technical fields,

their technical capabilities and expertise, understanding of the

scope of work, prior experience in facial recognition domain

and execution of a POC (Proof of Concept) of their FRS capa-

bilities etc as per POC guidelines given at Point No. 25.3.

Details of parameters for evaluation and their respective

weightages are given in Table-2:

27

Table 2

S.No. Parameters Specific Requirement Marks

1. Experience in Mobile Application/ Develop-ment Do-main

Bidder will share details of the relevant Work Orders.

20

2. Experience in Facial Recognition Domain

Bidder will share details of the Work Orders of work done for any Indian State Govt/ Cen-tral Govt agency in security related projects with Facial Recognition.

20

3. POC Bidder will be asked to do a POC to demon-strate the efficacy of their FRS (Facial Recognition Software) as detailed in scope of work. Department will provide the image database and test cases for the POC. Bid-der will need to get their own infra to Punjab Police premises to conduct the POC.

20

4. Experience on CCTNS/HRMS

Bidder will share details of the Work Orders for work done on CCTNS/HRMS related projects.

15

5. Presenta-tion (Submit the Hard Copy of the Presenta-tion)

Presentation should consist of:

a) Understanding of the complete scope of the project

b) Snapshots of mobile application, web application software.

c) Workflow of mobile application software, web application software.

25

TOTAL TECHNICAL SCORE (TS) 100

28

25.3 Guidelines for POC: -

Bidder will be asked to do a POC to demonstrate the efficacy of

their Facial Recognition Software (FRS). Focus will be on the func-

tionality of the FRS and not on the performance as the bidders will

be getting their own infra. Guidelines for the POC are given below:

Bidder will need to get their own infra to Punjab Police prem-

ises to conduct the POC.

Usage of Internet during the POC is strictly forbidden. Any Bid-

der found using the internet will be immediately disqualified

Punjab Police will provide dataset of 1000-10000 images to the

bidder. Average size of each image will be less than 30KB and

will be of jpeg format

The same dataset and test cases will be given to all the bid-

ders.

Images will be of varied quality and taken under different condi-

tions (both indoors and outside)

Test cases will include both 1:1 and 1:n match

25.4 Technical bid of the Bidder shall be opened and evaluated for

acceptability of Techno-functional requirements, deviations

and technical suitability.

25.5 The technical committee shall evaluate each technical pro-

posal by deploying the criteria as mentioned above. Each Bid-

der shall be marked on a scale of 1 to 100 based on their

technical proposal.

25.6 In case of no response by the Bidder to any of the parameters

of Table-2 above, no marks will be assigned for the same.

25.7 Bidders, whose bids are responsive and score a minimum of

50 marks (minimum marks to obtain for technically qualifying)

from the technical evaluation criteria would be considered

technically qualified for financial evaluation.

26. Opening of Financial Bids

26.1 Financial Bids of only those bidders who qualify subsequent to

Technical evaluation shall be opened.

29

26.2 No enquiry shall be made by the bidder(s) during the course

of evaluation of the tender, after opening of bid, till final deci-

sion is conveyed to the successful bidder(s). However, the

Committee or its authorized representative can make any en-

quiry or seek clarification from the bidders, which the bidders

must furnish within the stipulated time failing which bid of such

defaulting bidders may be rejected.

27. Integrated financial-cum-technical evaluation

27.1 The evaluation shall be based on the technical and financial

parameters. The weightage for the technical parameters shall

be 70% and the financial parameters shall be 30%.

27.1.1 Technical Weightage (St): The marks scored by

the bidder in technical evaluation shall be calcu-

lated to 70 points as St = T*0.70 where T is the

Technical score awarded to the bidder as per

Technical Evaluation Criteria.

27.1.2 Financial Weightage (Sf): The marks scored by the

bidder in financial evaluation shall be calculated to

30 points as below:

27.1.2.1 The Commercial scores of all the pro-

posals will be determined by Sf = 30 *

Fm/ F

27.1.2.2 Fm = Lowest evaluated tender cost

27.1.2.3 F = value of Commercial proposal un-

der consideration

27.1.3 Proposals will be ranked according to their com-

bined Technical (St) and Commercial (Sf) scores.

The combined Technical and Commercial score

shall be calculated as S=St + Sf.

30

27.1.4 The bidder with the highest combined score(s)

shall be declared successful to be awarded the

contract.

28. Notification of Award

28.1 Prior to the expiration of the period of bid validity, the success-

ful Bidder shall be conveyed in writing that its bid has been

accepted. The Bidder shall provide his/ her acceptance within

07 days of above communication, alongwith the Sizing re-

quirements of the Infrastructure. The notification of award will

constitute the formation of the Contract.

28.2 At the time of placement of the supply order, as per the re-

quirement of the department, the finally selected Bidder shall

sign the contract with Punjab Police. The finally selected Bid-

der shall bring along with him the power of attorney, the Per-

formance Bank Guarantee and common seal etc. for signing

the contract.

29. Performance Bank Guarantee (PBG)

Within 07 days of the receipt of notification of award or Letter of Intent

from Punjab Police, the Successful Bidder shall submit a Performance

Bank Guarantee (PBG) amounting to 5% of the contract value includ-

ing cost of Annual Maintenance Contract for three years of product/

services to be supplied, in favour of ADGP Technical Services, Pun-

jab, Chandigarh. The above mentioned 5% PBG will be released after

expiry of the three year AMC period.

30. Signing of Contract

The successful Bidder shall sign the contract within 7 working days of

submission of Performance Bank Guarantee.

31

Part-III – Scope of Work/ Technical Standards

31. Scope of Work/ Technical standards

Functional requirements/specifications for Development, Implementa-

tion and Maintenance of CCTNS/ HRMS mobile and web app with AI

powered search and quality validation technology

S.

No.

Item Description

1 Development of Mobile

(Android and iOS) App

and Web Application

i. A uniform and simplified User Inter-

face should be developed following

the standards and guidelines set up

for Android and iOS app development.

ii. Apps must look and function in a

similar manner across different

makes/ models of Android/iOS mobile

devices.

iii. Android App must support all mo-

bile devices including tablets with An-

droid 8.0 Oreo or above.

iv. iOS App must support all mobile

devices including tablets released by

Apple with iOS version 10.0 and

above.

v. Web Application should support

popular browsers such as Chrome,

Safari and Firefox.

vi. All App icons must be crisp, clean,

and distinguishable.

vii. All App buttons and objects must

be reactive to touch.

viii. All App functions must stay within

the mobile platform boundaries except

in case of Navigation.

ix. The app should support horizontal

and vertical scrolling to enable com-

plete viewing of attachments and data.

x. Wherever possible drop-down

menus must be provided instead of

32

text-boxes, so that data ambiguity is

avoided.

xi. After taking user consent App

should enable GPS and use GPS

functionality. (Note: GPS Locations to

use Reverse geocoding services from

ArcGIS.)

xii. App home screen must display all

services provided by the Police De-

partment as separate icons.

xiii. App must adhere to the e-Gov-

ernance Standards of the Govern-

ment.

xiv. App must have mechanisms to

include following data which can be in-

tegrated with CCTNS/ HRMS forms.

1. Facial Images and other photo-

graphs with use of Camera and device

storage.

2. Fingerprints with use of OTG (On

The Go) supported fingerprint scan-

ners without any need of additional

drivers. Punjab Police will be procur-

ing scanners which have SDKs which

can be installed on mobile devices.

Bidder will need to incorporate the

SDK in their applications to provide

the desired functionality.

2 User authentication and

login to App

i. The app must support 2-factor au-

thentication through password and

OTP via SMS. The 2 - factor au-

thentication would be valid for 2

hours (duration should be configu-

rable). During these 2 hours, after

2 mins (duration should be config-

urable) of idle time the user would

need to enter the password for any

data update. However, if the user

33

is just doing search, then no pass-

word is required even after 2 min

of idle time (within the 2 hours).

ii. New User registration/ verification

for this module (New User regis-

tration process flow for Village In-

formation System module and

Person of Interest module is de-

scribed later in this document) will

require approval from 3 levels

a) Designated person by respective

Unit Officer

b) Unit Officer

c) State Nodal Officer of the Appli-

cation

iii. Work flow for new user rejection/

verification

a) Upon successful submission

of the user details, the system au-

tomatically forwards the request

to the concerned district/unit des-

ignated person who must verify

the data. Upon successful vali-

dation, the request is forwarded

to the dashboard of head of dis-

trict/unit. Otherwise, the request

is rejected.

b) Upon receipt of request, head

of district/unit shall verify the user

details. If the user details are

valid, the request is forwarded to

the dashboard of State Nodal Of-

ficer. Otherwise, the request is

rejected.

c) Upon receipt of request, the

State Nodal Officer verifies the

user details. If the details are

valid, credentials of the new user

are generated and sent to him/

her through text message. Other-

wise, the request is rejected.

34

iv. All rejections/ acceptances above

would be conveyed to the applicant

through text messages.

v. Steps for new user registration/

verification:

a) After successful submission

of the user details, the details

must be automatically sent to

concerned District Designated

person by Unit Officer, where

Unit Designated person must

verify the data, if user details are

valid, an option must be pro-

vided to forward the request to

Unit Officer dashboard inward, if

user details are not valid the

Team Rejects the Request.

b) Whenever Unit Officer re-

ceives the request, he/ she ver-

ifies the user details. If user de-

tails are valid Unit Officer for-

wards the request to the State

Nodal Officer dashboard in-

ward. If user details are not valid

Unit Officer Rejects the Re-

quest.

c) Whenever the State Nodal Of-

ficer of the application receives

the request, he/ she verifies the

user details. If user details are

valid the same will be con-

firmed. After confirmation, user

will get text message of confir-

mation. If user details are not

valid, the State Nodal Officer of

the application rejects the Re-

quest.

vi. Cost of SMS for OTP will be borne by the Department.

35

3 Security and

Identity Man-

agement

i. The application should have secu-

rity at the network and application

layer. The app will only be accessed

if the user is on a VPN or secure in-

tranet. The user ID and password will

be authenticated against an LDAP

repository. The mobile app will have

an additional layer of authentication

of OTP password received over

SMS.

ii. The application should have role-

based access control at all levels and

follow the principle of "least privi-

lege". All the access logs need to be

captured and monitored.

iii. The system must be secure at all

user touch points by using suitable

security protocols and data protec-

tion methods.

iv. User credentials will be stored in

a LDAP repository. In addition to

user Id and password, the user re-

pository will also contain other attrib-

utes like Role which will be used to

authorize access.

v. Solution must be comprehensive

with user provisioning, de-provision-

ing and password management

tools.

vi. The solution should either use the

same LDAP repository as the

CCTNS/ HRMS application or pro-

vide SSO functionality with CCTNS/

HRMS

vii. Any files which are to be up-

loaded will need to be scanned for vi-

ruses before they are uploaded.

4 Integration with

specified Databases

and Access to Appli-

cations

The application must be fully inte-

grated with the following databases:-

i. CCTNS.

ii. HRMS.

36

Iii. PAIS. It must integrate with PAIS to

auto populate most fields after fill-

ing FIR details.

iii. Database schemas for relevant ta-

bles of CCTNS, PAIS and HRMS

will be shared with the successful

bidder.

iv. Persons of Interest (to be created

as part of this application).

v. Village Information System (to be

created as part of this applica-

tion).

An option must be pro-

vided for the user to login and

access the following portals (Au-

thorization to access these por-

tals to be defined in the User

Roles)

a) ArcGIS

b) ICJS

c) e-prisons

d) Saanjh

e) PAIS

Note: - Bidders can assume that the

initial dataset will consist of 1

Million Facial Images. Incre-

mental images per year will

be 100,000. Bidders will be

provided these images to

process and upload.

5 Record creation

module of

CCTNS/HRMS

i. App should allow the following

CCTNS forms to be filled. Follow-

ing CCTNS forms must be filled us-

ing mobile in the CCTNS database

(Bidder must obtain details of IIF

and CCTNS forms by visiting

http://punjabpo-

lice.gov.in/iifforms.aspx to access

development efforts involved).

a) Crime detail data (IIF2)

37

b) Arrest/ court surrender data (IIF3)

along with photos to support FRS

c) Property search and seizure data

(IIF4)

d) Missing person data (IIF8)

e) Unidentified person registration data

(IIF9)

f) Unidentified dead body data registra-

tion (IIF10)

g) Registration of unnatural death

(IIF11)

h) Gang profile (OCIS-1)

i) Gang organization (OCIS 2)

j) Member detail form (OCIS 3)

k) Additional fields defined by the Depart-

ment within 3 months of award of ten-

der will need to be added to the forms.

l) Additional forms defined by the De-

partment within 3 months of Award

of Tender will also have to be ca-

tered to.

ii. The application shall have to sup-

port the latest version/ updates of

CAS (Core Application Software)

CCTNS which are operationalized at

least one month before the expiry of

the Annual Maintenance Contract.

iii. An Investigation officer must be able

to access only those FIRs/Inquiries

assigned to him/her by logging in the

app. In addition, the IO will have vis-

ibility of the completion status of all

the forms associated with the FIR/In-

quiry.

iv. Application should access CCTNS/

HRMS data in real time and auto

populate related forms.

v. It should be possible to save any of

these forms with partial information

(as long as all the mandatory fields

have been filled) and update the

non-mandatory fields subsequently.

38

However, during subsequent up-

dates, only new data in the unfilled

fields may be accepted while the

fields already filled may be displayed

on the screen without rights of modi-

fication.

vi. Application should update CCTNS/

HRMS data in real time.

vii. While adding Crime details like

Crime Scene Details, Witness De-

tails, etc. there must be an option to

upload video, audio and image files

upto a max (configurable) limit. A se-

cure hash function must be used by

the application to generate secure

hash in order to prove the authentic-

ity of these files in future.

viii. All locations in the forms must be

pick-able with reverse geocoding

support using ArcGIS.

In order for the Bidder to build the

mobile and web apps which add

and update records to the CCTNS/

HRMS DB while meeting the

CCTNS/ HRMS application and

Database integrity constraints,

the department will share the rele-

vant portions of the CCTNS/

HRMS application code and Data-

base schema with the successful

bidder. The successful Bidder

shall sign a Non-Disclosure

Agreement and undertake to use

this code strictly for building the

app for the department and will

not copy, reproduce, translate,

adapt, vary, modify or share the

code with any other party.

6 Facial Recognition

Search (FRS)

i. FRS based search must have ac-

curacy of above 95% (positive match

rate) on publicly available large data

39

set having more than 1 million unique

facial images. The False Positive

match rate should be less than 1%.

ii. FRS based search must have short

processing time (less than 20 sec-

onds for 1 million images for 99% of

the queries

iii. Should be possible to configure pa-

rameters to control Percentage of

False Positives and False negatives

in the search result.

iv. FRS based search must be capable

of performing an automated one to

many {1:N} and a one-to-one {1:1)

search against a database of images

added from this App as well as im-

ages stored in CCTNS/HRMS and

any other DB provided by the Depart-

ment.

v. FRS based search must support

both colored and grey scale images.

vi. FRS based search must be able to

match facial images with change in

facial expression, direction, angle,

lighting, age, hairstyle, beard, facial

accessories (eye glasses, caps, tur-

ban, etc.) and scars, marks and tat-

toos. It should work regardless of

vantage point.

vii. FRS based search must be able to

work on moderate face rotation ei-

ther horizontal or vertical.

viii. FRS based search must be able to

use standard criteria including 2D for

matching of the faces with an exist-

ing facial database/gallery of face im-

ages.

ix. FRS based search must be capable

of comparing the following:

a) Mug shot to mug shot

b) Mug shot to CCTV image

c) CCTV image to Mug shot

40

d) CCTV image to CCTV image

x. FRS based search must have a re-

port management tool to generate

real time non-editable report based

upon different searches, such as:

a) Audit log report of searches per-

formed

b) Event log of searches performed

c) Hit List Report of the accused

found as "Best" by FRS

d) Statistics Report of the usage of

FRS

FRS based search must be hosted

on a facility provided/approved by

Punjab Police Data Centre, required

hardware and connectivity will be

provided by the Department.

xi. The hardware infra will be provided

by the department. Bidders can as-

sume that the initial dataset will con-

sist of 1 Million Facial Images. Incre-

mental images per year will be

100,000. Bidders will be provided

these images to process and upload.

7 Search module In addition to Facial Recognition

based Search defined above, the

search module of app must have:

a) Comprehensive search in which im-

portant fields including Police Sta-

tion, District, Crime Act and section,

offence type, weapon number, mo-

dus operandi, name of accused etc.

are searchable. The search could

further be filtered using different at-

tributes of accused like Age, Height,

Complexion, etc. In addition, the

search tool must also provide op-

tions for various types of filters and

sorting facilities.

41

b) Advanced Search facility wherein

the user can specify part or com-

plete Name of person. The Name

can be that of an Accused, Relative,

Witness, Victim, Person of Interest,

etc. If the user specifies different

combinations of Accused, Relative,

Witness, etc. then the search will re-

turn matches where ALL the condi-

tions are met. The search will return

possible matches and other details

like FIR No, Accused ID, etc. which

can help in further investigation.

c) Phonetic search for names of person

(accused, relative, witness, victim,

etc.) and names of places

d) Mobile Number Registration Search:

Providing a result which combines

the result from searching the 112

system (using APIs provided by the

department) and searching for the

Mobile numbers in the

CCTNS/HRMS DB.

e) Vehicle Number Search: Providing a

result which combines the result

from searching the Vaahan system

(using APIs provided by the depart-

ment) and searching for the Vehicle

numbers in the CCTNS/HRMS DB.

f) Finger Print based search: If the fin-

ger print of the person of interest are

available then the application must

search the fingerprint DB using

APIs provided by the department.

g) NERS DB Search: An option must be

provided to get the NERS call details

of a person by searching with Name

& Mobile number. APIs to get details

from NERS DB will be provided by

Department.

h) Search in Punjabi – Application

should be able to search for names

42

of People and Places in both Eng-

lish and Punjabi. English to Punjabi

translation for names of People and

Places will be done by calling a API

provided by the department.

i) Punjab Police can ask vendor to add

more search filters or modify exist-

ing search filters during the warran-

tee period without any additional

payment to the Vendor in case any

such need arises in future.

j) Accused Link analysis and search:

Different accused should be linka-

ble to each other through FIR data.

This should be at 3 level. Suppose

if A and B are co-accused in one

case, B and C are co- accused in

another case and C and D are co-

accused in yet another case, this

module should be able to link A, B,

C and D.

The application should return

the search results in less than 5

seconds for 99% of the queries. In

order to provide fast search capabil-

ities and also not put undue load on

the CCTNS/HRMS production DB,

it is recommended that the Bidder

create a search DB (using open

ArcGIS or Open Source technolo-

gies) which is populated on a peri-

odic (atleast once a day) basis.

8 Free Form AI Powered

Intuitive Search

The user can enter text in a free form

text field. The data entered could be a

Mobile Number, vehicle number, En-

gine or chasis number, etc. Based on

the format and type of text entered, the

system will use AI to understand the

intent of the user and do the appropri-

ate search.

43

9 Persons of interest

(PoI)

This module (an AI driven system)

will be used to create an additional

layer of information (over and above

the information already existing in

CCTNS/HRMS) about existing/ po-

tential crime/ criminals. Users will be

able to log into the system using their

HRMS ID and OTP. Key aspect of

this system is the anonymity of the in-

formation provided by the user.

a) Nature of crime:

PoI data to classify information

mainly on the following heads:

i. Drugs

ii. Terrorism

iii. Killing

iv. Rape

v. Fire Arms

vi. Liquor

vii. Gambling

viii. Sudden wealth

ix. Extortion

x. Snatching

xi. Land Mafia

xii. Eve teasers

xiii. Sand smuggling

xiv. Any other, please specify

b) Nature of data to be gathered

about Person of Interest:

1) Identity documents such as:

i. Passport

ii. Aadhar

iii. Driving License

iv. Voter Card

v. Employer Identity Card etc.

2) Provision to record all fields re-

lated to Person of Interest, viz.:

i. Phone numbers: Mobile/ Land-

line

ii. Photograph

iii. Property details

iv. Family relatives

44

v. Details of automobiles/ two

wheelers

vi. Details of Fire Arms

vii. Details of Bank Accounts.

viii. Details of Gangs/ Associates

ix. Details of Social Media platforms

such as: Facebook, Twitter, Email,

TikTok, Instagram, WhatsApp.

x. Field Unit to which the Person

of Interest is associated with

c) Flow of information:

i. Authorized persons can login and

input information.

ii. In addition to Information being

captured in structured form, user can

also enter data in a free text (unstruc-

tured data). The unstructured data

will be analysed using AI/ML. In ad-

dition to using this data in crime in-

vestigation, the analysis will also be

used to add more structured fields to

the form.

iii. The system would compare this

information with existing information

(based on CCTNS/HRMS/ PoI/

VIS/HRMS)

iv. If information is already there, no

further action would be required. Oth-

erwise, fresh inputs would become

visible to the concerned CP/ SSP.

v. CP/ SSP would be free to seek

fresh inputs from intelligence/ fields.

Then they would decide whether in-

formation is actionable or not.

vi. In case it is actionable, information

be added to the data bank compris-

ing of CCTNS/HRMS/ PoI/ VIS data,

otherwise the information would be

saved in a non-actionable database.

d) Other Features:

i. All in-service and retired police offi-

cials (with authorization for login)

45

would be able to make the initial in-

puts.

ii. Identity of the informant would be

anonymized before making the infor-

mation accessible to the next level

i.e. CP/ SSP.

iii. Facility for Intelligence/ Field staff

to modify/ edit information before

saving.

iv. Inputs which are not found to be

actionable and rejected would also

be separately saved.

v.Facility for grading of each transac-

tion about the quality of information.

Grading to be done by CP/ SSP on a

scale of five.

10 Village Information

System

This primary user of this module

will be the Village Information Of-

ficers. They will be the same us-

ers who have access to the

CCTNS/HRMS application. It will

provide them the ability to pro-

vide information about peo-

ple/place/event in their area of ju-

risdiction and also receive alerts.

1. Primary Data to be captured

a) Details of persons of interest

of area

Application should support cap-

ture of following information as

per the jurisdiction of the Village

Information Officer

i. Information of criminals of area

ii. Information of proclaimed offend-

ers.

iii. Information of persons actively

engaged in NDPS cases.

iv. Information of suspects/ accused

in snatching cases.

v. Information of idlers.

46

vi. Information of drug addicts and

their associates.

vii. Information of unemployed youth

of the area.

viii.Information of prominent persons

of the village pertaining to differ-

ent categories. Categories may

be drop down such as:

(a) Sarpanch

(b) Serving cop

(c) Retired cop

(d) Teacher

(e) Govt. employee

(f) Armed forces, etc.

ix. Thana and Village

x. Information of Influencer

b) Details of places of interest

i. Important landmarks

ii. Schools

iii. Colleges

iv. Religious places such as;

(a) Gurudwara,

(b) Temple,

(c) Mosque,

(d) Dera,

(e) Church; etc

v. Community Centres

vi. Data to be collected about these

places of Interest will include

lat/long, contact person, etc.

c) Details of important events

such as;

i. local melas,

ii. important murders,

iii. killings,

iv. terrorists’ incidents; etc.

d) Details of information of inter-

est such as;

i. Historical information,

ii. enmity amongst families etc.

2. Information which can be

viewed:

47

Village Information officer should

be able to see data of FIRs of ac-

cused/ suspects of those FIRs

and should be able to link addi-

tional data that has not been al-

ready captured through

CCTNS/HRMS such as;

a) Identity documents such as;

i) Passport

ii) Aadhar

iii) Driving License

iv) Voter Card

v) Employer Identity Card etc.

Provision to record all fields re-

lated to above documents.

b) Phone numbers: Mobile/ Landline

c) Property details

d) Family relatives

e) Details of automobiles/ two

wheelers

f) Details of Fire Arms

g) Details of Bank Accounts.

h) Details of Gangs/ Associates

i) Details of Social Media platforms

such as: Facebook, Twitter,

Email, TikTok, Instagram,

WhatsApp

3. Reports:

i. Village Information officer

should be able to access stand-

ard reports pertaining to his ar-

eas generated through

CCTNS/HRMS.

ii.He should also be able to see

information from VIS database

pertaining to his area.

4. Alerts:

Village Information officer should

receive alerts as soon as:

i. Jail Outs (persons who have come

out from Jail)

ii. Case is registered in his area

48

iii. An accused of his area is involved in

some FIR

Iv. An accused belonging to his area

is arrested anywhere in the State

v. An accused is arrested in his area.

11 HRMS (Human

Resource Man-

agement System)

The App should be capable of the fol-

lowing:-

1. To capture entry and exit of Employee

in HRMS. Entry could be due to fresh

appointment, deputation from Govt of In-

dia/other departments, absorption from

other organisations, reinstatement after

dismissal. Exit could be due to superan-

nuation, voluntary retirement, compul-

sory retirement, dismissal, death, depu-

tation/transfer to Government of In-

dia/other department, absorption in an-

other cadre

2. To capture vertical (promotion/demo-

tion) and horizontal (transfer/deputation)

movement within HRMS.

3. To capture all orders of attachments

(the official continues to remain in the

same unit but is attached to some other

unit/ individual for the purpose of duty).

4. To capture details of all deployments

in all units. This should support a multi-

level dropdown menu with all menus

from the second level onwards depend-

ing upon the choice of the immediate

49

previous level. The system should sup-

port up to 8 levels of such choices to fa-

cilitate drilldown of each deployment.

This would also cover all deploy-

ments with protectees for security

purposes.

5. To capture all orders currently being

managed through Order Book System

covering the following categories of or-

ders:

a. Training and Inspection - Including all

orders regarding parades, inspections

and duties.

b. Establishment - Including all orders

regarding enrolments, discharges, trans-

fers, increases and decreased of

strength, promotions, reductions, leave

and pensions.

c. Discipline - Including orders regard-

ing punishments, rewards and all orders

of a disciplinary nature.

d. Miscellaneous.

6. Tracking all movements related to

transfer/ deputation etc such as:

a. Charge relinquishing

b. Charge assuming

c. Departure

50

d. Arrival

6. Produce reports for concerned data

operators for manual entry into HRMS.

7 . Develop the following modules to

supplement HRMS

a. Departmental Enquiries.

b. Criminal cases against officials.

c. Vigilance Enquiries

d. Health information.

e. Issuing of resources to personnel

I. Vehicles

ii. Wireless sets

iii. Weapons

iv. Computers

8. The App should automatically update

the sign-on authorizations/ privileges de-

pending on any change in role/ jurisdic-

tion as per the updations in HRMS sta-

tus.

9. The HRMS Database will consist of 2

sets of tables. One set of tables will be

based on the HRMS DB (managed by

NIC). This data is for read purposes

only. Data in these tables will be popu-

lated based on data replication from

HRMS (NIC) to HRMS (DoGR) to this

HRMS module. The other set of tables

will be managed fully by this HRMS

51

module and will be used to provide the

above mentioned functionality.

12 Analytics Dash-

board

Vendor must integrate with CCTNS to build

the Analytics dashboards with the ability to

specify multiple parameters like

a) Jurisdiction wise (Unit/ Subdivision/

Circle/ PS),

b) Time period like between Dates, pre-

vious year, year, yesterday, last week,

last month

c) Crime Classification

d) Major Head

e) Grave/ Spl. Grave/ Non-Grave

f) IPC/ Cr.PC/ SLL

g) Acts

h) Sections

i) Accused Name/ Complaint Name

j) Stage of Case

k) Investigation Officer

The bidder will also need to develop new

dashboards using data from Person Of In-

terest, Village Information Systems and

HRMS.

13 Standard and Crimi-

nal Analytics Reports

Vendor must integrate with CCTNS

for the User to access the following

reports while specifying report spe-

cific parameters. These reports are

already developed in

CCTNS/HRMS and intent is for the

bidder to integrate with CCTNS to

get access to these reports

a) FIR Analytics

b) Under Investigation

c) Pending Trail

d) History Sheets/ Rowdy Sheets

e) Court Disposal

f) Arrests/ 41 CrPC

52

g) Police Disposal and required analyt-

ics

Vendor must integrate with

CCTNS for the User to access the

following reports while specifying

report specific parameters:

a) Crime Petition/ Service Petition De-

tails

b) Reported Cases

c) 41 CrPC/ Arrested Persons

d) Property Lost

e) Property Recovered

f) Petty Cases

g) Case Status Details (UI/ PT/ CD)

h) NBW (Pending/ Executed)

i) Summons/ witness

j) Missing Persons/ Unknown Dead

Bodies

k) Beats Served (Total Beats/ Beats

Served)

l) Patrollings Served

m) Night Duties (L&O/ Crime/ Patrol/

Anti Dacoity/ Pickets.

n) Vehicle Checking (Vehicles

Checked/ Cases Booked)

o) Road Accidents (Fatal/ Non-Fatal/

Dead/ Injured)

p) History Sheets/ Rowdy Sheets

q) Dial 100/ 112

In addition to accessing reports from

CCTNS, the bidder will also be

asked to develop 100 new reports

from defined databases such as

PAIS, POI, VIS, etc

14 Integration with

ArcGIS

i. The Vendor has to integrate custom

ArcGIS solution into the Mobile

Application and panel wherever re-

quired. API, SDK of ArcGIS with

required number of license and

53

concurrent users will be provided

by the Department. Required sup-

port from ArcGIS will also be pro-

vided by the Department.

ii. Vendor has to whitelist URLs in

such way that unauthorized usage

of Custom ArcGIS Maps/ Google

Maps by third parties will restrict.

iii. Daily usage statistics of Google

Maps/ ArcGIS hits should be pro-

vided in Dash board manner.

iv. All Maps licenses should be de-

ployed at Punjab Police Data Cen-

tre.

15 CCTNS/HRMS mo-

bile and web App

Administrative Panel

i. An additional Centralised mobile

App Administrative Panel need to

be developed and deployed along

with mobile apps.

ii. Users with admin-level User ac-

cess must have access to this

Panel.

iii. Panel must support following fea-

tures:

a) View/ Manage Users: Admin must

be able to View/ modify/ activate/

inactivate other users from the

System. Admin must also be able

to reset password of other users

and once reset, temporary pass-

word shall be sent to user, which

user can use to generate new

password.

b) Add new member: Admin must be

able to add Users, assign them

user roles, and assign other pa-

rameters like Police Station, Dis-

trict, etc.

c) Analytics Reports: Different Usage

report of mobile Apps like Audit log

report of searches performed,

Event log of searches performed,

54

Hit List Report of the accused

found as "Best" by FRS, Statistics

Report of the usage of FRS, etc.

must be available on Panel as ta-

ble as well as chart formats, wher-

ever possible.

d) View records by missing infor-

mation: Admin must be able to

check cases with missing manda-

tory fields after different time

frames.

e) Send Alerts: Admin should be able

to send alerts as broadcast or to

single Users. These alerts must

appear as Mobile notifications

even when User is logged out of

Mobile App.

f) View Feedbacks: Admin must be

able to view different feedback

provided by different levels of Us-

ers. Admin can also choose to re-

ply to any such feedback.

g) User Activity Logging: Admin must

be able to view different activities

performed by Users and must be

able to filter these activities based

on activity type, date-time, User

levels, etc.

16 Offline data collec-

tion and sync mod-

ule

i. Mobile App must be able to col-

lect data even when there is short-

age or blockage of mobile network

coverage.

ii. Such data must be stored offline

on mobile devices in encrypted for-

mat.

iii. Once connectivity resumes, of-

fline saved data must be sync back

to Server.

17 Alerts i. System must send auto-mated

alerts in the form of SMS to Police

Station of accused residence and

55

to Police Station where FIR was

filed against the accused.

ii. Alerts related to Investigation (in-

tegration with CCTNS/HRMS)

iii. Alerts related to ‘Jail in/ Jail out’ on

basis of PAIS.

iv. Other alerts as defined by Depart-

ment

v. Cost of SMS for OTP must be

borne by the department for the

duration of warranty period.

18 Quality Assurance i. System must have the ability

to do automated quality assurance

in order for continual and con-

sistent improvement and mainte-

nance of process and data that en-

ables quality.

ii. System must identify if face is

matching from accused photo-

graph and must intimate Admin

and IO.

iii. System must also be able to

identify quality of face in accused

photograph and must intimate Ad-

min and IO in case of poor quality

of face is identified by the System.

iv. The FRS system should incor-

porate a continuous cycle of train-

ing of the Machine Learning Algo-

rithms in order to maintain and im-

prove its effectiveness

19 Real time feedback

mechanism

Users must be able to send their feed-

back to the command center to Cen-

tralized mobile App Administrative

Panel and same could be assisted by

the technical and operational team in

real time.

20 Other Guidelines i. User forms and GUI of application

must be intuitive and easy to use.

GUI should have menu driven

56

combo boxes, radio buttons etc. to

minimize number of key-strokes.

ii. Input data validation as per defined

rules, must take place in the device

itself through client software to

eliminate errors before sending

data to data base.

iii. While filling details, it should be

possible to go back to previous

screen any time, edit the data and

come back to present screen.

iv. SMS Gateway integration should

be done for enabling SMS services

to the registered users.

v. Software should be scalable or

made compatible to retrieve data/

share data from/ to transport De-

partment, CCTNS/HRMS applica-

tion, ICJS, e-Prisons, ERVTS Ap-

plication, etc. automatically by us-

ing API/ Web services.

vi. Provision should be there to main-

tain server data base with regular

data back up and crash recovery of

data.

vii. High Availability of application and

Security of data should be main-

tained.

viii.The App should be compatible with

any android/ iOS based device

(both Legacy and New versions)

and regularly to be monitored dur-

ing warrantee period.

ix. General help files should also be

available in mobile application.

x. The overall design should be pref-

erably implemented using required

minimum components thereby re-

ducing the capital and operational

expenditure. The system should be

architected in such a manner that

57

additional infra increases scalabil-

ity in a near linear manner

xi. However, there should not be any

compromise on performance, high

availability and scalability.

21 Deployment Consid-

erations

i. The Application at the backend will

be deployed on X86 based hard-

ware running Windows or Linux

based Operating Systems.

ii. Infra for the Application deploy-

ment will be provided by the De-

partment.

iii. The deployment architecture

should provide High Availability

with no single point of failure.

iv. In order to keep the TCO low, the

solution should be based on Open

Source Software components.

v. Vendor should give sizing recom-

mendations for 100,000 registered

users and 1000 concurrent users.

vi. It shall be the responsibility of the

Vendor to ensure App Stores coor-

dination and Management includ-

ing Hosting of Mobile app on differ-

ent App Stores for different mobile

apps such as Google Playstore,

Apple Appstore etc. as well as the

Credentials/ Payments on apps

stores

vii. Network Load Time/Performance -

Vendor must evaluate the App

with different data load time of the

app on different network types and

speed of the app on all of the pop-

ular 2G, 3G, 4G, 5G networks

across different platforms and

compare the performance with

other popular apps and make con-

58

tinuous improvements so as to en-

hance user engagements and fast

loading of app.

viii. The test conducted should be

through an industry used tool

across platforms and not manual.

The device specifications (OS,

memory, processor etc.) used for

these tests (both Android and iOS

and other applicable platforms in-

cluding web) must be among the

most used category across the na-

tion. The cost of any tool used will

be borne by Vendor.

ix. The vendor will ensure Integration

of all the application modules for

seamless sharing of data across

divisions with adoption of

UNICODE 6.0 standard onwards.

32. Training

The successful bidder must train at-least 75 end users and 25 officers/

Master Trainers of Punjab Police in not less than 4 batches with no

batch exceeding 25 trainees, at a time/ place to be specified by Punjab

Police. The training would be assessed by a committee comprising of

officers of Punjab Police and Representatives of the company. The

training would have to be carried out to the satisfaction of Punjab Po-

lice. Infrastructure for organising the training will be provided by Punjab

Police.

59

Part-IV – Payments and Penalties:

33. Payment Schedule

33.1 Payment will be released to the implementing agency on com-

pletion of the following milestones as per the schedule pro-

vided below:

Milestone Condition of Completion Time Pe-

riod

% of Pay-

ment

M1 User authentication and

login to App, Record cre-

ation module of

CCTNS/HRMS, Search

(except FRS), Mobile App

Admin Panel, Offline

Data Collection and

Synch, Alerts, HRMS

Module, Reports on

HRMS

One Month

from sign-

ing of con-

tract

20 % of

project cost

excluding

AMC

M2 Person of Interest, Vil-

lage Information System

Two

Months

from sign-

ing of con-

tract

15 % of

project cost

excluding

AMC

M3 Facial Recognition

Search and integration

with mobile and web

app

Two months

and 15 days

from signing of

contract

25 % of

project cost

excluding

AMC

M4 Integration with specified

databases (CCTNS/HRMS,

VIS, POI) and systems

(ArcGIS, CCTNS/HRMS,

ICJS, e-Prisons, Saanjh,

Three

months and

15 days

15 % of

project cost

excluding

AMC

60

PAIS), Analytics Dash-

board, Reports (Standard

and Analytics reports)

from sign-

ing of con-

tract

M5 Finalisation/ Stabilisation

of the application.

Three

months

from the

date of Go-

Live

25 % of

project cost

excluding

AMC

33.2 In case of delay in the supply/ completion of product/ services/

project beyond the prescribed period penalty @ 0.05% of the

payable amount of the relevant mile stone(s) amount will be

imposed per day till the delay continues, subject to a maximum

of 10% of the Amount payable for the concerned Milestone.

33.3 No recovery of penalty will be made if the delayed supplies

are accepted by extending the delivery period by the depart-

ment.

33.4 The department may allow extension of milestone deadline in

exceptional circumstances beyond the control of the supplier.

34. Payments on account of Annual Maintenance Contract

Payments on account of Annual Maintenance Contract for each year

would be paid on a quarterly basis. 25% of the amount due for that fi-

nancial year after deducting penalties, if any, on account of Annual

Maintenance Contract would be payable upon successful completion

of each quarter of that year.

35. Service Level Agreement

The implementing agency would be bound by the levels of service de-

tailed below for the maintenance of the application:

61

35.1 This Service Level Agreement would be operative from the

time of issue of User Acceptance Testing service and would

continue till the expiry of the Annual Maintenance Contract.

35.2 The Network Operation Centre (NOC) of Punjab Police would

be a Single Point of Contact (SPoC) for Punjab Police to inter-

act with the implementing agency with service requests for fix-

ing of any bugs/ break-downs/ technical issues.

35.3 The implementing agency would provide a dedicated email ID

for lodging of service requests. The date of and time stamp-

ing of the email would serve as a reference for the lodging of

the request.

35.4 The implementing agency would also provide an escalation

matrix detailing the names, designation, phone/ mobile num-

bers of the contact persons at the appropriate level.

35.5 The implementing agency shall attend to the service requests

immediately but not later than 48 hours from the lodging of the

service requests for critical bugs (which cause the system to

be non functional) and a workaround provided in 24 hours. In

case of non-critical bugs, the solution has to be provided in 7

calendar days.

35.6 In case the implementing agency does not attend to the ser-

vice requests within the stipulated period (48 hours for critical

bugs and 7 calendar days for non-critical bugs), it shall be lia-

ble for imposition of penalties at the following rates:

35.6.1 Upto 2 days from the expiry of stipulated period.

Rs. 2,000/- per day or part thereof.

35.6.2 Beyond 2 days but before 6 days from the expiry of

stipulated period. Rs. 5,000/- per day or part thereof.

35.6.3 Beyond 6 days after the expiry of stipulated period.

Rs. 10,000/- per day or part thereof.

62

Annexure – 1

BIDDER PARTICULARS

(Enclose with Technical Bid)

1 Bidder type (Please tick any one) : Individual Consortium

2 Name of Individual Bidder/ Prime Bidder (in case of consortium)

:

3 Name of partner in case of consortium :

4 Particulars of Individual Bidder/ Prime Bidder :

Name of the Bidder :

Address of the Bidder :

Name & address of the person to whom all references shall be made regarding this ten-der enquiry

:

Telephone :

Mobile :

Fax :

E-mail :

Website

5 Particulars of consortium partner (if any) :

Telephone :

Mobile :

Fax :

E-mail :

Website

Signature :

Name :

Designation :

Company Seal :

63

Annexure - 2

BID FORM

(Enclose with Technical Bid)

To,

_____________________

_____________________

_____________________

Sir,

Having examined terms & conditions of tender for Selection of Agency for De-

velopment, Implementation and Maintenance of CCTNS/HRMS mobile app and

web with Al powered search and quality validation for Punjab Police, we

_________ (Name of the firm/ company), offer to develop, implement and main-

tain the same (including the AMC) in conformity with the said e-Tender.

We undertake, if our bid is accepted, to develop, implement and maintain the

proposed application software and provide all related services as per require-

ment and specifications of Punjab Police.

We further undertake that, if our bid is accepted, we will provide the perfor-

mance bank guarantee of a Commercial Bank of a sum equivalent to 5% of the

Contract Price including AMC for the due performance of the Contract as per

terms and conditions of the e-Tender.

This bid together with your written acceptance thereof and your notification of

award shall constitute a binding Contract between us.

We have noted the terms of Contract and agree to abide by terms and condi-

tions of the same.

SIGNATURE AND SEAL OF BIDDER

64

Annexure-3

GUARANTEE

(Enclose with Technical Bid)

To,

_____________________

_____________________

_____________________

Ref: e-Tender for Selection of Agency for Development, Implementation

and Maintenance of CCTNS/ HRMS mobile and web app with Al

powered search and quality validation.

We guarantee that development, customization and rollout of the above mobile

and web app shall be of the highest grade and quality and consistent with the

established and generally accepted standards for the mobile applications of the

type ordered and shall be in full conformity with the specifications/ samples.

We shall be fully responsible in case any software issues, bugs, vulnerabilities

and such other similar issues are found in the material and guarantee to ad-

dress these issues as defined in the Service Level Agreement.

SIGNATURE OF THE WITNESS SIGNATURE AND SEAL DATE OF BIDDER