open competitive bid (ocb) for consulting services on

APTS – RFP for Consulting Services on Assessment of ‘Mee Seva’ Service Delivery Platform for Performance High Availability & Certainty of Delivery ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

of 15

Open Competitive Bid (OCB)

for

Consulting Services on Assessment of ‘Mee Seva’ Service Delivery Platform for Performance High Availability & Certainty of Delivery

Bid calling date 28.06.2013 Pre-bid conference date/ time 03.07.2013, 11.30 AM at APTS Bid closing date/time 16.07.2013, 03-00 PM Bid Document Fee Rs.25,000/- APTS Contact person M.Sridhara Chary, SE,APTS

[email protected] [email protected],[email protected]

APTS Reference No. APTS/CS/RFP-ASSMT-MEESEVA /2013

For further details regarding detailed Tender Notification, specifications and digital certificate please visit http://www.apts.gov.in and www.eprocurement.gov.in.

Managing Director, A.P. Technology Services Ltd.


of 15

1. Introduction to ‘Mee Seva’ Service Delivery Platform

‘Mee Seva’ is the primary Government to Citizens (G2C) services delivery platform of the Government of Andhra Pradesh (GoAP). ‘Mee Seva’ service delivery is also aligned to the vision of National eGovernance Plan in terms of

“bringing all Government services closer to the citizens in an easily accessible manner through multiple channels”.

Nearly 112 G2C services spanning Revenue, Registration, Police, Municipality, Transport, Civil Supplies, & Education departments of GoAP are currently delivered through ‘Mee Seva’ platform. The detailed list of services is given in Appendix I.There are plans to increase the number of services delivered through ‘Mee Seva’ platform to more than 300 in the next six months. This may involve integration with multiple Department systems deployed on heterogeneous platforms.

‘Mee Seva’ services are delivered through nearly 6,500 Front‐End delivery points (aka‘Mee Seva’ Service Centers), spread across 23 districts of Andhra Pradesh. ‘Mee Seva’ service centers are operated by operators belonging to multiple Service Center Agents(SCAs) and by APOnline Franchisees. The SCAs are appointed by Electronic Service Delivery (ESD) department, which is a part of Information Technology &Communications (IT&C) department of GoAP.

APOnline is a joint venture company promoted jointly by M/s TCS and Government of Andhra Pradesh. Different SCA operators operate ‘Mee Seva’ service centers in different districts of A.P. Multiple APOnline franchisees operate ‘Mee Seva’ service centers throughout the entire state. ‘Mee Seva’ services are delivered through a common portal accessible by SCA and APOnline operators.

The Front‐End part of ‘Mee Seva’ service delivery platform, the integration layer with Multiple department systems, a portion of the Back‐End request processing for certain category of services are implemented and maintained by APOnline team.

1.1 ‘Mee Seva’ service delivery architecture overview

‘Mee Seva’ services delivery platform can be viewed to be made up of the following Components (Refer Appendix I – Solution Architecture)

1. Front‐End delivery channels (‘Mee Seva’ centers) 2. Middle/Intermediate Layer consisting of systems in SCA, APOnline, data centers&

SSDG 3. Back‐End systems (i.e. Request Processing Systems) in State Data Center, in NIC

Data Center & in Departments 4. Network segments connecting the Front‐End delivery channels to Back‐End


of 15

systems through Middle Layer.

Front‐End delivery channels aka ‘Mee Seva’ service centers are located in all mandals of the 23 districts in A.P.The systems comprising the Middle /Intermediate Layer are located in SCA data centers and APOnline data center. Back‐End systems are located in the respective government departments, in State Data Center (SDC) and in NIC Data Center.

The SCA operated ‘Mee Seva’ centers in Hyderabad and Ranga Reddy districts, are connected through Andhra Pradesh State Wide Area Network (APSWAN) to the Back‐End systems located in SDC or in government departments (Refer Appendix I).

The ‘Mee Seva’ centers operated by SCAs, at District and Mandal levels are connected through multiple Internet Service Providers (ISPs).The ‘Mee Seva’ centers operated as APOnline franchises, are connected to APOnline data center in Hyderabad through multiple Internet Service Providers (ISPs). In turn APOnline Data Center is connected to SDC through an ISP link.Mee Seva centers in Districts and municipal areas are connected to nearest PoP of APSWAN through ISP and inturn connected to SDC. These centers also maintains redundancy by direct connection through ISPs. (Refer Appendix I –


of 15

Solution Architecture). The data center of the SCA in Hyderabad is connected to SDC through APSWAN network.

APSWAN network has 8 Mbps bandwidth from State to District Head Quarters and 2Mbps bandwidth from District to Mandal Head Quarters.

‘Mee Seva’ services delivery platform as well as many Back‐End Request processing systems in SDCare implemented using Microsoft Technologies leaving the participating departments in their own technologies such as Oracle, Starfish, Java etc.

1.2 ‘Mee Seva’ Services The 112 Services that are currently delivered through ‘Mee Seva’ platform are grouped into i) Category ‘A’ Services & ii) Category ‘B’ Services. Different Service Level Agreements (SLAs) are associated with Category ‘A’ & Category ‘B’ services.

Category ‘A’ services are usually Over The Counter (OTC) services and are delivered within the same day.Category ‘B’ services may require some field verification by the departments concerned and hence are usually delivered within a period of 7 –30 days.

1.3 ‘Mee Seva’ Service Charges The service charges for each service are fixed by ESD department in consultation with SCAs, APOnline and departments concerned.

The service charges are collected by the ‘Mee Seva’ service center operators and recorded in the ‘Mee Seva’ system. Then they are distributed to all stakeholders through designated bank accounts. ‘Mee Seva’ system facilitates this transfer and reconciliation of user charges with banks as well as with respective departments.

1.4 ‘Mee Seva’ Operational Support ‘Mee Seva’ platform has integrated Short Messaging Services (SMS) Alerts support for tracking the progress of service requests. In addition through ‘Mee Seva’ Request Tracking System (MRTS) all users of ‘Mee Seva’ can raise operational issues related to ‘Mee Seva’ and track them to their resolution.

‘Mee Seva’ platform also incorporates a comprehensive online reports system which tracks multiple metrics related to the services delivered .

(Refer to Appendix I, for more details on Functional Architecture and Functional Description of ‘Mee Seva’).


of 15

2. Need for Request for Proposal (RFP) i) ‘Mee Seva’ services delivery platform has been in operation for more than a year during which period the configuration of delivery platform has been evolving in addition to multi‐fold increase in the number of services being delivered.

ii) ‘Mee Seva’ delivery platform incorporates a varied mix of front‐end, back‐end and intermediate systems deployed using multiple technologies. Network connectivity among these components is also of different bandwidths.

iii) In this heterogeneous environment which is also changing continuously, performance assessment of the entire ‘Mee Seva’ delivery platform is essential to determine the levels of availability and scalability for existing services delivered and future services planned.

iv) Such a performance assessment is intended to identify the existing as well as potential areas of performance bottlenecks if any and recommend mitigating actions. Thus in order to ensure the sustainability of ‘Mee Seva’ service delivery platform, in the present as well as in the future, it is necessary to undertake this performance assessment exercise now.

3. Scope Of Work 3.1The scope for the Assessment of ‘Mee Seva’ services delivery platform for performance covers the following components:

i) Front‐End Systems deployed in all ‘Mee Seva’ service centers (including Computer systems and Local Area Network components, if any deployed)

ii) Intermediate Layer Systems at SCA and APOnline data centers that process or route ‘Mee Seva’ service requests

iii) Back‐End Systems deployed in State Data Center (SDC) that are involved in processing ‘Mee Seva’ service requests

iv) Back‐End Systems deployed in NIC Data Center that are involved in processing ‘Mee Seva’ service requests

v) Back‐End Systems deployed in Departments that are involved in processing ‘Mee Seva’ service requests

vi) All Network elements interconnecting APOnline franchisee ‘Mee Seva’ service centers and APOnline Data Center through which ‘Mee Seva’ service requests are routed

vii) All Network elements interconnecting SCAs operated ‘Mee Seva’ service centers and data centers of SCAs, through ‘Mee Seva’ service requests are routed

viii) All Network elements interconnecting APOnline data center and SDC through ‘Mee Seva’ service requests are routed

ix) All Network elements interconnecting SCAs’ datacenters and SDC through ‘Mee Seva’ service requests are routed

x) All Network elements interconnecting Department systems and SDC through ‘Mee


of 15

Seva’ service requests are routed

xi) All Network elements interconnecting Department systems and APOnline data center through ‘Mee Seva’ service requests are routed

xii) All Network elements interconnecting Department systems and SCAs’ data centers through ‘Mee Seva’ service requests are routed

xiii) All Network elements that are part of APSWAN connectivity between SDC and A.P. Secretariat in the context of ‘Mee Seva’ service delivery

xiv) All Network elements that are part of APSWAN connectivity between SNC and DNC in the context of ‘Mee Seva’ service delivery.

xv) All network elements that are part of APSWAN connectivity between DNC and MNC in the context of ‘Mee Seva’ service delivery.

xvi) All network elements that are part of connectivity between MNC and Mee Seva center in the context of Mee Seva service delivery.

xvii) Payment Gateway, MSDG and SSDG Services

3.2 The bidder shall determine the System Under Test (SUT) consisting of the Front‐End systems, Intermediate Systems, Back‐End Systems and the interconnecting Network elements, specific to delivery of each service and assess the performance for each such configuration. The bidder shall also test ‘Mee Seva’ Services response time.

3.3 For each System Under Test (SUT) the bidder shall assess the following components comprising the SUT:

i. Network Tier (including Firewall, Load Balancer, Routers, Network Interface Cards, & Cabling between all components)

ii. Web Server Tier iii. Application Server Tier and iv. Database Server Tier

3.4 The bidder shall assess the ‘Mee Seva’ service delivery platform for the potential bottlenecks in Network, Web, Application, & DB Server and storage layers as indicated in Appendix VI.

3.5 The bidder shall determine the Performance Profiles for the System Under Test (SUT) before proceeding with testing for performance characteristics indicated in Appendix VII.

3.6 The performance bottlenecks related to the delivery of “Mee Seva” services listed Appendix V, shall be assessed.

3.7 The bidder shall establish key control points in the transaction paths pertaining to ‘Mee Seva’ services being assessed and compare the results with the expected norms of the given configuration.

3.8 The bidder shall also assess the adequacy of HW, Network resources deployed with respect to the estimated / projected volume of transactions, response time etc.


of 15

3.9 The bidder shall assess the robustness of the application architecture in terms of handling varying loads and other system break down conditions.

3.10 The bidder shall determine the best response time that can be achieved in the current configuration for handling 500+ services and shall propose changes to the configuration to achieve a response time in line with the Service Level Agreement.

3.11 The bidder shall determine appropriate benchmarks applicable to the ‘Mee Seva’ services delivery platform and assess the performance in the context of such benchmarks.

3.12 The bidder shall propose the approach to determine performance bottlenecks and obtain consensus of all stakeholders before proceeding with it.

3.13 The bidder shall use appropriate ‘State of the Art’, Load / Performance Testing techniques and tools as applicable to the web technologies used in the implementation of ‘Mee Seva’ services delivery platform.

3.14 The bidder shall complete the Performance assessment of ‘Mee Seva’ service delivery platform within an elapsed time period not exceeding 12 weeks from the date of award of contract.

3.15 The bidder shall deploy adequate resources as required for Load / Performance testing to determine the performance bottlenecks in ‘Mee Seva’ services delivery platform in the committed timelines.

3.16 The bidder shall deploy adequate number of resources in parallel but collaborating teams for conducting performance tests in the Front‐end systems (browsers, local servers if any), Back‐end & Intermediate systems (comprising of Web, Application, & Database Servers)and the interconnecting Network elements. Each of the Team Leaders for such teams will have a minimum 5 years of experience in the area the respective team is deployed(i.e. Front‐End Browsers, Back‐End systems: Application, Database, O.S., Webserver, etc.,& Network elements – switches, routers, firewalls/UTMs, proxy servers, etc.). Each team will have not less than 3 consultants, each of whom have a minimum 3 years of experience in Performance/Load Testing. The team assigned to work on Network performance assessment will have relevant and adequate experience in Wide Area Networks (WANs). The Team will also include consultants with minimum 10 years experience in Web Architecture Assessment preferably in Microsoft .Net Web Frameworks. The Project Leader/Manager will have a minimum 10 years of relevant experience that is aligned to the requirements of the current engagement.

3.17 The bidder shall perform Load / Performance Testing on production/staging environment of ‘Mee Seva’ service delivery platform as less intrusively as possible.

3.18 The bidder shall maintain all logs of the Load/Performance Testing performed and support the findings / conclusions with relevant data.

3.19 The bidder shall prioritise the services to be assessed according to the categories and propose a timeline for assessment not exceeding 3 weeks of elapsed time from the date of award of contract.


of 15

3.20 The bidder shall assess the deployment architecture of ‘Mee Seva’ service delivery platform, the network architecture for their suitability to achieve the determined benchmarks.

3.21 The bidder shall assess the performance bottlenecks in terms of the source, the reason and the proposed mitigation and report such findings as per the format given in the Technical Proposal (Refer Appendix IV)

3.22 The bidder shall report the findings in such a sequence as to reap the ‘low hanging’ fruits in terms of achieving the performance improvement.

3.23 The bidder shall report his findings in terms of Short and Long Term actions necessary to address the performance bottlenecks.

3.24 The bidder shall submit a Performance Assessment report based on Performance Assessment. The report shall clearly state the symptoms, the causes and the proposed remedial actions for each cause. The report shall prioritise the causes according to their impact on the ‘Mee Seva’ service delivery platform. The findings in the report shall be backed by analysis based on sufficient data points. Indicative timelines of implementation of remedial actions shall also form part of the Performance Assessment report.

3.25 The Performance Assessment report shall include suggestions for improving the Application, Database & Web Server Architectures as well as Industry Best Practices for the technologies used in ‘Mee Seva’ service delivery platform.

3.26. The bidder shall indicate the extent of utilization of various components of the ‘Mee Seva’ service delivery platform in terms of labels such as “Under” / “Over” / “Optimal” utilization, in the Performance Assessment report. Further the approach/strategy for transitioning each component operating in “Under” / “Over” utilization modes to “Optimal” utilization mode and the indicative timelines for the same, shall be included in the report.


of 15

4. Instructions to Bidders 4.1 Completeness of Response

a. Bidders are advised to study all instructions, forms, requirements and other information in the RFP documents carefully. Submission of the bid shall be deemed to have been done after careful study and examination of the RFP document with full understanding of its implications.

b. The response to this RFP should be full and complete in all respects. Failure to furnish all information required by the RFP documents or submission of a proposal not substantially responsive to this document will be at the Bidder's risk and may result in rejection of its Proposal.

4.2 Proposal preparation costs & related issues a. The bidder is responsible for all costs incurred in connection with participation in this

process, including, but not limited to, costs incurred in conduct of informative and other diligence activities, participation in meetings/discussions/presentations, preparation of proposal, in providing any additional information required by APTS to facilitate the evaluation process.

b. APTS will in no case be responsible or liable for those costs, regardless of the conduct or outcome of the bidding process.

c. This RFP does not commit APTS to award a contract or to engage in negotiations. Further, no reimbursable cost may be incurred in anticipation of award or for preparing this RFP.

d. All materials submitted by the bidder will become the property of APTS and may be returned completely at its sole discretion.

4.3 Prebid Meeting a. APTS shall hold a pre‐bid meeting with the prospective bidders on 03‐07.2013, at

11:00 a.m. By email on or before 03.07.2013 5:00 p.m. The Office of the Managing Director, Andhra Pradesh Technology Services Ltd., IV Floor, BRKR Bhavan, Tank bund Road, Hyderabad – 500063

b. The Bidders will have to ensure that their queries for Pre‐Bid meeting should reach to:

The Managing Director Andhra Pradesh Technology Services Ltd., IV Floor, Boorgula Rama Krishna Rao (BRKR) Bhavan, Tank bund road, Hyderabad – 500 063

Telephone: (040) 2322 0305, (040) 2322 3753 Fax: (040) 2322 7458 Email: [email protected]


of 15

c. All and any queries related to Scope of work, Payment Terms and mode of selection will be entertained during Pre‐bid clarifications meeting.

d. Max. Two representatives authorized by the company will be permitted to attend the meeting.

4.4 Responses to Prebid Queries and Issue of Corrigendum a. The Nodal Officer notified by the APTS will endeavour to provide timely response to all

queries. However, APTS makes no representation or warranty as to the completeness or accuracy of any response made in good faith, nor does APTS undertake to answer all the queries that have been posed by the bidders.

b. At any time prior to the last date for receipt of bids, APTS may, for any reason, whether at its own initiative or in response to a clarification requested by a prospective Bidder, modify the RFP Document by a corrigendum.

c. The Corrigendum(if any)&clarifications to the queries from all bidders will be posted in the portal (URL‐http://apts.gov.in) and www.eprocurement.gov.in.

d. Any such corrigendum shall be deemed to be incorporated into this RFP. e. In order to provide prospective Bidders reasonable time for taking the corrigendum into

account, APTS may, at its discretion, extend the last date for the receipt of RFP Proposals.

4.5 Right to Terminate the process a. APTS may terminate the RFP process at any time and without assigning any reason.

APTS makes no commitments, express or implied, that this process will result in a business transaction with anyone.

b. This RFP does not constitute an offer by APTS. The bidder's participation in this process may result in short listing of the bidder.

4.6 Preparation of Proposals a. The Proposal as well as all related correspondence exchanged by the bidders and APTS

shall be written in English language, unless specified otherwise.

b. In preparing their Proposal, Consultants are expected to examine in detail the documents comprising the RFP. Material deficiencies in providing the information requested may result in rejection of a Proposal.

c. The Technical Proposals shall contain an Executive summary giving a brief overview of the manner in which the bidder proposes to achieve the outcomes and the assessment of resources required.

d. The bidder is expected to submit the Technical Proposal as per the format given in Appendix III. Submission of the wrong type of Technical Proposal will result in the proposal being deemed non‐responsive. The Technical Proposal shall not include any financial information.

e. The Financial Proposal shall be prepared as per the format given in Appendix.

4.7 Submission of Responses a. The bidder shall submit the bid through eProcurement platform only.

b. The bidder shall submit (3) proposals – Pre‐Qualification Proposal, Technical Proposal as and Financial Proposal as per format given in Appendixes on eprocurement portal.


of 15

c. The original proposal both Technical and Financial shall contain no interlineations or overwriting, except as necessary to correct the errors made by the bidders themselves. The same authorized representative who has signed the proposal shall initial the corrections.

d. An authorized representative of the bidders shall initial all the pages of the original Technical and Financial Proposals. The authorization shall be in the form of written power of attorney accompanying the proposal and supported by any evidence that the representative has been duly authorized to sign.

e. One copy of the documents necessary for Pre‐Qualification as per the format given in Appendix II, shall be submitted . An authorized representative of the bidders shall initial all pages of Pre‐Qualification documents submitted.

f. The bidder shall submit one softcopy of the Technical Proposal in the form of an on‐rewriteable CD. CD media must be duly signed using a Permanent pen Marker and should bear the name of the bidder.

g. Bidder must ensure that the information furnished in the CD is identical to that submitted in the original paper document. In case of any discrepancy, the information furnished in the original paper document will prevail over the soft copy.

h. The bidder shall ensure that the proposal cost quoted in the Cost Break‐up form (Form‐F2) matches with the total cost (inclusive of taxes) quoted in the Financial Proposal form (Form‐F1).

4.8 Bid Submission Format a. The entire proposal shall be strictly as per the format specified in this Invitation for

Expression of Interest and any deviation may result in the rejection of the RFP proposal.

b. The documents to be submitted for Pre‐Qualification are:

i. Form‐PQ1: Covering Letter on the letterhead of the bidder with correspondence details

ii. Form‐PQ2: Details of Applicant’s Operations and Consulting Business

iii. Form‐PQ3: Compliance sheet for Pre‐Qualification criteria

c. The documents to be submitted for Technical Proposal are:

i. Executive Summary

ii. Form‐T1: Description of approach, methodology and work plan for performing this assignment

iii. Form‐T2: Team Composition and Task Assignment

iv. Form‐T3: Curriculum Vitae of the staff engaged in this assignment

v. Form‐T4: Proposed Work Schedule

vi. Form‐T5: Indicative Format for Assessment Report

vii. Form‐T6: Comments & Suggestions regarding Scope Of Work and support required (Optional)

d. The documents to be submitted for Financial Proposal are:


of 15

i. Form‐F1: Financial Proposal submission Form

ii. Form‐F2: Financial Proposal Cost Break‐up Form

4.9 Venue and deadline for submission

a. Proposals must be submitted through eProcurement Platform only on or before the last date time given.

b. Any proposal received by the APTS after the above deadline shall be rejected.

c. The bids submitted by telex/telegram/fax/e‐mail, etc. Shall not be considered. No correspondence will be entertained on this matter.

d. APTS reserves the right to modify and amend any of the above‐stipulated

condition /criterion depending upon assignment/project priorities vis‐à‐vis urgent commitments.

4.10 Short listing Criteria

a. APTS will shortlist bidders who meet the Pre‐Qualification criteria mentioned in this Invitation to RFP.

b. Any attempt by a Bidder to influence the bid evaluation Process may result in the rejection of its RFP Proposal.

c. APTS will constitute a Proposal Evaluation Committee to short‐list the bidders according the Pre‐Qualification criteria given in this document.

4.11 Evaluation Process a. The bidders will be shortlisted based on the Pre‐Qualification criteria as given in

section 5 of this RFP document.

b. There will be 3 stage evaluation of the proposals submitted by the bidders.

c. The Technical Proposals of the Pre‐Qualified bidders shall be evaluated as per the criteria given in section 6.

d. The bidders have to score a minimum of 70 marks out of 100 marks in the Technical Evaluation to be considered for Financial Evaluation.

e. The Financial Proposals of the bidders who have qualified in the Technical Evaluation will be evaluated as per the criteria given in section 7 & 8.

f. The overall method of evaluation is Quality cum Cost Based Selection (QCBS). The Technical Evaluation Score will be given a weightage of 70% and the Financial Evaluation Score, a weightage of 30%, in arriving at the overall score. The bidder who scores the highest overall score will be considered for selection.


of 15

5. PreQualification Criteria

a. The Proposal Evaluation Committee (PEC) shall determine the adherence of the bidders to the following Pre‐Qualification criteria based on the documents or other evidences provided:

S.No. Basic Requirement

Minimum Specific Requirement Documents Required

1 Legal Entity Should be Company registered under Companies Act, 1956 or a partnership firm registered under LLP Act, 2008 and also Registered with the Service Tax Authorities for last (5) years.

Should have been operating for the last three years.

Copy of Certificate of Incorporation; and Copy of Service Tax Registration Certificate

2 Sales Turnoverin IT Consulting related to Load/Performance Testing or Performance Bottlenecks Assessment of Web Portals / Web based Systems

Annual Sales Turnover generated from services related to IT Consulting pertaining to Web Portals / Web Applications Performance Assessment during each of the last three financial years (as per the last published Balance sheets), should be at least Rs.50 Lakhs.

This turnover should be on account of IT consulting related to Load/Performance Testing or Performance assessment of Web Portals or Web Applications only and should not comprise of sales revenues related to supply of hardware/IT infrastructure, software development and their associated maintenance services, implementation of packaged software etc.

Extracts from the audited Balance sheet and Profit & Loss;

OR

Certificate from the statutory auditor

3 Technical Capability

Bidder must have successfully completed at least any of the following consulting engagements of values specified herein : One project of Performance Assessment/ Load Testing for Performance of Web Portals or Web Applications, not less than the amount INR 50 Lakhs;

Completion Certificates from the client; OR Work Order + Self Certificate of Completion (Certified by the CEO/CFO);


of 15

OR Two (2) projects of similar nature not less than the amount equal INR 30 Lakhs each; OR Three (3) projects of similar nature not less than the amount equal INR 20 Lakhs each.

4 Certifications National / International / Industry Certifications pertaining to capability in Load / Performance Testing of Web Portals / Web Applications.

Copy of valid Certificates

5 Manpower / Resources

Bidder shall have adequate spare manpower for deployment in this engagement as per committed timelines Consultant shall provide evidence of capability to deploy a team as per the requirements given in section 3.16. within a week of award of contract.

Self‐Certification by the authorized signatory

6 Blacklist Bidder should give a Declaration that the Bidder has not been debarred/ blacklisted as on bid calling date by any Central or State Govt./ Quasi–Govt. Departments or organizations for non‐satisfactory past performance, corrupt, fraudulent or any other unethical business practices as per Format given in Form P7. If the bidder is debarred/ blacklisted as mentioned above after bid calling date and during execution of the contract, APTS reserves the right to withdraw the Notification of Award issued/ contract entered with the bidder and to cancel the tender/ to negotiate with the L2 bidder for entering into the contract

A self‐ declaration letter

7 Consortium Bidder can be an individual organization or Consortium i.e., One Prime Bidder and maximum Two Partners are allowed.


of 15